From c1909001a1619e1a635cfe108d233f00504d9222 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 22 Nov 2024 18:02:55 +0900 Subject: [PATCH 001/952] Update .github/workflows/close-stale-issues.yml: include PRs Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 26 ++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index a05a4e3cb..93991b521 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -1,11 +1,12 @@ --- -name: 'Close stale issues' +name: 'Close stale issues and PRs' on: # yamllint disable-line rule:truthy schedule: - cron: '30 1 * * *' permissions: issues: write + pull-requests: write jobs: stale: @@ -14,14 +15,31 @@ jobs: steps: - uses: actions/stale@v9 with: - # Don't process pull requests at all - days-before-pr-stale: -1 + # An allow-list of label(s) to only process the issues/PRs which contain one of these label(s). + any-of-labels: 'needs-info' + ###################################################################### + # Issues + ###################################################################### stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.' close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity. If this issue is still reproduced, feel free to provide the issue with up-to-date information.' stale-issue-label: 'stale' # Add this label to exempt the issue from being marked as stale due to inactivity exempt-issue-labels: 'confirmed' # An allow-list of label(s) to only process the issues which contain one of these label(s). - any-of-issue-labels: 'question,needs-info' + any-of-issue-labels: 'question' + ###################################################################### + # PRs + ###################################################################### + days-before-pr-stale: '365' + days-before-pr-close: '30' + stale-pr-message: 'This PR is stale because it has been open a year with no activity. Remove stale label or this will be closed in 30 days.' + close-pr-message: 'This PR was closed because it has been stalled for 30 days with no activity.' + stale-pr-label: 'stale' + # Add this label to exempt the PR from being marked as stale due to inactivity + exempt-pr-labels: 'confirmed' + # An allow-list of label(s) to only process the PRs which contain one of these label(s). + any-of-pr-labels: 'needs-rebase' + # Use this to ignore updates such as comments (only to keep the PR alive by bumping) + # ignore-pr-updates: true # Use this to do a dry run from a pull request # debug-only: true From b979bfed9ee53c403f59af5655efd8b439cbea99 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 22 Nov 2024 18:13:26 +0900 Subject: [PATCH 002/952] Update .github/workflows/close-stale-issues.yml: create issues/PRs section Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 93991b521..44124c2e2 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -15,8 +15,13 @@ jobs: steps: - uses: actions/stale@v9 with: + ###################################################################### + # Issues/PRs + ###################################################################### # An allow-list of label(s) to only process the issues/PRs which contain one of these label(s). any-of-labels: 'needs-info' + # Use this to do a dry run from a pull request + # debug-only: true ###################################################################### # Issues ###################################################################### @@ -41,5 +46,3 @@ jobs: any-of-pr-labels: 'needs-rebase' # Use this to ignore updates such as comments (only to keep the PR alive by bumping) # ignore-pr-updates: true - # Use this to do a dry run from a pull request - # debug-only: true From 94f15c451e11835eeef44bc14bf12784c165c940 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 22 Nov 2024 18:13:49 +0900 Subject: [PATCH 003/952] Update .github/workflows/close-stale-issues.yml: set exempt-assignees Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 44124c2e2..8e5c045df 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -18,6 +18,7 @@ jobs: ###################################################################### # Issues/PRs ###################################################################### + exempt-assignees: 'spantaleev,aine-etke' # An allow-list of label(s) to only process the issues/PRs which contain one of these label(s). any-of-labels: 'needs-info' # Use this to do a dry run from a pull request From 77ef807c54b8bc63d127e573cfee3ab17f12dda8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 23 Nov 2024 15:55:38 +0900 Subject: [PATCH 004/952] Update .github/workflows/close-stale-issues.yml: set ignore-pr-updates to true Without this option, stale counters for each PR keep restarting whenever any update occurs or a comment is added to them. Since the counters for PR are set to 365 days, ignore-pr-updates should help us to get rid of zombie PRs (which are kept open by bumps). Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 8e5c045df..88db2d986 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -46,4 +46,4 @@ jobs: # An allow-list of label(s) to only process the PRs which contain one of these label(s). any-of-pr-labels: 'needs-rebase' # Use this to ignore updates such as comments (only to keep the PR alive by bumping) - # ignore-pr-updates: true + ignore-pr-updates: true From ce0036e3963d2ce07d90a9895db3f5e868d8d06a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 23 Nov 2024 22:31:46 +0900 Subject: [PATCH 005/952] Set operations-per-run to 100 https://github.com/spantaleev/matrix-docker-ansible-deploy/actions/runs/11987582115/job/33421900339?pr=3813 has performed 62 operations, and 100 should be sufficient for a while. Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 88db2d986..45f31da7b 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -1,6 +1,8 @@ --- name: 'Close stale issues and PRs' on: # yamllint disable-line rule:truthy + # Use this to do a dry run from a pull request + # pull_request: schedule: - cron: '30 1 * * *' @@ -19,6 +21,7 @@ jobs: # Issues/PRs ###################################################################### exempt-assignees: 'spantaleev,aine-etke' + operations-per-run: 100 # An allow-list of label(s) to only process the issues/PRs which contain one of these label(s). any-of-labels: 'needs-info' # Use this to do a dry run from a pull request From c8affda9db43c44c6cee90de286f0d348ab23bf3 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sat, 23 Nov 2024 20:04:02 +0000 Subject: [PATCH 006/952] Update dependency docker to v7.4.3 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 0ed10a4fd..6bf8ddff5 100644 --- a/requirements.yml +++ b/requirements.yml @@ -10,7 +10,7 @@ version: v0.2.0-0 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker - version: 7.4.2 + version: 7.4.3 name: docker - src: git+https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python.git version: 129c8590e106b83e6f4c259649a613c6279e937a From ea7ffa8929a22689f7697e497379b28038584450 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 25 Nov 2024 13:13:43 +0900 Subject: [PATCH 007/952] Update .github/workflows/close-stale-issues.yml: edit stale messages and fix any-of-labels This is a follow-up to 5483925ee4ed40b6d4129e22b714dcf588a97520. Since any-of-issue/pr-labels overrides any-of-labels, the values specified by the latter need to be specified by the former. Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 45f31da7b..5612e7cc7 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -22,31 +22,29 @@ jobs: ###################################################################### exempt-assignees: 'spantaleev,aine-etke' operations-per-run: 100 - # An allow-list of label(s) to only process the issues/PRs which contain one of these label(s). - any-of-labels: 'needs-info' # Use this to do a dry run from a pull request # debug-only: true ###################################################################### # Issues ###################################################################### - stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.' + stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. To exempt the issue from being marked as stale again due to inactivity, add "confirmed" label.' close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity. If this issue is still reproduced, feel free to provide the issue with up-to-date information.' stale-issue-label: 'stale' # Add this label to exempt the issue from being marked as stale due to inactivity exempt-issue-labels: 'confirmed' # An allow-list of label(s) to only process the issues which contain one of these label(s). - any-of-issue-labels: 'question' + any-of-issue-labels: 'needs-info,question' ###################################################################### # PRs ###################################################################### days-before-pr-stale: '365' days-before-pr-close: '30' - stale-pr-message: 'This PR is stale because it has been open a year with no activity. Remove stale label or this will be closed in 30 days.' + stale-pr-message: 'This PR is stale because it has been open a year with no activity. Remove stale label or this will be closed in 30 days. To exempt the PR from being marked as stale again due to inactivity, add "confirmed" label.' close-pr-message: 'This PR was closed because it has been stalled for 30 days with no activity.' stale-pr-label: 'stale' # Add this label to exempt the PR from being marked as stale due to inactivity exempt-pr-labels: 'confirmed' # An allow-list of label(s) to only process the PRs which contain one of these label(s). - any-of-pr-labels: 'needs-rebase' + any-of-pr-labels: 'needs-info,needs-rebase' # Use this to ignore updates such as comments (only to keep the PR alive by bumping) ignore-pr-updates: true From 204878709a17632b02ca9309886ad3f1b8ef3825 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 25 Nov 2024 14:01:56 +0900 Subject: [PATCH 008/952] Update .github/workflows/close-stale-issues.yml: correct the stale message for PRs Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 5612e7cc7..3a799821b 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -39,7 +39,7 @@ jobs: ###################################################################### days-before-pr-stale: '365' days-before-pr-close: '30' - stale-pr-message: 'This PR is stale because it has been open a year with no activity. Remove stale label or this will be closed in 30 days. To exempt the PR from being marked as stale again due to inactivity, add "confirmed" label.' + stale-pr-message: 'This PR is stale because it has not been provided with required information or its conflicts have not been fixed over a year. Remove stale label or this will be closed in 30 days. To exempt the PR from being marked as stale again due to inactivity, add "confirmed" label.' close-pr-message: 'This PR was closed because it has been stalled for 30 days with no activity.' stale-pr-label: 'stale' # Add this label to exempt the PR from being marked as stale due to inactivity From b940b8591479b29e31a80a8bae47943f79adda26 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 25 Nov 2024 17:03:18 +0900 Subject: [PATCH 009/952] Edit docs/maintenance-migrating.md (#3816) * Edit docs/maintenance-migrating.md: replace the numbering list with sections for each item Also: add an ansible-playbook command with the stop tag as the main command to stop the Matrix services. Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: move the note under the header Signed-off-by: Suguru Hirahara * Update docs/maintenance-migrating.md Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: add a section "checking if services work" The commit does not include the detail as having another similar section increases doubles effort to maintain them and increases possibility of causing discrepancy. Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: add a note about joining the support room on Matrix Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: replace hosts with inventory/hosts Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: instruction to run ansible-playbook commands locally Signed-off-by: Suguru Hirahara * Edit docs/maintenance-migrating.md: edit the check section Signed-off-by: Suguru Hirahara * Update docs/maintenance-migrating.md Co-authored-by: Slavi Pantaleev * Update docs/maintenance-migrating.md: reflect the review and edit a note for creating a temporary account on another server Signed-off-by: Suguru Hirahara * Minor rewording in maintenance-migrating.md --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- docs/maintenance-migrating.md | 77 +++++++++++++++++++++++++++++------ 1 file changed, 65 insertions(+), 12 deletions(-) diff --git a/docs/maintenance-migrating.md b/docs/maintenance-migrating.md index d71a13e3d..29a2beb52 100644 --- a/docs/maintenance-migrating.md +++ b/docs/maintenance-migrating.md @@ -1,14 +1,67 @@ -> **Note**: This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`). -> -> If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is not possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore. - # Migrating to new server -1. Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes (step 4 below) would happen faster, leading to less downtime -2. Stop all services on the old server and make sure they won't be starting again. Execute this on the old server: `systemctl disable --now matrix*` (you might have to cd to /etc/systemd/system/ first) -3. Copy directory `/matrix` from the old server to the new server. Make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)! -4. Make sure your DNS records are adjusted to point to the new server's IP address -5. Remove old server from the `inventory/hosts` file and add new server. -6. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user`. This will create the `matrix` user and group on the new server -7. Because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files manually by running this on the new server: `chown -R matrix:matrix /matrix`. -8. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` to finish the installation and start all services +This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**. + +**Notes**: +- This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`). + + If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore. +- If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance. + +- You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment. + +## Lower DNS TTL + +Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime. + +## Stop services on the old server completely + +Before migrating, you need to stop all services on the old server and make sure they won't be starting again. + +To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server. + +Log in to the old server and run the command as `root` (or a user that can run it with `sudo`): + +```sh +cd /etc/systemd/system/ && systemctl disable --now matrix* +``` + +## Copy data directory to the new server + +After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)! + +## Adjust DNS records + +Make sure your DNS records are adjusted to point to the new server's IP address. + +## Update `inventory/hosts` file + +Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server. + +## Create `matrix` user and group on the new server + +Then, run the command below on your local computer to create the `matrix` user and group on the new server: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user +``` + +**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command: + +```sh +chown -R matrix:matrix /matrix +``` + +## Install and start all services on the new server + +Finally, run the command below on your local computer to finish the installation and start all services: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start +``` + +### Check if services work + +After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md) + +Having make sure that both services and federation work as expected, you can safely shutdown the old server. From 9ed782fcfdcd9889efd263220e78bc62247f0262 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 25 Nov 2024 17:22:20 +0900 Subject: [PATCH 010/952] Update docs/quick-start.md (#3818) * Edit docs/quick-start.md: add recommended server specs Signed-off-by: Suguru Hirahara * Update docs/quick-start.md: fix an anchor link Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/quick-start.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/quick-start.md b/docs/quick-start.md index 11af61f11..6100c82dc 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -25,6 +25,8 @@ Please remember to replace `example.com` with your own domain before running any At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works). +When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory. + @@ -171,7 +173,7 @@ After configuring the playbook, run the command below and wait until it finishes ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files,start ``` -💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-the-installation-command). +💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command). After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain. From ad3534dd9e26a87367c1c0fad99adbc0b0fb6b71 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 23 Nov 2024 02:57:41 +0900 Subject: [PATCH 011/952] Update docs/maintenance-upgrading-services.md: replace the list with sections Signed-off-by: Suguru Hirahara --- docs/maintenance-upgrading-services.md | 36 ++++++++++++++++---------- 1 file changed, 23 insertions(+), 13 deletions(-) diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md index 94fcafdcc..57aa80dda 100644 --- a/docs/maintenance-upgrading-services.md +++ b/docs/maintenance-upgrading-services.md @@ -14,27 +14,37 @@ If you want to be notified when new versions of Synapse are released, you should ## Steps to upgrade the Matrix services +### Check the changelog + Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of. -If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, then: +### Update the playbook and the Ansible roles -- update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) using: +If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running: - - either: `just update` - - or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`) +- either: `just update` +- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`) - If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force` +If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force` - For details about `just` commands, take a look at: [Running `just` commands](just.md). +**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md). -- re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services: +### Re-run the playbook setup - ```sh - ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start - ``` +After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services: -Note that if you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with `--tags=setup-all` instead of `--tags=install-all`. See [this page on the playbook tags](playbook-tags.md) for more information. +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start +``` -A way to invoke these `ansible-playbook` commands with less typing is to run the `just` "recipe": `just install-all` or `just setup-all`. +If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with `--tags=setup-all` instead of `--tags=install-all`. See [this page on the playbook tags](playbook-tags.md) for more information. -**Note**: major version upgrades to the internal PostgreSQL database are not done automatically. To upgrade it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql). +#### Run `just` to execute shortcut command + +If you want to invoke the `ansible-playbook` command with less typing, you can run `just` to execute the shortcut command: `just install-all` (or `just setup-all`). Note that it restarts all services automatically. + +## PostgreSQL major version upgrade + +Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually. + +For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql). From fb82b4672301b27bc5da9a9d3b668e37cd17a487 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 26 Nov 2024 01:18:11 +0900 Subject: [PATCH 012/952] Update docs/README.md (#3822) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update docs/README.md: add "installation guides" section Add the emoji to the link to quick-start.md only and not to full installation guide to emphasize the quick start guide Signed-off-by: Suguru Hirahara * Update docs/README.md: move a link to faq.md down Signed-off-by: Suguru Hirahara * Update docs/README.md: add "Maintenance" section Add a hint to join the support room under "Maintenance" header. Signed-off-by: Suguru Hirahara * Update docs/README.md: create the "configuration options" section and add a note Signed-off-by: Suguru Hirahara * Update docs/README.md: sort list items Signed-off-by: Suguru Hirahara * Update docs/README.md: emphasize the anchor link to faq.md Signed-off-by: Suguru Hirahara * Update docs/README.md: add other anchor links to the "other documentation pages" section Signed-off-by: Suguru Hirahara * Update docs/README.md: add the emoji ℹ️ before the anchor link to faq.md Signed-off-by: Suguru Hirahara * Update docs/README.md: explanation about FAQ Remove the hint to check the installation guides as links to them are listed on top of this page. Signed-off-by: Suguru Hirahara * Update docs/README.md: update text of the anchor link to docs/getting-the-playbook.md Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/README.md | 87 +++++++++++++++++++++++++++++++++++--------------- 1 file changed, 62 insertions(+), 25 deletions(-) diff --git a/docs/README.md b/docs/README.md index 1b681bc88..7ab368150 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,49 +1,86 @@ # Table of Contents -- [FAQ](faq.md) - lots of questions and answers. Jump to [Prerequisites](prerequisites.md) to avoid reading too much and to just start a guided installation. +## ⬇️ Installaton guides -- [Quick start](quick-start.md) - follow the guide to set up minimum core services on your server +There are two installation guides available for beginners and advanced users. -- [Prerequisites](prerequisites.md) - go here to a guided installation using this Ansible playbook +- ⚡ **[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". -- [Configuring your DNS settings](configuring-dns.md) +- **Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide. -- [Getting this playbook's source code](getting-the-playbook.md) + - [Prerequisites](prerequisites.md) -- [Configuring the playbook](configuring-playbook.md) + - [Configuring your DNS settings](configuring-dns.md) -- [Installing](installing.md) + - [Getting the playbook](getting-the-playbook.md) - - **Importing data from another server installation** + - [Configuring the playbook](configuring-playbook.md) - - [Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional) + - [Installing](installing.md) - - [Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional) +## 🛠️ Configuration options - - [Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional) + - - [Server Delegation](howto-server-delegation.md) +You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md) - - Server Delegation via a well-known file (recommended): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server) +- [Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation - - [Serving the base domain](configuring-playbook-base-domain-serving.md) +- [Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver - - [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md) +- [Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation + +- [Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks + +- [Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains + +- [Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system + +- [File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder + + + +- [Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories + +## 👨‍🔧 Maintenance + +If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help. + + + +- [Checking if services work](maintenance-checking-services.md) + +- [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md) + +- [PostgreSQL maintenance](maintenance-postgres.md) + +- [Synapse maintenance](maintenance-synapse.md) + +- [Upgrading services](maintenance-upgrading-services.md) + +## Other documentation pages + +- ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook + + + +- [Alternative architectures](alternative-architectures.md) + +- [Container images used by the playbook](container-images.md) + +- [Obtaining an Access Token](obtaining-access-tokens.md) - [Playbook tags](playbook-tags.md) - [Registering users](registering-users.md) -- [Updating users passwords](updating-users-passwords.md) +- [Running `just` commands](just.md) -- [Maintenance / checking if services work](maintenance-checking-services.md) - -- [Maintenance / upgrading services](maintenance-upgrading-services.md) - -- [Maintenance / Synapse](maintenance-synapse.md) - -- [Maintenance / PostgreSQL](maintenance-postgres.md) - -- [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md) +- [Self-building](self-building.md) - [Uninstalling](uninstalling.md) + +- [Updating users passwords](updating-users-passwords.md) From 344c860250b289cf9281e8ea2f89f4bceab4229e Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 26 Nov 2024 10:23:27 +0200 Subject: [PATCH 013/952] borgmatic v1.9.3 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 6bf8ddff5..f891b8f0d 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.2-1 + version: v1.4.0-1.9.3-1 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From 352f2ac24da225b8b026cf0d7b524a1c4e89763e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 26 Nov 2024 01:34:24 +0900 Subject: [PATCH 014/952] Update README.md: edit "Getting started" section to introduce two installation guides Signed-off-by: Suguru Hirahara --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a55def0f7..65ffe14d2 100644 --- a/README.md +++ b/README.md @@ -25,9 +25,12 @@ We have detailed documentation in the [docs/](./docs) directory - see the Table While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend: - Starting with the basics. You can always add/remove or tweak services later on. -- Following our guided installation, starting with the [Prerequisites](./docs/prerequisites.md) documentation page -If you have never configured Matrix services, follow the [**quick start**](./docs/quick-start.md) guide to set up minimum core services on your server. +- Following our installation guide. There are two guides available for beginners and advanced users: + + - ⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with "opinionated defaults". + + - **Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](./docs/prerequisites.md)** documentation page. ## ✔ Supported services From 4a254ec6dd8f813fc77501dc9c578b292e6d9f8e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 26 Nov 2024 19:51:51 +0900 Subject: [PATCH 015/952] Remove links to "Quick start" from the breadcrumbs on full installation guide pages Add a anchor link to quick-start.md on docs/prerequisites.md Signed-off-by: Suguru Hirahara --- docs/configuring-dns.md | 2 +- docs/configuring-playbook.md | 2 +- docs/getting-the-playbook.md | 2 +- docs/installing.md | 2 +- docs/prerequisites.md | 4 +++- 5 files changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 2e2cd6bae..86d730f45 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -1,6 +1,6 @@ # Configuring your DNS settings -⚡️[Quick start](quick-start.md) | [Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) To set up Matrix on your domain, you'd need to do some DNS configuration. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index c2eef40b8..d1b9993ec 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -1,6 +1,6 @@ # Configuring the playbook -⚡️[Quick start](quick-start.md) | [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md) +[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md) If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory: diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index 07d5154f5..aba240b4c 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -1,6 +1,6 @@ # Getting the playbook -⚡️[Quick start](quick-start.md) | [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) This Ansible playbook is meant to be executed on your own computer (not the Matrix server). diff --git a/docs/installing.md b/docs/installing.md index 7ca37e584..391fe8590 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -1,6 +1,6 @@ # Installing -⚡️[Quick start](quick-start.md) | [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing +[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing If you've configured your DNS records and the playbook, you can start the installation procedure. diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 412cace93..6cbfc9a23 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -1,11 +1,13 @@ # Prerequisites -⚡️[Quick start](quick-start.md) | Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step. We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands. +**Note**: if you do not have an existing Matrix server and want to start quickly with "opinionated defaults", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide. + ## Your local computer - [Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible. From c4e81097e31a3426787296a93beddb1be2c9be50 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 26 Nov 2024 17:02:02 +0200 Subject: [PATCH 016/952] Upgrade Synapse (v1.119.0 -> v1.120.0) and enable authenticated media by default --- CHANGELOG.md | 19 +++++++++++++++++++ roles/custom/matrix-synapse/defaults/main.yml | 8 ++++---- 2 files changed, 23 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index cb71f39de..eb1140930 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,22 @@ +# 2024-11-26 + +## (Backward Compatibility Break) Synapse now defaults to enabling authenticated media + +**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues). + +The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default). + +Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago. + +Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default. + +We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing. + +Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know. + +You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook. + + # 2024-11-23 ## (Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index e8c0441e7..8435ff8c0 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.119.0 +matrix_synapse_version: v1.120.0 matrix_synapse_username: '' matrix_synapse_uid: '' @@ -1010,10 +1010,10 @@ matrix_synapse_workers_media_repository_workers_container_arguments: [] # Adjusting this value manually is generally not necessary. matrix_synapse_enable_media_repo: "{{ not matrix_synapse_ext_media_repo_enabled and (not matrix_synapse_workers_enabled or (matrix_synapse_workers_enabled_list | selectattr('type', 'equalto', 'media_repository') | list | length == 0)) }}" -# matrix_synapse_enable_authenticated_media controls if authenticated media is enabled. If enabled all "old" media remains accessible over the legacy endpoints but new media is blocked. +# matrix_synapse_enable_authenticated_media controls if authenticated media is enabled. +# If enabled all "old" media remains accessible over the legacy endpoints but new media is blocked. # while this option is enabled all media access and downloads have to be done via authenticated endpoints. -# FIX_ME_WHEN_DEFAULT_TRUE: This option is going to become set to default true in Synapse at a later date. -matrix_synapse_enable_authenticated_media: false +matrix_synapse_enable_authenticated_media: true # matrix_synapse_media_instance_running_background_jobs populates the `media_instance_running_background_jobs` Synapse configuration used when Synapse workers are in use (`matrix_synapse_workers_enabled`). # `media_instance_running_background_jobs` is meant to point to a single media-repository worker, which is dedicated to running background tasks that maintain the media repository. From 304c33594037dfddb1803f134f2d729b328b9169 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 27 Nov 2024 01:09:31 +0900 Subject: [PATCH 017/952] Update docs/faq.md: add links to quick-start.md (#3826) * Update docs/faq.md: add links to quick-start.md Signed-off-by: Suguru Hirahara * Update faq.md --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- docs/faq.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 4a7e459a5..799ce43ed 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -6,8 +6,7 @@ This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org We've only started this FAQ recently, so it's still somewhat empty. -Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to [Prerequisites](prerequisites.md) to get guided into installing Matrix. - +Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides. ## Introductory @@ -66,7 +65,8 @@ Normally, you'd first choose the [Matrix](https://matrix.org/) server software y There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it. Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually. -To get started with the playbook, start at the [Prerequisites](prerequisites.md) page. + +To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page). ### What is Ansible? How does it work? @@ -373,13 +373,19 @@ Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable a See [Installing](installing.md) to learn how to use Ansible to install Matrix services. -Of course, don't just jump straight to Installing. Rather, start at [Prerequisites](prerequisites.md) and get guided from there (into [setting up DNS](configuring-dns.md), [configuring the playbook](configuring-playbook.md), etc). +However, we recommend you to follow our installation guide, instead of jumping straight to installing. + +There are two guides available: + +- ⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with "opinionated defaults". + +- **Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page. ### I installed Synapse some other way. Can I migrate such a setup to the playbook? Yes, you can. -You generally need to do a playbook installation (start at the [Prerequisites](prerequisites.md) page), followed by importing your existing data into it. +You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server. This Ansible playbook guides you into installing a server for `example.com` (user identifiers are like this: `@user:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup - [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain) From d08f1dcaff4e902e27f7ff43a6f4bec0130449aa Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 27 Nov 2024 00:51:10 +0000 Subject: [PATCH 018/952] Update nginx Docker tag to v1.27.3 --- .../matrix-synapse-reverse-proxy-companion/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 3d9173bd3..fa3a6a4ac 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -13,7 +13,7 @@ matrix_synapse_reverse_proxy_companion_enabled: true # renovate: datasource=docker depName=nginx -matrix_synapse_reverse_proxy_companion_version: 1.27.2-alpine +matrix_synapse_reverse_proxy_companion_version: 1.27.3-alpine matrix_synapse_reverse_proxy_companion_base_path: "{{ matrix_synapse_base_path }}/reverse-proxy-companion" matrix_synapse_reverse_proxy_companion_confd_path: "{{ matrix_synapse_reverse_proxy_companion_base_path }}/conf.d" From a368af41e3cbc9840f42bb0b19e86097edcfa788 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 27 Nov 2024 06:43:22 +0000 Subject: [PATCH 019/952] Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2024.11.27 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index c2967cce5..915630600 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -6,7 +6,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2024.11.20 +matrix_alertmanager_receiver_version: 2024.11.27 matrix_alertmanager_receiver_scheme: https From ed90f680ee2e2af9d5553bd562c7b3967b721fc4 Mon Sep 17 00:00:00 2001 From: Aine <97398200+aine-etke@users.noreply.github.com> Date: Thu, 28 Nov 2024 08:22:53 +0200 Subject: [PATCH 020/952] synapse-admin v0.10.3-etke32 --- roles/custom/matrix-synapse-admin/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 4dc80e510..8617dbefa 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -14,7 +14,7 @@ matrix_synapse_admin_container_image_self_build: false matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git" # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin -matrix_synapse_admin_version: v0.10.3-etke31 +matrix_synapse_admin_version: v0.10.3-etke32 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}" matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}" From 85b00f298e856d3b9a9a1bfb9b069e237ccdf28c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 28 Nov 2024 18:13:24 +0900 Subject: [PATCH 021/952] Update docs/faq.md (#3829) * Update docs/faq.md: replace instruction about restoration procedure with the anchor link to installing.md Note the link to docs/maintenance-migrating.md is placed on the entry just above. Signed-off-by: Suguru Hirahara * Update docs/faq.md: update description related to installation on matrix.example.com Summary: - Copy a paragraph from docs/howto-server-delegation.md - Simplify instruction to install on matrix.example.com by removing repetitive description - Remove duplicated description about server delegation - Replace deprecated (or soon to be deprecated) services on configuration example for inventory/host_vars/matrix.example.com/vars.yml Signed-off-by: Suguru Hirahara * Update docs/faq.md: fix and simplify the answer to the reason why install your server at matrix.example.com Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/faq.md | 39 ++++++++++++++++----------------------- 1 file changed, 16 insertions(+), 23 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 799ce43ed..37b1fb14d 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -232,11 +232,7 @@ If your distro runs within an [LXC container](https://linuxcontainers.org/), you It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work. -Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. - -We allow `matrix.example.com` to be the Matrix server handling Matrix stuff for `example.com` by [Server Delegation](howto-server-delegation.md). During the installation procedure, we recommend that you set up server delegation using the [.well-known](configuring-well-known.md) method. - -If you'd really like to install Matrix services directly on the base domain, see [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain) +Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default. ### I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do? @@ -248,11 +244,7 @@ If you really can't obtain an HTTPS certificate for your base domain, you can ta ### How do I install on matrix.example.com without involving the base domain? -This Ansible playbook guides you into installing a server for `example.com` (user identifiers are like this: `@user:example.com`), while the server is at `matrix.example.com`. - -We allow `matrix.example.com` to be the Matrix server handling Matrix stuff for `example.com` by [Server Delegation](howto-server-delegation.md). During the installation procedure, we recommend that you set up server delegation using the [.well-known](configuring-well-known.md) method. - -If you're fine with uglier identifiers (`@user:matrix.example.com`, which is the equivalent of having an email address like `bob@mail.company.com`, instead of just `bob@company.com`), you can do that as well using the following configuration in your `vars.yml` file: +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml # This is what your identifiers are like (e.g. `@bob:matrix.example.com`). @@ -267,17 +259,20 @@ matrix_server_fqn_matrix: "matrix.example.com" # Feel free to use `element.matrix.example.com`, if you'd prefer that. matrix_server_fqn_element: "element.example.com" -# This is where you access Dimension (if enabled via `matrix_dimension_enabled: true`; NOT enabled by default). +# This is where you access Etherpad (if enabled via `etherpad_enabled: true`; NOT enabled by default). # -# Feel free to use `dimension.matrix.example.com`, if you'd prefer that. -matrix_server_fqn_dimension: "dimension.example.com" - -# This is where you access Jitsi (if enabled via `jitsi_enabled: true`; NOT enabled by default). -# -# Feel free to use `jitsi.matrix.example.com`, if you'd prefer that. -matrix_server_fqn_jitsi: "jitsi.example.com" +# Feel free to use `etherpad.matrix.example.com`, if you'd prefer that. +matrix_server_fqn_etherpad: "etherpad.example.com" ``` +After configuring the playbook, run the [installation](installing.md) command: + +``` +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +**Note**: without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user identifiers will be like `@user:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`. + ### I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services? If you don't use your base domain for anything, then it's hard for you to "serve files over HTTPS" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md)). @@ -462,12 +457,10 @@ We haven't documented this properly yet, but the general advice is to: - back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql)). -You can later restore these roughly like this: +You can later restore these by: -- restore the `/matrix` directory and files on the new server manually -- run the playbook again (see [Installing](installing.md)), but **don't** start services yet (**don't run** `... --tags=start`). This step will fix any file permission mismatches and will also set up additional software (Docker, etc.) and files on the server (systemd service, etc.). -- perform a Postgres database import (see [Importing Postgres](importing-postgres.md)) to restore your database backup -- start services (see [Finalize the installation](installing.md#finalize-the-installation)) +- Restoring the `/matrix` directory and files on the new server manually +- Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data) If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again. From cd1905f576a60c2473951294df1cd89df4fd3021 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 28 Nov 2024 18:33:56 +0900 Subject: [PATCH 022/952] Update triple backticks with syntax highlighting (#3832) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Triple backticks with syntax highlighting: yml → yaml Signed-off-by: Suguru Hirahara * Triple backticks with syntax highlighting: yaml and sh The strings "yml" were replaced with "yaml" as the latter is used more than the former. Signed-off-by: Suguru Hirahara * Triple backticks with syntax highlighting: INI Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: remove redundant white space characters after triple backticks Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- CHANGELOG.md | 26 +++++++++---------- docs/ansible.md | 6 ++--- ...figuring-playbook-alertmanager-receiver.md | 4 +-- ...uring-playbook-appservice-double-puppet.md | 2 +- ...ng-playbook-appservice-draupnir-for-all.md | 2 +- docs/configuring-playbook-backup-borg.md | 6 ++--- docs/configuring-playbook-bot-baibot.md | 16 ++++++------ docs/configuring-playbook-bot-chatgpt.md | 2 +- docs/configuring-playbook-bot-draupnir.md | 4 +-- docs/configuring-playbook-bot-go-neb.md | 4 +-- ...ng-playbook-bot-matrix-registration-bot.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 4 +-- ...ng-playbook-bridge-appservice-kakaotalk.md | 2 +- ...iguring-playbook-bridge-mautrix-discord.md | 2 +- ...guring-playbook-bridge-mautrix-facebook.md | 2 +- ...nfiguring-playbook-bridge-mautrix-slack.md | 2 +- ...iguring-playbook-bridge-mx-puppet-slack.md | 2 +- docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-federation.md | 2 +- docs/configuring-playbook-jitsi.md | 8 +++--- ...-playbook-matrix-authentication-service.md | 2 +- ...onfiguring-playbook-matrix-registration.md | 6 ++--- docs/configuring-playbook-ntfy.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- docs/configuring-playbook-rageshake.md | 2 +- docs/configuring-playbook-sygnal.md | 2 +- ...ing-playbook-synapse-auto-accept-invite.md | 2 +- ...guring-playbook-synapse-auto-compressor.md | 2 +- docs/configuring-playbook-synapse.md | 2 +- docs/configuring-playbook-turn.md | 2 +- ...ring-playbook-user-verification-service.md | 2 +- docs/faq.md | 2 +- docs/getting-the-playbook.md | 2 +- docs/importing-postgres.md | 2 +- docs/maintenance-and-troubleshooting.md | 4 +-- docs/maintenance-checking-services.md | 2 +- docs/maintenance-postgres.md | 2 +- docs/maintenance-synapse.md | 8 +++--- docs/obtaining-access-tokens.md | 2 +- docs/updating-users-passwords.md | 6 ++--- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 41 files changed, 79 insertions(+), 79 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index eb1140930..47e9d92bb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -174,7 +174,7 @@ If upstream synapse-admin picks up the pace and improves, the etke.cc fork may d If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file: -```yml +```yaml matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}awesometechnologies/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else matrix_container_global_registry_prefix }}" @@ -199,7 +199,7 @@ All non-deprecated mautrix bridges in the playbook have been reworked to support We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file: -```yml +```yaml matrix_appservice_double_puppet_enabled: true ``` @@ -231,7 +231,7 @@ This upgrade necessitates configuration policy changes as described in [matrix-c If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file: -```yml +```yaml matrix_corporal_version: 2.8.0 ``` @@ -287,7 +287,7 @@ Still, if HTTP/3 cannot function correctly in your setup, it's best to disable a To **disable HTTP/3**, you can use the following configuration: -```yml +```yaml traefik_config_entrypoint_web_secure_http3_enabled: false # Disabling HTTP/3 for the web-secure entrypoint (above), @@ -301,7 +301,7 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_ena If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it: -```yml +```yaml # Disable HTTP/3 for the federation entrypoint. # If you'd like HTTP/3, consider configuring it for your other reverse-proxy. # @@ -322,7 +322,7 @@ The playbook has just started making use of this feature. **From now on, your sy If you'd like **to go back to the old unrestricted behavior**, use the following configuration: -```yml +```yaml # Use this configuration to allow synapse-admin to manage any homeserver instance. matrix_synapse_admin_config_restrictBaseUrl: [] ``` @@ -387,7 +387,7 @@ Users on `arm32` should be aware that there's **neither a prebuilt `arm32` conta **The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file: -```yml +```yaml # Explicitly disable KeyDB, which will auto-enable Redis # if the playbook requires it as a dependency for its operation. keydb_enabled: false @@ -2800,7 +2800,7 @@ You can now customize the server name string that Riot-web displays in its login These playbook variables, with these default values, have been added: -``` +```yaml matrix_riot_web_default_server_name: "{{ matrix_domain }}" ``` @@ -2828,7 +2828,7 @@ Still, we might become affected in the future. In any case, it's imminent that S To avoid future problems, we recommend that you run the following command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=upgrade-postgres --extra-vars='{"postgres_force_upgrade": true}' ``` @@ -3289,7 +3289,7 @@ The certificates from the Matrix domain will be used for the Coturn server. This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse: -```bash +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-coturn,setup-synapse,start ``` @@ -3628,7 +3628,7 @@ The playbook now allows you to set the log levels used by Synapse. The default l You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels -``` +```yaml matrix_synapse_log_level: "INFO" matrix_synapse_storage_sql_log_level: "INFO" matrix_synapse_root_log_level: "INFO" @@ -3641,7 +3641,7 @@ matrix_synapse_root_log_level: "INFO" You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added: -``` +```yaml matrix_riot_web_disable_custom_urls: true matrix_riot_web_disable_guests: true matrix_riot_web_integrations_ui_url: "https://scalar.vector.im/" @@ -3652,7 +3652,7 @@ matrix_riot_web_integrations_jitsi_widget_url: "https://scalar.vector.im/api/wid This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file: -``` +```yaml matrix_riot_web_integrations_ui_url: "https://dimension.t2bot.io/riot" matrix_riot_web_integrations_rest_url: "https://dimension.t2bot.io/api/v1/scalar" matrix_riot_web_integrations_widgets_urls: "https://dimension.t2bot.io/widgets" diff --git a/docs/ansible.md b/docs/ansible.md index 7783c55be..95fb72dbd 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -55,7 +55,7 @@ Alternatively, you can leave your `inventory/hosts` as is and specify the connec Run this from the playbook's directory: -```bash +```sh docker run -it --rm \ --privileged \ --pid=host \ @@ -76,7 +76,7 @@ Finally, you can execute `ansible-playbook ...` (or `ansible-playbook --connecti Run this from the playbook's directory: -```bash +```sh docker run -it --rm \ -w /work \ -v `pwd`:/work \ @@ -99,7 +99,7 @@ Finally, you execute `ansible-playbook ...` commands as per normal now. If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`). To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it ...` command), run: -```bash +```sh apk add sshpass ``` Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command. diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index ab81eb7c0..9eca526bd 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -12,7 +12,7 @@ This service is meant to be used with an external [Alertmanager](https://prometh To enable matrix-alertmanager-receiver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -```yml +```yaml matrix_alertmanager_receiver_enabled: true # If you'd like to change the username for this bot, uncomment and adjust. Otherwise, remove. @@ -85,7 +85,7 @@ Then, you can proceed to [Usage](#usage). Configure your Prometheus Alertmanager with configuration like this: -```yml +```yaml receivers: - name: matrix webhook_configs: diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index 814f34b9a..b07662059 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -10,7 +10,7 @@ Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/ To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -```yml +```yaml matrix_appservice_double_puppet_enabled: true ``` diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 862bf3dd7..37b7f86d3 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -51,7 +51,7 @@ matrix_appservice_draupnir_for_all_master_control_room_alias: "ALIAS_FROM_STEP_2 After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index b0bcfe68b..a7902d8de 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -18,7 +18,7 @@ By default, if you're using the integrated Postgres database server (as opposed 2. Create a new SSH key: - ```bash + ```sh ssh-keygen -t ed25519 -N '' -f matrix-borg-backup -C matrix ``` @@ -28,7 +28,7 @@ By default, if you're using the integrated Postgres database server (as opposed If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over: - ```bash + ```sh # example to append the new PUBKEY contents, where: # PUBKEY is path to the public key, # USER is a ssh user on a provider / server @@ -73,7 +73,7 @@ Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansib After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 1c7aa419e..be21ab98a 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -84,7 +84,7 @@ If `matrix_admin` is already configured in your `vars.yml` configuration, you ca **If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -```yml +```yaml # Uncomment to add one or more admins to this bridge: # # matrix_bot_baibot_config_access_admin_patterns: @@ -113,7 +113,7 @@ Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is op **If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -```yml +```yaml # Uncomment and adjust the bot users if necessary: # # Subsequent changes to `matrix_bot_baibot_config_initial_global_config_user_patterns` do not affect the bot's behavior. @@ -146,7 +146,7 @@ You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot Here's an example **addition** to your `vars.yml` file: -```yml +```yaml matrix_bot_baibot_config_agents_static_definitions_anthropic_enabled: true matrix_bot_baibot_config_agents_static_definitions_anthropic_config_api_key: "YOUR_API_KEY_HERE" @@ -173,7 +173,7 @@ You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot Here's an example **addition** to your `vars.yml` file: -```yml +```yaml matrix_bot_baibot_config_agents_static_definitions_groq_enabled: true matrix_bot_baibot_config_agents_static_definitions_groq_config_api_key: "YOUR_API_KEY_HERE" @@ -207,7 +207,7 @@ You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot Here's an example **addition** to your `vars.yml` file: -```yml +```yaml matrix_bot_baibot_config_agents_static_definitions_mistral_enabled: true matrix_bot_baibot_config_agents_static_definitions_mistral_config_api_key: "YOUR_API_KEY_HERE" @@ -238,7 +238,7 @@ The OpenAI provider is **only meant to be used with OpenAI's official API** and Here's an example **addition** to your `vars.yml` file: -```yml +```yaml matrix_bot_baibot_config_agents_static_definitions_openai_enabled: true matrix_bot_baibot_config_agents_static_definitions_openai_config_api_key: "YOUR_API_KEY_HERE" @@ -282,7 +282,7 @@ You can also define providers at runtime, by chatting with the bot, so using Ans Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**: -```yml +```yaml matrix_bot_baibot_config_agents_static_definitions_custom: # This agent will use the GPT 3.5 model and will only support text-generation, # even though the `openai` provider could support other features (e.g. image-generation). @@ -356,7 +356,7 @@ You can configure the **initial values** for these via Ansible, via the `matrix_ Example **additional** `vars.yml` configuration: -```yml +```yaml # Note: these are initial defaults for the bot's global configuration. # As such, changing any of these values subsequently has no effect on the bot's behavior. # Once initially configured, the global configuration is managed via bot commands, not via Ansible. diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 26973d43e..c1cc9ea3b 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -16,7 +16,7 @@ Choose a strong password for the bot. You can generate a good password with a co You can use the playbook to [register a new user](registering-users.md): -``` +```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 77d93f589..b3427f1b0 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -19,7 +19,7 @@ Choose a strong password for the bot. You can generate a good password with a co You can use the playbook to [register a new user](registering-users.md): -``` +```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` @@ -117,7 +117,7 @@ That is all you need to do due to that Draupnir can complete migration on its ow After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 1b21897ac..359aa7fe5 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -19,7 +19,7 @@ Choose a strong password for the bot. You can generate a good password with a co You can use the playbook to [register a new user](registering-users.md): -``` +```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` @@ -221,7 +221,7 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 6583a92e0..2d6c55711 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -46,6 +46,6 @@ If you have any questions, or if you need help setting it up, read the [troublsh To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc... you can use: -```bash +```sh just run-tags bot-matrix-registration-bot-clean-cache ``` diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index f4ccca11c..664a0a4ae 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -15,7 +15,7 @@ Choose a strong password for the bot. You can generate a good password with a co You can use the playbook to [register a new user](registering-users.md): -``` +```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` @@ -119,7 +119,7 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 1e9816b41..88f8bfbd1 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -21,7 +21,7 @@ You may optionally wish to add some [Additional configuration](#additional-confi After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index ee736cda0..be5eb3969 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -29,7 +29,7 @@ You may optionally wish to add some [Additional configuration](#additional-confi After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 9b881b1d8..0741d9f6e 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -97,7 +97,7 @@ The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs Example command for proxying your traffic through the Matrix server: -``` +```sh sshuttle -r root@matrix.example.com:22 0/0 ``` diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 9b5aab6de..9065ec0b4 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -32,7 +32,7 @@ You may optionally wish to add some [Additional configuration](#additional-confi After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index 18a8dff69..5372f73f6 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -25,7 +25,7 @@ matrix_mx_puppet_slack_oauth_client_secret: "" After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 06abd3097..9f6e358c2 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -71,7 +71,7 @@ By default, you will need to create a CNAME record for `dimension`. See [Configu After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index e187fa363..3a6c18ad9 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -57,7 +57,7 @@ Why? This change could be useful for people running small Synapse instances on s The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other: -``` +```yaml matrix_synapse_http_listener_resource_names: ["client","federation"] # Any port can be used but in this case we use 443 matrix_federation_public_port: 443 diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 55f647d90..623368b54 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -172,18 +172,18 @@ By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-vid There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start` For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example: -``` +```INI [jitsi_jvb_servers] ansible_host= ``` Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example: -``` yaml +```yaml jitsi_jvb_server_id: 'jvb-2' ``` -``` INI +```INI [jitsi_jvb_servers] jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2 jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2 @@ -271,7 +271,7 @@ jitsi_disable_gravatar: false After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index c94a250d9..fc79b7044 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -364,7 +364,7 @@ The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the M To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -```yml +```yaml # Adjust the mapping below to match your provider IDs on the Synapse side and the MAS side. # Don't forget that Synapse automatically adds an `oidc-` prefix to provider ids defined in its configuration. matrix_authentication_service_syn2mas_process_extra_arguments: diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index edc529eda..670562e34 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -54,7 +54,7 @@ If you've decided to use the default hostname, you won't need to do any extra DN After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` @@ -72,7 +72,7 @@ We make the most common APIs easy to use via the playbook (see below). To **create a new user registration token (link)**, use this command: -```bash +```sh ansible-playbook -i inventory/hosts setup.yml \ --tags=generate-matrix-registration-token \ --extra-vars="one_time=yes ex_date=2021-12-31" @@ -87,7 +87,7 @@ Share the unique registration link (generated by the command above) with users t To **list the existing user registration tokens**, use this command: -```bash +```sh ansible-playbook -i inventory/hosts setup.yml \ --tags=list-matrix-registration-tokens ``` diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index abd10feed..93db3c0f5 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -52,7 +52,7 @@ By default, you will need to create a CNAME record for `ntfy`. See [Configuring After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 109cf8c20..b05dddca1 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -31,6 +31,6 @@ Refer to the table below for additional configuration variables and their defaul After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index 538e86928..abc679d3f 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -53,7 +53,7 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 28f50b78f..004b9f9dc 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -79,7 +79,7 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-synapse-auto-accept-invite.md b/docs/configuring-playbook-synapse-auto-accept-invite.md index d315f6410..33e9268c2 100644 --- a/docs/configuring-playbook-synapse-auto-accept-invite.md +++ b/docs/configuring-playbook-synapse-auto-accept-invite.md @@ -34,7 +34,7 @@ Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.1 Here's example configuration for using the **native** Synapse feature: -```yml +```yaml matrix_synapse_auto_accept_invites_enabled: true # Default settings below. Uncomment and adjust this part if necessary. diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 3e1cda4bc..3a3a310d2 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -20,7 +20,7 @@ matrix_synapse_auto_compressor_enabled: true After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index a529d3e34..b9291c3b9 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -98,7 +98,7 @@ For more detailed documentation on available options and how to setup keycloak, In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ; -```yml +```yaml matrix_synapse_oidc_enabled: true matrix_synapse_oidc_providers: diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index b52b54691..6bd0a8ad7 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -40,7 +40,7 @@ The playbook uses the [`auth-secret` authentication method](https://github.com/c To do so, add this override to your configuration: -```yml +```yaml matrix_coturn_authentication_method: lt-cred-mech ``` diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index e0566c86b..0664ae826 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -92,7 +92,7 @@ This will instruct UVS to verify the OpenID token against any domain given in a After these variables have been set, run the [installation](installing.md) command to restart UVS: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-user-verification-service,start ``` diff --git a/docs/faq.md b/docs/faq.md index 37b1fb14d..74db0e8b9 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -267,7 +267,7 @@ matrix_server_fqn_etherpad: "etherpad.example.com" After configuring the playbook, run the [installation](installing.md) command: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index aba240b4c..3ae14a705 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -19,7 +19,7 @@ We recommend using the [git](https://git-scm.com/) tool to get the playbook's so Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code: -```bash +```sh git clone https://github.com/spantaleev/matrix-docker-ansible-deploy.git ``` diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index 762900c64..cdba3f743 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -94,7 +94,7 @@ Once the database is clear and the ownership of the tables has been fixed in the Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal) -``` +```sh /usr/bin/env docker run --rm --name matrix-postgres-import --log-driver=none --user=998:1001 --cap-drop=ALL --network=matrix --env-file=/matrix/postgres/env-postgres-psql --mount type=bind,src=/migration/synapse_dump.sql,dst=/synapse_dump.sql,ro --entrypoint=/bin/sh docker.io/postgres:15.0-alpine -c "cat /synapse_dump.sql | grep -vE '^(CREATE|ALTER) ROLE (matrix)(;| WITH)' | grep -vE '^CREATE DATABASE (matrix)\s' | psql -v ON_ERROR_STOP=1 -h matrix-postgres --dbname=synapse" ``` diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index e16b75977..c8803c844 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -3,7 +3,7 @@ ## How to see the current status of your services You can check the status of your services by using `systemctl status`. Example: -``` +```sh sudo systemctl status matrix-synapse ● matrix-synapse.service - Synapse server @@ -41,7 +41,7 @@ Re-run the playbook after making these configuration changes. ## Remove unused Docker data You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information. -```bash +```sh ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune ``` diff --git a/docs/maintenance-checking-services.md b/docs/maintenance-checking-services.md index 457cd0f47..e6975b9d1 100644 --- a/docs/maintenance-checking-services.md +++ b/docs/maintenance-checking-services.md @@ -4,7 +4,7 @@ This playbook can perform a check to ensure that you've configured things correc To perform the check, run: -```bash +```sh ansible-playbook -i inventory/hosts setup.yml --tags=self-check ``` diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index deac1faa7..9960e7e90 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -57,7 +57,7 @@ To automatically make Postgres database backups on a fixed schedule, see [Settin To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server: -```bash +```sh /usr/bin/docker exec \ --env-file=/matrix/postgres/env-postgres-psql \ matrix-postgres \ diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index a7220f5b8..fdf2856d7 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -35,7 +35,7 @@ After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintena To ask the playbook to run rust-synapse-compress-state, execute: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --tags=rust-synapse-compress-state ``` @@ -52,14 +52,14 @@ Editing the database manually is not recommended or supported by the Synapse dev First, set up an SSH tunnel to your Matrix server (skip if it is your local machine): -``` +```sh # you may replace 1799 with an arbitrary port unbound on both machines ssh -L 1799:localhost:1799 matrix.example.com ``` Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container: -``` +```sh docker run --rm --publish 1799:8080 --link matrix-postgres --net matrix adminer ``` @@ -93,7 +93,7 @@ You can **learn more about cache-autotuning and the global cache factor settings To **disable cache auto-tuning**, unset all values: -```yml +```yaml matrix_synapse_cache_autotuning_max_cache_memory_usage: '' matrix_synapse_cache_autotuning_target_cache_memory_usage: '' matrix_synapse_cache_autotuning_min_cache_ttl: '' diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index ba9381a82..12016cb96 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -25,7 +25,7 @@ Below, we describe 2 ways to generate an access token for a user - using [Elemen You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login): -``` +```sh curl -XPOST -d '{ "identifier": { "type": "m.id.user", "user": "USERNAME" }, "password": "PASSWORD", diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index 6461e1198..71cd3afe9 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -8,7 +8,7 @@ You can reset a user's password via the Ansible playbook: -``` +```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HERE password=PASSWORD_HERE' --tags=update-user-password ``` @@ -19,7 +19,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HE You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation): -``` +```sh docker exec -it matrix-synapse /usr/local/bin/hash_password -c /data/homeserver.yaml ``` @@ -42,6 +42,6 @@ If you didn't make your account a server admin when you created it, you can lear ### Example: To set @user:example.com's password to `correct_horse_battery_staple` you could use this curl command: -``` +```sh curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@user:example.com?access_token=MDA...this_is_my_access_token ``` diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 8435ff8c0..7896886b0 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -56,7 +56,7 @@ matrix_synapse_container_image_customizations_auto_accept_invite_installation_en # # Example usage: # -# ```yml +# ```yaml # matrix_synapse_container_image_customizations_templates_enabled: true # # The templates are expected to be in a `templates/` subdirectory in # matrix_synapse_container_image_customizations_templates_in_container_template_files_relative_path: templates/ From f19f3bea2d83957dac90bd2bc7f1149213bd2c95 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 28 Nov 2024 11:36:16 +0200 Subject: [PATCH 023/952] Progress a bit on self-building for Schildichat This is related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3831 It: - adds some missing variables - version variable to branch variable conversion While it improves the situation, it still doesn't result in a working self-building feature, because: - cloning a repository containing submodules requires special care, as described here (https://github.com/SchildiChat/schildichat-desktop/blob/c03ef20e5dc0a88cec479c9711d9941aba48ab97/README.md#initial-build-setup) - we likely better clone a specific repository version from the very beginning, instead of trying to change subsequently (and having to re-initilize submodules) though that's very different than what we're doing elsewhere and is likely very wasteful - we can't just build a `Dockerfile`, we need to invoke `make setup` (`./setup.sh`) - it's likely that the `docker-src` directory is not reusable across versions or may require special handling to clean up files, etc. --- .../defaults/main.yml | 8 ++- .../tasks/setup_install.yml | 68 +++++++++---------- 2 files changed, 41 insertions(+), 35 deletions(-) diff --git a/roles/custom/matrix-client-schildichat/defaults/main.yml b/roles/custom/matrix-client-schildichat/defaults/main.yml index bd7ab05d8..22d71f29e 100644 --- a/roles/custom/matrix-client-schildichat/defaults/main.yml +++ b/roles/custom/matrix-client-schildichat/defaults/main.yml @@ -4,6 +4,12 @@ matrix_client_schildichat_enabled: true matrix_client_schildichat_container_image_self_build: false +matrix_client_schildichat_container_image_self_build_repo: "https://github.com/SchildiChat/schildichat-desktop.git" +matrix_client_schildichat_container_image_self_build_version: "{{ 'lite' if matrix_client_schildichat_version == 'latest' else ('v' + matrix_client_schildichat_version) }}" +# Controls whether to patch webpack.config.js when self-building, so that building can pass on low-memory systems (< 4 GB RAM): +# - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357 +# - https://github.com/element-hq/element-web/issues/19544 +matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=ghcr.io/etkecc/schildichat-web matrix_client_schildichat_version: 1.11.36-sc.3 @@ -12,7 +18,7 @@ matrix_client_schildichat_docker_image_name_prefix: "{{ 'localhost/' if matrix_c matrix_client_schildichat_docker_image_force_pull: "{{ matrix_client_schildichat_docker_image.endswith(':latest') }}" matrix_client_schildichat_data_path: "{{ matrix_base_data_path }}/client-schildichat" -matrix_client_schildichat_docker_src_files_path: "{{ matrix_client_schildichat_data_path }}/docker-src" +matrix_client_schildichat_container_src_files_path: "{{ matrix_client_schildichat_data_path }}/docker-src" # The base container network matrix_client_schildichat_container_network: '' diff --git a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml index 6dc9222c4..b27f5bc48 100644 --- a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml +++ b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml @@ -9,10 +9,10 @@ group: "{{ matrix_user_groupname }}" with_items: - {path: "{{ matrix_client_schildichat_data_path }}", when: true} - - {path: "{{ matrix_client_schildichat_docker_src_files_path }}", when: "{{ matrix_client_schildichat_container_image_self_build }}"} + - {path: "{{ matrix_client_schildichat_container_src_files_path }}", when: "{{ matrix_client_schildichat_container_image_self_build }}"} when: "item.when | bool" -- name: Ensure SchildiChat Web Docker image is pulled +- name: Ensure SchildiChat Web container image is pulled community.docker.docker_image: name: "{{ matrix_client_schildichat_docker_image }}" source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" @@ -24,40 +24,40 @@ delay: "{{ devture_playbook_help_container_retries_delay }}" until: result is not failed -- name: Ensure SchildiChat Web repository is present on self-build - ansible.builtin.git: - repo: "{{ matrix_client_schildichat_container_image_self_build_repo }}" - dest: "{{ matrix_client_schildichat_docker_src_files_path }}" - version: "{{ matrix_client_schildichat_docker_image.split(':')[1] }}" - force: "yes" - become: true - become_user: "{{ matrix_user_username }}" - register: matrix_client_schildichat_git_pull_results - when: "matrix_client_schildichat_container_image_self_build | bool" +- when: "matrix_client_schildichat_container_image_self_build | bool" + block: + - name: Ensure SchildiChat Web repository is present on self-build + ansible.builtin.git: + repo: "{{ matrix_client_schildichat_container_image_self_build_repo }}" + dest: "{{ matrix_client_schildichat_container_src_files_path }}" + version: "{{ matrix_client_schildichat_container_image_self_build_version }}" + force: "yes" + become: true + become_user: "{{ matrix_user_username }}" + register: matrix_client_schildichat_git_pull_results -# See: -# - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357 -# - https://github.com/vector-im/schildichat-web/issues/19544 -- # Update (2023-12-15): 404 -- name: Patch webpack.config.js to support building on low-memory (<4G RAM) devices - ansible.builtin.lineinfile: - path: "{{ matrix_client_schildichat_docker_src_files_path }}/webpack.config.js" - regexp: '(\s+)splitChunks: \{' - line: '\1splitChunks: { maxSize: 100000,' - backrefs: true - owner: root - group: root - mode: '0644' - when: "matrix_client_schildichat_container_image_self_build | bool and matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled | bool" + # See: + # - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357 + # - https://github.com/vector-im/schildichat-web/issues/19544 -- # Update (2023-12-15): 404 + - name: Patch webpack.config.js to support building on low-memory (<4G RAM) devices + ansible.builtin.lineinfile: + path: "{{ matrix_client_schildichat_container_src_files_path }}/element-web/webpack.config.js" + regexp: '(\s+)splitChunks: \{' + line: '\1splitChunks: { maxSize: 100000,' + backrefs: true + owner: root + group: root + mode: '0644' + when: "matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled | bool" -- name: Ensure SchildiChat Web Docker image is built - ansible.builtin.command: - cmd: |- - {{ devture_systemd_docker_base_host_command_docker }} buildx build - --tag={{ matrix_client_schildichat_docker_image }} - --file={{ matrix_client_schildichat_docker_src_files_path }}/Dockerfile - {{ matrix_client_schildichat_docker_src_files_path }} - changed_when: true - when: matrix_client_schildichat_container_image_self_build | bool + - name: Ensure SchildiChat Web container image is built + ansible.builtin.command: + cmd: |- + {{ devture_systemd_docker_base_host_command_docker }} buildx build + --tag={{ matrix_client_schildichat_docker_image }} + --file={{ matrix_client_schildichat_container_src_files_path }}/Dockerfile + {{ matrix_client_schildichat_container_src_files_path }} + changed_when: true - name: Ensure SchildiChat Web configuration installed ansible.builtin.copy: From 8a18cc946d2114a1dd9c890428402092d0b556bf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 28 Nov 2024 20:53:11 +0900 Subject: [PATCH 024/952] Replace "@user1" with "@alice" and "@user2" with "@bob" (#3833) * Replace "@user1" with "@alice" Signed-off-by: Suguru Hirahara * Replace "@user2" with "@bob" Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 4 ++-- roles/custom/matrix-dimension/defaults/main.yml | 2 +- .../matrix-synapse/templates/synapse/homeserver.yaml.j2 | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 9f6e358c2..87365f26c 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -20,8 +20,8 @@ These users can modify the integrations this Dimension supports. Add this to you ```yaml matrix_dimension_admins: - - "@user1:{{ matrix_domain }}" - - "@user2:{{ matrix_domain }}" + - "@alice:{{ matrix_domain }}" + - "@bob:{{ matrix_domain }}" ``` 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. diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml index 1a19e9452..136d9b9ec 100644 --- a/roles/custom/matrix-dimension/defaults/main.yml +++ b/roles/custom/matrix-dimension/defaults/main.yml @@ -16,7 +16,7 @@ matrix_dimension_path_prefix: / # For information on how to acquire an access token, visit https://t2bot.io/docs/access_tokens matrix_dimension_access_token: "" -# Users in form: ['@user1:example.com', '@user2:example.com'] +# Users in form: ['@alice:example.com', '@bob:example.com'] matrix_dimension_admins: [] # Whether to allow Dimension widgets serve websites with invalid or self signed SSL certificates diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 index a5d578bc2..6ec45abdf 100644 --- a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 @@ -2846,8 +2846,8 @@ opentracing: # By default, the list is empty. # #force_tracing_for_users: - # - "@user1:server_name" - # - "@user2:server_name" + # - "@alice:server_name" + # - "@bob:server_name" # Jaeger can be configured to sample traces at different rates. # All configuration options provided by Jaeger can be set here. From 687627ccd74e2ab094b4d75a690a98ed916ad1d2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 27 Nov 2024 11:32:04 +0900 Subject: [PATCH 025/952] Use "alice" as placeholder username instead of "john" "alice" is normally used in combination with "bob", though. Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- docs/installing.md | 4 ++-- docs/just.md | 24 +++++++++---------- docs/quick-start.md | 4 ++-- docs/registering-users.md | 12 +++++----- docs/updating-users-passwords.md | 2 +- .../custom/matrix-user-creator/vars/main.yml | 2 +- 7 files changed, 25 insertions(+), 25 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 47e9d92bb..24663068f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1354,7 +1354,7 @@ Our [justfile](justfile) already defines some additional helpful **shortcut** co - `just run-tags install-mautrix-slack,start` - to run specific playbook tags - `just start-all` - (re-)starts all services - `just stop-group postgres` - to stop only the Postgres service -- `just register-user john secret-password yes` - registers a `john` user with the `secret-password` password and admin access (admin = `yes`) +- `just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`) Additional helpful commands and shortcuts may be defined in the future. diff --git a/docs/installing.md b/docs/installing.md index 391fe8590..a839c07b7 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -83,13 +83,13 @@ To create your user account (as an administrator of the server) via this Ansible **Notes**: - Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE` -- For `YOUR_USERNAME_HERE`, use a plain username like `john`, not your full identifier (`@user:example.com`) +- For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full identifier (`@alice:example.com`) - Use `admin=yes` to make your user account an administrator of the Matrix server ```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=YOUR_USERNAME_HERE password=YOUR_PASSWORD_HERE admin=yes' --tags=register-user -# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=john password=secret-password admin=yes' --tags=register-user +# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user ``` 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`. diff --git a/docs/just.md b/docs/just.md index d47ae00f3..ecc09e495 100644 --- a/docs/just.md +++ b/docs/just.md @@ -10,18 +10,18 @@ For some recipes such as `just update`, our `justfile` recommends installing [`a Here are some examples of shortcuts: -| Shortcut | Result | -|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------| -| `just roles` | Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml) | -| `just update` | Run `git pull` (to update the playbook) and install the Ansible roles | -| `just install-all` | Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` | -| `just setup-all` | Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start` | -| `just install-all --ask-vault-pass` | Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command) | -| `just run-tags install-mautrix-slack,start` | Run specific playbook tags (here `install-mautrix-slack` and `start`) | -| `just install-service mautrix-slack` | Run `just run-tags install-mautrix-slack,start` with even less typing | -| `just start-all` | (Re-)starts all services | -| `just stop-group postgres` | Stop only the Postgres service | -| `just register-user john secret-password yes` | Registers a `john` user with the `secret-password` password and admin access (admin = `yes`) | +| Shortcut | Result | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| `just roles` | Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml) | +| `just update` | Run `git pull` (to update the playbook) and install the Ansible roles | +| `just install-all` | Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` | +| `just setup-all` | Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start` | +| `just install-all --ask-vault-pass` | Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command) | +| `just run-tags install-mautrix-slack,start` | Run specific playbook tags (here `install-mautrix-slack` and `start`) | +| `just install-service mautrix-slack` | Run `just run-tags install-mautrix-slack,start` with even less typing | +| `just start-all` | (Re-)starts all services | +| `just stop-group postgres` | Stop only the Postgres service | +| `just register-user alice secret-password yes` | Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`) | While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`. diff --git a/docs/quick-start.md b/docs/quick-start.md index 6100c82dc..b08af6514 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -136,12 +136,12 @@ To create your user account (as an administrator of the server) via this Ansible **💡 Notes**: - Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE` -- For `YOUR_USERNAME_HERE`, use a plain username like `john`, not your full identifier (`@user:example.com`) +- For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full identifier (`@alice:example.com`) ```sh ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=YOUR_USERNAME_HERE password=YOUR_PASSWORD_HERE admin=yes' --tags=register-user -# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=john password=secret-password admin=yes' --tags=register-user +# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user ``` +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index b07662059..e4a3b3922 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -16,7 +16,20 @@ matrix_appservice_double_puppet_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 37b7f86d3..be13c93a3 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -49,12 +49,20 @@ matrix_appservice_draupnir_for_all_master_control_room_alias: "ALIAS_FROM_STEP_2 ### 4. Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index a7902d8de..07fc3080f 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -71,12 +71,17 @@ Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansib ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Manually start a backup For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index be21ab98a..423fcf16b 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -376,18 +376,22 @@ matrix_bot_baibot_config_initial_global_config_handler_image_generation: null ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -just run-tags install-all,ensure-matrix-users-created,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` **Notes**: -- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- if you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index d918f79ee..c1c00ecbe 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -56,18 +56,22 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` **Notes**: -- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- if you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index c1cc9ea3b..e892f2ea2 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -56,12 +56,20 @@ You will need to get tokens for ChatGPT. ## 4. Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index b3427f1b0..7f34158d8 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -115,12 +115,22 @@ That is all you need to do due to that Draupnir can complete migration on its ow ## 6. Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 359aa7fe5..42cbcdc98 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -219,12 +219,20 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index 982c7ca0a..bf210dc02 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -48,18 +48,22 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` **Notes**: -- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- if you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 2d6c55711..ef846f33f 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -32,7 +32,22 @@ The bot account will be created automatically. ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index 2bce34765..8142ac34f 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -27,18 +27,22 @@ matrix_bot_matrix_reminder_bot_reminders_timezone: Europe/London ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` **Notes**: -- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- if you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 05320d7bb..45b76f47a 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -49,11 +49,22 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` **Notes**: -- if you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 664a0a4ae..7d1be0404 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -117,12 +117,22 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] ## 7. Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 7f5ee714b..760782da2 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -30,12 +30,21 @@ matrix_appservice_discord_bot_token: "YOUR DISCORD APP BOT TOKEN" ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Self-Service Bridging (Manual) Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bridge-appservice-irc.md b/docs/configuring-playbook-bridge-appservice-irc.md index 84c3b4dd4..cbd995e32 100644 --- a/docs/configuring-playbook-bridge-appservice-irc.md +++ b/docs/configuring-playbook-bridge-appservice-irc.md @@ -62,7 +62,20 @@ matrix_appservice_irc_ircService_servers: ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 363f74709..4a85b2aed 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -33,12 +33,21 @@ Take a look at: ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage Start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index 1635ef77d..85196e189 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -65,12 +65,21 @@ Other configuration options are available via the `matrix_appservice_slack_confi ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage Send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room. diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index aea9f7f8a..a937e0583 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -26,12 +26,21 @@ matrix_appservice_webhooks_api_secret: '' ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage Invite the bridge bot user to your room in either way. diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 67133e50d..58fd43640 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -35,7 +35,20 @@ You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/co ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index 2370f5fa4..03b20989d 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -14,7 +14,20 @@ matrix_go_skype_bridge_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index 34dc627a4..96b7ca2f2 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -49,7 +49,20 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index 6ac1e686a..25103d753 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -33,7 +33,20 @@ matrix_sms_bridge_provider_android_truststore_password: 123 ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 4938a975e..0f72110bb 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -42,12 +42,21 @@ Take a look at: ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage ### Logging in diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 77bc5447d..8e41db1c6 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -55,7 +55,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/c ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index 00984faf5..c26b6e57e 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -20,7 +20,20 @@ matrix_mautrix_gmessages_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 0569276b6..4c368f2b9 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -20,7 +20,20 @@ matrix_mautrix_googlechat_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index 26177adf0..fb64ed097 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -22,7 +22,20 @@ matrix_mautrix_hangouts_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index b9130faf0..25a7b7d8b 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -42,7 +42,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/ ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index cb39b400d..cd70a8c42 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -68,7 +68,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templ ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index ab788408c..7883ebc9d 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -82,7 +82,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templ ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index 3b486d171..561bfac2a 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -68,7 +68,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/con ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 1653dd816..175202644 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -44,12 +44,21 @@ Take a look at: ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage 1. Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index 7c1426ff8..7b7d73182 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -22,7 +22,20 @@ matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index 5f7480cc8..6bde13c5a 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -22,7 +22,20 @@ matrix_mautrix_twitter_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index e2f73918f..35adeb85c 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -36,7 +36,20 @@ If you want to activate the relay bot in a room, send `!wa set-relay`. To deacti ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index cb0a9280a..ff9ff6246 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -41,7 +41,20 @@ By default, you will need to create a CNAME record for `wsproxy`. See [Configuri ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index c4958d4c4..3ab1b2ccf 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -18,7 +18,20 @@ matrix_mx_puppet_discord_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md index 424aa8855..ee0cf065a 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md +++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md @@ -14,7 +14,20 @@ matrix_mx_puppet_groupme_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md index 54bd0b011..3368dd579 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md +++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md @@ -14,7 +14,20 @@ matrix_mx_puppet_instagram_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index 5372f73f6..4cb19d1b6 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -23,12 +23,21 @@ matrix_mx_puppet_slack_oauth_client_secret: "" ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage Once the bot is enabled you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md index 08a52bd18..56e37f714 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-steam.md +++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md @@ -14,7 +14,20 @@ matrix_mx_puppet_steam_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md index c84c63e54..11024cf82 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md +++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md @@ -25,7 +25,20 @@ matrix_mx_puppet_twitter_environment: '' ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 799c0fd65..d7e96d1d7 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -49,18 +49,22 @@ You will also need to add several DNS records so that Postmoogle can send emails ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` **Notes**: -- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot. -- if you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password. ## Usage diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index 8e57062e5..5663904a1 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -14,7 +14,20 @@ matrix_wechat_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 0607e288e..6a3dd3f8d 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -63,7 +63,20 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 64ede1606..513cc7f6a 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -42,4 +42,13 @@ If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your ## Installing -After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 35706e4d5..f410459e3 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -71,4 +71,13 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index 1715c9804..600fc3b95 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -39,4 +39,13 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 0f5e6632c..780ac0829 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -69,4 +69,13 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 0ffa8ed04..31d43c0e2 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -34,4 +34,13 @@ Alternatively, **if there is no pre-defined variable** for a Dendrite setting yo ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 87365f26c..80645bcef 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -69,14 +69,20 @@ By default, you will need to create a CNAME record for `dimension`. See [Configu ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots. +**Notes**: +- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + + `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots. ## Jitsi domain diff --git a/docs/configuring-playbook-dynamic-dns.md b/docs/configuring-playbook-dynamic-dns.md index efabb75b9..e610f3b5f 100644 --- a/docs/configuring-playbook-dynamic-dns.md +++ b/docs/configuring-playbook-dynamic-dns.md @@ -25,7 +25,16 @@ matrix_dynamic_dns_domain_configurations: ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Additional Reading diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index ab274afe4..5b0bcd4fa 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -83,6 +83,16 @@ Refer to the official documentation [here](https://github.com/devture/email2matr ## Installing -To enable Email2Matrix, run the [installation](installing.md) command (`--tags=setup-email2matrix,start`). +To enable Email2Matrix, run the playbook with [playbook tags](playbook-tags.md) as below: -After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected. +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-email2matrix,start +``` + +**Notes**: + +- The shortcut commands with `just` program are also available: `just run-tags setup-email2matrix,start` or `just run-tags setup-all,start` + + `just run-tags setup-email2matrix,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected. diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 6bdc4a382..50ca562ed 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -44,7 +44,22 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`). + +- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + + `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password. ## Usage diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 623368b54..9ea3fb9e6 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -269,12 +269,17 @@ jitsi_disable_gravatar: false ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Usage You can use the self-hosted Jitsi server in multiple ways: diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index adebb4abd..42408aaed 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -131,7 +131,16 @@ matrix_ma1sd_configuration_extension_yaml: | ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Troubleshooting diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index fc79b7044..276c334fc 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -288,9 +288,20 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the [installation](installing.md) command: `just install-all` +Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below: -If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide. + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +**Notes**: + +- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + + `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide. 💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly). diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index bb72dbb72..3127ea701 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -116,8 +116,16 @@ To learn more about what the policy configuration, see the matrix-corporal docum ## Installing -After configuring the playbook, run the [installation](installing.md) command (`--tags=setup-all,start` or `--tags=setup-aux-files,setup-corporal,start`). +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just run-tags setup-all,start` + +`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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Matrix Corporal files diff --git a/docs/configuring-playbook-matrix-ldap-registration-proxy.md b/docs/configuring-playbook-matrix-ldap-registration-proxy.md index 828dee04a..02b04edf9 100644 --- a/docs/configuring-playbook-matrix-ldap-registration-proxy.md +++ b/docs/configuring-playbook-matrix-ldap-registration-proxy.md @@ -34,4 +34,13 @@ matrix_ldap_registration_proxy_systemd_wanted_services_list_custom: ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 670562e34..3308d273e 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -52,12 +52,16 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage @@ -91,3 +95,5 @@ To **list the existing user registration tokens**, use this command: ansible-playbook -i inventory/hosts setup.yml \ --tags=list-matrix-registration-tokens ``` + +The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens` diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md index 87482e039..99b9974d7 100644 --- a/docs/configuring-playbook-mautrix-bridges.md +++ b/docs/configuring-playbook-mautrix-bridges.md @@ -93,7 +93,20 @@ You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/template ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` + + `just install-all` 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. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Set up Double Puppeting diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index 93db3c0f5..dab016207 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -50,12 +50,16 @@ By default, you will need to create a CNAME record for `ntfy`. See [Configuring ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index 91bc9a0d9..5b0478a92 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -18,4 +18,13 @@ The default configuration should suffice. For advanced configuration, you can ov ## 2. Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index b05dddca1..9d3967cbc 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -29,8 +29,13 @@ Refer to the table below for additional configuration variables and their defaul ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 440b9f224..ae9ec582b 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -55,7 +55,16 @@ By default, you will need to create a CNAME record for `stats`. See [Configuring ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## What does it do? diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index e6ed3043a..c3c6081dd 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -22,7 +22,16 @@ matrix_prometheus_nginxlog_exporter_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Docker Image Compatibility diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md index f24bc0818..7d71b1c33 100644 --- a/docs/configuring-playbook-prometheus-postgres.md +++ b/docs/configuring-playbook-prometheus-postgres.md @@ -12,7 +12,16 @@ prometheus_postgres_exporter_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## What does it do? diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index abc679d3f..b74eaeefd 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -51,12 +51,16 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index c9352c6c6..224978ba6 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -26,4 +26,13 @@ matrix_synapse_password_config_localdb_enabled: false ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index eb05e0267..ecc4e588f 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -30,4 +30,13 @@ There are a few options for handling this: ### Re-running the playbook -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index 0c11df290..4d702704c 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -25,4 +25,13 @@ matrix_synapse_password_config_localdb_enabled: false ## Installing -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 52a9ee07c..491df75ba 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -39,7 +39,16 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all`. +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ### External databases diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 004b9f9dc..af1101c02 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -77,12 +77,16 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index 24547452e..a6b52fa9c 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -48,7 +48,16 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 3a3a310d2..94c85c76b 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -18,12 +18,16 @@ matrix_synapse_auto_compressor_enabled: true ## Installing -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) ## Usage diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index b3180281a..996ee2f03 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -50,4 +50,13 @@ If you've decided to use the default hostname, you won't need to do any extra DN ## Installing -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + +`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 0664ae826..0e1031028 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -90,12 +90,16 @@ This will instruct UVS to verify the OpenID token against any domain given in a ## Installing -After these variables have been set, run the [installation](installing.md) command to restart UVS: +After these variables have been set, run the playbook with [playbook tags](playbook-tags.md) as below to restart UVS: ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-user-verification-service,start ``` +The shortcut commands with `just` program are also available: `just run-tags setup-matrix-user-verification-service,start` or `just run-tags setup-all,start` + +`just run-tags setup-matrix-user-verification-service,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + ## Logging The configuration variable `UVS_LOG_LEVEL` can be set to: diff --git a/docs/faq.md b/docs/faq.md index 6afd37700..283604868 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -269,13 +269,20 @@ matrix_server_fqn_element: "element.example.com" matrix_server_fqn_etherpad: "etherpad.example.com" ``` -After configuring the playbook, run the [installation](installing.md) command: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -**Note**: without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user identifiers will be like `@user:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`. +**Notes**: + +- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + + `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user identifiers will be like `@user:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`. ### I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services? diff --git a/docs/importing-synapse-media-store.md b/docs/importing-synapse-media-store.md index 01180edab..4b6c1d336 100644 --- a/docs/importing-synapse-media-store.md +++ b/docs/importing-synapse-media-store.md @@ -18,6 +18,8 @@ As an alternative, you can perform a manual restore using the [AWS CLI tool](htt Run this command (make sure to replace `` with a path on your server): - ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_media_store=' --tags=import-synapse-media-store +```sh +ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_media_store=' --tags=import-synapse-media-store +``` **Note**: `` must be a file path to a `media_store` directory on the server (not on your local machine!). diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index c8803c844..586701da2 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -41,10 +41,13 @@ Re-run the playbook after making these configuration changes. ## Remove unused Docker data You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information. + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune ``` +The shortcut command with `just` program is also available: `just run-tags run-docker-prune` + ## Postgres See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page. diff --git a/docs/maintenance-checking-services.md b/docs/maintenance-checking-services.md index e6975b9d1..d68502357 100644 --- a/docs/maintenance-checking-services.md +++ b/docs/maintenance-checking-services.md @@ -8,6 +8,8 @@ To perform the check, run: ansible-playbook -i inventory/hosts setup.yml --tags=self-check ``` +The shortcut command with `just` program is also available: `just run-tags self-check` + If it's all green, everything is probably running correctly. Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain. diff --git a/docs/maintenance-migrating.md b/docs/maintenance-migrating.md index 29a2beb52..e2c0a7efa 100644 --- a/docs/maintenance-migrating.md +++ b/docs/maintenance-migrating.md @@ -46,6 +46,8 @@ Then, run the command below on your local computer to create the `matrix` user a ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user ``` +The shortcut command with `just` program is also available: `just run-tags setup-system-user` + **Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command: ```sh @@ -60,6 +62,8 @@ Finally, run the command below on your local computer to finish the installation ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start ``` +The shortcut command with `just` program is also available: `just run-tags install-all,start` + ### Check if services work After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md) diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index fdf2856d7..91e79661c 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -39,6 +39,8 @@ To ask the playbook to run rust-synapse-compress-state, execute: ansible-playbook -i inventory/hosts setup.yml --tags=rust-synapse-compress-state ``` +The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state` + By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above. After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql). diff --git a/docs/registering-users.md b/docs/registering-users.md index 3701b23e6..1633f162a 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -112,10 +112,20 @@ For Dendrite: matrix_dendrite_client_api_registration_disabled: false ``` -After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all` +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: -If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md). + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` +**Notes**: + +- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` + + `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + +- If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md). ## Adding/Removing Administrator privileges to an existing user From c385b794981bf257e2171c4df4e1529ef42f921c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 1 Dec 2024 01:44:37 +0900 Subject: [PATCH 038/952] Update docs/configuring-playbook-client-schildichat-web.md: remove warning notification about lagging versions As the SchildiChat Web docker image was updated with 14a3a01f43226487262d2e4c5d0a939ee93790be thanks to Aine, the warning is no longer relevant. Note that though the package name says it is a test, it is a test release for SchildiChat Web, and the codebase is Element Web v1.11.86. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-schildichat-web.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 780ac0829..a5ae5b2b7 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -8,8 +8,6 @@ SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with - [app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers -**WARNING**: SchildiChat Web is based on Element Web, but its releases are lagging behind. As of 2024-11, SchildiChat Web is many releases behind (it being based on Element Web `v1.11.36`, while Element Web is now on `v1.11.85`). Element Web frequently suffers from security issues (see [here](https://github.com/element-hq/element-web/security) for known issues), so running something based on an ancient Element Web release is **unsafe**. Use SchildiChat Web at your own risk! - ## Adjusting the playbook configuration To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: From bc1849d7ffbdabd530c71202fa770fc67bb87bb6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 00:04:54 +0900 Subject: [PATCH 039/952] Edit installing instructions (#3844) * Replace "just run-tags install-all/setup-all,start" with "just install-all/setup-all" Thanks to the tip by Slavi that the overhead of ensure-matrix-users-created is negligible. Signed-off-by: Suguru Hirahara * Edit installing instructions - Move the anchor links to docs/just.md - Add note about running "ensure-matrix-users-created" tags, if ansible-playbook's tags not "setup-all,ensure-matrix-users-created,start", ie. either "setup-all,start", "setup-email2matrix,start", "setup-aux-files,setup-corporal,start", or "setup-matrix-user-verification-service,start" Signed-off-by: Suguru Hirahara * Update descriptions about installation - Introduce the most conservative and stable raw ansible-playbook command. - Introduce the just commands on installing.md and maintenance-upgrading-services.md, not on quick-start.md, since it is too early for quick start guide readers who are just starting to climb learning curve to use the shortcuts. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: remove the note about ensure-matrix-users-created Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...configuring-playbook-alertmanager-receiver.md | 4 ++-- ...figuring-playbook-appservice-double-puppet.md | 4 ++-- ...uring-playbook-appservice-draupnir-for-all.md | 4 ++-- docs/configuring-playbook-backup-borg.md | 4 ++-- docs/configuring-playbook-bot-baibot.md | 4 ++-- docs/configuring-playbook-bot-buscarron.md | 4 ++-- docs/configuring-playbook-bot-chatgpt.md | 4 ++-- docs/configuring-playbook-bot-draupnir.md | 4 ++-- docs/configuring-playbook-bot-go-neb.md | 4 ++-- docs/configuring-playbook-bot-honoroit.md | 4 ++-- ...uring-playbook-bot-matrix-registration-bot.md | 4 ++-- ...nfiguring-playbook-bot-matrix-reminder-bot.md | 4 ++-- docs/configuring-playbook-bot-maubot.md | 4 ++-- docs/configuring-playbook-bot-mjolnir.md | 4 ++-- ...iguring-playbook-bridge-appservice-discord.md | 4 ++-- ...configuring-playbook-bridge-appservice-irc.md | 4 ++-- ...uring-playbook-bridge-appservice-kakaotalk.md | 4 ++-- ...nfiguring-playbook-bridge-appservice-slack.md | 4 ++-- ...guring-playbook-bridge-appservice-webhooks.md | 4 ++-- ...onfiguring-playbook-bridge-beeper-linkedin.md | 4 ++-- ...onfiguring-playbook-bridge-go-skype-bridge.md | 4 ++-- docs/configuring-playbook-bridge-heisenbridge.md | 4 ++-- ...figuring-playbook-bridge-matrix-bridge-sms.md | 4 ++-- ...onfiguring-playbook-bridge-mautrix-discord.md | 4 ++-- ...nfiguring-playbook-bridge-mautrix-facebook.md | 4 ++-- ...figuring-playbook-bridge-mautrix-gmessages.md | 4 ++-- ...iguring-playbook-bridge-mautrix-googlechat.md | 4 ++-- ...nfiguring-playbook-bridge-mautrix-hangouts.md | 4 ++-- ...figuring-playbook-bridge-mautrix-instagram.md | 4 ++-- ...ing-playbook-bridge-mautrix-meta-instagram.md | 4 ++-- ...ing-playbook-bridge-mautrix-meta-messenger.md | 4 ++-- ...configuring-playbook-bridge-mautrix-signal.md | 4 ++-- .../configuring-playbook-bridge-mautrix-slack.md | 4 ++-- ...nfiguring-playbook-bridge-mautrix-telegram.md | 4 ++-- ...onfiguring-playbook-bridge-mautrix-twitter.md | 4 ++-- ...nfiguring-playbook-bridge-mautrix-whatsapp.md | 4 ++-- ...onfiguring-playbook-bridge-mautrix-wsproxy.md | 4 ++-- ...figuring-playbook-bridge-mx-puppet-discord.md | 4 ++-- ...figuring-playbook-bridge-mx-puppet-groupme.md | 4 ++-- ...guring-playbook-bridge-mx-puppet-instagram.md | 4 ++-- ...onfiguring-playbook-bridge-mx-puppet-slack.md | 4 ++-- ...onfiguring-playbook-bridge-mx-puppet-steam.md | 4 ++-- ...figuring-playbook-bridge-mx-puppet-twitter.md | 4 ++-- docs/configuring-playbook-bridge-postmoogle.md | 4 ++-- docs/configuring-playbook-bridge-wechat.md | 4 ++-- docs/configuring-playbook-cactus-comments.md | 4 ++-- docs/configuring-playbook-client-cinny.md | 4 ++-- docs/configuring-playbook-client-element-web.md | 4 ++-- docs/configuring-playbook-client-hydrogen.md | 4 ++-- ...onfiguring-playbook-client-schildichat-web.md | 4 ++-- docs/configuring-playbook-dendrite.md | 4 ++-- docs/configuring-playbook-dimension.md | 4 ++-- docs/configuring-playbook-dynamic-dns.md | 4 ++-- docs/configuring-playbook-email2matrix.md | 4 ++-- docs/configuring-playbook-etherpad.md | 4 ++-- docs/configuring-playbook-jitsi.md | 4 ++-- docs/configuring-playbook-ma1sd.md | 4 ++-- ...ing-playbook-matrix-authentication-service.md | 4 ++-- docs/configuring-playbook-matrix-corporal.md | 4 ++-- ...ng-playbook-matrix-ldap-registration-proxy.md | 4 ++-- docs/configuring-playbook-matrix-registration.md | 4 ++-- docs/configuring-playbook-mautrix-bridges.md | 4 ++-- docs/configuring-playbook-ntfy.md | 4 ++-- docs/configuring-playbook-pantalaimon.md | 4 ++-- docs/configuring-playbook-postgres-backup.md | 4 ++-- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- docs/configuring-playbook-prometheus-nginxlog.md | 4 ++-- docs/configuring-playbook-prometheus-postgres.md | 4 ++-- docs/configuring-playbook-rageshake.md | 4 ++-- docs/configuring-playbook-rest-auth.md | 4 ++-- docs/configuring-playbook-riot-web.md | 4 ++-- docs/configuring-playbook-shared-secret-auth.md | 4 ++-- docs/configuring-playbook-sliding-sync-proxy.md | 4 ++-- docs/configuring-playbook-sygnal.md | 4 ++-- docs/configuring-playbook-synapse-admin.md | 4 ++-- ...nfiguring-playbook-synapse-auto-compressor.md | 4 ++-- ...onfiguring-playbook-synapse-usage-exporter.md | 4 ++-- ...iguring-playbook-user-verification-service.md | 4 ++-- docs/faq.md | 4 ++-- docs/installing.md | 16 +++++++++++++++- docs/maintenance-upgrading-services.md | 16 +++++++++++++--- docs/quick-start.md | 8 +++++++- docs/registering-users.md | 4 ++-- 83 files changed, 195 insertions(+), 165 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 1507d3bd9..635cb2e0e 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -87,9 +87,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index e4a3b3922..5f565c5da 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -27,9 +27,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index be13c93a3..18eadcfa8 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -60,9 +60,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 07fc3080f..abe8a55c7 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -78,9 +78,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Manually start a backup diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 423fcf16b..74d89eaad 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -387,9 +387,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index c1c00ecbe..7790558fd 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -67,9 +67,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index e892f2ea2..401fb9799 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -67,9 +67,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 7f34158d8..c3a57d563 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -126,9 +126,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 42cbcdc98..850fbbca5 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -230,9 +230,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index bf210dc02..acf340ce6 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -59,9 +59,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index ef846f33f..3d4d7efab 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -43,9 +43,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index 8142ac34f..e7a400fa4 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -38,9 +38,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 45b76f47a..bcc68b3d6 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -60,9 +60,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 7d1be0404..805c201ef 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -128,9 +128,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password. diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 760782da2..b8b73e08b 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -41,9 +41,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Self-Service Bridging (Manual) diff --git a/docs/configuring-playbook-bridge-appservice-irc.md b/docs/configuring-playbook-bridge-appservice-irc.md index cbd995e32..0a07b8588 100644 --- a/docs/configuring-playbook-bridge-appservice-irc.md +++ b/docs/configuring-playbook-bridge-appservice-irc.md @@ -73,9 +73,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 4a85b2aed..34e42bc52 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -44,9 +44,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index 85196e189..db2921315 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -76,9 +76,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index a937e0583..e20d3caa6 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -37,9 +37,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 58fd43640..24b689152 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -46,9 +46,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index 03b20989d..c96242185 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -25,9 +25,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index 96b7ca2f2..b85fab585 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -60,9 +60,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index 25103d753..d445ee0e7 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -44,9 +44,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 0f72110bb..39152d260 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -53,9 +53,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 8e41db1c6..848c1c64a 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -66,9 +66,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index c26b6e57e..e9a4fbc8b 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -31,9 +31,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 4c368f2b9..3cc73bae8 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -31,9 +31,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index fb64ed097..83aa016f7 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -33,9 +33,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 25a7b7d8b..d57b9346f 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -53,9 +53,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index cd70a8c42..1c1f1e793 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -79,9 +79,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 7883ebc9d..4ac22d227 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -93,9 +93,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index 561bfac2a..dea39e730 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -79,9 +79,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 175202644..167223d60 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -55,9 +55,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index 7b7d73182..b97fcbe77 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -33,9 +33,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index 6bde13c5a..93eaadb16 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -33,9 +33,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index 35adeb85c..a70f40d21 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -47,9 +47,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index ff9ff6246..a7363c190 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -52,9 +52,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index 3ab1b2ccf..b886f206b 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -29,9 +29,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md index ee0cf065a..3b928dd26 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md +++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md @@ -25,9 +25,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md index 3368dd579..da75cbb0c 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md +++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md @@ -25,9 +25,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index 4cb19d1b6..c9888729e 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -34,9 +34,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md index 56e37f714..5ab9655ae 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-steam.md +++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md @@ -25,9 +25,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md index 11024cf82..5d43b44b0 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md +++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md @@ -36,9 +36,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index d7e96d1d7..5b13a6719 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -60,9 +60,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index 5663904a1..98451bf00 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -25,9 +25,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 6a3dd3f8d..e39da3292 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -74,9 +74,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Usage diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 513cc7f6a..f4d02eefc 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -49,6 +49,6 @@ After configuring the playbook and [adjusting your DNS records](#adjusting-dns-r ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index f410459e3..deae92db1 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -78,6 +78,6 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index 600fc3b95..f63bf4eea 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -46,6 +46,6 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index a5ae5b2b7..670699d7c 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -74,6 +74,6 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 31d43c0e2..fd640cca0 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -41,6 +41,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 80645bcef..8544aa8cf 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -78,9 +78,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start **Notes**: -- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. - After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots. diff --git a/docs/configuring-playbook-dynamic-dns.md b/docs/configuring-playbook-dynamic-dns.md index e610f3b5f..48b0e6b61 100644 --- a/docs/configuring-playbook-dynamic-dns.md +++ b/docs/configuring-playbook-dynamic-dns.md @@ -32,9 +32,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Additional Reading diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 5b0bcd4fa..638ce468c 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -91,8 +91,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-email2matrix,start **Notes**: -- The shortcut commands with `just` program are also available: `just run-tags setup-email2matrix,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-email2matrix,start` or `just setup-all` - `just run-tags setup-email2matrix,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just run-tags setup-email2matrix,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. - After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected. diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 50ca562ed..a1d06d8d0 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -55,9 +55,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`). -- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. - 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. diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 9ea3fb9e6..fa560b844 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -276,9 +276,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 42408aaed..36485dcaf 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -138,9 +138,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Troubleshooting diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index 276c334fc..d3cfdd314 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -297,9 +297,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start **Notes**: -- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. - If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide. diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 3127ea701..6b04c4bcd 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -123,9 +123,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all` -`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. ## Matrix Corporal files diff --git a/docs/configuring-playbook-matrix-ldap-registration-proxy.md b/docs/configuring-playbook-matrix-ldap-registration-proxy.md index 02b04edf9..f38fd62a8 100644 --- a/docs/configuring-playbook-matrix-ldap-registration-proxy.md +++ b/docs/configuring-playbook-matrix-ldap-registration-proxy.md @@ -41,6 +41,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 3308d273e..1e8b4305d 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -59,9 +59,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md index 99b9974d7..8191e799b 100644 --- a/docs/configuring-playbook-mautrix-bridges.md +++ b/docs/configuring-playbook-mautrix-bridges.md @@ -104,9 +104,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -- The shortcut commands with `just` program are also available: `just install-all` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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. ## Set up Double Puppeting diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index dab016207..ee96d1813 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -57,9 +57,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index 5b0478a92..8b0d54589 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -25,6 +25,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 9d3967cbc..7204387f0 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -36,6 +36,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index ae9ec582b..7b63ebf1a 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -62,9 +62,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## What does it do? diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index c3c6081dd..296fad121 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -29,9 +29,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Docker Image Compatibility diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md index 7d71b1c33..019eb5a65 100644 --- a/docs/configuring-playbook-prometheus-postgres.md +++ b/docs/configuring-playbook-prometheus-postgres.md @@ -19,9 +19,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## What does it do? diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index b74eaeefd..292c17e5f 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -58,9 +58,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index 224978ba6..2a22841c5 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -33,6 +33,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index ecc4e588f..95a89ccd0 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -37,6 +37,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index 4d702704c..fb63001e4 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -32,6 +32,6 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 491df75ba..51a53df03 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -46,9 +46,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ### External databases diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index af1101c02..fc16c7911 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -84,9 +84,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index a6b52fa9c..ba33d177c 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -55,9 +55,9 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 94c85c76b..0e07ad1c7 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -25,9 +25,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 996ee2f03..0526becf5 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -57,6 +57,6 @@ After configuring the playbook and potentially [adjusting your DNS records](#adj ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 0e1031028..12ece9f02 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -96,9 +96,9 @@ After these variables have been set, run the playbook with [playbook tags](playb ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-user-verification-service,start ``` -The shortcut commands with `just` program are also available: `just run-tags setup-matrix-user-verification-service,start` or `just run-tags setup-all,start` +The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-matrix-user-verification-service,start` or `just setup-all` -`just run-tags setup-matrix-user-verification-service,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) +`just run-tags setup-matrix-user-verification-service,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. ## Logging diff --git a/docs/faq.md b/docs/faq.md index 283604868..aaf1ec362 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -278,9 +278,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start **Notes**: -- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. - Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user identifiers will be like `@user:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`. diff --git a/docs/installing.md b/docs/installing.md index f6c83bd66..0abfe0682 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -142,4 +142,18 @@ Since it is unsafe to keep outdated services running on the server connected to For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md) -Feel free to **re-run the setup command any time** you think something is off with the server configuration. Ansible will take your configuration and update your server to match. +Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match. + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags. + +### Make full use of `just` shortcut commands + +After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input. + +For example, `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + +You can learn about the shortcut commands on this page: [Running `just` commands](just.md) diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md index 57aa80dda..a59bf5940 100644 --- a/docs/maintenance-upgrading-services.md +++ b/docs/maintenance-upgrading-services.md @@ -37,11 +37,21 @@ After updating the Ansible roles, then re-run the [playbook setup](installing.md ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start ``` -If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with `--tags=setup-all` instead of `--tags=install-all`. See [this page on the playbook tags](playbook-tags.md) for more information. +If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below: -#### Run `just` to execute shortcut command +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` -If you want to invoke the `ansible-playbook` command with less typing, you can run `just` to execute the shortcut command: `just install-all` (or `just setup-all`). Note that it restarts all services automatically. +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any. + +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + + `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +- See [this page on the playbook tags](playbook-tags.md) for more information about those tags. ## PostgreSQL major version upgrade diff --git a/docs/quick-start.md b/docs/quick-start.md index b08af6514..11d8cb7d4 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -177,7 +177,13 @@ ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files 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. -If you think something is off with the server configuration, feel free to [re-run the full setup command](#run-the-installation-command) any time. +### Re-run the full setup command any time + +If you think something is wrong with the server configuration, feel free to re-run the setup command any time: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` ## Log in to your user account diff --git a/docs/registering-users.md b/docs/registering-users.md index 1633f162a..592d88b93 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -121,9 +121,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start **Notes**: -- The shortcut commands with `just` program are also available: `just run-tags install-all,start` or `just run-tags setup-all,start` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just run-tags install-all,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 run-tags setup-all,start`, or these components will still remain installed. For more information about `just` shortcuts, take a look at this page: [Running `just` commands](just.md) + `just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. - If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md). From dd5881f2b82d744ab3461f1d74a17ea6b484dc1d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 1 Dec 2024 02:28:06 +0900 Subject: [PATCH 040/952] Adjust blank lines: remove duplicated ones Signed-off-by: Suguru Hirahara --- docs/alternative-architectures.md | 1 - docs/ansible.md | 8 -------- .../configuring-playbook-alertmanager-receiver.md | 1 - ...guring-playbook-appservice-draupnir-for-all.md | 2 -- docs/configuring-playbook-base-domain-serving.md | 2 -- docs/configuring-playbook-bot-baibot.md | 13 ------------- docs/configuring-playbook-bot-chatgpt.md | 3 --- docs/configuring-playbook-bot-draupnir.md | 7 ------- docs/configuring-playbook-bot-go-neb.md | 2 -- docs/configuring-playbook-bot-honoroit.md | 1 - ...guring-playbook-bot-matrix-registration-bot.md | 1 - ...onfiguring-playbook-bot-matrix-reminder-bot.md | 2 -- docs/configuring-playbook-bot-mjolnir.md | 6 ------ ...configuring-playbook-bridge-beeper-linkedin.md | 2 -- docs/configuring-playbook-bridge-hookshot.md | 2 -- ...configuring-playbook-bridge-mautrix-discord.md | 1 - ...figuring-playbook-bridge-mautrix-googlechat.md | 1 - ...ring-playbook-bridge-mautrix-meta-messenger.md | 1 - docs/configuring-playbook-bridge-mautrix-slack.md | 1 - docs/configuring-playbook-bridge-postmoogle.md | 1 - docs/configuring-playbook-client-cinny.md | 1 - docs/configuring-playbook-client-element-web.md | 3 --- docs/configuring-playbook-conduit.md | 2 -- docs/configuring-playbook-dendrite.md | 2 -- docs/configuring-playbook-dimension.md | 1 - docs/configuring-playbook-email.md | 3 --- docs/configuring-playbook-email2matrix.md | 1 - docs/configuring-playbook-etherpad.md | 6 ------ docs/configuring-playbook-federation.md | 3 --- docs/configuring-playbook-jitsi.md | 4 ---- docs/configuring-playbook-ldap-auth.md | 3 --- docs/configuring-playbook-ma1sd.md | 2 -- ...ring-playbook-matrix-authentication-service.md | 15 --------------- docs/configuring-playbook-matrix-corporal.md | 1 - docs/configuring-playbook-matrix-registration.md | 3 --- docs/configuring-playbook-mautrix-bridges.md | 3 --- docs/configuring-playbook-ntfy.md | 2 -- docs/configuring-playbook-own-webserver.md | 3 --- docs/configuring-playbook-postgres-backup.md | 3 --- docs/configuring-playbook-prometheus-grafana.md | 3 --- docs/configuring-playbook-prometheus-postgres.md | 1 - docs/configuring-playbook-riot-web.md | 3 --- docs/configuring-playbook-s3-goofys.md | 2 -- docs/configuring-playbook-s3.md | 5 ----- docs/configuring-playbook-sliding-sync-proxy.md | 1 - docs/configuring-playbook-ssl-certificates.md | 4 ---- docs/configuring-playbook-synapse-admin.md | 1 - ...iguring-playbook-synapse-auto-accept-invite.md | 2 -- ...onfiguring-playbook-synapse-auto-compressor.md | 2 -- ...guring-playbook-synapse-s3-storage-provider.md | 3 --- docs/configuring-playbook-synapse.md | 5 ----- docs/configuring-playbook-telemetry.md | 2 -- docs/configuring-playbook-traefik.md | 3 --- docs/configuring-playbook-turn.md | 2 -- docs/configuring-playbook.md | 2 -- docs/configuring-well-known.md | 1 - docs/container-images.md | 1 - docs/faq.md | 4 ---- docs/getting-the-playbook.md | 3 --- docs/howto-server-delegation.md | 2 -- docs/importing-postgres.md | 2 -- docs/importing-synapse-media-store.md | 2 -- docs/importing-synapse-sqlite.md | 1 - docs/maintenance-and-troubleshooting.md | 1 - docs/maintenance-postgres.md | 4 ---- docs/maintenance-synapse.md | 2 -- docs/obtaining-access-tokens.md | 1 - docs/registering-users.md | 4 ---- docs/uninstalling.md | 5 ----- docs/updating-users-passwords.md | 2 -- 70 files changed, 195 deletions(-) diff --git a/docs/alternative-architectures.md b/docs/alternative-architectures.md index 0865de1f0..fa05a4b46 100644 --- a/docs/alternative-architectures.md +++ b/docs/alternative-architectures.md @@ -10,7 +10,6 @@ The playbook automatically determines the target server's architecture (the `mat Some tools and container images can be built on the host or other measures can be used to install on that architecture. - ## Implementation details For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building). diff --git a/docs/ansible.md b/docs/ansible.md index f71b5ccf2..a53289795 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -5,7 +5,6 @@ This playbook is meant to be run using [Ansible](https://www.ansible.com/). Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to). - ## Supported Ansible versions To manually check which version of Ansible you're on, run: `ansible --version`. @@ -16,7 +15,6 @@ We're not sure what's the minimum version of Ansible that can run this playbook If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker). - ## Upgrading Ansible Depending on your distribution, you may be able to upgrade Ansible in a few different ways: @@ -27,10 +25,8 @@ Depending on your distribution, you may be able to upgrade Ansible in a few diff If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path. - **Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software. - ## Using Ansible via Docker Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image). @@ -39,7 +35,6 @@ This ensures that you're using a very recent Ansible version, which is less like You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server). - ### Running Ansible in a container on the Matrix server itself To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it: @@ -71,7 +66,6 @@ First, consider running `git config --global --add safe.directory /work` to [res Finally, you can execute `ansible-playbook ...` (or `ansible-playbook --connection=community.docker.nsenter ...`) commands as per normal now. - ### Running Ansible in a container on another computer (not the Matrix server) Run this from the playbook's directory: @@ -93,7 +87,6 @@ First, consider running `git config --global --add safe.directory /work` to [res Finally, you execute `ansible-playbook ...` commands as per normal now. - #### If you don't use SSH keys for authentication If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`). @@ -104,7 +97,6 @@ apk add sshpass ``` Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command. - #### Resolve directory ownership issues 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: diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 635cb2e0e..43875bb1e 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -73,7 +73,6 @@ Steps 1 and 2 above only need to be done once, while preparing your [configurati Steps 3 and 4 need to be done for each new room you'd like the bot to deliver alerts to. Step 5 is optional and provides cleaner `/alert/` URLs. - ## Installing Now that you've [prepared the bot account and room](#account-and-room-preparation), [configured the playbook](#adjusting-the-playbook-configuration), and potentially [adjusted your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 18eadcfa8..28c231dd9 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -4,7 +4,6 @@ The playbook can install and configure the [Draupnir](https://github.com/the-dra Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below. - ## Draupnir Appservice mode compared to Draupnir bot mode The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document. @@ -17,7 +16,6 @@ Normal Draupnir does come with the benefit of access to Synapse Admin features. Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account. - ## Installation ### 1. Create a main management room. diff --git a/docs/configuring-playbook-base-domain-serving.md b/docs/configuring-playbook-base-domain-serving.md index 069ad195f..3a3335e70 100644 --- a/docs/configuring-playbook-base-domain-serving.md +++ b/docs/configuring-playbook-base-domain-serving.md @@ -33,7 +33,6 @@ Doing this, the playbook will: - serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain). - ## Serving a static website at the base domain By default, when "serving the base domain" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable. @@ -56,7 +55,6 @@ With this configuration, Ansible will no longer mess around with the `/matrix/st You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already. - ## Serving a more complicated website at the base domain If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice. diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 74d89eaad..4e09d5bad 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -11,12 +11,10 @@ It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/ch It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information. - ## Prerequisites API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md). - ## Adjusting the playbook configuration There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**: @@ -30,7 +28,6 @@ There are **a lot of configuration options** (some required, some possibly requi Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**. - ### Base configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -73,7 +70,6 @@ matrix_bot_baibot_config_persistence_config_encryption_key: 'A_HEX_STRING_OF_64_ As mentioned above, **this may not be enough**. Continue with the configuration sections below. - ### 👮‍♂️ Administrator configuration This is an addition to the [base configuration](#base-configuration). @@ -139,7 +135,6 @@ Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#G Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai). - #### Anthropic You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables. @@ -166,7 +161,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). - #### Groq You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables. @@ -200,7 +194,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). - #### Mistral You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables. @@ -229,7 +222,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). - #### OpenAI You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables. @@ -260,7 +252,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). - #### OpenAI Compatible You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables. @@ -271,7 +262,6 @@ Some of these popular services already have **shortcut** providers (see [support As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset). - #### Configuring additional agents (without a preset) The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration. @@ -327,7 +317,6 @@ As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents. 💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). - ### 🤝 Configuring initial default handlers This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**). @@ -373,7 +362,6 @@ matrix_bot_baibot_config_initial_global_config_handler_image_generation: null **Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands. - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -407,7 +395,6 @@ Send `!bai help` to the room at any time to see the bot's help menu for addition You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation. - ## Debugging As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot` diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 401fb9799..c04a0ddf3 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -20,14 +20,12 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` - ## 2. Get an access token and create encryption keys Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). 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). - ## 3. Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -53,7 +51,6 @@ matrix_bot_chatgpt_matrix_bot_prompt_prefix: 'Instructions:\nYou are ChatGPT, a You will need to get tokens for ChatGPT. - ## 4. Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index c3a57d563..f26337079 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -6,7 +6,6 @@ See the project's [documentation](https://github.com/the-draupnir-project/Draupn This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead. - If your migrating from Mjolnir skip to step 5b. ## 1. Register the bot account @@ -25,12 +24,10 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupni If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. - ## 2. Get an access token Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - ## 3. Make sure the account is free from rate limiting You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. @@ -39,8 +36,6 @@ If your Synapse Admin API is exposed to the internet for some reason like runnin The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@example:example.com/override_ratelimit` Replace `@example:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token. - - ## 4. Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. @@ -51,7 +46,6 @@ Once you have created the room you need to copy the room ID so you can tell the Finally invite the `@bot.draupnir:example.com` account you created earlier into the room. - ## 5. Adjusting the playbook configuration Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). @@ -200,7 +194,6 @@ To **enable a given protection**, send a command like this: `!draupnir enable PR To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`). - ## Extending the configuration You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 850fbbca5..a34a7dc01 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -8,7 +8,6 @@ Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the ori See the project's [documentation](https://github.com/matrix-org/go-neb) to learn what it does and why it might be useful to you. - ## Registering the bot user The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver. @@ -25,7 +24,6 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb Once the user is created you can [obtain an access token](obtaining-access-tokens.md). - ## Adjusting the playbook configuration To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index acf340ce6..d977df5b2 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -6,7 +6,6 @@ It's a bot you can use to setup **your own helpdesk on matrix** See the project's [documentation](https://github.com/etkecc/honoroit#how-it-looks-like) to learn what it does with screenshots and why it might be useful to you. - ## Adjusting the playbook configuration To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 3d4d7efab..6f2522c58 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -6,7 +6,6 @@ The bot allows you to easily **create and manage registration tokens** aka. invi See the project's [documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands) to learn what it does and why it might be useful to you. - ## Configuration To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index e7a400fa4..3d9c9c232 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -6,7 +6,6 @@ It's a bot you can use to **schedule one-off & recurring reminders and alarms**. See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage) to learn what it does and why it might be useful to you. - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -24,7 +23,6 @@ matrix_bot_matrix_reminder_bot_matrix_user_password: PASSWORD_FOR_THE_BOT matrix_bot_matrix_reminder_bot_reminders_timezone: Europe/London ``` - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 805c201ef..e3e7cf6cd 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -4,7 +4,6 @@ The playbook can install and configure the [Mjolnir](https://github.com/matrix-o See the project's [documentation](https://github.com/matrix-org/mjolnir) to learn what it does and why it might be useful to you. - ## 1. Register the bot account The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. @@ -21,12 +20,10 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. - ## 2. Get an access token Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - ## 3. Make sure the account is free from rate limiting You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. @@ -45,7 +42,6 @@ Once you have created the room you need to copy the room ID so you can tell the Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room. - ## 5. Adjusting the playbook configuration Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). @@ -105,7 +101,6 @@ matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): - ```yaml matrix_synapse_ext_spam_checker_mjolnir_antispam_enabled: true matrix_synapse_ext_spam_checker_mjolnir_antispam_config_block_invites: true @@ -114,7 +109,6 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_block_usernames: false matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] ``` - ## 7. Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 24b689152..02b4d5fed 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -58,7 +58,6 @@ Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppe Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - ## Usage You then need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). @@ -69,7 +68,6 @@ If you run into trouble, check the [Troubleshooting](#troubleshooting) section b After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so. - ## Troubleshooting ### Bridge asking for 2FA even if you don't have 2FA enabled diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index fdf4af00f..019ffa283 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -8,7 +8,6 @@ See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/l **Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author. - ## Setup Instructions Refer to the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) to learn what the individual options do. @@ -41,7 +40,6 @@ Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot **Important**: Note that the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation, see [URLs for bridges setup](#urls-for-bridges-setup) below. - ## More setup documentation ### URLs for bridges setup diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 39152d260..e0107ec07 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -8,7 +8,6 @@ The playbook can install and configure [mautrix-discord](https://github.com/maut See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you. - ## Prerequisites There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended). diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 3cc73bae8..1f5b1760d 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -61,7 +61,6 @@ Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppe Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - #### Method 2: manually, by asking each user to provide a working access token When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 4ac22d227..bf21c3008 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -48,7 +48,6 @@ You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variab Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.). - ### Bridge permissions By default, any user on your homeserver will be able to use the bridge. diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 167223d60..3459d8c34 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -10,7 +10,6 @@ See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.htm See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information. - ## Prerequisites For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html). diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 5b13a6719..a4cf9f7ff 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -19,7 +19,6 @@ If you don't open these ports, you will still be able to send emails, but not re These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use. - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index f4d02eefc..d75a2ef72 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -8,7 +8,6 @@ Cinny is a web client focusing primarily on simple, elegant and secure interface - [app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers - ## Adjusting the playbook configuration To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index deae92db1..989c41c9b 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -7,7 +7,6 @@ By default, this playbook installs the [Element Web](https://github.com/element- - [app.element.io](https://app.element.io/), hosted by [Element](https://element.io/) - [app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/) - ## Disabling Element Web If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -16,7 +15,6 @@ If you'd like for the playbook to not install Element Web (or to uninstall it if matrix_client_element_enabled: false ``` - ## Adjusting the playbook configuration The playbook provides some customization variables you could use to change Element Web's settings. @@ -33,7 +31,6 @@ Alternatively, **if there is no pre-defined variable** for an Element Web settin - or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml). - ### Themes To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting. diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 909c1ce0e..68faa0d3c 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -27,7 +27,6 @@ Since it is difficult to create the first user account on Conduit (see [famedly/ 5. Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time) 6. You can now use your server safely. Additional users can be created by messaging the internal Conduit bot - ## Configuring bridges / appservices Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start. @@ -36,7 +35,6 @@ You will have to manually register appservices using the the [register-appservic Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit: - @conduit:example.com: register-appservice ``` as_token: diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index fd640cca0..fdcb830f2 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -30,8 +30,6 @@ Alternatively, **if there is no pre-defined variable** for a Dendrite setting yo - or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). - - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 8544aa8cf..cd34fd5cd 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -90,7 +90,6 @@ By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `co In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately. - ## Additional features To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component. diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 1106a1f53..51615e752 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -10,12 +10,10 @@ By default, emails are sent from `matrix@matrix.example.com`, as specified by th 💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway. - ## Firewall settings No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration). - ## Relaying email through another SMTP server If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -32,7 +30,6 @@ exim_relay_relay_auth_password: "some-password" **Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**. - ### Configuations for sending emails using Sendgrid An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`. diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 638ce468c..a819aa081 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -6,7 +6,6 @@ The playbook can install and configure [email2matrix](https://github.com/devture See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you. - ## Preparation ### DNS configuration diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index a1d06d8d0..f91af766c 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -33,7 +33,6 @@ etherpad_hostname: "{{ matrix_server_fqn_matrix }}" etherpad_path_prefix: /etherpad ``` - ## Adjusting DNS records Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server. @@ -67,35 +66,30 @@ The Etherpad UI should be available at `https://etherpad.example.com`, while the If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage. - ### Managing / Deleting old pads If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above. Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a "Manage pads" section in the Admin web-UI. - ### How to use Etherpad widgets without an integration manager (like Dimension) This is how it works in Element Web, it might work quite similar with other clients: To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section. - ### Set Dimension default to the self-hosted Etherpad (optional) If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template. The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab. - #### Removing the integrated Etherpad chat If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template. Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false` - ## Known issues If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it. diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index 3a6c18ad9..56f31b319 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -16,7 +16,6 @@ matrix_synapse_federation_domain_whitelist: If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below). - ## Exposing the room directory over federation By default, your server's public rooms directory is not exposed to other servers via federation. @@ -27,7 +26,6 @@ If you wish to expose it, add this to your configuration file (`inventory/host_v matrix_synapse_allow_public_rooms_over_federation: true ``` - ## Disabling federation To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): @@ -54,7 +52,6 @@ matrix_synapse_reverse_proxy_companion_federation_api_enabled: false Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection. - The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other: ```yaml diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index fa560b844..50cb2594e 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -6,7 +6,6 @@ Jitsi installation is **not enabled by default**, because it's not a core compon The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here. - ## Prerequisites You may need to open the following ports to your server: @@ -14,7 +13,6 @@ You may need to open the following ports to your server: - `4443/tcp` - RTP media fallback over TCP - `10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)). - ## Adjusting the playbook configuration To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -114,7 +112,6 @@ jitsi_ldap_start_tls: false For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation. - ## (Optional) Making your Jitsi server work on a LAN By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok. @@ -292,7 +289,6 @@ You can use the self-hosted Jitsi server in multiple ways: **Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support). - ## Troubleshooting ### Rebuilding your Jitsi installation diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md index 451d386ba..8f77bd849 100644 --- a/docs/configuring-playbook-ldap-auth.md +++ b/docs/configuring-playbook-ldap-auth.md @@ -21,7 +21,6 @@ matrix_synapse_ext_password_provider_ldap_bind_password: "" matrix_synapse_ext_password_provider_ldap_filter: "" ``` - ## Authenticating only using a password provider If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it: @@ -30,12 +29,10 @@ If you wish for users to **authenticate only against configured password provide matrix_synapse_password_config_localdb_enabled: false ``` - ## Using ma1sd Identity Server for authentication If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication). - ## Handling user registration 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). diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 36485dcaf..14376d42d 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -51,7 +51,6 @@ Still, ma1sd can do much more. You can refer to the [ma1sd website](https://gith To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component. - #### Customizing email templates If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file. @@ -72,7 +71,6 @@ To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/featu **Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation). - #### Authentication [Authentication](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. diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index d3cfdd314..e81efd78a 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -12,7 +12,6 @@ Matrix Authentication Service is an implementation of [MSC3861: Next-generation **If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service). - ## Reasons to use Matrix Authentication Service You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled). @@ -33,7 +32,6 @@ Below, we'll try to **highlight some potential reasons for switching** to Matrix - To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article. - ## Prerequisites - ⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet. @@ -42,7 +40,6 @@ Below, we'll try to **highlight some potential reasons for switching** to Matrix - ❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below. - ## Expectations This section details what you can expect when switching to the Matrix Authentication Service (MAS). @@ -84,8 +81,6 @@ This section details what you can expect when switching to the Matrix Authentica - ✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. - - ## Installation flows ### New homeserver @@ -102,7 +97,6 @@ For existing Synapse homeservers: - then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration - ## Adjusting the playbook configuration To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -123,7 +117,6 @@ In the sub-sections that follow, we'll cover some additional configuration optio There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them. - ### Adjusting the Matrix Authentication Service URL By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. @@ -144,7 +137,6 @@ The [configuration above](#adjusting-the-playbook-configuration) instructs exist This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below. - ### Upstream OAuth2 configuration To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers). @@ -276,7 +268,6 @@ matrix_authentication_service_config_upstream_oauth2_providers: - go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process - remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration - ## Adjusting DNS records If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server. @@ -285,7 +276,6 @@ See [Configuring DNS](configuring-dns.md) for details about DNS changes. If you've decided to use the default hostname, you won't need to do any extra DNS configuration. - ## Installing Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below: @@ -305,7 +295,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start 💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly). - ## Migrating an existing Synapse homeserver to Matrix Authentication Service Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide. @@ -344,7 +333,6 @@ The installation + migration steps are like this: 6. [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) - ### Migrate your data from Synapse to Matrix Authentication Service using syn2mas We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work. @@ -418,7 +406,6 @@ just run-tags matrix-authentication-service-syn2mas Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. "Error: Unknown upstream provider oauth-delegated"). - ## Verify that Matrix Authentication Service is installed correctly After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly. @@ -453,14 +440,12 @@ This documentation page already mentions: There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview. - ## User registration After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration)). You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag). - ## Working around email deliverability issues Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working. diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 6b04c4bcd..cf8292eda 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -14,7 +14,6 @@ If you decide that you'd like to let this playbook install it for you, you'd nee - (required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) - (optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md) - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 1e8b4305d..a55a50b73 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -16,7 +16,6 @@ Use matrix-registration to **create unique registration links**, which people ca - **a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration` - ## Adjusting the playbook configuration To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -71,7 +70,6 @@ It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/a We make the most common APIs easy to use via the playbook (see below). - ### Creating registration tokens To **create a new user registration token (link)**, use this command: @@ -86,7 +84,6 @@ The above command creates and returns a **one-time use** token, which **expires* Share the unique registration link (generated by the command above) with users to let them register on your Matrix server. - ### Listing registration tokens To **list the existing user registration tokens**, use this command: diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md index 8191e799b..126fa5f3a 100644 --- a/docs/configuring-playbook-mautrix-bridges.md +++ b/docs/configuring-playbook-mautrix-bridges.md @@ -130,7 +130,6 @@ to `vars.yml` to control the logging level, where you may replace WARN with one If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful. - ## Usage You then need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). @@ -139,8 +138,6 @@ Send `login` to the bridge bot to get started. You can learn more here about aut If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. - - ## Troubleshooting For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge. diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index ee96d1813..9256697d7 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -8,7 +8,6 @@ This role is intended to support UnifiedPush notifications for use with the Matr **Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it. - ## Adjusting the playbook configuration To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -106,7 +105,6 @@ ntfy also has a web app to subscribe to and push to topics from the browser. Thi The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: "app"` and re-running Ansible. - ## Troubleshooting First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app. diff --git a/docs/configuring-playbook-own-webserver.md b/docs/configuring-playbook-own-webserver.md index c3aff0ac3..8f8f8682d 100644 --- a/docs/configuring-playbook-own-webserver.md +++ b/docs/configuring-playbook-own-webserver.md @@ -24,7 +24,6 @@ traefik_config_certificatesResolvers_acme_email: YOUR_EMAIL_ADDRESS Traefik will manage SSL certificates for all services seamlessly. - ### Traefik managed by you ```yaml @@ -132,7 +131,6 @@ There are 2 ways to go about it: - (difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports - ### Fronting the integrated reverse-proxy webserver with another reverse-proxy This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.). @@ -201,7 +199,6 @@ To put it another way: - `curl http://127.0.0.1:81` will result in a `404 - not found` error - but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work. - ### Using no reverse-proxy on the Matrix side at all 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. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 7204387f0..58d719f8f 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -4,7 +4,6 @@ The playbook can install and configure [docker-postgres-backup-local](https://gi For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead. - ## Adjusting the playbook configuration To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -15,7 +14,6 @@ postgres_backup_enabled: true Refer to the table below for additional configuration variables and their default values. - | Name | Default value | Description | | :-------------------------------- | :--------------------------- | :--------------------------------------------------------------- | |`postgres_backup_enabled`|`false`|Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups| @@ -26,7 +24,6 @@ Refer to the table below for additional configuration variables and their defaul |`postgres_backup_base_path` | `"{{ matrix_base_data_path }}/postgres-backup"` | Base path for postgres-backup. Also see `postgres_backup_data_path` | |`postgres_backup_data_path` | `"{{ postgres_backup_base_path }}/data"` | Storage path for postgres-backup database backups | - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 7b63ebf1a..f4786f807 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -78,14 +78,12 @@ Name | Description `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. `grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here - ## Security and privacy Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password. Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source. - ## Collecting metrics to an external Prometheus server **If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics "publicly". @@ -148,7 +146,6 @@ scrape_configs: index: 18111 ``` - ## More information - [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md index 019eb5a65..c3c05653c 100644 --- a/docs/configuring-playbook-prometheus-postgres.md +++ b/docs/configuring-playbook-prometheus-postgres.md @@ -32,7 +32,6 @@ Name | Description `prometheus_postgres_exporter_database_password`| The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook `prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page. - ## More information - [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard) diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index 95a89ccd0..398a0a444 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -7,7 +7,6 @@ Riot has since been [renamed to Element](https://element.io/blog/welcome-to-elem - to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page - to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below - ## Migrating to Element Web ### Migrating your custom settings @@ -16,7 +15,6 @@ If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/mat Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones. - ### Domain migration We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default. @@ -27,7 +25,6 @@ There are a few options for handling this: - (**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case. - ### Re-running the playbook After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-s3-goofys.md b/docs/configuring-playbook-s3-goofys.md index 81df60636..720c7d8b2 100644 --- a/docs/configuring-playbook-s3-goofys.md +++ b/docs/configuring-playbook-s3-goofys.md @@ -29,7 +29,6 @@ matrix_s3_media_store_custom_endpoint: "https://your-custom-endpoint" If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is. - ## Migrating from local filesystem storage to S3 It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one. @@ -85,7 +84,6 @@ After making the backup, follow one of the guides below for a migration path fro 14. When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup` - ### Migrating to Backblaze B2 1. While all Matrix services are running, run the following command on the server: diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md index 3620f70a8..cb43c62fb 100644 --- a/docs/configuring-playbook-s3.md +++ b/docs/configuring-playbook-s3.md @@ -12,7 +12,6 @@ Then, [create the S3 bucket](#bucket-creation-and-security-configuration). Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html)). - ## Choosing an Object Storage provider You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object 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. @@ -32,7 +31,6 @@ Here are some of the important aspects of choosing the right provider: - if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.) - if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case - ## Bucket creation and Security Configuration Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket. @@ -66,7 +64,6 @@ You'll need an Amazon S3 bucket and some IAM user credentials (access key + secr **Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**. - ## Backblaze B2 To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up. @@ -92,14 +89,12 @@ For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-stora - **Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value. - ## Other providers For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2)). You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner. - ## Setting up To set up Synapse to store files in S3, follow the instructions for the method of your choice: diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 51a53df03..b0a9c4a52 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -6,7 +6,6 @@ The playbook can install and configure [sliding-sync](https://github.com/matrix- 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. - ## Adjusting the playbook configuration To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-ssl-certificates.md b/docs/configuring-playbook-ssl-certificates.md index e086d457f..fc004d0bf 100644 --- a/docs/configuring-playbook-ssl-certificates.md +++ b/docs/configuring-playbook-ssl-certificates.md @@ -4,7 +4,6 @@ By default, this playbook retrieves and auto-renews free SSL certificates from [ This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md). - ## Using staging Let's Encrypt certificates instead of real ones For testing purposes, you may wish to use staging certificates provide by Let's Encrypt. @@ -15,7 +14,6 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ traefik_config_certificatesResolvers_acme_use_staging: true ``` - ## Disabling SSL termination For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`. @@ -26,7 +24,6 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ traefik_config_entrypoint_web_secure_enabled: false ``` - ## Using self-signed SSL certificates If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)): @@ -34,7 +31,6 @@ If you'd like to use your own SSL certificates, instead of the default (SSL cert - generate your self-signed certificate files - follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below - ## Using your own SSL certificates To use your own SSL certificates with Traefik, you need to: diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index ba33d177c..ffb2b4749 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -6,7 +6,6 @@ synapse-admin is a web UI tool you can use to **administrate users, rooms, media 💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting. - ## Adjusting the playbook configuration To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-synapse-auto-accept-invite.md b/docs/configuring-playbook-synapse-auto-accept-invite.md index 33e9268c2..4ef0c4b90 100644 --- a/docs/configuring-playbook-synapse-auto-accept-invite.md +++ b/docs/configuring-playbook-synapse-auto-accept-invite.md @@ -6,7 +6,6 @@ See that project's [documentation](https://github.com/matrix-org/synapse-auto-ac **Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module. - ## Configuration If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -27,7 +26,6 @@ matrix_synapse_ext_synapse_auto_accept_invite_worker_to_run_on: 'matrix-synapse- There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18). - ## Native alternative Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse. diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 0e07ad1c7..3e98fd9d1 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -6,7 +6,6 @@ It's a CLI tool that automatically compresses Synapse's `state_groups` database See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you. - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -15,7 +14,6 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_synapse_auto_compressor_enabled: true ``` - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index 410af46eb..82af9574d 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -4,7 +4,6 @@ If you'd like to store Synapse's content repository (`media_store`) files on Ama An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md). - ## How it works? Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/). @@ -22,7 +21,6 @@ You can run some scripts to delete the local files once in a while (which we do While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store. - ## Installing After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): @@ -57,7 +55,6 @@ If you have existing files in Synapse's media repository (`/matrix/synapse/media Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below. - ## Migrating your existing media files to the S3 store Migrating your existing data can happen in multiple ways: diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index b9291c3b9..9ec3876aa 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -16,7 +16,6 @@ Alternatively, **if there is no pre-defined variable** for a Synapse setting you - or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml). - ## Load balancing with workers To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). @@ -80,12 +79,10 @@ A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`. - ## Synapse Admin Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md). - ## Synapse + OpenID Connect for Single-Sign-On 💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment. @@ -117,7 +114,6 @@ matrix_synapse_oidc_providers: backchannel_logout_enabled: true # Optional ``` - ## Customizing templates [Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**. @@ -156,7 +152,6 @@ matrix_synapse_container_image_customizations_templates_git_repository_ssh_priva As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates. - ## Monitoring Synapse Metrics with Prometheus and Grafana This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse. diff --git a/docs/configuring-playbook-telemetry.md b/docs/configuring-playbook-telemetry.md index 37ad76b0b..cb144ee1c 100644 --- a/docs/configuring-playbook-telemetry.md +++ b/docs/configuring-playbook-telemetry.md @@ -4,7 +4,6 @@ By default, this playbook configures your Matrix homeserver to not send any tele The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success. - ## Enabling Telemetry If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -15,7 +14,6 @@ matrix_synapse_report_stats: true # for synapse matrix_dendrite_report_stats: true # for dendrite ``` - ## Usage statistics being submitted When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver. diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 019265b16..9032ed1cf 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -4,7 +4,6 @@ By default, this playbook installs and manages a [Traefik](https://doc.traefik.i This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file. - ## Adjusting SSL certificate retrieval See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page. @@ -89,7 +88,6 @@ traefik_configuration_extension_yaml: | insecureSkipVerify: true ``` - Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates. ```yaml @@ -138,7 +136,6 @@ With these changes, all TCP traffic will be reverse-proxied to the target system **WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. - ## Traefik behind a `proxy_protocol` reverse-proxy If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file: diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index 6bd0a8ad7..f71b84e69 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -4,7 +4,6 @@ The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server b By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook. - ## Disabling Coturn If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -48,7 +47,6 @@ Regardless of the selected authentication method, the playbook generates secrets If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method. - ## Using your own external Coturn server If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this: diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index d1b9993ec..1b1de3c50 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -24,7 +24,6 @@ For a more custom setup, see the [Other configuration options](#other-configurat [▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md). - ## Other configuration options ### Core service adjustments @@ -166,7 +165,6 @@ Bridges can be used to connect your Matrix installation with third-party communi - [Setting up WeChat bridging](configuring-playbook-bridge-wechat.md) - ### Bots Bots provide various additional functionality to your installation. diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index 0dab9c6c6..5b051492d 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -177,7 +177,6 @@ Make sure to: - **replace `example.com`** in the server configuration with your actual domain name - and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be - ## Confirming it works No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs: diff --git a/docs/container-images.md b/docs/container-images.md index 77d83eeb3..b893412d6 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -4,7 +4,6 @@ This page summarizes the container ([Docker](https://www.docker.com/)) images us We try to stick to official images (provided by their respective projects) as much as possible. - ## Homeserver | Service | Container image | Default? | Description | diff --git a/docs/faq.md b/docs/faq.md index aaf1ec362..c60d5e403 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -229,7 +229,6 @@ Besides the regular Matrix stuff, we also support things like video-conferencing If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container. - ## Configuration ### Why install my server at matrix.example.com and not at the base domain? @@ -372,7 +371,6 @@ Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable a **Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`). - ## Installation ### How do I run the installation? @@ -405,7 +403,6 @@ It can perform a local connection instead. Just set `ansible_connection=local` a If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible. - ## Troubleshooting ### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`. @@ -445,7 +442,6 @@ RateLimitBurst=0 Storage=persistent ``` - ## Maintenance ### Do I need to do anything to keep my Matrix server updated? diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index 3ae14a705..4db76c5c6 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -12,7 +12,6 @@ You can retrieve the playbook's source code by: - [Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended) - ## Using git to get the playbook We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md). @@ -25,7 +24,6 @@ git clone https://github.com/spantaleev/matrix-docker-ansible-deploy.git This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory. - ## Downloading the playbook as a ZIP archive Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead. @@ -34,7 +32,6 @@ The latest version is always at the following URL: https://github.com/spantaleev You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory. - --------------------------------------------- [▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md). diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index a4056f397..ff41f3eb3 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -33,7 +33,6 @@ Server Delegation by means of a `/.well-known/matrix/server` file is the most st Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated). - ## Server Delegation via a DNS SRV record (advanced) **Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this. @@ -60,7 +59,6 @@ If `example.com` and `matrix.example.com` are hosted on the same machine, you ca If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire. - ### Serving the Federation API with your certificates Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use. diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index cdba3f743..06ea65ea6 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -3,7 +3,6 @@ Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md)). - ## Prerequisites For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding. @@ -14,7 +13,6 @@ The migration might be a good moment, to "reset" a not properly working bridge. Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay). - ## Importing To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server): diff --git a/docs/importing-synapse-media-store.md b/docs/importing-synapse-media-store.md index 4b6c1d336..dd1fe9671 100644 --- a/docs/importing-synapse-media-store.md +++ b/docs/importing-synapse-media-store.md @@ -2,7 +2,6 @@ Run this if you'd like to import your `media_store` files from a previous installation of Synapse. - ## Prerequisites Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay). @@ -13,7 +12,6 @@ As an alternative, you can perform a manual restore using the [AWS CLI tool](htt **Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac. - ## Importing Run this command (make sure to replace `` with a path on your server): diff --git a/docs/importing-synapse-sqlite.md b/docs/importing-synapse-sqlite.md index b850cfa64..2453e8cfc 100644 --- a/docs/importing-synapse-sqlite.md +++ b/docs/importing-synapse-sqlite.md @@ -6,7 +6,6 @@ While this playbook only supports running Synapse in combination with PostgreSQL If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you. - ## Prerequisites Before doing the actual import: diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 586701da2..2847e6b1f 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -21,7 +21,6 @@ To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/j sudo journalctl -fu matrix-synapse ``` - ## Increasing Synapse logging 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`. diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index 9960e7e90..d652bac0b 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -30,7 +30,6 @@ You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;` **Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql). - ## Vacuuming PostgreSQL Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html). @@ -50,7 +49,6 @@ Example playbook invocations: - `just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services - `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times - ## Backing up PostgreSQL To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md). @@ -70,7 +68,6 @@ If you are using an [external Postgres server](configuring-playbook-external-pos Restoring a backup made this way can be done by [importing it](importing-postgres.md). - ## Upgrading PostgreSQL Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you. @@ -96,7 +93,6 @@ If you have plenty of space in `/tmp` and would rather avoid gzipping, you can e **All databases, roles, etc. on the Postgres server are migrated**. - ## Tuning PostgreSQL PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process. diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index 91e79661c..749e9deba 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -24,7 +24,6 @@ Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql). - ## Compressing state with rust-synapse-compress-state [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database. @@ -45,7 +44,6 @@ By default, all rooms with more than `100000` state group rows will be compresse After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql). - ## Browse and manipulate the database When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs. diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index 12016cb96..d60eee5e4 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -20,7 +20,6 @@ Below, we describe 2 ways to generate an access token for a user - using [Elemen ![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png) - ## Obtain an access token via curl You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login): diff --git a/docs/registering-users.md b/docs/registering-users.md index 592d88b93..7d6f6474f 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -11,7 +11,6 @@ Table of contents: - [Enabling public user registration](#enabling-public-user-registration) - [Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user) - ## Registering users manually **Notes**: @@ -83,19 +82,16 @@ This `register-user` script actually invokes the `mas-cli manage register-user` ⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information. - ## Managing users via a Web UI To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md). ⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information. - ## Letting certain users register on your private server If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md). - ## Enabling public user registration To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/uninstalling.md b/docs/uninstalling.md index 73a414ede..717037cee 100644 --- a/docs/uninstalling.md +++ b/docs/uninstalling.md @@ -6,17 +6,14 @@ - If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**. - ----------------- - ## Uninstalling using a script Installing places a `/matrix/bin/remove-all` script on the server. You can run it to to have it uninstall things for you automatically (see below). **Use with caution!** - ## Uninstalling manually If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself): @@ -32,5 +29,3 @@ If you prefer to uninstall manually, run these commands (most are meant to be ex - uninstall Docker itself, if necessary - delete the `/matrix` directory (`rm -rf /matrix`) - - diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index a95cf0ddd..9f5e0463a 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -14,7 +14,6 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HE **You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`. - ## Option 2 (if you are using an external Postgres server): You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation): @@ -31,7 +30,6 @@ UPDATE users SET password_hash = '' WHERE name = '@someone:exampl where `` is the hash returned by the docker command above. - ## Option 3: Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password From a31400ed4a5076aad3d057ae9e4edf9b09a0cb3b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 1 Dec 2024 11:57:41 +0900 Subject: [PATCH 041/952] Adjust blank lines: add ones Signed-off-by: Suguru Hirahara --- docs/ansible.md | 2 ++ docs/configuring-captcha.md | 1 + docs/configuring-playbook-bridge-beeper-linkedin.md | 2 ++ docs/configuring-playbook-bridge-hookshot.md | 2 ++ docs/configuring-playbook-bridge-mautrix-facebook.md | 2 ++ docs/configuring-playbook-bridge-mautrix-instagram.md | 2 ++ docs/configuring-playbook-bridge-mautrix-meta-instagram.md | 1 + docs/configuring-playbook-bridge-mautrix-meta-messenger.md | 1 + docs/configuring-playbook-bridge-mautrix-signal.md | 3 +++ docs/configuring-playbook-bridge-mautrix-telegram.md | 2 ++ docs/configuring-playbook-email.md | 1 + docs/configuring-playbook-jitsi.md | 1 + docs/configuring-playbook-matrix-media-repo.md | 1 + docs/configuring-playbook-prometheus-grafana.md | 1 + docs/configuring-playbook-user-verification-service.md | 2 ++ docs/importing-postgres.md | 2 ++ docs/maintenance-and-troubleshooting.md | 1 + docs/maintenance-postgres.md | 3 +-- docs/updating-users-passwords.md | 2 ++ 19 files changed, 30 insertions(+), 2 deletions(-) diff --git a/docs/ansible.md b/docs/ansible.md index a53289795..55aa26248 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -92,9 +92,11 @@ Finally, you execute `ansible-playbook ...` commands as per normal now. If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`). To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it ...` command), run: + ```sh apk add sshpass ``` + Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command. #### Resolve directory ownership issues diff --git a/docs/configuring-captcha.md b/docs/configuring-captcha.md index ad411ddde..a4a16a1dc 100644 --- a/docs/configuring-captcha.md +++ b/docs/configuring-captcha.md @@ -1,6 +1,7 @@ (Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md)) # Overview + Captcha can be enabled for this home server. This file explains how to do that. The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead. diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 02b4d5fed..5c876b862 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -15,6 +15,7 @@ matrix_beeper_linkedin_enabled: true There are some additional things you may wish to configure about the bridge before you continue. Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: + ```yaml matrix_beeper_linkedin_configuration_extension_yaml: | bridge: @@ -24,6 +25,7 @@ matrix_beeper_linkedin_configuration_extension_yaml: | ``` If you would like to be able to administrate the bridge from your account it can be configured like this: + ```yaml matrix_beeper_linkedin_configuration_extension_yaml: | bridge: diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 019ffa283..f8a83df1d 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -70,6 +70,7 @@ The GitHub bridge requires you to install a private key file. This can be done i - use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server. To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following additional configuration: + ```yaml aux_file_definitions: - dest: "{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}" @@ -78,6 +79,7 @@ aux_file_definitions: owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" ``` + For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml). ### Provisioning API diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 848c1c64a..e485f3dbd 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -23,6 +23,7 @@ matrix_mautrix_facebook_enabled: true There are some additional things you may wish to configure about the bridge before you continue. Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: + ```yaml matrix_mautrix_facebook_configuration_extension_yaml: | bridge: @@ -32,6 +33,7 @@ matrix_mautrix_facebook_configuration_extension_yaml: | ``` If you would like to be able to administrate the bridge from your account it can be configured like this: + ```yaml matrix_mautrix_facebook_configuration_extension_yaml: | bridge: diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index d57b9346f..76022f907 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -17,6 +17,7 @@ matrix_mautrix_instagram_enabled: true There are some additional things you may wish to configure about the bridge before you continue. Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: + ```yaml matrix_mautrix_instagram_configuration_extension_yaml: | bridge: @@ -26,6 +27,7 @@ matrix_mautrix_instagram_configuration_extension_yaml: | ``` If you would like to be able to administrate the bridge from your account it can be configured like this: + ```yaml # The easy way. The specified Matrix user ID will be made an admin of all bridges matrix_admin: "@YOUR_USERNAME:{{ matrix_domain }}" diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index 1c1f1e793..4305a45e8 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -48,6 +48,7 @@ Different levels of permission can be granted to users: The permissions are following the sequence: nothing < `relay` < `user` < `admin`. The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this: + ```yaml matrix_mautrix_meta_instagram_bridge_permissions_default: '*': relay diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index bf21c3008..ef3c8f35c 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -61,6 +61,7 @@ Different levels of permission can be granted to users: The permissions are following the sequence: nothing < `relay` < `user` < `admin`. The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this: + ```yaml matrix_mautrix_meta_messenger_bridge_permissions_default: '*': relay diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index dea39e730..7c12efb5b 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -41,6 +41,7 @@ Different levels of permission can be granted to users: The permissions are following the sequence: nothing < relay < user < admin. The default permissions are set as follows: + ```yaml permissions: '*': relay @@ -48,6 +49,7 @@ permissions: ``` If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file: + ```yaml matrix_mautrix_signal_configuration_extension_yaml: | bridge: @@ -58,6 +60,7 @@ matrix_mautrix_signal_configuration_extension_yaml: | This will add the admin permission to the specific user, while keeping the default permissions. In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file: + ```yaml matrix_mautrix_signal_bridge_permissions: '@ADMIN:example.com': admin diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index b97fcbe77..e32f5d181 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -52,6 +52,7 @@ matrix_mautrix_telegram_configuration_extension_yaml: | ``` You might also want to give permissions to administrate the bot: + ```yaml matrix_mautrix_telegram_configuration_extension_yaml: | bridge: @@ -62,6 +63,7 @@ matrix_mautrix_telegram_configuration_extension_yaml: | More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410 If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration: + ```yaml matrix_mautrix_telegram_filter_mode: whitelist ``` diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 51615e752..b10dd8224 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -31,6 +31,7 @@ exim_relay_relay_auth_password: "some-password" **Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**. ### Configuations for sending emails using Sendgrid + An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`. The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`. diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 50cb2594e..547c108c0 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -169,6 +169,7 @@ By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-vid There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start` For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example: + ```INI [jitsi_jvb_servers] ansible_host= diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 161965d95..96981ade8 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -30,6 +30,7 @@ By default, the media-repo will use the local filesystem for data storage. You c ## Configuring the media-repo Additional common configuration options: + ```yaml # The postgres database pooling options diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index f4786f807..ccc329c5b 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -120,6 +120,7 @@ Name | Description If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`. The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this: + ```yaml scrape_configs: - job_name: 'synapse' diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 12ece9f02..d1ffde99d 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -68,6 +68,7 @@ matrix_user_verification_service_uvs_auth_token: "TOKEN" In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token. ### (Optional) Disable Auth + Authorization is enabled by default. To disable set ```yaml @@ -108,6 +109,7 @@ The configuration variable `UVS_LOG_LEVEL` can be set to: - debug ## TLS Certificate Checking + If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message: > message: 'No response received: [object Object]', diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index 06ea65ea6..d7871a78a 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -32,6 +32,7 @@ just run-tags import-postgres \ ## Troubleshooting ### Table Ownership + A table ownership issue can occur if you are importing from a Synapse installation which was both: - migrated from SQLite to Postgres, and @@ -84,6 +85,7 @@ In this case you can use the command suggested in the import task to clear the d Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc. If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database. + ``` "ERROR: role synapse does not exist" ``` diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 2847e6b1f..673c89859 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -3,6 +3,7 @@ ## How to see the current status of your services You can check the status of your services by using `systemctl status`. Example: + ```sh sudo systemctl status matrix-synapse diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index d652bac0b..c2b0b3020 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -88,8 +88,7 @@ The auto-upgrade-backup directory stays around forever, until you **manually dec As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars="postgres_dump_dir=/directory/to/dump/here"` -To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. -If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars="postgres_dump_name=matrix-postgres-dump.sql"` +To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars="postgres_dump_name=matrix-postgres-dump.sql"` **All databases, roles, etc. on the Postgres server are migrated**. diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index 9f5e0463a..3dcc71e19 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -39,7 +39,9 @@ This requires an [access token](obtaining-access-tokens.md) from a server admin If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse). ### Example: + To set @user:example.com's password to `correct_horse_battery_staple` you could use this curl command: + ```sh curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@user:example.com?access_token=MDA...this_is_my_access_token ``` From dd31bf0a0a2c881373bc2d0f56a57c390bbaff59 Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 2 Dec 2024 01:23:29 +0200 Subject: [PATCH 042/952] synapse-admin: remove deprecated vars, introduce matrix_synapse_admin_configuration_extension_json_auto --- roles/custom/matrix-synapse-admin/defaults/main.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 8617dbefa..58ed20551 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -149,7 +149,6 @@ matrix_synapse_admin_path_prefix: /synapse-admin matrix_synapse_admin_configuration_default: restrictBaseUrl: "{{ matrix_synapse_admin_config_restrictBaseUrl }}" asManagedUsers: "{{ matrix_synapse_admin_config_asManagedUsers }}" - supportURL: "{{ matrix_synapse_admin_config_supportURL }}" menu: "{{ matrix_synapse_admin_config_menu }}" # Your custom JSON configuration for synapse-admin should go to `matrix_synapse_admin_configuration_extension_json`. @@ -169,7 +168,10 @@ matrix_synapse_admin_configuration_default: # } matrix_synapse_admin_configuration_extension_json: '{}' -matrix_synapse_admin_configuration_extension: "{{ matrix_synapse_admin_configuration_extension_json | from_json if matrix_synapse_admin_configuration_extension_json | from_json is mapping else {} }}" +# This is similar to `matrix_synapse_admin_configuration_extension_json`, but intended for use by playbook or group vars +matrix_synapse_admin_configuration_extension_json_auto: {} + +matrix_synapse_admin_configuration_extension: "{{ matrix_synapse_admin_configuration_extension_json_auto | combine(matrix_synapse_admin_configuration_extension_json | from_json if matrix_synapse_admin_configuration_extension_json | from_json is mapping else {}, recursive=True) }}" # Holds the final synapse-admin configuration (a combination of the default and its extension). # You most likely don't need to touch this variable. Instead, see `matrix_synapse_admin_configuration_default`. @@ -194,10 +196,6 @@ matrix_synapse_admin_config_restrictBaseUrl: "{{ [matrix_homeserver_url] }}" # # ] matrix_synapse_admin_config_menu: [] -# Controls the supportURL configuration setting, which, if defined, replaces the default link to the Synapse Admin GitHub repository. -# DEPRECATED: use matrix_synapse_admin_config_menu instead (migrated automatically). -matrix_synapse_admin_config_supportURL: '' # noqa var-naming - # Controls the asManagedUsers configuration setting (managed by playbook), which, if defined, # restricts modifications of the specified users (e.g., bridge-managed). # You should use JS regex syntax to match the user IDs. From bd6db6573131ea38a729d7598b5f2c04113af233 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 13:55:23 +0900 Subject: [PATCH 043/952] Adjust blank lines: *.md files outside of docs/ directory Double blank lines are preserved for the first level headings on CHANGELOG.md. Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 42 ------------------- README.md | 8 ---- .../caddy2-in-container/README.md | 1 - examples/reverse-proxies/caddy2/README.md | 2 - .../nginx-proxy-manager/README.md | 2 - examples/reverse-proxies/nginx/README.md | 2 - 6 files changed, 57 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 24663068f..8ccbdf71c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -163,7 +163,6 @@ It's designed as a more private and [✨ featureful](https://github.com/etkecc/b To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page. - ## Switching synapse-admin to etke.cc's fork The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software. @@ -252,7 +251,6 @@ For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details. - ## Traefik v3 and HTTP/3 are here now **TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it. @@ -273,7 +271,6 @@ If you've tweaked any of this playbook's `_path_prefix` variables and made them If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand. - ### HTTP/3 is enabled by default In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. @@ -347,7 +344,6 @@ When generating new webhooks, you should start seeing the new URLs being used. However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs. - # 2024-06-22 ## The maubot user is now managed by the playbook @@ -394,7 +390,6 @@ keydb_enabled: false ``` - # 2024-03-24 ## Initial work on IPv6 support @@ -564,7 +559,6 @@ Due to complexity and the playbook's flexibility (trying to accommodate a mix of After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`. - ### Going Traefik-native and cutting out all middlemen In our new setup, you'll see the bare minimum number of reverse-proxies. @@ -574,7 +568,6 @@ In most cases, there's only Traefik and all services being registered directly w This reduces "network" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime. - ### Traefik now has an extra job Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job. @@ -600,21 +593,18 @@ People running the default Traefik setup do not need to do anything to make Trae You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a "simpler" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended. - ### People managing their own Traefik instance need to do minor changes This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes. Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details. - ### People fronting Traefik with another reverse proxy need to do minor changes We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job). - ### Supported reverse proxy types are now fewer This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`). @@ -636,7 +626,6 @@ If you were using these values as a way to stay away from Traefik, you now have - (recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - (not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually - ### Container networking changes Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt. @@ -651,7 +640,6 @@ Carrying out these container networking changes necessitated modifying many comp We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much. - ### Metrics exposure changes This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server. @@ -664,7 +652,6 @@ From now on, there are new variables for doing roughly the same - `matrix_metric The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything! - ### Matrix static files As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files. @@ -673,7 +660,6 @@ All of this has been extracted into a new `matrix-static-files` Ansible role tha The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names. - ### A note on performance Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better. @@ -688,7 +674,6 @@ Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hi If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all. - ### Migration procedure The updated playbook will automatically perform some migration tasks for you: @@ -710,7 +695,6 @@ We don't recommend changing these variables and suppressing warnings, unless you **Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically. - ### Conclusion Thousands of lines of code were changed across hundreds of files. @@ -1238,7 +1222,6 @@ Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle] Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience. - ### Where we're going in the near future? The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point. @@ -1271,7 +1254,6 @@ Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.c Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix). - ## Draupnir moderation tool (bot) support Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer. @@ -1311,7 +1293,6 @@ This, however, means that **you will need to ensure these ports are open** in yo Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network. - ## (Backward Compatibility) Tightening Coturn security can lead to connectivity issues **TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it. @@ -1559,7 +1540,6 @@ This is not just for initial installations. Users with existing files (stored in To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation. - ## Synapse container image customization support We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/). @@ -1773,7 +1753,6 @@ If you still need bridging to [Skype](https://www.skype.com/), consider switchin If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal. - ## signald (0.19.0+) upgrade requires data migration In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`. @@ -1905,7 +1884,6 @@ Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started. - ## (Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading: @@ -2021,7 +1999,6 @@ matrix_homeserver_implementation: dendrite We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc! - ## Honoroit bot support Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot. @@ -2144,7 +2121,6 @@ Thanks to [foxcris](https://github.com/foxcris), the playbook can now make autom Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md). - # 2021-04-03 ## Mjolnir moderation tool (bot) support @@ -2471,7 +2447,6 @@ We've removed support for the unmaintained [synapse-janitor](https://github.com/ If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details. - ## Docker 20.10 is here (No need to do anything special in relation to this. Just something to keep in mind) @@ -2999,7 +2974,6 @@ This greatly reduces the number of log messages that are being logged, leading t If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging). - # 2019-07-08 ## Synapse Maintenance docs and synapse-janitor support are available @@ -3010,7 +2984,6 @@ There's a new documentation page about [Synapse maintenance](./docs/maintenance- Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you. - ## (BC Break) Rename run control variables Some internal playbook control variables have been renamed. @@ -3222,7 +3195,6 @@ If you're using your own Synapse instance (especially one not running in a conta Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers. - ## Bridges are now separate from the Synapse role Bridges are no longer part of the `matrix-synapse` role. @@ -3230,7 +3202,6 @@ Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`). These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook). - ## Renaming inconsistently-named Synapse variables For better consistency, the following variables have been renamed: @@ -3311,7 +3282,6 @@ If you don't have a dedicated server for your base domain and want to set up [Se It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page. - ## (BC break) matrix-nginx-proxy data variable renamed `matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`. @@ -3435,7 +3405,6 @@ Containers are given write access only to the directories they need to write to. A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you. - ## matrix-mailer is now based on Exim, not Postfix While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. @@ -3555,7 +3524,6 @@ For people who use Let's Encrypt (mostly everyone, since it's the default), you' - before: `host_specific_matrix_ssl_support_email` - after: `host_specific_matrix_ssl_lets_encrypt_support_email` - ## (BC Break) mxisd upgrade with multiple base DN support mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base). @@ -3676,7 +3644,6 @@ The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/18 If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql). - ## (BC Break) Renaming playbook variables Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit. @@ -3766,7 +3733,6 @@ The playbook now helps you set up [service discovery](https://matrix.org/docs/sp Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md). - ## (BC Break) Renaming playbook variables The following playbook variables were renamed: @@ -3783,19 +3749,16 @@ The playbook now supports bridging with [Telegram](https://telegram.org/) by ins Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md). - ## Events cache size increase and configurability for Matrix Synapse The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable. Previously, this value was hardcoded to `"10K"`. From now on, a more reasonable default of `"100K"` is used. - ## Password-peppering support for Matrix Synapse The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords. - ## Statistics-reporting support for Matrix Synapse There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy. @@ -3856,7 +3819,6 @@ The playbook can now install and configure [matrix-synapse-rest-auth](https://gi Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md). - ## Compression improvements Shifted Matrix Synapse compression from happening in the Matrix Synapse, @@ -3865,7 +3827,6 @@ to happening in the nginx proxy that's in front of it. Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB. - ## Disabling some unnecessary Synapse services The following services are not necessary, so they have been disabled: @@ -3896,7 +3857,6 @@ With this, Matrix Synapse is able to send email notifications for missed message # 2018-08-08 - ## (BC Break) Renaming playbook variables The following playbook variables were renamed: @@ -3912,13 +3872,11 @@ The following playbook variables were renamed: If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names. - ## Renaming Ansible playbook tag The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`. - ## Docker container linking Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network. diff --git a/README.md b/README.md index 65ffe14d2..dc8c7ddbe 100644 --- a/README.md +++ b/README.md @@ -63,8 +63,6 @@ Web clients for Matrix that you can host on your own domains. | [Cinny](https://github.com/ajbura/cinny) | ❌ | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-cinny.md) | | [SchildiChat Web](https://schildi.chat/) | ❌ | Based on Element Web, with a more traditional instant messaging experience | [Link](docs/configuring-playbook-client-schildichat-web.md) | - - ### Server Components Services that run on the server to make the various parts of your installation work. @@ -79,7 +77,6 @@ Services that run on the server to make the various parts of your installation w | [ma1sd](https://github.com/ma1uta/ma1sd) | ❌ | Matrix Identity Server | [Link](docs/configuring-playbook-ma1sd.md) | [ddclient](https://github.com/linuxserver/docker-ddclient) | ❌ | Dynamic DNS | [Link](docs/configuring-playbook-dynamic-dns.md) | - ### Authentication Extend and modify how users are authenticated on your homeserver. @@ -94,7 +91,6 @@ Extend and modify how users are authenticated on your homeserver. | [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS) | ❌ | Service to verify details of a user based on an Open ID token | [Link](docs/configuring-playbook-user-verification-service.md) | | [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced) | ❌ | A spam checker module | [Link](docs/configuring-playbook-synapse-simple-antispam.md) | - ### File Storage Use alternative file storage to the default `media_store` folder. @@ -140,7 +136,6 @@ Bridges can be used to connect your Matrix installation with third-party communi | [Email2Matrix](https://github.com/devture/email2matrix) | ❌ | Bridge for relaying emails to Matrix rooms | [Link](docs/configuring-playbook-email2matrix.md) | | [Postmoogle](https://github.com/etkecc/postmoogle) | ❌ | Email to Matrix bridge | [Link](docs/configuring-playbook-bridge-postmoogle.md) | - ### Bots Bots provide various additional functionality to your installation. @@ -187,14 +182,12 @@ Various services that don't fit any other categories. | [Sygnal](https://github.com/matrix-org/sygnal) | ❌ | Push gateway | [Link](docs/configuring-playbook-sygnal.md) | | [ntfy](https://ntfy.sh) | ❌ | Push notifications server | [Link](docs/configuring-playbook-ntfy.md) | - ## 🆕 Changes This playbook evolves over time, sometimes with backward-incompatible changes. When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new. - ## 🆘 Support - Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) @@ -203,7 +196,6 @@ When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up w - GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues) - ## 🤝 Related You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md)). diff --git a/examples/reverse-proxies/caddy2-in-container/README.md b/examples/reverse-proxies/caddy2-in-container/README.md index 51881ac60..3a87bf234 100644 --- a/examples/reverse-proxies/caddy2-in-container/README.md +++ b/examples/reverse-proxies/caddy2-in-container/README.md @@ -4,7 +4,6 @@ This directory contains a sample config that shows you how to front the integrat **Note**: if you're running Caddy on the host itself (not in a container), refer to the [caddy2](../caddy2/README.md) example instead. - ## Prerequisite configuration To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`). diff --git a/examples/reverse-proxies/caddy2/README.md b/examples/reverse-proxies/caddy2/README.md index 29693edc6..dcc1538af 100644 --- a/examples/reverse-proxies/caddy2/README.md +++ b/examples/reverse-proxies/caddy2/README.md @@ -2,12 +2,10 @@ This directory contains a sample config that shows you how to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with your own [Caddy](https://caddyserver.com/) reverse-proxy. - ## Prerequisite configuration To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`). - ## Using the Caddyfile You can either just use the [Caddyfile](Caddyfile) directly or append its content to your own Caddyfile. diff --git a/examples/reverse-proxies/nginx-proxy-manager/README.md b/examples/reverse-proxies/nginx-proxy-manager/README.md index 735901c3f..e90289e9c 100644 --- a/examples/reverse-proxies/nginx-proxy-manager/README.md +++ b/examples/reverse-proxies/nginx-proxy-manager/README.md @@ -4,14 +4,12 @@ Similar to standard nginx, [Nginx Proxy Manager](https://nginxproxymanager.com/) This page summarizes how to use Nginx Proxy Manager (NPM) to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver. - ## Prerequisite configuration To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`). If Matrix federation is enabled, then you will need to make changes to [NPM's Docker configuration](https://nginxproxymanager.com/guide/#quick-setup). By default NPM already exposes ports `80` and `443`, but you would also need to **additionally expose the Matrix Federation port** (as it appears on the public side): `8448`. - ## Using Nginx Proxy Manager You'll need to create two proxy hosts in NPM for Matrix web and federation traffic. diff --git a/examples/reverse-proxies/nginx/README.md b/examples/reverse-proxies/nginx/README.md index dfe53057c..1fe76340d 100644 --- a/examples/reverse-proxies/nginx/README.md +++ b/examples/reverse-proxies/nginx/README.md @@ -2,12 +2,10 @@ This directory contains a sample config that shows you how to use the [nginx](https://nginx.org/) webserver to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with another reverse-proxy. - ## Prerequisite configuration To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`). - ## Using the nginx configuration Copy the [matrix.conf](matrix.conf) file to your nginx server's filesystem, modify it to your needs and include it in your nginx configuration (e.g. `include /path/to/matrix.conf;`). From 78bb07877c76ebce28e1b6e16bba0c54f6de6cba Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 13:58:07 +0900 Subject: [PATCH 044/952] Update CHANGELOG.md: remove a redundant asterisk Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8ccbdf71c..285e27fb5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -339,7 +339,7 @@ To avoid future problems, we've [reconfigured](https://github.com/spantaleev/mat When generating new webhooks, you should start seeing the new URLs being used. -**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work***, so your webhooks will not break just yet. +**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet. However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs. From a07130e46ceb558c0b88973f1a746608db04c7d4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 14:22:38 +0900 Subject: [PATCH 045/952] Edit docs/maintenance-upgrading-services.md: add details about the difference between install-all and setup-all in speed Also: remove the redundant description about that difference from description about the "just" shortcuts. Signed-off-by: Suguru Hirahara --- docs/maintenance-upgrading-services.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md index a59bf5940..ca1ea78f1 100644 --- a/docs/maintenance-upgrading-services.md +++ b/docs/maintenance-upgrading-services.md @@ -47,9 +47,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any. -- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` +- Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information. - `just install-all` 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 these shortcuts run the `ensure-matrix-users-created` tag too. +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too. - See [this page on the playbook tags](playbook-tags.md) for more information about those tags. From e8548e0016ff79b99c9fc99e226e11cf4c489974 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 14:29:44 +0900 Subject: [PATCH 046/952] Mention how much "just install-all" is faster than "just setup-all" This way, the "installing" sections would cover from beginners to advanced (professional) readers. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 2 +- docs/configuring-playbook-appservice-double-puppet.md | 2 +- docs/configuring-playbook-appservice-draupnir-for-all.md | 2 +- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bot-buscarron.md | 2 +- docs/configuring-playbook-bot-chatgpt.md | 2 +- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bot-honoroit.md | 2 +- docs/configuring-playbook-bot-matrix-registration-bot.md | 2 +- docs/configuring-playbook-bot-matrix-reminder-bot.md | 2 +- docs/configuring-playbook-bot-maubot.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- docs/configuring-playbook-bridge-appservice-discord.md | 2 +- docs/configuring-playbook-bridge-appservice-irc.md | 2 +- docs/configuring-playbook-bridge-appservice-kakaotalk.md | 2 +- docs/configuring-playbook-bridge-appservice-slack.md | 2 +- docs/configuring-playbook-bridge-appservice-webhooks.md | 2 +- docs/configuring-playbook-bridge-beeper-linkedin.md | 2 +- docs/configuring-playbook-bridge-go-skype-bridge.md | 2 +- docs/configuring-playbook-bridge-heisenbridge.md | 2 +- docs/configuring-playbook-bridge-matrix-bridge-sms.md | 2 +- docs/configuring-playbook-bridge-mautrix-discord.md | 2 +- docs/configuring-playbook-bridge-mautrix-facebook.md | 2 +- docs/configuring-playbook-bridge-mautrix-gmessages.md | 2 +- docs/configuring-playbook-bridge-mautrix-googlechat.md | 2 +- docs/configuring-playbook-bridge-mautrix-hangouts.md | 2 +- docs/configuring-playbook-bridge-mautrix-instagram.md | 2 +- docs/configuring-playbook-bridge-mautrix-meta-instagram.md | 2 +- docs/configuring-playbook-bridge-mautrix-meta-messenger.md | 2 +- docs/configuring-playbook-bridge-mautrix-signal.md | 2 +- docs/configuring-playbook-bridge-mautrix-slack.md | 2 +- docs/configuring-playbook-bridge-mautrix-telegram.md | 2 +- docs/configuring-playbook-bridge-mautrix-twitter.md | 2 +- docs/configuring-playbook-bridge-mautrix-whatsapp.md | 2 +- docs/configuring-playbook-bridge-mautrix-wsproxy.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-discord.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-groupme.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-instagram.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-slack.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-steam.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-twitter.md | 2 +- docs/configuring-playbook-bridge-postmoogle.md | 2 +- docs/configuring-playbook-bridge-wechat.md | 2 +- docs/configuring-playbook-cactus-comments.md | 2 +- docs/configuring-playbook-client-cinny.md | 2 +- docs/configuring-playbook-client-element-web.md | 2 +- docs/configuring-playbook-client-hydrogen.md | 2 +- docs/configuring-playbook-client-schildichat-web.md | 2 +- docs/configuring-playbook-dendrite.md | 2 +- docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-dynamic-dns.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-ma1sd.md | 2 +- docs/configuring-playbook-matrix-authentication-service.md | 2 +- docs/configuring-playbook-matrix-ldap-registration-proxy.md | 2 +- docs/configuring-playbook-matrix-registration.md | 2 +- docs/configuring-playbook-mautrix-bridges.md | 2 +- docs/configuring-playbook-ntfy.md | 2 +- docs/configuring-playbook-pantalaimon.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- docs/configuring-playbook-prometheus-grafana.md | 2 +- docs/configuring-playbook-prometheus-nginxlog.md | 2 +- docs/configuring-playbook-prometheus-postgres.md | 2 +- docs/configuring-playbook-rageshake.md | 2 +- docs/configuring-playbook-rest-auth.md | 2 +- docs/configuring-playbook-riot-web.md | 2 +- docs/configuring-playbook-shared-secret-auth.md | 2 +- docs/configuring-playbook-sliding-sync-proxy.md | 2 +- docs/configuring-playbook-sygnal.md | 2 +- docs/configuring-playbook-synapse-admin.md | 2 +- docs/configuring-playbook-synapse-auto-compressor.md | 2 +- docs/configuring-playbook-synapse-usage-exporter.md | 2 +- docs/faq.md | 2 +- docs/installing.md | 2 +- docs/registering-users.md | 2 +- 78 files changed, 78 insertions(+), 78 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 43875bb1e..e92361ec6 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -88,7 +88,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index 5f565c5da..38b5b05b1 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -29,7 +29,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 28c231dd9..dcbc57853 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -60,7 +60,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index abe8a55c7..fc933d9e2 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -80,7 +80,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Manually start a backup diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 4e09d5bad..725c53a5a 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -377,7 +377,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 7790558fd..ee32ad90b 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -69,7 +69,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index c04a0ddf3..da963bdff 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -66,7 +66,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index f26337079..4c230297c 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -122,7 +122,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index a34a7dc01..17580e9b1 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -230,7 +230,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index d977df5b2..a6f767302 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -60,7 +60,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 6f2522c58..933ef52ab 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -44,7 +44,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index 3d9c9c232..518a9e53a 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -38,7 +38,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index bcc68b3d6..b1ffb08da 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -62,7 +62,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index e3e7cf6cd..7036a1180 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -124,7 +124,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password. diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index b8b73e08b..604356467 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -43,7 +43,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Self-Service Bridging (Manual) diff --git a/docs/configuring-playbook-bridge-appservice-irc.md b/docs/configuring-playbook-bridge-appservice-irc.md index 0a07b8588..2027d9822 100644 --- a/docs/configuring-playbook-bridge-appservice-irc.md +++ b/docs/configuring-playbook-bridge-appservice-irc.md @@ -75,7 +75,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 34e42bc52..4d7614eb6 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -46,7 +46,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index db2921315..c86e83def 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -78,7 +78,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index e20d3caa6..863593bfe 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -39,7 +39,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 5c876b862..e05a75c77 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -50,7 +50,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index c96242185..d6f5857ee 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -27,7 +27,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index b85fab585..473df643a 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -62,7 +62,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index d445ee0e7..7a2deeec7 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -46,7 +46,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index e0107ec07..6dac6cbfe 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -54,7 +54,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index e485f3dbd..f892371cf 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -70,7 +70,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index e9a4fbc8b..df3824e7a 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -33,7 +33,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 1f5b1760d..a44f94216 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -33,7 +33,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index 83aa016f7..0df76e1bd 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -35,7 +35,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 76022f907..65793e4e2 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -57,7 +57,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index 4305a45e8..83d73062f 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -82,7 +82,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index ef3c8f35c..1825751df 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -95,7 +95,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index 7c12efb5b..4f3780cc4 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -84,7 +84,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 3459d8c34..1794d9b72 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -56,7 +56,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index e32f5d181..34f385027 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -35,7 +35,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index 93eaadb16..b73a42ec9 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -35,7 +35,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index a70f40d21..d8af2f622 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -49,7 +49,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index a7363c190..84b247acb 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -54,7 +54,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index b886f206b..9ecdd5dab 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -31,7 +31,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md index 3b928dd26..72857aa9a 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md +++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md @@ -27,7 +27,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md index da75cbb0c..88b35d245 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md +++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md @@ -27,7 +27,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index c9888729e..3c4abe31b 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -36,7 +36,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md index 5ab9655ae..28c252a07 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-steam.md +++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md @@ -27,7 +27,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md index 5d43b44b0..9c275533e 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md +++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md @@ -38,7 +38,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index a4cf9f7ff..a7ce96ba4 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -61,7 +61,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password. diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index 98451bf00..7e96cab79 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -27,7 +27,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index e39da3292..2b7911810 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -76,7 +76,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index d75a2ef72..d943819be 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -50,4 +50,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 989c41c9b..08ad82448 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -77,4 +77,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index f63bf4eea..04baa5c8b 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -48,4 +48,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 670699d7c..a9064e250 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -76,4 +76,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index fdcb830f2..441872d73 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -41,4 +41,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index cd34fd5cd..6566015d8 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -80,7 +80,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots. diff --git a/docs/configuring-playbook-dynamic-dns.md b/docs/configuring-playbook-dynamic-dns.md index 48b0e6b61..7108e8b65 100644 --- a/docs/configuring-playbook-dynamic-dns.md +++ b/docs/configuring-playbook-dynamic-dns.md @@ -34,7 +34,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Additional Reading diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index f91af766c..63700e955 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -56,7 +56,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password. diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 547c108c0..dcb0a4232 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -276,7 +276,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 14376d42d..5a3aa6e16 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -138,7 +138,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Troubleshooting diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index e81efd78a..3dd34ae95 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -289,7 +289,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide. diff --git a/docs/configuring-playbook-matrix-ldap-registration-proxy.md b/docs/configuring-playbook-matrix-ldap-registration-proxy.md index f38fd62a8..5f58ead69 100644 --- a/docs/configuring-playbook-matrix-ldap-registration-proxy.md +++ b/docs/configuring-playbook-matrix-ldap-registration-proxy.md @@ -43,4 +43,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index a55a50b73..73168fdb8 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -60,7 +60,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md index 126fa5f3a..a7a2bde12 100644 --- a/docs/configuring-playbook-mautrix-bridges.md +++ b/docs/configuring-playbook-mautrix-bridges.md @@ -106,7 +106,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Set up Double Puppeting diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index 9256697d7..98eb703c6 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -58,7 +58,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index 8b0d54589..054fbcc32 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -27,4 +27,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 58d719f8f..165609d0c 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -35,4 +35,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index ccc329c5b..edd4526cb 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -64,7 +64,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## What does it do? diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 296fad121..ed90cb0aa 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -31,7 +31,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Docker Image Compatibility diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md index c3c05653c..74d3eda4f 100644 --- a/docs/configuring-playbook-prometheus-postgres.md +++ b/docs/configuring-playbook-prometheus-postgres.md @@ -21,7 +21,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## What does it do? diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index 292c17e5f..88bc3fd61 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -60,7 +60,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index 2a22841c5..e31957f47 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -35,4 +35,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index 398a0a444..e008a3f89 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -36,4 +36,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index fb63001e4..f1396ab83 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -34,4 +34,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index b0a9c4a52..2cd9bcca4 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -47,7 +47,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ### External databases diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index fc16c7911..9d92cda36 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -86,7 +86,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index ffb2b4749..dbdbafcd6 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -56,7 +56,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 3e98fd9d1..3ae325934 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -25,7 +25,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. ## Usage diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 0526becf5..db6264cb8 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -59,4 +59,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -`just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/faq.md b/docs/faq.md index c60d5e403..8b5165379 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -279,7 +279,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user identifiers will be like `@user:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`. diff --git a/docs/installing.md b/docs/installing.md index 0abfe0682..71b3c65c7 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -154,6 +154,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input. -For example, `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. +For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. You can learn about the shortcut commands on this page: [Running `just` commands](just.md) diff --git a/docs/registering-users.md b/docs/registering-users.md index 7d6f6474f..210c16838 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -119,7 +119,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - `just install-all` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md). From 34d1586f25413e758a16b0f11e59d76bc6fa4e77 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 2 Dec 2024 19:26:08 +0200 Subject: [PATCH 047/952] Actually make use of the matrix_mautrix_discord_bridge_double_puppet_server_map variable --- .../matrix-bridge-mautrix-discord/defaults/main.yml | 13 +++++++++++-- .../templates/config.yaml.j2 | 3 +-- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index 5e8ee7f53..fce3ef1f3 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -104,9 +104,18 @@ matrix_mautrix_discord_bridge_login_shared_secret_map: "{{ matrix_mautrix_discor matrix_mautrix_discord_bridge_login_shared_secret_map_auto: {} matrix_mautrix_discord_bridge_login_shared_secret_map_custom: {} + # Servers to always allow double puppeting from -matrix_mautrix_discord_bridge_double_puppet_server_map: - "{{ matrix_mautrix_discord_homeserver_domain : matrix_mautrix_discord_homeserver_address }}" +matrix_mautrix_discord_bridge_double_puppet_server_map: "{{ matrix_mautrix_discord_bridge_double_puppet_server_map_default | combine(matrix_mautrix_discord_bridge_double_puppet_server_map_auto) | combine(matrix_mautrix_discord_bridge_double_puppet_server_map_custom) }}" +matrix_mautrix_discord_bridge_double_puppet_server_map_default: |- + {{ + {} + | combine({ + matrix_beeper_linkedin_homeserver_domain: matrix_beeper_linkedin_homeserver_address + }) + }} +matrix_mautrix_discord_bridge_double_puppet_server_map_auto: {} +matrix_mautrix_discord_bridge_double_puppet_server_map_custom: {} # Default mautrix-discord configuration template which covers the generic use case. # You can customize it by controlling the various variables inside it. diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 index 56c3bcfb8..322bc763a 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 @@ -173,8 +173,7 @@ bridge: height: 320 fps: 25 # only for webm, webp and gif (2, 5, 10, 20 or 25 recommended) # Servers to always allow double puppeting from - double_puppet_server_map: - "{{ matrix_mautrix_discord_homeserver_domain }}": {{ matrix_mautrix_discord_homeserver_address }} + double_puppet_server_map: {{ matrix_mautrix_discord_bridge_double_puppet_server_map | to_json }} # Allow using double puppeting from any server with a valid client .well-known file. double_puppet_allow_discovery: false # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth From 4d8b226c389c8b3c952bcd71f29ed9fcea20e7d7 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 2 Dec 2024 19:37:08 +0200 Subject: [PATCH 048/952] Minor refactoring around matrix_synapse_presence_enabled passing --- group_vars/matrix_servers | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index b2a1e148d..8e53a4636 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -753,7 +753,7 @@ matrix_appservice_discord_container_additional_networks_auto: |- }} # If the homeserver disables presence, it's likely better (less wasteful) to also disable presence on the bridge side. -matrix_appservice_discord_bridge_disablePresence: "{{ not matrix_synapse_presence_enabled }}" +matrix_appservice_discord_bridge_disablePresence: "{{ (not matrix_synapse_presence_enabled) if matrix_homeserver_implementation == 'synapse' else false }}" matrix_appservice_discord_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'discord.as.token', rounds=655555) | to_uuid }}" @@ -914,7 +914,7 @@ matrix_appservice_irc_container_additional_networks_auto: |- # The IRC bridge docs say that if homeserver presence is disabled, it's better to also disable # IRC bridge presence, for performance reasons. -matrix_appservice_irc_homeserver_enablePresence: "{{ matrix_synapse_presence_enabled }}" +matrix_appservice_irc_homeserver_enablePresence: "{{ matrix_synapse_presence_enabled if matrix_homeserver_implementation == 'synapse' else true }}" matrix_appservice_irc_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'irc.as.token', rounds=655555) | to_uuid }}" @@ -1253,7 +1253,7 @@ matrix_mautrix_facebook_appservice_public_prefix: "/{{ '%s' | format(matrix_home matrix_mautrix_facebook_login_shared_secret: "{{ matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled else '' }}" -matrix_mautrix_facebook_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}" +matrix_mautrix_facebook_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}" matrix_mautrix_facebook_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}" @@ -1465,7 +1465,7 @@ matrix_mautrix_instagram_homeserver_token: "{{ '%s' | format(matrix_homeserver_g matrix_mautrix_instagram_login_shared_secret: "{{ matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled else '' }}" -matrix_mautrix_instagram_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}" +matrix_mautrix_instagram_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}" matrix_mautrix_instagram_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}" From e5a2935d0fa344b4b97d218c5c39ac814b4906db Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 2 Dec 2024 19:38:02 +0200 Subject: [PATCH 049/952] Move configuration-creation tasks for beeper-linkedin before container-related tasks --- .../tasks/setup_install.yml | 37 +++++++++---------- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml index 1c8bfe965..7d27b1559 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml @@ -14,8 +14,23 @@ - {path: "{{ matrix_beeper_linkedin_docker_src_files_path }}", when: "{{ matrix_beeper_linkedin_container_image_self_build }}"} when: "item.when | bool" +- name: Ensure beeper-linkedin config.yaml installed + ansible.builtin.copy: + content: "{{ matrix_beeper_linkedin_configuration | to_nice_yaml(indent=2, width=999999) }}" + dest: "{{ matrix_beeper_linkedin_config_path }}/config.yaml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" -- name: Ensure Beeper LinkedIn image is pulled +- name: Ensure beeper-linkedin registration.yaml installed + ansible.builtin.copy: + content: "{{ matrix_beeper_linkedin_registration | to_nice_yaml(indent=2, width=999999) }}" + dest: "{{ matrix_beeper_linkedin_config_path }}/registration.yaml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure Beeper LinkedIn container image is pulled community.docker.docker_image: name: "{{ matrix_beeper_linkedin_docker_image }}" source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" @@ -41,7 +56,7 @@ # Building the container image (using the default Dockerfile) requires that a docker-requirements.txt file be generated. # See: https://github.com/beeper/linkedin/blob/94442db17ccb9769b377cdb8e4bf1cb3955781d7/.gitlab-ci.yml#L30-40 - - name: Ensure docker-requirements.txt is generated before building Beeper LinkedIn Docker Image + - name: Ensure docker-requirements.txt is generated before building Beeper LinkedIn container image ansible.builtin.command: cmd: | {{ devture_systemd_docker_base_host_command_docker }} run @@ -54,7 +69,7 @@ register: matrix_beeper_linkedin_generate_docker_requirements_result changed_when: matrix_beeper_linkedin_generate_docker_requirements_result.rc == 0 - - name: Ensure Beeper LinkedIn Docker image is built + - name: Ensure Beeper LinkedIn container image is built community.docker.docker_image: name: "{{ matrix_beeper_linkedin_docker_image }}" source: build @@ -67,22 +82,6 @@ args: TARGETARCH: "{{ matrix_architecture }}" -- name: Ensure beeper-linkedin config.yaml installed - ansible.builtin.copy: - content: "{{ matrix_beeper_linkedin_configuration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_beeper_linkedin_config_path }}/config.yaml" - mode: 0644 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - -- name: Ensure beeper-linkedin registration.yaml installed - ansible.builtin.copy: - content: "{{ matrix_beeper_linkedin_registration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_beeper_linkedin_config_path }}/registration.yaml" - mode: 0644 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - - name: Ensure beeper-linkedin container network is created community.general.docker_network: enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" From 2c719b2ef7198e1e4d4921c5daaebee9e5d00255 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 2 Dec 2024 20:00:08 +0200 Subject: [PATCH 050/952] Update beeper-linkedin configuration to latest upstream config and properly pass double-puppeting login shared secrets We used to pass the shared secret for double-puppeting via a `login_shared_secret` parameter, which doesn't seem to exist anymore. The proper way to do it is via `login_shared_secret_map`. The comments for `login_shared_secret_map` seem to indicate that it's only usable with the shared-secret-auth password provider. However, this bridge is based on mautrix-python (`>=0.20.5,<0.21`) as per its `requirements.txt` Support for double-puppeting via arbitrary access tokens landed in mautrix-python 0.20.1 (https://github.com/mautrix/python/blob/6f25b62e80616fa8a8a57d12a03caca51b3c89b4/CHANGELOG.md#L44-L53), so it should be possible to use appservice double-puppet. Related to https://github.com/mautrix/python/commit/af04ca12389e344fbda10463085ed5df4b62db69 A bunch of other parameters seem to have moved around as well. This patch introduces some new Ansible variables for controlling additional settings related to encryption, etc. --- ...iguring-playbook-bridge-beeper-linkedin.md | 7 +- group_vars/matrix_servers | 12 +- .../defaults/main.yml | 24 +- .../tasks/validate_config.yml | 9 + .../templates/config.yaml.j2 | 245 ++++++++++++------ .../systemd/matrix-beeper-linkedin.service.j2 | 4 +- 6 files changed, 202 insertions(+), 99 deletions(-) diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index e05a75c77..b7cc04d30 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -17,11 +17,8 @@ There are some additional things you may wish to configure about the bridge befo Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: ```yaml -matrix_beeper_linkedin_configuration_extension_yaml: | - bridge: - encryption: - allow: true - default: true +matrix_beeper_linkedin_bridge_encryption_allow: true +matrix_beeper_linkedin_bridge_encryption_default: true ``` If you would like to be able to administrate the bridge from your account it can be configured like this: diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 8e53a4636..c08326b17 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -1011,18 +1011,20 @@ matrix_beeper_linkedin_appservice_token: "{{ '%s' | format(matrix_homeserver_gen matrix_beeper_linkedin_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" matrix_beeper_linkedin_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'linked.hs.token', rounds=655555) | to_uuid }}" -matrix_beeper_linkedin_login_shared_secret: |- +matrix_beeper_linkedin_bridge_login_shared_secret_map_auto: |- {{ - ("as_token:" + matrix_appservice_double_puppet_registration_as_token) + ({ + matrix_beeper_linkedin_homeserver_domain: ("as_token:" + matrix_appservice_double_puppet_registration_as_token) + }) if matrix_appservice_double_puppet_enabled else ( - matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled + {matrix_beeper_linkedin_homeserver_domain: matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret} if matrix_synapse_ext_password_provider_shared_secret_auth_enabled - else "" + else {} ) }} -matrix_beeper_linkedin_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}" +matrix_beeper_linkedin_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}" matrix_beeper_linkedin_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}" matrix_beeper_linkedin_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maulinkedin.db', rounds=655555) | to_uuid }}" diff --git a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml index 936b2844a..fcba1e9b6 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml @@ -60,7 +60,8 @@ matrix_beeper_linkedin_appservice_token: "" matrix_beeper_linkedin_homeserver_token: "" matrix_beeper_linkedin_appservice_bot_username: linkedinbot - +matrix_beeper_linkedin_appservice_bot_displayname: LinkedIn bridge bot +matrix_beeper_linkedin_appservice_bot_avatar: mxc://nevarro.space/cwsWnmeMpWSMZLUNblJHaIvP # Database-related configuration fields. # Only Postgres is supported. @@ -87,9 +88,24 @@ matrix_beeper_linkedin_appservice_database_uri: "{{ }[matrix_beeper_linkedin_database_engine] }}" +matrix_beeper_linkedin_bridge_login_shared_secret_map: "{{ matrix_beeper_linkedin_bridge_login_shared_secret_map_auto | combine(matrix_beeper_linkedin_bridge_login_shared_secret_map_custom) }}" +matrix_beeper_linkedin_bridge_login_shared_secret_map_auto: {} +matrix_beeper_linkedin_bridge_login_shared_secret_map_custom: {} -# Can be set to enable automatic double-puppeting via Shared Secret Auth (https://github.com/devture/matrix-synapse-shared-secret-auth) or Appservice Double Puppet. -matrix_beeper_linkedin_login_shared_secret: '' +# Servers to always allow double puppeting from +matrix_beeper_linkedin_bridge_double_puppet_server_map: "{{ matrix_beeper_linkedin_bridge_double_puppet_server_map_default | combine(matrix_beeper_linkedin_bridge_double_puppet_server_map_auto) | combine(matrix_beeper_linkedin_bridge_double_puppet_server_map_custom) }}" +matrix_beeper_linkedin_bridge_double_puppet_server_map_default: |- + {{ + {} + | combine({ + matrix_beeper_linkedin_homeserver_domain: matrix_beeper_linkedin_homeserver_address + }) + }} +matrix_beeper_linkedin_bridge_double_puppet_server_map_auto: {} +matrix_beeper_linkedin_bridge_double_puppet_server_map_custom: {} + +matrix_beeper_linkedin_provisioning_enabled: false +matrix_beeper_linkedin_provisioning_shared_secret: '' # Specifies the default log level for all bridge loggers. matrix_beeper_linkedin_logging_level: WARNING @@ -97,6 +113,8 @@ matrix_beeper_linkedin_logging_level: WARNING # Enable End-to-bridge encryption matrix_beeper_linkedin_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}" matrix_beeper_linkedin_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}" +matrix_beeper_linkedin_bridge_encryption_appservice: "{{ matrix_beeper_linkedin_bridge_encryption_default }}" +matrix_beeper_linkedin_bridge_encryption_require: false matrix_beeper_linkedin_bridge_encryption_key_sharing_allow: "{{ matrix_beeper_linkedin_bridge_encryption_allow }}" # Default beeper-linkedin configuration template which covers the generic use case. diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml index afbf5c619..cbf77eb71 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml @@ -11,3 +11,12 @@ - {'name': 'matrix_beeper_linkedin_homeserver_token', when: true} - {'name': 'matrix_beeper_linkedin_database_hostname', when: "{{ matrix_beeper_linkedin_database_engine == 'postgres' }}"} - {'name': 'matrix_beeper_linkedin_container_network', when: true} + +- name: (Deprecation) Catch and report renamed beeper-linkedin settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_beeper_linkedin_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2 b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2 index 531adfd98..d73988cdf 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2 @@ -1,62 +1,74 @@ #jinja2: lstrip_blocks: "True" -# Homeserver details. +# Homeserver details homeserver: # The address that this appservice can use to connect to the homeserver. - address: {{ matrix_beeper_linkedin_homeserver_address }} + address: {{ matrix_beeper_linkedin_homeserver_address | to_json }} # The domain of the homeserver (for MXIDs, etc). - domain: {{ matrix_beeper_linkedin_homeserver_domain }} + domain: {{ matrix_beeper_linkedin_homeserver_domain | to_json }} # Whether or not to verify the SSL certificate of the homeserver. # Only applies if address starts with https:// verify_ssl: true - # Whether or not the homeserver supports asmux-specific endpoints, - # such as /_matrix/client/unstable/net.maunium.asmux/dms for atomically - # updating m.direct. - asmux: false + # What software is the homeserver running? + # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here. + software: standard # Number of retries for all HTTP requests if the homeserver isn't reachable. http_retry_count: 4 + # The URL to push real-time bridge status to. + # If set, the bridge will make POST requests to this URL whenever a user's Signal connection state changes. + # The bridge will use the appservice as_token to authorize requests. + status_endpoint: null + # Endpoint for reporting per-message status. + message_send_checkpoint_endpoint: null + # Whether asynchronous uploads via MSC2246 should be enabled for media. + # Requires a media repo that supports MSC2246. + async_media: false - +# Application service host/registration related details +# Changing these values requires regeneration of the registration. appservice: # The address that the homeserver can use to connect to this appservice. - address: {{ matrix_beeper_linkedin_appservice_address }} + address: {{ matrix_beeper_linkedin_appservice_address | to_json }} # The hostname and port where this appservice should listen. hostname: 0.0.0.0 port: 29319 - # The maximum body size of appservice API requests (from the homeserver) in mebibytes # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s max_body_size: 1 - # The full URI to the database. Only Postgres is currently supported. - database: {{ matrix_beeper_linkedin_appservice_database_uri|to_json }} - # Additional arguments for asyncpg.create_pool() + # The full URI to the database. SQLite and Postgres are supported. + # Format examples: + # SQLite: sqlite:filename.db + # Postgres: postgres://username:password@hostname/dbname + database: {{ matrix_beeper_linkedin_appservice_database_uri | to_json }} + # Additional arguments for asyncpg.create_pool() or sqlite3.connect() # https://magicstack.github.io/asyncpg/current/api/index.html#asyncpg.pool.create_pool + # https://docs.python.org/3/library/sqlite3.html#sqlite3.connect + # For sqlite, min_size is used as the connection thread pool size and max_size is ignored. + # Additionally, SQLite supports init_commands as an array of SQL queries to run on connect (e.g. to set PRAGMAs). database_opts: - min_size: 5 + min_size: 1 max_size: 10 # Provisioning API part of the web server for automated portal creation and fetching information. # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager). provisioning: # Whether or not the provisioning API should be enabled. - enabled: true + enabled: {{ matrix_beeper_linkedin_provisioning_enabled | to_json }} # The prefix to use in the provisioning API endpoints. prefix: /_matrix/provision/v1 # The shared secret to authorize users of the API. # Set to "generate" to generate and save a new token. - shared_secret: generate + shared_secret: {{ matrix_beeper_linkedin_provisioning_shared_secret | to_json }} # The unique ID of this appservice. id: beeper_linkedin - # Appservice bot details. - bot: - # Username of the appservice bot. - username: {{ matrix_beeper_linkedin_appservice_bot_username|to_json }} - # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty - # to leave display name/avatar as-is. - displayname: LinkedIn bridge bot - avatar: mxc://sumnerevans.com/XMtwdeUBnxYvWNFFrfeTSHqB + # Username of the appservice bot. + bot_username: {{ matrix_beeper_linkedin_appservice_bot_username | to_json }} + # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty + # to leave display name/avatar as-is. + bot_displayname: {{ matrix_beeper_linkedin_appservice_bot_displayname | to_json }} + bot_avatar: {{ matrix_beeper_linkedin_appservice_bot_avatar | to_json }} # Whether or not to receive ephemeral events via appservice transactions. # Requires MSC2409 support (i.e. Synapse 1.22+). @@ -64,9 +76,17 @@ appservice: ephemeral_events: false # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify. - as_token: "{{ matrix_beeper_linkedin_appservice_token }}" - hs_token: "{{ matrix_beeper_linkedin_homeserver_token }}" + as_token: {{ matrix_beeper_linkedin_appservice_token | to_json }} + hs_token: {{ matrix_beeper_linkedin_homeserver_token | to_json }} +# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors. +analytics: + # Hostname of the tracking server. The path is hardcoded to /v1/track + host: api.segment.io + # API key to send with tracking requests. Tracking is disabled if this is null. + token: null + # Optional user ID for tracking events. If null, defaults to using Matrix user ID. + user_id: null # Prometheus telemetry config. Requires prometheus-client to be installed. metrics: @@ -84,30 +104,41 @@ manhole: whitelist: - 0 - # Bridge config bridge: # Localpart template of MXIDs for LinkedIn users. - # {userid} is replaced with the user ID of the LinkedIn user + # {userid} is replaced with the user ID of the LinkedIn user. username_template: "linkedin_{userid}" # Settings for creating a space for every user. space_support: # Whether or not to enable creating a space per user and inviting the # user (as well as all of the puppets) to that space. - enable: {{ matrix_beeper_linkedin_bridge_space_support_enable|to_json }} + enable: {{ matrix_beeper_linkedin_bridge_space_support_enable | to_json }} # The name of the space name: "LinkedIn" - # Displayname template for LinkedIn users. # {displayname} is replaced with the display name of the LinkedIn user # as defined below in displayname_preference. # Keys available for displayname_preference are also available here. displayname_template: "{displayname} (LinkedIn)" + # Available keys: + # "name" (full name) + # "first_name" + # "last_name" + displayname_preference: + - name + - first_name + + # Whether or not to set the topic on DMs to the user's occupation and a + # link to their profile. + set_topic_on_dms: true + + # The prefix for commands. Only required in non-management rooms. + command_prefix: {{ matrix_beeper_linkedin_command_prefix | to_json }} # Number of chats to sync (and create portals for) on startup/login. # Set 0 to disable automatic syncing. - initial_chat_sync: 10 - + initial_chat_sync: 20 # Whether or not the LinkedIn users of logged in Matrix users should be # invited to private chats when the user sends a message from another client. invite_own_puppet_to_pm: false @@ -119,65 +150,112 @@ bridge: # and is therefore prone to race conditions. sync_direct_chat_list: false # Servers to always allow double puppeting from - double_puppet_server_map: {} - # example.com: https://example.com + double_puppet_server_map: {{ matrix_beeper_linkedin_bridge_double_puppet_server_map | to_json }} # Allow using double puppeting from any server with a valid client .well-known file. - - # Maximum number of seconds since last message in chat to skip - # syncing the chat in any case. This setting will take priority - # over both recovery_chat_sync_limit and initial_chat_sync_count. - # Default is 3 days = 259200 seconds - sync_max_chat_age: 259200 - - # Whether or not to sync with custom puppets to receive EDUs that - # are not normally sent to appservices. - sync_with_custom_puppets: true - # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth + double_puppet_allow_discovery: false + # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth # # If set, custom puppets will be enabled automatically for local users # instead of users having to find an access token and run `login-matrix` # manually. - login_shared_secret: {{ matrix_beeper_linkedin_login_shared_secret|to_json }} - - # Allow using double puppeting from any server with a valid client .well-known file. - double_puppet_allow_discovery: false - + # If using this for other servers than the bridge's server, + # you must also set the URL in the double_puppet_server_map. + login_shared_secret_map: {{ matrix_beeper_linkedin_bridge_login_shared_secret_map | to_json }} # Whether or not to bridge presence in both directions. LinkedIn allows users not to broadcast # presence, but then it won't send other users' presence to the client. - presence: {{ matrix_beeper_linkedin_bridge_presence|to_json }} + presence: {{ matrix_beeper_linkedin_bridge_presence | to_json }} # Whether or not to update avatars when syncing all contacts at startup. update_avatar_initial_sync: true + # Whether or not created rooms should have federation enabled. + # If false, created portal rooms will never be federated. + federate_rooms: true + # Whether to explicitly set the avatar and room name for private chat portal rooms. + # If set to `default`, this will be enabled in encrypted rooms and disabled in unencrypted rooms. + # If set to `always`, all DM rooms will have explicit names and avatars set. + # If set to `never`, DM rooms will never have names and avatars set. + private_chat_portal_meta: default - - # End-to-bridge encryption support options. These require matrix-nio to be installed with pip - # and login_shared_secret to be configured in order to get a device for the bridge bot. + # End-to-bridge encryption support options. # - # Additionally, https://github.com/matrix-org/synapse/pull/5758 is required if using a normal - # application service. + # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info. encryption: # Allow encryption, work in group chat rooms with e2ee enabled - allow: {{ matrix_beeper_linkedin_bridge_encryption_allow|to_json }} + allow: {{ matrix_beeper_linkedin_bridge_encryption_allow | to_json }} # Default to encryption, force-enable encryption in all portals the bridge creates # This will cause the bridge bot to be in private chats for the encryption to work properly. - default: {{ matrix_beeper_linkedin_bridge_encryption_default|to_json }} - # Options for automatic key sharing. - key_sharing: - # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. - # You must use a client that supports requesting keys from other users to use this feature. - allow: {{ matrix_beeper_linkedin_bridge_encryption_key_sharing_allow|to_json }} - # Require the requesting device to have a valid cross-signing signature? - # This doesn't require that the bridge has verified the device, only that the user has verified it. - # Not yet implemented. - require_cross_signing: false - # Require devices to be verified by the bridge? - # Verification by the bridge is not yet implemented. - require_verification: true + default: {{ matrix_beeper_linkedin_bridge_encryption_default | to_json }} + # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data. + appservice: {{ matrix_beeper_linkedin_bridge_encryption_appservice | to_json }} + # Require encryption, drop any unencrypted messages. + require: {{ matrix_beeper_linkedin_bridge_encryption_require | to_json }} + # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. + # You must use a client that supports requesting keys from other users to use this feature. + allow_key_sharing: {{ matrix_beeper_linkedin_bridge_encryption_key_sharing_allow | to_json }} + # Options for deleting megolm sessions from the bridge. + delete_keys: + # Beeper-specific: delete outbound sessions when hungryserv confirms + # that the user has uploaded the key to key backup. + delete_outbound_on_ack: false + # Don't store outbound sessions in the inbound table. + dont_store_outbound: false + # Ratchet megolm sessions forward after decrypting messages. + ratchet_on_decrypt: false + # Delete fully used keys (index >= max_messages) after decrypting messages. + delete_fully_used_on_decrypt: false + # Delete previous megolm sessions from same device when receiving a new one. + delete_prev_on_new_session: false + # Delete megolm sessions received from a device when the device is deleted. + delete_on_device_delete: false + # Periodically delete megolm sessions when 2x max_age has passed since receiving the session. + periodically_delete_expired: false + # Delete inbound megolm sessions that don't have the received_at field used for + # automatic ratcheting and expired session deletion. This is meant as a migration + # to delete old keys prior to the bridge update. + delete_outdated_inbound: false + # What level of device verification should be required from users? + # + # Valid levels: + # unverified - Send keys to all device in the room. + # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys. + # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes). + # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot. + # Note that creating user signatures from the bridge bot is not currently possible. + # verified - Require manual per-device verification + # (currently only possible by modifying the `trust` column in the `crypto_device` database table). + verification_levels: + # Minimum level for which the bridge should send keys to when bridging messages from Telegram to Matrix. + receive: unverified + # Minimum level that the bridge should accept for incoming Matrix messages. + send: unverified + # Minimum level that the bridge should require for accepting key requests. + share: cross-signed-tofu + # Options for Megolm room key rotation. These options allow you to + # configure the m.room.encryption event content. See: + # https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for + # more information about that event. + rotation: + # Enable custom Megolm room key rotation settings. Note that these + # settings will only apply to rooms created after this option is + # set. + enable_custom: false + # The maximum number of milliseconds a session should be used + # before changing it. The Matrix spec recommends 604800000 (a week) + # as the default. + milliseconds: 604800000 + # The maximum number of messages that should be sent with a given a + # session before changing it. The Matrix spec recommends 100 as the + # default. + messages: 100 + + # Disable rotating keys when a user's devices change? + # You should not enable this option unless you understand all the implications. + disable_device_change_key_rotation: false + # Whether or not the bridge should send a read receipt from the bridge bot when a message has # been sent to LinkedIn. delivery_receipts: false # Whether to allow inviting arbitrary mxids to portal rooms allow_invites: false - # Settings for backfilling messages from LinkedIn. backfill: # Whether or not the LinkedIn users of logged in Matrix users should be @@ -194,6 +272,10 @@ bridge: # If using double puppeting, should notifications be disabled # while the initial backfill is in progress? disable_notifications: false + # If this value is greater than 0, then (on backfill) if the + # conversation's last message was more than this number of hours ago, + # then the conversation will automatically be marked it as read. + unread_hours_threshold: 0 periodic_reconnect: # TODO needed? # Interval in seconds in which to automatically reconnect all users. @@ -224,23 +306,20 @@ bridge: # Whether or not mute status and tags should only be bridged when the portal room is created. tag_only_on_create: true - - # The prefix for commands. Only required in non-management rooms. - command_prefix: "{{ matrix_beeper_linkedin_command_prefix }}" - # Permissions for using the bridge. # Permitted values: - # user - Access to use the bridge to chat with a Linkedin account. - # admin - User level and some additional administration tools + # user - Use the bridge with puppeting. + # admin - Use and administrate the bridge. # Permitted keys: # * - All Matrix users # domain - All users on that homeserver # mxid - Specific user - permissions: {{ matrix_beeper_linkedin_bridge_permissions|to_json }} + permissions: {{ matrix_beeper_linkedin_bridge_permissions | to_json }} - - -# Logging config. +# Python logging configuration. +# +# See section 16.7.2 of the Python documentation for more info: +# https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema logging: version: 1 formatters: @@ -256,10 +335,8 @@ logging: loggers: mau: level: {{ matrix_beeper_linkedin_logging_level|to_json }} - paho: - level: {{ matrix_beeper_linkedin_logging_level|to_json }} aiohttp: level: {{ matrix_beeper_linkedin_logging_level|to_json }} root: - level: {{ matrix_beeper_linkedin_logging_level|to_json }} + level: DEBUG handlers: [console] diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 index 68d062594..1b1cc582b 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 +++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 @@ -23,13 +23,13 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ --cap-drop=ALL \ --network={{ matrix_beeper_linkedin_container_network }} \ - --mount type=bind,src={{ matrix_beeper_linkedin_config_path }},dst=/data \ + --mount type=bind,src={{ matrix_beeper_linkedin_config_path }},dst=/config,ro \ --workdir=/opt/linkedin-matrix \ {% for arg in matrix_beeper_linkedin_container_extra_arguments %} {{ arg }} \ {% endfor %} {{ matrix_beeper_linkedin_docker_image }} \ - python3 -m linkedin_matrix -c /data/config.yaml -r /data/registration.yaml + python3 -m linkedin_matrix -c /config/config.yaml -r /config/registration.yaml --no-update {% for network in matrix_beeper_linkedin_container_additional_networks %} ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-beeper-linkedin From 819ca219541ec969cf5873567981ce257c24a0b4 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 3 Dec 2024 14:02:54 +0000 Subject: [PATCH 051/952] Update vectorim/element-web Docker tag to v1.11.87 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 4cea592b2..148c8e674 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.86 +matrix_client_element_version: v1.11.87 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" From bf123e7ad518e4d1d5883858ed5bce749e351191 Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 3 Dec 2024 18:38:17 +0200 Subject: [PATCH 052/952] synapse v1.120.2 --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 7896886b0..48bdce53b 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.120.0 +matrix_synapse_version: v1.120.2 matrix_synapse_username: '' matrix_synapse_uid: '' From b037cb6164f2f3bb51e50b9610ed2a71a101f87d Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 3 Dec 2024 20:03:28 +0200 Subject: [PATCH 053/952] fix postgres backup for postgres v17 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index a1302e6a3..839e67355 100644 --- a/requirements.yml +++ b/requirements.yml @@ -46,7 +46,7 @@ version: v17.2-0 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git - version: v16-0 + version: v17-0 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git version: v2.55.1-0 From 0e5d0aec654eeea1e83dd8ce199d9ec575a2c62d Mon Sep 17 00:00:00 2001 From: Aine Date: Wed, 4 Dec 2024 00:19:24 +0200 Subject: [PATCH 054/952] Synapse Admin v0.10.3-etke33 --- roles/custom/matrix-synapse-admin/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 58ed20551..b83597cd8 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -14,7 +14,7 @@ matrix_synapse_admin_container_image_self_build: false matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git" # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin -matrix_synapse_admin_version: v0.10.3-etke32 +matrix_synapse_admin_version: v0.10.3-etke33 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}" matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}" From 05ba03f9af326dc6bf4b0ccb775ea7557725b2b0 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 4 Dec 2024 01:55:57 +0000 Subject: [PATCH 055/952] Update joseluisq/static-web-server Docker tag to v2.34.0 --- roles/custom/matrix-cactus-comments-client/defaults/main.yml | 2 +- roles/custom/matrix-static-files/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 9e144adce..8d00cc1e5 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -13,7 +13,7 @@ matrix_cactus_comments_client_public_path: "{{ matrix_cactus_comments_client_bas matrix_cactus_comments_client_public_path_file_permissions: "0644" # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_cactus_comments_client_version: 2.33.1 +matrix_cactus_comments_client_version: 2.34.0 matrix_cactus_comments_client_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}" diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index 7e3abf2f5..112c4414b 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -8,7 +8,7 @@ matrix_static_files_enabled: true matrix_static_files_identifier: matrix-static-files # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_static_files_version: 2.33.1 +matrix_static_files_version: 2.34.0 matrix_static_files_base_path: "{{ matrix_base_data_path }}/{{ 'static-files' if matrix_static_files_identifier == 'matrix-static-files' else matrix_static_files_identifier }}" matrix_static_files_config_path: "{{ matrix_static_files_base_path }}/config" From 7d14294de6659ca33424f01fb3501bbbf6add5ba Mon Sep 17 00:00:00 2001 From: Aine Date: Thu, 5 Dec 2024 11:20:32 +0200 Subject: [PATCH 056/952] grafana v11.3.2 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 839e67355..3aa18851e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98-r0-2-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.3.1-0 + version: v11.3.2-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v9823-1 From 83f3b1aab4a90fdcda63573801988128c77260e4 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 5 Dec 2024 20:43:24 +0000 Subject: [PATCH 057/952] Update dependency grafana to v11.4.0-0 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 3aa18851e..1070b9d39 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98-r0-2-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.3.2-0 + version: v11.4.0-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v9823-1 From d1fa7378f73f58fd8d89948af8d6de177f55caf7 Mon Sep 17 00:00:00 2001 From: janonym1 <79254796+janonym1@users.noreply.github.com> Date: Fri, 6 Dec 2024 04:21:34 +0100 Subject: [PATCH 058/952] hookshot: Allow the localpart of the hookshot-bot to be defined (#3853) * set localpart of hookshot bot in main.yml * set sender_localpart in registration.yml.j2 template to variable * prettier location for bot localpart in main.yml * Update main.yml * Update registration.yml.j2 --------- Co-authored-by: Slavi Pantaleev --- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 3 +++ .../matrix-bridge-hookshot/templates/registration.yml.j2 | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 88542d9ee..5b1d6e210 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -30,6 +30,9 @@ matrix_hookshot_docker_src_files_path: "{{ matrix_hookshot_base_path }}/docker-s matrix_hookshot_homeserver_address: "" matrix_hookshot_container_url: 'matrix-hookshot' +# Sets the localpart of the Matrix ID for the hookshot bot +matrix_hookshot_bot_localpart: "hookshot" + matrix_hookshot_public_scheme: https matrix_hookshot_public_hostname: "{{ matrix_server_fqn_matrix }}" matrix_hookshot_public_endpoint: /hookshot diff --git a/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2 b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2 index 0f76b1c05..bb3dc34d1 100644 --- a/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2 +++ b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2 @@ -25,7 +25,7 @@ namespaces: - regex: "#github_.+:{{ matrix_domain }}" exclusive: true -sender_localpart: hookshot +sender_localpart: {{ matrix_hookshot_bot_localpart | to_json }} url: "http://{{ matrix_hookshot_container_url }}:{{ matrix_hookshot_appservice_port }}" # This should match the bridge.port in your config file rate_limited: false From 9178b2e053906447d5765933ba9a28e31ecf6545 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 6 Dec 2024 05:30:37 +0200 Subject: [PATCH 059/952] Add ghcr.io/matrixgpt/matrix-chatgpt-bot to Renovate's `ignoreDeps` list Related to: - https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3196 - ce893c1b221dfea2c1421a5f54dd8159f6fff601 - https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3200#issuecomment-2491780481 - https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3856 --- .github/renovate.json | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/renovate.json b/.github/renovate.json index f14fed020..e9c3ceb67 100644 --- a/.github/renovate.json +++ b/.github/renovate.json @@ -20,5 +20,8 @@ ], "ignoreUnstable": false } + ], + "ignoreDeps": [ + "ghcr.io/matrixgpt/matrix-chatgpt-bot" ] } From 0312ae490defae3c8561a796798453927a71f485 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 2 Dec 2024 20:35:40 +0900 Subject: [PATCH 060/952] Edit README.md: add links to docs/FAQ.md and to the support section Signed-off-by: Suguru Hirahara --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index dc8c7ddbe..412b73b65 100644 --- a/README.md +++ b/README.md @@ -32,6 +32,8 @@ While the [list of supported services](#-supported-services) and documentation i - **Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](./docs/prerequisites.md)** documentation page. +If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support). + ## ✔ Supported services Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else. From e5ab17cafd62feb6e68e3234d434d69cbb383962 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 4 Dec 2024 11:57:15 +0900 Subject: [PATCH 061/952] Remove numbering from headings for consistency Signed-off-by: Suguru Hirahara --- ...ing-playbook-appservice-draupnir-for-all.md | 12 ++++++------ docs/configuring-playbook-bot-chatgpt.md | 8 ++++---- docs/configuring-playbook-bot-draupnir.md | 18 +++++++++--------- docs/configuring-playbook-bot-mjolnir.md | 18 +++++++++--------- docs/configuring-playbook-pantalaimon.md | 4 ++-- 5 files changed, 30 insertions(+), 30 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index dcbc57853..9766af929 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -18,7 +18,7 @@ Draupnir for all does not support external tooling like [MRU](https://mru.rory.g ## Installation -### 1. Create a main management room. +### Create a main management room. The playbook does not create a management room for your Main Draupnir. This task you have to do on your own. @@ -29,11 +29,11 @@ This management room is used to control who has access to your D4A deployment. T As noted in the Draupnir install instructions the control room is sensitive. The following is said about the control room in the Draupnir install instructions. >Anyone in this room can control the bot so it is important that you only invite trusted users to this room. The room must be unencrypted since the playbook does not support installing Pantalaimon yet. -### 2. Give your main management room an alias. +### Give your main management room an alias. Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase. -### 3. Adjusting the playbook configuration. +### Adjusting the playbook configuration. Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -45,7 +45,7 @@ matrix_appservice_draupnir_for_all_enabled: true matrix_appservice_draupnir_for_all_master_control_room_alias: "ALIAS_FROM_STEP_2_GOES_HERE" ``` -### 4. Installing +### Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -68,7 +68,7 @@ If you made it through all the steps above and your main control room was joined The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot mode. -### 1. Granting Users the ability to use D4A +### Granting Users the ability to use D4A Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended. @@ -76,7 +76,7 @@ The bot requires a powerlevel of 50 in the management room to control who is all To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially. -### 2. How to provision a D4A once you are allowed to. +### How to provision a D4A once you are allowed to. Open a DM with @draupnir-main:example.com and if using an Element client send a message into this DM to finalise creating it. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience. diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index da963bdff..dd9601496 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -6,7 +6,7 @@ The playbook can install and configure [matrix-chatgpt-bot](https://github.com/m Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client! -## 1. Register the bot account +## Register the bot account The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. @@ -20,13 +20,13 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` -## 2. Get an access token and create encryption keys +## Get an access token and create encryption keys Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). 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). -## 3. Adjusting the playbook configuration +## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -51,7 +51,7 @@ matrix_bot_chatgpt_matrix_bot_prompt_prefix: 'Instructions:\nYou are ChatGPT, a You will need to get tokens for ChatGPT. -## 4. Installing +## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 4c230297c..47b0901ed 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -8,7 +8,7 @@ This documentation page is about installing Draupnir in bot mode. As an alternat If your migrating from Mjolnir skip to step 5b. -## 1. Register the bot account +## Register the bot account The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. @@ -24,11 +24,11 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupni If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -## 2. Get an access token +## Get an access token Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -## 3. Make sure the account is free from rate limiting +## Make sure the account is free from rate limiting You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. @@ -36,7 +36,7 @@ If your Synapse Admin API is exposed to the internet for some reason like runnin The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@example:example.com/override_ratelimit` Replace `@example:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token. -## 4. Create a management room +## Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. @@ -46,11 +46,11 @@ Once you have created the room you need to copy the room ID so you can tell the Finally invite the `@bot.draupnir:example.com` account you created earlier into the room. -## 5. Adjusting the playbook configuration +## Adjusting the playbook configuration Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). -### 5a. Configuration with E2EE support +### a. Configuration with E2EE support When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password. @@ -85,7 +85,7 @@ matrix_bot_draupnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matr matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" ``` -### 5b. Configuration without E2EE support +### b. Configuration without E2EE support When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account. @@ -101,13 +101,13 @@ matrix_bot_draupnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE" matrix_bot_draupnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" ``` -### 5c. Migrating from Mjolnir (Only required if migrating.) +### c. Migrating from Mjolnir (Only required if migrating.) Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration. That is all you need to do due to that Draupnir can complete migration on its own. -## 6. Installing +## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 7036a1180..81b23fdc8 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -4,7 +4,7 @@ The playbook can install and configure the [Mjolnir](https://github.com/matrix-o See the project's [documentation](https://github.com/matrix-org/mjolnir) to learn what it does and why it might be useful to you. -## 1. Register the bot account +## Register the bot account The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. @@ -20,11 +20,11 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -## 2. Get an access token +## Get an access token Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -## 3. Make sure the account is free from rate limiting +## Make sure the account is free from rate limiting You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. @@ -32,7 +32,7 @@ If your Synapse Admin API is exposed to the internet for some reason like runnin The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@example:example.com/override_ratelimit` Replace `@example:example.com` with the MXID of your Mjolnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Mjolnir itself. If you made Mjolnir Admin you can just use the Mjolnir token. -## 4. Create a management room +## Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. @@ -42,11 +42,11 @@ Once you have created the room you need to copy the room ID so you can tell the Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room. -## 5. Adjusting the playbook configuration +## Adjusting the playbook configuration Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). -### 5a. Configuration with E2EE support +### a. Configuration with E2EE support When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password. @@ -81,7 +81,7 @@ matrix_bot_mjolnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matri matrix_bot_mjolnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" ``` -### 5b. Configuration without E2EE support +### b. Configuration without E2EE support When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account. @@ -97,7 +97,7 @@ matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE" matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" ``` -## 6. Adding Mjolnir synapse antispam module (optional) +## Adding Mjolnir synapse antispam module (optional) Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -109,7 +109,7 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_block_usernames: false matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] ``` -## 7. Installing +## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index 054fbcc32..99c42324c 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -6,7 +6,7 @@ See the project's [documentation](https://github.com/matrix-org/pantalaimon) to This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it. -## 1. Adjusting the playbook configuration +## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -16,7 +16,7 @@ matrix_pantalaimon_enabled: true The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml). -## 2. Installing +## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 701e697d908159a29997868808c611f7d08adcdc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 5 Dec 2024 15:07:33 +0900 Subject: [PATCH 062/952] Update README.md: remove a redundant whitespace character Signed-off-by: Suguru Hirahara --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 7ab368150..6a0cf1059 100644 --- a/docs/README.md +++ b/docs/README.md @@ -27,7 +27,7 @@ NOTE: You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md) -- [Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation +- [Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation - [Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver From c1c1b3ada0007614794d4656d9f2f63f32932adc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 5 Dec 2024 15:14:47 +0900 Subject: [PATCH 063/952] Replace triple dots with horizontal ellipsis (U+2026) Signed-off-by: Suguru Hirahara --- .github/ISSUE_TEMPLATE/feature_request.md | 2 +- CHANGELOG.md | 8 ++++---- docs/ansible.md | 8 ++++---- ...ing-playbook-bot-matrix-registration-bot.md | 2 +- ...figuring-playbook-bridge-mautrix-discord.md | 2 +- docs/faq.md | 2 +- docs/importing-postgres.md | 6 +++--- .../caddy2-in-container/docker-compose.yaml | 2 +- justfile | 6 +++--- .../matrix-base/templates/bin/remove-all.j2 | 2 +- .../defaults/main.yml | 2 +- .../matrix-bridge-hookshot/defaults/main.yml | 2 +- .../matrix-dendrite/templates/dendrite.yaml.j2 | 2 +- .../defaults/main.yml | 2 +- roles/custom/matrix-synapse/defaults/main.yml | 4 ++-- .../templates/synapse/homeserver.yaml.j2 | 18 +++++++++--------- roles/custom/matrix-synapse/vars/main.yml | 2 +- 17 files changed, 36 insertions(+), 36 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 2dd100be5..1c50f6145 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -8,7 +8,7 @@ assignees: '' --- **Is your feature request related to a problem? Please describe.** -A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] +A clear and concise description of what the problem is. Ex. I'm always frustrated when […] The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room. This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel. -As noted in the Draupnir install instructions the control room is sensitive. The following is said about the control room in the Draupnir install instructions. ->Anyone in this room can control the bot so it is important that you only invite trusted users to this room. The room must be unencrypted since the playbook does not support installing Pantalaimon yet. +As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.** -### Give your main management room an alias. +### Set an alias to the management room -Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase. +Next, set an alias to the management room. -### Adjusting the playbook configuration. +This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +## Adjusting the playbook configuration -You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created in step 2. +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`. ```yaml matrix_appservice_draupnir_for_all_enabled: true -matrix_appservice_draupnir_for_all_master_control_room_alias: "ALIAS_FROM_STEP_2_GOES_HERE" +matrix_appservice_draupnir_for_all_master_control_room_alias: "MANAGEMENT_ROOM_ALIAS_HERE" ``` -### Installing +### Extending the configuration + +You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable. + +For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_appservice_draupnir_for_all_extension_yaml: | + # Your custom YAML configuration goes here. + # This configuration extends the default starting configuration (`matrix_appservice_draupnir_for_all_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_appservice_draupnir_for_all_yaml`. + protectAllJoinedRooms: true +``` + +You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation. + +**Notes**: + +- The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role. + +- Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms. + +## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -66,7 +95,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it. -The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot mode. +The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode. ### Granting Users the ability to use D4A @@ -76,30 +105,8 @@ The bot requires a powerlevel of 50 in the management room to control who is all To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially. -### How to provision a D4A once you are allowed to. +### How to provision a D4A once you are allowed to -Open a DM with @draupnir-main:example.com and if using an Element client send a message into this DM to finalise creating it. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience. +To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience. Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment. - -### Configuration of D4A - -You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation. Please note that the playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role. - -Please note that Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyways. Config extension instead touches the config passed to the Draupnirs that your Appservice creates. So for example below makes all provisioned Draupnirs protect all joined rooms. - -You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. - -For example to change Draupnir's `protectAllJoinedRooms` option to `true` you would add the following to your `vars.yml` file. - -```yaml -matrix_appservice_draupnir_for_all_extension_yaml: | - # Your custom YAML configuration goes here. - # This configuration extends the default starting configuration (`matrix_appservice_draupnir_for_all_yaml`). - # - # You can override individual variables from the default configuration, or introduce new ones. - # - # If you need something more special, you can take full control by - # completely redefining `matrix_appservice_draupnir_for_all_yaml`. - protectAllJoinedRooms: true -``` diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index ce80c9285..c4a0239c8 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -6,13 +6,13 @@ See the project's [documentation](https://github.com/the-draupnir-project/Draupn This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead. -If your migrating from Mjolnir skip to step 5b. +If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating). -## Register the bot account +## Prerequisites -The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. +### Register the bot account -You **need to register the bot user manually** before setting up the bot. +The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. @@ -22,25 +22,41 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` -If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. +If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -## Get an access token +### Get an access token -Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +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). -## Make sure the account is free from rate limiting +### Make sure the account is free from rate limiting -You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. +If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.** -If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands. +This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. -The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit` Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token. +To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. -## Create a management room +```yaml +matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true +``` + +The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). + +**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). + +To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: + +```sh +curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit +``` + +You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token. + +### Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. -If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below). +If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. @@ -48,9 +64,22 @@ Finally invite the `@bot.draupnir:example.com` account you created earlier into ## Adjusting the playbook configuration -Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. -### a. Configuration with E2EE support +```yaml +# Enable Draupnir +matrix_bot_draupnir_enabled: true + +matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE" +``` + +### End-to-End Encryption support + +Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. + +To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). + +#### Configuration with E2EE support When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password. @@ -60,17 +89,12 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ # Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md matrix_pantalaimon_enabled: true -# Enable Draupnir -matrix_bot_draupnir_enabled: true - # Tell Draupnir to use Pantalaimon matrix_bot_draupnir_pantalaimon_use: true -# User name and password for the bot. Required when using Pantalaimon. -matrix_bot_draupnir_pantalaimon_username: "DRAUPNIR_USERNAME_FROM_STEP_1" -matrix_bot_draupnir_pantalaimon_password: ### you should create a secure password for the bot account - -matrix_bot_draupnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" +# User name and password for the bot you have created above. Required when using Pantalaimon. +matrix_bot_draupnir_pantalaimon_username: "bot.draupnir" +matrix_bot_draupnir_pantalaimon_password: "PASSWORD_FOR_THE_BOT" ``` The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one "raw". This example is taken from the playbook's `group_vars`: @@ -85,23 +109,47 @@ matrix_bot_draupnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matr matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" ``` -### b. Configuration without E2EE support +#### Configuration without E2EE support When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): - -You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values. +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](#get-an-access-token). ```yaml -matrix_bot_draupnir_enabled: true - -matrix_bot_draupnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE" - -matrix_bot_draupnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" +matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" ``` -### c. Migrating from Mjolnir (Only required if migrating.) +### Abuse Reports + +Draupnir supports two methods to receive reports in the management room. + +The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you: + +```yaml +matrix_bot_draupnir_abuse_reporting_enabled: true +``` + +The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below. + +### Extending the configuration + +You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable. + +For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_bot_draupnir_configuration_extension_yaml: | + # Your custom YAML configuration goes here. + # This configuration extends the default starting configuration (`matrix_bot_draupnir_configuration_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_bot_draupnir_configuration_yaml`. + pollReports: true +``` + +### Migrating from Mjolnir (Only required if migrating) Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration. @@ -193,38 +241,3 @@ To **set a specific option for a given protection**, send a command like this: ` To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`). To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`). - -## Extending the configuration - -You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. - -For example to change Draupnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file. - -```yaml -matrix_bot_draupnir_configuration_extension_yaml: | - # Your custom YAML configuration goes here. - # This configuration extends the default starting configuration (`matrix_bot_draupnir_configuration_yaml`). - # - # You can override individual variables from the default configuration, or introduce new ones. - # - # If you need something more special, you can take full control by - # completely redefining `matrix_bot_draupnir_configuration_yaml`. - recordIgnoredInvites: true -``` - -## Abuse Reports - -Draupnir supports two methods to receive reports in the management room. - -The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you: - -```yaml -matrix_bot_draupnir_abuse_reporting_enabled: true -``` - -The other method polls an synapse admin API endpoint and is hence only available when using synapse and when the Draupnir user is an admin user (see step 1). To enable it, set `pollReports: true` in Draupnir's config: - -```yaml -matrix_bot_draupnir_configuration_extension_yaml: | - pollReports: true -``` diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 4f8430949..0a52f63fa 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -4,11 +4,11 @@ The playbook can install and configure the [Mjolnir](https://github.com/matrix-o See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you. -## Register the bot account +## Prerequisites -The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. +### Register the bot account -You **need to register the bot user manually** before setting up the bot. +The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. @@ -20,23 +20,39 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -## Get an access token +### Get an access token -Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +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). -## Make sure the account is free from rate limiting +### Make sure the account is free from rate limiting -You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues. +If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.** -If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands. +This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. -The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit` Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Mjolnir itself. If you made Mjolnir Admin you can just use the Mjolnir token. +To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. -## Create a management room +```yaml +matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true +``` + +The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). + +**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). + +To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: + +```sh +curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit +``` + +You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token. + +### Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. -If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below). +If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. @@ -44,9 +60,22 @@ Finally invite the `@bot.mjolnir:example.com` account you created earlier into t ## Adjusting the playbook configuration -Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. -### a. Configuration with E2EE support +```yaml +# Enable Mjolnir +matrix_bot_mjolnir_enabled: true + +matrix_bot_mjolnir_management_room: "MANAGEMENT_ROOM_ID_HERE" +``` + +### End-to-End Encryption support + +Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. + +To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). + +#### Configuration with E2EE support When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password. @@ -56,17 +85,12 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ # Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md matrix_pantalaimon_enabled: true -# Enable Mjolnir -matrix_bot_mjolnir_enabled: true - # Tell Mjolnir to use Pantalaimon matrix_bot_mjolnir_pantalaimon_use: true -# User name and password for the bot. Required when using Pantalaimon. -matrix_bot_mjolnir_pantalaimon_username: "MJOLNIR_USERNAME_FROM_STEP_1" -matrix_bot_mjolnir_pantalaimon_password: ### you should create a secure password for the bot account - -matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" +# User name and password for the bot you have created above. Required when using Pantalaimon. +matrix_bot_mjolnir_pantalaimon_username: "bot.mjolnir" +matrix_bot_mjolnir_pantalaimon_password: "PASSWORD_FOR_THE_BOT" ``` The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one "raw". This example is taken from the playbook's `group_vars`: @@ -81,25 +105,19 @@ matrix_bot_mjolnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matri matrix_bot_mjolnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" ``` -### b. Configuration without E2EE support +#### Configuration without E2EE support When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): - -You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values. +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](#get-an-access-token). ```yaml -matrix_bot_mjolnir_enabled: true - -matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE" - -matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE" +matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_HERE" ``` -## Adding Mjolnir synapse antispam module (optional) +### Adding Mjolnir synapse antispam module (optional) -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): ```yaml matrix_synapse_ext_spam_checker_mjolnir_antispam_enabled: true @@ -109,6 +127,24 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_block_usernames: false matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] ``` +### Extending the configuration + +You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. + +For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_bot_mjolnir_configuration_extension_yaml: | + # Your custom YAML configuration goes here. + # This configuration extends the default starting configuration (`matrix_bot_mjolnir_configuration_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_bot_mjolnir_configuration_yaml`. + recordIgnoredInvites: true +``` + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -131,19 +167,3 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot. - -You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. - -For example to change Mjolnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file. - -```yaml -matrix_bot_mjolnir_configuration_extension_yaml: | - # Your custom YAML configuration goes here. - # This configuration extends the default starting configuration (`matrix_bot_mjolnir_configuration_yaml`). - # - # You can override individual variables from the default configuration, or introduce new ones. - # - # If you need something more special, you can take full control by - # completely redefining `matrix_bot_mjolnir_configuration_yaml`. - recordIgnoredInvites: true -``` From 9f72062feabda17d2138e8675231df5c0d25b676 Mon Sep 17 00:00:00 2001 From: adam-kress Date: Tue, 17 Dec 2024 08:57:36 -0500 Subject: [PATCH 109/952] Upgrade Jitsi (v9823-1 -> v9909-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index a156fae82..479fa0e8e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.4.0-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v9823-1 + version: v9909-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-keydb.git version: v6.3.4-3 From 2d1c8c7c013458b54801a5d284948df557948963 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 13 Dec 2024 03:24:29 +0900 Subject: [PATCH 110/952] Update docs/configuring-playbook-alertmanager-receiver.md: adopt common docs structure This commit adopts common structure of descriptions on mjolnir and draupnir docs. Signed-off-by: Suguru Hirahara --- ...figuring-playbook-alertmanager-receiver.md | 61 +++++++++++-------- 1 file changed, 35 insertions(+), 26 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index f5107af66..de374e803 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -4,23 +4,50 @@ The playbook can install and configure the [matrix-alertmanager-receiver](https: 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. -At the moment, **setting up this service's bot requires some manual actions** as described below in [Account and room preparation](#account-and-room-preparation). - This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it. +## Prerequisites + +### Register the bot account + +This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages. + +The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. + +Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. + +You can use the playbook to [register a new user](registering-users.md): + +```sh +ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user +``` + +### Get an access token + +The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). + +### Join to rooms as the bot manually + +ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually. + +For each new room you would like the bot to deliver alerts to, invite the bot to the room. + +Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out. + +You may optionally adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID. It provides cleaner `/alert/` URLs. + ## Adjusting the playbook configuration -To enable matrix-alertmanager-receiver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#get-an-access-token). ```yaml matrix_alertmanager_receiver_enabled: true -# If you'd like to change the username for this bot, uncomment and adjust. Otherwise, remove. +# Uncomment and adjust this part if you'd like to use a username different than the default # matrix_alertmanager_receiver_config_matrix_user_id_localpart: "bot.alertmanager.receiver" # Specify the bot user's access token here. -# See the "Account and room preparation" section below. -matrix_alertmanager_receiver_config_matrix_access_token: '' +matrix_alertmanager_receiver_config_matrix_access_token: "ACCESS_TOKEN_HERE" # Optionally, configure some mappings (URL-friendly room name -> actual Matrix room ID). # @@ -57,25 +84,9 @@ See [Configuring DNS](configuring-dns.md) for details about DNS changes. If you've decided to use the default hostname, you won't need to do any extra DNS configuration. -## Account and room preparation - -The playbook can automatically create users, but it cannot automatically obtain access tokens, nor perform any of the other manual actions below. - -`matrix-alertmanager-receiver` uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see above) for delivering messages. You need to **manually register this bot acccount and obtain an access token for it**. - -1. [Register a new user](registering-users.md): `ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user` -2. [Obtain an access token](obtaining-access-tokens.md) for the bot's user account -3. Invite the bot to a room where you'd like to alerts to be delivered -4. Log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account and log out -5. (Optionally) Adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID - -Steps 1 and 2 above only need to be done once, while preparing your [configuration](#adjusting-the-playbook-configuration). - -Steps 3 and 4 need to be done for each new room you'd like the bot to deliver alerts to. Step 5 is optional and provides cleaner `/alert/` URLs. - ## Installing -Now that you've [prepared the bot account and room](#account-and-room-preparation), [configured the playbook](#adjusting-the-playbook-configuration), and potentially [adjusted your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below: +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: ```sh @@ -111,6 +122,4 @@ route: - receiver: matrix ``` -.. where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`. - -This bot does **not** accept room invitations automatically (like many other bots do). To deliver messages to rooms, **the bot must be joined to all rooms manually** - see Step 4 of the [Account and room preparation](#account-and-room-preparation) section. +where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`. From 708112423709e0da0a4910c71804d8679151104c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 13 Dec 2024 03:25:14 +0900 Subject: [PATCH 111/952] Update docs/configuring-playbook-alertmanager-receiver.md: remove duplicated instruction Usage of matrix_alertmanager_receiver_config_matrix_room_mapping is decribed below in the "Adjusting the playbook configuration" much more nicely. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index de374e803..078b7be17 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -34,8 +34,6 @@ For each new room you would like the bot to deliver alerts to, invite the bot to 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. -You may optionally adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID. It provides cleaner `/alert/` URLs. - ## Adjusting the playbook configuration 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](#get-an-access-token). From bfc6bf16d6862dd953ab957b55cd2716b7f7d75a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 17 Dec 2024 17:16:58 +0000 Subject: [PATCH 112/952] chore(deps): update vectorim/element-web docker tag to v1.11.88 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 148c8e674..c6c866d13 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.87 +matrix_client_element_version: v1.11.88 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" From a691b20cf2630f098ee6daf0805ea39f6939001c Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Tue, 17 Dec 2024 22:56:30 +0100 Subject: [PATCH 113/952] Update Mjolnir from 1.9.0 to 1.9.1 --- roles/custom/matrix-bot-mjolnir/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml index b1615c7b8..9f7fea28c 100644 --- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml +++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_mjolnir_enabled: true # renovate: datasource=docker depName=matrixdotorg/mjolnir -matrix_bot_mjolnir_version: "v1.9.0" +matrix_bot_mjolnir_version: "v1.9.1" matrix_bot_mjolnir_container_image_self_build: false matrix_bot_mjolnir_container_image_self_build_repo: "https://github.com/matrix-org/mjolnir.git" From 6a124f15b34376b75c68d9ee8815b47b1f28029a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 18 Dec 2024 06:27:54 +0000 Subject: [PATCH 114/952] chore(deps): update docker.io/metio/matrix-alertmanager-receiver docker tag to v2024.12.18 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index eeac37255..05e9c9705 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -6,7 +6,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2024.12.11 +matrix_alertmanager_receiver_version: 2024.12.18 matrix_alertmanager_receiver_scheme: https From a8372f3613d88fc8ddad4113569395d685b8625b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 18 Dec 2024 16:46:12 +0900 Subject: [PATCH 115/952] Edit docs/configuring-playbook-bridge-hookshot.md and two other documents about installing instruction (#3886) * Edit docs/configuring-playbook-bridge-hookshot.md: fix anchor links to "main.yml" Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: create "Adjusting the playbook configuration" section Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: split "End-to-bridge encryption" section Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: remove two items from the list Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: move "matrix_hookshot_github_private_key" to the playbook configuration adjustment section Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: create the "Installing" section Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: create the "extending the configuration" section This follows fea8df5ca2d5db2208370c891b1e0b5919b09324. Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: add a blank line Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: clarify when it is needed to download the private key file of a GitHub app Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: edit the instruction to add configuration to vars.yml file Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: replace "Important" with "Note" Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: capitalization Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: use the common instruction for sending a message for the help menu Follow docs/configuring-playbook-bridge-postmoogle.md Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: small edits Signed-off-by: Suguru Hirahara * Edit installing instructions: replace setup-SERVICE with setup-all along with just shortcuts with "install-service" Signed-off-by: Suguru Hirahara * Edit docs/configuring-playbook-bridge-hookshot.md: add optional label to GitHub private key instruction Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 78 ++++++++++++++----- docs/configuring-playbook-email2matrix.md | 9 ++- ...ring-playbook-user-verification-service.md | 9 ++- 3 files changed, 67 insertions(+), 29 deletions(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 6fcd29adf..7df6f4992 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -2,31 +2,58 @@ The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you. -Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, JIRA, and Figma, as well as generic webhooks. +Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks. See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you. **Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author. -## Setup Instructions +## Prerequisites -Refer to the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) to learn what the individual options do. +### Download GitHub app private key (optional) -1. Enable the bridge by adding `matrix_hookshot_enabled: true` to your `vars.yml` file -2. For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required. -3. Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab, Generic), while you must first add the required configuration and enable the others (GitHub, Jira, Figma). -4. If you're setting up the GitHub bridge, you'll need to generate and download a private key file after you created your GitHub app. Copy the contents of that file to the variable `matrix_hookshot_github_private_key` so the playbook can install it for you, or use one of the [other methods](#manage-github-private-key-with-aux-role) explained below. -5. If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready. Hookshot can be set up individually using the tag `setup-hookshot`. +If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it. -Other configuration options are available via the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables, see the comments in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) for how to use them. +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). -Finally, run the playbook (see [installing](installing.md)). +## Adjusting the playbook configuration -### End-to-bridge encryption +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). -You can enable [encryption](https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html) for Hookshot by adding `matrix_hookshot_encryption_enabled: true` to your configuration (`vars.yml`) and [executing the playbook](installing.md) again. +```yaml +matrix_hookshot_enabled: true -Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added, for example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-hookshot-encryption`. +# Uncomment to enable end-to-bridge encryption. +# See: https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html +# matrix_hookshot_experimental_encryption_enabled: true + +# Uncomment and paste the contents of GitHub app private key to enable GitHub bridge. +# Alternatively, you can use one of the other methods explained below on the "Manage GitHub Private Key with aux role" section. +# matrix_hookshot_github_private_key: "GITHUB_PRIVATE_KEY_HERE" +``` + +For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required. + +Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma). + +### Extending the configuration + +You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables. + +Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do. + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all` + +`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. ## Usage @@ -34,11 +61,19 @@ To use the bridge, you need to create a room and invite the Hookshot bot (`@hook Make sure the bot is able to send state events (usually the Moderator power level in clients). -Send a `!hookshot help` message to see a list of help commands. +Send `!hookshot help` to the room to see the bridge's help menu for additional commands. Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features. -**Important**: Note that the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation, see [URLs for bridges setup](#urls-for-bridges-setup) below. +💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below. + +### Reset crypto store + +Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=reset-hookshot-encryption +``` ## More setup documentation @@ -46,30 +81,31 @@ Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled). -| listener | default path | variable | used as | +| Listener | Default path | Variable | Used as | |---|---|---|---| | - | `/hookshot/webhooks/` | `matrix_hookshot_webhook_endpoint` | Webhook-prefix, which affects all webhook-related URLs below | | generic | `/hookshot/webhooks/webhook` | `matrix_hookshot_generic_endpoint` | Generic webhooks | | github oauth | `/hookshot/webhooks/oauth` | `matrix_hookshot_github_oauth_endpoint` | GitHub "Callback URL" | -| jira oauth | `/hookshot/webhooks/jira/oauth` | `matrix_hookshot_jira_oauth_endpoint` | JIRA OAuth | +| jira oauth | `/hookshot/webhooks/jira/oauth` | `matrix_hookshot_jira_oauth_endpoint` | Jira OAuth | | figma endpoint | `/hookshot/webhooks/figma/webhook` | `matrix_hookshot_figma_endpoint` | Figma | | provisioning | `/hookshot/v1/` | `matrix_hookshot_provisioning_endpoint` | Dimension [provisioning](#provisioning-api) | | appservice | `/hookshot/_matrix/app/` | `matrix_hookshot_appservice_endpoint` | Matrix server | | widgets | `/hookshot/widgetapi/` | `matrix_hookshot_widgets_endpoint` | Widgets | | metrics | `/metrics/hookshot` | `matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below. | Prometheus | -Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly. +Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly -The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info. +The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info. ### Manage GitHub Private Key with aux role The GitHub bridge requires you to install a private key file. This can be done in multiple ways: -- copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml)). + +- copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml)). - somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually. - use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server. -To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following additional configuration: +To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml aux_file_definitions: diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 910060118..45f928dc7 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -84,16 +84,17 @@ Refer to the official documentation [here](https://github.com/devture/email2matr ## Installing -To enable Email2Matrix, run the playbook with [playbook tags](playbook-tags.md) as below: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-email2matrix,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` **Notes**: -- The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-email2matrix,start` or `just setup-all` +- The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all` - `just run-tags setup-email2matrix,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. + `just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. - After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected. diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 9c7562d00..37802c30a 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -87,15 +87,16 @@ This will instruct UVS to verify the OpenID token against any domain given in a ## Installing -After these variables have been set, run the playbook with [playbook tags](playbook-tags.md) as below to restart UVS: +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-user-verification-service,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` -The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-matrix-user-verification-service,start` or `just setup-all` +The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all` -`just run-tags setup-matrix-user-verification-service,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. +`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. ## Logging From abfb17e8983c5e880c4c51eb8d002658499be640 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 18 Dec 2024 15:53:37 +0000 Subject: [PATCH 116/952] chore(deps): update matrixdotorg/dendrite-monolith docker tag to v0.14.0 --- roles/custom/matrix-dendrite/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml index fd6c50ed5..2484b6660 100644 --- a/roles/custom/matrix-dendrite/defaults/main.yml +++ b/roles/custom/matrix-dendrite/defaults/main.yml @@ -13,7 +13,7 @@ matrix_dendrite_docker_image_path: "matrixdotorg/dendrite-monolith" matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_name_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}" matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else matrix_container_global_registry_prefix }}" # renovate: datasource=docker depName=matrixdotorg/dendrite-monolith -matrix_dendrite_docker_image_tag: "v0.13.8" +matrix_dendrite_docker_image_tag: "v0.14.0" matrix_dendrite_docker_image_force_pull: "{{ matrix_dendrite_docker_image.endswith(':latest') }}" matrix_dendrite_base_path: "{{ matrix_base_data_path }}/dendrite" From b1769c1f395af8a0eb16b554b7ea0437aee55a74 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 18 Dec 2024 19:49:27 +0000 Subject: [PATCH 117/952] chore(deps): update vectorim/element-web docker tag to v1.11.89 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index c6c866d13..8f9c66a67 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.88 +matrix_client_element_version: v1.11.89 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" From 33b493737dc071adab3b82b688083e64ebf257c5 Mon Sep 17 00:00:00 2001 From: Aine <97398200+aine-etke@users.noreply.github.com> Date: Thu, 19 Dec 2024 11:31:16 +0200 Subject: [PATCH 118/952] Synapse Admin v0.10.3-etke35 --- roles/custom/matrix-synapse-admin/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 75661de08..06767753a 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -14,7 +14,7 @@ matrix_synapse_admin_container_image_self_build: false matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git" # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin -matrix_synapse_admin_version: v0.10.3-etke34 +matrix_synapse_admin_version: v0.10.3-etke35 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}" matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}" From d4f8d0918a29ad052f93239f3fcb4e79f317e86a Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 09:37:38 +0200 Subject: [PATCH 119/952] Initial work on translations / localization Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3841 Most of the preparation for this was done by Suguru Hirahara (https://github.com/luixxiul). I've merely reorganized/polished the scripts and instructions in the `i18n/` directory. While translations can happen even now, more work is necessary to - make the translation flow better (integrating Weblate), etc. - restore the Github Actions workflows that Suguru Hirahara had already developed to adapt them to our new workflow --- README.md | 6 + conf.py | 43 + docs/configuring-playbook-matrix-corporal.md | 4 +- i18n/.gitignore | 6 + i18n/PUBLISHED_LANGUAGES | 0 i18n/README.md | 97 + i18n/bin/build-translated-result.sh | 56 + i18n/bin/extract-translation-templates.sh | 34 + .../sync-translation-templates-to-locales.sh | 30 + i18n/justfile | 60 + i18n/locales/bg/LC_MESSAGES/CHANGELOG.po | 11137 ++++++++++++++++ i18n/locales/bg/LC_MESSAGES/README.po | 1374 ++ i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po | 679 + i18n/locales/bg/LC_MESSAGES/docs/README.po | 212 + .../docs/alternative-architectures.po | 78 + i18n/locales/bg/LC_MESSAGES/docs/ansible.po | 284 + .../LC_MESSAGES/docs/configuring-captcha.po | 93 + .../bg/LC_MESSAGES/docs/configuring-dns.po | 410 + ...figuring-playbook-alertmanager-receiver.po | 252 + ...uring-playbook-appservice-double-puppet.po | 108 + ...ng-playbook-appservice-draupnir-for-all.po | 298 + .../docs/configuring-playbook-backup-borg.po | 216 + ...onfiguring-playbook-base-domain-serving.po | 241 + .../docs/configuring-playbook-bot-baibot.po | 688 + .../configuring-playbook-bot-buscarron.po | 188 + .../docs/configuring-playbook-bot-chatgpt.po | 159 + .../docs/configuring-playbook-bot-draupnir.po | 553 + .../docs/configuring-playbook-bot-go-neb.po | 206 + .../docs/configuring-playbook-bot-honoroit.po | 169 + ...ng-playbook-bot-matrix-registration-bot.po | 148 + ...guring-playbook-bot-matrix-reminder-bot.po | 136 + .../docs/configuring-playbook-bot-maubot.po | 214 + .../docs/configuring-playbook-bot-mjolnir.po | 282 + ...ring-playbook-bridge-appservice-discord.po | 247 + ...figuring-playbook-bridge-appservice-irc.po | 103 + ...ng-playbook-bridge-appservice-kakaotalk.po | 230 + ...guring-playbook-bridge-appservice-slack.po | 326 + ...ing-playbook-bridge-appservice-webhooks.po | 157 + ...iguring-playbook-bridge-beeper-linkedin.po | 188 + ...iguring-playbook-bridge-go-skype-bridge.po | 100 + ...onfiguring-playbook-bridge-heisenbridge.po | 185 + .../configuring-playbook-bridge-hookshot.po | 485 + ...uring-playbook-bridge-matrix-bridge-sms.po | 101 + ...iguring-playbook-bridge-mautrix-discord.po | 353 + ...guring-playbook-bridge-mautrix-facebook.po | 287 + ...uring-playbook-bridge-mautrix-gmessages.po | 177 + ...ring-playbook-bridge-mautrix-googlechat.po | 217 + ...guring-playbook-bridge-mautrix-hangouts.po | 214 + ...uring-playbook-bridge-mautrix-instagram.po | 144 + ...-playbook-bridge-mautrix-meta-instagram.po | 296 + ...-playbook-bridge-mautrix-meta-messenger.po | 361 + ...figuring-playbook-bridge-mautrix-signal.po | 267 + ...nfiguring-playbook-bridge-mautrix-slack.po | 289 + ...guring-playbook-bridge-mautrix-telegram.po | 223 + ...iguring-playbook-bridge-mautrix-twitter.po | 190 + ...guring-playbook-bridge-mautrix-whatsapp.po | 213 + ...iguring-playbook-bridge-mautrix-wsproxy.po | 146 + ...uring-playbook-bridge-mx-puppet-discord.po | 140 + ...uring-playbook-bridge-mx-puppet-groupme.po | 124 + ...ing-playbook-bridge-mx-puppet-instagram.po | 138 + ...iguring-playbook-bridge-mx-puppet-skype.po | 42 + ...iguring-playbook-bridge-mx-puppet-slack.po | 137 + ...iguring-playbook-bridge-mx-puppet-steam.po | 117 + ...uring-playbook-bridge-mx-puppet-twitter.po | 131 + .../configuring-playbook-bridge-postmoogle.po | 194 + .../configuring-playbook-bridge-wechat.po | 99 + .../configuring-playbook-cactus-comments.po | 238 + .../docs/configuring-playbook-client-cinny.po | 146 + ...configuring-playbook-client-element-web.po | 236 + .../configuring-playbook-client-hydrogen.po | 123 + ...iguring-playbook-client-schildichat-web.po | 232 + .../docs/configuring-playbook-conduit.po | 138 + .../docs/configuring-playbook-dendrite.po | 152 + .../docs/configuring-playbook-dimension.po | 259 + .../docs/configuring-playbook-dynamic-dns.po | 100 + .../docs/configuring-playbook-email.po | 128 + .../docs/configuring-playbook-email2matrix.po | 259 + .../docs/configuring-playbook-etherpad.po | 251 + .../configuring-playbook-external-postgres.po | 77 + .../docs/configuring-playbook-federation.po | 139 + .../docs/configuring-playbook-jitsi.po | 557 + .../docs/configuring-playbook-ldap-auth.po | 84 + .../docs/configuring-playbook-ma1sd.po | 335 + ...-playbook-matrix-authentication-service.po | 1045 ++ .../configuring-playbook-matrix-corporal.po | 185 + ...playbook-matrix-ldap-registration-proxy.po | 90 + .../configuring-playbook-matrix-media-repo.po | 257 + ...onfiguring-playbook-matrix-registration.po | 219 + .../configuring-playbook-mautrix-bridges.po | 260 + .../docs/configuring-playbook-nginx.po | 31 + .../docs/configuring-playbook-ntfy.po | 355 + .../configuring-playbook-own-webserver.po | 292 + .../docs/configuring-playbook-pantalaimon.po | 93 + .../configuring-playbook-postgres-backup.po | 183 + ...configuring-playbook-prometheus-grafana.po | 513 + ...onfiguring-playbook-prometheus-nginxlog.po | 177 + ...onfiguring-playbook-prometheus-postgres.po | 140 + .../docs/configuring-playbook-rageshake.po | 146 + .../docs/configuring-playbook-rest-auth.po | 86 + .../docs/configuring-playbook-riot-web.po | 130 + .../docs/configuring-playbook-s3-goofys.po | 249 + .../docs/configuring-playbook-s3.po | 315 + ...configuring-playbook-shared-secret-auth.po | 89 + ...configuring-playbook-sliding-sync-proxy.po | 175 + .../configuring-playbook-ssl-certificates.po | 174 + .../docs/configuring-playbook-sygnal.po | 202 + .../configuring-playbook-synapse-admin.po | 207 + ...ing-playbook-synapse-auto-accept-invite.po | 103 + ...guring-playbook-synapse-auto-compressor.po | 109 + ...ng-playbook-synapse-s3-storage-provider.po | 382 + ...guring-playbook-synapse-simple-antispam.po | 52 + ...iguring-playbook-synapse-usage-exporter.po | 157 + .../docs/configuring-playbook-synapse.po | 437 + .../docs/configuring-playbook-telemetry.po | 75 + .../docs/configuring-playbook-traefik.po | 213 + .../docs/configuring-playbook-turn.po | 158 + ...ring-playbook-user-verification-service.po | 312 + .../LC_MESSAGES/docs/configuring-playbook.po | 777 ++ .../docs/configuring-well-known.po | 393 + .../bg/LC_MESSAGES/docs/container-images.po | 1314 ++ i18n/locales/bg/LC_MESSAGES/docs/faq.po | 1355 ++ .../LC_MESSAGES/docs/getting-the-playbook.po | 119 + .../docs/howto-server-delegation.po | 301 + .../docs/howto-srv-server-delegation.po | 219 + .../bg/LC_MESSAGES/docs/importing-postgres.po | 214 + .../docs/importing-synapse-media-store.po | 86 + .../docs/importing-synapse-sqlite.po | 108 + .../locales/bg/LC_MESSAGES/docs/installing.po | 449 + i18n/locales/bg/LC_MESSAGES/docs/just.po | 212 + .../docs/maintenance-and-troubleshooting.po | 125 + .../docs/maintenance-checking-services.po | 55 + .../LC_MESSAGES/docs/maintenance-migrating.po | 196 + .../LC_MESSAGES/docs/maintenance-postgres.po | 336 + .../LC_MESSAGES/docs/maintenance-synapse.po | 310 + .../docs/maintenance-upgrading-services.po | 182 + .../docs/obtaining-access-tokens.po | 122 + .../bg/LC_MESSAGES/docs/playbook-tags.po | 113 + .../bg/LC_MESSAGES/docs/prerequisites.po | 260 + .../bg/LC_MESSAGES/docs/quick-start.po | 615 + .../bg/LC_MESSAGES/docs/registering-users.po | 350 + .../bg/LC_MESSAGES/docs/self-building.po | 201 + .../bg/LC_MESSAGES/docs/uninstalling.po | 106 + .../docs/updating-users-passwords.po | 111 + i18n/locales/bg/LC_MESSAGES/i18n/README.po | 460 + i18n/locales/jp/LC_MESSAGES/CHANGELOG.po | 11136 +++++++++++++++ i18n/locales/jp/LC_MESSAGES/README.po | 1373 ++ i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po | 682 + i18n/locales/jp/LC_MESSAGES/docs/README.po | 211 + .../docs/alternative-architectures.po | 77 + i18n/locales/jp/LC_MESSAGES/docs/ansible.po | 283 + .../LC_MESSAGES/docs/configuring-captcha.po | 92 + .../jp/LC_MESSAGES/docs/configuring-dns.po | 409 + ...figuring-playbook-alertmanager-receiver.po | 251 + ...uring-playbook-appservice-double-puppet.po | 107 + ...ng-playbook-appservice-draupnir-for-all.po | 297 + .../docs/configuring-playbook-backup-borg.po | 215 + ...onfiguring-playbook-base-domain-serving.po | 240 + .../docs/configuring-playbook-bot-baibot.po | 687 + .../configuring-playbook-bot-buscarron.po | 187 + .../docs/configuring-playbook-bot-chatgpt.po | 158 + .../docs/configuring-playbook-bot-draupnir.po | 552 + .../docs/configuring-playbook-bot-go-neb.po | 209 + .../docs/configuring-playbook-bot-honoroit.po | 168 + ...ng-playbook-bot-matrix-registration-bot.po | 147 + ...guring-playbook-bot-matrix-reminder-bot.po | 135 + .../docs/configuring-playbook-bot-maubot.po | 213 + .../docs/configuring-playbook-bot-mjolnir.po | 281 + ...ring-playbook-bridge-appservice-discord.po | 246 + ...figuring-playbook-bridge-appservice-irc.po | 102 + ...ng-playbook-bridge-appservice-kakaotalk.po | 229 + ...guring-playbook-bridge-appservice-slack.po | 325 + ...ing-playbook-bridge-appservice-webhooks.po | 156 + ...iguring-playbook-bridge-beeper-linkedin.po | 187 + ...iguring-playbook-bridge-go-skype-bridge.po | 99 + ...onfiguring-playbook-bridge-heisenbridge.po | 184 + .../configuring-playbook-bridge-hookshot.po | 484 + ...uring-playbook-bridge-matrix-bridge-sms.po | 100 + ...iguring-playbook-bridge-mautrix-discord.po | 352 + ...guring-playbook-bridge-mautrix-facebook.po | 286 + ...uring-playbook-bridge-mautrix-gmessages.po | 176 + ...ring-playbook-bridge-mautrix-googlechat.po | 216 + ...guring-playbook-bridge-mautrix-hangouts.po | 213 + ...uring-playbook-bridge-mautrix-instagram.po | 143 + ...-playbook-bridge-mautrix-meta-instagram.po | 295 + ...-playbook-bridge-mautrix-meta-messenger.po | 360 + ...figuring-playbook-bridge-mautrix-signal.po | 266 + ...nfiguring-playbook-bridge-mautrix-slack.po | 288 + ...guring-playbook-bridge-mautrix-telegram.po | 222 + ...iguring-playbook-bridge-mautrix-twitter.po | 189 + ...guring-playbook-bridge-mautrix-whatsapp.po | 212 + ...iguring-playbook-bridge-mautrix-wsproxy.po | 145 + ...uring-playbook-bridge-mx-puppet-discord.po | 139 + ...uring-playbook-bridge-mx-puppet-groupme.po | 123 + ...ing-playbook-bridge-mx-puppet-instagram.po | 137 + ...iguring-playbook-bridge-mx-puppet-skype.po | 41 + ...iguring-playbook-bridge-mx-puppet-slack.po | 140 + ...iguring-playbook-bridge-mx-puppet-steam.po | 116 + ...uring-playbook-bridge-mx-puppet-twitter.po | 130 + .../configuring-playbook-bridge-postmoogle.po | 197 + .../configuring-playbook-bridge-wechat.po | 98 + .../configuring-playbook-cactus-comments.po | 237 + .../docs/configuring-playbook-client-cinny.po | 145 + ...configuring-playbook-client-element-web.po | 235 + .../configuring-playbook-client-hydrogen.po | 122 + ...iguring-playbook-client-schildichat-web.po | 231 + .../docs/configuring-playbook-conduit.po | 137 + .../docs/configuring-playbook-dendrite.po | 151 + .../docs/configuring-playbook-dimension.po | 258 + .../docs/configuring-playbook-dynamic-dns.po | 99 + .../docs/configuring-playbook-email.po | 127 + .../docs/configuring-playbook-email2matrix.po | 258 + .../docs/configuring-playbook-etherpad.po | 250 + .../configuring-playbook-external-postgres.po | 80 + .../docs/configuring-playbook-federation.po | 138 + .../docs/configuring-playbook-jitsi.po | 556 + .../docs/configuring-playbook-ldap-auth.po | 83 + .../docs/configuring-playbook-ma1sd.po | 334 + ...-playbook-matrix-authentication-service.po | 1044 ++ .../configuring-playbook-matrix-corporal.po | 184 + ...playbook-matrix-ldap-registration-proxy.po | 89 + .../configuring-playbook-matrix-media-repo.po | 256 + ...onfiguring-playbook-matrix-registration.po | 218 + .../configuring-playbook-mautrix-bridges.po | 259 + .../docs/configuring-playbook-nginx.po | 30 + .../docs/configuring-playbook-ntfy.po | 354 + .../configuring-playbook-own-webserver.po | 291 + .../docs/configuring-playbook-pantalaimon.po | 92 + .../configuring-playbook-postgres-backup.po | 182 + ...configuring-playbook-prometheus-grafana.po | 512 + ...onfiguring-playbook-prometheus-nginxlog.po | 176 + ...onfiguring-playbook-prometheus-postgres.po | 139 + .../docs/configuring-playbook-rageshake.po | 145 + .../docs/configuring-playbook-rest-auth.po | 89 + .../docs/configuring-playbook-riot-web.po | 129 + .../docs/configuring-playbook-s3-goofys.po | 248 + .../docs/configuring-playbook-s3.po | 314 + ...configuring-playbook-shared-secret-auth.po | 88 + ...configuring-playbook-sliding-sync-proxy.po | 174 + .../configuring-playbook-ssl-certificates.po | 173 + .../docs/configuring-playbook-sygnal.po | 201 + .../configuring-playbook-synapse-admin.po | 206 + ...ing-playbook-synapse-auto-accept-invite.po | 102 + ...guring-playbook-synapse-auto-compressor.po | 108 + ...ng-playbook-synapse-s3-storage-provider.po | 381 + ...guring-playbook-synapse-simple-antispam.po | 51 + ...iguring-playbook-synapse-usage-exporter.po | 156 + .../docs/configuring-playbook-synapse.po | 436 + .../docs/configuring-playbook-telemetry.po | 74 + .../docs/configuring-playbook-traefik.po | 212 + .../docs/configuring-playbook-turn.po | 157 + ...ring-playbook-user-verification-service.po | 311 + .../LC_MESSAGES/docs/configuring-playbook.po | 776 ++ .../docs/configuring-well-known.po | 396 + .../jp/LC_MESSAGES/docs/container-images.po | 1313 ++ i18n/locales/jp/LC_MESSAGES/docs/faq.po | 1354 ++ .../LC_MESSAGES/docs/getting-the-playbook.po | 118 + .../docs/howto-server-delegation.po | 300 + .../docs/howto-srv-server-delegation.po | 218 + .../jp/LC_MESSAGES/docs/importing-postgres.po | 213 + .../docs/importing-synapse-media-store.po | 85 + .../docs/importing-synapse-sqlite.po | 111 + .../locales/jp/LC_MESSAGES/docs/installing.po | 448 + i18n/locales/jp/LC_MESSAGES/docs/just.po | 211 + .../docs/maintenance-and-troubleshooting.po | 124 + .../docs/maintenance-checking-services.po | 54 + .../LC_MESSAGES/docs/maintenance-migrating.po | 195 + .../LC_MESSAGES/docs/maintenance-postgres.po | 335 + .../LC_MESSAGES/docs/maintenance-synapse.po | 309 + .../docs/maintenance-upgrading-services.po | 185 + .../docs/obtaining-access-tokens.po | 121 + .../jp/LC_MESSAGES/docs/playbook-tags.po | 112 + .../jp/LC_MESSAGES/docs/prerequisites.po | 259 + .../jp/LC_MESSAGES/docs/quick-start.po | 614 + .../jp/LC_MESSAGES/docs/registering-users.po | 349 + .../jp/LC_MESSAGES/docs/self-building.po | 200 + .../jp/LC_MESSAGES/docs/uninstalling.po | 105 + .../docs/updating-users-passwords.po | 110 + i18n/locales/jp/LC_MESSAGES/i18n/README.po | 446 + i18n/requirements.txt | 33 + i18n/translation-templates/CHANGELOG.pot | 6971 ++++++++++ i18n/translation-templates/README.pot | 1165 ++ i18n/translation-templates/YEAR-IN-REVIEW.pot | 289 + i18n/translation-templates/docs/README.pot | 169 + .../docs/alternative-architectures.pot | 57 + i18n/translation-templates/docs/ansible.pot | 180 + .../docs/configuring-captcha.pot | 75 + .../docs/configuring-dns.pot | 341 + ...iguring-playbook-alertmanager-receiver.pot | 161 + ...ring-playbook-appservice-double-puppet.pot | 73 + ...g-playbook-appservice-draupnir-for-all.pot | 185 + .../docs/configuring-playbook-backup-borg.pot | 137 + ...nfiguring-playbook-base-domain-serving.pot | 157 + .../docs/configuring-playbook-bot-baibot.pot | 424 + .../configuring-playbook-bot-buscarron.pot | 129 + .../docs/configuring-playbook-bot-chatgpt.pot | 113 + .../configuring-playbook-bot-draupnir.pot | 350 + .../docs/configuring-playbook-bot-go-neb.pot | 145 + .../configuring-playbook-bot-honoroit.pot | 117 + ...g-playbook-bot-matrix-registration-bot.pot | 97 + ...uring-playbook-bot-matrix-reminder-bot.pot | 93 + .../docs/configuring-playbook-bot-maubot.pot | 141 + .../docs/configuring-playbook-bot-mjolnir.pot | 183 + ...ing-playbook-bridge-appservice-discord.pot | 166 + ...iguring-playbook-bridge-appservice-irc.pot | 73 + ...g-playbook-bridge-appservice-kakaotalk.pot | 157 + ...uring-playbook-bridge-appservice-slack.pot | 242 + ...ng-playbook-bridge-appservice-webhooks.pot | 109 + ...guring-playbook-bridge-beeper-linkedin.pot | 125 + ...guring-playbook-bridge-go-skype-bridge.pot | 73 + ...nfiguring-playbook-bridge-heisenbridge.pot | 125 + .../configuring-playbook-bridge-hookshot.pot | 361 + ...ring-playbook-bridge-matrix-bridge-sms.pot | 73 + ...guring-playbook-bridge-mautrix-discord.pot | 241 + ...uring-playbook-bridge-mautrix-facebook.pot | 197 + ...ring-playbook-bridge-mautrix-gmessages.pot | 125 + ...ing-playbook-bridge-mautrix-googlechat.pot | 145 + ...uring-playbook-bridge-mautrix-hangouts.pot | 145 + ...ring-playbook-bridge-mautrix-instagram.pot | 97 + ...playbook-bridge-mautrix-meta-instagram.pot | 205 + ...playbook-bridge-mautrix-meta-messenger.pot | 241 + ...iguring-playbook-bridge-mautrix-signal.pot | 193 + ...figuring-playbook-bridge-mautrix-slack.pot | 193 + ...uring-playbook-bridge-mautrix-telegram.pot | 149 + ...guring-playbook-bridge-mautrix-twitter.pot | 129 + ...uring-playbook-bridge-mautrix-whatsapp.pot | 145 + ...guring-playbook-bridge-mautrix-wsproxy.pot | 101 + ...ring-playbook-bridge-mx-puppet-discord.pot | 97 + ...ring-playbook-bridge-mx-puppet-groupme.pot | 89 + ...ng-playbook-bridge-mx-puppet-instagram.pot | 101 + ...guring-playbook-bridge-mx-puppet-skype.pot | 29 + ...guring-playbook-bridge-mx-puppet-slack.pot | 97 + ...guring-playbook-bridge-mx-puppet-steam.pot | 85 + ...ring-playbook-bridge-mx-puppet-twitter.pot | 97 + ...configuring-playbook-bridge-postmoogle.pot | 137 + .../configuring-playbook-bridge-wechat.pot | 73 + .../configuring-playbook-cactus-comments.pot | 165 + .../configuring-playbook-client-cinny.pot | 97 + ...onfiguring-playbook-client-element-web.pot | 145 + .../configuring-playbook-client-hydrogen.pot | 85 + ...guring-playbook-client-schildichat-web.pot | 141 + .../docs/configuring-playbook-conduit.pot | 93 + .../docs/configuring-playbook-dendrite.pot | 89 + .../docs/configuring-playbook-dimension.pot | 157 + .../docs/configuring-playbook-dynamic-dns.pot | 73 + .../docs/configuring-playbook-email.pot | 85 + .../configuring-playbook-email2matrix.pot | 177 + .../docs/configuring-playbook-etherpad.pot | 169 + ...configuring-playbook-external-postgres.pot | 45 + .../docs/configuring-playbook-federation.pot | 85 + .../docs/configuring-playbook-jitsi.pot | 361 + .../docs/configuring-playbook-ldap-auth.pot | 57 + .../docs/configuring-playbook-ma1sd.pot | 209 + ...playbook-matrix-authentication-service.pot | 618 + .../configuring-playbook-matrix-corporal.pot | 121 + ...laybook-matrix-ldap-registration-proxy.pot | 61 + ...configuring-playbook-matrix-media-repo.pot | 164 + ...nfiguring-playbook-matrix-registration.pot | 153 + .../configuring-playbook-mautrix-bridges.pot | 178 + .../docs/configuring-playbook-nginx.pot | 25 + .../docs/configuring-playbook-ntfy.pot | 233 + .../configuring-playbook-own-webserver.pot | 189 + .../docs/configuring-playbook-pantalaimon.pot | 61 + .../configuring-playbook-postgres-backup.pot | 153 + ...onfiguring-playbook-prometheus-grafana.pot | 341 + ...nfiguring-playbook-prometheus-nginxlog.pot | 109 + ...nfiguring-playbook-prometheus-postgres.pot | 101 + .../docs/configuring-playbook-rageshake.pot | 101 + .../docs/configuring-playbook-rest-auth.pot | 61 + .../docs/configuring-playbook-riot-web.pot | 89 + .../docs/configuring-playbook-s3-goofys.pot | 178 + .../docs/configuring-playbook-s3.pot | 213 + ...onfiguring-playbook-shared-secret-auth.pot | 61 + ...onfiguring-playbook-sliding-sync-proxy.pot | 113 + .../configuring-playbook-ssl-certificates.pot | 118 + .../docs/configuring-playbook-sygnal.pot | 129 + .../configuring-playbook-synapse-admin.pot | 121 + ...ng-playbook-synapse-auto-accept-invite.pot | 65 + ...uring-playbook-synapse-auto-compressor.pot | 73 + ...g-playbook-synapse-s3-storage-provider.pot | 253 + ...uring-playbook-synapse-simple-antispam.pot | 37 + ...guring-playbook-synapse-usage-exporter.pot | 105 + .../docs/configuring-playbook-synapse.pot | 253 + .../docs/configuring-playbook-telemetry.pot | 49 + .../docs/configuring-playbook-traefik.pot | 134 + .../docs/configuring-playbook-turn.pot | 105 + ...ing-playbook-user-verification-service.pot | 213 + .../docs/configuring-playbook.pot | 529 + .../docs/configuring-well-known.pot | 253 + .../docs/container-images.pot | 1153 ++ i18n/translation-templates/docs/faq.pot | 874 ++ .../docs/getting-the-playbook.pot | 81 + .../docs/howto-server-delegation.pot | 185 + .../docs/howto-srv-server-delegation.pot | 145 + .../docs/importing-postgres.pot | 145 + .../docs/importing-synapse-media-store.pot | 57 + .../docs/importing-synapse-sqlite.pot | 73 + .../translation-templates/docs/installing.pot | 301 + i18n/translation-templates/docs/just.pot | 158 + .../docs/maintenance-and-troubleshooting.pot | 89 + .../docs/maintenance-checking-services.pot | 41 + .../docs/maintenance-migrating.pot | 133 + .../docs/maintenance-postgres.pot | 217 + .../docs/maintenance-synapse.pot | 193 + .../docs/maintenance-upgrading-services.pot | 125 + .../docs/obtaining-access-tokens.pot | 93 + .../docs/playbook-tags.pot | 73 + .../docs/prerequisites.pot | 161 + .../docs/quick-start.pot | 429 + .../docs/registering-users.pot | 242 + .../docs/self-building.pot | 173 + .../docs/uninstalling.pot | 77 + .../docs/updating-users-passwords.pot | 85 + i18n/translation-templates/i18n/README.pot | 216 + 413 files changed, 119935 insertions(+), 2 deletions(-) create mode 100644 conf.py create mode 100644 i18n/.gitignore create mode 100644 i18n/PUBLISHED_LANGUAGES create mode 100644 i18n/README.md create mode 100755 i18n/bin/build-translated-result.sh create mode 100755 i18n/bin/extract-translation-templates.sh create mode 100755 i18n/bin/sync-translation-templates-to-locales.sh create mode 100644 i18n/justfile create mode 100644 i18n/locales/bg/LC_MESSAGES/CHANGELOG.po create mode 100644 i18n/locales/bg/LC_MESSAGES/README.po create mode 100644 i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/README.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/ansible.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/container-images.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/faq.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/installing.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/just.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/quick-start.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/registering-users.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/self-building.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po create mode 100644 i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po create mode 100644 i18n/locales/bg/LC_MESSAGES/i18n/README.po create mode 100644 i18n/locales/jp/LC_MESSAGES/CHANGELOG.po create mode 100644 i18n/locales/jp/LC_MESSAGES/README.po create mode 100644 i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/README.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/ansible.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/container-images.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/faq.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/installing.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/just.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/quick-start.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/registering-users.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/self-building.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po create mode 100644 i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po create mode 100644 i18n/locales/jp/LC_MESSAGES/i18n/README.po create mode 100644 i18n/requirements.txt create mode 100644 i18n/translation-templates/CHANGELOG.pot create mode 100644 i18n/translation-templates/README.pot create mode 100644 i18n/translation-templates/YEAR-IN-REVIEW.pot create mode 100644 i18n/translation-templates/docs/README.pot create mode 100644 i18n/translation-templates/docs/alternative-architectures.pot create mode 100644 i18n/translation-templates/docs/ansible.pot create mode 100644 i18n/translation-templates/docs/configuring-captcha.pot create mode 100644 i18n/translation-templates/docs/configuring-dns.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-backup-borg.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-client-cinny.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-client-element-web.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-conduit.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-dendrite.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-dimension.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-email.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-email2matrix.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-etherpad.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-external-postgres.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-federation.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-jitsi.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-ma1sd.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-nginx.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-ntfy.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-own-webserver.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-rageshake.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-rest-auth.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-riot-web.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-s3.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-sygnal.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-synapse.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-telemetry.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-traefik.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-turn.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot create mode 100644 i18n/translation-templates/docs/configuring-playbook.pot create mode 100644 i18n/translation-templates/docs/configuring-well-known.pot create mode 100644 i18n/translation-templates/docs/container-images.pot create mode 100644 i18n/translation-templates/docs/faq.pot create mode 100644 i18n/translation-templates/docs/getting-the-playbook.pot create mode 100644 i18n/translation-templates/docs/howto-server-delegation.pot create mode 100644 i18n/translation-templates/docs/howto-srv-server-delegation.pot create mode 100644 i18n/translation-templates/docs/importing-postgres.pot create mode 100644 i18n/translation-templates/docs/importing-synapse-media-store.pot create mode 100644 i18n/translation-templates/docs/importing-synapse-sqlite.pot create mode 100644 i18n/translation-templates/docs/installing.pot create mode 100644 i18n/translation-templates/docs/just.pot create mode 100644 i18n/translation-templates/docs/maintenance-and-troubleshooting.pot create mode 100644 i18n/translation-templates/docs/maintenance-checking-services.pot create mode 100644 i18n/translation-templates/docs/maintenance-migrating.pot create mode 100644 i18n/translation-templates/docs/maintenance-postgres.pot create mode 100644 i18n/translation-templates/docs/maintenance-synapse.pot create mode 100644 i18n/translation-templates/docs/maintenance-upgrading-services.pot create mode 100644 i18n/translation-templates/docs/obtaining-access-tokens.pot create mode 100644 i18n/translation-templates/docs/playbook-tags.pot create mode 100644 i18n/translation-templates/docs/prerequisites.pot create mode 100644 i18n/translation-templates/docs/quick-start.pot create mode 100644 i18n/translation-templates/docs/registering-users.pot create mode 100644 i18n/translation-templates/docs/self-building.pot create mode 100644 i18n/translation-templates/docs/uninstalling.pot create mode 100644 i18n/translation-templates/docs/updating-users-passwords.pot create mode 100644 i18n/translation-templates/i18n/README.pot diff --git a/README.md b/README.md index 4482f2049..1e487cd92 100644 --- a/README.md +++ b/README.md @@ -198,6 +198,12 @@ When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up w - GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues) +## 🌐 Translation + +See the [i18n/README.md](i18n/README.md) file for more information about translation. + +Translations are still work in progress. + ## 🤝 Related You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md)). diff --git a/conf.py b/conf.py new file mode 100644 index 000000000..a36a20f4d --- /dev/null +++ b/conf.py @@ -0,0 +1,43 @@ +# Configuration file for the Sphinx documentation builder. +# Also see the `i18n/` directory. +# +# For the full list of built-in configuration values, see the documentation: +# https://www.sphinx-doc.org/en/master/usage/configuration.html + +# -- Project information ----------------------------------------------------- +# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information + +project = 'matrix-docker-ansible-deploy' +copyright = '2018-%Y, Slavi Pantaleev, Aine Etke, MDAD community members' +author = 'Slavi Pantaleev, Aine Etke, MDAD community members' + +# -- General configuration --------------------------------------------------- +# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration + +needs_sphinx = '8.1' # For the copyright year placeholder (%Y). Specified with pyproject.toml as well. + +extensions = [ + 'myst_parser', + 'sphinx_markdown_builder' +] +myst_gfm_only = True +myst_heading_anchors = 4 # https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#auto-generated-header-anchors + +master_doc = 'README' +source_suffix = {'.md': 'markdown'} + +# Though the default config file advocates exclude_patterns, it is straightforward for us to use include_patterns to select directories explicitly. +include_patterns = [ + 'docs/*', + 'i18n/README.md', + '*.md', +] + +locale_dirs = ['i18n/locales/'] +gettext_compact = False + +# -- Options for HTML output ------------------------------------------------- +# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output + +# html_theme = 'alabaster' +# html_static_path = ['_static'] diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 1e23e899a..ef9ab2d1b 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -1,10 +1,10 @@ # Setting up Matrix Corporal (optional, advanced) -------------------------------------- +
**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. -------------------------------------- +
The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you. diff --git a/i18n/.gitignore b/i18n/.gitignore new file mode 100644 index 000000000..e3430f08a --- /dev/null +++ b/i18n/.gitignore @@ -0,0 +1,6 @@ +.venv/ +doctrees +.doctrees/ +.mo + +/translated/* diff --git a/i18n/PUBLISHED_LANGUAGES b/i18n/PUBLISHED_LANGUAGES new file mode 100644 index 000000000..e69de29bb diff --git a/i18n/README.md b/i18n/README.md new file mode 100644 index 000000000..f5a1b5fa7 --- /dev/null +++ b/i18n/README.md @@ -0,0 +1,97 @@ +# Internationalization + +Translated documentation files are published and maintained in [`translated/`](translated/) directory. + +Currently, we support translation of: + +- Markdown files found at the top level project directory +- Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is) +- this current document in the `i18n` directory + +💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated). + +Organization of this `i18n` directory is as follows: + +- [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory) +- [.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold. +- [justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner +- [requirements.txt](requirements.txt): a list of Python packages required to work with translations +- [translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files +- [locales/](locales/): localization files for languages +- [translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language)) + +## Guide for translators + +This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents. + +For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well. + +For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface. + +### (Recommended) Using the uv package manager and just command runner + +If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents. + +The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it. + +#### Preparation + +Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed. + +#### Translation + +Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`): + +- Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date) + +- Use an editor to translate the files in the `locales/` directory + +- Build translated documents: `just build-for-language ` + +- Preview the result in the `translated/` directory + +- Commit your changes done to the `locales/` directory + +- If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language) + +### Using any other package manager and manual scripts + +If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can: + +- manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.) +- manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory + +#### Preparation + +##### virtualenv and pip + +- Create a Python virtual environment in the `.venv` directory: `virtualenv .venv` +- Activate the virtual environment: `source .venv/bin/activate` +- Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt` + +#### Translation + +Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`): + +- Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh` + +- Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh ` + +- Use an editor to translate the files in the `locales/` directory + +- Build translated documents: `./bin/build-translated-result.sh ` + +- Preview the result in the `translated/` directory + +- Commit your changes done to the `locales/` directory + +- If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language) + +### Publish translations in a new language + +To publish prebuilt documents translated in a new language to the `translated/` directory: + +- add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file +- whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file + +💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file. diff --git a/i18n/bin/build-translated-result.sh b/i18n/bin/build-translated-result.sh new file mode 100755 index 000000000..6695714ec --- /dev/null +++ b/i18n/bin/build-translated-result.sh @@ -0,0 +1,56 @@ +#!/bin/bash + +# This script builds the translated result (translated project) for a given language in the `translated//` directory. + +set -euxo pipefail + +if [ $# -ne 1 ]; then + echo "Usage: $0 " + exit 1 +fi + +LANGUAGE=$1 + +base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)" + +if [ ! -f ${base_path}/i18n/locales/${LANGUAGE}/LC_MESSAGES/README.po ]; then + echo "Locales for ${LANGUAGE} not found. Please run the `sync-translation-templates-to-locales.sh` script first." + exit 1 +fi + +# Prepare a clean build directory +if [ -d ${base_path}/i18n/translated-result-build-${LANGUAGE} ]; then + rm -rf ${base_path}/i18n/translated-result-build-${LANGUAGE} +fi +mkdir -p ${base_path}/i18n/translated-result-build-${LANGUAGE} + +# Build the translated documentation +sphinx-build \ + -b markdown \ + -D language="${LANGUAGE}" \ + ${base_path}/ \ + ${base_path}/i18n/translated-result-build-${LANGUAGE} + +# Clean up .mo files produced during the build. +# We don't commit them to the repository anyway, so they can be left alone, +# but we'd rather keep things clean anyway. +find ${base_path}/i18n/locales/${LANGUAGE} -type f -name '*.mo' -delete + +# Clean up the build directory +rm -rf ${base_path}/i18n/translated-result-build-${LANGUAGE}/.doctrees + +# Copy assets +cp -r ${base_path}/docs/assets ${base_path}/i18n/translated-result-build-${LANGUAGE}/docs/assets/ + +# Remove the old result directory for this language +if [ -d ${base_path}/i18n/translated/${LANGUAGE} ]; then + rm -rf ${base_path}/i18n/translated/${LANGUAGE} +fi + +# Make sure the `translated/` directory exists +if [ ! -d ${base_path}/i18n/translated ]; then + mkdir -p ${base_path}/i18n/translated +fi + +# Relocate the built result to translated/ +mv ${base_path}/i18n/translated-result-build-${LANGUAGE} ${base_path}/i18n/translated/${LANGUAGE} diff --git a/i18n/bin/extract-translation-templates.sh b/i18n/bin/extract-translation-templates.sh new file mode 100755 index 000000000..02abbcece --- /dev/null +++ b/i18n/bin/extract-translation-templates.sh @@ -0,0 +1,34 @@ +#!/bin/bash + +# This script extracts translation templates (original English strings) into the `translation-templates/` directory. +# These templates are later used to generate locale files for each language in the `locales/` directory. +# +# By default `sphinx-build` extracts the templates into a `build/gettext` directory, while we'd like to have them in the `translation-templates/` directory. +# To avoid the `POT-Creation-Date` information in templates being updated every time we extract them, +# we restore the `translation-templates/` directory to the `build/gettext` directory before running the script. + +set -euxo pipefail + +base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)" + +# Restore the `translation-templates/` directory to the `build/gettext` directory +if [ -d ${base_path}/i18n/build ]; then + rm -rf ${base_path}/i18n/build +fi +mkdir -p ${base_path}/i18n/build +cp -r ${base_path}/i18n/translation-templates ${base_path}/i18n/build/gettext + +# Extract translation templates from the documentation into the `build/gettext` directory +sphinx-build -M gettext ${base_path} ${base_path}/i18n/build + +# Clean up the build directory +rm -rf ${base_path}/i18n/build/gettext/.doctrees + +# Update the `translation-templates/` directory with the new templates +if [ -d ${base_path}/i18n/translation-templates ]; then + rm -rf ${base_path}/i18n/translation-templates +fi +mv ${base_path}/i18n/build/gettext ${base_path}/i18n/translation-templates + +# Get rid of the `build` directory +rmdir ${base_path}/i18n/build diff --git a/i18n/bin/sync-translation-templates-to-locales.sh b/i18n/bin/sync-translation-templates-to-locales.sh new file mode 100755 index 000000000..7d33921ce --- /dev/null +++ b/i18n/bin/sync-translation-templates-to-locales.sh @@ -0,0 +1,30 @@ +#!/bin/bash + +# This script updates the translation files (locales//**/*.po) for a given language. +# It uses the translation templates (translation-templates/**/*.pot) to generate the translation files. + +set -euxo pipefail + +if [ $# -ne 1 ]; then + echo "Usage: $0 " + exit 1 +fi + +LANGUAGE=$1 + +base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)" + +if [ ! -f ${base_path}/i18n/translation-templates/README.pot ]; then + echo "Translation templates not found. Please run the `extract-translation-templates.sh` script first." + exit 1 +fi + +# Create necessary directories to avoid race conditions caused by +# Sphinx potentially trying to concurrently create them from separate threads below. +mkdir -p ${base_path}/i18n/locales/${LANGUAGE}/LC_MESSAGES/docs + +# Update the translation files +sphinx-intl update \ + --pot-dir ${base_path}/i18n/translation-templates \ + --locale-dir ${base_path}/i18n/locales \ + --language ${LANGUAGE} diff --git a/i18n/justfile b/i18n/justfile new file mode 100644 index 000000000..4021dfabb --- /dev/null +++ b/i18n/justfile @@ -0,0 +1,60 @@ +# Shows help +default: + @just --list --justfile {{ justfile() }} + +# Extracts original English strings (translation templates) into the `translation-templates/` directory +extract-translation-templates: _venv + @echo "Extracting translation templates..." + PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/extract-translation-templates.sh + +# Syncs the translation templates (affects `translation-templates/`) and strings (affects `locales/*`) for all published languages (`PUBLISHED_LANGUAGES`) +sync-for-all-published-languages: _venv + #!/bin/sh + cat {{ justfile_directory() }}/PUBLISHED_LANGUAGES | while read language ; do + {{ just_executable() }} sync-for-language $language + done + +# Syncs the translation templates (affects `translation-templates/`) and strings for all known languages (`KNOWN_LANGUAGES`) +sync-for-all-known-languages: + #!/bin/sh + find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do + language=$(basename "$path") + echo "Syncing for language $language.." + {{ just_executable() }} sync-for-language $language + done + +# Updates the translation templates (affects `translation-templates/`) and syncs the translation strings for a given language (affects `locales/{{ language }}`) +sync-for-language language: extract-translation-templates (_sync-translation-templates-to-locales-for-language language) + +# Updates `locales/{{ language }}` files based on the original template strings from `translation-templates/` +_sync-translation-templates-to-locales-for-language language: _venv + PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/sync-translation-templates-to-locales.sh {{ language }} + +# Builds the translated result for a given language into the `translated/{{ language }}` directory +build-for-language language: _venv + PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/build-translated-result.sh {{ language }} + +# Builds the translated result for all published languages into the `translated/` directory +build-for-all-published-languages: + #!/bin/sh + cat {{ justfile_directory() }}/PUBLISHED_LANGUAGES | while read language ; do + {{ just_executable() }} build-for-language $language + done + +# Builds the translated result for all known languages into the `translated/` directory +build-for-all-known-languages: + #!/bin/sh + find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do + language=$(basename "$path") + echo "Building for language $language.." + {{ just_executable() }} build-for-language $language + done + +# Creates the virtual environment and installs the required Python packages +_venv: + #!/bin/sh + if [ ! -f {{ justfile_directory() }}/.venv/bin/sphinx-build ]; then + echo "No sphinx-build found, creating virtual environment and installing requirements..." + uv venv {{ justfile_directory() }}/.venv + VIRTUAL_ENV={{ justfile_directory() }}/.venv uv pip install -r {{ justfile_directory() }}/requirements.txt + fi diff --git a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po new file mode 100644 index 000000000..a293d80bd --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po @@ -0,0 +1,11137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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" + +#: ../../../CHANGELOG.md:1 +msgid "2024-11-26" +msgstr "" + +#: ../../../CHANGELOG.md:3 +msgid "" +"(Backward Compatibility Break) Synapse now defaults to enabling " +"authenticated media" +msgstr "" + +#: ../../../CHANGELOG.md:5 +msgid "" +"**TLDR**: with this update, your Synapse homeserver will start requiring " +"authentication for newly-uploaded media files. While the majority of the " +"ecosystem (clients, bots, etc.) should support this, certain software may" +" lack support for it (and you may wish to turn it off, if it's causing " +"issues)." +msgstr "" + +#: ../../../CHANGELOG.md:7 +msgid "" +"The default configuration for the Synapse homeserver now [enforces " +"Authenticated media by default](https://element-" +"hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-" +"enforced-by-default)." +msgstr "" + +#: ../../../CHANGELOG.md:9 +msgid "" +"Servers like `matrix.org` have already [sunset unauthenticated " +"media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-" +"media/) months ago." +msgstr "" + +#: ../../../CHANGELOG.md:11 +msgid "" +"Now that **various clients, bots, bridges and extra services have caught " +"up with authenticated media support**, Synapse developers seem confident " +"that it's time to enable authenticated media by default." +msgstr "" + +#: ../../../CHANGELOG.md:13 +msgid "" +"We're changing the playbook configuration for authenticated media to keep" +" up with upstream defaults changing." +msgstr "" + +#: ../../../CHANGELOG.md:15 +msgid "" +"Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not " +"support authenticated media. Other software may be similarly affected. If" +" you experience issues with some Matrix-related software, you may wish to" +" disable authenticated media and contact the software maintainers to let " +"them know." +msgstr "" + +#: ../../../CHANGELOG.md:17 +msgid "" +"You can disable authenticated media at any time by setting " +"`matrix_synapse_enable_authenticated_media: false` in your `vars.yml` " +"configuration file and re-running the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:20 +msgid "2024-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:22 +msgid "" +"(Backward Compatibility Break) The playbook now defaults to Valkey, " +"instead of KeyDB" +msgstr "" + +#: ../../../CHANGELOG.md:24 +msgid "" +"**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for " +"you before, it will now replace it with [Valkey](https://valkey.io/) (a " +"drop-in alternative). We [previously switched from Redis to KeyDB" +"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" +"instead-of-redis), but Valkey is a better alternative, so we're switching" +" again." +msgstr "" + +#: ../../../CHANGELOG.md:26 +msgid "" +"The playbook used to install Redis or KeyDB if services have a need for a" +" Redis-compatible implementation ([enabling worker support for " +"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" +"workers), [enabling Hookshot encryption](docs/configuring-playbook-" +"bridge-hookshot.md#end-to-bridge-encryption), etc.)." +msgstr "" + +#: ../../../CHANGELOG.md:28 +msgid "" +"Earlier this year, we switched from Redis to KeyDB - see [(Backward " +"Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" +"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" +"instead-of-redis)." +msgstr "" + +#: ../../../CHANGELOG.md:30 +msgid "" +"Because Valkey seems to be a better successor to Redis (than KeyDB) and " +"likely doesn't suffer from [issues like this " +"one](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3544), we now replace KeyDB with Valkey." +msgstr "" + +#: ../../../CHANGELOG.md:32 +msgid "" +"Valkey (like KeyDB and Redis in the past) is an implicitly enabled " +"dependency - you don't need custom configuration in `vars.yml` to enable " +"it." +msgstr "" + +#: ../../../CHANGELOG.md:34 +msgid "" +"Next time your run the playbook (via the `setup-all` tag), **KeyDB will " +"be automatically uninstalled and replaced with Valkey**. Some Synapse " +"downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:36 +msgid "" +"Users on `arm32` should be aware that there's **neither a prebuilt " +"`arm32` container image for Valkey**, nor the Valkey role supports self-" +"building yet. Users on this architecture likely don't run Synapse with " +"workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). " +"If Redis is necessary in an `arm32` deployment, disabling Valkey and " +"making the playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378 +msgid "" +"**The playbook still supports Redis** and you can keep using Redis (for " +"now) if you'd like, by adding this additional configuration to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:49 +msgid "" +"**The playbook still supports KeyDB** and you can keep using KeyDB (for " +"now) if you'd like, by adding this additional configuration to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:59 +msgid "" +"At some point in time in the future, we'll remove both KeyDB and Redis " +"from the playbook, so we recommend that you migrate to Valkey earlier " +"anyway." +msgstr "" + +#: ../../../CHANGELOG.md:62 +msgid "2024-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:64 +msgid "HTTP-compression support for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:66 +msgid "" +"The playbook now **automatically enables HTTP-compression support** for " +"major services powered by the playbook, like [Cinny](./docs/configuring-" +"playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-" +"client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-" +"hydrogen.md), as well as for Matrix Client-Server and Federation APIs " +"(`matrix.example.com`)." +msgstr "" + +#: ../../../CHANGELOG.md:68 +msgid "" +"Other services installed by the playbook are currently not compression-" +"enabled, but may become so over time. This change is rolled out on a per-" +"service basis (as opposed to doing it globally, at the Traefik entrypoint" +" level) to allow certain services or route endpoints which do not behave " +"well when compressed (e.g. [issue 3749](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/issues/3749)) to be excluded from " +"compression." +msgstr "" + +#: ../../../CHANGELOG.md:70 +msgid "" +"A long time ago, various services were operating with `gzip`-compression " +"enabled at the nginx level. Since the switch to Traefik (see [Goodbye, " +"`matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md" +"#goodbye-matrix-nginx-proxy-)), all services (with the exception of " +"Matrix APIs for Synapse worker-enabled setups which are powered by " +"`nginx` via `synapse-reverse-proxy-companion`) have been operating " +"without HTTP-compression support." +msgstr "" + +#: ../../../CHANGELOG.md:72 +msgid "" +"HTTP-compression is now done via Traefik's " +"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " +"middleware. We use the default configuration for this middleware, which " +"enables `zstd`, `br` and `gzip` support (in this order). This " +"middleware's configuration can be configured via variables in the Traefik" +" role (see " +"`traefik_config_http_middlewares_compression_middleware_options`)." +msgstr "" + +#: ../../../CHANGELOG.md:74 +msgid "" +"If you're using your own Traefik reverse-proxy server ([Traefik managed " +"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" +"you)) instead of the playbook's integrated Traefik service, you can " +"benefit from the same by:" +msgstr "" + +#: ../../../CHANGELOG.md:76 +msgid "" +"defining a " +"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " +"middleware (via the " +"[file](https://doc.traefik.io/traefik/providers/file/) or " +"[Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" +msgstr "" + +#: ../../../CHANGELOG.md:77 +msgid "" +"setting " +"`matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to" +" `true`" +msgstr "" + +#: ../../../CHANGELOG.md:78 +msgid "" +"specifying the middleware's name in " +"`matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g." +" `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-" +"compression-middleware@file`)" +msgstr "" + +#: ../../../CHANGELOG.md:80 +msgid "Timeout adjustments for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:82 +msgid "" +"The playbook now supports configuring various " +"[transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts)" +" timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the " +"`web`, `web-secure` and `matrix-federation` entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:84 +msgid "" +"If you're using your own Traefik reverse-proxy server ([Traefik managed " +"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" +"you)) instead of the playbook's integrated Traefik service, you may wish " +"to do similar configuration changes to your setup manually." +msgstr "" + +#: ../../../CHANGELOG.md:86 +msgid "" +"The most interesting of these is the `readTimeout` configuration value " +"(the maximum duration for reading the entire request, including the " +"body), which used to default to `60s`. For large and slowly progressing " +"file uploads, `60s` would often not be enough for the transfer to finish " +"and uploads would end up being interrupted. The playbook now raises the " +"`readTimeout` value to 5 minutes (`300s`) to improve this use-case." +msgstr "" + +#: ../../../CHANGELOG.md:88 +msgid "" +"The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` " +"variables (for the `web` entrypoint) cascade to affecting the timeout " +"values for the `web-secure` and `matrix-federation` entrypoints, so you " +"can easily adjust all timeout values using them." +msgstr "" + +#: ../../../CHANGELOG.md:90 +msgid "Example of the default timeout values used by the playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:101 +msgid "" +"Alternatively, you may adjust the timeout values for specific entrypoints" +" (like `web-secure` and `matrix-federation`) using dedicated variables " +"(like " +"`traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout`" +" and " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." +msgstr "" + +#: ../../../CHANGELOG.md:104 +msgid "2024-11-08" +msgstr "" + +#: ../../../CHANGELOG.md:106 +msgid "" +"Support for synapse-admin auto-configuration via /.well-" +"known/matrix/client" +msgstr "" + +#: ../../../CHANGELOG.md:108 +msgid "" +"You can administrate your Synapse-powered homeserver using synapse-admin " +"hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the " +"synapse-admin instance would still auto-configure itself correctly for " +"your server by [reading its `/.well-known/matrix/client` " +"file](https://github.com/etkecc/synapse-admin/pull/126)." +msgstr "" + +#: ../../../CHANGELOG.md:110 +msgid "" +"The playbook now configures the `/.well-known/matrix/client` file for " +"this by default, injecting into it a `cc.etke.synapse-admin` section that" +" contains the full synapse-admin configuration. This is done even if you " +"don't enable the synapse-admin service in your configuration. The reason " +"for always doing it is to allow users to skip the (small) overhead of " +"self-hosting the non-core synapse-admin service, yet still be able to use" +" it from elsewhere when needed." +msgstr "" + +#: ../../../CHANGELOG.md:112 +msgid "" +"If you don't ever plan on using synapse-admin from other servers (besides" +" your own due to [self-hosting synapse-admin](./docs/configuring-" +"playbook-synapse-admin.md)), you **can disable this** `/.well-" +"known/matrix/client` configuration via " +"`matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled:" +" false`" +msgstr "" + +#: ../../../CHANGELOG.md:115 +msgid "2024-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:117 +msgid "(BC Break) Postmoogle's variable names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:119 +msgid "" +"Due to the recategorization of [Postmoogle](./docs/configuring-playbook-" +"bridge-postmoogle.md) from the bot to the bridge, its variables were " +"renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to " +"adjust your `vars.yml` configuration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:121 +msgid "2024-10-19" +msgstr "" + +#: ../../../CHANGELOG.md:123 +msgid "Support for Matrix Authentication Service" +msgstr "" + +#: ../../../CHANGELOG.md:125 +msgid "" +"The playbook now supports installing and configuring [Matrix " +"Authentication Service](./docs/configuring-playbook-matrix-" +"authentication-service.md) (MAS)." +msgstr "" + +#: ../../../CHANGELOG.md:127 +msgid "" +"Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the " +"[Element](https://element.io/) / [Matrix Authentication " +"Service](https://github.com/element-hq/matrix-authentication-service) " +"team for answering our numerous questions about MAS." +msgstr "" + +#: ../../../CHANGELOG.md:129 +msgid "" +"This is an **experimental service** and there are **still certain issues " +"with it** (see [Expectations](./docs/configuring-playbook-matrix-" +"authentication-service.md#expectations)). Matrix server administrators " +"should only consider switching if they identify with one or more [reasons" +" to use Matrix Authentication Service](./docs/configuring-playbook-" +"matrix-authentication-service.md#reasons-to-use-matrix-authentication-" +"service). As MAS adoption improves and more services are adjusted to " +"support it, we expect that using MAS will become the norm." +msgstr "" + +#: ../../../CHANGELOG.md:131 +msgid "" +"Our [Setting up Matrix Authentication Service](./docs/configuring-" +"playbook-matrix-authentication-service.md) documentation page has more " +"details about this new service, what you might expect from the switch and" +" how you can migrate your existing (Synapse) homeserver setup to MAS." +msgstr "" + +#: ../../../CHANGELOG.md:134 +msgid "2024-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:136 +msgid "" +"(BC Break) Postgres & Traefik roles have been relocated and variable " +"names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:138 +msgid "" +"Various roles have been relocated from the " +"[devture](https://github.com/devture) organization to the [mother-of-all-" +"self-hosting](https://github.com/mother-of-all-self-hosting) " +"organization." +msgstr "" + +#: ../../../CHANGELOG.md:140 +msgid "" +"Along with the relocation, the `devture_` prefix was dropped from their " +"variable names, so you need to adjust your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:142 +msgid "You need to do the following replacements:" +msgstr "" + +#: ../../../CHANGELOG.md:144 +msgid "`devture_postgres_` -> `postgres_`" +msgstr "" + +#: ../../../CHANGELOG.md:145 +msgid "`devture_traefik_` -> `traefik_`" +msgstr "" + +#: ../../../CHANGELOG.md:147 +msgid "" +"As always, the playbook would let you know about this and point out any " +"variables you may have missed." +msgstr "" + +#: ../../../CHANGELOG.md:150 +msgid "2024-09-12" +msgstr "" + +#: ../../../CHANGELOG.md:152 +msgid "Support for baibot" +msgstr "" + +#: ../../../CHANGELOG.md:154 +msgid "" +"The playbook now supports installing [baibot](./docs/configuring-" +"playbook-bot-baibot.md) (pronounced bye-bot) - a " +"[Matrix](https://matrix.org/) bot developed by " +"[etke.cc](https://etke.cc/) that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you. 🤖" +msgstr "" + +#: ../../../CHANGELOG.md:156 +msgid "" +"It supports [OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other" +" [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../CHANGELOG.md:158 +msgid "" +"It's designed as a more private and [✨ " +"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" +"file#-features) alternative to the now-unmaintained [matrix-chatgpt-" +"bot](./docs/configuring-playbook-bot-chatgpt.md)." +msgstr "" + +#: ../../../CHANGELOG.md:160 +msgid "" +"To get started, see the [Setting up baibot](./docs/configuring-playbook-" +"bot-baibot.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:162 +msgid "Switching synapse-admin to etke.cc's fork" +msgstr "" + +#: ../../../CHANGELOG.md:164 +msgid "" +"The playbook now installs [etke.cc](https://etke.cc/)'s " +"[fork](https://github.com/etkecc/synapse-admin) of [synapse-" +"admin](https://github.com/Awesome-Technologies/synapse-admin) (originally" +" developed by [Awesome-Technologies](https://github.com/Awesome-" +"Technologies)). This fork is a drop-in replacement for the original " +"software." +msgstr "" + +#: ../../../CHANGELOG.md:166 +msgid "" +"The creation of the fork has been provoked by users frequently " +"encountering issues with the original synapse-admin software, such as " +"unintentionally deleting their one-and-only admin user account (fixed " +"[here](https://github.com/etkecc/synapse-admin/pull/1) and also " +"contributed upstream [here](https://github.com/Awesome-Technologies" +"/synapse-admin/pull/608) - to no avail for now). Since its inception, [a " +"bunch of other quality-of-life improvements](https://github.com/etkecc" +"/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." +msgstr "" + +#: ../../../CHANGELOG.md:168 +msgid "" +"If upstream synapse-admin picks up the pace and improves, the etke.cc " +"fork may disappear and the playbook may switch to the original software " +"again. Until that time comes, we believe that etke.cc's fork is the " +"better software to use right now." +msgstr "" + +#: ../../../CHANGELOG.md:170 +msgid "" +"If you'd like to switch back to the original synapse-admin software, you " +"can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:183 +msgid "2024-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:185 +msgid "New appservice-double-puppet service for better double-puppeting" +msgstr "" + +#: ../../../CHANGELOG.md:187 +msgid "" +"Mautrix bridges are undergoing large changes as announced in the [August " +"2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) " +"blog post." +msgstr "" + +#: ../../../CHANGELOG.md:189 +msgid "" +"The playbook has already upgraded to the rewritten mautrix-slack " +"([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and " +"mautrix-signal " +"([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) " +"bridges." +msgstr "" + +#: ../../../CHANGELOG.md:191 +msgid "" +"The newly rewritten bridges do not support double-puppeting via [Shared " +"Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, " +"which has prompted us to switch to the new & better [appservice " +"method](https://docs.mau.fi/bridges/general/double-puppeting.html" +"#appservice-method-new) for double-puppeting. The playbook automates this" +" double-puppeting setup for you if you enable the new [Appservice Double " +"Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." +msgstr "" + +#: ../../../CHANGELOG.md:193 +msgid "" +"All non-deprecated mautrix bridges in the playbook have been reworked to " +"support double-puppeting via an Appservice. Most bridges still support " +"double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-" +"shared-secret-auth.md), so the playbook supports it too. If only Shared " +"Secret Auth is enabled, double-puppeting will be configured using that " +"method (for the bridges that support it). That said, **Shared Secret Auth" +" double-puppeting is being phased out and we recommend replacing it with " +"the new Appservice method**." +msgstr "" + +#: ../../../CHANGELOG.md:195 +msgid "" +"We recommend **enabling double-puppeting via the new Appservice method** " +"by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:201 +msgid "" +"You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-" +"shared-secret-auth.md) enabled. Non-mautrix bridges and other services " +"(e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) " +"may still require it." +msgstr "" + +#: ../../../CHANGELOG.md:203 +msgid "" +"When both double-puppeting methods are enabled, the playbook will " +"automatically choose the new and better Appservice method for bridges " +"that support it." +msgstr "" + +#: ../../../CHANGELOG.md:206 +msgid "2024-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:208 +msgid "matrix-media-repo now configured for Authenticated Media" +msgstr "" + +#: ../../../CHANGELOG.md:210 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), our matrix-media-repo implementation now " +"automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-" +"repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per " +"[MSC3916](https://github.com/matrix-org/matrix-spec-" +"proposals/pull/3916))." +msgstr "" + +#: ../../../CHANGELOG.md:212 +msgid "" +"If you had never heard of Authenticated Media before, the [Sunsetting " +"unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-" +"unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a" +" good introduction." +msgstr "" + +#: ../../../CHANGELOG.md:214 +msgid "" +"This feature is enabled for matrix-media-repo installations by default " +"and will append an additional (matrix-media-repo-generated signing key) " +"to your homeserver's (Synapse or Dendrite) signing key. See the [Signing " +"keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and " +"[Key backup and revoking](./docs/configuring-playbook-matrix-media-" +"repo.md#key-backup-and-revoking) sections of the matrix-media-repo " +"documentation for more details." +msgstr "" + +#: ../../../CHANGELOG.md:216 +msgid "" +"If you'd like to avoid this new feature, you can disable it by setting " +"`matrix_media_repo_generate_signing_key: false` in your `vars.yml` " +"configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:219 +msgid "2024-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:221 +msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" +msgstr "" + +#: ../../../CHANGELOG.md:223 +msgid "" +"The playbook now installs [matrix-corporal](https://github.com/devture" +"/matrix-corporal) v3.0.0, which brings support for **power-level " +"management** (thanks to [this PR](https://github.com/devture/matrix-" +"corporal/pull/32))." +msgstr "" + +#: ../../../CHANGELOG.md:225 +msgid "" +"This upgrade necessitates configuration policy changes as described in " +"[matrix-corporal's changelog entry](https://github.com/devture/matrix-" +"corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." +msgstr "" + +#: ../../../CHANGELOG.md:227 +msgid "" +"If you'd like to remain on the old (v2) version of matrix-corporal, you " +"can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:233 +msgid "2024-07-25" +msgstr "" + +#: ../../../CHANGELOG.md:235 +msgid "synapse-usage-exporter support" +msgstr "" + +#: ../../../CHANGELOG.md:237 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook can now set up [synapse-usage-" +"exporter](https://github.com/loelkes/synapse-usage-exporter) - a small " +"[Flask](https://flask.palletsprojects.com)-based webservice which can " +"capture usage statistics from Synapse (via HTTP `PUT`) and then make them" +" available for Prometheus to scrape." +msgstr "" + +#: ../../../CHANGELOG.md:239 +msgid "" +"To learn more see our [Enabling synapse-usage-exporter for Synapse usage " +"statistics](docs/configuring-playbook-synapse-usage-exporter.md) " +"documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:242 +msgid "2024-07-06" +msgstr "" + +#: ../../../CHANGELOG.md:244 +msgid "matrix-alertmanager-receiver support" +msgstr "" + +#: ../../../CHANGELOG.md:246 +msgid "" +"For those wishing to more easily integrate " +"[Prometheus](https://prometheus.io/)' alerting service " +"([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/))" +" with Matrix, the playbook can now set up [matrix-alertmanager-" +"receiver](https://github.com/metio/matrix-alertmanager-receiver)." +msgstr "" + +#: ../../../CHANGELOG.md:248 +msgid "" +"See [Setting up Prometheus Alertmanager integration via matrix-" +"alertmanager-receiver](./docs/configuring-playbook-alertmanager-" +"receiver.md) for more details." +msgstr "" + +#: ../../../CHANGELOG.md:250 +msgid "Traefik v3 and HTTP/3 are here now" +msgstr "" + +#: ../../../CHANGELOG.md:252 +msgid "" +"**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to " +"the playbook. Mostly everything else worked out of the box. Most people " +"will not have to do any tweaks to their configuration. In addition, " +"[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-" +"enabled for the `web-secure` (port 443) and `matrix-federation` (port " +"`8448`) entrypoints. If you have a firewall in front of your server and " +"you wish to benefit from `HTTP3`, you will need to open the `443` and " +"`8448` UDP ports in it." +msgstr "" + +#: ../../../CHANGELOG.md:254 +msgid "Traefik v3" +msgstr "" + +#: ../../../CHANGELOG.md:256 +msgid "" +"The reverse-proxy that the playbook uses by default (Traefik) has " +"recently been upgraded to v3 (see [this blog " +"post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn " +"about its new features). Version 3 includes some small breaking " +"configuration changes requiring a " +"[migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:258 +msgid "" +"We have **updated the playbook to Traefik v3** (make sure to run `just " +"roles` / `make roles` to get it)." +msgstr "" + +#: ../../../CHANGELOG.md:260 +msgid "" +"There were **only minor playbook changes required** to adapt to Traefik " +"v3, and only to the Ansible role for [matrix-media-repo](./docs" +"/configuring-playbook-matrix-media-repo.md) where we changed a few " +"[`PathPrefix` instances to " +"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" +"pathprefix-and-pathregexp), because these instances were using a regular " +"expression instead of a fixed path. For fixed-path values, `PathPrefix` " +"is still the preferred matcher function to use." +msgstr "" + +#: ../../../CHANGELOG.md:262 +msgid "**Most people using the playbook should not have to do any changes**." +msgstr "" + +#: ../../../CHANGELOG.md:264 +msgid "" +"If you're using the playbook's Traefik instance to reverse-proxy to some " +"other services of your own (not managed by the playbook), you may wish to" +" review their Traefik labels and make sure they're in line with the " +"[Traefik v2 to v3 migration " +"guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:266 +msgid "" +"If you've tweaked any of this playbook's `_path_prefix` variables and " +"made them use a regular expression, you will now need to make additional " +"adjustments. The playbook makes extensive use of `PathPrefix()` matchers " +"in Traefik rules and `PathPrefix` does not support regular expressions " +"anymore. To work around it, you may now need to override a whole " +"`_traefik_rule` variable and switch it from [`PathPrefix` to " +"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" +"pathprefix-and-pathregexp)." +msgstr "" + +#: ../../../CHANGELOG.md:268 +msgid "" +"If you're not using [matrix-media-repo](./docs/configuring-playbook-" +"matrix-media-repo.md) (the only role we had to tweak to adapt it to " +"Traefik v3), you **may potentially downgrade to Traefik v2** (if " +"necessary) by adding `traefik_verison: v2.11.4` to your configuration. " +"People using `matrix-media-repo` cannot downgrade this way, because " +"`matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing " +"matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that" +" Traefik v2 does not understand." +msgstr "" + +#: ../../../CHANGELOG.md:270 +msgid "HTTP/3 is enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:272 +msgid "" +"In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is " +"no longer considered experimental now. Due to this, **the playbook auto-" +"enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` " +"(port `8448`) entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:274 +msgid "" +"HTTP3 uses the UDP protocol and **the playbook (together with Docker) " +"will make sure that the appropriate ports** (`443` over UDP & `8448` over" +" UDP) **are exposed and whitelisted in your server's firewall**. However," +" **if you have another firewall in front of your server** (as is the case" +" for many cloud providers), **you will need to manually open these UDP " +"ports**." +msgstr "" + +#: ../../../CHANGELOG.md:276 +msgid "" +"If you do not open the UDP ports correctly or there is some other issue, " +"clients (browsers, mostly) will fall-back to " +"[HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even " +"[HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." +msgstr "" + +#: ../../../CHANGELOG.md:278 +msgid "" +"Still, if HTTP/3 cannot function correctly in your setup, it's best to " +"disable advertising support for it (and misleading clients into trying to" +" use HTTP/3)." +msgstr "" + +#: ../../../CHANGELOG.md:280 +msgid "To **disable HTTP/3**, you can use the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:294 +msgid "" +"If you are using [your own webserver](./docs/configuring-playbook-own-" +"webserver.md) (in front of Traefik), port binding on UDP port `8448` by " +"default due to HTTP/3 is either unnecessary or [may get in the " +"way](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3402). If it does, you can disable it:" +msgstr "" + +#: ../../../CHANGELOG.md:307 +msgid "2024-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:309 +msgid "synapse-admin is now restricted to your homeserver's URL by default" +msgstr "" + +#: ../../../CHANGELOG.md:311 +msgid "" +"A new feature introduced in synapse-admin [v0.10.0](https://github.com" +"/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and " +"supported by the playbook since a a few months ago) provides the ability " +"to [restrict its usage to a specific homeserver](https://github.com" +"/Awesome-Technologies/synapse-" +"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" +"#restricting-available-homeserver) (or multiple homeservers)." +msgstr "" + +#: ../../../CHANGELOG.md:313 +msgid "" +"The playbook has just started making use of this feature. **From now on, " +"your synapse-admin instance will be restricted to the homeserver you're " +"managing via the playbook**. When configured like this, the *Homeserver " +"URL* field in synapse-admin's web UI changes from a text field to a " +"dropdown having a single value (the URL of your homeserver). This makes " +"usage simpler for most people, as they won't need to manually enter a " +"*Homeserver URL* anymore." +msgstr "" + +#: ../../../CHANGELOG.md:315 +msgid "" +"If you'd like **to go back to the old unrestricted behavior**, use the " +"following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:323 +msgid "2024-06-25" +msgstr "" + +#: ../../../CHANGELOG.md:325 +msgid "The URL-prefix for Hookshot generic webhooks has changed" +msgstr "" + +#: ../../../CHANGELOG.md:327 +msgid "" +"Until now, generic Hookshot webhook URLs looked like this: " +"`https://matrix.example.com/hookshot/webhooks/:hookId`." +msgstr "" + +#: ../../../CHANGELOG.md:329 +msgid "" +"The `/hookshot/webhooks` common prefix gets stripped by Traefik " +"automatically, so Hookshot only sees the part that comes after " +"(`/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:331 +msgid "" +"[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1681), Hookshot started to prefer to handle webhooks at a " +"`/webhook/:hookId` path (instead of directly at `/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:333 +msgid "" +"To avoid future problems, we've " +"[reconfigured](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot " +"configuration to use webhook URLs that include `/webhook` in the URL " +"suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of " +"`/hookshot/webhooks/:hookId`). This means that when we strip the common " +"prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to " +"Hookshot, just like recommended." +msgstr "" + +#: ../../../CHANGELOG.md:335 +msgid "" +"When generating new webhooks, you should start seeing the new URLs being " +"used." +msgstr "" + +#: ../../../CHANGELOG.md:337 +msgid "" +"**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new " +"URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your" +" webhooks will not break just yet." +msgstr "" + +#: ../../../CHANGELOG.md:339 +msgid "" +"However, **we recommend that you update all your old webhook URLs** " +"(configured in other systems) to include the new `/webhook` path " +"component, so that future Hookshot changes (whenever they come) will not " +"break your webhooks. You don't need to do anything on the Hookshot side -" +" you merely need to reconfigure the remote systems that use your webhook " +"URLs." +msgstr "" + +#: ../../../CHANGELOG.md:342 +msgid "2024-06-22" +msgstr "" + +#: ../../../CHANGELOG.md:344 +msgid "The maubot user is now managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:346 +msgid "" +"To make things easier and to be consistent with other roles, the " +"[maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by" +" default) is [now](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3376) automatically created be the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:348 +msgid "" +"If you have an existing maubot installation, you will need to specify " +"`matrix_bot_maubot_initial_password` in your `vars.yml` file to make the " +"playbook not complain about it being undefined. Since the bot is already " +"registered in your installation, there's nothing for the playbook to do " +"anyway. In case you don't remember the password you've registered your " +"maubot user account with, you can specify any value for this variable." +msgstr "" + +#: ../../../CHANGELOG.md:350 +msgid "" +"If you've registered another username for the bot (other than the " +"recommended default of `bot.maubot`), consider adjusting the " +"`matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: " +"my.maubot.username`)." +msgstr "" + +#: ../../../CHANGELOG.md:353 +msgid "2024-06-03" +msgstr "" + +#: ../../../CHANGELOG.md:355 +msgid "WeChat bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:357 +msgid "" +"Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s " +"[efforts](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3241), the playbook now supports bridging to " +"[WeChat](https://www.wechat.com/) via the [matrix-" +"wechat](https://github.com/duo/matrix-wechat) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:359 +msgid "" +"See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-" +"wechat.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:362 +msgid "2024-03-26" +msgstr "" + +#: ../../../CHANGELOG.md:364 +msgid "" +"(Backward Compatibility Break) The playbook now defaults to KeyDB, " +"instead of Redis" +msgstr "" + +#: ../../../CHANGELOG.md:366 +msgid "" +"**TLDR**: if the playbook used installed Redis as a dependency for you " +"before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a " +"drop-in alternative) due to [Redis having changed its " +"license](https://redis.com/blog/redis-adopts-dual-source-available-" +"licensing/)." +msgstr "" + +#: ../../../CHANGELOG.md:368 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook now uses " +"[KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), " +"instead of [Redis](https://redis.io/)." +msgstr "" + +#: ../../../CHANGELOG.md:370 +msgid "" +"The playbook used to install Redis (and now installs KeyDB in its place) " +"if services have a need for it ([enabling worker support for " +"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" +"workers), [enabling Hookshot encryption](docs/configuring-playbook-" +"bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly " +"enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." +msgstr "" + +#: ../../../CHANGELOG.md:372 +msgid "" +"This change is provoked by the fact that [Redis is now \"source " +"available\"](https://redis.com/blog/redis-adopts-dual-source-available-" +"licensing/). According to the Limitations of [the new " +"license](https://redis.com/legal/rsalv2-agreement/) (as best as we " +"understand them, given that we're not lawyers), using Redis in the " +"playbook (even in a commercial FOSS service like " +"[etke.cc](https://etke.cc/)) does not violate the new Redis license. That" +" said, we'd rather neither risk it, nor endorse shady licenses and " +"products that pretend to be free-software. Another high-quality " +"alternative to Redis seems to be " +"[Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly " +"license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-" +"file#readme) is no better than Redis's." +msgstr "" + +#: ../../../CHANGELOG.md:374 +msgid "" +"Next time your run the playbook (via the `setup-all` tag), **Redis will " +"be automatically uninstalled and replaced with KeyDB**. Some Synapse " +"downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:376 +msgid "" +"Users on `arm32` should be aware that there's **neither a prebuilt " +"`arm32` container image for KeyDB**, nor the KeyDB role supports self-" +"building yet. Users on this architecture likely don't run Synapse with " +"workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis" +" is necessary in an `arm32` deployment, disabling KeyDB and making the " +"playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:387 +msgid "2024-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:389 +msgid "Initial work on IPv6 support" +msgstr "" + +#: ../../../CHANGELOG.md:391 +msgid "" +"Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can " +"now enable IPv6 for container networks for various components (roles) via" +" [the `devture_systemd_docker_base_ipv6_enabled` " +"variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." +msgstr "" + +#: ../../../CHANGELOG.md:393 +msgid "It should be noted that:" +msgstr "" + +#: ../../../CHANGELOG.md:395 +msgid "" +"Matrix roles (`roles/custom/matrix-*`) respect this variable, but " +"external roles (those defined in `requirements.yml` and installed via " +"`just roles`) do not respect it yet. Additional work is necessary" +msgstr "" + +#: ../../../CHANGELOG.md:396 +msgid "" +"changing the variable subsequently may not change existing container " +"networks. Refer to [these " +"instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" +msgstr "" + +#: ../../../CHANGELOG.md:397 +msgid "this is all very new and untested" +msgstr "" + +#: ../../../CHANGELOG.md:399 +msgid "Pantalaimon support" +msgstr "" + +#: ../../../CHANGELOG.md:401 +msgid "" +"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " +"playbook can now install the [Pantalaimon](https://github.com/matrix-" +"org/pantalaimon) E2EE aware proxy daemon for you. It's already possible " +"to integrate it with [Draupnir](docs/configuring-playbook-bot-" +"draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs " +"for details." +msgstr "" + +#: ../../../CHANGELOG.md:403 +msgid "" +"See our [Setting up Pantalaimon](docs/configuring-playbook-" +"pantalaimon.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:406 +msgid "2024-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:408 +msgid "Support for Draupnir-for-all" +msgstr "" + +#: ../../../CHANGELOG.md:410 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " +"install [Draupnir for all](./docs/configuring-playbook-appservice-" +"draupnir-for-all.md) (aka multi-instance Draupnir running in appservice " +"mode)." +msgstr "" + +#: ../../../CHANGELOG.md:412 +msgid "" +"This is an alternative to [running Draupnir in bot mode](./docs" +"/configuring-playbook-bot-draupnir.md), which is still supported by the " +"playbook." +msgstr "" + +#: ../../../CHANGELOG.md:414 +msgid "" +"The documentation page for [Draupnir for all](./docs/configuring-" +"playbook-appservice-draupnir-for-all.md) contains more information on how" +" to install it." +msgstr "" + +#: ../../../CHANGELOG.md:417 +msgid "2024-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:419 +msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge" +msgstr "" + +#: ../../../CHANGELOG.md:421 +msgid "" +"The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-" +"facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-" +"mautrix-instagram.md) bridges are being [superseded by a new " +"bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-" +"meta](https://github.com/mautrix/meta) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:423 +msgid "" +"The playbook now supports the new mautrix-meta bridge - a single bridge, " +"which can run in different modes and bridge to Messenger (via " +"[Facebook](https://facebook.com/), Facebook over " +"[Tor](https://www.torproject.org/) or via " +"[Messenger](https://messenger.com/)) and " +"[Instagram](https://instagram.com/). The playbook makes this bridge " +"available via 2 separate Ansible roles, allowing you to easily run 2 " +"instances of mautrix-meta, for bridging to both services at the same " +"time." +msgstr "" + +#: ../../../CHANGELOG.md:425 +msgid "" +"If you're using mautrix-facebook or mautrix-instagram right now, **you " +"can still continue using the old bridges, but may wish to change to the " +"new bridge implementations**. See:" +msgstr "" + +#: ../../../CHANGELOG.md:427 +msgid "" +"[Setting up Instagram bridging via Mautrix Meta](docs/configuring-" +"playbook-bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../CHANGELOG.md:429 +msgid "" +"[Setting up Messenger bridging via Mautrix Meta](docs/configuring-" +"playbook-bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../CHANGELOG.md:431 +msgid "The documentation pages contain more information on how to migrate." +msgstr "" + +#: ../../../CHANGELOG.md:434 +msgid "2024-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:436 +msgid "Much larger Synapse caches and cache auto-tuning enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:438 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses " +"much larger caches and enables Synapse's [cache auto-tuning " +"functionality](https://matrix-" +"org.github.io/synapse/latest/usage/configuration/config_documentation.html" +"#caches-and-associated-values). This work and the default values used by " +"the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s " +"[Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." +msgstr "" + +#: ../../../CHANGELOG.md:440 +msgid "" +"The playbook has always used a very conservative cache factor " +"(`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK " +"for small and underactive deployments, but is not ideal for larger " +"servers. Paradoxically, a small global cache factor value [does not " +"necessarily decrease RAM usage as a whole](https://github.com/matrix-" +"org/synapse/issues/3939)." +msgstr "" + +#: ../../../CHANGELOG.md:442 +msgid "" +"The playbook now uses **a 20x larger cache factor** (currently `10`), " +"adjusts a few other cache-related variables, and **enables cache auto-" +"tuning** via the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:444 +msgid "" +"`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to " +"1/8 of total RAM with a cap of 2GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:445 +msgid "" +"`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to" +" 1/16 of total RAM with a cap of 1GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:446 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../CHANGELOG.md:448 +msgid "" +"These values should be good defaults for most servers, but may change " +"over time as we experiment further." +msgstr "" + +#: ../../../CHANGELOG.md:450 +msgid "" +"Refer to our new [Tuning caches and cache autotuning](docs/maintenance-" +"synapse.md#tuning-caches-and-cache-autotuning) documentation section for " +"more details." +msgstr "" + +#: ../../../CHANGELOG.md:453 +msgid "2024-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:455 +msgid "" +"(Backward-compatibility break) Minor changes necessary for some people " +"serving a static website at the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:457 +msgid "" +"This only affects people who are [Serving a static website at the base " +"domain](./docs/configuring-playbook-base-domain-serving.md#serving-a" +"-static-website-at-the-base-domain), but not managing its `index.html` " +"through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:459 +msgid "" +"That is, for people who have " +"`matrix_static_files_file_index_html_enabled: false` in their `vars.yml` " +"configuration, the playbook has a new default behavior. Since the " +"playbook is not managing the `index.html` file, it will default to a more" +" sensible way of handling the base domain - redirecting " +"`https://example.com/` to `https://matrix.example.com/`, instead of " +"serving a 404 page." +msgstr "" + +#: ../../../CHANGELOG.md:461 +msgid "" +"If you are managing your static website by yourself (by dropping files " +"into `/matrix/static-files/public` somehow), then you probably don't wish" +" for such redirection to happen. You can disable it by adding " +"`matrix_static_files_container_labels_base_domain_root_path_redirection_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:464 +msgid "2024-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:466 +msgid "Support for more efficient (specialized) Synapse workers" +msgstr "" + +#: ../../../CHANGELOG.md:468 +msgid "" +"Thanks to [Charles Wright](https://github.com/cvwright) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook has [received " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3100) for load-balancing the Synapse workload via " +"[specialized workers](./docs/configuring-playbook-synapse.md#specialized-" +"workers) which are supposed to work better than our old [generic " +"workers](./docs/configuring-playbook-synapse.md#generic-workers) " +"implementation." +msgstr "" + +#: ../../../CHANGELOG.md:470 +msgid "" +"For now, playbook defaults remain unchanged and the `one-of-each` " +"[workers preset](./docs/configuring-playbook-synapse.md#worker-presets) " +"continues being the default. However, the default may change in the " +"future. If you'd like to remain on this preset even if/when the defaults " +"change, consider explicitly adding `matrix_synapse_workers_preset: one-" +"of-each` to your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:472 +msgid "" +"Our specialized workers setup is based on recommendations found in [Tom " +"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/index.html). What's special " +"about our new setup is that we try to parse information out of the " +"request (who the user is; which room is being operated on) and try to " +"forward similar requests to the same worker. As an example, this means " +"that once a worker caches some room information, subsequent requests for " +"the same room will be routed to the same worker (which supposedly still " +"has the room's state cached)." +msgstr "" + +#: ../../../CHANGELOG.md:474 +msgid "" +"To get started, refer to our [Specialized workers](./docs/configuring-" +"playbook-synapse.md#specialized-workers) documentation section." +msgstr "" + +#: ../../../CHANGELOG.md:477 +msgid "2024-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:479 +msgid "Switching to Element's AGPLv3-licensed Synapse release" +msgstr "" + +#: ../../../CHANGELOG.md:481 +msgid "" +"A few months ago, the [Element](https://element.io/) company has " +"[announced](https://element.io/blog/element-to-adopt-agplv3/) that their " +"work on the Synapse homeserver would no longer be available under the " +"permissive [Apache-2.0 " +"license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" +msgstr "" + +#: ../../../CHANGELOG.md:483 +msgid "" +"the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software" +" license - the same license that this Ansible playbook has always used" +msgstr "" + +#: ../../../CHANGELOG.md:484 +msgid "" +"a proprietary license, for those wishing for Element to [sell them an " +"exception](https://gnu.org/philosophy/selling-exceptions.html) to the " +"AGPLv3 license" +msgstr "" + +#: ../../../CHANGELOG.md:486 +msgid "" +"You can also learn more in [this post](https://matrix.org/blog/2023/11/06" +"/future-of-synapse-dendrite/) by the Matrix Foundation." +msgstr "" + +#: ../../../CHANGELOG.md:488 +msgid "" +"The change has [already happened](https://element.io/blog/synapse-now-" +"lives-at-github-com-element-hq-synapse/) and the first Synapse release " +"under the new license is here: [v1.99.0](https://github.com/element-" +"hq/synapse/releases/tag/v1.99.0)." +msgstr "" + +#: ../../../CHANGELOG.md:490 +msgid "" +"There is no up-to-date alternative Synapse fork right now and this free-" +"software (AGPLv3-licensed) playbook is definitely not against free-" +"software licenses, so we are now switching to the Element-maintained " +"Synapse release." +msgstr "" + +#: ../../../CHANGELOG.md:492 +msgid "**What does this mean to you?**" +msgstr "" + +#: ../../../CHANGELOG.md:494 +msgid "" +"For most home users, it doesn't mean anything. Your installation will " +"continue working as it should and you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:496 +msgid "" +"For people building commercial products on top of Synapse, they may have " +"to either buy a license exception from Element (from what we hear, the " +"fee depends on the number of monthly-active users on your instance) or " +"they may need to release all related code as free-software (which is what" +" we've been doing at [etke.cc](https://etke.cc/) " +"([here](https://gitlab.com/etke.cc)) all along)." +msgstr "" + +#: ../../../CHANGELOG.md:498 +msgid "" +"We're no lawyers and this changelog entry does not aim to give you the " +"best legal advice, so please research on your own!" +msgstr "" + +#: ../../../CHANGELOG.md:500 +msgid "" +"If you'd like to continue using the old Apache-2.0-licensed Synapse (for " +"a while longer anyway), the playbook makes it possible by intruducing a " +"new Ansible variable. You can do it like this:" +msgstr "" + +#: ../../../CHANGELOG.md:512 +msgid "Notes:" +msgstr "" + +#: ../../../CHANGELOG.md:514 +msgid "" +"if you had already upgraded Synapse to `v1.99.0` by running this " +"playbook, you will still be able to downgrade to `v1.98.0`, because both " +"releases use the same database schema version (`SCHEMA_COMPAT_VERSION = " +"83` - see [here for v1.98.0](https://github.com/element-" +"hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and" +" [here for v1.99.0](https://github.com/element-" +"hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). " +"More details on Synapse's database schema are available [here](https" +"://element-" +"hq.github.io/synapse/develop/development/database_schema.html). It " +"appears that there are no new database migrations introduced in " +"`v1.99.0`, so going back to the older release is possible. This is not " +"guaranteed to hold true for future Synapse releases, so if you're seeing " +"this early-enough, consider pinning the version and organization before " +"re-running the playbook and getting upgraded to the latest version" +msgstr "" + +#: ../../../CHANGELOG.md:516 +msgid "" +"running an outdated homeserver exposes you to security issues and " +"incompatibilities. Only consider doing this as a short-term solution." +msgstr "" + +#: ../../../CHANGELOG.md:518 +msgid "2024-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:520 +msgid "`Draupnir` has been relicensed to AFL-3.0" +msgstr "" + +#: ../../../CHANGELOG.md:522 +msgid "" +"As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) " +"Draupnir changed its licence to AFL-3.0 from the CSL licence. This change" +" affects playbook users who could not run Draupnir under the old license " +"restrictions. The new license is considerably less restrictive and is OSI" +" approved. Draupnir version v1.86.0 and later are covered by this license" +" change." +msgstr "" + +#: ../../../CHANGELOG.md:524 +msgid "2024-01-15" +msgstr "" + +#: ../../../CHANGELOG.md:526 +msgid "Goodbye, `matrix-nginx-proxy` 🪦" +msgstr "" + +#: ../../../CHANGELOG.md:528 +msgid "" +"**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component " +"are now gone. This brought about many other internal changes (and " +"security improvements), so setups may need minor adjustments or suffer " +"some (temporary) breakage. People who have been on the Traefik-native " +"setup may upgrade without much issues. Those running their own Traefik " +"instance may need minor changes. People who have been postponing the " +"migration away from `matrix-nginx-proxy` (for more than a year already!) " +"will now finally need to do something about it." +msgstr "" + +#: ../../../CHANGELOG.md:530 +msgid "Backstory on `matrix-nginx-proxy`" +msgstr "" + +#: ../../../CHANGELOG.md:532 +msgid "" +"We gather here today to celebrate the loss of a once-beloved component in" +" our stack - `matrix-nginx-proxy`. It's been our " +"[nginx](https://nginx.org/)-based reverse-proxy of choice since the " +"[first commit](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7" +" years ago." +msgstr "" + +#: ../../../CHANGELOG.md:534 +msgid "" +"For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy " +"in our setup (doing SSL termination, etc.). After [transitioning to " +"Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-" +"nginx-proxy` took a step back. Nevertheless, since it was so ingrained " +"into the playbook, it still remained in use - even if only internally. " +"Despite our warnings of its imminent death, many of you have indubitably " +"continued to use it instead of Traefik. Its suffering continued for too " +"long, because it served many different purposes and massive effort was " +"required to transition them to others." +msgstr "" + +#: ../../../CHANGELOG.md:536 +msgid "To us, `matrix-nginx-proxy` was:" +msgstr "" + +#: ../../../CHANGELOG.md:538 +msgid "an [nginx](https://nginx.org/)-based reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:539 +msgid "" +"an Ansible role organizing the work of " +"[certbot](https://certbot.eff.org/) - retrieving free [Let's " +"Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-" +"proxy` and for the [Coturn TURN server](./docs/configuring-playbook-" +"turn.md)" +msgstr "" + +#: ../../../CHANGELOG.md:540 +msgid "" +"a central component for reverse-proxying to the [long list of " +"services](./docs/configuring-playbook.md) supported by the playbook. As " +"such, it became a dependency that all these services had to inject " +"themselves into during runtime" +msgstr "" + +#: ../../../CHANGELOG.md:541 +msgid "" +"an intermediary through which addons (bridges, bots) communicated with " +"the homeserver. Going through an intermediary (instead of directly " +"talking to the homeserver) is useful when certain components (like " +"[matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or " +"[matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are " +"enabled, because it lets these services \"steal routes\" from the " +"homeserver" +msgstr "" + +#: ../../../CHANGELOG.md:542 +msgid "" +"a webserver for serving the `/.well-known/matrix` static files (generated" +" by the `matrix-base` role until now)" +msgstr "" + +#: ../../../CHANGELOG.md:543 +msgid "" +"a webserver [serving your base domain](./docs/configuring-playbook-base-" +"domain-serving.md) (and also generating the `index.html` page for it)" +msgstr "" + +#: ../../../CHANGELOG.md:544 +msgid "" +"a central component providing global [HTTP Basic " +"Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) " +"password-protection for all `/metrics` endpoints when metrics were " +"exposed publicly for consumption from a remote Prometheus server" +msgstr "" + +#: ../../../CHANGELOG.md:546 +msgid "" +"Talk about a jack of all trades! The [UNIX " +"philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker " +"container philosophy) of \"do one thing and do it well\" had been " +"severely violated for too long." +msgstr "" + +#: ../../../CHANGELOG.md:548 +msgid "" +"On a related note, we also had a large chain of reverse-proxies in the " +"mix. In the worst case, it was something like this: (Traefik -> `matrix-" +"nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-" +"reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." +msgstr "" + +#: ../../../CHANGELOG.md:550 +msgid "" +"Due to complexity and the playbook's flexibility (trying to accommodate a" +" mix of tens of components), many layers of indirection were necessary. " +"We do like reverse-proxies, but.. not quite enough to enjoy going through" +" a chain of ~4 of them before reaching the target service." +msgstr "" + +#: ../../../CHANGELOG.md:552 +msgid "" +"After **a ton of work** in the last weeks (200+ commits, which changed " +"467 files - 8684 insertions and 8913 deletions), **we're finally saying " +"goodbye** to `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:554 +msgid "Going Traefik-native and cutting out all middlemen" +msgstr "" + +#: ../../../CHANGELOG.md:556 +msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." +msgstr "" + +#: ../../../CHANGELOG.md:558 +msgid "" +"In most cases, there's only Traefik and all services being registered " +"directly with it. When [Synapse workers](./docs/configuring-playbook-" +"synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-" +"reverse-proxy-companion` remains as an extra reverse-proxy that requests " +"go through (for load-balancing to the correct Synapse worker), but in all" +" other cases services are exposed directly." +msgstr "" + +#: ../../../CHANGELOG.md:560 +msgid "" +"This reduces \"network\" hops (improving performance) and also decreases " +"the number of components (containers). Each Ansible role in our setup is " +"now independent and doesn't need to interact with other roles during " +"runtime." +msgstr "" + +#: ../../../CHANGELOG.md:562 +msgid "Traefik now has an extra job" +msgstr "" + +#: ../../../CHANGELOG.md:564 +msgid "" +"Previously, **Traefik had a single purpose** - being the main reverse-" +"proxy. It was either front-most (terminating SSL, etc.) or you were " +"[fronting Traefik with your own other reverse-proxy](./docs/configuring-" +"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" +"webserver-with-another-reverse-proxy). In any case - it had this central " +"(yet decentralized) job." +msgstr "" + +#: ../../../CHANGELOG.md:566 +msgid "" +"Now, **Traefik has one more role** - it serves as an intermediary which " +"allows addon services (bridges, bots, etc.) to communicate with the " +"homeserver. As mentioned above, such an intermediary service is not " +"strictly necessary in all kinds of setups, but more complex setups " +"(including [matrix-media-repo](./docs/configuring-playbook-matrix-media-" +"repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-" +"corporal.md)) benefit from it." +msgstr "" + +#: ../../../CHANGELOG.md:568 +msgid "" +"To perform this new role, Traefik now has a new internal " +"[entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called " +"`matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, " +"Synapse and even `matrix-synapse-reverse-proxy-companion`) and " +"homeserver-related core services ([matrix-media-repo](./docs/configuring-" +"playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-" +"playbook-matrix-corporal.md) and potentially others) register their " +"routes (using [container labels](https://docs.docker.com/config/labels-" +"custom-metadata/)) not only on the public entrypoints (`web-secure`, " +"`matrix-federation`), but also on this new internal entrypoint." +msgstr "" + +#: ../../../CHANGELOG.md:570 +msgid "" +"Doing so, services can contact Traefik on this entrypoint's dedicated " +"port (the URL defaults to `http://matrix-traefik:8008`) and reach the " +"homeserver Client-Server API as they expect. Internally, Traefik takes " +"care of the routing to the correct service." +msgstr "" + +#: ../../../CHANGELOG.md:572 +msgid "" +"We've also considered keeping it simple and having services talk to the " +"homeserver over the public internet (e.g. `https://matrix.example.com`) " +"thus reusing all existing Traefik routing labels. In this scenario, " +"performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to" +" TLS and networking overhead. The need for fast internal communication " +"(via the new internal non-TLS-enabled Traefik entrypoint) is definitely " +"there. In our benchmarks, Traefik even proved more efficient than nginx " +"at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out " +"of ~1400 rps when talking to the Synapse homeserver directly)." +msgstr "" + +#: ../../../CHANGELOG.md:574 +msgid "Traefik serving this second purpose has a few downsides:" +msgstr "" + +#: ../../../CHANGELOG.md:576 +msgid "" +"Traefik becomes a runtime dependency for all homeserver-dependant " +"container services" +msgstr "" + +#: ../../../CHANGELOG.md:577 +msgid "" +"all homeserver-dependant services now need to be connected to the " +"`traefik` container network, even if they don't need public internet " +"exposure" +msgstr "" + +#: ../../../CHANGELOG.md:579 +msgid "" +"Despite these downsides (which the playbook manages automatically), we " +"believe it's still a good compromise given the amount of complexity it " +"eliminates and the performance benefits it yields. One alternative we've " +"[considered](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary " +"service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both " +"had much higher complexity (one more component in the mix; duplication of" +" effort to produce nginx-compatible route definitions for it) and " +"slightly worse performance (see above)." +msgstr "" + +#: ../../../CHANGELOG.md:581 +msgid "" +"People running the default Traefik setup do not need to do anything to " +"make Traefik take on this extra job. Your Traefik configuration will be " +"updated automatically." +msgstr "" + +#: ../../../CHANGELOG.md:583 +msgid "" +"**People runnning their own Traefik reverse-proxy need to do [minor " +"adjustments](#people-managing-their-own-traefik-instance-need-to-do-" +"minor-changes)**, as described in the section below." +msgstr "" + +#: ../../../CHANGELOG.md:585 +msgid "" +"You may disable Traefik acting as an intermediary by explicitly setting " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled`" +" to `false`. Services would then be configured to talk to the homeserver " +"directly, giving you a slight performance boost and a \"simpler\" Traefik" +" setup. However, such a configuration is less tested and will cause " +"troubles, especially if you enable more services (like `matrix-media-" +"repo`, etc.) in the future. As such, it's not recommended." +msgstr "" + +#: ../../../CHANGELOG.md:587 +msgid "People managing their own Traefik instance need to do minor changes" +msgstr "" + +#: ../../../CHANGELOG.md:589 +msgid "" +"This section is for people [managing their own Traefik instance on the " +"Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-" +"managed-by-you). Those [using Traefik managed by the playbook](./docs" +"/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) " +"don't need to do any changes." +msgstr "" + +#: ../../../CHANGELOG.md:591 +msgid "" +"Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), " +"you need to adapt your configuration to add the additional `matrix-" +"internal-matrix-client-api` entrypoint and potentially configure the " +"`matrix_playbook_reverse_proxy_container_network` variable. See the " +"[Traefik managed by you](./docs/configuring-playbook-own-webserver.md" +"#traefik-managed-by-you) documentation section for more details." +msgstr "" + +#: ../../../CHANGELOG.md:593 +msgid "" +"People fronting Traefik with another reverse proxy need to do minor " +"changes" +msgstr "" + +#: ../../../CHANGELOG.md:595 +msgid "" +"We've already previously mentioned that you need to do some minor " +"[configuration changes related to `traefik_additional_entrypoints_auto" +"`](#backward-compatibility-configuration-changes-required-for-people-" +"fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:597 +msgid "" +"If you don't do these changes (switching from " +"`traefik_additional_entrypoints_auto` to multiple other variables), your " +"Traefik setup will not automatically receive the new `matrix-internal-" +"matrix-client-api` Traefik entrypoint and Traefik would not be able to " +"perform [its new duty of connecting addons with the homeserver](#traefik-" +"now-has-an-extra-job)." +msgstr "" + +#: ../../../CHANGELOG.md:599 +msgid "Supported reverse proxy types are now fewer" +msgstr "" + +#: ../../../CHANGELOG.md:601 +msgid "" +"This section is for people using a more custom reverse-proxy setup - " +"those having `matrix_playbook_reverse_proxy_type` set to a value " +"different than the default (`playbook-managed-traefik`)." +msgstr "" + +#: ../../../CHANGELOG.md:603 +msgid "" +"Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to" +" 7 different values to accommodate various reverse-proxy setups." +msgstr "" + +#: ../../../CHANGELOG.md:605 +msgid "The complexity of this is too high, so we only support 3 values right now:" +msgstr "" + +#: ../../../CHANGELOG.md:607 +msgid "" +"(the default) `playbook-managed-traefik`, when you're [using Traefik " +"managed by the playbook](./docs/configuring-playbook-own-webserver.md" +"#traefik-managed-by-the-playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:608 +msgid "" +"`other-traefik-container`, when you're [managing your own Traefik " +"instance on the Matrix server](./docs/configuring-playbook-own-" +"webserver.md#traefik-managed-by-you)" +msgstr "" + +#: ../../../CHANGELOG.md:609 +msgid "" +"`none`, when you wish for [no reverse-proxy integration to be done at " +"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" +"on-the-matrix-side-at-all)" +msgstr "" + +#: ../../../CHANGELOG.md:611 +msgid "" +"The `none` value is not recommended and may not work adequately, due to " +"lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-" +"extra-job) in our setup." +msgstr "" + +#: ../../../CHANGELOG.md:613 +msgid "" +"**Previous values that are now gone** (and the playbook would report them" +" as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, " +"`other-on-same-host` and `other-on-another-host`." +msgstr "" + +#: ../../../CHANGELOG.md:615 +msgid "" +"If you were using these values as a way to stay away from Traefik, you " +"now have 2 options:" +msgstr "" + +#: ../../../CHANGELOG.md:617 +msgid "" +"(recommended) [Fronting Traefik with another reverse-proxy](./docs" +"/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-" +"proxy-webserver-with-another-reverse-proxy)" +msgstr "" + +#: ../../../CHANGELOG.md:618 +msgid "" +"(not recommended) [Using no reverse-proxy on the Matrix side at " +"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" +"on-the-matrix-side-at-all) and reverse-proxying to each and every service" +" manually" +msgstr "" + +#: ../../../CHANGELOG.md:620 +msgid "Container networking changes" +msgstr "" + +#: ../../../CHANGELOG.md:622 +msgid "" +"Now that `matrix-nginx-proxy` is not in the mix, it became easier to " +"clear out some other long-overdue technical debt." +msgstr "" + +#: ../../../CHANGELOG.md:624 +msgid "" +"Since the very beginning of this playbook, all playbook services were " +"connected to a single (shared) `matrix` container network. Later on, some" +" additional container networks appeared, but most services (database, " +"etc.) still remained in the `matrix` container network. This meant that " +"any random container in this network could try to talk (or attack) the " +"Postgres database operating in the same `matrix` network." +msgstr "" + +#: ../../../CHANGELOG.md:626 +msgid "" +"Moving components (especially the database) into other container networks" +" was difficult - it required changes to many other components to ensure " +"correct connectivity." +msgstr "" + +#: ../../../CHANGELOG.md:628 +msgid "" +"All the hard work has been done now. We've added much more isolation " +"between services by splitting them up into separate networks (`matrix-" +"homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, " +"etc). Components are only joined to the networks they need and should " +"(for the most part) not be able to access unrelated things." +msgstr "" + +#: ../../../CHANGELOG.md:630 +msgid "" +"Carrying out these container networking changes necessitated modifying " +"many components, so **we're hoping not too many bugs were introduced in " +"the process**." +msgstr "" + +#: ../../../CHANGELOG.md:632 +msgid "" +"We've refrained from creating too many container networks (e.g. one for " +"each component), to avoid exhausting Docker's default network pool and " +"contaminating the container networks list too much." +msgstr "" + +#: ../../../CHANGELOG.md:634 +msgid "Metrics exposure changes" +msgstr "" + +#: ../../../CHANGELOG.md:636 +msgid "" +"This section is for people who are exposing monitoring metrics publicly, " +"to be consumed by an external Prometheus server." +msgstr "" + +#: ../../../CHANGELOG.md:638 +msgid "" +"Previously, `matrix-nginx-proxy` was potentially password-protecting all " +"`/metrics/*` endpoints with the same username and password (specified as " +"plain-text in your `vars.yml` configuration file)." +msgstr "" + +#: ../../../CHANGELOG.md:640 +msgid "" +"From now on, there are new variables for doing roughly the same - " +"`matrix_metrics_exposure_enabled`, " +"`matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & " +"Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for" +" details." +msgstr "" + +#: ../../../CHANGELOG.md:642 +msgid "" +"`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now," +" each role provides its own metrics exposure and protection by " +"registering with Traefik. Nevertheless, all roles are wired (via playbook" +" configuration in `group_vars/matrix_servers`) to obey these new " +"`matrix_metrics_exposure_*` variables. We've eliminated the " +"centralization, but have kept the ease of use. Now, you can also do per-" +"service password-protection (with different credentials), should you need" +" to do that for some reason." +msgstr "" + +#: ../../../CHANGELOG.md:644 +msgid "" +"The playbook will tell you about all variables that you need to migrate " +"during runtime, so rest assured - you shouldn't be able to miss anything!" +msgstr "" + +#: ../../../CHANGELOG.md:646 +msgid "Matrix static files" +msgstr "" + +#: ../../../CHANGELOG.md:648 +msgid "" +"As mentioned above, static files like `/.well-known/matrix/*` or your " +"base domain's `index.html` file (when [serving the base domain via the " +"Matrix server](./docs/configuring-playbook-base-domain-serving.md) was " +"enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` " +"roles and put into a `/matrix/static-files` directory on the server. Then" +" `matrix-nginx-proxy` was serving all these static files." +msgstr "" + +#: ../../../CHANGELOG.md:650 +msgid "" +"All of this has been extracted into a new `matrix-static-files` Ansible " +"role that's part of the playbook. The static files generated by this new " +"role still live at roughly the same place (`/matrix/static-files/public` " +"directory, instead of `/matrix/static-files`)." +msgstr "" + +#: ../../../CHANGELOG.md:652 +msgid "" +"The playbook will migrate and update the `/.well-known/matrix/*` files " +"automatically but not your own files in `nginx-proxy/data/matrix-domain/`" +" you will need to back these up yourself otherwise they will be lost. It " +"will also warn you about usage of old variable names, so you can adapt to" +" the new names." +msgstr "" + +#: ../../../CHANGELOG.md:654 +msgid "A note on performance" +msgstr "" + +#: ../../../CHANGELOG.md:656 +msgid "" +"Some of you have been voicing their concerns (for a long time) about " +"Traefik being too slow and nginx being better." +msgstr "" + +#: ../../../CHANGELOG.md:658 +msgid "" +"Some online benchmarks support this by demonstrating slightly higher SSL-" +"termination performance in favor of nginx. The upcoming Traefik v3 " +"release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-" +"traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL " +"performance by some 20%, but that still ends up being somewhat slower " +"than nginx." +msgstr "" + +#: ../../../CHANGELOG.md:660 +msgid "" +"We believe that using Traefik provides way too many benefits to worry " +"about this minor performance impairment." +msgstr "" + +#: ../../../CHANGELOG.md:662 +msgid "" +"The heaviest part of running a Matrix homeserver is all the slow and " +"potentially inefficient things the homeserver (e.g. Synapse) is doing. " +"These things affect performance much more than whatever reverse-proxy is " +"in front. Your server will die the same way by joining the famously large" +" **Matrix HQ** room, no matter which reverse-proxy you put in front." +msgstr "" + +#: ../../../CHANGELOG.md:664 +msgid "" +"Even our previously mentioned benchmarks (yielding ~1300 rps) are " +"synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-" +"use does much more than this." +msgstr "" + +#: ../../../CHANGELOG.md:666 +msgid "" +"If this is still not convincing enough for you and you want the best " +"possible performance, consider [Fronting Traefik with another reverse-" +"proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-" +"integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus " +"having the slowest part - SSL termination - happen elsewhere) or [Using " +"no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-" +"own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The " +"playbook will not get in your way of doing that, but these options may " +"make your life much harder. Performance comes at a cost, after all." +msgstr "" + +#: ../../../CHANGELOG.md:668 +msgid "Migration procedure" +msgstr "" + +#: ../../../CHANGELOG.md:670 +msgid "" +"The updated playbook will automatically perform some migration tasks for " +"you:" +msgstr "" + +#: ../../../CHANGELOG.md:672 +msgid "" +"It will stop and remove the `matrix-nginx-proxy` systemd service and " +"container for you. This behavior cannot be disabled. It's essential that " +"this service gets stopped, because it remaining running (and having " +"container labels) may confuse Traefik as to where to route HTTP requests." +msgstr "" + +#: ../../../CHANGELOG.md:674 +msgid "" +"It will delete the `/matrix/nginx-proxy` directory and all files within " +"it. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: " +"false` to your `vars.yml` configuration file. Doing so will leave its " +"data around." +msgstr "" + +#: ../../../CHANGELOG.md:676 +msgid "" +"It will delete the `/matrix/ssl` directory and all files within it. You " +"can disable this behavior by adding " +"`matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to " +"your `vars.yml` configuration file. If you have some important " +"certificates there for some reason, take them out or temporarily disable " +"removal of these files until you do." +msgstr "" + +#: ../../../CHANGELOG.md:678 +msgid "" +"It will tell you about all variables (`matrix_nginx_proxy_*` and many " +"others - even from other roles) that have changed during this large " +"nginx-elimination upgrade. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:680 +msgid "" +"It will tell you about any leftover `matrix_nginx_proxy_*` variables in " +"your `vars.yml` file. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:682 +msgid "" +"It will tell you about any leftover `matrix_ssl_*` variables in your " +"`vars.yml` file. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: " +"false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:684 +msgid "" +"We don't recommend changing these variables and suppressing warnings, " +"unless you know what you're doing." +msgstr "" + +#: ../../../CHANGELOG.md:686 +msgid "" +"**Most people should just upgrade as per-normal**, bearing in mind that a" +" lot has changed and some issues may arise. The playbook would guide you " +"through renamed variables automatically." +msgstr "" + +#: ../../../CHANGELOG.md:688 +msgid "Conclusion" +msgstr "" + +#: ../../../CHANGELOG.md:690 +msgid "" +"Thousands of lines of code were changed across hundreds of files. All " +"addons (bridges, bots) were rewired in terms of container networking and " +"in terms of how they reach the homeserver." +msgstr "" + +#: ../../../CHANGELOG.md:692 +msgid "" +"I don't actively use all the ~100 components offered by the playbook (no " +"one does), nor do I operate servers exercising all edge-cases. As such, " +"issues may arise. Please have patience and report (or try to fix) these " +"issues!" +msgstr "" + +#: ../../../CHANGELOG.md:695 +msgid "2024-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:697 +msgid "" +"(Backward Compatibility) Configuration changes required for people " +"fronting the integrated reverse-proxy webserver with another reverse-" +"proxy" +msgstr "" + +#: ../../../CHANGELOG.md:699 +msgid "" +"If you're on the default setup (using the Traefik reverse-proxy as " +"installed by the playbook), you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:701 +msgid "" +"People who are [Fronting the integrated Traefik reverse-proxy webserver " +"with another reverse-proxy](./docs/configuring-playbook-own-webserver.md" +"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy), as per our previous instructions are redefining " +"`traefik_additional_entrypoints_auto` in their `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:703 +msgid "" +"Such a full variable redefinion is intrustive, because it prevents the " +"playbook from injecting additional entrypoints into the Traefik " +"webserver. In the future, the playbook may have a need to do so." +msgstr "" + +#: ../../../CHANGELOG.md:705 +msgid "" +"For this reason, we no longer recommend completely redefining " +"`traefik_additional_entrypoints_auto`. The playbook now defines [various " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` " +"variables in the `defaults/main.yml` file](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-" +"base/defaults/main.yml) of the `matrix-base` role which can be used as a " +"safer alternative to `traefik_additional_entrypoints_auto`." +msgstr "" + +#: ../../../CHANGELOG.md:707 +msgid "Adapt your configuration as seen below:" +msgstr "" + +#: ../../../CHANGELOG.md:740 +msgid "" +"Also, feel free to read the [Fronting the integrated Traefik reverse-" +"proxy webserver with another reverse-proxy](./docs/configuring-playbook-" +"own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-" +"another-reverse-proxy) documentation section again for additional " +"details." +msgstr "" + +#: ../../../CHANGELOG.md:743 +msgid "2024-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:745 +msgid "" +"matrix-reminder-bot update with more secure (backward-incompatible) " +"default settings" +msgstr "" + +#: ../../../CHANGELOG.md:747 +msgid "" +"**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453" +"/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs" +"/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By " +"default, like other bridges/bots managed by the playbook, it will only " +"provide its services to users of your own server (not to anyone, even " +"across the Matrix Federation). If that's fine, there's nothing you need " +"to do." +msgstr "" + +#: ../../../CHANGELOG.md:749 +msgid "" +"Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-" +"matrix-reminder-bot.md) has been picked up by [Kim " +"Brose](https://github.com/HarHarLinks) and " +"[@svierne](https://github.com/svierne)." +msgstr "" + +#: ../../../CHANGELOG.md:751 +msgid "" +"Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-" +"reminder-bot/releases/tag/v0.3.0) release is out. The new version is now " +"available for the ARM64 architecture, so playbook users on this " +"architecture will no longer need to wait for [self-building](./docs/self-" +"building.md) to happen." +msgstr "" + +#: ../../../CHANGELOG.md:753 +msgid "" +"The new version also comes with new `allowlist` and `blocklist` settings," +" which make it possible to restrict who can use the bot. Previously " +"anyone, even across the Matrix Federation could talk to it and schedule " +"reminders." +msgstr "" + +#: ../../../CHANGELOG.md:755 +msgid "" +"The playbook defaults all bridges and bots (where possible) to only be " +"exposed to users of the current homeserver, not users across federation. " +"Thanks to the new version of this bot making such a restriction possible," +" we're now making use of it. The playbook (via its " +"`group_vars/matrix_servers` file) automatically enables the `allowlist` " +"(`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures" +" it in such a way " +"(`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to " +"restrict the bot to your homeserver's users." +msgstr "" + +#: ../../../CHANGELOG.md:757 +msgid "" +"If you need **to undo or tweak these security improvements**, you can " +"change your `vars.yml` file to:" +msgstr "" + +#: ../../../CHANGELOG.md:759 +msgid "" +"disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled:" +" false`), making the bot allow usage by anyone, anywhere" +msgstr "" + +#: ../../../CHANGELOG.md:761 +msgid "" +"inject additional allowed servers or users by adding **additional** (on " +"top of the default allowlist in " +"`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes " +"in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list " +"variable (see the [syntax reference](https://github.com/anoadragon453" +"/matrix-reminder-" +"bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" +msgstr "" + +#: ../../../CHANGELOG.md:763 +msgid "" +"override the default allowlist (in the `group_vars/matrix_servers` file) " +"by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" +msgstr "" + +#: ../../../CHANGELOG.md:766 +msgid "2024-01-05" +msgstr "" + +#: ../../../CHANGELOG.md:768 +msgid "matrix-mailer has been replaced by the exim-relay external role" +msgstr "" + +#: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410 +msgid "" +"We're continuing our effort to make [the playbook use external roles for " +"some things](#the-playbook-now-uses-external-roles-for-some-things), so " +"as to avoid doing everything ourselves and to facilitate code re-use." +msgstr "" + +#: ../../../CHANGELOG.md:772 +msgid "" +"The `matrix-mailer` role has been moved to its own repository ([ansible-" +"role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-" +"role-exim-relay)) that this playbook now includes." +msgstr "" + +#: ../../../CHANGELOG.md:774 +msgid "To migrate:" +msgstr "" + +#: ../../../CHANGELOG.md:776 +msgid "pull the playbook changes, as usual" +msgstr "" + +#: ../../../CHANGELOG.md:777 +msgid "update your roles (run `just roles` or `make roles`)" +msgstr "" + +#: ../../../CHANGELOG.md:778 +msgid "" +"update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to " +"`exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> " +"`exim_relay_sender_address`). If you find none, it means you're using the" +" default configuration and your migraiton job is even simpler." +msgstr "" + +#: ../../../CHANGELOG.md:779 +msgid "re-run the playbook (`install-all` or `setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:781 +msgid "" +"The playbook will take care of stopping the old `matrix-mailer` systemd " +"service, relocating its directory and restarting it under the new name " +"(`matrix-exim-relay.service`)." +msgstr "" + +#: ../../../CHANGELOG.md:784 +msgid "2024-01-02" +msgstr "" + +#: ../../../CHANGELOG.md:786 +msgid "mautrix-signal now powered by the new Go-based bridge" +msgstr "" + +#: ../../../CHANGELOG.md:788 +msgid "" +"The old Python-based [mautrix-signal](https://github.com/mautrix/signal) " +"bridge is no longer maintained upstream. It's also known to have issues " +"linking new devices." +msgstr "" + +#: ../../../CHANGELOG.md:790 +msgid "" +"It seems like the path forward is to switch to the new mautrix-signal " +"bridge written in Golang, which we did thanks to [PR " +"#3031](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." +msgstr "" + +#: ../../../CHANGELOG.md:792 +msgid "" +"The playbook should **automatically migrate your mautrix-signal " +"installation to the new bridge code**. You will **need to relink all your" +" devices** to continue your bridged conversations." +msgstr "" + +#: ../../../CHANGELOG.md:795 +msgid "2023-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:797 +msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:799 +msgid "" +"**TDLR**: if your Matrix server is federating (which it mostly likely is," +" unless you've [disabled federation](docs/configuring-playbook-" +"federation.md#disabling-federation)), your public rooms will not only be " +"joinable across federation (as they've always been), but from now on will" +" be discoverable (made available as a list across federation). We're " +"changing this by flipping the value for Synapse's " +"`allow_public_rooms_over_federation` setting to `true`, going against the" +" upstream default. Servers that disable federation are not affected. " +"Servers that have public rooms which are not published to the room " +"directory are also not affected." +msgstr "" + +#: ../../../CHANGELOG.md:801 +msgid "" +"We generally try to stick to the default configuration for Synapse (and " +"all other components), unless these defaults seem wrong or harmful. One " +"such previous case from a few months ago was us [Enabling " +"`forget_rooms_on_leave` by default for Synapse](#enabling-" +"forget_rooms_on_leave-by-default-for-synapse) - the default value was " +"making Synapse more wasteful of resources by default." +msgstr "" + +#: ../../../CHANGELOG.md:803 +msgid "" +"Today, we're going against upstream defaults again and flipping the " +"`allow_public_rooms_over_federation` configuration option to `true`. This" +" way, public rooms on your server will be made discoverable by others via" +" federation, using the [`GET /_matrix/federation/v1/publicRooms` of the " +"Server-Server API](https://spec.matrix.org/v1.8/server-server-" +"api/#get_matrixfederationv1publicrooms)." +msgstr "" + +#: ../../../CHANGELOG.md:805 +msgid "" +"The upstream Synapse default is `false` (disabled), so that public rooms " +"are not exposed for other servers to discover (learn about their " +"existence). Nevertheless, even if these rooms are not exposed (listed) " +"for discovery, they are **still joinable** by anyone who knows their " +"address or is invited to the room by an existing member." +msgstr "" + +#: ../../../CHANGELOG.md:807 +msgid "" +"**We go against the upstream default** in an effort to make Matrix " +"federation more useful - a public room should be globally public - not " +"only joinable, but also discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:809 +msgid "The **historical reasoning** behind this change is as follows:" +msgstr "" + +#: ../../../CHANGELOG.md:811 +msgid "" +"`allow_public_rooms_over_federation` seems to have been enabled by " +"default for Synapse until v1.7.0 (~2019), just like we believe it should " +"be for a globally-federating network - rooms should be joinable and " +"discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:813 +msgid "" +"In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got " +"disabled](https://github.com/element-" +"hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891)" +" by default in a [security-by-" +"obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) " +"workaround for misconfigured servers. See the [Avoiding unwelcome " +"visitors on private Matrix servers](https://matrix.org/blog/2019/11/09" +"/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` " +"blog article. We believe that people wishing for a truly private server, " +"should [disable federation](docs/configuring-playbook-federation.md" +"#disabling-federation), instead of having a fully-federating server and " +"trying to hide its public rooms. We also provide other workarounds below." +" We (and the Synapse team, obviously) believe that Matrix should federate" +" by default, so federating the public room list seems to make sense." +msgstr "" + +#: ../../../CHANGELOG.md:815 +#, python-format +msgid "" +"[etke.cc](https://etke.cc/) has been developing the free-software [Matrix" +" Rooms Search](https://github.com/etkecc/mrs) project for a while now. " +"One public (demo) instance of it is hosted at " +"[matrixrooms.info](https://matrixrooms.info/). This search engine tries " +"to go through the Matrix federation and discover & index public rooms to " +"allow people to find them. We believe it's vital for Matrix (and any chat" +" or social network for that matter) to be more discoverable, so that " +"people can find communities and others to talk to. Today (on 23rd of " +"October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of " +"these, only `1567` servers (7%) are making their public rooms " +"discoverable. Who knows what wonderful communities and rooms are " +"available on these 93% other Matrix servers that are supposedly " +"federating, but are still gate-keeping their public room list. " +"Indubitably, many of these servers are hosted via matrix-docker-ansible-" +"deploy, so we feel partially responsible for making Matrix federation " +"less useful." +msgstr "" + +#: ../../../CHANGELOG.md:817 +msgid "Here are **actions you may wish to take** as a result of this change:" +msgstr "" + +#: ../../../CHANGELOG.md:819 +msgid "" +"(recommended) embrace the new default. If your Matrix server is " +"federating, your public rooms have always been joinable across federation" +" anyway. Exposing the list of public rooms does no harm and more-so does " +"good by contributing to the usefulness of the Matrix network by " +"facilitating room discovery." +msgstr "" + +#: ../../../CHANGELOG.md:821 +msgid "" +"(switch to a better way of doings things on your semi-private server) The" +" problem that the Synapse team appears to have solved by flipping the " +"`allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to " +"for \"mostly private\" servers, which federate and have a bunch of rooms " +"made public (and published in their room directory) in an effort to allow" +" people on the same homeserver to easily find and join them (self-" +"onboarding). With the introduction of Matrix Spaces, you can reorganize " +"your flow around spaces - you can auto-join your users to a Matrix Space " +"(via Synapse's `auto_join_rooms` setting - controlled by our " +"`matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to " +"the space and make them joinable by people belonging to the space. That " +"is to say, do not make rooms public and do not publish them to the room " +"directory unless they are really public. Instead, use other mechanisms " +"for semi-public rooms or private rooms. One alternative is to stick to " +"what you're doing (public rooms published to your rooms directory) but " +"having a `m.federate: true` flag set during creation (clients like " +"Element Web have a nice UI checkbox for this) to explicitly disable " +"federation for them." +msgstr "" + +#: ../../../CHANGELOG.md:823 +msgid "" +"(keeping the old behavior) if you wish to keep doing what you're doing " +"(keeping your Matrix server federating, but hiding its public rooms " +"list), add `matrix_synapse_allow_public_rooms_over_federation: false` to " +"your `vars.yml` configuration. This restores the old behavior. You may " +"also consider [disabling federation](docs/configuring-playbook-" +"federation.md#disabling-federation) completely instead of relying on " +"security-by-obscurity measures." +msgstr "" + +#: ../../../CHANGELOG.md:826 +msgid "2023-10-18" +msgstr "" + +#: ../../../CHANGELOG.md:828 +msgid "Postgres parameters are automatically tuned now" +msgstr "" + +#: ../../../CHANGELOG.md:830 +msgid "" +"The playbook has provided some hints about [Tuning PostgreSQL](docs" +"/maintenance-postgres.md#tuning-postgresql) for quite a while now." +msgstr "" + +#: ../../../CHANGELOG.md:832 +msgid "" +"From now on, the [Postgres Ansible role](https://github.com/mother-of-" +"all-self-hosting/ansible-role-postgres) automatically tunes your Postgres" +" configuration with the same [calculation " +"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" +" that powers https://pgtune.leopard.in.ua/." +msgstr "" + +#: ../../../CHANGELOG.md:834 +msgid "" +"Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) " +"documentation page has details about how you can turn auto-tuning off or " +"adjust the automatically-determined Postgres configuration parameters " +"manually." +msgstr "" + +#: ../../../CHANGELOG.md:836 +msgid "" +"People who [enable load-balancing with Synapse workers](docs/configuring-" +"playbook-synapse.md#load-balancing-with-workers) no longer need to " +"increase the maximum number of Postgres connections manually (previously " +"done via `postgres_process_extra_arguments`). There's a new variable " +"(`postgres_max_connections`) for controlling this number and the playbook" +" automatically raises its value from `200` to `500` for setups which " +"enable workers." +msgstr "" + +#: ../../../CHANGELOG.md:839 +msgid "2023-08-31" +msgstr "" + +#: ../../../CHANGELOG.md:841 +msgid "SchildiChat Web support" +msgstr "" + +#: ../../../CHANGELOG.md:843 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat" +" Web](https://github.com/SchildiChat/schildichat-desktop) client." +msgstr "" + +#: ../../../CHANGELOG.md:845 +msgid "" +"See our [Configuring SchildiChat Web](docs/configuring-playbook-client-" +"schildichat-web.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:848 +msgid "2023-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:850 +msgid "mautrix-wsproxy support" +msgstr "" + +#: ../../../CHANGELOG.md:852 +msgid "" +"Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who " +"finished what was started by [James Reilly](https://github.com/hanthor) " +"and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now " +"supports bridging to Android SMS and Apple iMessage via the [mautrix-" +"wsproxy](https://github.com/mautrix/wsproxy) service (in combination with" +" a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running" +" on your Mac or Android phone)." +msgstr "" + +#: ../../../CHANGELOG.md:854 +msgid "" +"See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple " +"iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) " +"documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:857 +msgid "2023-07-24" +msgstr "" + +#: ../../../CHANGELOG.md:859 +msgid "matrix-registration-bot usage changed" +msgstr "" + +#: ../../../CHANGELOG.md:861 +msgid "" +"[matrix-registration-bot](docs/configuring-playbook-bot-matrix-" +"registration-bot.md) got some updates and now supports password-only-" +"based login. Therefore the bot now doesn't need any manual configuration " +"except setting a password in your `vars.yml`. The bot will be registered " +"as admin and access tokens will be obtained automatically by the bot." +msgstr "" + +#: ../../../CHANGELOG.md:863 +msgid "" +"**For existing users** You need to set " +"`matrix_bot_matrix_registration_bot_bot_password` if you previously only " +"used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also " +"remove the following deprecated settings" +msgstr "" + +#: ../../../CHANGELOG.md:865 +msgid "`matrix_bot_matrix_registration_bot_bot_access_token`" +msgstr "" + +#: ../../../CHANGELOG.md:866 +msgid "`matrix_bot_matrix_registration_bot_api_token`" +msgstr "" + +#: ../../../CHANGELOG.md:869 +msgid "2023-07-21" +msgstr "" + +#: ../../../CHANGELOG.md:871 +msgid "mautrix-gmessages support" +msgstr "" + +#: ../../../CHANGELOG.md:873 +msgid "" +"Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, " +"the playbook now supports bridging to [Google " +"Messages](https://messages.google.com/) via the [mautrix-" +"gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting" +" up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-" +"mautrix-gmessages.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:876 +msgid "2023-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:878 +msgid "matrix-media-repo support" +msgstr "" + +#: ../../../CHANGELOG.md:880 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook can now set up [matrix-media-" +"repo](https://github.com/turt2live/matrix-media-repo) - an alternative " +"way to store homeserver media files, powered by a homeserver-independent " +"implementation which supports S3 storage, IPFS, deduplication and other " +"advanced features." +msgstr "" + +#: ../../../CHANGELOG.md:882 +msgid "" +"To learn more see our [Storing Matrix media files using matrix-media-" +"repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:885 +msgid "2023-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:887 +msgid "Enabling `forget_rooms_on_leave` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:889 +msgid "" +"With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/2698), we've also **changed the default " +"value** of the `forget_rooms_on_leave` setting of Synapse to a value of " +"`true`. This way, **when you leave a room, Synapse will now forget it " +"automatically**." +msgstr "" + +#: ../../../CHANGELOG.md:891 +msgid "" +"The upstream Synapse default is `false` (disabled), so that you must " +"forget rooms manually after leaving." +msgstr "" + +#: ../../../CHANGELOG.md:893 +msgid "" +"**We go against the upstream default** ([somewhat " +"controversially](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/2700)) in an effort to make Synapse leaner and potentially do" +" what we believe most users would expect their homeserver to be doing." +msgstr "" + +#: ../../../CHANGELOG.md:895 +msgid "" +"If you'd like to go back to the old behavior, add the following to your " +"configuration: `matrix_synapse_forget_rooms_on_leave: false`" +msgstr "" + +#: ../../../CHANGELOG.md:898 +msgid "2023-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:900 +msgid "The matrix-jitsi role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:902 +msgid "" +"**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-" +"jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) " +"repository, part of the [MASH playbook](https://github.com/mother-of-all-" +"self-hosting/mash-playbook). Some variables have been renamed. All " +"functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:904 +msgid "" +"The `matrix-jitsi` role has been relocated in its own repository, part of" +" the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) project - an Ansible playbook for self-hosting [a growing list " +"of FOSS software](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack " +"on the Matrix server itself did not stand right with you or you always " +"wanted to host most stuff, you can now use this new playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:906 +msgid "" +"As part of the extraction process of this role out of the Matrix " +"playbook, a few other things improved:" +msgstr "" + +#: ../../../CHANGELOG.md:908 +msgid "**native Traefik support** has been added" +msgstr "" + +#: ../../../CHANGELOG.md:909 +msgid "" +"**support for hosting under a subpath** has been added, although it " +"suffers from a few minor issues listed [here](https://github.com/mother-" +"of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" +msgstr "" + +#: ../../../CHANGELOG.md:911 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Jitsi or not." +msgstr "" + +#: ../../../CHANGELOG.md:913 +msgid "" +"If you're making use of Jitsi via this playbook, you will need to update " +"variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:915 +msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:916 +msgid "`matrix_jitsi_` -> `jitsi_`" +msgstr "" + +#: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944 +msgid "" +"some other internal variables have changed, but the playbook will tell " +"you about them" +msgstr "" + +#: ../../../CHANGELOG.md:919 +msgid "2023-03-22" +msgstr "" + +#: ../../../CHANGELOG.md:921 +msgid "ntfy Web App is disabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:923 +msgid "" +"ntfy provides a web app, which is now disabled by default, because it may" +" be unknown to and unused by most users of this playbook. You can enable " +"it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs" +"/configuring-playbook-ntfy.md))." +msgstr "" + +#: ../../../CHANGELOG.md:925 +msgid "" +"This change was already applied a while before this entry, but as some " +"users were reporting the missing web app, this entry was added (see " +"[#2529](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/2529))." +msgstr "" + +#: ../../../CHANGELOG.md:928 +msgid "2023-03-21" +msgstr "" + +#: ../../../CHANGELOG.md:930 +msgid "The matrix-prometheus role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:932 +msgid "" +"**TLDR**: the `matrix-prometheus` role is now included from the [ansible-" +"role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-" +"role-prometheus) repository, part of the [MASH " +"playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). " +"Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:934 +msgid "" +"The `matrix-prometheus` role has been relocated in its own repository, " +"part of the [MASH playbook](https://github.com/mother-of-all-self-hosting" +"/mash-playbook) project - an Ansible playbook for self-hosting [a growing" +" list of FOSS software](https://github.com/mother-of-all-self-hosting" +"/mash-playbook/blob/main/docs/supported-services.md). If hosting a " +"Prometheus stack on the Matrix server itself did not stand right with you" +" or you always wanted to host most stuff, you can now use this new " +"playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:936 +msgid "" +"Extracting the Prometheus role out of this Matrix playbook required huge " +"internal refactoring to the way the Prometheus configuration (scraping " +"jobs) is generated. If you notice any breakage after upgrading, let us " +"know." +msgstr "" + +#: ../../../CHANGELOG.md:938 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Prometheus or not." +msgstr "" + +#: ../../../CHANGELOG.md:940 +msgid "" +"If you're making use of Prometheus via this playbook, you will need to " +"update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:942 +msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:943 +msgid "`matrix_prometheus_` -> `prometheus_`" +msgstr "" + +#: ../../../CHANGELOG.md:947 +msgid "2023-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:949 +msgid "synapse-auto-compressor support" +msgstr "" + +#: ../../../CHANGELOG.md:951 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-" +"compress-state](https://github.com/matrix-org/rust-synapse-compress-" +"state)'s `synapse_auto_compressor` tool to run periodically." +msgstr "" + +#: ../../../CHANGELOG.md:953 +msgid "" +"If enabled, `synapse_auto_compressor` runs on a schedule and compresses " +"your Synapse database's `state_groups` table. It was possible to run " +"`rust-synapse-compress-state` manually via the playbook even before - see" +" [Compressing state with rust-synapse-compress-state](docs/maintenance-" +"synapse.md#compressing-state-with-rust-synapse-compress-state). However, " +"using `synapse_auto_compressor` is better, because:" +msgstr "" + +#: ../../../CHANGELOG.md:955 +msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" +msgstr "" + +#: ../../../CHANGELOG.md:956 +msgid "" +"it's a set-it-and-forget-it tool that you can enable and never have to " +"deal with manual compression anymore" +msgstr "" + +#: ../../../CHANGELOG.md:958 +msgid "" +"This tool needs to be enabled manually, for now. In the future, we're " +"considering enabling it by default for all Synapse installations." +msgstr "" + +#: ../../../CHANGELOG.md:960 +msgid "" +"See our [Setting up synapse-auto-compressor](docs/configuring-playbook-" +"synapse-auto-compressor.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:963 +msgid "2023-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:965 +msgid "Sliding Sync proxy (Element X) support" +msgstr "" + +#: ../../../CHANGELOG.md:967 +msgid "" +"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting " +"it started](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up" +" and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the" +" playbook can now install and configure the [sliding-sync " +"proxy](https://github.com/matrix-org/sliding-sync)." +msgstr "" + +#: ../../../CHANGELOG.md:969 +msgid "" +"The upcoming Element X clients ([Element X iOS](https://github.com" +"/vector-im/element-x-ios) and [Element X Android](https://github.com" +"/vector-im/element-x-android)) require the `sliding-sync` proxy to do " +"their job. **These clients are still in beta** (especially Element X " +"Android, which requires manual compilation to get it working with a " +"non-`matrix.org` homeseserver). Playbook users can now easily give these " +"clients a try and help test them thanks to us having `sliding-sync` " +"support." +msgstr "" + +#: ../../../CHANGELOG.md:971 +msgid "" +"To get started, see our [Setting up the Sliding Sync proxy](docs" +"/configuring-playbook-sliding-sync-proxy.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:974 +msgid "2023-03-02" +msgstr "" + +#: ../../../CHANGELOG.md:976 +msgid "The matrix-etherpad role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:978 +msgid "" +"**TLDR**: the `matrix-etherpad` role is now included from [another " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"etherpad). Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:980 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Etherpad or not." +msgstr "" + +#: ../../../CHANGELOG.md:982 +msgid "" +"If you're making use of Etherpad via this playbook, you will need to " +"update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:984 +msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`" +msgstr "" + +#: ../../../CHANGELOG.md:986 +msgid "Replace `matrix_etherpad_mode: dimension` with:" +msgstr "" + +#: ../../../CHANGELOG.md:987 +msgid "for `matrix-nginx-proxy` users:" +msgstr "" + +#: ../../../CHANGELOG.md:988 +msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`" +msgstr "" + +#: ../../../CHANGELOG.md:989 +msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:990 +msgid "for Traefik users:" +msgstr "" + +#: ../../../CHANGELOG.md:991 +msgid "" +"define your own `etherpad_hostname` and `etherpad_path_prefix` as you see" +" fit" +msgstr "" + +#: ../../../CHANGELOG.md:993 +msgid "Rename all other variables:" +msgstr "" + +#: ../../../CHANGELOG.md:994 +msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:995 +msgid "`matrix_etherpad_` -> `etherpad_`" +msgstr "" + +#: ../../../CHANGELOG.md:997 +msgid "Along with this relocation, the new role also:" +msgstr "" + +#: ../../../CHANGELOG.md:999 +msgid "" +"supports [self-building](docs/self-building.md), so it should work on " +"`arm32` and `arm64` architectures" +msgstr "" + +#: ../../../CHANGELOG.md:1000 +msgid "" +"has native Traefik reverse-proxy support (Etherpad requests no longer go " +"through `matrix-nginx-proxy` when using Traefik)" +msgstr "" + +#: ../../../CHANGELOG.md:1003 +msgid "2023-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:1005 +msgid "Traefik is the default reverse-proxy now" +msgstr "" + +#: ../../../CHANGELOG.md:1007 +msgid "" +"**TLDR**: new installations will now default to Traefik as their reverse-" +"proxy. Existing users need to explicitly choose their reverse-proxy type." +" [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is" +" strongly encouraged. `matrix-nginx-proxy` may break over time and will " +"ultimately be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1009 +msgid "" +"As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy " +"configuration changes and initial Traefik support](#backward-" +"compatibility-reverse-proxy-configuration-changes-and-initial-traefik-" +"support), the playbook is moving to Traefik as its default SSL-" +"terminating reverse-proxy." +msgstr "" + +#: ../../../CHANGELOG.md:1011 +msgid "" +"Until now, we've been doing the migration gradually and keeping full " +"backward compatibility. New installations were defaulting to `matrix-" +"nginx-proxy` (just like before), while existing installations were " +"allowed to remain on `matrix-nginx-proxy` as well. This makes things very" +" difficult for us, because we need to maintain and think about lots of " +"different setups:" +msgstr "" + +#: ../../../CHANGELOG.md:1013 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1014 +msgid "Traefik managed by the user in another way" +msgstr "" + +#: ../../../CHANGELOG.md:1015 +msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1016 +msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1017 +msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1018 +msgid "" +"`nginx` webserver operated by the user, running without a container on " +"the same server" +msgstr "" + +#: ../../../CHANGELOG.md:1020 +msgid "" +"Each change we do and each new feature that comes in needs to support all" +" these different ways of reverse-proxying. Because `matrix-nginx-proxy` " +"was the default and pretty much everyone was (and still is) using it, " +"means that new PRs also come with `matrix-nginx-proxy` as their main " +"focus and Traefik as an afterthought, which means we need to spend hours " +"fixing up Traefik support." +msgstr "" + +#: ../../../CHANGELOG.md:1022 +msgid "" +"We can't spend all this time maintaining so many different configurations" +" anymore. Traefik support has been an option for 2 weeks and lots of " +"people have already migrated their server and have tested things out. " +"Traefik is what we use and preferentially test for." +msgstr "" + +#: ../../../CHANGELOG.md:1024 +msgid "" +"It's time for the **next step in our migration process** to Traefik and " +"elimination of `matrix-nginx-proxy`:" +msgstr "" + +#: ../../../CHANGELOG.md:1026 +msgid "Traefik is now the default reverse-proxy for new installations" +msgstr "" + +#: ../../../CHANGELOG.md:1027 +msgid "" +"All existing users need to explicitly choose their reverse-proxy type by " +"defining the `matrix_playbook_reverse_proxy_type` variable in their " +"`vars.yml` configuration file. We strongly encourage existing users to " +"[switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the" +" nginx setup is bound to become more and more broken over time until it's" +" ultimately removed" +msgstr "" + +#: ../../../CHANGELOG.md:1029 +msgid "How do I switch my existing setup to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1031 +msgid "" +"**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy " +"provided by the playbook), switching to Traefik can happen with a simple " +"configuration change. Follow this section from 2 weeks ago: [How do I " +"explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-" +"traefik-right-now)." +msgstr "" + +#: ../../../CHANGELOG.md:1033 +msgid "If you experience trouble:" +msgstr "" + +#: ../../../CHANGELOG.md:1035 +msgid "" +"Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-" +"matrix-nginx-proxy) to bring your server back online using the old " +"reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:1036 +msgid "Ask for help in our [support channels](README.md#support)" +msgstr "" + +#: ../../../CHANGELOG.md:1037 +msgid "Try switching to Traefik again later" +msgstr "" + +#: ../../../CHANGELOG.md:1039 +msgid "" +"**For users with a more special reverse-proxying setup** (another nginx " +"server, Apache, Caddy, etc.), the migration may not be so smooth. Follow " +"the [Using your own webserver](docs/configuring-playbook-own-" +"webserver.md) guide. Ideally, your custom reverse-proxy will be " +"configured in such a way that it **fronts the Traefik reverse-proxy** " +"provided by the playbook. Other means of reverse-proxying are more " +"fragile and may be deprecated in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1041 +msgid "I already use my own Traefik server. How do I plug that in?" +msgstr "" + +#: ../../../CHANGELOG.md:1043 +msgid "" +"See the [Traefik managed by the playbook](docs/configuring-playbook-own-" +"webserver.md#traefik-managed-by-the-playbook) section." +msgstr "" + +#: ../../../CHANGELOG.md:1045 +msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1047 +msgid "" +"This playbook manages many different services. All these services were " +"initially integrated with `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:1049 +msgid "" +"While we migrate all these components to have native Traefik support, " +"some still go through nginx internally (Traefik -> local `matrix-nginx-" +"proxy` -> component). As time goes on, internal reliance on `matrix-" +"nginx-proxy` will gradually decrease until it's completely removed." +msgstr "" + +#: ../../../CHANGELOG.md:1051 +msgid "How do I remain on matrix-nginx-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1053 +msgid "" +"Most new work and testing targets Traefik, so remaining on nginx is " +"**not** \"the good old stable\" option, but rather the \"still available," +" but largely untested and likely to be broken very soon\" option." +msgstr "" + +#: ../../../CHANGELOG.md:1055 +msgid "" +"To proceed regardless of this warning, add " +"`matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your " +"configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1057 +msgid "" +"At some point in the **near** future (days, or even weeks at most), we " +"hope to completely get rid of `matrix-nginx-proxy` (or break it enough to" +" make it unusable), so you **will soon be forced to migrate** anyway. " +"Plan your migration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:1059 +msgid "How do I keep using my own other reverse-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1061 +msgid "" +"We recommend that you follow the guide for [Fronting the integrated " +"reverse-proxy webserver with another reverse-proxy](docs/configuring-" +"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" +"webserver-with-another-reverse-proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:1064 +msgid "2023-02-25" +msgstr "" + +#: ../../../CHANGELOG.md:1066 +msgid "rageshake support" +msgstr "" + +#: ../../../CHANGELOG.md:1068 +msgid "" +"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook" +" can now install and configure the [rageshake](https://github.com/matrix-" +"org/rageshake) bug report server." +msgstr "" + +#: ../../../CHANGELOG.md:1070 +msgid "" +"Additional details are available in [Setting up rageshake](docs" +"/configuring-playbook-rageshake.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1073 +msgid "2023-02-17" +msgstr "" + +#: ../../../CHANGELOG.md:1075 +msgid "Synapse templates customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1077 +msgid "The playbook can now help you customize Synapse's templates." +msgstr "" + +#: ../../../CHANGELOG.md:1079 +msgid "" +"Additional details are available in the [Customizing templates](docs" +"/configuring-playbook-synapse.md#customizing-templates) section of our " +"Synapse documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1081 +msgid "The matrix-redis role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1083 +msgid "" +"**TLDR**: the `matrix-redis` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1085 +msgid "" +"The `matrix-redis` role (which configures [Redis](https://redis.io/)) has" +" been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"redis). This makes it possible to easily use it in other Ansible " +"playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1087 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Ntfy or not. If you're making use " +"of Ntfy via this playbook, you will need to update variable references in" +" your `vars.yml` file (`matrix_redis_` -> `redis_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1089 +msgid "The matrix-ntfy role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1091 +msgid "" +"**TLDR**: the `matrix-ntfy` role is now included from another repository." +" Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1093 +msgid "" +"The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has " +"been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"ntfy). This makes it possible to easily use it in other Ansible " +"playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1095 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Ntfy or not. If you're making use " +"of Ntfy via this playbook, you will need to update variable references in" +" your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1098 +msgid "2023-02-15" +msgstr "" + +#: ../../../CHANGELOG.md:1100 +msgid "The matrix-grafana role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1102 +msgid "" +"**TLDR**: the `matrix-grafana` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1104 +msgid "" +"The `matrix-grafana` role (which configures [Grafana](docs/configuring-" +"playbook-prometheus-grafana.md)) has been extracted from the playbook and" +" now lives in its [own repository](https://github.com/mother-of-all-self-" +"hosting/ansible-role-grafana). This makes it possible to easily use it in" +" other Ansible playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1106 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Grafana or not. If you're making " +"use of Grafana via this playbook, you will need to update variable " +"references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1109 +msgid "2023-02-13" +msgstr "" + +#: ../../../CHANGELOG.md:1111 +msgid "The matrix-backup-borg role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1113 +msgid "" +"**TLDR**: the `matrix-backup-borg` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1115 +msgid "" +"Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` " +"role (which configures [BorgBackup](docs/configuring-playbook-backup-" +"borg.md)) has been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"backup_borg). This makes it possible to easily use it in other Ansible " +"playbooks and will become part of [nextcloud-docker-ansible-" +"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) " +"soon." +msgstr "" + +#: ../../../CHANGELOG.md:1117 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Borg's backup functionality or not." +" If you're making use of BorgBackup via this playbook, you will need to " +"update variable references in your `vars.yml` file (`matrix_backup_borg_`" +" -> `backup_borg_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1120 +msgid "2023-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1122 +msgid "" +"(Backward Compatibility) Reverse-proxy configuration changes and initial " +"Traefik support" +msgstr "" + +#: ../../../CHANGELOG.md:1124 +msgid "**TLDR**:" +msgstr "" + +#: ../../../CHANGELOG.md:1126 +msgid "" +"there's a new `matrix_playbook_reverse_proxy_type` variable (see " +"[roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-" +"base/defaults/main.yml)), which lets you tell the playbook what reverse-" +"proxy setup you'd like to have. This makes it easier for people who want " +"to do reverse-proxying in other ways." +msgstr "" + +#: ../../../CHANGELOG.md:1127 +msgid "" +"the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still" +" `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing" +" `matrix-nginx-proxy` users should not observe any changes** and can stay" +" on this for now." +msgstr "" + +#: ../../../CHANGELOG.md:1128 +msgid "" +"**Users who use their [own other webserver](docs/configuring-playbook-" +"own-webserver.md) (e.g. Apache, etc.) need to change** " +"`matrix_playbook_reverse_proxy_type` to something like `other-on-same-" +"host`, `other-on-another-host` or `other-nginx-non-container`" +msgstr "" + +#: ../../../CHANGELOG.md:1129 +msgid "" +"we now have **optional [Traefik](https://traefik.io/) support**, so you " +"could easily host Matrix and other Traefik-native services in containers " +"on the same server. Traefik support is still experimental (albeit, good " +"enough) and will improve over time. It does work, but certain esoteric " +"features may not be there yet." +msgstr "" + +#: ../../../CHANGELOG.md:1130 +msgid "" +"**Traefik will become the default reverse-proxy in the near future**. " +"`matrix-nginx-proxy` will either remain as an option, or be completely " +"removed to simplify the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1132 +msgid "Motivation for redoing our reverse-proxy setup" +msgstr "" + +#: ../../../CHANGELOG.md:1134 +msgid "" +"The playbook has supported various reverse-proxy setups for a long time. " +"We have various configuration variables (`matrix_nginx_proxy_enabled`, " +"various `_host_bind_port` variables, etc.) which allow the playbook to " +"adapt to these different setups. The whole situation was messy though - " +"hard to figure out and with lots of variables to toggle to make things " +"work as you'd expect - huge **operational complexity**." +msgstr "" + +#: ../../../CHANGELOG.md:1136 +msgid "" +"We love containers, proven by the fact that **everything** that this " +"playbook manages runs in a container. Yet, we weren't allowing people to " +"easily host other web-exposed containers alongside Matrix services on the" +" same server. We were using `matrix-nginx-proxy` (our integrated " +"[nginx](https://nginx.org/) server), which was handling web-exposure and " +"SSL termination for our own services, but we **weren't helping you with " +"all your other containers**." +msgstr "" + +#: ../../../CHANGELOG.md:1138 +msgid "" +"People who were **using `matrix-nginx-proxy`** were on the happy path on " +"which everything worked well by default (Matrix-wise), **but** could not " +"easily run other web-exposed services on their Matrix server because " +"`matrix-nginx-proxy` was occupying ports `80` and `443`. Other services " +"which wanted to get web exposure either had to be plugged into `matrix-" +"nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-" +"nginx-proxy` in favor of something else." +msgstr "" + +#: ../../../CHANGELOG.md:1140 +msgid "" +"Of those that decided to forgo `matrix-nginx-proxy`, many were **using " +"nginx** on the same server without a container. This was likely some " +"ancient nginx version, depending on your choice of distro. The Matrix " +"playbook was trying to be helpful and even with " +"`matrix_nginx_proxy_enabled: false` was still generating nginx " +"configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files " +"were adapted for inclusion into an nginx server running locally. " +"Disabling the `matrix-nginx-proxy` role like this, yet still having it " +"produce files is a bit disgusting, but it's what we've had since the " +"early beginnings of this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1142 +msgid "" +"Others still, wanted to run Matrix locally (no SSL certificates), " +"regardless of which web server technology this relied on, and then " +"**reverse-proxy from another machine on the network** which was doing SSL" +" termination. These people were:" +msgstr "" + +#: ../../../CHANGELOG.md:1144 +msgid "" +"*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined" +" with exposing services manually (setting `_bind_port` variables)" +msgstr "" + +#: ../../../CHANGELOG.md:1145 +msgid "" +"*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in " +"`http`-only mode (no SSL certificate retrieval)." +msgstr "" + +#: ../../../CHANGELOG.md:1147 +msgid "" +"Despite this operational complexity, things worked and were reasonably " +"flexible to adapt to all these situations." +msgstr "" + +#: ../../../CHANGELOG.md:1149 +msgid "" +"When using `matrix-nginx-proxy` as is, we still had another problem - one" +" of **internal playbook complexity**. Too many services need to be web-" +"exposed (port 80/443, SSL certificates). Because of this, they all had to" +" integrate with the `matrix-nginx-proxy` role. Tens of different roles " +"explicitly integrating with `matrix-nginx-proxy` is not what we call " +"clean. The `matrix-nginx-proxy` role contains variables for many of these" +" roles (yikes). Other roles were more decoupled from it and were " +"injecting configuration into `matrix-nginx-proxy` at runtime - see all " +"the `inject_into_nginx_proxy.yml` task files in this playbook (more " +"decoupled, but still.. yikes)." +msgstr "" + +#: ../../../CHANGELOG.md:1151 +msgid "" +"The next problem is one of **efficiency, interoperability and cost-" +"saving**. We're working on other playbooks:" +msgstr "" + +#: ../../../CHANGELOG.md:1153 +msgid "" +"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" +"/vaultwarden-docker-ansible-deploy) for hosting the " +"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an " +"alternative implementation of the [Bitwarden](https://bitwarden.com/) " +"password manager" +msgstr "" + +#: ../../../CHANGELOG.md:1154 +msgid "" +"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source " +"code hosting service" +msgstr "" + +#: ../../../CHANGELOG.md:1155 +msgid "" +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy) - for hosting the " +"[Nextcloud](https://nextcloud.com/) groupware platform" +msgstr "" + +#: ../../../CHANGELOG.md:1157 +msgid "" +"We'd love for users to be able to **seamlessly use all these playbooks " +"(and others, even) against a single server**. We don't want `matrix-" +"nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for " +"other services to join in on the party. Such a thing forces people into " +"running multiple servers (one for each service), which does provide nice " +"security benefits, but is costly and ineffiecient. We'd like to make " +"self-hosting these services cheap and easy." +msgstr "" + +#: ../../../CHANGELOG.md:1159 +msgid "" +"These other playbooks have been using [Traefik](https://traefik.io/) as " +"their default reverse-proxy for a long time. They can all coexist nicely " +"together (as an example, see the " +"[Interoperability](https://github.com/spantaleev/nextcloud-docker-" +"ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md)" +" documentation for the [Nextcloud playbook](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining " +"Traefik support, it will be able to interoperate with them. If you're " +"going this way, make sure to have the Matrix playbook install Traefik and" +" have the others use `*_reverse_proxy_type: other-traefik-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1161 +msgid "" +"Finally, at [etke.cc - a managed Matrix server hosting " +"service](https://etke.cc) (built on top of this playbook, and " +"coincidentally [turning 2 years old today](https://etke.cc/news" +"/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people " +"to host some additional services besides Matrix components. Exposing " +"these services to the web requires ugly hacks and configuration files " +"being dropped into `/matrix/nginx-proxy/conf.d`. We believe that " +"everything should run in independent containers and be exposed to the web" +" via a Traefik server, without a huge Ansible role like `matrix-nginx-" +"proxy` that everything else needs to integrate with." +msgstr "" + +#: ../../../CHANGELOG.md:1163 +msgid "How do these changes fix all these problems?" +msgstr "" + +#: ../../../CHANGELOG.md:1165 +msgid "" +"The new `matrix_playbook_reverse_proxy_type` lets you easily specify your" +" preferred reverse-proxy type, including `other-on-same-host`, `other-on-" +"another-host` and `none`, so people who'd like to reverse-proxy with " +"their own web server have more options now." +msgstr "" + +#: ../../../CHANGELOG.md:1167 +msgid "" +"Using Traefik greatly simplifies things, so going forward we'll have a " +"simpler and easier to maintain playbook, which is also interoperable with" +" other services." +msgstr "" + +#: ../../../CHANGELOG.md:1169 +msgid "" +"Traefik is a web server, which has been specifically **designed for " +"reverse-proxying to services running in containers**. It's ideal for " +"usage in an Ansible playbook which runs everything in containers." +msgstr "" + +#: ../../../CHANGELOG.md:1171 +msgid "" +"**Traefik obtains SSL certificates automatically**, so there's no need " +"for plugging additional tools like [Certbot](https://certbot.eff.org/) " +"into your web server (like we were doing in the `matrix-nginx-proxy` " +"role). No more certificate renewal timers, web server reloading timers, " +"etc. It's just simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1173 +msgid "" +"Traefik is a **modern web server**. " +"[HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is " +"supported already (experimentally) and will move to stable soon, in the " +"upcoming Traefik v3 release." +msgstr "" + +#: ../../../CHANGELOG.md:1175 +msgid "" +"Traefik does not lock important functionality we'd like to use into [plus" +" packages like nginx does](https://www.nginx.com/products/nginx/), " +"leading us to resolve to configuration workarounds. The default Traefik " +"package is good enough as it is." +msgstr "" + +#: ../../../CHANGELOG.md:1177 +msgid "Where we're at right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1179 +msgid "" +"`matrix_playbook_reverse_proxy_type` still defaults to a value of " +"`playbook-managed-nginx`." +msgstr "" + +#: ../../../CHANGELOG.md:1181 +msgid "" +"Unless we have some regression, **existing `matrix-nginx-proxy` users " +"should be able to update their Matrix server and not observe any " +"changes**. Their setup should still remain on nginx and everything should" +" still work as expected." +msgstr "" + +#: ../../../CHANGELOG.md:1183 +msgid "" +"**Users using [their own webservers](docs/configuring-playbook-own-" +"webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** " +"to something like `other-on-same-host`, `other-on-another-host` or " +"`other-nginx-non-container`. Previously, they could toggle " +"`matrix_nginx_proxy_enabled` to `false`, and that made the playbook " +"automatically expose services locally. Currently, we only do this if you " +"change the reverse-proxy type to `other-on-same-host`, `other-on-another-" +"host` or `other-nginx-non-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1185 +msgid "How do I explicitly switch to Traefik right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1187 +msgid "" +"**Users who wish to migrate to Traefik** today, can do so by **adding** " +"this to their configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1195 +msgid "" +"You may still need to keep certain old `matrix_nginx_proxy_*` variables " +"(like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using " +"Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` " +"variables just in case. In the future, reliance on `matrix-nginx-proxy` " +"will be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1197 +msgid "" +"Switching to Traefik will obtain new SSL certificates from Let's Encrypt " +"(stored in `/matrix/traefik/ssl/acme.json`). **The switch is " +"reversible**. You can always go back to `playbook-managed-nginx` if " +"Traefik is causing you trouble." +msgstr "" + +#: ../../../CHANGELOG.md:1199 +msgid "" +"**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik " +"and nginx will uninstall the Traefik role and all of its data (under " +"`/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you" +" do it often." +msgstr "" + +#: ../../../CHANGELOG.md:1201 +msgid "" +"Treafik directly reverse-proxies to **some** services right now, but for " +"most other services it goes through `matrix-nginx-proxy` (e.g. Traefik ->" +" `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, " +"even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being" +" installed in local-only mode. This will improve with time." +msgstr "" + +#: ../../../CHANGELOG.md:1203 +msgid "" +"Some services (like [Coturn](docs/configuring-playbook-turn.md) and " +"[Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be " +"reverse-proxied to directly from Traefik, so they require direct access " +"to SSL certificate files extracted out of Traefik. The playbook does this" +" automatically thanks to a new " +"[com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper)" +" role utilizing the [traefik-certs-dumper](https://github.com/ldez" +"/traefik-certs-dumper) tool." +msgstr "" + +#: ../../../CHANGELOG.md:1205 +msgid "" +"Our Traefik setup mostly works, but certain esoteric features may not " +"work. If you have a default setup, we expect you to have a good " +"experience." +msgstr "" + +#: ../../../CHANGELOG.md:1207 +msgid "Where we're going in the near future?" +msgstr "" + +#: ../../../CHANGELOG.md:1209 +msgid "" +"The `matrix-nginx-proxy` role is quite messy. It manages both nginx and " +"Certbot and its certificate renewal scripts and timers. It generates " +"configuration even when the role is disabled (weird). Although it doesn't" +" directly reach into variables from other roles, it has explicit " +"awareness of various other services that it reverse-proxies to " +"(`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-" +"ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is " +"probably to just get rid of the whole thing at some point." +msgstr "" + +#: ../../../CHANGELOG.md:1211 +msgid "For now, `matrix-nginx-proxy` will stay around." +msgstr "" + +#: ../../../CHANGELOG.md:1213 +msgid "" +"As mentioned above, Traefik still reverse-proxies to some (most) services" +" by going through a local-only `matrix-nginx-proxy` server. This has " +"allowed us to add Traefik support to the playbook early on (without " +"having to rework all services), but is not the final goal. We'll **work " +"on making each service support Traefik natively**, so that traffic will " +"not need to go through `matrix-nginx-proxy` anymore. In the end, choosing" +" Traefik should only give you a pure Traefik installation with no " +"`matrix-nginx-proxy` in sight." +msgstr "" + +#: ../../../CHANGELOG.md:1215 +msgid "" +"As Traefik support becomes complete and proves to be stable for a while, " +"especially as a playbook default, we will **most likely remove `matrix-" +"nginx-proxy` completely**. It will likely be some months before this " +"happens though. Keeping support for both Traefik and nginx in the " +"playbook will be a burden, especially with most of us running Traefik in " +"the future. The Traefik role should do everything nginx does in a better " +"and cleaner way. Users who use their own `nginx` server on the Matrix " +"server will be inconvenienced, as nothing will generate ready-to-include " +"nginx configuration for them. Still, we hope it won't be too hard to " +"migrate their setup to another way of doing things, like:" +msgstr "" + +#: ../../../CHANGELOG.md:1217 +msgid "" +"not using nginx anymore. A common reason for using nginx until now was " +"that you were running other containers and you need your own nginx to " +"reverse-proxy to all of them. Just switch them to Traefik as well." +msgstr "" + +#: ../../../CHANGELOG.md:1218 +msgid "" +"running Traefik in local-only mode " +"(`traefik_config_entrypoint_web_secure_enabled: false`) and using some " +"nginx configuration which reverse-proxies to Traefik (we should introduce" +" examples for this in `examples/nginx`)." +msgstr "" + +#: ../../../CHANGELOG.md:1220 +msgid "How do I help?" +msgstr "" + +#: ../../../CHANGELOG.md:1222 +msgid "You can help by:" +msgstr "" + +#: ../../../CHANGELOG.md:1224 +msgid "" +"**explicitly switching your server to Traefik** right now (see example " +"configuration in [How do I explicitly switch to Traefik right now?](#how-" +"do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting " +"troubles" +msgstr "" + +#: ../../../CHANGELOG.md:1226 +msgid "" +"**adding native Traefik support to a role** (requires adding Traefik " +"labels, etc.) - for inspiration, see these roles " +"([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting" +"/ansible-role-prometheus-node-exporter), " +"[prometheus_postgres_exporter](https://github.com/mother-of-all-self-" +"hosting/ansible-role-prometheus-postgres-exporter)) and how they're " +"hooked into the playbook via " +"[group_vars/matrix_servers](group_vars/matrix_servers)." +msgstr "" + +#: ../../../CHANGELOG.md:1228 +msgid "" +"**adding reverse-proxying examples for nginx users** in `examples/nginx`." +" People who insist on using their own `nginx` server on the same Matrix " +"host, can run Traefik in local-only mode " +"(`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy" +" to the Traefik server" +msgstr "" + +#: ../../../CHANGELOG.md:1231 +msgid "2023-02-10" +msgstr "" + +#: ../../../CHANGELOG.md:1233 +msgid "Matrix Authentication Support for Jitsi" +msgstr "" + +#: ../../../CHANGELOG.md:1235 +msgid "" +"Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk " +"gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for " +"authentication (via [Matrix User Verification Service](https://github.com" +"/matrix-org/matrix-user-verification-service))." +msgstr "" + +#: ../../../CHANGELOG.md:1237 +msgid "" +"Additional details are available in the [Authenticate using Matrix OpenID" +" (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-" +"using-matrix-openid-auth-type-matrix)." +msgstr "" + +#: ../../../CHANGELOG.md:1239 +msgid "Draupnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:1241 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " +"install and configure the [Draupnir](https://github.com/the-draupnir-" +"project/Draupnir) moderation tool (bot). Draupnir is a fork of " +"[Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook " +"has supported for a long time) maintained by Mjolnir's former lead " +"developer." +msgstr "" + +#: ../../../CHANGELOG.md:1243 +msgid "" +"Additional details are available in [Setting up Draupnir](docs" +"/configuring-playbook-bot-draupnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1246 +msgid "2023-02-05" +msgstr "" + +#: ../../../CHANGELOG.md:1248 +msgid "The matrix-prometheus-postgres-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1250 +msgid "" +"**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included " +"from another repository. Some variables have been renamed. All " +"functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1252 +msgid "" +"The `matrix-prometheus-postgres-exporter` role (which configures " +"[Prometheus Postgres Exporter](https://github.com/prometheus-" +"community/postgres_exporter)) has been extracted from the playbook and " +"now lives in its own repository at https://github.com/mother-of-all-self-" +"hosting/ansible-role-prometheus-postgres-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1254 +msgid "" +"It's still part of the playbook, but is now installed via `ansible-" +"galaxy` (by running `just roles` / `make roles`). Some variables have " +"been renamed (`matrix_prometheus_postgres_exporter_` -> " +"`prometheus_postgres_exporter_`, etc.). The playbook will report all " +"variables that you need to rename to get upgraded. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1256 +msgid "" +"The `matrix-prometheus-services-proxy-connect` role has bee adjusted to " +"help integrate the new `prometheus_postgres_exporter` role with our own " +"services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300 +msgid "" +"Other roles which aren't strictly related to Matrix are likely to follow " +"this fate of moving to their own repositories. Extracting them out allows" +" other Ansible playbooks to make use of these roles easily." +msgstr "" + +#: ../../../CHANGELOG.md:1261 +msgid "2023-01-26" +msgstr "" + +#: ../../../CHANGELOG.md:1263 +msgid "Coturn can now use host-networking" +msgstr "" + +#: ../../../CHANGELOG.md:1265 +msgid "" +"Large Coturn deployments (with a huge range of ports specified via " +"`matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) " +"experience a huge slowdown with how Docker publishes all these ports " +"(setting up firewall forwarding rules), which leads to a very slow Coturn" +" service startup and shutdown." +msgstr "" + +#: ../../../CHANGELOG.md:1267 +msgid "" +"Such deployments don't need to run Coturn within a private container " +"network anymore. Coturn can now run with host-networking by using " +"configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1273 +msgid "" +"With such a configuration, **Docker no longer needs to configure " +"thousands of firewall forwarding rules** each time Coturn starts and " +"stops. This, however, means that **you will need to ensure these ports " +"are open** in your firewall yourself." +msgstr "" + +#: ../../../CHANGELOG.md:1275 +msgid "" +"Thanks to us [tightening Coturn security](#backward-compatibility-" +"tightening-coturn-security-can-lead-to-connectivity-issues), running " +"Coturn with host-networking should be safe and not expose neither other " +"services running on the host, nor other services running on the local " +"network." +msgstr "" + +#: ../../../CHANGELOG.md:1277 +msgid "" +"(Backward Compatibility) Tightening Coturn security can lead to " +"connectivity issues" +msgstr "" + +#: ../../../CHANGELOG.md:1279 +msgid "" +"**TLDR**: users who run and access their Matrix server on a private " +"network (likely a small minority of users) may experience connectivity " +"issues with our new default Coturn blocklists. They may need to override " +"`matrix_coturn_denied_peer_ips` and remove some IP ranges from it." +msgstr "" + +#: ../../../CHANGELOG.md:1281 +msgid "" +"Inspired by [this security " +"article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-" +"access-control-protection/), we've decided to make use of Coturn's " +"`denied-peer-ip` functionality to prevent relaying network traffic to " +"certain private IP subnets. This ensures that your Coturn server won't " +"accidentally try to forward traffic to certain services running on your " +"local networks. We run Coturn in a container and in a private container " +"network by default, which should prevent such access anyway, but having " +"additional block layers in place is better." +msgstr "" + +#: ../../../CHANGELOG.md:1283 +msgid "" +"If you access your Matrix server from a local network and need Coturn to " +"relay to private IP addresses, you may observe that relaying is now " +"blocked due to our new default `denied-peer-ip` lists (specified in " +"`matrix_coturn_denied_peer_ips`). If you experience such connectivity " +"problems, consider overriding this setting in your `vars.yml` file and " +"removing certain networks from it." +msgstr "" + +#: ../../../CHANGELOG.md:1285 +msgid "" +"We've also added `no-multicast-peers` to the default Coturn " +"configuration, but we don't expect this to cause trouble for most people." +msgstr "" + +#: ../../../CHANGELOG.md:1288 +msgid "2023-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:1290 +msgid "The matrix-prometheus-node-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1292 +msgid "" +"**TLDR**: the `matrix-prometheus-node-exporter` role is now included from" +" another repository. Some variables have been renamed. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1294 +msgid "" +"The `matrix-prometheus-node-exporter` role (which configures [Prometheus " +"node exporter](https://github.com/prometheus/node_exporter)) has been " +"extracted from the playbook and now lives in its own repository at " +"https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-" +"node-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1296 +msgid "" +"It's still part of the playbook, but is now installed via `ansible-" +"galaxy` (by running `just roles` / `make roles`). Some variables have " +"been renamed (`matrix_prometheus_node_exporter_` -> " +"`prometheus_node_exporter_`, etc.). The playbook will report all " +"variables that you need to rename to get upgraded. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1298 +msgid "" +"A new `matrix-prometheus-services-proxy-connect` role was added to the " +"playbook to help integrate the new `prometheus_node_exporter` role with " +"our own services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1303 +msgid "2023-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:1305 +msgid "Support for running commands via just" +msgstr "" + +#: ../../../CHANGELOG.md:1307 +msgid "" +"We've previously used [make](https://www.gnu.org/software/make/) for " +"easily running some playbook commands (e.g. `make roles` which triggers " +"`ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still " +"around and you can still run these commands." +msgstr "" + +#: ../../../CHANGELOG.md:1309 +msgid "" +"In addition, we've added support for running commands via " +"[just](https://github.com/casey/just) - a more modern command-runner " +"alternative to `make`. Instead of `make roles`, you can now run `just " +"roles` to accomplish the same." +msgstr "" + +#: ../../../CHANGELOG.md:1311 +msgid "" +"Our [justfile](justfile) already defines some additional helpful " +"**shortcut** commands that weren't part of our `Makefile`. Here are some " +"examples:" +msgstr "" + +#: ../../../CHANGELOG.md:1313 +msgid "" +"`just install-all` to trigger the much longer `ansible-playbook -i " +"inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-" +"created,start` command" +msgstr "" + +#: ../../../CHANGELOG.md:1314 +msgid "" +"`just install-all --ask-vault-pass` - commands also support additional " +"arguments (`--ask-vault-pass` will be appended to the above installation " +"command)" +msgstr "" + +#: ../../../CHANGELOG.md:1315 +msgid "" +"`just run-tags install-mautrix-slack,start` - to run specific playbook " +"tags" +msgstr "" + +#: ../../../CHANGELOG.md:1316 +msgid "`just start-all` - (re-)starts all services" +msgstr "" + +#: ../../../CHANGELOG.md:1317 +msgid "`just stop-group postgres` - to stop only the Postgres service" +msgstr "" + +#: ../../../CHANGELOG.md:1318 +msgid "" +"`just register-user alice secret-password yes` - registers an `alice` " +"user with the `secret-password` password and admin access (admin = `yes`)" +msgstr "" + +#: ../../../CHANGELOG.md:1320 +msgid "Additional helpful commands and shortcuts may be defined in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1322 +msgid "" +"This is all completely optional. If you find it difficult to [install " +"`just`](https://github.com/casey/just#installation) or don't find any of " +"this convenient, feel free to run all commands manually." +msgstr "" + +#: ../../../CHANGELOG.md:1325 +msgid "2023-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:1327 +msgid "mautrix-slack support" +msgstr "" + +#: ../../../CHANGELOG.md:1329 +msgid "" +"Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the " +"playbook now supports bridging to [Slack](https://slack.com/) via the " +"[mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting " +"up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-" +"slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1331 +msgid "" +"**Note**: this is a new Slack bridge. The playbook still retains Slack " +"bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-" +"appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-" +"bridge-mx-puppet-slack.md). You're free to use the bridge that serves you" +" better, or even all three of them (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1334 +msgid "2023-01-10" +msgstr "" + +#: ../../../CHANGELOG.md:1336 +msgid "ChatGPT support" +msgstr "" + +#: ../../../CHANGELOG.md:1338 +msgid "" +"Thanks to [@bertybuttface](https://github.com/bertybuttface), the " +"playbook can now help you set up [matrix-chatgpt-" +"bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through " +"which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) " +"model." +msgstr "" + +#: ../../../CHANGELOG.md:1340 +msgid "" +"See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-" +"chatgpt.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1343 +msgid "2022-11-30" +msgstr "" + +#: ../../../CHANGELOG.md:1345 +msgid "" +"matrix-postgres-backup has been replaced by the ansible-role-postgres-" +"backup external role" +msgstr "" + +#: ../../../CHANGELOG.md:1347 +msgid "" +"Just like we've [replaced Postgres with an external role](#matrix-" +"postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-" +"role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an" +" external role - " +"[com.devture.ansible.role.postgres_backup](https://github.com/mother-of-" +"all-self-hosting/ansible-role-postgres_backup)." +msgstr "" + +#: ../../../CHANGELOG.md:1349 +msgid "" +"You'll need to rename your `matrix_postgres_backup`-prefixed variables " +"such that they use a `postgres_backup` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1352 +msgid "2022-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:1354 +msgid "" +"matrix-postgres has been replaced by the ansible-role-postgres external " +"role" +msgstr "" + +#: ../../../CHANGELOG.md:1356 +msgid "" +"**TLDR**: the tasks that install the integrated Postgres server now live " +"in an external role - [ansible-role-postgres](https://github.com/mother-" +"of-all-self-hosting/ansible-role-postgres). You'll need to run `make " +"roles` to install it, and to also rename your `matrix_postgres`-prefixed " +"variables to use a `devture_postgres` prefix (e.g. " +"`matrix_postgres_connection_password` -> `postgres_connection_password`)." +" All your data will still be there! Some scripts have moved " +"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." +msgstr "" + +#: ../../../CHANGELOG.md:1358 +msgid "" +"The `matrix-postgres` role that has been part of the playbook for a long " +"time has been replaced with the [ansible-role-" +"postgres](https://github.com/mother-of-all-self-hosting/ansible-role-" +"postgres) role. This was done as part of our work to [use external roles " +"for some things](#the-playbook-now-uses-external-roles-for-some-things) " +"for better code re-use and maintainability." +msgstr "" + +#: ../../../CHANGELOG.md:1360 +msgid "" +"The new role is an upgraded version of the old `matrix-postgres` role " +"with these notable differences:" +msgstr "" + +#: ../../../CHANGELOG.md:1362 +msgid "" +"it uses different names for its variables (`matrix_postgres` -> " +"`devture_postgres`)" +msgstr "" + +#: ../../../CHANGELOG.md:1363 +msgid "" +"when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-" +"postgresql), it will vacuum all your databases, not just the Synapse one" +msgstr "" + +#: ../../../CHANGELOG.md:1365 +msgid "" +"You'll need to run `make roles` to install the new role. You would also " +"need to rename your `matrix_postgres`-prefixed variables to use a " +"`devture_postgres` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1367 +msgid "" +"Note: the systemd service still remains the same - `matrix-" +"postgres.service`. Your data will still be in `/matrix/postgres`, etc. " +"Postgres-related scripts will be moved to `/matrix/postgres/bin` " +"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, " +"etc). Also see [The playbook no longer installs scripts in /usr/local/bin" +"](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." +msgstr "" + +#: ../../../CHANGELOG.md:1369 +msgid "The playbook no longer installs scripts to /usr/local/bin" +msgstr "" + +#: ../../../CHANGELOG.md:1371 +msgid "The locations of various scripts installed by the playbook have changed." +msgstr "" + +#: ../../../CHANGELOG.md:1373 +msgid "" +"The playbook no longer contaminates your `/usr/local/bin` directory. All " +"scripts installed by the playbook now live in `bin/` directories under " +"`/matrix`. Some examples are below:" +msgstr "" + +#: ../../../CHANGELOG.md:1375 +msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`" +msgstr "" + +#: ../../../CHANGELOG.md:1376 +msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1377 +msgid "" +"`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> " +"`/matrix/ssl/bin/lets-encrypt-certificates-renew`" +msgstr "" + +#: ../../../CHANGELOG.md:1378 +msgid "" +"`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin" +"/register-user`" +msgstr "" + +#: ../../../CHANGELOG.md:1381 +msgid "2022-11-25" +msgstr "" + +#: ../../../CHANGELOG.md:1383 +msgid "2x-5x performance improvements in playbook runtime" +msgstr "" + +#: ../../../CHANGELOG.md:1385 +msgid "" +"**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and " +"various other tags). It also has new `--tags=install-*` tags (like " +"`--tags=install-all`), which skip uninstallation tasks and bring an " +"additional 2.5x speedup. In total, the playbook can maintain your server " +"5 times faster." +msgstr "" + +#: ../../../CHANGELOG.md:1387 +msgid "" +"Our [etke.cc managed Matrix hosting service](https://etke.cc) runs " +"maintenance against hundreds of servers, so the playbook being fast means" +" a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible)" +" (which is an extension of this one) is growing to support more and more " +"services (besides just Matrix), so the Matrix playbook being leaner " +"prevents runtimes from becoming too slow and improves the customer " +"experience." +msgstr "" + +#: ../../../CHANGELOG.md:1389 +msgid "" +"Even when running `ansible-playbook` manually (as most of us here do), " +"it's beneficial not to waste time and CPU resources." +msgstr "" + +#: ../../../CHANGELOG.md:1391 +msgid "" +"Recently, a few large optimizations have been done to this playbook and " +"its external roles (see [The playbook now uses external roles for some " +"things](#the-playbook-now-uses-external-roles-for-some-things) and don't " +"forget to run `make roles`):" +msgstr "" + +#: ../../../CHANGELOG.md:1393 +msgid "" +"Replacing Ansible `import_tasks` calls with `include_tasks`, which " +"decreased runtime in half. Using `import_tasks` is slower and causes " +"Ansible to go through and skip way too many tasks (tasks which could have" +" been skipped altogether by not having Ansible include them in the first " +"place). On an experimental VM, **deployment time was decreased from ~530 " +"seconds to ~250 seconds**." +msgstr "" + +#: ../../../CHANGELOG.md:1395 +msgid "" +"Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, " +"e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible " +"tasks pertaining to installation, while skipping uninstallation tasks. In" +" most cases, people are maintaining the same setup or they're *adding* " +"new components. Removing components is rare. Running thousands of " +"uninstallation tasks each time is wasteful. On an experimental VM, " +"**deployment time was decreased from ~250 seconds (`--tags=setup-all`) to" +" ~100 seconds (`--tags=install-all`)**." +msgstr "" + +#: ../../../CHANGELOG.md:1397 +msgid "" +"You can still use `--tags=setup-all`. In fact, that's the best way to " +"ensure your server is reconciled with the `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1399 +msgid "" +"If you know you haven't uninstalled any services since the last time you " +"ran the playbook, you could run `--tags=install-all` instead and benefit " +"from quicker runtimes. It should be noted that a service may become " +"\"eligible for uninstallation\" even if your `vars.yml` file remains the " +"same. In rare cases, we toggle services from being auto-installed to " +"being optional, like we did on the 17th of March 2022 when we made [ma1sd" +" not get installed by default](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-" +"identity-server-no-longer-installed-by-default). In such rare cases, " +"you'd also need to run `--tags=setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:1402 +msgid "2022-11-22" +msgstr "" + +#: ../../../CHANGELOG.md:1404 +msgid "Automatic `matrix_architecture` determination" +msgstr "" + +#: ../../../CHANGELOG.md:1406 +msgid "" +"From now on, the playbook automatically determines your server's " +"architecture and sets the `matrix_architecture` variable accordingly. You" +" no longer need to set this variable manually in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1408 +msgid "Docker and the Docker SDK for Python are now installed via external roles" +msgstr "" + +#: ../../../CHANGELOG.md:1412 +msgid "" +"Docker will now be installed on the server via the " +"[geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) " +"Ansible role. If you'd like to manage the Docker installation yourself, " +"you can disable the playbook's installation of Docker by setting " +"`matrix_playbook_docker_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1414 +msgid "" +"The Docker SDK for Python (named `docker-python`, `python-docker`, etc. " +"on the different platforms) is now also installed by another role " +"([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python))." +" To disable this role and install the necessary tools yourself, use " +"`devture_docker_sdk_for_python_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1416 +msgid "" +"If you're hitting issues with Docker installation or Docker SDK for " +"Python installation, consider reporting bugs or contributing to these " +"other projects." +msgstr "" + +#: ../../../CHANGELOG.md:1418 +msgid "" +"These additional roles are downloaded into the playbook directory (to " +"`roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an " +"easy shortcut for invoking the `ansible-galaxy` command to download these" +" roles." +msgstr "" + +#: ../../../CHANGELOG.md:1421 +msgid "2022-11-20" +msgstr "" + +#: ../../../CHANGELOG.md:1423 +msgid "" +"(Backward Compatibility Break) Changing how reverse-proxying to Synapse " +"works - now via a `matrix-synapse-reverse-proxy-companion` service" +msgstr "" + +#: ../../../CHANGELOG.md:1425 +msgid "" +"**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx " +"service, which helps with reverse-proxying to Synapse and its various " +"worker processes (if workers are enabled), so that `matrix-nginx-proxy` " +"can be relieved of this role. `matrix-nginx-proxy` still remains as the " +"public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-" +"reverse-proxy-companion` is just one more reverse-proxy thrown into the " +"mix for convenience. People with a more custom reverse-proxying " +"configuration may be affected - see [Webserver configuration](#webserver-" +"configuration) below." +msgstr "" + +#: ../../../CHANGELOG.md:1427 +msgid "Background" +msgstr "" + +#: ../../../CHANGELOG.md:1429 +msgid "" +"Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. " +"When Synapse is running in worker mode, the reverse-proxying " +"configuration is more complicated (different requests need to go to " +"different Synapse worker processes). `matrix-nginx-proxy` had " +"configuration for sending each URL endpoint to the correct Synapse worker" +" responsible for handling it. However, sometimes people like to disable " +"`matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own" +" webserver, instead of this playbook's nginx proxy](docs/configuring-" +"playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1431 +msgid "" +"Because `matrix-nginx-proxy` was so central to request forwarding, when " +"it was disabled and Synapse was running with workers enabled, there was " +"nothing which could forward requests to the correct place anymore.. which" +" caused [problems such as this one affecting " +"Dimension](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/2090)." +msgstr "" + +#: ../../../CHANGELOG.md:1433 +msgid "Solution" +msgstr "" + +#: ../../../CHANGELOG.md:1435 +msgid "" +"From now on, `matrix-nginx-proxy` is relieved of its function of reverse-" +"proxying to Synapse and its various worker processes. This role is now " +"handled by the new `matrix-synapse-reverse-proxy-companion` nginx service" +" and works even if `matrix-nginx-proxy` is disabled. The purpose of the " +"new `matrix-synapse-reverse-proxy-companion` service is to:" +msgstr "" + +#: ../../../CHANGELOG.md:1437 +msgid "" +"serve as a companion to Synapse and know how to reverse-proxy to Synapse " +"correctly (no matter if workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1439 +msgid "" +"provide a unified container address for reaching Synapse (no matter if " +"workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1440 +msgid "" +"`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server " +"API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1441 +msgid "" +"`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server " +"(Federation) API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1443 +msgid "" +"simplify `matrix-nginx-proxy` configuration - it now only needs to send " +"requests to `matrix-synapse-reverse-proxy-companion` or `matrix-" +"dendrite`, etc., without having to worry about workers" +msgstr "" + +#: ../../../CHANGELOG.md:1445 +msgid "" +"allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is " +"disabled" +msgstr "" + +#: ../../../CHANGELOG.md:1447 +msgid "" +"`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-" +"proxy in the playbook. All traffic goes through it before reaching any of" +" the services. It's just that now the Synapse traffic is routed through " +"`matrix-synapse-reverse-proxy-companion` like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1449 +msgid "" +"(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> " +"(`matrix-synapse` or some Synapse worker))." +msgstr "" + +#: ../../../CHANGELOG.md:1451 +msgid "" +"Various services (like Dimension, etc.) still talk to Synapse via " +"`matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) " +"preferentially. They only talk to Synapse via the reverse-proxy companion" +" (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-" +"nginx-proxy` is disabled. Services should not be talking to Synapse (e.g." +" `https://matrix-synapse:8008` directly anymore), because when workers " +"are enabled, that's the Synapse `master` process and may not be serving " +"all URL endpoints needed by the service." +msgstr "" + +#: ../../../CHANGELOG.md:1453 +msgid "Webserver configuration" +msgstr "" + +#: ../../../CHANGELOG.md:1455 +msgid "" +"if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`," +" which is the default for the playbook), you don't need to do anything" +msgstr "" + +#: ../../../CHANGELOG.md:1457 +msgid "" +"if you're using your own `nginx` webserver running on the server, you " +"shouldn't be affected. The `/matrix/nginx/conf.d` configuration and " +"exposed ports that you're relying on will automatically be updated in a " +"way that should work" +msgstr "" + +#: ../../../CHANGELOG.md:1459 +msgid "" +"if you're using another local webserver (e.g. Apache, etc.) and haven't " +"changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't " +"be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and" +" `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed " +"on `127.0.0.1` by default - just not by the `matrix-synapse` container " +"from now on, but by the `matrix-synapse-reverse-proxy-companion` " +"container instead" +msgstr "" + +#: ../../../CHANGELOG.md:1461 +msgid "" +"if you've been exposing `matrix-synapse` ports " +"(`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, " +"you should consider exposing `matrix-synapse-reverse-proxy-companion` " +"ports instead" +msgstr "" + +#: ../../../CHANGELOG.md:1463 +msgid "" +"if you're running Traefik and reverse-proxying directly to the `matrix-" +"synapse` container, you should start reverse-proxying to the `matrix-" +"synapse-reverse-proxy-companion` container instead. See [our updated " +"Traefik example configuration](docs/configuring-playbook-own-webserver.md" +"#sample-configuration-for-running-behind-traefik-20). Note: we now " +"recommend calling the federation entry point `federation` (instead of " +"`synapse`) and reverse-proxying the federation traffic via `matrix-nginx-" +"proxy`, instead of sending it directly to Synapse (or `matrix-synapse-" +"reverse-proxy-companion`). This makes the configuration simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1466 +msgid "2022-11-05" +msgstr "" + +#: ../../../CHANGELOG.md:1468 +msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad" +msgstr "" + +#: ../../../CHANGELOG.md:1470 +msgid "" +"Until now, [Etherpad](https://etherpad.org/) (which [the playbook could " +"install for you](docs/configuring-playbook-etherpad.md)) required the " +"[Dimension integration manager](docs/configuring-playbook-dimension.md) " +"to also be installed, because Etherpad was hosted on the Dimension domain" +" (at `dimension.example.com/etherpad`)." +msgstr "" + +#: ../../../CHANGELOG.md:1472 +msgid "" +"From now on, Etherpad can be installed in `standalone` mode on " +"`etherpad.example.com` and used even without Dimension. This is much more" +" versatile, so the playbook now defaults to this new mode " +"(`etherpad_mode: standalone`)." +msgstr "" + +#: ../../../CHANGELOG.md:1474 +msgid "If you've already got both Etherpad and Dimension in use you could:" +msgstr "" + +#: ../../../CHANGELOG.md:1476 +msgid "" +"**either** keep hosting Etherpad under the Dimension domain by adding " +"`etherpad_mode: dimension` to your `vars.yml` file. All your existing " +"room widgets will continue working at the same URLs and no other changes " +"will be necessary." +msgstr "" + +#: ../../../CHANGELOG.md:1478 +msgid "" +"**or**, you could change to hosting Etherpad separately on " +"`etherpad.example.com`. You will need to [configure a DNS record](docs" +"/configuring-dns.md) for this new domain. You will also need to " +"reconfigure Dimension to use the new pad URLs " +"(`https://etherpad.example.com/…`) going forward (refer to our " +"[configuring Etherpad documentation](docs/configuring-playbook-" +"etherpad.md)). All your existing room widgets (which still use " +"`https://dimension.example.com/etherpad/…`) will break as Etherpad is not" +" hosted there anymore. You will need to re-add them or to consider not " +"using `standalone` mode" +msgstr "" + +#: ../../../CHANGELOG.md:1481 +msgid "2022-11-04" +msgstr "" + +#: ../../../CHANGELOG.md:1483 +msgid "The playbook now uses external roles for some things" +msgstr "" + +#: ../../../CHANGELOG.md:1485 +msgid "" +"**TLDR**: when updating the playbook and before running it, you'll need " +"to run `make roles` to make [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"download dependency roles (see the [`requirements.yml` " +"file](requirements.yml)) to the `roles/galaxy` directory. Without this, " +"the playbook won't work." +msgstr "" + +#: ../../../CHANGELOG.md:1487 +msgid "" +"We're in the process of trimming the playbook and making it reuse Ansible" +" roles." +msgstr "" + +#: ../../../CHANGELOG.md:1489 +msgid "Starting now, the playbook is composed of 2 types of Ansible roles:" +msgstr "" + +#: ../../../CHANGELOG.md:1491 +msgid "those that live within the playbook itself (`roles/custom/*`)" +msgstr "" + +#: ../../../CHANGELOG.md:1493 +msgid "" +"those downloaded from other sources (using [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"to `roles/galaxy`, based on the [`requirements.yml` " +"file](requirements.yml)). These roles are maintained by us or by other " +"people from the Ansible community." +msgstr "" + +#: ../../../CHANGELOG.md:1495 +msgid "" +"We're doing this for greater code-reuse (across Ansible playbooks, " +"including our own related playbooks [gitea-docker-ansible-" +"deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and " +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. " +"Until now, certain features were copy-pasted across playbooks or were " +"maintained separately in each one, with improvements often falling " +"behind. We've also tended to do too much by ourselves - installing Docker" +" on the server from our `matrix-base` role, etc. - something that we'd " +"rather not do anymore by switching to the " +"[geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." +msgstr "" + +#: ../../../CHANGELOG.md:1497 +msgid "" +"Some variable names will change during the transition to having more and " +"more external (galaxy) roles. There's a new " +"`custom/matrix_playbook_migration` role added to the playbook which will " +"tell you about these changes each time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1499 +msgid "" +"**From now on**, every time you update the playbook (well, every time the" +" `requirements.yml` file changes), it's best to run `make roles` to " +"update the roles downloaded from other sources. `make roles` is a " +"shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed" +" by the [`make`](https://www.gnu.org/software/make/) utility) which " +"ultimately runs [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"to download Ansible roles. If you don't have `make`, you can also " +"manually run the commands seen in the `Makefile`." +msgstr "" + +#: ../../../CHANGELOG.md:1502 +msgid "2022-10-14" +msgstr "" + +#: ../../../CHANGELOG.md:1504 +msgid "synapse-s3-storage-provider support" +msgstr "" + +#: ../../../CHANGELOG.md:1506 +msgid "" +"**`synapse-s3-storage-provider` support is very new and still relatively " +"untested. Using it may cause data loss.**" +msgstr "" + +#: ../../../CHANGELOG.md:1508 +msgid "" +"You can now store your Synapse media repository files on Amazon S3 (or " +"another S3-compatible object store) using [synapse-s3-storage-" +"provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a " +"media provider for Synapse (Python module), which should work faster and " +"more reliably than our previous [Goofys](docs/configuring-" +"playbook-s3-goofys.md) implementation (Goofys will continue to work)." +msgstr "" + +#: ../../../CHANGELOG.md:1510 +msgid "" +"This is not just for initial installations. Users with existing files " +"(stored in the local filesystem) can also migrate their files to " +"`synapse-s3-storage-provider`." +msgstr "" + +#: ../../../CHANGELOG.md:1512 +msgid "" +"To get started, see our [Storing Synapse media files on Amazon S3 with " +"synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3" +"-storage-provider.md) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1514 +msgid "Synapse container image customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1516 +msgid "" +"We now support customizing the Synapse container image by adding " +"additional build steps to its " +"[`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." +msgstr "" + +#: ../../../CHANGELOG.md:1518 +msgid "" +"Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-" +"support) is actually built on this. When `s3-storage-provider` is " +"enabled, we automatically add additional build steps to install its " +"Python module into the Synapse image." +msgstr "" + +#: ../../../CHANGELOG.md:1520 +msgid "" +"Besides this kind of auto-added build steps (for components supported by " +"the playbook), we also let you inject your own custom build steps using " +"configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1531 +msgid "" +"People who have needed to customize Synapse previously had to fork the " +"git repository, make their changes to the `Dockerfile` there, point the " +"playbook to the new repository " +"(`matrix_synapse_container_image_self_build_repo`) and enable self-" +"building from scratch (`matrix_synapse_container_image_self_build: " +"true`). This is harder and slower." +msgstr "" + +#: ../../../CHANGELOG.md:1533 +msgid "" +"With the new Synapse-customization feature in the playbook, we use the " +"original upstream (pre-built, if available) Synapse image and only build " +"on top of it, right on the Matrix server. This is much faster than " +"building all of Synapse from scratch." +msgstr "" + +#: ../../../CHANGELOG.md:1536 +msgid "2022-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:1538 +msgid "matrix-ldap-registration-proxy support" +msgstr "" + +#: ../../../CHANGELOG.md:1540 +msgid "" +"Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), " +"we now support installing [matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" - a proxy which handles Matrix registration requests and forwards them " +"to LDAP." +msgstr "" + +#: ../../../CHANGELOG.md:1542 +msgid "" +"See our [Setting up matrix-ldap-registration-proxy](docs/configuring-" +"playbook-matrix-ldap-registration-proxy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1545 +msgid "2022-09-15" +msgstr "" + +#: ../../../CHANGELOG.md:1547 +msgid "" +"(Potential Backward Compatibility Break) Major improvements to Synapse " +"workers" +msgstr "" + +#: ../../../CHANGELOG.md:1549 +msgid "" +"People who are interested in running a Synapse worker setup should know " +"that **our Synapse worker implementation is much more powerful now**:" +msgstr "" + +#: ../../../CHANGELOG.md:1551 +msgid "we've added support for [Stream writers](#stream-writers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1552 +msgid "" +"we've added support for [multiple federation sender workers](#multiple-" +"federation-sender-workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1553 +msgid "" +"we've added support for [multiple pusher workers](#multiple-pusher-" +"workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1554 +msgid "" +"we've added support for [running background tasks on a worker" +"](#background-tasks-can-run-on-a-worker)" +msgstr "" + +#: ../../../CHANGELOG.md:1555 +msgid "" +"we've restored support for [`appservice` workers](#appservice-worker-" +"support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1556 +msgid "" +"we've restored support for [`user_dir` workers](#user-directory-worker-" +"support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1557 +msgid "" +"we've made it possible to [reliably use more than 1 `media_repository` " +"worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" +msgstr "" + +#: ../../../CHANGELOG.md:1558 +msgid "" +"see the [Potential Backward Incompatibilities after these Synapse worker " +"changes](#potential-backward-incompatibilities-after-these-synapse-" +"worker-changes)" +msgstr "" + +#: ../../../CHANGELOG.md:1560 +msgid "Stream writers support" +msgstr "" + +#: ../../../CHANGELOG.md:1562 +msgid "" +"From now on, the playbook lets you easily set up various [stream writer " +"workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-" +"writers) which can handle different streams (`events` stream; `typing` " +"URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, " +"`receipts` URL endpoints, `presence` URL endpoints). All of this work was" +" previously handled by the main Synapse process, but can now be offloaded" +" to stream writer worker processes." +msgstr "" + +#: ../../../CHANGELOG.md:1564 +msgid "" +"If you're using `matrix_synapse_workers_preset: one-of-each`, you'll " +"automatically get 6 additional workers (one for each of the above stream " +"types). Our `little-federation-helper` preset (meant to be quite minimal " +"and focusing in improved federation performance) does not include stream " +"writer workers." +msgstr "" + +#: ../../../CHANGELOG.md:1566 +msgid "" +"If you'd like to customize the number of workers we also make that " +"possible using these variables:" +msgstr "" + +#: ../../../CHANGELOG.md:1579 +msgid "Multiple federation sender workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1581 +msgid "" +"Until now, we only supported a single `federation_sender` worker " +"(`matrix_synapse_workers_federation_sender_workers_count` could either be" +" `0` or `1`). From now on, you can have as many as you want to help with " +"your federation traffic." +msgstr "" + +#: ../../../CHANGELOG.md:1583 +msgid "Multiple pusher workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1585 +msgid "" +"Until now, we only supported a single `pusher` worker " +"(`matrix_synapse_workers_pusher_workers_count` could either be `0` or " +"`1`). From now on, you can have as many as you want to help with pushing " +"notifications out." +msgstr "" + +#: ../../../CHANGELOG.md:1587 +msgid "Background tasks can run on a worker" +msgstr "" + +#: ../../../CHANGELOG.md:1589 +msgid "" +"From now on, you can put [background task processing on a worker](https" +"://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." +msgstr "" + +#: ../../../CHANGELOG.md:1591 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`background` worker automatically. You can also control the `background` " +"workers count with `matrix_synapse_workers_background_workers_count`. " +"Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1593 +msgid "Appservice worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1595 +msgid "" +"We previously had an `appservice` worker type, which [Synapse deprecated " +"in v1.59.0](https://github.com/element-" +"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" +"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" +" did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1597 +msgid "" +"The new way to implement such workers is by using a `generic_worker` and " +"dedicating it to the task of talking to Application Services. From now " +"on, we have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1599 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`appservice` worker automatically. You can also control the `appservice` " +"workers count with `matrix_synapse_workers_appservice_workers_count`. " +"Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1601 +msgid "User Directory worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1603 +msgid "" +"We previously had a `user_dir` worker type, which [Synapse deprecated in " +"v1.59.0](https://github.com/element-" +"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" +"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" +" did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1605 +msgid "" +"The new way to implement such workers is by using a `generic_worker` and " +"dedicating it to the task of serving the user directory. From now on, we " +"have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1607 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`user_dir` worker automatically. You can also control the `user_dir` " +"workers count with `matrix_synapse_workers_user_dir_workers_count`. Only" +" `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1609 +msgid "Using more than 1 media repository worker is now more reliable" +msgstr "" + +#: ../../../CHANGELOG.md:1611 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, we only launch one " +"`media_repository` worker." +msgstr "" + +#: ../../../CHANGELOG.md:1613 +msgid "" +"If you've been configuring " +"`matrix_synapse_workers_media_repository_workers_count` manually, you may" +" have increased that to more workers. When multiple media repository " +"workers are in use, background tasks related to the media repository must" +" always be configured to run on a single `media_repository` worker via " +"`media_instance_running_background_jobs`. Until now, we weren't doing " +"this correctly, but we now are." +msgstr "" + +#: ../../../CHANGELOG.md:1615 +msgid "Potential Backward Incompatibilities after these Synapse worker changes" +msgstr "" + +#: ../../../CHANGELOG.md:1617 +msgid "Below we'll discuss **potential backward incompatibilities**." +msgstr "" + +#: ../../../CHANGELOG.md:1619 +msgid "" +"**Worker names** (container names, systemd services, worker configuration" +" files) **have changed**. Workers are now labeled sequentially (e.g. " +"`matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-" +"generic-0`). The playbook will handle these changes automatically." +msgstr "" + +#: ../../../CHANGELOG.md:1621 +msgid "" +"Due to increased worker types support above, people who use " +"`matrix_synapse_workers_preset: one-of-each` should be aware that with " +"these changes, **the playbook will deploy 9 additional workers** (6 " +"stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background " +"task worker). This **may increase RAM/CPU usage**, etc. If you find your " +"server struggling, consider disabling some workers with the appropriate " +"`matrix_synapse_workers_*_workers_count` variables." +msgstr "" + +#: ../../../CHANGELOG.md:1623 +msgid "" +"**Metric endpoints have also changed** " +"(`/metrics/synapse/worker/generic_worker-18111` -> " +"`/metrics/synapse/worker/generic-worker-0`). If you're [collecting " +"metrics to an external Prometheus server](docs/configuring-playbook-" +"prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-" +"server), consider revisiting our [Collecting Synapse worker metrics to an" +" external Prometheus server](docs/configuring-playbook-prometheus-" +"grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-" +"server) docs and updating your Prometheus configuration. **If you're " +"collecting metrics to the integrated Prometheus server** (not enabled by " +"default), **your Prometheus configuration will be updated " +"automatically**. Old data (from before this change) may stick around " +"though." +msgstr "" + +#: ../../../CHANGELOG.md:1625 +msgid "" +"**the format of `matrix_synapse_workers_enabled_list` has changed**. You " +"were never advised to use this variable for directly creating workers (we" +" advise people to control workers using `matrix_synapse_workers_preset` " +"or by tweaking `matrix_synapse_workers_*_workers_count` variables only), " +"but some people may have started using the " +"`matrix_synapse_workers_enabled_list` variable to gain more control over " +"workers. If you're one of them, you'll need to adjust its value. See " +"`roles/custom/matrix-synapse/defaults/main.yml` for more information on " +"the new format. The playbook will also do basic validation and complain " +"if you got something wrong." +msgstr "" + +#: ../../../CHANGELOG.md:1628 +msgid "2022-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:1630 +msgid "Cactus Comments support" +msgstr "" + +#: ../../../CHANGELOG.md:1632 +msgid "" +"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " +"the playbook can now set up [Cactus Comments](https://cactus.chat) - " +"federated comment system for the web based on Matrix." +msgstr "" + +#: ../../../CHANGELOG.md:1634 +msgid "" +"See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-" +"comments.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1637 +msgid "2022-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:1639 +msgid "Postmoogle email bridge support" +msgstr "" + +#: ../../../CHANGELOG.md:1641 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up the new " +"[Postmoogle](https://github.com/etkecc/postmoogle) email bridge. " +"Postmoogle is like the [email2matrix " +"bridge](https://github.com/devture/email2matrix) (also [already supported" +" by the playbook](docs/configuring-playbook-email2matrix.md)), but more " +"capable and with the intention to soon support *sending* emails, not just" +" receiving." +msgstr "" + +#: ../../../CHANGELOG.md:1643 +msgid "" +"See our [Setting up Postmoogle email bridging](docs/configuring-playbook-" +"bridge-postmoogle.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1646 +msgid "2022-08-10" +msgstr "" + +#: ../../../CHANGELOG.md:1648 +msgid "mautrix-whatsapp default configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:1650 +msgid "" +"In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/2012), we've made some changes to the default " +"configuration used by the `mautrix-whatsapp` bridge." +msgstr "" + +#: ../../../CHANGELOG.md:1652 +msgid "" +"If you're using this bridge, you should look into this PR and see if the " +"new configuration suits you. If not, you can always change individual " +"preferences in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1654 +msgid "" +"Most notably, spaces support has been enabled by default. The bridge will" +" now group rooms into a Matrix space. **If you've already bridged to " +"Whatsapp** prior to this update, you will need to send `!wa sync space` " +"to the bridge bot to make it create the space and put your existing rooms" +" into it." +msgstr "" + +#: ../../../CHANGELOG.md:1657 +msgid "2022-08-09" +msgstr "" + +#: ../../../CHANGELOG.md:1659 +msgid "Conduit support" +msgstr "" + +#: ../../../CHANGELOG.md:1661 +msgid "" +"Thanks to [Charles Wright](https://github.com/cvwright), we now have " +"optional experimental [Conduit](https://conduit.rs) homeserver support " +"for new installations. This comes as a follow-up to the playbook getting " +"[Dendrite support](#dendrite-support) earlier this year." +msgstr "" + +#: ../../../CHANGELOG.md:1663 +msgid "" +"Existing Synapse or Dendrite installations do **not** need to be updated." +" **Synapse is still the default homeserver implementation** installed by " +"the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1665 +msgid "" +"To try out Conduit, we recommend that you **use a new server** and the " +"following `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1671 +msgid "" +"**The homeserver implementation of an existing server cannot be changed**" +" (e.g. from Synapse or Dendrite to Conduit) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1674 +msgid "2022-07-29" +msgstr "" + +#: ../../../CHANGELOG.md:1676 +msgid "mautrix-discord support" +msgstr "" + +#: ../../../CHANGELOG.md:1678 +msgid "" +"Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the " +"playbook now supports bridging to [Discord](https://discordapp.com/) via " +"the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our " +"[Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-" +"mautrix-discord.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1680 +msgid "" +"**Note**: this is a new Discord bridge. The playbook still retains " +"Discord bridging via [matrix-appservice-discord](docs/configuring-" +"playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs" +"/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use " +"the bridge that serves you better, or even all three of them (for " +"different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1683 +msgid "2022-07-27" +msgstr "" + +#: ../../../CHANGELOG.md:1685 +msgid "matrix-appservice-kakaotalk support" +msgstr "" + +#: ../../../CHANGELOG.md:1687 +msgid "" +"The playbook now supports bridging to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +" via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk) - a bridge based on [node-" +"kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and " +"some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks" +" to [hnarjis](https://github.com/hnarjis) for helping us add support for " +"this!" +msgstr "" + +#: ../../../CHANGELOG.md:1689 +msgid "" +"See our [Setting up Appservice Kakaotalk bridging](docs/configuring-" +"playbook-bridge-appservice-kakaotalk.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1692 +msgid "2022-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:1694 +msgid "maubot support" +msgstr "" + +#: ../../../CHANGELOG.md:1696 +msgid "" +"Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for " +"starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr " +"(@moan0s)](https://github.com/moan0s) for finishing up (in [PR " +"#1894](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/1894)), the playbook can now help you set up " +"[maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot " +"system." +msgstr "" + +#: ../../../CHANGELOG.md:1698 +msgid "" +"See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) " +"documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1701 +msgid "2022-07-14" +msgstr "" + +#: ../../../CHANGELOG.md:1703 +msgid "mx-puppet-skype removal" +msgstr "" + +#: ../../../CHANGELOG.md:1705 +msgid "" +"The playbook no longer includes the [mx-puppet-" +"skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it " +"has been broken and unmaintained for a long time. Users that have " +"`matrix_mx_puppet_skype_enabled` in their configuration files will " +"encounter an error when running the playbook until they remove references" +" to this bridge from their configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1707 +msgid "" +"To completely clean up your server from `mx-puppet-skype`'s presence on " +"it:" +msgstr "" + +#: ../../../CHANGELOG.md:1709 +msgid "" +"ensure your Ansible configuration (`vars.yml` file) no longer contains " +"`matrix_mx_puppet_skype_*` references" +msgstr "" + +#: ../../../CHANGELOG.md:1710 +msgid "" +"stop and disable the systemd service (run `systemctl disable --now " +"matrix-mx-puppet-skype` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1711 +msgid "" +"delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-" +"skype.service` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1712 +msgid "" +"delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on" +" the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1713 +msgid "" +"drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-" +"postgres-cli` on the server, and execute the `DROP DATABASE " +"matrix_mx_puppet_skype;` query there)" +msgstr "" + +#: ../../../CHANGELOG.md:1715 +msgid "" +"If you still need bridging to [Skype](https://www.skype.com/), consider " +"switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-" +"bridge) instead. See [Setting up Go Skype Bridge bridging](docs" +"/configuring-playbook-bridge-go-skype-bridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1717 +msgid "" +"If you think this is a mistake and `mx-puppet-skype` works for you (or " +"you get it to work somehow), let us know and we may reconsider this " +"removal." +msgstr "" + +#: ../../../CHANGELOG.md:1719 +msgid "signald (0.19.0+) upgrade requires data migration" +msgstr "" + +#: ../../../CHANGELOG.md:1721 +msgid "" +"In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) " +"(used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." +msgstr "" + +#: ../../../CHANGELOG.md:1723 +msgid "" +"Back in the [`v0.19.0` released of " +"signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md)" +" (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-" +"data` command had been added that migrates avatars, group images, " +"attachments, etc., into the database (those were previously stored in the" +" filesystem)." +msgstr "" + +#: ../../../CHANGELOG.md:1725 +msgid "" +"If you've been using the mautrix-signal bridge for a while, you may have " +"files stored in the local filesystem, which will need to be upgraded." +msgstr "" + +#: ../../../CHANGELOG.md:1727 +msgid "" +"We attempt to do this data migration automatically every time Signald " +"starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` " +"systemd unit definition." +msgstr "" + +#: ../../../CHANGELOG.md:1729 +msgid "" +"Keep an eye on your Signal bridge and let us know (in our [support " +"room](README.md#support) or in [Pull Request " +"#1921](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/1921)) if you experience any trouble!" +msgstr "" + +#: ../../../CHANGELOG.md:1732 +msgid "2022-07-05" +msgstr "" + +#: ../../../CHANGELOG.md:1734 +msgid "Ntfy push notifications support" +msgstr "" + +#: ../../../CHANGELOG.md:1736 +msgid "" +"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " +"playbook can now install a [ntfy](https://ntfy.sh/) push notifications " +"server for you." +msgstr "" + +#: ../../../CHANGELOG.md:1738 +msgid "" +"See our [Setting up the ntfy push notifications server](docs/configuring-" +"playbook-ntfy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1741 +msgid "2022-06-23" +msgstr "" + +#: ../../../CHANGELOG.md:1743 +msgid "(Potential Backward Compatibility Break) Changes around metrics collection" +msgstr "" + +#: ../../../CHANGELOG.md:1745 +msgid "" +"**TLDR**: we've made extensive **changes to metrics exposure/collection, " +"which concern people using an external Prometheus server**. If you don't " +"know what that is, you don't need to read below." +msgstr "" + +#: ../../../CHANGELOG.md:1747 +msgid "" +"**Why do major changes to metrics**? Because various services were " +"exposing metrics in different, hacky, ways. Synapse was exposing metrics " +"at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the " +"`matrix.example.com`. The Hookshot role was **repurposing** the Granana " +"web UI domain (`stats.example.com`) for exposing its metrics on " +"`stats.example.com/hookshot/metrics`, while protecting these routes using" +" Basic Authentication **normally used for Synapse** " +"(`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were " +"advising for more `stats.example.com` usage in manual ways. Each role was" +" doing things differently and mixing variables from other roles. Each " +"metrics endpoint was ending up in a different place, protected by who " +"knows what Basic Authentication credentials (if protected at all)." +msgstr "" + +#: ../../../CHANGELOG.md:1749 +msgid "" +"**The solution**: a completely revamped way to expose metrics to an " +"external Prometheus server. We are **introducing new " +"`https://matrix.example.com/metrics/*` endpoints**, where various " +"services *can* expose their metrics, for collection by external " +"Prometheus servers. To enable the `/metrics/*` endpoints, use " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a " +"way to protect access using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)." +" See the `matrix-nginx-proxy` role or our [Collecting metrics to an " +"external Prometheus server](docs/configuring-playbook-prometheus-" +"grafana.md#collecting-metrics-to-an-external-prometheus-server) " +"documentation for additional variables around " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`." +msgstr "" + +#: ../../../CHANGELOG.md:1751 +msgid "" +"**If you are using the [Hookshot bridge](docs/configuring-playbook-" +"bridge-hookshot.md)**, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1752 +msgid "**Metrics may not be enabled by default anymore**:" +msgstr "" + +#: ../../../CHANGELOG.md:1753 +msgid "" +"If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot " +"metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: " +"true`). These metrics will be collected from the local (in-container) " +"Prometheus over the container network." +msgstr "" + +#: ../../../CHANGELOG.md:1754 +msgid "" +"**If Prometheus is not enabled** (you are either not using Prometheus or " +"are using an external one), **Hookshot metrics will not be enabled by " +"default anymore**. Feel free to enable them by setting " +"`matrix_hookshot_metrics_enabled: true`. Also, see below." +msgstr "" + +#: ../../../CHANGELOG.md:1755 +msgid "" +"When metrics are meant to be **consumed by an external Prometheus " +"server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to " +"`true`, so that metrics would be exposed (proxied) \"publicly\" on " +"`https://matrix.example.com/metrics/hookshot`. To make use of this, " +"you'll also need to enable the new `https://matrix.example.com/metrics/*`" +" endpoints mentioned above, using " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our " +"[Collecting metrics to an external Prometheus server](docs/configuring-" +"playbook-prometheus-grafana.md#collecting-metrics-to-an-external-" +"prometheus-server) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1756 +msgid "" +"**We've changed the URL we're exposing Hookshot metrics at** for external" +" Prometheus servers. Until now, you were advised to consume Hookshot " +"metrics from `https://stats.example.com/hookshot/metrics` (working in " +"conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now " +"on, **this no longer works**. As described above, you need to start " +"consuming metrics from `https://matrix.example.com/metrics/hookshot`." +msgstr "" + +#: ../../../CHANGELOG.md:1758 +msgid "" +"**If you're using node-exporter** " +"(`matrix_prometheus_node_exporter_enabled: true`) and would like to " +"collect its metrics from an external Prometheus server, see " +"`matrix_prometheus_node_exporter_metrics_proxying_enabled` described in " +"our [Collecting metrics to an external Prometheus server](docs" +"/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" +"external-prometheus-server) documentation. You will be able to collect " +"its metrics from `https://matrix.example.com/metrics/node-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1760 +msgid "" +"**If you're using [postgres-exporter](docs/configuring-playbook-" +"prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) " +"and would like to collect its metrics from an external Prometheus server," +" see " +"`matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled`" +" described in our [Collecting metrics to an external Prometheus " +"server](docs/configuring-playbook-prometheus-grafana.md#collecting-" +"metrics-to-an-external-prometheus-server) documentation. You will be able" +" to collect its metrics from `https://matrix.example.com/metrics" +"/postgres-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1762 +msgid "" +"**If you're using Synapse** and would like to collect its metrics from an" +" external Prometheus server, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1764 +msgid "" +"Exposing metrics is now done using " +"`matrix_synapse_metrics_proxying_enabled`, not " +"`matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to " +"enable metrics using `matrix_synapse_metrics_enabled: true` before " +"exposing them." +msgstr "" + +#: ../../../CHANGELOG.md:1765 +msgid "" +"Protecting metrics endpoints using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" +" is now done in another way. See our [Collecting metrics to an external " +"Prometheus server](docs/configuring-playbook-prometheus-grafana.md" +"#collecting-metrics-to-an-external-prometheus-server) documentation" +msgstr "" + +#: ../../../CHANGELOG.md:1766 +msgid "" +"If Synapse metrics are exposed, they will be made available at " +"`https://matrix.example.com/metrics/synapse/main-process` or " +"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers" +" are enabled), not at `https://matrix.example.com/_synapse/metrics` and " +"`https://matrix.example.com/_synapse-worker-…/metrics`" +msgstr "" + +#: ../../../CHANGELOG.md:1767 +msgid "" +"The playbook still generates an `external_prometheus.yml.example` sample " +"file for scraping Synapse from Prometheus as described in [Collecting " +"Synapse worker metrics to an external Prometheus server](docs" +"/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-" +"metrics-to-an-external-prometheus-server), but it's now saved under " +"`/matrix/synapse` (not `/matrix`)." +msgstr "" + +#: ../../../CHANGELOG.md:1769 +msgid "" +"**If you where already using a external Prometheus server** before this " +"change, and you gave a hashed version of the password as a variable, the " +"playbook will now take care of hashing the password for you. Thus, you " +"need to provide the non-hashed version now." +msgstr "" + +#: ../../../CHANGELOG.md:1771 +msgid "2022-06-13" +msgstr "" + +#: ../../../CHANGELOG.md:1773 +msgid "go-skype-bridge bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1775 +msgid "" +"Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can" +" now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-" +"bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." +msgstr "" + +#: ../../../CHANGELOG.md:1777 +msgid "" +"See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-" +"bridge-go-skype-bridge.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1779 +msgid "" +"The playbook has supported [mx-puppet-skype](https://github.com/Sorunome" +"/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype " +"bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since " +"[2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." +msgstr "" + +#: ../../../CHANGELOG.md:1782 +msgid "2022-06-09" +msgstr "" + +#: ../../../CHANGELOG.md:1784 +msgid "Running Ansible in a container can now happen on the Matrix server itself" +msgstr "" + +#: ../../../CHANGELOG.md:1786 +msgid "" +"If you're tired of being on an old and problematic Ansible version, you " +"can now run [run Ansible in a container on the Matrix server " +"itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-" +"server-itself)." +msgstr "" + +#: ../../../CHANGELOG.md:1789 +msgid "2022-05-31" +msgstr "" + +#: ../../../CHANGELOG.md:1791 +msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:1793 +msgid "" +"Synapse v1.60 will try to add a new unique index to `state_group_edges` " +"upon startup and could fail if your database is corrupted." +msgstr "" + +#: ../../../CHANGELOG.md:1795 +msgid "" +"We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade " +"notes](https://github.com/element-" +"hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-" +"state_group_edges-could-fail-if-your-database-is-corrupted) mention it, " +"so we're giving you a heads up here in case you're unlucky." +msgstr "" + +#: ../../../CHANGELOG.md:1797 +msgid "" +"**If Synapse fails to start** after your next playbook run, you'll need " +"to:" +msgstr "" + +#: ../../../CHANGELOG.md:1799 +msgid "SSH into the Matrix server" +msgstr "" + +#: ../../../CHANGELOG.md:1800 +msgid "launch `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1801 +msgid "switch to the `synapse` database: `\\c synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:1802 +msgid "run the following SQL query:" +msgstr "" + +#: ../../../CHANGELOG.md:1821 +msgid "" +"You could then restart services: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=start`" +msgstr "" + +#: ../../../CHANGELOG.md:1824 +msgid "2022-04-25" +msgstr "" + +#: ../../../CHANGELOG.md:1826 +msgid "Buscarron bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1828 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron " +"bot](https://github.com/etkecc/buscarron). It's a bot you can use to send" +" any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../CHANGELOG.md:1830 +msgid "" +"See our [Setting up Buscarron](docs/configuring-playbook-bot-" +"buscarron.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1833 +msgid "2022-04-21" +msgstr "" + +#: ../../../CHANGELOG.md:1835 +msgid "matrix-registration-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1837 +msgid "" +"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " +"the playbook can now help you set up [matrix-registration-" +"bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is " +"used to create and manage registration tokens for a Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1839 +msgid "" +"See our [Setting up matrix-registration-bot](docs/configuring-playbook-" +"bot-matrix-registration-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1842 +msgid "2022-04-19" +msgstr "" + +#: ../../../CHANGELOG.md:1844 +msgid "BorgBackup support" +msgstr "" + +#: ../../../CHANGELOG.md:1846 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up " +"[Borg](https://www.borgbackup.org/) backups with " +"[borgmatic](https://torsion.org/borgmatic/) of your Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1848 +msgid "" +"See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md)" +" documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1850 +msgid "" +"(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers " +"may require manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1852 +msgid "" +"If you're running a worker setup for Synapse " +"(`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade " +"notes](https://github.com/element-" +"hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-" +"for-application-services) say that you may need to take special care when" +" upgrading:" +msgstr "" + +#: ../../../CHANGELOG.md:1854 +msgid "" +"Synapse v1.57.0 includes a change to the way transaction IDs are managed " +"for application services. If your deployment uses a dedicated worker for " +"application service traffic, **it must be stopped** when the database is " +"upgraded (which normally happens when the main process is upgraded), to " +"ensure the change is made safely without any risk of reusing transaction " +"IDs." +msgstr "" + +#: ../../../CHANGELOG.md:1856 +msgid "" +"If you're not running an `appservice` worker " +"(`matrix_synapse_workers_preset: little-federation-helper` or " +"`matrix_synapse_workers_appservice_workers_count: 0`), you are probably " +"safe to upgrade as per normal, without taking any special care." +msgstr "" + +#: ../../../CHANGELOG.md:1858 +msgid "" +"If you are running a setup with an `appservice` worker, or otherwise want" +" to be on the safe side, we recommend the following upgrade path:" +msgstr "" + +#: ../../../CHANGELOG.md:1860 +msgid "Pull the latest playbook changes" +msgstr "" + +#: ../../../CHANGELOG.md:1861 +msgid "" +"Stop all services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:1862 +msgid "" +"Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:1863 +msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1864 +msgid "" +"Start the main Synapse process (`systemctl start matrix-synapse` on the " +"server)" +msgstr "" + +#: ../../../CHANGELOG.md:1865 +msgid "" +"Wait a while so that Synapse can start and complete the database " +"migrations. You can use `journalctl -fu matrix-synapse` on the server to " +"get a clue. Waiting a few minutes should also be enough." +msgstr "" + +#: ../../../CHANGELOG.md:1866 +msgid "" +"It should now be safe to start all other services. `ansible-playbook -i " +"inventory/hosts setup.yml --tags=start` will do it for you" +msgstr "" + +#: ../../../CHANGELOG.md:1869 +msgid "2022-04-14" +msgstr "" + +#: ../../../CHANGELOG.md:1871 +msgid "" +"(Compatibility Break) Changes to `docker-src` permissions necessitating " +"manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1873 +msgid "" +"Users who build container images from source will need to manually " +"correct file permissions of some directories on the server." +msgstr "" + +#: ../../../CHANGELOG.md:1875 +msgid "" +"When self-building, the playbook used to `git clone` repositories (into " +"`/matrix/SERVICE/docker-src`) using the `root` user, but now uses " +"`matrix` instead to work around [the following issue with git " +"2.35.2](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1749)." +msgstr "" + +#: ../../../CHANGELOG.md:1877 +msgid "" +"If you're on a non-`amd64` architecture (that is, you're overriding " +"`matrix_architecture` in your `vars.yml` file) or you have enabled self-" +"building for some service (e.g. `matrix_*_self_build: true`), you're " +"certainly building some container images from source and have `docker-" +"src` directories with mixed permissions lying around in various " +"`/matrix/SERVICE` directories." +msgstr "" + +#: ../../../CHANGELOG.md:1879 +msgid "" +"The playbook *could* correct these permissions automatically, but that " +"requires additional Ansible tasks in some ~45 different places - " +"something that takes considerable effort. So we ask users observing " +"errors related to `docker-src` directories to correct the problem " +"manually by **running this command on the Matrix server** (which deletes " +"all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name " +"'docker-src' | xargs rm -rf`" +msgstr "" + +#: ../../../CHANGELOG.md:1882 +msgid "2022-03-17" +msgstr "" + +#: ../../../CHANGELOG.md:1884 +msgid "(Compatibility Break) ma1sd identity server no longer installed by default" +msgstr "" + +#: ../../../CHANGELOG.md:1886 +msgid "" +"The playbook no longer installs the " +"[ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The " +"next time you run the playbook, ma1sd will be uninstalled from your " +"server, unless you explicitly enable the ma1sd service (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:1888 +msgid "" +"The main reason we used to install ma1sd by default in the past was to " +"prevent Element clients from talking to the `matrix.org` / `vector.im` " +"identity servers, by forcing it to talk to our own self-hosted (but " +"otherwise useless) identity server instead, thus preventing contact list " +"leaks." +msgstr "" + +#: ../../../CHANGELOG.md:1890 +msgid "" +"Since Element clients no longer default to using a public identity server" +" if another one is not provided, we can stop installing ma1sd." +msgstr "" + +#: ../../../CHANGELOG.md:1892 +msgid "" +"If you need to install the ma1sd identity server for some reason, you can" +" explicitly enable it by adding this to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:1899 +msgid "2022-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1901 +msgid "matrix_encryption_disabler support" +msgstr "" + +#: ../../../CHANGELOG.md:1903 +msgid "" +"We now support installing the " +"[matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler)" +" Synapse module, which lets you prevent End-to-End-Encryption from being " +"enabled by users on your homeserver. The popular opinion is that this is " +"dangerous and shouldn't be done, but there are valid use cases for " +"disabling encryption discussed [here](https://github.com/matrix-" +"org/synapse/issues/4401)." +msgstr "" + +#: ../../../CHANGELOG.md:1905 +msgid "" +"To enable this module (and prevent encryption from being used on your " +"homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to" +" your configuration. This module provides further customization. Check " +"its other configuration settings (and defaults) in `roles/custom/matrix-" +"synapse/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:1908 +msgid "2022-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:1910 +msgid "matrix-hookshot bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1912 +msgid "" +"Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can" +" now install the [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) bridge for bridging Matrix to multiple project management " +"services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-" +"hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to " +"get started." +msgstr "" + +#: ../../../CHANGELOG.md:1915 +msgid "2022-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:1917 +msgid "ARM support for matrix-corporal" +msgstr "" + +#: ../../../CHANGELOG.md:1919 +msgid "" +"[matrix-corporal](https://github.com/devture/matrix-corporal) (as of " +"version `2.2.3`) is now published to Docker Hub (see [devture/matrix-" +"corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-" +"arch container image with support for all these platforms: `linux/amd64`," +" `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to " +"self-building matrix-corporal on these ARM architectures." +msgstr "" + +#: ../../../CHANGELOG.md:1922 +msgid "2022-01-07" +msgstr "" + +#: ../../../CHANGELOG.md:1924 +msgid "Dendrite support" +msgstr "" + +#: ../../../CHANGELOG.md:1926 +msgid "" +"**TLDR**: We now have optional experimental [Dendrite](https://github.com" +"/matrix-org/dendrite) homeserver support for new installations. " +"**Existing (Synapse) installations need to be updated**, because some " +"internals changed. See [Adapting the configuration for existing Synapse " +"installations](#adapting-the-configuration-for-existing-synapse-" +"installations)." +msgstr "" + +#: ../../../CHANGELOG.md:1928 +msgid "" +"[Jip J. Dekker](https://github.com/Dekker1) did the [initial " +"work](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/818) of adding [Dendrite](https://github.com/matrix-" +"org/dendrite) support to the playbook back in January 2021. Lots of work " +"(and time) later, Dendrite support is finally ready for testing." +msgstr "" + +#: ../../../CHANGELOG.md:1930 +msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" +msgstr "" + +#: ../../../CHANGELOG.md:1932 +msgid "" +"The playbook was previously quite [Synapse](https://github.com/element-" +"hq/synapse)-centric, but can now accommodate multiple homeserver " +"implementations. Only one homeserver implementation can be active " +"(installed) at a given time." +msgstr "" + +#: ../../../CHANGELOG.md:1934 +msgid "" +"**Synapse is still the default homeserver implementation** installed by " +"the playbook. A new variable (`matrix_homeserver_implementation`) " +"controls which server implementation is enabled (`synapse` or `dendrite` " +"at the given moment)." +msgstr "" + +#: ../../../CHANGELOG.md:1936 +msgid "Adapting the configuration for existing Synapse installations" +msgstr "" + +#: ../../../CHANGELOG.md:1938 +msgid "" +"Because the playbook is not so Synapse-centric anymore, a small " +"configuration change is necessary for existing installations to bring " +"them up to date." +msgstr "" + +#: ../../../CHANGELOG.md:1940 +msgid "" +"The `vars.yml` file for **existing installations will need to be " +"updated** by adding this **additional configuration**:" +msgstr "" + +#: ../../../CHANGELOG.md:1952 +msgid "Trying out Dendrite" +msgstr "" + +#: ../../../CHANGELOG.md:1954 +msgid "" +"Finally, **to try out Dendrite**, we recommend that you **use a new " +"server** and the following addition to your `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1960 +msgid "" +"**The homeserver implementation of an existing server cannot be changed**" +" (e.g. from Synapse to Dendrite) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1962 +msgid "" +"We're excited to gain support for other homeserver implementations, like " +"[Conduit](https://conduit.rs/), etc!" +msgstr "" + +#: ../../../CHANGELOG.md:1964 +msgid "Honoroit bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1966 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now help you set up " +"[Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." +msgstr "" + +#: ../../../CHANGELOG.md:1968 +msgid "" +"See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) " +"documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1971 +msgid "2022-01-06" +msgstr "" + +#: ../../../CHANGELOG.md:1973 +msgid "Cinny support" +msgstr "" + +#: ../../../CHANGELOG.md:1975 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook now supports " +"[Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix " +"client." +msgstr "" + +#: ../../../CHANGELOG.md:1977 +msgid "" +"By default, we still install Element Web. Still, people who'd like to try" +" Cinny out can now install it via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1979 +msgid "" +"Additional details are available in [Setting up Cinny](docs/configuring-" +"playbook-client-cinny.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1982 +msgid "2021-12-22" +msgstr "" + +#: ../../../CHANGELOG.md:1984 +msgid "Twitter bridging support via mautrix-twitter" +msgstr "" + +#: ../../../CHANGELOG.md:1986 +msgid "" +"Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas " +"Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-" +"twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging" +" to [Twitter](https://twitter.com/) can now also happen with [mautrix-" +"twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1989 +msgid "2021-12-14" +msgstr "" + +#: ../../../CHANGELOG.md:1991 +msgid "" +"(Security) Users of the Signal bridge may wish to upgrade it to work " +"around log4j vulnerability" +msgstr "" + +#: ../../../CHANGELOG.md:1993 +msgid "" +"Recently, a security vulnerability affecting the Java logging package " +"`log4j` [has been discovered](https://www.huntress.com/blog/rapid-" +"response-critical-rce-vulnerability-is-affecting-java). Software that " +"uses this Java package is potentially vulnerable." +msgstr "" + +#: ../../../CHANGELOG.md:1995 +msgid "" +"One such piece of software that is part of the playbook is the [mautrix-" +"signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), " +"which [has been patched already](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/1452). If you're running this bridge, you may " +"wish to [upgrade](./docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1998 +msgid "2021-11-11" +msgstr "" + +#: ../../../CHANGELOG.md:2000 +msgid "Dropped support for Postgres v9.6" +msgstr "" + +#: ../../../CHANGELOG.md:2002 +msgid "" +"Postgres v9.6 reached its end of life today, so the playbook will refuse " +"to run for you if you're still on that version." +msgstr "" + +#: ../../../CHANGELOG.md:2004 +msgid "" +"Synapse still supports v9.6 (for now), but we're retiring support for it " +"early, to avoid having to maintain support for so many Postgres versions." +" Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs" +"/maintenance-postgres.md#upgrading-postgresql) via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2007 +msgid "2021-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:2009 +msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2011 +msgid "" +"The mautrix-hangouts bridge is no longer receiving updates upstream and " +"is likely to stop working in the future. We still retain support for this" +" bridge in the playbook, but you're encouraged to switch away from it." +msgstr "" + +#: ../../../CHANGELOG.md:2013 +msgid "" +"There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat)" +" bridge that you can [install using the playbook](docs/configuring-" +"playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will " +"not be migrated**, however. You need to start fresh with the new bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2016 +msgid "2021-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:2018 +msgid "LinkedIn bridging support via beeper-linkedin" +msgstr "" + +#: ../../../CHANGELOG.md:2020 +msgid "" +"Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook " +"can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin)" +" bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." +msgstr "" + +#: ../../../CHANGELOG.md:2022 +msgid "" +"This brings the total number of bridges supported by the playbook up to " +"20. See all supported bridges [here](docs/configuring-playbook.md" +"#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2024 +msgid "" +"To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn" +" bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2027 +msgid "2021-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:2029 +msgid "Sygnal upgraded - ARM support and no longer requires a database" +msgstr "" + +#: ../../../CHANGELOG.md:2031 +msgid "" +"The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been " +"upgraded from `v0.9.0` to `v0.10.1`." +msgstr "" + +#: ../../../CHANGELOG.md:2033 +msgid "" +"This is an optional component for the playbook, so most of our users " +"wouldn't care about this announcement." +msgstr "" + +#: ../../../CHANGELOG.md:2035 +msgid "" +"Since this feels like a relatively big (and untested, as of yet) Sygnal " +"change, we're putting up this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2037 +msgid "" +"The new version is also available for the ARM architecture. It also no " +"longer requires a database anymore. If you need to downgrade to the " +"previous version, changing `matrix_sygnal_version` or " +"`matrix_sygnal_docker_image` will not be enough, as we've removed the " +"`database` configuration completely. You'd need to switch to an earlier " +"playbook commit." +msgstr "" + +#: ../../../CHANGELOG.md:2040 +msgid "2021-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:2042 +msgid "Hydrogen support" +msgstr "" + +#: ../../../CHANGELOG.md:2044 +msgid "" +"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " +"now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a " +"new lightweight Matrix client with legacy and mobile browser support." +msgstr "" + +#: ../../../CHANGELOG.md:2046 +msgid "" +"By default, we still install Element Web, as Hydrogen is still not fully-" +"featured. Still, people who'd like to try Hydrogen out can now install it" +" via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2048 +msgid "" +"Additional details are available in [Setting up Hydrogen](docs" +"/configuring-playbook-client-hydrogen.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2051 +msgid "2021-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2053 +msgid "Heisenbridge support" +msgstr "" + +#: ../../../CHANGELOG.md:2055 +msgid "" +"Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now " +"supports bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet " +"another bridge (besides matrix-appservice-irc), called " +"[Heisenbridge](https://github.com/hifi/heisenbridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2057 +msgid "" +"Additional details are available in [Setting up Heisenbridge bouncer-" +"style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2060 +msgid "2021-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:2062 +msgid "Disabling TLSv1 and TLSv1.1 for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:2064 +msgid "" +"To improve security, we've [removed TLSv1 and TLSv1.1 " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/999) from our default " +"[Coturn](https://github.com/coturn/coturn) configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2066 +msgid "" +"If you need to support old clients, you can re-enable both (or whichever " +"one you need) with the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:2074 +msgid "2021-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2076 +msgid "Automated local Postgres backup support" +msgstr "" + +#: ../../../CHANGELOG.md:2078 +msgid "" +"Thanks to [foxcris](https://github.com/foxcris), the playbook can now " +"make automated local Postgres backups on a fixed schedule using [docker-" +"postgres-backup-local](https://github.com/prodrigestivill/docker-" +"postgres-backup-local)." +msgstr "" + +#: ../../../CHANGELOG.md:2080 +msgid "" +"Additional details are available in [Setting up postgres backup](docs" +"/configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2083 +msgid "2021-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2085 +msgid "Mjolnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:2087 +msgid "" +"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " +"can now install and configure the [Mjolnir](https://github.com/matrix-" +"org/mjolnir) moderation tool (bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2089 +msgid "" +"Additional details are available in [Setting up Mjolnir](docs" +"/configuring-playbook-bot-mjolnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2092 +msgid "2021-03-20" +msgstr "" + +#: ../../../CHANGELOG.md:2094 +msgid "Sygnal push gateway support" +msgstr "" + +#: ../../../CHANGELOG.md:2096 +msgid "" +"The playbook can now install the [Sygnal](https://github.com/matrix-" +"org/sygnal) push gateway for you." +msgstr "" + +#: ../../../CHANGELOG.md:2098 +msgid "" +"This is only useful to people who develop/build their own Matrix client " +"applications." +msgstr "" + +#: ../../../CHANGELOG.md:2100 +msgid "" +"Additional details are available in our [Setting up the Sygnal push " +"gateway](docs/configuring-playbook-sygnal.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2103 +msgid "2021-03-16" +msgstr "" + +#: ../../../CHANGELOG.md:2105 +msgid "Go-NEB support" +msgstr "" + +#: ../../../CHANGELOG.md:2107 +msgid "" +"Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install" +" and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." +msgstr "" + +#: ../../../CHANGELOG.md:2109 +msgid "" +"Additional details are available in [Setting up Go-NEB](docs/configuring-" +"playbook-bot-go-neb.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2112 +msgid "2021-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:2114 +msgid "GroupMe bridging support via mx-puppet-groupme" +msgstr "" + +#: ../../../CHANGELOG.md:2116 +msgid "" +"Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can " +"now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-" +"puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." +msgstr "" + +#: ../../../CHANGELOG.md:2118 +msgid "" +"This brings the total number of bridges supported by the playbook up to " +"18. See all supported bridges [here](docs/configuring-playbook.md" +"#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2120 +msgid "" +"To get started, follow our [Setting up MX Puppet GroupMe](docs" +"/configuring-playbook-bridge-mx-puppet-groupme.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2122 +msgid "Mautrix Instagram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2124 +msgid "" +"The playbook now supports bridging with " +"[Instagram](https://www.instagram.com/) by installing the [mautrix-" +"instagram](https://github.com/tulir/mautrix-instagram) bridge. This " +"playbook functionality is available thanks to " +"[@MarcProe](https://github.com/MarcProe)." +msgstr "" + +#: ../../../CHANGELOG.md:2126 +msgid "" +"Additional details are available in [Setting up Mautrix Instagram " +"bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2128 +msgid "Synapse workers support" +msgstr "" + +#: ../../../CHANGELOG.md:2130 +msgid "" +"After [lots and lots of work](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/456) (done over many months by [Marcel " +"Partap](https://github.com/eMPee584), [Max " +"Klenk](https://github.com/maxklenk), a few others from the [Technical " +"University of Dresden, Germany](https://tu-dresden.de/) and various other" +" contributors), support for Synapse workers has finally landed." +msgstr "" + +#: ../../../CHANGELOG.md:2132 +msgid "" +"Having support for workers makes the playbook suitable for larger " +"homeserver deployments." +msgstr "" + +#: ../../../CHANGELOG.md:2134 +msgid "" +"Our setup is not yet perfect (we don't support all types of workers; " +"scaling some of them (like `pusher`, `federation_sender`) beyond a single" +" instance is not yet supported). Still, it's a great start and can " +"already power homeservers with thousands of users, like the [Matrix " +"deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed" +" in [Matrix Live S06E09 - TU Dresden on their Matrix " +"deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." +msgstr "" + +#: ../../../CHANGELOG.md:2136 +msgid "" +"By default, workers are disabled and Synapse runs as a single process " +"(homeservers don't necessarily need the complexity and increased memory " +"requirements of running a worker-based setup)." +msgstr "" + +#: ../../../CHANGELOG.md:2138 +msgid "" +"To enable Synapse workers, follow our [Load balancing with workers](docs" +"/configuring-playbook-synapse.md#load-balancing-with-workers) " +"documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2141 +msgid "2021-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:2143 +msgid "" +"(Potential Breaking Change) Monitoring/metrics support using Prometheus " +"and Grafana" +msgstr "" + +#: ../../../CHANGELOG.md:2145 +msgid "" +"Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now " +"install a bunch of tools for monitoring your Matrix server: the " +"[Prometheus](https://prometheus.io) time-series database server, the " +"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" +"exporter/) host metrics exporter, and the [Grafana](https://grafana.com/)" +" web UI." +msgstr "" + +#: ../../../CHANGELOG.md:2147 +msgid "" +"To get get these installed, follow our [Enabling metrics and graphs " +"(Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-" +"prometheus-grafana.md) docs page." +msgstr "" + +#: ../../../CHANGELOG.md:2149 +msgid "" +"This update comes with a **potential breaking change** for people who " +"were already exposing Synapse metrics (for consumption via another " +"Prometheus installation). From now on, `matrix_synapse_metrics_enabled: " +"true` no longer exposes metrics publicly via matrix-nginx-proxy (at " +"`https://matrix.example.com/_synapse/metrics`). To do so, you'd need to " +"explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." +msgstr "" + +#: ../../../CHANGELOG.md:2152 +msgid "2021-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:2154 +msgid "Etherpad support" +msgstr "" + +#: ../../../CHANGELOG.md:2156 +msgid "" +"Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can " +"now install the [Etherpad](https://etherpad.org) realtime collaborative " +"text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video " +"call or integrated as a widget into Matrix chat rooms via the " +"[Dimension](https://dimension.t2bot.io) integration manager." +msgstr "" + +#: ../../../CHANGELOG.md:2158 +msgid "" +"To get it installed, follow [our Etherpad docs page](docs/configuring-" +"playbook-etherpad.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2161 +msgid "2021-01-22" +msgstr "" + +#: ../../../CHANGELOG.md:2163 +msgid "(Breaking Change) Postgres changes that require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:2165 +msgid "" +"We've made a lot of changes to our Postgres setup and some manual action " +"is required (described below). Sorry about the hassle." +msgstr "" + +#: ../../../CHANGELOG.md:2167 +msgid "" +"**TLDR**: people running an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md) don't need to change anything for now. " +"Everyone else (the common/default case) is affected and manual " +"intervention is required." +msgstr "" + +#: ../../../CHANGELOG.md:2169 +msgid "Why?" +msgstr "" + +#: ../../../CHANGELOG.md:2171 +msgid "" +"we had a default Postgres password (`matrix_postgres_connection_password:" +" synapse-password`), which we think is **not ideal for security " +"anymore**. We now ask you to generate/provide a strong password yourself." +" Postgres is normally not exposed outside the container network, making " +"it relatively secure, but still:" +msgstr "" + +#: ../../../CHANGELOG.md:2172 +msgid "" +"by tweaking the configuration, you may end up intentionally or " +"unintentionally exposing your Postgres server to the local network (or " +"even publicly), while still using the default default credentials " +"(`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2173 +msgid "" +"we can't be sure we trust all these services (bridges, etc). Some of them" +" may try to talk to or attack `matrix-postgres` using the default " +"credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2174 +msgid "" +"you may have other containers running on the same Docker network, which " +"may try to talk to or attack `matrix-postgres` using the default " +"credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2175 +msgid "" +"our Postgres usage **was overly-focused on Synapse** (default username of" +" `synapse` and default/main database of `homeserver`). Additional " +"homeserver options are likely coming in the future " +"([Dendrite](https://matrix.org/docs/projects/server/dendrite), " +"[Conduit](https://matrix.org/docs/projects/server/conduit), [The " +"Construct](https://matrix.org/docs/projects/server/construct)), so being " +"too focused on `matrix-synapse` is not great. From now on, Synapse is " +"just another component of this playbook, which happens to have an " +"*additional database* (called `synapse`) on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2176 +msgid "" +"we try to reorganize things a bit, to make the playbook even friendlier " +"to people running an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md). Work on this will proceed in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2178 +msgid "" +"So, this is some **effort to improve security** and to **prepare for a " +"brighter future of having more homeserver options** than just Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:2180 +msgid "What has really changed?" +msgstr "" + +#: ../../../CHANGELOG.md:2182 +msgid "" +"the default superuser Postgres username is now `matrix` (used to be " +"`synapse`)" +msgstr "" + +#: ../../../CHANGELOG.md:2183 +msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" +msgstr "" + +#: ../../../CHANGELOG.md:2184 +msgid "" +"Synapse's database is now `synapse` (used to be `homeserver`). This is " +"now just another \"additional database\" that the playbook manages for " +"you" +msgstr "" + +#: ../../../CHANGELOG.md:2185 +msgid "" +"Synapse's user called `synapse` is just a regular user that can only use " +"the `synapse` database (not a superuser anymore)" +msgstr "" + +#: ../../../CHANGELOG.md:2187 +msgid "What do I do if I'm using the integrated Postgres server (default)?" +msgstr "" + +#: ../../../CHANGELOG.md:2189 +msgid "" +"By default, the playbook runs an integrated Postgres server for you in a " +"container (`matrix-postgres`). Unless you've explicitly configured an " +"[external Postgres server](docs/configuring-playbook-external-" +"postgres.md), these steps are meant for you." +msgstr "" + +#: ../../../CHANGELOG.md:2191 +msgid "" +"To migrate to the new setup, expect a few minutes of downtime, while you " +"follow these steps:" +msgstr "" + +#: ../../../CHANGELOG.md:2193 +msgid "" +"We believe the steps below are safe and you won't encounter any data " +"loss, but consider [making a Postgres backup](docs/maintenance-" +"postgres.md#backing-up-postgresql) anyway. If you've never backed up " +"Postgres, now would be a good time to try it." +msgstr "" + +#: ../../../CHANGELOG.md:2195 +msgid "" +"Generate a strong password to be used for your superuser Postgres user " +"(called `matrix`). You can use `pwgen -s 64 1` to generate it, or some " +"other tool. The **maximum length** for a Postgres password is 100 bytes " +"(characters). Don't go crazy!" +msgstr "" + +#: ../../../CHANGELOG.md:2197 +msgid "" +"Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` " +"file, adding a line like this:" +msgstr "" + +#: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214 +msgid "" +".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the " +"password you generated during step #2." +msgstr "" + +#: ../../../CHANGELOG.md:2204 +msgid "" +"Stop all services: `ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`" +msgstr "" + +#: ../../../CHANGELOG.md:2205 +msgid "Log in to the server via SSH. The next commands will be performed there." +msgstr "" + +#: ../../../CHANGELOG.md:2206 +msgid "Start the Postgres database server: `systemctl start matrix-postgres`" +msgstr "" + +#: ../../../CHANGELOG.md:2207 +msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:2208 +msgid "" +"Execute the following query, while making sure to **change the password " +"inside** (**don't forget the ending `;`**):" +msgstr "" + +#: ../../../CHANGELOG.md:2216 +msgid "" +"Execute the following queries as you see them (no modifications " +"necessary, so you can just **paste them all at once**):" +msgstr "" + +#: ../../../CHANGELOG.md:2234 +msgid "You may need to press *Enter* after pasting the lines above." +msgstr "" + +#: ../../../CHANGELOG.md:2236 +msgid "" +"Re-run the playbook normally: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2238 +msgid "What do I do if I'm using an external Postgres server?" +msgstr "" + +#: ../../../CHANGELOG.md:2240 +msgid "" +"If you've explicitly configured an [external Postgres server](docs" +"/configuring-playbook-external-postgres.md), there are **no changes** " +"that you need to do at this time." +msgstr "" + +#: ../../../CHANGELOG.md:2242 +msgid "" +"The fact that we've renamed Synapse's database from `homeserver` to " +"`synapse` (in our defaults) should not affect you, as you're already " +"explicitly defining `matrix_synapse_database_database` (if you've " +"followed our guide, that is). If you're not explicitly defining this " +"variable, you may wish to do so (`matrix_synapse_database_database: " +"homeserver`), to avoid the new `synapse` default and keep things as they " +"were." +msgstr "" + +#: ../../../CHANGELOG.md:2245 +msgid "2021-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:2247 +msgid "" +"(Breaking Change) The mautrix-facebook bridge now requires a Postgres " +"database" +msgstr "" + +#: ../../../CHANGELOG.md:2249 +msgid "" +"**Update from 2021-11-15**: SQLite support has been re-added to the " +"mautrix-facebook bridge in " +"[v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You " +"can ignore this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2251 +msgid "" +"A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-" +"facebook) bridge has been released. It's a full rewrite of its backend " +"and the bridge now requires Postgres. New versions of the bridge can no " +"longer run on SQLite." +msgstr "" + +#: ../../../CHANGELOG.md:2253 +msgid "" +"**TLDR**: if you're NOT using an [external Postgres server](docs" +"/configuring-playbook-external-postgres.md) and have NOT forcefully kept " +"the bridge on SQLite during [The big move to all-on-Postgres (potentially" +" dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you" +" will be automatically upgraded without manual intervention. All you need" +" to do is send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2255 +msgid "Whether this change requires your intervention depends mostly on:" +msgstr "" + +#: ../../../CHANGELOG.md:2256 +msgid "" +"whether you're using an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md). If yes, then [you need to do something" +"](#upgrade-path-for-people-running-an-external-postgres-server)." +msgstr "" + +#: ../../../CHANGELOG.md:2257 +msgid "" +"or whether you've force-changed the bridge's database engine to SQLite " +"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " +"some time in the past (likely during [The big move to all-on-Postgres " +"(potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-" +"dangerous))." +msgstr "" + +#: ../../../CHANGELOG.md:2259 +msgid "" +"As already mentioned above, you most likely don't need to do anything. If" +" you rerun the playbook and don't get an error, you've been automatically" +" upgraded. Just send a `login` message to the Facebook bridge bot again. " +"Otherwise, read below for a solution." +msgstr "" + +#: ../../../CHANGELOG.md:2261 +msgid "" +"Upgrade path for people NOT running an external Postgres server (default " +"for the playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:2263 +msgid "" +"If you're **not running an external Postgres server**, then this bridge " +"either already works on Postgres for you, or you've intentionally kept it" +" back on SQLite with custom configuration " +"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " +"." +msgstr "" + +#: ../../../CHANGELOG.md:2265 +msgid "" +"Simply remove that custom configuration from your `vars.yml` file (if " +"it's there) and re-run the playbook. It should upgrade you automatically." +" You'll need to send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2267 +msgid "" +"Alternatively, [you can stay on SQLite for a little longer](#staying-on-" +"sqlite-for-a-little-longer-temporary-solution)." +msgstr "" + +#: ../../../CHANGELOG.md:2269 +msgid "Upgrade path for people running an external Postgres server" +msgstr "" + +#: ../../../CHANGELOG.md:2271 +msgid "" +"For people using the internal Postgres server (the default for the " +"playbook):" +msgstr "" + +#: ../../../CHANGELOG.md:2272 +msgid "" +"we automatically create an additional `matrix_mautrix_facebook` Postgres " +"database and credentials to access it" +msgstr "" + +#: ../../../CHANGELOG.md:2273 +msgid "" +"we automatically adjust the bridge's `matrix_mautrix_facebook_database_*`" +" variables to point the bridge to that Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2274 +msgid "" +"we use [pgloader](https://pgloader.io/) to automatically import the " +"existing SQLite data for the bridge into the `matrix_mautrix_facebook` " +"Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2276 +msgid "" +"If you are using an [external Postgres server](docs/configuring-playbook-" +"external-postgres.md), unfortunately we currently can't do any of that " +"for you." +msgstr "" + +#: ../../../CHANGELOG.md:2278 +msgid "You have 3 ways to proceed:" +msgstr "" + +#: ../../../CHANGELOG.md:2280 +msgid "contribute to the playbook to make this possible (difficult)" +msgstr "" + +#: ../../../CHANGELOG.md:2281 +msgid "or, do the migration \"steps\" manually:" +msgstr "" + +#: ../../../CHANGELOG.md:2282 +msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2283 +msgid "create a new `matrix_mautrix_facebook` Postgres database for it" +msgstr "" + +#: ../../../CHANGELOG.md:2284 +msgid "" +"run [pgloader](https://pgloader.io/) manually (we import this bridge's " +"data using default settings and it works well)" +msgstr "" + +#: ../../../CHANGELOG.md:2285 +msgid "" +"define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` " +"file (credentials, etc.) - you can find their defaults in `roles/custom" +"/matrix-mautrix-facebook/defaults/main.yml`" +msgstr "" + +#: ../../../CHANGELOG.md:2286 +msgid "" +"switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: " +"'postgres'` in your `vars.yml` file)" +msgstr "" + +#: ../../../CHANGELOG.md:2287 +msgid "" +"re-run the playbook (`--tags=setup-all,start`) and ensure the bridge " +"works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu " +"matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2288 +msgid "send a `login` message to the Facebook bridge bot again" +msgstr "" + +#: ../../../CHANGELOG.md:2289 +msgid "" +"or, [stay on SQLite for a little longer (temporary solution)](#staying-" +"on-sqlite-for-a-little-longer-temporary-solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2291 +msgid "Staying on SQLite for a little longer (temporary solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2293 +msgid "" +"To keep using this bridge with SQLite for a little longer (**not " +"recommended**), use the following configuration in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:2303 +msgid "" +"If you do this, keep in mind that **you can't run this forever**. This " +"SQLite-supporting bridge version is not getting any updates and will " +"break sooner or later. The playbook will also drop support for SQLite at " +"some point in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2306 +msgid "2021-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:2308 +msgid "matrix-corporal goes 2.0" +msgstr "" + +#: ../../../CHANGELOG.md:2310 +msgid "" +"[matrix-corporal v2 has been released](https://github.com/devture/matrix-" +"corporal/releases/tag/2.0.0) and the playbook also supports it now." +msgstr "" + +#: ../../../CHANGELOG.md:2312 +msgid "No manual intervention is required in the common case." +msgstr "" + +#: ../../../CHANGELOG.md:2314 +msgid "" +"The new [matrix-corporal](https://github.com/devture/matrix-corporal) " +"version is also the first one to support Interactive Authentication. If " +"you wish to enable that (hint: you should), you'll need to set up the " +"[REST auth password provider](docs/configuring-playbook-rest-auth.md). " +"There's more information in [our matrix-corporal docs](docs/configuring-" +"playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2317 +msgid "2021-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2319 +msgid "Moving from cronjobs to systemd timers" +msgstr "" + +#: ../../../CHANGELOG.md:2321 +msgid "" +"We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-" +"nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to " +"systemd timers." +msgstr "" + +#: ../../../CHANGELOG.md:2323 +msgid "" +"The largest benefit of this is that we no longer require you to install a" +" cron daemon, thus simplifying our install procedure." +msgstr "" + +#: ../../../CHANGELOG.md:2325 +msgid "" +"The playbook will migrate you from cronjobs to systemd timers " +"automatically. This is just a heads up." +msgstr "" + +#: ../../../CHANGELOG.md:2328 +msgid "2021-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:2330 +msgid "(Breaking Change) New SSL configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2332 +msgid "" +"SSL configuration (protocols, ciphers) can now be more easily controlled " +"thanks to us making use of configuration presets." +msgstr "" + +#: ../../../CHANGELOG.md:2334 +msgid "" +"We define a few presets (old, intermediate, modern), following the " +"[Mozilla SSL Configuration Generator](https://ssl-" +"config.mozilla.org/#server=nginx)." +msgstr "" + +#: ../../../CHANGELOG.md:2336 +msgid "" +"A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is " +"used (defaults to `\"intermediate\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2338 +msgid "" +"Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to " +"`off` (used to default to `on`). It also add some more ciphers to the " +"list, giving better performance on mobile devices, and removes some weak " +"ciphers. More information in the [documentation](docs/configuring-" +"playbook-nginx.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2340 +msgid "To revert to the old behaviour, set the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:2347 +msgid "" +"Just like before, you can still use your own custom protocols by " +"specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides" +" the values coming from the preset." +msgstr "" + +#: ../../../CHANGELOG.md:2350 +msgid "2021-01-03" +msgstr "" + +#: ../../../CHANGELOG.md:2352 +msgid "Signal bridging support via mautrix-signal" +msgstr "" + +#: ../../../CHANGELOG.md:2354 +msgid "" +"Thanks to [laszabine](https://github.com/laszabine)'s efforts, the " +"playbook now supports bridging to [Signal](https://www.signal.org/) via " +"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See" +" our [Setting up Mautrix Signal bridging](docs/configuring-playbook-" +"bridge-mautrix-signal.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2356 +msgid "" +"If you had installed the mautrix-signal bridge while its Pull Request was" +" still work-in-progress, you can migrate your data to the new and final " +"setup by referring to [this comment](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." +msgstr "" + +#: ../../../CHANGELOG.md:2359 +msgid "2020-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:2361 +msgid "The big move to all-on-Postgres (potentially dangerous)" +msgstr "" + +#: ../../../CHANGELOG.md:2363 +msgid "" +"**TLDR**: all your bridges (and other services) will likely be auto-" +"migrated from SQLite/nedb to Postgres, hopefully without trouble. You can" +" opt-out (see how below), if too worried about breakage." +msgstr "" + +#: ../../../CHANGELOG.md:2365 +msgid "" +"Until now, we've only used Postgres as a database for Synapse. All other " +"services (bridges, bots, etc.) were kept simple and used a file-based " +"database (SQLite or nedb)." +msgstr "" + +#: ../../../CHANGELOG.md:2367 +msgid "" +"Since [this huge pull request](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/740), **all of our services now use Postgres " +"by default**. Thanks to [Johanna Dorothea " +"Reichmann](https://github.com/jdreichmann) for starting the work on it " +"and for providing great input!" +msgstr "" + +#: ../../../CHANGELOG.md:2369 +msgid "Moving all services to Postgres brings a few **benefits** to us:" +msgstr "" + +#: ../../../CHANGELOG.md:2371 +msgid "**improved performance**" +msgstr "" + +#: ../../../CHANGELOG.md:2372 +msgid "" +"**improved compatibility**. Most bridges are deprecating SQLite/nedb " +"support or offer less features when not on Postgres." +msgstr "" + +#: ../../../CHANGELOG.md:2373 +msgid "" +"**easier backups**. It's still some effort to take a proper backup " +"(Postgres dump + various files, keys), but a Postgres dump now takes you " +"much further." +msgstr "" + +#: ../../../CHANGELOG.md:2374 +msgid "" +"we're now **more prepared to introduce other services** that need a " +"Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), " +"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge " +"(existing [pull request](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/686)), etc." +msgstr "" + +#: ../../../CHANGELOG.md:2376 +msgid "Key takeway" +msgstr "" + +#: ../../../CHANGELOG.md:2378 +msgid "" +"existing installations that use an [external " +"Postgres](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/master/docs/configuring-playbook-external-postgres.md) server" +" should be unaffected (they remain on SQLite/nedb for all services, " +"except Synapse)" +msgstr "" + +#: ../../../CHANGELOG.md:2380 +msgid "" +"for existing installations which use our integrated Postgres database " +"server (`matrix-postgres`, which is the default), **we automatically " +"migrate data** from SQLite/nedb to Postgres and **archive the database " +"files** (`something.db` -> `something.db.backup`), so you can restore " +"them if you need to go back (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:2382 +msgid "Opting-out of the Postgres migration" +msgstr "" + +#: ../../../CHANGELOG.md:2384 +msgid "" +"This is a **very large and somewhat untested change** (potentially " +"dangerous), so **if you're not feeling confident/experimental, opt-out** " +"of it for now. Still, it's the new default and what we (and various " +"bridges) will focus on going forward, so don't stick to old ways for too " +"long." +msgstr "" + +#: ../../../CHANGELOG.md:2386 +msgid "" +"You can remain on SQLite/nedb (at least for now) by adding a variable " +"like this to your `vars.yml` file for each service you use: " +"`matrix_COMPONENT_database_engine: sqlite` (e.g. " +"`matrix_mautrix_facebook_database_engine: sqlite`)." +msgstr "" + +#: ../../../CHANGELOG.md:2388 +msgid "" +"Some services (like `appservice-irc` and `appservice-slack`) don't use " +"SQLite, so use `nedb`, instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2390 +msgid "Going back to SQLite/nedb if things went wrong" +msgstr "" + +#: ../../../CHANGELOG.md:2392 +msgid "" +"If you went with the Postgres migration and it went badly for you (some " +"bridge not working as expected or not working at all), do this:" +msgstr "" + +#: ../../../CHANGELOG.md:2394 +msgid "" +"stop all services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:2395 +msgid "" +"SSH into the server and rename the old database files " +"(`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-" +"facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data" +"/mautrix-facebook.db`" +msgstr "" + +#: ../../../CHANGELOG.md:2396 +msgid "" +"switch the affected service back to SQLite (e.g. " +"`matrix_mautrix_facebook_database_engine: sqlite`). Some services (like " +"`appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`," +" instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2397 +msgid "" +"re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-all,start`)" +msgstr "" + +#: ../../../CHANGELOG.md:2398 +msgid "[get in touch](README.md#support) with us" +msgstr "" + +#: ../../../CHANGELOG.md:2400 +msgid "2020-12-11" +msgstr "" + +#: ../../../CHANGELOG.md:2402 +msgid "synapse-janitor support removed" +msgstr "" + +#: ../../../CHANGELOG.md:2404 +msgid "" +"We've removed support for the unmaintained [synapse-" +"janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's " +"been past reports of it corrupting the Synapse database. Since there " +"hasn't been any new development on it and it doesn't seem too useful " +"nowadays, there's no point in including it in the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2406 +msgid "" +"If you need to clean up or compact your database, consider using the " +"Synapse Admin APIs directly. See our [Synapse maintenance](docs" +"/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-" +"postgres.md) documentation pages for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2408 +msgid "Docker 20.10 is here" +msgstr "" + +#: ../../../CHANGELOG.md:2410 +msgid "" +"(No need to do anything special in relation to this. Just something to " +"keep in mind)" +msgstr "" + +#: ../../../CHANGELOG.md:2412 +msgid "" +"Docker 20.10 got released recently and your server will likely get it the" +" next time you update." +msgstr "" + +#: ../../../CHANGELOG.md:2414 +msgid "" +"This is the first major Docker update in a long time and it packs a lot " +"of changes. Some of them introduced some breakage for us initially (see " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should " +"be all good now." +msgstr "" + +#: ../../../CHANGELOG.md:2417 +msgid "2020-12-08" +msgstr "" + +#: ../../../CHANGELOG.md:2419 +msgid "" +"openid APIs exposed by default on the federation port when federation " +"disabled" +msgstr "" + +#: ../../../CHANGELOG.md:2421 +msgid "" +"We've changed some defaults. People running with our default " +"configuration (federation enabled), are not affected at all." +msgstr "" + +#: ../../../CHANGELOG.md:2423 +msgid "" +"If you are running an unfederated server " +"(`matrix_synapse_federation_enabled: false`), this may be of interest to " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:2425 +msgid "" +"When federation is disabled, but ma1sd or Dimension are enabled, we'll " +"now expose the `openid` APIs on the federation port. These APIs are " +"necessary for some ma1sd features to work. If you'd like to prevent this," +" you can: `matrix_synapse_federation_port_openid_resource_required: " +"false`." +msgstr "" + +#: ../../../CHANGELOG.md:2428 +msgid "2020-11-27" +msgstr "" + +#: ../../../CHANGELOG.md:2430 +msgid "Recent Jitsi updates may require configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:2432 +msgid "" +"We've recently [updated from Jitsi build 4857 to build " +"5142](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/719), which brings a lot of configuration changes." +msgstr "" + +#: ../../../CHANGELOG.md:2434 +msgid "**If you use our default Jitsi settings, you won't have to do anything.**" +msgstr "" + +#: ../../../CHANGELOG.md:2436 +msgid "" +"People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md" +"#optional-fine-tune-jitsi) may find that some options got renamed now, " +"others are gone and yet others still need to be defined in another way." +msgstr "" + +#: ../../../CHANGELOG.md:2438 +msgid "" +"The next time you run the playbook [installation](docs/installing.md) " +"command, our validation logic will tell you if you're using some " +"variables like that and will recommend a migration path for each one." +msgstr "" + +#: ../../../CHANGELOG.md:2440 +msgid "" +"Additionally, we've recently disabled transcriptions " +"(`jitsi_enable_transcriptions: false`) and recording " +"(`jitsi_enable_recording: false`) by default. These features did not work" +" anyway, because we don't install the required dependencies for them " +"(Jigasi and Jibri, respectively). If you've been somehow pointing your " +"Jitsi installation to some manually installed Jigasi/Jibri service, you " +"may need to toggle these flags back to enabled to have transcriptions and" +" recordings working." +msgstr "" + +#: ../../../CHANGELOG.md:2443 +msgid "2020-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:2445 ../../../CHANGELOG.md:2453 +msgid "Breaking change matrix-sms-bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2447 +msgid "" +"Because of many problems using gammu as SMS provider, matrix-sms-bridge " +"now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by " +"default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-" +"sms.md] which new vars you need to add." +msgstr "" + +#: ../../../CHANGELOG.md:2449 +msgid "" +"If you are using this playbook to deploy matrix-sms-bridge and still " +"really want to use gammu as SMS provider, we could possibly add support " +"for both android-sms-gateway-server and gammu." +msgstr "" + +#: ../../../CHANGELOG.md:2451 +msgid "2020-11-13" +msgstr "" + +#: ../../../CHANGELOG.md:2455 +msgid "" +"The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-" +"sms-bridge) changed its database from neo4j to h2. You need to sync the " +"bridge at the first start. Note that this only will sync rooms where the " +"@smsbot:yourServer is member. For rooms without @smsbot:yourServer you " +"need to kick and invite the telephone number **or** invite " +"@smsbot:yourServer." +msgstr "" + +#: ../../../CHANGELOG.md:2457 +msgid "" +"Add the following to your `vars.yml` file: " +"`matrix_sms_bridge_container_extra_arguments=['--env " +"SPRING_PROFILES_ACTIVE=initialsync']`" +msgstr "" + +#: ../../../CHANGELOG.md:2458 +msgid "" +"Login to your host shell and remove old systemd file from your host: `rm " +"/etc/systemd/system/matrix-sms-bridge-database.service`" +msgstr "" + +#: ../../../CHANGELOG.md:2459 +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-" +"sms-bridge,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2460 +msgid "" +"Login to your host shell and check the logs with `journalctl -u matrix-" +"sms-bridge` until the sync finished." +msgstr "" + +#: ../../../CHANGELOG.md:2461 +msgid "Remove the var from the first step." +msgstr "" + +#: ../../../CHANGELOG.md:2462 +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-" +"all,start`." +msgstr "" + +#: ../../../CHANGELOG.md:2464 +msgid "2020-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2466 +msgid "Dynamic DNS support" +msgstr "" + +#: ../../../CHANGELOG.md:2468 +msgid "" +"Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook " +"can now manage Dynamic DNS for you using " +"[ddclient](https://ddclient.net/)." +msgstr "" + +#: ../../../CHANGELOG.md:2470 +msgid "" +"To learn more, follow our [Dynamic DNS docs page](docs/configuring-" +"playbook-dynamic-dns.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2473 +msgid "2020-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:2475 +msgid "" +"(Compatibility Break) https://matrix.example.com/ now redirects to " +"https://element.example.com/" +msgstr "" + +#: ../../../CHANGELOG.md:2477 +msgid "" +"Until now, we used to serve a static page coming from Synapse at " +"`https://matrix.example.com/`. This page was not very useful to anyone." +msgstr "" + +#: ../../../CHANGELOG.md:2479 +msgid "" +"Since `matrix.example.com` may be accessed by regular users in certain " +"conditions, it's probably better to redirect them to a better place (e.g." +" to [Element Web](docs/configuring-playbook-client-element-web.md))." +msgstr "" + +#: ../../../CHANGELOG.md:2481 +msgid "" +"If Element Web is installed (`matrix_client_element_enabled: true`, which" +" it is by default), we now redirect people to it, instead of showing them" +" a Synapse static page." +msgstr "" + +#: ../../../CHANGELOG.md:2483 +msgid "" +"If you'd like to control where the redirect goes, use the " +"`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` " +"variable. To restore the old behavior of not redirecting anywhere and " +"serving the Synapse static page, set it to an empty value " +"(`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: " +"\"\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2486 +msgid "2020-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:2488 +msgid "" +"(Compatibility Break) /_synapse/admin is no longer publicly exposed by " +"default" +msgstr "" + +#: ../../../CHANGELOG.md:2490 +msgid "" +"We used to expose the Synapse Admin APIs publicly (at " +"`https://matrix.example.com/_synapse/admin`). These APIs require " +"authentication with a valid access token, so it's not that big a deal to " +"expose them." +msgstr "" + +#: ../../../CHANGELOG.md:2492 +msgid "" +"However, following [official Synapse's reverse-proxying " +"recommendations](https://github.com/element-" +"hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-" +"endpoints), we're no longer exposing `/_synapse/admin` by default." +msgstr "" + +#: ../../../CHANGELOG.md:2494 +msgid "" +"If you'd like to restore restore the old behavior and expose " +"`/_synapse/admin` publicly, you can use the following configuration (in " +"your `vars.yml`):" +msgstr "" + +#: ../../../CHANGELOG.md:2501 +msgid "2020-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:2503 +msgid "Minimum Ansible version raised to v2.7.0" +msgstr "" + +#: ../../../CHANGELOG.md:2505 +msgid "" +"We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 " +"and higher, but issues like [#662](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/662) demonstrate that we need at least " +"v2.7.0." +msgstr "" + +#: ../../../CHANGELOG.md:2507 +msgid "" +"If you've been using the playbook without getting any errors until now, " +"you're probably on a version higher than that already (or you're not " +"using the `matrix-ma1sd` and `matrix-client-element` roles)." +msgstr "" + +#: ../../../CHANGELOG.md:2509 +msgid "" +"Our [Ansible docs page](docs/ansible.md) contains information on how to " +"run a more up-to-date version of Ansible." +msgstr "" + +#: ../../../CHANGELOG.md:2512 +msgid "2020-10-01" +msgstr "" + +#: ../../../CHANGELOG.md:2514 +msgid "Postgres 13 support" +msgstr "" + +#: ../../../CHANGELOG.md:2516 +msgid "" +"The playbook now installs [Postgres " +"13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) " +"by default." +msgstr "" + +#: ../../../CHANGELOG.md:2518 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by " +"following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md" +"#upgrading-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2520 +msgid "2020-09-01" +msgstr "" + +#: ../../../CHANGELOG.md:2522 +msgid "matrix-registration support" +msgstr "" + +#: ../../../CHANGELOG.md:2524 +msgid "" +"The playbook can now help you set up [matrix-" +"registration](https://github.com/ZerataX/matrix-registration) - an " +"application that lets you keep your Matrix server's registration private," +" but still allow certain users (those having a unique registration link) " +"to register by themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2526 +msgid "" +"See our [Setting up matrix-registration](docs/configuring-playbook-" +"matrix-registration.md) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2529 +msgid "2020-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2531 +msgid "rust-synapse-compress-state support" +msgstr "" + +#: ../../../CHANGELOG.md:2533 +msgid "" +"The playbook can now help you use [rust-synapse-compress-" +"state](https://github.com/matrix-org/rust-synapse-compress-state) to " +"compress the state groups in your Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2535 +msgid "" +"See our [Compressing state with rust-synapse-compress-state](docs" +"/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-" +"state) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2538 +msgid "2020-07-22" +msgstr "" + +#: ../../../CHANGELOG.md:2540 +msgid "Synapse Admin support" +msgstr "" + +#: ../../../CHANGELOG.md:2542 +msgid "" +"The playbook can now help you set up [synapse-admin](https://github.com" +"/Awesome-Technologies/synapse-admin)." +msgstr "" + +#: ../../../CHANGELOG.md:2544 +msgid "" +"See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-" +"admin.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2547 +msgid "2020-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:2549 +msgid "matrix-reminder-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:2551 +msgid "" +"The playbook can now help you set up [matrix-reminder-" +"bot](https://github.com/anoadragon453/matrix-reminder-bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2553 +msgid "" +"See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-" +"matrix-reminder-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2556 +msgid "2020-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:2558 +msgid "(Compatibility Break) Riot is now Element" +msgstr "" + +#: ../../../CHANGELOG.md:2560 +msgid "" +"As per the official announcement, [Riot has been rebraned to " +"Element](https://element.io/blog/welcome-to-element/)." +msgstr "" + +#: ../../../CHANGELOG.md:2562 +msgid "" +"The playbook follows suit. Existing installations have a few options for " +"how to handle this." +msgstr "" + +#: ../../../CHANGELOG.md:2564 +msgid "" +"See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md" +"#migrating-to-element) documentation page for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2567 +msgid "2020-07-03" +msgstr "" + +#: ../../../CHANGELOG.md:2569 +msgid "Steam bridging support via mx-puppet-steam" +msgstr "" + +#: ../../../CHANGELOG.md:2571 +msgid "" +"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " +"playbook now supports bridging to [Steam](https://steamapp.com/) via the " +"[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge." +" See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-" +"bridge-mx-puppet-steam.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2574 +msgid "2020-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:2576 +msgid "Discord bridging support via mx-puppet-discord" +msgstr "" + +#: ../../../CHANGELOG.md:2578 +msgid "" +"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " +"playbook now supports bridging to [Discord](https://discordapp.com/) via " +"the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) " +"bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-" +"playbook-bridge-mx-puppet-discord.md) documentation page for getting " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2580 +msgid "" +"**Note**: this is a new Discord bridge. The playbook still retains " +"Discord bridging via [matrix-appservice-discord](docs/configuring-" +"playbook-bridge-appservice-discord.md). You're free too use the bridge " +"that serves you better, or even both (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:2583 +msgid "2020-06-30" +msgstr "" + +#: ../../../CHANGELOG.md:2585 +msgid "Instagram and Twitter bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2587 +msgid "" +"Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s " +"efforts, the playbook now supports bridging to " +"[Instagram](https://www.instagram.com/) via the [mx-puppet-" +"instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See " +"our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-" +"bridge-mx-puppet-instagram.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2589 +msgid "" +"Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the " +"playbook now supports bridging to [Twitter](https://twitter.com/) via the" +" [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) " +"bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-" +"playbook-bridge-mx-puppet-twitter.md) documentation page for getting " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2592 +msgid "2020-06-28" +msgstr "" + +#: ../../../CHANGELOG.md:2594 +msgid "" +"(Post Mortem / fixed Security Issue) Re-enabling User Directory search " +"powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625 +msgid "" +"User Directory search requests used to go to the ma1sd identity server by" +" default, which queried its own stores and the Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2598 +msgid "" +"ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has " +"been fixed in version `2.4.0`, with [this " +"commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd " +"2.4.0` is now the default version for this playbook. For more information" +" on what happened, please check the mentioned issue." +msgstr "" + +#: ../../../CHANGELOG.md:2600 +msgid "" +"We are re-enabling user directory search with this update. Those who " +"would like to keep it disabled can use this configuration: " +"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:2602 +msgid "As always, re-running the playbook is enough to get the updated bits." +msgstr "" + +#: ../../../CHANGELOG.md:2604 +msgid "2020-06-11" +msgstr "" + +#: ../../../CHANGELOG.md:2606 +msgid "SMS bridging requires db reset" +msgstr "" + +#: ../../../CHANGELOG.md:2608 +msgid "" +"The current version of [matrix-sms-bridge](https://github.com/benkuly" +"/matrix-sms-bridge) needs you to delete the database to work as expected." +" Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new " +"requried var `matrix_sms_bridge_default_region`." +msgstr "" + +#: ../../../CHANGELOG.md:2610 +msgid "" +"To reuse your existing rooms, invite `@smsbot:yourServer` to the room or " +"write a message. You are also able to use automated room creation with " +"telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a" +" room with `@smsbot:yourServer`. See [the " +"docs](https://github.com/benkuly/matrix-sms-bridge) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:2612 +msgid "2020-06-05" +msgstr "" + +#: ../../../CHANGELOG.md:2614 +msgid "SMS bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2616 +msgid "" +"Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook " +"now supports bridging to SMS (with one telephone number only) via " +"[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2618 +msgid "" +"See our [Setting up Matrix SMS bridging](docs/configuring-playbook-" +"bridge-matrix-bridge-sms.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2621 +msgid "2020-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2623 +msgid "" +"(Compatibility Break / Security Issue) Disabling User Directory search " +"powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2627 +msgid "" +"ma1sd current has [a security " +"issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak " +"information about all users - including users created by bridges, etc." +msgstr "" + +#: ../../../CHANGELOG.md:2629 +msgid "" +"Until the issue gets fixed, we're making User Directory search not go to " +"ma1sd by default. You **need to re-run the playbook and restart services " +"to apply this workaround**." +msgstr "" + +#: ../../../CHANGELOG.md:2631 +msgid "" +"*If you insist on restoring the old behavior* (**which has a security " +"issue!**), you *might* use this configuration: " +"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ " +"matrix_ma1sd_enabled }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2634 +msgid "2020-04-28" +msgstr "" + +#: ../../../CHANGELOG.md:2636 +msgid "Newer IRC bridge (with potential breaking change)" +msgstr "" + +#: ../../../CHANGELOG.md:2638 +msgid "" +"This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made" +" a change to how you define manual mappings. If you added a `mapping` to" +" your configuration, you will need to update it accoring to the [upstream" +" instructions](https://github.com/matrix-org/matrix-appservice-" +"irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include " +"`mappings` in your configuration for IRC, no change is necessary. " +"`mappings` is not part of the default configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2647 +msgid "2020-04-23" +msgstr "" + +#: ../../../CHANGELOG.md:2649 ../../../CHANGELOG.md:2880 +msgid "Slack bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2651 +msgid "" +"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " +"playbook now supports bridging to [Slack](https://slack.com) via the [mx-" +"puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2653 +msgid "" +"See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-" +"bridge-mx-puppet-slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2656 +msgid "2020-04-09" +msgstr "" + +#: ../../../CHANGELOG.md:2658 +msgid "Skype bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2660 +msgid "" +"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " +"playbook now supports bridging to [Skype](https://www.skype.com) via the " +"[mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2662 +msgid "" +"See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-" +"bridge-mx-puppet-skype.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2665 +msgid "2020-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2667 +msgid "Private Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2669 +msgid "" +"The [Jitsi support](#jitsi-support) we had landed a few weeks ago was " +"working well, but it was always open to the whole world." +msgstr "" + +#: ../../../CHANGELOG.md:2671 +msgid "" +"Running such an open instance is not desirable to most people, so " +"[teutat3s](https://github.com/teutat3s) has contributed support for " +"making Jitsi use authentication." +msgstr "" + +#: ../../../CHANGELOG.md:2673 +msgid "" +"To make your Jitsi server more private, see the [configure internal Jitsi" +" authentication and guests mode](docs/configuring-playbook-jitsi.md" +"#optional-configure-internal-jitsi-authentication-and-guests-mode) " +"section in our Jitsi documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2676 +msgid "2020-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2678 +msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" +msgstr "" + +#: ../../../CHANGELOG.md:2680 +msgid "" +"Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the " +"[mxisd](https://github.com/kamax-io/mxisd) identity server, which has " +"been deprecated for a long time, has finally been replaced by " +"[ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." +msgstr "" + +#: ../../../CHANGELOG.md:2682 +msgid "" +"**If you're using the default playbook configuration**, you don't need to" +" do anything -- your mxisd installation will be replaced with ma1sd and " +"all existing data will be migrated automatically the next time you run " +"the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2684 +msgid "" +"**If you're doing something more special** (defining custom " +"`matrix_mxisd_*` variables), the playbook will ask you to rename them to " +"`matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well " +"for such a more custom setup." +msgstr "" + +#: ../../../CHANGELOG.md:2687 +msgid "2020-03-29" +msgstr "" + +#: ../../../CHANGELOG.md:2689 +msgid "Archlinux support" +msgstr "" + +#: ../../../CHANGELOG.md:2691 +msgid "" +"Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts," +" the playbook now supports installing to an " +"[Archlinux](https://www.archlinux.org/) server." +msgstr "" + +#: ../../../CHANGELOG.md:2694 +msgid "2020-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:2696 +msgid "Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2698 +msgid "" +"The playbook can now (optionally) install the [Jitsi](https://jitsi.org/)" +" video-conferencing platform and integrate it with [Riot](docs" +"/configuring-playbook-riot-web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2700 +msgid "" +"See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to" +" get started." +msgstr "" + +#: ../../../CHANGELOG.md:2703 +msgid "2020-03-15" +msgstr "" + +#: ../../../CHANGELOG.md:2705 +msgid "Raspberry Pi support" +msgstr "" + +#: ../../../CHANGELOG.md:2707 +msgid "" +"Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the " +"playbook supports installing to a Raspberry Pi server, for at least some " +"of the services." +msgstr "" + +#: ../../../CHANGELOG.md:2709 +msgid "" +"Since most ready-made container images do not support that architecture, " +"we achieve this by building images locally on the device itself. See our " +"[Self-building documentation page](docs/self-building.md) for how to get " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2712 +msgid "2020-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:2714 +msgid "Riot-web themes are here" +msgstr "" + +#: ../../../CHANGELOG.md:2716 +msgid "The playbook now makes it easy to install custom riot-web themes." +msgstr "" + +#: ../../../CHANGELOG.md:2718 +msgid "" +"To learn more, take a look at our [riot-web documentation on Themes](docs" +"/configuring-playbook-riot-web.md#themes)." +msgstr "" + +#: ../../../CHANGELOG.md:2721 +msgid "2020-02-24" +msgstr "" + +#: ../../../CHANGELOG.md:2723 +msgid "Customize the server name in Riot's login page" +msgstr "" + +#: ../../../CHANGELOG.md:2725 +msgid "" +"You can now customize the server name string that Riot-web displays in " +"its login page." +msgstr "" + +#: ../../../CHANGELOG.md:2727 +msgid "These playbook variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:2733 +msgid "" +"The login page previously said \"Sign in to your Matrix account on " +"matrix.example.org\" (the homeserver's domain name). It will now say " +"\"Sign in … on example.org\" (the server name) by default, or \"Sign in …" +" on Our Server\" if you set the variable to \"Our Server\"." +msgstr "" + +#: ../../../CHANGELOG.md:2735 +msgid "" +"To support this, the config.json template is changed to use the " +"configuration key `default_server_config` for setting the default HS/IS, " +"and the new configuration key `server_name` is added in there." +msgstr "" + +#: ../../../CHANGELOG.md:2738 +msgid "2020-01-30" +msgstr "" + +#: ../../../CHANGELOG.md:2740 +msgid "Disabling TLSv1.1" +msgstr "" + +#: ../../../CHANGELOG.md:2742 +msgid "" +"To improve security, we've removed TLSv1.1 support from our default " +"matrix-nginx-proxy configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2744 +msgid "" +"If you need to support old clients, you can re-enable it with the " +"following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 " +"TLSv1.2 TLSv1.3\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2747 +msgid "2020-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:2749 +msgid "Postgres collation changes (action required!)" +msgstr "" + +#: ../../../CHANGELOG.md:2751 +msgid "" +"By default, we've been using a UTF-8 collation for Postgres. This is " +"known to cause Synapse some troubles (see the [relevant " +"issue](https://github.com/matrix-org/synapse/issues/6722)) on systems " +"that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in " +"an [Alpine Linux](https://alpinelinux.org/) container (which uses " +"[musl](https://www.musl-libc.org/), and not glibc), so our users are " +"likely not affected by the index corruption problem observed by others." +msgstr "" + +#: ../../../CHANGELOG.md:2753 +msgid "" +"Still, we might become affected in the future. In any case, it's imminent" +" that Synapse will complain about databases which do not use a C " +"collation." +msgstr "" + +#: ../../../CHANGELOG.md:2755 +msgid "To avoid future problems, we recommend that you run the following command:" +msgstr "" + +#: ../../../CHANGELOG.md:2761 +msgid "" +"It forces a [Postgres database upgrade](docs/maintenance-postgres.md" +"#upgrading-postgresql), which would recreate your Postgres database using" +" the proper (`C`) collation. If you are low on disk space, or run into " +"trouble, refer to the Postgres database upgrade documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:2764 +msgid "2020-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2766 +msgid "Added support for Appservice Webhooks" +msgstr "" + +#: ../../../CHANGELOG.md:2768 +msgid "" +"Thanks to a contribution from [Björn " +"Marten](https://github.com/tripleawwy) from " +"[netresearch](https://www.netresearch.de/), the playbook can now install " +"and configure [matrix-appservice-webhooks](https://github.com/turt2live" +"/matrix-appservice-webhooks) for you. This bridge provides support for " +"Slack-compatible webhooks." +msgstr "" + +#: ../../../CHANGELOG.md:2770 +msgid "" +"Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-" +"playbook-bridge-appservice-webhooks.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2773 +msgid "2020-01-12" +msgstr "" + +#: ../../../CHANGELOG.md:2775 +msgid "Added support for automatic Double Puppeting for all Mautrix bridges" +msgstr "" + +#: ../../../CHANGELOG.md:2777 +msgid "" +"Double Puppeting can now be easily enabled for all Mautrix bridges " +"supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." +msgstr "" + +#: ../../../CHANGELOG.md:2779 +msgid "" +"This is possible due to those bridges' integration with [matrix-synapse-" +"shared-secret-auth](https://github.com/devture/matrix-synapse-shared-" +"secret-auth) - yet another component that this playbook can install for " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:2781 +msgid "" +"To get started, following the playbook's documentation for the bridge " +"you'd like to configure." +msgstr "" + +#: ../../../CHANGELOG.md:2784 +msgid "2019-12-06" +msgstr "" + +#: ../../../CHANGELOG.md:2786 +msgid "Added support for an alternative method for using another webserver" +msgstr "" + +#: ../../../CHANGELOG.md:2788 +msgid "" +"We have added support for making `matrix-nginx-proxy` not being so " +"invasive, so that it would be easier to [use your own webserver](docs" +"/configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2790 +msgid "" +"The documentation has been updated with a **Method 2**, which might make " +"\"own webserver\" setup easier in some cases (such as [reverse-proxying " +"using Traefik](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/296))." +msgstr "" + +#: ../../../CHANGELOG.md:2792 +msgid "" +"**Existing users** are not affected by this and **don't need to change " +"anything**. The defaults are still the same (`matrix-nginx-proxy` " +"obtaining SSL certificates and doing everything for you automatically)." +msgstr "" + +#: ../../../CHANGELOG.md:2795 +msgid "2019-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2797 +msgid "Tightened security around room directory publishing" +msgstr "" + +#: ../../../CHANGELOG.md:2799 +msgid "" +"As per this [advisory blog post](https://matrix.org/blog/2019/11/09" +"/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to" +" change the default publishing rules for the Matrix room directory." +msgstr "" + +#: ../../../CHANGELOG.md:2801 +msgid "" +"Our general goal is to favor privacy and security when running personal " +"(family & friends) and corporate homeservers. Both of these likely " +"benefit from having a more secure default of **not showing the room " +"directory without authentication** and **not publishing the room " +"directory over federation**." +msgstr "" + +#: ../../../CHANGELOG.md:2803 +msgid "" +"As with anything else, these new defaults can be overriden by changing " +"the `matrix_synapse_allow_public_rooms_without_auth` and " +"`matrix_synapse_allow_public_rooms_over_federation` variables, " +"respectively." +msgstr "" + +#: ../../../CHANGELOG.md:2806 +msgid "2019-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:2808 +msgid "Improved Postgres upgrading/importing" +msgstr "" + +#: ../../../CHANGELOG.md:2810 +msgid "" +"Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) " +"and [importing](docs/importing-postgres.md) have been improved to add " +"support for multiple databases and roles." +msgstr "" + +#: ../../../CHANGELOG.md:2812 +msgid "" +"Previously, the playbook would only take care of the `homeserver` " +"database and `synapse` user. We now back up and restore all databases and" +" users on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2814 +msgid "" +"For now, the playbook only uses that one database (`homeserver`) and that" +" one single user (`synapse`), so it's all the same. However, in the " +"future, additional components besides Synapse may also make use the " +"Postgres database server. One such example is the [matrix-appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, " +"which strongly encourages use of Postgres in its v1.0 release. We are yet" +" to upgrade to it." +msgstr "" + +#: ../../../CHANGELOG.md:2816 +msgid "" +"Additionally, Postgres [upgrading](docs/maintenance-postgres.md" +"#upgrading-postgresql) now uses gzipped dump files by default, to " +"minimize disk space usage." +msgstr "" + +#: ../../../CHANGELOG.md:2819 +msgid "2019-10-04" +msgstr "" + +#: ../../../CHANGELOG.md:2821 +msgid "Postgres 12 support" +msgstr "" + +#: ../../../CHANGELOG.md:2823 +msgid "" +"The playbook now installs [Postgres " +"12](https://www.postgresql.org/about/news/1976/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:2825 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following" +" the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" +"postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2828 +msgid "2019-10-03" +msgstr "" + +#: ../../../CHANGELOG.md:2830 +msgid "Synapse 1.4.0" +msgstr "" + +#: ../../../CHANGELOG.md:2832 +msgid "" +"Synapse 1.4.0 [is " +"out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots" +" of changes related to privacy." +msgstr "" + +#: ../../../CHANGELOG.md:2834 +msgid "" +"Its new defaults (which we adopt as well) mean that certain old data will" +" automatically get purged after a certain number of days. 1.4.0 " +"automatically garbage collects redacted messages (defaults to 7 days) and" +" removes unused IP and user agent information stored in the user_ips " +"table (defaults to 30 days). If you'd like to preserve this data, we " +"encourage you to look at the `redaction_retention_period` and " +"`user_ips_max_age` options (controllable by the " +"`matrix_synapse_redaction_retention_period` and " +"`matrix_synapse_user_ips_max_age` playbook variables, respectively) " +"before doing the upgrade. If you'd like to keep data indefinitely, set " +"these variables to `null` (e.g. " +"`matrix_synapse_redaction_retention_period: ~`)." +msgstr "" + +#: ../../../CHANGELOG.md:2836 +msgid "" +"From now on the `trusted_key_servers` setting for Synapse is " +"configurable. It still defaults to `matrix.org` just like it always has, " +"but in a more explicit way now. If you'd like to use another trusted key " +"server, adjust the `matrix_synapse_trusted_key_servers` playbook " +"variable." +msgstr "" + +#: ../../../CHANGELOG.md:2838 +msgid "" +"Synapse 1.4.0 also changes lots of things related to identity server " +"integration. Because Synapse will now by default be responsible for " +"validating email addresses for user accounts, running without an identity" +" server looks more feasible. We still [have " +"concerns](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/275/files#r331104117) over disabling the identity server by " +"default, so for now it remains enabled." +msgstr "" + +#: ../../../CHANGELOG.md:2841 +msgid "2019-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:2843 +msgid "Synapse Simple Antispam support" +msgstr "" + +#: ../../../CHANGELOG.md:2845 +msgid "" +"There have been lots of invite-spam attacks lately and " +"[Travis](https://github.com/t2bot) has created a Synapse module " +"([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" +"antispam)) to let people protect themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2847 +msgid "" +"From now on, you can easily install and configure this spam checker " +"module through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2849 +msgid "" +"Learn more in [Setting up Synapse Simple Antispam](docs/configuring-" +"playbook-synapse-simple-antispam.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2852 +msgid "2019-08-25" +msgstr "" + +#: ../../../CHANGELOG.md:2854 +msgid "Extensible Riot-web configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2856 +msgid "" +"Similarly to [Extensible Synapse configuration](#extensible-synapse-" +"configuration) (below), Riot-web configuration is also extensible now." +msgstr "" + +#: ../../../CHANGELOG.md:2858 +msgid "" +"From now on, you can extend/override Riot-web's configuration by making " +"use of the `matrix_riot_web_configuration_extension_json` variable. This " +"should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2860 +msgid "" +"If you need even more power, you can now also take full control and " +"override `matrix_riot_web_configuration_default` (or " +"`matrix_riot_web_configuration`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2862 +msgid "" +"Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-" +"web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2865 +msgid "2019-08-22" +msgstr "" + +#: ../../../CHANGELOG.md:2867 +msgid "Extensible Synapse configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2869 +msgid "" +"Previously, we had to create custom Ansible variables for each and every " +"Synapse setting. This lead to too much effort (and configuration " +"ugliness) to all of Synapse's settings, so naturally, not all features of" +" Synapse could be controlled through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2871 +msgid "" +"From now on, you can extend/override the Synapse server's configuration " +"by making use of the `matrix_synapse_configuration_extension_yaml` " +"variable. This should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2873 +msgid "" +"If you need even more power, you can now also take full control and " +"override `matrix_synapse_configuration` (or " +"`matrix_synapse_configuration_yaml`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2875 +msgid "" +"Learn more here in [Configuring Synapse](docs/configuring-playbook-" +"synapse.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2878 +msgid "2019-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2882 +msgid "" +"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/205) of " +"[kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart " +"Mumford (Cadair)](https://github.com/Cadair), the playbook now supports " +"bridging to [Slack](https://slack.com) via the [appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2884 +msgid "" +"Additional details are available in [Setting up Appservice Slack " +"bridging](docs/configuring-playbook-bridge-appservice-slack.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2886 +msgid "Google Hangouts bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2888 +msgid "" +"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/251) of [Eduardo Beltrame " +"(Munfred)](https://github.com/Munfred) and [Robbie D " +"(microchipster)](https://github.com/microchipster), the playbook now " +"supports bridging to [Google Hangouts](https://hangouts.google.com/) via " +"the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2890 +msgid "" +"Additional details are available in [Setting up Mautrix Hangouts " +"bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2893 +msgid "2019-08-05" +msgstr "" + +#: ../../../CHANGELOG.md:2895 +msgid "Email2Matrix support" +msgstr "" + +#: ../../../CHANGELOG.md:2897 +msgid "" +"Support for [Email2Matrix](https://github.com/devture/email2matrix) has " +"been added." +msgstr "" + +#: ../../../CHANGELOG.md:2899 +msgid "It's an optional feature that you can enable via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2901 +msgid "" +"To learn more, see the [playbook's documentation on Email2Matrix](./docs" +"/configuring-playbook-email2matrix.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2904 +msgid "2019-08-03" +msgstr "" + +#: ../../../CHANGELOG.md:2906 +msgid "Synapse logging level has been reduced to WARNING" +msgstr "" + +#: ../../../CHANGELOG.md:2908 +msgid "" +"After [some discussion in our support " +"room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one)," +" we've decided to change the default logging level for Synapse from " +"`INFO` to `WARNING`." +msgstr "" + +#: ../../../CHANGELOG.md:2910 +msgid "" +"This greatly reduces the number of log messages that are being logged, " +"leading to:" +msgstr "" + +#: ../../../CHANGELOG.md:2912 +msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" +msgstr "" + +#: ../../../CHANGELOG.md:2913 +msgid "" +"easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages," +" as they're not longer buried in thousands of non-important `INFO` " +"messages" +msgstr "" + +#: ../../../CHANGELOG.md:2915 +msgid "" +"If you'd like to track down an issue, you [can always increase the " +"logging level as described here](./docs/maintenance-and-" +"troubleshooting.md#increasing-synapse-logging)." +msgstr "" + +#: ../../../CHANGELOG.md:2918 +msgid "2019-07-08" +msgstr "" + +#: ../../../CHANGELOG.md:2920 +msgid "Synapse Maintenance docs and synapse-janitor support are available" +msgstr "" + +#: ../../../CHANGELOG.md:2922 +msgid "The playbook can now help you with Synapse's maintenance." +msgstr "" + +#: ../../../CHANGELOG.md:2924 +msgid "" +"There's a new documentation page about [Synapse maintenance](./docs" +"/maintenance-synapse.md) and another section on [Postgres " +"vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2926 +msgid "" +"Among other things, if your Postgres database has grown significantly " +"over time, you may wish to [ask the playbook to purge unused data with " +"synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-" +"synapse-janitor) for you." +msgstr "" + +#: ../../../CHANGELOG.md:2928 +msgid "(BC Break) Rename run control variables" +msgstr "" + +#: ../../../CHANGELOG.md:2930 +msgid "Some internal playbook control variables have been renamed." +msgstr "" + +#: ../../../CHANGELOG.md:2932 +msgid "" +"This change **only affects people who run this playbook's roles from " +"another playbook**. If you're using this playbook as-is, you're not " +"affected and don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:2934 +msgid "The following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:2936 +msgid "from `run_import_postgres` to `run_postgres_import`" +msgstr "" + +#: ../../../CHANGELOG.md:2937 +msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`" +msgstr "" + +#: ../../../CHANGELOG.md:2938 +msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`" +msgstr "" + +#: ../../../CHANGELOG.md:2939 +msgid "from `run_import_media_store` to `run_synapse_import_media_store`" +msgstr "" + +#: ../../../CHANGELOG.md:2940 +msgid "from `run_register_user` to `run_synapse_register_user`" +msgstr "" + +#: ../../../CHANGELOG.md:2941 +msgid "from `run_update_user_password` to `run_synapse_update_user_password`" +msgstr "" + +#: ../../../CHANGELOG.md:2944 +msgid "2019-07-04" +msgstr "" + +#: ../../../CHANGELOG.md:2946 +msgid "Synapse no longer logs to text files" +msgstr "" + +#: ../../../CHANGELOG.md:2948 +msgid "" +"Following what the official Synapse Docker image is doing " +"([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've" +" been doing for mostly everything installed by this playbook, **Synapse " +"no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2950 +msgid "" +"From now on, Synapse would only log to console, which goes to systemd's " +"journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:2952 +msgid "" +"Because of this, the following variables have become obsolete and were " +"removed:" +msgstr "" + +#: ../../../CHANGELOG.md:2954 +msgid "`matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:2955 +msgid "`matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:2957 +msgid "" +"To prevent confusion, it'd be better if you delete all old files manually" +" after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2959 +msgid "" +"Because Synapse is incredibly chatty when it comes to logging (here's " +"[one such issue](https://github.com/matrix-org/synapse/issues/4751) " +"describing the problem), if you're running an ancient distribution (like " +"CentOS 7.0), be advised that systemd's journald default logging " +"restrictions may not be high enough to capture all log messages generated" +" by Synapse. This is especially true if you've got a busy (Synapse) " +"server. We advise that you manually add `RateLimitInterval=0` and " +"`RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` " +"file, followed by restarting the logging service (`systemctl restart " +"systemd-journald`)." +msgstr "" + +#: ../../../CHANGELOG.md:2962 +msgid "2019-06-27" +msgstr "" + +#: ../../../CHANGELOG.md:2964 +msgid "" +"(BC Break) Discord bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2966 +msgid "" +"Until now, the `config.yaml` file for the [Discord bridge](docs" +"/configuring-playbook-bridge-appservice-discord.md) was managed by the " +"playbook, but the `registration.yaml` file was not." +msgstr "" + +#: ../../../CHANGELOG.md:2968 +msgid "From now on, the playbook will keep both configuration files sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2970 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/appservice-discord/discord-registration.yaml` configuration file, those " +"would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2972 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix" +"/appservice-discord/config`)." +msgstr "" + +#: ../../../CHANGELOG.md:2974 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/appservice-" +"discord/data`). When you run the playbook with an existing database file " +"(`/matrix/appservice-discord/discord.db`), the playbook will stop the " +"bridge and relocate the database file to the `./data` directory. There's " +"no data-loss involved. You'll need to restart the bridge manually though " +"(`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2976 +msgid "" +"The main directory (`/matrix/appservice-discord`) may contain some " +"leftover files (`user-store.db`, `room-store.db`, `config.yaml`, " +"`discord-registration.yaml`, `invite_link`). These are no longer " +"necessary and can be deleted manually." +msgstr "" + +#: ../../../CHANGELOG.md:2978 +msgid "" +"We're now following the default sample configuration for the Discord " +"bridge. If you need to override some values, define them in " +"`matrix_appservice_discord_configuration_extension_yaml`." +msgstr "" + +#: ../../../CHANGELOG.md:2981 +msgid "2019-06-24" +msgstr "" + +#: ../../../CHANGELOG.md:2983 +msgid "" +"(BC Break) WhatsApp bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2985 +msgid "" +"Until now, configuration files for the [WhatsApp bridge](docs" +"/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004 +#: ../../../CHANGELOG.md:3023 ../../../CHANGELOG.md:3062 +msgid "From now on, the playbook will keep the configuration in sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2989 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-" +"whatsapp/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2991 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"whatsapp/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:2993 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"whatsapp/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2995 +msgid "We're now following the default configuration for the WhatsApp bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2998 +msgid "2019-06-20" +msgstr "" + +#: ../../../CHANGELOG.md:3000 +msgid "" +"(BC Break) IRC bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3002 +msgid "" +"Until now, configuration files for the [IRC bridge](docs/configuring-" +"playbook-bridge-appservice-irc.md) were created by the playbook " +"initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3006 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/appservice-irc/config.yaml` or `/matrix/appservice-" +"irc/registration.yaml` configuration files, those would be lost the next " +"time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3008 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix" +"/appservice-irc/config`), so your old configuration remains in the base " +"directory (`/matrix/appservice-irc`)." +msgstr "" + +#: ../../../CHANGELOG.md:3010 +msgid "" +"Previously, we asked people to configure bridged IRC servers by extending" +" the bridge configuration " +"(`matrix_appservice_irc_configuration_extension_yaml`). While this is " +"still possible and will continue working forever, **we now recommend " +"defining IRC servers in the easier to use " +"`matrix_appservice_irc_ircService_servers` variable**. See [our IRC " +"bridge documentation page](docs/configuring-playbook-bridge-appservice-" +"irc.md) for an example." +msgstr "" + +#: ../../../CHANGELOG.md:3012 +msgid "" +"If you decide to continue using " +"`matrix_appservice_irc_configuration_extension_yaml`, you might be " +"interested to know that `ircService.databaseUri` and a few other keys now" +" have default values in the base configuration " +"(`matrix_appservice_irc_configuration_yaml`). You may wish to stop " +"redefining those keys, unless you really intend to override them. You " +"most likely only need to override `ircService.servers`." +msgstr "" + +#: ../../../CHANGELOG.md:3014 +msgid "" +"Bridge data (`passkey.pem` and database files) is now also stored in a " +"subdirectory (`/matrix/appservice-irc/data`). When you run the playbook " +"with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook " +"will stop the bridge and relocate the passkey and database files " +"(`rooms.db` and `users.db`) to the `./data` directory. There's no data-" +"loss involved. You'll need to restart the bridge manually though " +"(`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3017 +msgid "2019-06-15" +msgstr "" + +#: ../../../CHANGELOG.md:3019 +msgid "" +"(BC Break) Telegram bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3021 +msgid "" +"Until now, configuration files for the [Telegram bridge](docs" +"/configuring-playbook-bridge-mautrix-telegram.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3025 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-telegram/config.yaml` or `/matrix/mautrix-" +"telegram/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3027 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"telegram/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-telegram`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_telegram_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3029 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"telegram/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3031 +msgid "" +"Also, we're now following the default configuration for the Telegram " +"bridge, so some default configuration values are different:" +msgstr "" + +#: ../../../CHANGELOG.md:3033 +msgid "" +"`edits_as_replies` (used to be `false`, now `true`) - previously replies " +"were not sent over to Matrix at all; ow they are sent over as a reply to " +"the original message" +msgstr "" + +#: ../../../CHANGELOG.md:3034 +msgid "" +"`inline_images` (used to be `true`, now `false`) - this has to do with " +"captioned images. Inline-image (included caption) are said to exhibit " +"troubles on Riot iOS. When `false`, the caption arrives on the Matrix " +"side as a separate message." +msgstr "" + +#: ../../../CHANGELOG.md:3035 +msgid "" +"`authless_portals` (used to be `false`, now `true`) - creating portals " +"from the Telegram side is now possible" +msgstr "" + +#: ../../../CHANGELOG.md:3036 +msgid "" +"`whitelist_group_admins` (used to be `false`, now `true`) - allows " +"Telegram group admins to use the bot commands" +msgstr "" + +#: ../../../CHANGELOG.md:3038 +msgid "" +"If the new values are not to your liking, use " +"`matrix_mautrix_telegram_configuration_extension_yaml` to specify an " +"override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure" +" out which variable goes where)." +msgstr "" + +#: ../../../CHANGELOG.md:3041 +msgid "2019-06-12" +msgstr "" + +#: ../../../CHANGELOG.md:3043 +msgid "Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3045 +msgid "" +"With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11" +"/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people " +"being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` " +"DNS SRV record that we've been keeping for compatibility with old Synapse" +" versions (<= 0.34)." +msgstr "" + +#: ../../../CHANGELOG.md:3047 +msgid "" +"According to the [Server Discovery " +"specification](https://matrix.org/docs/spec/server_server/r0.1.2.html" +"#server-discovery), it's no harm to keep the DNS SRV record. But since " +"it's not necessary for federating with the larger Matrix network anymore," +" you should be safe to get rid of it." +msgstr "" + +#: ../../../CHANGELOG.md:3049 +msgid "" +"**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` " +"DNS SRV records. The latter, **must not** be removed." +msgstr "" + +#: ../../../CHANGELOG.md:3051 +msgid "" +"For completeness, we must say that using a `_matrix._tcp` [SRV record for" +" Server Delegation](docs/howto-server-delegation.md#server-delegation-" +"via-a-dns-srv-record-advanced) is still valid and useful for certain " +"deployments. It's just that our guide recommends the [`/.well-" +"known/matrix/server` Server Delegation method](docs/howto-server-" +"delegation.md#server-delegation-via-a-well-known-file), due to its easier" +" implementation when using this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3053 +msgid "" +"Besides this optional/non-urgent DNS change, assuming you're already on " +"Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-" +"running the playbook](docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3056 +msgid "2019-06-07" +msgstr "" + +#: ../../../CHANGELOG.md:3058 +msgid "" +"(BC Break) Facebook bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3060 +msgid "" +"Until now, configuration files for the [Facebook bridge](docs" +"/configuring-playbook-bridge-mautrix-facebook.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3064 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-facebook/config.yaml` or `/matrix/mautrix-" +"facebook/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3066 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"facebook/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-facebook`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_facebook_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3068 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"facebook/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3071 +msgid "2019-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:3073 +msgid "Support for exposing container ports publicly (not just to the host)" +msgstr "" + +#: ../../../CHANGELOG.md:3075 +msgid "" +"Until now, various roles supported a `matrix_*_expose_port` variable, " +"which would expose their container's port to the host. This was mostly " +"useful for reverse-proxying manually (in case `matrix-nginx-proxy` was " +"disabled). It could also be used for installing some playbook services " +"(e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." +msgstr "" + +#: ../../../CHANGELOG.md:3077 +msgid "" +"`matrix_*_expose_port` variables were not granular enough - sometimes " +"they would expose one port, other times multiple. They also didn't " +"provide control over **where** to expose (to which port number and to " +"which network interface), because they would usually hardcode something " +"like `127.0.0.1:8080`." +msgstr "" + +#: ../../../CHANGELOG.md:3079 +msgid "" +"All such variables have been superseded by a better (more flexible) way " +"to do it." +msgstr "" + +#: ../../../CHANGELOG.md:3081 +msgid "" +"**Most** people (including those not using `matrix-nginx-proxy`), **don't" +" need** to bother with this." +msgstr "" + +#: ../../../CHANGELOG.md:3083 +msgid "Porting examples follow for people having more customized setups:" +msgstr "" + +#: ../../../CHANGELOG.md:3085 +msgid "" +"**from** `matrix_synapse_container_expose_client_api_port: true` **to** " +"`matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" +msgstr "" + +#: ../../../CHANGELOG.md:3087 +msgid "" +"**from** `matrix_synapse_container_expose_federation_api_port: true` " +"**to** `matrix_synapse_container_federation_api_plain_host_bind_port: " +"'127.0.0.1:8048'` and possibly " +"`matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" +msgstr "" + +#: ../../../CHANGELOG.md:3089 +msgid "" +"**from** `matrix_synapse_container_expose_metrics_port: true` **to** " +"`matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" +msgstr "" + +#: ../../../CHANGELOG.md:3091 +msgid "" +"**from** `matrix_riot_web_container_expose_port: true` **to** " +"`matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" +msgstr "" + +#: ../../../CHANGELOG.md:3093 +msgid "" +"**from** `matrix_mxisd_container_expose_port: true` **to** " +"`matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" +msgstr "" + +#: ../../../CHANGELOG.md:3095 +msgid "" +"**from** `matrix_dimension_container_expose_port: true` **to** " +"`matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" +msgstr "" + +#: ../../../CHANGELOG.md:3097 +msgid "" +"**from** `matrix_corporal_container_expose_ports: true` **to** " +"`matrix_corporal_container_http_gateway_host_bind_port: " +"'127.0.0.1:41080'` and possibly " +"`matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" +msgstr "" + +#: ../../../CHANGELOG.md:3099 +msgid "" +"**from** `matrix_appservice_irc_container_expose_client_server_api_port: " +"true` **to** `matrix_appservice_irc_container_http_host_bind_port: " +"'127.0.0.1:9999'`" +msgstr "" + +#: ../../../CHANGELOG.md:3101 +msgid "" +"**from** " +"`matrix_appservice_discord_container_expose_client_server_api_port: true`" +" **to** `matrix_appservice_discord_container_http_host_bind_port: " +"'127.0.0.1:9005'`" +msgstr "" + +#: ../../../CHANGELOG.md:3103 +msgid "" +"As always, if you forget to remove usage of some outdated variable, the " +"playbook will warn you." +msgstr "" + +#: ../../../CHANGELOG.md:3106 +msgid "2019-05-23" +msgstr "" + +#: ../../../CHANGELOG.md:3108 +msgid "(BC Break) Ansible 2.8 compatibility" +msgstr "" + +#: ../../../CHANGELOG.md:3110 +msgid "" +"Thanks to [@danbob](https://github.com/danbob), the playbook now " +"[supports the new Ansible 2.8](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/187)." +msgstr "" + +#: ../../../CHANGELOG.md:3112 +msgid "" +"A manual change is required to the `inventory/hosts` file, changing the " +"group name from `matrix-servers` to `matrix_servers` (dash to " +"underscore)." +msgstr "" + +#: ../../../CHANGELOG.md:3114 +msgid "To avoid doing it manually, run this:" +msgstr "" + +#: ../../../CHANGELOG.md:3115 +msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3116 +msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3119 +msgid "2019-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:3121 +msgid "Synapse no longer required" +msgstr "" + +#: ../../../CHANGELOG.md:3123 +msgid "" +"The playbook no longer insists on installing [Synapse](https://github.com" +"/element-hq/synapse) via the `matrix-synapse` role." +msgstr "" + +#: ../../../CHANGELOG.md:3125 +msgid "" +"If you would prefer to install Synapse another way and just use the " +"playbook to install other services, it should be possible " +"(`matrix_synapse_enabled: false`)." +msgstr "" + +#: ../../../CHANGELOG.md:3127 +msgid "" +"Note that it won't necessarily be the best experience, since the playbook" +" wires things to Synapse by default. If you're using your own Synapse " +"instance (especially one not running in a container), you may have to " +"override many variables to point them to the correct place." +msgstr "" + +#: ../../../CHANGELOG.md:3129 +msgid "" +"Having Synapse not be a required component potentially opens the door for" +" installing alternative Matrix homeservers." +msgstr "" + +#: ../../../CHANGELOG.md:3131 +msgid "Bridges are now separate from the Synapse role" +msgstr "" + +#: ../../../CHANGELOG.md:3133 +msgid "" +"Bridges are no longer part of the `matrix-synapse` role. Each bridge now " +"lives in its own separate role (`roles/custom/matrix-bridge-*`)." +msgstr "" + +#: ../../../CHANGELOG.md:3135 +msgid "" +"These bridge roles are independent of the `matrix-synapse` role, so it " +"should be possible to use them with a Synapse instance installed another " +"way (not through the playbook)." +msgstr "" + +#: ../../../CHANGELOG.md:3137 +msgid "Renaming inconsistently-named Synapse variables" +msgstr "" + +#: ../../../CHANGELOG.md:3139 +msgid "For better consistency, the following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3141 +msgid "" +"`matrix_enable_room_list_search` was renamed to " +"`matrix_synapse_enable_room_list_search`" +msgstr "" + +#: ../../../CHANGELOG.md:3142 +msgid "" +"`matrix_alias_creation_rules` was renamed to " +"`matrix_synapse_alias_creation_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3143 +msgid "" +"`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was " +"renamed to `matrix_synapse_room_list_publication_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3146 +msgid "2019-05-09" +msgstr "" + +#: ../../../CHANGELOG.md:3148 +msgid "" +"Besides a myriad of bug fixes and minor improvements, here are the more " +"notable (bigger) features we can announce today." +msgstr "" + +#: ../../../CHANGELOG.md:3150 +msgid "Mautrix Facebook/Messenger bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3152 +msgid "" +"The playbook now supports bridging with " +"[Facebook](https://www.facebook.com/) by installing the [mautrix-" +"facebook](https://github.com/tulir/mautrix-facebook) bridge. This " +"playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3154 +msgid "" +"Additional details are available in [Setting up Mautrix Facebook " +"bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3156 +msgid "mxisd Registration feature integration" +msgstr "" + +#: ../../../CHANGELOG.md:3158 +msgid "" +"The playbook can now help you integrate with mxisd's " +"[Registration](https://github.com/kamax-" +"matrix/mxisd/blob/master/docs/features/registration.md) feature." +msgstr "" + +#: ../../../CHANGELOG.md:3160 +msgid "" +"Learn more in [mxisd-controlled Registration](docs/configuring-playbook-" +"mxisd.md#mxisd-controlled-registration)." +msgstr "" + +#: ../../../CHANGELOG.md:3163 +msgid "2019-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:3165 +msgid "Caddy webserver examples" +msgstr "" + +#: ../../../CHANGELOG.md:3167 +msgid "" +"If you prefer using the [Caddy](https://caddyserver.com/) webserver " +"instead of our own integrated nginx, we now have examples for it in the " +"[`examples/caddy`](examples/caddy) directory" +msgstr "" + +#: ../../../CHANGELOG.md:3169 +msgid "2019-04-10" +msgstr "" + +#: ../../../CHANGELOG.md:3171 +msgid "Goofys support for other S3-compatible object stores" +msgstr "" + +#: ../../../CHANGELOG.md:3173 +msgid "" +"Until now, you could optionally host Synapse's media repository on Amazon" +" S3, but we now also support [using other S3-compatible object " +"stores](docs/configuring-playbook-s3.md)," +msgstr "" + +#: ../../../CHANGELOG.md:3176 +msgid "2019-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:3178 +msgid "Ansible >= 2.5 is required" +msgstr "" + +#: ../../../CHANGELOG.md:3180 +msgid "" +"Due to recent playbook improvements and the fact that the world keeps " +"turning, we're bumping the [version requirement for " +"Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." +msgstr "" + +#: ../../../CHANGELOG.md:3182 +msgid "" +"We've also started building our own Docker image of Ansible " +"([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is " +"useful for people who can't upgrade their local Ansible installation (see" +" [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." +msgstr "" + +#: ../../../CHANGELOG.md:3185 +msgid "2019-03-19" +msgstr "" + +#: ../../../CHANGELOG.md:3187 +msgid "TLS support for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:3189 +msgid "" +"We've added TLS support to the Coturn TURN server installed by the " +"playbook by default. The certificates from the Matrix domain will be used" +" for the Coturn server." +msgstr "" + +#: ../../../CHANGELOG.md:3191 +msgid "" +"This feature is enabled by default for new installations. To make use of " +"TLS support for your existing Matrix server's Coturn, make sure to " +"rebuild both Coturn and Synapse:" +msgstr "" + +#: ../../../CHANGELOG.md:3197 +msgid "" +"People who have an extra firewall (besides the iptables firewall, which " +"Docker manages automatically), will need to open these additional " +"firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over " +"UDP)." +msgstr "" + +#: ../../../CHANGELOG.md:3199 +msgid "" +"People who build their own custom playbook from our roles should be aware" +" that:" +msgstr "" + +#: ../../../CHANGELOG.md:3201 +msgid "" +"the `matrix-coturn` role and actually starting Coturn (e.g. " +"`--tags=start`), requires that certificates are already put in place. For" +" this reason, it's usually a good idea to have the `matrix-coturn` role " +"execute after `matrix-nginx-proxy` (which retrieves the certificates)." +msgstr "" + +#: ../../../CHANGELOG.md:3203 +msgid "" +"there are a few variables that can help you enable TLS support for " +"Coturn. See the `matrix-coturn` section in [group_vars/matrix-" +"servers](./group_vars/matrix-servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3206 +msgid "2019-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:3208 +msgid "matrix-nginx-proxy support for serving the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:3210 +msgid "" +"If you don't have a dedicated server for your base domain and want to set" +" up [Server Delegation via a well-known file](docs/howto-server-" +"delegation.md#server-delegation-via-a-well-known-file), the playbook has " +"got you covered now." +msgstr "" + +#: ../../../CHANGELOG.md:3212 +msgid "" +"It's now possible for the playbook to obtain an SSL certificate and serve" +" the necessary files for Matrix Server Delegation on your base domain. " +"Take a look at the new [Serving the base domain](docs/configuring-" +"playbook-base-domain-serving.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3214 +msgid "(BC break) matrix-nginx-proxy data variable renamed" +msgstr "" + +#: ../../../CHANGELOG.md:3216 +msgid "" +"`matrix_nginx_proxy_data_path` was renamed to " +"`matrix_nginx_proxy_base_path`." +msgstr "" + +#: ../../../CHANGELOG.md:3218 +msgid "" +"There's a new `matrix_nginx_proxy_data_path` variable, which has a " +"different use-purpose now (it's a subdirectory of " +"`matrix_nginx_proxy_base_path` and is meant for storing various data " +"files)." +msgstr "" + +#: ../../../CHANGELOG.md:3221 +msgid "2019-03-10" +msgstr "" + +#: ../../../CHANGELOG.md:3223 +msgid "Dimension integration manager support" +msgstr "" + +#: ../../../CHANGELOG.md:3225 +msgid "" +"Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can " +"now (optionally) install the [Dimension](https://dimension.t2bot.io/) " +"integration manager. To learn more, see the [Setting up Dimension](docs" +"/configuring-playbook-dimension.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3228 +msgid "2019-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:3230 +msgid "Ability to customize mxisd's email templates" +msgstr "" + +#: ../../../CHANGELOG.md:3232 +msgid "" +"Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's " +"email templates can now be customized easily. To learn more, see the " +"[Customizing email templates](docs/configuring-playbook-mxisd.md" +"#customizing-email-templates) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3235 +msgid "2019-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:3237 +msgid "Discord bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3239 +msgid "" +"[@Lionstiger](https://github.com/Lionstiger) has done some great work " +"adding Discord bridging support via [matrix-appservice-" +"discord](https://github.com/matrix-org/matrix-appservice-discord). To " +"learn more, see the [Setting up Appservice Discord bridging](docs" +"/configuring-playbook-bridge-appservice-discord.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3242 +msgid "2019-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:3244 +msgid "Renaming variables" +msgstr "" + +#: ../../../CHANGELOG.md:3246 ../../../CHANGELOG.md:3563 +#: ../../../CHANGELOG.md:3648 ../../../CHANGELOG.md:3768 +msgid "The following playbook variables were renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3248 +msgid "from `host_specific_hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3249 +msgid "from `hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3250 +msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`" +msgstr "" + +#: ../../../CHANGELOG.md:3251 +msgid "from `hostname_riot` to `matrix_server_fqn_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3252 +msgid "" +"from `host_specific_matrix_ssl_lets_encrypt_support_email` to " +"`matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3254 +msgid "" +"Doing that, we've simplified things, made names less confusing " +"(hopefully) and moved all variable names under the `matrix_` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:3257 +msgid "2019-02-16" +msgstr "" + +#: ../../../CHANGELOG.md:3259 +msgid "Riot v1.0.1 support" +msgstr "" + +#: ../../../CHANGELOG.md:3261 +msgid "You can now use the brand new and redesigned Riot." +msgstr "" + +#: ../../../CHANGELOG.md:3263 +msgid "" +"The new version no longer has a homepage by default, so we've also " +"removed the custom homepage that we've been installing." +msgstr "" + +#: ../../../CHANGELOG.md:3265 +msgid "" +"However, we still provide you with hooks to install your own `home.html` " +"file by specifying the `matrix_riot_web_embedded_pages_home_path` " +"variable (used to be called `matrix_riot_web_homepage_template` before)." +msgstr "" + +#: ../../../CHANGELOG.md:3268 +msgid "2019-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:3270 +msgid "Synapse v0.99.1" +msgstr "" + +#: ../../../CHANGELOG.md:3272 +msgid "" +"As we're moving toward Synapse v1.0, things are beginning to stabilize. " +"Upgrading from v0.99.0 to v0.99.1 should be painless." +msgstr "" + +#: ../../../CHANGELOG.md:3274 +msgid "" +"If you've been overriding the default configuration so that you can " +"terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), " +"you'll now have to replace this custom configuration with " +"`matrix_synapse_tls_federation_listener_enabled: true`. The " +"`matrix_synapse_no_tls` variable is no more." +msgstr "" + +#: ../../../CHANGELOG.md:3277 +msgid "2019-02-06" +msgstr "" + +#: ../../../CHANGELOG.md:3279 +msgid "Synapse v0.99 support and preparation for Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3281 +msgid "" +"Matrix is undergoing a lot of changes as it matures towards Synapse v1.0." +" The first step is the Synapse v0.99 transitional release, which this " +"playbook now supports." +msgstr "" + +#: ../../../CHANGELOG.md:3283 +msgid "" +"If you've been using this playbook successfully until now, you'd be aware" +" that we've been doing [Server Delegation](docs/howto-server-" +"delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring" +" DNS](docs/configuring-dns.md))." +msgstr "" + +#: ../../../CHANGELOG.md:3285 +msgid "" +"Due to changes related to certificate file requirements that will affect " +"us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV " +"record in the future** (when Synapse goes to v1.0 - around 5th of March " +"2019). We **still need to keep the SRV record for now**, for backward " +"compatibility with older Synapse versions (lower than v0.99)." +msgstr "" + +#: ../../../CHANGELOG.md:3287 +msgid "" +"**What you need to do now** is make use of this transitional Synapse " +"v0.99 release to **prepare your federation settings for the future**. You" +" have 2 choices to prepare yourself for compatibility with the future " +"Synapse v1.0:" +msgstr "" + +#: ../../../CHANGELOG.md:3289 +msgid "" +"(recommended) set up [Server Delegation via a well-known file](docs" +"/howto-server-delegation.md#server-delegation-via-a-well-known-file), " +"unless you are affected by the [Downsides of well-known-based Server " +"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" +"based-server-delegation). If you had previously set up the well-known " +"`client` file, depending on how you've done it, it may be that there is " +"nothing new required of you (besides [upgrading](docs/maintenance-" +"upgrading-services.md)). After upgrading, you can [run a self-check](docs" +"/maintenance-checking-services.md), which will tell you if you need to do" +" anything extra with regard to setting up [Server Delegation via a well-" +"known file](docs/howto-server-delegation.md#server-delegation-via-a-well-" +"known-file). After some time, when most people have upgraded to Synapse " +"v0.99 and older releases have disappeared, be prepared to drop your " +"`_matrix._tcp` SRV record." +msgstr "" + +#: ../../../CHANGELOG.md:3291 +msgid "" +"(more advanced) if the [Downsides of well-known-based Server " +"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" +"based-server-delegation) are not to your liking, **as an alternative**, " +"you can set up [Server Delegation via a DNS SRV record](docs/howto-" +"server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In" +" such a case, you get to keep using your existing `_matrix._tcp` DNS SRV " +"record forever and need to NOT set up a `/.well-known/matrix/server` " +"file. Don't forget that you need to do certificate changes though. Follow" +" the guide at [Server Delegation via a DNS SRV record](docs/howto-server-" +"delegation.md#server-delegation-via-a-dns-srv-record-advanced)." +msgstr "" + +#: ../../../CHANGELOG.md:3294 +msgid "2019-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:3296 +msgid "TLS v1.3 support" +msgstr "" + +#: ../../../CHANGELOG.md:3298 +msgid "" +"Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has " +"[added support for TLS v1.3](https://github.com/nginxinc/docker-" +"nginx/issues/190), we have enabled that protocol by default." +msgstr "" + +#: ../../../CHANGELOG.md:3300 +msgid "When using:" +msgstr "" + +#: ../../../CHANGELOG.md:3302 +msgid "" +"the **integrated nginx server**: TLS v1.3 support might not kick in " +"immediately, because the nginx version hasn't been bumped and you may " +"have an older build of the nginx Docker image (currently " +"`nginx:1.15.8-alpine`). Typically, we do not re-pull images that you " +"already have. When the nginx version gets bumped in the future, everyone " +"will get the update. Until then, you could manually force-pull the " +"rebuilt Docker image by running this on the server: `docker pull " +"nginx:1.15.8-alpine`." +msgstr "" + +#: ../../../CHANGELOG.md:3304 +msgid "" +"**your own external nginx server**: if your external nginx server is too " +"old, the new configuration we generate for you in `/matrix/nginx-" +"proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and " +"your nginx version might not support that. You can adjust the SSL " +"protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` " +"variable. Learn more in the documentation page for [Using your own " +"webserver, instead of this playbook's nginx proxy](docs/configuring-" +"playbook-own-webserver.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3306 +msgid "" +"**another web server**: you don't need to do anything to accommodate this" +" change" +msgstr "" + +#: ../../../CHANGELOG.md:3309 +msgid "2019-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:3311 +msgid "IRC bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3313 +msgid "" +"[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some " +"great work bringing IRC bridging support via [matrix-appservice-" +"irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, " +"see the [Setting up Appservice IRC bridging](docs/configuring-playbook-" +"bridge-appservice-irc.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3316 +msgid "2019-01-29" +msgstr "" + +#: ../../../CHANGELOG.md:3318 +msgid "" +"Running container processes as non-root, without capabilities and read-" +"only" +msgstr "" + +#: ../../../CHANGELOG.md:3320 +msgid "" +"To improve security, this playbook no longer starts container processes " +"as the `root` user. Most containers were dropping privileges anyway, but " +"we were trusting them with `root` privileges until they would do that. " +"Not anymore -- container processes now start as a non-root user (usually " +"`matrix`) from the get-go." +msgstr "" + +#: ../../../CHANGELOG.md:3322 +msgid "" +"For additional security, various capabilities are also dropped (see [why " +"it's important](https://github.com/projectatomic/atomic-site/issues/203))" +" for all containers." +msgstr "" + +#: ../../../CHANGELOG.md:3324 +msgid "" +"Additionally, most containers now use a read-only filesystem (see [why " +"it's important](https://www.projectatomic.io/blog/2015/12/making-docker-" +"images-write-only-in-production/)). Containers are given write access " +"only to the directories they need to write to." +msgstr "" + +#: ../../../CHANGELOG.md:3326 +msgid "" +"A minor breaking change is the " +"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` " +"variable having being renamed to " +"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` " +"(note the `_mb` suffix). The new variable expects a number value (e.g. " +"`25M` -> `25`). If you weren't customizing this variable, this wouldn't " +"affect you." +msgstr "" + +#: ../../../CHANGELOG.md:3328 +msgid "matrix-mailer is now based on Exim, not Postfix" +msgstr "" + +#: ../../../CHANGELOG.md:3330 +msgid "" +"While we would have preferred to stay with " +"[Postfix](http://www.postfix.org/), we found out that it cannot run as a " +"non-root user. We've had to replace it with [Exim](https://www.exim.org/)" +" (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" +"relay) container image)." +msgstr "" + +#: ../../../CHANGELOG.md:3332 +msgid "" +"The internal `matrix-mailer` service (running in a container) now listens" +" on port `8025` (used to be `587` before). The playbook will update your " +"Synapse and mxisd email settings to match (`matrix-mailer:587` -> " +"`matrix-mailer:8025`)." +msgstr "" + +#: ../../../CHANGELOG.md:3334 +msgid "" +"Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" +"relay) container image instead of " +"[panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us " +"a nice disk usage reduction (~200MB -> 8MB)." +msgstr "" + +#: ../../../CHANGELOG.md:3337 +msgid "2019-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:3339 +msgid "(BC Break) Making the playbook's roles more independent of one another" +msgstr "" + +#: ../../../CHANGELOG.md:3341 +msgid "" +"The following change **affects people running a more non-standard setup**" +" - external Postgres or using our roles in their own other playbook. " +"**Most users don't need to do anything**, besides becoming aware of the " +"new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-" +"servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3344 +msgid "" +"Because people like using the playbook's components independently " +"(outside of this playbook) and because it's much better for " +"maintainability, we've continued working on separating them. Still, we'd " +"like to offer a turnkey solution for running a fully-featured Matrix " +"server, so this playbook remains important for wiring up the various " +"components." +msgstr "" + +#: ../../../CHANGELOG.md:3346 +msgid "" +"With the new changes, **all roles are now only dependent on the minimal " +"`matrix-base` role**. They are no longer dependent among themselves." +msgstr "" + +#: ../../../CHANGELOG.md:3348 +msgid "" +"In addition, the following components can now be completely disabled (for" +" those who want/need to):" +msgstr "" + +#: ../../../CHANGELOG.md:3349 +msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3350 +msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3351 +msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3353 +msgid "The following changes had to be done:" +msgstr "" + +#: ../../../CHANGELOG.md:3355 +msgid "" +"glue variables had to be introduced to the playbook, so it can wire " +"together the various components. Those glue vars are stored in the " +"[`group_vars/matrix-servers`](group_vars/matrix-servers) file. When " +"overriding variables for a given component (role), you need to be aware " +"of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's " +"corresponding section in the [`group_vars/matrix-servers`](group_vars" +"/matrix-servers) file." +msgstr "" + +#: ../../../CHANGELOG.md:3357 +msgid "" +"`matrix_postgres_use_external` has been superceeded by the more " +"consistently named `matrix_postgres_enabled` variable and a few other " +"`matrix_synapse_database_` variables. See the [Using an external " +"PostgreSQL server (optional)](docs/configuring-playbook-external-" +"postgres.md) documentation page for an up-to-date replacement." +msgstr "" + +#: ../../../CHANGELOG.md:3359 +msgid "" +"Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are " +"no longer installed if you're not enabling the `matrix-postgres` role " +"(`matrix_postgres_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3361 +msgid "" +"roles, being more independent now, are more minimal and do not do so much" +" magic for you. People that are building their own playbook using our " +"roles will definitely need to take a look at the [`group_vars/matrix-" +"servers`](group_vars/matrix-servers) file and adapt their playbooks with " +"the same (or similar) wiring logic." +msgstr "" + +#: ../../../CHANGELOG.md:3364 +msgid "2019-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:3366 +msgid "Splitting the playbook into multiple roles" +msgstr "" + +#: ../../../CHANGELOG.md:3368 +msgid "" +"For better maintainability, the playbook logic (which all used to reside " +"in a single `matrix-server` role) has been split out into a number of " +"different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, " +"`matrix-mxisd`, etc. (see the `roles/` directory)." +msgstr "" + +#: ../../../CHANGELOG.md:3371 +msgid "" +"To keep the filesystem more consistent with this separation, the " +"**Postgres data had to be relocated**." +msgstr "" + +#: ../../../CHANGELOG.md:3373 +msgid "" +"The default value of `matrix_postgres_data_path` was changed from " +"`/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` " +"directory is what we consider a base path now (new variable " +"`matrix_postgres_base_path`). **Your Postgres data files will " +"automatically be relocated by the playbook** (`/matrix/postgres/*` -> " +"`/matrix/postgres/data/`) when you run with `--tags=setup-all` (or " +"`--tags=setup-postgres`). While this shouldn't cause data-loss, **it's " +"better if you do a Postgres backup just in case**. You'd need to restart " +"all services after this migration (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3376 +msgid "2019-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:3378 +msgid "(BC Break) mxisd configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:3380 +msgid "" +"To be more flexible and to support the upcoming " +"[mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released)," +" we've had to redo how mxisd gets configured." +msgstr "" + +#: ../../../CHANGELOG.md:3383 +msgid "The following variables are no longer supported by this playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:3385 +msgid "`matrix_mxisd_ldap_enabled`" +msgstr "" + +#: ../../../CHANGELOG.md:3386 +msgid "`matrix_mxisd_ldap_connection_host`" +msgstr "" + +#: ../../../CHANGELOG.md:3387 +msgid "`matrix_mxisd_ldap_connection_tls`" +msgstr "" + +#: ../../../CHANGELOG.md:3388 +msgid "`matrix_mxisd_ldap_connection_port`" +msgstr "" + +#: ../../../CHANGELOG.md:3389 +msgid "`matrix_mxisd_ldap_connection_baseDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3390 +msgid "`matrix_mxisd_ldap_connection_baseDns`" +msgstr "" + +#: ../../../CHANGELOG.md:3391 ../../../CHANGELOG.md:3392 +msgid "`matrix_mxisd_ldap_connection_bindDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3393 ../../../CHANGELOG.md:3397 +msgid "`matrix_mxisd_ldap_connection_bindPassword`" +msgstr "" + +#: ../../../CHANGELOG.md:3394 +msgid "`matrix_mxisd_ldap_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3395 +msgid "`matrix_mxisd_ldap_attribute_uid_type`" +msgstr "" + +#: ../../../CHANGELOG.md:3396 +msgid "`matrix_mxisd_ldap_attribute_uid_value`" +msgstr "" + +#: ../../../CHANGELOG.md:3398 +msgid "`matrix_mxisd_ldap_attribute_name`" +msgstr "" + +#: ../../../CHANGELOG.md:3399 +msgid "`matrix_mxisd_ldap_attribute_threepid_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3400 +msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`" +msgstr "" + +#: ../../../CHANGELOG.md:3401 +msgid "`matrix_mxisd_ldap_identity_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3402 +msgid "`matrix_mxisd_ldap_identity_medium`" +msgstr "" + +#: ../../../CHANGELOG.md:3403 +msgid "`matrix_mxisd_ldap_auth_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3404 +msgid "`matrix_mxisd_ldap_directory_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3405 +msgid "`matrix_mxisd_template_config`" +msgstr "" + +#: ../../../CHANGELOG.md:3407 +msgid "" +"You are encouraged to use the `matrix_mxisd_configuration_extension_yaml`" +" variable to define your own mxisd configuration additions and overrides." +" Refer to the [default variables file](roles/custom/matrix-" +"mxisd/defaults/main.yml) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:3409 +msgid "This new way of configuring mxisd is beneficial because:" +msgstr "" + +#: ../../../CHANGELOG.md:3411 +msgid "" +"it lets us support all mxisd configuration options, as the playbook " +"simply forwards them to mxisd without needing to care or understand them" +msgstr "" + +#: ../../../CHANGELOG.md:3412 +msgid "" +"it lets you upgrade to newer mxisd versions and make use of their " +"features, without us having to add support for them explicitly" +msgstr "" + +#: ../../../CHANGELOG.md:3415 +msgid "2019-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:3417 +msgid "(BC Break) Cronjob schedule no longer configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3419 +msgid "" +"Due to the way we manage cronjobs now, you can no longer configure the " +"schedule they're invoked at." +msgstr "" + +#: ../../../CHANGELOG.md:3421 +msgid "" +"If you were previously using " +"`matrix_ssl_lets_encrypt_renew_cron_time_definition` or " +"`matrix_nginx_proxy_reload_cron_time_definition` to set a custom " +"schedule, you should note that these variables don't affect anything " +"anymore." +msgstr "" + +#: ../../../CHANGELOG.md:3424 +msgid "" +"If you miss this functionality, please [open an " +"Issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/new) and let us know about your use case!" +msgstr "" + +#: ../../../CHANGELOG.md:3427 +msgid "2018-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:3429 +msgid "(BC Break) More SSL certificate retrieval methods" +msgstr "" + +#: ../../../CHANGELOG.md:3431 +msgid "" +"The playbook now lets you decide between 3 different SSL certificate " +"retrieval methods:" +msgstr "" + +#: ../../../CHANGELOG.md:3432 +msgid "(default) obtaining free SSL certificates from Let's Encrypt" +msgstr "" + +#: ../../../CHANGELOG.md:3433 +msgid "generating self-signed SSL certificates" +msgstr "" + +#: ../../../CHANGELOG.md:3434 +msgid "managing SSL certificates manually" +msgstr "" + +#: ../../../CHANGELOG.md:3436 +msgid "" +"Learn more in [Adjusting SSL certificate retrieval](docs/configuring-" +"playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3438 +msgid "" +"For people who use Let's Encrypt (mostly everyone, since it's the " +"default), you'll also have to rename a variable in your configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:3440 +msgid "before: `host_specific_matrix_ssl_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3441 +msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3443 +msgid "(BC Break) mxisd upgrade with multiple base DN support" +msgstr "" + +#: ../../../CHANGELOG.md:3445 +msgid "" +"mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-" +"matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base " +"DNs](https://github.com/kamax-" +"matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." +msgstr "" + +#: ../../../CHANGELOG.md:3447 +msgid "" +"If you were configuring this playbook's " +"`matrix_mxisd_ldap_connection_baseDn` variable until now (a string " +"containing a single base DN), you'll need to change to configuring the " +"`matrix_mxisd_ldap_connection_baseDns` variable (an array containing " +"multiple base DNs)." +msgstr "" + +#: ../../../CHANGELOG.md:3449 +msgid "Example change:" +msgstr "" + +#: ../../../CHANGELOG.md:3451 +msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`" +msgstr "" + +#: ../../../CHANGELOG.md:3452 +msgid "" +"after: `matrix_mxisd_ldap_connection_baseDns: " +"['OU=Users,DC=example,DC=org']`" +msgstr "" + +#: ../../../CHANGELOG.md:3455 +msgid "2018-12-21" +msgstr "" + +#: ../../../CHANGELOG.md:3457 +msgid "Synapse 0.34.0 and Python 3" +msgstr "" + +#: ../../../CHANGELOG.md:3459 +msgid "" +"Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on " +"feedback from others, running Synapse on Python 3 is supposed to decrease" +" memory usage significantly (~2x)." +msgstr "" + +#: ../../../CHANGELOG.md:3462 +msgid "2018-12-12" +msgstr "" + +#: ../../../CHANGELOG.md:3464 +msgid "Riot homepage customization" +msgstr "" + +#: ../../../CHANGELOG.md:3466 +msgid "" +"You can now customize some parts of the Riot homepage (or even completely" +" replace it with your own custom page). See the " +"`matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-" +"web/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:3469 +msgid "2018-12-04" +msgstr "" + +#: ../../../CHANGELOG.md:3471 +msgid "mxisd extensibility" +msgstr "" + +#: ../../../CHANGELOG.md:3473 +msgid "" +"The [LDAP identity store for mxisd](https://github.com/kamax-" +"matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured " +"easily using playbook variables (see the `matrix_mxisd_ldap_` variables " +"in `roles/custom/matrix-server/defaults/main.yml`)." +msgstr "" + +#: ../../../CHANGELOG.md:3476 +msgid "2018-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:3478 +msgid "More scripts" +msgstr "" + +#: ../../../CHANGELOG.md:3480 +msgid "matrix-remove-all allows to uninstall everything with a single command" +msgstr "" + +#: ../../../CHANGELOG.md:3481 +msgid "matrix-make-user-admin allows to upgrade a user's privileges" +msgstr "" + +#: ../../../CHANGELOG.md:3483 +msgid "LDAP auth support via matrix-synapse-ldap3" +msgstr "" + +#: ../../../CHANGELOG.md:3485 +msgid "" +"The playbook can now install and configure [LDAP auth " +"support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3487 +msgid "" +"Additional details are available in [Setting up the LDAP authentication " +"password provider module](docs/configuring-playbook-ldap-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3490 +msgid "2018-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:3492 +msgid "Support for controlling public registration and room auto-join" +msgstr "" + +#: ../../../CHANGELOG.md:3494 +msgid "" +"The playbook now lets you enable public registration for users " +"(controlled via `matrix_synapse_enable_registration`). By default, public" +" registration is forbidden." +msgstr "" + +#: ../../../CHANGELOG.md:3496 +msgid "" +"You can also make people automatically get auto-joined to rooms " +"(controlled via `matrix_synapse_auto_join_rooms`)." +msgstr "" + +#: ../../../CHANGELOG.md:3498 +msgid "Support for changing the welcome user ID (welcome bot)" +msgstr "" + +#: ../../../CHANGELOG.md:3500 +msgid "" +"By default, `@riot-bot:matrix.org` is used to welcome newly registered " +"users. This can be changed to something else (or disabled) via the new " +"`matrix_riot_web_welcome_user_id` variable." +msgstr "" + +#: ../../../CHANGELOG.md:3503 +msgid "2018-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:3505 +msgid "Ability to set Synapse log levels" +msgstr "" + +#: ../../../CHANGELOG.md:3507 +msgid "" +"The playbook now allows you to set the log levels used by Synapse. The " +"default logging levels remain the same." +msgstr "" + +#: ../../../CHANGELOG.md:3509 +msgid "" +"You can now override following variables with any of the supported log " +"levels listed here: https://docs.python.org/3/library/logging.html" +"#logging-levels" +msgstr "" + +#: ../../../CHANGELOG.md:3518 +msgid "2018-11-03" +msgstr "" + +#: ../../../CHANGELOG.md:3520 +msgid "Customize parts of Riot's config" +msgstr "" + +#: ../../../CHANGELOG.md:3522 +msgid "" +"You can now customize some parts of Riot's `config.json`. These playbook " +"variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:3533 +msgid "" +"This now allows you use a custom integration manager like " +"[Dimension](https://dimension.t2bot.io). For example, if you wish to use " +"the Dimension instance hosted at dimension.t2bot.io, you can set the " +"following in your vars.yml file:" +msgstr "" + +#: ../../../CHANGELOG.md:3542 +msgid "SSL protocols used to serve Riot and Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3544 +msgid "" +"There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, " +"which controls the SSL protocols used to serve Riot and Synapse. Its " +"default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 " +"TLSv1.1 TLSv1.2` to serve Riot and Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:3546 +msgid "" +"You may wish to reenable TLSv1 if you need to access Riot in older " +"browsers." +msgstr "" + +#: ../../../CHANGELOG.md:3548 +msgid "" +"Note: Currently the dockerized nginx doesn't support TLSv1.3. See " +"https://github.com/nginxinc/docker-nginx/issues/190 for more details." +msgstr "" + +#: ../../../CHANGELOG.md:3551 +msgid "2018-11-01" +msgstr "" + +#: ../../../CHANGELOG.md:3553 +msgid "Postgres 11 support" +msgstr "" + +#: ../../../CHANGELOG.md:3555 +msgid "" +"The playbook now installs [Postgres " +"11](https://www.postgresql.org/about/news/1894/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:3557 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x or 10.x). You can easily upgrade by following the " +"[upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" +"postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646 +#: ../../../CHANGELOG.md:3766 +msgid "(BC Break) Renaming playbook variables" +msgstr "" + +#: ../../../CHANGELOG.md:3561 +msgid "" +"Due to the large amount of features added to this playbook lately, to " +"keep things manageable we've had to reorganize its configuration " +"variables a bit." +msgstr "" + +#: ../../../CHANGELOG.md:3565 +msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3566 +msgid "" +"from `matrix_docker_image_mautrix_telegram` to " +"`matrix_mautrix_telegram_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3567 +msgid "" +"from `matrix_docker_image_mautrix_whatsapp` to " +"`matrix_mautrix_whatsapp_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3568 +msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3569 +msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3570 +msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3571 +msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3572 +msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3573 +msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3574 +msgid "" +"from `matrix_docker_image_postgres_v9` to " +"`matrix_postgres_docker_image_v9`" +msgstr "" + +#: ../../../CHANGELOG.md:3575 +msgid "" +"from `matrix_docker_image_postgres_v10` to " +"`matrix_postgres_docker_image_v10`" +msgstr "" + +#: ../../../CHANGELOG.md:3576 +msgid "" +"from `matrix_docker_image_postgres_latest` to " +"`matrix_postgres_docker_image_latest`" +msgstr "" + +#: ../../../CHANGELOG.md:3579 +msgid "2018-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:3581 +msgid "Mautrix Whatsapp bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3583 +msgid "" +"The playbook now supports bridging with " +"[Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-" +"whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This " +"playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3585 +msgid "" +"Additional details are available in [Setting up Mautrix Whatsapp " +"bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3588 +msgid "2018-10-25" +msgstr "" + +#: ../../../CHANGELOG.md:3590 +msgid "Support for controlling Matrix federation" +msgstr "" + +#: ../../../CHANGELOG.md:3592 +msgid "" +"The playbook can now help you with [Controlling Matrix federation](docs" +"/configuring-playbook-federation), should you wish to run a more private " +"(isolated) server." +msgstr "" + +#: ../../../CHANGELOG.md:3595 +msgid "2018-10-24" +msgstr "" + +#: ../../../CHANGELOG.md:3597 +msgid "Disabling riot-web guests" +msgstr "" + +#: ../../../CHANGELOG.md:3599 +msgid "" +"From now on, Riot's configuration setting `disable_guests` would be set " +"to `true`. The homeserver was rejecting guests anyway, so this is just a " +"cosmetic change affecting Riot's UI." +msgstr "" + +#: ../../../CHANGELOG.md:3602 +msgid "2018-10-21" +msgstr "" + +#: ../../../CHANGELOG.md:3604 +msgid "Self-check maintenance command" +msgstr "" + +#: ../../../CHANGELOG.md:3606 +msgid "" +"The playbook can now [check if services are configured correctly](docs" +"/maintenance-checking-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3609 +msgid "2018-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:3611 +msgid "Presence tracking made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3613 +msgid "" +"The playbook can now enable/disable user presence-status tracking in " +"Synapse, through the playbook's `matrix_synapse_use_presence` variable " +"(having a default value of `true` - enabled)." +msgstr "" + +#: ../../../CHANGELOG.md:3615 +msgid "" +"If users participate in large rooms with many other servers, disabling " +"presence will decrease server load significantly." +msgstr "" + +#: ../../../CHANGELOG.md:3618 +msgid "2018-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:3620 +msgid "Synapse Cache Factor made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3622 +msgid "" +"The playbook now makes the Synapse cache factor configurable, through the" +" playbook's `matrix_synapse_cache_factor` variable (having a default " +"value of `0.5`)." +msgstr "" + +#: ../../../CHANGELOG.md:3624 +msgid "" +"Changing that value allows you to potentially decrease RAM usage or to " +"increase performance by caching more stuff. Some information on it is " +"available here: https://github.com/element-hq/synapse#help-synapse-eats-" +"all-my-ram" +msgstr "" + +#: ../../../CHANGELOG.md:3627 +msgid "2018-09-26" +msgstr "" + +#: ../../../CHANGELOG.md:3629 +msgid "Disabling Docker container logging" +msgstr "" + +#: ../../../CHANGELOG.md:3631 +msgid "`--log-driver=none` is used for all Docker containers now." +msgstr "" + +#: ../../../CHANGELOG.md:3633 +msgid "" +"All these containers are started through systemd anyway and get logged in" +" journald, so there's no need for Docker to be logging the same thing " +"using the default `json-file` driver. Doing that was growing " +"`/var/lib/docker/containers/..` infinitely until service/container " +"restart." +msgstr "" + +#: ../../../CHANGELOG.md:3635 +msgid "" +"As a result of this, things like `docker logs matrix-synapse` won't work " +"anymore. `journalctl -u matrix-synapse` is how one can see the logs." +msgstr "" + +#: ../../../CHANGELOG.md:3638 +msgid "2018-09-17" +msgstr "" + +#: ../../../CHANGELOG.md:3640 +msgid "Service discovery support" +msgstr "" + +#: ../../../CHANGELOG.md:3642 +msgid "" +"The playbook now helps you set up [service " +"discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-" +"discovery) using a `/.well-known/matrix/client` file." +msgstr "" + +#: ../../../CHANGELOG.md:3644 +msgid "" +"Additional details are available in [Configuring service discovery via " +".well-known](docs/configuring-well-known.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3650 +msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" +msgstr "" + +#: ../../../CHANGELOG.md:3651 +msgid "" +"from `matrix_riot_web_default_identity_server_url` to " +"`matrix_identity_server_url`" +msgstr "" + +#: ../../../CHANGELOG.md:3654 +msgid "2018-09-07" +msgstr "" + +#: ../../../CHANGELOG.md:3656 +msgid "Mautrix Telegram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3658 +msgid "" +"The playbook now supports bridging with [Telegram](https://telegram.org/)" +" by installing the [mautrix-telegram](https://github.com/tulir/mautrix-" +"telegram) bridge. This playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3660 +msgid "" +"Additional details are available in [Setting up Mautrix Telegram " +"bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3662 +msgid "Events cache size increase and configurability for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3664 +msgid "" +"The playbook now lets you configure Matrix Synapse's `event_cache_size` " +"configuration via the `matrix_synapse_event_cache_size` playbook " +"variable." +msgstr "" + +#: ../../../CHANGELOG.md:3666 +msgid "" +"Previously, this value was hardcoded to `\"10K\"`. From now on, a more " +"reasonable default of `\"100K\"` is used." +msgstr "" + +#: ../../../CHANGELOG.md:3668 +msgid "Password-peppering support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3670 +msgid "" +"The playbook now supports enabling password-peppering for increased " +"security in Matrix Synapse via the " +"`matrix_synapse_password_config_pepper` playbook variable. Using a " +"password pepper is disabled by default (just like it used to be before " +"this playbook variable got introduced) and is not to be enabled/disabled " +"after initial setup, as that would invalidate all existing passwords." +msgstr "" + +#: ../../../CHANGELOG.md:3672 +msgid "Statistics-reporting support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3674 +msgid "" +"There's now a new `matrix_synapse_report_stats` playbook variable, which " +"controls the `report_stats` configuration option for Matrix Synapse. It " +"defaults to `false`, so no change is required to retain your privacy." +msgstr "" + +#: ../../../CHANGELOG.md:3676 +msgid "" +"If you'd like to start reporting statistics about your homeserver (things" +" like number of users, number of messages sent, uptime, load, etc.) to " +"matrix.org, you can turn on stats reporting." +msgstr "" + +#: ../../../CHANGELOG.md:3679 +msgid "2018-08-29" +msgstr "" + +#: ../../../CHANGELOG.md:3681 +msgid "Changing the way SSL certificates are retrieved" +msgstr "" + +#: ../../../CHANGELOG.md:3683 +msgid "" +"We've been using [acmetool](https://github.com/hlandau/acme) (with the " +"[willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) " +"Docker image) until now." +msgstr "" + +#: ../../../CHANGELOG.md:3685 +msgid "" +"Due to the Docker image being deprecated, and things looking bleak for " +"acmetool's support of the newer ACME v2 API endpoint, we've switched to " +"using [certbot](https://certbot.eff.org/) (with the " +"[certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker " +"image)." +msgstr "" + +#: ../../../CHANGELOG.md:3687 +msgid "" +"Simply re-running the playbook will retrieve new certificates (via " +"certbot) for you. To ensure you don't leave any old files behind, though," +" you'd better do this:" +msgstr "" + +#: ../../../CHANGELOG.md:3689 +msgid "`systemctl stop 'matrix*'`" +msgstr "" + +#: ../../../CHANGELOG.md:3690 +msgid "" +"stop your custom webserver, if you're running one (only affects you if " +"you've installed with `matrix_nginx_proxy_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3691 +msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3692 +msgid "re-run the playbook's [installation](docs/installing.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3693 +msgid "possibly delete `/matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3696 +msgid "2018-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:3698 +msgid "Matrix Corporal support" +msgstr "" + +#: ../../../CHANGELOG.md:3700 +msgid "" +"The playbook can now install and configure [matrix-" +"corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3702 +msgid "" +"Additional details are available in [Setting up Matrix Corporal](docs" +"/configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3705 +msgid "2018-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:3707 +msgid "Matrix Synapse rate limit control variables" +msgstr "" + +#: ../../../CHANGELOG.md:3709 +msgid "" +"The following new variables can now be configured to control Matrix " +"Synapse's rate-limiting (default values are shown below)." +msgstr "" + +#: ../../../CHANGELOG.md:3716 +msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3718 +msgid "" +"The playbook can now install and configure [matrix-synapse-shared-secret-" +"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:3720 +msgid "" +"Additional details are available in [Setting up the Shared Secret Auth " +"password provider module](docs/configuring-playbook-shared-secret-" +"auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3723 +msgid "2018-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:3725 +msgid "REST auth support via matrix-synapse-rest-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3727 +msgid "" +"The playbook can now install and configure [matrix-synapse-rest-" +"auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3729 +msgid "" +"Additional details are available in [Setting up the REST authentication " +"password provider module](docs/configuring-playbook-rest-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3731 +msgid "Compression improvements" +msgstr "" + +#: ../../../CHANGELOG.md:3733 +msgid "" +"Shifted Matrix Synapse compression from happening in the Matrix Synapse, " +"to happening in the nginx proxy that's in front of it." +msgstr "" + +#: ../../../CHANGELOG.md:3736 +msgid "" +"Additionally, `riot-web` also gets compressed now (in the nginx proxy), " +"which drops the initial page load's size from 5.31MB to 1.86MB." +msgstr "" + +#: ../../../CHANGELOG.md:3739 +msgid "Disabling some unnecessary Synapse services" +msgstr "" + +#: ../../../CHANGELOG.md:3741 +msgid "The following services are not necessary, so they have been disabled:" +msgstr "" + +#: ../../../CHANGELOG.md:3742 +msgid "on the federation port (8448): the `client` service" +msgstr "" + +#: ../../../CHANGELOG.md:3743 +msgid "" +"on the http port (8008, exposed over 443): the old Angular `webclient` " +"and the `federation` service" +msgstr "" + +#: ../../../CHANGELOG.md:3745 +msgid "" +"Federation runs only on the federation port (8448) now. The Client APIs " +"run only on the http port (8008) now." +msgstr "" + +#: ../../../CHANGELOG.md:3748 +msgid "2018-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:3750 +msgid "mxisd Identity Server support" +msgstr "" + +#: ../../../CHANGELOG.md:3752 +msgid "" +"The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) " +"Identity Server for you by default. Additional details are available in " +"[Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3755 +msgid "2018-08-14" +msgstr "" + +#: ../../../CHANGELOG.md:3757 +msgid "Email-sending support" +msgstr "" + +#: ../../../CHANGELOG.md:3759 +msgid "" +"The playbook now configures an email-sending service (postfix) by " +"default. Additional details are available in [Adjusting email-sending " +"settings](docs/configuring-playbook-email.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3761 +msgid "" +"With this, Matrix Synapse is able to send email notifications for missed " +"messages, etc." +msgstr "" + +#: ../../../CHANGELOG.md:3764 +msgid "2018-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:3770 +msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3771 +msgid "" +"from `matrix_max_log_file_size_mb` to " +"`matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3772 +msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:3773 +msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:3774 +msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`" +msgstr "" + +#: ../../../CHANGELOG.md:3775 +msgid "from `docker_riot_image` to `matrix_docker_image_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3776 +msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`" +msgstr "" + +#: ../../../CHANGELOG.md:3777 +msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" +msgstr "" + +#: ../../../CHANGELOG.md:3779 +msgid "" +"If you're overriding any of them in your `vars.yml` file, you'd need to " +"change to the new names." +msgstr "" + +#: ../../../CHANGELOG.md:3781 +msgid "Renaming Ansible playbook tag" +msgstr "" + +#: ../../../CHANGELOG.md:3783 +msgid "" +"The command for executing the whole playbook has changed. The `setup-" +"main` tag got renamed to `setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:3785 +msgid "Docker container linking" +msgstr "" + +#: ../../../CHANGELOG.md:3787 +msgid "" +"Changed the way the Docker containers are linked together. The ones that " +"need to communicate with others operate in a `matrix` network now and not" +" in the default bridge network." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/README.po b/i18n/locales/bg/LC_MESSAGES/README.po new file mode 100644 index 000000000..9ac7e37f0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/README.po @@ -0,0 +1,1374 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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" + +#: ../../../README.md:1 +msgid "" +"[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-" +"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" +"deploy%3Adevture.com&logo=matrix&style=for-the-" +"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" +"docker-ansible-deploy:devture.com) " +"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgstr "" + +#: ../../../README.md:1 +msgid "Support room on Matrix" +msgstr "" + +#: ../../../README.md:1 +msgid "donate" +msgstr "" + +#: ../../../README.md:3 +msgid "" +"Matrix (An open network for secure, decentralized communication) server " +"setup using Ansible and Docker" +msgstr "" + +#: ../../../README.md:5 +msgid "🎯 Purpose" +msgstr "" + +#: ../../../README.md:7 +msgid "" +"This [Ansible](https://www.ansible.com/) playbook is meant to help you " +"run your own [Matrix](http://matrix.org/) homeserver, along with the " +"[various services](#supported-services) related to that." +msgstr "Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#supported-services), свързани с това." + +#: ../../../README.md:9 +msgid "" +"That is, it lets you join the Matrix network using your own user ID like " +"`@alice:example.com`, all hosted on your own server (see " +"[prerequisites](docs/prerequisites.md))." +msgstr "" + +#: ../../../README.md:11 +msgid "" +"We run all [supported services](#-supported-services) in " +"[Docker](https://www.docker.com/) containers (see [the container images " +"we use](docs/container-images.md)), which lets us have a predictable and " +"up-to-date setup, across multiple supported distros (see " +"[prerequisites](docs/prerequisites.md)) and [architectures](docs" +"/alternative-architectures.md) (x86/amd64 being recommended)." +msgstr "" + +#: ../../../README.md:13 +msgid "" +"Installation (upgrades) and some maintenance tasks are automated using " +"[Ansible](https://www.ansible.com/) (see [our Ansible " +"guide](docs/ansible.md))." +msgstr "" + +#: ../../../README.md:15 +msgid "☁ Self-hosting or Managed / SaaS" +msgstr "" + +#: ../../../README.md:17 +msgid "" +"This Ansible playbook tries to make self-hosting and maintaining a Matrix" +" server fairly easy (see [Getting started](#-getting-started)). Still, " +"running any service smoothly requires knowledge, time and effort." +msgstr "" + +#: ../../../README.md:19 +msgid "" +"If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" +"source_software) spirit of this Ansible playbook, but prefer to put the " +"responsibility on someone else, you can also [get a managed Matrix server" +" from " +"etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" (both hosting and on-premises) - a service built on top of this Ansible " +"playbook but with [additional " +"components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" and " +"[services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" which all help you run a Matrix server with ease. Be advised that " +"etke.cc operates on a subscription-based approach and there is no \"just " +"set up my server once and be done with it\" option." +msgstr "" + +#: ../../../README.md:21 +msgid "🚀 Getting started" +msgstr "" + +#: ../../../README.md:23 +msgid "" +"We have detailed documentation in the [docs/](./docs) directory - see the" +" Table of Contents in the [documentation README](./docs/README.md)." +msgstr "" + +#: ../../../README.md:25 +msgid "" +"While the [list of supported services](#-supported-services) and " +"documentation is very extensive, you don't need to read through " +"everything. We recommend:" +msgstr "" + +#: ../../../README.md:27 +msgid "" +"Starting with the basics. You can always add/remove or tweak services " +"later on." +msgstr "" + +#: ../../../README.md:29 +msgid "" +"Following our installation guide. There are two guides available for " +"beginners and advanced users:" +msgstr "" + +#: ../../../README.md:31 +msgid "" +"⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is " +"recommended for those who do not have an existing Matrix server and want " +"to start quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../README.md:33 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide by starting with the " +"**[Prerequisites](./docs/prerequisites.md)** documentation page." +msgstr "" + +#: ../../../README.md:35 +msgid "" +"If you experience an issue on configuring the playbook, setting up your " +"server, maintaining services on it, etc., please take a look at our " +"[FAQ](./docs/faq.md). If you cannot find an answer to your question, feel" +" free to ask for [help and support](#-support)." +msgstr "" + +#: ../../../README.md:37 +msgid "✔ Supported services" +msgstr "" + +#: ../../../README.md:39 +msgid "" +"Using this playbook, you can get the following list of services " +"configured on your server. Basically, this playbook aims to get you up-" +"and-running with all the necessities around Matrix, without you having to" +" do anything else." +msgstr "" + +#: ../../../README.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../README.md:43 +msgid "" +"The list below is exhaustive. It includes optional or even some advanced " +"components that you will most likely not need. Sticking with the defaults" +" (which install a subset of the above components) is the best choice, " +"especially for a new installation. You can always re-run the playbook " +"later to add or remove components." +msgstr "" + +#: ../../../README.md:45 +msgid "" +"Deprecated or unmaintained services are not listed. You can find " +"documentations for them [here](docs/configuring-playbook.md#deprecated--" +"unmaintained--removed-services)." +msgstr "" + +#: ../../../README.md:47 +msgid "Homeserver" +msgstr "" + +#: ../../../README.md:49 +msgid "" +"The homeserver is the backbone of your Matrix system. Choose one from the" +" following list." +msgstr "" + +#: ../../../README.md +msgid "Name" +msgstr "" + +#: ../../../README.md +msgid "Default?" +msgstr "" + +#: ../../../README.md +msgid "Description" +msgstr "" + +#: ../../../README.md +msgid "Documentation" +msgstr "" + +#: ../../../README.md +msgid "[Synapse](https://github.com/element-hq/synapse)" +msgstr "" + +#: ../../../README.md +msgid "✅" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../README.md +msgid "[Conduit](https://conduit.rs)" +msgstr "" + +#: ../../../README.md +msgid "❌" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" +"source server implementation of the Matrix Specification with a focus on " +"easy setup and low system requirements" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../README.md +msgid "[Dendrite](https://github.com/matrix-org/dendrite)" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " +"Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../README.md:57 +msgid "Clients" +msgstr "" + +#: ../../../README.md:59 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../README.md +msgid "[Element Web](https://github.com/element-hq/element-web)" +msgstr "" + +#: ../../../README.md +msgid "" +"Default Matrix web client, configured to connect to your own Synapse " +"server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../README.md +msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../README.md +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../README.md +msgid "[Cinny](https://github.com/ajbura/cinny)" +msgstr "" + +#: ../../../README.md +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../README.md +msgid "[SchildiChat Web](https://schildi.chat/)" +msgstr "" + +#: ../../../README.md +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../README.md:68 +msgid "Server Components" +msgstr "" + +#: ../../../README.md:70 +msgid "" +"Services that run on the server to make the various parts of your " +"installation work." +msgstr "" + +#: ../../../README.md +msgid "[PostgreSQL](https://www.postgresql.org/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Database for Synapse. [Using an external PostgreSQL server](docs" +"/configuring-playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../README.md +msgid "[Coturn](https://github.com/coturn/coturn)" +msgstr "" + +#: ../../../README.md +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-turn.md)" +msgstr "" + +#: ../../../README.md +msgid "[Traefik](https://doc.traefik.io/traefik/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Web server, listening on ports 80, 443 and 8448 - standing in front of " +"all the other services. Using your own webserver [is possible](docs" +"/configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../README.md +msgid "[Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../README.md +msgid "Free SSL certificate, which secures the connection to all components" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../README.md +msgid "[Exim](https://www.exim.org/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Mail server, through which all Matrix services send outgoing email (can " +"be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-email.md)" +msgstr "" + +#: ../../../README.md +msgid "[ma1sd](https://github.com/ma1uta/ma1sd)" +msgstr "" + +#: ../../../README.md +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../README.md +msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)" +msgstr "" + +#: ../../../README.md +msgid "Dynamic DNS" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../README.md:82 +msgid "Authentication" +msgstr "" + +#: ../../../README.md:84 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-" +"password-provider) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-" +"synapse-shared-secret-auth) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "Password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-" +"ldap3) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ldap-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" (advanced)" +msgstr "" + +#: ../../../README.md +msgid "" +"A proxy that handles Matrix registration requests and forwards them to " +"LDAP." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)" +msgstr "" + +#: ../../../README.md +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Matrix User Verification Service](https://github.com/matrix-org/matrix-" +"user-verification-service) (UVS)" +msgstr "" + +#: ../../../README.md +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-user-verification-service.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" +"antispam) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "A spam checker module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)" +msgstr "" + +#: ../../../README.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../README.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../README.md +msgid "[Goofys](https://github.com/kahing/goofys)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " +"store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" +"-storage-provider)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-s3.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)" +msgstr "" + +#: ../../../README.md +msgid "" +"matrix-media-repo is a highly customizable multi-domain media repository " +"for Matrix. Intended for medium to large deployments, this media repo de-" +"duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../README.md:106 +msgid "Bridges" +msgstr "" + +#: ../../../README.md:108 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../README.md +msgid "[mautrix-discord](https://github.com/mautrix/discord)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-slack](https://github.com/mautrix/slack)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-telegram](https://github.com/mautrix/telegram)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-twitter](https://github.com/mautrix/twitter)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-meta](https://github.com/mautrix/instagram)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge to [Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-" +"messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-" +"meta-instagram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-signal](https://github.com/mautrix/signal)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../README.md +msgid "[beeper-linkedin](https://github.com/beeper/linkedin)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-" +"irc)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-discord](https://github.com/matrix-org/matrix-" +"appservice-discord)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-slack](https://github.com/matrix-org/matrix-" +"appservice-slack)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge for generic webhooks and multiple project management services, " +"such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to SMS" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../README.md +msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bouncer-style bridge to " +"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../README.md +msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-" +"discord)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-" +"groupme)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../README.md +msgid "[Email2Matrix](https://github.com/devture/email2matrix)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../README.md +msgid "[Postmoogle](https://github.com/etkecc/postmoogle)" +msgstr "" + +#: ../../../README.md +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../README.md:141 +msgid "Bots" +msgstr "" + +#: ../../../README.md:143 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../README.md +msgid "[baibot](https://github.com/etkecc/baibot)" +msgstr "" + +#: ../../../README.md +msgid "" +"A bot that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-" +"bot)" +msgstr "" + +#: ../../../README.md +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-registration-bot](https://github.com/moan0s/matrix-registration-" +"bot)" +msgstr "" + +#: ../../../README.md +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../README.md +msgid "[maubot](https://github.com/maubot/maubot)" +msgstr "" + +#: ../../../README.md +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../README.md +msgid "[Honoroit](https://github.com/etkecc/honoroit)" +msgstr "" + +#: ../../../README.md +msgid "A helpdesk bot" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../README.md +msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)" +msgstr "" + +#: ../../../README.md +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../README.md +msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)" +msgstr "" + +#: ../../../README.md +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice " +"mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" +msgstr "" + +#: ../../../README.md +msgid "[Buscarron](https://github.com/etkecc/buscarron)" +msgstr "" + +#: ../../../README.md +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../README.md:156 +msgid "Administration" +msgstr "" + +#: ../../../README.md:158 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-alertmanager-receiver](https://github.com/metio/matrix-" +"alertmanager-receiver)" +msgstr "" + +#: ../../../README.md +msgid "" +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " +"client" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Matrix Authentication Service](https://github.com/element-hq/matrix-" +"authentication-service/)" +msgstr "" + +#: ../../../README.md +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)" +msgstr "" + +#: ../../../README.md +msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)" +msgstr "" + +#: ../../../README.md +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../README.md +msgid "Metrics and Graphs" +msgstr "" + +#: ../../../README.md +msgid "" +"Consists of the [Prometheus](https://prometheus.io) time-series database " +"server, the Prometheus [node-exporter](https://prometheus.io/docs/guides" +"/node-exporter/) host metrics exporter, and the " +"[Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-" +"exporter](https://github.com/martin-helmich/prometheus-nginxlog-" +"exporter/) being available too" +msgstr "" + +#: ../../../README.md +msgid "" +"[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-" +"nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" +msgstr "" + +#: ../../../README.md +msgid "[Borg](https://borgbackup.org)" +msgstr "" + +#: ../../../README.md +msgid "Backups" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../README.md +msgid "[rageshake](https://github.com/matrix-org/rageshake)" +msgstr "" + +#: ../../../README.md +msgid "Bug report server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" +"exporter)" +msgstr "" + +#: ../../../README.md +msgid "" +"Export the usage statistics of a Synapse homeserver to be scraped by " +"Prometheus." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../README.md:170 +msgid "Misc" +msgstr "" + +#: ../../../README.md:172 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../README.md +msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../README.md +msgid "" +"(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` " +"and Conduit > `0.6.0`) Sliding Sync support for clients which require it " +"(e.g. old Element X versions before Simplified Sliding Sync was " +"developed)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-" +"accept-invite)" +msgstr "" + +#: ../../../README.md +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" +"compress-state/#automated-tool-synapse_auto_compressor)" +msgstr "" + +#: ../../../README.md +msgid "" +"A cli tool that automatically compresses `state_groups` database table in" +" background." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../README.md +msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-corporal.md)" +msgstr "" + +#: ../../../README.md +msgid "[Etherpad](https://etherpad.org)" +msgstr "" + +#: ../../../README.md +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../README.md +msgid "[Jitsi](https://jitsi.org/)" +msgstr "" + +#: ../../../README.md +msgid "An open source video-conferencing platform" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../README.md +msgid "[Cactus Comments](https://cactus.chat)" +msgstr "" + +#: ../../../README.md +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../README.md +msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)" +msgstr "" + +#: ../../../README.md +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../README.md +msgid "[Sygnal](https://github.com/matrix-org/sygnal)" +msgstr "" + +#: ../../../README.md +msgid "Push gateway" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../README.md +msgid "[ntfy](https://ntfy.sh)" +msgstr "" + +#: ../../../README.md +msgid "Push notifications server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../README.md:187 +msgid "🆕 Changes" +msgstr "" + +#: ../../../README.md:189 +msgid "" +"This playbook evolves over time, sometimes with backward-incompatible " +"changes." +msgstr "" + +#: ../../../README.md:191 +msgid "" +"When updating the playbook, refer to [the changelog](CHANGELOG.md) to " +"catch up with what's new." +msgstr "" + +#: ../../../README.md:193 +msgid "🆘 Support" +msgstr "" + +#: ../../../README.md:195 +msgid "" +"Matrix room: [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com)" +msgstr "" + +#: ../../../README.md:197 +msgid "" +"IRC channel: `#matrix-docker-ansible-deploy` on the [Libera " +"Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" +msgstr "" + +#: ../../../README.md:199 +msgid "" +"GitHub issues: [spantaleev/matrix-docker-ansible-" +"deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues)" +msgstr "" + +#: ../../../README.md:215 +msgid "🤝 Related" +msgstr "" + +#: ../../../README.md:217 +msgid "" +"You may also be interested in [mash-playbook](https://github.com/mother-" +"of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" +"hosting non-Matrix services (see its [List of supported " +"services](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/supported-services.md))." +msgstr "" + +#: ../../../README.md:219 +msgid "" +"mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" +"traefik.md) as its reverse-proxy, so with minor [interoperability " +"adjustments](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/interoperability.md), you can make matrix-docker-" +"ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " +"services on the same server." +msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po new file mode 100644 index 000000000..4fa9a26bd --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -0,0 +1,679 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../YEAR-IN-REVIEW.md:1 +msgid "2023" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:3 +msgid "" +"2023 was a year filled with many changes for matrix-docker-ansible-" +"deploy. In this post, we're looking backward at some of the major changes" +" that happened this year, as well as taking a glimpse of what's ahead in " +"2024." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:5 +msgid "" +"2023 is probably [the year of AI](https://journal.everypixel.com/2023" +"-the-year-of-ai), with millions of people jumping aboard " +"[OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) " +"train. matrix-docker-ansible-deploy is no stranger to this and 2023 began" +" with a PR from [bertybuttface](https://github.com/bertybuttface) who " +"added support for [matrix-chatgpt-bot](https://github.com/matrixgpt" +"/matrix-chatgpt-bot) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#chatgpt-support)). While OpenAI's chat GPT website was frequently " +"overloaded in the past, their API was up which made using this bot both " +"convenient and more reliable." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:7 +msgid "" +"AI aside, with the playbook's focus being containers, we're **doubling " +"down on being \"container native\"** and becoming more interoperable for " +"people hosting other containers on the Matrix server. In " +"[2022](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-" +"REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their " +"use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of " +"matrix-docker-ansible-deploy also switching to this reverse-proxy. This " +"prediction materialized quickly. The **largest change** in the playbook " +"in 2023 happened way back in February - matrix-docker-ansible-deploy " +"[starting the switch from nginx to Traefik](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#backward-compatibility-reverse-proxy-configuration-changes-and-initial-" +"traefik-support) and then quickly [making Treafik the default reverse-" +"proxy](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#traefik-is-the-default-reverse-proxy-now). As noted in the changelog " +"entries, we envisioned a quick and complete elimination of `matrix-nginx-" +"proxy`, but at the end of 2023, it hasn't happened yet. The playbook is " +"already using Traefik as the front-most reverse-proxy, but nginx (via " +"`matrix-nginx-proxy`) is still around - it has taken a step back and is " +"only used internally for new setups. Work got to a stall due to:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:9 +msgid "" +"complexity: untangling the overly large and messy `matrix-nginx-proxy` " +"component is difficult" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:10 +msgid "" +"the current setup became \"good enough\" because nginx has become an " +"internal implementation detail for those who have migrated to Traefik. " +"Traefik is already the default public reverse-proxy and gives better " +"possibilities to people wishing to run other web-exposed containers on " +"their Matrix server via [Docker " +"Compose](https://docs.docker.com/compose/), other Ansible playbooks like " +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) (more about this one, below) or any other way." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:12 +msgid "" +"`matrix-nginx-proxy` is no longer in the way of us being interoperable, " +"but its ugly internal details are still there. It is one more proxy in " +"the long chain of reverse-proxies we have and we'd like to cut it out. " +"This would both make things simpler and also boost performance." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:14 +msgid "" +"The delay in eliminating `matrix-nginx-proxy` has probably been welcome " +"by many existing users who decided to postpone the Traefik migration a " +"bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will " +"continue with rapid pace. People who are still using `matrix-nginx-proxy`" +" as their front-most reverse-proxy will need to rework their setup. About" +" a year of putting it off has been long enough." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:16 +msgid "" +"This large Traefik reverse-proxy change was also accompanied by another " +"internal change which began in 2022, but continued in 2023 - **moving " +"non-Matrix-related roles from being internal to the playbook to living " +"their own life outside of it**. Various roles were made more decoupled " +"and moved outside of the playbook, so that other projects (like the " +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) Ansible playbook or other Ansible playbooks) could benefit from" +" them. This led to the **death of a few sibling playbooks** ([gitea-" +"docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy), [nextcloud-docker-ansible-" +"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), " +"[peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-" +"docker-ansible-deploy), [vaultwarden-docker-ansible-" +"deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-" +"deploy)), but brought life to something better, which supports all these " +"services and more." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:18 +msgid "" +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) is a new Ansible playbook that a few of us (matrix-docker-" +"ansible-deploy contributors) have launched in 2023. It has quickly grown " +"to supports [60+ services](https://github.com/mother-of-all-self-hosting" +"/mash-playbook/blob/main/docs/supported-services.md) and aims to do the " +"same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" +"source_software) service hosting, as matrix-docker-ansible-deploy has " +"done for Matrix - providing a clean and secure way to run a bunch of " +"services in containers on a regular server (that is to say, without " +"Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to" +" host both mash-playbook services and matrix-docker-ansible-deploy " +"services on the same server - see mash-playbook's " +"[interoperability](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/interoperability.md) documentation page. If " +"you've been looking for a holiday project or your New Year's Resolutions " +"list contains \"self-hosting more services\", then you're welcome to give" +" this new playbook a try and join its Matrix room ([#mash-" +"playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:20 +msgid "" +"Because many of the roles are now external to this playbook (defined in " +"the [requirements.yml](https://github.com/spantaleev/matrix-docker-" +"ansible-" +"deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) " +"file), running `make roles` (or better yet `just roles` via the [just " +"tool](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#support-for-running-commands-via-just)) becomes a necessity each time " +"one pulls playbook updates (`git pull`). Pulling external roles happens " +"via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli" +"/ansible-galaxy.html) command-line tool, but if available, the playbook " +"would also use the much faster [agru](https://github.com/etkecc/agru) " +"tool (developed by [Aine](https://gitlab.com/etke.cc) from " +"[etke.cc](https://etke.cc/) this year)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:22 +msgid "" +"With the internal (but important) details out of the way, we can now talk" +" more about **new features that landed in matrix-docker-ansible-deploy in" +" 2023**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:24 +msgid "The following **new** **bridges** were added to the playbook in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:26 +msgid "" +"(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a " +"PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#mautrix-slack-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:27 +msgid "" +"(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), " +"thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#mautrix-gmessages-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:28 +msgid "" +"(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for " +"Apple iMessage bridging (when combined with the [mautrix-" +"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" +" or Android phone), thanks to a PR by [Johan " +"Swetzén](https://github.com/jswetzen)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:30 +msgid "" +"This brings the total number of **[bridges that the playbook " +"supports](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-" +"playbook.md#bridging-other-networks) up to 30**. There are alternative " +"bridge implementations for various networks and protocols, so the number " +"of \"unique bridged networks\" is surely much smaller." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:32 +msgid "A few other **major components and changes** landed in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:34 +msgid "" +"(2023-02-10) The [Draupnir](https://github.com/the-draupnir-" +"project/Draupnir) moderation tool (successor to " +"[Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by " +"[FSG-Cat](https://github.com/FSG-Cat) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#draupnir-moderation-tool-bot-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:35 +msgid "" +"(2023-02-10) [Matrix User Verification Service](https://github.com" +"/matrix-org/matrix-user-verification-service) to add Matrix " +"Authentication Support to our Jitsi setup, thanks to a PR by [Jakob " +"S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com" +"/zakk-it) (see the [changelog entry](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" +"authentication-support-for-jitsi))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:36 +msgid "" +"(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug" +" report server, thanks to a PR by [Benjamin " +"Kampmann](https://github.com/gnunicorn) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#rageshake-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:37 +msgid "" +"(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-" +"sync) (currently a necessary component for [Element " +"X](https://element.io/labs/element-x) to work), thanks to: [Benjamin " +"Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com" +"/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#sliding-sync-proxy-element-x-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:38 +msgid "" +"(2023-03-12) synapse-auto-compressor to periodically and automatically " +"run [rust-synapse-compress-state](https://github.com/matrix-org/rust-" +"synapse-compress-state), thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#synapse-auto-compressor-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:39 +msgid "" +"(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-" +"media-repo),  thanks to a PR by [Michael Hollister](https://github.com" +"/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of " +"the [Circles app](https://circu.li/) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" +"media-repo-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:40 +msgid "" +"(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat" +"/schildichat-desktop) client app (fork of [Element " +"Web)](https://github.com/element-hq/element-web), thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#schildichat-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:41 +msgid "" +"(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#postgres-parameters-are-automatically-tuned-now))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:42 +msgid "" +"(2023-10-23) Enabling federation of the room directory for Synapse (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:44 +msgid "" +"The most recent change in the list above (Enabling federation of the room" +" directory for Synapse) has been somewhat **controversial** as it goes " +"against upstream defaults for Synapse. Nevertheless, we believe it " +"**promotes the well-being of the Matrix Federation by improving room " +"discovery**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:46 +msgid "" +"**Matrix Federation Stats** (containing the percentage of servers " +"publishing their room directory publicly) are posted to " +"[TWIM](https://matrix.org/category/this-week-in-matrix/) each week by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The " +"number of servers which [currently published their room directory " +"publicly](https://matrix.org/blog/2023/12/2/this-week-in-" +"matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:48 +msgid "" +"**2.4% more** than when it was when [first published to " +"TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03" +"/#matrix-federation-stats) (1 month earlier, in November)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:49 +msgid "" +"likely about **15+% more** than from before we flipped the switch (in " +"October)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:51 +msgid "" +"Hopefully, Synapse defaults would also change the same way and we'd see " +"the number of servers publicly listing their room directory grow faster." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:53 +msgid "" +"With this configuration change in place, projects like " +"[MatrixRooms.info](https://matrixrooms.info/) (made by " +"[etke.cc](https://etke.cc/)) and potentially others in the future, can " +"discover, index the metadata (room address, title, topic, number of " +"users, etc.) and make public rooms browsable & searchable across the " +"whole Matrix Federation. It'd be great if users joining Matrix could more" +" easily find interesting communities that match their interests!" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:55 +msgid "" +"On the **media side of things**, besides Jitsi getting better Matrix " +"integration (via the aforementioned Matrix User Verification Service), " +"we've also had some [Coturn security " +"tightening](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#backward-compatibility-tightening-coturn-security-can-lead-to-" +"connectivity-issues) as well as [performance " +"optimizations](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-" +"can-now-use-host-networking) for configurations exposing lots of network " +"ports." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:57 +msgid "" +"[Element Call](https://github.com/element-hq/element-call) seems to have " +"become a nice and polished product lately (as proclaimed in [The Matrix " +"Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-" +"holiday-update-2023/)), so 2024 is likely the year we'll see support for " +"it in the playbook. Element Call depends on the " +"[LiveKit](https://livekit.io/) streaming server (which is also useful to " +"developers even by itself), so the first step is likely to see LiveKit " +"support in mash-playbook via a reusable Ansible role. Such a LiveKit " +"Ansible role could later easily land in matrix-docker-ansible-deploy and " +"an Element Call static website could be hooked to it." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:59 +msgid "" +"Besides these highlights, there were many other relatively large changes " +"announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-" +"ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and " +"hundreds of other more minor (but still important) playbook changes that " +"didn't get a mention." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:61 +msgid "" +"We have **hundreds of contributors to thank for their hard work** on " +"making Matrix self-hosting better for all of us! It should be noted that " +"**support comes in many shapes**, not only in raw code commits and " +"financial help (via [donations](https://liberapay.com/s.pantaleev) or " +"using the [etke.cc managed Matrix hosting service](https://etke.cc/) " +"which is based on matrix-docker-ansible-deploy). It also comes in the " +"shape of code reviews, helping others with " +"[issues](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues), reporting new issues, participating in our support room " +"on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to" +"/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has " +"been there to make matrix-docker-ansible-deploy better in 2023, thank " +"you! 🙇‍♂️" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:64 +msgid "2022" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:66 +msgid "" +"For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/), 2022 started with **breaking the** " +"[**Synapse**](https://github.com/element-hq/synapse) **monopoly** by " +"[adding support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#dendrite-support) for the [Dendrite](https://github.com/matrix-" +"org/dendrite) Matrix homeserver in early January. This required various " +"internal changes so that the [Ansible](https://www.ansible.com/) playbook" +" would not be Synapse-centric anymore. This groundwork paved the way for " +"continuing in this direction and we [added " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#conduit-support) for [Conduit](https://conduit.rs/) in August." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:68 +msgid "" +"When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, " +"2022 was the year of the non-Synapse homeserver implementation. In " +"practice, none of these homeserver implementations seem ready for prime-" +"time yet and there is no migration path when coming from Synapse. Having " +"done our job of adding support for these alternative homeserver " +"implementations, we can say that we're not getting in the way of future " +"progress. It's time for the Dendrite developers to push harder " +"(development-wise) and for the Synapse developers to take a well-deserved" +" long (infinite) break, and we may get to see more people migrating away " +"from Synapse in the next year(s)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:70 +msgid "Support for the following new **bridges** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:72 +msgid "" +"[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#postmoogle-email-bridge-support) for bi-directional email bridging, " +"which supersedes my old and simplistic " +"[email2matrix](https://github.com/devture/email2matrix) one-way bridge-" +"bot" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:73 +msgid "" +"[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#mautrix-discord-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:74 +msgid "" +"[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-" +"skype-bridge-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:75 +msgid "" +"[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"appservice-kakaotalk-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:77 +msgid "Support for the following new **bots** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:79 +msgid "" +"[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#buscarron-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:80 +msgid "" +"[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#honoroit-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:81 +msgid "" +"[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#matrix-registration-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:82 +msgid "" +"[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"hookshot-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:83 +msgid "" +"[maubot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-" +"support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:85 +msgid "Support for the following new **components and services** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:87 +msgid "" +"[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-" +"backup-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:88 +msgid "" +"[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-" +"comments-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:89 +msgid "" +"[Cinny](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-" +"support) client support" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:90 +msgid "" +"[ntfy](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-" +"push-notifications-support) notifications" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:91 +msgid "" +"[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"ldap-registration-proxy-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:92 +msgid "" +"[matrix\\_encryption\\_disabler support](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#matrix_encryption_disabler-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:93 +msgid "" +"[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3" +"-storage-provider-support) to stop the Synapse media store from being a " +"scalability problem. This brought along [another " +"feature](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#synapse-container-image-customization-support) - an easier way to " +"customize the Synapse container image without having to fork and self-" +"build all of it from scratch" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:95 +msgid "" +"Besides these major user-visible changes, a lot of work also happened " +"**under the hood**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:97 +msgid "" +"we made [major improvements to Synapse " +"workers](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#potential-backward-compatibility-break-major-improvements-to-synapse-" +"workers) - adding support for stream writers and for running multiple " +"workers of various kinds (federation senders, pushers, background task " +"processing workers, etc.)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:98 +msgid "" +"we [improved the compatibility of (Synapse + workers) with the rest of " +"the playbook](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-" +"works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by " +"introducing a new `matrix-synapse-reverse-proxy-companion-service` " +"service" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:99 +msgid "" +"we started [splitting various Ansible roles out of the Matrix playbook " +"and into independent roles](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-" +"postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-" +"self-hosting/ansible-role-postgres)), which could be included in other " +"Ansible playbooks. In fact, these roles already power a few **interesting" +" other sibling playbooks**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:100 +msgid "" +"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted " +"[Git](https://git-scm.com/) service) server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:101 +msgid "" +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy), for deploying a " +"[Nextcloud](https://nextcloud.com/) groupware server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:102 +msgid "" +"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" +"/vaultwarden-docker-ansible-deploy), for deploying a " +"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) password " +"manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible" +" server)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:104 +msgid "" +"These sibling playbooks co-exist nicely with one another due to using " +"[Traefik](https://traefik.io/) for reverse-proxying, instead of trying to" +" overtake the whole server by running their own " +"[nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix " +"playbook will follow suit and be powered by Traefik by default." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:106 +msgid "" +"Last, but not least, to optimize our [etke.cc managed Matrix hosting " +"service](https://etke.cc/)'s performance (but also individual Ansible " +"playbook runs for people self-hosting by themselves using the playbook), " +"we've [improved playbook runtime 2-5x](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-" +"performance-improvements-in-playbook-runtime) by employing various " +"Ansible tricks." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/README.po b/i18n/locales/bg/LC_MESSAGES/docs/README.po new file mode 100644 index 000000000..3df29f3ed --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/README.po @@ -0,0 +1,212 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/README.md:1 +msgid "Table of Contents" +msgstr "" + +#: ../../../docs/README.md:3 +msgid "" +"⬇️ Installaton guides " +msgstr "" + +#: ../../../docs/README.md:5 +msgid "" +"There are two installation guides available for beginners and advanced " +"users." +msgstr "" + +#: ../../../docs/README.md:7 +msgid "" +"⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended " +"for those who do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/README.md:9 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide." +msgstr "" + +#: ../../../docs/README.md:11 +msgid "[Prerequisites](prerequisites.md)" +msgstr "" + +#: ../../../docs/README.md:13 +msgid "[Configuring your DNS settings](configuring-dns.md)" +msgstr "" + +#: ../../../docs/README.md:15 +msgid "[Getting the playbook](getting-the-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:17 +msgid "[Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:19 +msgid "[Installing](installing.md)" +msgstr "" + +#: ../../../docs/README.md:21 +msgid "🛠️ Configuration options" +msgstr "" + +#: ../../../docs/README.md:28 +msgid "" +"You can check useful documentation for configuring components here: " +"[Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:30 +msgid "" +"[Administration](configuring-playbook.md#administration) - services that " +"help you in administrating and monitoring your Matrix installation" +msgstr "" + +#: ../../../docs/README.md:32 +msgid "" +"[Authentication and user-related](configuring-playbook.md#authentication-" +"and-user-related) - extend and modify how users are authenticated on your" +" homeserver" +msgstr "" + +#: ../../../docs/README.md:34 +msgid "" +"[Bots](configuring-playbook.md#bots) - bots provide various additional " +"functionality to your installation" +msgstr "" + +#: ../../../docs/README.md:36 +msgid "" +"[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can " +"be used to connect your Matrix installation with third-party " +"communication networks" +msgstr "" + +#: ../../../docs/README.md:38 +msgid "" +"[Clients](configuring-playbook.md#clients) - web clients for Matrix that " +"you can host on your own domains" +msgstr "" + +#: ../../../docs/README.md:40 +msgid "" +"[Core service adjustments](configuring-playbook.md#core-service-" +"adjustments) - backbone of your Matrix system" +msgstr "" + +#: ../../../docs/README.md:42 +msgid "" +"[File Storage](configuring-playbook.md#file-storage) - use alternative " +"file storage to the default `media_store` folder" +msgstr "" + +#: ../../../docs/README.md:46 +msgid "" +"[Other specialized services](configuring-playbook.md#other-specialized-" +"services) - various services that don't fit any other categories" +msgstr "" + +#: ../../../docs/README.md:48 +msgid "👨‍🔧 Maintenance" +msgstr "" + +#: ../../../docs/README.md:50 +msgid "" +"If your server and services experience issues, feel free to come to [our " +"support room](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com) and ask for help." +msgstr "" + +#: ../../../docs/README.md:54 +msgid "[Checking if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/README.md:56 +msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" +msgstr "" + +#: ../../../docs/README.md:58 +msgid "[PostgreSQL maintenance](maintenance-postgres.md)" +msgstr "" + +#: ../../../docs/README.md:60 +msgid "[Synapse maintenance](maintenance-synapse.md)" +msgstr "" + +#: ../../../docs/README.md:62 +msgid "[Upgrading services](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/README.md:64 +msgid "" +"Other documentation pages " +msgstr "" + +#: ../../../docs/README.md:66 +msgid "" +"ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, " +"with a focus on this Ansible playbook" +msgstr "" + +#: ../../../docs/README.md:70 +msgid "[Alternative architectures](alternative-architectures.md)" +msgstr "" + +#: ../../../docs/README.md:72 +msgid "[Container images used by the playbook](container-images.md)" +msgstr "" + +#: ../../../docs/README.md:74 +msgid "[Obtaining an Access Token](obtaining-access-tokens.md)" +msgstr "" + +#: ../../../docs/README.md:76 +msgid "[Playbook tags](playbook-tags.md)" +msgstr "" + +#: ../../../docs/README.md:78 +msgid "[Registering users](registering-users.md)" +msgstr "" + +#: ../../../docs/README.md:80 +msgid "[Running `just` commands](just.md)" +msgstr "" + +#: ../../../docs/README.md:82 +msgid "[Self-building](self-building.md)" +msgstr "" + +#: ../../../docs/README.md:84 +msgid "[Uninstalling](uninstalling.md)" +msgstr "" + +#: ../../../docs/README.md:86 +msgid "[Updating users passwords](updating-users-passwords.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po new file mode 100644 index 000000000..b7254ae41 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po @@ -0,0 +1,78 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/alternative-architectures.md:1 +msgid "Alternative architectures" +msgstr "Алтернативни архитектури" + +#: ../../../docs/alternative-architectures.md:3 +msgid "" +"As stated in the [Prerequisites](prerequisites.md), currently only " +"`amd64` (`x86_64`) is fully supported." +msgstr "Както е посочено в [Предусловия](prerequisites.md), в момента само `amd64` (`x86_64`) е напълно поддържана архитектура." + +#: ../../../docs/alternative-architectures.md:5 +msgid "" +"The playbook automatically determines the target server's architecture " +"(the `matrix_architecture` variable) to be one of the following:" +msgstr "" + +#: ../../../docs/alternative-architectures.md:7 +msgid "`amd64` (`x86_64`)" +msgstr "`amd64` (`x86_64`)" + +#: ../../../docs/alternative-architectures.md:8 +msgid "`arm32`" +msgstr "`arm32`" + +#: ../../../docs/alternative-architectures.md:9 +msgid "`arm64`" +msgstr "`arm64`" + +#: ../../../docs/alternative-architectures.md:11 +msgid "" +"Some tools and container images can be built on the host or other " +"measures can be used to install on that architecture." +msgstr "" + +#: ../../../docs/alternative-architectures.md:13 +msgid "Implementation details" +msgstr "" + +#: ../../../docs/alternative-architectures.md:15 +msgid "" +"For `amd64`, prebuilt container images (see the [container images we use" +"](container-images.md)) are used for all components (except [Hydrogen" +"](configuring-playbook-client-hydrogen.md), which goes through self-" +"building)." +msgstr "" + +#: ../../../docs/alternative-architectures.md:17 +msgid "" +"For other architecture (`arm64`, `arm32`), components which have a " +"prebuilt image make use of it. If the component is not available for the " +"specific architecture, [self-building](self-building.md) will be used. " +"Not all components support self-building though, so your mileage may " +"vary." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po new file mode 100644 index 000000000..a7f6eea4b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po @@ -0,0 +1,284 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/ansible.md:2 +msgid "Running this playbook" +msgstr "" + +#: ../../../docs/ansible.md:4 +msgid "" +"This playbook is meant to be run using " +"[Ansible](https://www.ansible.com/)." +msgstr "" + +#: ../../../docs/ansible.md:6 +msgid "" +"Ansible typically runs on your local computer and carries out tasks on a " +"remote server. If your local computer cannot run Ansible, you can also " +"run Ansible on some server somewhere (including the server you wish to " +"install to)." +msgstr "" + +#: ../../../docs/ansible.md:8 +msgid "Supported Ansible versions" +msgstr "" + +#: ../../../docs/ansible.md:10 +msgid "" +"To manually check which version of Ansible you're on, run: `ansible " +"--version`." +msgstr "" + +#: ../../../docs/ansible.md:12 +msgid "" +"For the **best experience**, we recommend getting the **latest version of" +" Ansible available**." +msgstr "" + +#: ../../../docs/ansible.md:14 +msgid "" +"We're not sure what's the minimum version of Ansible that can run this " +"playbook successfully. The lowest version that we've confirmed (on " +"2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined " +"with `ansible` (`4.10.0`)." +msgstr "" + +#: ../../../docs/ansible.md:16 +msgid "" +"If your distro ships with an Ansible version older than this, you may run" +" into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using " +"Ansible via Docker](#using-ansible-via-docker)." +msgstr "" + +#: ../../../docs/ansible.md:18 +msgid "Upgrading Ansible" +msgstr "" + +#: ../../../docs/ansible.md:20 +msgid "" +"Depending on your distribution, you may be able to upgrade Ansible in a " +"few different ways:" +msgstr "" + +#: ../../../docs/ansible.md:22 +msgid "" +"by using an additional repository (PPA, etc.), which provides newer " +"Ansible versions. See instructions for " +"[CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-rhel-centos-or-fedora), " +"[Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-debian), or " +"[Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-ubuntu) on the Ansible website." +msgstr "" + +#: ../../../docs/ansible.md:24 +msgid "" +"by removing the Ansible package (`yum remove ansible` or `apt-get remove " +"ansible`) and installing via " +"[pip](https://pip.pypa.io/en/stable/installation/) (`pip install " +"ansible`)." +msgstr "" + +#: ../../../docs/ansible.md:26 +msgid "" +"If using the `pip` method, do note that the `ansible-playbook` binary may" +" not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-" +"variable), but in some more special location like `/usr/local/bin" +"/ansible-playbook`. You may need to invoke it using the full path." +msgstr "" + +#: ../../../docs/ansible.md:28 +msgid "" +"**Note**: Both of the above methods are a bad way to run system software " +"such as Ansible. If you find yourself needing to resort to such hacks, " +"please consider reporting a bug to your distribution and/or switching to " +"a sane distribution, which provides up-to-date software." +msgstr "" + +#: ../../../docs/ansible.md:30 +msgid "Using Ansible via Docker" +msgstr "" + +#: ../../../docs/ansible.md:32 +msgid "" +"Alternatively, you can run Ansible inside a Docker container (powered by " +"the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker " +"image)." +msgstr "" + +#: ../../../docs/ansible.md:34 +msgid "" +"This ensures that you're using a very recent Ansible version, which is " +"less likely to be incompatible with the playbook." +msgstr "" + +#: ../../../docs/ansible.md:36 +msgid "" +"You can either [run Ansible in a container on the Matrix server itself" +"](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run " +"Ansible in a container on another computer (not the Matrix server" +")](#running-ansible-in-a-container-on-another-computer-not-the-matrix-" +"server)." +msgstr "" + +#: ../../../docs/ansible.md:38 +msgid "Running Ansible in a container on the Matrix server itself" +msgstr "" + +#: ../../../docs/ansible.md:40 +msgid "" +"To run Ansible in a (Docker) container on the Matrix server itself, you " +"need to have a working Docker installation. Docker is normally installed " +"by the playbook, so this may be a bit of a chicken and egg problem. To " +"solve it:" +msgstr "" + +#: ../../../docs/ansible.md:42 +msgid "" +"you **either** need to install Docker manually first. Follow [the " +"upstream instructions](https://docs.docker.com/engine/install/) for your " +"distribution and consider setting " +"`matrix_playbook_docker_installation_enabled: false` in your `vars.yml` " +"file, to prevent the playbook from installing Docker" +msgstr "" + +#: ../../../docs/ansible.md:43 +msgid "" +"**or** you need to run the playbook in another way (e.g. [Running Ansible" +" in a container on another computer (not the Matrix server)](#running-" +"ansible-in-a-container-on-another-computer-not-the-matrix-server)) at " +"least the first time around" +msgstr "" + +#: ../../../docs/ansible.md:45 +msgid "" +"Once you have a working Docker installation on the server, **clone the " +"playbook** somewhere on the server and configure it as per usual " +"(`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in " +"[configuring the playbook](configuring-playbook.md)." +msgstr "" + +#: ../../../docs/ansible.md:47 +msgid "" +"You would then need to add `ansible_connection=community.docker.nsenter` " +"to the host line in `inventory/hosts`. This tells Ansible to connect to " +"the \"remote\" machine by switching Linux namespaces with " +"[nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead " +"of using SSH." +msgstr "" + +#: ../../../docs/ansible.md:49 +msgid "" +"Alternatively, you can leave your `inventory/hosts` as is and specify the" +" connection type in **each** `ansible-playbook` call you do later, like " +"this: `ansible-playbook --connection=community.docker.nsenter …`" +msgstr "" + +#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 +msgid "Run this from the playbook's directory:" +msgstr "" + +#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 +msgid "" +"Once you execute the above command, you'll be dropped into a `/work` " +"directory inside a Docker container. The `/work` directory contains the " +"playbook's code." +msgstr "" + +#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 +msgid "" +"First, consider running `git config --global --add safe.directory /work` " +"to [resolve directory ownership issues](#resolve-directory-ownership-" +"issues)." +msgstr "" + +#: ../../../docs/ansible.md:67 +msgid "" +"Finally, you can execute `ansible-playbook …` (or `ansible-playbook " +"--connection=community.docker.nsenter …`) commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:69 +msgid "Running Ansible in a container on another computer (not the Matrix server)" +msgstr "" + +#: ../../../docs/ansible.md:82 +msgid "" +"The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into " +"the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different" +" path (not in `$HOME/.ssh/id_rsa`), adjust that part." +msgstr "" + +#: ../../../docs/ansible.md:88 +msgid "Finally, you execute `ansible-playbook …` commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:90 +msgid "If you don't use SSH keys for authentication" +msgstr "" + +#: ../../../docs/ansible.md:92 +msgid "" +"If you don't use SSH keys for authentication, simply remove that whole " +"line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." +msgstr "" + +#: ../../../docs/ansible.md:94 +msgid "" +"To authenticate at your server using a password, you need to add a " +"package. So, when you are in the shell of the ansible docker container " +"(the previously used `docker run -it …` command), run:" +msgstr "" + +#: ../../../docs/ansible.md:100 +msgid "" +"Then, to be asked for the password whenever running an `ansible-" +"playbook` command add `--ask-pass` to the arguments of the command." +msgstr "" + +#: ../../../docs/ansible.md:102 +msgid "Resolve directory ownership issues" +msgstr "" + +#: ../../../docs/ansible.md:104 +msgid "" +"Because you're `root` in the container running Ansible and this likely " +"differs fom the owner (your regular user account) of the playbook " +"directory outside of the container, certain playbook features which use " +"`git` locally may report warnings such as:" +msgstr "" + +#: ../../../docs/ansible.md:106 +msgid "" +"fatal: unsafe repository ('/work' is owned by someone else) To add an " +"exception for this directory, call: git config --global --add " +"safe.directory /work" +msgstr "" + +#: ../../../docs/ansible.md:110 +msgid "" +"These errors can be resolved by making `git` trust the playbook directory" +" by running `git config --global --add safe.directory /work`" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po new file mode 100644 index 000000000..2013360c8 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po @@ -0,0 +1,93 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-captcha.md:1 +msgid "" +"(Adapted from the [upstream project](https://github.com/element-" +"hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" +msgstr "" + +#: ../../../docs/configuring-captcha.md:3 +msgid "Overview" +msgstr "" + +#: ../../../docs/configuring-captcha.md:5 +msgid "" +"Captcha can be enabled for this home server. This file explains how to do" +" that." +msgstr "" + +#: ../../../docs/configuring-captcha.md:7 +msgid "" +"The captcha mechanism used is Google's " +"[ReCaptcha](https://www.google.com/recaptcha/). This requires API keys " +"from Google. If your homeserver is Dendrite then " +"[hCapcha](https://www.hcaptcha.com) can be used instead." +msgstr "" + +#: ../../../docs/configuring-captcha.md:9 +msgid "ReCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:11 +#: ../../../docs/configuring-captcha.md:37 +msgid "Getting keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:13 +#: ../../../docs/configuring-captcha.md:39 +msgid "Requires a site/secret key pair from:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:15 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:17 +msgid "" +"Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox " +"option" +msgstr "" + +#: ../../../docs/configuring-captcha.md:19 +msgid "Setting ReCaptcha keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:21 +msgid "" +"Once registered as above, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:35 +msgid "hCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:41 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:43 +msgid "Setting hCaptcha keys" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po new file mode 100644 index 000000000..6196e1200 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po @@ -0,0 +1,410 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dns.md:1 +msgid "Configuring your DNS settings" +msgstr "" + +#: ../../../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:5 +msgid "To set up Matrix on your domain, you'd need to do some DNS configuration." +msgstr "" + +#: ../../../docs/configuring-dns.md:7 +msgid "DNS setting for server delegation (optional)" +msgstr "" + +#: ../../../docs/configuring-dns.md:9 +msgid "" +"In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " +"we recommend to use a short user ID like `@alice:example.com` instead of " +"`@alice:matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-dns.md:11 +msgid "" +"To use such an ID, you don't need to install anything on the actual " +"`example.com` server. Instead, you need to instruct the Matrix network " +"that Matrix services for `example.com` are redirected over to " +"`matrix.example.com`. This redirection is also known as \"delegation\"." +msgstr "" + +#: ../../../docs/configuring-dns.md:13 +msgid "" +"As we discuss in [Server Delegation](howto-server-delegation.md), server " +"delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-dns.md:15 +msgid "" +"Setting up a `/.well-known/matrix/server` file on the base domain " +"(`example.com`)" +msgstr "" + +#: ../../../docs/configuring-dns.md:16 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-dns.md:18 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file, instead of using a " +"DNS SRV record." +msgstr "" + +#: ../../../docs/configuring-dns.md:20 +msgid "" +"If you choose the recommended method (file-based delegation), you do not " +"need to configure the DNS record to enable server delegation. You will " +"need to add a necessary configuration later, when you [finalize the " +"installation](installing.md#finalize-the-installation) after installing " +"and starting Matrix services." +msgstr "" + +#: ../../../docs/configuring-dns.md:22 +msgid "" +"On the other hand, if you choose this method (setting up a DNS SRV " +"record), you need to configure the additional DNS record as well as " +"adjust SSL certificate handling. Take a look at this documentation for " +"more information: [Server Delegation via a DNS SRV record (advanced" +")](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-" +"advanced)" +msgstr "" + +#: ../../../docs/configuring-dns.md:24 +msgid "DNS settings for services enabled by default" +msgstr "" + +#: ../../../docs/configuring-dns.md:26 +msgid "" +"To serve the base domain (`example.com`) and [Element Web](configuring-" +"playbook-client-element-web.md) with the default subdomain, adjust DNS " +"records as below." +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Type" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Host" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Priority" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Weight" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Port" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Target" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "A" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "CNAME" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`element`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/configuring-dns.md:33 +msgid "" +"As the table illustrates, you need to create 2 subdomains " +"(`matrix.example.com` and `element.example.com`) and point both of them " +"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/configuring-dns.md:35 +msgid "" +"The `element.example.com` subdomain is necessary, because this playbook " +"installs the [Element Web](https://github.com/element-hq/element-web) " +"client for you by default. If you'd rather instruct the playbook not to " +"install Element Web (`matrix_client_element_enabled: false` when " +"[Configuring the playbook](configuring-playbook.md) later), feel free to " +"skip the `element.example.com` DNS record." +msgstr "" + +#: ../../../docs/configuring-dns.md:37 +msgid "Be mindful as to how long it will take for the DNS records to propagate." +msgstr "" + +#: ../../../docs/configuring-dns.md:39 +msgid "" +"If you are using Cloudflare DNS, make sure to disable the proxy and set " +"all records to \"DNS only\". Otherwise, fetching certificates will fail." +msgstr "" + +#: ../../../docs/configuring-dns.md:41 +msgid "DNS settings for optional services/features" +msgstr "" + +#: ../../../docs/configuring-dns.md:43 +msgid "" +"For other services which may need subdomain settings, see the table below" +" and configure the DNS (`CNAME`) records accordingly." +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Used by component" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Dimension](configuring-playbook-dimension.md) integration server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`dimension`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`jitsi`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "" +"[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) " +"monitoring system" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`stats`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`goneb`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`sygnal`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`ntfy`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`etherpad`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`hydrogen`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Cinny](configuring-playbook-client-cinny.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`cinny`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`schildichat`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`wsproxy`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`buscarron`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[rageshake](configuring-playbook-rageshake.md) bug report server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`rageshake`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "SRV" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`_matrix-identity._tcp`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "10" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "0" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "443" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "" +"[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix" +"](configuring-playbook-email2matrix.md) email bridges" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "MX" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "TXT" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`v=spf1 ip4:matrix-server-IP -all`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`_dmarc.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`v=DMARC1; p=quarantine;`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`postmoogle._domainkey.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "get it from `!pm dkim`" +msgstr "" + +#: ../../../docs/configuring-dns.md:66 +msgid "SRV record for ma1sd" +msgstr "" + +#: ../../../docs/configuring-dns.md:68 +msgid "" +"To make ma1sd enable its federation features, you need to set up a " +"`_matrix-identity._tcp` SRV record. Don't confuse this with the " +"`_matrix._tcp` SRV record for server delegation. See the table above and " +"[this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for " +"values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:70 +msgid "" +"When setting up a SRV record, if you are asked for a service and protocol" +" instead of a hostname split the host value from the table where the " +"period is. For example use service as `_matrix-identity` and protocol as " +"`_tcp`." +msgstr "" + +#: ../../../docs/configuring-dns.md:72 +msgid "MX and TXT records for Postmoogle" +msgstr "" + +#: ../../../docs/configuring-dns.md:74 +msgid "" +"To make Postmoogle enable its email sending features, you need to " +"configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above " +"for values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:78 +msgid "" +"[▶️](getting-the-playbook.md) When you're done with the DNS configuration" +" and ready to proceed, continue with [Getting the playbook](getting-the-" +"playbook.md)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po new file mode 100644 index 000000000..6aa45c304 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po @@ -0,0 +1,252 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-alertmanager-receiver.md:1 +msgid "" +"Setting up Prometheus Alertmanager integration via matrix-alertmanager-" +"receiver (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 +msgid "" +"The playbook can install and configure the [matrix-alertmanager-" +"receiver](https://github.com/metio/matrix-alertmanager-receiver) service " +"for you. It's a " +"[client](https://prometheus.io/docs/alerting/latest/clients/) for " +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)," +" allowing you to deliver alerts to Matrix rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 +msgid "" +"See the project's [documentation](https://github.com/metio/matrix-" +"alertmanager-receiver) to learn more about what this component does and " +"why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 +msgid "" +"At the moment, **setting up this service's bot requires some manual " +"actions** as described below in [Account and room preparation](#account-" +"and-room-preparation)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +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:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 +msgid "" +"To enable matrix-alertmanager-receiver, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:36 +msgid "" +"See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " +"additional configuration variables." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +msgid "Adjusting the matrix-alertmanager-receiver URL" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +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:42 +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:44 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the matrix-alertmanager-receiver domain to the " +"Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 +msgid "Account and room preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 +msgid "" +"The playbook can automatically create users, but it cannot automatically " +"obtain access tokens, nor perform any of the other manual actions below." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 +msgid "" +"`matrix-alertmanager-receiver` uses a bot (with a username specified in " +"`matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see " +"above) for delivering messages. You need to **manually register this bot " +"acccount and obtain an access token for it**." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 +msgid "" +"[Register a new user](registering-users.md): `ansible-playbook -i " +"inventory/hosts setup.yml --extra-" +"vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT " +"admin=no' --tags=register-user`" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 +msgid "" +"[Obtain an access token](obtaining-access-tokens.md) for the bot's user " +"account" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 +msgid "Invite the bot to a room where you'd like to alerts to be delivered" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 +msgid "" +"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:70 +msgid "" +"(Optionally) Adjust " +"`matrix_alertmanager_receiver_config_matrix_room_mapping` to create a " +"mapping between the new room and its ID" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 +msgid "" +"Steps 1 and 2 above only need to be done once, while preparing your " +"[configuration](#adjusting-the-playbook-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 +msgid "" +"Steps 3 and 4 need to be done for each new room you'd like the bot to " +"deliver alerts to. Step 5 is optional and provides cleaner `/alert/` " +"URLs." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +msgid "" +"Now that you've [prepared the bot account and room](#account-and-room-" +"preparation), [configured the playbook](#adjusting-the-playbook-" +"configuration), and potentially [adjusted your DNS records](#adjusting-" +"dns-records), you can run the playbook with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +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:89 +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:91 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"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:93 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +msgid "Configure your Prometheus Alertmanager with configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 +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:116 +msgid "" +"This bot does **not** accept room invitations automatically (like many " +"other bots do). To deliver messages to rooms, **the bot must be joined to" +" all rooms manually** - see Step 4 of the [Account and room preparation" +"](#account-and-room-preparation) section." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po new file mode 100644 index 000000000..09d10f782 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po @@ -0,0 +1,108 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-appservice-double-puppet.md:1 +msgid "Setting up Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 +msgid "" +"Appservice Double Puppet is a homeserver appservice through which bridges" +" (and potentially other services) can impersonate any user on the " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 +msgid "" +"This is useful for performing [double-" +"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via" +" the [appservice method](https://docs.mau.fi/bridges/general/double-" +"puppeting.html#appservice-method-new). The Appservice Double Puppet " +"service is an implementation of this approach." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 +msgid "" +"Previously, bridges supported performing [double-" +"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"with the help of the [Shared Secret Auth password provider module" +"](./configuring-playbook-shared-secret-auth.md), but this old and hacky " +"solution has been superseded by this Appservice Double Puppet method." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 +msgid "" +"To enable the Appservice Double Puppet service, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 +msgid "" +"When enabled, double puppeting will automatically be enabled for all " +"bridges that support double puppeting via the appservice method." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po new file mode 100644 index 000000000..6e1b9782e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po @@ -0,0 +1,298 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-appservice-draupnir-for-all.md:1 +msgid "Setting up Draupnir for All/D4A (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 +msgid "" +"The playbook can install and configure the [Draupnir](https://github.com" +"/the-draupnir-project/Draupnir) moderation tool for you in appservice " +"mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 +msgid "" +"Appservice mode can be used together with the regular [Draupnir bot" +"](configuring-playbook-bot-draupnir.md) or independently. Details about " +"the differences between the 2 modes are described below." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 +msgid "Draupnir Appservice mode compared to Draupnir bot mode" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 +msgid "" +"The administrative functions for managing the appservice are alpha " +"quality and very limited. However, the experience of using an appservice-" +"provisioned Draupnir is on par with the experience of using Draupnir from" +" bot mode except in the case of avatar customisation as described later " +"on in this document." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 +msgid "" +"Draupnir for all is the way to go if you need more than 1 Draupnir " +"instance, but you don't need access to Synapse Admin features as they are" +" not accessible through Draupnir for All (Even though the commands do " +"show up in help)." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 +msgid "" +"Draupnir for all in the playbook is rate-limit-exempt automatically as " +"its appservice configuration file does not specify any rate limits." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 +msgid "" +"Normal Draupnir does come with the benefit of access to Synapse Admin " +"features. You are also able to more easily customise your normal Draupnir" +" than D4A as D4A even on the branch with the Avatar command (To be " +"Upstreamed to Mainline Draupnir) that command is clunky as it requires " +"the use of things like Element Web devtools. In normal Draupnir this is a" +" quick operation where you login to Draupnir with a normal client and set" +" Avatar and Display name normally." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 +msgid "" +"Draupnir for all does not support external tooling like " +"[MRU](https://mru.rory.gay) as it can't access Draupnir's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 +msgid "Installation" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 +msgid "Create a main management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 +msgid "" +"The playbook does not create a management room for your Main Draupnir. " +"This task you have to do on your own." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 +msgid "" +"The management room has to be given an alias and be public when you are " +"setting up the bot for the first time as the bot does not differentiate " +"between invites and invites to the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 +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:29 +msgid "" +"As noted in the Draupnir install instructions the control room is " +"sensitive. The following is said about the control room in the Draupnir " +"install instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +msgid "" +"Anyone in this room can control the bot so it is important that you only " +"invite trusted users to this room. The room must be unencrypted since the" +" playbook does not support installing Pantalaimon yet." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 +msgid "Give your main management room an alias." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 +msgid "" +"Give the room from step 1 an alias. This alias can be anything you want " +"and its recommended for increased security during the setup phase of the " +"bot that you make this alias be a random string. You can give your room a" +" secondary human readable alias when it has been locked down after setup " +"phase." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 +msgid "Adjusting the playbook configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:40 +msgid "" +"You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created" +" in step 2." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md: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-appservice-draupnir-for-all.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-appservice-draupnir-for-all.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 +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:69 +msgid "" +"The installation of Draupnir for all in this playbook is very much Alpha " +"quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot " +"mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +msgid "Granting Users the ability to use D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +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:75 +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:77 +msgid "" +"To allow users or whole homeservers you type /plain @draupnir-" +"main:example.com allow `target` and target can be either a MXID or a " +"wildcard like `@*:example.com` to allow all users on example.com to " +"register. We use /plain to force the client to not attempt to mess with " +"this command as it can break Wildcard commands especially." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 +msgid "How to provision a D4A once you are allowed to." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 +msgid "" +"Open a DM with @draupnir-main:example.com and if using an Element client " +"send a message into this DM to finalise creating it. The bot will reject " +"this invite and you will shortly get invited to the Draupnir control room" +" for your newly provisioned Draupnir. From here its just a normal " +"Draupnir experience." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +msgid "" +"Congratulations if you made it all the way here because you now have a " +"fully working Draupnir for all deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 +msgid "Configuration of D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 +msgid "" +"You can refer to the upstream [documentation](https://github.com/the-" +"draupnir-project/Draupnir) for more configuration documentation. Please " +"note that the playbook ships a full copy of the example config that does " +"transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in " +"the template directory of the role." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 +msgid "" +"Please note that Config extension does not affect the appservices config " +"as this config is not extensible in current Draupnir anyways. Config " +"extension instead touches the config passed to the Draupnirs that your " +"Appservice creates. So for example below makes all provisioned Draupnirs " +"protect all joined rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 +msgid "" +"You can configure additional options by adding the " +"`matrix_appservice_draupnir_for_all_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 +msgid "" +"For example to change Draupnir's `protectAllJoinedRooms` option to `true`" +" you would add the following to your `vars.yml` file." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po new file mode 100644 index 000000000..4ba66d027 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po @@ -0,0 +1,216 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-backup-borg.md:1 +msgid "Setting up BorgBackup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:3 +msgid "" +"The playbook can install and configure " +"[BorgBackup](https://www.borgbackup.org/) (short: Borg) with " +"[borgmatic](https://torsion.org/borgmatic/) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:5 +msgid "" +"BorgBackup is a deduplicating backup program with optional compression " +"and encryption. That means your daily incremental backups can be stored " +"in a fraction of the space and is safe whether you store it at home or on" +" a cloud service." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:7 +msgid "" +"You will need a remote server where BorgBackup will store the backups. " +"There are hosted, BorgBackup compatible solutions available, such as " +"[BorgBase](https://www.borgbase.com)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:9 +msgid "" +"The backup will run based on `backup_borg_schedule` var (systemd timer " +"calendar), default: 4am every day." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:11 +msgid "" +"By default, if you're using the integrated Postgres database server (as " +"opposed to [an external Postgres server](configuring-playbook-external-" +"postgres.md)), backups with BorgBackup will also include dumps of your " +"Postgres database. An alternative solution for backing up the Postgres " +"database is [postgres backup](configuring-playbook-postgres-backup.md). " +"If you decide to go with another solution, you can disable Postgres-" +"backup support for BorgBackup using the `backup_borg_postgresql_enabled` " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:13 +msgid "" +"**Note**: the component is not managed by this repository but its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"backup_borg)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:15 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:17 +msgid "" +"If you do not disable Postgres-backup support, make sure that the " +"Postgres version of your homeserver's database is compatible with " +"borgmatic." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:19 +msgid "Create a new SSH key:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:25 +msgid "" +"This can be done on any machine and you don't need to place the key in " +"the `.ssh` folder. It will be added to the Ansible config later." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:27 +msgid "" +"Add the **public** part of this SSH key (the `matrix-borg-backup.pub` " +"file) to your BorgBackup provider/server:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:29 +msgid "" +"If you plan to use a hosted solution, follow their instructions. If you " +"have your own server, copy the key over:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:39 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:41 +msgid "" +"Minimal working configuration " +"(`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:58 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:60 +msgid "USER - SSH user of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:61 +msgid "HOST - SSH host of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:62 +msgid "" +"REPO - BorgBackup repository name, it will be initialized on backup " +"start, eg: `matrix`, regarding Syntax see [Remote " +"repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html" +"#repository-urls)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:63 +msgid "" +"PASSPHRASE - passphrase used for encrypting backups, you may generate it " +"with `pwgen -s 64 1` or use any password manager" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:64 +msgid "" +"PRIVATE KEY - the content of the **private** part of the SSH key you " +"created before. The whole key (all of its belonging lines) under " +"`backup_borg_ssh_key_private` needs to be indented with 2 spaces" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:66 +msgid "" +"To backup without encryption, add `backup_borg_encryption: 'none'` to " +"your vars. This will also enable the " +"`backup_borg_unknown_unencrypted_repo_access_is_ok` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:68 +msgid "" +"`backup_borg_location_source_directories` defines the list of directories" +" to back up: it's set to `{{ matrix_base_data_path }}` by default, which " +"is the base directory for every service's data, such as Synapse, Postgres" +" and the bridges. You might want to exclude certain directories or file " +"patterns from the backup using the " +"`backup_borg_location_exclude_patterns` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:70 +msgid "" +"Check the [backup_borg role](https://github.com/mother-of-all-self-" +"hosting/ansible-role-backup_borg)'s " +"[defaults/main.yml](https://github.com/mother-of-all-self-hosting" +"/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full " +"list of available options." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:74 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:81 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:83 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:85 +msgid "Manually start a backup" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:87 +msgid "" +"For testing your setup it can be helpful to not wait until 4am. If you " +"want to run the backup immediately, log onto the server and run " +"`systemctl start matrix-backup-borg`. This will not return until the " +"backup is done, so possibly a long time. Consider using " +"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " +"unstable." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po new file mode 100644 index 000000000..3610179d0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po @@ -0,0 +1,241 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-base-domain-serving.md:1 +msgid "Serving the base domain (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:3 +msgid "" +"By default, this playbook sets up services on your Matrix server " +"(`matrix.example.com`), but has it configured so that it presents itself " +"as the base domain (`example.com`). To have this server officially be " +"responsible for Matrix services for the base domain (`example.com`), you " +"need to set up server delegation / redirection." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:5 +msgid "" +"As we discuss in [Server Delegation](howto-server-delegation.md), server " +"delegation / redirection can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:7 +msgid "" +"Setting up a `/.well-known/matrix/server` file on the base domain " +"(`example.com`)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:8 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:10 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:12 +msgid "" +"However, those who don't have a separate server to dedicate to the base " +"domain have trouble arranging this." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:14 +msgid "Usually, there are 2 options:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:16 +msgid "" +"either get a separate server for the base domain, just for serving the " +"files necessary for [Server Delegation via a well-known file](howto-" +"server-delegation.md#server-delegation-via-a-well-known-file)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:18 +msgid "" +"or, arrange for the Matrix server to serve the base domain. This either " +"involves you [using your own webserver](configuring-playbook-own-" +"webserver.md) or making the integrated webserver serve the base domain " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:20 +msgid "" +"This documentation page tells you how to do the latter. With some easy " +"changes, we make it possible to serve the base domain from the Matrix " +"server via the integrated webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:22 +msgid "" +"Just [**adjust your DNS records**](configuring-dns.md), so that your base" +" domain is pointed to the Matrix server's IP address (using a DNS `A` " +"record) **and then add the following configuration** to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:28 +msgid "Doing this, the playbook will:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:30 +msgid "" +"obtain an SSL certificate for the base domain, just like it does for all " +"other domains (see [how we handle SSL certificates](configuring-playbook-" +"ssl-certificates.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:32 +msgid "" +"serve the `/.well-known/matrix/*` files which are necessary for " +"[Federation Server Discovery](configuring-well-known.md#federation-" +"server-discovery) (also see [Server Delegation](howto-server-" +"delegation.md)) and [Client-Server discovery](configuring-well-known.md" +"#client-server-discovery)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:34 +msgid "" +"serve a simple homepage at `https://example.com` with content `Hello from" +" example.com` (configurable via the " +"`matrix_static_files_file_index_html_template` variable). You can also " +"[serve a more complicated static website](#serving-a-static-website-at-" +"the-base-domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:36 +msgid "Serving a static website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:38 +msgid "" +"By default, when \"serving the base domain\" is enabled, the playbook " +"hosts a simple `index.html` webpage at `/matrix/static-" +"files/public/index.html`. The content of this page is taken from the " +"`matrix_static_files_file_index_html_template` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:40 +msgid "" +"If you'd like to host your own static website (more than a single " +"`index.html` page) at the base domain, you can disable the creation of " +"this default `index.html` page like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:54 +msgid "" +"With this configuration, Ansible will no longer mess around with the " +"`/matrix/static-files/public/index.html` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:56 +msgid "" +"You are then free to upload any static website files to `/matrix/static-" +"files/public` and they will get served at the base domain. You can do so " +"manually or by using the [ansible-role-aux](https://github.com/mother-of-" +"all-self-hosting/ansible-role-aux) Ansible role, which is part of this " +"playbook already." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:58 +msgid "Serving a more complicated website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:60 +msgid "" +"If you'd like to serve an even more complicated (dynamic) website from " +"the Matrix server, relying on the playbook to serve the base domain is " +"not the best choice." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:62 +msgid "You have 2 options." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:64 +msgid "**One way is to host your base domain elsewhere**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:65 +msgid "" +"you stopping to serve it from the Matrix server: remove " +"`matrix_static_files_container_labels_base_domain_enabled` from your " +"configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:66 +msgid "" +"[configuring Matrix Delegation via well-known](./configuring-well-" +"known.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:68 +msgid "" +"**Another way is to serve the base domain from another (your own) " +"container on the Matrix server**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:69 +msgid "" +"telling the playbook to only serve `example.com/.well-known/matrix` files" +" by adjusting your `vars.yml` configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:70 +msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:71 +msgid "" +"add an extra: " +"`matrix_static_files_container_labels_base_domain_traefik_path_prefix: " +"/.well-known/matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:72 +msgid "building and running a new container on the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:73 +msgid "" +"it should be connected to the `traefik` network, so that Traefik can " +"reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:74 +msgid "" +"it should have appropriate [container " +"labels](https://docs.docker.com/config/labels-custom-metadata/), which " +"instruct Traefik to reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:76 +msgid "" +"How you'll be managing building and running this container is up-to-you. " +"You may use of the primitives from [ansible-role-aux](https://github.com" +"/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it" +" yourself, or you can set it up in another way." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po new file mode 100644 index 000000000..be332fe7e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -0,0 +1,688 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-baibot.md:1 +msgid "Setting up baibot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:8 +msgid "" +"🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a " +"[Matrix](https://matrix.org/) bot developed by " +"[etke.cc](https://etke.cc/) that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you. 🤖" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:10 +msgid "" +"It supports [OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other" +" [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:12 +msgid "" +"It's designed as a more private and [✨ " +"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" +"file#-features) alternative to [matrix-chatgpt-bot](./configuring-" +"playbook-bot-chatgpt.md). See the " +"[baibot](https://github.com/etkecc/baibot) project and its documentation " +"for more information." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:14 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:16 +msgid "" +"API access to one or more LLM [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:20 +msgid "" +"There are **a lot of configuration options** (some required, some " +"possibly required, some optional), so they're **split into multiple " +"sections below**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:23 +msgid "[Base configuration](#base-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:24 +msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:25 +msgid "[👥 Initial users configuration](#-initial-users-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:26 +msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:27 +msgid "" +"[🤝 Configuring initial default handlers](#-configuring-initial-default-" +"handlers)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:29 +msgid "" +"Depending on your current `vars.yml` file and desired configuration, " +"**you may require more than just the [base configuration](#base-" +"configuration)**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:31 +msgid "Base configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:33 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:71 +msgid "" +"As mentioned above, **this may not be enough**. Continue with the " +"configuration sections below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:73 +msgid "👮‍♂️ Administrator configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:75 +#: ../../../docs/configuring-playbook-bot-baibot.md:99 +msgid "This is an addition to the [base configuration](#base-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:77 +msgid "" +"To specify who is considered a bot [👮‍♂️ " +"Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators)," +" you either need to specify " +"`matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The " +"latter is a single variable which affects all bridges and bots." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:79 +msgid "" +"If `matrix_admin` is already configured in your `vars.yml` configuration," +" you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:81 +#: ../../../docs/configuring-playbook-bot-baibot.md:110 +msgid "" +"**If necessary**, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:95 +msgid "👥 Initial users configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:97 +msgid "" +"By default, **all users on your homeserver are considered allowed " +"users**. If that's OK, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:101 +msgid "" +"To specify who is considered a bot [👥 " +"User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), " +"you may:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:103 +msgid "" +"define an **initial** value for " +"`matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible " +"variable, as shown below" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:104 +msgid "" +"configure the list at runtime via the bot's `!bai access set-users " +"SPACE_SEPARATED_PATTERNS` command" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:106 +msgid "" +"Configuring " +"`matrix_bot_baibot_config_initial_global_config_user_patterns` is " +"optional, but it can be useful to pre-configure the bot with a list of " +"users who should have access to the bot's features." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:108 +msgid "" +"**Note**: Once initially configured, the allowed users list **cannot be " +"managed via Ansible anymore**. It can only be managed subsequently via " +"bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:122 +msgid "🤖 Configuring agents via Ansible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:124 +msgid "" +"You are **not required** to define agents " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration) via Ansible. **To get started quickly**, you can " +"**skip this section and define agents at runtime via chat commands** " +"(following the bot's guidance)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:126 +msgid "" +"Privileged users (like the [👮‍♂️ Administrator](#️-administrator-" +"configuration), but potentially others too - see the upstream [🔒 " +"access](https://github.com/etkecc/baibot/blob/main/docs/access.md) " +"documentation) can **define agents dynamically at any time** via chat " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:128 +msgid "" +"The Ansible role includes preset variables for easily enabling some [🤖 " +"agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on " +"various [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " +"(e.g. OpenAI, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:130 +msgid "" +"Besides the presets, the Ansible role also includes support for " +"configuring additional statically-defined agents via the " +"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:132 +msgid "" +"Agents defined statically and those created dynamically (via chat) are " +"named differently, so **conflict cannot arise**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:134 +msgid "" +"Depending on your propensity for " +"[GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to " +"define agents statically via Ansible, or you may wish to do it " +"dynamically via chat." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:136 +msgid "" +"Before proceeding, we recommend reading the upstream documentation on " +"[How to choose a " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#how-to-choose-a-provider). In short, it's probably best to go with " +"[OpenAI](#openai)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:138 +msgid "Anthropic" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:140 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [Anthropic " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:142 +#: ../../../docs/configuring-playbook-bot-baibot.md:168 +#: ../../../docs/configuring-playbook-bot-baibot.md:201 +#: ../../../docs/configuring-playbook-bot-baibot.md:231 +msgid "Here's an example **addition** to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:160 +#: ../../../docs/configuring-playbook-bot-baibot.md:193 +#: ../../../docs/configuring-playbook-bot-baibot.md:221 +#: ../../../docs/configuring-playbook-bot-baibot.md:251 +msgid "" +"If you'd like to use more than one model, take a look at the [Configuring" +" additional agents (without a preset)](#configuring-additional-agents-" +"without-a-preset) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:162 +#: ../../../docs/configuring-playbook-bot-baibot.md:195 +#: ../../../docs/configuring-playbook-bot-baibot.md:223 +#: ../../../docs/configuring-playbook-bot-baibot.md:253 +msgid "" +"💡 You may also wish to use this new agent for [🤝 Configuring initial " +"default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:164 +msgid "Groq" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:166 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [Groq " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:191 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/groq`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:197 +msgid "Mistral" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:199 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [🇫🇷 Mistral " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:219 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/mistral`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:225 +msgid "OpenAI" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:227 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [OpenAI " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:229 +msgid "" +"The OpenAI provider is **only meant to be used with OpenAI's official " +"API** and compatibility with other services (which do not fully adhere to" +" the OpenAI API spec completely) is limited. **If you're targeting an " +"OpenAI-compatible service**, use the [OpenAI Compatible](#openai-" +"compatible) provider instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:249 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/openai`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:255 +msgid "OpenAI Compatible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:257 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [OpenAI Compatible " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#openai-compatible) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:259 +msgid "" +"This provider allows you to use OpenAI-compatible API services like " +"[OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter)," +" [Together " +"AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#together-ai), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:261 +msgid "" +"Some of these popular services already have **shortcut** providers (see " +"[supported " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#supported-providers) leading to this one behind the scenes - this make " +"it easier to get started." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:263 +msgid "" +"As of this moment, the playbook does not include presets for any of these" +" services, so you'll need to [Configuring additional agents (without a " +"preset)](#configuring-additional-agents-without-a-preset)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:265 +msgid "Configuring additional agents (without a preset)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:267 +msgid "" +"The Ansible role may be lacking preset variables for some [☁️ " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), " +"or you may wish to statically-define an agent on the same provider twice " +"(or more) with different configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:269 +msgid "" +"It's possible to inject your own agent configuration using the " +"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:271 +msgid "" +"You can also define providers at runtime, by chatting with the bot, so " +"using Ansible is not a requirement." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:273 +msgid "" +"Below is an an **example** demonstrating **statically-defining agents via" +" Ansible without using presets**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:312 +msgid "" +"Because these are " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agents, they will be given a `static/` ID " +"prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and " +"`static/my-ollama-agent`, respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:314 +msgid "" +"💡 To figure out what to put in the `config` section, refer to the [☁️ " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " +"page, which contains **sample configuration YAML for each provider**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:316 +msgid "" +"As with any [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), " +"defining them means they exist. To actually make use of them, they need " +"to be configured as handlers globally or in a specific room - see [Mixing" +" & matching " +"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" +"--matching-models)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:318 +msgid "" +"💡 You may also wish to use these new agents for [🤝 Configuring initial " +"default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:320 +msgid "🤝 Configuring initial default handlers" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:322 +msgid "" +"This section is only useful if you're [🤖 Configuring agents via Ansible" +"](#-configuring-agents-via-ansible), as it lets you put these agents to " +"use as soon as the bot starts (by adjusting the bot's **initial global " +"configuration**)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:324 +msgid "If you're not configuring agents via Ansible, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:326 +msgid "" +"This section is only useful the first time around. **Once initially " +"configured the global configuration cannot be managed Ansible**, but only" +" via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:328 +msgid "" +"baibot supports [various " +"purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:330 +msgid "" +"[💬 text-" +"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-text-generation): communicating with you via text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:332 +msgid "" +"[🦻 speech-to-" +"text](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-speech-to-text): turning your voice messages into text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:334 +msgid "" +"[🗣️ text-to-" +"speech](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-text-to-speech): turning bot or users text messages into voice messages" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:336 +msgid "" +"[🖌️ image-" +"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-image-generation): generating images based on instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:338 +msgid "" +"❓ catch-all: special purposes, indicating use as a fallback (when no " +"specific handler is configured)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:340 +msgid "" +"[Mixing & matching " +"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" +"--matching-models) is made possible by the bot's ability to have " +"different [🤝 " +"handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md)" +" configured for different purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:342 +msgid "" +"This configuration can be done as a global fallback, or per-room. Both of" +" these [🛠️ " +"configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md)" +" are managed at runtime (viat chat), but **the global configuration can " +"have some initial defaults configured via Ansible**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:344 +msgid "" +"You can configure the **initial values** for these via Ansible, via the " +"`matrix_bot_baibot_config_initial_global_config_handler_*` variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:346 +msgid "Example **additional** `vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:363 +msgid "" +"**Note**: these are initial defaults for the bot's global configuration. " +"As such, changing any of these values subsequently has no effect on the " +"bot's behavior. **Once initially configured the global configuration " +"cannot be managed Ansible**, but only via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:365 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:367 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:374 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:376 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:378 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:380 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:382 +msgid "" +"If you change the bot password (`matrix_bot_baibot_config_user_password` " +"in your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_baibot_config_user_password` to let the bot know its new " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:384 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:386 +msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:388 +msgid "" +"If you're an allowed bot [👥 " +"user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) " +"(see [👥 Initial users configuration](#-initial-users-configuration)), the" +" bot will accept your invitation and join the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:390 +msgid "" +"After joining, the bot will introduce itself and show information about " +"the [✨ " +"features](https://github.com/etkecc/baibot/blob/main/docs/features.md) " +"that are enabled for it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:392 +msgid "" +"If you've [🤖 configured one or more agents via Ansible](#-configuring-" +"agents-via-ansible) and have [🤝 configured initial default handlers" +"](#configuring-initial-default-handlers), the bot will immediately be " +"able to make use of these agents for this new room. Otherwise, you will " +"need to configure agents and/or handlers via chat commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:394 +msgid "" +"Send `!bai help` to the room at any time to see the bot's help menu for " +"additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:396 +msgid "" +"You can also refer to the upstream " +"[baibot](https://github.com/etkecc/baibot) project's documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:398 +msgid "Debugging" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:400 +msgid "" +"As with all other services, you can find service logs in [systemd-" +"journald](https://www.freedesktop.org/software/systemd/man/systemd-" +"journald.service.html) by running something like `journalctl -fu matrix-" +"bot-baibot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:402 +msgid "" +"The default logging level for this service is `info`, but you can " +"increase it to `debug` (or even `trace`) with the following additional " +"configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:416 +msgid "" +"**Alternatively**, you can use a single variable to set the logging level" +" for all of the above (bot + all libraries):" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po new file mode 100644 index 000000000..5e130d865 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -0,0 +1,188 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-buscarron.md:1 +msgid "Setting up Buscarron (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:3 +msgid "" +"The playbook can install and configure " +"[Buscarron](https://github.com/etkecc/buscarron) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:5 +msgid "" +"Buscarron is bot that receives HTTP POST submissions of web forms and " +"forwards them to a Matrix room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:9 +msgid "" +"To enable Buscarron, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:32 +msgid "Adjusting the Buscarron URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:34 +msgid "" +"By default, this playbook installs Buscarron on the `buscarron.` " +"subdomain (`buscarron.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:36 +msgid "" +"By tweaking the `matrix_bot_buscarron_hostname` and " +"`matrix_bot_buscarron_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:38 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:49 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:51 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Buscarron domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:53 +msgid "" +"By default, you will need to create a CNAME record for `buscarron`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:55 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:57 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:59 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:66 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:68 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:70 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:72 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:74 +msgid "" +"If you change the bot password (`matrix_bot_buscarron_password` in your " +"`vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_buscarron_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:76 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:78 +msgid "" +"To use the bot, invite the `@bot.buscarron:example.com` to the room you " +"specified in a config, after that any point your form to the form url, " +"example for the `contact` form:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:86 +msgid "" +"**Note**: to fight against spam, Buscarron is **very aggressive when it " +"comes to banning** and will ban you if:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:88 +msgid "if you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:89 +msgid "" +"if you submit a form to the wrong URL (`POST` request to `/non-existing-" +"form`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:90 +msgid "" +"if `hasemail` is enabled for the form (like in the example above) and you" +" don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:92 +msgid "" +"If you get banned, you'd need to restart the process by running the " +"playbook with `--tags=start` or running `systemctl restart matrix-bot-" +"buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/buscarron)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po new file mode 100644 index 000000000..0106bfc01 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po @@ -0,0 +1,159 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-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 "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:11 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:13 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:15 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 +msgid "Get an access token and create encryption keys" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:27 +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:29 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:31 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:52 +msgid "You will need to get tokens for ChatGPT." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:56 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 +msgid "" +"To use the bot, invite the `@bot.chatgpt:example.com` to the room you " +"specified in a config, after that start speaking to it, use the prefix if" +" you configured one or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po new file mode 100644 index 000000000..0cd924e1d --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -0,0 +1,553 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-draupnir.md:1 +msgid "Setting up Draupnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:3 +msgid "" +"The playbook can install and configure the [Draupnir](https://github.com" +"/the-draupnir-project/Draupnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:5 +msgid "" +"See the project's [documentation](https://github.com/the-draupnir-" +"project/Draupnir) to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:7 +msgid "" +"This documentation page is about installing Draupnir in bot mode. As an " +"alternative, you can run a multi-instance Draupnir deployment by " +"installing [Draupnir in appservice mode](./configuring-playbook-" +"appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:9 +msgid "If your migrating from Mjolnir skip to step 5b." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:11 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:13 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:25 +msgid "" +"If you would like Draupnir to be able to deactivate users, move aliases, " +"shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc " +"then it must be a server admin so you need to change `admin=no` to " +"`admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:27 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:29 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:31 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:33 +msgid "" +"You will need to prevent Synapse from rate limiting the bot's account. " +"This is not an optional step. If you do not do this step Draupnir will " +"crash. This can be done using Synapse's [admin API](https://matrix-" +"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). Please ask for help if you are uncomfortable " +"with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:35 +msgid "" +"If your Synapse Admin API is exposed to the internet for some reason like" +" running the Synapse Admin Role [Link](configuring-playbook-synapse-" +"admin.md) or running " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true` in your playbook config. If your API is not externally exposed you" +" should still be able to on the local host for your synapse run these " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "" +"The following command works on semi up to date Windows 10 installs and " +"All Windows 11 installations and other systems that ship curl. `curl " +"--header \"Authorization: Bearer \" -X POST " +"https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" +" Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and " +"example.com with your homeserver domain. You can easily obtain an access " +"token for a homeserver admin account the same way you can obtain an " +"access token for Draupnir itself. If you made Draupnir Admin you can just" +" use the Draupnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:41 +msgid "" +"Using your own account, create a new invite only room that you will use " +"to manage the bot. This is the room where you will see the status of the " +"bot and where you will send commands to the bot, such as the command to " +"ban a user from another room. Anyone in this room can control the bot so " +"it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +msgid "" +"If you make the management room encrypted (E2EE), then you MUST enable " +"and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +msgid "" +"Once you have created the room you need to copy the room ID so you can " +"tell the bot to use that room. In Element Web you can do this by going to" +" the room's settings, clicking Advanced, and then copying the internal " +"room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +msgid "" +"Finally invite the `@bot.draupnir:example.com` account you created " +"earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:51 +msgid "" +"Decide whether you want Draupnir to be capable of operating in end-to-end" +" encrypted (E2EE) rooms. This includes the management room and the " +"moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon" +"](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +msgid "" +"When using Pantalaimon, Draupnir will log in to its bot account itself " +"through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:92 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "" +"The playbook's `group_vars` will configure other required settings. If " +"using this role separately without the playbook, you also need to " +"configure the two URLs that Draupnir uses to reach the homeserver, one " +"through Pantalaimon and one \"raw\". This example is taken from the " +"playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +msgid "" +"When NOT using Pantalaimon, Draupnir does not log in by itself and you " +"must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:94 +msgid "" +"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:104 +msgid "c. Migrating from Mjolnir (Only required if migrating.)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:106 +msgid "" +"Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " +"config. Also disable Mjolnir if you're doing migration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:108 +msgid "" +"That is all you need to do due to that Draupnir can complete migration on" +" its own." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:110 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:119 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:121 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:123 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:125 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:127 +msgid "" +"If you change the Pantalaimon's password " +"(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " +"subsequently, its credentials on the homeserver won't be updated " +"automatically. If you'd like to change the password, use a tool like " +"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " +"then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon" +" know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:129 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:131 +msgid "" +"You can refer to the upstream [documentation](https://the-draupnir-" +"project.github.io/draupnir-documentation/) for additional ways to use and" +" configure Draupnir and for a more detailed usage guide." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:133 +msgid "Below is a **non-exhaustive quick-start guide** for the impatient." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:135 +msgid "Making Draupnir join and protect a room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:137 +msgid "" +"Draupnir can be told to self-join public rooms, but it's better to follow" +" this flow which works well for all kinds of rooms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:139 +msgid "" +"Invite the bot to the room manually ([inviting Draupnir to rooms](https" +"://the-draupnir-project.github.io/draupnir-documentation/moderator" +"/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, " +"the bot *may* ask for confirmation in the Management Room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:141 +msgid "" +"[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" +"do-its-job)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:143 +msgid "" +"Tell it to protect the room (using the [rooms command](https://the-" +"draupnir-project.github.io/draupnir-documentation/moderator/managing-" +"protected-rooms#using-the-draupnir-rooms-command)) by sending the " +"following command to the Management Room: `!draupnir rooms add " +"!qporfwt:example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:145 +msgid "" +"To have Draupnir provide useful room protection, you need do to a bit " +"more work (at least the first time around). You may wish to [Subscribe to" +" a public policy list](#subscribing-to-a-public-policy-list), [Create " +"your own own policy and rules](#creating-your-own-policy-lists-and-rules)" +" and [Enabling built-in protections](#enabling-built-in-protections)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:147 +msgid "Giving Draupnir permissions to do its job" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:149 +msgid "" +"For Draupnir to do its job, you need to [give it permissions](https" +"://the-draupnir-project.github.io/draupnir-documentation/moderator" +"/managing-protected-rooms#giving-draupnir-permissions) in rooms it's " +"protecting. This involves **giving it an Administrator power level**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:151 +msgid "" +"**We recommend setting this power level as soon as the bot joins your " +"room** (and before you create new rules), so that it can apply rules as " +"soon as they are available. If the bot is under-privileged, it may fail " +"to apply protections and may not retry for a while (or until your restart" +" it)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:153 +msgid "Subscribing to a public policy list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:155 +msgid "" +"We recommend **subscribing to a public [policy list](https://the-" +"draupnir-project.github.io/draupnir-documentation/concepts/policy-" +"lists)** using the [watch command](https://the-draupnir-project.github.io" +"/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-" +"watch-command-to-subscribe-to-policy-rooms)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:157 +msgid "" +"Polcy lists are maintained in Matrix rooms. A popular policy list is " +"maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:159 +msgid "" +"You can tell Draupnir to subscribe to it by sending the following command" +" to the Management Room: `!draupnir watch #community-moderation-effort-" +"bl:neko.dev`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:161 +msgid "Creating your own policy lists and rules" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:163 +msgid "" +"We also recommend **creating your own policy lists** with the [list " +"create](https://the-draupnir-project.github.io/draupnir-" +"documentation/moderator/managing-policy-lists#using-draupnirs-list-" +"create-command-to-create-a-policy-room) command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +msgid "" +"You can do so by sending the following command to the Management Room: " +"`!draupnir list create my-bans my-bans-bl`. This will create a policy " +"list having a name (shortcode) of `my-bans` and stored in a public `#my-" +"bans-bl:example.com` room on your server. As soon as you run this " +"command, the bot will invite you to the policy list room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +msgid "" +"A policy list does nothing by itself, so the next step is **adding some " +"rules to your policy list**. Policies target a so-called `entity` (one " +"of: `user`, `room` or `server`). These entities are mentioned on the " +"[policy lists](https://the-draupnir-project.github.io/draupnir-" +"documentation/concepts/policy-lists) documentation page and in the Matrix" +" Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-" +"recommendation)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +msgid "" +"The simplest and most useful entity to target is `user`. Below are a few " +"examples using the [ban command](https://the-draupnir-project.github.io" +"/draupnir-documentation/moderator/managing-users#the-ban-command) and " +"targeting users." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +msgid "" +"To create rules, you run commands in the Management Room (**not** in the " +"policy list room)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +msgid "" +"(ban a single user on a given homeserver): `!draupnir ban " +"@charles:example.com my-bans Rude to others`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:174 +msgid "" +"(ban all users on a given homeserver by using a [wildcard](https://the-" +"draupnir-project.github.io/draupnir-documentation/moderator/managing-" +"users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - " +"all users are fake`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:176 +msgid "As a result of running these commands, you may observe:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:178 +msgid "" +"Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" +"bl:example.com` room on your server" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +msgid "" +"applying these rules against all rooms that Draupnir is an Administrator " +"in" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +msgid "" +"You can undo bans with the [unban command](https://the-draupnir-" +"project.github.io/draupnir-documentation/moderator/managing-users#the-" +"unban-command)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +msgid "Enabling built-in protections" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +msgid "" +"You can also **turn on various built-in [protections](https://the-" +"draupnir-project.github.io/draupnir-documentation/protections)** like " +"`JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the " +"room to invite-only\")." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +msgid "" +"To **see which protections are available and which are enabled**, send a " +"`!draupnir protections` command to the Management Room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +msgid "" +"To **see the configuration options for a given protection**, send a " +"`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " +"JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +msgid "" +"To **set a specific option for a given protection**, send a command like " +"this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " +"`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +msgid "" +"To **enable a given protection**, send a command like this: `!draupnir " +"enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +msgid "" +"To **disable a given protection**, send a command like this: `!draupnir " +"disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_draupnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +msgid "" +"For example to change Draupnir's `recordIgnoredInvites` option to `true` " +"you would add the following to your `vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +msgid "Abuse Reports" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +msgid "" +"The first method intercepts the report API endpoint of the client-server " +"API, which requires integration with the reverse proxy in front of the " +"homeserver. If you are using traefik, this playbook can set this up for " +"you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:225 +msgid "" +"The other method polls an synapse admin API endpoint and is hence only " +"available when using synapse and when the Draupnir user is an admin user " +"(see step 1). To enable it, set `pollReports: true` in Draupnir's config:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po new file mode 100644 index 000000000..ac819c836 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po @@ -0,0 +1,206 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:1 +msgid "Setting up Go-NEB (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:3 +msgid "" +"**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an " +"archived (**unmaintained**) project. We recommend not bothering with " +"installing it. While not a 1:1 replacement, the bridge's author suggests " +"taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) as a replacement, which can also be installed using [this " +"playbook](configuring-playbook-bridge-hookshot.md). Consider using that " +"bot instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:5 +msgid "" +"The playbook can install and configure [Go-NEB](https://github.com" +"/matrix-org/go-neb) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:7 +msgid "" +"Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, " +"the original Matrix bot written in Python." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/go-neb) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:11 +msgid "Registering the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:13 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires at least 1 access token to be able to connect to your " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:25 +msgid "" +"Once the user is created you can [obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:29 +msgid "" +"To enable Go-NEB, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:193 +msgid "Adjusting the Go-NEB URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:195 +msgid "" +"By default, this playbook installs Go-NEB on the `goneb.` subdomain " +"(`goneb.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:197 +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:199 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Go-NEB domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +msgid "" +"By default, you will need to create a CNAME record for `goneb`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +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:218 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +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:227 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +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:231 +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:233 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"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:235 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +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:239 +msgid "" +"Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy " +"matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 +msgid "" +"If you enabled the github_cmd service you can get the supported commands " +"via `!github help`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +msgid "" +"You can also refer to the upstream [Documentation](https://github.com" +"/matrix-org/go-neb)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po new file mode 100644 index 000000000..f0140fabc --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -0,0 +1,169 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bot-honoroit.md:1 +msgid "Setting up Honoroit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:3 +msgid "" +"The playbook can install and configure " +"[Honoroit](https://github.com/etkecc/honoroit) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:5 +msgid "It's a bot you can use to setup **your own helpdesk on matrix**" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:7 +msgid "" +"See the project's [documentation](https://github.com/etkecc/honoroit#how-" +"it-looks-like) to learn what it does with screenshots and why it might be" +" useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:11 +msgid "" +"To enable Honoroit, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:26 +msgid "Adjusting the Honoroit URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:28 +msgid "" +"By default, this playbook installs Honoroit on the `matrix.` subdomain, " +"at the `/honoroit` path (https://matrix.example.com/honoroit). This makes" +" it easy to install it, because it **doesn't require additional DNS " +"records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:30 +msgid "" +"By tweaking the `matrix_bot_honoroit_hostname` and " +"`matrix_bot_honoroit_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:32 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:42 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:46 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:50 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:59 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:65 +msgid "" +"If you change the bot password (`matrix_bot_honoroit_password` in your " +"`vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_honoroit_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:69 +msgid "" +"To use the bot, invite the `@honoroit:example.com` to the room you " +"specified in config, after that any Matrix user can send a message to the" +" `@honoroit:example.com` to start a new thread in that room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:71 +msgid "" +"Send `!ho help` to the room to see the bot's help menu for additional " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/honoroit#features)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po new file mode 100644 index 000000000..ecb6fe7c7 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -0,0 +1,148 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-matrix-registration-bot.md:1 +msgid "Setting up matrix-registration-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3 +msgid "" +"The playbook can install and configure [matrix-registration-" +"bot](https://github.com/moan0s/matrix-registration-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5 +msgid "" +"The bot allows you to easily **create and manage registration tokens** " +"aka. invitation codes. It can be used for an invitation-based server, " +"where you invite someone by sending them a registration token (tokens " +"look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but " +"have to provide a valid registration token in the final step of the " +"registration process." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 +msgid "" +"See the project's [documentation](https://github.com/moan0s/matrix-" +"registration-bot#supported-commands) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 +msgid "" +"To enable the bot, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30 +msgid "The bot account will be created automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49 +msgid "" +"If you change the bot password " +"(`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` " +"file) subsequently, the bot user's credentials on the homeserver won't be" +" updated automatically. If you'd like to change the bot user's password, " +"use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to" +" change it, and then update " +"`matrix_bot_matrix_registration_bot_bot_password` to let the bot know its" +" new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53 +msgid "" +"To use the bot, start a chat with `@bot.matrix-registration-" +"bot:example.com` (where `example.com` is your base domain, not the " +"`matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 +msgid "In this room send `help` and the bot will reply with all options." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 +msgid "" +"You can also refer to the upstream [Usage " +"documentation](https://github.com/moan0s/matrix-registration-bot" +"#supported-commands)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59 +msgid "" +"If you have any questions, or if you need help setting it up, read the " +"[troublshooting guide](https://github.com/moan0s/matrix-registration-" +"bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-" +"bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61 +msgid "" +"To clean the cache (session & encryption data) after you changed the " +"bot's username, changed the login method from access_token to password " +"etc… you can use:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po new file mode 100644 index 000000000..6bb4c05e2 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -0,0 +1,136 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-matrix-reminder-bot.md:1 +msgid "Setting up matrix-reminder-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3 +msgid "" +"The playbook can install and configure [matrix-reminder-" +"bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5 +msgid "" +"It's a bot you can use to **schedule one-off & recurring reminders and " +"alarms**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 +msgid "" +"See the project's [documentation](https://github.com/anoadragon453" +"/matrix-reminder-bot#usage) to learn what it does and why it might be " +"useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43 +msgid "" +"If you change the bot password " +"(`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml`" +" file) subsequently, the bot user's credentials on the homeserver won't " +"be updated automatically. If you'd like to change the bot user's " +"password, use a tool like [synapse-admin](configuring-playbook-synapse-" +"admin.md) to change it, and then update " +"`matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know" +" its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47 +msgid "" +"To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49 +msgid "" +"You can also add the bot to any existing Matrix room (`/invite @bot" +".matrix-reminder-bot:example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51 +msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53 +msgid "" +"Send `!help reminders` to the room to see the bot's help menu for " +"additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55 +msgid "" +"You can also refer to the upstream [Usage " +"documentation](https://github.com/anoadragon453/matrix-reminder-" +"bot#usage)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po new file mode 100644 index 000000000..cea5eba6f --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -0,0 +1,214 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bot-maubot.md:1 +msgid "Setting up maubot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:3 +msgid "" +"The playbook can install and configure " +"[maubot](https://github.com/maubot/maubot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:5 +msgid "" +"After setting up maubot, you can use the web management interface to make" +" it do things. The default location of the management interface is " +"`matrix.example.com/_matrix/maubot/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn " +"what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:11 +msgid "" +"To enable maubot, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:26 +msgid "" +"You can add multiple admins. The admin accounts are only used to access " +"the maubot administration interface." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:28 +msgid "Adjusting the maubot URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:30 +msgid "" +"By default, this playbook installs maubot on the `matrix.` subdomain, at " +"the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/)." +" This makes it easy to install it, because it **doesn't require " +"additional DNS records to be set up**. If that's okay, you can skip this " +"section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:32 +msgid "" +"By tweaking the `matrix_bot_maubot_hostname` and " +"`matrix_bot_maubot_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:44 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the maubot domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:48 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.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-bot-maubot.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:61 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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-bot-maubot.md:67 +msgid "" +"If you change the bot password (`matrix_bot_maubot_initial_password` in " +"your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_maubot_initial_password` to let the bot know its new " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:69 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:71 +msgid "" +"By default, you can visit `matrix.example.com/_matrix/maubot/` to manage " +"your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:73 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:74 +msgid "" +"**Create one or more clients**: A client is a Matrix account which the " +"bot will use to message. By default, the playbook creates a `bot.maubot` " +"account (as per the configuration above). You only need to [obtain an " +"access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:75 +msgid "" +"**Upload some Plugins**: Plugins can be obtained from " +"[here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:76 +msgid "" +"**Create an instance**: An instance is the actual bot. You have to " +"specify a client which the bot instance will use and the plugin (how the " +"bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:78 +msgid "Obtaining an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:80 +msgid "" +"This can be done via `mbc login` then `mbc auth` (see the [maubot " +"documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run " +"these commands, you'll first need to `exec` into the maubot container " +"with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:82 +msgid "" +"Alternatively, you can follow our generic [obtain an access token" +"](obtaining-access-tokens.md) documentation. Be aware that you'd better " +"use the **Obtain an access token via curl** method (not **Obtain an " +"access token via Element Web**) as the latter will give your bot issues " +"in encrypted rooms. Read " +"[more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po new file mode 100644 index 000000000..abfc1d669 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -0,0 +1,282 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-mjolnir.md:1 +msgid "Setting up Mjolnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:3 +msgid "" +"The playbook can install and configure the [Mjolnir](https://github.com" +"/matrix-org/mjolnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/mjolnir) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:7 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:9 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:11 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:13 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:15 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:21 +msgid "" +"If you would like Mjolnir to be able to deactivate users, move aliases, " +"shutdown rooms, etc then it must be a server admin so you need to change " +"`admin=no` to `admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:23 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:25 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:27 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:29 +msgid "" +"You will need to prevent Synapse from rate limiting the bot's account. " +"This is not an optional step. If you do not do this step Mjolnir will " +"crash. This can be done using Synapse's [admin API](https://matrix-" +"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). Please ask for help if you are uncomfortable " +"with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:31 +msgid "" +"If your Synapse Admin API is exposed to the internet for some reason like" +" running the Synapse Admin Role [Link](configuring-playbook-synapse-" +"admin.md) or running " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true` in your playbook config. If your API is not externally exposed you" +" should still be able to on the local host for your synapse run these " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "" +"The following command works on semi up to date Windows 10 installs and " +"All Windows 11 installations and other systems that ship curl. `curl " +"--header \"Authorization: Bearer \" -X POST " +"https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" +" Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and " +"example.com with your homeserver domain. You can easily obtain an access " +"token for a homeserver admin account the same way you can obtain an " +"access token for Mjolnir itself. If you made Mjolnir Admin you can just " +"use the Mjolnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 +msgid "" +"Using your own account, create a new invite only room that you will use " +"to manage the bot. This is the room where you will see the status of the " +"bot and where you will send commands to the bot, such as the command to " +"ban a user from another room. Anyone in this room can control the bot so " +"it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +msgid "" +"If you make the management room encrypted (E2EE), then you MUST enable " +"and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +msgid "" +"Once you have created the room you need to copy the room ID so you can " +"tell the bot to use that room. In Element Web you can do this by going to" +" the room's settings, clicking Advanced, and then copying the internal " +"room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +msgid "" +"Finally invite the `@bot.mjolnir:example.com` account you created earlier" +" into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 +msgid "" +"Decide whether you want Mjolnir to be capable of operating in end-to-end " +"encrypted (E2EE) rooms. This includes the management room and the " +"moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon" +"](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +msgid "" +"When using Pantalaimon, Mjolnir will log in to its bot account itself " +"through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "" +"The playbook's `group_vars` will configure other required settings. If " +"using this role separately without the playbook, you also need to " +"configure the two URLs that Mjolnir uses to reach the homeserver, one " +"through Pantalaimon and one \"raw\". This example is taken from the " +"playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +msgid "" +"When NOT using Pantalaimon, Mjolnir does not log in by itself and you " +"must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 +msgid "" +"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +msgid "Adding Mjolnir synapse antispam module (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 +msgid "" +"If you change the Pantalaimon's password " +"(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " +"subsequently, its credentials on the homeserver won't be updated " +"automatically. If you'd like to change the password, use a tool like " +"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " +"then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon " +"know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 +msgid "" +"You can refer to the upstream [documentation](https://github.com/matrix-" +"org/mjolnir) for additional ways to use and configure Mjolnir. Check out " +"their [quickstart guide](https://github.com/matrix-org/mjolnir" +"#quickstart-guide) for some basic commands you can give to the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 +msgid "" +"For example to change Mjolnir's `recordIgnoredInvites` option to `true` " +"you would add the following to your `vars.yml` file." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po new file mode 100644 index 000000000..5eeec1393 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po @@ -0,0 +1,247 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-discord.md:1 +msgid "Setting up Appservice Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" +"discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-" +"discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 +msgid "" +"For using as a Bot we are recommend the Appservice Discord bridge (the " +"one being discussed here), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 +msgid "" +"For personal use we recommend the [mautrix-discord](configuring-playbook-" +"bridge-mautrix-discord.md) bridge, because it is the most fully-featured " +"and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"discord](https://github.com/matrix-org/matrix-appservice-discord) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-discord/blob/master/README.md) to learn what it does and why " +"it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 +msgid "" +"Create a Discord Application " +"[here](https://discordapp.com/developers/applications). Then retrieve " +"Client ID, and create a bot from the Bot tab and retrieve the Bot token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 +msgid "Self-Service Bridging (Manual)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 +msgid "" +"Self-service bridging allows you to bridge specific and existing Matrix " +"rooms to specific Discord rooms. To enable it, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 +msgid "" +"**Note**: If self-service bridging is not enabled, `!discord help` " +"commands will return no results." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 +msgid "" +"Once self-service is enabled, start a chat with " +"`@_discord_bot:example.com` and say `!discord help bridge`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 +msgid "Then, follow the instructions in the help output message." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 +msgid "" +"If the bot is not already in the Discord server, follow the provided " +"invite link. This may require you to be a administrator of the Discord " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 +msgid "" +"On the Discord side, you can say `!matrix help` to get a list of " +"available commands to manage the bridge and Matrix users." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 +msgid "**Note**: Encrypted Matrix rooms are not supported as of writing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70 +msgid "Portal Bridging (Automatic)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 +msgid "" +"Through portal bridging, Matrix rooms will automatically be created by " +"the bot and bridged to the relevant Discord room. This is done by simply " +"joining a room with a specific name pattern " +"(`#_discord__`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74 +msgid "" +"All Matrix rooms created this way are **listed publicly** by default, and" +" you will not have admin permissions to change this. To get more control," +" [make yourself a room Administrator](#getting-administrator-access-in-a" +"-portal-bridged-room). You can then unlist the room from the directory " +"and change the join rules." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 +msgid "" +"To disable portal bridging, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 +msgid "To get started with Portal Bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 +msgid "" +"To invite the bot to Discord, retrieve the invite link from the `{{ " +"matrix_appservice_discord_config_path }}/invite_link` file on the server " +"(this defaults to `/matrix/appservice-discord/config/invite_link`). You " +"need to peek at the file on the server via SSH, etc., because it's not " +"available via HTTP(S)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 +msgid "" +"Room addresses follow this syntax: `#_discord__`. 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: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:90 +msgid "Getting Administrator access in a portal bridged room" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 +msgid "" +"By default, you won't have Administrator access in rooms created by the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 +msgid "" +"To adjust room access privileges or do various other things (change the " +"room name subsequently, etc.), you'd wish to become an Administrator." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 +msgid "" +"There's the Discord bridge's guide for [setting privileges on bridge " +"managed rooms](https://github.com/matrix-org/matrix-appservice-" +"discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-" +"rooms). To do the same with our container setup, run the following " +"command on the server:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po new file mode 100644 index 000000000..2f33fd7f5 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po @@ -0,0 +1,103 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-irc.md:1 +msgid "Setting up Appservice IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 +msgid "" +"**Note**: bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " +"via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) " +"bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 +msgid "" +"The playbook can install and configure the [matrix-appservice-" +"irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-irc/blob/master/HOWTO.md) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 +msgid "" +"To use the bridge, you need to start a chat with `@irc_bot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po new file mode 100644 index 000000000..6f6d15853 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po @@ -0,0 +1,230 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-kakaotalk.md:1 +msgid "Setting up Appservice Kakaotalk bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) " +"for you. `matrix-appservice-kakaotalk` is a bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +" based on [node-kakao](https://github.com/storycraft/node-kakao) (now " +"unmaintained) and some [mautrix-" +"facebook](https://github.com/mautrix/facebook) code." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 +msgid "" +"⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using" +" this bridge may get your account banned**." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 +msgid "" +"See the project's [documentation](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk) to learn what it does and why it might be useful to" +" you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 +msgid "" +"`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for " +"some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 +msgid "" +"`roles/custom/matrix-bridge-appservice-" +"kakaotalk/templates/config.yaml.j2` for the bridge's default " +"configuration. You can override settings (even those that don't have " +"dedicated playbook variables) using the " +"`matrix_appservice_kakaotalk_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:49 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53 +msgid "" +"To use the bridge, you need to start a chat with " +"`@kakaotalkbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55 +msgid "" +"Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable " +"bridging for your Kakaotalk account. The `--save` flag may be omitted, if" +" you'd rather not save your password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77 +msgid "" +"make sure you don't log out the `Appservice-Kakaotalk` device some time " +"in the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po new file mode 100644 index 000000000..387f43882 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po @@ -0,0 +1,326 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-slack.md:1 +msgid "Setting up Appservice Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3 +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4 +msgid "" +"Bridging to [Slack](https://slack.com) can also happen via the [mx-" +"puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " +"[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges " +"supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5 +msgid "" +"Currently (as of November, 2024) **this component is not available for " +"new installation unless you have already created a classic Slack " +"application** (which the bridge makes use of in order to enable bridging " +"between Slack and Matrix), because the creation of classic Slack " +"applications has been discontinued since June 4 2024. The author of the " +"bridge claims [here](https://github.com/matrix-org/matrix-appservice-" +"slack/issues/789#issuecomment-2172947787) that he plans to support the " +"modern Slack application and until then \"the best (and only) option for " +"new installations is to use the webhook bridging\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-slack/blob/master/README.md) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13 +msgid "Create a Classic Slack App" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15 +msgid "" +"First, you need to create a Classic Slack App " +"[here](https://api.slack.com/apps?new_classic_app=1)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17 +msgid "" +"Name the app \"matrixbot\" (or anything else you'll remember). Select the" +" team/workspace this app will belong to. Click on bot users and add a new" +" bot user. We will use this account to bridge the the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19 +msgid "" +"Then, click on Event Subscriptions and enable them and use the request " +"url: `https://matrix.example.com/appservice-slack`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21 +msgid "Add the following events as `Bot User Events` and save:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23 +msgid "team_domain_change" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 +msgid "message.channels" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25 +msgid "message.groups (if you want to bridge private channels)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 +msgid "reaction_added" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27 +msgid "reaction_removed" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29 +msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31 +msgid "chat:write:bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32 +msgid "users:read" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33 +msgid "reactions:write" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34 +msgid "files:write:user (if you want to bridge files)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36 +msgid "" +"**Note**: In order to make Slack files visible to Matrix users, this " +"bridge will make Slack files visible to anyone with the url (including " +"files in private channels). This is different than the current behavior " +"in Slack, which only allows authenticated access to media posted in " +"private channels. See MSC701 for details." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38 +msgid "" +"Click on \"Install App\" and \"Install App to Workspace\". Note the " +"access tokens shown. You will need the Bot User OAuth Access Token and if" +" you want to bridge files, the OAuth Access Token whenever you link a " +"room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40 +msgid "Create an administration control room on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42 +msgid "Create a new Matrix room to act as the administration control room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44 +msgid "" +"Note its internal room ID. This can be done in Element Web by sending a " +"message, opening the options for that message and choosing \"view " +"source\". The room ID will be displayed near the top." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 +msgid "" +"Other configuration options are available via the " +"`matrix_appservice_slack_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85 +msgid "" +"To use the bridge, you need to send `/invite @slackbot:example.com` to " +"invite the bridge bot user into the admin room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87 +msgid "" +"If Team Sync is not enabled, for each channel you would like to bridge, " +"perform the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 +msgid "" +"Create a Matrix room in the usual manner for your client. Take a note of " +"its Matrix room ID - it will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90 +msgid "" +"Invite the bot user to both the Slack and Matrix channels you would like " +"to bridge using `/invite @matrixbot` for Slack and `/invite " +"@slackbot:example.com` for Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 +msgid "" +"Determine the \"channel ID\" that Slack uses to identify the channel. You" +" can see it when you open a given Slack channel in a browser. The URL " +"reads like this: `https://app.slack.com/client/XXX//details/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:92 +msgid "" +"Issue a link command in the administration control room with these " +"collected values as arguments:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94 +msgid "with file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100 +msgid "without file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106 +msgid "These arguments can be shortened to single-letter forms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112 +msgid "Unlinking" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114 +msgid "Channels can be unlinked again by sending this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 +msgid "" +"Unlinking doesn't only disconnect the bridge, but also makes the slackbot" +" leave the bridged Matrix room. So in case you want to re-link later, " +"don't forget to re-invite the slackbot into this room again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124 +msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126 +msgid "Linking: \"Room is now pending-name\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 +msgid "" +"This typically means that you haven't used the correct Slack channel ID. " +"Unlink the room and recheck 'Determine the \"channel ID\"' from above." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130 +msgid "Messages work from Matrix to Slack, but not the other way around" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132 +msgid "Check you logs, if they say something like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 +#, python-format +msgid "" +"`WARN SlackEventHandler Ignoring message from unrecognised Slack channel " +"ID : %s (%s) `" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136 +msgid "" +"then unlink your room, reinvite the bot and re-link it again. This may " +"particularly hit you, if you tried to unsuccessfully link your room " +"multiple times without unlinking it after each failed attempt." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po new file mode 100644 index 000000000..27a70d5b4 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-webhooks.md:1 +msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 +msgid "" +"**Note**: This bridge has been deprecated. We recommend not bothering " +"with installing it. While not a 1:1 replacement, the bridge's author " +"suggests taking a look at [matrix-hookshot](https://github.com/matrix-org" +"/matrix-hookshot) as a replacement, which can also be installed using " +"[this playbook](configuring-playbook-bridge-hookshot.md). Consider using " +"that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for " +"you. This bridge provides support for Slack-compatible webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 +msgid "" +"See the project's [documentation](https://github.com/turt2live/matrix-" +"appservice-webhooks/blob/master/README.md) to learn what it does and why " +"it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:42 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46 +msgid "" +"To use the bridge, you need to invite the bridge bot user to your room in" +" either way." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48 +msgid "" +"Send `/invite @_webhook:example.com` (**Note**: Make sure you have " +"administration permissions in your room)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49 +msgid "" +"Add the bridge bot to a private channel (personal channels imply you " +"being an administrator)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 +msgid "" +"You then need to send a message to the bridge bot in order to receive a " +"private message including the webhook link:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 +msgid "The JSON body for posting messages will have to look like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68 +msgid "You can test this via curl like so:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81 +msgid "Setting Webhooks with Dimension integration manager" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83 +msgid "" +"If you're using the [Dimension integration manager](configuring-playbook-" +"dimension.md), you can configure the Webhooks bridge with it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85 +msgid "" +"To configure it, open the Dimension integration manager, and go to " +"\"Settings\" and \"Bridges\", then select edit action for \"Webhook " +"Bridge\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87 +msgid "" +"On the UI, press \"Add self-hosted Bridge\" button and populate " +"\"Provisioning URL\" and \"Shared Secret\" values from `/matrix" +"/appservice-webhooks/config/config.yaml` file's homeserver URL value and " +"provisioning secret value, respectively." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po new file mode 100644 index 000000000..1b533e49e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po @@ -0,0 +1,188 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-beeper-linkedin.md:1 +msgid "Setting up Beeper Linkedin bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 +msgid "" +"The playbook can install and configure [beeper-" +"linkedin](https://github.com/beeper/linkedin) for you, for bridging to " +"[LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on " +"the mautrix-python framework and can be configured in a similar way to " +"the other mautrix bridges" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 +msgid "" +"See the project's " +"[documentation](https://github.com/beeper/linkedin/blob/master/README.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-beeper-" +"linkedin/templates/config.yaml.j2` to find other things you would like to" +" configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 +msgid "" +"Set up Double Puppeting by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 +msgid "" +"To use the bridge, you need to start a chat with " +"`@linkedinbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 +msgid "" +"Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable " +"bridging for your LinkedIn account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 +msgid "" +"After successfully enabling bridging, you may wish to [set up Double " +"Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-" +"or-shared-secret-auth), if you haven't already done so." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72 +msgid "Bridge asking for 2FA even if you don't have 2FA enabled" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 +msgid "" +"If you don't have 2FA enabled and are logging in from a strange IP for " +"the first time, LinkedIn will send an email with a one-time code. You can" +" use this code to authorize the bridge session. In my experience, once " +"the IP is authorized, you will not be asked again." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po new file mode 100644 index 000000000..47df023ab --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po @@ -0,0 +1,100 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-go-skype-bridge.md:1 +msgid "Setting up Go Skype Bridge bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 +msgid "" +"The playbook can install and configure [go-skype-" +"bridge](https://github.com/kelaresg/go-skype-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 +msgid "" +"To enable the [Skype](https://www.skype.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Skype bridge bot` with " +"the handle `@skypebridgebot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 +msgid "Send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po new file mode 100644 index 000000000..0edf49773 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po @@ -0,0 +1,185 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-heisenbridge.md:1 +msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 +msgid "" +"**Note**: bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " +"via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-" +"irc.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 +msgid "" +"The playbook can install and configure " +"[Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 +msgid "" +"See the project's " +"[README](https://github.com/hifi/heisenbridge/blob/master/README.md) to " +"learn what it does and why it might be useful to you. You can also take a" +" look at [this demonstration " +"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 +msgid "" +"To enable Heisenbridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24 +msgid "" +"For a more complete list of variables that you could override, see the " +"[`defaults/main.yml` file](../roles/custom/matrix-bridge-" +"heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26 +msgid "Adjusting the Heisenbridge URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28 +msgid "" +"By default, this playbook installs Heisenbridge on the `matrix.` " +"subdomain, at the `/heisenbridge` path " +"(https://matrix.example.com/heisenbridge). It would handle media requests" +" there (see the [release notes for Heisenbridge " +"v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 +msgid "" +"This makes it easy to install it, because it **doesn't require additional" +" DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 +msgid "" +"By tweaking the `matrix_heisenbridge_hostname` and " +"`matrix_heisenbridge_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Heisenbridge domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 +msgid "" +"To use the bridge, you need to start a chat with " +"`@heisenbridge:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain). If the bridge ignores you and a DM is not " +"accepted then the owner setting may be wrong." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 +msgid "Help is available for all commands with the `-h` switch." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 +msgid "" +"You can also learn the basics by watching [this demonstration " +"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 +msgid "" +"If you encounter issues or feel lost you can join the project room at " +"[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po new file mode 100644 index 000000000..dfb2b601d --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po @@ -0,0 +1,485 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-hookshot.md:1 +msgid "Setting up matrix-hookshot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:3 +msgid "" +"The playbook can install and configure [matrix-" +"hookshot](https://github.com/matrix-org/matrix-hookshot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:5 +msgid "" +"Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " +"from software project management services such as GitHub, GitLab, JIRA, " +"and Figma, as well as generic webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:7 +msgid "" +"See the project's [documentation](https://matrix-org.github.io/matrix-" +"hookshot/latest/hookshot.html) to learn what it does in detail and why it" +" might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:9 +msgid "" +"**Note**: the playbook also supports [matrix-appservice-webhooks" +"](configuring-playbook-bridge-appservice-webhooks.md), which however was " +"deprecated by its author." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 +msgid "Setup Instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 +msgid "" +"Refer to the [official instructions](https://matrix-org.github.io/matrix-" +"hookshot/latest/setup.html) to learn what the individual options do." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 +msgid "" +"Enable the bridge by adding `matrix_hookshot_enabled: true` to your " +"`vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 +msgid "" +"For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) " +"fill in the respective variables `matrix_hookshot_service_*` listed in " +"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as " +"required." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 +msgid "" +"Take special note of the `matrix_hookshot_*_enabled` variables. Services " +"that need no further configuration are enabled by default (GitLab, " +"Generic), while you must first add the required configuration and enable " +"the others (GitHub, Jira, Figma)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 +msgid "" +"If you're setting up the GitHub bridge, you'll need to generate and " +"download a private key file after you created your GitHub app. Copy the " +"contents of that file to the variable " +"`matrix_hookshot_github_private_key` so the playbook can install it for " +"you, or use one of the [other methods](#manage-github-private-key-with-" +"aux-role) explained below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 +msgid "" +"If you've already installed Matrix services using the playbook before, " +"you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with" +" [configuring other playbook services](configuring-playbook.md) and then " +"with [Installing](installing.md). Get back to this guide once ready. " +"Hookshot can be set up individually using the tag `setup-hookshot`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 +msgid "" +"Other configuration options are available via the " +"`matrix_hookshot_configuration_extension_yaml` and " +"`matrix_hookshot_registration_extension_yaml` variables, see the comments" +" in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) " +"for how to use them." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 +msgid "Finally, run the playbook (see [installing](installing.md))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 +msgid "End-to-bridge encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +msgid "" +"You can enable [encryption](https://matrix-org.github.io/matrix-" +"hookshot/latest/advanced/encryption.html) for Hookshot by adding " +"`matrix_hookshot_encryption_enabled: true` to your configuration " +"(`vars.yml`) and [executing the playbook](installing.md) again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 +msgid "" +"Should the crypto store be corrupted, you can reset it by executing this " +"Ansible playbook with the tag `reset-hookshot-encryption` added, for " +"example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-" +"hookshot-encryption`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 +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:35 +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:37 +msgid "Send a `!hookshot help` message to see a list of help commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +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:41 +msgid "" +"**Important**: Note that the different listeners are bound to certain " +"paths which might differ from those assumed by the hookshot " +"documentation, see [URLs for bridges setup](#urls-for-bridges-setup) " +"below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +msgid "More setup documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +msgid "URLs for bridges setup" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +msgid "" +"Unless indicated otherwise, the following endpoints are reachable on your" +" `matrix.` subdomain (if the feature is enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "listener" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "default path" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "used as" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_webhook_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Webhook-prefix, which affects all webhook-related URLs below" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "generic" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_generic_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Generic webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "github oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_github_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "GitHub \"Callback URL\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "jira oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/jira/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_jira_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "JIRA OAuth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "figma endpoint" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/figma/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_figma_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Figma" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "provisioning" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/v1/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_provisioning_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Dimension [provisioning](#provisioning-api)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "appservice" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/_matrix/app/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_appservice_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Matrix server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/widgetapi/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_widgets_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/metrics/hookshot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "" +"`matrix_hookshot_metrics_enabled` and exposure enabled via " +"`matrix_hookshot_metrics_proxying_enabled` or " +"`matrix_metrics_exposure_enabled`. Read more in the [Metrics " +"section](#metrics) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Prometheus" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +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:63 +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:65 +msgid "Manage GitHub Private Key with aux role" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +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:68 +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:69 +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:70 +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:72 +msgid "" +"To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" +" variable is empty. Then add the following additional configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +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:85 +msgid "Provisioning API" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 +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:89 +msgid "Metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +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:93 +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:95 +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:97 +msgid "" +"either enabling metrics exposure for Hookshot via " +"`matrix_hookshot_metrics_proxying_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 +msgid "" +"or enabling metrics exposure for all services via " +"`matrix_metrics_exposure_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 +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:102 +msgid "Collision with matrix-appservice-webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +msgid "" +"If you are also running [matrix-appservice-webhooks](configuring-" +"playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" +" default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. " +"You should take care if you modify its or hookshot's prefix that they do " +"not collide with each other's namespace (default " +"`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po new file mode 100644 index 000000000..ef36a1e26 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po @@ -0,0 +1,101 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-matrix-bridge-sms.md:1 +msgid "Setting up Matrix SMS bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 +msgid "" +"The playbook can install and configure [matrix-sms-" +"bridge](https://github.com/benkuly/matrix-sms-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 +msgid "" +"**The bridge uses [android-sms-gateway-" +"server](https://github.com/RebekkaMa/android-sms-gateway-server). You " +"need to configure it first.**" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 +msgid "" +"Read the [user guide](https://github.com/benkuly/matrix-sms-" +"bridge/blob/master/README.md#user-guide) to see how this bridge works." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po new file mode 100644 index 000000000..270019a1f --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po @@ -0,0 +1,353 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-discord.md:1 +msgid "Setting up Mautrix Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" +"discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-" +"appservice-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Discord](configuring-" +"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 +msgid "" +"For personal use with a discord account we recommend the `mautrix-" +"discord` bridge (the one being discussed here), because it is the most " +"fully-featured and stable of the 3 Discord bridges supported by the " +"playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7 +msgid "" +"The playbook can install and configure [mautrix-" +"discord](https://github.com/mautrix/discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/discord/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 +msgid "" +"There are 2 ways to login to discord using this bridge, either by " +"[scanning a QR code](#method-1-login-using-qr-code-recommended) using the" +" Discord mobile app **or** by using a [Discord token](#method-2-login-" +"using-discord-token-not-recommended)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +msgid "" +"If this is a dealbreaker for you, consider using one of the other Discord" +" bridges supported by the playbook: [mx-puppet-discord](configuring-" +"playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord" +"](configuring-playbook-bridge-appservice-discord.md). These come with " +"their own complexity and limitations, however, so we recommend that you " +"proceed with this one if possible." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 +msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 +msgid "" +"`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some " +"variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 +msgid "" +"`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for" +" the bridge's default configuration. You can override settings (even " +"those that don't have dedicated playbook variables) using the " +"`matrix_mautrix_discord_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:55 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 +msgid "Logging in" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63 +msgid "Method 1: Login using QR code (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 +msgid "" +"For using this bridge, you would need to authenticate by **scanning a QR " +"code** with the Discord app on your phone." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 +msgid "You can delete the Discord app after the authentication process." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69 +msgid "Method 2: Login using Discord token (not recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 +msgid "" +"To acquire the token, open Discord in a private browser window. Then open" +" the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or " +"by pressing \"F12\"). Navigate to the \"Network\" tab then reload the " +"page. In the URL filter or search bar type \"/api\" and find the response" +" with the file name of \"library\". Under the request headers you should " +"find a variable called \"Authorization\", this is the token to your " +"Discord account. After copying the token, you can close the browser " +"window." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 +msgid "Bridging" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 +msgid "" +"Start a chat with `@discordbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:76 +msgid "" +"If you would like to login to Discord using a token, send `login-token` " +"command, otherwise, send `login-qr` command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77 +msgid "" +"You'll see a QR code which you need to scan with the Discord app on your " +"phone. You can scan it with the camera app too, which will open Discord, " +"which will then instruct you to scan it a 2nd time in the Discord app." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78 +msgid "" +"After confirming (in the Discord app) that you'd like to allow this " +"login, the bot should respond with \"Succcessfully authenticated as …\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 +msgid "" +"Now that you're logged in, you can send a `help` command to the bot " +"again, to see additional commands you have access to" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 +msgid "Some Direct Messages from Discord should start syncing automatically" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81 +msgid "If you'd like to bridge guilds:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82 +msgid "send `guilds status` to see the list of guilds" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83 +msgid "" +"for each guild that you'd like bridged, send `guilds bridge GUILD_ID " +"--entire`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84 +msgid "" +"You may wish to uninstall the Discord app from your phone now. It's not " +"needed for the bridge to function." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108 +msgid "" +"make sure you don't log out the `Mautrix-Discord` device some time in the" +" future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po new file mode 100644 index 000000000..bb76624e0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po @@ -0,0 +1,287 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-facebook.md:1 +msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 +msgid "" +"**Note**: This bridge has been deprecated in favor of the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " +"can be installed using [this playbook](configuring-playbook-bridge-" +"mautrix-meta-messenger.md). Consider using that bridge instead of this " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"facebook](https://github.com/mautrix/facebook) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 +msgid "" +"See the project's " +"[documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 +msgid "Using both would look like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-facebook/defaults/main.yml` to find other things you would like " +"to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:73 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77 +msgid "" +"To use the bridge, you need to start a chat with " +"`@facebookbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79 +msgid "" +"Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable " +"bridging for your Facebook Messenger account. You can learn more here " +"about authentication from the bridge's [official documentation on " +"Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103 +msgid "" +"make sure you don't log out the `Mautrix-Facebook` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107 +msgid "Facebook rejecting login attempts and forcing you to change password" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109 +msgid "" +"If your Matrix server is in a wildly different location than where you " +"usually use your Facebook account from, the bridge's login attempts may " +"be outright rejected by Facebook. Along with that, Facebook may even " +"force you to change the account's password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111 +msgid "" +"If you happen to run into this problem while [setting up " +"bridging](#usage), try to first get a successful session up by logging in" +" to Facebook through the Matrix server's IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113 +msgid "" +"The easiest way to do this may be to use " +"[sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic " +"through the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115 +msgid "Example command for proxying your traffic through the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121 +msgid "" +"Once connected, you should be able to verify that you're browsing the web" +" through the Matrix server's IP by checking " +"[icanhazip](https://icanhazip.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123 +msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125 +msgid "Once logged in, proceed to [set up bridging](#usage)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127 +msgid "" +"If that doesn't work, enable 2FA (see: [Facebook help page on enabling " +"2FA](https://www.facebook.com/help/148233965247823)) and try to login " +"again with a new password, and entering the 2FA code when prompted, it " +"may take more then one try, in between attempts, check facebook.com to " +"see if they are requiring another password change" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po new file mode 100644 index 000000000..338a8b498 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po @@ -0,0 +1,177 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-gmessages.md:1 +msgid "Setting up Mautrix Google Messages bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"gmessages](https://github.com/mautrix/gmessages) for you, for bridging to" +" [Google Messages](https://messages.google.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:36 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40 +msgid "" +"To use the bridge, you need to start a chat with " +"`@gmessagesbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62 +msgid "" +"make sure you don't log out the `Mautrix-gmessages` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po new file mode 100644 index 000000000..a86a75fdb --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po @@ -0,0 +1,217 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-googlechat.md:1 +msgid "Setting up Mautrix Google Chat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"googlechat](https://github.com/mautrix/googlechat) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/googlechat/index.html)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 +msgid "" +"To enable the [Google Chat](https://chat.google.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40 +msgid "" +"To use the bridge, you need to start a chat with `googlechat bridge bot` " +"with handle `@googlechatbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42 +msgid "" +"Send `login` to the bridge bot to receive a link to the portal from which" +" you can enable the bridging. Open the link sent by the bot and follow " +"the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44 +msgid "" +"Automatic login may not work. If it does not, reload the page and select " +"the \"Manual login\" checkbox before starting. Manual login involves " +"logging into your Google account normally and then manually getting the " +"OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46 +msgid "" +"Once logged in, recent chats should show up as new conversations " +"automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48 +msgid "" +"You can learn more about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72 +msgid "" +"make sure you don't log out the `Mautrix-googlechat` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po new file mode 100644 index 000000000..d50b64b16 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po @@ -0,0 +1,214 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-hangouts.md:1 +msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 +msgid "" +"💡 **Note**: This bridge has been deprecated in favor of [Google Chat " +"bridge](https://github.com/mautrix/googlechat), which can be installed " +"using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md)." +" Installing the mautrix-hangouts bridge is **no longer possible**. For " +"now, this documentation page remains here for historical purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"hangouts](https://github.com/mautrix/hangouts) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17 +msgid "" +"To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 +msgid "" +"To use the bridge, you need to start a chat with `Hangouts bridge bot` " +"with handle `@hangoutsbot:example.com` (where `example.com` is your base " +"domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 +msgid "" +"Send `login` to the bridge bot to receive a link to the portal from which" +" you can enable the bridging. Open the link sent by the bot and follow " +"the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 +msgid "" +"Automatic login may not work. If it does not, reload the page and select " +"the \"Manual login\" checkbox before starting. Manual login involves " +"logging into your Google account normally and then manually getting the " +"OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 +msgid "" +"Once logged in, recent chats should show up as new conversations " +"automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 +msgid "" +"You can learn more about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72 +msgid "" +"make sure you don't log out the `Mautrix-Hangouts` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po new file mode 100644 index 000000000..07597e931 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po @@ -0,0 +1,144 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-instagram.md:1 +msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 +msgid "" +"**Note**: This bridge has been deprecated in favor of the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " +"can be installed using [this playbook](configuring-playbook-bridge-" +"mautrix-meta-instagram.md). Consider using that bridge instead of this " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"instagram](https://github.com/mautrix/instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/instagram/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-instagram/defaults/main.yml` to find other things you would like " +"to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:60 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64 +msgid "" +"To use the bridge, you need to start a chat with " +"`@instagrambot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66 +msgid "" +"Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the " +"bridge bot to enable bridging for your instagram/Messenger account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68 +msgid "" +"You can learn more here about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po new file mode 100644 index 000000000..bae56eb70 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po @@ -0,0 +1,296 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-meta-instagram.md:1 +msgid "Setting up Instagram bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 +msgid "" +"The playbook can install and configure the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 +msgid "" +"Since this bridge component can bridge to both " +"[Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/) and you may wish to do both at the " +"same time, the playbook makes it available via 2 different Ansible roles " +"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" +"instagram`). The latter is a reconfigured copy of the first one (created " +"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" +"instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 +msgid "" +"This documentation page only deals with the bridge's ability to bridge to" +" Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger" +" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" +"messenger.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11 +msgid "Migrating from the old mautrix-instagram bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 +msgid "" +"If you've been using the [mautrix-instagram](./configuring-playbook-" +"bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first**" +" or the 2 bridges will be in conflict:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 +msgid "" +"both trying to use `@instagrambot:example.com` as their username. This " +"conflict may be resolved by adjusting " +"`matrix_mautrix_instagram_appservice_bot_username` or " +"`matrix_mautrix_meta_instagram_appservice_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 +msgid "both trying to bridge the same DMs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 +msgid "" +"To do so, send a `clean-rooms` command to the management room with the " +"old bridge bot (`@instagrambot:example.com`). It gives you a list of " +"portals and groups of portals you may purge. Proceed with sending " +"commands like `clean recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 +msgid "" +"Then, consider disabling the old bridge in your configuration, so it " +"won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:36 +msgid "" +"Before proceeding to [re-running the playbook](./installing.md), you may " +"wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 +msgid "" +"The permissions are following the sequence: nothing < `relay` < `user` < " +"`admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 +msgid "" +"The default permissions are set via " +"`matrix_mautrix_meta_instagram_bridge_permissions_default` and are " +"somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 +msgid "" +"If you don't define the `matrix_admin` in your configuration (e.g. " +"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61 +msgid "" +"You may redefine " +"`matrix_mautrix_meta_instagram_bridge_permissions_default` any way you " +"see fit, or add extra permissions using " +"`matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" +"instagram/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:85 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89 +msgid "" +"To use the bridge, you need to start a chat with " +"`@instagrambot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111 +msgid "" +"make sure you don't log out the session for which you obtained an access " +"token some time in the future, as that would break the Double Puppeting " +"feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po new file mode 100644 index 000000000..bc6aa6588 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po @@ -0,0 +1,361 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-meta-messenger.md:1 +msgid "Setting up Messenger bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 +msgid "" +"The playbook can install and configure the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 +msgid "" +"Since this bridge component can bridge to both " +"[Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/) and you may wish to do both at the " +"same time, the playbook makes it available via 2 different Ansible roles " +"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" +"instagram`). The latter is a reconfigured copy of the first one (created " +"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" +"instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 +msgid "" +"This documentation page only deals with the bridge's ability to bridge to" +" Facebook Messenger. For bridging to Instagram, see [Setting up Instagram" +" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" +"instagram.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 +msgid "Migrating from the old mautrix-facebook bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 +msgid "" +"If you've been using the [mautrix-facebook](./configuring-playbook-" +"bridge-mautrix-facebook.md) bridge, it's possible to migrate the database" +" using [instructions from the bridge " +"documentation](https://docs.mau.fi/bridges/go/meta/facebook-" +"migration.html) (advanced)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 +msgid "" +"Then you may wish to get rid of the Facebook bridge. To do so, send a " +"`clean-rooms` command to the management room with the old bridge bot " +"(`@facebookbot:example.com`). It gives you a list of portals and groups " +"of portals you may purge. Proceed with sending commands like `clean " +"recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 +msgid "" +"Then, consider disabling the old bridge in your configuration, so it " +"won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 +msgid "" +"**Note**: the user ID of the new bridge bot is " +"`@messengerbot:example.com`, not `@facebookbot:example.com`. After " +"disabling the old bridge, its bot user will stop responding to a command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 +msgid "" +"Before proceeding to [re-running the playbook](./installing.md), you may " +"wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 +msgid "Bridge mode" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 +msgid "" +"As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) " +"bridge supports multiple modes of operation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 +msgid "The bridge can pull your Messenger messages via 3 different methods:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43 +msgid "(`facebook`) Facebook via `facebook.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44 +msgid "" +"(`facebook-tor`) Facebook via " +"`facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` " +"([Tor](https://www.torproject.org/)) - does not currently proxy media " +"downloads" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 +msgid "" +"(default) (`messenger`) Messenger via `messenger.com` - usable even " +"without a Facebook account" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 +msgid "" +"You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode`" +" variable. The playbook defaults to the `messenger` mode, because it's " +"most universal (every Facebook user has a Messenger account, but the " +"opposite is not true)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 +msgid "" +"Note that switching the mode (especially between `facebook*` and " +"`messenger`) will intentionally make the bridge use another database " +"(`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to " +"isolate the 2 instances. Switching between Tor and non-Tor may be " +"possible without dataloss, but your mileage may vary. Before switching to" +" a new mode, you may wish to de-configure the old one (send `help` to the" +" bridge bot and unbridge your portals, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 +msgid "" +"The permissions are following the sequence: nothing < `relay` < `user` < " +"`admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 +msgid "" +"The default permissions are set via " +"`matrix_mautrix_meta_messenger_bridge_permissions_default` and are " +"somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 +msgid "" +"If you don't define the `matrix_admin` in your configuration (e.g. " +"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 +msgid "" +"You may redefine " +"`matrix_mautrix_meta_messenger_bridge_permissions_default` any way you " +"see fit, or add extra permissions using " +"`matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" +"messenger/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102 +msgid "" +"To use the bridge, you need to start a chat with " +"`@messengerbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain). Note that the user ID of the bridge's bot is not " +"`@facebookbot:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104 +msgid "" +"You then need to send a `login` command and follow the bridge bot's " +"instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106 +msgid "" +"Given that the bot is configured in `messenger` [bridge mode](#bridge-" +"mode) by default, you will need to log in to " +"[messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain " +"the cookies from there as per [the bridge's authentication " +"instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128 +msgid "" +"make sure you don't log out the session for which you obtained an access " +"token some time in the future, as that would break the Double Puppeting " +"feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po new file mode 100644 index 000000000..5998fd5cd --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po @@ -0,0 +1,267 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-signal.md:1 +msgid "Setting up Mautrix Signal bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"signal](https://github.com/mautrix/signal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/signal/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 +msgid "" +"**Note**: This revamped version of the [mautrix-signal (legacy" +")](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU " +"usage of your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 +msgid "Prerequisites (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11 +msgid "Prepare Postgres database on external Postgres server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 +msgid "" +"If you're running with the Postgres database server integrated by the " +"playbook (which is the default), you don't need to do anything special " +"and can easily proceed with installing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 +msgid "" +"However, if you're [using an external Postgres server](configuring-" +"playbook-external-postgres.md), you'd need to manually prepare a Postgres" +" database for this bridge and adjust the variables related to that " +"(`matrix_mautrix_signal_database_*`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 +msgid "Enable Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 +msgid "relay - Allowed to be relayed through the bridge, no access to commands;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38 +msgid "user - Use the bridge with puppeting;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39 +msgid "admin - Use and administer the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 +msgid "" +"The permissions are following the sequence: nothing < relay < user < " +"admin." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43 +msgid "The default permissions are set as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 +msgid "" +"If you want to augment the preset permissions, you might want to set the " +"additional permissions with the following settings in your `vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 +msgid "" +"This will add the admin permission to the specific user, while keeping " +"the default permissions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 +msgid "" +"In case you want to replace the default permissions settings " +"**completely**, populate the following item within your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"signal/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:87 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91 +msgid "" +"To use the bridge, you need to start a chat with `@signalbot:example.com`" +" (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113 +msgid "" +"make sure you don't log out the `Mautrix-Signal` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po new file mode 100644 index 000000000..015f60413 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po @@ -0,0 +1,289 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-slack.md:1 +msgid "Setting up Mautrix Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 +msgid "" +"**Note**: bridging to [Slack](https://slack.com/) can also happen via the" +" [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Slack](configuring-" +"playbook-bridge-appservice-slack.md), because it supports plumbing. Note " +"that it is not available for new installation unless you have already " +"created a classic Slack application, because the creation of classic " +"Slack applications, which this bridge makes use of, has been " +"discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 +msgid "" +"For personal use with a slack account we recommend the `mautrix-slack` " +"bridge (the one being discussed here), because it is the most fully-" +"featured and stable of the 3 Slack bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7 +msgid "" +"The playbook can install and configure [mautrix-" +"slack](https://github.com/mautrix/slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn" +" what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 +msgid "" +"See the [features and " +"roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more " +"information." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 +msgid "" +"For using this bridge, you would need to authenticate by **providing your" +" username and password** (legacy) or by using a **token login**. See more" +" information in the " +"[docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 +msgid "" +"Note that neither of these methods are officially supported by Slack. " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) uses a Slack bot account which is the only officially supported" +" method for bridging a Slack channel." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:33 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 +msgid "" +"There are some additional options you may wish to configure with the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41 +msgid "" +"`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some " +"variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +msgid "" +"`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for " +"the bridge's default configuration. You can override settings (even those" +" that don't have dedicated playbook variables) using the " +"`matrix_mautrix_slack_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 +msgid "" +"Start a chat with `@slackbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:64 +msgid "" +"If you would like to login to Slack using a token, send the `login-token`" +" command, otherwise, send the `login-password` command. Read " +"[here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how " +"to retrieve your token and cookie token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 +msgid "" +"The bot should respond with \"Successfully logged into for team " +"\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 +msgid "" +"Now that you're logged in, you can send a `help` command to the bot " +"again, to see additional commands you have access to." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 +msgid "" +"Slack channels should automatically begin bridging if you authenticated " +"using a token. Otherwise, you must wait to receive a message in the " +"channel if you used password authentication." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89 +msgid "" +"make sure you don't log out the `Mautrix-Slack` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po new file mode 100644 index 000000000..def8d3ed5 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po @@ -0,0 +1,223 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-telegram.md:1 +msgid "Setting up Mautrix Telegram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"telegram](https://github.com/mautrix/telegram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/telegram/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 +msgid "" +"You'll need to obtain API keys from " +"[https://my.telegram.org/apps](https://my.telegram.org/apps) and then add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 +msgid "" +"To use the bridge, you need to start a chat with " +"`@telegrambot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44 +msgid "" +"If you want to use the relay-bot feature ([relay bot " +"documentation](https://docs.mau.fi/bridges/python/telegram/relay-" +"bot.html)), which allows anonymous user to chat with telegram users, add " +"the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 +msgid "You might also want to give permissions to administrate the bot:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63 +msgid "" +"More details about permissions in this example: " +"https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-" +"config.yaml#L410" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65 +msgid "" +"If you like to exclude all groups from syncing and use the Telgeram-" +"Bridge only for direct chats, you can add the following additional " +"playbook configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +msgid "" +"**Note**: This method for enabling Double Puppeting can be configured " +"only after you've already set up bridging." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 +msgid "" +"send `login-matrix` to the bot and follow instructions about how to send " +"the access token to it" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 +msgid "" +"make sure you don't log out the `Mautrix-Telegram` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po new file mode 100644 index 000000000..081ced85a --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po @@ -0,0 +1,190 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-twitter.md:1 +msgid "Setting up Mautrix Twitter bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 +msgid "" +"**Note**: bridging to [Twitter](https://twitter.com/) can also happen via" +" the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-" +"twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"twitter](https://github.com/mautrix/twitter) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 +msgid "" +"See the project's [documentation](https://github.com/mautrix/twitter) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 +msgid "" +"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-twitter.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.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-twitter.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +msgid "" +"You then need to start a chat with `@twitterbot:example.com` (where " +"`example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +msgid "" +"Send login-cookie to start the login. The bot should respond with " +"instructions on how to proceed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +msgid "" +"You can learn more here about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 +msgid "" +"This method is currently not available for the Mautrix-Twitter bridge, " +"but is on the " +"[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) " +"under Misc/Manual login with `login-matrix`" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po new file mode 100644 index 000000000..90e8d06df --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-whatsapp.md:1 +msgid "Setting up Mautrix Whatsapp bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"whatsapp](https://github.com/mautrix/whatsapp) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 +msgid "" +"Whatsapp multidevice beta is required, now it is enough if Whatsapp is " +"connected to the Internet every 2 weeks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23 +msgid "" +"The relay bot functionality is off by default. If you would like to " +"enable the relay bot, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 +msgid "" +"By default, only admins are allowed to set themselves as relay users. To " +"allow anyone on your homeserver to set themselves as relay users add this" +" to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 +msgid "" +"If you want to activate the relay bot in a room, send `!wa set-relay`. To" +" deactivate, send `!wa unset-relay`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 +msgid "" +"To use the bridge, you need to start a chat with " +"`@whatsappbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80 +msgid "" +"make sure you don't log out the `Mautrix-Whatsapp` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po new file mode 100644 index 000000000..6a2c5924a --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po @@ -0,0 +1,146 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-wsproxy.md:1 +msgid "" +"Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage " +"(optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"wsproxy](https://github.com/mautrix/wsproxy) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 +msgid "" +"See the project's " +"[documentation](https://github.com/mautrix/wsproxy#readme) to learn what " +"it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 +msgid "" +"Note that the tokens must match what is compiled into the [mautrix-" +"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" +" or Android device." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 +msgid "Adjusting the wsproxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 +msgid "" +"By default, this playbook installs wsproxy on the `wsproxy.` subdomain " +"(`wsproxy.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27 +msgid "" +"By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can " +"easily make the service available at a **different hostname** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the wsproxy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40 +msgid "" +"By default, you will need to create a CNAME record for `wsproxy`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:55 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:57 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 +msgid "" +"Follow the [matrix-imessage " +"documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for " +"running `android-sms` and/or `matrix-imessage` on your device(s)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po new file mode 100644 index 000000000..26c2b1f5b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po @@ -0,0 +1,140 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mx-puppet-discord.md:1 +msgid "Setting up MX Puppet Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [matrix-appservice-discord](configuring-playbook-bridge-" +"appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-" +"mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Discord](configuring-" +"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:5 +msgid "" +"For personal use with a discord account we recommend the [mautrix-discord" +"](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is " +"the most fully-featured and stable of the 3 Discord bridges supported by " +"the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7 +msgid "" +"The playbook can install and configure [mx-puppet-" +"discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13 +msgid "" +"To enable the [Discord](https://discordapp.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:34 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38 +msgid "" +"To use the bridge, you need to start a chat with `Discord Puppet Bridge` " +"with the handle `@_discordpuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-discord [documentation](https://gitlab.com/mx-" +"puppet/discord/mx-puppet-discord) for more information about how to " +"configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po new file mode 100644 index 000000000..9aa89f8cd --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po @@ -0,0 +1,124 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mx-puppet-groupme.md:1 +msgid "Setting up MX Puppet GroupMe bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 +msgid "" +"To enable the [GroupMe](https://groupme.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 +msgid "" +"To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` " +"with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 +msgid "One authentication method is available." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 +msgid "" +"To link your GroupMe account, go to " +"[dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access" +" Token\" from the top menu. Copy the token and message the bridge with:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 +msgid "" +"Once logged in, send `listrooms` to the bot user to list the available " +"rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po new file mode 100644 index 000000000..66a26bda0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po @@ -0,0 +1,138 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-instagram.md:1 +msgid "Setting up MX Puppet Instagram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 +msgid "This allows you to bridge Instagram DirectMessages into Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 +msgid "" +"To enable the [Instagram](https://www.instagram.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Instagram Puppet " +"Bridge` with the handle `@_instagrampuppet_bot:example.com` (where " +"`example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36 +msgid "" +"Send `link ` 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 "" +"The `help` command shows which commands are available, though at the time" +" of writing, not every command is fully implemented." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po new file mode 100644 index 000000000..eb13e93f5 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po @@ -0,0 +1,42 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mx-puppet-skype.md:1 +msgid "Setting up MX Puppet Skype bridging (optional, removed)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 +msgid "" +"The playbook used to be able to install and configure [mx-puppet-" +"skype](https://github.com/Sorunome/mx-puppet-skype), but no longer " +"includes this component, because it has been broken and unmaintained for " +"a long time." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 +msgid "" +"Bridging to [Skype](https://www.skype.com/) can also happen via the [go-" +"skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge " +"supported by the playbook." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po new file mode 100644 index 000000000..93cc2b2bc --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po @@ -0,0 +1,137 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:1 +msgid "Setting up MX Puppet Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 +msgid "" +"**Note**: bridging to [Slack](https://slack.com) can also happen via the " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-" +"slack.md) bridges supported by the playbook. Note that `matrix-" +"appservice-slack` is not available for new installation unless you have " +"already created a classic Slack application, because the creation of " +"classic Slack applications, which this bridge makes use of, has been " +"discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 +msgid "" +"The playbook can install and configure [mx-puppet-" +"slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11 +msgid "" +"Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack#option-2-oauth) instructions to create a new Slack app, " +"setting the redirect URL to `https://matrix.example.com/slack/oauth`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15 +msgid "" +"To enable the [Slack](https://slack.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:39 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43 +msgid "" +"To use the bridge, you need to start a chat with `Slack Puppet Bridge` " +"with the handle `@_slackpuppet_bot:example.com` (where `example.com` is " +"your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-slack [documentation](https://gitlab.com/mx-" +"puppet/slack/mx-puppet-slack) for more information about how to configure" +" the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po new file mode 100644 index 000000000..41cb05e14 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po @@ -0,0 +1,117 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-steam.md:1 +msgid "Setting up MX Puppet Steam bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"steam](https://github.com/icewind1991/mx-puppet-steam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 +msgid "" +"To enable the [Steam](https://steampowered.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Steam Puppet Bridge` " +"with the handle `@_steampuppet_bot:example.com` (where `example.com` is " +"your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-steam [documentation](https://github.com/icewind1991" +"/mx-puppet-steam) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po new file mode 100644 index 000000000..de0581490 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po @@ -0,0 +1,131 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-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 page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11 +msgid "" +"Make an app on " +"[developer.twitter.com](https://developer.twitter.com/en/apps)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 +msgid "" +"To enable the [Twitter](https://twitter.com) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:41 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45 +msgid "" +"To use the bridge, you need to start a chat with `Twitter Puppet Bridge` " +"with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47 +msgid "To log in, use `link` and click the link." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po new file mode 100644 index 000000000..e16cef9a6 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -0,0 +1,194 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1 +msgid "Setting up Postmoogle email bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3 +msgid "" +"**Note**: email bridging can also happen via the [email2matrix" +"](configuring-playbook-email2matrix.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5 +msgid "" +"The playbook can install and configure " +"[Postmoogle](https://github.com/etkecc/postmoogle) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7 +msgid "" +"Postmoogle is a bridge you can use to have its bot user forward emails to" +" Matrix rooms. It runs an SMTP email server and allows you to assign " +"mailbox addresses to the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 +msgid "" +"See the project's [documentation](https://github.com/etkecc/postmoogle) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13 +msgid "" +"Open the following ports on your server to be able to receive incoming " +"emails:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15 +msgid "`25/tcp`: SMTP" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16 +msgid "`587/tcp`: Submission (TLS-encrypted SMTP)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18 +msgid "" +"If you don't open these ports, you will still be able to send emails, but" +" not receive any." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20 +msgid "" +"These port numbers are configurable via the " +"`matrix_postmoogle_smtp_host_bind_port` and " +"`matrix_postmoogle_submission_host_bind_port` variables, but other email " +"servers will try to deliver on these default (standard) ports, so " +"changing them is of little use." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47 +msgid "" +"You will also need to add several DNS records so that Postmoogle can send" +" emails. See [Configuring DNS](configuring-dns.md) for details about DNS " +"changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create a user account of the bridge's bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66 +msgid "" +"If you change the bridge's bot password (`matrix_postmoogle_password` in " +"your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_postmoogle_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70 +msgid "" +"To use the bridge, invite the `@postmoogle:example.com` bot user into a " +"room you want to use as a mailbox." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72 +msgid "" +"Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with " +"the email address `NAME@matrix.example.com`. Emails sent to that email " +"address will be forwarded to the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 +msgid "" +"Send `!pm help` to the room to see the bridge's help menu for additional " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/postmoogle)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78 +msgid "Debug/Logs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80 +msgid "" +"As with all other services, you can find their logs in [systemd-" +"journald](https://www.freedesktop.org/software/systemd/man/systemd-" +"journald.service.html) by running something like `journalctl -fu matrix-" +"postmoogle`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82 +msgid "" +"The default logging level for this bridge is `INFO`, but you can increase" +" it to `DEBUG` with the following additional configuration:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po new file mode 100644 index 000000000..95a401bfa --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po @@ -0,0 +1,99 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-wechat.md:1 +msgid "Setting up WeChat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:3 +msgid "" +"The playbook can install and configure the [matrix-" +"wechat](https://github.com/duo/matrix-wechat) bridge for you (for " +"bridging to the [WeChat](https://www.wechat.com/) network)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:34 +msgid "" +"Once the bridge is installed, start a chat with `@wechatbot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:36 +msgid "Send `help` to the bot to see the available commands." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po new file mode 100644 index 000000000..db70bbfd9 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po @@ -0,0 +1,238 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-cactus-comments.md:1 +msgid "Setting up Cactus Comments (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:3 +msgid "" +"The playbook can install and configure the [Cactus " +"Comments](https://cactus.chat) system for you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:5 +msgid "" +"Cactus Comments is a **federated comment system** built on Matrix. It " +"respects your privacy, and puts you in control." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:7 +msgid "" +"See the project's [documentation](https://cactus.chat/docs/getting-" +"started/introduction/) to learn what it does and why it might be useful " +"to you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:9 +msgid "" +"The playbook contains 2 roles for configuring different pieces of the " +"Cactus Comments system:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:11 +msgid "" +"`matrix-cactus-comments` - the backend appservice integrating with the " +"Matrix homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:13 +msgid "" +"`matrix-cactus-comments-client` - a static website server serving the " +"[cactus-client](https://cactus.chat/docs/client/introduction/) static " +"assets (`cactus.js` and `styles.css`)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:15 +msgid "You can enable whichever component you need (typically both)." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:17 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:19 +msgid "" +"To enable Cactus Comments, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:41 +msgid "Adjusting the Cactus Comments' client URL" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:43 +msgid "" +"By default, this playbook installs Cactus Comments' client on the " +"`matrix.` subdomain, at the `/cactus-comments` path " +"(https://matrix.example.com/cactus-comments). This makes it easy to " +"install it, because it **doesn't require additional DNS records to be set" +" up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:45 +msgid "" +"By tweaking the `matrix_cactus_comments_client_hostname` and " +"`matrix_cactus_comments_client_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:47 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:56 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:58 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Cactus Comments' client domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:60 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:62 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:64 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:66 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:73 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:75 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:77 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:79 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:81 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:83 +msgid "" +"Upon starting Cactus Comments, a `bot.cactusbot` user account is created " +"automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:85 +msgid "" +"To get started, send a `help` message to the `@bot.cactusbot:example.com`" +" bot to confirm it's working." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:87 +msgid "" +"Then, register a site by sending `register ` (where " +"`` is a unique identifier you choose. It does not have to " +"match your domain). You will then be invited into a moderation room." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:89 +msgid "Now you are good to go and can embed the comment section on your website!" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:91 +msgid "Embed Cactus Comments" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:93 +msgid "" +"The official [documentation](https://cactus.chat/docs/getting-started" +"/quick-start/) provides a useful guide to embed Cactus Comments on your " +"website." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:95 +msgid "" +"After including the JavaScript and CSS asset files, insert a `
` " +"where you'd like to display the comment section:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:101 +msgid "" +"Then, you need to initialize the comment section. Make sure to replace " +"`example.com` with your base domain and `` with the one " +"that has been registered above:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:115 +msgid "Adjust the domain name for self-hosting" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:117 +msgid "" +"To have the assets served from your homeserver (not from `cactus.chat`), " +"you need to adjust the domain name on the official documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:119 +msgid "" +"Make sure to replace `example.com` with your base domain before you " +"include the following lines, instead of the one provided by the official " +"documentation:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:126 +msgid "" +"**Note**: if the `matrix_cactus_comments_client_hostname` and " +"`matrix_cactus_comments_client_path_prefix` variables are tweaked, you " +"would need to adjust the URLs of the assets accordingly." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po new file mode 100644 index 000000000..04d679cb1 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po @@ -0,0 +1,146 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-client-cinny.md:1 +msgid "Setting up Cinny (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:3 +msgid "" +"This playbook can install the [Cinny](https://github.com/ajbura/cinny) " +"Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:5 +msgid "" +"Cinny is a web client focusing primarily on simple, elegant and secure " +"interface. It can be installed alongside or instead of [Element Web" +"](./configuring-playbook-client-element-web.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:7 +msgid "" +"💡 **Note**: the latest version of Cinny is also available on the web, " +"hosted by 3rd parties. If you trust giving your credentials to the " +"following 3rd party Single Page Applications, you can consider using it " +"from there and avoiding the (small) overhead of self-hosting:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:9 +msgid "" +"[app.cinny.in](https://app.cinny.in), hosted by the " +"[Cinny](https://cinny.in/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:13 +msgid "" +"To enable Cinny, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:19 +msgid "Adjusting the Cinny URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:21 +msgid "" +"By default, this playbook installs Cinny on the `cinny.` subdomain " +"(`cinny.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:23 +msgid "" +"By tweaking the `matrix_client_cinny_hostname` variable, you can easily " +"make the service available at a **different hostname** than the default " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:25 +msgid "" +"While a `matrix_client_cinny_path_prefix` variable exists for tweaking " +"the path-prefix, it's [not supported " +"anymore](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3701), because Cinny requires an application rebuild (with " +"a tweaked build config) to be functional under a custom path." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:27 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:34 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:36 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the Cinny domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:38 +msgid "" +"By default, you will need to create a CNAME record for `cinny`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:40 +msgid "" +"If you've adjusted `matrix_client_cinny_hostname`, you will need to " +"adjust your DNS configuration accordingly." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:44 +msgid "" +"After configuring the playbook and [adjusting your DNS records" +"](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:51 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:53 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po new file mode 100644 index 000000000..cbcdfcec2 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po @@ -0,0 +1,236 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-client-element-web.md:1 +msgid "Configuring Element Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:3 +msgid "" +"By default, this playbook installs the [Element Web](https://github.com" +"/element-hq/element-web) Matrix client for you. If that's okay, you can " +"skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:5 +msgid "" +"💡 **Note**: the latest version of Element Web is also available on the " +"web, hosted by 3rd parties. If you trust giving your credentials to the " +"following 3rd party Single Page Applications, you can consider using it " +"from there and avoiding the (small) overhead of self-hosting (by " +"[disabling Element Web](#disabling-element-web)):" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:7 +msgid "" +"[app.element.io](https://app.element.io/), hosted by " +"[Element](https://element.io/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:8 +msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:10 +msgid "Disabling Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:12 +msgid "" +"If you'd like for the playbook to not install Element Web (or to " +"uninstall it if it was previously installed), add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:20 +msgid "" +"The playbook provides some customization variables you could use to " +"change Element Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:22 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/element/config.json` file (on the server). This file is " +"generated from the [`roles/custom/matrix-client-" +"element/templates/config.json.j2`](../roles/custom/matrix-client-" +"element/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:24 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:26 +msgid "" +"Alternatively, **if there is no pre-defined variable** for an Element Web" +" setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:28 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Element Web's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:30 +msgid "" +"or, you can **extend and override the default configuration** " +"([`config.json.j2`](../roles/custom/matrix-client-" +"element/templates/config.json.j2)) by making use of the " +"`matrix_client_element_configuration_extension_json_` variable. You can " +"find information about this in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:32 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_client_element_configuration_default` (or " +"`matrix_client_element_configuration`). You can find information about " +"this in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:34 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:36 +msgid "" +"To change the look of Element Web, you can define your own themes " +"manually by using the " +"`matrix_client_element_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:38 +msgid "" +"Or better yet, you can automatically pull it all themes provided by the " +"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" +"themes) project by simply flipping a flag " +"(`matrix_client_element_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:40 +msgid "" +"If you make your own theme, we encourage you to submit it to the " +"**aaronraimist/element-themes** project, so that the whole community " +"could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:42 +msgid "" +"Note that for a custom theme to work well, all Element Web instances that" +" you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:44 +msgid "Adjusting the Element Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:46 +msgid "" +"By default, this playbook installs Element Web on the `element.` " +"subdomain (`element.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:48 +msgid "" +"By tweaking the `matrix_client_element_hostname` and " +"`matrix_client_element_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:50 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:61 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:63 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Element Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:65 +msgid "" +"By default, you will need to create a CNAME record for `element`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:67 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:69 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:71 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:78 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:80 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po new file mode 100644 index 000000000..bfa4ef79b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po @@ -0,0 +1,123 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-client-hydrogen.md:1 +msgid "Setting up Hydrogen (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:3 +msgid "" +"This playbook can install the [Hydrogen](https://github.com/element-hq" +"/hydrogen-web) Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:5 +msgid "" +"Hydrogen is a lightweight web client that supports mobile and legacy web " +"browsers. It can be installed alongside or instead of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:9 +msgid "" +"To enable Hydrogen, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:15 +msgid "Adjusting the Hydrogen URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:17 +msgid "" +"By default, this playbook installs Hydrogen on the `hydrogen.` subdomain " +"(`hydrogen.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:19 +msgid "" +"By tweaking the `matrix_client_hydrogen_hostname` and " +"`matrix_client_hydrogen_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:21 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:32 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:34 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Hydrogen domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:36 +msgid "" +"By default, you will need to create a CNAME record for `hydrogen`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:38 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:40 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:42 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:49 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:51 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po new file mode 100644 index 000000000..9fa8372e8 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po @@ -0,0 +1,232 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-client-schildichat-web.md:1 +msgid "Setting up SchildiChat Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:3 +msgid "" +"This playbook can install the [SchildiChat " +"Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:5 +msgid "" +"SchildiChat Web is a feature-rich messenger for Matrix based on Element " +"Web with some extras and tweaks. It can be installed alongside or instead" +" of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:7 +msgid "" +"💡 **Note**: the latest version of SchildiChat Web is also available on " +"the web, hosted by 3rd parties. If you trust giving your credentials to " +"the following 3rd party Single Page Application, you can consider using " +"it from there:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 +msgid "" +"[app.schildi.chat](https://app.schildi.chat/), hosted by the " +"[SchildiChat](https://schildi.chat/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 +msgid "" +"To enable SchildiChat Web, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 +msgid "" +"The playbook provides some customization variables you could use to " +"change SchildiChat Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:21 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml) and they ultimately end up in the " +"generated `/matrix/schildichat/config.json` file (on the server). This " +"file is generated from the [`roles/custom/matrix-client-" +"schildichat/templates/config.json.j2`](../roles/custom/matrix-client-" +"schildichat/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:23 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a SchildiChat " +"Web setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of SchildiChat Web's various" +" settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:29 +msgid "" +"or, you can **extend and override the default configuration** " +"([`config.json.j2`](../roles/custom/matrix-client-" +"schildichat/templates/config.json.j2)) by making use of the " +"`matrix_client_schildichat_configuration_extension_json_` variable. You " +"can find information about this in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:31 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_client_schildichat_configuration_default` (or " +"`matrix_client_schildichat_configuration`). You can find information " +"about this in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:33 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:35 +msgid "" +"To change the look of SchildiChat Web, you can define your own themes " +"manually by using the " +"`matrix_client_schildichat_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:37 +msgid "" +"Or better yet, you can automatically pull it all themes provided by the " +"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" +"themes) project by simply flipping a flag " +"(`matrix_client_schildichat_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:39 +msgid "" +"If you make your own theme, we encourage you to submit it to the " +"**aaronraimist/element-themes** project, so that the whole community " +"could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 +msgid "" +"Note that for a custom theme to work well, all SchildiChat Web instances " +"that you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 +msgid "Adjusting the SchildiChat Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:45 +msgid "" +"By default, this playbook installs SchildiChat Web on the `schildichat.` " +"subdomain (`schildichat.example.com`) and requires you to [adjust your " +"DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:47 +msgid "" +"By tweaking the `matrix_client_schildichat_hostname` and " +"`matrix_client_schildichat_path_prefix` variables, you can easily make " +"the service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:49 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:60 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:62 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the SchildiChat Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:64 +msgid "" +"By default, you will need to create a CNAME record for `schildichat`. See" +" [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:66 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:68 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:70 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po new file mode 100644 index 000000000..9f7d19965 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -0,0 +1,138 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-conduit.md:1 +msgid "Configuring Conduit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, but you can also use " +"[Conduit](https://conduit.rs)." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:7 +msgid "" +"**You can't switch an existing Matrix server's implementation** (e.g. " +"Synapse -> Conduit). Proceed below only if you're OK with losing data or " +"you're dealing with a server on a new domain name, which hasn't " +"participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:9 +msgid "" +"**homeserver implementations other than Synapse may not be fully " +"functional**. The playbook may also not assist you in an optimal way " +"(like it does with Synapse). Make yourself familiar with the downsides " +"before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:13 +msgid "" +"To use Conduit, you **generally** need to add the following configuration" +" to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:19 +msgid "Creating the first user account" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:21 +msgid "" +"Since it is difficult to create the first user account on Conduit (see " +"[famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) " +"and " +"[famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354))" +" and it does not support [registering users](registering-users.md) (via " +"the command line or via the playbook) like Synapse and Dendrite do, we " +"recommend the following procedure:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:23 +msgid "" +"Add `matrix_conduit_allow_registration: true` to your `vars.yml` the " +"first time around, temporarily" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:24 +msgid "" +"Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags" +"=setup-all,start` - see [Installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:25 +msgid "" +"Create your first user via Element Web or any other client which supports" +" creating users" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:26 +msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:27 +msgid "" +"Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-conduit,start` would be enough this time)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:28 +msgid "" +"You can now use your server safely. Additional users can be created by " +"messaging the internal Conduit bot" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:30 +msgid "Configuring bridges / appservices" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:32 +msgid "" +"Automatic appservice setup is currently unsupported when using Conduit. " +"After setting up the service as usual you may notice that it is unable to" +" start." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:34 +msgid "" +"You will have to manually register appservices using the the [register-" +"appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md)" +" command." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:36 +msgid "" +"Find the `registration.yaml` in the `/matrix` directory, for example " +"`/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content " +"to Conduit:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po new file mode 100644 index 000000000..519a7afa8 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -0,0 +1,152 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dendrite.md:1 +msgid "Configuring Dendrite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, but you can also use " +"[Dendrite](https://github.com/matrix-org/dendrite)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:7 +msgid "" +"**You can't switch an existing Matrix server's implementation** (e.g. " +"Synapse -> Dendrite). Proceed below only if you're OK with losing data or" +" you're dealing with a server on a new domain name, which hasn't " +"participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:9 +msgid "" +"**homeserver implementations other than Synapse may not be fully " +"functional**. The playbook may also not assist you in an optimal way " +"(like it does with Synapse). Make yourself familiar with the downsides " +"before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:13 +msgid "" +"To use Dendrite, you **generally** need to add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:19 +msgid "" +"The playbook provides lots of customization variables you could use to " +"change Dendrite's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:21 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/dendrite/config/dendrite.yaml` file (on the server). This file " +"is generated from the [`roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:23 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:25 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a Dendrite " +"setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:27 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Dendrite's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:29 +msgid "" +"or, you can **extend and override the default configuration** " +"([`dendrite.yaml.j2`](../roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the " +"`matrix_dendrite_configuration_extension_yaml` variable. You can find " +"information about this in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:31 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_dendrite_configuration` (or " +"`matrix_dendrite_configuration_yaml`). You can find information about " +"this in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:35 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:42 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:44 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po new file mode 100644 index 000000000..ed7f463fa --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -0,0 +1,259 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dimension.md:1 +msgid "Setting up Dimension integration manager (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:3 +msgid "" +"**[Dimension](https://dimension.t2bot.io) can only be installed after " +"Matrix services are installed and running.** If you're just installing " +"Matrix services for the first time, please continue with the " +"[Configuration](configuring-playbook.md) / [Installation](installing.md) " +"flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "" +"**Note**: 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:7 +msgid "" +"**Note**: This playbook now supports running " +"[Dimension](https://dimension.t2bot.io) in both a federated and " +"[unfederated](https://github.com/turt2live/matrix-" +"dimension/blob/master/docs/unfederated.md) environments. This is handled " +"automatically based on the value of " +"`matrix_homeserver_federation_enabled`. Enabling Dimension, means that " +"the `openid` API endpoints will be exposed on the Matrix Federation port " +"(usually `8448`), even if [federation](configuring-playbook-" +"federation.md) is disabled. It's something to be aware of, especially in " +"terms of firewall whitelisting (make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "" +"To enable Dimension, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "" +"These users can modify the integrations this Dimension supports. Add this" +" to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:27 +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:29 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "" +"We recommend that you create a dedicated Matrix user for Dimension " +"(`dimension` is a good username). Follow our [Registering users" +"](registering-users.md) guide to learn how to register **a regular (non-" +"admin) user**." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "" +"You are required to specify an access token (belonging to this new user) " +"for Dimension to work. To get an access token for the Dimension user, you" +" can follow the documentation on [how to do obtain an access token" +"](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "" +"Add access token to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:43 +msgid "" +"For more information on how to acquire an access token, visit " +"[https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "" +"By default, this playbook installs Dimension on the `dimension.` " +"subdomain (`dimension.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:49 +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:51 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:62 +msgid "" +"**Note**: While there is a `matrix_dimension_path_prefix` variable for " +"changing the path where Dimension is served, overriding it is not " +"possible due to [this Dimension issue](https://github.com/turt2live" +"/matrix-dimension/issues/510). You must serve Dimension at a dedicated " +"subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:64 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:66 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:68 +msgid "" +"By default, you will need to create a CNAME record for `dimension`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:81 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:83 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:85 +msgid "" +"After Dimension has been installed you may need to log out and log back " +"in for it to pick up the new integration manager. Then you can access " +"integrations in Element Web by opening a room, clicking the Room info " +"button (`i`) button in the top right corner of the screen, and then " +"clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:87 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:89 +msgid "" +"By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as " +"the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video " +"conference widgets. For users running [a self-hosted Jitsi instance" +"](./configuring-playbook-jitsi.md), you will likely want the widget to " +"use your own Jitsi instance. Currently there is no way to configure this " +"via the playbook, see [this issue](https://github.com/turt2live/matrix-" +"dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:91 +msgid "" +"In the interim until the above limitation is resolved, an admin user " +"needs to configure the domain via the admin ui once dimension is running." +" In Element Web, go to *Manage Integrations* → *Settings* " +"→ *Widgets* → *Jitsi Conference Settings* and set " +"*Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:93 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:95 +msgid "" +"To use a more custom configuration, you can define a " +"`matrix_dimension_configuration_extension_yaml` string variable and put " +"your configuration in it. To learn more about how to do this, refer to " +"the information about `matrix_dimension_configuration_extension_yaml` in " +"the [default variables file](../roles/custom/matrix-" +"dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:97 +msgid "" +"You can find all configuration options on [GitHub page of Dimension " +"project](https://github.com/turt2live/matrix-" +"dimension/blob/master/config/default.yaml)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po new file mode 100644 index 000000000..8a8ce45ce --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po @@ -0,0 +1,100 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dynamic-dns.md:1 +msgid "Setting up Dynamic DNS (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:3 +msgid "" +"The playbook can configure Dynamic DNS with " +"[ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl " +"client used to update dynamic DNS entries for accounts on Dynamic DNS " +"Network Service Provider." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:5 +msgid "" +"Most cloud providers / ISPs will charge you extra for a static IP " +"address. If you're not hosting a highly reliable homeserver you can " +"workaround this via dynamic DNS." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:7 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:9 +msgid "" +"You'll need to get a username and password from your DNS provider. Please" +" consult with the provider about how to retrieve them." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:13 +msgid "" +"To enable dynamic DNS, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:35 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:37 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:39 +msgid "Additional Reading" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:41 +msgid "Additional resources:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:43 +msgid "https://matrix.org/docs/guides/free-small-matrix-server" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po new file mode 100644 index 000000000..3d8308b17 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po @@ -0,0 +1,128 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-email.md:1 +msgid "Adjusting email-sending settings (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:3 +msgid "" +"By default, this playbook sets up an [Exim](https://www.exim.org/) email " +"server through which all Matrix services send emails." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:5 +msgid "" +"The email server would attempt to deliver emails directly to their final " +"destination. This may or may not work, depending on your domain " +"configuration (SPF settings, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:7 +msgid "" +"By default, emails are sent from `matrix@matrix.example.com`, as " +"specified by the `exim_relay_sender_address` playbook variable." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:9 +msgid "" +"⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is" +" always blocked](https://cloud.google.com/compute/docs/tutorials/sending-" +"mail/), so sending email directly from your server is not possible. You " +"will need to [relay email through another SMTP server](#relaying-email-" +"through-another-smtp-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:11 +msgid "" +"💡 To improve deliverability, we recommend [relaying email through another" +" SMTP server](#relaying-email-through-another-smtp-server) anyway." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:13 +msgid "Firewall settings" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:15 +msgid "" +"No matter whether you send email directly (the default) or you relay " +"email through another host (see how below), you'll probably need to allow" +" outgoing traffic for TCP ports 25/587 (depending on configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:17 +msgid "Relaying email through another SMTP server" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:19 +msgid "" +"If you'd like to relay email through another SMTP server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:31 +msgid "" +"**Note**: only the secure submission protocol (using `STARTTLS`, usually " +"on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port " +"`465`) **is not supported**." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:33 +msgid "Configuations for sending emails using Sendgrid" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:35 +msgid "" +"An easy and free SMTP service to set up is " +"[Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 " +"emails per day to be sent. In the settings below you can provide any " +"email for `exim_relay_sender_address`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:37 +msgid "" +"The only other thing you need to change is the " +"`exim_relay_relay_auth_password`, which you can generate at " +"https://app.sendgrid.com/settings/api_keys. The API key password looks " +"something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-" +"6zkdwrPP8bOeuI`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:39 +msgid "" +"Note that the `exim_relay_relay_auth_username` is literally the string " +"`apikey`, it's always the same for Sendgrid." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:51 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:53 +msgid "" +"If you're having trouble with email not being delivered, it may be useful" +" to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po new file mode 100644 index 000000000..199006251 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -0,0 +1,259 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-email2matrix.md:1 +msgid "Setting up Email2Matrix (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:3 +msgid "" +"**Note**: email bridging can also happen via the [Postmoogle" +"](configuring-playbook-bridge-postmoogle.md) bridge supported by the " +"playbook. Postmoogle is much more powerful and easier to use, so we " +"recommend that you use it, instead of Email2Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:5 +msgid "" +"The playbook can install and configure " +"[email2matrix](https://github.com/devture/email2matrix) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:7 +msgid "" +"See the project's " +"[documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:9 +msgid "Preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:11 +msgid "DNS configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:13 +msgid "" +"It's not strictly necessary, but you may increase the chances that " +"incoming emails reach your server by adding an `MX` record for " +"`matrix.example.com`, as described in the [Configuring DNS](configuring-" +"dns.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:15 +msgid "Port availability" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:17 +msgid "" +"Ensure that port 25 is available on your Matrix server and open in your " +"firewall." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:19 +msgid "" +"If you have `postfix` or some other email server software installed, you " +"may need to manually remove it first (unless you need it, of course)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:21 +msgid "" +"If you really need to run an email server on the Matrix machine for other" +" purposes, it may be possible to run Email2Matrix on another port (with a" +" configuration like `matrix_email2matrix_smtp_host_bind_port: " +"\"127.0.0.01:2525\"`) and have your other email server relay messages " +"there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:23 +msgid "" +"For details about using Email2Matrix alongside " +"[Postfix](http://www.postfix.org/), see " +"[here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:25 +msgid "Creating a user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:27 +msgid "" +"Before enabling Email2Matrix, you'd most likely wish to create a " +"dedicated user (or more) that would be sending messages on the Matrix " +"side. 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:29 +msgid "" +"Refer to [Registering users](registering-users.md) for ways to create a " +"user. A regular (non-admin) user works best." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:31 +msgid "Creating a shared room" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:33 +msgid "" +"After creating the sender user, you should create one or more Matrix " +"rooms that you share with that user. It doesn't matter who creates and " +"owns the rooms and who joins later (you or the sender user)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:35 +msgid "" +"What matters is that both you and the sender user are part of the same " +"room and that the sender user has enough privileges in the room to be " +"able to send messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:37 +msgid "Inviting additional people to the room is okay too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:39 +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:41 +msgid "Obtaining an access token for the sender user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:43 +msgid "" +"In order for the sender user created above to be able to send messages to" +" the room, we'll need to obtain an access token for it. Refer to the " +"documentation on [how to obtain an access token](obtaining-access-" +"tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:47 +msgid "" +"After doing the preparation steps above, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to " +"your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:72 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:74 +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:75 +msgid "" +"MatrixRoomId - internal ID of the room, to which received emails are sent" +" as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:76 +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:77 +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:78 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:79 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:80 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:81 +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:83 +msgid "" +"Refer to the official documentation " +"[here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:85 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:87 +msgid "" +"To enable Email2Matrix, run the playbook with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:95 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just run-tags setup-email2matrix,start` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:97 +msgid "" +"`just run-tags setup-email2matrix,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-email2matrix.md:99 +msgid "" +"After installation, you may wish to send a test email to the email " +"address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) " +"to make sure that Email2Matrix works as expected." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po new file mode 100644 index 000000000..8afb7b0ad --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -0,0 +1,251 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-etherpad.md:1 +msgid "Setting up Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:3 +msgid "" +"[Etherpad](https://etherpad.org) is an open source collaborative text " +"editor that can be embedded in a Matrix chat room using the [Dimension " +"integration manager](https://dimension.t2bot.io) or used as standalone " +"web app." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:5 +msgid "" +"When enabled together with the Jitsi audio/video conferencing system (see" +" [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made " +"available as an option during the conferences." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:9 +msgid "" +"To enable Etherpad, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:19 +msgid "Adjusting the Etherpad URL" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:21 +msgid "" +"By default, this playbook installs Etherpad on the `etherpad.` subdomain " +"(`etherpad.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:23 +msgid "" +"By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables," +" you can easily make the service available at a **different hostname " +"and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:25 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:38 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Etherpad domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:40 +msgid "" +"By default, you will need to create a CNAME record for `etherpad`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:42 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:46 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:55 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the Etherpad admin user (`etherpad_admin_username`)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:61 +msgid "" +"If you change the Etherpad admin user's password " +"(`etherpad_admin_password` in your `vars.yml` file) subsequently, the " +"admin user's credentials on the homeserver won't be updated " +"automatically. If you'd like to change the admin user's password, use a " +"tool like [synapse-admin](configuring-playbook-synapse-admin.md) to " +"change it, and then update `etherpad_admin_password` to let the admin " +"user know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:65 +msgid "" +"The Etherpad UI should be available at `https://etherpad.example.com`, " +"while the admin UI (if enabled) should then be available at " +"`https://etherpad.example.com/admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:67 +msgid "" +"If you've [decided on another hostname or path-prefix](#adjusting-the-" +"etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these " +"URLs accordingly before usage." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:69 +msgid "Managing / Deleting old pads" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:71 +msgid "" +"If you want to manage and remove old unused pads from Etherpad, you will " +"first need to able Admin access as described above." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:73 +msgid "" +"Then from the plugin manager page " +"(`https://etherpad.example.com/admin/plugins`, install the `adminpads2` " +"plugin. Once installed, you should have a \"Manage pads\" section in the " +"Admin web-UI." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:75 +msgid "" +"How to use Etherpad widgets without an integration manager (like " +"Dimension)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:77 +msgid "" +"This is how it works in Element Web, it might work quite similar with " +"other clients:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:79 +msgid "" +"To integrate a standalone Etherpad in a room, create your pad by visiting" +" `https://etherpad.example.com`. When the pad opens, copy the URL and " +"send a command like this to the room: `/addwidget URL`. You will then " +"find your integrated Etherpad within the right sidebar in the `Widgets` " +"section." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:81 +msgid "Set Dimension default to the self-hosted Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:83 +msgid "" +"If you decided to install [Dimension integration manager](configuring-" +"playbook-dimension.md) alongside Etherpad, the Dimension administrator " +"users can configure the default URL template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:85 +msgid "" +"The Dimension configuration menu can be accessed with the sprocket icon " +"as you begin to add a widget to a room in Element Web. There you will " +"find the Etherpad Widget Configuration action beneath the _Widgets_ tab." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:87 +msgid "Removing the integrated Etherpad chat" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:89 +msgid "" +"If you wish to disable the Etherpad chat button, you can do it by " +"appending `?showChat=false` to the end of the pad URL, or the template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:91 +msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:93 +msgid "Known issues" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:95 +msgid "" +"If your Etherpad widget fails to load, this might be due to Dimension " +"generating a Pad name so long, the Etherpad app rejects it." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:97 +msgid "" +"`$roomId_$padName` can end up being longer than 50 characters. You can " +"avoid having this problem by altering the template so it only contains " +"the three word random identifier `$padName`." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po new file mode 100644 index 000000000..42508e26f --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po @@ -0,0 +1,77 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-playbook-external-postgres.md:1 +msgid "Using an external PostgreSQL server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:3 +msgid "" +"By default, this playbook would set up a PostgreSQL database server on " +"your machine, running in a Docker container. If that's okay, you can skip" +" this document." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:5 +msgid "" +"**Note**: using **an external Postgres server is currently [not very " +"seamless](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1682#issuecomment-1061461683) when it comes to enabling " +"various other playbook services** - you will need to create a new " +"database/credentials for each service and to point each service to its " +"corresponding database using custom `vars.yml` configuration. **For the " +"best experience with the playbook, stick to using the integrated Postgres" +" server**." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:7 +msgid "" +"If you'd like to use an external Postgres server that you manage, add the" +" following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:23 +msgid "" +"The database (as specified in `matrix_synapse_database_database`) must " +"exist and be accessible with the given credentials. It must be empty or " +"contain a valid Synapse database. If empty, Synapse would populate it the" +" first time it runs." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:25 +msgid "" +"**Note**: the external server that you specify in " +"`matrix_synapse_database_host` must be accessible from within the " +"`matrix-synapse` Docker container (and possibly other containers too). " +"This means that it either needs to be a publicly accessible hostname or " +"that it's a hostname on the same Docker network where all containers " +"installed by this playbook run (a network called `matrix` by default). " +"Using a local PostgreSQL instance on the host (running on the same " +"machine, but not in a container) is not possible." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:27 +msgid "" +"The connection to your external Postgres server **will not be SSL " +"encrypted**, as [we don't support that yet](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/issues/89)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po new file mode 100644 index 000000000..444b60686 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -0,0 +1,139 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-federation.md:1 +msgid "Controlling Matrix federation (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:3 +msgid "" +"By default, your server federates with the whole Matrix network. That is," +" people on your server can communicate with people on any other Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:5 +msgid "" +"**Note**: in the sample `vars.yml` " +"([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a " +"short user ID like `@alice:example.com` instead of " +"`@alice:matrix.example.com` and set up [server delegation](howto-server-" +"delegation.md) / redirection. Without a proper configuration, your server" +" will effectively not be part of the Matrix network. If you find your " +"server is not federated, make sure to [check whether services work" +"](maintenance-checking-services.md) and your server is properly " +"delegated." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:7 +msgid "Federating only with select servers" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:9 +msgid "" +"To make your server only federate with servers of your choosing, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:17 +msgid "" +"If you wish to disable federation, you can do that with an empty list " +"(`[]`), or better yet by completely disabling federation (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:19 +msgid "Exposing the room directory over federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:21 +msgid "" +"By default, your server's public rooms directory is not exposed to other " +"servers via federation." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:23 +msgid "" +"If you wish to expose it, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:29 +msgid "Disabling federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:31 +msgid "" +"To completely disable federation, isolating your server from the rest of " +"the Matrix network, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:37 +msgid "" +"With that, your server's users will only be able to talk among " +"themselves, but not to anyone who is on another server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:39 +msgid "" +"**Disabling federation does not necessarily disable the federation port**" +" (`8448`). Services like [Dimension](configuring-playbook-dimension.md) " +"and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs" +" exposed on that port. Even if you disable federation and only if " +"necessary, we may still be exposing the federation port and serving the " +"`openid` APIs there. To override this and completely disable Synapse's " +"federation port use:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:51 +msgid "" +"Changing the federation port from 8448 to a different port to use a CDN " +"that only accepts 443/80 ports" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:53 +msgid "" +"Why? This change could be useful for people running small Synapse " +"instances on small severs/VPSes to avoid being impacted by a simple " +"DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your " +"hosting provider does not provide a DOS/DDOS protection." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:55 +msgid "" +"The following changes in the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and " +"make it possible to proxy the federation through a CDN such as CloudFlare" +" or any other:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:66 +msgid "" +"**Use this at you own risk as all the possible side-effects of doing this" +" are not fully known. However, it has been tested and works fine and " +"passes all the tests on without " +"issues.**" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po new file mode 100644 index 000000000..69dc68308 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -0,0 +1,557 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-jitsi.md:1 +msgid "Setting up the Jitsi video-conferencing platform (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:3 +msgid "" +"The playbook can install the [Jitsi](https://jitsi.org/) video-" +"conferencing platform and integrate it with Element clients ([Element Web" +"](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:5 +msgid "" +"Jitsi installation is **not enabled by default**, because it's not a core" +" component of Matrix services." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:7 +msgid "" +"The setup done by the playbook is very similar to [docker-jitsi-" +"meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the " +"documentation there for many of the options here." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:11 +msgid "You may need to open the following ports to your server:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:13 +msgid "`4443/tcp` - RTP media fallback over TCP" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:14 +msgid "" +"`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, " +"incoming RTP packets on port `10000` may have the external IP of your " +"firewall as destination address, due to the usage of STUN in JVB (see " +"[`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting" +"/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:16 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:18 +msgid "" +"To enable Jitsi, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:24 +msgid "Adjusting the Jitsi URL" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:26 +msgid "" +"By default, this playbook installs Jitsi on the `jitsi.` subdomain " +"(`jitsi.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:28 +msgid "" +"By tweaking the `jitsi_hostname` variable, you can easily make the " +"service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:30 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:37 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:39 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Jitsi domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:41 +msgid "" +"By default, you will need to create a CNAME record for `jitsi`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:43 +msgid "(Optional) Configure Jitsi authentication and guests mode" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:45 +msgid "" +"By default the Jitsi Meet instance does not require any kind of login and" +" is open to use for anyone without registration." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:47 +msgid "" +"If you're fine with such an open Jitsi instance, please skip to " +"[Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:49 +msgid "" +"If you would like to control who is allowed to open meetings on your new " +"Jitsi instance, then please follow the following steps to enable Jitsi's " +"authentication and optionally guests mode." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:51 +msgid "" +"Currently, there are three supported authentication modes: 'internal' " +"(default), 'matrix' and 'ldap'." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:53 +msgid "" +"**Note**: Authentication is not tested via the playbook's self-checks. We" +" therefore recommend that you manually verify if authentication is " +"required by jitsi. For this, try to manually create a conference on " +"jitsi.example.com in your browser." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:55 +msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:57 +msgid "" +"The default authentication mechanism is 'internal' auth, which requires " +"jitsi-accounts to be setup and is the recommended setup, as it also works" +" in federated rooms. With authentication enabled, all meeting rooms have " +"to be opened by a registered user, after which guests are free to join. " +"If a registered host is not yet present, guests are put on hold in " +"individual waiting rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:59 +msgid "" +"Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml`" +" configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:71 +msgid "" +"**Caution**: Accounts added here and subsequently removed will not be " +"automatically removed from the Prosody server until user account cleaning" +" is integrated into the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:73 +msgid "" +"**If you get an error** like this: \"Error: Account creation/modification" +" not supported.\", it's likely that you had previously installed Jitsi " +"without auth/guest support. In such a case, you should look into " +"[Rebuilding your Jitsi installation](#rebuilding-your-jitsi-" +"installation)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:75 +msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:77 +msgid "" +"**Attention: Probably breaks Jitsi in federated rooms and does not allow " +"sharing conference links with guests.**" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:79 +msgid "" +"Using this authentication type require a [Matrix User Verification " +"Service](https://github.com/matrix-org/matrix-user-verification-service)." +" By default, this playbook creates and configures a user-verification-" +"service to run locally, see [configuring-user-verification-service" +"](configuring-playbook-user-verification-service.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:81 +msgid "To enable set this configuration at host level:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:89 +msgid "" +"For more information see also [https://github.com/matrix-org/prosody-mod-" +"auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-" +"auth-matrix-user-verification)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:91 +msgid "Authenticate using LDAP (Auth-Type 'ldap')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:93 +msgid "An example LDAP configuration could be:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:113 +msgid "" +"For more information refer to the [docker-jitsi-" +"meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-" +"ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs" +"/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:115 +msgid "(Optional) Making your Jitsi server work on a LAN" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:117 +msgid "" +"By default the Jitsi Meet instance does not work with a client in LAN " +"(Local Area Network), even if others are connected from WAN. There are no" +" video and audio. In the case of WAN to WAN everything is ok." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:119 +msgid "" +"The reason is the Jitsi VideoBridge git to LAN client the IP address of " +"the docker image instead of the host. The " +"[documentation](https://jitsi.github.io/handbook/docs/devops-guide" +"/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of " +"Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment " +"variable to make it work." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:121 +msgid "Here is how to do it in the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:123 +msgid "" +"Add these two lines to your " +"`inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:130 +msgid "(Optional) Fine tune Jitsi" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:132 +msgid "" +"Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` " +"configuration to save up resources (explained below):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:147 +msgid "" +"You may want to **suspend unused video layers** until they are requested " +"again, to save up resources on both server and clients. Read more on this" +" feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-" +"feature/)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:149 +msgid "" +"You may wish to **disable audio levels** to avoid excessive refresh of " +"the client-side page and decrease the CPU consumption involved." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:151 +msgid "" +"You may want to **limit the number of video feeds forwarded to each " +"client**, to save up resources on both server and clients. As clients’ " +"bandwidth and CPU may not bear the load, use this setting to avoid lag " +"and crashes. This feature is found by default in other webconference " +"applications such as Office 365 Teams (limit is set to 4). Read how it " +"works [here](https://github.com/jitsi/jitsi-" +"videobridge/blob/master/doc/last-n.md) and performance evaluation on this" +" [study](https://jitsi.org/wp-" +"content/uploads/2016/12/nossdav2015lastn.pdf)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:153 +msgid "" +"You may want to **limit the maximum video resolution**, to save up " +"resources on both server and clients." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:155 +msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:157 +msgid "" +"The playbook allows a user to set a max number of participants allowed to" +" join a Jitsi conference. By default there is no limit." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:159 +msgid "" +"In order to set the max number of participants use the following " +"**additional** configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:165 +msgid "(Optional) Additional JVBs" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:167 +msgid "" +"By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi" +"/jitsi-videobridge)) is deployed on the same host as the Matrix server. " +"To allow more video-conferences to happen at the same time, you may need " +"to provision additional JVB services on other hosts." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:169 +msgid "" +"There is an ansible playbook that can be run with the following tag: " +"`ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers " +"jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:171 +msgid "" +"For this role to work you will need an additional section in the ansible " +"hosts file with the details of the JVB hosts, for example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:178 +msgid "" +"Each JVB will require a server ID to be set so that it can be uniquely " +"identified and this allows Jitsi to keep track of which conferences are " +"on which JVB. The server ID is set with the variable " +"`jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment " +"variables in the JVB docker container. This variable can be set via the " +"host file, a parameter to the ansible command or in the `vars.yaml` for " +"the host which will have the additional JVB. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:190 +msgid "" +"Note that the server ID `jvb-1` is reserved for the JVB instance running " +"on the Matrix host and therefore should not be used as the ID of an " +"additional jvb host." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:192 +msgid "" +"The additional JVB will also need to expose the colibri web socket port " +"and this can be done with the following variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:198 +msgid "" +"The JVB will also need to know where the prosody xmpp server is located, " +"similar to the server ID this can be set in the vars for the JVB by using" +" the variable `jitsi_xmpp_server`. The Jitsi prosody container is " +"deployed on the Matrix server by default so the value can be set to the " +"Matrix domain. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:204 +msgid "" +"However, it can also be set the ip address of the Matrix server. This can" +" be useful if you wish to use a private ip. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:210 +msgid "" +"For the JVB to be able to contact the XMPP server, the latter must expose" +" the XMPP port (5222). By default, the Matrix server does not expose the " +"port; only the XMPP container exposes it internally inside the host, " +"which means that the first JVB (which runs on the Matrix server) can " +"reach it but the additional JVB cannot. The port is exposed by setting " +"`jitsi_prosody_container_jvb_host_bind_port` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:216 +msgid "(The default is empty; if it's set then docker forwards the port.)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:218 +msgid "" +"Applied together this will allow you to provision extra JVB instances " +"which will register themselves with the prosody service and be available " +"for jicofo to route conferences too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:220 +msgid "" +"To make Traefik reverse-proxy to these additional JVBs (living on other " +"hosts), **you would need to add the following Traefik configuration " +"extension**:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:256 +msgid "(Optional) Enable Gravatar" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:258 +msgid "" +"In the default Jisti Meet configuration, gravatar.com is enabled as an " +"avatar service. This results in third party request leaking data to " +"gravatar. Since Element clients already send the url of configured Matrix" +" avatars to Jitsi, we disabled gravatar." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:260 +msgid "To enable Gravatar set:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:266 +msgid "" +"**Beware**: This leaks information to a third party, namely the Gravatar-" +"Service (unless configured otherwise: gravatar.com). Besides metadata, " +"this includes the Matrix user_id and possibly the room identifier (via " +"`referrer` header)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:268 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:270 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:277 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:279 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:281 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:283 +msgid "You can use the self-hosted Jitsi server in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:285 +msgid "" +"**by adding a widget to a room via Element Web** (the one configured by " +"the playbook at `https://element.example.com`). Just start a voice or a " +"video call in a room containing more than 2 members and that would create" +" a Jitsi widget which utilizes your self-hosted Jitsi server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:287 +msgid "" +"**by adding a widget to a room via the Dimension integration manager**. " +"You'll have to point the widget to your own Jitsi server manually. See " +"our [Dimension integration manager](./configuring-playbook-dimension.md) " +"documentation page for more details. Naturally, Dimension would need to " +"be installed first (the playbook doesn't install it by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:289 +msgid "" +"**directly (without any Matrix integration)**. Just go to " +"`https://jitsi.example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:291 +msgid "" +"**Note**: Element apps on mobile devices currently [don't support joining" +" meetings on a self-hosted Jitsi server](https://github.com/element-hq" +"/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md" +"#mobile-app-support)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:293 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:295 +msgid "Rebuilding your Jitsi installation" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:297 +msgid "" +"**If you ever run into any trouble** or **if you change configuration " +"(`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi " +"setup." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:299 +msgid "" +"We normally don't require such manual intervention for other services, " +"but Jitsi services generate a lot of configuration files on their own." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:301 +msgid "" +"These files are not all managed by Ansible (at least not yet), so you may" +" sometimes need to delete them all and start fresh." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:303 +msgid "To rebuild your Jitsi configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:305 +msgid "" +"ask Ansible to stop all Jitsi services: `just run-tags stop-group " +"--extra-vars=group=jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:306 +msgid "" +"SSH into the server and do this and remove all Jitsi configuration & data" +" (`rm -rf /matrix/jitsi`)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:307 +msgid "" +"ask Ansible to set up Jitsi anew and restart services (`just install-" +"service jitsi`)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po new file mode 100644 index 000000000..ebb1713a3 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po @@ -0,0 +1,84 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-ldap-auth.md:1 +msgid "" +"Setting up the LDAP authentication password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:3 +msgid "" +"The playbook can install and configure the [matrix-synapse-" +"ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth " +"password provider for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:7 +msgid "" +"If you decide that you'd like to let this playbook install it for you, " +"add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:24 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:26 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:32 +msgid "Using ma1sd Identity Server for authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:34 +msgid "" +"If you wish to use the ma1sd Identity Server for LDAP authentication " +"instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-" +"synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration" +"](configuring-playbook-ma1sd.md#authentication)." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:36 +msgid "Handling user registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:38 +msgid "" +"If you wish for users to also be able to make new registrations against " +"LDAP, you may **also** wish to [set up the ldap-registration-proxy" +"](configuring-playbook-matrix-ldap-registration-proxy.md)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po new file mode 100644 index 000000000..96aae51be --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -0,0 +1,335 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-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) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:11 +msgid "" +"**Note**: enabling ma1sd, means that the `openid` API endpoints will be " +"exposed on the Matrix Federation port (usually `8448`), even if " +"[federation](configuring-playbook-federation.md) is disabled. It's " +"something to be aware of, especially in terms of firewall whitelisting " +"(make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:13 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:15 +msgid "" +"To make the ma1sd Identity Server enable its federation features, set up " +"a SRV record that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:17 +msgid "Name: `_matrix-identity._tcp` (use this text as-is)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:18 +msgid "" +"Content: `10 0 443 matrix.example.com` (replace `example.com` with your " +"own)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:20 +msgid "" +"See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-" +"and-your-privacy#choices-are-never-easy) for information on the privacy " +"implications of setting up this SRV record." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:22 +msgid "" +"**Note**: This `_matrix-identity._tcp` SRV record for the identity server" +" is different from the `_matrix._tcp` that can be used for Synapse " +"delegation. See [howto-server-delegation.md](howto-server-delegation.md) " +"for more information about delegation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:24 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:26 +msgid "" +"To enable ma1sd, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:32 +msgid "Matrix.org lookup forwarding" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:34 +msgid "" +"To ensure maximum discovery, you can make your identity server also " +"forward lookups to the central matrix.org Identity server (at the cost of" +" potentially leaking all your contacts information)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:36 +msgid "" +"Enabling this is discouraged and you'd better [learn " +"more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups)" +" before proceeding." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:38 +msgid "" +"To enable matrix.org forwarding, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:44 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:46 +msgid "" +"What this playbook configures for your is some bare minimum Identity " +"Server functionality, so that you won't need to rely on external 3rd " +"party services." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:48 +msgid "" +"A few variables can be toggled in this playbook to alter the ma1sd " +"configuration that gets generated." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:50 +msgid "" +"Still, ma1sd can do much more. You can refer to the [ma1sd " +"website](https://github.com/ma1uta/ma1sd) for more details and " +"configuration options." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:52 +msgid "" +"To use a more custom configuration, you can define a " +"`matrix_ma1sd_configuration_extension_yaml` string variable and put your " +"configuration in it. To learn more about how to do this, refer to the " +"information about `matrix_ma1sd_configuration_extension_yaml` in the " +"[default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) " +"of the ma1sd component." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:54 +msgid "Customizing email templates" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:56 +msgid "" +"If you'd like to change the default email templates used by ma1sd, take a" +" look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in " +"the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:58 +msgid "ma1sd-controlled Registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:60 +msgid "" +"To use the " +"[Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" +" feature of ma1sd, you can make use of the following variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:62 +msgid "" +"`matrix_synapse_enable_registration` - to enable user-initiated " +"registration in Synapse" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:64 +msgid "" +"`matrix_synapse_enable_registration_captcha` - to validate registering " +"users using reCAPTCHA, as described in the [enabling reCAPTCHA" +"](configuring-captcha.md) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:66 +msgid "" +"`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among" +" `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:68 +msgid "" +"variables prefixed with `matrix_ma1sd_container_labels_` (e.g. " +"`matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) " +"- to configure the Traefik reverse-proxy to capture and send registration" +" requests to ma1sd (instead of Synapse), so it can apply its additional " +"functionality" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:70 +msgid "" +"`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as " +"required. See the [Registration feature's " +"docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" +" for inspiration. Also see the [Additional features](#additional-" +"features) section below to learn more about how to use " +"`matrix_ma1sd_configuration_extension_yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:72 +msgid "" +"**Note**: For this to work, either the homeserver needs to [federate" +"](configuring-playbook-federation.md) or the `openid` APIs need to " +"exposed on the federation port. When federation is disabled and ma1sd is " +"enabled, we automatically expose the `openid` APIs (only!) on the " +"federation port. Make sure the federation port (usually " +"`https://matrix.example.com:8448`) is whitelisted in your firewall (even " +"if you don't actually use/need federation)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:74 +msgid "Authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:76 +msgid "" +"[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md)" +" provides the possibility to use your own [Identity " +"Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md)" +" (for example LDAP) to authenticate users on your Homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:78 +msgid "" +"To enable authentication against an LDAP server, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:98 +msgid "Example: SMS verification" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:100 +msgid "" +"If your use case requires mobile verification, it is quite simple to " +"integrate ma1sd with [Twilio](https://www.twilio.com/), an online " +"telephony services gateway. Their prices are reasonable for low-volume " +"projects and integration can be done with the following configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:114 +msgid "Example: Open Registration for every Domain" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:116 +msgid "" +"If you want to open registration for any domain, you have to setup the " +"allowed domains with ma1sd's `blacklist` and `whitelist`. The default " +"behavior when neither the `blacklist`, nor the `whitelist` match, is to " +"allow registration. Beware: you can't block toplevel domains (aka `.xy`) " +"because the internal architecture of ma1sd doesn't allow that." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:130 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:132 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:139 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:141 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:143 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:145 +msgid "" +"If email address validation emails sent by ma1sd are not reaching you, " +"you should look into [Adjusting email-sending settings](configuring-" +"playbook-email.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:147 +msgid "" +"If you'd like additional logging information, temporarily enable verbose " +"logging for ma1sd." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:149 +msgid "" +"To enable it, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po new file mode 100644 index 000000000..f10c16f93 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po @@ -0,0 +1,1045 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-matrix-authentication-service.md:1 +msgid "Setting up Matrix Authentication Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3 +msgid "" +"This playbook can install and configure [Matrix Authentication " +"Service](https://github.com/element-hq/matrix-authentication-service/) " +"(MAS) - a service operating alongside your existing [Synapse" +"](./configuring-playbook-synapse.md) homeserver and providing [better " +"authentication, session management and permissions in " +"Matrix](https://matrix.org/blog/2023/09/better-auth/)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5 +msgid "" +"Matrix Authentication Service is an implementation of [MSC3861: Next-" +"generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com" +"/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, " +"tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7 +msgid "" +"**Before going through with starting to use Matrix Authentication " +"Service**, make sure to read:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9 +msgid "" +"the [Reasons to use Matrix Authentication Service](#reasons-to-use-" +"matrix-authentication-service) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10 +msgid "the [Expectations](#expectations) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11 +msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13 +msgid "" +"**If you've already been using Synapse** and have user accounts in its " +"database, you can [migrate to Matrix Authentication Service](#migrating-" +"an-existing-synapse-homeserver-to-matrix-authentication-service)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15 +msgid "Reasons to use Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17 +msgid "" +"You may be wondering whether you should make the switch to Matrix " +"Authentication Service (MAS) or keep using your existing authentication " +"flow via Synapse (password-based or [OIDC](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19 +msgid "" +"Matrix Authentication Service is **still an experimental service** and " +"**not a default** for this Ansible playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21 +msgid "" +"The [Expectations](#expectations) section contains a list of what works " +"and what doesn't (**some services don't work with MAS yet**), as well as " +"the **relative irreversability** of the migration process." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23 +msgid "" +"Below, we'll try to **highlight some potential reasons for switching** to" +" Matrix Authentication Service:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25 +msgid "" +"To use SSO in [Element X](https://element.io/blog/element-x-ignition/). " +"The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-" +"connect-for-single-sign-on) login flow is only supported in old Element " +"clients and will not be supported in Element X. Element X will only " +"support the new SSO-based login flow provided by MAS, so if you want to " +"use SSO with Element X, you will need to switch to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27 +msgid "" +"To help drive adoption of the \"Next-generation auth for Matrix\" by " +"switching to what's ultimately coming anyway" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29 +msgid "" +"To help discover (and potentially fix) MAS integration issues with this " +"Ansible playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31 +msgid "" +"To help discover (and potentially fix) MAS integration issues with " +"various other Matrix components (bridges, bots, clients, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33 +msgid "" +"To reap some of the security benefits that Matrix Authentication Service " +"offers, as outlined in the [Better authentication, session management and" +" permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) " +"article." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37 +msgid "" +"⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver " +"implementation (which is the default for this playbook). Other homeserver" +" implementations ([Dendrite](./configuring-playbook-dendrite.md), " +"[Conduit](./configuring-playbook-conduit.md), etc.) do not support " +"integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39 +msgid "" +"⚠️ **email sending** configured (see [Adjusting email-sending settings" +"](./configuring-playbook-email.md)), because **Matrix Authentication " +"Service [still insists](https://github.com/element-hq/matrix-" +"authentication-service/issues/1505) on having a verified email address " +"for each user** going through the new SSO-based login flow. It's also " +"possible to [work around email deliverability issues](#working-around-" +"email-deliverability-issues) if your email configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41 +msgid "" +"❌ **disabling all password providers** for Synapse (things like [shared-" +"secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth" +"](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-" +"playbook-ldap-auth.md), etc.) More details about this are available in " +"the [Expectations](#expectations) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43 +msgid "Expectations" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45 +msgid "" +"This section details what you can expect when switching to the Matrix " +"Authentication Service (MAS)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47 +msgid "" +"❌ **Synapse password providers will need to be disabled**. You can no " +"longer use [shared-secret-auth](./configuring-playbook-shared-secret-" +"auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth" +"](./configuring-playbook-ldap-auth.md), etc. When the authentication flow" +" is handled by MAS (not by Synapse anymore), it doesn't make sense to " +"extend the Synapse authentication flow with additional modules. Many " +"bridges used to rely on shared-secret-auth for doing double-puppeting " +"(impersonating other users), but most (at least the mautrix bridges) " +"nowadays use [Appservice Double Puppet](./configuring-playbook-" +"appservice-double-puppet.md) as a better alternative. Older/maintained " +"bridges may still rely on shared-secret-auth, as do other services like " +"[matrix-corporal](./configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49 +msgid "" +"❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-" +"admin.md) do not have full compatibility with MAS yet**. synapse-admin " +"already supports [login with access token](https://github.com/etkecc" +"/synapse-admin/pull/58), browsing users (which Synapse will internally " +"fetch from MAS) and updating user avatars. However, editing users " +"(passwords, etc.) now needs to happen directly against MAS using the [MAS" +" Admin API](https://element-hq.github.io/matrix-authentication-" +"service/api/index.html), which synapse-admin cannot interact with yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51 +msgid "❌ **Some services experience issues when authenticating via MAS**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53 +msgid "" +"[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first" +" time around, but it consistently fails after restarting:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55 +msgid "" +"cannot initialize matrix bot error=\"olm account is marked as shared, " +"keys seem to have disappeared from the server\"" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57 +msgid "" +"[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) " +"fails to start (see [element-hq/matrix-authentication-" +"service#3439](https://github.com/element-hq/matrix-authentication-" +"service/issues/3439))" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58 +msgid "Other services may be similarly affected. This list is not exhaustive." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60 +msgid "" +"❌ **Encrypted appservices** do not work yet (related to " +"[MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) " +"and [PR 17705 for Synapse](https://github.com/element-" +"hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will" +" fail to start (see [this issue](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/3658) for Hookshot). You can use these " +"bridges/bots only if you **keep end-to-bridge encryption disabled** " +"(which is the default setting)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62 +msgid "" +"⚠️ **You will need to have email sending configured** (see [Adjusting " +"email-sending settings](./configuring-playbook-email.md)), because " +"**Matrix Authentication Service [still insists](https://github.com" +"/element-hq/matrix-authentication-service/issues/1505) on having a " +"verified email address for each user** going through the new SSO-based " +"login flow. It's also possible to [work around email deliverability " +"issues](#working-around-email-deliverability-issues) if your email " +"configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64 +msgid "" +"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " +"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" +"authentication-service) is **possible**, but requires **some playbook-" +"assisted manual work**. Migration is **reversible with no or minor issues" +" if done quickly enough**, but as users start logging in (creating new " +"login sessions) via the new MAS setup, disabling MAS and reverting back " +"to the Synapse user database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66 +msgid "" +"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " +"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" +"authentication-service) does not currently seem to preserve the \"admin\"" +" flag for users (as found in the Synapse database). All users are " +"imported as non-admin - see [element-hq/matrix-authentication-" +"service#3440](https://github.com/element-hq/matrix-authentication-" +"service/issues/3440). You may need update the Matrix Authentication " +"Service's database manually and adjust the `can_request_admin` column in " +"the `users` table to `true` for users that need to be administrators " +"(e.g. `UPDATE users SET can_request_admin = true WHERE username = " +"'someone';`)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68 +msgid "" +"⚠️ Delegating user authentication to MAS causes **your Synapse server to " +"be completely dependant on one more service** for its operations. MAS is " +"quick & lightweight and should be stable enough already, but this is " +"something to keep in mind when making the switch." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70 +msgid "" +"⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " +"migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 " +"configuration](#upstream-oauth2-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72 +msgid "" +"⚠️ A [compatibility layer](https://element-hq.github.io/matrix-" +"authentication-service/setup/homeserver.html#set-up-the-compatibility-" +"layer) is installed - all `/_matrix/client/*/login` (etc.) requests will " +"be routed to MAS instead of going to the homeserver. This is done both " +"publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and " +"on the internal Traefik entrypoint (e.g. `https://matrix-" +"traefik:8008/_matrix/client/*/login`) which helps addon services reach " +"the homeserver's Client-Server API. You typically don't need to do " +"anything to make this work, but it's good to be aware of it, especially " +"if you have a [custom webserver setup](./configuring-playbook-own-" +"webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74 +msgid "" +"✅ Your **existing login sessions will continue to work** (you won't get " +"logged out). Migration will require a bit of manual work and minutes of " +"downtime, but it's not too bad." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76 +msgid "" +"✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), " +"[Element Web](./configuring-playbook-client-element-web.md), Element X, " +"FluffyChat) will be able to use the **new SSO-based login flow** provided" +" by Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78 +msgid "" +"✅ The **old login flow** (called `m.login.password`) **will still " +"continue to work**, so clients (old Element Web, etc.) and bridges/bots " +"that don't support the new OIDC-based login flow will still work. Going " +"through the old login flow does not require users to have a verified " +"email address, as [is the case](https://github.com/element-hq/matrix-" +"authentication-service/issues/1505) for the new SSO-based login flow." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80 +msgid "" +"✅ [Registering users](./registering-users.md) via **the playbook's " +"`register-user` tag remains unchanged**. The playbook automatically does " +"the right thing regardless of homeserver implementation (Synapse, " +"Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, " +"the playbook will forward user-registration requests to MAS. Registering " +"users via the command-line is no longer done via the " +"`/matrix/synapse/bin/register` script, but via `/matrix/matrix-" +"authentication-service/bin/register-user`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82 +msgid "" +"✅ Users that are prepared by the playbook (for bots, bridges, etc.) will " +"continue to be registered automatically as expected. The playbook " +"automatically does the right thing regardless of homeserver " +"implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or " +"not. When MAS is enabled, the playbook will forward user-registration " +"requests to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84 +msgid "Installation flows" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86 +msgid "New homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88 +msgid "" +"For new homeservers (which don't have any users in their Synapse database" +" yet), follow the [Adjusting the playbook configuration](#adjusting-the-" +"playbook-configuration) instructions and then proceed with " +"[Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90 +msgid "Existing homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92 +msgid "" +"Other homeserver implementations ([Dendrite](./configuring-playbook-" +"dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not " +"support integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94 +msgid "For existing Synapse homeservers:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96 +msgid "" +"when following the [Adjusting the playbook configuration](#adjusting-the-" +"playbook-configuration) instructions, make sure to **disable the " +"integration between Synapse and MAS** by **uncommenting** the " +"`matrix_authentication_service_migration_in_progress: true` line as " +"described in the [Marking an existing homeserver for migration](#marking-" +"an-existing-homeserver-for-migration) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98 +msgid "" +"then follow the [Migrating an existing Synapse homeserver to Matrix " +"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" +"matrix-authentication-service) instructions to perform the installation " +"and migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102 +msgid "" +"To enable Matrix Authentication Service, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116 +msgid "" +"In the sub-sections that follow, we'll cover some additional " +"configuration options that you may wish to adjust." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118 +msgid "" +"There are many other configuration options available. Consult the " +"[`defaults/main.yml` file](../roles/custom/matrix-authentication-" +"service/defaults/main.yml) in the [matrix-authentication-service " +"role](../roles/custom/matrix-authentication-service/) to discover them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120 +msgid "Adjusting the Matrix Authentication Service URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122 +msgid "" +"By default, this playbook installs the Matrix Authentication Service on " +"the `matrix.` subdomain, at the `/auth` path " +"(https://matrix.example.com/auth). This makes it easy to install it, " +"because it **doesn't require additional DNS records to be set up**. If " +"that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:124 +msgid "" +"By tweaking the `matrix_authentication_service_hostname` and " +"`matrix_authentication_service_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:126 +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134 +msgid "Marking an existing homeserver for migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136 +msgid "" +"The [configuration above](#adjusting-the-playbook-configuration) " +"instructs existing users wishing to migrate to add " +"`matrix_authentication_service_migration_in_progress: true` to their " +"configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138 +msgid "" +"This is done temporarily. The migration steps are described in more " +"detail in the [Migrating an existing Synapse homeserver to Matrix " +"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" +"matrix-authentication-service) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140 +msgid "Upstream OAuth2 configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142 +msgid "" +"To make Matrix Authentication Service delegate to an existing upstream " +"OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` " +"setting](https://element-hq.github.io/matrix-authentication-" +"service/reference/configuration.html#upstream_oauth2providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144 +msgid "" +"The playbook exposes a " +"`matrix_authentication_service_config_upstream_oauth2_providers` variable" +" for controlling this setting." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261 +msgid "" +"💡 Refer to the [`upstream_oauth2.providers` setting](https://element-" +"hq.github.io/matrix-authentication-" +"service/reference/configuration.html#upstream_oauth2providers) for the " +"most up-to-date schema and example for providers. The value shown above " +"here may be out of date." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263 +msgid "" +"⚠️ The syntax for existing [OIDC providers configured in Synapse" +"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" +"sign-on) is slightly different, so you will need to adjust your " +"configuration when switching from Synapse OIDC to MAS upstream OAuth2." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265 +msgid "" +"⚠️ When [migrating an existing homeserver](#migrating-an-existing-" +"synapse-homeserver-to-matrix-authentication-service) which contains OIDC-" +"sourced users, you will need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267 +msgid "" +"[Configure upstream OIDC provider mapping for syn2mas](#configuring-" +"upstream-oidc-provider-mapping-for-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268 +msgid "" +"go through the [migrating an existing homeserver](#migrating-an-existing-" +"synapse-homeserver-to-matrix-authentication-service) process" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269 +msgid "" +"remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) " +"to prevent it being in conflict with the MAS OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Matrix Authentication Service domain to the " +"Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281 +msgid "" +"Now that you've [adjusted the playbook configuration](#adjusting-the-" +"playbook-configuration) and [your DNS records](#adjusting-dns-records), " +"you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294 +msgid "" +"If you're in the process of migrating an existing Synapse homeserver to " +"MAS, you should now follow the rest of the steps in the [Migrating an " +"existing Synapse homeserver to Matrix Authentication Service](#migrating-" +"an-existing-synapse-homeserver-to-matrix-authentication-service) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296 +msgid "" +"💡 After installation, you should [verify that Matrix Authentication " +"Service is installed correctly](#verify-that-matrix-authentication-" +"service-is-installed-correctly)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298 +msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300 +msgid "" +"Our migration guide is loosely based on the upstream [Migrating an " +"existing homeserver](https://element-hq.github.io/matrix-authentication-" +"service/setup/migration.html) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302 +msgid "" +"Migration is done via a tool called `syn2mas`, which the playbook could " +"run for you (in a container)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304 +msgid "The installation + migration steps are like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306 +msgid "" +"[Adjust your configuration](#adjusting-the-playbook-configuration) to " +"**disable the integration between the homeserver and MAS**. This is done " +"by **uncommenting** the " +"`matrix_authentication_service_migration_in_progress: true` line." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308 +msgid "Perform the initial [installation](#installing). At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310 +msgid "" +"Matrix Authentication Service will be installed. Its database will be " +"empty, so it cannot validate existing access tokens or authentication " +"users yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312 +msgid "" +"The homeserver will still continue to use its local database for " +"validating existing access tokens." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314 +msgid "" +"Various [compatibility layer URLs](https://element-hq.github.io/matrix-" +"authentication-service/setup/homeserver.html#set-up-the-compatibility-" +"layer) are not yet installed. New login sessions will still be forwarded " +"to the homeserver, which is capable of completing them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316 +msgid "" +"The `matrix-user-creator` role would be suppressed, so that it doesn't " +"automatically attempt to create users (for bots, etc.) in the MAS " +"database. These user accounts likely already exist in Synapse's user " +"database and could be migrated over (via syn2mas, as per the steps " +"below), so creating them in the MAS database would have been unnecessary " +"and potentially problematic (conflicts during the syn2mas migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318 +msgid "" +"Consider taking a full [backup of your Postgres database](./maintenance-" +"postgres.md#backing-up-postgresql). This is done just in case. The " +"**syn2mas migration tool does not delete any data**, so it should be " +"possible to revert to your previous setup by merely disabling MAS and re-" +"running the playbook (no need to restore a Postgres backup). However, do " +"note that as users start logging in (creating new login sessions) via the" +" new MAS setup, disabling MAS and reverting back to the Synapse user " +"database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320 +msgid "" +"[Migrate your data from Synapse to Matrix Authentication Service using " +"syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-" +"service-using-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322 +msgid "" +"[Adjust your configuration](#adjusting-the-playbook-configuration) again," +" to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324 +msgid "" +"remove the `matrix_authentication_service_migration_in_progress: false` " +"line" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326 +msgid "" +"if you had been using [OIDC providers configured in Synapse" +"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" +"sign-on), remove all Synapse OIDC-related configuration " +"(`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS " +"OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328 +msgid "Perform the [installation](#installing) again. At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330 +msgid "The homeserver will start delegating authentication to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332 +msgid "" +"The compatibility layer URLs will be installed. New login sessions will " +"be completed by MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334 +msgid "" +"[Verify that Matrix Authentication Service is installed correctly" +"](#verify-that-matrix-authentication-service-is-installed-correctly)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336 +msgid "" +"Migrate your data from Synapse to Matrix Authentication Service using " +"syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338 +msgid "" +"We **don't** ask you to [run the `syn2mas` migration advisor " +"command](https://element-hq.github.io/matrix-authentication-" +"service/setup/migration.html#run-the-migration-advisor), because it only " +"gives you the green light if your Synapse configuration " +"(`homeserver.yaml`) is configured in a way that's compatible with MAS " +"(delegating authentication to MAS; disabling Synapse's password config; " +"etc.). Until we migrate your data with the `syn2mas` tool, we " +"intentionally avoid doing these changes to allow existing user sessions " +"to work." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340 +msgid "" +"You can invoke the `syn2mas` tool via the playbook by running the " +"playbook's `matrix-authentication-service-syn2mas` tag. We recommend " +"first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " +"migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342 +msgid "Configuring syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344 +msgid "" +"If you're using [OIDC with Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " +"[Configuring upstream OIDC provider mapping for syn2mas](#configuring-" +"upstream-oidc-provider-mapping-for-syn2mas)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346 +msgid "" +"If you only have local (non-OIDC) users in your Synapse database, you can" +" likely run `syn2mas` as-is (without doing additional configuration " +"changes)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348 +msgid "" +"When you're done with potentially configuring `syn2mas`, proceed to doing" +" a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " +"migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350 +msgid "Configuring upstream OIDC provider mapping for syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352 +msgid "" +"If you have existing OIDC users in your Synapse user database (which will" +" be the case if when using [OIDC with Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to " +"pass an additional `--upstreamProviderMapping` argument to the `syn2mas` " +"tool to tell it which provider (on the Synapse side) maps to which other " +"provider on the MAS side." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354 +msgid "If you don't do this, `syn2mas` would report errors like this one:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356 +msgid "" +"[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-" +"b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: " +"Unknown upstream provider oidc-keycloak]" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358 +msgid "Below is an example situation and a guide for how to solve it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360 +msgid "" +"If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) " +"named `keycloak`, in the Synapse database users would be associated with " +"the `oidc-keycloak` provider (note the `oidc-` prefix that was added " +"automatically by Synapse to your `idp_id` value)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362 +msgid "" +"The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` " +"on the MAS side, as defined in " +"`matrix_authentication_service_config_upstream_oauth2_providers` (see the" +" [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section " +"above)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364 +msgid "" +"To tell `syn2mas` how the Synapse-configured OIDC provider maps to the " +"new MAS-configured OIDC provider, add this additional configuration to " +"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373 +msgid "Performing a syn2mas dry-run" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375 +msgid "" +"Having [configured syn2mas](#configuring-syn2mas), we recommend doing a " +"[dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to " +"verify that everything will work out as expected." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377 +msgid "A dry-run would not cause downtime, because it avoids stopping Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379 +msgid "To perform a dry-run, run:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385 +msgid "" +"Observe the command output (especially the last line of the the syn2mas " +"output). If you are confident that the migration will work out as " +"expected, you can proceed with a [real migration](#performing-a-real-" +"syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387 +msgid "Performing a real syn2mas migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389 +msgid "Before performing a real migration make sure:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391 +msgid "you've familiarized yourself with the [expectations](#expectations)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393 +msgid "you've performed a Postgres backup, just in case" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395 +msgid "" +"you're aware of the irreversibility of the migration process without " +"disruption after users have created new login sessions via the new MAS " +"setup" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397 +msgid "" +"you've [configured syn2mas](#configuring-syn2mas), especially if you've " +"used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse" +"--openid-connect-for-single-sign-on)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399 +msgid "" +"you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and " +"don't see any issues in its output" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401 +msgid "" +"To perform a real migration, run the `matrix-authentication-service-" +"syn2mas` tag **without** the " +"`matrix_authentication_service_syn2mas_dry_run` variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407 +msgid "" +"Having performed a `syn2mas` migration once, trying to do it again will " +"report errors for users that were already migrated (e.g. \"Error: Unknown" +" upstream provider oauth-delegated\")." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409 +msgid "Verify that Matrix Authentication Service is installed correctly" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411 +msgid "" +"After [installation](#installing), run the `doctor` subcommand of the " +"[`mas-cli` command-line tool](https://element-hq.github.io/matrix-" +"authentication-service/reference/cli/index.html) to verify that MAS is " +"installed correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413 +msgid "You can do it:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415 +msgid "" +"either via the Ansible playbook's `matrix-authentication-service-mas-cli-" +"doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417 +msgid "" +"or by running the `mas-cli` script on the server (which invokes the `mas-" +"cli` tool inside a container): `/matrix/matrix-authentication-service/bin" +"/mas-cli doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419 +msgid "If successful, you should see some output that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431 +msgid "Management" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433 +msgid "" +"You can use the [`mas-cli` command-line tool](https://element-" +"hq.github.io/matrix-authentication-service/reference/cli/index.html) " +"(exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` " +"script) to perform administrative tasks against MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435 +msgid "This documentation page already mentions:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437 +msgid "" +"the `mas-cli doctor` sub-command in the [Verify that Matrix " +"Authentication Service is installed correctly](#verify-that-matrix-" +"authentication-service-is-installed-correctly) section, which you can run" +" via the CLI and via the Ansible playbook's `matrix-authentication-" +"service-mas-cli-doctor` tag" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439 +msgid "" +"the `mas-cli manage register-user` sub-command in the [Registering users" +"](./registering-users.md) documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441 +msgid "" +"There are other sub-commands available. Run `/matrix/matrix-" +"authentication-service/bin/mas-cli` to get an overview." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443 +msgid "User registration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445 +msgid "" +"After Matrix Authentication Service is [installed](#installing), users " +"need to be managed there (unless you're managing them in an [upstream " +"OAuth2 provider](#upstream-oauth2-configuration))." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447 +msgid "" +"You can register users new users as described in the [Registering users" +"](./registering-users.md) documentation (via `mas-cli manage register-" +"user` or the Ansible playbook's `register-user` tag)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449 +msgid "Working around email deliverability issues" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451 +msgid "" +"Because Matrix Authentication Service [still insists](https://github.com" +"/element-hq/matrix-authentication-service/issues/1505) on having a " +"verified email address for each user, you may need to work around email " +"deliverability issues if [your email-sending configuration" +"](./configuring-playbook-email.md) is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453 +msgid "" +"Matrix Authentication Service attempts to verify email addresses by " +"sending a verification email to the address specified by the user " +"whenever they log in to an account without a verified email address." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455 +msgid "" +"If email delivery is not working, **you can retrieve the email " +"configuration code from the Matrix Authentication Service's logs** " +"(`journalctl -fu matrix-authentication-service`)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457 +msgid "" +"Alternatively, you can use the [`mas-cli` management tool](#management) " +"to manually verify email addresses for users. Example: `/matrix/matrix-" +"authentication-service/bin/mas-cli manage verify-email some.username " +"email@example.com`" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po new file mode 100644 index 000000000..81721ce7b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po @@ -0,0 +1,185 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-corporal.md:1 +msgid "Setting up Matrix Corporal (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:5 +msgid "" +"**WARNING**: This is an advanced feature! It requires prior experience " +"with Matrix and a specific need for using [Matrix " +"Corporal](https://github.com/devture/matrix-corporal). If you're unsure " +"whether you have such a need, you most likely don't." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:9 +msgid "" +"The playbook can install and configure [matrix-" +"corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:11 +msgid "" +"In short, it's a sort of automation and firewalling service, which is " +"helpful if you're instaling Matrix services in a controlled corporate " +"environment. See that project's documentation to learn what it does and " +"why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:13 +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:14 +msgid "" +"(required) [set up the Shared Secret Auth password provider module" +"](configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +msgid "" +"(optional, but encouraged) [set up the REST authentication password " +"provider module](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:19 +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:72 +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:74 +msgid "" +"No matter what Matrix user ID you configure to run it with, make sure " +"that:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +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:78 +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:80 +msgid "Using a locally-stored static policy" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +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:114 +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:116 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +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:127 +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:129 +msgid "Matrix Corporal files" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +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:133 +msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +msgid "" +"`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " +"write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +msgid "" +"`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" +" and write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +msgid "" +"As an example: you can create your own configuration files in " +"`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " +"in the Docker container. Your configuration (stuff in " +"`matrix_corporal_policy_provider_config`) needs to refer to these files " +"via the local container paths - `/etc/matrix-corporal` (read-only), `/var" +"/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read " +"and write)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po new file mode 100644 index 000000000..690380370 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po @@ -0,0 +1,90 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-ldap-registration-proxy.md:1 +msgid "Setting up matrix-ldap-registration-proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 +msgid "" +"The playbook can install and configure [matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 +msgid "This proxy handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 +msgid "" +"**Note**: This does support the full Matrix specification for " +"registrations. It only provide a very coarse implementation of a basic " +"password registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 +msgid "" +"If you already use the [synapse external password provider via LDAP" +"](configuring-playbook-ldap-auth.md) (that is, you have " +"`matrix_synapse_ext_password_provider_ldap_enabled: true` and other " +"options in your configuration) you can use the following values as " +"configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po new file mode 100644 index 000000000..48e5a091b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po @@ -0,0 +1,257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-media-repo.md:1 +msgid "Storing Matrix media files using matrix-media-repo (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:3 +msgid "" +"[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often " +"abbreviated \"MMR\") is a highly customizable multi-domain media " +"repository for Matrix. Intended for medium to large environments " +"consisting of several homeservers, this media repo de-duplicates media " +"(including remote media) while being fully compliant with the " +"specification." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:5 +msgid "" +"Smaller/individual homeservers can still make use of this project's " +"features, though it may be difficult to set up or have higher than " +"expected resource consumption. Please do your research before deploying " +"this as this project may not be useful for your environment." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:7 +msgid "" +"For a simpler alternative (which allows you to offload your media " +"repository storage to S3, etc.), you can [configure S3 storage" +"](configuring-playbook-s3.md) instead of setting up matrix-media-repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "**Table of Contents**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Quickstart](#quickstart)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Additional configuration options](#configuring-the-media-repo)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "" +"[Importing data from an existing media store](#importing-data-from-an-" +"existing-media-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:15 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the " +"installation process](./installing.md) for the playbook:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:26 +msgid "" +"The repo is pre-configured for integrating with the Postgres database, " +"Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-" +"grafana.md) (if metrics enabled) from this playbook for all the available" +" homeserver roles. When the media repo is enabled, other media store " +"roles should be disabled (if using Synapse with other media store roles)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:28 +msgid "" +"By default, the media-repo will use the local filesystem for data " +"storage. You can alternatively use a `s3` cloud backend as well. Access " +"token caching is also enabled by default since the logout endpoints are " +"proxied through the media repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:30 +msgid "Configuring the media-repo" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:32 +msgid "Additional common configuration options:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:91 +msgid "" +"Full list of configuration options with documentation can be found in " +"[`roles/custom/matrix-media-" +"repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/master/roles/custom/matrix-media-" +"repo/defaults/main.yml)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:93 +msgid "Signing Keys" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:95 +msgid "" +"Authenticated media endpoints ([MSC3916](https://github.com/matrix-org" +"/matrix-spec-proposals/pull/3916)) requires MMR to have a configured " +"signing key to authorize outbound federation requests. Additionally, the " +"signing key must be merged with your homeserver's signing key file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:97 +msgid "" +"The playbook default is to generate a MMR signing key when invoking the " +"setup role and merge it with your homeserver if you are using Synapse or " +"Dendrite. This can be disabled if desired by setting the option in your " +"inventory:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:103 +msgid "" +"If you wish to manually generate the signing key and merge it with your " +"homeserver's signing key file, see https://docs.t2bot.io/matrix-media-" +"repo/v1.3.5/installation/signing-key/ for more details." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:105 +msgid "" +"**Note that if you uninstall MMR from the playbook, it will not remove " +"the old MMR signing key from your homeserver's signing key file. You will" +" have to remove it manually.**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:107 +msgid "Key backup and revoking" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:109 +msgid "" +"Since your homeserver signing key file is modified by the playbook, a " +"backup will be created in " +"`HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to " +"remove/revoke old keys, you can restore from this backup or remove the " +"MMR key ID from your `example.com.signing.key` file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:111 +msgid "" +"Additionally, its recommended after revoking a signing key to update your" +" homeserver config file (`old_signing_keys` field for Synapse and " +"`old_private_keys` for Dendrite). See your homeserver config file for " +"further documentation on how to populate the field." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:113 +msgid "Importing data from an existing media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:115 +msgid "" +"If you want to add this repo to an existing homeserver managed by the " +"playbook, you will need to import existing media into MMR's database or " +"you will lose access to older media while it is active. MMR versions up " +"to `v1.3.3` only support importing from Synapse, but newer versions (at " +"time of writing: only `latest`) also support importing from Dendrite." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:117 +msgid "" +"**Before importing**: ensure you have an initial matrix-media-repo " +"deployment by following the [quickstart](#quickstart) guide above" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:119 +msgid "" +"Depending on the homeserver implementation yu're using (Synapse, " +"Dendrite), you'll need to use a different import tool (part of matrix-" +"media-repo) and point it to the homeserver's database." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:121 +msgid "Importing data from the Synapse media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:123 +msgid "" +"To import the Synapse media store, you're supposed to invoke the " +"`import_synapse` tool which is part of the matrix-media-repo container " +"image. Your Synapse database is called `synapse` by default, unless " +"you've changed it by modifying `matrix_synapse_database_database`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:125 +msgid "" +"This guide here is adapted from the [upstream documentation about the " +"import_synapse script](https://github.com/turt2live/matrix-media-repo" +"#importing-media-from-synapse)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:127 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:149 +msgid "" +"Run the following command on the server (after replacing " +"`postgres_connection_password` in it with the value found in your " +"`vars.yml` file):" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:139 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:161 +msgid "" +"Enter `1` for the Machine ID when prompted (you are not doing any " +"horizontal scaling) unless you know what you're doing." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:141 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:163 +msgid "" +"This should output a `msg=\"Import completed\"` when finished " +"successfully!" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:143 +msgid "Importing data from the Dendrite media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:145 +msgid "" +"If you're using the [Dendrite](configuring-playbook-dendrite.md) " +"homeserver instead of the default for this playbook (Synapse), follow " +"this importing guide here." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:147 +msgid "" +"To import the Dendrite media store, you're supposed to invoke the " +"`import_dendrite` tool which is part of the matrix-media-repo container " +"image. Your Dendrite database is called `dendrite_mediaapi` by default, " +"unless you've changed it by modifying " +"`matrix_dendrite_media_api_database`." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po new file mode 100644 index 000000000..480591f98 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po @@ -0,0 +1,219 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-matrix-registration.md:1 +msgid "Setting up matrix-registration (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:3 +msgid "" +"The playbook can install and configure [matrix-" +"registration](https://github.com/ZerataX/matrix-registration) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:5 +msgid "" +"**WARNING**: this is a poorly maintained and buggy project. It's better " +"to avoid using it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:7 +msgid "" +"**WARNING**: this is not related to [matrix-registration-bot" +"](configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:9 +msgid "" +"matrix-registration is a simple python application to have a token based " +"Matrix registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:11 +msgid "" +"Use matrix-registration to **create unique registration links**, which " +"people can use to register on your Matrix server. It allows you to **keep" +" your server's registration closed (private)**, but still allow certain " +"people (these having a special link) to register a user account." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:13 +msgid "**matrix-registration** provides 2 things:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:15 +msgid "" +"**an API for creating registration tokens** (unique registration links). " +"This API can be used via `curl` or via the playbook (see [Usage](#usage) " +"below)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:17 +msgid "" +"**a user registration page**, where people can use these registration " +"tokens. By default, exposed at `https://matrix.example.com/matrix-" +"registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:19 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:21 +msgid "" +"To enable matrix-registration, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:30 +msgid "Adjusting the matrix-registration URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:32 +msgid "" +"By default, this playbook installs the matrix-registration on the " +"`matrix.` subdomain, at the `/matrix-registration` path " +"(https://matrix.example.com/matrix-registration). This makes it easy to " +"install it, because it **doesn't require additional DNS records to be set" +" up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:34 +msgid "" +"By tweaking the `matrix_registration_hostname` and " +"`matrix_registration_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:36 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:46 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the matrix-registration domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:48 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:50 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:54 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:67 +msgid "" +"**matrix-registration** gets exposed at `https://matrix.example.com" +"/matrix-registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:69 +msgid "" +"It provides various [APIs](https://github.com/ZerataX/matrix-" +"registration/wiki/api) - for creating registration tokens, listing " +"tokens, disabling tokens, etc. To make use of all of its capabilities, " +"consider using `curl`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:71 +msgid "We make the most common APIs easy to use via the playbook (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:73 +msgid "Creating registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:75 +msgid "To **create a new user registration token (link)**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:83 +msgid "" +"The above command creates and returns a **one-time use** token, which " +"**expires** on the 31st of December 2021. Adjust the `one_time` and " +"`ex_date` variables as you see fit." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:85 +msgid "" +"Share the unique registration link (generated by the command above) with " +"users to let them register on your Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:87 +msgid "Listing registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:89 +msgid "To **list the existing user registration tokens**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:96 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags list-matrix-registration-tokens`" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po new file mode 100644 index 000000000..b8b8158f3 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po @@ -0,0 +1,260 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-mautrix-bridges.md:1 +msgid "Setting up a Generic Mautrix Bridge (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:3 +msgid "" +"The playbook can install and configure various " +"[mautrix](https://github.com/mautrix) bridges (twitter, facebook, " +"instagram, signal, hangouts, googlechat, etc.), as well as many other " +"(non-mautrix) bridges. This is a common guide for configuring mautrix " +"bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:5 +msgid "" +"You can see each bridge's features at in the `ROADMAP.md` file in its " +"corresponding [mautrix](https://github.com/mautrix) repository." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:16 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue. Each bridge may have additional requirements " +"besides `_enabled: true`. For example, the mautrix-telegram bridge (our " +"documentation page about it is [here](configuring-playbook-bridge-" +"mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and " +"`matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each" +" bridge's individual documentation page for details about enabling " +"bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:18 +msgid "" +"To **configure a user as an administrator for all bridges**, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:24 +msgid "" +"**Alternatively** (more verbose, but allows multiple admins to be " +"configured), you can do the same on a per-bridge basis with:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:33 +msgid "encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:35 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:37 +msgid "**for all bridges with encryption support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:44 +#: ../../../docs/configuring-playbook-mautrix-bridges.md:61 +msgid "**Alternatively**, for a specific bridge:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:51 +msgid "relay mode" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:53 +msgid "" +"Relay mode is off by default. If you would like to enable relay mode, add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:55 +msgid "**for all bridges with relay mode support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:70 +msgid "" +"You can only have one " +"`matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in " +"`vars.yml` per bridge, so if you need multiple pieces of configuration " +"there, just merge them like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:82 +msgid "Setting the bot's username" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:88 +msgid "Can be used to set the username for the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:90 +msgid "Discovering additional configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:92 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-SERVICENAME/defaults/main.yml` to find other things you would " +"like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:94 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:96 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:103 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:105 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:107 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:109 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:111 +msgid "Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:113 +msgid "" +"To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-" +"puppeting.html) enable the [Appservice Double Puppet](configuring-" +"playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:115 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) is configured and enabled " +"on the server for this playbook by adding" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:121 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:123 +msgid "Controlling the logging level" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:129 +msgid "" +"to `vars.yml` to control the logging level, where you may replace WARN " +"with one of the following to control the verbosity of the logs generated:" +" TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:131 +msgid "" +"If you have issues with a service, and are requesting support, the higher" +" levels of logging will generally be more helpful." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:133 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:135 +msgid "" +"To use the bridge, you need to start a chat with " +"`@SERVICENAMEbot:example.com` (where `example.com` is your base domain, " +"not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:137 +msgid "" +"Send `login` to the bridge bot to get started. You can learn more here " +"about authentication from the bridge's official documentation on " +"Authentication: " +"https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:139 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:141 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:143 +msgid "" +"For troubleshooting information with a specific bridge, please see the " +"playbook documentation about it (some other document in in `docs/`) and " +"the upstream ([mautrix](https://github.com/mautrix)) bridge documentation" +" for that specific bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:145 +msgid "" +"Reporting bridge bugs should happen upstream, in the corresponding " +"mautrix repository, not to us." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po new file mode 100644 index 000000000..02dafa0c1 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po @@ -0,0 +1,31 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-nginx.md:1 +msgid "Configure Nginx (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-nginx.md:3 +msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po new file mode 100644 index 000000000..82b3ac0b0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -0,0 +1,355 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-ntfy.md:1 +msgid "Setting up the ntfy push notifications server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:3 +msgid "" +"The playbook can install and configure the [ntfy](https://ntfy.sh/) push " +"notifications server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:5 +msgid "" +"Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables " +"self-hosted (Google-free) push notifications from Matrix (and other) " +"servers to UnifiedPush-compatible Matrix compatible client apps running " +"on Android and other devices." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:7 +msgid "" +"This role is intended to support UnifiedPush notifications for use with " +"the Matrix and Matrix-related services that this playbook installs. This " +"role is not intended to support all of ntfy's other features." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:9 +msgid "" +"**Note**: In contrast to push notifications using Google's FCM or Apple's" +" APNs, the use of UnifiedPush allows each end-user to choose the push " +"notification server that they prefer. As a consequence, deploying this " +"ntfy server does not by itself ensure any particular user or device or " +"client app will use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:13 +msgid "" +"To enable ntfy, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:27 +msgid "" +"For a more complete list of variables that you could override, see the " +"[`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting" +"/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:29 +msgid "" +"For a complete list of ntfy config options that you could put in " +"`ntfy_configuration_extension_yaml`, see the [ntfy config " +"documentation](https://ntfy.sh/docs/config/#config-options)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:31 +msgid "Adjusting the ntfy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:33 +msgid "" +"By default, this playbook installs ntfy on the `ntfy.` subdomain " +"(`ntfy.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:35 +msgid "" +"By tweaking the `ntfy_hostname` variable, you can easily make the service" +" available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:37 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:46 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the ntfy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:48 +msgid "" +"By default, you will need to create a CNAME record for `ntfy`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:52 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:59 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:61 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:65 +msgid "" +"To make use of your ntfy installation, on Android for example, you need " +"two things:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:67 +msgid "the `ntfy` app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:68 +msgid "a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:70 +msgid "" +"You need to install the `ntfy` app on each device on which you want to " +"receive push notifications through your ntfy server. The `ntfy` app will " +"provide UnifiedPush notifications to any number of UnifiedPush-compatible" +" messaging apps installed on the same device." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:72 +msgid "Setting up the `ntfy` Android app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:74 +msgid "" +"Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) " +"from F-droid or Google Play." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:75 +msgid "" +"In its Settings -> `General: Default server`, enter your ntfy server URL," +" such as `https://ntfy.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:76 +msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:78 +msgid "" +"That is all you need to do in the ntfy app. It has many other features, " +"but for our purposes you can ignore them. In particular you do not need " +"to follow any instructions about subscribing to a notification topic as " +"UnifiedPush will do that automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:80 +msgid "Setting up a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:82 +msgid "" +"Install any UnifiedPush-enabled Matrix app on that same device. The " +"Matrix app will learn from the `ntfy` app that you have configured " +"UnifiedPush on this device, and then it will tell your Matrix server to " +"use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:84 +msgid "Steps needed for specific Matrix apps:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:86 +msgid "FluffyChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:87 +msgid "Should auto-detect and use it. No manual settings." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:89 +msgid "SchildiChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:90 +msgid "" +"enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push " +"gateway`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:91 +msgid "" +"choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push " +"distributor`. *(For info, a more complex alternative to achieve the same " +"is: delete the relevant unifiedpush registration in `ntfy` app, force-" +"close SchildiChat, re-open it.)*" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:92 +msgid "" +"verify `Settings` -> `Notifications` -> `UnifiedPush: Notification " +"targets` as described below in the \"Troubleshooting\" section." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:94 +msgid "Element-android v1.4.26+:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:95 +msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:96 +msgid "" +"verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification " +"settings`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:98 +msgid "" +"If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", " +"then choose \"ntfy\"." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:100 +msgid "" +"If the Matrix app doesn't seem to pick it up, try restarting it and try " +"the Troubleshooting section below." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:102 +msgid "Web App" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:104 +msgid "" +"ntfy also has a web app to subscribe to and push to topics from the " +"browser. This may be helpful to further troubleshoot UnifiedPush problems" +" or to use ntfy for other purposes. The web app only runs in the browser " +"locally (after downloading the JavaScript)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:106 +msgid "" +"The web app is disabled in this playbook by default as the expectation is" +" that most users won't use it. You can either use the [official hosted " +"one](https://ntfy.sh/app) (it supports using other public reachable ntfy " +"instances) or host it yourself by setting `ntfy_web_root: \"app\"` and " +"re-running Ansible." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:108 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:110 +msgid "" +"First check that the Matrix client app you are using supports " +"UnifiedPush. There may well be different variants of the app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:112 +msgid "" +"Set the ntfy server's log level to 'DEBUG', as shown in the example " +"settings above, and watch the server's logs with `sudo journalctl -fu " +"matrix-ntfy`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:114 +msgid "" +"To check if UnifiedPush is correctly configured on the client device, " +"look at \"Settings -> Notifications -> Notification Targets\" in Element " +"Android or SchildiChat Android, or \"Settings -> Notifications -> " +"Devices\" in FluffyChat. There should be one entry for each Matrix client" +" app that has enabled push notifications, and when that client is using " +"UnifiedPush you should see a URL that begins with your ntfy server's URL." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:116 +msgid "" +"In the \"Notification Targets\" screen in Element Android or SchildiChat " +"Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and " +"both should begin with your ntfy server's URL. If \"push\\_key\" shows " +"your server but \"Url\" shows an external server such as " +"`up.schildi.chat` then push notifications will still work but are being " +"routed through that external server before they reach your ntfy server. " +"To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you" +" must enable the `Force custom push gateway` setting as described in the " +"\"Usage\" section above." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:118 +msgid "" +"If it is not working, useful tools are \"Settings -> Notifications -> Re-" +"register push distributor\" and \"Settings -> Notifications -> " +"Troubleshoot Notifications\" in SchildiChat Android (possibly also " +"Element Android). In particular the \"Endpoint/FCM\" step of that " +"troubleshooter should display your ntfy server's URL that it has " +"discovered from the ntfy client app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:120 +msgid "" +"The simple [UnifiedPush " +"troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-" +"Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be" +" used to manually test UnifiedPush registration and operation on an " +"Android device." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po new file mode 100644 index 000000000..a4c8b4f62 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po @@ -0,0 +1,292 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-own-webserver.md:1 +msgid "" +"Using your own webserver, instead of this playbook's Traefik reverse-" +"proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:3 +msgid "" +"By default, this playbook installs its own [Traefik](https://traefik.io/)" +" reverse-proxy server (in a Docker container) which listens on ports 80 " +"and 443. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:5 +msgid "Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:7 +msgid "" +"[Traefik](https://traefik.io/) is the default reverse-proxy for the " +"playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 " +"purposes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:9 +msgid "" +"serving public traffic and providing SSL-termination with certificates " +"obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting " +"SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:11 +msgid "" +"assists internal communication between addon services (briges, bots, " +"etc.) and the homeserver via an internal entrypoint (`matrix-internal-" +"matrix-client-api`)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:13 +msgid "There are 2 ways to use Traefik with this playbook, as described below." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:15 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:17 +msgid "" +"To have the playbook install and use Traefik, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:25 +msgid "Traefik will manage SSL certificates for all services seamlessly." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:27 +msgid "Traefik managed by you" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:53 +msgid "" +"In this mode all roles will still have Traefik labels attached. You will," +" however, need to configure your Traefik instance and its entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:55 +msgid "" +"By default, the playbook configured a `default` certificate resolver and " +"multiple entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:57 +msgid "You need to configure 4 entrypoints for your Traefik server:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:59 +msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:60 +msgid "" +"`web-secure` (TCP port `443`) - used for exposing the Matrix Client-" +"Server API and all other services" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:61 +msgid "" +"`matrix-federation` (TCP port `8448`) - used for exposing the Matrix " +"Federation API" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:62 +msgid "" +"`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally " +"for addon services (bridges, bots) to communicate with the homserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:64 +msgid "" +"Below is some configuration for running Traefik yourself, although we " +"recommend using [Traefik managed by the playbook](#traefik-managed-by-" +"the-playbook)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:66 +msgid "" +"Note that this configuration on its own does **not** redirect traffic on " +"port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing " +"this in Traefik, it can be added to Traefik in a [file " +"provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:86 +msgid "" +"You can use the following `docker-compose.yml` as example to launch " +"Traefik." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:122 +msgid "Another webserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:124 +msgid "If you don't wish to use Traefik, you can also use your own webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:126 +msgid "Doing this is possible, but requires manual work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:128 +msgid "There are 2 ways to go about it:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:130 +msgid "" +"(recommended) [Fronting the integrated reverse-proxy webserver with " +"another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-" +"with-another-reverse-proxy) - using the playbook-managed reverse-proxy " +"(Traefik), but disabling SSL termination for it, exposing this reverse-" +"proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding " +"traffic from your own webserver to those few ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:132 +msgid "" +"(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-" +"reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed " +"reverse-proxy (Traefik), exposing services one by one using " +"`_host_bind_port` variables and forwarding traffic from your own " +"webserver to those ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:134 +msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:136 +msgid "" +"This method is about leaving the integrated reverse-proxy webserver be, " +"but making it not get in the way (using up important ports, trying to " +"retrieve SSL certificates, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:138 +msgid "" +"If you wish to use another webserver, the integrated reverse-proxy " +"webserver usually gets in the way because it attempts to fetch SSL " +"certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is" +" enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:140 +msgid "" +"You can disable such behavior and make the integrated reverse-proxy " +"webserver only serve traffic locally on the host itself (or over a local " +"network)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:142 +msgid "" +"This is the recommended way for using another reverse-proxy, because the " +"integrated one would act as a black box and wire all Matrix services " +"correctly. You would then only need to reverse-proxy a few individual " +"domains and ports over to it." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:144 +msgid "" +"To front Traefik with another reverse-proxy, you would need some " +"configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:194 +msgid "" +"Such a configuration would expose all services on a local port `81` and " +"Matrix Federation on a local port `8449`. Your reverse-proxy " +"configuration needs to send traffic to these ports. [`examples/reverse-" +"proxies`](../examples/reverse-proxies/) contains examples for various " +"webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy " +"Manager." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:196 +msgid "" +"It's important that these webservers proxy-pass requests to the correct " +"`ip:port` and also set the `Host` HTTP header appropriately. If you don't" +" pass the `Host` header correctly, Traefik will return a `404 - not " +"found` error." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:198 +msgid "To put it another way:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:199 +msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:200 +msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:202 +msgid "Using no reverse-proxy on the Matrix side at all" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:204 +msgid "" +"Instead of [Fronting the integrated reverse-proxy webserver with another " +"reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-" +"another-reverse-proxy), you can also go another way -- completely " +"disabling the playbook-managed Traefik reverse-proxy. You would then need" +" to reverse-proxy from your own webserver directly to each individual " +"Matrix service." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:206 +msgid "" +"This is more difficult, as you would need to handle the configuration for" +" each service manually. Enabling additional services would come with " +"extra manual work you need to do." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:208 +msgid "" +"Also, the Traefik reverse-proxy, besides fronting everything is also " +"serving a 2nd purpose of allowing addons services to communicate with the" +" Matrix homeserver thanks to its `matrix-internal-matrix-client-api` " +"entrypoint (read more about it above). Disabling Traefik completely means" +" the playbook would wire services to directly talk to the homeserver. " +"This can work for basic setups, but not for more complex setups involving" +" [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), " +"[matrix-corporal](./configuring-playbook-matrix-corporal.md) or other " +"such services that need to \"steal routes\" from the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:210 +msgid "" +"If your webserver is on the same machine, ensure your web server user " +"(something like `http`, `apache`, `www-data`, `nginx`) is part of the " +"`matrix` group. You should run something like this: `usermod -a -G matrix" +" nginx`. This allows your webserver user to access files owned by the " +"`matrix` group, so that it can serve static files from `/matrix/static-" +"files`." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po new file mode 100644 index 000000000..770043c21 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -0,0 +1,93 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-pantalaimon.md:1 +msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:3 +msgid "" +"The playbook can install and configure the " +"[pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy" +" daemon for you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-" +"org/pantalaimon) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:7 +msgid "" +"This role exposes Pantalaimon's API only within the container network, so" +" bots and clients installed on the same machine can use it. In particular" +" the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir" +"](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can " +"use it." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:17 +msgid "" +"The default configuration should suffice. For advanced configuration, you" +" can override the variables documented in the role's " +"[defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:21 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po new file mode 100644 index 000000000..30b6306eb --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po @@ -0,0 +1,183 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-postgres-backup.md:1 +msgid "Setting up postgres backup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:3 +msgid "" +"The playbook can install and configure [docker-postgres-backup-" +"local](https://github.com/prodrigestivill/docker-postgres-backup-local) " +"for you via the [ansible-role-postgres-backup](https://github.com/mother-" +"of-all-self-hosting/ansible-role-postgres-backup) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:5 +msgid "" +"For a more complete backup solution (one that includes not only Postgres," +" but also other configuration/data files), you may wish to look into " +"[BorgBackup](configuring-playbook-backup-borg.md) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:9 +msgid "" +"To enable Postgres backup, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:15 +msgid "" +"Refer to the table below for additional configuration variables and their" +" default values." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Default value" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`false`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "" +"Set to true to use [docker-postgres-backup-" +"local](https://github.com/prodrigestivill/docker-postgres-backup-local) " +"to create automatic database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_schedule`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`'@daily'`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Cron-schedule specifying the interval between postgres backups." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_days`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`7`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of daily backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_weeks`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`4`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of weekly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_months`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`12`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of monthly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_base_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ postgres_backup_base_path }}/data\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Storage path for postgres-backup database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po new file mode 100644 index 000000000..0d4835959 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po @@ -0,0 +1,513 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-prometheus-grafana.md:1 +msgid "" +"Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server " +"(optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:3 +msgid "" +"The playbook can install [Grafana](https://grafana.com/) with " +"[Prometheus](https://prometheus.io/) and configure performance metrics of" +" your homeserver with graphs for you." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:7 +msgid "" +"To enable Grafana and/or Prometheus, add the following configuration to " +"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:33 +msgid "" +"The retention policy of Prometheus metrics is [15 days by " +"default](https://prometheus.io/docs/prometheus/latest/storage" +"/#operational-aspects). Older data gets deleted automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:35 +msgid "Adjusting the Grafana URL" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:37 +msgid "" +"By default, this playbook installs Grafana web user-interface on the " +"`stats.` subdomain (`stats.example.com`) and requires you to [adjust your" +" DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:39 +msgid "" +"By tweaking the `grafana_hostname` variable, you can easily make the " +"service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:41 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:48 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:50 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the Grafana domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:52 +msgid "" +"By default, you will need to create a CNAME record for `stats`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:54 +msgid "" +"**Note**: It is possible to install Prometheus without installing " +"Grafana. This case it is not required to create the CNAME record." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:56 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:58 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:65 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:67 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:69 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Prometheus](https://prometheus.io) is a time series database. It holds " +"all the data we're going to talk about." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an " +"addon of sorts to Prometheus that collects generic system information " +"such as CPU, memory, filesystem, and even system temperatures" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an " +"addon of sorts to expose Postgres database metrics to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an " +"addon of sorts to expose NGINX logs to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Grafana](https://grafana.com/) is the visual component. It shows (on the" +" `stats.example.com` subdomain) the dashboards with the graphs that we're" +" interested in" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_anonymous_access`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"By default you need to log in to see graphs. If you want to publicly " +"share your graphs (e.g. when asking for help in " +"[`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org))" +" you'll want to enable this option." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"By default Grafana creates a user with `admin` as the username and " +"password. If you feel this is insecure and you want to change it " +"beforehand, you can do that here" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 +msgid "" +"Metrics and resulting graphs can contain a lot of information. This " +"includes system specs but also usage patterns. This applies especially to" +" small personal/family scale homeservers. Someone might be able to figure" +" out when you wake up and go to sleep by looking at the graphs over time." +" Think about this before enabling anonymous access. And you should really" +" not forget to change your Grafana password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:85 +msgid "" +"Most of our docker containers run with limited system access, but the " +"`prometheus-node-exporter` has access to the host network stack and " +"(readonly) root filesystem. This is required to report on them. If you " +"don't like that, you can set `prometheus_node_exporter_enabled: false` " +"(which is actually the default). You will still get Synapse metrics with " +"this container disabled. Both of the dashboards will always be enabled, " +"so you can still look at historical data after disabling either source." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:87 +msgid "Collecting metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 +msgid "" +"**If the integrated Prometheus server is enabled** (`prometheus_enabled: " +"true`), metrics are collected by it from each service via communication " +"that happens over the container network. Each service does not need to " +"expose its metrics \"publicly\"." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 +msgid "" +"When you'd like **to collect metrics from an external Prometheus " +"server**, you need to expose service metrics outside of the container " +"network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 +msgid "" +"The playbook provides a single endpoint " +"(`https://matrix.example.com/metrics/*`), under which various services " +"may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics" +"/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on" +" this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To " +"protect access using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)," +" see `matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users` below." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 +msgid "" +"When using `matrix_metrics_exposure_enabled`, you don't need to expose " +"metrics for individual services one by one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:97 +msgid "The following variables may be of interest:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to **enable metrics exposure for all services** on " +"`https://matrix.example.com/metrics/*`. If you think this is too much, " +"refer to the helpful (but nonexhaustive) list of individual " +"`matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below " +"for exposing metrics on a per-service basis." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_http_basic_auth_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to protect all `https://matrix.example.com/metrics/*` " +"endpoints with [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" +" (see the other variables below for supplying the actual credentials). " +"When enabled, all endpoints beneath `/metrics` will be protected with the" +" same credentials" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_http_basic_auth_users`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to the Basic Authentication credentials (raw `htpasswd` file " +"content) used to protect `/metrics/*`. This htpasswd-file needs to be " +"generated with the `htpasswd` tool and can include multiple " +"username/password pairs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_synapse_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make Synapse expose metrics (locally, on the " +"container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_synapse_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose Synapse's metrics on " +"`https://matrix.example.com/metrics/synapse/main-process` and " +"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below" +"](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if" +" you're running a Synapse worker setup (`matrix_synapse_workers_enabled: " +"true`). To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the node (general system stats) exporter " +"(locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the node (general system stats) metrics on " +"`https://matrix.example.com/metrics/node-exporter`. To password-protect " +"the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the [Postgres exporter](configuring-" +"playbook-prometheus-postgres.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Postgres exporter](configuring-" +"playbook-prometheus-postgres.md) metrics on " +"`https://matrix.example.com/metrics/postgres-exporter`. To password-" +"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " +"above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the [NGINX Log exporter](configuring-" +"playbook-prometheus-nginxlog.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-" +"sync-proxy.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Sliding Sync](configuring-playbook-" +"sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics" +"/sliding-sync`. To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make [Hookshot](configuring-playbook-bridge-" +"hookshot.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-" +"hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To" +" password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_SERVICE_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Various other services/roles may provide similar `_metrics_enabled` and " +"`_metrics_proxying_enabled` variables for exposing their metrics. Refer " +"to each role for details. To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above or " +"`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users`" +" variables provided by each role." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_media_repo_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make media-repo expose metrics (locally, on the " +"container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:118 +msgid "Collecting Synapse worker metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:120 +msgid "" +"If you are using workers (`matrix_synapse_workers_enabled: true`) and " +"have enabled `matrix_synapse_metrics_proxying_enabled` as described " +"above, the playbook will also automatically expose all Synapse worker " +"threads' metrics to " +"`https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` " +"corresponds to the worker `id` as exemplified in " +"`matrix_synapse_workers_enabled_list`." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:122 +msgid "" +"The playbook also generates an exemplary config file " +"(`/matrix/synapse/external_prometheus.yml.template`) with all the correct" +" paths which you can copy to your Prometheus server and adapt to your " +"needs. Make sure to edit the specified `password_file` path and contents " +"and path to your `synapse-v2.rules`. It will look a bit like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:152 +msgid "" +"[Enabling synapse-usage-exporter for Synapse usage statistics" +"](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:153 +msgid "" +"[Understanding Synapse Performance Issues Through Grafana Graphs](https" +"://element-" +"hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html)" +" at the Synapse Github Wiki" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:154 +msgid "" +"[The Prometheus scraping rules](https://github.com/element-" +"hq/synapse/tree/master/contrib/prometheus) (we use v2)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:155 +msgid "" +"[The Synapse Grafana dashboard](https://github.com/element-" +"hq/synapse/tree/master/contrib/grafana)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:156 +msgid "" +"[The Node Exporter dashboard](https://github.com/rfrail3/grafana-" +"dashboards) (for generic non-synapse performance graphs)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po new file mode 100644 index 000000000..9e5ce7b60 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po @@ -0,0 +1,177 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-prometheus-nginxlog.md:1 +msgid "Enabling metrics and graphs for NginX logs (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3 +msgid "" +"It can be useful to have some (visual) insight into " +"[nginx](https://nginx.org/) logs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5 +msgid "" +"This adds [prometheus-nginxlog-exporter](https://github.com/martin-" +"helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7 +msgid "" +"It will collect access logs from various nginx reverse-proxies which may " +"be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if " +"Synapse workers are enabled) and will make them available at a " +"Prometheus-compatible `/metrics` endpoint." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9 +msgid "" +"**Note**: nginx is only used internally by this Ansible playbook. With " +"Traefik being our default reverse-proxy, collecting nginx metrics is less" +" relevant." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11 +msgid "" +"To make use of this, you need to install [Prometheus](./configuring-" +"playbook-prometheus-grafana.md) either via the playbook or externally. " +"When using an external Prometheus, configuration adjustments are " +"necessary - see [Save metrics on an external Prometheus server](#save-" +"metrics-on-an-external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13 +msgid "" +"If your setup includes [Grafana](./configuring-playbook-prometheus-" +"grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:36 +msgid "Docker Image Compatibility" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38 +msgid "" +"At the moment of writing only images for `amd64` and `arm64` " +"architectures are available. The playbook currently does not support " +"[self-building](./self-building.md) a container image on other " +"architectures. You can however use a custom-build image by setting:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47 +msgid "" +"Metrics and resulting graphs can contain a lot of information. NginX logs" +" contain information like IP address, URLs, UserAgents and more. This " +"information can reveal usage patterns and could be considered Personally " +"Identifiable Information (PII). Think about this before enabling " +"(anonymous) access. Please make sure you change the default Grafana " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49 +msgid "Save metrics on an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51 +msgid "" +"The playbook will automatically integrate the metrics into the " +"[Prometheus](./configuring-playbook-prometheus-grafana.md) server " +"provided with this playbook (if enabled). In such cases, the metrics " +"endpoint is not exposed publicly - it's only available on the container " +"network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53 +msgid "" +"When using an external Prometheus server, you'll need to expose metrics " +"publicly. See [Collecting metrics to an external Prometheus server" +"](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" +"external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55 +msgid "" +"You can either use " +"`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to " +"expose just this one service, or `matrix_metrics_exposure_enabled: true` " +"to expose all services." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57 +msgid "" +"Whichever way you go with, this service will expose its metrics endpoint " +"**without password-protection** at " +"`https://matrix.example.com/metrics/nginxlog` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59 +msgid "" +"For password-protection, use " +"(`matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users`) or " +"(`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled`" +" and " +"`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po new file mode 100644 index 000000000..ecf92c21c --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po @@ -0,0 +1,140 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-prometheus-postgres.md:1 +msgid "Enabling metrics and graphs for Postgres (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:3 +msgid "" +"Expanding on the metrics exposed by the [synapse exporter and the node " +"exporter](configuring-playbook-prometheus-grafana.md), the playbook " +"enables the [postgres exporter](https://github.com/prometheus-" +"community/postgres_exporter) that exposes more detailed information about" +" what's happening on your postgres database." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:7 +msgid "" +"To enable the postgres exporter, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:13 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:15 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:22 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:24 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:26 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"Enable the postgres prometheus exporter. This sets up the docker " +"container, connects it to the database and adds a 'job' to the prometheus" +" config which tells prometheus about this new exporter. The default is " +"'false'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_database_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"The 'username' for the user that the exporter uses to connect to the " +"database. The default is 'matrix_prometheus_postgres_exporter'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_database_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"The 'password' for the user that the exporter uses to connect to the " +"database. By default, this is auto-generated by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"If set to `true`, exposes the Postgres exporter metrics on " +"`https://matrix.example.com/metrics/postgres-exporter` for usage with an " +"[external Prometheus server](configuring-playbook-prometheus-grafana.md" +"#collecting-metrics-to-an-external-prometheus-server). To password-" +"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " +"on that other documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:35 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:37 +msgid "" +"[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) " +"(generic postgres dashboard)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po new file mode 100644 index 000000000..799ecb51f --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -0,0 +1,146 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-rageshake.md:1 +msgid "Setting up the rageshake bug report server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:3 +msgid "" +"The playbook can install and configure the [rageshake](https://github.com" +"/matrix-org/rageshake) bug report server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:5 +msgid "" +"This is useful if you're developing your own applications and would like " +"to collect bug reports for them." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:9 +msgid "" +"To enable rageshake, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:15 +msgid "" +"rageshake has various options which don't have dedicated Ansible " +"variables. You can see the full list of options in the " +"[`rageshake.sample.yaml` file](https://github.com/matrix-" +"org/rageshake/blob/master/rageshake.sample.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:17 +msgid "" +"To set these, you can make use of the " +"`matrix_rageshake_configuration_extension_yaml` variable like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:27 +msgid "Adjusting the rageshake URL" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:29 +msgid "" +"By default, this playbook installs rageshake on the `rageshake.` " +"subdomain (`rageshake.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:31 +msgid "" +"By tweaking the `matrix_rageshake_hostname` and " +"`matrix_rageshake_path_prefix` variables, you can easily make the service" +" available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:33 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:46 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the rageshake domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:48 +msgid "" +"By default, you will need to create a CNAME record for `rageshake`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:50 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:54 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:67 +msgid "" +"Refer to the [rageshake documentation](https://github.com/matrix-" +"org/rageshake) for available APIs, etc." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po new file mode 100644 index 000000000..64f262b10 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po @@ -0,0 +1,86 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-playbook-rest-auth.md:1 +msgid "" +"Setting up the REST authentication password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:3 +msgid "" +"The playbook can install and configure [matrix-synapse-rest-" +"auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:19 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:21 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po new file mode 100644 index 000000000..20d1e3915 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po @@ -0,0 +1,130 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-riot-web.md:1 +msgid "Configuring Riot-web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:3 +msgid "" +"By default, this playbook **used to install** the [Riot-" +"web](https://github.com/element-hq/riot-web) Matrix client web " +"application." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:5 +msgid "" +"Riot has since been [renamed to Element](https://element.io/blog/welcome-" +"to-element/)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:7 +msgid "" +"to learn more about Element Web and its configuration, see our dedicated " +"[Configuring Element Web](configuring-playbook-client-element-web.md) " +"documentation page" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:8 +msgid "" +"to learn how to migrate from Riot to Element Web, see [Migrating to " +"Element Web](#migrating-to-element-web) below" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:10 +msgid "Migrating to Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:12 +msgid "Migrating your custom settings" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:14 +msgid "" +"If you have custom `matrix_riot_web_` variables in your " +"`inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to " +"rename them (`matrix_riot_web_` -> `matrix_client_element_`)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:16 +msgid "" +"Some other playbook variables (but not all) with `riot` in their name are" +" also renamed. The playbook checks and warns if you are using the old " +"name for some commonly used ones." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:18 +msgid "Domain migration" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:20 +msgid "" +"We used to set up Riot at the `riot.example.com` domain. The playbook now" +" sets up Element Web at `element.example.com` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:22 +msgid "There are a few options for handling this:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:24 +msgid "" +"(**avoiding changes** - using the old `riot.example.com` domain and " +"avoiding DNS changes) -- to keep using `riot.example.com` instead of " +"`element.example.com`, override the domain at which the playbook serves " +"Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:26 +msgid "" +"(**embracing changes** - using only `element.example.com`) - set up the " +"`element.example.com` DNS record (see [Configuring DNS](configuring-" +"dns.md)). You can drop the `riot.example.com` in this case." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:28 +msgid "Re-running the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:30 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:37 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:39 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po new file mode 100644 index 000000000..343adbf66 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po @@ -0,0 +1,249 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-s3-goofys.md:1 +msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:3 +msgid "" +"If you'd like to store Synapse's content repository (`media_store`) files" +" on Amazon S3 (or other S3-compatible service), you can let this playbook" +" configure [Goofys](https://github.com/kahing/goofys) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:5 +msgid "" +"Another (and better performing) way to use S3 storage with Synapse is " +"[synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-" +"provider.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:7 +msgid "" +"Using a Goofys-backed media store works, but performance may not be " +"ideal. If possible, try to use a region which is close to your Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:9 +msgid "" +"If you'd like to move your locally-stored media store data to Amazon S3 " +"(or another S3-compatible object store), we also provide some migration " +"instructions below." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:13 +msgid "" +"After [creating the S3 bucket and configuring it](configuring-" +"playbook-s3.md#bucket-creation-and-security-configuration), add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:23 +msgid "" +"You can use any S3-compatible object store by **additionally** " +"configuring these variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:30 +msgid "" +"If you have local media store files and wish to migrate to Backblaze B2 " +"subsequently, follow our [migration guide to Backblaze B2](#migrating-to-" +"backblaze-b2) below instead of applying this configuration as-is." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:32 +msgid "Migrating from local filesystem storage to S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:34 +msgid "" +"It's a good idea to [make a complete server backup](faq.md#how-do-i-back-" +"up-the-data-on-my-server) before migrating your local media store to an " +"S3-backed one." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:36 +msgid "" +"After making the backup, follow one of the guides below for a migration " +"path from a locally-stored media store to one stored on S3-compatible " +"storage:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:38 +msgid "" +"[Migrating to any S3-compatible storage (universal, but likely slow" +")](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:39 +msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:41 +msgid "Migrating to any S3-compatible storage (universal, but likely slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:43 +msgid "Proceed with the steps below without stopping Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:45 +msgid "" +"Start by adding the base S3 configuration in your `vars.yml` file (seen " +"above, may be different depending on the S3 provider of your choice)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:47 +msgid "" +"In addition to the base configuration you see above, add this to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:53 +msgid "" +"This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3" +"-media-store` without hooking it to your homeserver yet. Your homeserver " +"will still continue using your local filesystem for its media store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:55 +msgid "" +"Run the playbook to apply the changes: `ansible-playbook -i " +"inventory/hosts setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:57 +msgid "" +"Do an **initial sync of your files** by running this **on the server** " +"(it may take a very long time):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:63 +msgid "You may need to install `rsync` manually." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:65 +#: ../../../docs/configuring-playbook-s3-goofys.md:106 +msgid "" +"Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:67 +msgid "" +"Start the S3 service by running this **on the server**: `systemctl start " +"matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:69 +msgid "Sync the files again by re-running the `rsync` command you see in step #5" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:71 +msgid "" +"Stop the S3 service by running this **on the server**: `systemctl stop " +"matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:73 +#: ../../../docs/configuring-playbook-s3-goofys.md:114 +msgid "" +"Get the old media store out of the way by running this command on the " +"server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:79 +msgid "" +"Remove the `matrix_s3_media_store_path` configuration from your " +"`vars.yml` file (undoing step #3 above)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:81 +#: ../../../docs/configuring-playbook-s3-goofys.md:122 +msgid "" +"Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags" +"=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:83 +#: ../../../docs/configuring-playbook-s3-goofys.md:124 +msgid "" +"You're done! Verify that loading existing (old) media files works and " +"that you can upload new ones." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:85 +#: ../../../docs/configuring-playbook-s3-goofys.md:126 +msgid "" +"When confident that it all works, get rid of the local media store " +"directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:87 +msgid "Migrating to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:89 +msgid "" +"While all Matrix services are running, run the following command on the " +"server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:91 +msgid "(you need to adjust the 3 `--env` line below with your own data)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:104 +msgid "This is some initial file sync, which may take a very long time." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:108 +msgid "Run the command from step #1 again." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:110 +msgid "" +"Doing this will sync any new files that may have been created locally in " +"the meantime." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:112 +msgid "" +"Now that Matrix services aren't running, we're sure to get Backblaze B2 " +"and your local media store fully in sync." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:120 +msgid "" +"Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) " +"in your `vars.yml` file" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po new file mode 100644 index 000000000..561daed38 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -0,0 +1,315 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-s3.md:1 +msgid "" +"Storing Synapse media files on Amazon S3 or another compatible Object " +"Storage (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:3 +msgid "" +"By default, this playbook configures your server to store Synapse's " +"content repository (`media_store`) files on the local filesystem. If " +"that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:5 +msgid "" +"As an alternative to storing media files on the local filesystem, you can" +" store them on [Amazon S3](https://aws.amazon.com/s3/) or another " +"S3-compatible object store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:7 +msgid "" +"You can do this either by sticking to Synapse's media repository and " +"making that use S3 (read below for this method), or by switching to an " +"external media storage implementation like [matrix-media-repo" +"](configuring-playbook-matrix-media-repo.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:9 +msgid "" +"First, [choose an Object Storage provider](#choosing-an-object-storage-" +"provider)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:11 +msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:13 +msgid "" +"Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys" +"](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider" +"](configuring-playbook-synapse-s3-storage-provider.md), or use s3 " +"datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-" +"media-repo/configuration/s3-datastore.html))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:15 +msgid "Choosing an Object Storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:17 +msgid "" +"You can create [Amazon S3](https://aws.amazon.com/s3/) or another " +"S3-compatible object storage like [Backblaze " +"B2](https://www.backblaze.com/b2/cloud-storage.html), " +"[Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean " +"Spaces](https://www.digitalocean.com/products/spaces), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:19 +msgid "" +"Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges" +" for storing too little data." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:21 +msgid "" +"All these providers have different prices, with Storj appearing to be the" +" cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress " +"fee is $0.007 per GB). Backblaze egress is free, but for only certain " +"users for up to 3x the amount of data stored. Beyond that you will pay " +"$0.01/GB of egress." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:23 +msgid "" +"Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which" +" becomes expensive if you need to store less data than that. Likewise, " +"Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of " +"2022-10)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:25 +msgid "Here are some of the important aspects of choosing the right provider:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:27 +msgid "" +"if a provider is a company you like and trust (or dislike less than the " +"others)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:28 +msgid "if a provider implements end-to-end encryption of your data" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:29 +msgid "" +"if a provider has a data region close to your Matrix server (if it's " +"farther away, high latency may cause slowdowns)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:30 +msgid "" +"if a provider's infrastructure such as data center is centralized or " +"distributed" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:31 +msgid "" +"if a provider's price model is transparent (whether it includes hidden " +"costs like minimum charge, minimum storage term, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:32 +msgid "" +"if a provider has free or cheap egress fee (in case you need to get the " +"data out often, for some reason) - likely not too important for the " +"common use-case" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:34 +msgid "Bucket creation and Security Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:36 +msgid "" +"Now that you've [chosen an Object Storage provider](#choosing-an-object-" +"storage-provider), you need to create a storage bucket." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:38 +msgid "" +"How you do this varies from provider to provider, with Amazon S3 being " +"the most complicated due to its vast number of services and complicated " +"security policies." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:40 +msgid "" +"Below, we provider some guides for common providers. If you don't see " +"yours, look at the others for inspiration or read some guides online " +"about how to create a bucket. Feel free to contribute to this " +"documentation with an update!" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:42 +msgid "Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:44 +msgid "" +"You'll need an Amazon S3 bucket and some IAM user credentials (access key" +" + secret key) with full write access to the bucket. Example IAM security" +" policy:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:65 +msgid "" +"**Note**: This policy needs to be attached to an IAM user created from " +"the **Security Credentials** menu. This is not a **Bucket Policy**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:67 +msgid "Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:69 +msgid "" +"To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) " +"you first need to sign up." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:71 +msgid "" +"You [can't easily change which region (US, Europe) your Backblaze account" +" stores files " +"in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/)," +" so make sure to carefully choose the region when signing up (hint: it's " +"a hard to see dropdown below the username/password fields in the signup " +"form)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:73 +msgid "After logging in to Backblaze:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:75 +msgid "" +"create a new **private** bucket through its user interface (you can call " +"it something like `matrix-example-media-store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:76 +msgid "" +"note the **Endpoint** for your bucket (something like `s3.us-" +"west-002.backblazeb2.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:77 +msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:78 +msgid "" +"go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the " +"**Add a New Application Key** to create a new one" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:79 +msgid "" +"restrict it to the previously created bucket (e.g. `matrix-example-media-" +"store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:80 +msgid "give it *Read & Write* access" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:82 +msgid "" +"The `keyID` value is your **Access Key** and `applicationKey` is your " +"**Secret Key**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:84 +msgid "" +"For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3" +"-synapse-storage-provider](configuring-playbook-synapse-s3-storage-" +"provider.md) you will need:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:86 +msgid "" +"**Endpoint URL** - this is the **Endpoint** value you saw above, but " +"prefixed with `https://`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:88 +msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:90 +msgid "" +"**Storage Class** - use `STANDARD`. Backblaze B2 does not have different " +"storage classes, so it doesn't make sense to use any other value." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:92 +msgid "Other providers" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:94 +msgid "" +"For other S3-compatible providers, you may not need to configure security" +" policies, etc. (just like for [Backblaze B2](#backblaze-b2))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:96 +msgid "" +"You most likely just need to create an S3 bucket and get some credentials" +" (access key and secret key) for accessing the bucket in a read/write " +"manner." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:98 +msgid "Setting up" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:100 +msgid "" +"To set up Synapse to store files in S3, follow the instructions for the " +"method of your choice:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:102 +msgid "" +"using [synapse-s3-storage-provider](configuring-playbook-synapse-s3" +"-storage-provider.md) (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:103 +msgid "" +"using [Goofys to mount the S3 store to the local filesystem](configuring-" +"playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:104 +msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po new file mode 100644 index 000000000..06e5c3081 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-shared-secret-auth.md:1 +msgid "" +"Setting up the Shared Secret Auth password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:3 +msgid "" +"The playbook can install and configure [matrix-synapse-shared-secret-" +"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:18 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:20 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:35 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:37 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po new file mode 100644 index 000000000..dff86843c --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po @@ -0,0 +1,175 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-sliding-sync-proxy.md:1 +msgid "Setting up the Sliding Sync proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 +msgid "" +"**Note**: The sliding-sync proxy is **not required** anymore as it's been" +" replaced with a different method (called Simplified Sliding Sync) which " +"is integrated into newer homeservers by default (**Conduit** homeserver " +"from version `0.6.0` or **Synapse** from version `1.114`). This component" +" and documentation remain here for historical purposes, but **installing " +"this old sliding-sync proxy is generally not recommended anymore**." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 +msgid "" +"The playbook can install and configure [sliding-sync](https://github.com" +"/matrix-org/sliding-sync) proxy for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 +msgid "" +"Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-" +"org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and " +"a prerequisite for running Element X clients ([Element X " +"iOS](https://github.com/element-hq/element-x-ios) and [Element X " +"Android](https://github.com/element-hq/element-x-android)). See the " +"project's [documentation](https://github.com/matrix-org/sliding-sync) to " +"learn more." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 +msgid "" +"To enable Sliding Sync proxy, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 +msgid "Adjusting the Sliding Sync proxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19 +msgid "" +"By default, this playbook installs the Sliding Sync proxy on the " +"`matrix.` subdomain, at the `/sliding-sync` path " +"(https://matrix.example.com/sliding-sync). This makes it easy to install " +"it, because it **doesn't require additional DNS records to be set up**. " +"If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:21 +msgid "" +"By tweaking the `matrix_sliding_sync_hostname` and " +"`matrix_sliding_sync_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:48 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:52 +msgid "External databases" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54 +msgid "" +"Please note that, if your setup utilizes an external database, you must " +"also establish configuration for the sliding sync proxy. Alter the " +"defaults below to suit your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66 +msgid "" +"You **don't need to do anything special** to make use of the Sliding Sync" +" proxy. Simply open your client which supports Sliding Sync (like Element" +" X) and log in." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68 +msgid "" +"When the Sliding Sync proxy is [installed](#installing), your `/.well-" +"known/matrix/client` file is also updated. A new " +"`org.matrix.msc3575.proxy` section and `url` property are added there and" +" made to point to your Sliding Sync proxy's base URL (e.g. " +"`https://matrix.example.com/sliding-sync`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70 +msgid "" +"This allows clients which support Sliding Sync to detect the Sliding Sync" +" proxy's URL and make use of it." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po new file mode 100644 index 000000000..9b10fefa2 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po @@ -0,0 +1,174 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-ssl-certificates.md:1 +msgid "Adjusting SSL certificate retrieval (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:3 +msgid "" +"By default, this playbook retrieves and auto-renews free SSL certificates" +" from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs " +"(e.g. `matrix.example.com` and others)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:5 +msgid "" +"This guide is about using the integrated Traefik server and doesn't apply" +" if you're using [your own webserver](configuring-playbook-own-" +"webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:7 +msgid "Using staging Let's Encrypt certificates instead of real ones" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:9 +msgid "" +"For testing purposes, you may wish to use staging certificates provide by" +" Let's Encrypt." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:11 +#: ../../../docs/configuring-playbook-ssl-certificates.md:21 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:17 +msgid "Disabling SSL termination" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:19 +msgid "" +"For testing or other purposes, you may wish to install services without " +"SSL termination and have services exposed to `http://` instead of " +"`https://`." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:27 +msgid "Using self-signed SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:29 +msgid "" +"If you'd like to use your own SSL certificates, instead of the default " +"(SSL certificates obtained automatically via " +"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" +" from [Let's Encrypt](https://letsencrypt.org/)):" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:31 +msgid "generate your self-signed certificate files" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:32 +msgid "" +"follow the [Using your own SSL certificates](#using-your-own-ssl-" +"certificates) documentation below" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:34 +msgid "Using your own SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:36 +msgid "To use your own SSL certificates with Traefik, you need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:38 +msgid "" +"disable " +"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" +" / [Let's Encrypt](https://letsencrypt.org/) support" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:39 +msgid "" +"put a custom Traefik configuration file on the server, with the help of " +"this Ansible playbook (via the [`aux` role](https://github.com/mother-of-" +"all-self-hosting/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:40 +msgid "" +"register your custom configuration file with Traefik, by adding an extra " +"provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:41 +msgid "" +"put the SSL files on the server, with the help of this Ansible playbook " +"(via the [`aux` role](https://github.com/mother-of-all-self-hosting" +"/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:89 +msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:91 +msgid "" +"You can configure Traefik to use the [DNS-01 challenge " +"type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for" +" Let's Encrypt. This is less commonly used than the default [HTTP-01 " +"challenge type](https://letsencrypt.org/docs/challenge-" +"types/#http-01-challenge), but it can be helpful to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:93 +msgid "hide your public IP from Let's Encrypt logs" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:94 +msgid "" +"allow you to obtain SSL certificates for servers which are not accessible" +" (via HTTP) from the public internet (and for which the HTTP-01 challenge" +" would fail)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:96 +msgid "" +"This is an example for how to edit the `vars.yml` file if you're using " +"Cloudflare:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:111 +msgid "" +"Make sure to change the value of \"provider\" to your particular DNS " +"solution, and provide the appropriate environment variables. The full " +"list of supported providers is available " +"[here](https://doc.traefik.io/traefik/https/acme/#providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:113 +msgid "" +"This example assumes you're using Cloudflare to manage your DNS zone. " +"Note that it requires the use of two tokens: one for reading all zones " +"(`CF_ZONE_API_TOKEN`) and another that must be able to edit the " +"particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's " +"recommended that you create two fine-grained tokens for this purpose, but" +" you might choose to use the same token for both." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po new file mode 100644 index 000000000..6ab90bf55 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -0,0 +1,202 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-sygnal.md:1 +msgid "Setting up the Sygnal push gateway (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:3 +msgid "" +"The playbook can install and configure the [Sygnal](https://github.com" +"/matrix-org/sygnal) push gateway for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/sygnal) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:7 +msgid "" +"**Note**: most people don't need to install their own gateway. As " +"Sygnal's [Notes for application developers](https://github.com/matrix-" +"org/sygnal/blob/master/docs/applications.md) documentation says:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:9 +msgid "" +"It is not feasible to allow end-users to configure their own Sygnal " +"instance, because the Sygnal instance needs the appropriate FCM or APNs " +"secrets that belong to the application." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:11 +msgid "" +"This optional playbook component is only useful to people who " +"develop/build their own Matrix client applications themselves." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:15 +msgid "" +"To enable Sygnal, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:43 +msgid "" +"For a more complete example of available fields and values they can take," +" see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the " +"[upstream `sygnal.yaml.sample` configuration file](https://github.com" +"/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:45 +msgid "" +"Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) " +"is easier, as it only requires that you provide some config values." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:47 +msgid "" +"To configure [APNS](https://developer.apple.com/notifications/) (Apple " +"Push Notification Service), you'd need to provide one or more certificate" +" files. To do that, the above example configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:49 +msgid "" +"makes use of the [`aux` role](https://github.com/mother-of-all-self-" +"hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to " +"make the playbook install files into `/matrix/sygnal/data` (the " +"`matrix_sygnal_data_path` variable). See [`defaults/main.yml` " +"file](https://github.com/mother-of-all-self-hosting/ansible-role-" +"aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It" +" also makes sure the files are owned by `matrix:matrix`, so that Sygnal " +"can read them. Of course, you can also install these files manually " +"yourself, if you'd rather not use `aux`." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:51 +msgid "" +"references these files in the Sygnal configuration (`matrix_sygnal_apps`)" +" using a path like `/data/..` (the `/matrix/sygnal/data` directory on the" +" host system is mounted into the `/data` directory inside the container)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:53 +msgid "Adjusting the Sygnal URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:55 +msgid "" +"By default, this playbook installs Sygnal on the `sygnal.` subdomain " +"(`sygnal.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:57 +msgid "" +"By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` " +"variables, you can easily make the service available at a **different " +"hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:59 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:70 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:72 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Sygnal domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:74 +msgid "" +"By default, you will need to create a CNAME record for `sygnal`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:76 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:78 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:80 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:87 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:89 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:91 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:93 +msgid "" +"To make use of your Sygnal installation, you'd need to build your own " +"Matrix client application, which uses the same API keys (for " +"[GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and " +"certificates (for [APNS](https://developer.apple.com/notifications/)) and" +" is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:95 +msgid "" +"Refer to Sygnal's [Notes for application developers](https://github.com" +"/matrix-org/sygnal/blob/master/docs/applications.md) document." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po new file mode 100644 index 000000000..b99172d3e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -0,0 +1,207 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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://matrix-" +"org.github.io/dendrite/administration/adminapi) differs from [Synapse " +"Admin API](https://element-" +"hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:7 +msgid "" +"💡 **Note**: the latest version of synapse-admin is hosted by " +"[etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). " +"If you only need this service occasionally and trust giving your admin " +"credentials to a 3rd party Single Page Application, you can consider " +"using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:11 +msgid "" +"To enable Synapse Admin, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "" +"**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to" +" function. Access to them is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, for " +"additional security, we normally leave them unexposed, following " +"[official Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints). Because Synapse Admin needs these APIs to function, when " +"installing Synapse Admin, the playbook **automatically** exposes the " +"Synapse Admin API publicly for you. Depending on the homeserver " +"implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:19 +msgid "" +"for [Synapse](./configuring-playbook-synapse.md) (our default homeserver " +"implementation): " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:20 +msgid "" +"for [Dendrite](./configuring-playbook-dendrite.md): " +"`matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled:" +" true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:22 +msgid "" +"By default, synapse-admin installation will be [restricted to only work " +"with one homeserver](https://github.com/etkecc/synapse-" +"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" +"#restricting-available-homeserver) - the one managed by the playbook. To " +"adjust these restrictions, tweak the " +"`matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:24 +msgid "" +"⚠️ **Warning**: If you're using [Matrix Authentication Service" +"](./configuring-playbook-matrix-authentication-service.md) (MAS) for " +"authentication, you will be able to [log into synapse-admin with an " +"access token](https://github.com/etkecc/synapse-admin/pull/58), but " +"certain synapse-admin features (especially those around user management) " +"will be limited or not work at all." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:26 +msgid "Adjusting the Synapse Admin URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:28 +msgid "" +"By default, this playbook installs Synapse Admin on the `matrix.` " +"subdomain, at the `/synapse-admin` path (https://matrix.example.com" +"/synapse-admin). This makes it easy to install it, because it **doesn't " +"require additional DNS records to be set up**. If that's okay, you can " +"skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:30 +msgid "" +"By tweaking the `matrix_synapse_admin_hostname` and " +"`matrix_synapse_admin_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:32 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:42 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Synapse Admin domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:46 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:50 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:63 +msgid "" +"After installation, Synapse Admin will be accessible at: " +"`https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:65 +msgid "" +"To use Synapse Admin, you need to have [registered at least one " +"administrator account](registering-users.md) on your server." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po new file mode 100644 index 000000000..b7dce7685 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po @@ -0,0 +1,103 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-auto-accept-invite.md:1 +msgid "Setting up Synapse Auto Invite Accept (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 +msgid "" +"The playbook can install and configure [synapse-auto-invite-" +"accept](https://github.com/matrix-org/synapse-auto-accept-invite) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 +msgid "" +"See that project's [documentation](https://github.com/matrix-org/synapse-" +"auto-accept-invite) to learn what it does and why it might be useful to " +"you. In short, it automatically accepts room invites. You can specify " +"that only 1:1 room invites are auto-accepted. Defaults to false if not " +"specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:7 +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:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +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:19 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +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:27 +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:29 +msgid "Native alternative" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +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:33 +msgid "Here's example configuration for using the **native** Synapse feature:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po new file mode 100644 index 000000000..9d7430ffd --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po @@ -0,0 +1,109 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-auto-compressor.md:1 +msgid "Setting up synapse-auto-compressor (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 +msgid "" +"The playbook can install and configure " +"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" +"compress-state/#automated-tool-synapse_auto_compressor) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 +msgid "" +"It's a CLI tool that automatically compresses Synapse's `state_groups` " +"database table in the background." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/rust-" +"synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn " +"what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 +msgid "" +"After installation, `synapse_auto_compressor` will run automatically " +"every day at `00:00:00` (as defined in " +"`matrix_synapse_auto_compressor_calendar` by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 +msgid "Manually start the tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 +msgid "" +"For testing your setup it can be helpful to not wait until 00:00. If you " +"want to run the tool immediately, log onto the server and run `systemctl " +"start matrix-synapse-auto-compressor`. Running this command will not " +"return control to your terminal until the compression run is done, which " +"may take a long time. Consider using " +"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " +"unstable." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po new file mode 100644 index 000000000..710df5e05 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po @@ -0,0 +1,382 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-s3-storage-provider.md:1 +msgid "" +"Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider" +" (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 +msgid "" +"If you'd like to store Synapse's content repository (`media_store`) files" +" on Amazon S3 (or other S3-compatible service), you can use the " +"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" +"-storage-provider) media provider module for Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 +msgid "" +"An alternative (which has worse performance) is to use [Goofys to mount " +"the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 +msgid "How it works?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 +msgid "" +"Summarized writings here are inspired by [this " +"article](https://quentin.dufour.io/blog/2021-09-14/matrix-" +"synapse-s3-storage/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 +msgid "The way media storage providers in Synapse work has some caveats:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 +msgid "" +"Synapse still continues to use locally-stored files (for creating " +"thumbnails, serving files, etc)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 +msgid "" +"the media storage provider is just an extra storage mechanism (in " +"addition to the local filesystem)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 +msgid "" +"all files are stored locally at first, and then copied to the media " +"storage provider (either synchronously or asynchronously)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 +msgid "" +"if a file is not available on the local filesystem, it's pulled from a " +"media storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 +msgid "" +"You may be thinking **if all files are stored locally as well, what's the" +" point**?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 +msgid "" +"You can run some scripts to delete the local files once in a while (which" +" we do automatically by default - see [Periodically cleaning up the local" +" filesystem](#periodically-cleaning-up-the-local-filesystem)), thus " +"freeing up local disk space. If these files are needed in the future (for" +" serving them to users, etc.), Synapse will pull them from the media " +"storage provider on demand." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 +msgid "" +"While you will need some local disk space around, it's only to " +"accommodate usage, etc., and won't grow as large as your S3 store." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 +msgid "" +"After [creating the S3 bucket and configuring it](configuring-" +"playbook-s3.md#bucket-creation-and-security-configuration), you can " +"proceed to configure `s3-storage-provider` in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 +msgid "" +"If you have existing files in Synapse's media repository " +"(`/matrix/synapse/media-store/..`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 +msgid "new files will start being stored both locally and on the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53 +msgid "" +"the existing files will remain on the local filesystem only until " +"[migrating them to the S3 store](#migrating-your-existing-media-files-to-" +"the-s3-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 +msgid "" +"at some point (and periodically in the future), you can delete local " +"files which have been uploaded to the S3 store already" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 +msgid "" +"Regardless of whether you need to [Migrate your existing files to the S3 " +"store](#migrating-your-existing-media-files-to-the-s3-store) or not, make" +" sure you've familiarized yourself with [How it works?](#how-it-works) " +"above and [Periodically cleaning up the local filesystem](#periodically-" +"cleaning-up-the-local-filesystem) below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 +msgid "Migrating your existing media files to the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60 +msgid "Migrating your existing data can happen in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 +msgid "" +"[using the `s3_media_upload` script from `synapse-s3-storage-provider" +"`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " +"(very slow when dealing with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 +msgid "" +"[using another tool in combination with `s3_media_upload`](#using-" +"another-tool-in-combination-with-s3_media_upload) (quicker when dealing " +"with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 +msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 +msgid "" +"Instead of using `s3_media_upload` directly, which is very slow and " +"painful for an initial data migration, we recommend [using another tool " +"in combination with `s3_media_upload`](#using-another-tool-in-" +"combination-with-s3_media_upload)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69 +msgid "" +"To copy your existing files, SSH into the server and run " +"`/matrix/synapse/ext/s3-storage-provider/bin/shell`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 +msgid "" +"This launches a Synapse container, which has access to the local media " +"store, Postgres database, S3 store and has some convenient environment " +"variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, " +"`UPDATE_DB_DAYS`, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 +msgid "" +"Then use the following commands (`$` values come from environment " +"variables - they're **not placeholders** that you need to substitute):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 +msgid "" +"`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite " +"database (`cache.db`) with a list of media repository files (from the " +"`synapse` Postgres database) eligible for operating on" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76 +msgid "" +"`$UPDATE_DB_DURATION` is influenced by the " +"`matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` " +"variable (defaults to `0`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 +msgid "" +"`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include " +"files which haven't been accessed for more than 0 days** (that is, **all " +"files will be included**)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 +msgid "" +"`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the " +"local cache still exist in the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 +msgid "" +"`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class " +"$STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files " +"to S3 and deletes them from the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 +msgid "The `s3_media_upload upload` command may take a lot of time to complete." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 +msgid "" +"Instead of running the above commands manually in the shell, you can also" +" run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script " +"which will run the same commands automatically. We demonstrate how to do " +"it manually, because:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 +msgid "" +"it's what the upstream project demonstrates and it teaches you how to use" +" the `s3_media_upload` tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 +msgid "" +"allows you to check and verify the output of each command, to catch " +"mistakes" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 +msgid "includes progress bars and detailed output for each command" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 +msgid "" +"allows you to easily interrupt slow-running commands, etc. (the " +"`/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container " +"without interactive TTY support, so `Ctrl+C` may not work and you and " +"require killing via `docker kill ..`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 +msgid "Using another tool in combination with `s3_media_upload`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92 +msgid "To migrate your existing local data to S3, we recommend to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 +msgid "" +"**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or " +"[`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files" +" to the S3 bucket" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 +msgid "" +"**only then** [use the `s3_media_upload` tool to finish the migration" +"](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " +"(this checks to ensure all files are uploaded and then deletes the local " +"files)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 +msgid "Copying data to Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100 +msgid "To copy to AWS S3, start a container on the Matrix server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112 +msgid "Copying data to an S3 alternative using the aws-s3 tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114 +msgid "" +"To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean " +"Spaces, etc.), you can use the command for [Copying data to Amazon S3" +"](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` " +"argument." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116 +msgid "" +"Add this argument to the command **as-is** (`$ENDPOINT` is an environment" +" variable corresponding to " +"`matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so " +"you don't need to touch it). Make sure to add the argument **before** the" +" final quote (`'`) of the command." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118 +msgid "Copying data to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 +msgid "" +"You can copy files to Backblaze B2 either by following the [Copying data " +"to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3" +"-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 " +"command-line " +"tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as " +"described below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 +msgid "" +"To copy the data using the `b2` tool, start a container on the Matrix " +"server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136 +msgid "Periodically cleaning up the local filesystem" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138 +msgid "" +"As described in [How it works?](#how-it-works) above, when new media is " +"uploaded to the Synapse homeserver, it's first stored locally and then " +"also stored on the remote S3 storage." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140 +msgid "" +"By default, we periodically ensure that all local files are uploaded to " +"S3 and are then removed from the local filesystem. This is done " +"automatically using:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142 +msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143 +msgid "" +".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` " +"service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 +msgid "" +".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` " +"timer, every day at 05:00" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 +msgid "So.. you don't need to perform any maintenance yourself." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po new file mode 100644 index 000000000..823f71180 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po @@ -0,0 +1,52 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-simple-antispam.md:1 +msgid "Setting up Synapse Simple Antispam (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 +msgid "" +"The playbook can install and configure [synapse-simple-" +"antispam](https://github.com/t2bot/synapse-simple-antispam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you. In short, it lets you fight invite-spam by " +"automatically blocking invitiations from a list of servers specified by " +"you (blacklisting)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po new file mode 100644 index 000000000..b3a621a72 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-usage-exporter.md:1 +msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 +msgid "" +"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" +"exporter) allows you to export the usage statistics of a Synapse " +"homeserver to this container service and for the collected metrics to " +"later be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 +msgid "" +"Synapse does not include usage statistics in its Prometheus metrics. They" +" can be reported to an HTTP `PUT` endpoint 5 minutes after startup and " +"from then on at a fixed interval of once every three hours. This role " +"integrates a simple [Flask](https://flask.palletsprojects.com) project " +"that offers an HTTP `PUT` endpoint and holds the most recent received " +"record available to be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 +msgid "Enabling this service will automatically:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 +msgid "install the synapse-usage-exporter service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 +msgid "" +"re-configure Synapse to push (via HTTP `PUT`) usage statistics " +"information to synapse-usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 +msgid "" +"re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) " +"(if Prometheus is enabled), to periodically scrape metrics from synapse-" +"usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 +msgid "" +"add a new [Grafana](./configuring-playbook-prometheus-grafana.md) " +"dashboard (if Grafana is enabled) containing Synapse usage statistics" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 +msgid "" +"To enable synapse-usage-exporter, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 +msgid "Adjusting the synapse-usage-exporter URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 +msgid "" +"By default, this playbook installs synapse-usage-exporter on the " +"`matrix.` subdomain, at the `/report-usage-stats/push` path " +"(https://matrix.example.com/report-usage-stats/push). This makes it easy " +"to install it, because it **doesn't require additional DNS records to be " +"set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 +msgid "" +"By tweaking the `matrix_synapse_usage_exporter_hostname` and " +"`matrix_synapse_usage_exporter_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the synapse-usage-exporter domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po new file mode 100644 index 000000000..cc2210b70 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po @@ -0,0 +1,437 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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.md:1 +msgid "Configuring Synapse (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, so that it works for the general " +"case. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:5 +msgid "" +"The playbook provides lots of customization variables you could use to " +"change Synapse's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:7 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/synapse/config/homeserver.yaml` file (on the server). This file " +"is generated from the [`roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:9 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:11 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a Synapse " +"setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:13 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Synapse's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:15 +msgid "" +"or, you can **extend and override the default configuration** " +"([`homeserver.yaml.j2`](../roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2)) by making use of the " +"`matrix_synapse_configuration_extension_yaml` variable. You can find " +"information about this in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:17 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). " +"You can find information about this in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:19 +msgid "Load balancing with workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:21 +msgid "" +"To have Synapse gracefully handle thousands of users, worker support " +"should be enabled. It factors out some homeserver tasks and spreads the " +"load of incoming client and server-to-server traffic between multiple " +"processes. More information can be found in the [official Synapse workers" +" documentation](https://github.com/element-" +"hq/synapse/blob/master/docs/workers.md) and [Tom " +"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/index.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:23 +msgid "" +"To enable Synapse worker support, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:31 +msgid "" +"By default, this enables the `one-of-each` [worker preset](#worker-" +"presets), but you may wish to use another preset or [control the number " +"of worker instances](#controlling-the-number-of-worker-instances)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:33 +msgid "Worker presets" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:35 +msgid "" +"We support a few configuration presets (`matrix_synapse_workers_preset: " +"one-of-each` being the default configuration right now):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:37 +msgid "" +"(federation-only) `little-federation-helper` - a very minimal worker " +"configuration to improve federation performance" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:38 +msgid "" +"(generic) `one-of-each` - defaults to one worker of each supported type -" +" no smart routing, just generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:39 +msgid "" +"(specialized) `specialized-workers` - defaults to one worker of each " +"supported type, but disables generic workers and uses [specialized " +"workers](#specialized-workers) instead" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:41 +msgid "" +"These presets represent a few common configurations. There are many " +"worker types which can be mixed and matched based on your needs." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:43 +msgid "Generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:45 +msgid "" +"Previously, the playbook only supported the most basic type of load-" +"balancing. We call it **generic load-balancing** below, because incoming " +"HTTP requests are sent to a generic worker. Load-balancing was done based" +" on the requestor's IP address. This is simple, but not necessarily " +"optimal. If you're accessing your account from multiple IP addresses " +"(e.g. your mobile phone being on a different network than your PC), these" +" separate requests may potentially be routed to different workers, each " +"of which would need to cache roughly the same data." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:47 +msgid "" +"This is **still the default load-balancing method (preset) used by the " +"playbook**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:49 +msgid "" +"To use generic load-balancing, do not specify " +"`matrix_synapse_workers_preset` to make it use the default value (`one-" +"of-each`), or better yet - explicitly set it as `one-of-each`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:51 +msgid "" +"You may also consider [tweaking the number of workers of each type" +"](#controlling-the-number-of-worker-instances) from the default (one of " +"each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:53 +msgid "Specialized workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:55 +msgid "" +"The playbook now supports a smarter **specialized load-balancing** " +"inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse " +"homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead " +"of routing requests to one or more [generic workers](#generic-workers) " +"based only on the requestor's IP adddress, specialized load-balancing " +"routes to **4 different types of specialized workers** based on **smarter" +" criteria** - the access token (username) of the requestor and/or on the " +"resource (room, etc.) being requested." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:57 +msgid "The playbook supports these **4 types** of specialized workers:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:59 +msgid "" +"Room workers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) & " +"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs " +"dedicated to handling specific rooms" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:60 +msgid "" +"Sync workers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to " +"synchronization (most notably [the `/sync` " +"endpoint](https://spec.matrix.org/v1.9/client-server-" +"api/#get_matrixclientv3sync))" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:61 +msgid "" +"Client readers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are " +"not for specific rooms (handled by **room workers**) or for " +"synchronization (handled by **sync workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:62 +msgid "" +"Federation readers - handles various " +"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which " +"are not for specific rooms (handled by **room workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:64 +msgid "" +"To use specialized load-balancing, consider enabling the `specialized-" +"workers` [worker preset](#worker-presets) and potentially [tweaking the " +"number of workers of each type](#controlling-the-number-of-worker-" +"instances) from the default (one of each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:66 +msgid "Controlling the number of worker instances" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:68 +msgid "" +"If you'd like more customization power, you can start with one of the " +"[worker presets](#worker-presets) and then tweak various " +"`matrix_synapse_workers_*_count` variables manually." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:70 +msgid "" +"To find what variables are available for you to override in your own " +"`vars.yml` configuration file, see the [`defaults/main.yml` file for the " +"`matrix-synapse` Ansible role](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:72 +msgid "" +"The only thing you **cannot** do is mix [generic workers](#generic-" +"workers) and [specialized workers](#specialized-workers)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:74 +msgid "Effect of enabling workers on the rest of your server" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:76 +msgid "" +"When Synapse workers are enabled, the integrated [Postgres database is " +"tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum " +"number of Postgres connections are increased from `200` to `500`. If you " +"need to decrease or increase the number of maximum Postgres connections " +"further, use the `postgres_max_connections` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:78 +msgid "" +"A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and " +"component handles load-balancing for workers. This role/component is " +"automatically enabled when you enable workers. Make sure to use the " +"`setup-all` tag (not `install-all`!) during the playbook's " +"[installation](./installing.md) process, especially if you're disabling " +"workers, so that components may be installed/uninstalled correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:80 +msgid "" +"In case any problems occur, make sure to have a look at the [list of " +"synapse issues about workers](https://github.com/element-" +"hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit " +"'matrix-*'`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:82 +msgid "Synapse Admin" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:84 +msgid "" +"Certain Synapse administration tasks (managing users and rooms, etc.) can" +" be performed via a web user-interace, if you install [Synapse Admin" +"](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:86 +msgid "Synapse + OpenID Connect for Single-Sign-On" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:88 +msgid "" +"💡 An alternative to setting up OIDC in Synapse is to use [Matrix " +"Authentication Service](./configuring-playbook-matrix-authentication-" +"service.md) (MAS). Newer clients (like Element X) only support SSO-based " +"authentication via MAS and not via the legacy Synapse OIDC setup " +"described below. That said, MAS is still a new experimental service which" +" comes with its own downsides. Consult its documentation to learn if it " +"will be a good fit for your deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:90 +msgid "" +"If you'd like to use OpenID Connect authentication with Synapse, you'll " +"need some additional configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:92 +msgid "" +"This example configuration is for [keycloak](https://www.keycloak.org/), " +"an opensource Identity Provider maintained by Red Hat." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:94 +msgid "" +"For more detailed documentation on available options and how to setup " +"keycloak, see the [Synapse documentation on OpenID Connect with " +"keycloak](https://github.com/element-" +"hq/synapse/blob/develop/docs/openid.md#keycloak)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:96 +#, python-format +msgid "" +"In case you encounter errors regarding the parsing of the variables, you " +"can try to add `{% raw %}` and `{% endraw %}` blocks around them. For " +"example ;" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:117 +msgid "Customizing templates" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:119 +msgid "" +"[Templates](https://github.com/element-" +"hq/synapse/blob/develop/docs/templates.md) are used by Synapse for " +"showing **certain web pages** handled by the server, as well as for " +"**email notifications**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:121 +msgid "" +"This playbook allows you to customize the default templates (see the " +"[`synapse/res/templates` directory](https://github.com/element-" +"hq/synapse/tree/develop/synapse/res/templates))." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:123 +msgid "" +"If template customization is enabled, the playbook will build a custom " +"container image based on the official one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:125 +msgid "" +"Your custom templates need to live in a public or private git repository." +" This repository will be cloned during Synapse image customization " +"(during the playbook run)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:127 +msgid "" +"To enable template customizations, use a configuration " +"(`inventory/host_vars/matrix.example.com/vars.yml`) like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:153 +msgid "" +"As mentioned in Synapse's Templates documentation, Synapse will fall back" +" to its own templates if a template is not found in that directory. Due " +"to this, it's recommended to only store and maintain template files in " +"your repository if you need to make custom changes. Other files (which " +"you don't need to change), should not be duplicated, so that you don't " +"need to worry about getting out-of-sync with the original Synapse " +"templates." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:155 +msgid "Monitoring Synapse Metrics with Prometheus and Grafana" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:157 +msgid "" +"This playbook allows you to enable Synapse metrics, which can provide " +"insight into the performance and activity of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:159 +msgid "" +"To enable Synapse runtime metrics see: [Enabling metrics and graphs " +"(Prometheus, Grafana) for your Matrix server](configuring-playbook-" +"prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:161 +msgid "" +"To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter " +"for Synapse usage statistics](configuring-playbook-synapse-usage-" +"exporter.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po new file mode 100644 index 000000000..58fb8cae7 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po @@ -0,0 +1,75 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-telemetry.md:1 +msgid "Enabling Telemetry for your Matrix server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:3 +msgid "" +"By default, this playbook configures your Matrix homeserver to not send " +"any telemetry data anywhere." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:5 +msgid "" +"The [matrix.org](https://matrix.org) team would really appreciate it if " +"you could help the project out by reporting usage statistics from your " +"homeserver. Enabling usage statistics helps track the growth of the " +"Matrix community, and helps to make Matrix a success." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:7 +msgid "Enabling Telemetry" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:9 +msgid "" +"If you'd like to **help by enabling submission of general usage " +"statistics** for your homeserver, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:17 +msgid "Usage statistics being submitted" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:19 +msgid "" +"When enabled, your homeserver will regularly upload a few dozen " +"statistics about your server. This data includes your homeserver's " +"domain, the total number of users, the number of active users, the total " +"number of rooms, and the number of messages sent per day on your " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:21 +msgid "" +"See [Synapse's documentation](https://github.com/element-" +"hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md" +"#available-statistics) or [Dendrite's documentation](https://github.com" +"/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-" +"enabling-phone-home-statistics) for the full list of statistics that are " +"reported." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po new file mode 100644 index 000000000..0b97553e6 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-traefik.md:1 +msgid "Configuring the Traefik reverse-proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:3 +msgid "" +"By default, this playbook installs and manages a " +"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered " +"by the [ansible-role-traefik](https://github.com/mother-of-all-self-" +"hosting/ansible-role-traefik) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:5 +msgid "" +"This Ansible role support various configuration options. Feel free to " +"consult its `default/main.yml` variables file." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:7 +msgid "Adjusting SSL certificate retrieval" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:9 +msgid "" +"See the dedicated [Adjusting SSL certificate retrieval](configuring-" +"playbook-ssl-certificates.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:11 +msgid "Increase logging verbosity" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:17 +msgid "Disable access logs" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:19 +msgid "This will disable access logging." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:25 +msgid "Enable Traefik Dashboard" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:27 +msgid "" +"This will enable a Traefik " +"[Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at " +"`https://matrix.example.com/dashboard/` (note the trailing `/`)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:37 +msgid "" +"**WARNING**: Enabling the dashboard on a hostname you use for something " +"else (like `matrix_server_fqn_matrix` in the configuration above) may " +"cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all" +" `/dashboard` and `/api` requests and forward them to itself. If any of " +"the services hosted on the same hostname requires any of these 2 URL " +"prefixes, you will experience problems. So far, we're not aware of any " +"playbook services which occupy these endpoints and are likely to cause " +"conflicts." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:39 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:41 +msgid "" +"Use the `traefik_configuration_extension_yaml` variable provided by the " +"Traefik Ansible role to override or inject additional settings, even when" +" no dedicated variable exists." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:51 +msgid "Reverse-proxying another service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:53 +msgid "" +"The preferred way to reverse-proxy additional services behind Traefik " +"would be to start the service as another container, configure the " +"container with the corresponding Traefik [container " +"labels](https://docs.docker.com/config/labels-custom-metadata/) (see " +"[Traefik & " +"Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and " +"connect the service to the `traefik` network. Some services are also " +"already available via the compatible [mash-playbook](https://github.com" +"/mother-of-all-self-hosting/mash-playbook), but take a look at the minor " +"[interoperability adjustments](https://github.com/mother-of-all-self-" +"hosting/mash-playbook/blob/main/docs/interoperability.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:55 +msgid "" +"However, if your service does not run on a container or runs on another " +"machine, the following configuration might be what you are looking for." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:57 +msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:59 +msgid "" +"If you want to host another webserver would be reachable via `my-fancy-" +"website.example.net` from the internet and via `https://:` from inside your network, you can " +"make the playbook's integrated Traefik instance reverse-proxy the traffic" +" to the correct host." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:61 +msgid "" +"Prerequisites: DNS and routing for the domain `my-fancy-" +"website.example.net` need to be set up correctly. In this case, you'd be " +"pointing the domain name to your Matrix server - `my-fancy-" +"website.example.net` would be a CNAME going to `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:63 +msgid "" +"First, we have to adjust the static configuration of Traefik, so that we " +"can add additional configuration files:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:77 +msgid "" +"If you are using a self-signed certificate on your webserver, you can " +"tell Traefik to trust your own backend servers by adding more " +"configuration to the static configuration file. If you do so, bear in " +"mind the security implications of disabling the certificate validity " +"checks towards your back end." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:91 +msgid "" +"Next, you have to add a new dynamic configuration file for Traefik that " +"contains the actual information of the server using the " +"`aux_file_definitions` variable. In this example, we will terminate SSL " +"at the Traefik instance and connect to the other server via HTTPS. " +"Traefik will now take care of managing the certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:110 +#: ../../../docs/configuring-playbook-traefik.md:133 +msgid "" +"Changing the `url` to one with an `http://` prefix would allow to connect" +" to the server via HTTP." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:112 +msgid "Reverse-proxying another service behind Traefik without terminating SSL" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:114 +msgid "" +"If you do not want to terminate SSL at the Traefik instance (for example," +" because you're already terminating SSL at other webserver), you need to " +"adjust the static configuration in the same way as in the previous " +"chapter in order to be able to add our own dynamic configuration files. " +"Afterwards, you can add the following configuration to your `vars.yml` " +"configuration file:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:135 +msgid "" +"With these changes, all TCP traffic will be reverse-proxied to the target" +" system." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:137 +msgid "" +"**WARNING**: This configuration might lead to problems or need additional" +" steps when a [certbot](https://certbot.eff.org/) behind Traefik also " +"tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, " +"as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-" +"challenge/`)```." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:139 +msgid "Traefik behind a `proxy_protocol` reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:141 +msgid "" +"If you run a reverse-proxy which speaks `proxy_protocol`, add the " +"following to your configuration file:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po new file mode 100644 index 000000000..02a771d39 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -0,0 +1,158 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-turn.md:1 +msgid "Adjusting TURN server configuration (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:3 +msgid "" +"The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN " +"server by default, so that clients can make audio/video calls even from " +"[NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed " +"networks." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:5 +msgid "" +"By default, the Synapse chat server is configured, so that it points to " +"the Coturn TURN server installed by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:7 +msgid "Disabling Coturn" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:9 +msgid "" +"If, for some reason, you'd like to prevent the playbook from installing " +"Coturn, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:15 +msgid "" +"In that case, Synapse would not point to any Coturn servers and " +"audio/video call functionality may fail." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:17 +msgid "Manually defining your public IP" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:19 +msgid "" +"In the `hosts` file we explicitly ask for your server's external IP " +"address when defining `ansible_host`, because the same value is used for " +"configuring Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:21 +msgid "" +"If you'd rather use a local IP for `ansible_host`, make sure to set up " +"`matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with " +"the pubic IP used by the server." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:27 +msgid "" +"If you'd like to rely on external IP address auto-detection (not " +"recommended unless you need it), set " +"`matrix_coturn_turn_external_ip_address` to an empty value. The playbook " +"will automatically contact an " +"[EchoIP](https://github.com/mpolden/echoip)-compatible service " +"(`https://ifconfig.co/json` by default) to determine your server's IP " +"address. This API endpoint is configurable via the " +"`matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url`" +" variable." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:29 +msgid "" +"If your server has multiple external IP addresses, the Coturn role offers" +" a different variable for specifying them:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:36 +msgid "Changing the authentication mechanism" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:38 +msgid "" +"The playbook uses the [`auth-secret` authentication " +"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199)" +" by default, but you may switch to the [`lt-cred-mech` " +"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178)" +" which [some report](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3191) to be working better." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:40 +msgid "To do so, add this override to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:46 +msgid "" +"Regardless of the selected authentication method, the playbook generates " +"secrets automatically and passes them to the homeserver and Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:48 +msgid "" +"If you're using [Jitsi](./configuring-playbook-jitsi.md), note that " +"switching to `lt-cred-mech` will remove the integration between Jitsi and" +" your own Coturn server, because Jitsi only seems to support the `auth-" +"secret` authentication method." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:50 +msgid "Using your own external Coturn server" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:52 +msgid "" +"If you'd like to use another TURN server (be it Coturn or some other " +"one), you can configure the playbook like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:66 +msgid "" +"If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you" +" might want to enable the TURN server there too. If you do not do it, " +"Jitsi will fall back to an upstream service." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:72 +msgid "You can put multiple host/port combinations if you like." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:74 +msgid "Further variables and configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:75 +msgid "" +"To see all the available configuration options, check roles/custom" +"/matrix-coturn/defaults/main.yml" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po new file mode 100644 index 000000000..20c5ed834 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -0,0 +1,312 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-user-verification-service.md:1 +msgid "Setting up Matrix User Verification Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:3 +msgid "" +"**[Matrix User Verification Service](https://github.com/matrix-org" +"/matrix-user-verification-service) (hereafter: UVS) can only be installed" +" after Matrix services are installed and running.** If you're just " +"installing Matrix services for the first time, please continue with the " +"[Configuration](configuring-playbook.md) / [Installation](installing.md) " +"flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:5 +msgid "" +"Currently, the main purpose of this role is to allow Jitsi to " +"authenticate Matrix users and check if they are authorized to join a " +"conference. Please refer to the documentation of the [Matrix User " +"Verification Service](https://github.com/matrix-org/matrix-user-" +"verification-service) to understand how it works." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:7 +msgid "" +"**Note**: enabling Matrix User Verification Service, means that the " +"`openid` API endpoints will be exposed on the Matrix Federation port " +"(usually `8448`), even if [federation](configuring-playbook-" +"federation.md) is disabled." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:9 +msgid "" +"If the Jitsi server is also configured by this playbook, all plugging of " +"variables and secrets is handled in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:11 +msgid "" +"__Some general concepts of UVS may be helpful to understand the rest, so " +"here they are:__" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:13 +msgid "UVS can be used to verify two claims:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:15 +msgid "(A) Whether a given OpenID token is valid for a given server and" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:16 +msgid "" +"(B) whether a user is member of a given room and the corresponding " +"PowerLevel" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:18 +msgid "" +"Verifying an OpenID token ID done by finding the corresponding Homeserver" +" via '.well-known/matrix/server' for the given domain. The configured " +"`matrix_user_verification_service_uvs_homeserver_url` does **not** factor" +" into this. By default, this playbook only checks against " +"`matrix_server_fqn_matrix`. Therefore, the request will be made against " +"the public openid API for `matrix_server_fqn_matrix`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:20 +msgid "" +"Verifying RoomMembership and PowerLevel is done against " +"`matrix_user_verification_service_uvs_homeserver_url` which is by default" +" done via the docker network. UVS will verify the validity of the token " +"beforehand though." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:24 +msgid "" +"In order to use UVS, an admin token for the configured homeserver must be" +" supplied. For now this means configuring Synapse and creating the token " +"before installing UVS." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:26 +msgid "Enable" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:28 +msgid "" +"To enable Matrix User Verification Service, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:34 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:36 +msgid "" +"The only required configuration variable is " +"`matrix_user_verification_service_uvs_access_token` (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:38 +msgid "" +"For a list of all configuration options see the role defaults [`roles" +"/matrix-user-verification-service/defaults/main.yml`](../roles/custom" +"/matrix-user-verification-service/defaults/main.yml). But be aware of all" +" the plugging happening in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:40 +msgid "" +"In the default configuration, the UVS Server is only reachable via the " +"docker network, which is fine if e.g. Jitsi is also running in a " +"container on the host. However, it is possible to expose UVS via setting " +"`matrix_user_verification_service_container_http_host_bind_port`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:42 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:44 +msgid "" +"The Synapse Access Token is used to verify RoomMembership and PowerLevel " +"against `matrix_user_verification_service_uvs_homeserver_url`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:46 +msgid "" +"We recommend that you create a dedicated Matrix user for uvs (`uvs` is a " +"good username). Follow our [Registering users](registering-users.md) " +"guide to register a user with administration privileges." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:48 +msgid "" +"You are required to specify an access token (belonging to this new user) " +"for UVS to work. To get an access token for the UVS user, you can follow " +"the documentation on [how to do obtain an access token](obtaining-access-" +"tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:50 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:56 +msgid "(Optional) Custom Auth Token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:58 +msgid "" +"It is possible to set an API Auth Token to restrict access to the UVS. If" +" this is enabled, anyone making a request to UVS must provide it via the " +"header \"Authorization: Bearer TOKEN\"" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:60 +msgid "" +"By default, the token will be derived from " +"`matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:62 +msgid "" +"To set your own Token, add the following configuration to your `vars.yml`" +" file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:68 +msgid "" +"In case Jitsi is also managed by this playbook and 'matrix' " +"authentication in Jitsi is enabled, this collection will automatically " +"configure Jitsi to use the configured auth token." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:70 +msgid "(Optional) Disable Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:72 +msgid "" +"Authorization is enabled by default. To disable it, add the following " +"configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:78 +msgid "(Optional) Federation" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:80 +msgid "" +"In theory (however currently untested), UVS can handle federation. To " +"enable it, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:86 +msgid "" +"This will instruct UVS to verify the OpenID token against any domain " +"given in a request. Homeserver discovery is done via '.well-" +"known/matrix/server' of the given domain." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:88 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:90 +msgid "" +"After these variables have been set, run the playbook with [playbook tags" +"](playbook-tags.md) as below to restart UVS:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:96 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just run-tags setup-matrix-user-verification-service,start` " +"or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:98 +msgid "" +"`just run-tags setup-matrix-user-verification-service,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-user-verification-service.md:100 +msgid "Logging" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:102 +msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:103 +msgid "warning" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:104 +msgid "info" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:105 +msgid "debug" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:107 +msgid "TLS Certificate Checking" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:109 +msgid "" +"If the Matrix Homeserver does not provide a valid TLS certificate, UVS " +"will fail with the following error message:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:111 +msgid "message: 'No response received: [object Object]'," +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:113 +msgid "This also applies to self-signed and let's encrypt staging certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:115 +msgid "" +"To disable certificate validation altogether (INSECURE! Not suitable for " +"production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:117 +msgid "" +"Alternatively, it is possible to inject your own CA certificates into the" +" container by mounting a PEM file with additional trusted CAs into the " +"container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to " +"it." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po new file mode 100644 index 000000000..0bcce4848 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po @@ -0,0 +1,777 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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.md:1 +msgid "Configuring the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook.md:3 +msgid "" +"[Prerequisites](prerequisites.md) > [Configuring your DNS settings" +"](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) >" +" Configuring the playbook > [Installing](installing.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:5 +msgid "" +"If you've configured your DNS records and retrieved the playbook's source" +" code to your computer, you can start configuring the playbook. To do so," +" follow these steps inside the playbook directory:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:7 +msgid "" +"create a directory to hold your configuration (`mkdir -p " +"inventory/host_vars/matrix.example.com` where `example.com` is your " +"\"base domain\")" +msgstr "" + +#: ../../../docs/configuring-playbook.md:9 +msgid "" +"copy the sample configuration file (`cp examples/vars.yml " +"inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:11 +msgid "" +"edit the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You " +"may also take a look at the various " +"`roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's " +"something you'd like to copy over and override in your `vars.yml` " +"configuration file." +msgstr "" + +#: ../../../docs/configuring-playbook.md:13 +msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:15 +msgid "edit the inventory hosts file (`inventory/hosts`) to your liking" +msgstr "" + +#: ../../../docs/configuring-playbook.md:17 +msgid "" +"(optional, advanced) you may wish to keep your `inventory` directory " +"under version control with [git](https://git-scm.com/) or any other " +"version-control system." +msgstr "" + +#: ../../../docs/configuring-playbook.md:19 +msgid "" +"(optional, advanced) to run Ansible against multiple servers with " +"different `sudo` credentials, you can copy the sample inventory hosts " +"yaml file for each of your hosts: (`cp examples/host.yml " +"inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin" +"/ansible-all-hosts.sh) script [in the installation step](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:21 +msgid "For a basic Matrix installation, that's all you need." +msgstr "" + +#: ../../../docs/configuring-playbook.md:23 +msgid "" +"For a more custom setup, see the [Other configuration options](#other-" +"configuration-options) below." +msgstr "" + +#: ../../../docs/configuring-playbook.md:25 +msgid "" +"[▶️](installing.md) When you're done with all the configuration you'd " +"like to do, continue with [Installing](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:27 +msgid "Other configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook.md:29 +msgid "Core service adjustments" +msgstr "" + +#: ../../../docs/configuring-playbook.md:31 +msgid "Homeserver configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:32 +msgid "" +"[Configuring Synapse](configuring-playbook-synapse.md), if you're going " +"with the default/recommended homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:34 +msgid "" +"[Configuring Conduit](configuring-playbook-conduit.md), if you've " +"switched to the [Conduit](https://conduit.rs) homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:36 +msgid "" +"[Configuring Dendrite](configuring-playbook-dendrite.md), if you've " +"switched to the [Dendrite](https://matrix-org.github.io/dendrite) " +"homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:38 +msgid "Server components:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:39 +msgid "" +"[Using an external PostgreSQL server](configuring-playbook-external-" +"postgres.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:41 +msgid "" +"[Adjusting TURN server configuration](configuring-playbook-turn.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:43 +msgid "" +"[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:45 +msgid "" +"[Using your own webserver, instead of this playbook's Traefik reverse-" +"proxy](configuring-playbook-own-webserver.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:47 +msgid "" +"[Adjusting SSL certificate retrieval](configuring-playbook-ssl-" +"certificates.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:49 +msgid "[Adjusting email-sending settings](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:51 +msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:53 +msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:55 +msgid "Server connectivity:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:56 +msgid "" +"[Enabling Telemetry for your Matrix server](configuring-playbook-" +"telemetry.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:58 +msgid "[Controlling Matrix federation](configuring-playbook-federation.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:60 +msgid "Clients" +msgstr "" + +#: ../../../docs/configuring-playbook.md:62 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/configuring-playbook.md:64 +msgid "" +"[Configuring Element Web](configuring-playbook-client-element-web.md), if" +" you're going with the default/recommended client" +msgstr "" + +#: ../../../docs/configuring-playbook.md:66 +msgid "" +"[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've" +" enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a " +"lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/configuring-playbook.md:68 +msgid "" +"[Setting up Cinny](configuring-playbook-client-cinny.md), if you've " +"enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing " +"primarily on simple, elegant and secure interface" +msgstr "" + +#: ../../../docs/configuring-playbook.md:70 +msgid "" +"[Setting up SchildiChat Web](configuring-playbook-client-schildichat-" +"web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a " +"web client based on [Element Web](https://element.io/) with some extras " +"and tweaks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:72 +msgid "Authentication and user-related" +msgstr "" + +#: ../../../docs/configuring-playbook.md:74 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook.md:76 +msgid "" +"[Setting up Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md) (Next-generation auth for Matrix, based on " +"OAuth 2.0/OIDC)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:78 +msgid "" +"[Setting up Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:80 +msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:82 +msgid "" +"[Setting up matrix-registration](configuring-playbook-matrix-" +"registration.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:84 +msgid "" +"[Setting up the REST authentication password provider module" +"](configuring-playbook-rest-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:86 +msgid "" +"[Setting up the Shared Secret Auth password provider module](configuring-" +"playbook-shared-secret-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:88 +msgid "" +"[Setting up the LDAP authentication password provider module" +"](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:90 +msgid "" +"[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-" +"ldap-registration-proxy.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:92 +msgid "" +"[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-" +"antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:94 +msgid "" +"[Setting up Matrix User Verification Service](configuring-playbook-user-" +"verification-service.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../docs/configuring-playbook.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/configuring-playbook.md:100 +msgid "" +"[Storing Matrix media files on Amazon S3 with Goofys](configuring-" +"playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:102 +msgid "" +"[Storing Synapse media files on Amazon S3 or another compatible Object " +"Storage](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:104 +msgid "" +"[Storing Matrix media files using matrix-media-repo](configuring-" +"playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:106 +msgid "Bridging other networks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:108 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../docs/configuring-playbook.md:110 +msgid "" +"[Setting up Mautrix Discord bridging](configuring-playbook-bridge-" +"mautrix-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:112 +msgid "" +"[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-" +"mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:114 +msgid "" +"[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-" +"slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:116 +msgid "" +"[Setting up Mautrix Google Messages bridging](configuring-playbook-" +"bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:118 +msgid "" +"[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-" +"mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:120 +msgid "" +"[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-" +"bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:122 +msgid "" +"[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-" +"bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:124 +msgid "" +"[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-" +"mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:126 +msgid "" +"[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-" +"mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:128 +msgid "" +"[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-" +"signal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:130 +msgid "" +"[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage" +"](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:132 +msgid "" +"[Setting up Appservice IRC bridging](configuring-playbook-bridge-" +"appservice-irc.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:134 +msgid "" +"[Setting up Appservice Discord bridging](configuring-playbook-bridge-" +"appservice-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:136 +msgid "" +"[Setting up Appservice Slack bridging](configuring-playbook-bridge-" +"appservice-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:138 +msgid "" +"[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-" +"appservice-kakaotalk.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:140 +msgid "" +"[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-" +"linkedin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:142 +msgid "" +"[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a" +" bridge between Matrix and multiple project management services, such as " +"[GitHub](https://github.com), [GitLab](https://about.gitlab.com) and " +"[JIRA](https://www.atlassian.com/software/jira)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:144 +msgid "" +"[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-" +"puppet-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:146 +msgid "" +"[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-" +"puppet-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:148 +msgid "" +"[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-" +"puppet-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:150 +msgid "" +"[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-" +"puppet-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:152 +msgid "" +"[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-" +"puppet-groupme.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:154 +msgid "" +"[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-" +"puppet-steam.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:156 +msgid "" +"[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-" +"skype-bridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:158 +msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:160 +msgid "" +"[Setting up Postmoogle email bridging](configuring-playbook-bridge-" +"postmoogle.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:162 +msgid "" +"[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-" +"bridge-sms.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:164 +msgid "" +"[Setting up Heisenbridge bouncer-style IRC bridging](configuring-" +"playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:166 +msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:168 +msgid "Bots" +msgstr "" + +#: ../../../docs/configuring-playbook.md:170 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:172 +msgid "" +"[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through " +"which you can talk to various " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) " +"services ([OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) and " +"[others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:174 +msgid "" +"[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-" +"reminder-bot.md) - a bot to remind you about stuff" +msgstr "" + +#: ../../../docs/configuring-playbook.md:176 +msgid "" +"[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-" +"registration-bot.md) - a bot to create and manage registration tokens to " +"invite users" +msgstr "" + +#: ../../../docs/configuring-playbook.md:178 +msgid "" +"[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based " +"Matrix bot system" +msgstr "" + +#: ../../../docs/configuring-playbook.md:180 +msgid "" +"[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk " +"bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:182 +msgid "" +"[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation " +"tool/bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:184 +msgid "" +"[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a " +"moderation tool/bot, forked from Mjolnir and maintained by its former " +"leader developer" +msgstr "" + +#: ../../../docs/configuring-playbook.md:186 +msgid "" +"[Setting up Draupnir for all/D4A](configuring-playbook-appservice-" +"draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-" +"draupnir.md) mentioned above, but running in appservice mode and " +"supporting multiple instances" +msgstr "" + +#: ../../../docs/configuring-playbook.md:188 +msgid "" +"[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you" +" can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../docs/configuring-playbook.md:190 +msgid "Administration" +msgstr "" + +#: ../../../docs/configuring-playbook.md:192 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:194 +msgid "" +"[Setting up Prometheus Alertmanager integration via matrix-alertmanager-" +"receiver](configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:196 +msgid "" +"[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server" +"](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:198 +msgid "" +"[Enabling metrics and graphs for NginX logs](configuring-playbook-" +"prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:200 +msgid "" +"[Setting up the rageshake bug report server](configuring-playbook-" +"rageshake.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:202 +msgid "" +"[Enabling synapse-usage-exporter for Synapse usage statistics" +"](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:204 +msgid "Backups:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:205 +msgid "" +"[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full " +"Matrix server backup solution, including the Postgres database" +msgstr "" + +#: ../../../docs/configuring-playbook.md:207 +msgid "" +"[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a" +" Postgres-database backup solution (note: does not include other files)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:209 +msgid "Other specialized services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:211 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/configuring-playbook.md:213 +msgid "" +"[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-" +"auto-accept-invite.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:215 +msgid "" +"[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-" +"compressor.md) for compressing the database on Synapse homeservers" +msgstr "" + +#: ../../../docs/configuring-playbook.md:217 +msgid "" +"[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:219 +msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:221 +msgid "" +"[Setting up the Jitsi video-conferencing platform](configuring-playbook-" +"jitsi.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:223 +msgid "" +"[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a" +" federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook.md:225 +msgid "" +"[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-" +"pantalaimon.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:227 +msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:229 +msgid "" +"[Setting up the ntfy push notifications server](configuring-playbook-" +"ntfy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:231 +msgid "Deprecated / unmaintained / removed services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:233 +msgid "" +"**Note**: since a deprecated or unmaintained service will not be updated," +" its bug or vulnerability will be unlikely to get patched. It is " +"recommended to migrate from the service to an alternative if any, and " +"make sure to do your own research before you decide to keep it running " +"nonetheless." +msgstr "" + +#: ../../../docs/configuring-playbook.md:235 +msgid "" +"[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-" +"proxy.md) for clients which require Sliding Sync support (like old " +"Element X versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:237 +msgid "" +"[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-" +"appservice-webhooks.md) (deprecated; the bridge's author suggests taking " +"a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) as a replacement, which can also be installed using [this " +"playbook](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:239 +msgid "" +"[Setting up the Dimension integration manager](configuring-playbook-" +"dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/2806#issuecomment-1673559299); after " +"[installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:241 +msgid "" +"[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; " +"the bridge's author suggests taking a look at [matrix-" +"hookshot](https://github.com/matrix-org/matrix-hookshot) as a " +"replacement, which can also be installed using [this playbook" +"](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:243 +msgid "" +"[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) " +"(unmaintained; the bridge's author suggests taking a look at " +"[baibot](https://github.com/etkecc/baibot) as a replacement, which can " +"also be installed using [this playbook](configuring-playbook-bot-" +"baibot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:245 +msgid "" +"[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-" +"mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram " +"bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-" +"meta-messenger.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:247 +msgid "" +"[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-" +"mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with " +"[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:249 +msgid "" +"[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-" +"mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram " +"bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-" +"meta-instagram.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:251 +msgid "" +"[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-" +"puppet-skype.md) (removed; this component has been broken for a long " +"time, so it has been removed from the playbook. Consider [setting up Go " +"Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po new file mode 100644 index 000000000..669f9baa0 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po @@ -0,0 +1,393 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/configuring-well-known.md:1 +msgid "Configuring Service Discovery via .well-known" +msgstr "" + +#: ../../../docs/configuring-well-known.md:3 +msgid "" +"This documentation page explains how to configure Service discovery via " +"`/.well-known/` files. Service discovery is a way for the Matrix network " +"to discover where a Matrix server is." +msgstr "" + +#: ../../../docs/configuring-well-known.md:5 +msgid "Types of well-known service discovery mechanism" +msgstr "" + +#: ../../../docs/configuring-well-known.md:7 +msgid "" +"There are 3 types of well-known service discovery mechanism that Matrix " +"makes use of:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:9 +msgid "" +"(important) **Federation Server discovery** (`/.well-" +"known/matrix/server`) -- assists other servers in the Matrix network with" +" finding your server. With the default playbook configuration specified " +"on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " +"this is necessary for federation to work. Without a proper configuration," +" your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/configuring-well-known.md:11 +msgid "" +"(less important) **Client Server discovery** (`/.well-" +"known/matrix/client`) -- assists programs that you use to connect to your" +" server (e.g. Element Web), so that they can make it more convenient for " +"you by automatically configuring the \"Homeserver URL\" and \"Identity " +"Server URL\" addresses." +msgstr "" + +#: ../../../docs/configuring-well-known.md:13 +msgid "" +"(optional) **Support service discovery** (`/.well-known/matrix/support`) " +"-- returns server admin contact and support page of the domain." +msgstr "" + +#: ../../../docs/configuring-well-known.md:15 +msgid "Federation Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:17 +msgid "" +"All services created by this playbook are meant to be installed on their " +"own server (such as `matrix.example.com`), instead of the base domain " +"(`example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:19 +msgid "" +"As [per the Server-Server " +"specification](https://matrix.org/docs/spec/server_server/r0.1.0.html" +"#server-discovery), in order to use a short Matrix user ID like " +"`@alice:example.com` instead of `@alice:matrix.example.com` while hosting" +" services on a subdomain such as `matrix.example.com`, the Matrix network" +" needs to be instructed of [server delegation](howto-server-" +"delegation.md) / redirection." +msgstr "" + +#: ../../../docs/configuring-well-known.md:21 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:23 +msgid "" +"If you set up the DNS SRV record for server delegation instead, take a " +"look at this documentation for more information: [Server Delegation via a" +" DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-" +"via-a-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/configuring-well-known.md:25 +msgid "Client Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:27 +msgid "" +"Client Server Service discovery lets various client programs which " +"support it, to receive a full user ID (e.g. `@alice:example.com`) and " +"determine where the Matrix server is automatically (e.g. " +"`https://matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:29 +msgid "" +"This lets you (and your users) easily connect to your Matrix server " +"without having to customize connection URLs. When using client programs " +"that support it, you won't need to point them to " +"`https://matrix.example.com` in Custom Server options manually anymore. " +"The connection URL would be discovered automatically from your full " +"username." +msgstr "" + +#: ../../../docs/configuring-well-known.md:31 +msgid "" +"Without /.well-known/matrix/client, the client will make the wrong " +"\"homeserver URL\" assumption (it will default to using " +"https://example.com, and users will need to notice and adjust it manually" +" (changing it to https://matrix.example.com)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:33 +msgid "" +"As [per the Client-Server " +"specification](https://matrix.org/docs/spec/client_server/r0.4.0.html" +"#server-discovery) Matrix does Client Server service discovery using a " +"`/.well-known/matrix/client` file hosted on the base domain (e.g. " +"`example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:35 +msgid "" +"However, this playbook installs your Matrix server on another domain " +"(e.g. `matrix.example.com`) and not on the base domain (e.g. " +"`example.com`), so it takes a little extra manual effort to set up the " +"file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:37 +msgid "(Optional) Support Service Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:39 +msgid "" +"[MSC 1929](https://github.com/matrix-org/matrix-spec-" +"proposals/pull/1929), which was added to [Matrix Specification version " +"v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-" +"knownmatrixsupport), specifies a way to add contact details of admins, as" +" well as a link to a support page for users who are having issues with " +"the service. Automated services may also index this information and use " +"it for abuse reports, etc." +msgstr "" + +#: ../../../docs/configuring-well-known.md:41 +msgid "" +"To enable it, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:62 +msgid "Installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:64 +msgid "" +"To implement the service discovery mechanisms, your base domain's server " +"(e.g. `example.com`) needs to run an HTTPS-capable webserver." +msgstr "" + +#: ../../../docs/configuring-well-known.md:66 +msgid "Serving the base domain from the Matrix server via the playbook" +msgstr "" + +#: ../../../docs/configuring-well-known.md:68 +msgid "" +"If you don't have a server for your base domain at all, you can use the " +"Matrix server for this. If you don't need the base domain (e.g. " +"`example.com`) for anything else (hosting a website, etc.), you can point" +" it to the Matrix server's IP address and tell the playbook to configure " +"it." +msgstr "" + +#: ../../../docs/configuring-well-known.md:70 +msgid "" +"**This is the easiest way to set up well-known serving** -- letting the " +"playbook handle the whole base domain for you (including SSL " +"certificates, etc.) and take care to serve the appropriate well-known " +"files automatically." +msgstr "" + +#: ../../../docs/configuring-well-known.md:72 +msgid "" +"If you decide to go this route, you don't need to read ahead in this " +"document. Instead, go to [Serving the base domain](configuring-playbook-" +"base-domain-serving.md) to learn how the playbook can help you set it up." +msgstr "" + +#: ../../../docs/configuring-well-known.md:74 +msgid "" +"However, if you need to use the base domain for other things, this method" +" is less suitable than the one explained below." +msgstr "" + +#: ../../../docs/configuring-well-known.md:76 +msgid "Manually installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:78 +msgid "" +"If you're managing the base domain by yourself somehow, you'll need to " +"set up serving of some `/.well-known/matrix/*` files from it via HTTPS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:80 +msgid "" +"To make things easy for you to set up, this playbook generates and hosts " +"a few well-known files on the Matrix domain's server. The files are " +"generated at the `/matrix/static-files/public/.well-known/matrix/` path " +"on the server and hosted at URLs like `https://matrix.example.com/.well-" +"known/matrix/server` and `https://matrix.example.com/.well-" +"known/matrix/client`, even though this is the wrong place to host them." +msgstr "" + +#: ../../../docs/configuring-well-known.md:82 +msgid "" +"You have two options when it comes to installing the files on the base " +"domain's server:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:84 +msgid "(Option 1): **Copying the files manually** to your base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:86 +msgid "" +"**Hint**: Option 2 is generally a better way to do this. Make sure to go " +"with it, if possible." +msgstr "" + +#: ../../../docs/configuring-well-known.md:88 +msgid "All you need to do is:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:90 +msgid "" +"copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from " +"the Matrix server (e.g. `matrix.example.com`) to your base domain's " +"server (`example.com`). You can find these files in the `/matrix/static-" +"files/.well-known/matrix` directory on the Matrix server. They are also " +"accessible on URLs like this: `https://matrix.example.com/.well-" +"known/matrix/server` (same for `client`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:92 +msgid "" +"set up the server at your base domain (e.g. `example.com`) so that it " +"adds an extra HTTP header when serving the `/.well-known/matrix/client` " +"file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the" +" `Access-Control-Allow-Origin` header should be set with a value of `*`. " +"If you don't do this step, web-based Matrix clients (like Element Web) " +"may fail to work. Setting up headers for the `/.well-known/matrix/server`" +" file is not necessary, as this file is only consumed by non-browsers, " +"which don't care about CORS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:94 +msgid "" +"This is relatively easy to do and possibly your only choice if you can " +"only host static files from the base domain's server. It is, however, **a" +" little fragile**, as future updates performed by this playbook may " +"regenerate the well-known files and you may need to notice that and copy " +"them over again." +msgstr "" + +#: ../../../docs/configuring-well-known.md:96 +msgid "" +"(Option 2): **Setting up reverse-proxying** of the well-known files from " +"the base domain's server to the Matrix server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:98 +msgid "This option is less fragile and generally better." +msgstr "" + +#: ../../../docs/configuring-well-known.md:100 +msgid "" +"On the base domain's server (e.g. `example.com`), you can set up reverse-" +"proxying, so that any access for the `/.well-known/matrix` location " +"prefix is forwarded to the Matrix domain's server (e.g. " +"`matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:102 +msgid "" +"With this method, you **don't need** to add special HTTP headers for " +"[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons " +"(like `Access-Control-Allow-Origin`), because your Matrix server (where " +"requests ultimately go) will be configured by this playbook correctly." +msgstr "" + +#: ../../../docs/configuring-well-known.md:104 +msgid "**For nginx**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:121 +msgid "**For Apache2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:135 +msgid "**For Caddy 2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:145 +msgid "**For HAProxy**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:164 +msgid "" +"**For Netlify**, configure a " +"[redirect](https://docs.netlify.com/routing/redirects/) using a " +"`_redirects` file in the [publish directory](https://docs.netlify.com" +"/configure-builds/overview/#definitions) with contents like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:170 +msgid "**For AWS CloudFront**" +msgstr "" + +#: ../../../docs/configuring-well-known.md:172 +msgid "Add a custom origin with matrix.example.com to your distribution" +msgstr "" + +#: ../../../docs/configuring-well-known.md:173 +msgid "" +"Add two behaviors, one for `.well-known/matrix/client` and one for " +"`.well-known/matrix/server` and point them to your new origin." +msgstr "" + +#: ../../../docs/configuring-well-known.md:175 +msgid "Make sure to:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:177 +msgid "" +"**replace `example.com`** in the server configuration with your actual " +"domain name" +msgstr "" + +#: ../../../docs/configuring-well-known.md:178 +msgid "" +"and: to **do this for the HTTPS-enabled server block**, as that's where " +"Matrix expects the file to be" +msgstr "" + +#: ../../../docs/configuring-well-known.md:180 +msgid "Confirming it works" +msgstr "" + +#: ../../../docs/configuring-well-known.md:182 +msgid "" +"No matter which method you've used to set up the well-known files, if " +"you've done it correctly you should be able to see a JSON file at these " +"URLs:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:184 +msgid "`https://example.com/.well-known/matrix/server`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:185 +msgid "`https://example.com/.well-known/matrix/client`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:186 +msgid "`https://example.com/.well-known/matrix/support`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:188 +msgid "" +"You can also check if everything is configured correctly, by [checking if" +" services work](maintenance-checking-services.md)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/container-images.po b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po new file mode 100644 index 000000000..388d1b52e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po @@ -0,0 +1,1314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/container-images.md:1 +msgid "Container images used by the playbook" +msgstr "" + +#: ../../../docs/container-images.md:3 +msgid "" +"This page summarizes the container ([Docker](https://www.docker.com/)) " +"images used by the playbook when setting up your server." +msgstr "" + +#: ../../../docs/container-images.md:5 +msgid "" +"We try to stick to official images (provided by their respective " +"projects) as much as possible." +msgstr "" + +#: ../../../docs/container-images.md:7 +msgid "Homeserver" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Service" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Container image" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Default?" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Description" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Synapse](configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "✅" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Conduit](configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit" +"/matrix-conduit)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "❌" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" +"source server implementation of the Matrix Specification with a focus on " +"easy setup and low system requirements" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Dendrite](configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg" +"/dendrite-monolith/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " +"Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../docs/container-images.md:15 +msgid "Clients" +msgstr "" + +#: ../../../docs/container-images.md:17 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Element Web](configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Default Matrix web client, configured to connect to your own Synapse " +"server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Cinny](configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../docs/container-images.md:26 +msgid "Server Components" +msgstr "" + +#: ../../../docs/container-images.md:28 +msgid "" +"Services that run on the server to make the various parts of your " +"installation work." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[PostgreSQL](configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[postgres](https://hub.docker.com/_/postgres/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Database for Synapse. [Using an external PostgreSQL server](configuring-" +"playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Coturn](configuring-playbook-turn.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Traefik](configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Traefik](https://hub.docker.com/_/traefik/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Web server, listening on ports 80, 443 and 8448 - standing in front of " +"all the other services. Using your own webserver [is possible" +"](configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"The [certbot](https://certbot.eff.org/) tool for obtaining SSL " +"certificates from [Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Exim](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Mail server, through which all Matrix services send outgoing email (can " +"be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ma1sd](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ddclient](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Update dynamic DNS entries for accounts on Dynamic DNS Network Service " +"Provider" +msgstr "" + +#: ../../../docs/container-images.md:40 +msgid "Authentication" +msgstr "" + +#: ../../../docs/container-images.md:42 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "(N/A)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-" +"auth.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-" +"registration-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A proxy that handles Matrix registration requests and forwards them to " +"LDAP." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-registration](configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-" +"matrix-registration/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Matrix User Verification Service](configuring-playbook-user-" +"verification-service.md) (UVS)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-user-verification-" +"service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-" +"service)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[synapse-simple-antispam](configuring-playbook-synapse-simple-" +"antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A spam checker module" +msgstr "" + +#: ../../../docs/container-images.md:54 +msgid "File Storage" +msgstr "" + +#: ../../../docs/container-images.md:56 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Goofys](configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " +"store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"matrix-media-repo is a highly customizable multi-domain media repository " +"for Matrix. Intended for medium to large deployments, this media repo de-" +"duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../docs/container-images.md:64 +msgid "Bridges" +msgstr "" + +#: ../../../docs/container-images.md:66 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-" +"messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-" +"instagram.md))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge to [Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-appservice-" +"irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-" +"kakaotalk.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Self-building" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-discord](configuring-playbook-bridge-appservice-" +"discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-" +"appservice-discord)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-appservice-" +"slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-" +"hookshot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge for generic webhooks and multiple project management services, " +"such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[folivonet/matrix-sms-" +"bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-" +"bridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to SMS" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bouncer-style bridge to " +"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-" +"bridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-" +"puppet-instagram)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-" +"twitter)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-" +"puppet/discord/mx-puppet-discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-" +"groupme)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-" +"puppet-steam)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../docs/container-images.md:99 +msgid "Bots" +msgstr "" + +#: ../../../docs/container-images.md:101 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[baibot](configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A bot that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-" +"bot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-registration-bot](configuring-playbook-bot-matrix-registration-" +"bot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-" +"registration-bot/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[maubot](configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Honoroit](configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A helpdesk bot" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Draupnir](configuring-playbook-bot-draupnir.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Buscarron](configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../docs/container-images.md:114 +msgid "Administration" +msgstr "" + +#: ../../../docs/container-images.md:116 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-alertmanager-receiver](configuring-playbook-alertmanager-" +"receiver.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio" +"/matrix-alertmanager-receiver)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " +"client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[element-hq/matrix-authentication-service](https://ghcr.io/element-hq" +"/matrix-authentication-service)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Prometheus](https://prometheus.io) time-series database server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" +"exporter/) host metrics exporter" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Graphing tool that works well with the above two images. Our playbook " +"also adds two dashboards for [Synapse](https://github.com/element-" +"hq/synapse/tree/master/contrib/grafana) and [Node " +"Exporter](https://github.com/rfrail3/grafana-dashboards)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io" +"/martin-helmich/prometheus-nginxlog-exporter/exporter)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Addon for Prometheus that gathers access logs from various nginx reverse-" +"proxies" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Borg](configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Backups" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[rageshake](configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bug report server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Export the usage statistics of a Synapse homeserver to be scraped by " +"Prometheus." +msgstr "" + +#: ../../../docs/container-images.md:131 +msgid "Misc" +msgstr "" + +#: ../../../docs/container-images.md:133 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Sliding Sync support for clients which require it (like old Element X " +"versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-" +"invite.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-" +"synapse-compress-state/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A cli tool that automatically compresses `state_groups` database table in" +" background." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-" +"corporal/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Jitsi](configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) web UI" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Focus component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Video Bridge component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[cactuscomments/cactus-" +"appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-" +"web-server)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Sygnal](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Reference Push Gateway for Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ntfy](configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Self-hosted, UnifiedPush-compatible push notifications server" +msgstr "" + +#: ../../../docs/container-images.md:152 +msgid "Container images of deprecated / unmaintained services" +msgstr "" + +#: ../../../docs/container-images.md:154 +msgid "" +"The list of the deprecated or unmaintained services is available [here" +"](configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-" +"webhooks.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live" +"/matrix-appservice-webhooks)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-" +"ci.org/), [Slack](https://slack.com/) etc. pp.)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Dimension](configuring-playbook-dimension.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-" +"dimension)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An open source integration manager for Matrix clients" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A multi functional bot written in Go" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-" +"bot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Accessing ChatGPT via your favourite Matrix client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Facebook](https://facebook.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Instagram](https://instagram.com/)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/faq.po b/i18n/locales/bg/LC_MESSAGES/docs/faq.po new file mode 100644 index 000000000..d23a642e3 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/faq.po @@ -0,0 +1,1355 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/faq.md:1 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../../../docs/faq.md:3 +msgid "" +"This documentation page tries to answer various Frequently Asked " +"Questions about all things [Matrix](https://matrix.org/), with a focus on" +" this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How" +" does it work?](#what-is-ansible-how-does-it-work))." +msgstr "" + +#: ../../../docs/faq.md:5 +msgid "" +"This FAQ page does not intend to replace the [matrix.org " +"FAQ](https://matrix.org/faq/) (please see that one too)." +msgstr "" + +#: ../../../docs/faq.md:7 +msgid "We've only started this FAQ recently, so it's still somewhat empty." +msgstr "" + +#: ../../../docs/faq.md:9 +msgid "" +"Also, we encourage you to not dig yourself into a hole by reading way too" +" much. When you've heard enough, proceed to installation. To get started," +" see [below](#how-do-i-run-the-installation) about our installation " +"guides." +msgstr "" + +#: ../../../docs/faq.md:11 +msgid "Introductory" +msgstr "" + +#: ../../../docs/faq.md:13 +msgid "Where do I find more questions and answers about Matrix?" +msgstr "" + +#: ../../../docs/faq.md:15 +msgid "" +"This is a Frequently Asked Questions page focused on this " +"[Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does " +"it work?](#what-is-ansible-how-does-it-work)) for deploying a " +"[Matrix](https://matrix.org/) server." +msgstr "" + +#: ../../../docs/faq.md:17 +msgid "" +"For a lot more generic questions and answers, see the [matrix.org " +"FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:19 +msgid "" +"What is Matrix? What is Element? What is Synapse? Why are you confusing " +"me with so many terms?" +msgstr "" + +#: ../../../docs/faq.md:21 +msgid "" +"[Matrix](https://matrix.org/) is a new type of realtime communication " +"(chat) network, the closest analogy to which is probably \"email\"." +msgstr "" + +#: ../../../docs/faq.md:23 +msgid "" +"You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly " +"though. There's a *server* somewhere which stores your data " +"(`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you" +" access it by using these \"email\" protocols via some *client* program " +"(Outlook, Thunderbird, some website, etc)." +msgstr "" + +#: ../../../docs/faq.md:25 +msgid "" +"In the world of the Matrix chat protocol, there are various client " +"programs. The first and currently most full-featured one is called " +"[Element](https://element.io/) (used to be called Riot.im and Vector.im " +"in the past). There are [many other " +"clients](https://matrix.org/clients/). You can switch clients as much as " +"you want until you find the one that is right for you on a given platform" +" (you may use Element Desktop on your desktop, but Fluffychat on your " +"phone, etc)." +msgstr "" + +#: ../../../docs/faq.md:27 +msgid "" +"Matrix is also like email due to the fact that there are many servers " +"around the world which can all talk to each other (you can send email " +"from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` " +"addresses). It's the same with Matrix (`@bob:example.com` can talk to " +"`@alice:example.org`)." +msgstr "" + +#: ../../../docs/faq.md:29 +msgid "" +"If someone else is hosting your Matrix server (you being " +"`@alice:matrix.org` or some other public server like this), all you need " +"is a Matrix client program, like Element Web or Element X Android." +msgstr "" + +#: ../../../docs/faq.md:31 +msgid "" +"If you'd like to host your own server (you being `@alice:example.com`), " +"you'd need to set up a Matrix server program, like Synapse." +msgstr "" + +#: ../../../docs/faq.md:33 +msgid "In short:" +msgstr "" + +#: ../../../docs/faq.md:35 +msgid "" +"Matrix is the protocol - a set of rules about how the chat network " +"operates" +msgstr "" + +#: ../../../docs/faq.md:36 +msgid "" +"Element is a client program you can use to participate on the Matrix chat" +" network via some server (yours or someone else's). There are also [many " +"other client programs](https://matrix.org/clients/)." +msgstr "" + +#: ../../../docs/faq.md:37 +msgid "" +"Synapse is a server program you can use to host your very own Matrix " +"server." +msgstr "" + +#: ../../../docs/faq.md:39 +msgid "" +"This FAQ here mostly focuses on installing various Matrix services using " +"the Ansible automation tool. You can learn much more about Matrix in the " +"[matrix.org FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:41 +msgid "People I wish to talk to are not on Matrix. Can I talk to them?" +msgstr "" + +#: ../../../docs/faq.md:43 +msgid "" +"You most likely can. Besides Matrix-native chats, Matrix also supports " +"the concept of \"bridging\", which allows you to plug other networks into" +" it." +msgstr "" + +#: ../../../docs/faq.md:45 +msgid "" +"This Ansible playbook can help you install [tens of bridges for various " +"networks](configuring-playbook.md#bridging-other-networks)." +msgstr "" + +#: ../../../docs/faq.md:47 +msgid "" +"Besides setting up your own bridges (preferable), you can also use some " +"[public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." +msgstr "" + +#: ../../../docs/faq.md:49 +msgid "How do I get started with Matrix?" +msgstr "" + +#: ../../../docs/faq.md:51 +msgid "" +"One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared" +" to other chat networks) is its decentralized nature. There's not just " +"one entity (company, organization) controlling the servers. Rather " +"there's thousands of servers operated by different people - one server " +"being insecure, slow or disrespective toward its users does not affect " +"the rest of the network. To participate in that decentralization in its " +"fullest, consider hosting your own server or using some public server " +"other than the largest/default one (`matrix.org`)." +msgstr "" + +#: ../../../docs/faq.md:53 +msgid "" +"There are 3 ways to get into Matrix, depending on your technical ability " +"and needs:" +msgstr "" + +#: ../../../docs/faq.md:55 +msgid "" +"**using the existing default server** - the easiest way is to use an " +"existing server. The largest public Matrix server is `matrix.org` and " +"it's configured as a default server in clients such as [Element " +"Web](https://app.element.io) and many others. Just use Element Web on the" +" browser via that link (or [download client apps for your Desktop or " +"smartphone](https://element.io/app-for-productivity)), create an account " +"and start chatting." +msgstr "" + +#: ../../../docs/faq.md:57 +msgid "" +"**using some other server** - instead of using the largest public server " +"(`matrix.org`), you can use another public one. Here's a [list of public " +"Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to " +"[Element Web](https://app.element.io) or download [some other " +"client](https://matrix.org/clients/) of your choosing and adjust the " +"homeserver URL during login." +msgstr "" + +#: ../../../docs/faq.md:59 +msgid "" +"**using your own server** - running your own server puts you in ultimate " +"control of your data. It also lets you have your own user IDs (e.g. " +"`@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i" +"-set-up-my-own-matrix-server)." +msgstr "" + +#: ../../../docs/faq.md:61 +msgid "How do I set up my own Matrix server?" +msgstr "" + +#: ../../../docs/faq.md:63 +msgid "" +"Normally, you'd first choose the [Matrix](https://matrix.org/) server " +"software you'd like to run. At the time of this writing (January/2021), " +"there's only one fully-featured server program, so there's only one " +"reasonable choice. That's [Synapse](https://github.com/element-" +"hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:65 +msgid "" +"There are [many guides about installing " +"Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this " +"Ansible playbook is just one way of doing it." +msgstr "" + +#: ../../../docs/faq.md:67 +msgid "" +"Naturally, we're biased, so our usual recommendation is to go with this " +"[Ansible](https://www.ansible.com/) playbook, instead of installing " +"Synapse (and many many other things around it) manually." +msgstr "" + +#: ../../../docs/faq.md:69 +msgid "" +"To get started with the playbook, check out the [Quick start](quick-" +"start.md) or full installation guide (starting at the " +"[Prerequisites](prerequisites.md) page)." +msgstr "" + +#: ../../../docs/faq.md:71 +msgid "What is Ansible? How does it work?" +msgstr "" + +#: ../../../docs/faq.md:73 +msgid "" +"[Ansible](https://www.ansible.com/) is an automation program. This " +"\"playbook\" is a collection of tasks/scripts that will set up a " +"[Matrix](https://matrix.org/) server for you, so you don't have to " +"perform these tasks manually." +msgstr "" + +#: ../../../docs/faq.md:75 +msgid "" +"We have written these automated tasks for you and all you need to do is " +"execute them using the Ansible program." +msgstr "" + +#: ../../../docs/faq.md:77 +msgid "" +"You can install Ansible and this playbook code repository on your own " +"computer and tell it to install Matrix services at the server living at " +"`matrix.example.com`. We recommend installing Ansible on your own " +"computer." +msgstr "" + +#: ../../../docs/faq.md:79 +msgid "" +"Alternatively, you can download Ansible and the playbook itself directly " +"on the `matrix.example.com` server." +msgstr "" + +#: ../../../docs/faq.md:81 +msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)." +msgstr "" + +#: ../../../docs/faq.md:83 +msgid "What is `just`?" +msgstr "" + +#: ../../../docs/faq.md:85 +msgid "" +"[`just`](https://github.com/casey/just) is a modern command-runner " +"alternative to [make](https://www.gnu.org/software/make/). It can be used" +" to invoke commands with less typing." +msgstr "" + +#: ../../../docs/faq.md:87 +msgid "" +"The `just` utility executes shortcut commands (called \"recipes\"), which" +" invoke `ansible-playbook`, `ansible-galaxy` or " +"[`agru`](https://github.com/etkecc/agru) (depending on what is available " +"in your system). The targets of the recipes are defined in " +"[`justfile`](../justfile)." +msgstr "" + +#: ../../../docs/faq.md:89 +msgid "" +"For details about `just` commands, take a look at: [Running `just` " +"commands](just.md)." +msgstr "" + +#: ../../../docs/faq.md:91 +msgid "" +"The playbook also contains a `Makefile` for the `make` tool, but most of " +"the just recipes are not available as targets in the `Makefile`." +msgstr "" + +#: ../../../docs/faq.md:93 +msgid "Why use this playbook and not install Synapse and other things manually?" +msgstr "" + +#: ../../../docs/faq.md:95 +msgid "" +"There are various guides telling you how easy it is to install " +"[Synapse](https://github.com/element-hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:97 +msgid "" +"Reading the documentation of this Ansible playbook, you may also be " +"thinking:" +msgstr "" + +#: ../../../docs/faq.md:99 +msgid "" +"I don't know what [Ansible](https://www.ansible.com/) is. I don't know " +"what [Docker](https://www.docker.com/) is. This looks more complicated." +msgstr "" + +#: ../../../docs/faq.md:101 +msgid "" +".. so you may be leaning toward [installing Synapse " +"manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." +msgstr "" + +#: ../../../docs/faq.md:103 +msgid "The problem with a manual installation is:" +msgstr "" + +#: ../../../docs/faq.md:105 +msgid "" +"Synapse is written in Python. If not packaged for your distribution, " +"you'd need to install various Python modules, etc., and keep them " +"updated." +msgstr "" + +#: ../../../docs/faq.md:106 +msgid "" +"Synapse requires a [Postgres](https://www.postgresql.org/) database (it " +"can run on SQLite, but that's very much discouraged). So you'd need to " +"install Postgres as well." +msgstr "" + +#: ../../../docs/faq.md:107 +msgid "" +"you may also need a reverse-proxy server in front of it (nginx, Apache), " +"so you'd need to be familiar with that" +msgstr "" + +#: ../../../docs/faq.md:108 +msgid "" +"SSL is required, so you'd need to obtain Let's Encrypt (or other free or " +"non-free) certificates for one or more domain names. You'd need to be " +"familiar with [certbot](https://certbot.eff.org/) (when using Let's " +"Encrypt) or similar software." +msgstr "" + +#: ../../../docs/faq.md:109 +msgid "" +"for each additional component you'd like to add (client like " +"[Element](https://element.io), bridge to some other chat network, " +"integration manager (stickers, other services, Identity Manager, etc.), " +"you'll need to spend extra time installing and wiring it with the rest of" +" the system in a way that works." +msgstr "" + +#: ../../../docs/faq.md:110 +msgid "" +"you'll likely get slower updates for all of these components, depending " +"on your distro packaging or your own time and ability" +msgstr "" + +#: ../../../docs/faq.md:112 +msgid "" +"The playbook, on the other hand, installs a bunch of components for you " +"by default, obtains SSL certificates for you, etc. If you'd like, you can" +" enable various bridges and other services with very little effort. All " +"the components are wired to work together." +msgstr "" + +#: ../../../docs/faq.md:114 +msgid "" +"All services run in Docker containers (most being officially provided by " +"each component's developers), so we're not at the mercy of distro " +"packaging." +msgstr "" + +#: ../../../docs/faq.md:116 +msgid "Why use this playbook and not just use the Docker image directly?" +msgstr "" + +#: ../../../docs/faq.md:118 +msgid "Reasons are similar to the reasons for not installing manually." +msgstr "" + +#: ../../../docs/faq.md:120 +msgid "" +"Besides Synapse, you'd need other things - a Postgres database, likely " +"the [Element](https://element.io) client, etc., etc." +msgstr "" + +#: ../../../docs/faq.md:122 +msgid "" +"Using the playbook, you get all these components in a way that works well" +" together out of the box." +msgstr "" + +#: ../../../docs/faq.md:124 +msgid "Occasionally I see some people are talking about \"MDAD\". What is it?" +msgstr "" + +#: ../../../docs/faq.md:126 +msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." +msgstr "" + +#: ../../../docs/faq.md:128 +msgid "" +"What's different about this Ansible playbook compared to [EMnify/matrix-" +"synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-" +"deploy)?" +msgstr "" + +#: ../../../docs/faq.md:130 +msgid "" +"This is similar to the [EMnify/matrix-synapse-auto-" +"deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible " +"deployment, but:" +msgstr "" + +#: ../../../docs/faq.md:132 +msgid "" +"this one is a complete Ansible playbook (instead of just a role), so it's" +" **easier to run** - especially for folks not familiar with Ansible" +msgstr "" + +#: ../../../docs/faq.md:134 +msgid "" +"this one installs and hooks together **a lot more Matrix-related " +"services** for you (see above)" +msgstr "" + +#: ../../../docs/faq.md:136 +msgid "this one **can be executed more than once** without causing trouble" +msgstr "" + +#: ../../../docs/faq.md:138 +msgid "" +"works on various distros: **CentOS** (7.0+), Debian-based distributions " +"(**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" +msgstr "" + +#: ../../../docs/faq.md:140 +msgid "" +"this one installs everything in a single directory (`/matrix` by default)" +" and **doesn't \"contaminate\" your server** with files all over the " +"place" +msgstr "" + +#: ../../../docs/faq.md:142 +msgid "" +"this one **doesn't necessarily take over** ports 80 and 443. By default, " +"it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but " +"you can also [use your own webserver](configuring-playbook-own-" +"webserver.md)" +msgstr "" + +#: ../../../docs/faq.md:144 +msgid "" +"this one **runs everything in Docker containers**, so it's likely more " +"predictable and less fragile (see [Docker images used by this playbook" +"](container-images.md))" +msgstr "" + +#: ../../../docs/faq.md:146 +msgid "" +"this one retrieves and automatically renews free [Let's " +"Encrypt](https://letsencrypt.org/) **SSL certificates** for you" +msgstr "" + +#: ../../../docs/faq.md:148 +msgid "" +"this one optionally can store the `media_store` content repository files " +"on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files" +" on the server's filesystem)" +msgstr "" + +#: ../../../docs/faq.md:150 +msgid "" +"this one optionally **allows you to use an external PostgreSQL server** " +"for Synapse's database (but defaults to running one in a container)" +msgstr "" + +#: ../../../docs/faq.md:152 +msgid "" +"helps you **import data from a previous installation** (so you can " +"migrate your manual virtualenv/Docker setup to a more managed one)" +msgstr "" + +#: ../../../docs/faq.md:154 +msgid "this one is actually **maintained**" +msgstr "" + +#: ../../../docs/faq.md:156 +msgid "Server-related" +msgstr "" + +#: ../../../docs/faq.md:158 +msgid "" +"What kind of server do I need to install Matrix using this Ansible " +"playbook?" +msgstr "" + +#: ../../../docs/faq.md:160 +msgid "We list our server requirements in [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/faq.md:162 +msgid "Why not run Matrix on Kubernetes?" +msgstr "" + +#: ../../../docs/faq.md:164 +msgid "" +"There's no reason not to run Matrix on " +"[Kubernetes](https://kubernetes.io/)." +msgstr "" + +#: ../../../docs/faq.md:166 +msgid "" +"However, that's overly complicated for thousands of us who just want to " +"run a single small (and sometimes not so small) Matrix server, either " +"using \"cloud\" servers or even a [Raspberry " +"Pi](https://www.raspberrypi.org/) at home." +msgstr "" + +#: ../../../docs/faq.md:168 +msgid "" +"For us, a Kubernetes-based setup which requires a cluster of multiple " +"computers and is more technically-involved is a no-go." +msgstr "" + +#: ../../../docs/faq.md:170 +msgid "" +"There are others working on automating a Matrix-on-Kubernetes setup, such" +" as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21" +"/matrix-chart." +msgstr "" + +#: ../../../docs/faq.md:172 +msgid "Why don't you use Podman instead of Docker?" +msgstr "" + +#: ../../../docs/faq.md:174 +msgid "" +"We like the philosophy of a daemonless container runtime, but " +"[Podman](https://podman.io) is just not ready for our use case yet." +msgstr "" + +#: ../../../docs/faq.md:176 +msgid "" +"Learn more about our past experiences/attempts to give Podman a chance, " +"by reading [this issue](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/issues/520)." +msgstr "" + +#: ../../../docs/faq.md:178 +msgid "In short, `alias podman=docker` is a lie (for us)." +msgstr "" + +#: ../../../docs/faq.md:180 +msgid "Why use Docker?" +msgstr "" + +#: ../../../docs/faq.md:182 +msgid "" +"[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the " +"other one being [systemd](https://systemd.io/))." +msgstr "" + +#: ../../../docs/faq.md:184 +msgid "" +"It lets us run services in an isolated manner and independently of the " +"(usually old) packages available for distributions." +msgstr "" + +#: ../../../docs/faq.md:186 +msgid "" +"It also lets us have a unified setup which runs the same across various " +"supported distros (see them on [Prerequisites](prerequisites.md))." +msgstr "" + +#: ../../../docs/faq.md:188 +msgid "Is Docker a hard requirement?" +msgstr "" + +#: ../../../docs/faq.md:190 +msgid "" +"Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-" +"podman-instead-of-docker) for why we're not using another container " +"runtime." +msgstr "" + +#: ../../../docs/faq.md:192 +msgid "" +"All of our services run in containers. It's how we achieve predictability" +" and also how we support tens of different services across lots of " +"distros." +msgstr "" + +#: ../../../docs/faq.md:194 +msgid "" +"The only thing we need on the distro is systemd and Python (we install " +"Docker ourselves, unless you ask us not to)." +msgstr "" + +#: ../../../docs/faq.md:196 +msgid "Why don't you use docker-compose?" +msgstr "" + +#: ../../../docs/faq.md:198 +msgid "" +"Instead of using [docker-compose](https://docs.docker.com/compose/), we " +"prefer installing systemd services and scheduling those independently." +msgstr "" + +#: ../../../docs/faq.md:200 +msgid "" +"There are people who have worked on turning this setup into a docker-" +"compose-based one. See these experiments " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/64#issuecomment-603164625). There is also a demo project " +"([element-docker-demo](https://github.com/element-hq/element-docker-" +"demo)) by Element." +msgstr "" + +#: ../../../docs/faq.md:202 +msgid "Can I run this on a distro without systemd?" +msgstr "" + +#: ../../../docs/faq.md:204 +msgid "" +"No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the" +" other one being [Docker](https://www.docker.com/))." +msgstr "" + +#: ../../../docs/faq.md:206 +msgid "Can I install this on a Raspberry Pi?" +msgstr "" + +#: ../../../docs/faq.md:208 +msgid "" +"Yes, you can. See our [Alternative Architectures](alternative-" +"architectures.md) documentation page." +msgstr "" + +#: ../../../docs/faq.md:210 +msgid "" +"Whether a Raspberry Pi has enough power to give you a good experience is " +"another question. It depends on your use case." +msgstr "" + +#: ../../../docs/faq.md:212 +msgid "" +"Also see: [What kind of server specs do I need?](#what-kind-of-server-" +"specs-do-i-need)." +msgstr "" + +#: ../../../docs/faq.md:214 +msgid "What kind of server specs do I need?" +msgstr "" + +#: ../../../docs/faq.md:216 +msgid "" +"This largely depends on your use case. It's not so much the number of " +"users that you plan to host, but rather the number of large rooms they " +"will join." +msgstr "" + +#: ../../../docs/faq.md:218 +msgid "" +"Federated rooms with lots of history and containing hundreds of other " +"servers are very heavy CPU-wise and memory-wise." +msgstr "" + +#: ../../../docs/faq.md:220 +msgid "" +"You can probably use a 1 CPU + 1GB memory server to host hundreds of " +"local users just fine, but as soon as one of them joins a federated room " +"like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say " +"`##linux`), your server will get the need for a lot more power (at least " +"2GB RAM, etc)." +msgstr "" + +#: ../../../docs/faq.md:222 +msgid "" +"Running Matrix on a server with 1GB of memory is possible (especially if " +"you disable some not-so-important services). See [How do I optimize this " +"setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-" +"power-server)." +msgstr "" + +#: ../../../docs/faq.md:224 +msgid "" +"**We recommend starting with a server having at least 2GB of memory** and" +" even then using it sparingly. If you know for sure you'll be joining " +"various large rooms, etc., then going for 4GB of memory or more is a good" +" idea." +msgstr "" + +#: ../../../docs/faq.md:226 +msgid "" +"Besides the regular Matrix stuff, we also support things like video-" +"conferencing using [Jitsi](configuring-playbook-jitsi.md) and other " +"additional services which (when installed) may use up a lot of memory. " +"Things do add up. Besides the Synapse Matrix server, Jitsi is especially " +"notorious for consuming a lot of resources. If you plan on running Jitsi," +" we recommend a server with at least 2GB of memory (preferrably more). " +"See our [Jitsi documentation page](configuring-playbook-jitsi.md) to " +"learn how to optimize its memory/CPU usage." +msgstr "" + +#: ../../../docs/faq.md:228 +msgid "Can I run this in an LXC container?" +msgstr "" + +#: ../../../docs/faq.md:230 +msgid "" +"If your distro runs within an [LXC " +"container](https://linuxcontainers.org/), you may hit [this " +"issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/703). It can be worked around, if absolutely necessary, but" +" we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/faq.md:232 +msgid "Configuration" +msgstr "" + +#: ../../../docs/faq.md:234 +msgid "Why install my server at matrix.example.com and not at the base domain?" +msgstr "" + +#: ../../../docs/faq.md:236 +msgid "" +"It's the same with email servers. Your email address is likely " +"`name@company.com`, not `name@mail.company.com`, even though it's " +"`mail.company.com` that is really handling your data for `@company.com` " +"email to work." +msgstr "" + +#: ../../../docs/faq.md:238 +msgid "" +"Using a separate domain name is easier to manage (although it's a little " +"hard to get right at first) and keeps your Matrix server isolated from " +"your website (if you have one), from your email server (if you have one)," +" etc. Therefore, this playbook sets up services on your Matrix server " +"(`matrix.example.com`) by default." +msgstr "" + +#: ../../../docs/faq.md:240 +msgid "" +"I don't control anything on the base domain and can't set up delegation " +"to matrix.example.com. What do I do?" +msgstr "" + +#: ../../../docs/faq.md:242 +msgid "" +"If you're not in control of your base domain (or the server handling it) " +"at all, you can take a look at [How do I install on matrix.example.com " +"without involving the base domain?](#how-do-i-install-on-" +"matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:244 +msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?" +msgstr "" + +#: ../../../docs/faq.md:246 +msgid "" +"If you really can't obtain an HTTPS certificate for your base domain, you" +" can take a look at [How do I install on matrix.example.com without " +"involving the base domain?](#how-do-i-install-on-matrixexamplecom-" +"without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:248 +msgid "How do I install on matrix.example.com without involving the base domain?" +msgstr "" + +#: ../../../docs/faq.md:250 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:271 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/faq.md:278 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/faq.md:280 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/faq.md:282 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/faq.md:284 +msgid "" +"Without setting up [server delegation](howto-server-delegation.md) to " +"`matrix.example.com`, your user IDs will be like " +"`@alice:matrix.example.com`. This is equivalent to having an email " +"address like `bob@mail.company.com`, instead of just `bob@company.com`." +msgstr "" + +#: ../../../docs/faq.md:286 +msgid "" +"I don't use the base domain for anything. How am I supposed to set up " +"Server Delegation for Matrix services?" +msgstr "" + +#: ../../../docs/faq.md:288 +msgid "" +"If you don't use your base domain for anything, then it's hard for you to" +" \"serve files over HTTPS\" on it -- something we ask you to do for the " +"[.well-known](configuring-well-known.md) setup (needed for [Server " +"Delegation](howto-server-delegation.md))." +msgstr "" + +#: ../../../docs/faq.md:290 +msgid "" +"Luckily, the playbook can set up your Matrix server (at " +"`matrix.example.com`) to also handle traffic for the base domain " +"(`example.com`)." +msgstr "" + +#: ../../../docs/faq.md:292 +msgid "" +"See [Serving the base domain](configuring-playbook-base-domain-" +"serving.md)." +msgstr "" + +#: ../../../docs/faq.md:294 +msgid "How do I optimize this setup for a low-power server?" +msgstr "" + +#: ../../../docs/faq.md:296 +msgid "You can disable some not-so-important services to save on memory." +msgstr "" + +#: ../../../docs/faq.md:318 +msgid "" +"You can also consider implementing a restriction on room complexity, in " +"order to prevent users from joining very heavy rooms:" +msgstr "" + +#: ../../../docs/faq.md:328 +msgid "" +"If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed" +" by default), there are additional optimizations listed on its " +"documentation page that you can perform." +msgstr "" + +#: ../../../docs/faq.md:330 +msgid "" +"I already have Docker on my server. Can you stop installing Docker via " +"the playbook?" +msgstr "" + +#: ../../../docs/faq.md:332 +msgid "" +"Yes, we can stop installing Docker ourselves. Just use this in your " +"`vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:338 +msgid "" +"I run another webserver on the same server where I wish to install " +"Matrix. What now?" +msgstr "" + +#: ../../../docs/faq.md:340 +msgid "" +"By default, we install a webserver for you " +"([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your " +"own webserver](configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../docs/faq.md:342 +msgid "How is the effective configuration determined?" +msgstr "" + +#: ../../../docs/faq.md:344 +msgid "" +"Configuration variables are defined in multiple places in this playbook " +"and are considered in this order:" +msgstr "" + +#: ../../../docs/faq.md:346 +msgid "" +"there are defaults coming from each role's defaults file " +"(`role/matrix*/defaults/main.yml`). These variable values aim to be good " +"defaults for when the role is used standalone (outside of this collection" +" of roles, also called playbook)." +msgstr "" + +#: ../../../docs/faq.md:348 +msgid "" +"then, there are overrides in `group_vars/matrix_servers`, which aim to " +"adjust these \"standalone role defaults\" to something which better fits " +"the playbook in its entirety." +msgstr "" + +#: ../../../docs/faq.md:350 +msgid "" +"finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` " +"file, which is the ultimate override" +msgstr "" + +#: ../../../docs/faq.md:352 +msgid "What configuration variables are available?" +msgstr "" + +#: ../../../docs/faq.md:354 +msgid "" +"You can discover the variables you can override in each role " +"(`roles/*/*/defaults/main.yml`)." +msgstr "" + +#: ../../../docs/faq.md:356 +msgid "" +"As described in [How is the effective configuration determined?](#how-is-" +"the-effective-configuration-determined), these role-defaults may be " +"overriden by values defined in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/faq.md:358 +msgid "" +"Refer to both of these for inspiration. Still, as mentioned in " +"[Configuring the playbook](configuring-playbook.md), you're only ever " +"supposed to edit your own " +"`inventory/host_vars/matrix.example.com/vars.yml` file and nothing else " +"inside the playbook (unless you're meaning to contribute new features)." +msgstr "" + +#: ../../../docs/faq.md:360 ../../../docs/faq.md:372 +msgid "" +"**Note**: some of the roles (`roles/galaxy/*`) live in separate " +"repositories and are only installed after your run `just roles` (or `make" +" roles`) or `just update` (which automatically does `git pull` and `just " +"roles`)." +msgstr "" + +#: ../../../docs/faq.md:362 +msgid "" +"I'd like to adjust some configuration which doesn't have a corresponding " +"variable. How do I do it?" +msgstr "" + +#: ../../../docs/faq.md:364 +msgid "" +"The playbook doesn't aim to expose all configuration settings for all " +"services using variables. Doing so would amount to hundreds of variables " +"that we have to create and maintain." +msgstr "" + +#: ../../../docs/faq.md:366 +msgid "" +"Instead, we only try to make some important basics configurable using " +"dedicated variables you can see in each role. See [What configuration " +"variables are available?](#what-configuration-variables-are-available)." +msgstr "" + +#: ../../../docs/faq.md:368 +msgid "" +"Besides that, each role (component) aims to provide a " +"`matrix_SOME_COMPONENT_configuration_extension_yaml` (or " +"`matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can" +" be used to override the configuration." +msgstr "" + +#: ../../../docs/faq.md:370 +msgid "" +"Check each role's `roles/*/*/defaults/main.yml` for the corresponding " +"variable and an example for how use it." +msgstr "" + +#: ../../../docs/faq.md:374 +msgid "Installation" +msgstr "" + +#: ../../../docs/faq.md:376 +msgid "How do I run the installation?" +msgstr "" + +#: ../../../docs/faq.md:378 +msgid "" +"See [Installing](installing.md) to learn how to use Ansible to install " +"Matrix services." +msgstr "" + +#: ../../../docs/faq.md:380 +msgid "" +"However, we recommend you to follow our installation guide, instead of " +"jumping straight to installing." +msgstr "" + +#: ../../../docs/faq.md:382 +msgid "There are two guides available:" +msgstr "" + +#: ../../../docs/faq.md:384 +msgid "" +"⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended " +"for those who do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/faq.md:386 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide by starting with the " +"**[Prerequisites](prerequisites.md)** documentation page." +msgstr "" + +#: ../../../docs/faq.md:388 +msgid "" +"I installed Synapse some other way. Can I migrate such a setup to the " +"playbook?" +msgstr "" + +#: ../../../docs/faq.md:390 +msgid "Yes, you can." +msgstr "" + +#: ../../../docs/faq.md:392 +msgid "" +"You generally need to do a playbook installation. It's recommended to " +"follow the full installation guide (starting at the " +"[Prerequisites](prerequisites.md) page), not the [Quick start](quick-" +"start.md) guide. The full installation guide will tell you when it's time" +" to import your existing data into the newly-prepared server." +msgstr "" + +#: ../../../docs/faq.md:394 +msgid "" +"This Ansible playbook guides you into installing a server for " +"`example.com` (user IDs are like this: `@alice:example.com`), while the " +"server is at `matrix.example.com`. If your existing setup has a server " +"name (`server_name` configuration setting in Synapse's `homeserver.yaml` " +"file) other than the base `example.com`, you may need to tweak some " +"additional variables. This FAQ entry may be of use if you're dealing with" +" a more complicated setup - [How do I install on matrix.example.com " +"without involving the base domain?](#how-do-i-install-on-" +"matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:396 +msgid "" +"After configuring the playbook and installing and **before starting** " +"services (done with `ansible-playbook … --tags=start`) you'd import [your" +" SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-" +"postgres.md)) database and also [import your media store](importing-" +"synapse-media-store.md)." +msgstr "" + +#: ../../../docs/faq.md:398 +msgid "" +"I've downloaded Ansible and the playbook on the server. It can't connect " +"using SSH." +msgstr "" + +#: ../../../docs/faq.md:400 +msgid "" +"If you're using the playbook directly on the server, then Ansible doesn't" +" need to connect using SSH." +msgstr "" + +#: ../../../docs/faq.md:402 +msgid "" +"It can perform a local connection instead. Just set " +"`ansible_connection=local` at the end of the server line in " +"`inventory/hosts` and re-run the playbook." +msgstr "" + +#: ../../../docs/faq.md:404 +msgid "" +"If you're running Ansible from within a container (one of the " +"possibilities we list on our [dedicated Ansible documentation " +"page](ansible.md)), then using `ansible_connection=local` is not " +"possible." +msgstr "" + +#: ../../../docs/faq.md:406 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/faq.md:408 +msgid "" +"I get \"Error response from daemon: configured logging driver does not " +"support reading\" when I do `docker logs matrix-synapse`." +msgstr "" + +#: ../../../docs/faq.md:410 +msgid "See [How can I see the logs?](#how-can-i-see-the-logs)." +msgstr "" + +#: ../../../docs/faq.md:412 +msgid "How can I see the logs?" +msgstr "" + +#: ../../../docs/faq.md:414 +msgid "" +"We utilize " +"[systemd/journald](https://www.freedesktop.org/software/systemd/man" +"/systemd-journald.service.html#Description) for logging." +msgstr "" + +#: ../../../docs/faq.md:416 +msgid "" +"To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You" +" may wish to see the [manual page for " +"journalctl](https://www.commandlinux.com/man-" +"page/man1/journalctl.1.html)." +msgstr "" + +#: ../../../docs/faq.md:418 +msgid "" +"Available service names can be seen by doing `ls " +"/etc/systemd/system/matrix*.service` on the server." +msgstr "" + +#: ../../../docs/faq.md:420 +msgid "" +"Some services also log to files in `/matrix/*/data/..`, but we're slowly " +"moving away from that." +msgstr "" + +#: ../../../docs/faq.md:422 +msgid "" +"We also disable Docker logging, so you can't use `docker logs matrix-*` " +"either. We do this to prevent useless double (or even triple) logging and" +" to avoid having to rotate log files." +msgstr "" + +#: ../../../docs/faq.md:424 +msgid "" +"We just simply delegate logging to journald and it takes care of " +"persistence and expiring old data." +msgstr "" + +#: ../../../docs/faq.md:426 +msgid "" +"Also see: [How long do systemd/journald logs persist for?](#how-long-do-" +"systemdjournald-logs-persist-for)" +msgstr "" + +#: ../../../docs/faq.md:428 +msgid "How long do systemd/journald logs persist for?" +msgstr "" + +#: ../../../docs/faq.md:430 +msgid "" +"On some distros, the journald logs are just in-memory and not persisted " +"to disk." +msgstr "" + +#: ../../../docs/faq.md:432 +msgid "" +"Consult (and feel free to adjust) your distro's journald logging " +"configuration in `/etc/systemd/journald.conf`." +msgstr "" + +#: ../../../docs/faq.md:434 +msgid "" +"To enable persistence and put some limits on how large the journal log " +"files can become, adjust your configuration like this:" +msgstr "" + +#: ../../../docs/faq.md:445 +msgid "Maintenance" +msgstr "" + +#: ../../../docs/faq.md:447 +msgid "Do I need to do anything to keep my Matrix server updated?" +msgstr "" + +#: ../../../docs/faq.md:449 +msgid "Yes. We don't update anything for you automatically." +msgstr "" + +#: ../../../docs/faq.md:451 +msgid "" +"See our [documentation page about upgrading services](maintenance-" +"upgrading-services.md)." +msgstr "" + +#: ../../../docs/faq.md:453 +msgid "How do I move my existing installation to another (VM) server?" +msgstr "" + +#: ../../../docs/faq.md:455 +msgid "" +"If you have an existing installation done using this Ansible playbook, " +"you can easily migrate that to another server using [our dedicated server" +" migration guide](maintenance-migrating.md)." +msgstr "" + +#: ../../../docs/faq.md:457 +msgid "" +"If your previous installation is done in some other way (not using this " +"Ansible playbook), see [I installed Synapse some other way. Can I migrate" +" such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i" +"-migrate-such-a-setup-to-the-playbook)." +msgstr "" + +#: ../../../docs/faq.md:459 +msgid "How do I back up the data on my server?" +msgstr "" + +#: ../../../docs/faq.md:461 +msgid "We haven't documented this properly yet, but the general advice is to:" +msgstr "" + +#: ../../../docs/faq.md:463 +msgid "" +"back up Postgres by making a database dump. See [Backing up PostgreSQL" +"](maintenance-postgres.md#backing-up-postgresql)" +msgstr "" + +#: ../../../docs/faq.md:465 +msgid "" +"back up all `/matrix` files, except for `/matrix/postgres/data` (you " +"already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` " +"(this directory may exist and contain your old data if you've [performed " +"a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +msgstr "" + +#: ../../../docs/faq.md:467 +msgid "You can later restore these by:" +msgstr "" + +#: ../../../docs/faq.md:469 +msgid "Restoring the `/matrix` directory and files on the new server manually" +msgstr "" + +#: ../../../docs/faq.md:470 +msgid "" +"Following the instruction described on [Installing a server into which " +"you'll import old data](installing.md#installing-a-server-into-which-" +"youll-import-old-data)" +msgstr "" + +#: ../../../docs/faq.md:472 +msgid "" +"If your server's IP address has changed, you may need to [set up DNS" +"](configuring-dns.md) again." +msgstr "" + +#: ../../../docs/faq.md:474 +msgid "" +"What is this `/matrix/postgres/data-auto-upgrade-backup` directory that " +"is taking up so much space?" +msgstr "" + +#: ../../../docs/faq.md:476 +msgid "" +"When you [perform a major Postgres upgrade](maintenance-postgres.md" +"#upgrading-postgresql), we save the the old data files in " +"`/matrix/postgres/data-auto-upgrade-backup`, just so you could easily " +"restore them should something have gone wrong." +msgstr "" + +#: ../../../docs/faq.md:478 +msgid "" +"After verifying that everything still works after the Postgres upgrade, " +"you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +msgstr "" + +#: ../../../docs/faq.md:480 +msgid "How do I debug or force SSL certificate renewal?" +msgstr "" + +#: ../../../docs/faq.md:482 +msgid "" +"SSL certificates are managed automatically by the " +"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." +msgstr "" + +#: ../../../docs/faq.md:484 +msgid "" +"If you're having trouble with SSL certificate renewal, check the Traefik " +"logs (`journalctl -fu matrix-traefik`)." +msgstr "" + +#: ../../../docs/faq.md:486 +msgid "" +"If you're [using your own webserver](configuring-playbook-own-" +"webserver.md) instead of the integrated one (Traefik), you should " +"investigate in another way." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po new file mode 100644 index 000000000..cb1767774 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po @@ -0,0 +1,119 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/getting-the-playbook.md:1 +msgid "Getting the playbook" +msgstr "" + +#: ../../../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:5 +msgid "" +"This Ansible playbook is meant to be executed on your own computer (not " +"the Matrix server)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:7 +msgid "" +"In special cases (if your computer cannot run Ansible, etc.) you may put " +"the playbook on the server as well." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:9 +msgid "You can retrieve the playbook's source code by:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:11 +msgid "" +"[Using git to get the playbook](#using-git-to-get-the-playbook) " +"(recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:13 +msgid "" +"[Downloading the playbook as a ZIP archive](#downloading-the-playbook-" +"as-a-zip-archive) (not recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:15 +msgid "Using git to get the playbook" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:17 +msgid "" +"We recommend using the [git](https://git-scm.com/) tool to get the " +"playbook's source code, because it lets you easily keep up to date in the" +" future when [Maintaining services](maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:19 +msgid "" +"Once you've installed git on your computer, you can go to any directory " +"of your choosing and run the following command to retrieve the playbook's" +" source code:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:25 +msgid "" +"This will create a new `matrix-docker-ansible-deploy` directory. You're " +"supposed to execute all other installation commands inside that " +"directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:27 +msgid "Downloading the playbook as a ZIP archive" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:29 +msgid "" +"Alternatively, you can download the playbook as a ZIP archive. This is " +"not recommended, as it's not easy to keep up to date with future updates." +" We suggest you [use git](#using-git-to-get-the-playbook) instead." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:31 +msgid "" +"The latest version is always at the following URL: " +"https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/archive/master.zip" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:33 +msgid "" +"You can extract this archive anywhere. You'll get a directory called " +"`matrix-docker-ansible-deploy-master`. You're supposed to execute all " +"other installation commands inside that directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:37 +msgid "" +"[▶️](configuring-playbook.md) No matter which method you've used to " +"download the playbook, you can proceed by [Configuring the playbook" +"](configuring-playbook.md)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po new file mode 100644 index 000000000..4781be83b --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po @@ -0,0 +1,301 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/howto-server-delegation.md:1 +msgid "Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:3 +msgid "" +"By default, this playbook sets up services on your Matrix server " +"(`matrix.example.com`). To have this server officially be responsible for" +" Matrix services for the base domain (`example.com`), you need to set up " +"server delegation / redirection." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:5 +msgid "Server delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:7 +msgid "" +"[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a" +"-well-known-file) on the base domain (`example.com`)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:8 +msgid "" +"[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a" +"-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:10 +msgid "" +"Both methods have their place and will continue to do so. You only need " +"to use just one of these delegation methods." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:12 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file. However, that method " +"may have some downsides that are not to your liking. Hence this guide " +"about alternative ways to set up Server Delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:14 +msgid "" +"**Note**: as an alternative, it is possible to install the server such " +"that it uses only the `matrix.example.com` domain (instead of identifying" +" as the shorter base domain - `example.com`). This should be helpful if " +"you are not in control of anything on the base domain (`example.com`). In" +" this case, you would not need to configure server delegation, but you " +"would need to add other configuration. For more information, see [How do " +"I install on matrix.example.com without involving the base " +"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" +"the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:16 +msgid "Server Delegation via a well-known file" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:18 +msgid "" +"This playbook recommends you to set up server delegation by means of a " +"`/.well-known/matrix/server` file served from the base domain " +"(`example.com`), as this is the most straightforward way to set up the " +"delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:20 +msgid "" +"To configure server delegation with the well-known file, check this " +"section on [Configuring Service Discovery via .well-known](configuring-" +"well-known.md): [Installing well-known files on the base domain's server" +"](configuring-well-known.md#installing-well-known-files-on-the-base-" +"domain-s-server)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:22 +msgid "Downsides of well-known-based Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:24 +msgid "" +"Server Delegation by means of a `/.well-known/matrix/server` file is the " +"most straightforward, but suffers from the following downsides:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:26 +msgid "" +"you need to have a working HTTPS server for the base domain " +"(`example.com`). If you don't have any server for the base domain at all," +" you can easily solve it by making the playbook [serve the base domain " +"from the Matrix server](configuring-playbook-base-domain-serving.md)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:28 +msgid "" +"any downtime on the base domain (`example.com`) or network trouble " +"between the Matrix subdomain (`matrix.example.com`) and the base " +"`example.com` may cause Matrix Federation outages. As the [Server-Server " +"spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" +"discovery):" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:30 +msgid "" +"Errors are recommended to be cached for up to an hour, and servers are " +"encouraged to exponentially back off for repeated failures." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:32 +msgid "" +"**For most people, this is a reasonable tradeoff** given that it's easy " +"and straightforward to set up. We recommend you stay on this path." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:34 +msgid "" +"Otherwise, you can decide to go against the default for this playbook, " +"and instead set up [Server Delegation via a DNS SRV record (advanced" +")](#server-delegation-via-a-dns-srv-record-advanced) (much more " +"complicated)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:36 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:38 +msgid "" +"**Note**: doing Server Delegation via a DNS SRV record is a more " +"**advanced** way to do it and is not the default for this playbook. This " +"is usually **much more complicated** to set up, so **we don't recommend " +"it**. If you're not an experienced sysadmin, you'd better stay away from " +"this." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:40 +msgid "" +"As per the [Server-Server " +"spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" +"discovery), it's possible to do Server Delegation using only a SRV record" +" (without a `/.well-known/matrix/server` file)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:42 +msgid "" +"This prevents you from suffering the [Downsides of well-known-based " +"Server Delegation](#downsides-of-well-known-based-server-delegation)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:44 +msgid "To use DNS SRV record validation, you need to:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:46 +msgid "" +"ensure that `/.well-known/matrix/server` is **not served** from the base " +"domain, as that would interfere with DNS SRV record Server Delegation. To" +" make the playbook **not** generate and serve the file, use the following" +" configuration: `matrix_static_files_file_matrix_server_enabled: false`." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:48 +msgid "" +"ensure that you have a `_matrix._tcp` DNS SRV record for your base domain" +" (`example.com`) with a value of `10 0 8448 matrix.example.com`" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:50 +msgid "" +"ensure that you are serving the Matrix Federation API (tcp/8448) with a " +"certificate for `example.com` (not `matrix.example.com`!). Getting this " +"certificate to the `matrix.example.com` server may be complicated. The " +"playbook's automatic SSL obtaining/renewal flow will likely not work and " +"you'll need to copy certificates around manually. See below." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:52 +msgid "" +"For more details on how to configure the playbook to work with SRV " +"delegation, take a look at this documentation: [Server Delegation via a " +"DNS SRV record (advanced)](howto-srv-server-delegation.md)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:54 +msgid "Obtaining certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:56 +msgid "" +"How you can obtain a valid certificate for `example.com` on the " +"`matrix.example.com` server is up to you." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:58 +msgid "" +"If `example.com` and `matrix.example.com` are hosted on the same machine," +" you can let the playbook obtain the certificate for you, by following " +"our [Obtaining SSL certificates for additional domains](configuring-" +"playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-" +"domains) guide." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:60 +msgid "" +"If `example.com` and `matrix.example.com` are not hosted on the same " +"machine, you can copy over the certificate files manually. Don't forget " +"that they may get renewed once in a while, so you may also have to " +"transfer them periodically. How often you do that is up to you, as long " +"as the certificate files don't expire." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:62 +msgid "Serving the Federation API with your certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:64 +msgid "" +"Regardless of which method for obtaining certificates you've used, once " +"you've managed to get certificates for your base domain onto the " +"`matrix.example.com` machine you can put them to use." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:66 +msgid "Based on your setup, you have different ways to go about it:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:68 +msgid "" +"Serving the Federation API with your certificates and Synapse handling " +"Federation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:70 +msgid "You can let Synapse handle Federation by itself." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:72 +msgid "" +"To do that, make sure the certificate files are mounted into the Synapse " +"container:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:79 +msgid "" +"You can then tell Synapse to serve Federation traffic over TLS on " +"`tcp/8448`:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:87 +msgid "" +"Make sure to reload Synapse once in a while (`systemctl reload matrix-" +"synapse`), so that newer certificates can kick in. Reloading doesn't " +"cause any downtime." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:89 +msgid "Serving the Federation API with your certificates and another webserver" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:91 +msgid "" +"**Alternatively**, if you are using another webserver, you can set up " +"reverse-proxying for the `tcp/8448` port by yourself. Make sure to use " +"the proper certificates for `example.com` (not for `matrix.example.com`) " +"when serving the `tcp/8448` port." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:93 +msgid "" +"As recommended in our [Fronting the integrated reverse-proxy webserver " +"with another reverse-proxy](./configuring-playbook-own-webserver.md" +"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy) documentation section, we recommend you to expose the Matrix " +"Federation entrypoint from traffic at a local port (e.g. " +"`127.0.0.1:8449`), so your reverese-proxy should send traffic there." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po new file mode 100644 index 000000000..9143db321 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po @@ -0,0 +1,219 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/howto-srv-server-delegation.md:1 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:3 +msgid "" +"**Reminder** : unless you are affected by the [Downsides of well-known-" +"based Server Delegation](howto-server-delegation.md#downsides-of-well-" +"known-based-server-delegation), we suggest you **stay on the " +"simple/default path**: [Server Delegation](howto-server-delegation.md) by" +" [configuring well-known files](configuring-well-known.md) at the base " +"domain." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:5 +msgid "" +"This guide is about configuring Server Delegation using DNS SRV records " +"(for the [Traefik](https://doc.traefik.io/traefik/) webserver). This " +"method has special requirements when it comes to SSL certificates, so " +"various changes are required." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:9 +msgid "" +"SRV delegation while still using the playbook provided Traefik to get / " +"renew the certificate requires a wildcard certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:11 +msgid "" +"To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one" +" needs to use a [DNS-01 challenge](https://letsencrypt.org/docs" +"/challenge-types/#dns-01-challenge) method instead of the default " +"[HTTP-01](https://letsencrypt.org/docs/challenge-" +"types/#http-01-challenge)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:13 +msgid "" +"This means that this is **limited to the list of DNS providers supported " +"by Traefik**, unless you bring in your own certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:15 +msgid "" +"The up-to-date list can be accessed on [traefik's " +"documentation](https://doc.traefik.io/traefik/https/acme/#providers)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:17 +msgid "The changes" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:19 +msgid "" +"**Note**: the changes below instruct you how to do this for a basic " +"Synapse installation. You will need to adapt the variable name and the " +"content of the labels:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:21 +msgid "" +"if you're using another homeserver implementation (e.g. [Conduit" +"](./configuring-playbook-conduit.md) or [Dendrite](./configuring-" +"playbook-dendrite.md))" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:22 +msgid "" +"if you're using [Synapse with workers enabled](./configuring-playbook-" +"synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled:" +" true`). In that case, it's actually the `matrix-synapse-reverse-proxy-" +"companion` service which has Traefik labels attached" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:24 +msgid "" +"Also, all instructions below are from an older version of the playbook " +"and may not work anymore." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:26 +msgid "Federation Endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:33 +msgid "" +"This is because with SRV federation, some servers / tools (one of which " +"being the federation tester) try to access the federation API using the " +"resolved IP address instead of the domain name (or they are not using " +"SNI). This change will make Traefik route all traffic for which the path " +"match this rule go to the federation endpoint." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:35 +msgid "Tell Traefik which certificate to serve for the federation endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:37 +msgid "" +"Now that the federation endpoint is not bound to a domain anymore we need" +" to explicitely tell Traefik to use a wildcard certificate in addition to" +" one containing the base name." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:39 +msgid "" +"This is because the Matrix specification expects the federation endpoint " +"to be served using a certificate compatible with the base domain, " +"however, the other resources on the endpoint still need a valid " +"certificate to work." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:48 +msgid "Configure the DNS-01 challenge for let's encrypt" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:50 +msgid "" +"Since we're now requesting a wildcard certificate, we need to change the " +"ACME challenge method. To request a wildcard certificate from Let's " +"Encrypt we are required to use the DNS-01 challenge." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:52 +msgid "This will need 3 changes:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:53 +msgid "Add a new certificate resolver that works with DNS-01" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:54 +msgid "" +"Configure the resolver to allow access to the DNS zone to configure the " +"records to answer the challenge (refer to [Traefik's " +"documentation](https://doc.traefik.io/traefik/https/acme/#providers) to " +"know which environment variables to set)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:55 +msgid "Tell the playbook to use the new resolver as default" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:57 +msgid "" +"We cannot just disable the default resolver as that would disable SSL in " +"quite a few places in the playbook." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:86 +msgid "Adjust Coturn's configuration" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:88 +msgid "The last step is to alter the generated Coturn configuration." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:90 +msgid "" +"By default, Coturn is configured to wait on the certificate for the " +"`matrix.` subdomain using an [instantiated systemd " +"service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates)" +" using the domain name as the parameter for this service. However, we " +"need to serve the wildcard certificate, which is incompatible with " +"systemd, it will try to expand the `*`, which will break and prevent " +"Coturn from starting." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:92 +msgid "We also need to indicate to Coturn where the wildcard certificate is." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:94 +msgid "" +"**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still " +"fail to start because Traefik is still in the process of obtaining the " +"certificates. If you still get an error, make sure Traefik obtained the " +"certificates and restart the Coturn service (`just start-group coturn`)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:96 +msgid "" +"This should not happen again afterwards as Traefik will renew " +"certificates well before their expiry date, and the Coturn service is " +"setup to restart periodically." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:122 +msgid "Full example of a working configuration" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po new file mode 100644 index 000000000..710e0a74c --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po @@ -0,0 +1,214 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/importing-postgres.md:1 +msgid "" +"Importing an existing Postgres database from another installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-postgres.md:3 +msgid "" +"Run this if you'd like to import your database from a previous " +"installation. (don't forget to import your Synapse `media_store` files as" +" well - see [the importing-synape-media-store guide](importing-synapse-" +"media-store.md))." +msgstr "" + +#: ../../../docs/importing-postgres.md:6 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-postgres.md:8 +msgid "" +"For this to work, **the database name in Postgres must match** what this " +"playbook uses. This playbook uses a Postgres database name of `synapse` " +"by default (controlled by the `matrix_synapse_database_database` " +"variable). If your database name differs, be sure to change " +"`matrix_synapse_database_database` to your desired name and to re-run the" +" playbook before proceeding." +msgstr "" + +#: ../../../docs/importing-postgres.md:10 +msgid "" +"The playbook supports importing Postgres dump files in **text** (e.g. " +"`pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > " +"dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) " +"is also supported." +msgstr "" + +#: ../../../docs/importing-postgres.md:12 +msgid "" +"The migration might be a good moment, to \"reset\" a not properly working" +" bridge. Be aware, that it might affect all users (new link to bridge, " +"new rooms, …)" +msgstr "" + +#: ../../../docs/importing-postgres.md:14 +msgid "" +"Before doing the actual import, **you need to upload your Postgres dump " +"file to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-postgres.md:16 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-postgres.md:18 +msgid "" +"To import, run this command (make sure to replace " +"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-postgres.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/importing-postgres.md:28 +msgid "" +"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres " +"dump file on the server (not on your local machine!)" +msgstr "" + +#: ../../../docs/importing-postgres.md:29 +msgid "" +"`postgres_default_import_database` defaults to `matrix`, which is useful " +"for importing multiple databases (for dumps made with `pg_dumpall`). If " +"you're importing a single database (e.g. `synapse`), consider changing " +"`postgres_default_import_database` accordingly" +msgstr "" + +#: ../../../docs/importing-postgres.md:30 +msgid "" +"after importing a large database, it's a good idea to run [an `ANALYZE` " +"operation](https://www.postgresql.org/docs/current/sql-analyze.html) to " +"make Postgres rebuild its database statistics and optimize its query " +"planner. You can easily do this via the playbook by running `just run-" +"tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see " +"[Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for " +"more details)." +msgstr "" + +#: ../../../docs/importing-postgres.md:32 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/importing-postgres.md:34 +msgid "Table Ownership" +msgstr "" + +#: ../../../docs/importing-postgres.md:36 +msgid "" +"A table ownership issue can occur if you are importing from a Synapse " +"installation which was both:" +msgstr "" + +#: ../../../docs/importing-postgres.md:38 +msgid "migrated from SQLite to Postgres, and" +msgstr "" + +#: ../../../docs/importing-postgres.md:39 +msgid "used a username other than 'synapse'" +msgstr "" + +#: ../../../docs/importing-postgres.md:41 +msgid "In this case you may run into the following error during the import task:" +msgstr "" + +#: ../../../docs/importing-postgres.md:47 +msgid "" +"where `synapse_user` is the database username from the previous Synapse " +"installation." +msgstr "" + +#: ../../../docs/importing-postgres.md:49 +msgid "" +"This can be verified by examining the dump for ALTER TABLE statements " +"which set OWNER TO that username:" +msgstr "" + +#: ../../../docs/importing-postgres.md:61 +msgid "" +"It can be worked around by changing the username to `synapse`, for " +"example by using `sed`:" +msgstr "" + +#: ../../../docs/importing-postgres.md:67 +msgid "" +"This uses sed to perform an 'in-place' (`-i`) replacement globally " +"(`/g`), searching for `synapse_user` and replacing with `synapse` " +"(`s/synapse_user/synapse`). If your database username was different, " +"change `synapse_user` to that username instead. Expand search/replace " +"statement as shown in example above, in case of old user name like " +"`matrix` - replacing `matrix` only would… well - you can imagine." +msgstr "" + +#: ../../../docs/importing-postgres.md:69 +msgid "" +"Note that if the previous import failed with an error it may have made " +"changes which are incompatible with re-running the import task right " +"away; if you do so it may fail with an error such as:" +msgstr "" + +#: ../../../docs/importing-postgres.md:75 +msgid "Repeat import" +msgstr "" + +#: ../../../docs/importing-postgres.md:77 +msgid "" +"In this case you can use the command suggested in the import task to " +"clear the database before retrying the import:" +msgstr "" + +#: ../../../docs/importing-postgres.md:85 +msgid "" +"Now on your local machine run `just run-tags setup-postgres` to prepare " +"the database roles etc." +msgstr "" + +#: ../../../docs/importing-postgres.md:87 +msgid "" +"If not, you probably get this error. `synapse` is the correct table " +"owner, but the role is missing in database." +msgstr "" + +#: ../../../docs/importing-postgres.md:93 +msgid "" +"Once the database is clear and the ownership of the tables has been fixed" +" in the SQL file, the import task should succeed." +msgstr "" + +#: ../../../docs/importing-postgres.md:95 +msgid "" +"Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths" +" (or even better, copy this line from your terminal)" +msgstr "" + +#: ../../../docs/importing-postgres.md:101 +msgid "Hints" +msgstr "" + +#: ../../../docs/importing-postgres.md:103 +msgid "To open psql terminal run `/matrix/postgres/bin/cli`" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po new file mode 100644 index 000000000..ee4c523bf --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po @@ -0,0 +1,86 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/importing-synapse-media-store.md:1 +msgid "" +"Importing `media_store` data files from an existing Synapse installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:3 +msgid "" +"Run this if you'd like to import your `media_store` files from a previous" +" installation of Synapse." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:5 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:7 +msgid "" +"Before doing the actual data restore, **you need to upload your media " +"store directory to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:9 +msgid "" +"If you are [storing Matrix media files on Amazon S3](configuring-" +"playbook-s3.md) (optional), restoring with this tool is not possible " +"right now." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:11 +msgid "" +"As an alternative, you can perform a manual restore using the [AWS CLI " +"tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync " +"/path/to/server/media_store/. s3://name-of-bucket/`)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:13 +msgid "" +"**Note for Mac users**: Due to case-sensitivity issues on certain Mac " +"filesystems (HFS or HFS+), filename corruption may occur if you copy a " +"`media_store` directory to your Mac. If you're transferring a " +"`media_store` directory between 2 servers, make sure you do it directly " +"(from server to server with a tool such as " +"[rsync](https://rsync.samba.org/)), and not by downloading the files to " +"your Mac." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:15 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:17 +msgid "" +"Run this command (make sure to replace `` " +"with a path on your server):" +msgstr "" + +#: ../../../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 new file mode 100644 index 000000000..3f6d09b6a --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -0,0 +1,108 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/importing-synapse-sqlite.md:1 +msgid "" +"Importing an existing SQLite database from another Synapse installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:3 +msgid "" +"Run this if you'd like to import your database from a previous default " +"installation of Synapse (don't forget to import your `media_store` files " +"as well - see [the importing-synapse-media-store guide](importing-" +"synapse-media-store.md))." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:5 +msgid "" +"While this playbook only supports running Synapse in combination with " +"PostgreSQL, a Synapse instance installed manually usually defaults to " +"using an SQLite database." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:7 +msgid "" +"If you have such a Synapse setup and wish to migrate it to one managed by" +" the playbook (and over to PostgreSQL), this documentation page is for " +"you." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:11 +msgid "Before doing the actual import:" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:13 +msgid "" +"**ensure you have NOT started Synapse yet**. That is, make sure you have " +"followed the [Installing step](installing.md), but haven't run the " +"playbook's `start` tag yet. If you had started your new Synapse instance," +" it may have already initialized your Postgres database and importing " +"onto it may not work. In such cases, you may need to clean up the " +"`synapse` database first." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:14 +msgid "" +"**ensure you have uploaded your SQLite database file to the server** (any" +" path is okay)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:15 +msgid "" +"if you're using the integrated Postgres server (**by default, you are** " +"using it, unless you've explicitly switched to [Using an external " +"PostgreSQL server](configuring-playbook-external-postgres.md)), **make " +"sure Postgres is started** by running `just start-group postgres`" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:17 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:19 +msgid "" +"Run this command (make sure to replace `` " +"with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:25 +msgid "**Notes**:" +msgstr "" + +#: ../../../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:28 +msgid "" +"if the SQLite database is from an older version of Synapse, the " +"**importing procedure may run migrations on it to bring it up to date**. " +"That is, your SQLite database file may get modified and become unusable " +"with your older Synapse version. Keeping a copy of the original is " +"probably wise." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/installing.po b/i18n/locales/bg/LC_MESSAGES/docs/installing.po new file mode 100644 index 000000000..f29377f43 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/installing.po @@ -0,0 +1,449 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/installing.md:1 +msgid "Installing" +msgstr "" + +#: ../../../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:5 +msgid "" +"If you've configured your DNS records and the playbook, you can start the" +" installation procedure." +msgstr "" + +#: ../../../docs/installing.md:7 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/installing.md:9 +msgid "" +"Before installing, you need to update the Ansible roles that this " +"playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/installing.md:11 +msgid "" +"To update your playbook directory and all upstream Ansible roles (defined" +" in the `requirements.yml` file), run:" +msgstr "" + +#: ../../../docs/installing.md:13 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/installing.md:14 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/installing.md:16 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/installing.md:18 +msgid "" +"For details about `just` commands, take a look at: [Running `just` " +"commands](just.md)." +msgstr "" + +#: ../../../docs/installing.md:20 +msgid "Install Matrix server and services" +msgstr "" + +#: ../../../docs/installing.md:22 +msgid "" +"The Ansible playbook's tasks are tagged, so that certain parts of the " +"Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/installing.md:24 +msgid "" +"The general command syntax for installation (and also maintenance) is: " +"`ansible-playbook -i inventory/hosts setup.yml " +"--tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself " +"familiar with the [playbook tags](playbook-tags.md) before proceeding." +msgstr "" + +#: ../../../docs/installing.md:26 +msgid "" +"If you **don't** use SSH keys for authentication, but rather a regular " +"password, you may need to add `--ask-pass` to the all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:28 +msgid "" +"If you **do** use SSH keys for authentication, **and** use a non-root " +"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" +"pass`) to all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:30 +msgid "" +"There 2 ways to start the installation process - depending on whether " +"you're [Installing a brand new server (without importing " +"data)](#installing-a-brand-new-server-without-importing-data) or " +"[Installing a server into which you'll import old data](#installing-a" +"-server-into-which-youll-import-old-data)." +msgstr "" + +#: ../../../docs/installing.md:32 +msgid "" +"**Note**: if you are migrating from an old server to a new one, take a " +"look at [this guide](maintenance-migrating.md) instead. This is an easier" +" and more straightforward way than installing a server and importing old " +"data into it." +msgstr "" + +#: ../../../docs/installing.md:34 +msgid "Installing a brand new server (without importing data)" +msgstr "" + +#: ../../../docs/installing.md:36 +msgid "" +"If this is **a brand new** Matrix server and you **won't be importing old" +" data into it**, run all these tags:" +msgstr "" + +#: ../../../docs/installing.md:42 +msgid "This will do a full installation and start all Matrix services." +msgstr "" + +#: ../../../docs/installing.md:44 +msgid "" +"**Note**: if the command does not work as expected, make sure that you " +"have properly installed and configured software required to run the " +"playbook, as described on [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/installing.md:46 +msgid "Installing a server into which you'll import old data" +msgstr "" + +#: ../../../docs/installing.md:48 +msgid "" +"If you will be importing data into your newly created Matrix server, " +"install it, but **do not** start its services just yet. Starting its " +"services or messing with its database now will affect your data import " +"later on." +msgstr "" + +#: ../../../docs/installing.md:50 +msgid "" +"To do the installation **without** starting services, run `ansible-" +"playbook` with the `install-all` tag only:" +msgstr "" + +#: ../../../docs/installing.md:56 +msgid "" +"⚠️ **Warning**: do not run the just \"recipe\" `just install-all` " +"instead, because it automatically starts services at the end of " +"execution. See: [Difference between playbook tags and shortcuts](just.md" +"#difference-between-playbook-tags-and-shortcuts)" +msgstr "" + +#: ../../../docs/installing.md:58 +msgid "When this command completes, services won't be running yet." +msgstr "" + +#: ../../../docs/installing.md:60 +msgid "You can now:" +msgstr "" + +#: ../../../docs/installing.md:62 +msgid "" +"[Importing an existing SQLite database (from another Synapse installation" +")](importing-synapse-sqlite.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:64 +msgid "" +"[Importing an existing Postgres database (from another installation" +")](importing-postgres.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:66 +msgid "" +"[Importing `media_store` data files from an existing Synapse installation" +"](importing-synapse-media-store.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:68 +msgid ".. and then proceed to starting all services:" +msgstr "" + +#: ../../../docs/installing.md:74 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/installing.md:76 +msgid "" +"ℹ️ *You can skip this step if you have installed a server and imported " +"old data to it.*" +msgstr "" + +#: ../../../docs/installing.md:78 +msgid "" +"As you have configured your brand new server and the client, you need to " +"**create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/installing.md:80 +msgid "" +"After creating the user account, you can log in to it with [Element Web" +"](configuring-playbook-client-element-web.md) that this playbook has " +"installed for you at this URL: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/installing.md:82 +msgid "" +"To create your user account (as an administrator of the server) via this " +"Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/installing.md:84 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/installing.md:85 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/installing.md:86 +msgid "" +"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " +"full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/installing.md:87 +msgid "" +"Use `admin=yes` to make your user account an administrator of the Matrix " +"server" +msgstr "" + +#: ../../../docs/installing.md:95 +msgid "" +"Feel free to create as many accounts (for friends, family, etc.) as you " +"want. Still, perhaps you should grant full administrative access to your " +"account only (with `admin=yes`), and others should be created with " +"`admin=no`." +msgstr "" + +#: ../../../docs/installing.md:97 +msgid "" +"For more information, see the documentation for [registering users" +"](registering-users.md)." +msgstr "" + +#: ../../../docs/installing.md:99 +msgid "Finalize the installation" +msgstr "" + +#: ../../../docs/installing.md:101 +msgid "" +"Now you've configured Matrix services and your user account, you need to " +"**finalize the installation process** by [setting up Matrix delegation " +"(redirection)](howto-server-delegation.md), so that your Matrix server " +"(`matrix.example.com`) can present itself as the base domain " +"(`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:103 +msgid "" +"This is required for federation to work! Without a proper configuration, " +"your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:105 +msgid "" +"To configure the delegation, you have these two options. Choose one of " +"them according to your situation." +msgstr "" + +#: ../../../docs/installing.md:107 +msgid "" +"If you can afford to point the base domain at the Matrix server, follow " +"the instructions below which guide you into [serving the base domain" +"](configuring-playbook-base-domain-serving.md) from the integrated web " +"server. It will enable you to use a Matrix user ID like " +"`@alice:example.com` while hosting services on a subdomain like " +"`matrix.example.com`." +msgstr "" + +#: ../../../docs/installing.md:108 +msgid "" +"Alternatively, if you're using the base domain for other purposes and " +"cannot point it to the Matrix server (and thus cannot \"serve the base " +"domain\" from it), you most likely need to [manually install well-known " +"files on the base domain's server](configuring-well-known.md#manually-" +"installing-well-known-files-on-the-base-domains-server), but feel free to" +" familiarize yourself with all [server delegation (redirection) options" +"](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/installing.md:110 +msgid "" +"To have the base domain served from the integrated web server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/installing.md:116 +msgid "After configuring the playbook, run the command below:" +msgstr "" + +#: ../../../docs/installing.md:122 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/installing.md:124 +msgid "After finilizing the installation, you can:" +msgstr "" + +#: ../../../docs/installing.md:126 +msgid "[check if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/installing.md:127 +msgid "" +"or [set up additional services](configuring-playbook.md#other-" +"configuration-options) (bridges to other chat networks, bots, etc.)" +msgstr "" + +#: ../../../docs/installing.md:128 +msgid "" +"or learn how to [upgrade services when new versions are released" +"](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:129 +msgid "or learn how to [maintain your server](faq.md#maintenance)" +msgstr "" + +#: ../../../docs/installing.md:130 +msgid "or join some Matrix rooms:" +msgstr "" + +#: ../../../docs/installing.md:131 +msgid "" +"via the *Explore rooms* feature in Element Web or some other clients, or " +"by discovering them using this [matrix-static " +"list](https://view.matrix.org). **Note**: joining large rooms may " +"overload small servers." +msgstr "" + +#: ../../../docs/installing.md:132 +msgid "" +"or come say Hi in our support room - [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com). You might learn something or get to help someone " +"else new to Matrix hosting." +msgstr "" + +#: ../../../docs/installing.md:133 +msgid "" +"or help make this playbook better by contributing (code, documentation, " +"or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" +msgstr "" + +#: ../../../docs/installing.md:135 +msgid "Maintaining your setup in the future" +msgstr "" + +#: ../../../docs/installing.md:137 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/installing.md:139 +msgid "" +"The upstream projects, which this playbook makes use of, occasionally if " +"not often suffer from security vulnerabilities." +msgstr "" + +#: ../../../docs/installing.md:141 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/installing.md:143 +msgid "" +"For more information about upgrading or maintaining services with the " +"playbook, take at look at this page: [Upgrading the Matrix services" +"](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:145 +msgid "" +"Feel free to **re-run the setup command any time** you think something is" +" wrong with the server configuration. Ansible will take your " +"configuration and update your server to match." +msgstr "" + +#: ../../../docs/installing.md:151 +msgid "" +"**Note**: see [this page on the playbook tags](playbook-tags.md) for more" +" information about those tags." +msgstr "" + +#: ../../../docs/installing.md:153 +msgid "Make full use of `just` shortcut commands" +msgstr "" + +#: ../../../docs/installing.md:155 +msgid "" +"After you get familiar with reconfiguring and re-running the playbook to " +"maintain the server, upgrade its services, etc., you probably would like " +"to make use of `just` shortcut commands for faster input." +msgstr "" + +#: ../../../docs/installing.md:157 +msgid "" +"For example, `just install-all` is useful for maintaining your setup " +"quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-" +"in-playbook-runtime) than `just setup-all`) when its components remain " +"unchanged. If you adjust your `vars.yml` to remove other components, " +"you'd need to run `just setup-all`, or these components will still remain" +" installed." +msgstr "" + +#: ../../../docs/installing.md:159 +msgid "" +"You can learn about the shortcut commands on this page: [Running `just` " +"commands](just.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/just.po b/i18n/locales/bg/LC_MESSAGES/docs/just.po new file mode 100644 index 000000000..9bcab1d78 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/just.po @@ -0,0 +1,212 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/just.md:1 +msgid "Running `just` commands" +msgstr "" + +#: ../../../docs/just.md:3 +msgid "" +"We have previously used [make](https://www.gnu.org/software/make/) for " +"easily running some playbook commands (e.g. `make roles` which triggers " +"[`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-" +"galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can" +" still run these commands." +msgstr "" + +#: ../../../docs/just.md:5 +msgid "" +"In addition, we have added support for running commands via " +"[`just`](https://github.com/casey/just) - a more modern command-runner " +"alternative to `make`. It can be used to invoke `ansible-playbook` " +"commands with less typing." +msgstr "" + +#: ../../../docs/just.md:7 +msgid "" +"The `just` utility executes shortcut commands (called as \"recipes\"), " +"which invoke `ansible-playbook`, `ansible-galaxy` or " +"[`agru`](https://github.com/etkecc/agru) (depending on what is available " +"in your system). The targets of the recipes are defined in " +"[`justfile`](../justfile). Most of the just recipes have no corresponding" +" `Makefile` targets." +msgstr "" + +#: ../../../docs/just.md:9 +msgid "" +"For some recipes such as `just update`, our `justfile` recommends " +"installing [`agru`](https://github.com/etkecc/agru) (a faster alternative" +" to `ansible-galaxy`) to speed up the process." +msgstr "" + +#: ../../../docs/just.md:11 +msgid "Here are some examples of shortcuts:" +msgstr "" + +#: ../../../docs/just.md +msgid "Shortcut" +msgstr "" + +#: ../../../docs/just.md +msgid "Result" +msgstr "" + +#: ../../../docs/just.md +msgid "`just roles`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Install the necessary Ansible roles pinned in " +"[`requirements.yml`](../requirements.yml)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just update`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run `git pull` (to update the playbook) and install the Ansible roles" +msgstr "" + +#: ../../../docs/just.md ../../../docs/just.md:33 +msgid "`just install-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all" +",ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "`just setup-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all" +",ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "`just install-all --ask-vault-pass`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run commands with additional arguments (`--ask-vault-pass` will be " +"appended to the above installation command)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just run-tags install-mautrix-slack,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just install-service mautrix-slack`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run `just run-tags install-mautrix-slack,start` with even less typing" +msgstr "" + +#: ../../../docs/just.md +msgid "`just start-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "(Re-)starts all services" +msgstr "" + +#: ../../../docs/just.md +msgid "`just stop-group postgres`" +msgstr "" + +#: ../../../docs/just.md +msgid "Stop only the Postgres service" +msgstr "" + +#: ../../../docs/just.md +msgid "`just register-user alice secret-password yes`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Registers an `alice` user with the `secret-password` password and admin " +"access (admin = `yes`)" +msgstr "" + +#: ../../../docs/just.md:26 +msgid "" +"While [our documentation on prerequisites](prerequisites.md) lists `just`" +" as one of the requirements for installation, using `just` is optional. " +"If you find it difficult to install it, do not find it useful, or want to" +" prefer raw `ansible-playbook` commands for some reason, feel free to run" +" all commands manually. For example, you can run `ansible-galaxy` " +"directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-" +"galaxy install -r requirements.yml -p roles/galaxy/ --force`." +msgstr "" + +#: ../../../docs/just.md:28 +msgid "Difference between playbook tags and shortcuts" +msgstr "" + +#: ../../../docs/just.md:30 +msgid "" +"It is worth noting that `just` \"recipes\" are different from [playbook " +"tags](playbook-tags.md). The recipes are shortcuts of commands defined in" +" `justfile` and can be executed by the `just` program only, while the " +"playbook tags are available for the raw `ansible-playbook` commands as " +"well. Please be careful not to confuse them." +msgstr "" + +#: ../../../docs/just.md:32 +msgid "For example, these two commands are different:" +msgstr "" + +#: ../../../docs/just.md:34 +msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" +msgstr "" + +#: ../../../docs/just.md:36 +msgid "" +"The just recipe runs `ensure-matrix-users-created` and `start` tags after" +" `install-all`, while the latter runs only `install-all` tag. The correct" +" shortcut of the latter is `just run-tags install-all`." +msgstr "" + +#: ../../../docs/just.md:38 +msgid "" +"Such kind of difference sometimes matters. For example, when you install " +"a Matrix server into which you will import old data (see " +"[here](installing.md#installing-a-server-into-which-youll-import-old-" +"data)), you are not supposed to run `just install-all` or `just setup-" +"all`, because these commands start services immediately after installing " +"components which may prevent your from importing old data." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po new file mode 100644 index 000000000..204de1c85 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.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: 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" +"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/maintenance-and-troubleshooting.md:1 +msgid "Maintenance and Troubleshooting" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:3 +msgid "How to see the current status of your services" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:5 +msgid "" +"You can check the status of your services by using `systemctl status`. " +"Example:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:15 +msgid "" +"Docker containers that the playbook configures are supervised by " +"[systemd](https://wiki.archlinux.org/title/Systemd) and their logs are " +"configured to go to [systemd-" +"journald](https://wiki.archlinux.org/title/Systemd/Journal)." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:17 +msgid "" +"To prevent double-logging, Docker logging is disabled by explicitly " +"passing `--log-driver=none` to all containers. Due to this, you " +"**cannot** view logs using `docker logs`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:19 +msgid "" +"To view systemd-journald logs using " +"[journalctl](https://man.archlinux.org/man/journalctl.1), run a command " +"like this:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:25 +msgid "Increasing Synapse logging" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:27 +msgid "" +"Because the [Synapse](https://github.com/element-hq/synapse) Matrix " +"server is originally very chatty when it comes to logging, we " +"intentionally reduce its [logging " +"level](https://docs.python.org/3/library/logging.html#logging-levels) " +"from `INFO` to `WARNING`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:29 +msgid "" +"If you'd like to debug an issue or [report a Synapse " +"bug](https://github.com/element-hq/synapse/issues/new/choose) to the " +"developers, it'd be better if you temporarily increasing the logging " +"level to `INFO`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:31 +msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:39 +msgid "Re-run the playbook after making these configuration changes." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:41 +msgid "Remove unused Docker data" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:43 +msgid "" +"You can free some disk space from Docker, see [docker system " +"prune](https://docs.docker.com/engine/reference/commandline/system_prune/)" +" for more information." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:49 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags run-docker-prune`" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:51 +msgid "Postgres" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:53 +msgid "" +"See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) " +"documentation page." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:55 +msgid "Ma1sd" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:57 +msgid "" +"See the dedicated [Adjusting ma1sd Identity Server configuration" +"](configuring-playbook-ma1sd.md) documentation page." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po new file mode 100644 index 000000000..e0c108f7a --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po @@ -0,0 +1,55 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-checking-services.md:1 +msgid "Checking if services work" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:3 +msgid "" +"This playbook can perform a check to ensure that you've configured things" +" correctly and that services are running." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:5 +msgid "To perform the check, run:" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:11 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags self-check`" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:13 +msgid "If it's all green, everything is probably running correctly." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:15 +msgid "" +"Besides this self-check, you can also check whether your server federates" +" with the Matrix network by using the [Federation " +"Tester](https://federationtester.matrix.org/) against your base domain " +"(`example.com`), not the `matrix.example.com` subdomain." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po new file mode 100644 index 000000000..af7829c38 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po @@ -0,0 +1,196 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-migrating.md:1 +msgid "Migrating to new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:3 +msgid "" +"This documentation explains how to migrate your Matrix services (server, " +"client, bridges, etc.) and data **from an old server to a new server**." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:6 +msgid "" +"This migration guide is applicable if you migrate from one server to " +"another server having the same CPU architecture (e.g. both servers being " +"`amd64`)." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:8 +msgid "" +"If you're trying to migrate between different architectures (e.g. `amd64`" +" --> `arm64`), simply copying the complete `/matrix` directory is **not**" +" possible as it would move the raw PostgreSQL data " +"(`/matrix/postgres/data`) between different architectures. In this " +"specific case, you can use the guide below as a reference, but you would " +"also need to avoid syncing `/matrix/postgres/data` to the new host, and " +"also dump the database on your current server and import it properly on " +"the new server. See our [Backing up PostgreSQL](maintenance-postgres.md" +"#backing-up-postgresql) docs for help with PostgreSQL backup/restore." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:9 +msgid "" +"If you have any questions about migration or encountered an issue during " +"migration, do not hesitate to ask for help on [our Matrix " +"room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). " +"You probably might want to prepare a temporary/sub account on another " +"Matrix server in case it becomes impossible to use your server due to " +"migration failure by any chance." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:11 +msgid "" +"You can't change the domain (specified in the `matrix_domain` variable) " +"after the initial deployment." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:13 +msgid "Lower DNS TTL" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:15 +msgid "" +"Prepare by lowering DNS TTL for your domains (`matrix.example.com`, " +"etc.), so that DNS record changes would happen faster, leading to less " +"downtime." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:17 +msgid "Stop services on the old server completely" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:19 +msgid "" +"Before migrating, you need to stop all services on the old server and " +"make sure they won't be starting again." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:21 +msgid "" +"To do so, it is recommended to run the `systemctl` command on the server." +" Running the playbook's `stop` tag also stops the services, but just " +"once; they will start again if you reboot the server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:23 +msgid "" +"Log in to the old server and run the command as `root` (or a user that " +"can run it with `sudo`):" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:29 +msgid "Copy data directory to the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:31 +msgid "" +"After you've confirmed that all services were stopped, copy the `/matrix`" +" directory from the old server to the new server. When copying, make sure" +" to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:33 +msgid "Adjust DNS records" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:35 +msgid "" +"Make sure your DNS records are adjusted to point to the new server's IP " +"address." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:37 +msgid "Update `inventory/hosts` file" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:39 +msgid "" +"Having adjusted DNS records, replace the old server's external IP address" +" on the `inventory/hosts` file with that of the new server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:41 +msgid "Create `matrix` user and group on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:43 +msgid "" +"Then, run the command below on your local computer to create the `matrix`" +" user and group on the new server:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:49 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags setup-system-user`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:51 +msgid "" +"**Note**: because the `matrix` user and group are created dynamically on " +"each server, the user/group ID may differ between the old and new server." +" We suggest that you adjust ownership of `/matrix` files. To adjust the " +"ownership, log in to the new server and run the command:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:57 +msgid "Install and start all services on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:59 +msgid "" +"Finally, run the command below on your local computer to finish the " +"installation and start all services:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:65 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags install-all,start`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:67 +msgid "Check if services work" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:69 +msgid "" +"After starting the services, you probably might want to ensure that " +"you've migrated things correctly and that services are running. For " +"instructions, see: [check if services work](maintenance-checking-" +"services.md)" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:71 +msgid "" +"Having make sure that both services and federation work as expected, you " +"can safely shutdown the old server." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po new file mode 100644 index 000000000..7c8da8391 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po @@ -0,0 +1,336 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-postgres.md:1 +msgid "PostgreSQL maintenance" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:3 +msgid "" +"This document shows you how to perform various maintenance tasks related " +"to the Postgres database server used by Matrix." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:7 +msgid "" +"[Getting a database terminal](#getting-a-database-terminal), for when you" +" wish to execute SQL queries" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:9 +msgid "" +"[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a" +" Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-" +"vacuum.html) (optimizing disk space)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:11 +msgid "" +"[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to " +"make a backup" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:13 +msgid "" +"[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major" +" versions of PostgreSQL. Such **manual upgrades are sometimes required**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:15 +msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:17 +msgid "Getting a database terminal" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:19 +msgid "" +"You can use the `/matrix/postgres/bin/cli` tool to get interactive " +"terminal access ([psql](https://www.postgresql.org/docs/11/app-" +"psql.html)) to the PostgreSQL server." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:21 +msgid "" +"If you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), the above tool will not be available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:23 +msgid "" +"By default, this tool puts you in the `matrix` database, which contains " +"nothing." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:25 +msgid "To see the available databases, run `\\list` (or just `\\l`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:27 +msgid "" +"To change to another database (for example `synapse`), run `\\connect " +"synapse` (or just `\\c synapse`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:29 +msgid "" +"You can then proceed to write queries. Example: `SELECT COUNT(*) FROM " +"users;`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:31 +msgid "" +"**Be careful**. Modifying the database directly (especially as services " +"are running) is dangerous and may lead to irreversible database " +"corruption. When in doubt, consider [making a backup](#backing-up-" +"postgresql)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:33 +msgid "Vacuuming PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:35 +msgid "" +"Deleting lots data from Postgres does not make it release disk space, " +"until you perform a [`VACUUM` " +"operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:37 +msgid "" +"You can run different `VACUUM` operations via the playbook, with the " +"default preset being `vacuum-complete`:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:39 +msgid "" +"(default) `vacuum-complete`: stops all services temporarily and runs " +"`VACUUM FULL VERBOSE ANALYZE`." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:40 +msgid "" +"`vacuum-full`: stops all services temporarily and runs `VACUUM FULL " +"VERBOSE`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:41 +msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:42 +msgid "" +"`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any " +"services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:43 +msgid "" +"`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is " +"just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) " +"without doing a vacuum, so it's faster)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:45 +msgid "" +"**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll " +"need plenty of available disk space in your Postgres data directory " +"(usually `/matrix/postgres/data`). These presets also stop all services " +"(e.g. Synapse, etc.) while the vacuum operation is running." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:47 +msgid "Example playbook invocations:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:49 +msgid "" +"`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` " +"preset and restarts all services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:50 +msgid "" +"`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: " +"runs the `analyze` preset with all services remaining operational at all " +"times" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:52 +msgid "Backing up PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:54 +msgid "" +"To automatically make Postgres database backups on a fixed schedule, see " +"[Setting up postgres backup](configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:56 +msgid "" +"To make a one off back up of the current PostgreSQL database, make sure " +"it's running and then execute a command like this on the server:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:67 +msgid "" +"If you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), the above command will not work, because neither " +"the credentials file (`/matrix/postgres/env-postgres-psql`), nor the " +"`matrix-postgres` container is available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:69 +msgid "" +"Restoring a backup made this way can be done by [importing it](importing-" +"postgres.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:71 +msgid "Upgrading PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:73 +msgid "" +"Unless you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), this playbook initially installs Postgres for you." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:75 +msgid "" +"Once installed, the playbook attempts to preserve the Postgres version it" +" starts with. This is because newer Postgres versions cannot start with " +"data generated by older Postgres versions." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:77 +msgid "Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:79 +msgid "" +"This playbook can upgrade your existing Postgres setup with the following" +" command:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:85 +msgid "" +"**The old Postgres data directory is backed up** automatically, by " +"renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to " +"a different path, pass some extra flags to the command above, like this: " +"`--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk" +"/matrix-postgres-before-upgrade\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:87 +msgid "" +"The auto-upgrade-backup directory stays around forever, until you " +"**manually decide to delete it**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:89 +msgid "" +"As part of the upgrade, the database is dumped to `/tmp`, an upgraded and" +" empty Postgres server is started, and then the dump is restored into the" +" new server. To use a different directory for the dump, pass some extra " +"flags to the command above, like this: `--extra-" +"vars=\"postgres_dump_dir=/directory/to/dump/here\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:91 +msgid "" +"To save disk space in `/tmp`, the dump file is gzipped on the fly at the " +"expense of CPU usage. If you have plenty of space in `/tmp` and would " +"rather avoid gzipping, you can explicitly pass a dump filename which " +"doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-" +"postgres-dump.sql\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:93 +msgid "**All databases, roles, etc. on the Postgres server are migrated**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:95 +msgid "Tuning PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:97 +msgid "" +"PostgreSQL can be " +"[tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) " +"to make it run faster. This is done by passing extra arguments to the " +"Postgres process." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:99 +msgid "" +"The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting" +"/ansible-role-postgres) **already does some tuning by default**, which " +"matches the [tuning " +"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" +" done by websites like https://pgtune.leopard.in.ua/. You can manually " +"influence some of the tuning variables. These parameters (variables) are " +"injected via the `postgres_postgres_process_extra_arguments_auto` " +"variable." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:101 +msgid "" +"Most users should be fine with the automatically-done tuning. However, " +"you may wish to:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:103 +msgid "" +"**adjust the automatically-determined tuning parameters manually**: " +"change the values for the tuning variables defined in the Postgres role's" +" [default configuration file](https://github.com/mother-of-all-self-" +"hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see " +"`postgres_max_connections`, `postgres_data_storage` etc). These variables" +" are ultimately passed to Postgres via a " +"`postgres_postgres_process_extra_arguments_auto` variable" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:105 +msgid "" +"**turn automatically-performed tuning off**: override it like this: " +"`postgres_postgres_process_extra_arguments_auto: []`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:107 +msgid "" +"**add additional tuning parameters**: define your additional Postgres " +"configuration parameters in " +"`postgres_postgres_process_extra_arguments_custom`. See " +"`postgres_postgres_process_extra_arguments_auto` defined in the Postgres " +"role's [default configuration file](https://github.com/mother-of-all-" +"self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for " +"inspiration" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po new file mode 100644 index 000000000..e53044eb6 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po @@ -0,0 +1,310 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-synapse.md:1 +msgid "Synapse maintenance" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:3 +msgid "" +"This document shows you how to perform various maintenance tasks related " +"to the Synapse chat server." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:7 +msgid "" +"[Purging old data with the Purge History API](#purging-old-data-with-the-" +"purge-history-api), for when you wish to delete in-use (but old) data " +"from the Synapse database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:9 +msgid "" +"[Compressing state with rust-synapse-compress-state](#compressing-state-" +"with-rust-synapse-compress-state)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:11 +msgid "" +"[Browse and manipulate the database](#browse-and-manipulate-the-" +"database), for when you really need to take matters into your own hands" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:13 +msgid "[Make Synapse faster](#make-synapse-faster)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:15 +msgid "Purging old data with the Purge History API" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:17 +msgid "" +"You can use the **[Purge History API](https://github.com/element-" +"hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete " +"old messages on a per-room basis. **This is destructive** (especially for" +" non-federated rooms), because it means **people will no longer have " +"access to history past a certain point**." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:19 +msgid "" +"To make use of this Synapse Admin API, **you'll need an admin access " +"token** first. Refer to the documentation on [how to obtain an access " +"token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:21 +msgid "" +"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:23 +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:25 +msgid "" +"After deleting data, you may wish to run a [`FULL` Postgres `VACUUM" +"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:27 +msgid "Compressing state with rust-synapse-compress-state" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:29 +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:31 +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:33 +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:35 +msgid "To ask the playbook to run rust-synapse-compress-state, execute:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:41 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags rust-synapse-compress-state`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:43 +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:45 +msgid "" +"After state compression, you may wish to run a [`FULL` Postgres `VACUUM" +"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:47 +msgid "Browse and manipulate the database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:49 +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:51 +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:53 +msgid "" +"First, set up an SSH tunnel to your Matrix server (skip if it is your " +"local machine):" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:60 +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:66 +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:68 +msgid "" +"⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB " +"operations." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:70 +msgid "Make Synapse faster" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:72 +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:74 +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:76 +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:78 +msgid "Tuning caches and cache autotuning" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:80 +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:82 +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:84 +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:86 +msgid "" +"Cache autotuning is **enabled by default** and controlled via the " +"following variables:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:88 +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:89 +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:90 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:92 +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:94 +msgid "To **disable cache auto-tuning**, unset all values:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:102 +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:104 +msgid "" +"See also [How do I optimize this setup for a low-power server?](faq.md" +"#how-do-i-optimize-this-setup-for-a-low-power-server)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po new file mode 100644 index 000000000..24c523733 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po @@ -0,0 +1,182 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.16.0\n" + +#: ../../../docs/maintenance-upgrading-services.md:1 +msgid "Upgrading the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:3 +msgid "" +"This playbook not only installs the various Matrix services for you, but " +"can also upgrade them as new versions are made available." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:5 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:7 +msgid "" +"The upstream projects, which this playbook makes use of, occasionally if " +"not often suffer from security vulnerabilities (for example, see " +"[here](https://github.com/element-hq/element-web/security) for known ones" +" on Element Web)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:9 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:11 +msgid "" +"The developers of this playbook strive to maintain the playbook updated, " +"so that you can re-run the playbook to address such vulnerabilities. It " +"is **your responsibility** to keep your server and the services on it up-" +"to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:13 +msgid "" +"If you want to be notified when new versions of Synapse are released, you" +" should join the Synapse Homeowners room: " +"[#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:15 +msgid "Steps to upgrade the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:17 +msgid "Check the changelog" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:19 +msgid "" +"Before updating the playbook and the Ansible roles in the playbook, take " +"a look at [the changelog](../CHANGELOG.md) to see if there have been any " +"backward-incompatible changes that you need to take care of." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:21 +msgid "Update the playbook and the Ansible roles" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:23 +msgid "" +"If it looks good to you, go to the `matrix-docker-ansible-deploy` " +"directory, update your playbook directory and all upstream Ansible roles " +"(defined in the `requirements.yml` file) by running:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:25 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:26 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:28 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:30 +msgid "" +"**Note**: for details about `just` commands, take a look at: [Running " +"`just` commands](just.md)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:32 +msgid "Re-run the playbook setup" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:34 +msgid "" +"After updating the Ansible roles, then re-run the [playbook " +"setup](installing.md#maintaining-your-setup-in-the-future) and restart " +"all services:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:40 +msgid "" +"If you remove components from `vars.yml`, or if we switch some component " +"from being installed by default to not being installed by default " +"anymore, you'd need to run the setup command with the `setup-all` tag as " +"below:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:48 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account, if any." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:50 +msgid "" +"Our estimation is that running `--tags=install-all,start` is " +"approximately from **2 to 5 times faster** than running `setup-all" +",ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-" +"5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for " +"more information." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:52 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`. Note these shortcuts " +"run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:54 +msgid "" +"See [this page on the playbook tags](playbook-tags.md) for more " +"information about those tags." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:56 +msgid "PostgreSQL major version upgrade" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:58 +msgid "" +"Major version upgrades to the internal PostgreSQL database are not done " +"automatically. Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:60 +msgid "" +"For details about upgrading it, refer to the [upgrading PostgreSQL guide" +"](maintenance-postgres.md#upgrading-postgresql)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po new file mode 100644 index 000000000..5edcad58c --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -0,0 +1,122 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/obtaining-access-tokens.md:1 +msgid "Obtaining an Access Token" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:3 +msgid "" +"When setting up some optional features like bots and bridges you will " +"need to provide an access token for some user. This document provides " +"documentation on how to obtain such an access token." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:5 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:9 +msgid "" +"The user for whom you want to obtain an access token needs to already " +"exist. You can use this playbook to [register a new user](registering-" +"users.md), if you have not already." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:11 +msgid "" +"Below, we describe 2 ways to generate an access token for a user - using " +"[Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-" +"an-access-token-via-curl). For both ways you need the user's password." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:13 +msgid "Obtain an access token via Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:15 +msgid "In a private browsing session (incognito window), open Element Web." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:16 +msgid "Log in with the user's credentials." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:17 +msgid "" +"In the settings page, choose \"Help & About\", scroll down to the bottom " +"and expand the `Access Token` section (see screenshot below)." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:18 +msgid "Copy the access token to your configuration." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:19 +msgid "" +"Close the private browsing session. **Do not log out**. Logging out will " +"invalidate the token, making it not work." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "" +"![Obtaining an access token with Element " +"Web](assets/obtain_admin_access_token_element_web.png)" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "Obtaining an access token with Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:23 +msgid "Obtain an access token via curl" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:25 +msgid "" +"You can use the following command to get an access token for your user " +"directly from the [Matrix Client-Server " +"API](https://www.matrix.org/docs/guides/client-server-api#login):" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:35 +msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:37 +msgid "" +"`YOURDEVICEID` is optional and can be used to more easily identify the " +"session later. When omitted (mind the commas in the JSON payload if " +"you'll be omitting it), a random device ID will be generated." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:39 +msgid "Your response will look like this (prettified):" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po new file mode 100644 index 000000000..af10301e8 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po @@ -0,0 +1,113 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/playbook-tags.md:1 +msgid "Playbook tags" +msgstr "" + +#: ../../../docs/playbook-tags.md:3 +msgid "" +"The Ansible playbook's tasks are tagged, so that certain parts of the " +"Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/playbook-tags.md:5 +msgid "" +"The general command syntax is: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" +msgstr "" + +#: ../../../docs/playbook-tags.md:7 +msgid "Here are some playbook tags that you should be familiar with:" +msgstr "" + +#: ../../../docs/playbook-tags.md:9 +msgid "" +"`setup-all` - runs all setup tasks (installation and uninstallation) for " +"all components, but does not start/restart services" +msgstr "" + +#: ../../../docs/playbook-tags.md:11 +msgid "" +"`install-all` - like `setup-all`, but skips uninstallation tasks. Useful " +"for maintaining your setup quickly when its components remain unchanged. " +"If you adjust your `vars.yml` to remove components, you'd need to run " +"`setup-all` though, or these components will still remain installed" +msgstr "" + +#: ../../../docs/playbook-tags.md:13 +msgid "" +"`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for" +" a given role, but does not start/restart services. You can discover " +"these additional tags in each role (`roles/**/tasks/main.yml`). Running " +"per-component setup tasks is **not recommended**, as components sometimes" +" depend on each other and running just the setup tasks for a given " +"component may not be enough. For example, setting up the [mautrix-" +"telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in " +"addition to the `setup-mautrix-telegram` tag, requires database changes " +"(the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-" +"nginx-proxy` tag)." +msgstr "" + +#: ../../../docs/playbook-tags.md:15 +msgid "" +"`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but" +" skips uninstallation tasks. See `install-all` above for additional " +"information." +msgstr "" + +#: ../../../docs/playbook-tags.md:17 +msgid "" +"`start` - starts all systemd services and makes them start automatically " +"in the future" +msgstr "" + +#: ../../../docs/playbook-tags.md:19 +msgid "`stop` - stops all systemd services" +msgstr "" + +#: ../../../docs/playbook-tags.md:21 +msgid "" +"`ensure-matrix-users-created` - a special tag which ensures that all " +"special users needed by the playbook (for bots, etc.) are created" +msgstr "" + +#: ../../../docs/playbook-tags.md:23 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/playbook-tags.md:24 +msgid "" +"`setup-*` tags and `install-*` tags **do not start services** " +"automatically, because you may wish to do things before starting " +"services, such as importing a database dump, restoring data from another " +"server, etc." +msgstr "" + +#: ../../../docs/playbook-tags.md:25 +msgid "" +"Please be careful not to confuse the playbook tags with the `just` " +"shortcut commands (\"recipes\"). For details about `just` commands, see: " +"[Running `just` commands](just.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po new file mode 100644 index 000000000..b3df2522e --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po @@ -0,0 +1,260 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/prerequisites.md:1 +msgid "Prerequisites" +msgstr "" + +#: ../../../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:5 +msgid "" +"To install Matrix services using this Ansible playbook, you need to " +"prepare several requirements both on your local computer (where you will " +"run the playbook to configure the server) and the server (where the " +"playbook will install the Matrix services for you). **These requirements " +"need to be set up manually** before proceeding to the next step." +msgstr "" + +#: ../../../docs/prerequisites.md:7 +msgid "" +"We will be using `example.com` as the domain in the following " +"instruction. Please remember to replace it with your own domain before " +"running any commands." +msgstr "" + +#: ../../../docs/prerequisites.md:9 +msgid "" +"**Note**: if you do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\", we suggest you to follow ⚡ " +"**[Quick start](quick-start.md)** installation guide." +msgstr "" + +#: ../../../docs/prerequisites.md:11 +msgid "Your local computer" +msgstr "" + +#: ../../../docs/prerequisites.md:13 +msgid "" +"[Ansible](http://ansible.com/) program. It's used to run this playbook " +"and configures your server for you. Take a look at [our guide about " +"Ansible](ansible.md) for more information, as well as [version " +"requirements](ansible.md#supported-ansible-versions) and alternative ways" +" to run Ansible." +msgstr "" + +#: ../../../docs/prerequisites.md:15 +msgid "" +"[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python " +"library. See [this official " +"documentation](https://passlib.readthedocs.io/en/stable/install.html" +"#installation-instructions) for an instruction to install it. On most " +"distros, you need to install some `python-passlib` or `py3-passlib` " +"package, etc." +msgstr "" + +#: ../../../docs/prerequisites.md:17 +msgid "" +"[`git`](https://git-scm.com/) as the recommended way to download the " +"playbook. `git` may also be required on the server if you will be [self-" +"building](self-building.md) components." +msgstr "" + +#: ../../../docs/prerequisites.md:19 +msgid "" +"[`just`](https://github.com/casey/just) for running `just roles`, `just " +"update`, etc. (see [`justfile`](../justfile)), although you can also run " +"these commands manually. Take at look at this documentation for more " +"information: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:21 +msgid "" +"Strong password (random strings) generator. The playbook often requires " +"you to create a strong password and use it for settings on `vars.yml`, " +"components, etc. As any tools should be fine, this playbook has adopted " +"[`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). " +"[Password Tech](https://pwgen-win.sourceforge.io/), formerly known as " +"\"PWGen for Windows\", is available as free and open source password " +"generator for Windows. Generally, using a random generator available on " +"the internet is not recommended." +msgstr "" + +#: ../../../docs/prerequisites.md:23 +msgid "Server" +msgstr "" + +#: ../../../docs/prerequisites.md:25 +msgid "" +"(Recommended) An **x86** server ([What kind of server specs do I " +"need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these " +"operating systems that make use of [systemd](https://systemd.io/):" +msgstr "" + +#: ../../../docs/prerequisites.md:26 +msgid "**Archlinux**" +msgstr "" + +#: ../../../docs/prerequisites.md:27 +msgid "" +"**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL " +"alternatives (although your mileage may vary)" +msgstr "" + +#: ../../../docs/prerequisites.md:28 +msgid "**Debian** (10/Buster or newer)" +msgstr "" + +#: ../../../docs/prerequisites.md:29 +msgid "" +"**Ubuntu** (18.04 or newer, although [20.04 may be " +"problematic](ansible.md#supported-ansible-versions) if you run the " +"Ansible playbook on it)" +msgstr "" + +#: ../../../docs/prerequisites.md:31 +msgid "" +"Generally, newer is better. We only strive to support released stable " +"versions of distributions, not betas or pre-releases. This playbook can " +"take over your whole server or co-exist with other services that you have" +" there." +msgstr "" + +#: ../../../docs/prerequisites.md:33 +msgid "" +"This playbook somewhat supports running on non-`amd64` architectures like" +" ARM. See [Alternative Architectures](alternative-architectures.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:35 +msgid "" +"If your distro runs within an [LXC " +"container](https://linuxcontainers.org/), you may hit [this " +"issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/703). It can be worked around, if absolutely necessary, but" +" we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/prerequisites.md:37 +msgid "" +"`root` access to your server (or a user capable of elevating to `root` " +"via `sudo`)." +msgstr "" + +#: ../../../docs/prerequisites.md:39 +msgid "" +"[Python](https://www.python.org/). Most distributions install Python by " +"default, but some don't (e.g. Ubuntu 18.04) and require manual " +"installation (something like `apt-get install python3`). On some distros," +" Ansible may incorrectly [detect the Python " +"version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html)" +" (2 vs 3) and you may need to explicitly specify the interpreter path in " +"`inventory/hosts` during installation (e.g. " +"`ansible_python_interpreter=/usr/bin/python3`)" +msgstr "" + +#: ../../../docs/prerequisites.md:41 +msgid "" +"[sudo](https://www.sudo.ws/), even when you've configured Ansible to log " +"in as `root`. Some distributions, like a minimal Debian net install, do " +"not include the `sudo` package by default." +msgstr "" + +#: ../../../docs/prerequisites.md:43 +msgid "" +"An HTTPS-capable web server at the base domain name (`example.com`) which" +" is capable of serving static files. Unless you decide to [Serve the base" +" domain from the Matrix server](configuring-playbook-base-domain-" +"serving.md) or alternatively, to use DNS SRV records for [Server " +"Delegation](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:45 +msgid "" +"Properly configured DNS records for `example.com` (details in " +"[Configuring DNS](configuring-dns.md))." +msgstr "" + +#: ../../../docs/prerequisites.md:47 +msgid "" +"Some TCP/UDP ports open. This playbook (actually [Docker " +"itself](https://docs.docker.com/network/iptables/)) configures the " +"server's internal firewall for you. In most cases, you don't need to do " +"anything special. But **if your server is running behind another " +"firewall**, you'd need to open these ports:" +msgstr "" + +#: ../../../docs/prerequisites.md:49 +msgid "`80/tcp`: HTTP webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:50 +msgid "`443/tcp` and `443/udp`: HTTPS webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:51 +msgid "`3478/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:52 +msgid "`3478/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:53 +msgid "`5349/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:54 +msgid "`5349/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:55 +msgid "" +"`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some" +" cases, this **may necessary even with federation disabled**. Integration" +" Servers (like Dimension) and Identity Servers (like ma1sd) may need to " +"access `openid` APIs on the federation port." +msgstr "" + +#: ../../../docs/prerequisites.md:56 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:57 +msgid "" +"potentially some other ports, depending on the additional (non-default) " +"services that you enable in the **configuring the playbook** step (later " +"on). Consult each service's documentation page in `docs/` for that." +msgstr "" + +#: ../../../docs/prerequisites.md:61 +msgid "" +"[▶️](configuring-dns.md) When ready to proceed, continue with " +"[Configuring DNS](configuring-dns.md)." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po new file mode 100644 index 000000000..54f941341 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po @@ -0,0 +1,615 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/quick-start.md:1 +msgid "Quick start" +msgstr "" + +#: ../../../docs/quick-start.md:9 +msgid "" +"This page explains how to use this Ansible playbook to install Matrix " +"services on your server with a minimal set of core services." +msgstr "" + +#: ../../../docs/quick-start.md:11 +msgid "" +"We will be using `example.com` as the \"base domain\" in the following " +"instruction." +msgstr "" + +#: ../../../docs/quick-start.md:13 +msgid "By following the instruction on this page, you will set up:" +msgstr "" + +#: ../../../docs/quick-start.md:15 +msgid "" +"**your own Matrix server** on a `matrix.example.com` server, which is " +"configured to present itself as `example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:16 +msgid "**your user account** like `@alice:example.com` on the server" +msgstr "" + +#: ../../../docs/quick-start.md:17 +msgid "" +"a **self-hosted Matrix client**, [Element Web](configuring-playbook-" +"client-element-web.md) with the default subdomain at " +"`element.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:18 +msgid "" +"Matrix delegation, so that your `matrix.example.com` server (presenting " +"itself as `example.com`) can join the Matrix Federation and communicate " +"with any other server in the Matrix network" +msgstr "" + +#: ../../../docs/quick-start.md:20 +msgid "" +"Please remember to replace `example.com` with your own domain before " +"running any commands." +msgstr "" + +#: ../../../docs/quick-start.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/quick-start.md:24 +msgid "" +"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:26 +msgid "" +"At first, **check prerequisites** and prepare for installation by setting" +" up programs [on your own computer](prerequisites.md#your-local-computer)" +" and [your server](prerequisites.md#server). You also need `root` access " +"on your server (a user that could elevate to `root` via `sudo` also " +"works)." +msgstr "" + +#: ../../../docs/quick-start.md:28 +msgid "" +"When preparing your server, make sure to check [the server specs you " +"need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting " +"with a server having at least 2GB of memory." +msgstr "" + +#: ../../../docs/quick-start.md:34 +msgid "" +"If you encounter an error during installation, please make sure that you " +"have installed and configured programs correctly." +msgstr "" + +#: ../../../docs/quick-start.md:36 +msgid "" +"One of the main reasons of basic errors is using an incompatible version " +"of required software such as Ansible. Take a look at [our guide about " +"Ansible](ansible.md) for more information. In short: installing the " +"latest available version is recommended." +msgstr "" + +#: ../../../docs/quick-start.md:38 +msgid "Configure your DNS settings" +msgstr "" + +#: ../../../docs/quick-start.md:40 +msgid "" +"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:42 +msgid "" +"After installing and configuring prerequisites, you will need to " +"**configure DNS records**." +msgstr "" + +#: ../../../docs/quick-start.md:44 +msgid "" +"To configure Matrix services in the default settings, go to your DNS " +"service provider, and adjust DNS records as below." +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Type" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Host" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Priority" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Weight" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Port" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Target" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "A" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "-" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "CNAME" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`element`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:51 +msgid "" +"As the table illustrates, you need to create 2 subdomains " +"(`matrix.example.com` and `element.example.com`) and point both of them " +"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/quick-start.md:53 +msgid "It might take some time for the DNS records to propagate after creation." +msgstr "" + +#: ../../../docs/quick-start.md:55 +msgid "" +"**💡 Note**: if you are using Cloudflare DNS, make sure to disable the " +"proxy and set all records to \"DNS only\"" +msgstr "" + +#: ../../../docs/quick-start.md:57 +msgid "Get the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:59 +msgid "" +"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:61 +msgid "Next, let's **get the playbook's source code**." +msgstr "" + +#: ../../../docs/quick-start.md:63 +msgid "" +"We recommend to do so with [git](https://git-scm.com/) as it enables you " +"to keep it up to date with the latest source code. While it is possible " +"to download the playbook as a ZIP archive, it is not recommended." +msgstr "" + +#: ../../../docs/quick-start.md:65 +msgid "" +"To get the playbook with git, install git on your computer, go to a " +"directory, and run the command:" +msgstr "" + +#: ../../../docs/quick-start.md:71 +msgid "" +"It will fetch the playbook to a new `matrix-docker-ansible-deploy` " +"directory underneath the directory you are currently in." +msgstr "" + +#: ../../../docs/quick-start.md:73 +msgid "Configure the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:75 +msgid "" +"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:77 +msgid "" +"Now that the playbook was fetched, it is time to **configure** it per " +"your needs." +msgstr "" + +#: ../../../docs/quick-start.md:79 +msgid "" +"To install Matrix services with this playbook, you would at least need 2 " +"configuration files." +msgstr "" + +#: ../../../docs/quick-start.md:81 +msgid "" +"For your convenience, we have prepared example files of them " +"([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." +msgstr "" + +#: ../../../docs/quick-start.md:83 +msgid "" +"To start quickly based on these example files, go into the `matrix-" +"docker-ansible-deploy` directory and follow the instructions below:" +msgstr "" + +#: ../../../docs/quick-start.md:85 +msgid "" +"Create a directory to hold your configuration: `mkdir -p " +"inventory/host_vars/matrix.example.com` where `example.com` is your " +"\"base domain\"" +msgstr "" + +#: ../../../docs/quick-start.md:86 +msgid "" +"Copy the sample configuration file: `cp examples/vars.yml " +"inventory/host_vars/matrix.example.com/vars.yml`" +msgstr "" + +#: ../../../docs/quick-start.md:87 +msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`" +msgstr "" + +#: ../../../docs/quick-start.md:88 +msgid "" +"Edit the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/quick-start.md:89 +msgid "Edit the inventory hosts file (`inventory/hosts`)" +msgstr "" + +#: ../../../docs/quick-start.md:91 +msgid "" +"Before editing these 2 files, make sure to read explanations on them to " +"understand what needs to be configured." +msgstr "" + +#: ../../../docs/quick-start.md:93 +msgid "**💡 Notes:**" +msgstr "" + +#: ../../../docs/quick-start.md:94 +msgid "" +"If you are not in control of anything on the base domain, you would need " +"to set additional configuration on `vars.yml`. For more information, see " +"[How do I install on matrix.example.com without involving the base " +"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" +"the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/quick-start.md:95 +msgid "" +"Certain configuration decisions (like the base domain configured in " +"`matrix_domain` and homeserver implementation configured in " +"`matrix_homeserver_implementation`) are final. If you make the wrong " +"choice and wish to change it, you'll have to run the Uninstalling step " +"and start over." +msgstr "" + +#: ../../../docs/quick-start.md:96 +msgid "" +"Instead of configuring a lot of things all at once, we recommend starting" +" with the basic (default) settings in order to get yourself familiar with" +" how the playbook works. After making sure that everything works as " +"expected, you can add (and remove) advanced settings / features and run " +"the playbook as many times as you wish." +msgstr "" + +#: ../../../docs/quick-start.md:98 +msgid "Install" +msgstr "" + +#: ../../../docs/quick-start.md:100 +msgid "" +"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:102 +msgid "" +"After editing `vars.yml` and `hosts` files, let's start the " +"**installation** procedure." +msgstr "" + +#: ../../../docs/quick-start.md:104 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/quick-start.md:106 +msgid "" +"Before installing, you need to update the Ansible roles that this " +"playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/quick-start.md:108 +msgid "To update your playbook directory and all upstream Ansible roles, run:" +msgstr "" + +#: ../../../docs/quick-start.md:110 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/quick-start.md:111 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/quick-start.md:113 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/quick-start.md:115 +msgid "Run installation command" +msgstr "" + +#: ../../../docs/quick-start.md:117 +msgid "Then, run the command below to start installation:" +msgstr "" + +#: ../../../docs/quick-start.md:123 +msgid "" +"If you **don't** use SSH keys for authentication, but rather a regular " +"password, you may need to add `--ask-pass` to the command." +msgstr "" + +#: ../../../docs/quick-start.md:125 +msgid "" +"If you **do** use SSH keys for authentication, **and** use a non-root " +"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" +"pass`) to the command." +msgstr "" + +#: ../../../docs/quick-start.md:127 +msgid "" +"Wait until the command completes. If it's all green, everything should be" +" running properly." +msgstr "" + +#: ../../../docs/quick-start.md:129 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/quick-start.md:131 +msgid "" +"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:133 +msgid "" +"As you have configured your brand new server and the client, you need to " +"**create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/quick-start.md:135 +msgid "" +"To create your user account (as an administrator of the server) via this " +"Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/quick-start.md:137 +msgid "**💡 Notes**:" +msgstr "" + +#: ../../../docs/quick-start.md:138 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/quick-start.md:139 +msgid "" +"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " +"full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/quick-start.md:151 +msgid "Finalize server installation" +msgstr "" + +#: ../../../docs/quick-start.md:153 +msgid "" +"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:155 +msgid "" +"Now that you've configured Matrix services and your user account, you " +"need to **finalize the installation process** by [setting up Matrix " +"delegation (redirection)](howto-server-delegation.md), so that your " +"Matrix server (`matrix.example.com`) can present itself as the base " +"domain (`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/quick-start.md:157 +msgid "" +"**This is required for federation to work!** Without a proper " +"configuration, your server will effectively not be part of the Matrix " +"network." +msgstr "" + +#: ../../../docs/quick-start.md:159 +msgid "" +"To configure the delegation, you have these two options. Choose one of " +"them according to your situation." +msgstr "" + +#: ../../../docs/quick-start.md:161 +msgid "" +"If you can afford to point the base domain at the Matrix server, follow " +"the instruction below which guides you into [serving the base domain" +"](configuring-playbook-base-domain-serving.md) from the integrated web " +"server." +msgstr "" + +#: ../../../docs/quick-start.md:162 +msgid "" +"Alternatively, if you're using the base domain for other purposes and " +"cannot point it to the Matrix server (and thus cannot \"serve the base " +"domain\" from it), you most likely need to [manually install well-known " +"files on the base domain's server](configuring-well-known.md#manually-" +"installing-well-known-files-on-the-base-domains-server)." +msgstr "" + +#: ../../../docs/quick-start.md:164 +msgid "" +"To have the base domain served from the integrated web server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/quick-start.md:170 +msgid "" +"After configuring the playbook, run the command below and wait until it " +"finishes:" +msgstr "" + +#: ../../../docs/quick-start.md:176 +msgid "" +"💡 Running the `install-matrix-static-files` playbook tag (as done here) " +"is an optimized version of running [the full setup command](#run-" +"installation-command)." +msgstr "" + +#: ../../../docs/quick-start.md:178 +msgid "" +"After the command finishes, you can also check whether your server " +"federates with the Matrix network by using the [Federation " +"Tester](https://federationtester.matrix.org/) against your base domain " +"(`example.com`), not the `matrix.example.com` subdomain." +msgstr "" + +#: ../../../docs/quick-start.md:180 +msgid "Re-run the full setup command any time" +msgstr "" + +#: ../../../docs/quick-start.md:182 +msgid "" +"If you think something is wrong with the server configuration, feel free " +"to re-run the setup command any time:" +msgstr "" + +#: ../../../docs/quick-start.md:188 +msgid "Log in to your user account" +msgstr "" + +#: ../../../docs/quick-start.md:190 +msgid "" +"Finally, let's make sure that you can log in to the created account with " +"the specified password." +msgstr "" + +#: ../../../docs/quick-start.md:192 +msgid "" +"You should be able to log in to it with your own [Element Web" +"](configuring-playbook-client-element-web.md) client which you have set " +"up at `element.example.com` by running the playbook. Open the URL " +"(`https://element.example.com`) in a web browser and enter your " +"credentials to log in." +msgstr "" + +#: ../../../docs/quick-start.md:194 +msgid "" +"**If you successfully logged in to your account, installing and " +"configuring is complete**🎉" +msgstr "" + +#: ../../../docs/quick-start.md:196 +msgid "" +"Come say Hi👋 in our support room - [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com). You might learn something or get to help someone " +"else new to Matrix hosting." +msgstr "" + +#: ../../../docs/quick-start.md:198 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/quick-start.md:200 +msgid "" +"Once you get familiar with the playbook, you might probably want to set " +"up additional services such as a bridge on your server." +msgstr "" + +#: ../../../docs/quick-start.md:202 +msgid "" +"As this page intends to be a quick start guide which explains how to " +"start the core Matrix services, it does not cover a topic like how to set" +" them up. Take a look at the list of [things to do next](installing.md" +"#things-to-do-next) to learn more." +msgstr "" + +#: ../../../docs/quick-start.md:204 +msgid "⚠️Keep the playbook and services up-to-date" +msgstr "" + +#: ../../../docs/quick-start.md:206 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/quick-start.md:208 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/quick-start.md:210 +msgid "" +"For more information about upgrading or maintaining services with the " +"playbook, take at look at this page: [Upgrading the Matrix services" +"](maintenance-upgrading-services.md)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po new file mode 100644 index 000000000..cf0b27df5 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po @@ -0,0 +1,350 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/registering-users.md:1 +msgid "Registering users" +msgstr "" + +#: ../../../docs/registering-users.md:3 +msgid "" +"This documentation page tells you how to create user accounts on your " +"Matrix server." +msgstr "" + +#: ../../../docs/registering-users.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/registering-users.md:7 +msgid "[Registering users](#registering-users)" +msgstr "" + +#: ../../../docs/registering-users.md:8 +msgid "[Registering users manually](#registering-users-manually)" +msgstr "" + +#: ../../../docs/registering-users.md:9 +msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)" +msgstr "" + +#: ../../../docs/registering-users.md:10 +msgid "" +"[Letting certain users register on your private server](#letting-certain-" +"users-register-on-your-private-server)" +msgstr "" + +#: ../../../docs/registering-users.md:11 +msgid "[Enabling public user registration](#enabling-public-user-registration)" +msgstr "" + +#: ../../../docs/registering-users.md:12 +msgid "" +"[Adding/Removing Administrator privileges to an existing user" +"](#addingremoving-administrator-privileges-to-an-existing-user)" +msgstr "" + +#: ../../../docs/registering-users.md:14 +msgid "Registering users manually" +msgstr "" + +#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:118 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/registering-users.md:17 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/registering-users.md:18 +msgid "" +"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " +"(`@alice:example.com`)" +msgstr "" + +#: ../../../docs/registering-users.md:19 +msgid "" +"Use `admin=yes` or `admin=no` depending on whether you wish to make the " +"user an administrator of the Matrix server" +msgstr "" + +#: ../../../docs/registering-users.md:21 +msgid "" +"After registering a user (using one of the methods below), **you can log " +"in with that user** via the [Element Web](configuring-playbook-client-" +"element-web.md) service that this playbook has installed for you at a URL" +" like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/registering-users.md:23 +msgid "Registering users via the Ansible playbook" +msgstr "" + +#: ../../../docs/registering-users.md:25 +msgid "" +"It's best to register users via the Ansible playbook, because it works " +"regardless of homeserver implementation (Synapse, Dendrite, etc) or usage" +" of [Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md) (MAS)." +msgstr "" + +#: ../../../docs/registering-users.md:27 +msgid "To register a user via this Ansible playbook:" +msgstr "" + +#: ../../../docs/registering-users.md:35 +msgid "**or** by invoking `ansible-playbook` manually:" +msgstr "" + +#: ../../../docs/registering-users.md:43 +msgid "" +"Feel free to register as many users (for friends, family, etc.) as you " +"want. Still, perhaps you should grant full administrative access to your " +"user account only (with `admin=yes`), and others should be created with " +"`admin=no`." +msgstr "" + +#: ../../../docs/registering-users.md:45 +msgid "" +"⚠️ **Warning**: If you're registering users against Matrix Authentication" +" Service, do note that it [still insists](https://github.com/element-hq" +"/matrix-authentication-service/issues/1505) on having a verified email " +"address for each user. Upon a user's first login, they will be asked to " +"confirm their email address. This requires that email sending is " +"[configured](./configuring-playbook-email.md). You can also consult the " +"[Working around email deliverability issues](./configuring-playbook-" +"matrix-authentication-service.md#working-around-email-deliverability-" +"issues) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:47 +msgid "Registering users manually for Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:49 +msgid "" +"If you're using the [Synapse](configuring-playbook-synapse.md) homeserver" +" implementation (which is the default), you can register users via the " +"command-line after **SSH**-ing to your server (requires that [all " +"services have been started](installing.md#install-matrix-server-and-" +"services)):" +msgstr "" + +#: ../../../docs/registering-users.md:57 +msgid "Registering users manually for Dendrite" +msgstr "" + +#: ../../../docs/registering-users.md:59 +msgid "" +"If you're using the [Dendrite](./configuring-playbook-dendrite.md) " +"homeserver implementation, you can register users via the command-line " +"after **SSH**-ing to your server (requires that [all services have been " +"started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:67 +msgid "Registering users manually for Matrix Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:69 +msgid "" +"If you're using the [Matrix Authentication Service](./configuring-" +"playbook-matrix-authentication-service.md) and your existing homeserver " +"(most likely [Synapse](./configuring-playbook-synapse.md)) is delegating " +"authentication to it, you can register users via the command-line after " +"**SSH**-ing to your server (requires that [all services have been " +"started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:77 +msgid "" +"This `register-user` script actually invokes the `mas-cli manage " +"register-user` command under the hood. If you'd like more control over " +"the registration process, consider invoking the `mas-cli` command " +"directly:" +msgstr "" + +#: ../../../docs/registering-users.md:83 +msgid "" +"⚠️ **Warning**: Matrix Authentication Service [still " +"insists](https://github.com/element-hq/matrix-authentication-" +"service/issues/1505) on having a verified email address for each user. " +"Upon a user's first login, they will be asked to confirm their email " +"address. This requires that email sending is [configured](./configuring-" +"playbook-email.md). You can also consult the [Working around email " +"deliverability issues](./configuring-playbook-matrix-authentication-" +"service.md#working-around-email-deliverability-issues) section for more " +"information." +msgstr "" + +#: ../../../docs/registering-users.md:85 +msgid "Managing users via a Web UI" +msgstr "" + +#: ../../../docs/registering-users.md:87 +msgid "" +"To manage users more easily (via a web user-interace), you can install " +"[Synapse Admin](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/registering-users.md:89 +msgid "" +"⚠️ **Warning**: If you're using [Matrix Authentication Service" +"](configuring-playbook-matrix-authentication-service.md), note that user " +"management via synapse-admin is not fully working yet. See the " +"[Expectations](configuring-playbook-matrix-authentication-" +"service.md#expectations) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:91 +msgid "Letting certain users register on your private server" +msgstr "" + +#: ../../../docs/registering-users.md:93 +msgid "" +"If you'd rather **keep your server private** (public registration closed," +" as is the default), and **let certain people create accounts by " +"themselves** (instead of creating user accounts manually like this), " +"consider installing and making use of [matrix-registration](configuring-" +"playbook-matrix-registration.md)." +msgstr "" + +#: ../../../docs/registering-users.md:95 +msgid "Enabling public user registration" +msgstr "" + +#: ../../../docs/registering-users.md:97 +msgid "" +"To **open up user registration publicly** (usually **not recommended**), " +"add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/registering-users.md:99 +msgid "For Synapse:" +msgstr "" + +#: ../../../docs/registering-users.md:105 +msgid "For Dendrite:" +msgstr "" + +#: ../../../docs/registering-users.md:111 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/registering-users.md:120 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/registering-users.md:122 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/registering-users.md:124 +msgid "" +"If you're opening up registrations publicly like this, you might also " +"wish to [configure CAPTCHA protection](configuring-captcha.md)." +msgstr "" + +#: ../../../docs/registering-users.md:126 +msgid "Adding/Removing Administrator privileges to an existing user" +msgstr "" + +#: ../../../docs/registering-users.md:128 +msgid "Adding/Removing Administrator privileges to an existing user in Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:130 +msgid "" +"To change the admin privileges for a user in Synapse's local database, " +"you need to run an SQL query like this against the `synapse` database:" +msgstr "" + +#: ../../../docs/registering-users.md:136 +msgid "where:" +msgstr "" + +#: ../../../docs/registering-users.md:138 +msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)" +msgstr "" + +#: ../../../docs/registering-users.md:139 +msgid "`USER` and `example.com` pointing to a valid user on your server" +msgstr "" + +#: ../../../docs/registering-users.md:141 +msgid "" +"If you're using the integrated Postgres server and not an [external " +"Postgres server](configuring-playbook-external-postgres.md), you can " +"launch a Postgres into the `synapse` database by:" +msgstr "" + +#: ../../../docs/registering-users.md:143 +msgid "" +"running `/matrix/postgres/bin/cli` - to launch " +"[`psql`](https://www.postgresql.org/docs/current/app-psql.html)" +msgstr "" + +#: ../../../docs/registering-users.md:144 +msgid "running `\\c synapse` - to change to the `synapse` database" +msgstr "" + +#: ../../../docs/registering-users.md:146 +msgid "You can then proceed to run the query above." +msgstr "" + +#: ../../../docs/registering-users.md:148 +msgid "" +"**Note**: directly modifying the raw data of Synapse (or any other " +"software) could cause the software to break. You've been warned!" +msgstr "" + +#: ../../../docs/registering-users.md:150 +msgid "" +"Adding/Removing Administrator privileges to an existing user in Matrix " +"Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:152 +msgid "" +"Promoting/demoting a user in Matrix Authentication Service cannot " +"currently (2024-10-19) be done via the [`mas-cli` Management tool" +"](./configuring-playbook-matrix-authentication-service.md#management)." +msgstr "" + +#: ../../../docs/registering-users.md:154 +msgid "" +"You can do it via the [MAS Admin API](https://element-hq.github.io" +"/matrix-authentication-service/api/index.html)'s `POST " +"/api/admin/v1/users/{id}/set-admin` endpoint." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/self-building.po b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po new file mode 100644 index 000000000..5c29bb3b1 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po @@ -0,0 +1,201 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/self-building.md:1 +msgid "Self-building" +msgstr "" + +#: ../../../docs/self-building.md:3 +msgid "" +"**Caution: self-building does not have to be used on its own. See the " +"[Alternative Architectures](alternative-architectures.md) page.**" +msgstr "" + +#: ../../../docs/self-building.md:5 +msgid "" +"The playbook supports self-building of various components, which don't " +"have a container image for your architecture (see the [container images " +"we use](container-images.md)). For `amd64`, self-building is not " +"required." +msgstr "" + +#: ../../../docs/self-building.md:7 +msgid "" +"For other architectures (e.g. `arm32`, `arm64`), ready-made container " +"images are used when available. If there's no ready-made image for a " +"specific component and said component supports self-building, an image " +"will be built on the host. Building images like this takes more time and " +"resources (some build tools need to get installed by the playbook to " +"assist building)." +msgstr "" + +#: ../../../docs/self-building.md:9 +msgid "" +"To make use of self-building, you don't need to do anything. If a " +"component has an image for the specified architecture, the playbook will " +"use it directly. If not, it will build the image on the server itself." +msgstr "" + +#: ../../../docs/self-building.md:11 +msgid "Note that **not all components support self-building yet**." +msgstr "" + +#: ../../../docs/self-building.md:13 +msgid "" +"Possibly outdated list of roles where self-building the Docker image is " +"currently possible:" +msgstr "" + +#: ../../../docs/self-building.md:14 +msgid "`matrix-synapse`" +msgstr "" + +#: ../../../docs/self-building.md:15 +msgid "`matrix-synapse-admin`" +msgstr "" + +#: ../../../docs/self-building.md:16 +msgid "`matrix-client-element`" +msgstr "" + +#: ../../../docs/self-building.md:17 +msgid "`matrix-client-hydrogen`" +msgstr "" + +#: ../../../docs/self-building.md:18 +msgid "`matrix-client-cinny`" +msgstr "" + +#: ../../../docs/self-building.md:19 +msgid "`matrix-registration`" +msgstr "" + +#: ../../../docs/self-building.md:20 +msgid "`matrix-coturn`" +msgstr "" + +#: ../../../docs/self-building.md:21 +msgid "`matrix-corporal`" +msgstr "" + +#: ../../../docs/self-building.md:22 +msgid "`matrix-dimension`" +msgstr "" + +#: ../../../docs/self-building.md:23 +msgid "`matrix-ma1sd`" +msgstr "" + +#: ../../../docs/self-building.md:24 +msgid "`exim-relay`" +msgstr "" + +#: ../../../docs/self-building.md:25 +msgid "`matrix-bridge-hookshot`" +msgstr "" + +#: ../../../docs/self-building.md:26 +msgid "`matrix-bridge-appservice-irc`" +msgstr "" + +#: ../../../docs/self-building.md:27 +msgid "`matrix-bridge-appservice-slack`" +msgstr "" + +#: ../../../docs/self-building.md:28 +msgid "`matrix-bridge-appservice-webhooks`" +msgstr "" + +#: ../../../docs/self-building.md:29 +msgid "`matrix-bridge-beeper-linkedin`" +msgstr "" + +#: ../../../docs/self-building.md:30 +msgid "`matrix-bridge-mautrix-facebook`" +msgstr "" + +#: ../../../docs/self-building.md:31 +msgid "`matrix-bridge-mautrix-hangouts`" +msgstr "" + +#: ../../../docs/self-building.md:32 +msgid "`matrix-bridge-mautrix-googlechat`" +msgstr "" + +#: ../../../docs/self-building.md:33 +msgid "`matrix-bridge-mautrix-telegram`" +msgstr "" + +#: ../../../docs/self-building.md:34 +msgid "`matrix-bridge-mautrix-signal`" +msgstr "" + +#: ../../../docs/self-building.md:35 +msgid "`matrix-bridge-mautrix-gmessages`" +msgstr "" + +#: ../../../docs/self-building.md:36 +msgid "`matrix-bridge-mautrix-whatsapp`" +msgstr "" + +#: ../../../docs/self-building.md:37 +msgid "`matrix-bridge-mx-puppet-steam`" +msgstr "" + +#: ../../../docs/self-building.md:38 +msgid "`matrix-bot-mjolnir`" +msgstr "" + +#: ../../../docs/self-building.md:39 +msgid "`matrix-bot-honoroit`" +msgstr "" + +#: ../../../docs/self-building.md:40 +msgid "`matrix-bot-matrix-reminder-bot`" +msgstr "" + +#: ../../../docs/self-building.md:41 +msgid "`matrix-bot-maubot`" +msgstr "" + +#: ../../../docs/self-building.md:42 +msgid "`matrix-email2matrix`" +msgstr "" + +#: ../../../docs/self-building.md:43 +msgid "`matrix-pantalaimon`" +msgstr "" + +#: ../../../docs/self-building.md:45 +msgid "" +"Adding self-building support to other roles is welcome. Feel free to " +"contribute!" +msgstr "" + +#: ../../../docs/self-building.md:47 +msgid "" +"If you'd like **to force self-building** even if an image is available " +"for your architecture, look into the `matrix_*_self_build` variables " +"provided by individual roles." +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po new file mode 100644 index 000000000..487996aaa --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po @@ -0,0 +1,106 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/uninstalling.md:1 +msgid "Uninstalling" +msgstr "" + +#: ../../../docs/uninstalling.md:3 +msgid "**Warnings**:" +msgstr "" + +#: ../../../docs/uninstalling.md:5 +msgid "" +"If your server federates with others, make sure to **leave any federated " +"rooms before nuking your Matrix server's data**. Otherwise, the next time" +" you set up a Matrix server for this domain (regardless of the " +"installation method you use), you'll encounter trouble federating." +msgstr "" + +#: ../../../docs/uninstalling.md:7 +msgid "" +"If you have some trouble with your installation, you can just [re-run the" +" playbook](installing.md) and it will try to set things up again. " +"**Uninstalling and then installing anew rarely solves anything**." +msgstr "" + +#: ../../../docs/uninstalling.md:11 +msgid "Uninstalling using a script" +msgstr "" + +#: ../../../docs/uninstalling.md:13 +msgid "Installing places a `/matrix/bin/remove-all` script on the server." +msgstr "" + +#: ../../../docs/uninstalling.md:15 +msgid "" +"You can run it to to have it uninstall things for you automatically (see " +"below). **Use with caution!**" +msgstr "" + +#: ../../../docs/uninstalling.md:17 +msgid "Uninstalling manually" +msgstr "" + +#: ../../../docs/uninstalling.md:19 +msgid "" +"If you prefer to uninstall manually, run these commands (most are meant " +"to be executed on the Matrix server itself):" +msgstr "" + +#: ../../../docs/uninstalling.md:21 +msgid "" +"ensure all Matrix services are stopped: `ansible-playbook -i " +"inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working " +"to run this command, you can run `systemctl stop 'matrix*'` manually on " +"the server)" +msgstr "" + +#: ../../../docs/uninstalling.md:23 +msgid "" +"delete the Matrix-related systemd `.service` and `.timer` files (`rm -f " +"/etc/systemd/system/matrix*.{service,timer}`) and reload systemd " +"(`systemctl daemon-reload`)" +msgstr "" + +#: ../../../docs/uninstalling.md:25 +msgid "" +"delete some cached Docker images (`docker system prune -a`) or just " +"delete them all (`docker rmi $(docker images -aq)`)" +msgstr "" + +#: ../../../docs/uninstalling.md:27 +msgid "" +"delete the Docker networks: `docker network rm matrix matrix-coturn` " +"(might have been deleted already if you ran the `docker system prune` " +"command)" +msgstr "" + +#: ../../../docs/uninstalling.md:29 +msgid "uninstall Docker itself, if necessary" +msgstr "" + +#: ../../../docs/uninstalling.md:31 +msgid "delete the `/matrix` directory (`rm -rf /matrix`)" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po new file mode 100644 index 000000000..48dbc56e5 --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po @@ -0,0 +1,111 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/updating-users-passwords.md:1 +msgid "Updating users passwords" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:3 +msgid "Option 1 (if you are using the integrated Postgres database):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:6 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:7 +msgid "" +"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " +"(`@alice:example.com`)" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:9 +msgid "You can reset a user's password via the Ansible playbook:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:15 +msgid "" +"**You can then log in with that user** via Element Web that this playbook" +" has created for you at a URL like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:17 +msgid "Option 2 (if you are using an external Postgres server):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:19 +msgid "" +"You can manually generate the password hash by using the command-line " +"after **SSH**-ing to your server (requires that [all services have been " +"started](installing.md#finalize-the-installation):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:25 +msgid "and then connecting to the postgres server and executing:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:31 +msgid "where `` is the hash returned by the docker command above." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:33 +msgid "Option 3:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:35 +msgid "" +"Use the Synapse User Admin API as described here: https://github.com" +"/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-" +"password" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:37 +msgid "" +"This requires an [access token](obtaining-access-tokens.md) from a server" +" admin account. *This method will also log the user out of all of their " +"clients while the other options do not.*" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:39 +msgid "" +"If you didn't make your account a server admin when you created it, you " +"can learn how to switch it now by reading about it in [Adding/Removing " +"Administrator privileges to an existing user in Synapse](registering-" +"users.md#addingremoving-administrator-privileges-to-an-existing-user-in-" +"synapse)." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:41 +msgid "Example:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:43 +msgid "" +"To set @alice:example.com's password to `correct_horse_battery_staple` " +"you could use this curl command:" +msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/i18n/README.po b/i18n/locales/bg/LC_MESSAGES/i18n/README.po new file mode 100644 index 000000000..c60d751ed --- /dev/null +++ b/i18n/locales/bg/LC_MESSAGES/i18n/README.po @@ -0,0 +1,460 @@ +# Translations template for PROJECT. +# Copyright (C) 2024 ORGANIZATION +# This file is distributed under the same license as the PROJECT project. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PROJECT VERSION\n" +"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" +"POT-Creation-Date: 2024-12-20 09:29+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.16.0\n" + +#: ../../README.md:1 +msgid "Internationalization" +msgstr "" + +#: ../../README.md:3 +msgid "" +"Translated documentation files are published and maintained in " +"[`translated/`](translated/) directory." +msgstr "" + +#: ../../README.md:5 +msgid "Currently, we support translation of:" +msgstr "" + +#: ../../README.md:7 +msgid "Markdown files found at the top level project directory" +msgstr "" + +#: ../../README.md:8 +msgid "" +"Markdown files found in the [`docs`](../docs/) directory (this is where " +"the bulk of the documentation is)" +msgstr "" + +#: ../../README.md:9 +msgid "this current document in the `i18n` directory" +msgstr "" + +#: ../../README.md:11 +msgid "" +"💡 For readers' sake, we only [publish translations in a new language" +"](#publish-translations-in-a-new-language) when the translation " +"progresses beyond a certain threshold (requiring that at least the " +"project README and core installation guides are translated)." +msgstr "" + +#: ../../README.md:13 +msgid "Organization of this `i18n` directory is as follows:" +msgstr "" + +#: ../../README.md:15 +msgid "" +"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we " +"publish translations for (in the [translated/](translated/) directory)" +msgstr "" + +#: ../../README.md:16 +msgid "" +"[.gitignore](.gitignore): a list of files and directories to ignore in " +"the `i18n` directory. We intentionaly ignore translated results " +"(`translated/` 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:17 +msgid "" +"[justfile](justfile): a list of recipes for " +"[just](https://github.com/casey/just) command runner" +msgstr "" + +#: ../../README.md:18 +msgid "" +"[requirements.txt](requirements.txt): a list of Python packages required " +"to work with translations" +msgstr "" + +#: ../../README.md:19 +msgid "" +"[translation-templates/](translation-templates/): a list of English " +"translation templates - strings extracted from Markdown files" +msgstr "" + +#: ../../README.md:20 +msgid "[locales/](locales/): localization files for languages" +msgstr "" + +#: ../../README.md:21 +msgid "" +"[translated/](translated/): translated documents for published languages " +"(see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations" +" in a new language](#publish-translations-in-a-new-language))" +msgstr "" + +#: ../../README.md:23 +msgid "Guide for translators" +msgstr "" + +#: ../../README.md:25 +msgid "" +"This project uses [Sphinx](https://www.sphinx-doc.org/) to generate " +"translated documents." +msgstr "" + +#: ../../README.md:27 +msgid "" +"For details about using Sphinx for translation, refer [this official " +"document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) " +"as well." +msgstr "" + +#: ../../README.md:29 +msgid "" +"For now, translations are handled manually by editing `.po` files in the " +"`locales/` directory. In the future, we plan on integrating " +"with [Weblate](https://weblate.org/) to allow for translating from a web " +"interface." +msgstr "" + +#: ../../README.md:31 +msgid "(Recommended) Using the uv package manager and just command runner" +msgstr "" + +#: ../../README.md:33 +msgid "" +"If you have the [uv](https://docs.astral.sh/uv/) package manager and " +"[just](https://github.com/casey/just) command runner installed, you can " +"use our [justfile](justfile) recipes to easily manage translation files " +"and build translated documents." +msgstr "" + +#: ../../README.md:35 +msgid "" +"The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create" +" [a Python virtual " +"environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` " +"directory and install the required Python packages (as per " +"[requirements.txt](requirements.txt)) to it." +msgstr "" + +#: ../../README.md:37 ../../README.md:64 +msgid "Preparation" +msgstr "" + +#: ../../README.md:39 +msgid "" +"Make sure you have the [uv](https://docs.astral.sh/uv/) package manager " +"and [just](https://github.com/casey/just) command runner installed." +msgstr "" + +#: ../../README.md:41 ../../README.md:72 +msgid "Translation" +msgstr "" + +#: ../../README.md:43 ../../README.md:74 +msgid "" +"Recommended flow when working on a new language (replace `` " +"with the language code, e.g. `bg`):" +msgstr "" + +#: ../../README.md:45 +msgid "" +"Update the locale files for your language: `just sync-for-language " +"` (internally, this automatically runs `just extract-" +"translation-templates` to make sure the translation templates are up-to-" +"date)" +msgstr "" + +#: ../../README.md:47 ../../README.md:80 +msgid "Use an editor to translate the files in the `locales/` directory" +msgstr "" + +#: ../../README.md:49 +msgid "Build translated documents: `just build-for-language `" +msgstr "" + +#: ../../README.md:51 ../../README.md:84 +msgid "Preview the result in the `translated/` directory" +msgstr "" + +#: ../../README.md:53 ../../README.md:86 +msgid "Commit your changes done to the `locales/` directory" +msgstr "" + +#: ../../README.md:55 ../../README.md:88 +msgid "" +"If you have progressed with the translation beyond a certain threshold, " +"consider [Publishing translations in a new language](#publish-" +"translations-in-a-new-language)" +msgstr "" + +#: ../../README.md:57 +msgid "Using any other package manager and manual scripts" +msgstr "" + +#: ../../README.md:59 +msgid "" +"If you cannot use [uv](https://docs.astral.sh/uv/) and/or " +"[just](https://github.com/casey/just), you can:" +msgstr "" + +#: ../../README.md:61 +msgid "" +"manage Python packages in another way " +"([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-" +"poetry.org/), etc.)" +msgstr "" + +#: ../../README.md:62 +msgid "" +"manage translation strings and build translated documents manually by " +"invoking scripts from the [bin](bin/) directory" +msgstr "" + +#: ../../README.md:66 +msgid "virtualenv and pip" +msgstr "" + +#: ../../README.md:68 +msgid "" +"Create a Python virtual environment in the `.venv` directory: `virtualenv" +" .venv`" +msgstr "" + +#: ../../README.md:69 +msgid "Activate the virtual environment: `source .venv/bin/activate`" +msgstr "" + +#: ../../README.md:70 +msgid "" +"Install the required Python packages using " +"[pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" +msgstr "" + +#: ../../README.md:76 +msgid "" +"Ensure the English translation templates ([translation-templates" +"/](translation-templates/)) are extracted: `./bin/extract-translation-" +"templates.sh`" +msgstr "" + +#: ../../README.md:78 +msgid "" +"Update the locale files for your language: `./bin/sync-translation-" +"templates-to-locales.sh `" +msgstr "" + +#: ../../README.md:82 +msgid "Build translated documents: `./bin/build-translated-result.sh `" +msgstr "" + +#: ../../README.md:90 +msgid "Publish translations in a new language" +msgstr "" + +#: ../../README.md:92 +msgid "" +"To publish prebuilt documents translated in a new language to the " +"`translated/` directory:" +msgstr "" + +#: ../../README.md:94 +msgid "" +"add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) " +"file" +msgstr "" + +#: ../../README.md:95 +msgid "" +"whitelist its `translated/` directory by adding a " +"`!translated/` rule to the [.gitignore](.gitignore) file" +msgstr "" + +#: ../../README.md:97 +msgid "" +"💡 Leave a trailing new line at the end of the " +"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." +msgstr "" + +#~ msgid "" +#~ "Currently, we manage translaion of " +#~ "markdown files on the top level " +#~ "directory and inside [`docs`](../docs/), and" +#~ " this file (`README.md`) only." +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ For readers' sake, we set a " +#~ "minimum condition for publishing documents " +#~ "translated in your language: translating " +#~ "basic articles such as READMEs, " +#~ "installation guides ([Quick start](quick-" +#~ "start.md) and the full installation " +#~ "guide which starts at the " +#~ "[Prerequisites](prerequisites.md)), etc. If you " +#~ "think we have missed progress of " +#~ "translation in your language, please " +#~ "ping us at the Matrix room." +#~ msgstr "" + +#~ msgid "Translation guide" +#~ msgstr "" + +#~ msgid "" +#~ "If you are interested in translating " +#~ "this project, please check out our " +#~ "[Weblate project](https://example.com)." +#~ msgstr "" + +#~ msgid "" +#~ "If your language is not yet " +#~ "listed, please express your wishes to" +#~ " start translating it in our [Matrix" +#~ " room](https://matrix.to/#/#matrix-docker-ansible-" +#~ "deploy:devture.com). If anyone else is " +#~ "found to be working on your " +#~ "language, please co-ordinate if needed." +#~ msgstr "" + +#~ msgid "" +#~ "Currently, we manage translaion of " +#~ "markdown files on the top level " +#~ "directory and inside [`docs`](../docs/), and" +#~ " README files only." +#~ msgstr "" + +#~ msgid "" +#~ "Translated files are published and " +#~ "maintained in [`markdown`](../markdown/) directory." +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ For readers' sake, we set a " +#~ "minimum percentage of completion (70%) " +#~ "for publishing documents translated in " +#~ "your language. If you think we " +#~ "have missed progress of translation in" +#~ " your language, please ping us in " +#~ "the Matrix room." +#~ msgstr "" + +#~ msgid "Translation development guide" +#~ msgstr "" + +#~ msgid "Install packages" +#~ msgstr "" + +#~ msgid "" +#~ "To manage files for translation and " +#~ "build translated documents, you need to" +#~ " install packages at first. You can" +#~ " install them with " +#~ "[pip](https://pip.pypa.io/en/stable/)." +#~ msgstr "" + +#~ msgid "" +#~ "After installing pip and activating the" +#~ " virtual environment, run the command " +#~ "below on this directory:" +#~ msgstr "" + +#~ msgid "Update PO files" +#~ msgstr "" + +#~ msgid "" +#~ "If a document is updated, it is" +#~ " necessary to generate updated `.pot` " +#~ "(catalog templates) files and to apply" +#~ " differences to translated `.po` (message" +#~ " catalogs) files." +#~ msgstr "" + +#~ msgid "To do so, run these commands:" +#~ msgstr "" + +#~ msgid "" +#~ "To generate `.po` files for a new" +#~ " language, e.g. Bulgarian, run the " +#~ "command below:" +#~ msgstr "" + +#~ msgid "" +#~ "After the original documents have " +#~ "changed, run [i18n_update.sh](i18n_update.sh) to " +#~ "update `.po` files in all languages " +#~ "specified on [`LANG`](LANG) file:" +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ Unless your language code is " +#~ "added to the `LANG` file, running " +#~ "the script does not generate `.po` " +#~ "files in your language in `locales` " +#~ "directory." +#~ msgstr "" + +#~ msgid "Build" +#~ msgstr "" + +#~ msgid "To build the documentation in English, run the command below:" +#~ msgstr "" + +#~ msgid "It generates Markdown files in `_build/markdown/`." +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ As the original documents are " +#~ "also Markdown files, the generated files" +#~ " in English are identical to the " +#~ "original ones." +#~ msgstr "" + +#~ msgid "To build documents in another language, e.g. Bulgarian, run:" +#~ msgstr "" + +#~ msgid "" +#~ "Running [i18n_build.sh](i18n_build.sh) builds " +#~ "Markdown files in all languages " +#~ "specified on `LANG` file into `markdown`" +#~ " directory:" +#~ msgstr "" + +#~ msgid "Publish documents in a new language" +#~ msgstr "" + +#~ msgid "" +#~ "To publish documents translated in a " +#~ "new language on `markdown` directory, " +#~ "add its language code to `LANG` " +#~ "file. Then, run `i18n_update.sh` and " +#~ "`i18n_build.sh`. After that, you would " +#~ "need to push the documents to the" +#~ " repository." +#~ msgstr "" + +#~ msgid "💡 Leave an empty line at the end of the `LANG` file." +#~ msgstr "" + +#~ msgid "Using the uv package manager and just command runner" +#~ msgstr "" + +#~ msgid "" +#~ "Update the locale files for your " +#~ "language: `just sync-language ` " +#~ "(internally, this automatically runs `just " +#~ "extract-translation-templates` to make " +#~ "sure the translation templates are " +#~ "up-to-date)" +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po new file mode 100644 index 000000000..76931a0b2 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po @@ -0,0 +1,11136 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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" + +#: ../../../CHANGELOG.md:1 +msgid "2024-11-26" +msgstr "" + +#: ../../../CHANGELOG.md:3 +msgid "" +"(Backward Compatibility Break) Synapse now defaults to enabling " +"authenticated media" +msgstr "" + +#: ../../../CHANGELOG.md:5 +msgid "" +"**TLDR**: with this update, your Synapse homeserver will start requiring " +"authentication for newly-uploaded media files. While the majority of the " +"ecosystem (clients, bots, etc.) should support this, certain software may" +" lack support for it (and you may wish to turn it off, if it's causing " +"issues)." +msgstr "" + +#: ../../../CHANGELOG.md:7 +msgid "" +"The default configuration for the Synapse homeserver now [enforces " +"Authenticated media by default](https://element-" +"hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-" +"enforced-by-default)." +msgstr "" + +#: ../../../CHANGELOG.md:9 +msgid "" +"Servers like `matrix.org` have already [sunset unauthenticated " +"media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-" +"media/) months ago." +msgstr "" + +#: ../../../CHANGELOG.md:11 +msgid "" +"Now that **various clients, bots, bridges and extra services have caught " +"up with authenticated media support**, Synapse developers seem confident " +"that it's time to enable authenticated media by default." +msgstr "" + +#: ../../../CHANGELOG.md:13 +msgid "" +"We're changing the playbook configuration for authenticated media to keep" +" up with upstream defaults changing." +msgstr "" + +#: ../../../CHANGELOG.md:15 +msgid "" +"Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not " +"support authenticated media. Other software may be similarly affected. If" +" you experience issues with some Matrix-related software, you may wish to" +" disable authenticated media and contact the software maintainers to let " +"them know." +msgstr "" + +#: ../../../CHANGELOG.md:17 +msgid "" +"You can disable authenticated media at any time by setting " +"`matrix_synapse_enable_authenticated_media: false` in your `vars.yml` " +"configuration file and re-running the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:20 +msgid "2024-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:22 +msgid "" +"(Backward Compatibility Break) The playbook now defaults to Valkey, " +"instead of KeyDB" +msgstr "" + +#: ../../../CHANGELOG.md:24 +msgid "" +"**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for " +"you before, it will now replace it with [Valkey](https://valkey.io/) (a " +"drop-in alternative). We [previously switched from Redis to KeyDB" +"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" +"instead-of-redis), but Valkey is a better alternative, so we're switching" +" again." +msgstr "" + +#: ../../../CHANGELOG.md:26 +msgid "" +"The playbook used to install Redis or KeyDB if services have a need for a" +" Redis-compatible implementation ([enabling worker support for " +"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" +"workers), [enabling Hookshot encryption](docs/configuring-playbook-" +"bridge-hookshot.md#end-to-bridge-encryption), etc.)." +msgstr "" + +#: ../../../CHANGELOG.md:28 +msgid "" +"Earlier this year, we switched from Redis to KeyDB - see [(Backward " +"Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" +"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" +"instead-of-redis)." +msgstr "" + +#: ../../../CHANGELOG.md:30 +msgid "" +"Because Valkey seems to be a better successor to Redis (than KeyDB) and " +"likely doesn't suffer from [issues like this " +"one](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3544), we now replace KeyDB with Valkey." +msgstr "" + +#: ../../../CHANGELOG.md:32 +msgid "" +"Valkey (like KeyDB and Redis in the past) is an implicitly enabled " +"dependency - you don't need custom configuration in `vars.yml` to enable " +"it." +msgstr "" + +#: ../../../CHANGELOG.md:34 +msgid "" +"Next time your run the playbook (via the `setup-all` tag), **KeyDB will " +"be automatically uninstalled and replaced with Valkey**. Some Synapse " +"downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:36 +msgid "" +"Users on `arm32` should be aware that there's **neither a prebuilt " +"`arm32` container image for Valkey**, nor the Valkey role supports self-" +"building yet. Users on this architecture likely don't run Synapse with " +"workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). " +"If Redis is necessary in an `arm32` deployment, disabling Valkey and " +"making the playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378 +msgid "" +"**The playbook still supports Redis** and you can keep using Redis (for " +"now) if you'd like, by adding this additional configuration to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:49 +msgid "" +"**The playbook still supports KeyDB** and you can keep using KeyDB (for " +"now) if you'd like, by adding this additional configuration to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:59 +msgid "" +"At some point in time in the future, we'll remove both KeyDB and Redis " +"from the playbook, so we recommend that you migrate to Valkey earlier " +"anyway." +msgstr "" + +#: ../../../CHANGELOG.md:62 +msgid "2024-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:64 +msgid "HTTP-compression support for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:66 +msgid "" +"The playbook now **automatically enables HTTP-compression support** for " +"major services powered by the playbook, like [Cinny](./docs/configuring-" +"playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-" +"client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-" +"hydrogen.md), as well as for Matrix Client-Server and Federation APIs " +"(`matrix.example.com`)." +msgstr "" + +#: ../../../CHANGELOG.md:68 +msgid "" +"Other services installed by the playbook are currently not compression-" +"enabled, but may become so over time. This change is rolled out on a per-" +"service basis (as opposed to doing it globally, at the Traefik entrypoint" +" level) to allow certain services or route endpoints which do not behave " +"well when compressed (e.g. [issue 3749](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/issues/3749)) to be excluded from " +"compression." +msgstr "" + +#: ../../../CHANGELOG.md:70 +msgid "" +"A long time ago, various services were operating with `gzip`-compression " +"enabled at the nginx level. Since the switch to Traefik (see [Goodbye, " +"`matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md" +"#goodbye-matrix-nginx-proxy-)), all services (with the exception of " +"Matrix APIs for Synapse worker-enabled setups which are powered by " +"`nginx` via `synapse-reverse-proxy-companion`) have been operating " +"without HTTP-compression support." +msgstr "" + +#: ../../../CHANGELOG.md:72 +msgid "" +"HTTP-compression is now done via Traefik's " +"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " +"middleware. We use the default configuration for this middleware, which " +"enables `zstd`, `br` and `gzip` support (in this order). This " +"middleware's configuration can be configured via variables in the Traefik" +" role (see " +"`traefik_config_http_middlewares_compression_middleware_options`)." +msgstr "" + +#: ../../../CHANGELOG.md:74 +msgid "" +"If you're using your own Traefik reverse-proxy server ([Traefik managed " +"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" +"you)) instead of the playbook's integrated Traefik service, you can " +"benefit from the same by:" +msgstr "" + +#: ../../../CHANGELOG.md:76 +msgid "" +"defining a " +"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " +"middleware (via the " +"[file](https://doc.traefik.io/traefik/providers/file/) or " +"[Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" +msgstr "" + +#: ../../../CHANGELOG.md:77 +msgid "" +"setting " +"`matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to" +" `true`" +msgstr "" + +#: ../../../CHANGELOG.md:78 +msgid "" +"specifying the middleware's name in " +"`matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g." +" `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-" +"compression-middleware@file`)" +msgstr "" + +#: ../../../CHANGELOG.md:80 +msgid "Timeout adjustments for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:82 +msgid "" +"The playbook now supports configuring various " +"[transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts)" +" timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the " +"`web`, `web-secure` and `matrix-federation` entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:84 +msgid "" +"If you're using your own Traefik reverse-proxy server ([Traefik managed " +"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" +"you)) instead of the playbook's integrated Traefik service, you may wish " +"to do similar configuration changes to your setup manually." +msgstr "" + +#: ../../../CHANGELOG.md:86 +msgid "" +"The most interesting of these is the `readTimeout` configuration value " +"(the maximum duration for reading the entire request, including the " +"body), which used to default to `60s`. For large and slowly progressing " +"file uploads, `60s` would often not be enough for the transfer to finish " +"and uploads would end up being interrupted. The playbook now raises the " +"`readTimeout` value to 5 minutes (`300s`) to improve this use-case." +msgstr "" + +#: ../../../CHANGELOG.md:88 +msgid "" +"The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` " +"variables (for the `web` entrypoint) cascade to affecting the timeout " +"values for the `web-secure` and `matrix-federation` entrypoints, so you " +"can easily adjust all timeout values using them." +msgstr "" + +#: ../../../CHANGELOG.md:90 +msgid "Example of the default timeout values used by the playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:101 +msgid "" +"Alternatively, you may adjust the timeout values for specific entrypoints" +" (like `web-secure` and `matrix-federation`) using dedicated variables " +"(like " +"`traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout`" +" and " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." +msgstr "" + +#: ../../../CHANGELOG.md:104 +msgid "2024-11-08" +msgstr "" + +#: ../../../CHANGELOG.md:106 +msgid "" +"Support for synapse-admin auto-configuration via /.well-" +"known/matrix/client" +msgstr "" + +#: ../../../CHANGELOG.md:108 +msgid "" +"You can administrate your Synapse-powered homeserver using synapse-admin " +"hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the " +"synapse-admin instance would still auto-configure itself correctly for " +"your server by [reading its `/.well-known/matrix/client` " +"file](https://github.com/etkecc/synapse-admin/pull/126)." +msgstr "" + +#: ../../../CHANGELOG.md:110 +msgid "" +"The playbook now configures the `/.well-known/matrix/client` file for " +"this by default, injecting into it a `cc.etke.synapse-admin` section that" +" contains the full synapse-admin configuration. This is done even if you " +"don't enable the synapse-admin service in your configuration. The reason " +"for always doing it is to allow users to skip the (small) overhead of " +"self-hosting the non-core synapse-admin service, yet still be able to use" +" it from elsewhere when needed." +msgstr "" + +#: ../../../CHANGELOG.md:112 +msgid "" +"If you don't ever plan on using synapse-admin from other servers (besides" +" your own due to [self-hosting synapse-admin](./docs/configuring-" +"playbook-synapse-admin.md)), you **can disable this** `/.well-" +"known/matrix/client` configuration via " +"`matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled:" +" false`" +msgstr "" + +#: ../../../CHANGELOG.md:115 +msgid "2024-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:117 +msgid "(BC Break) Postmoogle's variable names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:119 +msgid "" +"Due to the recategorization of [Postmoogle](./docs/configuring-playbook-" +"bridge-postmoogle.md) from the bot to the bridge, its variables were " +"renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to " +"adjust your `vars.yml` configuration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:121 +msgid "2024-10-19" +msgstr "" + +#: ../../../CHANGELOG.md:123 +msgid "Support for Matrix Authentication Service" +msgstr "" + +#: ../../../CHANGELOG.md:125 +msgid "" +"The playbook now supports installing and configuring [Matrix " +"Authentication Service](./docs/configuring-playbook-matrix-" +"authentication-service.md) (MAS)." +msgstr "" + +#: ../../../CHANGELOG.md:127 +msgid "" +"Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the " +"[Element](https://element.io/) / [Matrix Authentication " +"Service](https://github.com/element-hq/matrix-authentication-service) " +"team for answering our numerous questions about MAS." +msgstr "" + +#: ../../../CHANGELOG.md:129 +msgid "" +"This is an **experimental service** and there are **still certain issues " +"with it** (see [Expectations](./docs/configuring-playbook-matrix-" +"authentication-service.md#expectations)). Matrix server administrators " +"should only consider switching if they identify with one or more [reasons" +" to use Matrix Authentication Service](./docs/configuring-playbook-" +"matrix-authentication-service.md#reasons-to-use-matrix-authentication-" +"service). As MAS adoption improves and more services are adjusted to " +"support it, we expect that using MAS will become the norm." +msgstr "" + +#: ../../../CHANGELOG.md:131 +msgid "" +"Our [Setting up Matrix Authentication Service](./docs/configuring-" +"playbook-matrix-authentication-service.md) documentation page has more " +"details about this new service, what you might expect from the switch and" +" how you can migrate your existing (Synapse) homeserver setup to MAS." +msgstr "" + +#: ../../../CHANGELOG.md:134 +msgid "2024-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:136 +msgid "" +"(BC Break) Postgres & Traefik roles have been relocated and variable " +"names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:138 +msgid "" +"Various roles have been relocated from the " +"[devture](https://github.com/devture) organization to the [mother-of-all-" +"self-hosting](https://github.com/mother-of-all-self-hosting) " +"organization." +msgstr "" + +#: ../../../CHANGELOG.md:140 +msgid "" +"Along with the relocation, the `devture_` prefix was dropped from their " +"variable names, so you need to adjust your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:142 +msgid "You need to do the following replacements:" +msgstr "" + +#: ../../../CHANGELOG.md:144 +msgid "`devture_postgres_` -> `postgres_`" +msgstr "" + +#: ../../../CHANGELOG.md:145 +msgid "`devture_traefik_` -> `traefik_`" +msgstr "" + +#: ../../../CHANGELOG.md:147 +msgid "" +"As always, the playbook would let you know about this and point out any " +"variables you may have missed." +msgstr "" + +#: ../../../CHANGELOG.md:150 +msgid "2024-09-12" +msgstr "" + +#: ../../../CHANGELOG.md:152 +msgid "Support for baibot" +msgstr "" + +#: ../../../CHANGELOG.md:154 +msgid "" +"The playbook now supports installing [baibot](./docs/configuring-" +"playbook-bot-baibot.md) (pronounced bye-bot) - a " +"[Matrix](https://matrix.org/) bot developed by " +"[etke.cc](https://etke.cc/) that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you. 🤖" +msgstr "" + +#: ../../../CHANGELOG.md:156 +msgid "" +"It supports [OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other" +" [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../CHANGELOG.md:158 +msgid "" +"It's designed as a more private and [✨ " +"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" +"file#-features) alternative to the now-unmaintained [matrix-chatgpt-" +"bot](./docs/configuring-playbook-bot-chatgpt.md)." +msgstr "" + +#: ../../../CHANGELOG.md:160 +msgid "" +"To get started, see the [Setting up baibot](./docs/configuring-playbook-" +"bot-baibot.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:162 +msgid "Switching synapse-admin to etke.cc's fork" +msgstr "" + +#: ../../../CHANGELOG.md:164 +msgid "" +"The playbook now installs [etke.cc](https://etke.cc/)'s " +"[fork](https://github.com/etkecc/synapse-admin) of [synapse-" +"admin](https://github.com/Awesome-Technologies/synapse-admin) (originally" +" developed by [Awesome-Technologies](https://github.com/Awesome-" +"Technologies)). This fork is a drop-in replacement for the original " +"software." +msgstr "" + +#: ../../../CHANGELOG.md:166 +msgid "" +"The creation of the fork has been provoked by users frequently " +"encountering issues with the original synapse-admin software, such as " +"unintentionally deleting their one-and-only admin user account (fixed " +"[here](https://github.com/etkecc/synapse-admin/pull/1) and also " +"contributed upstream [here](https://github.com/Awesome-Technologies" +"/synapse-admin/pull/608) - to no avail for now). Since its inception, [a " +"bunch of other quality-of-life improvements](https://github.com/etkecc" +"/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." +msgstr "" + +#: ../../../CHANGELOG.md:168 +msgid "" +"If upstream synapse-admin picks up the pace and improves, the etke.cc " +"fork may disappear and the playbook may switch to the original software " +"again. Until that time comes, we believe that etke.cc's fork is the " +"better software to use right now." +msgstr "" + +#: ../../../CHANGELOG.md:170 +msgid "" +"If you'd like to switch back to the original synapse-admin software, you " +"can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:183 +msgid "2024-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:185 +msgid "New appservice-double-puppet service for better double-puppeting" +msgstr "" + +#: ../../../CHANGELOG.md:187 +msgid "" +"Mautrix bridges are undergoing large changes as announced in the [August " +"2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) " +"blog post." +msgstr "" + +#: ../../../CHANGELOG.md:189 +msgid "" +"The playbook has already upgraded to the rewritten mautrix-slack " +"([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and " +"mautrix-signal " +"([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) " +"bridges." +msgstr "" + +#: ../../../CHANGELOG.md:191 +msgid "" +"The newly rewritten bridges do not support double-puppeting via [Shared " +"Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, " +"which has prompted us to switch to the new & better [appservice " +"method](https://docs.mau.fi/bridges/general/double-puppeting.html" +"#appservice-method-new) for double-puppeting. The playbook automates this" +" double-puppeting setup for you if you enable the new [Appservice Double " +"Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." +msgstr "" + +#: ../../../CHANGELOG.md:193 +msgid "" +"All non-deprecated mautrix bridges in the playbook have been reworked to " +"support double-puppeting via an Appservice. Most bridges still support " +"double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-" +"shared-secret-auth.md), so the playbook supports it too. If only Shared " +"Secret Auth is enabled, double-puppeting will be configured using that " +"method (for the bridges that support it). That said, **Shared Secret Auth" +" double-puppeting is being phased out and we recommend replacing it with " +"the new Appservice method**." +msgstr "" + +#: ../../../CHANGELOG.md:195 +msgid "" +"We recommend **enabling double-puppeting via the new Appservice method** " +"by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:201 +msgid "" +"You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-" +"shared-secret-auth.md) enabled. Non-mautrix bridges and other services " +"(e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) " +"may still require it." +msgstr "" + +#: ../../../CHANGELOG.md:203 +msgid "" +"When both double-puppeting methods are enabled, the playbook will " +"automatically choose the new and better Appservice method for bridges " +"that support it." +msgstr "" + +#: ../../../CHANGELOG.md:206 +msgid "2024-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:208 +msgid "matrix-media-repo now configured for Authenticated Media" +msgstr "" + +#: ../../../CHANGELOG.md:210 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), our matrix-media-repo implementation now " +"automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-" +"repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per " +"[MSC3916](https://github.com/matrix-org/matrix-spec-" +"proposals/pull/3916))." +msgstr "" + +#: ../../../CHANGELOG.md:212 +msgid "" +"If you had never heard of Authenticated Media before, the [Sunsetting " +"unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-" +"unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a" +" good introduction." +msgstr "" + +#: ../../../CHANGELOG.md:214 +msgid "" +"This feature is enabled for matrix-media-repo installations by default " +"and will append an additional (matrix-media-repo-generated signing key) " +"to your homeserver's (Synapse or Dendrite) signing key. See the [Signing " +"keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and " +"[Key backup and revoking](./docs/configuring-playbook-matrix-media-" +"repo.md#key-backup-and-revoking) sections of the matrix-media-repo " +"documentation for more details." +msgstr "" + +#: ../../../CHANGELOG.md:216 +msgid "" +"If you'd like to avoid this new feature, you can disable it by setting " +"`matrix_media_repo_generate_signing_key: false` in your `vars.yml` " +"configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:219 +msgid "2024-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:221 +msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" +msgstr "" + +#: ../../../CHANGELOG.md:223 +msgid "" +"The playbook now installs [matrix-corporal](https://github.com/devture" +"/matrix-corporal) v3.0.0, which brings support for **power-level " +"management** (thanks to [this PR](https://github.com/devture/matrix-" +"corporal/pull/32))." +msgstr "" + +#: ../../../CHANGELOG.md:225 +msgid "" +"This upgrade necessitates configuration policy changes as described in " +"[matrix-corporal's changelog entry](https://github.com/devture/matrix-" +"corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." +msgstr "" + +#: ../../../CHANGELOG.md:227 +msgid "" +"If you'd like to remain on the old (v2) version of matrix-corporal, you " +"can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:233 +msgid "2024-07-25" +msgstr "" + +#: ../../../CHANGELOG.md:235 +msgid "synapse-usage-exporter support" +msgstr "" + +#: ../../../CHANGELOG.md:237 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook can now set up [synapse-usage-" +"exporter](https://github.com/loelkes/synapse-usage-exporter) - a small " +"[Flask](https://flask.palletsprojects.com)-based webservice which can " +"capture usage statistics from Synapse (via HTTP `PUT`) and then make them" +" available for Prometheus to scrape." +msgstr "" + +#: ../../../CHANGELOG.md:239 +msgid "" +"To learn more see our [Enabling synapse-usage-exporter for Synapse usage " +"statistics](docs/configuring-playbook-synapse-usage-exporter.md) " +"documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:242 +msgid "2024-07-06" +msgstr "" + +#: ../../../CHANGELOG.md:244 +msgid "matrix-alertmanager-receiver support" +msgstr "" + +#: ../../../CHANGELOG.md:246 +msgid "" +"For those wishing to more easily integrate " +"[Prometheus](https://prometheus.io/)' alerting service " +"([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/))" +" with Matrix, the playbook can now set up [matrix-alertmanager-" +"receiver](https://github.com/metio/matrix-alertmanager-receiver)." +msgstr "" + +#: ../../../CHANGELOG.md:248 +msgid "" +"See [Setting up Prometheus Alertmanager integration via matrix-" +"alertmanager-receiver](./docs/configuring-playbook-alertmanager-" +"receiver.md) for more details." +msgstr "" + +#: ../../../CHANGELOG.md:250 +msgid "Traefik v3 and HTTP/3 are here now" +msgstr "" + +#: ../../../CHANGELOG.md:252 +msgid "" +"**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to " +"the playbook. Mostly everything else worked out of the box. Most people " +"will not have to do any tweaks to their configuration. In addition, " +"[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-" +"enabled for the `web-secure` (port 443) and `matrix-federation` (port " +"`8448`) entrypoints. If you have a firewall in front of your server and " +"you wish to benefit from `HTTP3`, you will need to open the `443` and " +"`8448` UDP ports in it." +msgstr "" + +#: ../../../CHANGELOG.md:254 +msgid "Traefik v3" +msgstr "" + +#: ../../../CHANGELOG.md:256 +msgid "" +"The reverse-proxy that the playbook uses by default (Traefik) has " +"recently been upgraded to v3 (see [this blog " +"post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn " +"about its new features). Version 3 includes some small breaking " +"configuration changes requiring a " +"[migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:258 +msgid "" +"We have **updated the playbook to Traefik v3** (make sure to run `just " +"roles` / `make roles` to get it)." +msgstr "" + +#: ../../../CHANGELOG.md:260 +msgid "" +"There were **only minor playbook changes required** to adapt to Traefik " +"v3, and only to the Ansible role for [matrix-media-repo](./docs" +"/configuring-playbook-matrix-media-repo.md) where we changed a few " +"[`PathPrefix` instances to " +"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" +"pathprefix-and-pathregexp), because these instances were using a regular " +"expression instead of a fixed path. For fixed-path values, `PathPrefix` " +"is still the preferred matcher function to use." +msgstr "" + +#: ../../../CHANGELOG.md:262 +msgid "**Most people using the playbook should not have to do any changes**." +msgstr "" + +#: ../../../CHANGELOG.md:264 +msgid "" +"If you're using the playbook's Traefik instance to reverse-proxy to some " +"other services of your own (not managed by the playbook), you may wish to" +" review their Traefik labels and make sure they're in line with the " +"[Traefik v2 to v3 migration " +"guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:266 +msgid "" +"If you've tweaked any of this playbook's `_path_prefix` variables and " +"made them use a regular expression, you will now need to make additional " +"adjustments. The playbook makes extensive use of `PathPrefix()` matchers " +"in Traefik rules and `PathPrefix` does not support regular expressions " +"anymore. To work around it, you may now need to override a whole " +"`_traefik_rule` variable and switch it from [`PathPrefix` to " +"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" +"pathprefix-and-pathregexp)." +msgstr "" + +#: ../../../CHANGELOG.md:268 +msgid "" +"If you're not using [matrix-media-repo](./docs/configuring-playbook-" +"matrix-media-repo.md) (the only role we had to tweak to adapt it to " +"Traefik v3), you **may potentially downgrade to Traefik v2** (if " +"necessary) by adding `traefik_verison: v2.11.4` to your configuration. " +"People using `matrix-media-repo` cannot downgrade this way, because " +"`matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing " +"matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that" +" Traefik v2 does not understand." +msgstr "" + +#: ../../../CHANGELOG.md:270 +msgid "HTTP/3 is enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:272 +msgid "" +"In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is " +"no longer considered experimental now. Due to this, **the playbook auto-" +"enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` " +"(port `8448`) entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:274 +msgid "" +"HTTP3 uses the UDP protocol and **the playbook (together with Docker) " +"will make sure that the appropriate ports** (`443` over UDP & `8448` over" +" UDP) **are exposed and whitelisted in your server's firewall**. However," +" **if you have another firewall in front of your server** (as is the case" +" for many cloud providers), **you will need to manually open these UDP " +"ports**." +msgstr "" + +#: ../../../CHANGELOG.md:276 +msgid "" +"If you do not open the UDP ports correctly or there is some other issue, " +"clients (browsers, mostly) will fall-back to " +"[HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even " +"[HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." +msgstr "" + +#: ../../../CHANGELOG.md:278 +msgid "" +"Still, if HTTP/3 cannot function correctly in your setup, it's best to " +"disable advertising support for it (and misleading clients into trying to" +" use HTTP/3)." +msgstr "" + +#: ../../../CHANGELOG.md:280 +msgid "To **disable HTTP/3**, you can use the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:294 +msgid "" +"If you are using [your own webserver](./docs/configuring-playbook-own-" +"webserver.md) (in front of Traefik), port binding on UDP port `8448` by " +"default due to HTTP/3 is either unnecessary or [may get in the " +"way](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3402). If it does, you can disable it:" +msgstr "" + +#: ../../../CHANGELOG.md:307 +msgid "2024-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:309 +msgid "synapse-admin is now restricted to your homeserver's URL by default" +msgstr "" + +#: ../../../CHANGELOG.md:311 +msgid "" +"A new feature introduced in synapse-admin [v0.10.0](https://github.com" +"/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and " +"supported by the playbook since a a few months ago) provides the ability " +"to [restrict its usage to a specific homeserver](https://github.com" +"/Awesome-Technologies/synapse-" +"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" +"#restricting-available-homeserver) (or multiple homeservers)." +msgstr "" + +#: ../../../CHANGELOG.md:313 +msgid "" +"The playbook has just started making use of this feature. **From now on, " +"your synapse-admin instance will be restricted to the homeserver you're " +"managing via the playbook**. When configured like this, the *Homeserver " +"URL* field in synapse-admin's web UI changes from a text field to a " +"dropdown having a single value (the URL of your homeserver). This makes " +"usage simpler for most people, as they won't need to manually enter a " +"*Homeserver URL* anymore." +msgstr "" + +#: ../../../CHANGELOG.md:315 +msgid "" +"If you'd like **to go back to the old unrestricted behavior**, use the " +"following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:323 +msgid "2024-06-25" +msgstr "" + +#: ../../../CHANGELOG.md:325 +msgid "The URL-prefix for Hookshot generic webhooks has changed" +msgstr "" + +#: ../../../CHANGELOG.md:327 +msgid "" +"Until now, generic Hookshot webhook URLs looked like this: " +"`https://matrix.example.com/hookshot/webhooks/:hookId`." +msgstr "" + +#: ../../../CHANGELOG.md:329 +msgid "" +"The `/hookshot/webhooks` common prefix gets stripped by Traefik " +"automatically, so Hookshot only sees the part that comes after " +"(`/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:331 +msgid "" +"[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1681), Hookshot started to prefer to handle webhooks at a " +"`/webhook/:hookId` path (instead of directly at `/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:333 +msgid "" +"To avoid future problems, we've " +"[reconfigured](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot " +"configuration to use webhook URLs that include `/webhook` in the URL " +"suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of " +"`/hookshot/webhooks/:hookId`). This means that when we strip the common " +"prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to " +"Hookshot, just like recommended." +msgstr "" + +#: ../../../CHANGELOG.md:335 +msgid "" +"When generating new webhooks, you should start seeing the new URLs being " +"used." +msgstr "" + +#: ../../../CHANGELOG.md:337 +msgid "" +"**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new " +"URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your" +" webhooks will not break just yet." +msgstr "" + +#: ../../../CHANGELOG.md:339 +msgid "" +"However, **we recommend that you update all your old webhook URLs** " +"(configured in other systems) to include the new `/webhook` path " +"component, so that future Hookshot changes (whenever they come) will not " +"break your webhooks. You don't need to do anything on the Hookshot side -" +" you merely need to reconfigure the remote systems that use your webhook " +"URLs." +msgstr "" + +#: ../../../CHANGELOG.md:342 +msgid "2024-06-22" +msgstr "" + +#: ../../../CHANGELOG.md:344 +msgid "The maubot user is now managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:346 +msgid "" +"To make things easier and to be consistent with other roles, the " +"[maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by" +" default) is [now](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3376) automatically created be the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:348 +msgid "" +"If you have an existing maubot installation, you will need to specify " +"`matrix_bot_maubot_initial_password` in your `vars.yml` file to make the " +"playbook not complain about it being undefined. Since the bot is already " +"registered in your installation, there's nothing for the playbook to do " +"anyway. In case you don't remember the password you've registered your " +"maubot user account with, you can specify any value for this variable." +msgstr "" + +#: ../../../CHANGELOG.md:350 +msgid "" +"If you've registered another username for the bot (other than the " +"recommended default of `bot.maubot`), consider adjusting the " +"`matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: " +"my.maubot.username`)." +msgstr "" + +#: ../../../CHANGELOG.md:353 +msgid "2024-06-03" +msgstr "" + +#: ../../../CHANGELOG.md:355 +msgid "WeChat bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:357 +msgid "" +"Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s " +"[efforts](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3241), the playbook now supports bridging to " +"[WeChat](https://www.wechat.com/) via the [matrix-" +"wechat](https://github.com/duo/matrix-wechat) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:359 +msgid "" +"See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-" +"wechat.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:362 +msgid "2024-03-26" +msgstr "" + +#: ../../../CHANGELOG.md:364 +msgid "" +"(Backward Compatibility Break) The playbook now defaults to KeyDB, " +"instead of Redis" +msgstr "" + +#: ../../../CHANGELOG.md:366 +msgid "" +"**TLDR**: if the playbook used installed Redis as a dependency for you " +"before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a " +"drop-in alternative) due to [Redis having changed its " +"license](https://redis.com/blog/redis-adopts-dual-source-available-" +"licensing/)." +msgstr "" + +#: ../../../CHANGELOG.md:368 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook now uses " +"[KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), " +"instead of [Redis](https://redis.io/)." +msgstr "" + +#: ../../../CHANGELOG.md:370 +msgid "" +"The playbook used to install Redis (and now installs KeyDB in its place) " +"if services have a need for it ([enabling worker support for " +"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" +"workers), [enabling Hookshot encryption](docs/configuring-playbook-" +"bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly " +"enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." +msgstr "" + +#: ../../../CHANGELOG.md:372 +msgid "" +"This change is provoked by the fact that [Redis is now \"source " +"available\"](https://redis.com/blog/redis-adopts-dual-source-available-" +"licensing/). According to the Limitations of [the new " +"license](https://redis.com/legal/rsalv2-agreement/) (as best as we " +"understand them, given that we're not lawyers), using Redis in the " +"playbook (even in a commercial FOSS service like " +"[etke.cc](https://etke.cc/)) does not violate the new Redis license. That" +" said, we'd rather neither risk it, nor endorse shady licenses and " +"products that pretend to be free-software. Another high-quality " +"alternative to Redis seems to be " +"[Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly " +"license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-" +"file#readme) is no better than Redis's." +msgstr "" + +#: ../../../CHANGELOG.md:374 +msgid "" +"Next time your run the playbook (via the `setup-all` tag), **Redis will " +"be automatically uninstalled and replaced with KeyDB**. Some Synapse " +"downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:376 +msgid "" +"Users on `arm32` should be aware that there's **neither a prebuilt " +"`arm32` container image for KeyDB**, nor the KeyDB role supports self-" +"building yet. Users on this architecture likely don't run Synapse with " +"workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis" +" is necessary in an `arm32` deployment, disabling KeyDB and making the " +"playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:387 +msgid "2024-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:389 +msgid "Initial work on IPv6 support" +msgstr "" + +#: ../../../CHANGELOG.md:391 +msgid "" +"Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can " +"now enable IPv6 for container networks for various components (roles) via" +" [the `devture_systemd_docker_base_ipv6_enabled` " +"variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." +msgstr "" + +#: ../../../CHANGELOG.md:393 +msgid "It should be noted that:" +msgstr "" + +#: ../../../CHANGELOG.md:395 +msgid "" +"Matrix roles (`roles/custom/matrix-*`) respect this variable, but " +"external roles (those defined in `requirements.yml` and installed via " +"`just roles`) do not respect it yet. Additional work is necessary" +msgstr "" + +#: ../../../CHANGELOG.md:396 +msgid "" +"changing the variable subsequently may not change existing container " +"networks. Refer to [these " +"instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" +msgstr "" + +#: ../../../CHANGELOG.md:397 +msgid "this is all very new and untested" +msgstr "" + +#: ../../../CHANGELOG.md:399 +msgid "Pantalaimon support" +msgstr "" + +#: ../../../CHANGELOG.md:401 +msgid "" +"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " +"playbook can now install the [Pantalaimon](https://github.com/matrix-" +"org/pantalaimon) E2EE aware proxy daemon for you. It's already possible " +"to integrate it with [Draupnir](docs/configuring-playbook-bot-" +"draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs " +"for details." +msgstr "" + +#: ../../../CHANGELOG.md:403 +msgid "" +"See our [Setting up Pantalaimon](docs/configuring-playbook-" +"pantalaimon.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:406 +msgid "2024-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:408 +msgid "Support for Draupnir-for-all" +msgstr "" + +#: ../../../CHANGELOG.md:410 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " +"install [Draupnir for all](./docs/configuring-playbook-appservice-" +"draupnir-for-all.md) (aka multi-instance Draupnir running in appservice " +"mode)." +msgstr "" + +#: ../../../CHANGELOG.md:412 +msgid "" +"This is an alternative to [running Draupnir in bot mode](./docs" +"/configuring-playbook-bot-draupnir.md), which is still supported by the " +"playbook." +msgstr "" + +#: ../../../CHANGELOG.md:414 +msgid "" +"The documentation page for [Draupnir for all](./docs/configuring-" +"playbook-appservice-draupnir-for-all.md) contains more information on how" +" to install it." +msgstr "" + +#: ../../../CHANGELOG.md:417 +msgid "2024-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:419 +msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge" +msgstr "" + +#: ../../../CHANGELOG.md:421 +msgid "" +"The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-" +"facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-" +"mautrix-instagram.md) bridges are being [superseded by a new " +"bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-" +"meta](https://github.com/mautrix/meta) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:423 +msgid "" +"The playbook now supports the new mautrix-meta bridge - a single bridge, " +"which can run in different modes and bridge to Messenger (via " +"[Facebook](https://facebook.com/), Facebook over " +"[Tor](https://www.torproject.org/) or via " +"[Messenger](https://messenger.com/)) and " +"[Instagram](https://instagram.com/). The playbook makes this bridge " +"available via 2 separate Ansible roles, allowing you to easily run 2 " +"instances of mautrix-meta, for bridging to both services at the same " +"time." +msgstr "" + +#: ../../../CHANGELOG.md:425 +msgid "" +"If you're using mautrix-facebook or mautrix-instagram right now, **you " +"can still continue using the old bridges, but may wish to change to the " +"new bridge implementations**. See:" +msgstr "" + +#: ../../../CHANGELOG.md:427 +msgid "" +"[Setting up Instagram bridging via Mautrix Meta](docs/configuring-" +"playbook-bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../CHANGELOG.md:429 +msgid "" +"[Setting up Messenger bridging via Mautrix Meta](docs/configuring-" +"playbook-bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../CHANGELOG.md:431 +msgid "The documentation pages contain more information on how to migrate." +msgstr "" + +#: ../../../CHANGELOG.md:434 +msgid "2024-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:436 +msgid "Much larger Synapse caches and cache auto-tuning enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:438 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses " +"much larger caches and enables Synapse's [cache auto-tuning " +"functionality](https://matrix-" +"org.github.io/synapse/latest/usage/configuration/config_documentation.html" +"#caches-and-associated-values). This work and the default values used by " +"the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s " +"[Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." +msgstr "" + +#: ../../../CHANGELOG.md:440 +msgid "" +"The playbook has always used a very conservative cache factor " +"(`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK " +"for small and underactive deployments, but is not ideal for larger " +"servers. Paradoxically, a small global cache factor value [does not " +"necessarily decrease RAM usage as a whole](https://github.com/matrix-" +"org/synapse/issues/3939)." +msgstr "" + +#: ../../../CHANGELOG.md:442 +msgid "" +"The playbook now uses **a 20x larger cache factor** (currently `10`), " +"adjusts a few other cache-related variables, and **enables cache auto-" +"tuning** via the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:444 +msgid "" +"`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to " +"1/8 of total RAM with a cap of 2GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:445 +msgid "" +"`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to" +" 1/16 of total RAM with a cap of 1GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:446 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../CHANGELOG.md:448 +msgid "" +"These values should be good defaults for most servers, but may change " +"over time as we experiment further." +msgstr "" + +#: ../../../CHANGELOG.md:450 +msgid "" +"Refer to our new [Tuning caches and cache autotuning](docs/maintenance-" +"synapse.md#tuning-caches-and-cache-autotuning) documentation section for " +"more details." +msgstr "" + +#: ../../../CHANGELOG.md:453 +msgid "2024-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:455 +msgid "" +"(Backward-compatibility break) Minor changes necessary for some people " +"serving a static website at the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:457 +msgid "" +"This only affects people who are [Serving a static website at the base " +"domain](./docs/configuring-playbook-base-domain-serving.md#serving-a" +"-static-website-at-the-base-domain), but not managing its `index.html` " +"through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:459 +msgid "" +"That is, for people who have " +"`matrix_static_files_file_index_html_enabled: false` in their `vars.yml` " +"configuration, the playbook has a new default behavior. Since the " +"playbook is not managing the `index.html` file, it will default to a more" +" sensible way of handling the base domain - redirecting " +"`https://example.com/` to `https://matrix.example.com/`, instead of " +"serving a 404 page." +msgstr "" + +#: ../../../CHANGELOG.md:461 +msgid "" +"If you are managing your static website by yourself (by dropping files " +"into `/matrix/static-files/public` somehow), then you probably don't wish" +" for such redirection to happen. You can disable it by adding " +"`matrix_static_files_container_labels_base_domain_root_path_redirection_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:464 +msgid "2024-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:466 +msgid "Support for more efficient (specialized) Synapse workers" +msgstr "" + +#: ../../../CHANGELOG.md:468 +msgid "" +"Thanks to [Charles Wright](https://github.com/cvwright) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook has [received " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3100) for load-balancing the Synapse workload via " +"[specialized workers](./docs/configuring-playbook-synapse.md#specialized-" +"workers) which are supposed to work better than our old [generic " +"workers](./docs/configuring-playbook-synapse.md#generic-workers) " +"implementation." +msgstr "" + +#: ../../../CHANGELOG.md:470 +msgid "" +"For now, playbook defaults remain unchanged and the `one-of-each` " +"[workers preset](./docs/configuring-playbook-synapse.md#worker-presets) " +"continues being the default. However, the default may change in the " +"future. If you'd like to remain on this preset even if/when the defaults " +"change, consider explicitly adding `matrix_synapse_workers_preset: one-" +"of-each` to your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:472 +msgid "" +"Our specialized workers setup is based on recommendations found in [Tom " +"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/index.html). What's special " +"about our new setup is that we try to parse information out of the " +"request (who the user is; which room is being operated on) and try to " +"forward similar requests to the same worker. As an example, this means " +"that once a worker caches some room information, subsequent requests for " +"the same room will be routed to the same worker (which supposedly still " +"has the room's state cached)." +msgstr "" + +#: ../../../CHANGELOG.md:474 +msgid "" +"To get started, refer to our [Specialized workers](./docs/configuring-" +"playbook-synapse.md#specialized-workers) documentation section." +msgstr "" + +#: ../../../CHANGELOG.md:477 +msgid "2024-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:479 +msgid "Switching to Element's AGPLv3-licensed Synapse release" +msgstr "" + +#: ../../../CHANGELOG.md:481 +msgid "" +"A few months ago, the [Element](https://element.io/) company has " +"[announced](https://element.io/blog/element-to-adopt-agplv3/) that their " +"work on the Synapse homeserver would no longer be available under the " +"permissive [Apache-2.0 " +"license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" +msgstr "" + +#: ../../../CHANGELOG.md:483 +msgid "" +"the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software" +" license - the same license that this Ansible playbook has always used" +msgstr "" + +#: ../../../CHANGELOG.md:484 +msgid "" +"a proprietary license, for those wishing for Element to [sell them an " +"exception](https://gnu.org/philosophy/selling-exceptions.html) to the " +"AGPLv3 license" +msgstr "" + +#: ../../../CHANGELOG.md:486 +msgid "" +"You can also learn more in [this post](https://matrix.org/blog/2023/11/06" +"/future-of-synapse-dendrite/) by the Matrix Foundation." +msgstr "" + +#: ../../../CHANGELOG.md:488 +msgid "" +"The change has [already happened](https://element.io/blog/synapse-now-" +"lives-at-github-com-element-hq-synapse/) and the first Synapse release " +"under the new license is here: [v1.99.0](https://github.com/element-" +"hq/synapse/releases/tag/v1.99.0)." +msgstr "" + +#: ../../../CHANGELOG.md:490 +msgid "" +"There is no up-to-date alternative Synapse fork right now and this free-" +"software (AGPLv3-licensed) playbook is definitely not against free-" +"software licenses, so we are now switching to the Element-maintained " +"Synapse release." +msgstr "" + +#: ../../../CHANGELOG.md:492 +msgid "**What does this mean to you?**" +msgstr "" + +#: ../../../CHANGELOG.md:494 +msgid "" +"For most home users, it doesn't mean anything. Your installation will " +"continue working as it should and you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:496 +msgid "" +"For people building commercial products on top of Synapse, they may have " +"to either buy a license exception from Element (from what we hear, the " +"fee depends on the number of monthly-active users on your instance) or " +"they may need to release all related code as free-software (which is what" +" we've been doing at [etke.cc](https://etke.cc/) " +"([here](https://gitlab.com/etke.cc)) all along)." +msgstr "" + +#: ../../../CHANGELOG.md:498 +msgid "" +"We're no lawyers and this changelog entry does not aim to give you the " +"best legal advice, so please research on your own!" +msgstr "" + +#: ../../../CHANGELOG.md:500 +msgid "" +"If you'd like to continue using the old Apache-2.0-licensed Synapse (for " +"a while longer anyway), the playbook makes it possible by intruducing a " +"new Ansible variable. You can do it like this:" +msgstr "" + +#: ../../../CHANGELOG.md:512 +msgid "Notes:" +msgstr "" + +#: ../../../CHANGELOG.md:514 +msgid "" +"if you had already upgraded Synapse to `v1.99.0` by running this " +"playbook, you will still be able to downgrade to `v1.98.0`, because both " +"releases use the same database schema version (`SCHEMA_COMPAT_VERSION = " +"83` - see [here for v1.98.0](https://github.com/element-" +"hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and" +" [here for v1.99.0](https://github.com/element-" +"hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). " +"More details on Synapse's database schema are available [here](https" +"://element-" +"hq.github.io/synapse/develop/development/database_schema.html). It " +"appears that there are no new database migrations introduced in " +"`v1.99.0`, so going back to the older release is possible. This is not " +"guaranteed to hold true for future Synapse releases, so if you're seeing " +"this early-enough, consider pinning the version and organization before " +"re-running the playbook and getting upgraded to the latest version" +msgstr "" + +#: ../../../CHANGELOG.md:516 +msgid "" +"running an outdated homeserver exposes you to security issues and " +"incompatibilities. Only consider doing this as a short-term solution." +msgstr "" + +#: ../../../CHANGELOG.md:518 +msgid "2024-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:520 +msgid "`Draupnir` has been relicensed to AFL-3.0" +msgstr "" + +#: ../../../CHANGELOG.md:522 +msgid "" +"As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) " +"Draupnir changed its licence to AFL-3.0 from the CSL licence. This change" +" affects playbook users who could not run Draupnir under the old license " +"restrictions. The new license is considerably less restrictive and is OSI" +" approved. Draupnir version v1.86.0 and later are covered by this license" +" change." +msgstr "" + +#: ../../../CHANGELOG.md:524 +msgid "2024-01-15" +msgstr "" + +#: ../../../CHANGELOG.md:526 +msgid "Goodbye, `matrix-nginx-proxy` 🪦" +msgstr "" + +#: ../../../CHANGELOG.md:528 +msgid "" +"**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component " +"are now gone. This brought about many other internal changes (and " +"security improvements), so setups may need minor adjustments or suffer " +"some (temporary) breakage. People who have been on the Traefik-native " +"setup may upgrade without much issues. Those running their own Traefik " +"instance may need minor changes. People who have been postponing the " +"migration away from `matrix-nginx-proxy` (for more than a year already!) " +"will now finally need to do something about it." +msgstr "" + +#: ../../../CHANGELOG.md:530 +msgid "Backstory on `matrix-nginx-proxy`" +msgstr "" + +#: ../../../CHANGELOG.md:532 +msgid "" +"We gather here today to celebrate the loss of a once-beloved component in" +" our stack - `matrix-nginx-proxy`. It's been our " +"[nginx](https://nginx.org/)-based reverse-proxy of choice since the " +"[first commit](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7" +" years ago." +msgstr "" + +#: ../../../CHANGELOG.md:534 +msgid "" +"For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy " +"in our setup (doing SSL termination, etc.). After [transitioning to " +"Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-" +"nginx-proxy` took a step back. Nevertheless, since it was so ingrained " +"into the playbook, it still remained in use - even if only internally. " +"Despite our warnings of its imminent death, many of you have indubitably " +"continued to use it instead of Traefik. Its suffering continued for too " +"long, because it served many different purposes and massive effort was " +"required to transition them to others." +msgstr "" + +#: ../../../CHANGELOG.md:536 +msgid "To us, `matrix-nginx-proxy` was:" +msgstr "" + +#: ../../../CHANGELOG.md:538 +msgid "an [nginx](https://nginx.org/)-based reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:539 +msgid "" +"an Ansible role organizing the work of " +"[certbot](https://certbot.eff.org/) - retrieving free [Let's " +"Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-" +"proxy` and for the [Coturn TURN server](./docs/configuring-playbook-" +"turn.md)" +msgstr "" + +#: ../../../CHANGELOG.md:540 +msgid "" +"a central component for reverse-proxying to the [long list of " +"services](./docs/configuring-playbook.md) supported by the playbook. As " +"such, it became a dependency that all these services had to inject " +"themselves into during runtime" +msgstr "" + +#: ../../../CHANGELOG.md:541 +msgid "" +"an intermediary through which addons (bridges, bots) communicated with " +"the homeserver. Going through an intermediary (instead of directly " +"talking to the homeserver) is useful when certain components (like " +"[matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or " +"[matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are " +"enabled, because it lets these services \"steal routes\" from the " +"homeserver" +msgstr "" + +#: ../../../CHANGELOG.md:542 +msgid "" +"a webserver for serving the `/.well-known/matrix` static files (generated" +" by the `matrix-base` role until now)" +msgstr "" + +#: ../../../CHANGELOG.md:543 +msgid "" +"a webserver [serving your base domain](./docs/configuring-playbook-base-" +"domain-serving.md) (and also generating the `index.html` page for it)" +msgstr "" + +#: ../../../CHANGELOG.md:544 +msgid "" +"a central component providing global [HTTP Basic " +"Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) " +"password-protection for all `/metrics` endpoints when metrics were " +"exposed publicly for consumption from a remote Prometheus server" +msgstr "" + +#: ../../../CHANGELOG.md:546 +msgid "" +"Talk about a jack of all trades! The [UNIX " +"philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker " +"container philosophy) of \"do one thing and do it well\" had been " +"severely violated for too long." +msgstr "" + +#: ../../../CHANGELOG.md:548 +msgid "" +"On a related note, we also had a large chain of reverse-proxies in the " +"mix. In the worst case, it was something like this: (Traefik -> `matrix-" +"nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-" +"reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." +msgstr "" + +#: ../../../CHANGELOG.md:550 +msgid "" +"Due to complexity and the playbook's flexibility (trying to accommodate a" +" mix of tens of components), many layers of indirection were necessary. " +"We do like reverse-proxies, but.. not quite enough to enjoy going through" +" a chain of ~4 of them before reaching the target service." +msgstr "" + +#: ../../../CHANGELOG.md:552 +msgid "" +"After **a ton of work** in the last weeks (200+ commits, which changed " +"467 files - 8684 insertions and 8913 deletions), **we're finally saying " +"goodbye** to `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:554 +msgid "Going Traefik-native and cutting out all middlemen" +msgstr "" + +#: ../../../CHANGELOG.md:556 +msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." +msgstr "" + +#: ../../../CHANGELOG.md:558 +msgid "" +"In most cases, there's only Traefik and all services being registered " +"directly with it. When [Synapse workers](./docs/configuring-playbook-" +"synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-" +"reverse-proxy-companion` remains as an extra reverse-proxy that requests " +"go through (for load-balancing to the correct Synapse worker), but in all" +" other cases services are exposed directly." +msgstr "" + +#: ../../../CHANGELOG.md:560 +msgid "" +"This reduces \"network\" hops (improving performance) and also decreases " +"the number of components (containers). Each Ansible role in our setup is " +"now independent and doesn't need to interact with other roles during " +"runtime." +msgstr "" + +#: ../../../CHANGELOG.md:562 +msgid "Traefik now has an extra job" +msgstr "" + +#: ../../../CHANGELOG.md:564 +msgid "" +"Previously, **Traefik had a single purpose** - being the main reverse-" +"proxy. It was either front-most (terminating SSL, etc.) or you were " +"[fronting Traefik with your own other reverse-proxy](./docs/configuring-" +"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" +"webserver-with-another-reverse-proxy). In any case - it had this central " +"(yet decentralized) job." +msgstr "" + +#: ../../../CHANGELOG.md:566 +msgid "" +"Now, **Traefik has one more role** - it serves as an intermediary which " +"allows addon services (bridges, bots, etc.) to communicate with the " +"homeserver. As mentioned above, such an intermediary service is not " +"strictly necessary in all kinds of setups, but more complex setups " +"(including [matrix-media-repo](./docs/configuring-playbook-matrix-media-" +"repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-" +"corporal.md)) benefit from it." +msgstr "" + +#: ../../../CHANGELOG.md:568 +msgid "" +"To perform this new role, Traefik now has a new internal " +"[entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called " +"`matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, " +"Synapse and even `matrix-synapse-reverse-proxy-companion`) and " +"homeserver-related core services ([matrix-media-repo](./docs/configuring-" +"playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-" +"playbook-matrix-corporal.md) and potentially others) register their " +"routes (using [container labels](https://docs.docker.com/config/labels-" +"custom-metadata/)) not only on the public entrypoints (`web-secure`, " +"`matrix-federation`), but also on this new internal entrypoint." +msgstr "" + +#: ../../../CHANGELOG.md:570 +msgid "" +"Doing so, services can contact Traefik on this entrypoint's dedicated " +"port (the URL defaults to `http://matrix-traefik:8008`) and reach the " +"homeserver Client-Server API as they expect. Internally, Traefik takes " +"care of the routing to the correct service." +msgstr "" + +#: ../../../CHANGELOG.md:572 +msgid "" +"We've also considered keeping it simple and having services talk to the " +"homeserver over the public internet (e.g. `https://matrix.example.com`) " +"thus reusing all existing Traefik routing labels. In this scenario, " +"performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to" +" TLS and networking overhead. The need for fast internal communication " +"(via the new internal non-TLS-enabled Traefik entrypoint) is definitely " +"there. In our benchmarks, Traefik even proved more efficient than nginx " +"at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out " +"of ~1400 rps when talking to the Synapse homeserver directly)." +msgstr "" + +#: ../../../CHANGELOG.md:574 +msgid "Traefik serving this second purpose has a few downsides:" +msgstr "" + +#: ../../../CHANGELOG.md:576 +msgid "" +"Traefik becomes a runtime dependency for all homeserver-dependant " +"container services" +msgstr "" + +#: ../../../CHANGELOG.md:577 +msgid "" +"all homeserver-dependant services now need to be connected to the " +"`traefik` container network, even if they don't need public internet " +"exposure" +msgstr "" + +#: ../../../CHANGELOG.md:579 +msgid "" +"Despite these downsides (which the playbook manages automatically), we " +"believe it's still a good compromise given the amount of complexity it " +"eliminates and the performance benefits it yields. One alternative we've " +"[considered](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary " +"service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both " +"had much higher complexity (one more component in the mix; duplication of" +" effort to produce nginx-compatible route definitions for it) and " +"slightly worse performance (see above)." +msgstr "" + +#: ../../../CHANGELOG.md:581 +msgid "" +"People running the default Traefik setup do not need to do anything to " +"make Traefik take on this extra job. Your Traefik configuration will be " +"updated automatically." +msgstr "" + +#: ../../../CHANGELOG.md:583 +msgid "" +"**People runnning their own Traefik reverse-proxy need to do [minor " +"adjustments](#people-managing-their-own-traefik-instance-need-to-do-" +"minor-changes)**, as described in the section below." +msgstr "" + +#: ../../../CHANGELOG.md:585 +msgid "" +"You may disable Traefik acting as an intermediary by explicitly setting " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled`" +" to `false`. Services would then be configured to talk to the homeserver " +"directly, giving you a slight performance boost and a \"simpler\" Traefik" +" setup. However, such a configuration is less tested and will cause " +"troubles, especially if you enable more services (like `matrix-media-" +"repo`, etc.) in the future. As such, it's not recommended." +msgstr "" + +#: ../../../CHANGELOG.md:587 +msgid "People managing their own Traefik instance need to do minor changes" +msgstr "" + +#: ../../../CHANGELOG.md:589 +msgid "" +"This section is for people [managing their own Traefik instance on the " +"Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-" +"managed-by-you). Those [using Traefik managed by the playbook](./docs" +"/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) " +"don't need to do any changes." +msgstr "" + +#: ../../../CHANGELOG.md:591 +msgid "" +"Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), " +"you need to adapt your configuration to add the additional `matrix-" +"internal-matrix-client-api` entrypoint and potentially configure the " +"`matrix_playbook_reverse_proxy_container_network` variable. See the " +"[Traefik managed by you](./docs/configuring-playbook-own-webserver.md" +"#traefik-managed-by-you) documentation section for more details." +msgstr "" + +#: ../../../CHANGELOG.md:593 +msgid "" +"People fronting Traefik with another reverse proxy need to do minor " +"changes" +msgstr "" + +#: ../../../CHANGELOG.md:595 +msgid "" +"We've already previously mentioned that you need to do some minor " +"[configuration changes related to `traefik_additional_entrypoints_auto" +"`](#backward-compatibility-configuration-changes-required-for-people-" +"fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:597 +msgid "" +"If you don't do these changes (switching from " +"`traefik_additional_entrypoints_auto` to multiple other variables), your " +"Traefik setup will not automatically receive the new `matrix-internal-" +"matrix-client-api` Traefik entrypoint and Traefik would not be able to " +"perform [its new duty of connecting addons with the homeserver](#traefik-" +"now-has-an-extra-job)." +msgstr "" + +#: ../../../CHANGELOG.md:599 +msgid "Supported reverse proxy types are now fewer" +msgstr "" + +#: ../../../CHANGELOG.md:601 +msgid "" +"This section is for people using a more custom reverse-proxy setup - " +"those having `matrix_playbook_reverse_proxy_type` set to a value " +"different than the default (`playbook-managed-traefik`)." +msgstr "" + +#: ../../../CHANGELOG.md:603 +msgid "" +"Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to" +" 7 different values to accommodate various reverse-proxy setups." +msgstr "" + +#: ../../../CHANGELOG.md:605 +msgid "The complexity of this is too high, so we only support 3 values right now:" +msgstr "" + +#: ../../../CHANGELOG.md:607 +msgid "" +"(the default) `playbook-managed-traefik`, when you're [using Traefik " +"managed by the playbook](./docs/configuring-playbook-own-webserver.md" +"#traefik-managed-by-the-playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:608 +msgid "" +"`other-traefik-container`, when you're [managing your own Traefik " +"instance on the Matrix server](./docs/configuring-playbook-own-" +"webserver.md#traefik-managed-by-you)" +msgstr "" + +#: ../../../CHANGELOG.md:609 +msgid "" +"`none`, when you wish for [no reverse-proxy integration to be done at " +"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" +"on-the-matrix-side-at-all)" +msgstr "" + +#: ../../../CHANGELOG.md:611 +msgid "" +"The `none` value is not recommended and may not work adequately, due to " +"lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-" +"extra-job) in our setup." +msgstr "" + +#: ../../../CHANGELOG.md:613 +msgid "" +"**Previous values that are now gone** (and the playbook would report them" +" as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, " +"`other-on-same-host` and `other-on-another-host`." +msgstr "" + +#: ../../../CHANGELOG.md:615 +msgid "" +"If you were using these values as a way to stay away from Traefik, you " +"now have 2 options:" +msgstr "" + +#: ../../../CHANGELOG.md:617 +msgid "" +"(recommended) [Fronting Traefik with another reverse-proxy](./docs" +"/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-" +"proxy-webserver-with-another-reverse-proxy)" +msgstr "" + +#: ../../../CHANGELOG.md:618 +msgid "" +"(not recommended) [Using no reverse-proxy on the Matrix side at " +"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" +"on-the-matrix-side-at-all) and reverse-proxying to each and every service" +" manually" +msgstr "" + +#: ../../../CHANGELOG.md:620 +msgid "Container networking changes" +msgstr "" + +#: ../../../CHANGELOG.md:622 +msgid "" +"Now that `matrix-nginx-proxy` is not in the mix, it became easier to " +"clear out some other long-overdue technical debt." +msgstr "" + +#: ../../../CHANGELOG.md:624 +msgid "" +"Since the very beginning of this playbook, all playbook services were " +"connected to a single (shared) `matrix` container network. Later on, some" +" additional container networks appeared, but most services (database, " +"etc.) still remained in the `matrix` container network. This meant that " +"any random container in this network could try to talk (or attack) the " +"Postgres database operating in the same `matrix` network." +msgstr "" + +#: ../../../CHANGELOG.md:626 +msgid "" +"Moving components (especially the database) into other container networks" +" was difficult - it required changes to many other components to ensure " +"correct connectivity." +msgstr "" + +#: ../../../CHANGELOG.md:628 +msgid "" +"All the hard work has been done now. We've added much more isolation " +"between services by splitting them up into separate networks (`matrix-" +"homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, " +"etc). Components are only joined to the networks they need and should " +"(for the most part) not be able to access unrelated things." +msgstr "" + +#: ../../../CHANGELOG.md:630 +msgid "" +"Carrying out these container networking changes necessitated modifying " +"many components, so **we're hoping not too many bugs were introduced in " +"the process**." +msgstr "" + +#: ../../../CHANGELOG.md:632 +msgid "" +"We've refrained from creating too many container networks (e.g. one for " +"each component), to avoid exhausting Docker's default network pool and " +"contaminating the container networks list too much." +msgstr "" + +#: ../../../CHANGELOG.md:634 +msgid "Metrics exposure changes" +msgstr "" + +#: ../../../CHANGELOG.md:636 +msgid "" +"This section is for people who are exposing monitoring metrics publicly, " +"to be consumed by an external Prometheus server." +msgstr "" + +#: ../../../CHANGELOG.md:638 +msgid "" +"Previously, `matrix-nginx-proxy` was potentially password-protecting all " +"`/metrics/*` endpoints with the same username and password (specified as " +"plain-text in your `vars.yml` configuration file)." +msgstr "" + +#: ../../../CHANGELOG.md:640 +msgid "" +"From now on, there are new variables for doing roughly the same - " +"`matrix_metrics_exposure_enabled`, " +"`matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & " +"Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for" +" details." +msgstr "" + +#: ../../../CHANGELOG.md:642 +msgid "" +"`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now," +" each role provides its own metrics exposure and protection by " +"registering with Traefik. Nevertheless, all roles are wired (via playbook" +" configuration in `group_vars/matrix_servers`) to obey these new " +"`matrix_metrics_exposure_*` variables. We've eliminated the " +"centralization, but have kept the ease of use. Now, you can also do per-" +"service password-protection (with different credentials), should you need" +" to do that for some reason." +msgstr "" + +#: ../../../CHANGELOG.md:644 +msgid "" +"The playbook will tell you about all variables that you need to migrate " +"during runtime, so rest assured - you shouldn't be able to miss anything!" +msgstr "" + +#: ../../../CHANGELOG.md:646 +msgid "Matrix static files" +msgstr "" + +#: ../../../CHANGELOG.md:648 +msgid "" +"As mentioned above, static files like `/.well-known/matrix/*` or your " +"base domain's `index.html` file (when [serving the base domain via the " +"Matrix server](./docs/configuring-playbook-base-domain-serving.md) was " +"enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` " +"roles and put into a `/matrix/static-files` directory on the server. Then" +" `matrix-nginx-proxy` was serving all these static files." +msgstr "" + +#: ../../../CHANGELOG.md:650 +msgid "" +"All of this has been extracted into a new `matrix-static-files` Ansible " +"role that's part of the playbook. The static files generated by this new " +"role still live at roughly the same place (`/matrix/static-files/public` " +"directory, instead of `/matrix/static-files`)." +msgstr "" + +#: ../../../CHANGELOG.md:652 +msgid "" +"The playbook will migrate and update the `/.well-known/matrix/*` files " +"automatically but not your own files in `nginx-proxy/data/matrix-domain/`" +" you will need to back these up yourself otherwise they will be lost. It " +"will also warn you about usage of old variable names, so you can adapt to" +" the new names." +msgstr "" + +#: ../../../CHANGELOG.md:654 +msgid "A note on performance" +msgstr "" + +#: ../../../CHANGELOG.md:656 +msgid "" +"Some of you have been voicing their concerns (for a long time) about " +"Traefik being too slow and nginx being better." +msgstr "" + +#: ../../../CHANGELOG.md:658 +msgid "" +"Some online benchmarks support this by demonstrating slightly higher SSL-" +"termination performance in favor of nginx. The upcoming Traefik v3 " +"release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-" +"traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL " +"performance by some 20%, but that still ends up being somewhat slower " +"than nginx." +msgstr "" + +#: ../../../CHANGELOG.md:660 +msgid "" +"We believe that using Traefik provides way too many benefits to worry " +"about this minor performance impairment." +msgstr "" + +#: ../../../CHANGELOG.md:662 +msgid "" +"The heaviest part of running a Matrix homeserver is all the slow and " +"potentially inefficient things the homeserver (e.g. Synapse) is doing. " +"These things affect performance much more than whatever reverse-proxy is " +"in front. Your server will die the same way by joining the famously large" +" **Matrix HQ** room, no matter which reverse-proxy you put in front." +msgstr "" + +#: ../../../CHANGELOG.md:664 +msgid "" +"Even our previously mentioned benchmarks (yielding ~1300 rps) are " +"synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-" +"use does much more than this." +msgstr "" + +#: ../../../CHANGELOG.md:666 +msgid "" +"If this is still not convincing enough for you and you want the best " +"possible performance, consider [Fronting Traefik with another reverse-" +"proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-" +"integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus " +"having the slowest part - SSL termination - happen elsewhere) or [Using " +"no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-" +"own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The " +"playbook will not get in your way of doing that, but these options may " +"make your life much harder. Performance comes at a cost, after all." +msgstr "" + +#: ../../../CHANGELOG.md:668 +msgid "Migration procedure" +msgstr "" + +#: ../../../CHANGELOG.md:670 +msgid "" +"The updated playbook will automatically perform some migration tasks for " +"you:" +msgstr "" + +#: ../../../CHANGELOG.md:672 +msgid "" +"It will stop and remove the `matrix-nginx-proxy` systemd service and " +"container for you. This behavior cannot be disabled. It's essential that " +"this service gets stopped, because it remaining running (and having " +"container labels) may confuse Traefik as to where to route HTTP requests." +msgstr "" + +#: ../../../CHANGELOG.md:674 +msgid "" +"It will delete the `/matrix/nginx-proxy` directory and all files within " +"it. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: " +"false` to your `vars.yml` configuration file. Doing so will leave its " +"data around." +msgstr "" + +#: ../../../CHANGELOG.md:676 +msgid "" +"It will delete the `/matrix/ssl` directory and all files within it. You " +"can disable this behavior by adding " +"`matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to " +"your `vars.yml` configuration file. If you have some important " +"certificates there for some reason, take them out or temporarily disable " +"removal of these files until you do." +msgstr "" + +#: ../../../CHANGELOG.md:678 +msgid "" +"It will tell you about all variables (`matrix_nginx_proxy_*` and many " +"others - even from other roles) that have changed during this large " +"nginx-elimination upgrade. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:680 +msgid "" +"It will tell you about any leftover `matrix_nginx_proxy_*` variables in " +"your `vars.yml` file. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled:" +" false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:682 +msgid "" +"It will tell you about any leftover `matrix_ssl_*` variables in your " +"`vars.yml` file. You can disable this behavior by adding " +"`matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: " +"false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:684 +msgid "" +"We don't recommend changing these variables and suppressing warnings, " +"unless you know what you're doing." +msgstr "" + +#: ../../../CHANGELOG.md:686 +msgid "" +"**Most people should just upgrade as per-normal**, bearing in mind that a" +" lot has changed and some issues may arise. The playbook would guide you " +"through renamed variables automatically." +msgstr "" + +#: ../../../CHANGELOG.md:688 +msgid "Conclusion" +msgstr "" + +#: ../../../CHANGELOG.md:690 +msgid "" +"Thousands of lines of code were changed across hundreds of files. All " +"addons (bridges, bots) were rewired in terms of container networking and " +"in terms of how they reach the homeserver." +msgstr "" + +#: ../../../CHANGELOG.md:692 +msgid "" +"I don't actively use all the ~100 components offered by the playbook (no " +"one does), nor do I operate servers exercising all edge-cases. As such, " +"issues may arise. Please have patience and report (or try to fix) these " +"issues!" +msgstr "" + +#: ../../../CHANGELOG.md:695 +msgid "2024-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:697 +msgid "" +"(Backward Compatibility) Configuration changes required for people " +"fronting the integrated reverse-proxy webserver with another reverse-" +"proxy" +msgstr "" + +#: ../../../CHANGELOG.md:699 +msgid "" +"If you're on the default setup (using the Traefik reverse-proxy as " +"installed by the playbook), you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:701 +msgid "" +"People who are [Fronting the integrated Traefik reverse-proxy webserver " +"with another reverse-proxy](./docs/configuring-playbook-own-webserver.md" +"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy), as per our previous instructions are redefining " +"`traefik_additional_entrypoints_auto` in their `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:703 +msgid "" +"Such a full variable redefinion is intrustive, because it prevents the " +"playbook from injecting additional entrypoints into the Traefik " +"webserver. In the future, the playbook may have a need to do so." +msgstr "" + +#: ../../../CHANGELOG.md:705 +msgid "" +"For this reason, we no longer recommend completely redefining " +"`traefik_additional_entrypoints_auto`. The playbook now defines [various " +"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` " +"variables in the `defaults/main.yml` file](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-" +"base/defaults/main.yml) of the `matrix-base` role which can be used as a " +"safer alternative to `traefik_additional_entrypoints_auto`." +msgstr "" + +#: ../../../CHANGELOG.md:707 +msgid "Adapt your configuration as seen below:" +msgstr "" + +#: ../../../CHANGELOG.md:740 +msgid "" +"Also, feel free to read the [Fronting the integrated Traefik reverse-" +"proxy webserver with another reverse-proxy](./docs/configuring-playbook-" +"own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-" +"another-reverse-proxy) documentation section again for additional " +"details." +msgstr "" + +#: ../../../CHANGELOG.md:743 +msgid "2024-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:745 +msgid "" +"matrix-reminder-bot update with more secure (backward-incompatible) " +"default settings" +msgstr "" + +#: ../../../CHANGELOG.md:747 +msgid "" +"**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453" +"/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs" +"/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By " +"default, like other bridges/bots managed by the playbook, it will only " +"provide its services to users of your own server (not to anyone, even " +"across the Matrix Federation). If that's fine, there's nothing you need " +"to do." +msgstr "" + +#: ../../../CHANGELOG.md:749 +msgid "" +"Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-" +"matrix-reminder-bot.md) has been picked up by [Kim " +"Brose](https://github.com/HarHarLinks) and " +"[@svierne](https://github.com/svierne)." +msgstr "" + +#: ../../../CHANGELOG.md:751 +msgid "" +"Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-" +"reminder-bot/releases/tag/v0.3.0) release is out. The new version is now " +"available for the ARM64 architecture, so playbook users on this " +"architecture will no longer need to wait for [self-building](./docs/self-" +"building.md) to happen." +msgstr "" + +#: ../../../CHANGELOG.md:753 +msgid "" +"The new version also comes with new `allowlist` and `blocklist` settings," +" which make it possible to restrict who can use the bot. Previously " +"anyone, even across the Matrix Federation could talk to it and schedule " +"reminders." +msgstr "" + +#: ../../../CHANGELOG.md:755 +msgid "" +"The playbook defaults all bridges and bots (where possible) to only be " +"exposed to users of the current homeserver, not users across federation. " +"Thanks to the new version of this bot making such a restriction possible," +" we're now making use of it. The playbook (via its " +"`group_vars/matrix_servers` file) automatically enables the `allowlist` " +"(`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures" +" it in such a way " +"(`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to " +"restrict the bot to your homeserver's users." +msgstr "" + +#: ../../../CHANGELOG.md:757 +msgid "" +"If you need **to undo or tweak these security improvements**, you can " +"change your `vars.yml` file to:" +msgstr "" + +#: ../../../CHANGELOG.md:759 +msgid "" +"disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled:" +" false`), making the bot allow usage by anyone, anywhere" +msgstr "" + +#: ../../../CHANGELOG.md:761 +msgid "" +"inject additional allowed servers or users by adding **additional** (on " +"top of the default allowlist in " +"`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes " +"in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list " +"variable (see the [syntax reference](https://github.com/anoadragon453" +"/matrix-reminder-" +"bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" +msgstr "" + +#: ../../../CHANGELOG.md:763 +msgid "" +"override the default allowlist (in the `group_vars/matrix_servers` file) " +"by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" +msgstr "" + +#: ../../../CHANGELOG.md:766 +msgid "2024-01-05" +msgstr "" + +#: ../../../CHANGELOG.md:768 +msgid "matrix-mailer has been replaced by the exim-relay external role" +msgstr "" + +#: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410 +msgid "" +"We're continuing our effort to make [the playbook use external roles for " +"some things](#the-playbook-now-uses-external-roles-for-some-things), so " +"as to avoid doing everything ourselves and to facilitate code re-use." +msgstr "" + +#: ../../../CHANGELOG.md:772 +msgid "" +"The `matrix-mailer` role has been moved to its own repository ([ansible-" +"role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-" +"role-exim-relay)) that this playbook now includes." +msgstr "" + +#: ../../../CHANGELOG.md:774 +msgid "To migrate:" +msgstr "" + +#: ../../../CHANGELOG.md:776 +msgid "pull the playbook changes, as usual" +msgstr "" + +#: ../../../CHANGELOG.md:777 +msgid "update your roles (run `just roles` or `make roles`)" +msgstr "" + +#: ../../../CHANGELOG.md:778 +msgid "" +"update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to " +"`exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> " +"`exim_relay_sender_address`). If you find none, it means you're using the" +" default configuration and your migraiton job is even simpler." +msgstr "" + +#: ../../../CHANGELOG.md:779 +msgid "re-run the playbook (`install-all` or `setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:781 +msgid "" +"The playbook will take care of stopping the old `matrix-mailer` systemd " +"service, relocating its directory and restarting it under the new name " +"(`matrix-exim-relay.service`)." +msgstr "" + +#: ../../../CHANGELOG.md:784 +msgid "2024-01-02" +msgstr "" + +#: ../../../CHANGELOG.md:786 +msgid "mautrix-signal now powered by the new Go-based bridge" +msgstr "" + +#: ../../../CHANGELOG.md:788 +msgid "" +"The old Python-based [mautrix-signal](https://github.com/mautrix/signal) " +"bridge is no longer maintained upstream. It's also known to have issues " +"linking new devices." +msgstr "" + +#: ../../../CHANGELOG.md:790 +msgid "" +"It seems like the path forward is to switch to the new mautrix-signal " +"bridge written in Golang, which we did thanks to [PR " +"#3031](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." +msgstr "" + +#: ../../../CHANGELOG.md:792 +msgid "" +"The playbook should **automatically migrate your mautrix-signal " +"installation to the new bridge code**. You will **need to relink all your" +" devices** to continue your bridged conversations." +msgstr "" + +#: ../../../CHANGELOG.md:795 +msgid "2023-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:797 +msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:799 +msgid "" +"**TDLR**: if your Matrix server is federating (which it mostly likely is," +" unless you've [disabled federation](docs/configuring-playbook-" +"federation.md#disabling-federation)), your public rooms will not only be " +"joinable across federation (as they've always been), but from now on will" +" be discoverable (made available as a list across federation). We're " +"changing this by flipping the value for Synapse's " +"`allow_public_rooms_over_federation` setting to `true`, going against the" +" upstream default. Servers that disable federation are not affected. " +"Servers that have public rooms which are not published to the room " +"directory are also not affected." +msgstr "" + +#: ../../../CHANGELOG.md:801 +msgid "" +"We generally try to stick to the default configuration for Synapse (and " +"all other components), unless these defaults seem wrong or harmful. One " +"such previous case from a few months ago was us [Enabling " +"`forget_rooms_on_leave` by default for Synapse](#enabling-" +"forget_rooms_on_leave-by-default-for-synapse) - the default value was " +"making Synapse more wasteful of resources by default." +msgstr "" + +#: ../../../CHANGELOG.md:803 +msgid "" +"Today, we're going against upstream defaults again and flipping the " +"`allow_public_rooms_over_federation` configuration option to `true`. This" +" way, public rooms on your server will be made discoverable by others via" +" federation, using the [`GET /_matrix/federation/v1/publicRooms` of the " +"Server-Server API](https://spec.matrix.org/v1.8/server-server-" +"api/#get_matrixfederationv1publicrooms)." +msgstr "" + +#: ../../../CHANGELOG.md:805 +msgid "" +"The upstream Synapse default is `false` (disabled), so that public rooms " +"are not exposed for other servers to discover (learn about their " +"existence). Nevertheless, even if these rooms are not exposed (listed) " +"for discovery, they are **still joinable** by anyone who knows their " +"address or is invited to the room by an existing member." +msgstr "" + +#: ../../../CHANGELOG.md:807 +msgid "" +"**We go against the upstream default** in an effort to make Matrix " +"federation more useful - a public room should be globally public - not " +"only joinable, but also discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:809 +msgid "The **historical reasoning** behind this change is as follows:" +msgstr "" + +#: ../../../CHANGELOG.md:811 +msgid "" +"`allow_public_rooms_over_federation` seems to have been enabled by " +"default for Synapse until v1.7.0 (~2019), just like we believe it should " +"be for a globally-federating network - rooms should be joinable and " +"discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:813 +msgid "" +"In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got " +"disabled](https://github.com/element-" +"hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891)" +" by default in a [security-by-" +"obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) " +"workaround for misconfigured servers. See the [Avoiding unwelcome " +"visitors on private Matrix servers](https://matrix.org/blog/2019/11/09" +"/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` " +"blog article. We believe that people wishing for a truly private server, " +"should [disable federation](docs/configuring-playbook-federation.md" +"#disabling-federation), instead of having a fully-federating server and " +"trying to hide its public rooms. We also provide other workarounds below." +" We (and the Synapse team, obviously) believe that Matrix should federate" +" by default, so federating the public room list seems to make sense." +msgstr "" + +#: ../../../CHANGELOG.md:815 +#, python-format +msgid "" +"[etke.cc](https://etke.cc/) has been developing the free-software [Matrix" +" Rooms Search](https://github.com/etkecc/mrs) project for a while now. " +"One public (demo) instance of it is hosted at " +"[matrixrooms.info](https://matrixrooms.info/). This search engine tries " +"to go through the Matrix federation and discover & index public rooms to " +"allow people to find them. We believe it's vital for Matrix (and any chat" +" or social network for that matter) to be more discoverable, so that " +"people can find communities and others to talk to. Today (on 23rd of " +"October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of " +"these, only `1567` servers (7%) are making their public rooms " +"discoverable. Who knows what wonderful communities and rooms are " +"available on these 93% other Matrix servers that are supposedly " +"federating, but are still gate-keeping their public room list. " +"Indubitably, many of these servers are hosted via matrix-docker-ansible-" +"deploy, so we feel partially responsible for making Matrix federation " +"less useful." +msgstr "" + +#: ../../../CHANGELOG.md:817 +msgid "Here are **actions you may wish to take** as a result of this change:" +msgstr "" + +#: ../../../CHANGELOG.md:819 +msgid "" +"(recommended) embrace the new default. If your Matrix server is " +"federating, your public rooms have always been joinable across federation" +" anyway. Exposing the list of public rooms does no harm and more-so does " +"good by contributing to the usefulness of the Matrix network by " +"facilitating room discovery." +msgstr "" + +#: ../../../CHANGELOG.md:821 +msgid "" +"(switch to a better way of doings things on your semi-private server) The" +" problem that the Synapse team appears to have solved by flipping the " +"`allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to " +"for \"mostly private\" servers, which federate and have a bunch of rooms " +"made public (and published in their room directory) in an effort to allow" +" people on the same homeserver to easily find and join them (self-" +"onboarding). With the introduction of Matrix Spaces, you can reorganize " +"your flow around spaces - you can auto-join your users to a Matrix Space " +"(via Synapse's `auto_join_rooms` setting - controlled by our " +"`matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to " +"the space and make them joinable by people belonging to the space. That " +"is to say, do not make rooms public and do not publish them to the room " +"directory unless they are really public. Instead, use other mechanisms " +"for semi-public rooms or private rooms. One alternative is to stick to " +"what you're doing (public rooms published to your rooms directory) but " +"having a `m.federate: true` flag set during creation (clients like " +"Element Web have a nice UI checkbox for this) to explicitly disable " +"federation for them." +msgstr "" + +#: ../../../CHANGELOG.md:823 +msgid "" +"(keeping the old behavior) if you wish to keep doing what you're doing " +"(keeping your Matrix server federating, but hiding its public rooms " +"list), add `matrix_synapse_allow_public_rooms_over_federation: false` to " +"your `vars.yml` configuration. This restores the old behavior. You may " +"also consider [disabling federation](docs/configuring-playbook-" +"federation.md#disabling-federation) completely instead of relying on " +"security-by-obscurity measures." +msgstr "" + +#: ../../../CHANGELOG.md:826 +msgid "2023-10-18" +msgstr "" + +#: ../../../CHANGELOG.md:828 +msgid "Postgres parameters are automatically tuned now" +msgstr "" + +#: ../../../CHANGELOG.md:830 +msgid "" +"The playbook has provided some hints about [Tuning PostgreSQL](docs" +"/maintenance-postgres.md#tuning-postgresql) for quite a while now." +msgstr "" + +#: ../../../CHANGELOG.md:832 +msgid "" +"From now on, the [Postgres Ansible role](https://github.com/mother-of-" +"all-self-hosting/ansible-role-postgres) automatically tunes your Postgres" +" configuration with the same [calculation " +"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" +" that powers https://pgtune.leopard.in.ua/." +msgstr "" + +#: ../../../CHANGELOG.md:834 +msgid "" +"Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) " +"documentation page has details about how you can turn auto-tuning off or " +"adjust the automatically-determined Postgres configuration parameters " +"manually." +msgstr "" + +#: ../../../CHANGELOG.md:836 +msgid "" +"People who [enable load-balancing with Synapse workers](docs/configuring-" +"playbook-synapse.md#load-balancing-with-workers) no longer need to " +"increase the maximum number of Postgres connections manually (previously " +"done via `postgres_process_extra_arguments`). There's a new variable " +"(`postgres_max_connections`) for controlling this number and the playbook" +" automatically raises its value from `200` to `500` for setups which " +"enable workers." +msgstr "" + +#: ../../../CHANGELOG.md:839 +msgid "2023-08-31" +msgstr "" + +#: ../../../CHANGELOG.md:841 +msgid "SchildiChat Web support" +msgstr "" + +#: ../../../CHANGELOG.md:843 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat" +" Web](https://github.com/SchildiChat/schildichat-desktop) client." +msgstr "" + +#: ../../../CHANGELOG.md:845 +msgid "" +"See our [Configuring SchildiChat Web](docs/configuring-playbook-client-" +"schildichat-web.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:848 +msgid "2023-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:850 +msgid "mautrix-wsproxy support" +msgstr "" + +#: ../../../CHANGELOG.md:852 +msgid "" +"Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who " +"finished what was started by [James Reilly](https://github.com/hanthor) " +"and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now " +"supports bridging to Android SMS and Apple iMessage via the [mautrix-" +"wsproxy](https://github.com/mautrix/wsproxy) service (in combination with" +" a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running" +" on your Mac or Android phone)." +msgstr "" + +#: ../../../CHANGELOG.md:854 +msgid "" +"See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple " +"iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) " +"documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:857 +msgid "2023-07-24" +msgstr "" + +#: ../../../CHANGELOG.md:859 +msgid "matrix-registration-bot usage changed" +msgstr "" + +#: ../../../CHANGELOG.md:861 +msgid "" +"[matrix-registration-bot](docs/configuring-playbook-bot-matrix-" +"registration-bot.md) got some updates and now supports password-only-" +"based login. Therefore the bot now doesn't need any manual configuration " +"except setting a password in your `vars.yml`. The bot will be registered " +"as admin and access tokens will be obtained automatically by the bot." +msgstr "" + +#: ../../../CHANGELOG.md:863 +msgid "" +"**For existing users** You need to set " +"`matrix_bot_matrix_registration_bot_bot_password` if you previously only " +"used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also " +"remove the following deprecated settings" +msgstr "" + +#: ../../../CHANGELOG.md:865 +msgid "`matrix_bot_matrix_registration_bot_bot_access_token`" +msgstr "" + +#: ../../../CHANGELOG.md:866 +msgid "`matrix_bot_matrix_registration_bot_api_token`" +msgstr "" + +#: ../../../CHANGELOG.md:869 +msgid "2023-07-21" +msgstr "" + +#: ../../../CHANGELOG.md:871 +msgid "mautrix-gmessages support" +msgstr "" + +#: ../../../CHANGELOG.md:873 +msgid "" +"Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, " +"the playbook now supports bridging to [Google " +"Messages](https://messages.google.com/) via the [mautrix-" +"gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting" +" up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-" +"mautrix-gmessages.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:876 +msgid "2023-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:878 +msgid "matrix-media-repo support" +msgstr "" + +#: ../../../CHANGELOG.md:880 +msgid "" +"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " +"[FUTO](https://www.futo.org/), the creators of the [Circles " +"app](https://circu.li/), the playbook can now set up [matrix-media-" +"repo](https://github.com/turt2live/matrix-media-repo) - an alternative " +"way to store homeserver media files, powered by a homeserver-independent " +"implementation which supports S3 storage, IPFS, deduplication and other " +"advanced features." +msgstr "" + +#: ../../../CHANGELOG.md:882 +msgid "" +"To learn more see our [Storing Matrix media files using matrix-media-" +"repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:885 +msgid "2023-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:887 +msgid "Enabling `forget_rooms_on_leave` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:889 +msgid "" +"With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/2698), we've also **changed the default " +"value** of the `forget_rooms_on_leave` setting of Synapse to a value of " +"`true`. This way, **when you leave a room, Synapse will now forget it " +"automatically**." +msgstr "" + +#: ../../../CHANGELOG.md:891 +msgid "" +"The upstream Synapse default is `false` (disabled), so that you must " +"forget rooms manually after leaving." +msgstr "" + +#: ../../../CHANGELOG.md:893 +msgid "" +"**We go against the upstream default** ([somewhat " +"controversially](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/2700)) in an effort to make Synapse leaner and potentially do" +" what we believe most users would expect their homeserver to be doing." +msgstr "" + +#: ../../../CHANGELOG.md:895 +msgid "" +"If you'd like to go back to the old behavior, add the following to your " +"configuration: `matrix_synapse_forget_rooms_on_leave: false`" +msgstr "" + +#: ../../../CHANGELOG.md:898 +msgid "2023-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:900 +msgid "The matrix-jitsi role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:902 +msgid "" +"**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-" +"jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) " +"repository, part of the [MASH playbook](https://github.com/mother-of-all-" +"self-hosting/mash-playbook). Some variables have been renamed. All " +"functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:904 +msgid "" +"The `matrix-jitsi` role has been relocated in its own repository, part of" +" the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) project - an Ansible playbook for self-hosting [a growing list " +"of FOSS software](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack " +"on the Matrix server itself did not stand right with you or you always " +"wanted to host most stuff, you can now use this new playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:906 +msgid "" +"As part of the extraction process of this role out of the Matrix " +"playbook, a few other things improved:" +msgstr "" + +#: ../../../CHANGELOG.md:908 +msgid "**native Traefik support** has been added" +msgstr "" + +#: ../../../CHANGELOG.md:909 +msgid "" +"**support for hosting under a subpath** has been added, although it " +"suffers from a few minor issues listed [here](https://github.com/mother-" +"of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" +msgstr "" + +#: ../../../CHANGELOG.md:911 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Jitsi or not." +msgstr "" + +#: ../../../CHANGELOG.md:913 +msgid "" +"If you're making use of Jitsi via this playbook, you will need to update " +"variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:915 +msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:916 +msgid "`matrix_jitsi_` -> `jitsi_`" +msgstr "" + +#: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944 +msgid "" +"some other internal variables have changed, but the playbook will tell " +"you about them" +msgstr "" + +#: ../../../CHANGELOG.md:919 +msgid "2023-03-22" +msgstr "" + +#: ../../../CHANGELOG.md:921 +msgid "ntfy Web App is disabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:923 +msgid "" +"ntfy provides a web app, which is now disabled by default, because it may" +" be unknown to and unused by most users of this playbook. You can enable " +"it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs" +"/configuring-playbook-ntfy.md))." +msgstr "" + +#: ../../../CHANGELOG.md:925 +msgid "" +"This change was already applied a while before this entry, but as some " +"users were reporting the missing web app, this entry was added (see " +"[#2529](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/2529))." +msgstr "" + +#: ../../../CHANGELOG.md:928 +msgid "2023-03-21" +msgstr "" + +#: ../../../CHANGELOG.md:930 +msgid "The matrix-prometheus role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:932 +msgid "" +"**TLDR**: the `matrix-prometheus` role is now included from the [ansible-" +"role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-" +"role-prometheus) repository, part of the [MASH " +"playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). " +"Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:934 +msgid "" +"The `matrix-prometheus` role has been relocated in its own repository, " +"part of the [MASH playbook](https://github.com/mother-of-all-self-hosting" +"/mash-playbook) project - an Ansible playbook for self-hosting [a growing" +" list of FOSS software](https://github.com/mother-of-all-self-hosting" +"/mash-playbook/blob/main/docs/supported-services.md). If hosting a " +"Prometheus stack on the Matrix server itself did not stand right with you" +" or you always wanted to host most stuff, you can now use this new " +"playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:936 +msgid "" +"Extracting the Prometheus role out of this Matrix playbook required huge " +"internal refactoring to the way the Prometheus configuration (scraping " +"jobs) is generated. If you notice any breakage after upgrading, let us " +"know." +msgstr "" + +#: ../../../CHANGELOG.md:938 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Prometheus or not." +msgstr "" + +#: ../../../CHANGELOG.md:940 +msgid "" +"If you're making use of Prometheus via this playbook, you will need to " +"update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:942 +msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:943 +msgid "`matrix_prometheus_` -> `prometheus_`" +msgstr "" + +#: ../../../CHANGELOG.md:947 +msgid "2023-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:949 +msgid "synapse-auto-compressor support" +msgstr "" + +#: ../../../CHANGELOG.md:951 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-" +"compress-state](https://github.com/matrix-org/rust-synapse-compress-" +"state)'s `synapse_auto_compressor` tool to run periodically." +msgstr "" + +#: ../../../CHANGELOG.md:953 +msgid "" +"If enabled, `synapse_auto_compressor` runs on a schedule and compresses " +"your Synapse database's `state_groups` table. It was possible to run " +"`rust-synapse-compress-state` manually via the playbook even before - see" +" [Compressing state with rust-synapse-compress-state](docs/maintenance-" +"synapse.md#compressing-state-with-rust-synapse-compress-state). However, " +"using `synapse_auto_compressor` is better, because:" +msgstr "" + +#: ../../../CHANGELOG.md:955 +msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" +msgstr "" + +#: ../../../CHANGELOG.md:956 +msgid "" +"it's a set-it-and-forget-it tool that you can enable and never have to " +"deal with manual compression anymore" +msgstr "" + +#: ../../../CHANGELOG.md:958 +msgid "" +"This tool needs to be enabled manually, for now. In the future, we're " +"considering enabling it by default for all Synapse installations." +msgstr "" + +#: ../../../CHANGELOG.md:960 +msgid "" +"See our [Setting up synapse-auto-compressor](docs/configuring-playbook-" +"synapse-auto-compressor.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:963 +msgid "2023-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:965 +msgid "Sliding Sync proxy (Element X) support" +msgstr "" + +#: ../../../CHANGELOG.md:967 +msgid "" +"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting " +"it started](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up" +" and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the" +" playbook can now install and configure the [sliding-sync " +"proxy](https://github.com/matrix-org/sliding-sync)." +msgstr "" + +#: ../../../CHANGELOG.md:969 +msgid "" +"The upcoming Element X clients ([Element X iOS](https://github.com" +"/vector-im/element-x-ios) and [Element X Android](https://github.com" +"/vector-im/element-x-android)) require the `sliding-sync` proxy to do " +"their job. **These clients are still in beta** (especially Element X " +"Android, which requires manual compilation to get it working with a " +"non-`matrix.org` homeseserver). Playbook users can now easily give these " +"clients a try and help test them thanks to us having `sliding-sync` " +"support." +msgstr "" + +#: ../../../CHANGELOG.md:971 +msgid "" +"To get started, see our [Setting up the Sliding Sync proxy](docs" +"/configuring-playbook-sliding-sync-proxy.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:974 +msgid "2023-03-02" +msgstr "" + +#: ../../../CHANGELOG.md:976 +msgid "The matrix-etherpad role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:978 +msgid "" +"**TLDR**: the `matrix-etherpad` role is now included from [another " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"etherpad). Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:980 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're using Etherpad or not." +msgstr "" + +#: ../../../CHANGELOG.md:982 +msgid "" +"If you're making use of Etherpad via this playbook, you will need to " +"update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:984 +msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`" +msgstr "" + +#: ../../../CHANGELOG.md:986 +msgid "Replace `matrix_etherpad_mode: dimension` with:" +msgstr "" + +#: ../../../CHANGELOG.md:987 +msgid "for `matrix-nginx-proxy` users:" +msgstr "" + +#: ../../../CHANGELOG.md:988 +msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`" +msgstr "" + +#: ../../../CHANGELOG.md:989 +msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:990 +msgid "for Traefik users:" +msgstr "" + +#: ../../../CHANGELOG.md:991 +msgid "" +"define your own `etherpad_hostname` and `etherpad_path_prefix` as you see" +" fit" +msgstr "" + +#: ../../../CHANGELOG.md:993 +msgid "Rename all other variables:" +msgstr "" + +#: ../../../CHANGELOG.md:994 +msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:995 +msgid "`matrix_etherpad_` -> `etherpad_`" +msgstr "" + +#: ../../../CHANGELOG.md:997 +msgid "Along with this relocation, the new role also:" +msgstr "" + +#: ../../../CHANGELOG.md:999 +msgid "" +"supports [self-building](docs/self-building.md), so it should work on " +"`arm32` and `arm64` architectures" +msgstr "" + +#: ../../../CHANGELOG.md:1000 +msgid "" +"has native Traefik reverse-proxy support (Etherpad requests no longer go " +"through `matrix-nginx-proxy` when using Traefik)" +msgstr "" + +#: ../../../CHANGELOG.md:1003 +msgid "2023-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:1005 +msgid "Traefik is the default reverse-proxy now" +msgstr "" + +#: ../../../CHANGELOG.md:1007 +msgid "" +"**TLDR**: new installations will now default to Traefik as their reverse-" +"proxy. Existing users need to explicitly choose their reverse-proxy type." +" [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is" +" strongly encouraged. `matrix-nginx-proxy` may break over time and will " +"ultimately be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1009 +msgid "" +"As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy " +"configuration changes and initial Traefik support](#backward-" +"compatibility-reverse-proxy-configuration-changes-and-initial-traefik-" +"support), the playbook is moving to Traefik as its default SSL-" +"terminating reverse-proxy." +msgstr "" + +#: ../../../CHANGELOG.md:1011 +msgid "" +"Until now, we've been doing the migration gradually and keeping full " +"backward compatibility. New installations were defaulting to `matrix-" +"nginx-proxy` (just like before), while existing installations were " +"allowed to remain on `matrix-nginx-proxy` as well. This makes things very" +" difficult for us, because we need to maintain and think about lots of " +"different setups:" +msgstr "" + +#: ../../../CHANGELOG.md:1013 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1014 +msgid "Traefik managed by the user in another way" +msgstr "" + +#: ../../../CHANGELOG.md:1015 +msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1016 +msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1017 +msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1018 +msgid "" +"`nginx` webserver operated by the user, running without a container on " +"the same server" +msgstr "" + +#: ../../../CHANGELOG.md:1020 +msgid "" +"Each change we do and each new feature that comes in needs to support all" +" these different ways of reverse-proxying. Because `matrix-nginx-proxy` " +"was the default and pretty much everyone was (and still is) using it, " +"means that new PRs also come with `matrix-nginx-proxy` as their main " +"focus and Traefik as an afterthought, which means we need to spend hours " +"fixing up Traefik support." +msgstr "" + +#: ../../../CHANGELOG.md:1022 +msgid "" +"We can't spend all this time maintaining so many different configurations" +" anymore. Traefik support has been an option for 2 weeks and lots of " +"people have already migrated their server and have tested things out. " +"Traefik is what we use and preferentially test for." +msgstr "" + +#: ../../../CHANGELOG.md:1024 +msgid "" +"It's time for the **next step in our migration process** to Traefik and " +"elimination of `matrix-nginx-proxy`:" +msgstr "" + +#: ../../../CHANGELOG.md:1026 +msgid "Traefik is now the default reverse-proxy for new installations" +msgstr "" + +#: ../../../CHANGELOG.md:1027 +msgid "" +"All existing users need to explicitly choose their reverse-proxy type by " +"defining the `matrix_playbook_reverse_proxy_type` variable in their " +"`vars.yml` configuration file. We strongly encourage existing users to " +"[switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the" +" nginx setup is bound to become more and more broken over time until it's" +" ultimately removed" +msgstr "" + +#: ../../../CHANGELOG.md:1029 +msgid "How do I switch my existing setup to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1031 +msgid "" +"**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy " +"provided by the playbook), switching to Traefik can happen with a simple " +"configuration change. Follow this section from 2 weeks ago: [How do I " +"explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-" +"traefik-right-now)." +msgstr "" + +#: ../../../CHANGELOG.md:1033 +msgid "If you experience trouble:" +msgstr "" + +#: ../../../CHANGELOG.md:1035 +msgid "" +"Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-" +"matrix-nginx-proxy) to bring your server back online using the old " +"reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:1036 +msgid "Ask for help in our [support channels](README.md#support)" +msgstr "" + +#: ../../../CHANGELOG.md:1037 +msgid "Try switching to Traefik again later" +msgstr "" + +#: ../../../CHANGELOG.md:1039 +msgid "" +"**For users with a more special reverse-proxying setup** (another nginx " +"server, Apache, Caddy, etc.), the migration may not be so smooth. Follow " +"the [Using your own webserver](docs/configuring-playbook-own-" +"webserver.md) guide. Ideally, your custom reverse-proxy will be " +"configured in such a way that it **fronts the Traefik reverse-proxy** " +"provided by the playbook. Other means of reverse-proxying are more " +"fragile and may be deprecated in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1041 +msgid "I already use my own Traefik server. How do I plug that in?" +msgstr "" + +#: ../../../CHANGELOG.md:1043 +msgid "" +"See the [Traefik managed by the playbook](docs/configuring-playbook-own-" +"webserver.md#traefik-managed-by-the-playbook) section." +msgstr "" + +#: ../../../CHANGELOG.md:1045 +msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1047 +msgid "" +"This playbook manages many different services. All these services were " +"initially integrated with `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:1049 +msgid "" +"While we migrate all these components to have native Traefik support, " +"some still go through nginx internally (Traefik -> local `matrix-nginx-" +"proxy` -> component). As time goes on, internal reliance on `matrix-" +"nginx-proxy` will gradually decrease until it's completely removed." +msgstr "" + +#: ../../../CHANGELOG.md:1051 +msgid "How do I remain on matrix-nginx-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1053 +msgid "" +"Most new work and testing targets Traefik, so remaining on nginx is " +"**not** \"the good old stable\" option, but rather the \"still available," +" but largely untested and likely to be broken very soon\" option." +msgstr "" + +#: ../../../CHANGELOG.md:1055 +msgid "" +"To proceed regardless of this warning, add " +"`matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your " +"configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1057 +msgid "" +"At some point in the **near** future (days, or even weeks at most), we " +"hope to completely get rid of `matrix-nginx-proxy` (or break it enough to" +" make it unusable), so you **will soon be forced to migrate** anyway. " +"Plan your migration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:1059 +msgid "How do I keep using my own other reverse-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1061 +msgid "" +"We recommend that you follow the guide for [Fronting the integrated " +"reverse-proxy webserver with another reverse-proxy](docs/configuring-" +"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" +"webserver-with-another-reverse-proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:1064 +msgid "2023-02-25" +msgstr "" + +#: ../../../CHANGELOG.md:1066 +msgid "rageshake support" +msgstr "" + +#: ../../../CHANGELOG.md:1068 +msgid "" +"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook" +" can now install and configure the [rageshake](https://github.com/matrix-" +"org/rageshake) bug report server." +msgstr "" + +#: ../../../CHANGELOG.md:1070 +msgid "" +"Additional details are available in [Setting up rageshake](docs" +"/configuring-playbook-rageshake.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1073 +msgid "2023-02-17" +msgstr "" + +#: ../../../CHANGELOG.md:1075 +msgid "Synapse templates customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1077 +msgid "The playbook can now help you customize Synapse's templates." +msgstr "" + +#: ../../../CHANGELOG.md:1079 +msgid "" +"Additional details are available in the [Customizing templates](docs" +"/configuring-playbook-synapse.md#customizing-templates) section of our " +"Synapse documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1081 +msgid "The matrix-redis role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1083 +msgid "" +"**TLDR**: the `matrix-redis` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1085 +msgid "" +"The `matrix-redis` role (which configures [Redis](https://redis.io/)) has" +" been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"redis). This makes it possible to easily use it in other Ansible " +"playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1087 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Ntfy or not. If you're making use " +"of Ntfy via this playbook, you will need to update variable references in" +" your `vars.yml` file (`matrix_redis_` -> `redis_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1089 +msgid "The matrix-ntfy role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1091 +msgid "" +"**TLDR**: the `matrix-ntfy` role is now included from another repository." +" Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1093 +msgid "" +"The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has " +"been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"ntfy). This makes it possible to easily use it in other Ansible " +"playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1095 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Ntfy or not. If you're making use " +"of Ntfy via this playbook, you will need to update variable references in" +" your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1098 +msgid "2023-02-15" +msgstr "" + +#: ../../../CHANGELOG.md:1100 +msgid "The matrix-grafana role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1102 +msgid "" +"**TLDR**: the `matrix-grafana` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1104 +msgid "" +"The `matrix-grafana` role (which configures [Grafana](docs/configuring-" +"playbook-prometheus-grafana.md)) has been extracted from the playbook and" +" now lives in its [own repository](https://github.com/mother-of-all-self-" +"hosting/ansible-role-grafana). This makes it possible to easily use it in" +" other Ansible playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1106 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Grafana or not. If you're making " +"use of Grafana via this playbook, you will need to update variable " +"references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1109 +msgid "2023-02-13" +msgstr "" + +#: ../../../CHANGELOG.md:1111 +msgid "The matrix-backup-borg role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1113 +msgid "" +"**TLDR**: the `matrix-backup-borg` role is now included from another " +"repository. Some variables have been renamed. All functionality remains " +"intact." +msgstr "" + +#: ../../../CHANGELOG.md:1115 +msgid "" +"Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` " +"role (which configures [BorgBackup](docs/configuring-playbook-backup-" +"borg.md)) has been extracted from the playbook and now lives in its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"backup_borg). This makes it possible to easily use it in other Ansible " +"playbooks and will become part of [nextcloud-docker-ansible-" +"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) " +"soon." +msgstr "" + +#: ../../../CHANGELOG.md:1117 +msgid "" +"You need to **update your roles** (`just roles` or `make roles`) " +"regardless of whether you're enabling Borg's backup functionality or not." +" If you're making use of BorgBackup via this playbook, you will need to " +"update variable references in your `vars.yml` file (`matrix_backup_borg_`" +" -> `backup_borg_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1120 +msgid "2023-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1122 +msgid "" +"(Backward Compatibility) Reverse-proxy configuration changes and initial " +"Traefik support" +msgstr "" + +#: ../../../CHANGELOG.md:1124 +msgid "**TLDR**:" +msgstr "" + +#: ../../../CHANGELOG.md:1126 +msgid "" +"there's a new `matrix_playbook_reverse_proxy_type` variable (see " +"[roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-" +"base/defaults/main.yml)), which lets you tell the playbook what reverse-" +"proxy setup you'd like to have. This makes it easier for people who want " +"to do reverse-proxying in other ways." +msgstr "" + +#: ../../../CHANGELOG.md:1127 +msgid "" +"the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still" +" `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing" +" `matrix-nginx-proxy` users should not observe any changes** and can stay" +" on this for now." +msgstr "" + +#: ../../../CHANGELOG.md:1128 +msgid "" +"**Users who use their [own other webserver](docs/configuring-playbook-" +"own-webserver.md) (e.g. Apache, etc.) need to change** " +"`matrix_playbook_reverse_proxy_type` to something like `other-on-same-" +"host`, `other-on-another-host` or `other-nginx-non-container`" +msgstr "" + +#: ../../../CHANGELOG.md:1129 +msgid "" +"we now have **optional [Traefik](https://traefik.io/) support**, so you " +"could easily host Matrix and other Traefik-native services in containers " +"on the same server. Traefik support is still experimental (albeit, good " +"enough) and will improve over time. It does work, but certain esoteric " +"features may not be there yet." +msgstr "" + +#: ../../../CHANGELOG.md:1130 +msgid "" +"**Traefik will become the default reverse-proxy in the near future**. " +"`matrix-nginx-proxy` will either remain as an option, or be completely " +"removed to simplify the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1132 +msgid "Motivation for redoing our reverse-proxy setup" +msgstr "" + +#: ../../../CHANGELOG.md:1134 +msgid "" +"The playbook has supported various reverse-proxy setups for a long time. " +"We have various configuration variables (`matrix_nginx_proxy_enabled`, " +"various `_host_bind_port` variables, etc.) which allow the playbook to " +"adapt to these different setups. The whole situation was messy though - " +"hard to figure out and with lots of variables to toggle to make things " +"work as you'd expect - huge **operational complexity**." +msgstr "" + +#: ../../../CHANGELOG.md:1136 +msgid "" +"We love containers, proven by the fact that **everything** that this " +"playbook manages runs in a container. Yet, we weren't allowing people to " +"easily host other web-exposed containers alongside Matrix services on the" +" same server. We were using `matrix-nginx-proxy` (our integrated " +"[nginx](https://nginx.org/) server), which was handling web-exposure and " +"SSL termination for our own services, but we **weren't helping you with " +"all your other containers**." +msgstr "" + +#: ../../../CHANGELOG.md:1138 +msgid "" +"People who were **using `matrix-nginx-proxy`** were on the happy path on " +"which everything worked well by default (Matrix-wise), **but** could not " +"easily run other web-exposed services on their Matrix server because " +"`matrix-nginx-proxy` was occupying ports `80` and `443`. Other services " +"which wanted to get web exposure either had to be plugged into `matrix-" +"nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-" +"nginx-proxy` in favor of something else." +msgstr "" + +#: ../../../CHANGELOG.md:1140 +msgid "" +"Of those that decided to forgo `matrix-nginx-proxy`, many were **using " +"nginx** on the same server without a container. This was likely some " +"ancient nginx version, depending on your choice of distro. The Matrix " +"playbook was trying to be helpful and even with " +"`matrix_nginx_proxy_enabled: false` was still generating nginx " +"configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files " +"were adapted for inclusion into an nginx server running locally. " +"Disabling the `matrix-nginx-proxy` role like this, yet still having it " +"produce files is a bit disgusting, but it's what we've had since the " +"early beginnings of this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1142 +msgid "" +"Others still, wanted to run Matrix locally (no SSL certificates), " +"regardless of which web server technology this relied on, and then " +"**reverse-proxy from another machine on the network** which was doing SSL" +" termination. These people were:" +msgstr "" + +#: ../../../CHANGELOG.md:1144 +msgid "" +"*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined" +" with exposing services manually (setting `_bind_port` variables)" +msgstr "" + +#: ../../../CHANGELOG.md:1145 +msgid "" +"*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in " +"`http`-only mode (no SSL certificate retrieval)." +msgstr "" + +#: ../../../CHANGELOG.md:1147 +msgid "" +"Despite this operational complexity, things worked and were reasonably " +"flexible to adapt to all these situations." +msgstr "" + +#: ../../../CHANGELOG.md:1149 +msgid "" +"When using `matrix-nginx-proxy` as is, we still had another problem - one" +" of **internal playbook complexity**. Too many services need to be web-" +"exposed (port 80/443, SSL certificates). Because of this, they all had to" +" integrate with the `matrix-nginx-proxy` role. Tens of different roles " +"explicitly integrating with `matrix-nginx-proxy` is not what we call " +"clean. The `matrix-nginx-proxy` role contains variables for many of these" +" roles (yikes). Other roles were more decoupled from it and were " +"injecting configuration into `matrix-nginx-proxy` at runtime - see all " +"the `inject_into_nginx_proxy.yml` task files in this playbook (more " +"decoupled, but still.. yikes)." +msgstr "" + +#: ../../../CHANGELOG.md:1151 +msgid "" +"The next problem is one of **efficiency, interoperability and cost-" +"saving**. We're working on other playbooks:" +msgstr "" + +#: ../../../CHANGELOG.md:1153 +msgid "" +"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" +"/vaultwarden-docker-ansible-deploy) for hosting the " +"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an " +"alternative implementation of the [Bitwarden](https://bitwarden.com/) " +"password manager" +msgstr "" + +#: ../../../CHANGELOG.md:1154 +msgid "" +"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source " +"code hosting service" +msgstr "" + +#: ../../../CHANGELOG.md:1155 +msgid "" +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy) - for hosting the " +"[Nextcloud](https://nextcloud.com/) groupware platform" +msgstr "" + +#: ../../../CHANGELOG.md:1157 +msgid "" +"We'd love for users to be able to **seamlessly use all these playbooks " +"(and others, even) against a single server**. We don't want `matrix-" +"nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for " +"other services to join in on the party. Such a thing forces people into " +"running multiple servers (one for each service), which does provide nice " +"security benefits, but is costly and ineffiecient. We'd like to make " +"self-hosting these services cheap and easy." +msgstr "" + +#: ../../../CHANGELOG.md:1159 +msgid "" +"These other playbooks have been using [Traefik](https://traefik.io/) as " +"their default reverse-proxy for a long time. They can all coexist nicely " +"together (as an example, see the " +"[Interoperability](https://github.com/spantaleev/nextcloud-docker-" +"ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md)" +" documentation for the [Nextcloud playbook](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining " +"Traefik support, it will be able to interoperate with them. If you're " +"going this way, make sure to have the Matrix playbook install Traefik and" +" have the others use `*_reverse_proxy_type: other-traefik-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1161 +msgid "" +"Finally, at [etke.cc - a managed Matrix server hosting " +"service](https://etke.cc) (built on top of this playbook, and " +"coincidentally [turning 2 years old today](https://etke.cc/news" +"/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people " +"to host some additional services besides Matrix components. Exposing " +"these services to the web requires ugly hacks and configuration files " +"being dropped into `/matrix/nginx-proxy/conf.d`. We believe that " +"everything should run in independent containers and be exposed to the web" +" via a Traefik server, without a huge Ansible role like `matrix-nginx-" +"proxy` that everything else needs to integrate with." +msgstr "" + +#: ../../../CHANGELOG.md:1163 +msgid "How do these changes fix all these problems?" +msgstr "" + +#: ../../../CHANGELOG.md:1165 +msgid "" +"The new `matrix_playbook_reverse_proxy_type` lets you easily specify your" +" preferred reverse-proxy type, including `other-on-same-host`, `other-on-" +"another-host` and `none`, so people who'd like to reverse-proxy with " +"their own web server have more options now." +msgstr "" + +#: ../../../CHANGELOG.md:1167 +msgid "" +"Using Traefik greatly simplifies things, so going forward we'll have a " +"simpler and easier to maintain playbook, which is also interoperable with" +" other services." +msgstr "" + +#: ../../../CHANGELOG.md:1169 +msgid "" +"Traefik is a web server, which has been specifically **designed for " +"reverse-proxying to services running in containers**. It's ideal for " +"usage in an Ansible playbook which runs everything in containers." +msgstr "" + +#: ../../../CHANGELOG.md:1171 +msgid "" +"**Traefik obtains SSL certificates automatically**, so there's no need " +"for plugging additional tools like [Certbot](https://certbot.eff.org/) " +"into your web server (like we were doing in the `matrix-nginx-proxy` " +"role). No more certificate renewal timers, web server reloading timers, " +"etc. It's just simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1173 +msgid "" +"Traefik is a **modern web server**. " +"[HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is " +"supported already (experimentally) and will move to stable soon, in the " +"upcoming Traefik v3 release." +msgstr "" + +#: ../../../CHANGELOG.md:1175 +msgid "" +"Traefik does not lock important functionality we'd like to use into [plus" +" packages like nginx does](https://www.nginx.com/products/nginx/), " +"leading us to resolve to configuration workarounds. The default Traefik " +"package is good enough as it is." +msgstr "" + +#: ../../../CHANGELOG.md:1177 +msgid "Where we're at right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1179 +msgid "" +"`matrix_playbook_reverse_proxy_type` still defaults to a value of " +"`playbook-managed-nginx`." +msgstr "" + +#: ../../../CHANGELOG.md:1181 +msgid "" +"Unless we have some regression, **existing `matrix-nginx-proxy` users " +"should be able to update their Matrix server and not observe any " +"changes**. Their setup should still remain on nginx and everything should" +" still work as expected." +msgstr "" + +#: ../../../CHANGELOG.md:1183 +msgid "" +"**Users using [their own webservers](docs/configuring-playbook-own-" +"webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** " +"to something like `other-on-same-host`, `other-on-another-host` or " +"`other-nginx-non-container`. Previously, they could toggle " +"`matrix_nginx_proxy_enabled` to `false`, and that made the playbook " +"automatically expose services locally. Currently, we only do this if you " +"change the reverse-proxy type to `other-on-same-host`, `other-on-another-" +"host` or `other-nginx-non-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1185 +msgid "How do I explicitly switch to Traefik right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1187 +msgid "" +"**Users who wish to migrate to Traefik** today, can do so by **adding** " +"this to their configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1195 +msgid "" +"You may still need to keep certain old `matrix_nginx_proxy_*` variables " +"(like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using " +"Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` " +"variables just in case. In the future, reliance on `matrix-nginx-proxy` " +"will be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1197 +msgid "" +"Switching to Traefik will obtain new SSL certificates from Let's Encrypt " +"(stored in `/matrix/traefik/ssl/acme.json`). **The switch is " +"reversible**. You can always go back to `playbook-managed-nginx` if " +"Traefik is causing you trouble." +msgstr "" + +#: ../../../CHANGELOG.md:1199 +msgid "" +"**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik " +"and nginx will uninstall the Traefik role and all of its data (under " +"`/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you" +" do it often." +msgstr "" + +#: ../../../CHANGELOG.md:1201 +msgid "" +"Treafik directly reverse-proxies to **some** services right now, but for " +"most other services it goes through `matrix-nginx-proxy` (e.g. Traefik ->" +" `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, " +"even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being" +" installed in local-only mode. This will improve with time." +msgstr "" + +#: ../../../CHANGELOG.md:1203 +msgid "" +"Some services (like [Coturn](docs/configuring-playbook-turn.md) and " +"[Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be " +"reverse-proxied to directly from Traefik, so they require direct access " +"to SSL certificate files extracted out of Traefik. The playbook does this" +" automatically thanks to a new " +"[com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper)" +" role utilizing the [traefik-certs-dumper](https://github.com/ldez" +"/traefik-certs-dumper) tool." +msgstr "" + +#: ../../../CHANGELOG.md:1205 +msgid "" +"Our Traefik setup mostly works, but certain esoteric features may not " +"work. If you have a default setup, we expect you to have a good " +"experience." +msgstr "" + +#: ../../../CHANGELOG.md:1207 +msgid "Where we're going in the near future?" +msgstr "" + +#: ../../../CHANGELOG.md:1209 +msgid "" +"The `matrix-nginx-proxy` role is quite messy. It manages both nginx and " +"Certbot and its certificate renewal scripts and timers. It generates " +"configuration even when the role is disabled (weird). Although it doesn't" +" directly reach into variables from other roles, it has explicit " +"awareness of various other services that it reverse-proxies to " +"(`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-" +"ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is " +"probably to just get rid of the whole thing at some point." +msgstr "" + +#: ../../../CHANGELOG.md:1211 +msgid "For now, `matrix-nginx-proxy` will stay around." +msgstr "" + +#: ../../../CHANGELOG.md:1213 +msgid "" +"As mentioned above, Traefik still reverse-proxies to some (most) services" +" by going through a local-only `matrix-nginx-proxy` server. This has " +"allowed us to add Traefik support to the playbook early on (without " +"having to rework all services), but is not the final goal. We'll **work " +"on making each service support Traefik natively**, so that traffic will " +"not need to go through `matrix-nginx-proxy` anymore. In the end, choosing" +" Traefik should only give you a pure Traefik installation with no " +"`matrix-nginx-proxy` in sight." +msgstr "" + +#: ../../../CHANGELOG.md:1215 +msgid "" +"As Traefik support becomes complete and proves to be stable for a while, " +"especially as a playbook default, we will **most likely remove `matrix-" +"nginx-proxy` completely**. It will likely be some months before this " +"happens though. Keeping support for both Traefik and nginx in the " +"playbook will be a burden, especially with most of us running Traefik in " +"the future. The Traefik role should do everything nginx does in a better " +"and cleaner way. Users who use their own `nginx` server on the Matrix " +"server will be inconvenienced, as nothing will generate ready-to-include " +"nginx configuration for them. Still, we hope it won't be too hard to " +"migrate their setup to another way of doing things, like:" +msgstr "" + +#: ../../../CHANGELOG.md:1217 +msgid "" +"not using nginx anymore. A common reason for using nginx until now was " +"that you were running other containers and you need your own nginx to " +"reverse-proxy to all of them. Just switch them to Traefik as well." +msgstr "" + +#: ../../../CHANGELOG.md:1218 +msgid "" +"running Traefik in local-only mode " +"(`traefik_config_entrypoint_web_secure_enabled: false`) and using some " +"nginx configuration which reverse-proxies to Traefik (we should introduce" +" examples for this in `examples/nginx`)." +msgstr "" + +#: ../../../CHANGELOG.md:1220 +msgid "How do I help?" +msgstr "" + +#: ../../../CHANGELOG.md:1222 +msgid "You can help by:" +msgstr "" + +#: ../../../CHANGELOG.md:1224 +msgid "" +"**explicitly switching your server to Traefik** right now (see example " +"configuration in [How do I explicitly switch to Traefik right now?](#how-" +"do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting " +"troubles" +msgstr "" + +#: ../../../CHANGELOG.md:1226 +msgid "" +"**adding native Traefik support to a role** (requires adding Traefik " +"labels, etc.) - for inspiration, see these roles " +"([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting" +"/ansible-role-prometheus-node-exporter), " +"[prometheus_postgres_exporter](https://github.com/mother-of-all-self-" +"hosting/ansible-role-prometheus-postgres-exporter)) and how they're " +"hooked into the playbook via " +"[group_vars/matrix_servers](group_vars/matrix_servers)." +msgstr "" + +#: ../../../CHANGELOG.md:1228 +msgid "" +"**adding reverse-proxying examples for nginx users** in `examples/nginx`." +" People who insist on using their own `nginx` server on the same Matrix " +"host, can run Traefik in local-only mode " +"(`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy" +" to the Traefik server" +msgstr "" + +#: ../../../CHANGELOG.md:1231 +msgid "2023-02-10" +msgstr "" + +#: ../../../CHANGELOG.md:1233 +msgid "Matrix Authentication Support for Jitsi" +msgstr "" + +#: ../../../CHANGELOG.md:1235 +msgid "" +"Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk " +"gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for " +"authentication (via [Matrix User Verification Service](https://github.com" +"/matrix-org/matrix-user-verification-service))." +msgstr "" + +#: ../../../CHANGELOG.md:1237 +msgid "" +"Additional details are available in the [Authenticate using Matrix OpenID" +" (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-" +"using-matrix-openid-auth-type-matrix)." +msgstr "" + +#: ../../../CHANGELOG.md:1239 +msgid "Draupnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:1241 +msgid "" +"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " +"install and configure the [Draupnir](https://github.com/the-draupnir-" +"project/Draupnir) moderation tool (bot). Draupnir is a fork of " +"[Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook " +"has supported for a long time) maintained by Mjolnir's former lead " +"developer." +msgstr "" + +#: ../../../CHANGELOG.md:1243 +msgid "" +"Additional details are available in [Setting up Draupnir](docs" +"/configuring-playbook-bot-draupnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1246 +msgid "2023-02-05" +msgstr "" + +#: ../../../CHANGELOG.md:1248 +msgid "The matrix-prometheus-postgres-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1250 +msgid "" +"**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included " +"from another repository. Some variables have been renamed. All " +"functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1252 +msgid "" +"The `matrix-prometheus-postgres-exporter` role (which configures " +"[Prometheus Postgres Exporter](https://github.com/prometheus-" +"community/postgres_exporter)) has been extracted from the playbook and " +"now lives in its own repository at https://github.com/mother-of-all-self-" +"hosting/ansible-role-prometheus-postgres-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1254 +msgid "" +"It's still part of the playbook, but is now installed via `ansible-" +"galaxy` (by running `just roles` / `make roles`). Some variables have " +"been renamed (`matrix_prometheus_postgres_exporter_` -> " +"`prometheus_postgres_exporter_`, etc.). The playbook will report all " +"variables that you need to rename to get upgraded. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1256 +msgid "" +"The `matrix-prometheus-services-proxy-connect` role has bee adjusted to " +"help integrate the new `prometheus_postgres_exporter` role with our own " +"services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300 +msgid "" +"Other roles which aren't strictly related to Matrix are likely to follow " +"this fate of moving to their own repositories. Extracting them out allows" +" other Ansible playbooks to make use of these roles easily." +msgstr "" + +#: ../../../CHANGELOG.md:1261 +msgid "2023-01-26" +msgstr "" + +#: ../../../CHANGELOG.md:1263 +msgid "Coturn can now use host-networking" +msgstr "" + +#: ../../../CHANGELOG.md:1265 +msgid "" +"Large Coturn deployments (with a huge range of ports specified via " +"`matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) " +"experience a huge slowdown with how Docker publishes all these ports " +"(setting up firewall forwarding rules), which leads to a very slow Coturn" +" service startup and shutdown." +msgstr "" + +#: ../../../CHANGELOG.md:1267 +msgid "" +"Such deployments don't need to run Coturn within a private container " +"network anymore. Coturn can now run with host-networking by using " +"configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1273 +msgid "" +"With such a configuration, **Docker no longer needs to configure " +"thousands of firewall forwarding rules** each time Coturn starts and " +"stops. This, however, means that **you will need to ensure these ports " +"are open** in your firewall yourself." +msgstr "" + +#: ../../../CHANGELOG.md:1275 +msgid "" +"Thanks to us [tightening Coturn security](#backward-compatibility-" +"tightening-coturn-security-can-lead-to-connectivity-issues), running " +"Coturn with host-networking should be safe and not expose neither other " +"services running on the host, nor other services running on the local " +"network." +msgstr "" + +#: ../../../CHANGELOG.md:1277 +msgid "" +"(Backward Compatibility) Tightening Coturn security can lead to " +"connectivity issues" +msgstr "" + +#: ../../../CHANGELOG.md:1279 +msgid "" +"**TLDR**: users who run and access their Matrix server on a private " +"network (likely a small minority of users) may experience connectivity " +"issues with our new default Coturn blocklists. They may need to override " +"`matrix_coturn_denied_peer_ips` and remove some IP ranges from it." +msgstr "" + +#: ../../../CHANGELOG.md:1281 +msgid "" +"Inspired by [this security " +"article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-" +"access-control-protection/), we've decided to make use of Coturn's " +"`denied-peer-ip` functionality to prevent relaying network traffic to " +"certain private IP subnets. This ensures that your Coturn server won't " +"accidentally try to forward traffic to certain services running on your " +"local networks. We run Coturn in a container and in a private container " +"network by default, which should prevent such access anyway, but having " +"additional block layers in place is better." +msgstr "" + +#: ../../../CHANGELOG.md:1283 +msgid "" +"If you access your Matrix server from a local network and need Coturn to " +"relay to private IP addresses, you may observe that relaying is now " +"blocked due to our new default `denied-peer-ip` lists (specified in " +"`matrix_coturn_denied_peer_ips`). If you experience such connectivity " +"problems, consider overriding this setting in your `vars.yml` file and " +"removing certain networks from it." +msgstr "" + +#: ../../../CHANGELOG.md:1285 +msgid "" +"We've also added `no-multicast-peers` to the default Coturn " +"configuration, but we don't expect this to cause trouble for most people." +msgstr "" + +#: ../../../CHANGELOG.md:1288 +msgid "2023-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:1290 +msgid "The matrix-prometheus-node-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1292 +msgid "" +"**TLDR**: the `matrix-prometheus-node-exporter` role is now included from" +" another repository. Some variables have been renamed. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1294 +msgid "" +"The `matrix-prometheus-node-exporter` role (which configures [Prometheus " +"node exporter](https://github.com/prometheus/node_exporter)) has been " +"extracted from the playbook and now lives in its own repository at " +"https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-" +"node-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1296 +msgid "" +"It's still part of the playbook, but is now installed via `ansible-" +"galaxy` (by running `just roles` / `make roles`). Some variables have " +"been renamed (`matrix_prometheus_node_exporter_` -> " +"`prometheus_node_exporter_`, etc.). The playbook will report all " +"variables that you need to rename to get upgraded. All functionality " +"remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1298 +msgid "" +"A new `matrix-prometheus-services-proxy-connect` role was added to the " +"playbook to help integrate the new `prometheus_node_exporter` role with " +"our own services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1303 +msgid "2023-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:1305 +msgid "Support for running commands via just" +msgstr "" + +#: ../../../CHANGELOG.md:1307 +msgid "" +"We've previously used [make](https://www.gnu.org/software/make/) for " +"easily running some playbook commands (e.g. `make roles` which triggers " +"`ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still " +"around and you can still run these commands." +msgstr "" + +#: ../../../CHANGELOG.md:1309 +msgid "" +"In addition, we've added support for running commands via " +"[just](https://github.com/casey/just) - a more modern command-runner " +"alternative to `make`. Instead of `make roles`, you can now run `just " +"roles` to accomplish the same." +msgstr "" + +#: ../../../CHANGELOG.md:1311 +msgid "" +"Our [justfile](justfile) already defines some additional helpful " +"**shortcut** commands that weren't part of our `Makefile`. Here are some " +"examples:" +msgstr "" + +#: ../../../CHANGELOG.md:1313 +msgid "" +"`just install-all` to trigger the much longer `ansible-playbook -i " +"inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-" +"created,start` command" +msgstr "" + +#: ../../../CHANGELOG.md:1314 +msgid "" +"`just install-all --ask-vault-pass` - commands also support additional " +"arguments (`--ask-vault-pass` will be appended to the above installation " +"command)" +msgstr "" + +#: ../../../CHANGELOG.md:1315 +msgid "" +"`just run-tags install-mautrix-slack,start` - to run specific playbook " +"tags" +msgstr "" + +#: ../../../CHANGELOG.md:1316 +msgid "`just start-all` - (re-)starts all services" +msgstr "" + +#: ../../../CHANGELOG.md:1317 +msgid "`just stop-group postgres` - to stop only the Postgres service" +msgstr "" + +#: ../../../CHANGELOG.md:1318 +msgid "" +"`just register-user alice secret-password yes` - registers an `alice` " +"user with the `secret-password` password and admin access (admin = `yes`)" +msgstr "" + +#: ../../../CHANGELOG.md:1320 +msgid "Additional helpful commands and shortcuts may be defined in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1322 +msgid "" +"This is all completely optional. If you find it difficult to [install " +"`just`](https://github.com/casey/just#installation) or don't find any of " +"this convenient, feel free to run all commands manually." +msgstr "" + +#: ../../../CHANGELOG.md:1325 +msgid "2023-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:1327 +msgid "mautrix-slack support" +msgstr "" + +#: ../../../CHANGELOG.md:1329 +msgid "" +"Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the " +"playbook now supports bridging to [Slack](https://slack.com/) via the " +"[mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting " +"up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-" +"slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1331 +msgid "" +"**Note**: this is a new Slack bridge. The playbook still retains Slack " +"bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-" +"appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-" +"bridge-mx-puppet-slack.md). You're free to use the bridge that serves you" +" better, or even all three of them (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1334 +msgid "2023-01-10" +msgstr "" + +#: ../../../CHANGELOG.md:1336 +msgid "ChatGPT support" +msgstr "" + +#: ../../../CHANGELOG.md:1338 +msgid "" +"Thanks to [@bertybuttface](https://github.com/bertybuttface), the " +"playbook can now help you set up [matrix-chatgpt-" +"bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through " +"which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) " +"model." +msgstr "" + +#: ../../../CHANGELOG.md:1340 +msgid "" +"See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-" +"chatgpt.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1343 +msgid "2022-11-30" +msgstr "" + +#: ../../../CHANGELOG.md:1345 +msgid "" +"matrix-postgres-backup has been replaced by the ansible-role-postgres-" +"backup external role" +msgstr "" + +#: ../../../CHANGELOG.md:1347 +msgid "" +"Just like we've [replaced Postgres with an external role](#matrix-" +"postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-" +"role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an" +" external role - " +"[com.devture.ansible.role.postgres_backup](https://github.com/mother-of-" +"all-self-hosting/ansible-role-postgres_backup)." +msgstr "" + +#: ../../../CHANGELOG.md:1349 +msgid "" +"You'll need to rename your `matrix_postgres_backup`-prefixed variables " +"such that they use a `postgres_backup` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1352 +msgid "2022-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:1354 +msgid "" +"matrix-postgres has been replaced by the ansible-role-postgres external " +"role" +msgstr "" + +#: ../../../CHANGELOG.md:1356 +msgid "" +"**TLDR**: the tasks that install the integrated Postgres server now live " +"in an external role - [ansible-role-postgres](https://github.com/mother-" +"of-all-self-hosting/ansible-role-postgres). You'll need to run `make " +"roles` to install it, and to also rename your `matrix_postgres`-prefixed " +"variables to use a `devture_postgres` prefix (e.g. " +"`matrix_postgres_connection_password` -> `postgres_connection_password`)." +" All your data will still be there! Some scripts have moved " +"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." +msgstr "" + +#: ../../../CHANGELOG.md:1358 +msgid "" +"The `matrix-postgres` role that has been part of the playbook for a long " +"time has been replaced with the [ansible-role-" +"postgres](https://github.com/mother-of-all-self-hosting/ansible-role-" +"postgres) role. This was done as part of our work to [use external roles " +"for some things](#the-playbook-now-uses-external-roles-for-some-things) " +"for better code re-use and maintainability." +msgstr "" + +#: ../../../CHANGELOG.md:1360 +msgid "" +"The new role is an upgraded version of the old `matrix-postgres` role " +"with these notable differences:" +msgstr "" + +#: ../../../CHANGELOG.md:1362 +msgid "" +"it uses different names for its variables (`matrix_postgres` -> " +"`devture_postgres`)" +msgstr "" + +#: ../../../CHANGELOG.md:1363 +msgid "" +"when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-" +"postgresql), it will vacuum all your databases, not just the Synapse one" +msgstr "" + +#: ../../../CHANGELOG.md:1365 +msgid "" +"You'll need to run `make roles` to install the new role. You would also " +"need to rename your `matrix_postgres`-prefixed variables to use a " +"`devture_postgres` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1367 +msgid "" +"Note: the systemd service still remains the same - `matrix-" +"postgres.service`. Your data will still be in `/matrix/postgres`, etc. " +"Postgres-related scripts will be moved to `/matrix/postgres/bin` " +"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, " +"etc). Also see [The playbook no longer installs scripts in /usr/local/bin" +"](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." +msgstr "" + +#: ../../../CHANGELOG.md:1369 +msgid "The playbook no longer installs scripts to /usr/local/bin" +msgstr "" + +#: ../../../CHANGELOG.md:1371 +msgid "The locations of various scripts installed by the playbook have changed." +msgstr "" + +#: ../../../CHANGELOG.md:1373 +msgid "" +"The playbook no longer contaminates your `/usr/local/bin` directory. All " +"scripts installed by the playbook now live in `bin/` directories under " +"`/matrix`. Some examples are below:" +msgstr "" + +#: ../../../CHANGELOG.md:1375 +msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`" +msgstr "" + +#: ../../../CHANGELOG.md:1376 +msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1377 +msgid "" +"`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> " +"`/matrix/ssl/bin/lets-encrypt-certificates-renew`" +msgstr "" + +#: ../../../CHANGELOG.md:1378 +msgid "" +"`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin" +"/register-user`" +msgstr "" + +#: ../../../CHANGELOG.md:1381 +msgid "2022-11-25" +msgstr "" + +#: ../../../CHANGELOG.md:1383 +msgid "2x-5x performance improvements in playbook runtime" +msgstr "" + +#: ../../../CHANGELOG.md:1385 +msgid "" +"**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and " +"various other tags). It also has new `--tags=install-*` tags (like " +"`--tags=install-all`), which skip uninstallation tasks and bring an " +"additional 2.5x speedup. In total, the playbook can maintain your server " +"5 times faster." +msgstr "" + +#: ../../../CHANGELOG.md:1387 +msgid "" +"Our [etke.cc managed Matrix hosting service](https://etke.cc) runs " +"maintenance against hundreds of servers, so the playbook being fast means" +" a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible)" +" (which is an extension of this one) is growing to support more and more " +"services (besides just Matrix), so the Matrix playbook being leaner " +"prevents runtimes from becoming too slow and improves the customer " +"experience." +msgstr "" + +#: ../../../CHANGELOG.md:1389 +msgid "" +"Even when running `ansible-playbook` manually (as most of us here do), " +"it's beneficial not to waste time and CPU resources." +msgstr "" + +#: ../../../CHANGELOG.md:1391 +msgid "" +"Recently, a few large optimizations have been done to this playbook and " +"its external roles (see [The playbook now uses external roles for some " +"things](#the-playbook-now-uses-external-roles-for-some-things) and don't " +"forget to run `make roles`):" +msgstr "" + +#: ../../../CHANGELOG.md:1393 +msgid "" +"Replacing Ansible `import_tasks` calls with `include_tasks`, which " +"decreased runtime in half. Using `import_tasks` is slower and causes " +"Ansible to go through and skip way too many tasks (tasks which could have" +" been skipped altogether by not having Ansible include them in the first " +"place). On an experimental VM, **deployment time was decreased from ~530 " +"seconds to ~250 seconds**." +msgstr "" + +#: ../../../CHANGELOG.md:1395 +msgid "" +"Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, " +"e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible " +"tasks pertaining to installation, while skipping uninstallation tasks. In" +" most cases, people are maintaining the same setup or they're *adding* " +"new components. Removing components is rare. Running thousands of " +"uninstallation tasks each time is wasteful. On an experimental VM, " +"**deployment time was decreased from ~250 seconds (`--tags=setup-all`) to" +" ~100 seconds (`--tags=install-all`)**." +msgstr "" + +#: ../../../CHANGELOG.md:1397 +msgid "" +"You can still use `--tags=setup-all`. In fact, that's the best way to " +"ensure your server is reconciled with the `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1399 +msgid "" +"If you know you haven't uninstalled any services since the last time you " +"ran the playbook, you could run `--tags=install-all` instead and benefit " +"from quicker runtimes. It should be noted that a service may become " +"\"eligible for uninstallation\" even if your `vars.yml` file remains the " +"same. In rare cases, we toggle services from being auto-installed to " +"being optional, like we did on the 17th of March 2022 when we made [ma1sd" +" not get installed by default](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-" +"identity-server-no-longer-installed-by-default). In such rare cases, " +"you'd also need to run `--tags=setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:1402 +msgid "2022-11-22" +msgstr "" + +#: ../../../CHANGELOG.md:1404 +msgid "Automatic `matrix_architecture` determination" +msgstr "" + +#: ../../../CHANGELOG.md:1406 +msgid "" +"From now on, the playbook automatically determines your server's " +"architecture and sets the `matrix_architecture` variable accordingly. You" +" no longer need to set this variable manually in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1408 +msgid "Docker and the Docker SDK for Python are now installed via external roles" +msgstr "" + +#: ../../../CHANGELOG.md:1412 +msgid "" +"Docker will now be installed on the server via the " +"[geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) " +"Ansible role. If you'd like to manage the Docker installation yourself, " +"you can disable the playbook's installation of Docker by setting " +"`matrix_playbook_docker_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1414 +msgid "" +"The Docker SDK for Python (named `docker-python`, `python-docker`, etc. " +"on the different platforms) is now also installed by another role " +"([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python))." +" To disable this role and install the necessary tools yourself, use " +"`devture_docker_sdk_for_python_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1416 +msgid "" +"If you're hitting issues with Docker installation or Docker SDK for " +"Python installation, consider reporting bugs or contributing to these " +"other projects." +msgstr "" + +#: ../../../CHANGELOG.md:1418 +msgid "" +"These additional roles are downloaded into the playbook directory (to " +"`roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an " +"easy shortcut for invoking the `ansible-galaxy` command to download these" +" roles." +msgstr "" + +#: ../../../CHANGELOG.md:1421 +msgid "2022-11-20" +msgstr "" + +#: ../../../CHANGELOG.md:1423 +msgid "" +"(Backward Compatibility Break) Changing how reverse-proxying to Synapse " +"works - now via a `matrix-synapse-reverse-proxy-companion` service" +msgstr "" + +#: ../../../CHANGELOG.md:1425 +msgid "" +"**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx " +"service, which helps with reverse-proxying to Synapse and its various " +"worker processes (if workers are enabled), so that `matrix-nginx-proxy` " +"can be relieved of this role. `matrix-nginx-proxy` still remains as the " +"public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-" +"reverse-proxy-companion` is just one more reverse-proxy thrown into the " +"mix for convenience. People with a more custom reverse-proxying " +"configuration may be affected - see [Webserver configuration](#webserver-" +"configuration) below." +msgstr "" + +#: ../../../CHANGELOG.md:1427 +msgid "Background" +msgstr "" + +#: ../../../CHANGELOG.md:1429 +msgid "" +"Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. " +"When Synapse is running in worker mode, the reverse-proxying " +"configuration is more complicated (different requests need to go to " +"different Synapse worker processes). `matrix-nginx-proxy` had " +"configuration for sending each URL endpoint to the correct Synapse worker" +" responsible for handling it. However, sometimes people like to disable " +"`matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own" +" webserver, instead of this playbook's nginx proxy](docs/configuring-" +"playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1431 +msgid "" +"Because `matrix-nginx-proxy` was so central to request forwarding, when " +"it was disabled and Synapse was running with workers enabled, there was " +"nothing which could forward requests to the correct place anymore.. which" +" caused [problems such as this one affecting " +"Dimension](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/2090)." +msgstr "" + +#: ../../../CHANGELOG.md:1433 +msgid "Solution" +msgstr "" + +#: ../../../CHANGELOG.md:1435 +msgid "" +"From now on, `matrix-nginx-proxy` is relieved of its function of reverse-" +"proxying to Synapse and its various worker processes. This role is now " +"handled by the new `matrix-synapse-reverse-proxy-companion` nginx service" +" and works even if `matrix-nginx-proxy` is disabled. The purpose of the " +"new `matrix-synapse-reverse-proxy-companion` service is to:" +msgstr "" + +#: ../../../CHANGELOG.md:1437 +msgid "" +"serve as a companion to Synapse and know how to reverse-proxy to Synapse " +"correctly (no matter if workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1439 +msgid "" +"provide a unified container address for reaching Synapse (no matter if " +"workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1440 +msgid "" +"`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server " +"API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1441 +msgid "" +"`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server " +"(Federation) API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1443 +msgid "" +"simplify `matrix-nginx-proxy` configuration - it now only needs to send " +"requests to `matrix-synapse-reverse-proxy-companion` or `matrix-" +"dendrite`, etc., without having to worry about workers" +msgstr "" + +#: ../../../CHANGELOG.md:1445 +msgid "" +"allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is " +"disabled" +msgstr "" + +#: ../../../CHANGELOG.md:1447 +msgid "" +"`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-" +"proxy in the playbook. All traffic goes through it before reaching any of" +" the services. It's just that now the Synapse traffic is routed through " +"`matrix-synapse-reverse-proxy-companion` like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1449 +msgid "" +"(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> " +"(`matrix-synapse` or some Synapse worker))." +msgstr "" + +#: ../../../CHANGELOG.md:1451 +msgid "" +"Various services (like Dimension, etc.) still talk to Synapse via " +"`matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) " +"preferentially. They only talk to Synapse via the reverse-proxy companion" +" (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-" +"nginx-proxy` is disabled. Services should not be talking to Synapse (e.g." +" `https://matrix-synapse:8008` directly anymore), because when workers " +"are enabled, that's the Synapse `master` process and may not be serving " +"all URL endpoints needed by the service." +msgstr "" + +#: ../../../CHANGELOG.md:1453 +msgid "Webserver configuration" +msgstr "" + +#: ../../../CHANGELOG.md:1455 +msgid "" +"if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`," +" which is the default for the playbook), you don't need to do anything" +msgstr "" + +#: ../../../CHANGELOG.md:1457 +msgid "" +"if you're using your own `nginx` webserver running on the server, you " +"shouldn't be affected. The `/matrix/nginx/conf.d` configuration and " +"exposed ports that you're relying on will automatically be updated in a " +"way that should work" +msgstr "" + +#: ../../../CHANGELOG.md:1459 +msgid "" +"if you're using another local webserver (e.g. Apache, etc.) and haven't " +"changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't " +"be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and" +" `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed " +"on `127.0.0.1` by default - just not by the `matrix-synapse` container " +"from now on, but by the `matrix-synapse-reverse-proxy-companion` " +"container instead" +msgstr "" + +#: ../../../CHANGELOG.md:1461 +msgid "" +"if you've been exposing `matrix-synapse` ports " +"(`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, " +"you should consider exposing `matrix-synapse-reverse-proxy-companion` " +"ports instead" +msgstr "" + +#: ../../../CHANGELOG.md:1463 +msgid "" +"if you're running Traefik and reverse-proxying directly to the `matrix-" +"synapse` container, you should start reverse-proxying to the `matrix-" +"synapse-reverse-proxy-companion` container instead. See [our updated " +"Traefik example configuration](docs/configuring-playbook-own-webserver.md" +"#sample-configuration-for-running-behind-traefik-20). Note: we now " +"recommend calling the federation entry point `federation` (instead of " +"`synapse`) and reverse-proxying the federation traffic via `matrix-nginx-" +"proxy`, instead of sending it directly to Synapse (or `matrix-synapse-" +"reverse-proxy-companion`). This makes the configuration simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1466 +msgid "2022-11-05" +msgstr "" + +#: ../../../CHANGELOG.md:1468 +msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad" +msgstr "" + +#: ../../../CHANGELOG.md:1470 +msgid "" +"Until now, [Etherpad](https://etherpad.org/) (which [the playbook could " +"install for you](docs/configuring-playbook-etherpad.md)) required the " +"[Dimension integration manager](docs/configuring-playbook-dimension.md) " +"to also be installed, because Etherpad was hosted on the Dimension domain" +" (at `dimension.example.com/etherpad`)." +msgstr "" + +#: ../../../CHANGELOG.md:1472 +msgid "" +"From now on, Etherpad can be installed in `standalone` mode on " +"`etherpad.example.com` and used even without Dimension. This is much more" +" versatile, so the playbook now defaults to this new mode " +"(`etherpad_mode: standalone`)." +msgstr "" + +#: ../../../CHANGELOG.md:1474 +msgid "If you've already got both Etherpad and Dimension in use you could:" +msgstr "" + +#: ../../../CHANGELOG.md:1476 +msgid "" +"**either** keep hosting Etherpad under the Dimension domain by adding " +"`etherpad_mode: dimension` to your `vars.yml` file. All your existing " +"room widgets will continue working at the same URLs and no other changes " +"will be necessary." +msgstr "" + +#: ../../../CHANGELOG.md:1478 +msgid "" +"**or**, you could change to hosting Etherpad separately on " +"`etherpad.example.com`. You will need to [configure a DNS record](docs" +"/configuring-dns.md) for this new domain. You will also need to " +"reconfigure Dimension to use the new pad URLs " +"(`https://etherpad.example.com/…`) going forward (refer to our " +"[configuring Etherpad documentation](docs/configuring-playbook-" +"etherpad.md)). All your existing room widgets (which still use " +"`https://dimension.example.com/etherpad/…`) will break as Etherpad is not" +" hosted there anymore. You will need to re-add them or to consider not " +"using `standalone` mode" +msgstr "" + +#: ../../../CHANGELOG.md:1481 +msgid "2022-11-04" +msgstr "" + +#: ../../../CHANGELOG.md:1483 +msgid "The playbook now uses external roles for some things" +msgstr "" + +#: ../../../CHANGELOG.md:1485 +msgid "" +"**TLDR**: when updating the playbook and before running it, you'll need " +"to run `make roles` to make [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"download dependency roles (see the [`requirements.yml` " +"file](requirements.yml)) to the `roles/galaxy` directory. Without this, " +"the playbook won't work." +msgstr "" + +#: ../../../CHANGELOG.md:1487 +msgid "" +"We're in the process of trimming the playbook and making it reuse Ansible" +" roles." +msgstr "" + +#: ../../../CHANGELOG.md:1489 +msgid "Starting now, the playbook is composed of 2 types of Ansible roles:" +msgstr "" + +#: ../../../CHANGELOG.md:1491 +msgid "those that live within the playbook itself (`roles/custom/*`)" +msgstr "" + +#: ../../../CHANGELOG.md:1493 +msgid "" +"those downloaded from other sources (using [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"to `roles/galaxy`, based on the [`requirements.yml` " +"file](requirements.yml)). These roles are maintained by us or by other " +"people from the Ansible community." +msgstr "" + +#: ../../../CHANGELOG.md:1495 +msgid "" +"We're doing this for greater code-reuse (across Ansible playbooks, " +"including our own related playbooks [gitea-docker-ansible-" +"deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and " +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. " +"Until now, certain features were copy-pasted across playbooks or were " +"maintained separately in each one, with improvements often falling " +"behind. We've also tended to do too much by ourselves - installing Docker" +" on the server from our `matrix-base` role, etc. - something that we'd " +"rather not do anymore by switching to the " +"[geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." +msgstr "" + +#: ../../../CHANGELOG.md:1497 +msgid "" +"Some variable names will change during the transition to having more and " +"more external (galaxy) roles. There's a new " +"`custom/matrix_playbook_migration` role added to the playbook which will " +"tell you about these changes each time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1499 +msgid "" +"**From now on**, every time you update the playbook (well, every time the" +" `requirements.yml` file changes), it's best to run `make roles` to " +"update the roles downloaded from other sources. `make roles` is a " +"shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed" +" by the [`make`](https://www.gnu.org/software/make/) utility) which " +"ultimately runs [ansible-" +"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " +"to download Ansible roles. If you don't have `make`, you can also " +"manually run the commands seen in the `Makefile`." +msgstr "" + +#: ../../../CHANGELOG.md:1502 +msgid "2022-10-14" +msgstr "" + +#: ../../../CHANGELOG.md:1504 +msgid "synapse-s3-storage-provider support" +msgstr "" + +#: ../../../CHANGELOG.md:1506 +msgid "" +"**`synapse-s3-storage-provider` support is very new and still relatively " +"untested. Using it may cause data loss.**" +msgstr "" + +#: ../../../CHANGELOG.md:1508 +msgid "" +"You can now store your Synapse media repository files on Amazon S3 (or " +"another S3-compatible object store) using [synapse-s3-storage-" +"provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a " +"media provider for Synapse (Python module), which should work faster and " +"more reliably than our previous [Goofys](docs/configuring-" +"playbook-s3-goofys.md) implementation (Goofys will continue to work)." +msgstr "" + +#: ../../../CHANGELOG.md:1510 +msgid "" +"This is not just for initial installations. Users with existing files " +"(stored in the local filesystem) can also migrate their files to " +"`synapse-s3-storage-provider`." +msgstr "" + +#: ../../../CHANGELOG.md:1512 +msgid "" +"To get started, see our [Storing Synapse media files on Amazon S3 with " +"synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3" +"-storage-provider.md) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1514 +msgid "Synapse container image customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1516 +msgid "" +"We now support customizing the Synapse container image by adding " +"additional build steps to its " +"[`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." +msgstr "" + +#: ../../../CHANGELOG.md:1518 +msgid "" +"Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-" +"support) is actually built on this. When `s3-storage-provider` is " +"enabled, we automatically add additional build steps to install its " +"Python module into the Synapse image." +msgstr "" + +#: ../../../CHANGELOG.md:1520 +msgid "" +"Besides this kind of auto-added build steps (for components supported by " +"the playbook), we also let you inject your own custom build steps using " +"configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1531 +msgid "" +"People who have needed to customize Synapse previously had to fork the " +"git repository, make their changes to the `Dockerfile` there, point the " +"playbook to the new repository " +"(`matrix_synapse_container_image_self_build_repo`) and enable self-" +"building from scratch (`matrix_synapse_container_image_self_build: " +"true`). This is harder and slower." +msgstr "" + +#: ../../../CHANGELOG.md:1533 +msgid "" +"With the new Synapse-customization feature in the playbook, we use the " +"original upstream (pre-built, if available) Synapse image and only build " +"on top of it, right on the Matrix server. This is much faster than " +"building all of Synapse from scratch." +msgstr "" + +#: ../../../CHANGELOG.md:1536 +msgid "2022-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:1538 +msgid "matrix-ldap-registration-proxy support" +msgstr "" + +#: ../../../CHANGELOG.md:1540 +msgid "" +"Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), " +"we now support installing [matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" - a proxy which handles Matrix registration requests and forwards them " +"to LDAP." +msgstr "" + +#: ../../../CHANGELOG.md:1542 +msgid "" +"See our [Setting up matrix-ldap-registration-proxy](docs/configuring-" +"playbook-matrix-ldap-registration-proxy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1545 +msgid "2022-09-15" +msgstr "" + +#: ../../../CHANGELOG.md:1547 +msgid "" +"(Potential Backward Compatibility Break) Major improvements to Synapse " +"workers" +msgstr "" + +#: ../../../CHANGELOG.md:1549 +msgid "" +"People who are interested in running a Synapse worker setup should know " +"that **our Synapse worker implementation is much more powerful now**:" +msgstr "" + +#: ../../../CHANGELOG.md:1551 +msgid "we've added support for [Stream writers](#stream-writers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1552 +msgid "" +"we've added support for [multiple federation sender workers](#multiple-" +"federation-sender-workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1553 +msgid "" +"we've added support for [multiple pusher workers](#multiple-pusher-" +"workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1554 +msgid "" +"we've added support for [running background tasks on a worker" +"](#background-tasks-can-run-on-a-worker)" +msgstr "" + +#: ../../../CHANGELOG.md:1555 +msgid "" +"we've restored support for [`appservice` workers](#appservice-worker-" +"support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1556 +msgid "" +"we've restored support for [`user_dir` workers](#user-directory-worker-" +"support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1557 +msgid "" +"we've made it possible to [reliably use more than 1 `media_repository` " +"worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" +msgstr "" + +#: ../../../CHANGELOG.md:1558 +msgid "" +"see the [Potential Backward Incompatibilities after these Synapse worker " +"changes](#potential-backward-incompatibilities-after-these-synapse-" +"worker-changes)" +msgstr "" + +#: ../../../CHANGELOG.md:1560 +msgid "Stream writers support" +msgstr "" + +#: ../../../CHANGELOG.md:1562 +msgid "" +"From now on, the playbook lets you easily set up various [stream writer " +"workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-" +"writers) which can handle different streams (`events` stream; `typing` " +"URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, " +"`receipts` URL endpoints, `presence` URL endpoints). All of this work was" +" previously handled by the main Synapse process, but can now be offloaded" +" to stream writer worker processes." +msgstr "" + +#: ../../../CHANGELOG.md:1564 +msgid "" +"If you're using `matrix_synapse_workers_preset: one-of-each`, you'll " +"automatically get 6 additional workers (one for each of the above stream " +"types). Our `little-federation-helper` preset (meant to be quite minimal " +"and focusing in improved federation performance) does not include stream " +"writer workers." +msgstr "" + +#: ../../../CHANGELOG.md:1566 +msgid "" +"If you'd like to customize the number of workers we also make that " +"possible using these variables:" +msgstr "" + +#: ../../../CHANGELOG.md:1579 +msgid "Multiple federation sender workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1581 +msgid "" +"Until now, we only supported a single `federation_sender` worker " +"(`matrix_synapse_workers_federation_sender_workers_count` could either be" +" `0` or `1`). From now on, you can have as many as you want to help with " +"your federation traffic." +msgstr "" + +#: ../../../CHANGELOG.md:1583 +msgid "Multiple pusher workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1585 +msgid "" +"Until now, we only supported a single `pusher` worker " +"(`matrix_synapse_workers_pusher_workers_count` could either be `0` or " +"`1`). From now on, you can have as many as you want to help with pushing " +"notifications out." +msgstr "" + +#: ../../../CHANGELOG.md:1587 +msgid "Background tasks can run on a worker" +msgstr "" + +#: ../../../CHANGELOG.md:1589 +msgid "" +"From now on, you can put [background task processing on a worker](https" +"://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." +msgstr "" + +#: ../../../CHANGELOG.md:1591 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`background` worker automatically. You can also control the `background` " +"workers count with `matrix_synapse_workers_background_workers_count`. " +"Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1593 +msgid "Appservice worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1595 +msgid "" +"We previously had an `appservice` worker type, which [Synapse deprecated " +"in v1.59.0](https://github.com/element-" +"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" +"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" +" did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1597 +msgid "" +"The new way to implement such workers is by using a `generic_worker` and " +"dedicating it to the task of talking to Application Services. From now " +"on, we have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1599 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`appservice` worker automatically. You can also control the `appservice` " +"workers count with `matrix_synapse_workers_appservice_workers_count`. " +"Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1601 +msgid "User Directory worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1603 +msgid "" +"We previously had a `user_dir` worker type, which [Synapse deprecated in " +"v1.59.0](https://github.com/element-" +"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" +"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" +" did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1605 +msgid "" +"The new way to implement such workers is by using a `generic_worker` and " +"dedicating it to the task of serving the user directory. From now on, we " +"have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1607 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " +"`user_dir` worker automatically. You can also control the `user_dir` " +"workers count with `matrix_synapse_workers_user_dir_workers_count`. Only" +" `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1609 +msgid "Using more than 1 media repository worker is now more reliable" +msgstr "" + +#: ../../../CHANGELOG.md:1611 +msgid "" +"With `matrix_synapse_workers_preset: one-of-each`, we only launch one " +"`media_repository` worker." +msgstr "" + +#: ../../../CHANGELOG.md:1613 +msgid "" +"If you've been configuring " +"`matrix_synapse_workers_media_repository_workers_count` manually, you may" +" have increased that to more workers. When multiple media repository " +"workers are in use, background tasks related to the media repository must" +" always be configured to run on a single `media_repository` worker via " +"`media_instance_running_background_jobs`. Until now, we weren't doing " +"this correctly, but we now are." +msgstr "" + +#: ../../../CHANGELOG.md:1615 +msgid "Potential Backward Incompatibilities after these Synapse worker changes" +msgstr "" + +#: ../../../CHANGELOG.md:1617 +msgid "Below we'll discuss **potential backward incompatibilities**." +msgstr "" + +#: ../../../CHANGELOG.md:1619 +msgid "" +"**Worker names** (container names, systemd services, worker configuration" +" files) **have changed**. Workers are now labeled sequentially (e.g. " +"`matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-" +"generic-0`). The playbook will handle these changes automatically." +msgstr "" + +#: ../../../CHANGELOG.md:1621 +msgid "" +"Due to increased worker types support above, people who use " +"`matrix_synapse_workers_preset: one-of-each` should be aware that with " +"these changes, **the playbook will deploy 9 additional workers** (6 " +"stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background " +"task worker). This **may increase RAM/CPU usage**, etc. If you find your " +"server struggling, consider disabling some workers with the appropriate " +"`matrix_synapse_workers_*_workers_count` variables." +msgstr "" + +#: ../../../CHANGELOG.md:1623 +msgid "" +"**Metric endpoints have also changed** " +"(`/metrics/synapse/worker/generic_worker-18111` -> " +"`/metrics/synapse/worker/generic-worker-0`). If you're [collecting " +"metrics to an external Prometheus server](docs/configuring-playbook-" +"prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-" +"server), consider revisiting our [Collecting Synapse worker metrics to an" +" external Prometheus server](docs/configuring-playbook-prometheus-" +"grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-" +"server) docs and updating your Prometheus configuration. **If you're " +"collecting metrics to the integrated Prometheus server** (not enabled by " +"default), **your Prometheus configuration will be updated " +"automatically**. Old data (from before this change) may stick around " +"though." +msgstr "" + +#: ../../../CHANGELOG.md:1625 +msgid "" +"**the format of `matrix_synapse_workers_enabled_list` has changed**. You " +"were never advised to use this variable for directly creating workers (we" +" advise people to control workers using `matrix_synapse_workers_preset` " +"or by tweaking `matrix_synapse_workers_*_workers_count` variables only), " +"but some people may have started using the " +"`matrix_synapse_workers_enabled_list` variable to gain more control over " +"workers. If you're one of them, you'll need to adjust its value. See " +"`roles/custom/matrix-synapse/defaults/main.yml` for more information on " +"the new format. The playbook will also do basic validation and complain " +"if you got something wrong." +msgstr "" + +#: ../../../CHANGELOG.md:1628 +msgid "2022-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:1630 +msgid "Cactus Comments support" +msgstr "" + +#: ../../../CHANGELOG.md:1632 +msgid "" +"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " +"the playbook can now set up [Cactus Comments](https://cactus.chat) - " +"federated comment system for the web based on Matrix." +msgstr "" + +#: ../../../CHANGELOG.md:1634 +msgid "" +"See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-" +"comments.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1637 +msgid "2022-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:1639 +msgid "Postmoogle email bridge support" +msgstr "" + +#: ../../../CHANGELOG.md:1641 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up the new " +"[Postmoogle](https://github.com/etkecc/postmoogle) email bridge. " +"Postmoogle is like the [email2matrix " +"bridge](https://github.com/devture/email2matrix) (also [already supported" +" by the playbook](docs/configuring-playbook-email2matrix.md)), but more " +"capable and with the intention to soon support *sending* emails, not just" +" receiving." +msgstr "" + +#: ../../../CHANGELOG.md:1643 +msgid "" +"See our [Setting up Postmoogle email bridging](docs/configuring-playbook-" +"bridge-postmoogle.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1646 +msgid "2022-08-10" +msgstr "" + +#: ../../../CHANGELOG.md:1648 +msgid "mautrix-whatsapp default configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:1650 +msgid "" +"In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/2012), we've made some changes to the default " +"configuration used by the `mautrix-whatsapp` bridge." +msgstr "" + +#: ../../../CHANGELOG.md:1652 +msgid "" +"If you're using this bridge, you should look into this PR and see if the " +"new configuration suits you. If not, you can always change individual " +"preferences in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1654 +msgid "" +"Most notably, spaces support has been enabled by default. The bridge will" +" now group rooms into a Matrix space. **If you've already bridged to " +"Whatsapp** prior to this update, you will need to send `!wa sync space` " +"to the bridge bot to make it create the space and put your existing rooms" +" into it." +msgstr "" + +#: ../../../CHANGELOG.md:1657 +msgid "2022-08-09" +msgstr "" + +#: ../../../CHANGELOG.md:1659 +msgid "Conduit support" +msgstr "" + +#: ../../../CHANGELOG.md:1661 +msgid "" +"Thanks to [Charles Wright](https://github.com/cvwright), we now have " +"optional experimental [Conduit](https://conduit.rs) homeserver support " +"for new installations. This comes as a follow-up to the playbook getting " +"[Dendrite support](#dendrite-support) earlier this year." +msgstr "" + +#: ../../../CHANGELOG.md:1663 +msgid "" +"Existing Synapse or Dendrite installations do **not** need to be updated." +" **Synapse is still the default homeserver implementation** installed by " +"the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1665 +msgid "" +"To try out Conduit, we recommend that you **use a new server** and the " +"following `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1671 +msgid "" +"**The homeserver implementation of an existing server cannot be changed**" +" (e.g. from Synapse or Dendrite to Conduit) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1674 +msgid "2022-07-29" +msgstr "" + +#: ../../../CHANGELOG.md:1676 +msgid "mautrix-discord support" +msgstr "" + +#: ../../../CHANGELOG.md:1678 +msgid "" +"Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the " +"playbook now supports bridging to [Discord](https://discordapp.com/) via " +"the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our " +"[Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-" +"mautrix-discord.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1680 +msgid "" +"**Note**: this is a new Discord bridge. The playbook still retains " +"Discord bridging via [matrix-appservice-discord](docs/configuring-" +"playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs" +"/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use " +"the bridge that serves you better, or even all three of them (for " +"different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1683 +msgid "2022-07-27" +msgstr "" + +#: ../../../CHANGELOG.md:1685 +msgid "matrix-appservice-kakaotalk support" +msgstr "" + +#: ../../../CHANGELOG.md:1687 +msgid "" +"The playbook now supports bridging to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +" via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk) - a bridge based on [node-" +"kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and " +"some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks" +" to [hnarjis](https://github.com/hnarjis) for helping us add support for " +"this!" +msgstr "" + +#: ../../../CHANGELOG.md:1689 +msgid "" +"See our [Setting up Appservice Kakaotalk bridging](docs/configuring-" +"playbook-bridge-appservice-kakaotalk.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1692 +msgid "2022-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:1694 +msgid "maubot support" +msgstr "" + +#: ../../../CHANGELOG.md:1696 +msgid "" +"Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for " +"starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr " +"(@moan0s)](https://github.com/moan0s) for finishing up (in [PR " +"#1894](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/1894)), the playbook can now help you set up " +"[maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot " +"system." +msgstr "" + +#: ../../../CHANGELOG.md:1698 +msgid "" +"See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) " +"documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1701 +msgid "2022-07-14" +msgstr "" + +#: ../../../CHANGELOG.md:1703 +msgid "mx-puppet-skype removal" +msgstr "" + +#: ../../../CHANGELOG.md:1705 +msgid "" +"The playbook no longer includes the [mx-puppet-" +"skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it " +"has been broken and unmaintained for a long time. Users that have " +"`matrix_mx_puppet_skype_enabled` in their configuration files will " +"encounter an error when running the playbook until they remove references" +" to this bridge from their configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1707 +msgid "" +"To completely clean up your server from `mx-puppet-skype`'s presence on " +"it:" +msgstr "" + +#: ../../../CHANGELOG.md:1709 +msgid "" +"ensure your Ansible configuration (`vars.yml` file) no longer contains " +"`matrix_mx_puppet_skype_*` references" +msgstr "" + +#: ../../../CHANGELOG.md:1710 +msgid "" +"stop and disable the systemd service (run `systemctl disable --now " +"matrix-mx-puppet-skype` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1711 +msgid "" +"delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-" +"skype.service` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1712 +msgid "" +"delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on" +" the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1713 +msgid "" +"drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-" +"postgres-cli` on the server, and execute the `DROP DATABASE " +"matrix_mx_puppet_skype;` query there)" +msgstr "" + +#: ../../../CHANGELOG.md:1715 +msgid "" +"If you still need bridging to [Skype](https://www.skype.com/), consider " +"switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-" +"bridge) instead. See [Setting up Go Skype Bridge bridging](docs" +"/configuring-playbook-bridge-go-skype-bridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1717 +msgid "" +"If you think this is a mistake and `mx-puppet-skype` works for you (or " +"you get it to work somehow), let us know and we may reconsider this " +"removal." +msgstr "" + +#: ../../../CHANGELOG.md:1719 +msgid "signald (0.19.0+) upgrade requires data migration" +msgstr "" + +#: ../../../CHANGELOG.md:1721 +msgid "" +"In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) " +"(used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." +msgstr "" + +#: ../../../CHANGELOG.md:1723 +msgid "" +"Back in the [`v0.19.0` released of " +"signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md)" +" (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-" +"data` command had been added that migrates avatars, group images, " +"attachments, etc., into the database (those were previously stored in the" +" filesystem)." +msgstr "" + +#: ../../../CHANGELOG.md:1725 +msgid "" +"If you've been using the mautrix-signal bridge for a while, you may have " +"files stored in the local filesystem, which will need to be upgraded." +msgstr "" + +#: ../../../CHANGELOG.md:1727 +msgid "" +"We attempt to do this data migration automatically every time Signald " +"starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` " +"systemd unit definition." +msgstr "" + +#: ../../../CHANGELOG.md:1729 +msgid "" +"Keep an eye on your Signal bridge and let us know (in our [support " +"room](README.md#support) or in [Pull Request " +"#1921](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/1921)) if you experience any trouble!" +msgstr "" + +#: ../../../CHANGELOG.md:1732 +msgid "2022-07-05" +msgstr "" + +#: ../../../CHANGELOG.md:1734 +msgid "Ntfy push notifications support" +msgstr "" + +#: ../../../CHANGELOG.md:1736 +msgid "" +"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " +"playbook can now install a [ntfy](https://ntfy.sh/) push notifications " +"server for you." +msgstr "" + +#: ../../../CHANGELOG.md:1738 +msgid "" +"See our [Setting up the ntfy push notifications server](docs/configuring-" +"playbook-ntfy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1741 +msgid "2022-06-23" +msgstr "" + +#: ../../../CHANGELOG.md:1743 +msgid "(Potential Backward Compatibility Break) Changes around metrics collection" +msgstr "" + +#: ../../../CHANGELOG.md:1745 +msgid "" +"**TLDR**: we've made extensive **changes to metrics exposure/collection, " +"which concern people using an external Prometheus server**. If you don't " +"know what that is, you don't need to read below." +msgstr "" + +#: ../../../CHANGELOG.md:1747 +msgid "" +"**Why do major changes to metrics**? Because various services were " +"exposing metrics in different, hacky, ways. Synapse was exposing metrics " +"at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the " +"`matrix.example.com`. The Hookshot role was **repurposing** the Granana " +"web UI domain (`stats.example.com`) for exposing its metrics on " +"`stats.example.com/hookshot/metrics`, while protecting these routes using" +" Basic Authentication **normally used for Synapse** " +"(`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were " +"advising for more `stats.example.com` usage in manual ways. Each role was" +" doing things differently and mixing variables from other roles. Each " +"metrics endpoint was ending up in a different place, protected by who " +"knows what Basic Authentication credentials (if protected at all)." +msgstr "" + +#: ../../../CHANGELOG.md:1749 +msgid "" +"**The solution**: a completely revamped way to expose metrics to an " +"external Prometheus server. We are **introducing new " +"`https://matrix.example.com/metrics/*` endpoints**, where various " +"services *can* expose their metrics, for collection by external " +"Prometheus servers. To enable the `/metrics/*` endpoints, use " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a " +"way to protect access using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)." +" See the `matrix-nginx-proxy` role or our [Collecting metrics to an " +"external Prometheus server](docs/configuring-playbook-prometheus-" +"grafana.md#collecting-metrics-to-an-external-prometheus-server) " +"documentation for additional variables around " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`." +msgstr "" + +#: ../../../CHANGELOG.md:1751 +msgid "" +"**If you are using the [Hookshot bridge](docs/configuring-playbook-" +"bridge-hookshot.md)**, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1752 +msgid "**Metrics may not be enabled by default anymore**:" +msgstr "" + +#: ../../../CHANGELOG.md:1753 +msgid "" +"If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot " +"metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: " +"true`). These metrics will be collected from the local (in-container) " +"Prometheus over the container network." +msgstr "" + +#: ../../../CHANGELOG.md:1754 +msgid "" +"**If Prometheus is not enabled** (you are either not using Prometheus or " +"are using an external one), **Hookshot metrics will not be enabled by " +"default anymore**. Feel free to enable them by setting " +"`matrix_hookshot_metrics_enabled: true`. Also, see below." +msgstr "" + +#: ../../../CHANGELOG.md:1755 +msgid "" +"When metrics are meant to be **consumed by an external Prometheus " +"server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to " +"`true`, so that metrics would be exposed (proxied) \"publicly\" on " +"`https://matrix.example.com/metrics/hookshot`. To make use of this, " +"you'll also need to enable the new `https://matrix.example.com/metrics/*`" +" endpoints mentioned above, using " +"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our " +"[Collecting metrics to an external Prometheus server](docs/configuring-" +"playbook-prometheus-grafana.md#collecting-metrics-to-an-external-" +"prometheus-server) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1756 +msgid "" +"**We've changed the URL we're exposing Hookshot metrics at** for external" +" Prometheus servers. Until now, you were advised to consume Hookshot " +"metrics from `https://stats.example.com/hookshot/metrics` (working in " +"conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now " +"on, **this no longer works**. As described above, you need to start " +"consuming metrics from `https://matrix.example.com/metrics/hookshot`." +msgstr "" + +#: ../../../CHANGELOG.md:1758 +msgid "" +"**If you're using node-exporter** " +"(`matrix_prometheus_node_exporter_enabled: true`) and would like to " +"collect its metrics from an external Prometheus server, see " +"`matrix_prometheus_node_exporter_metrics_proxying_enabled` described in " +"our [Collecting metrics to an external Prometheus server](docs" +"/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" +"external-prometheus-server) documentation. You will be able to collect " +"its metrics from `https://matrix.example.com/metrics/node-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1760 +msgid "" +"**If you're using [postgres-exporter](docs/configuring-playbook-" +"prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) " +"and would like to collect its metrics from an external Prometheus server," +" see " +"`matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled`" +" described in our [Collecting metrics to an external Prometheus " +"server](docs/configuring-playbook-prometheus-grafana.md#collecting-" +"metrics-to-an-external-prometheus-server) documentation. You will be able" +" to collect its metrics from `https://matrix.example.com/metrics" +"/postgres-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1762 +msgid "" +"**If you're using Synapse** and would like to collect its metrics from an" +" external Prometheus server, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1764 +msgid "" +"Exposing metrics is now done using " +"`matrix_synapse_metrics_proxying_enabled`, not " +"`matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to " +"enable metrics using `matrix_synapse_metrics_enabled: true` before " +"exposing them." +msgstr "" + +#: ../../../CHANGELOG.md:1765 +msgid "" +"Protecting metrics endpoints using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" +" is now done in another way. See our [Collecting metrics to an external " +"Prometheus server](docs/configuring-playbook-prometheus-grafana.md" +"#collecting-metrics-to-an-external-prometheus-server) documentation" +msgstr "" + +#: ../../../CHANGELOG.md:1766 +msgid "" +"If Synapse metrics are exposed, they will be made available at " +"`https://matrix.example.com/metrics/synapse/main-process` or " +"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers" +" are enabled), not at `https://matrix.example.com/_synapse/metrics` and " +"`https://matrix.example.com/_synapse-worker-…/metrics`" +msgstr "" + +#: ../../../CHANGELOG.md:1767 +msgid "" +"The playbook still generates an `external_prometheus.yml.example` sample " +"file for scraping Synapse from Prometheus as described in [Collecting " +"Synapse worker metrics to an external Prometheus server](docs" +"/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-" +"metrics-to-an-external-prometheus-server), but it's now saved under " +"`/matrix/synapse` (not `/matrix`)." +msgstr "" + +#: ../../../CHANGELOG.md:1769 +msgid "" +"**If you where already using a external Prometheus server** before this " +"change, and you gave a hashed version of the password as a variable, the " +"playbook will now take care of hashing the password for you. Thus, you " +"need to provide the non-hashed version now." +msgstr "" + +#: ../../../CHANGELOG.md:1771 +msgid "2022-06-13" +msgstr "" + +#: ../../../CHANGELOG.md:1773 +msgid "go-skype-bridge bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1775 +msgid "" +"Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can" +" now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-" +"bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." +msgstr "" + +#: ../../../CHANGELOG.md:1777 +msgid "" +"See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-" +"bridge-go-skype-bridge.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1779 +msgid "" +"The playbook has supported [mx-puppet-skype](https://github.com/Sorunome" +"/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype " +"bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since " +"[2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." +msgstr "" + +#: ../../../CHANGELOG.md:1782 +msgid "2022-06-09" +msgstr "" + +#: ../../../CHANGELOG.md:1784 +msgid "Running Ansible in a container can now happen on the Matrix server itself" +msgstr "" + +#: ../../../CHANGELOG.md:1786 +msgid "" +"If you're tired of being on an old and problematic Ansible version, you " +"can now run [run Ansible in a container on the Matrix server " +"itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-" +"server-itself)." +msgstr "" + +#: ../../../CHANGELOG.md:1789 +msgid "2022-05-31" +msgstr "" + +#: ../../../CHANGELOG.md:1791 +msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:1793 +msgid "" +"Synapse v1.60 will try to add a new unique index to `state_group_edges` " +"upon startup and could fail if your database is corrupted." +msgstr "" + +#: ../../../CHANGELOG.md:1795 +msgid "" +"We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade " +"notes](https://github.com/element-" +"hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-" +"state_group_edges-could-fail-if-your-database-is-corrupted) mention it, " +"so we're giving you a heads up here in case you're unlucky." +msgstr "" + +#: ../../../CHANGELOG.md:1797 +msgid "" +"**If Synapse fails to start** after your next playbook run, you'll need " +"to:" +msgstr "" + +#: ../../../CHANGELOG.md:1799 +msgid "SSH into the Matrix server" +msgstr "" + +#: ../../../CHANGELOG.md:1800 +msgid "launch `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1801 +msgid "switch to the `synapse` database: `\\c synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:1802 +msgid "run the following SQL query:" +msgstr "" + +#: ../../../CHANGELOG.md:1821 +msgid "" +"You could then restart services: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=start`" +msgstr "" + +#: ../../../CHANGELOG.md:1824 +msgid "2022-04-25" +msgstr "" + +#: ../../../CHANGELOG.md:1826 +msgid "Buscarron bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1828 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron " +"bot](https://github.com/etkecc/buscarron). It's a bot you can use to send" +" any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../CHANGELOG.md:1830 +msgid "" +"See our [Setting up Buscarron](docs/configuring-playbook-bot-" +"buscarron.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1833 +msgid "2022-04-21" +msgstr "" + +#: ../../../CHANGELOG.md:1835 +msgid "matrix-registration-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1837 +msgid "" +"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " +"the playbook can now help you set up [matrix-registration-" +"bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is " +"used to create and manage registration tokens for a Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1839 +msgid "" +"See our [Setting up matrix-registration-bot](docs/configuring-playbook-" +"bot-matrix-registration-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1842 +msgid "2022-04-19" +msgstr "" + +#: ../../../CHANGELOG.md:1844 +msgid "BorgBackup support" +msgstr "" + +#: ../../../CHANGELOG.md:1846 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now set up " +"[Borg](https://www.borgbackup.org/) backups with " +"[borgmatic](https://torsion.org/borgmatic/) of your Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1848 +msgid "" +"See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md)" +" documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1850 +msgid "" +"(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers " +"may require manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1852 +msgid "" +"If you're running a worker setup for Synapse " +"(`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade " +"notes](https://github.com/element-" +"hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-" +"for-application-services) say that you may need to take special care when" +" upgrading:" +msgstr "" + +#: ../../../CHANGELOG.md:1854 +msgid "" +"Synapse v1.57.0 includes a change to the way transaction IDs are managed " +"for application services. If your deployment uses a dedicated worker for " +"application service traffic, **it must be stopped** when the database is " +"upgraded (which normally happens when the main process is upgraded), to " +"ensure the change is made safely without any risk of reusing transaction " +"IDs." +msgstr "" + +#: ../../../CHANGELOG.md:1856 +msgid "" +"If you're not running an `appservice` worker " +"(`matrix_synapse_workers_preset: little-federation-helper` or " +"`matrix_synapse_workers_appservice_workers_count: 0`), you are probably " +"safe to upgrade as per normal, without taking any special care." +msgstr "" + +#: ../../../CHANGELOG.md:1858 +msgid "" +"If you are running a setup with an `appservice` worker, or otherwise want" +" to be on the safe side, we recommend the following upgrade path:" +msgstr "" + +#: ../../../CHANGELOG.md:1860 +msgid "Pull the latest playbook changes" +msgstr "" + +#: ../../../CHANGELOG.md:1861 +msgid "" +"Stop all services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:1862 +msgid "" +"Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:1863 +msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1864 +msgid "" +"Start the main Synapse process (`systemctl start matrix-synapse` on the " +"server)" +msgstr "" + +#: ../../../CHANGELOG.md:1865 +msgid "" +"Wait a while so that Synapse can start and complete the database " +"migrations. You can use `journalctl -fu matrix-synapse` on the server to " +"get a clue. Waiting a few minutes should also be enough." +msgstr "" + +#: ../../../CHANGELOG.md:1866 +msgid "" +"It should now be safe to start all other services. `ansible-playbook -i " +"inventory/hosts setup.yml --tags=start` will do it for you" +msgstr "" + +#: ../../../CHANGELOG.md:1869 +msgid "2022-04-14" +msgstr "" + +#: ../../../CHANGELOG.md:1871 +msgid "" +"(Compatibility Break) Changes to `docker-src` permissions necessitating " +"manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1873 +msgid "" +"Users who build container images from source will need to manually " +"correct file permissions of some directories on the server." +msgstr "" + +#: ../../../CHANGELOG.md:1875 +msgid "" +"When self-building, the playbook used to `git clone` repositories (into " +"`/matrix/SERVICE/docker-src`) using the `root` user, but now uses " +"`matrix` instead to work around [the following issue with git " +"2.35.2](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1749)." +msgstr "" + +#: ../../../CHANGELOG.md:1877 +msgid "" +"If you're on a non-`amd64` architecture (that is, you're overriding " +"`matrix_architecture` in your `vars.yml` file) or you have enabled self-" +"building for some service (e.g. `matrix_*_self_build: true`), you're " +"certainly building some container images from source and have `docker-" +"src` directories with mixed permissions lying around in various " +"`/matrix/SERVICE` directories." +msgstr "" + +#: ../../../CHANGELOG.md:1879 +msgid "" +"The playbook *could* correct these permissions automatically, but that " +"requires additional Ansible tasks in some ~45 different places - " +"something that takes considerable effort. So we ask users observing " +"errors related to `docker-src` directories to correct the problem " +"manually by **running this command on the Matrix server** (which deletes " +"all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name " +"'docker-src' | xargs rm -rf`" +msgstr "" + +#: ../../../CHANGELOG.md:1882 +msgid "2022-03-17" +msgstr "" + +#: ../../../CHANGELOG.md:1884 +msgid "(Compatibility Break) ma1sd identity server no longer installed by default" +msgstr "" + +#: ../../../CHANGELOG.md:1886 +msgid "" +"The playbook no longer installs the " +"[ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The " +"next time you run the playbook, ma1sd will be uninstalled from your " +"server, unless you explicitly enable the ma1sd service (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:1888 +msgid "" +"The main reason we used to install ma1sd by default in the past was to " +"prevent Element clients from talking to the `matrix.org` / `vector.im` " +"identity servers, by forcing it to talk to our own self-hosted (but " +"otherwise useless) identity server instead, thus preventing contact list " +"leaks." +msgstr "" + +#: ../../../CHANGELOG.md:1890 +msgid "" +"Since Element clients no longer default to using a public identity server" +" if another one is not provided, we can stop installing ma1sd." +msgstr "" + +#: ../../../CHANGELOG.md:1892 +msgid "" +"If you need to install the ma1sd identity server for some reason, you can" +" explicitly enable it by adding this to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:1899 +msgid "2022-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1901 +msgid "matrix_encryption_disabler support" +msgstr "" + +#: ../../../CHANGELOG.md:1903 +msgid "" +"We now support installing the " +"[matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler)" +" Synapse module, which lets you prevent End-to-End-Encryption from being " +"enabled by users on your homeserver. The popular opinion is that this is " +"dangerous and shouldn't be done, but there are valid use cases for " +"disabling encryption discussed [here](https://github.com/matrix-" +"org/synapse/issues/4401)." +msgstr "" + +#: ../../../CHANGELOG.md:1905 +msgid "" +"To enable this module (and prevent encryption from being used on your " +"homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to" +" your configuration. This module provides further customization. Check " +"its other configuration settings (and defaults) in `roles/custom/matrix-" +"synapse/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:1908 +msgid "2022-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:1910 +msgid "matrix-hookshot bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1912 +msgid "" +"Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can" +" now install the [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) bridge for bridging Matrix to multiple project management " +"services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-" +"hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to " +"get started." +msgstr "" + +#: ../../../CHANGELOG.md:1915 +msgid "2022-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:1917 +msgid "ARM support for matrix-corporal" +msgstr "" + +#: ../../../CHANGELOG.md:1919 +msgid "" +"[matrix-corporal](https://github.com/devture/matrix-corporal) (as of " +"version `2.2.3`) is now published to Docker Hub (see [devture/matrix-" +"corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-" +"arch container image with support for all these platforms: `linux/amd64`," +" `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to " +"self-building matrix-corporal on these ARM architectures." +msgstr "" + +#: ../../../CHANGELOG.md:1922 +msgid "2022-01-07" +msgstr "" + +#: ../../../CHANGELOG.md:1924 +msgid "Dendrite support" +msgstr "" + +#: ../../../CHANGELOG.md:1926 +msgid "" +"**TLDR**: We now have optional experimental [Dendrite](https://github.com" +"/matrix-org/dendrite) homeserver support for new installations. " +"**Existing (Synapse) installations need to be updated**, because some " +"internals changed. See [Adapting the configuration for existing Synapse " +"installations](#adapting-the-configuration-for-existing-synapse-" +"installations)." +msgstr "" + +#: ../../../CHANGELOG.md:1928 +msgid "" +"[Jip J. Dekker](https://github.com/Dekker1) did the [initial " +"work](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/818) of adding [Dendrite](https://github.com/matrix-" +"org/dendrite) support to the playbook back in January 2021. Lots of work " +"(and time) later, Dendrite support is finally ready for testing." +msgstr "" + +#: ../../../CHANGELOG.md:1930 +msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" +msgstr "" + +#: ../../../CHANGELOG.md:1932 +msgid "" +"The playbook was previously quite [Synapse](https://github.com/element-" +"hq/synapse)-centric, but can now accommodate multiple homeserver " +"implementations. Only one homeserver implementation can be active " +"(installed) at a given time." +msgstr "" + +#: ../../../CHANGELOG.md:1934 +msgid "" +"**Synapse is still the default homeserver implementation** installed by " +"the playbook. A new variable (`matrix_homeserver_implementation`) " +"controls which server implementation is enabled (`synapse` or `dendrite` " +"at the given moment)." +msgstr "" + +#: ../../../CHANGELOG.md:1936 +msgid "Adapting the configuration for existing Synapse installations" +msgstr "" + +#: ../../../CHANGELOG.md:1938 +msgid "" +"Because the playbook is not so Synapse-centric anymore, a small " +"configuration change is necessary for existing installations to bring " +"them up to date." +msgstr "" + +#: ../../../CHANGELOG.md:1940 +msgid "" +"The `vars.yml` file for **existing installations will need to be " +"updated** by adding this **additional configuration**:" +msgstr "" + +#: ../../../CHANGELOG.md:1952 +msgid "Trying out Dendrite" +msgstr "" + +#: ../../../CHANGELOG.md:1954 +msgid "" +"Finally, **to try out Dendrite**, we recommend that you **use a new " +"server** and the following addition to your `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1960 +msgid "" +"**The homeserver implementation of an existing server cannot be changed**" +" (e.g. from Synapse to Dendrite) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1962 +msgid "" +"We're excited to gain support for other homeserver implementations, like " +"[Conduit](https://conduit.rs/), etc!" +msgstr "" + +#: ../../../CHANGELOG.md:1964 +msgid "Honoroit bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1966 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook can now help you set up " +"[Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." +msgstr "" + +#: ../../../CHANGELOG.md:1968 +msgid "" +"See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) " +"documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1971 +msgid "2022-01-06" +msgstr "" + +#: ../../../CHANGELOG.md:1973 +msgid "Cinny support" +msgstr "" + +#: ../../../CHANGELOG.md:1975 +msgid "" +"Thanks to [Aine](https://gitlab.com/etke.cc) of " +"[etke.cc](https://etke.cc/), the playbook now supports " +"[Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix " +"client." +msgstr "" + +#: ../../../CHANGELOG.md:1977 +msgid "" +"By default, we still install Element Web. Still, people who'd like to try" +" Cinny out can now install it via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1979 +msgid "" +"Additional details are available in [Setting up Cinny](docs/configuring-" +"playbook-client-cinny.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1982 +msgid "2021-12-22" +msgstr "" + +#: ../../../CHANGELOG.md:1984 +msgid "Twitter bridging support via mautrix-twitter" +msgstr "" + +#: ../../../CHANGELOG.md:1986 +msgid "" +"Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas " +"Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-" +"twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging" +" to [Twitter](https://twitter.com/) can now also happen with [mautrix-" +"twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1989 +msgid "2021-12-14" +msgstr "" + +#: ../../../CHANGELOG.md:1991 +msgid "" +"(Security) Users of the Signal bridge may wish to upgrade it to work " +"around log4j vulnerability" +msgstr "" + +#: ../../../CHANGELOG.md:1993 +msgid "" +"Recently, a security vulnerability affecting the Java logging package " +"`log4j` [has been discovered](https://www.huntress.com/blog/rapid-" +"response-critical-rce-vulnerability-is-affecting-java). Software that " +"uses this Java package is potentially vulnerable." +msgstr "" + +#: ../../../CHANGELOG.md:1995 +msgid "" +"One such piece of software that is part of the playbook is the [mautrix-" +"signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), " +"which [has been patched already](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/1452). If you're running this bridge, you may " +"wish to [upgrade](./docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1998 +msgid "2021-11-11" +msgstr "" + +#: ../../../CHANGELOG.md:2000 +msgid "Dropped support for Postgres v9.6" +msgstr "" + +#: ../../../CHANGELOG.md:2002 +msgid "" +"Postgres v9.6 reached its end of life today, so the playbook will refuse " +"to run for you if you're still on that version." +msgstr "" + +#: ../../../CHANGELOG.md:2004 +msgid "" +"Synapse still supports v9.6 (for now), but we're retiring support for it " +"early, to avoid having to maintain support for so many Postgres versions." +" Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs" +"/maintenance-postgres.md#upgrading-postgresql) via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2007 +msgid "2021-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:2009 +msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2011 +msgid "" +"The mautrix-hangouts bridge is no longer receiving updates upstream and " +"is likely to stop working in the future. We still retain support for this" +" bridge in the playbook, but you're encouraged to switch away from it." +msgstr "" + +#: ../../../CHANGELOG.md:2013 +msgid "" +"There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat)" +" bridge that you can [install using the playbook](docs/configuring-" +"playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will " +"not be migrated**, however. You need to start fresh with the new bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2016 +msgid "2021-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:2018 +msgid "LinkedIn bridging support via beeper-linkedin" +msgstr "" + +#: ../../../CHANGELOG.md:2020 +msgid "" +"Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook " +"can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin)" +" bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." +msgstr "" + +#: ../../../CHANGELOG.md:2022 +msgid "" +"This brings the total number of bridges supported by the playbook up to " +"20. See all supported bridges [here](docs/configuring-playbook.md" +"#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2024 +msgid "" +"To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn" +" bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2027 +msgid "2021-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:2029 +msgid "Sygnal upgraded - ARM support and no longer requires a database" +msgstr "" + +#: ../../../CHANGELOG.md:2031 +msgid "" +"The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been " +"upgraded from `v0.9.0` to `v0.10.1`." +msgstr "" + +#: ../../../CHANGELOG.md:2033 +msgid "" +"This is an optional component for the playbook, so most of our users " +"wouldn't care about this announcement." +msgstr "" + +#: ../../../CHANGELOG.md:2035 +msgid "" +"Since this feels like a relatively big (and untested, as of yet) Sygnal " +"change, we're putting up this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2037 +msgid "" +"The new version is also available for the ARM architecture. It also no " +"longer requires a database anymore. If you need to downgrade to the " +"previous version, changing `matrix_sygnal_version` or " +"`matrix_sygnal_docker_image` will not be enough, as we've removed the " +"`database` configuration completely. You'd need to switch to an earlier " +"playbook commit." +msgstr "" + +#: ../../../CHANGELOG.md:2040 +msgid "2021-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:2042 +msgid "Hydrogen support" +msgstr "" + +#: ../../../CHANGELOG.md:2044 +msgid "" +"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " +"now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a " +"new lightweight Matrix client with legacy and mobile browser support." +msgstr "" + +#: ../../../CHANGELOG.md:2046 +msgid "" +"By default, we still install Element Web, as Hydrogen is still not fully-" +"featured. Still, people who'd like to try Hydrogen out can now install it" +" via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2048 +msgid "" +"Additional details are available in [Setting up Hydrogen](docs" +"/configuring-playbook-client-hydrogen.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2051 +msgid "2021-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2053 +msgid "Heisenbridge support" +msgstr "" + +#: ../../../CHANGELOG.md:2055 +msgid "" +"Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now " +"supports bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet " +"another bridge (besides matrix-appservice-irc), called " +"[Heisenbridge](https://github.com/hifi/heisenbridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2057 +msgid "" +"Additional details are available in [Setting up Heisenbridge bouncer-" +"style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2060 +msgid "2021-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:2062 +msgid "Disabling TLSv1 and TLSv1.1 for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:2064 +msgid "" +"To improve security, we've [removed TLSv1 and TLSv1.1 " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/999) from our default " +"[Coturn](https://github.com/coturn/coturn) configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2066 +msgid "" +"If you need to support old clients, you can re-enable both (or whichever " +"one you need) with the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:2074 +msgid "2021-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2076 +msgid "Automated local Postgres backup support" +msgstr "" + +#: ../../../CHANGELOG.md:2078 +msgid "" +"Thanks to [foxcris](https://github.com/foxcris), the playbook can now " +"make automated local Postgres backups on a fixed schedule using [docker-" +"postgres-backup-local](https://github.com/prodrigestivill/docker-" +"postgres-backup-local)." +msgstr "" + +#: ../../../CHANGELOG.md:2080 +msgid "" +"Additional details are available in [Setting up postgres backup](docs" +"/configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2083 +msgid "2021-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2085 +msgid "Mjolnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:2087 +msgid "" +"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " +"can now install and configure the [Mjolnir](https://github.com/matrix-" +"org/mjolnir) moderation tool (bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2089 +msgid "" +"Additional details are available in [Setting up Mjolnir](docs" +"/configuring-playbook-bot-mjolnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2092 +msgid "2021-03-20" +msgstr "" + +#: ../../../CHANGELOG.md:2094 +msgid "Sygnal push gateway support" +msgstr "" + +#: ../../../CHANGELOG.md:2096 +msgid "" +"The playbook can now install the [Sygnal](https://github.com/matrix-" +"org/sygnal) push gateway for you." +msgstr "" + +#: ../../../CHANGELOG.md:2098 +msgid "" +"This is only useful to people who develop/build their own Matrix client " +"applications." +msgstr "" + +#: ../../../CHANGELOG.md:2100 +msgid "" +"Additional details are available in our [Setting up the Sygnal push " +"gateway](docs/configuring-playbook-sygnal.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2103 +msgid "2021-03-16" +msgstr "" + +#: ../../../CHANGELOG.md:2105 +msgid "Go-NEB support" +msgstr "" + +#: ../../../CHANGELOG.md:2107 +msgid "" +"Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install" +" and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." +msgstr "" + +#: ../../../CHANGELOG.md:2109 +msgid "" +"Additional details are available in [Setting up Go-NEB](docs/configuring-" +"playbook-bot-go-neb.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2112 +msgid "2021-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:2114 +msgid "GroupMe bridging support via mx-puppet-groupme" +msgstr "" + +#: ../../../CHANGELOG.md:2116 +msgid "" +"Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can " +"now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-" +"puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." +msgstr "" + +#: ../../../CHANGELOG.md:2118 +msgid "" +"This brings the total number of bridges supported by the playbook up to " +"18. See all supported bridges [here](docs/configuring-playbook.md" +"#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2120 +msgid "" +"To get started, follow our [Setting up MX Puppet GroupMe](docs" +"/configuring-playbook-bridge-mx-puppet-groupme.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2122 +msgid "Mautrix Instagram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2124 +msgid "" +"The playbook now supports bridging with " +"[Instagram](https://www.instagram.com/) by installing the [mautrix-" +"instagram](https://github.com/tulir/mautrix-instagram) bridge. This " +"playbook functionality is available thanks to " +"[@MarcProe](https://github.com/MarcProe)." +msgstr "" + +#: ../../../CHANGELOG.md:2126 +msgid "" +"Additional details are available in [Setting up Mautrix Instagram " +"bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2128 +msgid "Synapse workers support" +msgstr "" + +#: ../../../CHANGELOG.md:2130 +msgid "" +"After [lots and lots of work](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/456) (done over many months by [Marcel " +"Partap](https://github.com/eMPee584), [Max " +"Klenk](https://github.com/maxklenk), a few others from the [Technical " +"University of Dresden, Germany](https://tu-dresden.de/) and various other" +" contributors), support for Synapse workers has finally landed." +msgstr "" + +#: ../../../CHANGELOG.md:2132 +msgid "" +"Having support for workers makes the playbook suitable for larger " +"homeserver deployments." +msgstr "" + +#: ../../../CHANGELOG.md:2134 +msgid "" +"Our setup is not yet perfect (we don't support all types of workers; " +"scaling some of them (like `pusher`, `federation_sender`) beyond a single" +" instance is not yet supported). Still, it's a great start and can " +"already power homeservers with thousands of users, like the [Matrix " +"deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed" +" in [Matrix Live S06E09 - TU Dresden on their Matrix " +"deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." +msgstr "" + +#: ../../../CHANGELOG.md:2136 +msgid "" +"By default, workers are disabled and Synapse runs as a single process " +"(homeservers don't necessarily need the complexity and increased memory " +"requirements of running a worker-based setup)." +msgstr "" + +#: ../../../CHANGELOG.md:2138 +msgid "" +"To enable Synapse workers, follow our [Load balancing with workers](docs" +"/configuring-playbook-synapse.md#load-balancing-with-workers) " +"documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2141 +msgid "2021-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:2143 +msgid "" +"(Potential Breaking Change) Monitoring/metrics support using Prometheus " +"and Grafana" +msgstr "" + +#: ../../../CHANGELOG.md:2145 +msgid "" +"Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now " +"install a bunch of tools for monitoring your Matrix server: the " +"[Prometheus](https://prometheus.io) time-series database server, the " +"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" +"exporter/) host metrics exporter, and the [Grafana](https://grafana.com/)" +" web UI." +msgstr "" + +#: ../../../CHANGELOG.md:2147 +msgid "" +"To get get these installed, follow our [Enabling metrics and graphs " +"(Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-" +"prometheus-grafana.md) docs page." +msgstr "" + +#: ../../../CHANGELOG.md:2149 +msgid "" +"This update comes with a **potential breaking change** for people who " +"were already exposing Synapse metrics (for consumption via another " +"Prometheus installation). From now on, `matrix_synapse_metrics_enabled: " +"true` no longer exposes metrics publicly via matrix-nginx-proxy (at " +"`https://matrix.example.com/_synapse/metrics`). To do so, you'd need to " +"explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." +msgstr "" + +#: ../../../CHANGELOG.md:2152 +msgid "2021-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:2154 +msgid "Etherpad support" +msgstr "" + +#: ../../../CHANGELOG.md:2156 +msgid "" +"Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can " +"now install the [Etherpad](https://etherpad.org) realtime collaborative " +"text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video " +"call or integrated as a widget into Matrix chat rooms via the " +"[Dimension](https://dimension.t2bot.io) integration manager." +msgstr "" + +#: ../../../CHANGELOG.md:2158 +msgid "" +"To get it installed, follow [our Etherpad docs page](docs/configuring-" +"playbook-etherpad.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2161 +msgid "2021-01-22" +msgstr "" + +#: ../../../CHANGELOG.md:2163 +msgid "(Breaking Change) Postgres changes that require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:2165 +msgid "" +"We've made a lot of changes to our Postgres setup and some manual action " +"is required (described below). Sorry about the hassle." +msgstr "" + +#: ../../../CHANGELOG.md:2167 +msgid "" +"**TLDR**: people running an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md) don't need to change anything for now. " +"Everyone else (the common/default case) is affected and manual " +"intervention is required." +msgstr "" + +#: ../../../CHANGELOG.md:2169 +msgid "Why?" +msgstr "" + +#: ../../../CHANGELOG.md:2171 +msgid "" +"we had a default Postgres password (`matrix_postgres_connection_password:" +" synapse-password`), which we think is **not ideal for security " +"anymore**. We now ask you to generate/provide a strong password yourself." +" Postgres is normally not exposed outside the container network, making " +"it relatively secure, but still:" +msgstr "" + +#: ../../../CHANGELOG.md:2172 +msgid "" +"by tweaking the configuration, you may end up intentionally or " +"unintentionally exposing your Postgres server to the local network (or " +"even publicly), while still using the default default credentials " +"(`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2173 +msgid "" +"we can't be sure we trust all these services (bridges, etc). Some of them" +" may try to talk to or attack `matrix-postgres` using the default " +"credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2174 +msgid "" +"you may have other containers running on the same Docker network, which " +"may try to talk to or attack `matrix-postgres` using the default " +"credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2175 +msgid "" +"our Postgres usage **was overly-focused on Synapse** (default username of" +" `synapse` and default/main database of `homeserver`). Additional " +"homeserver options are likely coming in the future " +"([Dendrite](https://matrix.org/docs/projects/server/dendrite), " +"[Conduit](https://matrix.org/docs/projects/server/conduit), [The " +"Construct](https://matrix.org/docs/projects/server/construct)), so being " +"too focused on `matrix-synapse` is not great. From now on, Synapse is " +"just another component of this playbook, which happens to have an " +"*additional database* (called `synapse`) on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2176 +msgid "" +"we try to reorganize things a bit, to make the playbook even friendlier " +"to people running an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md). Work on this will proceed in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2178 +msgid "" +"So, this is some **effort to improve security** and to **prepare for a " +"brighter future of having more homeserver options** than just Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:2180 +msgid "What has really changed?" +msgstr "" + +#: ../../../CHANGELOG.md:2182 +msgid "" +"the default superuser Postgres username is now `matrix` (used to be " +"`synapse`)" +msgstr "" + +#: ../../../CHANGELOG.md:2183 +msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" +msgstr "" + +#: ../../../CHANGELOG.md:2184 +msgid "" +"Synapse's database is now `synapse` (used to be `homeserver`). This is " +"now just another \"additional database\" that the playbook manages for " +"you" +msgstr "" + +#: ../../../CHANGELOG.md:2185 +msgid "" +"Synapse's user called `synapse` is just a regular user that can only use " +"the `synapse` database (not a superuser anymore)" +msgstr "" + +#: ../../../CHANGELOG.md:2187 +msgid "What do I do if I'm using the integrated Postgres server (default)?" +msgstr "" + +#: ../../../CHANGELOG.md:2189 +msgid "" +"By default, the playbook runs an integrated Postgres server for you in a " +"container (`matrix-postgres`). Unless you've explicitly configured an " +"[external Postgres server](docs/configuring-playbook-external-" +"postgres.md), these steps are meant for you." +msgstr "" + +#: ../../../CHANGELOG.md:2191 +msgid "" +"To migrate to the new setup, expect a few minutes of downtime, while you " +"follow these steps:" +msgstr "" + +#: ../../../CHANGELOG.md:2193 +msgid "" +"We believe the steps below are safe and you won't encounter any data " +"loss, but consider [making a Postgres backup](docs/maintenance-" +"postgres.md#backing-up-postgresql) anyway. If you've never backed up " +"Postgres, now would be a good time to try it." +msgstr "" + +#: ../../../CHANGELOG.md:2195 +msgid "" +"Generate a strong password to be used for your superuser Postgres user " +"(called `matrix`). You can use `pwgen -s 64 1` to generate it, or some " +"other tool. The **maximum length** for a Postgres password is 100 bytes " +"(characters). Don't go crazy!" +msgstr "" + +#: ../../../CHANGELOG.md:2197 +msgid "" +"Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` " +"file, adding a line like this:" +msgstr "" + +#: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214 +msgid "" +".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the " +"password you generated during step #2." +msgstr "" + +#: ../../../CHANGELOG.md:2204 +msgid "" +"Stop all services: `ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`" +msgstr "" + +#: ../../../CHANGELOG.md:2205 +msgid "Log in to the server via SSH. The next commands will be performed there." +msgstr "" + +#: ../../../CHANGELOG.md:2206 +msgid "Start the Postgres database server: `systemctl start matrix-postgres`" +msgstr "" + +#: ../../../CHANGELOG.md:2207 +msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:2208 +msgid "" +"Execute the following query, while making sure to **change the password " +"inside** (**don't forget the ending `;`**):" +msgstr "" + +#: ../../../CHANGELOG.md:2216 +msgid "" +"Execute the following queries as you see them (no modifications " +"necessary, so you can just **paste them all at once**):" +msgstr "" + +#: ../../../CHANGELOG.md:2234 +msgid "You may need to press *Enter* after pasting the lines above." +msgstr "" + +#: ../../../CHANGELOG.md:2236 +msgid "" +"Re-run the playbook normally: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2238 +msgid "What do I do if I'm using an external Postgres server?" +msgstr "" + +#: ../../../CHANGELOG.md:2240 +msgid "" +"If you've explicitly configured an [external Postgres server](docs" +"/configuring-playbook-external-postgres.md), there are **no changes** " +"that you need to do at this time." +msgstr "" + +#: ../../../CHANGELOG.md:2242 +msgid "" +"The fact that we've renamed Synapse's database from `homeserver` to " +"`synapse` (in our defaults) should not affect you, as you're already " +"explicitly defining `matrix_synapse_database_database` (if you've " +"followed our guide, that is). If you're not explicitly defining this " +"variable, you may wish to do so (`matrix_synapse_database_database: " +"homeserver`), to avoid the new `synapse` default and keep things as they " +"were." +msgstr "" + +#: ../../../CHANGELOG.md:2245 +msgid "2021-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:2247 +msgid "" +"(Breaking Change) The mautrix-facebook bridge now requires a Postgres " +"database" +msgstr "" + +#: ../../../CHANGELOG.md:2249 +msgid "" +"**Update from 2021-11-15**: SQLite support has been re-added to the " +"mautrix-facebook bridge in " +"[v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You " +"can ignore this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2251 +msgid "" +"A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-" +"facebook) bridge has been released. It's a full rewrite of its backend " +"and the bridge now requires Postgres. New versions of the bridge can no " +"longer run on SQLite." +msgstr "" + +#: ../../../CHANGELOG.md:2253 +msgid "" +"**TLDR**: if you're NOT using an [external Postgres server](docs" +"/configuring-playbook-external-postgres.md) and have NOT forcefully kept " +"the bridge on SQLite during [The big move to all-on-Postgres (potentially" +" dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you" +" will be automatically upgraded without manual intervention. All you need" +" to do is send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2255 +msgid "Whether this change requires your intervention depends mostly on:" +msgstr "" + +#: ../../../CHANGELOG.md:2256 +msgid "" +"whether you're using an [external Postgres server](docs/configuring-" +"playbook-external-postgres.md). If yes, then [you need to do something" +"](#upgrade-path-for-people-running-an-external-postgres-server)." +msgstr "" + +#: ../../../CHANGELOG.md:2257 +msgid "" +"or whether you've force-changed the bridge's database engine to SQLite " +"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " +"some time in the past (likely during [The big move to all-on-Postgres " +"(potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-" +"dangerous))." +msgstr "" + +#: ../../../CHANGELOG.md:2259 +msgid "" +"As already mentioned above, you most likely don't need to do anything. If" +" you rerun the playbook and don't get an error, you've been automatically" +" upgraded. Just send a `login` message to the Facebook bridge bot again. " +"Otherwise, read below for a solution." +msgstr "" + +#: ../../../CHANGELOG.md:2261 +msgid "" +"Upgrade path for people NOT running an external Postgres server (default " +"for the playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:2263 +msgid "" +"If you're **not running an external Postgres server**, then this bridge " +"either already works on Postgres for you, or you've intentionally kept it" +" back on SQLite with custom configuration " +"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " +"." +msgstr "" + +#: ../../../CHANGELOG.md:2265 +msgid "" +"Simply remove that custom configuration from your `vars.yml` file (if " +"it's there) and re-run the playbook. It should upgrade you automatically." +" You'll need to send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2267 +msgid "" +"Alternatively, [you can stay on SQLite for a little longer](#staying-on-" +"sqlite-for-a-little-longer-temporary-solution)." +msgstr "" + +#: ../../../CHANGELOG.md:2269 +msgid "Upgrade path for people running an external Postgres server" +msgstr "" + +#: ../../../CHANGELOG.md:2271 +msgid "" +"For people using the internal Postgres server (the default for the " +"playbook):" +msgstr "" + +#: ../../../CHANGELOG.md:2272 +msgid "" +"we automatically create an additional `matrix_mautrix_facebook` Postgres " +"database and credentials to access it" +msgstr "" + +#: ../../../CHANGELOG.md:2273 +msgid "" +"we automatically adjust the bridge's `matrix_mautrix_facebook_database_*`" +" variables to point the bridge to that Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2274 +msgid "" +"we use [pgloader](https://pgloader.io/) to automatically import the " +"existing SQLite data for the bridge into the `matrix_mautrix_facebook` " +"Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2276 +msgid "" +"If you are using an [external Postgres server](docs/configuring-playbook-" +"external-postgres.md), unfortunately we currently can't do any of that " +"for you." +msgstr "" + +#: ../../../CHANGELOG.md:2278 +msgid "You have 3 ways to proceed:" +msgstr "" + +#: ../../../CHANGELOG.md:2280 +msgid "contribute to the playbook to make this possible (difficult)" +msgstr "" + +#: ../../../CHANGELOG.md:2281 +msgid "or, do the migration \"steps\" manually:" +msgstr "" + +#: ../../../CHANGELOG.md:2282 +msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2283 +msgid "create a new `matrix_mautrix_facebook` Postgres database for it" +msgstr "" + +#: ../../../CHANGELOG.md:2284 +msgid "" +"run [pgloader](https://pgloader.io/) manually (we import this bridge's " +"data using default settings and it works well)" +msgstr "" + +#: ../../../CHANGELOG.md:2285 +msgid "" +"define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` " +"file (credentials, etc.) - you can find their defaults in `roles/custom" +"/matrix-mautrix-facebook/defaults/main.yml`" +msgstr "" + +#: ../../../CHANGELOG.md:2286 +msgid "" +"switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: " +"'postgres'` in your `vars.yml` file)" +msgstr "" + +#: ../../../CHANGELOG.md:2287 +msgid "" +"re-run the playbook (`--tags=setup-all,start`) and ensure the bridge " +"works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu " +"matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2288 +msgid "send a `login` message to the Facebook bridge bot again" +msgstr "" + +#: ../../../CHANGELOG.md:2289 +msgid "" +"or, [stay on SQLite for a little longer (temporary solution)](#staying-" +"on-sqlite-for-a-little-longer-temporary-solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2291 +msgid "Staying on SQLite for a little longer (temporary solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2293 +msgid "" +"To keep using this bridge with SQLite for a little longer (**not " +"recommended**), use the following configuration in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:2303 +msgid "" +"If you do this, keep in mind that **you can't run this forever**. This " +"SQLite-supporting bridge version is not getting any updates and will " +"break sooner or later. The playbook will also drop support for SQLite at " +"some point in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2306 +msgid "2021-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:2308 +msgid "matrix-corporal goes 2.0" +msgstr "" + +#: ../../../CHANGELOG.md:2310 +msgid "" +"[matrix-corporal v2 has been released](https://github.com/devture/matrix-" +"corporal/releases/tag/2.0.0) and the playbook also supports it now." +msgstr "" + +#: ../../../CHANGELOG.md:2312 +msgid "No manual intervention is required in the common case." +msgstr "" + +#: ../../../CHANGELOG.md:2314 +msgid "" +"The new [matrix-corporal](https://github.com/devture/matrix-corporal) " +"version is also the first one to support Interactive Authentication. If " +"you wish to enable that (hint: you should), you'll need to set up the " +"[REST auth password provider](docs/configuring-playbook-rest-auth.md). " +"There's more information in [our matrix-corporal docs](docs/configuring-" +"playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2317 +msgid "2021-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2319 +msgid "Moving from cronjobs to systemd timers" +msgstr "" + +#: ../../../CHANGELOG.md:2321 +msgid "" +"We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-" +"nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to " +"systemd timers." +msgstr "" + +#: ../../../CHANGELOG.md:2323 +msgid "" +"The largest benefit of this is that we no longer require you to install a" +" cron daemon, thus simplifying our install procedure." +msgstr "" + +#: ../../../CHANGELOG.md:2325 +msgid "" +"The playbook will migrate you from cronjobs to systemd timers " +"automatically. This is just a heads up." +msgstr "" + +#: ../../../CHANGELOG.md:2328 +msgid "2021-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:2330 +msgid "(Breaking Change) New SSL configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2332 +msgid "" +"SSL configuration (protocols, ciphers) can now be more easily controlled " +"thanks to us making use of configuration presets." +msgstr "" + +#: ../../../CHANGELOG.md:2334 +msgid "" +"We define a few presets (old, intermediate, modern), following the " +"[Mozilla SSL Configuration Generator](https://ssl-" +"config.mozilla.org/#server=nginx)." +msgstr "" + +#: ../../../CHANGELOG.md:2336 +msgid "" +"A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is " +"used (defaults to `\"intermediate\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2338 +msgid "" +"Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to " +"`off` (used to default to `on`). It also add some more ciphers to the " +"list, giving better performance on mobile devices, and removes some weak " +"ciphers. More information in the [documentation](docs/configuring-" +"playbook-nginx.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2340 +msgid "To revert to the old behaviour, set the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:2347 +msgid "" +"Just like before, you can still use your own custom protocols by " +"specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides" +" the values coming from the preset." +msgstr "" + +#: ../../../CHANGELOG.md:2350 +msgid "2021-01-03" +msgstr "" + +#: ../../../CHANGELOG.md:2352 +msgid "Signal bridging support via mautrix-signal" +msgstr "" + +#: ../../../CHANGELOG.md:2354 +msgid "" +"Thanks to [laszabine](https://github.com/laszabine)'s efforts, the " +"playbook now supports bridging to [Signal](https://www.signal.org/) via " +"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See" +" our [Setting up Mautrix Signal bridging](docs/configuring-playbook-" +"bridge-mautrix-signal.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2356 +msgid "" +"If you had installed the mautrix-signal bridge while its Pull Request was" +" still work-in-progress, you can migrate your data to the new and final " +"setup by referring to [this comment](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." +msgstr "" + +#: ../../../CHANGELOG.md:2359 +msgid "2020-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:2361 +msgid "The big move to all-on-Postgres (potentially dangerous)" +msgstr "" + +#: ../../../CHANGELOG.md:2363 +msgid "" +"**TLDR**: all your bridges (and other services) will likely be auto-" +"migrated from SQLite/nedb to Postgres, hopefully without trouble. You can" +" opt-out (see how below), if too worried about breakage." +msgstr "" + +#: ../../../CHANGELOG.md:2365 +msgid "" +"Until now, we've only used Postgres as a database for Synapse. All other " +"services (bridges, bots, etc.) were kept simple and used a file-based " +"database (SQLite or nedb)." +msgstr "" + +#: ../../../CHANGELOG.md:2367 +msgid "" +"Since [this huge pull request](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/740), **all of our services now use Postgres " +"by default**. Thanks to [Johanna Dorothea " +"Reichmann](https://github.com/jdreichmann) for starting the work on it " +"and for providing great input!" +msgstr "" + +#: ../../../CHANGELOG.md:2369 +msgid "Moving all services to Postgres brings a few **benefits** to us:" +msgstr "" + +#: ../../../CHANGELOG.md:2371 +msgid "**improved performance**" +msgstr "" + +#: ../../../CHANGELOG.md:2372 +msgid "" +"**improved compatibility**. Most bridges are deprecating SQLite/nedb " +"support or offer less features when not on Postgres." +msgstr "" + +#: ../../../CHANGELOG.md:2373 +msgid "" +"**easier backups**. It's still some effort to take a proper backup " +"(Postgres dump + various files, keys), but a Postgres dump now takes you " +"much further." +msgstr "" + +#: ../../../CHANGELOG.md:2374 +msgid "" +"we're now **more prepared to introduce other services** that need a " +"Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), " +"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge " +"(existing [pull request](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/686)), etc." +msgstr "" + +#: ../../../CHANGELOG.md:2376 +msgid "Key takeway" +msgstr "" + +#: ../../../CHANGELOG.md:2378 +msgid "" +"existing installations that use an [external " +"Postgres](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/master/docs/configuring-playbook-external-postgres.md) server" +" should be unaffected (they remain on SQLite/nedb for all services, " +"except Synapse)" +msgstr "" + +#: ../../../CHANGELOG.md:2380 +msgid "" +"for existing installations which use our integrated Postgres database " +"server (`matrix-postgres`, which is the default), **we automatically " +"migrate data** from SQLite/nedb to Postgres and **archive the database " +"files** (`something.db` -> `something.db.backup`), so you can restore " +"them if you need to go back (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:2382 +msgid "Opting-out of the Postgres migration" +msgstr "" + +#: ../../../CHANGELOG.md:2384 +msgid "" +"This is a **very large and somewhat untested change** (potentially " +"dangerous), so **if you're not feeling confident/experimental, opt-out** " +"of it for now. Still, it's the new default and what we (and various " +"bridges) will focus on going forward, so don't stick to old ways for too " +"long." +msgstr "" + +#: ../../../CHANGELOG.md:2386 +msgid "" +"You can remain on SQLite/nedb (at least for now) by adding a variable " +"like this to your `vars.yml` file for each service you use: " +"`matrix_COMPONENT_database_engine: sqlite` (e.g. " +"`matrix_mautrix_facebook_database_engine: sqlite`)." +msgstr "" + +#: ../../../CHANGELOG.md:2388 +msgid "" +"Some services (like `appservice-irc` and `appservice-slack`) don't use " +"SQLite, so use `nedb`, instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2390 +msgid "Going back to SQLite/nedb if things went wrong" +msgstr "" + +#: ../../../CHANGELOG.md:2392 +msgid "" +"If you went with the Postgres migration and it went badly for you (some " +"bridge not working as expected or not working at all), do this:" +msgstr "" + +#: ../../../CHANGELOG.md:2394 +msgid "" +"stop all services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:2395 +msgid "" +"SSH into the server and rename the old database files " +"(`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-" +"facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data" +"/mautrix-facebook.db`" +msgstr "" + +#: ../../../CHANGELOG.md:2396 +msgid "" +"switch the affected service back to SQLite (e.g. " +"`matrix_mautrix_facebook_database_engine: sqlite`). Some services (like " +"`appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`," +" instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2397 +msgid "" +"re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-all,start`)" +msgstr "" + +#: ../../../CHANGELOG.md:2398 +msgid "[get in touch](README.md#support) with us" +msgstr "" + +#: ../../../CHANGELOG.md:2400 +msgid "2020-12-11" +msgstr "" + +#: ../../../CHANGELOG.md:2402 +msgid "synapse-janitor support removed" +msgstr "" + +#: ../../../CHANGELOG.md:2404 +msgid "" +"We've removed support for the unmaintained [synapse-" +"janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's " +"been past reports of it corrupting the Synapse database. Since there " +"hasn't been any new development on it and it doesn't seem too useful " +"nowadays, there's no point in including it in the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2406 +msgid "" +"If you need to clean up or compact your database, consider using the " +"Synapse Admin APIs directly. See our [Synapse maintenance](docs" +"/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-" +"postgres.md) documentation pages for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2408 +msgid "Docker 20.10 is here" +msgstr "" + +#: ../../../CHANGELOG.md:2410 +msgid "" +"(No need to do anything special in relation to this. Just something to " +"keep in mind)" +msgstr "" + +#: ../../../CHANGELOG.md:2412 +msgid "" +"Docker 20.10 got released recently and your server will likely get it the" +" next time you update." +msgstr "" + +#: ../../../CHANGELOG.md:2414 +msgid "" +"This is the first major Docker update in a long time and it packs a lot " +"of changes. Some of them introduced some breakage for us initially (see " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should " +"be all good now." +msgstr "" + +#: ../../../CHANGELOG.md:2417 +msgid "2020-12-08" +msgstr "" + +#: ../../../CHANGELOG.md:2419 +msgid "" +"openid APIs exposed by default on the federation port when federation " +"disabled" +msgstr "" + +#: ../../../CHANGELOG.md:2421 +msgid "" +"We've changed some defaults. People running with our default " +"configuration (federation enabled), are not affected at all." +msgstr "" + +#: ../../../CHANGELOG.md:2423 +msgid "" +"If you are running an unfederated server " +"(`matrix_synapse_federation_enabled: false`), this may be of interest to " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:2425 +msgid "" +"When federation is disabled, but ma1sd or Dimension are enabled, we'll " +"now expose the `openid` APIs on the federation port. These APIs are " +"necessary for some ma1sd features to work. If you'd like to prevent this," +" you can: `matrix_synapse_federation_port_openid_resource_required: " +"false`." +msgstr "" + +#: ../../../CHANGELOG.md:2428 +msgid "2020-11-27" +msgstr "" + +#: ../../../CHANGELOG.md:2430 +msgid "Recent Jitsi updates may require configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:2432 +msgid "" +"We've recently [updated from Jitsi build 4857 to build " +"5142](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/719), which brings a lot of configuration changes." +msgstr "" + +#: ../../../CHANGELOG.md:2434 +msgid "**If you use our default Jitsi settings, you won't have to do anything.**" +msgstr "" + +#: ../../../CHANGELOG.md:2436 +msgid "" +"People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md" +"#optional-fine-tune-jitsi) may find that some options got renamed now, " +"others are gone and yet others still need to be defined in another way." +msgstr "" + +#: ../../../CHANGELOG.md:2438 +msgid "" +"The next time you run the playbook [installation](docs/installing.md) " +"command, our validation logic will tell you if you're using some " +"variables like that and will recommend a migration path for each one." +msgstr "" + +#: ../../../CHANGELOG.md:2440 +msgid "" +"Additionally, we've recently disabled transcriptions " +"(`jitsi_enable_transcriptions: false`) and recording " +"(`jitsi_enable_recording: false`) by default. These features did not work" +" anyway, because we don't install the required dependencies for them " +"(Jigasi and Jibri, respectively). If you've been somehow pointing your " +"Jitsi installation to some manually installed Jigasi/Jibri service, you " +"may need to toggle these flags back to enabled to have transcriptions and" +" recordings working." +msgstr "" + +#: ../../../CHANGELOG.md:2443 +msgid "2020-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:2445 ../../../CHANGELOG.md:2453 +msgid "Breaking change matrix-sms-bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2447 +msgid "" +"Because of many problems using gammu as SMS provider, matrix-sms-bridge " +"now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by " +"default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-" +"sms.md] which new vars you need to add." +msgstr "" + +#: ../../../CHANGELOG.md:2449 +msgid "" +"If you are using this playbook to deploy matrix-sms-bridge and still " +"really want to use gammu as SMS provider, we could possibly add support " +"for both android-sms-gateway-server and gammu." +msgstr "" + +#: ../../../CHANGELOG.md:2451 +msgid "2020-11-13" +msgstr "" + +#: ../../../CHANGELOG.md:2455 +msgid "" +"The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-" +"sms-bridge) changed its database from neo4j to h2. You need to sync the " +"bridge at the first start. Note that this only will sync rooms where the " +"@smsbot:yourServer is member. For rooms without @smsbot:yourServer you " +"need to kick and invite the telephone number **or** invite " +"@smsbot:yourServer." +msgstr "" + +#: ../../../CHANGELOG.md:2457 +msgid "" +"Add the following to your `vars.yml` file: " +"`matrix_sms_bridge_container_extra_arguments=['--env " +"SPRING_PROFILES_ACTIVE=initialsync']`" +msgstr "" + +#: ../../../CHANGELOG.md:2458 +msgid "" +"Login to your host shell and remove old systemd file from your host: `rm " +"/etc/systemd/system/matrix-sms-bridge-database.service`" +msgstr "" + +#: ../../../CHANGELOG.md:2459 +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-" +"sms-bridge,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2460 +msgid "" +"Login to your host shell and check the logs with `journalctl -u matrix-" +"sms-bridge` until the sync finished." +msgstr "" + +#: ../../../CHANGELOG.md:2461 +msgid "Remove the var from the first step." +msgstr "" + +#: ../../../CHANGELOG.md:2462 +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-" +"all,start`." +msgstr "" + +#: ../../../CHANGELOG.md:2464 +msgid "2020-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2466 +msgid "Dynamic DNS support" +msgstr "" + +#: ../../../CHANGELOG.md:2468 +msgid "" +"Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook " +"can now manage Dynamic DNS for you using " +"[ddclient](https://ddclient.net/)." +msgstr "" + +#: ../../../CHANGELOG.md:2470 +msgid "" +"To learn more, follow our [Dynamic DNS docs page](docs/configuring-" +"playbook-dynamic-dns.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2473 +msgid "2020-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:2475 +msgid "" +"(Compatibility Break) https://matrix.example.com/ now redirects to " +"https://element.example.com/" +msgstr "" + +#: ../../../CHANGELOG.md:2477 +msgid "" +"Until now, we used to serve a static page coming from Synapse at " +"`https://matrix.example.com/`. This page was not very useful to anyone." +msgstr "" + +#: ../../../CHANGELOG.md:2479 +msgid "" +"Since `matrix.example.com` may be accessed by regular users in certain " +"conditions, it's probably better to redirect them to a better place (e.g." +" to [Element Web](docs/configuring-playbook-client-element-web.md))." +msgstr "" + +#: ../../../CHANGELOG.md:2481 +msgid "" +"If Element Web is installed (`matrix_client_element_enabled: true`, which" +" it is by default), we now redirect people to it, instead of showing them" +" a Synapse static page." +msgstr "" + +#: ../../../CHANGELOG.md:2483 +msgid "" +"If you'd like to control where the redirect goes, use the " +"`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` " +"variable. To restore the old behavior of not redirecting anywhere and " +"serving the Synapse static page, set it to an empty value " +"(`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: " +"\"\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2486 +msgid "2020-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:2488 +msgid "" +"(Compatibility Break) /_synapse/admin is no longer publicly exposed by " +"default" +msgstr "" + +#: ../../../CHANGELOG.md:2490 +msgid "" +"We used to expose the Synapse Admin APIs publicly (at " +"`https://matrix.example.com/_synapse/admin`). These APIs require " +"authentication with a valid access token, so it's not that big a deal to " +"expose them." +msgstr "" + +#: ../../../CHANGELOG.md:2492 +msgid "" +"However, following [official Synapse's reverse-proxying " +"recommendations](https://github.com/element-" +"hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-" +"endpoints), we're no longer exposing `/_synapse/admin` by default." +msgstr "" + +#: ../../../CHANGELOG.md:2494 +msgid "" +"If you'd like to restore restore the old behavior and expose " +"`/_synapse/admin` publicly, you can use the following configuration (in " +"your `vars.yml`):" +msgstr "" + +#: ../../../CHANGELOG.md:2501 +msgid "2020-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:2503 +msgid "Minimum Ansible version raised to v2.7.0" +msgstr "" + +#: ../../../CHANGELOG.md:2505 +msgid "" +"We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 " +"and higher, but issues like [#662](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/662) demonstrate that we need at least " +"v2.7.0." +msgstr "" + +#: ../../../CHANGELOG.md:2507 +msgid "" +"If you've been using the playbook without getting any errors until now, " +"you're probably on a version higher than that already (or you're not " +"using the `matrix-ma1sd` and `matrix-client-element` roles)." +msgstr "" + +#: ../../../CHANGELOG.md:2509 +msgid "" +"Our [Ansible docs page](docs/ansible.md) contains information on how to " +"run a more up-to-date version of Ansible." +msgstr "" + +#: ../../../CHANGELOG.md:2512 +msgid "2020-10-01" +msgstr "" + +#: ../../../CHANGELOG.md:2514 +msgid "Postgres 13 support" +msgstr "" + +#: ../../../CHANGELOG.md:2516 +msgid "" +"The playbook now installs [Postgres " +"13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) " +"by default." +msgstr "" + +#: ../../../CHANGELOG.md:2518 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by " +"following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md" +"#upgrading-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2520 +msgid "2020-09-01" +msgstr "" + +#: ../../../CHANGELOG.md:2522 +msgid "matrix-registration support" +msgstr "" + +#: ../../../CHANGELOG.md:2524 +msgid "" +"The playbook can now help you set up [matrix-" +"registration](https://github.com/ZerataX/matrix-registration) - an " +"application that lets you keep your Matrix server's registration private," +" but still allow certain users (those having a unique registration link) " +"to register by themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2526 +msgid "" +"See our [Setting up matrix-registration](docs/configuring-playbook-" +"matrix-registration.md) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2529 +msgid "2020-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2531 +msgid "rust-synapse-compress-state support" +msgstr "" + +#: ../../../CHANGELOG.md:2533 +msgid "" +"The playbook can now help you use [rust-synapse-compress-" +"state](https://github.com/matrix-org/rust-synapse-compress-state) to " +"compress the state groups in your Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2535 +msgid "" +"See our [Compressing state with rust-synapse-compress-state](docs" +"/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-" +"state) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2538 +msgid "2020-07-22" +msgstr "" + +#: ../../../CHANGELOG.md:2540 +msgid "Synapse Admin support" +msgstr "" + +#: ../../../CHANGELOG.md:2542 +msgid "" +"The playbook can now help you set up [synapse-admin](https://github.com" +"/Awesome-Technologies/synapse-admin)." +msgstr "" + +#: ../../../CHANGELOG.md:2544 +msgid "" +"See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-" +"admin.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2547 +msgid "2020-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:2549 +msgid "matrix-reminder-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:2551 +msgid "" +"The playbook can now help you set up [matrix-reminder-" +"bot](https://github.com/anoadragon453/matrix-reminder-bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2553 +msgid "" +"See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-" +"matrix-reminder-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2556 +msgid "2020-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:2558 +msgid "(Compatibility Break) Riot is now Element" +msgstr "" + +#: ../../../CHANGELOG.md:2560 +msgid "" +"As per the official announcement, [Riot has been rebraned to " +"Element](https://element.io/blog/welcome-to-element/)." +msgstr "" + +#: ../../../CHANGELOG.md:2562 +msgid "" +"The playbook follows suit. Existing installations have a few options for " +"how to handle this." +msgstr "" + +#: ../../../CHANGELOG.md:2564 +msgid "" +"See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md" +"#migrating-to-element) documentation page for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2567 +msgid "2020-07-03" +msgstr "" + +#: ../../../CHANGELOG.md:2569 +msgid "Steam bridging support via mx-puppet-steam" +msgstr "" + +#: ../../../CHANGELOG.md:2571 +msgid "" +"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " +"playbook now supports bridging to [Steam](https://steamapp.com/) via the " +"[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge." +" See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-" +"bridge-mx-puppet-steam.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2574 +msgid "2020-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:2576 +msgid "Discord bridging support via mx-puppet-discord" +msgstr "" + +#: ../../../CHANGELOG.md:2578 +msgid "" +"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " +"playbook now supports bridging to [Discord](https://discordapp.com/) via " +"the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) " +"bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-" +"playbook-bridge-mx-puppet-discord.md) documentation page for getting " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2580 +msgid "" +"**Note**: this is a new Discord bridge. The playbook still retains " +"Discord bridging via [matrix-appservice-discord](docs/configuring-" +"playbook-bridge-appservice-discord.md). You're free too use the bridge " +"that serves you better, or even both (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:2583 +msgid "2020-06-30" +msgstr "" + +#: ../../../CHANGELOG.md:2585 +msgid "Instagram and Twitter bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2587 +msgid "" +"Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s " +"efforts, the playbook now supports bridging to " +"[Instagram](https://www.instagram.com/) via the [mx-puppet-" +"instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See " +"our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-" +"bridge-mx-puppet-instagram.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2589 +msgid "" +"Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the " +"playbook now supports bridging to [Twitter](https://twitter.com/) via the" +" [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) " +"bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-" +"playbook-bridge-mx-puppet-twitter.md) documentation page for getting " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2592 +msgid "2020-06-28" +msgstr "" + +#: ../../../CHANGELOG.md:2594 +msgid "" +"(Post Mortem / fixed Security Issue) Re-enabling User Directory search " +"powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625 +msgid "" +"User Directory search requests used to go to the ma1sd identity server by" +" default, which queried its own stores and the Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2598 +msgid "" +"ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has " +"been fixed in version `2.4.0`, with [this " +"commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd " +"2.4.0` is now the default version for this playbook. For more information" +" on what happened, please check the mentioned issue." +msgstr "" + +#: ../../../CHANGELOG.md:2600 +msgid "" +"We are re-enabling user directory search with this update. Those who " +"would like to keep it disabled can use this configuration: " +"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:2602 +msgid "As always, re-running the playbook is enough to get the updated bits." +msgstr "" + +#: ../../../CHANGELOG.md:2604 +msgid "2020-06-11" +msgstr "" + +#: ../../../CHANGELOG.md:2606 +msgid "SMS bridging requires db reset" +msgstr "" + +#: ../../../CHANGELOG.md:2608 +msgid "" +"The current version of [matrix-sms-bridge](https://github.com/benkuly" +"/matrix-sms-bridge) needs you to delete the database to work as expected." +" Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new " +"requried var `matrix_sms_bridge_default_region`." +msgstr "" + +#: ../../../CHANGELOG.md:2610 +msgid "" +"To reuse your existing rooms, invite `@smsbot:yourServer` to the room or " +"write a message. You are also able to use automated room creation with " +"telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a" +" room with `@smsbot:yourServer`. See [the " +"docs](https://github.com/benkuly/matrix-sms-bridge) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:2612 +msgid "2020-06-05" +msgstr "" + +#: ../../../CHANGELOG.md:2614 +msgid "SMS bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2616 +msgid "" +"Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook " +"now supports bridging to SMS (with one telephone number only) via " +"[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2618 +msgid "" +"See our [Setting up Matrix SMS bridging](docs/configuring-playbook-" +"bridge-matrix-bridge-sms.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2621 +msgid "2020-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2623 +msgid "" +"(Compatibility Break / Security Issue) Disabling User Directory search " +"powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2627 +msgid "" +"ma1sd current has [a security " +"issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak " +"information about all users - including users created by bridges, etc." +msgstr "" + +#: ../../../CHANGELOG.md:2629 +msgid "" +"Until the issue gets fixed, we're making User Directory search not go to " +"ma1sd by default. You **need to re-run the playbook and restart services " +"to apply this workaround**." +msgstr "" + +#: ../../../CHANGELOG.md:2631 +msgid "" +"*If you insist on restoring the old behavior* (**which has a security " +"issue!**), you *might* use this configuration: " +"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ " +"matrix_ma1sd_enabled }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2634 +msgid "2020-04-28" +msgstr "" + +#: ../../../CHANGELOG.md:2636 +msgid "Newer IRC bridge (with potential breaking change)" +msgstr "" + +#: ../../../CHANGELOG.md:2638 +msgid "" +"This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made" +" a change to how you define manual mappings. If you added a `mapping` to" +" your configuration, you will need to update it accoring to the [upstream" +" instructions](https://github.com/matrix-org/matrix-appservice-" +"irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include " +"`mappings` in your configuration for IRC, no change is necessary. " +"`mappings` is not part of the default configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2647 +msgid "2020-04-23" +msgstr "" + +#: ../../../CHANGELOG.md:2649 ../../../CHANGELOG.md:2880 +msgid "Slack bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2651 +msgid "" +"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " +"playbook now supports bridging to [Slack](https://slack.com) via the [mx-" +"puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2653 +msgid "" +"See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-" +"bridge-mx-puppet-slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2656 +msgid "2020-04-09" +msgstr "" + +#: ../../../CHANGELOG.md:2658 +msgid "Skype bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2660 +msgid "" +"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " +"playbook now supports bridging to [Skype](https://www.skype.com) via the " +"[mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2662 +msgid "" +"See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-" +"bridge-mx-puppet-skype.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2665 +msgid "2020-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2667 +msgid "Private Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2669 +msgid "" +"The [Jitsi support](#jitsi-support) we had landed a few weeks ago was " +"working well, but it was always open to the whole world." +msgstr "" + +#: ../../../CHANGELOG.md:2671 +msgid "" +"Running such an open instance is not desirable to most people, so " +"[teutat3s](https://github.com/teutat3s) has contributed support for " +"making Jitsi use authentication." +msgstr "" + +#: ../../../CHANGELOG.md:2673 +msgid "" +"To make your Jitsi server more private, see the [configure internal Jitsi" +" authentication and guests mode](docs/configuring-playbook-jitsi.md" +"#optional-configure-internal-jitsi-authentication-and-guests-mode) " +"section in our Jitsi documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2676 +msgid "2020-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2678 +msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" +msgstr "" + +#: ../../../CHANGELOG.md:2680 +msgid "" +"Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the " +"[mxisd](https://github.com/kamax-io/mxisd) identity server, which has " +"been deprecated for a long time, has finally been replaced by " +"[ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." +msgstr "" + +#: ../../../CHANGELOG.md:2682 +msgid "" +"**If you're using the default playbook configuration**, you don't need to" +" do anything -- your mxisd installation will be replaced with ma1sd and " +"all existing data will be migrated automatically the next time you run " +"the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2684 +msgid "" +"**If you're doing something more special** (defining custom " +"`matrix_mxisd_*` variables), the playbook will ask you to rename them to " +"`matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well " +"for such a more custom setup." +msgstr "" + +#: ../../../CHANGELOG.md:2687 +msgid "2020-03-29" +msgstr "" + +#: ../../../CHANGELOG.md:2689 +msgid "Archlinux support" +msgstr "" + +#: ../../../CHANGELOG.md:2691 +msgid "" +"Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts," +" the playbook now supports installing to an " +"[Archlinux](https://www.archlinux.org/) server." +msgstr "" + +#: ../../../CHANGELOG.md:2694 +msgid "2020-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:2696 +msgid "Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2698 +msgid "" +"The playbook can now (optionally) install the [Jitsi](https://jitsi.org/)" +" video-conferencing platform and integrate it with [Riot](docs" +"/configuring-playbook-riot-web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2700 +msgid "" +"See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to" +" get started." +msgstr "" + +#: ../../../CHANGELOG.md:2703 +msgid "2020-03-15" +msgstr "" + +#: ../../../CHANGELOG.md:2705 +msgid "Raspberry Pi support" +msgstr "" + +#: ../../../CHANGELOG.md:2707 +msgid "" +"Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the " +"playbook supports installing to a Raspberry Pi server, for at least some " +"of the services." +msgstr "" + +#: ../../../CHANGELOG.md:2709 +msgid "" +"Since most ready-made container images do not support that architecture, " +"we achieve this by building images locally on the device itself. See our " +"[Self-building documentation page](docs/self-building.md) for how to get " +"started." +msgstr "" + +#: ../../../CHANGELOG.md:2712 +msgid "2020-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:2714 +msgid "Riot-web themes are here" +msgstr "" + +#: ../../../CHANGELOG.md:2716 +msgid "The playbook now makes it easy to install custom riot-web themes." +msgstr "" + +#: ../../../CHANGELOG.md:2718 +msgid "" +"To learn more, take a look at our [riot-web documentation on Themes](docs" +"/configuring-playbook-riot-web.md#themes)." +msgstr "" + +#: ../../../CHANGELOG.md:2721 +msgid "2020-02-24" +msgstr "" + +#: ../../../CHANGELOG.md:2723 +msgid "Customize the server name in Riot's login page" +msgstr "" + +#: ../../../CHANGELOG.md:2725 +msgid "" +"You can now customize the server name string that Riot-web displays in " +"its login page." +msgstr "" + +#: ../../../CHANGELOG.md:2727 +msgid "These playbook variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:2733 +msgid "" +"The login page previously said \"Sign in to your Matrix account on " +"matrix.example.org\" (the homeserver's domain name). It will now say " +"\"Sign in … on example.org\" (the server name) by default, or \"Sign in …" +" on Our Server\" if you set the variable to \"Our Server\"." +msgstr "" + +#: ../../../CHANGELOG.md:2735 +msgid "" +"To support this, the config.json template is changed to use the " +"configuration key `default_server_config` for setting the default HS/IS, " +"and the new configuration key `server_name` is added in there." +msgstr "" + +#: ../../../CHANGELOG.md:2738 +msgid "2020-01-30" +msgstr "" + +#: ../../../CHANGELOG.md:2740 +msgid "Disabling TLSv1.1" +msgstr "" + +#: ../../../CHANGELOG.md:2742 +msgid "" +"To improve security, we've removed TLSv1.1 support from our default " +"matrix-nginx-proxy configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2744 +msgid "" +"If you need to support old clients, you can re-enable it with the " +"following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 " +"TLSv1.2 TLSv1.3\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2747 +msgid "2020-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:2749 +msgid "Postgres collation changes (action required!)" +msgstr "" + +#: ../../../CHANGELOG.md:2751 +msgid "" +"By default, we've been using a UTF-8 collation for Postgres. This is " +"known to cause Synapse some troubles (see the [relevant " +"issue](https://github.com/matrix-org/synapse/issues/6722)) on systems " +"that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in " +"an [Alpine Linux](https://alpinelinux.org/) container (which uses " +"[musl](https://www.musl-libc.org/), and not glibc), so our users are " +"likely not affected by the index corruption problem observed by others." +msgstr "" + +#: ../../../CHANGELOG.md:2753 +msgid "" +"Still, we might become affected in the future. In any case, it's imminent" +" that Synapse will complain about databases which do not use a C " +"collation." +msgstr "" + +#: ../../../CHANGELOG.md:2755 +msgid "To avoid future problems, we recommend that you run the following command:" +msgstr "" + +#: ../../../CHANGELOG.md:2761 +msgid "" +"It forces a [Postgres database upgrade](docs/maintenance-postgres.md" +"#upgrading-postgresql), which would recreate your Postgres database using" +" the proper (`C`) collation. If you are low on disk space, or run into " +"trouble, refer to the Postgres database upgrade documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:2764 +msgid "2020-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2766 +msgid "Added support for Appservice Webhooks" +msgstr "" + +#: ../../../CHANGELOG.md:2768 +msgid "" +"Thanks to a contribution from [Björn " +"Marten](https://github.com/tripleawwy) from " +"[netresearch](https://www.netresearch.de/), the playbook can now install " +"and configure [matrix-appservice-webhooks](https://github.com/turt2live" +"/matrix-appservice-webhooks) for you. This bridge provides support for " +"Slack-compatible webhooks." +msgstr "" + +#: ../../../CHANGELOG.md:2770 +msgid "" +"Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-" +"playbook-bridge-appservice-webhooks.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2773 +msgid "2020-01-12" +msgstr "" + +#: ../../../CHANGELOG.md:2775 +msgid "Added support for automatic Double Puppeting for all Mautrix bridges" +msgstr "" + +#: ../../../CHANGELOG.md:2777 +msgid "" +"Double Puppeting can now be easily enabled for all Mautrix bridges " +"supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." +msgstr "" + +#: ../../../CHANGELOG.md:2779 +msgid "" +"This is possible due to those bridges' integration with [matrix-synapse-" +"shared-secret-auth](https://github.com/devture/matrix-synapse-shared-" +"secret-auth) - yet another component that this playbook can install for " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:2781 +msgid "" +"To get started, following the playbook's documentation for the bridge " +"you'd like to configure." +msgstr "" + +#: ../../../CHANGELOG.md:2784 +msgid "2019-12-06" +msgstr "" + +#: ../../../CHANGELOG.md:2786 +msgid "Added support for an alternative method for using another webserver" +msgstr "" + +#: ../../../CHANGELOG.md:2788 +msgid "" +"We have added support for making `matrix-nginx-proxy` not being so " +"invasive, so that it would be easier to [use your own webserver](docs" +"/configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2790 +msgid "" +"The documentation has been updated with a **Method 2**, which might make " +"\"own webserver\" setup easier in some cases (such as [reverse-proxying " +"using Traefik](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/296))." +msgstr "" + +#: ../../../CHANGELOG.md:2792 +msgid "" +"**Existing users** are not affected by this and **don't need to change " +"anything**. The defaults are still the same (`matrix-nginx-proxy` " +"obtaining SSL certificates and doing everything for you automatically)." +msgstr "" + +#: ../../../CHANGELOG.md:2795 +msgid "2019-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2797 +msgid "Tightened security around room directory publishing" +msgstr "" + +#: ../../../CHANGELOG.md:2799 +msgid "" +"As per this [advisory blog post](https://matrix.org/blog/2019/11/09" +"/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to" +" change the default publishing rules for the Matrix room directory." +msgstr "" + +#: ../../../CHANGELOG.md:2801 +msgid "" +"Our general goal is to favor privacy and security when running personal " +"(family & friends) and corporate homeservers. Both of these likely " +"benefit from having a more secure default of **not showing the room " +"directory without authentication** and **not publishing the room " +"directory over federation**." +msgstr "" + +#: ../../../CHANGELOG.md:2803 +msgid "" +"As with anything else, these new defaults can be overriden by changing " +"the `matrix_synapse_allow_public_rooms_without_auth` and " +"`matrix_synapse_allow_public_rooms_over_federation` variables, " +"respectively." +msgstr "" + +#: ../../../CHANGELOG.md:2806 +msgid "2019-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:2808 +msgid "Improved Postgres upgrading/importing" +msgstr "" + +#: ../../../CHANGELOG.md:2810 +msgid "" +"Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) " +"and [importing](docs/importing-postgres.md) have been improved to add " +"support for multiple databases and roles." +msgstr "" + +#: ../../../CHANGELOG.md:2812 +msgid "" +"Previously, the playbook would only take care of the `homeserver` " +"database and `synapse` user. We now back up and restore all databases and" +" users on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2814 +msgid "" +"For now, the playbook only uses that one database (`homeserver`) and that" +" one single user (`synapse`), so it's all the same. However, in the " +"future, additional components besides Synapse may also make use the " +"Postgres database server. One such example is the [matrix-appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, " +"which strongly encourages use of Postgres in its v1.0 release. We are yet" +" to upgrade to it." +msgstr "" + +#: ../../../CHANGELOG.md:2816 +msgid "" +"Additionally, Postgres [upgrading](docs/maintenance-postgres.md" +"#upgrading-postgresql) now uses gzipped dump files by default, to " +"minimize disk space usage." +msgstr "" + +#: ../../../CHANGELOG.md:2819 +msgid "2019-10-04" +msgstr "" + +#: ../../../CHANGELOG.md:2821 +msgid "Postgres 12 support" +msgstr "" + +#: ../../../CHANGELOG.md:2823 +msgid "" +"The playbook now installs [Postgres " +"12](https://www.postgresql.org/about/news/1976/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:2825 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following" +" the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" +"postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2828 +msgid "2019-10-03" +msgstr "" + +#: ../../../CHANGELOG.md:2830 +msgid "Synapse 1.4.0" +msgstr "" + +#: ../../../CHANGELOG.md:2832 +msgid "" +"Synapse 1.4.0 [is " +"out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots" +" of changes related to privacy." +msgstr "" + +#: ../../../CHANGELOG.md:2834 +msgid "" +"Its new defaults (which we adopt as well) mean that certain old data will" +" automatically get purged after a certain number of days. 1.4.0 " +"automatically garbage collects redacted messages (defaults to 7 days) and" +" removes unused IP and user agent information stored in the user_ips " +"table (defaults to 30 days). If you'd like to preserve this data, we " +"encourage you to look at the `redaction_retention_period` and " +"`user_ips_max_age` options (controllable by the " +"`matrix_synapse_redaction_retention_period` and " +"`matrix_synapse_user_ips_max_age` playbook variables, respectively) " +"before doing the upgrade. If you'd like to keep data indefinitely, set " +"these variables to `null` (e.g. " +"`matrix_synapse_redaction_retention_period: ~`)." +msgstr "" + +#: ../../../CHANGELOG.md:2836 +msgid "" +"From now on the `trusted_key_servers` setting for Synapse is " +"configurable. It still defaults to `matrix.org` just like it always has, " +"but in a more explicit way now. If you'd like to use another trusted key " +"server, adjust the `matrix_synapse_trusted_key_servers` playbook " +"variable." +msgstr "" + +#: ../../../CHANGELOG.md:2838 +msgid "" +"Synapse 1.4.0 also changes lots of things related to identity server " +"integration. Because Synapse will now by default be responsible for " +"validating email addresses for user accounts, running without an identity" +" server looks more feasible. We still [have " +"concerns](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/pull/275/files#r331104117) over disabling the identity server by " +"default, so for now it remains enabled." +msgstr "" + +#: ../../../CHANGELOG.md:2841 +msgid "2019-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:2843 +msgid "Synapse Simple Antispam support" +msgstr "" + +#: ../../../CHANGELOG.md:2845 +msgid "" +"There have been lots of invite-spam attacks lately and " +"[Travis](https://github.com/t2bot) has created a Synapse module " +"([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" +"antispam)) to let people protect themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2847 +msgid "" +"From now on, you can easily install and configure this spam checker " +"module through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2849 +msgid "" +"Learn more in [Setting up Synapse Simple Antispam](docs/configuring-" +"playbook-synapse-simple-antispam.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2852 +msgid "2019-08-25" +msgstr "" + +#: ../../../CHANGELOG.md:2854 +msgid "Extensible Riot-web configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2856 +msgid "" +"Similarly to [Extensible Synapse configuration](#extensible-synapse-" +"configuration) (below), Riot-web configuration is also extensible now." +msgstr "" + +#: ../../../CHANGELOG.md:2858 +msgid "" +"From now on, you can extend/override Riot-web's configuration by making " +"use of the `matrix_riot_web_configuration_extension_json` variable. This " +"should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2860 +msgid "" +"If you need even more power, you can now also take full control and " +"override `matrix_riot_web_configuration_default` (or " +"`matrix_riot_web_configuration`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2862 +msgid "" +"Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-" +"web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2865 +msgid "2019-08-22" +msgstr "" + +#: ../../../CHANGELOG.md:2867 +msgid "Extensible Synapse configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2869 +msgid "" +"Previously, we had to create custom Ansible variables for each and every " +"Synapse setting. This lead to too much effort (and configuration " +"ugliness) to all of Synapse's settings, so naturally, not all features of" +" Synapse could be controlled through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2871 +msgid "" +"From now on, you can extend/override the Synapse server's configuration " +"by making use of the `matrix_synapse_configuration_extension_yaml` " +"variable. This should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2873 +msgid "" +"If you need even more power, you can now also take full control and " +"override `matrix_synapse_configuration` (or " +"`matrix_synapse_configuration_yaml`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2875 +msgid "" +"Learn more here in [Configuring Synapse](docs/configuring-playbook-" +"synapse.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2878 +msgid "2019-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2882 +msgid "" +"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/205) of " +"[kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart " +"Mumford (Cadair)](https://github.com/Cadair), the playbook now supports " +"bridging to [Slack](https://slack.com) via the [appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2884 +msgid "" +"Additional details are available in [Setting up Appservice Slack " +"bridging](docs/configuring-playbook-bridge-appservice-slack.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2886 +msgid "Google Hangouts bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2888 +msgid "" +"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/pull/251) of [Eduardo Beltrame " +"(Munfred)](https://github.com/Munfred) and [Robbie D " +"(microchipster)](https://github.com/microchipster), the playbook now " +"supports bridging to [Google Hangouts](https://hangouts.google.com/) via " +"the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2890 +msgid "" +"Additional details are available in [Setting up Mautrix Hangouts " +"bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2893 +msgid "2019-08-05" +msgstr "" + +#: ../../../CHANGELOG.md:2895 +msgid "Email2Matrix support" +msgstr "" + +#: ../../../CHANGELOG.md:2897 +msgid "" +"Support for [Email2Matrix](https://github.com/devture/email2matrix) has " +"been added." +msgstr "" + +#: ../../../CHANGELOG.md:2899 +msgid "It's an optional feature that you can enable via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2901 +msgid "" +"To learn more, see the [playbook's documentation on Email2Matrix](./docs" +"/configuring-playbook-email2matrix.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2904 +msgid "2019-08-03" +msgstr "" + +#: ../../../CHANGELOG.md:2906 +msgid "Synapse logging level has been reduced to WARNING" +msgstr "" + +#: ../../../CHANGELOG.md:2908 +msgid "" +"After [some discussion in our support " +"room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one)," +" we've decided to change the default logging level for Synapse from " +"`INFO` to `WARNING`." +msgstr "" + +#: ../../../CHANGELOG.md:2910 +msgid "" +"This greatly reduces the number of log messages that are being logged, " +"leading to:" +msgstr "" + +#: ../../../CHANGELOG.md:2912 +msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" +msgstr "" + +#: ../../../CHANGELOG.md:2913 +msgid "" +"easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages," +" as they're not longer buried in thousands of non-important `INFO` " +"messages" +msgstr "" + +#: ../../../CHANGELOG.md:2915 +msgid "" +"If you'd like to track down an issue, you [can always increase the " +"logging level as described here](./docs/maintenance-and-" +"troubleshooting.md#increasing-synapse-logging)." +msgstr "" + +#: ../../../CHANGELOG.md:2918 +msgid "2019-07-08" +msgstr "" + +#: ../../../CHANGELOG.md:2920 +msgid "Synapse Maintenance docs and synapse-janitor support are available" +msgstr "" + +#: ../../../CHANGELOG.md:2922 +msgid "The playbook can now help you with Synapse's maintenance." +msgstr "" + +#: ../../../CHANGELOG.md:2924 +msgid "" +"There's a new documentation page about [Synapse maintenance](./docs" +"/maintenance-synapse.md) and another section on [Postgres " +"vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2926 +msgid "" +"Among other things, if your Postgres database has grown significantly " +"over time, you may wish to [ask the playbook to purge unused data with " +"synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-" +"synapse-janitor) for you." +msgstr "" + +#: ../../../CHANGELOG.md:2928 +msgid "(BC Break) Rename run control variables" +msgstr "" + +#: ../../../CHANGELOG.md:2930 +msgid "Some internal playbook control variables have been renamed." +msgstr "" + +#: ../../../CHANGELOG.md:2932 +msgid "" +"This change **only affects people who run this playbook's roles from " +"another playbook**. If you're using this playbook as-is, you're not " +"affected and don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:2934 +msgid "The following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:2936 +msgid "from `run_import_postgres` to `run_postgres_import`" +msgstr "" + +#: ../../../CHANGELOG.md:2937 +msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`" +msgstr "" + +#: ../../../CHANGELOG.md:2938 +msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`" +msgstr "" + +#: ../../../CHANGELOG.md:2939 +msgid "from `run_import_media_store` to `run_synapse_import_media_store`" +msgstr "" + +#: ../../../CHANGELOG.md:2940 +msgid "from `run_register_user` to `run_synapse_register_user`" +msgstr "" + +#: ../../../CHANGELOG.md:2941 +msgid "from `run_update_user_password` to `run_synapse_update_user_password`" +msgstr "" + +#: ../../../CHANGELOG.md:2944 +msgid "2019-07-04" +msgstr "" + +#: ../../../CHANGELOG.md:2946 +msgid "Synapse no longer logs to text files" +msgstr "" + +#: ../../../CHANGELOG.md:2948 +msgid "" +"Following what the official Synapse Docker image is doing " +"([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've" +" been doing for mostly everything installed by this playbook, **Synapse " +"no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2950 +msgid "" +"From now on, Synapse would only log to console, which goes to systemd's " +"journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:2952 +msgid "" +"Because of this, the following variables have become obsolete and were " +"removed:" +msgstr "" + +#: ../../../CHANGELOG.md:2954 +msgid "`matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:2955 +msgid "`matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:2957 +msgid "" +"To prevent confusion, it'd be better if you delete all old files manually" +" after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2959 +msgid "" +"Because Synapse is incredibly chatty when it comes to logging (here's " +"[one such issue](https://github.com/matrix-org/synapse/issues/4751) " +"describing the problem), if you're running an ancient distribution (like " +"CentOS 7.0), be advised that systemd's journald default logging " +"restrictions may not be high enough to capture all log messages generated" +" by Synapse. This is especially true if you've got a busy (Synapse) " +"server. We advise that you manually add `RateLimitInterval=0` and " +"`RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` " +"file, followed by restarting the logging service (`systemctl restart " +"systemd-journald`)." +msgstr "" + +#: ../../../CHANGELOG.md:2962 +msgid "2019-06-27" +msgstr "" + +#: ../../../CHANGELOG.md:2964 +msgid "" +"(BC Break) Discord bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2966 +msgid "" +"Until now, the `config.yaml` file for the [Discord bridge](docs" +"/configuring-playbook-bridge-appservice-discord.md) was managed by the " +"playbook, but the `registration.yaml` file was not." +msgstr "" + +#: ../../../CHANGELOG.md:2968 +msgid "From now on, the playbook will keep both configuration files sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2970 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/appservice-discord/discord-registration.yaml` configuration file, those " +"would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2972 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix" +"/appservice-discord/config`)." +msgstr "" + +#: ../../../CHANGELOG.md:2974 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/appservice-" +"discord/data`). When you run the playbook with an existing database file " +"(`/matrix/appservice-discord/discord.db`), the playbook will stop the " +"bridge and relocate the database file to the `./data` directory. There's " +"no data-loss involved. You'll need to restart the bridge manually though " +"(`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2976 +msgid "" +"The main directory (`/matrix/appservice-discord`) may contain some " +"leftover files (`user-store.db`, `room-store.db`, `config.yaml`, " +"`discord-registration.yaml`, `invite_link`). These are no longer " +"necessary and can be deleted manually." +msgstr "" + +#: ../../../CHANGELOG.md:2978 +msgid "" +"We're now following the default sample configuration for the Discord " +"bridge. If you need to override some values, define them in " +"`matrix_appservice_discord_configuration_extension_yaml`." +msgstr "" + +#: ../../../CHANGELOG.md:2981 +msgid "2019-06-24" +msgstr "" + +#: ../../../CHANGELOG.md:2983 +msgid "" +"(BC Break) WhatsApp bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2985 +msgid "" +"Until now, configuration files for the [WhatsApp bridge](docs" +"/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004 +#: ../../../CHANGELOG.md:3023 ../../../CHANGELOG.md:3062 +msgid "From now on, the playbook will keep the configuration in sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2989 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-" +"whatsapp/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2991 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"whatsapp/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:2993 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"whatsapp/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2995 +msgid "We're now following the default configuration for the WhatsApp bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2998 +msgid "2019-06-20" +msgstr "" + +#: ../../../CHANGELOG.md:3000 +msgid "" +"(BC Break) IRC bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3002 +msgid "" +"Until now, configuration files for the [IRC bridge](docs/configuring-" +"playbook-bridge-appservice-irc.md) were created by the playbook " +"initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3006 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/appservice-irc/config.yaml` or `/matrix/appservice-" +"irc/registration.yaml` configuration files, those would be lost the next " +"time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3008 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix" +"/appservice-irc/config`), so your old configuration remains in the base " +"directory (`/matrix/appservice-irc`)." +msgstr "" + +#: ../../../CHANGELOG.md:3010 +msgid "" +"Previously, we asked people to configure bridged IRC servers by extending" +" the bridge configuration " +"(`matrix_appservice_irc_configuration_extension_yaml`). While this is " +"still possible and will continue working forever, **we now recommend " +"defining IRC servers in the easier to use " +"`matrix_appservice_irc_ircService_servers` variable**. See [our IRC " +"bridge documentation page](docs/configuring-playbook-bridge-appservice-" +"irc.md) for an example." +msgstr "" + +#: ../../../CHANGELOG.md:3012 +msgid "" +"If you decide to continue using " +"`matrix_appservice_irc_configuration_extension_yaml`, you might be " +"interested to know that `ircService.databaseUri` and a few other keys now" +" have default values in the base configuration " +"(`matrix_appservice_irc_configuration_yaml`). You may wish to stop " +"redefining those keys, unless you really intend to override them. You " +"most likely only need to override `ircService.servers`." +msgstr "" + +#: ../../../CHANGELOG.md:3014 +msgid "" +"Bridge data (`passkey.pem` and database files) is now also stored in a " +"subdirectory (`/matrix/appservice-irc/data`). When you run the playbook " +"with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook " +"will stop the bridge and relocate the passkey and database files " +"(`rooms.db` and `users.db`) to the `./data` directory. There's no data-" +"loss involved. You'll need to restart the bridge manually though " +"(`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3017 +msgid "2019-06-15" +msgstr "" + +#: ../../../CHANGELOG.md:3019 +msgid "" +"(BC Break) Telegram bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3021 +msgid "" +"Until now, configuration files for the [Telegram bridge](docs" +"/configuring-playbook-bridge-mautrix-telegram.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3025 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-telegram/config.yaml` or `/matrix/mautrix-" +"telegram/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3027 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"telegram/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-telegram`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_telegram_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3029 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"telegram/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3031 +msgid "" +"Also, we're now following the default configuration for the Telegram " +"bridge, so some default configuration values are different:" +msgstr "" + +#: ../../../CHANGELOG.md:3033 +msgid "" +"`edits_as_replies` (used to be `false`, now `true`) - previously replies " +"were not sent over to Matrix at all; ow they are sent over as a reply to " +"the original message" +msgstr "" + +#: ../../../CHANGELOG.md:3034 +msgid "" +"`inline_images` (used to be `true`, now `false`) - this has to do with " +"captioned images. Inline-image (included caption) are said to exhibit " +"troubles on Riot iOS. When `false`, the caption arrives on the Matrix " +"side as a separate message." +msgstr "" + +#: ../../../CHANGELOG.md:3035 +msgid "" +"`authless_portals` (used to be `false`, now `true`) - creating portals " +"from the Telegram side is now possible" +msgstr "" + +#: ../../../CHANGELOG.md:3036 +msgid "" +"`whitelist_group_admins` (used to be `false`, now `true`) - allows " +"Telegram group admins to use the bot commands" +msgstr "" + +#: ../../../CHANGELOG.md:3038 +msgid "" +"If the new values are not to your liking, use " +"`matrix_mautrix_telegram_configuration_extension_yaml` to specify an " +"override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure" +" out which variable goes where)." +msgstr "" + +#: ../../../CHANGELOG.md:3041 +msgid "2019-06-12" +msgstr "" + +#: ../../../CHANGELOG.md:3043 +msgid "Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3045 +msgid "" +"With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11" +"/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people " +"being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` " +"DNS SRV record that we've been keeping for compatibility with old Synapse" +" versions (<= 0.34)." +msgstr "" + +#: ../../../CHANGELOG.md:3047 +msgid "" +"According to the [Server Discovery " +"specification](https://matrix.org/docs/spec/server_server/r0.1.2.html" +"#server-discovery), it's no harm to keep the DNS SRV record. But since " +"it's not necessary for federating with the larger Matrix network anymore," +" you should be safe to get rid of it." +msgstr "" + +#: ../../../CHANGELOG.md:3049 +msgid "" +"**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` " +"DNS SRV records. The latter, **must not** be removed." +msgstr "" + +#: ../../../CHANGELOG.md:3051 +msgid "" +"For completeness, we must say that using a `_matrix._tcp` [SRV record for" +" Server Delegation](docs/howto-server-delegation.md#server-delegation-" +"via-a-dns-srv-record-advanced) is still valid and useful for certain " +"deployments. It's just that our guide recommends the [`/.well-" +"known/matrix/server` Server Delegation method](docs/howto-server-" +"delegation.md#server-delegation-via-a-well-known-file), due to its easier" +" implementation when using this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3053 +msgid "" +"Besides this optional/non-urgent DNS change, assuming you're already on " +"Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-" +"running the playbook](docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3056 +msgid "2019-06-07" +msgstr "" + +#: ../../../CHANGELOG.md:3058 +msgid "" +"(BC Break) Facebook bridge configuration is now entirely managed by the " +"playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3060 +msgid "" +"Until now, configuration files for the [Facebook bridge](docs" +"/configuring-playbook-bridge-mautrix-facebook.md) were created by the " +"playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3064 +msgid "" +"This means that if you were making manual changes to the `/matrix" +"/mautrix-facebook/config.yaml` or `/matrix/mautrix-" +"facebook/registration.yaml` configuration files, those would be lost the " +"next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3066 +msgid "" +"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" +"facebook/config`), so your old configuration remains in the base " +"directory (`/matrix/mautrix-facebook`). You need to migrate any manual " +"changes over to the new " +"`matrix_mautrix_facebook_configuration_extension_yaml` variable, so that " +"the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3068 +msgid "" +"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" +"facebook/data`). When you run the playbook with an existing database file" +" (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop" +" the bridge and relocate the database file to the `./data` directory. " +"There's no data-loss involved. You'll need to restart the bridge manually" +" though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3071 +msgid "2019-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:3073 +msgid "Support for exposing container ports publicly (not just to the host)" +msgstr "" + +#: ../../../CHANGELOG.md:3075 +msgid "" +"Until now, various roles supported a `matrix_*_expose_port` variable, " +"which would expose their container's port to the host. This was mostly " +"useful for reverse-proxying manually (in case `matrix-nginx-proxy` was " +"disabled). It could also be used for installing some playbook services " +"(e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." +msgstr "" + +#: ../../../CHANGELOG.md:3077 +msgid "" +"`matrix_*_expose_port` variables were not granular enough - sometimes " +"they would expose one port, other times multiple. They also didn't " +"provide control over **where** to expose (to which port number and to " +"which network interface), because they would usually hardcode something " +"like `127.0.0.1:8080`." +msgstr "" + +#: ../../../CHANGELOG.md:3079 +msgid "" +"All such variables have been superseded by a better (more flexible) way " +"to do it." +msgstr "" + +#: ../../../CHANGELOG.md:3081 +msgid "" +"**Most** people (including those not using `matrix-nginx-proxy`), **don't" +" need** to bother with this." +msgstr "" + +#: ../../../CHANGELOG.md:3083 +msgid "Porting examples follow for people having more customized setups:" +msgstr "" + +#: ../../../CHANGELOG.md:3085 +msgid "" +"**from** `matrix_synapse_container_expose_client_api_port: true` **to** " +"`matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" +msgstr "" + +#: ../../../CHANGELOG.md:3087 +msgid "" +"**from** `matrix_synapse_container_expose_federation_api_port: true` " +"**to** `matrix_synapse_container_federation_api_plain_host_bind_port: " +"'127.0.0.1:8048'` and possibly " +"`matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" +msgstr "" + +#: ../../../CHANGELOG.md:3089 +msgid "" +"**from** `matrix_synapse_container_expose_metrics_port: true` **to** " +"`matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" +msgstr "" + +#: ../../../CHANGELOG.md:3091 +msgid "" +"**from** `matrix_riot_web_container_expose_port: true` **to** " +"`matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" +msgstr "" + +#: ../../../CHANGELOG.md:3093 +msgid "" +"**from** `matrix_mxisd_container_expose_port: true` **to** " +"`matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" +msgstr "" + +#: ../../../CHANGELOG.md:3095 +msgid "" +"**from** `matrix_dimension_container_expose_port: true` **to** " +"`matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" +msgstr "" + +#: ../../../CHANGELOG.md:3097 +msgid "" +"**from** `matrix_corporal_container_expose_ports: true` **to** " +"`matrix_corporal_container_http_gateway_host_bind_port: " +"'127.0.0.1:41080'` and possibly " +"`matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" +msgstr "" + +#: ../../../CHANGELOG.md:3099 +msgid "" +"**from** `matrix_appservice_irc_container_expose_client_server_api_port: " +"true` **to** `matrix_appservice_irc_container_http_host_bind_port: " +"'127.0.0.1:9999'`" +msgstr "" + +#: ../../../CHANGELOG.md:3101 +msgid "" +"**from** " +"`matrix_appservice_discord_container_expose_client_server_api_port: true`" +" **to** `matrix_appservice_discord_container_http_host_bind_port: " +"'127.0.0.1:9005'`" +msgstr "" + +#: ../../../CHANGELOG.md:3103 +msgid "" +"As always, if you forget to remove usage of some outdated variable, the " +"playbook will warn you." +msgstr "" + +#: ../../../CHANGELOG.md:3106 +msgid "2019-05-23" +msgstr "" + +#: ../../../CHANGELOG.md:3108 +msgid "(BC Break) Ansible 2.8 compatibility" +msgstr "" + +#: ../../../CHANGELOG.md:3110 +msgid "" +"Thanks to [@danbob](https://github.com/danbob), the playbook now " +"[supports the new Ansible 2.8](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/pull/187)." +msgstr "" + +#: ../../../CHANGELOG.md:3112 +msgid "" +"A manual change is required to the `inventory/hosts` file, changing the " +"group name from `matrix-servers` to `matrix_servers` (dash to " +"underscore)." +msgstr "" + +#: ../../../CHANGELOG.md:3114 +msgid "To avoid doing it manually, run this:" +msgstr "" + +#: ../../../CHANGELOG.md:3115 +msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3116 +msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3119 +msgid "2019-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:3121 +msgid "Synapse no longer required" +msgstr "" + +#: ../../../CHANGELOG.md:3123 +msgid "" +"The playbook no longer insists on installing [Synapse](https://github.com" +"/element-hq/synapse) via the `matrix-synapse` role." +msgstr "" + +#: ../../../CHANGELOG.md:3125 +msgid "" +"If you would prefer to install Synapse another way and just use the " +"playbook to install other services, it should be possible " +"(`matrix_synapse_enabled: false`)." +msgstr "" + +#: ../../../CHANGELOG.md:3127 +msgid "" +"Note that it won't necessarily be the best experience, since the playbook" +" wires things to Synapse by default. If you're using your own Synapse " +"instance (especially one not running in a container), you may have to " +"override many variables to point them to the correct place." +msgstr "" + +#: ../../../CHANGELOG.md:3129 +msgid "" +"Having Synapse not be a required component potentially opens the door for" +" installing alternative Matrix homeservers." +msgstr "" + +#: ../../../CHANGELOG.md:3131 +msgid "Bridges are now separate from the Synapse role" +msgstr "" + +#: ../../../CHANGELOG.md:3133 +msgid "" +"Bridges are no longer part of the `matrix-synapse` role. Each bridge now " +"lives in its own separate role (`roles/custom/matrix-bridge-*`)." +msgstr "" + +#: ../../../CHANGELOG.md:3135 +msgid "" +"These bridge roles are independent of the `matrix-synapse` role, so it " +"should be possible to use them with a Synapse instance installed another " +"way (not through the playbook)." +msgstr "" + +#: ../../../CHANGELOG.md:3137 +msgid "Renaming inconsistently-named Synapse variables" +msgstr "" + +#: ../../../CHANGELOG.md:3139 +msgid "For better consistency, the following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3141 +msgid "" +"`matrix_enable_room_list_search` was renamed to " +"`matrix_synapse_enable_room_list_search`" +msgstr "" + +#: ../../../CHANGELOG.md:3142 +msgid "" +"`matrix_alias_creation_rules` was renamed to " +"`matrix_synapse_alias_creation_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3143 +msgid "" +"`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was " +"renamed to `matrix_synapse_room_list_publication_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3146 +msgid "2019-05-09" +msgstr "" + +#: ../../../CHANGELOG.md:3148 +msgid "" +"Besides a myriad of bug fixes and minor improvements, here are the more " +"notable (bigger) features we can announce today." +msgstr "" + +#: ../../../CHANGELOG.md:3150 +msgid "Mautrix Facebook/Messenger bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3152 +msgid "" +"The playbook now supports bridging with " +"[Facebook](https://www.facebook.com/) by installing the [mautrix-" +"facebook](https://github.com/tulir/mautrix-facebook) bridge. This " +"playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3154 +msgid "" +"Additional details are available in [Setting up Mautrix Facebook " +"bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3156 +msgid "mxisd Registration feature integration" +msgstr "" + +#: ../../../CHANGELOG.md:3158 +msgid "" +"The playbook can now help you integrate with mxisd's " +"[Registration](https://github.com/kamax-" +"matrix/mxisd/blob/master/docs/features/registration.md) feature." +msgstr "" + +#: ../../../CHANGELOG.md:3160 +msgid "" +"Learn more in [mxisd-controlled Registration](docs/configuring-playbook-" +"mxisd.md#mxisd-controlled-registration)." +msgstr "" + +#: ../../../CHANGELOG.md:3163 +msgid "2019-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:3165 +msgid "Caddy webserver examples" +msgstr "" + +#: ../../../CHANGELOG.md:3167 +msgid "" +"If you prefer using the [Caddy](https://caddyserver.com/) webserver " +"instead of our own integrated nginx, we now have examples for it in the " +"[`examples/caddy`](examples/caddy) directory" +msgstr "" + +#: ../../../CHANGELOG.md:3169 +msgid "2019-04-10" +msgstr "" + +#: ../../../CHANGELOG.md:3171 +msgid "Goofys support for other S3-compatible object stores" +msgstr "" + +#: ../../../CHANGELOG.md:3173 +msgid "" +"Until now, you could optionally host Synapse's media repository on Amazon" +" S3, but we now also support [using other S3-compatible object " +"stores](docs/configuring-playbook-s3.md)," +msgstr "" + +#: ../../../CHANGELOG.md:3176 +msgid "2019-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:3178 +msgid "Ansible >= 2.5 is required" +msgstr "" + +#: ../../../CHANGELOG.md:3180 +msgid "" +"Due to recent playbook improvements and the fact that the world keeps " +"turning, we're bumping the [version requirement for " +"Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." +msgstr "" + +#: ../../../CHANGELOG.md:3182 +msgid "" +"We've also started building our own Docker image of Ansible " +"([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is " +"useful for people who can't upgrade their local Ansible installation (see" +" [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." +msgstr "" + +#: ../../../CHANGELOG.md:3185 +msgid "2019-03-19" +msgstr "" + +#: ../../../CHANGELOG.md:3187 +msgid "TLS support for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:3189 +msgid "" +"We've added TLS support to the Coturn TURN server installed by the " +"playbook by default. The certificates from the Matrix domain will be used" +" for the Coturn server." +msgstr "" + +#: ../../../CHANGELOG.md:3191 +msgid "" +"This feature is enabled by default for new installations. To make use of " +"TLS support for your existing Matrix server's Coturn, make sure to " +"rebuild both Coturn and Synapse:" +msgstr "" + +#: ../../../CHANGELOG.md:3197 +msgid "" +"People who have an extra firewall (besides the iptables firewall, which " +"Docker manages automatically), will need to open these additional " +"firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over " +"UDP)." +msgstr "" + +#: ../../../CHANGELOG.md:3199 +msgid "" +"People who build their own custom playbook from our roles should be aware" +" that:" +msgstr "" + +#: ../../../CHANGELOG.md:3201 +msgid "" +"the `matrix-coturn` role and actually starting Coturn (e.g. " +"`--tags=start`), requires that certificates are already put in place. For" +" this reason, it's usually a good idea to have the `matrix-coturn` role " +"execute after `matrix-nginx-proxy` (which retrieves the certificates)." +msgstr "" + +#: ../../../CHANGELOG.md:3203 +msgid "" +"there are a few variables that can help you enable TLS support for " +"Coturn. See the `matrix-coturn` section in [group_vars/matrix-" +"servers](./group_vars/matrix-servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3206 +msgid "2019-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:3208 +msgid "matrix-nginx-proxy support for serving the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:3210 +msgid "" +"If you don't have a dedicated server for your base domain and want to set" +" up [Server Delegation via a well-known file](docs/howto-server-" +"delegation.md#server-delegation-via-a-well-known-file), the playbook has " +"got you covered now." +msgstr "" + +#: ../../../CHANGELOG.md:3212 +msgid "" +"It's now possible for the playbook to obtain an SSL certificate and serve" +" the necessary files for Matrix Server Delegation on your base domain. " +"Take a look at the new [Serving the base domain](docs/configuring-" +"playbook-base-domain-serving.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3214 +msgid "(BC break) matrix-nginx-proxy data variable renamed" +msgstr "" + +#: ../../../CHANGELOG.md:3216 +msgid "" +"`matrix_nginx_proxy_data_path` was renamed to " +"`matrix_nginx_proxy_base_path`." +msgstr "" + +#: ../../../CHANGELOG.md:3218 +msgid "" +"There's a new `matrix_nginx_proxy_data_path` variable, which has a " +"different use-purpose now (it's a subdirectory of " +"`matrix_nginx_proxy_base_path` and is meant for storing various data " +"files)." +msgstr "" + +#: ../../../CHANGELOG.md:3221 +msgid "2019-03-10" +msgstr "" + +#: ../../../CHANGELOG.md:3223 +msgid "Dimension integration manager support" +msgstr "" + +#: ../../../CHANGELOG.md:3225 +msgid "" +"Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can " +"now (optionally) install the [Dimension](https://dimension.t2bot.io/) " +"integration manager. To learn more, see the [Setting up Dimension](docs" +"/configuring-playbook-dimension.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3228 +msgid "2019-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:3230 +msgid "Ability to customize mxisd's email templates" +msgstr "" + +#: ../../../CHANGELOG.md:3232 +msgid "" +"Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's " +"email templates can now be customized easily. To learn more, see the " +"[Customizing email templates](docs/configuring-playbook-mxisd.md" +"#customizing-email-templates) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3235 +msgid "2019-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:3237 +msgid "Discord bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3239 +msgid "" +"[@Lionstiger](https://github.com/Lionstiger) has done some great work " +"adding Discord bridging support via [matrix-appservice-" +"discord](https://github.com/matrix-org/matrix-appservice-discord). To " +"learn more, see the [Setting up Appservice Discord bridging](docs" +"/configuring-playbook-bridge-appservice-discord.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3242 +msgid "2019-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:3244 +msgid "Renaming variables" +msgstr "" + +#: ../../../CHANGELOG.md:3246 ../../../CHANGELOG.md:3563 +#: ../../../CHANGELOG.md:3648 ../../../CHANGELOG.md:3768 +msgid "The following playbook variables were renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3248 +msgid "from `host_specific_hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3249 +msgid "from `hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3250 +msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`" +msgstr "" + +#: ../../../CHANGELOG.md:3251 +msgid "from `hostname_riot` to `matrix_server_fqn_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3252 +msgid "" +"from `host_specific_matrix_ssl_lets_encrypt_support_email` to " +"`matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3254 +msgid "" +"Doing that, we've simplified things, made names less confusing " +"(hopefully) and moved all variable names under the `matrix_` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:3257 +msgid "2019-02-16" +msgstr "" + +#: ../../../CHANGELOG.md:3259 +msgid "Riot v1.0.1 support" +msgstr "" + +#: ../../../CHANGELOG.md:3261 +msgid "You can now use the brand new and redesigned Riot." +msgstr "" + +#: ../../../CHANGELOG.md:3263 +msgid "" +"The new version no longer has a homepage by default, so we've also " +"removed the custom homepage that we've been installing." +msgstr "" + +#: ../../../CHANGELOG.md:3265 +msgid "" +"However, we still provide you with hooks to install your own `home.html` " +"file by specifying the `matrix_riot_web_embedded_pages_home_path` " +"variable (used to be called `matrix_riot_web_homepage_template` before)." +msgstr "" + +#: ../../../CHANGELOG.md:3268 +msgid "2019-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:3270 +msgid "Synapse v0.99.1" +msgstr "" + +#: ../../../CHANGELOG.md:3272 +msgid "" +"As we're moving toward Synapse v1.0, things are beginning to stabilize. " +"Upgrading from v0.99.0 to v0.99.1 should be painless." +msgstr "" + +#: ../../../CHANGELOG.md:3274 +msgid "" +"If you've been overriding the default configuration so that you can " +"terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), " +"you'll now have to replace this custom configuration with " +"`matrix_synapse_tls_federation_listener_enabled: true`. The " +"`matrix_synapse_no_tls` variable is no more." +msgstr "" + +#: ../../../CHANGELOG.md:3277 +msgid "2019-02-06" +msgstr "" + +#: ../../../CHANGELOG.md:3279 +msgid "Synapse v0.99 support and preparation for Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3281 +msgid "" +"Matrix is undergoing a lot of changes as it matures towards Synapse v1.0." +" The first step is the Synapse v0.99 transitional release, which this " +"playbook now supports." +msgstr "" + +#: ../../../CHANGELOG.md:3283 +msgid "" +"If you've been using this playbook successfully until now, you'd be aware" +" that we've been doing [Server Delegation](docs/howto-server-" +"delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring" +" DNS](docs/configuring-dns.md))." +msgstr "" + +#: ../../../CHANGELOG.md:3285 +msgid "" +"Due to changes related to certificate file requirements that will affect " +"us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV " +"record in the future** (when Synapse goes to v1.0 - around 5th of March " +"2019). We **still need to keep the SRV record for now**, for backward " +"compatibility with older Synapse versions (lower than v0.99)." +msgstr "" + +#: ../../../CHANGELOG.md:3287 +msgid "" +"**What you need to do now** is make use of this transitional Synapse " +"v0.99 release to **prepare your federation settings for the future**. You" +" have 2 choices to prepare yourself for compatibility with the future " +"Synapse v1.0:" +msgstr "" + +#: ../../../CHANGELOG.md:3289 +msgid "" +"(recommended) set up [Server Delegation via a well-known file](docs" +"/howto-server-delegation.md#server-delegation-via-a-well-known-file), " +"unless you are affected by the [Downsides of well-known-based Server " +"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" +"based-server-delegation). If you had previously set up the well-known " +"`client` file, depending on how you've done it, it may be that there is " +"nothing new required of you (besides [upgrading](docs/maintenance-" +"upgrading-services.md)). After upgrading, you can [run a self-check](docs" +"/maintenance-checking-services.md), which will tell you if you need to do" +" anything extra with regard to setting up [Server Delegation via a well-" +"known file](docs/howto-server-delegation.md#server-delegation-via-a-well-" +"known-file). After some time, when most people have upgraded to Synapse " +"v0.99 and older releases have disappeared, be prepared to drop your " +"`_matrix._tcp` SRV record." +msgstr "" + +#: ../../../CHANGELOG.md:3291 +msgid "" +"(more advanced) if the [Downsides of well-known-based Server " +"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" +"based-server-delegation) are not to your liking, **as an alternative**, " +"you can set up [Server Delegation via a DNS SRV record](docs/howto-" +"server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In" +" such a case, you get to keep using your existing `_matrix._tcp` DNS SRV " +"record forever and need to NOT set up a `/.well-known/matrix/server` " +"file. Don't forget that you need to do certificate changes though. Follow" +" the guide at [Server Delegation via a DNS SRV record](docs/howto-server-" +"delegation.md#server-delegation-via-a-dns-srv-record-advanced)." +msgstr "" + +#: ../../../CHANGELOG.md:3294 +msgid "2019-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:3296 +msgid "TLS v1.3 support" +msgstr "" + +#: ../../../CHANGELOG.md:3298 +msgid "" +"Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has " +"[added support for TLS v1.3](https://github.com/nginxinc/docker-" +"nginx/issues/190), we have enabled that protocol by default." +msgstr "" + +#: ../../../CHANGELOG.md:3300 +msgid "When using:" +msgstr "" + +#: ../../../CHANGELOG.md:3302 +msgid "" +"the **integrated nginx server**: TLS v1.3 support might not kick in " +"immediately, because the nginx version hasn't been bumped and you may " +"have an older build of the nginx Docker image (currently " +"`nginx:1.15.8-alpine`). Typically, we do not re-pull images that you " +"already have. When the nginx version gets bumped in the future, everyone " +"will get the update. Until then, you could manually force-pull the " +"rebuilt Docker image by running this on the server: `docker pull " +"nginx:1.15.8-alpine`." +msgstr "" + +#: ../../../CHANGELOG.md:3304 +msgid "" +"**your own external nginx server**: if your external nginx server is too " +"old, the new configuration we generate for you in `/matrix/nginx-" +"proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and " +"your nginx version might not support that. You can adjust the SSL " +"protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` " +"variable. Learn more in the documentation page for [Using your own " +"webserver, instead of this playbook's nginx proxy](docs/configuring-" +"playbook-own-webserver.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3306 +msgid "" +"**another web server**: you don't need to do anything to accommodate this" +" change" +msgstr "" + +#: ../../../CHANGELOG.md:3309 +msgid "2019-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:3311 +msgid "IRC bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3313 +msgid "" +"[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some " +"great work bringing IRC bridging support via [matrix-appservice-" +"irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, " +"see the [Setting up Appservice IRC bridging](docs/configuring-playbook-" +"bridge-appservice-irc.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3316 +msgid "2019-01-29" +msgstr "" + +#: ../../../CHANGELOG.md:3318 +msgid "" +"Running container processes as non-root, without capabilities and read-" +"only" +msgstr "" + +#: ../../../CHANGELOG.md:3320 +msgid "" +"To improve security, this playbook no longer starts container processes " +"as the `root` user. Most containers were dropping privileges anyway, but " +"we were trusting them with `root` privileges until they would do that. " +"Not anymore -- container processes now start as a non-root user (usually " +"`matrix`) from the get-go." +msgstr "" + +#: ../../../CHANGELOG.md:3322 +msgid "" +"For additional security, various capabilities are also dropped (see [why " +"it's important](https://github.com/projectatomic/atomic-site/issues/203))" +" for all containers." +msgstr "" + +#: ../../../CHANGELOG.md:3324 +msgid "" +"Additionally, most containers now use a read-only filesystem (see [why " +"it's important](https://www.projectatomic.io/blog/2015/12/making-docker-" +"images-write-only-in-production/)). Containers are given write access " +"only to the directories they need to write to." +msgstr "" + +#: ../../../CHANGELOG.md:3326 +msgid "" +"A minor breaking change is the " +"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` " +"variable having being renamed to " +"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` " +"(note the `_mb` suffix). The new variable expects a number value (e.g. " +"`25M` -> `25`). If you weren't customizing this variable, this wouldn't " +"affect you." +msgstr "" + +#: ../../../CHANGELOG.md:3328 +msgid "matrix-mailer is now based on Exim, not Postfix" +msgstr "" + +#: ../../../CHANGELOG.md:3330 +msgid "" +"While we would have preferred to stay with " +"[Postfix](http://www.postfix.org/), we found out that it cannot run as a " +"non-root user. We've had to replace it with [Exim](https://www.exim.org/)" +" (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" +"relay) container image)." +msgstr "" + +#: ../../../CHANGELOG.md:3332 +msgid "" +"The internal `matrix-mailer` service (running in a container) now listens" +" on port `8025` (used to be `587` before). The playbook will update your " +"Synapse and mxisd email settings to match (`matrix-mailer:587` -> " +"`matrix-mailer:8025`)." +msgstr "" + +#: ../../../CHANGELOG.md:3334 +msgid "" +"Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" +"relay) container image instead of " +"[panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us " +"a nice disk usage reduction (~200MB -> 8MB)." +msgstr "" + +#: ../../../CHANGELOG.md:3337 +msgid "2019-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:3339 +msgid "(BC Break) Making the playbook's roles more independent of one another" +msgstr "" + +#: ../../../CHANGELOG.md:3341 +msgid "" +"The following change **affects people running a more non-standard setup**" +" - external Postgres or using our roles in their own other playbook. " +"**Most users don't need to do anything**, besides becoming aware of the " +"new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-" +"servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3344 +msgid "" +"Because people like using the playbook's components independently " +"(outside of this playbook) and because it's much better for " +"maintainability, we've continued working on separating them. Still, we'd " +"like to offer a turnkey solution for running a fully-featured Matrix " +"server, so this playbook remains important for wiring up the various " +"components." +msgstr "" + +#: ../../../CHANGELOG.md:3346 +msgid "" +"With the new changes, **all roles are now only dependent on the minimal " +"`matrix-base` role**. They are no longer dependent among themselves." +msgstr "" + +#: ../../../CHANGELOG.md:3348 +msgid "" +"In addition, the following components can now be completely disabled (for" +" those who want/need to):" +msgstr "" + +#: ../../../CHANGELOG.md:3349 +msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3350 +msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3351 +msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3353 +msgid "The following changes had to be done:" +msgstr "" + +#: ../../../CHANGELOG.md:3355 +msgid "" +"glue variables had to be introduced to the playbook, so it can wire " +"together the various components. Those glue vars are stored in the " +"[`group_vars/matrix-servers`](group_vars/matrix-servers) file. When " +"overriding variables for a given component (role), you need to be aware " +"of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's " +"corresponding section in the [`group_vars/matrix-servers`](group_vars" +"/matrix-servers) file." +msgstr "" + +#: ../../../CHANGELOG.md:3357 +msgid "" +"`matrix_postgres_use_external` has been superceeded by the more " +"consistently named `matrix_postgres_enabled` variable and a few other " +"`matrix_synapse_database_` variables. See the [Using an external " +"PostgreSQL server (optional)](docs/configuring-playbook-external-" +"postgres.md) documentation page for an up-to-date replacement." +msgstr "" + +#: ../../../CHANGELOG.md:3359 +msgid "" +"Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are " +"no longer installed if you're not enabling the `matrix-postgres` role " +"(`matrix_postgres_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3361 +msgid "" +"roles, being more independent now, are more minimal and do not do so much" +" magic for you. People that are building their own playbook using our " +"roles will definitely need to take a look at the [`group_vars/matrix-" +"servers`](group_vars/matrix-servers) file and adapt their playbooks with " +"the same (or similar) wiring logic." +msgstr "" + +#: ../../../CHANGELOG.md:3364 +msgid "2019-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:3366 +msgid "Splitting the playbook into multiple roles" +msgstr "" + +#: ../../../CHANGELOG.md:3368 +msgid "" +"For better maintainability, the playbook logic (which all used to reside " +"in a single `matrix-server` role) has been split out into a number of " +"different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, " +"`matrix-mxisd`, etc. (see the `roles/` directory)." +msgstr "" + +#: ../../../CHANGELOG.md:3371 +msgid "" +"To keep the filesystem more consistent with this separation, the " +"**Postgres data had to be relocated**." +msgstr "" + +#: ../../../CHANGELOG.md:3373 +msgid "" +"The default value of `matrix_postgres_data_path` was changed from " +"`/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` " +"directory is what we consider a base path now (new variable " +"`matrix_postgres_base_path`). **Your Postgres data files will " +"automatically be relocated by the playbook** (`/matrix/postgres/*` -> " +"`/matrix/postgres/data/`) when you run with `--tags=setup-all` (or " +"`--tags=setup-postgres`). While this shouldn't cause data-loss, **it's " +"better if you do a Postgres backup just in case**. You'd need to restart " +"all services after this migration (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3376 +msgid "2019-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:3378 +msgid "(BC Break) mxisd configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:3380 +msgid "" +"To be more flexible and to support the upcoming " +"[mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released)," +" we've had to redo how mxisd gets configured." +msgstr "" + +#: ../../../CHANGELOG.md:3383 +msgid "The following variables are no longer supported by this playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:3385 +msgid "`matrix_mxisd_ldap_enabled`" +msgstr "" + +#: ../../../CHANGELOG.md:3386 +msgid "`matrix_mxisd_ldap_connection_host`" +msgstr "" + +#: ../../../CHANGELOG.md:3387 +msgid "`matrix_mxisd_ldap_connection_tls`" +msgstr "" + +#: ../../../CHANGELOG.md:3388 +msgid "`matrix_mxisd_ldap_connection_port`" +msgstr "" + +#: ../../../CHANGELOG.md:3389 +msgid "`matrix_mxisd_ldap_connection_baseDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3390 +msgid "`matrix_mxisd_ldap_connection_baseDns`" +msgstr "" + +#: ../../../CHANGELOG.md:3391 ../../../CHANGELOG.md:3392 +msgid "`matrix_mxisd_ldap_connection_bindDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3393 ../../../CHANGELOG.md:3397 +msgid "`matrix_mxisd_ldap_connection_bindPassword`" +msgstr "" + +#: ../../../CHANGELOG.md:3394 +msgid "`matrix_mxisd_ldap_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3395 +msgid "`matrix_mxisd_ldap_attribute_uid_type`" +msgstr "" + +#: ../../../CHANGELOG.md:3396 +msgid "`matrix_mxisd_ldap_attribute_uid_value`" +msgstr "" + +#: ../../../CHANGELOG.md:3398 +msgid "`matrix_mxisd_ldap_attribute_name`" +msgstr "" + +#: ../../../CHANGELOG.md:3399 +msgid "`matrix_mxisd_ldap_attribute_threepid_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3400 +msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`" +msgstr "" + +#: ../../../CHANGELOG.md:3401 +msgid "`matrix_mxisd_ldap_identity_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3402 +msgid "`matrix_mxisd_ldap_identity_medium`" +msgstr "" + +#: ../../../CHANGELOG.md:3403 +msgid "`matrix_mxisd_ldap_auth_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3404 +msgid "`matrix_mxisd_ldap_directory_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3405 +msgid "`matrix_mxisd_template_config`" +msgstr "" + +#: ../../../CHANGELOG.md:3407 +msgid "" +"You are encouraged to use the `matrix_mxisd_configuration_extension_yaml`" +" variable to define your own mxisd configuration additions and overrides." +" Refer to the [default variables file](roles/custom/matrix-" +"mxisd/defaults/main.yml) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:3409 +msgid "This new way of configuring mxisd is beneficial because:" +msgstr "" + +#: ../../../CHANGELOG.md:3411 +msgid "" +"it lets us support all mxisd configuration options, as the playbook " +"simply forwards them to mxisd without needing to care or understand them" +msgstr "" + +#: ../../../CHANGELOG.md:3412 +msgid "" +"it lets you upgrade to newer mxisd versions and make use of their " +"features, without us having to add support for them explicitly" +msgstr "" + +#: ../../../CHANGELOG.md:3415 +msgid "2019-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:3417 +msgid "(BC Break) Cronjob schedule no longer configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3419 +msgid "" +"Due to the way we manage cronjobs now, you can no longer configure the " +"schedule they're invoked at." +msgstr "" + +#: ../../../CHANGELOG.md:3421 +msgid "" +"If you were previously using " +"`matrix_ssl_lets_encrypt_renew_cron_time_definition` or " +"`matrix_nginx_proxy_reload_cron_time_definition` to set a custom " +"schedule, you should note that these variables don't affect anything " +"anymore." +msgstr "" + +#: ../../../CHANGELOG.md:3424 +msgid "" +"If you miss this functionality, please [open an " +"Issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/new) and let us know about your use case!" +msgstr "" + +#: ../../../CHANGELOG.md:3427 +msgid "2018-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:3429 +msgid "(BC Break) More SSL certificate retrieval methods" +msgstr "" + +#: ../../../CHANGELOG.md:3431 +msgid "" +"The playbook now lets you decide between 3 different SSL certificate " +"retrieval methods:" +msgstr "" + +#: ../../../CHANGELOG.md:3432 +msgid "(default) obtaining free SSL certificates from Let's Encrypt" +msgstr "" + +#: ../../../CHANGELOG.md:3433 +msgid "generating self-signed SSL certificates" +msgstr "" + +#: ../../../CHANGELOG.md:3434 +msgid "managing SSL certificates manually" +msgstr "" + +#: ../../../CHANGELOG.md:3436 +msgid "" +"Learn more in [Adjusting SSL certificate retrieval](docs/configuring-" +"playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3438 +msgid "" +"For people who use Let's Encrypt (mostly everyone, since it's the " +"default), you'll also have to rename a variable in your configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:3440 +msgid "before: `host_specific_matrix_ssl_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3441 +msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3443 +msgid "(BC Break) mxisd upgrade with multiple base DN support" +msgstr "" + +#: ../../../CHANGELOG.md:3445 +msgid "" +"mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-" +"matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base " +"DNs](https://github.com/kamax-" +"matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." +msgstr "" + +#: ../../../CHANGELOG.md:3447 +msgid "" +"If you were configuring this playbook's " +"`matrix_mxisd_ldap_connection_baseDn` variable until now (a string " +"containing a single base DN), you'll need to change to configuring the " +"`matrix_mxisd_ldap_connection_baseDns` variable (an array containing " +"multiple base DNs)." +msgstr "" + +#: ../../../CHANGELOG.md:3449 +msgid "Example change:" +msgstr "" + +#: ../../../CHANGELOG.md:3451 +msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`" +msgstr "" + +#: ../../../CHANGELOG.md:3452 +msgid "" +"after: `matrix_mxisd_ldap_connection_baseDns: " +"['OU=Users,DC=example,DC=org']`" +msgstr "" + +#: ../../../CHANGELOG.md:3455 +msgid "2018-12-21" +msgstr "" + +#: ../../../CHANGELOG.md:3457 +msgid "Synapse 0.34.0 and Python 3" +msgstr "" + +#: ../../../CHANGELOG.md:3459 +msgid "" +"Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on " +"feedback from others, running Synapse on Python 3 is supposed to decrease" +" memory usage significantly (~2x)." +msgstr "" + +#: ../../../CHANGELOG.md:3462 +msgid "2018-12-12" +msgstr "" + +#: ../../../CHANGELOG.md:3464 +msgid "Riot homepage customization" +msgstr "" + +#: ../../../CHANGELOG.md:3466 +msgid "" +"You can now customize some parts of the Riot homepage (or even completely" +" replace it with your own custom page). See the " +"`matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-" +"web/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:3469 +msgid "2018-12-04" +msgstr "" + +#: ../../../CHANGELOG.md:3471 +msgid "mxisd extensibility" +msgstr "" + +#: ../../../CHANGELOG.md:3473 +msgid "" +"The [LDAP identity store for mxisd](https://github.com/kamax-" +"matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured " +"easily using playbook variables (see the `matrix_mxisd_ldap_` variables " +"in `roles/custom/matrix-server/defaults/main.yml`)." +msgstr "" + +#: ../../../CHANGELOG.md:3476 +msgid "2018-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:3478 +msgid "More scripts" +msgstr "" + +#: ../../../CHANGELOG.md:3480 +msgid "matrix-remove-all allows to uninstall everything with a single command" +msgstr "" + +#: ../../../CHANGELOG.md:3481 +msgid "matrix-make-user-admin allows to upgrade a user's privileges" +msgstr "" + +#: ../../../CHANGELOG.md:3483 +msgid "LDAP auth support via matrix-synapse-ldap3" +msgstr "" + +#: ../../../CHANGELOG.md:3485 +msgid "" +"The playbook can now install and configure [LDAP auth " +"support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3487 +msgid "" +"Additional details are available in [Setting up the LDAP authentication " +"password provider module](docs/configuring-playbook-ldap-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3490 +msgid "2018-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:3492 +msgid "Support for controlling public registration and room auto-join" +msgstr "" + +#: ../../../CHANGELOG.md:3494 +msgid "" +"The playbook now lets you enable public registration for users " +"(controlled via `matrix_synapse_enable_registration`). By default, public" +" registration is forbidden." +msgstr "" + +#: ../../../CHANGELOG.md:3496 +msgid "" +"You can also make people automatically get auto-joined to rooms " +"(controlled via `matrix_synapse_auto_join_rooms`)." +msgstr "" + +#: ../../../CHANGELOG.md:3498 +msgid "Support for changing the welcome user ID (welcome bot)" +msgstr "" + +#: ../../../CHANGELOG.md:3500 +msgid "" +"By default, `@riot-bot:matrix.org` is used to welcome newly registered " +"users. This can be changed to something else (or disabled) via the new " +"`matrix_riot_web_welcome_user_id` variable." +msgstr "" + +#: ../../../CHANGELOG.md:3503 +msgid "2018-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:3505 +msgid "Ability to set Synapse log levels" +msgstr "" + +#: ../../../CHANGELOG.md:3507 +msgid "" +"The playbook now allows you to set the log levels used by Synapse. The " +"default logging levels remain the same." +msgstr "" + +#: ../../../CHANGELOG.md:3509 +msgid "" +"You can now override following variables with any of the supported log " +"levels listed here: https://docs.python.org/3/library/logging.html" +"#logging-levels" +msgstr "" + +#: ../../../CHANGELOG.md:3518 +msgid "2018-11-03" +msgstr "" + +#: ../../../CHANGELOG.md:3520 +msgid "Customize parts of Riot's config" +msgstr "" + +#: ../../../CHANGELOG.md:3522 +msgid "" +"You can now customize some parts of Riot's `config.json`. These playbook " +"variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:3533 +msgid "" +"This now allows you use a custom integration manager like " +"[Dimension](https://dimension.t2bot.io). For example, if you wish to use " +"the Dimension instance hosted at dimension.t2bot.io, you can set the " +"following in your vars.yml file:" +msgstr "" + +#: ../../../CHANGELOG.md:3542 +msgid "SSL protocols used to serve Riot and Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3544 +msgid "" +"There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, " +"which controls the SSL protocols used to serve Riot and Synapse. Its " +"default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 " +"TLSv1.1 TLSv1.2` to serve Riot and Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:3546 +msgid "" +"You may wish to reenable TLSv1 if you need to access Riot in older " +"browsers." +msgstr "" + +#: ../../../CHANGELOG.md:3548 +msgid "" +"Note: Currently the dockerized nginx doesn't support TLSv1.3. See " +"https://github.com/nginxinc/docker-nginx/issues/190 for more details." +msgstr "" + +#: ../../../CHANGELOG.md:3551 +msgid "2018-11-01" +msgstr "" + +#: ../../../CHANGELOG.md:3553 +msgid "Postgres 11 support" +msgstr "" + +#: ../../../CHANGELOG.md:3555 +msgid "" +"The playbook now installs [Postgres " +"11](https://www.postgresql.org/about/news/1894/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:3557 +msgid "" +"If you have have an existing setup, it's likely running on an older " +"Postgres version (9.x or 10.x). You can easily upgrade by following the " +"[upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" +"postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646 +#: ../../../CHANGELOG.md:3766 +msgid "(BC Break) Renaming playbook variables" +msgstr "" + +#: ../../../CHANGELOG.md:3561 +msgid "" +"Due to the large amount of features added to this playbook lately, to " +"keep things manageable we've had to reorganize its configuration " +"variables a bit." +msgstr "" + +#: ../../../CHANGELOG.md:3565 +msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3566 +msgid "" +"from `matrix_docker_image_mautrix_telegram` to " +"`matrix_mautrix_telegram_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3567 +msgid "" +"from `matrix_docker_image_mautrix_whatsapp` to " +"`matrix_mautrix_whatsapp_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3568 +msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3569 +msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3570 +msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3571 +msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3572 +msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3573 +msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3574 +msgid "" +"from `matrix_docker_image_postgres_v9` to " +"`matrix_postgres_docker_image_v9`" +msgstr "" + +#: ../../../CHANGELOG.md:3575 +msgid "" +"from `matrix_docker_image_postgres_v10` to " +"`matrix_postgres_docker_image_v10`" +msgstr "" + +#: ../../../CHANGELOG.md:3576 +msgid "" +"from `matrix_docker_image_postgres_latest` to " +"`matrix_postgres_docker_image_latest`" +msgstr "" + +#: ../../../CHANGELOG.md:3579 +msgid "2018-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:3581 +msgid "Mautrix Whatsapp bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3583 +msgid "" +"The playbook now supports bridging with " +"[Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-" +"whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This " +"playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3585 +msgid "" +"Additional details are available in [Setting up Mautrix Whatsapp " +"bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3588 +msgid "2018-10-25" +msgstr "" + +#: ../../../CHANGELOG.md:3590 +msgid "Support for controlling Matrix federation" +msgstr "" + +#: ../../../CHANGELOG.md:3592 +msgid "" +"The playbook can now help you with [Controlling Matrix federation](docs" +"/configuring-playbook-federation), should you wish to run a more private " +"(isolated) server." +msgstr "" + +#: ../../../CHANGELOG.md:3595 +msgid "2018-10-24" +msgstr "" + +#: ../../../CHANGELOG.md:3597 +msgid "Disabling riot-web guests" +msgstr "" + +#: ../../../CHANGELOG.md:3599 +msgid "" +"From now on, Riot's configuration setting `disable_guests` would be set " +"to `true`. The homeserver was rejecting guests anyway, so this is just a " +"cosmetic change affecting Riot's UI." +msgstr "" + +#: ../../../CHANGELOG.md:3602 +msgid "2018-10-21" +msgstr "" + +#: ../../../CHANGELOG.md:3604 +msgid "Self-check maintenance command" +msgstr "" + +#: ../../../CHANGELOG.md:3606 +msgid "" +"The playbook can now [check if services are configured correctly](docs" +"/maintenance-checking-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3609 +msgid "2018-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:3611 +msgid "Presence tracking made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3613 +msgid "" +"The playbook can now enable/disable user presence-status tracking in " +"Synapse, through the playbook's `matrix_synapse_use_presence` variable " +"(having a default value of `true` - enabled)." +msgstr "" + +#: ../../../CHANGELOG.md:3615 +msgid "" +"If users participate in large rooms with many other servers, disabling " +"presence will decrease server load significantly." +msgstr "" + +#: ../../../CHANGELOG.md:3618 +msgid "2018-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:3620 +msgid "Synapse Cache Factor made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3622 +msgid "" +"The playbook now makes the Synapse cache factor configurable, through the" +" playbook's `matrix_synapse_cache_factor` variable (having a default " +"value of `0.5`)." +msgstr "" + +#: ../../../CHANGELOG.md:3624 +msgid "" +"Changing that value allows you to potentially decrease RAM usage or to " +"increase performance by caching more stuff. Some information on it is " +"available here: https://github.com/element-hq/synapse#help-synapse-eats-" +"all-my-ram" +msgstr "" + +#: ../../../CHANGELOG.md:3627 +msgid "2018-09-26" +msgstr "" + +#: ../../../CHANGELOG.md:3629 +msgid "Disabling Docker container logging" +msgstr "" + +#: ../../../CHANGELOG.md:3631 +msgid "`--log-driver=none` is used for all Docker containers now." +msgstr "" + +#: ../../../CHANGELOG.md:3633 +msgid "" +"All these containers are started through systemd anyway and get logged in" +" journald, so there's no need for Docker to be logging the same thing " +"using the default `json-file` driver. Doing that was growing " +"`/var/lib/docker/containers/..` infinitely until service/container " +"restart." +msgstr "" + +#: ../../../CHANGELOG.md:3635 +msgid "" +"As a result of this, things like `docker logs matrix-synapse` won't work " +"anymore. `journalctl -u matrix-synapse` is how one can see the logs." +msgstr "" + +#: ../../../CHANGELOG.md:3638 +msgid "2018-09-17" +msgstr "" + +#: ../../../CHANGELOG.md:3640 +msgid "Service discovery support" +msgstr "" + +#: ../../../CHANGELOG.md:3642 +msgid "" +"The playbook now helps you set up [service " +"discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-" +"discovery) using a `/.well-known/matrix/client` file." +msgstr "" + +#: ../../../CHANGELOG.md:3644 +msgid "" +"Additional details are available in [Configuring service discovery via " +".well-known](docs/configuring-well-known.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3650 +msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" +msgstr "" + +#: ../../../CHANGELOG.md:3651 +msgid "" +"from `matrix_riot_web_default_identity_server_url` to " +"`matrix_identity_server_url`" +msgstr "" + +#: ../../../CHANGELOG.md:3654 +msgid "2018-09-07" +msgstr "" + +#: ../../../CHANGELOG.md:3656 +msgid "Mautrix Telegram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3658 +msgid "" +"The playbook now supports bridging with [Telegram](https://telegram.org/)" +" by installing the [mautrix-telegram](https://github.com/tulir/mautrix-" +"telegram) bridge. This playbook functionality is available thanks to " +"[@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3660 +msgid "" +"Additional details are available in [Setting up Mautrix Telegram " +"bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3662 +msgid "Events cache size increase and configurability for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3664 +msgid "" +"The playbook now lets you configure Matrix Synapse's `event_cache_size` " +"configuration via the `matrix_synapse_event_cache_size` playbook " +"variable." +msgstr "" + +#: ../../../CHANGELOG.md:3666 +msgid "" +"Previously, this value was hardcoded to `\"10K\"`. From now on, a more " +"reasonable default of `\"100K\"` is used." +msgstr "" + +#: ../../../CHANGELOG.md:3668 +msgid "Password-peppering support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3670 +msgid "" +"The playbook now supports enabling password-peppering for increased " +"security in Matrix Synapse via the " +"`matrix_synapse_password_config_pepper` playbook variable. Using a " +"password pepper is disabled by default (just like it used to be before " +"this playbook variable got introduced) and is not to be enabled/disabled " +"after initial setup, as that would invalidate all existing passwords." +msgstr "" + +#: ../../../CHANGELOG.md:3672 +msgid "Statistics-reporting support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3674 +msgid "" +"There's now a new `matrix_synapse_report_stats` playbook variable, which " +"controls the `report_stats` configuration option for Matrix Synapse. It " +"defaults to `false`, so no change is required to retain your privacy." +msgstr "" + +#: ../../../CHANGELOG.md:3676 +msgid "" +"If you'd like to start reporting statistics about your homeserver (things" +" like number of users, number of messages sent, uptime, load, etc.) to " +"matrix.org, you can turn on stats reporting." +msgstr "" + +#: ../../../CHANGELOG.md:3679 +msgid "2018-08-29" +msgstr "" + +#: ../../../CHANGELOG.md:3681 +msgid "Changing the way SSL certificates are retrieved" +msgstr "" + +#: ../../../CHANGELOG.md:3683 +msgid "" +"We've been using [acmetool](https://github.com/hlandau/acme) (with the " +"[willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) " +"Docker image) until now." +msgstr "" + +#: ../../../CHANGELOG.md:3685 +msgid "" +"Due to the Docker image being deprecated, and things looking bleak for " +"acmetool's support of the newer ACME v2 API endpoint, we've switched to " +"using [certbot](https://certbot.eff.org/) (with the " +"[certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker " +"image)." +msgstr "" + +#: ../../../CHANGELOG.md:3687 +msgid "" +"Simply re-running the playbook will retrieve new certificates (via " +"certbot) for you. To ensure you don't leave any old files behind, though," +" you'd better do this:" +msgstr "" + +#: ../../../CHANGELOG.md:3689 +msgid "`systemctl stop 'matrix*'`" +msgstr "" + +#: ../../../CHANGELOG.md:3690 +msgid "" +"stop your custom webserver, if you're running one (only affects you if " +"you've installed with `matrix_nginx_proxy_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3691 +msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3692 +msgid "re-run the playbook's [installation](docs/installing.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3693 +msgid "possibly delete `/matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3696 +msgid "2018-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:3698 +msgid "Matrix Corporal support" +msgstr "" + +#: ../../../CHANGELOG.md:3700 +msgid "" +"The playbook can now install and configure [matrix-" +"corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3702 +msgid "" +"Additional details are available in [Setting up Matrix Corporal](docs" +"/configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3705 +msgid "2018-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:3707 +msgid "Matrix Synapse rate limit control variables" +msgstr "" + +#: ../../../CHANGELOG.md:3709 +msgid "" +"The following new variables can now be configured to control Matrix " +"Synapse's rate-limiting (default values are shown below)." +msgstr "" + +#: ../../../CHANGELOG.md:3716 +msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3718 +msgid "" +"The playbook can now install and configure [matrix-synapse-shared-secret-" +"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " +"you." +msgstr "" + +#: ../../../CHANGELOG.md:3720 +msgid "" +"Additional details are available in [Setting up the Shared Secret Auth " +"password provider module](docs/configuring-playbook-shared-secret-" +"auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3723 +msgid "2018-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:3725 +msgid "REST auth support via matrix-synapse-rest-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3727 +msgid "" +"The playbook can now install and configure [matrix-synapse-rest-" +"auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3729 +msgid "" +"Additional details are available in [Setting up the REST authentication " +"password provider module](docs/configuring-playbook-rest-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3731 +msgid "Compression improvements" +msgstr "" + +#: ../../../CHANGELOG.md:3733 +msgid "" +"Shifted Matrix Synapse compression from happening in the Matrix Synapse, " +"to happening in the nginx proxy that's in front of it." +msgstr "" + +#: ../../../CHANGELOG.md:3736 +msgid "" +"Additionally, `riot-web` also gets compressed now (in the nginx proxy), " +"which drops the initial page load's size from 5.31MB to 1.86MB." +msgstr "" + +#: ../../../CHANGELOG.md:3739 +msgid "Disabling some unnecessary Synapse services" +msgstr "" + +#: ../../../CHANGELOG.md:3741 +msgid "The following services are not necessary, so they have been disabled:" +msgstr "" + +#: ../../../CHANGELOG.md:3742 +msgid "on the federation port (8448): the `client` service" +msgstr "" + +#: ../../../CHANGELOG.md:3743 +msgid "" +"on the http port (8008, exposed over 443): the old Angular `webclient` " +"and the `federation` service" +msgstr "" + +#: ../../../CHANGELOG.md:3745 +msgid "" +"Federation runs only on the federation port (8448) now. The Client APIs " +"run only on the http port (8008) now." +msgstr "" + +#: ../../../CHANGELOG.md:3748 +msgid "2018-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:3750 +msgid "mxisd Identity Server support" +msgstr "" + +#: ../../../CHANGELOG.md:3752 +msgid "" +"The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) " +"Identity Server for you by default. Additional details are available in " +"[Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3755 +msgid "2018-08-14" +msgstr "" + +#: ../../../CHANGELOG.md:3757 +msgid "Email-sending support" +msgstr "" + +#: ../../../CHANGELOG.md:3759 +msgid "" +"The playbook now configures an email-sending service (postfix) by " +"default. Additional details are available in [Adjusting email-sending " +"settings](docs/configuring-playbook-email.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3761 +msgid "" +"With this, Matrix Synapse is able to send email notifications for missed " +"messages, etc." +msgstr "" + +#: ../../../CHANGELOG.md:3764 +msgid "2018-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:3770 +msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3771 +msgid "" +"from `matrix_max_log_file_size_mb` to " +"`matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3772 +msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:3773 +msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:3774 +msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`" +msgstr "" + +#: ../../../CHANGELOG.md:3775 +msgid "from `docker_riot_image` to `matrix_docker_image_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3776 +msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`" +msgstr "" + +#: ../../../CHANGELOG.md:3777 +msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" +msgstr "" + +#: ../../../CHANGELOG.md:3779 +msgid "" +"If you're overriding any of them in your `vars.yml` file, you'd need to " +"change to the new names." +msgstr "" + +#: ../../../CHANGELOG.md:3781 +msgid "Renaming Ansible playbook tag" +msgstr "" + +#: ../../../CHANGELOG.md:3783 +msgid "" +"The command for executing the whole playbook has changed. The `setup-" +"main` tag got renamed to `setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:3785 +msgid "Docker container linking" +msgstr "" + +#: ../../../CHANGELOG.md:3787 +msgid "" +"Changed the way the Docker containers are linked together. The ones that " +"need to communicate with others operate in a `matrix` network now and not" +" in the default bridge network." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/README.po b/i18n/locales/jp/LC_MESSAGES/README.po new file mode 100644 index 000000000..b40cd4e22 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/README.po @@ -0,0 +1,1373 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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" + +#: ../../../README.md:1 +msgid "" +"[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-" +"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" +"deploy%3Adevture.com&logo=matrix&style=for-the-" +"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" +"docker-ansible-deploy:devture.com) " +"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgstr "" + +#: ../../../README.md:1 +msgid "Support room on Matrix" +msgstr "" + +#: ../../../README.md:1 +msgid "donate" +msgstr "" + +#: ../../../README.md:3 +msgid "" +"Matrix (An open network for secure, decentralized communication) server " +"setup using Ansible and Docker" +msgstr "" + +#: ../../../README.md:5 +msgid "🎯 Purpose" +msgstr "" + +#: ../../../README.md:7 +msgid "" +"This [Ansible](https://www.ansible.com/) playbook is meant to help you " +"run your own [Matrix](http://matrix.org/) homeserver, along with the " +"[various services](#supported-services) related to that." +msgstr "この [Ansible](https://www.ansible.com/) Playbook は、独自の [Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-services) を実行するのに役立つことを目的としています。" + +#: ../../../README.md:9 +msgid "" +"That is, it lets you join the Matrix network using your own user ID like " +"`@alice:example.com`, all hosted on your own server (see " +"[prerequisites](docs/prerequisites.md))." +msgstr "" + +#: ../../../README.md:11 +msgid "" +"We run all [supported services](#-supported-services) in " +"[Docker](https://www.docker.com/) containers (see [the container images " +"we use](docs/container-images.md)), which lets us have a predictable and " +"up-to-date setup, across multiple supported distros (see " +"[prerequisites](docs/prerequisites.md)) and [architectures](docs" +"/alternative-architectures.md) (x86/amd64 being recommended)." +msgstr "" + +#: ../../../README.md:13 +msgid "" +"Installation (upgrades) and some maintenance tasks are automated using " +"[Ansible](https://www.ansible.com/) (see [our Ansible " +"guide](docs/ansible.md))." +msgstr "" + +#: ../../../README.md:15 +msgid "☁ Self-hosting or Managed / SaaS" +msgstr "" + +#: ../../../README.md:17 +msgid "" +"This Ansible playbook tries to make self-hosting and maintaining a Matrix" +" server fairly easy (see [Getting started](#-getting-started)). Still, " +"running any service smoothly requires knowledge, time and effort." +msgstr "" + +#: ../../../README.md:19 +msgid "" +"If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" +"source_software) spirit of this Ansible playbook, but prefer to put the " +"responsibility on someone else, you can also [get a managed Matrix server" +" from " +"etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" (both hosting and on-premises) - a service built on top of this Ansible " +"playbook but with [additional " +"components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" and " +"[services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" +" which all help you run a Matrix server with ease. Be advised that " +"etke.cc operates on a subscription-based approach and there is no \"just " +"set up my server once and be done with it\" option." +msgstr "" + +#: ../../../README.md:21 +msgid "🚀 Getting started" +msgstr "" + +#: ../../../README.md:23 +msgid "" +"We have detailed documentation in the [docs/](./docs) directory - see the" +" Table of Contents in the [documentation README](./docs/README.md)." +msgstr "" + +#: ../../../README.md:25 +msgid "" +"While the [list of supported services](#-supported-services) and " +"documentation is very extensive, you don't need to read through " +"everything. We recommend:" +msgstr "" + +#: ../../../README.md:27 +msgid "" +"Starting with the basics. You can always add/remove or tweak services " +"later on." +msgstr "" + +#: ../../../README.md:29 +msgid "" +"Following our installation guide. There are two guides available for " +"beginners and advanced users:" +msgstr "" + +#: ../../../README.md:31 +msgid "" +"⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is " +"recommended for those who do not have an existing Matrix server and want " +"to start quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../README.md:33 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide by starting with the " +"**[Prerequisites](./docs/prerequisites.md)** documentation page." +msgstr "" + +#: ../../../README.md:35 +msgid "" +"If you experience an issue on configuring the playbook, setting up your " +"server, maintaining services on it, etc., please take a look at our " +"[FAQ](./docs/faq.md). If you cannot find an answer to your question, feel" +" free to ask for [help and support](#-support)." +msgstr "" + +#: ../../../README.md:37 +msgid "✔ Supported services" +msgstr "" + +#: ../../../README.md:39 +msgid "" +"Using this playbook, you can get the following list of services " +"configured on your server. Basically, this playbook aims to get you up-" +"and-running with all the necessities around Matrix, without you having to" +" do anything else." +msgstr "" + +#: ../../../README.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../README.md:43 +msgid "" +"The list below is exhaustive. It includes optional or even some advanced " +"components that you will most likely not need. Sticking with the defaults" +" (which install a subset of the above components) is the best choice, " +"especially for a new installation. You can always re-run the playbook " +"later to add or remove components." +msgstr "" + +#: ../../../README.md:45 +msgid "" +"Deprecated or unmaintained services are not listed. You can find " +"documentations for them [here](docs/configuring-playbook.md#deprecated--" +"unmaintained--removed-services)." +msgstr "" + +#: ../../../README.md:47 +msgid "Homeserver" +msgstr "" + +#: ../../../README.md:49 +msgid "" +"The homeserver is the backbone of your Matrix system. Choose one from the" +" following list." +msgstr "" + +#: ../../../README.md +msgid "Name" +msgstr "" + +#: ../../../README.md +msgid "Default?" +msgstr "" + +#: ../../../README.md +msgid "Description" +msgstr "" + +#: ../../../README.md +msgid "Documentation" +msgstr "" + +#: ../../../README.md +msgid "[Synapse](https://github.com/element-hq/synapse)" +msgstr "" + +#: ../../../README.md +msgid "✅" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../README.md +msgid "[Conduit](https://conduit.rs)" +msgstr "" + +#: ../../../README.md +msgid "❌" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" +"source server implementation of the Matrix Specification with a focus on " +"easy setup and low system requirements" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../README.md +msgid "[Dendrite](https://github.com/matrix-org/dendrite)" +msgstr "" + +#: ../../../README.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " +"Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../README.md:57 +msgid "Clients" +msgstr "" + +#: ../../../README.md:59 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../README.md +msgid "[Element Web](https://github.com/element-hq/element-web)" +msgstr "" + +#: ../../../README.md +msgid "" +"Default Matrix web client, configured to connect to your own Synapse " +"server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../README.md +msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../README.md +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../README.md +msgid "[Cinny](https://github.com/ajbura/cinny)" +msgstr "" + +#: ../../../README.md +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../README.md +msgid "[SchildiChat Web](https://schildi.chat/)" +msgstr "" + +#: ../../../README.md +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../README.md:68 +msgid "Server Components" +msgstr "" + +#: ../../../README.md:70 +msgid "" +"Services that run on the server to make the various parts of your " +"installation work." +msgstr "" + +#: ../../../README.md +msgid "[PostgreSQL](https://www.postgresql.org/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Database for Synapse. [Using an external PostgreSQL server](docs" +"/configuring-playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../README.md +msgid "[Coturn](https://github.com/coturn/coturn)" +msgstr "" + +#: ../../../README.md +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-turn.md)" +msgstr "" + +#: ../../../README.md +msgid "[Traefik](https://doc.traefik.io/traefik/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Web server, listening on ports 80, 443 and 8448 - standing in front of " +"all the other services. Using your own webserver [is possible](docs" +"/configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../README.md +msgid "[Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../README.md +msgid "Free SSL certificate, which secures the connection to all components" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../README.md +msgid "[Exim](https://www.exim.org/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Mail server, through which all Matrix services send outgoing email (can " +"be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-email.md)" +msgstr "" + +#: ../../../README.md +msgid "[ma1sd](https://github.com/ma1uta/ma1sd)" +msgstr "" + +#: ../../../README.md +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../README.md +msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)" +msgstr "" + +#: ../../../README.md +msgid "Dynamic DNS" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../README.md:82 +msgid "Authentication" +msgstr "" + +#: ../../../README.md:84 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-" +"password-provider) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-" +"synapse-shared-secret-auth) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "Password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-" +"ldap3) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ldap-auth.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" (advanced)" +msgstr "" + +#: ../../../README.md +msgid "" +"A proxy that handles Matrix registration requests and forwards them to " +"LDAP." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)" +msgstr "" + +#: ../../../README.md +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Matrix User Verification Service](https://github.com/matrix-org/matrix-" +"user-verification-service) (UVS)" +msgstr "" + +#: ../../../README.md +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-user-verification-service.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" +"antispam) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "A spam checker module" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)" +msgstr "" + +#: ../../../README.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../README.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../README.md +msgid "[Goofys](https://github.com/kahing/goofys)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " +"store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" +"-storage-provider)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-s3.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)" +msgstr "" + +#: ../../../README.md +msgid "" +"matrix-media-repo is a highly customizable multi-domain media repository " +"for Matrix. Intended for medium to large deployments, this media repo de-" +"duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../README.md:106 +msgid "Bridges" +msgstr "" + +#: ../../../README.md:108 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../README.md +msgid "[mautrix-discord](https://github.com/mautrix/discord)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-slack](https://github.com/mautrix/slack)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-telegram](https://github.com/mautrix/telegram)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-twitter](https://github.com/mautrix/twitter)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-meta](https://github.com/mautrix/instagram)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge to [Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../README.md +msgid "" +"Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-" +"messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-" +"meta-instagram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mautrix-signal](https://github.com/mautrix/signal)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../README.md +msgid "[beeper-linkedin](https://github.com/beeper/linkedin)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-" +"irc)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-discord](https://github.com/matrix-org/matrix-" +"appservice-discord)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-appservice-slack](https://github.com/matrix-org/matrix-" +"appservice-slack)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bridge for generic webhooks and multiple project management services, " +"such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to SMS" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../README.md +msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../README.md +msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)" +msgstr "" + +#: ../../../README.md +msgid "" +"Bouncer-style bridge to " +"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../README.md +msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-" +"discord)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-" +"groupme)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../README.md +msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)" +msgstr "" + +#: ../../../README.md +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../README.md +msgid "[Email2Matrix](https://github.com/devture/email2matrix)" +msgstr "" + +#: ../../../README.md +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../README.md +msgid "[Postmoogle](https://github.com/etkecc/postmoogle)" +msgstr "" + +#: ../../../README.md +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../README.md:141 +msgid "Bots" +msgstr "" + +#: ../../../README.md:143 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../README.md +msgid "[baibot](https://github.com/etkecc/baibot)" +msgstr "" + +#: ../../../README.md +msgid "" +"A bot that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-" +"bot)" +msgstr "" + +#: ../../../README.md +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-registration-bot](https://github.com/moan0s/matrix-registration-" +"bot)" +msgstr "" + +#: ../../../README.md +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../README.md +msgid "[maubot](https://github.com/maubot/maubot)" +msgstr "" + +#: ../../../README.md +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../README.md +msgid "[Honoroit](https://github.com/etkecc/honoroit)" +msgstr "" + +#: ../../../README.md +msgid "A helpdesk bot" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../README.md +msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)" +msgstr "" + +#: ../../../README.md +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../README.md +msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)" +msgstr "" + +#: ../../../README.md +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice " +"mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" +msgstr "" + +#: ../../../README.md +msgid "[Buscarron](https://github.com/etkecc/buscarron)" +msgstr "" + +#: ../../../README.md +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../README.md:156 +msgid "Administration" +msgstr "" + +#: ../../../README.md:158 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../README.md +msgid "" +"[matrix-alertmanager-receiver](https://github.com/metio/matrix-" +"alertmanager-receiver)" +msgstr "" + +#: ../../../README.md +msgid "" +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " +"client" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[Matrix Authentication Service](https://github.com/element-hq/matrix-" +"authentication-service/)" +msgstr "" + +#: ../../../README.md +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)" +msgstr "" + +#: ../../../README.md +msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)" +msgstr "" + +#: ../../../README.md +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../README.md +msgid "Metrics and Graphs" +msgstr "" + +#: ../../../README.md +msgid "" +"Consists of the [Prometheus](https://prometheus.io) time-series database " +"server, the Prometheus [node-exporter](https://prometheus.io/docs/guides" +"/node-exporter/) host metrics exporter, and the " +"[Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-" +"exporter](https://github.com/martin-helmich/prometheus-nginxlog-" +"exporter/) being available too" +msgstr "" + +#: ../../../README.md +msgid "" +"[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-" +"nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" +msgstr "" + +#: ../../../README.md +msgid "[Borg](https://borgbackup.org)" +msgstr "" + +#: ../../../README.md +msgid "Backups" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../README.md +msgid "[rageshake](https://github.com/matrix-org/rageshake)" +msgstr "" + +#: ../../../README.md +msgid "Bug report server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" +"exporter)" +msgstr "" + +#: ../../../README.md +msgid "" +"Export the usage statistics of a Synapse homeserver to be scraped by " +"Prometheus." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../README.md:170 +msgid "Misc" +msgstr "" + +#: ../../../README.md:172 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../README.md +msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../README.md +msgid "" +"(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` " +"and Conduit > `0.6.0`) Sliding Sync support for clients which require it " +"(e.g. old Element X versions before Simplified Sliding Sync was " +"developed)" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-" +"accept-invite)" +msgstr "" + +#: ../../../README.md +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)" +msgstr "" + +#: ../../../README.md +msgid "" +"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" +"compress-state/#automated-tool-synapse_auto_compressor)" +msgstr "" + +#: ../../../README.md +msgid "" +"A cli tool that automatically compresses `state_groups` database table in" +" background." +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../README.md +msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)" +msgstr "" + +#: ../../../README.md +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-matrix-corporal.md)" +msgstr "" + +#: ../../../README.md +msgid "[Etherpad](https://etherpad.org)" +msgstr "" + +#: ../../../README.md +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../README.md +msgid "[Jitsi](https://jitsi.org/)" +msgstr "" + +#: ../../../README.md +msgid "An open source video-conferencing platform" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../README.md +msgid "[Cactus Comments](https://cactus.chat)" +msgstr "" + +#: ../../../README.md +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../README.md +msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)" +msgstr "" + +#: ../../../README.md +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../README.md +msgid "[Sygnal](https://github.com/matrix-org/sygnal)" +msgstr "" + +#: ../../../README.md +msgid "Push gateway" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../README.md +msgid "[ntfy](https://ntfy.sh)" +msgstr "" + +#: ../../../README.md +msgid "Push notifications server" +msgstr "" + +#: ../../../README.md +msgid "[Link](docs/configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../README.md:187 +msgid "🆕 Changes" +msgstr "" + +#: ../../../README.md:189 +msgid "" +"This playbook evolves over time, sometimes with backward-incompatible " +"changes." +msgstr "" + +#: ../../../README.md:191 +msgid "" +"When updating the playbook, refer to [the changelog](CHANGELOG.md) to " +"catch up with what's new." +msgstr "" + +#: ../../../README.md:193 +msgid "🆘 Support" +msgstr "" + +#: ../../../README.md:195 +msgid "" +"Matrix room: [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com)" +msgstr "" + +#: ../../../README.md:197 +msgid "" +"IRC channel: `#matrix-docker-ansible-deploy` on the [Libera " +"Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" +msgstr "" + +#: ../../../README.md:199 +msgid "" +"GitHub issues: [spantaleev/matrix-docker-ansible-" +"deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues)" +msgstr "" + +#: ../../../README.md:215 +msgid "🤝 Related" +msgstr "" + +#: ../../../README.md:217 +msgid "" +"You may also be interested in [mash-playbook](https://github.com/mother-" +"of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" +"hosting non-Matrix services (see its [List of supported " +"services](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/supported-services.md))." +msgstr "" + +#: ../../../README.md:219 +msgid "" +"mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" +"traefik.md) as its reverse-proxy, so with minor [interoperability " +"adjustments](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/interoperability.md), you can make matrix-docker-" +"ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " +"services on the same server." +msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po new file mode 100644 index 000000000..c0d6a2a9f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -0,0 +1,682 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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" + +#: ../../../YEAR-IN-REVIEW.md:1 +msgid "2023" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:3 +msgid "" +"2023 was a year filled with many changes for matrix-docker-ansible-" +"deploy. In this post, we're looking backward at some of the major changes" +" that happened this year, as well as taking a glimpse of what's ahead in " +"2024." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:5 +msgid "" +"2023 is probably [the year of AI](https://journal.everypixel.com/2023" +"-the-year-of-ai), with millions of people jumping aboard " +"[OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) " +"train. matrix-docker-ansible-deploy is no stranger to this and 2023 began" +" with a PR from [bertybuttface](https://github.com/bertybuttface) who " +"added support for [matrix-chatgpt-bot](https://github.com/matrixgpt" +"/matrix-chatgpt-bot) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#chatgpt-support)). While OpenAI's chat GPT website was frequently " +"overloaded in the past, their API was up which made using this bot both " +"convenient and more reliable." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:7 +msgid "" +"AI aside, with the playbook's focus being containers, we're **doubling " +"down on being \"container native\"** and becoming more interoperable for " +"people hosting other containers on the Matrix server. In " +"[2022](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-" +"REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their " +"use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of " +"matrix-docker-ansible-deploy also switching to this reverse-proxy. This " +"prediction materialized quickly. The **largest change** in the playbook " +"in 2023 happened way back in February - matrix-docker-ansible-deploy " +"[starting the switch from nginx to Traefik](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#backward-compatibility-reverse-proxy-configuration-changes-and-initial-" +"traefik-support) and then quickly [making Treafik the default reverse-" +"proxy](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#traefik-is-the-default-reverse-proxy-now). As noted in the changelog " +"entries, we envisioned a quick and complete elimination of `matrix-nginx-" +"proxy`, but at the end of 2023, it hasn't happened yet. The playbook is " +"already using Traefik as the front-most reverse-proxy, but nginx (via " +"`matrix-nginx-proxy`) is still around - it has taken a step back and is " +"only used internally for new setups. Work got to a stall due to:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:9 +msgid "" +"complexity: untangling the overly large and messy `matrix-nginx-proxy` " +"component is difficult" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:10 +msgid "" +"the current setup became \"good enough\" because nginx has become an " +"internal implementation detail for those who have migrated to Traefik. " +"Traefik is already the default public reverse-proxy and gives better " +"possibilities to people wishing to run other web-exposed containers on " +"their Matrix server via [Docker " +"Compose](https://docs.docker.com/compose/), other Ansible playbooks like " +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) (more about this one, below) or any other way." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:12 +msgid "" +"`matrix-nginx-proxy` is no longer in the way of us being interoperable, " +"but its ugly internal details are still there. It is one more proxy in " +"the long chain of reverse-proxies we have and we'd like to cut it out. " +"This would both make things simpler and also boost performance." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:14 +msgid "" +"The delay in eliminating `matrix-nginx-proxy` has probably been welcome " +"by many existing users who decided to postpone the Traefik migration a " +"bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will " +"continue with rapid pace. People who are still using `matrix-nginx-proxy`" +" as their front-most reverse-proxy will need to rework their setup. About" +" a year of putting it off has been long enough." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:16 +msgid "" +"This large Traefik reverse-proxy change was also accompanied by another " +"internal change which began in 2022, but continued in 2023 - **moving " +"non-Matrix-related roles from being internal to the playbook to living " +"their own life outside of it**. Various roles were made more decoupled " +"and moved outside of the playbook, so that other projects (like the " +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) Ansible playbook or other Ansible playbooks) could benefit from" +" them. This led to the **death of a few sibling playbooks** ([gitea-" +"docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy), [nextcloud-docker-ansible-" +"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), " +"[peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-" +"docker-ansible-deploy), [vaultwarden-docker-ansible-" +"deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-" +"deploy)), but brought life to something better, which supports all these " +"services and more." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:18 +msgid "" +"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" +"playbook) is a new Ansible playbook that a few of us (matrix-docker-" +"ansible-deploy contributors) have launched in 2023. It has quickly grown " +"to supports [60+ services](https://github.com/mother-of-all-self-hosting" +"/mash-playbook/blob/main/docs/supported-services.md) and aims to do the " +"same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" +"source_software) service hosting, as matrix-docker-ansible-deploy has " +"done for Matrix - providing a clean and secure way to run a bunch of " +"services in containers on a regular server (that is to say, without " +"Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to" +" host both mash-playbook services and matrix-docker-ansible-deploy " +"services on the same server - see mash-playbook's " +"[interoperability](https://github.com/mother-of-all-self-hosting/mash-" +"playbook/blob/main/docs/interoperability.md) documentation page. If " +"you've been looking for a holiday project or your New Year's Resolutions " +"list contains \"self-hosting more services\", then you're welcome to give" +" this new playbook a try and join its Matrix room ([#mash-" +"playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:20 +msgid "" +"Because many of the roles are now external to this playbook (defined in " +"the [requirements.yml](https://github.com/spantaleev/matrix-docker-" +"ansible-" +"deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) " +"file), running `make roles` (or better yet `just roles` via the [just " +"tool](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#support-for-running-commands-via-just)) becomes a necessity each time " +"one pulls playbook updates (`git pull`). Pulling external roles happens " +"via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli" +"/ansible-galaxy.html) command-line tool, but if available, the playbook " +"would also use the much faster [agru](https://github.com/etkecc/agru) " +"tool (developed by [Aine](https://gitlab.com/etke.cc) from " +"[etke.cc](https://etke.cc/) this year)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:22 +msgid "" +"With the internal (but important) details out of the way, we can now talk" +" more about **new features that landed in matrix-docker-ansible-deploy in" +" 2023**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:24 +msgid "The following **new** **bridges** were added to the playbook in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:26 +msgid "" +"(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a " +"PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#mautrix-slack-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:27 +msgid "" +"(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), " +"thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#mautrix-gmessages-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:28 +msgid "" +"(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for " +"Apple iMessage bridging (when combined with the [mautrix-" +"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" +" or Android phone), thanks to a PR by [Johan " +"Swetzén](https://github.com/jswetzen)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:30 +msgid "" +"This brings the total number of **[bridges that the playbook " +"supports](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-" +"playbook.md#bridging-other-networks) up to 30**. There are alternative " +"bridge implementations for various networks and protocols, so the number " +"of \"unique bridged networks\" is surely much smaller." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:32 +msgid "A few other **major components and changes** landed in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:34 +msgid "" +"(2023-02-10) The [Draupnir](https://github.com/the-draupnir-" +"project/Draupnir) moderation tool (successor to " +"[Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by " +"[FSG-Cat](https://github.com/FSG-Cat) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#draupnir-moderation-tool-bot-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:35 +msgid "" +"(2023-02-10) [Matrix User Verification Service](https://github.com" +"/matrix-org/matrix-user-verification-service) to add Matrix " +"Authentication Support to our Jitsi setup, thanks to a PR by [Jakob " +"S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com" +"/zakk-it) (see the [changelog entry](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" +"authentication-support-for-jitsi))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:36 +msgid "" +"(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug" +" report server, thanks to a PR by [Benjamin " +"Kampmann](https://github.com/gnunicorn) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#rageshake-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:37 +msgid "" +"(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-" +"sync) (currently a necessary component for [Element " +"X](https://element.io/labs/element-x) to work), thanks to: [Benjamin " +"Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com" +"/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#sliding-sync-proxy-element-x-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:38 +msgid "" +"(2023-03-12) synapse-auto-compressor to periodically and automatically " +"run [rust-synapse-compress-state](https://github.com/matrix-org/rust-" +"synapse-compress-state), thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#synapse-auto-compressor-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:39 +msgid "" +"(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-" +"media-repo),  thanks to a PR by [Michael Hollister](https://github.com" +"/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of " +"the [Circles app](https://circu.li/) (see the [changelog " +"entry](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" +"media-repo-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:40 +msgid "" +"(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat" +"/schildichat-desktop) client app (fork of [Element " +"Web)](https://github.com/element-hq/element-web), thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#schildichat-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:41 +msgid "" +"(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#postgres-parameters-are-automatically-tuned-now))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:42 +msgid "" +"(2023-10-23) Enabling federation of the room directory for Synapse (see " +"the [changelog entry](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:44 +msgid "" +"The most recent change in the list above (Enabling federation of the room" +" directory for Synapse) has been somewhat **controversial** as it goes " +"against upstream defaults for Synapse. Nevertheless, we believe it " +"**promotes the well-being of the Matrix Federation by improving room " +"discovery**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:46 +msgid "" +"**Matrix Federation Stats** (containing the percentage of servers " +"publishing their room directory publicly) are posted to " +"[TWIM](https://matrix.org/category/this-week-in-matrix/) each week by " +"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The " +"number of servers which [currently published their room directory " +"publicly](https://matrix.org/blog/2023/12/2/this-week-in-" +"matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:48 +msgid "" +"**2.4% more** than when it was when [first published to " +"TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03" +"/#matrix-federation-stats) (1 month earlier, in November)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:49 +msgid "" +"likely about **15+% more** than from before we flipped the switch (in " +"October)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:51 +msgid "" +"Hopefully, Synapse defaults would also change the same way and we'd see " +"the number of servers publicly listing their room directory grow faster." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:53 +msgid "" +"With this configuration change in place, projects like " +"[MatrixRooms.info](https://matrixrooms.info/) (made by " +"[etke.cc](https://etke.cc/)) and potentially others in the future, can " +"discover, index the metadata (room address, title, topic, number of " +"users, etc.) and make public rooms browsable & searchable across the " +"whole Matrix Federation. It'd be great if users joining Matrix could more" +" easily find interesting communities that match their interests!" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:55 +msgid "" +"On the **media side of things**, besides Jitsi getting better Matrix " +"integration (via the aforementioned Matrix User Verification Service), " +"we've also had some [Coturn security " +"tightening](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" +"#backward-compatibility-tightening-coturn-security-can-lead-to-" +"connectivity-issues) as well as [performance " +"optimizations](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-" +"can-now-use-host-networking) for configurations exposing lots of network " +"ports." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:57 +msgid "" +"[Element Call](https://github.com/element-hq/element-call) seems to have " +"become a nice and polished product lately (as proclaimed in [The Matrix " +"Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-" +"holiday-update-2023/)), so 2024 is likely the year we'll see support for " +"it in the playbook. Element Call depends on the " +"[LiveKit](https://livekit.io/) streaming server (which is also useful to " +"developers even by itself), so the first step is likely to see LiveKit " +"support in mash-playbook via a reusable Ansible role. Such a LiveKit " +"Ansible role could later easily land in matrix-docker-ansible-deploy and " +"an Element Call static website could be hooked to it." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:59 +msgid "" +"Besides these highlights, there were many other relatively large changes " +"announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-" +"ansible-" +"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and " +"hundreds of other more minor (but still important) playbook changes that " +"didn't get a mention." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:61 +msgid "" +"We have **hundreds of contributors to thank for their hard work** on " +"making Matrix self-hosting better for all of us! It should be noted that " +"**support comes in many shapes**, not only in raw code commits and " +"financial help (via [donations](https://liberapay.com/s.pantaleev) or " +"using the [etke.cc managed Matrix hosting service](https://etke.cc/) " +"which is based on matrix-docker-ansible-deploy). It also comes in the " +"shape of code reviews, helping others with " +"[issues](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues), reporting new issues, participating in our support room " +"on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to" +"/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has " +"been there to make matrix-docker-ansible-deploy better in 2023, thank " +"you! 🙇‍♂️" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:64 +msgid "2022" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:66 +msgid "" +"For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/), 2022 started with **breaking the** " +"[**Synapse**](https://github.com/element-hq/synapse) **monopoly** by " +"[adding support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#dendrite-support) for the [Dendrite](https://github.com/matrix-" +"org/dendrite) Matrix homeserver in early January. This required various " +"internal changes so that the [Ansible](https://www.ansible.com/) playbook" +" would not be Synapse-centric anymore. This groundwork paved the way for " +"continuing in this direction and we [added " +"support](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#conduit-support) for [Conduit](https://conduit.rs/) in August." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:68 +msgid "" +"When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, " +"2022 was the year of the non-Synapse homeserver implementation. In " +"practice, none of these homeserver implementations seem ready for prime-" +"time yet and there is no migration path when coming from Synapse. Having " +"done our job of adding support for these alternative homeserver " +"implementations, we can say that we're not getting in the way of future " +"progress. It's time for the Dendrite developers to push harder " +"(development-wise) and for the Synapse developers to take a well-deserved" +" long (infinite) break, and we may get to see more people migrating away " +"from Synapse in the next year(s)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:70 +msgid "Support for the following new **bridges** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:72 +msgid "" +"[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#postmoogle-email-bridge-support) for bi-directional email bridging, " +"which supersedes my old and simplistic " +"[email2matrix](https://github.com/devture/email2matrix) one-way bridge-" +"bot" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:73 +msgid "" +"[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#mautrix-discord-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:74 +msgid "" +"[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-" +"skype-bridge-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:75 +msgid "" +"[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"appservice-kakaotalk-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:77 +msgid "Support for the following new **bots** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:79 +msgid "" +"[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#buscarron-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:80 +msgid "" +"[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#honoroit-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:81 +msgid "" +"[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#matrix-registration-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:82 +msgid "" +"[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"hookshot-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:83 +msgid "" +"[maubot](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-" +"support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:85 +msgid "Support for the following new **components and services** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:87 +msgid "" +"[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-" +"backup-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:88 +msgid "" +"[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-" +"comments-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:89 +msgid "" +"[Cinny](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-" +"support) client support" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:90 +msgid "" +"[ntfy](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-" +"push-notifications-support) notifications" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:91 +msgid "" +"[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" +"ldap-registration-proxy-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:92 +msgid "" +"[matrix\\_encryption\\_disabler support](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#matrix_encryption_disabler-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:93 +msgid "" +"[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-" +"docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3" +"-storage-provider-support) to stop the Synapse media store from being a " +"scalability problem. This brought along [another " +"feature](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#synapse-container-image-customization-support) - an easier way to " +"customize the Synapse container image without having to fork and self-" +"build all of it from scratch" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:95 +msgid "" +"Besides these major user-visible changes, a lot of work also happened " +"**under the hood**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:97 +msgid "" +"we made [major improvements to Synapse " +"workers](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#potential-backward-compatibility-break-major-improvements-to-synapse-" +"workers) - adding support for stream writers and for running multiple " +"workers of various kinds (federation senders, pushers, background task " +"processing workers, etc.)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:98 +msgid "" +"we [improved the compatibility of (Synapse + workers) with the rest of " +"the playbook](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-" +"works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by " +"introducing a new `matrix-synapse-reverse-proxy-companion-service` " +"service" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:99 +msgid "" +"we started [splitting various Ansible roles out of the Matrix playbook " +"and into independent roles](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" +"#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-" +"postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-" +"self-hosting/ansible-role-postgres)), which could be included in other " +"Ansible playbooks. In fact, these roles already power a few **interesting" +" other sibling playbooks**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:100 +msgid "" +"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" +"ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted " +"[Git](https://git-scm.com/) service) server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:101 +msgid "" +"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" +"/nextcloud-docker-ansible-deploy), for deploying a " +"[Nextcloud](https://nextcloud.com/) groupware server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:102 +msgid "" +"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" +"/vaultwarden-docker-ansible-deploy), for deploying a " +"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) password " +"manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible" +" server)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:104 +msgid "" +"These sibling playbooks co-exist nicely with one another due to using " +"[Traefik](https://traefik.io/) for reverse-proxying, instead of trying to" +" overtake the whole server by running their own " +"[nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix " +"playbook will follow suit and be powered by Traefik by default." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:106 +msgid "" +"Last, but not least, to optimize our [etke.cc managed Matrix hosting " +"service](https://etke.cc/)'s performance (but also individual Ansible " +"playbook runs for people self-hosting by themselves using the playbook), " +"we've [improved playbook runtime 2-5x](https://github.com/spantaleev" +"/matrix-docker-ansible-" +"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-" +"performance-improvements-in-playbook-runtime) by employing various " +"Ansible tricks." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/README.po b/i18n/locales/jp/LC_MESSAGES/docs/README.po new file mode 100644 index 000000000..893ee1477 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/README.po @@ -0,0 +1,211 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/README.md:1 +msgid "Table of Contents" +msgstr "" + +#: ../../../docs/README.md:3 +msgid "" +"⬇️ Installaton guides " +msgstr "" + +#: ../../../docs/README.md:5 +msgid "" +"There are two installation guides available for beginners and advanced " +"users." +msgstr "" + +#: ../../../docs/README.md:7 +msgid "" +"⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended " +"for those who do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/README.md:9 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide." +msgstr "" + +#: ../../../docs/README.md:11 +msgid "[Prerequisites](prerequisites.md)" +msgstr "" + +#: ../../../docs/README.md:13 +msgid "[Configuring your DNS settings](configuring-dns.md)" +msgstr "" + +#: ../../../docs/README.md:15 +msgid "[Getting the playbook](getting-the-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:17 +msgid "[Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:19 +msgid "[Installing](installing.md)" +msgstr "" + +#: ../../../docs/README.md:21 +msgid "🛠️ Configuration options" +msgstr "" + +#: ../../../docs/README.md:28 +msgid "" +"You can check useful documentation for configuring components here: " +"[Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:30 +msgid "" +"[Administration](configuring-playbook.md#administration) - services that " +"help you in administrating and monitoring your Matrix installation" +msgstr "" + +#: ../../../docs/README.md:32 +msgid "" +"[Authentication and user-related](configuring-playbook.md#authentication-" +"and-user-related) - extend and modify how users are authenticated on your" +" homeserver" +msgstr "" + +#: ../../../docs/README.md:34 +msgid "" +"[Bots](configuring-playbook.md#bots) - bots provide various additional " +"functionality to your installation" +msgstr "" + +#: ../../../docs/README.md:36 +msgid "" +"[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can " +"be used to connect your Matrix installation with third-party " +"communication networks" +msgstr "" + +#: ../../../docs/README.md:38 +msgid "" +"[Clients](configuring-playbook.md#clients) - web clients for Matrix that " +"you can host on your own domains" +msgstr "" + +#: ../../../docs/README.md:40 +msgid "" +"[Core service adjustments](configuring-playbook.md#core-service-" +"adjustments) - backbone of your Matrix system" +msgstr "" + +#: ../../../docs/README.md:42 +msgid "" +"[File Storage](configuring-playbook.md#file-storage) - use alternative " +"file storage to the default `media_store` folder" +msgstr "" + +#: ../../../docs/README.md:46 +msgid "" +"[Other specialized services](configuring-playbook.md#other-specialized-" +"services) - various services that don't fit any other categories" +msgstr "" + +#: ../../../docs/README.md:48 +msgid "👨‍🔧 Maintenance" +msgstr "" + +#: ../../../docs/README.md:50 +msgid "" +"If your server and services experience issues, feel free to come to [our " +"support room](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com) and ask for help." +msgstr "" + +#: ../../../docs/README.md:54 +msgid "[Checking if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/README.md:56 +msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" +msgstr "" + +#: ../../../docs/README.md:58 +msgid "[PostgreSQL maintenance](maintenance-postgres.md)" +msgstr "" + +#: ../../../docs/README.md:60 +msgid "[Synapse maintenance](maintenance-synapse.md)" +msgstr "" + +#: ../../../docs/README.md:62 +msgid "[Upgrading services](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/README.md:64 +msgid "" +"Other documentation pages " +msgstr "" + +#: ../../../docs/README.md:66 +msgid "" +"ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, " +"with a focus on this Ansible playbook" +msgstr "" + +#: ../../../docs/README.md:70 +msgid "[Alternative architectures](alternative-architectures.md)" +msgstr "" + +#: ../../../docs/README.md:72 +msgid "[Container images used by the playbook](container-images.md)" +msgstr "" + +#: ../../../docs/README.md:74 +msgid "[Obtaining an Access Token](obtaining-access-tokens.md)" +msgstr "" + +#: ../../../docs/README.md:76 +msgid "[Playbook tags](playbook-tags.md)" +msgstr "" + +#: ../../../docs/README.md:78 +msgid "[Registering users](registering-users.md)" +msgstr "" + +#: ../../../docs/README.md:80 +msgid "[Running `just` commands](just.md)" +msgstr "" + +#: ../../../docs/README.md:82 +msgid "[Self-building](self-building.md)" +msgstr "" + +#: ../../../docs/README.md:84 +msgid "[Uninstalling](uninstalling.md)" +msgstr "" + +#: ../../../docs/README.md:86 +msgid "[Updating users passwords](updating-users-passwords.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po new file mode 100644 index 000000000..5c7c21550 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po @@ -0,0 +1,77 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/alternative-architectures.md:1 +msgid "Alternative architectures" +msgstr "" + +#: ../../../docs/alternative-architectures.md:3 +msgid "" +"As stated in the [Prerequisites](prerequisites.md), currently only " +"`amd64` (`x86_64`) is fully supported." +msgstr "" + +#: ../../../docs/alternative-architectures.md:5 +msgid "" +"The playbook automatically determines the target server's architecture " +"(the `matrix_architecture` variable) to be one of the following:" +msgstr "" + +#: ../../../docs/alternative-architectures.md:7 +msgid "`amd64` (`x86_64`)" +msgstr "" + +#: ../../../docs/alternative-architectures.md:8 +msgid "`arm32`" +msgstr "" + +#: ../../../docs/alternative-architectures.md:9 +msgid "`arm64`" +msgstr "" + +#: ../../../docs/alternative-architectures.md:11 +msgid "" +"Some tools and container images can be built on the host or other " +"measures can be used to install on that architecture." +msgstr "" + +#: ../../../docs/alternative-architectures.md:13 +msgid "Implementation details" +msgstr "" + +#: ../../../docs/alternative-architectures.md:15 +msgid "" +"For `amd64`, prebuilt container images (see the [container images we use" +"](container-images.md)) are used for all components (except [Hydrogen" +"](configuring-playbook-client-hydrogen.md), which goes through self-" +"building)." +msgstr "" + +#: ../../../docs/alternative-architectures.md:17 +msgid "" +"For other architecture (`arm64`, `arm32`), components which have a " +"prebuilt image make use of it. If the component is not available for the " +"specific architecture, [self-building](self-building.md) will be used. " +"Not all components support self-building though, so your mileage may " +"vary." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po new file mode 100644 index 000000000..aa6d88c72 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po @@ -0,0 +1,283 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/ansible.md:2 +msgid "Running this playbook" +msgstr "" + +#: ../../../docs/ansible.md:4 +msgid "" +"This playbook is meant to be run using " +"[Ansible](https://www.ansible.com/)." +msgstr "" + +#: ../../../docs/ansible.md:6 +msgid "" +"Ansible typically runs on your local computer and carries out tasks on a " +"remote server. If your local computer cannot run Ansible, you can also " +"run Ansible on some server somewhere (including the server you wish to " +"install to)." +msgstr "" + +#: ../../../docs/ansible.md:8 +msgid "Supported Ansible versions" +msgstr "" + +#: ../../../docs/ansible.md:10 +msgid "" +"To manually check which version of Ansible you're on, run: `ansible " +"--version`." +msgstr "" + +#: ../../../docs/ansible.md:12 +msgid "" +"For the **best experience**, we recommend getting the **latest version of" +" Ansible available**." +msgstr "" + +#: ../../../docs/ansible.md:14 +msgid "" +"We're not sure what's the minimum version of Ansible that can run this " +"playbook successfully. The lowest version that we've confirmed (on " +"2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined " +"with `ansible` (`4.10.0`)." +msgstr "" + +#: ../../../docs/ansible.md:16 +msgid "" +"If your distro ships with an Ansible version older than this, you may run" +" into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using " +"Ansible via Docker](#using-ansible-via-docker)." +msgstr "" + +#: ../../../docs/ansible.md:18 +msgid "Upgrading Ansible" +msgstr "" + +#: ../../../docs/ansible.md:20 +msgid "" +"Depending on your distribution, you may be able to upgrade Ansible in a " +"few different ways:" +msgstr "" + +#: ../../../docs/ansible.md:22 +msgid "" +"by using an additional repository (PPA, etc.), which provides newer " +"Ansible versions. See instructions for " +"[CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-rhel-centos-or-fedora), " +"[Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-debian), or " +"[Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" +"#installing-ansible-on-ubuntu) on the Ansible website." +msgstr "" + +#: ../../../docs/ansible.md:24 +msgid "" +"by removing the Ansible package (`yum remove ansible` or `apt-get remove " +"ansible`) and installing via " +"[pip](https://pip.pypa.io/en/stable/installation/) (`pip install " +"ansible`)." +msgstr "" + +#: ../../../docs/ansible.md:26 +msgid "" +"If using the `pip` method, do note that the `ansible-playbook` binary may" +" not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-" +"variable), but in some more special location like `/usr/local/bin" +"/ansible-playbook`. You may need to invoke it using the full path." +msgstr "" + +#: ../../../docs/ansible.md:28 +msgid "" +"**Note**: Both of the above methods are a bad way to run system software " +"such as Ansible. If you find yourself needing to resort to such hacks, " +"please consider reporting a bug to your distribution and/or switching to " +"a sane distribution, which provides up-to-date software." +msgstr "" + +#: ../../../docs/ansible.md:30 +msgid "Using Ansible via Docker" +msgstr "" + +#: ../../../docs/ansible.md:32 +msgid "" +"Alternatively, you can run Ansible inside a Docker container (powered by " +"the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker " +"image)." +msgstr "" + +#: ../../../docs/ansible.md:34 +msgid "" +"This ensures that you're using a very recent Ansible version, which is " +"less likely to be incompatible with the playbook." +msgstr "" + +#: ../../../docs/ansible.md:36 +msgid "" +"You can either [run Ansible in a container on the Matrix server itself" +"](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run " +"Ansible in a container on another computer (not the Matrix server" +")](#running-ansible-in-a-container-on-another-computer-not-the-matrix-" +"server)." +msgstr "" + +#: ../../../docs/ansible.md:38 +msgid "Running Ansible in a container on the Matrix server itself" +msgstr "" + +#: ../../../docs/ansible.md:40 +msgid "" +"To run Ansible in a (Docker) container on the Matrix server itself, you " +"need to have a working Docker installation. Docker is normally installed " +"by the playbook, so this may be a bit of a chicken and egg problem. To " +"solve it:" +msgstr "" + +#: ../../../docs/ansible.md:42 +msgid "" +"you **either** need to install Docker manually first. Follow [the " +"upstream instructions](https://docs.docker.com/engine/install/) for your " +"distribution and consider setting " +"`matrix_playbook_docker_installation_enabled: false` in your `vars.yml` " +"file, to prevent the playbook from installing Docker" +msgstr "" + +#: ../../../docs/ansible.md:43 +msgid "" +"**or** you need to run the playbook in another way (e.g. [Running Ansible" +" in a container on another computer (not the Matrix server)](#running-" +"ansible-in-a-container-on-another-computer-not-the-matrix-server)) at " +"least the first time around" +msgstr "" + +#: ../../../docs/ansible.md:45 +msgid "" +"Once you have a working Docker installation on the server, **clone the " +"playbook** somewhere on the server and configure it as per usual " +"(`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in " +"[configuring the playbook](configuring-playbook.md)." +msgstr "" + +#: ../../../docs/ansible.md:47 +msgid "" +"You would then need to add `ansible_connection=community.docker.nsenter` " +"to the host line in `inventory/hosts`. This tells Ansible to connect to " +"the \"remote\" machine by switching Linux namespaces with " +"[nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead " +"of using SSH." +msgstr "" + +#: ../../../docs/ansible.md:49 +msgid "" +"Alternatively, you can leave your `inventory/hosts` as is and specify the" +" connection type in **each** `ansible-playbook` call you do later, like " +"this: `ansible-playbook --connection=community.docker.nsenter …`" +msgstr "" + +#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 +msgid "Run this from the playbook's directory:" +msgstr "" + +#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 +msgid "" +"Once you execute the above command, you'll be dropped into a `/work` " +"directory inside a Docker container. The `/work` directory contains the " +"playbook's code." +msgstr "" + +#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 +msgid "" +"First, consider running `git config --global --add safe.directory /work` " +"to [resolve directory ownership issues](#resolve-directory-ownership-" +"issues)." +msgstr "" + +#: ../../../docs/ansible.md:67 +msgid "" +"Finally, you can execute `ansible-playbook …` (or `ansible-playbook " +"--connection=community.docker.nsenter …`) commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:69 +msgid "Running Ansible in a container on another computer (not the Matrix server)" +msgstr "" + +#: ../../../docs/ansible.md:82 +msgid "" +"The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into " +"the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different" +" path (not in `$HOME/.ssh/id_rsa`), adjust that part." +msgstr "" + +#: ../../../docs/ansible.md:88 +msgid "Finally, you execute `ansible-playbook …` commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:90 +msgid "If you don't use SSH keys for authentication" +msgstr "" + +#: ../../../docs/ansible.md:92 +msgid "" +"If you don't use SSH keys for authentication, simply remove that whole " +"line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." +msgstr "" + +#: ../../../docs/ansible.md:94 +msgid "" +"To authenticate at your server using a password, you need to add a " +"package. So, when you are in the shell of the ansible docker container " +"(the previously used `docker run -it …` command), run:" +msgstr "" + +#: ../../../docs/ansible.md:100 +msgid "" +"Then, to be asked for the password whenever running an `ansible-" +"playbook` command add `--ask-pass` to the arguments of the command." +msgstr "" + +#: ../../../docs/ansible.md:102 +msgid "Resolve directory ownership issues" +msgstr "" + +#: ../../../docs/ansible.md:104 +msgid "" +"Because you're `root` in the container running Ansible and this likely " +"differs fom the owner (your regular user account) of the playbook " +"directory outside of the container, certain playbook features which use " +"`git` locally may report warnings such as:" +msgstr "" + +#: ../../../docs/ansible.md:106 +msgid "" +"fatal: unsafe repository ('/work' is owned by someone else) To add an " +"exception for this directory, call: git config --global --add " +"safe.directory /work" +msgstr "" + +#: ../../../docs/ansible.md:110 +msgid "" +"These errors can be resolved by making `git` trust the playbook directory" +" by running `git config --global --add safe.directory /work`" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po new file mode 100644 index 000000000..4e8c8d222 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po @@ -0,0 +1,92 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-captcha.md:1 +msgid "" +"(Adapted from the [upstream project](https://github.com/element-" +"hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" +msgstr "" + +#: ../../../docs/configuring-captcha.md:3 +msgid "Overview" +msgstr "" + +#: ../../../docs/configuring-captcha.md:5 +msgid "" +"Captcha can be enabled for this home server. This file explains how to do" +" that." +msgstr "" + +#: ../../../docs/configuring-captcha.md:7 +msgid "" +"The captcha mechanism used is Google's " +"[ReCaptcha](https://www.google.com/recaptcha/). This requires API keys " +"from Google. If your homeserver is Dendrite then " +"[hCapcha](https://www.hcaptcha.com) can be used instead." +msgstr "" + +#: ../../../docs/configuring-captcha.md:9 +msgid "ReCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:11 +#: ../../../docs/configuring-captcha.md:37 +msgid "Getting keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:13 +#: ../../../docs/configuring-captcha.md:39 +msgid "Requires a site/secret key pair from:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:15 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:17 +msgid "" +"Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox " +"option" +msgstr "" + +#: ../../../docs/configuring-captcha.md:19 +msgid "Setting ReCaptcha keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:21 +msgid "" +"Once registered as above, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:35 +msgid "hCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:41 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:43 +msgid "Setting hCaptcha keys" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po new file mode 100644 index 000000000..d53ffdd1d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po @@ -0,0 +1,409 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dns.md:1 +msgid "Configuring your DNS settings" +msgstr "" + +#: ../../../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:5 +msgid "To set up Matrix on your domain, you'd need to do some DNS configuration." +msgstr "" + +#: ../../../docs/configuring-dns.md:7 +msgid "DNS setting for server delegation (optional)" +msgstr "" + +#: ../../../docs/configuring-dns.md:9 +msgid "" +"In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " +"we recommend to use a short user ID like `@alice:example.com` instead of " +"`@alice:matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-dns.md:11 +msgid "" +"To use such an ID, you don't need to install anything on the actual " +"`example.com` server. Instead, you need to instruct the Matrix network " +"that Matrix services for `example.com` are redirected over to " +"`matrix.example.com`. This redirection is also known as \"delegation\"." +msgstr "" + +#: ../../../docs/configuring-dns.md:13 +msgid "" +"As we discuss in [Server Delegation](howto-server-delegation.md), server " +"delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-dns.md:15 +msgid "" +"Setting up a `/.well-known/matrix/server` file on the base domain " +"(`example.com`)" +msgstr "" + +#: ../../../docs/configuring-dns.md:16 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-dns.md:18 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file, instead of using a " +"DNS SRV record." +msgstr "" + +#: ../../../docs/configuring-dns.md:20 +msgid "" +"If you choose the recommended method (file-based delegation), you do not " +"need to configure the DNS record to enable server delegation. You will " +"need to add a necessary configuration later, when you [finalize the " +"installation](installing.md#finalize-the-installation) after installing " +"and starting Matrix services." +msgstr "" + +#: ../../../docs/configuring-dns.md:22 +msgid "" +"On the other hand, if you choose this method (setting up a DNS SRV " +"record), you need to configure the additional DNS record as well as " +"adjust SSL certificate handling. Take a look at this documentation for " +"more information: [Server Delegation via a DNS SRV record (advanced" +")](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-" +"advanced)" +msgstr "" + +#: ../../../docs/configuring-dns.md:24 +msgid "DNS settings for services enabled by default" +msgstr "" + +#: ../../../docs/configuring-dns.md:26 +msgid "" +"To serve the base domain (`example.com`) and [Element Web](configuring-" +"playbook-client-element-web.md) with the default subdomain, adjust DNS " +"records as below." +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Type" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Host" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Priority" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Weight" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Port" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Target" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "A" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "CNAME" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`element`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/configuring-dns.md:33 +msgid "" +"As the table illustrates, you need to create 2 subdomains " +"(`matrix.example.com` and `element.example.com`) and point both of them " +"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/configuring-dns.md:35 +msgid "" +"The `element.example.com` subdomain is necessary, because this playbook " +"installs the [Element Web](https://github.com/element-hq/element-web) " +"client for you by default. If you'd rather instruct the playbook not to " +"install Element Web (`matrix_client_element_enabled: false` when " +"[Configuring the playbook](configuring-playbook.md) later), feel free to " +"skip the `element.example.com` DNS record." +msgstr "" + +#: ../../../docs/configuring-dns.md:37 +msgid "Be mindful as to how long it will take for the DNS records to propagate." +msgstr "" + +#: ../../../docs/configuring-dns.md:39 +msgid "" +"If you are using Cloudflare DNS, make sure to disable the proxy and set " +"all records to \"DNS only\". Otherwise, fetching certificates will fail." +msgstr "" + +#: ../../../docs/configuring-dns.md:41 +msgid "DNS settings for optional services/features" +msgstr "" + +#: ../../../docs/configuring-dns.md:43 +msgid "" +"For other services which may need subdomain settings, see the table below" +" and configure the DNS (`CNAME`) records accordingly." +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "Used by component" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Dimension](configuring-playbook-dimension.md) integration server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`dimension`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`jitsi`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "" +"[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) " +"monitoring system" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`stats`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`goneb`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`sygnal`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`ntfy`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`etherpad`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`hydrogen`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Cinny](configuring-playbook-client-cinny.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`cinny`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`schildichat`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`wsproxy`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`buscarron`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[rageshake](configuring-playbook-rageshake.md) bug report server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`rageshake`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "SRV" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`_matrix-identity._tcp`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "10" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "0" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "443" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "" +"[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix" +"](configuring-playbook-email2matrix.md) email bridges" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "MX" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "TXT" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`v=spf1 ip4:matrix-server-IP -all`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`_dmarc.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`v=DMARC1; p=quarantine;`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "`postmoogle._domainkey.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md +msgid "get it from `!pm dkim`" +msgstr "" + +#: ../../../docs/configuring-dns.md:66 +msgid "SRV record for ma1sd" +msgstr "" + +#: ../../../docs/configuring-dns.md:68 +msgid "" +"To make ma1sd enable its federation features, you need to set up a " +"`_matrix-identity._tcp` SRV record. Don't confuse this with the " +"`_matrix._tcp` SRV record for server delegation. See the table above and " +"[this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for " +"values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:70 +msgid "" +"When setting up a SRV record, if you are asked for a service and protocol" +" instead of a hostname split the host value from the table where the " +"period is. For example use service as `_matrix-identity` and protocol as " +"`_tcp`." +msgstr "" + +#: ../../../docs/configuring-dns.md:72 +msgid "MX and TXT records for Postmoogle" +msgstr "" + +#: ../../../docs/configuring-dns.md:74 +msgid "" +"To make Postmoogle enable its email sending features, you need to " +"configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above " +"for values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:78 +msgid "" +"[▶️](getting-the-playbook.md) When you're done with the DNS configuration" +" and ready to proceed, continue with [Getting the playbook](getting-the-" +"playbook.md)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po new file mode 100644 index 000000000..eb7387679 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po @@ -0,0 +1,251 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-alertmanager-receiver.md:1 +msgid "" +"Setting up Prometheus Alertmanager integration via matrix-alertmanager-" +"receiver (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 +msgid "" +"The playbook can install and configure the [matrix-alertmanager-" +"receiver](https://github.com/metio/matrix-alertmanager-receiver) service " +"for you. It's a " +"[client](https://prometheus.io/docs/alerting/latest/clients/) for " +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)," +" allowing you to deliver alerts to Matrix rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 +msgid "" +"See the project's [documentation](https://github.com/metio/matrix-" +"alertmanager-receiver) to learn more about what this component does and " +"why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 +msgid "" +"At the moment, **setting up this service's bot requires some manual " +"actions** as described below in [Account and room preparation](#account-" +"and-room-preparation)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +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:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 +msgid "" +"To enable matrix-alertmanager-receiver, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:36 +msgid "" +"See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " +"additional configuration variables." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +msgid "Adjusting the matrix-alertmanager-receiver URL" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +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:42 +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:44 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the matrix-alertmanager-receiver domain to the " +"Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 +msgid "Account and room preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 +msgid "" +"The playbook can automatically create users, but it cannot automatically " +"obtain access tokens, nor perform any of the other manual actions below." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 +msgid "" +"`matrix-alertmanager-receiver` uses a bot (with a username specified in " +"`matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see " +"above) for delivering messages. You need to **manually register this bot " +"acccount and obtain an access token for it**." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 +msgid "" +"[Register a new user](registering-users.md): `ansible-playbook -i " +"inventory/hosts setup.yml --extra-" +"vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT " +"admin=no' --tags=register-user`" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 +msgid "" +"[Obtain an access token](obtaining-access-tokens.md) for the bot's user " +"account" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 +msgid "Invite the bot to a room where you'd like to alerts to be delivered" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 +msgid "" +"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:70 +msgid "" +"(Optionally) Adjust " +"`matrix_alertmanager_receiver_config_matrix_room_mapping` to create a " +"mapping between the new room and its ID" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 +msgid "" +"Steps 1 and 2 above only need to be done once, while preparing your " +"[configuration](#adjusting-the-playbook-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 +msgid "" +"Steps 3 and 4 need to be done for each new room you'd like the bot to " +"deliver alerts to. Step 5 is optional and provides cleaner `/alert/` " +"URLs." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +msgid "" +"Now that you've [prepared the bot account and room](#account-and-room-" +"preparation), [configured the playbook](#adjusting-the-playbook-" +"configuration), and potentially [adjusted your DNS records](#adjusting-" +"dns-records), you can run the playbook with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +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:89 +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:91 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"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:93 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +msgid "Configure your Prometheus Alertmanager with configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 +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:116 +msgid "" +"This bot does **not** accept room invitations automatically (like many " +"other bots do). To deliver messages to rooms, **the bot must be joined to" +" all rooms manually** - see Step 4 of the [Account and room preparation" +"](#account-and-room-preparation) section." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po new file mode 100644 index 000000000..55a27cd93 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po @@ -0,0 +1,107 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-appservice-double-puppet.md:1 +msgid "Setting up Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 +msgid "" +"Appservice Double Puppet is a homeserver appservice through which bridges" +" (and potentially other services) can impersonate any user on the " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 +msgid "" +"This is useful for performing [double-" +"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via" +" the [appservice method](https://docs.mau.fi/bridges/general/double-" +"puppeting.html#appservice-method-new). The Appservice Double Puppet " +"service is an implementation of this approach." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 +msgid "" +"Previously, bridges supported performing [double-" +"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"with the help of the [Shared Secret Auth password provider module" +"](./configuring-playbook-shared-secret-auth.md), but this old and hacky " +"solution has been superseded by this Appservice Double Puppet method." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 +msgid "" +"To enable the Appservice Double Puppet service, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 +msgid "" +"When enabled, double puppeting will automatically be enabled for all " +"bridges that support double puppeting via the appservice method." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po new file mode 100644 index 000000000..88f283561 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po @@ -0,0 +1,297 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-appservice-draupnir-for-all.md:1 +msgid "Setting up Draupnir for All/D4A (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 +msgid "" +"The playbook can install and configure the [Draupnir](https://github.com" +"/the-draupnir-project/Draupnir) moderation tool for you in appservice " +"mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 +msgid "" +"Appservice mode can be used together with the regular [Draupnir bot" +"](configuring-playbook-bot-draupnir.md) or independently. Details about " +"the differences between the 2 modes are described below." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 +msgid "Draupnir Appservice mode compared to Draupnir bot mode" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 +msgid "" +"The administrative functions for managing the appservice are alpha " +"quality and very limited. However, the experience of using an appservice-" +"provisioned Draupnir is on par with the experience of using Draupnir from" +" bot mode except in the case of avatar customisation as described later " +"on in this document." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 +msgid "" +"Draupnir for all is the way to go if you need more than 1 Draupnir " +"instance, but you don't need access to Synapse Admin features as they are" +" not accessible through Draupnir for All (Even though the commands do " +"show up in help)." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 +msgid "" +"Draupnir for all in the playbook is rate-limit-exempt automatically as " +"its appservice configuration file does not specify any rate limits." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 +msgid "" +"Normal Draupnir does come with the benefit of access to Synapse Admin " +"features. You are also able to more easily customise your normal Draupnir" +" than D4A as D4A even on the branch with the Avatar command (To be " +"Upstreamed to Mainline Draupnir) that command is clunky as it requires " +"the use of things like Element Web devtools. In normal Draupnir this is a" +" quick operation where you login to Draupnir with a normal client and set" +" Avatar and Display name normally." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 +msgid "" +"Draupnir for all does not support external tooling like " +"[MRU](https://mru.rory.gay) as it can't access Draupnir's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 +msgid "Installation" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 +msgid "Create a main management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 +msgid "" +"The playbook does not create a management room for your Main Draupnir. " +"This task you have to do on your own." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 +msgid "" +"The management room has to be given an alias and be public when you are " +"setting up the bot for the first time as the bot does not differentiate " +"between invites and invites to the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 +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:29 +msgid "" +"As noted in the Draupnir install instructions the control room is " +"sensitive. The following is said about the control room in the Draupnir " +"install instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +msgid "" +"Anyone in this room can control the bot so it is important that you only " +"invite trusted users to this room. The room must be unencrypted since the" +" playbook does not support installing Pantalaimon yet." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 +msgid "Give your main management room an alias." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 +msgid "" +"Give the room from step 1 an alias. This alias can be anything you want " +"and its recommended for increased security during the setup phase of the " +"bot that you make this alias be a random string. You can give your room a" +" secondary human readable alias when it has been locked down after setup " +"phase." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 +msgid "Adjusting the playbook configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:40 +msgid "" +"You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created" +" in step 2." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md: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-appservice-draupnir-for-all.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-appservice-draupnir-for-all.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 +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:69 +msgid "" +"The installation of Draupnir for all in this playbook is very much Alpha " +"quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot " +"mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +msgid "Granting Users the ability to use D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +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:75 +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:77 +msgid "" +"To allow users or whole homeservers you type /plain @draupnir-" +"main:example.com allow `target` and target can be either a MXID or a " +"wildcard like `@*:example.com` to allow all users on example.com to " +"register. We use /plain to force the client to not attempt to mess with " +"this command as it can break Wildcard commands especially." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 +msgid "How to provision a D4A once you are allowed to." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 +msgid "" +"Open a DM with @draupnir-main:example.com and if using an Element client " +"send a message into this DM to finalise creating it. The bot will reject " +"this invite and you will shortly get invited to the Draupnir control room" +" for your newly provisioned Draupnir. From here its just a normal " +"Draupnir experience." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +msgid "" +"Congratulations if you made it all the way here because you now have a " +"fully working Draupnir for all deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 +msgid "Configuration of D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 +msgid "" +"You can refer to the upstream [documentation](https://github.com/the-" +"draupnir-project/Draupnir) for more configuration documentation. Please " +"note that the playbook ships a full copy of the example config that does " +"transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in " +"the template directory of the role." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 +msgid "" +"Please note that Config extension does not affect the appservices config " +"as this config is not extensible in current Draupnir anyways. Config " +"extension instead touches the config passed to the Draupnirs that your " +"Appservice creates. So for example below makes all provisioned Draupnirs " +"protect all joined rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 +msgid "" +"You can configure additional options by adding the " +"`matrix_appservice_draupnir_for_all_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 +msgid "" +"For example to change Draupnir's `protectAllJoinedRooms` option to `true`" +" you would add the following to your `vars.yml` file." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po new file mode 100644 index 000000000..0a847ec70 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po @@ -0,0 +1,215 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-backup-borg.md:1 +msgid "Setting up BorgBackup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:3 +msgid "" +"The playbook can install and configure " +"[BorgBackup](https://www.borgbackup.org/) (short: Borg) with " +"[borgmatic](https://torsion.org/borgmatic/) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:5 +msgid "" +"BorgBackup is a deduplicating backup program with optional compression " +"and encryption. That means your daily incremental backups can be stored " +"in a fraction of the space and is safe whether you store it at home or on" +" a cloud service." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:7 +msgid "" +"You will need a remote server where BorgBackup will store the backups. " +"There are hosted, BorgBackup compatible solutions available, such as " +"[BorgBase](https://www.borgbase.com)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:9 +msgid "" +"The backup will run based on `backup_borg_schedule` var (systemd timer " +"calendar), default: 4am every day." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:11 +msgid "" +"By default, if you're using the integrated Postgres database server (as " +"opposed to [an external Postgres server](configuring-playbook-external-" +"postgres.md)), backups with BorgBackup will also include dumps of your " +"Postgres database. An alternative solution for backing up the Postgres " +"database is [postgres backup](configuring-playbook-postgres-backup.md). " +"If you decide to go with another solution, you can disable Postgres-" +"backup support for BorgBackup using the `backup_borg_postgresql_enabled` " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:13 +msgid "" +"**Note**: the component is not managed by this repository but its [own " +"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" +"backup_borg)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:15 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:17 +msgid "" +"If you do not disable Postgres-backup support, make sure that the " +"Postgres version of your homeserver's database is compatible with " +"borgmatic." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:19 +msgid "Create a new SSH key:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:25 +msgid "" +"This can be done on any machine and you don't need to place the key in " +"the `.ssh` folder. It will be added to the Ansible config later." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:27 +msgid "" +"Add the **public** part of this SSH key (the `matrix-borg-backup.pub` " +"file) to your BorgBackup provider/server:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:29 +msgid "" +"If you plan to use a hosted solution, follow their instructions. If you " +"have your own server, copy the key over:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:39 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:41 +msgid "" +"Minimal working configuration " +"(`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:58 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:60 +msgid "USER - SSH user of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:61 +msgid "HOST - SSH host of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:62 +msgid "" +"REPO - BorgBackup repository name, it will be initialized on backup " +"start, eg: `matrix`, regarding Syntax see [Remote " +"repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html" +"#repository-urls)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:63 +msgid "" +"PASSPHRASE - passphrase used for encrypting backups, you may generate it " +"with `pwgen -s 64 1` or use any password manager" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:64 +msgid "" +"PRIVATE KEY - the content of the **private** part of the SSH key you " +"created before. The whole key (all of its belonging lines) under " +"`backup_borg_ssh_key_private` needs to be indented with 2 spaces" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:66 +msgid "" +"To backup without encryption, add `backup_borg_encryption: 'none'` to " +"your vars. This will also enable the " +"`backup_borg_unknown_unencrypted_repo_access_is_ok` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:68 +msgid "" +"`backup_borg_location_source_directories` defines the list of directories" +" to back up: it's set to `{{ matrix_base_data_path }}` by default, which " +"is the base directory for every service's data, such as Synapse, Postgres" +" and the bridges. You might want to exclude certain directories or file " +"patterns from the backup using the " +"`backup_borg_location_exclude_patterns` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:70 +msgid "" +"Check the [backup_borg role](https://github.com/mother-of-all-self-" +"hosting/ansible-role-backup_borg)'s " +"[defaults/main.yml](https://github.com/mother-of-all-self-hosting" +"/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full " +"list of available options." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:74 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:81 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:83 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:85 +msgid "Manually start a backup" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:87 +msgid "" +"For testing your setup it can be helpful to not wait until 4am. If you " +"want to run the backup immediately, log onto the server and run " +"`systemctl start matrix-backup-borg`. This will not return until the " +"backup is done, so possibly a long time. Consider using " +"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " +"unstable." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po new file mode 100644 index 000000000..9f55db746 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po @@ -0,0 +1,240 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-base-domain-serving.md:1 +msgid "Serving the base domain (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:3 +msgid "" +"By default, this playbook sets up services on your Matrix server " +"(`matrix.example.com`), but has it configured so that it presents itself " +"as the base domain (`example.com`). To have this server officially be " +"responsible for Matrix services for the base domain (`example.com`), you " +"need to set up server delegation / redirection." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:5 +msgid "" +"As we discuss in [Server Delegation](howto-server-delegation.md), server " +"delegation / redirection can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:7 +msgid "" +"Setting up a `/.well-known/matrix/server` file on the base domain " +"(`example.com`)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:8 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:10 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:12 +msgid "" +"However, those who don't have a separate server to dedicate to the base " +"domain have trouble arranging this." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:14 +msgid "Usually, there are 2 options:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:16 +msgid "" +"either get a separate server for the base domain, just for serving the " +"files necessary for [Server Delegation via a well-known file](howto-" +"server-delegation.md#server-delegation-via-a-well-known-file)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:18 +msgid "" +"or, arrange for the Matrix server to serve the base domain. This either " +"involves you [using your own webserver](configuring-playbook-own-" +"webserver.md) or making the integrated webserver serve the base domain " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:20 +msgid "" +"This documentation page tells you how to do the latter. With some easy " +"changes, we make it possible to serve the base domain from the Matrix " +"server via the integrated webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:22 +msgid "" +"Just [**adjust your DNS records**](configuring-dns.md), so that your base" +" domain is pointed to the Matrix server's IP address (using a DNS `A` " +"record) **and then add the following configuration** to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:28 +msgid "Doing this, the playbook will:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:30 +msgid "" +"obtain an SSL certificate for the base domain, just like it does for all " +"other domains (see [how we handle SSL certificates](configuring-playbook-" +"ssl-certificates.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:32 +msgid "" +"serve the `/.well-known/matrix/*` files which are necessary for " +"[Federation Server Discovery](configuring-well-known.md#federation-" +"server-discovery) (also see [Server Delegation](howto-server-" +"delegation.md)) and [Client-Server discovery](configuring-well-known.md" +"#client-server-discovery)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:34 +msgid "" +"serve a simple homepage at `https://example.com` with content `Hello from" +" example.com` (configurable via the " +"`matrix_static_files_file_index_html_template` variable). You can also " +"[serve a more complicated static website](#serving-a-static-website-at-" +"the-base-domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:36 +msgid "Serving a static website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:38 +msgid "" +"By default, when \"serving the base domain\" is enabled, the playbook " +"hosts a simple `index.html` webpage at `/matrix/static-" +"files/public/index.html`. The content of this page is taken from the " +"`matrix_static_files_file_index_html_template` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:40 +msgid "" +"If you'd like to host your own static website (more than a single " +"`index.html` page) at the base domain, you can disable the creation of " +"this default `index.html` page like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:54 +msgid "" +"With this configuration, Ansible will no longer mess around with the " +"`/matrix/static-files/public/index.html` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:56 +msgid "" +"You are then free to upload any static website files to `/matrix/static-" +"files/public` and they will get served at the base domain. You can do so " +"manually or by using the [ansible-role-aux](https://github.com/mother-of-" +"all-self-hosting/ansible-role-aux) Ansible role, which is part of this " +"playbook already." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:58 +msgid "Serving a more complicated website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:60 +msgid "" +"If you'd like to serve an even more complicated (dynamic) website from " +"the Matrix server, relying on the playbook to serve the base domain is " +"not the best choice." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:62 +msgid "You have 2 options." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:64 +msgid "**One way is to host your base domain elsewhere**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:65 +msgid "" +"you stopping to serve it from the Matrix server: remove " +"`matrix_static_files_container_labels_base_domain_enabled` from your " +"configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:66 +msgid "" +"[configuring Matrix Delegation via well-known](./configuring-well-" +"known.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:68 +msgid "" +"**Another way is to serve the base domain from another (your own) " +"container on the Matrix server**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:69 +msgid "" +"telling the playbook to only serve `example.com/.well-known/matrix` files" +" by adjusting your `vars.yml` configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:70 +msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:71 +msgid "" +"add an extra: " +"`matrix_static_files_container_labels_base_domain_traefik_path_prefix: " +"/.well-known/matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:72 +msgid "building and running a new container on the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:73 +msgid "" +"it should be connected to the `traefik` network, so that Traefik can " +"reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:74 +msgid "" +"it should have appropriate [container " +"labels](https://docs.docker.com/config/labels-custom-metadata/), which " +"instruct Traefik to reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:76 +msgid "" +"How you'll be managing building and running this container is up-to-you. " +"You may use of the primitives from [ansible-role-aux](https://github.com" +"/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it" +" yourself, or you can set it up in another way." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po new file mode 100644 index 000000000..97e8bacc6 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -0,0 +1,687 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-baibot.md:1 +msgid "Setting up baibot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:8 +msgid "" +"🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a " +"[Matrix](https://matrix.org/) bot developed by " +"[etke.cc](https://etke.cc/) that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you. 🤖" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:10 +msgid "" +"It supports [OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other" +" [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:12 +msgid "" +"It's designed as a more private and [✨ " +"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" +"file#-features) alternative to [matrix-chatgpt-bot](./configuring-" +"playbook-bot-chatgpt.md). See the " +"[baibot](https://github.com/etkecc/baibot) project and its documentation " +"for more information." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:14 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:16 +msgid "" +"API access to one or more LLM [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:20 +msgid "" +"There are **a lot of configuration options** (some required, some " +"possibly required, some optional), so they're **split into multiple " +"sections below**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:23 +msgid "[Base configuration](#base-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:24 +msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:25 +msgid "[👥 Initial users configuration](#-initial-users-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:26 +msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:27 +msgid "" +"[🤝 Configuring initial default handlers](#-configuring-initial-default-" +"handlers)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:29 +msgid "" +"Depending on your current `vars.yml` file and desired configuration, " +"**you may require more than just the [base configuration](#base-" +"configuration)**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:31 +msgid "Base configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:33 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:71 +msgid "" +"As mentioned above, **this may not be enough**. Continue with the " +"configuration sections below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:73 +msgid "👮‍♂️ Administrator configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:75 +#: ../../../docs/configuring-playbook-bot-baibot.md:99 +msgid "This is an addition to the [base configuration](#base-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:77 +msgid "" +"To specify who is considered a bot [👮‍♂️ " +"Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators)," +" you either need to specify " +"`matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The " +"latter is a single variable which affects all bridges and bots." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:79 +msgid "" +"If `matrix_admin` is already configured in your `vars.yml` configuration," +" you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:81 +#: ../../../docs/configuring-playbook-bot-baibot.md:110 +msgid "" +"**If necessary**, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:95 +msgid "👥 Initial users configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:97 +msgid "" +"By default, **all users on your homeserver are considered allowed " +"users**. If that's OK, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:101 +msgid "" +"To specify who is considered a bot [👥 " +"User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), " +"you may:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:103 +msgid "" +"define an **initial** value for " +"`matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible " +"variable, as shown below" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:104 +msgid "" +"configure the list at runtime via the bot's `!bai access set-users " +"SPACE_SEPARATED_PATTERNS` command" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:106 +msgid "" +"Configuring " +"`matrix_bot_baibot_config_initial_global_config_user_patterns` is " +"optional, but it can be useful to pre-configure the bot with a list of " +"users who should have access to the bot's features." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:108 +msgid "" +"**Note**: Once initially configured, the allowed users list **cannot be " +"managed via Ansible anymore**. It can only be managed subsequently via " +"bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:122 +msgid "🤖 Configuring agents via Ansible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:124 +msgid "" +"You are **not required** to define agents " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration) via Ansible. **To get started quickly**, you can " +"**skip this section and define agents at runtime via chat commands** " +"(following the bot's guidance)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:126 +msgid "" +"Privileged users (like the [👮‍♂️ Administrator](#️-administrator-" +"configuration), but potentially others too - see the upstream [🔒 " +"access](https://github.com/etkecc/baibot/blob/main/docs/access.md) " +"documentation) can **define agents dynamically at any time** via chat " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:128 +msgid "" +"The Ansible role includes preset variables for easily enabling some [🤖 " +"agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on " +"various [☁️ " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " +"(e.g. OpenAI, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:130 +msgid "" +"Besides the presets, the Ansible role also includes support for " +"configuring additional statically-defined agents via the " +"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:132 +msgid "" +"Agents defined statically and those created dynamically (via chat) are " +"named differently, so **conflict cannot arise**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:134 +msgid "" +"Depending on your propensity for " +"[GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to " +"define agents statically via Ansible, or you may wish to do it " +"dynamically via chat." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:136 +msgid "" +"Before proceeding, we recommend reading the upstream documentation on " +"[How to choose a " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#how-to-choose-a-provider). In short, it's probably best to go with " +"[OpenAI](#openai)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:138 +msgid "Anthropic" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:140 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [Anthropic " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:142 +#: ../../../docs/configuring-playbook-bot-baibot.md:168 +#: ../../../docs/configuring-playbook-bot-baibot.md:201 +#: ../../../docs/configuring-playbook-bot-baibot.md:231 +msgid "Here's an example **addition** to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:160 +#: ../../../docs/configuring-playbook-bot-baibot.md:193 +#: ../../../docs/configuring-playbook-bot-baibot.md:221 +#: ../../../docs/configuring-playbook-bot-baibot.md:251 +msgid "" +"If you'd like to use more than one model, take a look at the [Configuring" +" additional agents (without a preset)](#configuring-additional-agents-" +"without-a-preset) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:162 +#: ../../../docs/configuring-playbook-bot-baibot.md:195 +#: ../../../docs/configuring-playbook-bot-baibot.md:223 +#: ../../../docs/configuring-playbook-bot-baibot.md:253 +msgid "" +"💡 You may also wish to use this new agent for [🤝 Configuring initial " +"default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:164 +msgid "Groq" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:166 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [Groq " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:191 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/groq`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:197 +msgid "Mistral" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:199 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [🇫🇷 Mistral " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:219 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/mistral`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:225 +msgid "OpenAI" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:227 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [OpenAI " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai)" +" with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:229 +msgid "" +"The OpenAI provider is **only meant to be used with OpenAI's official " +"API** and compatibility with other services (which do not fully adhere to" +" the OpenAI API spec completely) is limited. **If you're targeting an " +"OpenAI-compatible service**, use the [OpenAI Compatible](#openai-" +"compatible) provider instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:249 +msgid "" +"Because this is a " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agent, it will be given a `static/` ID " +"prefix and will be named `static/openai`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:255 +msgid "OpenAI Compatible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:257 +msgid "" +"You can statically-define a single [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " +"instance powered by the [OpenAI Compatible " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#openai-compatible) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:259 +msgid "" +"This provider allows you to use OpenAI-compatible API services like " +"[OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter)," +" [Together " +"AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#together-ai), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:261 +msgid "" +"Some of these popular services already have **shortcut** providers (see " +"[supported " +"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md" +"#supported-providers) leading to this one behind the scenes - this make " +"it easier to get started." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:263 +msgid "" +"As of this moment, the playbook does not include presets for any of these" +" services, so you'll need to [Configuring additional agents (without a " +"preset)](#configuring-additional-agents-without-a-preset)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:265 +msgid "Configuring additional agents (without a preset)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:267 +msgid "" +"The Ansible role may be lacking preset variables for some [☁️ " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), " +"or you may wish to statically-define an agent on the same provider twice " +"(or more) with different configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:269 +msgid "" +"It's possible to inject your own agent configuration using the " +"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " +"variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:271 +msgid "" +"You can also define providers at runtime, by chatting with the bot, so " +"using Ansible is not a requirement." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:273 +msgid "" +"Below is an an **example** demonstrating **statically-defining agents via" +" Ansible without using presets**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:312 +msgid "" +"Because these are " +"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" +"#static-configuration)-defined agents, they will be given a `static/` ID " +"prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and " +"`static/my-ollama-agent`, respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:314 +msgid "" +"💡 To figure out what to put in the `config` section, refer to the [☁️ " +"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " +"page, which contains **sample configuration YAML for each provider**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:316 +msgid "" +"As with any [🤖 " +"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), " +"defining them means they exist. To actually make use of them, they need " +"to be configured as handlers globally or in a specific room - see [Mixing" +" & matching " +"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" +"--matching-models)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:318 +msgid "" +"💡 You may also wish to use these new agents for [🤝 Configuring initial " +"default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:320 +msgid "🤝 Configuring initial default handlers" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:322 +msgid "" +"This section is only useful if you're [🤖 Configuring agents via Ansible" +"](#-configuring-agents-via-ansible), as it lets you put these agents to " +"use as soon as the bot starts (by adjusting the bot's **initial global " +"configuration**)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:324 +msgid "If you're not configuring agents via Ansible, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:326 +msgid "" +"This section is only useful the first time around. **Once initially " +"configured the global configuration cannot be managed Ansible**, but only" +" via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:328 +msgid "" +"baibot supports [various " +"purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:330 +msgid "" +"[💬 text-" +"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-text-generation): communicating with you via text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:332 +msgid "" +"[🦻 speech-to-" +"text](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-speech-to-text): turning your voice messages into text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:334 +msgid "" +"[🗣️ text-to-" +"speech](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-text-to-speech): turning bot or users text messages into voice messages" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:336 +msgid "" +"[🖌️ image-" +"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" +"#-image-generation): generating images based on instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:338 +msgid "" +"❓ catch-all: special purposes, indicating use as a fallback (when no " +"specific handler is configured)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:340 +msgid "" +"[Mixing & matching " +"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" +"--matching-models) is made possible by the bot's ability to have " +"different [🤝 " +"handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md)" +" configured for different purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:342 +msgid "" +"This configuration can be done as a global fallback, or per-room. Both of" +" these [🛠️ " +"configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md)" +" are managed at runtime (viat chat), but **the global configuration can " +"have some initial defaults configured via Ansible**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:344 +msgid "" +"You can configure the **initial values** for these via Ansible, via the " +"`matrix_bot_baibot_config_initial_global_config_handler_*` variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:346 +msgid "Example **additional** `vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:363 +msgid "" +"**Note**: these are initial defaults for the bot's global configuration. " +"As such, changing any of these values subsequently has no effect on the " +"bot's behavior. **Once initially configured the global configuration " +"cannot be managed Ansible**, but only via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:365 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:367 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:374 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:376 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:378 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:380 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:382 +msgid "" +"If you change the bot password (`matrix_bot_baibot_config_user_password` " +"in your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_baibot_config_user_password` to let the bot know its new " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:384 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:386 +msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:388 +msgid "" +"If you're an allowed bot [👥 " +"user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) " +"(see [👥 Initial users configuration](#-initial-users-configuration)), the" +" bot will accept your invitation and join the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:390 +msgid "" +"After joining, the bot will introduce itself and show information about " +"the [✨ " +"features](https://github.com/etkecc/baibot/blob/main/docs/features.md) " +"that are enabled for it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:392 +msgid "" +"If you've [🤖 configured one or more agents via Ansible](#-configuring-" +"agents-via-ansible) and have [🤝 configured initial default handlers" +"](#configuring-initial-default-handlers), the bot will immediately be " +"able to make use of these agents for this new room. Otherwise, you will " +"need to configure agents and/or handlers via chat commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:394 +msgid "" +"Send `!bai help` to the room at any time to see the bot's help menu for " +"additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:396 +msgid "" +"You can also refer to the upstream " +"[baibot](https://github.com/etkecc/baibot) project's documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:398 +msgid "Debugging" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:400 +msgid "" +"As with all other services, you can find service logs in [systemd-" +"journald](https://www.freedesktop.org/software/systemd/man/systemd-" +"journald.service.html) by running something like `journalctl -fu matrix-" +"bot-baibot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:402 +msgid "" +"The default logging level for this service is `info`, but you can " +"increase it to `debug` (or even `trace`) with the following additional " +"configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:416 +msgid "" +"**Alternatively**, you can use a single variable to set the logging level" +" for all of the above (bot + all libraries):" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po new file mode 100644 index 000000000..f919880a6 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -0,0 +1,187 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-buscarron.md:1 +msgid "Setting up Buscarron (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:3 +msgid "" +"The playbook can install and configure " +"[Buscarron](https://github.com/etkecc/buscarron) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:5 +msgid "" +"Buscarron is bot that receives HTTP POST submissions of web forms and " +"forwards them to a Matrix room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:9 +msgid "" +"To enable Buscarron, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:32 +msgid "Adjusting the Buscarron URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:34 +msgid "" +"By default, this playbook installs Buscarron on the `buscarron.` " +"subdomain (`buscarron.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:36 +msgid "" +"By tweaking the `matrix_bot_buscarron_hostname` and " +"`matrix_bot_buscarron_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:38 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:49 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:51 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Buscarron domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:53 +msgid "" +"By default, you will need to create a CNAME record for `buscarron`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:55 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:57 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:59 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:66 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:68 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:70 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:72 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:74 +msgid "" +"If you change the bot password (`matrix_bot_buscarron_password` in your " +"`vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_buscarron_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:76 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:78 +msgid "" +"To use the bot, invite the `@bot.buscarron:example.com` to the room you " +"specified in a config, after that any point your form to the form url, " +"example for the `contact` form:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:86 +msgid "" +"**Note**: to fight against spam, Buscarron is **very aggressive when it " +"comes to banning** and will ban you if:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:88 +msgid "if you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:89 +msgid "" +"if you submit a form to the wrong URL (`POST` request to `/non-existing-" +"form`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:90 +msgid "" +"if `hasemail` is enabled for the form (like in the example above) and you" +" don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:92 +msgid "" +"If you get banned, you'd need to restart the process by running the " +"playbook with `--tags=start` or running `systemctl restart matrix-bot-" +"buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/buscarron)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po new file mode 100644 index 000000000..121e56131 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po @@ -0,0 +1,158 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-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 "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:11 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:13 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:15 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 +msgid "Get an access token and create encryption keys" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:27 +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:29 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:31 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:52 +msgid "You will need to get tokens for ChatGPT." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:56 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 +msgid "" +"To use the bot, invite the `@bot.chatgpt:example.com` to the room you " +"specified in a config, after that start speaking to it, use the prefix if" +" you configured one or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po new file mode 100644 index 000000000..b1c589d9f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -0,0 +1,552 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-draupnir.md:1 +msgid "Setting up Draupnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:3 +msgid "" +"The playbook can install and configure the [Draupnir](https://github.com" +"/the-draupnir-project/Draupnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:5 +msgid "" +"See the project's [documentation](https://github.com/the-draupnir-" +"project/Draupnir) to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:7 +msgid "" +"This documentation page is about installing Draupnir in bot mode. As an " +"alternative, you can run a multi-instance Draupnir deployment by " +"installing [Draupnir in appservice mode](./configuring-playbook-" +"appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:9 +msgid "If your migrating from Mjolnir skip to step 5b." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:11 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:13 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:25 +msgid "" +"If you would like Draupnir to be able to deactivate users, move aliases, " +"shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc " +"then it must be a server admin so you need to change `admin=no` to " +"`admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:27 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:29 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:31 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:33 +msgid "" +"You will need to prevent Synapse from rate limiting the bot's account. " +"This is not an optional step. If you do not do this step Draupnir will " +"crash. This can be done using Synapse's [admin API](https://matrix-" +"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). Please ask for help if you are uncomfortable " +"with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:35 +msgid "" +"If your Synapse Admin API is exposed to the internet for some reason like" +" running the Synapse Admin Role [Link](configuring-playbook-synapse-" +"admin.md) or running " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true` in your playbook config. If your API is not externally exposed you" +" should still be able to on the local host for your synapse run these " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "" +"The following command works on semi up to date Windows 10 installs and " +"All Windows 11 installations and other systems that ship curl. `curl " +"--header \"Authorization: Bearer \" -X POST " +"https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" +" Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and " +"example.com with your homeserver domain. You can easily obtain an access " +"token for a homeserver admin account the same way you can obtain an " +"access token for Draupnir itself. If you made Draupnir Admin you can just" +" use the Draupnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:41 +msgid "" +"Using your own account, create a new invite only room that you will use " +"to manage the bot. This is the room where you will see the status of the " +"bot and where you will send commands to the bot, such as the command to " +"ban a user from another room. Anyone in this room can control the bot so " +"it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +msgid "" +"If you make the management room encrypted (E2EE), then you MUST enable " +"and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +msgid "" +"Once you have created the room you need to copy the room ID so you can " +"tell the bot to use that room. In Element Web you can do this by going to" +" the room's settings, clicking Advanced, and then copying the internal " +"room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +msgid "" +"Finally invite the `@bot.draupnir:example.com` account you created " +"earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:51 +msgid "" +"Decide whether you want Draupnir to be capable of operating in end-to-end" +" encrypted (E2EE) rooms. This includes the management room and the " +"moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon" +"](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +msgid "" +"When using Pantalaimon, Draupnir will log in to its bot account itself " +"through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:92 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "" +"The playbook's `group_vars` will configure other required settings. If " +"using this role separately without the playbook, you also need to " +"configure the two URLs that Draupnir uses to reach the homeserver, one " +"through Pantalaimon and one \"raw\". This example is taken from the " +"playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +msgid "" +"When NOT using Pantalaimon, Draupnir does not log in by itself and you " +"must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:94 +msgid "" +"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:104 +msgid "c. Migrating from Mjolnir (Only required if migrating.)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:106 +msgid "" +"Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " +"config. Also disable Mjolnir if you're doing migration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:108 +msgid "" +"That is all you need to do due to that Draupnir can complete migration on" +" its own." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:110 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:119 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:121 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:123 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:125 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:127 +msgid "" +"If you change the Pantalaimon's password " +"(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " +"subsequently, its credentials on the homeserver won't be updated " +"automatically. If you'd like to change the password, use a tool like " +"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " +"then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon" +" know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:129 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:131 +msgid "" +"You can refer to the upstream [documentation](https://the-draupnir-" +"project.github.io/draupnir-documentation/) for additional ways to use and" +" configure Draupnir and for a more detailed usage guide." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:133 +msgid "Below is a **non-exhaustive quick-start guide** for the impatient." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:135 +msgid "Making Draupnir join and protect a room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:137 +msgid "" +"Draupnir can be told to self-join public rooms, but it's better to follow" +" this flow which works well for all kinds of rooms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:139 +msgid "" +"Invite the bot to the room manually ([inviting Draupnir to rooms](https" +"://the-draupnir-project.github.io/draupnir-documentation/moderator" +"/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, " +"the bot *may* ask for confirmation in the Management Room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:141 +msgid "" +"[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" +"do-its-job)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:143 +msgid "" +"Tell it to protect the room (using the [rooms command](https://the-" +"draupnir-project.github.io/draupnir-documentation/moderator/managing-" +"protected-rooms#using-the-draupnir-rooms-command)) by sending the " +"following command to the Management Room: `!draupnir rooms add " +"!qporfwt:example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:145 +msgid "" +"To have Draupnir provide useful room protection, you need do to a bit " +"more work (at least the first time around). You may wish to [Subscribe to" +" a public policy list](#subscribing-to-a-public-policy-list), [Create " +"your own own policy and rules](#creating-your-own-policy-lists-and-rules)" +" and [Enabling built-in protections](#enabling-built-in-protections)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:147 +msgid "Giving Draupnir permissions to do its job" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:149 +msgid "" +"For Draupnir to do its job, you need to [give it permissions](https" +"://the-draupnir-project.github.io/draupnir-documentation/moderator" +"/managing-protected-rooms#giving-draupnir-permissions) in rooms it's " +"protecting. This involves **giving it an Administrator power level**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:151 +msgid "" +"**We recommend setting this power level as soon as the bot joins your " +"room** (and before you create new rules), so that it can apply rules as " +"soon as they are available. If the bot is under-privileged, it may fail " +"to apply protections and may not retry for a while (or until your restart" +" it)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:153 +msgid "Subscribing to a public policy list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:155 +msgid "" +"We recommend **subscribing to a public [policy list](https://the-" +"draupnir-project.github.io/draupnir-documentation/concepts/policy-" +"lists)** using the [watch command](https://the-draupnir-project.github.io" +"/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-" +"watch-command-to-subscribe-to-policy-rooms)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:157 +msgid "" +"Polcy lists are maintained in Matrix rooms. A popular policy list is " +"maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:159 +msgid "" +"You can tell Draupnir to subscribe to it by sending the following command" +" to the Management Room: `!draupnir watch #community-moderation-effort-" +"bl:neko.dev`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:161 +msgid "Creating your own policy lists and rules" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:163 +msgid "" +"We also recommend **creating your own policy lists** with the [list " +"create](https://the-draupnir-project.github.io/draupnir-" +"documentation/moderator/managing-policy-lists#using-draupnirs-list-" +"create-command-to-create-a-policy-room) command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +msgid "" +"You can do so by sending the following command to the Management Room: " +"`!draupnir list create my-bans my-bans-bl`. This will create a policy " +"list having a name (shortcode) of `my-bans` and stored in a public `#my-" +"bans-bl:example.com` room on your server. As soon as you run this " +"command, the bot will invite you to the policy list room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +msgid "" +"A policy list does nothing by itself, so the next step is **adding some " +"rules to your policy list**. Policies target a so-called `entity` (one " +"of: `user`, `room` or `server`). These entities are mentioned on the " +"[policy lists](https://the-draupnir-project.github.io/draupnir-" +"documentation/concepts/policy-lists) documentation page and in the Matrix" +" Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-" +"recommendation)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +msgid "" +"The simplest and most useful entity to target is `user`. Below are a few " +"examples using the [ban command](https://the-draupnir-project.github.io" +"/draupnir-documentation/moderator/managing-users#the-ban-command) and " +"targeting users." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +msgid "" +"To create rules, you run commands in the Management Room (**not** in the " +"policy list room)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +msgid "" +"(ban a single user on a given homeserver): `!draupnir ban " +"@charles:example.com my-bans Rude to others`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:174 +msgid "" +"(ban all users on a given homeserver by using a [wildcard](https://the-" +"draupnir-project.github.io/draupnir-documentation/moderator/managing-" +"users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - " +"all users are fake`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:176 +msgid "As a result of running these commands, you may observe:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:178 +msgid "" +"Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" +"bl:example.com` room on your server" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +msgid "" +"applying these rules against all rooms that Draupnir is an Administrator " +"in" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +msgid "" +"You can undo bans with the [unban command](https://the-draupnir-" +"project.github.io/draupnir-documentation/moderator/managing-users#the-" +"unban-command)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +msgid "Enabling built-in protections" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +msgid "" +"You can also **turn on various built-in [protections](https://the-" +"draupnir-project.github.io/draupnir-documentation/protections)** like " +"`JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the " +"room to invite-only\")." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +msgid "" +"To **see which protections are available and which are enabled**, send a " +"`!draupnir protections` command to the Management Room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +msgid "" +"To **see the configuration options for a given protection**, send a " +"`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " +"JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +msgid "" +"To **set a specific option for a given protection**, send a command like " +"this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " +"`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +msgid "" +"To **enable a given protection**, send a command like this: `!draupnir " +"enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +msgid "" +"To **disable a given protection**, send a command like this: `!draupnir " +"disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_draupnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +msgid "" +"For example to change Draupnir's `recordIgnoredInvites` option to `true` " +"you would add the following to your `vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +msgid "Abuse Reports" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +msgid "" +"The first method intercepts the report API endpoint of the client-server " +"API, which requires integration with the reverse proxy in front of the " +"homeserver. If you are using traefik, this playbook can set this up for " +"you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:225 +msgid "" +"The other method polls an synapse admin API endpoint and is hence only " +"available when using synapse and when the Draupnir user is an admin user " +"(see step 1). To enable it, set `pollReports: true` in Draupnir's config:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po new file mode 100644 index 000000000..ea89191dd --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po @@ -0,0 +1,209 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bot-go-neb.md:1 +msgid "Setting up Go-NEB (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:3 +msgid "" +"**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an " +"archived (**unmaintained**) project. We recommend not bothering with " +"installing it. While not a 1:1 replacement, the bridge's author suggests " +"taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) as a replacement, which can also be installed using [this " +"playbook](configuring-playbook-bridge-hookshot.md). Consider using that " +"bot instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:5 +msgid "" +"The playbook can install and configure [Go-NEB](https://github.com" +"/matrix-org/go-neb) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:7 +msgid "" +"Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, " +"the original Matrix bot written in Python." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/go-neb) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:11 +msgid "Registering the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:13 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires at least 1 access token to be able to connect to your " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:25 +msgid "" +"Once the user is created you can [obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:29 +msgid "" +"To enable Go-NEB, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:193 +msgid "Adjusting the Go-NEB URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:195 +msgid "" +"By default, this playbook installs Go-NEB on the `goneb.` subdomain " +"(`goneb.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:197 +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:199 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Go-NEB domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +msgid "" +"By default, you will need to create a CNAME record for `goneb`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +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:218 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +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:227 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +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:231 +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:233 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"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:235 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +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:239 +msgid "" +"Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy " +"matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 +msgid "" +"If you enabled the github_cmd service you can get the supported commands " +"via `!github help`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +msgid "" +"You can also refer to the upstream [Documentation](https://github.com" +"/matrix-org/go-neb)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po new file mode 100644 index 000000000..a0e5ceba7 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -0,0 +1,168 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bot-honoroit.md:1 +msgid "Setting up Honoroit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:3 +msgid "" +"The playbook can install and configure " +"[Honoroit](https://github.com/etkecc/honoroit) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:5 +msgid "It's a bot you can use to setup **your own helpdesk on matrix**" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:7 +msgid "" +"See the project's [documentation](https://github.com/etkecc/honoroit#how-" +"it-looks-like) to learn what it does with screenshots and why it might be" +" useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:11 +msgid "" +"To enable Honoroit, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:26 +msgid "Adjusting the Honoroit URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:28 +msgid "" +"By default, this playbook installs Honoroit on the `matrix.` subdomain, " +"at the `/honoroit` path (https://matrix.example.com/honoroit). This makes" +" it easy to install it, because it **doesn't require additional DNS " +"records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:30 +msgid "" +"By tweaking the `matrix_bot_honoroit_hostname` and " +"`matrix_bot_honoroit_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:32 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:42 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:46 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:50 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:59 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:65 +msgid "" +"If you change the bot password (`matrix_bot_honoroit_password` in your " +"`vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_honoroit_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:69 +msgid "" +"To use the bot, invite the `@honoroit:example.com` to the room you " +"specified in config, after that any Matrix user can send a message to the" +" `@honoroit:example.com` to start a new thread in that room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:71 +msgid "" +"Send `!ho help` to the room to see the bot's help menu for additional " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/honoroit#features)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po new file mode 100644 index 000000000..cc7e35bd2 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -0,0 +1,147 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-matrix-registration-bot.md:1 +msgid "Setting up matrix-registration-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3 +msgid "" +"The playbook can install and configure [matrix-registration-" +"bot](https://github.com/moan0s/matrix-registration-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5 +msgid "" +"The bot allows you to easily **create and manage registration tokens** " +"aka. invitation codes. It can be used for an invitation-based server, " +"where you invite someone by sending them a registration token (tokens " +"look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but " +"have to provide a valid registration token in the final step of the " +"registration process." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 +msgid "" +"See the project's [documentation](https://github.com/moan0s/matrix-" +"registration-bot#supported-commands) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 +msgid "" +"To enable the bot, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30 +msgid "The bot account will be created automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49 +msgid "" +"If you change the bot password " +"(`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` " +"file) subsequently, the bot user's credentials on the homeserver won't be" +" updated automatically. If you'd like to change the bot user's password, " +"use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to" +" change it, and then update " +"`matrix_bot_matrix_registration_bot_bot_password` to let the bot know its" +" new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53 +msgid "" +"To use the bot, start a chat with `@bot.matrix-registration-" +"bot:example.com` (where `example.com` is your base domain, not the " +"`matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 +msgid "In this room send `help` and the bot will reply with all options." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 +msgid "" +"You can also refer to the upstream [Usage " +"documentation](https://github.com/moan0s/matrix-registration-bot" +"#supported-commands)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59 +msgid "" +"If you have any questions, or if you need help setting it up, read the " +"[troublshooting guide](https://github.com/moan0s/matrix-registration-" +"bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-" +"bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61 +msgid "" +"To clean the cache (session & encryption data) after you changed the " +"bot's username, changed the login method from access_token to password " +"etc… you can use:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po new file mode 100644 index 000000000..6c3e1858a --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -0,0 +1,135 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-matrix-reminder-bot.md:1 +msgid "Setting up matrix-reminder-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3 +msgid "" +"The playbook can install and configure [matrix-reminder-" +"bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5 +msgid "" +"It's a bot you can use to **schedule one-off & recurring reminders and " +"alarms**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 +msgid "" +"See the project's [documentation](https://github.com/anoadragon453" +"/matrix-reminder-bot#usage) to learn what it does and why it might be " +"useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43 +msgid "" +"If you change the bot password " +"(`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml`" +" file) subsequently, the bot user's credentials on the homeserver won't " +"be updated automatically. If you'd like to change the bot user's " +"password, use a tool like [synapse-admin](configuring-playbook-synapse-" +"admin.md) to change it, and then update " +"`matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know" +" its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47 +msgid "" +"To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49 +msgid "" +"You can also add the bot to any existing Matrix room (`/invite @bot" +".matrix-reminder-bot:example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51 +msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53 +msgid "" +"Send `!help reminders` to the room to see the bot's help menu for " +"additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55 +msgid "" +"You can also refer to the upstream [Usage " +"documentation](https://github.com/anoadragon453/matrix-reminder-" +"bot#usage)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po new file mode 100644 index 000000000..c47d65373 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bot-maubot.md:1 +msgid "Setting up maubot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:3 +msgid "" +"The playbook can install and configure " +"[maubot](https://github.com/maubot/maubot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:5 +msgid "" +"After setting up maubot, you can use the web management interface to make" +" it do things. The default location of the management interface is " +"`matrix.example.com/_matrix/maubot/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn " +"what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:11 +msgid "" +"To enable maubot, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:26 +msgid "" +"You can add multiple admins. The admin accounts are only used to access " +"the maubot administration interface." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:28 +msgid "Adjusting the maubot URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:30 +msgid "" +"By default, this playbook installs maubot on the `matrix.` subdomain, at " +"the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/)." +" This makes it easy to install it, because it **doesn't require " +"additional DNS records to be set up**. If that's okay, you can skip this " +"section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:32 +msgid "" +"By tweaking the `matrix_bot_maubot_hostname` and " +"`matrix_bot_maubot_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:44 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the maubot domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:48 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.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-bot-maubot.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:61 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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-bot-maubot.md:67 +msgid "" +"If you change the bot password (`matrix_bot_maubot_initial_password` in " +"your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_bot_maubot_initial_password` to let the bot know its new " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:69 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:71 +msgid "" +"By default, you can visit `matrix.example.com/_matrix/maubot/` to manage " +"your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:73 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:74 +msgid "" +"**Create one or more clients**: A client is a Matrix account which the " +"bot will use to message. By default, the playbook creates a `bot.maubot` " +"account (as per the configuration above). You only need to [obtain an " +"access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:75 +msgid "" +"**Upload some Plugins**: Plugins can be obtained from " +"[here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:76 +msgid "" +"**Create an instance**: An instance is the actual bot. You have to " +"specify a client which the bot instance will use and the plugin (how the " +"bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:78 +msgid "Obtaining an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:80 +msgid "" +"This can be done via `mbc login` then `mbc auth` (see the [maubot " +"documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run " +"these commands, you'll first need to `exec` into the maubot container " +"with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:82 +msgid "" +"Alternatively, you can follow our generic [obtain an access token" +"](obtaining-access-tokens.md) documentation. Be aware that you'd better " +"use the **Obtain an access token via curl** method (not **Obtain an " +"access token via Element Web**) as the latter will give your bot issues " +"in encrypted rooms. Read " +"[more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po new file mode 100644 index 000000000..7a323cbe2 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -0,0 +1,281 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bot-mjolnir.md:1 +msgid "Setting up Mjolnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:3 +msgid "" +"The playbook can install and configure the [Mjolnir](https://github.com" +"/matrix-org/mjolnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/mjolnir) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:7 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:9 +msgid "" +"The playbook does not automatically create users for you. The bot " +"requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:11 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:13 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:15 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:21 +msgid "" +"If you would like Mjolnir to be able to deactivate users, move aliases, " +"shutdown rooms, etc then it must be a server admin so you need to change " +"`admin=no` to `admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:23 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:25 +msgid "" +"Refer to the documentation on [how to obtain an access token](obtaining-" +"access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:27 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:29 +msgid "" +"You will need to prevent Synapse from rate limiting the bot's account. " +"This is not an optional step. If you do not do this step Mjolnir will " +"crash. This can be done using Synapse's [admin API](https://matrix-" +"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). Please ask for help if you are uncomfortable " +"with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:31 +msgid "" +"If your Synapse Admin API is exposed to the internet for some reason like" +" running the Synapse Admin Role [Link](configuring-playbook-synapse-" +"admin.md) or running " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true` in your playbook config. If your API is not externally exposed you" +" should still be able to on the local host for your synapse run these " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "" +"The following command works on semi up to date Windows 10 installs and " +"All Windows 11 installations and other systems that ship curl. `curl " +"--header \"Authorization: Bearer \" -X POST " +"https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" +" Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and " +"example.com with your homeserver domain. You can easily obtain an access " +"token for a homeserver admin account the same way you can obtain an " +"access token for Mjolnir itself. If you made Mjolnir Admin you can just " +"use the Mjolnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 +msgid "" +"Using your own account, create a new invite only room that you will use " +"to manage the bot. This is the room where you will see the status of the " +"bot and where you will send commands to the bot, such as the command to " +"ban a user from another room. Anyone in this room can control the bot so " +"it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +msgid "" +"If you make the management room encrypted (E2EE), then you MUST enable " +"and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +msgid "" +"Once you have created the room you need to copy the room ID so you can " +"tell the bot to use that room. In Element Web you can do this by going to" +" the room's settings, clicking Advanced, and then copying the internal " +"room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +msgid "" +"Finally invite the `@bot.mjolnir:example.com` account you created earlier" +" into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 +msgid "" +"Decide whether you want Mjolnir to be capable of operating in end-to-end " +"encrypted (E2EE) rooms. This includes the management room and the " +"moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon" +"](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +msgid "" +"When using Pantalaimon, Mjolnir will log in to its bot account itself " +"through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "" +"The playbook's `group_vars` will configure other required settings. If " +"using this role separately without the playbook, you also need to " +"configure the two URLs that Mjolnir uses to reach the homeserver, one " +"through Pantalaimon and one \"raw\". This example is taken from the " +"playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +msgid "" +"When NOT using Pantalaimon, Mjolnir does not log in by itself and you " +"must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 +msgid "" +"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +msgid "Adding Mjolnir synapse antispam module (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 +msgid "" +"If you change the Pantalaimon's password " +"(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " +"subsequently, its credentials on the homeserver won't be updated " +"automatically. If you'd like to change the password, use a tool like " +"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " +"then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon " +"know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 +msgid "" +"You can refer to the upstream [documentation](https://github.com/matrix-" +"org/mjolnir) for additional ways to use and configure Mjolnir. Check out " +"their [quickstart guide](https://github.com/matrix-org/mjolnir" +"#quickstart-guide) for some basic commands you can give to the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 +msgid "" +"For example to change Mjolnir's `recordIgnoredInvites` option to `true` " +"you would add the following to your `vars.yml` file." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po new file mode 100644 index 000000000..9471d4d91 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po @@ -0,0 +1,246 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-discord.md:1 +msgid "Setting up Appservice Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" +"discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-" +"discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 +msgid "" +"For using as a Bot we are recommend the Appservice Discord bridge (the " +"one being discussed here), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 +msgid "" +"For personal use we recommend the [mautrix-discord](configuring-playbook-" +"bridge-mautrix-discord.md) bridge, because it is the most fully-featured " +"and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"discord](https://github.com/matrix-org/matrix-appservice-discord) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-discord/blob/master/README.md) to learn what it does and why " +"it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 +msgid "" +"Create a Discord Application " +"[here](https://discordapp.com/developers/applications). Then retrieve " +"Client ID, and create a bot from the Bot tab and retrieve the Bot token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 +msgid "Self-Service Bridging (Manual)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 +msgid "" +"Self-service bridging allows you to bridge specific and existing Matrix " +"rooms to specific Discord rooms. To enable it, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 +msgid "" +"**Note**: If self-service bridging is not enabled, `!discord help` " +"commands will return no results." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 +msgid "" +"Once self-service is enabled, start a chat with " +"`@_discord_bot:example.com` and say `!discord help bridge`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 +msgid "Then, follow the instructions in the help output message." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 +msgid "" +"If the bot is not already in the Discord server, follow the provided " +"invite link. This may require you to be a administrator of the Discord " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 +msgid "" +"On the Discord side, you can say `!matrix help` to get a list of " +"available commands to manage the bridge and Matrix users." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 +msgid "**Note**: Encrypted Matrix rooms are not supported as of writing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70 +msgid "Portal Bridging (Automatic)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 +msgid "" +"Through portal bridging, Matrix rooms will automatically be created by " +"the bot and bridged to the relevant Discord room. This is done by simply " +"joining a room with a specific name pattern " +"(`#_discord__`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74 +msgid "" +"All Matrix rooms created this way are **listed publicly** by default, and" +" you will not have admin permissions to change this. To get more control," +" [make yourself a room Administrator](#getting-administrator-access-in-a" +"-portal-bridged-room). You can then unlist the room from the directory " +"and change the join rules." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 +msgid "" +"To disable portal bridging, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 +msgid "To get started with Portal Bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 +msgid "" +"To invite the bot to Discord, retrieve the invite link from the `{{ " +"matrix_appservice_discord_config_path }}/invite_link` file on the server " +"(this defaults to `/matrix/appservice-discord/config/invite_link`). You " +"need to peek at the file on the server via SSH, etc., because it's not " +"available via HTTP(S)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 +msgid "" +"Room addresses follow this syntax: `#_discord__`. 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: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:90 +msgid "Getting Administrator access in a portal bridged room" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 +msgid "" +"By default, you won't have Administrator access in rooms created by the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 +msgid "" +"To adjust room access privileges or do various other things (change the " +"room name subsequently, etc.), you'd wish to become an Administrator." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 +msgid "" +"There's the Discord bridge's guide for [setting privileges on bridge " +"managed rooms](https://github.com/matrix-org/matrix-appservice-" +"discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-" +"rooms). To do the same with our container setup, run the following " +"command on the server:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po new file mode 100644 index 000000000..5b634a302 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po @@ -0,0 +1,102 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-irc.md:1 +msgid "Setting up Appservice IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 +msgid "" +"**Note**: bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " +"via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) " +"bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 +msgid "" +"The playbook can install and configure the [matrix-appservice-" +"irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-irc/blob/master/HOWTO.md) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 +msgid "" +"To use the bridge, you need to start a chat with `@irc_bot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po new file mode 100644 index 000000000..0cc472964 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po @@ -0,0 +1,229 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-kakaotalk.md:1 +msgid "Setting up Appservice Kakaotalk bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) " +"for you. `matrix-appservice-kakaotalk` is a bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +" based on [node-kakao](https://github.com/storycraft/node-kakao) (now " +"unmaintained) and some [mautrix-" +"facebook](https://github.com/mautrix/facebook) code." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 +msgid "" +"⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using" +" this bridge may get your account banned**." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 +msgid "" +"See the project's [documentation](https://src.miscworks.net/fair/matrix-" +"appservice-kakaotalk) to learn what it does and why it might be useful to" +" you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 +msgid "" +"`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for " +"some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 +msgid "" +"`roles/custom/matrix-bridge-appservice-" +"kakaotalk/templates/config.yaml.j2` for the bridge's default " +"configuration. You can override settings (even those that don't have " +"dedicated playbook variables) using the " +"`matrix_appservice_kakaotalk_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:49 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53 +msgid "" +"To use the bridge, you need to start a chat with " +"`@kakaotalkbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55 +msgid "" +"Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable " +"bridging for your Kakaotalk account. The `--save` flag may be omitted, if" +" you'd rather not save your password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77 +msgid "" +"make sure you don't log out the `Appservice-Kakaotalk` device some time " +"in the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po new file mode 100644 index 000000000..dced8b80f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po @@ -0,0 +1,325 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-slack.md:1 +msgid "Setting up Appservice Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3 +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4 +msgid "" +"Bridging to [Slack](https://slack.com) can also happen via the [mx-" +"puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " +"[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges " +"supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5 +msgid "" +"Currently (as of November, 2024) **this component is not available for " +"new installation unless you have already created a classic Slack " +"application** (which the bridge makes use of in order to enable bridging " +"between Slack and Matrix), because the creation of classic Slack " +"applications has been discontinued since June 4 2024. The author of the " +"bridge claims [here](https://github.com/matrix-org/matrix-appservice-" +"slack/issues/789#issuecomment-2172947787) that he plans to support the " +"modern Slack application and until then \"the best (and only) option for " +"new installations is to use the webhook bridging\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"slack](https://github.com/matrix-org/matrix-appservice-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"appservice-slack/blob/master/README.md) to learn what it does and why it " +"might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13 +msgid "Create a Classic Slack App" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15 +msgid "" +"First, you need to create a Classic Slack App " +"[here](https://api.slack.com/apps?new_classic_app=1)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17 +msgid "" +"Name the app \"matrixbot\" (or anything else you'll remember). Select the" +" team/workspace this app will belong to. Click on bot users and add a new" +" bot user. We will use this account to bridge the the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19 +msgid "" +"Then, click on Event Subscriptions and enable them and use the request " +"url: `https://matrix.example.com/appservice-slack`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21 +msgid "Add the following events as `Bot User Events` and save:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23 +msgid "team_domain_change" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 +msgid "message.channels" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25 +msgid "message.groups (if you want to bridge private channels)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 +msgid "reaction_added" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27 +msgid "reaction_removed" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29 +msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31 +msgid "chat:write:bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32 +msgid "users:read" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33 +msgid "reactions:write" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34 +msgid "files:write:user (if you want to bridge files)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36 +msgid "" +"**Note**: In order to make Slack files visible to Matrix users, this " +"bridge will make Slack files visible to anyone with the url (including " +"files in private channels). This is different than the current behavior " +"in Slack, which only allows authenticated access to media posted in " +"private channels. See MSC701 for details." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38 +msgid "" +"Click on \"Install App\" and \"Install App to Workspace\". Note the " +"access tokens shown. You will need the Bot User OAuth Access Token and if" +" you want to bridge files, the OAuth Access Token whenever you link a " +"room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40 +msgid "Create an administration control room on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42 +msgid "Create a new Matrix room to act as the administration control room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44 +msgid "" +"Note its internal room ID. This can be done in Element Web by sending a " +"message, opening the options for that message and choosing \"view " +"source\". The room ID will be displayed near the top." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 +msgid "" +"Other configuration options are available via the " +"`matrix_appservice_slack_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85 +msgid "" +"To use the bridge, you need to send `/invite @slackbot:example.com` to " +"invite the bridge bot user into the admin room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87 +msgid "" +"If Team Sync is not enabled, for each channel you would like to bridge, " +"perform the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 +msgid "" +"Create a Matrix room in the usual manner for your client. Take a note of " +"its Matrix room ID - it will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90 +msgid "" +"Invite the bot user to both the Slack and Matrix channels you would like " +"to bridge using `/invite @matrixbot` for Slack and `/invite " +"@slackbot:example.com` for Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 +msgid "" +"Determine the \"channel ID\" that Slack uses to identify the channel. You" +" can see it when you open a given Slack channel in a browser. The URL " +"reads like this: `https://app.slack.com/client/XXX//details/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:92 +msgid "" +"Issue a link command in the administration control room with these " +"collected values as arguments:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94 +msgid "with file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100 +msgid "without file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106 +msgid "These arguments can be shortened to single-letter forms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112 +msgid "Unlinking" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114 +msgid "Channels can be unlinked again by sending this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 +msgid "" +"Unlinking doesn't only disconnect the bridge, but also makes the slackbot" +" leave the bridged Matrix room. So in case you want to re-link later, " +"don't forget to re-invite the slackbot into this room again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124 +msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126 +msgid "Linking: \"Room is now pending-name\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 +msgid "" +"This typically means that you haven't used the correct Slack channel ID. " +"Unlink the room and recheck 'Determine the \"channel ID\"' from above." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130 +msgid "Messages work from Matrix to Slack, but not the other way around" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132 +msgid "Check you logs, if they say something like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 +#, python-format +msgid "" +"`WARN SlackEventHandler Ignoring message from unrecognised Slack channel " +"ID : %s (%s) `" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136 +msgid "" +"then unlink your room, reinvite the bot and re-link it again. This may " +"particularly hit you, if you tried to unsuccessfully link your room " +"multiple times without unlinking it after each failed attempt." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po new file mode 100644 index 000000000..af53cf585 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po @@ -0,0 +1,156 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-appservice-webhooks.md:1 +msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 +msgid "" +"**Note**: This bridge has been deprecated. We recommend not bothering " +"with installing it. While not a 1:1 replacement, the bridge's author " +"suggests taking a look at [matrix-hookshot](https://github.com/matrix-org" +"/matrix-hookshot) as a replacement, which can also be installed using " +"[this playbook](configuring-playbook-bridge-hookshot.md). Consider using " +"that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 +msgid "" +"The playbook can install and configure [matrix-appservice-" +"webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for " +"you. This bridge provides support for Slack-compatible webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 +msgid "" +"See the project's [documentation](https://github.com/turt2live/matrix-" +"appservice-webhooks/blob/master/README.md) to learn what it does and why " +"it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:42 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46 +msgid "" +"To use the bridge, you need to invite the bridge bot user to your room in" +" either way." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48 +msgid "" +"Send `/invite @_webhook:example.com` (**Note**: Make sure you have " +"administration permissions in your room)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49 +msgid "" +"Add the bridge bot to a private channel (personal channels imply you " +"being an administrator)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 +msgid "" +"You then need to send a message to the bridge bot in order to receive a " +"private message including the webhook link:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 +msgid "The JSON body for posting messages will have to look like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68 +msgid "You can test this via curl like so:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81 +msgid "Setting Webhooks with Dimension integration manager" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83 +msgid "" +"If you're using the [Dimension integration manager](configuring-playbook-" +"dimension.md), you can configure the Webhooks bridge with it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85 +msgid "" +"To configure it, open the Dimension integration manager, and go to " +"\"Settings\" and \"Bridges\", then select edit action for \"Webhook " +"Bridge\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87 +msgid "" +"On the UI, press \"Add self-hosted Bridge\" button and populate " +"\"Provisioning URL\" and \"Shared Secret\" values from `/matrix" +"/appservice-webhooks/config/config.yaml` file's homeserver URL value and " +"provisioning secret value, respectively." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po new file mode 100644 index 000000000..82271f69a --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po @@ -0,0 +1,187 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-beeper-linkedin.md:1 +msgid "Setting up Beeper Linkedin bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 +msgid "" +"The playbook can install and configure [beeper-" +"linkedin](https://github.com/beeper/linkedin) for you, for bridging to " +"[LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on " +"the mautrix-python framework and can be configured in a similar way to " +"the other mautrix bridges" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 +msgid "" +"See the project's " +"[documentation](https://github.com/beeper/linkedin/blob/master/README.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-beeper-" +"linkedin/templates/config.yaml.j2` to find other things you would like to" +" configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 +msgid "" +"Set up Double Puppeting by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 +msgid "" +"To use the bridge, you need to start a chat with " +"`@linkedinbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 +msgid "" +"Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable " +"bridging for your LinkedIn account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 +msgid "" +"After successfully enabling bridging, you may wish to [set up Double " +"Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-" +"or-shared-secret-auth), if you haven't already done so." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72 +msgid "Bridge asking for 2FA even if you don't have 2FA enabled" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 +msgid "" +"If you don't have 2FA enabled and are logging in from a strange IP for " +"the first time, LinkedIn will send an email with a one-time code. You can" +" use this code to authorize the bridge session. In my experience, once " +"the IP is authorized, you will not be asked again." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po new file mode 100644 index 000000000..7973bfcd1 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po @@ -0,0 +1,99 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-go-skype-bridge.md:1 +msgid "Setting up Go Skype Bridge bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 +msgid "" +"The playbook can install and configure [go-skype-" +"bridge](https://github.com/kelaresg/go-skype-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 +msgid "" +"To enable the [Skype](https://www.skype.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Skype bridge bot` with " +"the handle `@skypebridgebot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 +msgid "Send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po new file mode 100644 index 000000000..392e7645b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po @@ -0,0 +1,184 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-heisenbridge.md:1 +msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 +msgid "" +"**Note**: bridging to " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " +"via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-" +"irc.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 +msgid "" +"The playbook can install and configure " +"[Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style " +"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 +msgid "" +"See the project's " +"[README](https://github.com/hifi/heisenbridge/blob/master/README.md) to " +"learn what it does and why it might be useful to you. You can also take a" +" look at [this demonstration " +"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 +msgid "" +"To enable Heisenbridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24 +msgid "" +"For a more complete list of variables that you could override, see the " +"[`defaults/main.yml` file](../roles/custom/matrix-bridge-" +"heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26 +msgid "Adjusting the Heisenbridge URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28 +msgid "" +"By default, this playbook installs Heisenbridge on the `matrix.` " +"subdomain, at the `/heisenbridge` path " +"(https://matrix.example.com/heisenbridge). It would handle media requests" +" there (see the [release notes for Heisenbridge " +"v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 +msgid "" +"This makes it easy to install it, because it **doesn't require additional" +" DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 +msgid "" +"By tweaking the `matrix_heisenbridge_hostname` and " +"`matrix_heisenbridge_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Heisenbridge domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 +msgid "" +"To use the bridge, you need to start a chat with " +"`@heisenbridge:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain). If the bridge ignores you and a DM is not " +"accepted then the owner setting may be wrong." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 +msgid "Help is available for all commands with the `-h` switch." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 +msgid "" +"You can also learn the basics by watching [this demonstration " +"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 +msgid "" +"If you encounter issues or feel lost you can join the project room at " +"[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po new file mode 100644 index 000000000..3e2ad96e1 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po @@ -0,0 +1,484 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-hookshot.md:1 +msgid "Setting up matrix-hookshot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:3 +msgid "" +"The playbook can install and configure [matrix-" +"hookshot](https://github.com/matrix-org/matrix-hookshot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:5 +msgid "" +"Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " +"from software project management services such as GitHub, GitLab, JIRA, " +"and Figma, as well as generic webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:7 +msgid "" +"See the project's [documentation](https://matrix-org.github.io/matrix-" +"hookshot/latest/hookshot.html) to learn what it does in detail and why it" +" might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:9 +msgid "" +"**Note**: the playbook also supports [matrix-appservice-webhooks" +"](configuring-playbook-bridge-appservice-webhooks.md), which however was " +"deprecated by its author." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 +msgid "Setup Instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 +msgid "" +"Refer to the [official instructions](https://matrix-org.github.io/matrix-" +"hookshot/latest/setup.html) to learn what the individual options do." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 +msgid "" +"Enable the bridge by adding `matrix_hookshot_enabled: true` to your " +"`vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 +msgid "" +"For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) " +"fill in the respective variables `matrix_hookshot_service_*` listed in " +"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as " +"required." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 +msgid "" +"Take special note of the `matrix_hookshot_*_enabled` variables. Services " +"that need no further configuration are enabled by default (GitLab, " +"Generic), while you must first add the required configuration and enable " +"the others (GitHub, Jira, Figma)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 +msgid "" +"If you're setting up the GitHub bridge, you'll need to generate and " +"download a private key file after you created your GitHub app. Copy the " +"contents of that file to the variable " +"`matrix_hookshot_github_private_key` so the playbook can install it for " +"you, or use one of the [other methods](#manage-github-private-key-with-" +"aux-role) explained below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 +msgid "" +"If you've already installed Matrix services using the playbook before, " +"you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with" +" [configuring other playbook services](configuring-playbook.md) and then " +"with [Installing](installing.md). Get back to this guide once ready. " +"Hookshot can be set up individually using the tag `setup-hookshot`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 +msgid "" +"Other configuration options are available via the " +"`matrix_hookshot_configuration_extension_yaml` and " +"`matrix_hookshot_registration_extension_yaml` variables, see the comments" +" in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) " +"for how to use them." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 +msgid "Finally, run the playbook (see [installing](installing.md))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 +msgid "End-to-bridge encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +msgid "" +"You can enable [encryption](https://matrix-org.github.io/matrix-" +"hookshot/latest/advanced/encryption.html) for Hookshot by adding " +"`matrix_hookshot_encryption_enabled: true` to your configuration " +"(`vars.yml`) and [executing the playbook](installing.md) again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 +msgid "" +"Should the crypto store be corrupted, you can reset it by executing this " +"Ansible playbook with the tag `reset-hookshot-encryption` added, for " +"example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-" +"hookshot-encryption`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 +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:35 +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:37 +msgid "Send a `!hookshot help` message to see a list of help commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +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:41 +msgid "" +"**Important**: Note that the different listeners are bound to certain " +"paths which might differ from those assumed by the hookshot " +"documentation, see [URLs for bridges setup](#urls-for-bridges-setup) " +"below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +msgid "More setup documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +msgid "URLs for bridges setup" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +msgid "" +"Unless indicated otherwise, the following endpoints are reachable on your" +" `matrix.` subdomain (if the feature is enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "listener" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "default path" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "used as" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "-" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_webhook_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Webhook-prefix, which affects all webhook-related URLs below" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "generic" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_generic_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Generic webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "github oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_github_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "GitHub \"Callback URL\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "jira oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/jira/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_jira_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "JIRA OAuth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "figma endpoint" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/webhooks/figma/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_figma_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Figma" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "provisioning" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/v1/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_provisioning_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Dimension [provisioning](#provisioning-api)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "appservice" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/_matrix/app/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_appservice_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Matrix server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/hookshot/widgetapi/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`matrix_hookshot_widgets_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "`/metrics/hookshot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "" +"`matrix_hookshot_metrics_enabled` and exposure enabled via " +"`matrix_hookshot_metrics_proxying_enabled` or " +"`matrix_metrics_exposure_enabled`. Read more in the [Metrics " +"section](#metrics) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md +msgid "Prometheus" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +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:63 +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:65 +msgid "Manage GitHub Private Key with aux role" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +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:68 +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:69 +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:70 +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:72 +msgid "" +"To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" +" variable is empty. Then add the following additional configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +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:85 +msgid "Provisioning API" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 +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:89 +msgid "Metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +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:93 +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:95 +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:97 +msgid "" +"either enabling metrics exposure for Hookshot via " +"`matrix_hookshot_metrics_proxying_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 +msgid "" +"or enabling metrics exposure for all services via " +"`matrix_metrics_exposure_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 +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:102 +msgid "Collision with matrix-appservice-webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +msgid "" +"If you are also running [matrix-appservice-webhooks](configuring-" +"playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" +" default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. " +"You should take care if you modify its or hookshot's prefix that they do " +"not collide with each other's namespace (default " +"`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po new file mode 100644 index 000000000..b9ffa1e42 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po @@ -0,0 +1,100 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-matrix-bridge-sms.md:1 +msgid "Setting up Matrix SMS bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 +msgid "" +"The playbook can install and configure [matrix-sms-" +"bridge](https://github.com/benkuly/matrix-sms-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 +msgid "" +"**The bridge uses [android-sms-gateway-" +"server](https://github.com/RebekkaMa/android-sms-gateway-server). You " +"need to configure it first.**" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 +msgid "" +"Read the [user guide](https://github.com/benkuly/matrix-sms-" +"bridge/blob/master/README.md#user-guide) to see how this bridge works." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po new file mode 100644 index 000000000..d30d15e2e --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po @@ -0,0 +1,352 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-discord.md:1 +msgid "Setting up Mautrix Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" +"discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-" +"appservice-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Discord](configuring-" +"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 +msgid "" +"For personal use with a discord account we recommend the `mautrix-" +"discord` bridge (the one being discussed here), because it is the most " +"fully-featured and stable of the 3 Discord bridges supported by the " +"playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7 +msgid "" +"The playbook can install and configure [mautrix-" +"discord](https://github.com/mautrix/discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/discord/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 +msgid "" +"There are 2 ways to login to discord using this bridge, either by " +"[scanning a QR code](#method-1-login-using-qr-code-recommended) using the" +" Discord mobile app **or** by using a [Discord token](#method-2-login-" +"using-discord-token-not-recommended)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +msgid "" +"If this is a dealbreaker for you, consider using one of the other Discord" +" bridges supported by the playbook: [mx-puppet-discord](configuring-" +"playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord" +"](configuring-playbook-bridge-appservice-discord.md). These come with " +"their own complexity and limitations, however, so we recommend that you " +"proceed with this one if possible." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 +msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 +msgid "" +"`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some " +"variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 +msgid "" +"`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for" +" the bridge's default configuration. You can override settings (even " +"those that don't have dedicated playbook variables) using the " +"`matrix_mautrix_discord_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:55 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 +msgid "Logging in" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63 +msgid "Method 1: Login using QR code (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 +msgid "" +"For using this bridge, you would need to authenticate by **scanning a QR " +"code** with the Discord app on your phone." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 +msgid "You can delete the Discord app after the authentication process." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69 +msgid "Method 2: Login using Discord token (not recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 +msgid "" +"To acquire the token, open Discord in a private browser window. Then open" +" the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or " +"by pressing \"F12\"). Navigate to the \"Network\" tab then reload the " +"page. In the URL filter or search bar type \"/api\" and find the response" +" with the file name of \"library\". Under the request headers you should " +"find a variable called \"Authorization\", this is the token to your " +"Discord account. After copying the token, you can close the browser " +"window." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 +msgid "Bridging" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 +msgid "" +"Start a chat with `@discordbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:76 +msgid "" +"If you would like to login to Discord using a token, send `login-token` " +"command, otherwise, send `login-qr` command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77 +msgid "" +"You'll see a QR code which you need to scan with the Discord app on your " +"phone. You can scan it with the camera app too, which will open Discord, " +"which will then instruct you to scan it a 2nd time in the Discord app." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78 +msgid "" +"After confirming (in the Discord app) that you'd like to allow this " +"login, the bot should respond with \"Succcessfully authenticated as …\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 +msgid "" +"Now that you're logged in, you can send a `help` command to the bot " +"again, to see additional commands you have access to" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 +msgid "Some Direct Messages from Discord should start syncing automatically" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81 +msgid "If you'd like to bridge guilds:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82 +msgid "send `guilds status` to see the list of guilds" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83 +msgid "" +"for each guild that you'd like bridged, send `guilds bridge GUILD_ID " +"--entire`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84 +msgid "" +"You may wish to uninstall the Discord app from your phone now. It's not " +"needed for the bridge to function." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108 +msgid "" +"make sure you don't log out the `Mautrix-Discord` device some time in the" +" future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po new file mode 100644 index 000000000..5981bd708 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po @@ -0,0 +1,286 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-facebook.md:1 +msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 +msgid "" +"**Note**: This bridge has been deprecated in favor of the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " +"can be installed using [this playbook](configuring-playbook-bridge-" +"mautrix-meta-messenger.md). Consider using that bridge instead of this " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"facebook](https://github.com/mautrix/facebook) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 +msgid "" +"See the project's " +"[documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 +msgid "Using both would look like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-facebook/defaults/main.yml` to find other things you would like " +"to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:73 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77 +msgid "" +"To use the bridge, you need to start a chat with " +"`@facebookbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79 +msgid "" +"Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable " +"bridging for your Facebook Messenger account. You can learn more here " +"about authentication from the bridge's [official documentation on " +"Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103 +msgid "" +"make sure you don't log out the `Mautrix-Facebook` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107 +msgid "Facebook rejecting login attempts and forcing you to change password" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109 +msgid "" +"If your Matrix server is in a wildly different location than where you " +"usually use your Facebook account from, the bridge's login attempts may " +"be outright rejected by Facebook. Along with that, Facebook may even " +"force you to change the account's password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111 +msgid "" +"If you happen to run into this problem while [setting up " +"bridging](#usage), try to first get a successful session up by logging in" +" to Facebook through the Matrix server's IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113 +msgid "" +"The easiest way to do this may be to use " +"[sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic " +"through the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115 +msgid "Example command for proxying your traffic through the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121 +msgid "" +"Once connected, you should be able to verify that you're browsing the web" +" through the Matrix server's IP by checking " +"[icanhazip](https://icanhazip.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123 +msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125 +msgid "Once logged in, proceed to [set up bridging](#usage)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127 +msgid "" +"If that doesn't work, enable 2FA (see: [Facebook help page on enabling " +"2FA](https://www.facebook.com/help/148233965247823)) and try to login " +"again with a new password, and entering the 2FA code when prompted, it " +"may take more then one try, in between attempts, check facebook.com to " +"see if they are requiring another password change" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po new file mode 100644 index 000000000..4f2ae7fbf --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-gmessages.md:1 +msgid "Setting up Mautrix Google Messages bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"gmessages](https://github.com/mautrix/gmessages) for you, for bridging to" +" [Google Messages](https://messages.google.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:36 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40 +msgid "" +"To use the bridge, you need to start a chat with " +"`@gmessagesbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62 +msgid "" +"make sure you don't log out the `Mautrix-gmessages` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po new file mode 100644 index 000000000..6176e5ec0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po @@ -0,0 +1,216 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-googlechat.md:1 +msgid "Setting up Mautrix Google Chat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"googlechat](https://github.com/mautrix/googlechat) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/googlechat/index.html)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 +msgid "" +"To enable the [Google Chat](https://chat.google.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40 +msgid "" +"To use the bridge, you need to start a chat with `googlechat bridge bot` " +"with handle `@googlechatbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42 +msgid "" +"Send `login` to the bridge bot to receive a link to the portal from which" +" you can enable the bridging. Open the link sent by the bot and follow " +"the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44 +msgid "" +"Automatic login may not work. If it does not, reload the page and select " +"the \"Manual login\" checkbox before starting. Manual login involves " +"logging into your Google account normally and then manually getting the " +"OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46 +msgid "" +"Once logged in, recent chats should show up as new conversations " +"automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48 +msgid "" +"You can learn more about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72 +msgid "" +"make sure you don't log out the `Mautrix-googlechat` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po new file mode 100644 index 000000000..167839731 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-hangouts.md:1 +msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 +msgid "" +"💡 **Note**: This bridge has been deprecated in favor of [Google Chat " +"bridge](https://github.com/mautrix/googlechat), which can be installed " +"using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md)." +" Installing the mautrix-hangouts bridge is **no longer possible**. For " +"now, this documentation page remains here for historical purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"hangouts](https://github.com/mautrix/hangouts) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" +"auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17 +msgid "" +"To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 +msgid "" +"To use the bridge, you need to start a chat with `Hangouts bridge bot` " +"with handle `@hangoutsbot:example.com` (where `example.com` is your base " +"domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 +msgid "" +"Send `login` to the bridge bot to receive a link to the portal from which" +" you can enable the bridging. Open the link sent by the bot and follow " +"the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 +msgid "" +"Automatic login may not work. If it does not, reload the page and select " +"the \"Manual login\" checkbox before starting. Manual login involves " +"logging into your Google account normally and then manually getting the " +"OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 +msgid "" +"Once logged in, recent chats should show up as new conversations " +"automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 +msgid "" +"You can learn more about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service is configured and " +"enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72 +msgid "" +"make sure you don't log out the `Mautrix-Hangouts` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po new file mode 100644 index 000000000..85ea7a1ae --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po @@ -0,0 +1,143 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-instagram.md:1 +msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 +msgid "" +"**Note**: This bridge has been deprecated in favor of the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " +"can be installed using [this playbook](configuring-playbook-bridge-" +"mautrix-meta-instagram.md). Consider using that bridge instead of this " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"instagram](https://github.com/mautrix/instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/instagram/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29 +msgid "" +"If you would like to be able to administrate the bridge from your account" +" it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-instagram/defaults/main.yml` to find other things you would like " +"to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:60 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64 +msgid "" +"To use the bridge, you need to start a chat with " +"`@instagrambot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66 +msgid "" +"Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the " +"bridge bot to enable bridging for your instagram/Messenger account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68 +msgid "" +"You can learn more here about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po new file mode 100644 index 000000000..b17ea6ba8 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po @@ -0,0 +1,295 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-meta-instagram.md:1 +msgid "Setting up Instagram bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 +msgid "" +"The playbook can install and configure the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 +msgid "" +"Since this bridge component can bridge to both " +"[Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/) and you may wish to do both at the " +"same time, the playbook makes it available via 2 different Ansible roles " +"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" +"instagram`). The latter is a reconfigured copy of the first one (created " +"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" +"instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 +msgid "" +"This documentation page only deals with the bridge's ability to bridge to" +" Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger" +" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" +"messenger.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11 +msgid "Migrating from the old mautrix-instagram bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 +msgid "" +"If you've been using the [mautrix-instagram](./configuring-playbook-" +"bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first**" +" or the 2 bridges will be in conflict:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 +msgid "" +"both trying to use `@instagrambot:example.com` as their username. This " +"conflict may be resolved by adjusting " +"`matrix_mautrix_instagram_appservice_bot_username` or " +"`matrix_mautrix_meta_instagram_appservice_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 +msgid "both trying to bridge the same DMs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 +msgid "" +"To do so, send a `clean-rooms` command to the management room with the " +"old bridge bot (`@instagrambot:example.com`). It gives you a list of " +"portals and groups of portals you may purge. Proceed with sending " +"commands like `clean recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 +msgid "" +"Then, consider disabling the old bridge in your configuration, so it " +"won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:36 +msgid "" +"Before proceeding to [re-running the playbook](./installing.md), you may " +"wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 +msgid "" +"The permissions are following the sequence: nothing < `relay` < `user` < " +"`admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 +msgid "" +"The default permissions are set via " +"`matrix_mautrix_meta_instagram_bridge_permissions_default` and are " +"somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 +msgid "" +"If you don't define the `matrix_admin` in your configuration (e.g. " +"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61 +msgid "" +"You may redefine " +"`matrix_mautrix_meta_instagram_bridge_permissions_default` any way you " +"see fit, or add extra permissions using " +"`matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" +"instagram/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:85 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89 +msgid "" +"To use the bridge, you need to start a chat with " +"`@instagrambot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111 +msgid "" +"make sure you don't log out the session for which you obtained an access " +"token some time in the future, as that would break the Double Puppeting " +"feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po new file mode 100644 index 000000000..55a8a3868 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po @@ -0,0 +1,360 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-meta-messenger.md:1 +msgid "Setting up Messenger bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 +msgid "" +"The playbook can install and configure the [mautrix-" +"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 +msgid "" +"Since this bridge component can bridge to both " +"[Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/) and you may wish to do both at the " +"same time, the playbook makes it available via 2 different Ansible roles " +"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" +"instagram`). The latter is a reconfigured copy of the first one (created " +"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" +"instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 +msgid "" +"This documentation page only deals with the bridge's ability to bridge to" +" Facebook Messenger. For bridging to Instagram, see [Setting up Instagram" +" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" +"instagram.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 +msgid "Migrating from the old mautrix-facebook bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 +msgid "" +"If you've been using the [mautrix-facebook](./configuring-playbook-" +"bridge-mautrix-facebook.md) bridge, it's possible to migrate the database" +" using [instructions from the bridge " +"documentation](https://docs.mau.fi/bridges/go/meta/facebook-" +"migration.html) (advanced)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 +msgid "" +"Then you may wish to get rid of the Facebook bridge. To do so, send a " +"`clean-rooms` command to the management room with the old bridge bot " +"(`@facebookbot:example.com`). It gives you a list of portals and groups " +"of portals you may purge. Proceed with sending commands like `clean " +"recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 +msgid "" +"Then, consider disabling the old bridge in your configuration, so it " +"won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 +msgid "" +"**Note**: the user ID of the new bridge bot is " +"`@messengerbot:example.com`, not `@facebookbot:example.com`. After " +"disabling the old bridge, its bot user will stop responding to a command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 +msgid "" +"Before proceeding to [re-running the playbook](./installing.md), you may " +"wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 +msgid "Bridge mode" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 +msgid "" +"As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) " +"bridge supports multiple modes of operation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 +msgid "The bridge can pull your Messenger messages via 3 different methods:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43 +msgid "(`facebook`) Facebook via `facebook.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44 +msgid "" +"(`facebook-tor`) Facebook via " +"`facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` " +"([Tor](https://www.torproject.org/)) - does not currently proxy media " +"downloads" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 +msgid "" +"(default) (`messenger`) Messenger via `messenger.com` - usable even " +"without a Facebook account" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 +msgid "" +"You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode`" +" variable. The playbook defaults to the `messenger` mode, because it's " +"most universal (every Facebook user has a Messenger account, but the " +"opposite is not true)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 +msgid "" +"Note that switching the mode (especially between `facebook*` and " +"`messenger`) will intentionally make the bridge use another database " +"(`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to " +"isolate the 2 instances. Switching between Tor and non-Tor may be " +"possible without dataloss, but your mileage may vary. Before switching to" +" a new mode, you may wish to de-configure the old one (send `help` to the" +" bridge bot and unbridge your portals, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 +msgid "" +"The permissions are following the sequence: nothing < `relay` < `user` < " +"`admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 +msgid "" +"The default permissions are set via " +"`matrix_mautrix_meta_messenger_bridge_permissions_default` and are " +"somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 +msgid "" +"If you don't define the `matrix_admin` in your configuration (e.g. " +"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 +msgid "" +"You may redefine " +"`matrix_mautrix_meta_messenger_bridge_permissions_default` any way you " +"see fit, or add extra permissions using " +"`matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" +"messenger/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102 +msgid "" +"To use the bridge, you need to start a chat with " +"`@messengerbot:example.com` (where `example.com` is your base domain, not" +" the `matrix.` domain). Note that the user ID of the bridge's bot is not " +"`@facebookbot:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104 +msgid "" +"You then need to send a `login` command and follow the bridge bot's " +"instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106 +msgid "" +"Given that the bot is configured in `messenger` [bridge mode](#bridge-" +"mode) by default, you will need to log in to " +"[messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain " +"the cookies from there as per [the bridge's authentication " +"instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128 +msgid "" +"make sure you don't log out the session for which you obtained an access " +"token some time in the future, as that would break the Double Puppeting " +"feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po new file mode 100644 index 000000000..3912c9f1f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po @@ -0,0 +1,266 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-signal.md:1 +msgid "Setting up Mautrix Signal bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"signal](https://github.com/mautrix/signal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/signal/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 +msgid "" +"**Note**: This revamped version of the [mautrix-signal (legacy" +")](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU " +"usage of your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 +msgid "Prerequisites (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11 +msgid "Prepare Postgres database on external Postgres server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 +msgid "" +"If you're running with the Postgres database server integrated by the " +"playbook (which is the default), you don't need to do anything special " +"and can easily proceed with installing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 +msgid "" +"However, if you're [using an external Postgres server](configuring-" +"playbook-external-postgres.md), you'd need to manually prepare a Postgres" +" database for this bridge and adjust the variables related to that " +"(`matrix_mautrix_signal_database_*`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 +msgid "Enable Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 +msgid "relay - Allowed to be relayed through the bridge, no access to commands;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38 +msgid "user - Use the bridge with puppeting;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39 +msgid "admin - Use and administer the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 +msgid "" +"The permissions are following the sequence: nothing < relay < user < " +"admin." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43 +msgid "The default permissions are set as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 +msgid "" +"If you want to augment the preset permissions, you might want to set the " +"additional permissions with the following settings in your `vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 +msgid "" +"This will add the admin permission to the specific user, while keeping " +"the default permissions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 +msgid "" +"In case you want to replace the default permissions settings " +"**completely**, populate the following item within your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"signal/templates/config.yaml.j2` to find more information on the " +"permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:87 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91 +msgid "" +"To use the bridge, you need to start a chat with `@signalbot:example.com`" +" (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113 +msgid "" +"make sure you don't log out the `Mautrix-Signal` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po new file mode 100644 index 000000000..439a8b7d5 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po @@ -0,0 +1,288 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-slack.md:1 +msgid "Setting up Mautrix Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 +msgid "" +"**Note**: bridging to [Slack](https://slack.com/) can also happen via the" +" [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Slack](configuring-" +"playbook-bridge-appservice-slack.md), because it supports plumbing. Note " +"that it is not available for new installation unless you have already " +"created a classic Slack application, because the creation of classic " +"Slack applications, which this bridge makes use of, has been " +"discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 +msgid "" +"For personal use with a slack account we recommend the `mautrix-slack` " +"bridge (the one being discussed here), because it is the most fully-" +"featured and stable of the 3 Slack bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7 +msgid "" +"The playbook can install and configure [mautrix-" +"slack](https://github.com/mautrix/slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn" +" what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 +msgid "" +"See the [features and " +"roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more " +"information." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 +msgid "" +"For using this bridge, you would need to authenticate by **providing your" +" username and password** (legacy) or by using a **token login**. See more" +" information in the " +"[docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 +msgid "" +"Note that neither of these methods are officially supported by Slack. " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) uses a Slack bot account which is the only officially supported" +" method for bridging a Slack channel." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:33 +msgid "" +"You may optionally wish to add some [Additional configuration" +"](#additional-configuration), or to [prepare for double-puppeting](#set-" +"up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 +msgid "" +"There are some additional options you may wish to configure with the " +"bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41 +msgid "" +"`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some " +"variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +msgid "" +"`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for " +"the bridge's default configuration. You can override settings (even those" +" that don't have dedicated playbook variables) using the " +"`matrix_mautrix_slack_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 +msgid "" +"Start a chat with `@slackbot:example.com` (where `example.com` is your " +"base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:64 +msgid "" +"If you would like to login to Slack using a token, send the `login-token`" +" command, otherwise, send the `login-password` command. Read " +"[here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how " +"to retrieve your token and cookie token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 +msgid "" +"The bot should respond with \"Successfully logged into for team " +"\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 +msgid "" +"Now that you're logged in, you can send a `help` command to the bot " +"again, to see additional commands you have access to." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 +msgid "" +"Slack channels should automatically begin bridging if you authenticated " +"using a token. Otherwise, you must wait to receive a message in the " +"channel if you used password authentication." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89 +msgid "" +"make sure you don't log out the `Mautrix-Slack` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po new file mode 100644 index 000000000..601653ed9 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po @@ -0,0 +1,222 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-telegram.md:1 +msgid "Setting up Mautrix Telegram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"telegram](https://github.com/mautrix/telegram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/python/telegram/index.html) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 +msgid "" +"You'll need to obtain API keys from " +"[https://my.telegram.org/apps](https://my.telegram.org/apps) and then add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 +msgid "" +"To use the bridge, you need to start a chat with " +"`@telegrambot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44 +msgid "" +"If you want to use the relay-bot feature ([relay bot " +"documentation](https://docs.mau.fi/bridges/python/telegram/relay-" +"bot.html)), which allows anonymous user to chat with telegram users, add " +"the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 +msgid "You might also want to give permissions to administrate the bot:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63 +msgid "" +"More details about permissions in this example: " +"https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-" +"config.yaml#L410" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65 +msgid "" +"If you like to exclude all groups from syncing and use the Telgeram-" +"Bridge only for direct chats, you can add the following additional " +"playbook configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +msgid "" +"**Note**: This method for enabling Double Puppeting can be configured " +"only after you've already set up bridging." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 +msgid "" +"send `login-matrix` to the bot and follow instructions about how to send " +"the access token to it" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 +msgid "" +"make sure you don't log out the `Mautrix-Telegram` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po new file mode 100644 index 000000000..1e8109cd3 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po @@ -0,0 +1,189 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-twitter.md:1 +msgid "Setting up Mautrix Twitter bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 +msgid "" +"**Note**: bridging to [Twitter](https://twitter.com/) can also happen via" +" the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-" +"twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 +msgid "" +"The playbook can install and configure [mautrix-" +"twitter](https://github.com/mautrix/twitter) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 +msgid "" +"See the project's [documentation](https://github.com/mautrix/twitter) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 +msgid "" +"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-twitter.md:13 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.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-twitter.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +msgid "" +"You then need to start a chat with `@twitterbot:example.com` (where " +"`example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +msgid "" +"Send login-cookie to start the login. The bot should respond with " +"instructions on how to proceed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +msgid "" +"You can learn more here about authentication from the bridge's [official " +"documentation on " +"Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 +msgid "" +"This method is currently not available for the Mautrix-Twitter bridge, " +"but is on the " +"[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) " +"under Misc/Manual login with `login-matrix`" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po new file mode 100644 index 000000000..dbcd9512a --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po @@ -0,0 +1,212 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mautrix-whatsapp.md:1 +msgid "Setting up Mautrix Whatsapp bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"whatsapp](https://github.com/mautrix/whatsapp) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 +msgid "" +"See the project's " +"[documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 +msgid "" +"If you want to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do) for this bridge automatically, you need to " +"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" +"secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 +msgid "" +"For details about configuring Double Puppeting for this bridge, see the " +"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 +msgid "" +"Whatsapp multidevice beta is required, now it is enough if Whatsapp is " +"connected to the Internet every 2 weeks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23 +msgid "" +"The relay bot functionality is off by default. If you would like to " +"enable the relay bot, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 +msgid "" +"By default, only admins are allowed to set themselves as relay users. To " +"allow anyone on your homeserver to set themselves as relay users add this" +" to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 +msgid "" +"If you want to activate the relay bot in a room, send `!wa set-relay`. To" +" deactivate, send `!wa unset-relay`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 +msgid "" +"To use the bridge, you need to start a chat with " +"`@whatsappbot:example.com` (where `example.com` is your base domain, not " +"the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60 +msgid "" +"After successfully enabling bridging, you may wish to set up [Double " +"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " +"(hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64 +msgid "" +"Method 1: automatically, by enabling Appservice Double Puppet or Shared " +"Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66 +msgid "" +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " +"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " +"configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68 +msgid "" +"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md) is the recommended way of setting up Double Puppeting, " +"as it's easier to accomplish, works for all your users automatically, and" +" has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70 +msgid "" +"Enabling double puppeting by enabling the [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) service works at the time " +"of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74 +msgid "" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80 +msgid "" +"make sure you don't log out the `Mautrix-Whatsapp` device some time in " +"the future, as that would break the Double Puppeting feature" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po new file mode 100644 index 000000000..673a7908b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-wsproxy.md:1 +msgid "" +"Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage " +"(optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 +msgid "" +"The playbook can install and configure [mautrix-" +"wsproxy](https://github.com/mautrix/wsproxy) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 +msgid "" +"See the project's " +"[documentation](https://github.com/mautrix/wsproxy#readme) to learn what " +"it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 +msgid "" +"Note that the tokens must match what is compiled into the [mautrix-" +"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" +" or Android device." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 +msgid "Adjusting the wsproxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 +msgid "" +"By default, this playbook installs wsproxy on the `wsproxy.` subdomain " +"(`wsproxy.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27 +msgid "" +"By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can " +"easily make the service available at a **different hostname** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the wsproxy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40 +msgid "" +"By default, you will need to create a CNAME record for `wsproxy`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:55 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:57 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 +msgid "" +"Follow the [matrix-imessage " +"documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for " +"running `android-sms` and/or `matrix-imessage` on your device(s)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po new file mode 100644 index 000000000..ee082570c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po @@ -0,0 +1,139 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-discord.md:1 +msgid "Setting up MX Puppet Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 +msgid "" +"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " +"via the [matrix-appservice-discord](configuring-playbook-bridge-" +"appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-" +"mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4 +msgid "" +"For using as a Bot we recommend the [Appservice Discord](configuring-" +"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:5 +msgid "" +"For personal use with a discord account we recommend the [mautrix-discord" +"](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is " +"the most fully-featured and stable of the 3 Discord bridges supported by " +"the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7 +msgid "" +"The playbook can install and configure [mx-puppet-" +"discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13 +msgid "" +"To enable the [Discord](https://discordapp.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:34 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38 +msgid "" +"To use the bridge, you need to start a chat with `Discord Puppet Bridge` " +"with the handle `@_discordpuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-discord [documentation](https://gitlab.com/mx-" +"puppet/discord/mx-puppet-discord) for more information about how to " +"configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po new file mode 100644 index 000000000..0e89d39f8 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po @@ -0,0 +1,123 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-groupme.md:1 +msgid "Setting up MX Puppet GroupMe bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 +msgid "" +"To enable the [GroupMe](https://groupme.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 +msgid "" +"To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` " +"with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 +msgid "One authentication method is available." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 +msgid "" +"To link your GroupMe account, go to " +"[dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access" +" Token\" from the top menu. Copy the token and message the bridge with:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 +msgid "" +"Once logged in, send `listrooms` to the bot user to list the available " +"rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po new file mode 100644 index 000000000..450c385de --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-instagram.md:1 +msgid "Setting up MX Puppet Instagram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 +msgid "This allows you to bridge Instagram DirectMessages into Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 +msgid "" +"To enable the [Instagram](https://www.instagram.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Instagram Puppet " +"Bridge` with the handle `@_instagrampuppet_bot:example.com` (where " +"`example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36 +msgid "" +"Send `link ` 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 "" +"The `help` command shows which commands are available, though at the time" +" of writing, not every command is fully implemented." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po new file mode 100644 index 000000000..5b094b2c3 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po @@ -0,0 +1,41 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-skype.md:1 +msgid "Setting up MX Puppet Skype bridging (optional, removed)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 +msgid "" +"The playbook used to be able to install and configure [mx-puppet-" +"skype](https://github.com/Sorunome/mx-puppet-skype), but no longer " +"includes this component, because it has been broken and unmaintained for " +"a long time." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 +msgid "" +"Bridging to [Skype](https://www.skype.com/) can also happen via the [go-" +"skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge " +"supported by the playbook." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po new file mode 100644 index 000000000..02d3399ae --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po @@ -0,0 +1,140 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mx-puppet-slack.md:1 +msgid "Setting up MX Puppet Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 +msgid "" +"**Note**: bridging to [Slack](https://slack.com) can also happen via the " +"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" +"slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-" +"slack.md) bridges supported by the playbook. Note that `matrix-" +"appservice-slack` is not available for new installation unless you have " +"already created a classic Slack application, because the creation of " +"classic Slack applications, which this bridge makes use of, has been " +"discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 +msgid "" +"The playbook can install and configure [mx-puppet-" +"slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11 +msgid "" +"Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack#option-2-oauth) instructions to create a new Slack app, " +"setting the redirect URL to `https://matrix.example.com/slack/oauth`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15 +msgid "" +"To enable the [Slack](https://slack.com/) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:39 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43 +msgid "" +"To use the bridge, you need to start a chat with `Slack Puppet Bridge` " +"with the handle `@_slackpuppet_bot:example.com` (where `example.com` is " +"your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-slack [documentation](https://gitlab.com/mx-" +"puppet/slack/mx-puppet-slack) for more information about how to configure" +" the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po new file mode 100644 index 000000000..46bb77cc2 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po @@ -0,0 +1,116 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-bridge-mx-puppet-steam.md:1 +msgid "Setting up MX Puppet Steam bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 +msgid "" +"The playbook can install and configure [mx-puppet-" +"steam](https://github.com/icewind1991/mx-puppet-steam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 +msgid "" +"To enable the [Steam](https://steampowered.com/) bridge, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 +msgid "" +"To use the bridge, you need to start a chat with `Steam Puppet Bridge` " +"with the handle `@_steampuppet_bot:example.com` (where `example.com` is " +"your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 +msgid "" +"Three authentication methods are available, Legacy Token, OAuth and xoxc " +"token. See mx-puppet-steam [documentation](https://github.com/icewind1991" +"/mx-puppet-steam) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po new file mode 100644 index 000000000..4e21b4966 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po @@ -0,0 +1,130 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-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 page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11 +msgid "" +"Make an app on " +"[developer.twitter.com](https://developer.twitter.com/en/apps)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 +msgid "" +"To enable the [Twitter](https://twitter.com) bridge, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:41 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45 +msgid "" +"To use the bridge, you need to start a chat with `Twitter Puppet Bridge` " +"with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is" +" your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47 +msgid "To log in, use `link` and click the link." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 +msgid "" +"Clicking rooms in the list will result in you receiving an invitation to " +"the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po new file mode 100644 index 000000000..c70b924fd --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -0,0 +1,197 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-postmoogle.md:1 +msgid "Setting up Postmoogle email bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3 +msgid "" +"**Note**: email bridging can also happen via the [email2matrix" +"](configuring-playbook-email2matrix.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5 +msgid "" +"The playbook can install and configure " +"[Postmoogle](https://github.com/etkecc/postmoogle) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7 +msgid "" +"Postmoogle is a bridge you can use to have its bot user forward emails to" +" Matrix rooms. It runs an SMTP email server and allows you to assign " +"mailbox addresses to the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 +msgid "" +"See the project's [documentation](https://github.com/etkecc/postmoogle) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13 +msgid "" +"Open the following ports on your server to be able to receive incoming " +"emails:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15 +msgid "`25/tcp`: SMTP" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16 +msgid "`587/tcp`: Submission (TLS-encrypted SMTP)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18 +msgid "" +"If you don't open these ports, you will still be able to send emails, but" +" not receive any." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20 +msgid "" +"These port numbers are configurable via the " +"`matrix_postmoogle_smtp_host_bind_port` and " +"`matrix_postmoogle_submission_host_bind_port` variables, but other email " +"servers will try to deliver on these default (standard) ports, so " +"changing them is of little use." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47 +msgid "" +"You will also need to add several DNS records so that Postmoogle can send" +" emails. See [Configuring DNS](configuring-dns.md) for details about DNS " +"changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create a user account of the bridge's bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66 +msgid "" +"If you change the bridge's bot password (`matrix_postmoogle_password` in " +"your `vars.yml` file) subsequently, the bot user's credentials on the " +"homeserver won't be updated automatically. If you'd like to change the " +"bot user's password, use a tool like [synapse-admin](configuring-" +"playbook-synapse-admin.md) to change it, and then update " +"`matrix_postmoogle_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70 +msgid "" +"To use the bridge, invite the `@postmoogle:example.com` bot user into a " +"room you want to use as a mailbox." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72 +msgid "" +"Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with " +"the email address `NAME@matrix.example.com`. Emails sent to that email " +"address will be forwarded to the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 +msgid "" +"Send `!pm help` to the room to see the bridge's help menu for additional " +"commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 +msgid "" +"You can also refer to the upstream " +"[documentation](https://github.com/etkecc/postmoogle)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78 +msgid "Debug/Logs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80 +msgid "" +"As with all other services, you can find their logs in [systemd-" +"journald](https://www.freedesktop.org/software/systemd/man/systemd-" +"journald.service.html) by running something like `journalctl -fu matrix-" +"postmoogle`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82 +msgid "" +"The default logging level for this bridge is `INFO`, but you can increase" +" it to `DEBUG` with the following additional configuration:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po new file mode 100644 index 000000000..9adff616c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po @@ -0,0 +1,98 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-wechat.md:1 +msgid "Setting up WeChat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:3 +msgid "" +"The playbook can install and configure the [matrix-" +"wechat](https://github.com/duo/matrix-wechat) bridge for you (for " +"bridging to the [WeChat](https://www.wechat.com/) network)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:5 +msgid "" +"See the project page to learn what it does and why it might be useful to " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:17 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:26 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:34 +msgid "" +"Once the bridge is installed, start a chat with `@wechatbot:example.com` " +"(where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:36 +msgid "Send `help` to the bot to see the available commands." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po new file mode 100644 index 000000000..e0ba16d7c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po @@ -0,0 +1,237 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-cactus-comments.md:1 +msgid "Setting up Cactus Comments (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:3 +msgid "" +"The playbook can install and configure the [Cactus " +"Comments](https://cactus.chat) system for you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:5 +msgid "" +"Cactus Comments is a **federated comment system** built on Matrix. It " +"respects your privacy, and puts you in control." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:7 +msgid "" +"See the project's [documentation](https://cactus.chat/docs/getting-" +"started/introduction/) to learn what it does and why it might be useful " +"to you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:9 +msgid "" +"The playbook contains 2 roles for configuring different pieces of the " +"Cactus Comments system:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:11 +msgid "" +"`matrix-cactus-comments` - the backend appservice integrating with the " +"Matrix homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:13 +msgid "" +"`matrix-cactus-comments-client` - a static website server serving the " +"[cactus-client](https://cactus.chat/docs/client/introduction/) static " +"assets (`cactus.js` and `styles.css`)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:15 +msgid "You can enable whichever component you need (typically both)." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:17 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:19 +msgid "" +"To enable Cactus Comments, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:41 +msgid "Adjusting the Cactus Comments' client URL" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:43 +msgid "" +"By default, this playbook installs Cactus Comments' client on the " +"`matrix.` subdomain, at the `/cactus-comments` path " +"(https://matrix.example.com/cactus-comments). This makes it easy to " +"install it, because it **doesn't require additional DNS records to be set" +" up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:45 +msgid "" +"By tweaking the `matrix_cactus_comments_client_hostname` and " +"`matrix_cactus_comments_client_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:47 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:56 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:58 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Cactus Comments' client domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:60 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:62 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:64 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:66 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:73 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:75 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:77 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:79 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:81 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:83 +msgid "" +"Upon starting Cactus Comments, a `bot.cactusbot` user account is created " +"automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:85 +msgid "" +"To get started, send a `help` message to the `@bot.cactusbot:example.com`" +" bot to confirm it's working." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:87 +msgid "" +"Then, register a site by sending `register ` (where " +"`` is a unique identifier you choose. It does not have to " +"match your domain). You will then be invited into a moderation room." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:89 +msgid "Now you are good to go and can embed the comment section on your website!" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:91 +msgid "Embed Cactus Comments" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:93 +msgid "" +"The official [documentation](https://cactus.chat/docs/getting-started" +"/quick-start/) provides a useful guide to embed Cactus Comments on your " +"website." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:95 +msgid "" +"After including the JavaScript and CSS asset files, insert a `
` " +"where you'd like to display the comment section:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:101 +msgid "" +"Then, you need to initialize the comment section. Make sure to replace " +"`example.com` with your base domain and `` with the one " +"that has been registered above:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:115 +msgid "Adjust the domain name for self-hosting" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:117 +msgid "" +"To have the assets served from your homeserver (not from `cactus.chat`), " +"you need to adjust the domain name on the official documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:119 +msgid "" +"Make sure to replace `example.com` with your base domain before you " +"include the following lines, instead of the one provided by the official " +"documentation:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:126 +msgid "" +"**Note**: if the `matrix_cactus_comments_client_hostname` and " +"`matrix_cactus_comments_client_path_prefix` variables are tweaked, you " +"would need to adjust the URLs of the assets accordingly." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po new file mode 100644 index 000000000..2368b3e4f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-client-cinny.md:1 +msgid "Setting up Cinny (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:3 +msgid "" +"This playbook can install the [Cinny](https://github.com/ajbura/cinny) " +"Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:5 +msgid "" +"Cinny is a web client focusing primarily on simple, elegant and secure " +"interface. It can be installed alongside or instead of [Element Web" +"](./configuring-playbook-client-element-web.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:7 +msgid "" +"💡 **Note**: the latest version of Cinny is also available on the web, " +"hosted by 3rd parties. If you trust giving your credentials to the " +"following 3rd party Single Page Applications, you can consider using it " +"from there and avoiding the (small) overhead of self-hosting:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:9 +msgid "" +"[app.cinny.in](https://app.cinny.in), hosted by the " +"[Cinny](https://cinny.in/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:13 +msgid "" +"To enable Cinny, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:19 +msgid "Adjusting the Cinny URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:21 +msgid "" +"By default, this playbook installs Cinny on the `cinny.` subdomain " +"(`cinny.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:23 +msgid "" +"By tweaking the `matrix_client_cinny_hostname` variable, you can easily " +"make the service available at a **different hostname** than the default " +"one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:25 +msgid "" +"While a `matrix_client_cinny_path_prefix` variable exists for tweaking " +"the path-prefix, it's [not supported " +"anymore](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3701), because Cinny requires an application rebuild (with " +"a tweaked build config) to be functional under a custom path." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:27 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:34 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:36 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the Cinny domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:38 +msgid "" +"By default, you will need to create a CNAME record for `cinny`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:40 +msgid "" +"If you've adjusted `matrix_client_cinny_hostname`, you will need to " +"adjust your DNS configuration accordingly." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:44 +msgid "" +"After configuring the playbook and [adjusting your DNS records" +"](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:51 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:53 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po new file mode 100644 index 000000000..d1ecdbd21 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po @@ -0,0 +1,235 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-client-element-web.md:1 +msgid "Configuring Element Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:3 +msgid "" +"By default, this playbook installs the [Element Web](https://github.com" +"/element-hq/element-web) Matrix client for you. If that's okay, you can " +"skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:5 +msgid "" +"💡 **Note**: the latest version of Element Web is also available on the " +"web, hosted by 3rd parties. If you trust giving your credentials to the " +"following 3rd party Single Page Applications, you can consider using it " +"from there and avoiding the (small) overhead of self-hosting (by " +"[disabling Element Web](#disabling-element-web)):" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:7 +msgid "" +"[app.element.io](https://app.element.io/), hosted by " +"[Element](https://element.io/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:8 +msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:10 +msgid "Disabling Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:12 +msgid "" +"If you'd like for the playbook to not install Element Web (or to " +"uninstall it if it was previously installed), add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:20 +msgid "" +"The playbook provides some customization variables you could use to " +"change Element Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:22 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/element/config.json` file (on the server). This file is " +"generated from the [`roles/custom/matrix-client-" +"element/templates/config.json.j2`](../roles/custom/matrix-client-" +"element/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:24 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:26 +msgid "" +"Alternatively, **if there is no pre-defined variable** for an Element Web" +" setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:28 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Element Web's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:30 +msgid "" +"or, you can **extend and override the default configuration** " +"([`config.json.j2`](../roles/custom/matrix-client-" +"element/templates/config.json.j2)) by making use of the " +"`matrix_client_element_configuration_extension_json_` variable. You can " +"find information about this in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:32 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_client_element_configuration_default` (or " +"`matrix_client_element_configuration`). You can find information about " +"this in [`roles/custom/matrix-client-" +"element/defaults/main.yml`](../roles/custom/matrix-client-" +"element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:34 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:36 +msgid "" +"To change the look of Element Web, you can define your own themes " +"manually by using the " +"`matrix_client_element_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:38 +msgid "" +"Or better yet, you can automatically pull it all themes provided by the " +"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" +"themes) project by simply flipping a flag " +"(`matrix_client_element_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:40 +msgid "" +"If you make your own theme, we encourage you to submit it to the " +"**aaronraimist/element-themes** project, so that the whole community " +"could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:42 +msgid "" +"Note that for a custom theme to work well, all Element Web instances that" +" you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:44 +msgid "Adjusting the Element Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:46 +msgid "" +"By default, this playbook installs Element Web on the `element.` " +"subdomain (`element.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:48 +msgid "" +"By tweaking the `matrix_client_element_hostname` and " +"`matrix_client_element_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:50 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:61 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:63 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Element Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:65 +msgid "" +"By default, you will need to create a CNAME record for `element`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:67 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:69 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:71 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:78 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:80 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po new file mode 100644 index 000000000..c4fe82ea3 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po @@ -0,0 +1,122 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-client-hydrogen.md:1 +msgid "Setting up Hydrogen (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:3 +msgid "" +"This playbook can install the [Hydrogen](https://github.com/element-hq" +"/hydrogen-web) Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:5 +msgid "" +"Hydrogen is a lightweight web client that supports mobile and legacy web " +"browsers. It can be installed alongside or instead of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:9 +msgid "" +"To enable Hydrogen, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:15 +msgid "Adjusting the Hydrogen URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:17 +msgid "" +"By default, this playbook installs Hydrogen on the `hydrogen.` subdomain " +"(`hydrogen.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:19 +msgid "" +"By tweaking the `matrix_client_hydrogen_hostname` and " +"`matrix_client_hydrogen_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:21 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:32 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:34 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Hydrogen domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:36 +msgid "" +"By default, you will need to create a CNAME record for `hydrogen`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:38 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:40 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:42 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:49 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:51 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po new file mode 100644 index 000000000..944601214 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po @@ -0,0 +1,231 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-client-schildichat-web.md:1 +msgid "Setting up SchildiChat Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:3 +msgid "" +"This playbook can install the [SchildiChat " +"Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:5 +msgid "" +"SchildiChat Web is a feature-rich messenger for Matrix based on Element " +"Web with some extras and tweaks. It can be installed alongside or instead" +" of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:7 +msgid "" +"💡 **Note**: the latest version of SchildiChat Web is also available on " +"the web, hosted by 3rd parties. If you trust giving your credentials to " +"the following 3rd party Single Page Application, you can consider using " +"it from there:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 +msgid "" +"[app.schildi.chat](https://app.schildi.chat/), hosted by the " +"[SchildiChat](https://schildi.chat/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 +msgid "" +"To enable SchildiChat Web, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 +msgid "" +"The playbook provides some customization variables you could use to " +"change SchildiChat Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:21 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml) and they ultimately end up in the " +"generated `/matrix/schildichat/config.json` file (on the server). This " +"file is generated from the [`roles/custom/matrix-client-" +"schildichat/templates/config.json.j2`](../roles/custom/matrix-client-" +"schildichat/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:23 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a SchildiChat " +"Web setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of SchildiChat Web's various" +" settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:29 +msgid "" +"or, you can **extend and override the default configuration** " +"([`config.json.j2`](../roles/custom/matrix-client-" +"schildichat/templates/config.json.j2)) by making use of the " +"`matrix_client_schildichat_configuration_extension_json_` variable. You " +"can find information about this in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:31 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_client_schildichat_configuration_default` (or " +"`matrix_client_schildichat_configuration`). You can find information " +"about this in [`roles/custom/matrix-client-" +"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" +"schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:33 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:35 +msgid "" +"To change the look of SchildiChat Web, you can define your own themes " +"manually by using the " +"`matrix_client_schildichat_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:37 +msgid "" +"Or better yet, you can automatically pull it all themes provided by the " +"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" +"themes) project by simply flipping a flag " +"(`matrix_client_schildichat_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:39 +msgid "" +"If you make your own theme, we encourage you to submit it to the " +"**aaronraimist/element-themes** project, so that the whole community " +"could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 +msgid "" +"Note that for a custom theme to work well, all SchildiChat Web instances " +"that you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 +msgid "Adjusting the SchildiChat Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:45 +msgid "" +"By default, this playbook installs SchildiChat Web on the `schildichat.` " +"subdomain (`schildichat.example.com`) and requires you to [adjust your " +"DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:47 +msgid "" +"By tweaking the `matrix_client_schildichat_hostname` and " +"`matrix_client_schildichat_path_prefix` variables, you can easily make " +"the service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:49 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:60 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:62 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the SchildiChat Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:64 +msgid "" +"By default, you will need to create a CNAME record for `schildichat`. See" +" [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:66 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:68 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:70 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po new file mode 100644 index 000000000..4e013493d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-conduit.md:1 +msgid "Configuring Conduit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, but you can also use " +"[Conduit](https://conduit.rs)." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:7 +msgid "" +"**You can't switch an existing Matrix server's implementation** (e.g. " +"Synapse -> Conduit). Proceed below only if you're OK with losing data or " +"you're dealing with a server on a new domain name, which hasn't " +"participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:9 +msgid "" +"**homeserver implementations other than Synapse may not be fully " +"functional**. The playbook may also not assist you in an optimal way " +"(like it does with Synapse). Make yourself familiar with the downsides " +"before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:13 +msgid "" +"To use Conduit, you **generally** need to add the following configuration" +" to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:19 +msgid "Creating the first user account" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:21 +msgid "" +"Since it is difficult to create the first user account on Conduit (see " +"[famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) " +"and " +"[famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354))" +" and it does not support [registering users](registering-users.md) (via " +"the command line or via the playbook) like Synapse and Dendrite do, we " +"recommend the following procedure:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:23 +msgid "" +"Add `matrix_conduit_allow_registration: true` to your `vars.yml` the " +"first time around, temporarily" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:24 +msgid "" +"Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags" +"=setup-all,start` - see [Installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:25 +msgid "" +"Create your first user via Element Web or any other client which supports" +" creating users" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:26 +msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:27 +msgid "" +"Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=setup-conduit,start` would be enough this time)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:28 +msgid "" +"You can now use your server safely. Additional users can be created by " +"messaging the internal Conduit bot" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:30 +msgid "Configuring bridges / appservices" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:32 +msgid "" +"Automatic appservice setup is currently unsupported when using Conduit. " +"After setting up the service as usual you may notice that it is unable to" +" start." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:34 +msgid "" +"You will have to manually register appservices using the the [register-" +"appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md)" +" command." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:36 +msgid "" +"Find the `registration.yaml` in the `/matrix` directory, for example " +"`/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content " +"to Conduit:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po new file mode 100644 index 000000000..d371a0775 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -0,0 +1,151 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dendrite.md:1 +msgid "Configuring Dendrite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, but you can also use " +"[Dendrite](https://github.com/matrix-org/dendrite)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:7 +msgid "" +"**You can't switch an existing Matrix server's implementation** (e.g. " +"Synapse -> Dendrite). Proceed below only if you're OK with losing data or" +" you're dealing with a server on a new domain name, which hasn't " +"participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:9 +msgid "" +"**homeserver implementations other than Synapse may not be fully " +"functional**. The playbook may also not assist you in an optimal way " +"(like it does with Synapse). Make yourself familiar with the downsides " +"before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:13 +msgid "" +"To use Dendrite, you **generally** need to add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:19 +msgid "" +"The playbook provides lots of customization variables you could use to " +"change Dendrite's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:21 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/dendrite/config/dendrite.yaml` file (on the server). This file " +"is generated from the [`roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:23 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:25 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a Dendrite " +"setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:27 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Dendrite's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:29 +msgid "" +"or, you can **extend and override the default configuration** " +"([`dendrite.yaml.j2`](../roles/custom/matrix-" +"dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the " +"`matrix_dendrite_configuration_extension_yaml` variable. You can find " +"information about this in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:31 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_dendrite_configuration` (or " +"`matrix_dendrite_configuration_yaml`). You can find information about " +"this in [`roles/custom/matrix-" +"dendrite/defaults/main.yml`](../roles/custom/matrix-" +"dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:35 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:42 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:44 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po new file mode 100644 index 000000000..f4423b101 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -0,0 +1,258 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dimension.md:1 +msgid "Setting up Dimension integration manager (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:3 +msgid "" +"**[Dimension](https://dimension.t2bot.io) can only be installed after " +"Matrix services are installed and running.** If you're just installing " +"Matrix services for the first time, please continue with the " +"[Configuration](configuring-playbook.md) / [Installation](installing.md) " +"flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "" +"**Note**: 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:7 +msgid "" +"**Note**: This playbook now supports running " +"[Dimension](https://dimension.t2bot.io) in both a federated and " +"[unfederated](https://github.com/turt2live/matrix-" +"dimension/blob/master/docs/unfederated.md) environments. This is handled " +"automatically based on the value of " +"`matrix_homeserver_federation_enabled`. Enabling Dimension, means that " +"the `openid` API endpoints will be exposed on the Matrix Federation port " +"(usually `8448`), even if [federation](configuring-playbook-" +"federation.md) is disabled. It's something to be aware of, especially in " +"terms of firewall whitelisting (make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "" +"To enable Dimension, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "" +"These users can modify the integrations this Dimension supports. Add this" +" to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:27 +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:29 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "" +"We recommend that you create a dedicated Matrix user for Dimension " +"(`dimension` is a good username). Follow our [Registering users" +"](registering-users.md) guide to learn how to register **a regular (non-" +"admin) user**." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "" +"You are required to specify an access token (belonging to this new user) " +"for Dimension to work. To get an access token for the Dimension user, you" +" can follow the documentation on [how to do obtain an access token" +"](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "" +"Add access token to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:43 +msgid "" +"For more information on how to acquire an access token, visit " +"[https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "" +"By default, this playbook installs Dimension on the `dimension.` " +"subdomain (`dimension.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:49 +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:51 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:62 +msgid "" +"**Note**: While there is a `matrix_dimension_path_prefix` variable for " +"changing the path where Dimension is served, overriding it is not " +"possible due to [this Dimension issue](https://github.com/turt2live" +"/matrix-dimension/issues/510). You must serve Dimension at a dedicated " +"subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:64 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:66 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:68 +msgid "" +"By default, you will need to create a CNAME record for `dimension`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:81 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:83 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:85 +msgid "" +"After Dimension has been installed you may need to log out and log back " +"in for it to pick up the new integration manager. Then you can access " +"integrations in Element Web by opening a room, clicking the Room info " +"button (`i`) button in the top right corner of the screen, and then " +"clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:87 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:89 +msgid "" +"By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as " +"the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video " +"conference widgets. For users running [a self-hosted Jitsi instance" +"](./configuring-playbook-jitsi.md), you will likely want the widget to " +"use your own Jitsi instance. Currently there is no way to configure this " +"via the playbook, see [this issue](https://github.com/turt2live/matrix-" +"dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:91 +msgid "" +"In the interim until the above limitation is resolved, an admin user " +"needs to configure the domain via the admin ui once dimension is running." +" In Element Web, go to *Manage Integrations* → *Settings* " +"→ *Widgets* → *Jitsi Conference Settings* and set " +"*Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:93 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:95 +msgid "" +"To use a more custom configuration, you can define a " +"`matrix_dimension_configuration_extension_yaml` string variable and put " +"your configuration in it. To learn more about how to do this, refer to " +"the information about `matrix_dimension_configuration_extension_yaml` in " +"the [default variables file](../roles/custom/matrix-" +"dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:97 +msgid "" +"You can find all configuration options on [GitHub page of Dimension " +"project](https://github.com/turt2live/matrix-" +"dimension/blob/master/config/default.yaml)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po new file mode 100644 index 000000000..1a8304187 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po @@ -0,0 +1,99 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-dynamic-dns.md:1 +msgid "Setting up Dynamic DNS (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:3 +msgid "" +"The playbook can configure Dynamic DNS with " +"[ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl " +"client used to update dynamic DNS entries for accounts on Dynamic DNS " +"Network Service Provider." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:5 +msgid "" +"Most cloud providers / ISPs will charge you extra for a static IP " +"address. If you're not hosting a highly reliable homeserver you can " +"workaround this via dynamic DNS." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:7 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:9 +msgid "" +"You'll need to get a username and password from your DNS provider. Please" +" consult with the provider about how to retrieve them." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:13 +msgid "" +"To enable dynamic DNS, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:35 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:37 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:39 +msgid "Additional Reading" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:41 +msgid "Additional resources:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:43 +msgid "https://matrix.org/docs/guides/free-small-matrix-server" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po new file mode 100644 index 000000000..0efaa7bf5 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po @@ -0,0 +1,127 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-email.md:1 +msgid "Adjusting email-sending settings (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:3 +msgid "" +"By default, this playbook sets up an [Exim](https://www.exim.org/) email " +"server through which all Matrix services send emails." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:5 +msgid "" +"The email server would attempt to deliver emails directly to their final " +"destination. This may or may not work, depending on your domain " +"configuration (SPF settings, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:7 +msgid "" +"By default, emails are sent from `matrix@matrix.example.com`, as " +"specified by the `exim_relay_sender_address` playbook variable." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:9 +msgid "" +"⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is" +" always blocked](https://cloud.google.com/compute/docs/tutorials/sending-" +"mail/), so sending email directly from your server is not possible. You " +"will need to [relay email through another SMTP server](#relaying-email-" +"through-another-smtp-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:11 +msgid "" +"💡 To improve deliverability, we recommend [relaying email through another" +" SMTP server](#relaying-email-through-another-smtp-server) anyway." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:13 +msgid "Firewall settings" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:15 +msgid "" +"No matter whether you send email directly (the default) or you relay " +"email through another host (see how below), you'll probably need to allow" +" outgoing traffic for TCP ports 25/587 (depending on configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:17 +msgid "Relaying email through another SMTP server" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:19 +msgid "" +"If you'd like to relay email through another SMTP server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:31 +msgid "" +"**Note**: only the secure submission protocol (using `STARTTLS`, usually " +"on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port " +"`465`) **is not supported**." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:33 +msgid "Configuations for sending emails using Sendgrid" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:35 +msgid "" +"An easy and free SMTP service to set up is " +"[Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 " +"emails per day to be sent. In the settings below you can provide any " +"email for `exim_relay_sender_address`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:37 +msgid "" +"The only other thing you need to change is the " +"`exim_relay_relay_auth_password`, which you can generate at " +"https://app.sendgrid.com/settings/api_keys. The API key password looks " +"something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-" +"6zkdwrPP8bOeuI`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:39 +msgid "" +"Note that the `exim_relay_relay_auth_username` is literally the string " +"`apikey`, it's always the same for Sendgrid." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:51 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:53 +msgid "" +"If you're having trouble with email not being delivered, it may be useful" +" to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po new file mode 100644 index 000000000..dfac1cb02 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -0,0 +1,258 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-email2matrix.md:1 +msgid "Setting up Email2Matrix (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:3 +msgid "" +"**Note**: email bridging can also happen via the [Postmoogle" +"](configuring-playbook-bridge-postmoogle.md) bridge supported by the " +"playbook. Postmoogle is much more powerful and easier to use, so we " +"recommend that you use it, instead of Email2Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:5 +msgid "" +"The playbook can install and configure " +"[email2matrix](https://github.com/devture/email2matrix) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:7 +msgid "" +"See the project's " +"[documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md)" +" to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:9 +msgid "Preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:11 +msgid "DNS configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:13 +msgid "" +"It's not strictly necessary, but you may increase the chances that " +"incoming emails reach your server by adding an `MX` record for " +"`matrix.example.com`, as described in the [Configuring DNS](configuring-" +"dns.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:15 +msgid "Port availability" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:17 +msgid "" +"Ensure that port 25 is available on your Matrix server and open in your " +"firewall." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:19 +msgid "" +"If you have `postfix` or some other email server software installed, you " +"may need to manually remove it first (unless you need it, of course)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:21 +msgid "" +"If you really need to run an email server on the Matrix machine for other" +" purposes, it may be possible to run Email2Matrix on another port (with a" +" configuration like `matrix_email2matrix_smtp_host_bind_port: " +"\"127.0.0.01:2525\"`) and have your other email server relay messages " +"there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:23 +msgid "" +"For details about using Email2Matrix alongside " +"[Postfix](http://www.postfix.org/), see " +"[here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:25 +msgid "Creating a user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:27 +msgid "" +"Before enabling Email2Matrix, you'd most likely wish to create a " +"dedicated user (or more) that would be sending messages on the Matrix " +"side. 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:29 +msgid "" +"Refer to [Registering users](registering-users.md) for ways to create a " +"user. A regular (non-admin) user works best." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:31 +msgid "Creating a shared room" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:33 +msgid "" +"After creating the sender user, you should create one or more Matrix " +"rooms that you share with that user. It doesn't matter who creates and " +"owns the rooms and who joins later (you or the sender user)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:35 +msgid "" +"What matters is that both you and the sender user are part of the same " +"room and that the sender user has enough privileges in the room to be " +"able to send messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:37 +msgid "Inviting additional people to the room is okay too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:39 +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:41 +msgid "Obtaining an access token for the sender user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:43 +msgid "" +"In order for the sender user created above to be able to send messages to" +" the room, we'll need to obtain an access token for it. Refer to the " +"documentation on [how to obtain an access token](obtaining-access-" +"tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:47 +msgid "" +"After doing the preparation steps above, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to " +"your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:72 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:74 +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:75 +msgid "" +"MatrixRoomId - internal ID of the room, to which received emails are sent" +" as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:76 +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:77 +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:78 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:79 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:80 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:81 +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:83 +msgid "" +"Refer to the official documentation " +"[here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:85 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:87 +msgid "" +"To enable Email2Matrix, run the playbook with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:95 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just run-tags setup-email2matrix,start` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:97 +msgid "" +"`just run-tags setup-email2matrix,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-email2matrix.md:99 +msgid "" +"After installation, you may wish to send a test email to the email " +"address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) " +"to make sure that Email2Matrix works as expected." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po new file mode 100644 index 000000000..b8ea886cf --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -0,0 +1,250 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-etherpad.md:1 +msgid "Setting up Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:3 +msgid "" +"[Etherpad](https://etherpad.org) is an open source collaborative text " +"editor that can be embedded in a Matrix chat room using the [Dimension " +"integration manager](https://dimension.t2bot.io) or used as standalone " +"web app." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:5 +msgid "" +"When enabled together with the Jitsi audio/video conferencing system (see" +" [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made " +"available as an option during the conferences." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:9 +msgid "" +"To enable Etherpad, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:19 +msgid "Adjusting the Etherpad URL" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:21 +msgid "" +"By default, this playbook installs Etherpad on the `etherpad.` subdomain " +"(`etherpad.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:23 +msgid "" +"By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables," +" you can easily make the service available at a **different hostname " +"and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:25 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:38 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Etherpad domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:40 +msgid "" +"By default, you will need to create a CNAME record for `etherpad`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:42 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:46 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:55 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the Etherpad admin user (`etherpad_admin_username`)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:61 +msgid "" +"If you change the Etherpad admin user's password " +"(`etherpad_admin_password` in your `vars.yml` file) subsequently, the " +"admin user's credentials on the homeserver won't be updated " +"automatically. If you'd like to change the admin user's password, use a " +"tool like [synapse-admin](configuring-playbook-synapse-admin.md) to " +"change it, and then update `etherpad_admin_password` to let the admin " +"user know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:65 +msgid "" +"The Etherpad UI should be available at `https://etherpad.example.com`, " +"while the admin UI (if enabled) should then be available at " +"`https://etherpad.example.com/admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:67 +msgid "" +"If you've [decided on another hostname or path-prefix](#adjusting-the-" +"etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these " +"URLs accordingly before usage." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:69 +msgid "Managing / Deleting old pads" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:71 +msgid "" +"If you want to manage and remove old unused pads from Etherpad, you will " +"first need to able Admin access as described above." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:73 +msgid "" +"Then from the plugin manager page " +"(`https://etherpad.example.com/admin/plugins`, install the `adminpads2` " +"plugin. Once installed, you should have a \"Manage pads\" section in the " +"Admin web-UI." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:75 +msgid "" +"How to use Etherpad widgets without an integration manager (like " +"Dimension)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:77 +msgid "" +"This is how it works in Element Web, it might work quite similar with " +"other clients:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:79 +msgid "" +"To integrate a standalone Etherpad in a room, create your pad by visiting" +" `https://etherpad.example.com`. When the pad opens, copy the URL and " +"send a command like this to the room: `/addwidget URL`. You will then " +"find your integrated Etherpad within the right sidebar in the `Widgets` " +"section." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:81 +msgid "Set Dimension default to the self-hosted Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:83 +msgid "" +"If you decided to install [Dimension integration manager](configuring-" +"playbook-dimension.md) alongside Etherpad, the Dimension administrator " +"users can configure the default URL template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:85 +msgid "" +"The Dimension configuration menu can be accessed with the sprocket icon " +"as you begin to add a widget to a room in Element Web. There you will " +"find the Etherpad Widget Configuration action beneath the _Widgets_ tab." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:87 +msgid "Removing the integrated Etherpad chat" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:89 +msgid "" +"If you wish to disable the Etherpad chat button, you can do it by " +"appending `?showChat=false` to the end of the pad URL, or the template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:91 +msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:93 +msgid "Known issues" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:95 +msgid "" +"If your Etherpad widget fails to load, this might be due to Dimension " +"generating a Pad name so long, the Etherpad app rejects it." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:97 +msgid "" +"`$roomId_$padName` can end up being longer than 50 characters. You can " +"avoid having this problem by altering the template so it only contains " +"the three word random identifier `$padName`." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po new file mode 100644 index 000000000..e732065fb --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po @@ -0,0 +1,80 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-external-postgres.md:1 +msgid "Using an external PostgreSQL server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:3 +msgid "" +"By default, this playbook would set up a PostgreSQL database server on " +"your machine, running in a Docker container. If that's okay, you can skip" +" this document." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:5 +msgid "" +"**Note**: using **an external Postgres server is currently [not very " +"seamless](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/1682#issuecomment-1061461683) when it comes to enabling " +"various other playbook services** - you will need to create a new " +"database/credentials for each service and to point each service to its " +"corresponding database using custom `vars.yml` configuration. **For the " +"best experience with the playbook, stick to using the integrated Postgres" +" server**." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:7 +msgid "" +"If you'd like to use an external Postgres server that you manage, add the" +" following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:23 +msgid "" +"The database (as specified in `matrix_synapse_database_database`) must " +"exist and be accessible with the given credentials. It must be empty or " +"contain a valid Synapse database. If empty, Synapse would populate it the" +" first time it runs." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:25 +msgid "" +"**Note**: the external server that you specify in " +"`matrix_synapse_database_host` must be accessible from within the " +"`matrix-synapse` Docker container (and possibly other containers too). " +"This means that it either needs to be a publicly accessible hostname or " +"that it's a hostname on the same Docker network where all containers " +"installed by this playbook run (a network called `matrix` by default). " +"Using a local PostgreSQL instance on the host (running on the same " +"machine, but not in a container) is not possible." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:27 +msgid "" +"The connection to your external Postgres server **will not be SSL " +"encrypted**, as [we don't support that yet](https://github.com/spantaleev" +"/matrix-docker-ansible-deploy/issues/89)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po new file mode 100644 index 000000000..8056411de --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -0,0 +1,138 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-federation.md:1 +msgid "Controlling Matrix federation (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:3 +msgid "" +"By default, your server federates with the whole Matrix network. That is," +" people on your server can communicate with people on any other Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:5 +msgid "" +"**Note**: in the sample `vars.yml` " +"([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a " +"short user ID like `@alice:example.com` instead of " +"`@alice:matrix.example.com` and set up [server delegation](howto-server-" +"delegation.md) / redirection. Without a proper configuration, your server" +" will effectively not be part of the Matrix network. If you find your " +"server is not federated, make sure to [check whether services work" +"](maintenance-checking-services.md) and your server is properly " +"delegated." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:7 +msgid "Federating only with select servers" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:9 +msgid "" +"To make your server only federate with servers of your choosing, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:17 +msgid "" +"If you wish to disable federation, you can do that with an empty list " +"(`[]`), or better yet by completely disabling federation (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:19 +msgid "Exposing the room directory over federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:21 +msgid "" +"By default, your server's public rooms directory is not exposed to other " +"servers via federation." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:23 +msgid "" +"If you wish to expose it, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:29 +msgid "Disabling federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:31 +msgid "" +"To completely disable federation, isolating your server from the rest of " +"the Matrix network, add this to your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:37 +msgid "" +"With that, your server's users will only be able to talk among " +"themselves, but not to anyone who is on another server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:39 +msgid "" +"**Disabling federation does not necessarily disable the federation port**" +" (`8448`). Services like [Dimension](configuring-playbook-dimension.md) " +"and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs" +" exposed on that port. Even if you disable federation and only if " +"necessary, we may still be exposing the federation port and serving the " +"`openid` APIs there. To override this and completely disable Synapse's " +"federation port use:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:51 +msgid "" +"Changing the federation port from 8448 to a different port to use a CDN " +"that only accepts 443/80 ports" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:53 +msgid "" +"Why? This change could be useful for people running small Synapse " +"instances on small severs/VPSes to avoid being impacted by a simple " +"DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your " +"hosting provider does not provide a DOS/DDOS protection." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:55 +msgid "" +"The following changes in the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and " +"make it possible to proxy the federation through a CDN such as CloudFlare" +" or any other:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:66 +msgid "" +"**Use this at you own risk as all the possible side-effects of doing this" +" are not fully known. However, it has been tested and works fine and " +"passes all the tests on without " +"issues.**" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po new file mode 100644 index 000000000..e695de50c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -0,0 +1,556 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-jitsi.md:1 +msgid "Setting up the Jitsi video-conferencing platform (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:3 +msgid "" +"The playbook can install the [Jitsi](https://jitsi.org/) video-" +"conferencing platform and integrate it with Element clients ([Element Web" +"](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:5 +msgid "" +"Jitsi installation is **not enabled by default**, because it's not a core" +" component of Matrix services." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:7 +msgid "" +"The setup done by the playbook is very similar to [docker-jitsi-" +"meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the " +"documentation there for many of the options here." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:11 +msgid "You may need to open the following ports to your server:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:13 +msgid "`4443/tcp` - RTP media fallback over TCP" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:14 +msgid "" +"`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, " +"incoming RTP packets on port `10000` may have the external IP of your " +"firewall as destination address, due to the usage of STUN in JVB (see " +"[`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting" +"/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:16 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:18 +msgid "" +"To enable Jitsi, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:24 +msgid "Adjusting the Jitsi URL" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:26 +msgid "" +"By default, this playbook installs Jitsi on the `jitsi.` subdomain " +"(`jitsi.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:28 +msgid "" +"By tweaking the `jitsi_hostname` variable, you can easily make the " +"service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:30 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:37 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:39 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Jitsi domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:41 +msgid "" +"By default, you will need to create a CNAME record for `jitsi`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:43 +msgid "(Optional) Configure Jitsi authentication and guests mode" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:45 +msgid "" +"By default the Jitsi Meet instance does not require any kind of login and" +" is open to use for anyone without registration." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:47 +msgid "" +"If you're fine with such an open Jitsi instance, please skip to " +"[Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:49 +msgid "" +"If you would like to control who is allowed to open meetings on your new " +"Jitsi instance, then please follow the following steps to enable Jitsi's " +"authentication and optionally guests mode." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:51 +msgid "" +"Currently, there are three supported authentication modes: 'internal' " +"(default), 'matrix' and 'ldap'." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:53 +msgid "" +"**Note**: Authentication is not tested via the playbook's self-checks. We" +" therefore recommend that you manually verify if authentication is " +"required by jitsi. For this, try to manually create a conference on " +"jitsi.example.com in your browser." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:55 +msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:57 +msgid "" +"The default authentication mechanism is 'internal' auth, which requires " +"jitsi-accounts to be setup and is the recommended setup, as it also works" +" in federated rooms. With authentication enabled, all meeting rooms have " +"to be opened by a registered user, after which guests are free to join. " +"If a registered host is not yet present, guests are put on hold in " +"individual waiting rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:59 +msgid "" +"Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml`" +" configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:71 +msgid "" +"**Caution**: Accounts added here and subsequently removed will not be " +"automatically removed from the Prosody server until user account cleaning" +" is integrated into the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:73 +msgid "" +"**If you get an error** like this: \"Error: Account creation/modification" +" not supported.\", it's likely that you had previously installed Jitsi " +"without auth/guest support. In such a case, you should look into " +"[Rebuilding your Jitsi installation](#rebuilding-your-jitsi-" +"installation)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:75 +msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:77 +msgid "" +"**Attention: Probably breaks Jitsi in federated rooms and does not allow " +"sharing conference links with guests.**" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:79 +msgid "" +"Using this authentication type require a [Matrix User Verification " +"Service](https://github.com/matrix-org/matrix-user-verification-service)." +" By default, this playbook creates and configures a user-verification-" +"service to run locally, see [configuring-user-verification-service" +"](configuring-playbook-user-verification-service.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:81 +msgid "To enable set this configuration at host level:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:89 +msgid "" +"For more information see also [https://github.com/matrix-org/prosody-mod-" +"auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-" +"auth-matrix-user-verification)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:91 +msgid "Authenticate using LDAP (Auth-Type 'ldap')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:93 +msgid "An example LDAP configuration could be:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:113 +msgid "" +"For more information refer to the [docker-jitsi-" +"meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-" +"ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs" +"/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:115 +msgid "(Optional) Making your Jitsi server work on a LAN" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:117 +msgid "" +"By default the Jitsi Meet instance does not work with a client in LAN " +"(Local Area Network), even if others are connected from WAN. There are no" +" video and audio. In the case of WAN to WAN everything is ok." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:119 +msgid "" +"The reason is the Jitsi VideoBridge git to LAN client the IP address of " +"the docker image instead of the host. The " +"[documentation](https://jitsi.github.io/handbook/docs/devops-guide" +"/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of " +"Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment " +"variable to make it work." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:121 +msgid "Here is how to do it in the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:123 +msgid "" +"Add these two lines to your " +"`inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:130 +msgid "(Optional) Fine tune Jitsi" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:132 +msgid "" +"Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` " +"configuration to save up resources (explained below):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:147 +msgid "" +"You may want to **suspend unused video layers** until they are requested " +"again, to save up resources on both server and clients. Read more on this" +" feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-" +"feature/)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:149 +msgid "" +"You may wish to **disable audio levels** to avoid excessive refresh of " +"the client-side page and decrease the CPU consumption involved." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:151 +msgid "" +"You may want to **limit the number of video feeds forwarded to each " +"client**, to save up resources on both server and clients. As clients’ " +"bandwidth and CPU may not bear the load, use this setting to avoid lag " +"and crashes. This feature is found by default in other webconference " +"applications such as Office 365 Teams (limit is set to 4). Read how it " +"works [here](https://github.com/jitsi/jitsi-" +"videobridge/blob/master/doc/last-n.md) and performance evaluation on this" +" [study](https://jitsi.org/wp-" +"content/uploads/2016/12/nossdav2015lastn.pdf)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:153 +msgid "" +"You may want to **limit the maximum video resolution**, to save up " +"resources on both server and clients." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:155 +msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:157 +msgid "" +"The playbook allows a user to set a max number of participants allowed to" +" join a Jitsi conference. By default there is no limit." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:159 +msgid "" +"In order to set the max number of participants use the following " +"**additional** configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:165 +msgid "(Optional) Additional JVBs" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:167 +msgid "" +"By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi" +"/jitsi-videobridge)) is deployed on the same host as the Matrix server. " +"To allow more video-conferences to happen at the same time, you may need " +"to provision additional JVB services on other hosts." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:169 +msgid "" +"There is an ansible playbook that can be run with the following tag: " +"`ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers " +"jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:171 +msgid "" +"For this role to work you will need an additional section in the ansible " +"hosts file with the details of the JVB hosts, for example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:178 +msgid "" +"Each JVB will require a server ID to be set so that it can be uniquely " +"identified and this allows Jitsi to keep track of which conferences are " +"on which JVB. The server ID is set with the variable " +"`jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment " +"variables in the JVB docker container. This variable can be set via the " +"host file, a parameter to the ansible command or in the `vars.yaml` for " +"the host which will have the additional JVB. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:190 +msgid "" +"Note that the server ID `jvb-1` is reserved for the JVB instance running " +"on the Matrix host and therefore should not be used as the ID of an " +"additional jvb host." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:192 +msgid "" +"The additional JVB will also need to expose the colibri web socket port " +"and this can be done with the following variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:198 +msgid "" +"The JVB will also need to know where the prosody xmpp server is located, " +"similar to the server ID this can be set in the vars for the JVB by using" +" the variable `jitsi_xmpp_server`. The Jitsi prosody container is " +"deployed on the Matrix server by default so the value can be set to the " +"Matrix domain. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:204 +msgid "" +"However, it can also be set the ip address of the Matrix server. This can" +" be useful if you wish to use a private ip. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:210 +msgid "" +"For the JVB to be able to contact the XMPP server, the latter must expose" +" the XMPP port (5222). By default, the Matrix server does not expose the " +"port; only the XMPP container exposes it internally inside the host, " +"which means that the first JVB (which runs on the Matrix server) can " +"reach it but the additional JVB cannot. The port is exposed by setting " +"`jitsi_prosody_container_jvb_host_bind_port` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:216 +msgid "(The default is empty; if it's set then docker forwards the port.)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:218 +msgid "" +"Applied together this will allow you to provision extra JVB instances " +"which will register themselves with the prosody service and be available " +"for jicofo to route conferences too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:220 +msgid "" +"To make Traefik reverse-proxy to these additional JVBs (living on other " +"hosts), **you would need to add the following Traefik configuration " +"extension**:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:256 +msgid "(Optional) Enable Gravatar" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:258 +msgid "" +"In the default Jisti Meet configuration, gravatar.com is enabled as an " +"avatar service. This results in third party request leaking data to " +"gravatar. Since Element clients already send the url of configured Matrix" +" avatars to Jitsi, we disabled gravatar." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:260 +msgid "To enable Gravatar set:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:266 +msgid "" +"**Beware**: This leaks information to a third party, namely the Gravatar-" +"Service (unless configured otherwise: gravatar.com). Besides metadata, " +"this includes the Matrix user_id and possibly the room identifier (via " +"`referrer` header)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:268 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:270 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:277 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:279 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:281 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:283 +msgid "You can use the self-hosted Jitsi server in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:285 +msgid "" +"**by adding a widget to a room via Element Web** (the one configured by " +"the playbook at `https://element.example.com`). Just start a voice or a " +"video call in a room containing more than 2 members and that would create" +" a Jitsi widget which utilizes your self-hosted Jitsi server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:287 +msgid "" +"**by adding a widget to a room via the Dimension integration manager**. " +"You'll have to point the widget to your own Jitsi server manually. See " +"our [Dimension integration manager](./configuring-playbook-dimension.md) " +"documentation page for more details. Naturally, Dimension would need to " +"be installed first (the playbook doesn't install it by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:289 +msgid "" +"**directly (without any Matrix integration)**. Just go to " +"`https://jitsi.example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:291 +msgid "" +"**Note**: Element apps on mobile devices currently [don't support joining" +" meetings on a self-hosted Jitsi server](https://github.com/element-hq" +"/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md" +"#mobile-app-support)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:293 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:295 +msgid "Rebuilding your Jitsi installation" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:297 +msgid "" +"**If you ever run into any trouble** or **if you change configuration " +"(`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi " +"setup." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:299 +msgid "" +"We normally don't require such manual intervention for other services, " +"but Jitsi services generate a lot of configuration files on their own." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:301 +msgid "" +"These files are not all managed by Ansible (at least not yet), so you may" +" sometimes need to delete them all and start fresh." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:303 +msgid "To rebuild your Jitsi configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:305 +msgid "" +"ask Ansible to stop all Jitsi services: `just run-tags stop-group " +"--extra-vars=group=jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:306 +msgid "" +"SSH into the server and do this and remove all Jitsi configuration & data" +" (`rm -rf /matrix/jitsi`)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:307 +msgid "" +"ask Ansible to set up Jitsi anew and restart services (`just install-" +"service jitsi`)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po new file mode 100644 index 000000000..a02b8c7dd --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po @@ -0,0 +1,83 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-ldap-auth.md:1 +msgid "" +"Setting up the LDAP authentication password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:3 +msgid "" +"The playbook can install and configure the [matrix-synapse-" +"ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth " +"password provider for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:7 +msgid "" +"If you decide that you'd like to let this playbook install it for you, " +"add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:24 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:26 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:32 +msgid "Using ma1sd Identity Server for authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:34 +msgid "" +"If you wish to use the ma1sd Identity Server for LDAP authentication " +"instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-" +"synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration" +"](configuring-playbook-ma1sd.md#authentication)." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:36 +msgid "Handling user registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:38 +msgid "" +"If you wish for users to also be able to make new registrations against " +"LDAP, you may **also** wish to [set up the ldap-registration-proxy" +"](configuring-playbook-matrix-ldap-registration-proxy.md)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po new file mode 100644 index 000000000..c716e47a8 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -0,0 +1,334 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-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) to " +"learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:11 +msgid "" +"**Note**: enabling ma1sd, means that the `openid` API endpoints will be " +"exposed on the Matrix Federation port (usually `8448`), even if " +"[federation](configuring-playbook-federation.md) is disabled. It's " +"something to be aware of, especially in terms of firewall whitelisting " +"(make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:13 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:15 +msgid "" +"To make the ma1sd Identity Server enable its federation features, set up " +"a SRV record that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:17 +msgid "Name: `_matrix-identity._tcp` (use this text as-is)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:18 +msgid "" +"Content: `10 0 443 matrix.example.com` (replace `example.com` with your " +"own)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:20 +msgid "" +"See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-" +"and-your-privacy#choices-are-never-easy) for information on the privacy " +"implications of setting up this SRV record." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:22 +msgid "" +"**Note**: This `_matrix-identity._tcp` SRV record for the identity server" +" is different from the `_matrix._tcp` that can be used for Synapse " +"delegation. See [howto-server-delegation.md](howto-server-delegation.md) " +"for more information about delegation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:24 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:26 +msgid "" +"To enable ma1sd, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:32 +msgid "Matrix.org lookup forwarding" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:34 +msgid "" +"To ensure maximum discovery, you can make your identity server also " +"forward lookups to the central matrix.org Identity server (at the cost of" +" potentially leaking all your contacts information)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:36 +msgid "" +"Enabling this is discouraged and you'd better [learn " +"more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups)" +" before proceeding." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:38 +msgid "" +"To enable matrix.org forwarding, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:44 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:46 +msgid "" +"What this playbook configures for your is some bare minimum Identity " +"Server functionality, so that you won't need to rely on external 3rd " +"party services." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:48 +msgid "" +"A few variables can be toggled in this playbook to alter the ma1sd " +"configuration that gets generated." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:50 +msgid "" +"Still, ma1sd can do much more. You can refer to the [ma1sd " +"website](https://github.com/ma1uta/ma1sd) for more details and " +"configuration options." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:52 +msgid "" +"To use a more custom configuration, you can define a " +"`matrix_ma1sd_configuration_extension_yaml` string variable and put your " +"configuration in it. To learn more about how to do this, refer to the " +"information about `matrix_ma1sd_configuration_extension_yaml` in the " +"[default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) " +"of the ma1sd component." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:54 +msgid "Customizing email templates" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:56 +msgid "" +"If you'd like to change the default email templates used by ma1sd, take a" +" look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in " +"the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:58 +msgid "ma1sd-controlled Registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:60 +msgid "" +"To use the " +"[Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" +" feature of ma1sd, you can make use of the following variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:62 +msgid "" +"`matrix_synapse_enable_registration` - to enable user-initiated " +"registration in Synapse" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:64 +msgid "" +"`matrix_synapse_enable_registration_captcha` - to validate registering " +"users using reCAPTCHA, as described in the [enabling reCAPTCHA" +"](configuring-captcha.md) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:66 +msgid "" +"`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among" +" `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:68 +msgid "" +"variables prefixed with `matrix_ma1sd_container_labels_` (e.g. " +"`matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) " +"- to configure the Traefik reverse-proxy to capture and send registration" +" requests to ma1sd (instead of Synapse), so it can apply its additional " +"functionality" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:70 +msgid "" +"`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as " +"required. See the [Registration feature's " +"docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" +" for inspiration. Also see the [Additional features](#additional-" +"features) section below to learn more about how to use " +"`matrix_ma1sd_configuration_extension_yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:72 +msgid "" +"**Note**: For this to work, either the homeserver needs to [federate" +"](configuring-playbook-federation.md) or the `openid` APIs need to " +"exposed on the federation port. When federation is disabled and ma1sd is " +"enabled, we automatically expose the `openid` APIs (only!) on the " +"federation port. Make sure the federation port (usually " +"`https://matrix.example.com:8448`) is whitelisted in your firewall (even " +"if you don't actually use/need federation)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:74 +msgid "Authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:76 +msgid "" +"[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md)" +" provides the possibility to use your own [Identity " +"Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md)" +" (for example LDAP) to authenticate users on your Homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:78 +msgid "" +"To enable authentication against an LDAP server, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:98 +msgid "Example: SMS verification" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:100 +msgid "" +"If your use case requires mobile verification, it is quite simple to " +"integrate ma1sd with [Twilio](https://www.twilio.com/), an online " +"telephony services gateway. Their prices are reasonable for low-volume " +"projects and integration can be done with the following configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:114 +msgid "Example: Open Registration for every Domain" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:116 +msgid "" +"If you want to open registration for any domain, you have to setup the " +"allowed domains with ma1sd's `blacklist` and `whitelist`. The default " +"behavior when neither the `blacklist`, nor the `whitelist` match, is to " +"allow registration. Beware: you can't block toplevel domains (aka `.xy`) " +"because the internal architecture of ma1sd doesn't allow that." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:130 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:132 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:139 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:141 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:143 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:145 +msgid "" +"If email address validation emails sent by ma1sd are not reaching you, " +"you should look into [Adjusting email-sending settings](configuring-" +"playbook-email.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:147 +msgid "" +"If you'd like additional logging information, temporarily enable verbose " +"logging for ma1sd." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:149 +msgid "" +"To enable it, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po new file mode 100644 index 000000000..9d9eeb8ba --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po @@ -0,0 +1,1044 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-matrix-authentication-service.md:1 +msgid "Setting up Matrix Authentication Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3 +msgid "" +"This playbook can install and configure [Matrix Authentication " +"Service](https://github.com/element-hq/matrix-authentication-service/) " +"(MAS) - a service operating alongside your existing [Synapse" +"](./configuring-playbook-synapse.md) homeserver and providing [better " +"authentication, session management and permissions in " +"Matrix](https://matrix.org/blog/2023/09/better-auth/)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5 +msgid "" +"Matrix Authentication Service is an implementation of [MSC3861: Next-" +"generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com" +"/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, " +"tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7 +msgid "" +"**Before going through with starting to use Matrix Authentication " +"Service**, make sure to read:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9 +msgid "" +"the [Reasons to use Matrix Authentication Service](#reasons-to-use-" +"matrix-authentication-service) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10 +msgid "the [Expectations](#expectations) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11 +msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13 +msgid "" +"**If you've already been using Synapse** and have user accounts in its " +"database, you can [migrate to Matrix Authentication Service](#migrating-" +"an-existing-synapse-homeserver-to-matrix-authentication-service)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15 +msgid "Reasons to use Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17 +msgid "" +"You may be wondering whether you should make the switch to Matrix " +"Authentication Service (MAS) or keep using your existing authentication " +"flow via Synapse (password-based or [OIDC](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19 +msgid "" +"Matrix Authentication Service is **still an experimental service** and " +"**not a default** for this Ansible playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21 +msgid "" +"The [Expectations](#expectations) section contains a list of what works " +"and what doesn't (**some services don't work with MAS yet**), as well as " +"the **relative irreversability** of the migration process." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23 +msgid "" +"Below, we'll try to **highlight some potential reasons for switching** to" +" Matrix Authentication Service:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25 +msgid "" +"To use SSO in [Element X](https://element.io/blog/element-x-ignition/). " +"The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-" +"connect-for-single-sign-on) login flow is only supported in old Element " +"clients and will not be supported in Element X. Element X will only " +"support the new SSO-based login flow provided by MAS, so if you want to " +"use SSO with Element X, you will need to switch to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27 +msgid "" +"To help drive adoption of the \"Next-generation auth for Matrix\" by " +"switching to what's ultimately coming anyway" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29 +msgid "" +"To help discover (and potentially fix) MAS integration issues with this " +"Ansible playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31 +msgid "" +"To help discover (and potentially fix) MAS integration issues with " +"various other Matrix components (bridges, bots, clients, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33 +msgid "" +"To reap some of the security benefits that Matrix Authentication Service " +"offers, as outlined in the [Better authentication, session management and" +" permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) " +"article." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37 +msgid "" +"⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver " +"implementation (which is the default for this playbook). Other homeserver" +" implementations ([Dendrite](./configuring-playbook-dendrite.md), " +"[Conduit](./configuring-playbook-conduit.md), etc.) do not support " +"integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39 +msgid "" +"⚠️ **email sending** configured (see [Adjusting email-sending settings" +"](./configuring-playbook-email.md)), because **Matrix Authentication " +"Service [still insists](https://github.com/element-hq/matrix-" +"authentication-service/issues/1505) on having a verified email address " +"for each user** going through the new SSO-based login flow. It's also " +"possible to [work around email deliverability issues](#working-around-" +"email-deliverability-issues) if your email configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41 +msgid "" +"❌ **disabling all password providers** for Synapse (things like [shared-" +"secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth" +"](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-" +"playbook-ldap-auth.md), etc.) More details about this are available in " +"the [Expectations](#expectations) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43 +msgid "Expectations" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45 +msgid "" +"This section details what you can expect when switching to the Matrix " +"Authentication Service (MAS)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47 +msgid "" +"❌ **Synapse password providers will need to be disabled**. You can no " +"longer use [shared-secret-auth](./configuring-playbook-shared-secret-" +"auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth" +"](./configuring-playbook-ldap-auth.md), etc. When the authentication flow" +" is handled by MAS (not by Synapse anymore), it doesn't make sense to " +"extend the Synapse authentication flow with additional modules. Many " +"bridges used to rely on shared-secret-auth for doing double-puppeting " +"(impersonating other users), but most (at least the mautrix bridges) " +"nowadays use [Appservice Double Puppet](./configuring-playbook-" +"appservice-double-puppet.md) as a better alternative. Older/maintained " +"bridges may still rely on shared-secret-auth, as do other services like " +"[matrix-corporal](./configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49 +msgid "" +"❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-" +"admin.md) do not have full compatibility with MAS yet**. synapse-admin " +"already supports [login with access token](https://github.com/etkecc" +"/synapse-admin/pull/58), browsing users (which Synapse will internally " +"fetch from MAS) and updating user avatars. However, editing users " +"(passwords, etc.) now needs to happen directly against MAS using the [MAS" +" Admin API](https://element-hq.github.io/matrix-authentication-" +"service/api/index.html), which synapse-admin cannot interact with yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51 +msgid "❌ **Some services experience issues when authenticating via MAS**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53 +msgid "" +"[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first" +" time around, but it consistently fails after restarting:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55 +msgid "" +"cannot initialize matrix bot error=\"olm account is marked as shared, " +"keys seem to have disappeared from the server\"" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57 +msgid "" +"[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) " +"fails to start (see [element-hq/matrix-authentication-" +"service#3439](https://github.com/element-hq/matrix-authentication-" +"service/issues/3439))" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58 +msgid "Other services may be similarly affected. This list is not exhaustive." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60 +msgid "" +"❌ **Encrypted appservices** do not work yet (related to " +"[MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) " +"and [PR 17705 for Synapse](https://github.com/element-" +"hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will" +" fail to start (see [this issue](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/3658) for Hookshot). You can use these " +"bridges/bots only if you **keep end-to-bridge encryption disabled** " +"(which is the default setting)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62 +msgid "" +"⚠️ **You will need to have email sending configured** (see [Adjusting " +"email-sending settings](./configuring-playbook-email.md)), because " +"**Matrix Authentication Service [still insists](https://github.com" +"/element-hq/matrix-authentication-service/issues/1505) on having a " +"verified email address for each user** going through the new SSO-based " +"login flow. It's also possible to [work around email deliverability " +"issues](#working-around-email-deliverability-issues) if your email " +"configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64 +msgid "" +"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " +"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" +"authentication-service) is **possible**, but requires **some playbook-" +"assisted manual work**. Migration is **reversible with no or minor issues" +" if done quickly enough**, but as users start logging in (creating new " +"login sessions) via the new MAS setup, disabling MAS and reverting back " +"to the Synapse user database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66 +msgid "" +"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " +"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" +"authentication-service) does not currently seem to preserve the \"admin\"" +" flag for users (as found in the Synapse database). All users are " +"imported as non-admin - see [element-hq/matrix-authentication-" +"service#3440](https://github.com/element-hq/matrix-authentication-" +"service/issues/3440). You may need update the Matrix Authentication " +"Service's database manually and adjust the `can_request_admin` column in " +"the `users` table to `true` for users that need to be administrators " +"(e.g. `UPDATE users SET can_request_admin = true WHERE username = " +"'someone';`)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68 +msgid "" +"⚠️ Delegating user authentication to MAS causes **your Synapse server to " +"be completely dependant on one more service** for its operations. MAS is " +"quick & lightweight and should be stable enough already, but this is " +"something to keep in mind when making the switch." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70 +msgid "" +"⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " +"migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 " +"configuration](#upstream-oauth2-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72 +msgid "" +"⚠️ A [compatibility layer](https://element-hq.github.io/matrix-" +"authentication-service/setup/homeserver.html#set-up-the-compatibility-" +"layer) is installed - all `/_matrix/client/*/login` (etc.) requests will " +"be routed to MAS instead of going to the homeserver. This is done both " +"publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and " +"on the internal Traefik entrypoint (e.g. `https://matrix-" +"traefik:8008/_matrix/client/*/login`) which helps addon services reach " +"the homeserver's Client-Server API. You typically don't need to do " +"anything to make this work, but it's good to be aware of it, especially " +"if you have a [custom webserver setup](./configuring-playbook-own-" +"webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74 +msgid "" +"✅ Your **existing login sessions will continue to work** (you won't get " +"logged out). Migration will require a bit of manual work and minutes of " +"downtime, but it's not too bad." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76 +msgid "" +"✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), " +"[Element Web](./configuring-playbook-client-element-web.md), Element X, " +"FluffyChat) will be able to use the **new SSO-based login flow** provided" +" by Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78 +msgid "" +"✅ The **old login flow** (called `m.login.password`) **will still " +"continue to work**, so clients (old Element Web, etc.) and bridges/bots " +"that don't support the new OIDC-based login flow will still work. Going " +"through the old login flow does not require users to have a verified " +"email address, as [is the case](https://github.com/element-hq/matrix-" +"authentication-service/issues/1505) for the new SSO-based login flow." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80 +msgid "" +"✅ [Registering users](./registering-users.md) via **the playbook's " +"`register-user` tag remains unchanged**. The playbook automatically does " +"the right thing regardless of homeserver implementation (Synapse, " +"Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, " +"the playbook will forward user-registration requests to MAS. Registering " +"users via the command-line is no longer done via the " +"`/matrix/synapse/bin/register` script, but via `/matrix/matrix-" +"authentication-service/bin/register-user`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82 +msgid "" +"✅ Users that are prepared by the playbook (for bots, bridges, etc.) will " +"continue to be registered automatically as expected. The playbook " +"automatically does the right thing regardless of homeserver " +"implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or " +"not. When MAS is enabled, the playbook will forward user-registration " +"requests to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84 +msgid "Installation flows" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86 +msgid "New homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88 +msgid "" +"For new homeservers (which don't have any users in their Synapse database" +" yet), follow the [Adjusting the playbook configuration](#adjusting-the-" +"playbook-configuration) instructions and then proceed with " +"[Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90 +msgid "Existing homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92 +msgid "" +"Other homeserver implementations ([Dendrite](./configuring-playbook-" +"dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not " +"support integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94 +msgid "For existing Synapse homeservers:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96 +msgid "" +"when following the [Adjusting the playbook configuration](#adjusting-the-" +"playbook-configuration) instructions, make sure to **disable the " +"integration between Synapse and MAS** by **uncommenting** the " +"`matrix_authentication_service_migration_in_progress: true` line as " +"described in the [Marking an existing homeserver for migration](#marking-" +"an-existing-homeserver-for-migration) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98 +msgid "" +"then follow the [Migrating an existing Synapse homeserver to Matrix " +"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" +"matrix-authentication-service) instructions to perform the installation " +"and migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102 +msgid "" +"To enable Matrix Authentication Service, add the following configuration " +"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116 +msgid "" +"In the sub-sections that follow, we'll cover some additional " +"configuration options that you may wish to adjust." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118 +msgid "" +"There are many other configuration options available. Consult the " +"[`defaults/main.yml` file](../roles/custom/matrix-authentication-" +"service/defaults/main.yml) in the [matrix-authentication-service " +"role](../roles/custom/matrix-authentication-service/) to discover them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120 +msgid "Adjusting the Matrix Authentication Service URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122 +msgid "" +"By default, this playbook installs the Matrix Authentication Service on " +"the `matrix.` subdomain, at the `/auth` path " +"(https://matrix.example.com/auth). This makes it easy to install it, " +"because it **doesn't require additional DNS records to be set up**. If " +"that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:124 +msgid "" +"By tweaking the `matrix_authentication_service_hostname` and " +"`matrix_authentication_service_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:126 +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134 +msgid "Marking an existing homeserver for migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136 +msgid "" +"The [configuration above](#adjusting-the-playbook-configuration) " +"instructs existing users wishing to migrate to add " +"`matrix_authentication_service_migration_in_progress: true` to their " +"configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138 +msgid "" +"This is done temporarily. The migration steps are described in more " +"detail in the [Migrating an existing Synapse homeserver to Matrix " +"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" +"matrix-authentication-service) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140 +msgid "Upstream OAuth2 configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142 +msgid "" +"To make Matrix Authentication Service delegate to an existing upstream " +"OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` " +"setting](https://element-hq.github.io/matrix-authentication-" +"service/reference/configuration.html#upstream_oauth2providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144 +msgid "" +"The playbook exposes a " +"`matrix_authentication_service_config_upstream_oauth2_providers` variable" +" for controlling this setting." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261 +msgid "" +"💡 Refer to the [`upstream_oauth2.providers` setting](https://element-" +"hq.github.io/matrix-authentication-" +"service/reference/configuration.html#upstream_oauth2providers) for the " +"most up-to-date schema and example for providers. The value shown above " +"here may be out of date." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263 +msgid "" +"⚠️ The syntax for existing [OIDC providers configured in Synapse" +"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" +"sign-on) is slightly different, so you will need to adjust your " +"configuration when switching from Synapse OIDC to MAS upstream OAuth2." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265 +msgid "" +"⚠️ When [migrating an existing homeserver](#migrating-an-existing-" +"synapse-homeserver-to-matrix-authentication-service) which contains OIDC-" +"sourced users, you will need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267 +msgid "" +"[Configure upstream OIDC provider mapping for syn2mas](#configuring-" +"upstream-oidc-provider-mapping-for-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268 +msgid "" +"go through the [migrating an existing homeserver](#migrating-an-existing-" +"synapse-homeserver-to-matrix-authentication-service) process" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269 +msgid "" +"remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) " +"to prevent it being in conflict with the MAS OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Matrix Authentication Service domain to the " +"Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281 +msgid "" +"Now that you've [adjusted the playbook configuration](#adjusting-the-" +"playbook-configuration) and [your DNS records](#adjusting-dns-records), " +"you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294 +msgid "" +"If you're in the process of migrating an existing Synapse homeserver to " +"MAS, you should now follow the rest of the steps in the [Migrating an " +"existing Synapse homeserver to Matrix Authentication Service](#migrating-" +"an-existing-synapse-homeserver-to-matrix-authentication-service) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296 +msgid "" +"💡 After installation, you should [verify that Matrix Authentication " +"Service is installed correctly](#verify-that-matrix-authentication-" +"service-is-installed-correctly)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298 +msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300 +msgid "" +"Our migration guide is loosely based on the upstream [Migrating an " +"existing homeserver](https://element-hq.github.io/matrix-authentication-" +"service/setup/migration.html) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302 +msgid "" +"Migration is done via a tool called `syn2mas`, which the playbook could " +"run for you (in a container)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304 +msgid "The installation + migration steps are like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306 +msgid "" +"[Adjust your configuration](#adjusting-the-playbook-configuration) to " +"**disable the integration between the homeserver and MAS**. This is done " +"by **uncommenting** the " +"`matrix_authentication_service_migration_in_progress: true` line." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308 +msgid "Perform the initial [installation](#installing). At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310 +msgid "" +"Matrix Authentication Service will be installed. Its database will be " +"empty, so it cannot validate existing access tokens or authentication " +"users yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312 +msgid "" +"The homeserver will still continue to use its local database for " +"validating existing access tokens." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314 +msgid "" +"Various [compatibility layer URLs](https://element-hq.github.io/matrix-" +"authentication-service/setup/homeserver.html#set-up-the-compatibility-" +"layer) are not yet installed. New login sessions will still be forwarded " +"to the homeserver, which is capable of completing them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316 +msgid "" +"The `matrix-user-creator` role would be suppressed, so that it doesn't " +"automatically attempt to create users (for bots, etc.) in the MAS " +"database. These user accounts likely already exist in Synapse's user " +"database and could be migrated over (via syn2mas, as per the steps " +"below), so creating them in the MAS database would have been unnecessary " +"and potentially problematic (conflicts during the syn2mas migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318 +msgid "" +"Consider taking a full [backup of your Postgres database](./maintenance-" +"postgres.md#backing-up-postgresql). This is done just in case. The " +"**syn2mas migration tool does not delete any data**, so it should be " +"possible to revert to your previous setup by merely disabling MAS and re-" +"running the playbook (no need to restore a Postgres backup). However, do " +"note that as users start logging in (creating new login sessions) via the" +" new MAS setup, disabling MAS and reverting back to the Synapse user " +"database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320 +msgid "" +"[Migrate your data from Synapse to Matrix Authentication Service using " +"syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-" +"service-using-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322 +msgid "" +"[Adjust your configuration](#adjusting-the-playbook-configuration) again," +" to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324 +msgid "" +"remove the `matrix_authentication_service_migration_in_progress: false` " +"line" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326 +msgid "" +"if you had been using [OIDC providers configured in Synapse" +"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" +"sign-on), remove all Synapse OIDC-related configuration " +"(`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS " +"OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328 +msgid "Perform the [installation](#installing) again. At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330 +msgid "The homeserver will start delegating authentication to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332 +msgid "" +"The compatibility layer URLs will be installed. New login sessions will " +"be completed by MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334 +msgid "" +"[Verify that Matrix Authentication Service is installed correctly" +"](#verify-that-matrix-authentication-service-is-installed-correctly)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336 +msgid "" +"Migrate your data from Synapse to Matrix Authentication Service using " +"syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338 +msgid "" +"We **don't** ask you to [run the `syn2mas` migration advisor " +"command](https://element-hq.github.io/matrix-authentication-" +"service/setup/migration.html#run-the-migration-advisor), because it only " +"gives you the green light if your Synapse configuration " +"(`homeserver.yaml`) is configured in a way that's compatible with MAS " +"(delegating authentication to MAS; disabling Synapse's password config; " +"etc.). Until we migrate your data with the `syn2mas` tool, we " +"intentionally avoid doing these changes to allow existing user sessions " +"to work." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340 +msgid "" +"You can invoke the `syn2mas` tool via the playbook by running the " +"playbook's `matrix-authentication-service-syn2mas` tag. We recommend " +"first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " +"migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342 +msgid "Configuring syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344 +msgid "" +"If you're using [OIDC with Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " +"[Configuring upstream OIDC provider mapping for syn2mas](#configuring-" +"upstream-oidc-provider-mapping-for-syn2mas)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346 +msgid "" +"If you only have local (non-OIDC) users in your Synapse database, you can" +" likely run `syn2mas` as-is (without doing additional configuration " +"changes)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348 +msgid "" +"When you're done with potentially configuring `syn2mas`, proceed to doing" +" a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " +"migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350 +msgid "Configuring upstream OIDC provider mapping for syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352 +msgid "" +"If you have existing OIDC users in your Synapse user database (which will" +" be the case if when using [OIDC with Synapse](./configuring-playbook-" +"synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to " +"pass an additional `--upstreamProviderMapping` argument to the `syn2mas` " +"tool to tell it which provider (on the Synapse side) maps to which other " +"provider on the MAS side." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354 +msgid "If you don't do this, `syn2mas` would report errors like this one:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356 +msgid "" +"[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-" +"b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: " +"Unknown upstream provider oidc-keycloak]" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358 +msgid "Below is an example situation and a guide for how to solve it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360 +msgid "" +"If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) " +"named `keycloak`, in the Synapse database users would be associated with " +"the `oidc-keycloak` provider (note the `oidc-` prefix that was added " +"automatically by Synapse to your `idp_id` value)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362 +msgid "" +"The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` " +"on the MAS side, as defined in " +"`matrix_authentication_service_config_upstream_oauth2_providers` (see the" +" [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section " +"above)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364 +msgid "" +"To tell `syn2mas` how the Synapse-configured OIDC provider maps to the " +"new MAS-configured OIDC provider, add this additional configuration to " +"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373 +msgid "Performing a syn2mas dry-run" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375 +msgid "" +"Having [configured syn2mas](#configuring-syn2mas), we recommend doing a " +"[dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to " +"verify that everything will work out as expected." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377 +msgid "A dry-run would not cause downtime, because it avoids stopping Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379 +msgid "To perform a dry-run, run:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385 +msgid "" +"Observe the command output (especially the last line of the the syn2mas " +"output). If you are confident that the migration will work out as " +"expected, you can proceed with a [real migration](#performing-a-real-" +"syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387 +msgid "Performing a real syn2mas migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389 +msgid "Before performing a real migration make sure:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391 +msgid "you've familiarized yourself with the [expectations](#expectations)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393 +msgid "you've performed a Postgres backup, just in case" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395 +msgid "" +"you're aware of the irreversibility of the migration process without " +"disruption after users have created new login sessions via the new MAS " +"setup" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397 +msgid "" +"you've [configured syn2mas](#configuring-syn2mas), especially if you've " +"used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse" +"--openid-connect-for-single-sign-on)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399 +msgid "" +"you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and " +"don't see any issues in its output" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401 +msgid "" +"To perform a real migration, run the `matrix-authentication-service-" +"syn2mas` tag **without** the " +"`matrix_authentication_service_syn2mas_dry_run` variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407 +msgid "" +"Having performed a `syn2mas` migration once, trying to do it again will " +"report errors for users that were already migrated (e.g. \"Error: Unknown" +" upstream provider oauth-delegated\")." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409 +msgid "Verify that Matrix Authentication Service is installed correctly" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411 +msgid "" +"After [installation](#installing), run the `doctor` subcommand of the " +"[`mas-cli` command-line tool](https://element-hq.github.io/matrix-" +"authentication-service/reference/cli/index.html) to verify that MAS is " +"installed correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413 +msgid "You can do it:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415 +msgid "" +"either via the Ansible playbook's `matrix-authentication-service-mas-cli-" +"doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417 +msgid "" +"or by running the `mas-cli` script on the server (which invokes the `mas-" +"cli` tool inside a container): `/matrix/matrix-authentication-service/bin" +"/mas-cli doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419 +msgid "If successful, you should see some output that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431 +msgid "Management" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433 +msgid "" +"You can use the [`mas-cli` command-line tool](https://element-" +"hq.github.io/matrix-authentication-service/reference/cli/index.html) " +"(exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` " +"script) to perform administrative tasks against MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435 +msgid "This documentation page already mentions:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437 +msgid "" +"the `mas-cli doctor` sub-command in the [Verify that Matrix " +"Authentication Service is installed correctly](#verify-that-matrix-" +"authentication-service-is-installed-correctly) section, which you can run" +" via the CLI and via the Ansible playbook's `matrix-authentication-" +"service-mas-cli-doctor` tag" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439 +msgid "" +"the `mas-cli manage register-user` sub-command in the [Registering users" +"](./registering-users.md) documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441 +msgid "" +"There are other sub-commands available. Run `/matrix/matrix-" +"authentication-service/bin/mas-cli` to get an overview." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443 +msgid "User registration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445 +msgid "" +"After Matrix Authentication Service is [installed](#installing), users " +"need to be managed there (unless you're managing them in an [upstream " +"OAuth2 provider](#upstream-oauth2-configuration))." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447 +msgid "" +"You can register users new users as described in the [Registering users" +"](./registering-users.md) documentation (via `mas-cli manage register-" +"user` or the Ansible playbook's `register-user` tag)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449 +msgid "Working around email deliverability issues" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451 +msgid "" +"Because Matrix Authentication Service [still insists](https://github.com" +"/element-hq/matrix-authentication-service/issues/1505) on having a " +"verified email address for each user, you may need to work around email " +"deliverability issues if [your email-sending configuration" +"](./configuring-playbook-email.md) is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453 +msgid "" +"Matrix Authentication Service attempts to verify email addresses by " +"sending a verification email to the address specified by the user " +"whenever they log in to an account without a verified email address." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455 +msgid "" +"If email delivery is not working, **you can retrieve the email " +"configuration code from the Matrix Authentication Service's logs** " +"(`journalctl -fu matrix-authentication-service`)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457 +msgid "" +"Alternatively, you can use the [`mas-cli` management tool](#management) " +"to manually verify email addresses for users. Example: `/matrix/matrix-" +"authentication-service/bin/mas-cli manage verify-email some.username " +"email@example.com`" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po new file mode 100644 index 000000000..9e50af971 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po @@ -0,0 +1,184 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-matrix-corporal.md:1 +msgid "Setting up Matrix Corporal (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:5 +msgid "" +"**WARNING**: This is an advanced feature! It requires prior experience " +"with Matrix and a specific need for using [Matrix " +"Corporal](https://github.com/devture/matrix-corporal). If you're unsure " +"whether you have such a need, you most likely don't." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:9 +msgid "" +"The playbook can install and configure [matrix-" +"corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:11 +msgid "" +"In short, it's a sort of automation and firewalling service, which is " +"helpful if you're instaling Matrix services in a controlled corporate " +"environment. See that project's documentation to learn what it does and " +"why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:13 +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:14 +msgid "" +"(required) [set up the Shared Secret Auth password provider module" +"](configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +msgid "" +"(optional, but encouraged) [set up the REST authentication password " +"provider module](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:19 +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:72 +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:74 +msgid "" +"No matter what Matrix user ID you configure to run it with, make sure " +"that:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +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:78 +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:80 +msgid "Using a locally-stored static policy" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +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:114 +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:116 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +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:127 +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:129 +msgid "Matrix Corporal files" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +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:133 +msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +msgid "" +"`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " +"write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +msgid "" +"`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" +" and write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +msgid "" +"As an example: you can create your own configuration files in " +"`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " +"in the Docker container. Your configuration (stuff in " +"`matrix_corporal_policy_provider_config`) needs to refer to these files " +"via the local container paths - `/etc/matrix-corporal` (read-only), `/var" +"/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read " +"and write)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po new file mode 100644 index 000000000..6de48f670 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-ldap-registration-proxy.md:1 +msgid "Setting up matrix-ldap-registration-proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 +msgid "" +"The playbook can install and configure [matrix-ldap-registration-" +"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" +" for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 +msgid "This proxy handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 +msgid "" +"**Note**: This does support the full Matrix specification for " +"registrations. It only provide a very coarse implementation of a basic " +"password registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 +msgid "" +"If you already use the [synapse external password provider via LDAP" +"](configuring-playbook-ldap-auth.md) (that is, you have " +"`matrix_synapse_ext_password_provider_ldap_enabled: true` and other " +"options in your configuration) you can use the following values as " +"configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po new file mode 100644 index 000000000..0c5a8106b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po @@ -0,0 +1,256 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-matrix-media-repo.md:1 +msgid "Storing Matrix media files using matrix-media-repo (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:3 +msgid "" +"[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often " +"abbreviated \"MMR\") is a highly customizable multi-domain media " +"repository for Matrix. Intended for medium to large environments " +"consisting of several homeservers, this media repo de-duplicates media " +"(including remote media) while being fully compliant with the " +"specification." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:5 +msgid "" +"Smaller/individual homeservers can still make use of this project's " +"features, though it may be difficult to set up or have higher than " +"expected resource consumption. Please do your research before deploying " +"this as this project may not be useful for your environment." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:7 +msgid "" +"For a simpler alternative (which allows you to offload your media " +"repository storage to S3, etc.), you can [configure S3 storage" +"](configuring-playbook-s3.md) instead of setting up matrix-media-repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "**Table of Contents**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Quickstart](#quickstart)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "[Additional configuration options](#configuring-the-media-repo)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md +msgid "" +"[Importing data from an existing media store](#importing-data-from-an-" +"existing-media-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:15 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the " +"installation process](./installing.md) for the playbook:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:26 +msgid "" +"The repo is pre-configured for integrating with the Postgres database, " +"Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-" +"grafana.md) (if metrics enabled) from this playbook for all the available" +" homeserver roles. When the media repo is enabled, other media store " +"roles should be disabled (if using Synapse with other media store roles)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:28 +msgid "" +"By default, the media-repo will use the local filesystem for data " +"storage. You can alternatively use a `s3` cloud backend as well. Access " +"token caching is also enabled by default since the logout endpoints are " +"proxied through the media repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:30 +msgid "Configuring the media-repo" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:32 +msgid "Additional common configuration options:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:91 +msgid "" +"Full list of configuration options with documentation can be found in " +"[`roles/custom/matrix-media-" +"repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/blob/master/roles/custom/matrix-media-" +"repo/defaults/main.yml)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:93 +msgid "Signing Keys" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:95 +msgid "" +"Authenticated media endpoints ([MSC3916](https://github.com/matrix-org" +"/matrix-spec-proposals/pull/3916)) requires MMR to have a configured " +"signing key to authorize outbound federation requests. Additionally, the " +"signing key must be merged with your homeserver's signing key file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:97 +msgid "" +"The playbook default is to generate a MMR signing key when invoking the " +"setup role and merge it with your homeserver if you are using Synapse or " +"Dendrite. This can be disabled if desired by setting the option in your " +"inventory:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:103 +msgid "" +"If you wish to manually generate the signing key and merge it with your " +"homeserver's signing key file, see https://docs.t2bot.io/matrix-media-" +"repo/v1.3.5/installation/signing-key/ for more details." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:105 +msgid "" +"**Note that if you uninstall MMR from the playbook, it will not remove " +"the old MMR signing key from your homeserver's signing key file. You will" +" have to remove it manually.**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:107 +msgid "Key backup and revoking" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:109 +msgid "" +"Since your homeserver signing key file is modified by the playbook, a " +"backup will be created in " +"`HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to " +"remove/revoke old keys, you can restore from this backup or remove the " +"MMR key ID from your `example.com.signing.key` file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:111 +msgid "" +"Additionally, its recommended after revoking a signing key to update your" +" homeserver config file (`old_signing_keys` field for Synapse and " +"`old_private_keys` for Dendrite). See your homeserver config file for " +"further documentation on how to populate the field." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:113 +msgid "Importing data from an existing media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:115 +msgid "" +"If you want to add this repo to an existing homeserver managed by the " +"playbook, you will need to import existing media into MMR's database or " +"you will lose access to older media while it is active. MMR versions up " +"to `v1.3.3` only support importing from Synapse, but newer versions (at " +"time of writing: only `latest`) also support importing from Dendrite." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:117 +msgid "" +"**Before importing**: ensure you have an initial matrix-media-repo " +"deployment by following the [quickstart](#quickstart) guide above" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:119 +msgid "" +"Depending on the homeserver implementation yu're using (Synapse, " +"Dendrite), you'll need to use a different import tool (part of matrix-" +"media-repo) and point it to the homeserver's database." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:121 +msgid "Importing data from the Synapse media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:123 +msgid "" +"To import the Synapse media store, you're supposed to invoke the " +"`import_synapse` tool which is part of the matrix-media-repo container " +"image. Your Synapse database is called `synapse` by default, unless " +"you've changed it by modifying `matrix_synapse_database_database`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:125 +msgid "" +"This guide here is adapted from the [upstream documentation about the " +"import_synapse script](https://github.com/turt2live/matrix-media-repo" +"#importing-media-from-synapse)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:127 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:149 +msgid "" +"Run the following command on the server (after replacing " +"`postgres_connection_password` in it with the value found in your " +"`vars.yml` file):" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:139 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:161 +msgid "" +"Enter `1` for the Machine ID when prompted (you are not doing any " +"horizontal scaling) unless you know what you're doing." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:141 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:163 +msgid "" +"This should output a `msg=\"Import completed\"` when finished " +"successfully!" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:143 +msgid "Importing data from the Dendrite media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:145 +msgid "" +"If you're using the [Dendrite](configuring-playbook-dendrite.md) " +"homeserver instead of the default for this playbook (Synapse), follow " +"this importing guide here." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:147 +msgid "" +"To import the Dendrite media store, you're supposed to invoke the " +"`import_dendrite` tool which is part of the matrix-media-repo container " +"image. Your Dendrite database is called `dendrite_mediaapi` by default, " +"unless you've changed it by modifying " +"`matrix_dendrite_media_api_database`." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po new file mode 100644 index 000000000..3448174f7 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po @@ -0,0 +1,218 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-registration.md:1 +msgid "Setting up matrix-registration (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:3 +msgid "" +"The playbook can install and configure [matrix-" +"registration](https://github.com/ZerataX/matrix-registration) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:5 +msgid "" +"**WARNING**: this is a poorly maintained and buggy project. It's better " +"to avoid using it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:7 +msgid "" +"**WARNING**: this is not related to [matrix-registration-bot" +"](configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:9 +msgid "" +"matrix-registration is a simple python application to have a token based " +"Matrix registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:11 +msgid "" +"Use matrix-registration to **create unique registration links**, which " +"people can use to register on your Matrix server. It allows you to **keep" +" your server's registration closed (private)**, but still allow certain " +"people (these having a special link) to register a user account." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:13 +msgid "**matrix-registration** provides 2 things:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:15 +msgid "" +"**an API for creating registration tokens** (unique registration links). " +"This API can be used via `curl` or via the playbook (see [Usage](#usage) " +"below)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:17 +msgid "" +"**a user registration page**, where people can use these registration " +"tokens. By default, exposed at `https://matrix.example.com/matrix-" +"registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:19 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:21 +msgid "" +"To enable matrix-registration, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:30 +msgid "Adjusting the matrix-registration URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:32 +msgid "" +"By default, this playbook installs the matrix-registration on the " +"`matrix.` subdomain, at the `/matrix-registration` path " +"(https://matrix.example.com/matrix-registration). This makes it easy to " +"install it, because it **doesn't require additional DNS records to be set" +" up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:34 +msgid "" +"By tweaking the `matrix_registration_hostname` and " +"`matrix_registration_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:36 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:46 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the matrix-registration domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:48 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:50 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:54 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:67 +msgid "" +"**matrix-registration** gets exposed at `https://matrix.example.com" +"/matrix-registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:69 +msgid "" +"It provides various [APIs](https://github.com/ZerataX/matrix-" +"registration/wiki/api) - for creating registration tokens, listing " +"tokens, disabling tokens, etc. To make use of all of its capabilities, " +"consider using `curl`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:71 +msgid "We make the most common APIs easy to use via the playbook (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:73 +msgid "Creating registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:75 +msgid "To **create a new user registration token (link)**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:83 +msgid "" +"The above command creates and returns a **one-time use** token, which " +"**expires** on the 31st of December 2021. Adjust the `one_time` and " +"`ex_date` variables as you see fit." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:85 +msgid "" +"Share the unique registration link (generated by the command above) with " +"users to let them register on your Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:87 +msgid "Listing registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:89 +msgid "To **list the existing user registration tokens**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:96 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags list-matrix-registration-tokens`" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po new file mode 100644 index 000000000..c6c954d3f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po @@ -0,0 +1,259 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-mautrix-bridges.md:1 +msgid "Setting up a Generic Mautrix Bridge (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:3 +msgid "" +"The playbook can install and configure various " +"[mautrix](https://github.com/mautrix) bridges (twitter, facebook, " +"instagram, signal, hangouts, googlechat, etc.), as well as many other " +"(non-mautrix) bridges. This is a common guide for configuring mautrix " +"bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:5 +msgid "" +"You can see each bridge's features at in the `ROADMAP.md` file in its " +"corresponding [mautrix](https://github.com/mautrix) repository." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:9 +msgid "" +"To enable the bridge, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:16 +msgid "" +"There are some additional things you may wish to configure about the " +"bridge before you continue. Each bridge may have additional requirements " +"besides `_enabled: true`. For example, the mautrix-telegram bridge (our " +"documentation page about it is [here](configuring-playbook-bridge-" +"mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and " +"`matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each" +" bridge's individual documentation page for details about enabling " +"bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:18 +msgid "" +"To **configure a user as an administrator for all bridges**, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:24 +msgid "" +"**Alternatively** (more verbose, but allows multiple admins to be " +"configured), you can do the same on a per-bridge basis with:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:33 +msgid "encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:35 +msgid "" +"Encryption support is off by default. If you would like to enable " +"encryption, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:37 +msgid "**for all bridges with encryption support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:44 +#: ../../../docs/configuring-playbook-mautrix-bridges.md:61 +msgid "**Alternatively**, for a specific bridge:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:51 +msgid "relay mode" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:53 +msgid "" +"Relay mode is off by default. If you would like to enable relay mode, add" +" the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:55 +msgid "**for all bridges with relay mode support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:70 +msgid "" +"You can only have one " +"`matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in " +"`vars.yml` per bridge, so if you need multiple pieces of configuration " +"there, just merge them like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:82 +msgid "Setting the bot's username" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:88 +msgid "Can be used to set the username for the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:90 +msgid "Discovering additional configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:92 +msgid "" +"You may wish to look at `roles/custom/matrix-bridge-mautrix-" +"SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" +"mautrix-SERVICENAME/defaults/main.yml` to find other things you would " +"like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:94 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:96 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:103 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:105 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:107 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:109 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:111 +msgid "Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:113 +msgid "" +"To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-" +"puppeting.html) enable the [Appservice Double Puppet](configuring-" +"playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:115 +msgid "" +"The bridge automatically performs Double Puppeting if [Shared Secret Auth" +"](configuring-playbook-shared-secret-auth.md) is configured and enabled " +"on the server for this playbook by adding" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:121 +msgid "" +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:123 +msgid "Controlling the logging level" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:129 +msgid "" +"to `vars.yml` to control the logging level, where you may replace WARN " +"with one of the following to control the verbosity of the logs generated:" +" TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:131 +msgid "" +"If you have issues with a service, and are requesting support, the higher" +" levels of logging will generally be more helpful." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:133 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:135 +msgid "" +"To use the bridge, you need to start a chat with " +"`@SERVICENAMEbot:example.com` (where `example.com` is your base domain, " +"not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:137 +msgid "" +"Send `login` to the bridge bot to get started. You can learn more here " +"about authentication from the bridge's official documentation on " +"Authentication: " +"https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:139 +msgid "" +"If you run into trouble, check the [Troubleshooting](#troubleshooting) " +"section below." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:141 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:143 +msgid "" +"For troubleshooting information with a specific bridge, please see the " +"playbook documentation about it (some other document in in `docs/`) and " +"the upstream ([mautrix](https://github.com/mautrix)) bridge documentation" +" for that specific bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:145 +msgid "" +"Reporting bridge bugs should happen upstream, in the corresponding " +"mautrix repository, not to us." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po new file mode 100644 index 000000000..44ec0eb4a --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po @@ -0,0 +1,30 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-nginx.md:1 +msgid "Configure Nginx (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-nginx.md:3 +msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po new file mode 100644 index 000000000..e0c597e65 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -0,0 +1,354 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-ntfy.md:1 +msgid "Setting up the ntfy push notifications server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:3 +msgid "" +"The playbook can install and configure the [ntfy](https://ntfy.sh/) push " +"notifications server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:5 +msgid "" +"Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables " +"self-hosted (Google-free) push notifications from Matrix (and other) " +"servers to UnifiedPush-compatible Matrix compatible client apps running " +"on Android and other devices." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:7 +msgid "" +"This role is intended to support UnifiedPush notifications for use with " +"the Matrix and Matrix-related services that this playbook installs. This " +"role is not intended to support all of ntfy's other features." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:9 +msgid "" +"**Note**: In contrast to push notifications using Google's FCM or Apple's" +" APNs, the use of UnifiedPush allows each end-user to choose the push " +"notification server that they prefer. As a consequence, deploying this " +"ntfy server does not by itself ensure any particular user or device or " +"client app will use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:13 +msgid "" +"To enable ntfy, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:27 +msgid "" +"For a more complete list of variables that you could override, see the " +"[`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting" +"/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:29 +msgid "" +"For a complete list of ntfy config options that you could put in " +"`ntfy_configuration_extension_yaml`, see the [ntfy config " +"documentation](https://ntfy.sh/docs/config/#config-options)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:31 +msgid "Adjusting the ntfy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:33 +msgid "" +"By default, this playbook installs ntfy on the `ntfy.` subdomain " +"(`ntfy.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:35 +msgid "" +"By tweaking the `ntfy_hostname` variable, you can easily make the service" +" available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:37 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:46 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the ntfy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:48 +msgid "" +"By default, you will need to create a CNAME record for `ntfy`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:52 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:59 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:61 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:65 +msgid "" +"To make use of your ntfy installation, on Android for example, you need " +"two things:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:67 +msgid "the `ntfy` app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:68 +msgid "a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:70 +msgid "" +"You need to install the `ntfy` app on each device on which you want to " +"receive push notifications through your ntfy server. The `ntfy` app will " +"provide UnifiedPush notifications to any number of UnifiedPush-compatible" +" messaging apps installed on the same device." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:72 +msgid "Setting up the `ntfy` Android app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:74 +msgid "" +"Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) " +"from F-droid or Google Play." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:75 +msgid "" +"In its Settings -> `General: Default server`, enter your ntfy server URL," +" such as `https://ntfy.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:76 +msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:78 +msgid "" +"That is all you need to do in the ntfy app. It has many other features, " +"but for our purposes you can ignore them. In particular you do not need " +"to follow any instructions about subscribing to a notification topic as " +"UnifiedPush will do that automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:80 +msgid "Setting up a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:82 +msgid "" +"Install any UnifiedPush-enabled Matrix app on that same device. The " +"Matrix app will learn from the `ntfy` app that you have configured " +"UnifiedPush on this device, and then it will tell your Matrix server to " +"use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:84 +msgid "Steps needed for specific Matrix apps:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:86 +msgid "FluffyChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:87 +msgid "Should auto-detect and use it. No manual settings." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:89 +msgid "SchildiChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:90 +msgid "" +"enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push " +"gateway`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:91 +msgid "" +"choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push " +"distributor`. *(For info, a more complex alternative to achieve the same " +"is: delete the relevant unifiedpush registration in `ntfy` app, force-" +"close SchildiChat, re-open it.)*" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:92 +msgid "" +"verify `Settings` -> `Notifications` -> `UnifiedPush: Notification " +"targets` as described below in the \"Troubleshooting\" section." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:94 +msgid "Element-android v1.4.26+:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:95 +msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:96 +msgid "" +"verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification " +"settings`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:98 +msgid "" +"If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", " +"then choose \"ntfy\"." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:100 +msgid "" +"If the Matrix app doesn't seem to pick it up, try restarting it and try " +"the Troubleshooting section below." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:102 +msgid "Web App" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:104 +msgid "" +"ntfy also has a web app to subscribe to and push to topics from the " +"browser. This may be helpful to further troubleshoot UnifiedPush problems" +" or to use ntfy for other purposes. The web app only runs in the browser " +"locally (after downloading the JavaScript)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:106 +msgid "" +"The web app is disabled in this playbook by default as the expectation is" +" that most users won't use it. You can either use the [official hosted " +"one](https://ntfy.sh/app) (it supports using other public reachable ntfy " +"instances) or host it yourself by setting `ntfy_web_root: \"app\"` and " +"re-running Ansible." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:108 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:110 +msgid "" +"First check that the Matrix client app you are using supports " +"UnifiedPush. There may well be different variants of the app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:112 +msgid "" +"Set the ntfy server's log level to 'DEBUG', as shown in the example " +"settings above, and watch the server's logs with `sudo journalctl -fu " +"matrix-ntfy`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:114 +msgid "" +"To check if UnifiedPush is correctly configured on the client device, " +"look at \"Settings -> Notifications -> Notification Targets\" in Element " +"Android or SchildiChat Android, or \"Settings -> Notifications -> " +"Devices\" in FluffyChat. There should be one entry for each Matrix client" +" app that has enabled push notifications, and when that client is using " +"UnifiedPush you should see a URL that begins with your ntfy server's URL." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:116 +msgid "" +"In the \"Notification Targets\" screen in Element Android or SchildiChat " +"Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and " +"both should begin with your ntfy server's URL. If \"push\\_key\" shows " +"your server but \"Url\" shows an external server such as " +"`up.schildi.chat` then push notifications will still work but are being " +"routed through that external server before they reach your ntfy server. " +"To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you" +" must enable the `Force custom push gateway` setting as described in the " +"\"Usage\" section above." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:118 +msgid "" +"If it is not working, useful tools are \"Settings -> Notifications -> Re-" +"register push distributor\" and \"Settings -> Notifications -> " +"Troubleshoot Notifications\" in SchildiChat Android (possibly also " +"Element Android). In particular the \"Endpoint/FCM\" step of that " +"troubleshooter should display your ntfy server's URL that it has " +"discovered from the ntfy client app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:120 +msgid "" +"The simple [UnifiedPush " +"troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-" +"Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be" +" used to manually test UnifiedPush registration and operation on an " +"Android device." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po new file mode 100644 index 000000000..ac2916d9c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po @@ -0,0 +1,291 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-own-webserver.md:1 +msgid "" +"Using your own webserver, instead of this playbook's Traefik reverse-" +"proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:3 +msgid "" +"By default, this playbook installs its own [Traefik](https://traefik.io/)" +" reverse-proxy server (in a Docker container) which listens on ports 80 " +"and 443. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:5 +msgid "Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:7 +msgid "" +"[Traefik](https://traefik.io/) is the default reverse-proxy for the " +"playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 " +"purposes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:9 +msgid "" +"serving public traffic and providing SSL-termination with certificates " +"obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting " +"SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:11 +msgid "" +"assists internal communication between addon services (briges, bots, " +"etc.) and the homeserver via an internal entrypoint (`matrix-internal-" +"matrix-client-api`)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:13 +msgid "There are 2 ways to use Traefik with this playbook, as described below." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:15 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:17 +msgid "" +"To have the playbook install and use Traefik, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:25 +msgid "Traefik will manage SSL certificates for all services seamlessly." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:27 +msgid "Traefik managed by you" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:53 +msgid "" +"In this mode all roles will still have Traefik labels attached. You will," +" however, need to configure your Traefik instance and its entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:55 +msgid "" +"By default, the playbook configured a `default` certificate resolver and " +"multiple entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:57 +msgid "You need to configure 4 entrypoints for your Traefik server:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:59 +msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:60 +msgid "" +"`web-secure` (TCP port `443`) - used for exposing the Matrix Client-" +"Server API and all other services" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:61 +msgid "" +"`matrix-federation` (TCP port `8448`) - used for exposing the Matrix " +"Federation API" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:62 +msgid "" +"`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally " +"for addon services (bridges, bots) to communicate with the homserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:64 +msgid "" +"Below is some configuration for running Traefik yourself, although we " +"recommend using [Traefik managed by the playbook](#traefik-managed-by-" +"the-playbook)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:66 +msgid "" +"Note that this configuration on its own does **not** redirect traffic on " +"port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing " +"this in Traefik, it can be added to Traefik in a [file " +"provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:86 +msgid "" +"You can use the following `docker-compose.yml` as example to launch " +"Traefik." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:122 +msgid "Another webserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:124 +msgid "If you don't wish to use Traefik, you can also use your own webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:126 +msgid "Doing this is possible, but requires manual work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:128 +msgid "There are 2 ways to go about it:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:130 +msgid "" +"(recommended) [Fronting the integrated reverse-proxy webserver with " +"another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-" +"with-another-reverse-proxy) - using the playbook-managed reverse-proxy " +"(Traefik), but disabling SSL termination for it, exposing this reverse-" +"proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding " +"traffic from your own webserver to those few ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:132 +msgid "" +"(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-" +"reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed " +"reverse-proxy (Traefik), exposing services one by one using " +"`_host_bind_port` variables and forwarding traffic from your own " +"webserver to those ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:134 +msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:136 +msgid "" +"This method is about leaving the integrated reverse-proxy webserver be, " +"but making it not get in the way (using up important ports, trying to " +"retrieve SSL certificates, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:138 +msgid "" +"If you wish to use another webserver, the integrated reverse-proxy " +"webserver usually gets in the way because it attempts to fetch SSL " +"certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is" +" enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:140 +msgid "" +"You can disable such behavior and make the integrated reverse-proxy " +"webserver only serve traffic locally on the host itself (or over a local " +"network)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:142 +msgid "" +"This is the recommended way for using another reverse-proxy, because the " +"integrated one would act as a black box and wire all Matrix services " +"correctly. You would then only need to reverse-proxy a few individual " +"domains and ports over to it." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:144 +msgid "" +"To front Traefik with another reverse-proxy, you would need some " +"configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:194 +msgid "" +"Such a configuration would expose all services on a local port `81` and " +"Matrix Federation on a local port `8449`. Your reverse-proxy " +"configuration needs to send traffic to these ports. [`examples/reverse-" +"proxies`](../examples/reverse-proxies/) contains examples for various " +"webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy " +"Manager." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:196 +msgid "" +"It's important that these webservers proxy-pass requests to the correct " +"`ip:port` and also set the `Host` HTTP header appropriately. If you don't" +" pass the `Host` header correctly, Traefik will return a `404 - not " +"found` error." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:198 +msgid "To put it another way:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:199 +msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:200 +msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:202 +msgid "Using no reverse-proxy on the Matrix side at all" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:204 +msgid "" +"Instead of [Fronting the integrated reverse-proxy webserver with another " +"reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-" +"another-reverse-proxy), you can also go another way -- completely " +"disabling the playbook-managed Traefik reverse-proxy. You would then need" +" to reverse-proxy from your own webserver directly to each individual " +"Matrix service." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:206 +msgid "" +"This is more difficult, as you would need to handle the configuration for" +" each service manually. Enabling additional services would come with " +"extra manual work you need to do." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:208 +msgid "" +"Also, the Traefik reverse-proxy, besides fronting everything is also " +"serving a 2nd purpose of allowing addons services to communicate with the" +" Matrix homeserver thanks to its `matrix-internal-matrix-client-api` " +"entrypoint (read more about it above). Disabling Traefik completely means" +" the playbook would wire services to directly talk to the homeserver. " +"This can work for basic setups, but not for more complex setups involving" +" [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), " +"[matrix-corporal](./configuring-playbook-matrix-corporal.md) or other " +"such services that need to \"steal routes\" from the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:210 +msgid "" +"If your webserver is on the same machine, ensure your web server user " +"(something like `http`, `apache`, `www-data`, `nginx`) is part of the " +"`matrix` group. You should run something like this: `usermod -a -G matrix" +" nginx`. This allows your webserver user to access files owned by the " +"`matrix` group, so that it can serve static files from `/matrix/static-" +"files`." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po new file mode 100644 index 000000000..eaca549e9 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -0,0 +1,92 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-pantalaimon.md:1 +msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:3 +msgid "" +"The playbook can install and configure the " +"[pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy" +" daemon for you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-" +"org/pantalaimon) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:7 +msgid "" +"This role exposes Pantalaimon's API only within the container network, so" +" bots and clients installed on the same machine can use it. In particular" +" the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir" +"](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can " +"use it." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:17 +msgid "" +"The default configuration should suffice. For advanced configuration, you" +" can override the variables documented in the role's " +"[defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:21 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:28 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:30 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po new file mode 100644 index 000000000..2b01acb85 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po @@ -0,0 +1,182 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-postgres-backup.md:1 +msgid "Setting up postgres backup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:3 +msgid "" +"The playbook can install and configure [docker-postgres-backup-" +"local](https://github.com/prodrigestivill/docker-postgres-backup-local) " +"for you via the [ansible-role-postgres-backup](https://github.com/mother-" +"of-all-self-hosting/ansible-role-postgres-backup) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:5 +msgid "" +"For a more complete backup solution (one that includes not only Postgres," +" but also other configuration/data files), you may wish to look into " +"[BorgBackup](configuring-playbook-backup-borg.md) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:9 +msgid "" +"To enable Postgres backup, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:15 +msgid "" +"Refer to the table below for additional configuration variables and their" +" default values." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Default value" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`false`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "" +"Set to true to use [docker-postgres-backup-" +"local](https://github.com/prodrigestivill/docker-postgres-backup-local) " +"to create automatic database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_schedule`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`'@daily'`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Cron-schedule specifying the interval between postgres backups." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_days`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`7`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of daily backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_weeks`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`4`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of weekly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_keep_months`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`12`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Number of monthly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_base_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "`\"{{ postgres_backup_base_path }}/data\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md +msgid "Storage path for postgres-backup database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po new file mode 100644 index 000000000..a1364f30f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po @@ -0,0 +1,512 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-prometheus-grafana.md:1 +msgid "" +"Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server " +"(optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:3 +msgid "" +"The playbook can install [Grafana](https://grafana.com/) with " +"[Prometheus](https://prometheus.io/) and configure performance metrics of" +" your homeserver with graphs for you." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:7 +msgid "" +"To enable Grafana and/or Prometheus, add the following configuration to " +"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:33 +msgid "" +"The retention policy of Prometheus metrics is [15 days by " +"default](https://prometheus.io/docs/prometheus/latest/storage" +"/#operational-aspects). Older data gets deleted automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:35 +msgid "Adjusting the Grafana URL" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:37 +msgid "" +"By default, this playbook installs Grafana web user-interface on the " +"`stats.` subdomain (`stats.example.com`) and requires you to [adjust your" +" DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:39 +msgid "" +"By tweaking the `grafana_hostname` variable, you can easily make the " +"service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:41 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:48 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:50 +msgid "" +"Once you've decided on the domain, **you may need to adjust your DNS** " +"records to point the Grafana domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:52 +msgid "" +"By default, you will need to create a CNAME record for `stats`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:54 +msgid "" +"**Note**: It is possible to install Prometheus without installing " +"Grafana. This case it is not required to create the CNAME record." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:56 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:58 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:65 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:67 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:69 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Prometheus](https://prometheus.io) is a time series database. It holds " +"all the data we're going to talk about." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an " +"addon of sorts to Prometheus that collects generic system information " +"such as CPU, memory, filesystem, and even system temperatures" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an " +"addon of sorts to expose Postgres database metrics to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an " +"addon of sorts to expose NGINX logs to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"[Grafana](https://grafana.com/) is the visual component. It shows (on the" +" `stats.example.com` subdomain) the dashboards with the graphs that we're" +" interested in" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_anonymous_access`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"By default you need to log in to see graphs. If you want to publicly " +"share your graphs (e.g. when asking for help in " +"[`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org))" +" you'll want to enable this option." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"By default Grafana creates a user with `admin` as the username and " +"password. If you feel this is insecure and you want to change it " +"beforehand, you can do that here" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 +msgid "" +"Metrics and resulting graphs can contain a lot of information. This " +"includes system specs but also usage patterns. This applies especially to" +" small personal/family scale homeservers. Someone might be able to figure" +" out when you wake up and go to sleep by looking at the graphs over time." +" Think about this before enabling anonymous access. And you should really" +" not forget to change your Grafana password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:85 +msgid "" +"Most of our docker containers run with limited system access, but the " +"`prometheus-node-exporter` has access to the host network stack and " +"(readonly) root filesystem. This is required to report on them. If you " +"don't like that, you can set `prometheus_node_exporter_enabled: false` " +"(which is actually the default). You will still get Synapse metrics with " +"this container disabled. Both of the dashboards will always be enabled, " +"so you can still look at historical data after disabling either source." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:87 +msgid "Collecting metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 +msgid "" +"**If the integrated Prometheus server is enabled** (`prometheus_enabled: " +"true`), metrics are collected by it from each service via communication " +"that happens over the container network. Each service does not need to " +"expose its metrics \"publicly\"." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 +msgid "" +"When you'd like **to collect metrics from an external Prometheus " +"server**, you need to expose service metrics outside of the container " +"network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 +msgid "" +"The playbook provides a single endpoint " +"(`https://matrix.example.com/metrics/*`), under which various services " +"may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics" +"/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on" +" this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To " +"protect access using [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)," +" see `matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users` below." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 +msgid "" +"When using `matrix_metrics_exposure_enabled`, you don't need to expose " +"metrics for individual services one by one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:97 +msgid "The following variables may be of interest:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to **enable metrics exposure for all services** on " +"`https://matrix.example.com/metrics/*`. If you think this is too much, " +"refer to the helpful (but nonexhaustive) list of individual " +"`matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below " +"for exposing metrics on a per-service basis." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_http_basic_auth_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to protect all `https://matrix.example.com/metrics/*` " +"endpoints with [Basic " +"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" +" (see the other variables below for supplying the actual credentials). " +"When enabled, all endpoints beneath `/metrics` will be protected with the" +" same credentials" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_metrics_exposure_http_basic_auth_users`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to the Basic Authentication credentials (raw `htpasswd` file " +"content) used to protect `/metrics/*`. This htpasswd-file needs to be " +"generated with the `htpasswd` tool and can include multiple " +"username/password pairs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_synapse_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make Synapse expose metrics (locally, on the " +"container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_synapse_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose Synapse's metrics on " +"`https://matrix.example.com/metrics/synapse/main-process` and " +"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below" +"](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if" +" you're running a Synapse worker setup (`matrix_synapse_workers_enabled: " +"true`). To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the node (general system stats) exporter " +"(locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the node (general system stats) metrics on " +"`https://matrix.example.com/metrics/node-exporter`. To password-protect " +"the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the [Postgres exporter](configuring-" +"playbook-prometheus-postgres.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Postgres exporter](configuring-" +"playbook-prometheus-postgres.md) metrics on " +"`https://matrix.example.com/metrics/postgres-exporter`. To password-" +"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " +"above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to enable the [NGINX Log exporter](configuring-" +"playbook-prometheus-nginxlog.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-" +"sync-proxy.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_sliding_sync_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Sliding Sync](configuring-playbook-" +"sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics" +"/sliding-sync`. To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make [Hookshot](configuring-playbook-bridge-" +"hookshot.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-" +"hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To" +" password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_SERVICE_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Various other services/roles may provide similar `_metrics_enabled` and " +"`_metrics_proxying_enabled` variables for exposing their metrics. Refer " +"to each role for details. To password-protect the metrics, see " +"`matrix_metrics_exposure_http_basic_auth_users` above or " +"`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users`" +" variables provided by each role." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "`matrix_media_repo_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md +msgid "" +"Set this to `true` to make media-repo expose metrics (locally, on the " +"container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:118 +msgid "Collecting Synapse worker metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:120 +msgid "" +"If you are using workers (`matrix_synapse_workers_enabled: true`) and " +"have enabled `matrix_synapse_metrics_proxying_enabled` as described " +"above, the playbook will also automatically expose all Synapse worker " +"threads' metrics to " +"`https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` " +"corresponds to the worker `id` as exemplified in " +"`matrix_synapse_workers_enabled_list`." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:122 +msgid "" +"The playbook also generates an exemplary config file " +"(`/matrix/synapse/external_prometheus.yml.template`) with all the correct" +" paths which you can copy to your Prometheus server and adapt to your " +"needs. Make sure to edit the specified `password_file` path and contents " +"and path to your `synapse-v2.rules`. It will look a bit like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:152 +msgid "" +"[Enabling synapse-usage-exporter for Synapse usage statistics" +"](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:153 +msgid "" +"[Understanding Synapse Performance Issues Through Grafana Graphs](https" +"://element-" +"hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html)" +" at the Synapse Github Wiki" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:154 +msgid "" +"[The Prometheus scraping rules](https://github.com/element-" +"hq/synapse/tree/master/contrib/prometheus) (we use v2)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:155 +msgid "" +"[The Synapse Grafana dashboard](https://github.com/element-" +"hq/synapse/tree/master/contrib/grafana)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:156 +msgid "" +"[The Node Exporter dashboard](https://github.com/rfrail3/grafana-" +"dashboards) (for generic non-synapse performance graphs)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po new file mode 100644 index 000000000..3f33df892 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-prometheus-nginxlog.md:1 +msgid "Enabling metrics and graphs for NginX logs (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3 +msgid "" +"It can be useful to have some (visual) insight into " +"[nginx](https://nginx.org/) logs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5 +msgid "" +"This adds [prometheus-nginxlog-exporter](https://github.com/martin-" +"helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7 +msgid "" +"It will collect access logs from various nginx reverse-proxies which may " +"be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if " +"Synapse workers are enabled) and will make them available at a " +"Prometheus-compatible `/metrics` endpoint." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9 +msgid "" +"**Note**: nginx is only used internally by this Ansible playbook. With " +"Traefik being our default reverse-proxy, collecting nginx metrics is less" +" relevant." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11 +msgid "" +"To make use of this, you need to install [Prometheus](./configuring-" +"playbook-prometheus-grafana.md) either via the playbook or externally. " +"When using an external Prometheus, configuration adjustments are " +"necessary - see [Save metrics on an external Prometheus server](#save-" +"metrics-on-an-external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13 +msgid "" +"If your setup includes [Grafana](./configuring-playbook-prometheus-" +"grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:36 +msgid "Docker Image Compatibility" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38 +msgid "" +"At the moment of writing only images for `amd64` and `arm64` " +"architectures are available. The playbook currently does not support " +"[self-building](./self-building.md) a container image on other " +"architectures. You can however use a custom-build image by setting:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47 +msgid "" +"Metrics and resulting graphs can contain a lot of information. NginX logs" +" contain information like IP address, URLs, UserAgents and more. This " +"information can reveal usage patterns and could be considered Personally " +"Identifiable Information (PII). Think about this before enabling " +"(anonymous) access. Please make sure you change the default Grafana " +"password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49 +msgid "Save metrics on an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51 +msgid "" +"The playbook will automatically integrate the metrics into the " +"[Prometheus](./configuring-playbook-prometheus-grafana.md) server " +"provided with this playbook (if enabled). In such cases, the metrics " +"endpoint is not exposed publicly - it's only available on the container " +"network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53 +msgid "" +"When using an external Prometheus server, you'll need to expose metrics " +"publicly. See [Collecting metrics to an external Prometheus server" +"](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" +"external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55 +msgid "" +"You can either use " +"`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to " +"expose just this one service, or `matrix_metrics_exposure_enabled: true` " +"to expose all services." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57 +msgid "" +"Whichever way you go with, this service will expose its metrics endpoint " +"**without password-protection** at " +"`https://matrix.example.com/metrics/nginxlog` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59 +msgid "" +"For password-protection, use " +"(`matrix_metrics_exposure_http_basic_auth_enabled` and " +"`matrix_metrics_exposure_http_basic_auth_users`) or " +"(`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled`" +" and " +"`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po new file mode 100644 index 000000000..384f4fd51 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po @@ -0,0 +1,139 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-prometheus-postgres.md:1 +msgid "Enabling metrics and graphs for Postgres (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:3 +msgid "" +"Expanding on the metrics exposed by the [synapse exporter and the node " +"exporter](configuring-playbook-prometheus-grafana.md), the playbook " +"enables the [postgres exporter](https://github.com/prometheus-" +"community/postgres_exporter) that exposes more detailed information about" +" what's happening on your postgres database." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:7 +msgid "" +"To enable the postgres exporter, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:13 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:15 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:22 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:24 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:26 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"Enable the postgres prometheus exporter. This sets up the docker " +"container, connects it to the database and adds a 'job' to the prometheus" +" config which tells prometheus about this new exporter. The default is " +"'false'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_database_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"The 'username' for the user that the exporter uses to connect to the " +"database. The default is 'matrix_prometheus_postgres_exporter'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_database_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"The 'password' for the user that the exporter uses to connect to the " +"database. By default, this is auto-generated by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md +msgid "" +"If set to `true`, exposes the Postgres exporter metrics on " +"`https://matrix.example.com/metrics/postgres-exporter` for usage with an " +"[external Prometheus server](configuring-playbook-prometheus-grafana.md" +"#collecting-metrics-to-an-external-prometheus-server). To password-" +"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " +"on that other documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:35 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:37 +msgid "" +"[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) " +"(generic postgres dashboard)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po new file mode 100644 index 000000000..d12191917 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-rageshake.md:1 +msgid "Setting up the rageshake bug report server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:3 +msgid "" +"The playbook can install and configure the [rageshake](https://github.com" +"/matrix-org/rageshake) bug report server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:5 +msgid "" +"This is useful if you're developing your own applications and would like " +"to collect bug reports for them." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:9 +msgid "" +"To enable rageshake, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:15 +msgid "" +"rageshake has various options which don't have dedicated Ansible " +"variables. You can see the full list of options in the " +"[`rageshake.sample.yaml` file](https://github.com/matrix-" +"org/rageshake/blob/master/rageshake.sample.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:17 +msgid "" +"To set these, you can make use of the " +"`matrix_rageshake_configuration_extension_yaml` variable like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:27 +msgid "Adjusting the rageshake URL" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:29 +msgid "" +"By default, this playbook installs rageshake on the `rageshake.` " +"subdomain (`rageshake.example.com`) and requires you to [adjust your DNS " +"records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:31 +msgid "" +"By tweaking the `matrix_rageshake_hostname` and " +"`matrix_rageshake_path_prefix` variables, you can easily make the service" +" available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:33 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:46 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the rageshake domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:48 +msgid "" +"By default, you will need to create a CNAME record for `rageshake`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:50 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:54 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:61 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:63 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:67 +msgid "" +"Refer to the [rageshake documentation](https://github.com/matrix-" +"org/rageshake) for available APIs, etc." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po new file mode 100644 index 000000000..2a1d13324 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-rest-auth.md:1 +msgid "" +"Setting up the REST authentication password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:3 +msgid "" +"The playbook can install and configure [matrix-synapse-rest-" +"auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) " +"for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:19 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:21 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:29 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:36 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:38 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po new file mode 100644 index 000000000..d48c0f16c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po @@ -0,0 +1,129 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-riot-web.md:1 +msgid "Configuring Riot-web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:3 +msgid "" +"By default, this playbook **used to install** the [Riot-" +"web](https://github.com/element-hq/riot-web) Matrix client web " +"application." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:5 +msgid "" +"Riot has since been [renamed to Element](https://element.io/blog/welcome-" +"to-element/)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:7 +msgid "" +"to learn more about Element Web and its configuration, see our dedicated " +"[Configuring Element Web](configuring-playbook-client-element-web.md) " +"documentation page" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:8 +msgid "" +"to learn how to migrate from Riot to Element Web, see [Migrating to " +"Element Web](#migrating-to-element-web) below" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:10 +msgid "Migrating to Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:12 +msgid "Migrating your custom settings" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:14 +msgid "" +"If you have custom `matrix_riot_web_` variables in your " +"`inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to " +"rename them (`matrix_riot_web_` -> `matrix_client_element_`)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:16 +msgid "" +"Some other playbook variables (but not all) with `riot` in their name are" +" also renamed. The playbook checks and warns if you are using the old " +"name for some commonly used ones." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:18 +msgid "Domain migration" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:20 +msgid "" +"We used to set up Riot at the `riot.example.com` domain. The playbook now" +" sets up Element Web at `element.example.com` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:22 +msgid "There are a few options for handling this:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:24 +msgid "" +"(**avoiding changes** - using the old `riot.example.com` domain and " +"avoiding DNS changes) -- to keep using `riot.example.com` instead of " +"`element.example.com`, override the domain at which the playbook serves " +"Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:26 +msgid "" +"(**embracing changes** - using only `element.example.com`) - set up the " +"`element.example.com` DNS record (see [Configuring DNS](configuring-" +"dns.md)). You can drop the `riot.example.com` in this case." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:28 +msgid "Re-running the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:30 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:37 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:39 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po new file mode 100644 index 000000000..801a550f1 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po @@ -0,0 +1,248 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-s3-goofys.md:1 +msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:3 +msgid "" +"If you'd like to store Synapse's content repository (`media_store`) files" +" on Amazon S3 (or other S3-compatible service), you can let this playbook" +" configure [Goofys](https://github.com/kahing/goofys) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:5 +msgid "" +"Another (and better performing) way to use S3 storage with Synapse is " +"[synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-" +"provider.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:7 +msgid "" +"Using a Goofys-backed media store works, but performance may not be " +"ideal. If possible, try to use a region which is close to your Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:9 +msgid "" +"If you'd like to move your locally-stored media store data to Amazon S3 " +"(or another S3-compatible object store), we also provide some migration " +"instructions below." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:13 +msgid "" +"After [creating the S3 bucket and configuring it](configuring-" +"playbook-s3.md#bucket-creation-and-security-configuration), add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:23 +msgid "" +"You can use any S3-compatible object store by **additionally** " +"configuring these variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:30 +msgid "" +"If you have local media store files and wish to migrate to Backblaze B2 " +"subsequently, follow our [migration guide to Backblaze B2](#migrating-to-" +"backblaze-b2) below instead of applying this configuration as-is." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:32 +msgid "Migrating from local filesystem storage to S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:34 +msgid "" +"It's a good idea to [make a complete server backup](faq.md#how-do-i-back-" +"up-the-data-on-my-server) before migrating your local media store to an " +"S3-backed one." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:36 +msgid "" +"After making the backup, follow one of the guides below for a migration " +"path from a locally-stored media store to one stored on S3-compatible " +"storage:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:38 +msgid "" +"[Migrating to any S3-compatible storage (universal, but likely slow" +")](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:39 +msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:41 +msgid "Migrating to any S3-compatible storage (universal, but likely slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:43 +msgid "Proceed with the steps below without stopping Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:45 +msgid "" +"Start by adding the base S3 configuration in your `vars.yml` file (seen " +"above, may be different depending on the S3 provider of your choice)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:47 +msgid "" +"In addition to the base configuration you see above, add this to your " +"`vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:53 +msgid "" +"This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3" +"-media-store` without hooking it to your homeserver yet. Your homeserver " +"will still continue using your local filesystem for its media store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:55 +msgid "" +"Run the playbook to apply the changes: `ansible-playbook -i " +"inventory/hosts setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:57 +msgid "" +"Do an **initial sync of your files** by running this **on the server** " +"(it may take a very long time):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:63 +msgid "You may need to install `rsync` manually." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:65 +#: ../../../docs/configuring-playbook-s3-goofys.md:106 +msgid "" +"Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml " +"--tags=stop`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:67 +msgid "" +"Start the S3 service by running this **on the server**: `systemctl start " +"matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:69 +msgid "Sync the files again by re-running the `rsync` command you see in step #5" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:71 +msgid "" +"Stop the S3 service by running this **on the server**: `systemctl stop " +"matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:73 +#: ../../../docs/configuring-playbook-s3-goofys.md:114 +msgid "" +"Get the old media store out of the way by running this command on the " +"server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:79 +msgid "" +"Remove the `matrix_s3_media_store_path` configuration from your " +"`vars.yml` file (undoing step #3 above)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:81 +#: ../../../docs/configuring-playbook-s3-goofys.md:122 +msgid "" +"Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags" +"=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:83 +#: ../../../docs/configuring-playbook-s3-goofys.md:124 +msgid "" +"You're done! Verify that loading existing (old) media files works and " +"that you can upload new ones." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:85 +#: ../../../docs/configuring-playbook-s3-goofys.md:126 +msgid "" +"When confident that it all works, get rid of the local media store " +"directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:87 +msgid "Migrating to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:89 +msgid "" +"While all Matrix services are running, run the following command on the " +"server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:91 +msgid "(you need to adjust the 3 `--env` line below with your own data)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:104 +msgid "This is some initial file sync, which may take a very long time." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:108 +msgid "Run the command from step #1 again." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:110 +msgid "" +"Doing this will sync any new files that may have been created locally in " +"the meantime." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:112 +msgid "" +"Now that Matrix services aren't running, we're sure to get Backblaze B2 " +"and your local media store fully in sync." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:120 +msgid "" +"Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) " +"in your `vars.yml` file" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po new file mode 100644 index 000000000..afea36bc7 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -0,0 +1,314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-s3.md:1 +msgid "" +"Storing Synapse media files on Amazon S3 or another compatible Object " +"Storage (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:3 +msgid "" +"By default, this playbook configures your server to store Synapse's " +"content repository (`media_store`) files on the local filesystem. If " +"that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:5 +msgid "" +"As an alternative to storing media files on the local filesystem, you can" +" store them on [Amazon S3](https://aws.amazon.com/s3/) or another " +"S3-compatible object store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:7 +msgid "" +"You can do this either by sticking to Synapse's media repository and " +"making that use S3 (read below for this method), or by switching to an " +"external media storage implementation like [matrix-media-repo" +"](configuring-playbook-matrix-media-repo.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:9 +msgid "" +"First, [choose an Object Storage provider](#choosing-an-object-storage-" +"provider)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:11 +msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:13 +msgid "" +"Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys" +"](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider" +"](configuring-playbook-synapse-s3-storage-provider.md), or use s3 " +"datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-" +"media-repo/configuration/s3-datastore.html))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:15 +msgid "Choosing an Object Storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:17 +msgid "" +"You can create [Amazon S3](https://aws.amazon.com/s3/) or another " +"S3-compatible object storage like [Backblaze " +"B2](https://www.backblaze.com/b2/cloud-storage.html), " +"[Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean " +"Spaces](https://www.digitalocean.com/products/spaces), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:19 +msgid "" +"Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges" +" for storing too little data." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:21 +msgid "" +"All these providers have different prices, with Storj appearing to be the" +" cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress " +"fee is $0.007 per GB). Backblaze egress is free, but for only certain " +"users for up to 3x the amount of data stored. Beyond that you will pay " +"$0.01/GB of egress." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:23 +msgid "" +"Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which" +" becomes expensive if you need to store less data than that. Likewise, " +"Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of " +"2022-10)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:25 +msgid "Here are some of the important aspects of choosing the right provider:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:27 +msgid "" +"if a provider is a company you like and trust (or dislike less than the " +"others)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:28 +msgid "if a provider implements end-to-end encryption of your data" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:29 +msgid "" +"if a provider has a data region close to your Matrix server (if it's " +"farther away, high latency may cause slowdowns)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:30 +msgid "" +"if a provider's infrastructure such as data center is centralized or " +"distributed" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:31 +msgid "" +"if a provider's price model is transparent (whether it includes hidden " +"costs like minimum charge, minimum storage term, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:32 +msgid "" +"if a provider has free or cheap egress fee (in case you need to get the " +"data out often, for some reason) - likely not too important for the " +"common use-case" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:34 +msgid "Bucket creation and Security Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:36 +msgid "" +"Now that you've [chosen an Object Storage provider](#choosing-an-object-" +"storage-provider), you need to create a storage bucket." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:38 +msgid "" +"How you do this varies from provider to provider, with Amazon S3 being " +"the most complicated due to its vast number of services and complicated " +"security policies." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:40 +msgid "" +"Below, we provider some guides for common providers. If you don't see " +"yours, look at the others for inspiration or read some guides online " +"about how to create a bucket. Feel free to contribute to this " +"documentation with an update!" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:42 +msgid "Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:44 +msgid "" +"You'll need an Amazon S3 bucket and some IAM user credentials (access key" +" + secret key) with full write access to the bucket. Example IAM security" +" policy:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:65 +msgid "" +"**Note**: This policy needs to be attached to an IAM user created from " +"the **Security Credentials** menu. This is not a **Bucket Policy**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:67 +msgid "Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:69 +msgid "" +"To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) " +"you first need to sign up." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:71 +msgid "" +"You [can't easily change which region (US, Europe) your Backblaze account" +" stores files " +"in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/)," +" so make sure to carefully choose the region when signing up (hint: it's " +"a hard to see dropdown below the username/password fields in the signup " +"form)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:73 +msgid "After logging in to Backblaze:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:75 +msgid "" +"create a new **private** bucket through its user interface (you can call " +"it something like `matrix-example-media-store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:76 +msgid "" +"note the **Endpoint** for your bucket (something like `s3.us-" +"west-002.backblazeb2.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:77 +msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:78 +msgid "" +"go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the " +"**Add a New Application Key** to create a new one" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:79 +msgid "" +"restrict it to the previously created bucket (e.g. `matrix-example-media-" +"store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:80 +msgid "give it *Read & Write* access" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:82 +msgid "" +"The `keyID` value is your **Access Key** and `applicationKey` is your " +"**Secret Key**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:84 +msgid "" +"For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3" +"-synapse-storage-provider](configuring-playbook-synapse-s3-storage-" +"provider.md) you will need:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:86 +msgid "" +"**Endpoint URL** - this is the **Endpoint** value you saw above, but " +"prefixed with `https://`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:88 +msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:90 +msgid "" +"**Storage Class** - use `STANDARD`. Backblaze B2 does not have different " +"storage classes, so it doesn't make sense to use any other value." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:92 +msgid "Other providers" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:94 +msgid "" +"For other S3-compatible providers, you may not need to configure security" +" policies, etc. (just like for [Backblaze B2](#backblaze-b2))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:96 +msgid "" +"You most likely just need to create an S3 bucket and get some credentials" +" (access key and secret key) for accessing the bucket in a read/write " +"manner." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:98 +msgid "Setting up" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:100 +msgid "" +"To set up Synapse to store files in S3, follow the instructions for the " +"method of your choice:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:102 +msgid "" +"using [synapse-s3-storage-provider](configuring-playbook-synapse-s3" +"-storage-provider.md) (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:103 +msgid "" +"using [Goofys to mount the S3 store to the local filesystem](configuring-" +"playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:104 +msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po new file mode 100644 index 000000000..7c14374e6 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po @@ -0,0 +1,88 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-shared-secret-auth.md:1 +msgid "" +"Setting up the Shared Secret Auth password provider module (optional, " +"advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:3 +msgid "" +"The playbook can install and configure [matrix-synapse-shared-secret-" +"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:18 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:20 +msgid "" +"If you wish for users to **authenticate only against configured password " +"providers** (like this one), **without consulting Synapse's local " +"database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:35 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:37 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po new file mode 100644 index 000000000..751e3b1a0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po @@ -0,0 +1,174 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-sliding-sync-proxy.md:1 +msgid "Setting up the Sliding Sync proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 +msgid "" +"**Note**: The sliding-sync proxy is **not required** anymore as it's been" +" replaced with a different method (called Simplified Sliding Sync) which " +"is integrated into newer homeservers by default (**Conduit** homeserver " +"from version `0.6.0` or **Synapse** from version `1.114`). This component" +" and documentation remain here for historical purposes, but **installing " +"this old sliding-sync proxy is generally not recommended anymore**." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 +msgid "" +"The playbook can install and configure [sliding-sync](https://github.com" +"/matrix-org/sliding-sync) proxy for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 +msgid "" +"Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-" +"org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and " +"a prerequisite for running Element X clients ([Element X " +"iOS](https://github.com/element-hq/element-x-ios) and [Element X " +"Android](https://github.com/element-hq/element-x-android)). See the " +"project's [documentation](https://github.com/matrix-org/sliding-sync) to " +"learn more." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 +msgid "" +"To enable Sliding Sync proxy, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 +msgid "Adjusting the Sliding Sync proxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19 +msgid "" +"By default, this playbook installs the Sliding Sync proxy on the " +"`matrix.` subdomain, at the `/sliding-sync` path " +"(https://matrix.example.com/sliding-sync). This makes it easy to install " +"it, because it **doesn't require additional DNS records to be set up**. " +"If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:21 +msgid "" +"By tweaking the `matrix_sliding_sync_hostname` and " +"`matrix_sliding_sync_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:48 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:52 +msgid "External databases" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54 +msgid "" +"Please note that, if your setup utilizes an external database, you must " +"also establish configuration for the sliding sync proxy. Alter the " +"defaults below to suit your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66 +msgid "" +"You **don't need to do anything special** to make use of the Sliding Sync" +" proxy. Simply open your client which supports Sliding Sync (like Element" +" X) and log in." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68 +msgid "" +"When the Sliding Sync proxy is [installed](#installing), your `/.well-" +"known/matrix/client` file is also updated. A new " +"`org.matrix.msc3575.proxy` section and `url` property are added there and" +" made to point to your Sliding Sync proxy's base URL (e.g. " +"`https://matrix.example.com/sliding-sync`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70 +msgid "" +"This allows clients which support Sliding Sync to detect the Sliding Sync" +" proxy's URL and make use of it." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po new file mode 100644 index 000000000..70a3f345b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po @@ -0,0 +1,173 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-ssl-certificates.md:1 +msgid "Adjusting SSL certificate retrieval (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:3 +msgid "" +"By default, this playbook retrieves and auto-renews free SSL certificates" +" from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs " +"(e.g. `matrix.example.com` and others)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:5 +msgid "" +"This guide is about using the integrated Traefik server and doesn't apply" +" if you're using [your own webserver](configuring-playbook-own-" +"webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:7 +msgid "Using staging Let's Encrypt certificates instead of real ones" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:9 +msgid "" +"For testing purposes, you may wish to use staging certificates provide by" +" Let's Encrypt." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:11 +#: ../../../docs/configuring-playbook-ssl-certificates.md:21 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:17 +msgid "Disabling SSL termination" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:19 +msgid "" +"For testing or other purposes, you may wish to install services without " +"SSL termination and have services exposed to `http://` instead of " +"`https://`." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:27 +msgid "Using self-signed SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:29 +msgid "" +"If you'd like to use your own SSL certificates, instead of the default " +"(SSL certificates obtained automatically via " +"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" +" from [Let's Encrypt](https://letsencrypt.org/)):" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:31 +msgid "generate your self-signed certificate files" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:32 +msgid "" +"follow the [Using your own SSL certificates](#using-your-own-ssl-" +"certificates) documentation below" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:34 +msgid "Using your own SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:36 +msgid "To use your own SSL certificates with Traefik, you need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:38 +msgid "" +"disable " +"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" +" / [Let's Encrypt](https://letsencrypt.org/) support" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:39 +msgid "" +"put a custom Traefik configuration file on the server, with the help of " +"this Ansible playbook (via the [`aux` role](https://github.com/mother-of-" +"all-self-hosting/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:40 +msgid "" +"register your custom configuration file with Traefik, by adding an extra " +"provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:41 +msgid "" +"put the SSL files on the server, with the help of this Ansible playbook " +"(via the [`aux` role](https://github.com/mother-of-all-self-hosting" +"/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:89 +msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:91 +msgid "" +"You can configure Traefik to use the [DNS-01 challenge " +"type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for" +" Let's Encrypt. This is less commonly used than the default [HTTP-01 " +"challenge type](https://letsencrypt.org/docs/challenge-" +"types/#http-01-challenge), but it can be helpful to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:93 +msgid "hide your public IP from Let's Encrypt logs" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:94 +msgid "" +"allow you to obtain SSL certificates for servers which are not accessible" +" (via HTTP) from the public internet (and for which the HTTP-01 challenge" +" would fail)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:96 +msgid "" +"This is an example for how to edit the `vars.yml` file if you're using " +"Cloudflare:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:111 +msgid "" +"Make sure to change the value of \"provider\" to your particular DNS " +"solution, and provide the appropriate environment variables. The full " +"list of supported providers is available " +"[here](https://doc.traefik.io/traefik/https/acme/#providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:113 +msgid "" +"This example assumes you're using Cloudflare to manage your DNS zone. " +"Note that it requires the use of two tokens: one for reading all zones " +"(`CF_ZONE_API_TOKEN`) and another that must be able to edit the " +"particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's " +"recommended that you create two fine-grained tokens for this purpose, but" +" you might choose to use the same token for both." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po new file mode 100644 index 000000000..258e8279d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -0,0 +1,201 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-sygnal.md:1 +msgid "Setting up the Sygnal push gateway (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:3 +msgid "" +"The playbook can install and configure the [Sygnal](https://github.com" +"/matrix-org/sygnal) push gateway for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:5 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/sygnal) " +"to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:7 +msgid "" +"**Note**: most people don't need to install their own gateway. As " +"Sygnal's [Notes for application developers](https://github.com/matrix-" +"org/sygnal/blob/master/docs/applications.md) documentation says:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:9 +msgid "" +"It is not feasible to allow end-users to configure their own Sygnal " +"instance, because the Sygnal instance needs the appropriate FCM or APNs " +"secrets that belong to the application." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:11 +msgid "" +"This optional playbook component is only useful to people who " +"develop/build their own Matrix client applications themselves." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:15 +msgid "" +"To enable Sygnal, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:43 +msgid "" +"For a more complete example of available fields and values they can take," +" see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the " +"[upstream `sygnal.yaml.sample` configuration file](https://github.com" +"/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:45 +msgid "" +"Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) " +"is easier, as it only requires that you provide some config values." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:47 +msgid "" +"To configure [APNS](https://developer.apple.com/notifications/) (Apple " +"Push Notification Service), you'd need to provide one or more certificate" +" files. To do that, the above example configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:49 +msgid "" +"makes use of the [`aux` role](https://github.com/mother-of-all-self-" +"hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to " +"make the playbook install files into `/matrix/sygnal/data` (the " +"`matrix_sygnal_data_path` variable). See [`defaults/main.yml` " +"file](https://github.com/mother-of-all-self-hosting/ansible-role-" +"aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It" +" also makes sure the files are owned by `matrix:matrix`, so that Sygnal " +"can read them. Of course, you can also install these files manually " +"yourself, if you'd rather not use `aux`." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:51 +msgid "" +"references these files in the Sygnal configuration (`matrix_sygnal_apps`)" +" using a path like `/data/..` (the `/matrix/sygnal/data` directory on the" +" host system is mounted into the `/data` directory inside the container)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:53 +msgid "Adjusting the Sygnal URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:55 +msgid "" +"By default, this playbook installs Sygnal on the `sygnal.` subdomain " +"(`sygnal.example.com`) and requires you to [adjust your DNS records" +"](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:57 +msgid "" +"By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` " +"variables, you can easily make the service available at a **different " +"hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:59 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:70 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:72 +msgid "" +"Once you've decided on the domain and path, **you may need to adjust your" +" DNS** records to point the Sygnal domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:74 +msgid "" +"By default, you will need to create a CNAME record for `sygnal`. See " +"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:76 +msgid "" +"If you've decided to reuse the `matrix.` domain, you won't need to do any" +" extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:78 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:80 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:87 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:89 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:91 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:93 +msgid "" +"To make use of your Sygnal installation, you'd need to build your own " +"Matrix client application, which uses the same API keys (for " +"[GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and " +"certificates (for [APNS](https://developer.apple.com/notifications/)) and" +" is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:95 +msgid "" +"Refer to Sygnal's [Notes for application developers](https://github.com" +"/matrix-org/sygnal/blob/master/docs/applications.md) document." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po new file mode 100644 index 000000000..87d46a037 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -0,0 +1,206 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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://matrix-" +"org.github.io/dendrite/administration/adminapi) differs from [Synapse " +"Admin API](https://element-" +"hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:7 +msgid "" +"💡 **Note**: the latest version of synapse-admin is hosted by " +"[etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). " +"If you only need this service occasionally and trust giving your admin " +"credentials to a 3rd party Single Page Application, you can consider " +"using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:11 +msgid "" +"To enable Synapse Admin, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "" +"**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to" +" function. Access to them is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, for " +"additional security, we normally leave them unexposed, following " +"[official Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints). Because Synapse Admin needs these APIs to function, when " +"installing Synapse Admin, the playbook **automatically** exposes the " +"Synapse Admin API publicly for you. Depending on the homeserver " +"implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:19 +msgid "" +"for [Synapse](./configuring-playbook-synapse.md) (our default homeserver " +"implementation): " +"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +" true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:20 +msgid "" +"for [Dendrite](./configuring-playbook-dendrite.md): " +"`matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled:" +" true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:22 +msgid "" +"By default, synapse-admin installation will be [restricted to only work " +"with one homeserver](https://github.com/etkecc/synapse-" +"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" +"#restricting-available-homeserver) - the one managed by the playbook. To " +"adjust these restrictions, tweak the " +"`matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:24 +msgid "" +"⚠️ **Warning**: If you're using [Matrix Authentication Service" +"](./configuring-playbook-matrix-authentication-service.md) (MAS) for " +"authentication, you will be able to [log into synapse-admin with an " +"access token](https://github.com/etkecc/synapse-admin/pull/58), but " +"certain synapse-admin features (especially those around user management) " +"will be limited or not work at all." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:26 +msgid "Adjusting the Synapse Admin URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:28 +msgid "" +"By default, this playbook installs Synapse Admin on the `matrix.` " +"subdomain, at the `/synapse-admin` path (https://matrix.example.com" +"/synapse-admin). This makes it easy to install it, because it **doesn't " +"require additional DNS records to be set up**. If that's okay, you can " +"skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:30 +msgid "" +"By tweaking the `matrix_synapse_admin_hostname` and " +"`matrix_synapse_admin_path_prefix` variables, you can easily make the " +"service available at a **different hostname and/or path** than the " +"default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:32 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:42 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the Synapse Admin domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:46 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:50 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:57 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:59 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:63 +msgid "" +"After installation, Synapse Admin will be accessible at: " +"`https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:65 +msgid "" +"To use Synapse Admin, you need to have [registered at least one " +"administrator account](registering-users.md) on your server." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po new file mode 100644 index 000000000..acd1713e0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po @@ -0,0 +1,102 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-auto-accept-invite.md:1 +msgid "Setting up Synapse Auto Invite Accept (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 +msgid "" +"The playbook can install and configure [synapse-auto-invite-" +"accept](https://github.com/matrix-org/synapse-auto-accept-invite) for " +"you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 +msgid "" +"See that project's [documentation](https://github.com/matrix-org/synapse-" +"auto-accept-invite) to learn what it does and why it might be useful to " +"you. In short, it automatically accepts room invites. You can specify " +"that only 1:1 room invites are auto-accepted. Defaults to false if not " +"specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:7 +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:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +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:19 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +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:27 +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:29 +msgid "Native alternative" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +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:33 +msgid "Here's example configuration for using the **native** Synapse feature:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po new file mode 100644 index 000000000..a7359c3c0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po @@ -0,0 +1,108 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-auto-compressor.md:1 +msgid "Setting up synapse-auto-compressor (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 +msgid "" +"The playbook can install and configure " +"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" +"compress-state/#automated-tool-synapse_auto_compressor) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 +msgid "" +"It's a CLI tool that automatically compresses Synapse's `state_groups` " +"database table in the background." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 +msgid "" +"See the project's [documentation](https://github.com/matrix-org/rust-" +"synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn " +"what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 +msgid "" +"After installation, `synapse_auto_compressor` will run automatically " +"every day at `00:00:00` (as defined in " +"`matrix_synapse_auto_compressor_calendar` by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 +msgid "Manually start the tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 +msgid "" +"For testing your setup it can be helpful to not wait until 00:00. If you " +"want to run the tool immediately, log onto the server and run `systemctl " +"start matrix-synapse-auto-compressor`. Running this command will not " +"return control to your terminal until the compression run is done, which " +"may take a long time. Consider using " +"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " +"unstable." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po new file mode 100644 index 000000000..9fc0bf73d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po @@ -0,0 +1,381 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-s3-storage-provider.md:1 +msgid "" +"Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider" +" (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 +msgid "" +"If you'd like to store Synapse's content repository (`media_store`) files" +" on Amazon S3 (or other S3-compatible service), you can use the " +"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" +"-storage-provider) media provider module for Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 +msgid "" +"An alternative (which has worse performance) is to use [Goofys to mount " +"the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 +msgid "How it works?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 +msgid "" +"Summarized writings here are inspired by [this " +"article](https://quentin.dufour.io/blog/2021-09-14/matrix-" +"synapse-s3-storage/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 +msgid "The way media storage providers in Synapse work has some caveats:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 +msgid "" +"Synapse still continues to use locally-stored files (for creating " +"thumbnails, serving files, etc)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 +msgid "" +"the media storage provider is just an extra storage mechanism (in " +"addition to the local filesystem)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 +msgid "" +"all files are stored locally at first, and then copied to the media " +"storage provider (either synchronously or asynchronously)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 +msgid "" +"if a file is not available on the local filesystem, it's pulled from a " +"media storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 +msgid "" +"You may be thinking **if all files are stored locally as well, what's the" +" point**?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 +msgid "" +"You can run some scripts to delete the local files once in a while (which" +" we do automatically by default - see [Periodically cleaning up the local" +" filesystem](#periodically-cleaning-up-the-local-filesystem)), thus " +"freeing up local disk space. If these files are needed in the future (for" +" serving them to users, etc.), Synapse will pull them from the media " +"storage provider on demand." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 +msgid "" +"While you will need some local disk space around, it's only to " +"accommodate usage, etc., and won't grow as large as your S3 store." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 +msgid "" +"After [creating the S3 bucket and configuring it](configuring-" +"playbook-s3.md#bucket-creation-and-security-configuration), you can " +"proceed to configure `s3-storage-provider` in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 +msgid "" +"If you have existing files in Synapse's media repository " +"(`/matrix/synapse/media-store/..`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 +msgid "new files will start being stored both locally and on the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53 +msgid "" +"the existing files will remain on the local filesystem only until " +"[migrating them to the S3 store](#migrating-your-existing-media-files-to-" +"the-s3-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 +msgid "" +"at some point (and periodically in the future), you can delete local " +"files which have been uploaded to the S3 store already" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 +msgid "" +"Regardless of whether you need to [Migrate your existing files to the S3 " +"store](#migrating-your-existing-media-files-to-the-s3-store) or not, make" +" sure you've familiarized yourself with [How it works?](#how-it-works) " +"above and [Periodically cleaning up the local filesystem](#periodically-" +"cleaning-up-the-local-filesystem) below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 +msgid "Migrating your existing media files to the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60 +msgid "Migrating your existing data can happen in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 +msgid "" +"[using the `s3_media_upload` script from `synapse-s3-storage-provider" +"`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " +"(very slow when dealing with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 +msgid "" +"[using another tool in combination with `s3_media_upload`](#using-" +"another-tool-in-combination-with-s3_media_upload) (quicker when dealing " +"with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 +msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 +msgid "" +"Instead of using `s3_media_upload` directly, which is very slow and " +"painful for an initial data migration, we recommend [using another tool " +"in combination with `s3_media_upload`](#using-another-tool-in-" +"combination-with-s3_media_upload)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69 +msgid "" +"To copy your existing files, SSH into the server and run " +"`/matrix/synapse/ext/s3-storage-provider/bin/shell`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 +msgid "" +"This launches a Synapse container, which has access to the local media " +"store, Postgres database, S3 store and has some convenient environment " +"variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, " +"`UPDATE_DB_DAYS`, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 +msgid "" +"Then use the following commands (`$` values come from environment " +"variables - they're **not placeholders** that you need to substitute):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 +msgid "" +"`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite " +"database (`cache.db`) with a list of media repository files (from the " +"`synapse` Postgres database) eligible for operating on" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76 +msgid "" +"`$UPDATE_DB_DURATION` is influenced by the " +"`matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` " +"variable (defaults to `0`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 +msgid "" +"`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include " +"files which haven't been accessed for more than 0 days** (that is, **all " +"files will be included**)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 +msgid "" +"`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the " +"local cache still exist in the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 +msgid "" +"`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class " +"$STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files " +"to S3 and deletes them from the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 +msgid "The `s3_media_upload upload` command may take a lot of time to complete." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 +msgid "" +"Instead of running the above commands manually in the shell, you can also" +" run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script " +"which will run the same commands automatically. We demonstrate how to do " +"it manually, because:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 +msgid "" +"it's what the upstream project demonstrates and it teaches you how to use" +" the `s3_media_upload` tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 +msgid "" +"allows you to check and verify the output of each command, to catch " +"mistakes" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 +msgid "includes progress bars and detailed output for each command" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 +msgid "" +"allows you to easily interrupt slow-running commands, etc. (the " +"`/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container " +"without interactive TTY support, so `Ctrl+C` may not work and you and " +"require killing via `docker kill ..`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 +msgid "Using another tool in combination with `s3_media_upload`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92 +msgid "To migrate your existing local data to S3, we recommend to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 +msgid "" +"**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or " +"[`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files" +" to the S3 bucket" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 +msgid "" +"**only then** [use the `s3_media_upload` tool to finish the migration" +"](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " +"(this checks to ensure all files are uploaded and then deletes the local " +"files)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 +msgid "Copying data to Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100 +msgid "To copy to AWS S3, start a container on the Matrix server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112 +msgid "Copying data to an S3 alternative using the aws-s3 tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114 +msgid "" +"To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean " +"Spaces, etc.), you can use the command for [Copying data to Amazon S3" +"](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` " +"argument." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116 +msgid "" +"Add this argument to the command **as-is** (`$ENDPOINT` is an environment" +" variable corresponding to " +"`matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so " +"you don't need to touch it). Make sure to add the argument **before** the" +" final quote (`'`) of the command." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118 +msgid "Copying data to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 +msgid "" +"You can copy files to Backblaze B2 either by following the [Copying data " +"to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3" +"-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 " +"command-line " +"tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as " +"described below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 +msgid "" +"To copy the data using the `b2` tool, start a container on the Matrix " +"server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136 +msgid "Periodically cleaning up the local filesystem" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138 +msgid "" +"As described in [How it works?](#how-it-works) above, when new media is " +"uploaded to the Synapse homeserver, it's first stored locally and then " +"also stored on the remote S3 storage." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140 +msgid "" +"By default, we periodically ensure that all local files are uploaded to " +"S3 and are then removed from the local filesystem. This is done " +"automatically using:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142 +msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143 +msgid "" +".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` " +"service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 +msgid "" +".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` " +"timer, every day at 05:00" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 +msgid "So.. you don't need to perform any maintenance yourself." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po new file mode 100644 index 000000000..2e0c82766 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po @@ -0,0 +1,51 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-simple-antispam.md:1 +msgid "Setting up Synapse Simple Antispam (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 +msgid "" +"The playbook can install and configure [synapse-simple-" +"antispam](https://github.com/t2bot/synapse-simple-antispam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 +msgid "" +"See that project's documentation to learn what it does and why it might " +"be useful to you. In short, it lets you fight invite-spam by " +"automatically blocking invitiations from a list of servers specified by " +"you (blacklisting)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " +"needs):" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po new file mode 100644 index 000000000..15344e649 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po @@ -0,0 +1,156 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-usage-exporter.md:1 +msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 +msgid "" +"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" +"exporter) allows you to export the usage statistics of a Synapse " +"homeserver to this container service and for the collected metrics to " +"later be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 +msgid "" +"Synapse does not include usage statistics in its Prometheus metrics. They" +" can be reported to an HTTP `PUT` endpoint 5 minutes after startup and " +"from then on at a fixed interval of once every three hours. This role " +"integrates a simple [Flask](https://flask.palletsprojects.com) project " +"that offers an HTTP `PUT` endpoint and holds the most recent received " +"record available to be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 +msgid "Enabling this service will automatically:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 +msgid "install the synapse-usage-exporter service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 +msgid "" +"re-configure Synapse to push (via HTTP `PUT`) usage statistics " +"information to synapse-usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 +msgid "" +"re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) " +"(if Prometheus is enabled), to periodically scrape metrics from synapse-" +"usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 +msgid "" +"add a new [Grafana](./configuring-playbook-prometheus-grafana.md) " +"dashboard (if Grafana is enabled) containing Synapse usage statistics" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 +msgid "" +"To enable synapse-usage-exporter, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 +msgid "Adjusting the synapse-usage-exporter URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 +msgid "" +"By default, this playbook installs synapse-usage-exporter on the " +"`matrix.` subdomain, at the `/report-usage-stats/push` path " +"(https://matrix.example.com/report-usage-stats/push). This makes it easy " +"to install it, because it **doesn't require additional DNS records to be " +"set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 +msgid "" +"By tweaking the `matrix_synapse_usage_exporter_hostname` and " +"`matrix_synapse_usage_exporter_path_prefix` variables, you can easily " +"make the service available at a **different hostname and/or path** than " +"the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 +msgid "" +"Example additional configuration for your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45 +msgid "" +"If you've changed the default hostname, **you may need to adjust your " +"DNS** records to point the synapse-usage-exporter domain to the Matrix " +"server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 +msgid "" +"If you've decided to use the default hostname, you won't need to do any " +"extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 +msgid "" +"After configuring the playbook and potentially [adjusting your DNS " +"records](#adjusting-dns-records), run the playbook with [playbook tags" +"](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po new file mode 100644 index 000000000..309f23e01 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po @@ -0,0 +1,436 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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.md:1 +msgid "Configuring Synapse (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:3 +msgid "" +"By default, this playbook configures the [Synapse](https://github.com" +"/element-hq/synapse) Matrix server, so that it works for the general " +"case. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:5 +msgid "" +"The playbook provides lots of customization variables you could use to " +"change Synapse's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:7 +msgid "" +"Their defaults are defined in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml) and they ultimately end up in the generated " +"`/matrix/synapse/config/homeserver.yaml` file (on the server). This file " +"is generated from the [`roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:9 +msgid "" +"**If there's an existing variable** which controls a setting you wish to " +"change, you can simply define that variable in your configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " +"playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:11 +msgid "" +"Alternatively, **if there is no pre-defined variable** for a Synapse " +"setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:13 +msgid "" +"you can either **request a variable to be created** (or you can submit " +"such a contribution yourself). Keep in mind that it's **probably not a " +"good idea** to create variables for each one of Synapse's various " +"settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:15 +msgid "" +"or, you can **extend and override the default configuration** " +"([`homeserver.yaml.j2`](../roles/custom/matrix-" +"synapse/templates/synapse/homeserver.yaml.j2)) by making use of the " +"`matrix_synapse_configuration_extension_yaml` variable. You can find " +"information about this in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:17 +msgid "" +"or, if extending the configuration is still not powerful enough for your " +"needs, you can **override the configuration completely** using " +"`matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). " +"You can find information about this in [`roles/custom/matrix-" +"synapse/defaults/main.yml`](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:19 +msgid "Load balancing with workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:21 +msgid "" +"To have Synapse gracefully handle thousands of users, worker support " +"should be enabled. It factors out some homeserver tasks and spreads the " +"load of incoming client and server-to-server traffic between multiple " +"processes. More information can be found in the [official Synapse workers" +" documentation](https://github.com/element-" +"hq/synapse/blob/master/docs/workers.md) and [Tom " +"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " +"guide](https://tcpipuk.github.io/synapse/index.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:23 +msgid "" +"To enable Synapse worker support, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:31 +msgid "" +"By default, this enables the `one-of-each` [worker preset](#worker-" +"presets), but you may wish to use another preset or [control the number " +"of worker instances](#controlling-the-number-of-worker-instances)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:33 +msgid "Worker presets" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:35 +msgid "" +"We support a few configuration presets (`matrix_synapse_workers_preset: " +"one-of-each` being the default configuration right now):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:37 +msgid "" +"(federation-only) `little-federation-helper` - a very minimal worker " +"configuration to improve federation performance" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:38 +msgid "" +"(generic) `one-of-each` - defaults to one worker of each supported type -" +" no smart routing, just generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:39 +msgid "" +"(specialized) `specialized-workers` - defaults to one worker of each " +"supported type, but disables generic workers and uses [specialized " +"workers](#specialized-workers) instead" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:41 +msgid "" +"These presets represent a few common configurations. There are many " +"worker types which can be mixed and matched based on your needs." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:43 +msgid "Generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:45 +msgid "" +"Previously, the playbook only supported the most basic type of load-" +"balancing. We call it **generic load-balancing** below, because incoming " +"HTTP requests are sent to a generic worker. Load-balancing was done based" +" on the requestor's IP address. This is simple, but not necessarily " +"optimal. If you're accessing your account from multiple IP addresses " +"(e.g. your mobile phone being on a different network than your PC), these" +" separate requests may potentially be routed to different workers, each " +"of which would need to cache roughly the same data." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:47 +msgid "" +"This is **still the default load-balancing method (preset) used by the " +"playbook**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:49 +msgid "" +"To use generic load-balancing, do not specify " +"`matrix_synapse_workers_preset` to make it use the default value (`one-" +"of-each`), or better yet - explicitly set it as `one-of-each`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:51 +msgid "" +"You may also consider [tweaking the number of workers of each type" +"](#controlling-the-number-of-worker-instances) from the default (one of " +"each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:53 +msgid "Specialized workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:55 +msgid "" +"The playbook now supports a smarter **specialized load-balancing** " +"inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse " +"homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead " +"of routing requests to one or more [generic workers](#generic-workers) " +"based only on the requestor's IP adddress, specialized load-balancing " +"routes to **4 different types of specialized workers** based on **smarter" +" criteria** - the access token (username) of the requestor and/or on the " +"resource (room, etc.) being requested." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:57 +msgid "The playbook supports these **4 types** of specialized workers:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:59 +msgid "" +"Room workers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) & " +"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs " +"dedicated to handling specific rooms" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:60 +msgid "" +"Sync workers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to " +"synchronization (most notably [the `/sync` " +"endpoint](https://spec.matrix.org/v1.9/client-server-" +"api/#get_matrixclientv3sync))" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:61 +msgid "" +"Client readers - handles various [Client-" +"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are " +"not for specific rooms (handled by **room workers**) or for " +"synchronization (handled by **sync workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:62 +msgid "" +"Federation readers - handles various " +"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which " +"are not for specific rooms (handled by **room workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:64 +msgid "" +"To use specialized load-balancing, consider enabling the `specialized-" +"workers` [worker preset](#worker-presets) and potentially [tweaking the " +"number of workers of each type](#controlling-the-number-of-worker-" +"instances) from the default (one of each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:66 +msgid "Controlling the number of worker instances" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:68 +msgid "" +"If you'd like more customization power, you can start with one of the " +"[worker presets](#worker-presets) and then tweak various " +"`matrix_synapse_workers_*_count` variables manually." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:70 +msgid "" +"To find what variables are available for you to override in your own " +"`vars.yml` configuration file, see the [`defaults/main.yml` file for the " +"`matrix-synapse` Ansible role](../roles/custom/matrix-" +"synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:72 +msgid "" +"The only thing you **cannot** do is mix [generic workers](#generic-" +"workers) and [specialized workers](#specialized-workers)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:74 +msgid "Effect of enabling workers on the rest of your server" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:76 +msgid "" +"When Synapse workers are enabled, the integrated [Postgres database is " +"tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum " +"number of Postgres connections are increased from `200` to `500`. If you " +"need to decrease or increase the number of maximum Postgres connections " +"further, use the `postgres_max_connections` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:78 +msgid "" +"A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and " +"component handles load-balancing for workers. This role/component is " +"automatically enabled when you enable workers. Make sure to use the " +"`setup-all` tag (not `install-all`!) during the playbook's " +"[installation](./installing.md) process, especially if you're disabling " +"workers, so that components may be installed/uninstalled correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:80 +msgid "" +"In case any problems occur, make sure to have a look at the [list of " +"synapse issues about workers](https://github.com/element-" +"hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit " +"'matrix-*'`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:82 +msgid "Synapse Admin" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:84 +msgid "" +"Certain Synapse administration tasks (managing users and rooms, etc.) can" +" be performed via a web user-interace, if you install [Synapse Admin" +"](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:86 +msgid "Synapse + OpenID Connect for Single-Sign-On" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:88 +msgid "" +"💡 An alternative to setting up OIDC in Synapse is to use [Matrix " +"Authentication Service](./configuring-playbook-matrix-authentication-" +"service.md) (MAS). Newer clients (like Element X) only support SSO-based " +"authentication via MAS and not via the legacy Synapse OIDC setup " +"described below. That said, MAS is still a new experimental service which" +" comes with its own downsides. Consult its documentation to learn if it " +"will be a good fit for your deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:90 +msgid "" +"If you'd like to use OpenID Connect authentication with Synapse, you'll " +"need some additional configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:92 +msgid "" +"This example configuration is for [keycloak](https://www.keycloak.org/), " +"an opensource Identity Provider maintained by Red Hat." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:94 +msgid "" +"For more detailed documentation on available options and how to setup " +"keycloak, see the [Synapse documentation on OpenID Connect with " +"keycloak](https://github.com/element-" +"hq/synapse/blob/develop/docs/openid.md#keycloak)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:96 +#, python-format +msgid "" +"In case you encounter errors regarding the parsing of the variables, you " +"can try to add `{% raw %}` and `{% endraw %}` blocks around them. For " +"example ;" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:117 +msgid "Customizing templates" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:119 +msgid "" +"[Templates](https://github.com/element-" +"hq/synapse/blob/develop/docs/templates.md) are used by Synapse for " +"showing **certain web pages** handled by the server, as well as for " +"**email notifications**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:121 +msgid "" +"This playbook allows you to customize the default templates (see the " +"[`synapse/res/templates` directory](https://github.com/element-" +"hq/synapse/tree/develop/synapse/res/templates))." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:123 +msgid "" +"If template customization is enabled, the playbook will build a custom " +"container image based on the official one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:125 +msgid "" +"Your custom templates need to live in a public or private git repository." +" This repository will be cloned during Synapse image customization " +"(during the playbook run)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:127 +msgid "" +"To enable template customizations, use a configuration " +"(`inventory/host_vars/matrix.example.com/vars.yml`) like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:153 +msgid "" +"As mentioned in Synapse's Templates documentation, Synapse will fall back" +" to its own templates if a template is not found in that directory. Due " +"to this, it's recommended to only store and maintain template files in " +"your repository if you need to make custom changes. Other files (which " +"you don't need to change), should not be duplicated, so that you don't " +"need to worry about getting out-of-sync with the original Synapse " +"templates." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:155 +msgid "Monitoring Synapse Metrics with Prometheus and Grafana" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:157 +msgid "" +"This playbook allows you to enable Synapse metrics, which can provide " +"insight into the performance and activity of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:159 +msgid "" +"To enable Synapse runtime metrics see: [Enabling metrics and graphs " +"(Prometheus, Grafana) for your Matrix server](configuring-playbook-" +"prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:161 +msgid "" +"To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter " +"for Synapse usage statistics](configuring-playbook-synapse-usage-" +"exporter.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po new file mode 100644 index 000000000..e0d7c0b9c --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po @@ -0,0 +1,74 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-telemetry.md:1 +msgid "Enabling Telemetry for your Matrix server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:3 +msgid "" +"By default, this playbook configures your Matrix homeserver to not send " +"any telemetry data anywhere." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:5 +msgid "" +"The [matrix.org](https://matrix.org) team would really appreciate it if " +"you could help the project out by reporting usage statistics from your " +"homeserver. Enabling usage statistics helps track the growth of the " +"Matrix community, and helps to make Matrix a success." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:7 +msgid "Enabling Telemetry" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:9 +msgid "" +"If you'd like to **help by enabling submission of general usage " +"statistics** for your homeserver, add the following configuration to your" +" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:17 +msgid "Usage statistics being submitted" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:19 +msgid "" +"When enabled, your homeserver will regularly upload a few dozen " +"statistics about your server. This data includes your homeserver's " +"domain, the total number of users, the number of active users, the total " +"number of rooms, and the number of messages sent per day on your " +"homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:21 +msgid "" +"See [Synapse's documentation](https://github.com/element-" +"hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md" +"#available-statistics) or [Dendrite's documentation](https://github.com" +"/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-" +"enabling-phone-home-statistics) for the full list of statistics that are " +"reported." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po new file mode 100644 index 000000000..6542f6b36 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -0,0 +1,212 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-traefik.md:1 +msgid "Configuring the Traefik reverse-proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:3 +msgid "" +"By default, this playbook installs and manages a " +"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered " +"by the [ansible-role-traefik](https://github.com/mother-of-all-self-" +"hosting/ansible-role-traefik) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:5 +msgid "" +"This Ansible role support various configuration options. Feel free to " +"consult its `default/main.yml` variables file." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:7 +msgid "Adjusting SSL certificate retrieval" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:9 +msgid "" +"See the dedicated [Adjusting SSL certificate retrieval](configuring-" +"playbook-ssl-certificates.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:11 +msgid "Increase logging verbosity" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:17 +msgid "Disable access logs" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:19 +msgid "This will disable access logging." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:25 +msgid "Enable Traefik Dashboard" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:27 +msgid "" +"This will enable a Traefik " +"[Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at " +"`https://matrix.example.com/dashboard/` (note the trailing `/`)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:37 +msgid "" +"**WARNING**: Enabling the dashboard on a hostname you use for something " +"else (like `matrix_server_fqn_matrix` in the configuration above) may " +"cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all" +" `/dashboard` and `/api` requests and forward them to itself. If any of " +"the services hosted on the same hostname requires any of these 2 URL " +"prefixes, you will experience problems. So far, we're not aware of any " +"playbook services which occupy these endpoints and are likely to cause " +"conflicts." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:39 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:41 +msgid "" +"Use the `traefik_configuration_extension_yaml` variable provided by the " +"Traefik Ansible role to override or inject additional settings, even when" +" no dedicated variable exists." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:51 +msgid "Reverse-proxying another service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:53 +msgid "" +"The preferred way to reverse-proxy additional services behind Traefik " +"would be to start the service as another container, configure the " +"container with the corresponding Traefik [container " +"labels](https://docs.docker.com/config/labels-custom-metadata/) (see " +"[Traefik & " +"Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and " +"connect the service to the `traefik` network. Some services are also " +"already available via the compatible [mash-playbook](https://github.com" +"/mother-of-all-self-hosting/mash-playbook), but take a look at the minor " +"[interoperability adjustments](https://github.com/mother-of-all-self-" +"hosting/mash-playbook/blob/main/docs/interoperability.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:55 +msgid "" +"However, if your service does not run on a container or runs on another " +"machine, the following configuration might be what you are looking for." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:57 +msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:59 +msgid "" +"If you want to host another webserver would be reachable via `my-fancy-" +"website.example.net` from the internet and via `https://:` from inside your network, you can " +"make the playbook's integrated Traefik instance reverse-proxy the traffic" +" to the correct host." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:61 +msgid "" +"Prerequisites: DNS and routing for the domain `my-fancy-" +"website.example.net` need to be set up correctly. In this case, you'd be " +"pointing the domain name to your Matrix server - `my-fancy-" +"website.example.net` would be a CNAME going to `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:63 +msgid "" +"First, we have to adjust the static configuration of Traefik, so that we " +"can add additional configuration files:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:77 +msgid "" +"If you are using a self-signed certificate on your webserver, you can " +"tell Traefik to trust your own backend servers by adding more " +"configuration to the static configuration file. If you do so, bear in " +"mind the security implications of disabling the certificate validity " +"checks towards your back end." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:91 +msgid "" +"Next, you have to add a new dynamic configuration file for Traefik that " +"contains the actual information of the server using the " +"`aux_file_definitions` variable. In this example, we will terminate SSL " +"at the Traefik instance and connect to the other server via HTTPS. " +"Traefik will now take care of managing the certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:110 +#: ../../../docs/configuring-playbook-traefik.md:133 +msgid "" +"Changing the `url` to one with an `http://` prefix would allow to connect" +" to the server via HTTP." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:112 +msgid "Reverse-proxying another service behind Traefik without terminating SSL" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:114 +msgid "" +"If you do not want to terminate SSL at the Traefik instance (for example," +" because you're already terminating SSL at other webserver), you need to " +"adjust the static configuration in the same way as in the previous " +"chapter in order to be able to add our own dynamic configuration files. " +"Afterwards, you can add the following configuration to your `vars.yml` " +"configuration file:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:135 +msgid "" +"With these changes, all TCP traffic will be reverse-proxied to the target" +" system." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:137 +msgid "" +"**WARNING**: This configuration might lead to problems or need additional" +" steps when a [certbot](https://certbot.eff.org/) behind Traefik also " +"tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, " +"as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-" +"challenge/`)```." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:139 +msgid "Traefik behind a `proxy_protocol` reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:141 +msgid "" +"If you run a reverse-proxy which speaks `proxy_protocol`, add the " +"following to your configuration file:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po new file mode 100644 index 000000000..7ec5ad0df --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-turn.md:1 +msgid "Adjusting TURN server configuration (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:3 +msgid "" +"The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN " +"server by default, so that clients can make audio/video calls even from " +"[NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed " +"networks." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:5 +msgid "" +"By default, the Synapse chat server is configured, so that it points to " +"the Coturn TURN server installed by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:7 +msgid "Disabling Coturn" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:9 +msgid "" +"If, for some reason, you'd like to prevent the playbook from installing " +"Coturn, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:15 +msgid "" +"In that case, Synapse would not point to any Coturn servers and " +"audio/video call functionality may fail." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:17 +msgid "Manually defining your public IP" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:19 +msgid "" +"In the `hosts` file we explicitly ask for your server's external IP " +"address when defining `ansible_host`, because the same value is used for " +"configuring Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:21 +msgid "" +"If you'd rather use a local IP for `ansible_host`, make sure to set up " +"`matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with " +"the pubic IP used by the server." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:27 +msgid "" +"If you'd like to rely on external IP address auto-detection (not " +"recommended unless you need it), set " +"`matrix_coturn_turn_external_ip_address` to an empty value. The playbook " +"will automatically contact an " +"[EchoIP](https://github.com/mpolden/echoip)-compatible service " +"(`https://ifconfig.co/json` by default) to determine your server's IP " +"address. This API endpoint is configurable via the " +"`matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url`" +" variable." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:29 +msgid "" +"If your server has multiple external IP addresses, the Coturn role offers" +" a different variable for specifying them:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:36 +msgid "Changing the authentication mechanism" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:38 +msgid "" +"The playbook uses the [`auth-secret` authentication " +"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199)" +" by default, but you may switch to the [`lt-cred-mech` " +"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178)" +" which [some report](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/3191) to be working better." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:40 +msgid "To do so, add this override to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:46 +msgid "" +"Regardless of the selected authentication method, the playbook generates " +"secrets automatically and passes them to the homeserver and Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:48 +msgid "" +"If you're using [Jitsi](./configuring-playbook-jitsi.md), note that " +"switching to `lt-cred-mech` will remove the integration between Jitsi and" +" your own Coturn server, because Jitsi only seems to support the `auth-" +"secret` authentication method." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:50 +msgid "Using your own external Coturn server" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:52 +msgid "" +"If you'd like to use another TURN server (be it Coturn or some other " +"one), you can configure the playbook like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:66 +msgid "" +"If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you" +" might want to enable the TURN server there too. If you do not do it, " +"Jitsi will fall back to an upstream service." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:72 +msgid "You can put multiple host/port combinations if you like." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:74 +msgid "Further variables and configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:75 +msgid "" +"To see all the available configuration options, check roles/custom" +"/matrix-coturn/defaults/main.yml" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po new file mode 100644 index 000000000..ddb720e35 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -0,0 +1,311 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-user-verification-service.md:1 +msgid "Setting up Matrix User Verification Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:3 +msgid "" +"**[Matrix User Verification Service](https://github.com/matrix-org" +"/matrix-user-verification-service) (hereafter: UVS) can only be installed" +" after Matrix services are installed and running.** If you're just " +"installing Matrix services for the first time, please continue with the " +"[Configuration](configuring-playbook.md) / [Installation](installing.md) " +"flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:5 +msgid "" +"Currently, the main purpose of this role is to allow Jitsi to " +"authenticate Matrix users and check if they are authorized to join a " +"conference. Please refer to the documentation of the [Matrix User " +"Verification Service](https://github.com/matrix-org/matrix-user-" +"verification-service) to understand how it works." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:7 +msgid "" +"**Note**: enabling Matrix User Verification Service, means that the " +"`openid` API endpoints will be exposed on the Matrix Federation port " +"(usually `8448`), even if [federation](configuring-playbook-" +"federation.md) is disabled." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:9 +msgid "" +"If the Jitsi server is also configured by this playbook, all plugging of " +"variables and secrets is handled in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:11 +msgid "" +"__Some general concepts of UVS may be helpful to understand the rest, so " +"here they are:__" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:13 +msgid "UVS can be used to verify two claims:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:15 +msgid "(A) Whether a given OpenID token is valid for a given server and" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:16 +msgid "" +"(B) whether a user is member of a given room and the corresponding " +"PowerLevel" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:18 +msgid "" +"Verifying an OpenID token ID done by finding the corresponding Homeserver" +" via '.well-known/matrix/server' for the given domain. The configured " +"`matrix_user_verification_service_uvs_homeserver_url` does **not** factor" +" into this. By default, this playbook only checks against " +"`matrix_server_fqn_matrix`. Therefore, the request will be made against " +"the public openid API for `matrix_server_fqn_matrix`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:20 +msgid "" +"Verifying RoomMembership and PowerLevel is done against " +"`matrix_user_verification_service_uvs_homeserver_url` which is by default" +" done via the docker network. UVS will verify the validity of the token " +"beforehand though." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:24 +msgid "" +"In order to use UVS, an admin token for the configured homeserver must be" +" supplied. For now this means configuring Synapse and creating the token " +"before installing UVS." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:26 +msgid "Enable" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:28 +msgid "" +"To enable Matrix User Verification Service, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:34 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:36 +msgid "" +"The only required configuration variable is " +"`matrix_user_verification_service_uvs_access_token` (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:38 +msgid "" +"For a list of all configuration options see the role defaults [`roles" +"/matrix-user-verification-service/defaults/main.yml`](../roles/custom" +"/matrix-user-verification-service/defaults/main.yml). But be aware of all" +" the plugging happening in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:40 +msgid "" +"In the default configuration, the UVS Server is only reachable via the " +"docker network, which is fine if e.g. Jitsi is also running in a " +"container on the host. However, it is possible to expose UVS via setting " +"`matrix_user_verification_service_container_http_host_bind_port`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:42 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:44 +msgid "" +"The Synapse Access Token is used to verify RoomMembership and PowerLevel " +"against `matrix_user_verification_service_uvs_homeserver_url`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:46 +msgid "" +"We recommend that you create a dedicated Matrix user for uvs (`uvs` is a " +"good username). Follow our [Registering users](registering-users.md) " +"guide to register a user with administration privileges." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:48 +msgid "" +"You are required to specify an access token (belonging to this new user) " +"for UVS to work. To get an access token for the UVS user, you can follow " +"the documentation on [how to do obtain an access token](obtaining-access-" +"tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:50 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:56 +msgid "(Optional) Custom Auth Token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:58 +msgid "" +"It is possible to set an API Auth Token to restrict access to the UVS. If" +" this is enabled, anyone making a request to UVS must provide it via the " +"header \"Authorization: Bearer TOKEN\"" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:60 +msgid "" +"By default, the token will be derived from " +"`matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:62 +msgid "" +"To set your own Token, add the following configuration to your `vars.yml`" +" file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:68 +msgid "" +"In case Jitsi is also managed by this playbook and 'matrix' " +"authentication in Jitsi is enabled, this collection will automatically " +"configure Jitsi to use the configured auth token." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:70 +msgid "(Optional) Disable Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:72 +msgid "" +"Authorization is enabled by default. To disable it, add the following " +"configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:78 +msgid "(Optional) Federation" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:80 +msgid "" +"In theory (however currently untested), UVS can handle federation. To " +"enable it, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:86 +msgid "" +"This will instruct UVS to verify the OpenID token against any domain " +"given in a request. Homeserver discovery is done via '.well-" +"known/matrix/server' of the given domain." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:88 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:90 +msgid "" +"After these variables have been set, run the playbook with [playbook tags" +"](playbook-tags.md) as below to restart UVS:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:96 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just run-tags setup-matrix-user-verification-service,start` " +"or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:98 +msgid "" +"`just run-tags setup-matrix-user-verification-service,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-user-verification-service.md:100 +msgid "Logging" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:102 +msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:103 +msgid "warning" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:104 +msgid "info" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:105 +msgid "debug" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:107 +msgid "TLS Certificate Checking" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:109 +msgid "" +"If the Matrix Homeserver does not provide a valid TLS certificate, UVS " +"will fail with the following error message:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:111 +msgid "message: 'No response received: [object Object]'," +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:113 +msgid "This also applies to self-signed and let's encrypt staging certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:115 +msgid "" +"To disable certificate validation altogether (INSECURE! Not suitable for " +"production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:117 +msgid "" +"Alternatively, it is possible to inject your own CA certificates into the" +" container by mounting a PEM file with additional trusted CAs into the " +"container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to " +"it." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po new file mode 100644 index 000000000..678f78e99 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po @@ -0,0 +1,776 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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.md:1 +msgid "Configuring the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook.md:3 +msgid "" +"[Prerequisites](prerequisites.md) > [Configuring your DNS settings" +"](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) >" +" Configuring the playbook > [Installing](installing.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:5 +msgid "" +"If you've configured your DNS records and retrieved the playbook's source" +" code to your computer, you can start configuring the playbook. To do so," +" follow these steps inside the playbook directory:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:7 +msgid "" +"create a directory to hold your configuration (`mkdir -p " +"inventory/host_vars/matrix.example.com` where `example.com` is your " +"\"base domain\")" +msgstr "" + +#: ../../../docs/configuring-playbook.md:9 +msgid "" +"copy the sample configuration file (`cp examples/vars.yml " +"inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:11 +msgid "" +"edit the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You " +"may also take a look at the various " +"`roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's " +"something you'd like to copy over and override in your `vars.yml` " +"configuration file." +msgstr "" + +#: ../../../docs/configuring-playbook.md:13 +msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:15 +msgid "edit the inventory hosts file (`inventory/hosts`) to your liking" +msgstr "" + +#: ../../../docs/configuring-playbook.md:17 +msgid "" +"(optional, advanced) you may wish to keep your `inventory` directory " +"under version control with [git](https://git-scm.com/) or any other " +"version-control system." +msgstr "" + +#: ../../../docs/configuring-playbook.md:19 +msgid "" +"(optional, advanced) to run Ansible against multiple servers with " +"different `sudo` credentials, you can copy the sample inventory hosts " +"yaml file for each of your hosts: (`cp examples/host.yml " +"inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin" +"/ansible-all-hosts.sh) script [in the installation step](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:21 +msgid "For a basic Matrix installation, that's all you need." +msgstr "" + +#: ../../../docs/configuring-playbook.md:23 +msgid "" +"For a more custom setup, see the [Other configuration options](#other-" +"configuration-options) below." +msgstr "" + +#: ../../../docs/configuring-playbook.md:25 +msgid "" +"[▶️](installing.md) When you're done with all the configuration you'd " +"like to do, continue with [Installing](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:27 +msgid "Other configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook.md:29 +msgid "Core service adjustments" +msgstr "" + +#: ../../../docs/configuring-playbook.md:31 +msgid "Homeserver configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:32 +msgid "" +"[Configuring Synapse](configuring-playbook-synapse.md), if you're going " +"with the default/recommended homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:34 +msgid "" +"[Configuring Conduit](configuring-playbook-conduit.md), if you've " +"switched to the [Conduit](https://conduit.rs) homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:36 +msgid "" +"[Configuring Dendrite](configuring-playbook-dendrite.md), if you've " +"switched to the [Dendrite](https://matrix-org.github.io/dendrite) " +"homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:38 +msgid "Server components:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:39 +msgid "" +"[Using an external PostgreSQL server](configuring-playbook-external-" +"postgres.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:41 +msgid "" +"[Adjusting TURN server configuration](configuring-playbook-turn.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:43 +msgid "" +"[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:45 +msgid "" +"[Using your own webserver, instead of this playbook's Traefik reverse-" +"proxy](configuring-playbook-own-webserver.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:47 +msgid "" +"[Adjusting SSL certificate retrieval](configuring-playbook-ssl-" +"certificates.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:49 +msgid "[Adjusting email-sending settings](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:51 +msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:53 +msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:55 +msgid "Server connectivity:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:56 +msgid "" +"[Enabling Telemetry for your Matrix server](configuring-playbook-" +"telemetry.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:58 +msgid "[Controlling Matrix federation](configuring-playbook-federation.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:60 +msgid "Clients" +msgstr "" + +#: ../../../docs/configuring-playbook.md:62 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/configuring-playbook.md:64 +msgid "" +"[Configuring Element Web](configuring-playbook-client-element-web.md), if" +" you're going with the default/recommended client" +msgstr "" + +#: ../../../docs/configuring-playbook.md:66 +msgid "" +"[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've" +" enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a " +"lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/configuring-playbook.md:68 +msgid "" +"[Setting up Cinny](configuring-playbook-client-cinny.md), if you've " +"enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing " +"primarily on simple, elegant and secure interface" +msgstr "" + +#: ../../../docs/configuring-playbook.md:70 +msgid "" +"[Setting up SchildiChat Web](configuring-playbook-client-schildichat-" +"web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a " +"web client based on [Element Web](https://element.io/) with some extras " +"and tweaks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:72 +msgid "Authentication and user-related" +msgstr "" + +#: ../../../docs/configuring-playbook.md:74 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook.md:76 +msgid "" +"[Setting up Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md) (Next-generation auth for Matrix, based on " +"OAuth 2.0/OIDC)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:78 +msgid "" +"[Setting up Appservice Double Puppet](configuring-playbook-appservice-" +"double-puppet.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:80 +msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:82 +msgid "" +"[Setting up matrix-registration](configuring-playbook-matrix-" +"registration.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:84 +msgid "" +"[Setting up the REST authentication password provider module" +"](configuring-playbook-rest-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:86 +msgid "" +"[Setting up the Shared Secret Auth password provider module](configuring-" +"playbook-shared-secret-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:88 +msgid "" +"[Setting up the LDAP authentication password provider module" +"](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:90 +msgid "" +"[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-" +"ldap-registration-proxy.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:92 +msgid "" +"[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-" +"antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:94 +msgid "" +"[Setting up Matrix User Verification Service](configuring-playbook-user-" +"verification-service.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../docs/configuring-playbook.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/configuring-playbook.md:100 +msgid "" +"[Storing Matrix media files on Amazon S3 with Goofys](configuring-" +"playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:102 +msgid "" +"[Storing Synapse media files on Amazon S3 or another compatible Object " +"Storage](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:104 +msgid "" +"[Storing Matrix media files using matrix-media-repo](configuring-" +"playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:106 +msgid "Bridging other networks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:108 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../docs/configuring-playbook.md:110 +msgid "" +"[Setting up Mautrix Discord bridging](configuring-playbook-bridge-" +"mautrix-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:112 +msgid "" +"[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-" +"mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:114 +msgid "" +"[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-" +"slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:116 +msgid "" +"[Setting up Mautrix Google Messages bridging](configuring-playbook-" +"bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:118 +msgid "" +"[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-" +"mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:120 +msgid "" +"[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-" +"bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:122 +msgid "" +"[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-" +"bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:124 +msgid "" +"[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-" +"mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:126 +msgid "" +"[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-" +"mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:128 +msgid "" +"[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-" +"signal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:130 +msgid "" +"[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage" +"](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:132 +msgid "" +"[Setting up Appservice IRC bridging](configuring-playbook-bridge-" +"appservice-irc.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:134 +msgid "" +"[Setting up Appservice Discord bridging](configuring-playbook-bridge-" +"appservice-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:136 +msgid "" +"[Setting up Appservice Slack bridging](configuring-playbook-bridge-" +"appservice-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:138 +msgid "" +"[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-" +"appservice-kakaotalk.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:140 +msgid "" +"[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-" +"linkedin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:142 +msgid "" +"[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a" +" bridge between Matrix and multiple project management services, such as " +"[GitHub](https://github.com), [GitLab](https://about.gitlab.com) and " +"[JIRA](https://www.atlassian.com/software/jira)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:144 +msgid "" +"[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-" +"puppet-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:146 +msgid "" +"[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-" +"puppet-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:148 +msgid "" +"[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-" +"puppet-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:150 +msgid "" +"[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-" +"puppet-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:152 +msgid "" +"[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-" +"puppet-groupme.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:154 +msgid "" +"[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-" +"puppet-steam.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:156 +msgid "" +"[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-" +"skype-bridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:158 +msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:160 +msgid "" +"[Setting up Postmoogle email bridging](configuring-playbook-bridge-" +"postmoogle.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:162 +msgid "" +"[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-" +"bridge-sms.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:164 +msgid "" +"[Setting up Heisenbridge bouncer-style IRC bridging](configuring-" +"playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:166 +msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:168 +msgid "Bots" +msgstr "" + +#: ../../../docs/configuring-playbook.md:170 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:172 +msgid "" +"[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through " +"which you can talk to various " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) " +"services ([OpenAI](https://openai.com/)'s " +"[ChatGPT](https://openai.com/blog/chatgpt/) and " +"[others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:174 +msgid "" +"[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-" +"reminder-bot.md) - a bot to remind you about stuff" +msgstr "" + +#: ../../../docs/configuring-playbook.md:176 +msgid "" +"[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-" +"registration-bot.md) - a bot to create and manage registration tokens to " +"invite users" +msgstr "" + +#: ../../../docs/configuring-playbook.md:178 +msgid "" +"[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based " +"Matrix bot system" +msgstr "" + +#: ../../../docs/configuring-playbook.md:180 +msgid "" +"[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk " +"bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:182 +msgid "" +"[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation " +"tool/bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:184 +msgid "" +"[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a " +"moderation tool/bot, forked from Mjolnir and maintained by its former " +"leader developer" +msgstr "" + +#: ../../../docs/configuring-playbook.md:186 +msgid "" +"[Setting up Draupnir for all/D4A](configuring-playbook-appservice-" +"draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-" +"draupnir.md) mentioned above, but running in appservice mode and " +"supporting multiple instances" +msgstr "" + +#: ../../../docs/configuring-playbook.md:188 +msgid "" +"[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you" +" can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../docs/configuring-playbook.md:190 +msgid "Administration" +msgstr "" + +#: ../../../docs/configuring-playbook.md:192 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:194 +msgid "" +"[Setting up Prometheus Alertmanager integration via matrix-alertmanager-" +"receiver](configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:196 +msgid "" +"[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server" +"](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:198 +msgid "" +"[Enabling metrics and graphs for NginX logs](configuring-playbook-" +"prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:200 +msgid "" +"[Setting up the rageshake bug report server](configuring-playbook-" +"rageshake.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:202 +msgid "" +"[Enabling synapse-usage-exporter for Synapse usage statistics" +"](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:204 +msgid "Backups:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:205 +msgid "" +"[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full " +"Matrix server backup solution, including the Postgres database" +msgstr "" + +#: ../../../docs/configuring-playbook.md:207 +msgid "" +"[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a" +" Postgres-database backup solution (note: does not include other files)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:209 +msgid "Other specialized services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:211 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/configuring-playbook.md:213 +msgid "" +"[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-" +"auto-accept-invite.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:215 +msgid "" +"[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-" +"compressor.md) for compressing the database on Synapse homeservers" +msgstr "" + +#: ../../../docs/configuring-playbook.md:217 +msgid "" +"[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) " +"(advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:219 +msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:221 +msgid "" +"[Setting up the Jitsi video-conferencing platform](configuring-playbook-" +"jitsi.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:223 +msgid "" +"[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a" +" federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook.md:225 +msgid "" +"[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-" +"pantalaimon.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:227 +msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:229 +msgid "" +"[Setting up the ntfy push notifications server](configuring-playbook-" +"ntfy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:231 +msgid "Deprecated / unmaintained / removed services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:233 +msgid "" +"**Note**: since a deprecated or unmaintained service will not be updated," +" its bug or vulnerability will be unlikely to get patched. It is " +"recommended to migrate from the service to an alternative if any, and " +"make sure to do your own research before you decide to keep it running " +"nonetheless." +msgstr "" + +#: ../../../docs/configuring-playbook.md:235 +msgid "" +"[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-" +"proxy.md) for clients which require Sliding Sync support (like old " +"Element X versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:237 +msgid "" +"[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-" +"appservice-webhooks.md) (deprecated; the bridge's author suggests taking " +"a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" +"hookshot) as a replacement, which can also be installed using [this " +"playbook](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:239 +msgid "" +"[Setting up the Dimension integration manager](configuring-playbook-" +"dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-" +"docker-ansible-deploy/issues/2806#issuecomment-1673559299); after " +"[installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:241 +msgid "" +"[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; " +"the bridge's author suggests taking a look at [matrix-" +"hookshot](https://github.com/matrix-org/matrix-hookshot) as a " +"replacement, which can also be installed using [this playbook" +"](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:243 +msgid "" +"[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) " +"(unmaintained; the bridge's author suggests taking a look at " +"[baibot](https://github.com/etkecc/baibot) as a replacement, which can " +"also be installed using [this playbook](configuring-playbook-bot-" +"baibot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:245 +msgid "" +"[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-" +"mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram " +"bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-" +"meta-messenger.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:247 +msgid "" +"[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-" +"mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with " +"[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:249 +msgid "" +"[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-" +"mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram " +"bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-" +"meta-instagram.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:251 +msgid "" +"[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-" +"puppet-skype.md) (removed; this component has been broken for a long " +"time, so it has been removed from the playbook. Consider [setting up Go " +"Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po new file mode 100644 index 000000000..c6f731a5d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po @@ -0,0 +1,396 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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-well-known.md:1 +msgid "Configuring Service Discovery via .well-known" +msgstr "" + +#: ../../../docs/configuring-well-known.md:3 +msgid "" +"This documentation page explains how to configure Service discovery via " +"`/.well-known/` files. Service discovery is a way for the Matrix network " +"to discover where a Matrix server is." +msgstr "" + +#: ../../../docs/configuring-well-known.md:5 +msgid "Types of well-known service discovery mechanism" +msgstr "" + +#: ../../../docs/configuring-well-known.md:7 +msgid "" +"There are 3 types of well-known service discovery mechanism that Matrix " +"makes use of:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:9 +msgid "" +"(important) **Federation Server discovery** (`/.well-" +"known/matrix/server`) -- assists other servers in the Matrix network with" +" finding your server. With the default playbook configuration specified " +"on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " +"this is necessary for federation to work. Without a proper configuration," +" your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/configuring-well-known.md:11 +msgid "" +"(less important) **Client Server discovery** (`/.well-" +"known/matrix/client`) -- assists programs that you use to connect to your" +" server (e.g. Element Web), so that they can make it more convenient for " +"you by automatically configuring the \"Homeserver URL\" and \"Identity " +"Server URL\" addresses." +msgstr "" + +#: ../../../docs/configuring-well-known.md:13 +msgid "" +"(optional) **Support service discovery** (`/.well-known/matrix/support`) " +"-- returns server admin contact and support page of the domain." +msgstr "" + +#: ../../../docs/configuring-well-known.md:15 +msgid "Federation Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:17 +msgid "" +"All services created by this playbook are meant to be installed on their " +"own server (such as `matrix.example.com`), instead of the base domain " +"(`example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:19 +msgid "" +"As [per the Server-Server " +"specification](https://matrix.org/docs/spec/server_server/r0.1.0.html" +"#server-discovery), in order to use a short Matrix user ID like " +"`@alice:example.com` instead of `@alice:matrix.example.com` while hosting" +" services on a subdomain such as `matrix.example.com`, the Matrix network" +" needs to be instructed of [server delegation](howto-server-" +"delegation.md) / redirection." +msgstr "" + +#: ../../../docs/configuring-well-known.md:21 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:23 +msgid "" +"If you set up the DNS SRV record for server delegation instead, take a " +"look at this documentation for more information: [Server Delegation via a" +" DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-" +"via-a-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/configuring-well-known.md:25 +msgid "Client Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:27 +msgid "" +"Client Server Service discovery lets various client programs which " +"support it, to receive a full user ID (e.g. `@alice:example.com`) and " +"determine where the Matrix server is automatically (e.g. " +"`https://matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:29 +msgid "" +"This lets you (and your users) easily connect to your Matrix server " +"without having to customize connection URLs. When using client programs " +"that support it, you won't need to point them to " +"`https://matrix.example.com` in Custom Server options manually anymore. " +"The connection URL would be discovered automatically from your full " +"username." +msgstr "" + +#: ../../../docs/configuring-well-known.md:31 +msgid "" +"Without /.well-known/matrix/client, the client will make the wrong " +"\"homeserver URL\" assumption (it will default to using " +"https://example.com, and users will need to notice and adjust it manually" +" (changing it to https://matrix.example.com)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:33 +msgid "" +"As [per the Client-Server " +"specification](https://matrix.org/docs/spec/client_server/r0.4.0.html" +"#server-discovery) Matrix does Client Server service discovery using a " +"`/.well-known/matrix/client` file hosted on the base domain (e.g. " +"`example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:35 +msgid "" +"However, this playbook installs your Matrix server on another domain " +"(e.g. `matrix.example.com`) and not on the base domain (e.g. " +"`example.com`), so it takes a little extra manual effort to set up the " +"file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:37 +msgid "(Optional) Support Service Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:39 +msgid "" +"[MSC 1929](https://github.com/matrix-org/matrix-spec-" +"proposals/pull/1929), which was added to [Matrix Specification version " +"v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-" +"knownmatrixsupport), specifies a way to add contact details of admins, as" +" well as a link to a support page for users who are having issues with " +"the service. Automated services may also index this information and use " +"it for abuse reports, etc." +msgstr "" + +#: ../../../docs/configuring-well-known.md:41 +msgid "" +"To enable it, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:62 +msgid "Installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:64 +msgid "" +"To implement the service discovery mechanisms, your base domain's server " +"(e.g. `example.com`) needs to run an HTTPS-capable webserver." +msgstr "" + +#: ../../../docs/configuring-well-known.md:66 +msgid "Serving the base domain from the Matrix server via the playbook" +msgstr "" + +#: ../../../docs/configuring-well-known.md:68 +msgid "" +"If you don't have a server for your base domain at all, you can use the " +"Matrix server for this. If you don't need the base domain (e.g. " +"`example.com`) for anything else (hosting a website, etc.), you can point" +" it to the Matrix server's IP address and tell the playbook to configure " +"it." +msgstr "" + +#: ../../../docs/configuring-well-known.md:70 +msgid "" +"**This is the easiest way to set up well-known serving** -- letting the " +"playbook handle the whole base domain for you (including SSL " +"certificates, etc.) and take care to serve the appropriate well-known " +"files automatically." +msgstr "" + +#: ../../../docs/configuring-well-known.md:72 +msgid "" +"If you decide to go this route, you don't need to read ahead in this " +"document. Instead, go to [Serving the base domain](configuring-playbook-" +"base-domain-serving.md) to learn how the playbook can help you set it up." +msgstr "" + +#: ../../../docs/configuring-well-known.md:74 +msgid "" +"However, if you need to use the base domain for other things, this method" +" is less suitable than the one explained below." +msgstr "" + +#: ../../../docs/configuring-well-known.md:76 +msgid "Manually installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:78 +msgid "" +"If you're managing the base domain by yourself somehow, you'll need to " +"set up serving of some `/.well-known/matrix/*` files from it via HTTPS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:80 +msgid "" +"To make things easy for you to set up, this playbook generates and hosts " +"a few well-known files on the Matrix domain's server. The files are " +"generated at the `/matrix/static-files/public/.well-known/matrix/` path " +"on the server and hosted at URLs like `https://matrix.example.com/.well-" +"known/matrix/server` and `https://matrix.example.com/.well-" +"known/matrix/client`, even though this is the wrong place to host them." +msgstr "" + +#: ../../../docs/configuring-well-known.md:82 +msgid "" +"You have two options when it comes to installing the files on the base " +"domain's server:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:84 +msgid "(Option 1): **Copying the files manually** to your base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:86 +msgid "" +"**Hint**: Option 2 is generally a better way to do this. Make sure to go " +"with it, if possible." +msgstr "" + +#: ../../../docs/configuring-well-known.md:88 +msgid "All you need to do is:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:90 +msgid "" +"copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from " +"the Matrix server (e.g. `matrix.example.com`) to your base domain's " +"server (`example.com`). You can find these files in the `/matrix/static-" +"files/.well-known/matrix` directory on the Matrix server. They are also " +"accessible on URLs like this: `https://matrix.example.com/.well-" +"known/matrix/server` (same for `client`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:92 +msgid "" +"set up the server at your base domain (e.g. `example.com`) so that it " +"adds an extra HTTP header when serving the `/.well-known/matrix/client` " +"file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the" +" `Access-Control-Allow-Origin` header should be set with a value of `*`. " +"If you don't do this step, web-based Matrix clients (like Element Web) " +"may fail to work. Setting up headers for the `/.well-known/matrix/server`" +" file is not necessary, as this file is only consumed by non-browsers, " +"which don't care about CORS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:94 +msgid "" +"This is relatively easy to do and possibly your only choice if you can " +"only host static files from the base domain's server. It is, however, **a" +" little fragile**, as future updates performed by this playbook may " +"regenerate the well-known files and you may need to notice that and copy " +"them over again." +msgstr "" + +#: ../../../docs/configuring-well-known.md:96 +msgid "" +"(Option 2): **Setting up reverse-proxying** of the well-known files from " +"the base domain's server to the Matrix server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:98 +msgid "This option is less fragile and generally better." +msgstr "" + +#: ../../../docs/configuring-well-known.md:100 +msgid "" +"On the base domain's server (e.g. `example.com`), you can set up reverse-" +"proxying, so that any access for the `/.well-known/matrix` location " +"prefix is forwarded to the Matrix domain's server (e.g. " +"`matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:102 +msgid "" +"With this method, you **don't need** to add special HTTP headers for " +"[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons " +"(like `Access-Control-Allow-Origin`), because your Matrix server (where " +"requests ultimately go) will be configured by this playbook correctly." +msgstr "" + +#: ../../../docs/configuring-well-known.md:104 +msgid "**For nginx**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:121 +msgid "**For Apache2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:135 +msgid "**For Caddy 2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:145 +msgid "**For HAProxy**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:164 +msgid "" +"**For Netlify**, configure a " +"[redirect](https://docs.netlify.com/routing/redirects/) using a " +"`_redirects` file in the [publish directory](https://docs.netlify.com" +"/configure-builds/overview/#definitions) with contents like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:170 +msgid "**For AWS CloudFront**" +msgstr "" + +#: ../../../docs/configuring-well-known.md:172 +msgid "Add a custom origin with matrix.example.com to your distribution" +msgstr "" + +#: ../../../docs/configuring-well-known.md:173 +msgid "" +"Add two behaviors, one for `.well-known/matrix/client` and one for " +"`.well-known/matrix/server` and point them to your new origin." +msgstr "" + +#: ../../../docs/configuring-well-known.md:175 +msgid "Make sure to:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:177 +msgid "" +"**replace `example.com`** in the server configuration with your actual " +"domain name" +msgstr "" + +#: ../../../docs/configuring-well-known.md:178 +msgid "" +"and: to **do this for the HTTPS-enabled server block**, as that's where " +"Matrix expects the file to be" +msgstr "" + +#: ../../../docs/configuring-well-known.md:180 +msgid "Confirming it works" +msgstr "" + +#: ../../../docs/configuring-well-known.md:182 +msgid "" +"No matter which method you've used to set up the well-known files, if " +"you've done it correctly you should be able to see a JSON file at these " +"URLs:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:184 +msgid "`https://example.com/.well-known/matrix/server`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:185 +msgid "`https://example.com/.well-known/matrix/client`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:186 +msgid "`https://example.com/.well-known/matrix/support`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:188 +msgid "" +"You can also check if everything is configured correctly, by [checking if" +" services work](maintenance-checking-services.md)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/container-images.po b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po new file mode 100644 index 000000000..b62028a53 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po @@ -0,0 +1,1313 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/container-images.md:1 +msgid "Container images used by the playbook" +msgstr "" + +#: ../../../docs/container-images.md:3 +msgid "" +"This page summarizes the container ([Docker](https://www.docker.com/)) " +"images used by the playbook when setting up your server." +msgstr "" + +#: ../../../docs/container-images.md:5 +msgid "" +"We try to stick to official images (provided by their respective " +"projects) as much as possible." +msgstr "" + +#: ../../../docs/container-images.md:7 +msgid "Homeserver" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Service" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Container image" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Default?" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Description" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Synapse](configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "✅" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Conduit](configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit" +"/matrix-conduit)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "❌" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" +"source server implementation of the Matrix Specification with a focus on " +"easy setup and low system requirements" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Dendrite](configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg" +"/dendrite-monolith/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Storing your data and managing your presence in the " +"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " +"Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../docs/container-images.md:15 +msgid "Clients" +msgstr "" + +#: ../../../docs/container-images.md:17 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Element Web](configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Default Matrix web client, configured to connect to your own Synapse " +"server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Cinny](configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../docs/container-images.md:26 +msgid "Server Components" +msgstr "" + +#: ../../../docs/container-images.md:28 +msgid "" +"Services that run on the server to make the various parts of your " +"installation work." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[PostgreSQL](configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[postgres](https://hub.docker.com/_/postgres/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Database for Synapse. [Using an external PostgreSQL server](configuring-" +"playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Coturn](configuring-playbook-turn.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Traefik](configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Traefik](https://hub.docker.com/_/traefik/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Web server, listening on ports 80, 443 and 8448 - standing in front of " +"all the other services. Using your own webserver [is possible" +"](configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"The [certbot](https://certbot.eff.org/) tool for obtaining SSL " +"certificates from [Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Exim](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Mail server, through which all Matrix services send outgoing email (can " +"be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ma1sd](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ddclient](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Update dynamic DNS entries for accounts on Dynamic DNS Network Service " +"Provider" +msgstr "" + +#: ../../../docs/container-images.md:40 +msgid "Authentication" +msgstr "" + +#: ../../../docs/container-images.md:42 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "(N/A)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-" +"auth.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-" +"registration-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A proxy that handles Matrix registration requests and forwards them to " +"LDAP." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-registration](configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-" +"matrix-registration/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Matrix User Verification Service](configuring-playbook-user-" +"verification-service.md) (UVS)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-user-verification-" +"service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-" +"service)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[synapse-simple-antispam](configuring-playbook-synapse-simple-" +"antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A spam checker module" +msgstr "" + +#: ../../../docs/container-images.md:54 +msgid "File Storage" +msgstr "" + +#: ../../../docs/container-images.md:56 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Goofys](configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " +"store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"matrix-media-repo is a highly customizable multi-domain media repository " +"for Matrix. Intended for medium to large deployments, this media repo de-" +"duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../docs/container-images.md:64 +msgid "Bridges" +msgstr "" + +#: ../../../docs/container-images.md:66 +msgid "" +"Bridges can be used to connect your Matrix installation with third-party " +"communication networks." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-" +"messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-" +"instagram.md))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge to [Messenger](https://messenger.com/) and " +"[Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-appservice-" +"irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-" +"kakaotalk.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Self-building" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge to " +"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-discord](configuring-playbook-bridge-appservice-" +"discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-" +"appservice-discord)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixdotorg/matrix-appservice-" +"slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-" +"hookshot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge for generic webhooks and multiple project management services, " +"such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[folivonet/matrix-sms-" +"bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-" +"bridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to SMS" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bouncer-style bridge to " +"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-" +"bridge)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-" +"puppet-instagram)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-" +"twitter)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-" +"puppet/discord/mx-puppet-discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-" +"groupme)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-" +"puppet-steam)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../docs/container-images.md:99 +msgid "Bots" +msgstr "" + +#: ../../../docs/container-images.md:101 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[baibot](configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A bot that exposes the power of " +"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " +"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " +"you" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-" +"bot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-registration-bot](configuring-playbook-bot-matrix-registration-" +"bot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-" +"registration-bot/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[maubot](configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Honoroit](configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A helpdesk bot" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Draupnir](configuring-playbook-bot-draupnir.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Buscarron](configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../docs/container-images.md:114 +msgid "Administration" +msgstr "" + +#: ../../../docs/container-images.md:116 +msgid "" +"Services that help you in administrating and monitoring your Matrix " +"installation." +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-alertmanager-receiver](configuring-playbook-alertmanager-" +"receiver.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio" +"/matrix-alertmanager-receiver)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Prometheus' " +"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " +"client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[element-hq/matrix-authentication-service](https://ghcr.io/element-hq" +"/matrix-authentication-service)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Prometheus](https://prometheus.io) time-series database server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" +"exporter/) host metrics exporter" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Graphing tool that works well with the above two images. Our playbook " +"also adds two dashboards for [Synapse](https://github.com/element-" +"hq/synapse/tree/master/contrib/grafana) and [Node " +"Exporter](https://github.com/rfrail3/grafana-dashboards)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io" +"/martin-helmich/prometheus-nginxlog-exporter/exporter)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Addon for Prometheus that gathers access logs from various nginx reverse-" +"proxies" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Borg](configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Backups" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[rageshake](configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bug report server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Export the usage statistics of a Synapse homeserver to be scraped by " +"Prometheus." +msgstr "" + +#: ../../../docs/container-images.md:131 +msgid "Misc" +msgstr "" + +#: ../../../docs/container-images.md:133 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Sliding Sync support for clients which require it (like old Element X " +"versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-" +"invite.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-" +"synapse-compress-state/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"A cli tool that automatically compresses `state_groups` database table in" +" background." +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-" +"corporal/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Jitsi](configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) web UI" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Focus component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "the [Jitsi](https://jitsi.org/) Video Bridge component" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[cactuscomments/cactus-" +"appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-" +"web-server)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Sygnal](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Reference Push Gateway for Matrix" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[ntfy](configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Self-hosted, UnifiedPush-compatible push notifications server" +msgstr "" + +#: ../../../docs/container-images.md:152 +msgid "Container images of deprecated / unmaintained services" +msgstr "" + +#: ../../../docs/container-images.md:154 +msgid "" +"The list of the deprecated or unmaintained services is available [here" +"](configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-" +"webhooks.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live" +"/matrix-appservice-webhooks)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-" +"ci.org/), [Slack](https://slack.com/) etc. pp.)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Dimension](configuring-playbook-dimension.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-" +"dimension)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "An open source integration manager for Matrix clients" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "A multi functional bot written in Go" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "" +"[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-" +"bot)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Accessing ChatGPT via your favourite Matrix client" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Facebook](https://facebook.com/)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md +msgid "Bridge to [Instagram](https://instagram.com/)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/faq.po b/i18n/locales/jp/LC_MESSAGES/docs/faq.po new file mode 100644 index 000000000..1d9324658 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/faq.po @@ -0,0 +1,1354 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/faq.md:1 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../../../docs/faq.md:3 +msgid "" +"This documentation page tries to answer various Frequently Asked " +"Questions about all things [Matrix](https://matrix.org/), with a focus on" +" this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How" +" does it work?](#what-is-ansible-how-does-it-work))." +msgstr "" + +#: ../../../docs/faq.md:5 +msgid "" +"This FAQ page does not intend to replace the [matrix.org " +"FAQ](https://matrix.org/faq/) (please see that one too)." +msgstr "" + +#: ../../../docs/faq.md:7 +msgid "We've only started this FAQ recently, so it's still somewhat empty." +msgstr "" + +#: ../../../docs/faq.md:9 +msgid "" +"Also, we encourage you to not dig yourself into a hole by reading way too" +" much. When you've heard enough, proceed to installation. To get started," +" see [below](#how-do-i-run-the-installation) about our installation " +"guides." +msgstr "" + +#: ../../../docs/faq.md:11 +msgid "Introductory" +msgstr "" + +#: ../../../docs/faq.md:13 +msgid "Where do I find more questions and answers about Matrix?" +msgstr "" + +#: ../../../docs/faq.md:15 +msgid "" +"This is a Frequently Asked Questions page focused on this " +"[Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does " +"it work?](#what-is-ansible-how-does-it-work)) for deploying a " +"[Matrix](https://matrix.org/) server." +msgstr "" + +#: ../../../docs/faq.md:17 +msgid "" +"For a lot more generic questions and answers, see the [matrix.org " +"FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:19 +msgid "" +"What is Matrix? What is Element? What is Synapse? Why are you confusing " +"me with so many terms?" +msgstr "" + +#: ../../../docs/faq.md:21 +msgid "" +"[Matrix](https://matrix.org/) is a new type of realtime communication " +"(chat) network, the closest analogy to which is probably \"email\"." +msgstr "" + +#: ../../../docs/faq.md:23 +msgid "" +"You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly " +"though. There's a *server* somewhere which stores your data " +"(`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you" +" access it by using these \"email\" protocols via some *client* program " +"(Outlook, Thunderbird, some website, etc)." +msgstr "" + +#: ../../../docs/faq.md:25 +msgid "" +"In the world of the Matrix chat protocol, there are various client " +"programs. The first and currently most full-featured one is called " +"[Element](https://element.io/) (used to be called Riot.im and Vector.im " +"in the past). There are [many other " +"clients](https://matrix.org/clients/). You can switch clients as much as " +"you want until you find the one that is right for you on a given platform" +" (you may use Element Desktop on your desktop, but Fluffychat on your " +"phone, etc)." +msgstr "" + +#: ../../../docs/faq.md:27 +msgid "" +"Matrix is also like email due to the fact that there are many servers " +"around the world which can all talk to each other (you can send email " +"from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` " +"addresses). It's the same with Matrix (`@bob:example.com` can talk to " +"`@alice:example.org`)." +msgstr "" + +#: ../../../docs/faq.md:29 +msgid "" +"If someone else is hosting your Matrix server (you being " +"`@alice:matrix.org` or some other public server like this), all you need " +"is a Matrix client program, like Element Web or Element X Android." +msgstr "" + +#: ../../../docs/faq.md:31 +msgid "" +"If you'd like to host your own server (you being `@alice:example.com`), " +"you'd need to set up a Matrix server program, like Synapse." +msgstr "" + +#: ../../../docs/faq.md:33 +msgid "In short:" +msgstr "" + +#: ../../../docs/faq.md:35 +msgid "" +"Matrix is the protocol - a set of rules about how the chat network " +"operates" +msgstr "" + +#: ../../../docs/faq.md:36 +msgid "" +"Element is a client program you can use to participate on the Matrix chat" +" network via some server (yours or someone else's). There are also [many " +"other client programs](https://matrix.org/clients/)." +msgstr "" + +#: ../../../docs/faq.md:37 +msgid "" +"Synapse is a server program you can use to host your very own Matrix " +"server." +msgstr "" + +#: ../../../docs/faq.md:39 +msgid "" +"This FAQ here mostly focuses on installing various Matrix services using " +"the Ansible automation tool. You can learn much more about Matrix in the " +"[matrix.org FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:41 +msgid "People I wish to talk to are not on Matrix. Can I talk to them?" +msgstr "" + +#: ../../../docs/faq.md:43 +msgid "" +"You most likely can. Besides Matrix-native chats, Matrix also supports " +"the concept of \"bridging\", which allows you to plug other networks into" +" it." +msgstr "" + +#: ../../../docs/faq.md:45 +msgid "" +"This Ansible playbook can help you install [tens of bridges for various " +"networks](configuring-playbook.md#bridging-other-networks)." +msgstr "" + +#: ../../../docs/faq.md:47 +msgid "" +"Besides setting up your own bridges (preferable), you can also use some " +"[public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." +msgstr "" + +#: ../../../docs/faq.md:49 +msgid "How do I get started with Matrix?" +msgstr "" + +#: ../../../docs/faq.md:51 +msgid "" +"One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared" +" to other chat networks) is its decentralized nature. There's not just " +"one entity (company, organization) controlling the servers. Rather " +"there's thousands of servers operated by different people - one server " +"being insecure, slow or disrespective toward its users does not affect " +"the rest of the network. To participate in that decentralization in its " +"fullest, consider hosting your own server or using some public server " +"other than the largest/default one (`matrix.org`)." +msgstr "" + +#: ../../../docs/faq.md:53 +msgid "" +"There are 3 ways to get into Matrix, depending on your technical ability " +"and needs:" +msgstr "" + +#: ../../../docs/faq.md:55 +msgid "" +"**using the existing default server** - the easiest way is to use an " +"existing server. The largest public Matrix server is `matrix.org` and " +"it's configured as a default server in clients such as [Element " +"Web](https://app.element.io) and many others. Just use Element Web on the" +" browser via that link (or [download client apps for your Desktop or " +"smartphone](https://element.io/app-for-productivity)), create an account " +"and start chatting." +msgstr "" + +#: ../../../docs/faq.md:57 +msgid "" +"**using some other server** - instead of using the largest public server " +"(`matrix.org`), you can use another public one. Here's a [list of public " +"Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to " +"[Element Web](https://app.element.io) or download [some other " +"client](https://matrix.org/clients/) of your choosing and adjust the " +"homeserver URL during login." +msgstr "" + +#: ../../../docs/faq.md:59 +msgid "" +"**using your own server** - running your own server puts you in ultimate " +"control of your data. It also lets you have your own user IDs (e.g. " +"`@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i" +"-set-up-my-own-matrix-server)." +msgstr "" + +#: ../../../docs/faq.md:61 +msgid "How do I set up my own Matrix server?" +msgstr "" + +#: ../../../docs/faq.md:63 +msgid "" +"Normally, you'd first choose the [Matrix](https://matrix.org/) server " +"software you'd like to run. At the time of this writing (January/2021), " +"there's only one fully-featured server program, so there's only one " +"reasonable choice. That's [Synapse](https://github.com/element-" +"hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:65 +msgid "" +"There are [many guides about installing " +"Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this " +"Ansible playbook is just one way of doing it." +msgstr "" + +#: ../../../docs/faq.md:67 +msgid "" +"Naturally, we're biased, so our usual recommendation is to go with this " +"[Ansible](https://www.ansible.com/) playbook, instead of installing " +"Synapse (and many many other things around it) manually." +msgstr "" + +#: ../../../docs/faq.md:69 +msgid "" +"To get started with the playbook, check out the [Quick start](quick-" +"start.md) or full installation guide (starting at the " +"[Prerequisites](prerequisites.md) page)." +msgstr "" + +#: ../../../docs/faq.md:71 +msgid "What is Ansible? How does it work?" +msgstr "" + +#: ../../../docs/faq.md:73 +msgid "" +"[Ansible](https://www.ansible.com/) is an automation program. This " +"\"playbook\" is a collection of tasks/scripts that will set up a " +"[Matrix](https://matrix.org/) server for you, so you don't have to " +"perform these tasks manually." +msgstr "" + +#: ../../../docs/faq.md:75 +msgid "" +"We have written these automated tasks for you and all you need to do is " +"execute them using the Ansible program." +msgstr "" + +#: ../../../docs/faq.md:77 +msgid "" +"You can install Ansible and this playbook code repository on your own " +"computer and tell it to install Matrix services at the server living at " +"`matrix.example.com`. We recommend installing Ansible on your own " +"computer." +msgstr "" + +#: ../../../docs/faq.md:79 +msgid "" +"Alternatively, you can download Ansible and the playbook itself directly " +"on the `matrix.example.com` server." +msgstr "" + +#: ../../../docs/faq.md:81 +msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)." +msgstr "" + +#: ../../../docs/faq.md:83 +msgid "What is `just`?" +msgstr "" + +#: ../../../docs/faq.md:85 +msgid "" +"[`just`](https://github.com/casey/just) is a modern command-runner " +"alternative to [make](https://www.gnu.org/software/make/). It can be used" +" to invoke commands with less typing." +msgstr "" + +#: ../../../docs/faq.md:87 +msgid "" +"The `just` utility executes shortcut commands (called \"recipes\"), which" +" invoke `ansible-playbook`, `ansible-galaxy` or " +"[`agru`](https://github.com/etkecc/agru) (depending on what is available " +"in your system). The targets of the recipes are defined in " +"[`justfile`](../justfile)." +msgstr "" + +#: ../../../docs/faq.md:89 +msgid "" +"For details about `just` commands, take a look at: [Running `just` " +"commands](just.md)." +msgstr "" + +#: ../../../docs/faq.md:91 +msgid "" +"The playbook also contains a `Makefile` for the `make` tool, but most of " +"the just recipes are not available as targets in the `Makefile`." +msgstr "" + +#: ../../../docs/faq.md:93 +msgid "Why use this playbook and not install Synapse and other things manually?" +msgstr "" + +#: ../../../docs/faq.md:95 +msgid "" +"There are various guides telling you how easy it is to install " +"[Synapse](https://github.com/element-hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:97 +msgid "" +"Reading the documentation of this Ansible playbook, you may also be " +"thinking:" +msgstr "" + +#: ../../../docs/faq.md:99 +msgid "" +"I don't know what [Ansible](https://www.ansible.com/) is. I don't know " +"what [Docker](https://www.docker.com/) is. This looks more complicated." +msgstr "" + +#: ../../../docs/faq.md:101 +msgid "" +".. so you may be leaning toward [installing Synapse " +"manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." +msgstr "" + +#: ../../../docs/faq.md:103 +msgid "The problem with a manual installation is:" +msgstr "" + +#: ../../../docs/faq.md:105 +msgid "" +"Synapse is written in Python. If not packaged for your distribution, " +"you'd need to install various Python modules, etc., and keep them " +"updated." +msgstr "" + +#: ../../../docs/faq.md:106 +msgid "" +"Synapse requires a [Postgres](https://www.postgresql.org/) database (it " +"can run on SQLite, but that's very much discouraged). So you'd need to " +"install Postgres as well." +msgstr "" + +#: ../../../docs/faq.md:107 +msgid "" +"you may also need a reverse-proxy server in front of it (nginx, Apache), " +"so you'd need to be familiar with that" +msgstr "" + +#: ../../../docs/faq.md:108 +msgid "" +"SSL is required, so you'd need to obtain Let's Encrypt (or other free or " +"non-free) certificates for one or more domain names. You'd need to be " +"familiar with [certbot](https://certbot.eff.org/) (when using Let's " +"Encrypt) or similar software." +msgstr "" + +#: ../../../docs/faq.md:109 +msgid "" +"for each additional component you'd like to add (client like " +"[Element](https://element.io), bridge to some other chat network, " +"integration manager (stickers, other services, Identity Manager, etc.), " +"you'll need to spend extra time installing and wiring it with the rest of" +" the system in a way that works." +msgstr "" + +#: ../../../docs/faq.md:110 +msgid "" +"you'll likely get slower updates for all of these components, depending " +"on your distro packaging or your own time and ability" +msgstr "" + +#: ../../../docs/faq.md:112 +msgid "" +"The playbook, on the other hand, installs a bunch of components for you " +"by default, obtains SSL certificates for you, etc. If you'd like, you can" +" enable various bridges and other services with very little effort. All " +"the components are wired to work together." +msgstr "" + +#: ../../../docs/faq.md:114 +msgid "" +"All services run in Docker containers (most being officially provided by " +"each component's developers), so we're not at the mercy of distro " +"packaging." +msgstr "" + +#: ../../../docs/faq.md:116 +msgid "Why use this playbook and not just use the Docker image directly?" +msgstr "" + +#: ../../../docs/faq.md:118 +msgid "Reasons are similar to the reasons for not installing manually." +msgstr "" + +#: ../../../docs/faq.md:120 +msgid "" +"Besides Synapse, you'd need other things - a Postgres database, likely " +"the [Element](https://element.io) client, etc., etc." +msgstr "" + +#: ../../../docs/faq.md:122 +msgid "" +"Using the playbook, you get all these components in a way that works well" +" together out of the box." +msgstr "" + +#: ../../../docs/faq.md:124 +msgid "Occasionally I see some people are talking about \"MDAD\". What is it?" +msgstr "" + +#: ../../../docs/faq.md:126 +msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." +msgstr "" + +#: ../../../docs/faq.md:128 +msgid "" +"What's different about this Ansible playbook compared to [EMnify/matrix-" +"synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-" +"deploy)?" +msgstr "" + +#: ../../../docs/faq.md:130 +msgid "" +"This is similar to the [EMnify/matrix-synapse-auto-" +"deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible " +"deployment, but:" +msgstr "" + +#: ../../../docs/faq.md:132 +msgid "" +"this one is a complete Ansible playbook (instead of just a role), so it's" +" **easier to run** - especially for folks not familiar with Ansible" +msgstr "" + +#: ../../../docs/faq.md:134 +msgid "" +"this one installs and hooks together **a lot more Matrix-related " +"services** for you (see above)" +msgstr "" + +#: ../../../docs/faq.md:136 +msgid "this one **can be executed more than once** without causing trouble" +msgstr "" + +#: ../../../docs/faq.md:138 +msgid "" +"works on various distros: **CentOS** (7.0+), Debian-based distributions " +"(**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" +msgstr "" + +#: ../../../docs/faq.md:140 +msgid "" +"this one installs everything in a single directory (`/matrix` by default)" +" and **doesn't \"contaminate\" your server** with files all over the " +"place" +msgstr "" + +#: ../../../docs/faq.md:142 +msgid "" +"this one **doesn't necessarily take over** ports 80 and 443. By default, " +"it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but " +"you can also [use your own webserver](configuring-playbook-own-" +"webserver.md)" +msgstr "" + +#: ../../../docs/faq.md:144 +msgid "" +"this one **runs everything in Docker containers**, so it's likely more " +"predictable and less fragile (see [Docker images used by this playbook" +"](container-images.md))" +msgstr "" + +#: ../../../docs/faq.md:146 +msgid "" +"this one retrieves and automatically renews free [Let's " +"Encrypt](https://letsencrypt.org/) **SSL certificates** for you" +msgstr "" + +#: ../../../docs/faq.md:148 +msgid "" +"this one optionally can store the `media_store` content repository files " +"on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files" +" on the server's filesystem)" +msgstr "" + +#: ../../../docs/faq.md:150 +msgid "" +"this one optionally **allows you to use an external PostgreSQL server** " +"for Synapse's database (but defaults to running one in a container)" +msgstr "" + +#: ../../../docs/faq.md:152 +msgid "" +"helps you **import data from a previous installation** (so you can " +"migrate your manual virtualenv/Docker setup to a more managed one)" +msgstr "" + +#: ../../../docs/faq.md:154 +msgid "this one is actually **maintained**" +msgstr "" + +#: ../../../docs/faq.md:156 +msgid "Server-related" +msgstr "" + +#: ../../../docs/faq.md:158 +msgid "" +"What kind of server do I need to install Matrix using this Ansible " +"playbook?" +msgstr "" + +#: ../../../docs/faq.md:160 +msgid "We list our server requirements in [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/faq.md:162 +msgid "Why not run Matrix on Kubernetes?" +msgstr "" + +#: ../../../docs/faq.md:164 +msgid "" +"There's no reason not to run Matrix on " +"[Kubernetes](https://kubernetes.io/)." +msgstr "" + +#: ../../../docs/faq.md:166 +msgid "" +"However, that's overly complicated for thousands of us who just want to " +"run a single small (and sometimes not so small) Matrix server, either " +"using \"cloud\" servers or even a [Raspberry " +"Pi](https://www.raspberrypi.org/) at home." +msgstr "" + +#: ../../../docs/faq.md:168 +msgid "" +"For us, a Kubernetes-based setup which requires a cluster of multiple " +"computers and is more technically-involved is a no-go." +msgstr "" + +#: ../../../docs/faq.md:170 +msgid "" +"There are others working on automating a Matrix-on-Kubernetes setup, such" +" as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21" +"/matrix-chart." +msgstr "" + +#: ../../../docs/faq.md:172 +msgid "Why don't you use Podman instead of Docker?" +msgstr "" + +#: ../../../docs/faq.md:174 +msgid "" +"We like the philosophy of a daemonless container runtime, but " +"[Podman](https://podman.io) is just not ready for our use case yet." +msgstr "" + +#: ../../../docs/faq.md:176 +msgid "" +"Learn more about our past experiences/attempts to give Podman a chance, " +"by reading [this issue](https://github.com/spantaleev/matrix-docker-" +"ansible-deploy/issues/520)." +msgstr "" + +#: ../../../docs/faq.md:178 +msgid "In short, `alias podman=docker` is a lie (for us)." +msgstr "" + +#: ../../../docs/faq.md:180 +msgid "Why use Docker?" +msgstr "" + +#: ../../../docs/faq.md:182 +msgid "" +"[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the " +"other one being [systemd](https://systemd.io/))." +msgstr "" + +#: ../../../docs/faq.md:184 +msgid "" +"It lets us run services in an isolated manner and independently of the " +"(usually old) packages available for distributions." +msgstr "" + +#: ../../../docs/faq.md:186 +msgid "" +"It also lets us have a unified setup which runs the same across various " +"supported distros (see them on [Prerequisites](prerequisites.md))." +msgstr "" + +#: ../../../docs/faq.md:188 +msgid "Is Docker a hard requirement?" +msgstr "" + +#: ../../../docs/faq.md:190 +msgid "" +"Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-" +"podman-instead-of-docker) for why we're not using another container " +"runtime." +msgstr "" + +#: ../../../docs/faq.md:192 +msgid "" +"All of our services run in containers. It's how we achieve predictability" +" and also how we support tens of different services across lots of " +"distros." +msgstr "" + +#: ../../../docs/faq.md:194 +msgid "" +"The only thing we need on the distro is systemd and Python (we install " +"Docker ourselves, unless you ask us not to)." +msgstr "" + +#: ../../../docs/faq.md:196 +msgid "Why don't you use docker-compose?" +msgstr "" + +#: ../../../docs/faq.md:198 +msgid "" +"Instead of using [docker-compose](https://docs.docker.com/compose/), we " +"prefer installing systemd services and scheduling those independently." +msgstr "" + +#: ../../../docs/faq.md:200 +msgid "" +"There are people who have worked on turning this setup into a docker-" +"compose-based one. See these experiments " +"[here](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/64#issuecomment-603164625). There is also a demo project " +"([element-docker-demo](https://github.com/element-hq/element-docker-" +"demo)) by Element." +msgstr "" + +#: ../../../docs/faq.md:202 +msgid "Can I run this on a distro without systemd?" +msgstr "" + +#: ../../../docs/faq.md:204 +msgid "" +"No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the" +" other one being [Docker](https://www.docker.com/))." +msgstr "" + +#: ../../../docs/faq.md:206 +msgid "Can I install this on a Raspberry Pi?" +msgstr "" + +#: ../../../docs/faq.md:208 +msgid "" +"Yes, you can. See our [Alternative Architectures](alternative-" +"architectures.md) documentation page." +msgstr "" + +#: ../../../docs/faq.md:210 +msgid "" +"Whether a Raspberry Pi has enough power to give you a good experience is " +"another question. It depends on your use case." +msgstr "" + +#: ../../../docs/faq.md:212 +msgid "" +"Also see: [What kind of server specs do I need?](#what-kind-of-server-" +"specs-do-i-need)." +msgstr "" + +#: ../../../docs/faq.md:214 +msgid "What kind of server specs do I need?" +msgstr "" + +#: ../../../docs/faq.md:216 +msgid "" +"This largely depends on your use case. It's not so much the number of " +"users that you plan to host, but rather the number of large rooms they " +"will join." +msgstr "" + +#: ../../../docs/faq.md:218 +msgid "" +"Federated rooms with lots of history and containing hundreds of other " +"servers are very heavy CPU-wise and memory-wise." +msgstr "" + +#: ../../../docs/faq.md:220 +msgid "" +"You can probably use a 1 CPU + 1GB memory server to host hundreds of " +"local users just fine, but as soon as one of them joins a federated room " +"like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say " +"`##linux`), your server will get the need for a lot more power (at least " +"2GB RAM, etc)." +msgstr "" + +#: ../../../docs/faq.md:222 +msgid "" +"Running Matrix on a server with 1GB of memory is possible (especially if " +"you disable some not-so-important services). See [How do I optimize this " +"setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-" +"power-server)." +msgstr "" + +#: ../../../docs/faq.md:224 +msgid "" +"**We recommend starting with a server having at least 2GB of memory** and" +" even then using it sparingly. If you know for sure you'll be joining " +"various large rooms, etc., then going for 4GB of memory or more is a good" +" idea." +msgstr "" + +#: ../../../docs/faq.md:226 +msgid "" +"Besides the regular Matrix stuff, we also support things like video-" +"conferencing using [Jitsi](configuring-playbook-jitsi.md) and other " +"additional services which (when installed) may use up a lot of memory. " +"Things do add up. Besides the Synapse Matrix server, Jitsi is especially " +"notorious for consuming a lot of resources. If you plan on running Jitsi," +" we recommend a server with at least 2GB of memory (preferrably more). " +"See our [Jitsi documentation page](configuring-playbook-jitsi.md) to " +"learn how to optimize its memory/CPU usage." +msgstr "" + +#: ../../../docs/faq.md:228 +msgid "Can I run this in an LXC container?" +msgstr "" + +#: ../../../docs/faq.md:230 +msgid "" +"If your distro runs within an [LXC " +"container](https://linuxcontainers.org/), you may hit [this " +"issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/703). It can be worked around, if absolutely necessary, but" +" we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/faq.md:232 +msgid "Configuration" +msgstr "" + +#: ../../../docs/faq.md:234 +msgid "Why install my server at matrix.example.com and not at the base domain?" +msgstr "" + +#: ../../../docs/faq.md:236 +msgid "" +"It's the same with email servers. Your email address is likely " +"`name@company.com`, not `name@mail.company.com`, even though it's " +"`mail.company.com` that is really handling your data for `@company.com` " +"email to work." +msgstr "" + +#: ../../../docs/faq.md:238 +msgid "" +"Using a separate domain name is easier to manage (although it's a little " +"hard to get right at first) and keeps your Matrix server isolated from " +"your website (if you have one), from your email server (if you have one)," +" etc. Therefore, this playbook sets up services on your Matrix server " +"(`matrix.example.com`) by default." +msgstr "" + +#: ../../../docs/faq.md:240 +msgid "" +"I don't control anything on the base domain and can't set up delegation " +"to matrix.example.com. What do I do?" +msgstr "" + +#: ../../../docs/faq.md:242 +msgid "" +"If you're not in control of your base domain (or the server handling it) " +"at all, you can take a look at [How do I install on matrix.example.com " +"without involving the base domain?](#how-do-i-install-on-" +"matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:244 +msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?" +msgstr "" + +#: ../../../docs/faq.md:246 +msgid "" +"If you really can't obtain an HTTPS certificate for your base domain, you" +" can take a look at [How do I install on matrix.example.com without " +"involving the base domain?](#how-do-i-install-on-matrixexamplecom-" +"without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:248 +msgid "How do I install on matrix.example.com without involving the base domain?" +msgstr "" + +#: ../../../docs/faq.md:250 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:271 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/faq.md:278 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/faq.md:280 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/faq.md:282 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/faq.md:284 +msgid "" +"Without setting up [server delegation](howto-server-delegation.md) to " +"`matrix.example.com`, your user IDs will be like " +"`@alice:matrix.example.com`. This is equivalent to having an email " +"address like `bob@mail.company.com`, instead of just `bob@company.com`." +msgstr "" + +#: ../../../docs/faq.md:286 +msgid "" +"I don't use the base domain for anything. How am I supposed to set up " +"Server Delegation for Matrix services?" +msgstr "" + +#: ../../../docs/faq.md:288 +msgid "" +"If you don't use your base domain for anything, then it's hard for you to" +" \"serve files over HTTPS\" on it -- something we ask you to do for the " +"[.well-known](configuring-well-known.md) setup (needed for [Server " +"Delegation](howto-server-delegation.md))." +msgstr "" + +#: ../../../docs/faq.md:290 +msgid "" +"Luckily, the playbook can set up your Matrix server (at " +"`matrix.example.com`) to also handle traffic for the base domain " +"(`example.com`)." +msgstr "" + +#: ../../../docs/faq.md:292 +msgid "" +"See [Serving the base domain](configuring-playbook-base-domain-" +"serving.md)." +msgstr "" + +#: ../../../docs/faq.md:294 +msgid "How do I optimize this setup for a low-power server?" +msgstr "" + +#: ../../../docs/faq.md:296 +msgid "You can disable some not-so-important services to save on memory." +msgstr "" + +#: ../../../docs/faq.md:318 +msgid "" +"You can also consider implementing a restriction on room complexity, in " +"order to prevent users from joining very heavy rooms:" +msgstr "" + +#: ../../../docs/faq.md:328 +msgid "" +"If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed" +" by default), there are additional optimizations listed on its " +"documentation page that you can perform." +msgstr "" + +#: ../../../docs/faq.md:330 +msgid "" +"I already have Docker on my server. Can you stop installing Docker via " +"the playbook?" +msgstr "" + +#: ../../../docs/faq.md:332 +msgid "" +"Yes, we can stop installing Docker ourselves. Just use this in your " +"`vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:338 +msgid "" +"I run another webserver on the same server where I wish to install " +"Matrix. What now?" +msgstr "" + +#: ../../../docs/faq.md:340 +msgid "" +"By default, we install a webserver for you " +"([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your " +"own webserver](configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../docs/faq.md:342 +msgid "How is the effective configuration determined?" +msgstr "" + +#: ../../../docs/faq.md:344 +msgid "" +"Configuration variables are defined in multiple places in this playbook " +"and are considered in this order:" +msgstr "" + +#: ../../../docs/faq.md:346 +msgid "" +"there are defaults coming from each role's defaults file " +"(`role/matrix*/defaults/main.yml`). These variable values aim to be good " +"defaults for when the role is used standalone (outside of this collection" +" of roles, also called playbook)." +msgstr "" + +#: ../../../docs/faq.md:348 +msgid "" +"then, there are overrides in `group_vars/matrix_servers`, which aim to " +"adjust these \"standalone role defaults\" to something which better fits " +"the playbook in its entirety." +msgstr "" + +#: ../../../docs/faq.md:350 +msgid "" +"finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` " +"file, which is the ultimate override" +msgstr "" + +#: ../../../docs/faq.md:352 +msgid "What configuration variables are available?" +msgstr "" + +#: ../../../docs/faq.md:354 +msgid "" +"You can discover the variables you can override in each role " +"(`roles/*/*/defaults/main.yml`)." +msgstr "" + +#: ../../../docs/faq.md:356 +msgid "" +"As described in [How is the effective configuration determined?](#how-is-" +"the-effective-configuration-determined), these role-defaults may be " +"overriden by values defined in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/faq.md:358 +msgid "" +"Refer to both of these for inspiration. Still, as mentioned in " +"[Configuring the playbook](configuring-playbook.md), you're only ever " +"supposed to edit your own " +"`inventory/host_vars/matrix.example.com/vars.yml` file and nothing else " +"inside the playbook (unless you're meaning to contribute new features)." +msgstr "" + +#: ../../../docs/faq.md:360 ../../../docs/faq.md:372 +msgid "" +"**Note**: some of the roles (`roles/galaxy/*`) live in separate " +"repositories and are only installed after your run `just roles` (or `make" +" roles`) or `just update` (which automatically does `git pull` and `just " +"roles`)." +msgstr "" + +#: ../../../docs/faq.md:362 +msgid "" +"I'd like to adjust some configuration which doesn't have a corresponding " +"variable. How do I do it?" +msgstr "" + +#: ../../../docs/faq.md:364 +msgid "" +"The playbook doesn't aim to expose all configuration settings for all " +"services using variables. Doing so would amount to hundreds of variables " +"that we have to create and maintain." +msgstr "" + +#: ../../../docs/faq.md:366 +msgid "" +"Instead, we only try to make some important basics configurable using " +"dedicated variables you can see in each role. See [What configuration " +"variables are available?](#what-configuration-variables-are-available)." +msgstr "" + +#: ../../../docs/faq.md:368 +msgid "" +"Besides that, each role (component) aims to provide a " +"`matrix_SOME_COMPONENT_configuration_extension_yaml` (or " +"`matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can" +" be used to override the configuration." +msgstr "" + +#: ../../../docs/faq.md:370 +msgid "" +"Check each role's `roles/*/*/defaults/main.yml` for the corresponding " +"variable and an example for how use it." +msgstr "" + +#: ../../../docs/faq.md:374 +msgid "Installation" +msgstr "" + +#: ../../../docs/faq.md:376 +msgid "How do I run the installation?" +msgstr "" + +#: ../../../docs/faq.md:378 +msgid "" +"See [Installing](installing.md) to learn how to use Ansible to install " +"Matrix services." +msgstr "" + +#: ../../../docs/faq.md:380 +msgid "" +"However, we recommend you to follow our installation guide, instead of " +"jumping straight to installing." +msgstr "" + +#: ../../../docs/faq.md:382 +msgid "There are two guides available:" +msgstr "" + +#: ../../../docs/faq.md:384 +msgid "" +"⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended " +"for those who do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/faq.md:386 +msgid "" +"**Full installation guide (for advanced users)**: if you need to import " +"an existing Matrix server's data into the new server or want to learn " +"more while setting up the server, follow this guide by starting with the " +"**[Prerequisites](prerequisites.md)** documentation page." +msgstr "" + +#: ../../../docs/faq.md:388 +msgid "" +"I installed Synapse some other way. Can I migrate such a setup to the " +"playbook?" +msgstr "" + +#: ../../../docs/faq.md:390 +msgid "Yes, you can." +msgstr "" + +#: ../../../docs/faq.md:392 +msgid "" +"You generally need to do a playbook installation. It's recommended to " +"follow the full installation guide (starting at the " +"[Prerequisites](prerequisites.md) page), not the [Quick start](quick-" +"start.md) guide. The full installation guide will tell you when it's time" +" to import your existing data into the newly-prepared server." +msgstr "" + +#: ../../../docs/faq.md:394 +msgid "" +"This Ansible playbook guides you into installing a server for " +"`example.com` (user IDs are like this: `@alice:example.com`), while the " +"server is at `matrix.example.com`. If your existing setup has a server " +"name (`server_name` configuration setting in Synapse's `homeserver.yaml` " +"file) other than the base `example.com`, you may need to tweak some " +"additional variables. This FAQ entry may be of use if you're dealing with" +" a more complicated setup - [How do I install on matrix.example.com " +"without involving the base domain?](#how-do-i-install-on-" +"matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:396 +msgid "" +"After configuring the playbook and installing and **before starting** " +"services (done with `ansible-playbook … --tags=start`) you'd import [your" +" SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-" +"postgres.md)) database and also [import your media store](importing-" +"synapse-media-store.md)." +msgstr "" + +#: ../../../docs/faq.md:398 +msgid "" +"I've downloaded Ansible and the playbook on the server. It can't connect " +"using SSH." +msgstr "" + +#: ../../../docs/faq.md:400 +msgid "" +"If you're using the playbook directly on the server, then Ansible doesn't" +" need to connect using SSH." +msgstr "" + +#: ../../../docs/faq.md:402 +msgid "" +"It can perform a local connection instead. Just set " +"`ansible_connection=local` at the end of the server line in " +"`inventory/hosts` and re-run the playbook." +msgstr "" + +#: ../../../docs/faq.md:404 +msgid "" +"If you're running Ansible from within a container (one of the " +"possibilities we list on our [dedicated Ansible documentation " +"page](ansible.md)), then using `ansible_connection=local` is not " +"possible." +msgstr "" + +#: ../../../docs/faq.md:406 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/faq.md:408 +msgid "" +"I get \"Error response from daemon: configured logging driver does not " +"support reading\" when I do `docker logs matrix-synapse`." +msgstr "" + +#: ../../../docs/faq.md:410 +msgid "See [How can I see the logs?](#how-can-i-see-the-logs)." +msgstr "" + +#: ../../../docs/faq.md:412 +msgid "How can I see the logs?" +msgstr "" + +#: ../../../docs/faq.md:414 +msgid "" +"We utilize " +"[systemd/journald](https://www.freedesktop.org/software/systemd/man" +"/systemd-journald.service.html#Description) for logging." +msgstr "" + +#: ../../../docs/faq.md:416 +msgid "" +"To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You" +" may wish to see the [manual page for " +"journalctl](https://www.commandlinux.com/man-" +"page/man1/journalctl.1.html)." +msgstr "" + +#: ../../../docs/faq.md:418 +msgid "" +"Available service names can be seen by doing `ls " +"/etc/systemd/system/matrix*.service` on the server." +msgstr "" + +#: ../../../docs/faq.md:420 +msgid "" +"Some services also log to files in `/matrix/*/data/..`, but we're slowly " +"moving away from that." +msgstr "" + +#: ../../../docs/faq.md:422 +msgid "" +"We also disable Docker logging, so you can't use `docker logs matrix-*` " +"either. We do this to prevent useless double (or even triple) logging and" +" to avoid having to rotate log files." +msgstr "" + +#: ../../../docs/faq.md:424 +msgid "" +"We just simply delegate logging to journald and it takes care of " +"persistence and expiring old data." +msgstr "" + +#: ../../../docs/faq.md:426 +msgid "" +"Also see: [How long do systemd/journald logs persist for?](#how-long-do-" +"systemdjournald-logs-persist-for)" +msgstr "" + +#: ../../../docs/faq.md:428 +msgid "How long do systemd/journald logs persist for?" +msgstr "" + +#: ../../../docs/faq.md:430 +msgid "" +"On some distros, the journald logs are just in-memory and not persisted " +"to disk." +msgstr "" + +#: ../../../docs/faq.md:432 +msgid "" +"Consult (and feel free to adjust) your distro's journald logging " +"configuration in `/etc/systemd/journald.conf`." +msgstr "" + +#: ../../../docs/faq.md:434 +msgid "" +"To enable persistence and put some limits on how large the journal log " +"files can become, adjust your configuration like this:" +msgstr "" + +#: ../../../docs/faq.md:445 +msgid "Maintenance" +msgstr "" + +#: ../../../docs/faq.md:447 +msgid "Do I need to do anything to keep my Matrix server updated?" +msgstr "" + +#: ../../../docs/faq.md:449 +msgid "Yes. We don't update anything for you automatically." +msgstr "" + +#: ../../../docs/faq.md:451 +msgid "" +"See our [documentation page about upgrading services](maintenance-" +"upgrading-services.md)." +msgstr "" + +#: ../../../docs/faq.md:453 +msgid "How do I move my existing installation to another (VM) server?" +msgstr "" + +#: ../../../docs/faq.md:455 +msgid "" +"If you have an existing installation done using this Ansible playbook, " +"you can easily migrate that to another server using [our dedicated server" +" migration guide](maintenance-migrating.md)." +msgstr "" + +#: ../../../docs/faq.md:457 +msgid "" +"If your previous installation is done in some other way (not using this " +"Ansible playbook), see [I installed Synapse some other way. Can I migrate" +" such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i" +"-migrate-such-a-setup-to-the-playbook)." +msgstr "" + +#: ../../../docs/faq.md:459 +msgid "How do I back up the data on my server?" +msgstr "" + +#: ../../../docs/faq.md:461 +msgid "We haven't documented this properly yet, but the general advice is to:" +msgstr "" + +#: ../../../docs/faq.md:463 +msgid "" +"back up Postgres by making a database dump. See [Backing up PostgreSQL" +"](maintenance-postgres.md#backing-up-postgresql)" +msgstr "" + +#: ../../../docs/faq.md:465 +msgid "" +"back up all `/matrix` files, except for `/matrix/postgres/data` (you " +"already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` " +"(this directory may exist and contain your old data if you've [performed " +"a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +msgstr "" + +#: ../../../docs/faq.md:467 +msgid "You can later restore these by:" +msgstr "" + +#: ../../../docs/faq.md:469 +msgid "Restoring the `/matrix` directory and files on the new server manually" +msgstr "" + +#: ../../../docs/faq.md:470 +msgid "" +"Following the instruction described on [Installing a server into which " +"you'll import old data](installing.md#installing-a-server-into-which-" +"youll-import-old-data)" +msgstr "" + +#: ../../../docs/faq.md:472 +msgid "" +"If your server's IP address has changed, you may need to [set up DNS" +"](configuring-dns.md) again." +msgstr "" + +#: ../../../docs/faq.md:474 +msgid "" +"What is this `/matrix/postgres/data-auto-upgrade-backup` directory that " +"is taking up so much space?" +msgstr "" + +#: ../../../docs/faq.md:476 +msgid "" +"When you [perform a major Postgres upgrade](maintenance-postgres.md" +"#upgrading-postgresql), we save the the old data files in " +"`/matrix/postgres/data-auto-upgrade-backup`, just so you could easily " +"restore them should something have gone wrong." +msgstr "" + +#: ../../../docs/faq.md:478 +msgid "" +"After verifying that everything still works after the Postgres upgrade, " +"you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +msgstr "" + +#: ../../../docs/faq.md:480 +msgid "How do I debug or force SSL certificate renewal?" +msgstr "" + +#: ../../../docs/faq.md:482 +msgid "" +"SSL certificates are managed automatically by the " +"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." +msgstr "" + +#: ../../../docs/faq.md:484 +msgid "" +"If you're having trouble with SSL certificate renewal, check the Traefik " +"logs (`journalctl -fu matrix-traefik`)." +msgstr "" + +#: ../../../docs/faq.md:486 +msgid "" +"If you're [using your own webserver](configuring-playbook-own-" +"webserver.md) instead of the integrated one (Traefik), you should " +"investigate in another way." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po new file mode 100644 index 000000000..c81d847ca --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po @@ -0,0 +1,118 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/getting-the-playbook.md:1 +msgid "Getting the playbook" +msgstr "" + +#: ../../../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:5 +msgid "" +"This Ansible playbook is meant to be executed on your own computer (not " +"the Matrix server)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:7 +msgid "" +"In special cases (if your computer cannot run Ansible, etc.) you may put " +"the playbook on the server as well." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:9 +msgid "You can retrieve the playbook's source code by:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:11 +msgid "" +"[Using git to get the playbook](#using-git-to-get-the-playbook) " +"(recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:13 +msgid "" +"[Downloading the playbook as a ZIP archive](#downloading-the-playbook-" +"as-a-zip-archive) (not recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:15 +msgid "Using git to get the playbook" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:17 +msgid "" +"We recommend using the [git](https://git-scm.com/) tool to get the " +"playbook's source code, because it lets you easily keep up to date in the" +" future when [Maintaining services](maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:19 +msgid "" +"Once you've installed git on your computer, you can go to any directory " +"of your choosing and run the following command to retrieve the playbook's" +" source code:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:25 +msgid "" +"This will create a new `matrix-docker-ansible-deploy` directory. You're " +"supposed to execute all other installation commands inside that " +"directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:27 +msgid "Downloading the playbook as a ZIP archive" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:29 +msgid "" +"Alternatively, you can download the playbook as a ZIP archive. This is " +"not recommended, as it's not easy to keep up to date with future updates." +" We suggest you [use git](#using-git-to-get-the-playbook) instead." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:31 +msgid "" +"The latest version is always at the following URL: " +"https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/archive/master.zip" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:33 +msgid "" +"You can extract this archive anywhere. You'll get a directory called " +"`matrix-docker-ansible-deploy-master`. You're supposed to execute all " +"other installation commands inside that directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:37 +msgid "" +"[▶️](configuring-playbook.md) No matter which method you've used to " +"download the playbook, you can proceed by [Configuring the playbook" +"](configuring-playbook.md)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po new file mode 100644 index 000000000..6c64fd20f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po @@ -0,0 +1,300 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/howto-server-delegation.md:1 +msgid "Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:3 +msgid "" +"By default, this playbook sets up services on your Matrix server " +"(`matrix.example.com`). To have this server officially be responsible for" +" Matrix services for the base domain (`example.com`), you need to set up " +"server delegation / redirection." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:5 +msgid "Server delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:7 +msgid "" +"[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a" +"-well-known-file) on the base domain (`example.com`)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:8 +msgid "" +"[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a" +"-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:10 +msgid "" +"Both methods have their place and will continue to do so. You only need " +"to use just one of these delegation methods." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:12 +msgid "" +"For simplicity reasons, this playbook recommends you to set up server " +"delegation via a `/.well-known/matrix/server` file. However, that method " +"may have some downsides that are not to your liking. Hence this guide " +"about alternative ways to set up Server Delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:14 +msgid "" +"**Note**: as an alternative, it is possible to install the server such " +"that it uses only the `matrix.example.com` domain (instead of identifying" +" as the shorter base domain - `example.com`). This should be helpful if " +"you are not in control of anything on the base domain (`example.com`). In" +" this case, you would not need to configure server delegation, but you " +"would need to add other configuration. For more information, see [How do " +"I install on matrix.example.com without involving the base " +"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" +"the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:16 +msgid "Server Delegation via a well-known file" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:18 +msgid "" +"This playbook recommends you to set up server delegation by means of a " +"`/.well-known/matrix/server` file served from the base domain " +"(`example.com`), as this is the most straightforward way to set up the " +"delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:20 +msgid "" +"To configure server delegation with the well-known file, check this " +"section on [Configuring Service Discovery via .well-known](configuring-" +"well-known.md): [Installing well-known files on the base domain's server" +"](configuring-well-known.md#installing-well-known-files-on-the-base-" +"domain-s-server)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:22 +msgid "Downsides of well-known-based Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:24 +msgid "" +"Server Delegation by means of a `/.well-known/matrix/server` file is the " +"most straightforward, but suffers from the following downsides:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:26 +msgid "" +"you need to have a working HTTPS server for the base domain " +"(`example.com`). If you don't have any server for the base domain at all," +" you can easily solve it by making the playbook [serve the base domain " +"from the Matrix server](configuring-playbook-base-domain-serving.md)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:28 +msgid "" +"any downtime on the base domain (`example.com`) or network trouble " +"between the Matrix subdomain (`matrix.example.com`) and the base " +"`example.com` may cause Matrix Federation outages. As the [Server-Server " +"spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" +"discovery):" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:30 +msgid "" +"Errors are recommended to be cached for up to an hour, and servers are " +"encouraged to exponentially back off for repeated failures." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:32 +msgid "" +"**For most people, this is a reasonable tradeoff** given that it's easy " +"and straightforward to set up. We recommend you stay on this path." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:34 +msgid "" +"Otherwise, you can decide to go against the default for this playbook, " +"and instead set up [Server Delegation via a DNS SRV record (advanced" +")](#server-delegation-via-a-dns-srv-record-advanced) (much more " +"complicated)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:36 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:38 +msgid "" +"**Note**: doing Server Delegation via a DNS SRV record is a more " +"**advanced** way to do it and is not the default for this playbook. This " +"is usually **much more complicated** to set up, so **we don't recommend " +"it**. If you're not an experienced sysadmin, you'd better stay away from " +"this." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:40 +msgid "" +"As per the [Server-Server " +"spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" +"discovery), it's possible to do Server Delegation using only a SRV record" +" (without a `/.well-known/matrix/server` file)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:42 +msgid "" +"This prevents you from suffering the [Downsides of well-known-based " +"Server Delegation](#downsides-of-well-known-based-server-delegation)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:44 +msgid "To use DNS SRV record validation, you need to:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:46 +msgid "" +"ensure that `/.well-known/matrix/server` is **not served** from the base " +"domain, as that would interfere with DNS SRV record Server Delegation. To" +" make the playbook **not** generate and serve the file, use the following" +" configuration: `matrix_static_files_file_matrix_server_enabled: false`." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:48 +msgid "" +"ensure that you have a `_matrix._tcp` DNS SRV record for your base domain" +" (`example.com`) with a value of `10 0 8448 matrix.example.com`" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:50 +msgid "" +"ensure that you are serving the Matrix Federation API (tcp/8448) with a " +"certificate for `example.com` (not `matrix.example.com`!). Getting this " +"certificate to the `matrix.example.com` server may be complicated. The " +"playbook's automatic SSL obtaining/renewal flow will likely not work and " +"you'll need to copy certificates around manually. See below." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:52 +msgid "" +"For more details on how to configure the playbook to work with SRV " +"delegation, take a look at this documentation: [Server Delegation via a " +"DNS SRV record (advanced)](howto-srv-server-delegation.md)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:54 +msgid "Obtaining certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:56 +msgid "" +"How you can obtain a valid certificate for `example.com` on the " +"`matrix.example.com` server is up to you." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:58 +msgid "" +"If `example.com` and `matrix.example.com` are hosted on the same machine," +" you can let the playbook obtain the certificate for you, by following " +"our [Obtaining SSL certificates for additional domains](configuring-" +"playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-" +"domains) guide." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:60 +msgid "" +"If `example.com` and `matrix.example.com` are not hosted on the same " +"machine, you can copy over the certificate files manually. Don't forget " +"that they may get renewed once in a while, so you may also have to " +"transfer them periodically. How often you do that is up to you, as long " +"as the certificate files don't expire." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:62 +msgid "Serving the Federation API with your certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:64 +msgid "" +"Regardless of which method for obtaining certificates you've used, once " +"you've managed to get certificates for your base domain onto the " +"`matrix.example.com` machine you can put them to use." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:66 +msgid "Based on your setup, you have different ways to go about it:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:68 +msgid "" +"Serving the Federation API with your certificates and Synapse handling " +"Federation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:70 +msgid "You can let Synapse handle Federation by itself." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:72 +msgid "" +"To do that, make sure the certificate files are mounted into the Synapse " +"container:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:79 +msgid "" +"You can then tell Synapse to serve Federation traffic over TLS on " +"`tcp/8448`:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:87 +msgid "" +"Make sure to reload Synapse once in a while (`systemctl reload matrix-" +"synapse`), so that newer certificates can kick in. Reloading doesn't " +"cause any downtime." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:89 +msgid "Serving the Federation API with your certificates and another webserver" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:91 +msgid "" +"**Alternatively**, if you are using another webserver, you can set up " +"reverse-proxying for the `tcp/8448` port by yourself. Make sure to use " +"the proper certificates for `example.com` (not for `matrix.example.com`) " +"when serving the `tcp/8448` port." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:93 +msgid "" +"As recommended in our [Fronting the integrated reverse-proxy webserver " +"with another reverse-proxy](./configuring-playbook-own-webserver.md" +"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" +"proxy) documentation section, we recommend you to expose the Matrix " +"Federation entrypoint from traffic at a local port (e.g. " +"`127.0.0.1:8449`), so your reverese-proxy should send traffic there." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po new file mode 100644 index 000000000..51f8e250b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po @@ -0,0 +1,218 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/howto-srv-server-delegation.md:1 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:3 +msgid "" +"**Reminder** : unless you are affected by the [Downsides of well-known-" +"based Server Delegation](howto-server-delegation.md#downsides-of-well-" +"known-based-server-delegation), we suggest you **stay on the " +"simple/default path**: [Server Delegation](howto-server-delegation.md) by" +" [configuring well-known files](configuring-well-known.md) at the base " +"domain." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:5 +msgid "" +"This guide is about configuring Server Delegation using DNS SRV records " +"(for the [Traefik](https://doc.traefik.io/traefik/) webserver). This " +"method has special requirements when it comes to SSL certificates, so " +"various changes are required." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:9 +msgid "" +"SRV delegation while still using the playbook provided Traefik to get / " +"renew the certificate requires a wildcard certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:11 +msgid "" +"To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one" +" needs to use a [DNS-01 challenge](https://letsencrypt.org/docs" +"/challenge-types/#dns-01-challenge) method instead of the default " +"[HTTP-01](https://letsencrypt.org/docs/challenge-" +"types/#http-01-challenge)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:13 +msgid "" +"This means that this is **limited to the list of DNS providers supported " +"by Traefik**, unless you bring in your own certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:15 +msgid "" +"The up-to-date list can be accessed on [traefik's " +"documentation](https://doc.traefik.io/traefik/https/acme/#providers)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:17 +msgid "The changes" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:19 +msgid "" +"**Note**: the changes below instruct you how to do this for a basic " +"Synapse installation. You will need to adapt the variable name and the " +"content of the labels:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:21 +msgid "" +"if you're using another homeserver implementation (e.g. [Conduit" +"](./configuring-playbook-conduit.md) or [Dendrite](./configuring-" +"playbook-dendrite.md))" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:22 +msgid "" +"if you're using [Synapse with workers enabled](./configuring-playbook-" +"synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled:" +" true`). In that case, it's actually the `matrix-synapse-reverse-proxy-" +"companion` service which has Traefik labels attached" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:24 +msgid "" +"Also, all instructions below are from an older version of the playbook " +"and may not work anymore." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:26 +msgid "Federation Endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:33 +msgid "" +"This is because with SRV federation, some servers / tools (one of which " +"being the federation tester) try to access the federation API using the " +"resolved IP address instead of the domain name (or they are not using " +"SNI). This change will make Traefik route all traffic for which the path " +"match this rule go to the federation endpoint." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:35 +msgid "Tell Traefik which certificate to serve for the federation endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:37 +msgid "" +"Now that the federation endpoint is not bound to a domain anymore we need" +" to explicitely tell Traefik to use a wildcard certificate in addition to" +" one containing the base name." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:39 +msgid "" +"This is because the Matrix specification expects the federation endpoint " +"to be served using a certificate compatible with the base domain, " +"however, the other resources on the endpoint still need a valid " +"certificate to work." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:48 +msgid "Configure the DNS-01 challenge for let's encrypt" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:50 +msgid "" +"Since we're now requesting a wildcard certificate, we need to change the " +"ACME challenge method. To request a wildcard certificate from Let's " +"Encrypt we are required to use the DNS-01 challenge." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:52 +msgid "This will need 3 changes:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:53 +msgid "Add a new certificate resolver that works with DNS-01" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:54 +msgid "" +"Configure the resolver to allow access to the DNS zone to configure the " +"records to answer the challenge (refer to [Traefik's " +"documentation](https://doc.traefik.io/traefik/https/acme/#providers) to " +"know which environment variables to set)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:55 +msgid "Tell the playbook to use the new resolver as default" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:57 +msgid "" +"We cannot just disable the default resolver as that would disable SSL in " +"quite a few places in the playbook." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:86 +msgid "Adjust Coturn's configuration" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:88 +msgid "The last step is to alter the generated Coturn configuration." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:90 +msgid "" +"By default, Coturn is configured to wait on the certificate for the " +"`matrix.` subdomain using an [instantiated systemd " +"service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates)" +" using the domain name as the parameter for this service. However, we " +"need to serve the wildcard certificate, which is incompatible with " +"systemd, it will try to expand the `*`, which will break and prevent " +"Coturn from starting." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:92 +msgid "We also need to indicate to Coturn where the wildcard certificate is." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:94 +msgid "" +"**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still " +"fail to start because Traefik is still in the process of obtaining the " +"certificates. If you still get an error, make sure Traefik obtained the " +"certificates and restart the Coturn service (`just start-group coturn`)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:96 +msgid "" +"This should not happen again afterwards as Traefik will renew " +"certificates well before their expiry date, and the Coturn service is " +"setup to restart periodically." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:122 +msgid "Full example of a working configuration" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po new file mode 100644 index 000000000..2c9f142b8 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/importing-postgres.md:1 +msgid "" +"Importing an existing Postgres database from another installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-postgres.md:3 +msgid "" +"Run this if you'd like to import your database from a previous " +"installation. (don't forget to import your Synapse `media_store` files as" +" well - see [the importing-synape-media-store guide](importing-synapse-" +"media-store.md))." +msgstr "" + +#: ../../../docs/importing-postgres.md:6 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-postgres.md:8 +msgid "" +"For this to work, **the database name in Postgres must match** what this " +"playbook uses. This playbook uses a Postgres database name of `synapse` " +"by default (controlled by the `matrix_synapse_database_database` " +"variable). If your database name differs, be sure to change " +"`matrix_synapse_database_database` to your desired name and to re-run the" +" playbook before proceeding." +msgstr "" + +#: ../../../docs/importing-postgres.md:10 +msgid "" +"The playbook supports importing Postgres dump files in **text** (e.g. " +"`pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > " +"dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) " +"is also supported." +msgstr "" + +#: ../../../docs/importing-postgres.md:12 +msgid "" +"The migration might be a good moment, to \"reset\" a not properly working" +" bridge. Be aware, that it might affect all users (new link to bridge, " +"new rooms, …)" +msgstr "" + +#: ../../../docs/importing-postgres.md:14 +msgid "" +"Before doing the actual import, **you need to upload your Postgres dump " +"file to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-postgres.md:16 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-postgres.md:18 +msgid "" +"To import, run this command (make sure to replace " +"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-postgres.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/importing-postgres.md:28 +msgid "" +"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres " +"dump file on the server (not on your local machine!)" +msgstr "" + +#: ../../../docs/importing-postgres.md:29 +msgid "" +"`postgres_default_import_database` defaults to `matrix`, which is useful " +"for importing multiple databases (for dumps made with `pg_dumpall`). If " +"you're importing a single database (e.g. `synapse`), consider changing " +"`postgres_default_import_database` accordingly" +msgstr "" + +#: ../../../docs/importing-postgres.md:30 +msgid "" +"after importing a large database, it's a good idea to run [an `ANALYZE` " +"operation](https://www.postgresql.org/docs/current/sql-analyze.html) to " +"make Postgres rebuild its database statistics and optimize its query " +"planner. You can easily do this via the playbook by running `just run-" +"tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see " +"[Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for " +"more details)." +msgstr "" + +#: ../../../docs/importing-postgres.md:32 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/importing-postgres.md:34 +msgid "Table Ownership" +msgstr "" + +#: ../../../docs/importing-postgres.md:36 +msgid "" +"A table ownership issue can occur if you are importing from a Synapse " +"installation which was both:" +msgstr "" + +#: ../../../docs/importing-postgres.md:38 +msgid "migrated from SQLite to Postgres, and" +msgstr "" + +#: ../../../docs/importing-postgres.md:39 +msgid "used a username other than 'synapse'" +msgstr "" + +#: ../../../docs/importing-postgres.md:41 +msgid "In this case you may run into the following error during the import task:" +msgstr "" + +#: ../../../docs/importing-postgres.md:47 +msgid "" +"where `synapse_user` is the database username from the previous Synapse " +"installation." +msgstr "" + +#: ../../../docs/importing-postgres.md:49 +msgid "" +"This can be verified by examining the dump for ALTER TABLE statements " +"which set OWNER TO that username:" +msgstr "" + +#: ../../../docs/importing-postgres.md:61 +msgid "" +"It can be worked around by changing the username to `synapse`, for " +"example by using `sed`:" +msgstr "" + +#: ../../../docs/importing-postgres.md:67 +msgid "" +"This uses sed to perform an 'in-place' (`-i`) replacement globally " +"(`/g`), searching for `synapse_user` and replacing with `synapse` " +"(`s/synapse_user/synapse`). If your database username was different, " +"change `synapse_user` to that username instead. Expand search/replace " +"statement as shown in example above, in case of old user name like " +"`matrix` - replacing `matrix` only would… well - you can imagine." +msgstr "" + +#: ../../../docs/importing-postgres.md:69 +msgid "" +"Note that if the previous import failed with an error it may have made " +"changes which are incompatible with re-running the import task right " +"away; if you do so it may fail with an error such as:" +msgstr "" + +#: ../../../docs/importing-postgres.md:75 +msgid "Repeat import" +msgstr "" + +#: ../../../docs/importing-postgres.md:77 +msgid "" +"In this case you can use the command suggested in the import task to " +"clear the database before retrying the import:" +msgstr "" + +#: ../../../docs/importing-postgres.md:85 +msgid "" +"Now on your local machine run `just run-tags setup-postgres` to prepare " +"the database roles etc." +msgstr "" + +#: ../../../docs/importing-postgres.md:87 +msgid "" +"If not, you probably get this error. `synapse` is the correct table " +"owner, but the role is missing in database." +msgstr "" + +#: ../../../docs/importing-postgres.md:93 +msgid "" +"Once the database is clear and the ownership of the tables has been fixed" +" in the SQL file, the import task should succeed." +msgstr "" + +#: ../../../docs/importing-postgres.md:95 +msgid "" +"Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths" +" (or even better, copy this line from your terminal)" +msgstr "" + +#: ../../../docs/importing-postgres.md:101 +msgid "Hints" +msgstr "" + +#: ../../../docs/importing-postgres.md:103 +msgid "To open psql terminal run `/matrix/postgres/bin/cli`" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po new file mode 100644 index 000000000..fea696edc --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/importing-synapse-media-store.md:1 +msgid "" +"Importing `media_store` data files from an existing Synapse installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:3 +msgid "" +"Run this if you'd like to import your `media_store` files from a previous" +" installation of Synapse." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:5 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:7 +msgid "" +"Before doing the actual data restore, **you need to upload your media " +"store directory to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:9 +msgid "" +"If you are [storing Matrix media files on Amazon S3](configuring-" +"playbook-s3.md) (optional), restoring with this tool is not possible " +"right now." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:11 +msgid "" +"As an alternative, you can perform a manual restore using the [AWS CLI " +"tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync " +"/path/to/server/media_store/. s3://name-of-bucket/`)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:13 +msgid "" +"**Note for Mac users**: Due to case-sensitivity issues on certain Mac " +"filesystems (HFS or HFS+), filename corruption may occur if you copy a " +"`media_store` directory to your Mac. If you're transferring a " +"`media_store` directory between 2 servers, make sure you do it directly " +"(from server to server with a tool such as " +"[rsync](https://rsync.samba.org/)), and not by downloading the files to " +"your Mac." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:15 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:17 +msgid "" +"Run this command (make sure to replace `` " +"with a path on your server):" +msgstr "" + +#: ../../../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 new file mode 100644 index 000000000..75d5fd67f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -0,0 +1,111 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/importing-synapse-sqlite.md:1 +msgid "" +"Importing an existing SQLite database from another Synapse installation " +"(optional)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:3 +msgid "" +"Run this if you'd like to import your database from a previous default " +"installation of Synapse (don't forget to import your `media_store` files " +"as well - see [the importing-synapse-media-store guide](importing-" +"synapse-media-store.md))." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:5 +msgid "" +"While this playbook only supports running Synapse in combination with " +"PostgreSQL, a Synapse instance installed manually usually defaults to " +"using an SQLite database." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:7 +msgid "" +"If you have such a Synapse setup and wish to migrate it to one managed by" +" the playbook (and over to PostgreSQL), this documentation page is for " +"you." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:11 +msgid "Before doing the actual import:" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:13 +msgid "" +"**ensure you have NOT started Synapse yet**. That is, make sure you have " +"followed the [Installing step](installing.md), but haven't run the " +"playbook's `start` tag yet. If you had started your new Synapse instance," +" it may have already initialized your Postgres database and importing " +"onto it may not work. In such cases, you may need to clean up the " +"`synapse` database first." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:14 +msgid "" +"**ensure you have uploaded your SQLite database file to the server** (any" +" path is okay)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:15 +msgid "" +"if you're using the integrated Postgres server (**by default, you are** " +"using it, unless you've explicitly switched to [Using an external " +"PostgreSQL server](configuring-playbook-external-postgres.md)), **make " +"sure Postgres is started** by running `just start-group postgres`" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:17 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:19 +msgid "" +"Run this command (make sure to replace `` " +"with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:25 +msgid "**Notes**:" +msgstr "" + +#: ../../../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:28 +msgid "" +"if the SQLite database is from an older version of Synapse, the " +"**importing procedure may run migrations on it to bring it up to date**. " +"That is, your SQLite database file may get modified and become unusable " +"with your older Synapse version. Keeping a copy of the original is " +"probably wise." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/installing.po b/i18n/locales/jp/LC_MESSAGES/docs/installing.po new file mode 100644 index 000000000..84bbd57ad --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/installing.po @@ -0,0 +1,448 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/installing.md:1 +msgid "Installing" +msgstr "" + +#: ../../../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:5 +msgid "" +"If you've configured your DNS records and the playbook, you can start the" +" installation procedure." +msgstr "" + +#: ../../../docs/installing.md:7 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/installing.md:9 +msgid "" +"Before installing, you need to update the Ansible roles that this " +"playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/installing.md:11 +msgid "" +"To update your playbook directory and all upstream Ansible roles (defined" +" in the `requirements.yml` file), run:" +msgstr "" + +#: ../../../docs/installing.md:13 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/installing.md:14 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/installing.md:16 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/installing.md:18 +msgid "" +"For details about `just` commands, take a look at: [Running `just` " +"commands](just.md)." +msgstr "" + +#: ../../../docs/installing.md:20 +msgid "Install Matrix server and services" +msgstr "" + +#: ../../../docs/installing.md:22 +msgid "" +"The Ansible playbook's tasks are tagged, so that certain parts of the " +"Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/installing.md:24 +msgid "" +"The general command syntax for installation (and also maintenance) is: " +"`ansible-playbook -i inventory/hosts setup.yml " +"--tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself " +"familiar with the [playbook tags](playbook-tags.md) before proceeding." +msgstr "" + +#: ../../../docs/installing.md:26 +msgid "" +"If you **don't** use SSH keys for authentication, but rather a regular " +"password, you may need to add `--ask-pass` to the all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:28 +msgid "" +"If you **do** use SSH keys for authentication, **and** use a non-root " +"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" +"pass`) to all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:30 +msgid "" +"There 2 ways to start the installation process - depending on whether " +"you're [Installing a brand new server (without importing " +"data)](#installing-a-brand-new-server-without-importing-data) or " +"[Installing a server into which you'll import old data](#installing-a" +"-server-into-which-youll-import-old-data)." +msgstr "" + +#: ../../../docs/installing.md:32 +msgid "" +"**Note**: if you are migrating from an old server to a new one, take a " +"look at [this guide](maintenance-migrating.md) instead. This is an easier" +" and more straightforward way than installing a server and importing old " +"data into it." +msgstr "" + +#: ../../../docs/installing.md:34 +msgid "Installing a brand new server (without importing data)" +msgstr "" + +#: ../../../docs/installing.md:36 +msgid "" +"If this is **a brand new** Matrix server and you **won't be importing old" +" data into it**, run all these tags:" +msgstr "" + +#: ../../../docs/installing.md:42 +msgid "This will do a full installation and start all Matrix services." +msgstr "" + +#: ../../../docs/installing.md:44 +msgid "" +"**Note**: if the command does not work as expected, make sure that you " +"have properly installed and configured software required to run the " +"playbook, as described on [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/installing.md:46 +msgid "Installing a server into which you'll import old data" +msgstr "" + +#: ../../../docs/installing.md:48 +msgid "" +"If you will be importing data into your newly created Matrix server, " +"install it, but **do not** start its services just yet. Starting its " +"services or messing with its database now will affect your data import " +"later on." +msgstr "" + +#: ../../../docs/installing.md:50 +msgid "" +"To do the installation **without** starting services, run `ansible-" +"playbook` with the `install-all` tag only:" +msgstr "" + +#: ../../../docs/installing.md:56 +msgid "" +"⚠️ **Warning**: do not run the just \"recipe\" `just install-all` " +"instead, because it automatically starts services at the end of " +"execution. See: [Difference between playbook tags and shortcuts](just.md" +"#difference-between-playbook-tags-and-shortcuts)" +msgstr "" + +#: ../../../docs/installing.md:58 +msgid "When this command completes, services won't be running yet." +msgstr "" + +#: ../../../docs/installing.md:60 +msgid "You can now:" +msgstr "" + +#: ../../../docs/installing.md:62 +msgid "" +"[Importing an existing SQLite database (from another Synapse installation" +")](importing-synapse-sqlite.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:64 +msgid "" +"[Importing an existing Postgres database (from another installation" +")](importing-postgres.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:66 +msgid "" +"[Importing `media_store` data files from an existing Synapse installation" +"](importing-synapse-media-store.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:68 +msgid ".. and then proceed to starting all services:" +msgstr "" + +#: ../../../docs/installing.md:74 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/installing.md:76 +msgid "" +"ℹ️ *You can skip this step if you have installed a server and imported " +"old data to it.*" +msgstr "" + +#: ../../../docs/installing.md:78 +msgid "" +"As you have configured your brand new server and the client, you need to " +"**create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/installing.md:80 +msgid "" +"After creating the user account, you can log in to it with [Element Web" +"](configuring-playbook-client-element-web.md) that this playbook has " +"installed for you at this URL: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/installing.md:82 +msgid "" +"To create your user account (as an administrator of the server) via this " +"Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/installing.md:84 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/installing.md:85 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/installing.md:86 +msgid "" +"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " +"full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/installing.md:87 +msgid "" +"Use `admin=yes` to make your user account an administrator of the Matrix " +"server" +msgstr "" + +#: ../../../docs/installing.md:95 +msgid "" +"Feel free to create as many accounts (for friends, family, etc.) as you " +"want. Still, perhaps you should grant full administrative access to your " +"account only (with `admin=yes`), and others should be created with " +"`admin=no`." +msgstr "" + +#: ../../../docs/installing.md:97 +msgid "" +"For more information, see the documentation for [registering users" +"](registering-users.md)." +msgstr "" + +#: ../../../docs/installing.md:99 +msgid "Finalize the installation" +msgstr "" + +#: ../../../docs/installing.md:101 +msgid "" +"Now you've configured Matrix services and your user account, you need to " +"**finalize the installation process** by [setting up Matrix delegation " +"(redirection)](howto-server-delegation.md), so that your Matrix server " +"(`matrix.example.com`) can present itself as the base domain " +"(`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:103 +msgid "" +"This is required for federation to work! Without a proper configuration, " +"your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:105 +msgid "" +"To configure the delegation, you have these two options. Choose one of " +"them according to your situation." +msgstr "" + +#: ../../../docs/installing.md:107 +msgid "" +"If you can afford to point the base domain at the Matrix server, follow " +"the instructions below which guide you into [serving the base domain" +"](configuring-playbook-base-domain-serving.md) from the integrated web " +"server. It will enable you to use a Matrix user ID like " +"`@alice:example.com` while hosting services on a subdomain like " +"`matrix.example.com`." +msgstr "" + +#: ../../../docs/installing.md:108 +msgid "" +"Alternatively, if you're using the base domain for other purposes and " +"cannot point it to the Matrix server (and thus cannot \"serve the base " +"domain\" from it), you most likely need to [manually install well-known " +"files on the base domain's server](configuring-well-known.md#manually-" +"installing-well-known-files-on-the-base-domains-server), but feel free to" +" familiarize yourself with all [server delegation (redirection) options" +"](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/installing.md:110 +msgid "" +"To have the base domain served from the integrated web server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/installing.md:116 +msgid "After configuring the playbook, run the command below:" +msgstr "" + +#: ../../../docs/installing.md:122 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/installing.md:124 +msgid "After finilizing the installation, you can:" +msgstr "" + +#: ../../../docs/installing.md:126 +msgid "[check if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/installing.md:127 +msgid "" +"or [set up additional services](configuring-playbook.md#other-" +"configuration-options) (bridges to other chat networks, bots, etc.)" +msgstr "" + +#: ../../../docs/installing.md:128 +msgid "" +"or learn how to [upgrade services when new versions are released" +"](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:129 +msgid "or learn how to [maintain your server](faq.md#maintenance)" +msgstr "" + +#: ../../../docs/installing.md:130 +msgid "or join some Matrix rooms:" +msgstr "" + +#: ../../../docs/installing.md:131 +msgid "" +"via the *Explore rooms* feature in Element Web or some other clients, or " +"by discovering them using this [matrix-static " +"list](https://view.matrix.org). **Note**: joining large rooms may " +"overload small servers." +msgstr "" + +#: ../../../docs/installing.md:132 +msgid "" +"or come say Hi in our support room - [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com). You might learn something or get to help someone " +"else new to Matrix hosting." +msgstr "" + +#: ../../../docs/installing.md:133 +msgid "" +"or help make this playbook better by contributing (code, documentation, " +"or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" +msgstr "" + +#: ../../../docs/installing.md:135 +msgid "Maintaining your setup in the future" +msgstr "" + +#: ../../../docs/installing.md:137 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/installing.md:139 +msgid "" +"The upstream projects, which this playbook makes use of, occasionally if " +"not often suffer from security vulnerabilities." +msgstr "" + +#: ../../../docs/installing.md:141 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/installing.md:143 +msgid "" +"For more information about upgrading or maintaining services with the " +"playbook, take at look at this page: [Upgrading the Matrix services" +"](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:145 +msgid "" +"Feel free to **re-run the setup command any time** you think something is" +" wrong with the server configuration. Ansible will take your " +"configuration and update your server to match." +msgstr "" + +#: ../../../docs/installing.md:151 +msgid "" +"**Note**: see [this page on the playbook tags](playbook-tags.md) for more" +" information about those tags." +msgstr "" + +#: ../../../docs/installing.md:153 +msgid "Make full use of `just` shortcut commands" +msgstr "" + +#: ../../../docs/installing.md:155 +msgid "" +"After you get familiar with reconfiguring and re-running the playbook to " +"maintain the server, upgrade its services, etc., you probably would like " +"to make use of `just` shortcut commands for faster input." +msgstr "" + +#: ../../../docs/installing.md:157 +msgid "" +"For example, `just install-all` is useful for maintaining your setup " +"quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-" +"in-playbook-runtime) than `just setup-all`) when its components remain " +"unchanged. If you adjust your `vars.yml` to remove other components, " +"you'd need to run `just setup-all`, or these components will still remain" +" installed." +msgstr "" + +#: ../../../docs/installing.md:159 +msgid "" +"You can learn about the shortcut commands on this page: [Running `just` " +"commands](just.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/just.po b/i18n/locales/jp/LC_MESSAGES/docs/just.po new file mode 100644 index 000000000..819ada89b --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/just.po @@ -0,0 +1,211 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/just.md:1 +msgid "Running `just` commands" +msgstr "" + +#: ../../../docs/just.md:3 +msgid "" +"We have previously used [make](https://www.gnu.org/software/make/) for " +"easily running some playbook commands (e.g. `make roles` which triggers " +"[`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-" +"galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can" +" still run these commands." +msgstr "" + +#: ../../../docs/just.md:5 +msgid "" +"In addition, we have added support for running commands via " +"[`just`](https://github.com/casey/just) - a more modern command-runner " +"alternative to `make`. It can be used to invoke `ansible-playbook` " +"commands with less typing." +msgstr "" + +#: ../../../docs/just.md:7 +msgid "" +"The `just` utility executes shortcut commands (called as \"recipes\"), " +"which invoke `ansible-playbook`, `ansible-galaxy` or " +"[`agru`](https://github.com/etkecc/agru) (depending on what is available " +"in your system). The targets of the recipes are defined in " +"[`justfile`](../justfile). Most of the just recipes have no corresponding" +" `Makefile` targets." +msgstr "" + +#: ../../../docs/just.md:9 +msgid "" +"For some recipes such as `just update`, our `justfile` recommends " +"installing [`agru`](https://github.com/etkecc/agru) (a faster alternative" +" to `ansible-galaxy`) to speed up the process." +msgstr "" + +#: ../../../docs/just.md:11 +msgid "Here are some examples of shortcuts:" +msgstr "" + +#: ../../../docs/just.md +msgid "Shortcut" +msgstr "" + +#: ../../../docs/just.md +msgid "Result" +msgstr "" + +#: ../../../docs/just.md +msgid "`just roles`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Install the necessary Ansible roles pinned in " +"[`requirements.yml`](../requirements.yml)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just update`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run `git pull` (to update the playbook) and install the Ansible roles" +msgstr "" + +#: ../../../docs/just.md ../../../docs/just.md:33 +msgid "`just install-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all" +",ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "`just setup-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all" +",ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "`just install-all --ask-vault-pass`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Run commands with additional arguments (`--ask-vault-pass` will be " +"appended to the above installation command)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just run-tags install-mautrix-slack,start`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)" +msgstr "" + +#: ../../../docs/just.md +msgid "`just install-service mautrix-slack`" +msgstr "" + +#: ../../../docs/just.md +msgid "Run `just run-tags install-mautrix-slack,start` with even less typing" +msgstr "" + +#: ../../../docs/just.md +msgid "`just start-all`" +msgstr "" + +#: ../../../docs/just.md +msgid "(Re-)starts all services" +msgstr "" + +#: ../../../docs/just.md +msgid "`just stop-group postgres`" +msgstr "" + +#: ../../../docs/just.md +msgid "Stop only the Postgres service" +msgstr "" + +#: ../../../docs/just.md +msgid "`just register-user alice secret-password yes`" +msgstr "" + +#: ../../../docs/just.md +msgid "" +"Registers an `alice` user with the `secret-password` password and admin " +"access (admin = `yes`)" +msgstr "" + +#: ../../../docs/just.md:26 +msgid "" +"While [our documentation on prerequisites](prerequisites.md) lists `just`" +" as one of the requirements for installation, using `just` is optional. " +"If you find it difficult to install it, do not find it useful, or want to" +" prefer raw `ansible-playbook` commands for some reason, feel free to run" +" all commands manually. For example, you can run `ansible-galaxy` " +"directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-" +"galaxy install -r requirements.yml -p roles/galaxy/ --force`." +msgstr "" + +#: ../../../docs/just.md:28 +msgid "Difference between playbook tags and shortcuts" +msgstr "" + +#: ../../../docs/just.md:30 +msgid "" +"It is worth noting that `just` \"recipes\" are different from [playbook " +"tags](playbook-tags.md). The recipes are shortcuts of commands defined in" +" `justfile` and can be executed by the `just` program only, while the " +"playbook tags are available for the raw `ansible-playbook` commands as " +"well. Please be careful not to confuse them." +msgstr "" + +#: ../../../docs/just.md:32 +msgid "For example, these two commands are different:" +msgstr "" + +#: ../../../docs/just.md:34 +msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" +msgstr "" + +#: ../../../docs/just.md:36 +msgid "" +"The just recipe runs `ensure-matrix-users-created` and `start` tags after" +" `install-all`, while the latter runs only `install-all` tag. The correct" +" shortcut of the latter is `just run-tags install-all`." +msgstr "" + +#: ../../../docs/just.md:38 +msgid "" +"Such kind of difference sometimes matters. For example, when you install " +"a Matrix server into which you will import old data (see " +"[here](installing.md#installing-a-server-into-which-youll-import-old-" +"data)), you are not supposed to run `just install-all` or `just setup-" +"all`, because these commands start services immediately after installing " +"components which may prevent your from importing old data." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po new file mode 100644 index 000000000..fc7585a6d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po @@ -0,0 +1,124 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-and-troubleshooting.md:1 +msgid "Maintenance and Troubleshooting" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:3 +msgid "How to see the current status of your services" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:5 +msgid "" +"You can check the status of your services by using `systemctl status`. " +"Example:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:15 +msgid "" +"Docker containers that the playbook configures are supervised by " +"[systemd](https://wiki.archlinux.org/title/Systemd) and their logs are " +"configured to go to [systemd-" +"journald](https://wiki.archlinux.org/title/Systemd/Journal)." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:17 +msgid "" +"To prevent double-logging, Docker logging is disabled by explicitly " +"passing `--log-driver=none` to all containers. Due to this, you " +"**cannot** view logs using `docker logs`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:19 +msgid "" +"To view systemd-journald logs using " +"[journalctl](https://man.archlinux.org/man/journalctl.1), run a command " +"like this:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:25 +msgid "Increasing Synapse logging" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:27 +msgid "" +"Because the [Synapse](https://github.com/element-hq/synapse) Matrix " +"server is originally very chatty when it comes to logging, we " +"intentionally reduce its [logging " +"level](https://docs.python.org/3/library/logging.html#logging-levels) " +"from `INFO` to `WARNING`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:29 +msgid "" +"If you'd like to debug an issue or [report a Synapse " +"bug](https://github.com/element-hq/synapse/issues/new/choose) to the " +"developers, it'd be better if you temporarily increasing the logging " +"level to `INFO`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:31 +msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:39 +msgid "Re-run the playbook after making these configuration changes." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:41 +msgid "Remove unused Docker data" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:43 +msgid "" +"You can free some disk space from Docker, see [docker system " +"prune](https://docs.docker.com/engine/reference/commandline/system_prune/)" +" for more information." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:49 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags run-docker-prune`" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:51 +msgid "Postgres" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:53 +msgid "" +"See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) " +"documentation page." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:55 +msgid "Ma1sd" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:57 +msgid "" +"See the dedicated [Adjusting ma1sd Identity Server configuration" +"](configuring-playbook-ma1sd.md) documentation page." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po new file mode 100644 index 000000000..c27fdaf82 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po @@ -0,0 +1,54 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/maintenance-checking-services.md:1 +msgid "Checking if services work" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:3 +msgid "" +"This playbook can perform a check to ensure that you've configured things" +" correctly and that services are running." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:5 +msgid "To perform the check, run:" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:11 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags self-check`" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:13 +msgid "If it's all green, everything is probably running correctly." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:15 +msgid "" +"Besides this self-check, you can also check whether your server federates" +" with the Matrix network by using the [Federation " +"Tester](https://federationtester.matrix.org/) against your base domain " +"(`example.com`), not the `matrix.example.com` subdomain." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po new file mode 100644 index 000000000..81d3506bd --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po @@ -0,0 +1,195 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/maintenance-migrating.md:1 +msgid "Migrating to new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:3 +msgid "" +"This documentation explains how to migrate your Matrix services (server, " +"client, bridges, etc.) and data **from an old server to a new server**." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:6 +msgid "" +"This migration guide is applicable if you migrate from one server to " +"another server having the same CPU architecture (e.g. both servers being " +"`amd64`)." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:8 +msgid "" +"If you're trying to migrate between different architectures (e.g. `amd64`" +" --> `arm64`), simply copying the complete `/matrix` directory is **not**" +" possible as it would move the raw PostgreSQL data " +"(`/matrix/postgres/data`) between different architectures. In this " +"specific case, you can use the guide below as a reference, but you would " +"also need to avoid syncing `/matrix/postgres/data` to the new host, and " +"also dump the database on your current server and import it properly on " +"the new server. See our [Backing up PostgreSQL](maintenance-postgres.md" +"#backing-up-postgresql) docs for help with PostgreSQL backup/restore." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:9 +msgid "" +"If you have any questions about migration or encountered an issue during " +"migration, do not hesitate to ask for help on [our Matrix " +"room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). " +"You probably might want to prepare a temporary/sub account on another " +"Matrix server in case it becomes impossible to use your server due to " +"migration failure by any chance." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:11 +msgid "" +"You can't change the domain (specified in the `matrix_domain` variable) " +"after the initial deployment." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:13 +msgid "Lower DNS TTL" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:15 +msgid "" +"Prepare by lowering DNS TTL for your domains (`matrix.example.com`, " +"etc.), so that DNS record changes would happen faster, leading to less " +"downtime." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:17 +msgid "Stop services on the old server completely" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:19 +msgid "" +"Before migrating, you need to stop all services on the old server and " +"make sure they won't be starting again." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:21 +msgid "" +"To do so, it is recommended to run the `systemctl` command on the server." +" Running the playbook's `stop` tag also stops the services, but just " +"once; they will start again if you reboot the server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:23 +msgid "" +"Log in to the old server and run the command as `root` (or a user that " +"can run it with `sudo`):" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:29 +msgid "Copy data directory to the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:31 +msgid "" +"After you've confirmed that all services were stopped, copy the `/matrix`" +" directory from the old server to the new server. When copying, make sure" +" to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:33 +msgid "Adjust DNS records" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:35 +msgid "" +"Make sure your DNS records are adjusted to point to the new server's IP " +"address." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:37 +msgid "Update `inventory/hosts` file" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:39 +msgid "" +"Having adjusted DNS records, replace the old server's external IP address" +" on the `inventory/hosts` file with that of the new server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:41 +msgid "Create `matrix` user and group on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:43 +msgid "" +"Then, run the command below on your local computer to create the `matrix`" +" user and group on the new server:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:49 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags setup-system-user`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:51 +msgid "" +"**Note**: because the `matrix` user and group are created dynamically on " +"each server, the user/group ID may differ between the old and new server." +" We suggest that you adjust ownership of `/matrix` files. To adjust the " +"ownership, log in to the new server and run the command:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:57 +msgid "Install and start all services on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:59 +msgid "" +"Finally, run the command below on your local computer to finish the " +"installation and start all services:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:65 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags install-all,start`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:67 +msgid "Check if services work" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:69 +msgid "" +"After starting the services, you probably might want to ensure that " +"you've migrated things correctly and that services are running. For " +"instructions, see: [check if services work](maintenance-checking-" +"services.md)" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:71 +msgid "" +"Having make sure that both services and federation work as expected, you " +"can safely shutdown the old server." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po new file mode 100644 index 000000000..9bf3037a2 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po @@ -0,0 +1,335 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-postgres.md:1 +msgid "PostgreSQL maintenance" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:3 +msgid "" +"This document shows you how to perform various maintenance tasks related " +"to the Postgres database server used by Matrix." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:7 +msgid "" +"[Getting a database terminal](#getting-a-database-terminal), for when you" +" wish to execute SQL queries" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:9 +msgid "" +"[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a" +" Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-" +"vacuum.html) (optimizing disk space)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:11 +msgid "" +"[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to " +"make a backup" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:13 +msgid "" +"[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major" +" versions of PostgreSQL. Such **manual upgrades are sometimes required**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:15 +msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:17 +msgid "Getting a database terminal" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:19 +msgid "" +"You can use the `/matrix/postgres/bin/cli` tool to get interactive " +"terminal access ([psql](https://www.postgresql.org/docs/11/app-" +"psql.html)) to the PostgreSQL server." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:21 +msgid "" +"If you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), the above tool will not be available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:23 +msgid "" +"By default, this tool puts you in the `matrix` database, which contains " +"nothing." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:25 +msgid "To see the available databases, run `\\list` (or just `\\l`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:27 +msgid "" +"To change to another database (for example `synapse`), run `\\connect " +"synapse` (or just `\\c synapse`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:29 +msgid "" +"You can then proceed to write queries. Example: `SELECT COUNT(*) FROM " +"users;`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:31 +msgid "" +"**Be careful**. Modifying the database directly (especially as services " +"are running) is dangerous and may lead to irreversible database " +"corruption. When in doubt, consider [making a backup](#backing-up-" +"postgresql)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:33 +msgid "Vacuuming PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:35 +msgid "" +"Deleting lots data from Postgres does not make it release disk space, " +"until you perform a [`VACUUM` " +"operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:37 +msgid "" +"You can run different `VACUUM` operations via the playbook, with the " +"default preset being `vacuum-complete`:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:39 +msgid "" +"(default) `vacuum-complete`: stops all services temporarily and runs " +"`VACUUM FULL VERBOSE ANALYZE`." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:40 +msgid "" +"`vacuum-full`: stops all services temporarily and runs `VACUUM FULL " +"VERBOSE`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:41 +msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:42 +msgid "" +"`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any " +"services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:43 +msgid "" +"`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is " +"just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) " +"without doing a vacuum, so it's faster)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:45 +msgid "" +"**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll " +"need plenty of available disk space in your Postgres data directory " +"(usually `/matrix/postgres/data`). These presets also stop all services " +"(e.g. Synapse, etc.) while the vacuum operation is running." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:47 +msgid "Example playbook invocations:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:49 +msgid "" +"`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` " +"preset and restarts all services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:50 +msgid "" +"`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: " +"runs the `analyze` preset with all services remaining operational at all " +"times" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:52 +msgid "Backing up PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:54 +msgid "" +"To automatically make Postgres database backups on a fixed schedule, see " +"[Setting up postgres backup](configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:56 +msgid "" +"To make a one off back up of the current PostgreSQL database, make sure " +"it's running and then execute a command like this on the server:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:67 +msgid "" +"If you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), the above command will not work, because neither " +"the credentials file (`/matrix/postgres/env-postgres-psql`), nor the " +"`matrix-postgres` container is available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:69 +msgid "" +"Restoring a backup made this way can be done by [importing it](importing-" +"postgres.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:71 +msgid "Upgrading PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:73 +msgid "" +"Unless you are using an [external Postgres server](configuring-playbook-" +"external-postgres.md), this playbook initially installs Postgres for you." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:75 +msgid "" +"Once installed, the playbook attempts to preserve the Postgres version it" +" starts with. This is because newer Postgres versions cannot start with " +"data generated by older Postgres versions." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:77 +msgid "Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:79 +msgid "" +"This playbook can upgrade your existing Postgres setup with the following" +" command:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:85 +msgid "" +"**The old Postgres data directory is backed up** automatically, by " +"renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to " +"a different path, pass some extra flags to the command above, like this: " +"`--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk" +"/matrix-postgres-before-upgrade\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:87 +msgid "" +"The auto-upgrade-backup directory stays around forever, until you " +"**manually decide to delete it**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:89 +msgid "" +"As part of the upgrade, the database is dumped to `/tmp`, an upgraded and" +" empty Postgres server is started, and then the dump is restored into the" +" new server. To use a different directory for the dump, pass some extra " +"flags to the command above, like this: `--extra-" +"vars=\"postgres_dump_dir=/directory/to/dump/here\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:91 +msgid "" +"To save disk space in `/tmp`, the dump file is gzipped on the fly at the " +"expense of CPU usage. If you have plenty of space in `/tmp` and would " +"rather avoid gzipping, you can explicitly pass a dump filename which " +"doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-" +"postgres-dump.sql\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:93 +msgid "**All databases, roles, etc. on the Postgres server are migrated**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:95 +msgid "Tuning PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:97 +msgid "" +"PostgreSQL can be " +"[tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) " +"to make it run faster. This is done by passing extra arguments to the " +"Postgres process." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:99 +msgid "" +"The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting" +"/ansible-role-postgres) **already does some tuning by default**, which " +"matches the [tuning " +"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" +" done by websites like https://pgtune.leopard.in.ua/. You can manually " +"influence some of the tuning variables. These parameters (variables) are " +"injected via the `postgres_postgres_process_extra_arguments_auto` " +"variable." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:101 +msgid "" +"Most users should be fine with the automatically-done tuning. However, " +"you may wish to:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:103 +msgid "" +"**adjust the automatically-determined tuning parameters manually**: " +"change the values for the tuning variables defined in the Postgres role's" +" [default configuration file](https://github.com/mother-of-all-self-" +"hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see " +"`postgres_max_connections`, `postgres_data_storage` etc). These variables" +" are ultimately passed to Postgres via a " +"`postgres_postgres_process_extra_arguments_auto` variable" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:105 +msgid "" +"**turn automatically-performed tuning off**: override it like this: " +"`postgres_postgres_process_extra_arguments_auto: []`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:107 +msgid "" +"**add additional tuning parameters**: define your additional Postgres " +"configuration parameters in " +"`postgres_postgres_process_extra_arguments_custom`. See " +"`postgres_postgres_process_extra_arguments_auto` defined in the Postgres " +"role's [default configuration file](https://github.com/mother-of-all-" +"self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for " +"inspiration" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po new file mode 100644 index 000000000..b121bf1a8 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po @@ -0,0 +1,309 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/maintenance-synapse.md:1 +msgid "Synapse maintenance" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:3 +msgid "" +"This document shows you how to perform various maintenance tasks related " +"to the Synapse chat server." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:7 +msgid "" +"[Purging old data with the Purge History API](#purging-old-data-with-the-" +"purge-history-api), for when you wish to delete in-use (but old) data " +"from the Synapse database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:9 +msgid "" +"[Compressing state with rust-synapse-compress-state](#compressing-state-" +"with-rust-synapse-compress-state)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:11 +msgid "" +"[Browse and manipulate the database](#browse-and-manipulate-the-" +"database), for when you really need to take matters into your own hands" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:13 +msgid "[Make Synapse faster](#make-synapse-faster)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:15 +msgid "Purging old data with the Purge History API" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:17 +msgid "" +"You can use the **[Purge History API](https://github.com/element-" +"hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete " +"old messages on a per-room basis. **This is destructive** (especially for" +" non-federated rooms), because it means **people will no longer have " +"access to history past a certain point**." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:19 +msgid "" +"To make use of this Synapse Admin API, **you'll need an admin access " +"token** first. Refer to the documentation on [how to obtain an access " +"token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:21 +msgid "" +"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:23 +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:25 +msgid "" +"After deleting data, you may wish to run a [`FULL` Postgres `VACUUM" +"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:27 +msgid "Compressing state with rust-synapse-compress-state" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:29 +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:31 +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:33 +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:35 +msgid "To ask the playbook to run rust-synapse-compress-state, execute:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:41 +msgid "" +"The shortcut command with `just` program is also available: `just run-" +"tags rust-synapse-compress-state`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:43 +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:45 +msgid "" +"After state compression, you may wish to run a [`FULL` Postgres `VACUUM" +"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:47 +msgid "Browse and manipulate the database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:49 +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:51 +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:53 +msgid "" +"First, set up an SSH tunnel to your Matrix server (skip if it is your " +"local machine):" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:60 +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:66 +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:68 +msgid "" +"⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB " +"operations." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:70 +msgid "Make Synapse faster" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:72 +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:74 +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:76 +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:78 +msgid "Tuning caches and cache autotuning" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:80 +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:82 +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:84 +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:86 +msgid "" +"Cache autotuning is **enabled by default** and controlled via the " +"following variables:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:88 +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:89 +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:90 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:92 +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:94 +msgid "To **disable cache auto-tuning**, unset all values:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:102 +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:104 +msgid "" +"See also [How do I optimize this setup for a low-power server?](faq.md" +"#how-do-i-optimize-this-setup-for-a-low-power-server)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po new file mode 100644 index 000000000..0e5d6d184 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po @@ -0,0 +1,185 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/maintenance-upgrading-services.md:1 +msgid "Upgrading the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:3 +msgid "" +"This playbook not only installs the various Matrix services for you, but " +"can also upgrade them as new versions are made available." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:5 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:7 +msgid "" +"The upstream projects, which this playbook makes use of, occasionally if " +"not often suffer from security vulnerabilities (for example, see " +"[here](https://github.com/element-hq/element-web/security) for known ones" +" on Element Web)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:9 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:11 +msgid "" +"The developers of this playbook strive to maintain the playbook updated, " +"so that you can re-run the playbook to address such vulnerabilities. It " +"is **your responsibility** to keep your server and the services on it up-" +"to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:13 +msgid "" +"If you want to be notified when new versions of Synapse are released, you" +" should join the Synapse Homeowners room: " +"[#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:15 +msgid "Steps to upgrade the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:17 +msgid "Check the changelog" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:19 +msgid "" +"Before updating the playbook and the Ansible roles in the playbook, take " +"a look at [the changelog](../CHANGELOG.md) to see if there have been any " +"backward-incompatible changes that you need to take care of." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:21 +msgid "Update the playbook and the Ansible roles" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:23 +msgid "" +"If it looks good to you, go to the `matrix-docker-ansible-deploy` " +"directory, update your playbook directory and all upstream Ansible roles " +"(defined in the `requirements.yml` file) by running:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:25 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:26 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:28 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:30 +msgid "" +"**Note**: for details about `just` commands, take a look at: [Running " +"`just` commands](just.md)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:32 +msgid "Re-run the playbook setup" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:34 +msgid "" +"After updating the Ansible roles, then re-run the [playbook " +"setup](installing.md#maintaining-your-setup-in-the-future) and restart " +"all services:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:40 +msgid "" +"If you remove components from `vars.yml`, or if we switch some component " +"from being installed by default to not being installed by default " +"anymore, you'd need to run the setup command with the `setup-all` tag as " +"below:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:48 +msgid "" +"The `ensure-matrix-users-created` playbook tag makes the playbook " +"automatically create the bot's user account, if any." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:50 +msgid "" +"Our estimation is that running `--tags=install-all,start` is " +"approximately from **2 to 5 times faster** than running `setup-all" +",ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-" +"5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for " +"more information." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:52 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`. Note these shortcuts " +"run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:54 +msgid "" +"See [this page on the playbook tags](playbook-tags.md) for more " +"information about those tags." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:56 +msgid "PostgreSQL major version upgrade" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:58 +msgid "" +"Major version upgrades to the internal PostgreSQL database are not done " +"automatically. Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:60 +msgid "" +"For details about upgrading it, refer to the [upgrading PostgreSQL guide" +"](maintenance-postgres.md#upgrading-postgresql)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po new file mode 100644 index 000000000..463793e6a --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -0,0 +1,121 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/obtaining-access-tokens.md:1 +msgid "Obtaining an Access Token" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:3 +msgid "" +"When setting up some optional features like bots and bridges you will " +"need to provide an access token for some user. This document provides " +"documentation on how to obtain such an access token." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:5 +msgid "" +"**Access tokens are sensitive information. Do not include them in any bug" +" reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:9 +msgid "" +"The user for whom you want to obtain an access token needs to already " +"exist. You can use this playbook to [register a new user](registering-" +"users.md), if you have not already." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:11 +msgid "" +"Below, we describe 2 ways to generate an access token for a user - using " +"[Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-" +"an-access-token-via-curl). For both ways you need the user's password." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:13 +msgid "Obtain an access token via Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:15 +msgid "In a private browsing session (incognito window), open Element Web." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:16 +msgid "Log in with the user's credentials." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:17 +msgid "" +"In the settings page, choose \"Help & About\", scroll down to the bottom " +"and expand the `Access Token` section (see screenshot below)." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:18 +msgid "Copy the access token to your configuration." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:19 +msgid "" +"Close the private browsing session. **Do not log out**. Logging out will " +"invalidate the token, making it not work." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "" +"![Obtaining an access token with Element " +"Web](assets/obtain_admin_access_token_element_web.png)" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "Obtaining an access token with Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:23 +msgid "Obtain an access token via curl" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:25 +msgid "" +"You can use the following command to get an access token for your user " +"directly from the [Matrix Client-Server " +"API](https://www.matrix.org/docs/guides/client-server-api#login):" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:35 +msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:37 +msgid "" +"`YOURDEVICEID` is optional and can be used to more easily identify the " +"session later. When omitted (mind the commas in the JSON payload if " +"you'll be omitting it), a random device ID will be generated." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:39 +msgid "Your response will look like this (prettified):" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po new file mode 100644 index 000000000..54ba6d469 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po @@ -0,0 +1,112 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/playbook-tags.md:1 +msgid "Playbook tags" +msgstr "" + +#: ../../../docs/playbook-tags.md:3 +msgid "" +"The Ansible playbook's tasks are tagged, so that certain parts of the " +"Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/playbook-tags.md:5 +msgid "" +"The general command syntax is: `ansible-playbook -i inventory/hosts " +"setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" +msgstr "" + +#: ../../../docs/playbook-tags.md:7 +msgid "Here are some playbook tags that you should be familiar with:" +msgstr "" + +#: ../../../docs/playbook-tags.md:9 +msgid "" +"`setup-all` - runs all setup tasks (installation and uninstallation) for " +"all components, but does not start/restart services" +msgstr "" + +#: ../../../docs/playbook-tags.md:11 +msgid "" +"`install-all` - like `setup-all`, but skips uninstallation tasks. Useful " +"for maintaining your setup quickly when its components remain unchanged. " +"If you adjust your `vars.yml` to remove components, you'd need to run " +"`setup-all` though, or these components will still remain installed" +msgstr "" + +#: ../../../docs/playbook-tags.md:13 +msgid "" +"`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for" +" a given role, but does not start/restart services. You can discover " +"these additional tags in each role (`roles/**/tasks/main.yml`). Running " +"per-component setup tasks is **not recommended**, as components sometimes" +" depend on each other and running just the setup tasks for a given " +"component may not be enough. For example, setting up the [mautrix-" +"telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in " +"addition to the `setup-mautrix-telegram` tag, requires database changes " +"(the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-" +"nginx-proxy` tag)." +msgstr "" + +#: ../../../docs/playbook-tags.md:15 +msgid "" +"`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but" +" skips uninstallation tasks. See `install-all` above for additional " +"information." +msgstr "" + +#: ../../../docs/playbook-tags.md:17 +msgid "" +"`start` - starts all systemd services and makes them start automatically " +"in the future" +msgstr "" + +#: ../../../docs/playbook-tags.md:19 +msgid "`stop` - stops all systemd services" +msgstr "" + +#: ../../../docs/playbook-tags.md:21 +msgid "" +"`ensure-matrix-users-created` - a special tag which ensures that all " +"special users needed by the playbook (for bots, etc.) are created" +msgstr "" + +#: ../../../docs/playbook-tags.md:23 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/playbook-tags.md:24 +msgid "" +"`setup-*` tags and `install-*` tags **do not start services** " +"automatically, because you may wish to do things before starting " +"services, such as importing a database dump, restoring data from another " +"server, etc." +msgstr "" + +#: ../../../docs/playbook-tags.md:25 +msgid "" +"Please be careful not to confuse the playbook tags with the `just` " +"shortcut commands (\"recipes\"). For details about `just` commands, see: " +"[Running `just` commands](just.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po new file mode 100644 index 000000000..d7b541d33 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po @@ -0,0 +1,259 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/prerequisites.md:1 +msgid "Prerequisites" +msgstr "" + +#: ../../../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:5 +msgid "" +"To install Matrix services using this Ansible playbook, you need to " +"prepare several requirements both on your local computer (where you will " +"run the playbook to configure the server) and the server (where the " +"playbook will install the Matrix services for you). **These requirements " +"need to be set up manually** before proceeding to the next step." +msgstr "" + +#: ../../../docs/prerequisites.md:7 +msgid "" +"We will be using `example.com` as the domain in the following " +"instruction. Please remember to replace it with your own domain before " +"running any commands." +msgstr "" + +#: ../../../docs/prerequisites.md:9 +msgid "" +"**Note**: if you do not have an existing Matrix server and want to start " +"quickly with \"opinionated defaults\", we suggest you to follow ⚡ " +"**[Quick start](quick-start.md)** installation guide." +msgstr "" + +#: ../../../docs/prerequisites.md:11 +msgid "Your local computer" +msgstr "" + +#: ../../../docs/prerequisites.md:13 +msgid "" +"[Ansible](http://ansible.com/) program. It's used to run this playbook " +"and configures your server for you. Take a look at [our guide about " +"Ansible](ansible.md) for more information, as well as [version " +"requirements](ansible.md#supported-ansible-versions) and alternative ways" +" to run Ansible." +msgstr "" + +#: ../../../docs/prerequisites.md:15 +msgid "" +"[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python " +"library. See [this official " +"documentation](https://passlib.readthedocs.io/en/stable/install.html" +"#installation-instructions) for an instruction to install it. On most " +"distros, you need to install some `python-passlib` or `py3-passlib` " +"package, etc." +msgstr "" + +#: ../../../docs/prerequisites.md:17 +msgid "" +"[`git`](https://git-scm.com/) as the recommended way to download the " +"playbook. `git` may also be required on the server if you will be [self-" +"building](self-building.md) components." +msgstr "" + +#: ../../../docs/prerequisites.md:19 +msgid "" +"[`just`](https://github.com/casey/just) for running `just roles`, `just " +"update`, etc. (see [`justfile`](../justfile)), although you can also run " +"these commands manually. Take at look at this documentation for more " +"information: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:21 +msgid "" +"Strong password (random strings) generator. The playbook often requires " +"you to create a strong password and use it for settings on `vars.yml`, " +"components, etc. As any tools should be fine, this playbook has adopted " +"[`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). " +"[Password Tech](https://pwgen-win.sourceforge.io/), formerly known as " +"\"PWGen for Windows\", is available as free and open source password " +"generator for Windows. Generally, using a random generator available on " +"the internet is not recommended." +msgstr "" + +#: ../../../docs/prerequisites.md:23 +msgid "Server" +msgstr "" + +#: ../../../docs/prerequisites.md:25 +msgid "" +"(Recommended) An **x86** server ([What kind of server specs do I " +"need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these " +"operating systems that make use of [systemd](https://systemd.io/):" +msgstr "" + +#: ../../../docs/prerequisites.md:26 +msgid "**Archlinux**" +msgstr "" + +#: ../../../docs/prerequisites.md:27 +msgid "" +"**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL " +"alternatives (although your mileage may vary)" +msgstr "" + +#: ../../../docs/prerequisites.md:28 +msgid "**Debian** (10/Buster or newer)" +msgstr "" + +#: ../../../docs/prerequisites.md:29 +msgid "" +"**Ubuntu** (18.04 or newer, although [20.04 may be " +"problematic](ansible.md#supported-ansible-versions) if you run the " +"Ansible playbook on it)" +msgstr "" + +#: ../../../docs/prerequisites.md:31 +msgid "" +"Generally, newer is better. We only strive to support released stable " +"versions of distributions, not betas or pre-releases. This playbook can " +"take over your whole server or co-exist with other services that you have" +" there." +msgstr "" + +#: ../../../docs/prerequisites.md:33 +msgid "" +"This playbook somewhat supports running on non-`amd64` architectures like" +" ARM. See [Alternative Architectures](alternative-architectures.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:35 +msgid "" +"If your distro runs within an [LXC " +"container](https://linuxcontainers.org/), you may hit [this " +"issue](https://github.com/spantaleev/matrix-docker-ansible-" +"deploy/issues/703). It can be worked around, if absolutely necessary, but" +" we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/prerequisites.md:37 +msgid "" +"`root` access to your server (or a user capable of elevating to `root` " +"via `sudo`)." +msgstr "" + +#: ../../../docs/prerequisites.md:39 +msgid "" +"[Python](https://www.python.org/). Most distributions install Python by " +"default, but some don't (e.g. Ubuntu 18.04) and require manual " +"installation (something like `apt-get install python3`). On some distros," +" Ansible may incorrectly [detect the Python " +"version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html)" +" (2 vs 3) and you may need to explicitly specify the interpreter path in " +"`inventory/hosts` during installation (e.g. " +"`ansible_python_interpreter=/usr/bin/python3`)" +msgstr "" + +#: ../../../docs/prerequisites.md:41 +msgid "" +"[sudo](https://www.sudo.ws/), even when you've configured Ansible to log " +"in as `root`. Some distributions, like a minimal Debian net install, do " +"not include the `sudo` package by default." +msgstr "" + +#: ../../../docs/prerequisites.md:43 +msgid "" +"An HTTPS-capable web server at the base domain name (`example.com`) which" +" is capable of serving static files. Unless you decide to [Serve the base" +" domain from the Matrix server](configuring-playbook-base-domain-" +"serving.md) or alternatively, to use DNS SRV records for [Server " +"Delegation](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:45 +msgid "" +"Properly configured DNS records for `example.com` (details in " +"[Configuring DNS](configuring-dns.md))." +msgstr "" + +#: ../../../docs/prerequisites.md:47 +msgid "" +"Some TCP/UDP ports open. This playbook (actually [Docker " +"itself](https://docs.docker.com/network/iptables/)) configures the " +"server's internal firewall for you. In most cases, you don't need to do " +"anything special. But **if your server is running behind another " +"firewall**, you'd need to open these ports:" +msgstr "" + +#: ../../../docs/prerequisites.md:49 +msgid "`80/tcp`: HTTP webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:50 +msgid "`443/tcp` and `443/udp`: HTTPS webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:51 +msgid "`3478/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:52 +msgid "`3478/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:53 +msgid "`5349/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:54 +msgid "`5349/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:55 +msgid "" +"`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some" +" cases, this **may necessary even with federation disabled**. Integration" +" Servers (like Dimension) and Identity Servers (like ma1sd) may need to " +"access `openid` APIs on the federation port." +msgstr "" + +#: ../../../docs/prerequisites.md:56 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:57 +msgid "" +"potentially some other ports, depending on the additional (non-default) " +"services that you enable in the **configuring the playbook** step (later " +"on). Consult each service's documentation page in `docs/` for that." +msgstr "" + +#: ../../../docs/prerequisites.md:61 +msgid "" +"[▶️](configuring-dns.md) When ready to proceed, continue with " +"[Configuring DNS](configuring-dns.md)." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po new file mode 100644 index 000000000..dd3207b8d --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po @@ -0,0 +1,614 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/quick-start.md:1 +msgid "Quick start" +msgstr "" + +#: ../../../docs/quick-start.md:9 +msgid "" +"This page explains how to use this Ansible playbook to install Matrix " +"services on your server with a minimal set of core services." +msgstr "" + +#: ../../../docs/quick-start.md:11 +msgid "" +"We will be using `example.com` as the \"base domain\" in the following " +"instruction." +msgstr "" + +#: ../../../docs/quick-start.md:13 +msgid "By following the instruction on this page, you will set up:" +msgstr "" + +#: ../../../docs/quick-start.md:15 +msgid "" +"**your own Matrix server** on a `matrix.example.com` server, which is " +"configured to present itself as `example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:16 +msgid "**your user account** like `@alice:example.com` on the server" +msgstr "" + +#: ../../../docs/quick-start.md:17 +msgid "" +"a **self-hosted Matrix client**, [Element Web](configuring-playbook-" +"client-element-web.md) with the default subdomain at " +"`element.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:18 +msgid "" +"Matrix delegation, so that your `matrix.example.com` server (presenting " +"itself as `example.com`) can join the Matrix Federation and communicate " +"with any other server in the Matrix network" +msgstr "" + +#: ../../../docs/quick-start.md:20 +msgid "" +"Please remember to replace `example.com` with your own domain before " +"running any commands." +msgstr "" + +#: ../../../docs/quick-start.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/quick-start.md:24 +msgid "" +"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:26 +msgid "" +"At first, **check prerequisites** and prepare for installation by setting" +" up programs [on your own computer](prerequisites.md#your-local-computer)" +" and [your server](prerequisites.md#server). You also need `root` access " +"on your server (a user that could elevate to `root` via `sudo` also " +"works)." +msgstr "" + +#: ../../../docs/quick-start.md:28 +msgid "" +"When preparing your server, make sure to check [the server specs you " +"need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting " +"with a server having at least 2GB of memory." +msgstr "" + +#: ../../../docs/quick-start.md:34 +msgid "" +"If you encounter an error during installation, please make sure that you " +"have installed and configured programs correctly." +msgstr "" + +#: ../../../docs/quick-start.md:36 +msgid "" +"One of the main reasons of basic errors is using an incompatible version " +"of required software such as Ansible. Take a look at [our guide about " +"Ansible](ansible.md) for more information. In short: installing the " +"latest available version is recommended." +msgstr "" + +#: ../../../docs/quick-start.md:38 +msgid "Configure your DNS settings" +msgstr "" + +#: ../../../docs/quick-start.md:40 +msgid "" +"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:42 +msgid "" +"After installing and configuring prerequisites, you will need to " +"**configure DNS records**." +msgstr "" + +#: ../../../docs/quick-start.md:44 +msgid "" +"To configure Matrix services in the default settings, go to your DNS " +"service provider, and adjust DNS records as below." +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Type" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Host" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Priority" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Weight" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Port" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "Target" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "A" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "-" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "CNAME" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`element`" +msgstr "" + +#: ../../../docs/quick-start.md +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:51 +msgid "" +"As the table illustrates, you need to create 2 subdomains " +"(`matrix.example.com` and `element.example.com`) and point both of them " +"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/quick-start.md:53 +msgid "It might take some time for the DNS records to propagate after creation." +msgstr "" + +#: ../../../docs/quick-start.md:55 +msgid "" +"**💡 Note**: if you are using Cloudflare DNS, make sure to disable the " +"proxy and set all records to \"DNS only\"" +msgstr "" + +#: ../../../docs/quick-start.md:57 +msgid "Get the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:59 +msgid "" +"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:61 +msgid "Next, let's **get the playbook's source code**." +msgstr "" + +#: ../../../docs/quick-start.md:63 +msgid "" +"We recommend to do so with [git](https://git-scm.com/) as it enables you " +"to keep it up to date with the latest source code. While it is possible " +"to download the playbook as a ZIP archive, it is not recommended." +msgstr "" + +#: ../../../docs/quick-start.md:65 +msgid "" +"To get the playbook with git, install git on your computer, go to a " +"directory, and run the command:" +msgstr "" + +#: ../../../docs/quick-start.md:71 +msgid "" +"It will fetch the playbook to a new `matrix-docker-ansible-deploy` " +"directory underneath the directory you are currently in." +msgstr "" + +#: ../../../docs/quick-start.md:73 +msgid "Configure the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:75 +msgid "" +"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:77 +msgid "" +"Now that the playbook was fetched, it is time to **configure** it per " +"your needs." +msgstr "" + +#: ../../../docs/quick-start.md:79 +msgid "" +"To install Matrix services with this playbook, you would at least need 2 " +"configuration files." +msgstr "" + +#: ../../../docs/quick-start.md:81 +msgid "" +"For your convenience, we have prepared example files of them " +"([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." +msgstr "" + +#: ../../../docs/quick-start.md:83 +msgid "" +"To start quickly based on these example files, go into the `matrix-" +"docker-ansible-deploy` directory and follow the instructions below:" +msgstr "" + +#: ../../../docs/quick-start.md:85 +msgid "" +"Create a directory to hold your configuration: `mkdir -p " +"inventory/host_vars/matrix.example.com` where `example.com` is your " +"\"base domain\"" +msgstr "" + +#: ../../../docs/quick-start.md:86 +msgid "" +"Copy the sample configuration file: `cp examples/vars.yml " +"inventory/host_vars/matrix.example.com/vars.yml`" +msgstr "" + +#: ../../../docs/quick-start.md:87 +msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`" +msgstr "" + +#: ../../../docs/quick-start.md:88 +msgid "" +"Edit the configuration file " +"(`inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/quick-start.md:89 +msgid "Edit the inventory hosts file (`inventory/hosts`)" +msgstr "" + +#: ../../../docs/quick-start.md:91 +msgid "" +"Before editing these 2 files, make sure to read explanations on them to " +"understand what needs to be configured." +msgstr "" + +#: ../../../docs/quick-start.md:93 +msgid "**💡 Notes:**" +msgstr "" + +#: ../../../docs/quick-start.md:94 +msgid "" +"If you are not in control of anything on the base domain, you would need " +"to set additional configuration on `vars.yml`. For more information, see " +"[How do I install on matrix.example.com without involving the base " +"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" +"the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/quick-start.md:95 +msgid "" +"Certain configuration decisions (like the base domain configured in " +"`matrix_domain` and homeserver implementation configured in " +"`matrix_homeserver_implementation`) are final. If you make the wrong " +"choice and wish to change it, you'll have to run the Uninstalling step " +"and start over." +msgstr "" + +#: ../../../docs/quick-start.md:96 +msgid "" +"Instead of configuring a lot of things all at once, we recommend starting" +" with the basic (default) settings in order to get yourself familiar with" +" how the playbook works. After making sure that everything works as " +"expected, you can add (and remove) advanced settings / features and run " +"the playbook as many times as you wish." +msgstr "" + +#: ../../../docs/quick-start.md:98 +msgid "Install" +msgstr "" + +#: ../../../docs/quick-start.md:100 +msgid "" +"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:102 +msgid "" +"After editing `vars.yml` and `hosts` files, let's start the " +"**installation** procedure." +msgstr "" + +#: ../../../docs/quick-start.md:104 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/quick-start.md:106 +msgid "" +"Before installing, you need to update the Ansible roles that this " +"playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/quick-start.md:108 +msgid "To update your playbook directory and all upstream Ansible roles, run:" +msgstr "" + +#: ../../../docs/quick-start.md:110 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/quick-start.md:111 +msgid "" +"or: a combination of `git pull` and `just roles` (or `make roles` if you " +"have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/quick-start.md:113 +msgid "" +"If you don't have either `just` tool or `make` program, you can run the " +"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " +"install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/quick-start.md:115 +msgid "Run installation command" +msgstr "" + +#: ../../../docs/quick-start.md:117 +msgid "Then, run the command below to start installation:" +msgstr "" + +#: ../../../docs/quick-start.md:123 +msgid "" +"If you **don't** use SSH keys for authentication, but rather a regular " +"password, you may need to add `--ask-pass` to the command." +msgstr "" + +#: ../../../docs/quick-start.md:125 +msgid "" +"If you **do** use SSH keys for authentication, **and** use a non-root " +"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" +"pass`) to the command." +msgstr "" + +#: ../../../docs/quick-start.md:127 +msgid "" +"Wait until the command completes. If it's all green, everything should be" +" running properly." +msgstr "" + +#: ../../../docs/quick-start.md:129 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/quick-start.md:131 +msgid "" +"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:133 +msgid "" +"As you have configured your brand new server and the client, you need to " +"**create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/quick-start.md:135 +msgid "" +"To create your user account (as an administrator of the server) via this " +"Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/quick-start.md:137 +msgid "**💡 Notes**:" +msgstr "" + +#: ../../../docs/quick-start.md:138 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/quick-start.md:139 +msgid "" +"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " +"full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/quick-start.md:151 +msgid "Finalize server installation" +msgstr "" + +#: ../../../docs/quick-start.md:153 +msgid "" +"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:155 +msgid "" +"Now that you've configured Matrix services and your user account, you " +"need to **finalize the installation process** by [setting up Matrix " +"delegation (redirection)](howto-server-delegation.md), so that your " +"Matrix server (`matrix.example.com`) can present itself as the base " +"domain (`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/quick-start.md:157 +msgid "" +"**This is required for federation to work!** Without a proper " +"configuration, your server will effectively not be part of the Matrix " +"network." +msgstr "" + +#: ../../../docs/quick-start.md:159 +msgid "" +"To configure the delegation, you have these two options. Choose one of " +"them according to your situation." +msgstr "" + +#: ../../../docs/quick-start.md:161 +msgid "" +"If you can afford to point the base domain at the Matrix server, follow " +"the instruction below which guides you into [serving the base domain" +"](configuring-playbook-base-domain-serving.md) from the integrated web " +"server." +msgstr "" + +#: ../../../docs/quick-start.md:162 +msgid "" +"Alternatively, if you're using the base domain for other purposes and " +"cannot point it to the Matrix server (and thus cannot \"serve the base " +"domain\" from it), you most likely need to [manually install well-known " +"files on the base domain's server](configuring-well-known.md#manually-" +"installing-well-known-files-on-the-base-domains-server)." +msgstr "" + +#: ../../../docs/quick-start.md:164 +msgid "" +"To have the base domain served from the integrated web server, add the " +"following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/quick-start.md:170 +msgid "" +"After configuring the playbook, run the command below and wait until it " +"finishes:" +msgstr "" + +#: ../../../docs/quick-start.md:176 +msgid "" +"💡 Running the `install-matrix-static-files` playbook tag (as done here) " +"is an optimized version of running [the full setup command](#run-" +"installation-command)." +msgstr "" + +#: ../../../docs/quick-start.md:178 +msgid "" +"After the command finishes, you can also check whether your server " +"federates with the Matrix network by using the [Federation " +"Tester](https://federationtester.matrix.org/) against your base domain " +"(`example.com`), not the `matrix.example.com` subdomain." +msgstr "" + +#: ../../../docs/quick-start.md:180 +msgid "Re-run the full setup command any time" +msgstr "" + +#: ../../../docs/quick-start.md:182 +msgid "" +"If you think something is wrong with the server configuration, feel free " +"to re-run the setup command any time:" +msgstr "" + +#: ../../../docs/quick-start.md:188 +msgid "Log in to your user account" +msgstr "" + +#: ../../../docs/quick-start.md:190 +msgid "" +"Finally, let's make sure that you can log in to the created account with " +"the specified password." +msgstr "" + +#: ../../../docs/quick-start.md:192 +msgid "" +"You should be able to log in to it with your own [Element Web" +"](configuring-playbook-client-element-web.md) client which you have set " +"up at `element.example.com` by running the playbook. Open the URL " +"(`https://element.example.com`) in a web browser and enter your " +"credentials to log in." +msgstr "" + +#: ../../../docs/quick-start.md:194 +msgid "" +"**If you successfully logged in to your account, installing and " +"configuring is complete**🎉" +msgstr "" + +#: ../../../docs/quick-start.md:196 +msgid "" +"Come say Hi👋 in our support room - [#matrix-docker-ansible-" +"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" +"deploy:devture.com). You might learn something or get to help someone " +"else new to Matrix hosting." +msgstr "" + +#: ../../../docs/quick-start.md:198 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/quick-start.md:200 +msgid "" +"Once you get familiar with the playbook, you might probably want to set " +"up additional services such as a bridge on your server." +msgstr "" + +#: ../../../docs/quick-start.md:202 +msgid "" +"As this page intends to be a quick start guide which explains how to " +"start the core Matrix services, it does not cover a topic like how to set" +" them up. Take a look at the list of [things to do next](installing.md" +"#things-to-do-next) to learn more." +msgstr "" + +#: ../../../docs/quick-start.md:204 +msgid "⚠️Keep the playbook and services up-to-date" +msgstr "" + +#: ../../../docs/quick-start.md:206 +msgid "" +"While this playbook helps you to set up Matrix services and maintain " +"them, it will **not** automatically run the maintenance task for you. You" +" will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/quick-start.md:208 +msgid "" +"Since it is unsafe to keep outdated services running on the server " +"connected to the internet, please consider to update the playbook and re-" +"run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/quick-start.md:210 +msgid "" +"For more information about upgrading or maintaining services with the " +"playbook, take at look at this page: [Upgrading the Matrix services" +"](maintenance-upgrading-services.md)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po new file mode 100644 index 000000000..61b349423 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po @@ -0,0 +1,349 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/registering-users.md:1 +msgid "Registering users" +msgstr "" + +#: ../../../docs/registering-users.md:3 +msgid "" +"This documentation page tells you how to create user accounts on your " +"Matrix server." +msgstr "" + +#: ../../../docs/registering-users.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/registering-users.md:7 +msgid "[Registering users](#registering-users)" +msgstr "" + +#: ../../../docs/registering-users.md:8 +msgid "[Registering users manually](#registering-users-manually)" +msgstr "" + +#: ../../../docs/registering-users.md:9 +msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)" +msgstr "" + +#: ../../../docs/registering-users.md:10 +msgid "" +"[Letting certain users register on your private server](#letting-certain-" +"users-register-on-your-private-server)" +msgstr "" + +#: ../../../docs/registering-users.md:11 +msgid "[Enabling public user registration](#enabling-public-user-registration)" +msgstr "" + +#: ../../../docs/registering-users.md:12 +msgid "" +"[Adding/Removing Administrator privileges to an existing user" +"](#addingremoving-administrator-privileges-to-an-existing-user)" +msgstr "" + +#: ../../../docs/registering-users.md:14 +msgid "Registering users manually" +msgstr "" + +#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:118 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/registering-users.md:17 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/registering-users.md:18 +msgid "" +"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " +"(`@alice:example.com`)" +msgstr "" + +#: ../../../docs/registering-users.md:19 +msgid "" +"Use `admin=yes` or `admin=no` depending on whether you wish to make the " +"user an administrator of the Matrix server" +msgstr "" + +#: ../../../docs/registering-users.md:21 +msgid "" +"After registering a user (using one of the methods below), **you can log " +"in with that user** via the [Element Web](configuring-playbook-client-" +"element-web.md) service that this playbook has installed for you at a URL" +" like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/registering-users.md:23 +msgid "Registering users via the Ansible playbook" +msgstr "" + +#: ../../../docs/registering-users.md:25 +msgid "" +"It's best to register users via the Ansible playbook, because it works " +"regardless of homeserver implementation (Synapse, Dendrite, etc) or usage" +" of [Matrix Authentication Service](configuring-playbook-matrix-" +"authentication-service.md) (MAS)." +msgstr "" + +#: ../../../docs/registering-users.md:27 +msgid "To register a user via this Ansible playbook:" +msgstr "" + +#: ../../../docs/registering-users.md:35 +msgid "**or** by invoking `ansible-playbook` manually:" +msgstr "" + +#: ../../../docs/registering-users.md:43 +msgid "" +"Feel free to register as many users (for friends, family, etc.) as you " +"want. Still, perhaps you should grant full administrative access to your " +"user account only (with `admin=yes`), and others should be created with " +"`admin=no`." +msgstr "" + +#: ../../../docs/registering-users.md:45 +msgid "" +"⚠️ **Warning**: If you're registering users against Matrix Authentication" +" Service, do note that it [still insists](https://github.com/element-hq" +"/matrix-authentication-service/issues/1505) on having a verified email " +"address for each user. Upon a user's first login, they will be asked to " +"confirm their email address. This requires that email sending is " +"[configured](./configuring-playbook-email.md). You can also consult the " +"[Working around email deliverability issues](./configuring-playbook-" +"matrix-authentication-service.md#working-around-email-deliverability-" +"issues) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:47 +msgid "Registering users manually for Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:49 +msgid "" +"If you're using the [Synapse](configuring-playbook-synapse.md) homeserver" +" implementation (which is the default), you can register users via the " +"command-line after **SSH**-ing to your server (requires that [all " +"services have been started](installing.md#install-matrix-server-and-" +"services)):" +msgstr "" + +#: ../../../docs/registering-users.md:57 +msgid "Registering users manually for Dendrite" +msgstr "" + +#: ../../../docs/registering-users.md:59 +msgid "" +"If you're using the [Dendrite](./configuring-playbook-dendrite.md) " +"homeserver implementation, you can register users via the command-line " +"after **SSH**-ing to your server (requires that [all services have been " +"started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:67 +msgid "Registering users manually for Matrix Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:69 +msgid "" +"If you're using the [Matrix Authentication Service](./configuring-" +"playbook-matrix-authentication-service.md) and your existing homeserver " +"(most likely [Synapse](./configuring-playbook-synapse.md)) is delegating " +"authentication to it, you can register users via the command-line after " +"**SSH**-ing to your server (requires that [all services have been " +"started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:77 +msgid "" +"This `register-user` script actually invokes the `mas-cli manage " +"register-user` command under the hood. If you'd like more control over " +"the registration process, consider invoking the `mas-cli` command " +"directly:" +msgstr "" + +#: ../../../docs/registering-users.md:83 +msgid "" +"⚠️ **Warning**: Matrix Authentication Service [still " +"insists](https://github.com/element-hq/matrix-authentication-" +"service/issues/1505) on having a verified email address for each user. " +"Upon a user's first login, they will be asked to confirm their email " +"address. This requires that email sending is [configured](./configuring-" +"playbook-email.md). You can also consult the [Working around email " +"deliverability issues](./configuring-playbook-matrix-authentication-" +"service.md#working-around-email-deliverability-issues) section for more " +"information." +msgstr "" + +#: ../../../docs/registering-users.md:85 +msgid "Managing users via a Web UI" +msgstr "" + +#: ../../../docs/registering-users.md:87 +msgid "" +"To manage users more easily (via a web user-interace), you can install " +"[Synapse Admin](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/registering-users.md:89 +msgid "" +"⚠️ **Warning**: If you're using [Matrix Authentication Service" +"](configuring-playbook-matrix-authentication-service.md), note that user " +"management via synapse-admin is not fully working yet. See the " +"[Expectations](configuring-playbook-matrix-authentication-" +"service.md#expectations) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:91 +msgid "Letting certain users register on your private server" +msgstr "" + +#: ../../../docs/registering-users.md:93 +msgid "" +"If you'd rather **keep your server private** (public registration closed," +" as is the default), and **let certain people create accounts by " +"themselves** (instead of creating user accounts manually like this), " +"consider installing and making use of [matrix-registration](configuring-" +"playbook-matrix-registration.md)." +msgstr "" + +#: ../../../docs/registering-users.md:95 +msgid "Enabling public user registration" +msgstr "" + +#: ../../../docs/registering-users.md:97 +msgid "" +"To **open up user registration publicly** (usually **not recommended**), " +"add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/registering-users.md:99 +msgid "For Synapse:" +msgstr "" + +#: ../../../docs/registering-users.md:105 +msgid "For Dendrite:" +msgstr "" + +#: ../../../docs/registering-users.md:111 +msgid "" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" +msgstr "" + +#: ../../../docs/registering-users.md:120 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/registering-users.md:122 +msgid "" +"`just install-all` is useful for maintaining your setup quickly ([2x-5x " +"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" +"runtime) than `just setup-all`) when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/registering-users.md:124 +msgid "" +"If you're opening up registrations publicly like this, you might also " +"wish to [configure CAPTCHA protection](configuring-captcha.md)." +msgstr "" + +#: ../../../docs/registering-users.md:126 +msgid "Adding/Removing Administrator privileges to an existing user" +msgstr "" + +#: ../../../docs/registering-users.md:128 +msgid "Adding/Removing Administrator privileges to an existing user in Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:130 +msgid "" +"To change the admin privileges for a user in Synapse's local database, " +"you need to run an SQL query like this against the `synapse` database:" +msgstr "" + +#: ../../../docs/registering-users.md:136 +msgid "where:" +msgstr "" + +#: ../../../docs/registering-users.md:138 +msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)" +msgstr "" + +#: ../../../docs/registering-users.md:139 +msgid "`USER` and `example.com` pointing to a valid user on your server" +msgstr "" + +#: ../../../docs/registering-users.md:141 +msgid "" +"If you're using the integrated Postgres server and not an [external " +"Postgres server](configuring-playbook-external-postgres.md), you can " +"launch a Postgres into the `synapse` database by:" +msgstr "" + +#: ../../../docs/registering-users.md:143 +msgid "" +"running `/matrix/postgres/bin/cli` - to launch " +"[`psql`](https://www.postgresql.org/docs/current/app-psql.html)" +msgstr "" + +#: ../../../docs/registering-users.md:144 +msgid "running `\\c synapse` - to change to the `synapse` database" +msgstr "" + +#: ../../../docs/registering-users.md:146 +msgid "You can then proceed to run the query above." +msgstr "" + +#: ../../../docs/registering-users.md:148 +msgid "" +"**Note**: directly modifying the raw data of Synapse (or any other " +"software) could cause the software to break. You've been warned!" +msgstr "" + +#: ../../../docs/registering-users.md:150 +msgid "" +"Adding/Removing Administrator privileges to an existing user in Matrix " +"Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:152 +msgid "" +"Promoting/demoting a user in Matrix Authentication Service cannot " +"currently (2024-10-19) be done via the [`mas-cli` Management tool" +"](./configuring-playbook-matrix-authentication-service.md#management)." +msgstr "" + +#: ../../../docs/registering-users.md:154 +msgid "" +"You can do it via the [MAS Admin API](https://element-hq.github.io" +"/matrix-authentication-service/api/index.html)'s `POST " +"/api/admin/v1/users/{id}/set-admin` endpoint." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/self-building.po b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po new file mode 100644 index 000000000..257ace6c6 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po @@ -0,0 +1,200 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 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" +"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/self-building.md:1 +msgid "Self-building" +msgstr "" + +#: ../../../docs/self-building.md:3 +msgid "" +"**Caution: self-building does not have to be used on its own. See the " +"[Alternative Architectures](alternative-architectures.md) page.**" +msgstr "" + +#: ../../../docs/self-building.md:5 +msgid "" +"The playbook supports self-building of various components, which don't " +"have a container image for your architecture (see the [container images " +"we use](container-images.md)). For `amd64`, self-building is not " +"required." +msgstr "" + +#: ../../../docs/self-building.md:7 +msgid "" +"For other architectures (e.g. `arm32`, `arm64`), ready-made container " +"images are used when available. If there's no ready-made image for a " +"specific component and said component supports self-building, an image " +"will be built on the host. Building images like this takes more time and " +"resources (some build tools need to get installed by the playbook to " +"assist building)." +msgstr "" + +#: ../../../docs/self-building.md:9 +msgid "" +"To make use of self-building, you don't need to do anything. If a " +"component has an image for the specified architecture, the playbook will " +"use it directly. If not, it will build the image on the server itself." +msgstr "" + +#: ../../../docs/self-building.md:11 +msgid "Note that **not all components support self-building yet**." +msgstr "" + +#: ../../../docs/self-building.md:13 +msgid "" +"Possibly outdated list of roles where self-building the Docker image is " +"currently possible:" +msgstr "" + +#: ../../../docs/self-building.md:14 +msgid "`matrix-synapse`" +msgstr "" + +#: ../../../docs/self-building.md:15 +msgid "`matrix-synapse-admin`" +msgstr "" + +#: ../../../docs/self-building.md:16 +msgid "`matrix-client-element`" +msgstr "" + +#: ../../../docs/self-building.md:17 +msgid "`matrix-client-hydrogen`" +msgstr "" + +#: ../../../docs/self-building.md:18 +msgid "`matrix-client-cinny`" +msgstr "" + +#: ../../../docs/self-building.md:19 +msgid "`matrix-registration`" +msgstr "" + +#: ../../../docs/self-building.md:20 +msgid "`matrix-coturn`" +msgstr "" + +#: ../../../docs/self-building.md:21 +msgid "`matrix-corporal`" +msgstr "" + +#: ../../../docs/self-building.md:22 +msgid "`matrix-dimension`" +msgstr "" + +#: ../../../docs/self-building.md:23 +msgid "`matrix-ma1sd`" +msgstr "" + +#: ../../../docs/self-building.md:24 +msgid "`exim-relay`" +msgstr "" + +#: ../../../docs/self-building.md:25 +msgid "`matrix-bridge-hookshot`" +msgstr "" + +#: ../../../docs/self-building.md:26 +msgid "`matrix-bridge-appservice-irc`" +msgstr "" + +#: ../../../docs/self-building.md:27 +msgid "`matrix-bridge-appservice-slack`" +msgstr "" + +#: ../../../docs/self-building.md:28 +msgid "`matrix-bridge-appservice-webhooks`" +msgstr "" + +#: ../../../docs/self-building.md:29 +msgid "`matrix-bridge-beeper-linkedin`" +msgstr "" + +#: ../../../docs/self-building.md:30 +msgid "`matrix-bridge-mautrix-facebook`" +msgstr "" + +#: ../../../docs/self-building.md:31 +msgid "`matrix-bridge-mautrix-hangouts`" +msgstr "" + +#: ../../../docs/self-building.md:32 +msgid "`matrix-bridge-mautrix-googlechat`" +msgstr "" + +#: ../../../docs/self-building.md:33 +msgid "`matrix-bridge-mautrix-telegram`" +msgstr "" + +#: ../../../docs/self-building.md:34 +msgid "`matrix-bridge-mautrix-signal`" +msgstr "" + +#: ../../../docs/self-building.md:35 +msgid "`matrix-bridge-mautrix-gmessages`" +msgstr "" + +#: ../../../docs/self-building.md:36 +msgid "`matrix-bridge-mautrix-whatsapp`" +msgstr "" + +#: ../../../docs/self-building.md:37 +msgid "`matrix-bridge-mx-puppet-steam`" +msgstr "" + +#: ../../../docs/self-building.md:38 +msgid "`matrix-bot-mjolnir`" +msgstr "" + +#: ../../../docs/self-building.md:39 +msgid "`matrix-bot-honoroit`" +msgstr "" + +#: ../../../docs/self-building.md:40 +msgid "`matrix-bot-matrix-reminder-bot`" +msgstr "" + +#: ../../../docs/self-building.md:41 +msgid "`matrix-bot-maubot`" +msgstr "" + +#: ../../../docs/self-building.md:42 +msgid "`matrix-email2matrix`" +msgstr "" + +#: ../../../docs/self-building.md:43 +msgid "`matrix-pantalaimon`" +msgstr "" + +#: ../../../docs/self-building.md:45 +msgid "" +"Adding self-building support to other roles is welcome. Feel free to " +"contribute!" +msgstr "" + +#: ../../../docs/self-building.md:47 +msgid "" +"If you'd like **to force self-building** even if an image is available " +"for your architecture, look into the `matrix_*_self_build` variables " +"provided by individual roles." +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po new file mode 100644 index 000000000..7998ab8f0 --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po @@ -0,0 +1,105 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/uninstalling.md:1 +msgid "Uninstalling" +msgstr "" + +#: ../../../docs/uninstalling.md:3 +msgid "**Warnings**:" +msgstr "" + +#: ../../../docs/uninstalling.md:5 +msgid "" +"If your server federates with others, make sure to **leave any federated " +"rooms before nuking your Matrix server's data**. Otherwise, the next time" +" you set up a Matrix server for this domain (regardless of the " +"installation method you use), you'll encounter trouble federating." +msgstr "" + +#: ../../../docs/uninstalling.md:7 +msgid "" +"If you have some trouble with your installation, you can just [re-run the" +" playbook](installing.md) and it will try to set things up again. " +"**Uninstalling and then installing anew rarely solves anything**." +msgstr "" + +#: ../../../docs/uninstalling.md:11 +msgid "Uninstalling using a script" +msgstr "" + +#: ../../../docs/uninstalling.md:13 +msgid "Installing places a `/matrix/bin/remove-all` script on the server." +msgstr "" + +#: ../../../docs/uninstalling.md:15 +msgid "" +"You can run it to to have it uninstall things for you automatically (see " +"below). **Use with caution!**" +msgstr "" + +#: ../../../docs/uninstalling.md:17 +msgid "Uninstalling manually" +msgstr "" + +#: ../../../docs/uninstalling.md:19 +msgid "" +"If you prefer to uninstall manually, run these commands (most are meant " +"to be executed on the Matrix server itself):" +msgstr "" + +#: ../../../docs/uninstalling.md:21 +msgid "" +"ensure all Matrix services are stopped: `ansible-playbook -i " +"inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working " +"to run this command, you can run `systemctl stop 'matrix*'` manually on " +"the server)" +msgstr "" + +#: ../../../docs/uninstalling.md:23 +msgid "" +"delete the Matrix-related systemd `.service` and `.timer` files (`rm -f " +"/etc/systemd/system/matrix*.{service,timer}`) and reload systemd " +"(`systemctl daemon-reload`)" +msgstr "" + +#: ../../../docs/uninstalling.md:25 +msgid "" +"delete some cached Docker images (`docker system prune -a`) or just " +"delete them all (`docker rmi $(docker images -aq)`)" +msgstr "" + +#: ../../../docs/uninstalling.md:27 +msgid "" +"delete the Docker networks: `docker network rm matrix matrix-coturn` " +"(might have been deleted already if you ran the `docker system prune` " +"command)" +msgstr "" + +#: ../../../docs/uninstalling.md:29 +msgid "uninstall Docker itself, if necessary" +msgstr "" + +#: ../../../docs/uninstalling.md:31 +msgid "delete the `/matrix` directory (`rm -rf /matrix`)" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po new file mode 100644 index 000000000..ab02c7eee --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po @@ -0,0 +1,110 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community +# members +# This file is distributed under the same license as the +# matrix-docker-ansible-deploy package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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/updating-users-passwords.md:1 +msgid "Updating users passwords" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:3 +msgid "Option 1 (if you are using the integrated Postgres database):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:6 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:7 +msgid "" +"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " +"(`@alice:example.com`)" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:9 +msgid "You can reset a user's password via the Ansible playbook:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:15 +msgid "" +"**You can then log in with that user** via Element Web that this playbook" +" has created for you at a URL like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:17 +msgid "Option 2 (if you are using an external Postgres server):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:19 +msgid "" +"You can manually generate the password hash by using the command-line " +"after **SSH**-ing to your server (requires that [all services have been " +"started](installing.md#finalize-the-installation):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:25 +msgid "and then connecting to the postgres server and executing:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:31 +msgid "where `` is the hash returned by the docker command above." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:33 +msgid "Option 3:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:35 +msgid "" +"Use the Synapse User Admin API as described here: https://github.com" +"/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-" +"password" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:37 +msgid "" +"This requires an [access token](obtaining-access-tokens.md) from a server" +" admin account. *This method will also log the user out of all of their " +"clients while the other options do not.*" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:39 +msgid "" +"If you didn't make your account a server admin when you created it, you " +"can learn how to switch it now by reading about it in [Adding/Removing " +"Administrator privileges to an existing user in Synapse](registering-" +"users.md#addingremoving-administrator-privileges-to-an-existing-user-in-" +"synapse)." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:41 +msgid "Example:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:43 +msgid "" +"To set @alice:example.com's password to `correct_horse_battery_staple` " +"you could use this curl command:" +msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/i18n/README.po b/i18n/locales/jp/LC_MESSAGES/i18n/README.po new file mode 100644 index 000000000..359b7173f --- /dev/null +++ b/i18n/locales/jp/LC_MESSAGES/i18n/README.po @@ -0,0 +1,446 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 2024-12-20 09:29+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" + +#: ../../README.md:1 +msgid "Internationalization" +msgstr "" + +#: ../../README.md:3 +msgid "" +"Translated documentation files are published and maintained in " +"[`translated/`](translated/) directory." +msgstr "" + +#: ../../README.md:5 +msgid "Currently, we support translation of:" +msgstr "" + +#: ../../README.md:7 +msgid "Markdown files found at the top level project directory" +msgstr "" + +#: ../../README.md:8 +msgid "" +"Markdown files found in the [`docs`](../docs/) directory (this is where " +"the bulk of the documentation is)" +msgstr "" + +#: ../../README.md:9 +msgid "this current document in the `i18n` directory" +msgstr "" + +#: ../../README.md:11 +msgid "" +"💡 For readers' sake, we only [publish translations in a new language" +"](#publish-translations-in-a-new-language) when the translation " +"progresses beyond a certain threshold (requiring that at least the " +"project README and core installation guides are translated)." +msgstr "" + +#: ../../README.md:13 +msgid "Organization of this `i18n` directory is as follows:" +msgstr "" + +#: ../../README.md:15 +msgid "" +"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we " +"publish translations for (in the [translated/](translated/) directory)" +msgstr "" + +#: ../../README.md:16 +msgid "" +"[.gitignore](.gitignore): a list of files and directories to ignore in " +"the `i18n` directory. We intentionaly ignore translated results " +"(`translated/` 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:17 +msgid "" +"[justfile](justfile): a list of recipes for " +"[just](https://github.com/casey/just) command runner" +msgstr "" + +#: ../../README.md:18 +msgid "" +"[requirements.txt](requirements.txt): a list of Python packages required " +"to work with translations" +msgstr "" + +#: ../../README.md:19 +msgid "" +"[translation-templates/](translation-templates/): a list of English " +"translation templates - strings extracted from Markdown files" +msgstr "" + +#: ../../README.md:20 +msgid "[locales/](locales/): localization files for languages" +msgstr "" + +#: ../../README.md:21 +msgid "" +"[translated/](translated/): translated documents for published languages " +"(see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations" +" in a new language](#publish-translations-in-a-new-language))" +msgstr "" + +#: ../../README.md:23 +msgid "Guide for translators" +msgstr "" + +#: ../../README.md:25 +msgid "" +"This project uses [Sphinx](https://www.sphinx-doc.org/) to generate " +"translated documents." +msgstr "" + +#: ../../README.md:27 +msgid "" +"For details about using Sphinx for translation, refer [this official " +"document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) " +"as well." +msgstr "" + +#: ../../README.md:29 +msgid "" +"For now, translations are handled manually by editing `.po` files in the " +"`locales/` directory. In the future, we plan on integrating " +"with [Weblate](https://weblate.org/) to allow for translating from a web " +"interface." +msgstr "" + +#: ../../README.md:31 +msgid "(Recommended) Using the uv package manager and just command runner" +msgstr "" + +#: ../../README.md:33 +msgid "" +"If you have the [uv](https://docs.astral.sh/uv/) package manager and " +"[just](https://github.com/casey/just) command runner installed, you can " +"use our [justfile](justfile) recipes to easily manage translation files " +"and build translated documents." +msgstr "" + +#: ../../README.md:35 +msgid "" +"The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create" +" [a Python virtual " +"environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` " +"directory and install the required Python packages (as per " +"[requirements.txt](requirements.txt)) to it." +msgstr "" + +#: ../../README.md:37 ../../README.md:64 +msgid "Preparation" +msgstr "" + +#: ../../README.md:39 +msgid "" +"Make sure you have the [uv](https://docs.astral.sh/uv/) package manager " +"and [just](https://github.com/casey/just) command runner installed." +msgstr "" + +#: ../../README.md:41 ../../README.md:72 +msgid "Translation" +msgstr "" + +#: ../../README.md:43 ../../README.md:74 +msgid "" +"Recommended flow when working on a new language (replace `` " +"with the language code, e.g. `bg`):" +msgstr "" + +#: ../../README.md:45 +msgid "" +"Update the locale files for your language: `just sync-for-language " +"` (internally, this automatically runs `just extract-" +"translation-templates` to make sure the translation templates are up-to-" +"date)" +msgstr "" + +#: ../../README.md:47 ../../README.md:80 +msgid "Use an editor to translate the files in the `locales/` directory" +msgstr "" + +#: ../../README.md:49 +msgid "Build translated documents: `just build-for-language `" +msgstr "" + +#: ../../README.md:51 ../../README.md:84 +msgid "Preview the result in the `translated/` directory" +msgstr "" + +#: ../../README.md:53 ../../README.md:86 +msgid "Commit your changes done to the `locales/` directory" +msgstr "" + +#: ../../README.md:55 ../../README.md:88 +msgid "" +"If you have progressed with the translation beyond a certain threshold, " +"consider [Publishing translations in a new language](#publish-" +"translations-in-a-new-language)" +msgstr "" + +#: ../../README.md:57 +msgid "Using any other package manager and manual scripts" +msgstr "" + +#: ../../README.md:59 +msgid "" +"If you cannot use [uv](https://docs.astral.sh/uv/) and/or " +"[just](https://github.com/casey/just), you can:" +msgstr "" + +#: ../../README.md:61 +msgid "" +"manage Python packages in another way " +"([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-" +"poetry.org/), etc.)" +msgstr "" + +#: ../../README.md:62 +msgid "" +"manage translation strings and build translated documents manually by " +"invoking scripts from the [bin](bin/) directory" +msgstr "" + +#: ../../README.md:66 +msgid "virtualenv and pip" +msgstr "" + +#: ../../README.md:68 +msgid "" +"Create a Python virtual environment in the `.venv` directory: `virtualenv" +" .venv`" +msgstr "" + +#: ../../README.md:69 +msgid "Activate the virtual environment: `source .venv/bin/activate`" +msgstr "" + +#: ../../README.md:70 +msgid "" +"Install the required Python packages using " +"[pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" +msgstr "" + +#: ../../README.md:76 +msgid "" +"Ensure the English translation templates ([translation-templates" +"/](translation-templates/)) are extracted: `./bin/extract-translation-" +"templates.sh`" +msgstr "" + +#: ../../README.md:78 +msgid "" +"Update the locale files for your language: `./bin/sync-translation-" +"templates-to-locales.sh `" +msgstr "" + +#: ../../README.md:82 +msgid "Build translated documents: `./bin/build-translated-result.sh `" +msgstr "" + +#: ../../README.md:90 +msgid "Publish translations in a new language" +msgstr "" + +#: ../../README.md:92 +msgid "" +"To publish prebuilt documents translated in a new language to the " +"`translated/` directory:" +msgstr "" + +#: ../../README.md:94 +msgid "" +"add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) " +"file" +msgstr "" + +#: ../../README.md:95 +msgid "" +"whitelist its `translated/` directory by adding a " +"`!translated/` rule to the [.gitignore](.gitignore) file" +msgstr "" + +#: ../../README.md:97 +msgid "" +"💡 Leave a trailing new line at the end of the " +"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." +msgstr "" + +#~ msgid "Translation guide" +#~ msgstr "" + +#~ msgid "" +#~ "If you are interested in translating " +#~ "this project, please check out our " +#~ "[Weblate project](https://example.com)." +#~ msgstr "" + +#~ msgid "" +#~ "If your language is not yet " +#~ "listed, please express your wishes to" +#~ " start translating it in our [Matrix" +#~ " room](https://matrix.to/#/#matrix-docker-ansible-" +#~ "deploy:devture.com). If anyone else is " +#~ "found to be working on your " +#~ "language, please co-ordinate if needed." +#~ msgstr "" + +#~ msgid "" +#~ "Currently, we manage translaion of " +#~ "markdown files on the top level " +#~ "directory and inside [`docs`](../docs/), and" +#~ " this file (`README.md`) only." +#~ msgstr "" + +#~ msgid "" +#~ "Translated files are published and " +#~ "maintained in [`markdown`](../markdown/) directory." +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ For readers' sake, we set a " +#~ "minimum condition for publishing documents " +#~ "translated in your language: translating " +#~ "basic articles such as READMEs, " +#~ "installation guides ([Quick start](quick-" +#~ "start.md) and the full installation " +#~ "guide which starts at the " +#~ "[Prerequisites](prerequisites.md)), etc. If you " +#~ "think we have missed progress of " +#~ "translation in your language, please " +#~ "ping us at the Matrix room." +#~ msgstr "" + +#~ msgid "Translation development guide" +#~ msgstr "" + +#~ msgid "Install packages" +#~ msgstr "" + +#~ msgid "" +#~ "To manage files for translation and " +#~ "build translated documents, you need to" +#~ " install packages at first. You can" +#~ " install them with " +#~ "[pip](https://pip.pypa.io/en/stable/)." +#~ msgstr "" + +#~ msgid "" +#~ "After installing pip and activating the" +#~ " virtual environment, run the command " +#~ "below on this directory:" +#~ msgstr "" + +#~ msgid "Update PO files" +#~ msgstr "" + +#~ msgid "" +#~ "If a document is updated, it is" +#~ " necessary to generate updated `.pot` " +#~ "(catalog templates) files and to apply" +#~ " differences to translated `.po` (message" +#~ " catalogs) files." +#~ msgstr "" + +#~ msgid "To do so, run these commands:" +#~ msgstr "" + +#~ msgid "" +#~ "To generate `.po` files for a new" +#~ " language, e.g. Bulgarian, run the " +#~ "command below:" +#~ msgstr "" + +#~ msgid "" +#~ "After the original documents have " +#~ "changed, run [i18n_update.sh](i18n_update.sh) to " +#~ "update `.po` files in all languages " +#~ "specified on [`LANG`](LANG) file:" +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ Unless your language code is " +#~ "added to the `LANG` file, running " +#~ "the script does not generate `.po` " +#~ "files in your language in `locales` " +#~ "directory." +#~ msgstr "" + +#~ msgid "Build" +#~ msgstr "" + +#~ msgid "To build the documentation in English, run the command below:" +#~ msgstr "" + +#~ msgid "It generates Markdown files in `_build/markdown/`." +#~ msgstr "" + +#~ msgid "" +#~ "ℹ️ As the original documents are " +#~ "also Markdown files, the generated files" +#~ " in English are identical to the " +#~ "original ones." +#~ msgstr "" + +#~ msgid "To build documents in another language, e.g. Bulgarian, run:" +#~ msgstr "" + +#~ msgid "" +#~ "Running [i18n_build.sh](i18n_build.sh) builds " +#~ "Markdown files in all languages " +#~ "specified on `LANG` file into `markdown`" +#~ " directory:" +#~ msgstr "" + +#~ msgid "Publish documents in a new language" +#~ msgstr "" + +#~ msgid "" +#~ "To publish documents translated in a " +#~ "new language on `markdown` directory, " +#~ "add its language code to `LANG` " +#~ "file. Then, run `i18n_update.sh` and " +#~ "`i18n_build.sh`. After that, you would " +#~ "need to push the documents to the" +#~ " repository." +#~ msgstr "" + +#~ msgid "💡 Leave an empty line at the end of the `LANG` file." +#~ msgstr "" + +#~ msgid "Using the uv package manager and just command runner" +#~ msgstr "" + +#~ msgid "" +#~ "Update the locale files for your " +#~ "language: `just sync-language ` " +#~ "(internally, this automatically runs `just " +#~ "extract-translation-templates` to make " +#~ "sure the translation templates are " +#~ "up-to-date)" +#~ msgstr "" + diff --git a/i18n/requirements.txt b/i18n/requirements.txt new file mode 100644 index 000000000..92ee5b8b1 --- /dev/null +++ b/i18n/requirements.txt @@ -0,0 +1,33 @@ +alabaster==1.0.0 +babel==2.16.0 +certifi==2024.12.14 +charset-normalizer==3.4.0 +click==8.1.7 +docutils==0.21.2 +idna==3.10 +imagesize==1.4.1 +Jinja2==3.1.4 +linkify-it-py==2.0.3 +markdown-it-py==3.0.0 +MarkupSafe==3.0.2 +mdit-py-plugins==0.4.2 +mdurl==0.1.2 +myst-parser==4.0.0 +packaging==24.2 +Pygments==2.18.0 +PyYAML==6.0.2 +requests==2.32.3 +setuptools==75.6.0 +snowballstemmer==2.2.0 +Sphinx==8.1.3 +sphinx-intl==2.3.1 +sphinx-markdown-builder==0.6.7 +sphinxcontrib-applehelp==2.0.0 +sphinxcontrib-devhelp==2.0.0 +sphinxcontrib-htmlhelp==2.1.0 +sphinxcontrib-jsmath==1.0.1 +sphinxcontrib-qthelp==2.0.0 +sphinxcontrib-serializinghtml==2.0.0 +tabulate==0.9.0 +uc-micro-py==1.0.3 +urllib3==2.2.3 diff --git a/i18n/translation-templates/CHANGELOG.pot b/i18n/translation-templates/CHANGELOG.pot new file mode 100644 index 000000000..ce8eb6286 --- /dev/null +++ b/i18n/translation-templates/CHANGELOG.pot @@ -0,0 +1,6971 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../CHANGELOG.md:1 +msgid "2024-11-26" +msgstr "" + +#: ../../../CHANGELOG.md:3 +msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media" +msgstr "" + +#: ../../../CHANGELOG.md:5 +msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)." +msgstr "" + +#: ../../../CHANGELOG.md:7 +msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)." +msgstr "" + +#: ../../../CHANGELOG.md:9 +msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago." +msgstr "" + +#: ../../../CHANGELOG.md:11 +msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default." +msgstr "" + +#: ../../../CHANGELOG.md:13 +msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing." +msgstr "" + +#: ../../../CHANGELOG.md:15 +msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know." +msgstr "" + +#: ../../../CHANGELOG.md:17 +msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:20 +msgid "2024-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:22 +msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB" +msgstr "" + +#: ../../../CHANGELOG.md:24 +msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again." +msgstr "" + +#: ../../../CHANGELOG.md:26 +msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)." +msgstr "" + +#: ../../../CHANGELOG.md:28 +msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)." +msgstr "" + +#: ../../../CHANGELOG.md:30 +msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey." +msgstr "" + +#: ../../../CHANGELOG.md:32 +msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it." +msgstr "" + +#: ../../../CHANGELOG.md:34 +msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:36 +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:38 +#: ../../../CHANGELOG.md:378 +msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:49 +msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:59 +msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway." +msgstr "" + +#: ../../../CHANGELOG.md:62 +msgid "2024-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:64 +msgid "HTTP-compression support for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:66 +msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)." +msgstr "" + +#: ../../../CHANGELOG.md:68 +msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression." +msgstr "" + +#: ../../../CHANGELOG.md:70 +msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support." +msgstr "" + +#: ../../../CHANGELOG.md:72 +msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)." +msgstr "" + +#: ../../../CHANGELOG.md:74 +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:" +msgstr "" + +#: ../../../CHANGELOG.md:76 +msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" +msgstr "" + +#: ../../../CHANGELOG.md:77 +msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`" +msgstr "" + +#: ../../../CHANGELOG.md:78 +msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)" +msgstr "" + +#: ../../../CHANGELOG.md:80 +msgid "Timeout adjustments for Traefik-based setups" +msgstr "" + +#: ../../../CHANGELOG.md:82 +msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:84 +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually." +msgstr "" + +#: ../../../CHANGELOG.md:86 +msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case." +msgstr "" + +#: ../../../CHANGELOG.md:88 +msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them." +msgstr "" + +#: ../../../CHANGELOG.md:90 +msgid "Example of the default timeout values used by the playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:101 +msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." +msgstr "" + +#: ../../../CHANGELOG.md:104 +msgid "2024-11-08" +msgstr "" + +#: ../../../CHANGELOG.md:106 +msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client" +msgstr "" + +#: ../../../CHANGELOG.md:108 +msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)." +msgstr "" + +#: ../../../CHANGELOG.md:110 +msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed." +msgstr "" + +#: ../../../CHANGELOG.md:112 +msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:115 +msgid "2024-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:117 +msgid "(BC Break) Postmoogle's variable names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:119 +msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:121 +msgid "2024-10-19" +msgstr "" + +#: ../../../CHANGELOG.md:123 +msgid "Support for Matrix Authentication Service" +msgstr "" + +#: ../../../CHANGELOG.md:125 +msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)." +msgstr "" + +#: ../../../CHANGELOG.md:127 +msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS." +msgstr "" + +#: ../../../CHANGELOG.md:129 +msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm." +msgstr "" + +#: ../../../CHANGELOG.md:131 +msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS." +msgstr "" + +#: ../../../CHANGELOG.md:134 +msgid "2024-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:136 +msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments" +msgstr "" + +#: ../../../CHANGELOG.md:138 +msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." +msgstr "" + +#: ../../../CHANGELOG.md:140 +msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:142 +msgid "You need to do the following replacements:" +msgstr "" + +#: ../../../CHANGELOG.md:144 +msgid "`devture_postgres_` -> `postgres_`" +msgstr "" + +#: ../../../CHANGELOG.md:145 +msgid "`devture_traefik_` -> `traefik_`" +msgstr "" + +#: ../../../CHANGELOG.md:147 +msgid "As always, the playbook would let you know about this and point out any variables you may have missed." +msgstr "" + +#: ../../../CHANGELOG.md:150 +msgid "2024-09-12" +msgstr "" + +#: ../../../CHANGELOG.md:152 +msgid "Support for baibot" +msgstr "" + +#: ../../../CHANGELOG.md:154 +msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" +msgstr "" + +#: ../../../CHANGELOG.md:156 +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../CHANGELOG.md:158 +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)." +msgstr "" + +#: ../../../CHANGELOG.md:160 +msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:162 +msgid "Switching synapse-admin to etke.cc's fork" +msgstr "" + +#: ../../../CHANGELOG.md:164 +msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software." +msgstr "" + +#: ../../../CHANGELOG.md:166 +msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." +msgstr "" + +#: ../../../CHANGELOG.md:168 +msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now." +msgstr "" + +#: ../../../CHANGELOG.md:170 +msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:183 +msgid "2024-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:185 +msgid "New appservice-double-puppet service for better double-puppeting" +msgstr "" + +#: ../../../CHANGELOG.md:187 +msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post." +msgstr "" + +#: ../../../CHANGELOG.md:189 +msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges." +msgstr "" + +#: ../../../CHANGELOG.md:191 +msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." +msgstr "" + +#: ../../../CHANGELOG.md:193 +msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**." +msgstr "" + +#: ../../../CHANGELOG.md:195 +msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:201 +msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it." +msgstr "" + +#: ../../../CHANGELOG.md:203 +msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it." +msgstr "" + +#: ../../../CHANGELOG.md:206 +msgid "2024-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:208 +msgid "matrix-media-repo now configured for Authenticated Media" +msgstr "" + +#: ../../../CHANGELOG.md:210 +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))." +msgstr "" + +#: ../../../CHANGELOG.md:212 +msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction." +msgstr "" + +#: ../../../CHANGELOG.md:214 +msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details." +msgstr "" + +#: ../../../CHANGELOG.md:216 +msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:219 +msgid "2024-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:221 +msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" +msgstr "" + +#: ../../../CHANGELOG.md:223 +msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))." +msgstr "" + +#: ../../../CHANGELOG.md:225 +msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." +msgstr "" + +#: ../../../CHANGELOG.md:227 +msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:233 +msgid "2024-07-25" +msgstr "" + +#: ../../../CHANGELOG.md:235 +msgid "synapse-usage-exporter support" +msgstr "" + +#: ../../../CHANGELOG.md:237 +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape." +msgstr "" + +#: ../../../CHANGELOG.md:239 +msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:242 +msgid "2024-07-06" +msgstr "" + +#: ../../../CHANGELOG.md:244 +msgid "matrix-alertmanager-receiver support" +msgstr "" + +#: ../../../CHANGELOG.md:246 +msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)." +msgstr "" + +#: ../../../CHANGELOG.md:248 +msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details." +msgstr "" + +#: ../../../CHANGELOG.md:250 +msgid "Traefik v3 and HTTP/3 are here now" +msgstr "" + +#: ../../../CHANGELOG.md:252 +msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it." +msgstr "" + +#: ../../../CHANGELOG.md:254 +msgid "Traefik v3" +msgstr "" + +#: ../../../CHANGELOG.md:256 +msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:258 +msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)." +msgstr "" + +#: ../../../CHANGELOG.md:260 +msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use." +msgstr "" + +#: ../../../CHANGELOG.md:262 +msgid "**Most people using the playbook should not have to do any changes**." +msgstr "" + +#: ../../../CHANGELOG.md:264 +msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgstr "" + +#: ../../../CHANGELOG.md:266 +msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)." +msgstr "" + +#: ../../../CHANGELOG.md:268 +msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand." +msgstr "" + +#: ../../../CHANGELOG.md:270 +msgid "HTTP/3 is enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:272 +msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints." +msgstr "" + +#: ../../../CHANGELOG.md:274 +msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**." +msgstr "" + +#: ../../../CHANGELOG.md:276 +msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." +msgstr "" + +#: ../../../CHANGELOG.md:278 +msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)." +msgstr "" + +#: ../../../CHANGELOG.md:280 +msgid "To **disable HTTP/3**, you can use the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:294 +msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:" +msgstr "" + +#: ../../../CHANGELOG.md:307 +msgid "2024-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:309 +msgid "synapse-admin is now restricted to your homeserver's URL by default" +msgstr "" + +#: ../../../CHANGELOG.md:311 +msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)." +msgstr "" + +#: ../../../CHANGELOG.md:313 +msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore." +msgstr "" + +#: ../../../CHANGELOG.md:315 +msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:323 +msgid "2024-06-25" +msgstr "" + +#: ../../../CHANGELOG.md:325 +msgid "The URL-prefix for Hookshot generic webhooks has changed" +msgstr "" + +#: ../../../CHANGELOG.md:327 +msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`." +msgstr "" + +#: ../../../CHANGELOG.md:329 +msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:331 +msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)." +msgstr "" + +#: ../../../CHANGELOG.md:333 +msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended." +msgstr "" + +#: ../../../CHANGELOG.md:335 +msgid "When generating new webhooks, you should start seeing the new URLs being used." +msgstr "" + +#: ../../../CHANGELOG.md:337 +msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet." +msgstr "" + +#: ../../../CHANGELOG.md:339 +msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs." +msgstr "" + +#: ../../../CHANGELOG.md:342 +msgid "2024-06-22" +msgstr "" + +#: ../../../CHANGELOG.md:344 +msgid "The maubot user is now managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:346 +msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:348 +msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable." +msgstr "" + +#: ../../../CHANGELOG.md:350 +msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)." +msgstr "" + +#: ../../../CHANGELOG.md:353 +msgid "2024-06-03" +msgstr "" + +#: ../../../CHANGELOG.md:355 +msgid "WeChat bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:357 +msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:359 +msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:362 +msgid "2024-03-26" +msgstr "" + +#: ../../../CHANGELOG.md:364 +msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" +msgstr "" + +#: ../../../CHANGELOG.md:366 +msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)." +msgstr "" + +#: ../../../CHANGELOG.md:368 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)." +msgstr "" + +#: ../../../CHANGELOG.md:370 +msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." +msgstr "" + +#: ../../../CHANGELOG.md:372 +msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's." +msgstr "" + +#: ../../../CHANGELOG.md:374 +msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens." +msgstr "" + +#: ../../../CHANGELOG.md:376 +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)." +msgstr "" + +#: ../../../CHANGELOG.md:387 +msgid "2024-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:389 +msgid "Initial work on IPv6 support" +msgstr "" + +#: ../../../CHANGELOG.md:391 +msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." +msgstr "" + +#: ../../../CHANGELOG.md:393 +msgid "It should be noted that:" +msgstr "" + +#: ../../../CHANGELOG.md:395 +msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary" +msgstr "" + +#: ../../../CHANGELOG.md:396 +msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" +msgstr "" + +#: ../../../CHANGELOG.md:397 +msgid "this is all very new and untested" +msgstr "" + +#: ../../../CHANGELOG.md:399 +msgid "Pantalaimon support" +msgstr "" + +#: ../../../CHANGELOG.md:401 +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details." +msgstr "" + +#: ../../../CHANGELOG.md:403 +msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:406 +msgid "2024-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:408 +msgid "Support for Draupnir-for-all" +msgstr "" + +#: ../../../CHANGELOG.md:410 +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)." +msgstr "" + +#: ../../../CHANGELOG.md:412 +msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:414 +msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it." +msgstr "" + +#: ../../../CHANGELOG.md:417 +msgid "2024-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:419 +msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge" +msgstr "" + +#: ../../../CHANGELOG.md:421 +msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:423 +msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time." +msgstr "" + +#: ../../../CHANGELOG.md:425 +msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:" +msgstr "" + +#: ../../../CHANGELOG.md:427 +msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../CHANGELOG.md:429 +msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../CHANGELOG.md:431 +msgid "The documentation pages contain more information on how to migrate." +msgstr "" + +#: ../../../CHANGELOG.md:434 +msgid "2024-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:436 +msgid "Much larger Synapse caches and cache auto-tuning enabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:438 +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." +msgstr "" + +#: ../../../CHANGELOG.md:440 +msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." +msgstr "" + +#: ../../../CHANGELOG.md:442 +msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:444 +msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:445 +msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" +msgstr "" + +#: ../../../CHANGELOG.md:446 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../CHANGELOG.md:448 +msgid "These values should be good defaults for most servers, but may change over time as we experiment further." +msgstr "" + +#: ../../../CHANGELOG.md:450 +msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details." +msgstr "" + +#: ../../../CHANGELOG.md:453 +msgid "2024-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:455 +msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:457 +msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:459 +msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page." +msgstr "" + +#: ../../../CHANGELOG.md:461 +msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:464 +msgid "2024-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:466 +msgid "Support for more efficient (specialized) Synapse workers" +msgstr "" + +#: ../../../CHANGELOG.md:468 +msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation." +msgstr "" + +#: ../../../CHANGELOG.md:470 +msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:472 +msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)." +msgstr "" + +#: ../../../CHANGELOG.md:474 +msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section." +msgstr "" + +#: ../../../CHANGELOG.md:477 +msgid "2024-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:479 +msgid "Switching to Element's AGPLv3-licensed Synapse release" +msgstr "" + +#: ../../../CHANGELOG.md:481 +msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" +msgstr "" + +#: ../../../CHANGELOG.md:483 +msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used" +msgstr "" + +#: ../../../CHANGELOG.md:484 +msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license" +msgstr "" + +#: ../../../CHANGELOG.md:486 +msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation." +msgstr "" + +#: ../../../CHANGELOG.md:488 +msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)." +msgstr "" + +#: ../../../CHANGELOG.md:490 +msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release." +msgstr "" + +#: ../../../CHANGELOG.md:492 +msgid "**What does this mean to you?**" +msgstr "" + +#: ../../../CHANGELOG.md:494 +msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:496 +msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)." +msgstr "" + +#: ../../../CHANGELOG.md:498 +msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!" +msgstr "" + +#: ../../../CHANGELOG.md:500 +msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:" +msgstr "" + +#: ../../../CHANGELOG.md:512 +msgid "Notes:" +msgstr "" + +#: ../../../CHANGELOG.md:514 +msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version" +msgstr "" + +#: ../../../CHANGELOG.md:516 +msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution." +msgstr "" + +#: ../../../CHANGELOG.md:518 +msgid "2024-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:520 +msgid "`Draupnir` has been relicensed to AFL-3.0" +msgstr "" + +#: ../../../CHANGELOG.md:522 +msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change." +msgstr "" + +#: ../../../CHANGELOG.md:524 +msgid "2024-01-15" +msgstr "" + +#: ../../../CHANGELOG.md:526 +msgid "Goodbye, `matrix-nginx-proxy` 🪦" +msgstr "" + +#: ../../../CHANGELOG.md:528 +msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it." +msgstr "" + +#: ../../../CHANGELOG.md:530 +msgid "Backstory on `matrix-nginx-proxy`" +msgstr "" + +#: ../../../CHANGELOG.md:532 +msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago." +msgstr "" + +#: ../../../CHANGELOG.md:534 +msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others." +msgstr "" + +#: ../../../CHANGELOG.md:536 +msgid "To us, `matrix-nginx-proxy` was:" +msgstr "" + +#: ../../../CHANGELOG.md:538 +msgid "an [nginx](https://nginx.org/)-based reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:539 +msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)" +msgstr "" + +#: ../../../CHANGELOG.md:540 +msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime" +msgstr "" + +#: ../../../CHANGELOG.md:541 +msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver" +msgstr "" + +#: ../../../CHANGELOG.md:542 +msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)" +msgstr "" + +#: ../../../CHANGELOG.md:543 +msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)" +msgstr "" + +#: ../../../CHANGELOG.md:544 +msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server" +msgstr "" + +#: ../../../CHANGELOG.md:546 +msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long." +msgstr "" + +#: ../../../CHANGELOG.md:548 +msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." +msgstr "" + +#: ../../../CHANGELOG.md:550 +msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service." +msgstr "" + +#: ../../../CHANGELOG.md:552 +msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:554 +msgid "Going Traefik-native and cutting out all middlemen" +msgstr "" + +#: ../../../CHANGELOG.md:556 +msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." +msgstr "" + +#: ../../../CHANGELOG.md:558 +msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly." +msgstr "" + +#: ../../../CHANGELOG.md:560 +msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime." +msgstr "" + +#: ../../../CHANGELOG.md:562 +msgid "Traefik now has an extra job" +msgstr "" + +#: ../../../CHANGELOG.md:564 +msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job." +msgstr "" + +#: ../../../CHANGELOG.md:566 +msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it." +msgstr "" + +#: ../../../CHANGELOG.md:568 +msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint." +msgstr "" + +#: ../../../CHANGELOG.md:570 +msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service." +msgstr "" + +#: ../../../CHANGELOG.md:572 +msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)." +msgstr "" + +#: ../../../CHANGELOG.md:574 +msgid "Traefik serving this second purpose has a few downsides:" +msgstr "" + +#: ../../../CHANGELOG.md:576 +msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services" +msgstr "" + +#: ../../../CHANGELOG.md:577 +msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure" +msgstr "" + +#: ../../../CHANGELOG.md:579 +msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)." +msgstr "" + +#: ../../../CHANGELOG.md:581 +msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically." +msgstr "" + +#: ../../../CHANGELOG.md:583 +msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below." +msgstr "" + +#: ../../../CHANGELOG.md:585 +msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended." +msgstr "" + +#: ../../../CHANGELOG.md:587 +msgid "People managing their own Traefik instance need to do minor changes" +msgstr "" + +#: ../../../CHANGELOG.md:589 +msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes." +msgstr "" + +#: ../../../CHANGELOG.md:591 +msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details." +msgstr "" + +#: ../../../CHANGELOG.md:593 +msgid "People fronting Traefik with another reverse proxy need to do minor changes" +msgstr "" + +#: ../../../CHANGELOG.md:595 +msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:597 +msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)." +msgstr "" + +#: ../../../CHANGELOG.md:599 +msgid "Supported reverse proxy types are now fewer" +msgstr "" + +#: ../../../CHANGELOG.md:601 +msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)." +msgstr "" + +#: ../../../CHANGELOG.md:603 +msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups." +msgstr "" + +#: ../../../CHANGELOG.md:605 +msgid "The complexity of this is too high, so we only support 3 values right now:" +msgstr "" + +#: ../../../CHANGELOG.md:607 +msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:608 +msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)" +msgstr "" + +#: ../../../CHANGELOG.md:609 +msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)" +msgstr "" + +#: ../../../CHANGELOG.md:611 +msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup." +msgstr "" + +#: ../../../CHANGELOG.md:613 +msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`." +msgstr "" + +#: ../../../CHANGELOG.md:615 +msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:" +msgstr "" + +#: ../../../CHANGELOG.md:617 +msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)" +msgstr "" + +#: ../../../CHANGELOG.md:618 +msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually" +msgstr "" + +#: ../../../CHANGELOG.md:620 +msgid "Container networking changes" +msgstr "" + +#: ../../../CHANGELOG.md:622 +msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt." +msgstr "" + +#: ../../../CHANGELOG.md:624 +msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network." +msgstr "" + +#: ../../../CHANGELOG.md:626 +msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity." +msgstr "" + +#: ../../../CHANGELOG.md:628 +msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things." +msgstr "" + +#: ../../../CHANGELOG.md:630 +msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**." +msgstr "" + +#: ../../../CHANGELOG.md:632 +msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much." +msgstr "" + +#: ../../../CHANGELOG.md:634 +msgid "Metrics exposure changes" +msgstr "" + +#: ../../../CHANGELOG.md:636 +msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server." +msgstr "" + +#: ../../../CHANGELOG.md:638 +msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)." +msgstr "" + +#: ../../../CHANGELOG.md:640 +msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details." +msgstr "" + +#: ../../../CHANGELOG.md:642 +msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason." +msgstr "" + +#: ../../../CHANGELOG.md:644 +msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!" +msgstr "" + +#: ../../../CHANGELOG.md:646 +msgid "Matrix static files" +msgstr "" + +#: ../../../CHANGELOG.md:648 +msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files." +msgstr "" + +#: ../../../CHANGELOG.md:650 +msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)." +msgstr "" + +#: ../../../CHANGELOG.md:652 +msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names." +msgstr "" + +#: ../../../CHANGELOG.md:654 +msgid "A note on performance" +msgstr "" + +#: ../../../CHANGELOG.md:656 +msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better." +msgstr "" + +#: ../../../CHANGELOG.md:658 +msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx." +msgstr "" + +#: ../../../CHANGELOG.md:660 +msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment." +msgstr "" + +#: ../../../CHANGELOG.md:662 +msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front." +msgstr "" + +#: ../../../CHANGELOG.md:664 +msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this." +msgstr "" + +#: ../../../CHANGELOG.md:666 +msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all." +msgstr "" + +#: ../../../CHANGELOG.md:668 +msgid "Migration procedure" +msgstr "" + +#: ../../../CHANGELOG.md:670 +msgid "The updated playbook will automatically perform some migration tasks for you:" +msgstr "" + +#: ../../../CHANGELOG.md:672 +msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests." +msgstr "" + +#: ../../../CHANGELOG.md:674 +msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around." +msgstr "" + +#: ../../../CHANGELOG.md:676 +msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do." +msgstr "" + +#: ../../../CHANGELOG.md:678 +msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:680 +msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:682 +msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file." +msgstr "" + +#: ../../../CHANGELOG.md:684 +msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing." +msgstr "" + +#: ../../../CHANGELOG.md:686 +msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically." +msgstr "" + +#: ../../../CHANGELOG.md:688 +msgid "Conclusion" +msgstr "" + +#: ../../../CHANGELOG.md:690 +msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver." +msgstr "" + +#: ../../../CHANGELOG.md:692 +msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!" +msgstr "" + +#: ../../../CHANGELOG.md:695 +msgid "2024-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:697 +msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:699 +msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:701 +msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:703 +msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so." +msgstr "" + +#: ../../../CHANGELOG.md:705 +msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`." +msgstr "" + +#: ../../../CHANGELOG.md:707 +msgid "Adapt your configuration as seen below:" +msgstr "" + +#: ../../../CHANGELOG.md:740 +msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details." +msgstr "" + +#: ../../../CHANGELOG.md:743 +msgid "2024-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:745 +msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings" +msgstr "" + +#: ../../../CHANGELOG.md:747 +msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do." +msgstr "" + +#: ../../../CHANGELOG.md:749 +msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)." +msgstr "" + +#: ../../../CHANGELOG.md:751 +msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen." +msgstr "" + +#: ../../../CHANGELOG.md:753 +msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders." +msgstr "" + +#: ../../../CHANGELOG.md:755 +msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users." +msgstr "" + +#: ../../../CHANGELOG.md:757 +msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:" +msgstr "" + +#: ../../../CHANGELOG.md:759 +msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere" +msgstr "" + +#: ../../../CHANGELOG.md:761 +msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" +msgstr "" + +#: ../../../CHANGELOG.md:763 +msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" +msgstr "" + +#: ../../../CHANGELOG.md:766 +msgid "2024-01-05" +msgstr "" + +#: ../../../CHANGELOG.md:768 +msgid "matrix-mailer has been replaced by the exim-relay external role" +msgstr "" + +#: ../../../CHANGELOG.md:770 +#: ../../../CHANGELOG.md:1410 +msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use." +msgstr "" + +#: ../../../CHANGELOG.md:772 +msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes." +msgstr "" + +#: ../../../CHANGELOG.md:774 +msgid "To migrate:" +msgstr "" + +#: ../../../CHANGELOG.md:776 +msgid "pull the playbook changes, as usual" +msgstr "" + +#: ../../../CHANGELOG.md:777 +msgid "update your roles (run `just roles` or `make roles`)" +msgstr "" + +#: ../../../CHANGELOG.md:778 +msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler." +msgstr "" + +#: ../../../CHANGELOG.md:779 +msgid "re-run the playbook (`install-all` or `setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:781 +msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)." +msgstr "" + +#: ../../../CHANGELOG.md:784 +msgid "2024-01-02" +msgstr "" + +#: ../../../CHANGELOG.md:786 +msgid "mautrix-signal now powered by the new Go-based bridge" +msgstr "" + +#: ../../../CHANGELOG.md:788 +msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices." +msgstr "" + +#: ../../../CHANGELOG.md:790 +msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." +msgstr "" + +#: ../../../CHANGELOG.md:792 +msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations." +msgstr "" + +#: ../../../CHANGELOG.md:795 +msgid "2023-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:797 +msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:799 +msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected." +msgstr "" + +#: ../../../CHANGELOG.md:801 +msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default." +msgstr "" + +#: ../../../CHANGELOG.md:803 +msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)." +msgstr "" + +#: ../../../CHANGELOG.md:805 +msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member." +msgstr "" + +#: ../../../CHANGELOG.md:807 +msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:809 +msgid "The **historical reasoning** behind this change is as follows:" +msgstr "" + +#: ../../../CHANGELOG.md:811 +msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation." +msgstr "" + +#: ../../../CHANGELOG.md:813 +msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense." +msgstr "" + +#: ../../../CHANGELOG.md:815 +msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful." +msgstr "" + +#: ../../../CHANGELOG.md:817 +msgid "Here are **actions you may wish to take** as a result of this change:" +msgstr "" + +#: ../../../CHANGELOG.md:819 +msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery." +msgstr "" + +#: ../../../CHANGELOG.md:821 +msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them." +msgstr "" + +#: ../../../CHANGELOG.md:823 +msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures." +msgstr "" + +#: ../../../CHANGELOG.md:826 +msgid "2023-10-18" +msgstr "" + +#: ../../../CHANGELOG.md:828 +msgid "Postgres parameters are automatically tuned now" +msgstr "" + +#: ../../../CHANGELOG.md:830 +msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now." +msgstr "" + +#: ../../../CHANGELOG.md:832 +msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/." +msgstr "" + +#: ../../../CHANGELOG.md:834 +msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually." +msgstr "" + +#: ../../../CHANGELOG.md:836 +msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers." +msgstr "" + +#: ../../../CHANGELOG.md:839 +msgid "2023-08-31" +msgstr "" + +#: ../../../CHANGELOG.md:841 +msgid "SchildiChat Web support" +msgstr "" + +#: ../../../CHANGELOG.md:843 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client." +msgstr "" + +#: ../../../CHANGELOG.md:845 +msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:848 +msgid "2023-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:850 +msgid "mautrix-wsproxy support" +msgstr "" + +#: ../../../CHANGELOG.md:852 +msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)." +msgstr "" + +#: ../../../CHANGELOG.md:854 +msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:857 +msgid "2023-07-24" +msgstr "" + +#: ../../../CHANGELOG.md:859 +msgid "matrix-registration-bot usage changed" +msgstr "" + +#: ../../../CHANGELOG.md:861 +msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot." +msgstr "" + +#: ../../../CHANGELOG.md:863 +msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings" +msgstr "" + +#: ../../../CHANGELOG.md:865 +msgid "`matrix_bot_matrix_registration_bot_bot_access_token`" +msgstr "" + +#: ../../../CHANGELOG.md:866 +msgid "`matrix_bot_matrix_registration_bot_api_token`" +msgstr "" + +#: ../../../CHANGELOG.md:869 +msgid "2023-07-21" +msgstr "" + +#: ../../../CHANGELOG.md:871 +msgid "mautrix-gmessages support" +msgstr "" + +#: ../../../CHANGELOG.md:873 +msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:876 +msgid "2023-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:878 +msgid "matrix-media-repo support" +msgstr "" + +#: ../../../CHANGELOG.md:880 +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features." +msgstr "" + +#: ../../../CHANGELOG.md:882 +msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:885 +msgid "2023-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:887 +msgid "Enabling `forget_rooms_on_leave` by default for Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:889 +msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**." +msgstr "" + +#: ../../../CHANGELOG.md:891 +msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving." +msgstr "" + +#: ../../../CHANGELOG.md:893 +msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing." +msgstr "" + +#: ../../../CHANGELOG.md:895 +msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`" +msgstr "" + +#: ../../../CHANGELOG.md:898 +msgid "2023-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:900 +msgid "The matrix-jitsi role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:902 +msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:904 +msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:906 +msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:" +msgstr "" + +#: ../../../CHANGELOG.md:908 +msgid "**native Traefik support** has been added" +msgstr "" + +#: ../../../CHANGELOG.md:909 +msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" +msgstr "" + +#: ../../../CHANGELOG.md:911 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not." +msgstr "" + +#: ../../../CHANGELOG.md:913 +msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:915 +msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:916 +msgid "`matrix_jitsi_` -> `jitsi_`" +msgstr "" + +#: ../../../CHANGELOG.md:917 +#: ../../../CHANGELOG.md:944 +msgid "some other internal variables have changed, but the playbook will tell you about them" +msgstr "" + +#: ../../../CHANGELOG.md:919 +msgid "2023-03-22" +msgstr "" + +#: ../../../CHANGELOG.md:921 +msgid "ntfy Web App is disabled by default" +msgstr "" + +#: ../../../CHANGELOG.md:923 +msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))." +msgstr "" + +#: ../../../CHANGELOG.md:925 +msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))." +msgstr "" + +#: ../../../CHANGELOG.md:928 +msgid "2023-03-21" +msgstr "" + +#: ../../../CHANGELOG.md:930 +msgid "The matrix-prometheus role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:932 +msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:934 +msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." +msgstr "" + +#: ../../../CHANGELOG.md:936 +msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know." +msgstr "" + +#: ../../../CHANGELOG.md:938 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not." +msgstr "" + +#: ../../../CHANGELOG.md:940 +msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:942 +msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:943 +msgid "`matrix_prometheus_` -> `prometheus_`" +msgstr "" + +#: ../../../CHANGELOG.md:947 +msgid "2023-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:949 +msgid "synapse-auto-compressor support" +msgstr "" + +#: ../../../CHANGELOG.md:951 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically." +msgstr "" + +#: ../../../CHANGELOG.md:953 +msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:" +msgstr "" + +#: ../../../CHANGELOG.md:955 +msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" +msgstr "" + +#: ../../../CHANGELOG.md:956 +msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore" +msgstr "" + +#: ../../../CHANGELOG.md:958 +msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations." +msgstr "" + +#: ../../../CHANGELOG.md:960 +msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:963 +msgid "2023-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:965 +msgid "Sliding Sync proxy (Element X) support" +msgstr "" + +#: ../../../CHANGELOG.md:967 +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)." +msgstr "" + +#: ../../../CHANGELOG.md:969 +msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support." +msgstr "" + +#: ../../../CHANGELOG.md:971 +msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:974 +msgid "2023-03-02" +msgstr "" + +#: ../../../CHANGELOG.md:976 +msgid "The matrix-etherpad role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:978 +msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:980 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not." +msgstr "" + +#: ../../../CHANGELOG.md:982 +msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:984 +msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`" +msgstr "" + +#: ../../../CHANGELOG.md:986 +msgid "Replace `matrix_etherpad_mode: dimension` with:" +msgstr "" + +#: ../../../CHANGELOG.md:987 +msgid "for `matrix-nginx-proxy` users:" +msgstr "" + +#: ../../../CHANGELOG.md:988 +msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`" +msgstr "" + +#: ../../../CHANGELOG.md:989 +msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:990 +msgid "for Traefik users:" +msgstr "" + +#: ../../../CHANGELOG.md:991 +msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit" +msgstr "" + +#: ../../../CHANGELOG.md:993 +msgid "Rename all other variables:" +msgstr "" + +#: ../../../CHANGELOG.md:994 +msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`" +msgstr "" + +#: ../../../CHANGELOG.md:995 +msgid "`matrix_etherpad_` -> `etherpad_`" +msgstr "" + +#: ../../../CHANGELOG.md:997 +msgid "Along with this relocation, the new role also:" +msgstr "" + +#: ../../../CHANGELOG.md:999 +msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures" +msgstr "" + +#: ../../../CHANGELOG.md:1000 +msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)" +msgstr "" + +#: ../../../CHANGELOG.md:1003 +msgid "2023-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:1005 +msgid "Traefik is the default reverse-proxy now" +msgstr "" + +#: ../../../CHANGELOG.md:1007 +msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1009 +msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy." +msgstr "" + +#: ../../../CHANGELOG.md:1011 +msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:" +msgstr "" + +#: ../../../CHANGELOG.md:1013 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1014 +msgid "Traefik managed by the user in another way" +msgstr "" + +#: ../../../CHANGELOG.md:1015 +msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1016 +msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)" +msgstr "" + +#: ../../../CHANGELOG.md:1017 +msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1018 +msgid "`nginx` webserver operated by the user, running without a container on the same server" +msgstr "" + +#: ../../../CHANGELOG.md:1020 +msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support." +msgstr "" + +#: ../../../CHANGELOG.md:1022 +msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for." +msgstr "" + +#: ../../../CHANGELOG.md:1024 +msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:" +msgstr "" + +#: ../../../CHANGELOG.md:1026 +msgid "Traefik is now the default reverse-proxy for new installations" +msgstr "" + +#: ../../../CHANGELOG.md:1027 +msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed" +msgstr "" + +#: ../../../CHANGELOG.md:1029 +msgid "How do I switch my existing setup to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1031 +msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)." +msgstr "" + +#: ../../../CHANGELOG.md:1033 +msgid "If you experience trouble:" +msgstr "" + +#: ../../../CHANGELOG.md:1035 +msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy" +msgstr "" + +#: ../../../CHANGELOG.md:1036 +msgid "Ask for help in our [support channels](README.md#support)" +msgstr "" + +#: ../../../CHANGELOG.md:1037 +msgid "Try switching to Traefik again later" +msgstr "" + +#: ../../../CHANGELOG.md:1039 +msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1041 +msgid "I already use my own Traefik server. How do I plug that in?" +msgstr "" + +#: ../../../CHANGELOG.md:1043 +msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section." +msgstr "" + +#: ../../../CHANGELOG.md:1045 +msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" +msgstr "" + +#: ../../../CHANGELOG.md:1047 +msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`." +msgstr "" + +#: ../../../CHANGELOG.md:1049 +msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed." +msgstr "" + +#: ../../../CHANGELOG.md:1051 +msgid "How do I remain on matrix-nginx-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1053 +msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option." +msgstr "" + +#: ../../../CHANGELOG.md:1055 +msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1057 +msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly." +msgstr "" + +#: ../../../CHANGELOG.md:1059 +msgid "How do I keep using my own other reverse-proxy?" +msgstr "" + +#: ../../../CHANGELOG.md:1061 +msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." +msgstr "" + +#: ../../../CHANGELOG.md:1064 +msgid "2023-02-25" +msgstr "" + +#: ../../../CHANGELOG.md:1066 +msgid "rageshake support" +msgstr "" + +#: ../../../CHANGELOG.md:1068 +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server." +msgstr "" + +#: ../../../CHANGELOG.md:1070 +msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1073 +msgid "2023-02-17" +msgstr "" + +#: ../../../CHANGELOG.md:1075 +msgid "Synapse templates customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1077 +msgid "The playbook can now help you customize Synapse's templates." +msgstr "" + +#: ../../../CHANGELOG.md:1079 +msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1081 +msgid "The matrix-redis role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1083 +msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1085 +msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1087 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1089 +msgid "The matrix-ntfy role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1091 +msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1093 +msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1095 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1098 +msgid "2023-02-15" +msgstr "" + +#: ../../../CHANGELOG.md:1100 +msgid "The matrix-grafana role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1102 +msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1104 +msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks." +msgstr "" + +#: ../../../CHANGELOG.md:1106 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1109 +msgid "2023-02-13" +msgstr "" + +#: ../../../CHANGELOG.md:1111 +msgid "The matrix-backup-borg role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1113 +msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1115 +msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon." +msgstr "" + +#: ../../../CHANGELOG.md:1117 +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)." +msgstr "" + +#: ../../../CHANGELOG.md:1120 +msgid "2023-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1122 +msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support" +msgstr "" + +#: ../../../CHANGELOG.md:1124 +msgid "**TLDR**:" +msgstr "" + +#: ../../../CHANGELOG.md:1126 +msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways." +msgstr "" + +#: ../../../CHANGELOG.md:1127 +msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now." +msgstr "" + +#: ../../../CHANGELOG.md:1128 +msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`" +msgstr "" + +#: ../../../CHANGELOG.md:1129 +msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet." +msgstr "" + +#: ../../../CHANGELOG.md:1130 +msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:1132 +msgid "Motivation for redoing our reverse-proxy setup" +msgstr "" + +#: ../../../CHANGELOG.md:1134 +msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**." +msgstr "" + +#: ../../../CHANGELOG.md:1136 +msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**." +msgstr "" + +#: ../../../CHANGELOG.md:1138 +msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else." +msgstr "" + +#: ../../../CHANGELOG.md:1140 +msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1142 +msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:" +msgstr "" + +#: ../../../CHANGELOG.md:1144 +msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)" +msgstr "" + +#: ../../../CHANGELOG.md:1145 +msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)." +msgstr "" + +#: ../../../CHANGELOG.md:1147 +msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations." +msgstr "" + +#: ../../../CHANGELOG.md:1149 +msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)." +msgstr "" + +#: ../../../CHANGELOG.md:1151 +msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:" +msgstr "" + +#: ../../../CHANGELOG.md:1153 +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager" +msgstr "" + +#: ../../../CHANGELOG.md:1154 +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service" +msgstr "" + +#: ../../../CHANGELOG.md:1155 +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform" +msgstr "" + +#: ../../../CHANGELOG.md:1157 +msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy." +msgstr "" + +#: ../../../CHANGELOG.md:1159 +msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1161 +msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with." +msgstr "" + +#: ../../../CHANGELOG.md:1163 +msgid "How do these changes fix all these problems?" +msgstr "" + +#: ../../../CHANGELOG.md:1165 +msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now." +msgstr "" + +#: ../../../CHANGELOG.md:1167 +msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services." +msgstr "" + +#: ../../../CHANGELOG.md:1169 +msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers." +msgstr "" + +#: ../../../CHANGELOG.md:1171 +msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1173 +msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release." +msgstr "" + +#: ../../../CHANGELOG.md:1175 +msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is." +msgstr "" + +#: ../../../CHANGELOG.md:1177 +msgid "Where we're at right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1179 +msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`." +msgstr "" + +#: ../../../CHANGELOG.md:1181 +msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected." +msgstr "" + +#: ../../../CHANGELOG.md:1183 +msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`." +msgstr "" + +#: ../../../CHANGELOG.md:1185 +msgid "How do I explicitly switch to Traefik right now?" +msgstr "" + +#: ../../../CHANGELOG.md:1187 +msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1195 +msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed." +msgstr "" + +#: ../../../CHANGELOG.md:1197 +msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble." +msgstr "" + +#: ../../../CHANGELOG.md:1199 +msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often." +msgstr "" + +#: ../../../CHANGELOG.md:1201 +msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time." +msgstr "" + +#: ../../../CHANGELOG.md:1203 +msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool." +msgstr "" + +#: ../../../CHANGELOG.md:1205 +msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience." +msgstr "" + +#: ../../../CHANGELOG.md:1207 +msgid "Where we're going in the near future?" +msgstr "" + +#: ../../../CHANGELOG.md:1209 +msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point." +msgstr "" + +#: ../../../CHANGELOG.md:1211 +msgid "For now, `matrix-nginx-proxy` will stay around." +msgstr "" + +#: ../../../CHANGELOG.md:1213 +msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight." +msgstr "" + +#: ../../../CHANGELOG.md:1215 +msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:" +msgstr "" + +#: ../../../CHANGELOG.md:1217 +msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well." +msgstr "" + +#: ../../../CHANGELOG.md:1218 +msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)." +msgstr "" + +#: ../../../CHANGELOG.md:1220 +msgid "How do I help?" +msgstr "" + +#: ../../../CHANGELOG.md:1222 +msgid "You can help by:" +msgstr "" + +#: ../../../CHANGELOG.md:1224 +msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles" +msgstr "" + +#: ../../../CHANGELOG.md:1226 +msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)." +msgstr "" + +#: ../../../CHANGELOG.md:1228 +msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server" +msgstr "" + +#: ../../../CHANGELOG.md:1231 +msgid "2023-02-10" +msgstr "" + +#: ../../../CHANGELOG.md:1233 +msgid "Matrix Authentication Support for Jitsi" +msgstr "" + +#: ../../../CHANGELOG.md:1235 +msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))." +msgstr "" + +#: ../../../CHANGELOG.md:1237 +msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)." +msgstr "" + +#: ../../../CHANGELOG.md:1239 +msgid "Draupnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:1241 +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer." +msgstr "" + +#: ../../../CHANGELOG.md:1243 +msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1246 +msgid "2023-02-05" +msgstr "" + +#: ../../../CHANGELOG.md:1248 +msgid "The matrix-prometheus-postgres-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1250 +msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1252 +msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1254 +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1256 +msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1258 +#: ../../../CHANGELOG.md:1300 +msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily." +msgstr "" + +#: ../../../CHANGELOG.md:1261 +msgid "2023-01-26" +msgstr "" + +#: ../../../CHANGELOG.md:1263 +msgid "Coturn can now use host-networking" +msgstr "" + +#: ../../../CHANGELOG.md:1265 +msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown." +msgstr "" + +#: ../../../CHANGELOG.md:1267 +msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1273 +msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself." +msgstr "" + +#: ../../../CHANGELOG.md:1275 +msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network." +msgstr "" + +#: ../../../CHANGELOG.md:1277 +msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues" +msgstr "" + +#: ../../../CHANGELOG.md:1279 +msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it." +msgstr "" + +#: ../../../CHANGELOG.md:1281 +msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better." +msgstr "" + +#: ../../../CHANGELOG.md:1283 +msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it." +msgstr "" + +#: ../../../CHANGELOG.md:1285 +msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people." +msgstr "" + +#: ../../../CHANGELOG.md:1288 +msgid "2023-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:1290 +msgid "The matrix-prometheus-node-exporter role lives independently now" +msgstr "" + +#: ../../../CHANGELOG.md:1292 +msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1294 +msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter" +msgstr "" + +#: ../../../CHANGELOG.md:1296 +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." +msgstr "" + +#: ../../../CHANGELOG.md:1298 +msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)" +msgstr "" + +#: ../../../CHANGELOG.md:1303 +msgid "2023-01-13" +msgstr "" + +#: ../../../CHANGELOG.md:1305 +msgid "Support for running commands via just" +msgstr "" + +#: ../../../CHANGELOG.md:1307 +msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands." +msgstr "" + +#: ../../../CHANGELOG.md:1309 +msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same." +msgstr "" + +#: ../../../CHANGELOG.md:1311 +msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:" +msgstr "" + +#: ../../../CHANGELOG.md:1313 +msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command" +msgstr "" + +#: ../../../CHANGELOG.md:1314 +msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)" +msgstr "" + +#: ../../../CHANGELOG.md:1315 +msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags" +msgstr "" + +#: ../../../CHANGELOG.md:1316 +msgid "`just start-all` - (re-)starts all services" +msgstr "" + +#: ../../../CHANGELOG.md:1317 +msgid "`just stop-group postgres` - to stop only the Postgres service" +msgstr "" + +#: ../../../CHANGELOG.md:1318 +msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" +msgstr "" + +#: ../../../CHANGELOG.md:1320 +msgid "Additional helpful commands and shortcuts may be defined in the future." +msgstr "" + +#: ../../../CHANGELOG.md:1322 +msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually." +msgstr "" + +#: ../../../CHANGELOG.md:1325 +msgid "2023-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:1327 +msgid "mautrix-slack support" +msgstr "" + +#: ../../../CHANGELOG.md:1329 +msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1331 +msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1334 +msgid "2023-01-10" +msgstr "" + +#: ../../../CHANGELOG.md:1336 +msgid "ChatGPT support" +msgstr "" + +#: ../../../CHANGELOG.md:1338 +msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model." +msgstr "" + +#: ../../../CHANGELOG.md:1340 +msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1343 +msgid "2022-11-30" +msgstr "" + +#: ../../../CHANGELOG.md:1345 +msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role" +msgstr "" + +#: ../../../CHANGELOG.md:1347 +msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)." +msgstr "" + +#: ../../../CHANGELOG.md:1349 +msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1352 +msgid "2022-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:1354 +msgid "matrix-postgres has been replaced by the ansible-role-postgres external role" +msgstr "" + +#: ../../../CHANGELOG.md:1356 +msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." +msgstr "" + +#: ../../../CHANGELOG.md:1358 +msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability." +msgstr "" + +#: ../../../CHANGELOG.md:1360 +msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:" +msgstr "" + +#: ../../../CHANGELOG.md:1362 +msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)" +msgstr "" + +#: ../../../CHANGELOG.md:1363 +msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one" +msgstr "" + +#: ../../../CHANGELOG.md:1365 +msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:1367 +msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." +msgstr "" + +#: ../../../CHANGELOG.md:1369 +msgid "The playbook no longer installs scripts to /usr/local/bin" +msgstr "" + +#: ../../../CHANGELOG.md:1371 +msgid "The locations of various scripts installed by the playbook have changed." +msgstr "" + +#: ../../../CHANGELOG.md:1373 +msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:" +msgstr "" + +#: ../../../CHANGELOG.md:1375 +msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`" +msgstr "" + +#: ../../../CHANGELOG.md:1376 +msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1377 +msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`" +msgstr "" + +#: ../../../CHANGELOG.md:1378 +msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`" +msgstr "" + +#: ../../../CHANGELOG.md:1381 +msgid "2022-11-25" +msgstr "" + +#: ../../../CHANGELOG.md:1383 +msgid "2x-5x performance improvements in playbook runtime" +msgstr "" + +#: ../../../CHANGELOG.md:1385 +msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster." +msgstr "" + +#: ../../../CHANGELOG.md:1387 +msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience." +msgstr "" + +#: ../../../CHANGELOG.md:1389 +msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources." +msgstr "" + +#: ../../../CHANGELOG.md:1391 +msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):" +msgstr "" + +#: ../../../CHANGELOG.md:1393 +msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**." +msgstr "" + +#: ../../../CHANGELOG.md:1395 +msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**." +msgstr "" + +#: ../../../CHANGELOG.md:1397 +msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1399 +msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:1402 +msgid "2022-11-22" +msgstr "" + +#: ../../../CHANGELOG.md:1404 +msgid "Automatic `matrix_architecture` determination" +msgstr "" + +#: ../../../CHANGELOG.md:1406 +msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1408 +msgid "Docker and the Docker SDK for Python are now installed via external roles" +msgstr "" + +#: ../../../CHANGELOG.md:1412 +msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1414 +msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:1416 +msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects." +msgstr "" + +#: ../../../CHANGELOG.md:1418 +msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles." +msgstr "" + +#: ../../../CHANGELOG.md:1421 +msgid "2022-11-20" +msgstr "" + +#: ../../../CHANGELOG.md:1423 +msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service" +msgstr "" + +#: ../../../CHANGELOG.md:1425 +msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below." +msgstr "" + +#: ../../../CHANGELOG.md:1427 +msgid "Background" +msgstr "" + +#: ../../../CHANGELOG.md:1429 +msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1431 +msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)." +msgstr "" + +#: ../../../CHANGELOG.md:1433 +msgid "Solution" +msgstr "" + +#: ../../../CHANGELOG.md:1435 +msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:" +msgstr "" + +#: ../../../CHANGELOG.md:1437 +msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1439 +msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)" +msgstr "" + +#: ../../../CHANGELOG.md:1440 +msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1441 +msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic" +msgstr "" + +#: ../../../CHANGELOG.md:1443 +msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers" +msgstr "" + +#: ../../../CHANGELOG.md:1445 +msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled" +msgstr "" + +#: ../../../CHANGELOG.md:1447 +msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1449 +msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))." +msgstr "" + +#: ../../../CHANGELOG.md:1451 +msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service." +msgstr "" + +#: ../../../CHANGELOG.md:1453 +msgid "Webserver configuration" +msgstr "" + +#: ../../../CHANGELOG.md:1455 +msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything" +msgstr "" + +#: ../../../CHANGELOG.md:1457 +msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work" +msgstr "" + +#: ../../../CHANGELOG.md:1459 +msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead" +msgstr "" + +#: ../../../CHANGELOG.md:1461 +msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead" +msgstr "" + +#: ../../../CHANGELOG.md:1463 +msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler." +msgstr "" + +#: ../../../CHANGELOG.md:1466 +msgid "2022-11-05" +msgstr "" + +#: ../../../CHANGELOG.md:1468 +msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad" +msgstr "" + +#: ../../../CHANGELOG.md:1470 +msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)." +msgstr "" + +#: ../../../CHANGELOG.md:1472 +msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)." +msgstr "" + +#: ../../../CHANGELOG.md:1474 +msgid "If you've already got both Etherpad and Dimension in use you could:" +msgstr "" + +#: ../../../CHANGELOG.md:1476 +msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary." +msgstr "" + +#: ../../../CHANGELOG.md:1478 +msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode" +msgstr "" + +#: ../../../CHANGELOG.md:1481 +msgid "2022-11-04" +msgstr "" + +#: ../../../CHANGELOG.md:1483 +msgid "The playbook now uses external roles for some things" +msgstr "" + +#: ../../../CHANGELOG.md:1485 +msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work." +msgstr "" + +#: ../../../CHANGELOG.md:1487 +msgid "We're in the process of trimming the playbook and making it reuse Ansible roles." +msgstr "" + +#: ../../../CHANGELOG.md:1489 +msgid "Starting now, the playbook is composed of 2 types of Ansible roles:" +msgstr "" + +#: ../../../CHANGELOG.md:1491 +msgid "those that live within the playbook itself (`roles/custom/*`)" +msgstr "" + +#: ../../../CHANGELOG.md:1493 +msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community." +msgstr "" + +#: ../../../CHANGELOG.md:1495 +msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." +msgstr "" + +#: ../../../CHANGELOG.md:1497 +msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1499 +msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`." +msgstr "" + +#: ../../../CHANGELOG.md:1502 +msgid "2022-10-14" +msgstr "" + +#: ../../../CHANGELOG.md:1504 +msgid "synapse-s3-storage-provider support" +msgstr "" + +#: ../../../CHANGELOG.md:1506 +msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**" +msgstr "" + +#: ../../../CHANGELOG.md:1508 +msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)." +msgstr "" + +#: ../../../CHANGELOG.md:1510 +msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`." +msgstr "" + +#: ../../../CHANGELOG.md:1512 +msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1514 +msgid "Synapse container image customization support" +msgstr "" + +#: ../../../CHANGELOG.md:1516 +msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." +msgstr "" + +#: ../../../CHANGELOG.md:1518 +msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image." +msgstr "" + +#: ../../../CHANGELOG.md:1520 +msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:" +msgstr "" + +#: ../../../CHANGELOG.md:1531 +msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower." +msgstr "" + +#: ../../../CHANGELOG.md:1533 +msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch." +msgstr "" + +#: ../../../CHANGELOG.md:1536 +msgid "2022-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:1538 +msgid "matrix-ldap-registration-proxy support" +msgstr "" + +#: ../../../CHANGELOG.md:1540 +msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../CHANGELOG.md:1542 +msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1545 +msgid "2022-09-15" +msgstr "" + +#: ../../../CHANGELOG.md:1547 +msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers" +msgstr "" + +#: ../../../CHANGELOG.md:1549 +msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:" +msgstr "" + +#: ../../../CHANGELOG.md:1551 +msgid "we've added support for [Stream writers](#stream-writers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1552 +msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1553 +msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)" +msgstr "" + +#: ../../../CHANGELOG.md:1554 +msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)" +msgstr "" + +#: ../../../CHANGELOG.md:1555 +msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1556 +msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)" +msgstr "" + +#: ../../../CHANGELOG.md:1557 +msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" +msgstr "" + +#: ../../../CHANGELOG.md:1558 +msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)" +msgstr "" + +#: ../../../CHANGELOG.md:1560 +msgid "Stream writers support" +msgstr "" + +#: ../../../CHANGELOG.md:1562 +msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes." +msgstr "" + +#: ../../../CHANGELOG.md:1564 +msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers." +msgstr "" + +#: ../../../CHANGELOG.md:1566 +msgid "If you'd like to customize the number of workers we also make that possible using these variables:" +msgstr "" + +#: ../../../CHANGELOG.md:1579 +msgid "Multiple federation sender workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1581 +msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic." +msgstr "" + +#: ../../../CHANGELOG.md:1583 +msgid "Multiple pusher workers support" +msgstr "" + +#: ../../../CHANGELOG.md:1585 +msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out." +msgstr "" + +#: ../../../CHANGELOG.md:1587 +msgid "Background tasks can run on a worker" +msgstr "" + +#: ../../../CHANGELOG.md:1589 +msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." +msgstr "" + +#: ../../../CHANGELOG.md:1591 +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1593 +msgid "Appservice worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1595 +msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1597 +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1599 +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1601 +msgid "User Directory worker support is back" +msgstr "" + +#: ../../../CHANGELOG.md:1603 +msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." +msgstr "" + +#: ../../../CHANGELOG.md:1605 +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this." +msgstr "" + +#: ../../../CHANGELOG.md:1607 +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:1609 +msgid "Using more than 1 media repository worker is now more reliable" +msgstr "" + +#: ../../../CHANGELOG.md:1611 +msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker." +msgstr "" + +#: ../../../CHANGELOG.md:1613 +msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are." +msgstr "" + +#: ../../../CHANGELOG.md:1615 +msgid "Potential Backward Incompatibilities after these Synapse worker changes" +msgstr "" + +#: ../../../CHANGELOG.md:1617 +msgid "Below we'll discuss **potential backward incompatibilities**." +msgstr "" + +#: ../../../CHANGELOG.md:1619 +msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically." +msgstr "" + +#: ../../../CHANGELOG.md:1621 +msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables." +msgstr "" + +#: ../../../CHANGELOG.md:1623 +msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though." +msgstr "" + +#: ../../../CHANGELOG.md:1625 +msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong." +msgstr "" + +#: ../../../CHANGELOG.md:1628 +msgid "2022-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:1630 +msgid "Cactus Comments support" +msgstr "" + +#: ../../../CHANGELOG.md:1632 +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix." +msgstr "" + +#: ../../../CHANGELOG.md:1634 +msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1637 +msgid "2022-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:1639 +msgid "Postmoogle email bridge support" +msgstr "" + +#: ../../../CHANGELOG.md:1641 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving." +msgstr "" + +#: ../../../CHANGELOG.md:1643 +msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1646 +msgid "2022-08-10" +msgstr "" + +#: ../../../CHANGELOG.md:1648 +msgid "mautrix-whatsapp default configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:1650 +msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge." +msgstr "" + +#: ../../../CHANGELOG.md:1652 +msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:1654 +msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it." +msgstr "" + +#: ../../../CHANGELOG.md:1657 +msgid "2022-08-09" +msgstr "" + +#: ../../../CHANGELOG.md:1659 +msgid "Conduit support" +msgstr "" + +#: ../../../CHANGELOG.md:1661 +msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year." +msgstr "" + +#: ../../../CHANGELOG.md:1663 +msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1665 +msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1671 +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1674 +msgid "2022-07-29" +msgstr "" + +#: ../../../CHANGELOG.md:1676 +msgid "mautrix-discord support" +msgstr "" + +#: ../../../CHANGELOG.md:1678 +msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:1680 +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:1683 +msgid "2022-07-27" +msgstr "" + +#: ../../../CHANGELOG.md:1685 +msgid "matrix-appservice-kakaotalk support" +msgstr "" + +#: ../../../CHANGELOG.md:1687 +msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!" +msgstr "" + +#: ../../../CHANGELOG.md:1689 +msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1692 +msgid "2022-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:1694 +msgid "maubot support" +msgstr "" + +#: ../../../CHANGELOG.md:1696 +msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system." +msgstr "" + +#: ../../../CHANGELOG.md:1698 +msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1701 +msgid "2022-07-14" +msgstr "" + +#: ../../../CHANGELOG.md:1703 +msgid "mx-puppet-skype removal" +msgstr "" + +#: ../../../CHANGELOG.md:1705 +msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration." +msgstr "" + +#: ../../../CHANGELOG.md:1707 +msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:" +msgstr "" + +#: ../../../CHANGELOG.md:1709 +msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references" +msgstr "" + +#: ../../../CHANGELOG.md:1710 +msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1711 +msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1712 +msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1713 +msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)" +msgstr "" + +#: ../../../CHANGELOG.md:1715 +msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1717 +msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal." +msgstr "" + +#: ../../../CHANGELOG.md:1719 +msgid "signald (0.19.0+) upgrade requires data migration" +msgstr "" + +#: ../../../CHANGELOG.md:1721 +msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." +msgstr "" + +#: ../../../CHANGELOG.md:1723 +msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)." +msgstr "" + +#: ../../../CHANGELOG.md:1725 +msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded." +msgstr "" + +#: ../../../CHANGELOG.md:1727 +msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition." +msgstr "" + +#: ../../../CHANGELOG.md:1729 +msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!" +msgstr "" + +#: ../../../CHANGELOG.md:1732 +msgid "2022-07-05" +msgstr "" + +#: ../../../CHANGELOG.md:1734 +msgid "Ntfy push notifications support" +msgstr "" + +#: ../../../CHANGELOG.md:1736 +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you." +msgstr "" + +#: ../../../CHANGELOG.md:1738 +msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1741 +msgid "2022-06-23" +msgstr "" + +#: ../../../CHANGELOG.md:1743 +msgid "(Potential Backward Compatibility Break) Changes around metrics collection" +msgstr "" + +#: ../../../CHANGELOG.md:1745 +msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below." +msgstr "" + +#: ../../../CHANGELOG.md:1747 +msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)." +msgstr "" + +#: ../../../CHANGELOG.md:1749 +msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`." +msgstr "" + +#: ../../../CHANGELOG.md:1751 +msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1752 +msgid "**Metrics may not be enabled by default anymore**:" +msgstr "" + +#: ../../../CHANGELOG.md:1753 +msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network." +msgstr "" + +#: ../../../CHANGELOG.md:1754 +msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below." +msgstr "" + +#: ../../../CHANGELOG.md:1755 +msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:1756 +msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`." +msgstr "" + +#: ../../../CHANGELOG.md:1758 +msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1760 +msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`." +msgstr "" + +#: ../../../CHANGELOG.md:1762 +msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:" +msgstr "" + +#: ../../../CHANGELOG.md:1764 +msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them." +msgstr "" + +#: ../../../CHANGELOG.md:1765 +msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation" +msgstr "" + +#: ../../../CHANGELOG.md:1766 +msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`" +msgstr "" + +#: ../../../CHANGELOG.md:1767 +msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)." +msgstr "" + +#: ../../../CHANGELOG.md:1769 +msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now." +msgstr "" + +#: ../../../CHANGELOG.md:1771 +msgid "2022-06-13" +msgstr "" + +#: ../../../CHANGELOG.md:1773 +msgid "go-skype-bridge bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1775 +msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." +msgstr "" + +#: ../../../CHANGELOG.md:1777 +msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1779 +msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." +msgstr "" + +#: ../../../CHANGELOG.md:1782 +msgid "2022-06-09" +msgstr "" + +#: ../../../CHANGELOG.md:1784 +msgid "Running Ansible in a container can now happen on the Matrix server itself" +msgstr "" + +#: ../../../CHANGELOG.md:1786 +msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)." +msgstr "" + +#: ../../../CHANGELOG.md:1789 +msgid "2022-05-31" +msgstr "" + +#: ../../../CHANGELOG.md:1791 +msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:1793 +msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted." +msgstr "" + +#: ../../../CHANGELOG.md:1795 +msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky." +msgstr "" + +#: ../../../CHANGELOG.md:1797 +msgid "**If Synapse fails to start** after your next playbook run, you'll need to:" +msgstr "" + +#: ../../../CHANGELOG.md:1799 +msgid "SSH into the Matrix server" +msgstr "" + +#: ../../../CHANGELOG.md:1800 +msgid "launch `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:1801 +msgid "switch to the `synapse` database: `\\c synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:1802 +msgid "run the following SQL query:" +msgstr "" + +#: ../../../CHANGELOG.md:1821 +msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`" +msgstr "" + +#: ../../../CHANGELOG.md:1824 +msgid "2022-04-25" +msgstr "" + +#: ../../../CHANGELOG.md:1826 +msgid "Buscarron bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1828 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../CHANGELOG.md:1830 +msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1833 +msgid "2022-04-21" +msgstr "" + +#: ../../../CHANGELOG.md:1835 +msgid "matrix-registration-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1837 +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1839 +msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1842 +msgid "2022-04-19" +msgstr "" + +#: ../../../CHANGELOG.md:1844 +msgid "BorgBackup support" +msgstr "" + +#: ../../../CHANGELOG.md:1846 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server." +msgstr "" + +#: ../../../CHANGELOG.md:1848 +msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1850 +msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1852 +msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:" +msgstr "" + +#: ../../../CHANGELOG.md:1854 +msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs." +msgstr "" + +#: ../../../CHANGELOG.md:1856 +msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care." +msgstr "" + +#: ../../../CHANGELOG.md:1858 +msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:" +msgstr "" + +#: ../../../CHANGELOG.md:1860 +msgid "Pull the latest playbook changes" +msgstr "" + +#: ../../../CHANGELOG.md:1861 +msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:1862 +msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)" +msgstr "" + +#: ../../../CHANGELOG.md:1863 +msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1864 +msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)" +msgstr "" + +#: ../../../CHANGELOG.md:1865 +msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough." +msgstr "" + +#: ../../../CHANGELOG.md:1866 +msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you" +msgstr "" + +#: ../../../CHANGELOG.md:1869 +msgid "2022-04-14" +msgstr "" + +#: ../../../CHANGELOG.md:1871 +msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action" +msgstr "" + +#: ../../../CHANGELOG.md:1873 +msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server." +msgstr "" + +#: ../../../CHANGELOG.md:1875 +msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)." +msgstr "" + +#: ../../../CHANGELOG.md:1877 +msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories." +msgstr "" + +#: ../../../CHANGELOG.md:1879 +msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`" +msgstr "" + +#: ../../../CHANGELOG.md:1882 +msgid "2022-03-17" +msgstr "" + +#: ../../../CHANGELOG.md:1884 +msgid "(Compatibility Break) ma1sd identity server no longer installed by default" +msgstr "" + +#: ../../../CHANGELOG.md:1886 +msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:1888 +msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks." +msgstr "" + +#: ../../../CHANGELOG.md:1890 +msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd." +msgstr "" + +#: ../../../CHANGELOG.md:1892 +msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:1899 +msgid "2022-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:1901 +msgid "matrix_encryption_disabler support" +msgstr "" + +#: ../../../CHANGELOG.md:1903 +msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)." +msgstr "" + +#: ../../../CHANGELOG.md:1905 +msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:1908 +msgid "2022-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:1910 +msgid "matrix-hookshot bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:1912 +msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1915 +msgid "2022-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:1917 +msgid "ARM support for matrix-corporal" +msgstr "" + +#: ../../../CHANGELOG.md:1919 +msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures." +msgstr "" + +#: ../../../CHANGELOG.md:1922 +msgid "2022-01-07" +msgstr "" + +#: ../../../CHANGELOG.md:1924 +msgid "Dendrite support" +msgstr "" + +#: ../../../CHANGELOG.md:1926 +msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)." +msgstr "" + +#: ../../../CHANGELOG.md:1928 +msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing." +msgstr "" + +#: ../../../CHANGELOG.md:1930 +msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" +msgstr "" + +#: ../../../CHANGELOG.md:1932 +msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time." +msgstr "" + +#: ../../../CHANGELOG.md:1934 +msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)." +msgstr "" + +#: ../../../CHANGELOG.md:1936 +msgid "Adapting the configuration for existing Synapse installations" +msgstr "" + +#: ../../../CHANGELOG.md:1938 +msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date." +msgstr "" + +#: ../../../CHANGELOG.md:1940 +msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:" +msgstr "" + +#: ../../../CHANGELOG.md:1952 +msgid "Trying out Dendrite" +msgstr "" + +#: ../../../CHANGELOG.md:1954 +msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:1960 +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss." +msgstr "" + +#: ../../../CHANGELOG.md:1962 +msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!" +msgstr "" + +#: ../../../CHANGELOG.md:1964 +msgid "Honoroit bot support" +msgstr "" + +#: ../../../CHANGELOG.md:1966 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." +msgstr "" + +#: ../../../CHANGELOG.md:1968 +msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:1971 +msgid "2022-01-06" +msgstr "" + +#: ../../../CHANGELOG.md:1973 +msgid "Cinny support" +msgstr "" + +#: ../../../CHANGELOG.md:1975 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client." +msgstr "" + +#: ../../../CHANGELOG.md:1977 +msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:1979 +msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1982 +msgid "2021-12-22" +msgstr "" + +#: ../../../CHANGELOG.md:1984 +msgid "Twitter bridging support via mautrix-twitter" +msgstr "" + +#: ../../../CHANGELOG.md:1986 +msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1989 +msgid "2021-12-14" +msgstr "" + +#: ../../../CHANGELOG.md:1991 +msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability" +msgstr "" + +#: ../../../CHANGELOG.md:1993 +msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable." +msgstr "" + +#: ../../../CHANGELOG.md:1995 +msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:1998 +msgid "2021-11-11" +msgstr "" + +#: ../../../CHANGELOG.md:2000 +msgid "Dropped support for Postgres v9.6" +msgstr "" + +#: ../../../CHANGELOG.md:2002 +msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version." +msgstr "" + +#: ../../../CHANGELOG.md:2004 +msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2007 +msgid "2021-10-23" +msgstr "" + +#: ../../../CHANGELOG.md:2009 +msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2011 +msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it." +msgstr "" + +#: ../../../CHANGELOG.md:2013 +msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2016 +msgid "2021-08-23" +msgstr "" + +#: ../../../CHANGELOG.md:2018 +msgid "LinkedIn bridging support via beeper-linkedin" +msgstr "" + +#: ../../../CHANGELOG.md:2020 +msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." +msgstr "" + +#: ../../../CHANGELOG.md:2022 +msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2024 +msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2027 +msgid "2021-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:2029 +msgid "Sygnal upgraded - ARM support and no longer requires a database" +msgstr "" + +#: ../../../CHANGELOG.md:2031 +msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`." +msgstr "" + +#: ../../../CHANGELOG.md:2033 +msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement." +msgstr "" + +#: ../../../CHANGELOG.md:2035 +msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2037 +msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit." +msgstr "" + +#: ../../../CHANGELOG.md:2040 +msgid "2021-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:2042 +msgid "Hydrogen support" +msgstr "" + +#: ../../../CHANGELOG.md:2044 +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support." +msgstr "" + +#: ../../../CHANGELOG.md:2046 +msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2048 +msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2051 +msgid "2021-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2053 +msgid "Heisenbridge support" +msgstr "" + +#: ../../../CHANGELOG.md:2055 +msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2057 +msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2060 +msgid "2021-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:2062 +msgid "Disabling TLSv1 and TLSv1.1 for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:2064 +msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2066 +msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:2074 +msgid "2021-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2076 +msgid "Automated local Postgres backup support" +msgstr "" + +#: ../../../CHANGELOG.md:2078 +msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)." +msgstr "" + +#: ../../../CHANGELOG.md:2080 +msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2083 +msgid "2021-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2085 +msgid "Mjolnir moderation tool (bot) support" +msgstr "" + +#: ../../../CHANGELOG.md:2087 +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2089 +msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2092 +msgid "2021-03-20" +msgstr "" + +#: ../../../CHANGELOG.md:2094 +msgid "Sygnal push gateway support" +msgstr "" + +#: ../../../CHANGELOG.md:2096 +msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." +msgstr "" + +#: ../../../CHANGELOG.md:2098 +msgid "This is only useful to people who develop/build their own Matrix client applications." +msgstr "" + +#: ../../../CHANGELOG.md:2100 +msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2103 +msgid "2021-03-16" +msgstr "" + +#: ../../../CHANGELOG.md:2105 +msgid "Go-NEB support" +msgstr "" + +#: ../../../CHANGELOG.md:2107 +msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." +msgstr "" + +#: ../../../CHANGELOG.md:2109 +msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2112 +msgid "2021-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:2114 +msgid "GroupMe bridging support via mx-puppet-groupme" +msgstr "" + +#: ../../../CHANGELOG.md:2116 +msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." +msgstr "" + +#: ../../../CHANGELOG.md:2118 +msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." +msgstr "" + +#: ../../../CHANGELOG.md:2120 +msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs." +msgstr "" + +#: ../../../CHANGELOG.md:2122 +msgid "Mautrix Instagram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2124 +msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)." +msgstr "" + +#: ../../../CHANGELOG.md:2126 +msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2128 +msgid "Synapse workers support" +msgstr "" + +#: ../../../CHANGELOG.md:2130 +msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed." +msgstr "" + +#: ../../../CHANGELOG.md:2132 +msgid "Having support for workers makes the playbook suitable for larger homeserver deployments." +msgstr "" + +#: ../../../CHANGELOG.md:2134 +msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." +msgstr "" + +#: ../../../CHANGELOG.md:2136 +msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)." +msgstr "" + +#: ../../../CHANGELOG.md:2138 +msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2141 +msgid "2021-02-12" +msgstr "" + +#: ../../../CHANGELOG.md:2143 +msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana" +msgstr "" + +#: ../../../CHANGELOG.md:2145 +msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI." +msgstr "" + +#: ../../../CHANGELOG.md:2147 +msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page." +msgstr "" + +#: ../../../CHANGELOG.md:2149 +msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." +msgstr "" + +#: ../../../CHANGELOG.md:2152 +msgid "2021-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:2154 +msgid "Etherpad support" +msgstr "" + +#: ../../../CHANGELOG.md:2156 +msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager." +msgstr "" + +#: ../../../CHANGELOG.md:2158 +msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2161 +msgid "2021-01-22" +msgstr "" + +#: ../../../CHANGELOG.md:2163 +msgid "(Breaking Change) Postgres changes that require manual intervention" +msgstr "" + +#: ../../../CHANGELOG.md:2165 +msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle." +msgstr "" + +#: ../../../CHANGELOG.md:2167 +msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required." +msgstr "" + +#: ../../../CHANGELOG.md:2169 +msgid "Why?" +msgstr "" + +#: ../../../CHANGELOG.md:2171 +msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:" +msgstr "" + +#: ../../../CHANGELOG.md:2172 +msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2173 +msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2174 +msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" +msgstr "" + +#: ../../../CHANGELOG.md:2175 +msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2176 +msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2178 +msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:2180 +msgid "What has really changed?" +msgstr "" + +#: ../../../CHANGELOG.md:2182 +msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)" +msgstr "" + +#: ../../../CHANGELOG.md:2183 +msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" +msgstr "" + +#: ../../../CHANGELOG.md:2184 +msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you" +msgstr "" + +#: ../../../CHANGELOG.md:2185 +msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)" +msgstr "" + +#: ../../../CHANGELOG.md:2187 +msgid "What do I do if I'm using the integrated Postgres server (default)?" +msgstr "" + +#: ../../../CHANGELOG.md:2189 +msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you." +msgstr "" + +#: ../../../CHANGELOG.md:2191 +msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:" +msgstr "" + +#: ../../../CHANGELOG.md:2193 +msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it." +msgstr "" + +#: ../../../CHANGELOG.md:2195 +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" +msgstr "" + +#: ../../../CHANGELOG.md:2197 +msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:" +msgstr "" + +#: ../../../CHANGELOG.md:2202 +#: ../../../CHANGELOG.md:2214 +msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2." +msgstr "" + +#: ../../../CHANGELOG.md:2204 +msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`" +msgstr "" + +#: ../../../CHANGELOG.md:2205 +msgid "Log in to the server via SSH. The next commands will be performed there." +msgstr "" + +#: ../../../CHANGELOG.md:2206 +msgid "Start the Postgres database server: `systemctl start matrix-postgres`" +msgstr "" + +#: ../../../CHANGELOG.md:2207 +msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" +msgstr "" + +#: ../../../CHANGELOG.md:2208 +msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):" +msgstr "" + +#: ../../../CHANGELOG.md:2216 +msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):" +msgstr "" + +#: ../../../CHANGELOG.md:2234 +msgid "You may need to press *Enter* after pasting the lines above." +msgstr "" + +#: ../../../CHANGELOG.md:2236 +msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2238 +msgid "What do I do if I'm using an external Postgres server?" +msgstr "" + +#: ../../../CHANGELOG.md:2240 +msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time." +msgstr "" + +#: ../../../CHANGELOG.md:2242 +msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were." +msgstr "" + +#: ../../../CHANGELOG.md:2245 +msgid "2021-01-20" +msgstr "" + +#: ../../../CHANGELOG.md:2247 +msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2249 +msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry." +msgstr "" + +#: ../../../CHANGELOG.md:2251 +msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite." +msgstr "" + +#: ../../../CHANGELOG.md:2253 +msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2255 +msgid "Whether this change requires your intervention depends mostly on:" +msgstr "" + +#: ../../../CHANGELOG.md:2256 +msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)." +msgstr "" + +#: ../../../CHANGELOG.md:2257 +msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))." +msgstr "" + +#: ../../../CHANGELOG.md:2259 +msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution." +msgstr "" + +#: ../../../CHANGELOG.md:2261 +msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)" +msgstr "" + +#: ../../../CHANGELOG.md:2263 +msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ." +msgstr "" + +#: ../../../CHANGELOG.md:2265 +msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again." +msgstr "" + +#: ../../../CHANGELOG.md:2267 +msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)." +msgstr "" + +#: ../../../CHANGELOG.md:2269 +msgid "Upgrade path for people running an external Postgres server" +msgstr "" + +#: ../../../CHANGELOG.md:2271 +msgid "For people using the internal Postgres server (the default for the playbook):" +msgstr "" + +#: ../../../CHANGELOG.md:2272 +msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it" +msgstr "" + +#: ../../../CHANGELOG.md:2273 +msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2274 +msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database" +msgstr "" + +#: ../../../CHANGELOG.md:2276 +msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you." +msgstr "" + +#: ../../../CHANGELOG.md:2278 +msgid "You have 3 ways to proceed:" +msgstr "" + +#: ../../../CHANGELOG.md:2280 +msgid "contribute to the playbook to make this possible (difficult)" +msgstr "" + +#: ../../../CHANGELOG.md:2281 +msgid "or, do the migration \"steps\" manually:" +msgstr "" + +#: ../../../CHANGELOG.md:2282 +msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2283 +msgid "create a new `matrix_mautrix_facebook` Postgres database for it" +msgstr "" + +#: ../../../CHANGELOG.md:2284 +msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)" +msgstr "" + +#: ../../../CHANGELOG.md:2285 +msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`" +msgstr "" + +#: ../../../CHANGELOG.md:2286 +msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)" +msgstr "" + +#: ../../../CHANGELOG.md:2287 +msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)" +msgstr "" + +#: ../../../CHANGELOG.md:2288 +msgid "send a `login` message to the Facebook bridge bot again" +msgstr "" + +#: ../../../CHANGELOG.md:2289 +msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2291 +msgid "Staying on SQLite for a little longer (temporary solution)" +msgstr "" + +#: ../../../CHANGELOG.md:2293 +msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:" +msgstr "" + +#: ../../../CHANGELOG.md:2303 +msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future." +msgstr "" + +#: ../../../CHANGELOG.md:2306 +msgid "2021-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:2308 +msgid "matrix-corporal goes 2.0" +msgstr "" + +#: ../../../CHANGELOG.md:2310 +msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now." +msgstr "" + +#: ../../../CHANGELOG.md:2312 +msgid "No manual intervention is required in the common case." +msgstr "" + +#: ../../../CHANGELOG.md:2314 +msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2317 +msgid "2021-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2319 +msgid "Moving from cronjobs to systemd timers" +msgstr "" + +#: ../../../CHANGELOG.md:2321 +msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers." +msgstr "" + +#: ../../../CHANGELOG.md:2323 +msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure." +msgstr "" + +#: ../../../CHANGELOG.md:2325 +msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up." +msgstr "" + +#: ../../../CHANGELOG.md:2328 +msgid "2021-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:2330 +msgid "(Breaking Change) New SSL configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2332 +msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets." +msgstr "" + +#: ../../../CHANGELOG.md:2334 +msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)." +msgstr "" + +#: ../../../CHANGELOG.md:2336 +msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2338 +msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off` (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2340 +msgid "To revert to the old behaviour, set the following variables:" +msgstr "" + +#: ../../../CHANGELOG.md:2347 +msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset." +msgstr "" + +#: ../../../CHANGELOG.md:2350 +msgid "2021-01-03" +msgstr "" + +#: ../../../CHANGELOG.md:2352 +msgid "Signal bridging support via mautrix-signal" +msgstr "" + +#: ../../../CHANGELOG.md:2354 +msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2356 +msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." +msgstr "" + +#: ../../../CHANGELOG.md:2359 +msgid "2020-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:2361 +msgid "The big move to all-on-Postgres (potentially dangerous)" +msgstr "" + +#: ../../../CHANGELOG.md:2363 +msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage." +msgstr "" + +#: ../../../CHANGELOG.md:2365 +msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)." +msgstr "" + +#: ../../../CHANGELOG.md:2367 +msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!" +msgstr "" + +#: ../../../CHANGELOG.md:2369 +msgid "Moving all services to Postgres brings a few **benefits** to us:" +msgstr "" + +#: ../../../CHANGELOG.md:2371 +msgid "**improved performance**" +msgstr "" + +#: ../../../CHANGELOG.md:2372 +msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres." +msgstr "" + +#: ../../../CHANGELOG.md:2373 +msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further." +msgstr "" + +#: ../../../CHANGELOG.md:2374 +msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc." +msgstr "" + +#: ../../../CHANGELOG.md:2376 +msgid "Key takeway" +msgstr "" + +#: ../../../CHANGELOG.md:2378 +msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)" +msgstr "" + +#: ../../../CHANGELOG.md:2380 +msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)." +msgstr "" + +#: ../../../CHANGELOG.md:2382 +msgid "Opting-out of the Postgres migration" +msgstr "" + +#: ../../../CHANGELOG.md:2384 +msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long." +msgstr "" + +#: ../../../CHANGELOG.md:2386 +msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)." +msgstr "" + +#: ../../../CHANGELOG.md:2388 +msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2390 +msgid "Going back to SQLite/nedb if things went wrong" +msgstr "" + +#: ../../../CHANGELOG.md:2392 +msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:" +msgstr "" + +#: ../../../CHANGELOG.md:2394 +msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" +msgstr "" + +#: ../../../CHANGELOG.md:2395 +msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`" +msgstr "" + +#: ../../../CHANGELOG.md:2396 +msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." +msgstr "" + +#: ../../../CHANGELOG.md:2397 +msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)" +msgstr "" + +#: ../../../CHANGELOG.md:2398 +msgid "[get in touch](README.md#support) with us" +msgstr "" + +#: ../../../CHANGELOG.md:2400 +msgid "2020-12-11" +msgstr "" + +#: ../../../CHANGELOG.md:2402 +msgid "synapse-janitor support removed" +msgstr "" + +#: ../../../CHANGELOG.md:2404 +msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2406 +msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2408 +msgid "Docker 20.10 is here" +msgstr "" + +#: ../../../CHANGELOG.md:2410 +msgid "(No need to do anything special in relation to this. Just something to keep in mind)" +msgstr "" + +#: ../../../CHANGELOG.md:2412 +msgid "Docker 20.10 got released recently and your server will likely get it the next time you update." +msgstr "" + +#: ../../../CHANGELOG.md:2414 +msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now." +msgstr "" + +#: ../../../CHANGELOG.md:2417 +msgid "2020-12-08" +msgstr "" + +#: ../../../CHANGELOG.md:2419 +msgid "openid APIs exposed by default on the federation port when federation disabled" +msgstr "" + +#: ../../../CHANGELOG.md:2421 +msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all." +msgstr "" + +#: ../../../CHANGELOG.md:2423 +msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you." +msgstr "" + +#: ../../../CHANGELOG.md:2425 +msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`." +msgstr "" + +#: ../../../CHANGELOG.md:2428 +msgid "2020-11-27" +msgstr "" + +#: ../../../CHANGELOG.md:2430 +msgid "Recent Jitsi updates may require configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:2432 +msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes." +msgstr "" + +#: ../../../CHANGELOG.md:2434 +msgid "**If you use our default Jitsi settings, you won't have to do anything.**" +msgstr "" + +#: ../../../CHANGELOG.md:2436 +msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way." +msgstr "" + +#: ../../../CHANGELOG.md:2438 +msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one." +msgstr "" + +#: ../../../CHANGELOG.md:2440 +msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working." +msgstr "" + +#: ../../../CHANGELOG.md:2443 +msgid "2020-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:2445 +#: ../../../CHANGELOG.md:2453 +msgid "Breaking change matrix-sms-bridge" +msgstr "" + +#: ../../../CHANGELOG.md:2447 +msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add." +msgstr "" + +#: ../../../CHANGELOG.md:2449 +msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu." +msgstr "" + +#: ../../../CHANGELOG.md:2451 +msgid "2020-11-13" +msgstr "" + +#: ../../../CHANGELOG.md:2455 +msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer." +msgstr "" + +#: ../../../CHANGELOG.md:2457 +msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`" +msgstr "" + +#: ../../../CHANGELOG.md:2458 +msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`" +msgstr "" + +#: ../../../CHANGELOG.md:2459 +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`" +msgstr "" + +#: ../../../CHANGELOG.md:2460 +msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished." +msgstr "" + +#: ../../../CHANGELOG.md:2461 +msgid "Remove the var from the first step." +msgstr "" + +#: ../../../CHANGELOG.md:2462 +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`." +msgstr "" + +#: ../../../CHANGELOG.md:2464 +msgid "2020-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2466 +msgid "Dynamic DNS support" +msgstr "" + +#: ../../../CHANGELOG.md:2468 +msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)." +msgstr "" + +#: ../../../CHANGELOG.md:2470 +msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2473 +msgid "2020-10-28" +msgstr "" + +#: ../../../CHANGELOG.md:2475 +msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/" +msgstr "" + +#: ../../../CHANGELOG.md:2477 +msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone." +msgstr "" + +#: ../../../CHANGELOG.md:2479 +msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))." +msgstr "" + +#: ../../../CHANGELOG.md:2481 +msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page." +msgstr "" + +#: ../../../CHANGELOG.md:2483 +msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)." +msgstr "" + +#: ../../../CHANGELOG.md:2486 +msgid "2020-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:2488 +msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default" +msgstr "" + +#: ../../../CHANGELOG.md:2490 +msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them." +msgstr "" + +#: ../../../CHANGELOG.md:2492 +msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default." +msgstr "" + +#: ../../../CHANGELOG.md:2494 +msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):" +msgstr "" + +#: ../../../CHANGELOG.md:2501 +msgid "2020-10-02" +msgstr "" + +#: ../../../CHANGELOG.md:2503 +msgid "Minimum Ansible version raised to v2.7.0" +msgstr "" + +#: ../../../CHANGELOG.md:2505 +msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0." +msgstr "" + +#: ../../../CHANGELOG.md:2507 +msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)." +msgstr "" + +#: ../../../CHANGELOG.md:2509 +msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible." +msgstr "" + +#: ../../../CHANGELOG.md:2512 +msgid "2020-10-01" +msgstr "" + +#: ../../../CHANGELOG.md:2514 +msgid "Postgres 13 support" +msgstr "" + +#: ../../../CHANGELOG.md:2516 +msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:2518 +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2520 +msgid "2020-09-01" +msgstr "" + +#: ../../../CHANGELOG.md:2522 +msgid "matrix-registration support" +msgstr "" + +#: ../../../CHANGELOG.md:2524 +msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2526 +msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2529 +msgid "2020-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2531 +msgid "rust-synapse-compress-state support" +msgstr "" + +#: ../../../CHANGELOG.md:2533 +msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2535 +msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2538 +msgid "2020-07-22" +msgstr "" + +#: ../../../CHANGELOG.md:2540 +msgid "Synapse Admin support" +msgstr "" + +#: ../../../CHANGELOG.md:2542 +msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)." +msgstr "" + +#: ../../../CHANGELOG.md:2544 +msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2547 +msgid "2020-07-20" +msgstr "" + +#: ../../../CHANGELOG.md:2549 +msgid "matrix-reminder-bot support" +msgstr "" + +#: ../../../CHANGELOG.md:2551 +msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)." +msgstr "" + +#: ../../../CHANGELOG.md:2553 +msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2556 +msgid "2020-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:2558 +msgid "(Compatibility Break) Riot is now Element" +msgstr "" + +#: ../../../CHANGELOG.md:2560 +msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)." +msgstr "" + +#: ../../../CHANGELOG.md:2562 +msgid "The playbook follows suit. Existing installations have a few options for how to handle this." +msgstr "" + +#: ../../../CHANGELOG.md:2564 +msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details." +msgstr "" + +#: ../../../CHANGELOG.md:2567 +msgid "2020-07-03" +msgstr "" + +#: ../../../CHANGELOG.md:2569 +msgid "Steam bridging support via mx-puppet-steam" +msgstr "" + +#: ../../../CHANGELOG.md:2571 +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2574 +msgid "2020-07-01" +msgstr "" + +#: ../../../CHANGELOG.md:2576 +msgid "Discord bridging support via mx-puppet-discord" +msgstr "" + +#: ../../../CHANGELOG.md:2578 +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2580 +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)." +msgstr "" + +#: ../../../CHANGELOG.md:2583 +msgid "2020-06-30" +msgstr "" + +#: ../../../CHANGELOG.md:2585 +msgid "Instagram and Twitter bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2587 +msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2589 +msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2592 +msgid "2020-06-28" +msgstr "" + +#: ../../../CHANGELOG.md:2594 +msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2596 +#: ../../../CHANGELOG.md:2625 +msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database." +msgstr "" + +#: ../../../CHANGELOG.md:2598 +msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue." +msgstr "" + +#: ../../../CHANGELOG.md:2600 +msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:2602 +msgid "As always, re-running the playbook is enough to get the updated bits." +msgstr "" + +#: ../../../CHANGELOG.md:2604 +msgid "2020-06-11" +msgstr "" + +#: ../../../CHANGELOG.md:2606 +msgid "SMS bridging requires db reset" +msgstr "" + +#: ../../../CHANGELOG.md:2608 +msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`." +msgstr "" + +#: ../../../CHANGELOG.md:2610 +msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:2612 +msgid "2020-06-05" +msgstr "" + +#: ../../../CHANGELOG.md:2614 +msgid "SMS bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2616 +msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." +msgstr "" + +#: ../../../CHANGELOG.md:2618 +msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2621 +msgid "2020-05-19" +msgstr "" + +#: ../../../CHANGELOG.md:2623 +msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server" +msgstr "" + +#: ../../../CHANGELOG.md:2627 +msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc." +msgstr "" + +#: ../../../CHANGELOG.md:2629 +msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**." +msgstr "" + +#: ../../../CHANGELOG.md:2631 +msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2634 +msgid "2020-04-28" +msgstr "" + +#: ../../../CHANGELOG.md:2636 +msgid "Newer IRC bridge (with potential breaking change)" +msgstr "" + +#: ../../../CHANGELOG.md:2638 +msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2647 +msgid "2020-04-23" +msgstr "" + +#: ../../../CHANGELOG.md:2649 +#: ../../../CHANGELOG.md:2880 +msgid "Slack bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2651 +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2653 +msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2656 +msgid "2020-04-09" +msgstr "" + +#: ../../../CHANGELOG.md:2658 +msgid "Skype bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2660 +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2662 +msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started." +msgstr "" + +#: ../../../CHANGELOG.md:2665 +msgid "2020-04-05" +msgstr "" + +#: ../../../CHANGELOG.md:2667 +msgid "Private Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2669 +msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world." +msgstr "" + +#: ../../../CHANGELOG.md:2671 +msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication." +msgstr "" + +#: ../../../CHANGELOG.md:2673 +msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation." +msgstr "" + +#: ../../../CHANGELOG.md:2676 +msgid "2020-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:2678 +msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" +msgstr "" + +#: ../../../CHANGELOG.md:2680 +msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." +msgstr "" + +#: ../../../CHANGELOG.md:2682 +msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2684 +msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup." +msgstr "" + +#: ../../../CHANGELOG.md:2687 +msgid "2020-03-29" +msgstr "" + +#: ../../../CHANGELOG.md:2689 +msgid "Archlinux support" +msgstr "" + +#: ../../../CHANGELOG.md:2691 +msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server." +msgstr "" + +#: ../../../CHANGELOG.md:2694 +msgid "2020-03-24" +msgstr "" + +#: ../../../CHANGELOG.md:2696 +msgid "Jitsi support" +msgstr "" + +#: ../../../CHANGELOG.md:2698 +msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2700 +msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2703 +msgid "2020-03-15" +msgstr "" + +#: ../../../CHANGELOG.md:2705 +msgid "Raspberry Pi support" +msgstr "" + +#: ../../../CHANGELOG.md:2707 +msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services." +msgstr "" + +#: ../../../CHANGELOG.md:2709 +msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started." +msgstr "" + +#: ../../../CHANGELOG.md:2712 +msgid "2020-02-26" +msgstr "" + +#: ../../../CHANGELOG.md:2714 +msgid "Riot-web themes are here" +msgstr "" + +#: ../../../CHANGELOG.md:2716 +msgid "The playbook now makes it easy to install custom riot-web themes." +msgstr "" + +#: ../../../CHANGELOG.md:2718 +msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)." +msgstr "" + +#: ../../../CHANGELOG.md:2721 +msgid "2020-02-24" +msgstr "" + +#: ../../../CHANGELOG.md:2723 +msgid "Customize the server name in Riot's login page" +msgstr "" + +#: ../../../CHANGELOG.md:2725 +msgid "You can now customize the server name string that Riot-web displays in its login page." +msgstr "" + +#: ../../../CHANGELOG.md:2727 +msgid "These playbook variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:2733 +msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"." +msgstr "" + +#: ../../../CHANGELOG.md:2735 +msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there." +msgstr "" + +#: ../../../CHANGELOG.md:2738 +msgid "2020-01-30" +msgstr "" + +#: ../../../CHANGELOG.md:2740 +msgid "Disabling TLSv1.1" +msgstr "" + +#: ../../../CHANGELOG.md:2742 +msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration." +msgstr "" + +#: ../../../CHANGELOG.md:2744 +msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`" +msgstr "" + +#: ../../../CHANGELOG.md:2747 +msgid "2020-01-21" +msgstr "" + +#: ../../../CHANGELOG.md:2749 +msgid "Postgres collation changes (action required!)" +msgstr "" + +#: ../../../CHANGELOG.md:2751 +msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others." +msgstr "" + +#: ../../../CHANGELOG.md:2753 +msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation." +msgstr "" + +#: ../../../CHANGELOG.md:2755 +msgid "To avoid future problems, we recommend that you run the following command:" +msgstr "" + +#: ../../../CHANGELOG.md:2761 +msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:2764 +msgid "2020-01-14" +msgstr "" + +#: ../../../CHANGELOG.md:2766 +msgid "Added support for Appservice Webhooks" +msgstr "" + +#: ../../../CHANGELOG.md:2768 +msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." +msgstr "" + +#: ../../../CHANGELOG.md:2770 +msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2773 +msgid "2020-01-12" +msgstr "" + +#: ../../../CHANGELOG.md:2775 +msgid "Added support for automatic Double Puppeting for all Mautrix bridges" +msgstr "" + +#: ../../../CHANGELOG.md:2777 +msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." +msgstr "" + +#: ../../../CHANGELOG.md:2779 +msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you." +msgstr "" + +#: ../../../CHANGELOG.md:2781 +msgid "To get started, following the playbook's documentation for the bridge you'd like to configure." +msgstr "" + +#: ../../../CHANGELOG.md:2784 +msgid "2019-12-06" +msgstr "" + +#: ../../../CHANGELOG.md:2786 +msgid "Added support for an alternative method for using another webserver" +msgstr "" + +#: ../../../CHANGELOG.md:2788 +msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2790 +msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))." +msgstr "" + +#: ../../../CHANGELOG.md:2792 +msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)." +msgstr "" + +#: ../../../CHANGELOG.md:2795 +msgid "2019-11-10" +msgstr "" + +#: ../../../CHANGELOG.md:2797 +msgid "Tightened security around room directory publishing" +msgstr "" + +#: ../../../CHANGELOG.md:2799 +msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory." +msgstr "" + +#: ../../../CHANGELOG.md:2801 +msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**." +msgstr "" + +#: ../../../CHANGELOG.md:2803 +msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively." +msgstr "" + +#: ../../../CHANGELOG.md:2806 +msgid "2019-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:2808 +msgid "Improved Postgres upgrading/importing" +msgstr "" + +#: ../../../CHANGELOG.md:2810 +msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles." +msgstr "" + +#: ../../../CHANGELOG.md:2812 +msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server." +msgstr "" + +#: ../../../CHANGELOG.md:2814 +msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it." +msgstr "" + +#: ../../../CHANGELOG.md:2816 +msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage." +msgstr "" + +#: ../../../CHANGELOG.md:2819 +msgid "2019-10-04" +msgstr "" + +#: ../../../CHANGELOG.md:2821 +msgid "Postgres 12 support" +msgstr "" + +#: ../../../CHANGELOG.md:2823 +msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:2825 +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2828 +msgid "2019-10-03" +msgstr "" + +#: ../../../CHANGELOG.md:2830 +msgid "Synapse 1.4.0" +msgstr "" + +#: ../../../CHANGELOG.md:2832 +msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy." +msgstr "" + +#: ../../../CHANGELOG.md:2834 +msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)." +msgstr "" + +#: ../../../CHANGELOG.md:2836 +msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable." +msgstr "" + +#: ../../../CHANGELOG.md:2838 +msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled." +msgstr "" + +#: ../../../CHANGELOG.md:2841 +msgid "2019-09-09" +msgstr "" + +#: ../../../CHANGELOG.md:2843 +msgid "Synapse Simple Antispam support" +msgstr "" + +#: ../../../CHANGELOG.md:2845 +msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves." +msgstr "" + +#: ../../../CHANGELOG.md:2847 +msgid "From now on, you can easily install and configure this spam checker module through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2849 +msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2852 +msgid "2019-08-25" +msgstr "" + +#: ../../../CHANGELOG.md:2854 +msgid "Extensible Riot-web configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2856 +msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now." +msgstr "" + +#: ../../../CHANGELOG.md:2858 +msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2860 +msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2862 +msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2865 +msgid "2019-08-22" +msgstr "" + +#: ../../../CHANGELOG.md:2867 +msgid "Extensible Synapse configuration" +msgstr "" + +#: ../../../CHANGELOG.md:2869 +msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2871 +msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs." +msgstr "" + +#: ../../../CHANGELOG.md:2873 +msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly." +msgstr "" + +#: ../../../CHANGELOG.md:2875 +msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2878 +msgid "2019-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:2882 +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2884 +msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2886 +msgid "Google Hangouts bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:2888 +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2890 +msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2893 +msgid "2019-08-05" +msgstr "" + +#: ../../../CHANGELOG.md:2895 +msgid "Email2Matrix support" +msgstr "" + +#: ../../../CHANGELOG.md:2897 +msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added." +msgstr "" + +#: ../../../CHANGELOG.md:2899 +msgid "It's an optional feature that you can enable via the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2901 +msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)." +msgstr "" + +#: ../../../CHANGELOG.md:2904 +msgid "2019-08-03" +msgstr "" + +#: ../../../CHANGELOG.md:2906 +msgid "Synapse logging level has been reduced to WARNING" +msgstr "" + +#: ../../../CHANGELOG.md:2908 +msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`." +msgstr "" + +#: ../../../CHANGELOG.md:2910 +msgid "This greatly reduces the number of log messages that are being logged, leading to:" +msgstr "" + +#: ../../../CHANGELOG.md:2912 +msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" +msgstr "" + +#: ../../../CHANGELOG.md:2913 +msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages" +msgstr "" + +#: ../../../CHANGELOG.md:2915 +msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)." +msgstr "" + +#: ../../../CHANGELOG.md:2918 +msgid "2019-07-08" +msgstr "" + +#: ../../../CHANGELOG.md:2920 +msgid "Synapse Maintenance docs and synapse-janitor support are available" +msgstr "" + +#: ../../../CHANGELOG.md:2922 +msgid "The playbook can now help you with Synapse's maintenance." +msgstr "" + +#: ../../../CHANGELOG.md:2924 +msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:2926 +msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you." +msgstr "" + +#: ../../../CHANGELOG.md:2928 +msgid "(BC Break) Rename run control variables" +msgstr "" + +#: ../../../CHANGELOG.md:2930 +msgid "Some internal playbook control variables have been renamed." +msgstr "" + +#: ../../../CHANGELOG.md:2932 +msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything." +msgstr "" + +#: ../../../CHANGELOG.md:2934 +msgid "The following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:2936 +msgid "from `run_import_postgres` to `run_postgres_import`" +msgstr "" + +#: ../../../CHANGELOG.md:2937 +msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`" +msgstr "" + +#: ../../../CHANGELOG.md:2938 +msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`" +msgstr "" + +#: ../../../CHANGELOG.md:2939 +msgid "from `run_import_media_store` to `run_synapse_import_media_store`" +msgstr "" + +#: ../../../CHANGELOG.md:2940 +msgid "from `run_register_user` to `run_synapse_register_user`" +msgstr "" + +#: ../../../CHANGELOG.md:2941 +msgid "from `run_update_user_password` to `run_synapse_update_user_password`" +msgstr "" + +#: ../../../CHANGELOG.md:2944 +msgid "2019-07-04" +msgstr "" + +#: ../../../CHANGELOG.md:2946 +msgid "Synapse no longer logs to text files" +msgstr "" + +#: ../../../CHANGELOG.md:2948 +msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2950 +msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:2952 +msgid "Because of this, the following variables have become obsolete and were removed:" +msgstr "" + +#: ../../../CHANGELOG.md:2954 +msgid "`matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:2955 +msgid "`matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:2957 +msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." +msgstr "" + +#: ../../../CHANGELOG.md:2959 +msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)." +msgstr "" + +#: ../../../CHANGELOG.md:2962 +msgid "2019-06-27" +msgstr "" + +#: ../../../CHANGELOG.md:2964 +msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2966 +msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not." +msgstr "" + +#: ../../../CHANGELOG.md:2968 +msgid "From now on, the playbook will keep both configuration files sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2970 +msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2972 +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)." +msgstr "" + +#: ../../../CHANGELOG.md:2974 +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2976 +msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually." +msgstr "" + +#: ../../../CHANGELOG.md:2978 +msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`." +msgstr "" + +#: ../../../CHANGELOG.md:2981 +msgid "2019-06-24" +msgstr "" + +#: ../../../CHANGELOG.md:2983 +msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:2985 +msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:2987 +#: ../../../CHANGELOG.md:3004 +#: ../../../CHANGELOG.md:3023 +#: ../../../CHANGELOG.md:3062 +msgid "From now on, the playbook will keep the configuration in sync for you." +msgstr "" + +#: ../../../CHANGELOG.md:2989 +msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:2991 +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:2993 +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:2995 +msgid "We're now following the default configuration for the WhatsApp bridge." +msgstr "" + +#: ../../../CHANGELOG.md:2998 +msgid "2019-06-20" +msgstr "" + +#: ../../../CHANGELOG.md:3000 +msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3002 +msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3006 +msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3008 +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)." +msgstr "" + +#: ../../../CHANGELOG.md:3010 +msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example." +msgstr "" + +#: ../../../CHANGELOG.md:3012 +msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`." +msgstr "" + +#: ../../../CHANGELOG.md:3014 +msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3017 +msgid "2019-06-15" +msgstr "" + +#: ../../../CHANGELOG.md:3019 +msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3021 +msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3025 +msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3027 +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3029 +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3031 +msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:" +msgstr "" + +#: ../../../CHANGELOG.md:3033 +msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message" +msgstr "" + +#: ../../../CHANGELOG.md:3034 +msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message." +msgstr "" + +#: ../../../CHANGELOG.md:3035 +msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible" +msgstr "" + +#: ../../../CHANGELOG.md:3036 +msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands" +msgstr "" + +#: ../../../CHANGELOG.md:3038 +msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)." +msgstr "" + +#: ../../../CHANGELOG.md:3041 +msgid "2019-06-12" +msgstr "" + +#: ../../../CHANGELOG.md:3043 +msgid "Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3045 +msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)." +msgstr "" + +#: ../../../CHANGELOG.md:3047 +msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it." +msgstr "" + +#: ../../../CHANGELOG.md:3049 +msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed." +msgstr "" + +#: ../../../CHANGELOG.md:3051 +msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3053 +msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3056 +msgid "2019-06-07" +msgstr "" + +#: ../../../CHANGELOG.md:3058 +msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook" +msgstr "" + +#: ../../../CHANGELOG.md:3060 +msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on." +msgstr "" + +#: ../../../CHANGELOG.md:3064 +msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook." +msgstr "" + +#: ../../../CHANGELOG.md:3066 +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you." +msgstr "" + +#: ../../../CHANGELOG.md:3068 +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3071 +msgid "2019-05-25" +msgstr "" + +#: ../../../CHANGELOG.md:3073 +msgid "Support for exposing container ports publicly (not just to the host)" +msgstr "" + +#: ../../../CHANGELOG.md:3075 +msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." +msgstr "" + +#: ../../../CHANGELOG.md:3077 +msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`." +msgstr "" + +#: ../../../CHANGELOG.md:3079 +msgid "All such variables have been superseded by a better (more flexible) way to do it." +msgstr "" + +#: ../../../CHANGELOG.md:3081 +msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this." +msgstr "" + +#: ../../../CHANGELOG.md:3083 +msgid "Porting examples follow for people having more customized setups:" +msgstr "" + +#: ../../../CHANGELOG.md:3085 +msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" +msgstr "" + +#: ../../../CHANGELOG.md:3087 +msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" +msgstr "" + +#: ../../../CHANGELOG.md:3089 +msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" +msgstr "" + +#: ../../../CHANGELOG.md:3091 +msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" +msgstr "" + +#: ../../../CHANGELOG.md:3093 +msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" +msgstr "" + +#: ../../../CHANGELOG.md:3095 +msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" +msgstr "" + +#: ../../../CHANGELOG.md:3097 +msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" +msgstr "" + +#: ../../../CHANGELOG.md:3099 +msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`" +msgstr "" + +#: ../../../CHANGELOG.md:3101 +msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`" +msgstr "" + +#: ../../../CHANGELOG.md:3103 +msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you." +msgstr "" + +#: ../../../CHANGELOG.md:3106 +msgid "2019-05-23" +msgstr "" + +#: ../../../CHANGELOG.md:3108 +msgid "(BC Break) Ansible 2.8 compatibility" +msgstr "" + +#: ../../../CHANGELOG.md:3110 +msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)." +msgstr "" + +#: ../../../CHANGELOG.md:3112 +msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)." +msgstr "" + +#: ../../../CHANGELOG.md:3114 +msgid "To avoid doing it manually, run this:" +msgstr "" + +#: ../../../CHANGELOG.md:3115 +msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3116 +msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`" +msgstr "" + +#: ../../../CHANGELOG.md:3119 +msgid "2019-05-21" +msgstr "" + +#: ../../../CHANGELOG.md:3121 +msgid "Synapse no longer required" +msgstr "" + +#: ../../../CHANGELOG.md:3123 +msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role." +msgstr "" + +#: ../../../CHANGELOG.md:3125 +msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)." +msgstr "" + +#: ../../../CHANGELOG.md:3127 +msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place." +msgstr "" + +#: ../../../CHANGELOG.md:3129 +msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers." +msgstr "" + +#: ../../../CHANGELOG.md:3131 +msgid "Bridges are now separate from the Synapse role" +msgstr "" + +#: ../../../CHANGELOG.md:3133 +msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)." +msgstr "" + +#: ../../../CHANGELOG.md:3135 +msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)." +msgstr "" + +#: ../../../CHANGELOG.md:3137 +msgid "Renaming inconsistently-named Synapse variables" +msgstr "" + +#: ../../../CHANGELOG.md:3139 +msgid "For better consistency, the following variables have been renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3141 +msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`" +msgstr "" + +#: ../../../CHANGELOG.md:3142 +msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3143 +msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`" +msgstr "" + +#: ../../../CHANGELOG.md:3146 +msgid "2019-05-09" +msgstr "" + +#: ../../../CHANGELOG.md:3148 +msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today." +msgstr "" + +#: ../../../CHANGELOG.md:3150 +msgid "Mautrix Facebook/Messenger bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3152 +msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3154 +msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3156 +msgid "mxisd Registration feature integration" +msgstr "" + +#: ../../../CHANGELOG.md:3158 +msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature." +msgstr "" + +#: ../../../CHANGELOG.md:3160 +msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)." +msgstr "" + +#: ../../../CHANGELOG.md:3163 +msgid "2019-04-16" +msgstr "" + +#: ../../../CHANGELOG.md:3165 +msgid "Caddy webserver examples" +msgstr "" + +#: ../../../CHANGELOG.md:3167 +msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory" +msgstr "" + +#: ../../../CHANGELOG.md:3169 +msgid "2019-04-10" +msgstr "" + +#: ../../../CHANGELOG.md:3171 +msgid "Goofys support for other S3-compatible object stores" +msgstr "" + +#: ../../../CHANGELOG.md:3173 +msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md)," +msgstr "" + +#: ../../../CHANGELOG.md:3176 +msgid "2019-04-03" +msgstr "" + +#: ../../../CHANGELOG.md:3178 +msgid "Ansible >= 2.5 is required" +msgstr "" + +#: ../../../CHANGELOG.md:3180 +msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." +msgstr "" + +#: ../../../CHANGELOG.md:3182 +msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." +msgstr "" + +#: ../../../CHANGELOG.md:3185 +msgid "2019-03-19" +msgstr "" + +#: ../../../CHANGELOG.md:3187 +msgid "TLS support for Coturn" +msgstr "" + +#: ../../../CHANGELOG.md:3189 +msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server." +msgstr "" + +#: ../../../CHANGELOG.md:3191 +msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:" +msgstr "" + +#: ../../../CHANGELOG.md:3197 +msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)." +msgstr "" + +#: ../../../CHANGELOG.md:3199 +msgid "People who build their own custom playbook from our roles should be aware that:" +msgstr "" + +#: ../../../CHANGELOG.md:3201 +msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)." +msgstr "" + +#: ../../../CHANGELOG.md:3203 +msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3206 +msgid "2019-03-12" +msgstr "" + +#: ../../../CHANGELOG.md:3208 +msgid "matrix-nginx-proxy support for serving the base domain" +msgstr "" + +#: ../../../CHANGELOG.md:3210 +msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now." +msgstr "" + +#: ../../../CHANGELOG.md:3212 +msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3214 +msgid "(BC break) matrix-nginx-proxy data variable renamed" +msgstr "" + +#: ../../../CHANGELOG.md:3216 +msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`." +msgstr "" + +#: ../../../CHANGELOG.md:3218 +msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)." +msgstr "" + +#: ../../../CHANGELOG.md:3221 +msgid "2019-03-10" +msgstr "" + +#: ../../../CHANGELOG.md:3223 +msgid "Dimension integration manager support" +msgstr "" + +#: ../../../CHANGELOG.md:3225 +msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3228 +msgid "2019-03-07" +msgstr "" + +#: ../../../CHANGELOG.md:3230 +msgid "Ability to customize mxisd's email templates" +msgstr "" + +#: ../../../CHANGELOG.md:3232 +msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3235 +msgid "2019-03-05" +msgstr "" + +#: ../../../CHANGELOG.md:3237 +msgid "Discord bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3239 +msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3242 +msgid "2019-02-19" +msgstr "" + +#: ../../../CHANGELOG.md:3244 +msgid "Renaming variables" +msgstr "" + +#: ../../../CHANGELOG.md:3246 +#: ../../../CHANGELOG.md:3563 +#: ../../../CHANGELOG.md:3648 +#: ../../../CHANGELOG.md:3768 +msgid "The following playbook variables were renamed:" +msgstr "" + +#: ../../../CHANGELOG.md:3248 +msgid "from `host_specific_hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3249 +msgid "from `hostname_identity` to `matrix_domain`" +msgstr "" + +#: ../../../CHANGELOG.md:3250 +msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`" +msgstr "" + +#: ../../../CHANGELOG.md:3251 +msgid "from `hostname_riot` to `matrix_server_fqn_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3252 +msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3254 +msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix." +msgstr "" + +#: ../../../CHANGELOG.md:3257 +msgid "2019-02-16" +msgstr "" + +#: ../../../CHANGELOG.md:3259 +msgid "Riot v1.0.1 support" +msgstr "" + +#: ../../../CHANGELOG.md:3261 +msgid "You can now use the brand new and redesigned Riot." +msgstr "" + +#: ../../../CHANGELOG.md:3263 +msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing." +msgstr "" + +#: ../../../CHANGELOG.md:3265 +msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)." +msgstr "" + +#: ../../../CHANGELOG.md:3268 +msgid "2019-02-14" +msgstr "" + +#: ../../../CHANGELOG.md:3270 +msgid "Synapse v0.99.1" +msgstr "" + +#: ../../../CHANGELOG.md:3272 +msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless." +msgstr "" + +#: ../../../CHANGELOG.md:3274 +msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more." +msgstr "" + +#: ../../../CHANGELOG.md:3277 +msgid "2019-02-06" +msgstr "" + +#: ../../../CHANGELOG.md:3279 +msgid "Synapse v0.99 support and preparation for Synapse v1.0" +msgstr "" + +#: ../../../CHANGELOG.md:3281 +msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports." +msgstr "" + +#: ../../../CHANGELOG.md:3283 +msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))." +msgstr "" + +#: ../../../CHANGELOG.md:3285 +msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)." +msgstr "" + +#: ../../../CHANGELOG.md:3287 +msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:" +msgstr "" + +#: ../../../CHANGELOG.md:3289 +msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record." +msgstr "" + +#: ../../../CHANGELOG.md:3291 +msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)." +msgstr "" + +#: ../../../CHANGELOG.md:3294 +msgid "2019-02-01" +msgstr "" + +#: ../../../CHANGELOG.md:3296 +msgid "TLS v1.3 support" +msgstr "" + +#: ../../../CHANGELOG.md:3298 +msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default." +msgstr "" + +#: ../../../CHANGELOG.md:3300 +msgid "When using:" +msgstr "" + +#: ../../../CHANGELOG.md:3302 +msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`." +msgstr "" + +#: ../../../CHANGELOG.md:3304 +msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3306 +msgid "**another web server**: you don't need to do anything to accommodate this change" +msgstr "" + +#: ../../../CHANGELOG.md:3309 +msgid "2019-01-31" +msgstr "" + +#: ../../../CHANGELOG.md:3311 +msgid "IRC bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3313 +msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:3316 +msgid "2019-01-29" +msgstr "" + +#: ../../../CHANGELOG.md:3318 +msgid "Running container processes as non-root, without capabilities and read-only" +msgstr "" + +#: ../../../CHANGELOG.md:3320 +msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go." +msgstr "" + +#: ../../../CHANGELOG.md:3322 +msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers." +msgstr "" + +#: ../../../CHANGELOG.md:3324 +msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to." +msgstr "" + +#: ../../../CHANGELOG.md:3326 +msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you." +msgstr "" + +#: ../../../CHANGELOG.md:3328 +msgid "matrix-mailer is now based on Exim, not Postfix" +msgstr "" + +#: ../../../CHANGELOG.md:3330 +msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)." +msgstr "" + +#: ../../../CHANGELOG.md:3332 +msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)." +msgstr "" + +#: ../../../CHANGELOG.md:3334 +msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)." +msgstr "" + +#: ../../../CHANGELOG.md:3337 +msgid "2019-01-17" +msgstr "" + +#: ../../../CHANGELOG.md:3339 +msgid "(BC Break) Making the playbook's roles more independent of one another" +msgstr "" + +#: ../../../CHANGELOG.md:3341 +msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)." +msgstr "" + +#: ../../../CHANGELOG.md:3344 +msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components." +msgstr "" + +#: ../../../CHANGELOG.md:3346 +msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves." +msgstr "" + +#: ../../../CHANGELOG.md:3348 +msgid "In addition, the following components can now be completely disabled (for those who want/need to):" +msgstr "" + +#: ../../../CHANGELOG.md:3349 +msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3350 +msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3351 +msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`" +msgstr "" + +#: ../../../CHANGELOG.md:3353 +msgid "The following changes had to be done:" +msgstr "" + +#: ../../../CHANGELOG.md:3355 +msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file." +msgstr "" + +#: ../../../CHANGELOG.md:3357 +msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement." +msgstr "" + +#: ../../../CHANGELOG.md:3359 +msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3361 +msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic." +msgstr "" + +#: ../../../CHANGELOG.md:3364 +msgid "2019-01-16" +msgstr "" + +#: ../../../CHANGELOG.md:3366 +msgid "Splitting the playbook into multiple roles" +msgstr "" + +#: ../../../CHANGELOG.md:3368 +msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)." +msgstr "" + +#: ../../../CHANGELOG.md:3371 +msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**." +msgstr "" + +#: ../../../CHANGELOG.md:3373 +msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)." +msgstr "" + +#: ../../../CHANGELOG.md:3376 +msgid "2019-01-11" +msgstr "" + +#: ../../../CHANGELOG.md:3378 +msgid "(BC Break) mxisd configuration changes" +msgstr "" + +#: ../../../CHANGELOG.md:3380 +msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured." +msgstr "" + +#: ../../../CHANGELOG.md:3383 +msgid "The following variables are no longer supported by this playbook:" +msgstr "" + +#: ../../../CHANGELOG.md:3385 +msgid "`matrix_mxisd_ldap_enabled`" +msgstr "" + +#: ../../../CHANGELOG.md:3386 +msgid "`matrix_mxisd_ldap_connection_host`" +msgstr "" + +#: ../../../CHANGELOG.md:3387 +msgid "`matrix_mxisd_ldap_connection_tls`" +msgstr "" + +#: ../../../CHANGELOG.md:3388 +msgid "`matrix_mxisd_ldap_connection_port`" +msgstr "" + +#: ../../../CHANGELOG.md:3389 +msgid "`matrix_mxisd_ldap_connection_baseDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3390 +msgid "`matrix_mxisd_ldap_connection_baseDns`" +msgstr "" + +#: ../../../CHANGELOG.md:3391 +#: ../../../CHANGELOG.md:3392 +msgid "`matrix_mxisd_ldap_connection_bindDn`" +msgstr "" + +#: ../../../CHANGELOG.md:3393 +#: ../../../CHANGELOG.md:3397 +msgid "`matrix_mxisd_ldap_connection_bindPassword`" +msgstr "" + +#: ../../../CHANGELOG.md:3394 +msgid "`matrix_mxisd_ldap_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3395 +msgid "`matrix_mxisd_ldap_attribute_uid_type`" +msgstr "" + +#: ../../../CHANGELOG.md:3396 +msgid "`matrix_mxisd_ldap_attribute_uid_value`" +msgstr "" + +#: ../../../CHANGELOG.md:3398 +msgid "`matrix_mxisd_ldap_attribute_name`" +msgstr "" + +#: ../../../CHANGELOG.md:3399 +msgid "`matrix_mxisd_ldap_attribute_threepid_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3400 +msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`" +msgstr "" + +#: ../../../CHANGELOG.md:3401 +msgid "`matrix_mxisd_ldap_identity_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3402 +msgid "`matrix_mxisd_ldap_identity_medium`" +msgstr "" + +#: ../../../CHANGELOG.md:3403 +msgid "`matrix_mxisd_ldap_auth_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3404 +msgid "`matrix_mxisd_ldap_directory_filter`" +msgstr "" + +#: ../../../CHANGELOG.md:3405 +msgid "`matrix_mxisd_template_config`" +msgstr "" + +#: ../../../CHANGELOG.md:3407 +msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information." +msgstr "" + +#: ../../../CHANGELOG.md:3409 +msgid "This new way of configuring mxisd is beneficial because:" +msgstr "" + +#: ../../../CHANGELOG.md:3411 +msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them" +msgstr "" + +#: ../../../CHANGELOG.md:3412 +msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly" +msgstr "" + +#: ../../../CHANGELOG.md:3415 +msgid "2019-01-08" +msgstr "" + +#: ../../../CHANGELOG.md:3417 +msgid "(BC Break) Cronjob schedule no longer configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3419 +msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at." +msgstr "" + +#: ../../../CHANGELOG.md:3421 +msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore." +msgstr "" + +#: ../../../CHANGELOG.md:3424 +msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!" +msgstr "" + +#: ../../../CHANGELOG.md:3427 +msgid "2018-12-23" +msgstr "" + +#: ../../../CHANGELOG.md:3429 +msgid "(BC Break) More SSL certificate retrieval methods" +msgstr "" + +#: ../../../CHANGELOG.md:3431 +msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:" +msgstr "" + +#: ../../../CHANGELOG.md:3432 +msgid "(default) obtaining free SSL certificates from Let's Encrypt" +msgstr "" + +#: ../../../CHANGELOG.md:3433 +msgid "generating self-signed SSL certificates" +msgstr "" + +#: ../../../CHANGELOG.md:3434 +msgid "managing SSL certificates manually" +msgstr "" + +#: ../../../CHANGELOG.md:3436 +msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3438 +msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:" +msgstr "" + +#: ../../../CHANGELOG.md:3440 +msgid "before: `host_specific_matrix_ssl_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3441 +msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`" +msgstr "" + +#: ../../../CHANGELOG.md:3443 +msgid "(BC Break) mxisd upgrade with multiple base DN support" +msgstr "" + +#: ../../../CHANGELOG.md:3445 +msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." +msgstr "" + +#: ../../../CHANGELOG.md:3447 +msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)." +msgstr "" + +#: ../../../CHANGELOG.md:3449 +msgid "Example change:" +msgstr "" + +#: ../../../CHANGELOG.md:3451 +msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`" +msgstr "" + +#: ../../../CHANGELOG.md:3452 +msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`" +msgstr "" + +#: ../../../CHANGELOG.md:3455 +msgid "2018-12-21" +msgstr "" + +#: ../../../CHANGELOG.md:3457 +msgid "Synapse 0.34.0 and Python 3" +msgstr "" + +#: ../../../CHANGELOG.md:3459 +msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)." +msgstr "" + +#: ../../../CHANGELOG.md:3462 +msgid "2018-12-12" +msgstr "" + +#: ../../../CHANGELOG.md:3464 +msgid "Riot homepage customization" +msgstr "" + +#: ../../../CHANGELOG.md:3466 +msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`." +msgstr "" + +#: ../../../CHANGELOG.md:3469 +msgid "2018-12-04" +msgstr "" + +#: ../../../CHANGELOG.md:3471 +msgid "mxisd extensibility" +msgstr "" + +#: ../../../CHANGELOG.md:3473 +msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)." +msgstr "" + +#: ../../../CHANGELOG.md:3476 +msgid "2018-11-28" +msgstr "" + +#: ../../../CHANGELOG.md:3478 +msgid "More scripts" +msgstr "" + +#: ../../../CHANGELOG.md:3480 +msgid "matrix-remove-all allows to uninstall everything with a single command" +msgstr "" + +#: ../../../CHANGELOG.md:3481 +msgid "matrix-make-user-admin allows to upgrade a user's privileges" +msgstr "" + +#: ../../../CHANGELOG.md:3483 +msgid "LDAP auth support via matrix-synapse-ldap3" +msgstr "" + +#: ../../../CHANGELOG.md:3485 +msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3487 +msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3490 +msgid "2018-11-23" +msgstr "" + +#: ../../../CHANGELOG.md:3492 +msgid "Support for controlling public registration and room auto-join" +msgstr "" + +#: ../../../CHANGELOG.md:3494 +msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden." +msgstr "" + +#: ../../../CHANGELOG.md:3496 +msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)." +msgstr "" + +#: ../../../CHANGELOG.md:3498 +msgid "Support for changing the welcome user ID (welcome bot)" +msgstr "" + +#: ../../../CHANGELOG.md:3500 +msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable." +msgstr "" + +#: ../../../CHANGELOG.md:3503 +msgid "2018-11-14" +msgstr "" + +#: ../../../CHANGELOG.md:3505 +msgid "Ability to set Synapse log levels" +msgstr "" + +#: ../../../CHANGELOG.md:3507 +msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same." +msgstr "" + +#: ../../../CHANGELOG.md:3509 +msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels" +msgstr "" + +#: ../../../CHANGELOG.md:3518 +msgid "2018-11-03" +msgstr "" + +#: ../../../CHANGELOG.md:3520 +msgid "Customize parts of Riot's config" +msgstr "" + +#: ../../../CHANGELOG.md:3522 +msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:" +msgstr "" + +#: ../../../CHANGELOG.md:3533 +msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:" +msgstr "" + +#: ../../../CHANGELOG.md:3542 +msgid "SSL protocols used to serve Riot and Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3544 +msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:3546 +msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers." +msgstr "" + +#: ../../../CHANGELOG.md:3548 +msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details." +msgstr "" + +#: ../../../CHANGELOG.md:3551 +msgid "2018-11-01" +msgstr "" + +#: ../../../CHANGELOG.md:3553 +msgid "Postgres 11 support" +msgstr "" + +#: ../../../CHANGELOG.md:3555 +msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default." +msgstr "" + +#: ../../../CHANGELOG.md:3557 +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." +msgstr "" + +#: ../../../CHANGELOG.md:3559 +#: ../../../CHANGELOG.md:3646 +#: ../../../CHANGELOG.md:3766 +msgid "(BC Break) Renaming playbook variables" +msgstr "" + +#: ../../../CHANGELOG.md:3561 +msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit." +msgstr "" + +#: ../../../CHANGELOG.md:3565 +msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3566 +msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3567 +msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3568 +msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3569 +msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3570 +msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3571 +msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3572 +msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3573 +msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" +msgstr "" + +#: ../../../CHANGELOG.md:3574 +msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`" +msgstr "" + +#: ../../../CHANGELOG.md:3575 +msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`" +msgstr "" + +#: ../../../CHANGELOG.md:3576 +msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`" +msgstr "" + +#: ../../../CHANGELOG.md:3579 +msgid "2018-10-26" +msgstr "" + +#: ../../../CHANGELOG.md:3581 +msgid "Mautrix Whatsapp bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3583 +msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3585 +msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3588 +msgid "2018-10-25" +msgstr "" + +#: ../../../CHANGELOG.md:3590 +msgid "Support for controlling Matrix federation" +msgstr "" + +#: ../../../CHANGELOG.md:3592 +msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server." +msgstr "" + +#: ../../../CHANGELOG.md:3595 +msgid "2018-10-24" +msgstr "" + +#: ../../../CHANGELOG.md:3597 +msgid "Disabling riot-web guests" +msgstr "" + +#: ../../../CHANGELOG.md:3599 +msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI." +msgstr "" + +#: ../../../CHANGELOG.md:3602 +msgid "2018-10-21" +msgstr "" + +#: ../../../CHANGELOG.md:3604 +msgid "Self-check maintenance command" +msgstr "" + +#: ../../../CHANGELOG.md:3606 +msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3609 +msgid "2018-10-05" +msgstr "" + +#: ../../../CHANGELOG.md:3611 +msgid "Presence tracking made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3613 +msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)." +msgstr "" + +#: ../../../CHANGELOG.md:3615 +msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly." +msgstr "" + +#: ../../../CHANGELOG.md:3618 +msgid "2018-09-27" +msgstr "" + +#: ../../../CHANGELOG.md:3620 +msgid "Synapse Cache Factor made configurable" +msgstr "" + +#: ../../../CHANGELOG.md:3622 +msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)." +msgstr "" + +#: ../../../CHANGELOG.md:3624 +msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram" +msgstr "" + +#: ../../../CHANGELOG.md:3627 +msgid "2018-09-26" +msgstr "" + +#: ../../../CHANGELOG.md:3629 +msgid "Disabling Docker container logging" +msgstr "" + +#: ../../../CHANGELOG.md:3631 +msgid "`--log-driver=none` is used for all Docker containers now." +msgstr "" + +#: ../../../CHANGELOG.md:3633 +msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart." +msgstr "" + +#: ../../../CHANGELOG.md:3635 +msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs." +msgstr "" + +#: ../../../CHANGELOG.md:3638 +msgid "2018-09-17" +msgstr "" + +#: ../../../CHANGELOG.md:3640 +msgid "Service discovery support" +msgstr "" + +#: ../../../CHANGELOG.md:3642 +msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file." +msgstr "" + +#: ../../../CHANGELOG.md:3644 +msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3650 +msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" +msgstr "" + +#: ../../../CHANGELOG.md:3651 +msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`" +msgstr "" + +#: ../../../CHANGELOG.md:3654 +msgid "2018-09-07" +msgstr "" + +#: ../../../CHANGELOG.md:3656 +msgid "Mautrix Telegram bridging support" +msgstr "" + +#: ../../../CHANGELOG.md:3658 +msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." +msgstr "" + +#: ../../../CHANGELOG.md:3660 +msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3662 +msgid "Events cache size increase and configurability for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3664 +msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable." +msgstr "" + +#: ../../../CHANGELOG.md:3666 +msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used." +msgstr "" + +#: ../../../CHANGELOG.md:3668 +msgid "Password-peppering support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3670 +msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords." +msgstr "" + +#: ../../../CHANGELOG.md:3672 +msgid "Statistics-reporting support for Matrix Synapse" +msgstr "" + +#: ../../../CHANGELOG.md:3674 +msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy." +msgstr "" + +#: ../../../CHANGELOG.md:3676 +msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting." +msgstr "" + +#: ../../../CHANGELOG.md:3679 +msgid "2018-08-29" +msgstr "" + +#: ../../../CHANGELOG.md:3681 +msgid "Changing the way SSL certificates are retrieved" +msgstr "" + +#: ../../../CHANGELOG.md:3683 +msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now." +msgstr "" + +#: ../../../CHANGELOG.md:3685 +msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)." +msgstr "" + +#: ../../../CHANGELOG.md:3687 +msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:" +msgstr "" + +#: ../../../CHANGELOG.md:3689 +msgid "`systemctl stop 'matrix*'`" +msgstr "" + +#: ../../../CHANGELOG.md:3690 +msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)" +msgstr "" + +#: ../../../CHANGELOG.md:3691 +msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3692 +msgid "re-run the playbook's [installation](docs/installing.md)" +msgstr "" + +#: ../../../CHANGELOG.md:3693 +msgid "possibly delete `/matrix/ssl-acmetool-delete-later`" +msgstr "" + +#: ../../../CHANGELOG.md:3696 +msgid "2018-08-21" +msgstr "" + +#: ../../../CHANGELOG.md:3698 +msgid "Matrix Corporal support" +msgstr "" + +#: ../../../CHANGELOG.md:3700 +msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3702 +msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3705 +msgid "2018-08-20" +msgstr "" + +#: ../../../CHANGELOG.md:3707 +msgid "Matrix Synapse rate limit control variables" +msgstr "" + +#: ../../../CHANGELOG.md:3709 +msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)." +msgstr "" + +#: ../../../CHANGELOG.md:3716 +msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3718 +msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3720 +msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3723 +msgid "2018-08-17" +msgstr "" + +#: ../../../CHANGELOG.md:3725 +msgid "REST auth support via matrix-synapse-rest-auth" +msgstr "" + +#: ../../../CHANGELOG.md:3727 +msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." +msgstr "" + +#: ../../../CHANGELOG.md:3729 +msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3731 +msgid "Compression improvements" +msgstr "" + +#: ../../../CHANGELOG.md:3733 +msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it." +msgstr "" + +#: ../../../CHANGELOG.md:3736 +msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB." +msgstr "" + +#: ../../../CHANGELOG.md:3739 +msgid "Disabling some unnecessary Synapse services" +msgstr "" + +#: ../../../CHANGELOG.md:3741 +msgid "The following services are not necessary, so they have been disabled:" +msgstr "" + +#: ../../../CHANGELOG.md:3742 +msgid "on the federation port (8448): the `client` service" +msgstr "" + +#: ../../../CHANGELOG.md:3743 +msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service" +msgstr "" + +#: ../../../CHANGELOG.md:3745 +msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now." +msgstr "" + +#: ../../../CHANGELOG.md:3748 +msgid "2018-08-15" +msgstr "" + +#: ../../../CHANGELOG.md:3750 +msgid "mxisd Identity Server support" +msgstr "" + +#: ../../../CHANGELOG.md:3752 +msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3755 +msgid "2018-08-14" +msgstr "" + +#: ../../../CHANGELOG.md:3757 +msgid "Email-sending support" +msgstr "" + +#: ../../../CHANGELOG.md:3759 +msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)." +msgstr "" + +#: ../../../CHANGELOG.md:3761 +msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc." +msgstr "" + +#: ../../../CHANGELOG.md:3764 +msgid "2018-08-08" +msgstr "" + +#: ../../../CHANGELOG.md:3770 +msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3771 +msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`" +msgstr "" + +#: ../../../CHANGELOG.md:3772 +msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`" +msgstr "" + +#: ../../../CHANGELOG.md:3773 +msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`" +msgstr "" + +#: ../../../CHANGELOG.md:3774 +msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`" +msgstr "" + +#: ../../../CHANGELOG.md:3775 +msgid "from `docker_riot_image` to `matrix_docker_image_riot`" +msgstr "" + +#: ../../../CHANGELOG.md:3776 +msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`" +msgstr "" + +#: ../../../CHANGELOG.md:3777 +msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" +msgstr "" + +#: ../../../CHANGELOG.md:3779 +msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names." +msgstr "" + +#: ../../../CHANGELOG.md:3781 +msgid "Renaming Ansible playbook tag" +msgstr "" + +#: ../../../CHANGELOG.md:3783 +msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`." +msgstr "" + +#: ../../../CHANGELOG.md:3785 +msgid "Docker container linking" +msgstr "" + +#: ../../../CHANGELOG.md:3787 +msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network." +msgstr "" diff --git a/i18n/translation-templates/README.pot b/i18n/translation-templates/README.pot new file mode 100644 index 000000000..03f903992 --- /dev/null +++ b/i18n/translation-templates/README.pot @@ -0,0 +1,1165 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+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" + +#: ../../../README.md:1 +msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgstr "" + +#: ../../../README.md:1 +msgid "Support room on Matrix" +msgstr "" + +#: ../../../README.md:1 +msgid "donate" +msgstr "" + +#: ../../../README.md:3 +msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker" +msgstr "" + +#: ../../../README.md:5 +msgid "🎯 Purpose" +msgstr "" + +#: ../../../README.md:7 +msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that." +msgstr "" + +#: ../../../README.md:9 +msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))." +msgstr "" + +#: ../../../README.md:11 +msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)." +msgstr "" + +#: ../../../README.md:13 +msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))." +msgstr "" + +#: ../../../README.md:15 +msgid "☁ Self-hosting or Managed / SaaS" +msgstr "" + +#: ../../../README.md:17 +msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort." +msgstr "" + +#: ../../../README.md:19 +msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option." +msgstr "" + +#: ../../../README.md:21 +msgid "🚀 Getting started" +msgstr "" + +#: ../../../README.md:23 +msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)." +msgstr "" + +#: ../../../README.md:25 +msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:" +msgstr "" + +#: ../../../README.md:27 +msgid "Starting with the basics. You can always add/remove or tweak services later on." +msgstr "" + +#: ../../../README.md:29 +msgid "Following our installation guide. There are two guides available for beginners and advanced users:" +msgstr "" + +#: ../../../README.md:31 +msgid "⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../README.md:33 +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](./docs/prerequisites.md)** documentation page." +msgstr "" + +#: ../../../README.md:35 +msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)." +msgstr "" + +#: ../../../README.md:37 +msgid "✔ Supported services" +msgstr "" + +#: ../../../README.md:39 +msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else." +msgstr "" + +#: ../../../README.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../README.md:43 +msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components." +msgstr "" + +#: ../../../README.md:45 +msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgstr "" + +#: ../../../README.md:47 +msgid "Homeserver" +msgstr "" + +#: ../../../README.md:49 +msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list." +msgstr "" + +#: ../../../README.md:0 +msgid "Name" +msgstr "" + +#: ../../../README.md:0 +msgid "Default?" +msgstr "" + +#: ../../../README.md:0 +msgid "Description" +msgstr "" + +#: ../../../README.md:0 +msgid "Documentation" +msgstr "" + +#: ../../../README.md:0 +msgid "[Synapse](https://github.com/element-hq/synapse)" +msgstr "" + +#: ../../../README.md:0 +msgid "✅" +msgstr "" + +#: ../../../README.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Conduit](https://conduit.rs)" +msgstr "" + +#: ../../../README.md:0 +msgid "❌" +msgstr "" + +#: ../../../README.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Dendrite](https://github.com/matrix-org/dendrite)" +msgstr "" + +#: ../../../README.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../README.md:57 +msgid "Clients" +msgstr "" + +#: ../../../README.md:59 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../README.md:0 +msgid "[Element Web](https://github.com/element-hq/element-web)" +msgstr "" + +#: ../../../README.md:0 +msgid "Default Matrix web client, configured to connect to your own Synapse server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../README.md:0 +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Cinny](https://github.com/ajbura/cinny)" +msgstr "" + +#: ../../../README.md:0 +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[SchildiChat Web](https://schildi.chat/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../README.md:68 +msgid "Server Components" +msgstr "" + +#: ../../../README.md:70 +msgid "Services that run on the server to make the various parts of your installation work." +msgstr "" + +#: ../../../README.md:0 +msgid "[PostgreSQL](https://www.postgresql.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Coturn](https://github.com/coturn/coturn)" +msgstr "" + +#: ../../../README.md:0 +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-turn.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Traefik](https://doc.traefik.io/traefik/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Free SSL certificate, which secures the connection to all components" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Exim](https://www.exim.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-email.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[ma1sd](https://github.com/ma1uta/ma1sd)" +msgstr "" + +#: ../../../README.md:0 +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)" +msgstr "" + +#: ../../../README.md:0 +msgid "Dynamic DNS" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../README.md:82 +msgid "Authentication" +msgstr "" + +#: ../../../README.md:84 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "Password provider module" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-ldap-auth.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)" +msgstr "" + +#: ../../../README.md:0 +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)" +msgstr "" + +#: ../../../README.md:0 +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-user-verification-service.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "A spam checker module" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)" +msgstr "" + +#: ../../../README.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../README.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../README.md:0 +msgid "[Goofys](https://github.com/kahing/goofys)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-s3.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)" +msgstr "" + +#: ../../../README.md:0 +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../README.md:106 +msgid "Bridges" +msgstr "" + +#: ../../../README.md:108 +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-discord](https://github.com/mautrix/discord)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-slack](https://github.com/mautrix/slack)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-telegram](https://github.com/mautrix/telegram)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-twitter](https://github.com/mautrix/twitter)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-meta](https://github.com/mautrix/instagram)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mautrix-signal](https://github.com/mautrix/signal)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[beeper-linkedin](https://github.com/beeper/linkedin)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to SMS" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Email2Matrix](https://github.com/devture/email2matrix)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Postmoogle](https://github.com/etkecc/postmoogle)" +msgstr "" + +#: ../../../README.md:0 +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../README.md:141 +msgid "Bots" +msgstr "" + +#: ../../../README.md:143 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../README.md:0 +msgid "[baibot](https://github.com/etkecc/baibot)" +msgstr "" + +#: ../../../README.md:0 +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[maubot](https://github.com/maubot/maubot)" +msgstr "" + +#: ../../../README.md:0 +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Honoroit](https://github.com/etkecc/honoroit)" +msgstr "" + +#: ../../../README.md:0 +msgid "A helpdesk bot" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)" +msgstr "" + +#: ../../../README.md:0 +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)" +msgstr "" + +#: ../../../README.md:0 +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" +msgstr "" + +#: ../../../README.md:0 +msgid "[Buscarron](https://github.com/etkecc/buscarron)" +msgstr "" + +#: ../../../README.md:0 +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../README.md:156 +msgid "Administration" +msgstr "" + +#: ../../../README.md:158 +msgid "Services that help you in administrating and monitoring your Matrix installation." +msgstr "" + +#: ../../../README.md:0 +msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)" +msgstr "" + +#: ../../../README.md:0 +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)" +msgstr "" + +#: ../../../README.md:0 +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)" +msgstr "" + +#: ../../../README.md:0 +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "Metrics and Graphs" +msgstr "" + +#: ../../../README.md:0 +msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" +msgstr "" + +#: ../../../README.md:0 +msgid "[Borg](https://borgbackup.org)" +msgstr "" + +#: ../../../README.md:0 +msgid "Backups" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[rageshake](https://github.com/matrix-org/rageshake)" +msgstr "" + +#: ../../../README.md:0 +msgid "Bug report server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)" +msgstr "" + +#: ../../../README.md:0 +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../README.md:170 +msgid "Misc" +msgstr "" + +#: ../../../README.md:172 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../README.md:0 +msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../README.md:0 +msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)" +msgstr "" + +#: ../../../README.md:0 +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)" +msgstr "" + +#: ../../../README.md:0 +msgid "A cli tool that automatically compresses `state_groups` database table in background." +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)" +msgstr "" + +#: ../../../README.md:0 +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-matrix-corporal.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Etherpad](https://etherpad.org)" +msgstr "" + +#: ../../../README.md:0 +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Jitsi](https://jitsi.org/)" +msgstr "" + +#: ../../../README.md:0 +msgid "An open source video-conferencing platform" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Cactus Comments](https://cactus.chat)" +msgstr "" + +#: ../../../README.md:0 +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)" +msgstr "" + +#: ../../../README.md:0 +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[Sygnal](https://github.com/matrix-org/sygnal)" +msgstr "" + +#: ../../../README.md:0 +msgid "Push gateway" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../README.md:0 +msgid "[ntfy](https://ntfy.sh)" +msgstr "" + +#: ../../../README.md:0 +msgid "Push notifications server" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../README.md:187 +msgid "🆕 Changes" +msgstr "" + +#: ../../../README.md:189 +msgid "This playbook evolves over time, sometimes with backward-incompatible changes." +msgstr "" + +#: ../../../README.md:191 +msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new." +msgstr "" + +#: ../../../README.md:193 +msgid "🆘 Support" +msgstr "" + +#: ../../../README.md:195 +msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)" +msgstr "" + +#: ../../../README.md:197 +msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" +msgstr "" + +#: ../../../README.md:199 +msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)" +msgstr "" + +#: ../../../README.md:215 +msgid "🤝 Related" +msgstr "" + +#: ../../../README.md:217 +msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))." +msgstr "" + +#: ../../../README.md:219 +msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server." +msgstr "" diff --git a/i18n/translation-templates/YEAR-IN-REVIEW.pot b/i18n/translation-templates/YEAR-IN-REVIEW.pot new file mode 100644 index 000000000..57712a5b0 --- /dev/null +++ b/i18n/translation-templates/YEAR-IN-REVIEW.pot @@ -0,0 +1,289 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../YEAR-IN-REVIEW.md:1 +msgid "2023" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:3 +msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:5 +msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:7 +msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:9 +msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:10 +msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:12 +msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:14 +msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:16 +msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:18 +msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:20 +msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:22 +msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:24 +msgid "The following **new** **bridges** were added to the playbook in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:26 +msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:27 +msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:28 +msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:30 +msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:32 +msgid "A few other **major components and changes** landed in 2023:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:34 +msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:35 +msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:36 +msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:37 +msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:38 +msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:39 +msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:40 +msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:41 +msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:42 +msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:44 +msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:46 +msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:48 +msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:49 +msgid "likely about **15+% more** than from before we flipped the switch (in October)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:51 +msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:53 +msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:55 +msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:57 +msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:59 +msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:61 +msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:64 +msgid "2022" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:66 +msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:68 +msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:70 +msgid "Support for the following new **bridges** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:72 +msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:73 +msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:74 +msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:75 +msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:77 +msgid "Support for the following new **bots** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:79 +msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:80 +msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:81 +msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:82 +msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:83 +msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:85 +msgid "Support for the following new **components and services** was added:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:87 +msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:88 +msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:89 +msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:90 +msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:91 +msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:92 +msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:93 +msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:95 +msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:97 +msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:98 +msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:99 +msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:100 +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:101 +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:102 +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)" +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:104 +msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default." +msgstr "" + +#: ../../../YEAR-IN-REVIEW.md:106 +msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks." +msgstr "" diff --git a/i18n/translation-templates/docs/README.pot b/i18n/translation-templates/docs/README.pot new file mode 100644 index 000000000..bb84c68d5 --- /dev/null +++ b/i18n/translation-templates/docs/README.pot @@ -0,0 +1,169 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/README.md:1 +msgid "Table of Contents" +msgstr "" + +#: ../../../docs/README.md:3 +msgid "⬇️ Installaton guides " +msgstr "" + +#: ../../../docs/README.md:5 +msgid "There are two installation guides available for beginners and advanced users." +msgstr "" + +#: ../../../docs/README.md:7 +msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/README.md:9 +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide." +msgstr "" + +#: ../../../docs/README.md:11 +msgid "[Prerequisites](prerequisites.md)" +msgstr "" + +#: ../../../docs/README.md:13 +msgid "[Configuring your DNS settings](configuring-dns.md)" +msgstr "" + +#: ../../../docs/README.md:15 +msgid "[Getting the playbook](getting-the-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:17 +msgid "[Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:19 +msgid "[Installing](installing.md)" +msgstr "" + +#: ../../../docs/README.md:21 +msgid "🛠️ Configuration options" +msgstr "" + +#: ../../../docs/README.md:28 +msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)" +msgstr "" + +#: ../../../docs/README.md:30 +msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation" +msgstr "" + +#: ../../../docs/README.md:32 +msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver" +msgstr "" + +#: ../../../docs/README.md:34 +msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation" +msgstr "" + +#: ../../../docs/README.md:36 +msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks" +msgstr "" + +#: ../../../docs/README.md:38 +msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains" +msgstr "" + +#: ../../../docs/README.md:40 +msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system" +msgstr "" + +#: ../../../docs/README.md:42 +msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder" +msgstr "" + +#: ../../../docs/README.md:46 +msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories" +msgstr "" + +#: ../../../docs/README.md:48 +msgid "👨‍🔧 Maintenance" +msgstr "" + +#: ../../../docs/README.md:50 +msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help." +msgstr "" + +#: ../../../docs/README.md:54 +msgid "[Checking if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/README.md:56 +msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)" +msgstr "" + +#: ../../../docs/README.md:58 +msgid "[PostgreSQL maintenance](maintenance-postgres.md)" +msgstr "" + +#: ../../../docs/README.md:60 +msgid "[Synapse maintenance](maintenance-synapse.md)" +msgstr "" + +#: ../../../docs/README.md:62 +msgid "[Upgrading services](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/README.md:64 +msgid "Other documentation pages " +msgstr "" + +#: ../../../docs/README.md:66 +msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook" +msgstr "" + +#: ../../../docs/README.md:70 +msgid "[Alternative architectures](alternative-architectures.md)" +msgstr "" + +#: ../../../docs/README.md:72 +msgid "[Container images used by the playbook](container-images.md)" +msgstr "" + +#: ../../../docs/README.md:74 +msgid "[Obtaining an Access Token](obtaining-access-tokens.md)" +msgstr "" + +#: ../../../docs/README.md:76 +msgid "[Playbook tags](playbook-tags.md)" +msgstr "" + +#: ../../../docs/README.md:78 +msgid "[Registering users](registering-users.md)" +msgstr "" + +#: ../../../docs/README.md:80 +msgid "[Running `just` commands](just.md)" +msgstr "" + +#: ../../../docs/README.md:82 +msgid "[Self-building](self-building.md)" +msgstr "" + +#: ../../../docs/README.md:84 +msgid "[Uninstalling](uninstalling.md)" +msgstr "" + +#: ../../../docs/README.md:86 +msgid "[Updating users passwords](updating-users-passwords.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/alternative-architectures.pot b/i18n/translation-templates/docs/alternative-architectures.pot new file mode 100644 index 000000000..19cc7ee20 --- /dev/null +++ b/i18n/translation-templates/docs/alternative-architectures.pot @@ -0,0 +1,57 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/alternative-architectures.md:1 +msgid "Alternative architectures" +msgstr "" + +#: ../../../docs/alternative-architectures.md:3 +msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported." +msgstr "" + +#: ../../../docs/alternative-architectures.md:5 +msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:" +msgstr "" + +#: ../../../docs/alternative-architectures.md:7 +msgid "`amd64` (`x86_64`)" +msgstr "" + +#: ../../../docs/alternative-architectures.md:8 +msgid "`arm32`" +msgstr "" + +#: ../../../docs/alternative-architectures.md:9 +msgid "`arm64`" +msgstr "" + +#: ../../../docs/alternative-architectures.md:11 +msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture." +msgstr "" + +#: ../../../docs/alternative-architectures.md:13 +msgid "Implementation details" +msgstr "" + +#: ../../../docs/alternative-architectures.md:15 +msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)." +msgstr "" + +#: ../../../docs/alternative-architectures.md:17 +msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary." +msgstr "" diff --git a/i18n/translation-templates/docs/ansible.pot b/i18n/translation-templates/docs/ansible.pot new file mode 100644 index 000000000..5b0c6c9cd --- /dev/null +++ b/i18n/translation-templates/docs/ansible.pot @@ -0,0 +1,180 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/ansible.md:2 +msgid "Running this playbook" +msgstr "" + +#: ../../../docs/ansible.md:4 +msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)." +msgstr "" + +#: ../../../docs/ansible.md:6 +msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)." +msgstr "" + +#: ../../../docs/ansible.md:8 +msgid "Supported Ansible versions" +msgstr "" + +#: ../../../docs/ansible.md:10 +msgid "To manually check which version of Ansible you're on, run: `ansible --version`." +msgstr "" + +#: ../../../docs/ansible.md:12 +msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**." +msgstr "" + +#: ../../../docs/ansible.md:14 +msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)." +msgstr "" + +#: ../../../docs/ansible.md:16 +msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)." +msgstr "" + +#: ../../../docs/ansible.md:18 +msgid "Upgrading Ansible" +msgstr "" + +#: ../../../docs/ansible.md:20 +msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:" +msgstr "" + +#: ../../../docs/ansible.md:22 +msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website." +msgstr "" + +#: ../../../docs/ansible.md:24 +msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)." +msgstr "" + +#: ../../../docs/ansible.md:26 +msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path." +msgstr "" + +#: ../../../docs/ansible.md:28 +msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software." +msgstr "" + +#: ../../../docs/ansible.md:30 +msgid "Using Ansible via Docker" +msgstr "" + +#: ../../../docs/ansible.md:32 +msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)." +msgstr "" + +#: ../../../docs/ansible.md:34 +msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook." +msgstr "" + +#: ../../../docs/ansible.md:36 +msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)." +msgstr "" + +#: ../../../docs/ansible.md:38 +msgid "Running Ansible in a container on the Matrix server itself" +msgstr "" + +#: ../../../docs/ansible.md:40 +msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:" +msgstr "" + +#: ../../../docs/ansible.md:42 +msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker" +msgstr "" + +#: ../../../docs/ansible.md:43 +msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around" +msgstr "" + +#: ../../../docs/ansible.md:45 +msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)." +msgstr "" + +#: ../../../docs/ansible.md:47 +msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH." +msgstr "" + +#: ../../../docs/ansible.md:49 +msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`" +msgstr "" + +#: ../../../docs/ansible.md:51 +#: ../../../docs/ansible.md:71 +msgid "Run this from the playbook's directory:" +msgstr "" + +#: ../../../docs/ansible.md:63 +#: ../../../docs/ansible.md:84 +msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code." +msgstr "" + +#: ../../../docs/ansible.md:65 +#: ../../../docs/ansible.md:86 +msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)." +msgstr "" + +#: ../../../docs/ansible.md:67 +msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:69 +msgid "Running Ansible in a container on another computer (not the Matrix server)" +msgstr "" + +#: ../../../docs/ansible.md:82 +msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part." +msgstr "" + +#: ../../../docs/ansible.md:88 +msgid "Finally, you execute `ansible-playbook …` commands as per normal now." +msgstr "" + +#: ../../../docs/ansible.md:90 +msgid "If you don't use SSH keys for authentication" +msgstr "" + +#: ../../../docs/ansible.md:92 +msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." +msgstr "" + +#: ../../../docs/ansible.md:94 +msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:" +msgstr "" + +#: ../../../docs/ansible.md:100 +msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." +msgstr "" + +#: ../../../docs/ansible.md:102 +msgid "Resolve directory ownership issues" +msgstr "" + +#: ../../../docs/ansible.md:104 +msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" +msgstr "" + +#: ../../../docs/ansible.md:106 +msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /work" +msgstr "" + +#: ../../../docs/ansible.md:110 +msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-captcha.pot b/i18n/translation-templates/docs/configuring-captcha.pot new file mode 100644 index 000000000..7d6161f3d --- /dev/null +++ b/i18n/translation-templates/docs/configuring-captcha.pot @@ -0,0 +1,75 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-captcha.md:1 +msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" +msgstr "" + +#: ../../../docs/configuring-captcha.md:3 +msgid "Overview" +msgstr "" + +#: ../../../docs/configuring-captcha.md:5 +msgid "Captcha can be enabled for this home server. This file explains how to do that." +msgstr "" + +#: ../../../docs/configuring-captcha.md:7 +msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead." +msgstr "" + +#: ../../../docs/configuring-captcha.md:9 +msgid "ReCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:11 +#: ../../../docs/configuring-captcha.md:37 +msgid "Getting keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:13 +#: ../../../docs/configuring-captcha.md:39 +msgid "Requires a site/secret key pair from:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:15 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:17 +msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option" +msgstr "" + +#: ../../../docs/configuring-captcha.md:19 +msgid "Setting ReCaptcha keys" +msgstr "" + +#: ../../../docs/configuring-captcha.md:21 +msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-captcha.md:35 +msgid "hCaptcha" +msgstr "" + +#: ../../../docs/configuring-captcha.md:41 +msgid "" +msgstr "" + +#: ../../../docs/configuring-captcha.md:43 +msgid "Setting hCaptcha keys" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-dns.pot b/i18n/translation-templates/docs/configuring-dns.pot new file mode 100644 index 000000000..d46acdb00 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-dns.pot @@ -0,0 +1,341 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dns.md:1 +msgid "Configuring your DNS settings" +msgstr "" + +#: ../../../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:5 +msgid "To set up Matrix on your domain, you'd need to do some DNS configuration." +msgstr "" + +#: ../../../docs/configuring-dns.md:7 +msgid "DNS setting for server delegation (optional)" +msgstr "" + +#: ../../../docs/configuring-dns.md:9 +msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-dns.md:11 +msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"." +msgstr "" + +#: ../../../docs/configuring-dns.md:13 +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-dns.md:15 +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" +msgstr "" + +#: ../../../docs/configuring-dns.md:16 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-dns.md:18 +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record." +msgstr "" + +#: ../../../docs/configuring-dns.md:20 +msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services." +msgstr "" + +#: ../../../docs/configuring-dns.md:22 +msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/configuring-dns.md:24 +msgid "DNS settings for services enabled by default" +msgstr "" + +#: ../../../docs/configuring-dns.md:26 +msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below." +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Type" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Host" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Priority" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Weight" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Port" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Target" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "A" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "-" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "CNAME" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`element`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/configuring-dns.md:33 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/configuring-dns.md:35 +msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record." +msgstr "" + +#: ../../../docs/configuring-dns.md:37 +msgid "Be mindful as to how long it will take for the DNS records to propagate." +msgstr "" + +#: ../../../docs/configuring-dns.md:39 +msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail." +msgstr "" + +#: ../../../docs/configuring-dns.md:41 +msgid "DNS settings for optional services/features" +msgstr "" + +#: ../../../docs/configuring-dns.md:43 +msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly." +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "Used by component" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Dimension](configuring-playbook-dimension.md) integration server" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`dimension`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`jitsi`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`stats`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`goneb`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`sygnal`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`ntfy`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`etherpad`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`hydrogen`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Cinny](configuring-playbook-client-cinny.md) web client" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`cinny`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`schildichat`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`wsproxy`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`buscarron`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[rageshake](configuring-playbook-rageshake.md) bug report server" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`rageshake`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "SRV" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`_matrix-identity._tcp`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "10" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "0" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "443" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "MX" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "TXT" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`v=spf1 ip4:matrix-server-IP -all`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`_dmarc.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`v=DMARC1; p=quarantine;`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "`postmoogle._domainkey.matrix`" +msgstr "" + +#: ../../../docs/configuring-dns.md:0 +msgid "get it from `!pm dkim`" +msgstr "" + +#: ../../../docs/configuring-dns.md:66 +msgid "SRV record for ma1sd" +msgstr "" + +#: ../../../docs/configuring-dns.md:68 +msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:70 +msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`." +msgstr "" + +#: ../../../docs/configuring-dns.md:72 +msgid "MX and TXT records for Postmoogle" +msgstr "" + +#: ../../../docs/configuring-dns.md:74 +msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified." +msgstr "" + +#: ../../../docs/configuring-dns.md:78 +msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot new file mode 100644 index 000000000..9bf2960c1 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot @@ -0,0 +1,161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-alertmanager-receiver.md:1 +msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 +msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 +msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver) to learn more about what this component does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 +msgid "At the moment, **setting up this service's bot requires some manual actions** as described below in [Account and room preparation](#account-and-room-preparation)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +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:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 +msgid "To enable matrix-alertmanager-receiver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:36 +msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +msgid "Adjusting the matrix-alertmanager-receiver URL" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +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:42 +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:44 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 +msgid "Account and room preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 +msgid "The playbook can automatically create users, but it cannot automatically obtain access tokens, nor perform any of the other manual actions below." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 +msgid "`matrix-alertmanager-receiver` uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see above) for delivering messages. You need to **manually register this bot acccount and obtain an access token for it**." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 +msgid "[Register a new user](registering-users.md): `ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user`" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 +msgid "[Obtain an access token](obtaining-access-tokens.md) for the bot's user account" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 +msgid "Invite the bot to a room where you'd like to alerts to be delivered" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 +msgid "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:70 +msgid "(Optionally) Adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 +msgid "Steps 1 and 2 above only need to be done once, while preparing your [configuration](#adjusting-the-playbook-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 +msgid "Steps 3 and 4 need to be done for each new room you'd like the bot to deliver alerts to. Step 5 is optional and provides cleaner `/alert/` URLs." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +msgid "Now that you've [prepared the bot account and room](#account-and-room-preparation), [configured the playbook](#adjusting-the-playbook-configuration), and potentially [adjusted your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +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:89 +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:91 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:93 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +msgid "Configure your Prometheus Alertmanager with configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 +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:116 +msgid "This bot does **not** accept room invitations automatically (like many other bots do). To deliver messages to rooms, **the bot must be joined to all rooms manually** - see Step 4 of the [Account and room preparation](#account-and-room-preparation) section." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot b/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot new file mode 100644 index 000000000..07218f273 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-appservice-double-puppet.md:1 +msgid "Setting up Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 +msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 +msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 +msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 +msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 +msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot new file mode 100644 index 000000000..2366e7ae6 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot @@ -0,0 +1,185 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-appservice-draupnir-for-all.md:1 +msgid "Setting up Draupnir for All/D4A (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 +msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 +msgid "Draupnir Appservice mode compared to Draupnir bot mode" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 +msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 +msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 +msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 +msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 +msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 +msgid "Installation" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 +msgid "Create a main management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 +msgid "The playbook does not create a management room for your Main Draupnir. This task you have to do on your own." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 +msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 +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:29 +msgid "As noted in the Draupnir install instructions the control room is sensitive. The following is said about the control room in the Draupnir install instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +msgid "Anyone in this room can control the bot so it is important that you only invite trusted users to this room. The room must be unencrypted since the playbook does not support installing Pantalaimon yet." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 +msgid "Give your main management room an alias." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 +msgid "Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 +msgid "Adjusting the playbook configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:40 +msgid "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created in step 2." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md: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-appservice-draupnir-for-all.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-appservice-draupnir-for-all.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 +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:69 +msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +msgid "Granting Users the ability to use D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +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:75 +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:77 +msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 +msgid "How to provision a D4A once you are allowed to." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 +msgid "Open a DM with @draupnir-main:example.com and if using an Element client send a message into this DM to finalise creating it. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 +msgid "Configuration of D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 +msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation. Please note that the playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 +msgid "Please note that Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyways. Config extension instead touches the config passed to the Draupnirs that your Appservice creates. So for example below makes all provisioned Draupnirs protect all joined rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 +msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 +msgid "For example to change Draupnir's `protectAllJoinedRooms` option to `true` you would add the following to your `vars.yml` file." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot new file mode 100644 index 000000000..c4b7fc2a6 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-backup-borg.md:1 +msgid "Setting up BorgBackup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:3 +msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:5 +msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:7 +msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:9 +msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:11 +msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:13 +msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:15 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:17 +msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:19 +msgid "Create a new SSH key:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:25 +msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:27 +msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:29 +msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:39 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:41 +msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:58 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:60 +msgid "USER - SSH user of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:61 +msgid "HOST - SSH host of a provider/server" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:62 +msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:63 +msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:64 +msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:66 +msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:68 +msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:70 +msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:74 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:81 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:83 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:85 +msgid "Manually start a backup" +msgstr "" + +#: ../../../docs/configuring-playbook-backup-borg.md:87 +msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot b/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot new file mode 100644 index 000000000..3fb9115c7 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-base-domain-serving.md:1 +msgid "Serving the base domain (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:3 +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:5 +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:7 +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:8 +msgid "Setting up a `_matrix._tcp` DNS SRV record" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:10 +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:12 +msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:14 +msgid "Usually, there are 2 options:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:16 +msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:18 +msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:20 +msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:22 +msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:28 +msgid "Doing this, the playbook will:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:30 +msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:32 +msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:34 +msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:36 +msgid "Serving a static website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:38 +msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:40 +msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:54 +msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:56 +msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:58 +msgid "Serving a more complicated website at the base domain" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:60 +msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:62 +msgid "You have 2 options." +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:64 +msgid "**One way is to host your base domain elsewhere**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:65 +msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:66 +msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:68 +msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:69 +msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:70 +msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:71 +msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:72 +msgid "building and running a new container on the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:73 +msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:74 +msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it" +msgstr "" + +#: ../../../docs/configuring-playbook-base-domain-serving.md:76 +msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot new file mode 100644 index 000000000..0056d351c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot @@ -0,0 +1,424 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-baibot.md:1 +msgid "Setting up baibot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:8 +msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:10 +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:12 +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:14 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:16 +msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:20 +msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:23 +msgid "[Base configuration](#base-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:24 +msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:25 +msgid "[👥 Initial users configuration](#-initial-users-configuration)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:26 +msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:27 +msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:29 +msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:31 +msgid "Base configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:33 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:71 +msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:73 +msgid "👮‍♂️ Administrator configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:75 +#: ../../../docs/configuring-playbook-bot-baibot.md:99 +msgid "This is an addition to the [base configuration](#base-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:77 +msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:79 +msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:81 +#: ../../../docs/configuring-playbook-bot-baibot.md:110 +msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:95 +msgid "👥 Initial users configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:97 +msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:101 +msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:103 +msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:104 +msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:106 +msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:108 +msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:122 +msgid "🤖 Configuring agents via Ansible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:124 +msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:126 +msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:128 +msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:130 +msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:132 +msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:134 +msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:136 +msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:138 +msgid "Anthropic" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:140 +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:142 +#: ../../../docs/configuring-playbook-bot-baibot.md:168 +#: ../../../docs/configuring-playbook-bot-baibot.md:201 +#: ../../../docs/configuring-playbook-bot-baibot.md:231 +msgid "Here's an example **addition** to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:160 +#: ../../../docs/configuring-playbook-bot-baibot.md:193 +#: ../../../docs/configuring-playbook-bot-baibot.md:221 +#: ../../../docs/configuring-playbook-bot-baibot.md:251 +msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:162 +#: ../../../docs/configuring-playbook-bot-baibot.md:195 +#: ../../../docs/configuring-playbook-bot-baibot.md:223 +#: ../../../docs/configuring-playbook-bot-baibot.md:253 +msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:164 +msgid "Groq" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:166 +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:191 +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:197 +msgid "Mistral" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:199 +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:219 +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:225 +msgid "OpenAI" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:227 +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:229 +msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:249 +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:255 +msgid "OpenAI Compatible" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:257 +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:259 +msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:261 +msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:263 +msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:265 +msgid "Configuring additional agents (without a preset)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:267 +msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:269 +msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:271 +msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:273 +msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:312 +msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:314 +msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:316 +msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:318 +msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:320 +msgid "🤝 Configuring initial default handlers" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:322 +msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:324 +msgid "If you're not configuring agents via Ansible, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:326 +msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:328 +msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:330 +msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:332 +msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:334 +msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:336 +msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:338 +msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:340 +msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:342 +msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:344 +msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:346 +msgid "Example **additional** `vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:363 +msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:365 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:367 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:374 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:376 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:378 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:380 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:382 +msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:384 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:386 +msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:388 +msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:390 +msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:392 +msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:394 +msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:396 +msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:398 +msgid "Debugging" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:400 +msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:402 +msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-baibot.md:416 +msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot new file mode 100644 index 000000000..dbf33309f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot @@ -0,0 +1,129 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:1 +msgid "Setting up Buscarron (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:3 +msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:5 +msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:9 +msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:32 +msgid "Adjusting the Buscarron URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:34 +msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:36 +msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:38 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:49 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:51 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:53 +msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:55 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:57 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:59 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:66 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:68 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:70 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:72 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:74 +msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:76 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:78 +msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:86 +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:88 +msgid "if you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:89 +msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:90 +msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:92 +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot new file mode 100644 index 000000000..fb7c08818 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot @@ -0,0 +1,113 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-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 "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:11 +msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:13 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:15 +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 +msgid "Get an access token and create encryption keys" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 +msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:27 +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:29 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:31 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:52 +msgid "You will need to get tokens for ChatGPT." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:56 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 +msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot new file mode 100644 index 000000000..053368d5f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot @@ -0,0 +1,350 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+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" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:1 +msgid "Setting up Draupnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:3 +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:5 +msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:7 +msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:9 +msgid "If your migrating from Mjolnir skip to step 5b." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:11 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:13 +msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:17 +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:25 +msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:27 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:29 +msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:31 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:33 +msgid "You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:35 +msgid "If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header \"Authorization: Bearer \" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit` Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:41 +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:51 +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:92 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:94 +msgid "You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:104 +msgid "c. Migrating from Mjolnir (Only required if migrating.)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:106 +msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:108 +msgid "That is all you need to do due to that Draupnir can complete migration on its own." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:110 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:119 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:121 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:123 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:125 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:127 +msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:129 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:131 +msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:133 +msgid "Below is a **non-exhaustive quick-start guide** for the impatient." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:135 +msgid "Making Draupnir join and protect a room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:137 +msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:139 +msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:141 +msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:143 +msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:145 +msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:147 +msgid "Giving Draupnir permissions to do its job" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:149 +msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:151 +msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:153 +msgid "Subscribing to a public policy list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:155 +msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:157 +msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:159 +msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:161 +msgid "Creating your own policy lists and rules" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:163 +msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:174 +msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:176 +msgid "As a result of running these commands, you may observe:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:178 +msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +msgid "applying these rules against all rooms that Draupnir is an Administrator in" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +msgid "Enabling built-in protections" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +msgid "For example to change Draupnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +msgid "Abuse Reports" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:225 +msgid "The other method polls an synapse admin API endpoint and is hence only available when using synapse and when the Draupnir user is an admin user (see step 1). To enable it, set `pollReports: true` in Draupnir's config:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot new file mode 100644 index 000000000..f2de4ef5b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:1 +msgid "Setting up Go-NEB (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:3 +msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:5 +msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:7 +msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:9 +msgid "See the project's [documentation](https://github.com/matrix-org/go-neb) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:11 +msgid "Registering the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:13 +msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:15 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:17 +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:25 +msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:29 +msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:193 +msgid "Adjusting the Go-NEB URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:195 +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:197 +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:199 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +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:218 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +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:227 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +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:231 +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:233 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:235 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +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:239 +msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 +msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot new file mode 100644 index 000000000..303b56673 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot @@ -0,0 +1,117 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:1 +msgid "Setting up Honoroit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:3 +msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:5 +msgid "It's a bot you can use to setup **your own helpdesk on matrix**" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:7 +msgid "See the project's [documentation](https://github.com/etkecc/honoroit#how-it-looks-like) to learn what it does with screenshots and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:11 +msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:26 +msgid "Adjusting the Honoroit URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:28 +msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:30 +msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:32 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:42 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:46 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:50 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:57 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:59 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:61 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:63 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:65 +msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:69 +msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:71 +msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot new file mode 100644 index 000000000..ff313929a --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1 +msgid "Setting up matrix-registration-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3 +msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5 +msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 +msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30 +msgid "The bot account will be created automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49 +msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53 +msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 +msgid "In this room send `help` and the bot will reply with all options." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 +msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59 +msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61 +msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot new file mode 100644 index 000000000..9ad8e8d03 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot @@ -0,0 +1,93 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1 +msgid "Setting up matrix-reminder-bot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3 +msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5 +msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 +msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43 +msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47 +msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49 +msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51 +msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53 +msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55 +msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot new file mode 100644 index 000000000..674c77c54 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot @@ -0,0 +1,141 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-maubot.md:1 +msgid "Setting up maubot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:3 +msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:5 +msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:7 +msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:11 +msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:26 +msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:28 +msgid "Adjusting the maubot URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:30 +msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:32 +msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:34 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:44 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:48 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.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-bot-maubot.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:61 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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-bot-maubot.md:67 +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:69 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:71 +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:73 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:74 +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:75 +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:76 +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:78 +msgid "Obtaining an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:80 +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:82 +msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot new file mode 100644 index 000000000..46e7834be --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot @@ -0,0 +1,183 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:1 +msgid "Setting up Mjolnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:3 +msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:5 +msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:7 +msgid "Register the bot account" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:9 +msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:11 +msgid "You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:13 +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:15 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:21 +msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:23 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:25 +msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:27 +msgid "Make sure the account is free from rate limiting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:29 +msgid "You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:31 +msgid "If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header \"Authorization: Bearer \" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit` Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Mjolnir itself. If you made Mjolnir Admin you can just use the Mjolnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 +msgid "Create a management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +msgid "a. Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 +msgid "b. Configuration without E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 +msgid "You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +msgid "Adding Mjolnir synapse antispam module (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 +msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 +msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 +msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 +msgid "For example to change Mjolnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot new file mode 100644 index 000000000..a0e2402a4 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot @@ -0,0 +1,166 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-discord.md:1 +msgid "Setting up Appservice Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 +msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 +msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 +msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 +msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 +msgid "Self-Service Bridging (Manual)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 +msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 +msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 +msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 +msgid "Then, follow the instructions in the help output message." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 +msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 +msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 +msgid "**Note**: Encrypted Matrix rooms are not supported as of writing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70 +msgid "Portal Bridging (Automatic)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 +msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord__`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74 +msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 +msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 +msgid "To get started with Portal Bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 +msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 +msgid "Room addresses follow this syntax: `#_discord__`. 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: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:90 +msgid "Getting Administrator access in a portal bridged room" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 +msgid "By default, you won't have Administrator access in rooms created by the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 +msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 +msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot new file mode 100644 index 000000000..5da520867 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-irc.md:1 +msgid "Setting up Appservice IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 +msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 +msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot new file mode 100644 index 000000000..8605c2709 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-kakaotalk.md:1 +msgid "Setting up Appservice Kakaotalk bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 +msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 +msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 +msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_kakaotalk_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53 +msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55 +msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77 +msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot new file mode 100644 index 000000000..ed9cf1703 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot @@ -0,0 +1,242 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-slack.md:1 +msgid "Setting up Appservice Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3 +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4 +msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5 +msgid "Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then \"the best (and only) option for new installations is to use the webhook bridging\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7 +msgid "The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9 +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13 +msgid "Create a Classic Slack App" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15 +msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17 +msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19 +msgid "Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21 +msgid "Add the following events as `Bot User Events` and save:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23 +msgid "team_domain_change" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24 +msgid "message.channels" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25 +msgid "message.groups (if you want to bridge private channels)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26 +msgid "reaction_added" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27 +msgid "reaction_removed" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29 +msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31 +msgid "chat:write:bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32 +msgid "users:read" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33 +msgid "reactions:write" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34 +msgid "files:write:user (if you want to bridge files)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36 +msgid "**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38 +msgid "Click on \"Install App\" and \"Install App to Workspace\". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40 +msgid "Create an administration control room on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42 +msgid "Create a new Matrix room to act as the administration control room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44 +msgid "Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing \"view source\". The room ID will be displayed near the top." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 +msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85 +msgid "To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87 +msgid "If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 +msgid "Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID - it will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90 +msgid "Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 +msgid "Determine the \"channel ID\" that Slack uses to identify the channel. You can see it when you open a given Slack channel in a browser. The URL reads like this: `https://app.slack.com/client/XXX//details/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:92 +msgid "Issue a link command in the administration control room with these collected values as arguments:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94 +msgid "with file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100 +msgid "without file bridging:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106 +msgid "These arguments can be shortened to single-letter forms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112 +msgid "Unlinking" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114 +msgid "Channels can be unlinked again by sending this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 +msgid "Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124 +msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126 +msgid "Linking: \"Room is now pending-name\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 +msgid "This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the \"channel ID\"' from above." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130 +msgid "Messages work from Matrix to Slack, but not the other way around" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132 +msgid "Check you logs, if they say something like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 +msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) `" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136 +msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot new file mode 100644 index 000000000..01b5b7121 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot @@ -0,0 +1,109 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-appservice-webhooks.md:1 +msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 +msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 +msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 +msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:42 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46 +msgid "To use the bridge, you need to invite the bridge bot user to your room in either way." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48 +msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49 +msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 +msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 +msgid "The JSON body for posting messages will have to look like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68 +msgid "You can test this via curl like so:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81 +msgid "Setting Webhooks with Dimension integration manager" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83 +msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85 +msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87 +msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\" and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot new file mode 100644 index 000000000..3863e6d9b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot @@ -0,0 +1,125 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-beeper-linkedin.md:1 +msgid "Setting up Beeper Linkedin bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 +msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 +msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 +msgid "There are some additional things you may wish to configure about the bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24 +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 +msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 +msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 +msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 +msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 +msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72 +msgid "Bridge asking for 2FA even if you don't have 2FA enabled" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 +msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot new file mode 100644 index 000000000..15528742f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-go-skype-bridge.md:1 +msgid "Setting up Go Skype Bridge bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 +msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 +msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34 +msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 +msgid "Send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot new file mode 100644 index 000000000..3b2b5c57e --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot @@ -0,0 +1,125 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-heisenbridge.md:1 +msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 +msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 +msgid "See the project's [README](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 +msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24 +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26 +msgid "Adjusting the Heisenbridge URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28 +msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 +msgid "This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 +msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 +msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 +msgid "Help is available for all commands with the `-h` switch." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 +msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 +msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot new file mode 100644 index 000000000..028bcc45a --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot @@ -0,0 +1,361 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-hookshot.md:1 +msgid "Setting up matrix-hookshot (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:3 +msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:5 +msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, JIRA, and Figma, as well as generic webhooks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:7 +msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does in detail and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:9 +msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:11 +msgid "Setup Instructions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:13 +msgid "Refer to the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) to learn what the individual options do." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:15 +msgid "Enable the bridge by adding `matrix_hookshot_enabled: true` to your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 +msgid "For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:17 +msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab, Generic), while you must first add the required configuration and enable the others (GitHub, Jira, Figma)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 +msgid "If you're setting up the GitHub bridge, you'll need to generate and download a private key file after you created your GitHub app. Copy the contents of that file to the variable `matrix_hookshot_github_private_key` so the playbook can install it for you, or use one of the [other methods](#manage-github-private-key-with-aux-role) explained below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:19 +msgid "If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready. Hookshot can be set up individually using the tag `setup-hookshot`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:21 +msgid "Other configuration options are available via the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables, see the comments in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) for how to use them." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 +msgid "Finally, run the playbook (see [installing](installing.md))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 +msgid "End-to-bridge encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +msgid "You can enable [encryption](https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html) for Hookshot by adding `matrix_hookshot_encryption_enabled: true` to your configuration (`vars.yml`) and [executing the playbook](installing.md) again." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 +msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added, for example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-hookshot-encryption`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 +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:35 +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:37 +msgid "Send a `!hookshot help` message to see a list of help commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +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:41 +msgid "**Important**: Note that the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation, see [URLs for bridges setup](#urls-for-bridges-setup) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +msgid "More setup documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +msgid "URLs for bridges setup" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "listener" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "default path" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "used as" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "-" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/webhooks/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_webhook_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Webhook-prefix, which affects all webhook-related URLs below" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "generic" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/webhooks/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_generic_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Generic webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "github oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/webhooks/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_github_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "GitHub \"Callback URL\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "jira oauth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/webhooks/jira/oauth`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_jira_oauth_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "JIRA OAuth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "figma endpoint" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/webhooks/figma/webhook`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_figma_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Figma" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "provisioning" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/v1/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_provisioning_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Dimension [provisioning](#provisioning-api)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "appservice" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/_matrix/app/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_appservice_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Matrix server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/hookshot/widgetapi/`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_widgets_endpoint`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Widgets" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`/metrics/hookshot`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:0 +msgid "Prometheus" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +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:63 +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:65 +msgid "Manage GitHub Private Key with aux role" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +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:68 +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:69 +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:70 +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:72 +msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following additional configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +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:85 +msgid "Provisioning API" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 +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:89 +msgid "Metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +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:93 +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:95 +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:97 +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 +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:102 +msgid "Collision with matrix-appservice-webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot new file mode 100644 index 000000000..e70f094e0 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-matrix-bridge-sms.md:1 +msgid "Setting up Matrix SMS bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 +msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 +msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:34 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 +msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot new file mode 100644 index 000000000..6f571692f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot @@ -0,0 +1,241 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-discord.md:1 +msgid "Setting up Mautrix Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4 +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 +msgid "For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7 +msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 +msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 +msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 +msgid "There are some additional things you may wish to configure about the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 +msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 +msgid "`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_discord_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:55 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61 +msgid "Logging in" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63 +msgid "Method 1: Login using QR code (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 +msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 +msgid "You can delete the Discord app after the authentication process." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69 +msgid "Method 2: Login using Discord token (not recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 +msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 +msgid "Bridging" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 +msgid "Start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:76 +msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77 +msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78 +msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 +msgid "Some Direct Messages from Discord should start syncing automatically" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81 +msgid "If you'd like to bridge guilds:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82 +msgid "send `guilds status` to see the list of guilds" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83 +msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84 +msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92 +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108 +msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot new file mode 100644 index 000000000..3c03c30fb --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot @@ -0,0 +1,197 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-facebook.md:1 +msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 +msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 +msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 +msgid "There are some additional things you may wish to configure about the bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25 +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35 +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 +msgid "Using both would look like" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:73 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77 +msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79 +msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81 +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91 +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103 +msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107 +msgid "Facebook rejecting login attempts and forcing you to change password" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109 +msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111 +msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113 +msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115 +msgid "Example command for proxying your traffic through the Matrix server:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121 +msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123 +msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125 +msgid "Once logged in, proceed to [set up bridging](#usage)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127 +msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot new file mode 100644 index 000000000..6e2f83980 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot @@ -0,0 +1,125 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-gmessages.md:1 +msgid "Setting up Mautrix Google Messages bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 +msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:36 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40 +msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62 +msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot new file mode 100644 index 000000000..004ff9bd0 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-googlechat.md:1 +msgid "Setting up Mautrix Google Chat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 +msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 +msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40 +msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42 +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44 +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46 +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48 +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56 +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72 +msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot new file mode 100644 index 000000000..fecd8edf9 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-hangouts.md:1 +msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 +msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 +msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17 +msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 +msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58 +msgid "Method 1: automatically, by enabling Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60 +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72 +msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot new file mode 100644 index 000000000..83bc228d6 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-instagram.md:1 +msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 +msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 +msgid "There are some additional things you may wish to configure about the bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29 +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:60 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64 +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66 +msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68 +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot new file mode 100644 index 000000000..b71e4bb98 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot @@ -0,0 +1,205 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-meta-instagram.md:1 +msgid "Setting up Instagram bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 +msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11 +msgid "Migrating from the old mautrix-instagram bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 +msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 +msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 +msgid "both trying to bridge the same DMs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 +msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:36 +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 +msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61 +msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:85 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89 +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111 +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot new file mode 100644 index 000000000..3d2e0cebf --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot @@ -0,0 +1,241 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-meta-messenger.md:1 +msgid "Setting up Messenger bridging via Mautrix Meta (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 +msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11 +msgid "Migrating from the old mautrix-facebook bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 +msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 +msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 +msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 +msgid "Bridge mode" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 +msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 +msgid "The bridge can pull your Messenger messages via 3 different methods:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43 +msgid "(`facebook`) Facebook via `facebook.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44 +msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 +msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 +msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 +msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 +msgid "Bridge permissions" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57 +msgid "`relay` - Allowed to be relayed through the bridge, no access to commands" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58 +msgid "`user` - Use the bridge with puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59 +msgid "`admin` - Use and administer the bridge" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 +msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 +msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102 +msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104 +msgid "You then need to send a `login` command and follow the bridge bot's instructions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106 +msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128 +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot new file mode 100644 index 000000000..a931c0168 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot @@ -0,0 +1,193 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-signal.md:1 +msgid "Setting up Mautrix Signal bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 +msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 +msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 +msgid "Prerequisites (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11 +msgid "Prepare Postgres database on external Postgres server" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 +msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 +msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 +msgid "Enable Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 +msgid "There are some additional things you may wish to configure about the bridge before you continue." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 +msgid "By default, any user on your homeserver will be able to use the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35 +msgid "Different levels of permission can be granted to users:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37 +msgid "relay - Allowed to be relayed through the bridge, no access to commands;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38 +msgid "user - Use the bridge with puppeting;" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39 +msgid "admin - Use and administer the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 +msgid "The permissions are following the sequence: nothing < relay < user < admin." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43 +msgid "The default permissions are set as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 +msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 +msgid "This will add the admin permission to the specific user, while keeping the default permissions." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 +msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:87 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91 +msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113 +msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot new file mode 100644 index 000000000..8bca7986b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot @@ -0,0 +1,193 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-slack.md:1 +msgid "Setting up Mautrix Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 +msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4 +msgid "For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 +msgid "For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7 +msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 +msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 +msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:33 +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 +msgid "There are some additional options you may wish to configure with the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41 +msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 +msgid "`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_slack_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 +msgid "Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:64 +msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 +msgid "The bot should respond with \"Successfully logged into for team \"" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 +msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75 +msgid "Method 1: automatically, by enabling Appservice Double Puppet" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89 +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot new file mode 100644 index 000000000..a83d5467f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot @@ -0,0 +1,149 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-telegram.md:1 +msgid "Setting up Mautrix Telegram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 +msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 +msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 +msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44 +msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 +msgid "You might also want to give permissions to administrate the bot:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63 +msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65 +msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77 +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 +msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 +msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 +msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot new file mode 100644 index 000000000..7646fb6da --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot @@ -0,0 +1,129 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-twitter.md:1 +msgid "Setting up Mautrix Twitter bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 +msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 +msgid "See the project's [documentation](https://github.com/mautrix/twitter) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 +msgid "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-twitter.md:13 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.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-twitter.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 +msgid "This method is currently not available for the Mautrix-Twitter bridge, but is on the [roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) under Misc/Manual login with `login-matrix`" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot new file mode 100644 index 000000000..3cbe6494c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-whatsapp.md:1 +msgid "Setting up Mautrix Whatsapp bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 +msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 +msgid "Prerequisite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 +msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23 +msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 +msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 +msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 +msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 +msgid "💡 Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60 +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62 +msgid "To set it up, you have 2 ways of going about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64 +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66 +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68 +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70 +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72 +msgid "Method 2: manually, by asking each user to provide a working access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74 +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80 +msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot new file mode 100644 index 000000000..48492f6c1 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot @@ -0,0 +1,101 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mautrix-wsproxy.md:1 +msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 +msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 +msgid "See the project's [documentation](https://github.com/mautrix/wsproxy#readme) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 +msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 +msgid "Adjusting the wsproxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 +msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27 +msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38 +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40 +msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:51 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:55 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:57 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 +msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot new file mode 100644 index 000000000..161cdfd03 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-discord.md:1 +msgid "Setting up MX Puppet Discord bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4 +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:5 +msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7 +msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13 +msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:34 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38 +msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot new file mode 100644 index 000000000..a5531f79a --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-groupme.md:1 +msgid "Setting up MX Puppet GroupMe bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 +msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 +msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 +msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 +msgid "One authentication method is available." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 +msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 +msgid "Once logged in, send `listrooms` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot new file mode 100644 index 000000000..1b3cf7560 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot @@ -0,0 +1,101 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-instagram.md:1 +msgid "Setting up MX Puppet Instagram bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 +msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 +msgid "This allows you to bridge Instagram DirectMessages into Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 +msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34 +msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36 +msgid "Send `link ` 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 "The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot new file mode 100644 index 000000000..4984df1cc --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot @@ -0,0 +1,29 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-skype.md:1 +msgid "Setting up MX Puppet Skype bridging (optional, removed)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 +msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 +msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot new file mode 100644 index 000000000..0d8f02730 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-slack.md:1 +msgid "Setting up MX Puppet Slack bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 +msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 +msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11 +msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15 +msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:39 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43 +msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot new file mode 100644 index 000000000..9e9acd5de --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-mx-puppet-steam.md:1 +msgid "Setting up MX Puppet Steam bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 +msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 +msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 +msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot new file mode 100644 index 000000000..803010590 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-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 page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11 +msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 +msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:41 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45 +msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47 +msgid "To log in, use `link` and click the link." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49 +msgid "Once logged in, send `list` to the bot user to list the available rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 +msgid "Also send `help` to the bot to see the commands available." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot new file mode 100644 index 000000000..fd360ca8b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-postmoogle.md:1 +msgid "Setting up Postmoogle email bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3 +msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5 +msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7 +msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 +msgid "See the project's [documentation](https://github.com/etkecc/postmoogle) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13 +msgid "Open the following ports on your server to be able to receive incoming emails:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15 +msgid "`25/tcp`: SMTP" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16 +msgid "`587/tcp`: Submission (TLS-encrypted SMTP)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18 +msgid "If you don't open these ports, you will still be able to send emails, but not receive any." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20 +msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47 +msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66 +msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70 +msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72 +msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 +msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78 +msgid "Debug/Logs" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80 +msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82 +msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot new file mode 100644 index 000000000..025d428bf --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-bridge-wechat.md:1 +msgid "Setting up WeChat bridging (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:3 +msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:5 +msgid "See the project page to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:9 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:15 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:17 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:24 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:26 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:32 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:34 +msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-wechat.md:36 +msgid "Send `help` to the bot to see the available commands." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot new file mode 100644 index 000000000..30b147203 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot @@ -0,0 +1,165 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-cactus-comments.md:1 +msgid "Setting up Cactus Comments (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:3 +msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:5 +msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:7 +msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:9 +msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:11 +msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:13 +msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:15 +msgid "You can enable whichever component you need (typically both)." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:17 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:19 +msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:41 +msgid "Adjusting the Cactus Comments' client URL" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:43 +msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:45 +msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:47 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:56 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:58 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:60 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:62 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:64 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:66 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:73 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:75 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:77 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:79 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:81 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:83 +msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:85 +msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:87 +msgid "Then, register a site by sending `register ` (where `` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:89 +msgid "Now you are good to go and can embed the comment section on your website!" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:91 +msgid "Embed Cactus Comments" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:93 +msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:95 +msgid "After including the JavaScript and CSS asset files, insert a `
` where you'd like to display the comment section:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:101 +msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `` with the one that has been registered above:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:115 +msgid "Adjust the domain name for self-hosting" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:117 +msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:119 +msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:" +msgstr "" + +#: ../../../docs/configuring-playbook-cactus-comments.md:126 +msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot b/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot new file mode 100644 index 000000000..082f75d13 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot @@ -0,0 +1,97 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-cinny.md:1 +msgid "Setting up Cinny (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:3 +msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:5 +msgid "Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:7 +msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:9 +msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:13 +msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:19 +msgid "Adjusting the Cinny URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:21 +msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:23 +msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:25 +msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:27 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:34 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:36 +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:38 +msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:40 +msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly." +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:42 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:44 +msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:51 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-cinny.md:53 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot b/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot new file mode 100644 index 000000000..62f9e84eb --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-element-web.md:1 +msgid "Configuring Element Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:3 +msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:5 +msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:7 +msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:8 +msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:10 +msgid "Disabling Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:12 +msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:18 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:20 +msgid "The playbook provides some customization variables you could use to change Element Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:22 +msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:24 +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:26 +msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:28 +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:30 +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:32 +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:34 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:36 +msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:38 +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:40 +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:42 +msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:44 +msgid "Adjusting the Element Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:46 +msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:48 +msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:50 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:61 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:63 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:65 +msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:67 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:69 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:71 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:78 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-element-web.md:80 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot b/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot new file mode 100644 index 000000000..7d010672a --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-hydrogen.md:1 +msgid "Setting up Hydrogen (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:3 +msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:5 +msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:9 +msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:15 +msgid "Adjusting the Hydrogen URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:17 +msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:19 +msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:21 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:32 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:34 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:36 +msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:38 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:40 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:42 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:49 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-hydrogen.md:51 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot b/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot new file mode 100644 index 000000000..95c9e313d --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot @@ -0,0 +1,141 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-schildichat-web.md:1 +msgid "Setting up SchildiChat Web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:3 +msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:5 +msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:7 +msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:9 +msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:13 +msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:19 +msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:21 +msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:23 +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:25 +msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:27 +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:29 +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:31 +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:33 +msgid "Themes" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:35 +msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:37 +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:39 +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:41 +msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:43 +msgid "Adjusting the SchildiChat Web URL" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:45 +msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:47 +msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:49 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:60 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:62 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:64 +msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:66 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:68 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:70 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:77 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-client-schildichat-web.md:79 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-conduit.pot b/i18n/translation-templates/docs/configuring-playbook-conduit.pot new file mode 100644 index 000000000..8368dfff9 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-conduit.pot @@ -0,0 +1,93 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-conduit.md:1 +msgid "Configuring Conduit (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:3 +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:7 +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:9 +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:13 +msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:19 +msgid "Creating the first user account" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:21 +msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:23 +msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:24 +msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:25 +msgid "Create your first user via Element Web or any other client which supports creating users" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:26 +msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:27 +msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:28 +msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:30 +msgid "Configuring bridges / appservices" +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:32 +msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:34 +msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command." +msgstr "" + +#: ../../../docs/configuring-playbook-conduit.md:36 +msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-dendrite.pot b/i18n/translation-templates/docs/configuring-playbook-dendrite.pot new file mode 100644 index 000000000..fc9470318 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-dendrite.pot @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dendrite.md:1 +msgid "Configuring Dendrite (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:3 +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:7 +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:9 +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:13 +msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:19 +msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:21 +msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:23 +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:25 +msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:27 +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:29 +msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:31 +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:33 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:35 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:42 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dendrite.md:44 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-dimension.pot b/i18n/translation-templates/docs/configuring-playbook-dimension.pot new file mode 100644 index 000000000..ec8a03f96 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-dimension.pot @@ -0,0 +1,157 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dimension.md:1 +msgid "Setting up Dimension integration manager (optional, unmaintained)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:3 +msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "**Note**: 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:7 +msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:27 +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:29 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:43 +msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:49 +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:51 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:62 +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:64 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:66 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:68 +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:70 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:81 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:83 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:85 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:87 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:89 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:91 +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:93 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:95 +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:97 +msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot b/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot new file mode 100644 index 000000000..274db91df --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-dynamic-dns.md:1 +msgid "Setting up Dynamic DNS (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:3 +msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:5 +msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:7 +msgid "Prerequisite" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:9 +msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:13 +msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:35 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:37 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:39 +msgid "Additional Reading" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:41 +msgid "Additional resources:" +msgstr "" + +#: ../../../docs/configuring-playbook-dynamic-dns.md:43 +msgid "https://matrix.org/docs/guides/free-small-matrix-server" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-email.pot b/i18n/translation-templates/docs/configuring-playbook-email.pot new file mode 100644 index 000000000..7a23c69ef --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-email.pot @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-email.md:1 +msgid "Adjusting email-sending settings (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:3 +msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:5 +msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:7 +msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:9 +msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:11 +msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:13 +msgid "Firewall settings" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:15 +msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:17 +msgid "Relaying email through another SMTP server" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:19 +msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:31 +msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:33 +msgid "Configuations for sending emails using Sendgrid" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:35 +msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:37 +msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:39 +msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid." +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:51 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-email.md:53 +msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot new file mode 100644 index 000000000..66409c6dc --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot @@ -0,0 +1,177 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-email2matrix.md:1 +msgid "Setting up Email2Matrix (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:3 +msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:5 +msgid "The playbook can install and configure [email2matrix](https://github.com/devture/email2matrix) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:7 +msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:9 +msgid "Preparation" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:11 +msgid "DNS configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:13 +msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:15 +msgid "Port availability" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:17 +msgid "Ensure that port 25 is available on your Matrix server and open in your firewall." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:19 +msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:21 +msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:23 +msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:25 +msgid "Creating a user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:27 +msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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:29 +msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:31 +msgid "Creating a shared room" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:33 +msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:35 +msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:37 +msgid "Inviting additional people to the room is okay too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:39 +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:41 +msgid "Obtaining an access token for the sender user" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:43 +msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:45 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:47 +msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:72 +msgid "where:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:74 +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:75 +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:76 +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:77 +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:78 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:79 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:80 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:81 +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:83 +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:85 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:87 +msgid "To enable Email2Matrix, run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:95 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-email2matrix,start` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:97 +msgid "`just run-tags setup-email2matrix,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-email2matrix.md:99 +msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-etherpad.pot b/i18n/translation-templates/docs/configuring-playbook-etherpad.pot new file mode 100644 index 000000000..0856a2a9d --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-etherpad.pot @@ -0,0 +1,169 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-etherpad.md:1 +msgid "Setting up Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:3 +msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:5 +msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:9 +msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:19 +msgid "Adjusting the Etherpad URL" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:21 +msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:23 +msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:25 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:36 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:38 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:40 +msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:42 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:44 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:46 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:53 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:55 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:57 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:59 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:61 +msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:65 +msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:67 +msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:69 +msgid "Managing / Deleting old pads" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:71 +msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:73 +msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:75 +msgid "How to use Etherpad widgets without an integration manager (like Dimension)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:77 +msgid "This is how it works in Element Web, it might work quite similar with other clients:" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:79 +msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:81 +msgid "Set Dimension default to the self-hosted Etherpad (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:83 +msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:85 +msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:87 +msgid "Removing the integrated Etherpad chat" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:89 +msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:91 +msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:93 +msgid "Known issues" +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:95 +msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it." +msgstr "" + +#: ../../../docs/configuring-playbook-etherpad.md:97 +msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot b/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot new file mode 100644 index 000000000..525f188ed --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot @@ -0,0 +1,45 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-external-postgres.md:1 +msgid "Using an external PostgreSQL server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:3 +msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:5 +msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:7 +msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:23 +msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:25 +msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible." +msgstr "" + +#: ../../../docs/configuring-playbook-external-postgres.md:27 +msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-federation.pot b/i18n/translation-templates/docs/configuring-playbook-federation.pot new file mode 100644 index 000000000..f3ceaf31a --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-federation.pot @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-federation.md:1 +msgid "Controlling Matrix federation (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:3 +msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:5 +msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:7 +msgid "Federating only with select servers" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:9 +msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:17 +msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:19 +msgid "Exposing the room directory over federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:21 +msgid "By default, your server's public rooms directory is not exposed to other servers via federation." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:23 +msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:29 +msgid "Disabling federation" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:31 +msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:37 +msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:39 +msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:51 +msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:53 +msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection." +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:55 +msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:" +msgstr "" + +#: ../../../docs/configuring-playbook-federation.md:66 +msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on without issues.**" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-jitsi.pot b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot new file mode 100644 index 000000000..05c2280b2 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot @@ -0,0 +1,361 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-jitsi.md:1 +msgid "Setting up the Jitsi video-conferencing platform (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:3 +msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:5 +msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:7 +msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:11 +msgid "You may need to open the following ports to your server:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:13 +msgid "`4443/tcp` - RTP media fallback over TCP" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:14 +msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:16 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:18 +msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:24 +msgid "Adjusting the Jitsi URL" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:26 +msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:28 +msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:30 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:37 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:39 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:41 +msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:43 +msgid "(Optional) Configure Jitsi authentication and guests mode" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:45 +msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:47 +msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:49 +msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:51 +msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:53 +msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:55 +msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:57 +msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:59 +msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:71 +msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:73 +msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:75 +msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:77 +msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:79 +msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:81 +msgid "To enable set this configuration at host level:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:89 +msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:91 +msgid "Authenticate using LDAP (Auth-Type 'ldap')" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:93 +msgid "An example LDAP configuration could be:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:113 +msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:115 +msgid "(Optional) Making your Jitsi server work on a LAN" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:117 +msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:119 +msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:121 +msgid "Here is how to do it in the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:123 +msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:130 +msgid "(Optional) Fine tune Jitsi" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:132 +msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:147 +msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:149 +msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:151 +msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:153 +msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:155 +msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:157 +msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:159 +msgid "In order to set the max number of participants use the following **additional** configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:165 +msgid "(Optional) Additional JVBs" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:167 +msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:169 +msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:171 +msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:178 +msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:190 +msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:192 +msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:198 +msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:204 +msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:210 +msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:216 +msgid "(The default is empty; if it's set then docker forwards the port.)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:218 +msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:220 +msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:256 +msgid "(Optional) Enable Gravatar" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:258 +msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:260 +msgid "To enable Gravatar set:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:266 +msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:268 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:270 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:277 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:279 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:281 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:283 +msgid "You can use the self-hosted Jitsi server in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:285 +msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:287 +msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:289 +msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:291 +msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:293 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:295 +msgid "Rebuilding your Jitsi installation" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:297 +msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:299 +msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:301 +msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh." +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:303 +msgid "To rebuild your Jitsi configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:305 +msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:306 +msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)" +msgstr "" + +#: ../../../docs/configuring-playbook-jitsi.md:307 +msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot new file mode 100644 index 000000000..002e67cf2 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot @@ -0,0 +1,57 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-ldap-auth.md:1 +msgid "Setting up the LDAP authentication password provider module (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:3 +msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:5 +msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:7 +msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:24 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:26 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:32 +msgid "Using ma1sd Identity Server for authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:34 +msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)." +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:36 +msgid "Handling user registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ldap-auth.md:38 +msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot new file mode 100644 index 000000000..76969ae11 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot @@ -0,0 +1,209 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-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) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:11 +msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:13 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:15 +msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:17 +msgid "Name: `_matrix-identity._tcp` (use this text as-is)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:18 +msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:20 +msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:22 +msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:24 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:26 +msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:32 +msgid "Matrix.org lookup forwarding" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:34 +msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:36 +msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:38 +msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:44 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:46 +msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:48 +msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:50 +msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:52 +msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:54 +msgid "Customizing email templates" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:56 +msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:58 +msgid "ma1sd-controlled Registration" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:60 +msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:62 +msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:64 +msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:66 +msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:68 +msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:70 +msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:72 +msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:74 +msgid "Authentication" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:76 +msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:78 +msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:98 +msgid "Example: SMS verification" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:100 +msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:114 +msgid "Example: Open Registration for every Domain" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:116 +msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:130 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:132 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:139 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:141 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:143 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:145 +msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:147 +msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd." +msgstr "" + +#: ../../../docs/configuring-playbook-ma1sd.md:149 +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot new file mode 100644 index 000000000..85a638778 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot @@ -0,0 +1,618 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-authentication-service.md:1 +msgid "Setting up Matrix Authentication Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3 +msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5 +msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7 +msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9 +msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10 +msgid "the [Expectations](#expectations) section below" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11 +msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13 +msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15 +msgid "Reasons to use Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17 +msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19 +msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21 +msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23 +msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25 +msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27 +msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29 +msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31 +msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33 +msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37 +msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39 +msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41 +msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43 +msgid "Expectations" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45 +msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47 +msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49 +msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51 +msgid "❌ **Some services experience issues when authenticating via MAS**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53 +msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55 +msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\"" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57 +msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58 +msgid "Other services may be similarly affected. This list is not exhaustive." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60 +msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62 +msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64 +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66 +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68 +msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70 +msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72 +msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74 +msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76 +msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78 +msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80 +msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82 +msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84 +msgid "Installation flows" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86 +msgid "New homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88 +msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90 +msgid "Existing homeserver" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92 +msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94 +msgid "For existing Synapse homeservers:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96 +msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98 +msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102 +msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116 +msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118 +msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120 +msgid "Adjusting the Matrix Authentication Service URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122 +msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:124 +msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:126 +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134 +msgid "Marking an existing homeserver for migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136 +msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138 +msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140 +msgid "Upstream OAuth2 configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142 +msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144 +msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261 +msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263 +msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265 +msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267 +msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268 +msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269 +msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281 +msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294 +msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296 +msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298 +msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300 +msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302 +msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304 +msgid "The installation + migration steps are like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306 +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308 +msgid "Perform the initial [installation](#installing). At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310 +msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312 +msgid "The homeserver will still continue to use its local database for validating existing access tokens." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314 +msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316 +msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318 +msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320 +msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322 +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324 +msgid "remove the `matrix_authentication_service_migration_in_progress: false` line" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326 +msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328 +msgid "Perform the [installation](#installing) again. At this point:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330 +msgid "The homeserver will start delegating authentication to MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332 +msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334 +msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336 +msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338 +msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340 +msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342 +msgid "Configuring syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344 +msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346 +msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348 +msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350 +msgid "Configuring upstream OIDC provider mapping for syn2mas" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352 +msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354 +msgid "If you don't do this, `syn2mas` would report errors like this one:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356 +msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358 +msgid "Below is an example situation and a guide for how to solve it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360 +msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362 +msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364 +msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373 +msgid "Performing a syn2mas dry-run" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375 +msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377 +msgid "A dry-run would not cause downtime, because it avoids stopping Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379 +msgid "To perform a dry-run, run:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385 +msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387 +msgid "Performing a real syn2mas migration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389 +msgid "Before performing a real migration make sure:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391 +msgid "you've familiarized yourself with the [expectations](#expectations)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393 +msgid "you've performed a Postgres backup, just in case" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395 +msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397 +msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399 +msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401 +msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407 +msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409 +msgid "Verify that Matrix Authentication Service is installed correctly" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411 +msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413 +msgid "You can do it:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415 +msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417 +msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419 +msgid "If successful, you should see some output that looks like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431 +msgid "Management" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433 +msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435 +msgid "This documentation page already mentions:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437 +msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439 +msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441 +msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443 +msgid "User registration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445 +msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447 +msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449 +msgid "Working around email deliverability issues" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451 +msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453 +msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455 +msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457 +msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot new file mode 100644 index 000000000..866d2c6b1 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot @@ -0,0 +1,121 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-corporal.md:1 +msgid "Setting up Matrix Corporal (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:5 +msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:9 +msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:11 +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment. See that project's documentation to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:13 +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:14 +msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:19 +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:72 +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:74 +msgid "No matter what Matrix user ID you configure to run it with, make sure that:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +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:78 +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:80 +msgid "Using a locally-stored static policy" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +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:114 +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:116 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +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:127 +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:129 +msgid "Matrix Corporal files" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +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:133 +msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths - `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot new file mode 100644 index 000000000..848607daa --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot @@ -0,0 +1,61 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-ldap-registration-proxy.md:1 +msgid "Setting up matrix-ldap-registration-proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 +msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 +msgid "This proxy handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 +msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 +msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot new file mode 100644 index 000000000..c75b2e87c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot @@ -0,0 +1,164 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-media-repo.md:1 +msgid "Storing Matrix media files using matrix-media-repo (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:3 +msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:5 +msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:7 +msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:0 +msgid "**Table of Contents**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:0 +msgid "[Quickstart](#quickstart)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:0 +msgid "[Additional configuration options](#configuring-the-media-repo)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:0 +msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:15 +msgid "Quickstart" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:17 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:26 +msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:28 +msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:30 +msgid "Configuring the media-repo" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:32 +msgid "Additional common configuration options:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:91 +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:93 +msgid "Signing Keys" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:95 +msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:97 +msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:103 +msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:105 +msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:107 +msgid "Key backup and revoking" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:109 +msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:111 +msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:113 +msgid "Importing data from an existing media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:115 +msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:117 +msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:119 +msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:121 +msgid "Importing data from the Synapse media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:123 +msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:125 +msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:127 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:149 +msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:139 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:161 +msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:141 +#: ../../../docs/configuring-playbook-matrix-media-repo.md:163 +msgid "This should output a `msg=\"Import completed\"` when finished successfully!" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:143 +msgid "Importing data from the Dendrite media store" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:145 +msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-media-repo.md:147 +msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot new file mode 100644 index 000000000..7e114683c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot @@ -0,0 +1,153 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-matrix-registration.md:1 +msgid "Setting up matrix-registration (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:3 +msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:5 +msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:7 +msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:9 +msgid "matrix-registration is a simple python application to have a token based Matrix registration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:11 +msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:13 +msgid "**matrix-registration** provides 2 things:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:15 +msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:17 +msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:19 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:21 +msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:30 +msgid "Adjusting the matrix-registration URL" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:32 +msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:34 +msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:36 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:46 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:48 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:50 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:54 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:61 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:63 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:67 +msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:69 +msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:71 +msgid "We make the most common APIs easy to use via the playbook (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:73 +msgid "Creating registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:75 +msgid "To **create a new user registration token (link)**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:83 +msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:85 +msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:87 +msgid "Listing registration tokens" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:89 +msgid "To **list the existing user registration tokens**, use this command:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-registration.md:96 +msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot b/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot new file mode 100644 index 000000000..f97eeeb58 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot @@ -0,0 +1,178 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-mautrix-bridges.md:1 +msgid "Setting up a Generic Mautrix Bridge (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:3 +msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:5 +msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:9 +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:16 +msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:18 +msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:24 +msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:33 +msgid "encryption" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:35 +msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:37 +msgid "**for all bridges with encryption support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:44 +#: ../../../docs/configuring-playbook-mautrix-bridges.md:61 +msgid "**Alternatively**, for a specific bridge:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:51 +msgid "relay mode" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:53 +msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:55 +msgid "**for all bridges with relay mode support**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:70 +msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:82 +msgid "Setting the bot's username" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:88 +msgid "Can be used to set the username for the bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:90 +msgid "Discovering additional configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:92 +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:94 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:96 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:103 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:105 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:107 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:109 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:111 +msgid "Set up Double Puppeting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:113 +msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:115 +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:121 +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:123 +msgid "Controlling the logging level" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:129 +msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:131 +msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:133 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:135 +msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:137 +msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:139 +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:141 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:143 +msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge." +msgstr "" + +#: ../../../docs/configuring-playbook-mautrix-bridges.md:145 +msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-nginx.pot b/i18n/translation-templates/docs/configuring-playbook-nginx.pot new file mode 100644 index 000000000..9350df977 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-nginx.pot @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-nginx.md:1 +msgid "Configure Nginx (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-nginx.md:3 +msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-ntfy.pot b/i18n/translation-templates/docs/configuring-playbook-ntfy.pot new file mode 100644 index 000000000..f9e46f031 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-ntfy.pot @@ -0,0 +1,233 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-ntfy.md:1 +msgid "Setting up the ntfy push notifications server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:3 +msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:5 +msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:7 +msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:9 +msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:13 +msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:27 +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:29 +msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:31 +msgid "Adjusting the ntfy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:33 +msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:35 +msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:37 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:46 +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:48 +msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:50 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:52 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:59 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:61 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:63 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:65 +msgid "To make use of your ntfy installation, on Android for example, you need two things:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:67 +msgid "the `ntfy` app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:68 +msgid "a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:70 +msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:72 +msgid "Setting up the `ntfy` Android app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:74 +msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:75 +msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:76 +msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:78 +msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:80 +msgid "Setting up a UnifiedPush-compatible Matrix app" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:82 +msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:84 +msgid "Steps needed for specific Matrix apps:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:86 +msgid "FluffyChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:87 +msgid "Should auto-detect and use it. No manual settings." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:89 +msgid "SchildiChat-android:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:90 +msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:91 +msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:92 +msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:94 +msgid "Element-android v1.4.26+:" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:95 +msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:96 +msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:98 +msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:100 +msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:102 +msgid "Web App" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:104 +msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:106 +msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:108 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:110 +msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:112 +msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:114 +msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:116 +msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:118 +msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." +msgstr "" + +#: ../../../docs/configuring-playbook-ntfy.md:120 +msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot b/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot new file mode 100644 index 000000000..ed74fe60c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot @@ -0,0 +1,189 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-own-webserver.md:1 +msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:3 +msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:5 +msgid "Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:7 +msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:9 +msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:11 +msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:13 +msgid "There are 2 ways to use Traefik with this playbook, as described below." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:15 +msgid "Traefik managed by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:17 +msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:25 +msgid "Traefik will manage SSL certificates for all services seamlessly." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:27 +msgid "Traefik managed by you" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:53 +msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:55 +msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:57 +msgid "You need to configure 4 entrypoints for your Traefik server:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:59 +msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:60 +msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:61 +msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:62 +msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:64 +msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:66 +msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:86 +msgid "You can use the following `docker-compose.yml` as example to launch Traefik." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:122 +msgid "Another webserver" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:124 +msgid "If you don't wish to use Traefik, you can also use your own webserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:126 +msgid "Doing this is possible, but requires manual work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:128 +msgid "There are 2 ways to go about it:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:130 +msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:132 +msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:134 +msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:136 +msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:138 +msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:140 +msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:142 +msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:144 +msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:194 +msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:196 +msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:198 +msgid "To put it another way:" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:199 +msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:200 +msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:202 +msgid "Using no reverse-proxy on the Matrix side at all" +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:204 +msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:206 +msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:208 +msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-own-webserver.md:210 +msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot new file mode 100644 index 000000000..4462e3058 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot @@ -0,0 +1,61 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-pantalaimon.md:1 +msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:3 +msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:5 +msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:7 +msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:17 +msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:19 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:21 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:28 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-pantalaimon.md:30 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot b/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot new file mode 100644 index 000000000..80f120d2c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot @@ -0,0 +1,153 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-postgres-backup.md:1 +msgid "Setting up postgres backup (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:3 +msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:5 +msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:9 +msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:15 +msgid "Refer to the table below for additional configuration variables and their default values." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Default value" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`false`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_schedule`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`'@daily'`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Cron-schedule specifying the interval between postgres backups." +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_keep_days`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`7`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Number of daily backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_keep_weeks`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`4`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Number of weekly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_keep_months`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`12`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Number of monthly backups to keep" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_base_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`postgres_backup_data_path`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "`\"{{ postgres_backup_base_path }}/data\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:0 +msgid "Storage path for postgres-backup database backups" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-postgres-backup.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot new file mode 100644 index 000000000..28993edba --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot @@ -0,0 +1,341 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-prometheus-grafana.md:1 +msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:3 +msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:7 +msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:33 +msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:35 +msgid "Adjusting the Grafana URL" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:37 +msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:39 +msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:41 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:48 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:50 +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:52 +msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:54 +msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:56 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:58 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:65 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:67 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:69 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`prometheus_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`prometheus_node_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_prometheus_nginxlog_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`grafana_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`grafana_anonymous_access`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:81 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:83 +msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:85 +msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:87 +msgid "Collecting metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:89 +msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:91 +msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:93 +msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:95 +msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:97 +msgid "The following variables may be of interest:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_metrics_exposure_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_metrics_exposure_http_basic_auth_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_metrics_exposure_http_basic_auth_users`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_synapse_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_synapse_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_sliding_sync_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_sliding_sync_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_bridge_hookshot_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_SERVICE_metrics_proxying_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "`matrix_media_repo_metrics_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:0 +msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:118 +msgid "Collecting Synapse worker metrics to an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:120 +msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:122 +msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:150 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:152 +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:153 +msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:154 +msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:155 +msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-grafana.md:156 +msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot new file mode 100644 index 000000000..eda234799 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot @@ -0,0 +1,109 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-prometheus-nginxlog.md:1 +msgid "Enabling metrics and graphs for NginX logs (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3 +msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5 +msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7 +msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9 +msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11 +msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13 +msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:36 +msgid "Docker Image Compatibility" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38 +msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45 +msgid "Security and privacy" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47 +msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49 +msgid "Save metrics on an external Prometheus server" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51 +msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53 +msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55 +msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57 +msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59 +msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot new file mode 100644 index 000000000..07c9456bd --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot @@ -0,0 +1,101 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-prometheus-postgres.md:1 +msgid "Enabling metrics and graphs for Postgres (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:3 +msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:5 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:7 +msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:13 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:15 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:22 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:24 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:26 +msgid "What does it do?" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "Name" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "Description" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "`prometheus_postgres_exporter_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "`prometheus_postgres_exporter_database_username`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "`prometheus_postgres_exporter_database_password`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:0 +msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:35 +msgid "More information" +msgstr "" + +#: ../../../docs/configuring-playbook-prometheus-postgres.md:37 +msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-rageshake.pot b/i18n/translation-templates/docs/configuring-playbook-rageshake.pot new file mode 100644 index 000000000..1fa606dc9 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-rageshake.pot @@ -0,0 +1,101 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-rageshake.md:1 +msgid "Setting up the rageshake bug report server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:3 +msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:5 +msgid "This is useful if you're developing your own applications and would like to collect bug reports for them." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:9 +msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:15 +msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:17 +msgid "To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:27 +msgid "Adjusting the rageshake URL" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:29 +msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:31 +msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:33 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:44 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:46 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:48 +msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:50 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:52 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:54 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:61 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:63 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:65 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-rageshake.md:67 +msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot new file mode 100644 index 000000000..732aaad20 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot @@ -0,0 +1,61 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-rest-auth.md:1 +msgid "Setting up the REST authentication password provider module (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:3 +msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:5 +msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:9 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:19 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:21 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:27 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:29 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:36 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-rest-auth.md:38 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-riot-web.pot b/i18n/translation-templates/docs/configuring-playbook-riot-web.pot new file mode 100644 index 000000000..1e11e322b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-riot-web.pot @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-riot-web.md:1 +msgid "Configuring Riot-web (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:3 +msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:5 +msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:7 +msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:8 +msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:10 +msgid "Migrating to Element Web" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:12 +msgid "Migrating your custom settings" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:14 +msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:16 +msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:18 +msgid "Domain migration" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:20 +msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:22 +msgid "There are a few options for handling this:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:24 +msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:26 +msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case." +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:28 +msgid "Re-running the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:30 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:37 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-riot-web.md:39 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot b/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot new file mode 100644 index 000000000..768310b41 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot @@ -0,0 +1,178 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-s3-goofys.md:1 +msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:5 +msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:7 +msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:9 +msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:11 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:13 +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:23 +msgid "You can use any S3-compatible object store by **additionally** configuring these variables:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:30 +msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:32 +msgid "Migrating from local filesystem storage to S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:34 +msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:36 +msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:38 +msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:39 +msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:41 +msgid "Migrating to any S3-compatible storage (universal, but likely slow)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:43 +msgid "Proceed with the steps below without stopping Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:45 +msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:47 +msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:53 +msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:55 +msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:57 +msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:63 +msgid "You may need to install `rsync` manually." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:65 +#: ../../../docs/configuring-playbook-s3-goofys.md:106 +msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:67 +msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:69 +msgid "Sync the files again by re-running the `rsync` command you see in step #5" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:71 +msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:73 +#: ../../../docs/configuring-playbook-s3-goofys.md:114 +msgid "Get the old media store out of the way by running this command on the server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:79 +msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:81 +#: ../../../docs/configuring-playbook-s3-goofys.md:122 +msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:83 +#: ../../../docs/configuring-playbook-s3-goofys.md:124 +msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:85 +#: ../../../docs/configuring-playbook-s3-goofys.md:126 +msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:87 +msgid "Migrating to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:89 +msgid "While all Matrix services are running, run the following command on the server:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:91 +msgid "(you need to adjust the 3 `--env` line below with your own data)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:104 +msgid "This is some initial file sync, which may take a very long time." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:108 +msgid "Run the command from step #1 again." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:110 +msgid "Doing this will sync any new files that may have been created locally in the meantime." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:112 +msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync." +msgstr "" + +#: ../../../docs/configuring-playbook-s3-goofys.md:120 +msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-s3.pot b/i18n/translation-templates/docs/configuring-playbook-s3.pot new file mode 100644 index 000000000..9d2b4178e --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-s3.pot @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-s3.md:1 +msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:3 +msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:5 +msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:7 +msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:9 +msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:11 +msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:13 +msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:15 +msgid "Choosing an Object Storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:17 +msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:19 +msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:21 +msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:23 +msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:25 +msgid "Here are some of the important aspects of choosing the right provider:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:27 +msgid "if a provider is a company you like and trust (or dislike less than the others)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:28 +msgid "if a provider implements end-to-end encryption of your data" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:29 +msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:30 +msgid "if a provider's infrastructure such as data center is centralized or distributed" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:31 +msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:32 +msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:34 +msgid "Bucket creation and Security Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:36 +msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:38 +msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:40 +msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:42 +msgid "Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:44 +msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:65 +msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:67 +msgid "Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:69 +msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:71 +msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:73 +msgid "After logging in to Backblaze:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:75 +msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:76 +msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:77 +msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:78 +msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:79 +msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:80 +msgid "give it *Read & Write* access" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:82 +msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:84 +msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:86 +msgid "**Endpoint URL** - this is the **Endpoint** value you saw above, but prefixed with `https://`" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:88 +msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:90 +msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:92 +msgid "Other providers" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:94 +msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:96 +msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner." +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:98 +msgid "Setting up" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:100 +msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:102 +msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:103 +msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-s3.md:104 +msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot new file mode 100644 index 000000000..b251f695c --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot @@ -0,0 +1,61 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-shared-secret-auth.md:1 +msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:3 +msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:5 +msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:9 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:18 +msgid "Authenticating only using a password provider" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:20 +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:26 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:28 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:35 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-shared-secret-auth.md:37 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot b/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot new file mode 100644 index 000000000..a6693cf74 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot @@ -0,0 +1,113 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-sliding-sync-proxy.md:1 +msgid "Setting up the Sliding Sync proxy (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 +msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 +msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 +msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 +msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 +msgid "Adjusting the Sliding Sync proxy URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19 +msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:21 +msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:48 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:52 +msgid "External databases" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54 +msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66 +msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68 +msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70 +msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot b/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot new file mode 100644 index 000000000..3a34a243f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot @@ -0,0 +1,118 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-ssl-certificates.md:1 +msgid "Adjusting SSL certificate retrieval (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:3 +msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:5 +msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:7 +msgid "Using staging Let's Encrypt certificates instead of real ones" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:9 +msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:11 +#: ../../../docs/configuring-playbook-ssl-certificates.md:21 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:17 +msgid "Disabling SSL termination" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:19 +msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:27 +msgid "Using self-signed SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:29 +msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:31 +msgid "generate your self-signed certificate files" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:32 +msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:34 +msgid "Using your own SSL certificates" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:36 +msgid "To use your own SSL certificates with Traefik, you need to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:38 +msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:39 +msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:40 +msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:41 +msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:89 +msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:91 +msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:93 +msgid "hide your public IP from Let's Encrypt logs" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:94 +msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:96 +msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:" +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:111 +msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)." +msgstr "" + +#: ../../../docs/configuring-playbook-ssl-certificates.md:113 +msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-sygnal.pot b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot new file mode 100644 index 000000000..fd9586433 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot @@ -0,0 +1,129 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-sygnal.md:1 +msgid "Setting up the Sygnal push gateway (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:3 +msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:5 +msgid "See the project's [documentation](https://github.com/matrix-org/sygnal) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:7 +msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:9 +msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:11 +msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:13 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:15 +msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:43 +msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:45 +msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:47 +msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:49 +msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:51 +msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:53 +msgid "Adjusting the Sygnal URL" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:55 +msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:57 +msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:59 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:70 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:72 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:74 +msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:76 +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:78 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:80 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:87 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:89 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:91 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:93 +msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." +msgstr "" + +#: ../../../docs/configuring-playbook-sygnal.md:95 +msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot new file mode 100644 index 000000000..e93e9cce0 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot @@ -0,0 +1,121 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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:1 +msgid "Setting up Synapse Admin (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:3 +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:5 +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:7 +msgid "💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:11 +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:17 +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:19 +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:20 +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:22 +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) - the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:24 +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:26 +msgid "Adjusting the Synapse Admin URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:28 +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:30 +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:32 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:40 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:42 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:44 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:46 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:48 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:50 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:57 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:59 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:61 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:63 +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-admin.md:65 +msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot new file mode 100644 index 000000000..f210c7393 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot @@ -0,0 +1,65 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-auto-accept-invite.md:1 +msgid "Setting up Synapse Auto Invite Accept (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 +msgid "See that project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite) to learn what it does and why it might be useful to you. In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:7 +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:9 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +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:19 +msgid "Synapse worker deployments" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +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:27 +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:29 +msgid "Native alternative" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +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:33 +msgid "Here's example configuration for using the **native** Synapse feature:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot new file mode 100644 index 000000000..1fe44a3e1 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-auto-compressor.md:1 +msgid "Setting up synapse-auto-compressor (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 +msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 +msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 +msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 +msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 +msgid "Manually start the tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 +msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot new file mode 100644 index 000000000..9bcc08ffd --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot @@ -0,0 +1,253 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-s3-storage-provider.md:1 +msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 +msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 +msgid "How it works?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 +msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 +msgid "The way media storage providers in Synapse work has some caveats:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 +msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 +msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 +msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 +msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 +msgid "You may be thinking **if all files are stored locally as well, what's the point**?" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 +msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 +msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 +msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 +msgid "new files will start being stored both locally and on the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53 +msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 +msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 +msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 +msgid "Migrating your existing media files to the S3 store" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60 +msgid "Migrating your existing data can happen in multiple ways:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 +msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 +msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 +msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 +msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69 +msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 +msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 +msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 +msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76 +msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 +msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 +msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 +msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 +msgid "The `s3_media_upload upload` command may take a lot of time to complete." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 +msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 +msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 +msgid "allows you to check and verify the output of each command, to catch mistakes" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 +msgid "includes progress bars and detailed output for each command" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 +msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 +msgid "Using another tool in combination with `s3_media_upload`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92 +msgid "To migrate your existing local data to S3, we recommend to:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 +msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 +msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 +msgid "Copying data to Amazon S3" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100 +msgid "To copy to AWS S3, start a container on the Matrix server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112 +msgid "Copying data to an S3 alternative using the aws-s3 tool" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114 +msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116 +msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118 +msgid "Copying data to Backblaze B2" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 +msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 +msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136 +msgid "Periodically cleaning up the local filesystem" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138 +msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140 +msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142 +msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143 +msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 +msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 +msgid "So.. you don't need to perform any maintenance yourself." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot new file mode 100644 index 000000000..5a3202e23 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot @@ -0,0 +1,37 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+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" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:1 +msgid "Setting up Synapse Simple Antispam (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 +msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 +msgid "See that project's documentation to learn what it does and why it might be useful to you. In short, it lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot new file mode 100644 index 000000000..18bb463a6 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot @@ -0,0 +1,105 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-usage-exporter.md:1 +msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 +msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 +msgid "Enabling this service will automatically:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9 +msgid "install the synapse-usage-exporter service" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 +msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 +msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 +msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 +msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 +msgid "Adjusting the synapse-usage-exporter URL" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 +msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 +msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45 +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 +msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse.pot b/i18n/translation-templates/docs/configuring-playbook-synapse.pot new file mode 100644 index 000000000..3f6dd4aae --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-synapse.pot @@ -0,0 +1,253 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.md:1 +msgid "Configuring Synapse (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:3 +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:5 +msgid "The playbook provides lots of customization variables you could use to change Synapse's settings." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:7 +msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:9 +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:11 +msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:13 +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:15 +msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:17 +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:19 +msgid "Load balancing with workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:21 +msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:23 +msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:31 +msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:33 +msgid "Worker presets" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:35 +msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:37 +msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:38 +msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:39 +msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:41 +msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:43 +msgid "Generic workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:45 +msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:47 +msgid "This is **still the default load-balancing method (preset) used by the playbook**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:49 +msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:51 +msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:53 +msgid "Specialized workers" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:55 +msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:57 +msgid "The playbook supports these **4 types** of specialized workers:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:59 +msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:60 +msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:61 +msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:62 +msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:64 +msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:66 +msgid "Controlling the number of worker instances" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:68 +msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:70 +msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:72 +msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:74 +msgid "Effect of enabling workers on the rest of your server" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:76 +msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:78 +msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:80 +msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:82 +msgid "Synapse Admin" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:84 +msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:86 +msgid "Synapse + OpenID Connect for Single-Sign-On" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:88 +msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:90 +msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:92 +msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:94 +msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:96 +msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:117 +msgid "Customizing templates" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:119 +msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:121 +msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:123 +msgid "If template customization is enabled, the playbook will build a custom container image based on the official one." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:125 +msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:127 +msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:153 +msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:155 +msgid "Monitoring Synapse Metrics with Prometheus and Grafana" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:157 +msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse." +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:159 +msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse.md:161 +msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-telemetry.pot b/i18n/translation-templates/docs/configuring-playbook-telemetry.pot new file mode 100644 index 000000000..e9ada53e7 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-telemetry.pot @@ -0,0 +1,49 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-telemetry.md:1 +msgid "Enabling Telemetry for your Matrix server (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:3 +msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:5 +msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:7 +msgid "Enabling Telemetry" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:9 +msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:17 +msgid "Usage statistics being submitted" +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:19 +msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook-telemetry.md:21 +msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-traefik.pot b/i18n/translation-templates/docs/configuring-playbook-traefik.pot new file mode 100644 index 000000000..e8324e3e6 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-traefik.pot @@ -0,0 +1,134 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-traefik.md:1 +msgid "Configuring the Traefik reverse-proxy (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:3 +msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:5 +msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:7 +msgid "Adjusting SSL certificate retrieval" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:9 +msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:11 +msgid "Increase logging verbosity" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:17 +msgid "Disable access logs" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:19 +msgid "This will disable access logging." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:25 +msgid "Enable Traefik Dashboard" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:27 +msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:37 +msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:39 +msgid "Additional configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:41 +msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:51 +msgid "Reverse-proxying another service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:53 +msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:55 +msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:57 +msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:59 +msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://:` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:61 +msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:63 +msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:77 +msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:91 +msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:110 +#: ../../../docs/configuring-playbook-traefik.md:133 +msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:112 +msgid "Reverse-proxying another service behind Traefik without terminating SSL" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:114 +msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:135 +msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:137 +msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:139 +msgid "Traefik behind a `proxy_protocol` reverse-proxy" +msgstr "" + +#: ../../../docs/configuring-playbook-traefik.md:141 +msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-turn.pot b/i18n/translation-templates/docs/configuring-playbook-turn.pot new file mode 100644 index 000000000..624bf85e0 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-turn.pot @@ -0,0 +1,105 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-turn.md:1 +msgid "Adjusting TURN server configuration (optional, advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:3 +msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:5 +msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:7 +msgid "Disabling Coturn" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:9 +msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:15 +msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:17 +msgid "Manually defining your public IP" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:19 +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:21 +msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:27 +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:29 +msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:36 +msgid "Changing the authentication mechanism" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:38 +msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:40 +msgid "To do so, add this override to your configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:46 +msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and Coturn." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:48 +msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:50 +msgid "Using your own external Coturn server" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:52 +msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:66 +msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:72 +msgid "You can put multiple host/port combinations if you like." +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:74 +msgid "Further variables and configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook-turn.md:75 +msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot new file mode 100644 index 000000000..85eaa0963 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-user-verification-service.md:1 +msgid "Setting up Matrix User Verification Service (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:3 +msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:5 +msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:7 +msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:9 +msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:11 +msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:13 +msgid "UVS can be used to verify two claims:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:15 +msgid "(A) Whether a given OpenID token is valid for a given server and" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:16 +msgid "(B) whether a user is member of a given room and the corresponding PowerLevel" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:18 +msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:20 +msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:24 +msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:26 +msgid "Enable" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:28 +msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:34 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:36 +msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:38 +msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:40 +msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:42 +msgid "Access token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:44 +msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:46 +msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:48 +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:50 +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:56 +msgid "(Optional) Custom Auth Token" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:58 +msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\"" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:60 +msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:62 +msgid "To set your own Token, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:68 +msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:70 +msgid "(Optional) Disable Auth" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:72 +msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:78 +msgid "(Optional) Federation" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:80 +msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:86 +msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:88 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:90 +msgid "After these variables have been set, run the playbook with [playbook tags](playbook-tags.md) as below to restart UVS:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:96 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-matrix-user-verification-service,start` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:98 +msgid "`just run-tags setup-matrix-user-verification-service,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-user-verification-service.md:100 +msgid "Logging" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:102 +msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:103 +msgid "warning" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:104 +msgid "info" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:105 +msgid "debug" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:107 +msgid "TLS Certificate Checking" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:109 +msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:111 +msgid "message: 'No response received: [object Object]'," +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:113 +msgid "This also applies to self-signed and let's encrypt staging certificates." +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:115 +msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" +msgstr "" + +#: ../../../docs/configuring-playbook-user-verification-service.md:117 +msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook.pot b/i18n/translation-templates/docs/configuring-playbook.pot new file mode 100644 index 000000000..33265200b --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook.pot @@ -0,0 +1,529 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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.md:1 +msgid "Configuring the playbook" +msgstr "" + +#: ../../../docs/configuring-playbook.md:3 +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:5 +msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:7 +msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")" +msgstr "" + +#: ../../../docs/configuring-playbook.md:9 +msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:11 +msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file." +msgstr "" + +#: ../../../docs/configuring-playbook.md:13 +msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:15 +msgid "edit the inventory hosts file (`inventory/hosts`) to your liking" +msgstr "" + +#: ../../../docs/configuring-playbook.md:17 +msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system." +msgstr "" + +#: ../../../docs/configuring-playbook.md:19 +msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:21 +msgid "For a basic Matrix installation, that's all you need." +msgstr "" + +#: ../../../docs/configuring-playbook.md:23 +msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below." +msgstr "" + +#: ../../../docs/configuring-playbook.md:25 +msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:27 +msgid "Other configuration options" +msgstr "" + +#: ../../../docs/configuring-playbook.md:29 +msgid "Core service adjustments" +msgstr "" + +#: ../../../docs/configuring-playbook.md:31 +msgid "Homeserver configuration:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:32 +msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:34 +msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:36 +msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation" +msgstr "" + +#: ../../../docs/configuring-playbook.md:38 +msgid "Server components:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:39 +msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:41 +msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:43 +msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:45 +msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:47 +msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:49 +msgid "[Adjusting email-sending settings](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:51 +msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:53 +msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:55 +msgid "Server connectivity:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:56 +msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:58 +msgid "[Controlling Matrix federation](configuring-playbook-federation.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:60 +msgid "Clients" +msgstr "" + +#: ../../../docs/configuring-playbook.md:62 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/configuring-playbook.md:64 +msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client" +msgstr "" + +#: ../../../docs/configuring-playbook.md:66 +msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/configuring-playbook.md:68 +msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface" +msgstr "" + +#: ../../../docs/configuring-playbook.md:70 +msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:72 +msgid "Authentication and user-related" +msgstr "" + +#: ../../../docs/configuring-playbook.md:74 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/configuring-playbook.md:76 +msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:78 +msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:80 +msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:82 +msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:84 +msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:86 +msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:88 +msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:90 +msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:92 +msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:94 +msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:96 +msgid "File Storage" +msgstr "" + +#: ../../../docs/configuring-playbook.md:98 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/configuring-playbook.md:100 +msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:102 +msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:104 +msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:106 +msgid "Bridging other networks" +msgstr "" + +#: ../../../docs/configuring-playbook.md:108 +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." +msgstr "" + +#: ../../../docs/configuring-playbook.md:110 +msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:112 +msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:114 +msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:116 +msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:118 +msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:120 +msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:122 +msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:124 +msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:126 +msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:128 +msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:130 +msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:132 +msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:134 +msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:136 +msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:138 +msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:140 +msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:142 +msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)." +msgstr "" + +#: ../../../docs/configuring-playbook.md:144 +msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:146 +msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:148 +msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:150 +msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:152 +msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:154 +msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:156 +msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:158 +msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:160 +msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:162 +msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:164 +msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:166 +msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:168 +msgid "Bots" +msgstr "" + +#: ../../../docs/configuring-playbook.md:170 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:172 +msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:174 +msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff" +msgstr "" + +#: ../../../docs/configuring-playbook.md:176 +msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users" +msgstr "" + +#: ../../../docs/configuring-playbook.md:178 +msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system" +msgstr "" + +#: ../../../docs/configuring-playbook.md:180 +msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:182 +msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot" +msgstr "" + +#: ../../../docs/configuring-playbook.md:184 +msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer" +msgstr "" + +#: ../../../docs/configuring-playbook.md:186 +msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances" +msgstr "" + +#: ../../../docs/configuring-playbook.md:188 +msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgstr "" + +#: ../../../docs/configuring-playbook.md:190 +msgid "Administration" +msgstr "" + +#: ../../../docs/configuring-playbook.md:192 +msgid "Services that help you in administrating and monitoring your Matrix installation." +msgstr "" + +#: ../../../docs/configuring-playbook.md:194 +msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:196 +msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:198 +msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:200 +msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:202 +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:204 +msgid "Backups:" +msgstr "" + +#: ../../../docs/configuring-playbook.md:205 +msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database" +msgstr "" + +#: ../../../docs/configuring-playbook.md:207 +msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:209 +msgid "Other specialized services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:211 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/configuring-playbook.md:213 +msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:215 +msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers" +msgstr "" + +#: ../../../docs/configuring-playbook.md:217 +msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:219 +msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:221 +msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:223 +msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook.md:225 +msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:227 +msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:229 +msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:231 +msgid "Deprecated / unmaintained / removed services" +msgstr "" + +#: ../../../docs/configuring-playbook.md:233 +msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless." +msgstr "" + +#: ../../../docs/configuring-playbook.md:235 +msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:237 +msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:239 +msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:241 +msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:243 +msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:245 +msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:247 +msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:249 +msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" +msgstr "" + +#: ../../../docs/configuring-playbook.md:251 +msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-well-known.pot b/i18n/translation-templates/docs/configuring-well-known.pot new file mode 100644 index 000000000..157258f8f --- /dev/null +++ b/i18n/translation-templates/docs/configuring-well-known.pot @@ -0,0 +1,253 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \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-well-known.md:1 +msgid "Configuring Service Discovery via .well-known" +msgstr "" + +#: ../../../docs/configuring-well-known.md:3 +msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is." +msgstr "" + +#: ../../../docs/configuring-well-known.md:5 +msgid "Types of well-known service discovery mechanism" +msgstr "" + +#: ../../../docs/configuring-well-known.md:7 +msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:9 +msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/configuring-well-known.md:11 +msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses." +msgstr "" + +#: ../../../docs/configuring-well-known.md:13 +msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain." +msgstr "" + +#: ../../../docs/configuring-well-known.md:15 +msgid "Federation Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:17 +msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:19 +msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection." +msgstr "" + +#: ../../../docs/configuring-well-known.md:21 +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:23 +msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/configuring-well-known.md:25 +msgid "Client Server Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:27 +msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:29 +msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username." +msgstr "" + +#: ../../../docs/configuring-well-known.md:31 +msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:33 +msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:35 +msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file." +msgstr "" + +#: ../../../docs/configuring-well-known.md:37 +msgid "(Optional) Support Service Discovery" +msgstr "" + +#: ../../../docs/configuring-well-known.md:39 +msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc." +msgstr "" + +#: ../../../docs/configuring-well-known.md:41 +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:62 +msgid "Installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:64 +msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver." +msgstr "" + +#: ../../../docs/configuring-well-known.md:66 +msgid "Serving the base domain from the Matrix server via the playbook" +msgstr "" + +#: ../../../docs/configuring-well-known.md:68 +msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it." +msgstr "" + +#: ../../../docs/configuring-well-known.md:70 +msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically." +msgstr "" + +#: ../../../docs/configuring-well-known.md:72 +msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up." +msgstr "" + +#: ../../../docs/configuring-well-known.md:74 +msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below." +msgstr "" + +#: ../../../docs/configuring-well-known.md:76 +msgid "Manually installing well-known files on the base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:78 +msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:80 +msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them." +msgstr "" + +#: ../../../docs/configuring-well-known.md:82 +msgid "You have two options when it comes to installing the files on the base domain's server:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:84 +msgid "(Option 1): **Copying the files manually** to your base domain's server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:86 +msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible." +msgstr "" + +#: ../../../docs/configuring-well-known.md:88 +msgid "All you need to do is:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:90 +msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:92 +msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS." +msgstr "" + +#: ../../../docs/configuring-well-known.md:94 +msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again." +msgstr "" + +#: ../../../docs/configuring-well-known.md:96 +msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server" +msgstr "" + +#: ../../../docs/configuring-well-known.md:98 +msgid "This option is less fragile and generally better." +msgstr "" + +#: ../../../docs/configuring-well-known.md:100 +msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." +msgstr "" + +#: ../../../docs/configuring-well-known.md:102 +msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly." +msgstr "" + +#: ../../../docs/configuring-well-known.md:104 +msgid "**For nginx**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:121 +msgid "**For Apache2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:135 +msgid "**For Caddy 2**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:145 +msgid "**For HAProxy**, it would be something like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:164 +msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:170 +msgid "**For AWS CloudFront**" +msgstr "" + +#: ../../../docs/configuring-well-known.md:172 +msgid "Add a custom origin with matrix.example.com to your distribution" +msgstr "" + +#: ../../../docs/configuring-well-known.md:173 +msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin." +msgstr "" + +#: ../../../docs/configuring-well-known.md:175 +msgid "Make sure to:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:177 +msgid "**replace `example.com`** in the server configuration with your actual domain name" +msgstr "" + +#: ../../../docs/configuring-well-known.md:178 +msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be" +msgstr "" + +#: ../../../docs/configuring-well-known.md:180 +msgid "Confirming it works" +msgstr "" + +#: ../../../docs/configuring-well-known.md:182 +msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:" +msgstr "" + +#: ../../../docs/configuring-well-known.md:184 +msgid "`https://example.com/.well-known/matrix/server`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:185 +msgid "`https://example.com/.well-known/matrix/client`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:186 +msgid "`https://example.com/.well-known/matrix/support`" +msgstr "" + +#: ../../../docs/configuring-well-known.md:188 +msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)." +msgstr "" diff --git a/i18n/translation-templates/docs/container-images.pot b/i18n/translation-templates/docs/container-images.pot new file mode 100644 index 000000000..a944a484a --- /dev/null +++ b/i18n/translation-templates/docs/container-images.pot @@ -0,0 +1,1153 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/container-images.md:1 +msgid "Container images used by the playbook" +msgstr "" + +#: ../../../docs/container-images.md:3 +msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server." +msgstr "" + +#: ../../../docs/container-images.md:5 +msgid "We try to stick to official images (provided by their respective projects) as much as possible." +msgstr "" + +#: ../../../docs/container-images.md:7 +msgid "Homeserver" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Service" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Container image" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Default?" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Description" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Synapse](configuring-playbook-synapse.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "✅" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Conduit](configuring-playbook-conduit.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "❌" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Dendrite](configuring-playbook-dendrite.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." +msgstr "" + +#: ../../../docs/container-images.md:15 +msgid "Clients" +msgstr "" + +#: ../../../docs/container-images.md:17 +msgid "Web clients for Matrix that you can host on your own domains." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Element Web](configuring-playbook-client-element-web.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Default Matrix web client, configured to connect to your own Synapse server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Lightweight Matrix client with legacy and mobile browser support" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Cinny](configuring-playbook-client-cinny.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Simple, elegant and secure web client" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Based on Element Web, with a more traditional instant messaging experience" +msgstr "" + +#: ../../../docs/container-images.md:26 +msgid "Server Components" +msgstr "" + +#: ../../../docs/container-images.md:28 +msgid "Services that run on the server to make the various parts of your installation work." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[PostgreSQL](configuring-playbook-external-postgres.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[postgres](https://hub.docker.com/_/postgres/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Coturn](configuring-playbook-turn.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "STUN/TURN server for WebRTC audio/video calls" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Traefik](configuring-playbook-traefik.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Traefik](https://hub.docker.com/_/traefik/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Exim](configuring-playbook-email.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ma1sd](configuring-playbook-ma1sd.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Matrix Identity Server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ddclient](configuring-playbook-dynamic-dns.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider" +msgstr "" + +#: ../../../docs/container-images.md:40 +msgid "Authentication" +msgstr "" + +#: ../../../docs/container-images.md:42 +msgid "Extend and modify how users are authenticated on your homeserver." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "(N/A)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "REST authentication password provider module" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Password provider module" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "LDAP Auth password provider module" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-registration](configuring-playbook-matrix-registration.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A simple python application to have a token based Matrix registration" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Service to verify details of a user based on an Open ID token" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A spam checker module" +msgstr "" + +#: ../../../docs/container-images.md:54 +msgid "File Storage" +msgstr "" + +#: ../../../docs/container-images.md:56 +msgid "Use alternative file storage to the default `media_store` folder." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Goofys](configuring-playbook-s3-goofys.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." +msgstr "" + +#: ../../../docs/container-images.md:64 +msgid "Bridges" +msgstr "" + +#: ../../../docs/container-images.md:66 +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Discord](https://discord.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Slack](https://slack.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Telegram](https://telegram.org/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Google Messages](https://messages.google.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to Android SMS or Apple iMessage" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Twitter](https://twitter.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Signal](https://www.signal.org/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [LinkedIn](https://www.linkedin.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Self-building" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Discord](https://discordapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to SMS" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [WeChat](https://www.wechat.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Skype](https://www.skype.com)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Slack](https://slack.com)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [GroupMe](https://groupme.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Steam](https://steamapp.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Email2Matrix](configuring-playbook-email2matrix.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge for relaying emails to Matrix rooms" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Email to Matrix bridge" +msgstr "" + +#: ../../../docs/container-images.md:99 +msgid "Bots" +msgstr "" + +#: ../../../docs/container-images.md:101 +msgid "Bots provide various additional functionality to your installation." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[baibot](configuring-playbook-bot-baibot.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bot for scheduling one-off & recurring reminders and alarms" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bot for invitations by creating and managing registration tokens" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[maubot](configuring-playbook-bot-maubot.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A plugin-based Matrix bot system" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Honoroit](configuring-playbook-bot-honoroit.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A helpdesk bot" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A moderation tool for Matrix" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Draupnir](configuring-playbook-bot-draupnir.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A moderation tool for Matrix (Fork of Mjolnir)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Buscarron](configuring-playbook-bot-buscarron.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Web forms (HTTP POST) to Matrix" +msgstr "" + +#: ../../../docs/container-images.md:114 +msgid "Administration" +msgstr "" + +#: ../../../docs/container-images.md:116 +msgid "Services that help you in administrating and monitoring your Matrix installation." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "OAuth 2.0 and OpenID Provider server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse-admin](configuring-playbook-synapse-admin.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A web UI tool for administrating users and rooms on your Matrix server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Prometheus](https://prometheus.io) time-series database server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Borg](configuring-playbook-backup-borg.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Backups" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[rageshake](configuring-playbook-rageshake.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bug report server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." +msgstr "" + +#: ../../../docs/container-images.md:131 +msgid "Misc" +msgstr "" + +#: ../../../docs/container-images.md:133 +msgid "Various services that don't fit any other categories." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A Synapse module to automatically accept invites." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A cli tool that automatically compresses `state_groups` database table in background." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Reconciliator and gateway for a managed Matrix server" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Etherpad](configuring-playbook-etherpad.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "An open source collaborative text editor" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Jitsi](configuring-playbook-jitsi.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "the [Jitsi](https://jitsi.org/) web UI" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "the [Jitsi](https://jitsi.org/) Focus component" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "the [Jitsi](https://jitsi.org/) Video Bridge component" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A federated comment system built on Matrix" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "An E2EE aware proxy daemon" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Sygnal](configuring-playbook-sygnal.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Reference Push Gateway for Matrix" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[ntfy](configuring-playbook-ntfy.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Self-hosted, UnifiedPush-compatible push notifications server" +msgstr "" + +#: ../../../docs/container-images.md:152 +msgid "Container images of deprecated / unmaintained services" +msgstr "" + +#: ../../../docs/container-images.md:154 +msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Dimension](configuring-playbook-dimension.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "An open source integration manager for Matrix clients" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "A multi functional bot written in Go" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Accessing ChatGPT via your favourite Matrix client" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Facebook](https://facebook.com/)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Bridge to [Instagram](https://instagram.com/)" +msgstr "" diff --git a/i18n/translation-templates/docs/faq.pot b/i18n/translation-templates/docs/faq.pot new file mode 100644 index 000000000..a64544234 --- /dev/null +++ b/i18n/translation-templates/docs/faq.pot @@ -0,0 +1,874 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/faq.md:1 +msgid "Frequently Asked Questions" +msgstr "" + +#: ../../../docs/faq.md:3 +msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))." +msgstr "" + +#: ../../../docs/faq.md:5 +msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)." +msgstr "" + +#: ../../../docs/faq.md:7 +msgid "We've only started this FAQ recently, so it's still somewhat empty." +msgstr "" + +#: ../../../docs/faq.md:9 +msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides." +msgstr "" + +#: ../../../docs/faq.md:11 +msgid "Introductory" +msgstr "" + +#: ../../../docs/faq.md:13 +msgid "Where do I find more questions and answers about Matrix?" +msgstr "" + +#: ../../../docs/faq.md:15 +msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server." +msgstr "" + +#: ../../../docs/faq.md:17 +msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:19 +msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?" +msgstr "" + +#: ../../../docs/faq.md:21 +msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"." +msgstr "" + +#: ../../../docs/faq.md:23 +msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)." +msgstr "" + +#: ../../../docs/faq.md:25 +msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)." +msgstr "" + +#: ../../../docs/faq.md:27 +msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)." +msgstr "" + +#: ../../../docs/faq.md:29 +msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android." +msgstr "" + +#: ../../../docs/faq.md:31 +msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse." +msgstr "" + +#: ../../../docs/faq.md:33 +msgid "In short:" +msgstr "" + +#: ../../../docs/faq.md:35 +msgid "Matrix is the protocol - a set of rules about how the chat network operates" +msgstr "" + +#: ../../../docs/faq.md:36 +msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)." +msgstr "" + +#: ../../../docs/faq.md:37 +msgid "Synapse is a server program you can use to host your very own Matrix server." +msgstr "" + +#: ../../../docs/faq.md:39 +msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)." +msgstr "" + +#: ../../../docs/faq.md:41 +msgid "People I wish to talk to are not on Matrix. Can I talk to them?" +msgstr "" + +#: ../../../docs/faq.md:43 +msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it." +msgstr "" + +#: ../../../docs/faq.md:45 +msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)." +msgstr "" + +#: ../../../docs/faq.md:47 +msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." +msgstr "" + +#: ../../../docs/faq.md:49 +msgid "How do I get started with Matrix?" +msgstr "" + +#: ../../../docs/faq.md:51 +msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)." +msgstr "" + +#: ../../../docs/faq.md:53 +msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:" +msgstr "" + +#: ../../../docs/faq.md:55 +msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting." +msgstr "" + +#: ../../../docs/faq.md:57 +msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login." +msgstr "" + +#: ../../../docs/faq.md:59 +msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)." +msgstr "" + +#: ../../../docs/faq.md:61 +msgid "How do I set up my own Matrix server?" +msgstr "" + +#: ../../../docs/faq.md:63 +msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:65 +msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it." +msgstr "" + +#: ../../../docs/faq.md:67 +msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually." +msgstr "" + +#: ../../../docs/faq.md:69 +msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)." +msgstr "" + +#: ../../../docs/faq.md:71 +msgid "What is Ansible? How does it work?" +msgstr "" + +#: ../../../docs/faq.md:73 +msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually." +msgstr "" + +#: ../../../docs/faq.md:75 +msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program." +msgstr "" + +#: ../../../docs/faq.md:77 +msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer." +msgstr "" + +#: ../../../docs/faq.md:79 +msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server." +msgstr "" + +#: ../../../docs/faq.md:81 +msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)." +msgstr "" + +#: ../../../docs/faq.md:83 +msgid "What is `just`?" +msgstr "" + +#: ../../../docs/faq.md:85 +msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing." +msgstr "" + +#: ../../../docs/faq.md:87 +msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)." +msgstr "" + +#: ../../../docs/faq.md:89 +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/faq.md:91 +msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`." +msgstr "" + +#: ../../../docs/faq.md:93 +msgid "Why use this playbook and not install Synapse and other things manually?" +msgstr "" + +#: ../../../docs/faq.md:95 +msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)." +msgstr "" + +#: ../../../docs/faq.md:97 +msgid "Reading the documentation of this Ansible playbook, you may also be thinking:" +msgstr "" + +#: ../../../docs/faq.md:99 +msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated." +msgstr "" + +#: ../../../docs/faq.md:101 +msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." +msgstr "" + +#: ../../../docs/faq.md:103 +msgid "The problem with a manual installation is:" +msgstr "" + +#: ../../../docs/faq.md:105 +msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated." +msgstr "" + +#: ../../../docs/faq.md:106 +msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well." +msgstr "" + +#: ../../../docs/faq.md:107 +msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that" +msgstr "" + +#: ../../../docs/faq.md:108 +msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software." +msgstr "" + +#: ../../../docs/faq.md:109 +msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works." +msgstr "" + +#: ../../../docs/faq.md:110 +msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability" +msgstr "" + +#: ../../../docs/faq.md:112 +msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together." +msgstr "" + +#: ../../../docs/faq.md:114 +msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging." +msgstr "" + +#: ../../../docs/faq.md:116 +msgid "Why use this playbook and not just use the Docker image directly?" +msgstr "" + +#: ../../../docs/faq.md:118 +msgid "Reasons are similar to the reasons for not installing manually." +msgstr "" + +#: ../../../docs/faq.md:120 +msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc." +msgstr "" + +#: ../../../docs/faq.md:122 +msgid "Using the playbook, you get all these components in a way that works well together out of the box." +msgstr "" + +#: ../../../docs/faq.md:124 +msgid "Occasionally I see some people are talking about \"MDAD\". What is it?" +msgstr "" + +#: ../../../docs/faq.md:126 +msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." +msgstr "" + +#: ../../../docs/faq.md:128 +msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?" +msgstr "" + +#: ../../../docs/faq.md:130 +msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:" +msgstr "" + +#: ../../../docs/faq.md:132 +msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible" +msgstr "" + +#: ../../../docs/faq.md:134 +msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)" +msgstr "" + +#: ../../../docs/faq.md:136 +msgid "this one **can be executed more than once** without causing trouble" +msgstr "" + +#: ../../../docs/faq.md:138 +msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" +msgstr "" + +#: ../../../docs/faq.md:140 +msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place" +msgstr "" + +#: ../../../docs/faq.md:142 +msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)" +msgstr "" + +#: ../../../docs/faq.md:144 +msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))" +msgstr "" + +#: ../../../docs/faq.md:146 +msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you" +msgstr "" + +#: ../../../docs/faq.md:148 +msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)" +msgstr "" + +#: ../../../docs/faq.md:150 +msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)" +msgstr "" + +#: ../../../docs/faq.md:152 +msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)" +msgstr "" + +#: ../../../docs/faq.md:154 +msgid "this one is actually **maintained**" +msgstr "" + +#: ../../../docs/faq.md:156 +msgid "Server-related" +msgstr "" + +#: ../../../docs/faq.md:158 +msgid "What kind of server do I need to install Matrix using this Ansible playbook?" +msgstr "" + +#: ../../../docs/faq.md:160 +msgid "We list our server requirements in [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/faq.md:162 +msgid "Why not run Matrix on Kubernetes?" +msgstr "" + +#: ../../../docs/faq.md:164 +msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)." +msgstr "" + +#: ../../../docs/faq.md:166 +msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home." +msgstr "" + +#: ../../../docs/faq.md:168 +msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go." +msgstr "" + +#: ../../../docs/faq.md:170 +msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart." +msgstr "" + +#: ../../../docs/faq.md:172 +msgid "Why don't you use Podman instead of Docker?" +msgstr "" + +#: ../../../docs/faq.md:174 +msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet." +msgstr "" + +#: ../../../docs/faq.md:176 +msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)." +msgstr "" + +#: ../../../docs/faq.md:178 +msgid "In short, `alias podman=docker` is a lie (for us)." +msgstr "" + +#: ../../../docs/faq.md:180 +msgid "Why use Docker?" +msgstr "" + +#: ../../../docs/faq.md:182 +msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))." +msgstr "" + +#: ../../../docs/faq.md:184 +msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions." +msgstr "" + +#: ../../../docs/faq.md:186 +msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))." +msgstr "" + +#: ../../../docs/faq.md:188 +msgid "Is Docker a hard requirement?" +msgstr "" + +#: ../../../docs/faq.md:190 +msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime." +msgstr "" + +#: ../../../docs/faq.md:192 +msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros." +msgstr "" + +#: ../../../docs/faq.md:194 +msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)." +msgstr "" + +#: ../../../docs/faq.md:196 +msgid "Why don't you use docker-compose?" +msgstr "" + +#: ../../../docs/faq.md:198 +msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently." +msgstr "" + +#: ../../../docs/faq.md:200 +msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element." +msgstr "" + +#: ../../../docs/faq.md:202 +msgid "Can I run this on a distro without systemd?" +msgstr "" + +#: ../../../docs/faq.md:204 +msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))." +msgstr "" + +#: ../../../docs/faq.md:206 +msgid "Can I install this on a Raspberry Pi?" +msgstr "" + +#: ../../../docs/faq.md:208 +msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page." +msgstr "" + +#: ../../../docs/faq.md:210 +msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case." +msgstr "" + +#: ../../../docs/faq.md:212 +msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)." +msgstr "" + +#: ../../../docs/faq.md:214 +msgid "What kind of server specs do I need?" +msgstr "" + +#: ../../../docs/faq.md:216 +msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join." +msgstr "" + +#: ../../../docs/faq.md:218 +msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise." +msgstr "" + +#: ../../../docs/faq.md:220 +msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)." +msgstr "" + +#: ../../../docs/faq.md:222 +msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)." +msgstr "" + +#: ../../../docs/faq.md:224 +msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea." +msgstr "" + +#: ../../../docs/faq.md:226 +msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." +msgstr "" + +#: ../../../docs/faq.md:228 +msgid "Can I run this in an LXC container?" +msgstr "" + +#: ../../../docs/faq.md:230 +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/faq.md:232 +msgid "Configuration" +msgstr "" + +#: ../../../docs/faq.md:234 +msgid "Why install my server at matrix.example.com and not at the base domain?" +msgstr "" + +#: ../../../docs/faq.md:236 +msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work." +msgstr "" + +#: ../../../docs/faq.md:238 +msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default." +msgstr "" + +#: ../../../docs/faq.md:240 +msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?" +msgstr "" + +#: ../../../docs/faq.md:242 +msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:244 +msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?" +msgstr "" + +#: ../../../docs/faq.md:246 +msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:248 +msgid "How do I install on matrix.example.com without involving the base domain?" +msgstr "" + +#: ../../../docs/faq.md:250 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:271 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/faq.md:278 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/faq.md:280 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/faq.md:282 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/faq.md:284 +msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`." +msgstr "" + +#: ../../../docs/faq.md:286 +msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?" +msgstr "" + +#: ../../../docs/faq.md:288 +msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))." +msgstr "" + +#: ../../../docs/faq.md:290 +msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)." +msgstr "" + +#: ../../../docs/faq.md:292 +msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)." +msgstr "" + +#: ../../../docs/faq.md:294 +msgid "How do I optimize this setup for a low-power server?" +msgstr "" + +#: ../../../docs/faq.md:296 +msgid "You can disable some not-so-important services to save on memory." +msgstr "" + +#: ../../../docs/faq.md:318 +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" +msgstr "" + +#: ../../../docs/faq.md:328 +msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." +msgstr "" + +#: ../../../docs/faq.md:330 +msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" +msgstr "" + +#: ../../../docs/faq.md:332 +msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" +msgstr "" + +#: ../../../docs/faq.md:338 +msgid "I run another webserver on the same server where I wish to install Matrix. What now?" +msgstr "" + +#: ../../../docs/faq.md:340 +msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)." +msgstr "" + +#: ../../../docs/faq.md:342 +msgid "How is the effective configuration determined?" +msgstr "" + +#: ../../../docs/faq.md:344 +msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:" +msgstr "" + +#: ../../../docs/faq.md:346 +msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." +msgstr "" + +#: ../../../docs/faq.md:348 +msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." +msgstr "" + +#: ../../../docs/faq.md:350 +msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" +msgstr "" + +#: ../../../docs/faq.md:352 +msgid "What configuration variables are available?" +msgstr "" + +#: ../../../docs/faq.md:354 +msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." +msgstr "" + +#: ../../../docs/faq.md:356 +msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`." +msgstr "" + +#: ../../../docs/faq.md:358 +msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." +msgstr "" + +#: ../../../docs/faq.md:360 +#: ../../../docs/faq.md:372 +msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." +msgstr "" + +#: ../../../docs/faq.md:362 +msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" +msgstr "" + +#: ../../../docs/faq.md:364 +msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." +msgstr "" + +#: ../../../docs/faq.md:366 +msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." +msgstr "" + +#: ../../../docs/faq.md:368 +msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." +msgstr "" + +#: ../../../docs/faq.md:370 +msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it." +msgstr "" + +#: ../../../docs/faq.md:374 +msgid "Installation" +msgstr "" + +#: ../../../docs/faq.md:376 +msgid "How do I run the installation?" +msgstr "" + +#: ../../../docs/faq.md:378 +msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." +msgstr "" + +#: ../../../docs/faq.md:380 +msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." +msgstr "" + +#: ../../../docs/faq.md:382 +msgid "There are two guides available:" +msgstr "" + +#: ../../../docs/faq.md:384 +msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." +msgstr "" + +#: ../../../docs/faq.md:386 +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." +msgstr "" + +#: ../../../docs/faq.md:388 +msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" +msgstr "" + +#: ../../../docs/faq.md:390 +msgid "Yes, you can." +msgstr "" + +#: ../../../docs/faq.md:392 +msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." +msgstr "" + +#: ../../../docs/faq.md:394 +msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup - [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" +msgstr "" + +#: ../../../docs/faq.md:396 +msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." +msgstr "" + +#: ../../../docs/faq.md:398 +msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." +msgstr "" + +#: ../../../docs/faq.md:400 +msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." +msgstr "" + +#: ../../../docs/faq.md:402 +msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." +msgstr "" + +#: ../../../docs/faq.md:404 +msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible." +msgstr "" + +#: ../../../docs/faq.md:406 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/faq.md:408 +msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`." +msgstr "" + +#: ../../../docs/faq.md:410 +msgid "See [How can I see the logs?](#how-can-i-see-the-logs)." +msgstr "" + +#: ../../../docs/faq.md:412 +msgid "How can I see the logs?" +msgstr "" + +#: ../../../docs/faq.md:414 +msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging." +msgstr "" + +#: ../../../docs/faq.md:416 +msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)." +msgstr "" + +#: ../../../docs/faq.md:418 +msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server." +msgstr "" + +#: ../../../docs/faq.md:420 +msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." +msgstr "" + +#: ../../../docs/faq.md:422 +msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files." +msgstr "" + +#: ../../../docs/faq.md:424 +msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." +msgstr "" + +#: ../../../docs/faq.md:426 +msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)" +msgstr "" + +#: ../../../docs/faq.md:428 +msgid "How long do systemd/journald logs persist for?" +msgstr "" + +#: ../../../docs/faq.md:430 +msgid "On some distros, the journald logs are just in-memory and not persisted to disk." +msgstr "" + +#: ../../../docs/faq.md:432 +msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." +msgstr "" + +#: ../../../docs/faq.md:434 +msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" +msgstr "" + +#: ../../../docs/faq.md:445 +msgid "Maintenance" +msgstr "" + +#: ../../../docs/faq.md:447 +msgid "Do I need to do anything to keep my Matrix server updated?" +msgstr "" + +#: ../../../docs/faq.md:449 +msgid "Yes. We don't update anything for you automatically." +msgstr "" + +#: ../../../docs/faq.md:451 +msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../docs/faq.md:453 +msgid "How do I move my existing installation to another (VM) server?" +msgstr "" + +#: ../../../docs/faq.md:455 +msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)." +msgstr "" + +#: ../../../docs/faq.md:457 +msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." +msgstr "" + +#: ../../../docs/faq.md:459 +msgid "How do I back up the data on my server?" +msgstr "" + +#: ../../../docs/faq.md:461 +msgid "We haven't documented this properly yet, but the general advice is to:" +msgstr "" + +#: ../../../docs/faq.md:463 +msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" +msgstr "" + +#: ../../../docs/faq.md:465 +msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +msgstr "" + +#: ../../../docs/faq.md:467 +msgid "You can later restore these by:" +msgstr "" + +#: ../../../docs/faq.md:469 +msgid "Restoring the `/matrix` directory and files on the new server manually" +msgstr "" + +#: ../../../docs/faq.md:470 +msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)" +msgstr "" + +#: ../../../docs/faq.md:472 +msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again." +msgstr "" + +#: ../../../docs/faq.md:474 +msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?" +msgstr "" + +#: ../../../docs/faq.md:476 +msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong." +msgstr "" + +#: ../../../docs/faq.md:478 +msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`" +msgstr "" + +#: ../../../docs/faq.md:480 +msgid "How do I debug or force SSL certificate renewal?" +msgstr "" + +#: ../../../docs/faq.md:482 +msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server." +msgstr "" + +#: ../../../docs/faq.md:484 +msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)." +msgstr "" + +#: ../../../docs/faq.md:486 +msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." +msgstr "" diff --git a/i18n/translation-templates/docs/getting-the-playbook.pot b/i18n/translation-templates/docs/getting-the-playbook.pot new file mode 100644 index 000000000..e931dc6d9 --- /dev/null +++ b/i18n/translation-templates/docs/getting-the-playbook.pot @@ -0,0 +1,81 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/getting-the-playbook.md:1 +msgid "Getting the playbook" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:3 +msgid "[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:5 +msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:7 +msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:9 +msgid "You can retrieve the playbook's source code by:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:11 +msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:13 +msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:15 +msgid "Using git to get the playbook" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:17 +msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:19 +msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:25 +msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:27 +msgid "Downloading the playbook as a ZIP archive" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:29 +msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:31 +msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip" +msgstr "" + +#: ../../../docs/getting-the-playbook.md:33 +msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory." +msgstr "" + +#: ../../../docs/getting-the-playbook.md:37 +msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)." +msgstr "" diff --git a/i18n/translation-templates/docs/howto-server-delegation.pot b/i18n/translation-templates/docs/howto-server-delegation.pot new file mode 100644 index 000000000..45d19bc5a --- /dev/null +++ b/i18n/translation-templates/docs/howto-server-delegation.pot @@ -0,0 +1,185 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/howto-server-delegation.md:1 +msgid "Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:3 +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:5 +msgid "Server delegation can be configured in either of these ways:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:7 +msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:8 +msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:10 +msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:12 +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:14 +msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:16 +msgid "Server Delegation via a well-known file" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:18 +msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:20 +msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:22 +msgid "Downsides of well-known-based Server Delegation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:24 +msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:26 +msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:28 +msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:30 +msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:32 +msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:34 +msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:36 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:38 +msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:40 +msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:42 +msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:44 +msgid "To use DNS SRV record validation, you need to:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:46 +msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:48 +msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:50 +msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:52 +msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:54 +msgid "Obtaining certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:56 +msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:58 +msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:60 +msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:62 +msgid "Serving the Federation API with your certificates" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:64 +msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:66 +msgid "Based on your setup, you have different ways to go about it:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:68 +msgid "Serving the Federation API with your certificates and Synapse handling Federation" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:70 +msgid "You can let Synapse handle Federation by itself." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:72 +msgid "To do that, make sure the certificate files are mounted into the Synapse container:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:79 +msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:87 +msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:89 +msgid "Serving the Federation API with your certificates and another webserver" +msgstr "" + +#: ../../../docs/howto-server-delegation.md:91 +msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port." +msgstr "" + +#: ../../../docs/howto-server-delegation.md:93 +msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there." +msgstr "" diff --git a/i18n/translation-templates/docs/howto-srv-server-delegation.pot b/i18n/translation-templates/docs/howto-srv-server-delegation.pot new file mode 100644 index 000000000..a8f731254 --- /dev/null +++ b/i18n/translation-templates/docs/howto-srv-server-delegation.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/howto-srv-server-delegation.md:1 +msgid "Server Delegation via a DNS SRV record (advanced)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:3 +msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:5 +msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:9 +msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:11 +msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:13 +msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:15 +msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:17 +msgid "The changes" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:19 +msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:21 +msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:22 +msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:24 +msgid "Also, all instructions below are from an older version of the playbook and may not work anymore." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:26 +msgid "Federation Endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:33 +msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:35 +msgid "Tell Traefik which certificate to serve for the federation endpoint" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:37 +msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:39 +msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:48 +msgid "Configure the DNS-01 challenge for let's encrypt" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:50 +msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:52 +msgid "This will need 3 changes:" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:53 +msgid "Add a new certificate resolver that works with DNS-01" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:54 +msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:55 +msgid "Tell the playbook to use the new resolver as default" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:57 +msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:86 +msgid "Adjust Coturn's configuration" +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:88 +msgid "The last step is to alter the generated Coturn configuration." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:90 +msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:92 +msgid "We also need to indicate to Coturn where the wildcard certificate is." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:94 +msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:96 +msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically." +msgstr "" + +#: ../../../docs/howto-srv-server-delegation.md:122 +msgid "Full example of a working configuration" +msgstr "" diff --git a/i18n/translation-templates/docs/importing-postgres.pot b/i18n/translation-templates/docs/importing-postgres.pot new file mode 100644 index 000000000..3bb07e120 --- /dev/null +++ b/i18n/translation-templates/docs/importing-postgres.pot @@ -0,0 +1,145 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/importing-postgres.md:1 +msgid "Importing an existing Postgres database from another installation (optional)" +msgstr "" + +#: ../../../docs/importing-postgres.md:3 +msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))." +msgstr "" + +#: ../../../docs/importing-postgres.md:6 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-postgres.md:8 +msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding." +msgstr "" + +#: ../../../docs/importing-postgres.md:10 +msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported." +msgstr "" + +#: ../../../docs/importing-postgres.md:12 +msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)" +msgstr "" + +#: ../../../docs/importing-postgres.md:14 +msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-postgres.md:16 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-postgres.md:18 +msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-postgres.md:26 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/importing-postgres.md:28 +msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)" +msgstr "" + +#: ../../../docs/importing-postgres.md:29 +msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly" +msgstr "" + +#: ../../../docs/importing-postgres.md:30 +msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)." +msgstr "" + +#: ../../../docs/importing-postgres.md:32 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/importing-postgres.md:34 +msgid "Table Ownership" +msgstr "" + +#: ../../../docs/importing-postgres.md:36 +msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:" +msgstr "" + +#: ../../../docs/importing-postgres.md:38 +msgid "migrated from SQLite to Postgres, and" +msgstr "" + +#: ../../../docs/importing-postgres.md:39 +msgid "used a username other than 'synapse'" +msgstr "" + +#: ../../../docs/importing-postgres.md:41 +msgid "In this case you may run into the following error during the import task:" +msgstr "" + +#: ../../../docs/importing-postgres.md:47 +msgid "where `synapse_user` is the database username from the previous Synapse installation." +msgstr "" + +#: ../../../docs/importing-postgres.md:49 +msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:" +msgstr "" + +#: ../../../docs/importing-postgres.md:61 +msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:" +msgstr "" + +#: ../../../docs/importing-postgres.md:67 +msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine." +msgstr "" + +#: ../../../docs/importing-postgres.md:69 +msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:" +msgstr "" + +#: ../../../docs/importing-postgres.md:75 +msgid "Repeat import" +msgstr "" + +#: ../../../docs/importing-postgres.md:77 +msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:" +msgstr "" + +#: ../../../docs/importing-postgres.md:85 +msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc." +msgstr "" + +#: ../../../docs/importing-postgres.md:87 +msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database." +msgstr "" + +#: ../../../docs/importing-postgres.md:93 +msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed." +msgstr "" + +#: ../../../docs/importing-postgres.md:95 +msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)" +msgstr "" + +#: ../../../docs/importing-postgres.md:101 +msgid "Hints" +msgstr "" + +#: ../../../docs/importing-postgres.md:103 +msgid "To open psql terminal run `/matrix/postgres/bin/cli`" +msgstr "" diff --git a/i18n/translation-templates/docs/importing-synapse-media-store.pot b/i18n/translation-templates/docs/importing-synapse-media-store.pot new file mode 100644 index 000000000..6bf3b4e9c --- /dev/null +++ b/i18n/translation-templates/docs/importing-synapse-media-store.pot @@ -0,0 +1,57 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/importing-synapse-media-store.md:1 +msgid "Importing `media_store` data files from an existing Synapse installation (optional)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:3 +msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:5 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:7 +msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:9 +msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:11 +msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:13 +msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac." +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:15 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-media-store.md:17 +msgid "Run this command (make sure to replace `` with a path on your server):" +msgstr "" + +#: ../../../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/translation-templates/docs/importing-synapse-sqlite.pot b/i18n/translation-templates/docs/importing-synapse-sqlite.pot new file mode 100644 index 000000000..03ffd5cad --- /dev/null +++ b/i18n/translation-templates/docs/importing-synapse-sqlite.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/importing-synapse-sqlite.md:1 +msgid "Importing an existing SQLite database from another Synapse installation (optional)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:3 +msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:5 +msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:7 +msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:9 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:11 +msgid "Before doing the actual import:" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:13 +msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first." +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:14 +msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:15 +msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:17 +msgid "Importing" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:19 +msgid "Run this command (make sure to replace `` with a file path on your server):" +msgstr "" + +#: ../../../docs/importing-synapse-sqlite.md:25 +msgid "**Notes**:" +msgstr "" + +#: ../../../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:28 +msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise." +msgstr "" diff --git a/i18n/translation-templates/docs/installing.pot b/i18n/translation-templates/docs/installing.pot new file mode 100644 index 000000000..281020067 --- /dev/null +++ b/i18n/translation-templates/docs/installing.pot @@ -0,0 +1,301 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/installing.md:1 +msgid "Installing" +msgstr "" + +#: ../../../docs/installing.md:3 +msgid "[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:5 +msgid "If you've configured your DNS records and the playbook, you can start the installation procedure." +msgstr "" + +#: ../../../docs/installing.md:7 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/installing.md:9 +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/installing.md:11 +msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:" +msgstr "" + +#: ../../../docs/installing.md:13 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/installing.md:14 +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/installing.md:16 +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/installing.md:18 +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/installing.md:20 +msgid "Install Matrix server and services" +msgstr "" + +#: ../../../docs/installing.md:22 +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/installing.md:24 +msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding." +msgstr "" + +#: ../../../docs/installing.md:26 +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:28 +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands." +msgstr "" + +#: ../../../docs/installing.md:30 +msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)." +msgstr "" + +#: ../../../docs/installing.md:32 +msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it." +msgstr "" + +#: ../../../docs/installing.md:34 +msgid "Installing a brand new server (without importing data)" +msgstr "" + +#: ../../../docs/installing.md:36 +msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:" +msgstr "" + +#: ../../../docs/installing.md:42 +msgid "This will do a full installation and start all Matrix services." +msgstr "" + +#: ../../../docs/installing.md:44 +msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)." +msgstr "" + +#: ../../../docs/installing.md:46 +msgid "Installing a server into which you'll import old data" +msgstr "" + +#: ../../../docs/installing.md:48 +msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on." +msgstr "" + +#: ../../../docs/installing.md:50 +msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:" +msgstr "" + +#: ../../../docs/installing.md:56 +msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)" +msgstr "" + +#: ../../../docs/installing.md:58 +msgid "When this command completes, services won't be running yet." +msgstr "" + +#: ../../../docs/installing.md:60 +msgid "You can now:" +msgstr "" + +#: ../../../docs/installing.md:62 +msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:64 +msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:66 +msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)" +msgstr "" + +#: ../../../docs/installing.md:68 +msgid ".. and then proceed to starting all services:" +msgstr "" + +#: ../../../docs/installing.md:74 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/installing.md:76 +msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*" +msgstr "" + +#: ../../../docs/installing.md:78 +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/installing.md:80 +msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/installing.md:82 +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/installing.md:84 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/installing.md:85 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/installing.md:86 +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/installing.md:87 +msgid "Use `admin=yes` to make your user account an administrator of the Matrix server" +msgstr "" + +#: ../../../docs/installing.md:95 +msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`." +msgstr "" + +#: ../../../docs/installing.md:97 +msgid "For more information, see the documentation for [registering users](registering-users.md)." +msgstr "" + +#: ../../../docs/installing.md:99 +msgid "Finalize the installation" +msgstr "" + +#: ../../../docs/installing.md:101 +msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:103 +msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/installing.md:105 +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." +msgstr "" + +#: ../../../docs/installing.md:107 +msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`." +msgstr "" + +#: ../../../docs/installing.md:108 +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/installing.md:110 +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/installing.md:116 +msgid "After configuring the playbook, run the command below:" +msgstr "" + +#: ../../../docs/installing.md:122 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/installing.md:124 +msgid "After finilizing the installation, you can:" +msgstr "" + +#: ../../../docs/installing.md:126 +msgid "[check if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/installing.md:127 +msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)" +msgstr "" + +#: ../../../docs/installing.md:128 +msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:129 +msgid "or learn how to [maintain your server](faq.md#maintenance)" +msgstr "" + +#: ../../../docs/installing.md:130 +msgid "or join some Matrix rooms:" +msgstr "" + +#: ../../../docs/installing.md:131 +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." +msgstr "" + +#: ../../../docs/installing.md:132 +msgid "or come say Hi in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." +msgstr "" + +#: ../../../docs/installing.md:133 +msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" +msgstr "" + +#: ../../../docs/installing.md:135 +msgid "Maintaining your setup in the future" +msgstr "" + +#: ../../../docs/installing.md:137 +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/installing.md:139 +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." +msgstr "" + +#: ../../../docs/installing.md:141 +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/installing.md:143 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +msgstr "" + +#: ../../../docs/installing.md:145 +msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." +msgstr "" + +#: ../../../docs/installing.md:151 +msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." +msgstr "" + +#: ../../../docs/installing.md:153 +msgid "Make full use of `just` shortcut commands" +msgstr "" + +#: ../../../docs/installing.md:155 +msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." +msgstr "" + +#: ../../../docs/installing.md:157 +msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/installing.md:159 +msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/just.pot b/i18n/translation-templates/docs/just.pot new file mode 100644 index 000000000..20170310a --- /dev/null +++ b/i18n/translation-templates/docs/just.pot @@ -0,0 +1,158 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/just.md:1 +msgid "Running `just` commands" +msgstr "" + +#: ../../../docs/just.md:3 +msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands." +msgstr "" + +#: ../../../docs/just.md:5 +msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing." +msgstr "" + +#: ../../../docs/just.md:7 +msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets." +msgstr "" + +#: ../../../docs/just.md:9 +msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process." +msgstr "" + +#: ../../../docs/just.md:11 +msgid "Here are some examples of shortcuts:" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Shortcut" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Result" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just roles`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just update`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run `git pull` (to update the playbook) and install the Ansible roles" +msgstr "" + +#: ../../../docs/just.md:0 +#: ../../../docs/just.md:33 +msgid "`just install-all`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just setup-all`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just install-all --ask-vault-pass`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just run-tags install-mautrix-slack,start`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just install-service mautrix-slack`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Run `just run-tags install-mautrix-slack,start` with even less typing" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just start-all`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "(Re-)starts all services" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just stop-group postgres`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Stop only the Postgres service" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "`just register-user alice secret-password yes`" +msgstr "" + +#: ../../../docs/just.md:0 +msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" +msgstr "" + +#: ../../../docs/just.md:26 +msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`." +msgstr "" + +#: ../../../docs/just.md:28 +msgid "Difference between playbook tags and shortcuts" +msgstr "" + +#: ../../../docs/just.md:30 +msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them." +msgstr "" + +#: ../../../docs/just.md:32 +msgid "For example, these two commands are different:" +msgstr "" + +#: ../../../docs/just.md:34 +msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" +msgstr "" + +#: ../../../docs/just.md:36 +msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`." +msgstr "" + +#: ../../../docs/just.md:38 +msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data." +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot b/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot new file mode 100644 index 000000000..c4bcccb55 --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot @@ -0,0 +1,89 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-and-troubleshooting.md:1 +msgid "Maintenance and Troubleshooting" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:3 +msgid "How to see the current status of your services" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:5 +msgid "You can check the status of your services by using `systemctl status`. Example:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:15 +msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:17 +msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you **cannot** view logs using `docker logs`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:19 +msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:25 +msgid "Increasing Synapse logging" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:27 +msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:29 +msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increasing the logging level to `INFO`." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:31 +msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:39 +msgid "Re-run the playbook after making these configuration changes." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:41 +msgid "Remove unused Docker data" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:43 +msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:49 +msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:51 +msgid "Postgres" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:53 +msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page." +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:55 +msgid "Ma1sd" +msgstr "" + +#: ../../../docs/maintenance-and-troubleshooting.md:57 +msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page." +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-checking-services.pot b/i18n/translation-templates/docs/maintenance-checking-services.pot new file mode 100644 index 000000000..b42b1f143 --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-checking-services.pot @@ -0,0 +1,41 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-checking-services.md:1 +msgid "Checking if services work" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:3 +msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:5 +msgid "To perform the check, run:" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:11 +msgid "The shortcut command with `just` program is also available: `just run-tags self-check`" +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:13 +msgid "If it's all green, everything is probably running correctly." +msgstr "" + +#: ../../../docs/maintenance-checking-services.md:15 +msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-migrating.pot b/i18n/translation-templates/docs/maintenance-migrating.pot new file mode 100644 index 000000000..ad652d0ab --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-migrating.pot @@ -0,0 +1,133 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-migrating.md:1 +msgid "Migrating to new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:3 +msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:6 +msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:8 +msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:9 +msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:11 +msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:13 +msgid "Lower DNS TTL" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:15 +msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:17 +msgid "Stop services on the old server completely" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:19 +msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:21 +msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:23 +msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:29 +msgid "Copy data directory to the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:31 +msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:33 +msgid "Adjust DNS records" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:35 +msgid "Make sure your DNS records are adjusted to point to the new server's IP address." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:37 +msgid "Update `inventory/hosts` file" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:39 +msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server." +msgstr "" + +#: ../../../docs/maintenance-migrating.md:41 +msgid "Create `matrix` user and group on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:43 +msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:49 +msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:51 +msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:57 +msgid "Install and start all services on the new server" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:59 +msgid "Finally, run the command below on your local computer to finish the installation and start all services:" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:65 +msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:67 +msgid "Check if services work" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:69 +msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)" +msgstr "" + +#: ../../../docs/maintenance-migrating.md:71 +msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server." +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-postgres.pot b/i18n/translation-templates/docs/maintenance-postgres.pot new file mode 100644 index 000000000..80cd68776 --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-postgres.pot @@ -0,0 +1,217 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-postgres.md:1 +msgid "PostgreSQL maintenance" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:3 +msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:7 +msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:9 +msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:11 +msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:13 +msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:15 +msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:17 +msgid "Getting a database terminal" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:19 +msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:21 +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:23 +msgid "By default, this tool puts you in the `matrix` database, which contains nothing." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:25 +msgid "To see the available databases, run `\\list` (or just `\\l`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:27 +msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:29 +msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:31 +msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:33 +msgid "Vacuuming PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:35 +msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:37 +msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:39 +msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:40 +msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:41 +msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:42 +msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:43 +msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:45 +msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:47 +msgid "Example playbook invocations:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:49 +msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:50 +msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:52 +msgid "Backing up PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:54 +msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:56 +msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:67 +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:69 +msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:71 +msgid "Upgrading PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:73 +msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:75 +msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:77 +msgid "Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:79 +msgid "This playbook can upgrade your existing Postgres setup with the following command:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:85 +msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:87 +msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:89 +msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:91 +msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:93 +msgid "**All databases, roles, etc. on the Postgres server are migrated**." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:95 +msgid "Tuning PostgreSQL" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:97 +msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:99 +msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable." +msgstr "" + +#: ../../../docs/maintenance-postgres.md:101 +msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:103 +msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:105 +msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`" +msgstr "" + +#: ../../../docs/maintenance-postgres.md:107 +msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration" +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-synapse.pot b/i18n/translation-templates/docs/maintenance-synapse.pot new file mode 100644 index 000000000..b33365b79 --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-synapse.pot @@ -0,0 +1,193 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-synapse.md:1 +msgid "Synapse maintenance" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:3 +msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:7 +msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:9 +msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:11 +msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:13 +msgid "[Make Synapse faster](#make-synapse-faster)" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:15 +msgid "Purging old data with the Purge History API" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:17 +msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:19 +msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:21 +msgid "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:23 +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:25 +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:27 +msgid "Compressing state with rust-synapse-compress-state" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:29 +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:31 +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:33 +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:35 +msgid "To ask the playbook to run rust-synapse-compress-state, execute:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:41 +msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:43 +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:45 +msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:47 +msgid "Browse and manipulate the database" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:49 +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:51 +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:53 +msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:60 +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:66 +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:68 +msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:70 +msgid "Make Synapse faster" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:72 +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:74 +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:76 +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:78 +msgid "Tuning caches and cache autotuning" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:80 +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:82 +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:84 +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:86 +msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:88 +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:89 +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:90 +msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:92 +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:94 +msgid "To **disable cache auto-tuning**, unset all values:" +msgstr "" + +#: ../../../docs/maintenance-synapse.md:102 +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:104 +msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." +msgstr "" diff --git a/i18n/translation-templates/docs/maintenance-upgrading-services.pot b/i18n/translation-templates/docs/maintenance-upgrading-services.pot new file mode 100644 index 000000000..072d69f28 --- /dev/null +++ b/i18n/translation-templates/docs/maintenance-upgrading-services.pot @@ -0,0 +1,125 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/maintenance-upgrading-services.md:1 +msgid "Upgrading the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:3 +msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:5 +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:7 +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:9 +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:11 +msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:13 +msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:15 +msgid "Steps to upgrade the Matrix services" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:17 +msgid "Check the changelog" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:19 +msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:21 +msgid "Update the playbook and the Ansible roles" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:23 +msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:25 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:26 +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:28 +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:30 +msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:32 +msgid "Re-run the playbook setup" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:34 +msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:40 +msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:46 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:48 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:50 +msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:52 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:54 +msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:56 +msgid "PostgreSQL major version upgrade" +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:58 +msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually." +msgstr "" + +#: ../../../docs/maintenance-upgrading-services.md:60 +msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)." +msgstr "" diff --git a/i18n/translation-templates/docs/obtaining-access-tokens.pot b/i18n/translation-templates/docs/obtaining-access-tokens.pot new file mode 100644 index 000000000..60f498f36 --- /dev/null +++ b/i18n/translation-templates/docs/obtaining-access-tokens.pot @@ -0,0 +1,93 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/obtaining-access-tokens.md:1 +msgid "Obtaining an Access Token" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:3 +msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:5 +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:7 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:9 +msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:11 +msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:13 +msgid "Obtain an access token via Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:15 +msgid "In a private browsing session (incognito window), open Element Web." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:16 +msgid "Log in with the user's credentials." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:17 +msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:18 +msgid "Copy the access token to your configuration." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:19 +msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:21 +msgid "Obtaining an access token with Element Web" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:23 +msgid "Obtain an access token via curl" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:25 +msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):" +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:35 +msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:37 +msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated." +msgstr "" + +#: ../../../docs/obtaining-access-tokens.md:39 +msgid "Your response will look like this (prettified):" +msgstr "" diff --git a/i18n/translation-templates/docs/playbook-tags.pot b/i18n/translation-templates/docs/playbook-tags.pot new file mode 100644 index 000000000..4f6d03c03 --- /dev/null +++ b/i18n/translation-templates/docs/playbook-tags.pot @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/playbook-tags.md:1 +msgid "Playbook tags" +msgstr "" + +#: ../../../docs/playbook-tags.md:3 +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." +msgstr "" + +#: ../../../docs/playbook-tags.md:5 +msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" +msgstr "" + +#: ../../../docs/playbook-tags.md:7 +msgid "Here are some playbook tags that you should be familiar with:" +msgstr "" + +#: ../../../docs/playbook-tags.md:9 +msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services" +msgstr "" + +#: ../../../docs/playbook-tags.md:11 +msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed" +msgstr "" + +#: ../../../docs/playbook-tags.md:13 +msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)." +msgstr "" + +#: ../../../docs/playbook-tags.md:15 +msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information." +msgstr "" + +#: ../../../docs/playbook-tags.md:17 +msgid "`start` - starts all systemd services and makes them start automatically in the future" +msgstr "" + +#: ../../../docs/playbook-tags.md:19 +msgid "`stop` - stops all systemd services" +msgstr "" + +#: ../../../docs/playbook-tags.md:21 +msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created" +msgstr "" + +#: ../../../docs/playbook-tags.md:23 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/playbook-tags.md:24 +msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc." +msgstr "" + +#: ../../../docs/playbook-tags.md:25 +msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/prerequisites.pot b/i18n/translation-templates/docs/prerequisites.pot new file mode 100644 index 000000000..61adad37c --- /dev/null +++ b/i18n/translation-templates/docs/prerequisites.pot @@ -0,0 +1,161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/prerequisites.md:1 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/prerequisites.md:3 +msgid "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:5 +msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step." +msgstr "" + +#: ../../../docs/prerequisites.md:7 +msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands." +msgstr "" + +#: ../../../docs/prerequisites.md:9 +msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide." +msgstr "" + +#: ../../../docs/prerequisites.md:11 +msgid "Your local computer" +msgstr "" + +#: ../../../docs/prerequisites.md:13 +msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible." +msgstr "" + +#: ../../../docs/prerequisites.md:15 +msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc." +msgstr "" + +#: ../../../docs/prerequisites.md:17 +msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components." +msgstr "" + +#: ../../../docs/prerequisites.md:19 +msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:21 +msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended." +msgstr "" + +#: ../../../docs/prerequisites.md:23 +msgid "Server" +msgstr "" + +#: ../../../docs/prerequisites.md:25 +msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):" +msgstr "" + +#: ../../../docs/prerequisites.md:26 +msgid "**Archlinux**" +msgstr "" + +#: ../../../docs/prerequisites.md:27 +msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)" +msgstr "" + +#: ../../../docs/prerequisites.md:28 +msgid "**Debian** (10/Buster or newer)" +msgstr "" + +#: ../../../docs/prerequisites.md:29 +msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)" +msgstr "" + +#: ../../../docs/prerequisites.md:31 +msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there." +msgstr "" + +#: ../../../docs/prerequisites.md:33 +msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:35 +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." +msgstr "" + +#: ../../../docs/prerequisites.md:37 +msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)." +msgstr "" + +#: ../../../docs/prerequisites.md:39 +msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)" +msgstr "" + +#: ../../../docs/prerequisites.md:41 +msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." +msgstr "" + +#: ../../../docs/prerequisites.md:43 +msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)." +msgstr "" + +#: ../../../docs/prerequisites.md:45 +msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))." +msgstr "" + +#: ../../../docs/prerequisites.md:47 +msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:" +msgstr "" + +#: ../../../docs/prerequisites.md:49 +msgid "`80/tcp`: HTTP webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:50 +msgid "`443/tcp` and `443/udp`: HTTPS webserver" +msgstr "" + +#: ../../../docs/prerequisites.md:51 +msgid "`3478/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:52 +msgid "`3478/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:53 +msgid "`5349/tcp`: TURN over TCP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:54 +msgid "`5349/udp`: TURN over UDP (used by Coturn)" +msgstr "" + +#: ../../../docs/prerequisites.md:55 +msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port." +msgstr "" + +#: ../../../docs/prerequisites.md:56 +msgid "the range `49152-49172/udp`: TURN over UDP" +msgstr "" + +#: ../../../docs/prerequisites.md:57 +msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." +msgstr "" + +#: ../../../docs/prerequisites.md:61 +msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)." +msgstr "" diff --git a/i18n/translation-templates/docs/quick-start.pot b/i18n/translation-templates/docs/quick-start.pot new file mode 100644 index 000000000..17c232b8a --- /dev/null +++ b/i18n/translation-templates/docs/quick-start.pot @@ -0,0 +1,429 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/quick-start.md:1 +msgid "Quick start" +msgstr "" + +#: ../../../docs/quick-start.md:9 +msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." +msgstr "" + +#: ../../../docs/quick-start.md:11 +msgid "We will be using `example.com` as the \"base domain\" in the following instruction." +msgstr "" + +#: ../../../docs/quick-start.md:13 +msgid "By following the instruction on this page, you will set up:" +msgstr "" + +#: ../../../docs/quick-start.md:15 +msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:16 +msgid "**your user account** like `@alice:example.com` on the server" +msgstr "" + +#: ../../../docs/quick-start.md:17 +msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:18 +msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" +msgstr "" + +#: ../../../docs/quick-start.md:20 +msgid "Please remember to replace `example.com` with your own domain before running any commands." +msgstr "" + +#: ../../../docs/quick-start.md:22 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/quick-start.md:24 +msgid "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:26 +msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)." +msgstr "" + +#: ../../../docs/quick-start.md:28 +msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory." +msgstr "" + +#: ../../../docs/quick-start.md:34 +msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly." +msgstr "" + +#: ../../../docs/quick-start.md:36 +msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended." +msgstr "" + +#: ../../../docs/quick-start.md:38 +msgid "Configure your DNS settings" +msgstr "" + +#: ../../../docs/quick-start.md:40 +msgid "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:42 +msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." +msgstr "" + +#: ../../../docs/quick-start.md:44 +msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below." +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Type" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Host" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Priority" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Weight" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Port" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "Target" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "A" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "`matrix`" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "-" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "`matrix-server-IP`" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "CNAME" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "`element`" +msgstr "" + +#: ../../../docs/quick-start.md:0 +msgid "`matrix.example.com`" +msgstr "" + +#: ../../../docs/quick-start.md:51 +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgstr "" + +#: ../../../docs/quick-start.md:53 +msgid "It might take some time for the DNS records to propagate after creation." +msgstr "" + +#: ../../../docs/quick-start.md:55 +msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" +msgstr "" + +#: ../../../docs/quick-start.md:57 +msgid "Get the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:59 +msgid "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:61 +msgid "Next, let's **get the playbook's source code**." +msgstr "" + +#: ../../../docs/quick-start.md:63 +msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended." +msgstr "" + +#: ../../../docs/quick-start.md:65 +msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:" +msgstr "" + +#: ../../../docs/quick-start.md:71 +msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in." +msgstr "" + +#: ../../../docs/quick-start.md:73 +msgid "Configure the playbook" +msgstr "" + +#: ../../../docs/quick-start.md:75 +msgid "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:77 +msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." +msgstr "" + +#: ../../../docs/quick-start.md:79 +msgid "To install Matrix services with this playbook, you would at least need 2 configuration files." +msgstr "" + +#: ../../../docs/quick-start.md:81 +msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." +msgstr "" + +#: ../../../docs/quick-start.md:83 +msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:" +msgstr "" + +#: ../../../docs/quick-start.md:85 +msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\"" +msgstr "" + +#: ../../../docs/quick-start.md:86 +msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`" +msgstr "" + +#: ../../../docs/quick-start.md:87 +msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`" +msgstr "" + +#: ../../../docs/quick-start.md:88 +msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)" +msgstr "" + +#: ../../../docs/quick-start.md:89 +msgid "Edit the inventory hosts file (`inventory/hosts`)" +msgstr "" + +#: ../../../docs/quick-start.md:91 +msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured." +msgstr "" + +#: ../../../docs/quick-start.md:93 +msgid "**💡 Notes:**" +msgstr "" + +#: ../../../docs/quick-start.md:94 +msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." +msgstr "" + +#: ../../../docs/quick-start.md:95 +msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over." +msgstr "" + +#: ../../../docs/quick-start.md:96 +msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish." +msgstr "" + +#: ../../../docs/quick-start.md:98 +msgid "Install" +msgstr "" + +#: ../../../docs/quick-start.md:100 +msgid "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:102 +msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." +msgstr "" + +#: ../../../docs/quick-start.md:104 +msgid "Update Ansible roles" +msgstr "" + +#: ../../../docs/quick-start.md:106 +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." +msgstr "" + +#: ../../../docs/quick-start.md:108 +msgid "To update your playbook directory and all upstream Ansible roles, run:" +msgstr "" + +#: ../../../docs/quick-start.md:110 +msgid "either: `just update`" +msgstr "" + +#: ../../../docs/quick-start.md:111 +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" +msgstr "" + +#: ../../../docs/quick-start.md:113 +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" +msgstr "" + +#: ../../../docs/quick-start.md:115 +msgid "Run installation command" +msgstr "" + +#: ../../../docs/quick-start.md:117 +msgid "Then, run the command below to start installation:" +msgstr "" + +#: ../../../docs/quick-start.md:123 +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command." +msgstr "" + +#: ../../../docs/quick-start.md:125 +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command." +msgstr "" + +#: ../../../docs/quick-start.md:127 +msgid "Wait until the command completes. If it's all green, everything should be running properly." +msgstr "" + +#: ../../../docs/quick-start.md:129 +msgid "Create your user account" +msgstr "" + +#: ../../../docs/quick-start.md:131 +msgid "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:133 +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." +msgstr "" + +#: ../../../docs/quick-start.md:135 +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." +msgstr "" + +#: ../../../docs/quick-start.md:137 +msgid "**💡 Notes**:" +msgstr "" + +#: ../../../docs/quick-start.md:138 +msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/quick-start.md:139 +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/quick-start.md:151 +msgid "Finalize server installation" +msgstr "" + +#: ../../../docs/quick-start.md:153 +msgid "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:155 +msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." +msgstr "" + +#: ../../../docs/quick-start.md:157 +msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network." +msgstr "" + +#: ../../../docs/quick-start.md:159 +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." +msgstr "" + +#: ../../../docs/quick-start.md:161 +msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server." +msgstr "" + +#: ../../../docs/quick-start.md:162 +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)." +msgstr "" + +#: ../../../docs/quick-start.md:164 +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/quick-start.md:170 +msgid "After configuring the playbook, run the command below and wait until it finishes:" +msgstr "" + +#: ../../../docs/quick-start.md:176 +msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)." +msgstr "" + +#: ../../../docs/quick-start.md:178 +msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." +msgstr "" + +#: ../../../docs/quick-start.md:180 +msgid "Re-run the full setup command any time" +msgstr "" + +#: ../../../docs/quick-start.md:182 +msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:" +msgstr "" + +#: ../../../docs/quick-start.md:188 +msgid "Log in to your user account" +msgstr "" + +#: ../../../docs/quick-start.md:190 +msgid "Finally, let's make sure that you can log in to the created account with the specified password." +msgstr "" + +#: ../../../docs/quick-start.md:192 +msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in." +msgstr "" + +#: ../../../docs/quick-start.md:194 +msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉" +msgstr "" + +#: ../../../docs/quick-start.md:196 +msgid "Come say Hi👋 in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." +msgstr "" + +#: ../../../docs/quick-start.md:198 +msgid "Things to do next" +msgstr "" + +#: ../../../docs/quick-start.md:200 +msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server." +msgstr "" + +#: ../../../docs/quick-start.md:202 +msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more." +msgstr "" + +#: ../../../docs/quick-start.md:204 +msgid "⚠️Keep the playbook and services up-to-date" +msgstr "" + +#: ../../../docs/quick-start.md:206 +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." +msgstr "" + +#: ../../../docs/quick-start.md:208 +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." +msgstr "" + +#: ../../../docs/quick-start.md:210 +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" +msgstr "" diff --git a/i18n/translation-templates/docs/registering-users.pot b/i18n/translation-templates/docs/registering-users.pot new file mode 100644 index 000000000..6b8150c1d --- /dev/null +++ b/i18n/translation-templates/docs/registering-users.pot @@ -0,0 +1,242 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/registering-users.md:1 +msgid "Registering users" +msgstr "" + +#: ../../../docs/registering-users.md:3 +msgid "This documentation page tells you how to create user accounts on your Matrix server." +msgstr "" + +#: ../../../docs/registering-users.md:5 +msgid "Table of contents:" +msgstr "" + +#: ../../../docs/registering-users.md:7 +msgid "[Registering users](#registering-users)" +msgstr "" + +#: ../../../docs/registering-users.md:8 +msgid "[Registering users manually](#registering-users-manually)" +msgstr "" + +#: ../../../docs/registering-users.md:9 +msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)" +msgstr "" + +#: ../../../docs/registering-users.md:10 +msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)" +msgstr "" + +#: ../../../docs/registering-users.md:11 +msgid "[Enabling public user registration](#enabling-public-user-registration)" +msgstr "" + +#: ../../../docs/registering-users.md:12 +msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)" +msgstr "" + +#: ../../../docs/registering-users.md:14 +msgid "Registering users manually" +msgstr "" + +#: ../../../docs/registering-users.md:16 +#: ../../../docs/registering-users.md:118 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/registering-users.md:17 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/registering-users.md:18 +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/registering-users.md:19 +msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server" +msgstr "" + +#: ../../../docs/registering-users.md:21 +msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/registering-users.md:23 +msgid "Registering users via the Ansible playbook" +msgstr "" + +#: ../../../docs/registering-users.md:25 +msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)." +msgstr "" + +#: ../../../docs/registering-users.md:27 +msgid "To register a user via this Ansible playbook:" +msgstr "" + +#: ../../../docs/registering-users.md:35 +msgid "**or** by invoking `ansible-playbook` manually:" +msgstr "" + +#: ../../../docs/registering-users.md:43 +msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`." +msgstr "" + +#: ../../../docs/registering-users.md:45 +msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:47 +msgid "Registering users manually for Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:49 +msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:57 +msgid "Registering users manually for Dendrite" +msgstr "" + +#: ../../../docs/registering-users.md:59 +msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:67 +msgid "Registering users manually for Matrix Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:69 +msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" +msgstr "" + +#: ../../../docs/registering-users.md:77 +msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:" +msgstr "" + +#: ../../../docs/registering-users.md:83 +msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:85 +msgid "Managing users via a Web UI" +msgstr "" + +#: ../../../docs/registering-users.md:87 +msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/registering-users.md:89 +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information." +msgstr "" + +#: ../../../docs/registering-users.md:91 +msgid "Letting certain users register on your private server" +msgstr "" + +#: ../../../docs/registering-users.md:93 +msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)." +msgstr "" + +#: ../../../docs/registering-users.md:95 +msgid "Enabling public user registration" +msgstr "" + +#: ../../../docs/registering-users.md:97 +msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/registering-users.md:99 +msgid "For Synapse:" +msgstr "" + +#: ../../../docs/registering-users.md:105 +msgid "For Dendrite:" +msgstr "" + +#: ../../../docs/registering-users.md:111 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/registering-users.md:120 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/registering-users.md:122 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/registering-users.md:124 +msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)." +msgstr "" + +#: ../../../docs/registering-users.md:126 +msgid "Adding/Removing Administrator privileges to an existing user" +msgstr "" + +#: ../../../docs/registering-users.md:128 +msgid "Adding/Removing Administrator privileges to an existing user in Synapse" +msgstr "" + +#: ../../../docs/registering-users.md:130 +msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:" +msgstr "" + +#: ../../../docs/registering-users.md:136 +msgid "where:" +msgstr "" + +#: ../../../docs/registering-users.md:138 +msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)" +msgstr "" + +#: ../../../docs/registering-users.md:139 +msgid "`USER` and `example.com` pointing to a valid user on your server" +msgstr "" + +#: ../../../docs/registering-users.md:141 +msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:" +msgstr "" + +#: ../../../docs/registering-users.md:143 +msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)" +msgstr "" + +#: ../../../docs/registering-users.md:144 +msgid "running `\\c synapse` - to change to the `synapse` database" +msgstr "" + +#: ../../../docs/registering-users.md:146 +msgid "You can then proceed to run the query above." +msgstr "" + +#: ../../../docs/registering-users.md:148 +msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!" +msgstr "" + +#: ../../../docs/registering-users.md:150 +msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service" +msgstr "" + +#: ../../../docs/registering-users.md:152 +msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)." +msgstr "" + +#: ../../../docs/registering-users.md:154 +msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint." +msgstr "" diff --git a/i18n/translation-templates/docs/self-building.pot b/i18n/translation-templates/docs/self-building.pot new file mode 100644 index 000000000..1210370b6 --- /dev/null +++ b/i18n/translation-templates/docs/self-building.pot @@ -0,0 +1,173 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/self-building.md:1 +msgid "Self-building" +msgstr "" + +#: ../../../docs/self-building.md:3 +msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**" +msgstr "" + +#: ../../../docs/self-building.md:5 +msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required." +msgstr "" + +#: ../../../docs/self-building.md:7 +msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)." +msgstr "" + +#: ../../../docs/self-building.md:9 +msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself." +msgstr "" + +#: ../../../docs/self-building.md:11 +msgid "Note that **not all components support self-building yet**." +msgstr "" + +#: ../../../docs/self-building.md:13 +msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:" +msgstr "" + +#: ../../../docs/self-building.md:14 +msgid "`matrix-synapse`" +msgstr "" + +#: ../../../docs/self-building.md:15 +msgid "`matrix-synapse-admin`" +msgstr "" + +#: ../../../docs/self-building.md:16 +msgid "`matrix-client-element`" +msgstr "" + +#: ../../../docs/self-building.md:17 +msgid "`matrix-client-hydrogen`" +msgstr "" + +#: ../../../docs/self-building.md:18 +msgid "`matrix-client-cinny`" +msgstr "" + +#: ../../../docs/self-building.md:19 +msgid "`matrix-registration`" +msgstr "" + +#: ../../../docs/self-building.md:20 +msgid "`matrix-coturn`" +msgstr "" + +#: ../../../docs/self-building.md:21 +msgid "`matrix-corporal`" +msgstr "" + +#: ../../../docs/self-building.md:22 +msgid "`matrix-dimension`" +msgstr "" + +#: ../../../docs/self-building.md:23 +msgid "`matrix-ma1sd`" +msgstr "" + +#: ../../../docs/self-building.md:24 +msgid "`exim-relay`" +msgstr "" + +#: ../../../docs/self-building.md:25 +msgid "`matrix-bridge-hookshot`" +msgstr "" + +#: ../../../docs/self-building.md:26 +msgid "`matrix-bridge-appservice-irc`" +msgstr "" + +#: ../../../docs/self-building.md:27 +msgid "`matrix-bridge-appservice-slack`" +msgstr "" + +#: ../../../docs/self-building.md:28 +msgid "`matrix-bridge-appservice-webhooks`" +msgstr "" + +#: ../../../docs/self-building.md:29 +msgid "`matrix-bridge-beeper-linkedin`" +msgstr "" + +#: ../../../docs/self-building.md:30 +msgid "`matrix-bridge-mautrix-facebook`" +msgstr "" + +#: ../../../docs/self-building.md:31 +msgid "`matrix-bridge-mautrix-hangouts`" +msgstr "" + +#: ../../../docs/self-building.md:32 +msgid "`matrix-bridge-mautrix-googlechat`" +msgstr "" + +#: ../../../docs/self-building.md:33 +msgid "`matrix-bridge-mautrix-telegram`" +msgstr "" + +#: ../../../docs/self-building.md:34 +msgid "`matrix-bridge-mautrix-signal`" +msgstr "" + +#: ../../../docs/self-building.md:35 +msgid "`matrix-bridge-mautrix-gmessages`" +msgstr "" + +#: ../../../docs/self-building.md:36 +msgid "`matrix-bridge-mautrix-whatsapp`" +msgstr "" + +#: ../../../docs/self-building.md:37 +msgid "`matrix-bridge-mx-puppet-steam`" +msgstr "" + +#: ../../../docs/self-building.md:38 +msgid "`matrix-bot-mjolnir`" +msgstr "" + +#: ../../../docs/self-building.md:39 +msgid "`matrix-bot-honoroit`" +msgstr "" + +#: ../../../docs/self-building.md:40 +msgid "`matrix-bot-matrix-reminder-bot`" +msgstr "" + +#: ../../../docs/self-building.md:41 +msgid "`matrix-bot-maubot`" +msgstr "" + +#: ../../../docs/self-building.md:42 +msgid "`matrix-email2matrix`" +msgstr "" + +#: ../../../docs/self-building.md:43 +msgid "`matrix-pantalaimon`" +msgstr "" + +#: ../../../docs/self-building.md:45 +msgid "Adding self-building support to other roles is welcome. Feel free to contribute!" +msgstr "" + +#: ../../../docs/self-building.md:47 +msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles." +msgstr "" diff --git a/i18n/translation-templates/docs/uninstalling.pot b/i18n/translation-templates/docs/uninstalling.pot new file mode 100644 index 000000000..5c4b477ab --- /dev/null +++ b/i18n/translation-templates/docs/uninstalling.pot @@ -0,0 +1,77 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/uninstalling.md:1 +msgid "Uninstalling" +msgstr "" + +#: ../../../docs/uninstalling.md:3 +msgid "**Warnings**:" +msgstr "" + +#: ../../../docs/uninstalling.md:5 +msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating." +msgstr "" + +#: ../../../docs/uninstalling.md:7 +msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**." +msgstr "" + +#: ../../../docs/uninstalling.md:11 +msgid "Uninstalling using a script" +msgstr "" + +#: ../../../docs/uninstalling.md:13 +msgid "Installing places a `/matrix/bin/remove-all` script on the server." +msgstr "" + +#: ../../../docs/uninstalling.md:15 +msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**" +msgstr "" + +#: ../../../docs/uninstalling.md:17 +msgid "Uninstalling manually" +msgstr "" + +#: ../../../docs/uninstalling.md:19 +msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):" +msgstr "" + +#: ../../../docs/uninstalling.md:21 +msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)" +msgstr "" + +#: ../../../docs/uninstalling.md:23 +msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)" +msgstr "" + +#: ../../../docs/uninstalling.md:25 +msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)" +msgstr "" + +#: ../../../docs/uninstalling.md:27 +msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)" +msgstr "" + +#: ../../../docs/uninstalling.md:29 +msgid "uninstall Docker itself, if necessary" +msgstr "" + +#: ../../../docs/uninstalling.md:31 +msgid "delete the `/matrix` directory (`rm -rf /matrix`)" +msgstr "" diff --git a/i18n/translation-templates/docs/updating-users-passwords.pot b/i18n/translation-templates/docs/updating-users-passwords.pot new file mode 100644 index 000000000..efce7ebd2 --- /dev/null +++ b/i18n/translation-templates/docs/updating-users-passwords.pot @@ -0,0 +1,85 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/updating-users-passwords.md:1 +msgid "Updating users passwords" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:3 +msgid "Option 1 (if you are using the integrated Postgres database):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:5 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:6 +msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:7 +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:9 +msgid "You can reset a user's password via the Ansible playbook:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:15 +msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:17 +msgid "Option 2 (if you are using an external Postgres server):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:19 +msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:25 +msgid "and then connecting to the postgres server and executing:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:31 +msgid "where `` is the hash returned by the docker command above." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:33 +msgid "Option 3:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:35 +msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:37 +msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:39 +msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)." +msgstr "" + +#: ../../../docs/updating-users-passwords.md:41 +msgid "Example:" +msgstr "" + +#: ../../../docs/updating-users-passwords.md:43 +msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:" +msgstr "" diff --git a/i18n/translation-templates/i18n/README.pot b/i18n/translation-templates/i18n/README.pot new file mode 100644 index 000000000..929792829 --- /dev/null +++ b/i18n/translation-templates/i18n/README.pot @@ -0,0 +1,216 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-12-20 09:29+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" + +#: ../../README.md:1 +msgid "Internationalization" +msgstr "" + +#: ../../README.md:3 +msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." +msgstr "" + +#: ../../README.md:5 +msgid "Currently, we support translation of:" +msgstr "" + +#: ../../README.md:7 +msgid "Markdown files found at the top level project directory" +msgstr "" + +#: ../../README.md:8 +msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" +msgstr "" + +#: ../../README.md:9 +msgid "this current document in the `i18n` directory" +msgstr "" + +#: ../../README.md:11 +msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." +msgstr "" + +#: ../../README.md:13 +msgid "Organization of this `i18n` directory is as follows:" +msgstr "" + +#: ../../README.md:15 +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" +msgstr "" + +#: ../../README.md:16 +msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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:17 +msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" +msgstr "" + +#: ../../README.md:18 +msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" +msgstr "" + +#: ../../README.md:19 +msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" +msgstr "" + +#: ../../README.md:20 +msgid "[locales/](locales/): localization files for languages" +msgstr "" + +#: ../../README.md:21 +msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +msgstr "" + +#: ../../README.md:23 +msgid "Guide for translators" +msgstr "" + +#: ../../README.md:25 +msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." +msgstr "" + +#: ../../README.md:27 +msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." +msgstr "" + +#: ../../README.md:29 +msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." +msgstr "" + +#: ../../README.md:31 +msgid "(Recommended) Using the uv package manager and just command runner" +msgstr "" + +#: ../../README.md:33 +msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." +msgstr "" + +#: ../../README.md:35 +msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." +msgstr "" + +#: ../../README.md:37 +#: ../../README.md:64 +msgid "Preparation" +msgstr "" + +#: ../../README.md:39 +msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." +msgstr "" + +#: ../../README.md:41 +#: ../../README.md:72 +msgid "Translation" +msgstr "" + +#: ../../README.md:43 +#: ../../README.md:74 +msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" +msgstr "" + +#: ../../README.md:45 +msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" +msgstr "" + +#: ../../README.md:47 +#: ../../README.md:80 +msgid "Use an editor to translate the files in the `locales/` directory" +msgstr "" + +#: ../../README.md:49 +msgid "Build translated documents: `just build-for-language `" +msgstr "" + +#: ../../README.md:51 +#: ../../README.md:84 +msgid "Preview the result in the `translated/` directory" +msgstr "" + +#: ../../README.md:53 +#: ../../README.md:86 +msgid "Commit your changes done to the `locales/` directory" +msgstr "" + +#: ../../README.md:55 +#: ../../README.md:88 +msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" +msgstr "" + +#: ../../README.md:57 +msgid "Using any other package manager and manual scripts" +msgstr "" + +#: ../../README.md:59 +msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" +msgstr "" + +#: ../../README.md:61 +msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" +msgstr "" + +#: ../../README.md:62 +msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" +msgstr "" + +#: ../../README.md:66 +msgid "virtualenv and pip" +msgstr "" + +#: ../../README.md:68 +msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" +msgstr "" + +#: ../../README.md:69 +msgid "Activate the virtual environment: `source .venv/bin/activate`" +msgstr "" + +#: ../../README.md:70 +msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" +msgstr "" + +#: ../../README.md:76 +msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" +msgstr "" + +#: ../../README.md:78 +msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" +msgstr "" + +#: ../../README.md:82 +msgid "Build translated documents: `./bin/build-translated-result.sh `" +msgstr "" + +#: ../../README.md:90 +msgid "Publish translations in a new language" +msgstr "" + +#: ../../README.md:92 +msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" +msgstr "" + +#: ../../README.md:94 +msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" +msgstr "" + +#: ../../README.md:95 +msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" +msgstr "" + +#: ../../README.md:97 +msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." +msgstr "" From 7551680e091a67ccd5d6fee784e69bab7347801e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 09:50:26 +0200 Subject: [PATCH 120/952] Properly ignore .mo files --- i18n/.gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/.gitignore b/i18n/.gitignore index e3430f08a..78794379d 100644 --- a/i18n/.gitignore +++ b/i18n/.gitignore @@ -1,6 +1,6 @@ .venv/ doctrees .doctrees/ -.mo +/**/*.mo /translated/* From 1cf6f8695539fc6ade862c90618f44ab5c56b83b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 09:53:46 +0200 Subject: [PATCH 121/952] Update translation templates --- i18n/translation-templates/README.pot | 20 +- ...iguring-playbook-alertmanager-receiver.pot | 144 ++--- ...g-playbook-appservice-draupnir-for-all.pot | 155 +++--- .../configuring-playbook-bot-draupnir.pot | 499 +++++++++--------- .../docs/configuring-playbook-bot-go-neb.pot | 4 +- .../configuring-playbook-bot-honoroit.pot | 4 +- ...g-playbook-bot-matrix-registration-bot.pot | 4 +- ...uring-playbook-bot-matrix-reminder-bot.pot | 4 +- .../docs/configuring-playbook-bot-mjolnir.pot | 182 ++++--- ...g-playbook-bridge-appservice-kakaotalk.pot | 4 +- ...guring-playbook-bridge-go-skype-bridge.pot | 4 +- ...nfiguring-playbook-bridge-heisenbridge.pot | 4 +- .../configuring-playbook-bridge-hookshot.pot | 254 +++++---- ...ring-playbook-bridge-matrix-bridge-sms.pot | 4 +- ...guring-playbook-bridge-mautrix-twitter.pot | 64 ++- ...guring-playbook-bridge-mautrix-wsproxy.pot | 4 +- ...ring-playbook-bridge-mx-puppet-discord.pot | 4 +- ...ring-playbook-bridge-mx-puppet-groupme.pot | 4 +- ...guring-playbook-bridge-mx-puppet-slack.pot | 4 +- ...guring-playbook-bridge-mx-puppet-steam.pot | 4 +- ...ring-playbook-bridge-mx-puppet-twitter.pot | 4 +- ...configuring-playbook-bridge-postmoogle.pot | 4 +- .../configuring-playbook-bridge-wechat.pot | 4 +- .../configuring-playbook-email2matrix.pot | 16 +- .../docs/configuring-playbook-ldap-auth.pot | 4 +- .../docs/configuring-playbook-ma1sd.pot | 4 +- .../configuring-playbook-matrix-corporal.pot | 56 +- .../docs/configuring-playbook-pantalaimon.pot | 4 +- .../docs/configuring-playbook-rest-auth.pot | 4 +- ...onfiguring-playbook-shared-secret-auth.pot | 4 +- .../docs/configuring-playbook-sygnal.pot | 4 +- ...ng-playbook-synapse-auto-accept-invite.pot | 24 +- ...uring-playbook-synapse-auto-compressor.pot | 4 +- ...uring-playbook-synapse-simple-antispam.pot | 10 +- ...ing-playbook-user-verification-service.pot | 34 +- 35 files changed, 836 insertions(+), 714 deletions(-) diff --git a/i18n/translation-templates/README.pot b/i18n/translation-templates/README.pot index 03f903992..23cfe9a49 100644 --- a/i18n/translation-templates/README.pot +++ b/i18n/translation-templates/README.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\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" @@ -1152,14 +1152,26 @@ msgstr "" msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)" msgstr "" -#: ../../../README.md:215 +#: ../../../README.md:201 +msgid "🌐 Translation" +msgstr "" + +#: ../../../README.md:203 +msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation." +msgstr "" + +#: ../../../README.md:205 +msgid "Translations are still work in progress." +msgstr "" + +#: ../../../README.md:207 msgid "🤝 Related" msgstr "" -#: ../../../README.md:217 +#: ../../../README.md:209 msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))." msgstr "" -#: ../../../README.md:219 +#: ../../../README.md:211 msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot index 9bf2960c1..858379113 100644 --- a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot +++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,137 +25,137 @@ msgid "The playbook can install and configure the [matrix-alertmanager-receiver] msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 -msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver) to learn more about what this component does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 -msgid "At the moment, **setting up this service's bot requires some manual actions** as described below in [Account and room preparation](#account-and-room-preparation)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it." msgstr "" +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +msgid "Prerequisites" +msgstr "" + #: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 -msgid "Adjusting the playbook configuration" +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 -msgid "To enable matrix-alertmanager-receiver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +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:36 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 +msgid "Join to rooms as the bot manually" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 +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:33 +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:35 +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:37 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 +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](#get-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 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:42 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 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:44 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 -msgid "Account and room preparation" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 -msgid "The playbook can automatically create users, but it cannot automatically obtain access tokens, nor perform any of the other manual actions below." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 -msgid "`matrix-alertmanager-receiver` uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see above) for delivering messages. You need to **manually register this bot acccount and obtain an access token for it**." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 -msgid "[Register a new user](registering-users.md): `ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user`" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 -msgid "[Obtain an access token](obtaining-access-tokens.md) for the bot's user account" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 -msgid "Invite the bot to a room where you'd like to alerts to be delivered" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 -msgid "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:70 -msgid "(Optionally) Adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 -msgid "Steps 1 and 2 above only need to be done once, while preparing your [configuration](#adjusting-the-playbook-configuration)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 -msgid "Steps 3 and 4 need to be done for each new room you'd like the bot to deliver alerts to. Step 5 is optional and provides cleaner `/alert/` URLs." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 -msgid "Now that you've [prepared the bot account and room](#account-and-room-preparation), [configured the playbook](#adjusting-the-playbook-configuration), and potentially [adjusted your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-alertmanager-receiver.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-alertmanager-receiver.md:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 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:89 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:98 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:91 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 -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:116 -msgid "This bot does **not** accept room invitations automatically (like many other bots do). To deliver messages to rooms, **the bot must be joined to all rooms manually** - see Step 4 of the [Account and room preparation](#account-and-room-preparation) section." +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 +msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot index 2366e7ae6..5b480cc69 100644 --- a/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot +++ b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -53,133 +53,138 @@ msgid "Draupnir for all does not support external tooling like [MRU](https://mru msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 -msgid "Installation" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 -msgid "Create a main management room." +msgid "Create a main management room" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 -msgid "The playbook does not create a management room for your Main Draupnir. This task you have to do on your own." +msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 -msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 -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." +msgid "Note that the room must be unencrypted." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 -msgid "As noted in the Draupnir install instructions the control room is sensitive. The following is said about the control room in the Draupnir install instructions." +msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 -msgid "Anyone in this room can control the bot so it is important that you only invite trusted users to this room. The room must be unencrypted since the playbook does not support installing Pantalaimon yet." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 +msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 -msgid "Give your main management room an alias." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33 +msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 -msgid "Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35 +msgid "Set an alias to the management room" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 -msgid "Adjusting the playbook configuration." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37 +msgid "Next, set an alias to the management room." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39 +msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:40 -msgid "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created in step 2." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 -msgid "Installing" +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51 +msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 -msgid "**Notes**:" +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 +msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md: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-appservice-draupnir-for-all.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-appservice-draupnir-for-all.md:65 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 -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." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55 +msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 -msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot mode." +msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 -msgid "Granting Users the ability to use D4A" +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86 +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 -msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended." +msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 -msgid "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))" +msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 -msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 -msgid "How to provision a D4A once you are allowed to." +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 -msgid "Open a DM with @draupnir-main:example.com and if using an Element client send a message into this DM to finalise creating it. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 +msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98 +msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 +msgid "Granting Users the ability to use D4A" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 +msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 +msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 +msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 +msgid "How to provision a D4A once you are allowed to" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 +msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 -msgid "Configuration of D4A" -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 -msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation. Please note that the playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 -msgid "Please note that Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyways. Config extension instead touches the config passed to the Draupnirs that your Appservice creates. So for example below makes all provisioned Draupnirs protect all joined rooms." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 -msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 -msgid "For example to change Draupnir's `protectAllJoinedRooms` option to `true` you would add the following to your `vars.yml` file." -msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot index 053368d5f..0a1d292b3 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure the [Draupnir](https://github.com/ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:5 -msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:7 @@ -33,19 +33,19 @@ msgid "This documentation page is about installing Draupnir in bot mode. As an a msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:9 -msgid "If your migrating from Mjolnir skip to step 5b." +msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:11 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:13 -msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 @@ -57,7 +57,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 -msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." +msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 @@ -65,7 +65,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 -msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 @@ -73,278 +73,305 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 -msgid "The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header \"Authorization: Bearer \" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit` Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:39 -msgid "Create a management room" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:41 -msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:43 -msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:45 -msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:47 -msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:49 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:51 -msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:53 -msgid "a. Configuration with E2EE support" +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:55 -msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:57 -#: ../../../docs/configuring-playbook-bot-draupnir.md:92 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 +msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:78 +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:80 +msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:82 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:84 +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:86 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:100 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:88 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:94 -msgid "You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 +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](#get-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:104 -msgid "c. Migrating from Mjolnir (Only required if migrating.)" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:106 -msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:108 -msgid "That is all you need to do due to that Draupnir can complete migration on its own." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:110 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:119 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:121 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:123 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:125 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:127 -msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:129 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:131 -msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:133 -msgid "Below is a **non-exhaustive quick-start guide** for the impatient." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:135 -msgid "Making Draupnir join and protect a room" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:137 -msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:139 -msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:141 -msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:143 -msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:145 -msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:147 -msgid "Giving Draupnir permissions to do its job" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:149 -msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:151 -msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:153 -msgid "Subscribing to a public policy list" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:155 -msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:157 -msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:159 -msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:161 -msgid "Creating your own policy lists and rules" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:163 -msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:165 -msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 -msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 -msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 -msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 -msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:174 -msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:176 -msgid "As a result of running these commands, you may observe:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:178 -msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 -msgid "applying these rules against all rooms that Draupnir is an Administrator in" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 -msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 -msgid "Enabling built-in protections" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 -msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 -msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 -msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 -msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 -msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 -msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 -msgid "Extending the configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 -msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 -msgid "For example to change Draupnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +#: ../../../docs/configuring-playbook-bot-draupnir.md:122 msgid "Abuse Reports" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +#: ../../../docs/configuring-playbook-bot-draupnir.md:124 msgid "Draupnir supports two methods to receive reports in the management room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +#: ../../../docs/configuring-playbook-bot-draupnir.md:126 msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:225 -msgid "The other method polls an synapse admin API endpoint and is hence only available when using synapse and when the Draupnir user is an admin user (see step 1). To enable it, set `pollReports: true` in Draupnir's config:" +#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +msgid "Migrating from Mjolnir (Only required if migrating)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 +msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 +msgid "That is all you need to do due to that Draupnir can complete migration on its own." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 +msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +msgid "Below is a **non-exhaustive quick-start guide** for the impatient." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +msgid "Making Draupnir join and protect a room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +msgid "Giving Draupnir permissions to do its job" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +msgid "Subscribing to a public policy list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 +msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 +msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 +msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 +msgid "Creating your own policy lists and rules" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 +msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 +msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 +msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:222 +msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 +msgid "As a result of running these commands, you may observe:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 +msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:227 +msgid "applying these rules against all rooms that Draupnir is an Administrator in" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 +msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 +msgid "Enabling built-in protections" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 +msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 +msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 +msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 +msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 +msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 +msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot index f2de4ef5b..101a5dd72 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -33,7 +33,7 @@ msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:9 -msgid "See the project's [documentation](https://github.com/matrix-org/go-neb) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot index 303b56673..404a4f5c1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "It's a bot you can use to setup **your own helpdesk on matrix**" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:7 -msgid "See the project's [documentation](https://github.com/etkecc/honoroit#how-it-looks-like) to learn what it does with screenshots and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot index ff313929a..d2dfa6c62 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "The bot allows you to easily **create and manage registration tokens** ak msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 -msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot index 9ad8e8d03..6c96f8b74 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "It's a bot you can use to **schedule one-off & recurring reminders and al msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 -msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot index 46e7834be..d1aae2fce 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\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" @@ -25,19 +25,19 @@ msgid "The playbook can install and configure the [Mjolnir](https://github.com/m msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:5 -msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:7 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:9 -msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:11 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 @@ -57,7 +57,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 -msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 @@ -65,119 +65,153 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 -msgid "The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header \"Authorization: Bearer \" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit` Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Mjolnir itself. If you made Mjolnir Admin you can just use the Mjolnir token." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 -msgid "Create a management room" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 -msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:39 -msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:41 -msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:43 -msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 -msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:49 -msgid "a. Configuration with E2EE support" +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:51 -msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:53 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 +msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:76 +msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 -msgid "You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +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](#get-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -msgid "Installing" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 -msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 -msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 -msgid "For example to change Mjolnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file." +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 +msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 +msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot index 8605c2709..0d38f2077 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **u msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 -msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot index 15528742f..8f279cdf5 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [go-skype-bridge](https://github.c msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot index 3b2b5c57e..76127e7b9 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "The playbook can install and configure [Heisenbridge](https://github.com/ msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 -msgid "See the project's [README](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot index 028bcc45a..ba4ae20c1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\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" @@ -25,11 +25,11 @@ msgid "The playbook can install and configure [matrix-hookshot](https://github.c msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:5 -msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, JIRA, and Figma, as well as generic webhooks." +msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:7 -msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does in detail and why it might be useful to you." +msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:9 @@ -37,103 +37,123 @@ msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configu msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:11 -msgid "Setup Instructions" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:13 -msgid "Refer to the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) to learn what the individual options do." +msgid "Download GitHub app private key (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:15 -msgid "Enable the bridge by adding `matrix_hookshot_enabled: true` to your `vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 -msgid "For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." +msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:17 -msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab, Generic), while you must first add the required configuration and enable the others (GitHub, Jira, Figma)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 -msgid "If you're setting up the GitHub bridge, you'll need to generate and download a private key file after you created your GitHub app. Copy the contents of that file to the variable `matrix_hookshot_github_private_key` so the playbook can install it for you, or use one of the [other methods](#manage-github-private-key-with-aux-role) explained below." +msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:19 -msgid "If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready. Hookshot can be set up individually using the tag `setup-hookshot`." +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:21 -msgid "Other configuration options are available via the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables, see the comments in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) for how to use them." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 -msgid "Finally, run the playbook (see [installing](installing.md))." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 -msgid "End-to-bridge encryption" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 -msgid "You can enable [encryption](https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html) for Hookshot by adding `matrix_hookshot_encryption_enabled: true` to your configuration (`vars.yml`) and [executing the playbook](installing.md) again." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:29 -msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added, for example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-hookshot-encryption`." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 -msgid "Usage" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 -msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:35 -msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." +msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:37 -msgid "Send a `!hookshot help` message to see a list of help commands." +msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:39 -msgid "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." +msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:41 -msgid "**Important**: Note that the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation, see [URLs for bridges setup](#urls-for-bridges-setup) below." +msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:43 -msgid "More setup documentation" +msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:45 -msgid "URLs for bridges setup" +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 +msgid "`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:58 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:60 +msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:62 +msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:64 +msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:66 +msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:68 +msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +msgid "Reset crypto store" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 +msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:78 +msgid "More setup documentation" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:80 +msgid "URLs for bridges setup" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:82 msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 -msgid "listener" +msgid "Listener" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 -msgid "default path" +msgid "Default path" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 -msgid "variable" +msgid "Variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 -msgid "used as" +msgid "Used as" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 @@ -197,7 +217,7 @@ msgid "`matrix_hookshot_jira_oauth_endpoint`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 -msgid "JIRA OAuth" +msgid "Jira OAuth" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:0 @@ -280,82 +300,82 @@ msgstr "" msgid "Prometheus" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 -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:63 -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:65 -msgid "Manage GitHub Private Key with aux role" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 -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:68 -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:69 -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:70 -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:72 -msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following additional configuration:" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 -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:85 -msgid "Provisioning API" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 -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:89 -msgid "Metrics" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 -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:93 -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:95 -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:97 -msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" +#: ../../../docs/configuring-playbook-bridge-hookshot.md:96 +msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:98 -msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" +msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:100 -msgid "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." +msgid "Manage GitHub Private Key with aux role" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:102 -msgid "Collision with matrix-appservice-webhooks" +msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 +msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:106 +msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:108 +msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 +msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:121 +msgid "Provisioning API" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:123 +msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:125 +msgid "Metrics" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:127 +msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:129 +msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:131 +msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:133 +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 +msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 +msgid "Collision with matrix-appservice-webhooks" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:140 msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot index e70f094e0..aed94e159 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [matrix-sms-bridge](https://github msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot index 7646fb6da..ece21b5ac 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "The playbook can install and configure [mautrix-twitter](https://github.c msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 -msgid "See the project's [documentation](https://github.com/mautrix/twitter) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 @@ -37,87 +37,87 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.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." +msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 -msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-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) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 -msgid "Adjusting the playbook configuration" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44 msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 msgid "💡 Set up Double Puppeting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 msgid "To set it up, you have 2 ways of going about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 -msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" -msgstr "" - #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 -msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." +msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 -msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 -msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 @@ -125,5 +125,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 -msgid "This method is currently not available for the Mautrix-Twitter bridge, but is on the [roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) under Misc/Manual login with `login-matrix`" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69 +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot index 48492f6c1..2861d8a9a 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [mautrix-wsproxy](https://github.c msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 -msgid "See the project's [documentation](https://github.com/mautrix/wsproxy#readme) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot index 161cdfd03..43cdf46e6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -37,7 +37,7 @@ msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 -msgid "See the project page to learn what it does and why it might be useful to you." +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 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot index a5531f79a..50caaae7d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot index 0d8f02730..beb0f93e0 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.c msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot index 9e9acd5de..a40080de2 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [mx-puppet-steam](https://github.c msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot index 803010590..9d538d060 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "The playbook can install and configure [mx-puppet-twitter](https://github msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7 -msgid "See the project page to learn what it does and why it might be useful to you." +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 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot index fd360ca8b..9c61b8821 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -33,7 +33,7 @@ msgid "Postmoogle is a bridge you can use to have its bot user forward emails to msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 -msgid "See the project's [documentation](https://github.com/etkecc/postmoogle) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot index 025d428bf..4f6761621 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure the [matrix-wechat](https://github msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:5 -msgid "See the project page to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot index 66409c6dc..e0308bcc2 100644 --- a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot +++ b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -157,21 +157,21 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "To enable Email2Matrix, run the playbook with [playbook tags](playbook-tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:93 +#: ../../../docs/configuring-playbook-email2matrix.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:95 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-email2matrix,start` or `just setup-all`" +#: ../../../docs/configuring-playbook-email2matrix.md:96 +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:97 -msgid "`just run-tags setup-email2matrix,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." +#: ../../../docs/configuring-playbook-email2matrix.md:98 +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:99 +#: ../../../docs/configuring-playbook-email2matrix.md:100 msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot index 002e67cf2..45732b593 100644 --- a/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot +++ b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure the [matrix-synapse-ldap3](https:/ msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:5 -msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot index 76969ae11..0e2a2fc11 100644 --- a/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot +++ b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -33,7 +33,7 @@ msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numb msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:9 -msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd) to learn what it does and why it might be useful to you." +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 diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot index 866d2c6b1..f4ea1d1c0 100644 --- a/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,93 +29,97 @@ msgid "The playbook can install and configure [matrix-corporal](https://github.c msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:11 -msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment. See that project's documentation to learn what it does and why it might be useful to you." +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:13 -msgid "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:14 -msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" +msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:15 -msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" +msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:16 +msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:17 -msgid "Adjusting the playbook configuration" +msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:19 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:21 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:72 +#: ../../../docs/configuring-playbook-matrix-corporal.md:74 msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:74 +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 msgid "No matter what Matrix user ID you configure to run it with, make sure that:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +#: ../../../docs/configuring-playbook-matrix-corporal.md:78 msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:78 +#: ../../../docs/configuring-playbook-matrix-corporal.md:80 msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:80 +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 msgid "Using a locally-stored static policy" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +#: ../../../docs/configuring-playbook-matrix-corporal.md:84 msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:114 +#: ../../../docs/configuring-playbook-matrix-corporal.md:116 msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:116 +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +#: ../../../docs/configuring-playbook-matrix-corporal.md:120 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +#: ../../../docs/configuring-playbook-matrix-corporal.md:127 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:127 +#: ../../../docs/configuring-playbook-matrix-corporal.md:129 msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:129 +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 msgid "Matrix Corporal files" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +#: ../../../docs/configuring-playbook-matrix-corporal.md:133 msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:133 +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +#: ../../../docs/configuring-playbook-matrix-corporal.md:141 msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths - `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot index 4462e3058..cfe438475 100644 --- a/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot +++ b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure the [pantalaimon](https://github.c msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:5 -msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot index 732aaad20..18b3def98 100644 --- a/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot +++ b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [matrix-synapse-rest-auth](https:/ msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:5 -msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot index b251f695c..126f05428 100644 --- a/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot +++ b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:5 -msgid "See that project's documentation to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-sygnal.pot b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot index fd9586433..e61b6a508 100644 --- a/i18n/translation-templates/docs/configuring-playbook-sygnal.pot +++ b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,7 +25,7 @@ msgid "The playbook can install and configure the [Sygnal](https://github.com/ma msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:5 -msgid "See the project's [documentation](https://github.com/matrix-org/sygnal) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:7 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 f210c7393..7b6295506 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: 2024-12-20 07:23+0200\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" @@ -25,41 +25,45 @@ msgid "The playbook can install and configure [synapse-auto-invite-accept](https msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 -msgid "See that project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite) to learn what it does and why it might be useful to you. In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified." +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 "**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." +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 "Configuration" +msgid "**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +msgid "Configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 msgid "If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:19 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 msgid "Synapse worker deployments" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +#: ../../../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:27 +#: ../../../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:29 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +#: ../../../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:33 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:35 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot index 1fe44a3e1..389cc1136 100644 --- a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -29,7 +29,7 @@ msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` da msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 -msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot index 5a3202e23..aea18ce59 100644 --- a/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot +++ b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -25,13 +25,17 @@ msgid "The playbook can install and configure [synapse-simple-antispam](https:// msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 -msgid "See that project's documentation to learn what it does and why it might be useful to you. In short, it lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." +msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 -msgid "Adjusting the playbook configuration" +msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot index 85eaa0963..7a47a11a8 100644 --- a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot +++ b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -157,57 +157,57 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:90 -msgid "After these variables have been set, run the playbook with [playbook tags](playbook-tags.md) as below to restart UVS:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:96 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-matrix-user-verification-service,start` or `just setup-all`" +#: ../../../docs/configuring-playbook-user-verification-service.md:97 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:98 -msgid "`just run-tags setup-matrix-user-verification-service,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." +#: ../../../docs/configuring-playbook-user-verification-service.md:99 +msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:100 +#: ../../../docs/configuring-playbook-user-verification-service.md:101 msgid "Logging" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:102 +#: ../../../docs/configuring-playbook-user-verification-service.md:103 msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:103 +#: ../../../docs/configuring-playbook-user-verification-service.md:104 msgid "warning" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:104 +#: ../../../docs/configuring-playbook-user-verification-service.md:105 msgid "info" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:105 +#: ../../../docs/configuring-playbook-user-verification-service.md:106 msgid "debug" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:107 +#: ../../../docs/configuring-playbook-user-verification-service.md:108 msgid "TLS Certificate Checking" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:109 +#: ../../../docs/configuring-playbook-user-verification-service.md:110 msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:111 +#: ../../../docs/configuring-playbook-user-verification-service.md:112 msgid "message: 'No response received: [object Object]'," msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:113 +#: ../../../docs/configuring-playbook-user-verification-service.md:114 msgid "This also applies to self-signed and let's encrypt staging certificates." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:115 +#: ../../../docs/configuring-playbook-user-verification-service.md:116 msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:117 +#: ../../../docs/configuring-playbook-user-verification-service.md:118 msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it." msgstr "" From 0afa372ca81f08af1d6092b81ed3eb6a5b5bc7b0 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 09:54:28 +0200 Subject: [PATCH 122/952] Update locales --- i18n/locales/bg/LC_MESSAGES/README.po | 47 +- ...figuring-playbook-alertmanager-receiver.po | 316 ++++++++---- ...ng-playbook-appservice-draupnir-for-all.po | 303 ++++++++---- .../docs/configuring-playbook-bot-draupnir.po | 457 ++++++++++++------ .../docs/configuring-playbook-bot-go-neb.po | 14 +- .../docs/configuring-playbook-bot-honoroit.po | 16 +- ...ng-playbook-bot-matrix-registration-bot.po | 12 +- ...guring-playbook-bot-matrix-reminder-bot.po | 14 +- .../docs/configuring-playbook-bot-mjolnir.po | 314 +++++++++--- ...ng-playbook-bridge-appservice-kakaotalk.po | 14 +- ...iguring-playbook-bridge-go-skype-bridge.po | 13 +- ...onfiguring-playbook-bridge-heisenbridge.po | 18 +- .../configuring-playbook-bridge-hookshot.po | 403 +++++++++++---- ...uring-playbook-bridge-matrix-bridge-sms.po | 13 +- ...iguring-playbook-bridge-mautrix-twitter.po | 158 ++++-- ...iguring-playbook-bridge-mautrix-wsproxy.po | 13 +- ...uring-playbook-bridge-mx-puppet-discord.po | 13 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 13 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 13 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 13 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 13 +- .../configuring-playbook-bridge-postmoogle.po | 14 +- .../configuring-playbook-bridge-wechat.po | 13 +- .../docs/configuring-playbook-email2matrix.po | 44 +- .../docs/configuring-playbook-ldap-auth.po | 13 +- .../docs/configuring-playbook-ma1sd.po | 14 +- .../configuring-playbook-matrix-corporal.po | 64 ++- .../docs/configuring-playbook-pantalaimon.po | 12 +- .../docs/configuring-playbook-rest-auth.po | 13 +- ...configuring-playbook-shared-secret-auth.po | 13 +- .../docs/configuring-playbook-sygnal.po | 14 +- ...ing-playbook-synapse-auto-accept-invite.po | 43 +- ...guring-playbook-synapse-auto-compressor.po | 15 +- ...guring-playbook-synapse-simple-antispam.po | 27 +- ...ring-playbook-user-verification-service.po | 74 ++- i18n/locales/jp/LC_MESSAGES/README.po | 28 +- ...figuring-playbook-alertmanager-receiver.po | 316 ++++++++---- ...ng-playbook-appservice-draupnir-for-all.po | 303 ++++++++---- .../docs/configuring-playbook-bot-draupnir.po | 457 ++++++++++++------ .../docs/configuring-playbook-bot-go-neb.po | 14 +- .../docs/configuring-playbook-bot-honoroit.po | 16 +- ...ng-playbook-bot-matrix-registration-bot.po | 12 +- ...guring-playbook-bot-matrix-reminder-bot.po | 14 +- .../docs/configuring-playbook-bot-mjolnir.po | 314 +++++++++--- ...ng-playbook-bridge-appservice-kakaotalk.po | 14 +- ...iguring-playbook-bridge-go-skype-bridge.po | 13 +- ...onfiguring-playbook-bridge-heisenbridge.po | 18 +- .../configuring-playbook-bridge-hookshot.po | 403 +++++++++++---- ...uring-playbook-bridge-matrix-bridge-sms.po | 13 +- ...iguring-playbook-bridge-mautrix-twitter.po | 158 ++++-- ...iguring-playbook-bridge-mautrix-wsproxy.po | 13 +- ...uring-playbook-bridge-mx-puppet-discord.po | 13 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 13 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 13 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 13 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 13 +- .../configuring-playbook-bridge-postmoogle.po | 14 +- .../configuring-playbook-bridge-wechat.po | 13 +- .../docs/configuring-playbook-email2matrix.po | 44 +- .../docs/configuring-playbook-ldap-auth.po | 13 +- .../docs/configuring-playbook-ma1sd.po | 14 +- .../configuring-playbook-matrix-corporal.po | 64 ++- .../docs/configuring-playbook-pantalaimon.po | 12 +- .../docs/configuring-playbook-rest-auth.po | 13 +- ...configuring-playbook-shared-secret-auth.po | 13 +- .../docs/configuring-playbook-sygnal.po | 14 +- ...ing-playbook-synapse-auto-accept-invite.po | 43 +- ...guring-playbook-synapse-auto-compressor.po | 15 +- ...guring-playbook-synapse-simple-antispam.po | 27 +- ...ring-playbook-user-verification-service.po | 74 ++- 70 files changed, 3693 insertions(+), 1414 deletions(-) diff --git a/i18n/locales/bg/LC_MESSAGES/README.po b/i18n/locales/bg/LC_MESSAGES/README.po index 9ac7e37f0..10bc599a8 100644 --- a/i18n/locales/bg/LC_MESSAGES/README.po +++ b/i18n/locales/bg/LC_MESSAGES/README.po @@ -8,11 +8,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Project-Id-Version: matrix-docker-ansible-deploy\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" +"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"PO-Revision-Date: 2024-12-20 09:52+0200\n" +"Last-Translator: \n" "Language: bg\n" "Language-Team: bg \n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" @@ -30,10 +30,16 @@ msgid "" "docker-ansible-deploy:devture.com) " "[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" msgstr "" +"[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-" +"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" +"deploy%3Adevture.com&logo=matrix&style=for-the-" +"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" +"docker-ansible-deploy:devture.com) " +"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" #: ../../../README.md:1 msgid "Support room on Matrix" -msgstr "" +msgstr "Matrix стая за поддръжка" #: ../../../README.md:1 msgid "donate" @@ -47,14 +53,18 @@ msgstr "" #: ../../../README.md:5 msgid "🎯 Purpose" -msgstr "" +msgstr "🎯 Цел" #: ../../../README.md:7 msgid "" "This [Ansible](https://www.ansible.com/) playbook is meant to help you " "run your own [Matrix](http://matrix.org/) homeserver, along with the " "[various services](#supported-services) related to that." -msgstr "Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#supported-services), свързани с това." +msgstr "" +"Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви " +"помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен " +"сървър, заедно с [различните услуги](#supported-services), свързани с " +"това." #: ../../../README.md:9 msgid "" @@ -110,7 +120,7 @@ msgstr "" #: ../../../README.md:21 msgid "🚀 Getting started" -msgstr "" +msgstr "🚀 Стартиране" #: ../../../README.md:23 msgid "" @@ -1350,11 +1360,25 @@ msgid "" "deploy/issues)" msgstr "" -#: ../../../README.md:215 +#: ../../../README.md:201 +msgid "🌐 Translation" +msgstr "" + +#: ../../../README.md:203 +msgid "" +"See the [i18n/README.md](i18n/README.md) file for more information about " +"translation." +msgstr "" + +#: ../../../README.md:205 +msgid "Translations are still work in progress." +msgstr "" + +#: ../../../README.md:207 msgid "🤝 Related" msgstr "" -#: ../../../README.md:217 +#: ../../../README.md:209 msgid "" "You may also be interested in [mash-playbook](https://github.com/mother-" "of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" @@ -1363,7 +1387,7 @@ msgid "" "playbook/blob/main/docs/supported-services.md))." msgstr "" -#: ../../../README.md:219 +#: ../../../README.md:211 msgid "" "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" "traefik.md) as its reverse-proxy, so with minor [interoperability " @@ -1372,3 +1396,4 @@ msgid "" "ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " "services on the same server." msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index 6aa45c304..b66d0461a 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: 2024-12-16 12:05+0900\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" @@ -41,19 +41,12 @@ msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 msgid "" "See the project's [documentation](https://github.com/metio/matrix-" -"alertmanager-receiver) to learn more about what this component does and " -"why it might be useful to you." +"alertmanager-receiver/blob/main/README.md) to learn what it does and why " +"it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 msgid "" -"At the moment, **setting up this service's bot requires some manual " -"actions** as described below in [Account and room preparation](#account-" -"and-room-preparation)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 -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 & " @@ -62,27 +55,93 @@ msgid "" "it." msgstr "" +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +msgid "Prerequisites" +msgstr "" + #: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 -msgid "Adjusting the playbook configuration" +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 msgid "" -"To enable matrix-alertmanager-receiver, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +"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:36 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 +msgid "" +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 +msgid "Join to rooms as the bot manually" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 +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:33 +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:35 +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:37 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 +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](#get-an-access-" +"token)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 msgid "" "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " "additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 msgid "" "By default, this playbook installs matrix-alertmanager-receiver on the " "`matrix.` subdomain, at the `/matrix-alertmanager-receiver` path " @@ -91,7 +150,7 @@ msgid "" "to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 msgid "" "By tweaking the `matrix_alertmanager_receiver_hostname` and " "`matrix_alertmanager_receiver_path_prefix` variables, you can easily make" @@ -99,125 +158,61 @@ msgid "" "default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 msgid "" "Example additional configuration for your " "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 msgid "" "If you've changed the default hostname, **you may need to adjust your " "DNS** records to point the matrix-alertmanager-receiver domain to the " "Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 msgid "" "If you've decided to use the default hostname, you won't need to do any " "extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 -msgid "Account and room preparation" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 -msgid "" -"The playbook can automatically create users, but it cannot automatically " -"obtain access tokens, nor perform any of the other manual actions below." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 -msgid "" -"`matrix-alertmanager-receiver` uses a bot (with a username specified in " -"`matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see " -"above) for delivering messages. You need to **manually register this bot " -"acccount and obtain an access token for it**." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 -msgid "" -"[Register a new user](registering-users.md): `ansible-playbook -i " -"inventory/hosts setup.yml --extra-" -"vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT " -"admin=no' --tags=register-user`" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 -msgid "" -"[Obtain an access token](obtaining-access-tokens.md) for the bot's user " -"account" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 -msgid "Invite the bot to a room where you'd like to alerts to be delivered" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 -msgid "" -"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:70 -msgid "" -"(Optionally) Adjust " -"`matrix_alertmanager_receiver_config_matrix_room_mapping` to create a " -"mapping between the new room and its ID" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 -msgid "" -"Steps 1 and 2 above only need to be done once, while preparing your " -"[configuration](#adjusting-the-playbook-configuration)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 -msgid "" -"Steps 3 and 4 need to be done for each new room you'd like the bot to " -"deliver alerts to. Step 5 is optional and provides cleaner `/alert/` " -"URLs." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 msgid "" -"Now that you've [prepared the bot account and room](#account-and-room-" -"preparation), [configured the playbook](#adjusting-the-playbook-" -"configuration), and potentially [adjusted your DNS records](#adjusting-" -"dns-records), you can run the playbook with [playbook tags](playbook-" -"tags.md) as below:" +"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:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 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:89 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:98 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:91 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -226,27 +221,136 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 msgid "" -".. where `URL_HERE` looks like `https://matrix.example.com/matrix-" +"where `URL_HERE` looks like `https://matrix.example.com/matrix-" "alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or " "`https://matrix.example.com/matrix-alertmanager-receiver-" "RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:116 -msgid "" -"This bot does **not** accept room invitations automatically (like many " -"other bots do). To deliver messages to rooms, **the bot must be joined to" -" all rooms manually** - see Step 4 of the [Account and room preparation" -"](#account-and-room-preparation) section." -msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/metio/matrix-alertmanager-" +#~ "receiver) to learn more about what " +#~ "this component does and why it " +#~ "might be useful to you." +#~ msgstr "" + +#~ msgid "" +#~ "At the moment, **setting up this " +#~ "service's bot requires some manual " +#~ "actions** as described below in [Account" +#~ " and room preparation](#account-and-" +#~ "room-preparation)." +#~ msgstr "" + +#~ msgid "" +#~ "To enable matrix-alertmanager-receiver, " +#~ "add the following configuration to your" +#~ " `inventory/host_vars/matrix.example.com/vars.yml` file:" +#~ msgstr "" + +#~ msgid "Account and room preparation" +#~ msgstr "" + +#~ msgid "" +#~ "The playbook can automatically create " +#~ "users, but it cannot automatically " +#~ "obtain access tokens, nor perform any" +#~ " of the other manual actions below." +#~ msgstr "" + +#~ msgid "" +#~ "`matrix-alertmanager-receiver` uses a " +#~ "bot (with a username specified in " +#~ "`matrix_alertmanager_receiver_config_matrix_user_id_localpart` -" +#~ " see above) for delivering messages. " +#~ "You need to **manually register this " +#~ "bot acccount and obtain an access " +#~ "token for it**." +#~ msgstr "" + +#~ msgid "" +#~ "[Register a new user](registering-users.md):" +#~ " `ansible-playbook -i inventory/hosts " +#~ "setup.yml --extra-vars='username=bot.alertmanager.receiver" +#~ " password=PASSWORD_FOR_THE_BOT admin=no' --tags" +#~ "=register-user`" +#~ msgstr "" + +#~ msgid "" +#~ "[Obtain an access token](obtaining-access-" +#~ "tokens.md) for the bot's user account" +#~ msgstr "" + +#~ msgid "Invite the bot to a room where you'd like to alerts to be delivered" +#~ msgstr "" + +#~ msgid "" +#~ "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 "" + +#~ msgid "" +#~ "(Optionally) Adjust " +#~ "`matrix_alertmanager_receiver_config_matrix_room_mapping` to " +#~ "create a mapping between the new " +#~ "room and its ID" +#~ msgstr "" + +#~ msgid "" +#~ "Steps 1 and 2 above only need " +#~ "to be done once, while preparing " +#~ "your [configuration](#adjusting-the-playbook-" +#~ "configuration)." +#~ msgstr "" + +#~ msgid "" +#~ "Steps 3 and 4 need to be " +#~ "done for each new room you'd like" +#~ " the bot to deliver alerts to. " +#~ "Step 5 is optional and provides " +#~ "cleaner `/alert/` URLs." +#~ msgstr "" + +#~ msgid "" +#~ "Now that you've [prepared the bot " +#~ "account and room](#account-and-room-" +#~ "preparation), [configured the playbook" +#~ "](#adjusting-the-playbook-configuration), and " +#~ "potentially [adjusted your DNS records" +#~ "](#adjusting-dns-records), you can run " +#~ "the playbook with [playbook tags](playbook-" +#~ "tags.md) as below:" +#~ msgstr "" + +#~ 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 "" + +#~ msgid "" +#~ "This bot does **not** accept room " +#~ "invitations automatically (like many other " +#~ "bots do). To deliver messages to " +#~ "rooms, **the bot must be joined to" +#~ " all rooms manually** - see Step " +#~ "4 of the [Account and room " +#~ "preparation](#account-and-room-preparation) " +#~ "section." +#~ 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 6e1b9782e..e993b61b9 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: 2024-12-16 12:05+0900\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" @@ -84,27 +84,31 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 -msgid "Installation" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 -msgid "Create a main management room." +msgid "Create a main management room" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 msgid "" "The playbook does not create a management room for your Main Draupnir. " -"This task you have to do on your own." +"You **need to create the room manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 +msgid "Note that the room must be unencrypted." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 msgid "" "The management room has to be given an alias and be public when you are " "setting up the bot for the first time as the bot does not differentiate " "between invites and invites to the management room." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 msgid "" "This management room is used to control who has access to your D4A " "deployment. The room stores this data inside of the control room state so" @@ -112,77 +116,107 @@ msgid "" "This is default 50 or moderator as Element clients call this powerlevel." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33 msgid "" "As noted in the Draupnir install instructions the control room is " -"sensitive. The following is said about the control room in the Draupnir " -"install instructions." +"sensitive. **Anyone in this room can control the bot so it is important " +"that you only invite trusted users to this room.**" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35 +msgid "Set an alias to the management room" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37 +msgid "Next, set an alias to the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39 msgid "" -"Anyone in this room can control the bot so it is important that you only " -"invite trusted users to this room. The room must be unencrypted since the" -" playbook does not support installing Pantalaimon yet." +"This alias can be anything you want. However, for increased security " +"during the setup phase, it is recommended to make this alias be a random " +"string. When it has been locked down after setup phase, you can give your" +" room a secondary human readable alias." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 -msgid "Give your main management room an alias." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 -msgid "" -"Give the room from step 1 an alias. This alias can be anything you want " -"and its recommended for increased security during the setup phase of the " -"bot that you make this alias be a random string. You can give your room a" -" secondary human readable alias when it has been locked down after setup " -"phase." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 -msgid "Adjusting the playbook configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 msgid "" "Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +"`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:40 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 msgid "" -"You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created" -" in step 2." +"You can configure additional options by adding the " +"`matrix_appservice_draupnir_for_all_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55 +msgid "" +"For example, to change Draupnir's `protectAllJoinedRooms` option to " +"`true`, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 +msgid "" +"You can refer to the upstream [documentation](https://github.com/the-" +"draupnir-project/Draupnir) for more configuration documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +msgid "" +"The playbook ships a full copy of the example config that does transfer " +"to provisioned Draupnirs in the production-bots.yaml.j2 file in the " +"template directory of the role." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 +msgid "" +"Config extension does not affect the appservices config as this config is" +" not extensible in current Draupnir anyway. It instead touches the config" +" passed to the Draupnirs that your Appservice creates. So the example " +"above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs " +"protect all joined rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:61 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:63 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -191,29 +225,29 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:65 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 msgid "" "If you made it through all the steps above and your main control room was" " joined by a user called `@draupnir-main:example.com` you have " "succesfully installed Draupnir for All and can now start using it." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98 msgid "" "The installation of Draupnir for all in this playbook is very much Alpha " -"quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot " -"mode." +"quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot" +" mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 msgid "Granting Users the ability to use D4A" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 msgid "" "Draupnir for all includes several security measures like that it only " "allows users that are on its allow list to ask for a bot. To add a user " @@ -224,7 +258,7 @@ msgid "" " the chat is recomended." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 msgid "" "The bot requires a powerlevel of 50 in the management room to control who" " is allowed to use the bot. The bot does currently not say anything if " @@ -233,7 +267,7 @@ msgid "" "project/Draupnir/issues/297))" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 msgid "" "To allow users or whole homeservers you type /plain @draupnir-" "main:example.com allow `target` and target can be either a MXID or a " @@ -242,57 +276,146 @@ msgid "" "this command as it can break Wildcard commands especially." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 -msgid "How to provision a D4A once you are allowed to." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 +msgid "How to provision a D4A once you are allowed to" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 msgid "" -"Open a DM with @draupnir-main:example.com and if using an Element client " -"send a message into this DM to finalise creating it. The bot will reject " -"this invite and you will shortly get invited to the Draupnir control room" -" for your newly provisioned Draupnir. From here its just a normal " -"Draupnir experience." +"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:83 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 msgid "" "Congratulations if you made it all the way here because you now have a " "fully working Draupnir for all deployment." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 -msgid "Configuration of D4A" -msgstr "" +#~ msgid "Installation" +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 -msgid "" -"You can refer to the upstream [documentation](https://github.com/the-" -"draupnir-project/Draupnir) for more configuration documentation. Please " -"note that the playbook ships a full copy of the example config that does " -"transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in " -"the template directory of the role." -msgstr "" +#~ msgid "Create a main management room." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 -msgid "" -"Please note that Config extension does not affect the appservices config " -"as this config is not extensible in current Draupnir anyways. Config " -"extension instead touches the config passed to the Draupnirs that your " -"Appservice creates. So for example below makes all provisioned Draupnirs " -"protect all joined rooms." -msgstr "" +#~ msgid "" +#~ "The playbook does not create a " +#~ "management room for your Main Draupnir." +#~ " This task you have to do on" +#~ " your own." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 -msgid "" -"You can configure additional options by adding the " -"`matrix_appservice_draupnir_for_all_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "" +#~ "As noted in the Draupnir install " +#~ "instructions the control room is " +#~ "sensitive. The following is said about" +#~ " the control room in the Draupnir " +#~ "install instructions." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 -msgid "" -"For example to change Draupnir's `protectAllJoinedRooms` option to `true`" -" you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "Anyone in this room can control " +#~ "the bot so it is important that" +#~ " you only invite trusted users to " +#~ "this room. The room must be " +#~ "unencrypted since the playbook does not" +#~ " support installing Pantalaimon yet." +#~ msgstr "" + +#~ msgid "Give your main management room an alias." +#~ msgstr "" + +#~ msgid "" +#~ "Give the room from step 1 an " +#~ "alias. This alias can be anything " +#~ "you want and its recommended for " +#~ "increased security during the setup " +#~ "phase of the bot that you make " +#~ "this alias be a random string. You" +#~ " can give your room a secondary " +#~ "human readable alias when it has " +#~ "been locked down after setup phase." +#~ msgstr "" + +#~ msgid "Adjusting the playbook configuration." +#~ msgstr "" + +#~ msgid "" +#~ "Add the following configuration to your" +#~ " `inventory/host_vars/matrix.example.com/vars.yml` file " +#~ "(adapt to your needs):" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` " +#~ "with the alias you created in step" +#~ " 2." +#~ msgstr "" + +#~ msgid "" +#~ "The installation of Draupnir for all " +#~ "in this playbook is very much " +#~ "Alpha quality. Usage-wise, Draupnir for" +#~ " allis almost identical to Draupnir " +#~ "bot mode." +#~ msgstr "" + +#~ msgid "How to provision a D4A once you are allowed to." +#~ msgstr "" + +#~ msgid "" +#~ "Open a DM with @draupnir-" +#~ "main:example.com and if using an Element" +#~ " client send a message into this " +#~ "DM to finalise creating it. The " +#~ "bot will reject this invite and " +#~ "you will shortly get invited to " +#~ "the Draupnir control room for your " +#~ "newly provisioned Draupnir. From here " +#~ "its just a normal Draupnir experience." +#~ msgstr "" + +#~ msgid "Configuration of D4A" +#~ msgstr "" + +#~ msgid "" +#~ "You can refer to the upstream " +#~ "[documentation](https://github.com/the-draupnir-" +#~ "project/Draupnir) for more configuration " +#~ "documentation. Please note that the " +#~ "playbook ships a full copy of the" +#~ " example config that does transfer to" +#~ " provisioned Draupnirs in the " +#~ "production-bots.yaml.j2 file in the " +#~ "template directory of the role." +#~ msgstr "" + +#~ msgid "" +#~ "Please note that Config extension does" +#~ " not affect the appservices config as" +#~ " this config is not extensible in " +#~ "current Draupnir anyways. Config extension " +#~ "instead touches the config passed to " +#~ "the Draupnirs that your Appservice " +#~ "creates. So for example below makes " +#~ "all provisioned Draupnirs protect all " +#~ "joined rooms." +#~ msgstr "" + +#~ msgid "" +#~ "You can configure additional options by" +#~ " adding the " +#~ "`matrix_appservice_draupnir_for_all_extension_yaml` variable " +#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" +#~ " file." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Draupnir's " +#~ "`protectAllJoinedRooms` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index 0cd924e1d..2b5dc52fe 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -34,8 +34,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:5 msgid "" "See the project's [documentation](https://github.com/the-draupnir-" -"project/Draupnir) to learn what it does and why it might be useful to " -"you." +"project/Draupnir/blob/main/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:7 @@ -47,21 +47,23 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:9 -msgid "If your migrating from Mjolnir skip to step 5b." +msgid "" +"If your migrating from Mjolnir skip to [this section](#migrating-from-" +"mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:11 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:13 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 @@ -77,7 +79,7 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 msgid "" "If you would like Draupnir to be able to deactivate users, move aliases, " -"shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc " +"shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc " "then it must be a server admin so you need to change `admin=no` to " "`admin=yes` in the command above." msgstr "" @@ -88,8 +90,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 @@ -98,43 +101,65 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 msgid "" -"You will need to prevent Synapse from rate limiting the bot's account. " -"This is not an optional step. If you do not do this step Draupnir will " -"crash. This can be done using Synapse's [admin API](https://matrix-" -"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). Please ask for help if you are uncomfortable " -"with these steps or run into issues." +"If your homeserver's implementation is Synapse, you will need to prevent " +"it from rate limiting the bot's account. **This is a required step. If " +"you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 msgid "" -"If your Synapse Admin API is exposed to the internet for some reason like" -" running the Synapse Admin Role [Link](configuring-playbook-synapse-" -"admin.md) or running " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true` in your playbook config. If your API is not externally exposed you" -" should still be able to on the local host for your synapse run these " -"commands." +"This can be done using Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). They can be accessed both externally and " +"internally." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 msgid "" -"The following command works on semi up to date Windows 10 installs and " -"All Windows 11 installations and other systems that ship curl. `curl " -"--header \"Authorization: Bearer \" -X POST " -"https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" -" Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and " -"example.com with your homeserver domain. You can easily obtain an access " -"token for a homeserver admin account the same way you can obtain an " -"access token for Draupnir itself. If you made Draupnir Admin you can just" -" use the Draupnir token." +"To expose the APIs publicly, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:39 +#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +msgid "" +"The APIs can also be accessed via [Synapse " +"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " +"use to administrate users, rooms, media, etc. on your Matrix server. The " +"playbook can install and configure Synapse Admin for you. For details " +"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +msgid "" +"**Note**: access to the APIs is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, " +"doing so is not recommended for additional security. See [official " +"Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +msgid "" +"To discharge rate limiting, run the following command on systems that " +"ship curl (note that it does not work on outdated Windows 10). Even if " +"the APIs are not exposed to the internet, you should still be able to run" +" the command on the homeserver locally. Before running it, make sure to " +"replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +msgid "" +"You can obtain an access token for a homeserver admin account in the same" +" way as you can do so for Draupnir itself. If you have made Draupnir an " +"admin, you can just use the Draupnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:41 +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 msgid "" "Using your own account, create a new invite only room that you will use " "to manage the bot. This is the room where you will see the status of the " @@ -143,13 +168,13 @@ msgid "" "it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 msgid "" "If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see below)." +"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 msgid "" "Once you have created the room you need to copy the room ID so you can " "tell the bot to use that room. In Element Web you can do this by going to" @@ -157,43 +182,58 @@ msgid "" "room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 msgid "" "Finally invite the `@bot.draupnir:example.com` account you created " "earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:49 +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:51 +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `MANAGEMENT_ROOM_ID_HERE`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:78 msgid "" "Decide whether you want Draupnir to be capable of operating in end-to-end" " encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon" -"](configuring-playbook-pantalaimon.md)." +"moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:53 -msgid "a. Configuration with E2EE support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:80 +msgid "" +"To support E2EE, Draupnir needs to [use Pantalaimon](configuring-" +"playbook-pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +#: ../../../docs/configuring-playbook-bot-draupnir.md:82 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:84 msgid "" "When using Pantalaimon, Draupnir will log in to its bot account itself " "through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:57 -#: ../../../docs/configuring-playbook-bot-draupnir.md:92 +#: ../../../docs/configuring-playbook-bot-draupnir.md:86 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +#: ../../../docs/configuring-playbook-bot-draupnir.md:100 msgid "" "The playbook's `group_vars` will configure other required settings. If " "using this role separately without the playbook, you also need to " @@ -202,65 +242,108 @@ msgid "" "playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:88 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "" "When NOT using Pantalaimon, Draupnir does not log in by itself and you " "must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:94 +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 msgid "" -"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +"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](#get-an-access-" +"token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:104 -msgid "c. Migrating from Mjolnir (Only required if migrating.)" +#: ../../../docs/configuring-playbook-bot-draupnir.md:122 +msgid "Abuse Reports" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:106 +#: ../../../docs/configuring-playbook-bot-draupnir.md:124 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:126 +msgid "" +"The first method intercepts the report API endpoint of the client-server " +"API, which requires integration with the reverse proxy in front of the " +"homeserver. If you are using traefik, this playbook can set this up for " +"you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +msgid "" +"The other method polls an Synapse Admin API endpoint, hence it is " +"available only if using Synapse and if the Draupnir user is an admin (see" +" [above](#register-the-bot-account)). To enable it, set `pollReports: " +"true` on `vars.yml` file as below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_draupnir_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +msgid "" +"For example, to change Draupnir's `pollReports` option to `true`, add the" +" following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +msgid "Migrating from Mjolnir (Only required if migrating)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "" "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " "config. Also disable Mjolnir if you're doing migration." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:108 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "" "That is all you need to do due to that Draupnir can complete migration on" " its own." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:110 +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:119 +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:121 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:123 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:125 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -269,7 +352,7 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:127 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "" "If you change the Pantalaimon's password " "(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " @@ -280,32 +363,32 @@ msgid "" " know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:129 +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:131 +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 msgid "" "You can refer to the upstream [documentation](https://the-draupnir-" "project.github.io/draupnir-documentation/) for additional ways to use and" " configure Draupnir and for a more detailed usage guide." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:133 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:135 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:137 +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 msgid "" "Draupnir can be told to self-join public rooms, but it's better to follow" " this flow which works well for all kinds of rooms:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:139 +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 msgid "" "Invite the bot to the room manually ([inviting Draupnir to rooms](https" "://the-draupnir-project.github.io/draupnir-documentation/moderator" @@ -313,13 +396,13 @@ msgid "" "the bot *may* ask for confirmation in the Management Room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:141 +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 msgid "" "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" "do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:143 +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 msgid "" "Tell it to protect the room (using the [rooms command](https://the-" "draupnir-project.github.io/draupnir-documentation/moderator/managing-" @@ -328,7 +411,7 @@ msgid "" "!qporfwt:example.com`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:145 +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 msgid "" "To have Draupnir provide useful room protection, you need do to a bit " "more work (at least the first time around). You may wish to [Subscribe to" @@ -337,11 +420,11 @@ msgid "" " and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:147 +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:149 +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 msgid "" "For Draupnir to do its job, you need to [give it permissions](https" "://the-draupnir-project.github.io/draupnir-documentation/moderator" @@ -349,7 +432,7 @@ msgid "" "protecting. This involves **giving it an Administrator power level**." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:151 +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 msgid "" "**We recommend setting this power level as soon as the bot joins your " "room** (and before you create new rules), so that it can apply rules as " @@ -358,11 +441,11 @@ msgid "" " it)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:153 +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:155 +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 msgid "" "We recommend **subscribing to a public [policy list](https://the-" "draupnir-project.github.io/draupnir-documentation/concepts/policy-" @@ -371,24 +454,24 @@ msgid "" "watch-command-to-subscribe-to-policy-rooms)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:157 +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 msgid "" "Polcy lists are maintained in Matrix rooms. A popular policy list is " "maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:159 +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 msgid "" "You can tell Draupnir to subscribe to it by sending the following command" " to the Management Room: `!draupnir watch #community-moderation-effort-" "bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:161 +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:163 +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 msgid "" "We also recommend **creating your own policy lists** with the [list " "create](https://the-draupnir-project.github.io/draupnir-" @@ -396,7 +479,7 @@ msgid "" "create-command-to-create-a-policy-room) command." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 msgid "" "You can do so by sending the following command to the Management Room: " "`!draupnir list create my-bans my-bans-bl`. This will create a policy " @@ -405,7 +488,7 @@ msgid "" "command, the bot will invite you to the policy list room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 msgid "" "A policy list does nothing by itself, so the next step is **adding some " "rules to your policy list**. Policies target a so-called `entity` (one " @@ -416,7 +499,7 @@ msgid "" "recommendation)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "" "The simplest and most useful entity to target is `user`. Below are a few " "examples using the [ban command](https://the-draupnir-project.github.io" @@ -424,19 +507,19 @@ msgid "" "targeting users." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "" "To create rules, you run commands in the Management Room (**not** in the " "policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "" "(ban a single user on a given homeserver): `!draupnir ban " "@charles:example.com my-bans Rude to others`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:174 +#: ../../../docs/configuring-playbook-bot-draupnir.md:222 msgid "" "(ban all users on a given homeserver by using a [wildcard](https://the-" "draupnir-project.github.io/draupnir-documentation/moderator/managing-" @@ -444,34 +527,34 @@ msgid "" "all users are fake`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:176 +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:178 +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 msgid "" "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" "bl:example.com` room on your server" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +#: ../../../docs/configuring-playbook-bot-draupnir.md:227 msgid "" "applying these rules against all rooms that Draupnir is an Administrator " "in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 msgid "" "You can undo bans with the [unban command](https://the-draupnir-" "project.github.io/draupnir-documentation/moderator/managing-users#the-" "unban-command)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 msgid "" "You can also **turn on various built-in [protections](https://the-" "draupnir-project.github.io/draupnir-documentation/protections)** like " @@ -479,75 +562,179 @@ msgid "" "room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 msgid "" "To **see which protections are available and which are enabled**, send a " "`!draupnir protections` command to the Management Room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 msgid "" "To **see the configuration options for a given protection**, send a " "`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " "JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "" "To **set a specific option for a given protection**, send a command like " "this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " "`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 msgid "" "To **enable a given protection**, send a command like this: `!draupnir " "enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "" "To **disable a given protection**, send a command like this: `!draupnir " "disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 -msgid "Extending the configuration" -msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/the-draupnir-project/Draupnir) to learn " +#~ "what it does and why it might " +#~ "be useful to you." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_draupnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "If your migrating from Mjolnir skip to step 5b." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 -msgid "" -"For example to change Draupnir's `recordIgnoredInvites` option to `true` " -"you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "The playbook does not automatically " +#~ "create users for you. The bot " +#~ "requires an access token to be " +#~ "able to connect to your homeserver." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 -msgid "Abuse Reports" -msgstr "" +#~ msgid "" +#~ "You **need to register the bot " +#~ "user manually** before setting up the" +#~ " bot." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 -msgid "Draupnir supports two methods to receive reports in the management room." -msgstr "" +#~ msgid "" +#~ "If you would like Draupnir to be" +#~ " able to deactivate users, move " +#~ "aliases, shutdown rooms, show abuse " +#~ "reports ([see below](#abuse-reports)), etc " +#~ "then it must be a server admin " +#~ "so you need to change `admin=no` " +#~ "to `admin=yes` in the command above." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 -msgid "" -"The first method intercepts the report API endpoint of the client-server " -"API, which requires integration with the reverse proxy in front of the " -"homeserver. If you are using traefik, this playbook can set this up for " -"you:" -msgstr "" +#~ msgid "" +#~ "Refer to the documentation on [how " +#~ "to obtain an access token](obtaining-" +#~ "access-tokens.md)." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:225 -msgid "" -"The other method polls an synapse admin API endpoint and is hence only " -"available when using synapse and when the Draupnir user is an admin user " -"(see step 1). To enable it, set `pollReports: true` in Draupnir's config:" -msgstr "" +#~ msgid "" +#~ "You will need to prevent Synapse " +#~ "from rate limiting the bot's account." +#~ " This is not an optional step. " +#~ "If you do not do this step " +#~ "Draupnir will crash. This can be " +#~ "done using Synapse's [admin API](https" +#~ "://matrix-" +#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" +#~ "#override-ratelimiting-for-users). Please " +#~ "ask for help if you are " +#~ "uncomfortable with these steps or run" +#~ " into issues." +#~ msgstr "" + +#~ msgid "" +#~ "If your Synapse Admin API is " +#~ "exposed to the internet for some " +#~ "reason like running the Synapse Admin" +#~ " Role [Link](configuring-playbook-synapse-" +#~ "admin.md) or running " +#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +#~ " true` in your playbook config. If" +#~ " your API is not externally exposed" +#~ " you should still be able to on" +#~ " the local host for your synapse " +#~ "run these commands." +#~ msgstr "" + +#~ msgid "" +#~ "The following command works on semi " +#~ "up to date Windows 10 installs and" +#~ " All Windows 11 installations and " +#~ "other systems that ship curl. `curl " +#~ "--header \"Authorization: Bearer \"" +#~ " -X POST " +#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" +#~ " Replace `@bot.draupnir:example.com` with the " +#~ "MXID of your Draupnir and example.com" +#~ " with your homeserver domain. You can" +#~ " easily obtain an access token for" +#~ " a homeserver admin account the same" +#~ " way you can obtain an access " +#~ "token for Draupnir itself. If you " +#~ "made Draupnir Admin you can just " +#~ "use the Draupnir token." +#~ msgstr "" + +#~ msgid "" +#~ "If you make the management room " +#~ "encrypted (E2EE), then you MUST enable" +#~ " and use Pantalaimon (see below)." +#~ msgstr "" + +#~ msgid "" +#~ "Decide whether you want Draupnir to " +#~ "be capable of operating in end-" +#~ "to-end encrypted (E2EE) rooms. This " +#~ "includes the management room and the " +#~ "moderated rooms. To support E2EE, " +#~ "Draupnir needs to [use Pantalaimon" +#~ "](configuring-playbook-pantalaimon.md)." +#~ msgstr "" + +#~ msgid "a. Configuration with E2EE support" +#~ msgstr "" + +#~ msgid "b. Configuration without E2EE support" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace " +#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " +#~ "values." +#~ msgstr "" + +#~ msgid "c. Migrating from Mjolnir (Only required if migrating.)" +#~ msgstr "" + +#~ msgid "" +#~ "You can configure additional options by" +#~ " adding the " +#~ "`matrix_bot_draupnir_configuration_extension_yaml` variable " +#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" +#~ " file." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Draupnir's " +#~ "`recordIgnoredInvites` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ msgstr "" + +#~ msgid "" +#~ "The other method polls an synapse " +#~ "admin API endpoint and is hence " +#~ "only available when using synapse and" +#~ " when the Draupnir user is an " +#~ "admin user (see step 1). To enable" +#~ " it, set `pollReports: true` in " +#~ "Draupnir's config:" +#~ 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 ac819c836..ed983bb62 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,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"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" @@ -46,8 +46,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:9 msgid "" -"See the project's [documentation](https://github.com/matrix-org/go-neb) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-org/go-" +"neb/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 @@ -204,3 +205,10 @@ msgid "" "/matrix-org/go-neb)." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/go-neb) to learn what it" +#~ " does and why it might be " +#~ "useful to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index f0140fabc..02ef49eae 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -37,9 +37,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:7 msgid "" -"See the project's [documentation](https://github.com/etkecc/honoroit#how-" -"it-looks-like) to learn what it does with screenshots and why it might be" -" useful to you." +"See the project's " +"[documentation](https://github.com/etkecc/honoroit/blob/main/README.md) " +"to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:9 @@ -167,3 +167,11 @@ msgid "" "[documentation](https://github.com/etkecc/honoroit#features)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/etkecc/honoroit#how-it-" +#~ "looks-like) to learn what it does " +#~ "with screenshots and why it might " +#~ "be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index ecb6fe7c7..9d7ccf99e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -44,7 +44,7 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 msgid "" "See the project's [documentation](https://github.com/moan0s/matrix-" -"registration-bot#supported-commands) to learn what it does and why it " +"registration-bot/blob/master/README.md) to learn what it does and why it " "might be useful to you." msgstr "" @@ -146,3 +146,11 @@ msgid "" "etc… you can use:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/moan0s/matrix-" +#~ "registration-bot#supported-commands) to learn " +#~ "what it does and why it might " +#~ "be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index 6bb4c05e2..4875ce7c1 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -40,8 +40,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 msgid "" "See the project's [documentation](https://github.com/anoadragon453" -"/matrix-reminder-bot#usage) to learn what it does and why it might be " -"useful to you." +"/matrix-reminder-bot/blob/master/README.md) to learn what it does and why" +" it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 @@ -134,3 +134,11 @@ msgid "" "bot#usage)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/anoadragon453/matrix-" +#~ "reminder-bot#usage) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index abfc1d669..2075ec200 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -33,22 +33,23 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:5 msgid "" -"See the project's [documentation](https://github.com/matrix-org/mjolnir) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-" +"org/mjolnir/blob/main/README.md) to learn what it does and why it might " +"be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:7 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:9 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:11 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 @@ -74,8 +75,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 @@ -84,43 +86,65 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 msgid "" -"You will need to prevent Synapse from rate limiting the bot's account. " -"This is not an optional step. If you do not do this step Mjolnir will " -"crash. This can be done using Synapse's [admin API](https://matrix-" -"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). Please ask for help if you are uncomfortable " -"with these steps or run into issues." +"If your homeserver's implementation is Synapse, you will need to prevent " +"it from rate limiting the bot's account. **This is a required step. If " +"you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 msgid "" -"If your Synapse Admin API is exposed to the internet for some reason like" -" running the Synapse Admin Role [Link](configuring-playbook-synapse-" -"admin.md) or running " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true` in your playbook config. If your API is not externally exposed you" -" should still be able to on the local host for your synapse run these " -"commands." +"This can be done using Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). They can be accessed both externally and " +"internally." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 msgid "" -"The following command works on semi up to date Windows 10 installs and " -"All Windows 11 installations and other systems that ship curl. `curl " -"--header \"Authorization: Bearer \" -X POST " -"https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" -" Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and " -"example.com with your homeserver domain. You can easily obtain an access " -"token for a homeserver admin account the same way you can obtain an " -"access token for Mjolnir itself. If you made Mjolnir Admin you can just " -"use the Mjolnir token." +"To expose the APIs publicly, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +msgid "" +"The APIs can also be accessed via [Synapse " +"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " +"use to administrate users, rooms, media, etc. on your Matrix server. The " +"playbook can install and configure Synapse Admin for you. For details " +"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +msgid "" +"**Note**: access to the APIs is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, " +"doing so is not recommended for additional security. See [official " +"Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +msgid "" +"To discharge rate limiting, run the following command on systems that " +"ship curl (note that it does not work on outdated Windows 10). Even if " +"the APIs are not exposed to the internet, you should still be able to run" +" the command on the homeserver locally. Before running it, make sure to " +"replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +msgid "" +"You can obtain an access token for a homeserver admin account in the same" +" way as you can do so for Mjolnir itself. If you have made Mjolnir an " +"admin, you can just use the Mjolnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "" "Using your own account, create a new invite only room that you will use " "to manage the bot. This is the room where you will see the status of the " @@ -129,13 +153,13 @@ msgid "" "it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 msgid "" "If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see below)." +"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 msgid "" "Once you have created the room you need to copy the room ID so you can " "tell the bot to use that room. In Element Web you can do this by going to" @@ -143,44 +167,58 @@ msgid "" "room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 msgid "" "Finally invite the `@bot.mjolnir:example.com` account you created earlier" " into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `MANAGEMENT_ROOM_ID_HERE`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 msgid "" "Decide whether you want Mjolnir to be capable of operating in end-to-end " "encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon" -"](configuring-playbook-pantalaimon.md)." +"moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 -msgid "a. Configuration with E2EE support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:76 +msgid "" +"To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-" +"pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 msgid "" "When using Pantalaimon, Mjolnir will log in to its bot account itself " "through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 msgid "" "The playbook's `group_vars` will configure other required settings. If " "using this role separately without the playbook, you also need to " @@ -189,53 +227,80 @@ msgid "" "playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "" "When NOT using Pantalaimon, Mjolnir does not log in by itself and you " "must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "" -"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +"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](#get-an-access-" +"token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +msgid "" +"To enable Mjolnir synapse antispam module, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +msgid "" +"For example, to change Mjolnir's `recordIgnoredInvites` option to `true`," +" add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -244,7 +309,7 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 msgid "" "If you change the Pantalaimon's password " "(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " @@ -255,11 +320,11 @@ msgid "" "know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 msgid "" "You can refer to the upstream [documentation](https://github.com/matrix-" "org/mjolnir) for additional ways to use and configure Mjolnir. Check out " @@ -267,16 +332,113 @@ msgid "" "#quickstart-guide) for some basic commands you can give to the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/mjolnir) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 -msgid "" -"For example to change Mjolnir's `recordIgnoredInvites` option to `true` " -"you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "The playbook does not automatically " +#~ "create users for you. The bot " +#~ "requires an access token to be " +#~ "able to connect to your homeserver." +#~ msgstr "" + +#~ msgid "" +#~ "You **need to register the bot " +#~ "user manually** before setting up the" +#~ " bot." +#~ msgstr "" + +#~ msgid "" +#~ "Refer to the documentation on [how " +#~ "to obtain an access token](obtaining-" +#~ "access-tokens.md)." +#~ msgstr "" + +#~ msgid "" +#~ "You will need to prevent Synapse " +#~ "from rate limiting the bot's account." +#~ " This is not an optional step. " +#~ "If you do not do this step " +#~ "Mjolnir will crash. This can be " +#~ "done using Synapse's [admin API](https" +#~ "://matrix-" +#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" +#~ "#override-ratelimiting-for-users). Please " +#~ "ask for help if you are " +#~ "uncomfortable with these steps or run" +#~ " into issues." +#~ msgstr "" + +#~ msgid "" +#~ "If your Synapse Admin API is " +#~ "exposed to the internet for some " +#~ "reason like running the Synapse Admin" +#~ " Role [Link](configuring-playbook-synapse-" +#~ "admin.md) or running " +#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +#~ " true` in your playbook config. If" +#~ " your API is not externally exposed" +#~ " you should still be able to on" +#~ " the local host for your synapse " +#~ "run these commands." +#~ msgstr "" + +#~ msgid "" +#~ "The following command works on semi " +#~ "up to date Windows 10 installs and" +#~ " All Windows 11 installations and " +#~ "other systems that ship curl. `curl " +#~ "--header \"Authorization: Bearer \"" +#~ " -X POST " +#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" +#~ " Replace `@bot.mjolnir:example.com` with the " +#~ "MXID of your Mjolnir and example.com " +#~ "with your homeserver domain. You can " +#~ "easily obtain an access token for " +#~ "a homeserver admin account the same " +#~ "way you can obtain an access token" +#~ " for Mjolnir itself. If you made " +#~ "Mjolnir Admin you can just use the" +#~ " Mjolnir token." +#~ msgstr "" + +#~ msgid "" +#~ "If you make the management room " +#~ "encrypted (E2EE), then you MUST enable" +#~ " and use Pantalaimon (see below)." +#~ msgstr "" + +#~ msgid "" +#~ "Decide whether you want Mjolnir to " +#~ "be capable of operating in end-" +#~ "to-end encrypted (E2EE) rooms. This " +#~ "includes the management room and the " +#~ "moderated rooms. To support E2EE, " +#~ "Mjolnir needs to [use Pantalaimon" +#~ "](configuring-playbook-pantalaimon.md)." +#~ msgstr "" + +#~ msgid "a. Configuration with E2EE support" +#~ msgstr "" + +#~ msgid "b. Configuration without E2EE support" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace " +#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " +#~ "values." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Mjolnir's " +#~ "`recordIgnoredInvites` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ 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 6f6d15853..eb6315d87 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: 2024-12-16 12:05+0900\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" @@ -45,8 +45,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 msgid "" "See the project's [documentation](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk) to learn what it does and why it might be useful to" -" you." +"appservice-kakaotalk/src/branch/master/README.md) to learn what it does " +"and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 @@ -228,3 +228,11 @@ msgid "" "in the future, as that would break the Double Puppeting feature" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://src.miscworks.net/fair/matrix-" +#~ "appservice-kakaotalk) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ 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 47df023ab..b322b503e 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/kelaresg/go-skype-" +"bridge/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 @@ -98,3 +99,9 @@ msgstr "" msgid "Send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 0edf49773..919f68a76 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: 2024-12-16 12:05+0900\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" @@ -43,9 +43,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 msgid "" "See the project's " -"[README](https://github.com/hifi/heisenbridge/blob/master/README.md) to " -"learn what it does and why it might be useful to you. You can also take a" -" look at [this demonstration " +"[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 "" @@ -183,3 +183,13 @@ msgid "" "[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[README](https://github.com/hifi/heisenbridge/blob/master/README.md)" +#~ " to learn what it does and why" +#~ " it might be useful to you. You" +#~ " can also take a look at [this" +#~ " demonstration " +#~ "video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +#~ 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 dfb2b601d..394ad2aa8 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: 2024-12-16 12:05+0900\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" @@ -34,15 +34,15 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:5 msgid "" "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " -"from software project management services such as GitHub, GitLab, JIRA, " +"from software project management services such as GitHub, GitLab, Jira, " "and Figma, as well as generic webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:7 msgid "" "See the project's [documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/hookshot.html) to learn what it does in detail and why it" -" might be useful to you." +"hookshot/latest/hookshot.html) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:9 @@ -53,152 +53,172 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:11 -msgid "Setup Instructions" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:13 -msgid "" -"Refer to the [official instructions](https://matrix-org.github.io/matrix-" -"hookshot/latest/setup.html) to learn what the individual options do." +msgid "Download GitHub app private key (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:15 msgid "" -"Enable the bridge by adding `matrix_hookshot_enabled: true` to your " -"`vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 -msgid "" -"For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) " -"fill in the respective variables `matrix_hookshot_service_*` listed in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as " -"required." +"If you're setting up the GitHub bridge, you need to create your GitHub " +"app, and generate a private key file of it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:17 msgid "" -"Take special note of the `matrix_hookshot_*_enabled` variables. Services " -"that need no further configuration are enabled by default (GitLab, " -"Generic), while you must first add the required configuration and enable " -"the others (GitHub, Jira, Figma)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 -msgid "" -"If you're setting up the GitHub bridge, you'll need to generate and " -"download a private key file after you created your GitHub app. Copy the " -"contents of that file to the variable " -"`matrix_hookshot_github_private_key` so the playbook can install it for " -"you, or use one of the [other methods](#manage-github-private-key-with-" -"aux-role) explained below." +"You need to download the private key file, if you will install the file " +"manually or with the `aux` role. For details, see [the section below" +"](#manage-github-private-key-with-aux-role)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:19 -msgid "" -"If you've already installed Matrix services using the playbook before, " -"you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with" -" [configuring other playbook services](configuring-playbook.md) and then " -"with [Installing](installing.md). Get back to this guide once ready. " -"Hookshot can be set up individually using the tag `setup-hookshot`." +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:21 msgid "" -"Other configuration options are available via the " +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-" +"github-app-private-key)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 +msgid "" +"For each of the services (GitHub, GitLab, Jira, Figma, and generic " +"webhooks) fill in the respective variables `matrix_hookshot_service_*` " +"listed in [main.yml](../roles/custom/matrix-bridge-" +"hookshot/defaults/main.yml) as required." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 +msgid "" +"Take special note of the `matrix_hookshot_*_enabled` variables. Services " +"that need no further configuration are enabled by default (GitLab and " +"generic webhooks), while you must first add the required configuration " +"and enable the others (GitHub, Jira, and Figma)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 +msgid "" +"You can configure additional options by adding the " "`matrix_hookshot_configuration_extension_yaml` and " -"`matrix_hookshot_registration_extension_yaml` variables, see the comments" -" in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) " -"for how to use them." +"`matrix_hookshot_registration_extension_yaml` variables." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 -msgid "Finally, run the playbook (see [installing](installing.md))." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 -msgid "End-to-bridge encryption" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 msgid "" -"You can enable [encryption](https://matrix-org.github.io/matrix-" -"hookshot/latest/advanced/encryption.html) for Hookshot by adding " -"`matrix_hookshot_encryption_enabled: true` to your configuration " -"(`vars.yml`) and [executing the playbook](installing.md) again." +"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:29 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 msgid "" -"Should the crypto store be corrupted, you can reset it by executing this " -"Ansible playbook with the tag `reset-hookshot-encryption` added, for " -"example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-" -"hookshot-encryption`." +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-service hookshot` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 +msgid "" +"`just install-service hookshot` is useful for maintaining your setup " +"quickly when its components remain unchanged. If you adjust your " +"`vars.yml` to remove other components, you'd need to run `just setup-" +"all`, or these components will still remain installed. Note `just setup-" +"all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:58 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:60 msgid "" "To use the bridge, you need to create a room and invite the Hookshot bot " "(`@hookshot:example.com`) to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:62 msgid "" "Make sure the bot is able to send state events (usually the Moderator " "power level in clients)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 -msgid "Send a `!hookshot help` message to see a list of help commands." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:64 +msgid "" +"Send `!hookshot help` to the room to see the bridge's help menu for " +"additional commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:66 msgid "" "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-" "hookshot/latest/usage.html) for more details about using the bridge's " "various features." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:68 msgid "" -"**Important**: Note that the different listeners are bound to certain " -"paths which might differ from those assumed by the hookshot " -"documentation, see [URLs for bridges setup](#urls-for-bridges-setup) " -"below." +"💡 **Note**: the different listeners are bound to certain paths which " +"might differ from those assumed by the hookshot documentation. See [URLs " +"for bridges setup](#urls-for-bridges-setup) below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +msgid "Reset crypto store" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 +msgid "" +"Should the crypto store be corrupted, you can reset it by executing this " +"Ansible playbook with the tag `reset-hookshot-encryption` added:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:78 msgid "More setup documentation" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:80 msgid "URLs for bridges setup" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:82 msgid "" "Unless indicated otherwise, the following endpoints are reachable on your" " `matrix.` subdomain (if the feature is enabled)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "listener" +msgid "Listener" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "default path" +msgid "Default path" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "variable" +msgid "Variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "used as" +msgid "Used as" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -262,7 +282,7 @@ msgid "`matrix_hookshot_jira_oauth_endpoint`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "JIRA OAuth" +msgid "Jira OAuth" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -349,71 +369,72 @@ msgstr "" msgid "Prometheus" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:96 msgid "" "Also see the various `matrix_hookshot_container_labels_*` variables in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml), which" -" expose URLs publicly." +"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), " +"which expose URLs publicly" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 msgid "" "The different listeners are also reachable *internally* in the docker-" "network via the container's name (configured by " "`matrix_hookshot_container_url`) and on different ports (e.g. " -"`matrix_hookshot_appservice_port`). Read [main.yml](/roles/custom/matrix-" -"bridge-hookshot/defaults/main.yml) in detail for more info." +"`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:65 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 msgid "Manage GitHub Private Key with aux role" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:102 msgid "" "The GitHub bridge requires you to install a private key file. This can be" " done in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:68 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 msgid "" "copy the *contents* of the downloaded file and set the variable " "`matrix_hookshot_github_private_key` to the contents (see example in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml))." +"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 msgid "" "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ " "matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot" "/private-key.pem`) on the server manually." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:106 msgid "" "use the [`aux` role](https://github.com/mother-of-all-self-hosting" "/ansible-role-aux) to copy the file from an arbitrary path on your " "ansible client to the correct path on the server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:108 msgid "" "To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" -" variable is empty. Then add the following additional configuration:" +" variable is empty. Then add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 msgid "" "For more information, see the documentation in the [default configuration" " of the aux role](https://github.com/mother-of-all-self-hosting/ansible-" "role-aux/blob/main/defaults/main.yml)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:121 msgid "Provisioning API" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:123 msgid "" "The provisioning API will be enabled automatically if you set " "`matrix_dimension_enabled: true` and provided a " @@ -423,11 +444,11 @@ msgid "" "`matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:89 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:125 msgid "Metrics" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:127 msgid "" "Metrics are **only enabled by default** if the builtin [Prometheus" "](configuring-playbook-prometheus-grafana.md) is enabled (by default, " @@ -436,32 +457,32 @@ msgid "" "set up your own Dashboard for displaying them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:93 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:129 msgid "" "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: " "true`. This only exposes metrics over the container network, however." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:95 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:131 msgid "" "**To collect metrics from an external Prometheus server**, besides " "enabling metrics as described above, you will also need to enable metrics" " exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:97 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:133 msgid "" "either enabling metrics exposure for Hookshot via " "`matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 msgid "" "or enabling metrics exposure for all services via " "`matrix_metrics_exposure_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 msgid "" "Whichever one you go with, by default metrics are exposed publicly " "**without** password-protection. See [the Prometheus and Grafana docs" @@ -469,11 +490,11 @@ msgid "" "protection for metrics." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:102 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 msgid "Collision with matrix-appservice-webhooks" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:140 msgid "" "If you are also running [matrix-appservice-webhooks](configuring-" "playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" @@ -483,3 +504,175 @@ msgid "" "`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." msgstr "" +#~ 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 "" + +#~ msgid "" +#~ "See the project's [documentation](https://matrix-" +#~ "org.github.io/matrix-hookshot/latest/hookshot.html) to " +#~ "learn what it does in detail and" +#~ " why it might be useful to you." +#~ msgstr "" + +#~ msgid "Setup Instructions" +#~ msgstr "" + +#~ msgid "" +#~ "Refer to the [official instructions](https" +#~ "://matrix-org.github.io/matrix-hookshot/latest/setup.html)" +#~ " to learn what the individual options" +#~ " do." +#~ msgstr "" + +#~ msgid "" +#~ "Enable the bridge by adding " +#~ "`matrix_hookshot_enabled: true` to your " +#~ "`vars.yml` file" +#~ msgstr "" + +#~ msgid "" +#~ "For each of the services (GitHub, " +#~ "GitLab, Jira, Figma, generic webhooks) " +#~ "fill in the respective variables " +#~ "`matrix_hookshot_service_*` listed in " +#~ "[main.yml](/roles/custom/matrix-bridge-" +#~ "hookshot/defaults/main.yml) as required." +#~ msgstr "" + +#~ msgid "" +#~ "Take special note of the " +#~ "`matrix_hookshot_*_enabled` variables. Services that" +#~ " need no further configuration are " +#~ "enabled by default (GitLab, Generic), " +#~ "while you must first add the " +#~ "required configuration and enable the " +#~ "others (GitHub, Jira, Figma)." +#~ msgstr "" + +#~ msgid "" +#~ "If you're setting up the GitHub " +#~ "bridge, you'll need to generate and " +#~ "download a private key file after " +#~ "you created your GitHub app. Copy " +#~ "the contents of that file to the" +#~ " variable `matrix_hookshot_github_private_key` so " +#~ "the playbook can install it for " +#~ "you, or use one of the [other " +#~ "methods](#manage-github-private-key-with-" +#~ "aux-role) explained below." +#~ msgstr "" + +#~ msgid "" +#~ "If you've already installed Matrix " +#~ "services using the playbook before, " +#~ "you'll need to re-run it (`--tags" +#~ "=setup-all,start`). If not, proceed with" +#~ " [configuring other playbook services" +#~ "](configuring-playbook.md) and then with " +#~ "[Installing](installing.md). Get back to this" +#~ " guide once ready. Hookshot can be" +#~ " set up individually using the tag" +#~ " `setup-hookshot`." +#~ msgstr "" + +#~ msgid "" +#~ "Other configuration options are available " +#~ "via the `matrix_hookshot_configuration_extension_yaml` " +#~ "and `matrix_hookshot_registration_extension_yaml` " +#~ "variables, see the comments in " +#~ "[main.yml](/roles/custom/matrix-bridge-" +#~ "hookshot/defaults/main.yml) for how to use " +#~ "them." +#~ msgstr "" + +#~ msgid "Finally, run the playbook (see [installing](installing.md))." +#~ msgstr "" + +#~ msgid "End-to-bridge encryption" +#~ msgstr "" + +#~ msgid "" +#~ "You can enable [encryption](https://matrix-" +#~ "org.github.io/matrix-hookshot/latest/advanced/encryption.html)" +#~ " for Hookshot by adding " +#~ "`matrix_hookshot_encryption_enabled: true` to your" +#~ " configuration (`vars.yml`) and [executing " +#~ "the playbook](installing.md) again." +#~ msgstr "" + +#~ msgid "" +#~ "Should the crypto store be corrupted," +#~ " you can reset it by executing " +#~ "this Ansible playbook with the tag " +#~ "`reset-hookshot-encryption` added, for " +#~ "example `ansible-playbook -i inventory/hosts" +#~ " setup.yml --tags=reset-hookshot-encryption`." +#~ msgstr "" + +#~ msgid "Send a `!hookshot help` message to see a list of help commands." +#~ msgstr "" + +#~ msgid "" +#~ "**Important**: Note that the different " +#~ "listeners are bound to certain paths " +#~ "which might differ from those assumed" +#~ " by the hookshot documentation, see " +#~ "[URLs for bridges setup](#urls-for-" +#~ "bridges-setup) below." +#~ msgstr "" + +#~ msgid "listener" +#~ msgstr "" + +#~ msgid "default path" +#~ msgstr "" + +#~ msgid "variable" +#~ msgstr "" + +#~ msgid "used as" +#~ msgstr "" + +#~ msgid "JIRA OAuth" +#~ msgstr "" + +#~ 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 "" + +#~ 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 "" + +#~ 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 "" + +#~ msgid "" +#~ "To use the `aux` role, make sure" +#~ " the `matrix_hookshot_github_private_key` variable " +#~ "is empty. Then add the following " +#~ "additional configuration:" +#~ 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 ef36a1e26..d3f504115 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/benkuly/matrix-sms-" +"bridge/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 @@ -99,3 +100,9 @@ msgid "" "bridge/blob/master/README.md#user-guide) to see how this bridge works." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 081ced85a..76826e601 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: 2024-12-16 12:05+0900\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" @@ -40,8 +40,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 msgid "" -"See the project's [documentation](https://github.com/mautrix/twitter) to " -"learn what it does and why it might be useful to you." +"See the project's " +"[documentation](https://github.com/mautrix/twitter/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 @@ -49,58 +50,61 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 msgid "" "If you want to set up [Double " "Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " "(hint: you most likely do) for this bridge automatically, you need to " "have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +"double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 msgid "" "For details about configuring Double Puppeting for this bridge, see the " "section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 msgid "" "To enable the bridge, add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -109,71 +113,60 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44 msgid "" "You then need to start a chat with `@twitterbot:example.com` (where " "`example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 msgid "" "Send login-cookie to start the login. The bot should respond with " "instructions on how to proceed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 msgid "" "You can learn more here about authentication from the bridge's [official " "documentation on " "Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 msgid "💡 Set up Double Puppeting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 msgid "" "After successfully enabling bridging, you may wish to set up [Double " "Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " "(hint: you most likely do)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 msgid "To set it up, you have 2 ways of going about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" -msgstr "" - #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 @@ -182,9 +175,88 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 msgid "" -"This method is currently not available for the Mautrix-Twitter bridge, " -"but is on the " -"[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) " -"under Misc/Manual login with `login-matrix`" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" msgstr "" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69 +msgid "" +"make sure you don't log out the `Mautrix-Slack` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/mautrix/twitter) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ msgstr "" + +#~ 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 "" + +#~ msgid "" +#~ "Method 1: automatically, by enabling " +#~ "Appservice Double Puppet or Shared " +#~ "Secret Auth" +#~ msgstr "" + +#~ msgid "" +#~ "The bridge automatically performs Double " +#~ "Puppeting if [Appservice Double Puppet" +#~ "](configuring-playbook-appservice-double-" +#~ "puppet.md) or [Shared Secret Auth" +#~ "](configuring-playbook-shared-secret-auth.md) " +#~ "service is configured and enabled on " +#~ "the server for this playbook." +#~ msgstr "" + +#~ msgid "" +#~ "Enabling [Appservice Double Puppet](configuring-" +#~ "playbook-appservice-double-puppet.md) is " +#~ "the recommended way of setting up " +#~ "Double Puppeting, as it's easier to " +#~ "accomplish, works for all your users " +#~ "automatically, and has less of a " +#~ "chance of breaking in the future." +#~ msgstr "" + +#~ msgid "" +#~ "Enabling double puppeting by enabling " +#~ "the [Shared Secret Auth](configuring-" +#~ "playbook-shared-secret-auth.md) service " +#~ "works at the time of writing, but" +#~ " is deprecated and will stop working" +#~ " in the future." +#~ msgstr "" + +#~ msgid "" +#~ "This method is currently not available" +#~ " for the Mautrix-Twitter bridge, but" +#~ " is on the " +#~ "[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md)" +#~ " under Misc/Manual login with `login-" +#~ "matrix`" +#~ 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 6a2c5924a..91e79ff01 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: 2024-12-16 12:05+0900\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" @@ -36,8 +36,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 msgid "" "See the project's " -"[documentation](https://github.com/mautrix/wsproxy#readme) to learn what " -"it does and why it might be useful to you." +"[documentation](https://github.com/mautrix/wsproxy/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 @@ -144,3 +144,10 @@ msgid "" "running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/mautrix/wsproxy#readme) to" +#~ " learn what it does and why it" +#~ " might be useful to you." +#~ 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 26c2b1f5b..f71b36d15 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: 2024-12-16 12:05+0900\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" @@ -55,8 +55,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/mx-puppet/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 @@ -138,3 +139,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 9aa89f8cd..eb1a89f86 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: 2024-12-16 12:05+0900\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" @@ -34,8 +34,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/xangelix-pub/matrix" +"/mx-puppet-groupme/blob/master/README.md) to learn what it does and why " +"it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 @@ -122,3 +123,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 93cc2b2bc..344a58cfc 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,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"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" @@ -41,8 +41,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 @@ -135,3 +136,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 41cb05e14..f39f3bcfd 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/icewind1991/mx-" +"puppet-steam/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 @@ -115,3 +116,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 de0581490..8b1dec811 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: 2024-12-16 12:05+0900\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" @@ -40,8 +40,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/Sorunome/mx-puppet-" +"twitter/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 @@ -129,3 +130,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index e16cef9a6..d35e570a5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"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" @@ -42,8 +42,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 msgid "" -"See the project's [documentation](https://github.com/etkecc/postmoogle) " -"to learn what it does and why it might be useful to you." +"See the project's " +"[documentation](https://github.com/etkecc/postmoogle/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 @@ -192,3 +193,10 @@ msgid "" " it to `DEBUG` with the following additional configuration:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/etkecc/postmoogle) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 95a401bfa..24e25c999 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: 2024-12-16 12:05+0900\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" @@ -34,8 +34,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/duo/matrix-" +"wechat/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:7 @@ -97,3 +98,9 @@ msgstr "" msgid "Send `help` to the bot to see the available commands." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 199006251..18d078a8e 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: 2024-12-16 12:05+0900\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" @@ -227,33 +227,59 @@ msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 msgid "" -"To enable Email2Matrix, run the playbook with [playbook tags](playbook-" +"After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:93 +#: ../../../docs/configuring-playbook-email2matrix.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:95 +#: ../../../docs/configuring-playbook-email2matrix.md:96 msgid "" "The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-email2matrix,start` or `just setup-all`" +"available: `just install-service email2matrix` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:97 +#: ../../../docs/configuring-playbook-email2matrix.md:98 msgid "" -"`just run-tags setup-email2matrix,start` is useful for maintaining your " -"setup quickly when its components remain unchanged. If you adjust your " +"`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:99 +#: ../../../docs/configuring-playbook-email2matrix.md:100 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 "" +#~ msgid "" +#~ "To enable Email2Matrix, run the playbook" +#~ " with [playbook tags](playbook-tags.md) as" +#~ " below:" +#~ msgstr "" + +#~ msgid "" +#~ "The shortcut commands with the [`just`" +#~ " program](just.md) are also available: " +#~ "`just run-tags setup-email2matrix,start` " +#~ "or `just setup-all`" +#~ msgstr "" + +#~ msgid "" +#~ "`just run-tags setup-email2matrix,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 "" + 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 ebb1713a3..201c1802b 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: 2024-12-16 12:05+0900\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" @@ -36,8 +36,9 @@ msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"synapse-ldap3/blob/main/README.rst) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:7 @@ -82,3 +83,9 @@ msgid "" "](configuring-playbook-matrix-ldap-registration-proxy.md)." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 96aae51be..50a616c77 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: 2024-12-16 12:05+0900\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" @@ -53,8 +53,9 @@ msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:9 msgid "" -"See the project's [documentation](https://github.com/ma1uta/ma1sd) to " -"learn what it does and why it might be useful to you." +"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 @@ -333,3 +334,10 @@ msgid "" "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/ma1uta/ma1sd) to learn" +#~ " what it does and why it might" +#~ " be useful to you." +#~ 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 81721ce7b..76289ff29 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: 2024-12-16 12:05+0900\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" @@ -43,101 +43,107 @@ msgstr "" 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. See that project's documentation to learn what it does and " -"why it might be useful to you." +"environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:13 msgid "" +"See the project's [documentation](https://github.com/devture/matrix-" +"corporal/blob/main/README.md) to learn what it does and why it might be " +"useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +msgid "" "If you decide that you'd like to let this playbook install it for you, " "you'd need to also:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:14 +#: ../../../docs/configuring-playbook-matrix-corporal.md:16 msgid "" "(required) [set up the Shared Secret Auth password provider module" "](configuring-playbook-shared-secret-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 msgid "" "(optional, but encouraged) [set up the REST authentication password " "provider module](configuring-playbook-rest-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:17 +#: ../../../docs/configuring-playbook-matrix-corporal.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:19 +#: ../../../docs/configuring-playbook-matrix-corporal.md:21 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:72 +#: ../../../docs/configuring-playbook-matrix-corporal.md:74 msgid "" "Matrix Corporal operates with a specific Matrix user on your server. By " "default, it's `matrix-corporal` (controllable by the " "`matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:74 +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 msgid "" "No matter what Matrix user ID you configure to run it with, make sure " "that:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +#: ../../../docs/configuring-playbook-matrix-corporal.md:78 msgid "" "the Matrix Corporal user is created by [registering it](registering-" "users.md) **with administrator privileges**. Use a password you remember," " as you'll need to log in from time to time to create or join rooms" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:78 +#: ../../../docs/configuring-playbook-matrix-corporal.md:80 msgid "" "the Matrix Corporal user is joined and has Admin/Moderator-level access " "to any rooms you want it to manage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:80 +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 msgid "Using a locally-stored static policy" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +#: ../../../docs/configuring-playbook-matrix-corporal.md:84 msgid "" "If you'd like to use a [static policy file](https://github.com/devture" "/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-" "style-policy-provider), you can use a configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:114 +#: ../../../docs/configuring-playbook-matrix-corporal.md:116 msgid "" "To learn more about what the policy configuration, see the matrix-" "corporal documentation on [policy](https://github.com/devture/matrix-" "corporal/blob/master/docs/policy.md)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:116 +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +#: ../../../docs/configuring-playbook-matrix-corporal.md:120 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +#: ../../../docs/configuring-playbook-matrix-corporal.md:127 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just run-tags setup-aux-files,setup-corporal,start` or `just " "setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:127 +#: ../../../docs/configuring-playbook-matrix-corporal.md:129 msgid "" "`just run-tags setup-aux-files,setup-corporal,start` is useful for " "maintaining your setup quickly when its components remain unchanged. If " @@ -146,33 +152,33 @@ msgid "" "`just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:129 +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 msgid "Matrix Corporal files" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +#: ../../../docs/configuring-playbook-matrix-corporal.md:133 msgid "" "The following local filesystem paths are mounted in the `matrix-corporal`" " container and can be used in your configuration (or policy):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:133 +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 msgid "" "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " "write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 msgid "" "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" " and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +#: ../../../docs/configuring-playbook-matrix-corporal.md:141 msgid "" "As an example: you can create your own configuration files in " "`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " @@ -183,3 +189,13 @@ msgid "" "and write)." msgstr "" +#~ 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. See that project's documentation" +#~ " to learn what it does and why" +#~ " it might be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po index 770043c21..d5a6e3ef0 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -35,7 +35,8 @@ msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:5 msgid "" "See the project's [documentation](https://github.com/matrix-" -"org/pantalaimon) to learn what it does and why it might be useful to you." +"org/pantalaimon/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:7 @@ -91,3 +92,10 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/pantalaimon) to learn what it" +#~ " does and why it might be " +#~ "useful to you." +#~ 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 64f262b10..50a5e7e41 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,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"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" @@ -32,8 +32,9 @@ msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/ma1uta/matrix-" +"synapse-rest-password-provider/blob/master/README.md) to learn what it " +"does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:7 @@ -84,3 +85,9 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 06e5c3081..3cdbd4254 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: 2024-12-16 12:05+0900\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" @@ -36,8 +36,9 @@ msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/devture/matrix-" +"synapse-shared-secret-auth/blob/master/README.md) to learn what it does " +"and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:7 @@ -87,3 +88,9 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 6ab90bf55..2954af972 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:5 msgid "" -"See the project's [documentation](https://github.com/matrix-org/sygnal) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-" +"org/sygnal/blob/master/README.md) to learn what it does and why it might " +"be useful to you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:7 @@ -200,3 +201,10 @@ msgid "" "/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/sygnal) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ 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 b7dce7685..257927ce2 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: 2024-12-16 12:05+0900\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" @@ -34,15 +34,20 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 msgid "" -"See that project's [documentation](https://github.com/matrix-org/synapse-" -"auto-accept-invite) to learn what it does and why it might be useful to " -"you. In short, it automatically accepts room invites. You can specify " -"that only 1:1 room invites are auto-accepted. Defaults to false if not " +"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 " @@ -52,11 +57,11 @@ msgid "" "party module." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 msgid "Configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +#: ../../../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-" @@ -64,11 +69,11 @@ msgid "" "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:19 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 msgid "Synapse worker deployments" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23 msgid "" "In a [workerized Synapse deployment](https://github.com/spantaleev" "/matrix-docker-ansible-" @@ -78,17 +83,17 @@ msgid "" "is `null`). For example, add this to your configuration:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:27 +#: ../../../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:29 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +#: ../../../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 " @@ -97,7 +102,19 @@ msgid "" "/element-hq/synapse/pull/17147) part of Synapse." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:35 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" +#~ msgid "" +#~ "See that project's " +#~ "[documentation](https://github.com/matrix-org/synapse-" +#~ "auto-accept-invite) to learn what it" +#~ " does and why it might be " +#~ "useful to you. In short, it " +#~ "automatically accepts room invites. You " +#~ "can specify that only 1:1 room " +#~ "invites are auto-accepted. Defaults to" +#~ " false if not specified." +#~ 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 9d7430ffd..46ecd6c5a 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: 2024-12-16 12:05+0900\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" @@ -41,8 +41,9 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 msgid "" "See the project's [documentation](https://github.com/matrix-org/rust-" -"synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn " -"what it does and why it might be useful to you." +"synapse-compress-state/blob/master/README.md#automated-tool-" +"synapse_auto_compressor) to learn what it does and why it might be useful" +" to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 @@ -107,3 +108,11 @@ msgid "" "unstable." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/rust-synapse-compress-state" +#~ "/#automated-tool-synapse_auto_compressor) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 823f71180..b28d1a365 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: 2024-12-16 12:05+0900\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" @@ -33,20 +33,35 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you. In short, it lets you fight invite-spam by " -"automatically blocking invitiations from a list of servers specified by " -"you (blacklisting)." +"It lets you fight invite-spam by automatically blocking invitiations from" +" a list of servers specified by you (blacklisting)." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 -msgid "Adjusting the playbook configuration" +msgid "" +"See the project's [documentation](https://github.com/t2bot/synapse-" +"simple-antispam/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you. In short," +#~ " it lets you fight invite-spam " +#~ "by automatically blocking invitiations from" +#~ " a list of servers specified by " +#~ "you (blacklisting)." +#~ msgstr "" + diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index 20c5ed834..7b5148329 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -238,71 +238,71 @@ msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:90 msgid "" -"After these variables have been set, run the playbook with [playbook tags" -"](playbook-tags.md) as below to restart UVS:" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:96 +#: ../../../docs/configuring-playbook-user-verification-service.md:97 msgid "" "The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-matrix-user-verification-service,start` " -"or `just setup-all`" +"available: `just install-service matrix-user-verification-service` or " +"`just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:98 +#: ../../../docs/configuring-playbook-user-verification-service.md:99 msgid "" -"`just run-tags setup-matrix-user-verification-service,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." +"`just install-service matrix-user-verification-service` is useful for " +"maintaining your setup quickly when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"`just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:100 +#: ../../../docs/configuring-playbook-user-verification-service.md:101 msgid "Logging" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:102 +#: ../../../docs/configuring-playbook-user-verification-service.md:103 msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:103 +#: ../../../docs/configuring-playbook-user-verification-service.md:104 msgid "warning" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:104 +#: ../../../docs/configuring-playbook-user-verification-service.md:105 msgid "info" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:105 +#: ../../../docs/configuring-playbook-user-verification-service.md:106 msgid "debug" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:107 +#: ../../../docs/configuring-playbook-user-verification-service.md:108 msgid "TLS Certificate Checking" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:109 +#: ../../../docs/configuring-playbook-user-verification-service.md:110 msgid "" "If the Matrix Homeserver does not provide a valid TLS certificate, UVS " "will fail with the following error message:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:111 +#: ../../../docs/configuring-playbook-user-verification-service.md:112 msgid "message: 'No response received: [object Object]'," msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:113 +#: ../../../docs/configuring-playbook-user-verification-service.md:114 msgid "This also applies to self-signed and let's encrypt staging certificates." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:115 +#: ../../../docs/configuring-playbook-user-verification-service.md:116 msgid "" "To disable certificate validation altogether (INSECURE! Not suitable for " "production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:117 +#: ../../../docs/configuring-playbook-user-verification-service.md:118 msgid "" "Alternatively, it is possible to inject your own CA certificates into the" " container by mounting a PEM file with additional trusted CAs into the " @@ -310,3 +310,31 @@ msgid "" "it." msgstr "" +#~ msgid "" +#~ "After these variables have been set, " +#~ "run the playbook with [playbook tags" +#~ "](playbook-tags.md) as below to restart " +#~ "UVS:" +#~ msgstr "" + +#~ msgid "" +#~ "The shortcut commands with the [`just`" +#~ " program](just.md) are also available: " +#~ "`just run-tags setup-matrix-user-" +#~ "verification-service,start` or `just setup-" +#~ "all`" +#~ msgstr "" + +#~ msgid "" +#~ "`just run-tags setup-matrix-user-" +#~ "verification-service,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 "" + diff --git a/i18n/locales/jp/LC_MESSAGES/README.po b/i18n/locales/jp/LC_MESSAGES/README.po index b40cd4e22..41e9558db 100644 --- a/i18n/locales/jp/LC_MESSAGES/README.po +++ b/i18n/locales/jp/LC_MESSAGES/README.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -53,7 +53,10 @@ msgid "" "This [Ansible](https://www.ansible.com/) playbook is meant to help you " "run your own [Matrix](http://matrix.org/) homeserver, along with the " "[various services](#supported-services) related to that." -msgstr "この [Ansible](https://www.ansible.com/) Playbook は、独自の [Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-services) を実行するのに役立つことを目的としています。" +msgstr "" +"この [Ansible](https://www.ansible.com/) Playbook は、独自の " +"[Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-" +"services) を実行するのに役立つことを目的としています。" #: ../../../README.md:9 msgid "" @@ -1349,11 +1352,25 @@ msgid "" "deploy/issues)" msgstr "" -#: ../../../README.md:215 +#: ../../../README.md:201 +msgid "🌐 Translation" +msgstr "" + +#: ../../../README.md:203 +msgid "" +"See the [i18n/README.md](i18n/README.md) file for more information about " +"translation." +msgstr "" + +#: ../../../README.md:205 +msgid "Translations are still work in progress." +msgstr "" + +#: ../../../README.md:207 msgid "🤝 Related" msgstr "" -#: ../../../README.md:217 +#: ../../../README.md:209 msgid "" "You may also be interested in [mash-playbook](https://github.com/mother-" "of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" @@ -1362,7 +1379,7 @@ msgid "" "playbook/blob/main/docs/supported-services.md))." msgstr "" -#: ../../../README.md:219 +#: ../../../README.md:211 msgid "" "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" "traefik.md) as its reverse-proxy, so with minor [interoperability " @@ -1371,3 +1388,4 @@ msgid "" "ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " "services on the same server." msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index eb7387679..ef770ef02 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: 2024-12-16 12:05+0900\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" @@ -40,19 +40,12 @@ msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 msgid "" "See the project's [documentation](https://github.com/metio/matrix-" -"alertmanager-receiver) to learn more about what this component does and " -"why it might be useful to you." +"alertmanager-receiver/blob/main/README.md) to learn what it does and why " +"it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 msgid "" -"At the moment, **setting up this service's bot requires some manual " -"actions** as described below in [Account and room preparation](#account-" -"and-room-preparation)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 -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 & " @@ -61,27 +54,93 @@ msgid "" "it." msgstr "" +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 +msgid "Prerequisites" +msgstr "" + #: ../../../docs/configuring-playbook-alertmanager-receiver.md:11 -msgid "Adjusting the playbook configuration" +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 msgid "" -"To enable matrix-alertmanager-receiver, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +"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:36 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 +msgid "" +"Choose a strong password for the bot. You can generate a good password " +"with a command like this: `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 +msgid "Get an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 +msgid "" +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 +msgid "Join to rooms as the bot manually" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 +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:33 +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:35 +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:37 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 +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](#get-an-access-" +"token)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 msgid "" "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " "additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:38 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:40 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 msgid "" "By default, this playbook installs matrix-alertmanager-receiver on the " "`matrix.` subdomain, at the `/matrix-alertmanager-receiver` path " @@ -90,7 +149,7 @@ msgid "" "to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:42 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 msgid "" "By tweaking the `matrix_alertmanager_receiver_hostname` and " "`matrix_alertmanager_receiver_path_prefix` variables, you can easily make" @@ -98,125 +157,61 @@ msgid "" "default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:44 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 msgid "" "Example additional configuration for your " "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:52 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:54 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 msgid "" "If you've changed the default hostname, **you may need to adjust your " "DNS** records to point the matrix-alertmanager-receiver domain to the " "Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:56 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:58 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 msgid "" "If you've decided to use the default hostname, you won't need to do any " "extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 -msgid "Account and room preparation" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 -msgid "" -"The playbook can automatically create users, but it cannot automatically " -"obtain access tokens, nor perform any of the other manual actions below." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 -msgid "" -"`matrix-alertmanager-receiver` uses a bot (with a username specified in " -"`matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see " -"above) for delivering messages. You need to **manually register this bot " -"acccount and obtain an access token for it**." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 -msgid "" -"[Register a new user](registering-users.md): `ansible-playbook -i " -"inventory/hosts setup.yml --extra-" -"vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT " -"admin=no' --tags=register-user`" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 -msgid "" -"[Obtain an access token](obtaining-access-tokens.md) for the bot's user " -"account" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 -msgid "Invite the bot to a room where you'd like to alerts to be delivered" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 -msgid "" -"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:70 -msgid "" -"(Optionally) Adjust " -"`matrix_alertmanager_receiver_config_matrix_room_mapping` to create a " -"mapping between the new room and its ID" -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:72 -msgid "" -"Steps 1 and 2 above only need to be done once, while preparing your " -"[configuration](#adjusting-the-playbook-configuration)." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:74 -msgid "" -"Steps 3 and 4 need to be done for each new room you'd like the bot to " -"deliver alerts to. Step 5 is optional and provides cleaner `/alert/` " -"URLs." -msgstr "" - -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 msgid "" -"Now that you've [prepared the bot account and room](#account-and-room-" -"preparation), [configured the playbook](#adjusting-the-playbook-" -"configuration), and potentially [adjusted your DNS records](#adjusting-" -"dns-records), you can run the playbook with [playbook tags](playbook-" -"tags.md) as below:" +"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:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 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:89 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:98 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:91 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -225,27 +220,136 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:114 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 msgid "" -".. where `URL_HERE` looks like `https://matrix.example.com/matrix-" +"where `URL_HERE` looks like `https://matrix.example.com/matrix-" "alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or " "`https://matrix.example.com/matrix-alertmanager-receiver-" "RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:116 -msgid "" -"This bot does **not** accept room invitations automatically (like many " -"other bots do). To deliver messages to rooms, **the bot must be joined to" -" all rooms manually** - see Step 4 of the [Account and room preparation" -"](#account-and-room-preparation) section." -msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/metio/matrix-alertmanager-" +#~ "receiver) to learn more about what " +#~ "this component does and why it " +#~ "might be useful to you." +#~ msgstr "" + +#~ msgid "" +#~ "At the moment, **setting up this " +#~ "service's bot requires some manual " +#~ "actions** as described below in [Account" +#~ " and room preparation](#account-and-" +#~ "room-preparation)." +#~ msgstr "" + +#~ msgid "" +#~ "To enable matrix-alertmanager-receiver, " +#~ "add the following configuration to your" +#~ " `inventory/host_vars/matrix.example.com/vars.yml` file:" +#~ msgstr "" + +#~ msgid "Account and room preparation" +#~ msgstr "" + +#~ msgid "" +#~ "The playbook can automatically create " +#~ "users, but it cannot automatically " +#~ "obtain access tokens, nor perform any" +#~ " of the other manual actions below." +#~ msgstr "" + +#~ msgid "" +#~ "`matrix-alertmanager-receiver` uses a " +#~ "bot (with a username specified in " +#~ "`matrix_alertmanager_receiver_config_matrix_user_id_localpart` -" +#~ " see above) for delivering messages. " +#~ "You need to **manually register this " +#~ "bot acccount and obtain an access " +#~ "token for it**." +#~ msgstr "" + +#~ msgid "" +#~ "[Register a new user](registering-users.md):" +#~ " `ansible-playbook -i inventory/hosts " +#~ "setup.yml --extra-vars='username=bot.alertmanager.receiver" +#~ " password=PASSWORD_FOR_THE_BOT admin=no' --tags" +#~ "=register-user`" +#~ msgstr "" + +#~ msgid "" +#~ "[Obtain an access token](obtaining-access-" +#~ "tokens.md) for the bot's user account" +#~ msgstr "" + +#~ msgid "Invite the bot to a room where you'd like to alerts to be delivered" +#~ msgstr "" + +#~ msgid "" +#~ "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 "" + +#~ msgid "" +#~ "(Optionally) Adjust " +#~ "`matrix_alertmanager_receiver_config_matrix_room_mapping` to " +#~ "create a mapping between the new " +#~ "room and its ID" +#~ msgstr "" + +#~ msgid "" +#~ "Steps 1 and 2 above only need " +#~ "to be done once, while preparing " +#~ "your [configuration](#adjusting-the-playbook-" +#~ "configuration)." +#~ msgstr "" + +#~ msgid "" +#~ "Steps 3 and 4 need to be " +#~ "done for each new room you'd like" +#~ " the bot to deliver alerts to. " +#~ "Step 5 is optional and provides " +#~ "cleaner `/alert/` URLs." +#~ msgstr "" + +#~ msgid "" +#~ "Now that you've [prepared the bot " +#~ "account and room](#account-and-room-" +#~ "preparation), [configured the playbook" +#~ "](#adjusting-the-playbook-configuration), and " +#~ "potentially [adjusted your DNS records" +#~ "](#adjusting-dns-records), you can run " +#~ "the playbook with [playbook tags](playbook-" +#~ "tags.md) as below:" +#~ msgstr "" + +#~ 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 "" + +#~ msgid "" +#~ "This bot does **not** accept room " +#~ "invitations automatically (like many other " +#~ "bots do). To deliver messages to " +#~ "rooms, **the bot must be joined to" +#~ " all rooms manually** - see Step " +#~ "4 of the [Account and room " +#~ "preparation](#account-and-room-preparation) " +#~ "section." +#~ 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 88f283561..fc4f586b9 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: 2024-12-16 12:05+0900\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" @@ -83,27 +83,31 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 -msgid "Installation" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21 -msgid "Create a main management room." +msgid "Create a main management room" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 msgid "" "The playbook does not create a management room for your Main Draupnir. " -"This task you have to do on your own." +"You **need to create the room manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 +msgid "Note that the room must be unencrypted." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 msgid "" "The management room has to be given an alias and be public when you are " "setting up the bot for the first time as the bot does not differentiate " "between invites and invites to the management room." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 msgid "" "This management room is used to control who has access to your D4A " "deployment. The room stores this data inside of the control room state so" @@ -111,77 +115,107 @@ msgid "" "This is default 50 or moderator as Element clients call this powerlevel." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33 msgid "" "As noted in the Draupnir install instructions the control room is " -"sensitive. The following is said about the control room in the Draupnir " -"install instructions." +"sensitive. **Anyone in this room can control the bot so it is important " +"that you only invite trusted users to this room.**" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35 +msgid "Set an alias to the management room" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37 +msgid "Next, set an alias to the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39 msgid "" -"Anyone in this room can control the bot so it is important that you only " -"invite trusted users to this room. The room must be unencrypted since the" -" playbook does not support installing Pantalaimon yet." +"This alias can be anything you want. However, for increased security " +"during the setup phase, it is recommended to make this alias be a random " +"string. When it has been locked down after setup phase, you can give your" +" room a secondary human readable alias." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32 -msgid "Give your main management room an alias." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34 -msgid "" -"Give the room from step 1 an alias. This alias can be anything you want " -"and its recommended for increased security during the setup phase of the " -"bot that you make this alias be a random string. You can give your room a" -" secondary human readable alias when it has been locked down after setup " -"phase." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36 -msgid "Adjusting the playbook configuration." -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 msgid "" "Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +"`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:40 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 msgid "" -"You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created" -" in step 2." +"You can configure additional options by adding the " +"`matrix_appservice_draupnir_for_all_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:48 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55 +msgid "" +"For example, to change Draupnir's `protectAllJoinedRooms` option to " +"`true`, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 +msgid "" +"You can refer to the upstream [documentation](https://github.com/the-" +"draupnir-project/Draupnir) for more configuration documentation." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +msgid "" +"The playbook ships a full copy of the example config that does transfer " +"to provisioned Draupnirs in the production-bots.yaml.j2 file in the " +"template directory of the role." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 +msgid "" +"Config extension does not affect the appservices config as this config is" +" not extensible in current Draupnir anyway. It instead touches the config" +" passed to the Draupnirs that your Appservice creates. So the example " +"above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs " +"protect all joined rooms." +msgstr "" + +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:50 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:61 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:63 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -190,29 +224,29 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:65 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 msgid "" "If you made it through all the steps above and your main control room was" " joined by a user called `@draupnir-main:example.com` you have " "succesfully installed Draupnir for All and can now start using it." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98 msgid "" "The installation of Draupnir for all in this playbook is very much Alpha " -"quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot " -"mode." +"quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot" +" mode." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 msgid "Granting Users the ability to use D4A" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 msgid "" "Draupnir for all includes several security measures like that it only " "allows users that are on its allow list to ask for a bot. To add a user " @@ -223,7 +257,7 @@ msgid "" " the chat is recomended." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 msgid "" "The bot requires a powerlevel of 50 in the management room to control who" " is allowed to use the bot. The bot does currently not say anything if " @@ -232,7 +266,7 @@ msgid "" "project/Draupnir/issues/297))" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 msgid "" "To allow users or whole homeservers you type /plain @draupnir-" "main:example.com allow `target` and target can be either a MXID or a " @@ -241,57 +275,146 @@ msgid "" "this command as it can break Wildcard commands especially." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 -msgid "How to provision a D4A once you are allowed to." +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 +msgid "How to provision a D4A once you are allowed to" msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 msgid "" -"Open a DM with @draupnir-main:example.com and if using an Element client " -"send a message into this DM to finalise creating it. The bot will reject " -"this invite and you will shortly get invited to the Draupnir control room" -" for your newly provisioned Draupnir. From here its just a normal " -"Draupnir experience." +"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:83 +#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 msgid "" "Congratulations if you made it all the way here because you now have a " "fully working Draupnir for all deployment." msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85 -msgid "Configuration of D4A" -msgstr "" +#~ msgid "Installation" +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87 -msgid "" -"You can refer to the upstream [documentation](https://github.com/the-" -"draupnir-project/Draupnir) for more configuration documentation. Please " -"note that the playbook ships a full copy of the example config that does " -"transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in " -"the template directory of the role." -msgstr "" +#~ msgid "Create a main management room." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89 -msgid "" -"Please note that Config extension does not affect the appservices config " -"as this config is not extensible in current Draupnir anyways. Config " -"extension instead touches the config passed to the Draupnirs that your " -"Appservice creates. So for example below makes all provisioned Draupnirs " -"protect all joined rooms." -msgstr "" +#~ msgid "" +#~ "The playbook does not create a " +#~ "management room for your Main Draupnir." +#~ " This task you have to do on" +#~ " your own." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91 -msgid "" -"You can configure additional options by adding the " -"`matrix_appservice_draupnir_for_all_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "" +#~ "As noted in the Draupnir install " +#~ "instructions the control room is " +#~ "sensitive. The following is said about" +#~ " the control room in the Draupnir " +#~ "install instructions." +#~ msgstr "" -#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:93 -msgid "" -"For example to change Draupnir's `protectAllJoinedRooms` option to `true`" -" you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "Anyone in this room can control " +#~ "the bot so it is important that" +#~ " you only invite trusted users to " +#~ "this room. The room must be " +#~ "unencrypted since the playbook does not" +#~ " support installing Pantalaimon yet." +#~ msgstr "" + +#~ msgid "Give your main management room an alias." +#~ msgstr "" + +#~ msgid "" +#~ "Give the room from step 1 an " +#~ "alias. This alias can be anything " +#~ "you want and its recommended for " +#~ "increased security during the setup " +#~ "phase of the bot that you make " +#~ "this alias be a random string. You" +#~ " can give your room a secondary " +#~ "human readable alias when it has " +#~ "been locked down after setup phase." +#~ msgstr "" + +#~ msgid "Adjusting the playbook configuration." +#~ msgstr "" + +#~ msgid "" +#~ "Add the following configuration to your" +#~ " `inventory/host_vars/matrix.example.com/vars.yml` file " +#~ "(adapt to your needs):" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` " +#~ "with the alias you created in step" +#~ " 2." +#~ msgstr "" + +#~ msgid "" +#~ "The installation of Draupnir for all " +#~ "in this playbook is very much " +#~ "Alpha quality. Usage-wise, Draupnir for" +#~ " allis almost identical to Draupnir " +#~ "bot mode." +#~ msgstr "" + +#~ msgid "How to provision a D4A once you are allowed to." +#~ msgstr "" + +#~ msgid "" +#~ "Open a DM with @draupnir-" +#~ "main:example.com and if using an Element" +#~ " client send a message into this " +#~ "DM to finalise creating it. The " +#~ "bot will reject this invite and " +#~ "you will shortly get invited to " +#~ "the Draupnir control room for your " +#~ "newly provisioned Draupnir. From here " +#~ "its just a normal Draupnir experience." +#~ msgstr "" + +#~ msgid "Configuration of D4A" +#~ msgstr "" + +#~ msgid "" +#~ "You can refer to the upstream " +#~ "[documentation](https://github.com/the-draupnir-" +#~ "project/Draupnir) for more configuration " +#~ "documentation. Please note that the " +#~ "playbook ships a full copy of the" +#~ " example config that does transfer to" +#~ " provisioned Draupnirs in the " +#~ "production-bots.yaml.j2 file in the " +#~ "template directory of the role." +#~ msgstr "" + +#~ msgid "" +#~ "Please note that Config extension does" +#~ " not affect the appservices config as" +#~ " this config is not extensible in " +#~ "current Draupnir anyways. Config extension " +#~ "instead touches the config passed to " +#~ "the Draupnirs that your Appservice " +#~ "creates. So for example below makes " +#~ "all provisioned Draupnirs protect all " +#~ "joined rooms." +#~ msgstr "" + +#~ msgid "" +#~ "You can configure additional options by" +#~ " adding the " +#~ "`matrix_appservice_draupnir_for_all_extension_yaml` variable " +#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" +#~ " file." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Draupnir's " +#~ "`protectAllJoinedRooms` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index b1c589d9f..0e3677f70 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -33,8 +33,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:5 msgid "" "See the project's [documentation](https://github.com/the-draupnir-" -"project/Draupnir) to learn what it does and why it might be useful to " -"you." +"project/Draupnir/blob/main/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:7 @@ -46,21 +46,23 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:9 -msgid "If your migrating from Mjolnir skip to step 5b." +msgid "" +"If your migrating from Mjolnir skip to [this section](#migrating-from-" +"mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:11 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:13 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 @@ -76,7 +78,7 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 msgid "" "If you would like Draupnir to be able to deactivate users, move aliases, " -"shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc " +"shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc " "then it must be a server admin so you need to change `admin=no` to " "`admin=yes` in the command above." msgstr "" @@ -87,8 +89,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 @@ -97,43 +100,65 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 msgid "" -"You will need to prevent Synapse from rate limiting the bot's account. " -"This is not an optional step. If you do not do this step Draupnir will " -"crash. This can be done using Synapse's [admin API](https://matrix-" -"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). Please ask for help if you are uncomfortable " -"with these steps or run into issues." +"If your homeserver's implementation is Synapse, you will need to prevent " +"it from rate limiting the bot's account. **This is a required step. If " +"you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 msgid "" -"If your Synapse Admin API is exposed to the internet for some reason like" -" running the Synapse Admin Role [Link](configuring-playbook-synapse-" -"admin.md) or running " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true` in your playbook config. If your API is not externally exposed you" -" should still be able to on the local host for your synapse run these " -"commands." +"This can be done using Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). They can be accessed both externally and " +"internally." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 msgid "" -"The following command works on semi up to date Windows 10 installs and " -"All Windows 11 installations and other systems that ship curl. `curl " -"--header \"Authorization: Bearer \" -X POST " -"https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" -" Replace `@bot.draupnir:example.com` with the MXID of your Draupnir and " -"example.com with your homeserver domain. You can easily obtain an access " -"token for a homeserver admin account the same way you can obtain an " -"access token for Draupnir itself. If you made Draupnir Admin you can just" -" use the Draupnir token." +"To expose the APIs publicly, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:39 +#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +msgid "" +"The APIs can also be accessed via [Synapse " +"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " +"use to administrate users, rooms, media, etc. on your Matrix server. The " +"playbook can install and configure Synapse Admin for you. For details " +"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +msgid "" +"**Note**: access to the APIs is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, " +"doing so is not recommended for additional security. See [official " +"Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +msgid "" +"To discharge rate limiting, run the following command on systems that " +"ship curl (note that it does not work on outdated Windows 10). Even if " +"the APIs are not exposed to the internet, you should still be able to run" +" the command on the homeserver locally. Before running it, make sure to " +"replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +msgid "" +"You can obtain an access token for a homeserver admin account in the same" +" way as you can do so for Draupnir itself. If you have made Draupnir an " +"admin, you can just use the Draupnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:41 +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 msgid "" "Using your own account, create a new invite only room that you will use " "to manage the bot. This is the room where you will see the status of the " @@ -142,13 +167,13 @@ msgid "" "it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 msgid "" "If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see below)." +"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 msgid "" "Once you have created the room you need to copy the room ID so you can " "tell the bot to use that room. In Element Web you can do this by going to" @@ -156,43 +181,58 @@ msgid "" "room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 msgid "" "Finally invite the `@bot.draupnir:example.com` account you created " "earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:49 +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:51 +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `MANAGEMENT_ROOM_ID_HERE`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:78 msgid "" "Decide whether you want Draupnir to be capable of operating in end-to-end" " encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon" -"](configuring-playbook-pantalaimon.md)." +"moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:53 -msgid "a. Configuration with E2EE support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:80 +msgid "" +"To support E2EE, Draupnir needs to [use Pantalaimon](configuring-" +"playbook-pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +#: ../../../docs/configuring-playbook-bot-draupnir.md:82 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:84 msgid "" "When using Pantalaimon, Draupnir will log in to its bot account itself " "through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:57 -#: ../../../docs/configuring-playbook-bot-draupnir.md:92 +#: ../../../docs/configuring-playbook-bot-draupnir.md:86 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +#: ../../../docs/configuring-playbook-bot-draupnir.md:100 msgid "" "The playbook's `group_vars` will configure other required settings. If " "using this role separately without the playbook, you also need to " @@ -201,65 +241,108 @@ msgid "" "playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:88 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:90 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "" "When NOT using Pantalaimon, Draupnir does not log in by itself and you " "must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:94 +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 msgid "" -"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +"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](#get-an-access-" +"token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:104 -msgid "c. Migrating from Mjolnir (Only required if migrating.)" +#: ../../../docs/configuring-playbook-bot-draupnir.md:122 +msgid "Abuse Reports" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:106 +#: ../../../docs/configuring-playbook-bot-draupnir.md:124 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:126 +msgid "" +"The first method intercepts the report API endpoint of the client-server " +"API, which requires integration with the reverse proxy in front of the " +"homeserver. If you are using traefik, this playbook can set this up for " +"you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +msgid "" +"The other method polls an Synapse Admin API endpoint, hence it is " +"available only if using Synapse and if the Draupnir user is an admin (see" +" [above](#register-the-bot-account)). To enable it, set `pollReports: " +"true` on `vars.yml` file as below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_draupnir_configuration_extension_yaml` variable." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +msgid "" +"For example, to change Draupnir's `pollReports` option to `true`, add the" +" following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +msgid "Migrating from Mjolnir (Only required if migrating)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "" "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " "config. Also disable Mjolnir if you're doing migration." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:108 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "" "That is all you need to do due to that Draupnir can complete migration on" " its own." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:110 +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:119 +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:121 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:123 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:125 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -268,7 +351,7 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:127 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "" "If you change the Pantalaimon's password " "(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " @@ -279,32 +362,32 @@ msgid "" " know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:129 +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:131 +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 msgid "" "You can refer to the upstream [documentation](https://the-draupnir-" "project.github.io/draupnir-documentation/) for additional ways to use and" " configure Draupnir and for a more detailed usage guide." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:133 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:135 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:137 +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 msgid "" "Draupnir can be told to self-join public rooms, but it's better to follow" " this flow which works well for all kinds of rooms:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:139 +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 msgid "" "Invite the bot to the room manually ([inviting Draupnir to rooms](https" "://the-draupnir-project.github.io/draupnir-documentation/moderator" @@ -312,13 +395,13 @@ msgid "" "the bot *may* ask for confirmation in the Management Room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:141 +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 msgid "" "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" "do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:143 +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 msgid "" "Tell it to protect the room (using the [rooms command](https://the-" "draupnir-project.github.io/draupnir-documentation/moderator/managing-" @@ -327,7 +410,7 @@ msgid "" "!qporfwt:example.com`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:145 +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 msgid "" "To have Draupnir provide useful room protection, you need do to a bit " "more work (at least the first time around). You may wish to [Subscribe to" @@ -336,11 +419,11 @@ msgid "" " and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:147 +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:149 +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 msgid "" "For Draupnir to do its job, you need to [give it permissions](https" "://the-draupnir-project.github.io/draupnir-documentation/moderator" @@ -348,7 +431,7 @@ msgid "" "protecting. This involves **giving it an Administrator power level**." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:151 +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 msgid "" "**We recommend setting this power level as soon as the bot joins your " "room** (and before you create new rules), so that it can apply rules as " @@ -357,11 +440,11 @@ msgid "" " it)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:153 +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:155 +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 msgid "" "We recommend **subscribing to a public [policy list](https://the-" "draupnir-project.github.io/draupnir-documentation/concepts/policy-" @@ -370,24 +453,24 @@ msgid "" "watch-command-to-subscribe-to-policy-rooms)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:157 +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 msgid "" "Polcy lists are maintained in Matrix rooms. A popular policy list is " "maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:159 +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 msgid "" "You can tell Draupnir to subscribe to it by sending the following command" " to the Management Room: `!draupnir watch #community-moderation-effort-" "bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:161 +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:163 +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 msgid "" "We also recommend **creating your own policy lists** with the [list " "create](https://the-draupnir-project.github.io/draupnir-" @@ -395,7 +478,7 @@ msgid "" "create-command-to-create-a-policy-room) command." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 msgid "" "You can do so by sending the following command to the Management Room: " "`!draupnir list create my-bans my-bans-bl`. This will create a policy " @@ -404,7 +487,7 @@ msgid "" "command, the bot will invite you to the policy list room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 msgid "" "A policy list does nothing by itself, so the next step is **adding some " "rules to your policy list**. Policies target a so-called `entity` (one " @@ -415,7 +498,7 @@ msgid "" "recommendation)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "" "The simplest and most useful entity to target is `user`. Below are a few " "examples using the [ban command](https://the-draupnir-project.github.io" @@ -423,19 +506,19 @@ msgid "" "targeting users." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "" "To create rules, you run commands in the Management Room (**not** in the " "policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "" "(ban a single user on a given homeserver): `!draupnir ban " "@charles:example.com my-bans Rude to others`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:174 +#: ../../../docs/configuring-playbook-bot-draupnir.md:222 msgid "" "(ban all users on a given homeserver by using a [wildcard](https://the-" "draupnir-project.github.io/draupnir-documentation/moderator/managing-" @@ -443,34 +526,34 @@ msgid "" "all users are fake`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:176 +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:178 +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 msgid "" "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" "bl:example.com` room on your server" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +#: ../../../docs/configuring-playbook-bot-draupnir.md:227 msgid "" "applying these rules against all rooms that Draupnir is an Administrator " "in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 msgid "" "You can undo bans with the [unban command](https://the-draupnir-" "project.github.io/draupnir-documentation/moderator/managing-users#the-" "unban-command)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 msgid "" "You can also **turn on various built-in [protections](https://the-" "draupnir-project.github.io/draupnir-documentation/protections)** like " @@ -478,75 +561,179 @@ msgid "" "room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 msgid "" "To **see which protections are available and which are enabled**, send a " "`!draupnir protections` command to the Management Room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 msgid "" "To **see the configuration options for a given protection**, send a " "`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " "JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "" "To **set a specific option for a given protection**, send a command like " "this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " "`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 msgid "" "To **enable a given protection**, send a command like this: `!draupnir " "enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "" "To **disable a given protection**, send a command like this: `!draupnir " "disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 -msgid "Extending the configuration" -msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/the-draupnir-project/Draupnir) to learn " +#~ "what it does and why it might " +#~ "be useful to you." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_draupnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "If your migrating from Mjolnir skip to step 5b." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 -msgid "" -"For example to change Draupnir's `recordIgnoredInvites` option to `true` " -"you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "The playbook does not automatically " +#~ "create users for you. The bot " +#~ "requires an access token to be " +#~ "able to connect to your homeserver." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 -msgid "Abuse Reports" -msgstr "" +#~ msgid "" +#~ "You **need to register the bot " +#~ "user manually** before setting up the" +#~ " bot." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 -msgid "Draupnir supports two methods to receive reports in the management room." -msgstr "" +#~ msgid "" +#~ "If you would like Draupnir to be" +#~ " able to deactivate users, move " +#~ "aliases, shutdown rooms, show abuse " +#~ "reports ([see below](#abuse-reports)), etc " +#~ "then it must be a server admin " +#~ "so you need to change `admin=no` " +#~ "to `admin=yes` in the command above." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 -msgid "" -"The first method intercepts the report API endpoint of the client-server " -"API, which requires integration with the reverse proxy in front of the " -"homeserver. If you are using traefik, this playbook can set this up for " -"you:" -msgstr "" +#~ msgid "" +#~ "Refer to the documentation on [how " +#~ "to obtain an access token](obtaining-" +#~ "access-tokens.md)." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:225 -msgid "" -"The other method polls an synapse admin API endpoint and is hence only " -"available when using synapse and when the Draupnir user is an admin user " -"(see step 1). To enable it, set `pollReports: true` in Draupnir's config:" -msgstr "" +#~ msgid "" +#~ "You will need to prevent Synapse " +#~ "from rate limiting the bot's account." +#~ " This is not an optional step. " +#~ "If you do not do this step " +#~ "Draupnir will crash. This can be " +#~ "done using Synapse's [admin API](https" +#~ "://matrix-" +#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" +#~ "#override-ratelimiting-for-users). Please " +#~ "ask for help if you are " +#~ "uncomfortable with these steps or run" +#~ " into issues." +#~ msgstr "" + +#~ msgid "" +#~ "If your Synapse Admin API is " +#~ "exposed to the internet for some " +#~ "reason like running the Synapse Admin" +#~ " Role [Link](configuring-playbook-synapse-" +#~ "admin.md) or running " +#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +#~ " true` in your playbook config. If" +#~ " your API is not externally exposed" +#~ " you should still be able to on" +#~ " the local host for your synapse " +#~ "run these commands." +#~ msgstr "" + +#~ msgid "" +#~ "The following command works on semi " +#~ "up to date Windows 10 installs and" +#~ " All Windows 11 installations and " +#~ "other systems that ship curl. `curl " +#~ "--header \"Authorization: Bearer \"" +#~ " -X POST " +#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" +#~ " Replace `@bot.draupnir:example.com` with the " +#~ "MXID of your Draupnir and example.com" +#~ " with your homeserver domain. You can" +#~ " easily obtain an access token for" +#~ " a homeserver admin account the same" +#~ " way you can obtain an access " +#~ "token for Draupnir itself. If you " +#~ "made Draupnir Admin you can just " +#~ "use the Draupnir token." +#~ msgstr "" + +#~ msgid "" +#~ "If you make the management room " +#~ "encrypted (E2EE), then you MUST enable" +#~ " and use Pantalaimon (see below)." +#~ msgstr "" + +#~ msgid "" +#~ "Decide whether you want Draupnir to " +#~ "be capable of operating in end-" +#~ "to-end encrypted (E2EE) rooms. This " +#~ "includes the management room and the " +#~ "moderated rooms. To support E2EE, " +#~ "Draupnir needs to [use Pantalaimon" +#~ "](configuring-playbook-pantalaimon.md)." +#~ msgstr "" + +#~ msgid "a. Configuration with E2EE support" +#~ msgstr "" + +#~ msgid "b. Configuration without E2EE support" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace " +#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " +#~ "values." +#~ msgstr "" + +#~ msgid "c. Migrating from Mjolnir (Only required if migrating.)" +#~ msgstr "" + +#~ msgid "" +#~ "You can configure additional options by" +#~ " adding the " +#~ "`matrix_bot_draupnir_configuration_extension_yaml` variable " +#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" +#~ " file." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Draupnir's " +#~ "`recordIgnoredInvites` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ msgstr "" + +#~ msgid "" +#~ "The other method polls an synapse " +#~ "admin API endpoint and is hence " +#~ "only available when using synapse and" +#~ " when the Draupnir user is an " +#~ "admin user (see step 1). To enable" +#~ " it, set `pollReports: true` in " +#~ "Draupnir's config:" +#~ 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 ea89191dd..8dbd4665d 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: 2024-12-16 12:05+0900\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" @@ -49,8 +49,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:9 msgid "" -"See the project's [documentation](https://github.com/matrix-org/go-neb) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-org/go-" +"neb/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 @@ -207,3 +208,10 @@ msgid "" "/matrix-org/go-neb)." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/go-neb) to learn what it" +#~ " does and why it might be " +#~ "useful to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index a0e5ceba7..e551070dc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -36,9 +36,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:7 msgid "" -"See the project's [documentation](https://github.com/etkecc/honoroit#how-" -"it-looks-like) to learn what it does with screenshots and why it might be" -" useful to you." +"See the project's " +"[documentation](https://github.com/etkecc/honoroit/blob/main/README.md) " +"to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:9 @@ -166,3 +166,11 @@ msgid "" "[documentation](https://github.com/etkecc/honoroit#features)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/etkecc/honoroit#how-it-" +#~ "looks-like) to learn what it does " +#~ "with screenshots and why it might " +#~ "be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index cc7e35bd2..fb61172cc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -43,7 +43,7 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 msgid "" "See the project's [documentation](https://github.com/moan0s/matrix-" -"registration-bot#supported-commands) to learn what it does and why it " +"registration-bot/blob/master/README.md) to learn what it does and why it " "might be useful to you." msgstr "" @@ -145,3 +145,11 @@ msgid "" "etc… you can use:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/moan0s/matrix-" +#~ "registration-bot#supported-commands) to learn " +#~ "what it does and why it might " +#~ "be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index 6c3e1858a..5148da31a 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -39,8 +39,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 msgid "" "See the project's [documentation](https://github.com/anoadragon453" -"/matrix-reminder-bot#usage) to learn what it does and why it might be " -"useful to you." +"/matrix-reminder-bot/blob/master/README.md) to learn what it does and why" +" it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 @@ -133,3 +133,11 @@ msgid "" "bot#usage)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/anoadragon453/matrix-" +#~ "reminder-bot#usage) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index 7a323cbe2..cbadc9714 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -32,22 +32,23 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:5 msgid "" -"See the project's [documentation](https://github.com/matrix-org/mjolnir) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-" +"org/mjolnir/blob/main/README.md) to learn what it does and why it might " +"be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:7 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:9 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:11 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "" +"The playbook does not automatically create users for you. You **need to " +"register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 @@ -73,8 +74,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +"The bot requires an access token to be able to connect to your " +"homeserver. Refer to the documentation on [how to obtain an access token" +"](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 @@ -83,43 +85,65 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 msgid "" -"You will need to prevent Synapse from rate limiting the bot's account. " -"This is not an optional step. If you do not do this step Mjolnir will " -"crash. This can be done using Synapse's [admin API](https://matrix-" -"org.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). Please ask for help if you are uncomfortable " -"with these steps or run into issues." +"If your homeserver's implementation is Synapse, you will need to prevent " +"it from rate limiting the bot's account. **This is a required step. If " +"you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 msgid "" -"If your Synapse Admin API is exposed to the internet for some reason like" -" running the Synapse Admin Role [Link](configuring-playbook-synapse-" -"admin.md) or running " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true` in your playbook config. If your API is not externally exposed you" -" should still be able to on the local host for your synapse run these " -"commands." +"This can be done using Synapse's [Admin APIs](https://element-" +"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" +"ratelimiting-for-users). They can be accessed both externally and " +"internally." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 msgid "" -"The following command works on semi up to date Windows 10 installs and " -"All Windows 11 installations and other systems that ship curl. `curl " -"--header \"Authorization: Bearer \" -X POST " -"https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" -" Replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir and " -"example.com with your homeserver domain. You can easily obtain an access " -"token for a homeserver admin account the same way you can obtain an " -"access token for Mjolnir itself. If you made Mjolnir Admin you can just " -"use the Mjolnir token." +"To expose the APIs publicly, add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +msgid "" +"The APIs can also be accessed via [Synapse " +"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " +"use to administrate users, rooms, media, etc. on your Matrix server. The " +"playbook can install and configure Synapse Admin for you. For details " +"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +msgid "" +"**Note**: access to the APIs is restricted with a valid access token, so " +"exposing them publicly should not be a real security concern. Still, " +"doing so is not recommended for additional security. See [official " +"Synapse reverse-proxying recommendations](https://element-" +"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" +"endpoints)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +msgid "" +"To discharge rate limiting, run the following command on systems that " +"ship curl (note that it does not work on outdated Windows 10). Even if " +"the APIs are not exposed to the internet, you should still be able to run" +" the command on the homeserver locally. Before running it, make sure to " +"replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +msgid "" +"You can obtain an access token for a homeserver admin account in the same" +" way as you can do so for Mjolnir itself. If you have made Mjolnir an " +"admin, you can just use the Mjolnir token." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:37 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "" "Using your own account, create a new invite only room that you will use " "to manage the bot. This is the room where you will see the status of the " @@ -128,13 +152,13 @@ msgid "" "it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 msgid "" "If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see below)." +"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 msgid "" "Once you have created the room you need to copy the room ID so you can " "tell the bot to use that room. In Element Web you can do this by going to" @@ -142,44 +166,58 @@ msgid "" "room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 msgid "" "Finally invite the `@bot.mjolnir:example.com` account you created earlier" " into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 +msgid "" +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `MANAGEMENT_ROOM_ID_HERE`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 msgid "" "Decide whether you want Mjolnir to be capable of operating in end-to-end " "encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon" -"](configuring-playbook-pantalaimon.md)." +"moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 -msgid "a. Configuration with E2EE support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:76 +msgid "" +"To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-" +"pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 +msgid "Configuration with E2EE support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 msgid "" "When using Pantalaimon, Mjolnir will log in to its bot account itself " "through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:88 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:102 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 msgid "" "The playbook's `group_vars` will configure other required settings. If " "using this role separately without the playbook, you also need to " @@ -188,53 +226,80 @@ msgid "" "playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 -msgid "b. Configuration without E2EE support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "" "When NOT using Pantalaimon, Mjolnir does not log in by itself and you " "must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:90 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "" -"You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -"`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own values." +"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](#get-an-access-" +"token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:100 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +msgid "" +"To enable Mjolnir synapse antispam module, add the following " +"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " +"file (adapt to your needs):" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 +msgid "" +"You can configure additional options by adding the " +"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +msgid "" +"For example, to change Mjolnir's `recordIgnoredInvites` option to `true`," +" add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:121 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:123 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:125 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:127 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -243,7 +308,7 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:129 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 msgid "" "If you change the Pantalaimon's password " "(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " @@ -254,11 +319,11 @@ msgid "" "know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:131 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:133 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 msgid "" "You can refer to the upstream [documentation](https://github.com/matrix-" "org/mjolnir) for additional ways to use and configure Mjolnir. Check out " @@ -266,16 +331,113 @@ msgid "" "#quickstart-guide) for some basic commands you can give to the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:135 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." -msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/mjolnir) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:137 -msgid "" -"For example to change Mjolnir's `recordIgnoredInvites` option to `true` " -"you would add the following to your `vars.yml` file." -msgstr "" +#~ msgid "" +#~ "The playbook does not automatically " +#~ "create users for you. The bot " +#~ "requires an access token to be " +#~ "able to connect to your homeserver." +#~ msgstr "" + +#~ msgid "" +#~ "You **need to register the bot " +#~ "user manually** before setting up the" +#~ " bot." +#~ msgstr "" + +#~ msgid "" +#~ "Refer to the documentation on [how " +#~ "to obtain an access token](obtaining-" +#~ "access-tokens.md)." +#~ msgstr "" + +#~ msgid "" +#~ "You will need to prevent Synapse " +#~ "from rate limiting the bot's account." +#~ " This is not an optional step. " +#~ "If you do not do this step " +#~ "Mjolnir will crash. This can be " +#~ "done using Synapse's [admin API](https" +#~ "://matrix-" +#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" +#~ "#override-ratelimiting-for-users). Please " +#~ "ask for help if you are " +#~ "uncomfortable with these steps or run" +#~ " into issues." +#~ msgstr "" + +#~ msgid "" +#~ "If your Synapse Admin API is " +#~ "exposed to the internet for some " +#~ "reason like running the Synapse Admin" +#~ " Role [Link](configuring-playbook-synapse-" +#~ "admin.md) or running " +#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" +#~ " true` in your playbook config. If" +#~ " your API is not externally exposed" +#~ " you should still be able to on" +#~ " the local host for your synapse " +#~ "run these commands." +#~ msgstr "" + +#~ msgid "" +#~ "The following command works on semi " +#~ "up to date Windows 10 installs and" +#~ " All Windows 11 installations and " +#~ "other systems that ship curl. `curl " +#~ "--header \"Authorization: Bearer \"" +#~ " -X POST " +#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" +#~ " Replace `@bot.mjolnir:example.com` with the " +#~ "MXID of your Mjolnir and example.com " +#~ "with your homeserver domain. You can " +#~ "easily obtain an access token for " +#~ "a homeserver admin account the same " +#~ "way you can obtain an access token" +#~ " for Mjolnir itself. If you made " +#~ "Mjolnir Admin you can just use the" +#~ " Mjolnir token." +#~ msgstr "" + +#~ msgid "" +#~ "If you make the management room " +#~ "encrypted (E2EE), then you MUST enable" +#~ " and use Pantalaimon (see below)." +#~ msgstr "" + +#~ msgid "" +#~ "Decide whether you want Mjolnir to " +#~ "be capable of operating in end-" +#~ "to-end encrypted (E2EE) rooms. This " +#~ "includes the management room and the " +#~ "moderated rooms. To support E2EE, " +#~ "Mjolnir needs to [use Pantalaimon" +#~ "](configuring-playbook-pantalaimon.md)." +#~ msgstr "" + +#~ msgid "a. Configuration with E2EE support" +#~ msgstr "" + +#~ msgid "b. Configuration without E2EE support" +#~ msgstr "" + +#~ msgid "" +#~ "You must replace " +#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " +#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " +#~ "values." +#~ msgstr "" + +#~ msgid "" +#~ "For example to change Mjolnir's " +#~ "`recordIgnoredInvites` option to `true` you" +#~ " would add the following to your " +#~ "`vars.yml` file." +#~ 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 0cc472964..39afd04fa 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: 2024-12-16 12:05+0900\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" @@ -44,8 +44,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 msgid "" "See the project's [documentation](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk) to learn what it does and why it might be useful to" -" you." +"appservice-kakaotalk/src/branch/master/README.md) to learn what it does " +"and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 @@ -227,3 +227,11 @@ msgid "" "in the future, as that would break the Double Puppeting feature" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://src.miscworks.net/fair/matrix-" +#~ "appservice-kakaotalk) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ 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 7973bfcd1..ce60bf716 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: 2024-12-16 12:05+0900\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" @@ -32,8 +32,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/kelaresg/go-skype-" +"bridge/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 @@ -97,3 +98,9 @@ msgstr "" msgid "Send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 392e7645b..86ee04111 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: 2024-12-16 12:05+0900\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" @@ -42,9 +42,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 msgid "" "See the project's " -"[README](https://github.com/hifi/heisenbridge/blob/master/README.md) to " -"learn what it does and why it might be useful to you. You can also take a" -" look at [this demonstration " +"[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 "" @@ -182,3 +182,13 @@ msgid "" "[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[README](https://github.com/hifi/heisenbridge/blob/master/README.md)" +#~ " to learn what it does and why" +#~ " it might be useful to you. You" +#~ " can also take a look at [this" +#~ " demonstration " +#~ "video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +#~ 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 3e2ad96e1..14ef06275 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: 2024-12-16 12:05+0900\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" @@ -33,15 +33,15 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:5 msgid "" "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " -"from software project management services such as GitHub, GitLab, JIRA, " +"from software project management services such as GitHub, GitLab, Jira, " "and Figma, as well as generic webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:7 msgid "" "See the project's [documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/hookshot.html) to learn what it does in detail and why it" -" might be useful to you." +"hookshot/latest/hookshot.html) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:9 @@ -52,152 +52,172 @@ msgid "" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:11 -msgid "Setup Instructions" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:13 -msgid "" -"Refer to the [official instructions](https://matrix-org.github.io/matrix-" -"hookshot/latest/setup.html) to learn what the individual options do." +msgid "Download GitHub app private key (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:15 msgid "" -"Enable the bridge by adding `matrix_hookshot_enabled: true` to your " -"`vars.yml` file" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:16 -msgid "" -"For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) " -"fill in the respective variables `matrix_hookshot_service_*` listed in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as " -"required." +"If you're setting up the GitHub bridge, you need to create your GitHub " +"app, and generate a private key file of it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:17 msgid "" -"Take special note of the `matrix_hookshot_*_enabled` variables. Services " -"that need no further configuration are enabled by default (GitLab, " -"Generic), while you must first add the required configuration and enable " -"the others (GitHub, Jira, Figma)." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:18 -msgid "" -"If you're setting up the GitHub bridge, you'll need to generate and " -"download a private key file after you created your GitHub app. Copy the " -"contents of that file to the variable " -"`matrix_hookshot_github_private_key` so the playbook can install it for " -"you, or use one of the [other methods](#manage-github-private-key-with-" -"aux-role) explained below." +"You need to download the private key file, if you will install the file " +"manually or with the `aux` role. For details, see [the section below" +"](#manage-github-private-key-with-aux-role)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:19 -msgid "" -"If you've already installed Matrix services using the playbook before, " -"you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with" -" [configuring other playbook services](configuring-playbook.md) and then " -"with [Installing](installing.md). Get back to this guide once ready. " -"Hookshot can be set up individually using the tag `setup-hookshot`." +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:21 msgid "" -"Other configuration options are available via the " +"Add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " +"replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-" +"github-app-private-key)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 +msgid "" +"For each of the services (GitHub, GitLab, Jira, Figma, and generic " +"webhooks) fill in the respective variables `matrix_hookshot_service_*` " +"listed in [main.yml](../roles/custom/matrix-bridge-" +"hookshot/defaults/main.yml) as required." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 +msgid "" +"Take special note of the `matrix_hookshot_*_enabled` variables. Services " +"that need no further configuration are enabled by default (GitLab and " +"generic webhooks), while you must first add the required configuration " +"and enable the others (GitHub, Jira, and Figma)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 +msgid "" +"You can configure additional options by adding the " "`matrix_hookshot_configuration_extension_yaml` and " -"`matrix_hookshot_registration_extension_yaml` variables, see the comments" -" in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) " -"for how to use them." +"`matrix_hookshot_registration_extension_yaml` variables." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:23 -msgid "Finally, run the playbook (see [installing](installing.md))." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:25 -msgid "End-to-bridge encryption" -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:27 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 msgid "" -"You can enable [encryption](https://matrix-org.github.io/matrix-" -"hookshot/latest/advanced/encryption.html) for Hookshot by adding " -"`matrix_hookshot_encryption_enabled: true` to your configuration " -"(`vars.yml`) and [executing the playbook](installing.md) again." +"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:29 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 msgid "" -"Should the crypto store be corrupted, you can reset it by executing this " -"Ansible playbook with the tag `reset-hookshot-encryption` added, for " -"example `ansible-playbook -i inventory/hosts setup.yml --tags=reset-" -"hookshot-encryption`." +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:31 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 +msgid "" +"The shortcut commands with the [`just` program](just.md) are also " +"available: `just install-service hookshot` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 +msgid "" +"`just install-service hookshot` is useful for maintaining your setup " +"quickly when its components remain unchanged. If you adjust your " +"`vars.yml` to remove other components, you'd need to run `just setup-" +"all`, or these components will still remain installed. Note `just setup-" +"all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:58 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:33 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:60 msgid "" "To use the bridge, you need to create a room and invite the Hookshot bot " "(`@hookshot:example.com`) to it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:35 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:62 msgid "" "Make sure the bot is able to send state events (usually the Moderator " "power level in clients)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:37 -msgid "Send a `!hookshot help` message to see a list of help commands." +#: ../../../docs/configuring-playbook-bridge-hookshot.md:64 +msgid "" +"Send `!hookshot help` to the room to see the bridge's help menu for " +"additional commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:39 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:66 msgid "" "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-" "hookshot/latest/usage.html) for more details about using the bridge's " "various features." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:41 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:68 msgid "" -"**Important**: Note that the different listeners are bound to certain " -"paths which might differ from those assumed by the hookshot " -"documentation, see [URLs for bridges setup](#urls-for-bridges-setup) " -"below." +"💡 **Note**: the different listeners are bound to certain paths which " +"might differ from those assumed by the hookshot documentation. See [URLs " +"for bridges setup](#urls-for-bridges-setup) below." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:43 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +msgid "Reset crypto store" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 +msgid "" +"Should the crypto store be corrupted, you can reset it by executing this " +"Ansible playbook with the tag `reset-hookshot-encryption` added:" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-hookshot.md:78 msgid "More setup documentation" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:45 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:80 msgid "URLs for bridges setup" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:47 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:82 msgid "" "Unless indicated otherwise, the following endpoints are reachable on your" " `matrix.` subdomain (if the feature is enabled)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "listener" +msgid "Listener" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "default path" +msgid "Default path" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "variable" +msgid "Variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "used as" +msgid "Used as" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -261,7 +281,7 @@ msgid "`matrix_hookshot_jira_oauth_endpoint`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md -msgid "JIRA OAuth" +msgid "Jira OAuth" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -348,71 +368,72 @@ msgstr "" msgid "Prometheus" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:96 msgid "" "Also see the various `matrix_hookshot_container_labels_*` variables in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml), which" -" expose URLs publicly." +"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), " +"which expose URLs publicly" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 msgid "" "The different listeners are also reachable *internally* in the docker-" "network via the container's name (configured by " "`matrix_hookshot_container_url`) and on different ports (e.g. " -"`matrix_hookshot_appservice_port`). Read [main.yml](/roles/custom/matrix-" -"bridge-hookshot/defaults/main.yml) in detail for more info." +"`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:65 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 msgid "Manage GitHub Private Key with aux role" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:67 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:102 msgid "" "The GitHub bridge requires you to install a private key file. This can be" " done in multiple ways:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:68 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 msgid "" "copy the *contents* of the downloaded file and set the variable " "`matrix_hookshot_github_private_key` to the contents (see example in " -"[main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml))." +"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:69 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 msgid "" "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ " "matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot" "/private-key.pem`) on the server manually." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:106 msgid "" "use the [`aux` role](https://github.com/mother-of-all-self-hosting" "/ansible-role-aux) to copy the file from an arbitrary path on your " "ansible client to the correct path on the server." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:108 msgid "" "To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" -" variable is empty. Then add the following additional configuration:" +" variable is empty. Then add the following configuration to your " +"`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 msgid "" "For more information, see the documentation in the [default configuration" " of the aux role](https://github.com/mother-of-all-self-hosting/ansible-" "role-aux/blob/main/defaults/main.yml)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:85 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:121 msgid "Provisioning API" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:87 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:123 msgid "" "The provisioning API will be enabled automatically if you set " "`matrix_dimension_enabled: true` and provided a " @@ -422,11 +443,11 @@ msgid "" "`matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:89 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:125 msgid "Metrics" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:91 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:127 msgid "" "Metrics are **only enabled by default** if the builtin [Prometheus" "](configuring-playbook-prometheus-grafana.md) is enabled (by default, " @@ -435,32 +456,32 @@ msgid "" "set up your own Dashboard for displaying them." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:93 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:129 msgid "" "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: " "true`. This only exposes metrics over the container network, however." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:95 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:131 msgid "" "**To collect metrics from an external Prometheus server**, besides " "enabling metrics as described above, you will also need to enable metrics" " exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:97 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:133 msgid "" "either enabling metrics exposure for Hookshot via " "`matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:134 msgid "" "or enabling metrics exposure for all services via " "`matrix_metrics_exposure_enabled: true`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:100 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:136 msgid "" "Whichever one you go with, by default metrics are exposed publicly " "**without** password-protection. See [the Prometheus and Grafana docs" @@ -468,11 +489,11 @@ msgid "" "protection for metrics." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:102 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:138 msgid "Collision with matrix-appservice-webhooks" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:104 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:140 msgid "" "If you are also running [matrix-appservice-webhooks](configuring-" "playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" @@ -482,3 +503,175 @@ msgid "" "`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." msgstr "" +#~ 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 "" + +#~ msgid "" +#~ "See the project's [documentation](https://matrix-" +#~ "org.github.io/matrix-hookshot/latest/hookshot.html) to " +#~ "learn what it does in detail and" +#~ " why it might be useful to you." +#~ msgstr "" + +#~ msgid "Setup Instructions" +#~ msgstr "" + +#~ msgid "" +#~ "Refer to the [official instructions](https" +#~ "://matrix-org.github.io/matrix-hookshot/latest/setup.html)" +#~ " to learn what the individual options" +#~ " do." +#~ msgstr "" + +#~ msgid "" +#~ "Enable the bridge by adding " +#~ "`matrix_hookshot_enabled: true` to your " +#~ "`vars.yml` file" +#~ msgstr "" + +#~ msgid "" +#~ "For each of the services (GitHub, " +#~ "GitLab, Jira, Figma, generic webhooks) " +#~ "fill in the respective variables " +#~ "`matrix_hookshot_service_*` listed in " +#~ "[main.yml](/roles/custom/matrix-bridge-" +#~ "hookshot/defaults/main.yml) as required." +#~ msgstr "" + +#~ msgid "" +#~ "Take special note of the " +#~ "`matrix_hookshot_*_enabled` variables. Services that" +#~ " need no further configuration are " +#~ "enabled by default (GitLab, Generic), " +#~ "while you must first add the " +#~ "required configuration and enable the " +#~ "others (GitHub, Jira, Figma)." +#~ msgstr "" + +#~ msgid "" +#~ "If you're setting up the GitHub " +#~ "bridge, you'll need to generate and " +#~ "download a private key file after " +#~ "you created your GitHub app. Copy " +#~ "the contents of that file to the" +#~ " variable `matrix_hookshot_github_private_key` so " +#~ "the playbook can install it for " +#~ "you, or use one of the [other " +#~ "methods](#manage-github-private-key-with-" +#~ "aux-role) explained below." +#~ msgstr "" + +#~ msgid "" +#~ "If you've already installed Matrix " +#~ "services using the playbook before, " +#~ "you'll need to re-run it (`--tags" +#~ "=setup-all,start`). If not, proceed with" +#~ " [configuring other playbook services" +#~ "](configuring-playbook.md) and then with " +#~ "[Installing](installing.md). Get back to this" +#~ " guide once ready. Hookshot can be" +#~ " set up individually using the tag" +#~ " `setup-hookshot`." +#~ msgstr "" + +#~ msgid "" +#~ "Other configuration options are available " +#~ "via the `matrix_hookshot_configuration_extension_yaml` " +#~ "and `matrix_hookshot_registration_extension_yaml` " +#~ "variables, see the comments in " +#~ "[main.yml](/roles/custom/matrix-bridge-" +#~ "hookshot/defaults/main.yml) for how to use " +#~ "them." +#~ msgstr "" + +#~ msgid "Finally, run the playbook (see [installing](installing.md))." +#~ msgstr "" + +#~ msgid "End-to-bridge encryption" +#~ msgstr "" + +#~ msgid "" +#~ "You can enable [encryption](https://matrix-" +#~ "org.github.io/matrix-hookshot/latest/advanced/encryption.html)" +#~ " for Hookshot by adding " +#~ "`matrix_hookshot_encryption_enabled: true` to your" +#~ " configuration (`vars.yml`) and [executing " +#~ "the playbook](installing.md) again." +#~ msgstr "" + +#~ msgid "" +#~ "Should the crypto store be corrupted," +#~ " you can reset it by executing " +#~ "this Ansible playbook with the tag " +#~ "`reset-hookshot-encryption` added, for " +#~ "example `ansible-playbook -i inventory/hosts" +#~ " setup.yml --tags=reset-hookshot-encryption`." +#~ msgstr "" + +#~ msgid "Send a `!hookshot help` message to see a list of help commands." +#~ msgstr "" + +#~ msgid "" +#~ "**Important**: Note that the different " +#~ "listeners are bound to certain paths " +#~ "which might differ from those assumed" +#~ " by the hookshot documentation, see " +#~ "[URLs for bridges setup](#urls-for-" +#~ "bridges-setup) below." +#~ msgstr "" + +#~ msgid "listener" +#~ msgstr "" + +#~ msgid "default path" +#~ msgstr "" + +#~ msgid "variable" +#~ msgstr "" + +#~ msgid "used as" +#~ msgstr "" + +#~ msgid "JIRA OAuth" +#~ msgstr "" + +#~ 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 "" + +#~ 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 "" + +#~ 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 "" + +#~ msgid "" +#~ "To use the `aux` role, make sure" +#~ " the `matrix_hookshot_github_private_key` variable " +#~ "is empty. Then add the following " +#~ "additional configuration:" +#~ 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 b9ffa1e42..3ee8066a8 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: 2024-12-16 12:05+0900\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" @@ -32,8 +32,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/benkuly/matrix-sms-" +"bridge/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 @@ -98,3 +99,9 @@ msgid "" "bridge/blob/master/README.md#user-guide) to see how this bridge works." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 1e8109cd3..badc8ae74 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: 2024-12-16 12:05+0900\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" @@ -39,8 +39,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 msgid "" -"See the project's [documentation](https://github.com/mautrix/twitter) to " -"learn what it does and why it might be useful to you." +"See the project's " +"[documentation](https://github.com/mautrix/twitter/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 @@ -48,58 +49,61 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11 +msgid "Enable Appservice Double Puppet (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 msgid "" "If you want to set up [Double " "Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " "(hint: you most likely do) for this bridge automatically, you need to " "have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +"double-puppet.md) service for this playbook." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 msgid "" "For details about configuring Double Puppeting for this bridge, see the " "section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 msgid "" "To enable the bridge, add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:23 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:32 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 msgid "" "The `ensure-matrix-users-created` playbook tag makes the playbook " "automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 msgid "" "`just install-all` is useful for maintaining your setup quickly ([2x-5x " "faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" @@ -108,71 +112,60 @@ msgid "" "`just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44 msgid "" "You then need to start a chat with `@twitterbot:example.com` (where " "`example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:43 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 msgid "" "Send login-cookie to start the login. The bot should respond with " "instructions on how to proceed." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 msgid "" "You can learn more here about authentication from the bridge's [official " "documentation on " "Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 msgid "💡 Set up Double Puppeting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 msgid "" "After successfully enabling bridging, you may wish to set up [Double " "Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " "(hint: you most likely do)." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 msgid "To set it up, you have 2 ways of going about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" -msgstr "" - #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +"The bridge automatically performs Double Puppeting if [Appservice Double " +"Puppet](configuring-playbook-appservice-double-puppet.md) service is " +"configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +"This is the recommended way of setting up Double Puppeting, as it's " +"easier to accomplish, works for all your users automatically, and has " +"less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 @@ -181,9 +174,88 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 msgid "" -"This method is currently not available for the Mautrix-Twitter bridge, " -"but is on the " -"[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) " -"under Misc/Manual login with `login-matrix`" +"When using this method, **each user** that wishes to enable Double " +"Puppeting needs to follow the following steps:" msgstr "" +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 +msgid "" +"retrieve a Matrix access token for yourself. Refer to the documentation " +"on [how to do that](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 +msgid "" +"send the access token to the bot. Example: `login-matrix " +"MATRIX_ACCESS_TOKEN_HERE`" +msgstr "" + +#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69 +msgid "" +"make sure you don't log out the `Mautrix-Slack` device some time in the " +"future, as that would break the Double Puppeting feature" +msgstr "" + +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/mautrix/twitter) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ msgstr "" + +#~ 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 "" + +#~ msgid "" +#~ "Method 1: automatically, by enabling " +#~ "Appservice Double Puppet or Shared " +#~ "Secret Auth" +#~ msgstr "" + +#~ msgid "" +#~ "The bridge automatically performs Double " +#~ "Puppeting if [Appservice Double Puppet" +#~ "](configuring-playbook-appservice-double-" +#~ "puppet.md) or [Shared Secret Auth" +#~ "](configuring-playbook-shared-secret-auth.md) " +#~ "service is configured and enabled on " +#~ "the server for this playbook." +#~ msgstr "" + +#~ msgid "" +#~ "Enabling [Appservice Double Puppet](configuring-" +#~ "playbook-appservice-double-puppet.md) is " +#~ "the recommended way of setting up " +#~ "Double Puppeting, as it's easier to " +#~ "accomplish, works for all your users " +#~ "automatically, and has less of a " +#~ "chance of breaking in the future." +#~ msgstr "" + +#~ msgid "" +#~ "Enabling double puppeting by enabling " +#~ "the [Shared Secret Auth](configuring-" +#~ "playbook-shared-secret-auth.md) service " +#~ "works at the time of writing, but" +#~ " is deprecated and will stop working" +#~ " in the future." +#~ msgstr "" + +#~ msgid "" +#~ "This method is currently not available" +#~ " for the Mautrix-Twitter bridge, but" +#~ " is on the " +#~ "[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md)" +#~ " under Misc/Manual login with `login-" +#~ "matrix`" +#~ 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 673a7908b..16822cbfc 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: 2024-12-16 12:05+0900\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" @@ -35,8 +35,8 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 msgid "" "See the project's " -"[documentation](https://github.com/mautrix/wsproxy#readme) to learn what " -"it does and why it might be useful to you." +"[documentation](https://github.com/mautrix/wsproxy/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 @@ -143,3 +143,10 @@ msgid "" "running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/mautrix/wsproxy#readme) to" +#~ " learn what it does and why it" +#~ " might be useful to you." +#~ 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 ee082570c..715823a51 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: 2024-12-16 12:05+0900\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" @@ -54,8 +54,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/mx-puppet/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 @@ -137,3 +138,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 0e89d39f8..4381c17cf 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/xangelix-pub/matrix" +"/mx-puppet-groupme/blob/master/README.md) to learn what it does and why " +"it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 @@ -121,3 +122,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 02d3399ae..80130e822 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: 2024-12-16 12:05+0900\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" @@ -44,8 +44,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-" +"puppet-slack/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 @@ -138,3 +139,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 46bb77cc2..e95f4c70a 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: 2024-12-16 12:05+0900\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" @@ -32,8 +32,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/icewind1991/mx-" +"puppet-steam/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 @@ -114,3 +115,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 4e21b4966..1583475ca 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: 2024-12-16 12:05+0900\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" @@ -39,8 +39,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/Sorunome/mx-puppet-" +"twitter/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9 @@ -128,3 +129,9 @@ msgstr "" msgid "Also send `help` to the bot to see the commands available." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index c70b924fd..7bc3831ab 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -45,8 +45,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 msgid "" -"See the project's [documentation](https://github.com/etkecc/postmoogle) " -"to learn what it does and why it might be useful to you." +"See the project's " +"[documentation](https://github.com/etkecc/postmoogle/blob/master/README.md)" +" to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 @@ -195,3 +196,10 @@ msgid "" " it to `DEBUG` with the following additional configuration:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/etkecc/postmoogle) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 9adff616c..6fd0059f3 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: 2024-12-16 12:05+0900\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" @@ -33,8 +33,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:5 msgid "" -"See the project page to learn what it does and why it might be useful to " -"you." +"See the project's [documentation](https://github.com/duo/matrix-" +"wechat/blob/master/README.md) to learn what it does and why it might be " +"useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:7 @@ -96,3 +97,9 @@ msgstr "" msgid "Send `help` to the bot to see the available commands." msgstr "" +#~ msgid "" +#~ "See the project page to learn what" +#~ " it does and why it might be" +#~ " useful to you." +#~ 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 dfac1cb02..8b73bae84 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: 2024-12-16 12:05+0900\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" @@ -226,33 +226,59 @@ msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 msgid "" -"To enable Email2Matrix, run the playbook with [playbook tags](playbook-" +"After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:93 +#: ../../../docs/configuring-playbook-email2matrix.md:94 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:95 +#: ../../../docs/configuring-playbook-email2matrix.md:96 msgid "" "The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-email2matrix,start` or `just setup-all`" +"available: `just install-service email2matrix` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:97 +#: ../../../docs/configuring-playbook-email2matrix.md:98 msgid "" -"`just run-tags setup-email2matrix,start` is useful for maintaining your " -"setup quickly when its components remain unchanged. If you adjust your " +"`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:99 +#: ../../../docs/configuring-playbook-email2matrix.md:100 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 "" +#~ msgid "" +#~ "To enable Email2Matrix, run the playbook" +#~ " with [playbook tags](playbook-tags.md) as" +#~ " below:" +#~ msgstr "" + +#~ msgid "" +#~ "The shortcut commands with the [`just`" +#~ " program](just.md) are also available: " +#~ "`just run-tags setup-email2matrix,start` " +#~ "or `just setup-all`" +#~ msgstr "" + +#~ msgid "" +#~ "`just run-tags setup-email2matrix,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 "" + 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 a02b8c7dd..49d8e8fe4 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: 2024-12-16 12:05+0900\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" @@ -35,8 +35,9 @@ msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/matrix-org/matrix-" +"synapse-ldap3/blob/main/README.rst) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:7 @@ -81,3 +82,9 @@ msgid "" "](configuring-playbook-matrix-ldap-registration-proxy.md)." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 c716e47a8..fd9b19f79 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: 2024-12-16 12:05+0900\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" @@ -52,8 +52,9 @@ msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:9 msgid "" -"See the project's [documentation](https://github.com/ma1uta/ma1sd) to " -"learn what it does and why it might be useful to you." +"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 @@ -332,3 +333,10 @@ msgid "" "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" +#~ msgid "" +#~ "See the project's " +#~ "[documentation](https://github.com/ma1uta/ma1sd) to learn" +#~ " what it does and why it might" +#~ " be useful to you." +#~ 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 9e50af971..43934ff04 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: 2024-12-16 12:05+0900\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" @@ -42,101 +42,107 @@ msgstr "" 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. See that project's documentation to learn what it does and " -"why it might be useful to you." +"environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:13 msgid "" +"See the project's [documentation](https://github.com/devture/matrix-" +"corporal/blob/main/README.md) to learn what it does and why it might be " +"useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +msgid "" "If you decide that you'd like to let this playbook install it for you, " "you'd need to also:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:14 +#: ../../../docs/configuring-playbook-matrix-corporal.md:16 msgid "" "(required) [set up the Shared Secret Auth password provider module" "](configuring-playbook-shared-secret-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:15 +#: ../../../docs/configuring-playbook-matrix-corporal.md:17 msgid "" "(optional, but encouraged) [set up the REST authentication password " "provider module](configuring-playbook-rest-auth.md)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:17 +#: ../../../docs/configuring-playbook-matrix-corporal.md:19 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:19 +#: ../../../docs/configuring-playbook-matrix-corporal.md:21 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:72 +#: ../../../docs/configuring-playbook-matrix-corporal.md:74 msgid "" "Matrix Corporal operates with a specific Matrix user on your server. By " "default, it's `matrix-corporal` (controllable by the " "`matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:74 +#: ../../../docs/configuring-playbook-matrix-corporal.md:76 msgid "" "No matter what Matrix user ID you configure to run it with, make sure " "that:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:76 +#: ../../../docs/configuring-playbook-matrix-corporal.md:78 msgid "" "the Matrix Corporal user is created by [registering it](registering-" "users.md) **with administrator privileges**. Use a password you remember," " as you'll need to log in from time to time to create or join rooms" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:78 +#: ../../../docs/configuring-playbook-matrix-corporal.md:80 msgid "" "the Matrix Corporal user is joined and has Admin/Moderator-level access " "to any rooms you want it to manage" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:80 +#: ../../../docs/configuring-playbook-matrix-corporal.md:82 msgid "Using a locally-stored static policy" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:82 +#: ../../../docs/configuring-playbook-matrix-corporal.md:84 msgid "" "If you'd like to use a [static policy file](https://github.com/devture" "/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-" "style-policy-provider), you can use a configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:114 +#: ../../../docs/configuring-playbook-matrix-corporal.md:116 msgid "" "To learn more about what the policy configuration, see the matrix-" "corporal documentation on [policy](https://github.com/devture/matrix-" "corporal/blob/master/docs/policy.md)." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:116 +#: ../../../docs/configuring-playbook-matrix-corporal.md:118 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:118 +#: ../../../docs/configuring-playbook-matrix-corporal.md:120 msgid "" "After configuring the playbook, run it with [playbook tags](playbook-" "tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:125 +#: ../../../docs/configuring-playbook-matrix-corporal.md:127 msgid "" "The shortcut commands with the [`just` program](just.md) are also " "available: `just run-tags setup-aux-files,setup-corporal,start` or `just " "setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:127 +#: ../../../docs/configuring-playbook-matrix-corporal.md:129 msgid "" "`just run-tags setup-aux-files,setup-corporal,start` is useful for " "maintaining your setup quickly when its components remain unchanged. If " @@ -145,33 +151,33 @@ msgid "" "`just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:129 +#: ../../../docs/configuring-playbook-matrix-corporal.md:131 msgid "Matrix Corporal files" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:131 +#: ../../../docs/configuring-playbook-matrix-corporal.md:133 msgid "" "The following local filesystem paths are mounted in the `matrix-corporal`" " container and can be used in your configuration (or policy):" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:133 +#: ../../../docs/configuring-playbook-matrix-corporal.md:135 msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:135 +#: ../../../docs/configuring-playbook-matrix-corporal.md:137 msgid "" "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " "write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:137 +#: ../../../docs/configuring-playbook-matrix-corporal.md:139 msgid "" "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" " and write)" msgstr "" -#: ../../../docs/configuring-playbook-matrix-corporal.md:139 +#: ../../../docs/configuring-playbook-matrix-corporal.md:141 msgid "" "As an example: you can create your own configuration files in " "`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " @@ -182,3 +188,13 @@ msgid "" "and write)." msgstr "" +#~ 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. See that project's documentation" +#~ " to learn what it does and why" +#~ " it might be useful to you." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po index eaca549e9..4e47061d4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -34,7 +34,8 @@ msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:5 msgid "" "See the project's [documentation](https://github.com/matrix-" -"org/pantalaimon) to learn what it does and why it might be useful to you." +"org/pantalaimon/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:7 @@ -90,3 +91,10 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/pantalaimon) to learn what it" +#~ " does and why it might be " +#~ "useful to you." +#~ 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 2a1d13324..ec978d039 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: 2024-12-16 12:05+0900\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" @@ -35,8 +35,9 @@ msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/ma1uta/matrix-" +"synapse-rest-password-provider/blob/master/README.md) to learn what it " +"does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:7 @@ -87,3 +88,9 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 7c14374e6..7c1c8bc8b 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: 2024-12-16 12:05+0900\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" @@ -35,8 +35,9 @@ msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you." +"See the project's [documentation](https://github.com/devture/matrix-" +"synapse-shared-secret-auth/blob/master/README.md) to learn what it does " +"and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:7 @@ -86,3 +87,9 @@ msgid "" "these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 258e8279d..81646fa21 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: 2024-12-16 12:05+0900\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" @@ -32,8 +32,9 @@ msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:5 msgid "" -"See the project's [documentation](https://github.com/matrix-org/sygnal) " -"to learn what it does and why it might be useful to you." +"See the project's [documentation](https://github.com/matrix-" +"org/sygnal/blob/master/README.md) to learn what it does and why it might " +"be useful to you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:7 @@ -199,3 +200,10 @@ msgid "" "/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/sygnal) to learn what it " +#~ "does and why it might be useful" +#~ " to you." +#~ 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 acd1713e0..bf5494b8b 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: 2024-12-16 12:05+0900\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" @@ -33,15 +33,20 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 msgid "" -"See that project's [documentation](https://github.com/matrix-org/synapse-" -"auto-accept-invite) to learn what it does and why it might be useful to " -"you. In short, it automatically accepts room invites. You can specify " -"that only 1:1 room invites are auto-accepted. Defaults to false if not " +"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 " @@ -51,11 +56,11 @@ msgid "" "party module." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 msgid "Configuration" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11 +#: ../../../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-" @@ -63,11 +68,11 @@ msgid "" "`inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:19 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 msgid "Synapse worker deployments" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23 msgid "" "In a [workerized Synapse deployment](https://github.com/spantaleev" "/matrix-docker-ansible-" @@ -77,17 +82,17 @@ msgid "" "is `null`). For example, add this to your configuration:" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:27 +#: ../../../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:29 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 msgid "Native alternative" msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31 +#: ../../../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 " @@ -96,7 +101,19 @@ msgid "" "/element-hq/synapse/pull/17147) part of Synapse." msgstr "" -#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 +#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:35 msgid "Here's example configuration for using the **native** Synapse feature:" msgstr "" +#~ msgid "" +#~ "See that project's " +#~ "[documentation](https://github.com/matrix-org/synapse-" +#~ "auto-accept-invite) to learn what it" +#~ " does and why it might be " +#~ "useful to you. In short, it " +#~ "automatically accepts room invites. You " +#~ "can specify that only 1:1 room " +#~ "invites are auto-accepted. Defaults to" +#~ " false if not specified." +#~ 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 a7359c3c0..cb5655ca9 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: 2024-12-16 12:05+0900\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" @@ -40,8 +40,9 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 msgid "" "See the project's [documentation](https://github.com/matrix-org/rust-" -"synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn " -"what it does and why it might be useful to you." +"synapse-compress-state/blob/master/README.md#automated-tool-" +"synapse_auto_compressor) to learn what it does and why it might be useful" +" to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 @@ -106,3 +107,11 @@ msgid "" "unstable." msgstr "" +#~ msgid "" +#~ "See the project's [documentation](https://github.com" +#~ "/matrix-org/rust-synapse-compress-state" +#~ "/#automated-tool-synapse_auto_compressor) to " +#~ "learn what it does and why it " +#~ "might be useful to you." +#~ 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 2e0c82766..6803bc2ba 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: 2024-12-16 12:05+0900\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" @@ -32,20 +32,35 @@ msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 msgid "" -"See that project's documentation to learn what it does and why it might " -"be useful to you. In short, it lets you fight invite-spam by " -"automatically blocking invitiations from a list of servers specified by " -"you (blacklisting)." +"It lets you fight invite-spam by automatically blocking invitiations from" +" a list of servers specified by you (blacklisting)." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 -msgid "Adjusting the playbook configuration" +msgid "" +"See the project's [documentation](https://github.com/t2bot/synapse-" +"simple-antispam/blob/master/README.md) to learn what it does and why it " +"might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 msgid "" "Add the following configuration to your " "`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " "needs):" msgstr "" +#~ msgid "" +#~ "See that project's documentation to " +#~ "learn what it does and why it " +#~ "might be useful to you. In short," +#~ " it lets you fight invite-spam " +#~ "by automatically blocking invitiations from" +#~ " a list of servers specified by " +#~ "you (blacklisting)." +#~ msgstr "" + diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index ddb720e35..d33faf33d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -237,71 +237,71 @@ msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:90 msgid "" -"After these variables have been set, run the playbook with [playbook tags" -"](playbook-tags.md) as below to restart UVS:" +"After configuring the playbook, run it with [playbook tags](playbook-" +"tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:96 +#: ../../../docs/configuring-playbook-user-verification-service.md:97 msgid "" "The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-matrix-user-verification-service,start` " -"or `just setup-all`" +"available: `just install-service matrix-user-verification-service` or " +"`just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:98 +#: ../../../docs/configuring-playbook-user-verification-service.md:99 msgid "" -"`just run-tags setup-matrix-user-verification-service,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." +"`just install-service matrix-user-verification-service` is useful for " +"maintaining your setup quickly when its components remain unchanged. If " +"you adjust your `vars.yml` to remove other components, you'd need to run " +"`just setup-all`, or these components will still remain installed. Note " +"`just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:100 +#: ../../../docs/configuring-playbook-user-verification-service.md:101 msgid "Logging" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:102 +#: ../../../docs/configuring-playbook-user-verification-service.md:103 msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:103 +#: ../../../docs/configuring-playbook-user-verification-service.md:104 msgid "warning" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:104 +#: ../../../docs/configuring-playbook-user-verification-service.md:105 msgid "info" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:105 +#: ../../../docs/configuring-playbook-user-verification-service.md:106 msgid "debug" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:107 +#: ../../../docs/configuring-playbook-user-verification-service.md:108 msgid "TLS Certificate Checking" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:109 +#: ../../../docs/configuring-playbook-user-verification-service.md:110 msgid "" "If the Matrix Homeserver does not provide a valid TLS certificate, UVS " "will fail with the following error message:" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:111 +#: ../../../docs/configuring-playbook-user-verification-service.md:112 msgid "message: 'No response received: [object Object]'," msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:113 +#: ../../../docs/configuring-playbook-user-verification-service.md:114 msgid "This also applies to self-signed and let's encrypt staging certificates." msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:115 +#: ../../../docs/configuring-playbook-user-verification-service.md:116 msgid "" "To disable certificate validation altogether (INSECURE! Not suitable for " "production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" msgstr "" -#: ../../../docs/configuring-playbook-user-verification-service.md:117 +#: ../../../docs/configuring-playbook-user-verification-service.md:118 msgid "" "Alternatively, it is possible to inject your own CA certificates into the" " container by mounting a PEM file with additional trusted CAs into the " @@ -309,3 +309,31 @@ msgid "" "it." msgstr "" +#~ msgid "" +#~ "After these variables have been set, " +#~ "run the playbook with [playbook tags" +#~ "](playbook-tags.md) as below to restart " +#~ "UVS:" +#~ msgstr "" + +#~ msgid "" +#~ "The shortcut commands with the [`just`" +#~ " program](just.md) are also available: " +#~ "`just run-tags setup-matrix-user-" +#~ "verification-service,start` or `just setup-" +#~ "all`" +#~ msgstr "" + +#~ msgid "" +#~ "`just run-tags setup-matrix-user-" +#~ "verification-service,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 "" + From 1636c491346c98cdc2bc9f4ef1657fd0d77b4dc0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 20 Dec 2024 18:58:05 +0900 Subject: [PATCH 123/952] Start adopting REUSE on files for a brand new subproject (translation) REUSE is an initiative by FSFE, which intends to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable. Because these files are new and translation shall involve a lot of people as copyright holders, now is the best time to adopt REUSE. As a first implementation, this commit intentionally limits the scope to i18n directory. Cherry-picked from c737ed0612e5b8bd5837877df63932d77bdcfcf7 and a2445af6d0100a43d6011b31402b9ae8f0c38f0c Signed-off-by: Suguru Hirahara --- LICENSES/AGPL-3.0-or-later.txt | 235 ++++++++++++++++++ conf.py | 5 + i18n/README.md | 7 + i18n/bin/build-translated-result.sh | 4 + i18n/bin/extract-translation-templates.sh | 2 + .../sync-translation-templates-to-locales.sh | 4 + i18n/justfile | 4 + reuse.toml | 25 ++ 8 files changed, 286 insertions(+) create mode 100644 LICENSES/AGPL-3.0-or-later.txt create mode 100644 reuse.toml diff --git a/LICENSES/AGPL-3.0-or-later.txt b/LICENSES/AGPL-3.0-or-later.txt new file mode 100644 index 000000000..0c97efd25 --- /dev/null +++ b/LICENSES/AGPL-3.0-or-later.txt @@ -0,0 +1,235 @@ +GNU AFFERO GENERAL PUBLIC LICENSE +Version 3, 19 November 2007 + +Copyright (C) 2007 Free Software Foundation, Inc. + +Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. + + Preamble + +The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. + +The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. + +When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. + +Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. + +A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. + +The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. + +An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. + +The precise terms and conditions for copying, distribution and modification follow. + + TERMS AND CONDITIONS + +0. Definitions. + +"This License" refers to version 3 of the GNU Affero General Public License. + +"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. + +"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. + +To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. + +A "covered work" means either the unmodified Program or a work based on the Program. + +To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. + +To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. + +An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. + +1. Source Code. +The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. + +A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. + +The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. + +The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those +subprograms and other parts of the work. + +The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. + +The Corresponding Source for a work in source code form is that same work. + +2. Basic Permissions. +All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. + +You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. + +Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. + +3. Protecting Users' Legal Rights From Anti-Circumvention Law. +No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. + +When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. + +4. Conveying Verbatim Copies. +You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. + +You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. + +5. Conveying Modified Source Versions. +You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". + + c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. + +A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. + +6. Conveying Non-Source Forms. +You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: + + a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. + + d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + +A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. + +A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. + +"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. + +If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). + +The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. + +Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. + +7. Additional Terms. +"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. + +When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. + +Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or authors of the material; or + + e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. + +All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. + +If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. + +Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. + +8. Termination. + +You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). + +However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. + +Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. + +Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. + +9. Acceptance Not Required for Having Copies. + +You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. + +10. Automatic Licensing of Downstream Recipients. + +Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. + +An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. + +You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. + +11. Patents. + +A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". + +A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. + +Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. + +In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. + +If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. + +If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. + +A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. + +Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. + +12. No Surrender of Others' Freedom. + +If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. + +13. Remote Network Interaction; Use with the GNU General Public License. + +Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. + +Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. + +14. Revised Versions of this License. + +The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. + +If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. + +Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. + +15. Disclaimer of Warranty. + +THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + +16. Limitation of Liability. + +IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +17. Interpretation of Sections 15 and 16. + +If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + +END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + +If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. + +To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. + + This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + +If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. + +You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see . diff --git a/conf.py b/conf.py index a36a20f4d..1dcc1801d 100644 --- a/conf.py +++ b/conf.py @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # Configuration file for the Sphinx documentation builder. # Also see the `i18n/` directory. # diff --git a/i18n/README.md b/i18n/README.md index f5a1b5fa7..93e99ad8e 100644 --- a/i18n/README.md +++ b/i18n/README.md @@ -1,3 +1,10 @@ + + # Internationalization Translated documentation files are published and maintained in [`translated/`](translated/) directory. diff --git a/i18n/bin/build-translated-result.sh b/i18n/bin/build-translated-result.sh index 6695714ec..d918100d3 100755 --- a/i18n/bin/build-translated-result.sh +++ b/i18n/bin/build-translated-result.sh @@ -1,5 +1,9 @@ #!/bin/bash +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # This script builds the translated result (translated project) for a given language in the `translated//` directory. set -euxo pipefail diff --git a/i18n/bin/extract-translation-templates.sh b/i18n/bin/extract-translation-templates.sh index 02abbcece..3cbaeec8f 100755 --- a/i18n/bin/extract-translation-templates.sh +++ b/i18n/bin/extract-translation-templates.sh @@ -1,5 +1,7 @@ #!/bin/bash +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev + # This script extracts translation templates (original English strings) into the `translation-templates/` directory. # These templates are later used to generate locale files for each language in the `locales/` directory. # diff --git a/i18n/bin/sync-translation-templates-to-locales.sh b/i18n/bin/sync-translation-templates-to-locales.sh index 7d33921ce..4d990df6e 100755 --- a/i18n/bin/sync-translation-templates-to-locales.sh +++ b/i18n/bin/sync-translation-templates-to-locales.sh @@ -1,5 +1,9 @@ #!/bin/bash +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # This script updates the translation files (locales//**/*.po) for a given language. # It uses the translation templates (translation-templates/**/*.pot) to generate the translation files. diff --git a/i18n/justfile b/i18n/justfile index 4021dfabb..d33f2cd61 100644 --- a/i18n/justfile +++ b/i18n/justfile @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # Shows help default: @just --list --justfile {{ justfile() }} diff --git a/reuse.toml b/reuse.toml new file mode 100644 index 000000000..77ad4587b --- /dev/null +++ b/reuse.toml @@ -0,0 +1,25 @@ +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + +version = 1 + +# Computer-generated files and other files which cannot be copyrighted +[[annotations]] +path = [ + "i18n/.gitignore", + "i18n/requirements.txt", + "i18n/PUBLISHED_LANGUAGES" +] +SPDX-FileCopyrightText = "NONE" +SPDX-License-Identifier = "CC0-1.0" + +# See https://reuse.software/faq/#aggregate-info +[[annotations]] +path = [ + "i18n/**/*.po", + "i18n/**/*.pot" +] +precedence = "aggregate" +SPDX-FileCopyrightText = "Slavi Pantaleev, MDAD community members" +SPDX-License-Identifier = "AGPL-3.0-or-later" From 71e5f1103d658ebc1710df048b0f3a676c3c755e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 14:33:31 +0200 Subject: [PATCH 124/952] Use msgcat to avoid word-wrapping in .po files --- .../sync-translation-templates-to-locales.sh | 8 + i18n/locales/bg/LC_MESSAGES/CHANGELOG.po | 6313 +++-------------- i18n/locales/bg/LC_MESSAGES/README.po | 380 +- i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po | 511 +- i18n/locales/bg/LC_MESSAGES/docs/README.po | 70 +- .../docs/alternative-architectures.po | 26 +- i18n/locales/bg/LC_MESSAGES/docs/ansible.po | 162 +- .../LC_MESSAGES/docs/configuring-captcha.po | 23 +- .../bg/LC_MESSAGES/docs/configuring-dns.po | 102 +- ...figuring-playbook-alertmanager-receiver.po | 236 +- ...uring-playbook-appservice-double-puppet.po | 48 +- ...ng-playbook-appservice-draupnir-for-all.po | 284 +- .../docs/configuring-playbook-backup-borg.po | 116 +- ...onfiguring-playbook-base-domain-serving.po | 129 +- .../docs/configuring-playbook-bot-baibot.po | 403 +- .../configuring-playbook-bot-buscarron.po | 94 +- .../docs/configuring-playbook-bot-chatgpt.po | 69 +- .../docs/configuring-playbook-bot-draupnir.po | 488 +- .../docs/configuring-playbook-bot-go-neb.po | 112 +- .../docs/configuring-playbook-bot-honoroit.po | 87 +- ...ng-playbook-bot-matrix-registration-bot.po | 80 +- ...guring-playbook-bot-matrix-reminder-bot.po | 72 +- .../docs/configuring-playbook-bot-maubot.po | 110 +- .../docs/configuring-playbook-bot-mjolnir.po | 290 +- ...ring-playbook-bridge-appservice-discord.po | 126 +- ...figuring-playbook-bridge-appservice-irc.po | 43 +- ...ng-playbook-bridge-appservice-kakaotalk.po | 122 +- ...guring-playbook-bridge-appservice-slack.po | 130 +- ...ing-playbook-bridge-appservice-webhooks.po | 73 +- ...iguring-playbook-bridge-beeper-linkedin.po | 98 +- ...iguring-playbook-bridge-go-skype-bridge.po | 45 +- ...onfiguring-playbook-bridge-heisenbridge.po | 101 +- .../configuring-playbook-bridge-hookshot.po | 368 +- ...uring-playbook-bridge-matrix-bridge-sms.po | 48 +- ...iguring-playbook-bridge-mautrix-discord.po | 179 +- ...guring-playbook-bridge-mautrix-facebook.po | 143 +- ...uring-playbook-bridge-mautrix-gmessages.po | 81 +- ...ring-playbook-bridge-mautrix-googlechat.po | 113 +- ...guring-playbook-bridge-mautrix-hangouts.po | 108 +- ...uring-playbook-bridge-mautrix-instagram.po | 72 +- ...-playbook-bridge-mautrix-meta-instagram.po | 142 +- ...-playbook-bridge-mautrix-meta-messenger.po | 185 +- ...figuring-playbook-bridge-mautrix-signal.po | 121 +- ...nfiguring-playbook-bridge-mautrix-slack.po | 153 +- ...guring-playbook-bridge-mautrix-telegram.po | 115 +- ...iguring-playbook-bridge-mautrix-twitter.po | 156 +- ...guring-playbook-bridge-mautrix-whatsapp.po | 109 +- ...iguring-playbook-bridge-mautrix-wsproxy.po | 77 +- ...uring-playbook-bridge-mx-puppet-discord.po | 71 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 59 +- ...ing-playbook-bridge-mx-puppet-instagram.po | 58 +- ...iguring-playbook-bridge-mx-puppet-skype.po | 12 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 70 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 54 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 58 +- .../configuring-playbook-bridge-postmoogle.po | 104 +- .../configuring-playbook-bridge-wechat.po | 44 +- .../configuring-playbook-cactus-comments.po | 118 +- .../docs/configuring-playbook-client-cinny.po | 74 +- ...configuring-playbook-client-element-web.po | 134 +- .../configuring-playbook-client-hydrogen.po | 57 +- ...iguring-playbook-client-schildichat-web.po | 136 +- .../docs/configuring-playbook-conduit.po | 66 +- .../docs/configuring-playbook-dendrite.po | 86 +- .../docs/configuring-playbook-dimension.po | 147 +- .../docs/configuring-playbook-dynamic-dns.po | 36 +- .../docs/configuring-playbook-email.po | 62 +- .../docs/configuring-playbook-email2matrix.po | 153 +- .../docs/configuring-playbook-etherpad.po | 129 +- .../configuring-playbook-external-postgres.po | 43 +- .../docs/configuring-playbook-federation.po | 75 +- .../docs/configuring-playbook-jitsi.po | 309 +- .../docs/configuring-playbook-ldap-auth.po | 43 +- .../docs/configuring-playbook-ma1sd.po | 199 +- ...-playbook-matrix-authentication-service.po | 636 +- .../configuring-playbook-matrix-corporal.po | 113 +- ...playbook-matrix-ldap-registration-proxy.po | 38 +- .../configuring-playbook-matrix-media-repo.po | 136 +- ...onfiguring-playbook-matrix-registration.po | 103 +- .../configuring-playbook-mautrix-bridges.po | 125 +- .../docs/configuring-playbook-nginx.po | 1 - .../docs/configuring-playbook-ntfy.po | 187 +- .../configuring-playbook-own-webserver.po | 152 +- .../docs/configuring-playbook-pantalaimon.po | 51 +- .../configuring-playbook-postgres-backup.po | 41 +- ...configuring-playbook-prometheus-grafana.po | 265 +- ...onfiguring-playbook-prometheus-nginxlog.po | 97 +- ...onfiguring-playbook-prometheus-postgres.po | 54 +- .../docs/configuring-playbook-rageshake.po | 70 +- .../docs/configuring-playbook-rest-auth.po | 47 +- .../docs/configuring-playbook-riot-web.po | 60 +- .../docs/configuring-playbook-s3-goofys.po | 120 +- .../docs/configuring-playbook-s3.po | 167 +- ...configuring-playbook-shared-secret-auth.po | 46 +- ...configuring-playbook-sliding-sync-proxy.po | 89 +- .../configuring-playbook-ssl-certificates.po | 83 +- .../docs/configuring-playbook-sygnal.po | 120 +- .../configuring-playbook-synapse-admin.po | 119 +- ...ing-playbook-synapse-auto-accept-invite.po | 62 +- ...guring-playbook-synapse-auto-compressor.po | 58 +- ...ng-playbook-synapse-s3-storage-provider.po | 206 +- ...guring-playbook-synapse-simple-antispam.po | 29 +- ...iguring-playbook-synapse-usage-exporter.po | 75 +- .../docs/configuring-playbook-synapse.po | 272 +- .../docs/configuring-playbook-telemetry.po | 31 +- .../docs/configuring-playbook-traefik.po | 110 +- .../docs/configuring-playbook-turn.po | 76 +- ...ring-playbook-user-verification-service.po | 182 +- .../LC_MESSAGES/docs/configuring-playbook.po | 435 +- .../docs/configuring-well-known.po | 213 +- .../bg/LC_MESSAGES/docs/container-images.po | 298 +- i18n/locales/bg/LC_MESSAGES/docs/faq.po | 791 +-- .../LC_MESSAGES/docs/getting-the-playbook.po | 57 +- .../docs/howto-server-delegation.po | 173 +- .../docs/howto-srv-server-delegation.po | 107 +- .../bg/LC_MESSAGES/docs/importing-postgres.po | 106 +- .../docs/importing-synapse-media-store.po | 40 +- .../docs/importing-synapse-sqlite.po | 54 +- .../locales/bg/LC_MESSAGES/docs/installing.po | 241 +- i18n/locales/bg/LC_MESSAGES/docs/just.po | 76 +- .../docs/maintenance-and-troubleshooting.po | 51 +- .../docs/maintenance-checking-services.po | 15 +- .../LC_MESSAGES/docs/maintenance-migrating.po | 96 +- .../LC_MESSAGES/docs/maintenance-postgres.po | 188 +- .../LC_MESSAGES/docs/maintenance-synapse.po | 178 +- .../docs/maintenance-upgrading-services.po | 94 +- .../docs/obtaining-access-tokens.po | 42 +- .../bg/LC_MESSAGES/docs/playbook-tags.po | 55 +- .../bg/LC_MESSAGES/docs/prerequisites.po | 142 +- .../bg/LC_MESSAGES/docs/quick-start.po | 309 +- .../bg/LC_MESSAGES/docs/registering-users.po | 162 +- .../bg/LC_MESSAGES/docs/self-building.po | 37 +- .../bg/LC_MESSAGES/docs/uninstalling.po | 40 +- .../docs/updating-users-passwords.po | 35 +- i18n/locales/bg/LC_MESSAGES/i18n/README.po | 308 +- i18n/locales/jp/LC_MESSAGES/CHANGELOG.po | 6313 +++-------------- i18n/locales/jp/LC_MESSAGES/README.po | 358 +- i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po | 511 +- i18n/locales/jp/LC_MESSAGES/docs/README.po | 70 +- .../docs/alternative-architectures.po | 26 +- i18n/locales/jp/LC_MESSAGES/docs/ansible.po | 162 +- .../LC_MESSAGES/docs/configuring-captcha.po | 23 +- .../jp/LC_MESSAGES/docs/configuring-dns.po | 102 +- ...figuring-playbook-alertmanager-receiver.po | 236 +- ...uring-playbook-appservice-double-puppet.po | 48 +- ...ng-playbook-appservice-draupnir-for-all.po | 284 +- .../docs/configuring-playbook-backup-borg.po | 116 +- ...onfiguring-playbook-base-domain-serving.po | 129 +- .../docs/configuring-playbook-bot-baibot.po | 403 +- .../configuring-playbook-bot-buscarron.po | 94 +- .../docs/configuring-playbook-bot-chatgpt.po | 69 +- .../docs/configuring-playbook-bot-draupnir.po | 488 +- .../docs/configuring-playbook-bot-go-neb.po | 112 +- .../docs/configuring-playbook-bot-honoroit.po | 87 +- ...ng-playbook-bot-matrix-registration-bot.po | 80 +- ...guring-playbook-bot-matrix-reminder-bot.po | 72 +- .../docs/configuring-playbook-bot-maubot.po | 110 +- .../docs/configuring-playbook-bot-mjolnir.po | 290 +- ...ring-playbook-bridge-appservice-discord.po | 126 +- ...figuring-playbook-bridge-appservice-irc.po | 43 +- ...ng-playbook-bridge-appservice-kakaotalk.po | 122 +- ...guring-playbook-bridge-appservice-slack.po | 130 +- ...ing-playbook-bridge-appservice-webhooks.po | 73 +- ...iguring-playbook-bridge-beeper-linkedin.po | 98 +- ...iguring-playbook-bridge-go-skype-bridge.po | 45 +- ...onfiguring-playbook-bridge-heisenbridge.po | 101 +- .../configuring-playbook-bridge-hookshot.po | 368 +- ...uring-playbook-bridge-matrix-bridge-sms.po | 48 +- ...iguring-playbook-bridge-mautrix-discord.po | 179 +- ...guring-playbook-bridge-mautrix-facebook.po | 143 +- ...uring-playbook-bridge-mautrix-gmessages.po | 81 +- ...ring-playbook-bridge-mautrix-googlechat.po | 113 +- ...guring-playbook-bridge-mautrix-hangouts.po | 108 +- ...uring-playbook-bridge-mautrix-instagram.po | 72 +- ...-playbook-bridge-mautrix-meta-instagram.po | 142 +- ...-playbook-bridge-mautrix-meta-messenger.po | 185 +- ...figuring-playbook-bridge-mautrix-signal.po | 121 +- ...nfiguring-playbook-bridge-mautrix-slack.po | 153 +- ...guring-playbook-bridge-mautrix-telegram.po | 115 +- ...iguring-playbook-bridge-mautrix-twitter.po | 156 +- ...guring-playbook-bridge-mautrix-whatsapp.po | 109 +- ...iguring-playbook-bridge-mautrix-wsproxy.po | 77 +- ...uring-playbook-bridge-mx-puppet-discord.po | 71 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 59 +- ...ing-playbook-bridge-mx-puppet-instagram.po | 58 +- ...iguring-playbook-bridge-mx-puppet-skype.po | 12 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 70 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 54 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 58 +- .../configuring-playbook-bridge-postmoogle.po | 104 +- .../configuring-playbook-bridge-wechat.po | 44 +- .../configuring-playbook-cactus-comments.po | 118 +- .../docs/configuring-playbook-client-cinny.po | 74 +- ...configuring-playbook-client-element-web.po | 134 +- .../configuring-playbook-client-hydrogen.po | 57 +- ...iguring-playbook-client-schildichat-web.po | 136 +- .../docs/configuring-playbook-conduit.po | 66 +- .../docs/configuring-playbook-dendrite.po | 86 +- .../docs/configuring-playbook-dimension.po | 147 +- .../docs/configuring-playbook-dynamic-dns.po | 36 +- .../docs/configuring-playbook-email.po | 62 +- .../docs/configuring-playbook-email2matrix.po | 153 +- .../docs/configuring-playbook-etherpad.po | 129 +- .../configuring-playbook-external-postgres.po | 43 +- .../docs/configuring-playbook-federation.po | 75 +- .../docs/configuring-playbook-jitsi.po | 309 +- .../docs/configuring-playbook-ldap-auth.po | 43 +- .../docs/configuring-playbook-ma1sd.po | 199 +- ...-playbook-matrix-authentication-service.po | 636 +- .../configuring-playbook-matrix-corporal.po | 113 +- ...playbook-matrix-ldap-registration-proxy.po | 38 +- .../configuring-playbook-matrix-media-repo.po | 136 +- ...onfiguring-playbook-matrix-registration.po | 103 +- .../configuring-playbook-mautrix-bridges.po | 125 +- .../docs/configuring-playbook-nginx.po | 1 - .../docs/configuring-playbook-ntfy.po | 187 +- .../configuring-playbook-own-webserver.po | 152 +- .../docs/configuring-playbook-pantalaimon.po | 51 +- .../configuring-playbook-postgres-backup.po | 41 +- ...configuring-playbook-prometheus-grafana.po | 265 +- ...onfiguring-playbook-prometheus-nginxlog.po | 97 +- ...onfiguring-playbook-prometheus-postgres.po | 54 +- .../docs/configuring-playbook-rageshake.po | 70 +- .../docs/configuring-playbook-rest-auth.po | 47 +- .../docs/configuring-playbook-riot-web.po | 60 +- .../docs/configuring-playbook-s3-goofys.po | 120 +- .../docs/configuring-playbook-s3.po | 167 +- ...configuring-playbook-shared-secret-auth.po | 46 +- ...configuring-playbook-sliding-sync-proxy.po | 89 +- .../configuring-playbook-ssl-certificates.po | 83 +- .../docs/configuring-playbook-sygnal.po | 120 +- .../configuring-playbook-synapse-admin.po | 119 +- ...ing-playbook-synapse-auto-accept-invite.po | 62 +- ...guring-playbook-synapse-auto-compressor.po | 58 +- ...ng-playbook-synapse-s3-storage-provider.po | 206 +- ...guring-playbook-synapse-simple-antispam.po | 29 +- ...iguring-playbook-synapse-usage-exporter.po | 75 +- .../docs/configuring-playbook-synapse.po | 272 +- .../docs/configuring-playbook-telemetry.po | 31 +- .../docs/configuring-playbook-traefik.po | 110 +- .../docs/configuring-playbook-turn.po | 76 +- ...ring-playbook-user-verification-service.po | 182 +- .../LC_MESSAGES/docs/configuring-playbook.po | 435 +- .../docs/configuring-well-known.po | 213 +- .../jp/LC_MESSAGES/docs/container-images.po | 298 +- i18n/locales/jp/LC_MESSAGES/docs/faq.po | 791 +-- .../LC_MESSAGES/docs/getting-the-playbook.po | 57 +- .../docs/howto-server-delegation.po | 173 +- .../docs/howto-srv-server-delegation.po | 107 +- .../jp/LC_MESSAGES/docs/importing-postgres.po | 106 +- .../docs/importing-synapse-media-store.po | 40 +- .../docs/importing-synapse-sqlite.po | 54 +- .../locales/jp/LC_MESSAGES/docs/installing.po | 241 +- i18n/locales/jp/LC_MESSAGES/docs/just.po | 76 +- .../docs/maintenance-and-troubleshooting.po | 51 +- .../docs/maintenance-checking-services.po | 15 +- .../LC_MESSAGES/docs/maintenance-migrating.po | 96 +- .../LC_MESSAGES/docs/maintenance-postgres.po | 188 +- .../LC_MESSAGES/docs/maintenance-synapse.po | 178 +- .../docs/maintenance-upgrading-services.po | 94 +- .../docs/obtaining-access-tokens.po | 42 +- .../jp/LC_MESSAGES/docs/playbook-tags.po | 55 +- .../jp/LC_MESSAGES/docs/prerequisites.po | 142 +- .../jp/LC_MESSAGES/docs/quick-start.po | 309 +- .../jp/LC_MESSAGES/docs/registering-users.po | 162 +- .../jp/LC_MESSAGES/docs/self-building.po | 37 +- .../jp/LC_MESSAGES/docs/uninstalling.po | 40 +- .../docs/updating-users-passwords.po | 35 +- i18n/locales/jp/LC_MESSAGES/i18n/README.po | 291 +- 269 files changed, 8438 insertions(+), 39279 deletions(-) diff --git a/i18n/bin/sync-translation-templates-to-locales.sh b/i18n/bin/sync-translation-templates-to-locales.sh index 4d990df6e..c1678a393 100755 --- a/i18n/bin/sync-translation-templates-to-locales.sh +++ b/i18n/bin/sync-translation-templates-to-locales.sh @@ -32,3 +32,11 @@ sphinx-intl update \ --pot-dir ${base_path}/i18n/translation-templates \ --locale-dir ${base_path}/i18n/locales \ --language ${LANGUAGE} + +# Post-process all .po files to remove word-wrapping. +# +# Tools for editing .po files like Poedit don't use word-wrapping, +# and us not using word-wrapping here means diffs can be smaller. +for po_file in $(find ${base_path}/i18n/locales -name '*.po'); do + msgcat --no-wrap -o "$po_file" "$po_file" +done diff --git a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po index a293d80bd..d9f668a66 100644 --- a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po +++ b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po @@ -26,62 +26,35 @@ msgid "2024-11-26" msgstr "" #: ../../../CHANGELOG.md:3 -msgid "" -"(Backward Compatibility Break) Synapse now defaults to enabling " -"authenticated media" +msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media" msgstr "" #: ../../../CHANGELOG.md:5 -msgid "" -"**TLDR**: with this update, your Synapse homeserver will start requiring " -"authentication for newly-uploaded media files. While the majority of the " -"ecosystem (clients, bots, etc.) should support this, certain software may" -" lack support for it (and you may wish to turn it off, if it's causing " -"issues)." +msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)." msgstr "" #: ../../../CHANGELOG.md:7 -msgid "" -"The default configuration for the Synapse homeserver now [enforces " -"Authenticated media by default](https://element-" -"hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-" -"enforced-by-default)." +msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)." msgstr "" #: ../../../CHANGELOG.md:9 -msgid "" -"Servers like `matrix.org` have already [sunset unauthenticated " -"media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-" -"media/) months ago." +msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago." msgstr "" #: ../../../CHANGELOG.md:11 -msgid "" -"Now that **various clients, bots, bridges and extra services have caught " -"up with authenticated media support**, Synapse developers seem confident " -"that it's time to enable authenticated media by default." +msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default." msgstr "" #: ../../../CHANGELOG.md:13 -msgid "" -"We're changing the playbook configuration for authenticated media to keep" -" up with upstream defaults changing." +msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing." msgstr "" #: ../../../CHANGELOG.md:15 -msgid "" -"Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not " -"support authenticated media. Other software may be similarly affected. If" -" you experience issues with some Matrix-related software, you may wish to" -" disable authenticated media and contact the software maintainers to let " -"them know." +msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know." msgstr "" #: ../../../CHANGELOG.md:17 -msgid "" -"You can disable authenticated media at any time by setting " -"`matrix_synapse_enable_authenticated_media: false` in your `vars.yml` " -"configuration file and re-running the playbook." +msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook." msgstr "" #: ../../../CHANGELOG.md:20 @@ -89,89 +62,47 @@ msgid "2024-11-23" msgstr "" #: ../../../CHANGELOG.md:22 -msgid "" -"(Backward Compatibility Break) The playbook now defaults to Valkey, " -"instead of KeyDB" +msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB" msgstr "" #: ../../../CHANGELOG.md:24 -msgid "" -"**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for " -"you before, it will now replace it with [Valkey](https://valkey.io/) (a " -"drop-in alternative). We [previously switched from Redis to KeyDB" -"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" -"instead-of-redis), but Valkey is a better alternative, so we're switching" -" again." +msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again." msgstr "" #: ../../../CHANGELOG.md:26 -msgid "" -"The playbook used to install Redis or KeyDB if services have a need for a" -" Redis-compatible implementation ([enabling worker support for " -"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" -"workers), [enabling Hookshot encryption](docs/configuring-playbook-" -"bridge-hookshot.md#end-to-bridge-encryption), etc.)." +msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)." msgstr "" #: ../../../CHANGELOG.md:28 -msgid "" -"Earlier this year, we switched from Redis to KeyDB - see [(Backward " -"Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" -"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" -"instead-of-redis)." +msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)." msgstr "" #: ../../../CHANGELOG.md:30 -msgid "" -"Because Valkey seems to be a better successor to Redis (than KeyDB) and " -"likely doesn't suffer from [issues like this " -"one](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3544), we now replace KeyDB with Valkey." +msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey." msgstr "" #: ../../../CHANGELOG.md:32 -msgid "" -"Valkey (like KeyDB and Redis in the past) is an implicitly enabled " -"dependency - you don't need custom configuration in `vars.yml` to enable " -"it." +msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it." msgstr "" #: ../../../CHANGELOG.md:34 -msgid "" -"Next time your run the playbook (via the `setup-all` tag), **KeyDB will " -"be automatically uninstalled and replaced with Valkey**. Some Synapse " -"downtime may occur while the switch happens." +msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens." msgstr "" #: ../../../CHANGELOG.md:36 -msgid "" -"Users on `arm32` should be aware that there's **neither a prebuilt " -"`arm32` container image for Valkey**, nor the Valkey role supports self-" -"building yet. Users on this architecture likely don't run Synapse with " -"workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). " -"If Redis is necessary in an `arm32` deployment, disabling Valkey and " -"making the playbook fall back to Redis is possible (see below)." +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)." msgstr "" #: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378 -msgid "" -"**The playbook still supports Redis** and you can keep using Redis (for " -"now) if you'd like, by adding this additional configuration to your " -"`vars.yml` file:" +msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:49 -msgid "" -"**The playbook still supports KeyDB** and you can keep using KeyDB (for " -"now) if you'd like, by adding this additional configuration to your " -"`vars.yml` file:" +msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:59 -msgid "" -"At some point in time in the future, we'll remove both KeyDB and Redis " -"from the playbook, so we recommend that you migrate to Valkey earlier " -"anyway." +msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway." msgstr "" #: ../../../CHANGELOG.md:62 @@ -183,79 +114,35 @@ msgid "HTTP-compression support for Traefik-based setups" msgstr "" #: ../../../CHANGELOG.md:66 -msgid "" -"The playbook now **automatically enables HTTP-compression support** for " -"major services powered by the playbook, like [Cinny](./docs/configuring-" -"playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-" -"client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-" -"hydrogen.md), as well as for Matrix Client-Server and Federation APIs " -"(`matrix.example.com`)." +msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)." msgstr "" #: ../../../CHANGELOG.md:68 -msgid "" -"Other services installed by the playbook are currently not compression-" -"enabled, but may become so over time. This change is rolled out on a per-" -"service basis (as opposed to doing it globally, at the Traefik entrypoint" -" level) to allow certain services or route endpoints which do not behave " -"well when compressed (e.g. [issue 3749](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/issues/3749)) to be excluded from " -"compression." +msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression." msgstr "" #: ../../../CHANGELOG.md:70 -msgid "" -"A long time ago, various services were operating with `gzip`-compression " -"enabled at the nginx level. Since the switch to Traefik (see [Goodbye, " -"`matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md" -"#goodbye-matrix-nginx-proxy-)), all services (with the exception of " -"Matrix APIs for Synapse worker-enabled setups which are powered by " -"`nginx` via `synapse-reverse-proxy-companion`) have been operating " -"without HTTP-compression support." +msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support." msgstr "" #: ../../../CHANGELOG.md:72 -msgid "" -"HTTP-compression is now done via Traefik's " -"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " -"middleware. We use the default configuration for this middleware, which " -"enables `zstd`, `br` and `gzip` support (in this order). This " -"middleware's configuration can be configured via variables in the Traefik" -" role (see " -"`traefik_config_http_middlewares_compression_middleware_options`)." +msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)." msgstr "" #: ../../../CHANGELOG.md:74 -msgid "" -"If you're using your own Traefik reverse-proxy server ([Traefik managed " -"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" -"you)) instead of the playbook's integrated Traefik service, you can " -"benefit from the same by:" +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:" msgstr "" #: ../../../CHANGELOG.md:76 -msgid "" -"defining a " -"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " -"middleware (via the " -"[file](https://doc.traefik.io/traefik/providers/file/) or " -"[Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" +msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" msgstr "" #: ../../../CHANGELOG.md:77 -msgid "" -"setting " -"`matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to" -" `true`" +msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`" msgstr "" #: ../../../CHANGELOG.md:78 -msgid "" -"specifying the middleware's name in " -"`matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g." -" `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-" -"compression-middleware@file`)" +msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)" msgstr "" #: ../../../CHANGELOG.md:80 @@ -263,37 +150,19 @@ msgid "Timeout adjustments for Traefik-based setups" msgstr "" #: ../../../CHANGELOG.md:82 -msgid "" -"The playbook now supports configuring various " -"[transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts)" -" timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the " -"`web`, `web-secure` and `matrix-federation` entrypoints." +msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints." msgstr "" #: ../../../CHANGELOG.md:84 -msgid "" -"If you're using your own Traefik reverse-proxy server ([Traefik managed " -"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" -"you)) instead of the playbook's integrated Traefik service, you may wish " -"to do similar configuration changes to your setup manually." +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually." msgstr "" #: ../../../CHANGELOG.md:86 -msgid "" -"The most interesting of these is the `readTimeout` configuration value " -"(the maximum duration for reading the entire request, including the " -"body), which used to default to `60s`. For large and slowly progressing " -"file uploads, `60s` would often not be enough for the transfer to finish " -"and uploads would end up being interrupted. The playbook now raises the " -"`readTimeout` value to 5 minutes (`300s`) to improve this use-case." +msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case." msgstr "" #: ../../../CHANGELOG.md:88 -msgid "" -"The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` " -"variables (for the `web` entrypoint) cascade to affecting the timeout " -"values for the `web-secure` and `matrix-federation` entrypoints, so you " -"can easily adjust all timeout values using them." +msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them." msgstr "" #: ../../../CHANGELOG.md:90 @@ -301,13 +170,7 @@ msgid "Example of the default timeout values used by the playbook:" msgstr "" #: ../../../CHANGELOG.md:101 -msgid "" -"Alternatively, you may adjust the timeout values for specific entrypoints" -" (like `web-secure` and `matrix-federation`) using dedicated variables " -"(like " -"`traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout`" -" and " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." +msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." msgstr "" #: ../../../CHANGELOG.md:104 @@ -315,39 +178,19 @@ msgid "2024-11-08" msgstr "" #: ../../../CHANGELOG.md:106 -msgid "" -"Support for synapse-admin auto-configuration via /.well-" -"known/matrix/client" +msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client" msgstr "" #: ../../../CHANGELOG.md:108 -msgid "" -"You can administrate your Synapse-powered homeserver using synapse-admin " -"hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the " -"synapse-admin instance would still auto-configure itself correctly for " -"your server by [reading its `/.well-known/matrix/client` " -"file](https://github.com/etkecc/synapse-admin/pull/126)." +msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)." msgstr "" #: ../../../CHANGELOG.md:110 -msgid "" -"The playbook now configures the `/.well-known/matrix/client` file for " -"this by default, injecting into it a `cc.etke.synapse-admin` section that" -" contains the full synapse-admin configuration. This is done even if you " -"don't enable the synapse-admin service in your configuration. The reason " -"for always doing it is to allow users to skip the (small) overhead of " -"self-hosting the non-core synapse-admin service, yet still be able to use" -" it from elsewhere when needed." +msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed." msgstr "" #: ../../../CHANGELOG.md:112 -msgid "" -"If you don't ever plan on using synapse-admin from other servers (besides" -" your own due to [self-hosting synapse-admin](./docs/configuring-" -"playbook-synapse-admin.md)), you **can disable this** `/.well-" -"known/matrix/client` configuration via " -"`matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled:" -" false`" +msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`" msgstr "" #: ../../../CHANGELOG.md:115 @@ -359,11 +202,7 @@ msgid "(BC Break) Postmoogle's variable names need adjustments" msgstr "" #: ../../../CHANGELOG.md:119 -msgid "" -"Due to the recategorization of [Postmoogle](./docs/configuring-playbook-" -"bridge-postmoogle.md) from the bot to the bridge, its variables were " -"renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to " -"adjust your `vars.yml` configuration accordingly." +msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly." msgstr "" #: ../../../CHANGELOG.md:121 @@ -375,38 +214,19 @@ msgid "Support for Matrix Authentication Service" msgstr "" #: ../../../CHANGELOG.md:125 -msgid "" -"The playbook now supports installing and configuring [Matrix " -"Authentication Service](./docs/configuring-playbook-matrix-" -"authentication-service.md) (MAS)." +msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)." msgstr "" #: ../../../CHANGELOG.md:127 -msgid "" -"Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the " -"[Element](https://element.io/) / [Matrix Authentication " -"Service](https://github.com/element-hq/matrix-authentication-service) " -"team for answering our numerous questions about MAS." +msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS." msgstr "" #: ../../../CHANGELOG.md:129 -msgid "" -"This is an **experimental service** and there are **still certain issues " -"with it** (see [Expectations](./docs/configuring-playbook-matrix-" -"authentication-service.md#expectations)). Matrix server administrators " -"should only consider switching if they identify with one or more [reasons" -" to use Matrix Authentication Service](./docs/configuring-playbook-" -"matrix-authentication-service.md#reasons-to-use-matrix-authentication-" -"service). As MAS adoption improves and more services are adjusted to " -"support it, we expect that using MAS will become the norm." +msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm." msgstr "" #: ../../../CHANGELOG.md:131 -msgid "" -"Our [Setting up Matrix Authentication Service](./docs/configuring-" -"playbook-matrix-authentication-service.md) documentation page has more " -"details about this new service, what you might expect from the switch and" -" how you can migrate your existing (Synapse) homeserver setup to MAS." +msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS." msgstr "" #: ../../../CHANGELOG.md:134 @@ -414,23 +234,15 @@ msgid "2024-09-27" msgstr "" #: ../../../CHANGELOG.md:136 -msgid "" -"(BC Break) Postgres & Traefik roles have been relocated and variable " -"names need adjustments" +msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments" msgstr "" #: ../../../CHANGELOG.md:138 -msgid "" -"Various roles have been relocated from the " -"[devture](https://github.com/devture) organization to the [mother-of-all-" -"self-hosting](https://github.com/mother-of-all-self-hosting) " -"organization." +msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" #: ../../../CHANGELOG.md:140 -msgid "" -"Along with the relocation, the `devture_` prefix was dropped from their " -"variable names, so you need to adjust your `vars.yml` configuration." +msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:142 @@ -446,9 +258,7 @@ msgid "`devture_traefik_` -> `traefik_`" msgstr "" #: ../../../CHANGELOG.md:147 -msgid "" -"As always, the playbook would let you know about this and point out any " -"variables you may have missed." +msgid "As always, the playbook would let you know about this and point out any variables you may have missed." msgstr "" #: ../../../CHANGELOG.md:150 @@ -460,36 +270,19 @@ msgid "Support for baibot" msgstr "" #: ../../../CHANGELOG.md:154 -msgid "" -"The playbook now supports installing [baibot](./docs/configuring-" -"playbook-bot-baibot.md) (pronounced bye-bot) - a " -"[Matrix](https://matrix.org/) bot developed by " -"[etke.cc](https://etke.cc/) that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you. 🤖" +msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" msgstr "" #: ../../../CHANGELOG.md:156 -msgid "" -"It supports [OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other" -" [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../CHANGELOG.md:158 -msgid "" -"It's designed as a more private and [✨ " -"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" -"file#-features) alternative to the now-unmaintained [matrix-chatgpt-" -"bot](./docs/configuring-playbook-bot-chatgpt.md)." +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)." msgstr "" #: ../../../CHANGELOG.md:160 -msgid "" -"To get started, see the [Setting up baibot](./docs/configuring-playbook-" -"bot-baibot.md) documentation page." +msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:162 @@ -497,39 +290,19 @@ msgid "Switching synapse-admin to etke.cc's fork" msgstr "" #: ../../../CHANGELOG.md:164 -msgid "" -"The playbook now installs [etke.cc](https://etke.cc/)'s " -"[fork](https://github.com/etkecc/synapse-admin) of [synapse-" -"admin](https://github.com/Awesome-Technologies/synapse-admin) (originally" -" developed by [Awesome-Technologies](https://github.com/Awesome-" -"Technologies)). This fork is a drop-in replacement for the original " -"software." +msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software." msgstr "" #: ../../../CHANGELOG.md:166 -msgid "" -"The creation of the fork has been provoked by users frequently " -"encountering issues with the original synapse-admin software, such as " -"unintentionally deleting their one-and-only admin user account (fixed " -"[here](https://github.com/etkecc/synapse-admin/pull/1) and also " -"contributed upstream [here](https://github.com/Awesome-Technologies" -"/synapse-admin/pull/608) - to no avail for now). Since its inception, [a " -"bunch of other quality-of-life improvements](https://github.com/etkecc" -"/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." +msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." msgstr "" #: ../../../CHANGELOG.md:168 -msgid "" -"If upstream synapse-admin picks up the pace and improves, the etke.cc " -"fork may disappear and the playbook may switch to the original software " -"again. Until that time comes, we believe that etke.cc's fork is the " -"better software to use right now." +msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now." msgstr "" #: ../../../CHANGELOG.md:170 -msgid "" -"If you'd like to switch back to the original synapse-admin software, you " -"can do so by adding the following configuration to your `vars.yml` file:" +msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:183 @@ -541,63 +314,31 @@ msgid "New appservice-double-puppet service for better double-puppeting" msgstr "" #: ../../../CHANGELOG.md:187 -msgid "" -"Mautrix bridges are undergoing large changes as announced in the [August " -"2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) " -"blog post." +msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post." msgstr "" #: ../../../CHANGELOG.md:189 -msgid "" -"The playbook has already upgraded to the rewritten mautrix-slack " -"([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and " -"mautrix-signal " -"([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) " -"bridges." +msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges." msgstr "" #: ../../../CHANGELOG.md:191 -msgid "" -"The newly rewritten bridges do not support double-puppeting via [Shared " -"Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, " -"which has prompted us to switch to the new & better [appservice " -"method](https://docs.mau.fi/bridges/general/double-puppeting.html" -"#appservice-method-new) for double-puppeting. The playbook automates this" -" double-puppeting setup for you if you enable the new [Appservice Double " -"Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." +msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." msgstr "" #: ../../../CHANGELOG.md:193 -msgid "" -"All non-deprecated mautrix bridges in the playbook have been reworked to " -"support double-puppeting via an Appservice. Most bridges still support " -"double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-" -"shared-secret-auth.md), so the playbook supports it too. If only Shared " -"Secret Auth is enabled, double-puppeting will be configured using that " -"method (for the bridges that support it). That said, **Shared Secret Auth" -" double-puppeting is being phased out and we recommend replacing it with " -"the new Appservice method**." +msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**." msgstr "" #: ../../../CHANGELOG.md:195 -msgid "" -"We recommend **enabling double-puppeting via the new Appservice method** " -"by adding the following configuration to your `vars.yml` file:" +msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:201 -msgid "" -"You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-" -"shared-secret-auth.md) enabled. Non-mautrix bridges and other services " -"(e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) " -"may still require it." +msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it." msgstr "" #: ../../../CHANGELOG.md:203 -msgid "" -"When both double-puppeting methods are enabled, the playbook will " -"automatically choose the new and better Appservice method for bridges " -"that support it." +msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it." msgstr "" #: ../../../CHANGELOG.md:206 @@ -609,39 +350,19 @@ msgid "matrix-media-repo now configured for Authenticated Media" msgstr "" #: ../../../CHANGELOG.md:210 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), our matrix-media-repo implementation now " -"automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-" -"repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per " -"[MSC3916](https://github.com/matrix-org/matrix-spec-" -"proposals/pull/3916))." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))." msgstr "" #: ../../../CHANGELOG.md:212 -msgid "" -"If you had never heard of Authenticated Media before, the [Sunsetting " -"unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-" -"unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a" -" good introduction." +msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction." msgstr "" #: ../../../CHANGELOG.md:214 -msgid "" -"This feature is enabled for matrix-media-repo installations by default " -"and will append an additional (matrix-media-repo-generated signing key) " -"to your homeserver's (Synapse or Dendrite) signing key. See the [Signing " -"keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and " -"[Key backup and revoking](./docs/configuring-playbook-matrix-media-" -"repo.md#key-backup-and-revoking) sections of the matrix-media-repo " -"documentation for more details." +msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details." msgstr "" #: ../../../CHANGELOG.md:216 -msgid "" -"If you'd like to avoid this new feature, you can disable it by setting " -"`matrix_media_repo_generate_signing_key: false` in your `vars.yml` " -"configuration file." +msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:219 @@ -653,24 +374,15 @@ msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" msgstr "" #: ../../../CHANGELOG.md:223 -msgid "" -"The playbook now installs [matrix-corporal](https://github.com/devture" -"/matrix-corporal) v3.0.0, which brings support for **power-level " -"management** (thanks to [this PR](https://github.com/devture/matrix-" -"corporal/pull/32))." +msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))." msgstr "" #: ../../../CHANGELOG.md:225 -msgid "" -"This upgrade necessitates configuration policy changes as described in " -"[matrix-corporal's changelog entry](https://github.com/devture/matrix-" -"corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." +msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." msgstr "" #: ../../../CHANGELOG.md:227 -msgid "" -"If you'd like to remain on the old (v2) version of matrix-corporal, you " -"can do so by adding the following configuration to your `vars.yml` file:" +msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:233 @@ -682,21 +394,11 @@ msgid "synapse-usage-exporter support" msgstr "" #: ../../../CHANGELOG.md:237 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook can now set up [synapse-usage-" -"exporter](https://github.com/loelkes/synapse-usage-exporter) - a small " -"[Flask](https://flask.palletsprojects.com)-based webservice which can " -"capture usage statistics from Synapse (via HTTP `PUT`) and then make them" -" available for Prometheus to scrape." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape." msgstr "" #: ../../../CHANGELOG.md:239 -msgid "" -"To learn more see our [Enabling synapse-usage-exporter for Synapse usage " -"statistics](docs/configuring-playbook-synapse-usage-exporter.md) " -"documentation page." +msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:242 @@ -708,19 +410,11 @@ msgid "matrix-alertmanager-receiver support" msgstr "" #: ../../../CHANGELOG.md:246 -msgid "" -"For those wishing to more easily integrate " -"[Prometheus](https://prometheus.io/)' alerting service " -"([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/))" -" with Matrix, the playbook can now set up [matrix-alertmanager-" -"receiver](https://github.com/metio/matrix-alertmanager-receiver)." +msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)." msgstr "" #: ../../../CHANGELOG.md:248 -msgid "" -"See [Setting up Prometheus Alertmanager integration via matrix-" -"alertmanager-receiver](./docs/configuring-playbook-alertmanager-" -"receiver.md) for more details." +msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details." msgstr "" #: ../../../CHANGELOG.md:250 @@ -728,15 +422,7 @@ msgid "Traefik v3 and HTTP/3 are here now" msgstr "" #: ../../../CHANGELOG.md:252 -msgid "" -"**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to " -"the playbook. Mostly everything else worked out of the box. Most people " -"will not have to do any tweaks to their configuration. In addition, " -"[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-" -"enabled for the `web-secure` (port 443) and `matrix-federation` (port " -"`8448`) entrypoints. If you have a firewall in front of your server and " -"you wish to benefit from `HTTP3`, you will need to open the `443` and " -"`8448` UDP ports in it." +msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it." msgstr "" #: ../../../CHANGELOG.md:254 @@ -744,31 +430,15 @@ msgid "Traefik v3" msgstr "" #: ../../../CHANGELOG.md:256 -msgid "" -"The reverse-proxy that the playbook uses by default (Traefik) has " -"recently been upgraded to v3 (see [this blog " -"post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn " -"about its new features). Version 3 includes some small breaking " -"configuration changes requiring a " -"[migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." msgstr "" #: ../../../CHANGELOG.md:258 -msgid "" -"We have **updated the playbook to Traefik v3** (make sure to run `just " -"roles` / `make roles` to get it)." +msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)." msgstr "" #: ../../../CHANGELOG.md:260 -msgid "" -"There were **only minor playbook changes required** to adapt to Traefik " -"v3, and only to the Ansible role for [matrix-media-repo](./docs" -"/configuring-playbook-matrix-media-repo.md) where we changed a few " -"[`PathPrefix` instances to " -"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" -"pathprefix-and-pathregexp), because these instances were using a regular " -"expression instead of a fixed path. For fixed-path values, `PathPrefix` " -"is still the preferred matcher function to use." +msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use." msgstr "" #: ../../../CHANGELOG.md:262 @@ -776,36 +446,15 @@ msgid "**Most people using the playbook should not have to do any changes**." msgstr "" #: ../../../CHANGELOG.md:264 -msgid "" -"If you're using the playbook's Traefik instance to reverse-proxy to some " -"other services of your own (not managed by the playbook), you may wish to" -" review their Traefik labels and make sure they're in line with the " -"[Traefik v2 to v3 migration " -"guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." msgstr "" #: ../../../CHANGELOG.md:266 -msgid "" -"If you've tweaked any of this playbook's `_path_prefix` variables and " -"made them use a regular expression, you will now need to make additional " -"adjustments. The playbook makes extensive use of `PathPrefix()` matchers " -"in Traefik rules and `PathPrefix` does not support regular expressions " -"anymore. To work around it, you may now need to override a whole " -"`_traefik_rule` variable and switch it from [`PathPrefix` to " -"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" -"pathprefix-and-pathregexp)." +msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)." msgstr "" #: ../../../CHANGELOG.md:268 -msgid "" -"If you're not using [matrix-media-repo](./docs/configuring-playbook-" -"matrix-media-repo.md) (the only role we had to tweak to adapt it to " -"Traefik v3), you **may potentially downgrade to Traefik v2** (if " -"necessary) by adding `traefik_verison: v2.11.4` to your configuration. " -"People using `matrix-media-repo` cannot downgrade this way, because " -"`matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing " -"matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that" -" Traefik v2 does not understand." +msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand." msgstr "" #: ../../../CHANGELOG.md:270 @@ -813,36 +462,19 @@ msgid "HTTP/3 is enabled by default" msgstr "" #: ../../../CHANGELOG.md:272 -msgid "" -"In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is " -"no longer considered experimental now. Due to this, **the playbook auto-" -"enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` " -"(port `8448`) entrypoints." +msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints." msgstr "" #: ../../../CHANGELOG.md:274 -msgid "" -"HTTP3 uses the UDP protocol and **the playbook (together with Docker) " -"will make sure that the appropriate ports** (`443` over UDP & `8448` over" -" UDP) **are exposed and whitelisted in your server's firewall**. However," -" **if you have another firewall in front of your server** (as is the case" -" for many cloud providers), **you will need to manually open these UDP " -"ports**." +msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**." msgstr "" #: ../../../CHANGELOG.md:276 -msgid "" -"If you do not open the UDP ports correctly or there is some other issue, " -"clients (browsers, mostly) will fall-back to " -"[HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even " -"[HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." +msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." msgstr "" #: ../../../CHANGELOG.md:278 -msgid "" -"Still, if HTTP/3 cannot function correctly in your setup, it's best to " -"disable advertising support for it (and misleading clients into trying to" -" use HTTP/3)." +msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)." msgstr "" #: ../../../CHANGELOG.md:280 @@ -850,12 +482,7 @@ msgid "To **disable HTTP/3**, you can use the following configuration:" msgstr "" #: ../../../CHANGELOG.md:294 -msgid "" -"If you are using [your own webserver](./docs/configuring-playbook-own-" -"webserver.md) (in front of Traefik), port binding on UDP port `8448` by " -"default due to HTTP/3 is either unnecessary or [may get in the " -"way](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3402). If it does, you can disable it:" +msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:" msgstr "" #: ../../../CHANGELOG.md:307 @@ -867,31 +494,15 @@ msgid "synapse-admin is now restricted to your homeserver's URL by default" msgstr "" #: ../../../CHANGELOG.md:311 -msgid "" -"A new feature introduced in synapse-admin [v0.10.0](https://github.com" -"/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and " -"supported by the playbook since a a few months ago) provides the ability " -"to [restrict its usage to a specific homeserver](https://github.com" -"/Awesome-Technologies/synapse-" -"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" -"#restricting-available-homeserver) (or multiple homeservers)." +msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)." msgstr "" #: ../../../CHANGELOG.md:313 -msgid "" -"The playbook has just started making use of this feature. **From now on, " -"your synapse-admin instance will be restricted to the homeserver you're " -"managing via the playbook**. When configured like this, the *Homeserver " -"URL* field in synapse-admin's web UI changes from a text field to a " -"dropdown having a single value (the URL of your homeserver). This makes " -"usage simpler for most people, as they won't need to manually enter a " -"*Homeserver URL* anymore." +msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore." msgstr "" #: ../../../CHANGELOG.md:315 -msgid "" -"If you'd like **to go back to the old unrestricted behavior**, use the " -"following configuration:" +msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:" msgstr "" #: ../../../CHANGELOG.md:323 @@ -903,58 +514,31 @@ msgid "The URL-prefix for Hookshot generic webhooks has changed" msgstr "" #: ../../../CHANGELOG.md:327 -msgid "" -"Until now, generic Hookshot webhook URLs looked like this: " -"`https://matrix.example.com/hookshot/webhooks/:hookId`." +msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`." msgstr "" #: ../../../CHANGELOG.md:329 -msgid "" -"The `/hookshot/webhooks` common prefix gets stripped by Traefik " -"automatically, so Hookshot only sees the part that comes after " -"(`/:hookId`)." +msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)." msgstr "" #: ../../../CHANGELOG.md:331 -msgid "" -"[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1681), Hookshot started to prefer to handle webhooks at a " -"`/webhook/:hookId` path (instead of directly at `/:hookId`)." +msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)." msgstr "" #: ../../../CHANGELOG.md:333 -msgid "" -"To avoid future problems, we've " -"[reconfigured](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot " -"configuration to use webhook URLs that include `/webhook` in the URL " -"suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of " -"`/hookshot/webhooks/:hookId`). This means that when we strip the common " -"prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to " -"Hookshot, just like recommended." +msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended." msgstr "" #: ../../../CHANGELOG.md:335 -msgid "" -"When generating new webhooks, you should start seeing the new URLs being " -"used." +msgid "When generating new webhooks, you should start seeing the new URLs being used." msgstr "" #: ../../../CHANGELOG.md:337 -msgid "" -"**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new " -"URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your" -" webhooks will not break just yet." +msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet." msgstr "" #: ../../../CHANGELOG.md:339 -msgid "" -"However, **we recommend that you update all your old webhook URLs** " -"(configured in other systems) to include the new `/webhook` path " -"component, so that future Hookshot changes (whenever they come) will not " -"break your webhooks. You don't need to do anything on the Hookshot side -" -" you merely need to reconfigure the remote systems that use your webhook " -"URLs." +msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs." msgstr "" #: ../../../CHANGELOG.md:342 @@ -966,29 +550,15 @@ msgid "The maubot user is now managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:346 -msgid "" -"To make things easier and to be consistent with other roles, the " -"[maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by" -" default) is [now](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3376) automatically created be the playbook." +msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook." msgstr "" #: ../../../CHANGELOG.md:348 -msgid "" -"If you have an existing maubot installation, you will need to specify " -"`matrix_bot_maubot_initial_password` in your `vars.yml` file to make the " -"playbook not complain about it being undefined. Since the bot is already " -"registered in your installation, there's nothing for the playbook to do " -"anyway. In case you don't remember the password you've registered your " -"maubot user account with, you can specify any value for this variable." +msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable." msgstr "" #: ../../../CHANGELOG.md:350 -msgid "" -"If you've registered another username for the bot (other than the " -"recommended default of `bot.maubot`), consider adjusting the " -"`matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: " -"my.maubot.username`)." +msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)." msgstr "" #: ../../../CHANGELOG.md:353 @@ -1000,18 +570,11 @@ msgid "WeChat bridging support" msgstr "" #: ../../../CHANGELOG.md:357 -msgid "" -"Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s " -"[efforts](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3241), the playbook now supports bridging to " -"[WeChat](https://www.wechat.com/) via the [matrix-" -"wechat](https://github.com/duo/matrix-wechat) bridge." +msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge." msgstr "" #: ../../../CHANGELOG.md:359 -msgid "" -"See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-" -"wechat.md) documentation page for getting started." +msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:362 @@ -1019,70 +582,31 @@ msgid "2024-03-26" msgstr "" #: ../../../CHANGELOG.md:364 -msgid "" -"(Backward Compatibility Break) The playbook now defaults to KeyDB, " -"instead of Redis" +msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" msgstr "" #: ../../../CHANGELOG.md:366 -msgid "" -"**TLDR**: if the playbook used installed Redis as a dependency for you " -"before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a " -"drop-in alternative) due to [Redis having changed its " -"license](https://redis.com/blog/redis-adopts-dual-source-available-" -"licensing/)." +msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)." msgstr "" #: ../../../CHANGELOG.md:368 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook now uses " -"[KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), " -"instead of [Redis](https://redis.io/)." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)." msgstr "" #: ../../../CHANGELOG.md:370 -msgid "" -"The playbook used to install Redis (and now installs KeyDB in its place) " -"if services have a need for it ([enabling worker support for " -"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" -"workers), [enabling Hookshot encryption](docs/configuring-playbook-" -"bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly " -"enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." +msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." msgstr "" #: ../../../CHANGELOG.md:372 -msgid "" -"This change is provoked by the fact that [Redis is now \"source " -"available\"](https://redis.com/blog/redis-adopts-dual-source-available-" -"licensing/). According to the Limitations of [the new " -"license](https://redis.com/legal/rsalv2-agreement/) (as best as we " -"understand them, given that we're not lawyers), using Redis in the " -"playbook (even in a commercial FOSS service like " -"[etke.cc](https://etke.cc/)) does not violate the new Redis license. That" -" said, we'd rather neither risk it, nor endorse shady licenses and " -"products that pretend to be free-software. Another high-quality " -"alternative to Redis seems to be " -"[Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly " -"license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-" -"file#readme) is no better than Redis's." +msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's." msgstr "" #: ../../../CHANGELOG.md:374 -msgid "" -"Next time your run the playbook (via the `setup-all` tag), **Redis will " -"be automatically uninstalled and replaced with KeyDB**. Some Synapse " -"downtime may occur while the switch happens." +msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens." msgstr "" #: ../../../CHANGELOG.md:376 -msgid "" -"Users on `arm32` should be aware that there's **neither a prebuilt " -"`arm32` container image for KeyDB**, nor the KeyDB role supports self-" -"building yet. Users on this architecture likely don't run Synapse with " -"workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis" -" is necessary in an `arm32` deployment, disabling KeyDB and making the " -"playbook fall back to Redis is possible (see below)." +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)." msgstr "" #: ../../../CHANGELOG.md:387 @@ -1094,11 +618,7 @@ msgid "Initial work on IPv6 support" msgstr "" #: ../../../CHANGELOG.md:391 -msgid "" -"Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can " -"now enable IPv6 for container networks for various components (roles) via" -" [the `devture_systemd_docker_base_ipv6_enabled` " -"variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." +msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." msgstr "" #: ../../../CHANGELOG.md:393 @@ -1106,17 +626,11 @@ msgid "It should be noted that:" msgstr "" #: ../../../CHANGELOG.md:395 -msgid "" -"Matrix roles (`roles/custom/matrix-*`) respect this variable, but " -"external roles (those defined in `requirements.yml` and installed via " -"`just roles`) do not respect it yet. Additional work is necessary" +msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary" msgstr "" #: ../../../CHANGELOG.md:396 -msgid "" -"changing the variable subsequently may not change existing container " -"networks. Refer to [these " -"instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" +msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" msgstr "" #: ../../../CHANGELOG.md:397 @@ -1128,19 +642,11 @@ msgid "Pantalaimon support" msgstr "" #: ../../../CHANGELOG.md:401 -msgid "" -"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " -"playbook can now install the [Pantalaimon](https://github.com/matrix-" -"org/pantalaimon) E2EE aware proxy daemon for you. It's already possible " -"to integrate it with [Draupnir](docs/configuring-playbook-bot-" -"draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs " -"for details." +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details." msgstr "" #: ../../../CHANGELOG.md:403 -msgid "" -"See our [Setting up Pantalaimon](docs/configuring-playbook-" -"pantalaimon.md) documentation to get started." +msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:406 @@ -1152,25 +658,15 @@ msgid "Support for Draupnir-for-all" msgstr "" #: ../../../CHANGELOG.md:410 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " -"install [Draupnir for all](./docs/configuring-playbook-appservice-" -"draupnir-for-all.md) (aka multi-instance Draupnir running in appservice " -"mode)." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)." msgstr "" #: ../../../CHANGELOG.md:412 -msgid "" -"This is an alternative to [running Draupnir in bot mode](./docs" -"/configuring-playbook-bot-draupnir.md), which is still supported by the " -"playbook." +msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook." msgstr "" #: ../../../CHANGELOG.md:414 -msgid "" -"The documentation page for [Draupnir for all](./docs/configuring-" -"playbook-appservice-draupnir-for-all.md) contains more information on how" -" to install it." +msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it." msgstr "" #: ../../../CHANGELOG.md:417 @@ -1182,44 +678,23 @@ msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridg msgstr "" #: ../../../CHANGELOG.md:421 -msgid "" -"The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-" -"facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-" -"mautrix-instagram.md) bridges are being [superseded by a new " -"bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-" -"meta](https://github.com/mautrix/meta) bridge." +msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge." msgstr "" #: ../../../CHANGELOG.md:423 -msgid "" -"The playbook now supports the new mautrix-meta bridge - a single bridge, " -"which can run in different modes and bridge to Messenger (via " -"[Facebook](https://facebook.com/), Facebook over " -"[Tor](https://www.torproject.org/) or via " -"[Messenger](https://messenger.com/)) and " -"[Instagram](https://instagram.com/). The playbook makes this bridge " -"available via 2 separate Ansible roles, allowing you to easily run 2 " -"instances of mautrix-meta, for bridging to both services at the same " -"time." +msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time." msgstr "" #: ../../../CHANGELOG.md:425 -msgid "" -"If you're using mautrix-facebook or mautrix-instagram right now, **you " -"can still continue using the old bridges, but may wish to change to the " -"new bridge implementations**. See:" +msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:" msgstr "" #: ../../../CHANGELOG.md:427 -msgid "" -"[Setting up Instagram bridging via Mautrix Meta](docs/configuring-" -"playbook-bridge-mautrix-meta-instagram.md)" +msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../CHANGELOG.md:429 -msgid "" -"[Setting up Messenger bridging via Mautrix Meta](docs/configuring-" -"playbook-bridge-mautrix-meta-messenger.md)" +msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)" msgstr "" #: ../../../CHANGELOG.md:431 @@ -1235,44 +710,23 @@ msgid "Much larger Synapse caches and cache auto-tuning enabled by default" msgstr "" #: ../../../CHANGELOG.md:438 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses " -"much larger caches and enables Synapse's [cache auto-tuning " -"functionality](https://matrix-" -"org.github.io/synapse/latest/usage/configuration/config_documentation.html" -"#caches-and-associated-values). This work and the default values used by " -"the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s " -"[Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." msgstr "" #: ../../../CHANGELOG.md:440 -msgid "" -"The playbook has always used a very conservative cache factor " -"(`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK " -"for small and underactive deployments, but is not ideal for larger " -"servers. Paradoxically, a small global cache factor value [does not " -"necessarily decrease RAM usage as a whole](https://github.com/matrix-" -"org/synapse/issues/3939)." +msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" #: ../../../CHANGELOG.md:442 -msgid "" -"The playbook now uses **a 20x larger cache factor** (currently `10`), " -"adjusts a few other cache-related variables, and **enables cache auto-" -"tuning** via the following variables:" +msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:" msgstr "" #: ../../../CHANGELOG.md:444 -msgid "" -"`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to " -"1/8 of total RAM with a cap of 2GB; values are specified in bytes" +msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" #: ../../../CHANGELOG.md:445 -msgid "" -"`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to" -" 1/16 of total RAM with a cap of 1GB; values are specified in bytes" +msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" #: ../../../CHANGELOG.md:446 @@ -1280,16 +734,11 @@ msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" #: ../../../CHANGELOG.md:448 -msgid "" -"These values should be good defaults for most servers, but may change " -"over time as we experiment further." +msgid "These values should be good defaults for most servers, but may change over time as we experiment further." msgstr "" #: ../../../CHANGELOG.md:450 -msgid "" -"Refer to our new [Tuning caches and cache autotuning](docs/maintenance-" -"synapse.md#tuning-caches-and-cache-autotuning) documentation section for " -"more details." +msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details." msgstr "" #: ../../../CHANGELOG.md:453 @@ -1297,37 +746,19 @@ msgid "2024-01-31" msgstr "" #: ../../../CHANGELOG.md:455 -msgid "" -"(Backward-compatibility break) Minor changes necessary for some people " -"serving a static website at the base domain" +msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain" msgstr "" #: ../../../CHANGELOG.md:457 -msgid "" -"This only affects people who are [Serving a static website at the base " -"domain](./docs/configuring-playbook-base-domain-serving.md#serving-a" -"-static-website-at-the-base-domain), but not managing its `index.html` " -"through the playbook." +msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook." msgstr "" #: ../../../CHANGELOG.md:459 -msgid "" -"That is, for people who have " -"`matrix_static_files_file_index_html_enabled: false` in their `vars.yml` " -"configuration, the playbook has a new default behavior. Since the " -"playbook is not managing the `index.html` file, it will default to a more" -" sensible way of handling the base domain - redirecting " -"`https://example.com/` to `https://matrix.example.com/`, instead of " -"serving a 404 page." +msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page." msgstr "" #: ../../../CHANGELOG.md:461 -msgid "" -"If you are managing your static website by yourself (by dropping files " -"into `/matrix/static-files/public` somehow), then you probably don't wish" -" for such redirection to happen. You can disable it by adding " -"`matrix_static_files_container_labels_base_domain_root_path_redirection_enabled:" -" false` to your `vars.yml` configuration file." +msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:464 @@ -1339,45 +770,19 @@ msgid "Support for more efficient (specialized) Synapse workers" msgstr "" #: ../../../CHANGELOG.md:468 -msgid "" -"Thanks to [Charles Wright](https://github.com/cvwright) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook has [received " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3100) for load-balancing the Synapse workload via " -"[specialized workers](./docs/configuring-playbook-synapse.md#specialized-" -"workers) which are supposed to work better than our old [generic " -"workers](./docs/configuring-playbook-synapse.md#generic-workers) " -"implementation." +msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation." msgstr "" #: ../../../CHANGELOG.md:470 -msgid "" -"For now, playbook defaults remain unchanged and the `one-of-each` " -"[workers preset](./docs/configuring-playbook-synapse.md#worker-presets) " -"continues being the default. However, the default may change in the " -"future. If you'd like to remain on this preset even if/when the defaults " -"change, consider explicitly adding `matrix_synapse_workers_preset: one-" -"of-each` to your `vars.yml` configuration." +msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:472 -msgid "" -"Our specialized workers setup is based on recommendations found in [Tom " -"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/index.html). What's special " -"about our new setup is that we try to parse information out of the " -"request (who the user is; which room is being operated on) and try to " -"forward similar requests to the same worker. As an example, this means " -"that once a worker caches some room information, subsequent requests for " -"the same room will be routed to the same worker (which supposedly still " -"has the room's state cached)." +msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)." msgstr "" #: ../../../CHANGELOG.md:474 -msgid "" -"To get started, refer to our [Specialized workers](./docs/configuring-" -"playbook-synapse.md#specialized-workers) documentation section." +msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section." msgstr "" #: ../../../CHANGELOG.md:477 @@ -1389,47 +794,27 @@ msgid "Switching to Element's AGPLv3-licensed Synapse release" msgstr "" #: ../../../CHANGELOG.md:481 -msgid "" -"A few months ago, the [Element](https://element.io/) company has " -"[announced](https://element.io/blog/element-to-adopt-agplv3/) that their " -"work on the Synapse homeserver would no longer be available under the " -"permissive [Apache-2.0 " -"license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" +msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" msgstr "" #: ../../../CHANGELOG.md:483 -msgid "" -"the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software" -" license - the same license that this Ansible playbook has always used" +msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used" msgstr "" #: ../../../CHANGELOG.md:484 -msgid "" -"a proprietary license, for those wishing for Element to [sell them an " -"exception](https://gnu.org/philosophy/selling-exceptions.html) to the " -"AGPLv3 license" +msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license" msgstr "" #: ../../../CHANGELOG.md:486 -msgid "" -"You can also learn more in [this post](https://matrix.org/blog/2023/11/06" -"/future-of-synapse-dendrite/) by the Matrix Foundation." +msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation." msgstr "" #: ../../../CHANGELOG.md:488 -msgid "" -"The change has [already happened](https://element.io/blog/synapse-now-" -"lives-at-github-com-element-hq-synapse/) and the first Synapse release " -"under the new license is here: [v1.99.0](https://github.com/element-" -"hq/synapse/releases/tag/v1.99.0)." +msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)." msgstr "" #: ../../../CHANGELOG.md:490 -msgid "" -"There is no up-to-date alternative Synapse fork right now and this free-" -"software (AGPLv3-licensed) playbook is definitely not against free-" -"software licenses, so we are now switching to the Element-maintained " -"Synapse release." +msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release." msgstr "" #: ../../../CHANGELOG.md:492 @@ -1437,32 +822,19 @@ msgid "**What does this mean to you?**" msgstr "" #: ../../../CHANGELOG.md:494 -msgid "" -"For most home users, it doesn't mean anything. Your installation will " -"continue working as it should and you don't need to do anything." +msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:496 -msgid "" -"For people building commercial products on top of Synapse, they may have " -"to either buy a license exception from Element (from what we hear, the " -"fee depends on the number of monthly-active users on your instance) or " -"they may need to release all related code as free-software (which is what" -" we've been doing at [etke.cc](https://etke.cc/) " -"([here](https://gitlab.com/etke.cc)) all along)." +msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)." msgstr "" #: ../../../CHANGELOG.md:498 -msgid "" -"We're no lawyers and this changelog entry does not aim to give you the " -"best legal advice, so please research on your own!" +msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!" msgstr "" #: ../../../CHANGELOG.md:500 -msgid "" -"If you'd like to continue using the old Apache-2.0-licensed Synapse (for " -"a while longer anyway), the playbook makes it possible by intruducing a " -"new Ansible variable. You can do it like this:" +msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:" msgstr "" #: ../../../CHANGELOG.md:512 @@ -1470,28 +842,11 @@ msgid "Notes:" msgstr "" #: ../../../CHANGELOG.md:514 -msgid "" -"if you had already upgraded Synapse to `v1.99.0` by running this " -"playbook, you will still be able to downgrade to `v1.98.0`, because both " -"releases use the same database schema version (`SCHEMA_COMPAT_VERSION = " -"83` - see [here for v1.98.0](https://github.com/element-" -"hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and" -" [here for v1.99.0](https://github.com/element-" -"hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). " -"More details on Synapse's database schema are available [here](https" -"://element-" -"hq.github.io/synapse/develop/development/database_schema.html). It " -"appears that there are no new database migrations introduced in " -"`v1.99.0`, so going back to the older release is possible. This is not " -"guaranteed to hold true for future Synapse releases, so if you're seeing " -"this early-enough, consider pinning the version and organization before " -"re-running the playbook and getting upgraded to the latest version" +msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version" msgstr "" #: ../../../CHANGELOG.md:516 -msgid "" -"running an outdated homeserver exposes you to security issues and " -"incompatibilities. Only consider doing this as a short-term solution." +msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution." msgstr "" #: ../../../CHANGELOG.md:518 @@ -1503,13 +858,7 @@ msgid "`Draupnir` has been relicensed to AFL-3.0" msgstr "" #: ../../../CHANGELOG.md:522 -msgid "" -"As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) " -"Draupnir changed its licence to AFL-3.0 from the CSL licence. This change" -" affects playbook users who could not run Draupnir under the old license " -"restrictions. The new license is considerably less restrictive and is OSI" -" approved. Draupnir version v1.86.0 and later are covered by this license" -" change." +msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change." msgstr "" #: ../../../CHANGELOG.md:524 @@ -1521,15 +870,7 @@ msgid "Goodbye, `matrix-nginx-proxy` 🪦" msgstr "" #: ../../../CHANGELOG.md:528 -msgid "" -"**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component " -"are now gone. This brought about many other internal changes (and " -"security improvements), so setups may need minor adjustments or suffer " -"some (temporary) breakage. People who have been on the Traefik-native " -"setup may upgrade without much issues. Those running their own Traefik " -"instance may need minor changes. People who have been postponing the " -"migration away from `matrix-nginx-proxy` (for more than a year already!) " -"will now finally need to do something about it." +msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it." msgstr "" #: ../../../CHANGELOG.md:530 @@ -1537,26 +878,11 @@ msgid "Backstory on `matrix-nginx-proxy`" msgstr "" #: ../../../CHANGELOG.md:532 -msgid "" -"We gather here today to celebrate the loss of a once-beloved component in" -" our stack - `matrix-nginx-proxy`. It's been our " -"[nginx](https://nginx.org/)-based reverse-proxy of choice since the " -"[first commit](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7" -" years ago." +msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago." msgstr "" #: ../../../CHANGELOG.md:534 -msgid "" -"For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy " -"in our setup (doing SSL termination, etc.). After [transitioning to " -"Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-" -"nginx-proxy` took a step back. Nevertheless, since it was so ingrained " -"into the playbook, it still remained in use - even if only internally. " -"Despite our warnings of its imminent death, many of you have indubitably " -"continued to use it instead of Traefik. Its suffering continued for too " -"long, because it served many different purposes and massive effort was " -"required to transition them to others." +msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others." msgstr "" #: ../../../CHANGELOG.md:536 @@ -1568,82 +894,43 @@ msgid "an [nginx](https://nginx.org/)-based reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:539 -msgid "" -"an Ansible role organizing the work of " -"[certbot](https://certbot.eff.org/) - retrieving free [Let's " -"Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-" -"proxy` and for the [Coturn TURN server](./docs/configuring-playbook-" -"turn.md)" +msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)" msgstr "" #: ../../../CHANGELOG.md:540 -msgid "" -"a central component for reverse-proxying to the [long list of " -"services](./docs/configuring-playbook.md) supported by the playbook. As " -"such, it became a dependency that all these services had to inject " -"themselves into during runtime" +msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime" msgstr "" #: ../../../CHANGELOG.md:541 -msgid "" -"an intermediary through which addons (bridges, bots) communicated with " -"the homeserver. Going through an intermediary (instead of directly " -"talking to the homeserver) is useful when certain components (like " -"[matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or " -"[matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are " -"enabled, because it lets these services \"steal routes\" from the " -"homeserver" +msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver" msgstr "" #: ../../../CHANGELOG.md:542 -msgid "" -"a webserver for serving the `/.well-known/matrix` static files (generated" -" by the `matrix-base` role until now)" +msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)" msgstr "" #: ../../../CHANGELOG.md:543 -msgid "" -"a webserver [serving your base domain](./docs/configuring-playbook-base-" -"domain-serving.md) (and also generating the `index.html` page for it)" +msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)" msgstr "" #: ../../../CHANGELOG.md:544 -msgid "" -"a central component providing global [HTTP Basic " -"Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) " -"password-protection for all `/metrics` endpoints when metrics were " -"exposed publicly for consumption from a remote Prometheus server" +msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server" msgstr "" #: ../../../CHANGELOG.md:546 -msgid "" -"Talk about a jack of all trades! The [UNIX " -"philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker " -"container philosophy) of \"do one thing and do it well\" had been " -"severely violated for too long." +msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long." msgstr "" #: ../../../CHANGELOG.md:548 -msgid "" -"On a related note, we also had a large chain of reverse-proxies in the " -"mix. In the worst case, it was something like this: (Traefik -> `matrix-" -"nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-" -"reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." +msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." msgstr "" #: ../../../CHANGELOG.md:550 -msgid "" -"Due to complexity and the playbook's flexibility (trying to accommodate a" -" mix of tens of components), many layers of indirection were necessary. " -"We do like reverse-proxies, but.. not quite enough to enjoy going through" -" a chain of ~4 of them before reaching the target service." +msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service." msgstr "" #: ../../../CHANGELOG.md:552 -msgid "" -"After **a ton of work** in the last weeks (200+ commits, which changed " -"467 files - 8684 insertions and 8913 deletions), **we're finally saying " -"goodbye** to `matrix-nginx-proxy`." +msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`." msgstr "" #: ../../../CHANGELOG.md:554 @@ -1655,21 +942,11 @@ msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." msgstr "" #: ../../../CHANGELOG.md:558 -msgid "" -"In most cases, there's only Traefik and all services being registered " -"directly with it. When [Synapse workers](./docs/configuring-playbook-" -"synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-" -"reverse-proxy-companion` remains as an extra reverse-proxy that requests " -"go through (for load-balancing to the correct Synapse worker), but in all" -" other cases services are exposed directly." +msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly." msgstr "" #: ../../../CHANGELOG.md:560 -msgid "" -"This reduces \"network\" hops (improving performance) and also decreases " -"the number of components (containers). Each Ansible role in our setup is " -"now independent and doesn't need to interact with other roles during " -"runtime." +msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime." msgstr "" #: ../../../CHANGELOG.md:562 @@ -1677,59 +954,23 @@ msgid "Traefik now has an extra job" msgstr "" #: ../../../CHANGELOG.md:564 -msgid "" -"Previously, **Traefik had a single purpose** - being the main reverse-" -"proxy. It was either front-most (terminating SSL, etc.) or you were " -"[fronting Traefik with your own other reverse-proxy](./docs/configuring-" -"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" -"webserver-with-another-reverse-proxy). In any case - it had this central " -"(yet decentralized) job." +msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job." msgstr "" #: ../../../CHANGELOG.md:566 -msgid "" -"Now, **Traefik has one more role** - it serves as an intermediary which " -"allows addon services (bridges, bots, etc.) to communicate with the " -"homeserver. As mentioned above, such an intermediary service is not " -"strictly necessary in all kinds of setups, but more complex setups " -"(including [matrix-media-repo](./docs/configuring-playbook-matrix-media-" -"repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-" -"corporal.md)) benefit from it." +msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it." msgstr "" #: ../../../CHANGELOG.md:568 -msgid "" -"To perform this new role, Traefik now has a new internal " -"[entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called " -"`matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, " -"Synapse and even `matrix-synapse-reverse-proxy-companion`) and " -"homeserver-related core services ([matrix-media-repo](./docs/configuring-" -"playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-" -"playbook-matrix-corporal.md) and potentially others) register their " -"routes (using [container labels](https://docs.docker.com/config/labels-" -"custom-metadata/)) not only on the public entrypoints (`web-secure`, " -"`matrix-federation`), but also on this new internal entrypoint." +msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint." msgstr "" #: ../../../CHANGELOG.md:570 -msgid "" -"Doing so, services can contact Traefik on this entrypoint's dedicated " -"port (the URL defaults to `http://matrix-traefik:8008`) and reach the " -"homeserver Client-Server API as they expect. Internally, Traefik takes " -"care of the routing to the correct service." +msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service." msgstr "" #: ../../../CHANGELOG.md:572 -msgid "" -"We've also considered keeping it simple and having services talk to the " -"homeserver over the public internet (e.g. `https://matrix.example.com`) " -"thus reusing all existing Traefik routing labels. In this scenario, " -"performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to" -" TLS and networking overhead. The need for fast internal communication " -"(via the new internal non-TLS-enabled Traefik entrypoint) is definitely " -"there. In our benchmarks, Traefik even proved more efficient than nginx " -"at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out " -"of ~1400 rps when talking to the Synapse homeserver directly)." +msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)." msgstr "" #: ../../../CHANGELOG.md:574 @@ -1737,54 +978,27 @@ msgid "Traefik serving this second purpose has a few downsides:" msgstr "" #: ../../../CHANGELOG.md:576 -msgid "" -"Traefik becomes a runtime dependency for all homeserver-dependant " -"container services" +msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services" msgstr "" #: ../../../CHANGELOG.md:577 -msgid "" -"all homeserver-dependant services now need to be connected to the " -"`traefik` container network, even if they don't need public internet " -"exposure" +msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure" msgstr "" #: ../../../CHANGELOG.md:579 -msgid "" -"Despite these downsides (which the playbook manages automatically), we " -"believe it's still a good compromise given the amount of complexity it " -"eliminates and the performance benefits it yields. One alternative we've " -"[considered](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary " -"service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both " -"had much higher complexity (one more component in the mix; duplication of" -" effort to produce nginx-compatible route definitions for it) and " -"slightly worse performance (see above)." +msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)." msgstr "" #: ../../../CHANGELOG.md:581 -msgid "" -"People running the default Traefik setup do not need to do anything to " -"make Traefik take on this extra job. Your Traefik configuration will be " -"updated automatically." +msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically." msgstr "" #: ../../../CHANGELOG.md:583 -msgid "" -"**People runnning their own Traefik reverse-proxy need to do [minor " -"adjustments](#people-managing-their-own-traefik-instance-need-to-do-" -"minor-changes)**, as described in the section below." +msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below." msgstr "" #: ../../../CHANGELOG.md:585 -msgid "" -"You may disable Traefik acting as an intermediary by explicitly setting " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled`" -" to `false`. Services would then be configured to talk to the homeserver " -"directly, giving you a slight performance boost and a \"simpler\" Traefik" -" setup. However, such a configuration is less tested and will cause " -"troubles, especially if you enable more services (like `matrix-media-" -"repo`, etc.) in the future. As such, it's not recommended." +msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended." msgstr "" #: ../../../CHANGELOG.md:587 @@ -1792,47 +1006,23 @@ msgid "People managing their own Traefik instance need to do minor changes" msgstr "" #: ../../../CHANGELOG.md:589 -msgid "" -"This section is for people [managing their own Traefik instance on the " -"Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-" -"managed-by-you). Those [using Traefik managed by the playbook](./docs" -"/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) " -"don't need to do any changes." +msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes." msgstr "" #: ../../../CHANGELOG.md:591 -msgid "" -"Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), " -"you need to adapt your configuration to add the additional `matrix-" -"internal-matrix-client-api` entrypoint and potentially configure the " -"`matrix_playbook_reverse_proxy_container_network` variable. See the " -"[Traefik managed by you](./docs/configuring-playbook-own-webserver.md" -"#traefik-managed-by-you) documentation section for more details." +msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details." msgstr "" #: ../../../CHANGELOG.md:593 -msgid "" -"People fronting Traefik with another reverse proxy need to do minor " -"changes" +msgid "People fronting Traefik with another reverse proxy need to do minor changes" msgstr "" #: ../../../CHANGELOG.md:595 -msgid "" -"We've already previously mentioned that you need to do some minor " -"[configuration changes related to `traefik_additional_entrypoints_auto" -"`](#backward-compatibility-configuration-changes-required-for-people-" -"fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy)." +msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." msgstr "" #: ../../../CHANGELOG.md:597 -msgid "" -"If you don't do these changes (switching from " -"`traefik_additional_entrypoints_auto` to multiple other variables), your " -"Traefik setup will not automatically receive the new `matrix-internal-" -"matrix-client-api` Traefik entrypoint and Traefik would not be able to " -"perform [its new duty of connecting addons with the homeserver](#traefik-" -"now-has-an-extra-job)." +msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)." msgstr "" #: ../../../CHANGELOG.md:599 @@ -1840,16 +1030,11 @@ msgid "Supported reverse proxy types are now fewer" msgstr "" #: ../../../CHANGELOG.md:601 -msgid "" -"This section is for people using a more custom reverse-proxy setup - " -"those having `matrix_playbook_reverse_proxy_type` set to a value " -"different than the default (`playbook-managed-traefik`)." +msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)." msgstr "" #: ../../../CHANGELOG.md:603 -msgid "" -"Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to" -" 7 different values to accommodate various reverse-proxy setups." +msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups." msgstr "" #: ../../../CHANGELOG.md:605 @@ -1857,59 +1042,35 @@ msgid "The complexity of this is too high, so we only support 3 values right now msgstr "" #: ../../../CHANGELOG.md:607 -msgid "" -"(the default) `playbook-managed-traefik`, when you're [using Traefik " -"managed by the playbook](./docs/configuring-playbook-own-webserver.md" -"#traefik-managed-by-the-playbook)" +msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)" msgstr "" #: ../../../CHANGELOG.md:608 -msgid "" -"`other-traefik-container`, when you're [managing your own Traefik " -"instance on the Matrix server](./docs/configuring-playbook-own-" -"webserver.md#traefik-managed-by-you)" +msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)" msgstr "" #: ../../../CHANGELOG.md:609 -msgid "" -"`none`, when you wish for [no reverse-proxy integration to be done at " -"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" -"on-the-matrix-side-at-all)" +msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)" msgstr "" #: ../../../CHANGELOG.md:611 -msgid "" -"The `none` value is not recommended and may not work adequately, due to " -"lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-" -"extra-job) in our setup." +msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup." msgstr "" #: ../../../CHANGELOG.md:613 -msgid "" -"**Previous values that are now gone** (and the playbook would report them" -" as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, " -"`other-on-same-host` and `other-on-another-host`." +msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`." msgstr "" #: ../../../CHANGELOG.md:615 -msgid "" -"If you were using these values as a way to stay away from Traefik, you " -"now have 2 options:" +msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:" msgstr "" #: ../../../CHANGELOG.md:617 -msgid "" -"(recommended) [Fronting Traefik with another reverse-proxy](./docs" -"/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-" -"proxy-webserver-with-another-reverse-proxy)" +msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)" msgstr "" #: ../../../CHANGELOG.md:618 -msgid "" -"(not recommended) [Using no reverse-proxy on the Matrix side at " -"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" -"on-the-matrix-side-at-all) and reverse-proxying to each and every service" -" manually" +msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually" msgstr "" #: ../../../CHANGELOG.md:620 @@ -1917,49 +1078,27 @@ msgid "Container networking changes" msgstr "" #: ../../../CHANGELOG.md:622 -msgid "" -"Now that `matrix-nginx-proxy` is not in the mix, it became easier to " -"clear out some other long-overdue technical debt." +msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt." msgstr "" #: ../../../CHANGELOG.md:624 -msgid "" -"Since the very beginning of this playbook, all playbook services were " -"connected to a single (shared) `matrix` container network. Later on, some" -" additional container networks appeared, but most services (database, " -"etc.) still remained in the `matrix` container network. This meant that " -"any random container in this network could try to talk (or attack) the " -"Postgres database operating in the same `matrix` network." +msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network." msgstr "" #: ../../../CHANGELOG.md:626 -msgid "" -"Moving components (especially the database) into other container networks" -" was difficult - it required changes to many other components to ensure " -"correct connectivity." +msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity." msgstr "" #: ../../../CHANGELOG.md:628 -msgid "" -"All the hard work has been done now. We've added much more isolation " -"between services by splitting them up into separate networks (`matrix-" -"homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, " -"etc). Components are only joined to the networks they need and should " -"(for the most part) not be able to access unrelated things." +msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things." msgstr "" #: ../../../CHANGELOG.md:630 -msgid "" -"Carrying out these container networking changes necessitated modifying " -"many components, so **we're hoping not too many bugs were introduced in " -"the process**." +msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**." msgstr "" #: ../../../CHANGELOG.md:632 -msgid "" -"We've refrained from creating too many container networks (e.g. one for " -"each component), to avoid exhausting Docker's default network pool and " -"contaminating the container networks list too much." +msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much." msgstr "" #: ../../../CHANGELOG.md:634 @@ -1967,44 +1106,23 @@ msgid "Metrics exposure changes" msgstr "" #: ../../../CHANGELOG.md:636 -msgid "" -"This section is for people who are exposing monitoring metrics publicly, " -"to be consumed by an external Prometheus server." +msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server." msgstr "" #: ../../../CHANGELOG.md:638 -msgid "" -"Previously, `matrix-nginx-proxy` was potentially password-protecting all " -"`/metrics/*` endpoints with the same username and password (specified as " -"plain-text in your `vars.yml` configuration file)." +msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)." msgstr "" #: ../../../CHANGELOG.md:640 -msgid "" -"From now on, there are new variables for doing roughly the same - " -"`matrix_metrics_exposure_enabled`, " -"`matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & " -"Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for" -" details." +msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details." msgstr "" #: ../../../CHANGELOG.md:642 -msgid "" -"`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now," -" each role provides its own metrics exposure and protection by " -"registering with Traefik. Nevertheless, all roles are wired (via playbook" -" configuration in `group_vars/matrix_servers`) to obey these new " -"`matrix_metrics_exposure_*` variables. We've eliminated the " -"centralization, but have kept the ease of use. Now, you can also do per-" -"service password-protection (with different credentials), should you need" -" to do that for some reason." +msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason." msgstr "" #: ../../../CHANGELOG.md:644 -msgid "" -"The playbook will tell you about all variables that you need to migrate " -"during runtime, so rest assured - you shouldn't be able to miss anything!" +msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!" msgstr "" #: ../../../CHANGELOG.md:646 @@ -2012,30 +1130,15 @@ msgid "Matrix static files" msgstr "" #: ../../../CHANGELOG.md:648 -msgid "" -"As mentioned above, static files like `/.well-known/matrix/*` or your " -"base domain's `index.html` file (when [serving the base domain via the " -"Matrix server](./docs/configuring-playbook-base-domain-serving.md) was " -"enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` " -"roles and put into a `/matrix/static-files` directory on the server. Then" -" `matrix-nginx-proxy` was serving all these static files." +msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files." msgstr "" #: ../../../CHANGELOG.md:650 -msgid "" -"All of this has been extracted into a new `matrix-static-files` Ansible " -"role that's part of the playbook. The static files generated by this new " -"role still live at roughly the same place (`/matrix/static-files/public` " -"directory, instead of `/matrix/static-files`)." +msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)." msgstr "" #: ../../../CHANGELOG.md:652 -msgid "" -"The playbook will migrate and update the `/.well-known/matrix/*` files " -"automatically but not your own files in `nginx-proxy/data/matrix-domain/`" -" you will need to back these up yourself otherwise they will be lost. It " -"will also warn you about usage of old variable names, so you can adapt to" -" the new names." +msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names." msgstr "" #: ../../../CHANGELOG.md:654 @@ -2043,54 +1146,27 @@ msgid "A note on performance" msgstr "" #: ../../../CHANGELOG.md:656 -msgid "" -"Some of you have been voicing their concerns (for a long time) about " -"Traefik being too slow and nginx being better." +msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better." msgstr "" #: ../../../CHANGELOG.md:658 -msgid "" -"Some online benchmarks support this by demonstrating slightly higher SSL-" -"termination performance in favor of nginx. The upcoming Traefik v3 " -"release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-" -"traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL " -"performance by some 20%, but that still ends up being somewhat slower " -"than nginx." +msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx." msgstr "" #: ../../../CHANGELOG.md:660 -msgid "" -"We believe that using Traefik provides way too many benefits to worry " -"about this minor performance impairment." +msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment." msgstr "" #: ../../../CHANGELOG.md:662 -msgid "" -"The heaviest part of running a Matrix homeserver is all the slow and " -"potentially inefficient things the homeserver (e.g. Synapse) is doing. " -"These things affect performance much more than whatever reverse-proxy is " -"in front. Your server will die the same way by joining the famously large" -" **Matrix HQ** room, no matter which reverse-proxy you put in front." +msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front." msgstr "" #: ../../../CHANGELOG.md:664 -msgid "" -"Even our previously mentioned benchmarks (yielding ~1300 rps) are " -"synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-" -"use does much more than this." +msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this." msgstr "" #: ../../../CHANGELOG.md:666 -msgid "" -"If this is still not convincing enough for you and you want the best " -"possible performance, consider [Fronting Traefik with another reverse-" -"proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-" -"integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus " -"having the slowest part - SSL termination - happen elsewhere) or [Using " -"no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-" -"own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The " -"playbook will not get in your way of doing that, but these options may " -"make your life much harder. Performance comes at a cost, after all." +msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all." msgstr "" #: ../../../CHANGELOG.md:668 @@ -2098,74 +1174,39 @@ msgid "Migration procedure" msgstr "" #: ../../../CHANGELOG.md:670 -msgid "" -"The updated playbook will automatically perform some migration tasks for " -"you:" +msgid "The updated playbook will automatically perform some migration tasks for you:" msgstr "" #: ../../../CHANGELOG.md:672 -msgid "" -"It will stop and remove the `matrix-nginx-proxy` systemd service and " -"container for you. This behavior cannot be disabled. It's essential that " -"this service gets stopped, because it remaining running (and having " -"container labels) may confuse Traefik as to where to route HTTP requests." +msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests." msgstr "" #: ../../../CHANGELOG.md:674 -msgid "" -"It will delete the `/matrix/nginx-proxy` directory and all files within " -"it. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: " -"false` to your `vars.yml` configuration file. Doing so will leave its " -"data around." +msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around." msgstr "" #: ../../../CHANGELOG.md:676 -msgid "" -"It will delete the `/matrix/ssl` directory and all files within it. You " -"can disable this behavior by adding " -"`matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to " -"your `vars.yml` configuration file. If you have some important " -"certificates there for some reason, take them out or temporarily disable " -"removal of these files until you do." +msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do." msgstr "" #: ../../../CHANGELOG.md:678 -msgid "" -"It will tell you about all variables (`matrix_nginx_proxy_*` and many " -"others - even from other roles) that have changed during this large " -"nginx-elimination upgrade. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled:" -" false` to your `vars.yml` configuration file." +msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:680 -msgid "" -"It will tell you about any leftover `matrix_nginx_proxy_*` variables in " -"your `vars.yml` file. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled:" -" false` to your `vars.yml` configuration file." +msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:682 -msgid "" -"It will tell you about any leftover `matrix_ssl_*` variables in your " -"`vars.yml` file. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: " -"false` to your `vars.yml` configuration file." +msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:684 -msgid "" -"We don't recommend changing these variables and suppressing warnings, " -"unless you know what you're doing." +msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing." msgstr "" #: ../../../CHANGELOG.md:686 -msgid "" -"**Most people should just upgrade as per-normal**, bearing in mind that a" -" lot has changed and some issues may arise. The playbook would guide you " -"through renamed variables automatically." +msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically." msgstr "" #: ../../../CHANGELOG.md:688 @@ -2173,18 +1214,11 @@ msgid "Conclusion" msgstr "" #: ../../../CHANGELOG.md:690 -msgid "" -"Thousands of lines of code were changed across hundreds of files. All " -"addons (bridges, bots) were rewired in terms of container networking and " -"in terms of how they reach the homeserver." +msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver." msgstr "" #: ../../../CHANGELOG.md:692 -msgid "" -"I don't actively use all the ~100 components offered by the playbook (no " -"one does), nor do I operate servers exercising all edge-cases. As such, " -"issues may arise. Please have patience and report (or try to fix) these " -"issues!" +msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!" msgstr "" #: ../../../CHANGELOG.md:695 @@ -2192,43 +1226,23 @@ msgid "2024-01-14" msgstr "" #: ../../../CHANGELOG.md:697 -msgid "" -"(Backward Compatibility) Configuration changes required for people " -"fronting the integrated reverse-proxy webserver with another reverse-" -"proxy" +msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:699 -msgid "" -"If you're on the default setup (using the Traefik reverse-proxy as " -"installed by the playbook), you don't need to do anything." +msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:701 -msgid "" -"People who are [Fronting the integrated Traefik reverse-proxy webserver " -"with another reverse-proxy](./docs/configuring-playbook-own-webserver.md" -"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy), as per our previous instructions are redefining " -"`traefik_additional_entrypoints_auto` in their `vars.yml` configuration." +msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:703 -msgid "" -"Such a full variable redefinion is intrustive, because it prevents the " -"playbook from injecting additional entrypoints into the Traefik " -"webserver. In the future, the playbook may have a need to do so." +msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so." msgstr "" #: ../../../CHANGELOG.md:705 -msgid "" -"For this reason, we no longer recommend completely redefining " -"`traefik_additional_entrypoints_auto`. The playbook now defines [various " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` " -"variables in the `defaults/main.yml` file](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-" -"base/defaults/main.yml) of the `matrix-base` role which can be used as a " -"safer alternative to `traefik_additional_entrypoints_auto`." +msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`." msgstr "" #: ../../../CHANGELOG.md:707 @@ -2236,12 +1250,7 @@ msgid "Adapt your configuration as seen below:" msgstr "" #: ../../../CHANGELOG.md:740 -msgid "" -"Also, feel free to read the [Fronting the integrated Traefik reverse-" -"proxy webserver with another reverse-proxy](./docs/configuring-playbook-" -"own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-" -"another-reverse-proxy) documentation section again for additional " -"details." +msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details." msgstr "" #: ../../../CHANGELOG.md:743 @@ -2249,87 +1258,43 @@ msgid "2024-01-13" msgstr "" #: ../../../CHANGELOG.md:745 -msgid "" -"matrix-reminder-bot update with more secure (backward-incompatible) " -"default settings" +msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings" msgstr "" #: ../../../CHANGELOG.md:747 -msgid "" -"**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453" -"/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs" -"/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By " -"default, like other bridges/bots managed by the playbook, it will only " -"provide its services to users of your own server (not to anyone, even " -"across the Matrix Federation). If that's fine, there's nothing you need " -"to do." +msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do." msgstr "" #: ../../../CHANGELOG.md:749 -msgid "" -"Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-" -"matrix-reminder-bot.md) has been picked up by [Kim " -"Brose](https://github.com/HarHarLinks) and " -"[@svierne](https://github.com/svierne)." +msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)." msgstr "" #: ../../../CHANGELOG.md:751 -msgid "" -"Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-" -"reminder-bot/releases/tag/v0.3.0) release is out. The new version is now " -"available for the ARM64 architecture, so playbook users on this " -"architecture will no longer need to wait for [self-building](./docs/self-" -"building.md) to happen." +msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen." msgstr "" #: ../../../CHANGELOG.md:753 -msgid "" -"The new version also comes with new `allowlist` and `blocklist` settings," -" which make it possible to restrict who can use the bot. Previously " -"anyone, even across the Matrix Federation could talk to it and schedule " -"reminders." +msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders." msgstr "" #: ../../../CHANGELOG.md:755 -msgid "" -"The playbook defaults all bridges and bots (where possible) to only be " -"exposed to users of the current homeserver, not users across federation. " -"Thanks to the new version of this bot making such a restriction possible," -" we're now making use of it. The playbook (via its " -"`group_vars/matrix_servers` file) automatically enables the `allowlist` " -"(`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures" -" it in such a way " -"(`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to " -"restrict the bot to your homeserver's users." +msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users." msgstr "" #: ../../../CHANGELOG.md:757 -msgid "" -"If you need **to undo or tweak these security improvements**, you can " -"change your `vars.yml` file to:" +msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:" msgstr "" #: ../../../CHANGELOG.md:759 -msgid "" -"disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled:" -" false`), making the bot allow usage by anyone, anywhere" +msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere" msgstr "" #: ../../../CHANGELOG.md:761 -msgid "" -"inject additional allowed servers or users by adding **additional** (on " -"top of the default allowlist in " -"`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes " -"in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list " -"variable (see the [syntax reference](https://github.com/anoadragon453" -"/matrix-reminder-" -"bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" +msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" msgstr "" #: ../../../CHANGELOG.md:763 -msgid "" -"override the default allowlist (in the `group_vars/matrix_servers` file) " -"by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" +msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" msgstr "" #: ../../../CHANGELOG.md:766 @@ -2341,17 +1306,11 @@ msgid "matrix-mailer has been replaced by the exim-relay external role" msgstr "" #: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410 -msgid "" -"We're continuing our effort to make [the playbook use external roles for " -"some things](#the-playbook-now-uses-external-roles-for-some-things), so " -"as to avoid doing everything ourselves and to facilitate code re-use." +msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use." msgstr "" #: ../../../CHANGELOG.md:772 -msgid "" -"The `matrix-mailer` role has been moved to its own repository ([ansible-" -"role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-" -"role-exim-relay)) that this playbook now includes." +msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes." msgstr "" #: ../../../CHANGELOG.md:774 @@ -2367,11 +1326,7 @@ msgid "update your roles (run `just roles` or `make roles`)" msgstr "" #: ../../../CHANGELOG.md:778 -msgid "" -"update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to " -"`exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> " -"`exim_relay_sender_address`). If you find none, it means you're using the" -" default configuration and your migraiton job is even simpler." +msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler." msgstr "" #: ../../../CHANGELOG.md:779 @@ -2379,10 +1334,7 @@ msgid "re-run the playbook (`install-all` or `setup-all`)" msgstr "" #: ../../../CHANGELOG.md:781 -msgid "" -"The playbook will take care of stopping the old `matrix-mailer` systemd " -"service, relocating its directory and restarting it under the new name " -"(`matrix-exim-relay.service`)." +msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)." msgstr "" #: ../../../CHANGELOG.md:784 @@ -2394,25 +1346,15 @@ msgid "mautrix-signal now powered by the new Go-based bridge" msgstr "" #: ../../../CHANGELOG.md:788 -msgid "" -"The old Python-based [mautrix-signal](https://github.com/mautrix/signal) " -"bridge is no longer maintained upstream. It's also known to have issues " -"linking new devices." +msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices." msgstr "" #: ../../../CHANGELOG.md:790 -msgid "" -"It seems like the path forward is to switch to the new mautrix-signal " -"bridge written in Golang, which we did thanks to [PR " -"#3031](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." +msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." msgstr "" #: ../../../CHANGELOG.md:792 -msgid "" -"The playbook should **automatically migrate your mautrix-signal " -"installation to the new bridge code**. You will **need to relink all your" -" devices** to continue your bridged conversations." +msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations." msgstr "" #: ../../../CHANGELOG.md:795 @@ -2424,53 +1366,23 @@ msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" msgstr "" #: ../../../CHANGELOG.md:799 -msgid "" -"**TDLR**: if your Matrix server is federating (which it mostly likely is," -" unless you've [disabled federation](docs/configuring-playbook-" -"federation.md#disabling-federation)), your public rooms will not only be " -"joinable across federation (as they've always been), but from now on will" -" be discoverable (made available as a list across federation). We're " -"changing this by flipping the value for Synapse's " -"`allow_public_rooms_over_federation` setting to `true`, going against the" -" upstream default. Servers that disable federation are not affected. " -"Servers that have public rooms which are not published to the room " -"directory are also not affected." +msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected." msgstr "" #: ../../../CHANGELOG.md:801 -msgid "" -"We generally try to stick to the default configuration for Synapse (and " -"all other components), unless these defaults seem wrong or harmful. One " -"such previous case from a few months ago was us [Enabling " -"`forget_rooms_on_leave` by default for Synapse](#enabling-" -"forget_rooms_on_leave-by-default-for-synapse) - the default value was " -"making Synapse more wasteful of resources by default." +msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default." msgstr "" #: ../../../CHANGELOG.md:803 -msgid "" -"Today, we're going against upstream defaults again and flipping the " -"`allow_public_rooms_over_federation` configuration option to `true`. This" -" way, public rooms on your server will be made discoverable by others via" -" federation, using the [`GET /_matrix/federation/v1/publicRooms` of the " -"Server-Server API](https://spec.matrix.org/v1.8/server-server-" -"api/#get_matrixfederationv1publicrooms)." +msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)." msgstr "" #: ../../../CHANGELOG.md:805 -msgid "" -"The upstream Synapse default is `false` (disabled), so that public rooms " -"are not exposed for other servers to discover (learn about their " -"existence). Nevertheless, even if these rooms are not exposed (listed) " -"for discovery, they are **still joinable** by anyone who knows their " -"address or is invited to the room by an existing member." +msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member." msgstr "" #: ../../../CHANGELOG.md:807 -msgid "" -"**We go against the upstream default** in an effort to make Matrix " -"federation more useful - a public room should be globally public - not " -"only joinable, but also discoverable across federation." +msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation." msgstr "" #: ../../../CHANGELOG.md:809 @@ -2478,50 +1390,16 @@ msgid "The **historical reasoning** behind this change is as follows:" msgstr "" #: ../../../CHANGELOG.md:811 -msgid "" -"`allow_public_rooms_over_federation` seems to have been enabled by " -"default for Synapse until v1.7.0 (~2019), just like we believe it should " -"be for a globally-federating network - rooms should be joinable and " -"discoverable across federation." +msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation." msgstr "" #: ../../../CHANGELOG.md:813 -msgid "" -"In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got " -"disabled](https://github.com/element-" -"hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891)" -" by default in a [security-by-" -"obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) " -"workaround for misconfigured servers. See the [Avoiding unwelcome " -"visitors on private Matrix servers](https://matrix.org/blog/2019/11/09" -"/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` " -"blog article. We believe that people wishing for a truly private server, " -"should [disable federation](docs/configuring-playbook-federation.md" -"#disabling-federation), instead of having a fully-federating server and " -"trying to hide its public rooms. We also provide other workarounds below." -" We (and the Synapse team, obviously) believe that Matrix should federate" -" by default, so federating the public room list seems to make sense." +msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense." msgstr "" #: ../../../CHANGELOG.md:815 #, python-format -msgid "" -"[etke.cc](https://etke.cc/) has been developing the free-software [Matrix" -" Rooms Search](https://github.com/etkecc/mrs) project for a while now. " -"One public (demo) instance of it is hosted at " -"[matrixrooms.info](https://matrixrooms.info/). This search engine tries " -"to go through the Matrix federation and discover & index public rooms to " -"allow people to find them. We believe it's vital for Matrix (and any chat" -" or social network for that matter) to be more discoverable, so that " -"people can find communities and others to talk to. Today (on 23rd of " -"October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of " -"these, only `1567` servers (7%) are making their public rooms " -"discoverable. Who knows what wonderful communities and rooms are " -"available on these 93% other Matrix servers that are supposedly " -"federating, but are still gate-keeping their public room list. " -"Indubitably, many of these servers are hosted via matrix-docker-ansible-" -"deploy, so we feel partially responsible for making Matrix federation " -"less useful." +msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful." msgstr "" #: ../../../CHANGELOG.md:817 @@ -2529,45 +1407,15 @@ msgid "Here are **actions you may wish to take** as a result of this change:" msgstr "" #: ../../../CHANGELOG.md:819 -msgid "" -"(recommended) embrace the new default. If your Matrix server is " -"federating, your public rooms have always been joinable across federation" -" anyway. Exposing the list of public rooms does no harm and more-so does " -"good by contributing to the usefulness of the Matrix network by " -"facilitating room discovery." +msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery." msgstr "" #: ../../../CHANGELOG.md:821 -msgid "" -"(switch to a better way of doings things on your semi-private server) The" -" problem that the Synapse team appears to have solved by flipping the " -"`allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to " -"for \"mostly private\" servers, which federate and have a bunch of rooms " -"made public (and published in their room directory) in an effort to allow" -" people on the same homeserver to easily find and join them (self-" -"onboarding). With the introduction of Matrix Spaces, you can reorganize " -"your flow around spaces - you can auto-join your users to a Matrix Space " -"(via Synapse's `auto_join_rooms` setting - controlled by our " -"`matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to " -"the space and make them joinable by people belonging to the space. That " -"is to say, do not make rooms public and do not publish them to the room " -"directory unless they are really public. Instead, use other mechanisms " -"for semi-public rooms or private rooms. One alternative is to stick to " -"what you're doing (public rooms published to your rooms directory) but " -"having a `m.federate: true` flag set during creation (clients like " -"Element Web have a nice UI checkbox for this) to explicitly disable " -"federation for them." +msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them." msgstr "" #: ../../../CHANGELOG.md:823 -msgid "" -"(keeping the old behavior) if you wish to keep doing what you're doing " -"(keeping your Matrix server federating, but hiding its public rooms " -"list), add `matrix_synapse_allow_public_rooms_over_federation: false` to " -"your `vars.yml` configuration. This restores the old behavior. You may " -"also consider [disabling federation](docs/configuring-playbook-" -"federation.md#disabling-federation) completely instead of relying on " -"security-by-obscurity measures." +msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures." msgstr "" #: ../../../CHANGELOG.md:826 @@ -2579,37 +1427,19 @@ msgid "Postgres parameters are automatically tuned now" msgstr "" #: ../../../CHANGELOG.md:830 -msgid "" -"The playbook has provided some hints about [Tuning PostgreSQL](docs" -"/maintenance-postgres.md#tuning-postgresql) for quite a while now." +msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now." msgstr "" #: ../../../CHANGELOG.md:832 -msgid "" -"From now on, the [Postgres Ansible role](https://github.com/mother-of-" -"all-self-hosting/ansible-role-postgres) automatically tunes your Postgres" -" configuration with the same [calculation " -"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" -" that powers https://pgtune.leopard.in.ua/." +msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/." msgstr "" #: ../../../CHANGELOG.md:834 -msgid "" -"Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) " -"documentation page has details about how you can turn auto-tuning off or " -"adjust the automatically-determined Postgres configuration parameters " -"manually." +msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually." msgstr "" #: ../../../CHANGELOG.md:836 -msgid "" -"People who [enable load-balancing with Synapse workers](docs/configuring-" -"playbook-synapse.md#load-balancing-with-workers) no longer need to " -"increase the maximum number of Postgres connections manually (previously " -"done via `postgres_process_extra_arguments`). There's a new variable " -"(`postgres_max_connections`) for controlling this number and the playbook" -" automatically raises its value from `200` to `500` for setups which " -"enable workers." +msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers." msgstr "" #: ../../../CHANGELOG.md:839 @@ -2621,16 +1451,11 @@ msgid "SchildiChat Web support" msgstr "" #: ../../../CHANGELOG.md:843 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat" -" Web](https://github.com/SchildiChat/schildichat-desktop) client." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client." msgstr "" #: ../../../CHANGELOG.md:845 -msgid "" -"See our [Configuring SchildiChat Web](docs/configuring-playbook-client-" -"schildichat-web.md) documentation to get started." +msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:848 @@ -2642,21 +1467,11 @@ msgid "mautrix-wsproxy support" msgstr "" #: ../../../CHANGELOG.md:852 -msgid "" -"Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who " -"finished what was started by [James Reilly](https://github.com/hanthor) " -"and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now " -"supports bridging to Android SMS and Apple iMessage via the [mautrix-" -"wsproxy](https://github.com/mautrix/wsproxy) service (in combination with" -" a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running" -" on your Mac or Android phone)." +msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)." msgstr "" #: ../../../CHANGELOG.md:854 -msgid "" -"See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple " -"iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) " -"documentation page for getting started." +msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:857 @@ -2668,20 +1483,11 @@ msgid "matrix-registration-bot usage changed" msgstr "" #: ../../../CHANGELOG.md:861 -msgid "" -"[matrix-registration-bot](docs/configuring-playbook-bot-matrix-" -"registration-bot.md) got some updates and now supports password-only-" -"based login. Therefore the bot now doesn't need any manual configuration " -"except setting a password in your `vars.yml`. The bot will be registered " -"as admin and access tokens will be obtained automatically by the bot." +msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot." msgstr "" #: ../../../CHANGELOG.md:863 -msgid "" -"**For existing users** You need to set " -"`matrix_bot_matrix_registration_bot_bot_password` if you previously only " -"used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also " -"remove the following deprecated settings" +msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings" msgstr "" #: ../../../CHANGELOG.md:865 @@ -2701,13 +1507,7 @@ msgid "mautrix-gmessages support" msgstr "" #: ../../../CHANGELOG.md:873 -msgid "" -"Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, " -"the playbook now supports bridging to [Google " -"Messages](https://messages.google.com/) via the [mautrix-" -"gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting" -" up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-" -"mautrix-gmessages.md) documentation page for getting started." +msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:876 @@ -2719,20 +1519,11 @@ msgid "matrix-media-repo support" msgstr "" #: ../../../CHANGELOG.md:880 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook can now set up [matrix-media-" -"repo](https://github.com/turt2live/matrix-media-repo) - an alternative " -"way to store homeserver media files, powered by a homeserver-independent " -"implementation which supports S3 storage, IPFS, deduplication and other " -"advanced features." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features." msgstr "" #: ../../../CHANGELOG.md:882 -msgid "" -"To learn more see our [Storing Matrix media files using matrix-media-" -"repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." +msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:885 @@ -2744,32 +1535,19 @@ msgid "Enabling `forget_rooms_on_leave` by default for Synapse" msgstr "" #: ../../../CHANGELOG.md:889 -msgid "" -"With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/2698), we've also **changed the default " -"value** of the `forget_rooms_on_leave` setting of Synapse to a value of " -"`true`. This way, **when you leave a room, Synapse will now forget it " -"automatically**." +msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**." msgstr "" #: ../../../CHANGELOG.md:891 -msgid "" -"The upstream Synapse default is `false` (disabled), so that you must " -"forget rooms manually after leaving." +msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving." msgstr "" #: ../../../CHANGELOG.md:893 -msgid "" -"**We go against the upstream default** ([somewhat " -"controversially](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/2700)) in an effort to make Synapse leaner and potentially do" -" what we believe most users would expect their homeserver to be doing." +msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing." msgstr "" #: ../../../CHANGELOG.md:895 -msgid "" -"If you'd like to go back to the old behavior, add the following to your " -"configuration: `matrix_synapse_forget_rooms_on_leave: false`" +msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`" msgstr "" #: ../../../CHANGELOG.md:898 @@ -2781,29 +1559,15 @@ msgid "The matrix-jitsi role lives independently now" msgstr "" #: ../../../CHANGELOG.md:902 -msgid "" -"**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-" -"jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) " -"repository, part of the [MASH playbook](https://github.com/mother-of-all-" -"self-hosting/mash-playbook). Some variables have been renamed. All " -"functionality remains intact." +msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:904 -msgid "" -"The `matrix-jitsi` role has been relocated in its own repository, part of" -" the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) project - an Ansible playbook for self-hosting [a growing list " -"of FOSS software](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack " -"on the Matrix server itself did not stand right with you or you always " -"wanted to host most stuff, you can now use this new playbook to do so." +msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." msgstr "" #: ../../../CHANGELOG.md:906 -msgid "" -"As part of the extraction process of this role out of the Matrix " -"playbook, a few other things improved:" +msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:" msgstr "" #: ../../../CHANGELOG.md:908 @@ -2811,22 +1575,15 @@ msgid "**native Traefik support** has been added" msgstr "" #: ../../../CHANGELOG.md:909 -msgid "" -"**support for hosting under a subpath** has been added, although it " -"suffers from a few minor issues listed [here](https://github.com/mother-" -"of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" +msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" msgstr "" #: ../../../CHANGELOG.md:911 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Jitsi or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not." msgstr "" #: ../../../CHANGELOG.md:913 -msgid "" -"If you're making use of Jitsi via this playbook, you will need to update " -"variable references in your `vars.yml` file:" +msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:915 @@ -2838,9 +1595,7 @@ msgid "`matrix_jitsi_` -> `jitsi_`" msgstr "" #: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944 -msgid "" -"some other internal variables have changed, but the playbook will tell " -"you about them" +msgid "some other internal variables have changed, but the playbook will tell you about them" msgstr "" #: ../../../CHANGELOG.md:919 @@ -2852,19 +1607,11 @@ msgid "ntfy Web App is disabled by default" msgstr "" #: ../../../CHANGELOG.md:923 -msgid "" -"ntfy provides a web app, which is now disabled by default, because it may" -" be unknown to and unused by most users of this playbook. You can enable " -"it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs" -"/configuring-playbook-ntfy.md))." +msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))." msgstr "" #: ../../../CHANGELOG.md:925 -msgid "" -"This change was already applied a while before this entry, but as some " -"users were reporting the missing web app, this entry was added (see " -"[#2529](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2529))." +msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))." msgstr "" #: ../../../CHANGELOG.md:928 @@ -2876,44 +1623,23 @@ msgid "The matrix-prometheus role lives independently now" msgstr "" #: ../../../CHANGELOG.md:932 -msgid "" -"**TLDR**: the `matrix-prometheus` role is now included from the [ansible-" -"role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-" -"role-prometheus) repository, part of the [MASH " -"playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). " -"Some variables have been renamed. All functionality remains intact." +msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:934 -msgid "" -"The `matrix-prometheus` role has been relocated in its own repository, " -"part of the [MASH playbook](https://github.com/mother-of-all-self-hosting" -"/mash-playbook) project - an Ansible playbook for self-hosting [a growing" -" list of FOSS software](https://github.com/mother-of-all-self-hosting" -"/mash-playbook/blob/main/docs/supported-services.md). If hosting a " -"Prometheus stack on the Matrix server itself did not stand right with you" -" or you always wanted to host most stuff, you can now use this new " -"playbook to do so." +msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." msgstr "" #: ../../../CHANGELOG.md:936 -msgid "" -"Extracting the Prometheus role out of this Matrix playbook required huge " -"internal refactoring to the way the Prometheus configuration (scraping " -"jobs) is generated. If you notice any breakage after upgrading, let us " -"know." +msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know." msgstr "" #: ../../../CHANGELOG.md:938 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Prometheus or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not." msgstr "" #: ../../../CHANGELOG.md:940 -msgid "" -"If you're making use of Prometheus via this playbook, you will need to " -"update variable references in your `vars.yml` file:" +msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:942 @@ -2933,21 +1659,11 @@ msgid "synapse-auto-compressor support" msgstr "" #: ../../../CHANGELOG.md:951 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-" -"compress-state](https://github.com/matrix-org/rust-synapse-compress-" -"state)'s `synapse_auto_compressor` tool to run periodically." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically." msgstr "" #: ../../../CHANGELOG.md:953 -msgid "" -"If enabled, `synapse_auto_compressor` runs on a schedule and compresses " -"your Synapse database's `state_groups` table. It was possible to run " -"`rust-synapse-compress-state` manually via the playbook even before - see" -" [Compressing state with rust-synapse-compress-state](docs/maintenance-" -"synapse.md#compressing-state-with-rust-synapse-compress-state). However, " -"using `synapse_auto_compressor` is better, because:" +msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:" msgstr "" #: ../../../CHANGELOG.md:955 @@ -2955,21 +1671,15 @@ msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" msgstr "" #: ../../../CHANGELOG.md:956 -msgid "" -"it's a set-it-and-forget-it tool that you can enable and never have to " -"deal with manual compression anymore" +msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore" msgstr "" #: ../../../CHANGELOG.md:958 -msgid "" -"This tool needs to be enabled manually, for now. In the future, we're " -"considering enabling it by default for all Synapse installations." +msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations." msgstr "" #: ../../../CHANGELOG.md:960 -msgid "" -"See our [Setting up synapse-auto-compressor](docs/configuring-playbook-" -"synapse-auto-compressor.md) documentation to get started." +msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:963 @@ -2981,31 +1691,15 @@ msgid "Sliding Sync proxy (Element X) support" msgstr "" #: ../../../CHANGELOG.md:967 -msgid "" -"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting " -"it started](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up" -" and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the" -" playbook can now install and configure the [sliding-sync " -"proxy](https://github.com/matrix-org/sliding-sync)." +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)." msgstr "" #: ../../../CHANGELOG.md:969 -msgid "" -"The upcoming Element X clients ([Element X iOS](https://github.com" -"/vector-im/element-x-ios) and [Element X Android](https://github.com" -"/vector-im/element-x-android)) require the `sliding-sync` proxy to do " -"their job. **These clients are still in beta** (especially Element X " -"Android, which requires manual compilation to get it working with a " -"non-`matrix.org` homeseserver). Playbook users can now easily give these " -"clients a try and help test them thanks to us having `sliding-sync` " -"support." +msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support." msgstr "" #: ../../../CHANGELOG.md:971 -msgid "" -"To get started, see our [Setting up the Sliding Sync proxy](docs" -"/configuring-playbook-sliding-sync-proxy.md) documentation page." +msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:974 @@ -3017,23 +1711,15 @@ msgid "The matrix-etherpad role lives independently now" msgstr "" #: ../../../CHANGELOG.md:978 -msgid "" -"**TLDR**: the `matrix-etherpad` role is now included from [another " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"etherpad). Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:980 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Etherpad or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not." msgstr "" #: ../../../CHANGELOG.md:982 -msgid "" -"If you're making use of Etherpad via this playbook, you will need to " -"update variable references in your `vars.yml` file:" +msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:984 @@ -3061,9 +1747,7 @@ msgid "for Traefik users:" msgstr "" #: ../../../CHANGELOG.md:991 -msgid "" -"define your own `etherpad_hostname` and `etherpad_path_prefix` as you see" -" fit" +msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit" msgstr "" #: ../../../CHANGELOG.md:993 @@ -3083,15 +1767,11 @@ msgid "Along with this relocation, the new role also:" msgstr "" #: ../../../CHANGELOG.md:999 -msgid "" -"supports [self-building](docs/self-building.md), so it should work on " -"`arm32` and `arm64` architectures" +msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures" msgstr "" #: ../../../CHANGELOG.md:1000 -msgid "" -"has native Traefik reverse-proxy support (Etherpad requests no longer go " -"through `matrix-nginx-proxy` when using Traefik)" +msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)" msgstr "" #: ../../../CHANGELOG.md:1003 @@ -3103,31 +1783,15 @@ msgid "Traefik is the default reverse-proxy now" msgstr "" #: ../../../CHANGELOG.md:1007 -msgid "" -"**TLDR**: new installations will now default to Traefik as their reverse-" -"proxy. Existing users need to explicitly choose their reverse-proxy type." -" [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is" -" strongly encouraged. `matrix-nginx-proxy` may break over time and will " -"ultimately be removed." +msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed." msgstr "" #: ../../../CHANGELOG.md:1009 -msgid "" -"As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy " -"configuration changes and initial Traefik support](#backward-" -"compatibility-reverse-proxy-configuration-changes-and-initial-traefik-" -"support), the playbook is moving to Traefik as its default SSL-" -"terminating reverse-proxy." +msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy." msgstr "" #: ../../../CHANGELOG.md:1011 -msgid "" -"Until now, we've been doing the migration gradually and keeping full " -"backward compatibility. New installations were defaulting to `matrix-" -"nginx-proxy` (just like before), while existing installations were " -"allowed to remain on `matrix-nginx-proxy` as well. This makes things very" -" difficult for us, because we need to maintain and think about lots of " -"different setups:" +msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:" msgstr "" #: ../../../CHANGELOG.md:1013 @@ -3151,33 +1815,19 @@ msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:1018 -msgid "" -"`nginx` webserver operated by the user, running without a container on " -"the same server" +msgid "`nginx` webserver operated by the user, running without a container on the same server" msgstr "" #: ../../../CHANGELOG.md:1020 -msgid "" -"Each change we do and each new feature that comes in needs to support all" -" these different ways of reverse-proxying. Because `matrix-nginx-proxy` " -"was the default and pretty much everyone was (and still is) using it, " -"means that new PRs also come with `matrix-nginx-proxy` as their main " -"focus and Traefik as an afterthought, which means we need to spend hours " -"fixing up Traefik support." +msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support." msgstr "" #: ../../../CHANGELOG.md:1022 -msgid "" -"We can't spend all this time maintaining so many different configurations" -" anymore. Traefik support has been an option for 2 weeks and lots of " -"people have already migrated their server and have tested things out. " -"Traefik is what we use and preferentially test for." +msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for." msgstr "" #: ../../../CHANGELOG.md:1024 -msgid "" -"It's time for the **next step in our migration process** to Traefik and " -"elimination of `matrix-nginx-proxy`:" +msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:" msgstr "" #: ../../../CHANGELOG.md:1026 @@ -3185,13 +1835,7 @@ msgid "Traefik is now the default reverse-proxy for new installations" msgstr "" #: ../../../CHANGELOG.md:1027 -msgid "" -"All existing users need to explicitly choose their reverse-proxy type by " -"defining the `matrix_playbook_reverse_proxy_type` variable in their " -"`vars.yml` configuration file. We strongly encourage existing users to " -"[switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the" -" nginx setup is bound to become more and more broken over time until it's" -" ultimately removed" +msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed" msgstr "" #: ../../../CHANGELOG.md:1029 @@ -3199,12 +1843,7 @@ msgid "How do I switch my existing setup to Traefik?" msgstr "" #: ../../../CHANGELOG.md:1031 -msgid "" -"**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy " -"provided by the playbook), switching to Traefik can happen with a simple " -"configuration change. Follow this section from 2 weeks ago: [How do I " -"explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-" -"traefik-right-now)." +msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)." msgstr "" #: ../../../CHANGELOG.md:1033 @@ -3212,10 +1851,7 @@ msgid "If you experience trouble:" msgstr "" #: ../../../CHANGELOG.md:1035 -msgid "" -"Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-" -"matrix-nginx-proxy) to bring your server back online using the old " -"reverse-proxy" +msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:1036 @@ -3227,14 +1863,7 @@ msgid "Try switching to Traefik again later" msgstr "" #: ../../../CHANGELOG.md:1039 -msgid "" -"**For users with a more special reverse-proxying setup** (another nginx " -"server, Apache, Caddy, etc.), the migration may not be so smooth. Follow " -"the [Using your own webserver](docs/configuring-playbook-own-" -"webserver.md) guide. Ideally, your custom reverse-proxy will be " -"configured in such a way that it **fronts the Traefik reverse-proxy** " -"provided by the playbook. Other means of reverse-proxying are more " -"fragile and may be deprecated in the future." +msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future." msgstr "" #: ../../../CHANGELOG.md:1041 @@ -3242,9 +1871,7 @@ msgid "I already use my own Traefik server. How do I plug that in?" msgstr "" #: ../../../CHANGELOG.md:1043 -msgid "" -"See the [Traefik managed by the playbook](docs/configuring-playbook-own-" -"webserver.md#traefik-managed-by-the-playbook) section." +msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section." msgstr "" #: ../../../CHANGELOG.md:1045 @@ -3252,17 +1879,11 @@ msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" msgstr "" #: ../../../CHANGELOG.md:1047 -msgid "" -"This playbook manages many different services. All these services were " -"initially integrated with `matrix-nginx-proxy`." +msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`." msgstr "" #: ../../../CHANGELOG.md:1049 -msgid "" -"While we migrate all these components to have native Traefik support, " -"some still go through nginx internally (Traefik -> local `matrix-nginx-" -"proxy` -> component). As time goes on, internal reliance on `matrix-" -"nginx-proxy` will gradually decrease until it's completely removed." +msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed." msgstr "" #: ../../../CHANGELOG.md:1051 @@ -3270,25 +1891,15 @@ msgid "How do I remain on matrix-nginx-proxy?" msgstr "" #: ../../../CHANGELOG.md:1053 -msgid "" -"Most new work and testing targets Traefik, so remaining on nginx is " -"**not** \"the good old stable\" option, but rather the \"still available," -" but largely untested and likely to be broken very soon\" option." +msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option." msgstr "" #: ../../../CHANGELOG.md:1055 -msgid "" -"To proceed regardless of this warning, add " -"`matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your " -"configuration." +msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration." msgstr "" #: ../../../CHANGELOG.md:1057 -msgid "" -"At some point in the **near** future (days, or even weeks at most), we " -"hope to completely get rid of `matrix-nginx-proxy` (or break it enough to" -" make it unusable), so you **will soon be forced to migrate** anyway. " -"Plan your migration accordingly." +msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly." msgstr "" #: ../../../CHANGELOG.md:1059 @@ -3296,11 +1907,7 @@ msgid "How do I keep using my own other reverse-proxy?" msgstr "" #: ../../../CHANGELOG.md:1061 -msgid "" -"We recommend that you follow the guide for [Fronting the integrated " -"reverse-proxy webserver with another reverse-proxy](docs/configuring-" -"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" -"webserver-with-another-reverse-proxy)." +msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." msgstr "" #: ../../../CHANGELOG.md:1064 @@ -3312,16 +1919,11 @@ msgid "rageshake support" msgstr "" #: ../../../CHANGELOG.md:1068 -msgid "" -"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook" -" can now install and configure the [rageshake](https://github.com/matrix-" -"org/rageshake) bug report server." +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server." msgstr "" #: ../../../CHANGELOG.md:1070 -msgid "" -"Additional details are available in [Setting up rageshake](docs" -"/configuring-playbook-rageshake.md)." +msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)." msgstr "" #: ../../../CHANGELOG.md:1073 @@ -3337,10 +1939,7 @@ msgid "The playbook can now help you customize Synapse's templates." msgstr "" #: ../../../CHANGELOG.md:1079 -msgid "" -"Additional details are available in the [Customizing templates](docs" -"/configuring-playbook-synapse.md#customizing-templates) section of our " -"Synapse documentation." +msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation." msgstr "" #: ../../../CHANGELOG.md:1081 @@ -3348,27 +1947,15 @@ msgid "The matrix-redis role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1083 -msgid "" -"**TLDR**: the `matrix-redis` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1085 -msgid "" -"The `matrix-redis` role (which configures [Redis](https://redis.io/)) has" -" been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"redis). This makes it possible to easily use it in other Ansible " -"playbooks." +msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1087 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Ntfy or not. If you're making use " -"of Ntfy via this playbook, you will need to update variable references in" -" your `vars.yml` file (`matrix_redis_` -> `redis_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)." msgstr "" #: ../../../CHANGELOG.md:1089 @@ -3376,26 +1963,15 @@ msgid "The matrix-ntfy role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1091 -msgid "" -"**TLDR**: the `matrix-ntfy` role is now included from another repository." -" Some variables have been renamed. All functionality remains intact." +msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1093 -msgid "" -"The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has " -"been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"ntfy). This makes it possible to easily use it in other Ansible " -"playbooks." +msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1095 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Ntfy or not. If you're making use " -"of Ntfy via this playbook, you will need to update variable references in" -" your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." msgstr "" #: ../../../CHANGELOG.md:1098 @@ -3407,27 +1983,15 @@ msgid "The matrix-grafana role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1102 -msgid "" -"**TLDR**: the `matrix-grafana` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1104 -msgid "" -"The `matrix-grafana` role (which configures [Grafana](docs/configuring-" -"playbook-prometheus-grafana.md)) has been extracted from the playbook and" -" now lives in its [own repository](https://github.com/mother-of-all-self-" -"hosting/ansible-role-grafana). This makes it possible to easily use it in" -" other Ansible playbooks." +msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1106 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Grafana or not. If you're making " -"use of Grafana via this playbook, you will need to update variable " -"references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." msgstr "" #: ../../../CHANGELOG.md:1109 @@ -3439,31 +2003,15 @@ msgid "The matrix-backup-borg role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1113 -msgid "" -"**TLDR**: the `matrix-backup-borg` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1115 -msgid "" -"Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` " -"role (which configures [BorgBackup](docs/configuring-playbook-backup-" -"borg.md)) has been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"backup_borg). This makes it possible to easily use it in other Ansible " -"playbooks and will become part of [nextcloud-docker-ansible-" -"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) " -"soon." +msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon." msgstr "" #: ../../../CHANGELOG.md:1117 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Borg's backup functionality or not." -" If you're making use of BorgBackup via this playbook, you will need to " -"update variable references in your `vars.yml` file (`matrix_backup_borg_`" -" -> `backup_borg_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)." msgstr "" #: ../../../CHANGELOG.md:1120 @@ -3471,9 +2019,7 @@ msgid "2023-02-12" msgstr "" #: ../../../CHANGELOG.md:1122 -msgid "" -"(Backward Compatibility) Reverse-proxy configuration changes and initial " -"Traefik support" +msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support" msgstr "" #: ../../../CHANGELOG.md:1124 @@ -3481,44 +2027,23 @@ msgid "**TLDR**:" msgstr "" #: ../../../CHANGELOG.md:1126 -msgid "" -"there's a new `matrix_playbook_reverse_proxy_type` variable (see " -"[roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-" -"base/defaults/main.yml)), which lets you tell the playbook what reverse-" -"proxy setup you'd like to have. This makes it easier for people who want " -"to do reverse-proxying in other ways." +msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways." msgstr "" #: ../../../CHANGELOG.md:1127 -msgid "" -"the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still" -" `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing" -" `matrix-nginx-proxy` users should not observe any changes** and can stay" -" on this for now." +msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now." msgstr "" #: ../../../CHANGELOG.md:1128 -msgid "" -"**Users who use their [own other webserver](docs/configuring-playbook-" -"own-webserver.md) (e.g. Apache, etc.) need to change** " -"`matrix_playbook_reverse_proxy_type` to something like `other-on-same-" -"host`, `other-on-another-host` or `other-nginx-non-container`" +msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`" msgstr "" #: ../../../CHANGELOG.md:1129 -msgid "" -"we now have **optional [Traefik](https://traefik.io/) support**, so you " -"could easily host Matrix and other Traefik-native services in containers " -"on the same server. Traefik support is still experimental (albeit, good " -"enough) and will improve over time. It does work, but certain esoteric " -"features may not be there yet." +msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet." msgstr "" #: ../../../CHANGELOG.md:1130 -msgid "" -"**Traefik will become the default reverse-proxy in the near future**. " -"`matrix-nginx-proxy` will either remain as an option, or be completely " -"removed to simplify the playbook" +msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook" msgstr "" #: ../../../CHANGELOG.md:1132 @@ -3526,157 +2051,67 @@ msgid "Motivation for redoing our reverse-proxy setup" msgstr "" #: ../../../CHANGELOG.md:1134 -msgid "" -"The playbook has supported various reverse-proxy setups for a long time. " -"We have various configuration variables (`matrix_nginx_proxy_enabled`, " -"various `_host_bind_port` variables, etc.) which allow the playbook to " -"adapt to these different setups. The whole situation was messy though - " -"hard to figure out and with lots of variables to toggle to make things " -"work as you'd expect - huge **operational complexity**." +msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**." msgstr "" #: ../../../CHANGELOG.md:1136 -msgid "" -"We love containers, proven by the fact that **everything** that this " -"playbook manages runs in a container. Yet, we weren't allowing people to " -"easily host other web-exposed containers alongside Matrix services on the" -" same server. We were using `matrix-nginx-proxy` (our integrated " -"[nginx](https://nginx.org/) server), which was handling web-exposure and " -"SSL termination for our own services, but we **weren't helping you with " -"all your other containers**." +msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**." msgstr "" #: ../../../CHANGELOG.md:1138 -msgid "" -"People who were **using `matrix-nginx-proxy`** were on the happy path on " -"which everything worked well by default (Matrix-wise), **but** could not " -"easily run other web-exposed services on their Matrix server because " -"`matrix-nginx-proxy` was occupying ports `80` and `443`. Other services " -"which wanted to get web exposure either had to be plugged into `matrix-" -"nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-" -"nginx-proxy` in favor of something else." +msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else." msgstr "" #: ../../../CHANGELOG.md:1140 -msgid "" -"Of those that decided to forgo `matrix-nginx-proxy`, many were **using " -"nginx** on the same server without a container. This was likely some " -"ancient nginx version, depending on your choice of distro. The Matrix " -"playbook was trying to be helpful and even with " -"`matrix_nginx_proxy_enabled: false` was still generating nginx " -"configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files " -"were adapted for inclusion into an nginx server running locally. " -"Disabling the `matrix-nginx-proxy` role like this, yet still having it " -"produce files is a bit disgusting, but it's what we've had since the " -"early beginnings of this playbook." +msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook." msgstr "" #: ../../../CHANGELOG.md:1142 -msgid "" -"Others still, wanted to run Matrix locally (no SSL certificates), " -"regardless of which web server technology this relied on, and then " -"**reverse-proxy from another machine on the network** which was doing SSL" -" termination. These people were:" +msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:" msgstr "" #: ../../../CHANGELOG.md:1144 -msgid "" -"*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined" -" with exposing services manually (setting `_bind_port` variables)" +msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)" msgstr "" #: ../../../CHANGELOG.md:1145 -msgid "" -"*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in " -"`http`-only mode (no SSL certificate retrieval)." +msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)." msgstr "" #: ../../../CHANGELOG.md:1147 -msgid "" -"Despite this operational complexity, things worked and were reasonably " -"flexible to adapt to all these situations." +msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations." msgstr "" #: ../../../CHANGELOG.md:1149 -msgid "" -"When using `matrix-nginx-proxy` as is, we still had another problem - one" -" of **internal playbook complexity**. Too many services need to be web-" -"exposed (port 80/443, SSL certificates). Because of this, they all had to" -" integrate with the `matrix-nginx-proxy` role. Tens of different roles " -"explicitly integrating with `matrix-nginx-proxy` is not what we call " -"clean. The `matrix-nginx-proxy` role contains variables for many of these" -" roles (yikes). Other roles were more decoupled from it and were " -"injecting configuration into `matrix-nginx-proxy` at runtime - see all " -"the `inject_into_nginx_proxy.yml` task files in this playbook (more " -"decoupled, but still.. yikes)." +msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)." msgstr "" #: ../../../CHANGELOG.md:1151 -msgid "" -"The next problem is one of **efficiency, interoperability and cost-" -"saving**. We're working on other playbooks:" +msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:" msgstr "" #: ../../../CHANGELOG.md:1153 -msgid "" -"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" -"/vaultwarden-docker-ansible-deploy) for hosting the " -"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an " -"alternative implementation of the [Bitwarden](https://bitwarden.com/) " -"password manager" +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager" msgstr "" #: ../../../CHANGELOG.md:1154 -msgid "" -"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source " -"code hosting service" +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service" msgstr "" #: ../../../CHANGELOG.md:1155 -msgid "" -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy) - for hosting the " -"[Nextcloud](https://nextcloud.com/) groupware platform" +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform" msgstr "" #: ../../../CHANGELOG.md:1157 -msgid "" -"We'd love for users to be able to **seamlessly use all these playbooks " -"(and others, even) against a single server**. We don't want `matrix-" -"nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for " -"other services to join in on the party. Such a thing forces people into " -"running multiple servers (one for each service), which does provide nice " -"security benefits, but is costly and ineffiecient. We'd like to make " -"self-hosting these services cheap and easy." +msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy." msgstr "" #: ../../../CHANGELOG.md:1159 -msgid "" -"These other playbooks have been using [Traefik](https://traefik.io/) as " -"their default reverse-proxy for a long time. They can all coexist nicely " -"together (as an example, see the " -"[Interoperability](https://github.com/spantaleev/nextcloud-docker-" -"ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md)" -" documentation for the [Nextcloud playbook](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining " -"Traefik support, it will be able to interoperate with them. If you're " -"going this way, make sure to have the Matrix playbook install Traefik and" -" have the others use `*_reverse_proxy_type: other-traefik-container`." +msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`." msgstr "" #: ../../../CHANGELOG.md:1161 -msgid "" -"Finally, at [etke.cc - a managed Matrix server hosting " -"service](https://etke.cc) (built on top of this playbook, and " -"coincidentally [turning 2 years old today](https://etke.cc/news" -"/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people " -"to host some additional services besides Matrix components. Exposing " -"these services to the web requires ugly hacks and configuration files " -"being dropped into `/matrix/nginx-proxy/conf.d`. We believe that " -"everything should run in independent containers and be exposed to the web" -" via a Traefik server, without a huge Ansible role like `matrix-nginx-" -"proxy` that everything else needs to integrate with." +msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with." msgstr "" #: ../../../CHANGELOG.md:1163 @@ -3684,50 +2119,27 @@ msgid "How do these changes fix all these problems?" msgstr "" #: ../../../CHANGELOG.md:1165 -msgid "" -"The new `matrix_playbook_reverse_proxy_type` lets you easily specify your" -" preferred reverse-proxy type, including `other-on-same-host`, `other-on-" -"another-host` and `none`, so people who'd like to reverse-proxy with " -"their own web server have more options now." +msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now." msgstr "" #: ../../../CHANGELOG.md:1167 -msgid "" -"Using Traefik greatly simplifies things, so going forward we'll have a " -"simpler and easier to maintain playbook, which is also interoperable with" -" other services." +msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services." msgstr "" #: ../../../CHANGELOG.md:1169 -msgid "" -"Traefik is a web server, which has been specifically **designed for " -"reverse-proxying to services running in containers**. It's ideal for " -"usage in an Ansible playbook which runs everything in containers." +msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers." msgstr "" #: ../../../CHANGELOG.md:1171 -msgid "" -"**Traefik obtains SSL certificates automatically**, so there's no need " -"for plugging additional tools like [Certbot](https://certbot.eff.org/) " -"into your web server (like we were doing in the `matrix-nginx-proxy` " -"role). No more certificate renewal timers, web server reloading timers, " -"etc. It's just simpler." +msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler." msgstr "" #: ../../../CHANGELOG.md:1173 -msgid "" -"Traefik is a **modern web server**. " -"[HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is " -"supported already (experimentally) and will move to stable soon, in the " -"upcoming Traefik v3 release." +msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release." msgstr "" #: ../../../CHANGELOG.md:1175 -msgid "" -"Traefik does not lock important functionality we'd like to use into [plus" -" packages like nginx does](https://www.nginx.com/products/nginx/), " -"leading us to resolve to configuration workarounds. The default Traefik " -"package is good enough as it is." +msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is." msgstr "" #: ../../../CHANGELOG.md:1177 @@ -3735,29 +2147,15 @@ msgid "Where we're at right now?" msgstr "" #: ../../../CHANGELOG.md:1179 -msgid "" -"`matrix_playbook_reverse_proxy_type` still defaults to a value of " -"`playbook-managed-nginx`." +msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`." msgstr "" #: ../../../CHANGELOG.md:1181 -msgid "" -"Unless we have some regression, **existing `matrix-nginx-proxy` users " -"should be able to update their Matrix server and not observe any " -"changes**. Their setup should still remain on nginx and everything should" -" still work as expected." +msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected." msgstr "" #: ../../../CHANGELOG.md:1183 -msgid "" -"**Users using [their own webservers](docs/configuring-playbook-own-" -"webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** " -"to something like `other-on-same-host`, `other-on-another-host` or " -"`other-nginx-non-container`. Previously, they could toggle " -"`matrix_nginx_proxy_enabled` to `false`, and that made the playbook " -"automatically expose services locally. Currently, we only do this if you " -"change the reverse-proxy type to `other-on-same-host`, `other-on-another-" -"host` or `other-nginx-non-container`." +msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`." msgstr "" #: ../../../CHANGELOG.md:1185 @@ -3765,62 +2163,31 @@ msgid "How do I explicitly switch to Traefik right now?" msgstr "" #: ../../../CHANGELOG.md:1187 -msgid "" -"**Users who wish to migrate to Traefik** today, can do so by **adding** " -"this to their configuration:" +msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:" msgstr "" #: ../../../CHANGELOG.md:1195 -msgid "" -"You may still need to keep certain old `matrix_nginx_proxy_*` variables " -"(like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using " -"Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` " -"variables just in case. In the future, reliance on `matrix-nginx-proxy` " -"will be removed." +msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed." msgstr "" #: ../../../CHANGELOG.md:1197 -msgid "" -"Switching to Traefik will obtain new SSL certificates from Let's Encrypt " -"(stored in `/matrix/traefik/ssl/acme.json`). **The switch is " -"reversible**. You can always go back to `playbook-managed-nginx` if " -"Traefik is causing you trouble." +msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble." msgstr "" #: ../../../CHANGELOG.md:1199 -msgid "" -"**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik " -"and nginx will uninstall the Traefik role and all of its data (under " -"`/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you" -" do it often." +msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often." msgstr "" #: ../../../CHANGELOG.md:1201 -msgid "" -"Treafik directly reverse-proxies to **some** services right now, but for " -"most other services it goes through `matrix-nginx-proxy` (e.g. Traefik ->" -" `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, " -"even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being" -" installed in local-only mode. This will improve with time." +msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time." msgstr "" #: ../../../CHANGELOG.md:1203 -msgid "" -"Some services (like [Coturn](docs/configuring-playbook-turn.md) and " -"[Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be " -"reverse-proxied to directly from Traefik, so they require direct access " -"to SSL certificate files extracted out of Traefik. The playbook does this" -" automatically thanks to a new " -"[com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper)" -" role utilizing the [traefik-certs-dumper](https://github.com/ldez" -"/traefik-certs-dumper) tool." +msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool." msgstr "" #: ../../../CHANGELOG.md:1205 -msgid "" -"Our Traefik setup mostly works, but certain esoteric features may not " -"work. If you have a default setup, we expect you to have a good " -"experience." +msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience." msgstr "" #: ../../../CHANGELOG.md:1207 @@ -3828,15 +2195,7 @@ msgid "Where we're going in the near future?" msgstr "" #: ../../../CHANGELOG.md:1209 -msgid "" -"The `matrix-nginx-proxy` role is quite messy. It manages both nginx and " -"Certbot and its certificate renewal scripts and timers. It generates " -"configuration even when the role is disabled (weird). Although it doesn't" -" directly reach into variables from other roles, it has explicit " -"awareness of various other services that it reverse-proxies to " -"(`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-" -"ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is " -"probably to just get rid of the whole thing at some point." +msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point." msgstr "" #: ../../../CHANGELOG.md:1211 @@ -3844,44 +2203,19 @@ msgid "For now, `matrix-nginx-proxy` will stay around." msgstr "" #: ../../../CHANGELOG.md:1213 -msgid "" -"As mentioned above, Traefik still reverse-proxies to some (most) services" -" by going through a local-only `matrix-nginx-proxy` server. This has " -"allowed us to add Traefik support to the playbook early on (without " -"having to rework all services), but is not the final goal. We'll **work " -"on making each service support Traefik natively**, so that traffic will " -"not need to go through `matrix-nginx-proxy` anymore. In the end, choosing" -" Traefik should only give you a pure Traefik installation with no " -"`matrix-nginx-proxy` in sight." +msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight." msgstr "" #: ../../../CHANGELOG.md:1215 -msgid "" -"As Traefik support becomes complete and proves to be stable for a while, " -"especially as a playbook default, we will **most likely remove `matrix-" -"nginx-proxy` completely**. It will likely be some months before this " -"happens though. Keeping support for both Traefik and nginx in the " -"playbook will be a burden, especially with most of us running Traefik in " -"the future. The Traefik role should do everything nginx does in a better " -"and cleaner way. Users who use their own `nginx` server on the Matrix " -"server will be inconvenienced, as nothing will generate ready-to-include " -"nginx configuration for them. Still, we hope it won't be too hard to " -"migrate their setup to another way of doing things, like:" +msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:" msgstr "" #: ../../../CHANGELOG.md:1217 -msgid "" -"not using nginx anymore. A common reason for using nginx until now was " -"that you were running other containers and you need your own nginx to " -"reverse-proxy to all of them. Just switch them to Traefik as well." +msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well." msgstr "" #: ../../../CHANGELOG.md:1218 -msgid "" -"running Traefik in local-only mode " -"(`traefik_config_entrypoint_web_secure_enabled: false`) and using some " -"nginx configuration which reverse-proxies to Traefik (we should introduce" -" examples for this in `examples/nginx`)." +msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)." msgstr "" #: ../../../CHANGELOG.md:1220 @@ -3893,32 +2227,15 @@ msgid "You can help by:" msgstr "" #: ../../../CHANGELOG.md:1224 -msgid "" -"**explicitly switching your server to Traefik** right now (see example " -"configuration in [How do I explicitly switch to Traefik right now?](#how-" -"do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting " -"troubles" +msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles" msgstr "" #: ../../../CHANGELOG.md:1226 -msgid "" -"**adding native Traefik support to a role** (requires adding Traefik " -"labels, etc.) - for inspiration, see these roles " -"([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting" -"/ansible-role-prometheus-node-exporter), " -"[prometheus_postgres_exporter](https://github.com/mother-of-all-self-" -"hosting/ansible-role-prometheus-postgres-exporter)) and how they're " -"hooked into the playbook via " -"[group_vars/matrix_servers](group_vars/matrix_servers)." +msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)." msgstr "" #: ../../../CHANGELOG.md:1228 -msgid "" -"**adding reverse-proxying examples for nginx users** in `examples/nginx`." -" People who insist on using their own `nginx` server on the same Matrix " -"host, can run Traefik in local-only mode " -"(`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy" -" to the Traefik server" +msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server" msgstr "" #: ../../../CHANGELOG.md:1231 @@ -3930,18 +2247,11 @@ msgid "Matrix Authentication Support for Jitsi" msgstr "" #: ../../../CHANGELOG.md:1235 -msgid "" -"Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk " -"gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for " -"authentication (via [Matrix User Verification Service](https://github.com" -"/matrix-org/matrix-user-verification-service))." +msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))." msgstr "" #: ../../../CHANGELOG.md:1237 -msgid "" -"Additional details are available in the [Authenticate using Matrix OpenID" -" (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-" -"using-matrix-openid-auth-type-matrix)." +msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)." msgstr "" #: ../../../CHANGELOG.md:1239 @@ -3949,19 +2259,11 @@ msgid "Draupnir moderation tool (bot) support" msgstr "" #: ../../../CHANGELOG.md:1241 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " -"install and configure the [Draupnir](https://github.com/the-draupnir-" -"project/Draupnir) moderation tool (bot). Draupnir is a fork of " -"[Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook " -"has supported for a long time) maintained by Mjolnir's former lead " -"developer." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer." msgstr "" #: ../../../CHANGELOG.md:1243 -msgid "" -"Additional details are available in [Setting up Draupnir](docs" -"/configuring-playbook-bot-draupnir.md)." +msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)." msgstr "" #: ../../../CHANGELOG.md:1246 @@ -3973,43 +2275,23 @@ msgid "The matrix-prometheus-postgres-exporter role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1250 -msgid "" -"**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included " -"from another repository. Some variables have been renamed. All " -"functionality remains intact." +msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1252 -msgid "" -"The `matrix-prometheus-postgres-exporter` role (which configures " -"[Prometheus Postgres Exporter](https://github.com/prometheus-" -"community/postgres_exporter)) has been extracted from the playbook and " -"now lives in its own repository at https://github.com/mother-of-all-self-" -"hosting/ansible-role-prometheus-postgres-exporter" +msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter" msgstr "" #: ../../../CHANGELOG.md:1254 -msgid "" -"It's still part of the playbook, but is now installed via `ansible-" -"galaxy` (by running `just roles` / `make roles`). Some variables have " -"been renamed (`matrix_prometheus_postgres_exporter_` -> " -"`prometheus_postgres_exporter_`, etc.). The playbook will report all " -"variables that you need to rename to get upgraded. All functionality " -"remains intact." +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1256 -msgid "" -"The `matrix-prometheus-services-proxy-connect` role has bee adjusted to " -"help integrate the new `prometheus_postgres_exporter` role with our own " -"services (`matrix-nginx-proxy`)" +msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)" msgstr "" #: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300 -msgid "" -"Other roles which aren't strictly related to Matrix are likely to follow " -"this fate of moving to their own repositories. Extracting them out allows" -" other Ansible playbooks to make use of these roles easily." +msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily." msgstr "" #: ../../../CHANGELOG.md:1261 @@ -4021,79 +2303,39 @@ msgid "Coturn can now use host-networking" msgstr "" #: ../../../CHANGELOG.md:1265 -msgid "" -"Large Coturn deployments (with a huge range of ports specified via " -"`matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) " -"experience a huge slowdown with how Docker publishes all these ports " -"(setting up firewall forwarding rules), which leads to a very slow Coturn" -" service startup and shutdown." +msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown." msgstr "" #: ../../../CHANGELOG.md:1267 -msgid "" -"Such deployments don't need to run Coturn within a private container " -"network anymore. Coturn can now run with host-networking by using " -"configuration like this:" +msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:" msgstr "" #: ../../../CHANGELOG.md:1273 -msgid "" -"With such a configuration, **Docker no longer needs to configure " -"thousands of firewall forwarding rules** each time Coturn starts and " -"stops. This, however, means that **you will need to ensure these ports " -"are open** in your firewall yourself." +msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself." msgstr "" #: ../../../CHANGELOG.md:1275 -msgid "" -"Thanks to us [tightening Coturn security](#backward-compatibility-" -"tightening-coturn-security-can-lead-to-connectivity-issues), running " -"Coturn with host-networking should be safe and not expose neither other " -"services running on the host, nor other services running on the local " -"network." +msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network." msgstr "" #: ../../../CHANGELOG.md:1277 -msgid "" -"(Backward Compatibility) Tightening Coturn security can lead to " -"connectivity issues" +msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues" msgstr "" #: ../../../CHANGELOG.md:1279 -msgid "" -"**TLDR**: users who run and access their Matrix server on a private " -"network (likely a small minority of users) may experience connectivity " -"issues with our new default Coturn blocklists. They may need to override " -"`matrix_coturn_denied_peer_ips` and remove some IP ranges from it." +msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it." msgstr "" #: ../../../CHANGELOG.md:1281 -msgid "" -"Inspired by [this security " -"article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-" -"access-control-protection/), we've decided to make use of Coturn's " -"`denied-peer-ip` functionality to prevent relaying network traffic to " -"certain private IP subnets. This ensures that your Coturn server won't " -"accidentally try to forward traffic to certain services running on your " -"local networks. We run Coturn in a container and in a private container " -"network by default, which should prevent such access anyway, but having " -"additional block layers in place is better." +msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better." msgstr "" #: ../../../CHANGELOG.md:1283 -msgid "" -"If you access your Matrix server from a local network and need Coturn to " -"relay to private IP addresses, you may observe that relaying is now " -"blocked due to our new default `denied-peer-ip` lists (specified in " -"`matrix_coturn_denied_peer_ips`). If you experience such connectivity " -"problems, consider overriding this setting in your `vars.yml` file and " -"removing certain networks from it." +msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it." msgstr "" #: ../../../CHANGELOG.md:1285 -msgid "" -"We've also added `no-multicast-peers` to the default Coturn " -"configuration, but we don't expect this to cause trouble for most people." +msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people." msgstr "" #: ../../../CHANGELOG.md:1288 @@ -4105,36 +2347,19 @@ msgid "The matrix-prometheus-node-exporter role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1292 -msgid "" -"**TLDR**: the `matrix-prometheus-node-exporter` role is now included from" -" another repository. Some variables have been renamed. All functionality " -"remains intact." +msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1294 -msgid "" -"The `matrix-prometheus-node-exporter` role (which configures [Prometheus " -"node exporter](https://github.com/prometheus/node_exporter)) has been " -"extracted from the playbook and now lives in its own repository at " -"https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-" -"node-exporter" +msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter" msgstr "" #: ../../../CHANGELOG.md:1296 -msgid "" -"It's still part of the playbook, but is now installed via `ansible-" -"galaxy` (by running `just roles` / `make roles`). Some variables have " -"been renamed (`matrix_prometheus_node_exporter_` -> " -"`prometheus_node_exporter_`, etc.). The playbook will report all " -"variables that you need to rename to get upgraded. All functionality " -"remains intact." +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1298 -msgid "" -"A new `matrix-prometheus-services-proxy-connect` role was added to the " -"playbook to help integrate the new `prometheus_node_exporter` role with " -"our own services (`matrix-nginx-proxy`)" +msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)" msgstr "" #: ../../../CHANGELOG.md:1303 @@ -4146,46 +2371,27 @@ msgid "Support for running commands via just" msgstr "" #: ../../../CHANGELOG.md:1307 -msgid "" -"We've previously used [make](https://www.gnu.org/software/make/) for " -"easily running some playbook commands (e.g. `make roles` which triggers " -"`ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still " -"around and you can still run these commands." +msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands." msgstr "" #: ../../../CHANGELOG.md:1309 -msgid "" -"In addition, we've added support for running commands via " -"[just](https://github.com/casey/just) - a more modern command-runner " -"alternative to `make`. Instead of `make roles`, you can now run `just " -"roles` to accomplish the same." +msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same." msgstr "" #: ../../../CHANGELOG.md:1311 -msgid "" -"Our [justfile](justfile) already defines some additional helpful " -"**shortcut** commands that weren't part of our `Makefile`. Here are some " -"examples:" +msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:" msgstr "" #: ../../../CHANGELOG.md:1313 -msgid "" -"`just install-all` to trigger the much longer `ansible-playbook -i " -"inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-" -"created,start` command" +msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command" msgstr "" #: ../../../CHANGELOG.md:1314 -msgid "" -"`just install-all --ask-vault-pass` - commands also support additional " -"arguments (`--ask-vault-pass` will be appended to the above installation " -"command)" +msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)" msgstr "" #: ../../../CHANGELOG.md:1315 -msgid "" -"`just run-tags install-mautrix-slack,start` - to run specific playbook " -"tags" +msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags" msgstr "" #: ../../../CHANGELOG.md:1316 @@ -4197,9 +2403,7 @@ msgid "`just stop-group postgres` - to stop only the Postgres service" msgstr "" #: ../../../CHANGELOG.md:1318 -msgid "" -"`just register-user alice secret-password yes` - registers an `alice` " -"user with the `secret-password` password and admin access (admin = `yes`)" +msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" #: ../../../CHANGELOG.md:1320 @@ -4207,10 +2411,7 @@ msgid "Additional helpful commands and shortcuts may be defined in the future." msgstr "" #: ../../../CHANGELOG.md:1322 -msgid "" -"This is all completely optional. If you find it difficult to [install " -"`just`](https://github.com/casey/just#installation) or don't find any of " -"this convenient, feel free to run all commands manually." +msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually." msgstr "" #: ../../../CHANGELOG.md:1325 @@ -4222,21 +2423,11 @@ msgid "mautrix-slack support" msgstr "" #: ../../../CHANGELOG.md:1329 -msgid "" -"Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the " -"playbook now supports bridging to [Slack](https://slack.com/) via the " -"[mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting " -"up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-" -"slack.md) documentation page for getting started." +msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:1331 -msgid "" -"**Note**: this is a new Slack bridge. The playbook still retains Slack " -"bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-" -"appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-" -"bridge-mx-puppet-slack.md). You're free to use the bridge that serves you" -" better, or even all three of them (for different users and use-cases)." +msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:1334 @@ -4248,18 +2439,11 @@ msgid "ChatGPT support" msgstr "" #: ../../../CHANGELOG.md:1338 -msgid "" -"Thanks to [@bertybuttface](https://github.com/bertybuttface), the " -"playbook can now help you set up [matrix-chatgpt-" -"bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through " -"which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) " -"model." +msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model." msgstr "" #: ../../../CHANGELOG.md:1340 -msgid "" -"See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-" -"chatgpt.md) documentation to get started." +msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1343 @@ -4267,25 +2451,15 @@ msgid "2022-11-30" msgstr "" #: ../../../CHANGELOG.md:1345 -msgid "" -"matrix-postgres-backup has been replaced by the ansible-role-postgres-" -"backup external role" +msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role" msgstr "" #: ../../../CHANGELOG.md:1347 -msgid "" -"Just like we've [replaced Postgres with an external role](#matrix-" -"postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-" -"role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an" -" external role - " -"[com.devture.ansible.role.postgres_backup](https://github.com/mother-of-" -"all-self-hosting/ansible-role-postgres_backup)." +msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)." msgstr "" #: ../../../CHANGELOG.md:1349 -msgid "" -"You'll need to rename your `matrix_postgres_backup`-prefixed variables " -"such that they use a `postgres_backup` prefix." +msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix." msgstr "" #: ../../../CHANGELOG.md:1352 @@ -4293,66 +2467,35 @@ msgid "2022-11-28" msgstr "" #: ../../../CHANGELOG.md:1354 -msgid "" -"matrix-postgres has been replaced by the ansible-role-postgres external " -"role" +msgid "matrix-postgres has been replaced by the ansible-role-postgres external role" msgstr "" #: ../../../CHANGELOG.md:1356 -msgid "" -"**TLDR**: the tasks that install the integrated Postgres server now live " -"in an external role - [ansible-role-postgres](https://github.com/mother-" -"of-all-self-hosting/ansible-role-postgres). You'll need to run `make " -"roles` to install it, and to also rename your `matrix_postgres`-prefixed " -"variables to use a `devture_postgres` prefix (e.g. " -"`matrix_postgres_connection_password` -> `postgres_connection_password`)." -" All your data will still be there! Some scripts have moved " -"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." +msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." msgstr "" #: ../../../CHANGELOG.md:1358 -msgid "" -"The `matrix-postgres` role that has been part of the playbook for a long " -"time has been replaced with the [ansible-role-" -"postgres](https://github.com/mother-of-all-self-hosting/ansible-role-" -"postgres) role. This was done as part of our work to [use external roles " -"for some things](#the-playbook-now-uses-external-roles-for-some-things) " -"for better code re-use and maintainability." +msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability." msgstr "" #: ../../../CHANGELOG.md:1360 -msgid "" -"The new role is an upgraded version of the old `matrix-postgres` role " -"with these notable differences:" +msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:" msgstr "" #: ../../../CHANGELOG.md:1362 -msgid "" -"it uses different names for its variables (`matrix_postgres` -> " -"`devture_postgres`)" +msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)" msgstr "" #: ../../../CHANGELOG.md:1363 -msgid "" -"when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-" -"postgresql), it will vacuum all your databases, not just the Synapse one" +msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one" msgstr "" #: ../../../CHANGELOG.md:1365 -msgid "" -"You'll need to run `make roles` to install the new role. You would also " -"need to rename your `matrix_postgres`-prefixed variables to use a " -"`devture_postgres` prefix." +msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix." msgstr "" #: ../../../CHANGELOG.md:1367 -msgid "" -"Note: the systemd service still remains the same - `matrix-" -"postgres.service`. Your data will still be in `/matrix/postgres`, etc. " -"Postgres-related scripts will be moved to `/matrix/postgres/bin` " -"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, " -"etc). Also see [The playbook no longer installs scripts in /usr/local/bin" -"](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." +msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." msgstr "" #: ../../../CHANGELOG.md:1369 @@ -4364,10 +2507,7 @@ msgid "The locations of various scripts installed by the playbook have changed." msgstr "" #: ../../../CHANGELOG.md:1373 -msgid "" -"The playbook no longer contaminates your `/usr/local/bin` directory. All " -"scripts installed by the playbook now live in `bin/` directories under " -"`/matrix`. Some examples are below:" +msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:" msgstr "" #: ../../../CHANGELOG.md:1375 @@ -4379,15 +2519,11 @@ msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" msgstr "" #: ../../../CHANGELOG.md:1377 -msgid "" -"`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> " -"`/matrix/ssl/bin/lets-encrypt-certificates-renew`" +msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`" msgstr "" #: ../../../CHANGELOG.md:1378 -msgid "" -"`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin" -"/register-user`" +msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`" msgstr "" #: ../../../CHANGELOG.md:1381 @@ -4399,79 +2535,35 @@ msgid "2x-5x performance improvements in playbook runtime" msgstr "" #: ../../../CHANGELOG.md:1385 -msgid "" -"**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and " -"various other tags). It also has new `--tags=install-*` tags (like " -"`--tags=install-all`), which skip uninstallation tasks and bring an " -"additional 2.5x speedup. In total, the playbook can maintain your server " -"5 times faster." +msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster." msgstr "" #: ../../../CHANGELOG.md:1387 -msgid "" -"Our [etke.cc managed Matrix hosting service](https://etke.cc) runs " -"maintenance against hundreds of servers, so the playbook being fast means" -" a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible)" -" (which is an extension of this one) is growing to support more and more " -"services (besides just Matrix), so the Matrix playbook being leaner " -"prevents runtimes from becoming too slow and improves the customer " -"experience." +msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience." msgstr "" #: ../../../CHANGELOG.md:1389 -msgid "" -"Even when running `ansible-playbook` manually (as most of us here do), " -"it's beneficial not to waste time and CPU resources." +msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources." msgstr "" #: ../../../CHANGELOG.md:1391 -msgid "" -"Recently, a few large optimizations have been done to this playbook and " -"its external roles (see [The playbook now uses external roles for some " -"things](#the-playbook-now-uses-external-roles-for-some-things) and don't " -"forget to run `make roles`):" +msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):" msgstr "" #: ../../../CHANGELOG.md:1393 -msgid "" -"Replacing Ansible `import_tasks` calls with `include_tasks`, which " -"decreased runtime in half. Using `import_tasks` is slower and causes " -"Ansible to go through and skip way too many tasks (tasks which could have" -" been skipped altogether by not having Ansible include them in the first " -"place). On an experimental VM, **deployment time was decreased from ~530 " -"seconds to ~250 seconds**." +msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**." msgstr "" #: ../../../CHANGELOG.md:1395 -msgid "" -"Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, " -"e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible " -"tasks pertaining to installation, while skipping uninstallation tasks. In" -" most cases, people are maintaining the same setup or they're *adding* " -"new components. Removing components is rare. Running thousands of " -"uninstallation tasks each time is wasteful. On an experimental VM, " -"**deployment time was decreased from ~250 seconds (`--tags=setup-all`) to" -" ~100 seconds (`--tags=install-all`)**." +msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**." msgstr "" #: ../../../CHANGELOG.md:1397 -msgid "" -"You can still use `--tags=setup-all`. In fact, that's the best way to " -"ensure your server is reconciled with the `vars.yml` configuration." +msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:1399 -msgid "" -"If you know you haven't uninstalled any services since the last time you " -"ran the playbook, you could run `--tags=install-all` instead and benefit " -"from quicker runtimes. It should be noted that a service may become " -"\"eligible for uninstallation\" even if your `vars.yml` file remains the " -"same. In rare cases, we toggle services from being auto-installed to " -"being optional, like we did on the 17th of March 2022 when we made [ma1sd" -" not get installed by default](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-" -"identity-server-no-longer-installed-by-default). In such rare cases, " -"you'd also need to run `--tags=setup-all`." +msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`." msgstr "" #: ../../../CHANGELOG.md:1402 @@ -4483,10 +2575,7 @@ msgid "Automatic `matrix_architecture` determination" msgstr "" #: ../../../CHANGELOG.md:1406 -msgid "" -"From now on, the playbook automatically determines your server's " -"architecture and sets the `matrix_architecture` variable accordingly. You" -" no longer need to set this variable manually in your `vars.yml` file." +msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file." msgstr "" #: ../../../CHANGELOG.md:1408 @@ -4494,36 +2583,19 @@ msgid "Docker and the Docker SDK for Python are now installed via external roles msgstr "" #: ../../../CHANGELOG.md:1412 -msgid "" -"Docker will now be installed on the server via the " -"[geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) " -"Ansible role. If you'd like to manage the Docker installation yourself, " -"you can disable the playbook's installation of Docker by setting " -"`matrix_playbook_docker_installation_enabled: false`." +msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`." msgstr "" #: ../../../CHANGELOG.md:1414 -msgid "" -"The Docker SDK for Python (named `docker-python`, `python-docker`, etc. " -"on the different platforms) is now also installed by another role " -"([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python))." -" To disable this role and install the necessary tools yourself, use " -"`devture_docker_sdk_for_python_installation_enabled: false`." +msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`." msgstr "" #: ../../../CHANGELOG.md:1416 -msgid "" -"If you're hitting issues with Docker installation or Docker SDK for " -"Python installation, consider reporting bugs or contributing to these " -"other projects." +msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects." msgstr "" #: ../../../CHANGELOG.md:1418 -msgid "" -"These additional roles are downloaded into the playbook directory (to " -"`roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an " -"easy shortcut for invoking the `ansible-galaxy` command to download these" -" roles." +msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles." msgstr "" #: ../../../CHANGELOG.md:1421 @@ -4531,22 +2603,11 @@ msgid "2022-11-20" msgstr "" #: ../../../CHANGELOG.md:1423 -msgid "" -"(Backward Compatibility Break) Changing how reverse-proxying to Synapse " -"works - now via a `matrix-synapse-reverse-proxy-companion` service" +msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service" msgstr "" #: ../../../CHANGELOG.md:1425 -msgid "" -"**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx " -"service, which helps with reverse-proxying to Synapse and its various " -"worker processes (if workers are enabled), so that `matrix-nginx-proxy` " -"can be relieved of this role. `matrix-nginx-proxy` still remains as the " -"public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-" -"reverse-proxy-companion` is just one more reverse-proxy thrown into the " -"mix for convenience. People with a more custom reverse-proxying " -"configuration may be affected - see [Webserver configuration](#webserver-" -"configuration) below." +msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below." msgstr "" #: ../../../CHANGELOG.md:1427 @@ -4554,26 +2615,11 @@ msgid "Background" msgstr "" #: ../../../CHANGELOG.md:1429 -msgid "" -"Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. " -"When Synapse is running in worker mode, the reverse-proxying " -"configuration is more complicated (different requests need to go to " -"different Synapse worker processes). `matrix-nginx-proxy` had " -"configuration for sending each URL endpoint to the correct Synapse worker" -" responsible for handling it. However, sometimes people like to disable " -"`matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own" -" webserver, instead of this playbook's nginx proxy](docs/configuring-" -"playbook-own-webserver.md)." +msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)." msgstr "" #: ../../../CHANGELOG.md:1431 -msgid "" -"Because `matrix-nginx-proxy` was so central to request forwarding, when " -"it was disabled and Synapse was running with workers enabled, there was " -"nothing which could forward requests to the correct place anymore.. which" -" caused [problems such as this one affecting " -"Dimension](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2090)." +msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)." msgstr "" #: ../../../CHANGELOG.md:1433 @@ -4581,75 +2627,43 @@ msgid "Solution" msgstr "" #: ../../../CHANGELOG.md:1435 -msgid "" -"From now on, `matrix-nginx-proxy` is relieved of its function of reverse-" -"proxying to Synapse and its various worker processes. This role is now " -"handled by the new `matrix-synapse-reverse-proxy-companion` nginx service" -" and works even if `matrix-nginx-proxy` is disabled. The purpose of the " -"new `matrix-synapse-reverse-proxy-companion` service is to:" +msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:" msgstr "" #: ../../../CHANGELOG.md:1437 -msgid "" -"serve as a companion to Synapse and know how to reverse-proxy to Synapse " -"correctly (no matter if workers are enabled or not)" +msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)" msgstr "" #: ../../../CHANGELOG.md:1439 -msgid "" -"provide a unified container address for reaching Synapse (no matter if " -"workers are enabled or not)" +msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)" msgstr "" #: ../../../CHANGELOG.md:1440 -msgid "" -"`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server " -"API traffic" +msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic" msgstr "" #: ../../../CHANGELOG.md:1441 -msgid "" -"`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server " -"(Federation) API traffic" +msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic" msgstr "" #: ../../../CHANGELOG.md:1443 -msgid "" -"simplify `matrix-nginx-proxy` configuration - it now only needs to send " -"requests to `matrix-synapse-reverse-proxy-companion` or `matrix-" -"dendrite`, etc., without having to worry about workers" +msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers" msgstr "" #: ../../../CHANGELOG.md:1445 -msgid "" -"allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is " -"disabled" +msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled" msgstr "" #: ../../../CHANGELOG.md:1447 -msgid "" -"`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-" -"proxy in the playbook. All traffic goes through it before reaching any of" -" the services. It's just that now the Synapse traffic is routed through " -"`matrix-synapse-reverse-proxy-companion` like this:" +msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:" msgstr "" #: ../../../CHANGELOG.md:1449 -msgid "" -"(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> " -"(`matrix-synapse` or some Synapse worker))." +msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))." msgstr "" #: ../../../CHANGELOG.md:1451 -msgid "" -"Various services (like Dimension, etc.) still talk to Synapse via " -"`matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) " -"preferentially. They only talk to Synapse via the reverse-proxy companion" -" (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-" -"nginx-proxy` is disabled. Services should not be talking to Synapse (e.g." -" `https://matrix-synapse:8008` directly anymore), because when workers " -"are enabled, that's the Synapse `master` process and may not be serving " -"all URL endpoints needed by the service." +msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service." msgstr "" #: ../../../CHANGELOG.md:1453 @@ -4657,49 +2671,23 @@ msgid "Webserver configuration" msgstr "" #: ../../../CHANGELOG.md:1455 -msgid "" -"if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`," -" which is the default for the playbook), you don't need to do anything" +msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything" msgstr "" #: ../../../CHANGELOG.md:1457 -msgid "" -"if you're using your own `nginx` webserver running on the server, you " -"shouldn't be affected. The `/matrix/nginx/conf.d` configuration and " -"exposed ports that you're relying on will automatically be updated in a " -"way that should work" +msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work" msgstr "" #: ../../../CHANGELOG.md:1459 -msgid "" -"if you're using another local webserver (e.g. Apache, etc.) and haven't " -"changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't " -"be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and" -" `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed " -"on `127.0.0.1` by default - just not by the `matrix-synapse` container " -"from now on, but by the `matrix-synapse-reverse-proxy-companion` " -"container instead" +msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead" msgstr "" #: ../../../CHANGELOG.md:1461 -msgid "" -"if you've been exposing `matrix-synapse` ports " -"(`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, " -"you should consider exposing `matrix-synapse-reverse-proxy-companion` " -"ports instead" +msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead" msgstr "" #: ../../../CHANGELOG.md:1463 -msgid "" -"if you're running Traefik and reverse-proxying directly to the `matrix-" -"synapse` container, you should start reverse-proxying to the `matrix-" -"synapse-reverse-proxy-companion` container instead. See [our updated " -"Traefik example configuration](docs/configuring-playbook-own-webserver.md" -"#sample-configuration-for-running-behind-traefik-20). Note: we now " -"recommend calling the federation entry point `federation` (instead of " -"`synapse`) and reverse-proxying the federation traffic via `matrix-nginx-" -"proxy`, instead of sending it directly to Synapse (or `matrix-synapse-" -"reverse-proxy-companion`). This makes the configuration simpler." +msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler." msgstr "" #: ../../../CHANGELOG.md:1466 @@ -4711,20 +2699,11 @@ msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad msgstr "" #: ../../../CHANGELOG.md:1470 -msgid "" -"Until now, [Etherpad](https://etherpad.org/) (which [the playbook could " -"install for you](docs/configuring-playbook-etherpad.md)) required the " -"[Dimension integration manager](docs/configuring-playbook-dimension.md) " -"to also be installed, because Etherpad was hosted on the Dimension domain" -" (at `dimension.example.com/etherpad`)." +msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)." msgstr "" #: ../../../CHANGELOG.md:1472 -msgid "" -"From now on, Etherpad can be installed in `standalone` mode on " -"`etherpad.example.com` and used even without Dimension. This is much more" -" versatile, so the playbook now defaults to this new mode " -"(`etherpad_mode: standalone`)." +msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)." msgstr "" #: ../../../CHANGELOG.md:1474 @@ -4732,25 +2711,11 @@ msgid "If you've already got both Etherpad and Dimension in use you could:" msgstr "" #: ../../../CHANGELOG.md:1476 -msgid "" -"**either** keep hosting Etherpad under the Dimension domain by adding " -"`etherpad_mode: dimension` to your `vars.yml` file. All your existing " -"room widgets will continue working at the same URLs and no other changes " -"will be necessary." +msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary." msgstr "" #: ../../../CHANGELOG.md:1478 -msgid "" -"**or**, you could change to hosting Etherpad separately on " -"`etherpad.example.com`. You will need to [configure a DNS record](docs" -"/configuring-dns.md) for this new domain. You will also need to " -"reconfigure Dimension to use the new pad URLs " -"(`https://etherpad.example.com/…`) going forward (refer to our " -"[configuring Etherpad documentation](docs/configuring-playbook-" -"etherpad.md)). All your existing room widgets (which still use " -"`https://dimension.example.com/etherpad/…`) will break as Etherpad is not" -" hosted there anymore. You will need to re-add them or to consider not " -"using `standalone` mode" +msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode" msgstr "" #: ../../../CHANGELOG.md:1481 @@ -4762,19 +2727,11 @@ msgid "The playbook now uses external roles for some things" msgstr "" #: ../../../CHANGELOG.md:1485 -msgid "" -"**TLDR**: when updating the playbook and before running it, you'll need " -"to run `make roles` to make [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"download dependency roles (see the [`requirements.yml` " -"file](requirements.yml)) to the `roles/galaxy` directory. Without this, " -"the playbook won't work." +msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work." msgstr "" #: ../../../CHANGELOG.md:1487 -msgid "" -"We're in the process of trimming the playbook and making it reuse Ansible" -" roles." +msgid "We're in the process of trimming the playbook and making it reuse Ansible roles." msgstr "" #: ../../../CHANGELOG.md:1489 @@ -4786,48 +2743,19 @@ msgid "those that live within the playbook itself (`roles/custom/*`)" msgstr "" #: ../../../CHANGELOG.md:1493 -msgid "" -"those downloaded from other sources (using [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"to `roles/galaxy`, based on the [`requirements.yml` " -"file](requirements.yml)). These roles are maintained by us or by other " -"people from the Ansible community." +msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community." msgstr "" #: ../../../CHANGELOG.md:1495 -msgid "" -"We're doing this for greater code-reuse (across Ansible playbooks, " -"including our own related playbooks [gitea-docker-ansible-" -"deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and " -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. " -"Until now, certain features were copy-pasted across playbooks or were " -"maintained separately in each one, with improvements often falling " -"behind. We've also tended to do too much by ourselves - installing Docker" -" on the server from our `matrix-base` role, etc. - something that we'd " -"rather not do anymore by switching to the " -"[geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." +msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." msgstr "" #: ../../../CHANGELOG.md:1497 -msgid "" -"Some variable names will change during the transition to having more and " -"more external (galaxy) roles. There's a new " -"`custom/matrix_playbook_migration` role added to the playbook which will " -"tell you about these changes each time you run the playbook." +msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:1499 -msgid "" -"**From now on**, every time you update the playbook (well, every time the" -" `requirements.yml` file changes), it's best to run `make roles` to " -"update the roles downloaded from other sources. `make roles` is a " -"shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed" -" by the [`make`](https://www.gnu.org/software/make/) utility) which " -"ultimately runs [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"to download Ansible roles. If you don't have `make`, you can also " -"manually run the commands seen in the `Makefile`." +msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`." msgstr "" #: ../../../CHANGELOG.md:1502 @@ -4839,33 +2767,19 @@ msgid "synapse-s3-storage-provider support" msgstr "" #: ../../../CHANGELOG.md:1506 -msgid "" -"**`synapse-s3-storage-provider` support is very new and still relatively " -"untested. Using it may cause data loss.**" +msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**" msgstr "" #: ../../../CHANGELOG.md:1508 -msgid "" -"You can now store your Synapse media repository files on Amazon S3 (or " -"another S3-compatible object store) using [synapse-s3-storage-" -"provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a " -"media provider for Synapse (Python module), which should work faster and " -"more reliably than our previous [Goofys](docs/configuring-" -"playbook-s3-goofys.md) implementation (Goofys will continue to work)." +msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)." msgstr "" #: ../../../CHANGELOG.md:1510 -msgid "" -"This is not just for initial installations. Users with existing files " -"(stored in the local filesystem) can also migrate their files to " -"`synapse-s3-storage-provider`." +msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`." msgstr "" #: ../../../CHANGELOG.md:1512 -msgid "" -"To get started, see our [Storing Synapse media files on Amazon S3 with " -"synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3" -"-storage-provider.md) documentation." +msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation." msgstr "" #: ../../../CHANGELOG.md:1514 @@ -4873,43 +2787,23 @@ msgid "Synapse container image customization support" msgstr "" #: ../../../CHANGELOG.md:1516 -msgid "" -"We now support customizing the Synapse container image by adding " -"additional build steps to its " -"[`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." +msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." msgstr "" #: ../../../CHANGELOG.md:1518 -msgid "" -"Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-" -"support) is actually built on this. When `s3-storage-provider` is " -"enabled, we automatically add additional build steps to install its " -"Python module into the Synapse image." +msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image." msgstr "" #: ../../../CHANGELOG.md:1520 -msgid "" -"Besides this kind of auto-added build steps (for components supported by " -"the playbook), we also let you inject your own custom build steps using " -"configuration like this:" +msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:" msgstr "" #: ../../../CHANGELOG.md:1531 -msgid "" -"People who have needed to customize Synapse previously had to fork the " -"git repository, make their changes to the `Dockerfile` there, point the " -"playbook to the new repository " -"(`matrix_synapse_container_image_self_build_repo`) and enable self-" -"building from scratch (`matrix_synapse_container_image_self_build: " -"true`). This is harder and slower." +msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower." msgstr "" #: ../../../CHANGELOG.md:1533 -msgid "" -"With the new Synapse-customization feature in the playbook, we use the " -"original upstream (pre-built, if available) Synapse image and only build " -"on top of it, right on the Matrix server. This is much faster than " -"building all of Synapse from scratch." +msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch." msgstr "" #: ../../../CHANGELOG.md:1536 @@ -4921,18 +2815,11 @@ msgid "matrix-ldap-registration-proxy support" msgstr "" #: ../../../CHANGELOG.md:1540 -msgid "" -"Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), " -"we now support installing [matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" - a proxy which handles Matrix registration requests and forwards them " -"to LDAP." +msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../CHANGELOG.md:1542 -msgid "" -"See our [Setting up matrix-ldap-registration-proxy](docs/configuring-" -"playbook-matrix-ldap-registration-proxy.md) documentation to get started." +msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1545 @@ -4940,15 +2827,11 @@ msgid "2022-09-15" msgstr "" #: ../../../CHANGELOG.md:1547 -msgid "" -"(Potential Backward Compatibility Break) Major improvements to Synapse " -"workers" +msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers" msgstr "" #: ../../../CHANGELOG.md:1549 -msgid "" -"People who are interested in running a Synapse worker setup should know " -"that **our Synapse worker implementation is much more powerful now**:" +msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:" msgstr "" #: ../../../CHANGELOG.md:1551 @@ -4956,46 +2839,31 @@ msgid "we've added support for [Stream writers](#stream-writers-support)" msgstr "" #: ../../../CHANGELOG.md:1552 -msgid "" -"we've added support for [multiple federation sender workers](#multiple-" -"federation-sender-workers-support)" +msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)" msgstr "" #: ../../../CHANGELOG.md:1553 -msgid "" -"we've added support for [multiple pusher workers](#multiple-pusher-" -"workers-support)" +msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)" msgstr "" #: ../../../CHANGELOG.md:1554 -msgid "" -"we've added support for [running background tasks on a worker" -"](#background-tasks-can-run-on-a-worker)" +msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)" msgstr "" #: ../../../CHANGELOG.md:1555 -msgid "" -"we've restored support for [`appservice` workers](#appservice-worker-" -"support-is-back)" +msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)" msgstr "" #: ../../../CHANGELOG.md:1556 -msgid "" -"we've restored support for [`user_dir` workers](#user-directory-worker-" -"support-is-back)" +msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)" msgstr "" #: ../../../CHANGELOG.md:1557 -msgid "" -"we've made it possible to [reliably use more than 1 `media_repository` " -"worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" +msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" msgstr "" #: ../../../CHANGELOG.md:1558 -msgid "" -"see the [Potential Backward Incompatibilities after these Synapse worker " -"changes](#potential-backward-incompatibilities-after-these-synapse-" -"worker-changes)" +msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)" msgstr "" #: ../../../CHANGELOG.md:1560 @@ -5003,29 +2871,15 @@ msgid "Stream writers support" msgstr "" #: ../../../CHANGELOG.md:1562 -msgid "" -"From now on, the playbook lets you easily set up various [stream writer " -"workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-" -"writers) which can handle different streams (`events` stream; `typing` " -"URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, " -"`receipts` URL endpoints, `presence` URL endpoints). All of this work was" -" previously handled by the main Synapse process, but can now be offloaded" -" to stream writer worker processes." +msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes." msgstr "" #: ../../../CHANGELOG.md:1564 -msgid "" -"If you're using `matrix_synapse_workers_preset: one-of-each`, you'll " -"automatically get 6 additional workers (one for each of the above stream " -"types). Our `little-federation-helper` preset (meant to be quite minimal " -"and focusing in improved federation performance) does not include stream " -"writer workers." +msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers." msgstr "" #: ../../../CHANGELOG.md:1566 -msgid "" -"If you'd like to customize the number of workers we also make that " -"possible using these variables:" +msgid "If you'd like to customize the number of workers we also make that possible using these variables:" msgstr "" #: ../../../CHANGELOG.md:1579 @@ -5033,11 +2887,7 @@ msgid "Multiple federation sender workers support" msgstr "" #: ../../../CHANGELOG.md:1581 -msgid "" -"Until now, we only supported a single `federation_sender` worker " -"(`matrix_synapse_workers_federation_sender_workers_count` could either be" -" `0` or `1`). From now on, you can have as many as you want to help with " -"your federation traffic." +msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic." msgstr "" #: ../../../CHANGELOG.md:1583 @@ -5045,11 +2895,7 @@ msgid "Multiple pusher workers support" msgstr "" #: ../../../CHANGELOG.md:1585 -msgid "" -"Until now, we only supported a single `pusher` worker " -"(`matrix_synapse_workers_pusher_workers_count` could either be `0` or " -"`1`). From now on, you can have as many as you want to help with pushing " -"notifications out." +msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out." msgstr "" #: ../../../CHANGELOG.md:1587 @@ -5057,17 +2903,11 @@ msgid "Background tasks can run on a worker" msgstr "" #: ../../../CHANGELOG.md:1589 -msgid "" -"From now on, you can put [background task processing on a worker](https" -"://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." +msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." msgstr "" #: ../../../CHANGELOG.md:1591 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`background` worker automatically. You can also control the `background` " -"workers count with `matrix_synapse_workers_background_workers_count`. " -"Only `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1593 @@ -5075,27 +2915,15 @@ msgid "Appservice worker support is back" msgstr "" #: ../../../CHANGELOG.md:1595 -msgid "" -"We previously had an `appservice` worker type, which [Synapse deprecated " -"in v1.59.0](https://github.com/element-" -"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" -"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" -" did we, at the time." +msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." msgstr "" #: ../../../CHANGELOG.md:1597 -msgid "" -"The new way to implement such workers is by using a `generic_worker` and " -"dedicating it to the task of talking to Application Services. From now " -"on, we have support for this." +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this." msgstr "" #: ../../../CHANGELOG.md:1599 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`appservice` worker automatically. You can also control the `appservice` " -"workers count with `matrix_synapse_workers_appservice_workers_count`. " -"Only `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1601 @@ -5103,27 +2931,15 @@ msgid "User Directory worker support is back" msgstr "" #: ../../../CHANGELOG.md:1603 -msgid "" -"We previously had a `user_dir` worker type, which [Synapse deprecated in " -"v1.59.0](https://github.com/element-" -"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" -"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" -" did we, at the time." +msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." msgstr "" #: ../../../CHANGELOG.md:1605 -msgid "" -"The new way to implement such workers is by using a `generic_worker` and " -"dedicating it to the task of serving the user directory. From now on, we " -"have support for this." +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this." msgstr "" #: ../../../CHANGELOG.md:1607 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`user_dir` worker automatically. You can also control the `user_dir` " -"workers count with `matrix_synapse_workers_user_dir_workers_count`. Only" -" `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1609 @@ -5131,20 +2947,11 @@ msgid "Using more than 1 media repository worker is now more reliable" msgstr "" #: ../../../CHANGELOG.md:1611 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, we only launch one " -"`media_repository` worker." +msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker." msgstr "" #: ../../../CHANGELOG.md:1613 -msgid "" -"If you've been configuring " -"`matrix_synapse_workers_media_repository_workers_count` manually, you may" -" have increased that to more workers. When multiple media repository " -"workers are in use, background tasks related to the media repository must" -" always be configured to run on a single `media_repository` worker via " -"`media_instance_running_background_jobs`. Until now, we weren't doing " -"this correctly, but we now are." +msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are." msgstr "" #: ../../../CHANGELOG.md:1615 @@ -5156,53 +2963,19 @@ msgid "Below we'll discuss **potential backward incompatibilities**." msgstr "" #: ../../../CHANGELOG.md:1619 -msgid "" -"**Worker names** (container names, systemd services, worker configuration" -" files) **have changed**. Workers are now labeled sequentially (e.g. " -"`matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-" -"generic-0`). The playbook will handle these changes automatically." +msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically." msgstr "" #: ../../../CHANGELOG.md:1621 -msgid "" -"Due to increased worker types support above, people who use " -"`matrix_synapse_workers_preset: one-of-each` should be aware that with " -"these changes, **the playbook will deploy 9 additional workers** (6 " -"stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background " -"task worker). This **may increase RAM/CPU usage**, etc. If you find your " -"server struggling, consider disabling some workers with the appropriate " -"`matrix_synapse_workers_*_workers_count` variables." +msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables." msgstr "" #: ../../../CHANGELOG.md:1623 -msgid "" -"**Metric endpoints have also changed** " -"(`/metrics/synapse/worker/generic_worker-18111` -> " -"`/metrics/synapse/worker/generic-worker-0`). If you're [collecting " -"metrics to an external Prometheus server](docs/configuring-playbook-" -"prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-" -"server), consider revisiting our [Collecting Synapse worker metrics to an" -" external Prometheus server](docs/configuring-playbook-prometheus-" -"grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-" -"server) docs and updating your Prometheus configuration. **If you're " -"collecting metrics to the integrated Prometheus server** (not enabled by " -"default), **your Prometheus configuration will be updated " -"automatically**. Old data (from before this change) may stick around " -"though." +msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though." msgstr "" #: ../../../CHANGELOG.md:1625 -msgid "" -"**the format of `matrix_synapse_workers_enabled_list` has changed**. You " -"were never advised to use this variable for directly creating workers (we" -" advise people to control workers using `matrix_synapse_workers_preset` " -"or by tweaking `matrix_synapse_workers_*_workers_count` variables only), " -"but some people may have started using the " -"`matrix_synapse_workers_enabled_list` variable to gain more control over " -"workers. If you're one of them, you'll need to adjust its value. See " -"`roles/custom/matrix-synapse/defaults/main.yml` for more information on " -"the new format. The playbook will also do basic validation and complain " -"if you got something wrong." +msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong." msgstr "" #: ../../../CHANGELOG.md:1628 @@ -5214,16 +2987,11 @@ msgid "Cactus Comments support" msgstr "" #: ../../../CHANGELOG.md:1632 -msgid "" -"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " -"the playbook can now set up [Cactus Comments](https://cactus.chat) - " -"federated comment system for the web based on Matrix." +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix." msgstr "" #: ../../../CHANGELOG.md:1634 -msgid "" -"See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-" -"comments.md) documentation to get started." +msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1637 @@ -5235,21 +3003,11 @@ msgid "Postmoogle email bridge support" msgstr "" #: ../../../CHANGELOG.md:1641 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up the new " -"[Postmoogle](https://github.com/etkecc/postmoogle) email bridge. " -"Postmoogle is like the [email2matrix " -"bridge](https://github.com/devture/email2matrix) (also [already supported" -" by the playbook](docs/configuring-playbook-email2matrix.md)), but more " -"capable and with the intention to soon support *sending* emails, not just" -" receiving." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving." msgstr "" #: ../../../CHANGELOG.md:1643 -msgid "" -"See our [Setting up Postmoogle email bridging](docs/configuring-playbook-" -"bridge-postmoogle.md) documentation to get started." +msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1646 @@ -5261,26 +3019,15 @@ msgid "mautrix-whatsapp default configuration changes" msgstr "" #: ../../../CHANGELOG.md:1650 -msgid "" -"In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/2012), we've made some changes to the default " -"configuration used by the `mautrix-whatsapp` bridge." +msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge." msgstr "" #: ../../../CHANGELOG.md:1652 -msgid "" -"If you're using this bridge, you should look into this PR and see if the " -"new configuration suits you. If not, you can always change individual " -"preferences in your `vars.yml` file." +msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file." msgstr "" #: ../../../CHANGELOG.md:1654 -msgid "" -"Most notably, spaces support has been enabled by default. The bridge will" -" now group rooms into a Matrix space. **If you've already bridged to " -"Whatsapp** prior to this update, you will need to send `!wa sync space` " -"to the bridge bot to make it create the space and put your existing rooms" -" into it." +msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it." msgstr "" #: ../../../CHANGELOG.md:1657 @@ -5292,30 +3039,19 @@ msgid "Conduit support" msgstr "" #: ../../../CHANGELOG.md:1661 -msgid "" -"Thanks to [Charles Wright](https://github.com/cvwright), we now have " -"optional experimental [Conduit](https://conduit.rs) homeserver support " -"for new installations. This comes as a follow-up to the playbook getting " -"[Dendrite support](#dendrite-support) earlier this year." +msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year." msgstr "" #: ../../../CHANGELOG.md:1663 -msgid "" -"Existing Synapse or Dendrite installations do **not** need to be updated." -" **Synapse is still the default homeserver implementation** installed by " -"the playbook." +msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook." msgstr "" #: ../../../CHANGELOG.md:1665 -msgid "" -"To try out Conduit, we recommend that you **use a new server** and the " -"following `vars.yml` configuration:" +msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:" msgstr "" #: ../../../CHANGELOG.md:1671 -msgid "" -"**The homeserver implementation of an existing server cannot be changed**" -" (e.g. from Synapse or Dendrite to Conduit) without data loss." +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss." msgstr "" #: ../../../CHANGELOG.md:1674 @@ -5327,22 +3063,11 @@ msgid "mautrix-discord support" msgstr "" #: ../../../CHANGELOG.md:1678 -msgid "" -"Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the " -"playbook now supports bridging to [Discord](https://discordapp.com/) via " -"the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our " -"[Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-" -"mautrix-discord.md) documentation page for getting started." +msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:1680 -msgid "" -"**Note**: this is a new Discord bridge. The playbook still retains " -"Discord bridging via [matrix-appservice-discord](docs/configuring-" -"playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs" -"/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use " -"the bridge that serves you better, or even all three of them (for " -"different users and use-cases)." +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:1683 @@ -5354,21 +3079,11 @@ msgid "matrix-appservice-kakaotalk support" msgstr "" #: ../../../CHANGELOG.md:1687 -msgid "" -"The playbook now supports bridging to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" -" via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk) - a bridge based on [node-" -"kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and " -"some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks" -" to [hnarjis](https://github.com/hnarjis) for helping us add support for " -"this!" +msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!" msgstr "" #: ../../../CHANGELOG.md:1689 -msgid "" -"See our [Setting up Appservice Kakaotalk bridging](docs/configuring-" -"playbook-bridge-appservice-kakaotalk.md) documentation to get started." +msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1692 @@ -5380,22 +3095,11 @@ msgid "maubot support" msgstr "" #: ../../../CHANGELOG.md:1696 -msgid "" -"Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for " -"starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr " -"(@moan0s)](https://github.com/moan0s) for finishing up (in [PR " -"#1894](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/1894)), the playbook can now help you set up " -"[maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot " -"system." +msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system." msgstr "" #: ../../../CHANGELOG.md:1698 -msgid "" -"See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) " -"documentation to get started." +msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1701 @@ -5407,65 +3111,39 @@ msgid "mx-puppet-skype removal" msgstr "" #: ../../../CHANGELOG.md:1705 -msgid "" -"The playbook no longer includes the [mx-puppet-" -"skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it " -"has been broken and unmaintained for a long time. Users that have " -"`matrix_mx_puppet_skype_enabled` in their configuration files will " -"encounter an error when running the playbook until they remove references" -" to this bridge from their configuration." +msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration." msgstr "" #: ../../../CHANGELOG.md:1707 -msgid "" -"To completely clean up your server from `mx-puppet-skype`'s presence on " -"it:" +msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:" msgstr "" #: ../../../CHANGELOG.md:1709 -msgid "" -"ensure your Ansible configuration (`vars.yml` file) no longer contains " -"`matrix_mx_puppet_skype_*` references" +msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references" msgstr "" #: ../../../CHANGELOG.md:1710 -msgid "" -"stop and disable the systemd service (run `systemctl disable --now " -"matrix-mx-puppet-skype` on the server)" +msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)" msgstr "" #: ../../../CHANGELOG.md:1711 -msgid "" -"delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-" -"skype.service` on the server)" +msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)" msgstr "" #: ../../../CHANGELOG.md:1712 -msgid "" -"delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on" -" the server)" +msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)" msgstr "" #: ../../../CHANGELOG.md:1713 -msgid "" -"drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-" -"postgres-cli` on the server, and execute the `DROP DATABASE " -"matrix_mx_puppet_skype;` query there)" +msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)" msgstr "" #: ../../../CHANGELOG.md:1715 -msgid "" -"If you still need bridging to [Skype](https://www.skype.com/), consider " -"switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-" -"bridge) instead. See [Setting up Go Skype Bridge bridging](docs" -"/configuring-playbook-bridge-go-skype-bridge.md)." +msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)." msgstr "" #: ../../../CHANGELOG.md:1717 -msgid "" -"If you think this is a mistake and `mx-puppet-skype` works for you (or " -"you get it to work somehow), let us know and we may reconsider this " -"removal." +msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal." msgstr "" #: ../../../CHANGELOG.md:1719 @@ -5473,41 +3151,23 @@ msgid "signald (0.19.0+) upgrade requires data migration" msgstr "" #: ../../../CHANGELOG.md:1721 -msgid "" -"In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) " -"(used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." +msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." msgstr "" #: ../../../CHANGELOG.md:1723 -msgid "" -"Back in the [`v0.19.0` released of " -"signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md)" -" (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-" -"data` command had been added that migrates avatars, group images, " -"attachments, etc., into the database (those were previously stored in the" -" filesystem)." +msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)." msgstr "" #: ../../../CHANGELOG.md:1725 -msgid "" -"If you've been using the mautrix-signal bridge for a while, you may have " -"files stored in the local filesystem, which will need to be upgraded." +msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded." msgstr "" #: ../../../CHANGELOG.md:1727 -msgid "" -"We attempt to do this data migration automatically every time Signald " -"starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` " -"systemd unit definition." +msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition." msgstr "" #: ../../../CHANGELOG.md:1729 -msgid "" -"Keep an eye on your Signal bridge and let us know (in our [support " -"room](README.md#support) or in [Pull Request " -"#1921](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/1921)) if you experience any trouble!" +msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!" msgstr "" #: ../../../CHANGELOG.md:1732 @@ -5519,16 +3179,11 @@ msgid "Ntfy push notifications support" msgstr "" #: ../../../CHANGELOG.md:1736 -msgid "" -"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " -"playbook can now install a [ntfy](https://ntfy.sh/) push notifications " -"server for you." +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" #: ../../../CHANGELOG.md:1738 -msgid "" -"See our [Setting up the ntfy push notifications server](docs/configuring-" -"playbook-ntfy.md) documentation to get started." +msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1741 @@ -5540,49 +3195,19 @@ msgid "(Potential Backward Compatibility Break) Changes around metrics collectio msgstr "" #: ../../../CHANGELOG.md:1745 -msgid "" -"**TLDR**: we've made extensive **changes to metrics exposure/collection, " -"which concern people using an external Prometheus server**. If you don't " -"know what that is, you don't need to read below." +msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below." msgstr "" #: ../../../CHANGELOG.md:1747 -msgid "" -"**Why do major changes to metrics**? Because various services were " -"exposing metrics in different, hacky, ways. Synapse was exposing metrics " -"at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the " -"`matrix.example.com`. The Hookshot role was **repurposing** the Granana " -"web UI domain (`stats.example.com`) for exposing its metrics on " -"`stats.example.com/hookshot/metrics`, while protecting these routes using" -" Basic Authentication **normally used for Synapse** " -"(`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were " -"advising for more `stats.example.com` usage in manual ways. Each role was" -" doing things differently and mixing variables from other roles. Each " -"metrics endpoint was ending up in a different place, protected by who " -"knows what Basic Authentication credentials (if protected at all)." +msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)." msgstr "" #: ../../../CHANGELOG.md:1749 -msgid "" -"**The solution**: a completely revamped way to expose metrics to an " -"external Prometheus server. We are **introducing new " -"`https://matrix.example.com/metrics/*` endpoints**, where various " -"services *can* expose their metrics, for collection by external " -"Prometheus servers. To enable the `/metrics/*` endpoints, use " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a " -"way to protect access using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)." -" See the `matrix-nginx-proxy` role or our [Collecting metrics to an " -"external Prometheus server](docs/configuring-playbook-prometheus-" -"grafana.md#collecting-metrics-to-an-external-prometheus-server) " -"documentation for additional variables around " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`." +msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`." msgstr "" #: ../../../CHANGELOG.md:1751 -msgid "" -"**If you are using the [Hookshot bridge](docs/configuring-playbook-" -"bridge-hookshot.md)**, you may find that:" +msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:" msgstr "" #: ../../../CHANGELOG.md:1752 @@ -5590,120 +3215,51 @@ msgid "**Metrics may not be enabled by default anymore**:" msgstr "" #: ../../../CHANGELOG.md:1753 -msgid "" -"If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot " -"metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: " -"true`). These metrics will be collected from the local (in-container) " -"Prometheus over the container network." +msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network." msgstr "" #: ../../../CHANGELOG.md:1754 -msgid "" -"**If Prometheus is not enabled** (you are either not using Prometheus or " -"are using an external one), **Hookshot metrics will not be enabled by " -"default anymore**. Feel free to enable them by setting " -"`matrix_hookshot_metrics_enabled: true`. Also, see below." +msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below." msgstr "" #: ../../../CHANGELOG.md:1755 -msgid "" -"When metrics are meant to be **consumed by an external Prometheus " -"server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to " -"`true`, so that metrics would be exposed (proxied) \"publicly\" on " -"`https://matrix.example.com/metrics/hookshot`. To make use of this, " -"you'll also need to enable the new `https://matrix.example.com/metrics/*`" -" endpoints mentioned above, using " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our " -"[Collecting metrics to an external Prometheus server](docs/configuring-" -"playbook-prometheus-grafana.md#collecting-metrics-to-an-external-" -"prometheus-server) documentation." +msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation." msgstr "" #: ../../../CHANGELOG.md:1756 -msgid "" -"**We've changed the URL we're exposing Hookshot metrics at** for external" -" Prometheus servers. Until now, you were advised to consume Hookshot " -"metrics from `https://stats.example.com/hookshot/metrics` (working in " -"conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now " -"on, **this no longer works**. As described above, you need to start " -"consuming metrics from `https://matrix.example.com/metrics/hookshot`." +msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`." msgstr "" #: ../../../CHANGELOG.md:1758 -msgid "" -"**If you're using node-exporter** " -"(`matrix_prometheus_node_exporter_enabled: true`) and would like to " -"collect its metrics from an external Prometheus server, see " -"`matrix_prometheus_node_exporter_metrics_proxying_enabled` described in " -"our [Collecting metrics to an external Prometheus server](docs" -"/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" -"external-prometheus-server) documentation. You will be able to collect " -"its metrics from `https://matrix.example.com/metrics/node-exporter`." +msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`." msgstr "" #: ../../../CHANGELOG.md:1760 -msgid "" -"**If you're using [postgres-exporter](docs/configuring-playbook-" -"prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) " -"and would like to collect its metrics from an external Prometheus server," -" see " -"`matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled`" -" described in our [Collecting metrics to an external Prometheus " -"server](docs/configuring-playbook-prometheus-grafana.md#collecting-" -"metrics-to-an-external-prometheus-server) documentation. You will be able" -" to collect its metrics from `https://matrix.example.com/metrics" -"/postgres-exporter`." +msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`." msgstr "" #: ../../../CHANGELOG.md:1762 -msgid "" -"**If you're using Synapse** and would like to collect its metrics from an" -" external Prometheus server, you may find that:" +msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:" msgstr "" #: ../../../CHANGELOG.md:1764 -msgid "" -"Exposing metrics is now done using " -"`matrix_synapse_metrics_proxying_enabled`, not " -"`matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to " -"enable metrics using `matrix_synapse_metrics_enabled: true` before " -"exposing them." +msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them." msgstr "" #: ../../../CHANGELOG.md:1765 -msgid "" -"Protecting metrics endpoints using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" -" is now done in another way. See our [Collecting metrics to an external " -"Prometheus server](docs/configuring-playbook-prometheus-grafana.md" -"#collecting-metrics-to-an-external-prometheus-server) documentation" +msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation" msgstr "" #: ../../../CHANGELOG.md:1766 -msgid "" -"If Synapse metrics are exposed, they will be made available at " -"`https://matrix.example.com/metrics/synapse/main-process` or " -"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers" -" are enabled), not at `https://matrix.example.com/_synapse/metrics` and " -"`https://matrix.example.com/_synapse-worker-…/metrics`" +msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`" msgstr "" #: ../../../CHANGELOG.md:1767 -msgid "" -"The playbook still generates an `external_prometheus.yml.example` sample " -"file for scraping Synapse from Prometheus as described in [Collecting " -"Synapse worker metrics to an external Prometheus server](docs" -"/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-" -"metrics-to-an-external-prometheus-server), but it's now saved under " -"`/matrix/synapse` (not `/matrix`)." +msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)." msgstr "" #: ../../../CHANGELOG.md:1769 -msgid "" -"**If you where already using a external Prometheus server** before this " -"change, and you gave a hashed version of the password as a variable, the " -"playbook will now take care of hashing the password for you. Thus, you " -"need to provide the non-hashed version now." +msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now." msgstr "" #: ../../../CHANGELOG.md:1771 @@ -5715,24 +3271,15 @@ msgid "go-skype-bridge bridging support" msgstr "" #: ../../../CHANGELOG.md:1775 -msgid "" -"Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can" -" now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-" -"bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." +msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." msgstr "" #: ../../../CHANGELOG.md:1777 -msgid "" -"See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-" -"bridge-go-skype-bridge.md) documentation to get started." +msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1779 -msgid "" -"The playbook has supported [mx-puppet-skype](https://github.com/Sorunome" -"/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype " -"bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since " -"[2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." +msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." msgstr "" #: ../../../CHANGELOG.md:1782 @@ -5744,11 +3291,7 @@ msgid "Running Ansible in a container can now happen on the Matrix server itself msgstr "" #: ../../../CHANGELOG.md:1786 -msgid "" -"If you're tired of being on an old and problematic Ansible version, you " -"can now run [run Ansible in a container on the Matrix server " -"itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-" -"server-itself)." +msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)." msgstr "" #: ../../../CHANGELOG.md:1789 @@ -5760,24 +3303,15 @@ msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" msgstr "" #: ../../../CHANGELOG.md:1793 -msgid "" -"Synapse v1.60 will try to add a new unique index to `state_group_edges` " -"upon startup and could fail if your database is corrupted." +msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted." msgstr "" #: ../../../CHANGELOG.md:1795 -msgid "" -"We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade " -"notes](https://github.com/element-" -"hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-" -"state_group_edges-could-fail-if-your-database-is-corrupted) mention it, " -"so we're giving you a heads up here in case you're unlucky." +msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky." msgstr "" #: ../../../CHANGELOG.md:1797 -msgid "" -"**If Synapse fails to start** after your next playbook run, you'll need " -"to:" +msgid "**If Synapse fails to start** after your next playbook run, you'll need to:" msgstr "" #: ../../../CHANGELOG.md:1799 @@ -5797,9 +3331,7 @@ msgid "run the following SQL query:" msgstr "" #: ../../../CHANGELOG.md:1821 -msgid "" -"You could then restart services: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=start`" +msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`" msgstr "" #: ../../../CHANGELOG.md:1824 @@ -5811,17 +3343,11 @@ msgid "Buscarron bot support" msgstr "" #: ../../../CHANGELOG.md:1828 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron " -"bot](https://github.com/etkecc/buscarron). It's a bot you can use to send" -" any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" msgstr "" #: ../../../CHANGELOG.md:1830 -msgid "" -"See our [Setting up Buscarron](docs/configuring-playbook-bot-" -"buscarron.md) documentation to get started." +msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1833 @@ -5833,17 +3359,11 @@ msgid "matrix-registration-bot support" msgstr "" #: ../../../CHANGELOG.md:1837 -msgid "" -"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " -"the playbook can now help you set up [matrix-registration-" -"bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is " -"used to create and manage registration tokens for a Matrix server." +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server." msgstr "" #: ../../../CHANGELOG.md:1839 -msgid "" -"See our [Setting up matrix-registration-bot](docs/configuring-playbook-" -"bot-matrix-registration-bot.md) documentation to get started." +msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1842 @@ -5855,57 +3375,31 @@ msgid "BorgBackup support" msgstr "" #: ../../../CHANGELOG.md:1846 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up " -"[Borg](https://www.borgbackup.org/) backups with " -"[borgmatic](https://torsion.org/borgmatic/) of your Matrix server." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server." msgstr "" #: ../../../CHANGELOG.md:1848 -msgid "" -"See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md)" -" documentation to get started." +msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1850 -msgid "" -"(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers " -"may require manual action" +msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action" msgstr "" #: ../../../CHANGELOG.md:1852 -msgid "" -"If you're running a worker setup for Synapse " -"(`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade " -"notes](https://github.com/element-" -"hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-" -"for-application-services) say that you may need to take special care when" -" upgrading:" +msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:" msgstr "" #: ../../../CHANGELOG.md:1854 -msgid "" -"Synapse v1.57.0 includes a change to the way transaction IDs are managed " -"for application services. If your deployment uses a dedicated worker for " -"application service traffic, **it must be stopped** when the database is " -"upgraded (which normally happens when the main process is upgraded), to " -"ensure the change is made safely without any risk of reusing transaction " -"IDs." +msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs." msgstr "" #: ../../../CHANGELOG.md:1856 -msgid "" -"If you're not running an `appservice` worker " -"(`matrix_synapse_workers_preset: little-federation-helper` or " -"`matrix_synapse_workers_appservice_workers_count: 0`), you are probably " -"safe to upgrade as per normal, without taking any special care." +msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care." msgstr "" #: ../../../CHANGELOG.md:1858 -msgid "" -"If you are running a setup with an `appservice` worker, or otherwise want" -" to be on the safe side, we recommend the following upgrade path:" +msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:" msgstr "" #: ../../../CHANGELOG.md:1860 @@ -5913,15 +3407,11 @@ msgid "Pull the latest playbook changes" msgstr "" #: ../../../CHANGELOG.md:1861 -msgid "" -"Stop all services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../CHANGELOG.md:1862 -msgid "" -"Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-all`)" +msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)" msgstr "" #: ../../../CHANGELOG.md:1863 @@ -5929,22 +3419,15 @@ msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" msgstr "" #: ../../../CHANGELOG.md:1864 -msgid "" -"Start the main Synapse process (`systemctl start matrix-synapse` on the " -"server)" +msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)" msgstr "" #: ../../../CHANGELOG.md:1865 -msgid "" -"Wait a while so that Synapse can start and complete the database " -"migrations. You can use `journalctl -fu matrix-synapse` on the server to " -"get a clue. Waiting a few minutes should also be enough." +msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough." msgstr "" #: ../../../CHANGELOG.md:1866 -msgid "" -"It should now be safe to start all other services. `ansible-playbook -i " -"inventory/hosts setup.yml --tags=start` will do it for you" +msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you" msgstr "" #: ../../../CHANGELOG.md:1869 @@ -5952,45 +3435,23 @@ msgid "2022-04-14" msgstr "" #: ../../../CHANGELOG.md:1871 -msgid "" -"(Compatibility Break) Changes to `docker-src` permissions necessitating " -"manual action" +msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action" msgstr "" #: ../../../CHANGELOG.md:1873 -msgid "" -"Users who build container images from source will need to manually " -"correct file permissions of some directories on the server." +msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server." msgstr "" #: ../../../CHANGELOG.md:1875 -msgid "" -"When self-building, the playbook used to `git clone` repositories (into " -"`/matrix/SERVICE/docker-src`) using the `root` user, but now uses " -"`matrix` instead to work around [the following issue with git " -"2.35.2](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1749)." +msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)." msgstr "" #: ../../../CHANGELOG.md:1877 -msgid "" -"If you're on a non-`amd64` architecture (that is, you're overriding " -"`matrix_architecture` in your `vars.yml` file) or you have enabled self-" -"building for some service (e.g. `matrix_*_self_build: true`), you're " -"certainly building some container images from source and have `docker-" -"src` directories with mixed permissions lying around in various " -"`/matrix/SERVICE` directories." +msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories." msgstr "" #: ../../../CHANGELOG.md:1879 -msgid "" -"The playbook *could* correct these permissions automatically, but that " -"requires additional Ansible tasks in some ~45 different places - " -"something that takes considerable effort. So we ask users observing " -"errors related to `docker-src` directories to correct the problem " -"manually by **running this command on the Matrix server** (which deletes " -"all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name " -"'docker-src' | xargs rm -rf`" +msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`" msgstr "" #: ../../../CHANGELOG.md:1882 @@ -6002,32 +3463,19 @@ msgid "(Compatibility Break) ma1sd identity server no longer installed by defaul msgstr "" #: ../../../CHANGELOG.md:1886 -msgid "" -"The playbook no longer installs the " -"[ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The " -"next time you run the playbook, ma1sd will be uninstalled from your " -"server, unless you explicitly enable the ma1sd service (see how below)." +msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)." msgstr "" #: ../../../CHANGELOG.md:1888 -msgid "" -"The main reason we used to install ma1sd by default in the past was to " -"prevent Element clients from talking to the `matrix.org` / `vector.im` " -"identity servers, by forcing it to talk to our own self-hosted (but " -"otherwise useless) identity server instead, thus preventing contact list " -"leaks." +msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks." msgstr "" #: ../../../CHANGELOG.md:1890 -msgid "" -"Since Element clients no longer default to using a public identity server" -" if another one is not provided, we can stop installing ma1sd." +msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd." msgstr "" #: ../../../CHANGELOG.md:1892 -msgid "" -"If you need to install the ma1sd identity server for some reason, you can" -" explicitly enable it by adding this to your `vars.yml` file:" +msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:1899 @@ -6039,23 +3487,11 @@ msgid "matrix_encryption_disabler support" msgstr "" #: ../../../CHANGELOG.md:1903 -msgid "" -"We now support installing the " -"[matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler)" -" Synapse module, which lets you prevent End-to-End-Encryption from being " -"enabled by users on your homeserver. The popular opinion is that this is " -"dangerous and shouldn't be done, but there are valid use cases for " -"disabling encryption discussed [here](https://github.com/matrix-" -"org/synapse/issues/4401)." +msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)." msgstr "" #: ../../../CHANGELOG.md:1905 -msgid "" -"To enable this module (and prevent encryption from being used on your " -"homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to" -" your configuration. This module provides further customization. Check " -"its other configuration settings (and defaults) in `roles/custom/matrix-" -"synapse/defaults/main.yml`." +msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`." msgstr "" #: ../../../CHANGELOG.md:1908 @@ -6067,13 +3503,7 @@ msgid "matrix-hookshot bridging support" msgstr "" #: ../../../CHANGELOG.md:1912 -msgid "" -"Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can" -" now install the [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) bridge for bridging Matrix to multiple project management " -"services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-" -"hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to " -"get started." +msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1915 @@ -6085,13 +3515,7 @@ msgid "ARM support for matrix-corporal" msgstr "" #: ../../../CHANGELOG.md:1919 -msgid "" -"[matrix-corporal](https://github.com/devture/matrix-corporal) (as of " -"version `2.2.3`) is now published to Docker Hub (see [devture/matrix-" -"corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-" -"arch container image with support for all these platforms: `linux/amd64`," -" `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to " -"self-building matrix-corporal on these ARM architectures." +msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures." msgstr "" #: ../../../CHANGELOG.md:1922 @@ -6103,22 +3527,11 @@ msgid "Dendrite support" msgstr "" #: ../../../CHANGELOG.md:1926 -msgid "" -"**TLDR**: We now have optional experimental [Dendrite](https://github.com" -"/matrix-org/dendrite) homeserver support for new installations. " -"**Existing (Synapse) installations need to be updated**, because some " -"internals changed. See [Adapting the configuration for existing Synapse " -"installations](#adapting-the-configuration-for-existing-synapse-" -"installations)." +msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)." msgstr "" #: ../../../CHANGELOG.md:1928 -msgid "" -"[Jip J. Dekker](https://github.com/Dekker1) did the [initial " -"work](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/818) of adding [Dendrite](https://github.com/matrix-" -"org/dendrite) support to the playbook back in January 2021. Lots of work " -"(and time) later, Dendrite support is finally ready for testing." +msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing." msgstr "" #: ../../../CHANGELOG.md:1930 @@ -6126,19 +3539,11 @@ msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" msgstr "" #: ../../../CHANGELOG.md:1932 -msgid "" -"The playbook was previously quite [Synapse](https://github.com/element-" -"hq/synapse)-centric, but can now accommodate multiple homeserver " -"implementations. Only one homeserver implementation can be active " -"(installed) at a given time." +msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time." msgstr "" #: ../../../CHANGELOG.md:1934 -msgid "" -"**Synapse is still the default homeserver implementation** installed by " -"the playbook. A new variable (`matrix_homeserver_implementation`) " -"controls which server implementation is enabled (`synapse` or `dendrite` " -"at the given moment)." +msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)." msgstr "" #: ../../../CHANGELOG.md:1936 @@ -6146,16 +3551,11 @@ msgid "Adapting the configuration for existing Synapse installations" msgstr "" #: ../../../CHANGELOG.md:1938 -msgid "" -"Because the playbook is not so Synapse-centric anymore, a small " -"configuration change is necessary for existing installations to bring " -"them up to date." +msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date." msgstr "" #: ../../../CHANGELOG.md:1940 -msgid "" -"The `vars.yml` file for **existing installations will need to be " -"updated** by adding this **additional configuration**:" +msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:" msgstr "" #: ../../../CHANGELOG.md:1952 @@ -6163,21 +3563,15 @@ msgid "Trying out Dendrite" msgstr "" #: ../../../CHANGELOG.md:1954 -msgid "" -"Finally, **to try out Dendrite**, we recommend that you **use a new " -"server** and the following addition to your `vars.yml` configuration:" +msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:" msgstr "" #: ../../../CHANGELOG.md:1960 -msgid "" -"**The homeserver implementation of an existing server cannot be changed**" -" (e.g. from Synapse to Dendrite) without data loss." +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss." msgstr "" #: ../../../CHANGELOG.md:1962 -msgid "" -"We're excited to gain support for other homeserver implementations, like " -"[Conduit](https://conduit.rs/), etc!" +msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!" msgstr "" #: ../../../CHANGELOG.md:1964 @@ -6185,16 +3579,11 @@ msgid "Honoroit bot support" msgstr "" #: ../../../CHANGELOG.md:1966 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now help you set up " -"[Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." msgstr "" #: ../../../CHANGELOG.md:1968 -msgid "" -"See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) " -"documentation to get started." +msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1971 @@ -6206,23 +3595,15 @@ msgid "Cinny support" msgstr "" #: ../../../CHANGELOG.md:1975 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook now supports " -"[Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix " -"client." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client." msgstr "" #: ../../../CHANGELOG.md:1977 -msgid "" -"By default, we still install Element Web. Still, people who'd like to try" -" Cinny out can now install it via the playbook." +msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook." msgstr "" #: ../../../CHANGELOG.md:1979 -msgid "" -"Additional details are available in [Setting up Cinny](docs/configuring-" -"playbook-client-cinny.md)." +msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)." msgstr "" #: ../../../CHANGELOG.md:1982 @@ -6234,12 +3615,7 @@ msgid "Twitter bridging support via mautrix-twitter" msgstr "" #: ../../../CHANGELOG.md:1986 -msgid "" -"Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas " -"Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-" -"twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging" -" to [Twitter](https://twitter.com/) can now also happen with [mautrix-" -"twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." +msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." msgstr "" #: ../../../CHANGELOG.md:1989 @@ -6247,26 +3623,15 @@ msgid "2021-12-14" msgstr "" #: ../../../CHANGELOG.md:1991 -msgid "" -"(Security) Users of the Signal bridge may wish to upgrade it to work " -"around log4j vulnerability" +msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability" msgstr "" #: ../../../CHANGELOG.md:1993 -msgid "" -"Recently, a security vulnerability affecting the Java logging package " -"`log4j` [has been discovered](https://www.huntress.com/blog/rapid-" -"response-critical-rce-vulnerability-is-affecting-java). Software that " -"uses this Java package is potentially vulnerable." +msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable." msgstr "" #: ../../../CHANGELOG.md:1995 -msgid "" -"One such piece of software that is part of the playbook is the [mautrix-" -"signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), " -"which [has been patched already](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/1452). If you're running this bridge, you may " -"wish to [upgrade](./docs/maintenance-upgrading-services.md)." +msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)." msgstr "" #: ../../../CHANGELOG.md:1998 @@ -6278,17 +3643,11 @@ msgid "Dropped support for Postgres v9.6" msgstr "" #: ../../../CHANGELOG.md:2002 -msgid "" -"Postgres v9.6 reached its end of life today, so the playbook will refuse " -"to run for you if you're still on that version." +msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version." msgstr "" #: ../../../CHANGELOG.md:2004 -msgid "" -"Synapse still supports v9.6 (for now), but we're retiring support for it " -"early, to avoid having to maintain support for so many Postgres versions." -" Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs" -"/maintenance-postgres.md#upgrading-postgresql) via the playbook." +msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook." msgstr "" #: ../../../CHANGELOG.md:2007 @@ -6300,18 +3659,11 @@ msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" msgstr "" #: ../../../CHANGELOG.md:2011 -msgid "" -"The mautrix-hangouts bridge is no longer receiving updates upstream and " -"is likely to stop working in the future. We still retain support for this" -" bridge in the playbook, but you're encouraged to switch away from it." +msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it." msgstr "" #: ../../../CHANGELOG.md:2013 -msgid "" -"There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat)" -" bridge that you can [install using the playbook](docs/configuring-" -"playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will " -"not be migrated**, however. You need to start fresh with the new bridge." +msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge." msgstr "" #: ../../../CHANGELOG.md:2016 @@ -6323,23 +3675,15 @@ msgid "LinkedIn bridging support via beeper-linkedin" msgstr "" #: ../../../CHANGELOG.md:2020 -msgid "" -"Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook " -"can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin)" -" bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." +msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." msgstr "" #: ../../../CHANGELOG.md:2022 -msgid "" -"This brings the total number of bridges supported by the playbook up to " -"20. See all supported bridges [here](docs/configuring-playbook.md" -"#bridging-other-networks)." +msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../CHANGELOG.md:2024 -msgid "" -"To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn" -" bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." +msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." msgstr "" #: ../../../CHANGELOG.md:2027 @@ -6351,31 +3695,19 @@ msgid "Sygnal upgraded - ARM support and no longer requires a database" msgstr "" #: ../../../CHANGELOG.md:2031 -msgid "" -"The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been " -"upgraded from `v0.9.0` to `v0.10.1`." +msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`." msgstr "" #: ../../../CHANGELOG.md:2033 -msgid "" -"This is an optional component for the playbook, so most of our users " -"wouldn't care about this announcement." +msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement." msgstr "" #: ../../../CHANGELOG.md:2035 -msgid "" -"Since this feels like a relatively big (and untested, as of yet) Sygnal " -"change, we're putting up this changelog entry." +msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry." msgstr "" #: ../../../CHANGELOG.md:2037 -msgid "" -"The new version is also available for the ARM architecture. It also no " -"longer requires a database anymore. If you need to downgrade to the " -"previous version, changing `matrix_sygnal_version` or " -"`matrix_sygnal_docker_image` will not be enough, as we've removed the " -"`database` configuration completely. You'd need to switch to an earlier " -"playbook commit." +msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit." msgstr "" #: ../../../CHANGELOG.md:2040 @@ -6387,23 +3719,15 @@ msgid "Hydrogen support" msgstr "" #: ../../../CHANGELOG.md:2044 -msgid "" -"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " -"now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a " -"new lightweight Matrix client with legacy and mobile browser support." +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support." msgstr "" #: ../../../CHANGELOG.md:2046 -msgid "" -"By default, we still install Element Web, as Hydrogen is still not fully-" -"featured. Still, people who'd like to try Hydrogen out can now install it" -" via the playbook." +msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook." msgstr "" #: ../../../CHANGELOG.md:2048 -msgid "" -"Additional details are available in [Setting up Hydrogen](docs" -"/configuring-playbook-client-hydrogen.md)." +msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)." msgstr "" #: ../../../CHANGELOG.md:2051 @@ -6415,18 +3739,11 @@ msgid "Heisenbridge support" msgstr "" #: ../../../CHANGELOG.md:2055 -msgid "" -"Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now " -"supports bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet " -"another bridge (besides matrix-appservice-irc), called " -"[Heisenbridge](https://github.com/hifi/heisenbridge)." +msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)." msgstr "" #: ../../../CHANGELOG.md:2057 -msgid "" -"Additional details are available in [Setting up Heisenbridge bouncer-" -"style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." +msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." msgstr "" #: ../../../CHANGELOG.md:2060 @@ -6438,17 +3755,11 @@ msgid "Disabling TLSv1 and TLSv1.1 for Coturn" msgstr "" #: ../../../CHANGELOG.md:2064 -msgid "" -"To improve security, we've [removed TLSv1 and TLSv1.1 " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/999) from our default " -"[Coturn](https://github.com/coturn/coturn) configuration." +msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration." msgstr "" #: ../../../CHANGELOG.md:2066 -msgid "" -"If you need to support old clients, you can re-enable both (or whichever " -"one you need) with the following configuration:" +msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:" msgstr "" #: ../../../CHANGELOG.md:2074 @@ -6460,17 +3771,11 @@ msgid "Automated local Postgres backup support" msgstr "" #: ../../../CHANGELOG.md:2078 -msgid "" -"Thanks to [foxcris](https://github.com/foxcris), the playbook can now " -"make automated local Postgres backups on a fixed schedule using [docker-" -"postgres-backup-local](https://github.com/prodrigestivill/docker-" -"postgres-backup-local)." +msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)." msgstr "" #: ../../../CHANGELOG.md:2080 -msgid "" -"Additional details are available in [Setting up postgres backup](docs" -"/configuring-playbook-postgres-backup.md)." +msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)." msgstr "" #: ../../../CHANGELOG.md:2083 @@ -6482,16 +3787,11 @@ msgid "Mjolnir moderation tool (bot) support" msgstr "" #: ../../../CHANGELOG.md:2087 -msgid "" -"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " -"can now install and configure the [Mjolnir](https://github.com/matrix-" -"org/mjolnir) moderation tool (bot)." +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)." msgstr "" #: ../../../CHANGELOG.md:2089 -msgid "" -"Additional details are available in [Setting up Mjolnir](docs" -"/configuring-playbook-bot-mjolnir.md)." +msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)." msgstr "" #: ../../../CHANGELOG.md:2092 @@ -6503,21 +3803,15 @@ msgid "Sygnal push gateway support" msgstr "" #: ../../../CHANGELOG.md:2096 -msgid "" -"The playbook can now install the [Sygnal](https://github.com/matrix-" -"org/sygnal) push gateway for you." +msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" #: ../../../CHANGELOG.md:2098 -msgid "" -"This is only useful to people who develop/build their own Matrix client " -"applications." +msgid "This is only useful to people who develop/build their own Matrix client applications." msgstr "" #: ../../../CHANGELOG.md:2100 -msgid "" -"Additional details are available in our [Setting up the Sygnal push " -"gateway](docs/configuring-playbook-sygnal.md) docs." +msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs." msgstr "" #: ../../../CHANGELOG.md:2103 @@ -6529,15 +3823,11 @@ msgid "Go-NEB support" msgstr "" #: ../../../CHANGELOG.md:2107 -msgid "" -"Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install" -" and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." +msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." msgstr "" #: ../../../CHANGELOG.md:2109 -msgid "" -"Additional details are available in [Setting up Go-NEB](docs/configuring-" -"playbook-bot-go-neb.md)." +msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)." msgstr "" #: ../../../CHANGELOG.md:2112 @@ -6549,23 +3839,15 @@ msgid "GroupMe bridging support via mx-puppet-groupme" msgstr "" #: ../../../CHANGELOG.md:2116 -msgid "" -"Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can " -"now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-" -"puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." +msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." msgstr "" #: ../../../CHANGELOG.md:2118 -msgid "" -"This brings the total number of bridges supported by the playbook up to " -"18. See all supported bridges [here](docs/configuring-playbook.md" -"#bridging-other-networks)." +msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../CHANGELOG.md:2120 -msgid "" -"To get started, follow our [Setting up MX Puppet GroupMe](docs" -"/configuring-playbook-bridge-mx-puppet-groupme.md) docs." +msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs." msgstr "" #: ../../../CHANGELOG.md:2122 @@ -6573,18 +3855,11 @@ msgid "Mautrix Instagram bridging support" msgstr "" #: ../../../CHANGELOG.md:2124 -msgid "" -"The playbook now supports bridging with " -"[Instagram](https://www.instagram.com/) by installing the [mautrix-" -"instagram](https://github.com/tulir/mautrix-instagram) bridge. This " -"playbook functionality is available thanks to " -"[@MarcProe](https://github.com/MarcProe)." +msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)." msgstr "" #: ../../../CHANGELOG.md:2126 -msgid "" -"Additional details are available in [Setting up Mautrix Instagram " -"bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." +msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." msgstr "" #: ../../../CHANGELOG.md:2128 @@ -6592,44 +3867,23 @@ msgid "Synapse workers support" msgstr "" #: ../../../CHANGELOG.md:2130 -msgid "" -"After [lots and lots of work](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/456) (done over many months by [Marcel " -"Partap](https://github.com/eMPee584), [Max " -"Klenk](https://github.com/maxklenk), a few others from the [Technical " -"University of Dresden, Germany](https://tu-dresden.de/) and various other" -" contributors), support for Synapse workers has finally landed." +msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed." msgstr "" #: ../../../CHANGELOG.md:2132 -msgid "" -"Having support for workers makes the playbook suitable for larger " -"homeserver deployments." +msgid "Having support for workers makes the playbook suitable for larger homeserver deployments." msgstr "" #: ../../../CHANGELOG.md:2134 -msgid "" -"Our setup is not yet perfect (we don't support all types of workers; " -"scaling some of them (like `pusher`, `federation_sender`) beyond a single" -" instance is not yet supported). Still, it's a great start and can " -"already power homeservers with thousands of users, like the [Matrix " -"deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed" -" in [Matrix Live S06E09 - TU Dresden on their Matrix " -"deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." +msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." msgstr "" #: ../../../CHANGELOG.md:2136 -msgid "" -"By default, workers are disabled and Synapse runs as a single process " -"(homeservers don't necessarily need the complexity and increased memory " -"requirements of running a worker-based setup)." +msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)." msgstr "" #: ../../../CHANGELOG.md:2138 -msgid "" -"To enable Synapse workers, follow our [Load balancing with workers](docs" -"/configuring-playbook-synapse.md#load-balancing-with-workers) " -"documentation." +msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation." msgstr "" #: ../../../CHANGELOG.md:2141 @@ -6637,36 +3891,19 @@ msgid "2021-02-12" msgstr "" #: ../../../CHANGELOG.md:2143 -msgid "" -"(Potential Breaking Change) Monitoring/metrics support using Prometheus " -"and Grafana" +msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana" msgstr "" #: ../../../CHANGELOG.md:2145 -msgid "" -"Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now " -"install a bunch of tools for monitoring your Matrix server: the " -"[Prometheus](https://prometheus.io) time-series database server, the " -"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" -"exporter/) host metrics exporter, and the [Grafana](https://grafana.com/)" -" web UI." +msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI." msgstr "" #: ../../../CHANGELOG.md:2147 -msgid "" -"To get get these installed, follow our [Enabling metrics and graphs " -"(Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-" -"prometheus-grafana.md) docs page." +msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page." msgstr "" #: ../../../CHANGELOG.md:2149 -msgid "" -"This update comes with a **potential breaking change** for people who " -"were already exposing Synapse metrics (for consumption via another " -"Prometheus installation). From now on, `matrix_synapse_metrics_enabled: " -"true` no longer exposes metrics publicly via matrix-nginx-proxy (at " -"`https://matrix.example.com/_synapse/metrics`). To do so, you'd need to " -"explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." +msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." msgstr "" #: ../../../CHANGELOG.md:2152 @@ -6678,18 +3915,11 @@ msgid "Etherpad support" msgstr "" #: ../../../CHANGELOG.md:2156 -msgid "" -"Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can " -"now install the [Etherpad](https://etherpad.org) realtime collaborative " -"text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video " -"call or integrated as a widget into Matrix chat rooms via the " -"[Dimension](https://dimension.t2bot.io) integration manager." +msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager." msgstr "" #: ../../../CHANGELOG.md:2158 -msgid "" -"To get it installed, follow [our Etherpad docs page](docs/configuring-" -"playbook-etherpad.md)." +msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)." msgstr "" #: ../../../CHANGELOG.md:2161 @@ -6701,17 +3931,11 @@ msgid "(Breaking Change) Postgres changes that require manual intervention" msgstr "" #: ../../../CHANGELOG.md:2165 -msgid "" -"We've made a lot of changes to our Postgres setup and some manual action " -"is required (described below). Sorry about the hassle." +msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle." msgstr "" #: ../../../CHANGELOG.md:2167 -msgid "" -"**TLDR**: people running an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md) don't need to change anything for now. " -"Everyone else (the common/default case) is affected and manual " -"intervention is required." +msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required." msgstr "" #: ../../../CHANGELOG.md:2169 @@ -6719,60 +3943,31 @@ msgid "Why?" msgstr "" #: ../../../CHANGELOG.md:2171 -msgid "" -"we had a default Postgres password (`matrix_postgres_connection_password:" -" synapse-password`), which we think is **not ideal for security " -"anymore**. We now ask you to generate/provide a strong password yourself." -" Postgres is normally not exposed outside the container network, making " -"it relatively secure, but still:" +msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:" msgstr "" #: ../../../CHANGELOG.md:2172 -msgid "" -"by tweaking the configuration, you may end up intentionally or " -"unintentionally exposing your Postgres server to the local network (or " -"even publicly), while still using the default default credentials " -"(`synapse` + `synapse-password`)" +msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2173 -msgid "" -"we can't be sure we trust all these services (bridges, etc). Some of them" -" may try to talk to or attack `matrix-postgres` using the default " -"credentials (`synapse` + `synapse-password`)" +msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2174 -msgid "" -"you may have other containers running on the same Docker network, which " -"may try to talk to or attack `matrix-postgres` using the default " -"credentials (`synapse` + `synapse-password`)" +msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2175 -msgid "" -"our Postgres usage **was overly-focused on Synapse** (default username of" -" `synapse` and default/main database of `homeserver`). Additional " -"homeserver options are likely coming in the future " -"([Dendrite](https://matrix.org/docs/projects/server/dendrite), " -"[Conduit](https://matrix.org/docs/projects/server/conduit), [The " -"Construct](https://matrix.org/docs/projects/server/construct)), so being " -"too focused on `matrix-synapse` is not great. From now on, Synapse is " -"just another component of this playbook, which happens to have an " -"*additional database* (called `synapse`) on the Postgres server." +msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server." msgstr "" #: ../../../CHANGELOG.md:2176 -msgid "" -"we try to reorganize things a bit, to make the playbook even friendlier " -"to people running an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md). Work on this will proceed in the future." +msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future." msgstr "" #: ../../../CHANGELOG.md:2178 -msgid "" -"So, this is some **effort to improve security** and to **prepare for a " -"brighter future of having more homeserver options** than just Synapse." +msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse." msgstr "" #: ../../../CHANGELOG.md:2180 @@ -6780,9 +3975,7 @@ msgid "What has really changed?" msgstr "" #: ../../../CHANGELOG.md:2182 -msgid "" -"the default superuser Postgres username is now `matrix` (used to be " -"`synapse`)" +msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)" msgstr "" #: ../../../CHANGELOG.md:2183 @@ -6790,16 +3983,11 @@ msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" msgstr "" #: ../../../CHANGELOG.md:2184 -msgid "" -"Synapse's database is now `synapse` (used to be `homeserver`). This is " -"now just another \"additional database\" that the playbook manages for " -"you" +msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you" msgstr "" #: ../../../CHANGELOG.md:2185 -msgid "" -"Synapse's user called `synapse` is just a regular user that can only use " -"the `synapse` database (not a superuser anymore)" +msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)" msgstr "" #: ../../../CHANGELOG.md:2187 @@ -6807,51 +3995,31 @@ msgid "What do I do if I'm using the integrated Postgres server (default)?" msgstr "" #: ../../../CHANGELOG.md:2189 -msgid "" -"By default, the playbook runs an integrated Postgres server for you in a " -"container (`matrix-postgres`). Unless you've explicitly configured an " -"[external Postgres server](docs/configuring-playbook-external-" -"postgres.md), these steps are meant for you." +msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you." msgstr "" #: ../../../CHANGELOG.md:2191 -msgid "" -"To migrate to the new setup, expect a few minutes of downtime, while you " -"follow these steps:" +msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:" msgstr "" #: ../../../CHANGELOG.md:2193 -msgid "" -"We believe the steps below are safe and you won't encounter any data " -"loss, but consider [making a Postgres backup](docs/maintenance-" -"postgres.md#backing-up-postgresql) anyway. If you've never backed up " -"Postgres, now would be a good time to try it." +msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it." msgstr "" #: ../../../CHANGELOG.md:2195 -msgid "" -"Generate a strong password to be used for your superuser Postgres user " -"(called `matrix`). You can use `pwgen -s 64 1` to generate it, or some " -"other tool. The **maximum length** for a Postgres password is 100 bytes " -"(characters). Don't go crazy!" +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" msgstr "" #: ../../../CHANGELOG.md:2197 -msgid "" -"Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` " -"file, adding a line like this:" +msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:" msgstr "" #: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214 -msgid "" -".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the " -"password you generated during step #2." +msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2." msgstr "" #: ../../../CHANGELOG.md:2204 -msgid "" -"Stop all services: `ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`" +msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`" msgstr "" #: ../../../CHANGELOG.md:2205 @@ -6867,15 +4035,11 @@ msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" msgstr "" #: ../../../CHANGELOG.md:2208 -msgid "" -"Execute the following query, while making sure to **change the password " -"inside** (**don't forget the ending `;`**):" +msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):" msgstr "" #: ../../../CHANGELOG.md:2216 -msgid "" -"Execute the following queries as you see them (no modifications " -"necessary, so you can just **paste them all at once**):" +msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):" msgstr "" #: ../../../CHANGELOG.md:2234 @@ -6883,9 +4047,7 @@ msgid "You may need to press *Enter* after pasting the lines above." msgstr "" #: ../../../CHANGELOG.md:2236 -msgid "" -"Re-run the playbook normally: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=setup-all,start`" +msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../CHANGELOG.md:2238 @@ -6893,21 +4055,11 @@ msgid "What do I do if I'm using an external Postgres server?" msgstr "" #: ../../../CHANGELOG.md:2240 -msgid "" -"If you've explicitly configured an [external Postgres server](docs" -"/configuring-playbook-external-postgres.md), there are **no changes** " -"that you need to do at this time." +msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time." msgstr "" #: ../../../CHANGELOG.md:2242 -msgid "" -"The fact that we've renamed Synapse's database from `homeserver` to " -"`synapse` (in our defaults) should not affect you, as you're already " -"explicitly defining `matrix_synapse_database_database` (if you've " -"followed our guide, that is). If you're not explicitly defining this " -"variable, you may wish to do so (`matrix_synapse_database_database: " -"homeserver`), to avoid the new `synapse` default and keep things as they " -"were." +msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were." msgstr "" #: ../../../CHANGELOG.md:2245 @@ -6915,35 +4067,19 @@ msgid "2021-01-20" msgstr "" #: ../../../CHANGELOG.md:2247 -msgid "" -"(Breaking Change) The mautrix-facebook bridge now requires a Postgres " -"database" +msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database" msgstr "" #: ../../../CHANGELOG.md:2249 -msgid "" -"**Update from 2021-11-15**: SQLite support has been re-added to the " -"mautrix-facebook bridge in " -"[v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You " -"can ignore this changelog entry." +msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry." msgstr "" #: ../../../CHANGELOG.md:2251 -msgid "" -"A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-" -"facebook) bridge has been released. It's a full rewrite of its backend " -"and the bridge now requires Postgres. New versions of the bridge can no " -"longer run on SQLite." +msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite." msgstr "" #: ../../../CHANGELOG.md:2253 -msgid "" -"**TLDR**: if you're NOT using an [external Postgres server](docs" -"/configuring-playbook-external-postgres.md) and have NOT forcefully kept " -"the bridge on SQLite during [The big move to all-on-Postgres (potentially" -" dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you" -" will be automatically upgraded without manual intervention. All you need" -" to do is send a `login` message to the Facebook bridge bot again." +msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again." msgstr "" #: ../../../CHANGELOG.md:2255 @@ -6951,55 +4087,31 @@ msgid "Whether this change requires your intervention depends mostly on:" msgstr "" #: ../../../CHANGELOG.md:2256 -msgid "" -"whether you're using an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md). If yes, then [you need to do something" -"](#upgrade-path-for-people-running-an-external-postgres-server)." +msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)." msgstr "" #: ../../../CHANGELOG.md:2257 -msgid "" -"or whether you've force-changed the bridge's database engine to SQLite " -"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " -"some time in the past (likely during [The big move to all-on-Postgres " -"(potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-" -"dangerous))." +msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))." msgstr "" #: ../../../CHANGELOG.md:2259 -msgid "" -"As already mentioned above, you most likely don't need to do anything. If" -" you rerun the playbook and don't get an error, you've been automatically" -" upgraded. Just send a `login` message to the Facebook bridge bot again. " -"Otherwise, read below for a solution." +msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution." msgstr "" #: ../../../CHANGELOG.md:2261 -msgid "" -"Upgrade path for people NOT running an external Postgres server (default " -"for the playbook)" +msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)" msgstr "" #: ../../../CHANGELOG.md:2263 -msgid "" -"If you're **not running an external Postgres server**, then this bridge " -"either already works on Postgres for you, or you've intentionally kept it" -" back on SQLite with custom configuration " -"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " -"." +msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ." msgstr "" #: ../../../CHANGELOG.md:2265 -msgid "" -"Simply remove that custom configuration from your `vars.yml` file (if " -"it's there) and re-run the playbook. It should upgrade you automatically." -" You'll need to send a `login` message to the Facebook bridge bot again." +msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again." msgstr "" #: ../../../CHANGELOG.md:2267 -msgid "" -"Alternatively, [you can stay on SQLite for a little longer](#staying-on-" -"sqlite-for-a-little-longer-temporary-solution)." +msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)." msgstr "" #: ../../../CHANGELOG.md:2269 @@ -7007,35 +4119,23 @@ msgid "Upgrade path for people running an external Postgres server" msgstr "" #: ../../../CHANGELOG.md:2271 -msgid "" -"For people using the internal Postgres server (the default for the " -"playbook):" +msgid "For people using the internal Postgres server (the default for the playbook):" msgstr "" #: ../../../CHANGELOG.md:2272 -msgid "" -"we automatically create an additional `matrix_mautrix_facebook` Postgres " -"database and credentials to access it" +msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it" msgstr "" #: ../../../CHANGELOG.md:2273 -msgid "" -"we automatically adjust the bridge's `matrix_mautrix_facebook_database_*`" -" variables to point the bridge to that Postgres database" +msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database" msgstr "" #: ../../../CHANGELOG.md:2274 -msgid "" -"we use [pgloader](https://pgloader.io/) to automatically import the " -"existing SQLite data for the bridge into the `matrix_mautrix_facebook` " -"Postgres database" +msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database" msgstr "" #: ../../../CHANGELOG.md:2276 -msgid "" -"If you are using an [external Postgres server](docs/configuring-playbook-" -"external-postgres.md), unfortunately we currently can't do any of that " -"for you." +msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you." msgstr "" #: ../../../CHANGELOG.md:2278 @@ -7059,29 +4159,19 @@ msgid "create a new `matrix_mautrix_facebook` Postgres database for it" msgstr "" #: ../../../CHANGELOG.md:2284 -msgid "" -"run [pgloader](https://pgloader.io/) manually (we import this bridge's " -"data using default settings and it works well)" +msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)" msgstr "" #: ../../../CHANGELOG.md:2285 -msgid "" -"define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` " -"file (credentials, etc.) - you can find their defaults in `roles/custom" -"/matrix-mautrix-facebook/defaults/main.yml`" +msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`" msgstr "" #: ../../../CHANGELOG.md:2286 -msgid "" -"switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: " -"'postgres'` in your `vars.yml` file)" +msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)" msgstr "" #: ../../../CHANGELOG.md:2287 -msgid "" -"re-run the playbook (`--tags=setup-all,start`) and ensure the bridge " -"works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu " -"matrix-mautrix-facebook`)" +msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)" msgstr "" #: ../../../CHANGELOG.md:2288 @@ -7089,9 +4179,7 @@ msgid "send a `login` message to the Facebook bridge bot again" msgstr "" #: ../../../CHANGELOG.md:2289 -msgid "" -"or, [stay on SQLite for a little longer (temporary solution)](#staying-" -"on-sqlite-for-a-little-longer-temporary-solution)" +msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)" msgstr "" #: ../../../CHANGELOG.md:2291 @@ -7099,17 +4187,11 @@ msgid "Staying on SQLite for a little longer (temporary solution)" msgstr "" #: ../../../CHANGELOG.md:2293 -msgid "" -"To keep using this bridge with SQLite for a little longer (**not " -"recommended**), use the following configuration in your `vars.yml` file:" +msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:2303 -msgid "" -"If you do this, keep in mind that **you can't run this forever**. This " -"SQLite-supporting bridge version is not getting any updates and will " -"break sooner or later. The playbook will also drop support for SQLite at " -"some point in the future." +msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future." msgstr "" #: ../../../CHANGELOG.md:2306 @@ -7121,9 +4203,7 @@ msgid "matrix-corporal goes 2.0" msgstr "" #: ../../../CHANGELOG.md:2310 -msgid "" -"[matrix-corporal v2 has been released](https://github.com/devture/matrix-" -"corporal/releases/tag/2.0.0) and the playbook also supports it now." +msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now." msgstr "" #: ../../../CHANGELOG.md:2312 @@ -7131,13 +4211,7 @@ msgid "No manual intervention is required in the common case." msgstr "" #: ../../../CHANGELOG.md:2314 -msgid "" -"The new [matrix-corporal](https://github.com/devture/matrix-corporal) " -"version is also the first one to support Interactive Authentication. If " -"you wish to enable that (hint: you should), you'll need to set up the " -"[REST auth password provider](docs/configuring-playbook-rest-auth.md). " -"There's more information in [our matrix-corporal docs](docs/configuring-" -"playbook-matrix-corporal.md)." +msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../CHANGELOG.md:2317 @@ -7149,22 +4223,15 @@ msgid "Moving from cronjobs to systemd timers" msgstr "" #: ../../../CHANGELOG.md:2321 -msgid "" -"We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-" -"nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to " -"systemd timers." +msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers." msgstr "" #: ../../../CHANGELOG.md:2323 -msgid "" -"The largest benefit of this is that we no longer require you to install a" -" cron daemon, thus simplifying our install procedure." +msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure." msgstr "" #: ../../../CHANGELOG.md:2325 -msgid "" -"The playbook will migrate you from cronjobs to systemd timers " -"automatically. This is just a heads up." +msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up." msgstr "" #: ../../../CHANGELOG.md:2328 @@ -7176,31 +4243,19 @@ msgid "(Breaking Change) New SSL configuration" msgstr "" #: ../../../CHANGELOG.md:2332 -msgid "" -"SSL configuration (protocols, ciphers) can now be more easily controlled " -"thanks to us making use of configuration presets." +msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets." msgstr "" #: ../../../CHANGELOG.md:2334 -msgid "" -"We define a few presets (old, intermediate, modern), following the " -"[Mozilla SSL Configuration Generator](https://ssl-" -"config.mozilla.org/#server=nginx)." +msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)." msgstr "" #: ../../../CHANGELOG.md:2336 -msgid "" -"A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is " -"used (defaults to `\"intermediate\"`)." +msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)." msgstr "" #: ../../../CHANGELOG.md:2338 -msgid "" -"Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to " -"`off` (used to default to `on`). It also add some more ciphers to the " -"list, giving better performance on mobile devices, and removes some weak " -"ciphers. More information in the [documentation](docs/configuring-" -"playbook-nginx.md)." +msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off` (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)." msgstr "" #: ../../../CHANGELOG.md:2340 @@ -7208,10 +4263,7 @@ msgid "To revert to the old behaviour, set the following variables:" msgstr "" #: ../../../CHANGELOG.md:2347 -msgid "" -"Just like before, you can still use your own custom protocols by " -"specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides" -" the values coming from the preset." +msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset." msgstr "" #: ../../../CHANGELOG.md:2350 @@ -7223,20 +4275,11 @@ msgid "Signal bridging support via mautrix-signal" msgstr "" #: ../../../CHANGELOG.md:2354 -msgid "" -"Thanks to [laszabine](https://github.com/laszabine)'s efforts, the " -"playbook now supports bridging to [Signal](https://www.signal.org/) via " -"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See" -" our [Setting up Mautrix Signal bridging](docs/configuring-playbook-" -"bridge-mautrix-signal.md) documentation page for getting started." +msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2356 -msgid "" -"If you had installed the mautrix-signal bridge while its Pull Request was" -" still work-in-progress, you can migrate your data to the new and final " -"setup by referring to [this comment](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." +msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." msgstr "" #: ../../../CHANGELOG.md:2359 @@ -7248,26 +4291,15 @@ msgid "The big move to all-on-Postgres (potentially dangerous)" msgstr "" #: ../../../CHANGELOG.md:2363 -msgid "" -"**TLDR**: all your bridges (and other services) will likely be auto-" -"migrated from SQLite/nedb to Postgres, hopefully without trouble. You can" -" opt-out (see how below), if too worried about breakage." +msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage." msgstr "" #: ../../../CHANGELOG.md:2365 -msgid "" -"Until now, we've only used Postgres as a database for Synapse. All other " -"services (bridges, bots, etc.) were kept simple and used a file-based " -"database (SQLite or nedb)." +msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)." msgstr "" #: ../../../CHANGELOG.md:2367 -msgid "" -"Since [this huge pull request](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/740), **all of our services now use Postgres " -"by default**. Thanks to [Johanna Dorothea " -"Reichmann](https://github.com/jdreichmann) for starting the work on it " -"and for providing great input!" +msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!" msgstr "" #: ../../../CHANGELOG.md:2369 @@ -7279,25 +4311,15 @@ msgid "**improved performance**" msgstr "" #: ../../../CHANGELOG.md:2372 -msgid "" -"**improved compatibility**. Most bridges are deprecating SQLite/nedb " -"support or offer less features when not on Postgres." +msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres." msgstr "" #: ../../../CHANGELOG.md:2373 -msgid "" -"**easier backups**. It's still some effort to take a proper backup " -"(Postgres dump + various files, keys), but a Postgres dump now takes you " -"much further." +msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further." msgstr "" #: ../../../CHANGELOG.md:2374 -msgid "" -"we're now **more prepared to introduce other services** that need a " -"Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), " -"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge " -"(existing [pull request](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/686)), etc." +msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc." msgstr "" #: ../../../CHANGELOG.md:2376 @@ -7305,21 +4327,11 @@ msgid "Key takeway" msgstr "" #: ../../../CHANGELOG.md:2378 -msgid "" -"existing installations that use an [external " -"Postgres](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/master/docs/configuring-playbook-external-postgres.md) server" -" should be unaffected (they remain on SQLite/nedb for all services, " -"except Synapse)" +msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)" msgstr "" #: ../../../CHANGELOG.md:2380 -msgid "" -"for existing installations which use our integrated Postgres database " -"server (`matrix-postgres`, which is the default), **we automatically " -"migrate data** from SQLite/nedb to Postgres and **archive the database " -"files** (`something.db` -> `something.db.backup`), so you can restore " -"them if you need to go back (see how below)." +msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)." msgstr "" #: ../../../CHANGELOG.md:2382 @@ -7327,26 +4339,15 @@ msgid "Opting-out of the Postgres migration" msgstr "" #: ../../../CHANGELOG.md:2384 -msgid "" -"This is a **very large and somewhat untested change** (potentially " -"dangerous), so **if you're not feeling confident/experimental, opt-out** " -"of it for now. Still, it's the new default and what we (and various " -"bridges) will focus on going forward, so don't stick to old ways for too " -"long." +msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long." msgstr "" #: ../../../CHANGELOG.md:2386 -msgid "" -"You can remain on SQLite/nedb (at least for now) by adding a variable " -"like this to your `vars.yml` file for each service you use: " -"`matrix_COMPONENT_database_engine: sqlite` (e.g. " -"`matrix_mautrix_facebook_database_engine: sqlite`)." +msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)." msgstr "" #: ../../../CHANGELOG.md:2388 -msgid "" -"Some services (like `appservice-irc` and `appservice-slack`) don't use " -"SQLite, so use `nedb`, instead of `sqlite` for them." +msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." msgstr "" #: ../../../CHANGELOG.md:2390 @@ -7354,37 +4355,23 @@ msgid "Going back to SQLite/nedb if things went wrong" msgstr "" #: ../../../CHANGELOG.md:2392 -msgid "" -"If you went with the Postgres migration and it went badly for you (some " -"bridge not working as expected or not working at all), do this:" +msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:" msgstr "" #: ../../../CHANGELOG.md:2394 -msgid "" -"stop all services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../CHANGELOG.md:2395 -msgid "" -"SSH into the server and rename the old database files " -"(`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-" -"facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data" -"/mautrix-facebook.db`" +msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`" msgstr "" #: ../../../CHANGELOG.md:2396 -msgid "" -"switch the affected service back to SQLite (e.g. " -"`matrix_mautrix_facebook_database_engine: sqlite`). Some services (like " -"`appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`," -" instead of `sqlite` for them." +msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." msgstr "" #: ../../../CHANGELOG.md:2397 -msgid "" -"re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-all,start`)" +msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)" msgstr "" #: ../../../CHANGELOG.md:2398 @@ -7400,20 +4387,11 @@ msgid "synapse-janitor support removed" msgstr "" #: ../../../CHANGELOG.md:2404 -msgid "" -"We've removed support for the unmaintained [synapse-" -"janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's " -"been past reports of it corrupting the Synapse database. Since there " -"hasn't been any new development on it and it doesn't seem too useful " -"nowadays, there's no point in including it in the playbook." +msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook." msgstr "" #: ../../../CHANGELOG.md:2406 -msgid "" -"If you need to clean up or compact your database, consider using the " -"Synapse Admin APIs directly. See our [Synapse maintenance](docs" -"/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-" -"postgres.md) documentation pages for more details." +msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details." msgstr "" #: ../../../CHANGELOG.md:2408 @@ -7421,26 +4399,15 @@ msgid "Docker 20.10 is here" msgstr "" #: ../../../CHANGELOG.md:2410 -msgid "" -"(No need to do anything special in relation to this. Just something to " -"keep in mind)" +msgid "(No need to do anything special in relation to this. Just something to keep in mind)" msgstr "" #: ../../../CHANGELOG.md:2412 -msgid "" -"Docker 20.10 got released recently and your server will likely get it the" -" next time you update." +msgid "Docker 20.10 got released recently and your server will likely get it the next time you update." msgstr "" #: ../../../CHANGELOG.md:2414 -msgid "" -"This is the first major Docker update in a long time and it packs a lot " -"of changes. Some of them introduced some breakage for us initially (see " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should " -"be all good now." +msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now." msgstr "" #: ../../../CHANGELOG.md:2417 @@ -7448,31 +4415,19 @@ msgid "2020-12-08" msgstr "" #: ../../../CHANGELOG.md:2419 -msgid "" -"openid APIs exposed by default on the federation port when federation " -"disabled" +msgid "openid APIs exposed by default on the federation port when federation disabled" msgstr "" #: ../../../CHANGELOG.md:2421 -msgid "" -"We've changed some defaults. People running with our default " -"configuration (federation enabled), are not affected at all." +msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all." msgstr "" #: ../../../CHANGELOG.md:2423 -msgid "" -"If you are running an unfederated server " -"(`matrix_synapse_federation_enabled: false`), this may be of interest to " -"you." +msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you." msgstr "" #: ../../../CHANGELOG.md:2425 -msgid "" -"When federation is disabled, but ma1sd or Dimension are enabled, we'll " -"now expose the `openid` APIs on the federation port. These APIs are " -"necessary for some ma1sd features to work. If you'd like to prevent this," -" you can: `matrix_synapse_federation_port_openid_resource_required: " -"false`." +msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`." msgstr "" #: ../../../CHANGELOG.md:2428 @@ -7484,10 +4439,7 @@ msgid "Recent Jitsi updates may require configuration changes" msgstr "" #: ../../../CHANGELOG.md:2432 -msgid "" -"We've recently [updated from Jitsi build 4857 to build " -"5142](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/719), which brings a lot of configuration changes." +msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes." msgstr "" #: ../../../CHANGELOG.md:2434 @@ -7495,29 +4447,15 @@ msgid "**If you use our default Jitsi settings, you won't have to do anything.** msgstr "" #: ../../../CHANGELOG.md:2436 -msgid "" -"People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md" -"#optional-fine-tune-jitsi) may find that some options got renamed now, " -"others are gone and yet others still need to be defined in another way." +msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way." msgstr "" #: ../../../CHANGELOG.md:2438 -msgid "" -"The next time you run the playbook [installation](docs/installing.md) " -"command, our validation logic will tell you if you're using some " -"variables like that and will recommend a migration path for each one." +msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one." msgstr "" #: ../../../CHANGELOG.md:2440 -msgid "" -"Additionally, we've recently disabled transcriptions " -"(`jitsi_enable_transcriptions: false`) and recording " -"(`jitsi_enable_recording: false`) by default. These features did not work" -" anyway, because we don't install the required dependencies for them " -"(Jigasi and Jibri, respectively). If you've been somehow pointing your " -"Jitsi installation to some manually installed Jigasi/Jibri service, you " -"may need to toggle these flags back to enabled to have transcriptions and" -" recordings working." +msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working." msgstr "" #: ../../../CHANGELOG.md:2443 @@ -7529,18 +4467,11 @@ msgid "Breaking change matrix-sms-bridge" msgstr "" #: ../../../CHANGELOG.md:2447 -msgid "" -"Because of many problems using gammu as SMS provider, matrix-sms-bridge " -"now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by " -"default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-" -"sms.md] which new vars you need to add." +msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add." msgstr "" #: ../../../CHANGELOG.md:2449 -msgid "" -"If you are using this playbook to deploy matrix-sms-bridge and still " -"really want to use gammu as SMS provider, we could possibly add support " -"for both android-sms-gateway-server and gammu." +msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu." msgstr "" #: ../../../CHANGELOG.md:2451 @@ -7548,38 +4479,23 @@ msgid "2020-11-13" msgstr "" #: ../../../CHANGELOG.md:2455 -msgid "" -"The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-" -"sms-bridge) changed its database from neo4j to h2. You need to sync the " -"bridge at the first start. Note that this only will sync rooms where the " -"@smsbot:yourServer is member. For rooms without @smsbot:yourServer you " -"need to kick and invite the telephone number **or** invite " -"@smsbot:yourServer." +msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer." msgstr "" #: ../../../CHANGELOG.md:2457 -msgid "" -"Add the following to your `vars.yml` file: " -"`matrix_sms_bridge_container_extra_arguments=['--env " -"SPRING_PROFILES_ACTIVE=initialsync']`" +msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`" msgstr "" #: ../../../CHANGELOG.md:2458 -msgid "" -"Login to your host shell and remove old systemd file from your host: `rm " -"/etc/systemd/system/matrix-sms-bridge-database.service`" +msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`" msgstr "" #: ../../../CHANGELOG.md:2459 -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-" -"sms-bridge,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`" msgstr "" #: ../../../CHANGELOG.md:2460 -msgid "" -"Login to your host shell and check the logs with `journalctl -u matrix-" -"sms-bridge` until the sync finished." +msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished." msgstr "" #: ../../../CHANGELOG.md:2461 @@ -7587,9 +4503,7 @@ msgid "Remove the var from the first step." msgstr "" #: ../../../CHANGELOG.md:2462 -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-" -"all,start`." +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`." msgstr "" #: ../../../CHANGELOG.md:2464 @@ -7601,16 +4515,11 @@ msgid "Dynamic DNS support" msgstr "" #: ../../../CHANGELOG.md:2468 -msgid "" -"Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook " -"can now manage Dynamic DNS for you using " -"[ddclient](https://ddclient.net/)." +msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)." msgstr "" #: ../../../CHANGELOG.md:2470 -msgid "" -"To learn more, follow our [Dynamic DNS docs page](docs/configuring-" -"playbook-dynamic-dns.md)." +msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)." msgstr "" #: ../../../CHANGELOG.md:2473 @@ -7618,39 +4527,23 @@ msgid "2020-10-28" msgstr "" #: ../../../CHANGELOG.md:2475 -msgid "" -"(Compatibility Break) https://matrix.example.com/ now redirects to " -"https://element.example.com/" +msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/" msgstr "" #: ../../../CHANGELOG.md:2477 -msgid "" -"Until now, we used to serve a static page coming from Synapse at " -"`https://matrix.example.com/`. This page was not very useful to anyone." +msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone." msgstr "" #: ../../../CHANGELOG.md:2479 -msgid "" -"Since `matrix.example.com` may be accessed by regular users in certain " -"conditions, it's probably better to redirect them to a better place (e.g." -" to [Element Web](docs/configuring-playbook-client-element-web.md))." +msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))." msgstr "" #: ../../../CHANGELOG.md:2481 -msgid "" -"If Element Web is installed (`matrix_client_element_enabled: true`, which" -" it is by default), we now redirect people to it, instead of showing them" -" a Synapse static page." +msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page." msgstr "" #: ../../../CHANGELOG.md:2483 -msgid "" -"If you'd like to control where the redirect goes, use the " -"`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` " -"variable. To restore the old behavior of not redirecting anywhere and " -"serving the Synapse static page, set it to an empty value " -"(`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: " -"\"\"`)." +msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)." msgstr "" #: ../../../CHANGELOG.md:2486 @@ -7658,32 +4551,19 @@ msgid "2020-10-26" msgstr "" #: ../../../CHANGELOG.md:2488 -msgid "" -"(Compatibility Break) /_synapse/admin is no longer publicly exposed by " -"default" +msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default" msgstr "" #: ../../../CHANGELOG.md:2490 -msgid "" -"We used to expose the Synapse Admin APIs publicly (at " -"`https://matrix.example.com/_synapse/admin`). These APIs require " -"authentication with a valid access token, so it's not that big a deal to " -"expose them." +msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them." msgstr "" #: ../../../CHANGELOG.md:2492 -msgid "" -"However, following [official Synapse's reverse-proxying " -"recommendations](https://github.com/element-" -"hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-" -"endpoints), we're no longer exposing `/_synapse/admin` by default." +msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default." msgstr "" #: ../../../CHANGELOG.md:2494 -msgid "" -"If you'd like to restore restore the old behavior and expose " -"`/_synapse/admin` publicly, you can use the following configuration (in " -"your `vars.yml`):" +msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):" msgstr "" #: ../../../CHANGELOG.md:2501 @@ -7695,24 +4575,15 @@ msgid "Minimum Ansible version raised to v2.7.0" msgstr "" #: ../../../CHANGELOG.md:2505 -msgid "" -"We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 " -"and higher, but issues like [#662](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/662) demonstrate that we need at least " -"v2.7.0." +msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0." msgstr "" #: ../../../CHANGELOG.md:2507 -msgid "" -"If you've been using the playbook without getting any errors until now, " -"you're probably on a version higher than that already (or you're not " -"using the `matrix-ma1sd` and `matrix-client-element` roles)." +msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)." msgstr "" #: ../../../CHANGELOG.md:2509 -msgid "" -"Our [Ansible docs page](docs/ansible.md) contains information on how to " -"run a more up-to-date version of Ansible." +msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible." msgstr "" #: ../../../CHANGELOG.md:2512 @@ -7724,18 +4595,11 @@ msgid "Postgres 13 support" msgstr "" #: ../../../CHANGELOG.md:2516 -msgid "" -"The playbook now installs [Postgres " -"13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) " -"by default." +msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default." msgstr "" #: ../../../CHANGELOG.md:2518 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by " -"following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md" -"#upgrading-postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2520 @@ -7747,18 +4611,11 @@ msgid "matrix-registration support" msgstr "" #: ../../../CHANGELOG.md:2524 -msgid "" -"The playbook can now help you set up [matrix-" -"registration](https://github.com/ZerataX/matrix-registration) - an " -"application that lets you keep your Matrix server's registration private," -" but still allow certain users (those having a unique registration link) " -"to register by themselves." +msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves." msgstr "" #: ../../../CHANGELOG.md:2526 -msgid "" -"See our [Setting up matrix-registration](docs/configuring-playbook-" -"matrix-registration.md) documentation page to get started." +msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started." msgstr "" #: ../../../CHANGELOG.md:2529 @@ -7770,17 +4627,11 @@ msgid "rust-synapse-compress-state support" msgstr "" #: ../../../CHANGELOG.md:2533 -msgid "" -"The playbook can now help you use [rust-synapse-compress-" -"state](https://github.com/matrix-org/rust-synapse-compress-state) to " -"compress the state groups in your Synapse database." +msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database." msgstr "" #: ../../../CHANGELOG.md:2535 -msgid "" -"See our [Compressing state with rust-synapse-compress-state](docs" -"/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-" -"state) documentation page to get started." +msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started." msgstr "" #: ../../../CHANGELOG.md:2538 @@ -7792,15 +4643,11 @@ msgid "Synapse Admin support" msgstr "" #: ../../../CHANGELOG.md:2542 -msgid "" -"The playbook can now help you set up [synapse-admin](https://github.com" -"/Awesome-Technologies/synapse-admin)." +msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)." msgstr "" #: ../../../CHANGELOG.md:2544 -msgid "" -"See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-" -"admin.md) documentation to get started." +msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:2547 @@ -7812,15 +4659,11 @@ msgid "matrix-reminder-bot support" msgstr "" #: ../../../CHANGELOG.md:2551 -msgid "" -"The playbook can now help you set up [matrix-reminder-" -"bot](https://github.com/anoadragon453/matrix-reminder-bot)." +msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)." msgstr "" #: ../../../CHANGELOG.md:2553 -msgid "" -"See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-" -"matrix-reminder-bot.md) documentation to get started." +msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:2556 @@ -7832,21 +4675,15 @@ msgid "(Compatibility Break) Riot is now Element" msgstr "" #: ../../../CHANGELOG.md:2560 -msgid "" -"As per the official announcement, [Riot has been rebraned to " -"Element](https://element.io/blog/welcome-to-element/)." +msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)." msgstr "" #: ../../../CHANGELOG.md:2562 -msgid "" -"The playbook follows suit. Existing installations have a few options for " -"how to handle this." +msgid "The playbook follows suit. Existing installations have a few options for how to handle this." msgstr "" #: ../../../CHANGELOG.md:2564 -msgid "" -"See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md" -"#migrating-to-element) documentation page for more details." +msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details." msgstr "" #: ../../../CHANGELOG.md:2567 @@ -7858,12 +4695,7 @@ msgid "Steam bridging support via mx-puppet-steam" msgstr "" #: ../../../CHANGELOG.md:2571 -msgid "" -"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " -"playbook now supports bridging to [Steam](https://steamapp.com/) via the " -"[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge." -" See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-" -"bridge-mx-puppet-steam.md) documentation page for getting started." +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2574 @@ -7875,21 +4707,11 @@ msgid "Discord bridging support via mx-puppet-discord" msgstr "" #: ../../../CHANGELOG.md:2578 -msgid "" -"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " -"playbook now supports bridging to [Discord](https://discordapp.com/) via " -"the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) " -"bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-" -"playbook-bridge-mx-puppet-discord.md) documentation page for getting " -"started." +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2580 -msgid "" -"**Note**: this is a new Discord bridge. The playbook still retains " -"Discord bridging via [matrix-appservice-discord](docs/configuring-" -"playbook-bridge-appservice-discord.md). You're free too use the bridge " -"that serves you better, or even both (for different users and use-cases)." +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:2583 @@ -7901,23 +4723,11 @@ msgid "Instagram and Twitter bridging support" msgstr "" #: ../../../CHANGELOG.md:2587 -msgid "" -"Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s " -"efforts, the playbook now supports bridging to " -"[Instagram](https://www.instagram.com/) via the [mx-puppet-" -"instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See " -"our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-" -"bridge-mx-puppet-instagram.md) documentation page for getting started." +msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2589 -msgid "" -"Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the " -"playbook now supports bridging to [Twitter](https://twitter.com/) via the" -" [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) " -"bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-" -"playbook-bridge-mx-puppet-twitter.md) documentation page for getting " -"started." +msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2592 @@ -7925,31 +4735,19 @@ msgid "2020-06-28" msgstr "" #: ../../../CHANGELOG.md:2594 -msgid "" -"(Post Mortem / fixed Security Issue) Re-enabling User Directory search " -"powered by the ma1sd Identity Server" +msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server" msgstr "" #: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625 -msgid "" -"User Directory search requests used to go to the ma1sd identity server by" -" default, which queried its own stores and the Synapse database." +msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database." msgstr "" #: ../../../CHANGELOG.md:2598 -msgid "" -"ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has " -"been fixed in version `2.4.0`, with [this " -"commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd " -"2.4.0` is now the default version for this playbook. For more information" -" on what happened, please check the mentioned issue." +msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue." msgstr "" #: ../../../CHANGELOG.md:2600 -msgid "" -"We are re-enabling user directory search with this update. Those who " -"would like to keep it disabled can use this configuration: " -"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" +msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" msgstr "" #: ../../../CHANGELOG.md:2602 @@ -7965,20 +4763,11 @@ msgid "SMS bridging requires db reset" msgstr "" #: ../../../CHANGELOG.md:2608 -msgid "" -"The current version of [matrix-sms-bridge](https://github.com/benkuly" -"/matrix-sms-bridge) needs you to delete the database to work as expected." -" Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new " -"requried var `matrix_sms_bridge_default_region`." +msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`." msgstr "" #: ../../../CHANGELOG.md:2610 -msgid "" -"To reuse your existing rooms, invite `@smsbot:yourServer` to the room or " -"write a message. You are also able to use automated room creation with " -"telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a" -" room with `@smsbot:yourServer`. See [the " -"docs](https://github.com/benkuly/matrix-sms-bridge) for more information." +msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information." msgstr "" #: ../../../CHANGELOG.md:2612 @@ -7990,16 +4779,11 @@ msgid "SMS bridging support" msgstr "" #: ../../../CHANGELOG.md:2616 -msgid "" -"Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook " -"now supports bridging to SMS (with one telephone number only) via " -"[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." +msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." msgstr "" #: ../../../CHANGELOG.md:2618 -msgid "" -"See our [Setting up Matrix SMS bridging](docs/configuring-playbook-" -"bridge-matrix-bridge-sms.md) documentation page for getting started." +msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2621 @@ -8007,31 +4791,19 @@ msgid "2020-05-19" msgstr "" #: ../../../CHANGELOG.md:2623 -msgid "" -"(Compatibility Break / Security Issue) Disabling User Directory search " -"powered by the ma1sd Identity Server" +msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server" msgstr "" #: ../../../CHANGELOG.md:2627 -msgid "" -"ma1sd current has [a security " -"issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak " -"information about all users - including users created by bridges, etc." +msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc." msgstr "" #: ../../../CHANGELOG.md:2629 -msgid "" -"Until the issue gets fixed, we're making User Directory search not go to " -"ma1sd by default. You **need to re-run the playbook and restart services " -"to apply this workaround**." +msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**." msgstr "" #: ../../../CHANGELOG.md:2631 -msgid "" -"*If you insist on restoring the old behavior* (**which has a security " -"issue!**), you *might* use this configuration: " -"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ " -"matrix_ma1sd_enabled }}\"`" +msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`" msgstr "" #: ../../../CHANGELOG.md:2634 @@ -8043,14 +4815,7 @@ msgid "Newer IRC bridge (with potential breaking change)" msgstr "" #: ../../../CHANGELOG.md:2638 -msgid "" -"This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made" -" a change to how you define manual mappings. If you added a `mapping` to" -" your configuration, you will need to update it accoring to the [upstream" -" instructions](https://github.com/matrix-org/matrix-appservice-" -"irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include " -"`mappings` in your configuration for IRC, no change is necessary. " -"`mappings` is not part of the default configuration." +msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration." msgstr "" #: ../../../CHANGELOG.md:2647 @@ -8062,16 +4827,11 @@ msgid "Slack bridging support" msgstr "" #: ../../../CHANGELOG.md:2651 -msgid "" -"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " -"playbook now supports bridging to [Slack](https://slack.com) via the [mx-" -"puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." msgstr "" #: ../../../CHANGELOG.md:2653 -msgid "" -"See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-" -"bridge-mx-puppet-slack.md) documentation page for getting started." +msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2656 @@ -8083,16 +4843,11 @@ msgid "Skype bridging support" msgstr "" #: ../../../CHANGELOG.md:2660 -msgid "" -"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " -"playbook now supports bridging to [Skype](https://www.skype.com) via the " -"[mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." msgstr "" #: ../../../CHANGELOG.md:2662 -msgid "" -"See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-" -"bridge-mx-puppet-skype.md) documentation page for getting started." +msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2665 @@ -8104,24 +4859,15 @@ msgid "Private Jitsi support" msgstr "" #: ../../../CHANGELOG.md:2669 -msgid "" -"The [Jitsi support](#jitsi-support) we had landed a few weeks ago was " -"working well, but it was always open to the whole world." +msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world." msgstr "" #: ../../../CHANGELOG.md:2671 -msgid "" -"Running such an open instance is not desirable to most people, so " -"[teutat3s](https://github.com/teutat3s) has contributed support for " -"making Jitsi use authentication." +msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication." msgstr "" #: ../../../CHANGELOG.md:2673 -msgid "" -"To make your Jitsi server more private, see the [configure internal Jitsi" -" authentication and guests mode](docs/configuring-playbook-jitsi.md" -"#optional-configure-internal-jitsi-authentication-and-guests-mode) " -"section in our Jitsi documentation." +msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation." msgstr "" #: ../../../CHANGELOG.md:2676 @@ -8133,27 +4879,15 @@ msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" msgstr "" #: ../../../CHANGELOG.md:2680 -msgid "" -"Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the " -"[mxisd](https://github.com/kamax-io/mxisd) identity server, which has " -"been deprecated for a long time, has finally been replaced by " -"[ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." +msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." msgstr "" #: ../../../CHANGELOG.md:2682 -msgid "" -"**If you're using the default playbook configuration**, you don't need to" -" do anything -- your mxisd installation will be replaced with ma1sd and " -"all existing data will be migrated automatically the next time you run " -"the playbook." +msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2684 -msgid "" -"**If you're doing something more special** (defining custom " -"`matrix_mxisd_*` variables), the playbook will ask you to rename them to " -"`matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well " -"for such a more custom setup." +msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup." msgstr "" #: ../../../CHANGELOG.md:2687 @@ -8165,10 +4899,7 @@ msgid "Archlinux support" msgstr "" #: ../../../CHANGELOG.md:2691 -msgid "" -"Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts," -" the playbook now supports installing to an " -"[Archlinux](https://www.archlinux.org/) server." +msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server." msgstr "" #: ../../../CHANGELOG.md:2694 @@ -8180,16 +4911,11 @@ msgid "Jitsi support" msgstr "" #: ../../../CHANGELOG.md:2698 -msgid "" -"The playbook can now (optionally) install the [Jitsi](https://jitsi.org/)" -" video-conferencing platform and integrate it with [Riot](docs" -"/configuring-playbook-riot-web.md)." +msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)." msgstr "" #: ../../../CHANGELOG.md:2700 -msgid "" -"See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to" -" get started." +msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started." msgstr "" #: ../../../CHANGELOG.md:2703 @@ -8201,18 +4927,11 @@ msgid "Raspberry Pi support" msgstr "" #: ../../../CHANGELOG.md:2707 -msgid "" -"Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the " -"playbook supports installing to a Raspberry Pi server, for at least some " -"of the services." +msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services." msgstr "" #: ../../../CHANGELOG.md:2709 -msgid "" -"Since most ready-made container images do not support that architecture, " -"we achieve this by building images locally on the device itself. See our " -"[Self-building documentation page](docs/self-building.md) for how to get " -"started." +msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started." msgstr "" #: ../../../CHANGELOG.md:2712 @@ -8228,9 +4947,7 @@ msgid "The playbook now makes it easy to install custom riot-web themes." msgstr "" #: ../../../CHANGELOG.md:2718 -msgid "" -"To learn more, take a look at our [riot-web documentation on Themes](docs" -"/configuring-playbook-riot-web.md#themes)." +msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)." msgstr "" #: ../../../CHANGELOG.md:2721 @@ -8242,9 +4959,7 @@ msgid "Customize the server name in Riot's login page" msgstr "" #: ../../../CHANGELOG.md:2725 -msgid "" -"You can now customize the server name string that Riot-web displays in " -"its login page." +msgid "You can now customize the server name string that Riot-web displays in its login page." msgstr "" #: ../../../CHANGELOG.md:2727 @@ -8252,18 +4967,11 @@ msgid "These playbook variables, with these default values, have been added:" msgstr "" #: ../../../CHANGELOG.md:2733 -msgid "" -"The login page previously said \"Sign in to your Matrix account on " -"matrix.example.org\" (the homeserver's domain name). It will now say " -"\"Sign in … on example.org\" (the server name) by default, or \"Sign in …" -" on Our Server\" if you set the variable to \"Our Server\"." +msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"." msgstr "" #: ../../../CHANGELOG.md:2735 -msgid "" -"To support this, the config.json template is changed to use the " -"configuration key `default_server_config` for setting the default HS/IS, " -"and the new configuration key `server_name` is added in there." +msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there." msgstr "" #: ../../../CHANGELOG.md:2738 @@ -8275,16 +4983,11 @@ msgid "Disabling TLSv1.1" msgstr "" #: ../../../CHANGELOG.md:2742 -msgid "" -"To improve security, we've removed TLSv1.1 support from our default " -"matrix-nginx-proxy configuration." +msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration." msgstr "" #: ../../../CHANGELOG.md:2744 -msgid "" -"If you need to support old clients, you can re-enable it with the " -"following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 " -"TLSv1.2 TLSv1.3\"`" +msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`" msgstr "" #: ../../../CHANGELOG.md:2747 @@ -8296,21 +4999,11 @@ msgid "Postgres collation changes (action required!)" msgstr "" #: ../../../CHANGELOG.md:2751 -msgid "" -"By default, we've been using a UTF-8 collation for Postgres. This is " -"known to cause Synapse some troubles (see the [relevant " -"issue](https://github.com/matrix-org/synapse/issues/6722)) on systems " -"that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in " -"an [Alpine Linux](https://alpinelinux.org/) container (which uses " -"[musl](https://www.musl-libc.org/), and not glibc), so our users are " -"likely not affected by the index corruption problem observed by others." +msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others." msgstr "" #: ../../../CHANGELOG.md:2753 -msgid "" -"Still, we might become affected in the future. In any case, it's imminent" -" that Synapse will complain about databases which do not use a C " -"collation." +msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation." msgstr "" #: ../../../CHANGELOG.md:2755 @@ -8318,11 +5011,7 @@ msgid "To avoid future problems, we recommend that you run the following command msgstr "" #: ../../../CHANGELOG.md:2761 -msgid "" -"It forces a [Postgres database upgrade](docs/maintenance-postgres.md" -"#upgrading-postgresql), which would recreate your Postgres database using" -" the proper (`C`) collation. If you are low on disk space, or run into " -"trouble, refer to the Postgres database upgrade documentation page." +msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page." msgstr "" #: ../../../CHANGELOG.md:2764 @@ -8334,19 +5023,11 @@ msgid "Added support for Appservice Webhooks" msgstr "" #: ../../../CHANGELOG.md:2768 -msgid "" -"Thanks to a contribution from [Björn " -"Marten](https://github.com/tripleawwy) from " -"[netresearch](https://www.netresearch.de/), the playbook can now install " -"and configure [matrix-appservice-webhooks](https://github.com/turt2live" -"/matrix-appservice-webhooks) for you. This bridge provides support for " -"Slack-compatible webhooks." +msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" #: ../../../CHANGELOG.md:2770 -msgid "" -"Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-" -"playbook-bridge-appservice-webhooks.md)." +msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)." msgstr "" #: ../../../CHANGELOG.md:2773 @@ -8358,23 +5039,15 @@ msgid "Added support for automatic Double Puppeting for all Mautrix bridges" msgstr "" #: ../../../CHANGELOG.md:2777 -msgid "" -"Double Puppeting can now be easily enabled for all Mautrix bridges " -"supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." +msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." msgstr "" #: ../../../CHANGELOG.md:2779 -msgid "" -"This is possible due to those bridges' integration with [matrix-synapse-" -"shared-secret-auth](https://github.com/devture/matrix-synapse-shared-" -"secret-auth) - yet another component that this playbook can install for " -"you." +msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you." msgstr "" #: ../../../CHANGELOG.md:2781 -msgid "" -"To get started, following the playbook's documentation for the bridge " -"you'd like to configure." +msgid "To get started, following the playbook's documentation for the bridge you'd like to configure." msgstr "" #: ../../../CHANGELOG.md:2784 @@ -8386,25 +5059,15 @@ msgid "Added support for an alternative method for using another webserver" msgstr "" #: ../../../CHANGELOG.md:2788 -msgid "" -"We have added support for making `matrix-nginx-proxy` not being so " -"invasive, so that it would be easier to [use your own webserver](docs" -"/configuring-playbook-own-webserver.md)." +msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)." msgstr "" #: ../../../CHANGELOG.md:2790 -msgid "" -"The documentation has been updated with a **Method 2**, which might make " -"\"own webserver\" setup easier in some cases (such as [reverse-proxying " -"using Traefik](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/296))." +msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))." msgstr "" #: ../../../CHANGELOG.md:2792 -msgid "" -"**Existing users** are not affected by this and **don't need to change " -"anything**. The defaults are still the same (`matrix-nginx-proxy` " -"obtaining SSL certificates and doing everything for you automatically)." +msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)." msgstr "" #: ../../../CHANGELOG.md:2795 @@ -8416,27 +5079,15 @@ msgid "Tightened security around room directory publishing" msgstr "" #: ../../../CHANGELOG.md:2799 -msgid "" -"As per this [advisory blog post](https://matrix.org/blog/2019/11/09" -"/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to" -" change the default publishing rules for the Matrix room directory." +msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory." msgstr "" #: ../../../CHANGELOG.md:2801 -msgid "" -"Our general goal is to favor privacy and security when running personal " -"(family & friends) and corporate homeservers. Both of these likely " -"benefit from having a more secure default of **not showing the room " -"directory without authentication** and **not publishing the room " -"directory over federation**." +msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**." msgstr "" #: ../../../CHANGELOG.md:2803 -msgid "" -"As with anything else, these new defaults can be overriden by changing " -"the `matrix_synapse_allow_public_rooms_without_auth` and " -"`matrix_synapse_allow_public_rooms_over_federation` variables, " -"respectively." +msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively." msgstr "" #: ../../../CHANGELOG.md:2806 @@ -8448,35 +5099,19 @@ msgid "Improved Postgres upgrading/importing" msgstr "" #: ../../../CHANGELOG.md:2810 -msgid "" -"Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) " -"and [importing](docs/importing-postgres.md) have been improved to add " -"support for multiple databases and roles." +msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles." msgstr "" #: ../../../CHANGELOG.md:2812 -msgid "" -"Previously, the playbook would only take care of the `homeserver` " -"database and `synapse` user. We now back up and restore all databases and" -" users on the Postgres server." +msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server." msgstr "" #: ../../../CHANGELOG.md:2814 -msgid "" -"For now, the playbook only uses that one database (`homeserver`) and that" -" one single user (`synapse`), so it's all the same. However, in the " -"future, additional components besides Synapse may also make use the " -"Postgres database server. One such example is the [matrix-appservice-" -"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, " -"which strongly encourages use of Postgres in its v1.0 release. We are yet" -" to upgrade to it." +msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it." msgstr "" #: ../../../CHANGELOG.md:2816 -msgid "" -"Additionally, Postgres [upgrading](docs/maintenance-postgres.md" -"#upgrading-postgresql) now uses gzipped dump files by default, to " -"minimize disk space usage." +msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage." msgstr "" #: ../../../CHANGELOG.md:2819 @@ -8488,17 +5123,11 @@ msgid "Postgres 12 support" msgstr "" #: ../../../CHANGELOG.md:2823 -msgid "" -"The playbook now installs [Postgres " -"12](https://www.postgresql.org/about/news/1976/) by default." +msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default." msgstr "" #: ../../../CHANGELOG.md:2825 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following" -" the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" -"postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2828 @@ -8510,46 +5139,19 @@ msgid "Synapse 1.4.0" msgstr "" #: ../../../CHANGELOG.md:2832 -msgid "" -"Synapse 1.4.0 [is " -"out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots" -" of changes related to privacy." +msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy." msgstr "" #: ../../../CHANGELOG.md:2834 -msgid "" -"Its new defaults (which we adopt as well) mean that certain old data will" -" automatically get purged after a certain number of days. 1.4.0 " -"automatically garbage collects redacted messages (defaults to 7 days) and" -" removes unused IP and user agent information stored in the user_ips " -"table (defaults to 30 days). If you'd like to preserve this data, we " -"encourage you to look at the `redaction_retention_period` and " -"`user_ips_max_age` options (controllable by the " -"`matrix_synapse_redaction_retention_period` and " -"`matrix_synapse_user_ips_max_age` playbook variables, respectively) " -"before doing the upgrade. If you'd like to keep data indefinitely, set " -"these variables to `null` (e.g. " -"`matrix_synapse_redaction_retention_period: ~`)." +msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)." msgstr "" #: ../../../CHANGELOG.md:2836 -msgid "" -"From now on the `trusted_key_servers` setting for Synapse is " -"configurable. It still defaults to `matrix.org` just like it always has, " -"but in a more explicit way now. If you'd like to use another trusted key " -"server, adjust the `matrix_synapse_trusted_key_servers` playbook " -"variable." +msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable." msgstr "" #: ../../../CHANGELOG.md:2838 -msgid "" -"Synapse 1.4.0 also changes lots of things related to identity server " -"integration. Because Synapse will now by default be responsible for " -"validating email addresses for user accounts, running without an identity" -" server looks more feasible. We still [have " -"concerns](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/275/files#r331104117) over disabling the identity server by " -"default, so for now it remains enabled." +msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled." msgstr "" #: ../../../CHANGELOG.md:2841 @@ -8561,23 +5163,15 @@ msgid "Synapse Simple Antispam support" msgstr "" #: ../../../CHANGELOG.md:2845 -msgid "" -"There have been lots of invite-spam attacks lately and " -"[Travis](https://github.com/t2bot) has created a Synapse module " -"([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" -"antispam)) to let people protect themselves." +msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves." msgstr "" #: ../../../CHANGELOG.md:2847 -msgid "" -"From now on, you can easily install and configure this spam checker " -"module through the playbook." +msgid "From now on, you can easily install and configure this spam checker module through the playbook." msgstr "" #: ../../../CHANGELOG.md:2849 -msgid "" -"Learn more in [Setting up Synapse Simple Antispam](docs/configuring-" -"playbook-synapse-simple-antispam.md)." +msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)." msgstr "" #: ../../../CHANGELOG.md:2852 @@ -8589,29 +5183,19 @@ msgid "Extensible Riot-web configuration" msgstr "" #: ../../../CHANGELOG.md:2856 -msgid "" -"Similarly to [Extensible Synapse configuration](#extensible-synapse-" -"configuration) (below), Riot-web configuration is also extensible now." +msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now." msgstr "" #: ../../../CHANGELOG.md:2858 -msgid "" -"From now on, you can extend/override Riot-web's configuration by making " -"use of the `matrix_riot_web_configuration_extension_json` variable. This " -"should be enough for most customization needs." +msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs." msgstr "" #: ../../../CHANGELOG.md:2860 -msgid "" -"If you need even more power, you can now also take full control and " -"override `matrix_riot_web_configuration_default` (or " -"`matrix_riot_web_configuration`) directly." +msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly." msgstr "" #: ../../../CHANGELOG.md:2862 -msgid "" -"Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-" -"web.md)." +msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)." msgstr "" #: ../../../CHANGELOG.md:2865 @@ -8623,31 +5207,19 @@ msgid "Extensible Synapse configuration" msgstr "" #: ../../../CHANGELOG.md:2869 -msgid "" -"Previously, we had to create custom Ansible variables for each and every " -"Synapse setting. This lead to too much effort (and configuration " -"ugliness) to all of Synapse's settings, so naturally, not all features of" -" Synapse could be controlled through the playbook." +msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook." msgstr "" #: ../../../CHANGELOG.md:2871 -msgid "" -"From now on, you can extend/override the Synapse server's configuration " -"by making use of the `matrix_synapse_configuration_extension_yaml` " -"variable. This should be enough for most customization needs." +msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs." msgstr "" #: ../../../CHANGELOG.md:2873 -msgid "" -"If you need even more power, you can now also take full control and " -"override `matrix_synapse_configuration` (or " -"`matrix_synapse_configuration_yaml`) directly." +msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly." msgstr "" #: ../../../CHANGELOG.md:2875 -msgid "" -"Learn more here in [Configuring Synapse](docs/configuring-playbook-" -"synapse.md)." +msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)." msgstr "" #: ../../../CHANGELOG.md:2878 @@ -8655,19 +5227,11 @@ msgid "2019-08-21" msgstr "" #: ../../../CHANGELOG.md:2882 -msgid "" -"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/205) of " -"[kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart " -"Mumford (Cadair)](https://github.com/Cadair), the playbook now supports " -"bridging to [Slack](https://slack.com) via the [appservice-" -"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." msgstr "" #: ../../../CHANGELOG.md:2884 -msgid "" -"Additional details are available in [Setting up Appservice Slack " -"bridging](docs/configuring-playbook-bridge-appservice-slack.md)." +msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)." msgstr "" #: ../../../CHANGELOG.md:2886 @@ -8675,19 +5239,11 @@ msgid "Google Hangouts bridging support" msgstr "" #: ../../../CHANGELOG.md:2888 -msgid "" -"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/251) of [Eduardo Beltrame " -"(Munfred)](https://github.com/Munfred) and [Robbie D " -"(microchipster)](https://github.com/microchipster), the playbook now " -"supports bridging to [Google Hangouts](https://hangouts.google.com/) via " -"the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." msgstr "" #: ../../../CHANGELOG.md:2890 -msgid "" -"Additional details are available in [Setting up Mautrix Hangouts " -"bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." +msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." msgstr "" #: ../../../CHANGELOG.md:2893 @@ -8699,9 +5255,7 @@ msgid "Email2Matrix support" msgstr "" #: ../../../CHANGELOG.md:2897 -msgid "" -"Support for [Email2Matrix](https://github.com/devture/email2matrix) has " -"been added." +msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added." msgstr "" #: ../../../CHANGELOG.md:2899 @@ -8709,9 +5263,7 @@ msgid "It's an optional feature that you can enable via the playbook." msgstr "" #: ../../../CHANGELOG.md:2901 -msgid "" -"To learn more, see the [playbook's documentation on Email2Matrix](./docs" -"/configuring-playbook-email2matrix.md)." +msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)." msgstr "" #: ../../../CHANGELOG.md:2904 @@ -8723,17 +5275,11 @@ msgid "Synapse logging level has been reduced to WARNING" msgstr "" #: ../../../CHANGELOG.md:2908 -msgid "" -"After [some discussion in our support " -"room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one)," -" we've decided to change the default logging level for Synapse from " -"`INFO` to `WARNING`." +msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`." msgstr "" #: ../../../CHANGELOG.md:2910 -msgid "" -"This greatly reduces the number of log messages that are being logged, " -"leading to:" +msgid "This greatly reduces the number of log messages that are being logged, leading to:" msgstr "" #: ../../../CHANGELOG.md:2912 @@ -8741,17 +5287,11 @@ msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" msgstr "" #: ../../../CHANGELOG.md:2913 -msgid "" -"easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages," -" as they're not longer buried in thousands of non-important `INFO` " -"messages" +msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages" msgstr "" #: ../../../CHANGELOG.md:2915 -msgid "" -"If you'd like to track down an issue, you [can always increase the " -"logging level as described here](./docs/maintenance-and-" -"troubleshooting.md#increasing-synapse-logging)." +msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)." msgstr "" #: ../../../CHANGELOG.md:2918 @@ -8767,18 +5307,11 @@ msgid "The playbook can now help you with Synapse's maintenance." msgstr "" #: ../../../CHANGELOG.md:2924 -msgid "" -"There's a new documentation page about [Synapse maintenance](./docs" -"/maintenance-synapse.md) and another section on [Postgres " -"vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." +msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2926 -msgid "" -"Among other things, if your Postgres database has grown significantly " -"over time, you may wish to [ask the playbook to purge unused data with " -"synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-" -"synapse-janitor) for you." +msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you." msgstr "" #: ../../../CHANGELOG.md:2928 @@ -8790,10 +5323,7 @@ msgid "Some internal playbook control variables have been renamed." msgstr "" #: ../../../CHANGELOG.md:2932 -msgid "" -"This change **only affects people who run this playbook's roles from " -"another playbook**. If you're using this playbook as-is, you're not " -"affected and don't need to do anything." +msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:2934 @@ -8833,23 +5363,15 @@ msgid "Synapse no longer logs to text files" msgstr "" #: ../../../CHANGELOG.md:2948 -msgid "" -"Following what the official Synapse Docker image is doing " -"([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've" -" been doing for mostly everything installed by this playbook, **Synapse " -"no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." +msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." msgstr "" #: ../../../CHANGELOG.md:2950 -msgid "" -"From now on, Synapse would only log to console, which goes to systemd's " -"journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" +msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" msgstr "" #: ../../../CHANGELOG.md:2952 -msgid "" -"Because of this, the following variables have become obsolete and were " -"removed:" +msgid "Because of this, the following variables have become obsolete and were removed:" msgstr "" #: ../../../CHANGELOG.md:2954 @@ -8861,23 +5383,11 @@ msgid "`matrix_synapse_max_log_files_count`" msgstr "" #: ../../../CHANGELOG.md:2957 -msgid "" -"To prevent confusion, it'd be better if you delete all old files manually" -" after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." +msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." msgstr "" #: ../../../CHANGELOG.md:2959 -msgid "" -"Because Synapse is incredibly chatty when it comes to logging (here's " -"[one such issue](https://github.com/matrix-org/synapse/issues/4751) " -"describing the problem), if you're running an ancient distribution (like " -"CentOS 7.0), be advised that systemd's journald default logging " -"restrictions may not be high enough to capture all log messages generated" -" by Synapse. This is especially true if you've got a busy (Synapse) " -"server. We advise that you manually add `RateLimitInterval=0` and " -"`RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` " -"file, followed by restarting the logging service (`systemctl restart " -"systemd-journald`)." +msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)." msgstr "" #: ../../../CHANGELOG.md:2962 @@ -8885,16 +5395,11 @@ msgid "2019-06-27" msgstr "" #: ../../../CHANGELOG.md:2964 -msgid "" -"(BC Break) Discord bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:2966 -msgid "" -"Until now, the `config.yaml` file for the [Discord bridge](docs" -"/configuring-playbook-bridge-appservice-discord.md) was managed by the " -"playbook, but the `registration.yaml` file was not." +msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not." msgstr "" #: ../../../CHANGELOG.md:2968 @@ -8902,41 +5407,23 @@ msgid "From now on, the playbook will keep both configuration files sync for you msgstr "" #: ../../../CHANGELOG.md:2970 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/appservice-discord/discord-registration.yaml` configuration file, those " -"would be lost the next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2972 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix" -"/appservice-discord/config`)." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)." msgstr "" #: ../../../CHANGELOG.md:2974 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/appservice-" -"discord/data`). When you run the playbook with an existing database file " -"(`/matrix/appservice-discord/discord.db`), the playbook will stop the " -"bridge and relocate the database file to the `./data` directory. There's " -"no data-loss involved. You'll need to restart the bridge manually though " -"(`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:2976 -msgid "" -"The main directory (`/matrix/appservice-discord`) may contain some " -"leftover files (`user-store.db`, `room-store.db`, `config.yaml`, " -"`discord-registration.yaml`, `invite_link`). These are no longer " -"necessary and can be deleted manually." +msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually." msgstr "" #: ../../../CHANGELOG.md:2978 -msgid "" -"We're now following the default sample configuration for the Discord " -"bridge. If you need to override some values, define them in " -"`matrix_appservice_discord_configuration_extension_yaml`." +msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`." msgstr "" #: ../../../CHANGELOG.md:2981 @@ -8944,16 +5431,11 @@ msgid "2019-06-24" msgstr "" #: ../../../CHANGELOG.md:2983 -msgid "" -"(BC Break) WhatsApp bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:2985 -msgid "" -"Until now, configuration files for the [WhatsApp bridge](docs" -"/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004 @@ -8962,31 +5444,15 @@ msgid "From now on, the playbook will keep the configuration in sync for you." msgstr "" #: ../../../CHANGELOG.md:2989 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-" -"whatsapp/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2991 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"whatsapp/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:2993 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"whatsapp/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:2995 @@ -8998,65 +5464,31 @@ msgid "2019-06-20" msgstr "" #: ../../../CHANGELOG.md:3000 -msgid "" -"(BC Break) IRC bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3002 -msgid "" -"Until now, configuration files for the [IRC bridge](docs/configuring-" -"playbook-bridge-appservice-irc.md) were created by the playbook " -"initially, but never modified later on." +msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3006 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/appservice-irc/config.yaml` or `/matrix/appservice-" -"irc/registration.yaml` configuration files, those would be lost the next " -"time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3008 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix" -"/appservice-irc/config`), so your old configuration remains in the base " -"directory (`/matrix/appservice-irc`)." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)." msgstr "" #: ../../../CHANGELOG.md:3010 -msgid "" -"Previously, we asked people to configure bridged IRC servers by extending" -" the bridge configuration " -"(`matrix_appservice_irc_configuration_extension_yaml`). While this is " -"still possible and will continue working forever, **we now recommend " -"defining IRC servers in the easier to use " -"`matrix_appservice_irc_ircService_servers` variable**. See [our IRC " -"bridge documentation page](docs/configuring-playbook-bridge-appservice-" -"irc.md) for an example." +msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example." msgstr "" #: ../../../CHANGELOG.md:3012 -msgid "" -"If you decide to continue using " -"`matrix_appservice_irc_configuration_extension_yaml`, you might be " -"interested to know that `ircService.databaseUri` and a few other keys now" -" have default values in the base configuration " -"(`matrix_appservice_irc_configuration_yaml`). You may wish to stop " -"redefining those keys, unless you really intend to override them. You " -"most likely only need to override `ircService.servers`." +msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`." msgstr "" #: ../../../CHANGELOG.md:3014 -msgid "" -"Bridge data (`passkey.pem` and database files) is now also stored in a " -"subdirectory (`/matrix/appservice-irc/data`). When you run the playbook " -"with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook " -"will stop the bridge and relocate the passkey and database files " -"(`rooms.db` and `users.db`) to the `./data` directory. There's no data-" -"loss involved. You'll need to restart the bridge manually though " -"(`--tags=start`)." +msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3017 @@ -9064,85 +5496,47 @@ msgid "2019-06-15" msgstr "" #: ../../../CHANGELOG.md:3019 -msgid "" -"(BC Break) Telegram bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3021 -msgid "" -"Until now, configuration files for the [Telegram bridge](docs" -"/configuring-playbook-bridge-mautrix-telegram.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3025 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-telegram/config.yaml` or `/matrix/mautrix-" -"telegram/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3027 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"telegram/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-telegram`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_telegram_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:3029 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"telegram/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3031 -msgid "" -"Also, we're now following the default configuration for the Telegram " -"bridge, so some default configuration values are different:" +msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:" msgstr "" #: ../../../CHANGELOG.md:3033 -msgid "" -"`edits_as_replies` (used to be `false`, now `true`) - previously replies " -"were not sent over to Matrix at all; ow they are sent over as a reply to " -"the original message" +msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message" msgstr "" #: ../../../CHANGELOG.md:3034 -msgid "" -"`inline_images` (used to be `true`, now `false`) - this has to do with " -"captioned images. Inline-image (included caption) are said to exhibit " -"troubles on Riot iOS. When `false`, the caption arrives on the Matrix " -"side as a separate message." +msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message." msgstr "" #: ../../../CHANGELOG.md:3035 -msgid "" -"`authless_portals` (used to be `false`, now `true`) - creating portals " -"from the Telegram side is now possible" +msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible" msgstr "" #: ../../../CHANGELOG.md:3036 -msgid "" -"`whitelist_group_admins` (used to be `false`, now `true`) - allows " -"Telegram group admins to use the bot commands" +msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands" msgstr "" #: ../../../CHANGELOG.md:3038 -msgid "" -"If the new values are not to your liking, use " -"`matrix_mautrix_telegram_configuration_extension_yaml` to specify an " -"override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure" -" out which variable goes where)." +msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)." msgstr "" #: ../../../CHANGELOG.md:3041 @@ -9154,45 +5548,23 @@ msgid "Synapse v1.0" msgstr "" #: ../../../CHANGELOG.md:3045 -msgid "" -"With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11" -"/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people " -"being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` " -"DNS SRV record that we've been keeping for compatibility with old Synapse" -" versions (<= 0.34)." +msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)." msgstr "" #: ../../../CHANGELOG.md:3047 -msgid "" -"According to the [Server Discovery " -"specification](https://matrix.org/docs/spec/server_server/r0.1.2.html" -"#server-discovery), it's no harm to keep the DNS SRV record. But since " -"it's not necessary for federating with the larger Matrix network anymore," -" you should be safe to get rid of it." +msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it." msgstr "" #: ../../../CHANGELOG.md:3049 -msgid "" -"**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` " -"DNS SRV records. The latter, **must not** be removed." +msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed." msgstr "" #: ../../../CHANGELOG.md:3051 -msgid "" -"For completeness, we must say that using a `_matrix._tcp` [SRV record for" -" Server Delegation](docs/howto-server-delegation.md#server-delegation-" -"via-a-dns-srv-record-advanced) is still valid and useful for certain " -"deployments. It's just that our guide recommends the [`/.well-" -"known/matrix/server` Server Delegation method](docs/howto-server-" -"delegation.md#server-delegation-via-a-well-known-file), due to its easier" -" implementation when using this playbook." +msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook." msgstr "" #: ../../../CHANGELOG.md:3053 -msgid "" -"Besides this optional/non-urgent DNS change, assuming you're already on " -"Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-" -"running the playbook](docs/maintenance-upgrading-services.md)." +msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)." msgstr "" #: ../../../CHANGELOG.md:3056 @@ -9200,44 +5572,23 @@ msgid "2019-06-07" msgstr "" #: ../../../CHANGELOG.md:3058 -msgid "" -"(BC Break) Facebook bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3060 -msgid "" -"Until now, configuration files for the [Facebook bridge](docs" -"/configuring-playbook-bridge-mautrix-facebook.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3064 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-facebook/config.yaml` or `/matrix/mautrix-" -"facebook/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3066 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"facebook/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-facebook`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_facebook_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:3068 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"facebook/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3071 @@ -9249,33 +5600,19 @@ msgid "Support for exposing container ports publicly (not just to the host)" msgstr "" #: ../../../CHANGELOG.md:3075 -msgid "" -"Until now, various roles supported a `matrix_*_expose_port` variable, " -"which would expose their container's port to the host. This was mostly " -"useful for reverse-proxying manually (in case `matrix-nginx-proxy` was " -"disabled). It could also be used for installing some playbook services " -"(e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." +msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." msgstr "" #: ../../../CHANGELOG.md:3077 -msgid "" -"`matrix_*_expose_port` variables were not granular enough - sometimes " -"they would expose one port, other times multiple. They also didn't " -"provide control over **where** to expose (to which port number and to " -"which network interface), because they would usually hardcode something " -"like `127.0.0.1:8080`." +msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`." msgstr "" #: ../../../CHANGELOG.md:3079 -msgid "" -"All such variables have been superseded by a better (more flexible) way " -"to do it." +msgid "All such variables have been superseded by a better (more flexible) way to do it." msgstr "" #: ../../../CHANGELOG.md:3081 -msgid "" -"**Most** people (including those not using `matrix-nginx-proxy`), **don't" -" need** to bother with this." +msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this." msgstr "" #: ../../../CHANGELOG.md:3083 @@ -9283,70 +5620,43 @@ msgid "Porting examples follow for people having more customized setups:" msgstr "" #: ../../../CHANGELOG.md:3085 -msgid "" -"**from** `matrix_synapse_container_expose_client_api_port: true` **to** " -"`matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" +msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" msgstr "" #: ../../../CHANGELOG.md:3087 -msgid "" -"**from** `matrix_synapse_container_expose_federation_api_port: true` " -"**to** `matrix_synapse_container_federation_api_plain_host_bind_port: " -"'127.0.0.1:8048'` and possibly " -"`matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" +msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" msgstr "" #: ../../../CHANGELOG.md:3089 -msgid "" -"**from** `matrix_synapse_container_expose_metrics_port: true` **to** " -"`matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" +msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" msgstr "" #: ../../../CHANGELOG.md:3091 -msgid "" -"**from** `matrix_riot_web_container_expose_port: true` **to** " -"`matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" +msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" msgstr "" #: ../../../CHANGELOG.md:3093 -msgid "" -"**from** `matrix_mxisd_container_expose_port: true` **to** " -"`matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" +msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" msgstr "" #: ../../../CHANGELOG.md:3095 -msgid "" -"**from** `matrix_dimension_container_expose_port: true` **to** " -"`matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" +msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" msgstr "" #: ../../../CHANGELOG.md:3097 -msgid "" -"**from** `matrix_corporal_container_expose_ports: true` **to** " -"`matrix_corporal_container_http_gateway_host_bind_port: " -"'127.0.0.1:41080'` and possibly " -"`matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" +msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" msgstr "" #: ../../../CHANGELOG.md:3099 -msgid "" -"**from** `matrix_appservice_irc_container_expose_client_server_api_port: " -"true` **to** `matrix_appservice_irc_container_http_host_bind_port: " -"'127.0.0.1:9999'`" +msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`" msgstr "" #: ../../../CHANGELOG.md:3101 -msgid "" -"**from** " -"`matrix_appservice_discord_container_expose_client_server_api_port: true`" -" **to** `matrix_appservice_discord_container_http_host_bind_port: " -"'127.0.0.1:9005'`" +msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`" msgstr "" #: ../../../CHANGELOG.md:3103 -msgid "" -"As always, if you forget to remove usage of some outdated variable, the " -"playbook will warn you." +msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you." msgstr "" #: ../../../CHANGELOG.md:3106 @@ -9358,17 +5668,11 @@ msgid "(BC Break) Ansible 2.8 compatibility" msgstr "" #: ../../../CHANGELOG.md:3110 -msgid "" -"Thanks to [@danbob](https://github.com/danbob), the playbook now " -"[supports the new Ansible 2.8](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/187)." +msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)." msgstr "" #: ../../../CHANGELOG.md:3112 -msgid "" -"A manual change is required to the `inventory/hosts` file, changing the " -"group name from `matrix-servers` to `matrix_servers` (dash to " -"underscore)." +msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)." msgstr "" #: ../../../CHANGELOG.md:3114 @@ -9392,30 +5696,19 @@ msgid "Synapse no longer required" msgstr "" #: ../../../CHANGELOG.md:3123 -msgid "" -"The playbook no longer insists on installing [Synapse](https://github.com" -"/element-hq/synapse) via the `matrix-synapse` role." +msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role." msgstr "" #: ../../../CHANGELOG.md:3125 -msgid "" -"If you would prefer to install Synapse another way and just use the " -"playbook to install other services, it should be possible " -"(`matrix_synapse_enabled: false`)." +msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)." msgstr "" #: ../../../CHANGELOG.md:3127 -msgid "" -"Note that it won't necessarily be the best experience, since the playbook" -" wires things to Synapse by default. If you're using your own Synapse " -"instance (especially one not running in a container), you may have to " -"override many variables to point them to the correct place." +msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place." msgstr "" #: ../../../CHANGELOG.md:3129 -msgid "" -"Having Synapse not be a required component potentially opens the door for" -" installing alternative Matrix homeservers." +msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers." msgstr "" #: ../../../CHANGELOG.md:3131 @@ -9423,16 +5716,11 @@ msgid "Bridges are now separate from the Synapse role" msgstr "" #: ../../../CHANGELOG.md:3133 -msgid "" -"Bridges are no longer part of the `matrix-synapse` role. Each bridge now " -"lives in its own separate role (`roles/custom/matrix-bridge-*`)." +msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)." msgstr "" #: ../../../CHANGELOG.md:3135 -msgid "" -"These bridge roles are independent of the `matrix-synapse` role, so it " -"should be possible to use them with a Synapse instance installed another " -"way (not through the playbook)." +msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)." msgstr "" #: ../../../CHANGELOG.md:3137 @@ -9444,21 +5732,15 @@ msgid "For better consistency, the following variables have been renamed:" msgstr "" #: ../../../CHANGELOG.md:3141 -msgid "" -"`matrix_enable_room_list_search` was renamed to " -"`matrix_synapse_enable_room_list_search`" +msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`" msgstr "" #: ../../../CHANGELOG.md:3142 -msgid "" -"`matrix_alias_creation_rules` was renamed to " -"`matrix_synapse_alias_creation_rules`" +msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`" msgstr "" #: ../../../CHANGELOG.md:3143 -msgid "" -"`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was " -"renamed to `matrix_synapse_room_list_publication_rules`" +msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`" msgstr "" #: ../../../CHANGELOG.md:3146 @@ -9466,9 +5748,7 @@ msgid "2019-05-09" msgstr "" #: ../../../CHANGELOG.md:3148 -msgid "" -"Besides a myriad of bug fixes and minor improvements, here are the more " -"notable (bigger) features we can announce today." +msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today." msgstr "" #: ../../../CHANGELOG.md:3150 @@ -9476,18 +5756,11 @@ msgid "Mautrix Facebook/Messenger bridging support" msgstr "" #: ../../../CHANGELOG.md:3152 -msgid "" -"The playbook now supports bridging with " -"[Facebook](https://www.facebook.com/) by installing the [mautrix-" -"facebook](https://github.com/tulir/mautrix-facebook) bridge. This " -"playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3154 -msgid "" -"Additional details are available in [Setting up Mautrix Facebook " -"bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." +msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." msgstr "" #: ../../../CHANGELOG.md:3156 @@ -9495,16 +5768,11 @@ msgid "mxisd Registration feature integration" msgstr "" #: ../../../CHANGELOG.md:3158 -msgid "" -"The playbook can now help you integrate with mxisd's " -"[Registration](https://github.com/kamax-" -"matrix/mxisd/blob/master/docs/features/registration.md) feature." +msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature." msgstr "" #: ../../../CHANGELOG.md:3160 -msgid "" -"Learn more in [mxisd-controlled Registration](docs/configuring-playbook-" -"mxisd.md#mxisd-controlled-registration)." +msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)." msgstr "" #: ../../../CHANGELOG.md:3163 @@ -9516,10 +5784,7 @@ msgid "Caddy webserver examples" msgstr "" #: ../../../CHANGELOG.md:3167 -msgid "" -"If you prefer using the [Caddy](https://caddyserver.com/) webserver " -"instead of our own integrated nginx, we now have examples for it in the " -"[`examples/caddy`](examples/caddy) directory" +msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory" msgstr "" #: ../../../CHANGELOG.md:3169 @@ -9531,10 +5796,7 @@ msgid "Goofys support for other S3-compatible object stores" msgstr "" #: ../../../CHANGELOG.md:3173 -msgid "" -"Until now, you could optionally host Synapse's media repository on Amazon" -" S3, but we now also support [using other S3-compatible object " -"stores](docs/configuring-playbook-s3.md)," +msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md)," msgstr "" #: ../../../CHANGELOG.md:3176 @@ -9546,18 +5808,11 @@ msgid "Ansible >= 2.5 is required" msgstr "" #: ../../../CHANGELOG.md:3180 -msgid "" -"Due to recent playbook improvements and the fact that the world keeps " -"turning, we're bumping the [version requirement for " -"Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." +msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." msgstr "" #: ../../../CHANGELOG.md:3182 -msgid "" -"We've also started building our own Docker image of Ansible " -"([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is " -"useful for people who can't upgrade their local Ansible installation (see" -" [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." +msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." msgstr "" #: ../../../CHANGELOG.md:3185 @@ -9569,46 +5824,27 @@ msgid "TLS support for Coturn" msgstr "" #: ../../../CHANGELOG.md:3189 -msgid "" -"We've added TLS support to the Coturn TURN server installed by the " -"playbook by default. The certificates from the Matrix domain will be used" -" for the Coturn server." +msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server." msgstr "" #: ../../../CHANGELOG.md:3191 -msgid "" -"This feature is enabled by default for new installations. To make use of " -"TLS support for your existing Matrix server's Coturn, make sure to " -"rebuild both Coturn and Synapse:" +msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:" msgstr "" #: ../../../CHANGELOG.md:3197 -msgid "" -"People who have an extra firewall (besides the iptables firewall, which " -"Docker manages automatically), will need to open these additional " -"firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over " -"UDP)." +msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)." msgstr "" #: ../../../CHANGELOG.md:3199 -msgid "" -"People who build their own custom playbook from our roles should be aware" -" that:" +msgid "People who build their own custom playbook from our roles should be aware that:" msgstr "" #: ../../../CHANGELOG.md:3201 -msgid "" -"the `matrix-coturn` role and actually starting Coturn (e.g. " -"`--tags=start`), requires that certificates are already put in place. For" -" this reason, it's usually a good idea to have the `matrix-coturn` role " -"execute after `matrix-nginx-proxy` (which retrieves the certificates)." +msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)." msgstr "" #: ../../../CHANGELOG.md:3203 -msgid "" -"there are a few variables that can help you enable TLS support for " -"Coturn. See the `matrix-coturn` section in [group_vars/matrix-" -"servers](./group_vars/matrix-servers)." +msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)." msgstr "" #: ../../../CHANGELOG.md:3206 @@ -9620,19 +5856,11 @@ msgid "matrix-nginx-proxy support for serving the base domain" msgstr "" #: ../../../CHANGELOG.md:3210 -msgid "" -"If you don't have a dedicated server for your base domain and want to set" -" up [Server Delegation via a well-known file](docs/howto-server-" -"delegation.md#server-delegation-via-a-well-known-file), the playbook has " -"got you covered now." +msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now." msgstr "" #: ../../../CHANGELOG.md:3212 -msgid "" -"It's now possible for the playbook to obtain an SSL certificate and serve" -" the necessary files for Matrix Server Delegation on your base domain. " -"Take a look at the new [Serving the base domain](docs/configuring-" -"playbook-base-domain-serving.md) documentation page." +msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3214 @@ -9640,17 +5868,11 @@ msgid "(BC break) matrix-nginx-proxy data variable renamed" msgstr "" #: ../../../CHANGELOG.md:3216 -msgid "" -"`matrix_nginx_proxy_data_path` was renamed to " -"`matrix_nginx_proxy_base_path`." +msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`." msgstr "" #: ../../../CHANGELOG.md:3218 -msgid "" -"There's a new `matrix_nginx_proxy_data_path` variable, which has a " -"different use-purpose now (it's a subdirectory of " -"`matrix_nginx_proxy_base_path` and is meant for storing various data " -"files)." +msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)." msgstr "" #: ../../../CHANGELOG.md:3221 @@ -9662,11 +5884,7 @@ msgid "Dimension integration manager support" msgstr "" #: ../../../CHANGELOG.md:3225 -msgid "" -"Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can " -"now (optionally) install the [Dimension](https://dimension.t2bot.io/) " -"integration manager. To learn more, see the [Setting up Dimension](docs" -"/configuring-playbook-dimension.md) documentation page." +msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3228 @@ -9678,11 +5896,7 @@ msgid "Ability to customize mxisd's email templates" msgstr "" #: ../../../CHANGELOG.md:3232 -msgid "" -"Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's " -"email templates can now be customized easily. To learn more, see the " -"[Customizing email templates](docs/configuring-playbook-mxisd.md" -"#customizing-email-templates) documentation page." +msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page." msgstr "" #: ../../../CHANGELOG.md:3235 @@ -9694,12 +5908,7 @@ msgid "Discord bridging support" msgstr "" #: ../../../CHANGELOG.md:3239 -msgid "" -"[@Lionstiger](https://github.com/Lionstiger) has done some great work " -"adding Discord bridging support via [matrix-appservice-" -"discord](https://github.com/matrix-org/matrix-appservice-discord). To " -"learn more, see the [Setting up Appservice Discord bridging](docs" -"/configuring-playbook-bridge-appservice-discord.md) documentation page." +msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3242 @@ -9732,15 +5941,11 @@ msgid "from `hostname_riot` to `matrix_server_fqn_riot`" msgstr "" #: ../../../CHANGELOG.md:3252 -msgid "" -"from `host_specific_matrix_ssl_lets_encrypt_support_email` to " -"`matrix_ssl_lets_encrypt_support_email`" +msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`" msgstr "" #: ../../../CHANGELOG.md:3254 -msgid "" -"Doing that, we've simplified things, made names less confusing " -"(hopefully) and moved all variable names under the `matrix_` prefix." +msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix." msgstr "" #: ../../../CHANGELOG.md:3257 @@ -9756,16 +5961,11 @@ msgid "You can now use the brand new and redesigned Riot." msgstr "" #: ../../../CHANGELOG.md:3263 -msgid "" -"The new version no longer has a homepage by default, so we've also " -"removed the custom homepage that we've been installing." +msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing." msgstr "" #: ../../../CHANGELOG.md:3265 -msgid "" -"However, we still provide you with hooks to install your own `home.html` " -"file by specifying the `matrix_riot_web_embedded_pages_home_path` " -"variable (used to be called `matrix_riot_web_homepage_template` before)." +msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)." msgstr "" #: ../../../CHANGELOG.md:3268 @@ -9777,18 +5977,11 @@ msgid "Synapse v0.99.1" msgstr "" #: ../../../CHANGELOG.md:3272 -msgid "" -"As we're moving toward Synapse v1.0, things are beginning to stabilize. " -"Upgrading from v0.99.0 to v0.99.1 should be painless." +msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless." msgstr "" #: ../../../CHANGELOG.md:3274 -msgid "" -"If you've been overriding the default configuration so that you can " -"terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), " -"you'll now have to replace this custom configuration with " -"`matrix_synapse_tls_federation_listener_enabled: true`. The " -"`matrix_synapse_no_tls` variable is no more." +msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more." msgstr "" #: ../../../CHANGELOG.md:3277 @@ -9800,67 +5993,27 @@ msgid "Synapse v0.99 support and preparation for Synapse v1.0" msgstr "" #: ../../../CHANGELOG.md:3281 -msgid "" -"Matrix is undergoing a lot of changes as it matures towards Synapse v1.0." -" The first step is the Synapse v0.99 transitional release, which this " -"playbook now supports." +msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports." msgstr "" #: ../../../CHANGELOG.md:3283 -msgid "" -"If you've been using this playbook successfully until now, you'd be aware" -" that we've been doing [Server Delegation](docs/howto-server-" -"delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring" -" DNS](docs/configuring-dns.md))." +msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))." msgstr "" #: ../../../CHANGELOG.md:3285 -msgid "" -"Due to changes related to certificate file requirements that will affect " -"us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV " -"record in the future** (when Synapse goes to v1.0 - around 5th of March " -"2019). We **still need to keep the SRV record for now**, for backward " -"compatibility with older Synapse versions (lower than v0.99)." +msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)." msgstr "" #: ../../../CHANGELOG.md:3287 -msgid "" -"**What you need to do now** is make use of this transitional Synapse " -"v0.99 release to **prepare your federation settings for the future**. You" -" have 2 choices to prepare yourself for compatibility with the future " -"Synapse v1.0:" +msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:" msgstr "" #: ../../../CHANGELOG.md:3289 -msgid "" -"(recommended) set up [Server Delegation via a well-known file](docs" -"/howto-server-delegation.md#server-delegation-via-a-well-known-file), " -"unless you are affected by the [Downsides of well-known-based Server " -"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" -"based-server-delegation). If you had previously set up the well-known " -"`client` file, depending on how you've done it, it may be that there is " -"nothing new required of you (besides [upgrading](docs/maintenance-" -"upgrading-services.md)). After upgrading, you can [run a self-check](docs" -"/maintenance-checking-services.md), which will tell you if you need to do" -" anything extra with regard to setting up [Server Delegation via a well-" -"known file](docs/howto-server-delegation.md#server-delegation-via-a-well-" -"known-file). After some time, when most people have upgraded to Synapse " -"v0.99 and older releases have disappeared, be prepared to drop your " -"`_matrix._tcp` SRV record." +msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record." msgstr "" #: ../../../CHANGELOG.md:3291 -msgid "" -"(more advanced) if the [Downsides of well-known-based Server " -"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" -"based-server-delegation) are not to your liking, **as an alternative**, " -"you can set up [Server Delegation via a DNS SRV record](docs/howto-" -"server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In" -" such a case, you get to keep using your existing `_matrix._tcp` DNS SRV " -"record forever and need to NOT set up a `/.well-known/matrix/server` " -"file. Don't forget that you need to do certificate changes though. Follow" -" the guide at [Server Delegation via a DNS SRV record](docs/howto-server-" -"delegation.md#server-delegation-via-a-dns-srv-record-advanced)." +msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)." msgstr "" #: ../../../CHANGELOG.md:3294 @@ -9872,10 +6025,7 @@ msgid "TLS v1.3 support" msgstr "" #: ../../../CHANGELOG.md:3298 -msgid "" -"Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has " -"[added support for TLS v1.3](https://github.com/nginxinc/docker-" -"nginx/issues/190), we have enabled that protocol by default." +msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default." msgstr "" #: ../../../CHANGELOG.md:3300 @@ -9883,33 +6033,15 @@ msgid "When using:" msgstr "" #: ../../../CHANGELOG.md:3302 -msgid "" -"the **integrated nginx server**: TLS v1.3 support might not kick in " -"immediately, because the nginx version hasn't been bumped and you may " -"have an older build of the nginx Docker image (currently " -"`nginx:1.15.8-alpine`). Typically, we do not re-pull images that you " -"already have. When the nginx version gets bumped in the future, everyone " -"will get the update. Until then, you could manually force-pull the " -"rebuilt Docker image by running this on the server: `docker pull " -"nginx:1.15.8-alpine`." +msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`." msgstr "" #: ../../../CHANGELOG.md:3304 -msgid "" -"**your own external nginx server**: if your external nginx server is too " -"old, the new configuration we generate for you in `/matrix/nginx-" -"proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and " -"your nginx version might not support that. You can adjust the SSL " -"protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` " -"variable. Learn more in the documentation page for [Using your own " -"webserver, instead of this playbook's nginx proxy](docs/configuring-" -"playbook-own-webserver.md)" +msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)" msgstr "" #: ../../../CHANGELOG.md:3306 -msgid "" -"**another web server**: you don't need to do anything to accommodate this" -" change" +msgid "**another web server**: you don't need to do anything to accommodate this change" msgstr "" #: ../../../CHANGELOG.md:3309 @@ -9921,12 +6053,7 @@ msgid "IRC bridging support" msgstr "" #: ../../../CHANGELOG.md:3313 -msgid "" -"[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some " -"great work bringing IRC bridging support via [matrix-appservice-" -"irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, " -"see the [Setting up Appservice IRC bridging](docs/configuring-playbook-" -"bridge-appservice-irc.md) documentation page." +msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3316 @@ -9934,44 +6061,23 @@ msgid "2019-01-29" msgstr "" #: ../../../CHANGELOG.md:3318 -msgid "" -"Running container processes as non-root, without capabilities and read-" -"only" +msgid "Running container processes as non-root, without capabilities and read-only" msgstr "" #: ../../../CHANGELOG.md:3320 -msgid "" -"To improve security, this playbook no longer starts container processes " -"as the `root` user. Most containers were dropping privileges anyway, but " -"we were trusting them with `root` privileges until they would do that. " -"Not anymore -- container processes now start as a non-root user (usually " -"`matrix`) from the get-go." +msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go." msgstr "" #: ../../../CHANGELOG.md:3322 -msgid "" -"For additional security, various capabilities are also dropped (see [why " -"it's important](https://github.com/projectatomic/atomic-site/issues/203))" -" for all containers." +msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers." msgstr "" #: ../../../CHANGELOG.md:3324 -msgid "" -"Additionally, most containers now use a read-only filesystem (see [why " -"it's important](https://www.projectatomic.io/blog/2015/12/making-docker-" -"images-write-only-in-production/)). Containers are given write access " -"only to the directories they need to write to." +msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to." msgstr "" #: ../../../CHANGELOG.md:3326 -msgid "" -"A minor breaking change is the " -"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` " -"variable having being renamed to " -"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` " -"(note the `_mb` suffix). The new variable expects a number value (e.g. " -"`25M` -> `25`). If you weren't customizing this variable, this wouldn't " -"affect you." +msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you." msgstr "" #: ../../../CHANGELOG.md:3328 @@ -9979,28 +6085,15 @@ msgid "matrix-mailer is now based on Exim, not Postfix" msgstr "" #: ../../../CHANGELOG.md:3330 -msgid "" -"While we would have preferred to stay with " -"[Postfix](http://www.postfix.org/), we found out that it cannot run as a " -"non-root user. We've had to replace it with [Exim](https://www.exim.org/)" -" (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" -"relay) container image)." +msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)." msgstr "" #: ../../../CHANGELOG.md:3332 -msgid "" -"The internal `matrix-mailer` service (running in a container) now listens" -" on port `8025` (used to be `587` before). The playbook will update your " -"Synapse and mxisd email settings to match (`matrix-mailer:587` -> " -"`matrix-mailer:8025`)." +msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)." msgstr "" #: ../../../CHANGELOG.md:3334 -msgid "" -"Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" -"relay) container image instead of " -"[panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us " -"a nice disk usage reduction (~200MB -> 8MB)." +msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)." msgstr "" #: ../../../CHANGELOG.md:3337 @@ -10012,34 +6105,19 @@ msgid "(BC Break) Making the playbook's roles more independent of one another" msgstr "" #: ../../../CHANGELOG.md:3341 -msgid "" -"The following change **affects people running a more non-standard setup**" -" - external Postgres or using our roles in their own other playbook. " -"**Most users don't need to do anything**, besides becoming aware of the " -"new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-" -"servers)." +msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)." msgstr "" #: ../../../CHANGELOG.md:3344 -msgid "" -"Because people like using the playbook's components independently " -"(outside of this playbook) and because it's much better for " -"maintainability, we've continued working on separating them. Still, we'd " -"like to offer a turnkey solution for running a fully-featured Matrix " -"server, so this playbook remains important for wiring up the various " -"components." +msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components." msgstr "" #: ../../../CHANGELOG.md:3346 -msgid "" -"With the new changes, **all roles are now only dependent on the minimal " -"`matrix-base` role**. They are no longer dependent among themselves." +msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves." msgstr "" #: ../../../CHANGELOG.md:3348 -msgid "" -"In addition, the following components can now be completely disabled (for" -" those who want/need to):" +msgid "In addition, the following components can now be completely disabled (for those who want/need to):" msgstr "" #: ../../../CHANGELOG.md:3349 @@ -10059,39 +6137,19 @@ msgid "The following changes had to be done:" msgstr "" #: ../../../CHANGELOG.md:3355 -msgid "" -"glue variables had to be introduced to the playbook, so it can wire " -"together the various components. Those glue vars are stored in the " -"[`group_vars/matrix-servers`](group_vars/matrix-servers) file. When " -"overriding variables for a given component (role), you need to be aware " -"of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's " -"corresponding section in the [`group_vars/matrix-servers`](group_vars" -"/matrix-servers) file." +msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file." msgstr "" #: ../../../CHANGELOG.md:3357 -msgid "" -"`matrix_postgres_use_external` has been superceeded by the more " -"consistently named `matrix_postgres_enabled` variable and a few other " -"`matrix_synapse_database_` variables. See the [Using an external " -"PostgreSQL server (optional)](docs/configuring-playbook-external-" -"postgres.md) documentation page for an up-to-date replacement." +msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement." msgstr "" #: ../../../CHANGELOG.md:3359 -msgid "" -"Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are " -"no longer installed if you're not enabling the `matrix-postgres` role " -"(`matrix_postgres_enabled: false`)" +msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)" msgstr "" #: ../../../CHANGELOG.md:3361 -msgid "" -"roles, being more independent now, are more minimal and do not do so much" -" magic for you. People that are building their own playbook using our " -"roles will definitely need to take a look at the [`group_vars/matrix-" -"servers`](group_vars/matrix-servers) file and adapt their playbooks with " -"the same (or similar) wiring logic." +msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic." msgstr "" #: ../../../CHANGELOG.md:3364 @@ -10103,30 +6161,15 @@ msgid "Splitting the playbook into multiple roles" msgstr "" #: ../../../CHANGELOG.md:3368 -msgid "" -"For better maintainability, the playbook logic (which all used to reside " -"in a single `matrix-server` role) has been split out into a number of " -"different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, " -"`matrix-mxisd`, etc. (see the `roles/` directory)." +msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)." msgstr "" #: ../../../CHANGELOG.md:3371 -msgid "" -"To keep the filesystem more consistent with this separation, the " -"**Postgres data had to be relocated**." +msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**." msgstr "" #: ../../../CHANGELOG.md:3373 -msgid "" -"The default value of `matrix_postgres_data_path` was changed from " -"`/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` " -"directory is what we consider a base path now (new variable " -"`matrix_postgres_base_path`). **Your Postgres data files will " -"automatically be relocated by the playbook** (`/matrix/postgres/*` -> " -"`/matrix/postgres/data/`) when you run with `--tags=setup-all` (or " -"`--tags=setup-postgres`). While this shouldn't cause data-loss, **it's " -"better if you do a Postgres backup just in case**. You'd need to restart " -"all services after this migration (`--tags=start`)." +msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3376 @@ -10138,10 +6181,7 @@ msgid "(BC Break) mxisd configuration changes" msgstr "" #: ../../../CHANGELOG.md:3380 -msgid "" -"To be more flexible and to support the upcoming " -"[mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released)," -" we've had to redo how mxisd gets configured." +msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured." msgstr "" #: ../../../CHANGELOG.md:3383 @@ -10225,11 +6265,7 @@ msgid "`matrix_mxisd_template_config`" msgstr "" #: ../../../CHANGELOG.md:3407 -msgid "" -"You are encouraged to use the `matrix_mxisd_configuration_extension_yaml`" -" variable to define your own mxisd configuration additions and overrides." -" Refer to the [default variables file](roles/custom/matrix-" -"mxisd/defaults/main.yml) for more information." +msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information." msgstr "" #: ../../../CHANGELOG.md:3409 @@ -10237,15 +6273,11 @@ msgid "This new way of configuring mxisd is beneficial because:" msgstr "" #: ../../../CHANGELOG.md:3411 -msgid "" -"it lets us support all mxisd configuration options, as the playbook " -"simply forwards them to mxisd without needing to care or understand them" +msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them" msgstr "" #: ../../../CHANGELOG.md:3412 -msgid "" -"it lets you upgrade to newer mxisd versions and make use of their " -"features, without us having to add support for them explicitly" +msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly" msgstr "" #: ../../../CHANGELOG.md:3415 @@ -10257,25 +6289,15 @@ msgid "(BC Break) Cronjob schedule no longer configurable" msgstr "" #: ../../../CHANGELOG.md:3419 -msgid "" -"Due to the way we manage cronjobs now, you can no longer configure the " -"schedule they're invoked at." +msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at." msgstr "" #: ../../../CHANGELOG.md:3421 -msgid "" -"If you were previously using " -"`matrix_ssl_lets_encrypt_renew_cron_time_definition` or " -"`matrix_nginx_proxy_reload_cron_time_definition` to set a custom " -"schedule, you should note that these variables don't affect anything " -"anymore." +msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore." msgstr "" #: ../../../CHANGELOG.md:3424 -msgid "" -"If you miss this functionality, please [open an " -"Issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/new) and let us know about your use case!" +msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!" msgstr "" #: ../../../CHANGELOG.md:3427 @@ -10287,9 +6309,7 @@ msgid "(BC Break) More SSL certificate retrieval methods" msgstr "" #: ../../../CHANGELOG.md:3431 -msgid "" -"The playbook now lets you decide between 3 different SSL certificate " -"retrieval methods:" +msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:" msgstr "" #: ../../../CHANGELOG.md:3432 @@ -10305,15 +6325,11 @@ msgid "managing SSL certificates manually" msgstr "" #: ../../../CHANGELOG.md:3436 -msgid "" -"Learn more in [Adjusting SSL certificate retrieval](docs/configuring-" -"playbook-ssl-certificates.md)." +msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)." msgstr "" #: ../../../CHANGELOG.md:3438 -msgid "" -"For people who use Let's Encrypt (mostly everyone, since it's the " -"default), you'll also have to rename a variable in your configuration:" +msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:" msgstr "" #: ../../../CHANGELOG.md:3440 @@ -10329,20 +6345,11 @@ msgid "(BC Break) mxisd upgrade with multiple base DN support" msgstr "" #: ../../../CHANGELOG.md:3445 -msgid "" -"mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-" -"matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base " -"DNs](https://github.com/kamax-" -"matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." +msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." msgstr "" #: ../../../CHANGELOG.md:3447 -msgid "" -"If you were configuring this playbook's " -"`matrix_mxisd_ldap_connection_baseDn` variable until now (a string " -"containing a single base DN), you'll need to change to configuring the " -"`matrix_mxisd_ldap_connection_baseDns` variable (an array containing " -"multiple base DNs)." +msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)." msgstr "" #: ../../../CHANGELOG.md:3449 @@ -10354,9 +6361,7 @@ msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org` msgstr "" #: ../../../CHANGELOG.md:3452 -msgid "" -"after: `matrix_mxisd_ldap_connection_baseDns: " -"['OU=Users,DC=example,DC=org']`" +msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`" msgstr "" #: ../../../CHANGELOG.md:3455 @@ -10368,10 +6373,7 @@ msgid "Synapse 0.34.0 and Python 3" msgstr "" #: ../../../CHANGELOG.md:3459 -msgid "" -"Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on " -"feedback from others, running Synapse on Python 3 is supposed to decrease" -" memory usage significantly (~2x)." +msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)." msgstr "" #: ../../../CHANGELOG.md:3462 @@ -10383,11 +6385,7 @@ msgid "Riot homepage customization" msgstr "" #: ../../../CHANGELOG.md:3466 -msgid "" -"You can now customize some parts of the Riot homepage (or even completely" -" replace it with your own custom page). See the " -"`matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-" -"web/defaults/main.yml`." +msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`." msgstr "" #: ../../../CHANGELOG.md:3469 @@ -10399,11 +6397,7 @@ msgid "mxisd extensibility" msgstr "" #: ../../../CHANGELOG.md:3473 -msgid "" -"The [LDAP identity store for mxisd](https://github.com/kamax-" -"matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured " -"easily using playbook variables (see the `matrix_mxisd_ldap_` variables " -"in `roles/custom/matrix-server/defaults/main.yml`)." +msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)." msgstr "" #: ../../../CHANGELOG.md:3476 @@ -10427,15 +6421,11 @@ msgid "LDAP auth support via matrix-synapse-ldap3" msgstr "" #: ../../../CHANGELOG.md:3485 -msgid "" -"The playbook can now install and configure [LDAP auth " -"support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." +msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." msgstr "" #: ../../../CHANGELOG.md:3487 -msgid "" -"Additional details are available in [Setting up the LDAP authentication " -"password provider module](docs/configuring-playbook-ldap-auth.md)." +msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3490 @@ -10447,16 +6437,11 @@ msgid "Support for controlling public registration and room auto-join" msgstr "" #: ../../../CHANGELOG.md:3494 -msgid "" -"The playbook now lets you enable public registration for users " -"(controlled via `matrix_synapse_enable_registration`). By default, public" -" registration is forbidden." +msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden." msgstr "" #: ../../../CHANGELOG.md:3496 -msgid "" -"You can also make people automatically get auto-joined to rooms " -"(controlled via `matrix_synapse_auto_join_rooms`)." +msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)." msgstr "" #: ../../../CHANGELOG.md:3498 @@ -10464,10 +6449,7 @@ msgid "Support for changing the welcome user ID (welcome bot)" msgstr "" #: ../../../CHANGELOG.md:3500 -msgid "" -"By default, `@riot-bot:matrix.org` is used to welcome newly registered " -"users. This can be changed to something else (or disabled) via the new " -"`matrix_riot_web_welcome_user_id` variable." +msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable." msgstr "" #: ../../../CHANGELOG.md:3503 @@ -10479,16 +6461,11 @@ msgid "Ability to set Synapse log levels" msgstr "" #: ../../../CHANGELOG.md:3507 -msgid "" -"The playbook now allows you to set the log levels used by Synapse. The " -"default logging levels remain the same." +msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same." msgstr "" #: ../../../CHANGELOG.md:3509 -msgid "" -"You can now override following variables with any of the supported log " -"levels listed here: https://docs.python.org/3/library/logging.html" -"#logging-levels" +msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels" msgstr "" #: ../../../CHANGELOG.md:3518 @@ -10500,17 +6477,11 @@ msgid "Customize parts of Riot's config" msgstr "" #: ../../../CHANGELOG.md:3522 -msgid "" -"You can now customize some parts of Riot's `config.json`. These playbook " -"variables, with these default values, have been added:" +msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:" msgstr "" #: ../../../CHANGELOG.md:3533 -msgid "" -"This now allows you use a custom integration manager like " -"[Dimension](https://dimension.t2bot.io). For example, if you wish to use " -"the Dimension instance hosted at dimension.t2bot.io, you can set the " -"following in your vars.yml file:" +msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:" msgstr "" #: ../../../CHANGELOG.md:3542 @@ -10518,23 +6489,15 @@ msgid "SSL protocols used to serve Riot and Synapse" msgstr "" #: ../../../CHANGELOG.md:3544 -msgid "" -"There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, " -"which controls the SSL protocols used to serve Riot and Synapse. Its " -"default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 " -"TLSv1.1 TLSv1.2` to serve Riot and Synapse." +msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse." msgstr "" #: ../../../CHANGELOG.md:3546 -msgid "" -"You may wish to reenable TLSv1 if you need to access Riot in older " -"browsers." +msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers." msgstr "" #: ../../../CHANGELOG.md:3548 -msgid "" -"Note: Currently the dockerized nginx doesn't support TLSv1.3. See " -"https://github.com/nginxinc/docker-nginx/issues/190 for more details." +msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details." msgstr "" #: ../../../CHANGELOG.md:3551 @@ -10546,17 +6509,11 @@ msgid "Postgres 11 support" msgstr "" #: ../../../CHANGELOG.md:3555 -msgid "" -"The playbook now installs [Postgres " -"11](https://www.postgresql.org/about/news/1894/) by default." +msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default." msgstr "" #: ../../../CHANGELOG.md:3557 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x or 10.x). You can easily upgrade by following the " -"[upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" -"postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646 @@ -10565,10 +6522,7 @@ msgid "(BC Break) Renaming playbook variables" msgstr "" #: ../../../CHANGELOG.md:3561 -msgid "" -"Due to the large amount of features added to this playbook lately, to " -"keep things manageable we've had to reorganize its configuration " -"variables a bit." +msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit." msgstr "" #: ../../../CHANGELOG.md:3565 @@ -10576,15 +6530,11 @@ msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3566 -msgid "" -"from `matrix_docker_image_mautrix_telegram` to " -"`matrix_mautrix_telegram_docker_image`" +msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3567 -msgid "" -"from `matrix_docker_image_mautrix_whatsapp` to " -"`matrix_mautrix_whatsapp_docker_image`" +msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3568 @@ -10612,21 +6562,15 @@ msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3574 -msgid "" -"from `matrix_docker_image_postgres_v9` to " -"`matrix_postgres_docker_image_v9`" +msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`" msgstr "" #: ../../../CHANGELOG.md:3575 -msgid "" -"from `matrix_docker_image_postgres_v10` to " -"`matrix_postgres_docker_image_v10`" +msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`" msgstr "" #: ../../../CHANGELOG.md:3576 -msgid "" -"from `matrix_docker_image_postgres_latest` to " -"`matrix_postgres_docker_image_latest`" +msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`" msgstr "" #: ../../../CHANGELOG.md:3579 @@ -10638,18 +6582,11 @@ msgid "Mautrix Whatsapp bridging support" msgstr "" #: ../../../CHANGELOG.md:3583 -msgid "" -"The playbook now supports bridging with " -"[Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-" -"whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This " -"playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3585 -msgid "" -"Additional details are available in [Setting up Mautrix Whatsapp " -"bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." +msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." msgstr "" #: ../../../CHANGELOG.md:3588 @@ -10661,10 +6598,7 @@ msgid "Support for controlling Matrix federation" msgstr "" #: ../../../CHANGELOG.md:3592 -msgid "" -"The playbook can now help you with [Controlling Matrix federation](docs" -"/configuring-playbook-federation), should you wish to run a more private " -"(isolated) server." +msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server." msgstr "" #: ../../../CHANGELOG.md:3595 @@ -10676,10 +6610,7 @@ msgid "Disabling riot-web guests" msgstr "" #: ../../../CHANGELOG.md:3599 -msgid "" -"From now on, Riot's configuration setting `disable_guests` would be set " -"to `true`. The homeserver was rejecting guests anyway, so this is just a " -"cosmetic change affecting Riot's UI." +msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI." msgstr "" #: ../../../CHANGELOG.md:3602 @@ -10691,9 +6622,7 @@ msgid "Self-check maintenance command" msgstr "" #: ../../../CHANGELOG.md:3606 -msgid "" -"The playbook can now [check if services are configured correctly](docs" -"/maintenance-checking-services.md)." +msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)." msgstr "" #: ../../../CHANGELOG.md:3609 @@ -10705,16 +6634,11 @@ msgid "Presence tracking made configurable" msgstr "" #: ../../../CHANGELOG.md:3613 -msgid "" -"The playbook can now enable/disable user presence-status tracking in " -"Synapse, through the playbook's `matrix_synapse_use_presence` variable " -"(having a default value of `true` - enabled)." +msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)." msgstr "" #: ../../../CHANGELOG.md:3615 -msgid "" -"If users participate in large rooms with many other servers, disabling " -"presence will decrease server load significantly." +msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly." msgstr "" #: ../../../CHANGELOG.md:3618 @@ -10726,18 +6650,11 @@ msgid "Synapse Cache Factor made configurable" msgstr "" #: ../../../CHANGELOG.md:3622 -msgid "" -"The playbook now makes the Synapse cache factor configurable, through the" -" playbook's `matrix_synapse_cache_factor` variable (having a default " -"value of `0.5`)." +msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)." msgstr "" #: ../../../CHANGELOG.md:3624 -msgid "" -"Changing that value allows you to potentially decrease RAM usage or to " -"increase performance by caching more stuff. Some information on it is " -"available here: https://github.com/element-hq/synapse#help-synapse-eats-" -"all-my-ram" +msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram" msgstr "" #: ../../../CHANGELOG.md:3627 @@ -10753,18 +6670,11 @@ msgid "`--log-driver=none` is used for all Docker containers now." msgstr "" #: ../../../CHANGELOG.md:3633 -msgid "" -"All these containers are started through systemd anyway and get logged in" -" journald, so there's no need for Docker to be logging the same thing " -"using the default `json-file` driver. Doing that was growing " -"`/var/lib/docker/containers/..` infinitely until service/container " -"restart." +msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart." msgstr "" #: ../../../CHANGELOG.md:3635 -msgid "" -"As a result of this, things like `docker logs matrix-synapse` won't work " -"anymore. `journalctl -u matrix-synapse` is how one can see the logs." +msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs." msgstr "" #: ../../../CHANGELOG.md:3638 @@ -10776,16 +6686,11 @@ msgid "Service discovery support" msgstr "" #: ../../../CHANGELOG.md:3642 -msgid "" -"The playbook now helps you set up [service " -"discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-" -"discovery) using a `/.well-known/matrix/client` file." +msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file." msgstr "" #: ../../../CHANGELOG.md:3644 -msgid "" -"Additional details are available in [Configuring service discovery via " -".well-known](docs/configuring-well-known.md)." +msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)." msgstr "" #: ../../../CHANGELOG.md:3650 @@ -10793,9 +6698,7 @@ msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" msgstr "" #: ../../../CHANGELOG.md:3651 -msgid "" -"from `matrix_riot_web_default_identity_server_url` to " -"`matrix_identity_server_url`" +msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`" msgstr "" #: ../../../CHANGELOG.md:3654 @@ -10807,17 +6710,11 @@ msgid "Mautrix Telegram bridging support" msgstr "" #: ../../../CHANGELOG.md:3658 -msgid "" -"The playbook now supports bridging with [Telegram](https://telegram.org/)" -" by installing the [mautrix-telegram](https://github.com/tulir/mautrix-" -"telegram) bridge. This playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3660 -msgid "" -"Additional details are available in [Setting up Mautrix Telegram " -"bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." +msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." msgstr "" #: ../../../CHANGELOG.md:3662 @@ -10825,16 +6722,11 @@ msgid "Events cache size increase and configurability for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3664 -msgid "" -"The playbook now lets you configure Matrix Synapse's `event_cache_size` " -"configuration via the `matrix_synapse_event_cache_size` playbook " -"variable." +msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable." msgstr "" #: ../../../CHANGELOG.md:3666 -msgid "" -"Previously, this value was hardcoded to `\"10K\"`. From now on, a more " -"reasonable default of `\"100K\"` is used." +msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used." msgstr "" #: ../../../CHANGELOG.md:3668 @@ -10842,13 +6734,7 @@ msgid "Password-peppering support for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3670 -msgid "" -"The playbook now supports enabling password-peppering for increased " -"security in Matrix Synapse via the " -"`matrix_synapse_password_config_pepper` playbook variable. Using a " -"password pepper is disabled by default (just like it used to be before " -"this playbook variable got introduced) and is not to be enabled/disabled " -"after initial setup, as that would invalidate all existing passwords." +msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords." msgstr "" #: ../../../CHANGELOG.md:3672 @@ -10856,17 +6742,11 @@ msgid "Statistics-reporting support for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3674 -msgid "" -"There's now a new `matrix_synapse_report_stats` playbook variable, which " -"controls the `report_stats` configuration option for Matrix Synapse. It " -"defaults to `false`, so no change is required to retain your privacy." +msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy." msgstr "" #: ../../../CHANGELOG.md:3676 -msgid "" -"If you'd like to start reporting statistics about your homeserver (things" -" like number of users, number of messages sent, uptime, load, etc.) to " -"matrix.org, you can turn on stats reporting." +msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting." msgstr "" #: ../../../CHANGELOG.md:3679 @@ -10878,26 +6758,15 @@ msgid "Changing the way SSL certificates are retrieved" msgstr "" #: ../../../CHANGELOG.md:3683 -msgid "" -"We've been using [acmetool](https://github.com/hlandau/acme) (with the " -"[willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) " -"Docker image) until now." +msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now." msgstr "" #: ../../../CHANGELOG.md:3685 -msgid "" -"Due to the Docker image being deprecated, and things looking bleak for " -"acmetool's support of the newer ACME v2 API endpoint, we've switched to " -"using [certbot](https://certbot.eff.org/) (with the " -"[certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker " -"image)." +msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)." msgstr "" #: ../../../CHANGELOG.md:3687 -msgid "" -"Simply re-running the playbook will retrieve new certificates (via " -"certbot) for you. To ensure you don't leave any old files behind, though," -" you'd better do this:" +msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:" msgstr "" #: ../../../CHANGELOG.md:3689 @@ -10905,9 +6774,7 @@ msgid "`systemctl stop 'matrix*'`" msgstr "" #: ../../../CHANGELOG.md:3690 -msgid "" -"stop your custom webserver, if you're running one (only affects you if " -"you've installed with `matrix_nginx_proxy_enabled: false`)" +msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)" msgstr "" #: ../../../CHANGELOG.md:3691 @@ -10931,15 +6798,11 @@ msgid "Matrix Corporal support" msgstr "" #: ../../../CHANGELOG.md:3700 -msgid "" -"The playbook can now install and configure [matrix-" -"corporal](https://github.com/devture/matrix-corporal) for you." +msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" #: ../../../CHANGELOG.md:3702 -msgid "" -"Additional details are available in [Setting up Matrix Corporal](docs" -"/configuring-playbook-matrix-corporal.md)." +msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../CHANGELOG.md:3705 @@ -10951,9 +6814,7 @@ msgid "Matrix Synapse rate limit control variables" msgstr "" #: ../../../CHANGELOG.md:3709 -msgid "" -"The following new variables can now be configured to control Matrix " -"Synapse's rate-limiting (default values are shown below)." +msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)." msgstr "" #: ../../../CHANGELOG.md:3716 @@ -10961,17 +6822,11 @@ msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" msgstr "" #: ../../../CHANGELOG.md:3718 -msgid "" -"The playbook can now install and configure [matrix-synapse-shared-secret-" -"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " -"you." +msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" #: ../../../CHANGELOG.md:3720 -msgid "" -"Additional details are available in [Setting up the Shared Secret Auth " -"password provider module](docs/configuring-playbook-shared-secret-" -"auth.md)." +msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3723 @@ -10983,15 +6838,11 @@ msgid "REST auth support via matrix-synapse-rest-auth" msgstr "" #: ../../../CHANGELOG.md:3727 -msgid "" -"The playbook can now install and configure [matrix-synapse-rest-" -"auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." +msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." msgstr "" #: ../../../CHANGELOG.md:3729 -msgid "" -"Additional details are available in [Setting up the REST authentication " -"password provider module](docs/configuring-playbook-rest-auth.md)." +msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3731 @@ -10999,15 +6850,11 @@ msgid "Compression improvements" msgstr "" #: ../../../CHANGELOG.md:3733 -msgid "" -"Shifted Matrix Synapse compression from happening in the Matrix Synapse, " -"to happening in the nginx proxy that's in front of it." +msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it." msgstr "" #: ../../../CHANGELOG.md:3736 -msgid "" -"Additionally, `riot-web` also gets compressed now (in the nginx proxy), " -"which drops the initial page load's size from 5.31MB to 1.86MB." +msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB." msgstr "" #: ../../../CHANGELOG.md:3739 @@ -11023,15 +6870,11 @@ msgid "on the federation port (8448): the `client` service" msgstr "" #: ../../../CHANGELOG.md:3743 -msgid "" -"on the http port (8008, exposed over 443): the old Angular `webclient` " -"and the `federation` service" +msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service" msgstr "" #: ../../../CHANGELOG.md:3745 -msgid "" -"Federation runs only on the federation port (8448) now. The Client APIs " -"run only on the http port (8008) now." +msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now." msgstr "" #: ../../../CHANGELOG.md:3748 @@ -11043,10 +6886,7 @@ msgid "mxisd Identity Server support" msgstr "" #: ../../../CHANGELOG.md:3752 -msgid "" -"The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) " -"Identity Server for you by default. Additional details are available in " -"[Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." +msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." msgstr "" #: ../../../CHANGELOG.md:3755 @@ -11058,16 +6898,11 @@ msgid "Email-sending support" msgstr "" #: ../../../CHANGELOG.md:3759 -msgid "" -"The playbook now configures an email-sending service (postfix) by " -"default. Additional details are available in [Adjusting email-sending " -"settings](docs/configuring-playbook-email.md)." +msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)." msgstr "" #: ../../../CHANGELOG.md:3761 -msgid "" -"With this, Matrix Synapse is able to send email notifications for missed " -"messages, etc." +msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc." msgstr "" #: ../../../CHANGELOG.md:3764 @@ -11079,9 +6914,7 @@ msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" msgstr "" #: ../../../CHANGELOG.md:3771 -msgid "" -"from `matrix_max_log_file_size_mb` to " -"`matrix_synapse_max_log_file_size_mb`" +msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`" msgstr "" #: ../../../CHANGELOG.md:3772 @@ -11109,9 +6942,7 @@ msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" msgstr "" #: ../../../CHANGELOG.md:3779 -msgid "" -"If you're overriding any of them in your `vars.yml` file, you'd need to " -"change to the new names." +msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names." msgstr "" #: ../../../CHANGELOG.md:3781 @@ -11119,9 +6950,7 @@ msgid "Renaming Ansible playbook tag" msgstr "" #: ../../../CHANGELOG.md:3783 -msgid "" -"The command for executing the whole playbook has changed. The `setup-" -"main` tag got renamed to `setup-all`." +msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`." msgstr "" #: ../../../CHANGELOG.md:3785 @@ -11129,9 +6958,5 @@ msgid "Docker container linking" msgstr "" #: ../../../CHANGELOG.md:3787 -msgid "" -"Changed the way the Docker containers are linked together. The ones that " -"need to communicate with others operate in a `matrix` network now and not" -" in the default bridge network." +msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/README.po b/i18n/locales/bg/LC_MESSAGES/README.po index 10bc599a8..06e8535f1 100644 --- a/i18n/locales/bg/LC_MESSAGES/README.po +++ b/i18n/locales/bg/LC_MESSAGES/README.po @@ -8,34 +8,23 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: matrix-docker-ansible-deploy\n" +"Project-Id-Version: matrix-docker-ansible-deploy\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-12-20 09:53+0200\n" -"PO-Revision-Date: 2024-12-20 09:52+0200\n" +"PO-Revision-Date: 2024-12-20 14:33+0200\n" "Last-Translator: \n" -"Language: bg\n" "Language-Team: bg \n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"Language: bg\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "Generated-By: Babel 2.16.0\n" +"X-Generator: Poedit 3.4.2\n" #: ../../../README.md:1 -msgid "" -"[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-" -"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" -"deploy%3Adevture.com&logo=matrix&style=for-the-" -"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" -"docker-ansible-deploy:devture.com) " -"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" -msgstr "" -"[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-" -"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" -"deploy%3Adevture.com&logo=matrix&style=for-the-" -"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" -"docker-ansible-deploy:devture.com) " -"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgstr "[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" #: ../../../README.md:1 msgid "Support room on Matrix" @@ -46,9 +35,7 @@ msgid "donate" msgstr "" #: ../../../README.md:3 -msgid "" -"Matrix (An open network for secure, decentralized communication) server " -"setup using Ansible and Docker" +msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker" msgstr "" #: ../../../README.md:5 @@ -56,38 +43,19 @@ msgid "🎯 Purpose" msgstr "🎯 Цел" #: ../../../README.md:7 -msgid "" -"This [Ansible](https://www.ansible.com/) playbook is meant to help you " -"run your own [Matrix](http://matrix.org/) homeserver, along with the " -"[various services](#supported-services) related to that." -msgstr "" -"Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви " -"помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен " -"сървър, заедно с [различните услуги](#supported-services), свързани с " -"това." +msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that." +msgstr "Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#supported-services), свързани с това." #: ../../../README.md:9 -msgid "" -"That is, it lets you join the Matrix network using your own user ID like " -"`@alice:example.com`, all hosted on your own server (see " -"[prerequisites](docs/prerequisites.md))." +msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))." msgstr "" #: ../../../README.md:11 -msgid "" -"We run all [supported services](#-supported-services) in " -"[Docker](https://www.docker.com/) containers (see [the container images " -"we use](docs/container-images.md)), which lets us have a predictable and " -"up-to-date setup, across multiple supported distros (see " -"[prerequisites](docs/prerequisites.md)) and [architectures](docs" -"/alternative-architectures.md) (x86/amd64 being recommended)." +msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)." msgstr "" #: ../../../README.md:13 -msgid "" -"Installation (upgrades) and some maintenance tasks are automated using " -"[Ansible](https://www.ansible.com/) (see [our Ansible " -"guide](docs/ansible.md))." +msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))." msgstr "" #: ../../../README.md:15 @@ -95,27 +63,11 @@ msgid "☁ Self-hosting or Managed / SaaS" msgstr "" #: ../../../README.md:17 -msgid "" -"This Ansible playbook tries to make self-hosting and maintaining a Matrix" -" server fairly easy (see [Getting started](#-getting-started)). Still, " -"running any service smoothly requires knowledge, time and effort." +msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort." msgstr "" #: ../../../README.md:19 -msgid "" -"If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" -"source_software) spirit of this Ansible playbook, but prefer to put the " -"responsibility on someone else, you can also [get a managed Matrix server" -" from " -"etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" (both hosting and on-premises) - a service built on top of this Ansible " -"playbook but with [additional " -"components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" and " -"[services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" which all help you run a Matrix server with ease. Be advised that " -"etke.cc operates on a subscription-based approach and there is no \"just " -"set up my server once and be done with it\" option." +msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option." msgstr "" #: ../../../README.md:21 @@ -123,51 +75,31 @@ msgid "🚀 Getting started" msgstr "🚀 Стартиране" #: ../../../README.md:23 -msgid "" -"We have detailed documentation in the [docs/](./docs) directory - see the" -" Table of Contents in the [documentation README](./docs/README.md)." +msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)." msgstr "" #: ../../../README.md:25 -msgid "" -"While the [list of supported services](#-supported-services) and " -"documentation is very extensive, you don't need to read through " -"everything. We recommend:" +msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:" msgstr "" #: ../../../README.md:27 -msgid "" -"Starting with the basics. You can always add/remove or tweak services " -"later on." +msgid "Starting with the basics. You can always add/remove or tweak services later on." msgstr "" #: ../../../README.md:29 -msgid "" -"Following our installation guide. There are two guides available for " -"beginners and advanced users:" +msgid "Following our installation guide. There are two guides available for beginners and advanced users:" msgstr "" #: ../../../README.md:31 -msgid "" -"⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is " -"recommended for those who do not have an existing Matrix server and want " -"to start quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../README.md:33 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide by starting with the " -"**[Prerequisites](./docs/prerequisites.md)** documentation page." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](./docs/prerequisites.md)** documentation page." msgstr "" #: ../../../README.md:35 -msgid "" -"If you experience an issue on configuring the playbook, setting up your " -"server, maintaining services on it, etc., please take a look at our " -"[FAQ](./docs/faq.md). If you cannot find an answer to your question, feel" -" free to ask for [help and support](#-support)." +msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)." msgstr "" #: ../../../README.md:37 @@ -175,11 +107,7 @@ msgid "✔ Supported services" msgstr "" #: ../../../README.md:39 -msgid "" -"Using this playbook, you can get the following list of services " -"configured on your server. Basically, this playbook aims to get you up-" -"and-running with all the necessities around Matrix, without you having to" -" do anything else." +msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else." msgstr "" #: ../../../README.md:41 @@ -187,19 +115,11 @@ msgid "**Notes**:" msgstr "" #: ../../../README.md:43 -msgid "" -"The list below is exhaustive. It includes optional or even some advanced " -"components that you will most likely not need. Sticking with the defaults" -" (which install a subset of the above components) is the best choice, " -"especially for a new installation. You can always re-run the playbook " -"later to add or remove components." +msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components." msgstr "" #: ../../../README.md:45 -msgid "" -"Deprecated or unmaintained services are not listed. You can find " -"documentations for them [here](docs/configuring-playbook.md#deprecated--" -"unmaintained--removed-services)." +msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)." msgstr "" #: ../../../README.md:47 @@ -207,9 +127,7 @@ msgid "Homeserver" msgstr "" #: ../../../README.md:49 -msgid "" -"The homeserver is the backbone of your Matrix system. Choose one from the" -" following list." +msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list." msgstr "" #: ../../../README.md @@ -226,7 +144,7 @@ msgstr "" #: ../../../README.md msgid "Documentation" -msgstr "" +msgstr "Документация" #: ../../../README.md msgid "[Synapse](https://github.com/element-hq/synapse)" @@ -237,9 +155,7 @@ msgid "✅" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" msgstr "" #: ../../../README.md @@ -255,11 +171,7 @@ msgid "❌" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" -"source server implementation of the Matrix Specification with a focus on " -"easy setup and low system requirements" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" msgstr "" #: ../../../README.md @@ -271,10 +183,7 @@ msgid "[Dendrite](https://github.com/matrix-org/dendrite)" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " -"Matrix homeserver written in Go, an alternative to Synapse." +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." msgstr "" #: ../../../README.md @@ -283,7 +192,7 @@ msgstr "" #: ../../../README.md:57 msgid "Clients" -msgstr "" +msgstr "Клиенти" #: ../../../README.md:59 msgid "Web clients for Matrix that you can host on your own domains." @@ -294,9 +203,7 @@ msgid "[Element Web](https://github.com/element-hq/element-web)" msgstr "" #: ../../../README.md -msgid "" -"Default Matrix web client, configured to connect to your own Synapse " -"server" +msgid "Default Matrix web client, configured to connect to your own Synapse server" msgstr "" #: ../../../README.md @@ -344,9 +251,7 @@ msgid "Server Components" msgstr "" #: ../../../README.md:70 -msgid "" -"Services that run on the server to make the various parts of your " -"installation work." +msgid "Services that run on the server to make the various parts of your installation work." msgstr "" #: ../../../README.md @@ -354,9 +259,7 @@ msgid "[PostgreSQL](https://www.postgresql.org/)" msgstr "" #: ../../../README.md -msgid "" -"Database for Synapse. [Using an external PostgreSQL server](docs" -"/configuring-playbook-external-postgres.md) is also possible." +msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible." msgstr "" #: ../../../README.md @@ -380,10 +283,7 @@ msgid "[Traefik](https://doc.traefik.io/traefik/)" msgstr "" #: ../../../README.md -msgid "" -"Web server, listening on ports 80, 443 and 8448 - standing in front of " -"all the other services. Using your own webserver [is possible](docs" -"/configuring-playbook-own-webserver.md)" +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)" msgstr "" #: ../../../README.md @@ -407,9 +307,7 @@ msgid "[Exim](https://www.exim.org/)" msgstr "" #: ../../../README.md -msgid "" -"Mail server, through which all Matrix services send outgoing email (can " -"be configured to relay through another SMTP server)" +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" msgstr "" #: ../../../README.md @@ -449,9 +347,7 @@ msgid "Extend and modify how users are authenticated on your homeserver." msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-" -"password-provider) (advanced)" +msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)" msgstr "" #: ../../../README.md @@ -463,9 +359,7 @@ msgid "[Link](docs/configuring-playbook-rest-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-" -"synapse-shared-secret-auth) (advanced)" +msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)" msgstr "" #: ../../../README.md @@ -477,9 +371,7 @@ msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-" -"ldap3) (advanced)" +msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)" msgstr "" #: ../../../README.md @@ -491,16 +383,11 @@ msgid "[Link](docs/configuring-playbook-ldap-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" (advanced)" +msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)" msgstr "" #: ../../../README.md -msgid "" -"A proxy that handles Matrix registration requests and forwards them to " -"LDAP." +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../README.md @@ -520,9 +407,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../README.md -msgid "" -"[Matrix User Verification Service](https://github.com/matrix-org/matrix-" -"user-verification-service) (UVS)" +msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)" msgstr "" #: ../../../README.md @@ -534,9 +419,7 @@ msgid "[Link](docs/configuring-playbook-user-verification-service.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" -"antispam) (advanced)" +msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)" msgstr "" #: ../../../README.md @@ -560,9 +443,7 @@ msgid "[Goofys](https://github.com/kahing/goofys)" msgstr "" #: ../../../README.md -msgid "" -"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " -"store) storage for Synapse's content repository (`media_store`) files" +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" msgstr "" #: ../../../README.md @@ -570,9 +451,7 @@ msgid "[Link](docs/configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" -"-storage-provider)" +msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)" msgstr "" #: ../../../README.md @@ -584,10 +463,7 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)" msgstr "" #: ../../../README.md -msgid "" -"matrix-media-repo is a highly customizable multi-domain media repository " -"for Matrix. Intended for medium to large deployments, this media repo de-" -"duplicates media while being fully compliant with the specification." +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." msgstr "" #: ../../../README.md @@ -599,9 +475,7 @@ msgid "Bridges" msgstr "" #: ../../../README.md:108 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../README.md @@ -705,16 +579,11 @@ msgid "[mautrix-meta](https://github.com/mautrix/instagram)" msgstr "" #: ../../../README.md -msgid "" -"Bridge to [Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/)" +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" msgstr "" #: ../../../README.md -msgid "" -"Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-" -"messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-" -"meta-instagram.md)" +msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../README.md @@ -742,9 +611,7 @@ msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-" -"irc)" +msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)" msgstr "" #: ../../../README.md @@ -756,15 +623,11 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk)" +msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)" msgstr "" #: ../../../README.md -msgid "" -"Bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" msgstr "" #: ../../../README.md @@ -772,9 +635,7 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-discord](https://github.com/matrix-org/matrix-" -"appservice-discord)" +msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)" msgstr "" #: ../../../README.md @@ -786,9 +647,7 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-slack](https://github.com/matrix-org/matrix-" -"appservice-slack)" +msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)" msgstr "" #: ../../../README.md @@ -800,9 +659,7 @@ msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)" msgstr "" #: ../../../README.md -msgid "" -"Bridge for generic webhooks and multiple project management services, " -"such as GitHub, GitLab, Figma, and Jira in particular" +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" msgstr "" #: ../../../README.md @@ -838,9 +695,7 @@ msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)" msgstr "" #: ../../../README.md -msgid "" -"Bouncer-style bridge to " -"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../README.md @@ -896,9 +751,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../README.md -msgid "" -"[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-" -"discord)" +msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)" msgstr "" #: ../../../README.md @@ -906,9 +759,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../README.md -msgid "" -"[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-" -"groupme)" +msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)" msgstr "" #: ../../../README.md @@ -968,11 +819,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)" msgstr "" #: ../../../README.md -msgid "" -"A bot that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you" +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" msgstr "" #: ../../../README.md @@ -980,9 +827,7 @@ msgid "[Link](docs/configuring-playbook-bot-baibot.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-" -"bot)" +msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)" msgstr "" #: ../../../README.md @@ -994,9 +839,7 @@ msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-registration-bot](https://github.com/moan0s/matrix-registration-" -"bot)" +msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)" msgstr "" #: ../../../README.md @@ -1052,9 +895,7 @@ msgid "A moderation tool for Matrix (Fork of Mjolnir)" msgstr "" #: ../../../README.md -msgid "" -"[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice " -"mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" +msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" msgstr "" #: ../../../README.md @@ -1074,22 +915,15 @@ msgid "Administration" msgstr "" #: ../../../README.md:158 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../README.md -msgid "" -"[matrix-alertmanager-receiver](https://github.com/metio/matrix-" -"alertmanager-receiver)" +msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)" msgstr "" #: ../../../README.md -msgid "" -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"client" +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" msgstr "" #: ../../../README.md @@ -1097,9 +931,7 @@ msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../README.md -msgid "" -"[Matrix Authentication Service](https://github.com/element-hq/matrix-" -"authentication-service/)" +msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)" msgstr "" #: ../../../README.md @@ -1127,19 +959,11 @@ msgid "Metrics and Graphs" msgstr "" #: ../../../README.md -msgid "" -"Consists of the [Prometheus](https://prometheus.io) time-series database " -"server, the Prometheus [node-exporter](https://prometheus.io/docs/guides" -"/node-exporter/) host metrics exporter, and the " -"[Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-" -"exporter](https://github.com/martin-helmich/prometheus-nginxlog-" -"exporter/) being available too" +msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too" msgstr "" #: ../../../README.md -msgid "" -"[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-" -"nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" +msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" msgstr "" #: ../../../README.md @@ -1167,15 +991,11 @@ msgid "[Link](docs/configuring-playbook-rageshake.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" -"exporter)" +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)" msgstr "" #: ../../../README.md -msgid "" -"Export the usage statistics of a Synapse homeserver to be scraped by " -"Prometheus." +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." msgstr "" #: ../../../README.md @@ -1195,11 +1015,7 @@ msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)" msgstr "" #: ../../../README.md -msgid "" -"(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` " -"and Conduit > `0.6.0`) Sliding Sync support for clients which require it " -"(e.g. old Element X versions before Simplified Sliding Sync was " -"developed)" +msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)" msgstr "" #: ../../../README.md @@ -1207,9 +1023,7 @@ msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-" -"accept-invite)" +msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)" msgstr "" #: ../../../README.md @@ -1221,15 +1035,11 @@ msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" -"compress-state/#automated-tool-synapse_auto_compressor)" +msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)" msgstr "" #: ../../../README.md -msgid "" -"A cli tool that automatically compresses `state_groups` database table in" -" background." +msgid "A cli tool that automatically compresses `state_groups` database table in background." msgstr "" #: ../../../README.md @@ -1325,15 +1135,11 @@ msgid "🆕 Changes" msgstr "" #: ../../../README.md:189 -msgid "" -"This playbook evolves over time, sometimes with backward-incompatible " -"changes." +msgid "This playbook evolves over time, sometimes with backward-incompatible changes." msgstr "" #: ../../../README.md:191 -msgid "" -"When updating the playbook, refer to [the changelog](CHANGELOG.md) to " -"catch up with what's new." +msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new." msgstr "" #: ../../../README.md:193 @@ -1341,23 +1147,15 @@ msgid "🆘 Support" msgstr "" #: ../../../README.md:195 -msgid "" -"Matrix room: [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com)" +msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)" msgstr "" #: ../../../README.md:197 -msgid "" -"IRC channel: `#matrix-docker-ansible-deploy` on the [Libera " -"Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" +msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" msgstr "" #: ../../../README.md:199 -msgid "" -"GitHub issues: [spantaleev/matrix-docker-ansible-" -"deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues)" +msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)" msgstr "" #: ../../../README.md:201 @@ -1365,9 +1163,7 @@ msgid "🌐 Translation" msgstr "" #: ../../../README.md:203 -msgid "" -"See the [i18n/README.md](i18n/README.md) file for more information about " -"translation." +msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation." msgstr "" #: ../../../README.md:205 @@ -1379,21 +1175,9 @@ msgid "🤝 Related" msgstr "" #: ../../../README.md:209 -msgid "" -"You may also be interested in [mash-playbook](https://github.com/mother-" -"of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" -"hosting non-Matrix services (see its [List of supported " -"services](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/supported-services.md))." +msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))." msgstr "" #: ../../../README.md:211 -msgid "" -"mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" -"traefik.md) as its reverse-proxy, so with minor [interoperability " -"adjustments](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/interoperability.md), you can make matrix-docker-" -"ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " -"services on the same server." +msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po index 4fa9a26bd..70d2e7f11 100644 --- a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po +++ b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -22,157 +22,47 @@ msgid "2023" msgstr "" #: ../../../YEAR-IN-REVIEW.md:3 -msgid "" -"2023 was a year filled with many changes for matrix-docker-ansible-" -"deploy. In this post, we're looking backward at some of the major changes" -" that happened this year, as well as taking a glimpse of what's ahead in " -"2024." +msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024." msgstr "" #: ../../../YEAR-IN-REVIEW.md:5 -msgid "" -"2023 is probably [the year of AI](https://journal.everypixel.com/2023" -"-the-year-of-ai), with millions of people jumping aboard " -"[OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) " -"train. matrix-docker-ansible-deploy is no stranger to this and 2023 began" -" with a PR from [bertybuttface](https://github.com/bertybuttface) who " -"added support for [matrix-chatgpt-bot](https://github.com/matrixgpt" -"/matrix-chatgpt-bot) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#chatgpt-support)). While OpenAI's chat GPT website was frequently " -"overloaded in the past, their API was up which made using this bot both " -"convenient and more reliable." +msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable." msgstr "" #: ../../../YEAR-IN-REVIEW.md:7 -msgid "" -"AI aside, with the playbook's focus being containers, we're **doubling " -"down on being \"container native\"** and becoming more interoperable for " -"people hosting other containers on the Matrix server. In " -"[2022](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-" -"REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their " -"use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of " -"matrix-docker-ansible-deploy also switching to this reverse-proxy. This " -"prediction materialized quickly. The **largest change** in the playbook " -"in 2023 happened way back in February - matrix-docker-ansible-deploy " -"[starting the switch from nginx to Traefik](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#backward-compatibility-reverse-proxy-configuration-changes-and-initial-" -"traefik-support) and then quickly [making Treafik the default reverse-" -"proxy](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#traefik-is-the-default-reverse-proxy-now). As noted in the changelog " -"entries, we envisioned a quick and complete elimination of `matrix-nginx-" -"proxy`, but at the end of 2023, it hasn't happened yet. The playbook is " -"already using Traefik as the front-most reverse-proxy, but nginx (via " -"`matrix-nginx-proxy`) is still around - it has taken a step back and is " -"only used internally for new setups. Work got to a stall due to:" +msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:9 -msgid "" -"complexity: untangling the overly large and messy `matrix-nginx-proxy` " -"component is difficult" +msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult" msgstr "" #: ../../../YEAR-IN-REVIEW.md:10 -msgid "" -"the current setup became \"good enough\" because nginx has become an " -"internal implementation detail for those who have migrated to Traefik. " -"Traefik is already the default public reverse-proxy and gives better " -"possibilities to people wishing to run other web-exposed containers on " -"their Matrix server via [Docker " -"Compose](https://docs.docker.com/compose/), other Ansible playbooks like " -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) (more about this one, below) or any other way." +msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way." msgstr "" #: ../../../YEAR-IN-REVIEW.md:12 -msgid "" -"`matrix-nginx-proxy` is no longer in the way of us being interoperable, " -"but its ugly internal details are still there. It is one more proxy in " -"the long chain of reverse-proxies we have and we'd like to cut it out. " -"This would both make things simpler and also boost performance." +msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance." msgstr "" #: ../../../YEAR-IN-REVIEW.md:14 -msgid "" -"The delay in eliminating `matrix-nginx-proxy` has probably been welcome " -"by many existing users who decided to postpone the Traefik migration a " -"bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will " -"continue with rapid pace. People who are still using `matrix-nginx-proxy`" -" as their front-most reverse-proxy will need to rework their setup. About" -" a year of putting it off has been long enough." +msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough." msgstr "" #: ../../../YEAR-IN-REVIEW.md:16 -msgid "" -"This large Traefik reverse-proxy change was also accompanied by another " -"internal change which began in 2022, but continued in 2023 - **moving " -"non-Matrix-related roles from being internal to the playbook to living " -"their own life outside of it**. Various roles were made more decoupled " -"and moved outside of the playbook, so that other projects (like the " -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) Ansible playbook or other Ansible playbooks) could benefit from" -" them. This led to the **death of a few sibling playbooks** ([gitea-" -"docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy), [nextcloud-docker-ansible-" -"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), " -"[peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-" -"docker-ansible-deploy), [vaultwarden-docker-ansible-" -"deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-" -"deploy)), but brought life to something better, which supports all these " -"services and more." +msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more." msgstr "" #: ../../../YEAR-IN-REVIEW.md:18 -msgid "" -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) is a new Ansible playbook that a few of us (matrix-docker-" -"ansible-deploy contributors) have launched in 2023. It has quickly grown " -"to supports [60+ services](https://github.com/mother-of-all-self-hosting" -"/mash-playbook/blob/main/docs/supported-services.md) and aims to do the " -"same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" -"source_software) service hosting, as matrix-docker-ansible-deploy has " -"done for Matrix - providing a clean and secure way to run a bunch of " -"services in containers on a regular server (that is to say, without " -"Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to" -" host both mash-playbook services and matrix-docker-ansible-deploy " -"services on the same server - see mash-playbook's " -"[interoperability](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/interoperability.md) documentation page. If " -"you've been looking for a holiday project or your New Year's Resolutions " -"list contains \"self-hosting more services\", then you're welcome to give" -" this new playbook a try and join its Matrix room ([#mash-" -"playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." +msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." msgstr "" #: ../../../YEAR-IN-REVIEW.md:20 -msgid "" -"Because many of the roles are now external to this playbook (defined in " -"the [requirements.yml](https://github.com/spantaleev/matrix-docker-" -"ansible-" -"deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) " -"file), running `make roles` (or better yet `just roles` via the [just " -"tool](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#support-for-running-commands-via-just)) becomes a necessity each time " -"one pulls playbook updates (`git pull`). Pulling external roles happens " -"via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli" -"/ansible-galaxy.html) command-line tool, but if available, the playbook " -"would also use the much faster [agru](https://github.com/etkecc/agru) " -"tool (developed by [Aine](https://gitlab.com/etke.cc) from " -"[etke.cc](https://etke.cc/) this year)." +msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)." msgstr "" #: ../../../YEAR-IN-REVIEW.md:22 -msgid "" -"With the internal (but important) details out of the way, we can now talk" -" more about **new features that landed in matrix-docker-ansible-deploy in" -" 2023**." +msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**." msgstr "" #: ../../../YEAR-IN-REVIEW.md:24 @@ -180,40 +70,19 @@ msgid "The following **new** **bridges** were added to the playbook in 2023:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:26 -msgid "" -"(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a " -"PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#mautrix-slack-support))" +msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:27 -msgid "" -"(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), " -"thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#mautrix-gmessages-support))" +msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:28 -msgid "" -"(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for " -"Apple iMessage bridging (when combined with the [mautrix-" -"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" -" or Android phone), thanks to a PR by [Johan " -"Swetzén](https://github.com/jswetzen)" +msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:30 -msgid "" -"This brings the total number of **[bridges that the playbook " -"supports](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-" -"playbook.md#bridging-other-networks) up to 30**. There are alternative " -"bridge implementations for various networks and protocols, so the number " -"of \"unique bridged networks\" is surely much smaller." +msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller." msgstr "" #: ../../../YEAR-IN-REVIEW.md:32 @@ -221,204 +90,79 @@ msgid "A few other **major components and changes** landed in 2023:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:34 -msgid "" -"(2023-02-10) The [Draupnir](https://github.com/the-draupnir-" -"project/Draupnir) moderation tool (successor to " -"[Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by " -"[FSG-Cat](https://github.com/FSG-Cat) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#draupnir-moderation-tool-bot-support))" +msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:35 -msgid "" -"(2023-02-10) [Matrix User Verification Service](https://github.com" -"/matrix-org/matrix-user-verification-service) to add Matrix " -"Authentication Support to our Jitsi setup, thanks to a PR by [Jakob " -"S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com" -"/zakk-it) (see the [changelog entry](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" -"authentication-support-for-jitsi))" +msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:36 -msgid "" -"(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug" -" report server, thanks to a PR by [Benjamin " -"Kampmann](https://github.com/gnunicorn) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#rageshake-support))" +msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:37 -msgid "" -"(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-" -"sync) (currently a necessary component for [Element " -"X](https://element.io/labs/element-x) to work), thanks to: [Benjamin " -"Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com" -"/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#sliding-sync-proxy-element-x-support))" +msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:38 -msgid "" -"(2023-03-12) synapse-auto-compressor to periodically and automatically " -"run [rust-synapse-compress-state](https://github.com/matrix-org/rust-" -"synapse-compress-state), thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#synapse-auto-compressor-support))" +msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:39 -msgid "" -"(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-" -"media-repo),  thanks to a PR by [Michael Hollister](https://github.com" -"/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of " -"the [Circles app](https://circu.li/) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" -"media-repo-support))" +msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:40 -msgid "" -"(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat" -"/schildichat-desktop) client app (fork of [Element " -"Web)](https://github.com/element-hq/element-web), thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#schildichat-support))" +msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:41 -msgid "" -"(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#postgres-parameters-are-automatically-tuned-now))" +msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:42 -msgid "" -"(2023-10-23) Enabling federation of the room directory for Synapse (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" +msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:44 -msgid "" -"The most recent change in the list above (Enabling federation of the room" -" directory for Synapse) has been somewhat **controversial** as it goes " -"against upstream defaults for Synapse. Nevertheless, we believe it " -"**promotes the well-being of the Matrix Federation by improving room " -"discovery**." +msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**." msgstr "" #: ../../../YEAR-IN-REVIEW.md:46 -msgid "" -"**Matrix Federation Stats** (containing the percentage of servers " -"publishing their room directory publicly) are posted to " -"[TWIM](https://matrix.org/category/this-week-in-matrix/) each week by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The " -"number of servers which [currently published their room directory " -"publicly](https://matrix.org/blog/2023/12/2/this-week-in-" -"matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" +msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:48 -msgid "" -"**2.4% more** than when it was when [first published to " -"TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03" -"/#matrix-federation-stats) (1 month earlier, in November)" +msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:49 -msgid "" -"likely about **15+% more** than from before we flipped the switch (in " -"October)" +msgid "likely about **15+% more** than from before we flipped the switch (in October)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:51 -msgid "" -"Hopefully, Synapse defaults would also change the same way and we'd see " -"the number of servers publicly listing their room directory grow faster." +msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster." msgstr "" #: ../../../YEAR-IN-REVIEW.md:53 -msgid "" -"With this configuration change in place, projects like " -"[MatrixRooms.info](https://matrixrooms.info/) (made by " -"[etke.cc](https://etke.cc/)) and potentially others in the future, can " -"discover, index the metadata (room address, title, topic, number of " -"users, etc.) and make public rooms browsable & searchable across the " -"whole Matrix Federation. It'd be great if users joining Matrix could more" -" easily find interesting communities that match their interests!" +msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!" msgstr "" #: ../../../YEAR-IN-REVIEW.md:55 -msgid "" -"On the **media side of things**, besides Jitsi getting better Matrix " -"integration (via the aforementioned Matrix User Verification Service), " -"we've also had some [Coturn security " -"tightening](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#backward-compatibility-tightening-coturn-security-can-lead-to-" -"connectivity-issues) as well as [performance " -"optimizations](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-" -"can-now-use-host-networking) for configurations exposing lots of network " -"ports." +msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports." msgstr "" #: ../../../YEAR-IN-REVIEW.md:57 -msgid "" -"[Element Call](https://github.com/element-hq/element-call) seems to have " -"become a nice and polished product lately (as proclaimed in [The Matrix " -"Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-" -"holiday-update-2023/)), so 2024 is likely the year we'll see support for " -"it in the playbook. Element Call depends on the " -"[LiveKit](https://livekit.io/) streaming server (which is also useful to " -"developers even by itself), so the first step is likely to see LiveKit " -"support in mash-playbook via a reusable Ansible role. Such a LiveKit " -"Ansible role could later easily land in matrix-docker-ansible-deploy and " -"an Element Call static website could be hooked to it." +msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it." msgstr "" #: ../../../YEAR-IN-REVIEW.md:59 -msgid "" -"Besides these highlights, there were many other relatively large changes " -"announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-" -"ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and " -"hundreds of other more minor (but still important) playbook changes that " -"didn't get a mention." +msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention." msgstr "" #: ../../../YEAR-IN-REVIEW.md:61 -msgid "" -"We have **hundreds of contributors to thank for their hard work** on " -"making Matrix self-hosting better for all of us! It should be noted that " -"**support comes in many shapes**, not only in raw code commits and " -"financial help (via [donations](https://liberapay.com/s.pantaleev) or " -"using the [etke.cc managed Matrix hosting service](https://etke.cc/) " -"which is based on matrix-docker-ansible-deploy). It also comes in the " -"shape of code reviews, helping others with " -"[issues](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues), reporting new issues, participating in our support room " -"on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to" -"/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has " -"been there to make matrix-docker-ansible-deploy better in 2023, thank " -"you! 🙇‍♂️" +msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️" msgstr "" #: ../../../YEAR-IN-REVIEW.md:64 @@ -426,34 +170,11 @@ msgid "2022" msgstr "" #: ../../../YEAR-IN-REVIEW.md:66 -msgid "" -"For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/), 2022 started with **breaking the** " -"[**Synapse**](https://github.com/element-hq/synapse) **monopoly** by " -"[adding support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#dendrite-support) for the [Dendrite](https://github.com/matrix-" -"org/dendrite) Matrix homeserver in early January. This required various " -"internal changes so that the [Ansible](https://www.ansible.com/) playbook" -" would not be Synapse-centric anymore. This groundwork paved the way for " -"continuing in this direction and we [added " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#conduit-support) for [Conduit](https://conduit.rs/) in August." +msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August." msgstr "" #: ../../../YEAR-IN-REVIEW.md:68 -msgid "" -"When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, " -"2022 was the year of the non-Synapse homeserver implementation. In " -"practice, none of these homeserver implementations seem ready for prime-" -"time yet and there is no migration path when coming from Synapse. Having " -"done our job of adding support for these alternative homeserver " -"implementations, we can say that we're not getting in the way of future " -"progress. It's time for the Dendrite developers to push harder " -"(development-wise) and for the Synapse developers to take a well-deserved" -" long (infinite) break, and we may get to see more people migrating away " -"from Synapse in the next year(s)." +msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)." msgstr "" #: ../../../YEAR-IN-REVIEW.md:70 @@ -461,35 +182,19 @@ msgid "Support for the following new **bridges** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:72 -msgid "" -"[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#postmoogle-email-bridge-support) for bi-directional email bridging, " -"which supersedes my old and simplistic " -"[email2matrix](https://github.com/devture/email2matrix) one-way bridge-" -"bot" +msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot" msgstr "" #: ../../../YEAR-IN-REVIEW.md:73 -msgid "" -"[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#mautrix-discord-support)" +msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:74 -msgid "" -"[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-" -"skype-bridge-bridging-support)" +msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:75 -msgid "" -"[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"appservice-kakaotalk-support)" +msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:77 @@ -497,38 +202,23 @@ msgid "Support for the following new **bots** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:79 -msgid "" -"[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#buscarron-bot-support)" +msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:80 -msgid "" -"[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#honoroit-bot-support)" +msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:81 -msgid "" -"[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#matrix-registration-bot-support)" +msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:82 -msgid "" -"[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"hookshot-bridging-support)" +msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:83 -msgid "" -"[maubot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-" -"support)" +msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:85 @@ -536,144 +226,65 @@ msgid "Support for the following new **components and services** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:87 -msgid "" -"[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-" -"backup-support)" +msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:88 -msgid "" -"[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-" -"comments-support)" +msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:89 -msgid "" -"[Cinny](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-" -"support) client support" +msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support" msgstr "" #: ../../../YEAR-IN-REVIEW.md:90 -msgid "" -"[ntfy](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-" -"push-notifications-support) notifications" +msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications" msgstr "" #: ../../../YEAR-IN-REVIEW.md:91 -msgid "" -"[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"ldap-registration-proxy-support)" +msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:92 -msgid "" -"[matrix\\_encryption\\_disabler support](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#matrix_encryption_disabler-support)" +msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:93 -msgid "" -"[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3" -"-storage-provider-support) to stop the Synapse media store from being a " -"scalability problem. This brought along [another " -"feature](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#synapse-container-image-customization-support) - an easier way to " -"customize the Synapse container image without having to fork and self-" -"build all of it from scratch" +msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch" msgstr "" #: ../../../YEAR-IN-REVIEW.md:95 -msgid "" -"Besides these major user-visible changes, a lot of work also happened " -"**under the hood**:" +msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:97 -msgid "" -"we made [major improvements to Synapse " -"workers](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#potential-backward-compatibility-break-major-improvements-to-synapse-" -"workers) - adding support for stream writers and for running multiple " -"workers of various kinds (federation senders, pushers, background task " -"processing workers, etc.)" +msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:98 -msgid "" -"we [improved the compatibility of (Synapse + workers) with the rest of " -"the playbook](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-" -"works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by " -"introducing a new `matrix-synapse-reverse-proxy-companion-service` " -"service" +msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service" msgstr "" #: ../../../YEAR-IN-REVIEW.md:99 -msgid "" -"we started [splitting various Ansible roles out of the Matrix playbook " -"and into independent roles](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-" -"postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-" -"self-hosting/ansible-role-postgres)), which could be included in other " -"Ansible playbooks. In fact, these roles already power a few **interesting" -" other sibling playbooks**:" +msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:100 -msgid "" -"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted " -"[Git](https://git-scm.com/) service) server" +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server" msgstr "" #: ../../../YEAR-IN-REVIEW.md:101 -msgid "" -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy), for deploying a " -"[Nextcloud](https://nextcloud.com/) groupware server" +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server" msgstr "" #: ../../../YEAR-IN-REVIEW.md:102 -msgid "" -"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" -"/vaultwarden-docker-ansible-deploy), for deploying a " -"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) password " -"manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible" -" server)" +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:104 -msgid "" -"These sibling playbooks co-exist nicely with one another due to using " -"[Traefik](https://traefik.io/) for reverse-proxying, instead of trying to" -" overtake the whole server by running their own " -"[nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix " -"playbook will follow suit and be powered by Traefik by default." +msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default." msgstr "" #: ../../../YEAR-IN-REVIEW.md:106 -msgid "" -"Last, but not least, to optimize our [etke.cc managed Matrix hosting " -"service](https://etke.cc/)'s performance (but also individual Ansible " -"playbook runs for people self-hosting by themselves using the playbook), " -"we've [improved playbook runtime 2-5x](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-" -"performance-improvements-in-playbook-runtime) by employing various " -"Ansible tricks." +msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/README.po b/i18n/locales/bg/LC_MESSAGES/docs/README.po index 3df29f3ed..57112b8f3 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/README.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/README.po @@ -26,29 +26,19 @@ msgid "Table of Contents" msgstr "" #: ../../../docs/README.md:3 -msgid "" -"⬇️ Installaton guides " +msgid "⬇️ Installaton guides " msgstr "" #: ../../../docs/README.md:5 -msgid "" -"There are two installation guides available for beginners and advanced " -"users." +msgid "There are two installation guides available for beginners and advanced users." msgstr "" #: ../../../docs/README.md:7 -msgid "" -"⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended " -"for those who do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/README.md:9 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide." msgstr "" #: ../../../docs/README.md:11 @@ -76,59 +66,39 @@ msgid "🛠️ Configuration options" msgstr "" #: ../../../docs/README.md:28 -msgid "" -"You can check useful documentation for configuring components here: " -"[Configuring the playbook](configuring-playbook.md)" +msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)" msgstr "" #: ../../../docs/README.md:30 -msgid "" -"[Administration](configuring-playbook.md#administration) - services that " -"help you in administrating and monitoring your Matrix installation" +msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation" msgstr "" #: ../../../docs/README.md:32 -msgid "" -"[Authentication and user-related](configuring-playbook.md#authentication-" -"and-user-related) - extend and modify how users are authenticated on your" -" homeserver" +msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver" msgstr "" #: ../../../docs/README.md:34 -msgid "" -"[Bots](configuring-playbook.md#bots) - bots provide various additional " -"functionality to your installation" +msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation" msgstr "" #: ../../../docs/README.md:36 -msgid "" -"[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can " -"be used to connect your Matrix installation with third-party " -"communication networks" +msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks" msgstr "" #: ../../../docs/README.md:38 -msgid "" -"[Clients](configuring-playbook.md#clients) - web clients for Matrix that " -"you can host on your own domains" +msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains" msgstr "" #: ../../../docs/README.md:40 -msgid "" -"[Core service adjustments](configuring-playbook.md#core-service-" -"adjustments) - backbone of your Matrix system" +msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system" msgstr "" #: ../../../docs/README.md:42 -msgid "" -"[File Storage](configuring-playbook.md#file-storage) - use alternative " -"file storage to the default `media_store` folder" +msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder" msgstr "" #: ../../../docs/README.md:46 -msgid "" -"[Other specialized services](configuring-playbook.md#other-specialized-" -"services) - various services that don't fit any other categories" +msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories" msgstr "" #: ../../../docs/README.md:48 @@ -136,10 +106,7 @@ msgid "👨‍🔧 Maintenance" msgstr "" #: ../../../docs/README.md:50 -msgid "" -"If your server and services experience issues, feel free to come to [our " -"support room](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com) and ask for help." +msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help." msgstr "" #: ../../../docs/README.md:54 @@ -163,15 +130,11 @@ msgid "[Upgrading services](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/README.md:64 -msgid "" -"Other documentation pages " +msgid "Other documentation pages " msgstr "" #: ../../../docs/README.md:66 -msgid "" -"ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, " -"with a focus on this Ansible playbook" +msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook" msgstr "" #: ../../../docs/README.md:70 @@ -209,4 +172,3 @@ msgstr "" #: ../../../docs/README.md:86 msgid "[Updating users passwords](updating-users-passwords.md)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po index b7254ae41..24b46ed48 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po @@ -26,15 +26,11 @@ msgid "Alternative architectures" msgstr "Алтернативни архитектури" #: ../../../docs/alternative-architectures.md:3 -msgid "" -"As stated in the [Prerequisites](prerequisites.md), currently only " -"`amd64` (`x86_64`) is fully supported." +msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported." msgstr "Както е посочено в [Предусловия](prerequisites.md), в момента само `amd64` (`x86_64`) е напълно поддържана архитектура." #: ../../../docs/alternative-architectures.md:5 -msgid "" -"The playbook automatically determines the target server's architecture " -"(the `matrix_architecture` variable) to be one of the following:" +msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:" msgstr "" #: ../../../docs/alternative-architectures.md:7 @@ -50,9 +46,7 @@ msgid "`arm64`" msgstr "`arm64`" #: ../../../docs/alternative-architectures.md:11 -msgid "" -"Some tools and container images can be built on the host or other " -"measures can be used to install on that architecture." +msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture." msgstr "" #: ../../../docs/alternative-architectures.md:13 @@ -60,19 +54,9 @@ msgid "Implementation details" msgstr "" #: ../../../docs/alternative-architectures.md:15 -msgid "" -"For `amd64`, prebuilt container images (see the [container images we use" -"](container-images.md)) are used for all components (except [Hydrogen" -"](configuring-playbook-client-hydrogen.md), which goes through self-" -"building)." +msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)." msgstr "" #: ../../../docs/alternative-architectures.md:17 -msgid "" -"For other architecture (`arm64`, `arm32`), components which have a " -"prebuilt image make use of it. If the component is not available for the " -"specific architecture, [self-building](self-building.md) will be used. " -"Not all components support self-building though, so your mileage may " -"vary." +msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po index a7f6eea4b..3b6998f22 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po @@ -26,17 +26,11 @@ msgid "Running this playbook" msgstr "" #: ../../../docs/ansible.md:4 -msgid "" -"This playbook is meant to be run using " -"[Ansible](https://www.ansible.com/)." +msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)." msgstr "" #: ../../../docs/ansible.md:6 -msgid "" -"Ansible typically runs on your local computer and carries out tasks on a " -"remote server. If your local computer cannot run Ansible, you can also " -"run Ansible on some server somewhere (including the server you wish to " -"install to)." +msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)." msgstr "" #: ../../../docs/ansible.md:8 @@ -44,30 +38,19 @@ msgid "Supported Ansible versions" msgstr "" #: ../../../docs/ansible.md:10 -msgid "" -"To manually check which version of Ansible you're on, run: `ansible " -"--version`." +msgid "To manually check which version of Ansible you're on, run: `ansible --version`." msgstr "" #: ../../../docs/ansible.md:12 -msgid "" -"For the **best experience**, we recommend getting the **latest version of" -" Ansible available**." +msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**." msgstr "" #: ../../../docs/ansible.md:14 -msgid "" -"We're not sure what's the minimum version of Ansible that can run this " -"playbook successfully. The lowest version that we've confirmed (on " -"2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined " -"with `ansible` (`4.10.0`)." +msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)." msgstr "" #: ../../../docs/ansible.md:16 -msgid "" -"If your distro ships with an Ansible version older than this, you may run" -" into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using " -"Ansible via Docker](#using-ansible-via-docker)." +msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)." msgstr "" #: ../../../docs/ansible.md:18 @@ -75,45 +58,23 @@ msgid "Upgrading Ansible" msgstr "" #: ../../../docs/ansible.md:20 -msgid "" -"Depending on your distribution, you may be able to upgrade Ansible in a " -"few different ways:" +msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:" msgstr "" #: ../../../docs/ansible.md:22 -msgid "" -"by using an additional repository (PPA, etc.), which provides newer " -"Ansible versions. See instructions for " -"[CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-rhel-centos-or-fedora), " -"[Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-debian), or " -"[Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-ubuntu) on the Ansible website." +msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website." msgstr "" #: ../../../docs/ansible.md:24 -msgid "" -"by removing the Ansible package (`yum remove ansible` or `apt-get remove " -"ansible`) and installing via " -"[pip](https://pip.pypa.io/en/stable/installation/) (`pip install " -"ansible`)." +msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)." msgstr "" #: ../../../docs/ansible.md:26 -msgid "" -"If using the `pip` method, do note that the `ansible-playbook` binary may" -" not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-" -"variable), but in some more special location like `/usr/local/bin" -"/ansible-playbook`. You may need to invoke it using the full path." +msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path." msgstr "" #: ../../../docs/ansible.md:28 -msgid "" -"**Note**: Both of the above methods are a bad way to run system software " -"such as Ansible. If you find yourself needing to resort to such hacks, " -"please consider reporting a bug to your distribution and/or switching to " -"a sane distribution, which provides up-to-date software." +msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software." msgstr "" #: ../../../docs/ansible.md:30 @@ -121,25 +82,15 @@ msgid "Using Ansible via Docker" msgstr "" #: ../../../docs/ansible.md:32 -msgid "" -"Alternatively, you can run Ansible inside a Docker container (powered by " -"the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker " -"image)." +msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)." msgstr "" #: ../../../docs/ansible.md:34 -msgid "" -"This ensures that you're using a very recent Ansible version, which is " -"less likely to be incompatible with the playbook." +msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook." msgstr "" #: ../../../docs/ansible.md:36 -msgid "" -"You can either [run Ansible in a container on the Matrix server itself" -"](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run " -"Ansible in a container on another computer (not the Matrix server" -")](#running-ansible-in-a-container-on-another-computer-not-the-matrix-" -"server)." +msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)." msgstr "" #: ../../../docs/ansible.md:38 @@ -147,52 +98,27 @@ msgid "Running Ansible in a container on the Matrix server itself" msgstr "" #: ../../../docs/ansible.md:40 -msgid "" -"To run Ansible in a (Docker) container on the Matrix server itself, you " -"need to have a working Docker installation. Docker is normally installed " -"by the playbook, so this may be a bit of a chicken and egg problem. To " -"solve it:" +msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:" msgstr "" #: ../../../docs/ansible.md:42 -msgid "" -"you **either** need to install Docker manually first. Follow [the " -"upstream instructions](https://docs.docker.com/engine/install/) for your " -"distribution and consider setting " -"`matrix_playbook_docker_installation_enabled: false` in your `vars.yml` " -"file, to prevent the playbook from installing Docker" +msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker" msgstr "" #: ../../../docs/ansible.md:43 -msgid "" -"**or** you need to run the playbook in another way (e.g. [Running Ansible" -" in a container on another computer (not the Matrix server)](#running-" -"ansible-in-a-container-on-another-computer-not-the-matrix-server)) at " -"least the first time around" +msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around" msgstr "" #: ../../../docs/ansible.md:45 -msgid "" -"Once you have a working Docker installation on the server, **clone the " -"playbook** somewhere on the server and configure it as per usual " -"(`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in " -"[configuring the playbook](configuring-playbook.md)." +msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)." msgstr "" #: ../../../docs/ansible.md:47 -msgid "" -"You would then need to add `ansible_connection=community.docker.nsenter` " -"to the host line in `inventory/hosts`. This tells Ansible to connect to " -"the \"remote\" machine by switching Linux namespaces with " -"[nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead " -"of using SSH." +msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH." msgstr "" #: ../../../docs/ansible.md:49 -msgid "" -"Alternatively, you can leave your `inventory/hosts` as is and specify the" -" connection type in **each** `ansible-playbook` call you do later, like " -"this: `ansible-playbook --connection=community.docker.nsenter …`" +msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`" msgstr "" #: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 @@ -200,23 +126,15 @@ msgid "Run this from the playbook's directory:" msgstr "" #: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 -msgid "" -"Once you execute the above command, you'll be dropped into a `/work` " -"directory inside a Docker container. The `/work` directory contains the " -"playbook's code." +msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code." msgstr "" #: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 -msgid "" -"First, consider running `git config --global --add safe.directory /work` " -"to [resolve directory ownership issues](#resolve-directory-ownership-" -"issues)." +msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)." msgstr "" #: ../../../docs/ansible.md:67 -msgid "" -"Finally, you can execute `ansible-playbook …` (or `ansible-playbook " -"--connection=community.docker.nsenter …`) commands as per normal now." +msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." msgstr "" #: ../../../docs/ansible.md:69 @@ -224,10 +142,7 @@ msgid "Running Ansible in a container on another computer (not the Matrix server msgstr "" #: ../../../docs/ansible.md:82 -msgid "" -"The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into " -"the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different" -" path (not in `$HOME/.ssh/id_rsa`), adjust that part." +msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part." msgstr "" #: ../../../docs/ansible.md:88 @@ -239,22 +154,15 @@ msgid "If you don't use SSH keys for authentication" msgstr "" #: ../../../docs/ansible.md:92 -msgid "" -"If you don't use SSH keys for authentication, simply remove that whole " -"line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." +msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." msgstr "" #: ../../../docs/ansible.md:94 -msgid "" -"To authenticate at your server using a password, you need to add a " -"package. So, when you are in the shell of the ansible docker container " -"(the previously used `docker run -it …` command), run:" +msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:" msgstr "" #: ../../../docs/ansible.md:100 -msgid "" -"Then, to be asked for the password whenever running an `ansible-" -"playbook` command add `--ask-pass` to the arguments of the command." +msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." msgstr "" #: ../../../docs/ansible.md:102 @@ -262,23 +170,13 @@ msgid "Resolve directory ownership issues" msgstr "" #: ../../../docs/ansible.md:104 -msgid "" -"Because you're `root` in the container running Ansible and this likely " -"differs fom the owner (your regular user account) of the playbook " -"directory outside of the container, certain playbook features which use " -"`git` locally may report warnings such as:" +msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" msgstr "" #: ../../../docs/ansible.md:106 -msgid "" -"fatal: unsafe repository ('/work' is owned by someone else) To add an " -"exception for this directory, call: git config --global --add " -"safe.directory /work" +msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /work" msgstr "" #: ../../../docs/ansible.md:110 -msgid "" -"These errors can be resolved by making `git` trust the playbook directory" -" by running `git config --global --add safe.directory /work`" +msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po index 2013360c8..ebdb77ac7 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po @@ -22,9 +22,7 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-captcha.md:1 -msgid "" -"(Adapted from the [upstream project](https://github.com/element-" -"hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" +msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" msgstr "" #: ../../../docs/configuring-captcha.md:3 @@ -32,17 +30,11 @@ msgid "Overview" msgstr "" #: ../../../docs/configuring-captcha.md:5 -msgid "" -"Captcha can be enabled for this home server. This file explains how to do" -" that." +msgid "Captcha can be enabled for this home server. This file explains how to do that." msgstr "" #: ../../../docs/configuring-captcha.md:7 -msgid "" -"The captcha mechanism used is Google's " -"[ReCaptcha](https://www.google.com/recaptcha/). This requires API keys " -"from Google. If your homeserver is Dendrite then " -"[hCapcha](https://www.hcaptcha.com) can be used instead." +msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead." msgstr "" #: ../../../docs/configuring-captcha.md:9 @@ -64,9 +56,7 @@ msgid "" msgstr "" #: ../../../docs/configuring-captcha.md:17 -msgid "" -"Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox " -"option" +msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option" msgstr "" #: ../../../docs/configuring-captcha.md:19 @@ -74,9 +64,7 @@ msgid "Setting ReCaptcha keys" msgstr "" #: ../../../docs/configuring-captcha.md:21 -msgid "" -"Once registered as above, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-captcha.md:35 @@ -90,4 +78,3 @@ msgstr "" #: ../../../docs/configuring-captcha.md:43 msgid "Setting hCaptcha keys" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po index 6196e1200..c74078901 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po @@ -26,10 +26,7 @@ msgid "Configuring your DNS settings" msgstr "" #: ../../../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)" +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:5 @@ -41,30 +38,19 @@ msgid "DNS setting for server delegation (optional)" msgstr "" #: ../../../docs/configuring-dns.md:9 -msgid "" -"In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " -"we recommend to use a short user ID like `@alice:example.com` instead of " -"`@alice:matrix.example.com`." +msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`." msgstr "" #: ../../../docs/configuring-dns.md:11 -msgid "" -"To use such an ID, you don't need to install anything on the actual " -"`example.com` server. Instead, you need to instruct the Matrix network " -"that Matrix services for `example.com` are redirected over to " -"`matrix.example.com`. This redirection is also known as \"delegation\"." +msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"." msgstr "" #: ../../../docs/configuring-dns.md:13 -msgid "" -"As we discuss in [Server Delegation](howto-server-delegation.md), server " -"delegation can be configured in either of these ways:" +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:" msgstr "" #: ../../../docs/configuring-dns.md:15 -msgid "" -"Setting up a `/.well-known/matrix/server` file on the base domain " -"(`example.com`)" +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" #: ../../../docs/configuring-dns.md:16 @@ -72,29 +58,15 @@ msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" #: ../../../docs/configuring-dns.md:18 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file, instead of using a " -"DNS SRV record." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record." msgstr "" #: ../../../docs/configuring-dns.md:20 -msgid "" -"If you choose the recommended method (file-based delegation), you do not " -"need to configure the DNS record to enable server delegation. You will " -"need to add a necessary configuration later, when you [finalize the " -"installation](installing.md#finalize-the-installation) after installing " -"and starting Matrix services." +msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services." msgstr "" #: ../../../docs/configuring-dns.md:22 -msgid "" -"On the other hand, if you choose this method (setting up a DNS SRV " -"record), you need to configure the additional DNS record as well as " -"adjust SSL certificate handling. Take a look at this documentation for " -"more information: [Server Delegation via a DNS SRV record (advanced" -")](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-" -"advanced)" +msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/configuring-dns.md:24 @@ -102,10 +74,7 @@ msgid "DNS settings for services enabled by default" msgstr "" #: ../../../docs/configuring-dns.md:26 -msgid "" -"To serve the base domain (`example.com`) and [Element Web](configuring-" -"playbook-client-element-web.md) with the default subdomain, adjust DNS " -"records as below." +msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below." msgstr "" #: ../../../docs/configuring-dns.md @@ -161,20 +130,11 @@ msgid "`matrix.example.com`" msgstr "" #: ../../../docs/configuring-dns.md:33 -msgid "" -"As the table illustrates, you need to create 2 subdomains " -"(`matrix.example.com` and `element.example.com`) and point both of them " -"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" #: ../../../docs/configuring-dns.md:35 -msgid "" -"The `element.example.com` subdomain is necessary, because this playbook " -"installs the [Element Web](https://github.com/element-hq/element-web) " -"client for you by default. If you'd rather instruct the playbook not to " -"install Element Web (`matrix_client_element_enabled: false` when " -"[Configuring the playbook](configuring-playbook.md) later), feel free to " -"skip the `element.example.com` DNS record." +msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record." msgstr "" #: ../../../docs/configuring-dns.md:37 @@ -182,9 +142,7 @@ msgid "Be mindful as to how long it will take for the DNS records to propagate." msgstr "" #: ../../../docs/configuring-dns.md:39 -msgid "" -"If you are using Cloudflare DNS, make sure to disable the proxy and set " -"all records to \"DNS only\". Otherwise, fetching certificates will fail." +msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail." msgstr "" #: ../../../docs/configuring-dns.md:41 @@ -192,9 +150,7 @@ msgid "DNS settings for optional services/features" msgstr "" #: ../../../docs/configuring-dns.md:43 -msgid "" -"For other services which may need subdomain settings, see the table below" -" and configure the DNS (`CNAME`) records accordingly." +msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly." msgstr "" #: ../../../docs/configuring-dns.md @@ -218,9 +174,7 @@ msgid "`jitsi`" msgstr "" #: ../../../docs/configuring-dns.md -msgid "" -"[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) " -"monitoring system" +msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system" msgstr "" #: ../../../docs/configuring-dns.md @@ -332,9 +286,7 @@ msgid "443" msgstr "" #: ../../../docs/configuring-dns.md -msgid "" -"[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix" -"](configuring-playbook-email2matrix.md) email bridges" +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges" msgstr "" #: ../../../docs/configuring-dns.md @@ -374,20 +326,11 @@ msgid "SRV record for ma1sd" msgstr "" #: ../../../docs/configuring-dns.md:68 -msgid "" -"To make ma1sd enable its federation features, you need to set up a " -"`_matrix-identity._tcp` SRV record. Don't confuse this with the " -"`_matrix._tcp` SRV record for server delegation. See the table above and " -"[this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for " -"values which need to be specified." +msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified." msgstr "" #: ../../../docs/configuring-dns.md:70 -msgid "" -"When setting up a SRV record, if you are asked for a service and protocol" -" instead of a hostname split the host value from the table where the " -"period is. For example use service as `_matrix-identity` and protocol as " -"`_tcp`." +msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`." msgstr "" #: ../../../docs/configuring-dns.md:72 @@ -395,16 +338,9 @@ msgid "MX and TXT records for Postmoogle" msgstr "" #: ../../../docs/configuring-dns.md:74 -msgid "" -"To make Postmoogle enable its email sending features, you need to " -"configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above " -"for values which need to be specified." +msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified." msgstr "" #: ../../../docs/configuring-dns.md:78 -msgid "" -"[▶️](getting-the-playbook.md) When you're done with the DNS configuration" -" and ready to proceed, continue with [Getting the playbook](getting-the-" -"playbook.md)." +msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index b66d0461a..7c6a635af 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 @@ -22,37 +22,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:1 -msgid "" -"Setting up Prometheus Alertmanager integration via matrix-alertmanager-" -"receiver (optional)" +msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 -msgid "" -"The playbook can install and configure the [matrix-alertmanager-" -"receiver](https://github.com/metio/matrix-alertmanager-receiver) service " -"for you. It's a " -"[client](https://prometheus.io/docs/alerting/latest/clients/) for " -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)," -" allowing you to deliver alerts to Matrix rooms." +msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 -msgid "" -"See the project's [documentation](https://github.com/metio/matrix-" -"alertmanager-receiver/blob/main/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 -msgid "" -"This service is meant to be used with an external " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"instance. It's **not** meant to be integrated with the [Prometheus & " -"Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by" -" this playbook, because the Alertmanager component is not installed by " -"it." +msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 @@ -64,22 +46,15 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 -msgid "" -"This service uses a bot (with a username specified in " -"`matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for " -"delivering messages." +msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 @@ -91,10 +66,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 @@ -102,21 +74,15 @@ msgid "Join to rooms as the bot manually" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 -msgid "" -"ℹ️ **This bot does not accept room invitations automatically**. To " -"deliver messages to rooms, the bot must be joined to all rooms manually." +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:33 -msgid "" -"For each new room you would like the bot to deliver alerts to, invite the" -" bot to the room." +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:35 -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." +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:37 @@ -124,17 +90,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 -msgid "" -"See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " -"additional configuration variables." +msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 @@ -142,26 +102,15 @@ msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 -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." +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:67 -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." +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:69 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 @@ -169,10 +118,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the matrix-alertmanager-receiver domain to the " -"Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 @@ -180,9 +126,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 @@ -190,10 +134,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.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:" +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:94 @@ -201,24 +142,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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:98 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:100 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:102 @@ -230,127 +162,5 @@ msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 -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`." +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 "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/metio/matrix-alertmanager-" -#~ "receiver) to learn more about what " -#~ "this component does and why it " -#~ "might be useful to you." -#~ msgstr "" - -#~ msgid "" -#~ "At the moment, **setting up this " -#~ "service's bot requires some manual " -#~ "actions** as described below in [Account" -#~ " and room preparation](#account-and-" -#~ "room-preparation)." -#~ msgstr "" - -#~ msgid "" -#~ "To enable matrix-alertmanager-receiver, " -#~ "add the following configuration to your" -#~ " `inventory/host_vars/matrix.example.com/vars.yml` file:" -#~ msgstr "" - -#~ msgid "Account and room preparation" -#~ msgstr "" - -#~ msgid "" -#~ "The playbook can automatically create " -#~ "users, but it cannot automatically " -#~ "obtain access tokens, nor perform any" -#~ " of the other manual actions below." -#~ msgstr "" - -#~ msgid "" -#~ "`matrix-alertmanager-receiver` uses a " -#~ "bot (with a username specified in " -#~ "`matrix_alertmanager_receiver_config_matrix_user_id_localpart` -" -#~ " see above) for delivering messages. " -#~ "You need to **manually register this " -#~ "bot acccount and obtain an access " -#~ "token for it**." -#~ msgstr "" - -#~ msgid "" -#~ "[Register a new user](registering-users.md):" -#~ " `ansible-playbook -i inventory/hosts " -#~ "setup.yml --extra-vars='username=bot.alertmanager.receiver" -#~ " password=PASSWORD_FOR_THE_BOT admin=no' --tags" -#~ "=register-user`" -#~ msgstr "" - -#~ msgid "" -#~ "[Obtain an access token](obtaining-access-" -#~ "tokens.md) for the bot's user account" -#~ msgstr "" - -#~ msgid "Invite the bot to a room where you'd like to alerts to be delivered" -#~ msgstr "" - -#~ msgid "" -#~ "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 "" - -#~ msgid "" -#~ "(Optionally) Adjust " -#~ "`matrix_alertmanager_receiver_config_matrix_room_mapping` to " -#~ "create a mapping between the new " -#~ "room and its ID" -#~ msgstr "" - -#~ msgid "" -#~ "Steps 1 and 2 above only need " -#~ "to be done once, while preparing " -#~ "your [configuration](#adjusting-the-playbook-" -#~ "configuration)." -#~ msgstr "" - -#~ msgid "" -#~ "Steps 3 and 4 need to be " -#~ "done for each new room you'd like" -#~ " the bot to deliver alerts to. " -#~ "Step 5 is optional and provides " -#~ "cleaner `/alert/` URLs." -#~ msgstr "" - -#~ msgid "" -#~ "Now that you've [prepared the bot " -#~ "account and room](#account-and-room-" -#~ "preparation), [configured the playbook" -#~ "](#adjusting-the-playbook-configuration), and " -#~ "potentially [adjusted your DNS records" -#~ "](#adjusting-dns-records), you can run " -#~ "the playbook with [playbook tags](playbook-" -#~ "tags.md) as below:" -#~ msgstr "" - -#~ 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 "" - -#~ msgid "" -#~ "This bot does **not** accept room " -#~ "invitations automatically (like many other " -#~ "bots do). To deliver messages to " -#~ "rooms, **the bot must be joined to" -#~ " all rooms manually** - see Step " -#~ "4 of the [Account and room " -#~ "preparation](#account-and-room-preparation) " -#~ "section." -#~ 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 09d10f782..1fc381a95 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 @@ -26,28 +26,15 @@ msgid "Setting up Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 -msgid "" -"Appservice Double Puppet is a homeserver appservice through which bridges" -" (and potentially other services) can impersonate any user on the " -"homeserver." +msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 -msgid "" -"This is useful for performing [double-" -"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via" -" the [appservice method](https://docs.mau.fi/bridges/general/double-" -"puppeting.html#appservice-method-new). The Appservice Double Puppet " -"service is an implementation of this approach." +msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 -msgid "" -"Previously, bridges supported performing [double-" -"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"with the help of the [Shared Secret Auth password provider module" -"](./configuring-playbook-shared-secret-auth.md), but this old and hacky " -"solution has been superseded by this Appservice Double Puppet method." +msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 @@ -55,10 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 -msgid "" -"To enable the Appservice Double Puppet service, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 @@ -66,9 +50,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 @@ -76,24 +58,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 @@ -101,8 +74,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 -msgid "" -"When enabled, double puppeting will automatically be enabled for all " -"bridges that support double puppeting via the appservice method." +msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po index e993b61b9..e4c00fb90 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 @@ -26,17 +26,11 @@ msgid "Setting up Draupnir for All/D4A (optional)" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 -msgid "" -"The playbook can install and configure the [Draupnir](https://github.com" -"/the-draupnir-project/Draupnir) moderation tool for you in appservice " -"mode." +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 -msgid "" -"Appservice mode can be used together with the regular [Draupnir bot" -"](configuring-playbook-bot-draupnir.md) or independently. Details about " -"the differences between the 2 modes are described below." +msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 @@ -44,43 +38,23 @@ msgid "Draupnir Appservice mode compared to Draupnir bot mode" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 -msgid "" -"The administrative functions for managing the appservice are alpha " -"quality and very limited. However, the experience of using an appservice-" -"provisioned Draupnir is on par with the experience of using Draupnir from" -" bot mode except in the case of avatar customisation as described later " -"on in this document." +msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 -msgid "" -"Draupnir for all is the way to go if you need more than 1 Draupnir " -"instance, but you don't need access to Synapse Admin features as they are" -" not accessible through Draupnir for All (Even though the commands do " -"show up in help)." +msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 -msgid "" -"Draupnir for all in the playbook is rate-limit-exempt automatically as " -"its appservice configuration file does not specify any rate limits." +msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 -msgid "" -"Normal Draupnir does come with the benefit of access to Synapse Admin " -"features. You are also able to more easily customise your normal Draupnir" -" than D4A as D4A even on the branch with the Avatar command (To be " -"Upstreamed to Mainline Draupnir) that command is clunky as it requires " -"the use of things like Element Web devtools. In normal Draupnir this is a" -" quick operation where you login to Draupnir with a normal client and set" -" Avatar and Display name normally." +msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 -msgid "" -"Draupnir for all does not support external tooling like " -"[MRU](https://mru.rory.gay) as it can't access Draupnir's user account." +msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 @@ -92,9 +66,7 @@ msgid "Create a main management room" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 -msgid "" -"The playbook does not create a management room for your Main Draupnir. " -"You **need to create the room manually** before setting up the bot." +msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 @@ -102,25 +74,15 @@ msgid "Note that the room must be unencrypted." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 -msgid "" -"The management room has to be given an alias and be public when you are " -"setting up the bot for the first time as the bot does not differentiate " -"between invites and invites to the management room." +msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 -msgid "" -"This management room is used to control who has access to your D4A " -"deployment. The room stores this data inside of the control room state so" -" your bot must have sufficient powerlevel to send custom state events. " -"This is default 50 or moderator as Element clients call this powerlevel." +msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33 -msgid "" -"As noted in the Draupnir install instructions the control room is " -"sensitive. **Anyone in this room can control the bot so it is important " -"that you only invite trusted users to this room.**" +msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35 @@ -132,11 +94,7 @@ msgid "Next, set an alias to the management room." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39 -msgid "" -"This alias can be anything you want. However, for increased security " -"during the setup phase, it is recommended to make this alias be a random " -"string. When it has been locked down after setup phase, you can give your" -" room a secondary human readable alias." +msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41 @@ -144,10 +102,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ALIAS_HERE`." +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 @@ -155,22 +110,15 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 -msgid "" -"You can configure additional options by adding the " -"`matrix_appservice_draupnir_for_all_extension_yaml` variable." +msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55 -msgid "" -"For example, to change Draupnir's `protectAllJoinedRooms` option to " -"`true`, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 -msgid "" -"You can refer to the upstream [documentation](https://github.com/the-" -"draupnir-project/Draupnir) for more configuration documentation." +msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 @@ -179,19 +127,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 -msgid "" -"The playbook ships a full copy of the example config that does transfer " -"to provisioned Draupnirs in the production-bots.yaml.j2 file in the " -"template directory of the role." +msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 -msgid "" -"Config extension does not affect the appservices config as this config is" -" not extensible in current Draupnir anyway. It instead touches the config" -" passed to the Draupnirs that your Appservice creates. So the example " -"above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs " -"protect all joined rooms." +msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 @@ -199,30 +139,19 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 @@ -230,17 +159,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 -msgid "" -"If you made it through all the steps above and your main control room was" -" joined by a user called `@draupnir-main:example.com` you have " -"succesfully installed Draupnir for All and can now start using it." +msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98 -msgid "" -"The installation of Draupnir for all in this playbook is very much Alpha " -"quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot" -" mode." +msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 @@ -248,32 +171,15 @@ msgid "Granting Users the ability to use D4A" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 -msgid "" -"Draupnir for all includes several security measures like that it only " -"allows users that are on its allow list to ask for a bot. To add a user " -"to this list we have 2 primary options. Using the chat to tell Draupnir " -"to do this for us or if you want to automatically do it by sending " -"`m.policy.rule.user` events that target the subject you want to allow " -"provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using" -" the chat is recomended." +msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 -msgid "" -"The bot requires a powerlevel of 50 in the management room to control who" -" is allowed to use the bot. The bot does currently not say anything if " -"this is true or false. (This is considered a bug and is documented in " -"issue [#297](https://github.com/the-draupnir-" -"project/Draupnir/issues/297))" +msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 -msgid "" -"To allow users or whole homeservers you type /plain @draupnir-" -"main:example.com allow `target` and target can be either a MXID or a " -"wildcard like `@*:example.com` to allow all users on example.com to " -"register. We use /plain to force the client to not attempt to mess with " -"this command as it can break Wildcard commands especially." +msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 @@ -281,141 +187,9 @@ msgid "How to provision a D4A once you are allowed to" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 -msgid "" -"To provision a D4A, you need to start a chat with `@draupnir-" -"main:example.com`. The bot will reject this invite and you will shortly " -"get invited to the Draupnir control room for your newly provisioned " -"Draupnir. From here its just a normal Draupnir experience." +msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 -msgid "" -"Congratulations if you made it all the way here because you now have a " -"fully working Draupnir for all deployment." +msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." msgstr "" - -#~ msgid "Installation" -#~ msgstr "" - -#~ msgid "Create a main management room." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not create a " -#~ "management room for your Main Draupnir." -#~ " This task you have to do on" -#~ " your own." -#~ msgstr "" - -#~ msgid "" -#~ "As noted in the Draupnir install " -#~ "instructions the control room is " -#~ "sensitive. The following is said about" -#~ " the control room in the Draupnir " -#~ "install instructions." -#~ msgstr "" - -#~ msgid "" -#~ "Anyone in this room can control " -#~ "the bot so it is important that" -#~ " you only invite trusted users to " -#~ "this room. The room must be " -#~ "unencrypted since the playbook does not" -#~ " support installing Pantalaimon yet." -#~ msgstr "" - -#~ msgid "Give your main management room an alias." -#~ msgstr "" - -#~ msgid "" -#~ "Give the room from step 1 an " -#~ "alias. This alias can be anything " -#~ "you want and its recommended for " -#~ "increased security during the setup " -#~ "phase of the bot that you make " -#~ "this alias be a random string. You" -#~ " can give your room a secondary " -#~ "human readable alias when it has " -#~ "been locked down after setup phase." -#~ msgstr "" - -#~ msgid "Adjusting the playbook configuration." -#~ msgstr "" - -#~ msgid "" -#~ "Add the following configuration to your" -#~ " `inventory/host_vars/matrix.example.com/vars.yml` file " -#~ "(adapt to your needs):" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` " -#~ "with the alias you created in step" -#~ " 2." -#~ msgstr "" - -#~ msgid "" -#~ "The installation of Draupnir for all " -#~ "in this playbook is very much " -#~ "Alpha quality. Usage-wise, Draupnir for" -#~ " allis almost identical to Draupnir " -#~ "bot mode." -#~ msgstr "" - -#~ msgid "How to provision a D4A once you are allowed to." -#~ msgstr "" - -#~ msgid "" -#~ "Open a DM with @draupnir-" -#~ "main:example.com and if using an Element" -#~ " client send a message into this " -#~ "DM to finalise creating it. The " -#~ "bot will reject this invite and " -#~ "you will shortly get invited to " -#~ "the Draupnir control room for your " -#~ "newly provisioned Draupnir. From here " -#~ "its just a normal Draupnir experience." -#~ msgstr "" - -#~ msgid "Configuration of D4A" -#~ msgstr "" - -#~ msgid "" -#~ "You can refer to the upstream " -#~ "[documentation](https://github.com/the-draupnir-" -#~ "project/Draupnir) for more configuration " -#~ "documentation. Please note that the " -#~ "playbook ships a full copy of the" -#~ " example config that does transfer to" -#~ " provisioned Draupnirs in the " -#~ "production-bots.yaml.j2 file in the " -#~ "template directory of the role." -#~ msgstr "" - -#~ msgid "" -#~ "Please note that Config extension does" -#~ " not affect the appservices config as" -#~ " this config is not extensible in " -#~ "current Draupnir anyways. Config extension " -#~ "instead touches the config passed to " -#~ "the Draupnirs that your Appservice " -#~ "creates. So for example below makes " -#~ "all provisioned Draupnirs protect all " -#~ "joined rooms." -#~ msgstr "" - -#~ msgid "" -#~ "You can configure additional options by" -#~ " adding the " -#~ "`matrix_appservice_draupnir_for_all_extension_yaml` variable " -#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" -#~ " file." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Draupnir's " -#~ "`protectAllJoinedRooms` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ 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 4ba66d027..8d90bc9eb 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 @@ -26,50 +26,27 @@ msgid "Setting up BorgBackup (optional)" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:3 -msgid "" -"The playbook can install and configure " -"[BorgBackup](https://www.borgbackup.org/) (short: Borg) with " -"[borgmatic](https://torsion.org/borgmatic/) for you." +msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:5 -msgid "" -"BorgBackup is a deduplicating backup program with optional compression " -"and encryption. That means your daily incremental backups can be stored " -"in a fraction of the space and is safe whether you store it at home or on" -" a cloud service." +msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:7 -msgid "" -"You will need a remote server where BorgBackup will store the backups. " -"There are hosted, BorgBackup compatible solutions available, such as " -"[BorgBase](https://www.borgbase.com)." +msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:9 -msgid "" -"The backup will run based on `backup_borg_schedule` var (systemd timer " -"calendar), default: 4am every day." +msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:11 -msgid "" -"By default, if you're using the integrated Postgres database server (as " -"opposed to [an external Postgres server](configuring-playbook-external-" -"postgres.md)), backups with BorgBackup will also include dumps of your " -"Postgres database. An alternative solution for backing up the Postgres " -"database is [postgres backup](configuring-playbook-postgres-backup.md). " -"If you decide to go with another solution, you can disable Postgres-" -"backup support for BorgBackup using the `backup_borg_postgresql_enabled` " -"variable." +msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:13 -msgid "" -"**Note**: the component is not managed by this repository but its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"backup_borg)." +msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:15 @@ -77,10 +54,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:17 -msgid "" -"If you do not disable Postgres-backup support, make sure that the " -"Postgres version of your homeserver's database is compatible with " -"borgmatic." +msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:19 @@ -88,21 +62,15 @@ msgid "Create a new SSH key:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:25 -msgid "" -"This can be done on any machine and you don't need to place the key in " -"the `.ssh` folder. It will be added to the Ansible config later." +msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:27 -msgid "" -"Add the **public** part of this SSH key (the `matrix-borg-backup.pub` " -"file) to your BorgBackup provider/server:" +msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:29 -msgid "" -"If you plan to use a hosted solution, follow their instructions. If you " -"have your own server, copy the key over:" +msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:39 @@ -110,9 +78,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:41 -msgid "" -"Minimal working configuration " -"(`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" +msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:58 @@ -128,50 +94,27 @@ msgid "HOST - SSH host of a provider/server" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:62 -msgid "" -"REPO - BorgBackup repository name, it will be initialized on backup " -"start, eg: `matrix`, regarding Syntax see [Remote " -"repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html" -"#repository-urls)" +msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:63 -msgid "" -"PASSPHRASE - passphrase used for encrypting backups, you may generate it " -"with `pwgen -s 64 1` or use any password manager" +msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:64 -msgid "" -"PRIVATE KEY - the content of the **private** part of the SSH key you " -"created before. The whole key (all of its belonging lines) under " -"`backup_borg_ssh_key_private` needs to be indented with 2 spaces" +msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:66 -msgid "" -"To backup without encryption, add `backup_borg_encryption: 'none'` to " -"your vars. This will also enable the " -"`backup_borg_unknown_unencrypted_repo_access_is_ok` variable." +msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:68 -msgid "" -"`backup_borg_location_source_directories` defines the list of directories" -" to back up: it's set to `{{ matrix_base_data_path }}` by default, which " -"is the base directory for every service's data, such as Synapse, Postgres" -" and the bridges. You might want to exclude certain directories or file " -"patterns from the backup using the " -"`backup_borg_location_exclude_patterns` variable." +msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:70 -msgid "" -"Check the [backup_borg role](https://github.com/mother-of-all-self-" -"hosting/ansible-role-backup_borg)'s " -"[defaults/main.yml](https://github.com/mother-of-all-self-hosting" -"/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full " -"list of available options." +msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:72 @@ -179,25 +122,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:74 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:81 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:83 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:85 @@ -205,12 +138,5 @@ msgid "Manually start a backup" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:87 -msgid "" -"For testing your setup it can be helpful to not wait until 4am. If you " -"want to run the backup immediately, log onto the server and run " -"`systemctl start matrix-backup-borg`. This will not return until the " -"backup is done, so possibly a long time. Consider using " -"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " -"unstable." +msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po index 3610179d0..df0ffc237 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po @@ -26,24 +26,15 @@ msgid "Serving the base domain (optional)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:3 -msgid "" -"By default, this playbook sets up services on your Matrix server " -"(`matrix.example.com`), but has it configured so that it presents itself " -"as the base domain (`example.com`). To have this server officially be " -"responsible for Matrix services for the base domain (`example.com`), you " -"need to set up server delegation / redirection." +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:5 -msgid "" -"As we discuss in [Server Delegation](howto-server-delegation.md), server " -"delegation / redirection can be configured in either of these ways:" +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:7 -msgid "" -"Setting up a `/.well-known/matrix/server` file on the base domain " -"(`example.com`)" +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:8 @@ -51,15 +42,11 @@ msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:10 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:12 -msgid "" -"However, those who don't have a separate server to dedicate to the base " -"domain have trouble arranging this." +msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:14 @@ -67,33 +54,19 @@ msgid "Usually, there are 2 options:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:16 -msgid "" -"either get a separate server for the base domain, just for serving the " -"files necessary for [Server Delegation via a well-known file](howto-" -"server-delegation.md#server-delegation-via-a-well-known-file)" +msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:18 -msgid "" -"or, arrange for the Matrix server to serve the base domain. This either " -"involves you [using your own webserver](configuring-playbook-own-" -"webserver.md) or making the integrated webserver serve the base domain " -"for you." +msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:20 -msgid "" -"This documentation page tells you how to do the latter. With some easy " -"changes, we make it possible to serve the base domain from the Matrix " -"server via the integrated webserver." +msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:22 -msgid "" -"Just [**adjust your DNS records**](configuring-dns.md), so that your base" -" domain is pointed to the Matrix server's IP address (using a DNS `A` " -"record) **and then add the following configuration** to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:28 @@ -101,28 +74,15 @@ msgid "Doing this, the playbook will:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:30 -msgid "" -"obtain an SSL certificate for the base domain, just like it does for all " -"other domains (see [how we handle SSL certificates](configuring-playbook-" -"ssl-certificates.md))" +msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:32 -msgid "" -"serve the `/.well-known/matrix/*` files which are necessary for " -"[Federation Server Discovery](configuring-well-known.md#federation-" -"server-discovery) (also see [Server Delegation](howto-server-" -"delegation.md)) and [Client-Server discovery](configuring-well-known.md" -"#client-server-discovery)" +msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:34 -msgid "" -"serve a simple homepage at `https://example.com` with content `Hello from" -" example.com` (configurable via the " -"`matrix_static_files_file_index_html_template` variable). You can also " -"[serve a more complicated static website](#serving-a-static-website-at-" -"the-base-domain)." +msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:36 @@ -130,33 +90,19 @@ msgid "Serving a static website at the base domain" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:38 -msgid "" -"By default, when \"serving the base domain\" is enabled, the playbook " -"hosts a simple `index.html` webpage at `/matrix/static-" -"files/public/index.html`. The content of this page is taken from the " -"`matrix_static_files_file_index_html_template` variable." +msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:40 -msgid "" -"If you'd like to host your own static website (more than a single " -"`index.html` page) at the base domain, you can disable the creation of " -"this default `index.html` page like this:" +msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:54 -msgid "" -"With this configuration, Ansible will no longer mess around with the " -"`/matrix/static-files/public/index.html` file." +msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:56 -msgid "" -"You are then free to upload any static website files to `/matrix/static-" -"files/public` and they will get served at the base domain. You can do so " -"manually or by using the [ansible-role-aux](https://github.com/mother-of-" -"all-self-hosting/ansible-role-aux) Ansible role, which is part of this " -"playbook already." +msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:58 @@ -164,10 +110,7 @@ msgid "Serving a more complicated website at the base domain" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:60 -msgid "" -"If you'd like to serve an even more complicated (dynamic) website from " -"the Matrix server, relying on the playbook to serve the base domain is " -"not the best choice." +msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:62 @@ -179,28 +122,19 @@ msgid "**One way is to host your base domain elsewhere**. This involves:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:65 -msgid "" -"you stopping to serve it from the Matrix server: remove " -"`matrix_static_files_container_labels_base_domain_enabled` from your " -"configuration" +msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:66 -msgid "" -"[configuring Matrix Delegation via well-known](./configuring-well-" -"known.md)" +msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:68 -msgid "" -"**Another way is to serve the base domain from another (your own) " -"container on the Matrix server**. This involves:" +msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:69 -msgid "" -"telling the playbook to only serve `example.com/.well-known/matrix` files" -" by adjusting your `vars.yml` configuration like this:" +msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:70 @@ -208,10 +142,7 @@ msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:71 -msgid "" -"add an extra: " -"`matrix_static_files_container_labels_base_domain_traefik_path_prefix: " -"/.well-known/matrix`" +msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:72 @@ -219,23 +150,13 @@ msgid "building and running a new container on the Matrix server:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:73 -msgid "" -"it should be connected to the `traefik` network, so that Traefik can " -"reverse-proxy to it" +msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:74 -msgid "" -"it should have appropriate [container " -"labels](https://docs.docker.com/config/labels-custom-metadata/), which " -"instruct Traefik to reverse-proxy to it" +msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:76 -msgid "" -"How you'll be managing building and running this container is up-to-you. " -"You may use of the primitives from [ansible-role-aux](https://github.com" -"/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it" -" yourself, or you can set it up in another way." +msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po index be332fe7e..d135c0566 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -26,31 +26,15 @@ msgid "Setting up baibot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:8 -msgid "" -"🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a " -"[Matrix](https://matrix.org/) bot developed by " -"[etke.cc](https://etke.cc/) that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you. 🤖" +msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:10 -msgid "" -"It supports [OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other" -" [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:12 -msgid "" -"It's designed as a more private and [✨ " -"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" -"file#-features) alternative to [matrix-chatgpt-bot](./configuring-" -"playbook-bot-chatgpt.md). See the " -"[baibot](https://github.com/etkecc/baibot) project and its documentation " -"for more information." +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:14 @@ -58,9 +42,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:16 -msgid "" -"API access to one or more LLM [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:18 @@ -68,10 +50,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:20 -msgid "" -"There are **a lot of configuration options** (some required, some " -"possibly required, some optional), so they're **split into multiple " -"sections below**:" +msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:23 @@ -91,16 +70,11 @@ msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:27 -msgid "" -"[🤝 Configuring initial default handlers](#-configuring-initial-default-" -"handlers)" +msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:29 -msgid "" -"Depending on your current `vars.yml` file and desired configuration, " -"**you may require more than just the [base configuration](#base-" -"configuration)**." +msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:31 @@ -108,15 +82,11 @@ msgid "Base configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:33 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:71 -msgid "" -"As mentioned above, **this may not be enough**. Continue with the " -"configuration sections below." +msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:73 @@ -129,25 +99,16 @@ msgid "This is an addition to the [base configuration](#base-configuration)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:77 -msgid "" -"To specify who is considered a bot [👮‍♂️ " -"Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators)," -" you either need to specify " -"`matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The " -"latter is a single variable which affects all bridges and bots." +msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:79 -msgid "" -"If `matrix_admin` is already configured in your `vars.yml` configuration," -" you can skip this section." +msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:81 #: ../../../docs/configuring-playbook-bot-baibot.md:110 -msgid "" -"**If necessary**, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:95 @@ -155,44 +116,27 @@ msgid "👥 Initial users configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:97 -msgid "" -"By default, **all users on your homeserver are considered allowed " -"users**. If that's OK, you can skip this section." +msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:101 -msgid "" -"To specify who is considered a bot [👥 " -"User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), " -"you may:" +msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:103 -msgid "" -"define an **initial** value for " -"`matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible " -"variable, as shown below" +msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:104 -msgid "" -"configure the list at runtime via the bot's `!bai access set-users " -"SPACE_SEPARATED_PATTERNS` command" +msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:106 -msgid "" -"Configuring " -"`matrix_bot_baibot_config_initial_global_config_user_patterns` is " -"optional, but it can be useful to pre-configure the bot with a list of " -"users who should have access to the bot's features." +msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:108 -msgid "" -"**Note**: Once initially configured, the allowed users list **cannot be " -"managed via Ansible anymore**. It can only be managed subsequently via " -"bot commands." +msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:122 @@ -200,61 +144,31 @@ msgid "🤖 Configuring agents via Ansible" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:124 -msgid "" -"You are **not required** to define agents " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration) via Ansible. **To get started quickly**, you can " -"**skip this section and define agents at runtime via chat commands** " -"(following the bot's guidance)." +msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:126 -msgid "" -"Privileged users (like the [👮‍♂️ Administrator](#️-administrator-" -"configuration), but potentially others too - see the upstream [🔒 " -"access](https://github.com/etkecc/baibot/blob/main/docs/access.md) " -"documentation) can **define agents dynamically at any time** via chat " -"commands." +msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:128 -msgid "" -"The Ansible role includes preset variables for easily enabling some [🤖 " -"agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on " -"various [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " -"(e.g. OpenAI, etc)." +msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:130 -msgid "" -"Besides the presets, the Ansible role also includes support for " -"configuring additional statically-defined agents via the " -"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " -"variable." +msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:132 -msgid "" -"Agents defined statically and those created dynamically (via chat) are " -"named differently, so **conflict cannot arise**." +msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:134 -msgid "" -"Depending on your propensity for " -"[GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to " -"define agents statically via Ansible, or you may wish to do it " -"dynamically via chat." +msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:136 -msgid "" -"Before proceeding, we recommend reading the upstream documentation on " -"[How to choose a " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#how-to-choose-a-provider). In short, it's probably best to go with " -"[OpenAI](#openai)." +msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:138 @@ -262,12 +176,7 @@ msgid "Anthropic" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:140 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [Anthropic " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:142 @@ -281,19 +190,14 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:193 #: ../../../docs/configuring-playbook-bot-baibot.md:221 #: ../../../docs/configuring-playbook-bot-baibot.md:251 -msgid "" -"If you'd like to use more than one model, take a look at the [Configuring" -" additional agents (without a preset)](#configuring-additional-agents-" -"without-a-preset) section below." +msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:162 #: ../../../docs/configuring-playbook-bot-baibot.md:195 #: ../../../docs/configuring-playbook-bot-baibot.md:223 #: ../../../docs/configuring-playbook-bot-baibot.md:253 -msgid "" -"💡 You may also wish to use this new agent for [🤝 Configuring initial " -"default handlers](#-configuring-initial-default-handlers)." +msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:164 @@ -301,20 +205,11 @@ msgid "Groq" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:166 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [Groq " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:191 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/groq`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:197 @@ -322,20 +217,11 @@ msgid "Mistral" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:199 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [🇫🇷 Mistral " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:219 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/mistral`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:225 @@ -343,29 +229,15 @@ msgid "OpenAI" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:227 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [OpenAI " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:229 -msgid "" -"The OpenAI provider is **only meant to be used with OpenAI's official " -"API** and compatibility with other services (which do not fully adhere to" -" the OpenAI API spec completely) is limited. **If you're targeting an " -"OpenAI-compatible service**, use the [OpenAI Compatible](#openai-" -"compatible) provider instead." +msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:249 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/openai`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:255 @@ -373,37 +245,19 @@ msgid "OpenAI Compatible" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:257 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [OpenAI Compatible " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#openai-compatible) with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:259 -msgid "" -"This provider allows you to use OpenAI-compatible API services like " -"[OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter)," -" [Together " -"AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#together-ai), etc." +msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:261 -msgid "" -"Some of these popular services already have **shortcut** providers (see " -"[supported " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#supported-providers) leading to this one behind the scenes - this make " -"it easier to get started." +msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:263 -msgid "" -"As of this moment, the playbook does not include presets for any of these" -" services, so you'll need to [Configuring additional agents (without a " -"preset)](#configuring-additional-agents-without-a-preset)." +msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:265 @@ -411,63 +265,35 @@ msgid "Configuring additional agents (without a preset)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:267 -msgid "" -"The Ansible role may be lacking preset variables for some [☁️ " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), " -"or you may wish to statically-define an agent on the same provider twice " -"(or more) with different configuration." +msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:269 -msgid "" -"It's possible to inject your own agent configuration using the " -"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " -"variable." +msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:271 -msgid "" -"You can also define providers at runtime, by chatting with the bot, so " -"using Ansible is not a requirement." +msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:273 -msgid "" -"Below is an an **example** demonstrating **statically-defining agents via" -" Ansible without using presets**:" +msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:312 -msgid "" -"Because these are " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agents, they will be given a `static/` ID " -"prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and " -"`static/my-ollama-agent`, respectively." +msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:314 -msgid "" -"💡 To figure out what to put in the `config` section, refer to the [☁️ " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " -"page, which contains **sample configuration YAML for each provider**." +msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:316 -msgid "" -"As with any [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), " -"defining them means they exist. To actually make use of them, they need " -"to be configured as handlers globally or in a specific room - see [Mixing" -" & matching " -"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" -"--matching-models)." +msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:318 -msgid "" -"💡 You may also wish to use these new agents for [🤝 Configuring initial " -"default handlers](#-configuring-initial-default-handlers)." +msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:320 @@ -475,11 +301,7 @@ msgid "🤝 Configuring initial default handlers" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:322 -msgid "" -"This section is only useful if you're [🤖 Configuring agents via Ansible" -"](#-configuring-agents-via-ansible), as it lets you put these agents to " -"use as soon as the bot starts (by adjusting the bot's **initial global " -"configuration**)." +msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:324 @@ -487,75 +309,43 @@ msgid "If you're not configuring agents via Ansible, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:326 -msgid "" -"This section is only useful the first time around. **Once initially " -"configured the global configuration cannot be managed Ansible**, but only" -" via bot commands." +msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:328 -msgid "" -"baibot supports [various " -"purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" +msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:330 -msgid "" -"[💬 text-" -"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-text-generation): communicating with you via text" +msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:332 -msgid "" -"[🦻 speech-to-" -"text](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-speech-to-text): turning your voice messages into text" +msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:334 -msgid "" -"[🗣️ text-to-" -"speech](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-text-to-speech): turning bot or users text messages into voice messages" +msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:336 -msgid "" -"[🖌️ image-" -"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-image-generation): generating images based on instructions" +msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:338 -msgid "" -"❓ catch-all: special purposes, indicating use as a fallback (when no " -"specific handler is configured)" +msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:340 -msgid "" -"[Mixing & matching " -"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" -"--matching-models) is made possible by the bot's ability to have " -"different [🤝 " -"handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md)" -" configured for different purposes." +msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:342 -msgid "" -"This configuration can be done as a global fallback, or per-room. Both of" -" these [🛠️ " -"configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md)" -" are managed at runtime (viat chat), but **the global configuration can " -"have some initial defaults configured via Ansible**." +msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:344 -msgid "" -"You can configure the **initial values** for these via Ansible, via the " -"`matrix_bot_baibot_config_initial_global_config_handler_*` variables." +msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:346 @@ -563,11 +353,7 @@ msgid "Example **additional** `vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:363 -msgid "" -"**Note**: these are initial defaults for the bot's global configuration. " -"As such, changing any of these values subsequently has no effect on the " -"bot's behavior. **Once initially configured the global configuration " -"cannot be managed Ansible**, but only via bot commands." +msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:365 @@ -575,9 +361,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:367 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:374 @@ -585,35 +369,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:376 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:378 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:380 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:382 -msgid "" -"If you change the bot password (`matrix_bot_baibot_config_user_password` " -"in your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_baibot_config_user_password` to let the bot know its new " -"password." +msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:384 @@ -625,40 +393,23 @@ msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:388 -msgid "" -"If you're an allowed bot [👥 " -"user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) " -"(see [👥 Initial users configuration](#-initial-users-configuration)), the" -" bot will accept your invitation and join the room." +msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:390 -msgid "" -"After joining, the bot will introduce itself and show information about " -"the [✨ " -"features](https://github.com/etkecc/baibot/blob/main/docs/features.md) " -"that are enabled for it." +msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:392 -msgid "" -"If you've [🤖 configured one or more agents via Ansible](#-configuring-" -"agents-via-ansible) and have [🤝 configured initial default handlers" -"](#configuring-initial-default-handlers), the bot will immediately be " -"able to make use of these agents for this new room. Otherwise, you will " -"need to configure agents and/or handlers via chat commands." +msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:394 -msgid "" -"Send `!bai help` to the room at any time to see the bot's help menu for " -"additional commands." +msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:396 -msgid "" -"You can also refer to the upstream " -"[baibot](https://github.com/etkecc/baibot) project's documentation." +msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:398 @@ -666,23 +417,13 @@ msgid "Debugging" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:400 -msgid "" -"As with all other services, you can find service logs in [systemd-" -"journald](https://www.freedesktop.org/software/systemd/man/systemd-" -"journald.service.html) by running something like `journalctl -fu matrix-" -"bot-baibot`" +msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:402 -msgid "" -"The default logging level for this service is `info`, but you can " -"increase it to `debug` (or even `trace`) with the following additional " -"configuration:" +msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:416 -msgid "" -"**Alternatively**, you can use a single variable to set the logging level" -" for all of the above (bot + all libraries):" +msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po index 5e130d865..1965840a5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -26,15 +26,11 @@ msgid "Setting up Buscarron (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:3 -msgid "" -"The playbook can install and configure " -"[Buscarron](https://github.com/etkecc/buscarron) for you." +msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:5 -msgid "" -"Buscarron is bot that receives HTTP POST submissions of web forms and " -"forwards them to a Matrix room." +msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:7 @@ -42,9 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:9 -msgid "" -"To enable Buscarron, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:32 @@ -52,24 +46,15 @@ msgid "Adjusting the Buscarron URL" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:34 -msgid "" -"By default, this playbook installs Buscarron on the `buscarron.` " -"subdomain (`buscarron.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:36 -msgid "" -"By tweaking the `matrix_bot_buscarron_hostname` and " -"`matrix_bot_buscarron_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:38 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:49 @@ -77,21 +62,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:51 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Buscarron domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:53 -msgid "" -"By default, you will need to create a CNAME record for `buscarron`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:55 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:57 @@ -99,10 +78,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:59 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:66 @@ -110,34 +86,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:68 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:70 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:72 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:74 -msgid "" -"If you change the bot password (`matrix_bot_buscarron_password` in your " -"`vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_buscarron_password` to let the bot know its new password." +msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:76 @@ -145,16 +106,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:78 -msgid "" -"To use the bot, invite the `@bot.buscarron:example.com` to the room you " -"specified in a config, after that any point your form to the form url, " -"example for the `contact` form:" +msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:86 -msgid "" -"**Note**: to fight against spam, Buscarron is **very aggressive when it " -"comes to banning** and will ban you if:" +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:88 @@ -162,27 +118,17 @@ msgid "if you hit the homepage (HTTP `GET` request to `/`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:89 -msgid "" -"if you submit a form to the wrong URL (`POST` request to `/non-existing-" -"form`)" +msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:90 -msgid "" -"if `hasemail` is enabled for the form (like in the example above) and you" -" don't submit an `email` field" +msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:92 -msgid "" -"If you get banned, you'd need to restart the process by running the " -"playbook with `--tags=start` or running `systemctl restart matrix-bot-" -"buscarron` on the server." +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:94 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/buscarron)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index 0106bfc01..06ee33bc8 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 @@ -26,25 +26,15 @@ 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." +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." +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!" +msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:9 @@ -52,9 +42,7 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 @@ -62,9 +50,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:15 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 @@ -76,18 +62,11 @@ msgid "Get an access token and create encryption keys" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:25 -msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:27 -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)." +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:29 @@ -95,10 +74,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:31 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:52 @@ -110,9 +86,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:56 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:63 @@ -120,24 +94,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:65 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:67 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:69 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:71 @@ -145,15 +110,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:73 -msgid "" -"To use the bot, invite the `@bot.chatgpt:example.com` to the room you " -"specified in a config, after that start speaking to it, use the prefix if" -" you configured one or mention the bot." +msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:75 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." +msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index 2b5dc52fe..c0d39766e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -26,30 +26,19 @@ msgid "Setting up Draupnir (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:3 -msgid "" -"The playbook can install and configure the [Draupnir](https://github.com" -"/the-draupnir-project/Draupnir) moderation bot for you." +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:5 -msgid "" -"See the project's [documentation](https://github.com/the-draupnir-" -"project/Draupnir/blob/main/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:7 -msgid "" -"This documentation page is about installing Draupnir in bot mode. As an " -"alternative, you can run a multi-instance Draupnir deployment by " -"installing [Draupnir in appservice mode](./configuring-playbook-" -"appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." +msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:9 -msgid "" -"If your migrating from Mjolnir skip to [this section](#migrating-from-" -"mjolnir-only-required-if-migrating)." +msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:11 @@ -61,15 +50,11 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:15 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 @@ -77,11 +62,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 -msgid "" -"If you would like Draupnir to be able to deactivate users, move aliases, " -"shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc " -"then it must be a server admin so you need to change `admin=no` to " -"`admin=yes` in the command above." +msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 @@ -89,10 +70,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 @@ -100,59 +78,31 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "" -"If your homeserver's implementation is Synapse, you will need to prevent " -"it from rate limiting the bot's account. **This is a required step. If " -"you do not configure it, Draupnir will crash.**" +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "" -"This can be done using Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). They can be accessed both externally and " -"internally." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 -msgid "" -"To expose the APIs publicly, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:43 -msgid "" -"The APIs can also be accessed via [Synapse " -"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " -"use to administrate users, rooms, media, etc. on your Matrix server. The " -"playbook can install and configure Synapse Admin for you. For details " -"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:45 -msgid "" -"**Note**: access to the APIs is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, " -"doing so is not recommended for additional security. See [official " -"Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints)." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:47 -msgid "" -"To discharge rate limiting, run the following command on systems that " -"ship curl (note that it does not work on outdated Windows 10). Even if " -"the APIs are not exposed to the internet, you should still be able to run" -" the command on the homeserver locally. Before running it, make sure to " -"replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:53 -msgid "" -"You can obtain an access token for a homeserver admin account in the same" -" way as you can do so for Draupnir itself. If you have made Draupnir an " -"admin, you can just use the Draupnir token." +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:55 @@ -160,32 +110,19 @@ msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:57 -msgid "" -"Using your own account, create a new invite only room that you will use " -"to manage the bot. This is the room where you will see the status of the " -"bot and where you will send commands to the bot, such as the command to " -"ban a user from another room. Anyone in this room can control the bot so " -"it is important that you only invite trusted users to this room." +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:59 -msgid "" -"If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:61 -msgid "" -"Once you have created the room you need to copy the room ID so you can " -"tell the bot to use that room. In Element Web you can do this by going to" -" the room's settings, clicking Advanced, and then copying the internal " -"room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:63 -msgid "" -"Finally invite the `@bot.draupnir:example.com` account you created " -"earlier into the room." +msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:65 @@ -193,10 +130,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:67 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:76 @@ -204,16 +138,11 @@ msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:78 -msgid "" -"Decide whether you want Draupnir to be capable of operating in end-to-end" -" encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms." +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:80 -msgid "" -"To support E2EE, Draupnir needs to [use Pantalaimon](configuring-" -"playbook-pantalaimon.md)." +msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:82 @@ -221,25 +150,15 @@ msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:84 -msgid "" -"When using Pantalaimon, Draupnir will log in to its bot account itself " -"through Pantalaimon, so configure its username and password." +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:86 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:100 -msgid "" -"The playbook's `group_vars` will configure other required settings. If " -"using this role separately without the playbook, you also need to " -"configure the two URLs that Draupnir uses to reach the homeserver, one " -"through Pantalaimon and one \"raw\". This example is taken from the " -"playbook's `group_vars`:" +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:112 @@ -247,17 +166,11 @@ msgid "Configuration without E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:114 -msgid "" -"When NOT using Pantalaimon, Draupnir does not log in by itself and you " -"must give it an access token for its bot account." +msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:116 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:122 @@ -269,19 +182,11 @@ msgid "Draupnir supports two methods to receive reports in the management room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:126 -msgid "" -"The first method intercepts the report API endpoint of the client-server " -"API, which requires integration with the reverse proxy in front of the " -"homeserver. If you are using traefik, this playbook can set this up for " -"you:" +msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:132 -msgid "" -"The other method polls an Synapse Admin API endpoint, hence it is " -"available only if using Synapse and if the Draupnir user is an admin (see" -" [above](#register-the-bot-account)). To enable it, set `pollReports: " -"true` on `vars.yml` file as below." +msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:134 @@ -289,16 +194,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:136 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_draupnir_configuration_extension_yaml` variable." +msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:138 -msgid "" -"For example, to change Draupnir's `pollReports` option to `true`, add the" -" following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:152 @@ -306,15 +206,11 @@ msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:154 -msgid "" -"Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " -"config. Also disable Mjolnir if you're doing migration." +msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:156 -msgid "" -"That is all you need to do due to that Draupnir can complete migration on" -" its own." +msgid "That is all you need to do due to that Draupnir can complete migration on its own." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:158 @@ -322,9 +218,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:160 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:167 @@ -332,35 +226,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:169 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:171 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:173 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:175 -msgid "" -"If you change the Pantalaimon's password " -"(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " -"subsequently, its credentials on the homeserver won't be updated " -"automatically. If you'd like to change the password, use a tool like " -"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " -"then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon" -" know its new password." +msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:177 @@ -368,10 +246,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:179 -msgid "" -"You can refer to the upstream [documentation](https://the-draupnir-" -"project.github.io/draupnir-documentation/) for additional ways to use and" -" configure Draupnir and for a more detailed usage guide." +msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:181 @@ -383,41 +258,23 @@ msgid "Making Draupnir join and protect a room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:185 -msgid "" -"Draupnir can be told to self-join public rooms, but it's better to follow" -" this flow which works well for all kinds of rooms:" +msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:187 -msgid "" -"Invite the bot to the room manually ([inviting Draupnir to rooms](https" -"://the-draupnir-project.github.io/draupnir-documentation/moderator" -"/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, " -"the bot *may* ask for confirmation in the Management Room" +msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:189 -msgid "" -"[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" -"do-its-job)" +msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:191 -msgid "" -"Tell it to protect the room (using the [rooms command](https://the-" -"draupnir-project.github.io/draupnir-documentation/moderator/managing-" -"protected-rooms#using-the-draupnir-rooms-command)) by sending the " -"following command to the Management Room: `!draupnir rooms add " -"!qporfwt:example.com`" +msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:193 -msgid "" -"To have Draupnir provide useful room protection, you need do to a bit " -"more work (at least the first time around). You may wish to [Subscribe to" -" a public policy list](#subscribing-to-a-public-policy-list), [Create " -"your own own policy and rules](#creating-your-own-policy-lists-and-rules)" -" and [Enabling built-in protections](#enabling-built-in-protections)." +msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:195 @@ -425,20 +282,11 @@ msgid "Giving Draupnir permissions to do its job" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:197 -msgid "" -"For Draupnir to do its job, you need to [give it permissions](https" -"://the-draupnir-project.github.io/draupnir-documentation/moderator" -"/managing-protected-rooms#giving-draupnir-permissions) in rooms it's " -"protecting. This involves **giving it an Administrator power level**." +msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:199 -msgid "" -"**We recommend setting this power level as soon as the bot joins your " -"room** (and before you create new rules), so that it can apply rules as " -"soon as they are available. If the bot is under-privileged, it may fail " -"to apply protections and may not retry for a while (or until your restart" -" it)." +msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:201 @@ -446,25 +294,15 @@ msgid "Subscribing to a public policy list" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:203 -msgid "" -"We recommend **subscribing to a public [policy list](https://the-" -"draupnir-project.github.io/draupnir-documentation/concepts/policy-" -"lists)** using the [watch command](https://the-draupnir-project.github.io" -"/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-" -"watch-command-to-subscribe-to-policy-rooms)." +msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:205 -msgid "" -"Polcy lists are maintained in Matrix rooms. A popular policy list is " -"maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:207 -msgid "" -"You can tell Draupnir to subscribe to it by sending the following command" -" to the Management Room: `!draupnir watch #community-moderation-effort-" -"bl:neko.dev`" +msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:209 @@ -472,59 +310,31 @@ msgid "Creating your own policy lists and rules" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:211 -msgid "" -"We also recommend **creating your own policy lists** with the [list " -"create](https://the-draupnir-project.github.io/draupnir-" -"documentation/moderator/managing-policy-lists#using-draupnirs-list-" -"create-command-to-create-a-policy-room) command." +msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:213 -msgid "" -"You can do so by sending the following command to the Management Room: " -"`!draupnir list create my-bans my-bans-bl`. This will create a policy " -"list having a name (shortcode) of `my-bans` and stored in a public `#my-" -"bans-bl:example.com` room on your server. As soon as you run this " -"command, the bot will invite you to the policy list room." +msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:215 -msgid "" -"A policy list does nothing by itself, so the next step is **adding some " -"rules to your policy list**. Policies target a so-called `entity` (one " -"of: `user`, `room` or `server`). These entities are mentioned on the " -"[policy lists](https://the-draupnir-project.github.io/draupnir-" -"documentation/concepts/policy-lists) documentation page and in the Matrix" -" Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-" -"recommendation)." +msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:217 -msgid "" -"The simplest and most useful entity to target is `user`. Below are a few " -"examples using the [ban command](https://the-draupnir-project.github.io" -"/draupnir-documentation/moderator/managing-users#the-ban-command) and " -"targeting users." +msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:219 -msgid "" -"To create rules, you run commands in the Management Room (**not** in the " -"policy list room)." +msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:221 -msgid "" -"(ban a single user on a given homeserver): `!draupnir ban " -"@charles:example.com my-bans Rude to others`" +msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:222 -msgid "" -"(ban all users on a given homeserver by using a [wildcard](https://the-" -"draupnir-project.github.io/draupnir-documentation/moderator/managing-" -"users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - " -"all users are fake`" +msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:224 @@ -532,22 +342,15 @@ msgid "As a result of running these commands, you may observe:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:226 -msgid "" -"Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" -"bl:example.com` room on your server" +msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:227 -msgid "" -"applying these rules against all rooms that Draupnir is an Administrator " -"in" +msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:229 -msgid "" -"You can undo bans with the [unban command](https://the-draupnir-" -"project.github.io/draupnir-documentation/moderator/managing-users#the-" -"unban-command)." +msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:231 @@ -555,186 +358,25 @@ msgid "Enabling built-in protections" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:233 -msgid "" -"You can also **turn on various built-in [protections](https://the-" -"draupnir-project.github.io/draupnir-documentation/protections)** like " -"`JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the " -"room to invite-only\")." +msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:235 -msgid "" -"To **see which protections are available and which are enabled**, send a " -"`!draupnir protections` command to the Management Room." +msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:237 -msgid "" -"To **see the configuration options for a given protection**, send a " -"`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " -"JoinWaveShortCircuit`)." +msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:239 -msgid "" -"To **set a specific option for a given protection**, send a command like " -"this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " -"`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:241 -msgid "" -"To **enable a given protection**, send a command like this: `!draupnir " -"enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:243 -msgid "" -"To **disable a given protection**, send a command like this: `!draupnir " -"disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." +msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/the-draupnir-project/Draupnir) to learn " -#~ "what it does and why it might " -#~ "be useful to you." -#~ msgstr "" - -#~ msgid "If your migrating from Mjolnir skip to step 5b." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not automatically " -#~ "create users for you. The bot " -#~ "requires an access token to be " -#~ "able to connect to your homeserver." -#~ msgstr "" - -#~ msgid "" -#~ "You **need to register the bot " -#~ "user manually** before setting up the" -#~ " bot." -#~ msgstr "" - -#~ msgid "" -#~ "If you would like Draupnir to be" -#~ " able to deactivate users, move " -#~ "aliases, shutdown rooms, show abuse " -#~ "reports ([see below](#abuse-reports)), etc " -#~ "then it must be a server admin " -#~ "so you need to change `admin=no` " -#~ "to `admin=yes` in the command above." -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the documentation on [how " -#~ "to obtain an access token](obtaining-" -#~ "access-tokens.md)." -#~ msgstr "" - -#~ msgid "" -#~ "You will need to prevent Synapse " -#~ "from rate limiting the bot's account." -#~ " This is not an optional step. " -#~ "If you do not do this step " -#~ "Draupnir will crash. This can be " -#~ "done using Synapse's [admin API](https" -#~ "://matrix-" -#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" -#~ "#override-ratelimiting-for-users). Please " -#~ "ask for help if you are " -#~ "uncomfortable with these steps or run" -#~ " into issues." -#~ msgstr "" - -#~ msgid "" -#~ "If your Synapse Admin API is " -#~ "exposed to the internet for some " -#~ "reason like running the Synapse Admin" -#~ " Role [Link](configuring-playbook-synapse-" -#~ "admin.md) or running " -#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -#~ " true` in your playbook config. If" -#~ " your API is not externally exposed" -#~ " you should still be able to on" -#~ " the local host for your synapse " -#~ "run these commands." -#~ msgstr "" - -#~ msgid "" -#~ "The following command works on semi " -#~ "up to date Windows 10 installs and" -#~ " All Windows 11 installations and " -#~ "other systems that ship curl. `curl " -#~ "--header \"Authorization: Bearer \"" -#~ " -X POST " -#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" -#~ " Replace `@bot.draupnir:example.com` with the " -#~ "MXID of your Draupnir and example.com" -#~ " with your homeserver domain. You can" -#~ " easily obtain an access token for" -#~ " a homeserver admin account the same" -#~ " way you can obtain an access " -#~ "token for Draupnir itself. If you " -#~ "made Draupnir Admin you can just " -#~ "use the Draupnir token." -#~ msgstr "" - -#~ msgid "" -#~ "If you make the management room " -#~ "encrypted (E2EE), then you MUST enable" -#~ " and use Pantalaimon (see below)." -#~ msgstr "" - -#~ msgid "" -#~ "Decide whether you want Draupnir to " -#~ "be capable of operating in end-" -#~ "to-end encrypted (E2EE) rooms. This " -#~ "includes the management room and the " -#~ "moderated rooms. To support E2EE, " -#~ "Draupnir needs to [use Pantalaimon" -#~ "](configuring-playbook-pantalaimon.md)." -#~ msgstr "" - -#~ msgid "a. Configuration with E2EE support" -#~ msgstr "" - -#~ msgid "b. Configuration without E2EE support" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace " -#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " -#~ "values." -#~ msgstr "" - -#~ msgid "c. Migrating from Mjolnir (Only required if migrating.)" -#~ msgstr "" - -#~ msgid "" -#~ "You can configure additional options by" -#~ " adding the " -#~ "`matrix_bot_draupnir_configuration_extension_yaml` variable " -#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" -#~ " file." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Draupnir's " -#~ "`recordIgnoredInvites` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ msgstr "" - -#~ msgid "" -#~ "The other method polls an synapse " -#~ "admin API endpoint and is hence " -#~ "only available when using synapse and" -#~ " when the Draupnir user is an " -#~ "admin user (see step 1). To enable" -#~ " it, set `pollReports: true` in " -#~ "Draupnir's config:" -#~ 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 ed983bb62..f9abc1654 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 @@ -22,33 +22,19 @@ msgid "Setting up Go-NEB (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:3 -msgid "" -"**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an " -"archived (**unmaintained**) project. We recommend not bothering with " -"installing it. While not a 1:1 replacement, the bridge's author suggests " -"taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) as a replacement, which can also be installed using [this " -"playbook](configuring-playbook-bridge-hookshot.md). Consider using that " -"bot instead of this one." +msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:5 -msgid "" -"The playbook can install and configure [Go-NEB](https://github.com" -"/matrix-org/go-neb) for you." +msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:7 -msgid "" -"Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, " -"the original Matrix bot written in Python." +msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:9 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/go-" -"neb/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 @@ -56,10 +42,7 @@ msgid "Registering the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires at least 1 access token to be able to connect to your " -"homeserver." +msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:15 @@ -67,9 +50,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:19 @@ -77,9 +58,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:25 -msgid "" -"Once the user is created you can [obtain an access token](obtaining-" -"access-tokens.md)." +msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:27 @@ -87,9 +66,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "" -"To enable Go-NEB, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:193 @@ -97,24 +74,15 @@ msgid "Adjusting the Go-NEB URL" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:195 -msgid "" -"By default, this playbook installs Go-NEB on the `goneb.` subdomain " -"(`goneb.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:197 -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." +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:199 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:210 @@ -122,21 +90,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:212 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Go-NEB domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:214 -msgid "" -"By default, you will need to create a CNAME record for `goneb`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:216 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +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:218 @@ -144,10 +106,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:220 -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 "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:227 @@ -155,24 +114,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:229 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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:231 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:233 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:235 @@ -180,35 +130,17 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:237 -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." +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:239 -msgid "" -"Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy " -"matrix`" +msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:241 -msgid "" -"If you enabled the github_cmd service you can get the supported commands " -"via `!github help`" +msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:243 -msgid "" -"You can also refer to the upstream [Documentation](https://github.com" -"/matrix-org/go-neb)." +msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/go-neb) to learn what it" -#~ " does and why it might be " -#~ "useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index 02ef49eae..827fc18d3 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -26,9 +26,7 @@ msgid "Setting up Honoroit (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:3 -msgid "" -"The playbook can install and configure " -"[Honoroit](https://github.com/etkecc/honoroit) for you." +msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:5 @@ -36,10 +34,7 @@ msgid "It's a bot you can use to setup **your own helpdesk on matrix**" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/etkecc/honoroit/blob/main/README.md) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:9 @@ -47,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:11 -msgid "" -"To enable Honoroit, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:26 @@ -57,25 +50,15 @@ msgid "Adjusting the Honoroit URL" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:28 -msgid "" -"By default, this playbook installs Honoroit on the `matrix.` subdomain, " -"at the `/honoroit` path (https://matrix.example.com/honoroit). This makes" -" it easy to install it, because it **doesn't require additional DNS " -"records to be set up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:30 -msgid "" -"By tweaking the `matrix_bot_honoroit_hostname` and " -"`matrix_bot_honoroit_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:32 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:40 @@ -83,9 +66,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:42 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Honoroit domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:44 @@ -93,9 +74,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:46 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:48 @@ -103,10 +82,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:50 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:57 @@ -114,34 +90,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:59 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:65 -msgid "" -"If you change the bot password (`matrix_bot_honoroit_password` in your " -"`vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_honoroit_password` to let the bot know its new password." +msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:67 @@ -149,29 +110,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:69 -msgid "" -"To use the bot, invite the `@honoroit:example.com` to the room you " -"specified in config, after that any Matrix user can send a message to the" -" `@honoroit:example.com` to start a new thread in that room." +msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "" -"Send `!ho help` to the room to see the bot's help menu for additional " -"commands." +msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/honoroit#features)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/etkecc/honoroit#how-it-" -#~ "looks-like) to learn what it does " -#~ "with screenshots and why it might " -#~ "be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index 9d7ccf99e..073beaf8b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -26,26 +26,15 @@ msgid "Setting up matrix-registration-bot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3 -msgid "" -"The playbook can install and configure [matrix-registration-" -"bot](https://github.com/moan0s/matrix-registration-bot) for you." +msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5 -msgid "" -"The bot allows you to easily **create and manage registration tokens** " -"aka. invitation codes. It can be used for an invitation-based server, " -"where you invite someone by sending them a registration token (tokens " -"look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but " -"have to provide a valid registration token in the final step of the " -"registration process." +msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 -msgid "" -"See the project's [documentation](https://github.com/moan0s/matrix-" -"registration-bot/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 @@ -53,9 +42,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 -msgid "" -"To enable the bot, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30 @@ -67,9 +54,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41 @@ -77,36 +62,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49 -msgid "" -"If you change the bot password " -"(`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` " -"file) subsequently, the bot user's credentials on the homeserver won't be" -" updated automatically. If you'd like to change the bot user's password, " -"use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to" -" change it, and then update " -"`matrix_bot_matrix_registration_bot_bot_password` to let the bot know its" -" new password." +msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51 @@ -114,10 +82,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53 -msgid "" -"To use the bot, start a chat with `@bot.matrix-registration-" -"bot:example.com` (where `example.com` is your base domain, not the " -"`matrix.` domain)." +msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 @@ -125,32 +90,13 @@ msgid "In this room send `help` and the bot will reply with all options." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 -msgid "" -"You can also refer to the upstream [Usage " -"documentation](https://github.com/moan0s/matrix-registration-bot" -"#supported-commands)." +msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59 -msgid "" -"If you have any questions, or if you need help setting it up, read the " -"[troublshooting guide](https://github.com/moan0s/matrix-registration-" -"bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-" -"bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." +msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61 -msgid "" -"To clean the cache (session & encryption data) after you changed the " -"bot's username, changed the login method from access_token to password " -"etc… you can use:" +msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/moan0s/matrix-" -#~ "registration-bot#supported-commands) to learn " -#~ "what it does and why it might " -#~ "be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index 4875ce7c1..fa00c1476 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -26,22 +26,15 @@ msgid "Setting up matrix-reminder-bot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3 -msgid "" -"The playbook can install and configure [matrix-reminder-" -"bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." +msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5 -msgid "" -"It's a bot you can use to **schedule one-off & recurring reminders and " -"alarms**." +msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 -msgid "" -"See the project's [documentation](https://github.com/anoadragon453" -"/matrix-reminder-bot/blob/master/README.md) to learn what it does and why" -" it might be useful to you." +msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 @@ -49,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 @@ -59,9 +50,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35 @@ -69,36 +58,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43 -msgid "" -"If you change the bot password " -"(`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml`" -" file) subsequently, the bot user's credentials on the homeserver won't " -"be updated automatically. If you'd like to change the bot user's " -"password, use a tool like [synapse-admin](configuring-playbook-synapse-" -"admin.md) to change it, and then update " -"`matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know" -" its new password." +msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45 @@ -106,15 +78,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47 -msgid "" -"To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49 -msgid "" -"You can also add the bot to any existing Matrix room (`/invite @bot" -".matrix-reminder-bot:example.com`)." +msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51 @@ -122,23 +90,9 @@ msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53 -msgid "" -"Send `!help reminders` to the room to see the bot's help menu for " -"additional commands." +msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55 -msgid "" -"You can also refer to the upstream [Usage " -"documentation](https://github.com/anoadragon453/matrix-reminder-" -"bot#usage)." +msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/anoadragon453/matrix-" -#~ "reminder-bot#usage) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po index cea5eba6f..cf4454110 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -26,23 +26,15 @@ msgid "Setting up maubot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:3 -msgid "" -"The playbook can install and configure " -"[maubot](https://github.com/maubot/maubot) for you." +msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:5 -msgid "" -"After setting up maubot, you can use the web management interface to make" -" it do things. The default location of the management interface is " -"`matrix.example.com/_matrix/maubot/`" +msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn " -"what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:9 @@ -50,15 +42,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:11 -msgid "" -"To enable maubot, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:26 -msgid "" -"You can add multiple admins. The admin accounts are only used to access " -"the maubot administration interface." +msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:28 @@ -66,26 +54,15 @@ msgid "Adjusting the maubot URL" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:30 -msgid "" -"By default, this playbook installs maubot on the `matrix.` subdomain, at " -"the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/)." -" This makes it easy to install it, because it **doesn't require " -"additional DNS records to be set up**. If that's okay, you can skip this " -"section." +msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:32 -msgid "" -"By tweaking the `matrix_bot_maubot_hostname` and " -"`matrix_bot_maubot_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:42 @@ -93,9 +70,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:44 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the maubot domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:46 @@ -103,9 +78,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:48 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:50 @@ -113,10 +86,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.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:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:59 @@ -124,35 +94,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:61 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:63 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md: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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:67 -msgid "" -"If you change the bot password (`matrix_bot_maubot_initial_password` in " -"your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_maubot_initial_password` to let the bot know its new " -"password." +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:69 @@ -160,9 +114,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:71 -msgid "" -"By default, you can visit `matrix.example.com/_matrix/maubot/` to manage " -"your available plugins, clients and instances." +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:73 @@ -170,24 +122,15 @@ msgid "You should start in the following order" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:74 -msgid "" -"**Create one or more clients**: A client is a Matrix account which the " -"bot will use to message. By default, the playbook creates a `bot.maubot` " -"account (as per the configuration above). You only need to [obtain an " -"access token](#obtaining-an-access-token) for it" +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:75 -msgid "" -"**Upload some Plugins**: Plugins can be obtained from " -"[here](https://github.com/maubot/maubot#plugins) or any other source." +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:76 -msgid "" -"**Create an instance**: An instance is the actual bot. You have to " -"specify a client which the bot instance will use and the plugin (how the " -"bot will behave)" +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 @@ -195,20 +138,9 @@ msgid "Obtaining an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 -msgid "" -"This can be done via `mbc login` then `mbc auth` (see the [maubot " -"documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run " -"these commands, you'll first need to `exec` into the maubot container " -"with `docker exec -it matrix-bot-maubot sh`." +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:82 -msgid "" -"Alternatively, you can follow our generic [obtain an access token" -"](obtaining-access-tokens.md) documentation. Be aware that you'd better " -"use the **Obtain an access token via curl** method (not **Obtain an " -"access token via Element Web**) as the latter will give your bot issues " -"in encrypted rooms. Read " -"[more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index 2075ec200..770378086 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -26,16 +26,11 @@ msgid "Setting up Mjolnir (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:3 -msgid "" -"The playbook can install and configure the [Mjolnir](https://github.com" -"/matrix-org/mjolnir) moderation bot for you." +msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/mjolnir/blob/main/README.md) to learn what it does and why it might " -"be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:7 @@ -47,15 +42,11 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:11 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:15 @@ -63,10 +54,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:21 -msgid "" -"If you would like Mjolnir to be able to deactivate users, move aliases, " -"shutdown rooms, etc then it must be a server admin so you need to change " -"`admin=no` to `admin=yes` in the command above." +msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:23 @@ -74,10 +62,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 @@ -85,59 +70,31 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "" -"If your homeserver's implementation is Synapse, you will need to prevent " -"it from rate limiting the bot's account. **This is a required step. If " -"you do not configure it, Mjolnir will crash.**" +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "" -"This can be done using Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). They can be accessed both externally and " -"internally." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 -msgid "" -"To expose the APIs publicly, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:39 -msgid "" -"The APIs can also be accessed via [Synapse " -"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " -"use to administrate users, rooms, media, etc. on your Matrix server. The " -"playbook can install and configure Synapse Admin for you. For details " -"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:41 -msgid "" -"**Note**: access to the APIs is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, " -"doing so is not recommended for additional security. See [official " -"Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints)." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:43 -msgid "" -"To discharge rate limiting, run the following command on systems that " -"ship curl (note that it does not work on outdated Windows 10). Even if " -"the APIs are not exposed to the internet, you should still be able to run" -" the command on the homeserver locally. Before running it, make sure to " -"replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:49 -msgid "" -"You can obtain an access token for a homeserver admin account in the same" -" way as you can do so for Mjolnir itself. If you have made Mjolnir an " -"admin, you can just use the Mjolnir token." +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:51 @@ -145,32 +102,19 @@ msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:53 -msgid "" -"Using your own account, create a new invite only room that you will use " -"to manage the bot. This is the room where you will see the status of the " -"bot and where you will send commands to the bot, such as the command to " -"ban a user from another room. Anyone in this room can control the bot so " -"it is important that you only invite trusted users to this room." +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:55 -msgid "" -"If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:57 -msgid "" -"Once you have created the room you need to copy the room ID so you can " -"tell the bot to use that room. In Element Web you can do this by going to" -" the room's settings, clicking Advanced, and then copying the internal " -"room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:59 -msgid "" -"Finally invite the `@bot.mjolnir:example.com` account you created earlier" -" into the room." +msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:61 @@ -178,10 +122,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:63 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:72 @@ -189,16 +130,11 @@ msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:74 -msgid "" -"Decide whether you want Mjolnir to be capable of operating in end-to-end " -"encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms." +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:76 -msgid "" -"To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-" -"pantalaimon.md)." +msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:78 @@ -206,25 +142,15 @@ msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:80 -msgid "" -"When using Pantalaimon, Mjolnir will log in to its bot account itself " -"through Pantalaimon, so configure its username and password." +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:82 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:96 -msgid "" -"The playbook's `group_vars` will configure other required settings. If " -"using this role separately without the playbook, you also need to " -"configure the two URLs that Mjolnir uses to reach the homeserver, one " -"through Pantalaimon and one \"raw\". This example is taken from the " -"playbook's `group_vars`:" +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:108 @@ -232,17 +158,11 @@ msgid "Configuration without E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:110 -msgid "" -"When NOT using Pantalaimon, Mjolnir does not log in by itself and you " -"must give it an access token for its bot account." +msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:118 @@ -250,10 +170,7 @@ msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:120 -msgid "" -"To enable Mjolnir synapse antispam module, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file (adapt to your needs):" +msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:130 @@ -261,17 +178,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:132 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:134 -msgid "" -"For example, to change Mjolnir's `recordIgnoredInvites` option to `true`," -" add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:148 @@ -279,9 +190,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:150 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:157 @@ -289,35 +198,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:159 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:161 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:163 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:165 -msgid "" -"If you change the Pantalaimon's password " -"(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " -"subsequently, its credentials on the homeserver won't be updated " -"automatically. If you'd like to change the password, use a tool like " -"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " -"then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon " -"know its new password." +msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:167 @@ -325,120 +218,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:169 -msgid "" -"You can refer to the upstream [documentation](https://github.com/matrix-" -"org/mjolnir) for additional ways to use and configure Mjolnir. Check out " -"their [quickstart guide](https://github.com/matrix-org/mjolnir" -"#quickstart-guide) for some basic commands you can give to the bot." +msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/mjolnir) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not automatically " -#~ "create users for you. The bot " -#~ "requires an access token to be " -#~ "able to connect to your homeserver." -#~ msgstr "" - -#~ msgid "" -#~ "You **need to register the bot " -#~ "user manually** before setting up the" -#~ " bot." -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the documentation on [how " -#~ "to obtain an access token](obtaining-" -#~ "access-tokens.md)." -#~ msgstr "" - -#~ msgid "" -#~ "You will need to prevent Synapse " -#~ "from rate limiting the bot's account." -#~ " This is not an optional step. " -#~ "If you do not do this step " -#~ "Mjolnir will crash. This can be " -#~ "done using Synapse's [admin API](https" -#~ "://matrix-" -#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" -#~ "#override-ratelimiting-for-users). Please " -#~ "ask for help if you are " -#~ "uncomfortable with these steps or run" -#~ " into issues." -#~ msgstr "" - -#~ msgid "" -#~ "If your Synapse Admin API is " -#~ "exposed to the internet for some " -#~ "reason like running the Synapse Admin" -#~ " Role [Link](configuring-playbook-synapse-" -#~ "admin.md) or running " -#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -#~ " true` in your playbook config. If" -#~ " your API is not externally exposed" -#~ " you should still be able to on" -#~ " the local host for your synapse " -#~ "run these commands." -#~ msgstr "" - -#~ msgid "" -#~ "The following command works on semi " -#~ "up to date Windows 10 installs and" -#~ " All Windows 11 installations and " -#~ "other systems that ship curl. `curl " -#~ "--header \"Authorization: Bearer \"" -#~ " -X POST " -#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" -#~ " Replace `@bot.mjolnir:example.com` with the " -#~ "MXID of your Mjolnir and example.com " -#~ "with your homeserver domain. You can " -#~ "easily obtain an access token for " -#~ "a homeserver admin account the same " -#~ "way you can obtain an access token" -#~ " for Mjolnir itself. If you made " -#~ "Mjolnir Admin you can just use the" -#~ " Mjolnir token." -#~ msgstr "" - -#~ msgid "" -#~ "If you make the management room " -#~ "encrypted (E2EE), then you MUST enable" -#~ " and use Pantalaimon (see below)." -#~ msgstr "" - -#~ msgid "" -#~ "Decide whether you want Mjolnir to " -#~ "be capable of operating in end-" -#~ "to-end encrypted (E2EE) rooms. This " -#~ "includes the management room and the " -#~ "moderated rooms. To support E2EE, " -#~ "Mjolnir needs to [use Pantalaimon" -#~ "](configuring-playbook-pantalaimon.md)." -#~ msgstr "" - -#~ msgid "a. Configuration with E2EE support" -#~ msgstr "" - -#~ msgid "b. Configuration without E2EE support" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace " -#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " -#~ "values." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Mjolnir's " -#~ "`recordIgnoredInvites` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ 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 5eeec1393..19e765ead 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 @@ -26,38 +26,23 @@ msgid "Setting up Appservice Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" -"discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-" -"discord.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 -msgid "" -"For using as a Bot we are recommend the Appservice Discord bridge (the " -"one being discussed here), because it supports plumbing." +msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 -msgid "" -"For personal use we recommend the [mautrix-discord](configuring-playbook-" -"bridge-mautrix-discord.md) bridge, because it is the most fully-featured " -"and stable of the 3 Discord bridges supported by the playbook." +msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"discord](https://github.com/matrix-org/matrix-appservice-discord) for " -"you." +msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"appservice-discord/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 @@ -65,10 +50,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 -msgid "" -"Create a Discord Application " -"[here](https://discordapp.com/developers/applications). Then retrieve " -"Client ID, and create a bot from the Bot tab and retrieve the Bot token." +msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 @@ -76,9 +58,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 @@ -86,9 +66,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 @@ -96,24 +74,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 @@ -121,17 +90,11 @@ msgid "Self-Service Bridging (Manual)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 -msgid "" -"Self-service bridging allows you to bridge specific and existing Matrix " -"rooms to specific Discord rooms. To enable it, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 -msgid "" -"**Note**: If self-service bridging is not enabled, `!discord help` " -"commands will return no results." +msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 @@ -140,9 +103,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 -msgid "" -"Once self-service is enabled, start a chat with " -"`@_discord_bot:example.com` and say `!discord help bridge`." +msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 @@ -150,16 +111,11 @@ msgid "Then, follow the instructions in the help output message." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 -msgid "" -"If the bot is not already in the Discord server, follow the provided " -"invite link. This may require you to be a administrator of the Discord " -"server." +msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 -msgid "" -"On the Discord side, you can say `!matrix help` to get a list of " -"available commands to manage the bridge and Matrix users." +msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 @@ -171,26 +127,15 @@ msgid "Portal Bridging (Automatic)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 -msgid "" -"Through portal bridging, Matrix rooms will automatically be created by " -"the bot and bridged to the relevant Discord room. This is done by simply " -"joining a room with a specific name pattern " -"(`#_discord__`)." +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: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." +msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 -msgid "" -"To disable portal bridging, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 @@ -198,26 +143,15 @@ msgid "To get started with Portal Bridging:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 -msgid "" -"To invite the bot to Discord, retrieve the invite link from the `{{ " -"matrix_appservice_discord_config_path }}/invite_link` file on the server " -"(this defaults to `/matrix/appservice-discord/config/invite_link`). You " -"need to peek at the file on the server via SSH, etc., because it's not " -"available via HTTP(S)." +msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 -msgid "" -"Room addresses follow this syntax: `#_discord__`. 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//`." +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:88 -msgid "" -"Once you have figured out the appropriate room address, you can join by " -"doing `/join #_discord__` in your Matrix client." +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:90 @@ -225,23 +159,13 @@ msgid "Getting Administrator access in a portal bridged room" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 -msgid "" -"By default, you won't have Administrator access in rooms created by the " -"bridge." +msgid "By default, you won't have Administrator access in rooms created by the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 -msgid "" -"To adjust room access privileges or do various other things (change the " -"room name subsequently, etc.), you'd wish to become an Administrator." +msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 -msgid "" -"There's the Discord bridge's guide for [setting privileges on bridge " -"managed rooms](https://github.com/matrix-org/matrix-appservice-" -"discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-" -"rooms). To do the same with our container setup, run the following " -"command on the server:" +msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po index 2f33fd7f5..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 @@ -26,24 +26,15 @@ msgid "Setting up Appservice IRC bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 -msgid "" -"**Note**: bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " -"via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) " -"bridge supported by the playbook." +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 -msgid "" -"The playbook can install and configure the [matrix-appservice-" -"irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." +msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"appservice-irc/blob/master/HOWTO.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 @@ -51,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 @@ -61,9 +50,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 @@ -71,24 +58,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 @@ -96,8 +74,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 -msgid "" -"To use the bridge, you need to start a chat with `@irc_bot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po index eb6315d87..f45dd6fa7 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 @@ -26,27 +26,15 @@ msgid "Setting up Appservice Kakaotalk bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) " -"for you. `matrix-appservice-kakaotalk` is a bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" -" based on [node-kakao](https://github.com/storycraft/node-kakao) (now " -"unmaintained) and some [mautrix-" -"facebook](https://github.com/mautrix/facebook) code." +msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 -msgid "" -"⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using" -" this bridge may get your account banned**." +msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 -msgid "" -"See the project's [documentation](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk/src/branch/master/README.md) to learn what it does " -"and why it might be useful to you." +msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 @@ -54,18 +42,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15 @@ -73,16 +54,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 @@ -90,9 +66,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29 @@ -100,18 +74,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 -msgid "" -"`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for " -"some variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 -msgid "" -"`roles/custom/matrix-bridge-appservice-" -"kakaotalk/templates/config.yaml.j2` for the bridge's default " -"configuration. You can override settings (even those that don't have " -"dedicated playbook variables) using the " -"`matrix_appservice_kakaotalk_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_kakaotalk_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 @@ -119,9 +86,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 @@ -129,24 +94,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:49 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51 @@ -154,17 +110,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53 -msgid "" -"To use the bridge, you need to start a chat with " -"`@kakaotalkbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55 -msgid "" -"Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable " -"bridging for your Kakaotalk account. The `--save` flag may be omitted, if" -" you'd rather not save your password." +msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57 @@ -172,10 +122,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 @@ -187,17 +134,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 @@ -205,34 +146,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77 -msgid "" -"make sure you don't log out the `Appservice-Kakaotalk` device some time " -"in the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://src.miscworks.net/fair/matrix-" -#~ "appservice-kakaotalk) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ 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 387f43882..d290ee5a5 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 @@ -31,37 +31,19 @@ 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." +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\"." +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." +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." +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 @@ -73,22 +55,15 @@ 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)." +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." +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`." +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 @@ -136,20 +111,11 @@ 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." +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." +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 @@ -161,10 +127,7 @@ 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." +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 @@ -172,15 +135,11 @@ 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:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 -msgid "" -"Other configuration options are available via the " -"`matrix_appservice_slack_configuration_extension_yaml` variable." +msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 @@ -188,30 +147,19 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83 @@ -219,42 +167,27 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85 -msgid "" -"To use the bridge, you need to send `/invite @slackbot:example.com` to " -"invite the bridge bot user into the admin room." +msgid "To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87 -msgid "" -"If Team Sync is not enabled, for each channel you would like to bridge, " -"perform the following steps:" +msgid "If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 -msgid "" -"Create a Matrix room in the usual manner for your client. Take a note of " -"its Matrix room ID - it will look something like `!qporfwt:example.com`." +msgid "Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID - it will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90 -msgid "" -"Invite the bot user to both the Slack and Matrix channels you would like " -"to bridge using `/invite @matrixbot` for Slack and `/invite " -"@slackbot:example.com` for Matrix." +msgid "Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 -msgid "" -"Determine the \"channel ID\" that Slack uses to identify the channel. You" -" can see it when you open a given Slack channel in a browser. The URL " -"reads like this: `https://app.slack.com/client/XXX//details/`." +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:92 -msgid "" -"Issue a link command in the administration control room with these " -"collected values as arguments:" +msgid "Issue a link command in the administration control room with these collected values as arguments:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94 @@ -278,10 +211,7 @@ msgid "Channels can be unlinked again by sending this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 -msgid "" -"Unlinking doesn't only disconnect the bridge, but also makes the slackbot" -" leave the bridged Matrix room. So in case you want to re-link later, " -"don't forget to re-invite the slackbot into this room again." +msgid "Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122 @@ -297,9 +227,7 @@ msgid "Linking: \"Room is now pending-name\"" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 -msgid "" -"This typically means that you haven't used the correct Slack channel ID. " -"Unlink the room and recheck 'Determine the \"channel ID\"' from above." +msgid "This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the \"channel ID\"' from above." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130 @@ -312,15 +240,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 #, python-format -msgid "" -"`WARN SlackEventHandler Ignoring message from unrecognised Slack channel " -"ID : %s (%s) `" +msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) `" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136 -msgid "" -"then unlink your room, reinvite the bot and re-link it again. This may " -"particularly hit you, if you tried to unsuccessfully link your room " -"multiple times without unlinking it after each failed attempt." +msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po index 27a70d5b4..64a274009 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 @@ -26,27 +26,15 @@ msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 -msgid "" -"**Note**: This bridge has been deprecated. We recommend not bothering " -"with installing it. While not a 1:1 replacement, the bridge's author " -"suggests taking a look at [matrix-hookshot](https://github.com/matrix-org" -"/matrix-hookshot) as a replacement, which can also be installed using " -"[this playbook](configuring-playbook-bridge-hookshot.md). Consider using " -"that bridge instead of this one." +msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for " -"you. This bridge provides support for Slack-compatible webhooks." +msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 -msgid "" -"See the project's [documentation](https://github.com/turt2live/matrix-" -"appservice-webhooks/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 @@ -54,9 +42,7 @@ 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:" +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 @@ -64,9 +50,7 @@ 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:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 @@ -74,24 +58,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -99,27 +74,19 @@ 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." +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)" +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)" +msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 -msgid "" -"You then need to send a message to the bridge bot in order to receive a " -"private message including the webhook link:" +msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 @@ -135,23 +102,13 @@ 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." +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\"." +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." +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 1b533e49e..d837a775d 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 @@ -26,19 +26,11 @@ msgid "Setting up Beeper Linkedin bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 -msgid "" -"The playbook can install and configure [beeper-" -"linkedin](https://github.com/beeper/linkedin) for you, for bridging to " -"[LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on " -"the mautrix-python framework and can be configured in a similar way to " -"the other mautrix bridges" +msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 -msgid "" -"See the project's " -"[documentation](https://github.com/beeper/linkedin/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 @@ -46,34 +38,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-beeper-" -"linkedin/templates/config.yaml.j2` to find other things you would like to" -" configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 @@ -81,9 +62,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 @@ -91,53 +70,31 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 -msgid "" -"Set up Double Puppeting by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 @@ -145,29 +102,19 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 -msgid "" -"To use the bridge, you need to start a chat with " -"`@linkedinbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 -msgid "" -"Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable " -"bridging for your LinkedIn account." +msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 -msgid "" -"After successfully enabling bridging, you may wish to [set up Double " -"Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-" -"or-shared-secret-auth), if you haven't already done so." +msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70 @@ -179,10 +126,5 @@ msgid "Bridge asking for 2FA even if you don't have 2FA enabled" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 -msgid "" -"If you don't have 2FA enabled and are logging in from a strange IP for " -"the first time, LinkedIn will send an email with a one-time code. You can" -" use this code to authorize the bridge session. In my experience, once " -"the IP is authorized, you will not be asked again." +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 b322b503e..6565f7474 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 @@ -26,16 +26,11 @@ msgid "Setting up Go Skype Bridge bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 -msgid "" -"The playbook can install and configure [go-skype-" -"bridge](https://github.com/kelaresg/go-skype-bridge) for you." +msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 -msgid "" -"See the project's [documentation](https://github.com/kelaresg/go-skype-" -"bridge/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 @@ -43,10 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 -msgid "" -"To enable the [Skype](https://www.skype.com/) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15 @@ -54,9 +46,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24 @@ -64,24 +54,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32 @@ -89,19 +70,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34 -msgid "" -"To use the bridge, you need to start a chat with `Skype bridge bot` with " -"the handle `@skypebridgebot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 msgid "Send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 919f68a76..028356920 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 @@ -26,27 +26,15 @@ msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 -msgid "" -"**Note**: bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " -"via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-" -"irc.md) bridge supported by the playbook." +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 -msgid "" -"The playbook can install and configure " -"[Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." +msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/hifi/heisenbridge/blob/master/README.md)" -" to learn what it does and why it might be useful to you. You can also " -"take a look at [this demonstration " -"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 @@ -54,16 +42,11 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 -msgid "" -"To enable Heisenbridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24 -msgid "" -"For a more complete list of variables that you could override, see the " -"[`defaults/main.yml` file](../roles/custom/matrix-bridge-" -"heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26 @@ -71,32 +54,19 @@ msgid "Adjusting the Heisenbridge URL" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28 -msgid "" -"By default, this playbook installs Heisenbridge on the `matrix.` " -"subdomain, at the `/heisenbridge` path " -"(https://matrix.example.com/heisenbridge). It would handle media requests" -" there (see the [release notes for Heisenbridge " -"v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." +msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 -msgid "" -"This makes it easy to install it, because it **doesn't require additional" -" DNS records to be set up**. If that's okay, you can skip this section." +msgid "This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 -msgid "" -"By tweaking the `matrix_heisenbridge_hostname` and " -"`matrix_heisenbridge_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 @@ -104,9 +74,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Heisenbridge domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 @@ -114,9 +82,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 @@ -124,10 +90,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 @@ -135,24 +98,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 @@ -160,11 +114,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 -msgid "" -"To use the bridge, you need to start a chat with " -"`@heisenbridge:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain). If the bridge ignores you and a DM is not " -"accepted then the owner setting may be wrong." +msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 @@ -172,24 +122,9 @@ msgid "Help is available for all commands with the `-h` switch." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 -msgid "" -"You can also learn the basics by watching [this demonstration " -"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 -msgid "" -"If you encounter issues or feel lost you can join the project room at " -"[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." +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 "" - -#~ msgid "" -#~ "See the project's " -#~ "[README](https://github.com/hifi/heisenbridge/blob/master/README.md)" -#~ " to learn what it does and why" -#~ " it might be useful to you. You" -#~ " can also take a look at [this" -#~ " demonstration " -#~ "video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." -#~ 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 394ad2aa8..969a85e2a 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 @@ -26,30 +26,19 @@ msgid "Setting up matrix-hookshot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:3 -msgid "" -"The playbook can install and configure [matrix-" -"hookshot](https://github.com/matrix-org/matrix-hookshot) for you." +msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:5 -msgid "" -"Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " -"from software project management services such as GitHub, GitLab, Jira, " -"and Figma, as well as generic webhooks." +msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:7 -msgid "" -"See the project's [documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/hookshot.html) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:9 -msgid "" -"**Note**: the playbook also supports [matrix-appservice-webhooks" -"](configuring-playbook-bridge-appservice-webhooks.md), which however was " -"deprecated by its author." +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 @@ -61,16 +50,11 @@ msgid "Download GitHub app private key (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:15 -msgid "" -"If you're setting up the GitHub bridge, you need to create your GitHub " -"app, and generate a private key file of it." +msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:17 -msgid "" -"You need to download the private key file, if you will install the file " -"manually or with the `aux` role. For details, see [the section below" -"](#manage-github-private-key-with-aux-role)." +msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:19 @@ -78,27 +62,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-" -"github-app-private-key)." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:35 -msgid "" -"For each of the services (GitHub, GitLab, Jira, Figma, and generic " -"webhooks) fill in the respective variables `matrix_hookshot_service_*` " -"listed in [main.yml](../roles/custom/matrix-bridge-" -"hookshot/defaults/main.yml) as required." +msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:37 -msgid "" -"Take special note of the `matrix_hookshot_*_enabled` variables. Services " -"that need no further configuration are enabled by default (GitLab and " -"generic webhooks), while you must first add the required configuration " -"and enable the others (GitHub, Jira, and Figma)." +msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:39 @@ -106,18 +78,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:41 -msgid "" -"You can configure additional options by adding the " -"`matrix_hookshot_configuration_extension_yaml` and " -"`matrix_hookshot_registration_extension_yaml` variables." +msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:43 -msgid "" -"Refer the [official instructions](https://matrix-org.github.io/matrix-" -"hookshot/latest/setup.html) and the comments in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to " -"learn what the individual options do." +msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:45 @@ -125,24 +90,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:47 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:54 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service hookshot` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:56 -msgid "" -"`just install-service hookshot` is useful for maintaining your setup " -"quickly when its components remain unchanged. If you adjust your " -"`vars.yml` to remove other components, you'd need to run `just setup-" -"all`, or these components will still remain installed. Note `just setup-" -"all` runs the `ensure-matrix-users-created` tag too." +msgid "`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:58 @@ -150,35 +106,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:60 -msgid "" -"To use the bridge, you need to create a room and invite the Hookshot bot " -"(`@hookshot:example.com`) to it." +msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:62 -msgid "" -"Make sure the bot is able to send state events (usually the Moderator " -"power level in clients)." +msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:64 -msgid "" -"Send `!hookshot help` to the room to see the bridge's help menu for " -"additional commands." +msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:66 -msgid "" -"Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/usage.html) for more details about using the bridge's " -"various features." +msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:68 -msgid "" -"💡 **Note**: the different listeners are bound to certain paths which " -"might differ from those assumed by the hookshot documentation. See [URLs " -"for bridges setup](#urls-for-bridges-setup) below." +msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:70 @@ -186,9 +130,7 @@ msgid "Reset crypto store" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:72 -msgid "" -"Should the crypto store be corrupted, you can reset it by executing this " -"Ansible playbook with the tag `reset-hookshot-encryption` added:" +msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:78 @@ -200,9 +142,7 @@ msgid "URLs for bridges setup" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:82 -msgid "" -"Unless indicated otherwise, the following endpoints are reachable on your" -" `matrix.` subdomain (if the feature is enabled)." +msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -358,11 +298,7 @@ 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." +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 @@ -370,19 +306,11 @@ msgid "Prometheus" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:96 -msgid "" -"Also see the various `matrix_hookshot_container_labels_*` variables in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), " -"which expose URLs publicly" +msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:98 -msgid "" -"The different listeners are also reachable *internally* in the docker-" -"network via the container's name (configured by " -"`matrix_hookshot_container_url`) and on different ports (e.g. " -"`matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom" -"/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." +msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:100 @@ -390,44 +318,27 @@ msgid "Manage GitHub Private Key with aux role" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:102 -msgid "" -"The GitHub bridge requires you to install a private key file. This can be" -" done in multiple ways:" +msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:104 -msgid "" -"copy the *contents* of the downloaded file and set the variable " -"`matrix_hookshot_github_private_key` to the contents (see example in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." +msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:105 -msgid "" -"somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ " -"matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot" -"/private-key.pem`) on the server manually." +msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:106 -msgid "" -"use the [`aux` role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-aux) to copy the file from an arbitrary path on your " -"ansible client to the correct path on the server." +msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:108 -msgid "" -"To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" -" variable is empty. Then add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:119 -msgid "" -"For more information, see the documentation in the [default configuration" -" of the aux role](https://github.com/mother-of-all-self-hosting/ansible-" -"role-aux/blob/main/defaults/main.yml)." +msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:121 @@ -435,13 +346,7 @@ msgid "Provisioning API" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:123 -msgid "" -"The provisioning API will be enabled automatically if you set " -"`matrix_dimension_enabled: true` and provided a " -"`matrix_hookshot_provisioning_secret`, unless you override it either way." -" To use hookshot with dimension, you will need to enter as \"Provisioning" -" URL\": `http://matrix-hookshot:9002`, which is made up of the variables " -"`matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." +msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:125 @@ -449,45 +354,27 @@ msgid "Metrics" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:127 -msgid "" -"Metrics are **only enabled by default** if the builtin [Prometheus" -"](configuring-playbook-prometheus-grafana.md) is enabled (by default, " -"Prometheus isn't enabled). If so, metrics will automatically be collected" -" by Prometheus and made available in Grafana. You will, however, need to " -"set up your own Dashboard for displaying them." +msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:129 -msgid "" -"To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: " -"true`. This only exposes metrics over the container network, however." +msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:131 -msgid "" -"**To collect metrics from an external Prometheus server**, besides " -"enabling metrics as described above, you will also need to enable metrics" -" exposure on `https://matrix.example.com/metrics/hookshot` by:" +msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:133 -msgid "" -"either enabling metrics exposure for Hookshot via " -"`matrix_hookshot_metrics_proxying_enabled: true`" +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:134 -msgid "" -"or enabling metrics exposure for all services via " -"`matrix_metrics_exposure_enabled: true`" +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:136 -msgid "" -"Whichever one you go with, by default metrics are exposed publicly " -"**without** password-protection. See [the Prometheus and Grafana docs" -"](configuring-playbook-prometheus-grafana.md) for details about password-" -"protection for metrics." +msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:138 @@ -495,184 +382,5 @@ msgid "Collision with matrix-appservice-webhooks" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:140 -msgid "" -"If you are also running [matrix-appservice-webhooks](configuring-" -"playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" -" default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. " -"You should take care if you modify its or hookshot's prefix that they do " -"not collide with each other's namespace (default " -"`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." +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 "" - -#~ 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 "" - -#~ msgid "" -#~ "See the project's [documentation](https://matrix-" -#~ "org.github.io/matrix-hookshot/latest/hookshot.html) to " -#~ "learn what it does in detail and" -#~ " why it might be useful to you." -#~ msgstr "" - -#~ msgid "Setup Instructions" -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the [official instructions](https" -#~ "://matrix-org.github.io/matrix-hookshot/latest/setup.html)" -#~ " to learn what the individual options" -#~ " do." -#~ msgstr "" - -#~ msgid "" -#~ "Enable the bridge by adding " -#~ "`matrix_hookshot_enabled: true` to your " -#~ "`vars.yml` file" -#~ msgstr "" - -#~ msgid "" -#~ "For each of the services (GitHub, " -#~ "GitLab, Jira, Figma, generic webhooks) " -#~ "fill in the respective variables " -#~ "`matrix_hookshot_service_*` listed in " -#~ "[main.yml](/roles/custom/matrix-bridge-" -#~ "hookshot/defaults/main.yml) as required." -#~ msgstr "" - -#~ msgid "" -#~ "Take special note of the " -#~ "`matrix_hookshot_*_enabled` variables. Services that" -#~ " need no further configuration are " -#~ "enabled by default (GitLab, Generic), " -#~ "while you must first add the " -#~ "required configuration and enable the " -#~ "others (GitHub, Jira, Figma)." -#~ msgstr "" - -#~ msgid "" -#~ "If you're setting up the GitHub " -#~ "bridge, you'll need to generate and " -#~ "download a private key file after " -#~ "you created your GitHub app. Copy " -#~ "the contents of that file to the" -#~ " variable `matrix_hookshot_github_private_key` so " -#~ "the playbook can install it for " -#~ "you, or use one of the [other " -#~ "methods](#manage-github-private-key-with-" -#~ "aux-role) explained below." -#~ msgstr "" - -#~ msgid "" -#~ "If you've already installed Matrix " -#~ "services using the playbook before, " -#~ "you'll need to re-run it (`--tags" -#~ "=setup-all,start`). If not, proceed with" -#~ " [configuring other playbook services" -#~ "](configuring-playbook.md) and then with " -#~ "[Installing](installing.md). Get back to this" -#~ " guide once ready. Hookshot can be" -#~ " set up individually using the tag" -#~ " `setup-hookshot`." -#~ msgstr "" - -#~ msgid "" -#~ "Other configuration options are available " -#~ "via the `matrix_hookshot_configuration_extension_yaml` " -#~ "and `matrix_hookshot_registration_extension_yaml` " -#~ "variables, see the comments in " -#~ "[main.yml](/roles/custom/matrix-bridge-" -#~ "hookshot/defaults/main.yml) for how to use " -#~ "them." -#~ msgstr "" - -#~ msgid "Finally, run the playbook (see [installing](installing.md))." -#~ msgstr "" - -#~ msgid "End-to-bridge encryption" -#~ msgstr "" - -#~ msgid "" -#~ "You can enable [encryption](https://matrix-" -#~ "org.github.io/matrix-hookshot/latest/advanced/encryption.html)" -#~ " for Hookshot by adding " -#~ "`matrix_hookshot_encryption_enabled: true` to your" -#~ " configuration (`vars.yml`) and [executing " -#~ "the playbook](installing.md) again." -#~ msgstr "" - -#~ msgid "" -#~ "Should the crypto store be corrupted," -#~ " you can reset it by executing " -#~ "this Ansible playbook with the tag " -#~ "`reset-hookshot-encryption` added, for " -#~ "example `ansible-playbook -i inventory/hosts" -#~ " setup.yml --tags=reset-hookshot-encryption`." -#~ msgstr "" - -#~ msgid "Send a `!hookshot help` message to see a list of help commands." -#~ msgstr "" - -#~ msgid "" -#~ "**Important**: Note that the different " -#~ "listeners are bound to certain paths " -#~ "which might differ from those assumed" -#~ " by the hookshot documentation, see " -#~ "[URLs for bridges setup](#urls-for-" -#~ "bridges-setup) below." -#~ msgstr "" - -#~ msgid "listener" -#~ msgstr "" - -#~ msgid "default path" -#~ msgstr "" - -#~ msgid "variable" -#~ msgstr "" - -#~ msgid "used as" -#~ msgstr "" - -#~ msgid "JIRA OAuth" -#~ msgstr "" - -#~ 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 "" - -#~ 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 "" - -#~ 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 "" - -#~ msgid "" -#~ "To use the `aux` role, make sure" -#~ " the `matrix_hookshot_github_private_key` variable " -#~ "is empty. Then add the following " -#~ "additional configuration:" -#~ 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 d3f504115..c2f8ef9ba 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 @@ -26,23 +26,15 @@ msgid "Setting up Matrix SMS bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 -msgid "" -"The playbook can install and configure [matrix-sms-" -"bridge](https://github.com/benkuly/matrix-sms-bridge) for you." +msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 -msgid "" -"See the project's [documentation](https://github.com/benkuly/matrix-sms-" -"bridge/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 -msgid "" -"**The bridge uses [android-sms-gateway-" -"server](https://github.com/RebekkaMa/android-sms-gateway-server). You " -"need to configure it first.**" +msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 @@ -50,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:34 @@ -60,9 +50,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 @@ -70,24 +58,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 @@ -95,14 +74,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 -msgid "" -"Read the [user guide](https://github.com/benkuly/matrix-sms-" -"bridge/blob/master/README.md#user-guide) to see how this bridge works." +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 "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 270019a1f..2c8767d29 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 @@ -26,38 +26,23 @@ msgid "Setting up Mautrix Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" -"discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-" -"appservice-discord.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4 -msgid "" -"For using as a Bot we recommend the [Appservice Discord](configuring-" -"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 -msgid "" -"For personal use with a discord account we recommend the `mautrix-" -"discord` bridge (the one being discussed here), because it is the most " -"fully-featured and stable of the 3 Discord bridges supported by the " -"playbook." +msgid "For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7 -msgid "" -"The playbook can install and configure [mautrix-" -"discord](https://github.com/mautrix/discord) for you." +msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/discord/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 @@ -65,21 +50,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 -msgid "" -"There are 2 ways to login to discord using this bridge, either by " -"[scanning a QR code](#method-1-login-using-qr-code-recommended) using the" -" Discord mobile app **or** by using a [Discord token](#method-2-login-" -"using-discord-token-not-recommended)." +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 -msgid "" -"If this is a dealbreaker for you, consider using one of the other Discord" -" bridges supported by the playbook: [mx-puppet-discord](configuring-" -"playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord" -"](configuring-playbook-bridge-appservice-discord.md). These come with " -"their own complexity and limitations, however, so we recommend that you " -"proceed with this one if possible." +msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 @@ -87,19 +62,11 @@ msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 @@ -107,16 +74,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 @@ -124,9 +86,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 @@ -134,17 +94,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 -msgid "" -"`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some " -"variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 -msgid "" -"`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for" -" the bridge's default configuration. You can override settings (even " -"those that don't have dedicated playbook variables) using the " -"`matrix_mautrix_discord_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_discord_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 @@ -152,9 +106,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 @@ -162,24 +114,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 @@ -195,9 +138,7 @@ msgid "Method 1: Login using QR code (recommended)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 -msgid "" -"For using this bridge, you would need to authenticate by **scanning a QR " -"code** with the Discord app on your phone." +msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 @@ -209,15 +150,7 @@ msgid "Method 2: Login using Discord token (not recommended)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 -msgid "" -"To acquire the token, open Discord in a private browser window. Then open" -" the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or " -"by pressing \"F12\"). Navigate to the \"Network\" tab then reload the " -"page. In the URL filter or search bar type \"/api\" and find the response" -" with the file name of \"library\". Under the request headers you should " -"find a variable called \"Authorization\", this is the token to your " -"Discord account. After copying the token, you can close the browser " -"window." +msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 @@ -225,34 +158,23 @@ msgid "Bridging" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 -msgid "" -"Start a chat with `@discordbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "Start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:76 -msgid "" -"If you would like to login to Discord using a token, send `login-token` " -"command, otherwise, send `login-qr` command." +msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77 -msgid "" -"You'll see a QR code which you need to scan with the Discord app on your " -"phone. You can scan it with the camera app too, which will open Discord, " -"which will then instruct you to scan it a 2nd time in the Discord app." +msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78 -msgid "" -"After confirming (in the Discord app) that you'd like to allow this " -"login, the bot should respond with \"Succcessfully authenticated as …\"" +msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\"" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 -msgid "" -"Now that you're logged in, you can send a `help` command to the bot " -"again, to see additional commands you have access to" +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 @@ -268,15 +190,11 @@ msgid "send `guilds status` to see the list of guilds" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83 -msgid "" -"for each guild that you'd like bridged, send `guilds bridge GUILD_ID " -"--entire`" +msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84 -msgid "" -"You may wish to uninstall the Discord app from your phone now. It's not " -"needed for the bridge to function." +msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86 @@ -284,10 +202,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90 @@ -295,32 +210,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100 @@ -328,26 +230,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108 -msgid "" -"make sure you don't log out the `Mautrix-Discord` device some time in the" -" future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po index bb76624e0..9325f317c 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 @@ -26,25 +26,15 @@ msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 -msgid "" -"**Note**: This bridge has been deprecated in favor of the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " -"can be installed using [this playbook](configuring-playbook-bridge-" -"mautrix-meta-messenger.md). Consider using that bridge instead of this " -"one." +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"facebook](https://github.com/mautrix/facebook) for you." +msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 @@ -52,18 +42,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 @@ -71,27 +54,19 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 @@ -99,11 +74,7 @@ msgid "Using both would look like" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-facebook/defaults/main.yml` to find other things you would like " -"to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 @@ -111,9 +82,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67 @@ -121,24 +90,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:73 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75 @@ -146,24 +106,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77 -msgid "" -"To use the bridge, you need to start a chat with " -"`@facebookbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79 -msgid "" -"Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable " -"bridging for your Facebook Messenger account. You can learn more here " -"about authentication from the bridge's [official documentation on " -"Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." +msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83 @@ -171,10 +122,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87 @@ -186,17 +134,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95 @@ -204,27 +146,19 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103 -msgid "" -"make sure you don't log out the `Mautrix-Facebook` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105 @@ -236,25 +170,15 @@ msgid "Facebook rejecting login attempts and forcing you to change password" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109 -msgid "" -"If your Matrix server is in a wildly different location than where you " -"usually use your Facebook account from, the bridge's login attempts may " -"be outright rejected by Facebook. Along with that, Facebook may even " -"force you to change the account's password." +msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111 -msgid "" -"If you happen to run into this problem while [setting up " -"bridging](#usage), try to first get a successful session up by logging in" -" to Facebook through the Matrix server's IP address." +msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113 -msgid "" -"The easiest way to do this may be to use " -"[sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic " -"through the Matrix server." +msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115 @@ -262,10 +186,7 @@ msgid "Example command for proxying your traffic through the Matrix server:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121 -msgid "" -"Once connected, you should be able to verify that you're browsing the web" -" through the Matrix server's IP by checking " -"[icanhazip](https://icanhazip.com/)." +msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123 @@ -277,11 +198,5 @@ msgid "Once logged in, proceed to [set up bridging](#usage)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127 -msgid "" -"If that doesn't work, enable 2FA (see: [Facebook help page on enabling " -"2FA](https://www.facebook.com/help/148233965247823)) and try to login " -"again with a new password, and entering the 2FA code when prompted, it " -"may take more then one try, in between attempts, check facebook.com to " -"see if they are requiring another password change" +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 338a8b498..f181bca9b 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 @@ -26,17 +26,11 @@ msgid "Setting up Mautrix Google Messages bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"gmessages](https://github.com/mautrix/gmessages) for you, for bridging to" -" [Google Messages](https://messages.google.com/)." +msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 @@ -44,18 +38,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 @@ -63,9 +50,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 @@ -73,9 +58,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 @@ -83,24 +66,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:36 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 @@ -108,10 +82,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40 -msgid "" -"To use the bridge, you need to start a chat with " -"`@gmessagesbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 @@ -119,10 +90,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46 @@ -134,17 +102,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54 @@ -152,26 +114,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62 -msgid "" -"make sure you don't log out the `Mautrix-gmessages` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po index a86a75fdb..2f4d93ae1 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 @@ -26,16 +26,11 @@ msgid "Setting up Mautrix Google Chat bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"googlechat](https://github.com/mautrix/googlechat) for you." +msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/googlechat/index.html)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 @@ -43,19 +38,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 @@ -63,10 +50,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 -msgid "" -"To enable the [Google Chat](https://chat.google.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 @@ -74,9 +58,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 @@ -84,24 +66,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 @@ -109,38 +82,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40 -msgid "" -"To use the bridge, you need to start a chat with `googlechat bridge bot` " -"with handle `@googlechatbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42 -msgid "" -"Send `login` to the bridge bot to receive a link to the portal from which" -" you can enable the bridging. Open the link sent by the bot and follow " -"the instructions." +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44 -msgid "" -"Automatic login may not work. If it does not, reload the page and select " -"the \"Manual login\" checkbox before starting. Manual login involves " -"logging into your Google account normally and then manually getting the " -"OAuth token from browser cookies with developer tools." +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46 -msgid "" -"Once logged in, recent chats should show up as new conversations " -"automatically. Other chats will get portals as you receive messages." +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48 -msgid "" -"You can learn more about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50 @@ -148,10 +106,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 @@ -159,32 +114,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 @@ -192,26 +134,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72 -msgid "" -"make sure you don't log out the `Mautrix-googlechat` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po index d50b64b16..fa5c12175 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 @@ -26,25 +26,15 @@ msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 -msgid "" -"💡 **Note**: This bridge has been deprecated in favor of [Google Chat " -"bridge](https://github.com/mautrix/googlechat), which can be installed " -"using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md)." -" Installing the mautrix-hangouts bridge is **no longer possible**. For " -"now, this documentation page remains here for historical purposes." +msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"hangouts](https://github.com/mautrix/hangouts) for you." +msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 @@ -52,18 +42,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 @@ -71,10 +54,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17 -msgid "" -"To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23 @@ -82,9 +62,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32 @@ -92,24 +70,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40 @@ -117,38 +86,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 -msgid "" -"To use the bridge, you need to start a chat with `Hangouts bridge bot` " -"with handle `@hangoutsbot:example.com` (where `example.com` is your base " -"domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 -msgid "" -"Send `login` to the bridge bot to receive a link to the portal from which" -" you can enable the bridging. Open the link sent by the bot and follow " -"the instructions." +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 -msgid "" -"Automatic login may not work. If it does not, reload the page and select " -"the \"Manual login\" checkbox before starting. Manual login involves " -"logging into your Google account normally and then manually getting the " -"OAuth token from browser cookies with developer tools." +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 -msgid "" -"Once logged in, recent chats should show up as new conversations " -"automatically. Other chats will get portals as you receive messages." +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 -msgid "" -"You can learn more about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 @@ -156,10 +110,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 @@ -171,17 +122,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64 @@ -189,26 +134,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72 -msgid "" -"make sure you don't log out the `Mautrix-Hangouts` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po index 07597e931..71ddb21c6 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 @@ -26,25 +26,15 @@ msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 -msgid "" -"**Note**: This bridge has been deprecated in favor of the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " -"can be installed using [this playbook](configuring-playbook-bridge-" -"mautrix-meta-instagram.md). Consider using that bridge instead of this " -"one." +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"instagram](https://github.com/mautrix/instagram) for you." +msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/instagram/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 @@ -52,35 +42,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-instagram/defaults/main.yml` to find other things you would like " -"to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45 @@ -88,9 +66,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54 @@ -98,24 +74,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:60 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62 @@ -123,22 +90,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64 -msgid "" -"To use the bridge, you need to start a chat with " -"`@instagrambot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66 -msgid "" -"Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the " -"bridge bot to enable bridging for your instagram/Messenger account." +msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68 -msgid "" -"You can learn more here about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po index bae56eb70..b8e6a3229 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 @@ -26,30 +26,15 @@ msgid "Setting up Instagram bridging via Mautrix Meta (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 -msgid "" -"The playbook can install and configure the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " -"you." +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 -msgid "" -"Since this bridge component can bridge to both " -"[Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/) and you may wish to do both at the " -"same time, the playbook makes it available via 2 different Ansible roles " -"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" -"instagram`). The latter is a reconfigured copy of the first one (created " -"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" -"instagram.sh`)." +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 -msgid "" -"This documentation page only deals with the bridge's ability to bridge to" -" Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger" -" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" -"messenger.md)." +msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 @@ -61,18 +46,11 @@ msgid "Migrating from the old mautrix-instagram bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 -msgid "" -"If you've been using the [mautrix-instagram](./configuring-playbook-" -"bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first**" -" or the 2 bridges will be in conflict:" +msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 -msgid "" -"both trying to use `@instagrambot:example.com` as their username. This " -"conflict may be resolved by adjusting " -"`matrix_mautrix_instagram_appservice_bot_username` or " -"`matrix_mautrix_meta_instagram_appservice_username`" +msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 @@ -80,17 +58,11 @@ msgid "both trying to bridge the same DMs" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 -msgid "" -"To do so, send a `clean-rooms` command to the management room with the " -"old bridge bot (`@instagrambot:example.com`). It gives you a list of " -"portals and groups of portals you may purge. Proceed with sending " -"commands like `clean recommended`, etc." +msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 -msgid "" -"Then, consider disabling the old bridge in your configuration, so it " -"won't recreate the portals when you receive new messages." +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 @@ -98,18 +70,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28 @@ -117,15 +82,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:36 -msgid "" -"Before proceeding to [re-running the playbook](./installing.md), you may " -"wish to adjust the configuration further. See below." +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38 @@ -153,37 +114,23 @@ msgid "`admin` - Use and administer the bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 -msgid "" -"The permissions are following the sequence: nothing < `relay` < `user` < " -"`admin`." +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 -msgid "" -"The default permissions are set via " -"`matrix_mautrix_meta_instagram_bridge_permissions_default` and are " -"somewhat like this:" +msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 -msgid "" -"If you don't define the `matrix_admin` in your configuration (e.g. " -"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61 -msgid "" -"You may redefine " -"`matrix_mautrix_meta_instagram_bridge_permissions_default` any way you " -"see fit, or add extra permissions using " -"`matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" +msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" -"instagram/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 @@ -191,9 +138,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79 @@ -201,24 +146,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:85 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87 @@ -226,10 +162,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89 -msgid "" -"To use the bridge, you need to start a chat with " -"`@instagrambot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91 @@ -237,10 +170,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95 @@ -252,17 +182,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103 @@ -270,27 +194,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111 -msgid "" -"make sure you don't log out the session for which you obtained an access " -"token some time in the future, as that would break the Double Puppeting " -"feature" +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po index bc6aa6588..deedc6840 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 @@ -26,30 +26,15 @@ msgid "Setting up Messenger bridging via Mautrix Meta (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 -msgid "" -"The playbook can install and configure the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " -"you." +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 -msgid "" -"Since this bridge component can bridge to both " -"[Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/) and you may wish to do both at the " -"same time, the playbook makes it available via 2 different Ansible roles " -"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" -"instagram`). The latter is a reconfigured copy of the first one (created " -"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" -"instagram.sh`)." +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 -msgid "" -"This documentation page only deals with the bridge's ability to bridge to" -" Facebook Messenger. For bridging to Instagram, see [Setting up Instagram" -" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" -"instagram.md)." +msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 @@ -61,34 +46,19 @@ msgid "Migrating from the old mautrix-facebook bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 -msgid "" -"If you've been using the [mautrix-facebook](./configuring-playbook-" -"bridge-mautrix-facebook.md) bridge, it's possible to migrate the database" -" using [instructions from the bridge " -"documentation](https://docs.mau.fi/bridges/go/meta/facebook-" -"migration.html) (advanced)." +msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 -msgid "" -"Then you may wish to get rid of the Facebook bridge. To do so, send a " -"`clean-rooms` command to the management room with the old bridge bot " -"(`@facebookbot:example.com`). It gives you a list of portals and groups " -"of portals you may purge. Proceed with sending commands like `clean " -"recommended`, etc." +msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 -msgid "" -"Then, consider disabling the old bridge in your configuration, so it " -"won't recreate the portals when you receive new messages." +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 -msgid "" -"**Note**: the user ID of the new bridge bot is " -"`@messengerbot:example.com`, not `@facebookbot:example.com`. After " -"disabling the old bridge, its bot user will stop responding to a command." +msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 @@ -96,18 +66,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 @@ -115,15 +78,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 -msgid "" -"Before proceeding to [re-running the playbook](./installing.md), you may " -"wish to adjust the configuration further. See below." +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 @@ -131,9 +90,7 @@ msgid "Bridge mode" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 -msgid "" -"As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) " -"bridge supports multiple modes of operation." +msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 @@ -145,36 +102,19 @@ msgid "(`facebook`) Facebook via `facebook.com`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44 -msgid "" -"(`facebook-tor`) Facebook via " -"`facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` " -"([Tor](https://www.torproject.org/)) - does not currently proxy media " -"downloads" +msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 -msgid "" -"(default) (`messenger`) Messenger via `messenger.com` - usable even " -"without a Facebook account" +msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 -msgid "" -"You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode`" -" variable. The playbook defaults to the `messenger` mode, because it's " -"most universal (every Facebook user has a Messenger account, but the " -"opposite is not true)." +msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 -msgid "" -"Note that switching the mode (especially between `facebook*` and " -"`messenger`) will intentionally make the bridge use another database " -"(`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to " -"isolate the 2 instances. Switching between Tor and non-Tor may be " -"possible without dataloss, but your mileage may vary. Before switching to" -" a new mode, you may wish to de-configure the old one (send `help` to the" -" bridge bot and unbridge your portals, etc.)." +msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 @@ -202,37 +142,23 @@ msgid "`admin` - Use and administer the bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 -msgid "" -"The permissions are following the sequence: nothing < `relay` < `user` < " -"`admin`." +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 -msgid "" -"The default permissions are set via " -"`matrix_mautrix_meta_messenger_bridge_permissions_default` and are " -"somewhat like this:" +msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 -msgid "" -"If you don't define the `matrix_admin` in your configuration (e.g. " -"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 -msgid "" -"You may redefine " -"`matrix_mautrix_meta_messenger_bridge_permissions_default` any way you " -"see fit, or add extra permissions using " -"`matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" +msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" -"messenger/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83 @@ -240,9 +166,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 @@ -250,24 +174,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100 @@ -275,26 +190,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102 -msgid "" -"To use the bridge, you need to start a chat with " -"`@messengerbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain). Note that the user ID of the bridge's bot is not " -"`@facebookbot:example.com`." +msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104 -msgid "" -"You then need to send a `login` command and follow the bridge bot's " -"instructions." +msgid "You then need to send a `login` command and follow the bridge bot's instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106 -msgid "" -"Given that the bot is configured in `messenger` [bridge mode](#bridge-" -"mode) by default, you will need to log in to " -"[messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain " -"the cookies from there as per [the bridge's authentication " -"instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." +msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108 @@ -302,10 +206,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112 @@ -317,17 +218,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120 @@ -335,27 +230,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128 -msgid "" -"make sure you don't log out the session for which you obtained an access " -"token some time in the future, as that would break the Double Puppeting " -"feature" +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po index 5998fd5cd..3767bf9d3 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 @@ -26,23 +26,15 @@ msgid "Setting up Mautrix Signal bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"signal](https://github.com/mautrix/signal) for you." +msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/signal/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 -msgid "" -"**Note**: This revamped version of the [mautrix-signal (legacy" -")](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU " -"usage of your homeserver." +msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 @@ -54,18 +46,11 @@ msgid "Prepare Postgres database on external Postgres server" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 -msgid "" -"If you're running with the Postgres database server integrated by the " -"playbook (which is the default), you don't need to do anything special " -"and can easily proceed with installing." +msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 -msgid "" -"However, if you're [using an external Postgres server](configuring-" -"playbook-external-postgres.md), you'd need to manually prepare a Postgres" -" database for this bridge and adjust the variables related to that " -"(`matrix_mautrix_signal_database_*`)." +msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 @@ -73,18 +58,11 @@ msgid "Enable Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 @@ -92,15 +70,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 @@ -124,9 +98,7 @@ msgid "admin - Use and administer the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 -msgid "" -"The permissions are following the sequence: nothing < relay < user < " -"admin." +msgid "The permissions are following the sequence: nothing < relay < user < admin." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43 @@ -134,29 +106,19 @@ msgid "The default permissions are set as follows:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 -msgid "" -"If you want to augment the preset permissions, you might want to set the " -"additional permissions with the following settings in your `vars.yml` " -"file:" +msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 -msgid "" -"This will add the admin permission to the specific user, while keeping " -"the default permissions." +msgid "This will add the admin permission to the specific user, while keeping the default permissions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 -msgid "" -"In case you want to replace the default permissions settings " -"**completely**, populate the following item within your `vars.yml` file:" +msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"signal/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 @@ -164,9 +126,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81 @@ -174,24 +134,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:87 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89 @@ -199,9 +150,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91 -msgid "" -"To use the bridge, you need to start a chat with `@signalbot:example.com`" -" (where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93 @@ -209,10 +158,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97 @@ -224,17 +170,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105 @@ -242,26 +182,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113 -msgid "" -"make sure you don't log out the `Mautrix-Signal` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po index 015f60413..95912f8f4 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 @@ -26,48 +26,27 @@ msgid "Setting up Mautrix Slack bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 -msgid "" -"**Note**: bridging to [Slack](https://slack.com/) can also happen via the" -" [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4 -msgid "" -"For using as a Bot we recommend the [Appservice Slack](configuring-" -"playbook-bridge-appservice-slack.md), because it supports plumbing. Note " -"that it is not available for new installation unless you have already " -"created a classic Slack application, because the creation of classic " -"Slack applications, which this bridge makes use of, has been " -"discontinued." +msgid "For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 -msgid "" -"For personal use with a slack account we recommend the `mautrix-slack` " -"bridge (the one being discussed here), because it is the most fully-" -"featured and stable of the 3 Slack bridges supported by the playbook." +msgid "For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7 -msgid "" -"The playbook can install and configure [mautrix-" -"slack](https://github.com/mautrix/slack) for you." +msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn" -" what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 -msgid "" -"See the [features and " -"roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more " -"information." +msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 @@ -75,19 +54,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 -msgid "" -"For using this bridge, you would need to authenticate by **providing your" -" username and password** (legacy) or by using a **token login**. See more" -" information in the " -"[docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." +msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 -msgid "" -"Note that neither of these methods are officially supported by Slack. " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) uses a Slack bot account which is the only officially supported" -" method for bridging a Slack channel." +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 @@ -95,18 +66,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 @@ -114,16 +78,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:33 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 @@ -131,9 +90,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 -msgid "" -"There are some additional options you may wish to configure with the " -"bridge." +msgid "There are some additional options you may wish to configure with the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39 @@ -141,17 +98,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41 -msgid "" -"`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some " -"variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 -msgid "" -"`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for " -"the bridge's default configuration. You can override settings (even those" -" that don't have dedicated playbook variables) using the " -"`matrix_mautrix_slack_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_slack_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 @@ -159,9 +110,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 @@ -169,24 +118,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 @@ -194,36 +134,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 -msgid "" -"Start a chat with `@slackbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:64 -msgid "" -"If you would like to login to Slack using a token, send the `login-token`" -" command, otherwise, send the `login-password` command. Read " -"[here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how " -"to retrieve your token and cookie token." +msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 -msgid "" -"The bot should respond with \"Successfully logged into for team " -"\"" +msgid "The bot should respond with \"Successfully logged into for team \"" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 -msgid "" -"Now that you're logged in, you can send a `help` command to the bot " -"again, to see additional commands you have access to." +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 -msgid "" -"Slack channels should automatically begin bridging if you authenticated " -"using a token. Otherwise, you must wait to receive a message in the " -"channel if you used password authentication." +msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 @@ -231,10 +158,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 @@ -246,17 +170,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81 @@ -264,26 +182,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89 -msgid "" -"make sure you don't log out the `Mautrix-Slack` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po index def8d3ed5..fcdaf40dc 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 @@ -26,16 +26,11 @@ msgid "Setting up Mautrix Telegram bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"telegram](https://github.com/mautrix/telegram) for you." +msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/telegram/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 @@ -43,19 +38,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 @@ -63,11 +50,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 -msgid "" -"You'll need to obtain API keys from " -"[https://my.telegram.org/apps](https://my.telegram.org/apps) and then add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 @@ -75,9 +58,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 @@ -85,24 +66,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40 @@ -110,19 +82,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 -msgid "" -"To use the bridge, you need to start a chat with " -"`@telegrambot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44 -msgid "" -"If you want to use the relay-bot feature ([relay bot " -"documentation](https://docs.mau.fi/bridges/python/telegram/relay-" -"bot.html)), which allows anonymous user to chat with telegram users, add " -"the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 @@ -130,17 +94,11 @@ msgid "You might also want to give permissions to administrate the bot:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63 -msgid "" -"More details about permissions in this example: " -"https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-" -"config.yaml#L410" +msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65 -msgid "" -"If you like to exclude all groups from syncing and use the Telgeram-" -"Bridge only for direct chats, you can add the following additional " -"playbook configuration:" +msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71 @@ -148,10 +106,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75 @@ -159,32 +114,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 @@ -192,32 +134,21 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 -msgid "" -"**Note**: This method for enabling Double Puppeting can be configured " -"only after you've already set up bridging." +msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 -msgid "" -"send `login-matrix` to the bot and follow instructions about how to send " -"the access token to it" +msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 -msgid "" -"make sure you don't log out the `Mautrix-Telegram` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po index 76826e601..e16a0a587 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 @@ -26,23 +26,15 @@ msgid "Setting up Mautrix Twitter bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 -msgid "" -"**Note**: bridging to [Twitter](https://twitter.com/) can also happen via" -" the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-" -"twitter.md) bridge supported by the playbook." +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"twitter](https://github.com/mautrix/twitter) for you." +msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/twitter/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 @@ -54,18 +46,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 @@ -73,9 +58,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 @@ -83,9 +66,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 @@ -93,24 +74,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 @@ -118,22 +90,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44 -msgid "" -"You then need to start a chat with `@twitterbot:example.com` (where " -"`example.com` is your base domain, not the `matrix.` domain)." +msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 -msgid "" -"Send login-cookie to start the login. The bot should respond with " -"instructions on how to proceed." +msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 -msgid "" -"You can learn more here about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 @@ -141,10 +106,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 @@ -156,17 +118,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 @@ -174,89 +130,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69 -msgid "" -"make sure you don't log out the `Mautrix-Slack` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/mautrix/twitter) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ msgstr "" - -#~ 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 "" - -#~ msgid "" -#~ "Method 1: automatically, by enabling " -#~ "Appservice Double Puppet or Shared " -#~ "Secret Auth" -#~ msgstr "" - -#~ msgid "" -#~ "The bridge automatically performs Double " -#~ "Puppeting if [Appservice Double Puppet" -#~ "](configuring-playbook-appservice-double-" -#~ "puppet.md) or [Shared Secret Auth" -#~ "](configuring-playbook-shared-secret-auth.md) " -#~ "service is configured and enabled on " -#~ "the server for this playbook." -#~ msgstr "" - -#~ msgid "" -#~ "Enabling [Appservice Double Puppet](configuring-" -#~ "playbook-appservice-double-puppet.md) is " -#~ "the recommended way of setting up " -#~ "Double Puppeting, as it's easier to " -#~ "accomplish, works for all your users " -#~ "automatically, and has less of a " -#~ "chance of breaking in the future." -#~ msgstr "" - -#~ msgid "" -#~ "Enabling double puppeting by enabling " -#~ "the [Shared Secret Auth](configuring-" -#~ "playbook-shared-secret-auth.md) service " -#~ "works at the time of writing, but" -#~ " is deprecated and will stop working" -#~ " in the future." -#~ msgstr "" - -#~ msgid "" -#~ "This method is currently not available" -#~ " for the Mautrix-Twitter bridge, but" -#~ " is on the " -#~ "[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md)" -#~ " under Misc/Manual login with `login-" -#~ "matrix`" -#~ 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 90e8d06df..f38bbc6b1 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 @@ -26,16 +26,11 @@ msgid "Setting up Mautrix Whatsapp bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"whatsapp](https://github.com/mautrix/whatsapp) for you." +msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 @@ -43,19 +38,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 @@ -63,34 +50,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 -msgid "" -"Whatsapp multidevice beta is required, now it is enough if Whatsapp is " -"connected to the Internet every 2 weeks." +msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23 -msgid "" -"The relay bot functionality is off by default. If you would like to " -"enable the relay bot, add the following to your `vars.yml` file:" +msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 -msgid "" -"By default, only admins are allowed to set themselves as relay users. To " -"allow anyone on your homeserver to set themselves as relay users add this" -" to your `vars.yml` file:" +msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 -msgid "" -"If you want to activate the relay bot in a room, send `!wa set-relay`. To" -" deactivate, send `!wa unset-relay`." +msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37 @@ -98,9 +74,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 @@ -108,24 +82,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 @@ -133,10 +98,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 -msgid "" -"To use the bridge, you need to start a chat with " -"`@whatsappbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 @@ -144,10 +106,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62 @@ -155,32 +114,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72 @@ -188,26 +134,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80 -msgid "" -"make sure you don't log out the `Mautrix-Whatsapp` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po index 91e79ff01..840972572 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 @@ -22,22 +22,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1 -msgid "" -"Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage " -"(optional)" +msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"wsproxy](https://github.com/mautrix/wsproxy) for you." +msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/wsproxy/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 @@ -45,16 +38,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 -msgid "" -"Note that the tokens must match what is compiled into the [mautrix-" -"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" -" or Android device." +msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 @@ -62,23 +50,15 @@ msgid "Adjusting the wsproxy URL" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 -msgid "" -"By default, this playbook installs wsproxy on the `wsproxy.` subdomain " -"(`wsproxy.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27 -msgid "" -"By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can " -"easily make the service available at a **different hostname** than the " -"default one." +msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36 @@ -86,15 +66,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the wsproxy domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40 -msgid "" -"By default, you will need to create a CNAME record for `wsproxy`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 @@ -102,10 +78,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:51 @@ -113,24 +86,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:55 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:57 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 @@ -138,16 +102,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 -msgid "" -"Follow the [matrix-imessage " -"documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for " -"running `android-sms` and/or `matrix-imessage` on your device(s)." +msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/mautrix/wsproxy#readme) to" -#~ " learn what it does and why it" -#~ " might be useful to you." -#~ 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 f71b36d15..63c31ff55 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 @@ -26,38 +26,23 @@ msgid "Setting up MX Puppet Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [matrix-appservice-discord](configuring-playbook-bridge-" -"appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-" -"mautrix-discord.md) bridges supported by the playbook." +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." +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." +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." +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." +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 @@ -65,10 +50,7 @@ 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:" +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 @@ -76,9 +58,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +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 @@ -86,24 +66,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -111,18 +82,11 @@ 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)." +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." +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 @@ -130,18 +94,9 @@ 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." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 eb1a89f86..61d002626 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 @@ -26,17 +26,11 @@ msgid "Setting up MX Puppet GroupMe bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for " -"you." +msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 -msgid "" -"See the project's [documentation](https://gitlab.com/xangelix-pub/matrix" -"/mx-puppet-groupme/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 @@ -44,10 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 -msgid "" -"To enable the [GroupMe](https://groupme.com/) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 @@ -55,9 +46,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 @@ -65,24 +54,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 @@ -90,10 +70,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 -msgid "" -"To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` " -"with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is" -" your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 @@ -101,31 +78,17 @@ msgid "One authentication method is available." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 -msgid "" -"To link your GroupMe account, go to " -"[dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access" -" Token\" from the top menu. Copy the token and message the bridge with:" +msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 -msgid "" -"Once logged in, send `listrooms` to the bot user to list the available " -"rooms." +msgid "Once logged in, send `listrooms` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 66a26bda0..7174fc472 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 @@ -26,9 +26,7 @@ msgid "Setting up MX Puppet Instagram bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." +msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 @@ -40,10 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 -msgid "" -"To enable the [Instagram](https://www.instagram.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +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 @@ -51,9 +46,7 @@ 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:" +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 @@ -61,24 +54,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -86,22 +70,15 @@ 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)." +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." +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." +msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40 @@ -109,9 +86,7 @@ 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)" +msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43 @@ -119,20 +94,13 @@ 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)" +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." +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 "" -"The `help` command shows which commands are available, though at the time" -" of writing, not every command is fully implemented." +msgid "The `help` command shows which commands are available, though 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 eb13e93f5..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 @@ -26,17 +26,9 @@ msgid "Setting up MX Puppet Skype bridging (optional, removed)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 -msgid "" -"The playbook used to be able to install and configure [mx-puppet-" -"skype](https://github.com/Sorunome/mx-puppet-skype), but no longer " -"includes this component, because it has been broken and unmaintained for " -"a long time." +msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 -msgid "" -"Bridging to [Skype](https://www.skype.com/) can also happen via the [go-" -"skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge " -"supported by the playbook." +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 344a58cfc..4ca40c767 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 @@ -22,28 +22,15 @@ msgid "Setting up MX Puppet Slack bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 -msgid "" -"**Note**: bridging to [Slack](https://slack.com) can also happen via the " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-" -"slack.md) bridges supported by the playbook. Note that `matrix-" -"appservice-slack` is not available for new installation unless you have " -"already created a classic Slack application, because the creation of " -"classic Slack applications, which this bridge makes use of, has been " -"discontinued." +msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 -msgid "" -"The playbook can install and configure [mx-puppet-" -"slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." +msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 -msgid "" -"See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-" -"puppet-slack/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 @@ -51,10 +38,7 @@ 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`." +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 @@ -62,10 +46,7 @@ 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:" +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 @@ -73,9 +54,7 @@ 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:" +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 @@ -83,24 +62,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -108,18 +78,11 @@ 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)." +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." +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 @@ -127,18 +90,9 @@ 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." +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 "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 f39f3bcfd..fbad3d73e 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 @@ -26,16 +26,11 @@ msgid "Setting up MX Puppet Steam bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"steam](https://github.com/icewind1991/mx-puppet-steam) for you." +msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 -msgid "" -"See the project's [documentation](https://github.com/icewind1991/mx-" -"puppet-steam/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 @@ -43,10 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 -msgid "" -"To enable the [Steam](https://steampowered.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 @@ -54,9 +46,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 @@ -64,24 +54,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 @@ -89,17 +70,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 -msgid "" -"To use the bridge, you need to start a chat with `Steam Puppet Bridge` " -"with the handle `@_steampuppet_bot:example.com` (where `example.com` is " -"your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 -msgid "" -"Three authentication methods are available, Legacy Token, OAuth and xoxc " -"token. See mx-puppet-steam [documentation](https://github.com/icewind1991" -"/mx-puppet-steam) for more information about how to configure the bridge." +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 @@ -107,18 +82,9 @@ msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 8b1dec811..e881607c3 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 @@ -26,23 +26,15 @@ 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." +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." +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." +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 @@ -50,9 +42,7 @@ 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)." +msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 @@ -60,10 +50,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 -msgid "" -"To enable the [Twitter](https://twitter.com) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +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 @@ -71,9 +58,7 @@ 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:" +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 @@ -81,24 +66,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -106,10 +82,7 @@ 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)." +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 @@ -121,18 +94,9 @@ msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index d35e570a5..17eb742c0 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -22,29 +22,19 @@ msgid "Setting up Postmoogle email bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:3 -msgid "" -"**Note**: email bridging can also happen via the [email2matrix" -"](configuring-playbook-email2matrix.md) bridge supported by the playbook." +msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:5 -msgid "" -"The playbook can install and configure " -"[Postmoogle](https://github.com/etkecc/postmoogle) for you." +msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:7 -msgid "" -"Postmoogle is a bridge you can use to have its bot user forward emails to" -" Matrix rooms. It runs an SMTP email server and allows you to assign " -"mailbox addresses to the rooms." +msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 -msgid "" -"See the project's " -"[documentation](https://github.com/etkecc/postmoogle/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 @@ -52,9 +42,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:13 -msgid "" -"Open the following ports on your server to be able to receive incoming " -"emails:" +msgid "Open the following ports on your server to be able to receive incoming emails:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:15 @@ -66,18 +54,11 @@ msgid "`587/tcp`: Submission (TLS-encrypted SMTP)" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:18 -msgid "" -"If you don't open these ports, you will still be able to send emails, but" -" not receive any." +msgid "If you don't open these ports, you will still be able to send emails, but not receive any." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:20 -msgid "" -"These port numbers are configurable via the " -"`matrix_postmoogle_smtp_host_bind_port` and " -"`matrix_postmoogle_submission_host_bind_port` variables, but other email " -"servers will try to deliver on these default (standard) ports, so " -"changing them is of little use." +msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:22 @@ -85,9 +66,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:24 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:45 @@ -95,10 +74,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:47 -msgid "" -"You will also need to add several DNS records so that Postmoogle can send" -" emails. See [Configuring DNS](configuring-dns.md) for details about DNS " -"changes." +msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:49 @@ -106,9 +82,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:51 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:58 @@ -116,34 +90,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:60 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create a user account of the bridge's bot." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:62 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:64 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:66 -msgid "" -"If you change the bridge's bot password (`matrix_postmoogle_password` in " -"your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_postmoogle_password` to let the bot know its new password." +msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:68 @@ -151,28 +110,19 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:70 -msgid "" -"To use the bridge, invite the `@postmoogle:example.com` bot user into a " -"room you want to use as a mailbox." +msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:72 -msgid "" -"Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with " -"the email address `NAME@matrix.example.com`. Emails sent to that email " -"address will be forwarded to the room." +msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 -msgid "" -"Send `!pm help` to the room to see the bridge's help menu for additional " -"commands." +msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/postmoogle)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:78 @@ -180,23 +130,9 @@ msgid "Debug/Logs" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:80 -msgid "" -"As with all other services, you can find their logs in [systemd-" -"journald](https://www.freedesktop.org/software/systemd/man/systemd-" -"journald.service.html) by running something like `journalctl -fu matrix-" -"postmoogle`" +msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:82 -msgid "" -"The default logging level for this bridge is `INFO`, but you can increase" -" it to `DEBUG` with the following additional configuration:" +msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/etkecc/postmoogle) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 24e25c999..8654f62a0 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 @@ -26,17 +26,11 @@ msgid "Setting up WeChat bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:3 -msgid "" -"The playbook can install and configure the [matrix-" -"wechat](https://github.com/duo/matrix-wechat) bridge for you (for " -"bridging to the [WeChat](https://www.wechat.com/) network)." +msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:5 -msgid "" -"See the project's [documentation](https://github.com/duo/matrix-" -"wechat/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:7 @@ -44,9 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:15 @@ -54,9 +46,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:24 @@ -64,24 +54,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:26 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:32 @@ -89,18 +70,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:34 -msgid "" -"Once the bridge is installed, start a chat with `@wechatbot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:36 msgid "Send `help` to the bot to see the available commands." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 db70bbfd9..79c9dddee 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 @@ -26,41 +26,27 @@ msgid "Setting up Cactus Comments (optional)" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:3 -msgid "" -"The playbook can install and configure the [Cactus " -"Comments](https://cactus.chat) system for you." +msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:5 -msgid "" -"Cactus Comments is a **federated comment system** built on Matrix. It " -"respects your privacy, and puts you in control." +msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:7 -msgid "" -"See the project's [documentation](https://cactus.chat/docs/getting-" -"started/introduction/) to learn what it does and why it might be useful " -"to you." +msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:9 -msgid "" -"The playbook contains 2 roles for configuring different pieces of the " -"Cactus Comments system:" +msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:11 -msgid "" -"`matrix-cactus-comments` - the backend appservice integrating with the " -"Matrix homeserver" +msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:13 -msgid "" -"`matrix-cactus-comments-client` - a static website server serving the " -"[cactus-client](https://cactus.chat/docs/client/introduction/) static " -"assets (`cactus.js` and `styles.css`)" +msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:15 @@ -72,9 +58,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:19 -msgid "" -"To enable Cactus Comments, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:41 @@ -82,26 +66,15 @@ msgid "Adjusting the Cactus Comments' client URL" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:43 -msgid "" -"By default, this playbook installs Cactus Comments' client on the " -"`matrix.` subdomain, at the `/cactus-comments` path " -"(https://matrix.example.com/cactus-comments). This makes it easy to " -"install it, because it **doesn't require additional DNS records to be set" -" up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:45 -msgid "" -"By tweaking the `matrix_cactus_comments_client_hostname` and " -"`matrix_cactus_comments_client_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:47 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:56 @@ -109,10 +82,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:58 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Cactus Comments' client domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:60 @@ -120,9 +90,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:62 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:64 @@ -130,10 +98,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:66 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:73 @@ -141,24 +106,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:75 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:77 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:79 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:81 @@ -166,22 +122,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:83 -msgid "" -"Upon starting Cactus Comments, a `bot.cactusbot` user account is created " -"automatically." +msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:85 -msgid "" -"To get started, send a `help` message to the `@bot.cactusbot:example.com`" -" bot to confirm it's working." +msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:87 -msgid "" -"Then, register a site by sending `register ` (where " -"`` is a unique identifier you choose. It does not have to " -"match your domain). You will then be invited into a moderation room." +msgid "Then, register a site by sending `register ` (where `` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:89 @@ -193,23 +142,15 @@ msgid "Embed Cactus Comments" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:93 -msgid "" -"The official [documentation](https://cactus.chat/docs/getting-started" -"/quick-start/) provides a useful guide to embed Cactus Comments on your " -"website." +msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:95 -msgid "" -"After including the JavaScript and CSS asset files, insert a `
` " -"where you'd like to display the comment section:" +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:101 -msgid "" -"Then, you need to initialize the comment section. Make sure to replace " -"`example.com` with your base domain and `` with the one " -"that has been registered above:" +msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `` with the one that has been registered above:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:115 @@ -217,22 +158,13 @@ msgid "Adjust the domain name for self-hosting" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:117 -msgid "" -"To have the assets served from your homeserver (not from `cactus.chat`), " -"you need to adjust the domain name on the official documentation." +msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:119 -msgid "" -"Make sure to replace `example.com` with your base domain before you " -"include the following lines, instead of the one provided by the official " -"documentation:" +msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:126 -msgid "" -"**Note**: if the `matrix_cactus_comments_client_hostname` and " -"`matrix_cactus_comments_client_path_prefix` variables are tweaked, you " -"would need to adjust the URLs of the assets accordingly." +msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po index 04d679cb1..b6f8f2750 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 @@ -26,30 +26,19 @@ msgid "Setting up Cinny (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:3 -msgid "" -"This playbook can install the [Cinny](https://github.com/ajbura/cinny) " -"Matrix web client for you." +msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:5 -msgid "" -"Cinny is a web client focusing primarily on simple, elegant and secure " -"interface. It can be installed alongside or instead of [Element Web" -"](./configuring-playbook-client-element-web.md)." +msgid "Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md)." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:7 -msgid "" -"💡 **Note**: the latest version of Cinny is also available on the web, " -"hosted by 3rd parties. If you trust giving your credentials to the " -"following 3rd party Single Page Applications, you can consider using it " -"from there and avoiding the (small) overhead of self-hosting:" +msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:9 -msgid "" -"[app.cinny.in](https://app.cinny.in), hosted by the " -"[Cinny](https://cinny.in/) developers" +msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:11 @@ -57,9 +46,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:13 -msgid "" -"To enable Cinny, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:19 @@ -67,32 +54,19 @@ msgid "Adjusting the Cinny URL" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:21 -msgid "" -"By default, this playbook installs Cinny on the `cinny.` subdomain " -"(`cinny.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:23 -msgid "" -"By tweaking the `matrix_client_cinny_hostname` variable, you can easily " -"make the service available at a **different hostname** than the default " -"one." +msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:25 -msgid "" -"While a `matrix_client_cinny_path_prefix` variable exists for tweaking " -"the path-prefix, it's [not supported " -"anymore](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3701), because Cinny requires an application rebuild (with " -"a tweaked build config) to be functional under a custom path." +msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:27 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:34 @@ -100,21 +74,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:36 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the Cinny domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:38 -msgid "" -"By default, you will need to create a CNAME record for `cinny`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:40 -msgid "" -"If you've adjusted `matrix_client_cinny_hostname`, you will need to " -"adjust your DNS configuration accordingly." +msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:42 @@ -122,25 +90,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:44 -msgid "" -"After configuring the playbook and [adjusting your DNS records" -"](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:51 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:53 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po index cbcdfcec2..ab7f413bf 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 @@ -26,25 +26,15 @@ msgid "Configuring Element Web (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:3 -msgid "" -"By default, this playbook installs the [Element Web](https://github.com" -"/element-hq/element-web) Matrix client for you. If that's okay, you can " -"skip this document." +msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:5 -msgid "" -"💡 **Note**: the latest version of Element Web is also available on the " -"web, hosted by 3rd parties. If you trust giving your credentials to the " -"following 3rd party Single Page Applications, you can consider using it " -"from there and avoiding the (small) overhead of self-hosting (by " -"[disabling Element Web](#disabling-element-web)):" +msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:7 -msgid "" -"[app.element.io](https://app.element.io/), hosted by " -"[Element](https://element.io/)" +msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:8 @@ -56,11 +46,7 @@ msgid "Disabling Element Web" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:12 -msgid "" -"If you'd like for the playbook to not install Element Web (or to " -"uninstall it if it was previously installed), add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:18 @@ -68,64 +54,31 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:20 -msgid "" -"The playbook provides some customization variables you could use to " -"change Element Web's settings." +msgid "The playbook provides some customization variables you could use to change Element Web's settings." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:22 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/element/config.json` file (on the server). This file is " -"generated from the [`roles/custom/matrix-client-" -"element/templates/config.json.j2`](../roles/custom/matrix-client-" -"element/templates/config.json.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:24 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:26 -msgid "" -"Alternatively, **if there is no pre-defined variable** for an Element Web" -" setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:28 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Element Web's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:30 -msgid "" -"or, you can **extend and override the default configuration** " -"([`config.json.j2`](../roles/custom/matrix-client-" -"element/templates/config.json.j2)) by making use of the " -"`matrix_client_element_configuration_extension_json_` variable. You can " -"find information about this in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:32 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_client_element_configuration_default` (or " -"`matrix_client_element_configuration`). You can find information about " -"this in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:34 @@ -133,31 +86,19 @@ msgid "Themes" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:36 -msgid "" -"To change the look of Element Web, you can define your own themes " -"manually by using the " -"`matrix_client_element_setting_defaults_custom_themes` setting." +msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:38 -msgid "" -"Or better yet, you can automatically pull it all themes provided by the " -"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" -"themes) project by simply flipping a flag " -"(`matrix_client_element_themes_enabled: true`)." +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:40 -msgid "" -"If you make your own theme, we encourage you to submit it to the " -"**aaronraimist/element-themes** project, so that the whole community " -"could easily enjoy it." +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:42 -msgid "" -"Note that for a custom theme to work well, all Element Web instances that" -" you use must have the same theme installed." +msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:44 @@ -165,24 +106,15 @@ msgid "Adjusting the Element Web URL" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:46 -msgid "" -"By default, this playbook installs Element Web on the `element.` " -"subdomain (`element.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:48 -msgid "" -"By tweaking the `matrix_client_element_hostname` and " -"`matrix_client_element_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:50 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:61 @@ -190,21 +122,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:63 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Element Web domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:65 -msgid "" -"By default, you will need to create a CNAME record for `element`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:67 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:69 @@ -212,25 +138,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:71 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:78 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:80 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po index bfa4ef79b..ad0c5b439 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 @@ -26,15 +26,11 @@ msgid "Setting up Hydrogen (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:3 -msgid "" -"This playbook can install the [Hydrogen](https://github.com/element-hq" -"/hydrogen-web) Matrix web client for you." +msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:5 -msgid "" -"Hydrogen is a lightweight web client that supports mobile and legacy web " -"browsers. It can be installed alongside or instead of Element Web." +msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:7 @@ -42,9 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:9 -msgid "" -"To enable Hydrogen, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:15 @@ -52,24 +46,15 @@ msgid "Adjusting the Hydrogen URL" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:17 -msgid "" -"By default, this playbook installs Hydrogen on the `hydrogen.` subdomain " -"(`hydrogen.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:19 -msgid "" -"By tweaking the `matrix_client_hydrogen_hostname` and " -"`matrix_client_hydrogen_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:21 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:32 @@ -77,21 +62,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:34 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Hydrogen domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:36 -msgid "" -"By default, you will need to create a CNAME record for `hydrogen`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:38 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:40 @@ -99,25 +78,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:42 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:49 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:51 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po index 9fa8372e8..dfe68ae18 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 @@ -26,31 +26,19 @@ msgid "Setting up SchildiChat Web (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:3 -msgid "" -"This playbook can install the [SchildiChat " -"Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client " -"for you." +msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:5 -msgid "" -"SchildiChat Web is a feature-rich messenger for Matrix based on Element " -"Web with some extras and tweaks. It can be installed alongside or instead" -" of Element Web." +msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:7 -msgid "" -"💡 **Note**: the latest version of SchildiChat Web is also available on " -"the web, hosted by 3rd parties. If you trust giving your credentials to " -"the following 3rd party Single Page Application, you can consider using " -"it from there:" +msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:9 -msgid "" -"[app.schildi.chat](https://app.schildi.chat/), hosted by the " -"[SchildiChat](https://schildi.chat/) developers" +msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:11 @@ -58,70 +46,35 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:13 -msgid "" -"To enable SchildiChat Web, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:19 -msgid "" -"The playbook provides some customization variables you could use to " -"change SchildiChat Web's settings." +msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:21 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml) and they ultimately end up in the " -"generated `/matrix/schildichat/config.json` file (on the server). This " -"file is generated from the [`roles/custom/matrix-client-" -"schildichat/templates/config.json.j2`](../roles/custom/matrix-client-" -"schildichat/templates/config.json.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:23 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:25 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a SchildiChat " -"Web setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:27 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of SchildiChat Web's various" -" settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:29 -msgid "" -"or, you can **extend and override the default configuration** " -"([`config.json.j2`](../roles/custom/matrix-client-" -"schildichat/templates/config.json.j2)) by making use of the " -"`matrix_client_schildichat_configuration_extension_json_` variable. You " -"can find information about this in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:31 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_client_schildichat_configuration_default` (or " -"`matrix_client_schildichat_configuration`). You can find information " -"about this in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:33 @@ -129,31 +82,19 @@ msgid "Themes" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:35 -msgid "" -"To change the look of SchildiChat Web, you can define your own themes " -"manually by using the " -"`matrix_client_schildichat_setting_defaults_custom_themes` setting." +msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:37 -msgid "" -"Or better yet, you can automatically pull it all themes provided by the " -"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" -"themes) project by simply flipping a flag " -"(`matrix_client_schildichat_themes_enabled: true`)." +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:39 -msgid "" -"If you make your own theme, we encourage you to submit it to the " -"**aaronraimist/element-themes** project, so that the whole community " -"could easily enjoy it." +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:41 -msgid "" -"Note that for a custom theme to work well, all SchildiChat Web instances " -"that you use must have the same theme installed." +msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:43 @@ -161,24 +102,15 @@ msgid "Adjusting the SchildiChat Web URL" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:45 -msgid "" -"By default, this playbook installs SchildiChat Web on the `schildichat.` " -"subdomain (`schildichat.example.com`) and requires you to [adjust your " -"DNS records](#adjusting-dns-records)." +msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:47 -msgid "" -"By tweaking the `matrix_client_schildichat_hostname` and " -"`matrix_client_schildichat_path_prefix` variables, you can easily make " -"the service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:49 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:60 @@ -186,21 +118,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:62 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the SchildiChat Web domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:64 -msgid "" -"By default, you will need to create a CNAME record for `schildichat`. See" -" [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:66 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:68 @@ -208,25 +134,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:70 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:77 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:79 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po index 9f7d19965..5142b6b0c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -26,10 +26,7 @@ msgid "Configuring Conduit (optional)" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, but you can also use " -"[Conduit](https://conduit.rs)." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:5 @@ -37,19 +34,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:7 -msgid "" -"**You can't switch an existing Matrix server's implementation** (e.g. " -"Synapse -> Conduit). Proceed below only if you're OK with losing data or " -"you're dealing with a server on a new domain name, which hasn't " -"participated in the Matrix federation yet." +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:9 -msgid "" -"**homeserver implementations other than Synapse may not be fully " -"functional**. The playbook may also not assist you in an optimal way " -"(like it does with Synapse). Make yourself familiar with the downsides " -"before proceeding" +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:11 @@ -57,9 +46,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:13 -msgid "" -"To use Conduit, you **generally** need to add the following configuration" -" to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:19 @@ -67,32 +54,19 @@ msgid "Creating the first user account" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:21 -msgid "" -"Since it is difficult to create the first user account on Conduit (see " -"[famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) " -"and " -"[famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354))" -" and it does not support [registering users](registering-users.md) (via " -"the command line or via the playbook) like Synapse and Dendrite do, we " -"recommend the following procedure:" +msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:23 -msgid "" -"Add `matrix_conduit_allow_registration: true` to your `vars.yml` the " -"first time around, temporarily" +msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:24 -msgid "" -"Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags" -"=setup-all,start` - see [Installing](installing.md))" +msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:25 -msgid "" -"Create your first user via Element Web or any other client which supports" -" creating users" +msgid "Create your first user via Element Web or any other client which supports creating users" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:26 @@ -100,15 +74,11 @@ msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml` msgstr "" #: ../../../docs/configuring-playbook-conduit.md:27 -msgid "" -"Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-conduit,start` would be enough this time)" +msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:28 -msgid "" -"You can now use your server safely. Additional users can be created by " -"messaging the internal Conduit bot" +msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:30 @@ -116,23 +86,13 @@ msgid "Configuring bridges / appservices" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:32 -msgid "" -"Automatic appservice setup is currently unsupported when using Conduit. " -"After setting up the service as usual you may notice that it is unable to" -" start." +msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:34 -msgid "" -"You will have to manually register appservices using the the [register-" -"appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md)" -" command." +msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:36 -msgid "" -"Find the `registration.yaml` in the `/matrix` directory, for example " -"`/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content " -"to Conduit:" +msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po index 519a7afa8..35c0c5383 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -26,10 +26,7 @@ msgid "Configuring Dendrite (optional)" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, but you can also use " -"[Dendrite](https://github.com/matrix-org/dendrite)." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:5 @@ -37,19 +34,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:7 -msgid "" -"**You can't switch an existing Matrix server's implementation** (e.g. " -"Synapse -> Dendrite). Proceed below only if you're OK with losing data or" -" you're dealing with a server on a new domain name, which hasn't " -"participated in the Matrix federation yet." +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:9 -msgid "" -"**homeserver implementations other than Synapse may not be fully " -"functional**. The playbook may also not assist you in an optimal way " -"(like it does with Synapse). Make yourself familiar with the downsides " -"before proceeding" +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:11 @@ -57,71 +46,35 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:13 -msgid "" -"To use Dendrite, you **generally** need to add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:19 -msgid "" -"The playbook provides lots of customization variables you could use to " -"change Dendrite's settings." +msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:21 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/dendrite/config/dendrite.yaml` file (on the server). This file " -"is generated from the [`roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:23 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:25 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a Dendrite " -"setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:27 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Dendrite's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:29 -msgid "" -"or, you can **extend and override the default configuration** " -"([`dendrite.yaml.j2`](../roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the " -"`matrix_dendrite_configuration_extension_yaml` variable. You can find " -"information about this in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:31 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_dendrite_configuration` (or " -"`matrix_dendrite_configuration_yaml`). You can find information about " -"this in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:33 @@ -129,24 +82,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:35 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:42 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:44 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po index ed7f463fa..a2dcc6505 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -26,34 +26,15 @@ msgid "Setting up Dimension integration manager (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:3 -msgid "" -"**[Dimension](https://dimension.t2bot.io) can only be installed after " -"Matrix services are installed and running.** If you're just installing " -"Matrix services for the first time, please continue with the " -"[Configuration](configuring-playbook.md) / [Installation](installing.md) " -"flow and come back here later." +msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:5 -msgid "" -"**Note**: Dimension is **[officially " -"unmaintained](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering" -" with installing it." +msgid "**Note**: 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:7 -msgid "" -"**Note**: This playbook now supports running " -"[Dimension](https://dimension.t2bot.io) in both a federated and " -"[unfederated](https://github.com/turt2live/matrix-" -"dimension/blob/master/docs/unfederated.md) environments. This is handled " -"automatically based on the value of " -"`matrix_homeserver_federation_enabled`. Enabling Dimension, means that " -"the `openid` API endpoints will be exposed on the Matrix Federation port " -"(usually `8448`), even if [federation](configuring-playbook-" -"federation.md) is disabled. It's something to be aware of, especially in " -"terms of firewall whitelisting (make sure port `8448` is accessible)." +msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:9 @@ -61,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:11 -msgid "" -"To enable Dimension, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:17 @@ -71,18 +50,11 @@ msgid "Define admin users" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:19 -msgid "" -"These users can modify the integrations this Dimension supports. Add this" -" to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:27 -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." +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:29 @@ -90,37 +62,23 @@ msgid "Access token" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:31 -msgid "" -"We recommend that you create a dedicated Matrix user for Dimension " -"(`dimension` is a good username). Follow our [Registering users" -"](registering-users.md) guide to learn how to register **a regular (non-" -"admin) user**." +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:33 -msgid "" -"You are required to specify an access token (belonging to this new user) " -"for Dimension to work. To get an access token for the Dimension user, you" -" can follow the documentation on [how to do obtain an access token" -"](obtaining-access-tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:35 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:37 -msgid "" -"Add access token to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:43 -msgid "" -"For more information on how to acquire an access token, visit " -"[https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." +msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:45 @@ -128,32 +86,19 @@ msgid "Adjusting the Dimension URL" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:47 -msgid "" -"By default, this playbook installs Dimension on the `dimension.` " -"subdomain (`dimension.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:49 -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." +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:51 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:62 -msgid "" -"**Note**: While there is a `matrix_dimension_path_prefix` variable for " -"changing the path where Dimension is served, overriding it is not " -"possible due to [this Dimension issue](https://github.com/turt2live" -"/matrix-dimension/issues/510). You must serve Dimension at a dedicated " -"subdomain." +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:64 @@ -161,15 +106,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:66 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Dimension domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:68 -msgid "" -"By default, you will need to create a CNAME record for `dimension`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:70 @@ -177,10 +118,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dimension.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:" +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:79 @@ -188,28 +126,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:81 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:83 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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:85 -msgid "" -"After Dimension has been installed you may need to log out and log back " -"in for it to pick up the new integration manager. Then you can access " -"integrations in Element Web by opening a room, clicking the Room info " -"button (`i`) button in the top right corner of the screen, and then " -"clicking Add widgets, bridges & bots." +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:87 @@ -217,23 +142,11 @@ msgid "Jitsi domain" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:89 -msgid "" -"By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as " -"the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video " -"conference widgets. For users running [a self-hosted Jitsi instance" -"](./configuring-playbook-jitsi.md), you will likely want the widget to " -"use your own Jitsi instance. Currently there is no way to configure this " -"via the playbook, see [this issue](https://github.com/turt2live/matrix-" -"dimension/issues/345) for details." +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:91 -msgid "" -"In the interim until the above limitation is resolved, an admin user " -"needs to configure the domain via the admin ui once dimension is running." -" In Element Web, go to *Manage Integrations* → *Settings* " -"→ *Widgets* → *Jitsi Conference Settings* and set " -"*Jitsi Domain* and *Jitsi Script URL* appropriately." +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:93 @@ -241,19 +154,9 @@ msgid "Additional features" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:95 -msgid "" -"To use a more custom configuration, you can define a " -"`matrix_dimension_configuration_extension_yaml` string variable and put " -"your configuration in it. To learn more about how to do this, refer to " -"the information about `matrix_dimension_configuration_extension_yaml` in " -"the [default variables file](../roles/custom/matrix-" -"dimension/defaults/main.yml) of the Dimension component." +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:97 -msgid "" -"You can find all configuration options on [GitHub page of Dimension " -"project](https://github.com/turt2live/matrix-" -"dimension/blob/master/config/default.yaml)." +msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po index 8a8ce45ce..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 @@ -26,18 +26,11 @@ msgid "Setting up Dynamic DNS (optional)" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:3 -msgid "" -"The playbook can configure Dynamic DNS with " -"[ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl " -"client used to update dynamic DNS entries for accounts on Dynamic DNS " -"Network Service Provider." +msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:5 -msgid "" -"Most cloud providers / ISPs will charge you extra for a static IP " -"address. If you're not hosting a highly reliable homeserver you can " -"workaround this via dynamic DNS." +msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:7 @@ -45,9 +38,7 @@ msgid "Prerequisite" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:9 -msgid "" -"You'll need to get a username and password from your DNS provider. Please" -" consult with the provider about how to retrieve them." +msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:11 @@ -55,9 +46,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:13 -msgid "" -"To enable dynamic DNS, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:26 @@ -65,25 +54,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:35 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:37 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:39 @@ -97,4 +76,3 @@ msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:43 msgid "https://matrix.org/docs/guides/free-small-matrix-server" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po index 3d8308b17..d6bc0411f 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po @@ -26,37 +26,23 @@ msgid "Adjusting email-sending settings (optional)" msgstr "" #: ../../../docs/configuring-playbook-email.md:3 -msgid "" -"By default, this playbook sets up an [Exim](https://www.exim.org/) email " -"server through which all Matrix services send emails." +msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails." msgstr "" #: ../../../docs/configuring-playbook-email.md:5 -msgid "" -"The email server would attempt to deliver emails directly to their final " -"destination. This may or may not work, depending on your domain " -"configuration (SPF settings, etc.)" +msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)" msgstr "" #: ../../../docs/configuring-playbook-email.md:7 -msgid "" -"By default, emails are sent from `matrix@matrix.example.com`, as " -"specified by the `exim_relay_sender_address` playbook variable." +msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable." msgstr "" #: ../../../docs/configuring-playbook-email.md:9 -msgid "" -"⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is" -" always blocked](https://cloud.google.com/compute/docs/tutorials/sending-" -"mail/), so sending email directly from your server is not possible. You " -"will need to [relay email through another SMTP server](#relaying-email-" -"through-another-smtp-server)." +msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)." msgstr "" #: ../../../docs/configuring-playbook-email.md:11 -msgid "" -"💡 To improve deliverability, we recommend [relaying email through another" -" SMTP server](#relaying-email-through-another-smtp-server) anyway." +msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway." msgstr "" #: ../../../docs/configuring-playbook-email.md:13 @@ -64,10 +50,7 @@ msgid "Firewall settings" msgstr "" #: ../../../docs/configuring-playbook-email.md:15 -msgid "" -"No matter whether you send email directly (the default) or you relay " -"email through another host (see how below), you'll probably need to allow" -" outgoing traffic for TCP ports 25/587 (depending on configuration)." +msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." msgstr "" #: ../../../docs/configuring-playbook-email.md:17 @@ -75,18 +58,11 @@ msgid "Relaying email through another SMTP server" msgstr "" #: ../../../docs/configuring-playbook-email.md:19 -msgid "" -"If you'd like to relay email through another SMTP server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email.md:31 -msgid "" -"**Note**: only the secure submission protocol (using `STARTTLS`, usually " -"on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port " -"`465`) **is not supported**." +msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**." msgstr "" #: ../../../docs/configuring-playbook-email.md:33 @@ -94,26 +70,15 @@ msgid "Configuations for sending emails using Sendgrid" msgstr "" #: ../../../docs/configuring-playbook-email.md:35 -msgid "" -"An easy and free SMTP service to set up is " -"[Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 " -"emails per day to be sent. In the settings below you can provide any " -"email for `exim_relay_sender_address`." +msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`." msgstr "" #: ../../../docs/configuring-playbook-email.md:37 -msgid "" -"The only other thing you need to change is the " -"`exim_relay_relay_auth_password`, which you can generate at " -"https://app.sendgrid.com/settings/api_keys. The API key password looks " -"something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-" -"6zkdwrPP8bOeuI`." +msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`." msgstr "" #: ../../../docs/configuring-playbook-email.md:39 -msgid "" -"Note that the `exim_relay_relay_auth_username` is literally the string " -"`apikey`, it's always the same for Sendgrid." +msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid." msgstr "" #: ../../../docs/configuring-playbook-email.md:51 @@ -121,8 +86,5 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-email.md:53 -msgid "" -"If you're having trouble with email not being delivered, it may be useful" -" to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." +msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index 18d078a8e..0bdcf7ed3 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -26,24 +26,15 @@ msgid "Setting up Email2Matrix (optional)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:3 -msgid "" -"**Note**: email bridging can also happen via the [Postmoogle" -"](configuring-playbook-bridge-postmoogle.md) bridge supported by the " -"playbook. Postmoogle is much more powerful and easier to use, so we " -"recommend that you use it, instead of Email2Matrix." +msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:5 -msgid "" -"The playbook can install and configure " -"[email2matrix](https://github.com/devture/email2matrix) for you." +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." +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 @@ -55,11 +46,7 @@ msgid "DNS configuration" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:13 -msgid "" -"It's not strictly necessary, but you may increase the chances that " -"incoming emails reach your server by adding an `MX` record for " -"`matrix.example.com`, as described in the [Configuring DNS](configuring-" -"dns.md) documentation page." +msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:15 @@ -67,31 +54,19 @@ msgid "Port availability" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:17 -msgid "" -"Ensure that port 25 is available on your Matrix server and open in your " -"firewall." +msgid "Ensure that port 25 is available on your Matrix server and open in your firewall." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:19 -msgid "" -"If you have `postfix` or some other email server software installed, you " -"may need to manually remove it first (unless you need it, of course)." +msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:21 -msgid "" -"If you really need to run an email server on the Matrix machine for other" -" purposes, it may be possible to run Email2Matrix on another port (with a" -" configuration like `matrix_email2matrix_smtp_host_bind_port: " -"\"127.0.0.01:2525\"`) and have your other email server relay messages " -"there." +msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:23 -msgid "" -"For details about using Email2Matrix alongside " -"[Postfix](http://www.postfix.org/), see " -"[here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:25 @@ -99,18 +74,11 @@ msgid "Creating a user" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:27 -msgid "" -"Before enabling Email2Matrix, you'd most likely wish to create a " -"dedicated user (or more) that would be sending messages on the Matrix " -"side. 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." +msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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:29 -msgid "" -"Refer to [Registering users](registering-users.md) for ways to create a " -"user. A regular (non-admin) user works best." +msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:31 @@ -118,17 +86,11 @@ msgid "Creating a shared room" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:33 -msgid "" -"After creating the sender user, you should create one or more Matrix " -"rooms that you share with that user. It doesn't matter who creates and " -"owns the rooms and who joins later (you or the sender user)." +msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:35 -msgid "" -"What matters is that both you and the sender user are part of the same " -"room and that the sender user has enough privileges in the room to be " -"able to send messages there." +msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:37 @@ -136,10 +98,7 @@ msgid "Inviting additional people to the room is okay too." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:39 -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." +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:41 @@ -147,11 +106,7 @@ msgid "Obtaining an access token for the sender user" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 -msgid "" -"In order for the sender user created above to be able to send messages to" -" the room, we'll need to obtain an access token for it. Refer to the " -"documentation on [how to obtain an access token](obtaining-access-" -"tokens.md)." +msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:45 @@ -159,10 +114,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:47 -msgid "" -"After doing the preparation steps above, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to " -"your needs):" +msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:72 @@ -170,31 +122,19 @@ msgid "where:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:74 -msgid "" -"MailboxName - local-part of the email address, through which emails are " -"bridged to the room whose ID is defined with MatrixRoomId" +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:75 -msgid "" -"MatrixRoomId - internal ID of the room, to which received emails are sent" -" as Matrix message" +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:76 -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" +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:77 -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)" +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:78 @@ -210,15 +150,11 @@ msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matri msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:81 -msgid "" -"SkipMarkdown - if set to \"true\", emails are bridged as plain text " -"Matrix message instead of Markdown (actually HTML)" +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:83 -msgid "" -"Refer to the official documentation " -"[here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:85 @@ -226,9 +162,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:94 @@ -236,50 +170,13 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:96 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service email2matrix` or `just setup-all`" +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:98 -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." +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:100 -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." +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 "" - -#~ msgid "" -#~ "To enable Email2Matrix, run the playbook" -#~ " with [playbook tags](playbook-tags.md) as" -#~ " below:" -#~ msgstr "" - -#~ msgid "" -#~ "The shortcut commands with the [`just`" -#~ " program](just.md) are also available: " -#~ "`just run-tags setup-email2matrix,start` " -#~ "or `just setup-all`" -#~ msgstr "" - -#~ msgid "" -#~ "`just run-tags setup-email2matrix,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 "" - 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 8afb7b0ad..8c8626914 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -26,18 +26,11 @@ msgid "Setting up Etherpad (optional)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:3 -msgid "" -"[Etherpad](https://etherpad.org) is an open source collaborative text " -"editor that can be embedded in a Matrix chat room using the [Dimension " -"integration manager](https://dimension.t2bot.io) or used as standalone " -"web app." +msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:5 -msgid "" -"When enabled together with the Jitsi audio/video conferencing system (see" -" [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made " -"available as an option during the conferences." +msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:7 @@ -45,9 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:9 -msgid "" -"To enable Etherpad, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:19 @@ -55,23 +46,15 @@ msgid "Adjusting the Etherpad URL" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:21 -msgid "" -"By default, this playbook installs Etherpad on the `etherpad.` subdomain " -"(`etherpad.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:23 -msgid "" -"By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables," -" you can easily make the service available at a **different hostname " -"and/or path** than the default one." +msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:25 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:36 @@ -79,21 +62,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:38 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Etherpad domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:40 -msgid "" -"By default, you will need to create a CNAME record for `etherpad`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:42 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:44 @@ -101,10 +78,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:46 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:53 @@ -112,35 +86,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:55 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the Etherpad admin user (`etherpad_admin_username`)." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:61 -msgid "" -"If you change the Etherpad admin user's password " -"(`etherpad_admin_password` in your `vars.yml` file) subsequently, the " -"admin user's credentials on the homeserver won't be updated " -"automatically. If you'd like to change the admin user's password, use a " -"tool like [synapse-admin](configuring-playbook-synapse-admin.md) to " -"change it, and then update `etherpad_admin_password` to let the admin " -"user know its new password." +msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:63 @@ -148,17 +106,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:65 -msgid "" -"The Etherpad UI should be available at `https://etherpad.example.com`, " -"while the admin UI (if enabled) should then be available at " -"`https://etherpad.example.com/admin`." +msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:67 -msgid "" -"If you've [decided on another hostname or path-prefix](#adjusting-the-" -"etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these " -"URLs accordingly before usage." +msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:69 @@ -166,38 +118,23 @@ msgid "Managing / Deleting old pads" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:71 -msgid "" -"If you want to manage and remove old unused pads from Etherpad, you will " -"first need to able Admin access as described above." +msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:73 -msgid "" -"Then from the plugin manager page " -"(`https://etherpad.example.com/admin/plugins`, install the `adminpads2` " -"plugin. Once installed, you should have a \"Manage pads\" section in the " -"Admin web-UI." +msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:75 -msgid "" -"How to use Etherpad widgets without an integration manager (like " -"Dimension)" +msgid "How to use Etherpad widgets without an integration manager (like Dimension)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:77 -msgid "" -"This is how it works in Element Web, it might work quite similar with " -"other clients:" +msgid "This is how it works in Element Web, it might work quite similar with other clients:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:79 -msgid "" -"To integrate a standalone Etherpad in a room, create your pad by visiting" -" `https://etherpad.example.com`. When the pad opens, copy the URL and " -"send a command like this to the room: `/addwidget URL`. You will then " -"find your integrated Etherpad within the right sidebar in the `Widgets` " -"section." +msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:81 @@ -205,17 +142,11 @@ msgid "Set Dimension default to the self-hosted Etherpad (optional)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:83 -msgid "" -"If you decided to install [Dimension integration manager](configuring-" -"playbook-dimension.md) alongside Etherpad, the Dimension administrator " -"users can configure the default URL template." +msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:85 -msgid "" -"The Dimension configuration menu can be accessed with the sprocket icon " -"as you begin to add a widget to a room in Element Web. There you will " -"find the Etherpad Widget Configuration action beneath the _Widgets_ tab." +msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:87 @@ -223,9 +154,7 @@ msgid "Removing the integrated Etherpad chat" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:89 -msgid "" -"If you wish to disable the Etherpad chat button, you can do it by " -"appending `?showChat=false` to the end of the pad URL, or the template." +msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:91 @@ -237,15 +166,9 @@ msgid "Known issues" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:95 -msgid "" -"If your Etherpad widget fails to load, this might be due to Dimension " -"generating a Pad name so long, the Etherpad app rejects it." +msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:97 -msgid "" -"`$roomId_$padName` can end up being longer than 50 characters. You can " -"avoid having this problem by altering the template so it only contains " -"the three word random identifier `$padName`." +msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po index 42508e26f..f0f9f2c1e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po @@ -22,56 +22,25 @@ msgid "Using an external PostgreSQL server (optional)" msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:3 -msgid "" -"By default, this playbook would set up a PostgreSQL database server on " -"your machine, running in a Docker container. If that's okay, you can skip" -" this document." +msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:5 -msgid "" -"**Note**: using **an external Postgres server is currently [not very " -"seamless](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1682#issuecomment-1061461683) when it comes to enabling " -"various other playbook services** - you will need to create a new " -"database/credentials for each service and to point each service to its " -"corresponding database using custom `vars.yml` configuration. **For the " -"best experience with the playbook, stick to using the integrated Postgres" -" server**." +msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:7 -msgid "" -"If you'd like to use an external Postgres server that you manage, add the" -" following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:23 -msgid "" -"The database (as specified in `matrix_synapse_database_database`) must " -"exist and be accessible with the given credentials. It must be empty or " -"contain a valid Synapse database. If empty, Synapse would populate it the" -" first time it runs." +msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:25 -msgid "" -"**Note**: the external server that you specify in " -"`matrix_synapse_database_host` must be accessible from within the " -"`matrix-synapse` Docker container (and possibly other containers too). " -"This means that it either needs to be a publicly accessible hostname or " -"that it's a hostname on the same Docker network where all containers " -"installed by this playbook run (a network called `matrix` by default). " -"Using a local PostgreSQL instance on the host (running on the same " -"machine, but not in a container) is not possible." +msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:27 -msgid "" -"The connection to your external Postgres server **will not be SSL " -"encrypted**, as [we don't support that yet](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/issues/89)." +msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po index 444b60686..ca5aac059 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -26,23 +26,11 @@ msgid "Controlling Matrix federation (optional)" msgstr "" #: ../../../docs/configuring-playbook-federation.md:3 -msgid "" -"By default, your server federates with the whole Matrix network. That is," -" people on your server can communicate with people on any other Matrix " -"server." +msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server." msgstr "" #: ../../../docs/configuring-playbook-federation.md:5 -msgid "" -"**Note**: in the sample `vars.yml` " -"([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a " -"short user ID like `@alice:example.com` instead of " -"`@alice:matrix.example.com` and set up [server delegation](howto-server-" -"delegation.md) / redirection. Without a proper configuration, your server" -" will effectively not be part of the Matrix network. If you find your " -"server is not federated, make sure to [check whether services work" -"](maintenance-checking-services.md) and your server is properly " -"delegated." +msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated." msgstr "" #: ../../../docs/configuring-playbook-federation.md:7 @@ -50,17 +38,11 @@ msgid "Federating only with select servers" msgstr "" #: ../../../docs/configuring-playbook-federation.md:9 -msgid "" -"To make your server only federate with servers of your choosing, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:17 -msgid "" -"If you wish to disable federation, you can do that with an empty list " -"(`[]`), or better yet by completely disabling federation (see below)." +msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)." msgstr "" #: ../../../docs/configuring-playbook-federation.md:19 @@ -68,15 +50,11 @@ msgid "Exposing the room directory over federation" msgstr "" #: ../../../docs/configuring-playbook-federation.md:21 -msgid "" -"By default, your server's public rooms directory is not exposed to other " -"servers via federation." +msgid "By default, your server's public rooms directory is not exposed to other servers via federation." msgstr "" #: ../../../docs/configuring-playbook-federation.md:23 -msgid "" -"If you wish to expose it, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:29 @@ -84,56 +62,29 @@ msgid "Disabling federation" msgstr "" #: ../../../docs/configuring-playbook-federation.md:31 -msgid "" -"To completely disable federation, isolating your server from the rest of " -"the Matrix network, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:37 -msgid "" -"With that, your server's users will only be able to talk among " -"themselves, but not to anyone who is on another server." +msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server." msgstr "" #: ../../../docs/configuring-playbook-federation.md:39 -msgid "" -"**Disabling federation does not necessarily disable the federation port**" -" (`8448`). Services like [Dimension](configuring-playbook-dimension.md) " -"and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs" -" exposed on that port. Even if you disable federation and only if " -"necessary, we may still be exposing the federation port and serving the " -"`openid` APIs there. To override this and completely disable Synapse's " -"federation port use:" +msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" msgstr "" #: ../../../docs/configuring-playbook-federation.md:51 -msgid "" -"Changing the federation port from 8448 to a different port to use a CDN " -"that only accepts 443/80 ports" +msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports" msgstr "" #: ../../../docs/configuring-playbook-federation.md:53 -msgid "" -"Why? This change could be useful for people running small Synapse " -"instances on small severs/VPSes to avoid being impacted by a simple " -"DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your " -"hosting provider does not provide a DOS/DDOS protection." +msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection." msgstr "" #: ../../../docs/configuring-playbook-federation.md:55 -msgid "" -"The following changes in the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and " -"make it possible to proxy the federation through a CDN such as CloudFlare" -" or any other:" +msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:" msgstr "" #: ../../../docs/configuring-playbook-federation.md:66 -msgid "" -"**Use this at you own risk as all the possible side-effects of doing this" -" are not fully known. However, it has been tested and works fine and " -"passes all the tests on without " -"issues.**" +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 69dc68308..323995184 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -26,23 +26,15 @@ msgid "Setting up the Jitsi video-conferencing platform (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:3 -msgid "" -"The playbook can install the [Jitsi](https://jitsi.org/) video-" -"conferencing platform and integrate it with Element clients ([Element Web" -"](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." +msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:5 -msgid "" -"Jitsi installation is **not enabled by default**, because it's not a core" -" component of Matrix services." +msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:7 -msgid "" -"The setup done by the playbook is very similar to [docker-jitsi-" -"meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the " -"documentation there for many of the options here." +msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:9 @@ -58,12 +50,7 @@ msgid "`4443/tcp` - RTP media fallback over TCP" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:14 -msgid "" -"`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, " -"incoming RTP packets on port `10000` may have the external IP of your " -"firewall as destination address, due to the usage of STUN in JVB (see " -"[`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting" -"/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:16 @@ -71,9 +58,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:18 -msgid "" -"To enable Jitsi, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:24 @@ -81,22 +66,15 @@ msgid "Adjusting the Jitsi URL" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:26 -msgid "" -"By default, this playbook installs Jitsi on the `jitsi.` subdomain " -"(`jitsi.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:28 -msgid "" -"By tweaking the `jitsi_hostname` variable, you can easily make the " -"service available at a **different hostname** than the default one." +msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:30 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:37 @@ -104,15 +82,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:39 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Jitsi domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:41 -msgid "" -"By default, you will need to create a CNAME record for `jitsi`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:43 @@ -120,36 +94,23 @@ msgid "(Optional) Configure Jitsi authentication and guests mode" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:45 -msgid "" -"By default the Jitsi Meet instance does not require any kind of login and" -" is open to use for anyone without registration." +msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:47 -msgid "" -"If you're fine with such an open Jitsi instance, please skip to " -"[Installing](#installing)." +msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:49 -msgid "" -"If you would like to control who is allowed to open meetings on your new " -"Jitsi instance, then please follow the following steps to enable Jitsi's " -"authentication and optionally guests mode." +msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:51 -msgid "" -"Currently, there are three supported authentication modes: 'internal' " -"(default), 'matrix' and 'ldap'." +msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:53 -msgid "" -"**Note**: Authentication is not tested via the playbook's self-checks. We" -" therefore recommend that you manually verify if authentication is " -"required by jitsi. For this, try to manually create a conference on " -"jitsi.example.com in your browser." +msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:55 @@ -157,35 +118,19 @@ msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:57 -msgid "" -"The default authentication mechanism is 'internal' auth, which requires " -"jitsi-accounts to be setup and is the recommended setup, as it also works" -" in federated rooms. With authentication enabled, all meeting rooms have " -"to be opened by a registered user, after which guests are free to join. " -"If a registered host is not yet present, guests are put on hold in " -"individual waiting rooms." +msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:59 -msgid "" -"Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml`" -" configuration:" +msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:71 -msgid "" -"**Caution**: Accounts added here and subsequently removed will not be " -"automatically removed from the Prosody server until user account cleaning" -" is integrated into the playbook." +msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:73 -msgid "" -"**If you get an error** like this: \"Error: Account creation/modification" -" not supported.\", it's likely that you had previously installed Jitsi " -"without auth/guest support. In such a case, you should look into " -"[Rebuilding your Jitsi installation](#rebuilding-your-jitsi-" -"installation)." +msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:75 @@ -193,18 +138,11 @@ msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:77 -msgid "" -"**Attention: Probably breaks Jitsi in federated rooms and does not allow " -"sharing conference links with guests.**" +msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:79 -msgid "" -"Using this authentication type require a [Matrix User Verification " -"Service](https://github.com/matrix-org/matrix-user-verification-service)." -" By default, this playbook creates and configures a user-verification-" -"service to run locally, see [configuring-user-verification-service" -"](configuring-playbook-user-verification-service.md)." +msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:81 @@ -212,10 +150,7 @@ msgid "To enable set this configuration at host level:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:89 -msgid "" -"For more information see also [https://github.com/matrix-org/prosody-mod-" -"auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-" -"auth-matrix-user-verification)." +msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:91 @@ -227,11 +162,7 @@ msgid "An example LDAP configuration could be:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:113 -msgid "" -"For more information refer to the [docker-jitsi-" -"meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-" -"ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs" -"/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:115 @@ -239,20 +170,11 @@ msgid "(Optional) Making your Jitsi server work on a LAN" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:117 -msgid "" -"By default the Jitsi Meet instance does not work with a client in LAN " -"(Local Area Network), even if others are connected from WAN. There are no" -" video and audio. In the case of WAN to WAN everything is ok." +msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:119 -msgid "" -"The reason is the Jitsi VideoBridge git to LAN client the IP address of " -"the docker image instead of the host. The " -"[documentation](https://jitsi.github.io/handbook/docs/devops-guide" -"/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of " -"Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment " -"variable to make it work." +msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:121 @@ -260,9 +182,7 @@ msgid "Here is how to do it in the playbook." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:123 -msgid "" -"Add these two lines to your " -"`inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:130 @@ -270,42 +190,23 @@ msgid "(Optional) Fine tune Jitsi" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:132 -msgid "" -"Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` " -"configuration to save up resources (explained below):" +msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:147 -msgid "" -"You may want to **suspend unused video layers** until they are requested " -"again, to save up resources on both server and clients. Read more on this" -" feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-" -"feature/)" +msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:149 -msgid "" -"You may wish to **disable audio levels** to avoid excessive refresh of " -"the client-side page and decrease the CPU consumption involved." +msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:151 -msgid "" -"You may want to **limit the number of video feeds forwarded to each " -"client**, to save up resources on both server and clients. As clients’ " -"bandwidth and CPU may not bear the load, use this setting to avoid lag " -"and crashes. This feature is found by default in other webconference " -"applications such as Office 365 Teams (limit is set to 4). Read how it " -"works [here](https://github.com/jitsi/jitsi-" -"videobridge/blob/master/doc/last-n.md) and performance evaluation on this" -" [study](https://jitsi.org/wp-" -"content/uploads/2016/12/nossdav2015lastn.pdf)." +msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:153 -msgid "" -"You may want to **limit the maximum video resolution**, to save up " -"resources on both server and clients." +msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:155 @@ -313,15 +214,11 @@ msgid "(Optional) Specify a Max number of participants on a Jitsi conference" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:157 -msgid "" -"The playbook allows a user to set a max number of participants allowed to" -" join a Jitsi conference. By default there is no limit." +msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:159 -msgid "" -"In order to set the max number of participants use the following " -"**additional** configuration:" +msgid "In order to set the max number of participants use the following **additional** configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:165 @@ -329,73 +226,39 @@ msgid "(Optional) Additional JVBs" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:167 -msgid "" -"By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi" -"/jitsi-videobridge)) is deployed on the same host as the Matrix server. " -"To allow more video-conferences to happen at the same time, you may need " -"to provision additional JVB services on other hosts." +msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:169 -msgid "" -"There is an ansible playbook that can be run with the following tag: " -"`ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers " -"jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" +msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:171 -msgid "" -"For this role to work you will need an additional section in the ansible " -"hosts file with the details of the JVB hosts, for example:" +msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:178 -msgid "" -"Each JVB will require a server ID to be set so that it can be uniquely " -"identified and this allows Jitsi to keep track of which conferences are " -"on which JVB. The server ID is set with the variable " -"`jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment " -"variables in the JVB docker container. This variable can be set via the " -"host file, a parameter to the ansible command or in the `vars.yaml` for " -"the host which will have the additional JVB. For example:" +msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:190 -msgid "" -"Note that the server ID `jvb-1` is reserved for the JVB instance running " -"on the Matrix host and therefore should not be used as the ID of an " -"additional jvb host." +msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:192 -msgid "" -"The additional JVB will also need to expose the colibri web socket port " -"and this can be done with the following variable:" +msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:198 -msgid "" -"The JVB will also need to know where the prosody xmpp server is located, " -"similar to the server ID this can be set in the vars for the JVB by using" -" the variable `jitsi_xmpp_server`. The Jitsi prosody container is " -"deployed on the Matrix server by default so the value can be set to the " -"Matrix domain. For example:" +msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:204 -msgid "" -"However, it can also be set the ip address of the Matrix server. This can" -" be useful if you wish to use a private ip. For example:" +msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:210 -msgid "" -"For the JVB to be able to contact the XMPP server, the latter must expose" -" the XMPP port (5222). By default, the Matrix server does not expose the " -"port; only the XMPP container exposes it internally inside the host, " -"which means that the first JVB (which runs on the Matrix server) can " -"reach it but the additional JVB cannot. The port is exposed by setting " -"`jitsi_prosody_container_jvb_host_bind_port` like this:" +msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:216 @@ -403,17 +266,11 @@ msgid "(The default is empty; if it's set then docker forwards the port.)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:218 -msgid "" -"Applied together this will allow you to provision extra JVB instances " -"which will register themselves with the prosody service and be available " -"for jicofo to route conferences too." +msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:220 -msgid "" -"To make Traefik reverse-proxy to these additional JVBs (living on other " -"hosts), **you would need to add the following Traefik configuration " -"extension**:" +msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:256 @@ -421,11 +278,7 @@ msgid "(Optional) Enable Gravatar" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:258 -msgid "" -"In the default Jisti Meet configuration, gravatar.com is enabled as an " -"avatar service. This results in third party request leaking data to " -"gravatar. Since Element clients already send the url of configured Matrix" -" avatars to Jitsi, we disabled gravatar." +msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:260 @@ -433,11 +286,7 @@ msgid "To enable Gravatar set:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:266 -msgid "" -"**Beware**: This leaks information to a third party, namely the Gravatar-" -"Service (unless configured otherwise: gravatar.com). Besides metadata, " -"this includes the Matrix user_id and possibly the room identifier (via " -"`referrer` header)." +msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:268 @@ -445,26 +294,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:270 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:277 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:279 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:281 @@ -476,34 +314,19 @@ msgid "You can use the self-hosted Jitsi server in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:285 -msgid "" -"**by adding a widget to a room via Element Web** (the one configured by " -"the playbook at `https://element.example.com`). Just start a voice or a " -"video call in a room containing more than 2 members and that would create" -" a Jitsi widget which utilizes your self-hosted Jitsi server." +msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:287 -msgid "" -"**by adding a widget to a room via the Dimension integration manager**. " -"You'll have to point the widget to your own Jitsi server manually. See " -"our [Dimension integration manager](./configuring-playbook-dimension.md) " -"documentation page for more details. Naturally, Dimension would need to " -"be installed first (the playbook doesn't install it by default)." +msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:289 -msgid "" -"**directly (without any Matrix integration)**. Just go to " -"`https://jitsi.example.com`" +msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:291 -msgid "" -"**Note**: Element apps on mobile devices currently [don't support joining" -" meetings on a self-hosted Jitsi server](https://github.com/element-hq" -"/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md" -"#mobile-app-support)." +msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:293 @@ -515,22 +338,15 @@ msgid "Rebuilding your Jitsi installation" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:297 -msgid "" -"**If you ever run into any trouble** or **if you change configuration " -"(`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi " -"setup." +msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:299 -msgid "" -"We normally don't require such manual intervention for other services, " -"but Jitsi services generate a lot of configuration files on their own." +msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:301 -msgid "" -"These files are not all managed by Ansible (at least not yet), so you may" -" sometimes need to delete them all and start fresh." +msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:303 @@ -538,20 +354,13 @@ msgid "To rebuild your Jitsi configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:305 -msgid "" -"ask Ansible to stop all Jitsi services: `just run-tags stop-group " -"--extra-vars=group=jitsi`" +msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:306 -msgid "" -"SSH into the server and do this and remove all Jitsi configuration & data" -" (`rm -rf /matrix/jitsi`)" +msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:307 -msgid "" -"ask Ansible to set up Jitsi anew and restart services (`just install-" -"service jitsi`)" +msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po index 201c1802b..bcbd4040f 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 @@ -22,31 +22,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-ldap-auth.md:1 -msgid "" -"Setting up the LDAP authentication password provider module (optional, " -"advanced)" +msgid "Setting up the LDAP authentication password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:3 -msgid "" -"The playbook can install and configure the [matrix-synapse-" -"ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth " -"password provider for you." +msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"synapse-ldap3/blob/main/README.rst) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:7 -msgid "" -"If you decide that you'd like to let this playbook install it for you, " -"add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:24 @@ -54,10 +42,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:26 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:32 @@ -65,11 +50,7 @@ msgid "Using ma1sd Identity Server for authentication" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:34 -msgid "" -"If you wish to use the ma1sd Identity Server for LDAP authentication " -"instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-" -"synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration" -"](configuring-playbook-ma1sd.md#authentication)." +msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:36 @@ -77,15 +58,5 @@ msgid "Handling user registration" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:38 -msgid "" -"If you wish for users to also be able to make new registrations against " -"LDAP, you may **also** wish to [set up the ldap-registration-proxy" -"](configuring-playbook-matrix-ldap-registration-proxy.md)." +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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 50a616c77..16c0ce771 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -26,45 +26,23 @@ 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)." +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." +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." +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." +msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:11 -msgid "" -"**Note**: enabling ma1sd, means that the `openid` API endpoints will be " -"exposed on the Matrix Federation port (usually `8448`), even if " -"[federation](configuring-playbook-federation.md) is disabled. It's " -"something to be aware of, especially in terms of firewall whitelisting " -"(make sure port `8448` is accessible)." +msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:13 @@ -72,9 +50,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:15 -msgid "" -"To make the ma1sd Identity Server enable its federation features, set up " -"a SRV record that looks like this:" +msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:17 @@ -82,24 +58,15 @@ msgid "Name: `_matrix-identity._tcp` (use this text as-is)" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:18 -msgid "" -"Content: `10 0 443 matrix.example.com` (replace `example.com` with your " -"own)" +msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:20 -msgid "" -"See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-" -"and-your-privacy#choices-are-never-easy) for information on the privacy " -"implications of setting up this SRV record." +msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:22 -msgid "" -"**Note**: This `_matrix-identity._tcp` SRV record for the identity server" -" is different from the `_matrix._tcp` that can be used for Synapse " -"delegation. See [howto-server-delegation.md](howto-server-delegation.md) " -"for more information about delegation." +msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:24 @@ -107,9 +74,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:26 -msgid "" -"To enable ma1sd, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:32 @@ -117,23 +82,15 @@ msgid "Matrix.org lookup forwarding" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:34 -msgid "" -"To ensure maximum discovery, you can make your identity server also " -"forward lookups to the central matrix.org Identity server (at the cost of" -" potentially leaking all your contacts information)." +msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:36 -msgid "" -"Enabling this is discouraged and you'd better [learn " -"more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups)" -" before proceeding." +msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:38 -msgid "" -"To enable matrix.org forwarding, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:44 @@ -141,33 +98,19 @@ msgid "Additional features" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:46 -msgid "" -"What this playbook configures for your is some bare minimum Identity " -"Server functionality, so that you won't need to rely on external 3rd " -"party services." +msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:48 -msgid "" -"A few variables can be toggled in this playbook to alter the ma1sd " -"configuration that gets generated." +msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:50 -msgid "" -"Still, ma1sd can do much more. You can refer to the [ma1sd " -"website](https://github.com/ma1uta/ma1sd) for more details and " -"configuration options." +msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:52 -msgid "" -"To use a more custom configuration, you can define a " -"`matrix_ma1sd_configuration_extension_yaml` string variable and put your " -"configuration in it. To learn more about how to do this, refer to the " -"information about `matrix_ma1sd_configuration_extension_yaml` in the " -"[default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) " -"of the ma1sd component." +msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:54 @@ -175,10 +118,7 @@ msgid "Customizing email templates" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:56 -msgid "" -"If you'd like to change the default email templates used by ma1sd, take a" -" look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in " -"the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:58 @@ -186,59 +126,31 @@ msgid "ma1sd-controlled Registration" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:60 -msgid "" -"To use the " -"[Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" -" feature of ma1sd, you can make use of the following variables:" +msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:62 -msgid "" -"`matrix_synapse_enable_registration` - to enable user-initiated " -"registration in Synapse" +msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:64 -msgid "" -"`matrix_synapse_enable_registration_captcha` - to validate registering " -"users using reCAPTCHA, as described in the [enabling reCAPTCHA" -"](configuring-captcha.md) documentation." +msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:66 -msgid "" -"`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among" -" `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:68 -msgid "" -"variables prefixed with `matrix_ma1sd_container_labels_` (e.g. " -"`matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) " -"- to configure the Traefik reverse-proxy to capture and send registration" -" requests to ma1sd (instead of Synapse), so it can apply its additional " -"functionality" +msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:70 -msgid "" -"`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as " -"required. See the [Registration feature's " -"docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" -" for inspiration. Also see the [Additional features](#additional-" -"features) section below to learn more about how to use " -"`matrix_ma1sd_configuration_extension_yaml`." +msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:72 -msgid "" -"**Note**: For this to work, either the homeserver needs to [federate" -"](configuring-playbook-federation.md) or the `openid` APIs need to " -"exposed on the federation port. When federation is disabled and ma1sd is " -"enabled, we automatically expose the `openid` APIs (only!) on the " -"federation port. Make sure the federation port (usually " -"`https://matrix.example.com:8448`) is whitelisted in your firewall (even " -"if you don't actually use/need federation)." +msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:74 @@ -246,18 +158,11 @@ msgid "Authentication" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:76 -msgid "" -"[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md)" -" provides the possibility to use your own [Identity " -"Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md)" -" (for example LDAP) to authenticate users on your Homeserver." +msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:78 -msgid "" -"To enable authentication against an LDAP server, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:98 @@ -265,11 +170,7 @@ msgid "Example: SMS verification" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:100 -msgid "" -"If your use case requires mobile verification, it is quite simple to " -"integrate ma1sd with [Twilio](https://www.twilio.com/), an online " -"telephony services gateway. Their prices are reasonable for low-volume " -"projects and integration can be done with the following configuration:" +msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:114 @@ -277,12 +178,7 @@ msgid "Example: Open Registration for every Domain" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:116 -msgid "" -"If you want to open registration for any domain, you have to setup the " -"allowed domains with ma1sd's `blacklist` and `whitelist`. The default " -"behavior when neither the `blacklist`, nor the `whitelist` match, is to " -"allow registration. Beware: you can't block toplevel domains (aka `.xy`) " -"because the internal architecture of ma1sd doesn't allow that." +msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:130 @@ -290,25 +186,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:132 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:139 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:141 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:143 @@ -316,28 +202,13 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:145 -msgid "" -"If email address validation emails sent by ma1sd are not reaching you, " -"you should look into [Adjusting email-sending settings](configuring-" -"playbook-email.md)." +msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:147 -msgid "" -"If you'd like additional logging information, temporarily enable verbose " -"logging for ma1sd." +msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:149 -msgid "" -"To enable it, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/ma1uta/ma1sd) to learn" -#~ " what it does and why it might" -#~ " be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po index f10c16f93..3420a45fc 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po @@ -26,33 +26,19 @@ msgid "Setting up Matrix Authentication Service (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:3 -msgid "" -"This playbook can install and configure [Matrix Authentication " -"Service](https://github.com/element-hq/matrix-authentication-service/) " -"(MAS) - a service operating alongside your existing [Synapse" -"](./configuring-playbook-synapse.md) homeserver and providing [better " -"authentication, session management and permissions in " -"Matrix](https://matrix.org/blog/2023/09/better-auth/)." +msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:5 -msgid "" -"Matrix Authentication Service is an implementation of [MSC3861: Next-" -"generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com" -"/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, " -"tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." +msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:7 -msgid "" -"**Before going through with starting to use Matrix Authentication " -"Service**, make sure to read:" +msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:9 -msgid "" -"the [Reasons to use Matrix Authentication Service](#reasons-to-use-" -"matrix-authentication-service) section below" +msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:10 @@ -64,10 +50,7 @@ msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:13 -msgid "" -"**If you've already been using Synapse** and have user accounts in its " -"database, you can [migrate to Matrix Authentication Service](#migrating-" -"an-existing-synapse-homeserver-to-matrix-authentication-service)." +msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:15 @@ -75,66 +58,39 @@ msgid "Reasons to use Matrix Authentication Service" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:17 -msgid "" -"You may be wondering whether you should make the switch to Matrix " -"Authentication Service (MAS) or keep using your existing authentication " -"flow via Synapse (password-based or [OIDC](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." +msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:19 -msgid "" -"Matrix Authentication Service is **still an experimental service** and " -"**not a default** for this Ansible playbook." +msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:21 -msgid "" -"The [Expectations](#expectations) section contains a list of what works " -"and what doesn't (**some services don't work with MAS yet**), as well as " -"the **relative irreversability** of the migration process." +msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:23 -msgid "" -"Below, we'll try to **highlight some potential reasons for switching** to" -" Matrix Authentication Service:" +msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:25 -msgid "" -"To use SSO in [Element X](https://element.io/blog/element-x-ignition/). " -"The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-" -"connect-for-single-sign-on) login flow is only supported in old Element " -"clients and will not be supported in Element X. Element X will only " -"support the new SSO-based login flow provided by MAS, so if you want to " -"use SSO with Element X, you will need to switch to MAS." +msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:27 -msgid "" -"To help drive adoption of the \"Next-generation auth for Matrix\" by " -"switching to what's ultimately coming anyway" +msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:29 -msgid "" -"To help discover (and potentially fix) MAS integration issues with this " -"Ansible playbook" +msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:31 -msgid "" -"To help discover (and potentially fix) MAS integration issues with " -"various other Matrix components (bridges, bots, clients, etc.)" +msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:33 -msgid "" -"To reap some of the security benefits that Matrix Authentication Service " -"offers, as outlined in the [Better authentication, session management and" -" permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) " -"article." +msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:35 @@ -142,32 +98,15 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:37 -msgid "" -"⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver " -"implementation (which is the default for this playbook). Other homeserver" -" implementations ([Dendrite](./configuring-playbook-dendrite.md), " -"[Conduit](./configuring-playbook-conduit.md), etc.) do not support " -"integrating wtih Matrix Authentication Service yet." +msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:39 -msgid "" -"⚠️ **email sending** configured (see [Adjusting email-sending settings" -"](./configuring-playbook-email.md)), because **Matrix Authentication " -"Service [still insists](https://github.com/element-hq/matrix-" -"authentication-service/issues/1505) on having a verified email address " -"for each user** going through the new SSO-based login flow. It's also " -"possible to [work around email deliverability issues](#working-around-" -"email-deliverability-issues) if your email configuration is not working." +msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:41 -msgid "" -"❌ **disabling all password providers** for Synapse (things like [shared-" -"secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth" -"](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-" -"playbook-ldap-auth.md), etc.) More details about this are available in " -"the [Expectations](#expectations) section below." +msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:43 @@ -175,37 +114,15 @@ msgid "Expectations" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:45 -msgid "" -"This section details what you can expect when switching to the Matrix " -"Authentication Service (MAS)." +msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:47 -msgid "" -"❌ **Synapse password providers will need to be disabled**. You can no " -"longer use [shared-secret-auth](./configuring-playbook-shared-secret-" -"auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth" -"](./configuring-playbook-ldap-auth.md), etc. When the authentication flow" -" is handled by MAS (not by Synapse anymore), it doesn't make sense to " -"extend the Synapse authentication flow with additional modules. Many " -"bridges used to rely on shared-secret-auth for doing double-puppeting " -"(impersonating other users), but most (at least the mautrix bridges) " -"nowadays use [Appservice Double Puppet](./configuring-playbook-" -"appservice-double-puppet.md) as a better alternative. Older/maintained " -"bridges may still rely on shared-secret-auth, as do other services like " -"[matrix-corporal](./configuring-playbook-matrix-corporal.md)." +msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:49 -msgid "" -"❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-" -"admin.md) do not have full compatibility with MAS yet**. synapse-admin " -"already supports [login with access token](https://github.com/etkecc" -"/synapse-admin/pull/58), browsing users (which Synapse will internally " -"fetch from MAS) and updating user avatars. However, editing users " -"(passwords, etc.) now needs to happen directly against MAS using the [MAS" -" Admin API](https://element-hq.github.io/matrix-authentication-" -"service/api/index.html), which synapse-admin cannot interact with yet." +msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:51 @@ -213,23 +130,15 @@ msgid "❌ **Some services experience issues when authenticating via MAS**:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:53 -msgid "" -"[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first" -" time around, but it consistently fails after restarting:" +msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:55 -msgid "" -"cannot initialize matrix bot error=\"olm account is marked as shared, " -"keys seem to have disappeared from the server\"" +msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\"" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:57 -msgid "" -"[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) " -"fails to start (see [element-hq/matrix-authentication-" -"service#3439](https://github.com/element-hq/matrix-authentication-" -"service/issues/3439))" +msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:58 @@ -237,131 +146,51 @@ msgid "Other services may be similarly affected. This list is not exhaustive." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:60 -msgid "" -"❌ **Encrypted appservices** do not work yet (related to " -"[MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) " -"and [PR 17705 for Synapse](https://github.com/element-" -"hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will" -" fail to start (see [this issue](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/3658) for Hookshot). You can use these " -"bridges/bots only if you **keep end-to-bridge encryption disabled** " -"(which is the default setting)." +msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:62 -msgid "" -"⚠️ **You will need to have email sending configured** (see [Adjusting " -"email-sending settings](./configuring-playbook-email.md)), because " -"**Matrix Authentication Service [still insists](https://github.com" -"/element-hq/matrix-authentication-service/issues/1505) on having a " -"verified email address for each user** going through the new SSO-based " -"login flow. It's also possible to [work around email deliverability " -"issues](#working-around-email-deliverability-issues) if your email " -"configuration is not working." +msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:64 -msgid "" -"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " -"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" -"authentication-service) is **possible**, but requires **some playbook-" -"assisted manual work**. Migration is **reversible with no or minor issues" -" if done quickly enough**, but as users start logging in (creating new " -"login sessions) via the new MAS setup, disabling MAS and reverting back " -"to the Synapse user database will cause these new sessions to break." +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:66 -msgid "" -"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " -"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" -"authentication-service) does not currently seem to preserve the \"admin\"" -" flag for users (as found in the Synapse database). All users are " -"imported as non-admin - see [element-hq/matrix-authentication-" -"service#3440](https://github.com/element-hq/matrix-authentication-" -"service/issues/3440). You may need update the Matrix Authentication " -"Service's database manually and adjust the `can_request_admin` column in " -"the `users` table to `true` for users that need to be administrators " -"(e.g. `UPDATE users SET can_request_admin = true WHERE username = " -"'someone';`)" +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:68 -msgid "" -"⚠️ Delegating user authentication to MAS causes **your Synapse server to " -"be completely dependant on one more service** for its operations. MAS is " -"quick & lightweight and should be stable enough already, but this is " -"something to keep in mind when making the switch." +msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:70 -msgid "" -"⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " -"migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 " -"configuration](#upstream-oauth2-configuration)." +msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:72 -msgid "" -"⚠️ A [compatibility layer](https://element-hq.github.io/matrix-" -"authentication-service/setup/homeserver.html#set-up-the-compatibility-" -"layer) is installed - all `/_matrix/client/*/login` (etc.) requests will " -"be routed to MAS instead of going to the homeserver. This is done both " -"publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and " -"on the internal Traefik entrypoint (e.g. `https://matrix-" -"traefik:8008/_matrix/client/*/login`) which helps addon services reach " -"the homeserver's Client-Server API. You typically don't need to do " -"anything to make this work, but it's good to be aware of it, especially " -"if you have a [custom webserver setup](./configuring-playbook-own-" -"webserver.md)." +msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:74 -msgid "" -"✅ Your **existing login sessions will continue to work** (you won't get " -"logged out). Migration will require a bit of manual work and minutes of " -"downtime, but it's not too bad." +msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:76 -msgid "" -"✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), " -"[Element Web](./configuring-playbook-client-element-web.md), Element X, " -"FluffyChat) will be able to use the **new SSO-based login flow** provided" -" by Matrix Authentication Service" +msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:78 -msgid "" -"✅ The **old login flow** (called `m.login.password`) **will still " -"continue to work**, so clients (old Element Web, etc.) and bridges/bots " -"that don't support the new OIDC-based login flow will still work. Going " -"through the old login flow does not require users to have a verified " -"email address, as [is the case](https://github.com/element-hq/matrix-" -"authentication-service/issues/1505) for the new SSO-based login flow." +msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:80 -msgid "" -"✅ [Registering users](./registering-users.md) via **the playbook's " -"`register-user` tag remains unchanged**. The playbook automatically does " -"the right thing regardless of homeserver implementation (Synapse, " -"Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, " -"the playbook will forward user-registration requests to MAS. Registering " -"users via the command-line is no longer done via the " -"`/matrix/synapse/bin/register` script, but via `/matrix/matrix-" -"authentication-service/bin/register-user`." +msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:82 -msgid "" -"✅ Users that are prepared by the playbook (for bots, bridges, etc.) will " -"continue to be registered automatically as expected. The playbook " -"automatically does the right thing regardless of homeserver " -"implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or " -"not. When MAS is enabled, the playbook will forward user-registration " -"requests to MAS." +msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:84 @@ -373,11 +202,7 @@ msgid "New homeserver" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:88 -msgid "" -"For new homeservers (which don't have any users in their Synapse database" -" yet), follow the [Adjusting the playbook configuration](#adjusting-the-" -"playbook-configuration) instructions and then proceed with " -"[Installing](#installing)." +msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:90 @@ -385,10 +210,7 @@ msgid "Existing homeserver" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:92 -msgid "" -"Other homeserver implementations ([Dendrite](./configuring-playbook-" -"dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not " -"support integrating wtih Matrix Authentication Service yet." +msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:94 @@ -396,21 +218,11 @@ msgid "For existing Synapse homeservers:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:96 -msgid "" -"when following the [Adjusting the playbook configuration](#adjusting-the-" -"playbook-configuration) instructions, make sure to **disable the " -"integration between Synapse and MAS** by **uncommenting** the " -"`matrix_authentication_service_migration_in_progress: true` line as " -"described in the [Marking an existing homeserver for migration](#marking-" -"an-existing-homeserver-for-migration) section below." +msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:98 -msgid "" -"then follow the [Migrating an existing Synapse homeserver to Matrix " -"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" -"matrix-authentication-service) instructions to perform the installation " -"and migration" +msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:100 @@ -418,23 +230,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:102 -msgid "" -"To enable Matrix Authentication Service, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:116 -msgid "" -"In the sub-sections that follow, we'll cover some additional " -"configuration options that you may wish to adjust." +msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:118 -msgid "" -"There are many other configuration options available. Consult the " -"[`defaults/main.yml` file](../roles/custom/matrix-authentication-" -"service/defaults/main.yml) in the [matrix-authentication-service " -"role](../roles/custom/matrix-authentication-service/) to discover them." +msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:120 @@ -442,27 +246,16 @@ msgid "Adjusting the Matrix Authentication Service URL" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:122 -msgid "" -"By default, this playbook installs the Matrix Authentication Service on " -"the `matrix.` subdomain, at the `/auth` path " -"(https://matrix.example.com/auth). This makes it easy to install it, " -"because it **doesn't require additional DNS records to be set up**. If " -"that's okay, you can skip this section." +msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:124 -msgid "" -"By tweaking the `matrix_authentication_service_hostname` and " -"`matrix_authentication_service_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:126 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:149 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:134 @@ -470,19 +263,11 @@ msgid "Marking an existing homeserver for migration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:136 -msgid "" -"The [configuration above](#adjusting-the-playbook-configuration) " -"instructs existing users wishing to migrate to add " -"`matrix_authentication_service_migration_in_progress: true` to their " -"configuration." +msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:138 -msgid "" -"This is done temporarily. The migration steps are described in more " -"detail in the [Migrating an existing Synapse homeserver to Matrix " -"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" -"matrix-authentication-service) section below." +msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:140 @@ -490,60 +275,35 @@ msgid "Upstream OAuth2 configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:142 -msgid "" -"To make Matrix Authentication Service delegate to an existing upstream " -"OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` " -"setting](https://element-hq.github.io/matrix-authentication-" -"service/reference/configuration.html#upstream_oauth2providers)." +msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:144 -msgid "" -"The playbook exposes a " -"`matrix_authentication_service_config_upstream_oauth2_providers` variable" -" for controlling this setting." +msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:261 -msgid "" -"💡 Refer to the [`upstream_oauth2.providers` setting](https://element-" -"hq.github.io/matrix-authentication-" -"service/reference/configuration.html#upstream_oauth2providers) for the " -"most up-to-date schema and example for providers. The value shown above " -"here may be out of date." +msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:263 -msgid "" -"⚠️ The syntax for existing [OIDC providers configured in Synapse" -"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" -"sign-on) is slightly different, so you will need to adjust your " -"configuration when switching from Synapse OIDC to MAS upstream OAuth2." +msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:265 -msgid "" -"⚠️ When [migrating an existing homeserver](#migrating-an-existing-" -"synapse-homeserver-to-matrix-authentication-service) which contains OIDC-" -"sourced users, you will need to:" +msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:267 -msgid "" -"[Configure upstream OIDC provider mapping for syn2mas](#configuring-" -"upstream-oidc-provider-mapping-for-syn2mas)" +msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:268 -msgid "" -"go through the [migrating an existing homeserver](#migrating-an-existing-" -"synapse-homeserver-to-matrix-authentication-service) process" +msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:269 -msgid "" -"remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) " -"to prevent it being in conflict with the MAS OIDC configuration" +msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:271 @@ -551,10 +311,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:273 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Matrix Authentication Service domain to the " -"Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:275 @@ -562,9 +319,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:277 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:279 @@ -572,10 +327,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:281 -msgid "" -"Now that you've [adjusted the playbook configuration](#adjusting-the-" -"playbook-configuration) and [your DNS records](#adjusting-dns-records), " -"you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:288 @@ -583,34 +335,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:290 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:292 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:294 -msgid "" -"If you're in the process of migrating an existing Synapse homeserver to " -"MAS, you should now follow the rest of the steps in the [Migrating an " -"existing Synapse homeserver to Matrix Authentication Service](#migrating-" -"an-existing-synapse-homeserver-to-matrix-authentication-service) guide." +msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:296 -msgid "" -"💡 After installation, you should [verify that Matrix Authentication " -"Service is installed correctly](#verify-that-matrix-authentication-" -"service-is-installed-correctly)." +msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:298 @@ -618,16 +355,11 @@ msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:300 -msgid "" -"Our migration guide is loosely based on the upstream [Migrating an " -"existing homeserver](https://element-hq.github.io/matrix-authentication-" -"service/setup/migration.html) guide." +msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:302 -msgid "" -"Migration is done via a tool called `syn2mas`, which the playbook could " -"run for you (in a container)." +msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:304 @@ -635,11 +367,7 @@ msgid "The installation + migration steps are like this:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:306 -msgid "" -"[Adjust your configuration](#adjusting-the-playbook-configuration) to " -"**disable the integration between the homeserver and MAS**. This is done " -"by **uncommenting** the " -"`matrix_authentication_service_migration_in_progress: true` line." +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:308 @@ -647,74 +375,39 @@ msgid "Perform the initial [installation](#installing). At this point:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:310 -msgid "" -"Matrix Authentication Service will be installed. Its database will be " -"empty, so it cannot validate existing access tokens or authentication " -"users yet." +msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:312 -msgid "" -"The homeserver will still continue to use its local database for " -"validating existing access tokens." +msgid "The homeserver will still continue to use its local database for validating existing access tokens." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:314 -msgid "" -"Various [compatibility layer URLs](https://element-hq.github.io/matrix-" -"authentication-service/setup/homeserver.html#set-up-the-compatibility-" -"layer) are not yet installed. New login sessions will still be forwarded " -"to the homeserver, which is capable of completing them." +msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:316 -msgid "" -"The `matrix-user-creator` role would be suppressed, so that it doesn't " -"automatically attempt to create users (for bots, etc.) in the MAS " -"database. These user accounts likely already exist in Synapse's user " -"database and could be migrated over (via syn2mas, as per the steps " -"below), so creating them in the MAS database would have been unnecessary " -"and potentially problematic (conflicts during the syn2mas migration)." +msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:318 -msgid "" -"Consider taking a full [backup of your Postgres database](./maintenance-" -"postgres.md#backing-up-postgresql). This is done just in case. The " -"**syn2mas migration tool does not delete any data**, so it should be " -"possible to revert to your previous setup by merely disabling MAS and re-" -"running the playbook (no need to restore a Postgres backup). However, do " -"note that as users start logging in (creating new login sessions) via the" -" new MAS setup, disabling MAS and reverting back to the Synapse user " -"database will cause these new sessions to break." +msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:320 -msgid "" -"[Migrate your data from Synapse to Matrix Authentication Service using " -"syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-" -"service-using-syn2mas)" +msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:322 -msgid "" -"[Adjust your configuration](#adjusting-the-playbook-configuration) again," -" to:" +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:324 -msgid "" -"remove the `matrix_authentication_service_migration_in_progress: false` " -"line" +msgid "remove the `matrix_authentication_service_migration_in_progress: false` line" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:326 -msgid "" -"if you had been using [OIDC providers configured in Synapse" -"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" -"sign-on), remove all Synapse OIDC-related configuration " -"(`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS " -"OIDC configuration" +msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:328 @@ -726,42 +419,23 @@ msgid "The homeserver will start delegating authentication to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:332 -msgid "" -"The compatibility layer URLs will be installed. New login sessions will " -"be completed by MAS." +msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:334 -msgid "" -"[Verify that Matrix Authentication Service is installed correctly" -"](#verify-that-matrix-authentication-service-is-installed-correctly)" +msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:336 -msgid "" -"Migrate your data from Synapse to Matrix Authentication Service using " -"syn2mas" +msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:338 -msgid "" -"We **don't** ask you to [run the `syn2mas` migration advisor " -"command](https://element-hq.github.io/matrix-authentication-" -"service/setup/migration.html#run-the-migration-advisor), because it only " -"gives you the green light if your Synapse configuration " -"(`homeserver.yaml`) is configured in a way that's compatible with MAS " -"(delegating authentication to MAS; disabling Synapse's password config; " -"etc.). Until we migrate your data with the `syn2mas` tool, we " -"intentionally avoid doing these changes to allow existing user sessions " -"to work." +msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:340 -msgid "" -"You can invoke the `syn2mas` tool via the playbook by running the " -"playbook's `matrix-authentication-service-syn2mas` tag. We recommend " -"first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " -"migration](#performing-a-real-syn2mas-migration)." +msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:342 @@ -769,25 +443,15 @@ msgid "Configuring syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:344 -msgid "" -"If you're using [OIDC with Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " -"[Configuring upstream OIDC provider mapping for syn2mas](#configuring-" -"upstream-oidc-provider-mapping-for-syn2mas)." +msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:346 -msgid "" -"If you only have local (non-OIDC) users in your Synapse database, you can" -" likely run `syn2mas` as-is (without doing additional configuration " -"changes)." +msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:348 -msgid "" -"When you're done with potentially configuring `syn2mas`, proceed to doing" -" a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " -"migration](#performing-a-real-syn2mas-migration)." +msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:350 @@ -795,13 +459,7 @@ msgid "Configuring upstream OIDC provider mapping for syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:352 -msgid "" -"If you have existing OIDC users in your Synapse user database (which will" -" be the case if when using [OIDC with Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to " -"pass an additional `--upstreamProviderMapping` argument to the `syn2mas` " -"tool to tell it which provider (on the Synapse side) maps to which other " -"provider on the MAS side." +msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:354 @@ -809,10 +467,7 @@ msgid "If you don't do this, `syn2mas` would report errors like this one:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:356 -msgid "" -"[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-" -"b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: " -"Unknown upstream provider oidc-keycloak]" +msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:358 @@ -820,27 +475,15 @@ msgid "Below is an example situation and a guide for how to solve it." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:360 -msgid "" -"If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) " -"named `keycloak`, in the Synapse database users would be associated with " -"the `oidc-keycloak` provider (note the `oidc-` prefix that was added " -"automatically by Synapse to your `idp_id` value)." +msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:362 -msgid "" -"The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` " -"on the MAS side, as defined in " -"`matrix_authentication_service_config_upstream_oauth2_providers` (see the" -" [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section " -"above)." +msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:364 -msgid "" -"To tell `syn2mas` how the Synapse-configured OIDC provider maps to the " -"new MAS-configured OIDC provider, add this additional configuration to " -"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:373 @@ -848,10 +491,7 @@ msgid "Performing a syn2mas dry-run" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:375 -msgid "" -"Having [configured syn2mas](#configuring-syn2mas), we recommend doing a " -"[dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to " -"verify that everything will work out as expected." +msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:377 @@ -863,11 +503,7 @@ msgid "To perform a dry-run, run:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:385 -msgid "" -"Observe the command output (especially the last line of the the syn2mas " -"output). If you are confident that the migration will work out as " -"expected, you can proceed with a [real migration](#performing-a-real-" -"syn2mas-migration)." +msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:387 @@ -887,37 +523,23 @@ msgid "you've performed a Postgres backup, just in case" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:395 -msgid "" -"you're aware of the irreversibility of the migration process without " -"disruption after users have created new login sessions via the new MAS " -"setup" +msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:397 -msgid "" -"you've [configured syn2mas](#configuring-syn2mas), especially if you've " -"used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse" -"--openid-connect-for-single-sign-on)" +msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:399 -msgid "" -"you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and " -"don't see any issues in its output" +msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:401 -msgid "" -"To perform a real migration, run the `matrix-authentication-service-" -"syn2mas` tag **without** the " -"`matrix_authentication_service_syn2mas_dry_run` variable:" +msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:407 -msgid "" -"Having performed a `syn2mas` migration once, trying to do it again will " -"report errors for users that were already migrated (e.g. \"Error: Unknown" -" upstream provider oauth-delegated\")." +msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:409 @@ -925,11 +547,7 @@ msgid "Verify that Matrix Authentication Service is installed correctly" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:411 -msgid "" -"After [installation](#installing), run the `doctor` subcommand of the " -"[`mas-cli` command-line tool](https://element-hq.github.io/matrix-" -"authentication-service/reference/cli/index.html) to verify that MAS is " -"installed correctly." +msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:413 @@ -937,16 +555,11 @@ msgid "You can do it:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:415 -msgid "" -"either via the Ansible playbook's `matrix-authentication-service-mas-cli-" -"doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" +msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:417 -msgid "" -"or by running the `mas-cli` script on the server (which invokes the `mas-" -"cli` tool inside a container): `/matrix/matrix-authentication-service/bin" -"/mas-cli doctor`" +msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:419 @@ -958,11 +571,7 @@ msgid "Management" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:433 -msgid "" -"You can use the [`mas-cli` command-line tool](https://element-" -"hq.github.io/matrix-authentication-service/reference/cli/index.html) " -"(exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` " -"script) to perform administrative tasks against MAS." +msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:435 @@ -970,24 +579,15 @@ msgid "This documentation page already mentions:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:437 -msgid "" -"the `mas-cli doctor` sub-command in the [Verify that Matrix " -"Authentication Service is installed correctly](#verify-that-matrix-" -"authentication-service-is-installed-correctly) section, which you can run" -" via the CLI and via the Ansible playbook's `matrix-authentication-" -"service-mas-cli-doctor` tag" +msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:439 -msgid "" -"the `mas-cli manage register-user` sub-command in the [Registering users" -"](./registering-users.md) documentation" +msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:441 -msgid "" -"There are other sub-commands available. Run `/matrix/matrix-" -"authentication-service/bin/mas-cli` to get an overview." +msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:443 @@ -995,17 +595,11 @@ msgid "User registration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:445 -msgid "" -"After Matrix Authentication Service is [installed](#installing), users " -"need to be managed there (unless you're managing them in an [upstream " -"OAuth2 provider](#upstream-oauth2-configuration))." +msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:447 -msgid "" -"You can register users new users as described in the [Registering users" -"](./registering-users.md) documentation (via `mas-cli manage register-" -"user` or the Ansible playbook's `register-user` tag)." +msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:449 @@ -1013,33 +607,17 @@ msgid "Working around email deliverability issues" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:451 -msgid "" -"Because Matrix Authentication Service [still insists](https://github.com" -"/element-hq/matrix-authentication-service/issues/1505) on having a " -"verified email address for each user, you may need to work around email " -"deliverability issues if [your email-sending configuration" -"](./configuring-playbook-email.md) is not working." +msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:453 -msgid "" -"Matrix Authentication Service attempts to verify email addresses by " -"sending a verification email to the address specified by the user " -"whenever they log in to an account without a verified email address." +msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:455 -msgid "" -"If email delivery is not working, **you can retrieve the email " -"configuration code from the Matrix Authentication Service's logs** " -"(`journalctl -fu matrix-authentication-service`)." +msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:457 -msgid "" -"Alternatively, you can use the [`mas-cli` management tool](#management) " -"to manually verify email addresses for users. Example: `/matrix/matrix-" -"authentication-service/bin/mas-cli manage verify-email some.username " -"email@example.com`" +msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po index 76289ff29..45f650bac 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 @@ -26,49 +26,31 @@ msgid "Setting up Matrix Corporal (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:5 -msgid "" -"**WARNING**: This is an advanced feature! It requires prior experience " -"with Matrix and a specific need for using [Matrix " -"Corporal](https://github.com/devture/matrix-corporal). If you're unsure " -"whether you have such a need, you most likely don't." +msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:9 -msgid "" -"The playbook can install and configure [matrix-" -"corporal](https://github.com/devture/matrix-corporal) for you." +msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:11 -msgid "" -"In short, it's a sort of automation and firewalling service, which is " -"helpful if you're instaling Matrix services in a controlled corporate " -"environment." +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:13 -msgid "" -"See the project's [documentation](https://github.com/devture/matrix-" -"corporal/blob/main/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:15 -msgid "" -"If you decide that you'd like to let this playbook install it for you, " -"you'd need to also:" +msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:16 -msgid "" -"(required) [set up the Shared Secret Auth password provider module" -"](configuring-playbook-shared-secret-auth.md)" +msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:17 -msgid "" -"(optional, but encouraged) [set up the REST authentication password " -"provider module](configuring-playbook-rest-auth.md)" +msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:19 @@ -76,36 +58,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:74 -msgid "" -"Matrix Corporal operates with a specific Matrix user on your server. By " -"default, it's `matrix-corporal` (controllable by the " -"`matrix_corporal_reconciliation_user_id_local_part` setting, see above)." +msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:76 -msgid "" -"No matter what Matrix user ID you configure to run it with, make sure " -"that:" +msgid "No matter what Matrix user ID you configure to run it with, make sure that:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:78 -msgid "" -"the Matrix Corporal user is created by [registering it](registering-" -"users.md) **with administrator privileges**. Use a password you remember," -" as you'll need to log in from time to time to create or join rooms" +msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:80 -msgid "" -"the Matrix Corporal user is joined and has Admin/Moderator-level access " -"to any rooms you want it to manage" +msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:82 @@ -113,17 +82,11 @@ msgid "Using a locally-stored static policy" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:84 -msgid "" -"If you'd like to use a [static policy file](https://github.com/devture" -"/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-" -"style-policy-provider), you can use a configuration like this:" +msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:116 -msgid "" -"To learn more about what the policy configuration, see the matrix-" -"corporal documentation on [policy](https://github.com/devture/matrix-" -"corporal/blob/master/docs/policy.md)." +msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:118 @@ -131,25 +94,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:120 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:127 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-aux-files,setup-corporal,start` or `just " -"setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:129 -msgid "" -"`just run-tags setup-aux-files,setup-corporal,start` is useful for " -"maintaining your setup quickly when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"`just setup-all` runs the `ensure-matrix-users-created` tag too." +msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:131 @@ -157,9 +110,7 @@ msgid "Matrix Corporal files" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:133 -msgid "" -"The following local filesystem paths are mounted in the `matrix-corporal`" -" container and can be used in your configuration (or policy):" +msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:135 @@ -167,35 +118,13 @@ msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:137 -msgid "" -"`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " -"write)" +msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:139 -msgid "" -"`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" -" and write)" +msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:141 -msgid "" -"As an example: you can create your own configuration files in " -"`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " -"in the Docker container. Your configuration (stuff in " -"`matrix_corporal_policy_provider_config`) needs to refer to these files " -"via the local container paths - `/etc/matrix-corporal` (read-only), `/var" -"/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read " -"and write)." +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 "" - -#~ 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. See that project's documentation" -#~ " to learn what it does and why" -#~ " it might be useful to you." -#~ 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 690380370..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 @@ -26,10 +26,7 @@ msgid "Setting up matrix-ldap-registration-proxy (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 -msgid "" -"The playbook can install and configure [matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" for you." +msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 @@ -37,10 +34,7 @@ msgid "This proxy handles Matrix registration requests and forwards them to LDAP msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 -msgid "" -"**Note**: This does support the full Matrix specification for " -"registrations. It only provide a very coarse implementation of a basic " -"password registration." +msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration." msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 @@ -48,18 +42,11 @@ msgid "Quickstart" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 -msgid "" -"If you already use the [synapse external password provider via LDAP" -"](configuring-playbook-ldap-auth.md) (that is, you have " -"`matrix_synapse_ext_password_provider_ldap_enabled: true` and other " -"options in your configuration) you can use the following values as " -"configuration:" +msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 @@ -67,24 +54,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po index 48e5a091b..a3d6a1636 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 @@ -26,28 +26,15 @@ msgid "Storing Matrix media files using matrix-media-repo (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:3 -msgid "" -"[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often " -"abbreviated \"MMR\") is a highly customizable multi-domain media " -"repository for Matrix. Intended for medium to large environments " -"consisting of several homeservers, this media repo de-duplicates media " -"(including remote media) while being fully compliant with the " -"specification." +msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:5 -msgid "" -"Smaller/individual homeservers can still make use of this project's " -"features, though it may be difficult to set up or have higher than " -"expected resource consumption. Please do your research before deploying " -"this as this project may not be useful for your environment." +msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:7 -msgid "" -"For a simpler alternative (which allows you to offload your media " -"repository storage to S3, etc.), you can [configure S3 storage" -"](configuring-playbook-s3.md) instead of setting up matrix-media-repo." +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 @@ -63,9 +50,7 @@ msgid "[Additional configuration options](#configuring-the-media-repo)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md -msgid "" -"[Importing data from an existing media store](#importing-data-from-an-" -"existing-media-store)" +msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:15 @@ -73,27 +58,15 @@ msgid "Quickstart" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:17 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the " -"installation process](./installing.md) for the playbook:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:26 -msgid "" -"The repo is pre-configured for integrating with the Postgres database, " -"Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-" -"grafana.md) (if metrics enabled) from this playbook for all the available" -" homeserver roles. When the media repo is enabled, other media store " -"roles should be disabled (if using Synapse with other media store roles)." +msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:28 -msgid "" -"By default, the media-repo will use the local filesystem for data " -"storage. You can alternatively use a `s3` cloud backend as well. Access " -"token caching is also enabled by default since the logout endpoints are " -"proxied through the media repo." +msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:30 @@ -105,12 +78,7 @@ msgid "Additional common configuration options:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:91 -msgid "" -"Full list of configuration options with documentation can be found in " -"[`roles/custom/matrix-media-" -"repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/master/roles/custom/matrix-media-" -"repo/defaults/main.yml)" +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:93 @@ -118,33 +86,19 @@ msgid "Signing Keys" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:95 -msgid "" -"Authenticated media endpoints ([MSC3916](https://github.com/matrix-org" -"/matrix-spec-proposals/pull/3916)) requires MMR to have a configured " -"signing key to authorize outbound federation requests. Additionally, the " -"signing key must be merged with your homeserver's signing key file." +msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:97 -msgid "" -"The playbook default is to generate a MMR signing key when invoking the " -"setup role and merge it with your homeserver if you are using Synapse or " -"Dendrite. This can be disabled if desired by setting the option in your " -"inventory:" +msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:103 -msgid "" -"If you wish to manually generate the signing key and merge it with your " -"homeserver's signing key file, see https://docs.t2bot.io/matrix-media-" -"repo/v1.3.5/installation/signing-key/ for more details." +msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:105 -msgid "" -"**Note that if you uninstall MMR from the playbook, it will not remove " -"the old MMR signing key from your homeserver's signing key file. You will" -" have to remove it manually.**" +msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:107 @@ -152,20 +106,11 @@ msgid "Key backup and revoking" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:109 -msgid "" -"Since your homeserver signing key file is modified by the playbook, a " -"backup will be created in " -"`HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to " -"remove/revoke old keys, you can restore from this backup or remove the " -"MMR key ID from your `example.com.signing.key` file." +msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:111 -msgid "" -"Additionally, its recommended after revoking a signing key to update your" -" homeserver config file (`old_signing_keys` field for Synapse and " -"`old_private_keys` for Dendrite). See your homeserver config file for " -"further documentation on how to populate the field." +msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:113 @@ -173,25 +118,15 @@ msgid "Importing data from an existing media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:115 -msgid "" -"If you want to add this repo to an existing homeserver managed by the " -"playbook, you will need to import existing media into MMR's database or " -"you will lose access to older media while it is active. MMR versions up " -"to `v1.3.3` only support importing from Synapse, but newer versions (at " -"time of writing: only `latest`) also support importing from Dendrite." +msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:117 -msgid "" -"**Before importing**: ensure you have an initial matrix-media-repo " -"deployment by following the [quickstart](#quickstart) guide above" +msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:119 -msgid "" -"Depending on the homeserver implementation yu're using (Synapse, " -"Dendrite), you'll need to use a different import tool (part of matrix-" -"media-repo) and point it to the homeserver's database." +msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:121 @@ -199,40 +134,26 @@ msgid "Importing data from the Synapse media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:123 -msgid "" -"To import the Synapse media store, you're supposed to invoke the " -"`import_synapse` tool which is part of the matrix-media-repo container " -"image. Your Synapse database is called `synapse` by default, unless " -"you've changed it by modifying `matrix_synapse_database_database`." +msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:125 -msgid "" -"This guide here is adapted from the [upstream documentation about the " -"import_synapse script](https://github.com/turt2live/matrix-media-repo" -"#importing-media-from-synapse)." +msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:127 #: ../../../docs/configuring-playbook-matrix-media-repo.md:149 -msgid "" -"Run the following command on the server (after replacing " -"`postgres_connection_password` in it with the value found in your " -"`vars.yml` file):" +msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:139 #: ../../../docs/configuring-playbook-matrix-media-repo.md:161 -msgid "" -"Enter `1` for the Machine ID when prompted (you are not doing any " -"horizontal scaling) unless you know what you're doing." +msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:141 #: ../../../docs/configuring-playbook-matrix-media-repo.md:163 -msgid "" -"This should output a `msg=\"Import completed\"` when finished " -"successfully!" +msgid "This should output a `msg=\"Import completed\"` when finished successfully!" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:143 @@ -240,18 +161,9 @@ msgid "Importing data from the Dendrite media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:145 -msgid "" -"If you're using the [Dendrite](configuring-playbook-dendrite.md) " -"homeserver instead of the default for this playbook (Synapse), follow " -"this importing guide here." +msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:147 -msgid "" -"To import the Dendrite media store, you're supposed to invoke the " -"`import_dendrite` tool which is part of the matrix-media-repo container " -"image. Your Dendrite database is called `dendrite_mediaapi` by default, " -"unless you've changed it by modifying " -"`matrix_dendrite_media_api_database`." +msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po index 480591f98..64f9e90c3 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 @@ -26,35 +26,23 @@ msgid "Setting up matrix-registration (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:3 -msgid "" -"The playbook can install and configure [matrix-" -"registration](https://github.com/ZerataX/matrix-registration) for you." +msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:5 -msgid "" -"**WARNING**: this is a poorly maintained and buggy project. It's better " -"to avoid using it." +msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:7 -msgid "" -"**WARNING**: this is not related to [matrix-registration-bot" -"](configuring-playbook-bot-matrix-registration-bot.md)" +msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:9 -msgid "" -"matrix-registration is a simple python application to have a token based " -"Matrix registration." +msgid "matrix-registration is a simple python application to have a token based Matrix registration." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:11 -msgid "" -"Use matrix-registration to **create unique registration links**, which " -"people can use to register on your Matrix server. It allows you to **keep" -" your server's registration closed (private)**, but still allow certain " -"people (these having a special link) to register a user account." +msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:13 @@ -62,17 +50,11 @@ msgid "**matrix-registration** provides 2 things:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:15 -msgid "" -"**an API for creating registration tokens** (unique registration links). " -"This API can be used via `curl` or via the playbook (see [Usage](#usage) " -"below)" +msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:17 -msgid "" -"**a user registration page**, where people can use these registration " -"tokens. By default, exposed at `https://matrix.example.com/matrix-" -"registration`" +msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:19 @@ -80,9 +62,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:21 -msgid "" -"To enable matrix-registration, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:30 @@ -90,26 +70,15 @@ msgid "Adjusting the matrix-registration URL" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:32 -msgid "" -"By default, this playbook installs the matrix-registration on the " -"`matrix.` subdomain, at the `/matrix-registration` path " -"(https://matrix.example.com/matrix-registration). This makes it easy to " -"install it, because it **doesn't require additional DNS records to be set" -" up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:34 -msgid "" -"By tweaking the `matrix_registration_hostname` and " -"`matrix_registration_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:36 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:44 @@ -117,10 +86,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:46 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the matrix-registration domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:48 @@ -128,9 +94,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:50 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:52 @@ -138,26 +102,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:54 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:65 @@ -165,17 +118,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:67 -msgid "" -"**matrix-registration** gets exposed at `https://matrix.example.com" -"/matrix-registration`" +msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:69 -msgid "" -"It provides various [APIs](https://github.com/ZerataX/matrix-" -"registration/wiki/api) - for creating registration tokens, listing " -"tokens, disabling tokens, etc. To make use of all of its capabilities, " -"consider using `curl`." +msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:71 @@ -191,16 +138,11 @@ msgid "To **create a new user registration token (link)**, use this command:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:83 -msgid "" -"The above command creates and returns a **one-time use** token, which " -"**expires** on the 31st of December 2021. Adjust the `one_time` and " -"`ex_date` variables as you see fit." +msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:85 -msgid "" -"Share the unique registration link (generated by the command above) with " -"users to let them register on your Matrix server." +msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:87 @@ -212,8 +154,5 @@ msgid "To **list the existing user registration tokens**, use this command:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:96 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags list-matrix-registration-tokens`" +msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po index b8b8158f3..3435536f2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po @@ -26,18 +26,11 @@ msgid "Setting up a Generic Mautrix Bridge (optional)" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:3 -msgid "" -"The playbook can install and configure various " -"[mautrix](https://github.com/mautrix) bridges (twitter, facebook, " -"instagram, signal, hangouts, googlechat, etc.), as well as many other " -"(non-mautrix) bridges. This is a common guide for configuring mautrix " -"bridges." +msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:5 -msgid "" -"You can see each bridge's features at in the `ROADMAP.md` file in its " -"corresponding [mautrix](https://github.com/mautrix) repository." +msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:7 @@ -45,34 +38,19 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:16 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue. Each bridge may have additional requirements " -"besides `_enabled: true`. For example, the mautrix-telegram bridge (our " -"documentation page about it is [here](configuring-playbook-bridge-" -"mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and " -"`matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each" -" bridge's individual documentation page for details about enabling " -"bridges." +msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:18 -msgid "" -"To **configure a user as an administrator for all bridges**, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:24 -msgid "" -"**Alternatively** (more verbose, but allows multiple admins to be " -"configured), you can do the same on a per-bridge basis with:" +msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:33 @@ -80,10 +58,7 @@ msgid "encryption" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:35 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:37 @@ -100,10 +75,7 @@ msgid "relay mode" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:53 -msgid "" -"Relay mode is off by default. If you would like to enable relay mode, add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:55 @@ -111,11 +83,7 @@ msgid "**for all bridges with relay mode support**:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:70 -msgid "" -"You can only have one " -"`matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in " -"`vars.yml` per bridge, so if you need multiple pieces of configuration " -"there, just merge them like this:" +msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:82 @@ -131,11 +99,7 @@ msgid "Discovering additional configuration options" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:92 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-SERVICENAME/defaults/main.yml` to find other things you would " -"like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:94 @@ -143,9 +107,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:96 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:103 @@ -153,24 +115,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:105 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:107 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:109 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:111 @@ -178,24 +131,15 @@ msgid "Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:113 -msgid "" -"To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-" -"puppeting.html) enable the [Appservice Double Puppet](configuring-" -"playbook-appservice-double-puppet.md) service for this playbook." +msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:115 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) is configured and enabled " -"on the server for this playbook by adding" +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:121 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:123 @@ -203,16 +147,11 @@ msgid "Controlling the logging level" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:129 -msgid "" -"to `vars.yml` to control the logging level, where you may replace WARN " -"with one of the following to control the verbosity of the logs generated:" -" TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." +msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:131 -msgid "" -"If you have issues with a service, and are requesting support, the higher" -" levels of logging will generally be more helpful." +msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:133 @@ -220,24 +159,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:135 -msgid "" -"To use the bridge, you need to start a chat with " -"`@SERVICENAMEbot:example.com` (where `example.com` is your base domain, " -"not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:137 -msgid "" -"Send `login` to the bridge bot to get started. You can learn more here " -"about authentication from the bridge's official documentation on " -"Authentication: " -"https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" +msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:139 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:141 @@ -245,16 +175,9 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:143 -msgid "" -"For troubleshooting information with a specific bridge, please see the " -"playbook documentation about it (some other document in in `docs/`) and " -"the upstream ([mautrix](https://github.com/mautrix)) bridge documentation" -" for that specific bridge." +msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:145 -msgid "" -"Reporting bridge bugs should happen upstream, in the corresponding " -"mautrix repository, not to us." +msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po index 02dafa0c1..db6c60afb 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po @@ -28,4 +28,3 @@ msgstr "" #: ../../../docs/configuring-playbook-nginx.md:3 msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po index 82b3ac0b0..daed6d5af 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -26,33 +26,19 @@ msgid "Setting up the ntfy push notifications server (optional)" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:3 -msgid "" -"The playbook can install and configure the [ntfy](https://ntfy.sh/) push " -"notifications server for you." +msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:5 -msgid "" -"Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables " -"self-hosted (Google-free) push notifications from Matrix (and other) " -"servers to UnifiedPush-compatible Matrix compatible client apps running " -"on Android and other devices." +msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:7 -msgid "" -"This role is intended to support UnifiedPush notifications for use with " -"the Matrix and Matrix-related services that this playbook installs. This " -"role is not intended to support all of ntfy's other features." +msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:9 -msgid "" -"**Note**: In contrast to push notifications using Google's FCM or Apple's" -" APNs, the use of UnifiedPush allows each end-user to choose the push " -"notification server that they prefer. As a consequence, deploying this " -"ntfy server does not by itself ensure any particular user or device or " -"client app will use it." +msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:11 @@ -60,23 +46,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:13 -msgid "" -"To enable ntfy, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:27 -msgid "" -"For a more complete list of variables that you could override, see the " -"[`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting" -"/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:29 -msgid "" -"For a complete list of ntfy config options that you could put in " -"`ntfy_configuration_extension_yaml`, see the [ntfy config " -"documentation](https://ntfy.sh/docs/config/#config-options)." +msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:31 @@ -84,22 +62,15 @@ msgid "Adjusting the ntfy URL" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:33 -msgid "" -"By default, this playbook installs ntfy on the `ntfy.` subdomain " -"(`ntfy.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:35 -msgid "" -"By tweaking the `ntfy_hostname` variable, you can easily make the service" -" available at a **different hostname** than the default one." +msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:37 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:44 @@ -107,15 +78,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:46 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the ntfy domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:48 -msgid "" -"By default, you will need to create a CNAME record for `ntfy`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:50 @@ -123,26 +90,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:52 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:59 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:61 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:63 @@ -150,9 +106,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:65 -msgid "" -"To make use of your ntfy installation, on Android for example, you need " -"two things:" +msgid "To make use of your ntfy installation, on Android for example, you need two things:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:67 @@ -164,11 +118,7 @@ msgid "a UnifiedPush-compatible Matrix app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:70 -msgid "" -"You need to install the `ntfy` app on each device on which you want to " -"receive push notifications through your ntfy server. The `ntfy` app will " -"provide UnifiedPush notifications to any number of UnifiedPush-compatible" -" messaging apps installed on the same device." +msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:72 @@ -176,15 +126,11 @@ msgid "Setting up the `ntfy` Android app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:74 -msgid "" -"Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) " -"from F-droid or Google Play." +msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:75 -msgid "" -"In its Settings -> `General: Default server`, enter your ntfy server URL," -" such as `https://ntfy.example.com`." +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 @@ -192,11 +138,7 @@ 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." +msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:80 @@ -204,11 +146,7 @@ msgid "Setting up a UnifiedPush-compatible Matrix app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:82 -msgid "" -"Install any UnifiedPush-enabled Matrix app on that same device. The " -"Matrix app will learn from the `ntfy` app that you have configured " -"UnifiedPush on this device, and then it will tell your Matrix server to " -"use it." +msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:84 @@ -228,23 +166,15 @@ msgid "SchildiChat-android:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:90 -msgid "" -"enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push " -"gateway`." +msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:91 -msgid "" -"choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push " -"distributor`. *(For info, a more complex alternative to achieve the same " -"is: delete the relevant unifiedpush registration in `ntfy` app, force-" -"close SchildiChat, re-open it.)*" +msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:92 -msgid "" -"verify `Settings` -> `Notifications` -> `UnifiedPush: Notification " -"targets` as described below in the \"Troubleshooting\" section." +msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:94 @@ -256,21 +186,15 @@ msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:96 -msgid "" -"verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification " -"settings`" +msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:98 -msgid "" -"If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", " -"then choose \"ntfy\"." +msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:100 -msgid "" -"If the Matrix app doesn't seem to pick it up, try restarting it and try " -"the Troubleshooting section below." +msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:102 @@ -278,20 +202,11 @@ msgid "Web App" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:104 -msgid "" -"ntfy also has a web app to subscribe to and push to topics from the " -"browser. This may be helpful to further troubleshoot UnifiedPush problems" -" or to use ntfy for other purposes. The web app only runs in the browser " -"locally (after downloading the JavaScript)." +msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:106 -msgid "" -"The web app is disabled in this playbook by default as the expectation is" -" that most users won't use it. You can either use the [official hosted " -"one](https://ntfy.sh/app) (it supports using other public reachable ntfy " -"instances) or host it yourself by setting `ntfy_web_root: \"app\"` and " -"re-running Ansible." +msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:108 @@ -299,57 +214,25 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:110 -msgid "" -"First check that the Matrix client app you are using supports " -"UnifiedPush. There may well be different variants of the app." +msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:112 -msgid "" -"Set the ntfy server's log level to 'DEBUG', as shown in the example " -"settings above, and watch the server's logs with `sudo journalctl -fu " -"matrix-ntfy`." +msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:114 -msgid "" -"To check if UnifiedPush is correctly configured on the client device, " -"look at \"Settings -> Notifications -> Notification Targets\" in Element " -"Android or SchildiChat Android, or \"Settings -> Notifications -> " -"Devices\" in FluffyChat. There should be one entry for each Matrix client" -" app that has enabled push notifications, and when that client is using " -"UnifiedPush you should see a URL that begins with your ntfy server's URL." +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." +msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:118 -msgid "" -"If it is not working, useful tools are \"Settings -> Notifications -> Re-" -"register push distributor\" and \"Settings -> Notifications -> " -"Troubleshoot Notifications\" in SchildiChat Android (possibly also " -"Element Android). In particular the \"Endpoint/FCM\" step of that " -"troubleshooter should display your ntfy server's URL that it has " -"discovered from the ntfy client app." +msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:120 -msgid "" -"The simple [UnifiedPush " -"troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-" -"Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be" -" used to manually test UnifiedPush registration and operation on an " -"Android device." +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 a4c8b4f62..f84aa080d 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 @@ -22,16 +22,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-own-webserver.md:1 -msgid "" -"Using your own webserver, instead of this playbook's Traefik reverse-" -"proxy (optional, advanced)" +msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:3 -msgid "" -"By default, this playbook installs its own [Traefik](https://traefik.io/)" -" reverse-proxy server (in a Docker container) which listens on ports 80 " -"and 443. If that's okay, you can skip this document." +msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:5 @@ -39,24 +34,15 @@ msgid "Traefik" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:7 -msgid "" -"[Traefik](https://traefik.io/) is the default reverse-proxy for the " -"playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 " -"purposes**:" +msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:9 -msgid "" -"serving public traffic and providing SSL-termination with certificates " -"obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting " -"SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." +msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:11 -msgid "" -"assists internal communication between addon services (briges, bots, " -"etc.) and the homeserver via an internal entrypoint (`matrix-internal-" -"matrix-client-api`)." +msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:13 @@ -68,10 +54,7 @@ msgid "Traefik managed by the playbook" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:17 -msgid "" -"To have the playbook install and use Traefik, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:25 @@ -83,15 +66,11 @@ msgid "Traefik managed by you" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:53 -msgid "" -"In this mode all roles will still have Traefik labels attached. You will," -" however, need to configure your Traefik instance and its entrypoints." +msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:55 -msgid "" -"By default, the playbook configured a `default` certificate resolver and " -"multiple entrypoints." +msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:57 @@ -103,42 +82,27 @@ msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:60 -msgid "" -"`web-secure` (TCP port `443`) - used for exposing the Matrix Client-" -"Server API and all other services" +msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:61 -msgid "" -"`matrix-federation` (TCP port `8448`) - used for exposing the Matrix " -"Federation API" +msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:62 -msgid "" -"`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally " -"for addon services (bridges, bots) to communicate with the homserver" +msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:64 -msgid "" -"Below is some configuration for running Traefik yourself, although we " -"recommend using [Traefik managed by the playbook](#traefik-managed-by-" -"the-playbook)." +msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:66 -msgid "" -"Note that this configuration on its own does **not** redirect traffic on " -"port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing " -"this in Traefik, it can be added to Traefik in a [file " -"provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" +msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:86 -msgid "" -"You can use the following `docker-compose.yml` as example to launch " -"Traefik." +msgid "You can use the following `docker-compose.yml` as example to launch Traefik." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:122 @@ -158,22 +122,11 @@ msgid "There are 2 ways to go about it:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:130 -msgid "" -"(recommended) [Fronting the integrated reverse-proxy webserver with " -"another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-" -"with-another-reverse-proxy) - using the playbook-managed reverse-proxy " -"(Traefik), but disabling SSL termination for it, exposing this reverse-" -"proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding " -"traffic from your own webserver to those few ports" +msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:132 -msgid "" -"(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-" -"reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed " -"reverse-proxy (Traefik), exposing services one by one using " -"`_host_bind_port` variables and forwarding traffic from your own " -"webserver to those ports" +msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:134 @@ -181,57 +134,31 @@ msgid "Fronting the integrated reverse-proxy webserver with another reverse-prox msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:136 -msgid "" -"This method is about leaving the integrated reverse-proxy webserver be, " -"but making it not get in the way (using up important ports, trying to " -"retrieve SSL certificates, etc.)." +msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:138 -msgid "" -"If you wish to use another webserver, the integrated reverse-proxy " -"webserver usually gets in the way because it attempts to fetch SSL " -"certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is" -" enabled)." +msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:140 -msgid "" -"You can disable such behavior and make the integrated reverse-proxy " -"webserver only serve traffic locally on the host itself (or over a local " -"network)." +msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:142 -msgid "" -"This is the recommended way for using another reverse-proxy, because the " -"integrated one would act as a black box and wire all Matrix services " -"correctly. You would then only need to reverse-proxy a few individual " -"domains and ports over to it." +msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:144 -msgid "" -"To front Traefik with another reverse-proxy, you would need some " -"configuration like this:" +msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:194 -msgid "" -"Such a configuration would expose all services on a local port `81` and " -"Matrix Federation on a local port `8449`. Your reverse-proxy " -"configuration needs to send traffic to these ports. [`examples/reverse-" -"proxies`](../examples/reverse-proxies/) contains examples for various " -"webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy " -"Manager." +msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:196 -msgid "" -"It's important that these webservers proxy-pass requests to the correct " -"`ip:port` and also set the `Host` HTTP header appropriately. If you don't" -" pass the `Host` header correctly, Traefik will return a `404 - not " -"found` error." +msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:198 @@ -251,42 +178,17 @@ msgid "Using no reverse-proxy on the Matrix side at all" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:204 -msgid "" -"Instead of [Fronting the integrated reverse-proxy webserver with another " -"reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-" -"another-reverse-proxy), you can also go another way -- completely " -"disabling the playbook-managed Traefik reverse-proxy. You would then need" -" to reverse-proxy from your own webserver directly to each individual " -"Matrix service." +msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:206 -msgid "" -"This is more difficult, as you would need to handle the configuration for" -" each service manually. Enabling additional services would come with " -"extra manual work you need to do." +msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:208 -msgid "" -"Also, the Traefik reverse-proxy, besides fronting everything is also " -"serving a 2nd purpose of allowing addons services to communicate with the" -" Matrix homeserver thanks to its `matrix-internal-matrix-client-api` " -"entrypoint (read more about it above). Disabling Traefik completely means" -" the playbook would wire services to directly talk to the homeserver. " -"This can work for basic setups, but not for more complex setups involving" -" [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), " -"[matrix-corporal](./configuring-playbook-matrix-corporal.md) or other " -"such services that need to \"steal routes\" from the homeserver." +msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:210 -msgid "" -"If your webserver is on the same machine, ensure your web server user " -"(something like `http`, `apache`, `www-data`, `nginx`) is part of the " -"`matrix` group. You should run something like this: `usermod -a -G matrix" -" nginx`. This allows your webserver user to access files owned by the " -"`matrix` group, so that it can serve static files from `/matrix/static-" -"files`." +msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po index d5a6e3ef0..b8e55d975 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -26,26 +26,15 @@ msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:3 -msgid "" -"The playbook can install and configure the " -"[pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy" -" daemon for you." +msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/pantalaimon/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:7 -msgid "" -"This role exposes Pantalaimon's API only within the container network, so" -" bots and clients installed on the same machine can use it. In particular" -" the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir" -"](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can " -"use it." +msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:9 @@ -53,17 +42,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:17 -msgid "" -"The default configuration should suffice. For advanced configuration, you" -" can override the variables documented in the role's " -"[defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." +msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:19 @@ -71,31 +54,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:21 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:28 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/pantalaimon) to learn what it" -#~ " does and why it might be " -#~ "useful to you." -#~ 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 30b6306eb..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 @@ -26,18 +26,11 @@ 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." +msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:5 -msgid "" -"For a more complete backup solution (one that includes not only Postgres," -" but also other configuration/data files), you may wish to look into " -"[BorgBackup](configuring-playbook-backup-borg.md) instead." +msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:7 @@ -45,15 +38,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:9 -msgid "" -"To enable Postgres backup, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:15 -msgid "" -"Refer to the table below for additional configuration variables and their" -" default values." +msgid "Refer to the table below for additional configuration variables and their default values." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md @@ -77,10 +66,7 @@ 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" +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 @@ -160,24 +146,13 @@ 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:" +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 0d4835959..45ed22103 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 @@ -22,16 +22,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-prometheus-grafana.md:1 -msgid "" -"Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server " -"(optional)" +msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:3 -msgid "" -"The playbook can install [Grafana](https://grafana.com/) with " -"[Prometheus](https://prometheus.io/) and configure performance metrics of" -" your homeserver with graphs for you." +msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:5 @@ -39,16 +34,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:7 -msgid "" -"To enable Grafana and/or Prometheus, add the following configuration to " -"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:33 -msgid "" -"The retention policy of Prometheus metrics is [15 days by " -"default](https://prometheus.io/docs/prometheus/latest/storage" -"/#operational-aspects). Older data gets deleted automatically." +msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:35 @@ -56,22 +46,15 @@ msgid "Adjusting the Grafana URL" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:37 -msgid "" -"By default, this playbook installs Grafana web user-interface on the " -"`stats.` subdomain (`stats.example.com`) and requires you to [adjust your" -" DNS records](#adjusting-dns-records)." +msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:39 -msgid "" -"By tweaking the `grafana_hostname` variable, you can easily make the " -"service available at a **different hostname** than the default one." +msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:41 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:48 @@ -79,21 +62,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:50 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the Grafana domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:52 -msgid "" -"By default, you will need to create a CNAME record for `stats`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:54 -msgid "" -"**Note**: It is possible to install Prometheus without installing " -"Grafana. This case it is not required to create the CNAME record." +msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:56 @@ -101,26 +78,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:58 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:65 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:67 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:69 @@ -140,9 +106,7 @@ msgid "`prometheus_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Prometheus](https://prometheus.io) is a time series database. It holds " -"all the data we're going to talk about." +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 @@ -150,10 +114,7 @@ msgid "`prometheus_node_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an " -"addon of sorts to Prometheus that collects generic system information " -"such as CPU, memory, filesystem, and even system temperatures" +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 @@ -161,9 +122,7 @@ msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an " -"addon of sorts to expose Postgres database metrics to Prometheus." +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 @@ -171,9 +130,7 @@ msgid "`matrix_prometheus_nginxlog_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an " -"addon of sorts to expose NGINX logs to Prometheus." +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 @@ -181,10 +138,7 @@ msgid "`grafana_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Grafana](https://grafana.com/) is the visual component. It shows (on the" -" `stats.example.com` subdomain) the dashboards with the graphs that we're" -" interested in" +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 @@ -192,11 +146,7 @@ msgid "`grafana_anonymous_access`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"By default you need to log in to see graphs. If you want to publicly " -"share your graphs (e.g. when asking for help in " -"[`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org))" -" you'll want to enable this option." +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 @@ -204,10 +154,7 @@ msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"By default Grafana creates a user with `admin` as the username and " -"password. If you feel this is insecure and you want to change it " -"beforehand, you can do that here" +msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:81 @@ -215,24 +162,11 @@ msgid "Security and privacy" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:83 -msgid "" -"Metrics and resulting graphs can contain a lot of information. This " -"includes system specs but also usage patterns. This applies especially to" -" small personal/family scale homeservers. Someone might be able to figure" -" out when you wake up and go to sleep by looking at the graphs over time." -" Think about this before enabling anonymous access. And you should really" -" not forget to change your Grafana password." +msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:85 -msgid "" -"Most of our docker containers run with limited system access, but the " -"`prometheus-node-exporter` has access to the host network stack and " -"(readonly) root filesystem. This is required to report on them. If you " -"don't like that, you can set `prometheus_node_exporter_enabled: false` " -"(which is actually the default). You will still get Synapse metrics with " -"this container disabled. Both of the dashboards will always be enabled, " -"so you can still look at historical data after disabling either source." +msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:87 @@ -240,37 +174,19 @@ msgid "Collecting metrics to an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:89 -msgid "" -"**If the integrated Prometheus server is enabled** (`prometheus_enabled: " -"true`), metrics are collected by it from each service via communication " -"that happens over the container network. Each service does not need to " -"expose its metrics \"publicly\"." +msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:91 -msgid "" -"When you'd like **to collect metrics from an external Prometheus " -"server**, you need to expose service metrics outside of the container " -"network." +msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:93 -msgid "" -"The playbook provides a single endpoint " -"(`https://matrix.example.com/metrics/*`), under which various services " -"may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics" -"/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on" -" this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To " -"protect access using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)," -" see `matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users` below." +msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:95 -msgid "" -"When using `matrix_metrics_exposure_enabled`, you don't need to expose " -"metrics for individual services one by one." +msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:97 @@ -282,12 +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/*`. 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." +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 @@ -295,13 +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). " -"When enabled, all endpoints beneath `/metrics` will be protected with the" -" same 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 @@ -309,11 +214,7 @@ msgid "`matrix_metrics_exposure_http_basic_auth_users`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to the Basic Authentication credentials (raw `htpasswd` file " -"content) used to protect `/metrics/*`. This htpasswd-file needs to be " -"generated with the `htpasswd` tool and can include multiple " -"username/password pairs." +msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -321,9 +222,7 @@ msgid "`matrix_synapse_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make Synapse expose metrics (locally, on the " -"container network)" +msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -331,20 +230,11 @@ msgid "`matrix_synapse_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose Synapse's metrics on " -"`https://matrix.example.com/metrics/synapse/main-process` and " -"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below" -"](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if" -" you're running a Synapse worker setup (`matrix_synapse_workers_enabled: " -"true`). To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the node (general system stats) exporter " -"(locally, on the container network)" +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 @@ -352,16 +242,11 @@ msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the node (general system stats) metrics on " -"`https://matrix.example.com/metrics/node-exporter`. To password-protect " -"the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the [Postgres exporter](configuring-" -"playbook-prometheus-postgres.md) (locally, on the container network)" +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 @@ -369,18 +254,11 @@ msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Postgres exporter](configuring-" -"playbook-prometheus-postgres.md) metrics on " -"`https://matrix.example.com/metrics/postgres-exporter`. To password-" -"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " -"above." +msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the [NGINX Log exporter](configuring-" -"playbook-prometheus-nginxlog.md) (locally, on the container network)" +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 @@ -388,9 +266,7 @@ msgid "`matrix_sliding_sync_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-" -"sync-proxy.md) expose metrics (locally, on the container network)" +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 @@ -398,11 +274,7 @@ msgid "`matrix_sliding_sync_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Sliding Sync](configuring-playbook-" -"sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics" -"/sliding-sync`. To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +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 @@ -410,9 +282,7 @@ msgid "`matrix_bridge_hookshot_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make [Hookshot](configuring-playbook-bridge-" -"hookshot.md) expose metrics (locally, on the container network)" +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 @@ -420,11 +290,7 @@ msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-" -"hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To" -" password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +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 @@ -432,13 +298,7 @@ msgid "`matrix_SERVICE_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Various other services/roles may provide similar `_metrics_enabled` and " -"`_metrics_proxying_enabled` variables for exposing their metrics. Refer " -"to each role for details. To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above or " -"`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users`" -" variables provided by each role." +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 @@ -446,9 +306,7 @@ msgid "`matrix_media_repo_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make media-repo expose metrics (locally, on the " -"container network)" +msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:118 @@ -456,23 +314,11 @@ msgid "Collecting Synapse worker metrics to an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:120 -msgid "" -"If you are using workers (`matrix_synapse_workers_enabled: true`) and " -"have enabled `matrix_synapse_metrics_proxying_enabled` as described " -"above, the playbook will also automatically expose all Synapse worker " -"threads' metrics to " -"`https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` " -"corresponds to the worker `id` as exemplified in " -"`matrix_synapse_workers_enabled_list`." +msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:122 -msgid "" -"The playbook also generates an exemplary config file " -"(`/matrix/synapse/external_prometheus.yml.template`) with all the correct" -" paths which you can copy to your Prometheus server and adapt to your " -"needs. Make sure to edit the specified `password_file` path and contents " -"and path to your `synapse-v2.rules`. It will look a bit like this:" +msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:150 @@ -480,34 +326,21 @@ msgid "More information" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:152 -msgid "" -"[Enabling synapse-usage-exporter for Synapse usage statistics" -"](configuring-playbook-synapse-usage-exporter.md)" +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:153 -msgid "" -"[Understanding Synapse Performance Issues Through Grafana Graphs](https" -"://element-" -"hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html)" -" at the Synapse Github Wiki" +msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:154 -msgid "" -"[The Prometheus scraping rules](https://github.com/element-" -"hq/synapse/tree/master/contrib/prometheus) (we use v2)" +msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:155 -msgid "" -"[The Synapse Grafana dashboard](https://github.com/element-" -"hq/synapse/tree/master/contrib/grafana)" +msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:156 -msgid "" -"[The Node Exporter dashboard](https://github.com/rfrail3/grafana-" -"dashboards) (for generic non-synapse performance graphs)" +msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po index 9e5ce7b60..9b64b1d1e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po @@ -26,45 +26,27 @@ msgid "Enabling metrics and graphs for NginX logs (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3 -msgid "" -"It can be useful to have some (visual) insight into " -"[nginx](https://nginx.org/) logs." +msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5 -msgid "" -"This adds [prometheus-nginxlog-exporter](https://github.com/martin-" -"helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." +msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7 -msgid "" -"It will collect access logs from various nginx reverse-proxies which may " -"be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if " -"Synapse workers are enabled) and will make them available at a " -"Prometheus-compatible `/metrics` endpoint." +msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9 -msgid "" -"**Note**: nginx is only used internally by this Ansible playbook. With " -"Traefik being our default reverse-proxy, collecting nginx metrics is less" -" relevant." +msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11 -msgid "" -"To make use of this, you need to install [Prometheus](./configuring-" -"playbook-prometheus-grafana.md) either via the playbook or externally. " -"When using an external Prometheus, configuration adjustments are " -"necessary - see [Save metrics on an external Prometheus server](#save-" -"metrics-on-an-external-prometheus-server)." +msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13 -msgid "" -"If your setup includes [Grafana](./configuring-playbook-prometheus-" -"grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." +msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15 @@ -72,9 +54,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23 @@ -82,25 +62,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:36 @@ -108,11 +78,7 @@ msgid "Docker Image Compatibility" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38 -msgid "" -"At the moment of writing only images for `amd64` and `arm64` " -"architectures are available. The playbook currently does not support " -"[self-building](./self-building.md) a container image on other " -"architectures. You can however use a custom-build image by setting:" +msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45 @@ -120,13 +86,7 @@ msgid "Security and privacy" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47 -msgid "" -"Metrics and resulting graphs can contain a lot of information. NginX logs" -" contain information like IP address, URLs, UserAgents and more. This " -"information can reveal usage patterns and could be considered Personally " -"Identifiable Information (PII). Think about this before enabling " -"(anonymous) access. Please make sure you change the default Grafana " -"password." +msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49 @@ -134,44 +94,21 @@ msgid "Save metrics on an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51 -msgid "" -"The playbook will automatically integrate the metrics into the " -"[Prometheus](./configuring-playbook-prometheus-grafana.md) server " -"provided with this playbook (if enabled). In such cases, the metrics " -"endpoint is not exposed publicly - it's only available on the container " -"network." +msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53 -msgid "" -"When using an external Prometheus server, you'll need to expose metrics " -"publicly. See [Collecting metrics to an external Prometheus server" -"](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" -"external-prometheus-server)." +msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55 -msgid "" -"You can either use " -"`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to " -"expose just this one service, or `matrix_metrics_exposure_enabled: true` " -"to expose all services." +msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57 -msgid "" -"Whichever way you go with, this service will expose its metrics endpoint " -"**without password-protection** at " -"`https://matrix.example.com/metrics/nginxlog` by default." +msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59 -msgid "" -"For password-protection, use " -"(`matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users`) or " -"(`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled`" -" and " -"`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." +msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po index ecf92c21c..f0e689f1a 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po @@ -26,12 +26,7 @@ msgid "Enabling metrics and graphs for Postgres (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:3 -msgid "" -"Expanding on the metrics exposed by the [synapse exporter and the node " -"exporter](configuring-playbook-prometheus-grafana.md), the playbook " -"enables the [postgres exporter](https://github.com/prometheus-" -"community/postgres_exporter) that exposes more detailed information about" -" what's happening on your postgres database." +msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:5 @@ -39,9 +34,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:7 -msgid "" -"To enable the postgres exporter, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:13 @@ -49,25 +42,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:15 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:22 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:24 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:26 @@ -87,11 +70,7 @@ msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"Enable the postgres prometheus exporter. This sets up the docker " -"container, connects it to the database and adds a 'job' to the prometheus" -" config which tells prometheus about this new exporter. The default is " -"'false'" +msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -99,9 +78,7 @@ msgid "`prometheus_postgres_exporter_database_username`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"The 'username' for the user that the exporter uses to connect to the " -"database. The default is 'matrix_prometheus_postgres_exporter'" +msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -109,9 +86,7 @@ msgid "`prometheus_postgres_exporter_database_password`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"The 'password' for the user that the exporter uses to connect to the " -"database. By default, this is auto-generated by the playbook" +msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -119,13 +94,7 @@ msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"If set to `true`, exposes the Postgres exporter metrics on " -"`https://matrix.example.com/metrics/postgres-exporter` for usage with an " -"[external Prometheus server](configuring-playbook-prometheus-grafana.md" -"#collecting-metrics-to-an-external-prometheus-server). To password-" -"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " -"on that other documentation page." +msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:35 @@ -133,8 +102,5 @@ msgid "More information" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:37 -msgid "" -"[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) " -"(generic postgres dashboard)" +msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po index 799ecb51f..f9ff03223 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -26,15 +26,11 @@ msgid "Setting up the rageshake bug report server (optional)" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:3 -msgid "" -"The playbook can install and configure the [rageshake](https://github.com" -"/matrix-org/rageshake) bug report server for you." +msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:5 -msgid "" -"This is useful if you're developing your own applications and would like " -"to collect bug reports for them." +msgid "This is useful if you're developing your own applications and would like to collect bug reports for them." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:7 @@ -42,23 +38,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:9 -msgid "" -"To enable rageshake, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:15 -msgid "" -"rageshake has various options which don't have dedicated Ansible " -"variables. You can see the full list of options in the " -"[`rageshake.sample.yaml` file](https://github.com/matrix-" -"org/rageshake/blob/master/rageshake.sample.yaml)." +msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:17 -msgid "" -"To set these, you can make use of the " -"`matrix_rageshake_configuration_extension_yaml` variable like this:" +msgid "To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:27 @@ -66,23 +54,15 @@ msgid "Adjusting the rageshake URL" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:29 -msgid "" -"By default, this playbook installs rageshake on the `rageshake.` " -"subdomain (`rageshake.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:31 -msgid "" -"By tweaking the `matrix_rageshake_hostname` and " -"`matrix_rageshake_path_prefix` variables, you can easily make the service" -" available at a **different hostname and/or path** than the default one." +msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:33 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:44 @@ -90,21 +70,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:46 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the rageshake domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:48 -msgid "" -"By default, you will need to create a CNAME record for `rageshake`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:50 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:52 @@ -112,26 +86,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:54 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:65 @@ -139,8 +102,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:67 -msgid "" -"Refer to the [rageshake documentation](https://github.com/matrix-" -"org/rageshake) for available APIs, etc." +msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po index 50a5e7e41..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 @@ -18,23 +18,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-rest-auth.md:1 -msgid "" -"Setting up the REST authentication password provider module (optional, " -"advanced)" +msgid "Setting up the REST authentication password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:3 -msgid "" -"The playbook can install and configure [matrix-synapse-rest-" -"auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) " -"for you." +msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/ma1uta/matrix-" -"synapse-rest-password-provider/blob/master/README.md) to learn what it " -"does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:7 @@ -42,10 +34,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:9 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:19 @@ -53,10 +42,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:21 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:27 @@ -64,30 +50,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:29 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po index 20d1e3915..ea4db761c 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po @@ -26,29 +26,19 @@ msgid "Configuring Riot-web (optional)" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:3 -msgid "" -"By default, this playbook **used to install** the [Riot-" -"web](https://github.com/element-hq/riot-web) Matrix client web " -"application." +msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:5 -msgid "" -"Riot has since been [renamed to Element](https://element.io/blog/welcome-" -"to-element/)." +msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:7 -msgid "" -"to learn more about Element Web and its configuration, see our dedicated " -"[Configuring Element Web](configuring-playbook-client-element-web.md) " -"documentation page" +msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:8 -msgid "" -"to learn how to migrate from Riot to Element Web, see [Migrating to " -"Element Web](#migrating-to-element-web) below" +msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:10 @@ -60,17 +50,11 @@ msgid "Migrating your custom settings" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:14 -msgid "" -"If you have custom `matrix_riot_web_` variables in your " -"`inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to " -"rename them (`matrix_riot_web_` -> `matrix_client_element_`)." +msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:16 -msgid "" -"Some other playbook variables (but not all) with `riot` in their name are" -" also renamed. The playbook checks and warns if you are using the old " -"name for some commonly used ones." +msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:18 @@ -78,9 +62,7 @@ msgid "Domain migration" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:20 -msgid "" -"We used to set up Riot at the `riot.example.com` domain. The playbook now" -" sets up Element Web at `element.example.com` by default." +msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:22 @@ -88,18 +70,11 @@ msgid "There are a few options for handling this:" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:24 -msgid "" -"(**avoiding changes** - using the old `riot.example.com` domain and " -"avoiding DNS changes) -- to keep using `riot.example.com` instead of " -"`element.example.com`, override the domain at which the playbook serves " -"Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" +msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:26 -msgid "" -"(**embracing changes** - using only `element.example.com`) - set up the " -"`element.example.com` DNS record (see [Configuring DNS](configuring-" -"dns.md)). You can drop the `riot.example.com` in this case." +msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:28 @@ -107,24 +82,13 @@ msgid "Re-running the playbook" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:30 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:37 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:39 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po index 343adbf66..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 @@ -26,31 +26,19 @@ msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:3 -msgid "" -"If you'd like to store Synapse's content repository (`media_store`) files" -" on Amazon S3 (or other S3-compatible service), you can let this playbook" -" configure [Goofys](https://github.com/kahing/goofys) for you." +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:5 -msgid "" -"Another (and better performing) way to use S3 storage with Synapse is " -"[synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-" -"provider.md)." +msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:7 -msgid "" -"Using a Goofys-backed media store works, but performance may not be " -"ideal. If possible, try to use a region which is close to your Matrix " -"server." +msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:9 -msgid "" -"If you'd like to move your locally-stored media store data to Amazon S3 " -"(or another S3-compatible object store), we also provide some migration " -"instructions below." +msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:11 @@ -58,25 +46,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:13 -msgid "" -"After [creating the S3 bucket and configuring it](configuring-" -"playbook-s3.md#bucket-creation-and-security-configuration), add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:23 -msgid "" -"You can use any S3-compatible object store by **additionally** " -"configuring these variables:" +msgid "You can use any S3-compatible object store by **additionally** configuring these variables:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:30 -msgid "" -"If you have local media store files and wish to migrate to Backblaze B2 " -"subsequently, follow our [migration guide to Backblaze B2](#migrating-to-" -"backblaze-b2) below instead of applying this configuration as-is." +msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:32 @@ -84,23 +62,15 @@ msgid "Migrating from local filesystem storage to S3" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:34 -msgid "" -"It's a good idea to [make a complete server backup](faq.md#how-do-i-back-" -"up-the-data-on-my-server) before migrating your local media store to an " -"S3-backed one." +msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:36 -msgid "" -"After making the backup, follow one of the guides below for a migration " -"path from a locally-stored media store to one stored on S3-compatible " -"storage:" +msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:38 -msgid "" -"[Migrating to any S3-compatible storage (universal, but likely slow" -")](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" +msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:39 @@ -116,34 +86,23 @@ msgid "Proceed with the steps below without stopping Matrix services" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:45 -msgid "" -"Start by adding the base S3 configuration in your `vars.yml` file (seen " -"above, may be different depending on the S3 provider of your choice)" +msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:47 -msgid "" -"In addition to the base configuration you see above, add this to your " -"`vars.yml` file:" +msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:53 -msgid "" -"This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3" -"-media-store` without hooking it to your homeserver yet. Your homeserver " -"will still continue using your local filesystem for its media store." +msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:55 -msgid "" -"Run the playbook to apply the changes: `ansible-playbook -i " -"inventory/hosts setup.yml --tags=setup-all,start`" +msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:57 -msgid "" -"Do an **initial sync of your files** by running this **on the server** " -"(it may take a very long time):" +msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:63 @@ -152,15 +111,11 @@ msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:65 #: ../../../docs/configuring-playbook-s3-goofys.md:106 -msgid "" -"Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:67 -msgid "" -"Start the S3 service by running this **on the server**: `systemctl start " -"matrix-goofys`" +msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:69 @@ -168,43 +123,31 @@ msgid "Sync the files again by re-running the `rsync` command you see in step #5 msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:71 -msgid "" -"Stop the S3 service by running this **on the server**: `systemctl stop " -"matrix-goofys`" +msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:73 #: ../../../docs/configuring-playbook-s3-goofys.md:114 -msgid "" -"Get the old media store out of the way by running this command on the " -"server:" +msgid "Get the old media store out of the way by running this command on the server:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:79 -msgid "" -"Remove the `matrix_s3_media_store_path` configuration from your " -"`vars.yml` file (undoing step #3 above)" +msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:81 #: ../../../docs/configuring-playbook-s3-goofys.md:122 -msgid "" -"Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags" -"=setup-all,start`" +msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:83 #: ../../../docs/configuring-playbook-s3-goofys.md:124 -msgid "" -"You're done! Verify that loading existing (old) media files works and " -"that you can upload new ones." +msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:85 #: ../../../docs/configuring-playbook-s3-goofys.md:126 -msgid "" -"When confident that it all works, get rid of the local media store " -"directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" +msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:87 @@ -212,9 +155,7 @@ msgid "Migrating to Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:89 -msgid "" -"While all Matrix services are running, run the following command on the " -"server:" +msgid "While all Matrix services are running, run the following command on the server:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:91 @@ -230,20 +171,13 @@ msgid "Run the command from step #1 again." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:110 -msgid "" -"Doing this will sync any new files that may have been created locally in " -"the meantime." +msgid "Doing this will sync any new files that may have been created locally in the meantime." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:112 -msgid "" -"Now that Matrix services aren't running, we're sure to get Backblaze B2 " -"and your local media store fully in sync." +msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:120 -msgid "" -"Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) " -"in your `vars.yml` file" +msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po index 561daed38..c097ff4d3 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -22,37 +22,23 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-s3.md:1 -msgid "" -"Storing Synapse media files on Amazon S3 or another compatible Object " -"Storage (optional)" +msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:3 -msgid "" -"By default, this playbook configures your server to store Synapse's " -"content repository (`media_store`) files on the local filesystem. If " -"that's okay, you can skip this document." +msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-s3.md:5 -msgid "" -"As an alternative to storing media files on the local filesystem, you can" -" store them on [Amazon S3](https://aws.amazon.com/s3/) or another " -"S3-compatible object store." +msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store." msgstr "" #: ../../../docs/configuring-playbook-s3.md:7 -msgid "" -"You can do this either by sticking to Synapse's media repository and " -"making that use S3 (read below for this method), or by switching to an " -"external media storage implementation like [matrix-media-repo" -"](configuring-playbook-matrix-media-repo.md)." +msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:9 -msgid "" -"First, [choose an Object Storage provider](#choosing-an-object-storage-" -"provider)." +msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:11 @@ -60,12 +46,7 @@ msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration) msgstr "" #: ../../../docs/configuring-playbook-s3.md:13 -msgid "" -"Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys" -"](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider" -"](configuring-playbook-synapse-s3-storage-provider.md), or use s3 " -"datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-" -"media-repo/configuration/s3-datastore.html))." +msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))." msgstr "" #: ../../../docs/configuring-playbook-s3.md:15 @@ -73,35 +54,19 @@ msgid "Choosing an Object Storage provider" msgstr "" #: ../../../docs/configuring-playbook-s3.md:17 -msgid "" -"You can create [Amazon S3](https://aws.amazon.com/s3/) or another " -"S3-compatible object storage like [Backblaze " -"B2](https://www.backblaze.com/b2/cloud-storage.html), " -"[Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean " -"Spaces](https://www.digitalocean.com/products/spaces), etc." +msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc." msgstr "" #: ../../../docs/configuring-playbook-s3.md:19 -msgid "" -"Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges" -" for storing too little data." +msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data." msgstr "" #: ../../../docs/configuring-playbook-s3.md:21 -msgid "" -"All these providers have different prices, with Storj appearing to be the" -" cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress " -"fee is $0.007 per GB). Backblaze egress is free, but for only certain " -"users for up to 3x the amount of data stored. Beyond that you will pay " -"$0.01/GB of egress." +msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." msgstr "" #: ../../../docs/configuring-playbook-s3.md:23 -msgid "" -"Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which" -" becomes expensive if you need to store less data than that. Likewise, " -"Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of " -"2022-10)." +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 @@ -109,9 +74,7 @@ msgid "Here are some of the important aspects of choosing the right provider:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:27 -msgid "" -"if a provider is a company you like and trust (or dislike less than the " -"others)" +msgid "if a provider is a company you like and trust (or dislike less than the others)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:28 @@ -119,28 +82,19 @@ msgid "if a provider implements end-to-end encryption of your data" msgstr "" #: ../../../docs/configuring-playbook-s3.md:29 -msgid "" -"if a provider has a data region close to your Matrix server (if it's " -"farther away, high latency may cause slowdowns)" +msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:30 -msgid "" -"if a provider's infrastructure such as data center is centralized or " -"distributed" +msgid "if a provider's infrastructure such as data center is centralized or distributed" msgstr "" #: ../../../docs/configuring-playbook-s3.md:31 -msgid "" -"if a provider's price model is transparent (whether it includes hidden " -"costs like minimum charge, minimum storage term, etc.)" +msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:32 -msgid "" -"if a provider has free or cheap egress fee (in case you need to get the " -"data out often, for some reason) - likely not too important for the " -"common use-case" +msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case" msgstr "" #: ../../../docs/configuring-playbook-s3.md:34 @@ -148,24 +102,15 @@ msgid "Bucket creation and Security Configuration" msgstr "" #: ../../../docs/configuring-playbook-s3.md:36 -msgid "" -"Now that you've [chosen an Object Storage provider](#choosing-an-object-" -"storage-provider), you need to create a storage bucket." +msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket." msgstr "" #: ../../../docs/configuring-playbook-s3.md:38 -msgid "" -"How you do this varies from provider to provider, with Amazon S3 being " -"the most complicated due to its vast number of services and complicated " -"security policies." +msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies." msgstr "" #: ../../../docs/configuring-playbook-s3.md:40 -msgid "" -"Below, we provider some guides for common providers. If you don't see " -"yours, look at the others for inspiration or read some guides online " -"about how to create a bucket. Feel free to contribute to this " -"documentation with an update!" +msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!" msgstr "" #: ../../../docs/configuring-playbook-s3.md:42 @@ -173,16 +118,11 @@ msgid "Amazon S3" msgstr "" #: ../../../docs/configuring-playbook-s3.md:44 -msgid "" -"You'll need an Amazon S3 bucket and some IAM user credentials (access key" -" + secret key) with full write access to the bucket. Example IAM security" -" policy:" +msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:65 -msgid "" -"**Note**: This policy needs to be attached to an IAM user created from " -"the **Security Credentials** menu. This is not a **Bucket Policy**." +msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**." msgstr "" #: ../../../docs/configuring-playbook-s3.md:67 @@ -190,19 +130,11 @@ msgid "Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-s3.md:69 -msgid "" -"To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) " -"you first need to sign up." +msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up." msgstr "" #: ../../../docs/configuring-playbook-s3.md:71 -msgid "" -"You [can't easily change which region (US, Europe) your Backblaze account" -" stores files " -"in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/)," -" so make sure to carefully choose the region when signing up (hint: it's " -"a hard to see dropdown below the username/password fields in the signup " -"form)." +msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:73 @@ -210,15 +142,11 @@ msgid "After logging in to Backblaze:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:75 -msgid "" -"create a new **private** bucket through its user interface (you can call " -"it something like `matrix-example-media-store`)" +msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:76 -msgid "" -"note the **Endpoint** for your bucket (something like `s3.us-" -"west-002.backblazeb2.com`)." +msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:77 @@ -226,15 +154,11 @@ msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" msgstr "" #: ../../../docs/configuring-playbook-s3.md:78 -msgid "" -"go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the " -"**Add a New Application Key** to create a new one" +msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one" msgstr "" #: ../../../docs/configuring-playbook-s3.md:79 -msgid "" -"restrict it to the previously created bucket (e.g. `matrix-example-media-" -"store`)" +msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:80 @@ -242,22 +166,15 @@ msgid "give it *Read & Write* access" msgstr "" #: ../../../docs/configuring-playbook-s3.md:82 -msgid "" -"The `keyID` value is your **Access Key** and `applicationKey` is your " -"**Secret Key**." +msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**." msgstr "" #: ../../../docs/configuring-playbook-s3.md:84 -msgid "" -"For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3" -"-synapse-storage-provider](configuring-playbook-synapse-s3-storage-" -"provider.md) you will need:" +msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:86 -msgid "" -"**Endpoint URL** - this is the **Endpoint** value you saw above, but " -"prefixed with `https://`" +msgid "**Endpoint URL** - this is the **Endpoint** value you saw above, but prefixed with `https://`" msgstr "" #: ../../../docs/configuring-playbook-s3.md:88 @@ -265,9 +182,7 @@ msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:90 -msgid "" -"**Storage Class** - use `STANDARD`. Backblaze B2 does not have different " -"storage classes, so it doesn't make sense to use any other value." +msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value." msgstr "" #: ../../../docs/configuring-playbook-s3.md:92 @@ -275,16 +190,11 @@ msgid "Other providers" msgstr "" #: ../../../docs/configuring-playbook-s3.md:94 -msgid "" -"For other S3-compatible providers, you may not need to configure security" -" policies, etc. (just like for [Backblaze B2](#backblaze-b2))." +msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))." msgstr "" #: ../../../docs/configuring-playbook-s3.md:96 -msgid "" -"You most likely just need to create an S3 bucket and get some credentials" -" (access key and secret key) for accessing the bucket in a read/write " -"manner." +msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner." msgstr "" #: ../../../docs/configuring-playbook-s3.md:98 @@ -292,24 +202,17 @@ msgid "Setting up" msgstr "" #: ../../../docs/configuring-playbook-s3.md:100 -msgid "" -"To set up Synapse to store files in S3, follow the instructions for the " -"method of your choice:" +msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:102 -msgid "" -"using [synapse-s3-storage-provider](configuring-playbook-synapse-s3" -"-storage-provider.md) (recommended)" +msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:103 -msgid "" -"using [Goofys to mount the S3 store to the local filesystem](configuring-" -"playbook-s3-goofys.md)" +msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:104 msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po index 3cdbd4254..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 @@ -22,23 +22,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-shared-secret-auth.md:1 -msgid "" -"Setting up the Shared Secret Auth password provider module (optional, " -"advanced)" +msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:3 -msgid "" -"The playbook can install and configure [matrix-synapse-shared-secret-" -"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " -"you." +msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/devture/matrix-" -"synapse-shared-secret-auth/blob/master/README.md) to learn what it does " -"and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:7 @@ -46,9 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:9 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:18 @@ -56,10 +46,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:20 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:26 @@ -67,30 +54,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:35 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:37 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 dff86843c..a89308ff2 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 @@ -26,30 +26,15 @@ msgid "Setting up the Sliding Sync proxy (optional)" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 -msgid "" -"**Note**: The sliding-sync proxy is **not required** anymore as it's been" -" replaced with a different method (called Simplified Sliding Sync) which " -"is integrated into newer homeservers by default (**Conduit** homeserver " -"from version `0.6.0` or **Synapse** from version `1.114`). This component" -" and documentation remain here for historical purposes, but **installing " -"this old sliding-sync proxy is generally not recommended anymore**." +msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 -msgid "" -"The playbook can install and configure [sliding-sync](https://github.com" -"/matrix-org/sliding-sync) proxy for you." +msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 -msgid "" -"Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-" -"org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and " -"a prerequisite for running Element X clients ([Element X " -"iOS](https://github.com/element-hq/element-x-ios) and [Element X " -"Android](https://github.com/element-hq/element-x-android)). See the " -"project's [documentation](https://github.com/matrix-org/sliding-sync) to " -"learn more." +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 @@ -57,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 -msgid "" -"To enable Sliding Sync proxy, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 @@ -67,26 +50,15 @@ msgid "Adjusting the Sliding Sync proxy URL" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19 -msgid "" -"By default, this playbook installs the Sliding Sync proxy on the " -"`matrix.` subdomain, at the `/sliding-sync` path " -"(https://matrix.example.com/sliding-sync). This makes it easy to install " -"it, because it **doesn't require additional DNS records to be set up**. " -"If that's okay, you can skip this section." +msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:21 -msgid "" -"By tweaking the `matrix_sliding_sync_hostname` and " -"`matrix_sliding_sync_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31 @@ -94,9 +66,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Honoroit domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 @@ -104,9 +74,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 @@ -114,26 +82,15 @@ 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:" +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 @@ -141,10 +98,7 @@ 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:" +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 @@ -152,24 +106,13 @@ 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." +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`)." +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." +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 9b10fefa2..5009ae9dd 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 @@ -26,17 +26,11 @@ msgid "Adjusting SSL certificate retrieval (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:3 -msgid "" -"By default, this playbook retrieves and auto-renews free SSL certificates" -" from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs " -"(e.g. `matrix.example.com` and others)" +msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:5 -msgid "" -"This guide is about using the integrated Traefik server and doesn't apply" -" if you're using [your own webserver](configuring-playbook-own-" -"webserver.md)." +msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:7 @@ -44,16 +38,12 @@ msgid "Using staging Let's Encrypt certificates instead of real ones" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:9 -msgid "" -"For testing purposes, you may wish to use staging certificates provide by" -" Let's Encrypt." +msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:11 #: ../../../docs/configuring-playbook-ssl-certificates.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:17 @@ -61,10 +51,7 @@ msgid "Disabling SSL termination" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:19 -msgid "" -"For testing or other purposes, you may wish to install services without " -"SSL termination and have services exposed to `http://` instead of " -"`https://`." +msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:27 @@ -72,11 +59,7 @@ msgid "Using self-signed SSL certificates" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:29 -msgid "" -"If you'd like to use your own SSL certificates, instead of the default " -"(SSL certificates obtained automatically via " -"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" -" from [Let's Encrypt](https://letsencrypt.org/)):" +msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:31 @@ -84,9 +67,7 @@ msgid "generate your self-signed certificate files" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:32 -msgid "" -"follow the [Using your own SSL certificates](#using-your-own-ssl-" -"certificates) documentation below" +msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:34 @@ -98,30 +79,19 @@ msgid "To use your own SSL certificates with Traefik, you need to:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:38 -msgid "" -"disable " -"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" -" / [Let's Encrypt](https://letsencrypt.org/) support" +msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:39 -msgid "" -"put a custom Traefik configuration file on the server, with the help of " -"this Ansible playbook (via the [`aux` role](https://github.com/mother-of-" -"all-self-hosting/ansible-role-aux)) or manually" +msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:40 -msgid "" -"register your custom configuration file with Traefik, by adding an extra " -"provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:41 -msgid "" -"put the SSL files on the server, with the help of this Ansible playbook " -"(via the [`aux` role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-aux)) or manually" +msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:89 @@ -129,12 +99,7 @@ msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:91 -msgid "" -"You can configure Traefik to use the [DNS-01 challenge " -"type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for" -" Let's Encrypt. This is less commonly used than the default [HTTP-01 " -"challenge type](https://letsencrypt.org/docs/challenge-" -"types/#http-01-challenge), but it can be helpful to:" +msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:93 @@ -142,33 +107,17 @@ msgid "hide your public IP from Let's Encrypt logs" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:94 -msgid "" -"allow you to obtain SSL certificates for servers which are not accessible" -" (via HTTP) from the public internet (and for which the HTTP-01 challenge" -" would fail)" +msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:96 -msgid "" -"This is an example for how to edit the `vars.yml` file if you're using " -"Cloudflare:" +msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:111 -msgid "" -"Make sure to change the value of \"provider\" to your particular DNS " -"solution, and provide the appropriate environment variables. The full " -"list of supported providers is available " -"[here](https://doc.traefik.io/traefik/https/acme/#providers)." +msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:113 -msgid "" -"This example assumes you're using Cloudflare to manage your DNS zone. " -"Note that it requires the use of two tokens: one for reading all zones " -"(`CF_ZONE_API_TOKEN`) and another that must be able to edit the " -"particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's " -"recommended that you create two fine-grained tokens for this purpose, but" -" you might choose to use the same token for both." +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 2954af972..4194057d0 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -26,36 +26,23 @@ msgid "Setting up the Sygnal push gateway (optional)" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:3 -msgid "" -"The playbook can install and configure the [Sygnal](https://github.com" -"/matrix-org/sygnal) push gateway for you." +msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/sygnal/blob/master/README.md) to learn what it does and why it might " -"be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:7 -msgid "" -"**Note**: most people don't need to install their own gateway. As " -"Sygnal's [Notes for application developers](https://github.com/matrix-" -"org/sygnal/blob/master/docs/applications.md) documentation says:" +msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:9 -msgid "" -"It is not feasible to allow end-users to configure their own Sygnal " -"instance, because the Sygnal instance needs the appropriate FCM or APNs " -"secrets that belong to the application." +msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:11 -msgid "" -"This optional playbook component is only useful to people who " -"develop/build their own Matrix client applications themselves." +msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:13 @@ -63,50 +50,27 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:15 -msgid "" -"To enable Sygnal, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:43 -msgid "" -"For a more complete example of available fields and values they can take," -" see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the " -"[upstream `sygnal.yaml.sample` configuration file](https://github.com" -"/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." +msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:45 -msgid "" -"Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) " -"is easier, as it only requires that you provide some config values." +msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:47 -msgid "" -"To configure [APNS](https://developer.apple.com/notifications/) (Apple " -"Push Notification Service), you'd need to provide one or more certificate" -" files. To do that, the above example configuration:" +msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:49 -msgid "" -"makes use of the [`aux` role](https://github.com/mother-of-all-self-" -"hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to " -"make the playbook install files into `/matrix/sygnal/data` (the " -"`matrix_sygnal_data_path` variable). See [`defaults/main.yml` " -"file](https://github.com/mother-of-all-self-hosting/ansible-role-" -"aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It" -" also makes sure the files are owned by `matrix:matrix`, so that Sygnal " -"can read them. Of course, you can also install these files manually " -"yourself, if you'd rather not use `aux`." +msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:51 -msgid "" -"references these files in the Sygnal configuration (`matrix_sygnal_apps`)" -" using a path like `/data/..` (the `/matrix/sygnal/data` directory on the" -" host system is mounted into the `/data` directory inside the container)" +msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:53 @@ -114,23 +78,15 @@ msgid "Adjusting the Sygnal URL" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:55 -msgid "" -"By default, this playbook installs Sygnal on the `sygnal.` subdomain " -"(`sygnal.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:57 -msgid "" -"By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` " -"variables, you can easily make the service available at a **different " -"hostname and/or path** than the default one." +msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:59 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:70 @@ -138,21 +94,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:72 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Sygnal domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:74 -msgid "" -"By default, you will need to create a CNAME record for `sygnal`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:76 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:78 @@ -160,26 +110,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:80 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:87 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:89 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:91 @@ -187,24 +126,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:93 -msgid "" -"To make use of your Sygnal installation, you'd need to build your own " -"Matrix client application, which uses the same API keys (for " -"[GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and " -"certificates (for [APNS](https://developer.apple.com/notifications/)) and" -" is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." +msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:95 -msgid "" -"Refer to Sygnal's [Notes for application developers](https://github.com" -"/matrix-org/sygnal/blob/master/docs/applications.md) document." +msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/sygnal) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ 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 index b99172d3e..79fa31889 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -26,33 +26,15 @@ 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." +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:5 -msgid "" -"synapse-admin is a web UI tool you can use to **administrate users, " -"rooms, media, etc. on your Matrix server**. It's designed to work with " -"the Synapse homeserver implementation and WON'T work with Dendrite " -"because [Dendrite Admin API](https://matrix-" -"org.github.io/dendrite/administration/adminapi) differs from [Synapse " -"Admin API](https://element-" -"hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:7 -msgid "" -"💡 **Note**: the latest version of synapse-admin is hosted by " -"[etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). " -"If you only need this service occasionally and trust giving your admin " -"credentials to a 3rd party Single Page Application, you can consider " -"using it from there and avoiding the (small) overhead of self-hosting." +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 @@ -60,59 +42,27 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:11 -msgid "" -"To enable Synapse Admin, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:17 -msgid "" -"**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to" -" function. Access to them is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, for " -"additional security, we normally leave them unexposed, following " -"[official Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints). Because Synapse Admin needs these APIs to function, when " -"installing Synapse Admin, the playbook **automatically** exposes the " -"Synapse Admin API publicly for you. Depending on the homeserver " -"implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:19 -msgid "" -"for [Synapse](./configuring-playbook-synapse.md) (our default homeserver " -"implementation): " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true`" +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:20 -msgid "" -"for [Dendrite](./configuring-playbook-dendrite.md): " -"`matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled:" -" true`" +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:22 -msgid "" -"By default, synapse-admin installation will be [restricted to only work " -"with one homeserver](https://github.com/etkecc/synapse-" -"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" -"#restricting-available-homeserver) - the one managed by the playbook. To " -"adjust these restrictions, tweak the " -"`matrix_synapse_admin_config_restrictBaseUrl` variable." +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) - the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:24 -msgid "" -"⚠️ **Warning**: If you're using [Matrix Authentication Service" -"](./configuring-playbook-matrix-authentication-service.md) (MAS) for " -"authentication, you will be able to [log into synapse-admin with an " -"access token](https://github.com/etkecc/synapse-admin/pull/58), but " -"certain synapse-admin features (especially those around user management) " -"will be limited or not work at all." +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:26 @@ -120,26 +70,15 @@ msgid "Adjusting the Synapse Admin URL" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:28 -msgid "" -"By default, this playbook installs Synapse Admin on the `matrix.` " -"subdomain, at the `/synapse-admin` path (https://matrix.example.com" -"/synapse-admin). This makes it easy to install it, because it **doesn't " -"require additional DNS records to be set up**. If that's okay, you can " -"skip this section." +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:30 -msgid "" -"By tweaking the `matrix_synapse_admin_hostname` and " -"`matrix_synapse_admin_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:32 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:40 @@ -147,9 +86,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:42 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Synapse Admin domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:44 @@ -157,9 +94,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:46 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:48 @@ -167,26 +102,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:50 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:61 @@ -194,14 +118,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:63 -msgid "" -"After installation, Synapse Admin will be accessible at: " -"`https://matrix.example.com/synapse-admin/`" +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:65 -msgid "" -"To use Synapse Admin, you need to have [registered at least one " -"administrator account](registering-users.md) on your server." +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 257927ce2..bab4c606a 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 @@ -26,35 +26,19 @@ msgid "Setting up Synapse Auto Invite Accept (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 -msgid "" -"The playbook can install and configure [synapse-auto-invite-" -"accept](https://github.com/matrix-org/synapse-auto-accept-invite) for " -"you." +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 -msgid "" -"In short, it automatically accepts room invites. You can specify that " -"only 1:1 room invites are auto-accepted. Defaults to false if not " -"specified." +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." +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." +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 @@ -62,11 +46,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 -msgid "" -"If you decide that you'd like to let this playbook install the [synapse-" -"auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-" -"invite module for you, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +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 @@ -74,19 +54,11 @@ 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:" +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)." +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 @@ -94,27 +66,9 @@ msgid "Native alternative" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 -msgid "" -"Since Synapse [v1.109.0](https://github.com/element-" -"hq/synapse/releases/tag/v1.109.0), the functionality provided by the " -"[synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-" -"accept-invite) 3rd party module [has been made](https://github.com" -"/element-hq/synapse/pull/17147) part of Synapse." +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 "" - -#~ msgid "" -#~ "See that project's " -#~ "[documentation](https://github.com/matrix-org/synapse-" -#~ "auto-accept-invite) to learn what it" -#~ " does and why it might be " -#~ "useful to you. In short, it " -#~ "automatically accepts room invites. You " -#~ "can specify that only 1:1 room " -#~ "invites are auto-accepted. Defaults to" -#~ " false if not specified." -#~ 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 46ecd6c5a..df3897dff 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 @@ -26,24 +26,15 @@ msgid "Setting up synapse-auto-compressor (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 -msgid "" -"The playbook can install and configure " -"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" -"compress-state/#automated-tool-synapse_auto_compressor) for you." +msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 -msgid "" -"It's a CLI tool that automatically compresses Synapse's `state_groups` " -"database table in the background." +msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/rust-" -"synapse-compress-state/blob/master/README.md#automated-tool-" -"synapse_auto_compressor) to learn what it does and why it might be useful" -" to you." +msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 @@ -51,9 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 @@ -61,25 +50,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 @@ -87,10 +66,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 -msgid "" -"After installation, `synapse_auto_compressor` will run automatically " -"every day at `00:00:00` (as defined in " -"`matrix_synapse_auto_compressor_calendar` by default)." +msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 @@ -98,21 +74,5 @@ msgid "Manually start the tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 -msgid "" -"For testing your setup it can be helpful to not wait until 00:00. If you " -"want to run the tool immediately, log onto the server and run `systemctl " -"start matrix-synapse-auto-compressor`. Running this command will not " -"return control to your terminal until the compression run is done, which " -"may take a long time. Consider using " -"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " -"unstable." +msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/rust-synapse-compress-state" -#~ "/#automated-tool-synapse_auto_compressor) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 710df5e05..088ddec64 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 @@ -22,23 +22,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1 -msgid "" -"Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider" -" (optional)" +msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 -msgid "" -"If you'd like to store Synapse's content repository (`media_store`) files" -" on Amazon S3 (or other S3-compatible service), you can use the " -"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" -"-storage-provider) media provider module for Synapse." +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 -msgid "" -"An alternative (which has worse performance) is to use [Goofys to mount " -"the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." +msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 @@ -46,10 +38,7 @@ msgid "How it works?" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 -msgid "" -"Summarized writings here are inspired by [this " -"article](https://quentin.dufour.io/blog/2021-09-14/matrix-" -"synapse-s3-storage/)." +msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 @@ -57,49 +46,31 @@ msgid "The way media storage providers in Synapse work has some caveats:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 -msgid "" -"Synapse still continues to use locally-stored files (for creating " -"thumbnails, serving files, etc)" +msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 -msgid "" -"the media storage provider is just an extra storage mechanism (in " -"addition to the local filesystem)" +msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 -msgid "" -"all files are stored locally at first, and then copied to the media " -"storage provider (either synchronously or asynchronously)" +msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 -msgid "" -"if a file is not available on the local filesystem, it's pulled from a " -"media storage provider" +msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 -msgid "" -"You may be thinking **if all files are stored locally as well, what's the" -" point**?" +msgid "You may be thinking **if all files are stored locally as well, what's the point**?" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 -msgid "" -"You can run some scripts to delete the local files once in a while (which" -" we do automatically by default - see [Periodically cleaning up the local" -" filesystem](#periodically-cleaning-up-the-local-filesystem)), thus " -"freeing up local disk space. If these files are needed in the future (for" -" serving them to users, etc.), Synapse will pull them from the media " -"storage provider on demand." +msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 -msgid "" -"While you will need some local disk space around, it's only to " -"accommodate usage, etc., and won't grow as large as your S3 store." +msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 @@ -107,17 +78,11 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 -msgid "" -"After [creating the S3 bucket and configuring it](configuring-" -"playbook-s3.md#bucket-creation-and-security-configuration), you can " -"proceed to configure `s3-storage-provider` in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 -msgid "" -"If you have existing files in Synapse's media repository " -"(`/matrix/synapse/media-store/..`):" +msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 @@ -125,25 +90,15 @@ msgid "new files will start being stored both locally and on the S3 store" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53 -msgid "" -"the existing files will remain on the local filesystem only until " -"[migrating them to the S3 store](#migrating-your-existing-media-files-to-" -"the-s3-store)" +msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 -msgid "" -"at some point (and periodically in the future), you can delete local " -"files which have been uploaded to the S3 store already" +msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 -msgid "" -"Regardless of whether you need to [Migrate your existing files to the S3 " -"store](#migrating-your-existing-media-files-to-the-s3-store) or not, make" -" sure you've familiarized yourself with [How it works?](#how-it-works) " -"above and [Periodically cleaning up the local filesystem](#periodically-" -"cleaning-up-the-local-filesystem) below." +msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 @@ -155,17 +110,11 @@ msgid "Migrating your existing data can happen in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 -msgid "" -"[using the `s3_media_upload` script from `synapse-s3-storage-provider" -"`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " -"(very slow when dealing with lots of data)" +msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 -msgid "" -"[using another tool in combination with `s3_media_upload`](#using-" -"another-tool-in-combination-with-s3_media_upload) (quicker when dealing " -"with lots of data)" +msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 @@ -173,65 +122,39 @@ msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 -msgid "" -"Instead of using `s3_media_upload` directly, which is very slow and " -"painful for an initial data migration, we recommend [using another tool " -"in combination with `s3_media_upload`](#using-another-tool-in-" -"combination-with-s3_media_upload)." +msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69 -msgid "" -"To copy your existing files, SSH into the server and run " -"`/matrix/synapse/ext/s3-storage-provider/bin/shell`." +msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 -msgid "" -"This launches a Synapse container, which has access to the local media " -"store, Postgres database, S3 store and has some convenient environment " -"variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, " -"`UPDATE_DB_DAYS`, etc)." +msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 -msgid "" -"Then use the following commands (`$` values come from environment " -"variables - they're **not placeholders** that you need to substitute):" +msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 -msgid "" -"`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite " -"database (`cache.db`) with a list of media repository files (from the " -"`synapse` Postgres database) eligible for operating on" +msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76 -msgid "" -"`$UPDATE_DB_DURATION` is influenced by the " -"`matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` " -"variable (defaults to `0`)" +msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 -msgid "" -"`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include " -"files which haven't been accessed for more than 0 days** (that is, **all " -"files will be included**)." +msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 -msgid "" -"`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the " -"local cache still exist in the local media repository directory" +msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 -msgid "" -"`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class " -"$STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files " -"to S3 and deletes them from the local media repository directory" +msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 @@ -239,23 +162,15 @@ msgid "The `s3_media_upload upload` command may take a lot of time to complete." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 -msgid "" -"Instead of running the above commands manually in the shell, you can also" -" run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script " -"which will run the same commands automatically. We demonstrate how to do " -"it manually, because:" +msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 -msgid "" -"it's what the upstream project demonstrates and it teaches you how to use" -" the `s3_media_upload` tool" +msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 -msgid "" -"allows you to check and verify the output of each command, to catch " -"mistakes" +msgid "allows you to check and verify the output of each command, to catch mistakes" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 @@ -263,11 +178,7 @@ msgid "includes progress bars and detailed output for each command" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 -msgid "" -"allows you to easily interrupt slow-running commands, etc. (the " -"`/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container " -"without interactive TTY support, so `Ctrl+C` may not work and you and " -"require killing via `docker kill ..`)" +msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 @@ -279,18 +190,11 @@ msgid "To migrate your existing local data to S3, we recommend to:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 -msgid "" -"**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or " -"[`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files" -" to the S3 bucket" +msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 -msgid "" -"**only then** [use the `s3_media_upload` tool to finish the migration" -"](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " -"(this checks to ensure all files are uploaded and then deletes the local " -"files)" +msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 @@ -306,20 +210,11 @@ msgid "Copying data to an S3 alternative using the aws-s3 tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114 -msgid "" -"To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean " -"Spaces, etc.), you can use the command for [Copying data to Amazon S3" -"](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` " -"argument." +msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116 -msgid "" -"Add this argument to the command **as-is** (`$ENDPOINT` is an environment" -" variable corresponding to " -"`matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so " -"you don't need to touch it). Make sure to add the argument **before** the" -" final quote (`'`) of the command." +msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118 @@ -327,19 +222,11 @@ msgid "Copying data to Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 -msgid "" -"You can copy files to Backblaze B2 either by following the [Copying data " -"to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3" -"-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 " -"command-line " -"tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as " -"described below." +msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 -msgid "" -"To copy the data using the `b2` tool, start a container on the Matrix " -"server like this:" +msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136 @@ -347,17 +234,11 @@ msgid "Periodically cleaning up the local filesystem" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138 -msgid "" -"As described in [How it works?](#how-it-works) above, when new media is " -"uploaded to the Synapse homeserver, it's first stored locally and then " -"also stored on the remote S3 storage." +msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140 -msgid "" -"By default, we periodically ensure that all local files are uploaded to " -"S3 and are then removed from the local filesystem. This is done " -"automatically using:" +msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142 @@ -365,18 +246,13 @@ msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143 -msgid "" -".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` " -"service" +msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 -msgid "" -".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` " -"timer, every day at 05:00" +msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 msgid "So.. you don't need to perform any maintenance yourself." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po index b28d1a365..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 @@ -26,22 +26,15 @@ msgid "Setting up Synapse Simple Antispam (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 -msgid "" -"The playbook can install and configure [synapse-simple-" -"antispam](https://github.com/t2bot/synapse-simple-antispam) for you." +msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 -msgid "" -"It lets you fight invite-spam by automatically blocking invitiations from" -" a list of servers specified by you (blacklisting)." +msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 -msgid "" -"See the project's [documentation](https://github.com/t2bot/synapse-" -"simple-antispam/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 @@ -49,19 +42,5 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you. In short," -#~ " it lets you fight invite-spam " -#~ "by automatically blocking invitiations from" -#~ " a list of servers specified by " -#~ "you (blacklisting)." -#~ 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 b3a621a72..6cf2793d2 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 @@ -26,21 +26,11 @@ msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 -msgid "" -"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" -"exporter) allows you to export the usage statistics of a Synapse " -"homeserver to this container service and for the collected metrics to " -"later be scraped by Prometheus." +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 -msgid "" -"Synapse does not include usage statistics in its Prometheus metrics. They" -" can be reported to an HTTP `PUT` endpoint 5 minutes after startup and " -"from then on at a fixed interval of once every three hours. This role " -"integrates a simple [Flask](https://flask.palletsprojects.com) project " -"that offers an HTTP `PUT` endpoint and holds the most recent received " -"record available to be scraped by Prometheus." +msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 @@ -52,22 +42,15 @@ msgid "install the synapse-usage-exporter service" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 -msgid "" -"re-configure Synapse to push (via HTTP `PUT`) usage statistics " -"information to synapse-usage-exporter" +msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 -msgid "" -"re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) " -"(if Prometheus is enabled), to periodically scrape metrics from synapse-" -"usage-exporter" +msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 -msgid "" -"add a new [Grafana](./configuring-playbook-prometheus-grafana.md) " -"dashboard (if Grafana is enabled) containing Synapse usage statistics" +msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 @@ -75,9 +58,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 -msgid "" -"To enable synapse-usage-exporter, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 @@ -85,26 +66,15 @@ msgid "Adjusting the synapse-usage-exporter URL" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 -msgid "" -"By default, this playbook installs synapse-usage-exporter on the " -"`matrix.` subdomain, at the `/report-usage-stats/push` path " -"(https://matrix.example.com/report-usage-stats/push). This makes it easy " -"to install it, because it **doesn't require additional DNS records to be " -"set up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 -msgid "" -"By tweaking the `matrix_synapse_usage_exporter_hostname` and " -"`matrix_synapse_usage_exporter_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43 @@ -112,10 +82,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the synapse-usage-exporter domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 @@ -123,9 +90,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 @@ -133,25 +98,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po index cc2210b70..423c85fd5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po @@ -26,70 +26,35 @@ msgid "Configuring Synapse (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, so that it works for the general " -"case. If that's okay, you can skip this document." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:5 -msgid "" -"The playbook provides lots of customization variables you could use to " -"change Synapse's settings." +msgid "The playbook provides lots of customization variables you could use to change Synapse's settings." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:7 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/synapse/config/homeserver.yaml` file (on the server). This file " -"is generated from the [`roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:9 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:11 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a Synapse " -"setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:13 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Synapse's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:15 -msgid "" -"or, you can **extend and override the default configuration** " -"([`homeserver.yaml.j2`](../roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2)) by making use of the " -"`matrix_synapse_configuration_extension_yaml` variable. You can find " -"information about this in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:17 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). " -"You can find information about this in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:19 @@ -97,28 +62,15 @@ msgid "Load balancing with workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:21 -msgid "" -"To have Synapse gracefully handle thousands of users, worker support " -"should be enabled. It factors out some homeserver tasks and spreads the " -"load of incoming client and server-to-server traffic between multiple " -"processes. More information can be found in the [official Synapse workers" -" documentation](https://github.com/element-" -"hq/synapse/blob/master/docs/workers.md) and [Tom " -"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/index.html)." +msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:23 -msgid "" -"To enable Synapse worker support, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:31 -msgid "" -"By default, this enables the `one-of-each` [worker preset](#worker-" -"presets), but you may wish to use another preset or [control the number " -"of worker instances](#controlling-the-number-of-worker-instances)." +msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:33 @@ -126,34 +78,23 @@ msgid "Worker presets" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:35 -msgid "" -"We support a few configuration presets (`matrix_synapse_workers_preset: " -"one-of-each` being the default configuration right now):" +msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:37 -msgid "" -"(federation-only) `little-federation-helper` - a very minimal worker " -"configuration to improve federation performance" +msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:38 -msgid "" -"(generic) `one-of-each` - defaults to one worker of each supported type -" -" no smart routing, just generic workers" +msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:39 -msgid "" -"(specialized) `specialized-workers` - defaults to one worker of each " -"supported type, but disables generic workers and uses [specialized " -"workers](#specialized-workers) instead" +msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:41 -msgid "" -"These presets represent a few common configurations. There are many " -"worker types which can be mixed and matched based on your needs." +msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:43 @@ -161,35 +102,19 @@ msgid "Generic workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:45 -msgid "" -"Previously, the playbook only supported the most basic type of load-" -"balancing. We call it **generic load-balancing** below, because incoming " -"HTTP requests are sent to a generic worker. Load-balancing was done based" -" on the requestor's IP address. This is simple, but not necessarily " -"optimal. If you're accessing your account from multiple IP addresses " -"(e.g. your mobile phone being on a different network than your PC), these" -" separate requests may potentially be routed to different workers, each " -"of which would need to cache roughly the same data." +msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:47 -msgid "" -"This is **still the default load-balancing method (preset) used by the " -"playbook**." +msgid "This is **still the default load-balancing method (preset) used by the playbook**." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:49 -msgid "" -"To use generic load-balancing, do not specify " -"`matrix_synapse_workers_preset` to make it use the default value (`one-" -"of-each`), or better yet - explicitly set it as `one-of-each`." +msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:51 -msgid "" -"You may also consider [tweaking the number of workers of each type" -"](#controlling-the-number-of-worker-instances) from the default (one of " -"each)." +msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:53 @@ -197,15 +122,7 @@ msgid "Specialized workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:55 -msgid "" -"The playbook now supports a smarter **specialized load-balancing** " -"inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse " -"homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead " -"of routing requests to one or more [generic workers](#generic-workers) " -"based only on the requestor's IP adddress, specialized load-balancing " -"routes to **4 different types of specialized workers** based on **smarter" -" criteria** - the access token (username) of the requestor and/or on the " -"resource (room, etc.) being requested." +msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:57 @@ -213,43 +130,23 @@ msgid "The playbook supports these **4 types** of specialized workers:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:59 -msgid "" -"Room workers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) & " -"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs " -"dedicated to handling specific rooms" +msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:60 -msgid "" -"Sync workers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to " -"synchronization (most notably [the `/sync` " -"endpoint](https://spec.matrix.org/v1.9/client-server-" -"api/#get_matrixclientv3sync))" +msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:61 -msgid "" -"Client readers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are " -"not for specific rooms (handled by **room workers**) or for " -"synchronization (handled by **sync workers**)" +msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:62 -msgid "" -"Federation readers - handles various " -"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which " -"are not for specific rooms (handled by **room workers**)" +msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:64 -msgid "" -"To use specialized load-balancing, consider enabling the `specialized-" -"workers` [worker preset](#worker-presets) and potentially [tweaking the " -"number of workers of each type](#controlling-the-number-of-worker-" -"instances) from the default (one of each)." +msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:66 @@ -257,24 +154,15 @@ msgid "Controlling the number of worker instances" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:68 -msgid "" -"If you'd like more customization power, you can start with one of the " -"[worker presets](#worker-presets) and then tweak various " -"`matrix_synapse_workers_*_count` variables manually." +msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:70 -msgid "" -"To find what variables are available for you to override in your own " -"`vars.yml` configuration file, see the [`defaults/main.yml` file for the " -"`matrix-synapse` Ansible role](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:72 -msgid "" -"The only thing you **cannot** do is mix [generic workers](#generic-" -"workers) and [specialized workers](#specialized-workers)." +msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:74 @@ -282,30 +170,15 @@ msgid "Effect of enabling workers on the rest of your server" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:76 -msgid "" -"When Synapse workers are enabled, the integrated [Postgres database is " -"tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum " -"number of Postgres connections are increased from `200` to `500`. If you " -"need to decrease or increase the number of maximum Postgres connections " -"further, use the `postgres_max_connections` variable." +msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:78 -msgid "" -"A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and " -"component handles load-balancing for workers. This role/component is " -"automatically enabled when you enable workers. Make sure to use the " -"`setup-all` tag (not `install-all`!) during the playbook's " -"[installation](./installing.md) process, especially if you're disabling " -"workers, so that components may be installed/uninstalled correctly." +msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:80 -msgid "" -"In case any problems occur, make sure to have a look at the [list of " -"synapse issues about workers](https://github.com/element-" -"hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit " -"'matrix-*'`." +msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:82 @@ -313,10 +186,7 @@ msgid "Synapse Admin" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:84 -msgid "" -"Certain Synapse administration tasks (managing users and rooms, etc.) can" -" be performed via a web user-interace, if you install [Synapse Admin" -"](configuring-playbook-synapse-admin.md)." +msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:86 @@ -324,42 +194,24 @@ msgid "Synapse + OpenID Connect for Single-Sign-On" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:88 -msgid "" -"💡 An alternative to setting up OIDC in Synapse is to use [Matrix " -"Authentication Service](./configuring-playbook-matrix-authentication-" -"service.md) (MAS). Newer clients (like Element X) only support SSO-based " -"authentication via MAS and not via the legacy Synapse OIDC setup " -"described below. That said, MAS is still a new experimental service which" -" comes with its own downsides. Consult its documentation to learn if it " -"will be a good fit for your deployment." +msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:90 -msgid "" -"If you'd like to use OpenID Connect authentication with Synapse, you'll " -"need some additional configuration." +msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:92 -msgid "" -"This example configuration is for [keycloak](https://www.keycloak.org/), " -"an opensource Identity Provider maintained by Red Hat." +msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:94 -msgid "" -"For more detailed documentation on available options and how to setup " -"keycloak, see the [Synapse documentation on OpenID Connect with " -"keycloak](https://github.com/element-" -"hq/synapse/blob/develop/docs/openid.md#keycloak)." +msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:96 #, python-format -msgid "" -"In case you encounter errors regarding the parsing of the variables, you " -"can try to add `{% raw %}` and `{% endraw %}` blocks around them. For " -"example ;" +msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:117 @@ -367,48 +219,27 @@ msgid "Customizing templates" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:119 -msgid "" -"[Templates](https://github.com/element-" -"hq/synapse/blob/develop/docs/templates.md) are used by Synapse for " -"showing **certain web pages** handled by the server, as well as for " -"**email notifications**." +msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:121 -msgid "" -"This playbook allows you to customize the default templates (see the " -"[`synapse/res/templates` directory](https://github.com/element-" -"hq/synapse/tree/develop/synapse/res/templates))." +msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:123 -msgid "" -"If template customization is enabled, the playbook will build a custom " -"container image based on the official one." +msgid "If template customization is enabled, the playbook will build a custom container image based on the official one." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:125 -msgid "" -"Your custom templates need to live in a public or private git repository." -" This repository will be cloned during Synapse image customization " -"(during the playbook run)." +msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:127 -msgid "" -"To enable template customizations, use a configuration " -"(`inventory/host_vars/matrix.example.com/vars.yml`) like this:" +msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:153 -msgid "" -"As mentioned in Synapse's Templates documentation, Synapse will fall back" -" to its own templates if a template is not found in that directory. Due " -"to this, it's recommended to only store and maintain template files in " -"your repository if you need to make custom changes. Other files (which " -"you don't need to change), should not be duplicated, so that you don't " -"need to worry about getting out-of-sync with the original Synapse " -"templates." +msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:155 @@ -416,22 +247,13 @@ msgid "Monitoring Synapse Metrics with Prometheus and Grafana" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:157 -msgid "" -"This playbook allows you to enable Synapse metrics, which can provide " -"insight into the performance and activity of Synapse." +msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:159 -msgid "" -"To enable Synapse runtime metrics see: [Enabling metrics and graphs " -"(Prometheus, Grafana) for your Matrix server](configuring-playbook-" -"prometheus-grafana.md)" +msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:161 -msgid "" -"To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter " -"for Synapse usage statistics](configuring-playbook-synapse-usage-" -"exporter.md)" +msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po index 58fb8cae7..e2736973a 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po @@ -26,17 +26,11 @@ msgid "Enabling Telemetry for your Matrix server (optional)" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:3 -msgid "" -"By default, this playbook configures your Matrix homeserver to not send " -"any telemetry data anywhere." +msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:5 -msgid "" -"The [matrix.org](https://matrix.org) team would really appreciate it if " -"you could help the project out by reporting usage statistics from your " -"homeserver. Enabling usage statistics helps track the growth of the " -"Matrix community, and helps to make Matrix a success." +msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:7 @@ -44,10 +38,7 @@ msgid "Enabling Telemetry" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:9 -msgid "" -"If you'd like to **help by enabling submission of general usage " -"statistics** for your homeserver, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:17 @@ -55,21 +46,9 @@ msgid "Usage statistics being submitted" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:19 -msgid "" -"When enabled, your homeserver will regularly upload a few dozen " -"statistics about your server. This data includes your homeserver's " -"domain, the total number of users, the number of active users, the total " -"number of rooms, and the number of messages sent per day on your " -"homeserver." +msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:21 -msgid "" -"See [Synapse's documentation](https://github.com/element-" -"hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md" -"#available-statistics) or [Dendrite's documentation](https://github.com" -"/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-" -"enabling-phone-home-statistics) for the full list of statistics that are " -"reported." +msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po index 0b97553e6..f33124d44 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -26,17 +26,11 @@ msgid "Configuring the Traefik reverse-proxy (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:3 -msgid "" -"By default, this playbook installs and manages a " -"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered " -"by the [ansible-role-traefik](https://github.com/mother-of-all-self-" -"hosting/ansible-role-traefik) Ansible role." +msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:5 -msgid "" -"This Ansible role support various configuration options. Feel free to " -"consult its `default/main.yml` variables file." +msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:7 @@ -44,9 +38,7 @@ msgid "Adjusting SSL certificate retrieval" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:9 -msgid "" -"See the dedicated [Adjusting SSL certificate retrieval](configuring-" -"playbook-ssl-certificates.md) documentation page." +msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:11 @@ -66,22 +58,11 @@ msgid "Enable Traefik Dashboard" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:27 -msgid "" -"This will enable a Traefik " -"[Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at " -"`https://matrix.example.com/dashboard/` (note the trailing `/`)." +msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:37 -msgid "" -"**WARNING**: Enabling the dashboard on a hostname you use for something " -"else (like `matrix_server_fqn_matrix` in the configuration above) may " -"cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all" -" `/dashboard` and `/api` requests and forward them to itself. If any of " -"the services hosted on the same hostname requires any of these 2 URL " -"prefixes, you will experience problems. So far, we're not aware of any " -"playbook services which occupy these endpoints and are likely to cause " -"conflicts." +msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:39 @@ -89,10 +70,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:41 -msgid "" -"Use the `traefik_configuration_extension_yaml` variable provided by the " -"Traefik Ansible role to override or inject additional settings, even when" -" no dedicated variable exists." +msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:51 @@ -100,24 +78,11 @@ msgid "Reverse-proxying another service behind Traefik" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:53 -msgid "" -"The preferred way to reverse-proxy additional services behind Traefik " -"would be to start the service as another container, configure the " -"container with the corresponding Traefik [container " -"labels](https://docs.docker.com/config/labels-custom-metadata/) (see " -"[Traefik & " -"Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and " -"connect the service to the `traefik` network. Some services are also " -"already available via the compatible [mash-playbook](https://github.com" -"/mother-of-all-self-hosting/mash-playbook), but take a look at the minor " -"[interoperability adjustments](https://github.com/mother-of-all-self-" -"hosting/mash-playbook/blob/main/docs/interoperability.md)." +msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:55 -msgid "" -"However, if your service does not run on a container or runs on another " -"machine, the following configuration might be what you are looking for." +msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:57 @@ -125,51 +90,28 @@ msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:59 -msgid "" -"If you want to host another webserver would be reachable via `my-fancy-" -"website.example.net` from the internet and via `https://:` from inside your network, you can " -"make the playbook's integrated Traefik instance reverse-proxy the traffic" -" to the correct host." +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:61 -msgid "" -"Prerequisites: DNS and routing for the domain `my-fancy-" -"website.example.net` need to be set up correctly. In this case, you'd be " -"pointing the domain name to your Matrix server - `my-fancy-" -"website.example.net` would be a CNAME going to `matrix.example.com`." +msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:63 -msgid "" -"First, we have to adjust the static configuration of Traefik, so that we " -"can add additional configuration files:" +msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:77 -msgid "" -"If you are using a self-signed certificate on your webserver, you can " -"tell Traefik to trust your own backend servers by adding more " -"configuration to the static configuration file. If you do so, bear in " -"mind the security implications of disabling the certificate validity " -"checks towards your back end." +msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:91 -msgid "" -"Next, you have to add a new dynamic configuration file for Traefik that " -"contains the actual information of the server using the " -"`aux_file_definitions` variable. In this example, we will terminate SSL " -"at the Traefik instance and connect to the other server via HTTPS. " -"Traefik will now take care of managing the certificates." +msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:110 #: ../../../docs/configuring-playbook-traefik.md:133 -msgid "" -"Changing the `url` to one with an `http://` prefix would allow to connect" -" to the server via HTTP." +msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:112 @@ -177,28 +119,15 @@ msgid "Reverse-proxying another service behind Traefik without terminating SSL" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:114 -msgid "" -"If you do not want to terminate SSL at the Traefik instance (for example," -" because you're already terminating SSL at other webserver), you need to " -"adjust the static configuration in the same way as in the previous " -"chapter in order to be able to add our own dynamic configuration files. " -"Afterwards, you can add the following configuration to your `vars.yml` " -"configuration file:" +msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:135 -msgid "" -"With these changes, all TCP traffic will be reverse-proxied to the target" -" system." +msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:137 -msgid "" -"**WARNING**: This configuration might lead to problems or need additional" -" steps when a [certbot](https://certbot.eff.org/) behind Traefik also " -"tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, " -"as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-" -"challenge/`)```." +msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:139 @@ -206,8 +135,5 @@ msgid "Traefik behind a `proxy_protocol` reverse-proxy" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:141 -msgid "" -"If you run a reverse-proxy which speaks `proxy_protocol`, add the " -"following to your configuration file:" +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 02a771d39..8fbfe1733 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -26,17 +26,11 @@ msgid "Adjusting TURN server configuration (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-turn.md:3 -msgid "" -"The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN " -"server by default, so that clients can make audio/video calls even from " -"[NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed " -"networks." +msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks." msgstr "" #: ../../../docs/configuring-playbook-turn.md:5 -msgid "" -"By default, the Synapse chat server is configured, so that it points to " -"the Coturn TURN server installed by the playbook." +msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook." msgstr "" #: ../../../docs/configuring-playbook-turn.md:7 @@ -44,16 +38,11 @@ msgid "Disabling Coturn" msgstr "" #: ../../../docs/configuring-playbook-turn.md:9 -msgid "" -"If, for some reason, you'd like to prevent the playbook from installing " -"Coturn, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:15 -msgid "" -"In that case, Synapse would not point to any Coturn servers and " -"audio/video call functionality may fail." +msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail." msgstr "" #: ../../../docs/configuring-playbook-turn.md:17 @@ -61,36 +50,19 @@ msgid "Manually defining your public IP" msgstr "" #: ../../../docs/configuring-playbook-turn.md:19 -msgid "" -"In the `hosts` file we explicitly ask for your server's external IP " -"address when defining `ansible_host`, because the same value is used for " -"configuring Coturn." +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring Coturn." msgstr "" #: ../../../docs/configuring-playbook-turn.md:21 -msgid "" -"If you'd rather use a local IP for `ansible_host`, make sure to set up " -"`matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with " -"the pubic IP used by the server." +msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server." msgstr "" #: ../../../docs/configuring-playbook-turn.md:27 -msgid "" -"If you'd like to rely on external IP address auto-detection (not " -"recommended unless you need it), set " -"`matrix_coturn_turn_external_ip_address` to an empty value. The playbook " -"will automatically contact an " -"[EchoIP](https://github.com/mpolden/echoip)-compatible service " -"(`https://ifconfig.co/json` by default) to determine your server's IP " -"address. This API endpoint is configurable via the " -"`matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url`" -" variable." +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." msgstr "" #: ../../../docs/configuring-playbook-turn.md:29 -msgid "" -"If your server has multiple external IP addresses, the Coturn role offers" -" a different variable for specifying them:" +msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:36 @@ -98,13 +70,7 @@ msgid "Changing the authentication mechanism" msgstr "" #: ../../../docs/configuring-playbook-turn.md:38 -msgid "" -"The playbook uses the [`auth-secret` authentication " -"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199)" -" by default, but you may switch to the [`lt-cred-mech` " -"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178)" -" which [some report](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3191) to be working better." +msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." msgstr "" #: ../../../docs/configuring-playbook-turn.md:40 @@ -112,17 +78,11 @@ msgid "To do so, add this override to your configuration:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:46 -msgid "" -"Regardless of the selected authentication method, the playbook generates " -"secrets automatically and passes them to the homeserver and Coturn." +msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and Coturn." msgstr "" #: ../../../docs/configuring-playbook-turn.md:48 -msgid "" -"If you're using [Jitsi](./configuring-playbook-jitsi.md), note that " -"switching to `lt-cred-mech` will remove the integration between Jitsi and" -" your own Coturn server, because Jitsi only seems to support the `auth-" -"secret` authentication method." +msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method." msgstr "" #: ../../../docs/configuring-playbook-turn.md:50 @@ -130,16 +90,11 @@ msgid "Using your own external Coturn server" msgstr "" #: ../../../docs/configuring-playbook-turn.md:52 -msgid "" -"If you'd like to use another TURN server (be it Coturn or some other " -"one), you can configure the playbook like this:" +msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:66 -msgid "" -"If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you" -" might want to enable the TURN server there too. If you do not do it, " -"Jitsi will fall back to an upstream service." +msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." msgstr "" #: ../../../docs/configuring-playbook-turn.md:72 @@ -151,8 +106,5 @@ msgid "Further variables and configuration options" msgstr "" #: ../../../docs/configuring-playbook-turn.md:75 -msgid "" -"To see all the available configuration options, check roles/custom" -"/matrix-coturn/defaults/main.yml" +msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index 7b5148329..0e4f60922 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -26,42 +26,23 @@ msgid "Setting up Matrix User Verification Service (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:3 -msgid "" -"**[Matrix User Verification Service](https://github.com/matrix-org" -"/matrix-user-verification-service) (hereafter: UVS) can only be installed" -" after Matrix services are installed and running.** If you're just " -"installing Matrix services for the first time, please continue with the " -"[Configuration](configuring-playbook.md) / [Installation](installing.md) " -"flow and come back here later." +msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:5 -msgid "" -"Currently, the main purpose of this role is to allow Jitsi to " -"authenticate Matrix users and check if they are authorized to join a " -"conference. Please refer to the documentation of the [Matrix User " -"Verification Service](https://github.com/matrix-org/matrix-user-" -"verification-service) to understand how it works." +msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:7 -msgid "" -"**Note**: enabling Matrix User Verification Service, means that the " -"`openid` API endpoints will be exposed on the Matrix Federation port " -"(usually `8448`), even if [federation](configuring-playbook-" -"federation.md) is disabled." +msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:9 -msgid "" -"If the Jitsi server is also configured by this playbook, all plugging of " -"variables and secrets is handled in `group_vars/matrix_servers`." +msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:11 -msgid "" -"__Some general concepts of UVS may be helpful to understand the rest, so " -"here they are:__" +msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:13 @@ -73,27 +54,15 @@ msgid "(A) Whether a given OpenID token is valid for a given server and" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:16 -msgid "" -"(B) whether a user is member of a given room and the corresponding " -"PowerLevel" +msgid "(B) whether a user is member of a given room and the corresponding PowerLevel" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:18 -msgid "" -"Verifying an OpenID token ID done by finding the corresponding Homeserver" -" via '.well-known/matrix/server' for the given domain. The configured " -"`matrix_user_verification_service_uvs_homeserver_url` does **not** factor" -" into this. By default, this playbook only checks against " -"`matrix_server_fqn_matrix`. Therefore, the request will be made against " -"the public openid API for `matrix_server_fqn_matrix`." +msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:20 -msgid "" -"Verifying RoomMembership and PowerLevel is done against " -"`matrix_user_verification_service_uvs_homeserver_url` which is by default" -" done via the docker network. UVS will verify the validity of the token " -"beforehand though." +msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:22 @@ -101,10 +70,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:24 -msgid "" -"In order to use UVS, an admin token for the configured homeserver must be" -" supplied. For now this means configuring Synapse and creating the token " -"before installing UVS." +msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:26 @@ -112,10 +78,7 @@ msgid "Enable" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:28 -msgid "" -"To enable Matrix User Verification Service, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:34 @@ -123,25 +86,15 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:36 -msgid "" -"The only required configuration variable is " -"`matrix_user_verification_service_uvs_access_token` (see below)." +msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:38 -msgid "" -"For a list of all configuration options see the role defaults [`roles" -"/matrix-user-verification-service/defaults/main.yml`](../roles/custom" -"/matrix-user-verification-service/defaults/main.yml). But be aware of all" -" the plugging happening in `group_vars/matrix_servers`." +msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:40 -msgid "" -"In the default configuration, the UVS Server is only reachable via the " -"docker network, which is fine if e.g. Jitsi is also running in a " -"container on the host. However, it is possible to expose UVS via setting " -"`matrix_user_verification_service_container_http_host_bind_port`." +msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:42 @@ -149,30 +102,19 @@ msgid "Access token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:44 -msgid "" -"The Synapse Access Token is used to verify RoomMembership and PowerLevel " -"against `matrix_user_verification_service_uvs_homeserver_url`." +msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:46 -msgid "" -"We recommend that you create a dedicated Matrix user for uvs (`uvs` is a " -"good username). Follow our [Registering users](registering-users.md) " -"guide to register a user with administration privileges." +msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:48 -msgid "" -"You are required to specify an access token (belonging to this new user) " -"for UVS to work. To get an access token for the UVS user, you can follow " -"the documentation on [how to do obtain an access token](obtaining-access-" -"tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:50 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:56 @@ -180,29 +122,19 @@ msgid "(Optional) Custom Auth Token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:58 -msgid "" -"It is possible to set an API Auth Token to restrict access to the UVS. If" -" this is enabled, anyone making a request to UVS must provide it via the " -"header \"Authorization: Bearer TOKEN\"" +msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\"" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:60 -msgid "" -"By default, the token will be derived from " -"`matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." +msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:62 -msgid "" -"To set your own Token, add the following configuration to your `vars.yml`" -" file:" +msgid "To set your own Token, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:68 -msgid "" -"In case Jitsi is also managed by this playbook and 'matrix' " -"authentication in Jitsi is enabled, this collection will automatically " -"configure Jitsi to use the configured auth token." +msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:70 @@ -210,9 +142,7 @@ msgid "(Optional) Disable Auth" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:72 -msgid "" -"Authorization is enabled by default. To disable it, add the following " -"configuration to your `vars.yml` file:" +msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:78 @@ -220,16 +150,11 @@ msgid "(Optional) Federation" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:80 -msgid "" -"In theory (however currently untested), UVS can handle federation. To " -"enable it, add the following configuration to your `vars.yml` file:" +msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:86 -msgid "" -"This will instruct UVS to verify the OpenID token against any domain " -"given in a request. Homeserver discovery is done via '.well-" -"known/matrix/server' of the given domain." +msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:88 @@ -237,25 +162,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:90 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:97 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service matrix-user-verification-service` or " -"`just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:99 -msgid "" -"`just install-service matrix-user-verification-service` is useful for " -"maintaining your setup quickly when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"`just setup-all` runs the `ensure-matrix-users-created` tag too." +msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:101 @@ -283,9 +198,7 @@ msgid "TLS Certificate Checking" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:110 -msgid "" -"If the Matrix Homeserver does not provide a valid TLS certificate, UVS " -"will fail with the following error message:" +msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:112 @@ -297,44 +210,9 @@ msgid "This also applies to self-signed and let's encrypt staging certificates." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:116 -msgid "" -"To disable certificate validation altogether (INSECURE! Not suitable for " -"production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" +msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:118 -msgid "" -"Alternatively, it is possible to inject your own CA certificates into the" -" container by mounting a PEM file with additional trusted CAs into the " -"container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to " -"it." +msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it." msgstr "" - -#~ msgid "" -#~ "After these variables have been set, " -#~ "run the playbook with [playbook tags" -#~ "](playbook-tags.md) as below to restart " -#~ "UVS:" -#~ msgstr "" - -#~ msgid "" -#~ "The shortcut commands with the [`just`" -#~ " program](just.md) are also available: " -#~ "`just run-tags setup-matrix-user-" -#~ "verification-service,start` or `just setup-" -#~ "all`" -#~ msgstr "" - -#~ msgid "" -#~ "`just run-tags setup-matrix-user-" -#~ "verification-service,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 "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po index 0bcce4848..f75851e6b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po @@ -26,40 +26,23 @@ msgid "Configuring the playbook" msgstr "" #: ../../../docs/configuring-playbook.md:3 -msgid "" -"[Prerequisites](prerequisites.md) > [Configuring your DNS settings" -"](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) >" -" Configuring the playbook > [Installing](installing.md)" +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)" msgstr "" #: ../../../docs/configuring-playbook.md:5 -msgid "" -"If you've configured your DNS records and retrieved the playbook's source" -" code to your computer, you can start configuring the playbook. To do so," -" follow these steps inside the playbook directory:" +msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:" msgstr "" #: ../../../docs/configuring-playbook.md:7 -msgid "" -"create a directory to hold your configuration (`mkdir -p " -"inventory/host_vars/matrix.example.com` where `example.com` is your " -"\"base domain\")" +msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")" msgstr "" #: ../../../docs/configuring-playbook.md:9 -msgid "" -"copy the sample configuration file (`cp examples/vars.yml " -"inventory/host_vars/matrix.example.com/vars.yml`)" +msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" #: ../../../docs/configuring-playbook.md:11 -msgid "" -"edit the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You " -"may also take a look at the various " -"`roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's " -"something you'd like to copy over and override in your `vars.yml` " -"configuration file." +msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file." msgstr "" #: ../../../docs/configuring-playbook.md:13 @@ -71,19 +54,11 @@ msgid "edit the inventory hosts file (`inventory/hosts`) to your liking" msgstr "" #: ../../../docs/configuring-playbook.md:17 -msgid "" -"(optional, advanced) you may wish to keep your `inventory` directory " -"under version control with [git](https://git-scm.com/) or any other " -"version-control system." +msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system." msgstr "" #: ../../../docs/configuring-playbook.md:19 -msgid "" -"(optional, advanced) to run Ansible against multiple servers with " -"different `sudo` credentials, you can copy the sample inventory hosts " -"yaml file for each of your hosts: (`cp examples/host.yml " -"inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin" -"/ansible-all-hosts.sh) script [in the installation step](installing.md)." +msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)." msgstr "" #: ../../../docs/configuring-playbook.md:21 @@ -91,15 +66,11 @@ msgid "For a basic Matrix installation, that's all you need." msgstr "" #: ../../../docs/configuring-playbook.md:23 -msgid "" -"For a more custom setup, see the [Other configuration options](#other-" -"configuration-options) below." +msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below." msgstr "" #: ../../../docs/configuring-playbook.md:25 -msgid "" -"[▶️](installing.md) When you're done with all the configuration you'd " -"like to do, continue with [Installing](installing.md)." +msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)." msgstr "" #: ../../../docs/configuring-playbook.md:27 @@ -115,22 +86,15 @@ msgid "Homeserver configuration:" msgstr "" #: ../../../docs/configuring-playbook.md:32 -msgid "" -"[Configuring Synapse](configuring-playbook-synapse.md), if you're going " -"with the default/recommended homeserver implementation" +msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:34 -msgid "" -"[Configuring Conduit](configuring-playbook-conduit.md), if you've " -"switched to the [Conduit](https://conduit.rs) homeserver implementation" +msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:36 -msgid "" -"[Configuring Dendrite](configuring-playbook-dendrite.md), if you've " -"switched to the [Dendrite](https://matrix-org.github.io/dendrite) " -"homeserver implementation" +msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:38 @@ -138,33 +102,23 @@ msgid "Server components:" msgstr "" #: ../../../docs/configuring-playbook.md:39 -msgid "" -"[Using an external PostgreSQL server](configuring-playbook-external-" -"postgres.md)" +msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)" msgstr "" #: ../../../docs/configuring-playbook.md:41 -msgid "" -"[Adjusting TURN server configuration](configuring-playbook-turn.md) " -"(advanced)" +msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:43 -msgid "" -"[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) " -"(advanced)" +msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:45 -msgid "" -"[Using your own webserver, instead of this playbook's Traefik reverse-" -"proxy](configuring-playbook-own-webserver.md) (advanced)" +msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:47 -msgid "" -"[Adjusting SSL certificate retrieval](configuring-playbook-ssl-" -"certificates.md) (advanced)" +msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:49 @@ -184,9 +138,7 @@ msgid "Server connectivity:" msgstr "" #: ../../../docs/configuring-playbook.md:56 -msgid "" -"[Enabling Telemetry for your Matrix server](configuring-playbook-" -"telemetry.md)" +msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)" msgstr "" #: ../../../docs/configuring-playbook.md:58 @@ -202,31 +154,19 @@ msgid "Web clients for Matrix that you can host on your own domains." msgstr "" #: ../../../docs/configuring-playbook.md:64 -msgid "" -"[Configuring Element Web](configuring-playbook-client-element-web.md), if" -" you're going with the default/recommended client" +msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client" msgstr "" #: ../../../docs/configuring-playbook.md:66 -msgid "" -"[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've" -" enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a " -"lightweight Matrix client with legacy and mobile browser support" +msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support" msgstr "" #: ../../../docs/configuring-playbook.md:68 -msgid "" -"[Setting up Cinny](configuring-playbook-client-cinny.md), if you've " -"enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing " -"primarily on simple, elegant and secure interface" +msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface" msgstr "" #: ../../../docs/configuring-playbook.md:70 -msgid "" -"[Setting up SchildiChat Web](configuring-playbook-client-schildichat-" -"web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a " -"web client based on [Element Web](https://element.io/) with some extras " -"and tweaks" +msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks" msgstr "" #: ../../../docs/configuring-playbook.md:72 @@ -238,16 +178,11 @@ msgid "Extend and modify how users are authenticated on your homeserver." msgstr "" #: ../../../docs/configuring-playbook.md:76 -msgid "" -"[Setting up Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md) (Next-generation auth for Matrix, based on " -"OAuth 2.0/OIDC)" +msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)" msgstr "" #: ../../../docs/configuring-playbook.md:78 -msgid "" -"[Setting up Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md)" +msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)" msgstr "" #: ../../../docs/configuring-playbook.md:80 @@ -255,45 +190,31 @@ msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)" msgstr "" #: ../../../docs/configuring-playbook.md:82 -msgid "" -"[Setting up matrix-registration](configuring-playbook-matrix-" -"registration.md)" +msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../docs/configuring-playbook.md:84 -msgid "" -"[Setting up the REST authentication password provider module" -"](configuring-playbook-rest-auth.md) (advanced)" +msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:86 -msgid "" -"[Setting up the Shared Secret Auth password provider module](configuring-" -"playbook-shared-secret-auth.md) (advanced)" +msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:88 -msgid "" -"[Setting up the LDAP authentication password provider module" -"](configuring-playbook-ldap-auth.md) (advanced)" +msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:90 -msgid "" -"[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-" -"ldap-registration-proxy.md) (advanced)" +msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:92 -msgid "" -"[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-" -"antispam.md) (advanced)" +msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:94 -msgid "" -"[Setting up Matrix User Verification Service](configuring-playbook-user-" -"verification-service.md) (advanced)" +msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:96 @@ -305,21 +226,15 @@ msgid "Use alternative file storage to the default `media_store` folder." msgstr "" #: ../../../docs/configuring-playbook.md:100 -msgid "" -"[Storing Matrix media files on Amazon S3 with Goofys](configuring-" -"playbook-s3-goofys.md)" +msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../docs/configuring-playbook.md:102 -msgid "" -"[Storing Synapse media files on Amazon S3 or another compatible Object " -"Storage](configuring-playbook-s3.md)" +msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)" msgstr "" #: ../../../docs/configuring-playbook.md:104 -msgid "" -"[Storing Matrix media files using matrix-media-repo](configuring-" -"playbook-matrix-media-repo.md)" +msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" #: ../../../docs/configuring-playbook.md:106 @@ -327,155 +242,103 @@ msgid "Bridging other networks" msgstr "" #: ../../../docs/configuring-playbook.md:108 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../docs/configuring-playbook.md:110 -msgid "" -"[Setting up Mautrix Discord bridging](configuring-playbook-bridge-" -"mautrix-discord.md)" +msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:112 -msgid "" -"[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-" -"mautrix-telegram.md)" +msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:114 -msgid "" -"[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-" -"slack.md)" +msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:116 -msgid "" -"[Setting up Mautrix Google Messages bridging](configuring-playbook-" -"bridge-mautrix-gmessages.md)" +msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)" msgstr "" #: ../../../docs/configuring-playbook.md:118 -msgid "" -"[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-" -"mautrix-whatsapp.md)" +msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)" msgstr "" #: ../../../docs/configuring-playbook.md:120 -msgid "" -"[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-" -"bridge-mautrix-meta-instagram.md)" +msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:122 -msgid "" -"[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-" -"bridge-mautrix-meta-messenger.md)" +msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)" msgstr "" #: ../../../docs/configuring-playbook.md:124 -msgid "" -"[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-" -"mautrix-googlechat.md)" +msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)" msgstr "" #: ../../../docs/configuring-playbook.md:126 -msgid "" -"[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-" -"mautrix-twitter.md)" +msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:128 -msgid "" -"[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-" -"signal.md)" +msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)" msgstr "" #: ../../../docs/configuring-playbook.md:130 -msgid "" -"[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage" -"](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)" msgstr "" #: ../../../docs/configuring-playbook.md:132 -msgid "" -"[Setting up Appservice IRC bridging](configuring-playbook-bridge-" -"appservice-irc.md)" +msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../docs/configuring-playbook.md:134 -msgid "" -"[Setting up Appservice Discord bridging](configuring-playbook-bridge-" -"appservice-discord.md)" +msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:136 -msgid "" -"[Setting up Appservice Slack bridging](configuring-playbook-bridge-" -"appservice-slack.md)" +msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:138 -msgid "" -"[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-" -"appservice-kakaotalk.md)" +msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../docs/configuring-playbook.md:140 -msgid "" -"[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-" -"linkedin.md)" +msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)" msgstr "" #: ../../../docs/configuring-playbook.md:142 -msgid "" -"[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a" -" bridge between Matrix and multiple project management services, such as " -"[GitHub](https://github.com), [GitLab](https://about.gitlab.com) and " -"[JIRA](https://www.atlassian.com/software/jira)." +msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)." msgstr "" #: ../../../docs/configuring-playbook.md:144 -msgid "" -"[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-" -"puppet-slack.md)" +msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:146 -msgid "" -"[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-" -"puppet-instagram.md)" +msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:148 -msgid "" -"[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-" -"puppet-twitter.md)" +msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:150 -msgid "" -"[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-" -"puppet-discord.md)" +msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:152 -msgid "" -"[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-" -"puppet-groupme.md)" +msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)" msgstr "" #: ../../../docs/configuring-playbook.md:154 -msgid "" -"[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-" -"puppet-steam.md)" +msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)" msgstr "" #: ../../../docs/configuring-playbook.md:156 -msgid "" -"[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-" -"skype-bridge.md)" +msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)" msgstr "" #: ../../../docs/configuring-playbook.md:158 @@ -483,21 +346,15 @@ msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)" msgstr "" #: ../../../docs/configuring-playbook.md:160 -msgid "" -"[Setting up Postmoogle email bridging](configuring-playbook-bridge-" -"postmoogle.md)" +msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)" msgstr "" #: ../../../docs/configuring-playbook.md:162 -msgid "" -"[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-" -"bridge-sms.md)" +msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)" msgstr "" #: ../../../docs/configuring-playbook.md:164 -msgid "" -"[Setting up Heisenbridge bouncer-style IRC bridging](configuring-" -"playbook-bridge-heisenbridge.md)" +msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)" msgstr "" #: ../../../docs/configuring-playbook.md:166 @@ -513,66 +370,39 @@ msgid "Bots provide various additional functionality to your installation." msgstr "" #: ../../../docs/configuring-playbook.md:172 -msgid "" -"[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through " -"which you can talk to various " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) " -"services ([OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) and " -"[others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" +msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" msgstr "" #: ../../../docs/configuring-playbook.md:174 -msgid "" -"[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-" -"reminder-bot.md) - a bot to remind you about stuff" +msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff" msgstr "" #: ../../../docs/configuring-playbook.md:176 -msgid "" -"[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-" -"registration-bot.md) - a bot to create and manage registration tokens to " -"invite users" +msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users" msgstr "" #: ../../../docs/configuring-playbook.md:178 -msgid "" -"[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based " -"Matrix bot system" +msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system" msgstr "" #: ../../../docs/configuring-playbook.md:180 -msgid "" -"[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk " -"bot" +msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot" msgstr "" #: ../../../docs/configuring-playbook.md:182 -msgid "" -"[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation " -"tool/bot" +msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot" msgstr "" #: ../../../docs/configuring-playbook.md:184 -msgid "" -"[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a " -"moderation tool/bot, forked from Mjolnir and maintained by its former " -"leader developer" +msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer" msgstr "" #: ../../../docs/configuring-playbook.md:186 -msgid "" -"[Setting up Draupnir for all/D4A](configuring-playbook-appservice-" -"draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-" -"draupnir.md) mentioned above, but running in appservice mode and " -"supporting multiple instances" +msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances" msgstr "" #: ../../../docs/configuring-playbook.md:188 -msgid "" -"[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you" -" can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" msgstr "" #: ../../../docs/configuring-playbook.md:190 @@ -580,39 +410,27 @@ msgid "Administration" msgstr "" #: ../../../docs/configuring-playbook.md:192 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../docs/configuring-playbook.md:194 -msgid "" -"[Setting up Prometheus Alertmanager integration via matrix-alertmanager-" -"receiver](configuring-playbook-alertmanager-receiver.md)" +msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../docs/configuring-playbook.md:196 -msgid "" -"[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server" -"](configuring-playbook-prometheus-grafana.md)" +msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" msgstr "" #: ../../../docs/configuring-playbook.md:198 -msgid "" -"[Enabling metrics and graphs for NginX logs](configuring-playbook-" -"prometheus-nginxlog.md)" +msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)" msgstr "" #: ../../../docs/configuring-playbook.md:200 -msgid "" -"[Setting up the rageshake bug report server](configuring-playbook-" -"rageshake.md)" +msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)" msgstr "" #: ../../../docs/configuring-playbook.md:202 -msgid "" -"[Enabling synapse-usage-exporter for Synapse usage statistics" -"](configuring-playbook-synapse-usage-exporter.md)" +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:204 @@ -620,15 +438,11 @@ msgid "Backups:" msgstr "" #: ../../../docs/configuring-playbook.md:205 -msgid "" -"[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full " -"Matrix server backup solution, including the Postgres database" +msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database" msgstr "" #: ../../../docs/configuring-playbook.md:207 -msgid "" -"[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a" -" Postgres-database backup solution (note: does not include other files)" +msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)" msgstr "" #: ../../../docs/configuring-playbook.md:209 @@ -640,21 +454,15 @@ msgid "Various services that don't fit any other categories." msgstr "" #: ../../../docs/configuring-playbook.md:213 -msgid "" -"[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-" -"auto-accept-invite.md)" +msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../docs/configuring-playbook.md:215 -msgid "" -"[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-" -"compressor.md) for compressing the database on Synapse homeservers" +msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers" msgstr "" #: ../../../docs/configuring-playbook.md:217 -msgid "" -"[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) " -"(advanced)" +msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:219 @@ -662,21 +470,15 @@ msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" msgstr "" #: ../../../docs/configuring-playbook.md:221 -msgid "" -"[Setting up the Jitsi video-conferencing platform](configuring-playbook-" -"jitsi.md)" +msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)" msgstr "" #: ../../../docs/configuring-playbook.md:223 -msgid "" -"[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a" -" federated comment system built on Matrix" +msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix" msgstr "" #: ../../../docs/configuring-playbook.md:225 -msgid "" -"[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-" -"pantalaimon.md) (advanced)" +msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:227 @@ -684,9 +486,7 @@ msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" msgstr "" #: ../../../docs/configuring-playbook.md:229 -msgid "" -"[Setting up the ntfy push notifications server](configuring-playbook-" -"ntfy.md)" +msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)" msgstr "" #: ../../../docs/configuring-playbook.md:231 @@ -694,84 +494,41 @@ msgid "Deprecated / unmaintained / removed services" msgstr "" #: ../../../docs/configuring-playbook.md:233 -msgid "" -"**Note**: since a deprecated or unmaintained service will not be updated," -" its bug or vulnerability will be unlikely to get patched. It is " -"recommended to migrate from the service to an alternative if any, and " -"make sure to do your own research before you decide to keep it running " -"nonetheless." +msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless." msgstr "" #: ../../../docs/configuring-playbook.md:235 -msgid "" -"[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-" -"proxy.md) for clients which require Sliding Sync support (like old " -"Element X versions, before it got switched to Simplified Sliding Sync)" +msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)" msgstr "" #: ../../../docs/configuring-playbook.md:237 -msgid "" -"[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-" -"appservice-webhooks.md) (deprecated; the bridge's author suggests taking " -"a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) as a replacement, which can also be installed using [this " -"playbook](configuring-playbook-bridge-hookshot.md))" +msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:239 -msgid "" -"[Setting up the Dimension integration manager](configuring-playbook-" -"dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/2806#issuecomment-1673559299); after " -"[installing](installing.md))" +msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))" msgstr "" #: ../../../docs/configuring-playbook.md:241 -msgid "" -"[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; " -"the bridge's author suggests taking a look at [matrix-" -"hookshot](https://github.com/matrix-org/matrix-hookshot) as a " -"replacement, which can also be installed using [this playbook" -"](configuring-playbook-bridge-hookshot.md))" +msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:243 -msgid "" -"[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) " -"(unmaintained; the bridge's author suggests taking a look at " -"[baibot](https://github.com/etkecc/baibot) as a replacement, which can " -"also be installed using [this playbook](configuring-playbook-bot-" -"baibot.md))" +msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:245 -msgid "" -"[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-" -"mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram " -"bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-" -"meta-messenger.md))" +msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))" msgstr "" #: ../../../docs/configuring-playbook.md:247 -msgid "" -"[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-" -"mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with " -"[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" +msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" msgstr "" #: ../../../docs/configuring-playbook.md:249 -msgid "" -"[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-" -"mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram " -"bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-" -"meta-instagram.md))" +msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" msgstr "" #: ../../../docs/configuring-playbook.md:251 -msgid "" -"[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-" -"puppet-skype.md) (removed; this component has been broken for a long " -"time, so it has been removed from the playbook. Consider [setting up Go " -"Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" +msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po index 669f9baa0..19ba61dcd 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po @@ -22,10 +22,7 @@ msgid "Configuring Service Discovery via .well-known" msgstr "" #: ../../../docs/configuring-well-known.md:3 -msgid "" -"This documentation page explains how to configure Service discovery via " -"`/.well-known/` files. Service discovery is a way for the Matrix network " -"to discover where a Matrix server is." +msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is." msgstr "" #: ../../../docs/configuring-well-known.md:5 @@ -33,34 +30,19 @@ msgid "Types of well-known service discovery mechanism" msgstr "" #: ../../../docs/configuring-well-known.md:7 -msgid "" -"There are 3 types of well-known service discovery mechanism that Matrix " -"makes use of:" +msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:" msgstr "" #: ../../../docs/configuring-well-known.md:9 -msgid "" -"(important) **Federation Server discovery** (`/.well-" -"known/matrix/server`) -- assists other servers in the Matrix network with" -" finding your server. With the default playbook configuration specified " -"on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " -"this is necessary for federation to work. Without a proper configuration," -" your server will effectively not be part of the Matrix network." +msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/configuring-well-known.md:11 -msgid "" -"(less important) **Client Server discovery** (`/.well-" -"known/matrix/client`) -- assists programs that you use to connect to your" -" server (e.g. Element Web), so that they can make it more convenient for " -"you by automatically configuring the \"Homeserver URL\" and \"Identity " -"Server URL\" addresses." +msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses." msgstr "" #: ../../../docs/configuring-well-known.md:13 -msgid "" -"(optional) **Support service discovery** (`/.well-known/matrix/support`) " -"-- returns server admin contact and support page of the domain." +msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain." msgstr "" #: ../../../docs/configuring-well-known.md:15 @@ -68,35 +50,19 @@ msgid "Federation Server Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:17 -msgid "" -"All services created by this playbook are meant to be installed on their " -"own server (such as `matrix.example.com`), instead of the base domain " -"(`example.com`)." +msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:19 -msgid "" -"As [per the Server-Server " -"specification](https://matrix.org/docs/spec/server_server/r0.1.0.html" -"#server-discovery), in order to use a short Matrix user ID like " -"`@alice:example.com` instead of `@alice:matrix.example.com` while hosting" -" services on a subdomain such as `matrix.example.com`, the Matrix network" -" needs to be instructed of [server delegation](howto-server-" -"delegation.md) / redirection." +msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection." msgstr "" #: ../../../docs/configuring-well-known.md:21 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" #: ../../../docs/configuring-well-known.md:23 -msgid "" -"If you set up the DNS SRV record for server delegation instead, take a " -"look at this documentation for more information: [Server Delegation via a" -" DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-" -"via-a-dns-srv-record-advanced)" +msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/configuring-well-known.md:25 @@ -104,46 +70,23 @@ msgid "Client Server Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:27 -msgid "" -"Client Server Service discovery lets various client programs which " -"support it, to receive a full user ID (e.g. `@alice:example.com`) and " -"determine where the Matrix server is automatically (e.g. " -"`https://matrix.example.com`)." +msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:29 -msgid "" -"This lets you (and your users) easily connect to your Matrix server " -"without having to customize connection URLs. When using client programs " -"that support it, you won't need to point them to " -"`https://matrix.example.com` in Custom Server options manually anymore. " -"The connection URL would be discovered automatically from your full " -"username." +msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username." msgstr "" #: ../../../docs/configuring-well-known.md:31 -msgid "" -"Without /.well-known/matrix/client, the client will make the wrong " -"\"homeserver URL\" assumption (it will default to using " -"https://example.com, and users will need to notice and adjust it manually" -" (changing it to https://matrix.example.com)." +msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)." msgstr "" #: ../../../docs/configuring-well-known.md:33 -msgid "" -"As [per the Client-Server " -"specification](https://matrix.org/docs/spec/client_server/r0.4.0.html" -"#server-discovery) Matrix does Client Server service discovery using a " -"`/.well-known/matrix/client` file hosted on the base domain (e.g. " -"`example.com`)." +msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:35 -msgid "" -"However, this playbook installs your Matrix server on another domain " -"(e.g. `matrix.example.com`) and not on the base domain (e.g. " -"`example.com`), so it takes a little extra manual effort to set up the " -"file." +msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file." msgstr "" #: ../../../docs/configuring-well-known.md:37 @@ -151,20 +94,11 @@ msgid "(Optional) Support Service Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:39 -msgid "" -"[MSC 1929](https://github.com/matrix-org/matrix-spec-" -"proposals/pull/1929), which was added to [Matrix Specification version " -"v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-" -"knownmatrixsupport), specifies a way to add contact details of admins, as" -" well as a link to a support page for users who are having issues with " -"the service. Automated services may also index this information and use " -"it for abuse reports, etc." +msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc." msgstr "" #: ../../../docs/configuring-well-known.md:41 -msgid "" -"To enable it, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-well-known.md:62 @@ -172,9 +106,7 @@ msgid "Installing well-known files on the base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:64 -msgid "" -"To implement the service discovery mechanisms, your base domain's server " -"(e.g. `example.com`) needs to run an HTTPS-capable webserver." +msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver." msgstr "" #: ../../../docs/configuring-well-known.md:66 @@ -182,33 +114,19 @@ msgid "Serving the base domain from the Matrix server via the playbook" msgstr "" #: ../../../docs/configuring-well-known.md:68 -msgid "" -"If you don't have a server for your base domain at all, you can use the " -"Matrix server for this. If you don't need the base domain (e.g. " -"`example.com`) for anything else (hosting a website, etc.), you can point" -" it to the Matrix server's IP address and tell the playbook to configure " -"it." +msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it." msgstr "" #: ../../../docs/configuring-well-known.md:70 -msgid "" -"**This is the easiest way to set up well-known serving** -- letting the " -"playbook handle the whole base domain for you (including SSL " -"certificates, etc.) and take care to serve the appropriate well-known " -"files automatically." +msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically." msgstr "" #: ../../../docs/configuring-well-known.md:72 -msgid "" -"If you decide to go this route, you don't need to read ahead in this " -"document. Instead, go to [Serving the base domain](configuring-playbook-" -"base-domain-serving.md) to learn how the playbook can help you set it up." +msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up." msgstr "" #: ../../../docs/configuring-well-known.md:74 -msgid "" -"However, if you need to use the base domain for other things, this method" -" is less suitable than the one explained below." +msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below." msgstr "" #: ../../../docs/configuring-well-known.md:76 @@ -216,25 +134,15 @@ msgid "Manually installing well-known files on the base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:78 -msgid "" -"If you're managing the base domain by yourself somehow, you'll need to " -"set up serving of some `/.well-known/matrix/*` files from it via HTTPS." +msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS." msgstr "" #: ../../../docs/configuring-well-known.md:80 -msgid "" -"To make things easy for you to set up, this playbook generates and hosts " -"a few well-known files on the Matrix domain's server. The files are " -"generated at the `/matrix/static-files/public/.well-known/matrix/` path " -"on the server and hosted at URLs like `https://matrix.example.com/.well-" -"known/matrix/server` and `https://matrix.example.com/.well-" -"known/matrix/client`, even though this is the wrong place to host them." +msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them." msgstr "" #: ../../../docs/configuring-well-known.md:82 -msgid "" -"You have two options when it comes to installing the files on the base " -"domain's server:" +msgid "You have two options when it comes to installing the files on the base domain's server:" msgstr "" #: ../../../docs/configuring-well-known.md:84 @@ -242,9 +150,7 @@ msgid "(Option 1): **Copying the files manually** to your base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:86 -msgid "" -"**Hint**: Option 2 is generally a better way to do this. Make sure to go " -"with it, if possible." +msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible." msgstr "" #: ../../../docs/configuring-well-known.md:88 @@ -252,40 +158,19 @@ msgid "All you need to do is:" msgstr "" #: ../../../docs/configuring-well-known.md:90 -msgid "" -"copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from " -"the Matrix server (e.g. `matrix.example.com`) to your base domain's " -"server (`example.com`). You can find these files in the `/matrix/static-" -"files/.well-known/matrix` directory on the Matrix server. They are also " -"accessible on URLs like this: `https://matrix.example.com/.well-" -"known/matrix/server` (same for `client`)." +msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)." msgstr "" #: ../../../docs/configuring-well-known.md:92 -msgid "" -"set up the server at your base domain (e.g. `example.com`) so that it " -"adds an extra HTTP header when serving the `/.well-known/matrix/client` " -"file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the" -" `Access-Control-Allow-Origin` header should be set with a value of `*`. " -"If you don't do this step, web-based Matrix clients (like Element Web) " -"may fail to work. Setting up headers for the `/.well-known/matrix/server`" -" file is not necessary, as this file is only consumed by non-browsers, " -"which don't care about CORS." +msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS." msgstr "" #: ../../../docs/configuring-well-known.md:94 -msgid "" -"This is relatively easy to do and possibly your only choice if you can " -"only host static files from the base domain's server. It is, however, **a" -" little fragile**, as future updates performed by this playbook may " -"regenerate the well-known files and you may need to notice that and copy " -"them over again." +msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again." msgstr "" #: ../../../docs/configuring-well-known.md:96 -msgid "" -"(Option 2): **Setting up reverse-proxying** of the well-known files from " -"the base domain's server to the Matrix server" +msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server" msgstr "" #: ../../../docs/configuring-well-known.md:98 @@ -293,19 +178,11 @@ msgid "This option is less fragile and generally better." msgstr "" #: ../../../docs/configuring-well-known.md:100 -msgid "" -"On the base domain's server (e.g. `example.com`), you can set up reverse-" -"proxying, so that any access for the `/.well-known/matrix` location " -"prefix is forwarded to the Matrix domain's server (e.g. " -"`matrix.example.com`)." +msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:102 -msgid "" -"With this method, you **don't need** to add special HTTP headers for " -"[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons " -"(like `Access-Control-Allow-Origin`), because your Matrix server (where " -"requests ultimately go) will be configured by this playbook correctly." +msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly." msgstr "" #: ../../../docs/configuring-well-known.md:104 @@ -325,11 +202,7 @@ msgid "**For HAProxy**, it would be something like this:" msgstr "" #: ../../../docs/configuring-well-known.md:164 -msgid "" -"**For Netlify**, configure a " -"[redirect](https://docs.netlify.com/routing/redirects/) using a " -"`_redirects` file in the [publish directory](https://docs.netlify.com" -"/configure-builds/overview/#definitions) with contents like this:" +msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:" msgstr "" #: ../../../docs/configuring-well-known.md:170 @@ -341,9 +214,7 @@ msgid "Add a custom origin with matrix.example.com to your distribution" msgstr "" #: ../../../docs/configuring-well-known.md:173 -msgid "" -"Add two behaviors, one for `.well-known/matrix/client` and one for " -"`.well-known/matrix/server` and point them to your new origin." +msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin." msgstr "" #: ../../../docs/configuring-well-known.md:175 @@ -351,15 +222,11 @@ msgid "Make sure to:" msgstr "" #: ../../../docs/configuring-well-known.md:177 -msgid "" -"**replace `example.com`** in the server configuration with your actual " -"domain name" +msgid "**replace `example.com`** in the server configuration with your actual domain name" msgstr "" #: ../../../docs/configuring-well-known.md:178 -msgid "" -"and: to **do this for the HTTPS-enabled server block**, as that's where " -"Matrix expects the file to be" +msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be" msgstr "" #: ../../../docs/configuring-well-known.md:180 @@ -367,10 +234,7 @@ msgid "Confirming it works" msgstr "" #: ../../../docs/configuring-well-known.md:182 -msgid "" -"No matter which method you've used to set up the well-known files, if " -"you've done it correctly you should be able to see a JSON file at these " -"URLs:" +msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:" msgstr "" #: ../../../docs/configuring-well-known.md:184 @@ -386,8 +250,5 @@ msgid "`https://example.com/.well-known/matrix/support`" msgstr "" #: ../../../docs/configuring-well-known.md:188 -msgid "" -"You can also check if everything is configured correctly, by [checking if" -" services work](maintenance-checking-services.md)." +msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/container-images.po b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po index 388d1b52e..9fd9bdc81 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/container-images.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po @@ -26,15 +26,11 @@ msgid "Container images used by the playbook" msgstr "" #: ../../../docs/container-images.md:3 -msgid "" -"This page summarizes the container ([Docker](https://www.docker.com/)) " -"images used by the playbook when setting up your server." +msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server." msgstr "" #: ../../../docs/container-images.md:5 -msgid "" -"We try to stick to official images (provided by their respective " -"projects) as much as possible." +msgid "We try to stick to official images (provided by their respective projects) as much as possible." msgstr "" #: ../../../docs/container-images.md:7 @@ -70,9 +66,7 @@ msgid "✅" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" msgstr "" #: ../../../docs/container-images.md @@ -80,9 +74,7 @@ msgid "[Conduit](configuring-playbook-conduit.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit" -"/matrix-conduit)" +msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)" msgstr "" #: ../../../docs/container-images.md @@ -90,11 +82,7 @@ msgid "❌" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" -"source server implementation of the Matrix Specification with a focus on " -"easy setup and low system requirements" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" msgstr "" #: ../../../docs/container-images.md @@ -102,16 +90,11 @@ msgid "[Dendrite](configuring-playbook-dendrite.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg" -"/dendrite-monolith/)" +msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " -"Matrix homeserver written in Go, an alternative to Synapse." +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." msgstr "" #: ../../../docs/container-images.md:15 @@ -131,9 +114,7 @@ msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Default Matrix web client, configured to connect to your own Synapse " -"server" +msgid "Default Matrix web client, configured to connect to your own Synapse server" msgstr "" #: ../../../docs/container-images.md @@ -177,9 +158,7 @@ msgid "Server Components" msgstr "" #: ../../../docs/container-images.md:28 -msgid "" -"Services that run on the server to make the various parts of your " -"installation work." +msgid "Services that run on the server to make the various parts of your installation work." msgstr "" #: ../../../docs/container-images.md @@ -191,9 +170,7 @@ msgid "[postgres](https://hub.docker.com/_/postgres/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Database for Synapse. [Using an external PostgreSQL server](configuring-" -"playbook-external-postgres.md) is also possible." +msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible." msgstr "" #: ../../../docs/container-images.md @@ -217,10 +194,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Web server, listening on ports 80, 443 and 8448 - standing in front of " -"all the other services. Using your own webserver [is possible" -"](configuring-playbook-own-webserver.md)" +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)" msgstr "" #: ../../../docs/container-images.md @@ -232,9 +206,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"The [certbot](https://certbot.eff.org/) tool for obtaining SSL " -"certificates from [Let's Encrypt](https://letsencrypt.org/)" +msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)" msgstr "" #: ../../../docs/container-images.md @@ -246,9 +218,7 @@ msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Mail server, through which all Matrix services send outgoing email (can " -"be configured to relay through another SMTP server)" +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" msgstr "" #: ../../../docs/container-images.md @@ -272,9 +242,7 @@ msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Update dynamic DNS entries for accounts on Dynamic DNS Network Service " -"Provider" +msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider" msgstr "" #: ../../../docs/container-images.md:40 @@ -298,9 +266,7 @@ msgid "REST authentication password provider module" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-" -"auth.md)" +msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../docs/container-images.md @@ -316,9 +282,7 @@ msgid "LDAP Auth password provider module" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-" -"registration-proxy.md)" +msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)" msgstr "" #: ../../../docs/container-images.md @@ -326,9 +290,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co msgstr "" #: ../../../docs/container-images.md -msgid "" -"A proxy that handles Matrix registration requests and forwards them to " -"LDAP." +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../docs/container-images.md @@ -336,9 +298,7 @@ msgid "[matrix-registration](configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-" -"matrix-registration/)" +msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)" msgstr "" #: ../../../docs/container-images.md @@ -346,16 +306,11 @@ msgid "A simple python application to have a token based Matrix registration" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Matrix User Verification Service](configuring-playbook-user-" -"verification-service.md) (UVS)" +msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-user-verification-" -"service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-" -"service)" +msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)" msgstr "" #: ../../../docs/container-images.md @@ -363,9 +318,7 @@ msgid "Service to verify details of a user based on an Open ID token" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[synapse-simple-antispam](configuring-playbook-synapse-simple-" -"antispam.md) (advanced)" +msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" msgstr "" #: ../../../docs/container-images.md @@ -389,9 +342,7 @@ msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " -"store) storage for Synapse's content repository (`media_store`) files" +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" msgstr "" #: ../../../docs/container-images.md @@ -407,10 +358,7 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"matrix-media-repo is a highly customizable multi-domain media repository " -"for Matrix. Intended for medium to large deployments, this media repo de-" -"duplicates media while being fully compliant with the specification." +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." msgstr "" #: ../../../docs/container-images.md:64 @@ -418,9 +366,7 @@ msgid "Bridges" msgstr "" #: ../../../docs/container-images.md:66 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../docs/container-images.md @@ -520,10 +466,7 @@ msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-" -"messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-" -"instagram.md))" +msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" msgstr "" #: ../../../docs/container-images.md @@ -531,9 +474,7 @@ msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge to [Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/)" +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" msgstr "" #: ../../../docs/container-images.md @@ -565,9 +506,7 @@ msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-appservice-" -"irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" +msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" msgstr "" #: ../../../docs/container-images.md @@ -575,9 +514,7 @@ msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-" -"kakaotalk.md)" +msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../docs/container-images.md @@ -585,21 +522,15 @@ msgid "Self-building" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-discord](configuring-playbook-bridge-appservice-" -"discord.md)" +msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-" -"appservice-discord)" +msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)" msgstr "" #: ../../../docs/container-images.md @@ -611,9 +542,7 @@ msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-appservice-" -"slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" +msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" msgstr "" #: ../../../docs/container-images.md @@ -621,15 +550,11 @@ msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-" -"hookshot)" +msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge for generic webhooks and multiple project management services, " -"such as GitHub, GitLab, Figma, and Jira in particular" +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" msgstr "" #: ../../../docs/container-images.md @@ -637,10 +562,7 @@ msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[folivonet/matrix-sms-" -"bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-" -"bridge)" +msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)" msgstr "" #: ../../../docs/container-images.md @@ -668,9 +590,7 @@ msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bouncer-style bridge to " -"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../docs/container-images.md @@ -678,9 +598,7 @@ msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-" -"bridge)" +msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)" msgstr "" #: ../../../docs/container-images.md @@ -692,9 +610,7 @@ msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-" -"puppet-slack/container_registry)" +msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)" msgstr "" #: ../../../docs/container-images.md @@ -706,9 +622,7 @@ msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md) msgstr "" #: ../../../docs/container-images.md -msgid "" -"[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-" -"puppet-instagram)" +msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)" msgstr "" #: ../../../docs/container-images.md @@ -720,9 +634,7 @@ msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-" -"twitter)" +msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)" msgstr "" #: ../../../docs/container-images.md @@ -734,9 +646,7 @@ msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-" -"puppet/discord/mx-puppet-discord/container_registry)" +msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)" msgstr "" #: ../../../docs/container-images.md @@ -744,9 +654,7 @@ msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-" -"groupme)" +msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)" msgstr "" #: ../../../docs/container-images.md @@ -758,9 +666,7 @@ msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-" -"puppet-steam)" +msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)" msgstr "" #: ../../../docs/container-images.md @@ -808,11 +714,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"A bot that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you" +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" msgstr "" #: ../../../docs/container-images.md @@ -820,9 +722,7 @@ msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-" -"bot)" +msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)" msgstr "" #: ../../../docs/container-images.md @@ -830,15 +730,11 @@ msgid "Bot for scheduling one-off & recurring reminders and alarms" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-registration-bot](configuring-playbook-bot-matrix-registration-" -"bot.md)" +msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-" -"registration-bot/)" +msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)" msgstr "" #: ../../../docs/container-images.md @@ -910,40 +806,27 @@ msgid "Administration" msgstr "" #: ../../../docs/container-images.md:116 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-alertmanager-receiver](configuring-playbook-alertmanager-" -"receiver.md)" +msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio" -"/matrix-alertmanager-receiver)" +msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"client" +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md)" +msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[element-hq/matrix-authentication-service](https://ghcr.io/element-hq" -"/matrix-authentication-service)" +msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)" msgstr "" #: ../../../docs/container-images.md @@ -979,9 +862,7 @@ msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" -"exporter/) host metrics exporter" +msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter" msgstr "" #: ../../../docs/container-images.md @@ -989,11 +870,7 @@ msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Graphing tool that works well with the above two images. Our playbook " -"also adds two dashboards for [Synapse](https://github.com/element-" -"hq/synapse/tree/master/contrib/grafana) and [Node " -"Exporter](https://github.com/rfrail3/grafana-dashboards)" +msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)" msgstr "" #: ../../../docs/container-images.md @@ -1001,15 +878,11 @@ msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io" -"/martin-helmich/prometheus-nginxlog-exporter/exporter)" +msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Addon for Prometheus that gathers access logs from various nginx reverse-" -"proxies" +msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies" msgstr "" #: ../../../docs/container-images.md @@ -1037,9 +910,7 @@ msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Export the usage statistics of a Synapse homeserver to be scraped by " -"Prometheus." +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." msgstr "" #: ../../../docs/container-images.md:131 @@ -1059,15 +930,11 @@ msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Sliding Sync support for clients which require it (like old Element X " -"versions, before it got switched to Simplified Sliding Sync)" +msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-" -"invite.md)" +msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../docs/container-images.md @@ -1079,15 +946,11 @@ msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md msgstr "" #: ../../../docs/container-images.md -msgid "" -"[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-" -"synapse-compress-state/container_registry)" +msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"A cli tool that automatically compresses `state_groups` database table in" -" background." +msgid "A cli tool that automatically compresses `state_groups` database table in background." msgstr "" #: ../../../docs/container-images.md @@ -1095,9 +958,7 @@ msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-" -"corporal/)" +msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)" msgstr "" #: ../../../docs/container-images.md @@ -1157,9 +1018,7 @@ msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[cactuscomments/cactus-" -"appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" +msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" msgstr "" #: ../../../docs/container-images.md @@ -1167,9 +1026,7 @@ msgid "A federated comment system built on Matrix" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-" -"web-server)" +msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)" msgstr "" #: ../../../docs/container-images.md @@ -1213,27 +1070,19 @@ msgid "Container images of deprecated / unmaintained services" msgstr "" #: ../../../docs/container-images.md:154 -msgid "" -"The list of the deprecated or unmaintained services is available [here" -"](configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)." msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-" -"webhooks.md)" +msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live" -"/matrix-appservice-webhooks)" +msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-" -"ci.org/), [Slack](https://slack.com/) etc. pp.)" +msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)" msgstr "" #: ../../../docs/container-images.md @@ -1241,9 +1090,7 @@ msgid "[Dimension](configuring-playbook-dimension.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-" -"dimension)" +msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)" msgstr "" #: ../../../docs/container-images.md @@ -1267,9 +1114,7 @@ msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-" -"bot)" +msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)" msgstr "" #: ../../../docs/container-images.md @@ -1311,4 +1156,3 @@ msgstr "" #: ../../../docs/container-images.md msgid "Bridge to [Instagram](https://instagram.com/)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/faq.po b/i18n/locales/bg/LC_MESSAGES/docs/faq.po index d23a642e3..0c06ff7b1 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/faq.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/faq.po @@ -26,17 +26,11 @@ msgid "Frequently Asked Questions" msgstr "" #: ../../../docs/faq.md:3 -msgid "" -"This documentation page tries to answer various Frequently Asked " -"Questions about all things [Matrix](https://matrix.org/), with a focus on" -" this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How" -" does it work?](#what-is-ansible-how-does-it-work))." +msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))." msgstr "" #: ../../../docs/faq.md:5 -msgid "" -"This FAQ page does not intend to replace the [matrix.org " -"FAQ](https://matrix.org/faq/) (please see that one too)." +msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)." msgstr "" #: ../../../docs/faq.md:7 @@ -44,11 +38,7 @@ msgid "We've only started this FAQ recently, so it's still somewhat empty." msgstr "" #: ../../../docs/faq.md:9 -msgid "" -"Also, we encourage you to not dig yourself into a hole by reading way too" -" much. When you've heard enough, proceed to installation. To get started," -" see [below](#how-do-i-run-the-installation) about our installation " -"guides." +msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides." msgstr "" #: ../../../docs/faq.md:11 @@ -60,72 +50,39 @@ msgid "Where do I find more questions and answers about Matrix?" msgstr "" #: ../../../docs/faq.md:15 -msgid "" -"This is a Frequently Asked Questions page focused on this " -"[Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does " -"it work?](#what-is-ansible-how-does-it-work)) for deploying a " -"[Matrix](https://matrix.org/) server." +msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server." msgstr "" #: ../../../docs/faq.md:17 -msgid "" -"For a lot more generic questions and answers, see the [matrix.org " -"FAQ](https://matrix.org/faq/)." +msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" #: ../../../docs/faq.md:19 -msgid "" -"What is Matrix? What is Element? What is Synapse? Why are you confusing " -"me with so many terms?" +msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?" msgstr "" #: ../../../docs/faq.md:21 -msgid "" -"[Matrix](https://matrix.org/) is a new type of realtime communication " -"(chat) network, the closest analogy to which is probably \"email\"." +msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"." msgstr "" #: ../../../docs/faq.md:23 -msgid "" -"You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly " -"though. There's a *server* somewhere which stores your data " -"(`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you" -" access it by using these \"email\" protocols via some *client* program " -"(Outlook, Thunderbird, some website, etc)." +msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)." msgstr "" #: ../../../docs/faq.md:25 -msgid "" -"In the world of the Matrix chat protocol, there are various client " -"programs. The first and currently most full-featured one is called " -"[Element](https://element.io/) (used to be called Riot.im and Vector.im " -"in the past). There are [many other " -"clients](https://matrix.org/clients/). You can switch clients as much as " -"you want until you find the one that is right for you on a given platform" -" (you may use Element Desktop on your desktop, but Fluffychat on your " -"phone, etc)." +msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)." msgstr "" #: ../../../docs/faq.md:27 -msgid "" -"Matrix is also like email due to the fact that there are many servers " -"around the world which can all talk to each other (you can send email " -"from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` " -"addresses). It's the same with Matrix (`@bob:example.com` can talk to " -"`@alice:example.org`)." +msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)." msgstr "" #: ../../../docs/faq.md:29 -msgid "" -"If someone else is hosting your Matrix server (you being " -"`@alice:matrix.org` or some other public server like this), all you need " -"is a Matrix client program, like Element Web or Element X Android." +msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android." msgstr "" #: ../../../docs/faq.md:31 -msgid "" -"If you'd like to host your own server (you being `@alice:example.com`), " -"you'd need to set up a Matrix server program, like Synapse." +msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse." msgstr "" #: ../../../docs/faq.md:33 @@ -133,29 +90,19 @@ msgid "In short:" msgstr "" #: ../../../docs/faq.md:35 -msgid "" -"Matrix is the protocol - a set of rules about how the chat network " -"operates" +msgid "Matrix is the protocol - a set of rules about how the chat network operates" msgstr "" #: ../../../docs/faq.md:36 -msgid "" -"Element is a client program you can use to participate on the Matrix chat" -" network via some server (yours or someone else's). There are also [many " -"other client programs](https://matrix.org/clients/)." +msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)." msgstr "" #: ../../../docs/faq.md:37 -msgid "" -"Synapse is a server program you can use to host your very own Matrix " -"server." +msgid "Synapse is a server program you can use to host your very own Matrix server." msgstr "" #: ../../../docs/faq.md:39 -msgid "" -"This FAQ here mostly focuses on installing various Matrix services using " -"the Ansible automation tool. You can learn much more about Matrix in the " -"[matrix.org FAQ](https://matrix.org/faq/)." +msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" #: ../../../docs/faq.md:41 @@ -163,22 +110,15 @@ msgid "People I wish to talk to are not on Matrix. Can I talk to them?" msgstr "" #: ../../../docs/faq.md:43 -msgid "" -"You most likely can. Besides Matrix-native chats, Matrix also supports " -"the concept of \"bridging\", which allows you to plug other networks into" -" it." +msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it." msgstr "" #: ../../../docs/faq.md:45 -msgid "" -"This Ansible playbook can help you install [tens of bridges for various " -"networks](configuring-playbook.md#bridging-other-networks)." +msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../docs/faq.md:47 -msgid "" -"Besides setting up your own bridges (preferable), you can also use some " -"[public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." +msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." msgstr "" #: ../../../docs/faq.md:49 @@ -186,50 +126,23 @@ msgid "How do I get started with Matrix?" msgstr "" #: ../../../docs/faq.md:51 -msgid "" -"One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared" -" to other chat networks) is its decentralized nature. There's not just " -"one entity (company, organization) controlling the servers. Rather " -"there's thousands of servers operated by different people - one server " -"being insecure, slow or disrespective toward its users does not affect " -"the rest of the network. To participate in that decentralization in its " -"fullest, consider hosting your own server or using some public server " -"other than the largest/default one (`matrix.org`)." +msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)." msgstr "" #: ../../../docs/faq.md:53 -msgid "" -"There are 3 ways to get into Matrix, depending on your technical ability " -"and needs:" +msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:" msgstr "" #: ../../../docs/faq.md:55 -msgid "" -"**using the existing default server** - the easiest way is to use an " -"existing server. The largest public Matrix server is `matrix.org` and " -"it's configured as a default server in clients such as [Element " -"Web](https://app.element.io) and many others. Just use Element Web on the" -" browser via that link (or [download client apps for your Desktop or " -"smartphone](https://element.io/app-for-productivity)), create an account " -"and start chatting." +msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting." msgstr "" #: ../../../docs/faq.md:57 -msgid "" -"**using some other server** - instead of using the largest public server " -"(`matrix.org`), you can use another public one. Here's a [list of public " -"Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to " -"[Element Web](https://app.element.io) or download [some other " -"client](https://matrix.org/clients/) of your choosing and adjust the " -"homeserver URL during login." +msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login." msgstr "" #: ../../../docs/faq.md:59 -msgid "" -"**using your own server** - running your own server puts you in ultimate " -"control of your data. It also lets you have your own user IDs (e.g. " -"`@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i" -"-set-up-my-own-matrix-server)." +msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)." msgstr "" #: ../../../docs/faq.md:61 @@ -237,33 +150,19 @@ msgid "How do I set up my own Matrix server?" msgstr "" #: ../../../docs/faq.md:63 -msgid "" -"Normally, you'd first choose the [Matrix](https://matrix.org/) server " -"software you'd like to run. At the time of this writing (January/2021), " -"there's only one fully-featured server program, so there's only one " -"reasonable choice. That's [Synapse](https://github.com/element-" -"hq/synapse)." +msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)." msgstr "" #: ../../../docs/faq.md:65 -msgid "" -"There are [many guides about installing " -"Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this " -"Ansible playbook is just one way of doing it." +msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it." msgstr "" #: ../../../docs/faq.md:67 -msgid "" -"Naturally, we're biased, so our usual recommendation is to go with this " -"[Ansible](https://www.ansible.com/) playbook, instead of installing " -"Synapse (and many many other things around it) manually." +msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually." msgstr "" #: ../../../docs/faq.md:69 -msgid "" -"To get started with the playbook, check out the [Quick start](quick-" -"start.md) or full installation guide (starting at the " -"[Prerequisites](prerequisites.md) page)." +msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)." msgstr "" #: ../../../docs/faq.md:71 @@ -271,31 +170,19 @@ msgid "What is Ansible? How does it work?" msgstr "" #: ../../../docs/faq.md:73 -msgid "" -"[Ansible](https://www.ansible.com/) is an automation program. This " -"\"playbook\" is a collection of tasks/scripts that will set up a " -"[Matrix](https://matrix.org/) server for you, so you don't have to " -"perform these tasks manually." +msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually." msgstr "" #: ../../../docs/faq.md:75 -msgid "" -"We have written these automated tasks for you and all you need to do is " -"execute them using the Ansible program." +msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program." msgstr "" #: ../../../docs/faq.md:77 -msgid "" -"You can install Ansible and this playbook code repository on your own " -"computer and tell it to install Matrix services at the server living at " -"`matrix.example.com`. We recommend installing Ansible on your own " -"computer." +msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer." msgstr "" #: ../../../docs/faq.md:79 -msgid "" -"Alternatively, you can download Ansible and the playbook itself directly " -"on the `matrix.example.com` server." +msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server." msgstr "" #: ../../../docs/faq.md:81 @@ -307,31 +194,19 @@ msgid "What is `just`?" msgstr "" #: ../../../docs/faq.md:85 -msgid "" -"[`just`](https://github.com/casey/just) is a modern command-runner " -"alternative to [make](https://www.gnu.org/software/make/). It can be used" -" to invoke commands with less typing." +msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing." msgstr "" #: ../../../docs/faq.md:87 -msgid "" -"The `just` utility executes shortcut commands (called \"recipes\"), which" -" invoke `ansible-playbook`, `ansible-galaxy` or " -"[`agru`](https://github.com/etkecc/agru) (depending on what is available " -"in your system). The targets of the recipes are defined in " -"[`justfile`](../justfile)." +msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)." msgstr "" #: ../../../docs/faq.md:89 -msgid "" -"For details about `just` commands, take a look at: [Running `just` " -"commands](just.md)." +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/faq.md:91 -msgid "" -"The playbook also contains a `Makefile` for the `make` tool, but most of " -"the just recipes are not available as targets in the `Makefile`." +msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`." msgstr "" #: ../../../docs/faq.md:93 @@ -339,27 +214,19 @@ msgid "Why use this playbook and not install Synapse and other things manually?" msgstr "" #: ../../../docs/faq.md:95 -msgid "" -"There are various guides telling you how easy it is to install " -"[Synapse](https://github.com/element-hq/synapse)." +msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)." msgstr "" #: ../../../docs/faq.md:97 -msgid "" -"Reading the documentation of this Ansible playbook, you may also be " -"thinking:" +msgid "Reading the documentation of this Ansible playbook, you may also be thinking:" msgstr "" #: ../../../docs/faq.md:99 -msgid "" -"I don't know what [Ansible](https://www.ansible.com/) is. I don't know " -"what [Docker](https://www.docker.com/) is. This looks more complicated." +msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated." msgstr "" #: ../../../docs/faq.md:101 -msgid "" -".. so you may be leaning toward [installing Synapse " -"manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." +msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." msgstr "" #: ../../../docs/faq.md:103 @@ -367,61 +234,35 @@ msgid "The problem with a manual installation is:" msgstr "" #: ../../../docs/faq.md:105 -msgid "" -"Synapse is written in Python. If not packaged for your distribution, " -"you'd need to install various Python modules, etc., and keep them " -"updated." +msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated." msgstr "" #: ../../../docs/faq.md:106 -msgid "" -"Synapse requires a [Postgres](https://www.postgresql.org/) database (it " -"can run on SQLite, but that's very much discouraged). So you'd need to " -"install Postgres as well." +msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well." msgstr "" #: ../../../docs/faq.md:107 -msgid "" -"you may also need a reverse-proxy server in front of it (nginx, Apache), " -"so you'd need to be familiar with that" +msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that" msgstr "" #: ../../../docs/faq.md:108 -msgid "" -"SSL is required, so you'd need to obtain Let's Encrypt (or other free or " -"non-free) certificates for one or more domain names. You'd need to be " -"familiar with [certbot](https://certbot.eff.org/) (when using Let's " -"Encrypt) or similar software." +msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software." msgstr "" #: ../../../docs/faq.md:109 -msgid "" -"for each additional component you'd like to add (client like " -"[Element](https://element.io), bridge to some other chat network, " -"integration manager (stickers, other services, Identity Manager, etc.), " -"you'll need to spend extra time installing and wiring it with the rest of" -" the system in a way that works." +msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works." msgstr "" #: ../../../docs/faq.md:110 -msgid "" -"you'll likely get slower updates for all of these components, depending " -"on your distro packaging or your own time and ability" +msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability" msgstr "" #: ../../../docs/faq.md:112 -msgid "" -"The playbook, on the other hand, installs a bunch of components for you " -"by default, obtains SSL certificates for you, etc. If you'd like, you can" -" enable various bridges and other services with very little effort. All " -"the components are wired to work together." +msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together." msgstr "" #: ../../../docs/faq.md:114 -msgid "" -"All services run in Docker containers (most being officially provided by " -"each component's developers), so we're not at the mercy of distro " -"packaging." +msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging." msgstr "" #: ../../../docs/faq.md:116 @@ -433,15 +274,11 @@ msgid "Reasons are similar to the reasons for not installing manually." msgstr "" #: ../../../docs/faq.md:120 -msgid "" -"Besides Synapse, you'd need other things - a Postgres database, likely " -"the [Element](https://element.io) client, etc., etc." +msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc." msgstr "" #: ../../../docs/faq.md:122 -msgid "" -"Using the playbook, you get all these components in a way that works well" -" together out of the box." +msgid "Using the playbook, you get all these components in a way that works well together out of the box." msgstr "" #: ../../../docs/faq.md:124 @@ -453,29 +290,19 @@ msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." msgstr "" #: ../../../docs/faq.md:128 -msgid "" -"What's different about this Ansible playbook compared to [EMnify/matrix-" -"synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-" -"deploy)?" +msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?" msgstr "" #: ../../../docs/faq.md:130 -msgid "" -"This is similar to the [EMnify/matrix-synapse-auto-" -"deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible " -"deployment, but:" +msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:" msgstr "" #: ../../../docs/faq.md:132 -msgid "" -"this one is a complete Ansible playbook (instead of just a role), so it's" -" **easier to run** - especially for folks not familiar with Ansible" +msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible" msgstr "" #: ../../../docs/faq.md:134 -msgid "" -"this one installs and hooks together **a lot more Matrix-related " -"services** for you (see above)" +msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)" msgstr "" #: ../../../docs/faq.md:136 @@ -483,56 +310,35 @@ msgid "this one **can be executed more than once** without causing trouble" msgstr "" #: ../../../docs/faq.md:138 -msgid "" -"works on various distros: **CentOS** (7.0+), Debian-based distributions " -"(**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" +msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" msgstr "" #: ../../../docs/faq.md:140 -msgid "" -"this one installs everything in a single directory (`/matrix` by default)" -" and **doesn't \"contaminate\" your server** with files all over the " -"place" +msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place" msgstr "" #: ../../../docs/faq.md:142 -msgid "" -"this one **doesn't necessarily take over** ports 80 and 443. By default, " -"it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but " -"you can also [use your own webserver](configuring-playbook-own-" -"webserver.md)" +msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)" msgstr "" #: ../../../docs/faq.md:144 -msgid "" -"this one **runs everything in Docker containers**, so it's likely more " -"predictable and less fragile (see [Docker images used by this playbook" -"](container-images.md))" +msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))" msgstr "" #: ../../../docs/faq.md:146 -msgid "" -"this one retrieves and automatically renews free [Let's " -"Encrypt](https://letsencrypt.org/) **SSL certificates** for you" +msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you" msgstr "" #: ../../../docs/faq.md:148 -msgid "" -"this one optionally can store the `media_store` content repository files " -"on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files" -" on the server's filesystem)" +msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)" msgstr "" #: ../../../docs/faq.md:150 -msgid "" -"this one optionally **allows you to use an external PostgreSQL server** " -"for Synapse's database (but defaults to running one in a container)" +msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)" msgstr "" #: ../../../docs/faq.md:152 -msgid "" -"helps you **import data from a previous installation** (so you can " -"migrate your manual virtualenv/Docker setup to a more managed one)" +msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)" msgstr "" #: ../../../docs/faq.md:154 @@ -544,9 +350,7 @@ msgid "Server-related" msgstr "" #: ../../../docs/faq.md:158 -msgid "" -"What kind of server do I need to install Matrix using this Ansible " -"playbook?" +msgid "What kind of server do I need to install Matrix using this Ansible playbook?" msgstr "" #: ../../../docs/faq.md:160 @@ -558,30 +362,19 @@ msgid "Why not run Matrix on Kubernetes?" msgstr "" #: ../../../docs/faq.md:164 -msgid "" -"There's no reason not to run Matrix on " -"[Kubernetes](https://kubernetes.io/)." +msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)." msgstr "" #: ../../../docs/faq.md:166 -msgid "" -"However, that's overly complicated for thousands of us who just want to " -"run a single small (and sometimes not so small) Matrix server, either " -"using \"cloud\" servers or even a [Raspberry " -"Pi](https://www.raspberrypi.org/) at home." +msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home." msgstr "" #: ../../../docs/faq.md:168 -msgid "" -"For us, a Kubernetes-based setup which requires a cluster of multiple " -"computers and is more technically-involved is a no-go." +msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go." msgstr "" #: ../../../docs/faq.md:170 -msgid "" -"There are others working on automating a Matrix-on-Kubernetes setup, such" -" as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21" -"/matrix-chart." +msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart." msgstr "" #: ../../../docs/faq.md:172 @@ -589,16 +382,11 @@ msgid "Why don't you use Podman instead of Docker?" msgstr "" #: ../../../docs/faq.md:174 -msgid "" -"We like the philosophy of a daemonless container runtime, but " -"[Podman](https://podman.io) is just not ready for our use case yet." +msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet." msgstr "" #: ../../../docs/faq.md:176 -msgid "" -"Learn more about our past experiences/attempts to give Podman a chance, " -"by reading [this issue](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/issues/520)." +msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)." msgstr "" #: ../../../docs/faq.md:178 @@ -610,21 +398,15 @@ msgid "Why use Docker?" msgstr "" #: ../../../docs/faq.md:182 -msgid "" -"[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the " -"other one being [systemd](https://systemd.io/))." +msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))." msgstr "" #: ../../../docs/faq.md:184 -msgid "" -"It lets us run services in an isolated manner and independently of the " -"(usually old) packages available for distributions." +msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions." msgstr "" #: ../../../docs/faq.md:186 -msgid "" -"It also lets us have a unified setup which runs the same across various " -"supported distros (see them on [Prerequisites](prerequisites.md))." +msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))." msgstr "" #: ../../../docs/faq.md:188 @@ -632,23 +414,15 @@ msgid "Is Docker a hard requirement?" msgstr "" #: ../../../docs/faq.md:190 -msgid "" -"Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-" -"podman-instead-of-docker) for why we're not using another container " -"runtime." +msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime." msgstr "" #: ../../../docs/faq.md:192 -msgid "" -"All of our services run in containers. It's how we achieve predictability" -" and also how we support tens of different services across lots of " -"distros." +msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros." msgstr "" #: ../../../docs/faq.md:194 -msgid "" -"The only thing we need on the distro is systemd and Python (we install " -"Docker ourselves, unless you ask us not to)." +msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)." msgstr "" #: ../../../docs/faq.md:196 @@ -656,19 +430,11 @@ msgid "Why don't you use docker-compose?" msgstr "" #: ../../../docs/faq.md:198 -msgid "" -"Instead of using [docker-compose](https://docs.docker.com/compose/), we " -"prefer installing systemd services and scheduling those independently." +msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently." msgstr "" #: ../../../docs/faq.md:200 -msgid "" -"There are people who have worked on turning this setup into a docker-" -"compose-based one. See these experiments " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/64#issuecomment-603164625). There is also a demo project " -"([element-docker-demo](https://github.com/element-hq/element-docker-" -"demo)) by Element." +msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element." msgstr "" #: ../../../docs/faq.md:202 @@ -676,9 +442,7 @@ msgid "Can I run this on a distro without systemd?" msgstr "" #: ../../../docs/faq.md:204 -msgid "" -"No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the" -" other one being [Docker](https://www.docker.com/))." +msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))." msgstr "" #: ../../../docs/faq.md:206 @@ -686,21 +450,15 @@ msgid "Can I install this on a Raspberry Pi?" msgstr "" #: ../../../docs/faq.md:208 -msgid "" -"Yes, you can. See our [Alternative Architectures](alternative-" -"architectures.md) documentation page." +msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page." msgstr "" #: ../../../docs/faq.md:210 -msgid "" -"Whether a Raspberry Pi has enough power to give you a good experience is " -"another question. It depends on your use case." +msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case." msgstr "" #: ../../../docs/faq.md:212 -msgid "" -"Also see: [What kind of server specs do I need?](#what-kind-of-server-" -"specs-do-i-need)." +msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)." msgstr "" #: ../../../docs/faq.md:214 @@ -708,53 +466,27 @@ msgid "What kind of server specs do I need?" msgstr "" #: ../../../docs/faq.md:216 -msgid "" -"This largely depends on your use case. It's not so much the number of " -"users that you plan to host, but rather the number of large rooms they " -"will join." +msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join." msgstr "" #: ../../../docs/faq.md:218 -msgid "" -"Federated rooms with lots of history and containing hundreds of other " -"servers are very heavy CPU-wise and memory-wise." +msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise." msgstr "" #: ../../../docs/faq.md:220 -msgid "" -"You can probably use a 1 CPU + 1GB memory server to host hundreds of " -"local users just fine, but as soon as one of them joins a federated room " -"like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say " -"`##linux`), your server will get the need for a lot more power (at least " -"2GB RAM, etc)." +msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)." msgstr "" #: ../../../docs/faq.md:222 -msgid "" -"Running Matrix on a server with 1GB of memory is possible (especially if " -"you disable some not-so-important services). See [How do I optimize this " -"setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-" -"power-server)." +msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" #: ../../../docs/faq.md:224 -msgid "" -"**We recommend starting with a server having at least 2GB of memory** and" -" even then using it sparingly. If you know for sure you'll be joining " -"various large rooms, etc., then going for 4GB of memory or more is a good" -" idea." +msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea." msgstr "" #: ../../../docs/faq.md:226 -msgid "" -"Besides the regular Matrix stuff, we also support things like video-" -"conferencing using [Jitsi](configuring-playbook-jitsi.md) and other " -"additional services which (when installed) may use up a lot of memory. " -"Things do add up. Besides the Synapse Matrix server, Jitsi is especially " -"notorious for consuming a lot of resources. If you plan on running Jitsi," -" we recommend a server with at least 2GB of memory (preferrably more). " -"See our [Jitsi documentation page](configuring-playbook-jitsi.md) to " -"learn how to optimize its memory/CPU usage." +msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." msgstr "" #: ../../../docs/faq.md:228 @@ -762,12 +494,7 @@ msgid "Can I run this in an LXC container?" msgstr "" #: ../../../docs/faq.md:230 -msgid "" -"If your distro runs within an [LXC " -"container](https://linuxcontainers.org/), you may hit [this " -"issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/703). It can be worked around, if absolutely necessary, but" -" we suggest that you avoid running from within an LXC container." +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" #: ../../../docs/faq.md:232 @@ -779,34 +506,19 @@ msgid "Why install my server at matrix.example.com and not at the base domain?" msgstr "" #: ../../../docs/faq.md:236 -msgid "" -"It's the same with email servers. Your email address is likely " -"`name@company.com`, not `name@mail.company.com`, even though it's " -"`mail.company.com` that is really handling your data for `@company.com` " -"email to work." +msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work." msgstr "" #: ../../../docs/faq.md:238 -msgid "" -"Using a separate domain name is easier to manage (although it's a little " -"hard to get right at first) and keeps your Matrix server isolated from " -"your website (if you have one), from your email server (if you have one)," -" etc. Therefore, this playbook sets up services on your Matrix server " -"(`matrix.example.com`) by default." +msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default." msgstr "" #: ../../../docs/faq.md:240 -msgid "" -"I don't control anything on the base domain and can't set up delegation " -"to matrix.example.com. What do I do?" +msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?" msgstr "" #: ../../../docs/faq.md:242 -msgid "" -"If you're not in control of your base domain (or the server handling it) " -"at all, you can take a look at [How do I install on matrix.example.com " -"without involving the base domain?](#how-do-i-install-on-" -"matrixexamplecom-without-involving-the-base-domain)" +msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:244 @@ -814,11 +526,7 @@ msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating msgstr "" #: ../../../docs/faq.md:246 -msgid "" -"If you really can't obtain an HTTPS certificate for your base domain, you" -" can take a look at [How do I install on matrix.example.com without " -"involving the base domain?](#how-do-i-install-on-matrixexamplecom-" -"without-involving-the-base-domain)" +msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:248 @@ -826,15 +534,11 @@ msgid "How do I install on matrix.example.com without involving the base domain? msgstr "" #: ../../../docs/faq.md:250 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/faq.md:271 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/faq.md:278 @@ -842,54 +546,31 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/faq.md:280 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/faq.md:282 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/faq.md:284 -msgid "" -"Without setting up [server delegation](howto-server-delegation.md) to " -"`matrix.example.com`, your user IDs will be like " -"`@alice:matrix.example.com`. This is equivalent to having an email " -"address like `bob@mail.company.com`, instead of just `bob@company.com`." +msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`." msgstr "" #: ../../../docs/faq.md:286 -msgid "" -"I don't use the base domain for anything. How am I supposed to set up " -"Server Delegation for Matrix services?" +msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?" msgstr "" #: ../../../docs/faq.md:288 -msgid "" -"If you don't use your base domain for anything, then it's hard for you to" -" \"serve files over HTTPS\" on it -- something we ask you to do for the " -"[.well-known](configuring-well-known.md) setup (needed for [Server " -"Delegation](howto-server-delegation.md))." +msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))." msgstr "" #: ../../../docs/faq.md:290 -msgid "" -"Luckily, the playbook can set up your Matrix server (at " -"`matrix.example.com`) to also handle traffic for the base domain " -"(`example.com`)." +msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)." msgstr "" #: ../../../docs/faq.md:292 -msgid "" -"See [Serving the base domain](configuring-playbook-base-domain-" -"serving.md)." +msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)." msgstr "" #: ../../../docs/faq.md:294 @@ -901,41 +582,27 @@ msgid "You can disable some not-so-important services to save on memory." msgstr "" #: ../../../docs/faq.md:318 -msgid "" -"You can also consider implementing a restriction on room complexity, in " -"order to prevent users from joining very heavy rooms:" +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" msgstr "" #: ../../../docs/faq.md:328 -msgid "" -"If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed" -" by default), there are additional optimizations listed on its " -"documentation page that you can perform." +msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." msgstr "" #: ../../../docs/faq.md:330 -msgid "" -"I already have Docker on my server. Can you stop installing Docker via " -"the playbook?" +msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" msgstr "" #: ../../../docs/faq.md:332 -msgid "" -"Yes, we can stop installing Docker ourselves. Just use this in your " -"`vars.yml` file:" +msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" msgstr "" #: ../../../docs/faq.md:338 -msgid "" -"I run another webserver on the same server where I wish to install " -"Matrix. What now?" +msgid "I run another webserver on the same server where I wish to install Matrix. What now?" msgstr "" #: ../../../docs/faq.md:340 -msgid "" -"By default, we install a webserver for you " -"([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your " -"own webserver](configuring-playbook-own-webserver.md)." +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 @@ -943,30 +610,19 @@ 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:" +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)." +msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." msgstr "" #: ../../../docs/faq.md:348 -msgid "" -"then, there are overrides in `group_vars/matrix_servers`, which aim to " -"adjust these \"standalone role defaults\" to something which better fits " -"the playbook in its entirety." +msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." msgstr "" #: ../../../docs/faq.md:350 -msgid "" -"finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` " -"file, which is the ultimate override" +msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" msgstr "" #: ../../../docs/faq.md:352 @@ -974,67 +630,39 @@ msgid "What configuration variables are available?" msgstr "" #: ../../../docs/faq.md:354 -msgid "" -"You can discover the variables you can override in each role " -"(`roles/*/*/defaults/main.yml`)." +msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." msgstr "" #: ../../../docs/faq.md:356 -msgid "" -"As described in [How is the effective configuration determined?](#how-is-" -"the-effective-configuration-determined), these role-defaults may be " -"overriden by values defined in `group_vars/matrix_servers`." +msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/faq.md:358 -msgid "" -"Refer to both of these for inspiration. Still, as mentioned in " -"[Configuring the playbook](configuring-playbook.md), you're only ever " -"supposed to edit your own " -"`inventory/host_vars/matrix.example.com/vars.yml` file and nothing else " -"inside the playbook (unless you're meaning to contribute new features)." +msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." msgstr "" #: ../../../docs/faq.md:360 ../../../docs/faq.md:372 -msgid "" -"**Note**: some of the roles (`roles/galaxy/*`) live in separate " -"repositories and are only installed after your run `just roles` (or `make" -" roles`) or `just update` (which automatically does `git pull` and `just " -"roles`)." +msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." msgstr "" #: ../../../docs/faq.md:362 -msgid "" -"I'd like to adjust some configuration which doesn't have a corresponding " -"variable. How do I do it?" +msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" msgstr "" #: ../../../docs/faq.md:364 -msgid "" -"The playbook doesn't aim to expose all configuration settings for all " -"services using variables. Doing so would amount to hundreds of variables " -"that we have to create and maintain." +msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." msgstr "" #: ../../../docs/faq.md:366 -msgid "" -"Instead, we only try to make some important basics configurable using " -"dedicated variables you can see in each role. See [What configuration " -"variables are available?](#what-configuration-variables-are-available)." +msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." msgstr "" #: ../../../docs/faq.md:368 -msgid "" -"Besides that, each role (component) aims to provide a " -"`matrix_SOME_COMPONENT_configuration_extension_yaml` (or " -"`matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can" -" be used to override the configuration." +msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." msgstr "" #: ../../../docs/faq.md:370 -msgid "" -"Check each role's `roles/*/*/defaults/main.yml` for the corresponding " -"variable and an example for how use it." +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 @@ -1046,15 +674,11 @@ msgid "How do I run the installation?" msgstr "" #: ../../../docs/faq.md:378 -msgid "" -"See [Installing](installing.md) to learn how to use Ansible to install " -"Matrix services." +msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." msgstr "" #: ../../../docs/faq.md:380 -msgid "" -"However, we recommend you to follow our installation guide, instead of " -"jumping straight to installing." +msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." msgstr "" #: ../../../docs/faq.md:382 @@ -1062,24 +686,15 @@ msgid "There are two guides available:" msgstr "" #: ../../../docs/faq.md:384 -msgid "" -"⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended " -"for those who do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/faq.md:386 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide by starting with the " -"**[Prerequisites](prerequisites.md)** documentation page." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." msgstr "" #: ../../../docs/faq.md:388 -msgid "" -"I installed Synapse some other way. Can I migrate such a setup to the " -"playbook?" +msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" msgstr "" #: ../../../docs/faq.md:390 @@ -1087,61 +702,31 @@ msgid "Yes, you can." msgstr "" #: ../../../docs/faq.md:392 -msgid "" -"You generally need to do a playbook installation. It's recommended to " -"follow the full installation guide (starting at the " -"[Prerequisites](prerequisites.md) page), not the [Quick start](quick-" -"start.md) guide. The full installation guide will tell you when it's time" -" to import your existing data into the newly-prepared server." +msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." msgstr "" #: ../../../docs/faq.md:394 -msgid "" -"This Ansible playbook guides you into installing a server for " -"`example.com` (user IDs are like this: `@alice:example.com`), while the " -"server is at `matrix.example.com`. If your existing setup has a server " -"name (`server_name` configuration setting in Synapse's `homeserver.yaml` " -"file) other than the base `example.com`, you may need to tweak some " -"additional variables. This FAQ entry may be of use if you're dealing with" -" a more complicated setup - [How do I install on matrix.example.com " -"without involving the base domain?](#how-do-i-install-on-" -"matrixexamplecom-without-involving-the-base-domain)" +msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup - [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:396 -msgid "" -"After configuring the playbook and installing and **before starting** " -"services (done with `ansible-playbook … --tags=start`) you'd import [your" -" SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-" -"postgres.md)) database and also [import your media store](importing-" -"synapse-media-store.md)." +msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." msgstr "" #: ../../../docs/faq.md:398 -msgid "" -"I've downloaded Ansible and the playbook on the server. It can't connect " -"using SSH." +msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." msgstr "" #: ../../../docs/faq.md:400 -msgid "" -"If you're using the playbook directly on the server, then Ansible doesn't" -" need to connect using SSH." +msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." msgstr "" #: ../../../docs/faq.md:402 -msgid "" -"It can perform a local connection instead. Just set " -"`ansible_connection=local` at the end of the server line in " -"`inventory/hosts` and re-run the playbook." +msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." msgstr "" #: ../../../docs/faq.md:404 -msgid "" -"If you're running Ansible from within a container (one of the " -"possibilities we list on our [dedicated Ansible documentation " -"page](ansible.md)), then using `ansible_connection=local` is not " -"possible." +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 @@ -1149,9 +734,7 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/faq.md:408 -msgid "" -"I get \"Error response from daemon: configured logging driver does not " -"support reading\" when I do `docker logs matrix-synapse`." +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 @@ -1163,49 +746,31 @@ msgid "How can I see the logs?" msgstr "" #: ../../../docs/faq.md:414 -msgid "" -"We utilize " -"[systemd/journald](https://www.freedesktop.org/software/systemd/man" -"/systemd-journald.service.html#Description) for logging." +msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging." msgstr "" #: ../../../docs/faq.md:416 -msgid "" -"To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You" -" may wish to see the [manual page for " -"journalctl](https://www.commandlinux.com/man-" -"page/man1/journalctl.1.html)." +msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)." msgstr "" #: ../../../docs/faq.md:418 -msgid "" -"Available service names can be seen by doing `ls " -"/etc/systemd/system/matrix*.service` on the server." +msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server." msgstr "" #: ../../../docs/faq.md:420 -msgid "" -"Some services also log to files in `/matrix/*/data/..`, but we're slowly " -"moving away from that." +msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." msgstr "" #: ../../../docs/faq.md:422 -msgid "" -"We also disable Docker logging, so you can't use `docker logs matrix-*` " -"either. We do this to prevent useless double (or even triple) logging and" -" to avoid having to rotate log files." +msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files." msgstr "" #: ../../../docs/faq.md:424 -msgid "" -"We just simply delegate logging to journald and it takes care of " -"persistence and expiring old data." +msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." msgstr "" #: ../../../docs/faq.md:426 -msgid "" -"Also see: [How long do systemd/journald logs persist for?](#how-long-do-" -"systemdjournald-logs-persist-for)" +msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)" msgstr "" #: ../../../docs/faq.md:428 @@ -1213,21 +778,15 @@ msgid "How long do systemd/journald logs persist for?" msgstr "" #: ../../../docs/faq.md:430 -msgid "" -"On some distros, the journald logs are just in-memory and not persisted " -"to disk." +msgid "On some distros, the journald logs are just in-memory and not persisted to disk." msgstr "" #: ../../../docs/faq.md:432 -msgid "" -"Consult (and feel free to adjust) your distro's journald logging " -"configuration in `/etc/systemd/journald.conf`." +msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." msgstr "" #: ../../../docs/faq.md:434 -msgid "" -"To enable persistence and put some limits on how large the journal log " -"files can become, adjust your configuration like this:" +msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" msgstr "" #: ../../../docs/faq.md:445 @@ -1243,9 +802,7 @@ msgid "Yes. We don't update anything for you automatically." msgstr "" #: ../../../docs/faq.md:451 -msgid "" -"See our [documentation page about upgrading services](maintenance-" -"upgrading-services.md)." +msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." msgstr "" #: ../../../docs/faq.md:453 @@ -1253,18 +810,11 @@ msgid "How do I move my existing installation to another (VM) server?" msgstr "" #: ../../../docs/faq.md:455 -msgid "" -"If you have an existing installation done using this Ansible playbook, " -"you can easily migrate that to another server using [our dedicated server" -" migration guide](maintenance-migrating.md)." +msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)." msgstr "" #: ../../../docs/faq.md:457 -msgid "" -"If your previous installation is done in some other way (not using this " -"Ansible playbook), see [I installed Synapse some other way. Can I migrate" -" such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i" -"-migrate-such-a-setup-to-the-playbook)." +msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." msgstr "" #: ../../../docs/faq.md:459 @@ -1276,17 +826,11 @@ msgid "We haven't documented this properly yet, but the general advice is to:" msgstr "" #: ../../../docs/faq.md:463 -msgid "" -"back up Postgres by making a database dump. See [Backing up PostgreSQL" -"](maintenance-postgres.md#backing-up-postgresql)" +msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" msgstr "" #: ../../../docs/faq.md:465 -msgid "" -"back up all `/matrix` files, except for `/matrix/postgres/data` (you " -"already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` " -"(this directory may exist and contain your old data if you've [performed " -"a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." msgstr "" #: ../../../docs/faq.md:467 @@ -1298,36 +842,23 @@ 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)" +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." +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?" +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." +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`" +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 @@ -1335,21 +866,13 @@ 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." +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`)." +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." +msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po index cb1767774..f381493e5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po @@ -26,22 +26,15 @@ msgid "Getting the playbook" msgstr "" #: ../../../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)" +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:5 -msgid "" -"This Ansible playbook is meant to be executed on your own computer (not " -"the Matrix server)." +msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)." msgstr "" #: ../../../docs/getting-the-playbook.md:7 -msgid "" -"In special cases (if your computer cannot run Ansible, etc.) you may put " -"the playbook on the server as well." +msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well." msgstr "" #: ../../../docs/getting-the-playbook.md:9 @@ -49,15 +42,11 @@ msgid "You can retrieve the playbook's source code by:" msgstr "" #: ../../../docs/getting-the-playbook.md:11 -msgid "" -"[Using git to get the playbook](#using-git-to-get-the-playbook) " -"(recommended)" +msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)" msgstr "" #: ../../../docs/getting-the-playbook.md:13 -msgid "" -"[Downloading the playbook as a ZIP archive](#downloading-the-playbook-" -"as-a-zip-archive) (not recommended)" +msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)" msgstr "" #: ../../../docs/getting-the-playbook.md:15 @@ -65,24 +54,15 @@ msgid "Using git to get the playbook" msgstr "" #: ../../../docs/getting-the-playbook.md:17 -msgid "" -"We recommend using the [git](https://git-scm.com/) tool to get the " -"playbook's source code, because it lets you easily keep up to date in the" -" future when [Maintaining services](maintenance-upgrading-services.md)." +msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)." msgstr "" #: ../../../docs/getting-the-playbook.md:19 -msgid "" -"Once you've installed git on your computer, you can go to any directory " -"of your choosing and run the following command to retrieve the playbook's" -" source code:" +msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:" msgstr "" #: ../../../docs/getting-the-playbook.md:25 -msgid "" -"This will create a new `matrix-docker-ansible-deploy` directory. You're " -"supposed to execute all other installation commands inside that " -"directory." +msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory." msgstr "" #: ../../../docs/getting-the-playbook.md:27 @@ -90,30 +70,17 @@ msgid "Downloading the playbook as a ZIP archive" msgstr "" #: ../../../docs/getting-the-playbook.md:29 -msgid "" -"Alternatively, you can download the playbook as a ZIP archive. This is " -"not recommended, as it's not easy to keep up to date with future updates." -" We suggest you [use git](#using-git-to-get-the-playbook) instead." +msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead." msgstr "" #: ../../../docs/getting-the-playbook.md:31 -msgid "" -"The latest version is always at the following URL: " -"https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/archive/master.zip" +msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip" msgstr "" #: ../../../docs/getting-the-playbook.md:33 -msgid "" -"You can extract this archive anywhere. You'll get a directory called " -"`matrix-docker-ansible-deploy-master`. You're supposed to execute all " -"other installation commands inside that directory." +msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory." msgstr "" #: ../../../docs/getting-the-playbook.md:37 -msgid "" -"[▶️](configuring-playbook.md) No matter which method you've used to " -"download the playbook, you can proceed by [Configuring the playbook" -"](configuring-playbook.md)." +msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po index 4781be83b..122665b7b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po @@ -26,11 +26,7 @@ msgid "Server Delegation" msgstr "" #: ../../../docs/howto-server-delegation.md:3 -msgid "" -"By default, this playbook sets up services on your Matrix server " -"(`matrix.example.com`). To have this server officially be responsible for" -" Matrix services for the base domain (`example.com`), you need to set up " -"server delegation / redirection." +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." msgstr "" #: ../../../docs/howto-server-delegation.md:5 @@ -38,42 +34,23 @@ msgid "Server delegation can be configured in either of these ways:" msgstr "" #: ../../../docs/howto-server-delegation.md:7 -msgid "" -"[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a" -"-well-known-file) on the base domain (`example.com`)" +msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)" msgstr "" #: ../../../docs/howto-server-delegation.md:8 -msgid "" -"[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a" -"-dns-srv-record-advanced)" +msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/howto-server-delegation.md:10 -msgid "" -"Both methods have their place and will continue to do so. You only need " -"to use just one of these delegation methods." +msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods." msgstr "" #: ../../../docs/howto-server-delegation.md:12 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file. However, that method " -"may have some downsides that are not to your liking. Hence this guide " -"about alternative ways to set up Server Delegation." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation." msgstr "" #: ../../../docs/howto-server-delegation.md:14 -msgid "" -"**Note**: as an alternative, it is possible to install the server such " -"that it uses only the `matrix.example.com` domain (instead of identifying" -" as the shorter base domain - `example.com`). This should be helpful if " -"you are not in control of anything on the base domain (`example.com`). In" -" this case, you would not need to configure server delegation, but you " -"would need to add other configuration. For more information, see [How do " -"I install on matrix.example.com without involving the base " -"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" -"the-base-domain) on our FAQ." +msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" #: ../../../docs/howto-server-delegation.md:16 @@ -81,20 +58,11 @@ msgid "Server Delegation via a well-known file" msgstr "" #: ../../../docs/howto-server-delegation.md:18 -msgid "" -"This playbook recommends you to set up server delegation by means of a " -"`/.well-known/matrix/server` file served from the base domain " -"(`example.com`), as this is the most straightforward way to set up the " -"delegation." +msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation." msgstr "" #: ../../../docs/howto-server-delegation.md:20 -msgid "" -"To configure server delegation with the well-known file, check this " -"section on [Configuring Service Discovery via .well-known](configuring-" -"well-known.md): [Installing well-known files on the base domain's server" -"](configuring-well-known.md#installing-well-known-files-on-the-base-" -"domain-s-server)" +msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)" msgstr "" #: ../../../docs/howto-server-delegation.md:22 @@ -102,46 +70,27 @@ msgid "Downsides of well-known-based Server Delegation" msgstr "" #: ../../../docs/howto-server-delegation.md:24 -msgid "" -"Server Delegation by means of a `/.well-known/matrix/server` file is the " -"most straightforward, but suffers from the following downsides:" +msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:" msgstr "" #: ../../../docs/howto-server-delegation.md:26 -msgid "" -"you need to have a working HTTPS server for the base domain " -"(`example.com`). If you don't have any server for the base domain at all," -" you can easily solve it by making the playbook [serve the base domain " -"from the Matrix server](configuring-playbook-base-domain-serving.md)." +msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)." msgstr "" #: ../../../docs/howto-server-delegation.md:28 -msgid "" -"any downtime on the base domain (`example.com`) or network trouble " -"between the Matrix subdomain (`matrix.example.com`) and the base " -"`example.com` may cause Matrix Federation outages. As the [Server-Server " -"spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" -"discovery):" +msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):" msgstr "" #: ../../../docs/howto-server-delegation.md:30 -msgid "" -"Errors are recommended to be cached for up to an hour, and servers are " -"encouraged to exponentially back off for repeated failures." +msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures." msgstr "" #: ../../../docs/howto-server-delegation.md:32 -msgid "" -"**For most people, this is a reasonable tradeoff** given that it's easy " -"and straightforward to set up. We recommend you stay on this path." +msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path." msgstr "" #: ../../../docs/howto-server-delegation.md:34 -msgid "" -"Otherwise, you can decide to go against the default for this playbook, " -"and instead set up [Server Delegation via a DNS SRV record (advanced" -")](#server-delegation-via-a-dns-srv-record-advanced) (much more " -"complicated)." +msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)." msgstr "" #: ../../../docs/howto-server-delegation.md:36 @@ -149,26 +98,15 @@ msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" #: ../../../docs/howto-server-delegation.md:38 -msgid "" -"**Note**: doing Server Delegation via a DNS SRV record is a more " -"**advanced** way to do it and is not the default for this playbook. This " -"is usually **much more complicated** to set up, so **we don't recommend " -"it**. If you're not an experienced sysadmin, you'd better stay away from " -"this." +msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this." msgstr "" #: ../../../docs/howto-server-delegation.md:40 -msgid "" -"As per the [Server-Server " -"spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" -"discovery), it's possible to do Server Delegation using only a SRV record" -" (without a `/.well-known/matrix/server` file)." +msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)." msgstr "" #: ../../../docs/howto-server-delegation.md:42 -msgid "" -"This prevents you from suffering the [Downsides of well-known-based " -"Server Delegation](#downsides-of-well-known-based-server-delegation)." +msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)." msgstr "" #: ../../../docs/howto-server-delegation.md:44 @@ -176,33 +114,19 @@ msgid "To use DNS SRV record validation, you need to:" msgstr "" #: ../../../docs/howto-server-delegation.md:46 -msgid "" -"ensure that `/.well-known/matrix/server` is **not served** from the base " -"domain, as that would interfere with DNS SRV record Server Delegation. To" -" make the playbook **not** generate and serve the file, use the following" -" configuration: `matrix_static_files_file_matrix_server_enabled: false`." +msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`." msgstr "" #: ../../../docs/howto-server-delegation.md:48 -msgid "" -"ensure that you have a `_matrix._tcp` DNS SRV record for your base domain" -" (`example.com`) with a value of `10 0 8448 matrix.example.com`" +msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`" msgstr "" #: ../../../docs/howto-server-delegation.md:50 -msgid "" -"ensure that you are serving the Matrix Federation API (tcp/8448) with a " -"certificate for `example.com` (not `matrix.example.com`!). Getting this " -"certificate to the `matrix.example.com` server may be complicated. The " -"playbook's automatic SSL obtaining/renewal flow will likely not work and " -"you'll need to copy certificates around manually. See below." +msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below." msgstr "" #: ../../../docs/howto-server-delegation.md:52 -msgid "" -"For more details on how to configure the playbook to work with SRV " -"delegation, take a look at this documentation: [Server Delegation via a " -"DNS SRV record (advanced)](howto-srv-server-delegation.md)" +msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)" msgstr "" #: ../../../docs/howto-server-delegation.md:54 @@ -210,27 +134,15 @@ msgid "Obtaining certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:56 -msgid "" -"How you can obtain a valid certificate for `example.com` on the " -"`matrix.example.com` server is up to you." +msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you." msgstr "" #: ../../../docs/howto-server-delegation.md:58 -msgid "" -"If `example.com` and `matrix.example.com` are hosted on the same machine," -" you can let the playbook obtain the certificate for you, by following " -"our [Obtaining SSL certificates for additional domains](configuring-" -"playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-" -"domains) guide." +msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide." msgstr "" #: ../../../docs/howto-server-delegation.md:60 -msgid "" -"If `example.com` and `matrix.example.com` are not hosted on the same " -"machine, you can copy over the certificate files manually. Don't forget " -"that they may get renewed once in a while, so you may also have to " -"transfer them periodically. How often you do that is up to you, as long " -"as the certificate files don't expire." +msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire." msgstr "" #: ../../../docs/howto-server-delegation.md:62 @@ -238,10 +150,7 @@ msgid "Serving the Federation API with your certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:64 -msgid "" -"Regardless of which method for obtaining certificates you've used, once " -"you've managed to get certificates for your base domain onto the " -"`matrix.example.com` machine you can put them to use." +msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use." msgstr "" #: ../../../docs/howto-server-delegation.md:66 @@ -249,9 +158,7 @@ msgid "Based on your setup, you have different ways to go about it:" msgstr "" #: ../../../docs/howto-server-delegation.md:68 -msgid "" -"Serving the Federation API with your certificates and Synapse handling " -"Federation" +msgid "Serving the Federation API with your certificates and Synapse handling Federation" msgstr "" #: ../../../docs/howto-server-delegation.md:70 @@ -259,22 +166,15 @@ msgid "You can let Synapse handle Federation by itself." msgstr "" #: ../../../docs/howto-server-delegation.md:72 -msgid "" -"To do that, make sure the certificate files are mounted into the Synapse " -"container:" +msgid "To do that, make sure the certificate files are mounted into the Synapse container:" msgstr "" #: ../../../docs/howto-server-delegation.md:79 -msgid "" -"You can then tell Synapse to serve Federation traffic over TLS on " -"`tcp/8448`:" +msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:" msgstr "" #: ../../../docs/howto-server-delegation.md:87 -msgid "" -"Make sure to reload Synapse once in a while (`systemctl reload matrix-" -"synapse`), so that newer certificates can kick in. Reloading doesn't " -"cause any downtime." +msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime." msgstr "" #: ../../../docs/howto-server-delegation.md:89 @@ -282,20 +182,9 @@ msgid "Serving the Federation API with your certificates and another webserver" msgstr "" #: ../../../docs/howto-server-delegation.md:91 -msgid "" -"**Alternatively**, if you are using another webserver, you can set up " -"reverse-proxying for the `tcp/8448` port by yourself. Make sure to use " -"the proper certificates for `example.com` (not for `matrix.example.com`) " -"when serving the `tcp/8448` port." +msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port." msgstr "" #: ../../../docs/howto-server-delegation.md:93 -msgid "" -"As recommended in our [Fronting the integrated reverse-proxy webserver " -"with another reverse-proxy](./configuring-playbook-own-webserver.md" -"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy) documentation section, we recommend you to expose the Matrix " -"Federation entrypoint from traffic at a local port (e.g. " -"`127.0.0.1:8449`), so your reverese-proxy should send traffic there." +msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po index 9143db321..e315fb1c8 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 @@ -26,21 +26,11 @@ msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:3 -msgid "" -"**Reminder** : unless you are affected by the [Downsides of well-known-" -"based Server Delegation](howto-server-delegation.md#downsides-of-well-" -"known-based-server-delegation), we suggest you **stay on the " -"simple/default path**: [Server Delegation](howto-server-delegation.md) by" -" [configuring well-known files](configuring-well-known.md) at the base " -"domain." +msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:5 -msgid "" -"This guide is about configuring Server Delegation using DNS SRV records " -"(for the [Traefik](https://doc.traefik.io/traefik/) webserver). This " -"method has special requirements when it comes to SSL certificates, so " -"various changes are required." +msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:7 @@ -48,30 +38,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:9 -msgid "" -"SRV delegation while still using the playbook provided Traefik to get / " -"renew the certificate requires a wildcard certificate." +msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:11 -msgid "" -"To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one" -" needs to use a [DNS-01 challenge](https://letsencrypt.org/docs" -"/challenge-types/#dns-01-challenge) method instead of the default " -"[HTTP-01](https://letsencrypt.org/docs/challenge-" -"types/#http-01-challenge)." +msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:13 -msgid "" -"This means that this is **limited to the list of DNS providers supported " -"by Traefik**, unless you bring in your own certificate." +msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:15 -msgid "" -"The up-to-date list can be accessed on [traefik's " -"documentation](https://doc.traefik.io/traefik/https/acme/#providers)" +msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:17 @@ -79,31 +58,19 @@ msgid "The changes" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:19 -msgid "" -"**Note**: the changes below instruct you how to do this for a basic " -"Synapse installation. You will need to adapt the variable name and the " -"content of the labels:" +msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:21 -msgid "" -"if you're using another homeserver implementation (e.g. [Conduit" -"](./configuring-playbook-conduit.md) or [Dendrite](./configuring-" -"playbook-dendrite.md))" +msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:22 -msgid "" -"if you're using [Synapse with workers enabled](./configuring-playbook-" -"synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled:" -" true`). In that case, it's actually the `matrix-synapse-reverse-proxy-" -"companion` service which has Traefik labels attached" +msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:24 -msgid "" -"Also, all instructions below are from an older version of the playbook " -"and may not work anymore." +msgid "Also, all instructions below are from an older version of the playbook and may not work anymore." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:26 @@ -111,12 +78,7 @@ msgid "Federation Endpoint" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:33 -msgid "" -"This is because with SRV federation, some servers / tools (one of which " -"being the federation tester) try to access the federation API using the " -"resolved IP address instead of the domain name (or they are not using " -"SNI). This change will make Traefik route all traffic for which the path " -"match this rule go to the federation endpoint." +msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:35 @@ -124,18 +86,11 @@ msgid "Tell Traefik which certificate to serve for the federation endpoint" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:37 -msgid "" -"Now that the federation endpoint is not bound to a domain anymore we need" -" to explicitely tell Traefik to use a wildcard certificate in addition to" -" one containing the base name." +msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:39 -msgid "" -"This is because the Matrix specification expects the federation endpoint " -"to be served using a certificate compatible with the base domain, " -"however, the other resources on the endpoint still need a valid " -"certificate to work." +msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:48 @@ -143,10 +98,7 @@ msgid "Configure the DNS-01 challenge for let's encrypt" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:50 -msgid "" -"Since we're now requesting a wildcard certificate, we need to change the " -"ACME challenge method. To request a wildcard certificate from Let's " -"Encrypt we are required to use the DNS-01 challenge." +msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:52 @@ -158,11 +110,7 @@ msgid "Add a new certificate resolver that works with DNS-01" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:54 -msgid "" -"Configure the resolver to allow access to the DNS zone to configure the " -"records to answer the challenge (refer to [Traefik's " -"documentation](https://doc.traefik.io/traefik/https/acme/#providers) to " -"know which environment variables to set)" +msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:55 @@ -170,9 +118,7 @@ msgid "Tell the playbook to use the new resolver as default" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:57 -msgid "" -"We cannot just disable the default resolver as that would disable SSL in " -"quite a few places in the playbook." +msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:86 @@ -184,14 +130,7 @@ msgid "The last step is to alter the generated Coturn configuration." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:90 -msgid "" -"By default, Coturn is configured to wait on the certificate for the " -"`matrix.` subdomain using an [instantiated systemd " -"service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates)" -" using the domain name as the parameter for this service. However, we " -"need to serve the wildcard certificate, which is incompatible with " -"systemd, it will try to expand the `*`, which will break and prevent " -"Coturn from starting." +msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:92 @@ -199,21 +138,13 @@ msgid "We also need to indicate to Coturn where the wildcard certificate is." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:94 -msgid "" -"**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still " -"fail to start because Traefik is still in the process of obtaining the " -"certificates. If you still get an error, make sure Traefik obtained the " -"certificates and restart the Coturn service (`just start-group coturn`)." +msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:96 -msgid "" -"This should not happen again afterwards as Traefik will renew " -"certificates well before their expiry date, and the Coturn service is " -"setup to restart periodically." +msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:122 msgid "Full example of a working configuration" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po index 710e0a74c..f6a164585 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po @@ -22,17 +22,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-postgres.md:1 -msgid "" -"Importing an existing Postgres database from another installation " -"(optional)" +msgid "Importing an existing Postgres database from another installation (optional)" msgstr "" #: ../../../docs/importing-postgres.md:3 -msgid "" -"Run this if you'd like to import your database from a previous " -"installation. (don't forget to import your Synapse `media_store` files as" -" well - see [the importing-synape-media-store guide](importing-synapse-" -"media-store.md))." +msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))." msgstr "" #: ../../../docs/importing-postgres.md:6 @@ -40,34 +34,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/importing-postgres.md:8 -msgid "" -"For this to work, **the database name in Postgres must match** what this " -"playbook uses. This playbook uses a Postgres database name of `synapse` " -"by default (controlled by the `matrix_synapse_database_database` " -"variable). If your database name differs, be sure to change " -"`matrix_synapse_database_database` to your desired name and to re-run the" -" playbook before proceeding." +msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding." msgstr "" #: ../../../docs/importing-postgres.md:10 -msgid "" -"The playbook supports importing Postgres dump files in **text** (e.g. " -"`pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > " -"dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) " -"is also supported." +msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported." msgstr "" #: ../../../docs/importing-postgres.md:12 -msgid "" -"The migration might be a good moment, to \"reset\" a not properly working" -" bridge. Be aware, that it might affect all users (new link to bridge, " -"new rooms, …)" +msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)" msgstr "" #: ../../../docs/importing-postgres.md:14 -msgid "" -"Before doing the actual import, **you need to upload your Postgres dump " -"file to the server** (any path is okay)." +msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)." msgstr "" #: ../../../docs/importing-postgres.md:16 @@ -75,9 +54,7 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-postgres.md:18 -msgid "" -"To import, run this command (make sure to replace " -"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" +msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" msgstr "" #: ../../../docs/importing-postgres.md:26 @@ -85,28 +62,15 @@ 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!)" +msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)" msgstr "" #: ../../../docs/importing-postgres.md:29 -msgid "" -"`postgres_default_import_database` defaults to `matrix`, which is useful " -"for importing multiple databases (for dumps made with `pg_dumpall`). If " -"you're importing a single database (e.g. `synapse`), consider changing " -"`postgres_default_import_database` accordingly" +msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly" msgstr "" #: ../../../docs/importing-postgres.md:30 -msgid "" -"after importing a large database, it's a good idea to run [an `ANALYZE` " -"operation](https://www.postgresql.org/docs/current/sql-analyze.html) to " -"make Postgres rebuild its database statistics and optimize its query " -"planner. You can easily do this via the playbook by running `just run-" -"tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see " -"[Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for " -"more details)." +msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)." msgstr "" #: ../../../docs/importing-postgres.md:32 @@ -118,9 +82,7 @@ msgid "Table Ownership" msgstr "" #: ../../../docs/importing-postgres.md:36 -msgid "" -"A table ownership issue can occur if you are importing from a Synapse " -"installation which was both:" +msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:" msgstr "" #: ../../../docs/importing-postgres.md:38 @@ -136,38 +98,23 @@ msgid "In this case you may run into the following error during the import task: msgstr "" #: ../../../docs/importing-postgres.md:47 -msgid "" -"where `synapse_user` is the database username from the previous Synapse " -"installation." +msgid "where `synapse_user` is the database username from the previous Synapse installation." msgstr "" #: ../../../docs/importing-postgres.md:49 -msgid "" -"This can be verified by examining the dump for ALTER TABLE statements " -"which set OWNER TO that username:" +msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:" msgstr "" #: ../../../docs/importing-postgres.md:61 -msgid "" -"It can be worked around by changing the username to `synapse`, for " -"example by using `sed`:" +msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:" msgstr "" #: ../../../docs/importing-postgres.md:67 -msgid "" -"This uses sed to perform an 'in-place' (`-i`) replacement globally " -"(`/g`), searching for `synapse_user` and replacing with `synapse` " -"(`s/synapse_user/synapse`). If your database username was different, " -"change `synapse_user` to that username instead. Expand search/replace " -"statement as shown in example above, in case of old user name like " -"`matrix` - replacing `matrix` only would… well - you can imagine." +msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine." msgstr "" #: ../../../docs/importing-postgres.md:69 -msgid "" -"Note that if the previous import failed with an error it may have made " -"changes which are incompatible with re-running the import task right " -"away; if you do so it may fail with an error such as:" +msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:" msgstr "" #: ../../../docs/importing-postgres.md:75 @@ -175,33 +122,23 @@ msgid "Repeat import" msgstr "" #: ../../../docs/importing-postgres.md:77 -msgid "" -"In this case you can use the command suggested in the import task to " -"clear the database before retrying the import:" +msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:" msgstr "" #: ../../../docs/importing-postgres.md:85 -msgid "" -"Now on your local machine run `just run-tags setup-postgres` to prepare " -"the database roles etc." +msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc." msgstr "" #: ../../../docs/importing-postgres.md:87 -msgid "" -"If not, you probably get this error. `synapse` is the correct table " -"owner, but the role is missing in database." +msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database." msgstr "" #: ../../../docs/importing-postgres.md:93 -msgid "" -"Once the database is clear and the ownership of the tables has been fixed" -" in the SQL file, the import task should succeed." +msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed." msgstr "" #: ../../../docs/importing-postgres.md:95 -msgid "" -"Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths" -" (or even better, copy this line from your terminal)" +msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)" msgstr "" #: ../../../docs/importing-postgres.md:101 @@ -211,4 +148,3 @@ msgstr "" #: ../../../docs/importing-postgres.md:103 msgid "To open psql terminal run `/matrix/postgres/bin/cli`" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po index ee4c523bf..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 @@ -22,15 +22,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-synapse-media-store.md:1 -msgid "" -"Importing `media_store` data files from an existing Synapse installation " -"(optional)" +msgid "Importing `media_store` data files from an existing Synapse installation (optional)" msgstr "" #: ../../../docs/importing-synapse-media-store.md:3 -msgid "" -"Run this if you'd like to import your `media_store` files from a previous" -" installation of Synapse." +msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse." msgstr "" #: ../../../docs/importing-synapse-media-store.md:5 @@ -38,34 +34,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/importing-synapse-media-store.md:7 -msgid "" -"Before doing the actual data restore, **you need to upload your media " -"store directory to the server** (any path is okay)." +msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)." msgstr "" #: ../../../docs/importing-synapse-media-store.md:9 -msgid "" -"If you are [storing Matrix media files on Amazon S3](configuring-" -"playbook-s3.md) (optional), restoring with this tool is not possible " -"right now." +msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now." msgstr "" #: ../../../docs/importing-synapse-media-store.md:11 -msgid "" -"As an alternative, you can perform a manual restore using the [AWS CLI " -"tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync " -"/path/to/server/media_store/. s3://name-of-bucket/`)" +msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)" msgstr "" #: ../../../docs/importing-synapse-media-store.md:13 -msgid "" -"**Note for Mac users**: Due to case-sensitivity issues on certain Mac " -"filesystems (HFS or HFS+), filename corruption may occur if you copy a " -"`media_store` directory to your Mac. If you're transferring a " -"`media_store` directory between 2 servers, make sure you do it directly " -"(from server to server with a tool such as " -"[rsync](https://rsync.samba.org/)), and not by downloading the files to " -"your Mac." +msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac." msgstr "" #: ../../../docs/importing-synapse-media-store.md:15 @@ -73,14 +54,9 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-synapse-media-store.md:17 -msgid "" -"Run this command (make sure to replace `` " -"with a path on your server):" +msgid "Run this command (make sure to replace `` with a path on your server):" msgstr "" #: ../../../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!)." +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 3f6d09b6a..c14221242 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -18,31 +18,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-synapse-sqlite.md:1 -msgid "" -"Importing an existing SQLite database from another Synapse installation " -"(optional)" +msgid "Importing an existing SQLite database from another Synapse installation (optional)" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:3 -msgid "" -"Run this if you'd like to import your database from a previous default " -"installation of Synapse (don't forget to import your `media_store` files " -"as well - see [the importing-synapse-media-store guide](importing-" -"synapse-media-store.md))." +msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:5 -msgid "" -"While this playbook only supports running Synapse in combination with " -"PostgreSQL, a Synapse instance installed manually usually defaults to " -"using an SQLite database." +msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:7 -msgid "" -"If you have such a Synapse setup and wish to migrate it to one managed by" -" the playbook (and over to PostgreSQL), this documentation page is for " -"you." +msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:9 @@ -54,27 +42,15 @@ msgid "Before doing the actual import:" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:13 -msgid "" -"**ensure you have NOT started Synapse yet**. That is, make sure you have " -"followed the [Installing step](installing.md), but haven't run the " -"playbook's `start` tag yet. If you had started your new Synapse instance," -" it may have already initialized your Postgres database and importing " -"onto it may not work. In such cases, you may need to clean up the " -"`synapse` database first." +msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:14 -msgid "" -"**ensure you have uploaded your SQLite database file to the server** (any" -" path is okay)" +msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:15 -msgid "" -"if you're using the integrated Postgres server (**by default, you are** " -"using it, unless you've explicitly switched to [Using an external " -"PostgreSQL server](configuring-playbook-external-postgres.md)), **make " -"sure Postgres is started** by running `just start-group postgres`" +msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:17 @@ -82,9 +58,7 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:19 -msgid "" -"Run this command (make sure to replace `` " -"with a file path on your server):" +msgid "Run this command (make sure to replace `` with a file path on your server):" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:25 @@ -92,17 +66,9 @@ msgid "**Notes**:" msgstr "" #: ../../../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!)." +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: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." +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 f29377f43..7240f0158 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/installing.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/installing.po @@ -26,16 +26,11 @@ msgid "Installing" msgstr "" #: ../../../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" +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:5 -msgid "" -"If you've configured your DNS records and the playbook, you can start the" -" installation procedure." +msgid "If you've configured your DNS records and the playbook, you can start the installation procedure." msgstr "" #: ../../../docs/installing.md:7 @@ -43,15 +38,11 @@ msgid "Update Ansible roles" msgstr "" #: ../../../docs/installing.md:9 -msgid "" -"Before installing, you need to update the Ansible roles that this " -"playbook uses and fetches from outside." +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" #: ../../../docs/installing.md:11 -msgid "" -"To update your playbook directory and all upstream Ansible roles (defined" -" in the `requirements.yml` file), run:" +msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:" msgstr "" #: ../../../docs/installing.md:13 @@ -59,22 +50,15 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/installing.md:14 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/installing.md:16 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/installing.md:18 -msgid "" -"For details about `just` commands, take a look at: [Running `just` " -"commands](just.md)." +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/installing.md:20 @@ -82,47 +66,27 @@ msgid "Install Matrix server and services" msgstr "" #: ../../../docs/installing.md:22 -msgid "" -"The Ansible playbook's tasks are tagged, so that certain parts of the " -"Ansible playbook can be run without running all other tasks." +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" #: ../../../docs/installing.md:24 -msgid "" -"The general command syntax for installation (and also maintenance) is: " -"`ansible-playbook -i inventory/hosts setup.yml " -"--tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself " -"familiar with the [playbook tags](playbook-tags.md) before proceeding." +msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding." msgstr "" #: ../../../docs/installing.md:26 -msgid "" -"If you **don't** use SSH keys for authentication, but rather a regular " -"password, you may need to add `--ask-pass` to the all Ansible commands." +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands." msgstr "" #: ../../../docs/installing.md:28 -msgid "" -"If you **do** use SSH keys for authentication, **and** use a non-root " -"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" -"pass`) to all Ansible commands." +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands." msgstr "" #: ../../../docs/installing.md:30 -msgid "" -"There 2 ways to start the installation process - depending on whether " -"you're [Installing a brand new server (without importing " -"data)](#installing-a-brand-new-server-without-importing-data) or " -"[Installing a server into which you'll import old data](#installing-a" -"-server-into-which-youll-import-old-data)." +msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)." msgstr "" #: ../../../docs/installing.md:32 -msgid "" -"**Note**: if you are migrating from an old server to a new one, take a " -"look at [this guide](maintenance-migrating.md) instead. This is an easier" -" and more straightforward way than installing a server and importing old " -"data into it." +msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it." msgstr "" #: ../../../docs/installing.md:34 @@ -130,9 +94,7 @@ msgid "Installing a brand new server (without importing data)" msgstr "" #: ../../../docs/installing.md:36 -msgid "" -"If this is **a brand new** Matrix server and you **won't be importing old" -" data into it**, run all these tags:" +msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:" msgstr "" #: ../../../docs/installing.md:42 @@ -140,10 +102,7 @@ msgid "This will do a full installation and start all Matrix services." msgstr "" #: ../../../docs/installing.md:44 -msgid "" -"**Note**: if the command does not work as expected, make sure that you " -"have properly installed and configured software required to run the " -"playbook, as described on [Prerequisites](prerequisites.md)." +msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)." msgstr "" #: ../../../docs/installing.md:46 @@ -151,25 +110,15 @@ msgid "Installing a server into which you'll import old data" msgstr "" #: ../../../docs/installing.md:48 -msgid "" -"If you will be importing data into your newly created Matrix server, " -"install it, but **do not** start its services just yet. Starting its " -"services or messing with its database now will affect your data import " -"later on." +msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on." msgstr "" #: ../../../docs/installing.md:50 -msgid "" -"To do the installation **without** starting services, run `ansible-" -"playbook` with the `install-all` tag only:" +msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:" msgstr "" #: ../../../docs/installing.md:56 -msgid "" -"⚠️ **Warning**: do not run the just \"recipe\" `just install-all` " -"instead, because it automatically starts services at the end of " -"execution. See: [Difference between playbook tags and shortcuts](just.md" -"#difference-between-playbook-tags-and-shortcuts)" +msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)" msgstr "" #: ../../../docs/installing.md:58 @@ -181,21 +130,15 @@ msgid "You can now:" msgstr "" #: ../../../docs/installing.md:62 -msgid "" -"[Importing an existing SQLite database (from another Synapse installation" -")](importing-synapse-sqlite.md) (optional)" +msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)" msgstr "" #: ../../../docs/installing.md:64 -msgid "" -"[Importing an existing Postgres database (from another installation" -")](importing-postgres.md) (optional)" +msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)" msgstr "" #: ../../../docs/installing.md:66 -msgid "" -"[Importing `media_store` data files from an existing Synapse installation" -"](importing-synapse-media-store.md) (optional)" +msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)" msgstr "" #: ../../../docs/installing.md:68 @@ -207,28 +150,19 @@ msgid "Create your user account" msgstr "" #: ../../../docs/installing.md:76 -msgid "" -"ℹ️ *You can skip this step if you have installed a server and imported " -"old data to it.*" +msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*" msgstr "" #: ../../../docs/installing.md:78 -msgid "" -"As you have configured your brand new server and the client, you need to " -"**create your user account** on your Matrix server." +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" #: ../../../docs/installing.md:80 -msgid "" -"After creating the user account, you can log in to it with [Element Web" -"](configuring-playbook-client-element-web.md) that this playbook has " -"installed for you at this URL: `https://element.example.com/`." +msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`." msgstr "" #: ../../../docs/installing.md:82 -msgid "" -"To create your user account (as an administrator of the server) via this " -"Ansible playbook, run the command below on your local computer." +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" #: ../../../docs/installing.md:84 @@ -240,29 +174,19 @@ msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" #: ../../../docs/installing.md:86 -msgid "" -"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " -"full ID (`@alice:example.com`)" +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/installing.md:87 -msgid "" -"Use `admin=yes` to make your user account an administrator of the Matrix " -"server" +msgid "Use `admin=yes` to make your user account an administrator of the Matrix server" msgstr "" #: ../../../docs/installing.md:95 -msgid "" -"Feel free to create as many accounts (for friends, family, etc.) as you " -"want. Still, perhaps you should grant full administrative access to your " -"account only (with `admin=yes`), and others should be created with " -"`admin=no`." +msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" #: ../../../docs/installing.md:97 -msgid "" -"For more information, see the documentation for [registering users" -"](registering-users.md)." +msgid "For more information, see the documentation for [registering users](registering-users.md)." msgstr "" #: ../../../docs/installing.md:99 @@ -270,52 +194,27 @@ msgid "Finalize the installation" msgstr "" #: ../../../docs/installing.md:101 -msgid "" -"Now you've configured Matrix services and your user account, you need to " -"**finalize the installation process** by [setting up Matrix delegation " -"(redirection)](howto-server-delegation.md), so that your Matrix server " -"(`matrix.example.com`) can present itself as the base domain " -"(`example.com`) in the Matrix network." +msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" #: ../../../docs/installing.md:103 -msgid "" -"This is required for federation to work! Without a proper configuration, " -"your server will effectively not be part of the Matrix network." +msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/installing.md:105 -msgid "" -"To configure the delegation, you have these two options. Choose one of " -"them according to your situation." +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" #: ../../../docs/installing.md:107 -msgid "" -"If you can afford to point the base domain at the Matrix server, follow " -"the instructions below which guide you into [serving the base domain" -"](configuring-playbook-base-domain-serving.md) from the integrated web " -"server. It will enable you to use a Matrix user ID like " -"`@alice:example.com` while hosting services on a subdomain like " -"`matrix.example.com`." +msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`." msgstr "" #: ../../../docs/installing.md:108 -msgid "" -"Alternatively, if you're using the base domain for other purposes and " -"cannot point it to the Matrix server (and thus cannot \"serve the base " -"domain\" from it), you most likely need to [manually install well-known " -"files on the base domain's server](configuring-well-known.md#manually-" -"installing-well-known-files-on-the-base-domains-server), but feel free to" -" familiarize yourself with all [server delegation (redirection) options" -"](howto-server-delegation.md)." +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)." msgstr "" #: ../../../docs/installing.md:110 -msgid "" -"To have the base domain served from the integrated web server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/installing.md:116 @@ -335,15 +234,11 @@ msgid "[check if services work](maintenance-checking-services.md)" msgstr "" #: ../../../docs/installing.md:127 -msgid "" -"or [set up additional services](configuring-playbook.md#other-" -"configuration-options) (bridges to other chat networks, bots, etc.)" +msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)" msgstr "" #: ../../../docs/installing.md:128 -msgid "" -"or learn how to [upgrade services when new versions are released" -"](maintenance-upgrading-services.md)" +msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/installing.md:129 @@ -355,25 +250,15 @@ msgid "or join some Matrix rooms:" msgstr "" #: ../../../docs/installing.md:131 -msgid "" -"via the *Explore rooms* feature in Element Web or some other clients, or " -"by discovering them using this [matrix-static " -"list](https://view.matrix.org). **Note**: joining large rooms may " -"overload small servers." +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." msgstr "" #: ../../../docs/installing.md:132 -msgid "" -"or come say Hi in our support room - [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com). You might learn something or get to help someone " -"else new to Matrix hosting." +msgid "or come say Hi in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" #: ../../../docs/installing.md:133 -msgid "" -"or help make this playbook better by contributing (code, documentation, " -"or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" +msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" msgstr "" #: ../../../docs/installing.md:135 @@ -381,43 +266,27 @@ msgid "Maintaining your setup in the future" msgstr "" #: ../../../docs/installing.md:137 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/installing.md:139 -msgid "" -"The upstream projects, which this playbook makes use of, occasionally if " -"not often suffer from security vulnerabilities." +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." msgstr "" #: ../../../docs/installing.md:141 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/installing.md:143 -msgid "" -"For more information about upgrading or maintaining services with the " -"playbook, take at look at this page: [Upgrading the Matrix services" -"](maintenance-upgrading-services.md)" +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/installing.md:145 -msgid "" -"Feel free to **re-run the setup command any time** you think something is" -" wrong with the server configuration. Ansible will take your " -"configuration and update your server to match." +msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." msgstr "" #: ../../../docs/installing.md:151 -msgid "" -"**Note**: see [this page on the playbook tags](playbook-tags.md) for more" -" information about those tags." +msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" #: ../../../docs/installing.md:153 @@ -425,25 +294,13 @@ msgid "Make full use of `just` shortcut commands" msgstr "" #: ../../../docs/installing.md:155 -msgid "" -"After you get familiar with reconfiguring and re-running the playbook to " -"maintain the server, upgrade its services, etc., you probably would like " -"to make use of `just` shortcut commands for faster input." +msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." msgstr "" #: ../../../docs/installing.md:157 -msgid "" -"For example, `just install-all` is useful for maintaining your setup " -"quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-" -"in-playbook-runtime) than `just setup-all`) when its components remain " -"unchanged. If you adjust your `vars.yml` to remove other components, " -"you'd need to run `just setup-all`, or these components will still remain" -" installed." +msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/installing.md:159 -msgid "" -"You can learn about the shortcut commands on this page: [Running `just` " -"commands](just.md)" +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 9bcab1d78..b6a4f5f16 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/just.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/just.po @@ -26,37 +26,19 @@ msgid "Running `just` commands" msgstr "" #: ../../../docs/just.md:3 -msgid "" -"We have previously used [make](https://www.gnu.org/software/make/) for " -"easily running some playbook commands (e.g. `make roles` which triggers " -"[`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-" -"galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can" -" still run these commands." +msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands." msgstr "" #: ../../../docs/just.md:5 -msgid "" -"In addition, we have added support for running commands via " -"[`just`](https://github.com/casey/just) - a more modern command-runner " -"alternative to `make`. It can be used to invoke `ansible-playbook` " -"commands with less typing." +msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing." msgstr "" #: ../../../docs/just.md:7 -msgid "" -"The `just` utility executes shortcut commands (called as \"recipes\"), " -"which invoke `ansible-playbook`, `ansible-galaxy` or " -"[`agru`](https://github.com/etkecc/agru) (depending on what is available " -"in your system). The targets of the recipes are defined in " -"[`justfile`](../justfile). Most of the just recipes have no corresponding" -" `Makefile` targets." +msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets." msgstr "" #: ../../../docs/just.md:9 -msgid "" -"For some recipes such as `just update`, our `justfile` recommends " -"installing [`agru`](https://github.com/etkecc/agru) (a faster alternative" -" to `ansible-galaxy`) to speed up the process." +msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process." msgstr "" #: ../../../docs/just.md:11 @@ -76,9 +58,7 @@ msgid "`just roles`" msgstr "" #: ../../../docs/just.md -msgid "" -"Install the necessary Ansible roles pinned in " -"[`requirements.yml`](../requirements.yml)" +msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)" msgstr "" #: ../../../docs/just.md @@ -94,9 +74,7 @@ msgid "`just install-all`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all" -",ensure-matrix-users-created,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`" msgstr "" #: ../../../docs/just.md @@ -104,9 +82,7 @@ msgid "`just setup-all`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all" -",ensure-matrix-users-created,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`" msgstr "" #: ../../../docs/just.md @@ -114,9 +90,7 @@ msgid "`just install-all --ask-vault-pass`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run commands with additional arguments (`--ask-vault-pass` will be " -"appended to the above installation command)" +msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)" msgstr "" #: ../../../docs/just.md @@ -156,20 +130,11 @@ msgid "`just register-user alice secret-password yes`" msgstr "" #: ../../../docs/just.md -msgid "" -"Registers an `alice` user with the `secret-password` password and admin " -"access (admin = `yes`)" +msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" #: ../../../docs/just.md:26 -msgid "" -"While [our documentation on prerequisites](prerequisites.md) lists `just`" -" as one of the requirements for installation, using `just` is optional. " -"If you find it difficult to install it, do not find it useful, or want to" -" prefer raw `ansible-playbook` commands for some reason, feel free to run" -" all commands manually. For example, you can run `ansible-galaxy` " -"directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-" -"galaxy install -r requirements.yml -p roles/galaxy/ --force`." +msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`." msgstr "" #: ../../../docs/just.md:28 @@ -177,12 +142,7 @@ msgid "Difference between playbook tags and shortcuts" msgstr "" #: ../../../docs/just.md:30 -msgid "" -"It is worth noting that `just` \"recipes\" are different from [playbook " -"tags](playbook-tags.md). The recipes are shortcuts of commands defined in" -" `justfile` and can be executed by the `just` program only, while the " -"playbook tags are available for the raw `ansible-playbook` commands as " -"well. Please be careful not to confuse them." +msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them." msgstr "" #: ../../../docs/just.md:32 @@ -194,19 +154,9 @@ msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" msgstr "" #: ../../../docs/just.md:36 -msgid "" -"The just recipe runs `ensure-matrix-users-created` and `start` tags after" -" `install-all`, while the latter runs only `install-all` tag. The correct" -" shortcut of the latter is `just run-tags install-all`." +msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`." msgstr "" #: ../../../docs/just.md:38 -msgid "" -"Such kind of difference sometimes matters. For example, when you install " -"a Matrix server into which you will import old data (see " -"[here](installing.md#installing-a-server-into-which-youll-import-old-" -"data)), you are not supposed to run `just install-all` or `just setup-" -"all`, because these commands start services immediately after installing " -"components which may prevent your from importing old data." +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 204de1c85..0cac254c2 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po @@ -30,31 +30,19 @@ msgid "How to see the current status of your services" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:5 -msgid "" -"You can check the status of your services by using `systemctl status`. " -"Example:" +msgid "You can check the status of your services by using `systemctl status`. Example:" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:15 -msgid "" -"Docker containers that the playbook configures are supervised by " -"[systemd](https://wiki.archlinux.org/title/Systemd) and their logs are " -"configured to go to [systemd-" -"journald](https://wiki.archlinux.org/title/Systemd/Journal)." +msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:17 -msgid "" -"To prevent double-logging, Docker logging is disabled by explicitly " -"passing `--log-driver=none` to all containers. Due to this, you " -"**cannot** view logs using `docker logs`." +msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you **cannot** view logs using `docker logs`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:19 -msgid "" -"To view systemd-journald logs using " -"[journalctl](https://man.archlinux.org/man/journalctl.1), run a command " -"like this:" +msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:25 @@ -62,20 +50,11 @@ msgid "Increasing Synapse logging" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:27 -msgid "" -"Because the [Synapse](https://github.com/element-hq/synapse) Matrix " -"server is originally very chatty when it comes to logging, we " -"intentionally reduce its [logging " -"level](https://docs.python.org/3/library/logging.html#logging-levels) " -"from `INFO` to `WARNING`." +msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:29 -msgid "" -"If you'd like to debug an issue or [report a Synapse " -"bug](https://github.com/element-hq/synapse/issues/new/choose) to the " -"developers, it'd be better if you temporarily increasing the logging " -"level to `INFO`." +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 @@ -91,16 +70,11 @@ msgid "Remove unused Docker data" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:43 -msgid "" -"You can free some disk space from Docker, see [docker system " -"prune](https://docs.docker.com/engine/reference/commandline/system_prune/)" -" for more information." +msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:49 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags run-docker-prune`" +msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:51 @@ -108,9 +82,7 @@ msgid "Postgres" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:53 -msgid "" -"See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) " -"documentation page." +msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:55 @@ -118,8 +90,5 @@ msgid "Ma1sd" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:57 -msgid "" -"See the dedicated [Adjusting ma1sd Identity Server configuration" -"](configuring-playbook-ma1sd.md) documentation page." +msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po index e0c108f7a..fe81bb15d 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po @@ -26,9 +26,7 @@ msgid "Checking if services work" msgstr "" #: ../../../docs/maintenance-checking-services.md:3 -msgid "" -"This playbook can perform a check to ensure that you've configured things" -" correctly and that services are running." +msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running." msgstr "" #: ../../../docs/maintenance-checking-services.md:5 @@ -36,9 +34,7 @@ msgid "To perform the check, run:" msgstr "" #: ../../../docs/maintenance-checking-services.md:11 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags self-check`" +msgid "The shortcut command with `just` program is also available: `just run-tags self-check`" msgstr "" #: ../../../docs/maintenance-checking-services.md:13 @@ -46,10 +42,5 @@ msgid "If it's all green, everything is probably running correctly." msgstr "" #: ../../../docs/maintenance-checking-services.md:15 -msgid "" -"Besides this self-check, you can also check whether your server federates" -" with the Matrix network by using the [Federation " -"Tester](https://federationtester.matrix.org/) against your base domain " -"(`example.com`), not the `matrix.example.com` subdomain." +msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po index af7829c38..a82fdaf44 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po @@ -26,9 +26,7 @@ msgid "Migrating to new server" msgstr "" #: ../../../docs/maintenance-migrating.md:3 -msgid "" -"This documentation explains how to migrate your Matrix services (server, " -"client, bridges, etc.) and data **from an old server to a new server**." +msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**." msgstr "" #: ../../../docs/maintenance-migrating.md:5 @@ -36,39 +34,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/maintenance-migrating.md:6 -msgid "" -"This migration guide is applicable if you migrate from one server to " -"another server having the same CPU architecture (e.g. both servers being " -"`amd64`)." +msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)." msgstr "" #: ../../../docs/maintenance-migrating.md:8 -msgid "" -"If you're trying to migrate between different architectures (e.g. `amd64`" -" --> `arm64`), simply copying the complete `/matrix` directory is **not**" -" possible as it would move the raw PostgreSQL data " -"(`/matrix/postgres/data`) between different architectures. In this " -"specific case, you can use the guide below as a reference, but you would " -"also need to avoid syncing `/matrix/postgres/data` to the new host, and " -"also dump the database on your current server and import it properly on " -"the new server. See our [Backing up PostgreSQL](maintenance-postgres.md" -"#backing-up-postgresql) docs for help with PostgreSQL backup/restore." +msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore." msgstr "" #: ../../../docs/maintenance-migrating.md:9 -msgid "" -"If you have any questions about migration or encountered an issue during " -"migration, do not hesitate to ask for help on [our Matrix " -"room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). " -"You probably might want to prepare a temporary/sub account on another " -"Matrix server in case it becomes impossible to use your server due to " -"migration failure by any chance." +msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance." msgstr "" #: ../../../docs/maintenance-migrating.md:11 -msgid "" -"You can't change the domain (specified in the `matrix_domain` variable) " -"after the initial deployment." +msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment." msgstr "" #: ../../../docs/maintenance-migrating.md:13 @@ -76,10 +54,7 @@ msgid "Lower DNS TTL" msgstr "" #: ../../../docs/maintenance-migrating.md:15 -msgid "" -"Prepare by lowering DNS TTL for your domains (`matrix.example.com`, " -"etc.), so that DNS record changes would happen faster, leading to less " -"downtime." +msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime." msgstr "" #: ../../../docs/maintenance-migrating.md:17 @@ -87,22 +62,15 @@ msgid "Stop services on the old server completely" msgstr "" #: ../../../docs/maintenance-migrating.md:19 -msgid "" -"Before migrating, you need to stop all services on the old server and " -"make sure they won't be starting again." +msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again." msgstr "" #: ../../../docs/maintenance-migrating.md:21 -msgid "" -"To do so, it is recommended to run the `systemctl` command on the server." -" Running the playbook's `stop` tag also stops the services, but just " -"once; they will start again if you reboot the server." +msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server." msgstr "" #: ../../../docs/maintenance-migrating.md:23 -msgid "" -"Log in to the old server and run the command as `root` (or a user that " -"can run it with `sudo`):" +msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):" msgstr "" #: ../../../docs/maintenance-migrating.md:29 @@ -110,10 +78,7 @@ msgid "Copy data directory to the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:31 -msgid "" -"After you've confirmed that all services were stopped, copy the `/matrix`" -" directory from the old server to the new server. When copying, make sure" -" to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" +msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" msgstr "" #: ../../../docs/maintenance-migrating.md:33 @@ -121,9 +86,7 @@ msgid "Adjust DNS records" msgstr "" #: ../../../docs/maintenance-migrating.md:35 -msgid "" -"Make sure your DNS records are adjusted to point to the new server's IP " -"address." +msgid "Make sure your DNS records are adjusted to point to the new server's IP address." msgstr "" #: ../../../docs/maintenance-migrating.md:37 @@ -131,9 +94,7 @@ msgid "Update `inventory/hosts` file" msgstr "" #: ../../../docs/maintenance-migrating.md:39 -msgid "" -"Having adjusted DNS records, replace the old server's external IP address" -" on the `inventory/hosts` file with that of the new server." +msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server." msgstr "" #: ../../../docs/maintenance-migrating.md:41 @@ -141,23 +102,15 @@ msgid "Create `matrix` user and group on the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:43 -msgid "" -"Then, run the command below on your local computer to create the `matrix`" -" user and group on the new server:" +msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:" msgstr "" #: ../../../docs/maintenance-migrating.md:49 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags setup-system-user`" +msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`" msgstr "" #: ../../../docs/maintenance-migrating.md:51 -msgid "" -"**Note**: because the `matrix` user and group are created dynamically on " -"each server, the user/group ID may differ between the old and new server." -" We suggest that you adjust ownership of `/matrix` files. To adjust the " -"ownership, log in to the new server and run the command:" +msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:" msgstr "" #: ../../../docs/maintenance-migrating.md:57 @@ -165,15 +118,11 @@ msgid "Install and start all services on the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:59 -msgid "" -"Finally, run the command below on your local computer to finish the " -"installation and start all services:" +msgid "Finally, run the command below on your local computer to finish the installation and start all services:" msgstr "" #: ../../../docs/maintenance-migrating.md:65 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags install-all,start`" +msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`" msgstr "" #: ../../../docs/maintenance-migrating.md:67 @@ -181,16 +130,9 @@ msgid "Check if services work" msgstr "" #: ../../../docs/maintenance-migrating.md:69 -msgid "" -"After starting the services, you probably might want to ensure that " -"you've migrated things correctly and that services are running. For " -"instructions, see: [check if services work](maintenance-checking-" -"services.md)" +msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)" msgstr "" #: ../../../docs/maintenance-migrating.md:71 -msgid "" -"Having make sure that both services and federation work as expected, you " -"can safely shutdown the old server." +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 7c8da8391..5cea97a95 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po @@ -26,9 +26,7 @@ msgid "PostgreSQL maintenance" msgstr "" #: ../../../docs/maintenance-postgres.md:3 -msgid "" -"This document shows you how to perform various maintenance tasks related " -"to the Postgres database server used by Matrix." +msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix." msgstr "" #: ../../../docs/maintenance-postgres.md:5 @@ -36,28 +34,19 @@ msgid "Table of contents:" msgstr "" #: ../../../docs/maintenance-postgres.md:7 -msgid "" -"[Getting a database terminal](#getting-a-database-terminal), for when you" -" wish to execute SQL queries" +msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries" msgstr "" #: ../../../docs/maintenance-postgres.md:9 -msgid "" -"[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a" -" Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-" -"vacuum.html) (optimizing disk space)" +msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)" msgstr "" #: ../../../docs/maintenance-postgres.md:11 -msgid "" -"[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to " -"make a backup" +msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup" msgstr "" #: ../../../docs/maintenance-postgres.md:13 -msgid "" -"[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major" -" versions of PostgreSQL. Such **manual upgrades are sometimes required**." +msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**." msgstr "" #: ../../../docs/maintenance-postgres.md:15 @@ -69,22 +58,15 @@ msgid "Getting a database terminal" msgstr "" #: ../../../docs/maintenance-postgres.md:19 -msgid "" -"You can use the `/matrix/postgres/bin/cli` tool to get interactive " -"terminal access ([psql](https://www.postgresql.org/docs/11/app-" -"psql.html)) to the PostgreSQL server." +msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server." msgstr "" #: ../../../docs/maintenance-postgres.md:21 -msgid "" -"If you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), the above tool will not be available." +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available." msgstr "" #: ../../../docs/maintenance-postgres.md:23 -msgid "" -"By default, this tool puts you in the `matrix` database, which contains " -"nothing." +msgid "By default, this tool puts you in the `matrix` database, which contains nothing." msgstr "" #: ../../../docs/maintenance-postgres.md:25 @@ -92,23 +74,15 @@ msgid "To see the available databases, run `\\list` (or just `\\l`)." msgstr "" #: ../../../docs/maintenance-postgres.md:27 -msgid "" -"To change to another database (for example `synapse`), run `\\connect " -"synapse` (or just `\\c synapse`)." +msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)." msgstr "" #: ../../../docs/maintenance-postgres.md:29 -msgid "" -"You can then proceed to write queries. Example: `SELECT COUNT(*) FROM " -"users;`" +msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`" msgstr "" #: ../../../docs/maintenance-postgres.md:31 -msgid "" -"**Be careful**. Modifying the database directly (especially as services " -"are running) is dangerous and may lead to irreversible database " -"corruption. When in doubt, consider [making a backup](#backing-up-" -"postgresql)." +msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)." msgstr "" #: ../../../docs/maintenance-postgres.md:33 @@ -116,28 +90,19 @@ msgid "Vacuuming PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:35 -msgid "" -"Deleting lots data from Postgres does not make it release disk space, " -"until you perform a [`VACUUM` " -"operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." +msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." msgstr "" #: ../../../docs/maintenance-postgres.md:37 -msgid "" -"You can run different `VACUUM` operations via the playbook, with the " -"default preset being `vacuum-complete`:" +msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:" msgstr "" #: ../../../docs/maintenance-postgres.md:39 -msgid "" -"(default) `vacuum-complete`: stops all services temporarily and runs " -"`VACUUM FULL VERBOSE ANALYZE`." +msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`." msgstr "" #: ../../../docs/maintenance-postgres.md:40 -msgid "" -"`vacuum-full`: stops all services temporarily and runs `VACUUM FULL " -"VERBOSE`" +msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`" msgstr "" #: ../../../docs/maintenance-postgres.md:41 @@ -145,24 +110,15 @@ msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" msgstr "" #: ../../../docs/maintenance-postgres.md:42 -msgid "" -"`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any " -"services" +msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services" msgstr "" #: ../../../docs/maintenance-postgres.md:43 -msgid "" -"`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is " -"just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) " -"without doing a vacuum, so it's faster)" +msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)" msgstr "" #: ../../../docs/maintenance-postgres.md:45 -msgid "" -"**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll " -"need plenty of available disk space in your Postgres data directory " -"(usually `/matrix/postgres/data`). These presets also stop all services " -"(e.g. Synapse, etc.) while the vacuum operation is running." +msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running." msgstr "" #: ../../../docs/maintenance-postgres.md:47 @@ -170,16 +126,11 @@ msgid "Example playbook invocations:" msgstr "" #: ../../../docs/maintenance-postgres.md:49 -msgid "" -"`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` " -"preset and restarts all services" +msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services" msgstr "" #: ../../../docs/maintenance-postgres.md:50 -msgid "" -"`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: " -"runs the `analyze` preset with all services remaining operational at all " -"times" +msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times" msgstr "" #: ../../../docs/maintenance-postgres.md:52 @@ -187,29 +138,19 @@ msgid "Backing up PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:54 -msgid "" -"To automatically make Postgres database backups on a fixed schedule, see " -"[Setting up postgres backup](configuring-playbook-postgres-backup.md)." +msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)." msgstr "" #: ../../../docs/maintenance-postgres.md:56 -msgid "" -"To make a one off back up of the current PostgreSQL database, make sure " -"it's running and then execute a command like this on the server:" +msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" msgstr "" #: ../../../docs/maintenance-postgres.md:67 -msgid "" -"If you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), the above command will not work, because neither " -"the credentials file (`/matrix/postgres/env-postgres-psql`), nor the " -"`matrix-postgres` container is available." +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available." msgstr "" #: ../../../docs/maintenance-postgres.md:69 -msgid "" -"Restoring a backup made this way can be done by [importing it](importing-" -"postgres.md)." +msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)." msgstr "" #: ../../../docs/maintenance-postgres.md:71 @@ -217,16 +158,11 @@ msgid "Upgrading PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:73 -msgid "" -"Unless you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), this playbook initially installs Postgres for you." +msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you." msgstr "" #: ../../../docs/maintenance-postgres.md:75 -msgid "" -"Once installed, the playbook attempts to preserve the Postgres version it" -" starts with. This is because newer Postgres versions cannot start with " -"data generated by older Postgres versions." +msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions." msgstr "" #: ../../../docs/maintenance-postgres.md:77 @@ -234,42 +170,23 @@ msgid "Upgrades must be performed manually." msgstr "" #: ../../../docs/maintenance-postgres.md:79 -msgid "" -"This playbook can upgrade your existing Postgres setup with the following" -" command:" +msgid "This playbook can upgrade your existing Postgres setup with the following command:" msgstr "" #: ../../../docs/maintenance-postgres.md:85 -msgid "" -"**The old Postgres data directory is backed up** automatically, by " -"renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to " -"a different path, pass some extra flags to the command above, like this: " -"`--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk" -"/matrix-postgres-before-upgrade\"`" +msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:87 -msgid "" -"The auto-upgrade-backup directory stays around forever, until you " -"**manually decide to delete it**." +msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**." msgstr "" #: ../../../docs/maintenance-postgres.md:89 -msgid "" -"As part of the upgrade, the database is dumped to `/tmp`, an upgraded and" -" empty Postgres server is started, and then the dump is restored into the" -" new server. To use a different directory for the dump, pass some extra " -"flags to the command above, like this: `--extra-" -"vars=\"postgres_dump_dir=/directory/to/dump/here\"`" +msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:91 -msgid "" -"To save disk space in `/tmp`, the dump file is gzipped on the fly at the " -"expense of CPU usage. If you have plenty of space in `/tmp` and would " -"rather avoid gzipping, you can explicitly pass a dump filename which " -"doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-" -"postgres-dump.sql\"`" +msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:93 @@ -281,56 +198,25 @@ msgid "Tuning PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:97 -msgid "" -"PostgreSQL can be " -"[tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) " -"to make it run faster. This is done by passing extra arguments to the " -"Postgres process." +msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process." msgstr "" #: ../../../docs/maintenance-postgres.md:99 -msgid "" -"The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-postgres) **already does some tuning by default**, which " -"matches the [tuning " -"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" -" done by websites like https://pgtune.leopard.in.ua/. You can manually " -"influence some of the tuning variables. These parameters (variables) are " -"injected via the `postgres_postgres_process_extra_arguments_auto` " -"variable." +msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable." msgstr "" #: ../../../docs/maintenance-postgres.md:101 -msgid "" -"Most users should be fine with the automatically-done tuning. However, " -"you may wish to:" +msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:" msgstr "" #: ../../../docs/maintenance-postgres.md:103 -msgid "" -"**adjust the automatically-determined tuning parameters manually**: " -"change the values for the tuning variables defined in the Postgres role's" -" [default configuration file](https://github.com/mother-of-all-self-" -"hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see " -"`postgres_max_connections`, `postgres_data_storage` etc). These variables" -" are ultimately passed to Postgres via a " -"`postgres_postgres_process_extra_arguments_auto` variable" +msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable" msgstr "" #: ../../../docs/maintenance-postgres.md:105 -msgid "" -"**turn automatically-performed tuning off**: override it like this: " -"`postgres_postgres_process_extra_arguments_auto: []`" +msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`" msgstr "" #: ../../../docs/maintenance-postgres.md:107 -msgid "" -"**add additional tuning parameters**: define your additional Postgres " -"configuration parameters in " -"`postgres_postgres_process_extra_arguments_custom`. See " -"`postgres_postgres_process_extra_arguments_auto` defined in the Postgres " -"role's [default configuration file](https://github.com/mother-of-all-" -"self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for " -"inspiration" +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 e53044eb6..1d92a8229 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po @@ -26,9 +26,7 @@ msgid "Synapse maintenance" msgstr "" #: ../../../docs/maintenance-synapse.md:3 -msgid "" -"This document shows you how to perform various maintenance tasks related " -"to the Synapse chat server." +msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server." msgstr "" #: ../../../docs/maintenance-synapse.md:5 @@ -36,22 +34,15 @@ msgid "Table of contents:" msgstr "" #: ../../../docs/maintenance-synapse.md:7 -msgid "" -"[Purging old data with the Purge History API](#purging-old-data-with-the-" -"purge-history-api), for when you wish to delete in-use (but old) data " -"from the Synapse database" +msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database" msgstr "" #: ../../../docs/maintenance-synapse.md:9 -msgid "" -"[Compressing state with rust-synapse-compress-state](#compressing-state-" -"with-rust-synapse-compress-state)" +msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)" msgstr "" #: ../../../docs/maintenance-synapse.md:11 -msgid "" -"[Browse and manipulate the database](#browse-and-manipulate-the-" -"database), for when you really need to take matters into your own hands" +msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands" msgstr "" #: ../../../docs/maintenance-synapse.md:13 @@ -63,42 +54,23 @@ msgid "Purging old data with the Purge History API" msgstr "" #: ../../../docs/maintenance-synapse.md:17 -msgid "" -"You can use the **[Purge History API](https://github.com/element-" -"hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete " -"old messages on a per-room basis. **This is destructive** (especially for" -" non-federated rooms), because it means **people will no longer have " -"access to history past a certain point**." +msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**." msgstr "" #: ../../../docs/maintenance-synapse.md:19 -msgid "" -"To make use of this Synapse Admin API, **you'll need an admin access " -"token** first. Refer to the documentation on [how to obtain an access " -"token](obtaining-access-tokens.md)." +msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/maintenance-synapse.md:21 -msgid "" -"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." +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:23 -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." +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:25 -msgid "" -"After deleting data, you may wish to run a [`FULL` Postgres `VACUUM" -"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:27 @@ -106,27 +78,15 @@ msgid "Compressing state with rust-synapse-compress-state" msgstr "" #: ../../../docs/maintenance-synapse.md:29 -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." +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:31 -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." +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:33 -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." +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:35 @@ -134,23 +94,15 @@ msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" #: ../../../docs/maintenance-synapse.md:41 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags rust-synapse-compress-state`" +msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" #: ../../../docs/maintenance-synapse.md:43 -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." +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:45 -msgid "" -"After state compression, you may wish to run a [`FULL` Postgres `VACUUM" -"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:47 @@ -158,46 +110,27 @@ msgid "Browse and manipulate the database" msgstr "" #: ../../../docs/maintenance-synapse.md:49 -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." +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:51 -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)." +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:53 -msgid "" -"First, set up an SSH tunnel to your Matrix server (skip if it is your " -"local machine):" +msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" #: ../../../docs/maintenance-synapse.md:60 -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:" +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:66 -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`)" +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:68 -msgid "" -"⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB " -"operations." +msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" #: ../../../docs/maintenance-synapse.md:70 @@ -205,28 +138,15 @@ msgid "Make Synapse faster" msgstr "" #: ../../../docs/maintenance-synapse.md:72 -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." +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:74 -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)." +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:76 -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." +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:78 @@ -234,44 +154,27 @@ msgid "Tuning caches and cache autotuning" msgstr "" #: ../../../docs/maintenance-synapse.md:80 -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." +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:82 -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)." +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:84 -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)." +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:86 -msgid "" -"Cache autotuning is **enabled by default** and controlled via the " -"following variables:" +msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" #: ../../../docs/maintenance-synapse.md:88 -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" +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:89 -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" +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:90 @@ -279,12 +182,7 @@ msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" #: ../../../docs/maintenance-synapse.md:92 -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)." +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:94 @@ -292,19 +190,9 @@ msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" #: ../../../docs/maintenance-synapse.md:102 -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." +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:104 -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)." +msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po index 24c523733..495acd2e7 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po @@ -22,46 +22,27 @@ msgid "Upgrading the Matrix services" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:3 -msgid "" -"This playbook not only installs the various Matrix services for you, but " -"can also upgrade them as new versions are made available." +msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:5 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:7 -msgid "" -"The upstream projects, which this playbook makes use of, occasionally if " -"not often suffer from security vulnerabilities (for example, see " -"[here](https://github.com/element-hq/element-web/security) for known ones" -" on Element Web)." +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:9 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:11 -msgid "" -"The developers of this playbook strive to maintain the playbook updated, " -"so that you can re-run the playbook to address such vulnerabilities. It " -"is **your responsibility** to keep your server and the services on it up-" -"to-date." +msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:13 -msgid "" -"If you want to be notified when new versions of Synapse are released, you" -" should join the Synapse Homeowners room: " -"[#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." +msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:15 @@ -73,10 +54,7 @@ msgid "Check the changelog" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:19 -msgid "" -"Before updating the playbook and the Ansible roles in the playbook, take " -"a look at [the changelog](../CHANGELOG.md) to see if there have been any " -"backward-incompatible changes that you need to take care of." +msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:21 @@ -84,10 +62,7 @@ msgid "Update the playbook and the Ansible roles" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:23 -msgid "" -"If it looks good to you, go to the `matrix-docker-ansible-deploy` " -"directory, update your playbook directory and all upstream Ansible roles " -"(defined in the `requirements.yml` file) by running:" +msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:25 @@ -95,22 +70,15 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:26 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:28 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:30 -msgid "" -"**Note**: for details about `just` commands, take a look at: [Running " -"`just` commands](just.md)." +msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:32 @@ -118,18 +86,11 @@ msgid "Re-run the playbook setup" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:34 -msgid "" -"After updating the Ansible roles, then re-run the [playbook " -"setup](installing.md#maintaining-your-setup-in-the-future) and restart " -"all services:" +msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:40 -msgid "" -"If you remove components from `vars.yml`, or if we switch some component " -"from being installed by default to not being installed by default " -"anymore, you'd need to run the setup command with the `setup-all` tag as " -"below:" +msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:46 @@ -137,31 +98,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:48 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account, if any." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:50 -msgid "" -"Our estimation is that running `--tags=install-all,start` is " -"approximately from **2 to 5 times faster** than running `setup-all" -",ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-" -"5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for " -"more information." +msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:52 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`. Note these shortcuts " -"run the `ensure-matrix-users-created` tag too." +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:54 -msgid "" -"See [this page on the playbook tags](playbook-tags.md) for more " -"information about those tags." +msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:56 @@ -169,14 +118,9 @@ msgid "PostgreSQL major version upgrade" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:58 -msgid "" -"Major version upgrades to the internal PostgreSQL database are not done " -"automatically. Upgrades must be performed manually." +msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:60 -msgid "" -"For details about upgrading it, refer to the [upgrading PostgreSQL guide" -"](maintenance-postgres.md#upgrading-postgresql)." +msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po index 5edcad58c..f14ecacfd 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -26,16 +26,11 @@ msgid "Obtaining an Access Token" msgstr "" #: ../../../docs/obtaining-access-tokens.md:3 -msgid "" -"When setting up some optional features like bots and bridges you will " -"need to provide an access token for some user. This document provides " -"documentation on how to obtain such an access token." +msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token." msgstr "" #: ../../../docs/obtaining-access-tokens.md:5 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/obtaining-access-tokens.md:7 @@ -43,17 +38,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/obtaining-access-tokens.md:9 -msgid "" -"The user for whom you want to obtain an access token needs to already " -"exist. You can use this playbook to [register a new user](registering-" -"users.md), if you have not already." +msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already." msgstr "" #: ../../../docs/obtaining-access-tokens.md:11 -msgid "" -"Below, we describe 2 ways to generate an access token for a user - using " -"[Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-" -"an-access-token-via-curl). For both ways you need the user's password." +msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password." msgstr "" #: ../../../docs/obtaining-access-tokens.md:13 @@ -69,9 +58,7 @@ msgid "Log in with the user's credentials." msgstr "" #: ../../../docs/obtaining-access-tokens.md:17 -msgid "" -"In the settings page, choose \"Help & About\", scroll down to the bottom " -"and expand the `Access Token` section (see screenshot below)." +msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)." msgstr "" #: ../../../docs/obtaining-access-tokens.md:18 @@ -79,15 +66,11 @@ msgid "Copy the access token to your configuration." msgstr "" #: ../../../docs/obtaining-access-tokens.md:19 -msgid "" -"Close the private browsing session. **Do not log out**. Logging out will " -"invalidate the token, making it not work." +msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work." msgstr "" #: ../../../docs/obtaining-access-tokens.md:21 -msgid "" -"![Obtaining an access token with Element " -"Web](assets/obtain_admin_access_token_element_web.png)" +msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)" msgstr "" #: ../../../docs/obtaining-access-tokens.md:21 @@ -99,10 +82,7 @@ msgid "Obtain an access token via curl" msgstr "" #: ../../../docs/obtaining-access-tokens.md:25 -msgid "" -"You can use the following command to get an access token for your user " -"directly from the [Matrix Client-Server " -"API](https://www.matrix.org/docs/guides/client-server-api#login):" +msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):" msgstr "" #: ../../../docs/obtaining-access-tokens.md:35 @@ -110,13 +90,9 @@ msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly." msgstr "" #: ../../../docs/obtaining-access-tokens.md:37 -msgid "" -"`YOURDEVICEID` is optional and can be used to more easily identify the " -"session later. When omitted (mind the commas in the JSON payload if " -"you'll be omitting it), a random device ID will be generated." +msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated." msgstr "" #: ../../../docs/obtaining-access-tokens.md:39 msgid "Your response will look like this (prettified):" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po index af10301e8..d25b07a92 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po @@ -26,15 +26,11 @@ msgid "Playbook tags" msgstr "" #: ../../../docs/playbook-tags.md:3 -msgid "" -"The Ansible playbook's tasks are tagged, so that certain parts of the " -"Ansible playbook can be run without running all other tasks." +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" #: ../../../docs/playbook-tags.md:5 -msgid "" -"The general command syntax is: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" +msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" msgstr "" #: ../../../docs/playbook-tags.md:7 @@ -42,44 +38,23 @@ msgid "Here are some playbook tags that you should be familiar with:" msgstr "" #: ../../../docs/playbook-tags.md:9 -msgid "" -"`setup-all` - runs all setup tasks (installation and uninstallation) for " -"all components, but does not start/restart services" +msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services" msgstr "" #: ../../../docs/playbook-tags.md:11 -msgid "" -"`install-all` - like `setup-all`, but skips uninstallation tasks. Useful " -"for maintaining your setup quickly when its components remain unchanged. " -"If you adjust your `vars.yml` to remove components, you'd need to run " -"`setup-all` though, or these components will still remain installed" +msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed" msgstr "" #: ../../../docs/playbook-tags.md:13 -msgid "" -"`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for" -" a given role, but does not start/restart services. You can discover " -"these additional tags in each role (`roles/**/tasks/main.yml`). Running " -"per-component setup tasks is **not recommended**, as components sometimes" -" depend on each other and running just the setup tasks for a given " -"component may not be enough. For example, setting up the [mautrix-" -"telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in " -"addition to the `setup-mautrix-telegram` tag, requires database changes " -"(the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-" -"nginx-proxy` tag)." +msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)." msgstr "" #: ../../../docs/playbook-tags.md:15 -msgid "" -"`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but" -" skips uninstallation tasks. See `install-all` above for additional " -"information." +msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information." msgstr "" #: ../../../docs/playbook-tags.md:17 -msgid "" -"`start` - starts all systemd services and makes them start automatically " -"in the future" +msgid "`start` - starts all systemd services and makes them start automatically in the future" msgstr "" #: ../../../docs/playbook-tags.md:19 @@ -87,9 +62,7 @@ msgid "`stop` - stops all systemd services" msgstr "" #: ../../../docs/playbook-tags.md:21 -msgid "" -"`ensure-matrix-users-created` - a special tag which ensures that all " -"special users needed by the playbook (for bots, etc.) are created" +msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created" msgstr "" #: ../../../docs/playbook-tags.md:23 @@ -97,17 +70,9 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/playbook-tags.md:24 -msgid "" -"`setup-*` tags and `install-*` tags **do not start services** " -"automatically, because you may wish to do things before starting " -"services, such as importing a database dump, restoring data from another " -"server, etc." +msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc." msgstr "" #: ../../../docs/playbook-tags.md:25 -msgid "" -"Please be careful not to confuse the playbook tags with the `just` " -"shortcut commands (\"recipes\"). For details about `just` commands, see: " -"[Running `just` commands](just.md)" +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 b3df2522e..9ae3849bd 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po @@ -26,33 +26,19 @@ msgid "Prerequisites" msgstr "" #: ../../../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)" +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: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." +msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step." msgstr "" #: ../../../docs/prerequisites.md:7 -msgid "" -"We will be using `example.com` as the domain in the following " -"instruction. Please remember to replace it with your own domain before " -"running any commands." +msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands." msgstr "" #: ../../../docs/prerequisites.md:9 -msgid "" -"**Note**: if you do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\", we suggest you to follow ⚡ " -"**[Quick start](quick-start.md)** installation guide." +msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide." msgstr "" #: ../../../docs/prerequisites.md:11 @@ -60,49 +46,23 @@ msgid "Your local computer" msgstr "" #: ../../../docs/prerequisites.md:13 -msgid "" -"[Ansible](http://ansible.com/) program. It's used to run this playbook " -"and configures your server for you. Take a look at [our guide about " -"Ansible](ansible.md) for more information, as well as [version " -"requirements](ansible.md#supported-ansible-versions) and alternative ways" -" to run Ansible." +msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible." msgstr "" #: ../../../docs/prerequisites.md:15 -msgid "" -"[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python " -"library. See [this official " -"documentation](https://passlib.readthedocs.io/en/stable/install.html" -"#installation-instructions) for an instruction to install it. On most " -"distros, you need to install some `python-passlib` or `py3-passlib` " -"package, etc." +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." +msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components." msgstr "" #: ../../../docs/prerequisites.md:19 -msgid "" -"[`just`](https://github.com/casey/just) for running `just roles`, `just " -"update`, etc. (see [`justfile`](../justfile)), although you can also run " -"these commands manually. Take at look at this documentation for more " -"information: [Running `just` commands](just.md)." +msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/prerequisites.md:21 -msgid "" -"Strong password (random strings) generator. The playbook often requires " -"you to create a strong password and use it for settings on `vars.yml`, " -"components, etc. As any tools should be fine, this playbook has adopted " -"[`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). " -"[Password Tech](https://pwgen-win.sourceforge.io/), formerly known as " -"\"PWGen for Windows\", is available as free and open source password " -"generator for Windows. Generally, using a random generator available on " -"the internet is not recommended." +msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended." msgstr "" #: ../../../docs/prerequisites.md:23 @@ -110,10 +70,7 @@ msgid "Server" msgstr "" #: ../../../docs/prerequisites.md:25 -msgid "" -"(Recommended) An **x86** server ([What kind of server specs do I " -"need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these " -"operating systems that make use of [systemd](https://systemd.io/):" +msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):" msgstr "" #: ../../../docs/prerequisites.md:26 @@ -121,9 +78,7 @@ msgid "**Archlinux**" msgstr "" #: ../../../docs/prerequisites.md:27 -msgid "" -"**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL " -"alternatives (although your mileage may vary)" +msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)" msgstr "" #: ../../../docs/prerequisites.md:28 @@ -131,82 +86,43 @@ msgid "**Debian** (10/Buster or newer)" msgstr "" #: ../../../docs/prerequisites.md:29 -msgid "" -"**Ubuntu** (18.04 or newer, although [20.04 may be " -"problematic](ansible.md#supported-ansible-versions) if you run the " -"Ansible playbook on it)" +msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)" msgstr "" #: ../../../docs/prerequisites.md:31 -msgid "" -"Generally, newer is better. We only strive to support released stable " -"versions of distributions, not betas or pre-releases. This playbook can " -"take over your whole server or co-exist with other services that you have" -" there." +msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there." msgstr "" #: ../../../docs/prerequisites.md:33 -msgid "" -"This playbook somewhat supports running on non-`amd64` architectures like" -" ARM. See [Alternative Architectures](alternative-architectures.md)." +msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)." msgstr "" #: ../../../docs/prerequisites.md:35 -msgid "" -"If your distro runs within an [LXC " -"container](https://linuxcontainers.org/), you may hit [this " -"issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/703). It can be worked around, if absolutely necessary, but" -" we suggest that you avoid running from within an LXC container." +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" #: ../../../docs/prerequisites.md:37 -msgid "" -"`root` access to your server (or a user capable of elevating to `root` " -"via `sudo`)." +msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)." msgstr "" #: ../../../docs/prerequisites.md:39 -msgid "" -"[Python](https://www.python.org/). Most distributions install Python by " -"default, but some don't (e.g. Ubuntu 18.04) and require manual " -"installation (something like `apt-get install python3`). On some distros," -" Ansible may incorrectly [detect the Python " -"version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html)" -" (2 vs 3) and you may need to explicitly specify the interpreter path in " -"`inventory/hosts` during installation (e.g. " -"`ansible_python_interpreter=/usr/bin/python3`)" +msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)" msgstr "" #: ../../../docs/prerequisites.md:41 -msgid "" -"[sudo](https://www.sudo.ws/), even when you've configured Ansible to log " -"in as `root`. Some distributions, like a minimal Debian net install, do " -"not include the `sudo` package by default." +msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." msgstr "" #: ../../../docs/prerequisites.md:43 -msgid "" -"An HTTPS-capable web server at the base domain name (`example.com`) which" -" is capable of serving static files. Unless you decide to [Serve the base" -" domain from the Matrix server](configuring-playbook-base-domain-" -"serving.md) or alternatively, to use DNS SRV records for [Server " -"Delegation](howto-server-delegation.md)." +msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)." msgstr "" #: ../../../docs/prerequisites.md:45 -msgid "" -"Properly configured DNS records for `example.com` (details in " -"[Configuring DNS](configuring-dns.md))." +msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))." msgstr "" #: ../../../docs/prerequisites.md:47 -msgid "" -"Some TCP/UDP ports open. This playbook (actually [Docker " -"itself](https://docs.docker.com/network/iptables/)) configures the " -"server's internal firewall for you. In most cases, you don't need to do " -"anything special. But **if your server is running behind another " -"firewall**, you'd need to open these ports:" +msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:" msgstr "" #: ../../../docs/prerequisites.md:49 @@ -234,11 +150,7 @@ msgid "`5349/udp`: TURN over UDP (used by Coturn)" msgstr "" #: ../../../docs/prerequisites.md:55 -msgid "" -"`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some" -" cases, this **may necessary even with federation disabled**. Integration" -" Servers (like Dimension) and Identity Servers (like ma1sd) may need to " -"access `openid` APIs on the federation port." +msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port." msgstr "" #: ../../../docs/prerequisites.md:56 @@ -246,15 +158,9 @@ 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." +msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." msgstr "" #: ../../../docs/prerequisites.md:61 -msgid "" -"[▶️](configuring-dns.md) When ready to proceed, continue with " -"[Configuring DNS](configuring-dns.md)." +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 54f941341..5bec8b522 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po @@ -26,15 +26,11 @@ msgid "Quick start" msgstr "" #: ../../../docs/quick-start.md:9 -msgid "" -"This page explains how to use this Ansible playbook to install Matrix " -"services on your server with a minimal set of core services." +msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." msgstr "" #: ../../../docs/quick-start.md:11 -msgid "" -"We will be using `example.com` as the \"base domain\" in the following " -"instruction." +msgid "We will be using `example.com` as the \"base domain\" in the following instruction." msgstr "" #: ../../../docs/quick-start.md:13 @@ -42,9 +38,7 @@ msgid "By following the instruction on this page, you will set up:" msgstr "" #: ../../../docs/quick-start.md:15 -msgid "" -"**your own Matrix server** on a `matrix.example.com` server, which is " -"configured to present itself as `example.com`" +msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" msgstr "" #: ../../../docs/quick-start.md:16 @@ -52,23 +46,15 @@ msgid "**your user account** like `@alice:example.com` on the server" msgstr "" #: ../../../docs/quick-start.md:17 -msgid "" -"a **self-hosted Matrix client**, [Element Web](configuring-playbook-" -"client-element-web.md) with the default subdomain at " -"`element.example.com`" +msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" msgstr "" #: ../../../docs/quick-start.md:18 -msgid "" -"Matrix delegation, so that your `matrix.example.com` server (presenting " -"itself as `example.com`) can join the Matrix Federation and communicate " -"with any other server in the Matrix network" +msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" msgstr "" #: ../../../docs/quick-start.md:20 -msgid "" -"Please remember to replace `example.com` with your own domain before " -"running any commands." +msgid "Please remember to replace `example.com` with your own domain before running any commands." msgstr "" #: ../../../docs/quick-start.md:22 @@ -76,40 +62,23 @@ msgid "Prerequisites" msgstr "" #: ../../../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)" +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: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)." +msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)." msgstr "" #: ../../../docs/quick-start.md:28 -msgid "" -"When preparing your server, make sure to check [the server specs you " -"need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting " -"with a server having at least 2GB of memory." +msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory." msgstr "" #: ../../../docs/quick-start.md:34 -msgid "" -"If you encounter an error during installation, please make sure that you " -"have installed and configured programs correctly." +msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly." msgstr "" #: ../../../docs/quick-start.md:36 -msgid "" -"One of the main reasons of basic errors is using an incompatible version " -"of required software such as Ansible. Take a look at [our guide about " -"Ansible](ansible.md) for more information. In short: installing the " -"latest available version is recommended." +msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended." msgstr "" #: ../../../docs/quick-start.md:38 @@ -117,22 +86,15 @@ msgid "Configure your DNS settings" msgstr "" #: ../../../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)" +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:42 -msgid "" -"After installing and configuring prerequisites, you will need to " -"**configure DNS records**." +msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." msgstr "" #: ../../../docs/quick-start.md:44 -msgid "" -"To configure Matrix services in the default settings, go to your DNS " -"service provider, and adjust DNS records as below." +msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below." msgstr "" #: ../../../docs/quick-start.md @@ -188,10 +150,7 @@ msgid "`matrix.example.com`" msgstr "" #: ../../../docs/quick-start.md:51 -msgid "" -"As the table illustrates, you need to create 2 subdomains " -"(`matrix.example.com` and `element.example.com`) and point both of them " -"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" #: ../../../docs/quick-start.md:53 @@ -199,9 +158,7 @@ msgid "It might take some time for the DNS records to propagate after creation." msgstr "" #: ../../../docs/quick-start.md:55 -msgid "" -"**💡 Note**: if you are using Cloudflare DNS, make sure to disable the " -"proxy and set all records to \"DNS only\"" +msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" msgstr "" #: ../../../docs/quick-start.md:57 @@ -209,10 +166,7 @@ msgid "Get the playbook" msgstr "" #: ../../../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)" +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:61 @@ -220,22 +174,15 @@ msgid "Next, let's **get the playbook's source code**." msgstr "" #: ../../../docs/quick-start.md:63 -msgid "" -"We recommend to do so with [git](https://git-scm.com/) as it enables you " -"to keep it up to date with the latest source code. While it is possible " -"to download the playbook as a ZIP archive, it is not recommended." +msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended." msgstr "" #: ../../../docs/quick-start.md:65 -msgid "" -"To get the playbook with git, install git on your computer, go to a " -"directory, and run the command:" +msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:" msgstr "" #: ../../../docs/quick-start.md:71 -msgid "" -"It will fetch the playbook to a new `matrix-docker-ansible-deploy` " -"directory underneath the directory you are currently in." +msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in." msgstr "" #: ../../../docs/quick-start.md:73 @@ -243,47 +190,31 @@ msgid "Configure the playbook" msgstr "" #: ../../../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)" +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:77 -msgid "" -"Now that the playbook was fetched, it is time to **configure** it per " -"your needs." +msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." msgstr "" #: ../../../docs/quick-start.md:79 -msgid "" -"To install Matrix services with this playbook, you would at least need 2 " -"configuration files." +msgid "To install Matrix services with this playbook, you would at least need 2 configuration files." msgstr "" #: ../../../docs/quick-start.md:81 -msgid "" -"For your convenience, we have prepared example files of them " -"([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." +msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." msgstr "" #: ../../../docs/quick-start.md:83 -msgid "" -"To start quickly based on these example files, go into the `matrix-" -"docker-ansible-deploy` directory and follow the instructions below:" +msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:" msgstr "" #: ../../../docs/quick-start.md:85 -msgid "" -"Create a directory to hold your configuration: `mkdir -p " -"inventory/host_vars/matrix.example.com` where `example.com` is your " -"\"base domain\"" +msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\"" msgstr "" #: ../../../docs/quick-start.md:86 -msgid "" -"Copy the sample configuration file: `cp examples/vars.yml " -"inventory/host_vars/matrix.example.com/vars.yml`" +msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`" msgstr "" #: ../../../docs/quick-start.md:87 @@ -291,9 +222,7 @@ msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts` msgstr "" #: ../../../docs/quick-start.md:88 -msgid "" -"Edit the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`)" +msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" #: ../../../docs/quick-start.md:89 @@ -301,9 +230,7 @@ msgid "Edit the inventory hosts file (`inventory/hosts`)" msgstr "" #: ../../../docs/quick-start.md:91 -msgid "" -"Before editing these 2 files, make sure to read explanations on them to " -"understand what needs to be configured." +msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured." msgstr "" #: ../../../docs/quick-start.md:93 @@ -311,30 +238,15 @@ msgid "**💡 Notes:**" msgstr "" #: ../../../docs/quick-start.md:94 -msgid "" -"If you are not in control of anything on the base domain, you would need " -"to set additional configuration on `vars.yml`. For more information, see " -"[How do I install on matrix.example.com without involving the base " -"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" -"the-base-domain) on our FAQ." +msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" #: ../../../docs/quick-start.md:95 -msgid "" -"Certain configuration decisions (like the base domain configured in " -"`matrix_domain` and homeserver implementation configured in " -"`matrix_homeserver_implementation`) are final. If you make the wrong " -"choice and wish to change it, you'll have to run the Uninstalling step " -"and start over." +msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over." msgstr "" #: ../../../docs/quick-start.md:96 -msgid "" -"Instead of configuring a lot of things all at once, we recommend starting" -" with the basic (default) settings in order to get yourself familiar with" -" how the playbook works. After making sure that everything works as " -"expected, you can add (and remove) advanced settings / features and run " -"the playbook as many times as you wish." +msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish." msgstr "" #: ../../../docs/quick-start.md:98 @@ -342,16 +254,11 @@ msgid "Install" msgstr "" #: ../../../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)" +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:102 -msgid "" -"After editing `vars.yml` and `hosts` files, let's start the " -"**installation** procedure." +msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." msgstr "" #: ../../../docs/quick-start.md:104 @@ -359,9 +266,7 @@ msgid "Update Ansible roles" msgstr "" #: ../../../docs/quick-start.md:106 -msgid "" -"Before installing, you need to update the Ansible roles that this " -"playbook uses and fetches from outside." +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" #: ../../../docs/quick-start.md:108 @@ -373,16 +278,11 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/quick-start.md:111 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/quick-start.md:113 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/quick-start.md:115 @@ -394,22 +294,15 @@ msgid "Then, run the command below to start installation:" msgstr "" #: ../../../docs/quick-start.md:123 -msgid "" -"If you **don't** use SSH keys for authentication, but rather a regular " -"password, you may need to add `--ask-pass` to the command." +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command." msgstr "" #: ../../../docs/quick-start.md:125 -msgid "" -"If you **do** use SSH keys for authentication, **and** use a non-root " -"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" -"pass`) to the command." +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command." msgstr "" #: ../../../docs/quick-start.md:127 -msgid "" -"Wait until the command completes. If it's all green, everything should be" -" running properly." +msgid "Wait until the command completes. If it's all green, everything should be running properly." msgstr "" #: ../../../docs/quick-start.md:129 @@ -417,22 +310,15 @@ msgid "Create your user account" msgstr "" #: ../../../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)" +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:133 -msgid "" -"As you have configured your brand new server and the client, you need to " -"**create your user account** on your Matrix server." +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" #: ../../../docs/quick-start.md:135 -msgid "" -"To create your user account (as an administrator of the server) via this " -"Ansible playbook, run the command below on your local computer." +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" #: ../../../docs/quick-start.md:137 @@ -444,9 +330,7 @@ msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" #: ../../../docs/quick-start.md:139 -msgid "" -"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " -"full ID (`@alice:example.com`)" +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/quick-start.md:151 @@ -454,77 +338,43 @@ msgid "Finalize server installation" msgstr "" #: ../../../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)" +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: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." +msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" #: ../../../docs/quick-start.md:157 -msgid "" -"**This is required for federation to work!** Without a proper " -"configuration, your server will effectively not be part of the Matrix " -"network." +msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/quick-start.md:159 -msgid "" -"To configure the delegation, you have these two options. Choose one of " -"them according to your situation." +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" #: ../../../docs/quick-start.md:161 -msgid "" -"If you can afford to point the base domain at the Matrix server, follow " -"the instruction below which guides you into [serving the base domain" -"](configuring-playbook-base-domain-serving.md) from the integrated web " -"server." +msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server." msgstr "" #: ../../../docs/quick-start.md:162 -msgid "" -"Alternatively, if you're using the base domain for other purposes and " -"cannot point it to the Matrix server (and thus cannot \"serve the base " -"domain\" from it), you most likely need to [manually install well-known " -"files on the base domain's server](configuring-well-known.md#manually-" -"installing-well-known-files-on-the-base-domains-server)." +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)." msgstr "" #: ../../../docs/quick-start.md:164 -msgid "" -"To have the base domain served from the integrated web server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/quick-start.md:170 -msgid "" -"After configuring the playbook, run the command below and wait until it " -"finishes:" +msgid "After configuring the playbook, run the command below and wait until it finishes:" msgstr "" #: ../../../docs/quick-start.md:176 -msgid "" -"💡 Running the `install-matrix-static-files` playbook tag (as done here) " -"is an optimized version of running [the full setup command](#run-" -"installation-command)." +msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)." msgstr "" #: ../../../docs/quick-start.md:178 -msgid "" -"After the command finishes, you can also check whether your server " -"federates with the Matrix network by using the [Federation " -"Tester](https://federationtester.matrix.org/) against your base domain " -"(`example.com`), not the `matrix.example.com` subdomain." +msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" #: ../../../docs/quick-start.md:180 @@ -532,9 +382,7 @@ msgid "Re-run the full setup command any time" msgstr "" #: ../../../docs/quick-start.md:182 -msgid "" -"If you think something is wrong with the server configuration, feel free " -"to re-run the setup command any time:" +msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:" msgstr "" #: ../../../docs/quick-start.md:188 @@ -542,32 +390,19 @@ msgid "Log in to your user account" msgstr "" #: ../../../docs/quick-start.md:190 -msgid "" -"Finally, let's make sure that you can log in to the created account with " -"the specified password." +msgid "Finally, let's make sure that you can log in to the created account with the specified password." msgstr "" #: ../../../docs/quick-start.md:192 -msgid "" -"You should be able to log in to it with your own [Element Web" -"](configuring-playbook-client-element-web.md) client which you have set " -"up at `element.example.com` by running the playbook. Open the URL " -"(`https://element.example.com`) in a web browser and enter your " -"credentials to log in." +msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in." msgstr "" #: ../../../docs/quick-start.md:194 -msgid "" -"**If you successfully logged in to your account, installing and " -"configuring is complete**🎉" +msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉" msgstr "" #: ../../../docs/quick-start.md:196 -msgid "" -"Come say Hi👋 in our support room - [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com). You might learn something or get to help someone " -"else new to Matrix hosting." +msgid "Come say Hi👋 in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" #: ../../../docs/quick-start.md:198 @@ -575,17 +410,11 @@ msgid "Things to do next" msgstr "" #: ../../../docs/quick-start.md:200 -msgid "" -"Once you get familiar with the playbook, you might probably want to set " -"up additional services such as a bridge on your server." +msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server." msgstr "" #: ../../../docs/quick-start.md:202 -msgid "" -"As this page intends to be a quick start guide which explains how to " -"start the core Matrix services, it does not cover a topic like how to set" -" them up. Take a look at the list of [things to do next](installing.md" -"#things-to-do-next) to learn more." +msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more." msgstr "" #: ../../../docs/quick-start.md:204 @@ -593,23 +422,13 @@ msgid "⚠️Keep the playbook and services up-to-date" msgstr "" #: ../../../docs/quick-start.md:206 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/quick-start.md:208 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/quick-start.md:210 -msgid "" -"For more information about upgrading or maintaining services with the " -"playbook, take at look at this page: [Upgrading the Matrix services" -"](maintenance-upgrading-services.md)" +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po index cf0b27df5..f8e0f8d37 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po @@ -26,9 +26,7 @@ msgid "Registering users" msgstr "" #: ../../../docs/registering-users.md:3 -msgid "" -"This documentation page tells you how to create user accounts on your " -"Matrix server." +msgid "This documentation page tells you how to create user accounts on your Matrix server." msgstr "" #: ../../../docs/registering-users.md:5 @@ -48,9 +46,7 @@ msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)" msgstr "" #: ../../../docs/registering-users.md:10 -msgid "" -"[Letting certain users register on your private server](#letting-certain-" -"users-register-on-your-private-server)" +msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)" msgstr "" #: ../../../docs/registering-users.md:11 @@ -58,9 +54,7 @@ msgid "[Enabling public user registration](#enabling-public-user-registration)" msgstr "" #: ../../../docs/registering-users.md:12 -msgid "" -"[Adding/Removing Administrator privileges to an existing user" -"](#addingremoving-administrator-privileges-to-an-existing-user)" +msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)" msgstr "" #: ../../../docs/registering-users.md:14 @@ -76,23 +70,15 @@ msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" #: ../../../docs/registering-users.md:18 -msgid "" -"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " -"(`@alice:example.com`)" +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/registering-users.md:19 -msgid "" -"Use `admin=yes` or `admin=no` depending on whether you wish to make the " -"user an administrator of the Matrix server" +msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server" msgstr "" #: ../../../docs/registering-users.md:21 -msgid "" -"After registering a user (using one of the methods below), **you can log " -"in with that user** via the [Element Web](configuring-playbook-client-" -"element-web.md) service that this playbook has installed for you at a URL" -" like this: `https://element.example.com/`." +msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`." msgstr "" #: ../../../docs/registering-users.md:23 @@ -100,11 +86,7 @@ msgid "Registering users via the Ansible playbook" msgstr "" #: ../../../docs/registering-users.md:25 -msgid "" -"It's best to register users via the Ansible playbook, because it works " -"regardless of homeserver implementation (Synapse, Dendrite, etc) or usage" -" of [Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md) (MAS)." +msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)." msgstr "" #: ../../../docs/registering-users.md:27 @@ -116,24 +98,11 @@ msgid "**or** by invoking `ansible-playbook` manually:" msgstr "" #: ../../../docs/registering-users.md:43 -msgid "" -"Feel free to register as many users (for friends, family, etc.) as you " -"want. Still, perhaps you should grant full administrative access to your " -"user account only (with `admin=yes`), and others should be created with " -"`admin=no`." +msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" #: ../../../docs/registering-users.md:45 -msgid "" -"⚠️ **Warning**: If you're registering users against Matrix Authentication" -" Service, do note that it [still insists](https://github.com/element-hq" -"/matrix-authentication-service/issues/1505) on having a verified email " -"address for each user. Upon a user's first login, they will be asked to " -"confirm their email address. This requires that email sending is " -"[configured](./configuring-playbook-email.md). You can also consult the " -"[Working around email deliverability issues](./configuring-playbook-" -"matrix-authentication-service.md#working-around-email-deliverability-" -"issues) section for more information." +msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." msgstr "" #: ../../../docs/registering-users.md:47 @@ -141,12 +110,7 @@ msgid "Registering users manually for Synapse" msgstr "" #: ../../../docs/registering-users.md:49 -msgid "" -"If you're using the [Synapse](configuring-playbook-synapse.md) homeserver" -" implementation (which is the default), you can register users via the " -"command-line after **SSH**-ing to your server (requires that [all " -"services have been started](installing.md#install-matrix-server-and-" -"services)):" +msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:57 @@ -154,11 +118,7 @@ msgid "Registering users manually for Dendrite" msgstr "" #: ../../../docs/registering-users.md:59 -msgid "" -"If you're using the [Dendrite](./configuring-playbook-dendrite.md) " -"homeserver implementation, you can register users via the command-line " -"after **SSH**-ing to your server (requires that [all services have been " -"started](installing.md#install-matrix-server-and-services)):" +msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:67 @@ -166,34 +126,15 @@ msgid "Registering users manually for Matrix Authentication Service" msgstr "" #: ../../../docs/registering-users.md:69 -msgid "" -"If you're using the [Matrix Authentication Service](./configuring-" -"playbook-matrix-authentication-service.md) and your existing homeserver " -"(most likely [Synapse](./configuring-playbook-synapse.md)) is delegating " -"authentication to it, you can register users via the command-line after " -"**SSH**-ing to your server (requires that [all services have been " -"started](installing.md#install-matrix-server-and-services)):" +msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:77 -msgid "" -"This `register-user` script actually invokes the `mas-cli manage " -"register-user` command under the hood. If you'd like more control over " -"the registration process, consider invoking the `mas-cli` command " -"directly:" +msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:" msgstr "" #: ../../../docs/registering-users.md:83 -msgid "" -"⚠️ **Warning**: Matrix Authentication Service [still " -"insists](https://github.com/element-hq/matrix-authentication-" -"service/issues/1505) on having a verified email address for each user. " -"Upon a user's first login, they will be asked to confirm their email " -"address. This requires that email sending is [configured](./configuring-" -"playbook-email.md). You can also consult the [Working around email " -"deliverability issues](./configuring-playbook-matrix-authentication-" -"service.md#working-around-email-deliverability-issues) section for more " -"information." +msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." msgstr "" #: ../../../docs/registering-users.md:85 @@ -201,18 +142,11 @@ msgid "Managing users via a Web UI" msgstr "" #: ../../../docs/registering-users.md:87 -msgid "" -"To manage users more easily (via a web user-interace), you can install " -"[Synapse Admin](configuring-playbook-synapse-admin.md)." +msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/registering-users.md:89 -msgid "" -"⚠️ **Warning**: If you're using [Matrix Authentication Service" -"](configuring-playbook-matrix-authentication-service.md), note that user " -"management via synapse-admin is not fully working yet. See the " -"[Expectations](configuring-playbook-matrix-authentication-" -"service.md#expectations) section for more information." +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information." msgstr "" #: ../../../docs/registering-users.md:91 @@ -220,12 +154,7 @@ msgid "Letting certain users register on your private server" msgstr "" #: ../../../docs/registering-users.md:93 -msgid "" -"If you'd rather **keep your server private** (public registration closed," -" as is the default), and **let certain people create accounts by " -"themselves** (instead of creating user accounts manually like this), " -"consider installing and making use of [matrix-registration](configuring-" -"playbook-matrix-registration.md)." +msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)." msgstr "" #: ../../../docs/registering-users.md:95 @@ -233,10 +162,7 @@ msgid "Enabling public user registration" msgstr "" #: ../../../docs/registering-users.md:97 -msgid "" -"To **open up user registration publicly** (usually **not recommended**), " -"add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/registering-users.md:99 @@ -248,31 +174,19 @@ msgid "For Dendrite:" msgstr "" #: ../../../docs/registering-users.md:111 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/registering-users.md:120 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/registering-users.md:122 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/registering-users.md:124 -msgid "" -"If you're opening up registrations publicly like this, you might also " -"wish to [configure CAPTCHA protection](configuring-captcha.md)." +msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)." msgstr "" #: ../../../docs/registering-users.md:126 @@ -284,9 +198,7 @@ msgid "Adding/Removing Administrator privileges to an existing user in Synapse" msgstr "" #: ../../../docs/registering-users.md:130 -msgid "" -"To change the admin privileges for a user in Synapse's local database, " -"you need to run an SQL query like this against the `synapse` database:" +msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:" msgstr "" #: ../../../docs/registering-users.md:136 @@ -302,16 +214,11 @@ msgid "`USER` and `example.com` pointing to a valid user on your server" msgstr "" #: ../../../docs/registering-users.md:141 -msgid "" -"If you're using the integrated Postgres server and not an [external " -"Postgres server](configuring-playbook-external-postgres.md), you can " -"launch a Postgres into the `synapse` database by:" +msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:" msgstr "" #: ../../../docs/registering-users.md:143 -msgid "" -"running `/matrix/postgres/bin/cli` - to launch " -"[`psql`](https://www.postgresql.org/docs/current/app-psql.html)" +msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)" msgstr "" #: ../../../docs/registering-users.md:144 @@ -323,28 +230,17 @@ msgid "You can then proceed to run the query above." msgstr "" #: ../../../docs/registering-users.md:148 -msgid "" -"**Note**: directly modifying the raw data of Synapse (or any other " -"software) could cause the software to break. You've been warned!" +msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!" msgstr "" #: ../../../docs/registering-users.md:150 -msgid "" -"Adding/Removing Administrator privileges to an existing user in Matrix " -"Authentication Service" +msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service" msgstr "" #: ../../../docs/registering-users.md:152 -msgid "" -"Promoting/demoting a user in Matrix Authentication Service cannot " -"currently (2024-10-19) be done via the [`mas-cli` Management tool" -"](./configuring-playbook-matrix-authentication-service.md#management)." +msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)." msgstr "" #: ../../../docs/registering-users.md:154 -msgid "" -"You can do it via the [MAS Admin API](https://element-hq.github.io" -"/matrix-authentication-service/api/index.html)'s `POST " -"/api/admin/v1/users/{id}/set-admin` endpoint." +msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/self-building.po b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po index 5c29bb3b1..89bf5c0f5 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/self-building.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po @@ -26,34 +26,19 @@ msgid "Self-building" msgstr "" #: ../../../docs/self-building.md:3 -msgid "" -"**Caution: self-building does not have to be used on its own. See the " -"[Alternative Architectures](alternative-architectures.md) page.**" +msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**" msgstr "" #: ../../../docs/self-building.md:5 -msgid "" -"The playbook supports self-building of various components, which don't " -"have a container image for your architecture (see the [container images " -"we use](container-images.md)). For `amd64`, self-building is not " -"required." +msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required." msgstr "" #: ../../../docs/self-building.md:7 -msgid "" -"For other architectures (e.g. `arm32`, `arm64`), ready-made container " -"images are used when available. If there's no ready-made image for a " -"specific component and said component supports self-building, an image " -"will be built on the host. Building images like this takes more time and " -"resources (some build tools need to get installed by the playbook to " -"assist building)." +msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)." msgstr "" #: ../../../docs/self-building.md:9 -msgid "" -"To make use of self-building, you don't need to do anything. If a " -"component has an image for the specified architecture, the playbook will " -"use it directly. If not, it will build the image on the server itself." +msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself." msgstr "" #: ../../../docs/self-building.md:11 @@ -61,9 +46,7 @@ msgid "Note that **not all components support self-building yet**." msgstr "" #: ../../../docs/self-building.md:13 -msgid "" -"Possibly outdated list of roles where self-building the Docker image is " -"currently possible:" +msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:" msgstr "" #: ../../../docs/self-building.md:14 @@ -187,15 +170,9 @@ msgid "`matrix-pantalaimon`" msgstr "" #: ../../../docs/self-building.md:45 -msgid "" -"Adding self-building support to other roles is welcome. Feel free to " -"contribute!" +msgid "Adding self-building support to other roles is welcome. Feel free to contribute!" msgstr "" #: ../../../docs/self-building.md:47 -msgid "" -"If you'd like **to force self-building** even if an image is available " -"for your architecture, look into the `matrix_*_self_build` variables " -"provided by individual roles." +msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles." msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po index 487996aaa..3215c013b 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po @@ -30,18 +30,11 @@ msgid "**Warnings**:" msgstr "" #: ../../../docs/uninstalling.md:5 -msgid "" -"If your server federates with others, make sure to **leave any federated " -"rooms before nuking your Matrix server's data**. Otherwise, the next time" -" you set up a Matrix server for this domain (regardless of the " -"installation method you use), you'll encounter trouble federating." +msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating." msgstr "" #: ../../../docs/uninstalling.md:7 -msgid "" -"If you have some trouble with your installation, you can just [re-run the" -" playbook](installing.md) and it will try to set things up again. " -"**Uninstalling and then installing anew rarely solves anything**." +msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**." msgstr "" #: ../../../docs/uninstalling.md:11 @@ -53,9 +46,7 @@ msgid "Installing places a `/matrix/bin/remove-all` script on the server." msgstr "" #: ../../../docs/uninstalling.md:15 -msgid "" -"You can run it to to have it uninstall things for you automatically (see " -"below). **Use with caution!**" +msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**" msgstr "" #: ../../../docs/uninstalling.md:17 @@ -63,37 +54,23 @@ msgid "Uninstalling manually" msgstr "" #: ../../../docs/uninstalling.md:19 -msgid "" -"If you prefer to uninstall manually, run these commands (most are meant " -"to be executed on the Matrix server itself):" +msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):" msgstr "" #: ../../../docs/uninstalling.md:21 -msgid "" -"ensure all Matrix services are stopped: `ansible-playbook -i " -"inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working " -"to run this command, you can run `systemctl stop 'matrix*'` manually on " -"the server)" +msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)" msgstr "" #: ../../../docs/uninstalling.md:23 -msgid "" -"delete the Matrix-related systemd `.service` and `.timer` files (`rm -f " -"/etc/systemd/system/matrix*.{service,timer}`) and reload systemd " -"(`systemctl daemon-reload`)" +msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)" msgstr "" #: ../../../docs/uninstalling.md:25 -msgid "" -"delete some cached Docker images (`docker system prune -a`) or just " -"delete them all (`docker rmi $(docker images -aq)`)" +msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)" msgstr "" #: ../../../docs/uninstalling.md:27 -msgid "" -"delete the Docker networks: `docker network rm matrix matrix-coturn` " -"(might have been deleted already if you ran the `docker system prune` " -"command)" +msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)" msgstr "" #: ../../../docs/uninstalling.md:29 @@ -103,4 +80,3 @@ msgstr "" #: ../../../docs/uninstalling.md:31 msgid "delete the `/matrix` directory (`rm -rf /matrix`)" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po index 48dbc56e5..7c381ab52 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po @@ -38,9 +38,7 @@ msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" #: ../../../docs/updating-users-passwords.md:7 -msgid "" -"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " -"(`@alice:example.com`)" +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/updating-users-passwords.md:9 @@ -48,9 +46,7 @@ msgid "You can reset a user's password via the Ansible playbook:" msgstr "" #: ../../../docs/updating-users-passwords.md:15 -msgid "" -"**You can then log in with that user** via Element Web that this playbook" -" has created for you at a URL like this: `https://element.example.com/`." +msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`." msgstr "" #: ../../../docs/updating-users-passwords.md:17 @@ -58,10 +54,7 @@ msgid "Option 2 (if you are using an external Postgres server):" msgstr "" #: ../../../docs/updating-users-passwords.md:19 -msgid "" -"You can manually generate the password hash by using the command-line " -"after **SSH**-ing to your server (requires that [all services have been " -"started](installing.md#finalize-the-installation):" +msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):" msgstr "" #: ../../../docs/updating-users-passwords.md:25 @@ -77,26 +70,15 @@ msgid "Option 3:" msgstr "" #: ../../../docs/updating-users-passwords.md:35 -msgid "" -"Use the Synapse User Admin API as described here: https://github.com" -"/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-" -"password" +msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password" msgstr "" #: ../../../docs/updating-users-passwords.md:37 -msgid "" -"This requires an [access token](obtaining-access-tokens.md) from a server" -" admin account. *This method will also log the user out of all of their " -"clients while the other options do not.*" +msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*" msgstr "" #: ../../../docs/updating-users-passwords.md:39 -msgid "" -"If you didn't make your account a server admin when you created it, you " -"can learn how to switch it now by reading about it in [Adding/Removing " -"Administrator privileges to an existing user in Synapse](registering-" -"users.md#addingremoving-administrator-privileges-to-an-existing-user-in-" -"synapse)." +msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)." msgstr "" #: ../../../docs/updating-users-passwords.md:41 @@ -104,8 +86,5 @@ msgid "Example:" msgstr "" #: ../../../docs/updating-users-passwords.md:43 -msgid "" -"To set @alice:example.com's password to `correct_horse_battery_staple` " -"you could use this curl command:" +msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:" msgstr "" - diff --git a/i18n/locales/bg/LC_MESSAGES/i18n/README.po b/i18n/locales/bg/LC_MESSAGES/i18n/README.po index c60d751ed..72a8111ae 100644 --- a/i18n/locales/bg/LC_MESSAGES/i18n/README.po +++ b/i18n/locales/bg/LC_MESSAGES/i18n/README.po @@ -22,9 +22,7 @@ msgid "Internationalization" msgstr "" #: ../../README.md:3 -msgid "" -"Translated documentation files are published and maintained in " -"[`translated/`](translated/) directory." +msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." msgstr "" #: ../../README.md:5 @@ -36,9 +34,7 @@ msgid "Markdown files found at the top level project directory" msgstr "" #: ../../README.md:8 -msgid "" -"Markdown files found in the [`docs`](../docs/) directory (this is where " -"the bulk of the documentation is)" +msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" msgstr "" #: ../../README.md:9 @@ -46,11 +42,7 @@ msgid "this current document in the `i18n` directory" msgstr "" #: ../../README.md:11 -msgid "" -"💡 For readers' sake, we only [publish translations in a new language" -"](#publish-translations-in-a-new-language) when the translation " -"progresses beyond a certain threshold (requiring that at least the " -"project README and core installation guides are translated)." +msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." msgstr "" #: ../../README.md:13 @@ -58,37 +50,23 @@ msgid "Organization of this `i18n` directory is as follows:" msgstr "" #: ../../README.md:15 -msgid "" -"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we " -"publish translations for (in the [translated/](translated/) directory)" +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" msgstr "" #: ../../README.md:16 -msgid "" -"[.gitignore](.gitignore): a list of files and directories to ignore in " -"the `i18n` directory. We intentionaly ignore translated results " -"(`translated/` 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." +msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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:17 -msgid "" -"[justfile](justfile): a list of recipes for " -"[just](https://github.com/casey/just) command runner" +msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" msgstr "" #: ../../README.md:18 -msgid "" -"[requirements.txt](requirements.txt): a list of Python packages required " -"to work with translations" +msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" msgstr "" #: ../../README.md:19 -msgid "" -"[translation-templates/](translation-templates/): a list of English " -"translation templates - strings extracted from Markdown files" +msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" msgstr "" #: ../../README.md:20 @@ -96,10 +74,7 @@ msgid "[locales/](locales/): localization files for languages" msgstr "" #: ../../README.md:21 -msgid "" -"[translated/](translated/): translated documents for published languages " -"(see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations" -" in a new language](#publish-translations-in-a-new-language))" +msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" msgstr "" #: ../../README.md:23 @@ -107,24 +82,15 @@ msgid "Guide for translators" msgstr "" #: ../../README.md:25 -msgid "" -"This project uses [Sphinx](https://www.sphinx-doc.org/) to generate " -"translated documents." +msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." msgstr "" #: ../../README.md:27 -msgid "" -"For details about using Sphinx for translation, refer [this official " -"document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) " -"as well." +msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." msgstr "" #: ../../README.md:29 -msgid "" -"For now, translations are handled manually by editing `.po` files in the " -"`locales/` directory. In the future, we plan on integrating " -"with [Weblate](https://weblate.org/) to allow for translating from a web " -"interface." +msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." msgstr "" #: ../../README.md:31 @@ -132,20 +98,11 @@ msgid "(Recommended) Using the uv package manager and just command runner" msgstr "" #: ../../README.md:33 -msgid "" -"If you have the [uv](https://docs.astral.sh/uv/) package manager and " -"[just](https://github.com/casey/just) command runner installed, you can " -"use our [justfile](justfile) recipes to easily manage translation files " -"and build translated documents." +msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." msgstr "" #: ../../README.md:35 -msgid "" -"The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create" -" [a Python virtual " -"environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` " -"directory and install the required Python packages (as per " -"[requirements.txt](requirements.txt)) to it." +msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." msgstr "" #: ../../README.md:37 ../../README.md:64 @@ -153,9 +110,7 @@ msgid "Preparation" msgstr "" #: ../../README.md:39 -msgid "" -"Make sure you have the [uv](https://docs.astral.sh/uv/) package manager " -"and [just](https://github.com/casey/just) command runner installed." +msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." msgstr "" #: ../../README.md:41 ../../README.md:72 @@ -163,17 +118,11 @@ msgid "Translation" msgstr "" #: ../../README.md:43 ../../README.md:74 -msgid "" -"Recommended flow when working on a new language (replace `` " -"with the language code, e.g. `bg`):" +msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" msgstr "" #: ../../README.md:45 -msgid "" -"Update the locale files for your language: `just sync-for-language " -"` (internally, this automatically runs `just extract-" -"translation-templates` to make sure the translation templates are up-to-" -"date)" +msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" msgstr "" #: ../../README.md:47 ../../README.md:80 @@ -193,10 +142,7 @@ msgid "Commit your changes done to the `locales/` directory" msgstr "" #: ../../README.md:55 ../../README.md:88 -msgid "" -"If you have progressed with the translation beyond a certain threshold, " -"consider [Publishing translations in a new language](#publish-" -"translations-in-a-new-language)" +msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" msgstr "" #: ../../README.md:57 @@ -204,22 +150,15 @@ msgid "Using any other package manager and manual scripts" msgstr "" #: ../../README.md:59 -msgid "" -"If you cannot use [uv](https://docs.astral.sh/uv/) and/or " -"[just](https://github.com/casey/just), you can:" +msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" msgstr "" #: ../../README.md:61 -msgid "" -"manage Python packages in another way " -"([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-" -"poetry.org/), etc.)" +msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" msgstr "" #: ../../README.md:62 -msgid "" -"manage translation strings and build translated documents manually by " -"invoking scripts from the [bin](bin/) directory" +msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" msgstr "" #: ../../README.md:66 @@ -227,9 +166,7 @@ msgid "virtualenv and pip" msgstr "" #: ../../README.md:68 -msgid "" -"Create a Python virtual environment in the `.venv` directory: `virtualenv" -" .venv`" +msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" msgstr "" #: ../../README.md:69 @@ -237,22 +174,15 @@ msgid "Activate the virtual environment: `source .venv/bin/activate`" msgstr "" #: ../../README.md:70 -msgid "" -"Install the required Python packages using " -"[pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" +msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" msgstr "" #: ../../README.md:76 -msgid "" -"Ensure the English translation templates ([translation-templates" -"/](translation-templates/)) are extracted: `./bin/extract-translation-" -"templates.sh`" +msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" msgstr "" #: ../../README.md:78 -msgid "" -"Update the locale files for your language: `./bin/sync-translation-" -"templates-to-locales.sh `" +msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" msgstr "" #: ../../README.md:82 @@ -264,197 +194,17 @@ msgid "Publish translations in a new language" msgstr "" #: ../../README.md:92 -msgid "" -"To publish prebuilt documents translated in a new language to the " -"`translated/` directory:" +msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" msgstr "" #: ../../README.md:94 -msgid "" -"add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) " -"file" +msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" msgstr "" #: ../../README.md:95 -msgid "" -"whitelist its `translated/` directory by adding a " -"`!translated/` rule to the [.gitignore](.gitignore) file" +msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" msgstr "" #: ../../README.md:97 -msgid "" -"💡 Leave a trailing new line at the end of the " -"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." +msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." msgstr "" - -#~ msgid "" -#~ "Currently, we manage translaion of " -#~ "markdown files on the top level " -#~ "directory and inside [`docs`](../docs/), and" -#~ " this file (`README.md`) only." -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ For readers' sake, we set a " -#~ "minimum condition for publishing documents " -#~ "translated in your language: translating " -#~ "basic articles such as READMEs, " -#~ "installation guides ([Quick start](quick-" -#~ "start.md) and the full installation " -#~ "guide which starts at the " -#~ "[Prerequisites](prerequisites.md)), etc. If you " -#~ "think we have missed progress of " -#~ "translation in your language, please " -#~ "ping us at the Matrix room." -#~ msgstr "" - -#~ msgid "Translation guide" -#~ msgstr "" - -#~ msgid "" -#~ "If you are interested in translating " -#~ "this project, please check out our " -#~ "[Weblate project](https://example.com)." -#~ msgstr "" - -#~ msgid "" -#~ "If your language is not yet " -#~ "listed, please express your wishes to" -#~ " start translating it in our [Matrix" -#~ " room](https://matrix.to/#/#matrix-docker-ansible-" -#~ "deploy:devture.com). If anyone else is " -#~ "found to be working on your " -#~ "language, please co-ordinate if needed." -#~ msgstr "" - -#~ msgid "" -#~ "Currently, we manage translaion of " -#~ "markdown files on the top level " -#~ "directory and inside [`docs`](../docs/), and" -#~ " README files only." -#~ msgstr "" - -#~ msgid "" -#~ "Translated files are published and " -#~ "maintained in [`markdown`](../markdown/) directory." -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ For readers' sake, we set a " -#~ "minimum percentage of completion (70%) " -#~ "for publishing documents translated in " -#~ "your language. If you think we " -#~ "have missed progress of translation in" -#~ " your language, please ping us in " -#~ "the Matrix room." -#~ msgstr "" - -#~ msgid "Translation development guide" -#~ msgstr "" - -#~ msgid "Install packages" -#~ msgstr "" - -#~ msgid "" -#~ "To manage files for translation and " -#~ "build translated documents, you need to" -#~ " install packages at first. You can" -#~ " install them with " -#~ "[pip](https://pip.pypa.io/en/stable/)." -#~ msgstr "" - -#~ msgid "" -#~ "After installing pip and activating the" -#~ " virtual environment, run the command " -#~ "below on this directory:" -#~ msgstr "" - -#~ msgid "Update PO files" -#~ msgstr "" - -#~ msgid "" -#~ "If a document is updated, it is" -#~ " necessary to generate updated `.pot` " -#~ "(catalog templates) files and to apply" -#~ " differences to translated `.po` (message" -#~ " catalogs) files." -#~ msgstr "" - -#~ msgid "To do so, run these commands:" -#~ msgstr "" - -#~ msgid "" -#~ "To generate `.po` files for a new" -#~ " language, e.g. Bulgarian, run the " -#~ "command below:" -#~ msgstr "" - -#~ msgid "" -#~ "After the original documents have " -#~ "changed, run [i18n_update.sh](i18n_update.sh) to " -#~ "update `.po` files in all languages " -#~ "specified on [`LANG`](LANG) file:" -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ Unless your language code is " -#~ "added to the `LANG` file, running " -#~ "the script does not generate `.po` " -#~ "files in your language in `locales` " -#~ "directory." -#~ msgstr "" - -#~ msgid "Build" -#~ msgstr "" - -#~ msgid "To build the documentation in English, run the command below:" -#~ msgstr "" - -#~ msgid "It generates Markdown files in `_build/markdown/`." -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ As the original documents are " -#~ "also Markdown files, the generated files" -#~ " in English are identical to the " -#~ "original ones." -#~ msgstr "" - -#~ msgid "To build documents in another language, e.g. Bulgarian, run:" -#~ msgstr "" - -#~ msgid "" -#~ "Running [i18n_build.sh](i18n_build.sh) builds " -#~ "Markdown files in all languages " -#~ "specified on `LANG` file into `markdown`" -#~ " directory:" -#~ msgstr "" - -#~ msgid "Publish documents in a new language" -#~ msgstr "" - -#~ msgid "" -#~ "To publish documents translated in a " -#~ "new language on `markdown` directory, " -#~ "add its language code to `LANG` " -#~ "file. Then, run `i18n_update.sh` and " -#~ "`i18n_build.sh`. After that, you would " -#~ "need to push the documents to the" -#~ " repository." -#~ msgstr "" - -#~ msgid "💡 Leave an empty line at the end of the `LANG` file." -#~ msgstr "" - -#~ msgid "Using the uv package manager and just command runner" -#~ msgstr "" - -#~ msgid "" -#~ "Update the locale files for your " -#~ "language: `just sync-language ` " -#~ "(internally, this automatically runs `just " -#~ "extract-translation-templates` to make " -#~ "sure the translation templates are " -#~ "up-to-date)" -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po index 76931a0b2..f0f6914ef 100644 --- a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po +++ b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po @@ -25,62 +25,35 @@ msgid "2024-11-26" msgstr "" #: ../../../CHANGELOG.md:3 -msgid "" -"(Backward Compatibility Break) Synapse now defaults to enabling " -"authenticated media" +msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media" msgstr "" #: ../../../CHANGELOG.md:5 -msgid "" -"**TLDR**: with this update, your Synapse homeserver will start requiring " -"authentication for newly-uploaded media files. While the majority of the " -"ecosystem (clients, bots, etc.) should support this, certain software may" -" lack support for it (and you may wish to turn it off, if it's causing " -"issues)." +msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)." msgstr "" #: ../../../CHANGELOG.md:7 -msgid "" -"The default configuration for the Synapse homeserver now [enforces " -"Authenticated media by default](https://element-" -"hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-" -"enforced-by-default)." +msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)." msgstr "" #: ../../../CHANGELOG.md:9 -msgid "" -"Servers like `matrix.org` have already [sunset unauthenticated " -"media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-" -"media/) months ago." +msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago." msgstr "" #: ../../../CHANGELOG.md:11 -msgid "" -"Now that **various clients, bots, bridges and extra services have caught " -"up with authenticated media support**, Synapse developers seem confident " -"that it's time to enable authenticated media by default." +msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default." msgstr "" #: ../../../CHANGELOG.md:13 -msgid "" -"We're changing the playbook configuration for authenticated media to keep" -" up with upstream defaults changing." +msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing." msgstr "" #: ../../../CHANGELOG.md:15 -msgid "" -"Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not " -"support authenticated media. Other software may be similarly affected. If" -" you experience issues with some Matrix-related software, you may wish to" -" disable authenticated media and contact the software maintainers to let " -"them know." +msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know." msgstr "" #: ../../../CHANGELOG.md:17 -msgid "" -"You can disable authenticated media at any time by setting " -"`matrix_synapse_enable_authenticated_media: false` in your `vars.yml` " -"configuration file and re-running the playbook." +msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook." msgstr "" #: ../../../CHANGELOG.md:20 @@ -88,89 +61,47 @@ msgid "2024-11-23" msgstr "" #: ../../../CHANGELOG.md:22 -msgid "" -"(Backward Compatibility Break) The playbook now defaults to Valkey, " -"instead of KeyDB" +msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB" msgstr "" #: ../../../CHANGELOG.md:24 -msgid "" -"**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for " -"you before, it will now replace it with [Valkey](https://valkey.io/) (a " -"drop-in alternative). We [previously switched from Redis to KeyDB" -"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" -"instead-of-redis), but Valkey is a better alternative, so we're switching" -" again." +msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again." msgstr "" #: ../../../CHANGELOG.md:26 -msgid "" -"The playbook used to install Redis or KeyDB if services have a need for a" -" Redis-compatible implementation ([enabling worker support for " -"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" -"workers), [enabling Hookshot encryption](docs/configuring-playbook-" -"bridge-hookshot.md#end-to-bridge-encryption), etc.)." +msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)." msgstr "" #: ../../../CHANGELOG.md:28 -msgid "" -"Earlier this year, we switched from Redis to KeyDB - see [(Backward " -"Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" -"](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-" -"instead-of-redis)." +msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)." msgstr "" #: ../../../CHANGELOG.md:30 -msgid "" -"Because Valkey seems to be a better successor to Redis (than KeyDB) and " -"likely doesn't suffer from [issues like this " -"one](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3544), we now replace KeyDB with Valkey." +msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey." msgstr "" #: ../../../CHANGELOG.md:32 -msgid "" -"Valkey (like KeyDB and Redis in the past) is an implicitly enabled " -"dependency - you don't need custom configuration in `vars.yml` to enable " -"it." +msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it." msgstr "" #: ../../../CHANGELOG.md:34 -msgid "" -"Next time your run the playbook (via the `setup-all` tag), **KeyDB will " -"be automatically uninstalled and replaced with Valkey**. Some Synapse " -"downtime may occur while the switch happens." +msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens." msgstr "" #: ../../../CHANGELOG.md:36 -msgid "" -"Users on `arm32` should be aware that there's **neither a prebuilt " -"`arm32` container image for Valkey**, nor the Valkey role supports self-" -"building yet. Users on this architecture likely don't run Synapse with " -"workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). " -"If Redis is necessary in an `arm32` deployment, disabling Valkey and " -"making the playbook fall back to Redis is possible (see below)." +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)." msgstr "" #: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378 -msgid "" -"**The playbook still supports Redis** and you can keep using Redis (for " -"now) if you'd like, by adding this additional configuration to your " -"`vars.yml` file:" +msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:49 -msgid "" -"**The playbook still supports KeyDB** and you can keep using KeyDB (for " -"now) if you'd like, by adding this additional configuration to your " -"`vars.yml` file:" +msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:59 -msgid "" -"At some point in time in the future, we'll remove both KeyDB and Redis " -"from the playbook, so we recommend that you migrate to Valkey earlier " -"anyway." +msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway." msgstr "" #: ../../../CHANGELOG.md:62 @@ -182,79 +113,35 @@ msgid "HTTP-compression support for Traefik-based setups" msgstr "" #: ../../../CHANGELOG.md:66 -msgid "" -"The playbook now **automatically enables HTTP-compression support** for " -"major services powered by the playbook, like [Cinny](./docs/configuring-" -"playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-" -"client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-" -"hydrogen.md), as well as for Matrix Client-Server and Federation APIs " -"(`matrix.example.com`)." +msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)." msgstr "" #: ../../../CHANGELOG.md:68 -msgid "" -"Other services installed by the playbook are currently not compression-" -"enabled, but may become so over time. This change is rolled out on a per-" -"service basis (as opposed to doing it globally, at the Traefik entrypoint" -" level) to allow certain services or route endpoints which do not behave " -"well when compressed (e.g. [issue 3749](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/issues/3749)) to be excluded from " -"compression." +msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression." msgstr "" #: ../../../CHANGELOG.md:70 -msgid "" -"A long time ago, various services were operating with `gzip`-compression " -"enabled at the nginx level. Since the switch to Traefik (see [Goodbye, " -"`matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md" -"#goodbye-matrix-nginx-proxy-)), all services (with the exception of " -"Matrix APIs for Synapse worker-enabled setups which are powered by " -"`nginx` via `synapse-reverse-proxy-companion`) have been operating " -"without HTTP-compression support." +msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support." msgstr "" #: ../../../CHANGELOG.md:72 -msgid "" -"HTTP-compression is now done via Traefik's " -"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " -"middleware. We use the default configuration for this middleware, which " -"enables `zstd`, `br` and `gzip` support (in this order). This " -"middleware's configuration can be configured via variables in the Traefik" -" role (see " -"`traefik_config_http_middlewares_compression_middleware_options`)." +msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)." msgstr "" #: ../../../CHANGELOG.md:74 -msgid "" -"If you're using your own Traefik reverse-proxy server ([Traefik managed " -"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" -"you)) instead of the playbook's integrated Traefik service, you can " -"benefit from the same by:" +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:" msgstr "" #: ../../../CHANGELOG.md:76 -msgid "" -"defining a " -"[compress](https://doc.traefik.io/traefik/middlewares/http/compress/) " -"middleware (via the " -"[file](https://doc.traefik.io/traefik/providers/file/) or " -"[Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" +msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)" msgstr "" #: ../../../CHANGELOG.md:77 -msgid "" -"setting " -"`matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to" -" `true`" +msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`" msgstr "" #: ../../../CHANGELOG.md:78 -msgid "" -"specifying the middleware's name in " -"`matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g." -" `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-" -"compression-middleware@file`)" +msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)" msgstr "" #: ../../../CHANGELOG.md:80 @@ -262,37 +149,19 @@ msgid "Timeout adjustments for Traefik-based setups" msgstr "" #: ../../../CHANGELOG.md:82 -msgid "" -"The playbook now supports configuring various " -"[transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts)" -" timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the " -"`web`, `web-secure` and `matrix-federation` entrypoints." +msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints." msgstr "" #: ../../../CHANGELOG.md:84 -msgid "" -"If you're using your own Traefik reverse-proxy server ([Traefik managed " -"by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-" -"you)) instead of the playbook's integrated Traefik service, you may wish " -"to do similar configuration changes to your setup manually." +msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually." msgstr "" #: ../../../CHANGELOG.md:86 -msgid "" -"The most interesting of these is the `readTimeout` configuration value " -"(the maximum duration for reading the entire request, including the " -"body), which used to default to `60s`. For large and slowly progressing " -"file uploads, `60s` would often not be enough for the transfer to finish " -"and uploads would end up being interrupted. The playbook now raises the " -"`readTimeout` value to 5 minutes (`300s`) to improve this use-case." +msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case." msgstr "" #: ../../../CHANGELOG.md:88 -msgid "" -"The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` " -"variables (for the `web` entrypoint) cascade to affecting the timeout " -"values for the `web-secure` and `matrix-federation` entrypoints, so you " -"can easily adjust all timeout values using them." +msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them." msgstr "" #: ../../../CHANGELOG.md:90 @@ -300,13 +169,7 @@ msgid "Example of the default timeout values used by the playbook:" msgstr "" #: ../../../CHANGELOG.md:101 -msgid "" -"Alternatively, you may adjust the timeout values for specific entrypoints" -" (like `web-secure` and `matrix-federation`) using dedicated variables " -"(like " -"`traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout`" -" and " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." +msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)." msgstr "" #: ../../../CHANGELOG.md:104 @@ -314,39 +177,19 @@ msgid "2024-11-08" msgstr "" #: ../../../CHANGELOG.md:106 -msgid "" -"Support for synapse-admin auto-configuration via /.well-" -"known/matrix/client" +msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client" msgstr "" #: ../../../CHANGELOG.md:108 -msgid "" -"You can administrate your Synapse-powered homeserver using synapse-admin " -"hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the " -"synapse-admin instance would still auto-configure itself correctly for " -"your server by [reading its `/.well-known/matrix/client` " -"file](https://github.com/etkecc/synapse-admin/pull/126)." +msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)." msgstr "" #: ../../../CHANGELOG.md:110 -msgid "" -"The playbook now configures the `/.well-known/matrix/client` file for " -"this by default, injecting into it a `cc.etke.synapse-admin` section that" -" contains the full synapse-admin configuration. This is done even if you " -"don't enable the synapse-admin service in your configuration. The reason " -"for always doing it is to allow users to skip the (small) overhead of " -"self-hosting the non-core synapse-admin service, yet still be able to use" -" it from elsewhere when needed." +msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed." msgstr "" #: ../../../CHANGELOG.md:112 -msgid "" -"If you don't ever plan on using synapse-admin from other servers (besides" -" your own due to [self-hosting synapse-admin](./docs/configuring-" -"playbook-synapse-admin.md)), you **can disable this** `/.well-" -"known/matrix/client` configuration via " -"`matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled:" -" false`" +msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`" msgstr "" #: ../../../CHANGELOG.md:115 @@ -358,11 +201,7 @@ msgid "(BC Break) Postmoogle's variable names need adjustments" msgstr "" #: ../../../CHANGELOG.md:119 -msgid "" -"Due to the recategorization of [Postmoogle](./docs/configuring-playbook-" -"bridge-postmoogle.md) from the bot to the bridge, its variables were " -"renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to " -"adjust your `vars.yml` configuration accordingly." +msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly." msgstr "" #: ../../../CHANGELOG.md:121 @@ -374,38 +213,19 @@ msgid "Support for Matrix Authentication Service" msgstr "" #: ../../../CHANGELOG.md:125 -msgid "" -"The playbook now supports installing and configuring [Matrix " -"Authentication Service](./docs/configuring-playbook-matrix-" -"authentication-service.md) (MAS)." +msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)." msgstr "" #: ../../../CHANGELOG.md:127 -msgid "" -"Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the " -"[Element](https://element.io/) / [Matrix Authentication " -"Service](https://github.com/element-hq/matrix-authentication-service) " -"team for answering our numerous questions about MAS." +msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS." msgstr "" #: ../../../CHANGELOG.md:129 -msgid "" -"This is an **experimental service** and there are **still certain issues " -"with it** (see [Expectations](./docs/configuring-playbook-matrix-" -"authentication-service.md#expectations)). Matrix server administrators " -"should only consider switching if they identify with one or more [reasons" -" to use Matrix Authentication Service](./docs/configuring-playbook-" -"matrix-authentication-service.md#reasons-to-use-matrix-authentication-" -"service). As MAS adoption improves and more services are adjusted to " -"support it, we expect that using MAS will become the norm." +msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm." msgstr "" #: ../../../CHANGELOG.md:131 -msgid "" -"Our [Setting up Matrix Authentication Service](./docs/configuring-" -"playbook-matrix-authentication-service.md) documentation page has more " -"details about this new service, what you might expect from the switch and" -" how you can migrate your existing (Synapse) homeserver setup to MAS." +msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS." msgstr "" #: ../../../CHANGELOG.md:134 @@ -413,23 +233,15 @@ msgid "2024-09-27" msgstr "" #: ../../../CHANGELOG.md:136 -msgid "" -"(BC Break) Postgres & Traefik roles have been relocated and variable " -"names need adjustments" +msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments" msgstr "" #: ../../../CHANGELOG.md:138 -msgid "" -"Various roles have been relocated from the " -"[devture](https://github.com/devture) organization to the [mother-of-all-" -"self-hosting](https://github.com/mother-of-all-self-hosting) " -"organization." +msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" #: ../../../CHANGELOG.md:140 -msgid "" -"Along with the relocation, the `devture_` prefix was dropped from their " -"variable names, so you need to adjust your `vars.yml` configuration." +msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:142 @@ -445,9 +257,7 @@ msgid "`devture_traefik_` -> `traefik_`" msgstr "" #: ../../../CHANGELOG.md:147 -msgid "" -"As always, the playbook would let you know about this and point out any " -"variables you may have missed." +msgid "As always, the playbook would let you know about this and point out any variables you may have missed." msgstr "" #: ../../../CHANGELOG.md:150 @@ -459,36 +269,19 @@ msgid "Support for baibot" msgstr "" #: ../../../CHANGELOG.md:154 -msgid "" -"The playbook now supports installing [baibot](./docs/configuring-" -"playbook-bot-baibot.md) (pronounced bye-bot) - a " -"[Matrix](https://matrix.org/) bot developed by " -"[etke.cc](https://etke.cc/) that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you. 🤖" +msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" msgstr "" #: ../../../CHANGELOG.md:156 -msgid "" -"It supports [OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other" -" [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../CHANGELOG.md:158 -msgid "" -"It's designed as a more private and [✨ " -"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" -"file#-features) alternative to the now-unmaintained [matrix-chatgpt-" -"bot](./docs/configuring-playbook-bot-chatgpt.md)." +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)." msgstr "" #: ../../../CHANGELOG.md:160 -msgid "" -"To get started, see the [Setting up baibot](./docs/configuring-playbook-" -"bot-baibot.md) documentation page." +msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:162 @@ -496,39 +289,19 @@ msgid "Switching synapse-admin to etke.cc's fork" msgstr "" #: ../../../CHANGELOG.md:164 -msgid "" -"The playbook now installs [etke.cc](https://etke.cc/)'s " -"[fork](https://github.com/etkecc/synapse-admin) of [synapse-" -"admin](https://github.com/Awesome-Technologies/synapse-admin) (originally" -" developed by [Awesome-Technologies](https://github.com/Awesome-" -"Technologies)). This fork is a drop-in replacement for the original " -"software." +msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software." msgstr "" #: ../../../CHANGELOG.md:166 -msgid "" -"The creation of the fork has been provoked by users frequently " -"encountering issues with the original synapse-admin software, such as " -"unintentionally deleting their one-and-only admin user account (fixed " -"[here](https://github.com/etkecc/synapse-admin/pull/1) and also " -"contributed upstream [here](https://github.com/Awesome-Technologies" -"/synapse-admin/pull/608) - to no avail for now). Since its inception, [a " -"bunch of other quality-of-life improvements](https://github.com/etkecc" -"/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." +msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork." msgstr "" #: ../../../CHANGELOG.md:168 -msgid "" -"If upstream synapse-admin picks up the pace and improves, the etke.cc " -"fork may disappear and the playbook may switch to the original software " -"again. Until that time comes, we believe that etke.cc's fork is the " -"better software to use right now." +msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now." msgstr "" #: ../../../CHANGELOG.md:170 -msgid "" -"If you'd like to switch back to the original synapse-admin software, you " -"can do so by adding the following configuration to your `vars.yml` file:" +msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:183 @@ -540,63 +313,31 @@ msgid "New appservice-double-puppet service for better double-puppeting" msgstr "" #: ../../../CHANGELOG.md:187 -msgid "" -"Mautrix bridges are undergoing large changes as announced in the [August " -"2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) " -"blog post." +msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post." msgstr "" #: ../../../CHANGELOG.md:189 -msgid "" -"The playbook has already upgraded to the rewritten mautrix-slack " -"([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and " -"mautrix-signal " -"([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) " -"bridges." +msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges." msgstr "" #: ../../../CHANGELOG.md:191 -msgid "" -"The newly rewritten bridges do not support double-puppeting via [Shared " -"Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, " -"which has prompted us to switch to the new & better [appservice " -"method](https://docs.mau.fi/bridges/general/double-puppeting.html" -"#appservice-method-new) for double-puppeting. The playbook automates this" -" double-puppeting setup for you if you enable the new [Appservice Double " -"Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." +msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service." msgstr "" #: ../../../CHANGELOG.md:193 -msgid "" -"All non-deprecated mautrix bridges in the playbook have been reworked to " -"support double-puppeting via an Appservice. Most bridges still support " -"double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-" -"shared-secret-auth.md), so the playbook supports it too. If only Shared " -"Secret Auth is enabled, double-puppeting will be configured using that " -"method (for the bridges that support it). That said, **Shared Secret Auth" -" double-puppeting is being phased out and we recommend replacing it with " -"the new Appservice method**." +msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**." msgstr "" #: ../../../CHANGELOG.md:195 -msgid "" -"We recommend **enabling double-puppeting via the new Appservice method** " -"by adding the following configuration to your `vars.yml` file:" +msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:201 -msgid "" -"You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-" -"shared-secret-auth.md) enabled. Non-mautrix bridges and other services " -"(e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) " -"may still require it." +msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it." msgstr "" #: ../../../CHANGELOG.md:203 -msgid "" -"When both double-puppeting methods are enabled, the playbook will " -"automatically choose the new and better Appservice method for bridges " -"that support it." +msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it." msgstr "" #: ../../../CHANGELOG.md:206 @@ -608,39 +349,19 @@ msgid "matrix-media-repo now configured for Authenticated Media" msgstr "" #: ../../../CHANGELOG.md:210 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), our matrix-media-repo implementation now " -"automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-" -"repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per " -"[MSC3916](https://github.com/matrix-org/matrix-spec-" -"proposals/pull/3916))." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))." msgstr "" #: ../../../CHANGELOG.md:212 -msgid "" -"If you had never heard of Authenticated Media before, the [Sunsetting " -"unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-" -"unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a" -" good introduction." +msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction." msgstr "" #: ../../../CHANGELOG.md:214 -msgid "" -"This feature is enabled for matrix-media-repo installations by default " -"and will append an additional (matrix-media-repo-generated signing key) " -"to your homeserver's (Synapse or Dendrite) signing key. See the [Signing " -"keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and " -"[Key backup and revoking](./docs/configuring-playbook-matrix-media-" -"repo.md#key-backup-and-revoking) sections of the matrix-media-repo " -"documentation for more details." +msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details." msgstr "" #: ../../../CHANGELOG.md:216 -msgid "" -"If you'd like to avoid this new feature, you can disable it by setting " -"`matrix_media_repo_generate_signing_key: false` in your `vars.yml` " -"configuration file." +msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:219 @@ -652,24 +373,15 @@ msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" msgstr "" #: ../../../CHANGELOG.md:223 -msgid "" -"The playbook now installs [matrix-corporal](https://github.com/devture" -"/matrix-corporal) v3.0.0, which brings support for **power-level " -"management** (thanks to [this PR](https://github.com/devture/matrix-" -"corporal/pull/32))." +msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))." msgstr "" #: ../../../CHANGELOG.md:225 -msgid "" -"This upgrade necessitates configuration policy changes as described in " -"[matrix-corporal's changelog entry](https://github.com/devture/matrix-" -"corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." +msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)." msgstr "" #: ../../../CHANGELOG.md:227 -msgid "" -"If you'd like to remain on the old (v2) version of matrix-corporal, you " -"can do so by adding the following configuration to your `vars.yml` file:" +msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:233 @@ -681,21 +393,11 @@ msgid "synapse-usage-exporter support" msgstr "" #: ../../../CHANGELOG.md:237 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook can now set up [synapse-usage-" -"exporter](https://github.com/loelkes/synapse-usage-exporter) - a small " -"[Flask](https://flask.palletsprojects.com)-based webservice which can " -"capture usage statistics from Synapse (via HTTP `PUT`) and then make them" -" available for Prometheus to scrape." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape." msgstr "" #: ../../../CHANGELOG.md:239 -msgid "" -"To learn more see our [Enabling synapse-usage-exporter for Synapse usage " -"statistics](docs/configuring-playbook-synapse-usage-exporter.md) " -"documentation page." +msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:242 @@ -707,19 +409,11 @@ msgid "matrix-alertmanager-receiver support" msgstr "" #: ../../../CHANGELOG.md:246 -msgid "" -"For those wishing to more easily integrate " -"[Prometheus](https://prometheus.io/)' alerting service " -"([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/))" -" with Matrix, the playbook can now set up [matrix-alertmanager-" -"receiver](https://github.com/metio/matrix-alertmanager-receiver)." +msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)." msgstr "" #: ../../../CHANGELOG.md:248 -msgid "" -"See [Setting up Prometheus Alertmanager integration via matrix-" -"alertmanager-receiver](./docs/configuring-playbook-alertmanager-" -"receiver.md) for more details." +msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details." msgstr "" #: ../../../CHANGELOG.md:250 @@ -727,15 +421,7 @@ msgid "Traefik v3 and HTTP/3 are here now" msgstr "" #: ../../../CHANGELOG.md:252 -msgid "" -"**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to " -"the playbook. Mostly everything else worked out of the box. Most people " -"will not have to do any tweaks to their configuration. In addition, " -"[HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-" -"enabled for the `web-secure` (port 443) and `matrix-federation` (port " -"`8448`) entrypoints. If you have a firewall in front of your server and " -"you wish to benefit from `HTTP3`, you will need to open the `443` and " -"`8448` UDP ports in it." +msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it." msgstr "" #: ../../../CHANGELOG.md:254 @@ -743,31 +429,15 @@ msgid "Traefik v3" msgstr "" #: ../../../CHANGELOG.md:256 -msgid "" -"The reverse-proxy that the playbook uses by default (Traefik) has " -"recently been upgraded to v3 (see [this blog " -"post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn " -"about its new features). Version 3 includes some small breaking " -"configuration changes requiring a " -"[migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)." msgstr "" #: ../../../CHANGELOG.md:258 -msgid "" -"We have **updated the playbook to Traefik v3** (make sure to run `just " -"roles` / `make roles` to get it)." +msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)." msgstr "" #: ../../../CHANGELOG.md:260 -msgid "" -"There were **only minor playbook changes required** to adapt to Traefik " -"v3, and only to the Ansible role for [matrix-media-repo](./docs" -"/configuring-playbook-matrix-media-repo.md) where we changed a few " -"[`PathPrefix` instances to " -"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" -"pathprefix-and-pathregexp), because these instances were using a regular " -"expression instead of a fixed path. For fixed-path values, `PathPrefix` " -"is still the preferred matcher function to use." +msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use." msgstr "" #: ../../../CHANGELOG.md:262 @@ -775,36 +445,15 @@ msgid "**Most people using the playbook should not have to do any changes**." msgstr "" #: ../../../CHANGELOG.md:264 -msgid "" -"If you're using the playbook's Traefik instance to reverse-proxy to some " -"other services of your own (not managed by the playbook), you may wish to" -" review their Traefik labels and make sure they're in line with the " -"[Traefik v2 to v3 migration " -"guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." +msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)." msgstr "" #: ../../../CHANGELOG.md:266 -msgid "" -"If you've tweaked any of this playbook's `_path_prefix` variables and " -"made them use a regular expression, you will now need to make additional " -"adjustments. The playbook makes extensive use of `PathPrefix()` matchers " -"in Traefik rules and `PathPrefix` does not support regular expressions " -"anymore. To work around it, you may now need to override a whole " -"`_traefik_rule` variable and switch it from [`PathPrefix` to " -"`PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-" -"pathprefix-and-pathregexp)." +msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)." msgstr "" #: ../../../CHANGELOG.md:268 -msgid "" -"If you're not using [matrix-media-repo](./docs/configuring-playbook-" -"matrix-media-repo.md) (the only role we had to tweak to adapt it to " -"Traefik v3), you **may potentially downgrade to Traefik v2** (if " -"necessary) by adding `traefik_verison: v2.11.4` to your configuration. " -"People using `matrix-media-repo` cannot downgrade this way, because " -"`matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing " -"matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that" -" Traefik v2 does not understand." +msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand." msgstr "" #: ../../../CHANGELOG.md:270 @@ -812,36 +461,19 @@ msgid "HTTP/3 is enabled by default" msgstr "" #: ../../../CHANGELOG.md:272 -msgid "" -"In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is " -"no longer considered experimental now. Due to this, **the playbook auto-" -"enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` " -"(port `8448`) entrypoints." +msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints." msgstr "" #: ../../../CHANGELOG.md:274 -msgid "" -"HTTP3 uses the UDP protocol and **the playbook (together with Docker) " -"will make sure that the appropriate ports** (`443` over UDP & `8448` over" -" UDP) **are exposed and whitelisted in your server's firewall**. However," -" **if you have another firewall in front of your server** (as is the case" -" for many cloud providers), **you will need to manually open these UDP " -"ports**." +msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**." msgstr "" #: ../../../CHANGELOG.md:276 -msgid "" -"If you do not open the UDP ports correctly or there is some other issue, " -"clients (browsers, mostly) will fall-back to " -"[HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even " -"[HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." +msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)." msgstr "" #: ../../../CHANGELOG.md:278 -msgid "" -"Still, if HTTP/3 cannot function correctly in your setup, it's best to " -"disable advertising support for it (and misleading clients into trying to" -" use HTTP/3)." +msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)." msgstr "" #: ../../../CHANGELOG.md:280 @@ -849,12 +481,7 @@ msgid "To **disable HTTP/3**, you can use the following configuration:" msgstr "" #: ../../../CHANGELOG.md:294 -msgid "" -"If you are using [your own webserver](./docs/configuring-playbook-own-" -"webserver.md) (in front of Traefik), port binding on UDP port `8448` by " -"default due to HTTP/3 is either unnecessary or [may get in the " -"way](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3402). If it does, you can disable it:" +msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:" msgstr "" #: ../../../CHANGELOG.md:307 @@ -866,31 +493,15 @@ msgid "synapse-admin is now restricted to your homeserver's URL by default" msgstr "" #: ../../../CHANGELOG.md:311 -msgid "" -"A new feature introduced in synapse-admin [v0.10.0](https://github.com" -"/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and " -"supported by the playbook since a a few months ago) provides the ability " -"to [restrict its usage to a specific homeserver](https://github.com" -"/Awesome-Technologies/synapse-" -"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" -"#restricting-available-homeserver) (or multiple homeservers)." +msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)." msgstr "" #: ../../../CHANGELOG.md:313 -msgid "" -"The playbook has just started making use of this feature. **From now on, " -"your synapse-admin instance will be restricted to the homeserver you're " -"managing via the playbook**. When configured like this, the *Homeserver " -"URL* field in synapse-admin's web UI changes from a text field to a " -"dropdown having a single value (the URL of your homeserver). This makes " -"usage simpler for most people, as they won't need to manually enter a " -"*Homeserver URL* anymore." +msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore." msgstr "" #: ../../../CHANGELOG.md:315 -msgid "" -"If you'd like **to go back to the old unrestricted behavior**, use the " -"following configuration:" +msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:" msgstr "" #: ../../../CHANGELOG.md:323 @@ -902,58 +513,31 @@ msgid "The URL-prefix for Hookshot generic webhooks has changed" msgstr "" #: ../../../CHANGELOG.md:327 -msgid "" -"Until now, generic Hookshot webhook URLs looked like this: " -"`https://matrix.example.com/hookshot/webhooks/:hookId`." +msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`." msgstr "" #: ../../../CHANGELOG.md:329 -msgid "" -"The `/hookshot/webhooks` common prefix gets stripped by Traefik " -"automatically, so Hookshot only sees the part that comes after " -"(`/:hookId`)." +msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)." msgstr "" #: ../../../CHANGELOG.md:331 -msgid "" -"[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1681), Hookshot started to prefer to handle webhooks at a " -"`/webhook/:hookId` path (instead of directly at `/:hookId`)." +msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)." msgstr "" #: ../../../CHANGELOG.md:333 -msgid "" -"To avoid future problems, we've " -"[reconfigured](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot " -"configuration to use webhook URLs that include `/webhook` in the URL " -"suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of " -"`/hookshot/webhooks/:hookId`). This means that when we strip the common " -"prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to " -"Hookshot, just like recommended." +msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended." msgstr "" #: ../../../CHANGELOG.md:335 -msgid "" -"When generating new webhooks, you should start seeing the new URLs being " -"used." +msgid "When generating new webhooks, you should start seeing the new URLs being used." msgstr "" #: ../../../CHANGELOG.md:337 -msgid "" -"**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new " -"URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your" -" webhooks will not break just yet." +msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet." msgstr "" #: ../../../CHANGELOG.md:339 -msgid "" -"However, **we recommend that you update all your old webhook URLs** " -"(configured in other systems) to include the new `/webhook` path " -"component, so that future Hookshot changes (whenever they come) will not " -"break your webhooks. You don't need to do anything on the Hookshot side -" -" you merely need to reconfigure the remote systems that use your webhook " -"URLs." +msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs." msgstr "" #: ../../../CHANGELOG.md:342 @@ -965,29 +549,15 @@ msgid "The maubot user is now managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:346 -msgid "" -"To make things easier and to be consistent with other roles, the " -"[maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by" -" default) is [now](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3376) automatically created be the playbook." +msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook." msgstr "" #: ../../../CHANGELOG.md:348 -msgid "" -"If you have an existing maubot installation, you will need to specify " -"`matrix_bot_maubot_initial_password` in your `vars.yml` file to make the " -"playbook not complain about it being undefined. Since the bot is already " -"registered in your installation, there's nothing for the playbook to do " -"anyway. In case you don't remember the password you've registered your " -"maubot user account with, you can specify any value for this variable." +msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable." msgstr "" #: ../../../CHANGELOG.md:350 -msgid "" -"If you've registered another username for the bot (other than the " -"recommended default of `bot.maubot`), consider adjusting the " -"`matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: " -"my.maubot.username`)." +msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)." msgstr "" #: ../../../CHANGELOG.md:353 @@ -999,18 +569,11 @@ msgid "WeChat bridging support" msgstr "" #: ../../../CHANGELOG.md:357 -msgid "" -"Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s " -"[efforts](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3241), the playbook now supports bridging to " -"[WeChat](https://www.wechat.com/) via the [matrix-" -"wechat](https://github.com/duo/matrix-wechat) bridge." +msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge." msgstr "" #: ../../../CHANGELOG.md:359 -msgid "" -"See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-" -"wechat.md) documentation page for getting started." +msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:362 @@ -1018,70 +581,31 @@ msgid "2024-03-26" msgstr "" #: ../../../CHANGELOG.md:364 -msgid "" -"(Backward Compatibility Break) The playbook now defaults to KeyDB, " -"instead of Redis" +msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" msgstr "" #: ../../../CHANGELOG.md:366 -msgid "" -"**TLDR**: if the playbook used installed Redis as a dependency for you " -"before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a " -"drop-in alternative) due to [Redis having changed its " -"license](https://redis.com/blog/redis-adopts-dual-source-available-" -"licensing/)." +msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)." msgstr "" #: ../../../CHANGELOG.md:368 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook now uses " -"[KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), " -"instead of [Redis](https://redis.io/)." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)." msgstr "" #: ../../../CHANGELOG.md:370 -msgid "" -"The playbook used to install Redis (and now installs KeyDB in its place) " -"if services have a need for it ([enabling worker support for " -"Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-" -"workers), [enabling Hookshot encryption](docs/configuring-playbook-" -"bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly " -"enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." +msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)." msgstr "" #: ../../../CHANGELOG.md:372 -msgid "" -"This change is provoked by the fact that [Redis is now \"source " -"available\"](https://redis.com/blog/redis-adopts-dual-source-available-" -"licensing/). According to the Limitations of [the new " -"license](https://redis.com/legal/rsalv2-agreement/) (as best as we " -"understand them, given that we're not lawyers), using Redis in the " -"playbook (even in a commercial FOSS service like " -"[etke.cc](https://etke.cc/)) does not violate the new Redis license. That" -" said, we'd rather neither risk it, nor endorse shady licenses and " -"products that pretend to be free-software. Another high-quality " -"alternative to Redis seems to be " -"[Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly " -"license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-" -"file#readme) is no better than Redis's." +msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's." msgstr "" #: ../../../CHANGELOG.md:374 -msgid "" -"Next time your run the playbook (via the `setup-all` tag), **Redis will " -"be automatically uninstalled and replaced with KeyDB**. Some Synapse " -"downtime may occur while the switch happens." +msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens." msgstr "" #: ../../../CHANGELOG.md:376 -msgid "" -"Users on `arm32` should be aware that there's **neither a prebuilt " -"`arm32` container image for KeyDB**, nor the KeyDB role supports self-" -"building yet. Users on this architecture likely don't run Synapse with " -"workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis" -" is necessary in an `arm32` deployment, disabling KeyDB and making the " -"playbook fall back to Redis is possible (see below)." +msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)." msgstr "" #: ../../../CHANGELOG.md:387 @@ -1093,11 +617,7 @@ msgid "Initial work on IPv6 support" msgstr "" #: ../../../CHANGELOG.md:391 -msgid "" -"Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can " -"now enable IPv6 for container networks for various components (roles) via" -" [the `devture_systemd_docker_base_ipv6_enabled` " -"variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." +msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)." msgstr "" #: ../../../CHANGELOG.md:393 @@ -1105,17 +625,11 @@ msgid "It should be noted that:" msgstr "" #: ../../../CHANGELOG.md:395 -msgid "" -"Matrix roles (`roles/custom/matrix-*`) respect this variable, but " -"external roles (those defined in `requirements.yml` and installed via " -"`just roles`) do not respect it yet. Additional work is necessary" +msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary" msgstr "" #: ../../../CHANGELOG.md:396 -msgid "" -"changing the variable subsequently may not change existing container " -"networks. Refer to [these " -"instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" +msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)" msgstr "" #: ../../../CHANGELOG.md:397 @@ -1127,19 +641,11 @@ msgid "Pantalaimon support" msgstr "" #: ../../../CHANGELOG.md:401 -msgid "" -"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " -"playbook can now install the [Pantalaimon](https://github.com/matrix-" -"org/pantalaimon) E2EE aware proxy daemon for you. It's already possible " -"to integrate it with [Draupnir](docs/configuring-playbook-bot-" -"draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs " -"for details." +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details." msgstr "" #: ../../../CHANGELOG.md:403 -msgid "" -"See our [Setting up Pantalaimon](docs/configuring-playbook-" -"pantalaimon.md) documentation to get started." +msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:406 @@ -1151,25 +657,15 @@ msgid "Support for Draupnir-for-all" msgstr "" #: ../../../CHANGELOG.md:410 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " -"install [Draupnir for all](./docs/configuring-playbook-appservice-" -"draupnir-for-all.md) (aka multi-instance Draupnir running in appservice " -"mode)." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)." msgstr "" #: ../../../CHANGELOG.md:412 -msgid "" -"This is an alternative to [running Draupnir in bot mode](./docs" -"/configuring-playbook-bot-draupnir.md), which is still supported by the " -"playbook." +msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook." msgstr "" #: ../../../CHANGELOG.md:414 -msgid "" -"The documentation page for [Draupnir for all](./docs/configuring-" -"playbook-appservice-draupnir-for-all.md) contains more information on how" -" to install it." +msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it." msgstr "" #: ../../../CHANGELOG.md:417 @@ -1181,44 +677,23 @@ msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridg msgstr "" #: ../../../CHANGELOG.md:421 -msgid "" -"The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-" -"facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-" -"mautrix-instagram.md) bridges are being [superseded by a new " -"bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-" -"meta](https://github.com/mautrix/meta) bridge." +msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge." msgstr "" #: ../../../CHANGELOG.md:423 -msgid "" -"The playbook now supports the new mautrix-meta bridge - a single bridge, " -"which can run in different modes and bridge to Messenger (via " -"[Facebook](https://facebook.com/), Facebook over " -"[Tor](https://www.torproject.org/) or via " -"[Messenger](https://messenger.com/)) and " -"[Instagram](https://instagram.com/). The playbook makes this bridge " -"available via 2 separate Ansible roles, allowing you to easily run 2 " -"instances of mautrix-meta, for bridging to both services at the same " -"time." +msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time." msgstr "" #: ../../../CHANGELOG.md:425 -msgid "" -"If you're using mautrix-facebook or mautrix-instagram right now, **you " -"can still continue using the old bridges, but may wish to change to the " -"new bridge implementations**. See:" +msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:" msgstr "" #: ../../../CHANGELOG.md:427 -msgid "" -"[Setting up Instagram bridging via Mautrix Meta](docs/configuring-" -"playbook-bridge-mautrix-meta-instagram.md)" +msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../CHANGELOG.md:429 -msgid "" -"[Setting up Messenger bridging via Mautrix Meta](docs/configuring-" -"playbook-bridge-mautrix-meta-messenger.md)" +msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)" msgstr "" #: ../../../CHANGELOG.md:431 @@ -1234,44 +709,23 @@ msgid "Much larger Synapse caches and cache auto-tuning enabled by default" msgstr "" #: ../../../CHANGELOG.md:438 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses " -"much larger caches and enables Synapse's [cache auto-tuning " -"functionality](https://matrix-" -"org.github.io/synapse/latest/usage/configuration/config_documentation.html" -"#caches-and-associated-values). This work and the default values used by " -"the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s " -"[Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)." msgstr "" #: ../../../CHANGELOG.md:440 -msgid "" -"The playbook has always used a very conservative cache factor " -"(`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK " -"for small and underactive deployments, but is not ideal for larger " -"servers. Paradoxically, a small global cache factor value [does not " -"necessarily decrease RAM usage as a whole](https://github.com/matrix-" -"org/synapse/issues/3939)." +msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" #: ../../../CHANGELOG.md:442 -msgid "" -"The playbook now uses **a 20x larger cache factor** (currently `10`), " -"adjusts a few other cache-related variables, and **enables cache auto-" -"tuning** via the following variables:" +msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:" msgstr "" #: ../../../CHANGELOG.md:444 -msgid "" -"`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to " -"1/8 of total RAM with a cap of 2GB; values are specified in bytes" +msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" #: ../../../CHANGELOG.md:445 -msgid "" -"`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to" -" 1/16 of total RAM with a cap of 1GB; values are specified in bytes" +msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" #: ../../../CHANGELOG.md:446 @@ -1279,16 +733,11 @@ msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" #: ../../../CHANGELOG.md:448 -msgid "" -"These values should be good defaults for most servers, but may change " -"over time as we experiment further." +msgid "These values should be good defaults for most servers, but may change over time as we experiment further." msgstr "" #: ../../../CHANGELOG.md:450 -msgid "" -"Refer to our new [Tuning caches and cache autotuning](docs/maintenance-" -"synapse.md#tuning-caches-and-cache-autotuning) documentation section for " -"more details." +msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details." msgstr "" #: ../../../CHANGELOG.md:453 @@ -1296,37 +745,19 @@ msgid "2024-01-31" msgstr "" #: ../../../CHANGELOG.md:455 -msgid "" -"(Backward-compatibility break) Minor changes necessary for some people " -"serving a static website at the base domain" +msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain" msgstr "" #: ../../../CHANGELOG.md:457 -msgid "" -"This only affects people who are [Serving a static website at the base " -"domain](./docs/configuring-playbook-base-domain-serving.md#serving-a" -"-static-website-at-the-base-domain), but not managing its `index.html` " -"through the playbook." +msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook." msgstr "" #: ../../../CHANGELOG.md:459 -msgid "" -"That is, for people who have " -"`matrix_static_files_file_index_html_enabled: false` in their `vars.yml` " -"configuration, the playbook has a new default behavior. Since the " -"playbook is not managing the `index.html` file, it will default to a more" -" sensible way of handling the base domain - redirecting " -"`https://example.com/` to `https://matrix.example.com/`, instead of " -"serving a 404 page." +msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page." msgstr "" #: ../../../CHANGELOG.md:461 -msgid "" -"If you are managing your static website by yourself (by dropping files " -"into `/matrix/static-files/public` somehow), then you probably don't wish" -" for such redirection to happen. You can disable it by adding " -"`matrix_static_files_container_labels_base_domain_root_path_redirection_enabled:" -" false` to your `vars.yml` configuration file." +msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:464 @@ -1338,45 +769,19 @@ msgid "Support for more efficient (specialized) Synapse workers" msgstr "" #: ../../../CHANGELOG.md:468 -msgid "" -"Thanks to [Charles Wright](https://github.com/cvwright) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook has [received " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3100) for load-balancing the Synapse workload via " -"[specialized workers](./docs/configuring-playbook-synapse.md#specialized-" -"workers) which are supposed to work better than our old [generic " -"workers](./docs/configuring-playbook-synapse.md#generic-workers) " -"implementation." +msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation." msgstr "" #: ../../../CHANGELOG.md:470 -msgid "" -"For now, playbook defaults remain unchanged and the `one-of-each` " -"[workers preset](./docs/configuring-playbook-synapse.md#worker-presets) " -"continues being the default. However, the default may change in the " -"future. If you'd like to remain on this preset even if/when the defaults " -"change, consider explicitly adding `matrix_synapse_workers_preset: one-" -"of-each` to your `vars.yml` configuration." +msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:472 -msgid "" -"Our specialized workers setup is based on recommendations found in [Tom " -"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/index.html). What's special " -"about our new setup is that we try to parse information out of the " -"request (who the user is; which room is being operated on) and try to " -"forward similar requests to the same worker. As an example, this means " -"that once a worker caches some room information, subsequent requests for " -"the same room will be routed to the same worker (which supposedly still " -"has the room's state cached)." +msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)." msgstr "" #: ../../../CHANGELOG.md:474 -msgid "" -"To get started, refer to our [Specialized workers](./docs/configuring-" -"playbook-synapse.md#specialized-workers) documentation section." +msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section." msgstr "" #: ../../../CHANGELOG.md:477 @@ -1388,47 +793,27 @@ msgid "Switching to Element's AGPLv3-licensed Synapse release" msgstr "" #: ../../../CHANGELOG.md:481 -msgid "" -"A few months ago, the [Element](https://element.io/) company has " -"[announced](https://element.io/blog/element-to-adopt-agplv3/) that their " -"work on the Synapse homeserver would no longer be available under the " -"permissive [Apache-2.0 " -"license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" +msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:" msgstr "" #: ../../../CHANGELOG.md:483 -msgid "" -"the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software" -" license - the same license that this Ansible playbook has always used" +msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used" msgstr "" #: ../../../CHANGELOG.md:484 -msgid "" -"a proprietary license, for those wishing for Element to [sell them an " -"exception](https://gnu.org/philosophy/selling-exceptions.html) to the " -"AGPLv3 license" +msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license" msgstr "" #: ../../../CHANGELOG.md:486 -msgid "" -"You can also learn more in [this post](https://matrix.org/blog/2023/11/06" -"/future-of-synapse-dendrite/) by the Matrix Foundation." +msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation." msgstr "" #: ../../../CHANGELOG.md:488 -msgid "" -"The change has [already happened](https://element.io/blog/synapse-now-" -"lives-at-github-com-element-hq-synapse/) and the first Synapse release " -"under the new license is here: [v1.99.0](https://github.com/element-" -"hq/synapse/releases/tag/v1.99.0)." +msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)." msgstr "" #: ../../../CHANGELOG.md:490 -msgid "" -"There is no up-to-date alternative Synapse fork right now and this free-" -"software (AGPLv3-licensed) playbook is definitely not against free-" -"software licenses, so we are now switching to the Element-maintained " -"Synapse release." +msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release." msgstr "" #: ../../../CHANGELOG.md:492 @@ -1436,32 +821,19 @@ msgid "**What does this mean to you?**" msgstr "" #: ../../../CHANGELOG.md:494 -msgid "" -"For most home users, it doesn't mean anything. Your installation will " -"continue working as it should and you don't need to do anything." +msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:496 -msgid "" -"For people building commercial products on top of Synapse, they may have " -"to either buy a license exception from Element (from what we hear, the " -"fee depends on the number of monthly-active users on your instance) or " -"they may need to release all related code as free-software (which is what" -" we've been doing at [etke.cc](https://etke.cc/) " -"([here](https://gitlab.com/etke.cc)) all along)." +msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)." msgstr "" #: ../../../CHANGELOG.md:498 -msgid "" -"We're no lawyers and this changelog entry does not aim to give you the " -"best legal advice, so please research on your own!" +msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!" msgstr "" #: ../../../CHANGELOG.md:500 -msgid "" -"If you'd like to continue using the old Apache-2.0-licensed Synapse (for " -"a while longer anyway), the playbook makes it possible by intruducing a " -"new Ansible variable. You can do it like this:" +msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:" msgstr "" #: ../../../CHANGELOG.md:512 @@ -1469,28 +841,11 @@ msgid "Notes:" msgstr "" #: ../../../CHANGELOG.md:514 -msgid "" -"if you had already upgraded Synapse to `v1.99.0` by running this " -"playbook, you will still be able to downgrade to `v1.98.0`, because both " -"releases use the same database schema version (`SCHEMA_COMPAT_VERSION = " -"83` - see [here for v1.98.0](https://github.com/element-" -"hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and" -" [here for v1.99.0](https://github.com/element-" -"hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). " -"More details on Synapse's database schema are available [here](https" -"://element-" -"hq.github.io/synapse/develop/development/database_schema.html). It " -"appears that there are no new database migrations introduced in " -"`v1.99.0`, so going back to the older release is possible. This is not " -"guaranteed to hold true for future Synapse releases, so if you're seeing " -"this early-enough, consider pinning the version and organization before " -"re-running the playbook and getting upgraded to the latest version" +msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version" msgstr "" #: ../../../CHANGELOG.md:516 -msgid "" -"running an outdated homeserver exposes you to security issues and " -"incompatibilities. Only consider doing this as a short-term solution." +msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution." msgstr "" #: ../../../CHANGELOG.md:518 @@ -1502,13 +857,7 @@ msgid "`Draupnir` has been relicensed to AFL-3.0" msgstr "" #: ../../../CHANGELOG.md:522 -msgid "" -"As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) " -"Draupnir changed its licence to AFL-3.0 from the CSL licence. This change" -" affects playbook users who could not run Draupnir under the old license " -"restrictions. The new license is considerably less restrictive and is OSI" -" approved. Draupnir version v1.86.0 and later are covered by this license" -" change." +msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change." msgstr "" #: ../../../CHANGELOG.md:524 @@ -1520,15 +869,7 @@ msgid "Goodbye, `matrix-nginx-proxy` 🪦" msgstr "" #: ../../../CHANGELOG.md:528 -msgid "" -"**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component " -"are now gone. This brought about many other internal changes (and " -"security improvements), so setups may need minor adjustments or suffer " -"some (temporary) breakage. People who have been on the Traefik-native " -"setup may upgrade without much issues. Those running their own Traefik " -"instance may need minor changes. People who have been postponing the " -"migration away from `matrix-nginx-proxy` (for more than a year already!) " -"will now finally need to do something about it." +msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it." msgstr "" #: ../../../CHANGELOG.md:530 @@ -1536,26 +877,11 @@ msgid "Backstory on `matrix-nginx-proxy`" msgstr "" #: ../../../CHANGELOG.md:532 -msgid "" -"We gather here today to celebrate the loss of a once-beloved component in" -" our stack - `matrix-nginx-proxy`. It's been our " -"[nginx](https://nginx.org/)-based reverse-proxy of choice since the " -"[first commit](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7" -" years ago." +msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago." msgstr "" #: ../../../CHANGELOG.md:534 -msgid "" -"For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy " -"in our setup (doing SSL termination, etc.). After [transitioning to " -"Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-" -"nginx-proxy` took a step back. Nevertheless, since it was so ingrained " -"into the playbook, it still remained in use - even if only internally. " -"Despite our warnings of its imminent death, many of you have indubitably " -"continued to use it instead of Traefik. Its suffering continued for too " -"long, because it served many different purposes and massive effort was " -"required to transition them to others." +msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others." msgstr "" #: ../../../CHANGELOG.md:536 @@ -1567,82 +893,43 @@ msgid "an [nginx](https://nginx.org/)-based reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:539 -msgid "" -"an Ansible role organizing the work of " -"[certbot](https://certbot.eff.org/) - retrieving free [Let's " -"Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-" -"proxy` and for the [Coturn TURN server](./docs/configuring-playbook-" -"turn.md)" +msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)" msgstr "" #: ../../../CHANGELOG.md:540 -msgid "" -"a central component for reverse-proxying to the [long list of " -"services](./docs/configuring-playbook.md) supported by the playbook. As " -"such, it became a dependency that all these services had to inject " -"themselves into during runtime" +msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime" msgstr "" #: ../../../CHANGELOG.md:541 -msgid "" -"an intermediary through which addons (bridges, bots) communicated with " -"the homeserver. Going through an intermediary (instead of directly " -"talking to the homeserver) is useful when certain components (like " -"[matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or " -"[matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are " -"enabled, because it lets these services \"steal routes\" from the " -"homeserver" +msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver" msgstr "" #: ../../../CHANGELOG.md:542 -msgid "" -"a webserver for serving the `/.well-known/matrix` static files (generated" -" by the `matrix-base` role until now)" +msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)" msgstr "" #: ../../../CHANGELOG.md:543 -msgid "" -"a webserver [serving your base domain](./docs/configuring-playbook-base-" -"domain-serving.md) (and also generating the `index.html` page for it)" +msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)" msgstr "" #: ../../../CHANGELOG.md:544 -msgid "" -"a central component providing global [HTTP Basic " -"Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) " -"password-protection for all `/metrics` endpoints when metrics were " -"exposed publicly for consumption from a remote Prometheus server" +msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server" msgstr "" #: ../../../CHANGELOG.md:546 -msgid "" -"Talk about a jack of all trades! The [UNIX " -"philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker " -"container philosophy) of \"do one thing and do it well\" had been " -"severely violated for too long." +msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long." msgstr "" #: ../../../CHANGELOG.md:548 -msgid "" -"On a related note, we also had a large chain of reverse-proxies in the " -"mix. In the worst case, it was something like this: (Traefik -> `matrix-" -"nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-" -"reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." +msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)." msgstr "" #: ../../../CHANGELOG.md:550 -msgid "" -"Due to complexity and the playbook's flexibility (trying to accommodate a" -" mix of tens of components), many layers of indirection were necessary. " -"We do like reverse-proxies, but.. not quite enough to enjoy going through" -" a chain of ~4 of them before reaching the target service." +msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service." msgstr "" #: ../../../CHANGELOG.md:552 -msgid "" -"After **a ton of work** in the last weeks (200+ commits, which changed " -"467 files - 8684 insertions and 8913 deletions), **we're finally saying " -"goodbye** to `matrix-nginx-proxy`." +msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`." msgstr "" #: ../../../CHANGELOG.md:554 @@ -1654,21 +941,11 @@ msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." msgstr "" #: ../../../CHANGELOG.md:558 -msgid "" -"In most cases, there's only Traefik and all services being registered " -"directly with it. When [Synapse workers](./docs/configuring-playbook-" -"synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-" -"reverse-proxy-companion` remains as an extra reverse-proxy that requests " -"go through (for load-balancing to the correct Synapse worker), but in all" -" other cases services are exposed directly." +msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly." msgstr "" #: ../../../CHANGELOG.md:560 -msgid "" -"This reduces \"network\" hops (improving performance) and also decreases " -"the number of components (containers). Each Ansible role in our setup is " -"now independent and doesn't need to interact with other roles during " -"runtime." +msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime." msgstr "" #: ../../../CHANGELOG.md:562 @@ -1676,59 +953,23 @@ msgid "Traefik now has an extra job" msgstr "" #: ../../../CHANGELOG.md:564 -msgid "" -"Previously, **Traefik had a single purpose** - being the main reverse-" -"proxy. It was either front-most (terminating SSL, etc.) or you were " -"[fronting Traefik with your own other reverse-proxy](./docs/configuring-" -"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" -"webserver-with-another-reverse-proxy). In any case - it had this central " -"(yet decentralized) job." +msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job." msgstr "" #: ../../../CHANGELOG.md:566 -msgid "" -"Now, **Traefik has one more role** - it serves as an intermediary which " -"allows addon services (bridges, bots, etc.) to communicate with the " -"homeserver. As mentioned above, such an intermediary service is not " -"strictly necessary in all kinds of setups, but more complex setups " -"(including [matrix-media-repo](./docs/configuring-playbook-matrix-media-" -"repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-" -"corporal.md)) benefit from it." +msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it." msgstr "" #: ../../../CHANGELOG.md:568 -msgid "" -"To perform this new role, Traefik now has a new internal " -"[entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called " -"`matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, " -"Synapse and even `matrix-synapse-reverse-proxy-companion`) and " -"homeserver-related core services ([matrix-media-repo](./docs/configuring-" -"playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-" -"playbook-matrix-corporal.md) and potentially others) register their " -"routes (using [container labels](https://docs.docker.com/config/labels-" -"custom-metadata/)) not only on the public entrypoints (`web-secure`, " -"`matrix-federation`), but also on this new internal entrypoint." +msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint." msgstr "" #: ../../../CHANGELOG.md:570 -msgid "" -"Doing so, services can contact Traefik on this entrypoint's dedicated " -"port (the URL defaults to `http://matrix-traefik:8008`) and reach the " -"homeserver Client-Server API as they expect. Internally, Traefik takes " -"care of the routing to the correct service." +msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service." msgstr "" #: ../../../CHANGELOG.md:572 -msgid "" -"We've also considered keeping it simple and having services talk to the " -"homeserver over the public internet (e.g. `https://matrix.example.com`) " -"thus reusing all existing Traefik routing labels. In this scenario, " -"performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to" -" TLS and networking overhead. The need for fast internal communication " -"(via the new internal non-TLS-enabled Traefik entrypoint) is definitely " -"there. In our benchmarks, Traefik even proved more efficient than nginx " -"at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out " -"of ~1400 rps when talking to the Synapse homeserver directly)." +msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)." msgstr "" #: ../../../CHANGELOG.md:574 @@ -1736,54 +977,27 @@ msgid "Traefik serving this second purpose has a few downsides:" msgstr "" #: ../../../CHANGELOG.md:576 -msgid "" -"Traefik becomes a runtime dependency for all homeserver-dependant " -"container services" +msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services" msgstr "" #: ../../../CHANGELOG.md:577 -msgid "" -"all homeserver-dependant services now need to be connected to the " -"`traefik` container network, even if they don't need public internet " -"exposure" +msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure" msgstr "" #: ../../../CHANGELOG.md:579 -msgid "" -"Despite these downsides (which the playbook manages automatically), we " -"believe it's still a good compromise given the amount of complexity it " -"eliminates and the performance benefits it yields. One alternative we've " -"[considered](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary " -"service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both " -"had much higher complexity (one more component in the mix; duplication of" -" effort to produce nginx-compatible route definitions for it) and " -"slightly worse performance (see above)." +msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)." msgstr "" #: ../../../CHANGELOG.md:581 -msgid "" -"People running the default Traefik setup do not need to do anything to " -"make Traefik take on this extra job. Your Traefik configuration will be " -"updated automatically." +msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically." msgstr "" #: ../../../CHANGELOG.md:583 -msgid "" -"**People runnning their own Traefik reverse-proxy need to do [minor " -"adjustments](#people-managing-their-own-traefik-instance-need-to-do-" -"minor-changes)**, as described in the section below." +msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below." msgstr "" #: ../../../CHANGELOG.md:585 -msgid "" -"You may disable Traefik acting as an intermediary by explicitly setting " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled`" -" to `false`. Services would then be configured to talk to the homeserver " -"directly, giving you a slight performance boost and a \"simpler\" Traefik" -" setup. However, such a configuration is less tested and will cause " -"troubles, especially if you enable more services (like `matrix-media-" -"repo`, etc.) in the future. As such, it's not recommended." +msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended." msgstr "" #: ../../../CHANGELOG.md:587 @@ -1791,47 +1005,23 @@ msgid "People managing their own Traefik instance need to do minor changes" msgstr "" #: ../../../CHANGELOG.md:589 -msgid "" -"This section is for people [managing their own Traefik instance on the " -"Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-" -"managed-by-you). Those [using Traefik managed by the playbook](./docs" -"/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) " -"don't need to do any changes." +msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes." msgstr "" #: ../../../CHANGELOG.md:591 -msgid "" -"Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), " -"you need to adapt your configuration to add the additional `matrix-" -"internal-matrix-client-api` entrypoint and potentially configure the " -"`matrix_playbook_reverse_proxy_container_network` variable. See the " -"[Traefik managed by you](./docs/configuring-playbook-own-webserver.md" -"#traefik-managed-by-you) documentation section for more details." +msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details." msgstr "" #: ../../../CHANGELOG.md:593 -msgid "" -"People fronting Traefik with another reverse proxy need to do minor " -"changes" +msgid "People fronting Traefik with another reverse proxy need to do minor changes" msgstr "" #: ../../../CHANGELOG.md:595 -msgid "" -"We've already previously mentioned that you need to do some minor " -"[configuration changes related to `traefik_additional_entrypoints_auto" -"`](#backward-compatibility-configuration-changes-required-for-people-" -"fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy)." +msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." msgstr "" #: ../../../CHANGELOG.md:597 -msgid "" -"If you don't do these changes (switching from " -"`traefik_additional_entrypoints_auto` to multiple other variables), your " -"Traefik setup will not automatically receive the new `matrix-internal-" -"matrix-client-api` Traefik entrypoint and Traefik would not be able to " -"perform [its new duty of connecting addons with the homeserver](#traefik-" -"now-has-an-extra-job)." +msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)." msgstr "" #: ../../../CHANGELOG.md:599 @@ -1839,16 +1029,11 @@ msgid "Supported reverse proxy types are now fewer" msgstr "" #: ../../../CHANGELOG.md:601 -msgid "" -"This section is for people using a more custom reverse-proxy setup - " -"those having `matrix_playbook_reverse_proxy_type` set to a value " -"different than the default (`playbook-managed-traefik`)." +msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)." msgstr "" #: ../../../CHANGELOG.md:603 -msgid "" -"Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to" -" 7 different values to accommodate various reverse-proxy setups." +msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups." msgstr "" #: ../../../CHANGELOG.md:605 @@ -1856,59 +1041,35 @@ msgid "The complexity of this is too high, so we only support 3 values right now msgstr "" #: ../../../CHANGELOG.md:607 -msgid "" -"(the default) `playbook-managed-traefik`, when you're [using Traefik " -"managed by the playbook](./docs/configuring-playbook-own-webserver.md" -"#traefik-managed-by-the-playbook)" +msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)" msgstr "" #: ../../../CHANGELOG.md:608 -msgid "" -"`other-traefik-container`, when you're [managing your own Traefik " -"instance on the Matrix server](./docs/configuring-playbook-own-" -"webserver.md#traefik-managed-by-you)" +msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)" msgstr "" #: ../../../CHANGELOG.md:609 -msgid "" -"`none`, when you wish for [no reverse-proxy integration to be done at " -"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" -"on-the-matrix-side-at-all)" +msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)" msgstr "" #: ../../../CHANGELOG.md:611 -msgid "" -"The `none` value is not recommended and may not work adequately, due to " -"lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-" -"extra-job) in our setup." +msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup." msgstr "" #: ../../../CHANGELOG.md:613 -msgid "" -"**Previous values that are now gone** (and the playbook would report them" -" as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, " -"`other-on-same-host` and `other-on-another-host`." +msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`." msgstr "" #: ../../../CHANGELOG.md:615 -msgid "" -"If you were using these values as a way to stay away from Traefik, you " -"now have 2 options:" +msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:" msgstr "" #: ../../../CHANGELOG.md:617 -msgid "" -"(recommended) [Fronting Traefik with another reverse-proxy](./docs" -"/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-" -"proxy-webserver-with-another-reverse-proxy)" +msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)" msgstr "" #: ../../../CHANGELOG.md:618 -msgid "" -"(not recommended) [Using no reverse-proxy on the Matrix side at " -"all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-" -"on-the-matrix-side-at-all) and reverse-proxying to each and every service" -" manually" +msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually" msgstr "" #: ../../../CHANGELOG.md:620 @@ -1916,49 +1077,27 @@ msgid "Container networking changes" msgstr "" #: ../../../CHANGELOG.md:622 -msgid "" -"Now that `matrix-nginx-proxy` is not in the mix, it became easier to " -"clear out some other long-overdue technical debt." +msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt." msgstr "" #: ../../../CHANGELOG.md:624 -msgid "" -"Since the very beginning of this playbook, all playbook services were " -"connected to a single (shared) `matrix` container network. Later on, some" -" additional container networks appeared, but most services (database, " -"etc.) still remained in the `matrix` container network. This meant that " -"any random container in this network could try to talk (or attack) the " -"Postgres database operating in the same `matrix` network." +msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network." msgstr "" #: ../../../CHANGELOG.md:626 -msgid "" -"Moving components (especially the database) into other container networks" -" was difficult - it required changes to many other components to ensure " -"correct connectivity." +msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity." msgstr "" #: ../../../CHANGELOG.md:628 -msgid "" -"All the hard work has been done now. We've added much more isolation " -"between services by splitting them up into separate networks (`matrix-" -"homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, " -"etc). Components are only joined to the networks they need and should " -"(for the most part) not be able to access unrelated things." +msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things." msgstr "" #: ../../../CHANGELOG.md:630 -msgid "" -"Carrying out these container networking changes necessitated modifying " -"many components, so **we're hoping not too many bugs were introduced in " -"the process**." +msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**." msgstr "" #: ../../../CHANGELOG.md:632 -msgid "" -"We've refrained from creating too many container networks (e.g. one for " -"each component), to avoid exhausting Docker's default network pool and " -"contaminating the container networks list too much." +msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much." msgstr "" #: ../../../CHANGELOG.md:634 @@ -1966,44 +1105,23 @@ msgid "Metrics exposure changes" msgstr "" #: ../../../CHANGELOG.md:636 -msgid "" -"This section is for people who are exposing monitoring metrics publicly, " -"to be consumed by an external Prometheus server." +msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server." msgstr "" #: ../../../CHANGELOG.md:638 -msgid "" -"Previously, `matrix-nginx-proxy` was potentially password-protecting all " -"`/metrics/*` endpoints with the same username and password (specified as " -"plain-text in your `vars.yml` configuration file)." +msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)." msgstr "" #: ../../../CHANGELOG.md:640 -msgid "" -"From now on, there are new variables for doing roughly the same - " -"`matrix_metrics_exposure_enabled`, " -"`matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & " -"Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for" -" details." +msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details." msgstr "" #: ../../../CHANGELOG.md:642 -msgid "" -"`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now," -" each role provides its own metrics exposure and protection by " -"registering with Traefik. Nevertheless, all roles are wired (via playbook" -" configuration in `group_vars/matrix_servers`) to obey these new " -"`matrix_metrics_exposure_*` variables. We've eliminated the " -"centralization, but have kept the ease of use. Now, you can also do per-" -"service password-protection (with different credentials), should you need" -" to do that for some reason." +msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason." msgstr "" #: ../../../CHANGELOG.md:644 -msgid "" -"The playbook will tell you about all variables that you need to migrate " -"during runtime, so rest assured - you shouldn't be able to miss anything!" +msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!" msgstr "" #: ../../../CHANGELOG.md:646 @@ -2011,30 +1129,15 @@ msgid "Matrix static files" msgstr "" #: ../../../CHANGELOG.md:648 -msgid "" -"As mentioned above, static files like `/.well-known/matrix/*` or your " -"base domain's `index.html` file (when [serving the base domain via the " -"Matrix server](./docs/configuring-playbook-base-domain-serving.md) was " -"enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` " -"roles and put into a `/matrix/static-files` directory on the server. Then" -" `matrix-nginx-proxy` was serving all these static files." +msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files." msgstr "" #: ../../../CHANGELOG.md:650 -msgid "" -"All of this has been extracted into a new `matrix-static-files` Ansible " -"role that's part of the playbook. The static files generated by this new " -"role still live at roughly the same place (`/matrix/static-files/public` " -"directory, instead of `/matrix/static-files`)." +msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)." msgstr "" #: ../../../CHANGELOG.md:652 -msgid "" -"The playbook will migrate and update the `/.well-known/matrix/*` files " -"automatically but not your own files in `nginx-proxy/data/matrix-domain/`" -" you will need to back these up yourself otherwise they will be lost. It " -"will also warn you about usage of old variable names, so you can adapt to" -" the new names." +msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names." msgstr "" #: ../../../CHANGELOG.md:654 @@ -2042,54 +1145,27 @@ msgid "A note on performance" msgstr "" #: ../../../CHANGELOG.md:656 -msgid "" -"Some of you have been voicing their concerns (for a long time) about " -"Traefik being too slow and nginx being better." +msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better." msgstr "" #: ../../../CHANGELOG.md:658 -msgid "" -"Some online benchmarks support this by demonstrating slightly higher SSL-" -"termination performance in favor of nginx. The upcoming Traefik v3 " -"release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-" -"traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL " -"performance by some 20%, but that still ends up being somewhat slower " -"than nginx." +msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx." msgstr "" #: ../../../CHANGELOG.md:660 -msgid "" -"We believe that using Traefik provides way too many benefits to worry " -"about this minor performance impairment." +msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment." msgstr "" #: ../../../CHANGELOG.md:662 -msgid "" -"The heaviest part of running a Matrix homeserver is all the slow and " -"potentially inefficient things the homeserver (e.g. Synapse) is doing. " -"These things affect performance much more than whatever reverse-proxy is " -"in front. Your server will die the same way by joining the famously large" -" **Matrix HQ** room, no matter which reverse-proxy you put in front." +msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front." msgstr "" #: ../../../CHANGELOG.md:664 -msgid "" -"Even our previously mentioned benchmarks (yielding ~1300 rps) are " -"synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-" -"use does much more than this." +msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this." msgstr "" #: ../../../CHANGELOG.md:666 -msgid "" -"If this is still not convincing enough for you and you want the best " -"possible performance, consider [Fronting Traefik with another reverse-" -"proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-" -"integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus " -"having the slowest part - SSL termination - happen elsewhere) or [Using " -"no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-" -"own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The " -"playbook will not get in your way of doing that, but these options may " -"make your life much harder. Performance comes at a cost, after all." +msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all." msgstr "" #: ../../../CHANGELOG.md:668 @@ -2097,74 +1173,39 @@ msgid "Migration procedure" msgstr "" #: ../../../CHANGELOG.md:670 -msgid "" -"The updated playbook will automatically perform some migration tasks for " -"you:" +msgid "The updated playbook will automatically perform some migration tasks for you:" msgstr "" #: ../../../CHANGELOG.md:672 -msgid "" -"It will stop and remove the `matrix-nginx-proxy` systemd service and " -"container for you. This behavior cannot be disabled. It's essential that " -"this service gets stopped, because it remaining running (and having " -"container labels) may confuse Traefik as to where to route HTTP requests." +msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests." msgstr "" #: ../../../CHANGELOG.md:674 -msgid "" -"It will delete the `/matrix/nginx-proxy` directory and all files within " -"it. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: " -"false` to your `vars.yml` configuration file. Doing so will leave its " -"data around." +msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around." msgstr "" #: ../../../CHANGELOG.md:676 -msgid "" -"It will delete the `/matrix/ssl` directory and all files within it. You " -"can disable this behavior by adding " -"`matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to " -"your `vars.yml` configuration file. If you have some important " -"certificates there for some reason, take them out or temporarily disable " -"removal of these files until you do." +msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do." msgstr "" #: ../../../CHANGELOG.md:678 -msgid "" -"It will tell you about all variables (`matrix_nginx_proxy_*` and many " -"others - even from other roles) that have changed during this large " -"nginx-elimination upgrade. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled:" -" false` to your `vars.yml` configuration file." +msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:680 -msgid "" -"It will tell you about any leftover `matrix_nginx_proxy_*` variables in " -"your `vars.yml` file. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled:" -" false` to your `vars.yml` configuration file." +msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:682 -msgid "" -"It will tell you about any leftover `matrix_ssl_*` variables in your " -"`vars.yml` file. You can disable this behavior by adding " -"`matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: " -"false` to your `vars.yml` configuration file." +msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file." msgstr "" #: ../../../CHANGELOG.md:684 -msgid "" -"We don't recommend changing these variables and suppressing warnings, " -"unless you know what you're doing." +msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing." msgstr "" #: ../../../CHANGELOG.md:686 -msgid "" -"**Most people should just upgrade as per-normal**, bearing in mind that a" -" lot has changed and some issues may arise. The playbook would guide you " -"through renamed variables automatically." +msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically." msgstr "" #: ../../../CHANGELOG.md:688 @@ -2172,18 +1213,11 @@ msgid "Conclusion" msgstr "" #: ../../../CHANGELOG.md:690 -msgid "" -"Thousands of lines of code were changed across hundreds of files. All " -"addons (bridges, bots) were rewired in terms of container networking and " -"in terms of how they reach the homeserver." +msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver." msgstr "" #: ../../../CHANGELOG.md:692 -msgid "" -"I don't actively use all the ~100 components offered by the playbook (no " -"one does), nor do I operate servers exercising all edge-cases. As such, " -"issues may arise. Please have patience and report (or try to fix) these " -"issues!" +msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!" msgstr "" #: ../../../CHANGELOG.md:695 @@ -2191,43 +1225,23 @@ msgid "2024-01-14" msgstr "" #: ../../../CHANGELOG.md:697 -msgid "" -"(Backward Compatibility) Configuration changes required for people " -"fronting the integrated reverse-proxy webserver with another reverse-" -"proxy" +msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:699 -msgid "" -"If you're on the default setup (using the Traefik reverse-proxy as " -"installed by the playbook), you don't need to do anything." +msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:701 -msgid "" -"People who are [Fronting the integrated Traefik reverse-proxy webserver " -"with another reverse-proxy](./docs/configuring-playbook-own-webserver.md" -"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy), as per our previous instructions are redefining " -"`traefik_additional_entrypoints_auto` in their `vars.yml` configuration." +msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:703 -msgid "" -"Such a full variable redefinion is intrustive, because it prevents the " -"playbook from injecting additional entrypoints into the Traefik " -"webserver. In the future, the playbook may have a need to do so." +msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so." msgstr "" #: ../../../CHANGELOG.md:705 -msgid "" -"For this reason, we no longer recommend completely redefining " -"`traefik_additional_entrypoints_auto`. The playbook now defines [various " -"`matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` " -"variables in the `defaults/main.yml` file](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-" -"base/defaults/main.yml) of the `matrix-base` role which can be used as a " -"safer alternative to `traefik_additional_entrypoints_auto`." +msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`." msgstr "" #: ../../../CHANGELOG.md:707 @@ -2235,12 +1249,7 @@ msgid "Adapt your configuration as seen below:" msgstr "" #: ../../../CHANGELOG.md:740 -msgid "" -"Also, feel free to read the [Fronting the integrated Traefik reverse-" -"proxy webserver with another reverse-proxy](./docs/configuring-playbook-" -"own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-" -"another-reverse-proxy) documentation section again for additional " -"details." +msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details." msgstr "" #: ../../../CHANGELOG.md:743 @@ -2248,87 +1257,43 @@ msgid "2024-01-13" msgstr "" #: ../../../CHANGELOG.md:745 -msgid "" -"matrix-reminder-bot update with more secure (backward-incompatible) " -"default settings" +msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings" msgstr "" #: ../../../CHANGELOG.md:747 -msgid "" -"**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453" -"/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs" -"/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By " -"default, like other bridges/bots managed by the playbook, it will only " -"provide its services to users of your own server (not to anyone, even " -"across the Matrix Federation). If that's fine, there's nothing you need " -"to do." +msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do." msgstr "" #: ../../../CHANGELOG.md:749 -msgid "" -"Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-" -"matrix-reminder-bot.md) has been picked up by [Kim " -"Brose](https://github.com/HarHarLinks) and " -"[@svierne](https://github.com/svierne)." +msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)." msgstr "" #: ../../../CHANGELOG.md:751 -msgid "" -"Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-" -"reminder-bot/releases/tag/v0.3.0) release is out. The new version is now " -"available for the ARM64 architecture, so playbook users on this " -"architecture will no longer need to wait for [self-building](./docs/self-" -"building.md) to happen." +msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen." msgstr "" #: ../../../CHANGELOG.md:753 -msgid "" -"The new version also comes with new `allowlist` and `blocklist` settings," -" which make it possible to restrict who can use the bot. Previously " -"anyone, even across the Matrix Federation could talk to it and schedule " -"reminders." +msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders." msgstr "" #: ../../../CHANGELOG.md:755 -msgid "" -"The playbook defaults all bridges and bots (where possible) to only be " -"exposed to users of the current homeserver, not users across federation. " -"Thanks to the new version of this bot making such a restriction possible," -" we're now making use of it. The playbook (via its " -"`group_vars/matrix_servers` file) automatically enables the `allowlist` " -"(`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures" -" it in such a way " -"(`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to " -"restrict the bot to your homeserver's users." +msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users." msgstr "" #: ../../../CHANGELOG.md:757 -msgid "" -"If you need **to undo or tweak these security improvements**, you can " -"change your `vars.yml` file to:" +msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:" msgstr "" #: ../../../CHANGELOG.md:759 -msgid "" -"disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled:" -" false`), making the bot allow usage by anyone, anywhere" +msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere" msgstr "" #: ../../../CHANGELOG.md:761 -msgid "" -"inject additional allowed servers or users by adding **additional** (on " -"top of the default allowlist in " -"`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes " -"in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list " -"variable (see the [syntax reference](https://github.com/anoadragon453" -"/matrix-reminder-" -"bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" +msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))" msgstr "" #: ../../../CHANGELOG.md:763 -msgid "" -"override the default allowlist (in the `group_vars/matrix_servers` file) " -"by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" +msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`" msgstr "" #: ../../../CHANGELOG.md:766 @@ -2340,17 +1305,11 @@ msgid "matrix-mailer has been replaced by the exim-relay external role" msgstr "" #: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410 -msgid "" -"We're continuing our effort to make [the playbook use external roles for " -"some things](#the-playbook-now-uses-external-roles-for-some-things), so " -"as to avoid doing everything ourselves and to facilitate code re-use." +msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use." msgstr "" #: ../../../CHANGELOG.md:772 -msgid "" -"The `matrix-mailer` role has been moved to its own repository ([ansible-" -"role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-" -"role-exim-relay)) that this playbook now includes." +msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes." msgstr "" #: ../../../CHANGELOG.md:774 @@ -2366,11 +1325,7 @@ msgid "update your roles (run `just roles` or `make roles`)" msgstr "" #: ../../../CHANGELOG.md:778 -msgid "" -"update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to " -"`exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> " -"`exim_relay_sender_address`). If you find none, it means you're using the" -" default configuration and your migraiton job is even simpler." +msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler." msgstr "" #: ../../../CHANGELOG.md:779 @@ -2378,10 +1333,7 @@ msgid "re-run the playbook (`install-all` or `setup-all`)" msgstr "" #: ../../../CHANGELOG.md:781 -msgid "" -"The playbook will take care of stopping the old `matrix-mailer` systemd " -"service, relocating its directory and restarting it under the new name " -"(`matrix-exim-relay.service`)." +msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)." msgstr "" #: ../../../CHANGELOG.md:784 @@ -2393,25 +1345,15 @@ msgid "mautrix-signal now powered by the new Go-based bridge" msgstr "" #: ../../../CHANGELOG.md:788 -msgid "" -"The old Python-based [mautrix-signal](https://github.com/mautrix/signal) " -"bridge is no longer maintained upstream. It's also known to have issues " -"linking new devices." +msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices." msgstr "" #: ../../../CHANGELOG.md:790 -msgid "" -"It seems like the path forward is to switch to the new mautrix-signal " -"bridge written in Golang, which we did thanks to [PR " -"#3031](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." +msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)." msgstr "" #: ../../../CHANGELOG.md:792 -msgid "" -"The playbook should **automatically migrate your mautrix-signal " -"installation to the new bridge code**. You will **need to relink all your" -" devices** to continue your bridged conversations." +msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations." msgstr "" #: ../../../CHANGELOG.md:795 @@ -2423,53 +1365,23 @@ msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" msgstr "" #: ../../../CHANGELOG.md:799 -msgid "" -"**TDLR**: if your Matrix server is federating (which it mostly likely is," -" unless you've [disabled federation](docs/configuring-playbook-" -"federation.md#disabling-federation)), your public rooms will not only be " -"joinable across federation (as they've always been), but from now on will" -" be discoverable (made available as a list across federation). We're " -"changing this by flipping the value for Synapse's " -"`allow_public_rooms_over_federation` setting to `true`, going against the" -" upstream default. Servers that disable federation are not affected. " -"Servers that have public rooms which are not published to the room " -"directory are also not affected." +msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected." msgstr "" #: ../../../CHANGELOG.md:801 -msgid "" -"We generally try to stick to the default configuration for Synapse (and " -"all other components), unless these defaults seem wrong or harmful. One " -"such previous case from a few months ago was us [Enabling " -"`forget_rooms_on_leave` by default for Synapse](#enabling-" -"forget_rooms_on_leave-by-default-for-synapse) - the default value was " -"making Synapse more wasteful of resources by default." +msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default." msgstr "" #: ../../../CHANGELOG.md:803 -msgid "" -"Today, we're going against upstream defaults again and flipping the " -"`allow_public_rooms_over_federation` configuration option to `true`. This" -" way, public rooms on your server will be made discoverable by others via" -" federation, using the [`GET /_matrix/federation/v1/publicRooms` of the " -"Server-Server API](https://spec.matrix.org/v1.8/server-server-" -"api/#get_matrixfederationv1publicrooms)." +msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)." msgstr "" #: ../../../CHANGELOG.md:805 -msgid "" -"The upstream Synapse default is `false` (disabled), so that public rooms " -"are not exposed for other servers to discover (learn about their " -"existence). Nevertheless, even if these rooms are not exposed (listed) " -"for discovery, they are **still joinable** by anyone who knows their " -"address or is invited to the room by an existing member." +msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member." msgstr "" #: ../../../CHANGELOG.md:807 -msgid "" -"**We go against the upstream default** in an effort to make Matrix " -"federation more useful - a public room should be globally public - not " -"only joinable, but also discoverable across federation." +msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation." msgstr "" #: ../../../CHANGELOG.md:809 @@ -2477,50 +1389,16 @@ msgid "The **historical reasoning** behind this change is as follows:" msgstr "" #: ../../../CHANGELOG.md:811 -msgid "" -"`allow_public_rooms_over_federation` seems to have been enabled by " -"default for Synapse until v1.7.0 (~2019), just like we believe it should " -"be for a globally-federating network - rooms should be joinable and " -"discoverable across federation." +msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation." msgstr "" #: ../../../CHANGELOG.md:813 -msgid "" -"In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got " -"disabled](https://github.com/element-" -"hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891)" -" by default in a [security-by-" -"obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) " -"workaround for misconfigured servers. See the [Avoiding unwelcome " -"visitors on private Matrix servers](https://matrix.org/blog/2019/11/09" -"/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` " -"blog article. We believe that people wishing for a truly private server, " -"should [disable federation](docs/configuring-playbook-federation.md" -"#disabling-federation), instead of having a fully-federating server and " -"trying to hide its public rooms. We also provide other workarounds below." -" We (and the Synapse team, obviously) believe that Matrix should federate" -" by default, so federating the public room list seems to make sense." +msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense." msgstr "" #: ../../../CHANGELOG.md:815 #, python-format -msgid "" -"[etke.cc](https://etke.cc/) has been developing the free-software [Matrix" -" Rooms Search](https://github.com/etkecc/mrs) project for a while now. " -"One public (demo) instance of it is hosted at " -"[matrixrooms.info](https://matrixrooms.info/). This search engine tries " -"to go through the Matrix federation and discover & index public rooms to " -"allow people to find them. We believe it's vital for Matrix (and any chat" -" or social network for that matter) to be more discoverable, so that " -"people can find communities and others to talk to. Today (on 23rd of " -"October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of " -"these, only `1567` servers (7%) are making their public rooms " -"discoverable. Who knows what wonderful communities and rooms are " -"available on these 93% other Matrix servers that are supposedly " -"federating, but are still gate-keeping their public room list. " -"Indubitably, many of these servers are hosted via matrix-docker-ansible-" -"deploy, so we feel partially responsible for making Matrix federation " -"less useful." +msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful." msgstr "" #: ../../../CHANGELOG.md:817 @@ -2528,45 +1406,15 @@ msgid "Here are **actions you may wish to take** as a result of this change:" msgstr "" #: ../../../CHANGELOG.md:819 -msgid "" -"(recommended) embrace the new default. If your Matrix server is " -"federating, your public rooms have always been joinable across federation" -" anyway. Exposing the list of public rooms does no harm and more-so does " -"good by contributing to the usefulness of the Matrix network by " -"facilitating room discovery." +msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery." msgstr "" #: ../../../CHANGELOG.md:821 -msgid "" -"(switch to a better way of doings things on your semi-private server) The" -" problem that the Synapse team appears to have solved by flipping the " -"`allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to " -"for \"mostly private\" servers, which federate and have a bunch of rooms " -"made public (and published in their room directory) in an effort to allow" -" people on the same homeserver to easily find and join them (self-" -"onboarding). With the introduction of Matrix Spaces, you can reorganize " -"your flow around spaces - you can auto-join your users to a Matrix Space " -"(via Synapse's `auto_join_rooms` setting - controlled by our " -"`matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to " -"the space and make them joinable by people belonging to the space. That " -"is to say, do not make rooms public and do not publish them to the room " -"directory unless they are really public. Instead, use other mechanisms " -"for semi-public rooms or private rooms. One alternative is to stick to " -"what you're doing (public rooms published to your rooms directory) but " -"having a `m.federate: true` flag set during creation (clients like " -"Element Web have a nice UI checkbox for this) to explicitly disable " -"federation for them." +msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them." msgstr "" #: ../../../CHANGELOG.md:823 -msgid "" -"(keeping the old behavior) if you wish to keep doing what you're doing " -"(keeping your Matrix server federating, but hiding its public rooms " -"list), add `matrix_synapse_allow_public_rooms_over_federation: false` to " -"your `vars.yml` configuration. This restores the old behavior. You may " -"also consider [disabling federation](docs/configuring-playbook-" -"federation.md#disabling-federation) completely instead of relying on " -"security-by-obscurity measures." +msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures." msgstr "" #: ../../../CHANGELOG.md:826 @@ -2578,37 +1426,19 @@ msgid "Postgres parameters are automatically tuned now" msgstr "" #: ../../../CHANGELOG.md:830 -msgid "" -"The playbook has provided some hints about [Tuning PostgreSQL](docs" -"/maintenance-postgres.md#tuning-postgresql) for quite a while now." +msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now." msgstr "" #: ../../../CHANGELOG.md:832 -msgid "" -"From now on, the [Postgres Ansible role](https://github.com/mother-of-" -"all-self-hosting/ansible-role-postgres) automatically tunes your Postgres" -" configuration with the same [calculation " -"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" -" that powers https://pgtune.leopard.in.ua/." +msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/." msgstr "" #: ../../../CHANGELOG.md:834 -msgid "" -"Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) " -"documentation page has details about how you can turn auto-tuning off or " -"adjust the automatically-determined Postgres configuration parameters " -"manually." +msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually." msgstr "" #: ../../../CHANGELOG.md:836 -msgid "" -"People who [enable load-balancing with Synapse workers](docs/configuring-" -"playbook-synapse.md#load-balancing-with-workers) no longer need to " -"increase the maximum number of Postgres connections manually (previously " -"done via `postgres_process_extra_arguments`). There's a new variable " -"(`postgres_max_connections`) for controlling this number and the playbook" -" automatically raises its value from `200` to `500` for setups which " -"enable workers." +msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers." msgstr "" #: ../../../CHANGELOG.md:839 @@ -2620,16 +1450,11 @@ msgid "SchildiChat Web support" msgstr "" #: ../../../CHANGELOG.md:843 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat" -" Web](https://github.com/SchildiChat/schildichat-desktop) client." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client." msgstr "" #: ../../../CHANGELOG.md:845 -msgid "" -"See our [Configuring SchildiChat Web](docs/configuring-playbook-client-" -"schildichat-web.md) documentation to get started." +msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:848 @@ -2641,21 +1466,11 @@ msgid "mautrix-wsproxy support" msgstr "" #: ../../../CHANGELOG.md:852 -msgid "" -"Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who " -"finished what was started by [James Reilly](https://github.com/hanthor) " -"and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now " -"supports bridging to Android SMS and Apple iMessage via the [mautrix-" -"wsproxy](https://github.com/mautrix/wsproxy) service (in combination with" -" a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running" -" on your Mac or Android phone)." +msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)." msgstr "" #: ../../../CHANGELOG.md:854 -msgid "" -"See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple " -"iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) " -"documentation page for getting started." +msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:857 @@ -2667,20 +1482,11 @@ msgid "matrix-registration-bot usage changed" msgstr "" #: ../../../CHANGELOG.md:861 -msgid "" -"[matrix-registration-bot](docs/configuring-playbook-bot-matrix-" -"registration-bot.md) got some updates and now supports password-only-" -"based login. Therefore the bot now doesn't need any manual configuration " -"except setting a password in your `vars.yml`. The bot will be registered " -"as admin and access tokens will be obtained automatically by the bot." +msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot." msgstr "" #: ../../../CHANGELOG.md:863 -msgid "" -"**For existing users** You need to set " -"`matrix_bot_matrix_registration_bot_bot_password` if you previously only " -"used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also " -"remove the following deprecated settings" +msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings" msgstr "" #: ../../../CHANGELOG.md:865 @@ -2700,13 +1506,7 @@ msgid "mautrix-gmessages support" msgstr "" #: ../../../CHANGELOG.md:873 -msgid "" -"Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, " -"the playbook now supports bridging to [Google " -"Messages](https://messages.google.com/) via the [mautrix-" -"gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting" -" up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-" -"mautrix-gmessages.md) documentation page for getting started." +msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:876 @@ -2718,20 +1518,11 @@ msgid "matrix-media-repo support" msgstr "" #: ../../../CHANGELOG.md:880 -msgid "" -"Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from " -"[FUTO](https://www.futo.org/), the creators of the [Circles " -"app](https://circu.li/), the playbook can now set up [matrix-media-" -"repo](https://github.com/turt2live/matrix-media-repo) - an alternative " -"way to store homeserver media files, powered by a homeserver-independent " -"implementation which supports S3 storage, IPFS, deduplication and other " -"advanced features." +msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features." msgstr "" #: ../../../CHANGELOG.md:882 -msgid "" -"To learn more see our [Storing Matrix media files using matrix-media-" -"repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." +msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:885 @@ -2743,32 +1534,19 @@ msgid "Enabling `forget_rooms_on_leave` by default for Synapse" msgstr "" #: ../../../CHANGELOG.md:889 -msgid "" -"With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/2698), we've also **changed the default " -"value** of the `forget_rooms_on_leave` setting of Synapse to a value of " -"`true`. This way, **when you leave a room, Synapse will now forget it " -"automatically**." +msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**." msgstr "" #: ../../../CHANGELOG.md:891 -msgid "" -"The upstream Synapse default is `false` (disabled), so that you must " -"forget rooms manually after leaving." +msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving." msgstr "" #: ../../../CHANGELOG.md:893 -msgid "" -"**We go against the upstream default** ([somewhat " -"controversially](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/2700)) in an effort to make Synapse leaner and potentially do" -" what we believe most users would expect their homeserver to be doing." +msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing." msgstr "" #: ../../../CHANGELOG.md:895 -msgid "" -"If you'd like to go back to the old behavior, add the following to your " -"configuration: `matrix_synapse_forget_rooms_on_leave: false`" +msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`" msgstr "" #: ../../../CHANGELOG.md:898 @@ -2780,29 +1558,15 @@ msgid "The matrix-jitsi role lives independently now" msgstr "" #: ../../../CHANGELOG.md:902 -msgid "" -"**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-" -"jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) " -"repository, part of the [MASH playbook](https://github.com/mother-of-all-" -"self-hosting/mash-playbook). Some variables have been renamed. All " -"functionality remains intact." +msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:904 -msgid "" -"The `matrix-jitsi` role has been relocated in its own repository, part of" -" the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) project - an Ansible playbook for self-hosting [a growing list " -"of FOSS software](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack " -"on the Matrix server itself did not stand right with you or you always " -"wanted to host most stuff, you can now use this new playbook to do so." +msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." msgstr "" #: ../../../CHANGELOG.md:906 -msgid "" -"As part of the extraction process of this role out of the Matrix " -"playbook, a few other things improved:" +msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:" msgstr "" #: ../../../CHANGELOG.md:908 @@ -2810,22 +1574,15 @@ msgid "**native Traefik support** has been added" msgstr "" #: ../../../CHANGELOG.md:909 -msgid "" -"**support for hosting under a subpath** has been added, although it " -"suffers from a few minor issues listed [here](https://github.com/mother-" -"of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" +msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)" msgstr "" #: ../../../CHANGELOG.md:911 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Jitsi or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not." msgstr "" #: ../../../CHANGELOG.md:913 -msgid "" -"If you're making use of Jitsi via this playbook, you will need to update " -"variable references in your `vars.yml` file:" +msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:915 @@ -2837,9 +1594,7 @@ msgid "`matrix_jitsi_` -> `jitsi_`" msgstr "" #: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944 -msgid "" -"some other internal variables have changed, but the playbook will tell " -"you about them" +msgid "some other internal variables have changed, but the playbook will tell you about them" msgstr "" #: ../../../CHANGELOG.md:919 @@ -2851,19 +1606,11 @@ msgid "ntfy Web App is disabled by default" msgstr "" #: ../../../CHANGELOG.md:923 -msgid "" -"ntfy provides a web app, which is now disabled by default, because it may" -" be unknown to and unused by most users of this playbook. You can enable " -"it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs" -"/configuring-playbook-ntfy.md))." +msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))." msgstr "" #: ../../../CHANGELOG.md:925 -msgid "" -"This change was already applied a while before this entry, but as some " -"users were reporting the missing web app, this entry was added (see " -"[#2529](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2529))." +msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))." msgstr "" #: ../../../CHANGELOG.md:928 @@ -2875,44 +1622,23 @@ msgid "The matrix-prometheus role lives independently now" msgstr "" #: ../../../CHANGELOG.md:932 -msgid "" -"**TLDR**: the `matrix-prometheus` role is now included from the [ansible-" -"role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-" -"role-prometheus) repository, part of the [MASH " -"playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). " -"Some variables have been renamed. All functionality remains intact." +msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:934 -msgid "" -"The `matrix-prometheus` role has been relocated in its own repository, " -"part of the [MASH playbook](https://github.com/mother-of-all-self-hosting" -"/mash-playbook) project - an Ansible playbook for self-hosting [a growing" -" list of FOSS software](https://github.com/mother-of-all-self-hosting" -"/mash-playbook/blob/main/docs/supported-services.md). If hosting a " -"Prometheus stack on the Matrix server itself did not stand right with you" -" or you always wanted to host most stuff, you can now use this new " -"playbook to do so." +msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so." msgstr "" #: ../../../CHANGELOG.md:936 -msgid "" -"Extracting the Prometheus role out of this Matrix playbook required huge " -"internal refactoring to the way the Prometheus configuration (scraping " -"jobs) is generated. If you notice any breakage after upgrading, let us " -"know." +msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know." msgstr "" #: ../../../CHANGELOG.md:938 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Prometheus or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not." msgstr "" #: ../../../CHANGELOG.md:940 -msgid "" -"If you're making use of Prometheus via this playbook, you will need to " -"update variable references in your `vars.yml` file:" +msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:942 @@ -2932,21 +1658,11 @@ msgid "synapse-auto-compressor support" msgstr "" #: ../../../CHANGELOG.md:951 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-" -"compress-state](https://github.com/matrix-org/rust-synapse-compress-" -"state)'s `synapse_auto_compressor` tool to run periodically." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically." msgstr "" #: ../../../CHANGELOG.md:953 -msgid "" -"If enabled, `synapse_auto_compressor` runs on a schedule and compresses " -"your Synapse database's `state_groups` table. It was possible to run " -"`rust-synapse-compress-state` manually via the playbook even before - see" -" [Compressing state with rust-synapse-compress-state](docs/maintenance-" -"synapse.md#compressing-state-with-rust-synapse-compress-state). However, " -"using `synapse_auto_compressor` is better, because:" +msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:" msgstr "" #: ../../../CHANGELOG.md:955 @@ -2954,21 +1670,15 @@ msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" msgstr "" #: ../../../CHANGELOG.md:956 -msgid "" -"it's a set-it-and-forget-it tool that you can enable and never have to " -"deal with manual compression anymore" +msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore" msgstr "" #: ../../../CHANGELOG.md:958 -msgid "" -"This tool needs to be enabled manually, for now. In the future, we're " -"considering enabling it by default for all Synapse installations." +msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations." msgstr "" #: ../../../CHANGELOG.md:960 -msgid "" -"See our [Setting up synapse-auto-compressor](docs/configuring-playbook-" -"synapse-auto-compressor.md) documentation to get started." +msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:963 @@ -2980,31 +1690,15 @@ msgid "Sliding Sync proxy (Element X) support" msgstr "" #: ../../../CHANGELOG.md:967 -msgid "" -"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting " -"it started](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up" -" and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the" -" playbook can now install and configure the [sliding-sync " -"proxy](https://github.com/matrix-org/sliding-sync)." +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)." msgstr "" #: ../../../CHANGELOG.md:969 -msgid "" -"The upcoming Element X clients ([Element X iOS](https://github.com" -"/vector-im/element-x-ios) and [Element X Android](https://github.com" -"/vector-im/element-x-android)) require the `sliding-sync` proxy to do " -"their job. **These clients are still in beta** (especially Element X " -"Android, which requires manual compilation to get it working with a " -"non-`matrix.org` homeseserver). Playbook users can now easily give these " -"clients a try and help test them thanks to us having `sliding-sync` " -"support." +msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support." msgstr "" #: ../../../CHANGELOG.md:971 -msgid "" -"To get started, see our [Setting up the Sliding Sync proxy](docs" -"/configuring-playbook-sliding-sync-proxy.md) documentation page." +msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:974 @@ -3016,23 +1710,15 @@ msgid "The matrix-etherpad role lives independently now" msgstr "" #: ../../../CHANGELOG.md:978 -msgid "" -"**TLDR**: the `matrix-etherpad` role is now included from [another " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"etherpad). Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:980 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're using Etherpad or not." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not." msgstr "" #: ../../../CHANGELOG.md:982 -msgid "" -"If you're making use of Etherpad via this playbook, you will need to " -"update variable references in your `vars.yml` file:" +msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:984 @@ -3060,9 +1746,7 @@ msgid "for Traefik users:" msgstr "" #: ../../../CHANGELOG.md:991 -msgid "" -"define your own `etherpad_hostname` and `etherpad_path_prefix` as you see" -" fit" +msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit" msgstr "" #: ../../../CHANGELOG.md:993 @@ -3082,15 +1766,11 @@ msgid "Along with this relocation, the new role also:" msgstr "" #: ../../../CHANGELOG.md:999 -msgid "" -"supports [self-building](docs/self-building.md), so it should work on " -"`arm32` and `arm64` architectures" +msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures" msgstr "" #: ../../../CHANGELOG.md:1000 -msgid "" -"has native Traefik reverse-proxy support (Etherpad requests no longer go " -"through `matrix-nginx-proxy` when using Traefik)" +msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)" msgstr "" #: ../../../CHANGELOG.md:1003 @@ -3102,31 +1782,15 @@ msgid "Traefik is the default reverse-proxy now" msgstr "" #: ../../../CHANGELOG.md:1007 -msgid "" -"**TLDR**: new installations will now default to Traefik as their reverse-" -"proxy. Existing users need to explicitly choose their reverse-proxy type." -" [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is" -" strongly encouraged. `matrix-nginx-proxy` may break over time and will " -"ultimately be removed." +msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed." msgstr "" #: ../../../CHANGELOG.md:1009 -msgid "" -"As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy " -"configuration changes and initial Traefik support](#backward-" -"compatibility-reverse-proxy-configuration-changes-and-initial-traefik-" -"support), the playbook is moving to Traefik as its default SSL-" -"terminating reverse-proxy." +msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy." msgstr "" #: ../../../CHANGELOG.md:1011 -msgid "" -"Until now, we've been doing the migration gradually and keeping full " -"backward compatibility. New installations were defaulting to `matrix-" -"nginx-proxy` (just like before), while existing installations were " -"allowed to remain on `matrix-nginx-proxy` as well. This makes things very" -" difficult for us, because we need to maintain and think about lots of " -"different setups:" +msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:" msgstr "" #: ../../../CHANGELOG.md:1013 @@ -3150,33 +1814,19 @@ msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:1018 -msgid "" -"`nginx` webserver operated by the user, running without a container on " -"the same server" +msgid "`nginx` webserver operated by the user, running without a container on the same server" msgstr "" #: ../../../CHANGELOG.md:1020 -msgid "" -"Each change we do and each new feature that comes in needs to support all" -" these different ways of reverse-proxying. Because `matrix-nginx-proxy` " -"was the default and pretty much everyone was (and still is) using it, " -"means that new PRs also come with `matrix-nginx-proxy` as their main " -"focus and Traefik as an afterthought, which means we need to spend hours " -"fixing up Traefik support." +msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support." msgstr "" #: ../../../CHANGELOG.md:1022 -msgid "" -"We can't spend all this time maintaining so many different configurations" -" anymore. Traefik support has been an option for 2 weeks and lots of " -"people have already migrated their server and have tested things out. " -"Traefik is what we use and preferentially test for." +msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for." msgstr "" #: ../../../CHANGELOG.md:1024 -msgid "" -"It's time for the **next step in our migration process** to Traefik and " -"elimination of `matrix-nginx-proxy`:" +msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:" msgstr "" #: ../../../CHANGELOG.md:1026 @@ -3184,13 +1834,7 @@ msgid "Traefik is now the default reverse-proxy for new installations" msgstr "" #: ../../../CHANGELOG.md:1027 -msgid "" -"All existing users need to explicitly choose their reverse-proxy type by " -"defining the `matrix_playbook_reverse_proxy_type` variable in their " -"`vars.yml` configuration file. We strongly encourage existing users to " -"[switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the" -" nginx setup is bound to become more and more broken over time until it's" -" ultimately removed" +msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed" msgstr "" #: ../../../CHANGELOG.md:1029 @@ -3198,12 +1842,7 @@ msgid "How do I switch my existing setup to Traefik?" msgstr "" #: ../../../CHANGELOG.md:1031 -msgid "" -"**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy " -"provided by the playbook), switching to Traefik can happen with a simple " -"configuration change. Follow this section from 2 weeks ago: [How do I " -"explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-" -"traefik-right-now)." +msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)." msgstr "" #: ../../../CHANGELOG.md:1033 @@ -3211,10 +1850,7 @@ msgid "If you experience trouble:" msgstr "" #: ../../../CHANGELOG.md:1035 -msgid "" -"Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-" -"matrix-nginx-proxy) to bring your server back online using the old " -"reverse-proxy" +msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy" msgstr "" #: ../../../CHANGELOG.md:1036 @@ -3226,14 +1862,7 @@ msgid "Try switching to Traefik again later" msgstr "" #: ../../../CHANGELOG.md:1039 -msgid "" -"**For users with a more special reverse-proxying setup** (another nginx " -"server, Apache, Caddy, etc.), the migration may not be so smooth. Follow " -"the [Using your own webserver](docs/configuring-playbook-own-" -"webserver.md) guide. Ideally, your custom reverse-proxy will be " -"configured in such a way that it **fronts the Traefik reverse-proxy** " -"provided by the playbook. Other means of reverse-proxying are more " -"fragile and may be deprecated in the future." +msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future." msgstr "" #: ../../../CHANGELOG.md:1041 @@ -3241,9 +1870,7 @@ msgid "I already use my own Traefik server. How do I plug that in?" msgstr "" #: ../../../CHANGELOG.md:1043 -msgid "" -"See the [Traefik managed by the playbook](docs/configuring-playbook-own-" -"webserver.md#traefik-managed-by-the-playbook) section." +msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section." msgstr "" #: ../../../CHANGELOG.md:1045 @@ -3251,17 +1878,11 @@ msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" msgstr "" #: ../../../CHANGELOG.md:1047 -msgid "" -"This playbook manages many different services. All these services were " -"initially integrated with `matrix-nginx-proxy`." +msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`." msgstr "" #: ../../../CHANGELOG.md:1049 -msgid "" -"While we migrate all these components to have native Traefik support, " -"some still go through nginx internally (Traefik -> local `matrix-nginx-" -"proxy` -> component). As time goes on, internal reliance on `matrix-" -"nginx-proxy` will gradually decrease until it's completely removed." +msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed." msgstr "" #: ../../../CHANGELOG.md:1051 @@ -3269,25 +1890,15 @@ msgid "How do I remain on matrix-nginx-proxy?" msgstr "" #: ../../../CHANGELOG.md:1053 -msgid "" -"Most new work and testing targets Traefik, so remaining on nginx is " -"**not** \"the good old stable\" option, but rather the \"still available," -" but largely untested and likely to be broken very soon\" option." +msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option." msgstr "" #: ../../../CHANGELOG.md:1055 -msgid "" -"To proceed regardless of this warning, add " -"`matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your " -"configuration." +msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration." msgstr "" #: ../../../CHANGELOG.md:1057 -msgid "" -"At some point in the **near** future (days, or even weeks at most), we " -"hope to completely get rid of `matrix-nginx-proxy` (or break it enough to" -" make it unusable), so you **will soon be forced to migrate** anyway. " -"Plan your migration accordingly." +msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly." msgstr "" #: ../../../CHANGELOG.md:1059 @@ -3295,11 +1906,7 @@ msgid "How do I keep using my own other reverse-proxy?" msgstr "" #: ../../../CHANGELOG.md:1061 -msgid "" -"We recommend that you follow the guide for [Fronting the integrated " -"reverse-proxy webserver with another reverse-proxy](docs/configuring-" -"playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-" -"webserver-with-another-reverse-proxy)." +msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)." msgstr "" #: ../../../CHANGELOG.md:1064 @@ -3311,16 +1918,11 @@ msgid "rageshake support" msgstr "" #: ../../../CHANGELOG.md:1068 -msgid "" -"Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook" -" can now install and configure the [rageshake](https://github.com/matrix-" -"org/rageshake) bug report server." +msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server." msgstr "" #: ../../../CHANGELOG.md:1070 -msgid "" -"Additional details are available in [Setting up rageshake](docs" -"/configuring-playbook-rageshake.md)." +msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)." msgstr "" #: ../../../CHANGELOG.md:1073 @@ -3336,10 +1938,7 @@ msgid "The playbook can now help you customize Synapse's templates." msgstr "" #: ../../../CHANGELOG.md:1079 -msgid "" -"Additional details are available in the [Customizing templates](docs" -"/configuring-playbook-synapse.md#customizing-templates) section of our " -"Synapse documentation." +msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation." msgstr "" #: ../../../CHANGELOG.md:1081 @@ -3347,27 +1946,15 @@ msgid "The matrix-redis role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1083 -msgid "" -"**TLDR**: the `matrix-redis` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1085 -msgid "" -"The `matrix-redis` role (which configures [Redis](https://redis.io/)) has" -" been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"redis). This makes it possible to easily use it in other Ansible " -"playbooks." +msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1087 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Ntfy or not. If you're making use " -"of Ntfy via this playbook, you will need to update variable references in" -" your `vars.yml` file (`matrix_redis_` -> `redis_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)." msgstr "" #: ../../../CHANGELOG.md:1089 @@ -3375,26 +1962,15 @@ msgid "The matrix-ntfy role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1091 -msgid "" -"**TLDR**: the `matrix-ntfy` role is now included from another repository." -" Some variables have been renamed. All functionality remains intact." +msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1093 -msgid "" -"The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has " -"been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"ntfy). This makes it possible to easily use it in other Ansible " -"playbooks." +msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1095 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Ntfy or not. If you're making use " -"of Ntfy via this playbook, you will need to update variable references in" -" your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)." msgstr "" #: ../../../CHANGELOG.md:1098 @@ -3406,27 +1982,15 @@ msgid "The matrix-grafana role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1102 -msgid "" -"**TLDR**: the `matrix-grafana` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1104 -msgid "" -"The `matrix-grafana` role (which configures [Grafana](docs/configuring-" -"playbook-prometheus-grafana.md)) has been extracted from the playbook and" -" now lives in its [own repository](https://github.com/mother-of-all-self-" -"hosting/ansible-role-grafana). This makes it possible to easily use it in" -" other Ansible playbooks." +msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks." msgstr "" #: ../../../CHANGELOG.md:1106 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Grafana or not. If you're making " -"use of Grafana via this playbook, you will need to update variable " -"references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)." msgstr "" #: ../../../CHANGELOG.md:1109 @@ -3438,31 +2002,15 @@ msgid "The matrix-backup-borg role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1113 -msgid "" -"**TLDR**: the `matrix-backup-borg` role is now included from another " -"repository. Some variables have been renamed. All functionality remains " -"intact." +msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1115 -msgid "" -"Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` " -"role (which configures [BorgBackup](docs/configuring-playbook-backup-" -"borg.md)) has been extracted from the playbook and now lives in its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"backup_borg). This makes it possible to easily use it in other Ansible " -"playbooks and will become part of [nextcloud-docker-ansible-" -"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) " -"soon." +msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon." msgstr "" #: ../../../CHANGELOG.md:1117 -msgid "" -"You need to **update your roles** (`just roles` or `make roles`) " -"regardless of whether you're enabling Borg's backup functionality or not." -" If you're making use of BorgBackup via this playbook, you will need to " -"update variable references in your `vars.yml` file (`matrix_backup_borg_`" -" -> `backup_borg_`)." +msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)." msgstr "" #: ../../../CHANGELOG.md:1120 @@ -3470,9 +2018,7 @@ msgid "2023-02-12" msgstr "" #: ../../../CHANGELOG.md:1122 -msgid "" -"(Backward Compatibility) Reverse-proxy configuration changes and initial " -"Traefik support" +msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support" msgstr "" #: ../../../CHANGELOG.md:1124 @@ -3480,44 +2026,23 @@ msgid "**TLDR**:" msgstr "" #: ../../../CHANGELOG.md:1126 -msgid "" -"there's a new `matrix_playbook_reverse_proxy_type` variable (see " -"[roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-" -"base/defaults/main.yml)), which lets you tell the playbook what reverse-" -"proxy setup you'd like to have. This makes it easier for people who want " -"to do reverse-proxying in other ways." +msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways." msgstr "" #: ../../../CHANGELOG.md:1127 -msgid "" -"the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still" -" `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing" -" `matrix-nginx-proxy` users should not observe any changes** and can stay" -" on this for now." +msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now." msgstr "" #: ../../../CHANGELOG.md:1128 -msgid "" -"**Users who use their [own other webserver](docs/configuring-playbook-" -"own-webserver.md) (e.g. Apache, etc.) need to change** " -"`matrix_playbook_reverse_proxy_type` to something like `other-on-same-" -"host`, `other-on-another-host` or `other-nginx-non-container`" +msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`" msgstr "" #: ../../../CHANGELOG.md:1129 -msgid "" -"we now have **optional [Traefik](https://traefik.io/) support**, so you " -"could easily host Matrix and other Traefik-native services in containers " -"on the same server. Traefik support is still experimental (albeit, good " -"enough) and will improve over time. It does work, but certain esoteric " -"features may not be there yet." +msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet." msgstr "" #: ../../../CHANGELOG.md:1130 -msgid "" -"**Traefik will become the default reverse-proxy in the near future**. " -"`matrix-nginx-proxy` will either remain as an option, or be completely " -"removed to simplify the playbook" +msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook" msgstr "" #: ../../../CHANGELOG.md:1132 @@ -3525,157 +2050,67 @@ msgid "Motivation for redoing our reverse-proxy setup" msgstr "" #: ../../../CHANGELOG.md:1134 -msgid "" -"The playbook has supported various reverse-proxy setups for a long time. " -"We have various configuration variables (`matrix_nginx_proxy_enabled`, " -"various `_host_bind_port` variables, etc.) which allow the playbook to " -"adapt to these different setups. The whole situation was messy though - " -"hard to figure out and with lots of variables to toggle to make things " -"work as you'd expect - huge **operational complexity**." +msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**." msgstr "" #: ../../../CHANGELOG.md:1136 -msgid "" -"We love containers, proven by the fact that **everything** that this " -"playbook manages runs in a container. Yet, we weren't allowing people to " -"easily host other web-exposed containers alongside Matrix services on the" -" same server. We were using `matrix-nginx-proxy` (our integrated " -"[nginx](https://nginx.org/) server), which was handling web-exposure and " -"SSL termination for our own services, but we **weren't helping you with " -"all your other containers**." +msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**." msgstr "" #: ../../../CHANGELOG.md:1138 -msgid "" -"People who were **using `matrix-nginx-proxy`** were on the happy path on " -"which everything worked well by default (Matrix-wise), **but** could not " -"easily run other web-exposed services on their Matrix server because " -"`matrix-nginx-proxy` was occupying ports `80` and `443`. Other services " -"which wanted to get web exposure either had to be plugged into `matrix-" -"nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-" -"nginx-proxy` in favor of something else." +msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else." msgstr "" #: ../../../CHANGELOG.md:1140 -msgid "" -"Of those that decided to forgo `matrix-nginx-proxy`, many were **using " -"nginx** on the same server without a container. This was likely some " -"ancient nginx version, depending on your choice of distro. The Matrix " -"playbook was trying to be helpful and even with " -"`matrix_nginx_proxy_enabled: false` was still generating nginx " -"configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files " -"were adapted for inclusion into an nginx server running locally. " -"Disabling the `matrix-nginx-proxy` role like this, yet still having it " -"produce files is a bit disgusting, but it's what we've had since the " -"early beginnings of this playbook." +msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook." msgstr "" #: ../../../CHANGELOG.md:1142 -msgid "" -"Others still, wanted to run Matrix locally (no SSL certificates), " -"regardless of which web server technology this relied on, and then " -"**reverse-proxy from another machine on the network** which was doing SSL" -" termination. These people were:" +msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:" msgstr "" #: ../../../CHANGELOG.md:1144 -msgid "" -"*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined" -" with exposing services manually (setting `_bind_port` variables)" +msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)" msgstr "" #: ../../../CHANGELOG.md:1145 -msgid "" -"*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in " -"`http`-only mode (no SSL certificate retrieval)." +msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)." msgstr "" #: ../../../CHANGELOG.md:1147 -msgid "" -"Despite this operational complexity, things worked and were reasonably " -"flexible to adapt to all these situations." +msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations." msgstr "" #: ../../../CHANGELOG.md:1149 -msgid "" -"When using `matrix-nginx-proxy` as is, we still had another problem - one" -" of **internal playbook complexity**. Too many services need to be web-" -"exposed (port 80/443, SSL certificates). Because of this, they all had to" -" integrate with the `matrix-nginx-proxy` role. Tens of different roles " -"explicitly integrating with `matrix-nginx-proxy` is not what we call " -"clean. The `matrix-nginx-proxy` role contains variables for many of these" -" roles (yikes). Other roles were more decoupled from it and were " -"injecting configuration into `matrix-nginx-proxy` at runtime - see all " -"the `inject_into_nginx_proxy.yml` task files in this playbook (more " -"decoupled, but still.. yikes)." +msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)." msgstr "" #: ../../../CHANGELOG.md:1151 -msgid "" -"The next problem is one of **efficiency, interoperability and cost-" -"saving**. We're working on other playbooks:" +msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:" msgstr "" #: ../../../CHANGELOG.md:1153 -msgid "" -"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" -"/vaultwarden-docker-ansible-deploy) for hosting the " -"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an " -"alternative implementation of the [Bitwarden](https://bitwarden.com/) " -"password manager" +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager" msgstr "" #: ../../../CHANGELOG.md:1154 -msgid "" -"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source " -"code hosting service" +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service" msgstr "" #: ../../../CHANGELOG.md:1155 -msgid "" -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy) - for hosting the " -"[Nextcloud](https://nextcloud.com/) groupware platform" +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform" msgstr "" #: ../../../CHANGELOG.md:1157 -msgid "" -"We'd love for users to be able to **seamlessly use all these playbooks " -"(and others, even) against a single server**. We don't want `matrix-" -"nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for " -"other services to join in on the party. Such a thing forces people into " -"running multiple servers (one for each service), which does provide nice " -"security benefits, but is costly and ineffiecient. We'd like to make " -"self-hosting these services cheap and easy." +msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy." msgstr "" #: ../../../CHANGELOG.md:1159 -msgid "" -"These other playbooks have been using [Traefik](https://traefik.io/) as " -"their default reverse-proxy for a long time. They can all coexist nicely " -"together (as an example, see the " -"[Interoperability](https://github.com/spantaleev/nextcloud-docker-" -"ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md)" -" documentation for the [Nextcloud playbook](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining " -"Traefik support, it will be able to interoperate with them. If you're " -"going this way, make sure to have the Matrix playbook install Traefik and" -" have the others use `*_reverse_proxy_type: other-traefik-container`." +msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`." msgstr "" #: ../../../CHANGELOG.md:1161 -msgid "" -"Finally, at [etke.cc - a managed Matrix server hosting " -"service](https://etke.cc) (built on top of this playbook, and " -"coincidentally [turning 2 years old today](https://etke.cc/news" -"/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people " -"to host some additional services besides Matrix components. Exposing " -"these services to the web requires ugly hacks and configuration files " -"being dropped into `/matrix/nginx-proxy/conf.d`. We believe that " -"everything should run in independent containers and be exposed to the web" -" via a Traefik server, without a huge Ansible role like `matrix-nginx-" -"proxy` that everything else needs to integrate with." +msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with." msgstr "" #: ../../../CHANGELOG.md:1163 @@ -3683,50 +2118,27 @@ msgid "How do these changes fix all these problems?" msgstr "" #: ../../../CHANGELOG.md:1165 -msgid "" -"The new `matrix_playbook_reverse_proxy_type` lets you easily specify your" -" preferred reverse-proxy type, including `other-on-same-host`, `other-on-" -"another-host` and `none`, so people who'd like to reverse-proxy with " -"their own web server have more options now." +msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now." msgstr "" #: ../../../CHANGELOG.md:1167 -msgid "" -"Using Traefik greatly simplifies things, so going forward we'll have a " -"simpler and easier to maintain playbook, which is also interoperable with" -" other services." +msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services." msgstr "" #: ../../../CHANGELOG.md:1169 -msgid "" -"Traefik is a web server, which has been specifically **designed for " -"reverse-proxying to services running in containers**. It's ideal for " -"usage in an Ansible playbook which runs everything in containers." +msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers." msgstr "" #: ../../../CHANGELOG.md:1171 -msgid "" -"**Traefik obtains SSL certificates automatically**, so there's no need " -"for plugging additional tools like [Certbot](https://certbot.eff.org/) " -"into your web server (like we were doing in the `matrix-nginx-proxy` " -"role). No more certificate renewal timers, web server reloading timers, " -"etc. It's just simpler." +msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler." msgstr "" #: ../../../CHANGELOG.md:1173 -msgid "" -"Traefik is a **modern web server**. " -"[HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is " -"supported already (experimentally) and will move to stable soon, in the " -"upcoming Traefik v3 release." +msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release." msgstr "" #: ../../../CHANGELOG.md:1175 -msgid "" -"Traefik does not lock important functionality we'd like to use into [plus" -" packages like nginx does](https://www.nginx.com/products/nginx/), " -"leading us to resolve to configuration workarounds. The default Traefik " -"package is good enough as it is." +msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is." msgstr "" #: ../../../CHANGELOG.md:1177 @@ -3734,29 +2146,15 @@ msgid "Where we're at right now?" msgstr "" #: ../../../CHANGELOG.md:1179 -msgid "" -"`matrix_playbook_reverse_proxy_type` still defaults to a value of " -"`playbook-managed-nginx`." +msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`." msgstr "" #: ../../../CHANGELOG.md:1181 -msgid "" -"Unless we have some regression, **existing `matrix-nginx-proxy` users " -"should be able to update their Matrix server and not observe any " -"changes**. Their setup should still remain on nginx and everything should" -" still work as expected." +msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected." msgstr "" #: ../../../CHANGELOG.md:1183 -msgid "" -"**Users using [their own webservers](docs/configuring-playbook-own-" -"webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** " -"to something like `other-on-same-host`, `other-on-another-host` or " -"`other-nginx-non-container`. Previously, they could toggle " -"`matrix_nginx_proxy_enabled` to `false`, and that made the playbook " -"automatically expose services locally. Currently, we only do this if you " -"change the reverse-proxy type to `other-on-same-host`, `other-on-another-" -"host` or `other-nginx-non-container`." +msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`." msgstr "" #: ../../../CHANGELOG.md:1185 @@ -3764,62 +2162,31 @@ msgid "How do I explicitly switch to Traefik right now?" msgstr "" #: ../../../CHANGELOG.md:1187 -msgid "" -"**Users who wish to migrate to Traefik** today, can do so by **adding** " -"this to their configuration:" +msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:" msgstr "" #: ../../../CHANGELOG.md:1195 -msgid "" -"You may still need to keep certain old `matrix_nginx_proxy_*` variables " -"(like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using " -"Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` " -"variables just in case. In the future, reliance on `matrix-nginx-proxy` " -"will be removed." +msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed." msgstr "" #: ../../../CHANGELOG.md:1197 -msgid "" -"Switching to Traefik will obtain new SSL certificates from Let's Encrypt " -"(stored in `/matrix/traefik/ssl/acme.json`). **The switch is " -"reversible**. You can always go back to `playbook-managed-nginx` if " -"Traefik is causing you trouble." +msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble." msgstr "" #: ../../../CHANGELOG.md:1199 -msgid "" -"**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik " -"and nginx will uninstall the Traefik role and all of its data (under " -"`/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you" -" do it often." +msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often." msgstr "" #: ../../../CHANGELOG.md:1201 -msgid "" -"Treafik directly reverse-proxies to **some** services right now, but for " -"most other services it goes through `matrix-nginx-proxy` (e.g. Traefik ->" -" `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, " -"even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being" -" installed in local-only mode. This will improve with time." +msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time." msgstr "" #: ../../../CHANGELOG.md:1203 -msgid "" -"Some services (like [Coturn](docs/configuring-playbook-turn.md) and " -"[Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be " -"reverse-proxied to directly from Traefik, so they require direct access " -"to SSL certificate files extracted out of Traefik. The playbook does this" -" automatically thanks to a new " -"[com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper)" -" role utilizing the [traefik-certs-dumper](https://github.com/ldez" -"/traefik-certs-dumper) tool." +msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool." msgstr "" #: ../../../CHANGELOG.md:1205 -msgid "" -"Our Traefik setup mostly works, but certain esoteric features may not " -"work. If you have a default setup, we expect you to have a good " -"experience." +msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience." msgstr "" #: ../../../CHANGELOG.md:1207 @@ -3827,15 +2194,7 @@ msgid "Where we're going in the near future?" msgstr "" #: ../../../CHANGELOG.md:1209 -msgid "" -"The `matrix-nginx-proxy` role is quite messy. It manages both nginx and " -"Certbot and its certificate renewal scripts and timers. It generates " -"configuration even when the role is disabled (weird). Although it doesn't" -" directly reach into variables from other roles, it has explicit " -"awareness of various other services that it reverse-proxies to " -"(`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-" -"ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is " -"probably to just get rid of the whole thing at some point." +msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point." msgstr "" #: ../../../CHANGELOG.md:1211 @@ -3843,44 +2202,19 @@ msgid "For now, `matrix-nginx-proxy` will stay around." msgstr "" #: ../../../CHANGELOG.md:1213 -msgid "" -"As mentioned above, Traefik still reverse-proxies to some (most) services" -" by going through a local-only `matrix-nginx-proxy` server. This has " -"allowed us to add Traefik support to the playbook early on (without " -"having to rework all services), but is not the final goal. We'll **work " -"on making each service support Traefik natively**, so that traffic will " -"not need to go through `matrix-nginx-proxy` anymore. In the end, choosing" -" Traefik should only give you a pure Traefik installation with no " -"`matrix-nginx-proxy` in sight." +msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight." msgstr "" #: ../../../CHANGELOG.md:1215 -msgid "" -"As Traefik support becomes complete and proves to be stable for a while, " -"especially as a playbook default, we will **most likely remove `matrix-" -"nginx-proxy` completely**. It will likely be some months before this " -"happens though. Keeping support for both Traefik and nginx in the " -"playbook will be a burden, especially with most of us running Traefik in " -"the future. The Traefik role should do everything nginx does in a better " -"and cleaner way. Users who use their own `nginx` server on the Matrix " -"server will be inconvenienced, as nothing will generate ready-to-include " -"nginx configuration for them. Still, we hope it won't be too hard to " -"migrate their setup to another way of doing things, like:" +msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:" msgstr "" #: ../../../CHANGELOG.md:1217 -msgid "" -"not using nginx anymore. A common reason for using nginx until now was " -"that you were running other containers and you need your own nginx to " -"reverse-proxy to all of them. Just switch them to Traefik as well." +msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well." msgstr "" #: ../../../CHANGELOG.md:1218 -msgid "" -"running Traefik in local-only mode " -"(`traefik_config_entrypoint_web_secure_enabled: false`) and using some " -"nginx configuration which reverse-proxies to Traefik (we should introduce" -" examples for this in `examples/nginx`)." +msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)." msgstr "" #: ../../../CHANGELOG.md:1220 @@ -3892,32 +2226,15 @@ msgid "You can help by:" msgstr "" #: ../../../CHANGELOG.md:1224 -msgid "" -"**explicitly switching your server to Traefik** right now (see example " -"configuration in [How do I explicitly switch to Traefik right now?](#how-" -"do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting " -"troubles" +msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles" msgstr "" #: ../../../CHANGELOG.md:1226 -msgid "" -"**adding native Traefik support to a role** (requires adding Traefik " -"labels, etc.) - for inspiration, see these roles " -"([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting" -"/ansible-role-prometheus-node-exporter), " -"[prometheus_postgres_exporter](https://github.com/mother-of-all-self-" -"hosting/ansible-role-prometheus-postgres-exporter)) and how they're " -"hooked into the playbook via " -"[group_vars/matrix_servers](group_vars/matrix_servers)." +msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)." msgstr "" #: ../../../CHANGELOG.md:1228 -msgid "" -"**adding reverse-proxying examples for nginx users** in `examples/nginx`." -" People who insist on using their own `nginx` server on the same Matrix " -"host, can run Traefik in local-only mode " -"(`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy" -" to the Traefik server" +msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server" msgstr "" #: ../../../CHANGELOG.md:1231 @@ -3929,18 +2246,11 @@ msgid "Matrix Authentication Support for Jitsi" msgstr "" #: ../../../CHANGELOG.md:1235 -msgid "" -"Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk " -"gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for " -"authentication (via [Matrix User Verification Service](https://github.com" -"/matrix-org/matrix-user-verification-service))." +msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))." msgstr "" #: ../../../CHANGELOG.md:1237 -msgid "" -"Additional details are available in the [Authenticate using Matrix OpenID" -" (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-" -"using-matrix-openid-auth-type-matrix)." +msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)." msgstr "" #: ../../../CHANGELOG.md:1239 @@ -3948,19 +2258,11 @@ msgid "Draupnir moderation tool (bot) support" msgstr "" #: ../../../CHANGELOG.md:1241 -msgid "" -"Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now " -"install and configure the [Draupnir](https://github.com/the-draupnir-" -"project/Draupnir) moderation tool (bot). Draupnir is a fork of " -"[Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook " -"has supported for a long time) maintained by Mjolnir's former lead " -"developer." +msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer." msgstr "" #: ../../../CHANGELOG.md:1243 -msgid "" -"Additional details are available in [Setting up Draupnir](docs" -"/configuring-playbook-bot-draupnir.md)." +msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)." msgstr "" #: ../../../CHANGELOG.md:1246 @@ -3972,43 +2274,23 @@ msgid "The matrix-prometheus-postgres-exporter role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1250 -msgid "" -"**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included " -"from another repository. Some variables have been renamed. All " -"functionality remains intact." +msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1252 -msgid "" -"The `matrix-prometheus-postgres-exporter` role (which configures " -"[Prometheus Postgres Exporter](https://github.com/prometheus-" -"community/postgres_exporter)) has been extracted from the playbook and " -"now lives in its own repository at https://github.com/mother-of-all-self-" -"hosting/ansible-role-prometheus-postgres-exporter" +msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter" msgstr "" #: ../../../CHANGELOG.md:1254 -msgid "" -"It's still part of the playbook, but is now installed via `ansible-" -"galaxy` (by running `just roles` / `make roles`). Some variables have " -"been renamed (`matrix_prometheus_postgres_exporter_` -> " -"`prometheus_postgres_exporter_`, etc.). The playbook will report all " -"variables that you need to rename to get upgraded. All functionality " -"remains intact." +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1256 -msgid "" -"The `matrix-prometheus-services-proxy-connect` role has bee adjusted to " -"help integrate the new `prometheus_postgres_exporter` role with our own " -"services (`matrix-nginx-proxy`)" +msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)" msgstr "" #: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300 -msgid "" -"Other roles which aren't strictly related to Matrix are likely to follow " -"this fate of moving to their own repositories. Extracting them out allows" -" other Ansible playbooks to make use of these roles easily." +msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily." msgstr "" #: ../../../CHANGELOG.md:1261 @@ -4020,79 +2302,39 @@ msgid "Coturn can now use host-networking" msgstr "" #: ../../../CHANGELOG.md:1265 -msgid "" -"Large Coturn deployments (with a huge range of ports specified via " -"`matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) " -"experience a huge slowdown with how Docker publishes all these ports " -"(setting up firewall forwarding rules), which leads to a very slow Coturn" -" service startup and shutdown." +msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown." msgstr "" #: ../../../CHANGELOG.md:1267 -msgid "" -"Such deployments don't need to run Coturn within a private container " -"network anymore. Coturn can now run with host-networking by using " -"configuration like this:" +msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:" msgstr "" #: ../../../CHANGELOG.md:1273 -msgid "" -"With such a configuration, **Docker no longer needs to configure " -"thousands of firewall forwarding rules** each time Coturn starts and " -"stops. This, however, means that **you will need to ensure these ports " -"are open** in your firewall yourself." +msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself." msgstr "" #: ../../../CHANGELOG.md:1275 -msgid "" -"Thanks to us [tightening Coturn security](#backward-compatibility-" -"tightening-coturn-security-can-lead-to-connectivity-issues), running " -"Coturn with host-networking should be safe and not expose neither other " -"services running on the host, nor other services running on the local " -"network." +msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network." msgstr "" #: ../../../CHANGELOG.md:1277 -msgid "" -"(Backward Compatibility) Tightening Coturn security can lead to " -"connectivity issues" +msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues" msgstr "" #: ../../../CHANGELOG.md:1279 -msgid "" -"**TLDR**: users who run and access their Matrix server on a private " -"network (likely a small minority of users) may experience connectivity " -"issues with our new default Coturn blocklists. They may need to override " -"`matrix_coturn_denied_peer_ips` and remove some IP ranges from it." +msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it." msgstr "" #: ../../../CHANGELOG.md:1281 -msgid "" -"Inspired by [this security " -"article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-" -"access-control-protection/), we've decided to make use of Coturn's " -"`denied-peer-ip` functionality to prevent relaying network traffic to " -"certain private IP subnets. This ensures that your Coturn server won't " -"accidentally try to forward traffic to certain services running on your " -"local networks. We run Coturn in a container and in a private container " -"network by default, which should prevent such access anyway, but having " -"additional block layers in place is better." +msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better." msgstr "" #: ../../../CHANGELOG.md:1283 -msgid "" -"If you access your Matrix server from a local network and need Coturn to " -"relay to private IP addresses, you may observe that relaying is now " -"blocked due to our new default `denied-peer-ip` lists (specified in " -"`matrix_coturn_denied_peer_ips`). If you experience such connectivity " -"problems, consider overriding this setting in your `vars.yml` file and " -"removing certain networks from it." +msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it." msgstr "" #: ../../../CHANGELOG.md:1285 -msgid "" -"We've also added `no-multicast-peers` to the default Coturn " -"configuration, but we don't expect this to cause trouble for most people." +msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people." msgstr "" #: ../../../CHANGELOG.md:1288 @@ -4104,36 +2346,19 @@ msgid "The matrix-prometheus-node-exporter role lives independently now" msgstr "" #: ../../../CHANGELOG.md:1292 -msgid "" -"**TLDR**: the `matrix-prometheus-node-exporter` role is now included from" -" another repository. Some variables have been renamed. All functionality " -"remains intact." +msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1294 -msgid "" -"The `matrix-prometheus-node-exporter` role (which configures [Prometheus " -"node exporter](https://github.com/prometheus/node_exporter)) has been " -"extracted from the playbook and now lives in its own repository at " -"https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-" -"node-exporter" +msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter" msgstr "" #: ../../../CHANGELOG.md:1296 -msgid "" -"It's still part of the playbook, but is now installed via `ansible-" -"galaxy` (by running `just roles` / `make roles`). Some variables have " -"been renamed (`matrix_prometheus_node_exporter_` -> " -"`prometheus_node_exporter_`, etc.). The playbook will report all " -"variables that you need to rename to get upgraded. All functionality " -"remains intact." +msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact." msgstr "" #: ../../../CHANGELOG.md:1298 -msgid "" -"A new `matrix-prometheus-services-proxy-connect` role was added to the " -"playbook to help integrate the new `prometheus_node_exporter` role with " -"our own services (`matrix-nginx-proxy`)" +msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)" msgstr "" #: ../../../CHANGELOG.md:1303 @@ -4145,46 +2370,27 @@ msgid "Support for running commands via just" msgstr "" #: ../../../CHANGELOG.md:1307 -msgid "" -"We've previously used [make](https://www.gnu.org/software/make/) for " -"easily running some playbook commands (e.g. `make roles` which triggers " -"`ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still " -"around and you can still run these commands." +msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands." msgstr "" #: ../../../CHANGELOG.md:1309 -msgid "" -"In addition, we've added support for running commands via " -"[just](https://github.com/casey/just) - a more modern command-runner " -"alternative to `make`. Instead of `make roles`, you can now run `just " -"roles` to accomplish the same." +msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same." msgstr "" #: ../../../CHANGELOG.md:1311 -msgid "" -"Our [justfile](justfile) already defines some additional helpful " -"**shortcut** commands that weren't part of our `Makefile`. Here are some " -"examples:" +msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:" msgstr "" #: ../../../CHANGELOG.md:1313 -msgid "" -"`just install-all` to trigger the much longer `ansible-playbook -i " -"inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-" -"created,start` command" +msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command" msgstr "" #: ../../../CHANGELOG.md:1314 -msgid "" -"`just install-all --ask-vault-pass` - commands also support additional " -"arguments (`--ask-vault-pass` will be appended to the above installation " -"command)" +msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)" msgstr "" #: ../../../CHANGELOG.md:1315 -msgid "" -"`just run-tags install-mautrix-slack,start` - to run specific playbook " -"tags" +msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags" msgstr "" #: ../../../CHANGELOG.md:1316 @@ -4196,9 +2402,7 @@ msgid "`just stop-group postgres` - to stop only the Postgres service" msgstr "" #: ../../../CHANGELOG.md:1318 -msgid "" -"`just register-user alice secret-password yes` - registers an `alice` " -"user with the `secret-password` password and admin access (admin = `yes`)" +msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" #: ../../../CHANGELOG.md:1320 @@ -4206,10 +2410,7 @@ msgid "Additional helpful commands and shortcuts may be defined in the future." msgstr "" #: ../../../CHANGELOG.md:1322 -msgid "" -"This is all completely optional. If you find it difficult to [install " -"`just`](https://github.com/casey/just#installation) or don't find any of " -"this convenient, feel free to run all commands manually." +msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually." msgstr "" #: ../../../CHANGELOG.md:1325 @@ -4221,21 +2422,11 @@ msgid "mautrix-slack support" msgstr "" #: ../../../CHANGELOG.md:1329 -msgid "" -"Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the " -"playbook now supports bridging to [Slack](https://slack.com/) via the " -"[mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting " -"up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-" -"slack.md) documentation page for getting started." +msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:1331 -msgid "" -"**Note**: this is a new Slack bridge. The playbook still retains Slack " -"bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-" -"appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-" -"bridge-mx-puppet-slack.md). You're free to use the bridge that serves you" -" better, or even all three of them (for different users and use-cases)." +msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:1334 @@ -4247,18 +2438,11 @@ msgid "ChatGPT support" msgstr "" #: ../../../CHANGELOG.md:1338 -msgid "" -"Thanks to [@bertybuttface](https://github.com/bertybuttface), the " -"playbook can now help you set up [matrix-chatgpt-" -"bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through " -"which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) " -"model." +msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model." msgstr "" #: ../../../CHANGELOG.md:1340 -msgid "" -"See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-" -"chatgpt.md) documentation to get started." +msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1343 @@ -4266,25 +2450,15 @@ msgid "2022-11-30" msgstr "" #: ../../../CHANGELOG.md:1345 -msgid "" -"matrix-postgres-backup has been replaced by the ansible-role-postgres-" -"backup external role" +msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role" msgstr "" #: ../../../CHANGELOG.md:1347 -msgid "" -"Just like we've [replaced Postgres with an external role](#matrix-" -"postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-" -"role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an" -" external role - " -"[com.devture.ansible.role.postgres_backup](https://github.com/mother-of-" -"all-self-hosting/ansible-role-postgres_backup)." +msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)." msgstr "" #: ../../../CHANGELOG.md:1349 -msgid "" -"You'll need to rename your `matrix_postgres_backup`-prefixed variables " -"such that they use a `postgres_backup` prefix." +msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix." msgstr "" #: ../../../CHANGELOG.md:1352 @@ -4292,66 +2466,35 @@ msgid "2022-11-28" msgstr "" #: ../../../CHANGELOG.md:1354 -msgid "" -"matrix-postgres has been replaced by the ansible-role-postgres external " -"role" +msgid "matrix-postgres has been replaced by the ansible-role-postgres external role" msgstr "" #: ../../../CHANGELOG.md:1356 -msgid "" -"**TLDR**: the tasks that install the integrated Postgres server now live " -"in an external role - [ansible-role-postgres](https://github.com/mother-" -"of-all-self-hosting/ansible-role-postgres). You'll need to run `make " -"roles` to install it, and to also rename your `matrix_postgres`-prefixed " -"variables to use a `devture_postgres` prefix (e.g. " -"`matrix_postgres_connection_password` -> `postgres_connection_password`)." -" All your data will still be there! Some scripts have moved " -"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." +msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)." msgstr "" #: ../../../CHANGELOG.md:1358 -msgid "" -"The `matrix-postgres` role that has been part of the playbook for a long " -"time has been replaced with the [ansible-role-" -"postgres](https://github.com/mother-of-all-self-hosting/ansible-role-" -"postgres) role. This was done as part of our work to [use external roles " -"for some things](#the-playbook-now-uses-external-roles-for-some-things) " -"for better code re-use and maintainability." +msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability." msgstr "" #: ../../../CHANGELOG.md:1360 -msgid "" -"The new role is an upgraded version of the old `matrix-postgres` role " -"with these notable differences:" +msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:" msgstr "" #: ../../../CHANGELOG.md:1362 -msgid "" -"it uses different names for its variables (`matrix_postgres` -> " -"`devture_postgres`)" +msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)" msgstr "" #: ../../../CHANGELOG.md:1363 -msgid "" -"when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-" -"postgresql), it will vacuum all your databases, not just the Synapse one" +msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one" msgstr "" #: ../../../CHANGELOG.md:1365 -msgid "" -"You'll need to run `make roles` to install the new role. You would also " -"need to rename your `matrix_postgres`-prefixed variables to use a " -"`devture_postgres` prefix." +msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix." msgstr "" #: ../../../CHANGELOG.md:1367 -msgid "" -"Note: the systemd service still remains the same - `matrix-" -"postgres.service`. Your data will still be in `/matrix/postgres`, etc. " -"Postgres-related scripts will be moved to `/matrix/postgres/bin` " -"(`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, " -"etc). Also see [The playbook no longer installs scripts in /usr/local/bin" -"](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." +msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)." msgstr "" #: ../../../CHANGELOG.md:1369 @@ -4363,10 +2506,7 @@ msgid "The locations of various scripts installed by the playbook have changed." msgstr "" #: ../../../CHANGELOG.md:1373 -msgid "" -"The playbook no longer contaminates your `/usr/local/bin` directory. All " -"scripts installed by the playbook now live in `bin/` directories under " -"`/matrix`. Some examples are below:" +msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:" msgstr "" #: ../../../CHANGELOG.md:1375 @@ -4378,15 +2518,11 @@ msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" msgstr "" #: ../../../CHANGELOG.md:1377 -msgid "" -"`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> " -"`/matrix/ssl/bin/lets-encrypt-certificates-renew`" +msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`" msgstr "" #: ../../../CHANGELOG.md:1378 -msgid "" -"`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin" -"/register-user`" +msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`" msgstr "" #: ../../../CHANGELOG.md:1381 @@ -4398,79 +2534,35 @@ msgid "2x-5x performance improvements in playbook runtime" msgstr "" #: ../../../CHANGELOG.md:1385 -msgid "" -"**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and " -"various other tags). It also has new `--tags=install-*` tags (like " -"`--tags=install-all`), which skip uninstallation tasks and bring an " -"additional 2.5x speedup. In total, the playbook can maintain your server " -"5 times faster." +msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster." msgstr "" #: ../../../CHANGELOG.md:1387 -msgid "" -"Our [etke.cc managed Matrix hosting service](https://etke.cc) runs " -"maintenance against hundreds of servers, so the playbook being fast means" -" a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible)" -" (which is an extension of this one) is growing to support more and more " -"services (besides just Matrix), so the Matrix playbook being leaner " -"prevents runtimes from becoming too slow and improves the customer " -"experience." +msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience." msgstr "" #: ../../../CHANGELOG.md:1389 -msgid "" -"Even when running `ansible-playbook` manually (as most of us here do), " -"it's beneficial not to waste time and CPU resources." +msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources." msgstr "" #: ../../../CHANGELOG.md:1391 -msgid "" -"Recently, a few large optimizations have been done to this playbook and " -"its external roles (see [The playbook now uses external roles for some " -"things](#the-playbook-now-uses-external-roles-for-some-things) and don't " -"forget to run `make roles`):" +msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):" msgstr "" #: ../../../CHANGELOG.md:1393 -msgid "" -"Replacing Ansible `import_tasks` calls with `include_tasks`, which " -"decreased runtime in half. Using `import_tasks` is slower and causes " -"Ansible to go through and skip way too many tasks (tasks which could have" -" been skipped altogether by not having Ansible include them in the first " -"place). On an experimental VM, **deployment time was decreased from ~530 " -"seconds to ~250 seconds**." +msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**." msgstr "" #: ../../../CHANGELOG.md:1395 -msgid "" -"Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, " -"e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible " -"tasks pertaining to installation, while skipping uninstallation tasks. In" -" most cases, people are maintaining the same setup or they're *adding* " -"new components. Removing components is rare. Running thousands of " -"uninstallation tasks each time is wasteful. On an experimental VM, " -"**deployment time was decreased from ~250 seconds (`--tags=setup-all`) to" -" ~100 seconds (`--tags=install-all`)**." +msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**." msgstr "" #: ../../../CHANGELOG.md:1397 -msgid "" -"You can still use `--tags=setup-all`. In fact, that's the best way to " -"ensure your server is reconciled with the `vars.yml` configuration." +msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration." msgstr "" #: ../../../CHANGELOG.md:1399 -msgid "" -"If you know you haven't uninstalled any services since the last time you " -"ran the playbook, you could run `--tags=install-all` instead and benefit " -"from quicker runtimes. It should be noted that a service may become " -"\"eligible for uninstallation\" even if your `vars.yml` file remains the " -"same. In rare cases, we toggle services from being auto-installed to " -"being optional, like we did on the 17th of March 2022 when we made [ma1sd" -" not get installed by default](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-" -"identity-server-no-longer-installed-by-default). In such rare cases, " -"you'd also need to run `--tags=setup-all`." +msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`." msgstr "" #: ../../../CHANGELOG.md:1402 @@ -4482,10 +2574,7 @@ msgid "Automatic `matrix_architecture` determination" msgstr "" #: ../../../CHANGELOG.md:1406 -msgid "" -"From now on, the playbook automatically determines your server's " -"architecture and sets the `matrix_architecture` variable accordingly. You" -" no longer need to set this variable manually in your `vars.yml` file." +msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file." msgstr "" #: ../../../CHANGELOG.md:1408 @@ -4493,36 +2582,19 @@ msgid "Docker and the Docker SDK for Python are now installed via external roles msgstr "" #: ../../../CHANGELOG.md:1412 -msgid "" -"Docker will now be installed on the server via the " -"[geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) " -"Ansible role. If you'd like to manage the Docker installation yourself, " -"you can disable the playbook's installation of Docker by setting " -"`matrix_playbook_docker_installation_enabled: false`." +msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`." msgstr "" #: ../../../CHANGELOG.md:1414 -msgid "" -"The Docker SDK for Python (named `docker-python`, `python-docker`, etc. " -"on the different platforms) is now also installed by another role " -"([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python))." -" To disable this role and install the necessary tools yourself, use " -"`devture_docker_sdk_for_python_installation_enabled: false`." +msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`." msgstr "" #: ../../../CHANGELOG.md:1416 -msgid "" -"If you're hitting issues with Docker installation or Docker SDK for " -"Python installation, consider reporting bugs or contributing to these " -"other projects." +msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects." msgstr "" #: ../../../CHANGELOG.md:1418 -msgid "" -"These additional roles are downloaded into the playbook directory (to " -"`roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an " -"easy shortcut for invoking the `ansible-galaxy` command to download these" -" roles." +msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles." msgstr "" #: ../../../CHANGELOG.md:1421 @@ -4530,22 +2602,11 @@ msgid "2022-11-20" msgstr "" #: ../../../CHANGELOG.md:1423 -msgid "" -"(Backward Compatibility Break) Changing how reverse-proxying to Synapse " -"works - now via a `matrix-synapse-reverse-proxy-companion` service" +msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service" msgstr "" #: ../../../CHANGELOG.md:1425 -msgid "" -"**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx " -"service, which helps with reverse-proxying to Synapse and its various " -"worker processes (if workers are enabled), so that `matrix-nginx-proxy` " -"can be relieved of this role. `matrix-nginx-proxy` still remains as the " -"public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-" -"reverse-proxy-companion` is just one more reverse-proxy thrown into the " -"mix for convenience. People with a more custom reverse-proxying " -"configuration may be affected - see [Webserver configuration](#webserver-" -"configuration) below." +msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below." msgstr "" #: ../../../CHANGELOG.md:1427 @@ -4553,26 +2614,11 @@ msgid "Background" msgstr "" #: ../../../CHANGELOG.md:1429 -msgid "" -"Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. " -"When Synapse is running in worker mode, the reverse-proxying " -"configuration is more complicated (different requests need to go to " -"different Synapse worker processes). `matrix-nginx-proxy` had " -"configuration for sending each URL endpoint to the correct Synapse worker" -" responsible for handling it. However, sometimes people like to disable " -"`matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own" -" webserver, instead of this playbook's nginx proxy](docs/configuring-" -"playbook-own-webserver.md)." +msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)." msgstr "" #: ../../../CHANGELOG.md:1431 -msgid "" -"Because `matrix-nginx-proxy` was so central to request forwarding, when " -"it was disabled and Synapse was running with workers enabled, there was " -"nothing which could forward requests to the correct place anymore.. which" -" caused [problems such as this one affecting " -"Dimension](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2090)." +msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)." msgstr "" #: ../../../CHANGELOG.md:1433 @@ -4580,75 +2626,43 @@ msgid "Solution" msgstr "" #: ../../../CHANGELOG.md:1435 -msgid "" -"From now on, `matrix-nginx-proxy` is relieved of its function of reverse-" -"proxying to Synapse and its various worker processes. This role is now " -"handled by the new `matrix-synapse-reverse-proxy-companion` nginx service" -" and works even if `matrix-nginx-proxy` is disabled. The purpose of the " -"new `matrix-synapse-reverse-proxy-companion` service is to:" +msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:" msgstr "" #: ../../../CHANGELOG.md:1437 -msgid "" -"serve as a companion to Synapse and know how to reverse-proxy to Synapse " -"correctly (no matter if workers are enabled or not)" +msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)" msgstr "" #: ../../../CHANGELOG.md:1439 -msgid "" -"provide a unified container address for reaching Synapse (no matter if " -"workers are enabled or not)" +msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)" msgstr "" #: ../../../CHANGELOG.md:1440 -msgid "" -"`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server " -"API traffic" +msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic" msgstr "" #: ../../../CHANGELOG.md:1441 -msgid "" -"`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server " -"(Federation) API traffic" +msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic" msgstr "" #: ../../../CHANGELOG.md:1443 -msgid "" -"simplify `matrix-nginx-proxy` configuration - it now only needs to send " -"requests to `matrix-synapse-reverse-proxy-companion` or `matrix-" -"dendrite`, etc., without having to worry about workers" +msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers" msgstr "" #: ../../../CHANGELOG.md:1445 -msgid "" -"allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is " -"disabled" +msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled" msgstr "" #: ../../../CHANGELOG.md:1447 -msgid "" -"`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-" -"proxy in the playbook. All traffic goes through it before reaching any of" -" the services. It's just that now the Synapse traffic is routed through " -"`matrix-synapse-reverse-proxy-companion` like this:" +msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:" msgstr "" #: ../../../CHANGELOG.md:1449 -msgid "" -"(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> " -"(`matrix-synapse` or some Synapse worker))." +msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))." msgstr "" #: ../../../CHANGELOG.md:1451 -msgid "" -"Various services (like Dimension, etc.) still talk to Synapse via " -"`matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) " -"preferentially. They only talk to Synapse via the reverse-proxy companion" -" (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-" -"nginx-proxy` is disabled. Services should not be talking to Synapse (e.g." -" `https://matrix-synapse:8008` directly anymore), because when workers " -"are enabled, that's the Synapse `master` process and may not be serving " -"all URL endpoints needed by the service." +msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service." msgstr "" #: ../../../CHANGELOG.md:1453 @@ -4656,49 +2670,23 @@ msgid "Webserver configuration" msgstr "" #: ../../../CHANGELOG.md:1455 -msgid "" -"if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`," -" which is the default for the playbook), you don't need to do anything" +msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything" msgstr "" #: ../../../CHANGELOG.md:1457 -msgid "" -"if you're using your own `nginx` webserver running on the server, you " -"shouldn't be affected. The `/matrix/nginx/conf.d` configuration and " -"exposed ports that you're relying on will automatically be updated in a " -"way that should work" +msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work" msgstr "" #: ../../../CHANGELOG.md:1459 -msgid "" -"if you're using another local webserver (e.g. Apache, etc.) and haven't " -"changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't " -"be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and" -" `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed " -"on `127.0.0.1` by default - just not by the `matrix-synapse` container " -"from now on, but by the `matrix-synapse-reverse-proxy-companion` " -"container instead" +msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead" msgstr "" #: ../../../CHANGELOG.md:1461 -msgid "" -"if you've been exposing `matrix-synapse` ports " -"(`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, " -"you should consider exposing `matrix-synapse-reverse-proxy-companion` " -"ports instead" +msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead" msgstr "" #: ../../../CHANGELOG.md:1463 -msgid "" -"if you're running Traefik and reverse-proxying directly to the `matrix-" -"synapse` container, you should start reverse-proxying to the `matrix-" -"synapse-reverse-proxy-companion` container instead. See [our updated " -"Traefik example configuration](docs/configuring-playbook-own-webserver.md" -"#sample-configuration-for-running-behind-traefik-20). Note: we now " -"recommend calling the federation entry point `federation` (instead of " -"`synapse`) and reverse-proxying the federation traffic via `matrix-nginx-" -"proxy`, instead of sending it directly to Synapse (or `matrix-synapse-" -"reverse-proxy-companion`). This makes the configuration simpler." +msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler." msgstr "" #: ../../../CHANGELOG.md:1466 @@ -4710,20 +2698,11 @@ msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad msgstr "" #: ../../../CHANGELOG.md:1470 -msgid "" -"Until now, [Etherpad](https://etherpad.org/) (which [the playbook could " -"install for you](docs/configuring-playbook-etherpad.md)) required the " -"[Dimension integration manager](docs/configuring-playbook-dimension.md) " -"to also be installed, because Etherpad was hosted on the Dimension domain" -" (at `dimension.example.com/etherpad`)." +msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)." msgstr "" #: ../../../CHANGELOG.md:1472 -msgid "" -"From now on, Etherpad can be installed in `standalone` mode on " -"`etherpad.example.com` and used even without Dimension. This is much more" -" versatile, so the playbook now defaults to this new mode " -"(`etherpad_mode: standalone`)." +msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)." msgstr "" #: ../../../CHANGELOG.md:1474 @@ -4731,25 +2710,11 @@ msgid "If you've already got both Etherpad and Dimension in use you could:" msgstr "" #: ../../../CHANGELOG.md:1476 -msgid "" -"**either** keep hosting Etherpad under the Dimension domain by adding " -"`etherpad_mode: dimension` to your `vars.yml` file. All your existing " -"room widgets will continue working at the same URLs and no other changes " -"will be necessary." +msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary." msgstr "" #: ../../../CHANGELOG.md:1478 -msgid "" -"**or**, you could change to hosting Etherpad separately on " -"`etherpad.example.com`. You will need to [configure a DNS record](docs" -"/configuring-dns.md) for this new domain. You will also need to " -"reconfigure Dimension to use the new pad URLs " -"(`https://etherpad.example.com/…`) going forward (refer to our " -"[configuring Etherpad documentation](docs/configuring-playbook-" -"etherpad.md)). All your existing room widgets (which still use " -"`https://dimension.example.com/etherpad/…`) will break as Etherpad is not" -" hosted there anymore. You will need to re-add them or to consider not " -"using `standalone` mode" +msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode" msgstr "" #: ../../../CHANGELOG.md:1481 @@ -4761,19 +2726,11 @@ msgid "The playbook now uses external roles for some things" msgstr "" #: ../../../CHANGELOG.md:1485 -msgid "" -"**TLDR**: when updating the playbook and before running it, you'll need " -"to run `make roles` to make [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"download dependency roles (see the [`requirements.yml` " -"file](requirements.yml)) to the `roles/galaxy` directory. Without this, " -"the playbook won't work." +msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work." msgstr "" #: ../../../CHANGELOG.md:1487 -msgid "" -"We're in the process of trimming the playbook and making it reuse Ansible" -" roles." +msgid "We're in the process of trimming the playbook and making it reuse Ansible roles." msgstr "" #: ../../../CHANGELOG.md:1489 @@ -4785,48 +2742,19 @@ msgid "those that live within the playbook itself (`roles/custom/*`)" msgstr "" #: ../../../CHANGELOG.md:1493 -msgid "" -"those downloaded from other sources (using [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"to `roles/galaxy`, based on the [`requirements.yml` " -"file](requirements.yml)). These roles are maintained by us or by other " -"people from the Ansible community." +msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community." msgstr "" #: ../../../CHANGELOG.md:1495 -msgid "" -"We're doing this for greater code-reuse (across Ansible playbooks, " -"including our own related playbooks [gitea-docker-ansible-" -"deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and " -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. " -"Until now, certain features were copy-pasted across playbooks or were " -"maintained separately in each one, with improvements often falling " -"behind. We've also tended to do too much by ourselves - installing Docker" -" on the server from our `matrix-base` role, etc. - something that we'd " -"rather not do anymore by switching to the " -"[geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." +msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role." msgstr "" #: ../../../CHANGELOG.md:1497 -msgid "" -"Some variable names will change during the transition to having more and " -"more external (galaxy) roles. There's a new " -"`custom/matrix_playbook_migration` role added to the playbook which will " -"tell you about these changes each time you run the playbook." +msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:1499 -msgid "" -"**From now on**, every time you update the playbook (well, every time the" -" `requirements.yml` file changes), it's best to run `make roles` to " -"update the roles downloaded from other sources. `make roles` is a " -"shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed" -" by the [`make`](https://www.gnu.org/software/make/) utility) which " -"ultimately runs [ansible-" -"galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) " -"to download Ansible roles. If you don't have `make`, you can also " -"manually run the commands seen in the `Makefile`." +msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`." msgstr "" #: ../../../CHANGELOG.md:1502 @@ -4838,33 +2766,19 @@ msgid "synapse-s3-storage-provider support" msgstr "" #: ../../../CHANGELOG.md:1506 -msgid "" -"**`synapse-s3-storage-provider` support is very new and still relatively " -"untested. Using it may cause data loss.**" +msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**" msgstr "" #: ../../../CHANGELOG.md:1508 -msgid "" -"You can now store your Synapse media repository files on Amazon S3 (or " -"another S3-compatible object store) using [synapse-s3-storage-" -"provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a " -"media provider for Synapse (Python module), which should work faster and " -"more reliably than our previous [Goofys](docs/configuring-" -"playbook-s3-goofys.md) implementation (Goofys will continue to work)." +msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)." msgstr "" #: ../../../CHANGELOG.md:1510 -msgid "" -"This is not just for initial installations. Users with existing files " -"(stored in the local filesystem) can also migrate their files to " -"`synapse-s3-storage-provider`." +msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`." msgstr "" #: ../../../CHANGELOG.md:1512 -msgid "" -"To get started, see our [Storing Synapse media files on Amazon S3 with " -"synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3" -"-storage-provider.md) documentation." +msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation." msgstr "" #: ../../../CHANGELOG.md:1514 @@ -4872,43 +2786,23 @@ msgid "Synapse container image customization support" msgstr "" #: ../../../CHANGELOG.md:1516 -msgid "" -"We now support customizing the Synapse container image by adding " -"additional build steps to its " -"[`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." +msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)." msgstr "" #: ../../../CHANGELOG.md:1518 -msgid "" -"Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-" -"support) is actually built on this. When `s3-storage-provider` is " -"enabled, we automatically add additional build steps to install its " -"Python module into the Synapse image." +msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image." msgstr "" #: ../../../CHANGELOG.md:1520 -msgid "" -"Besides this kind of auto-added build steps (for components supported by " -"the playbook), we also let you inject your own custom build steps using " -"configuration like this:" +msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:" msgstr "" #: ../../../CHANGELOG.md:1531 -msgid "" -"People who have needed to customize Synapse previously had to fork the " -"git repository, make their changes to the `Dockerfile` there, point the " -"playbook to the new repository " -"(`matrix_synapse_container_image_self_build_repo`) and enable self-" -"building from scratch (`matrix_synapse_container_image_self_build: " -"true`). This is harder and slower." +msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower." msgstr "" #: ../../../CHANGELOG.md:1533 -msgid "" -"With the new Synapse-customization feature in the playbook, we use the " -"original upstream (pre-built, if available) Synapse image and only build " -"on top of it, right on the Matrix server. This is much faster than " -"building all of Synapse from scratch." +msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch." msgstr "" #: ../../../CHANGELOG.md:1536 @@ -4920,18 +2814,11 @@ msgid "matrix-ldap-registration-proxy support" msgstr "" #: ../../../CHANGELOG.md:1540 -msgid "" -"Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), " -"we now support installing [matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" - a proxy which handles Matrix registration requests and forwards them " -"to LDAP." +msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../CHANGELOG.md:1542 -msgid "" -"See our [Setting up matrix-ldap-registration-proxy](docs/configuring-" -"playbook-matrix-ldap-registration-proxy.md) documentation to get started." +msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1545 @@ -4939,15 +2826,11 @@ msgid "2022-09-15" msgstr "" #: ../../../CHANGELOG.md:1547 -msgid "" -"(Potential Backward Compatibility Break) Major improvements to Synapse " -"workers" +msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers" msgstr "" #: ../../../CHANGELOG.md:1549 -msgid "" -"People who are interested in running a Synapse worker setup should know " -"that **our Synapse worker implementation is much more powerful now**:" +msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:" msgstr "" #: ../../../CHANGELOG.md:1551 @@ -4955,46 +2838,31 @@ msgid "we've added support for [Stream writers](#stream-writers-support)" msgstr "" #: ../../../CHANGELOG.md:1552 -msgid "" -"we've added support for [multiple federation sender workers](#multiple-" -"federation-sender-workers-support)" +msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)" msgstr "" #: ../../../CHANGELOG.md:1553 -msgid "" -"we've added support for [multiple pusher workers](#multiple-pusher-" -"workers-support)" +msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)" msgstr "" #: ../../../CHANGELOG.md:1554 -msgid "" -"we've added support for [running background tasks on a worker" -"](#background-tasks-can-run-on-a-worker)" +msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)" msgstr "" #: ../../../CHANGELOG.md:1555 -msgid "" -"we've restored support for [`appservice` workers](#appservice-worker-" -"support-is-back)" +msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)" msgstr "" #: ../../../CHANGELOG.md:1556 -msgid "" -"we've restored support for [`user_dir` workers](#user-directory-worker-" -"support-is-back)" +msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)" msgstr "" #: ../../../CHANGELOG.md:1557 -msgid "" -"we've made it possible to [reliably use more than 1 `media_repository` " -"worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" +msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)" msgstr "" #: ../../../CHANGELOG.md:1558 -msgid "" -"see the [Potential Backward Incompatibilities after these Synapse worker " -"changes](#potential-backward-incompatibilities-after-these-synapse-" -"worker-changes)" +msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)" msgstr "" #: ../../../CHANGELOG.md:1560 @@ -5002,29 +2870,15 @@ msgid "Stream writers support" msgstr "" #: ../../../CHANGELOG.md:1562 -msgid "" -"From now on, the playbook lets you easily set up various [stream writer " -"workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-" -"writers) which can handle different streams (`events` stream; `typing` " -"URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, " -"`receipts` URL endpoints, `presence` URL endpoints). All of this work was" -" previously handled by the main Synapse process, but can now be offloaded" -" to stream writer worker processes." +msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes." msgstr "" #: ../../../CHANGELOG.md:1564 -msgid "" -"If you're using `matrix_synapse_workers_preset: one-of-each`, you'll " -"automatically get 6 additional workers (one for each of the above stream " -"types). Our `little-federation-helper` preset (meant to be quite minimal " -"and focusing in improved federation performance) does not include stream " -"writer workers." +msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers." msgstr "" #: ../../../CHANGELOG.md:1566 -msgid "" -"If you'd like to customize the number of workers we also make that " -"possible using these variables:" +msgid "If you'd like to customize the number of workers we also make that possible using these variables:" msgstr "" #: ../../../CHANGELOG.md:1579 @@ -5032,11 +2886,7 @@ msgid "Multiple federation sender workers support" msgstr "" #: ../../../CHANGELOG.md:1581 -msgid "" -"Until now, we only supported a single `federation_sender` worker " -"(`matrix_synapse_workers_federation_sender_workers_count` could either be" -" `0` or `1`). From now on, you can have as many as you want to help with " -"your federation traffic." +msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic." msgstr "" #: ../../../CHANGELOG.md:1583 @@ -5044,11 +2894,7 @@ msgid "Multiple pusher workers support" msgstr "" #: ../../../CHANGELOG.md:1585 -msgid "" -"Until now, we only supported a single `pusher` worker " -"(`matrix_synapse_workers_pusher_workers_count` could either be `0` or " -"`1`). From now on, you can have as many as you want to help with pushing " -"notifications out." +msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out." msgstr "" #: ../../../CHANGELOG.md:1587 @@ -5056,17 +2902,11 @@ msgid "Background tasks can run on a worker" msgstr "" #: ../../../CHANGELOG.md:1589 -msgid "" -"From now on, you can put [background task processing on a worker](https" -"://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." +msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)." msgstr "" #: ../../../CHANGELOG.md:1591 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`background` worker automatically. You can also control the `background` " -"workers count with `matrix_synapse_workers_background_workers_count`. " -"Only `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1593 @@ -5074,27 +2914,15 @@ msgid "Appservice worker support is back" msgstr "" #: ../../../CHANGELOG.md:1595 -msgid "" -"We previously had an `appservice` worker type, which [Synapse deprecated " -"in v1.59.0](https://github.com/element-" -"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" -"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" -" did we, at the time." +msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." msgstr "" #: ../../../CHANGELOG.md:1597 -msgid "" -"The new way to implement such workers is by using a `generic_worker` and " -"dedicating it to the task of talking to Application Services. From now " -"on, we have support for this." +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this." msgstr "" #: ../../../CHANGELOG.md:1599 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`appservice` worker automatically. You can also control the `appservice` " -"workers count with `matrix_synapse_workers_appservice_workers_count`. " -"Only `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1601 @@ -5102,27 +2930,15 @@ msgid "User Directory worker support is back" msgstr "" #: ../../../CHANGELOG.md:1603 -msgid "" -"We previously had a `user_dir` worker type, which [Synapse deprecated in " -"v1.59.0](https://github.com/element-" -"hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-" -"synapseappappservice-and-synapseappuser_dir-worker-application-types). So" -" did we, at the time." +msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time." msgstr "" #: ../../../CHANGELOG.md:1605 -msgid "" -"The new way to implement such workers is by using a `generic_worker` and " -"dedicating it to the task of serving the user directory. From now on, we " -"have support for this." +msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this." msgstr "" #: ../../../CHANGELOG.md:1607 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, you'll get one " -"`user_dir` worker automatically. You can also control the `user_dir` " -"workers count with `matrix_synapse_workers_user_dir_workers_count`. Only" -" `0` or `1` workers of this type are supported by Synapse." +msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only `0` or `1` workers of this type are supported by Synapse." msgstr "" #: ../../../CHANGELOG.md:1609 @@ -5130,20 +2946,11 @@ msgid "Using more than 1 media repository worker is now more reliable" msgstr "" #: ../../../CHANGELOG.md:1611 -msgid "" -"With `matrix_synapse_workers_preset: one-of-each`, we only launch one " -"`media_repository` worker." +msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker." msgstr "" #: ../../../CHANGELOG.md:1613 -msgid "" -"If you've been configuring " -"`matrix_synapse_workers_media_repository_workers_count` manually, you may" -" have increased that to more workers. When multiple media repository " -"workers are in use, background tasks related to the media repository must" -" always be configured to run on a single `media_repository` worker via " -"`media_instance_running_background_jobs`. Until now, we weren't doing " -"this correctly, but we now are." +msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are." msgstr "" #: ../../../CHANGELOG.md:1615 @@ -5155,53 +2962,19 @@ msgid "Below we'll discuss **potential backward incompatibilities**." msgstr "" #: ../../../CHANGELOG.md:1619 -msgid "" -"**Worker names** (container names, systemd services, worker configuration" -" files) **have changed**. Workers are now labeled sequentially (e.g. " -"`matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-" -"generic-0`). The playbook will handle these changes automatically." +msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically." msgstr "" #: ../../../CHANGELOG.md:1621 -msgid "" -"Due to increased worker types support above, people who use " -"`matrix_synapse_workers_preset: one-of-each` should be aware that with " -"these changes, **the playbook will deploy 9 additional workers** (6 " -"stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background " -"task worker). This **may increase RAM/CPU usage**, etc. If you find your " -"server struggling, consider disabling some workers with the appropriate " -"`matrix_synapse_workers_*_workers_count` variables." +msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables." msgstr "" #: ../../../CHANGELOG.md:1623 -msgid "" -"**Metric endpoints have also changed** " -"(`/metrics/synapse/worker/generic_worker-18111` -> " -"`/metrics/synapse/worker/generic-worker-0`). If you're [collecting " -"metrics to an external Prometheus server](docs/configuring-playbook-" -"prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-" -"server), consider revisiting our [Collecting Synapse worker metrics to an" -" external Prometheus server](docs/configuring-playbook-prometheus-" -"grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-" -"server) docs and updating your Prometheus configuration. **If you're " -"collecting metrics to the integrated Prometheus server** (not enabled by " -"default), **your Prometheus configuration will be updated " -"automatically**. Old data (from before this change) may stick around " -"though." +msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though." msgstr "" #: ../../../CHANGELOG.md:1625 -msgid "" -"**the format of `matrix_synapse_workers_enabled_list` has changed**. You " -"were never advised to use this variable for directly creating workers (we" -" advise people to control workers using `matrix_synapse_workers_preset` " -"or by tweaking `matrix_synapse_workers_*_workers_count` variables only), " -"but some people may have started using the " -"`matrix_synapse_workers_enabled_list` variable to gain more control over " -"workers. If you're one of them, you'll need to adjust its value. See " -"`roles/custom/matrix-synapse/defaults/main.yml` for more information on " -"the new format. The playbook will also do basic validation and complain " -"if you got something wrong." +msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong." msgstr "" #: ../../../CHANGELOG.md:1628 @@ -5213,16 +2986,11 @@ msgid "Cactus Comments support" msgstr "" #: ../../../CHANGELOG.md:1632 -msgid "" -"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " -"the playbook can now set up [Cactus Comments](https://cactus.chat) - " -"federated comment system for the web based on Matrix." +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix." msgstr "" #: ../../../CHANGELOG.md:1634 -msgid "" -"See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-" -"comments.md) documentation to get started." +msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1637 @@ -5234,21 +3002,11 @@ msgid "Postmoogle email bridge support" msgstr "" #: ../../../CHANGELOG.md:1641 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up the new " -"[Postmoogle](https://github.com/etkecc/postmoogle) email bridge. " -"Postmoogle is like the [email2matrix " -"bridge](https://github.com/devture/email2matrix) (also [already supported" -" by the playbook](docs/configuring-playbook-email2matrix.md)), but more " -"capable and with the intention to soon support *sending* emails, not just" -" receiving." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving." msgstr "" #: ../../../CHANGELOG.md:1643 -msgid "" -"See our [Setting up Postmoogle email bridging](docs/configuring-playbook-" -"bridge-postmoogle.md) documentation to get started." +msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1646 @@ -5260,26 +3018,15 @@ msgid "mautrix-whatsapp default configuration changes" msgstr "" #: ../../../CHANGELOG.md:1650 -msgid "" -"In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/2012), we've made some changes to the default " -"configuration used by the `mautrix-whatsapp` bridge." +msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge." msgstr "" #: ../../../CHANGELOG.md:1652 -msgid "" -"If you're using this bridge, you should look into this PR and see if the " -"new configuration suits you. If not, you can always change individual " -"preferences in your `vars.yml` file." +msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file." msgstr "" #: ../../../CHANGELOG.md:1654 -msgid "" -"Most notably, spaces support has been enabled by default. The bridge will" -" now group rooms into a Matrix space. **If you've already bridged to " -"Whatsapp** prior to this update, you will need to send `!wa sync space` " -"to the bridge bot to make it create the space and put your existing rooms" -" into it." +msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it." msgstr "" #: ../../../CHANGELOG.md:1657 @@ -5291,30 +3038,19 @@ msgid "Conduit support" msgstr "" #: ../../../CHANGELOG.md:1661 -msgid "" -"Thanks to [Charles Wright](https://github.com/cvwright), we now have " -"optional experimental [Conduit](https://conduit.rs) homeserver support " -"for new installations. This comes as a follow-up to the playbook getting " -"[Dendrite support](#dendrite-support) earlier this year." +msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year." msgstr "" #: ../../../CHANGELOG.md:1663 -msgid "" -"Existing Synapse or Dendrite installations do **not** need to be updated." -" **Synapse is still the default homeserver implementation** installed by " -"the playbook." +msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook." msgstr "" #: ../../../CHANGELOG.md:1665 -msgid "" -"To try out Conduit, we recommend that you **use a new server** and the " -"following `vars.yml` configuration:" +msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:" msgstr "" #: ../../../CHANGELOG.md:1671 -msgid "" -"**The homeserver implementation of an existing server cannot be changed**" -" (e.g. from Synapse or Dendrite to Conduit) without data loss." +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss." msgstr "" #: ../../../CHANGELOG.md:1674 @@ -5326,22 +3062,11 @@ msgid "mautrix-discord support" msgstr "" #: ../../../CHANGELOG.md:1678 -msgid "" -"Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the " -"playbook now supports bridging to [Discord](https://discordapp.com/) via " -"the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our " -"[Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-" -"mautrix-discord.md) documentation page for getting started." +msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:1680 -msgid "" -"**Note**: this is a new Discord bridge. The playbook still retains " -"Discord bridging via [matrix-appservice-discord](docs/configuring-" -"playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs" -"/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use " -"the bridge that serves you better, or even all three of them (for " -"different users and use-cases)." +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:1683 @@ -5353,21 +3078,11 @@ msgid "matrix-appservice-kakaotalk support" msgstr "" #: ../../../CHANGELOG.md:1687 -msgid "" -"The playbook now supports bridging to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" -" via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk) - a bridge based on [node-" -"kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and " -"some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks" -" to [hnarjis](https://github.com/hnarjis) for helping us add support for " -"this!" +msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!" msgstr "" #: ../../../CHANGELOG.md:1689 -msgid "" -"See our [Setting up Appservice Kakaotalk bridging](docs/configuring-" -"playbook-bridge-appservice-kakaotalk.md) documentation to get started." +msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1692 @@ -5379,22 +3094,11 @@ msgid "maubot support" msgstr "" #: ../../../CHANGELOG.md:1696 -msgid "" -"Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for " -"starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr " -"(@moan0s)](https://github.com/moan0s) for finishing up (in [PR " -"#1894](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/1894)), the playbook can now help you set up " -"[maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot " -"system." +msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system." msgstr "" #: ../../../CHANGELOG.md:1698 -msgid "" -"See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) " -"documentation to get started." +msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1701 @@ -5406,65 +3110,39 @@ msgid "mx-puppet-skype removal" msgstr "" #: ../../../CHANGELOG.md:1705 -msgid "" -"The playbook no longer includes the [mx-puppet-" -"skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it " -"has been broken and unmaintained for a long time. Users that have " -"`matrix_mx_puppet_skype_enabled` in their configuration files will " -"encounter an error when running the playbook until they remove references" -" to this bridge from their configuration." +msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration." msgstr "" #: ../../../CHANGELOG.md:1707 -msgid "" -"To completely clean up your server from `mx-puppet-skype`'s presence on " -"it:" +msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:" msgstr "" #: ../../../CHANGELOG.md:1709 -msgid "" -"ensure your Ansible configuration (`vars.yml` file) no longer contains " -"`matrix_mx_puppet_skype_*` references" +msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references" msgstr "" #: ../../../CHANGELOG.md:1710 -msgid "" -"stop and disable the systemd service (run `systemctl disable --now " -"matrix-mx-puppet-skype` on the server)" +msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)" msgstr "" #: ../../../CHANGELOG.md:1711 -msgid "" -"delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-" -"skype.service` on the server)" +msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)" msgstr "" #: ../../../CHANGELOG.md:1712 -msgid "" -"delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on" -" the server)" +msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)" msgstr "" #: ../../../CHANGELOG.md:1713 -msgid "" -"drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-" -"postgres-cli` on the server, and execute the `DROP DATABASE " -"matrix_mx_puppet_skype;` query there)" +msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)" msgstr "" #: ../../../CHANGELOG.md:1715 -msgid "" -"If you still need bridging to [Skype](https://www.skype.com/), consider " -"switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-" -"bridge) instead. See [Setting up Go Skype Bridge bridging](docs" -"/configuring-playbook-bridge-go-skype-bridge.md)." +msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)." msgstr "" #: ../../../CHANGELOG.md:1717 -msgid "" -"If you think this is a mistake and `mx-puppet-skype` works for you (or " -"you get it to work somehow), let us know and we may reconsider this " -"removal." +msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal." msgstr "" #: ../../../CHANGELOG.md:1719 @@ -5472,41 +3150,23 @@ msgid "signald (0.19.0+) upgrade requires data migration" msgstr "" #: ../../../CHANGELOG.md:1721 -msgid "" -"In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) " -"(used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." +msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`." msgstr "" #: ../../../CHANGELOG.md:1723 -msgid "" -"Back in the [`v0.19.0` released of " -"signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md)" -" (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-" -"data` command had been added that migrates avatars, group images, " -"attachments, etc., into the database (those were previously stored in the" -" filesystem)." +msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)." msgstr "" #: ../../../CHANGELOG.md:1725 -msgid "" -"If you've been using the mautrix-signal bridge for a while, you may have " -"files stored in the local filesystem, which will need to be upgraded." +msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded." msgstr "" #: ../../../CHANGELOG.md:1727 -msgid "" -"We attempt to do this data migration automatically every time Signald " -"starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` " -"systemd unit definition." +msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition." msgstr "" #: ../../../CHANGELOG.md:1729 -msgid "" -"Keep an eye on your Signal bridge and let us know (in our [support " -"room](README.md#support) or in [Pull Request " -"#1921](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/1921)) if you experience any trouble!" +msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!" msgstr "" #: ../../../CHANGELOG.md:1732 @@ -5518,16 +3178,11 @@ msgid "Ntfy push notifications support" msgstr "" #: ../../../CHANGELOG.md:1736 -msgid "" -"Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the " -"playbook can now install a [ntfy](https://ntfy.sh/) push notifications " -"server for you." +msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" #: ../../../CHANGELOG.md:1738 -msgid "" -"See our [Setting up the ntfy push notifications server](docs/configuring-" -"playbook-ntfy.md) documentation to get started." +msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1741 @@ -5539,49 +3194,19 @@ msgid "(Potential Backward Compatibility Break) Changes around metrics collectio msgstr "" #: ../../../CHANGELOG.md:1745 -msgid "" -"**TLDR**: we've made extensive **changes to metrics exposure/collection, " -"which concern people using an external Prometheus server**. If you don't " -"know what that is, you don't need to read below." +msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below." msgstr "" #: ../../../CHANGELOG.md:1747 -msgid "" -"**Why do major changes to metrics**? Because various services were " -"exposing metrics in different, hacky, ways. Synapse was exposing metrics " -"at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the " -"`matrix.example.com`. The Hookshot role was **repurposing** the Granana " -"web UI domain (`stats.example.com`) for exposing its metrics on " -"`stats.example.com/hookshot/metrics`, while protecting these routes using" -" Basic Authentication **normally used for Synapse** " -"(`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were " -"advising for more `stats.example.com` usage in manual ways. Each role was" -" doing things differently and mixing variables from other roles. Each " -"metrics endpoint was ending up in a different place, protected by who " -"knows what Basic Authentication credentials (if protected at all)." +msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)." msgstr "" #: ../../../CHANGELOG.md:1749 -msgid "" -"**The solution**: a completely revamped way to expose metrics to an " -"external Prometheus server. We are **introducing new " -"`https://matrix.example.com/metrics/*` endpoints**, where various " -"services *can* expose their metrics, for collection by external " -"Prometheus servers. To enable the `/metrics/*` endpoints, use " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a " -"way to protect access using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)." -" See the `matrix-nginx-proxy` role or our [Collecting metrics to an " -"external Prometheus server](docs/configuring-playbook-prometheus-" -"grafana.md#collecting-metrics-to-an-external-prometheus-server) " -"documentation for additional variables around " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`." +msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`." msgstr "" #: ../../../CHANGELOG.md:1751 -msgid "" -"**If you are using the [Hookshot bridge](docs/configuring-playbook-" -"bridge-hookshot.md)**, you may find that:" +msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:" msgstr "" #: ../../../CHANGELOG.md:1752 @@ -5589,120 +3214,51 @@ msgid "**Metrics may not be enabled by default anymore**:" msgstr "" #: ../../../CHANGELOG.md:1753 -msgid "" -"If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot " -"metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: " -"true`). These metrics will be collected from the local (in-container) " -"Prometheus over the container network." +msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network." msgstr "" #: ../../../CHANGELOG.md:1754 -msgid "" -"**If Prometheus is not enabled** (you are either not using Prometheus or " -"are using an external one), **Hookshot metrics will not be enabled by " -"default anymore**. Feel free to enable them by setting " -"`matrix_hookshot_metrics_enabled: true`. Also, see below." +msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below." msgstr "" #: ../../../CHANGELOG.md:1755 -msgid "" -"When metrics are meant to be **consumed by an external Prometheus " -"server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to " -"`true`, so that metrics would be exposed (proxied) \"publicly\" on " -"`https://matrix.example.com/metrics/hookshot`. To make use of this, " -"you'll also need to enable the new `https://matrix.example.com/metrics/*`" -" endpoints mentioned above, using " -"`matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our " -"[Collecting metrics to an external Prometheus server](docs/configuring-" -"playbook-prometheus-grafana.md#collecting-metrics-to-an-external-" -"prometheus-server) documentation." +msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation." msgstr "" #: ../../../CHANGELOG.md:1756 -msgid "" -"**We've changed the URL we're exposing Hookshot metrics at** for external" -" Prometheus servers. Until now, you were advised to consume Hookshot " -"metrics from `https://stats.example.com/hookshot/metrics` (working in " -"conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now " -"on, **this no longer works**. As described above, you need to start " -"consuming metrics from `https://matrix.example.com/metrics/hookshot`." +msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`." msgstr "" #: ../../../CHANGELOG.md:1758 -msgid "" -"**If you're using node-exporter** " -"(`matrix_prometheus_node_exporter_enabled: true`) and would like to " -"collect its metrics from an external Prometheus server, see " -"`matrix_prometheus_node_exporter_metrics_proxying_enabled` described in " -"our [Collecting metrics to an external Prometheus server](docs" -"/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" -"external-prometheus-server) documentation. You will be able to collect " -"its metrics from `https://matrix.example.com/metrics/node-exporter`." +msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`." msgstr "" #: ../../../CHANGELOG.md:1760 -msgid "" -"**If you're using [postgres-exporter](docs/configuring-playbook-" -"prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) " -"and would like to collect its metrics from an external Prometheus server," -" see " -"`matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled`" -" described in our [Collecting metrics to an external Prometheus " -"server](docs/configuring-playbook-prometheus-grafana.md#collecting-" -"metrics-to-an-external-prometheus-server) documentation. You will be able" -" to collect its metrics from `https://matrix.example.com/metrics" -"/postgres-exporter`." +msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`." msgstr "" #: ../../../CHANGELOG.md:1762 -msgid "" -"**If you're using Synapse** and would like to collect its metrics from an" -" external Prometheus server, you may find that:" +msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:" msgstr "" #: ../../../CHANGELOG.md:1764 -msgid "" -"Exposing metrics is now done using " -"`matrix_synapse_metrics_proxying_enabled`, not " -"`matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to " -"enable metrics using `matrix_synapse_metrics_enabled: true` before " -"exposing them." +msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them." msgstr "" #: ../../../CHANGELOG.md:1765 -msgid "" -"Protecting metrics endpoints using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)" -" is now done in another way. See our [Collecting metrics to an external " -"Prometheus server](docs/configuring-playbook-prometheus-grafana.md" -"#collecting-metrics-to-an-external-prometheus-server) documentation" +msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation" msgstr "" #: ../../../CHANGELOG.md:1766 -msgid "" -"If Synapse metrics are exposed, they will be made available at " -"`https://matrix.example.com/metrics/synapse/main-process` or " -"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers" -" are enabled), not at `https://matrix.example.com/_synapse/metrics` and " -"`https://matrix.example.com/_synapse-worker-…/metrics`" +msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`" msgstr "" #: ../../../CHANGELOG.md:1767 -msgid "" -"The playbook still generates an `external_prometheus.yml.example` sample " -"file for scraping Synapse from Prometheus as described in [Collecting " -"Synapse worker metrics to an external Prometheus server](docs" -"/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-" -"metrics-to-an-external-prometheus-server), but it's now saved under " -"`/matrix/synapse` (not `/matrix`)." +msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)." msgstr "" #: ../../../CHANGELOG.md:1769 -msgid "" -"**If you where already using a external Prometheus server** before this " -"change, and you gave a hashed version of the password as a variable, the " -"playbook will now take care of hashing the password for you. Thus, you " -"need to provide the non-hashed version now." +msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now." msgstr "" #: ../../../CHANGELOG.md:1771 @@ -5714,24 +3270,15 @@ msgid "go-skype-bridge bridging support" msgstr "" #: ../../../CHANGELOG.md:1775 -msgid "" -"Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can" -" now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-" -"bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." +msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)." msgstr "" #: ../../../CHANGELOG.md:1777 -msgid "" -"See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-" -"bridge-go-skype-bridge.md) documentation to get started." +msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1779 -msgid "" -"The playbook has supported [mx-puppet-skype](https://github.com/Sorunome" -"/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype " -"bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since " -"[2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." +msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken." msgstr "" #: ../../../CHANGELOG.md:1782 @@ -5743,11 +3290,7 @@ msgid "Running Ansible in a container can now happen on the Matrix server itself msgstr "" #: ../../../CHANGELOG.md:1786 -msgid "" -"If you're tired of being on an old and problematic Ansible version, you " -"can now run [run Ansible in a container on the Matrix server " -"itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-" -"server-itself)." +msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)." msgstr "" #: ../../../CHANGELOG.md:1789 @@ -5759,24 +3302,15 @@ msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" msgstr "" #: ../../../CHANGELOG.md:1793 -msgid "" -"Synapse v1.60 will try to add a new unique index to `state_group_edges` " -"upon startup and could fail if your database is corrupted." +msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted." msgstr "" #: ../../../CHANGELOG.md:1795 -msgid "" -"We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade " -"notes](https://github.com/element-" -"hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-" -"state_group_edges-could-fail-if-your-database-is-corrupted) mention it, " -"so we're giving you a heads up here in case you're unlucky." +msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky." msgstr "" #: ../../../CHANGELOG.md:1797 -msgid "" -"**If Synapse fails to start** after your next playbook run, you'll need " -"to:" +msgid "**If Synapse fails to start** after your next playbook run, you'll need to:" msgstr "" #: ../../../CHANGELOG.md:1799 @@ -5796,9 +3330,7 @@ msgid "run the following SQL query:" msgstr "" #: ../../../CHANGELOG.md:1821 -msgid "" -"You could then restart services: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=start`" +msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`" msgstr "" #: ../../../CHANGELOG.md:1824 @@ -5810,17 +3342,11 @@ msgid "Buscarron bot support" msgstr "" #: ../../../CHANGELOG.md:1828 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron " -"bot](https://github.com/etkecc/buscarron). It's a bot you can use to send" -" any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" msgstr "" #: ../../../CHANGELOG.md:1830 -msgid "" -"See our [Setting up Buscarron](docs/configuring-playbook-bot-" -"buscarron.md) documentation to get started." +msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1833 @@ -5832,17 +3358,11 @@ msgid "matrix-registration-bot support" msgstr "" #: ../../../CHANGELOG.md:1837 -msgid "" -"Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), " -"the playbook can now help you set up [matrix-registration-" -"bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is " -"used to create and manage registration tokens for a Matrix server." +msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server." msgstr "" #: ../../../CHANGELOG.md:1839 -msgid "" -"See our [Setting up matrix-registration-bot](docs/configuring-playbook-" -"bot-matrix-registration-bot.md) documentation to get started." +msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1842 @@ -5854,57 +3374,31 @@ msgid "BorgBackup support" msgstr "" #: ../../../CHANGELOG.md:1846 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now set up " -"[Borg](https://www.borgbackup.org/) backups with " -"[borgmatic](https://torsion.org/borgmatic/) of your Matrix server." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server." msgstr "" #: ../../../CHANGELOG.md:1848 -msgid "" -"See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md)" -" documentation to get started." +msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1850 -msgid "" -"(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers " -"may require manual action" +msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action" msgstr "" #: ../../../CHANGELOG.md:1852 -msgid "" -"If you're running a worker setup for Synapse " -"(`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade " -"notes](https://github.com/element-" -"hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-" -"for-application-services) say that you may need to take special care when" -" upgrading:" +msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:" msgstr "" #: ../../../CHANGELOG.md:1854 -msgid "" -"Synapse v1.57.0 includes a change to the way transaction IDs are managed " -"for application services. If your deployment uses a dedicated worker for " -"application service traffic, **it must be stopped** when the database is " -"upgraded (which normally happens when the main process is upgraded), to " -"ensure the change is made safely without any risk of reusing transaction " -"IDs." +msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs." msgstr "" #: ../../../CHANGELOG.md:1856 -msgid "" -"If you're not running an `appservice` worker " -"(`matrix_synapse_workers_preset: little-federation-helper` or " -"`matrix_synapse_workers_appservice_workers_count: 0`), you are probably " -"safe to upgrade as per normal, without taking any special care." +msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care." msgstr "" #: ../../../CHANGELOG.md:1858 -msgid "" -"If you are running a setup with an `appservice` worker, or otherwise want" -" to be on the safe side, we recommend the following upgrade path:" +msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:" msgstr "" #: ../../../CHANGELOG.md:1860 @@ -5912,15 +3406,11 @@ msgid "Pull the latest playbook changes" msgstr "" #: ../../../CHANGELOG.md:1861 -msgid "" -"Stop all services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../CHANGELOG.md:1862 -msgid "" -"Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-all`)" +msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)" msgstr "" #: ../../../CHANGELOG.md:1863 @@ -5928,22 +3418,15 @@ msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" msgstr "" #: ../../../CHANGELOG.md:1864 -msgid "" -"Start the main Synapse process (`systemctl start matrix-synapse` on the " -"server)" +msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)" msgstr "" #: ../../../CHANGELOG.md:1865 -msgid "" -"Wait a while so that Synapse can start and complete the database " -"migrations. You can use `journalctl -fu matrix-synapse` on the server to " -"get a clue. Waiting a few minutes should also be enough." +msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough." msgstr "" #: ../../../CHANGELOG.md:1866 -msgid "" -"It should now be safe to start all other services. `ansible-playbook -i " -"inventory/hosts setup.yml --tags=start` will do it for you" +msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you" msgstr "" #: ../../../CHANGELOG.md:1869 @@ -5951,45 +3434,23 @@ msgid "2022-04-14" msgstr "" #: ../../../CHANGELOG.md:1871 -msgid "" -"(Compatibility Break) Changes to `docker-src` permissions necessitating " -"manual action" +msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action" msgstr "" #: ../../../CHANGELOG.md:1873 -msgid "" -"Users who build container images from source will need to manually " -"correct file permissions of some directories on the server." +msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server." msgstr "" #: ../../../CHANGELOG.md:1875 -msgid "" -"When self-building, the playbook used to `git clone` repositories (into " -"`/matrix/SERVICE/docker-src`) using the `root` user, but now uses " -"`matrix` instead to work around [the following issue with git " -"2.35.2](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1749)." +msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)." msgstr "" #: ../../../CHANGELOG.md:1877 -msgid "" -"If you're on a non-`amd64` architecture (that is, you're overriding " -"`matrix_architecture` in your `vars.yml` file) or you have enabled self-" -"building for some service (e.g. `matrix_*_self_build: true`), you're " -"certainly building some container images from source and have `docker-" -"src` directories with mixed permissions lying around in various " -"`/matrix/SERVICE` directories." +msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories." msgstr "" #: ../../../CHANGELOG.md:1879 -msgid "" -"The playbook *could* correct these permissions automatically, but that " -"requires additional Ansible tasks in some ~45 different places - " -"something that takes considerable effort. So we ask users observing " -"errors related to `docker-src` directories to correct the problem " -"manually by **running this command on the Matrix server** (which deletes " -"all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name " -"'docker-src' | xargs rm -rf`" +msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`" msgstr "" #: ../../../CHANGELOG.md:1882 @@ -6001,32 +3462,19 @@ msgid "(Compatibility Break) ma1sd identity server no longer installed by defaul msgstr "" #: ../../../CHANGELOG.md:1886 -msgid "" -"The playbook no longer installs the " -"[ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The " -"next time you run the playbook, ma1sd will be uninstalled from your " -"server, unless you explicitly enable the ma1sd service (see how below)." +msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)." msgstr "" #: ../../../CHANGELOG.md:1888 -msgid "" -"The main reason we used to install ma1sd by default in the past was to " -"prevent Element clients from talking to the `matrix.org` / `vector.im` " -"identity servers, by forcing it to talk to our own self-hosted (but " -"otherwise useless) identity server instead, thus preventing contact list " -"leaks." +msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks." msgstr "" #: ../../../CHANGELOG.md:1890 -msgid "" -"Since Element clients no longer default to using a public identity server" -" if another one is not provided, we can stop installing ma1sd." +msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd." msgstr "" #: ../../../CHANGELOG.md:1892 -msgid "" -"If you need to install the ma1sd identity server for some reason, you can" -" explicitly enable it by adding this to your `vars.yml` file:" +msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:1899 @@ -6038,23 +3486,11 @@ msgid "matrix_encryption_disabler support" msgstr "" #: ../../../CHANGELOG.md:1903 -msgid "" -"We now support installing the " -"[matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler)" -" Synapse module, which lets you prevent End-to-End-Encryption from being " -"enabled by users on your homeserver. The popular opinion is that this is " -"dangerous and shouldn't be done, but there are valid use cases for " -"disabling encryption discussed [here](https://github.com/matrix-" -"org/synapse/issues/4401)." +msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)." msgstr "" #: ../../../CHANGELOG.md:1905 -msgid "" -"To enable this module (and prevent encryption from being used on your " -"homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to" -" your configuration. This module provides further customization. Check " -"its other configuration settings (and defaults) in `roles/custom/matrix-" -"synapse/defaults/main.yml`." +msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`." msgstr "" #: ../../../CHANGELOG.md:1908 @@ -6066,13 +3502,7 @@ msgid "matrix-hookshot bridging support" msgstr "" #: ../../../CHANGELOG.md:1912 -msgid "" -"Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can" -" now install the [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) bridge for bridging Matrix to multiple project management " -"services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-" -"hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to " -"get started." +msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1915 @@ -6084,13 +3514,7 @@ msgid "ARM support for matrix-corporal" msgstr "" #: ../../../CHANGELOG.md:1919 -msgid "" -"[matrix-corporal](https://github.com/devture/matrix-corporal) (as of " -"version `2.2.3`) is now published to Docker Hub (see [devture/matrix-" -"corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-" -"arch container image with support for all these platforms: `linux/amd64`," -" `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to " -"self-building matrix-corporal on these ARM architectures." +msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures." msgstr "" #: ../../../CHANGELOG.md:1922 @@ -6102,22 +3526,11 @@ msgid "Dendrite support" msgstr "" #: ../../../CHANGELOG.md:1926 -msgid "" -"**TLDR**: We now have optional experimental [Dendrite](https://github.com" -"/matrix-org/dendrite) homeserver support for new installations. " -"**Existing (Synapse) installations need to be updated**, because some " -"internals changed. See [Adapting the configuration for existing Synapse " -"installations](#adapting-the-configuration-for-existing-synapse-" -"installations)." +msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)." msgstr "" #: ../../../CHANGELOG.md:1928 -msgid "" -"[Jip J. Dekker](https://github.com/Dekker1) did the [initial " -"work](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/818) of adding [Dendrite](https://github.com/matrix-" -"org/dendrite) support to the playbook back in January 2021. Lots of work " -"(and time) later, Dendrite support is finally ready for testing." +msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing." msgstr "" #: ../../../CHANGELOG.md:1930 @@ -6125,19 +3538,11 @@ msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" msgstr "" #: ../../../CHANGELOG.md:1932 -msgid "" -"The playbook was previously quite [Synapse](https://github.com/element-" -"hq/synapse)-centric, but can now accommodate multiple homeserver " -"implementations. Only one homeserver implementation can be active " -"(installed) at a given time." +msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time." msgstr "" #: ../../../CHANGELOG.md:1934 -msgid "" -"**Synapse is still the default homeserver implementation** installed by " -"the playbook. A new variable (`matrix_homeserver_implementation`) " -"controls which server implementation is enabled (`synapse` or `dendrite` " -"at the given moment)." +msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)." msgstr "" #: ../../../CHANGELOG.md:1936 @@ -6145,16 +3550,11 @@ msgid "Adapting the configuration for existing Synapse installations" msgstr "" #: ../../../CHANGELOG.md:1938 -msgid "" -"Because the playbook is not so Synapse-centric anymore, a small " -"configuration change is necessary for existing installations to bring " -"them up to date." +msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date." msgstr "" #: ../../../CHANGELOG.md:1940 -msgid "" -"The `vars.yml` file for **existing installations will need to be " -"updated** by adding this **additional configuration**:" +msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:" msgstr "" #: ../../../CHANGELOG.md:1952 @@ -6162,21 +3562,15 @@ msgid "Trying out Dendrite" msgstr "" #: ../../../CHANGELOG.md:1954 -msgid "" -"Finally, **to try out Dendrite**, we recommend that you **use a new " -"server** and the following addition to your `vars.yml` configuration:" +msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:" msgstr "" #: ../../../CHANGELOG.md:1960 -msgid "" -"**The homeserver implementation of an existing server cannot be changed**" -" (e.g. from Synapse to Dendrite) without data loss." +msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss." msgstr "" #: ../../../CHANGELOG.md:1962 -msgid "" -"We're excited to gain support for other homeserver implementations, like " -"[Conduit](https://conduit.rs/), etc!" +msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!" msgstr "" #: ../../../CHANGELOG.md:1964 @@ -6184,16 +3578,11 @@ msgid "Honoroit bot support" msgstr "" #: ../../../CHANGELOG.md:1966 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook can now help you set up " -"[Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot." msgstr "" #: ../../../CHANGELOG.md:1968 -msgid "" -"See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) " -"documentation to get started." +msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:1971 @@ -6205,23 +3594,15 @@ msgid "Cinny support" msgstr "" #: ../../../CHANGELOG.md:1975 -msgid "" -"Thanks to [Aine](https://gitlab.com/etke.cc) of " -"[etke.cc](https://etke.cc/), the playbook now supports " -"[Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix " -"client." +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client." msgstr "" #: ../../../CHANGELOG.md:1977 -msgid "" -"By default, we still install Element Web. Still, people who'd like to try" -" Cinny out can now install it via the playbook." +msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook." msgstr "" #: ../../../CHANGELOG.md:1979 -msgid "" -"Additional details are available in [Setting up Cinny](docs/configuring-" -"playbook-client-cinny.md)." +msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)." msgstr "" #: ../../../CHANGELOG.md:1982 @@ -6233,12 +3614,7 @@ msgid "Twitter bridging support via mautrix-twitter" msgstr "" #: ../../../CHANGELOG.md:1986 -msgid "" -"Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas " -"Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-" -"twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging" -" to [Twitter](https://twitter.com/) can now also happen with [mautrix-" -"twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." +msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)." msgstr "" #: ../../../CHANGELOG.md:1989 @@ -6246,26 +3622,15 @@ msgid "2021-12-14" msgstr "" #: ../../../CHANGELOG.md:1991 -msgid "" -"(Security) Users of the Signal bridge may wish to upgrade it to work " -"around log4j vulnerability" +msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability" msgstr "" #: ../../../CHANGELOG.md:1993 -msgid "" -"Recently, a security vulnerability affecting the Java logging package " -"`log4j` [has been discovered](https://www.huntress.com/blog/rapid-" -"response-critical-rce-vulnerability-is-affecting-java). Software that " -"uses this Java package is potentially vulnerable." +msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable." msgstr "" #: ../../../CHANGELOG.md:1995 -msgid "" -"One such piece of software that is part of the playbook is the [mautrix-" -"signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), " -"which [has been patched already](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/1452). If you're running this bridge, you may " -"wish to [upgrade](./docs/maintenance-upgrading-services.md)." +msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)." msgstr "" #: ../../../CHANGELOG.md:1998 @@ -6277,17 +3642,11 @@ msgid "Dropped support for Postgres v9.6" msgstr "" #: ../../../CHANGELOG.md:2002 -msgid "" -"Postgres v9.6 reached its end of life today, so the playbook will refuse " -"to run for you if you're still on that version." +msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version." msgstr "" #: ../../../CHANGELOG.md:2004 -msgid "" -"Synapse still supports v9.6 (for now), but we're retiring support for it " -"early, to avoid having to maintain support for so many Postgres versions." -" Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs" -"/maintenance-postgres.md#upgrading-postgresql) via the playbook." +msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook." msgstr "" #: ../../../CHANGELOG.md:2007 @@ -6299,18 +3658,11 @@ msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" msgstr "" #: ../../../CHANGELOG.md:2011 -msgid "" -"The mautrix-hangouts bridge is no longer receiving updates upstream and " -"is likely to stop working in the future. We still retain support for this" -" bridge in the playbook, but you're encouraged to switch away from it." +msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it." msgstr "" #: ../../../CHANGELOG.md:2013 -msgid "" -"There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat)" -" bridge that you can [install using the playbook](docs/configuring-" -"playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will " -"not be migrated**, however. You need to start fresh with the new bridge." +msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge." msgstr "" #: ../../../CHANGELOG.md:2016 @@ -6322,23 +3674,15 @@ msgid "LinkedIn bridging support via beeper-linkedin" msgstr "" #: ../../../CHANGELOG.md:2020 -msgid "" -"Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook " -"can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin)" -" bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." +msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging." msgstr "" #: ../../../CHANGELOG.md:2022 -msgid "" -"This brings the total number of bridges supported by the playbook up to " -"20. See all supported bridges [here](docs/configuring-playbook.md" -"#bridging-other-networks)." +msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../CHANGELOG.md:2024 -msgid "" -"To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn" -" bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." +msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." msgstr "" #: ../../../CHANGELOG.md:2027 @@ -6350,31 +3694,19 @@ msgid "Sygnal upgraded - ARM support and no longer requires a database" msgstr "" #: ../../../CHANGELOG.md:2031 -msgid "" -"The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been " -"upgraded from `v0.9.0` to `v0.10.1`." +msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`." msgstr "" #: ../../../CHANGELOG.md:2033 -msgid "" -"This is an optional component for the playbook, so most of our users " -"wouldn't care about this announcement." +msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement." msgstr "" #: ../../../CHANGELOG.md:2035 -msgid "" -"Since this feels like a relatively big (and untested, as of yet) Sygnal " -"change, we're putting up this changelog entry." +msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry." msgstr "" #: ../../../CHANGELOG.md:2037 -msgid "" -"The new version is also available for the ARM architecture. It also no " -"longer requires a database anymore. If you need to downgrade to the " -"previous version, changing `matrix_sygnal_version` or " -"`matrix_sygnal_docker_image` will not be enough, as we've removed the " -"`database` configuration completely. You'd need to switch to an earlier " -"playbook commit." +msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit." msgstr "" #: ../../../CHANGELOG.md:2040 @@ -6386,23 +3718,15 @@ msgid "Hydrogen support" msgstr "" #: ../../../CHANGELOG.md:2044 -msgid "" -"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " -"now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a " -"new lightweight Matrix client with legacy and mobile browser support." +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support." msgstr "" #: ../../../CHANGELOG.md:2046 -msgid "" -"By default, we still install Element Web, as Hydrogen is still not fully-" -"featured. Still, people who'd like to try Hydrogen out can now install it" -" via the playbook." +msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook." msgstr "" #: ../../../CHANGELOG.md:2048 -msgid "" -"Additional details are available in [Setting up Hydrogen](docs" -"/configuring-playbook-client-hydrogen.md)." +msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)." msgstr "" #: ../../../CHANGELOG.md:2051 @@ -6414,18 +3738,11 @@ msgid "Heisenbridge support" msgstr "" #: ../../../CHANGELOG.md:2055 -msgid "" -"Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now " -"supports bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet " -"another bridge (besides matrix-appservice-irc), called " -"[Heisenbridge](https://github.com/hifi/heisenbridge)." +msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)." msgstr "" #: ../../../CHANGELOG.md:2057 -msgid "" -"Additional details are available in [Setting up Heisenbridge bouncer-" -"style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." +msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." msgstr "" #: ../../../CHANGELOG.md:2060 @@ -6437,17 +3754,11 @@ msgid "Disabling TLSv1 and TLSv1.1 for Coturn" msgstr "" #: ../../../CHANGELOG.md:2064 -msgid "" -"To improve security, we've [removed TLSv1 and TLSv1.1 " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/999) from our default " -"[Coturn](https://github.com/coturn/coturn) configuration." +msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration." msgstr "" #: ../../../CHANGELOG.md:2066 -msgid "" -"If you need to support old clients, you can re-enable both (or whichever " -"one you need) with the following configuration:" +msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:" msgstr "" #: ../../../CHANGELOG.md:2074 @@ -6459,17 +3770,11 @@ msgid "Automated local Postgres backup support" msgstr "" #: ../../../CHANGELOG.md:2078 -msgid "" -"Thanks to [foxcris](https://github.com/foxcris), the playbook can now " -"make automated local Postgres backups on a fixed schedule using [docker-" -"postgres-backup-local](https://github.com/prodrigestivill/docker-" -"postgres-backup-local)." +msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)." msgstr "" #: ../../../CHANGELOG.md:2080 -msgid "" -"Additional details are available in [Setting up postgres backup](docs" -"/configuring-playbook-postgres-backup.md)." +msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)." msgstr "" #: ../../../CHANGELOG.md:2083 @@ -6481,16 +3786,11 @@ msgid "Mjolnir moderation tool (bot) support" msgstr "" #: ../../../CHANGELOG.md:2087 -msgid "" -"Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook " -"can now install and configure the [Mjolnir](https://github.com/matrix-" -"org/mjolnir) moderation tool (bot)." +msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)." msgstr "" #: ../../../CHANGELOG.md:2089 -msgid "" -"Additional details are available in [Setting up Mjolnir](docs" -"/configuring-playbook-bot-mjolnir.md)." +msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)." msgstr "" #: ../../../CHANGELOG.md:2092 @@ -6502,21 +3802,15 @@ msgid "Sygnal push gateway support" msgstr "" #: ../../../CHANGELOG.md:2096 -msgid "" -"The playbook can now install the [Sygnal](https://github.com/matrix-" -"org/sygnal) push gateway for you." +msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" #: ../../../CHANGELOG.md:2098 -msgid "" -"This is only useful to people who develop/build their own Matrix client " -"applications." +msgid "This is only useful to people who develop/build their own Matrix client applications." msgstr "" #: ../../../CHANGELOG.md:2100 -msgid "" -"Additional details are available in our [Setting up the Sygnal push " -"gateway](docs/configuring-playbook-sygnal.md) docs." +msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs." msgstr "" #: ../../../CHANGELOG.md:2103 @@ -6528,15 +3822,11 @@ msgid "Go-NEB support" msgstr "" #: ../../../CHANGELOG.md:2107 -msgid "" -"Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install" -" and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." +msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot." msgstr "" #: ../../../CHANGELOG.md:2109 -msgid "" -"Additional details are available in [Setting up Go-NEB](docs/configuring-" -"playbook-bot-go-neb.md)." +msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)." msgstr "" #: ../../../CHANGELOG.md:2112 @@ -6548,23 +3838,15 @@ msgid "GroupMe bridging support via mx-puppet-groupme" msgstr "" #: ../../../CHANGELOG.md:2116 -msgid "" -"Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can " -"now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-" -"puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." +msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)." msgstr "" #: ../../../CHANGELOG.md:2118 -msgid "" -"This brings the total number of bridges supported by the playbook up to " -"18. See all supported bridges [here](docs/configuring-playbook.md" -"#bridging-other-networks)." +msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../CHANGELOG.md:2120 -msgid "" -"To get started, follow our [Setting up MX Puppet GroupMe](docs" -"/configuring-playbook-bridge-mx-puppet-groupme.md) docs." +msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs." msgstr "" #: ../../../CHANGELOG.md:2122 @@ -6572,18 +3854,11 @@ msgid "Mautrix Instagram bridging support" msgstr "" #: ../../../CHANGELOG.md:2124 -msgid "" -"The playbook now supports bridging with " -"[Instagram](https://www.instagram.com/) by installing the [mautrix-" -"instagram](https://github.com/tulir/mautrix-instagram) bridge. This " -"playbook functionality is available thanks to " -"[@MarcProe](https://github.com/MarcProe)." +msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)." msgstr "" #: ../../../CHANGELOG.md:2126 -msgid "" -"Additional details are available in [Setting up Mautrix Instagram " -"bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." +msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." msgstr "" #: ../../../CHANGELOG.md:2128 @@ -6591,44 +3866,23 @@ msgid "Synapse workers support" msgstr "" #: ../../../CHANGELOG.md:2130 -msgid "" -"After [lots and lots of work](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/456) (done over many months by [Marcel " -"Partap](https://github.com/eMPee584), [Max " -"Klenk](https://github.com/maxklenk), a few others from the [Technical " -"University of Dresden, Germany](https://tu-dresden.de/) and various other" -" contributors), support for Synapse workers has finally landed." +msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed." msgstr "" #: ../../../CHANGELOG.md:2132 -msgid "" -"Having support for workers makes the playbook suitable for larger " -"homeserver deployments." +msgid "Having support for workers makes the playbook suitable for larger homeserver deployments." msgstr "" #: ../../../CHANGELOG.md:2134 -msgid "" -"Our setup is not yet perfect (we don't support all types of workers; " -"scaling some of them (like `pusher`, `federation_sender`) beyond a single" -" instance is not yet supported). Still, it's a great start and can " -"already power homeservers with thousands of users, like the [Matrix " -"deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed" -" in [Matrix Live S06E09 - TU Dresden on their Matrix " -"deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." +msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)." msgstr "" #: ../../../CHANGELOG.md:2136 -msgid "" -"By default, workers are disabled and Synapse runs as a single process " -"(homeservers don't necessarily need the complexity and increased memory " -"requirements of running a worker-based setup)." +msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)." msgstr "" #: ../../../CHANGELOG.md:2138 -msgid "" -"To enable Synapse workers, follow our [Load balancing with workers](docs" -"/configuring-playbook-synapse.md#load-balancing-with-workers) " -"documentation." +msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation." msgstr "" #: ../../../CHANGELOG.md:2141 @@ -6636,36 +3890,19 @@ msgid "2021-02-12" msgstr "" #: ../../../CHANGELOG.md:2143 -msgid "" -"(Potential Breaking Change) Monitoring/metrics support using Prometheus " -"and Grafana" +msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana" msgstr "" #: ../../../CHANGELOG.md:2145 -msgid "" -"Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now " -"install a bunch of tools for monitoring your Matrix server: the " -"[Prometheus](https://prometheus.io) time-series database server, the " -"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" -"exporter/) host metrics exporter, and the [Grafana](https://grafana.com/)" -" web UI." +msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI." msgstr "" #: ../../../CHANGELOG.md:2147 -msgid "" -"To get get these installed, follow our [Enabling metrics and graphs " -"(Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-" -"prometheus-grafana.md) docs page." +msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page." msgstr "" #: ../../../CHANGELOG.md:2149 -msgid "" -"This update comes with a **potential breaking change** for people who " -"were already exposing Synapse metrics (for consumption via another " -"Prometheus installation). From now on, `matrix_synapse_metrics_enabled: " -"true` no longer exposes metrics publicly via matrix-nginx-proxy (at " -"`https://matrix.example.com/_synapse/metrics`). To do so, you'd need to " -"explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." +msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`." msgstr "" #: ../../../CHANGELOG.md:2152 @@ -6677,18 +3914,11 @@ msgid "Etherpad support" msgstr "" #: ../../../CHANGELOG.md:2156 -msgid "" -"Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can " -"now install the [Etherpad](https://etherpad.org) realtime collaborative " -"text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video " -"call or integrated as a widget into Matrix chat rooms via the " -"[Dimension](https://dimension.t2bot.io) integration manager." +msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager." msgstr "" #: ../../../CHANGELOG.md:2158 -msgid "" -"To get it installed, follow [our Etherpad docs page](docs/configuring-" -"playbook-etherpad.md)." +msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)." msgstr "" #: ../../../CHANGELOG.md:2161 @@ -6700,17 +3930,11 @@ msgid "(Breaking Change) Postgres changes that require manual intervention" msgstr "" #: ../../../CHANGELOG.md:2165 -msgid "" -"We've made a lot of changes to our Postgres setup and some manual action " -"is required (described below). Sorry about the hassle." +msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle." msgstr "" #: ../../../CHANGELOG.md:2167 -msgid "" -"**TLDR**: people running an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md) don't need to change anything for now. " -"Everyone else (the common/default case) is affected and manual " -"intervention is required." +msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required." msgstr "" #: ../../../CHANGELOG.md:2169 @@ -6718,60 +3942,31 @@ msgid "Why?" msgstr "" #: ../../../CHANGELOG.md:2171 -msgid "" -"we had a default Postgres password (`matrix_postgres_connection_password:" -" synapse-password`), which we think is **not ideal for security " -"anymore**. We now ask you to generate/provide a strong password yourself." -" Postgres is normally not exposed outside the container network, making " -"it relatively secure, but still:" +msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:" msgstr "" #: ../../../CHANGELOG.md:2172 -msgid "" -"by tweaking the configuration, you may end up intentionally or " -"unintentionally exposing your Postgres server to the local network (or " -"even publicly), while still using the default default credentials " -"(`synapse` + `synapse-password`)" +msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2173 -msgid "" -"we can't be sure we trust all these services (bridges, etc). Some of them" -" may try to talk to or attack `matrix-postgres` using the default " -"credentials (`synapse` + `synapse-password`)" +msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2174 -msgid "" -"you may have other containers running on the same Docker network, which " -"may try to talk to or attack `matrix-postgres` using the default " -"credentials (`synapse` + `synapse-password`)" +msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)" msgstr "" #: ../../../CHANGELOG.md:2175 -msgid "" -"our Postgres usage **was overly-focused on Synapse** (default username of" -" `synapse` and default/main database of `homeserver`). Additional " -"homeserver options are likely coming in the future " -"([Dendrite](https://matrix.org/docs/projects/server/dendrite), " -"[Conduit](https://matrix.org/docs/projects/server/conduit), [The " -"Construct](https://matrix.org/docs/projects/server/construct)), so being " -"too focused on `matrix-synapse` is not great. From now on, Synapse is " -"just another component of this playbook, which happens to have an " -"*additional database* (called `synapse`) on the Postgres server." +msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server." msgstr "" #: ../../../CHANGELOG.md:2176 -msgid "" -"we try to reorganize things a bit, to make the playbook even friendlier " -"to people running an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md). Work on this will proceed in the future." +msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future." msgstr "" #: ../../../CHANGELOG.md:2178 -msgid "" -"So, this is some **effort to improve security** and to **prepare for a " -"brighter future of having more homeserver options** than just Synapse." +msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse." msgstr "" #: ../../../CHANGELOG.md:2180 @@ -6779,9 +3974,7 @@ msgid "What has really changed?" msgstr "" #: ../../../CHANGELOG.md:2182 -msgid "" -"the default superuser Postgres username is now `matrix` (used to be " -"`synapse`)" +msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)" msgstr "" #: ../../../CHANGELOG.md:2183 @@ -6789,16 +3982,11 @@ msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" msgstr "" #: ../../../CHANGELOG.md:2184 -msgid "" -"Synapse's database is now `synapse` (used to be `homeserver`). This is " -"now just another \"additional database\" that the playbook manages for " -"you" +msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you" msgstr "" #: ../../../CHANGELOG.md:2185 -msgid "" -"Synapse's user called `synapse` is just a regular user that can only use " -"the `synapse` database (not a superuser anymore)" +msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)" msgstr "" #: ../../../CHANGELOG.md:2187 @@ -6806,51 +3994,31 @@ msgid "What do I do if I'm using the integrated Postgres server (default)?" msgstr "" #: ../../../CHANGELOG.md:2189 -msgid "" -"By default, the playbook runs an integrated Postgres server for you in a " -"container (`matrix-postgres`). Unless you've explicitly configured an " -"[external Postgres server](docs/configuring-playbook-external-" -"postgres.md), these steps are meant for you." +msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you." msgstr "" #: ../../../CHANGELOG.md:2191 -msgid "" -"To migrate to the new setup, expect a few minutes of downtime, while you " -"follow these steps:" +msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:" msgstr "" #: ../../../CHANGELOG.md:2193 -msgid "" -"We believe the steps below are safe and you won't encounter any data " -"loss, but consider [making a Postgres backup](docs/maintenance-" -"postgres.md#backing-up-postgresql) anyway. If you've never backed up " -"Postgres, now would be a good time to try it." +msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it." msgstr "" #: ../../../CHANGELOG.md:2195 -msgid "" -"Generate a strong password to be used for your superuser Postgres user " -"(called `matrix`). You can use `pwgen -s 64 1` to generate it, or some " -"other tool. The **maximum length** for a Postgres password is 100 bytes " -"(characters). Don't go crazy!" +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" msgstr "" #: ../../../CHANGELOG.md:2197 -msgid "" -"Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` " -"file, adding a line like this:" +msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:" msgstr "" #: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214 -msgid "" -".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the " -"password you generated during step #2." +msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2." msgstr "" #: ../../../CHANGELOG.md:2204 -msgid "" -"Stop all services: `ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`" +msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`" msgstr "" #: ../../../CHANGELOG.md:2205 @@ -6866,15 +4034,11 @@ msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" msgstr "" #: ../../../CHANGELOG.md:2208 -msgid "" -"Execute the following query, while making sure to **change the password " -"inside** (**don't forget the ending `;`**):" +msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):" msgstr "" #: ../../../CHANGELOG.md:2216 -msgid "" -"Execute the following queries as you see them (no modifications " -"necessary, so you can just **paste them all at once**):" +msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):" msgstr "" #: ../../../CHANGELOG.md:2234 @@ -6882,9 +4046,7 @@ msgid "You may need to press *Enter* after pasting the lines above." msgstr "" #: ../../../CHANGELOG.md:2236 -msgid "" -"Re-run the playbook normally: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=setup-all,start`" +msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../CHANGELOG.md:2238 @@ -6892,21 +4054,11 @@ msgid "What do I do if I'm using an external Postgres server?" msgstr "" #: ../../../CHANGELOG.md:2240 -msgid "" -"If you've explicitly configured an [external Postgres server](docs" -"/configuring-playbook-external-postgres.md), there are **no changes** " -"that you need to do at this time." +msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time." msgstr "" #: ../../../CHANGELOG.md:2242 -msgid "" -"The fact that we've renamed Synapse's database from `homeserver` to " -"`synapse` (in our defaults) should not affect you, as you're already " -"explicitly defining `matrix_synapse_database_database` (if you've " -"followed our guide, that is). If you're not explicitly defining this " -"variable, you may wish to do so (`matrix_synapse_database_database: " -"homeserver`), to avoid the new `synapse` default and keep things as they " -"were." +msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were." msgstr "" #: ../../../CHANGELOG.md:2245 @@ -6914,35 +4066,19 @@ msgid "2021-01-20" msgstr "" #: ../../../CHANGELOG.md:2247 -msgid "" -"(Breaking Change) The mautrix-facebook bridge now requires a Postgres " -"database" +msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database" msgstr "" #: ../../../CHANGELOG.md:2249 -msgid "" -"**Update from 2021-11-15**: SQLite support has been re-added to the " -"mautrix-facebook bridge in " -"[v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You " -"can ignore this changelog entry." +msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry." msgstr "" #: ../../../CHANGELOG.md:2251 -msgid "" -"A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-" -"facebook) bridge has been released. It's a full rewrite of its backend " -"and the bridge now requires Postgres. New versions of the bridge can no " -"longer run on SQLite." +msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite." msgstr "" #: ../../../CHANGELOG.md:2253 -msgid "" -"**TLDR**: if you're NOT using an [external Postgres server](docs" -"/configuring-playbook-external-postgres.md) and have NOT forcefully kept " -"the bridge on SQLite during [The big move to all-on-Postgres (potentially" -" dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you" -" will be automatically upgraded without manual intervention. All you need" -" to do is send a `login` message to the Facebook bridge bot again." +msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again." msgstr "" #: ../../../CHANGELOG.md:2255 @@ -6950,55 +4086,31 @@ msgid "Whether this change requires your intervention depends mostly on:" msgstr "" #: ../../../CHANGELOG.md:2256 -msgid "" -"whether you're using an [external Postgres server](docs/configuring-" -"playbook-external-postgres.md). If yes, then [you need to do something" -"](#upgrade-path-for-people-running-an-external-postgres-server)." +msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)." msgstr "" #: ../../../CHANGELOG.md:2257 -msgid "" -"or whether you've force-changed the bridge's database engine to SQLite " -"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " -"some time in the past (likely during [The big move to all-on-Postgres " -"(potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-" -"dangerous))." +msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))." msgstr "" #: ../../../CHANGELOG.md:2259 -msgid "" -"As already mentioned above, you most likely don't need to do anything. If" -" you rerun the playbook and don't get an error, you've been automatically" -" upgraded. Just send a `login` message to the Facebook bridge bot again. " -"Otherwise, read below for a solution." +msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution." msgstr "" #: ../../../CHANGELOG.md:2261 -msgid "" -"Upgrade path for people NOT running an external Postgres server (default " -"for the playbook)" +msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)" msgstr "" #: ../../../CHANGELOG.md:2263 -msgid "" -"If you're **not running an external Postgres server**, then this bridge " -"either already works on Postgres for you, or you've intentionally kept it" -" back on SQLite with custom configuration " -"(`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) " -"." +msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ." msgstr "" #: ../../../CHANGELOG.md:2265 -msgid "" -"Simply remove that custom configuration from your `vars.yml` file (if " -"it's there) and re-run the playbook. It should upgrade you automatically." -" You'll need to send a `login` message to the Facebook bridge bot again." +msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again." msgstr "" #: ../../../CHANGELOG.md:2267 -msgid "" -"Alternatively, [you can stay on SQLite for a little longer](#staying-on-" -"sqlite-for-a-little-longer-temporary-solution)." +msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)." msgstr "" #: ../../../CHANGELOG.md:2269 @@ -7006,35 +4118,23 @@ msgid "Upgrade path for people running an external Postgres server" msgstr "" #: ../../../CHANGELOG.md:2271 -msgid "" -"For people using the internal Postgres server (the default for the " -"playbook):" +msgid "For people using the internal Postgres server (the default for the playbook):" msgstr "" #: ../../../CHANGELOG.md:2272 -msgid "" -"we automatically create an additional `matrix_mautrix_facebook` Postgres " -"database and credentials to access it" +msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it" msgstr "" #: ../../../CHANGELOG.md:2273 -msgid "" -"we automatically adjust the bridge's `matrix_mautrix_facebook_database_*`" -" variables to point the bridge to that Postgres database" +msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database" msgstr "" #: ../../../CHANGELOG.md:2274 -msgid "" -"we use [pgloader](https://pgloader.io/) to automatically import the " -"existing SQLite data for the bridge into the `matrix_mautrix_facebook` " -"Postgres database" +msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database" msgstr "" #: ../../../CHANGELOG.md:2276 -msgid "" -"If you are using an [external Postgres server](docs/configuring-playbook-" -"external-postgres.md), unfortunately we currently can't do any of that " -"for you." +msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you." msgstr "" #: ../../../CHANGELOG.md:2278 @@ -7058,29 +4158,19 @@ msgid "create a new `matrix_mautrix_facebook` Postgres database for it" msgstr "" #: ../../../CHANGELOG.md:2284 -msgid "" -"run [pgloader](https://pgloader.io/) manually (we import this bridge's " -"data using default settings and it works well)" +msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)" msgstr "" #: ../../../CHANGELOG.md:2285 -msgid "" -"define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` " -"file (credentials, etc.) - you can find their defaults in `roles/custom" -"/matrix-mautrix-facebook/defaults/main.yml`" +msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`" msgstr "" #: ../../../CHANGELOG.md:2286 -msgid "" -"switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: " -"'postgres'` in your `vars.yml` file)" +msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)" msgstr "" #: ../../../CHANGELOG.md:2287 -msgid "" -"re-run the playbook (`--tags=setup-all,start`) and ensure the bridge " -"works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu " -"matrix-mautrix-facebook`)" +msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)" msgstr "" #: ../../../CHANGELOG.md:2288 @@ -7088,9 +4178,7 @@ msgid "send a `login` message to the Facebook bridge bot again" msgstr "" #: ../../../CHANGELOG.md:2289 -msgid "" -"or, [stay on SQLite for a little longer (temporary solution)](#staying-" -"on-sqlite-for-a-little-longer-temporary-solution)" +msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)" msgstr "" #: ../../../CHANGELOG.md:2291 @@ -7098,17 +4186,11 @@ msgid "Staying on SQLite for a little longer (temporary solution)" msgstr "" #: ../../../CHANGELOG.md:2293 -msgid "" -"To keep using this bridge with SQLite for a little longer (**not " -"recommended**), use the following configuration in your `vars.yml` file:" +msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:" msgstr "" #: ../../../CHANGELOG.md:2303 -msgid "" -"If you do this, keep in mind that **you can't run this forever**. This " -"SQLite-supporting bridge version is not getting any updates and will " -"break sooner or later. The playbook will also drop support for SQLite at " -"some point in the future." +msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future." msgstr "" #: ../../../CHANGELOG.md:2306 @@ -7120,9 +4202,7 @@ msgid "matrix-corporal goes 2.0" msgstr "" #: ../../../CHANGELOG.md:2310 -msgid "" -"[matrix-corporal v2 has been released](https://github.com/devture/matrix-" -"corporal/releases/tag/2.0.0) and the playbook also supports it now." +msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now." msgstr "" #: ../../../CHANGELOG.md:2312 @@ -7130,13 +4210,7 @@ msgid "No manual intervention is required in the common case." msgstr "" #: ../../../CHANGELOG.md:2314 -msgid "" -"The new [matrix-corporal](https://github.com/devture/matrix-corporal) " -"version is also the first one to support Interactive Authentication. If " -"you wish to enable that (hint: you should), you'll need to set up the " -"[REST auth password provider](docs/configuring-playbook-rest-auth.md). " -"There's more information in [our matrix-corporal docs](docs/configuring-" -"playbook-matrix-corporal.md)." +msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../CHANGELOG.md:2317 @@ -7148,22 +4222,15 @@ msgid "Moving from cronjobs to systemd timers" msgstr "" #: ../../../CHANGELOG.md:2321 -msgid "" -"We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-" -"nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to " -"systemd timers." +msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers." msgstr "" #: ../../../CHANGELOG.md:2323 -msgid "" -"The largest benefit of this is that we no longer require you to install a" -" cron daemon, thus simplifying our install procedure." +msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure." msgstr "" #: ../../../CHANGELOG.md:2325 -msgid "" -"The playbook will migrate you from cronjobs to systemd timers " -"automatically. This is just a heads up." +msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up." msgstr "" #: ../../../CHANGELOG.md:2328 @@ -7175,31 +4242,19 @@ msgid "(Breaking Change) New SSL configuration" msgstr "" #: ../../../CHANGELOG.md:2332 -msgid "" -"SSL configuration (protocols, ciphers) can now be more easily controlled " -"thanks to us making use of configuration presets." +msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets." msgstr "" #: ../../../CHANGELOG.md:2334 -msgid "" -"We define a few presets (old, intermediate, modern), following the " -"[Mozilla SSL Configuration Generator](https://ssl-" -"config.mozilla.org/#server=nginx)." +msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)." msgstr "" #: ../../../CHANGELOG.md:2336 -msgid "" -"A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is " -"used (defaults to `\"intermediate\"`)." +msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)." msgstr "" #: ../../../CHANGELOG.md:2338 -msgid "" -"Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to " -"`off` (used to default to `on`). It also add some more ciphers to the " -"list, giving better performance on mobile devices, and removes some weak " -"ciphers. More information in the [documentation](docs/configuring-" -"playbook-nginx.md)." +msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off` (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)." msgstr "" #: ../../../CHANGELOG.md:2340 @@ -7207,10 +4262,7 @@ msgid "To revert to the old behaviour, set the following variables:" msgstr "" #: ../../../CHANGELOG.md:2347 -msgid "" -"Just like before, you can still use your own custom protocols by " -"specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides" -" the values coming from the preset." +msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset." msgstr "" #: ../../../CHANGELOG.md:2350 @@ -7222,20 +4274,11 @@ msgid "Signal bridging support via mautrix-signal" msgstr "" #: ../../../CHANGELOG.md:2354 -msgid "" -"Thanks to [laszabine](https://github.com/laszabine)'s efforts, the " -"playbook now supports bridging to [Signal](https://www.signal.org/) via " -"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See" -" our [Setting up Mautrix Signal bridging](docs/configuring-playbook-" -"bridge-mautrix-signal.md) documentation page for getting started." +msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2356 -msgid "" -"If you had installed the mautrix-signal bridge while its Pull Request was" -" still work-in-progress, you can migrate your data to the new and final " -"setup by referring to [this comment](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." +msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)." msgstr "" #: ../../../CHANGELOG.md:2359 @@ -7247,26 +4290,15 @@ msgid "The big move to all-on-Postgres (potentially dangerous)" msgstr "" #: ../../../CHANGELOG.md:2363 -msgid "" -"**TLDR**: all your bridges (and other services) will likely be auto-" -"migrated from SQLite/nedb to Postgres, hopefully without trouble. You can" -" opt-out (see how below), if too worried about breakage." +msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage." msgstr "" #: ../../../CHANGELOG.md:2365 -msgid "" -"Until now, we've only used Postgres as a database for Synapse. All other " -"services (bridges, bots, etc.) were kept simple and used a file-based " -"database (SQLite or nedb)." +msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)." msgstr "" #: ../../../CHANGELOG.md:2367 -msgid "" -"Since [this huge pull request](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/740), **all of our services now use Postgres " -"by default**. Thanks to [Johanna Dorothea " -"Reichmann](https://github.com/jdreichmann) for starting the work on it " -"and for providing great input!" +msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!" msgstr "" #: ../../../CHANGELOG.md:2369 @@ -7278,25 +4310,15 @@ msgid "**improved performance**" msgstr "" #: ../../../CHANGELOG.md:2372 -msgid "" -"**improved compatibility**. Most bridges are deprecating SQLite/nedb " -"support or offer less features when not on Postgres." +msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres." msgstr "" #: ../../../CHANGELOG.md:2373 -msgid "" -"**easier backups**. It's still some effort to take a proper backup " -"(Postgres dump + various files, keys), but a Postgres dump now takes you " -"much further." +msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further." msgstr "" #: ../../../CHANGELOG.md:2374 -msgid "" -"we're now **more prepared to introduce other services** that need a " -"Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), " -"the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge " -"(existing [pull request](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/686)), etc." +msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc." msgstr "" #: ../../../CHANGELOG.md:2376 @@ -7304,21 +4326,11 @@ msgid "Key takeway" msgstr "" #: ../../../CHANGELOG.md:2378 -msgid "" -"existing installations that use an [external " -"Postgres](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/master/docs/configuring-playbook-external-postgres.md) server" -" should be unaffected (they remain on SQLite/nedb for all services, " -"except Synapse)" +msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)" msgstr "" #: ../../../CHANGELOG.md:2380 -msgid "" -"for existing installations which use our integrated Postgres database " -"server (`matrix-postgres`, which is the default), **we automatically " -"migrate data** from SQLite/nedb to Postgres and **archive the database " -"files** (`something.db` -> `something.db.backup`), so you can restore " -"them if you need to go back (see how below)." +msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)." msgstr "" #: ../../../CHANGELOG.md:2382 @@ -7326,26 +4338,15 @@ msgid "Opting-out of the Postgres migration" msgstr "" #: ../../../CHANGELOG.md:2384 -msgid "" -"This is a **very large and somewhat untested change** (potentially " -"dangerous), so **if you're not feeling confident/experimental, opt-out** " -"of it for now. Still, it's the new default and what we (and various " -"bridges) will focus on going forward, so don't stick to old ways for too " -"long." +msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long." msgstr "" #: ../../../CHANGELOG.md:2386 -msgid "" -"You can remain on SQLite/nedb (at least for now) by adding a variable " -"like this to your `vars.yml` file for each service you use: " -"`matrix_COMPONENT_database_engine: sqlite` (e.g. " -"`matrix_mautrix_facebook_database_engine: sqlite`)." +msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)." msgstr "" #: ../../../CHANGELOG.md:2388 -msgid "" -"Some services (like `appservice-irc` and `appservice-slack`) don't use " -"SQLite, so use `nedb`, instead of `sqlite` for them." +msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." msgstr "" #: ../../../CHANGELOG.md:2390 @@ -7353,37 +4354,23 @@ msgid "Going back to SQLite/nedb if things went wrong" msgstr "" #: ../../../CHANGELOG.md:2392 -msgid "" -"If you went with the Postgres migration and it went badly for you (some " -"bridge not working as expected or not working at all), do this:" +msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:" msgstr "" #: ../../../CHANGELOG.md:2394 -msgid "" -"stop all services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../CHANGELOG.md:2395 -msgid "" -"SSH into the server and rename the old database files " -"(`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-" -"facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data" -"/mautrix-facebook.db`" +msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`" msgstr "" #: ../../../CHANGELOG.md:2396 -msgid "" -"switch the affected service back to SQLite (e.g. " -"`matrix_mautrix_facebook_database_engine: sqlite`). Some services (like " -"`appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`," -" instead of `sqlite` for them." +msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." msgstr "" #: ../../../CHANGELOG.md:2397 -msgid "" -"re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-all,start`)" +msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)" msgstr "" #: ../../../CHANGELOG.md:2398 @@ -7399,20 +4386,11 @@ msgid "synapse-janitor support removed" msgstr "" #: ../../../CHANGELOG.md:2404 -msgid "" -"We've removed support for the unmaintained [synapse-" -"janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's " -"been past reports of it corrupting the Synapse database. Since there " -"hasn't been any new development on it and it doesn't seem too useful " -"nowadays, there's no point in including it in the playbook." +msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook." msgstr "" #: ../../../CHANGELOG.md:2406 -msgid "" -"If you need to clean up or compact your database, consider using the " -"Synapse Admin APIs directly. See our [Synapse maintenance](docs" -"/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-" -"postgres.md) documentation pages for more details." +msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details." msgstr "" #: ../../../CHANGELOG.md:2408 @@ -7420,26 +4398,15 @@ msgid "Docker 20.10 is here" msgstr "" #: ../../../CHANGELOG.md:2410 -msgid "" -"(No need to do anything special in relation to this. Just something to " -"keep in mind)" +msgid "(No need to do anything special in relation to this. Just something to keep in mind)" msgstr "" #: ../../../CHANGELOG.md:2412 -msgid "" -"Docker 20.10 got released recently and your server will likely get it the" -" next time you update." +msgid "Docker 20.10 got released recently and your server will likely get it the next time you update." msgstr "" #: ../../../CHANGELOG.md:2414 -msgid "" -"This is the first major Docker update in a long time and it packs a lot " -"of changes. Some of them introduced some breakage for us initially (see " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should " -"be all good now." +msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now." msgstr "" #: ../../../CHANGELOG.md:2417 @@ -7447,31 +4414,19 @@ msgid "2020-12-08" msgstr "" #: ../../../CHANGELOG.md:2419 -msgid "" -"openid APIs exposed by default on the federation port when federation " -"disabled" +msgid "openid APIs exposed by default on the federation port when federation disabled" msgstr "" #: ../../../CHANGELOG.md:2421 -msgid "" -"We've changed some defaults. People running with our default " -"configuration (federation enabled), are not affected at all." +msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all." msgstr "" #: ../../../CHANGELOG.md:2423 -msgid "" -"If you are running an unfederated server " -"(`matrix_synapse_federation_enabled: false`), this may be of interest to " -"you." +msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you." msgstr "" #: ../../../CHANGELOG.md:2425 -msgid "" -"When federation is disabled, but ma1sd or Dimension are enabled, we'll " -"now expose the `openid` APIs on the federation port. These APIs are " -"necessary for some ma1sd features to work. If you'd like to prevent this," -" you can: `matrix_synapse_federation_port_openid_resource_required: " -"false`." +msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`." msgstr "" #: ../../../CHANGELOG.md:2428 @@ -7483,10 +4438,7 @@ msgid "Recent Jitsi updates may require configuration changes" msgstr "" #: ../../../CHANGELOG.md:2432 -msgid "" -"We've recently [updated from Jitsi build 4857 to build " -"5142](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/719), which brings a lot of configuration changes." +msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes." msgstr "" #: ../../../CHANGELOG.md:2434 @@ -7494,29 +4446,15 @@ msgid "**If you use our default Jitsi settings, you won't have to do anything.** msgstr "" #: ../../../CHANGELOG.md:2436 -msgid "" -"People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md" -"#optional-fine-tune-jitsi) may find that some options got renamed now, " -"others are gone and yet others still need to be defined in another way." +msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way." msgstr "" #: ../../../CHANGELOG.md:2438 -msgid "" -"The next time you run the playbook [installation](docs/installing.md) " -"command, our validation logic will tell you if you're using some " -"variables like that and will recommend a migration path for each one." +msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one." msgstr "" #: ../../../CHANGELOG.md:2440 -msgid "" -"Additionally, we've recently disabled transcriptions " -"(`jitsi_enable_transcriptions: false`) and recording " -"(`jitsi_enable_recording: false`) by default. These features did not work" -" anyway, because we don't install the required dependencies for them " -"(Jigasi and Jibri, respectively). If you've been somehow pointing your " -"Jitsi installation to some manually installed Jigasi/Jibri service, you " -"may need to toggle these flags back to enabled to have transcriptions and" -" recordings working." +msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working." msgstr "" #: ../../../CHANGELOG.md:2443 @@ -7528,18 +4466,11 @@ msgid "Breaking change matrix-sms-bridge" msgstr "" #: ../../../CHANGELOG.md:2447 -msgid "" -"Because of many problems using gammu as SMS provider, matrix-sms-bridge " -"now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by " -"default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-" -"sms.md] which new vars you need to add." +msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add." msgstr "" #: ../../../CHANGELOG.md:2449 -msgid "" -"If you are using this playbook to deploy matrix-sms-bridge and still " -"really want to use gammu as SMS provider, we could possibly add support " -"for both android-sms-gateway-server and gammu." +msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu." msgstr "" #: ../../../CHANGELOG.md:2451 @@ -7547,38 +4478,23 @@ msgid "2020-11-13" msgstr "" #: ../../../CHANGELOG.md:2455 -msgid "" -"The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-" -"sms-bridge) changed its database from neo4j to h2. You need to sync the " -"bridge at the first start. Note that this only will sync rooms where the " -"@smsbot:yourServer is member. For rooms without @smsbot:yourServer you " -"need to kick and invite the telephone number **or** invite " -"@smsbot:yourServer." +msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer." msgstr "" #: ../../../CHANGELOG.md:2457 -msgid "" -"Add the following to your `vars.yml` file: " -"`matrix_sms_bridge_container_extra_arguments=['--env " -"SPRING_PROFILES_ACTIVE=initialsync']`" +msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`" msgstr "" #: ../../../CHANGELOG.md:2458 -msgid "" -"Login to your host shell and remove old systemd file from your host: `rm " -"/etc/systemd/system/matrix-sms-bridge-database.service`" +msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`" msgstr "" #: ../../../CHANGELOG.md:2459 -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-" -"sms-bridge,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`" msgstr "" #: ../../../CHANGELOG.md:2460 -msgid "" -"Login to your host shell and check the logs with `journalctl -u matrix-" -"sms-bridge` until the sync finished." +msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished." msgstr "" #: ../../../CHANGELOG.md:2461 @@ -7586,9 +4502,7 @@ msgid "Remove the var from the first step." msgstr "" #: ../../../CHANGELOG.md:2462 -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-" -"all,start`." +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`." msgstr "" #: ../../../CHANGELOG.md:2464 @@ -7600,16 +4514,11 @@ msgid "Dynamic DNS support" msgstr "" #: ../../../CHANGELOG.md:2468 -msgid "" -"Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook " -"can now manage Dynamic DNS for you using " -"[ddclient](https://ddclient.net/)." +msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)." msgstr "" #: ../../../CHANGELOG.md:2470 -msgid "" -"To learn more, follow our [Dynamic DNS docs page](docs/configuring-" -"playbook-dynamic-dns.md)." +msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)." msgstr "" #: ../../../CHANGELOG.md:2473 @@ -7617,39 +4526,23 @@ msgid "2020-10-28" msgstr "" #: ../../../CHANGELOG.md:2475 -msgid "" -"(Compatibility Break) https://matrix.example.com/ now redirects to " -"https://element.example.com/" +msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/" msgstr "" #: ../../../CHANGELOG.md:2477 -msgid "" -"Until now, we used to serve a static page coming from Synapse at " -"`https://matrix.example.com/`. This page was not very useful to anyone." +msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone." msgstr "" #: ../../../CHANGELOG.md:2479 -msgid "" -"Since `matrix.example.com` may be accessed by regular users in certain " -"conditions, it's probably better to redirect them to a better place (e.g." -" to [Element Web](docs/configuring-playbook-client-element-web.md))." +msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))." msgstr "" #: ../../../CHANGELOG.md:2481 -msgid "" -"If Element Web is installed (`matrix_client_element_enabled: true`, which" -" it is by default), we now redirect people to it, instead of showing them" -" a Synapse static page." +msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page." msgstr "" #: ../../../CHANGELOG.md:2483 -msgid "" -"If you'd like to control where the redirect goes, use the " -"`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` " -"variable. To restore the old behavior of not redirecting anywhere and " -"serving the Synapse static page, set it to an empty value " -"(`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: " -"\"\"`)." +msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)." msgstr "" #: ../../../CHANGELOG.md:2486 @@ -7657,32 +4550,19 @@ msgid "2020-10-26" msgstr "" #: ../../../CHANGELOG.md:2488 -msgid "" -"(Compatibility Break) /_synapse/admin is no longer publicly exposed by " -"default" +msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default" msgstr "" #: ../../../CHANGELOG.md:2490 -msgid "" -"We used to expose the Synapse Admin APIs publicly (at " -"`https://matrix.example.com/_synapse/admin`). These APIs require " -"authentication with a valid access token, so it's not that big a deal to " -"expose them." +msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them." msgstr "" #: ../../../CHANGELOG.md:2492 -msgid "" -"However, following [official Synapse's reverse-proxying " -"recommendations](https://github.com/element-" -"hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-" -"endpoints), we're no longer exposing `/_synapse/admin` by default." +msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default." msgstr "" #: ../../../CHANGELOG.md:2494 -msgid "" -"If you'd like to restore restore the old behavior and expose " -"`/_synapse/admin` publicly, you can use the following configuration (in " -"your `vars.yml`):" +msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):" msgstr "" #: ../../../CHANGELOG.md:2501 @@ -7694,24 +4574,15 @@ msgid "Minimum Ansible version raised to v2.7.0" msgstr "" #: ../../../CHANGELOG.md:2505 -msgid "" -"We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 " -"and higher, but issues like [#662](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/662) demonstrate that we need at least " -"v2.7.0." +msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0." msgstr "" #: ../../../CHANGELOG.md:2507 -msgid "" -"If you've been using the playbook without getting any errors until now, " -"you're probably on a version higher than that already (or you're not " -"using the `matrix-ma1sd` and `matrix-client-element` roles)." +msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)." msgstr "" #: ../../../CHANGELOG.md:2509 -msgid "" -"Our [Ansible docs page](docs/ansible.md) contains information on how to " -"run a more up-to-date version of Ansible." +msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible." msgstr "" #: ../../../CHANGELOG.md:2512 @@ -7723,18 +4594,11 @@ msgid "Postgres 13 support" msgstr "" #: ../../../CHANGELOG.md:2516 -msgid "" -"The playbook now installs [Postgres " -"13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) " -"by default." +msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default." msgstr "" #: ../../../CHANGELOG.md:2518 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by " -"following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md" -"#upgrading-postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2520 @@ -7746,18 +4610,11 @@ msgid "matrix-registration support" msgstr "" #: ../../../CHANGELOG.md:2524 -msgid "" -"The playbook can now help you set up [matrix-" -"registration](https://github.com/ZerataX/matrix-registration) - an " -"application that lets you keep your Matrix server's registration private," -" but still allow certain users (those having a unique registration link) " -"to register by themselves." +msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves." msgstr "" #: ../../../CHANGELOG.md:2526 -msgid "" -"See our [Setting up matrix-registration](docs/configuring-playbook-" -"matrix-registration.md) documentation page to get started." +msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started." msgstr "" #: ../../../CHANGELOG.md:2529 @@ -7769,17 +4626,11 @@ msgid "rust-synapse-compress-state support" msgstr "" #: ../../../CHANGELOG.md:2533 -msgid "" -"The playbook can now help you use [rust-synapse-compress-" -"state](https://github.com/matrix-org/rust-synapse-compress-state) to " -"compress the state groups in your Synapse database." +msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database." msgstr "" #: ../../../CHANGELOG.md:2535 -msgid "" -"See our [Compressing state with rust-synapse-compress-state](docs" -"/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-" -"state) documentation page to get started." +msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started." msgstr "" #: ../../../CHANGELOG.md:2538 @@ -7791,15 +4642,11 @@ msgid "Synapse Admin support" msgstr "" #: ../../../CHANGELOG.md:2542 -msgid "" -"The playbook can now help you set up [synapse-admin](https://github.com" -"/Awesome-Technologies/synapse-admin)." +msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)." msgstr "" #: ../../../CHANGELOG.md:2544 -msgid "" -"See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-" -"admin.md) documentation to get started." +msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:2547 @@ -7811,15 +4658,11 @@ msgid "matrix-reminder-bot support" msgstr "" #: ../../../CHANGELOG.md:2551 -msgid "" -"The playbook can now help you set up [matrix-reminder-" -"bot](https://github.com/anoadragon453/matrix-reminder-bot)." +msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)." msgstr "" #: ../../../CHANGELOG.md:2553 -msgid "" -"See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-" -"matrix-reminder-bot.md) documentation to get started." +msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started." msgstr "" #: ../../../CHANGELOG.md:2556 @@ -7831,21 +4674,15 @@ msgid "(Compatibility Break) Riot is now Element" msgstr "" #: ../../../CHANGELOG.md:2560 -msgid "" -"As per the official announcement, [Riot has been rebraned to " -"Element](https://element.io/blog/welcome-to-element/)." +msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)." msgstr "" #: ../../../CHANGELOG.md:2562 -msgid "" -"The playbook follows suit. Existing installations have a few options for " -"how to handle this." +msgid "The playbook follows suit. Existing installations have a few options for how to handle this." msgstr "" #: ../../../CHANGELOG.md:2564 -msgid "" -"See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md" -"#migrating-to-element) documentation page for more details." +msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details." msgstr "" #: ../../../CHANGELOG.md:2567 @@ -7857,12 +4694,7 @@ msgid "Steam bridging support via mx-puppet-steam" msgstr "" #: ../../../CHANGELOG.md:2571 -msgid "" -"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " -"playbook now supports bridging to [Steam](https://steamapp.com/) via the " -"[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge." -" See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-" -"bridge-mx-puppet-steam.md) documentation page for getting started." +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2574 @@ -7874,21 +4706,11 @@ msgid "Discord bridging support via mx-puppet-discord" msgstr "" #: ../../../CHANGELOG.md:2578 -msgid "" -"Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the " -"playbook now supports bridging to [Discord](https://discordapp.com/) via " -"the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) " -"bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-" -"playbook-bridge-mx-puppet-discord.md) documentation page for getting " -"started." +msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2580 -msgid "" -"**Note**: this is a new Discord bridge. The playbook still retains " -"Discord bridging via [matrix-appservice-discord](docs/configuring-" -"playbook-bridge-appservice-discord.md). You're free too use the bridge " -"that serves you better, or even both (for different users and use-cases)." +msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)." msgstr "" #: ../../../CHANGELOG.md:2583 @@ -7900,23 +4722,11 @@ msgid "Instagram and Twitter bridging support" msgstr "" #: ../../../CHANGELOG.md:2587 -msgid "" -"Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s " -"efforts, the playbook now supports bridging to " -"[Instagram](https://www.instagram.com/) via the [mx-puppet-" -"instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See " -"our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-" -"bridge-mx-puppet-instagram.md) documentation page for getting started." +msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2589 -msgid "" -"Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the " -"playbook now supports bridging to [Twitter](https://twitter.com/) via the" -" [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) " -"bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-" -"playbook-bridge-mx-puppet-twitter.md) documentation page for getting " -"started." +msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2592 @@ -7924,31 +4734,19 @@ msgid "2020-06-28" msgstr "" #: ../../../CHANGELOG.md:2594 -msgid "" -"(Post Mortem / fixed Security Issue) Re-enabling User Directory search " -"powered by the ma1sd Identity Server" +msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server" msgstr "" #: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625 -msgid "" -"User Directory search requests used to go to the ma1sd identity server by" -" default, which queried its own stores and the Synapse database." +msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database." msgstr "" #: ../../../CHANGELOG.md:2598 -msgid "" -"ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has " -"been fixed in version `2.4.0`, with [this " -"commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd " -"2.4.0` is now the default version for this playbook. For more information" -" on what happened, please check the mentioned issue." +msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue." msgstr "" #: ../../../CHANGELOG.md:2600 -msgid "" -"We are re-enabling user directory search with this update. Those who " -"would like to keep it disabled can use this configuration: " -"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" +msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`" msgstr "" #: ../../../CHANGELOG.md:2602 @@ -7964,20 +4762,11 @@ msgid "SMS bridging requires db reset" msgstr "" #: ../../../CHANGELOG.md:2608 -msgid "" -"The current version of [matrix-sms-bridge](https://github.com/benkuly" -"/matrix-sms-bridge) needs you to delete the database to work as expected." -" Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new " -"requried var `matrix_sms_bridge_default_region`." +msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`." msgstr "" #: ../../../CHANGELOG.md:2610 -msgid "" -"To reuse your existing rooms, invite `@smsbot:yourServer` to the room or " -"write a message. You are also able to use automated room creation with " -"telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a" -" room with `@smsbot:yourServer`. See [the " -"docs](https://github.com/benkuly/matrix-sms-bridge) for more information." +msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information." msgstr "" #: ../../../CHANGELOG.md:2612 @@ -7989,16 +4778,11 @@ msgid "SMS bridging support" msgstr "" #: ../../../CHANGELOG.md:2616 -msgid "" -"Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook " -"now supports bridging to SMS (with one telephone number only) via " -"[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." +msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)." msgstr "" #: ../../../CHANGELOG.md:2618 -msgid "" -"See our [Setting up Matrix SMS bridging](docs/configuring-playbook-" -"bridge-matrix-bridge-sms.md) documentation page for getting started." +msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2621 @@ -8006,31 +4790,19 @@ msgid "2020-05-19" msgstr "" #: ../../../CHANGELOG.md:2623 -msgid "" -"(Compatibility Break / Security Issue) Disabling User Directory search " -"powered by the ma1sd Identity Server" +msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server" msgstr "" #: ../../../CHANGELOG.md:2627 -msgid "" -"ma1sd current has [a security " -"issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak " -"information about all users - including users created by bridges, etc." +msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc." msgstr "" #: ../../../CHANGELOG.md:2629 -msgid "" -"Until the issue gets fixed, we're making User Directory search not go to " -"ma1sd by default. You **need to re-run the playbook and restart services " -"to apply this workaround**." +msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**." msgstr "" #: ../../../CHANGELOG.md:2631 -msgid "" -"*If you insist on restoring the old behavior* (**which has a security " -"issue!**), you *might* use this configuration: " -"`matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ " -"matrix_ma1sd_enabled }}\"`" +msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`" msgstr "" #: ../../../CHANGELOG.md:2634 @@ -8042,14 +4814,7 @@ msgid "Newer IRC bridge (with potential breaking change)" msgstr "" #: ../../../CHANGELOG.md:2638 -msgid "" -"This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made" -" a change to how you define manual mappings. If you added a `mapping` to" -" your configuration, you will need to update it accoring to the [upstream" -" instructions](https://github.com/matrix-org/matrix-appservice-" -"irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include " -"`mappings` in your configuration for IRC, no change is necessary. " -"`mappings` is not part of the default configuration." +msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration." msgstr "" #: ../../../CHANGELOG.md:2647 @@ -8061,16 +4826,11 @@ msgid "Slack bridging support" msgstr "" #: ../../../CHANGELOG.md:2651 -msgid "" -"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " -"playbook now supports bridging to [Slack](https://slack.com) via the [mx-" -"puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge." msgstr "" #: ../../../CHANGELOG.md:2653 -msgid "" -"See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-" -"bridge-mx-puppet-slack.md) documentation page for getting started." +msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2656 @@ -8082,16 +4842,11 @@ msgid "Skype bridging support" msgstr "" #: ../../../CHANGELOG.md:2660 -msgid "" -"Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the " -"playbook now supports bridging to [Skype](https://www.skype.com) via the " -"[mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." +msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge." msgstr "" #: ../../../CHANGELOG.md:2662 -msgid "" -"See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-" -"bridge-mx-puppet-skype.md) documentation page for getting started." +msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started." msgstr "" #: ../../../CHANGELOG.md:2665 @@ -8103,24 +4858,15 @@ msgid "Private Jitsi support" msgstr "" #: ../../../CHANGELOG.md:2669 -msgid "" -"The [Jitsi support](#jitsi-support) we had landed a few weeks ago was " -"working well, but it was always open to the whole world." +msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world." msgstr "" #: ../../../CHANGELOG.md:2671 -msgid "" -"Running such an open instance is not desirable to most people, so " -"[teutat3s](https://github.com/teutat3s) has contributed support for " -"making Jitsi use authentication." +msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication." msgstr "" #: ../../../CHANGELOG.md:2673 -msgid "" -"To make your Jitsi server more private, see the [configure internal Jitsi" -" authentication and guests mode](docs/configuring-playbook-jitsi.md" -"#optional-configure-internal-jitsi-authentication-and-guests-mode) " -"section in our Jitsi documentation." +msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation." msgstr "" #: ../../../CHANGELOG.md:2676 @@ -8132,27 +4878,15 @@ msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" msgstr "" #: ../../../CHANGELOG.md:2680 -msgid "" -"Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the " -"[mxisd](https://github.com/kamax-io/mxisd) identity server, which has " -"been deprecated for a long time, has finally been replaced by " -"[ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." +msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork." msgstr "" #: ../../../CHANGELOG.md:2682 -msgid "" -"**If you're using the default playbook configuration**, you don't need to" -" do anything -- your mxisd installation will be replaced with ma1sd and " -"all existing data will be migrated automatically the next time you run " -"the playbook." +msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2684 -msgid "" -"**If you're doing something more special** (defining custom " -"`matrix_mxisd_*` variables), the playbook will ask you to rename them to " -"`matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well " -"for such a more custom setup." +msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup." msgstr "" #: ../../../CHANGELOG.md:2687 @@ -8164,10 +4898,7 @@ msgid "Archlinux support" msgstr "" #: ../../../CHANGELOG.md:2691 -msgid "" -"Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts," -" the playbook now supports installing to an " -"[Archlinux](https://www.archlinux.org/) server." +msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server." msgstr "" #: ../../../CHANGELOG.md:2694 @@ -8179,16 +4910,11 @@ msgid "Jitsi support" msgstr "" #: ../../../CHANGELOG.md:2698 -msgid "" -"The playbook can now (optionally) install the [Jitsi](https://jitsi.org/)" -" video-conferencing platform and integrate it with [Riot](docs" -"/configuring-playbook-riot-web.md)." +msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)." msgstr "" #: ../../../CHANGELOG.md:2700 -msgid "" -"See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to" -" get started." +msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started." msgstr "" #: ../../../CHANGELOG.md:2703 @@ -8200,18 +4926,11 @@ msgid "Raspberry Pi support" msgstr "" #: ../../../CHANGELOG.md:2707 -msgid "" -"Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the " -"playbook supports installing to a Raspberry Pi server, for at least some " -"of the services." +msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services." msgstr "" #: ../../../CHANGELOG.md:2709 -msgid "" -"Since most ready-made container images do not support that architecture, " -"we achieve this by building images locally on the device itself. See our " -"[Self-building documentation page](docs/self-building.md) for how to get " -"started." +msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started." msgstr "" #: ../../../CHANGELOG.md:2712 @@ -8227,9 +4946,7 @@ msgid "The playbook now makes it easy to install custom riot-web themes." msgstr "" #: ../../../CHANGELOG.md:2718 -msgid "" -"To learn more, take a look at our [riot-web documentation on Themes](docs" -"/configuring-playbook-riot-web.md#themes)." +msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)." msgstr "" #: ../../../CHANGELOG.md:2721 @@ -8241,9 +4958,7 @@ msgid "Customize the server name in Riot's login page" msgstr "" #: ../../../CHANGELOG.md:2725 -msgid "" -"You can now customize the server name string that Riot-web displays in " -"its login page." +msgid "You can now customize the server name string that Riot-web displays in its login page." msgstr "" #: ../../../CHANGELOG.md:2727 @@ -8251,18 +4966,11 @@ msgid "These playbook variables, with these default values, have been added:" msgstr "" #: ../../../CHANGELOG.md:2733 -msgid "" -"The login page previously said \"Sign in to your Matrix account on " -"matrix.example.org\" (the homeserver's domain name). It will now say " -"\"Sign in … on example.org\" (the server name) by default, or \"Sign in …" -" on Our Server\" if you set the variable to \"Our Server\"." +msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"." msgstr "" #: ../../../CHANGELOG.md:2735 -msgid "" -"To support this, the config.json template is changed to use the " -"configuration key `default_server_config` for setting the default HS/IS, " -"and the new configuration key `server_name` is added in there." +msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there." msgstr "" #: ../../../CHANGELOG.md:2738 @@ -8274,16 +4982,11 @@ msgid "Disabling TLSv1.1" msgstr "" #: ../../../CHANGELOG.md:2742 -msgid "" -"To improve security, we've removed TLSv1.1 support from our default " -"matrix-nginx-proxy configuration." +msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration." msgstr "" #: ../../../CHANGELOG.md:2744 -msgid "" -"If you need to support old clients, you can re-enable it with the " -"following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 " -"TLSv1.2 TLSv1.3\"`" +msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`" msgstr "" #: ../../../CHANGELOG.md:2747 @@ -8295,21 +4998,11 @@ msgid "Postgres collation changes (action required!)" msgstr "" #: ../../../CHANGELOG.md:2751 -msgid "" -"By default, we've been using a UTF-8 collation for Postgres. This is " -"known to cause Synapse some troubles (see the [relevant " -"issue](https://github.com/matrix-org/synapse/issues/6722)) on systems " -"that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in " -"an [Alpine Linux](https://alpinelinux.org/) container (which uses " -"[musl](https://www.musl-libc.org/), and not glibc), so our users are " -"likely not affected by the index corruption problem observed by others." +msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others." msgstr "" #: ../../../CHANGELOG.md:2753 -msgid "" -"Still, we might become affected in the future. In any case, it's imminent" -" that Synapse will complain about databases which do not use a C " -"collation." +msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation." msgstr "" #: ../../../CHANGELOG.md:2755 @@ -8317,11 +5010,7 @@ msgid "To avoid future problems, we recommend that you run the following command msgstr "" #: ../../../CHANGELOG.md:2761 -msgid "" -"It forces a [Postgres database upgrade](docs/maintenance-postgres.md" -"#upgrading-postgresql), which would recreate your Postgres database using" -" the proper (`C`) collation. If you are low on disk space, or run into " -"trouble, refer to the Postgres database upgrade documentation page." +msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page." msgstr "" #: ../../../CHANGELOG.md:2764 @@ -8333,19 +5022,11 @@ msgid "Added support for Appservice Webhooks" msgstr "" #: ../../../CHANGELOG.md:2768 -msgid "" -"Thanks to a contribution from [Björn " -"Marten](https://github.com/tripleawwy) from " -"[netresearch](https://www.netresearch.de/), the playbook can now install " -"and configure [matrix-appservice-webhooks](https://github.com/turt2live" -"/matrix-appservice-webhooks) for you. This bridge provides support for " -"Slack-compatible webhooks." +msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" #: ../../../CHANGELOG.md:2770 -msgid "" -"Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-" -"playbook-bridge-appservice-webhooks.md)." +msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)." msgstr "" #: ../../../CHANGELOG.md:2773 @@ -8357,23 +5038,15 @@ msgid "Added support for automatic Double Puppeting for all Mautrix bridges" msgstr "" #: ../../../CHANGELOG.md:2777 -msgid "" -"Double Puppeting can now be easily enabled for all Mautrix bridges " -"supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." +msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." msgstr "" #: ../../../CHANGELOG.md:2779 -msgid "" -"This is possible due to those bridges' integration with [matrix-synapse-" -"shared-secret-auth](https://github.com/devture/matrix-synapse-shared-" -"secret-auth) - yet another component that this playbook can install for " -"you." +msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you." msgstr "" #: ../../../CHANGELOG.md:2781 -msgid "" -"To get started, following the playbook's documentation for the bridge " -"you'd like to configure." +msgid "To get started, following the playbook's documentation for the bridge you'd like to configure." msgstr "" #: ../../../CHANGELOG.md:2784 @@ -8385,25 +5058,15 @@ msgid "Added support for an alternative method for using another webserver" msgstr "" #: ../../../CHANGELOG.md:2788 -msgid "" -"We have added support for making `matrix-nginx-proxy` not being so " -"invasive, so that it would be easier to [use your own webserver](docs" -"/configuring-playbook-own-webserver.md)." +msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)." msgstr "" #: ../../../CHANGELOG.md:2790 -msgid "" -"The documentation has been updated with a **Method 2**, which might make " -"\"own webserver\" setup easier in some cases (such as [reverse-proxying " -"using Traefik](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/296))." +msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))." msgstr "" #: ../../../CHANGELOG.md:2792 -msgid "" -"**Existing users** are not affected by this and **don't need to change " -"anything**. The defaults are still the same (`matrix-nginx-proxy` " -"obtaining SSL certificates and doing everything for you automatically)." +msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)." msgstr "" #: ../../../CHANGELOG.md:2795 @@ -8415,27 +5078,15 @@ msgid "Tightened security around room directory publishing" msgstr "" #: ../../../CHANGELOG.md:2799 -msgid "" -"As per this [advisory blog post](https://matrix.org/blog/2019/11/09" -"/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to" -" change the default publishing rules for the Matrix room directory." +msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory." msgstr "" #: ../../../CHANGELOG.md:2801 -msgid "" -"Our general goal is to favor privacy and security when running personal " -"(family & friends) and corporate homeservers. Both of these likely " -"benefit from having a more secure default of **not showing the room " -"directory without authentication** and **not publishing the room " -"directory over federation**." +msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**." msgstr "" #: ../../../CHANGELOG.md:2803 -msgid "" -"As with anything else, these new defaults can be overriden by changing " -"the `matrix_synapse_allow_public_rooms_without_auth` and " -"`matrix_synapse_allow_public_rooms_over_federation` variables, " -"respectively." +msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively." msgstr "" #: ../../../CHANGELOG.md:2806 @@ -8447,35 +5098,19 @@ msgid "Improved Postgres upgrading/importing" msgstr "" #: ../../../CHANGELOG.md:2810 -msgid "" -"Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) " -"and [importing](docs/importing-postgres.md) have been improved to add " -"support for multiple databases and roles." +msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles." msgstr "" #: ../../../CHANGELOG.md:2812 -msgid "" -"Previously, the playbook would only take care of the `homeserver` " -"database and `synapse` user. We now back up and restore all databases and" -" users on the Postgres server." +msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server." msgstr "" #: ../../../CHANGELOG.md:2814 -msgid "" -"For now, the playbook only uses that one database (`homeserver`) and that" -" one single user (`synapse`), so it's all the same. However, in the " -"future, additional components besides Synapse may also make use the " -"Postgres database server. One such example is the [matrix-appservice-" -"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, " -"which strongly encourages use of Postgres in its v1.0 release. We are yet" -" to upgrade to it." +msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it." msgstr "" #: ../../../CHANGELOG.md:2816 -msgid "" -"Additionally, Postgres [upgrading](docs/maintenance-postgres.md" -"#upgrading-postgresql) now uses gzipped dump files by default, to " -"minimize disk space usage." +msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage." msgstr "" #: ../../../CHANGELOG.md:2819 @@ -8487,17 +5122,11 @@ msgid "Postgres 12 support" msgstr "" #: ../../../CHANGELOG.md:2823 -msgid "" -"The playbook now installs [Postgres " -"12](https://www.postgresql.org/about/news/1976/) by default." +msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default." msgstr "" #: ../../../CHANGELOG.md:2825 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following" -" the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" -"postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2828 @@ -8509,46 +5138,19 @@ msgid "Synapse 1.4.0" msgstr "" #: ../../../CHANGELOG.md:2832 -msgid "" -"Synapse 1.4.0 [is " -"out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots" -" of changes related to privacy." +msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy." msgstr "" #: ../../../CHANGELOG.md:2834 -msgid "" -"Its new defaults (which we adopt as well) mean that certain old data will" -" automatically get purged after a certain number of days. 1.4.0 " -"automatically garbage collects redacted messages (defaults to 7 days) and" -" removes unused IP and user agent information stored in the user_ips " -"table (defaults to 30 days). If you'd like to preserve this data, we " -"encourage you to look at the `redaction_retention_period` and " -"`user_ips_max_age` options (controllable by the " -"`matrix_synapse_redaction_retention_period` and " -"`matrix_synapse_user_ips_max_age` playbook variables, respectively) " -"before doing the upgrade. If you'd like to keep data indefinitely, set " -"these variables to `null` (e.g. " -"`matrix_synapse_redaction_retention_period: ~`)." +msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)." msgstr "" #: ../../../CHANGELOG.md:2836 -msgid "" -"From now on the `trusted_key_servers` setting for Synapse is " -"configurable. It still defaults to `matrix.org` just like it always has, " -"but in a more explicit way now. If you'd like to use another trusted key " -"server, adjust the `matrix_synapse_trusted_key_servers` playbook " -"variable." +msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable." msgstr "" #: ../../../CHANGELOG.md:2838 -msgid "" -"Synapse 1.4.0 also changes lots of things related to identity server " -"integration. Because Synapse will now by default be responsible for " -"validating email addresses for user accounts, running without an identity" -" server looks more feasible. We still [have " -"concerns](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/pull/275/files#r331104117) over disabling the identity server by " -"default, so for now it remains enabled." +msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled." msgstr "" #: ../../../CHANGELOG.md:2841 @@ -8560,23 +5162,15 @@ msgid "Synapse Simple Antispam support" msgstr "" #: ../../../CHANGELOG.md:2845 -msgid "" -"There have been lots of invite-spam attacks lately and " -"[Travis](https://github.com/t2bot) has created a Synapse module " -"([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" -"antispam)) to let people protect themselves." +msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves." msgstr "" #: ../../../CHANGELOG.md:2847 -msgid "" -"From now on, you can easily install and configure this spam checker " -"module through the playbook." +msgid "From now on, you can easily install and configure this spam checker module through the playbook." msgstr "" #: ../../../CHANGELOG.md:2849 -msgid "" -"Learn more in [Setting up Synapse Simple Antispam](docs/configuring-" -"playbook-synapse-simple-antispam.md)." +msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)." msgstr "" #: ../../../CHANGELOG.md:2852 @@ -8588,29 +5182,19 @@ msgid "Extensible Riot-web configuration" msgstr "" #: ../../../CHANGELOG.md:2856 -msgid "" -"Similarly to [Extensible Synapse configuration](#extensible-synapse-" -"configuration) (below), Riot-web configuration is also extensible now." +msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now." msgstr "" #: ../../../CHANGELOG.md:2858 -msgid "" -"From now on, you can extend/override Riot-web's configuration by making " -"use of the `matrix_riot_web_configuration_extension_json` variable. This " -"should be enough for most customization needs." +msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs." msgstr "" #: ../../../CHANGELOG.md:2860 -msgid "" -"If you need even more power, you can now also take full control and " -"override `matrix_riot_web_configuration_default` (or " -"`matrix_riot_web_configuration`) directly." +msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly." msgstr "" #: ../../../CHANGELOG.md:2862 -msgid "" -"Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-" -"web.md)." +msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)." msgstr "" #: ../../../CHANGELOG.md:2865 @@ -8622,31 +5206,19 @@ msgid "Extensible Synapse configuration" msgstr "" #: ../../../CHANGELOG.md:2869 -msgid "" -"Previously, we had to create custom Ansible variables for each and every " -"Synapse setting. This lead to too much effort (and configuration " -"ugliness) to all of Synapse's settings, so naturally, not all features of" -" Synapse could be controlled through the playbook." +msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook." msgstr "" #: ../../../CHANGELOG.md:2871 -msgid "" -"From now on, you can extend/override the Synapse server's configuration " -"by making use of the `matrix_synapse_configuration_extension_yaml` " -"variable. This should be enough for most customization needs." +msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs." msgstr "" #: ../../../CHANGELOG.md:2873 -msgid "" -"If you need even more power, you can now also take full control and " -"override `matrix_synapse_configuration` (or " -"`matrix_synapse_configuration_yaml`) directly." +msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly." msgstr "" #: ../../../CHANGELOG.md:2875 -msgid "" -"Learn more here in [Configuring Synapse](docs/configuring-playbook-" -"synapse.md)." +msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)." msgstr "" #: ../../../CHANGELOG.md:2878 @@ -8654,19 +5226,11 @@ msgid "2019-08-21" msgstr "" #: ../../../CHANGELOG.md:2882 -msgid "" -"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/205) of " -"[kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart " -"Mumford (Cadair)](https://github.com/Cadair), the playbook now supports " -"bridging to [Slack](https://slack.com) via the [appservice-" -"slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge." msgstr "" #: ../../../CHANGELOG.md:2884 -msgid "" -"Additional details are available in [Setting up Appservice Slack " -"bridging](docs/configuring-playbook-bridge-appservice-slack.md)." +msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)." msgstr "" #: ../../../CHANGELOG.md:2886 @@ -8674,19 +5238,11 @@ msgid "Google Hangouts bridging support" msgstr "" #: ../../../CHANGELOG.md:2888 -msgid "" -"Thanks to the [great work](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/pull/251) of [Eduardo Beltrame " -"(Munfred)](https://github.com/Munfred) and [Robbie D " -"(microchipster)](https://github.com/microchipster), the playbook now " -"supports bridging to [Google Hangouts](https://hangouts.google.com/) via " -"the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." +msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge." msgstr "" #: ../../../CHANGELOG.md:2890 -msgid "" -"Additional details are available in [Setting up Mautrix Hangouts " -"bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." +msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." msgstr "" #: ../../../CHANGELOG.md:2893 @@ -8698,9 +5254,7 @@ msgid "Email2Matrix support" msgstr "" #: ../../../CHANGELOG.md:2897 -msgid "" -"Support for [Email2Matrix](https://github.com/devture/email2matrix) has " -"been added." +msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added." msgstr "" #: ../../../CHANGELOG.md:2899 @@ -8708,9 +5262,7 @@ msgid "It's an optional feature that you can enable via the playbook." msgstr "" #: ../../../CHANGELOG.md:2901 -msgid "" -"To learn more, see the [playbook's documentation on Email2Matrix](./docs" -"/configuring-playbook-email2matrix.md)." +msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)." msgstr "" #: ../../../CHANGELOG.md:2904 @@ -8722,17 +5274,11 @@ msgid "Synapse logging level has been reduced to WARNING" msgstr "" #: ../../../CHANGELOG.md:2908 -msgid "" -"After [some discussion in our support " -"room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one)," -" we've decided to change the default logging level for Synapse from " -"`INFO` to `WARNING`." +msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`." msgstr "" #: ../../../CHANGELOG.md:2910 -msgid "" -"This greatly reduces the number of log messages that are being logged, " -"leading to:" +msgid "This greatly reduces the number of log messages that are being logged, leading to:" msgstr "" #: ../../../CHANGELOG.md:2912 @@ -8740,17 +5286,11 @@ msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" msgstr "" #: ../../../CHANGELOG.md:2913 -msgid "" -"easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages," -" as they're not longer buried in thousands of non-important `INFO` " -"messages" +msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages" msgstr "" #: ../../../CHANGELOG.md:2915 -msgid "" -"If you'd like to track down an issue, you [can always increase the " -"logging level as described here](./docs/maintenance-and-" -"troubleshooting.md#increasing-synapse-logging)." +msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)." msgstr "" #: ../../../CHANGELOG.md:2918 @@ -8766,18 +5306,11 @@ msgid "The playbook can now help you with Synapse's maintenance." msgstr "" #: ../../../CHANGELOG.md:2924 -msgid "" -"There's a new documentation page about [Synapse maintenance](./docs" -"/maintenance-synapse.md) and another section on [Postgres " -"vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." +msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../CHANGELOG.md:2926 -msgid "" -"Among other things, if your Postgres database has grown significantly " -"over time, you may wish to [ask the playbook to purge unused data with " -"synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-" -"synapse-janitor) for you." +msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you." msgstr "" #: ../../../CHANGELOG.md:2928 @@ -8789,10 +5322,7 @@ msgid "Some internal playbook control variables have been renamed." msgstr "" #: ../../../CHANGELOG.md:2932 -msgid "" -"This change **only affects people who run this playbook's roles from " -"another playbook**. If you're using this playbook as-is, you're not " -"affected and don't need to do anything." +msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything." msgstr "" #: ../../../CHANGELOG.md:2934 @@ -8832,23 +5362,15 @@ msgid "Synapse no longer logs to text files" msgstr "" #: ../../../CHANGELOG.md:2948 -msgid "" -"Following what the official Synapse Docker image is doing " -"([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've" -" been doing for mostly everything installed by this playbook, **Synapse " -"no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." +msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)." msgstr "" #: ../../../CHANGELOG.md:2950 -msgid "" -"From now on, Synapse would only log to console, which goes to systemd's " -"journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" +msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`" msgstr "" #: ../../../CHANGELOG.md:2952 -msgid "" -"Because of this, the following variables have become obsolete and were " -"removed:" +msgid "Because of this, the following variables have become obsolete and were removed:" msgstr "" #: ../../../CHANGELOG.md:2954 @@ -8860,23 +5382,11 @@ msgid "`matrix_synapse_max_log_files_count`" msgstr "" #: ../../../CHANGELOG.md:2957 -msgid "" -"To prevent confusion, it'd be better if you delete all old files manually" -" after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." +msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)." msgstr "" #: ../../../CHANGELOG.md:2959 -msgid "" -"Because Synapse is incredibly chatty when it comes to logging (here's " -"[one such issue](https://github.com/matrix-org/synapse/issues/4751) " -"describing the problem), if you're running an ancient distribution (like " -"CentOS 7.0), be advised that systemd's journald default logging " -"restrictions may not be high enough to capture all log messages generated" -" by Synapse. This is especially true if you've got a busy (Synapse) " -"server. We advise that you manually add `RateLimitInterval=0` and " -"`RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` " -"file, followed by restarting the logging service (`systemctl restart " -"systemd-journald`)." +msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)." msgstr "" #: ../../../CHANGELOG.md:2962 @@ -8884,16 +5394,11 @@ msgid "2019-06-27" msgstr "" #: ../../../CHANGELOG.md:2964 -msgid "" -"(BC Break) Discord bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:2966 -msgid "" -"Until now, the `config.yaml` file for the [Discord bridge](docs" -"/configuring-playbook-bridge-appservice-discord.md) was managed by the " -"playbook, but the `registration.yaml` file was not." +msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not." msgstr "" #: ../../../CHANGELOG.md:2968 @@ -8901,41 +5406,23 @@ msgid "From now on, the playbook will keep both configuration files sync for you msgstr "" #: ../../../CHANGELOG.md:2970 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/appservice-discord/discord-registration.yaml` configuration file, those " -"would be lost the next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2972 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix" -"/appservice-discord/config`)." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)." msgstr "" #: ../../../CHANGELOG.md:2974 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/appservice-" -"discord/data`). When you run the playbook with an existing database file " -"(`/matrix/appservice-discord/discord.db`), the playbook will stop the " -"bridge and relocate the database file to the `./data` directory. There's " -"no data-loss involved. You'll need to restart the bridge manually though " -"(`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:2976 -msgid "" -"The main directory (`/matrix/appservice-discord`) may contain some " -"leftover files (`user-store.db`, `room-store.db`, `config.yaml`, " -"`discord-registration.yaml`, `invite_link`). These are no longer " -"necessary and can be deleted manually." +msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually." msgstr "" #: ../../../CHANGELOG.md:2978 -msgid "" -"We're now following the default sample configuration for the Discord " -"bridge. If you need to override some values, define them in " -"`matrix_appservice_discord_configuration_extension_yaml`." +msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`." msgstr "" #: ../../../CHANGELOG.md:2981 @@ -8943,16 +5430,11 @@ msgid "2019-06-24" msgstr "" #: ../../../CHANGELOG.md:2983 -msgid "" -"(BC Break) WhatsApp bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:2985 -msgid "" -"Until now, configuration files for the [WhatsApp bridge](docs" -"/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004 @@ -8961,31 +5443,15 @@ msgid "From now on, the playbook will keep the configuration in sync for you." msgstr "" #: ../../../CHANGELOG.md:2989 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-" -"whatsapp/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:2991 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"whatsapp/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:2993 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"whatsapp/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:2995 @@ -8997,65 +5463,31 @@ msgid "2019-06-20" msgstr "" #: ../../../CHANGELOG.md:3000 -msgid "" -"(BC Break) IRC bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3002 -msgid "" -"Until now, configuration files for the [IRC bridge](docs/configuring-" -"playbook-bridge-appservice-irc.md) were created by the playbook " -"initially, but never modified later on." +msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3006 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/appservice-irc/config.yaml` or `/matrix/appservice-" -"irc/registration.yaml` configuration files, those would be lost the next " -"time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3008 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix" -"/appservice-irc/config`), so your old configuration remains in the base " -"directory (`/matrix/appservice-irc`)." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)." msgstr "" #: ../../../CHANGELOG.md:3010 -msgid "" -"Previously, we asked people to configure bridged IRC servers by extending" -" the bridge configuration " -"(`matrix_appservice_irc_configuration_extension_yaml`). While this is " -"still possible and will continue working forever, **we now recommend " -"defining IRC servers in the easier to use " -"`matrix_appservice_irc_ircService_servers` variable**. See [our IRC " -"bridge documentation page](docs/configuring-playbook-bridge-appservice-" -"irc.md) for an example." +msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example." msgstr "" #: ../../../CHANGELOG.md:3012 -msgid "" -"If you decide to continue using " -"`matrix_appservice_irc_configuration_extension_yaml`, you might be " -"interested to know that `ircService.databaseUri` and a few other keys now" -" have default values in the base configuration " -"(`matrix_appservice_irc_configuration_yaml`). You may wish to stop " -"redefining those keys, unless you really intend to override them. You " -"most likely only need to override `ircService.servers`." +msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`." msgstr "" #: ../../../CHANGELOG.md:3014 -msgid "" -"Bridge data (`passkey.pem` and database files) is now also stored in a " -"subdirectory (`/matrix/appservice-irc/data`). When you run the playbook " -"with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook " -"will stop the bridge and relocate the passkey and database files " -"(`rooms.db` and `users.db`) to the `./data` directory. There's no data-" -"loss involved. You'll need to restart the bridge manually though " -"(`--tags=start`)." +msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3017 @@ -9063,85 +5495,47 @@ msgid "2019-06-15" msgstr "" #: ../../../CHANGELOG.md:3019 -msgid "" -"(BC Break) Telegram bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3021 -msgid "" -"Until now, configuration files for the [Telegram bridge](docs" -"/configuring-playbook-bridge-mautrix-telegram.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3025 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-telegram/config.yaml` or `/matrix/mautrix-" -"telegram/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3027 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"telegram/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-telegram`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_telegram_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:3029 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"telegram/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3031 -msgid "" -"Also, we're now following the default configuration for the Telegram " -"bridge, so some default configuration values are different:" +msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:" msgstr "" #: ../../../CHANGELOG.md:3033 -msgid "" -"`edits_as_replies` (used to be `false`, now `true`) - previously replies " -"were not sent over to Matrix at all; ow they are sent over as a reply to " -"the original message" +msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message" msgstr "" #: ../../../CHANGELOG.md:3034 -msgid "" -"`inline_images` (used to be `true`, now `false`) - this has to do with " -"captioned images. Inline-image (included caption) are said to exhibit " -"troubles on Riot iOS. When `false`, the caption arrives on the Matrix " -"side as a separate message." +msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message." msgstr "" #: ../../../CHANGELOG.md:3035 -msgid "" -"`authless_portals` (used to be `false`, now `true`) - creating portals " -"from the Telegram side is now possible" +msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible" msgstr "" #: ../../../CHANGELOG.md:3036 -msgid "" -"`whitelist_group_admins` (used to be `false`, now `true`) - allows " -"Telegram group admins to use the bot commands" +msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands" msgstr "" #: ../../../CHANGELOG.md:3038 -msgid "" -"If the new values are not to your liking, use " -"`matrix_mautrix_telegram_configuration_extension_yaml` to specify an " -"override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure" -" out which variable goes where)." +msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)." msgstr "" #: ../../../CHANGELOG.md:3041 @@ -9153,45 +5547,23 @@ msgid "Synapse v1.0" msgstr "" #: ../../../CHANGELOG.md:3045 -msgid "" -"With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11" -"/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people " -"being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` " -"DNS SRV record that we've been keeping for compatibility with old Synapse" -" versions (<= 0.34)." +msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)." msgstr "" #: ../../../CHANGELOG.md:3047 -msgid "" -"According to the [Server Discovery " -"specification](https://matrix.org/docs/spec/server_server/r0.1.2.html" -"#server-discovery), it's no harm to keep the DNS SRV record. But since " -"it's not necessary for federating with the larger Matrix network anymore," -" you should be safe to get rid of it." +msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it." msgstr "" #: ../../../CHANGELOG.md:3049 -msgid "" -"**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` " -"DNS SRV records. The latter, **must not** be removed." +msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed." msgstr "" #: ../../../CHANGELOG.md:3051 -msgid "" -"For completeness, we must say that using a `_matrix._tcp` [SRV record for" -" Server Delegation](docs/howto-server-delegation.md#server-delegation-" -"via-a-dns-srv-record-advanced) is still valid and useful for certain " -"deployments. It's just that our guide recommends the [`/.well-" -"known/matrix/server` Server Delegation method](docs/howto-server-" -"delegation.md#server-delegation-via-a-well-known-file), due to its easier" -" implementation when using this playbook." +msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook." msgstr "" #: ../../../CHANGELOG.md:3053 -msgid "" -"Besides this optional/non-urgent DNS change, assuming you're already on " -"Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-" -"running the playbook](docs/maintenance-upgrading-services.md)." +msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)." msgstr "" #: ../../../CHANGELOG.md:3056 @@ -9199,44 +5571,23 @@ msgid "2019-06-07" msgstr "" #: ../../../CHANGELOG.md:3058 -msgid "" -"(BC Break) Facebook bridge configuration is now entirely managed by the " -"playbook" +msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook" msgstr "" #: ../../../CHANGELOG.md:3060 -msgid "" -"Until now, configuration files for the [Facebook bridge](docs" -"/configuring-playbook-bridge-mautrix-facebook.md) were created by the " -"playbook initially, but never modified later on." +msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on." msgstr "" #: ../../../CHANGELOG.md:3064 -msgid "" -"This means that if you were making manual changes to the `/matrix" -"/mautrix-facebook/config.yaml` or `/matrix/mautrix-" -"facebook/registration.yaml` configuration files, those would be lost the " -"next time you run the playbook." +msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook." msgstr "" #: ../../../CHANGELOG.md:3066 -msgid "" -"The bridge now stores configuration in a subdirectory (`/matrix/mautrix-" -"facebook/config`), so your old configuration remains in the base " -"directory (`/matrix/mautrix-facebook`). You need to migrate any manual " -"changes over to the new " -"`matrix_mautrix_facebook_configuration_extension_yaml` variable, so that " -"the playbook would apply them for you." +msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you." msgstr "" #: ../../../CHANGELOG.md:3068 -msgid "" -"Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-" -"facebook/data`). When you run the playbook with an existing database file" -" (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop" -" the bridge and relocate the database file to the `./data` directory. " -"There's no data-loss involved. You'll need to restart the bridge manually" -" though (`--tags=start`)." +msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3071 @@ -9248,33 +5599,19 @@ msgid "Support for exposing container ports publicly (not just to the host)" msgstr "" #: ../../../CHANGELOG.md:3075 -msgid "" -"Until now, various roles supported a `matrix_*_expose_port` variable, " -"which would expose their container's port to the host. This was mostly " -"useful for reverse-proxying manually (in case `matrix-nginx-proxy` was " -"disabled). It could also be used for installing some playbook services " -"(e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." +msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup." msgstr "" #: ../../../CHANGELOG.md:3077 -msgid "" -"`matrix_*_expose_port` variables were not granular enough - sometimes " -"they would expose one port, other times multiple. They also didn't " -"provide control over **where** to expose (to which port number and to " -"which network interface), because they would usually hardcode something " -"like `127.0.0.1:8080`." +msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`." msgstr "" #: ../../../CHANGELOG.md:3079 -msgid "" -"All such variables have been superseded by a better (more flexible) way " -"to do it." +msgid "All such variables have been superseded by a better (more flexible) way to do it." msgstr "" #: ../../../CHANGELOG.md:3081 -msgid "" -"**Most** people (including those not using `matrix-nginx-proxy`), **don't" -" need** to bother with this." +msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this." msgstr "" #: ../../../CHANGELOG.md:3083 @@ -9282,70 +5619,43 @@ msgid "Porting examples follow for people having more customized setups:" msgstr "" #: ../../../CHANGELOG.md:3085 -msgid "" -"**from** `matrix_synapse_container_expose_client_api_port: true` **to** " -"`matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" +msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`" msgstr "" #: ../../../CHANGELOG.md:3087 -msgid "" -"**from** `matrix_synapse_container_expose_federation_api_port: true` " -"**to** `matrix_synapse_container_federation_api_plain_host_bind_port: " -"'127.0.0.1:8048'` and possibly " -"`matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" +msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`" msgstr "" #: ../../../CHANGELOG.md:3089 -msgid "" -"**from** `matrix_synapse_container_expose_metrics_port: true` **to** " -"`matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" +msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`" msgstr "" #: ../../../CHANGELOG.md:3091 -msgid "" -"**from** `matrix_riot_web_container_expose_port: true` **to** " -"`matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" +msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`" msgstr "" #: ../../../CHANGELOG.md:3093 -msgid "" -"**from** `matrix_mxisd_container_expose_port: true` **to** " -"`matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" +msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" msgstr "" #: ../../../CHANGELOG.md:3095 -msgid "" -"**from** `matrix_dimension_container_expose_port: true` **to** " -"`matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" +msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" msgstr "" #: ../../../CHANGELOG.md:3097 -msgid "" -"**from** `matrix_corporal_container_expose_ports: true` **to** " -"`matrix_corporal_container_http_gateway_host_bind_port: " -"'127.0.0.1:41080'` and possibly " -"`matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" +msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`" msgstr "" #: ../../../CHANGELOG.md:3099 -msgid "" -"**from** `matrix_appservice_irc_container_expose_client_server_api_port: " -"true` **to** `matrix_appservice_irc_container_http_host_bind_port: " -"'127.0.0.1:9999'`" +msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`" msgstr "" #: ../../../CHANGELOG.md:3101 -msgid "" -"**from** " -"`matrix_appservice_discord_container_expose_client_server_api_port: true`" -" **to** `matrix_appservice_discord_container_http_host_bind_port: " -"'127.0.0.1:9005'`" +msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`" msgstr "" #: ../../../CHANGELOG.md:3103 -msgid "" -"As always, if you forget to remove usage of some outdated variable, the " -"playbook will warn you." +msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you." msgstr "" #: ../../../CHANGELOG.md:3106 @@ -9357,17 +5667,11 @@ msgid "(BC Break) Ansible 2.8 compatibility" msgstr "" #: ../../../CHANGELOG.md:3110 -msgid "" -"Thanks to [@danbob](https://github.com/danbob), the playbook now " -"[supports the new Ansible 2.8](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/pull/187)." +msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)." msgstr "" #: ../../../CHANGELOG.md:3112 -msgid "" -"A manual change is required to the `inventory/hosts` file, changing the " -"group name from `matrix-servers` to `matrix_servers` (dash to " -"underscore)." +msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)." msgstr "" #: ../../../CHANGELOG.md:3114 @@ -9391,30 +5695,19 @@ msgid "Synapse no longer required" msgstr "" #: ../../../CHANGELOG.md:3123 -msgid "" -"The playbook no longer insists on installing [Synapse](https://github.com" -"/element-hq/synapse) via the `matrix-synapse` role." +msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role." msgstr "" #: ../../../CHANGELOG.md:3125 -msgid "" -"If you would prefer to install Synapse another way and just use the " -"playbook to install other services, it should be possible " -"(`matrix_synapse_enabled: false`)." +msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)." msgstr "" #: ../../../CHANGELOG.md:3127 -msgid "" -"Note that it won't necessarily be the best experience, since the playbook" -" wires things to Synapse by default. If you're using your own Synapse " -"instance (especially one not running in a container), you may have to " -"override many variables to point them to the correct place." +msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place." msgstr "" #: ../../../CHANGELOG.md:3129 -msgid "" -"Having Synapse not be a required component potentially opens the door for" -" installing alternative Matrix homeservers." +msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers." msgstr "" #: ../../../CHANGELOG.md:3131 @@ -9422,16 +5715,11 @@ msgid "Bridges are now separate from the Synapse role" msgstr "" #: ../../../CHANGELOG.md:3133 -msgid "" -"Bridges are no longer part of the `matrix-synapse` role. Each bridge now " -"lives in its own separate role (`roles/custom/matrix-bridge-*`)." +msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)." msgstr "" #: ../../../CHANGELOG.md:3135 -msgid "" -"These bridge roles are independent of the `matrix-synapse` role, so it " -"should be possible to use them with a Synapse instance installed another " -"way (not through the playbook)." +msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)." msgstr "" #: ../../../CHANGELOG.md:3137 @@ -9443,21 +5731,15 @@ msgid "For better consistency, the following variables have been renamed:" msgstr "" #: ../../../CHANGELOG.md:3141 -msgid "" -"`matrix_enable_room_list_search` was renamed to " -"`matrix_synapse_enable_room_list_search`" +msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`" msgstr "" #: ../../../CHANGELOG.md:3142 -msgid "" -"`matrix_alias_creation_rules` was renamed to " -"`matrix_synapse_alias_creation_rules`" +msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`" msgstr "" #: ../../../CHANGELOG.md:3143 -msgid "" -"`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was " -"renamed to `matrix_synapse_room_list_publication_rules`" +msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`" msgstr "" #: ../../../CHANGELOG.md:3146 @@ -9465,9 +5747,7 @@ msgid "2019-05-09" msgstr "" #: ../../../CHANGELOG.md:3148 -msgid "" -"Besides a myriad of bug fixes and minor improvements, here are the more " -"notable (bigger) features we can announce today." +msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today." msgstr "" #: ../../../CHANGELOG.md:3150 @@ -9475,18 +5755,11 @@ msgid "Mautrix Facebook/Messenger bridging support" msgstr "" #: ../../../CHANGELOG.md:3152 -msgid "" -"The playbook now supports bridging with " -"[Facebook](https://www.facebook.com/) by installing the [mautrix-" -"facebook](https://github.com/tulir/mautrix-facebook) bridge. This " -"playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3154 -msgid "" -"Additional details are available in [Setting up Mautrix Facebook " -"bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." +msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." msgstr "" #: ../../../CHANGELOG.md:3156 @@ -9494,16 +5767,11 @@ msgid "mxisd Registration feature integration" msgstr "" #: ../../../CHANGELOG.md:3158 -msgid "" -"The playbook can now help you integrate with mxisd's " -"[Registration](https://github.com/kamax-" -"matrix/mxisd/blob/master/docs/features/registration.md) feature." +msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature." msgstr "" #: ../../../CHANGELOG.md:3160 -msgid "" -"Learn more in [mxisd-controlled Registration](docs/configuring-playbook-" -"mxisd.md#mxisd-controlled-registration)." +msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)." msgstr "" #: ../../../CHANGELOG.md:3163 @@ -9515,10 +5783,7 @@ msgid "Caddy webserver examples" msgstr "" #: ../../../CHANGELOG.md:3167 -msgid "" -"If you prefer using the [Caddy](https://caddyserver.com/) webserver " -"instead of our own integrated nginx, we now have examples for it in the " -"[`examples/caddy`](examples/caddy) directory" +msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory" msgstr "" #: ../../../CHANGELOG.md:3169 @@ -9530,10 +5795,7 @@ msgid "Goofys support for other S3-compatible object stores" msgstr "" #: ../../../CHANGELOG.md:3173 -msgid "" -"Until now, you could optionally host Synapse's media repository on Amazon" -" S3, but we now also support [using other S3-compatible object " -"stores](docs/configuring-playbook-s3.md)," +msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md)," msgstr "" #: ../../../CHANGELOG.md:3176 @@ -9545,18 +5807,11 @@ msgid "Ansible >= 2.5 is required" msgstr "" #: ../../../CHANGELOG.md:3180 -msgid "" -"Due to recent playbook improvements and the fact that the world keeps " -"turning, we're bumping the [version requirement for " -"Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." +msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)." msgstr "" #: ../../../CHANGELOG.md:3182 -msgid "" -"We've also started building our own Docker image of Ansible " -"([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is " -"useful for people who can't upgrade their local Ansible installation (see" -" [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." +msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))." msgstr "" #: ../../../CHANGELOG.md:3185 @@ -9568,46 +5823,27 @@ msgid "TLS support for Coturn" msgstr "" #: ../../../CHANGELOG.md:3189 -msgid "" -"We've added TLS support to the Coturn TURN server installed by the " -"playbook by default. The certificates from the Matrix domain will be used" -" for the Coturn server." +msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server." msgstr "" #: ../../../CHANGELOG.md:3191 -msgid "" -"This feature is enabled by default for new installations. To make use of " -"TLS support for your existing Matrix server's Coturn, make sure to " -"rebuild both Coturn and Synapse:" +msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:" msgstr "" #: ../../../CHANGELOG.md:3197 -msgid "" -"People who have an extra firewall (besides the iptables firewall, which " -"Docker manages automatically), will need to open these additional " -"firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over " -"UDP)." +msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)." msgstr "" #: ../../../CHANGELOG.md:3199 -msgid "" -"People who build their own custom playbook from our roles should be aware" -" that:" +msgid "People who build their own custom playbook from our roles should be aware that:" msgstr "" #: ../../../CHANGELOG.md:3201 -msgid "" -"the `matrix-coturn` role and actually starting Coturn (e.g. " -"`--tags=start`), requires that certificates are already put in place. For" -" this reason, it's usually a good idea to have the `matrix-coturn` role " -"execute after `matrix-nginx-proxy` (which retrieves the certificates)." +msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)." msgstr "" #: ../../../CHANGELOG.md:3203 -msgid "" -"there are a few variables that can help you enable TLS support for " -"Coturn. See the `matrix-coturn` section in [group_vars/matrix-" -"servers](./group_vars/matrix-servers)." +msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)." msgstr "" #: ../../../CHANGELOG.md:3206 @@ -9619,19 +5855,11 @@ msgid "matrix-nginx-proxy support for serving the base domain" msgstr "" #: ../../../CHANGELOG.md:3210 -msgid "" -"If you don't have a dedicated server for your base domain and want to set" -" up [Server Delegation via a well-known file](docs/howto-server-" -"delegation.md#server-delegation-via-a-well-known-file), the playbook has " -"got you covered now." +msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now." msgstr "" #: ../../../CHANGELOG.md:3212 -msgid "" -"It's now possible for the playbook to obtain an SSL certificate and serve" -" the necessary files for Matrix Server Delegation on your base domain. " -"Take a look at the new [Serving the base domain](docs/configuring-" -"playbook-base-domain-serving.md) documentation page." +msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3214 @@ -9639,17 +5867,11 @@ msgid "(BC break) matrix-nginx-proxy data variable renamed" msgstr "" #: ../../../CHANGELOG.md:3216 -msgid "" -"`matrix_nginx_proxy_data_path` was renamed to " -"`matrix_nginx_proxy_base_path`." +msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`." msgstr "" #: ../../../CHANGELOG.md:3218 -msgid "" -"There's a new `matrix_nginx_proxy_data_path` variable, which has a " -"different use-purpose now (it's a subdirectory of " -"`matrix_nginx_proxy_base_path` and is meant for storing various data " -"files)." +msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)." msgstr "" #: ../../../CHANGELOG.md:3221 @@ -9661,11 +5883,7 @@ msgid "Dimension integration manager support" msgstr "" #: ../../../CHANGELOG.md:3225 -msgid "" -"Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can " -"now (optionally) install the [Dimension](https://dimension.t2bot.io/) " -"integration manager. To learn more, see the [Setting up Dimension](docs" -"/configuring-playbook-dimension.md) documentation page." +msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3228 @@ -9677,11 +5895,7 @@ msgid "Ability to customize mxisd's email templates" msgstr "" #: ../../../CHANGELOG.md:3232 -msgid "" -"Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's " -"email templates can now be customized easily. To learn more, see the " -"[Customizing email templates](docs/configuring-playbook-mxisd.md" -"#customizing-email-templates) documentation page." +msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page." msgstr "" #: ../../../CHANGELOG.md:3235 @@ -9693,12 +5907,7 @@ msgid "Discord bridging support" msgstr "" #: ../../../CHANGELOG.md:3239 -msgid "" -"[@Lionstiger](https://github.com/Lionstiger) has done some great work " -"adding Discord bridging support via [matrix-appservice-" -"discord](https://github.com/matrix-org/matrix-appservice-discord). To " -"learn more, see the [Setting up Appservice Discord bridging](docs" -"/configuring-playbook-bridge-appservice-discord.md) documentation page." +msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3242 @@ -9731,15 +5940,11 @@ msgid "from `hostname_riot` to `matrix_server_fqn_riot`" msgstr "" #: ../../../CHANGELOG.md:3252 -msgid "" -"from `host_specific_matrix_ssl_lets_encrypt_support_email` to " -"`matrix_ssl_lets_encrypt_support_email`" +msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`" msgstr "" #: ../../../CHANGELOG.md:3254 -msgid "" -"Doing that, we've simplified things, made names less confusing " -"(hopefully) and moved all variable names under the `matrix_` prefix." +msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix." msgstr "" #: ../../../CHANGELOG.md:3257 @@ -9755,16 +5960,11 @@ msgid "You can now use the brand new and redesigned Riot." msgstr "" #: ../../../CHANGELOG.md:3263 -msgid "" -"The new version no longer has a homepage by default, so we've also " -"removed the custom homepage that we've been installing." +msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing." msgstr "" #: ../../../CHANGELOG.md:3265 -msgid "" -"However, we still provide you with hooks to install your own `home.html` " -"file by specifying the `matrix_riot_web_embedded_pages_home_path` " -"variable (used to be called `matrix_riot_web_homepage_template` before)." +msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)." msgstr "" #: ../../../CHANGELOG.md:3268 @@ -9776,18 +5976,11 @@ msgid "Synapse v0.99.1" msgstr "" #: ../../../CHANGELOG.md:3272 -msgid "" -"As we're moving toward Synapse v1.0, things are beginning to stabilize. " -"Upgrading from v0.99.0 to v0.99.1 should be painless." +msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless." msgstr "" #: ../../../CHANGELOG.md:3274 -msgid "" -"If you've been overriding the default configuration so that you can " -"terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), " -"you'll now have to replace this custom configuration with " -"`matrix_synapse_tls_federation_listener_enabled: true`. The " -"`matrix_synapse_no_tls` variable is no more." +msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more." msgstr "" #: ../../../CHANGELOG.md:3277 @@ -9799,67 +5992,27 @@ msgid "Synapse v0.99 support and preparation for Synapse v1.0" msgstr "" #: ../../../CHANGELOG.md:3281 -msgid "" -"Matrix is undergoing a lot of changes as it matures towards Synapse v1.0." -" The first step is the Synapse v0.99 transitional release, which this " -"playbook now supports." +msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports." msgstr "" #: ../../../CHANGELOG.md:3283 -msgid "" -"If you've been using this playbook successfully until now, you'd be aware" -" that we've been doing [Server Delegation](docs/howto-server-" -"delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring" -" DNS](docs/configuring-dns.md))." +msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))." msgstr "" #: ../../../CHANGELOG.md:3285 -msgid "" -"Due to changes related to certificate file requirements that will affect " -"us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV " -"record in the future** (when Synapse goes to v1.0 - around 5th of March " -"2019). We **still need to keep the SRV record for now**, for backward " -"compatibility with older Synapse versions (lower than v0.99)." +msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)." msgstr "" #: ../../../CHANGELOG.md:3287 -msgid "" -"**What you need to do now** is make use of this transitional Synapse " -"v0.99 release to **prepare your federation settings for the future**. You" -" have 2 choices to prepare yourself for compatibility with the future " -"Synapse v1.0:" +msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:" msgstr "" #: ../../../CHANGELOG.md:3289 -msgid "" -"(recommended) set up [Server Delegation via a well-known file](docs" -"/howto-server-delegation.md#server-delegation-via-a-well-known-file), " -"unless you are affected by the [Downsides of well-known-based Server " -"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" -"based-server-delegation). If you had previously set up the well-known " -"`client` file, depending on how you've done it, it may be that there is " -"nothing new required of you (besides [upgrading](docs/maintenance-" -"upgrading-services.md)). After upgrading, you can [run a self-check](docs" -"/maintenance-checking-services.md), which will tell you if you need to do" -" anything extra with regard to setting up [Server Delegation via a well-" -"known file](docs/howto-server-delegation.md#server-delegation-via-a-well-" -"known-file). After some time, when most people have upgraded to Synapse " -"v0.99 and older releases have disappeared, be prepared to drop your " -"`_matrix._tcp` SRV record." +msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record." msgstr "" #: ../../../CHANGELOG.md:3291 -msgid "" -"(more advanced) if the [Downsides of well-known-based Server " -"Delegation](docs/howto-server-delegation.md#downsides-of-well-known-" -"based-server-delegation) are not to your liking, **as an alternative**, " -"you can set up [Server Delegation via a DNS SRV record](docs/howto-" -"server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In" -" such a case, you get to keep using your existing `_matrix._tcp` DNS SRV " -"record forever and need to NOT set up a `/.well-known/matrix/server` " -"file. Don't forget that you need to do certificate changes though. Follow" -" the guide at [Server Delegation via a DNS SRV record](docs/howto-server-" -"delegation.md#server-delegation-via-a-dns-srv-record-advanced)." +msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)." msgstr "" #: ../../../CHANGELOG.md:3294 @@ -9871,10 +6024,7 @@ msgid "TLS v1.3 support" msgstr "" #: ../../../CHANGELOG.md:3298 -msgid "" -"Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has " -"[added support for TLS v1.3](https://github.com/nginxinc/docker-" -"nginx/issues/190), we have enabled that protocol by default." +msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default." msgstr "" #: ../../../CHANGELOG.md:3300 @@ -9882,33 +6032,15 @@ msgid "When using:" msgstr "" #: ../../../CHANGELOG.md:3302 -msgid "" -"the **integrated nginx server**: TLS v1.3 support might not kick in " -"immediately, because the nginx version hasn't been bumped and you may " -"have an older build of the nginx Docker image (currently " -"`nginx:1.15.8-alpine`). Typically, we do not re-pull images that you " -"already have. When the nginx version gets bumped in the future, everyone " -"will get the update. Until then, you could manually force-pull the " -"rebuilt Docker image by running this on the server: `docker pull " -"nginx:1.15.8-alpine`." +msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`." msgstr "" #: ../../../CHANGELOG.md:3304 -msgid "" -"**your own external nginx server**: if your external nginx server is too " -"old, the new configuration we generate for you in `/matrix/nginx-" -"proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and " -"your nginx version might not support that. You can adjust the SSL " -"protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` " -"variable. Learn more in the documentation page for [Using your own " -"webserver, instead of this playbook's nginx proxy](docs/configuring-" -"playbook-own-webserver.md)" +msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)" msgstr "" #: ../../../CHANGELOG.md:3306 -msgid "" -"**another web server**: you don't need to do anything to accommodate this" -" change" +msgid "**another web server**: you don't need to do anything to accommodate this change" msgstr "" #: ../../../CHANGELOG.md:3309 @@ -9920,12 +6052,7 @@ msgid "IRC bridging support" msgstr "" #: ../../../CHANGELOG.md:3313 -msgid "" -"[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some " -"great work bringing IRC bridging support via [matrix-appservice-" -"irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, " -"see the [Setting up Appservice IRC bridging](docs/configuring-playbook-" -"bridge-appservice-irc.md) documentation page." +msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:3316 @@ -9933,44 +6060,23 @@ msgid "2019-01-29" msgstr "" #: ../../../CHANGELOG.md:3318 -msgid "" -"Running container processes as non-root, without capabilities and read-" -"only" +msgid "Running container processes as non-root, without capabilities and read-only" msgstr "" #: ../../../CHANGELOG.md:3320 -msgid "" -"To improve security, this playbook no longer starts container processes " -"as the `root` user. Most containers were dropping privileges anyway, but " -"we were trusting them with `root` privileges until they would do that. " -"Not anymore -- container processes now start as a non-root user (usually " -"`matrix`) from the get-go." +msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go." msgstr "" #: ../../../CHANGELOG.md:3322 -msgid "" -"For additional security, various capabilities are also dropped (see [why " -"it's important](https://github.com/projectatomic/atomic-site/issues/203))" -" for all containers." +msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers." msgstr "" #: ../../../CHANGELOG.md:3324 -msgid "" -"Additionally, most containers now use a read-only filesystem (see [why " -"it's important](https://www.projectatomic.io/blog/2015/12/making-docker-" -"images-write-only-in-production/)). Containers are given write access " -"only to the directories they need to write to." +msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to." msgstr "" #: ../../../CHANGELOG.md:3326 -msgid "" -"A minor breaking change is the " -"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` " -"variable having being renamed to " -"`matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` " -"(note the `_mb` suffix). The new variable expects a number value (e.g. " -"`25M` -> `25`). If you weren't customizing this variable, this wouldn't " -"affect you." +msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you." msgstr "" #: ../../../CHANGELOG.md:3328 @@ -9978,28 +6084,15 @@ msgid "matrix-mailer is now based on Exim, not Postfix" msgstr "" #: ../../../CHANGELOG.md:3330 -msgid "" -"While we would have preferred to stay with " -"[Postfix](http://www.postfix.org/), we found out that it cannot run as a " -"non-root user. We've had to replace it with [Exim](https://www.exim.org/)" -" (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" -"relay) container image)." +msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)." msgstr "" #: ../../../CHANGELOG.md:3332 -msgid "" -"The internal `matrix-mailer` service (running in a container) now listens" -" on port `8025` (used to be `587` before). The playbook will update your " -"Synapse and mxisd email settings to match (`matrix-mailer:587` -> " -"`matrix-mailer:8025`)." +msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)." msgstr "" #: ../../../CHANGELOG.md:3334 -msgid "" -"Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-" -"relay) container image instead of " -"[panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us " -"a nice disk usage reduction (~200MB -> 8MB)." +msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)." msgstr "" #: ../../../CHANGELOG.md:3337 @@ -10011,34 +6104,19 @@ msgid "(BC Break) Making the playbook's roles more independent of one another" msgstr "" #: ../../../CHANGELOG.md:3341 -msgid "" -"The following change **affects people running a more non-standard setup**" -" - external Postgres or using our roles in their own other playbook. " -"**Most users don't need to do anything**, besides becoming aware of the " -"new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-" -"servers)." +msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)." msgstr "" #: ../../../CHANGELOG.md:3344 -msgid "" -"Because people like using the playbook's components independently " -"(outside of this playbook) and because it's much better for " -"maintainability, we've continued working on separating them. Still, we'd " -"like to offer a turnkey solution for running a fully-featured Matrix " -"server, so this playbook remains important for wiring up the various " -"components." +msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components." msgstr "" #: ../../../CHANGELOG.md:3346 -msgid "" -"With the new changes, **all roles are now only dependent on the minimal " -"`matrix-base` role**. They are no longer dependent among themselves." +msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves." msgstr "" #: ../../../CHANGELOG.md:3348 -msgid "" -"In addition, the following components can now be completely disabled (for" -" those who want/need to):" +msgid "In addition, the following components can now be completely disabled (for those who want/need to):" msgstr "" #: ../../../CHANGELOG.md:3349 @@ -10058,39 +6136,19 @@ msgid "The following changes had to be done:" msgstr "" #: ../../../CHANGELOG.md:3355 -msgid "" -"glue variables had to be introduced to the playbook, so it can wire " -"together the various components. Those glue vars are stored in the " -"[`group_vars/matrix-servers`](group_vars/matrix-servers) file. When " -"overriding variables for a given component (role), you need to be aware " -"of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's " -"corresponding section in the [`group_vars/matrix-servers`](group_vars" -"/matrix-servers) file." +msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file." msgstr "" #: ../../../CHANGELOG.md:3357 -msgid "" -"`matrix_postgres_use_external` has been superceeded by the more " -"consistently named `matrix_postgres_enabled` variable and a few other " -"`matrix_synapse_database_` variables. See the [Using an external " -"PostgreSQL server (optional)](docs/configuring-playbook-external-" -"postgres.md) documentation page for an up-to-date replacement." +msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement." msgstr "" #: ../../../CHANGELOG.md:3359 -msgid "" -"Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are " -"no longer installed if you're not enabling the `matrix-postgres` role " -"(`matrix_postgres_enabled: false`)" +msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)" msgstr "" #: ../../../CHANGELOG.md:3361 -msgid "" -"roles, being more independent now, are more minimal and do not do so much" -" magic for you. People that are building their own playbook using our " -"roles will definitely need to take a look at the [`group_vars/matrix-" -"servers`](group_vars/matrix-servers) file and adapt their playbooks with " -"the same (or similar) wiring logic." +msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic." msgstr "" #: ../../../CHANGELOG.md:3364 @@ -10102,30 +6160,15 @@ msgid "Splitting the playbook into multiple roles" msgstr "" #: ../../../CHANGELOG.md:3368 -msgid "" -"For better maintainability, the playbook logic (which all used to reside " -"in a single `matrix-server` role) has been split out into a number of " -"different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, " -"`matrix-mxisd`, etc. (see the `roles/` directory)." +msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)." msgstr "" #: ../../../CHANGELOG.md:3371 -msgid "" -"To keep the filesystem more consistent with this separation, the " -"**Postgres data had to be relocated**." +msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**." msgstr "" #: ../../../CHANGELOG.md:3373 -msgid "" -"The default value of `matrix_postgres_data_path` was changed from " -"`/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` " -"directory is what we consider a base path now (new variable " -"`matrix_postgres_base_path`). **Your Postgres data files will " -"automatically be relocated by the playbook** (`/matrix/postgres/*` -> " -"`/matrix/postgres/data/`) when you run with `--tags=setup-all` (or " -"`--tags=setup-postgres`). While this shouldn't cause data-loss, **it's " -"better if you do a Postgres backup just in case**. You'd need to restart " -"all services after this migration (`--tags=start`)." +msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)." msgstr "" #: ../../../CHANGELOG.md:3376 @@ -10137,10 +6180,7 @@ msgid "(BC Break) mxisd configuration changes" msgstr "" #: ../../../CHANGELOG.md:3380 -msgid "" -"To be more flexible and to support the upcoming " -"[mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released)," -" we've had to redo how mxisd gets configured." +msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured." msgstr "" #: ../../../CHANGELOG.md:3383 @@ -10224,11 +6264,7 @@ msgid "`matrix_mxisd_template_config`" msgstr "" #: ../../../CHANGELOG.md:3407 -msgid "" -"You are encouraged to use the `matrix_mxisd_configuration_extension_yaml`" -" variable to define your own mxisd configuration additions and overrides." -" Refer to the [default variables file](roles/custom/matrix-" -"mxisd/defaults/main.yml) for more information." +msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information." msgstr "" #: ../../../CHANGELOG.md:3409 @@ -10236,15 +6272,11 @@ msgid "This new way of configuring mxisd is beneficial because:" msgstr "" #: ../../../CHANGELOG.md:3411 -msgid "" -"it lets us support all mxisd configuration options, as the playbook " -"simply forwards them to mxisd without needing to care or understand them" +msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them" msgstr "" #: ../../../CHANGELOG.md:3412 -msgid "" -"it lets you upgrade to newer mxisd versions and make use of their " -"features, without us having to add support for them explicitly" +msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly" msgstr "" #: ../../../CHANGELOG.md:3415 @@ -10256,25 +6288,15 @@ msgid "(BC Break) Cronjob schedule no longer configurable" msgstr "" #: ../../../CHANGELOG.md:3419 -msgid "" -"Due to the way we manage cronjobs now, you can no longer configure the " -"schedule they're invoked at." +msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at." msgstr "" #: ../../../CHANGELOG.md:3421 -msgid "" -"If you were previously using " -"`matrix_ssl_lets_encrypt_renew_cron_time_definition` or " -"`matrix_nginx_proxy_reload_cron_time_definition` to set a custom " -"schedule, you should note that these variables don't affect anything " -"anymore." +msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore." msgstr "" #: ../../../CHANGELOG.md:3424 -msgid "" -"If you miss this functionality, please [open an " -"Issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/new) and let us know about your use case!" +msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!" msgstr "" #: ../../../CHANGELOG.md:3427 @@ -10286,9 +6308,7 @@ msgid "(BC Break) More SSL certificate retrieval methods" msgstr "" #: ../../../CHANGELOG.md:3431 -msgid "" -"The playbook now lets you decide between 3 different SSL certificate " -"retrieval methods:" +msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:" msgstr "" #: ../../../CHANGELOG.md:3432 @@ -10304,15 +6324,11 @@ msgid "managing SSL certificates manually" msgstr "" #: ../../../CHANGELOG.md:3436 -msgid "" -"Learn more in [Adjusting SSL certificate retrieval](docs/configuring-" -"playbook-ssl-certificates.md)." +msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)." msgstr "" #: ../../../CHANGELOG.md:3438 -msgid "" -"For people who use Let's Encrypt (mostly everyone, since it's the " -"default), you'll also have to rename a variable in your configuration:" +msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:" msgstr "" #: ../../../CHANGELOG.md:3440 @@ -10328,20 +6344,11 @@ msgid "(BC Break) mxisd upgrade with multiple base DN support" msgstr "" #: ../../../CHANGELOG.md:3445 -msgid "" -"mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-" -"matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base " -"DNs](https://github.com/kamax-" -"matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." +msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)." msgstr "" #: ../../../CHANGELOG.md:3447 -msgid "" -"If you were configuring this playbook's " -"`matrix_mxisd_ldap_connection_baseDn` variable until now (a string " -"containing a single base DN), you'll need to change to configuring the " -"`matrix_mxisd_ldap_connection_baseDns` variable (an array containing " -"multiple base DNs)." +msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)." msgstr "" #: ../../../CHANGELOG.md:3449 @@ -10353,9 +6360,7 @@ msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org` msgstr "" #: ../../../CHANGELOG.md:3452 -msgid "" -"after: `matrix_mxisd_ldap_connection_baseDns: " -"['OU=Users,DC=example,DC=org']`" +msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`" msgstr "" #: ../../../CHANGELOG.md:3455 @@ -10367,10 +6372,7 @@ msgid "Synapse 0.34.0 and Python 3" msgstr "" #: ../../../CHANGELOG.md:3459 -msgid "" -"Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on " -"feedback from others, running Synapse on Python 3 is supposed to decrease" -" memory usage significantly (~2x)." +msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)." msgstr "" #: ../../../CHANGELOG.md:3462 @@ -10382,11 +6384,7 @@ msgid "Riot homepage customization" msgstr "" #: ../../../CHANGELOG.md:3466 -msgid "" -"You can now customize some parts of the Riot homepage (or even completely" -" replace it with your own custom page). See the " -"`matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-" -"web/defaults/main.yml`." +msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`." msgstr "" #: ../../../CHANGELOG.md:3469 @@ -10398,11 +6396,7 @@ msgid "mxisd extensibility" msgstr "" #: ../../../CHANGELOG.md:3473 -msgid "" -"The [LDAP identity store for mxisd](https://github.com/kamax-" -"matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured " -"easily using playbook variables (see the `matrix_mxisd_ldap_` variables " -"in `roles/custom/matrix-server/defaults/main.yml`)." +msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)." msgstr "" #: ../../../CHANGELOG.md:3476 @@ -10426,15 +6420,11 @@ msgid "LDAP auth support via matrix-synapse-ldap3" msgstr "" #: ../../../CHANGELOG.md:3485 -msgid "" -"The playbook can now install and configure [LDAP auth " -"support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." +msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." msgstr "" #: ../../../CHANGELOG.md:3487 -msgid "" -"Additional details are available in [Setting up the LDAP authentication " -"password provider module](docs/configuring-playbook-ldap-auth.md)." +msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3490 @@ -10446,16 +6436,11 @@ msgid "Support for controlling public registration and room auto-join" msgstr "" #: ../../../CHANGELOG.md:3494 -msgid "" -"The playbook now lets you enable public registration for users " -"(controlled via `matrix_synapse_enable_registration`). By default, public" -" registration is forbidden." +msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden." msgstr "" #: ../../../CHANGELOG.md:3496 -msgid "" -"You can also make people automatically get auto-joined to rooms " -"(controlled via `matrix_synapse_auto_join_rooms`)." +msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)." msgstr "" #: ../../../CHANGELOG.md:3498 @@ -10463,10 +6448,7 @@ msgid "Support for changing the welcome user ID (welcome bot)" msgstr "" #: ../../../CHANGELOG.md:3500 -msgid "" -"By default, `@riot-bot:matrix.org` is used to welcome newly registered " -"users. This can be changed to something else (or disabled) via the new " -"`matrix_riot_web_welcome_user_id` variable." +msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable." msgstr "" #: ../../../CHANGELOG.md:3503 @@ -10478,16 +6460,11 @@ msgid "Ability to set Synapse log levels" msgstr "" #: ../../../CHANGELOG.md:3507 -msgid "" -"The playbook now allows you to set the log levels used by Synapse. The " -"default logging levels remain the same." +msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same." msgstr "" #: ../../../CHANGELOG.md:3509 -msgid "" -"You can now override following variables with any of the supported log " -"levels listed here: https://docs.python.org/3/library/logging.html" -"#logging-levels" +msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels" msgstr "" #: ../../../CHANGELOG.md:3518 @@ -10499,17 +6476,11 @@ msgid "Customize parts of Riot's config" msgstr "" #: ../../../CHANGELOG.md:3522 -msgid "" -"You can now customize some parts of Riot's `config.json`. These playbook " -"variables, with these default values, have been added:" +msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:" msgstr "" #: ../../../CHANGELOG.md:3533 -msgid "" -"This now allows you use a custom integration manager like " -"[Dimension](https://dimension.t2bot.io). For example, if you wish to use " -"the Dimension instance hosted at dimension.t2bot.io, you can set the " -"following in your vars.yml file:" +msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:" msgstr "" #: ../../../CHANGELOG.md:3542 @@ -10517,23 +6488,15 @@ msgid "SSL protocols used to serve Riot and Synapse" msgstr "" #: ../../../CHANGELOG.md:3544 -msgid "" -"There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, " -"which controls the SSL protocols used to serve Riot and Synapse. Its " -"default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 " -"TLSv1.1 TLSv1.2` to serve Riot and Synapse." +msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse." msgstr "" #: ../../../CHANGELOG.md:3546 -msgid "" -"You may wish to reenable TLSv1 if you need to access Riot in older " -"browsers." +msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers." msgstr "" #: ../../../CHANGELOG.md:3548 -msgid "" -"Note: Currently the dockerized nginx doesn't support TLSv1.3. See " -"https://github.com/nginxinc/docker-nginx/issues/190 for more details." +msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details." msgstr "" #: ../../../CHANGELOG.md:3551 @@ -10545,17 +6508,11 @@ msgid "Postgres 11 support" msgstr "" #: ../../../CHANGELOG.md:3555 -msgid "" -"The playbook now installs [Postgres " -"11](https://www.postgresql.org/about/news/1894/) by default." +msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default." msgstr "" #: ../../../CHANGELOG.md:3557 -msgid "" -"If you have have an existing setup, it's likely running on an older " -"Postgres version (9.x or 10.x). You can easily upgrade by following the " -"[upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-" -"postgresql)." +msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)." msgstr "" #: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646 @@ -10564,10 +6521,7 @@ msgid "(BC Break) Renaming playbook variables" msgstr "" #: ../../../CHANGELOG.md:3561 -msgid "" -"Due to the large amount of features added to this playbook lately, to " -"keep things manageable we've had to reorganize its configuration " -"variables a bit." +msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit." msgstr "" #: ../../../CHANGELOG.md:3565 @@ -10575,15 +6529,11 @@ msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3566 -msgid "" -"from `matrix_docker_image_mautrix_telegram` to " -"`matrix_mautrix_telegram_docker_image`" +msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3567 -msgid "" -"from `matrix_docker_image_mautrix_whatsapp` to " -"`matrix_mautrix_whatsapp_docker_image`" +msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3568 @@ -10611,21 +6561,15 @@ msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" msgstr "" #: ../../../CHANGELOG.md:3574 -msgid "" -"from `matrix_docker_image_postgres_v9` to " -"`matrix_postgres_docker_image_v9`" +msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`" msgstr "" #: ../../../CHANGELOG.md:3575 -msgid "" -"from `matrix_docker_image_postgres_v10` to " -"`matrix_postgres_docker_image_v10`" +msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`" msgstr "" #: ../../../CHANGELOG.md:3576 -msgid "" -"from `matrix_docker_image_postgres_latest` to " -"`matrix_postgres_docker_image_latest`" +msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`" msgstr "" #: ../../../CHANGELOG.md:3579 @@ -10637,18 +6581,11 @@ msgid "Mautrix Whatsapp bridging support" msgstr "" #: ../../../CHANGELOG.md:3583 -msgid "" -"The playbook now supports bridging with " -"[Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-" -"whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This " -"playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3585 -msgid "" -"Additional details are available in [Setting up Mautrix Whatsapp " -"bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." +msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." msgstr "" #: ../../../CHANGELOG.md:3588 @@ -10660,10 +6597,7 @@ msgid "Support for controlling Matrix federation" msgstr "" #: ../../../CHANGELOG.md:3592 -msgid "" -"The playbook can now help you with [Controlling Matrix federation](docs" -"/configuring-playbook-federation), should you wish to run a more private " -"(isolated) server." +msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server." msgstr "" #: ../../../CHANGELOG.md:3595 @@ -10675,10 +6609,7 @@ msgid "Disabling riot-web guests" msgstr "" #: ../../../CHANGELOG.md:3599 -msgid "" -"From now on, Riot's configuration setting `disable_guests` would be set " -"to `true`. The homeserver was rejecting guests anyway, so this is just a " -"cosmetic change affecting Riot's UI." +msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI." msgstr "" #: ../../../CHANGELOG.md:3602 @@ -10690,9 +6621,7 @@ msgid "Self-check maintenance command" msgstr "" #: ../../../CHANGELOG.md:3606 -msgid "" -"The playbook can now [check if services are configured correctly](docs" -"/maintenance-checking-services.md)." +msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)." msgstr "" #: ../../../CHANGELOG.md:3609 @@ -10704,16 +6633,11 @@ msgid "Presence tracking made configurable" msgstr "" #: ../../../CHANGELOG.md:3613 -msgid "" -"The playbook can now enable/disable user presence-status tracking in " -"Synapse, through the playbook's `matrix_synapse_use_presence` variable " -"(having a default value of `true` - enabled)." +msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)." msgstr "" #: ../../../CHANGELOG.md:3615 -msgid "" -"If users participate in large rooms with many other servers, disabling " -"presence will decrease server load significantly." +msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly." msgstr "" #: ../../../CHANGELOG.md:3618 @@ -10725,18 +6649,11 @@ msgid "Synapse Cache Factor made configurable" msgstr "" #: ../../../CHANGELOG.md:3622 -msgid "" -"The playbook now makes the Synapse cache factor configurable, through the" -" playbook's `matrix_synapse_cache_factor` variable (having a default " -"value of `0.5`)." +msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)." msgstr "" #: ../../../CHANGELOG.md:3624 -msgid "" -"Changing that value allows you to potentially decrease RAM usage or to " -"increase performance by caching more stuff. Some information on it is " -"available here: https://github.com/element-hq/synapse#help-synapse-eats-" -"all-my-ram" +msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram" msgstr "" #: ../../../CHANGELOG.md:3627 @@ -10752,18 +6669,11 @@ msgid "`--log-driver=none` is used for all Docker containers now." msgstr "" #: ../../../CHANGELOG.md:3633 -msgid "" -"All these containers are started through systemd anyway and get logged in" -" journald, so there's no need for Docker to be logging the same thing " -"using the default `json-file` driver. Doing that was growing " -"`/var/lib/docker/containers/..` infinitely until service/container " -"restart." +msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart." msgstr "" #: ../../../CHANGELOG.md:3635 -msgid "" -"As a result of this, things like `docker logs matrix-synapse` won't work " -"anymore. `journalctl -u matrix-synapse` is how one can see the logs." +msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs." msgstr "" #: ../../../CHANGELOG.md:3638 @@ -10775,16 +6685,11 @@ msgid "Service discovery support" msgstr "" #: ../../../CHANGELOG.md:3642 -msgid "" -"The playbook now helps you set up [service " -"discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-" -"discovery) using a `/.well-known/matrix/client` file." +msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file." msgstr "" #: ../../../CHANGELOG.md:3644 -msgid "" -"Additional details are available in [Configuring service discovery via " -".well-known](docs/configuring-well-known.md)." +msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)." msgstr "" #: ../../../CHANGELOG.md:3650 @@ -10792,9 +6697,7 @@ msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" msgstr "" #: ../../../CHANGELOG.md:3651 -msgid "" -"from `matrix_riot_web_default_identity_server_url` to " -"`matrix_identity_server_url`" +msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`" msgstr "" #: ../../../CHANGELOG.md:3654 @@ -10806,17 +6709,11 @@ msgid "Mautrix Telegram bridging support" msgstr "" #: ../../../CHANGELOG.md:3658 -msgid "" -"The playbook now supports bridging with [Telegram](https://telegram.org/)" -" by installing the [mautrix-telegram](https://github.com/tulir/mautrix-" -"telegram) bridge. This playbook functionality is available thanks to " -"[@izissise](https://github.com/izissise)." +msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)." msgstr "" #: ../../../CHANGELOG.md:3660 -msgid "" -"Additional details are available in [Setting up Mautrix Telegram " -"bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." +msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." msgstr "" #: ../../../CHANGELOG.md:3662 @@ -10824,16 +6721,11 @@ msgid "Events cache size increase and configurability for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3664 -msgid "" -"The playbook now lets you configure Matrix Synapse's `event_cache_size` " -"configuration via the `matrix_synapse_event_cache_size` playbook " -"variable." +msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable." msgstr "" #: ../../../CHANGELOG.md:3666 -msgid "" -"Previously, this value was hardcoded to `\"10K\"`. From now on, a more " -"reasonable default of `\"100K\"` is used." +msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used." msgstr "" #: ../../../CHANGELOG.md:3668 @@ -10841,13 +6733,7 @@ msgid "Password-peppering support for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3670 -msgid "" -"The playbook now supports enabling password-peppering for increased " -"security in Matrix Synapse via the " -"`matrix_synapse_password_config_pepper` playbook variable. Using a " -"password pepper is disabled by default (just like it used to be before " -"this playbook variable got introduced) and is not to be enabled/disabled " -"after initial setup, as that would invalidate all existing passwords." +msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords." msgstr "" #: ../../../CHANGELOG.md:3672 @@ -10855,17 +6741,11 @@ msgid "Statistics-reporting support for Matrix Synapse" msgstr "" #: ../../../CHANGELOG.md:3674 -msgid "" -"There's now a new `matrix_synapse_report_stats` playbook variable, which " -"controls the `report_stats` configuration option for Matrix Synapse. It " -"defaults to `false`, so no change is required to retain your privacy." +msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy." msgstr "" #: ../../../CHANGELOG.md:3676 -msgid "" -"If you'd like to start reporting statistics about your homeserver (things" -" like number of users, number of messages sent, uptime, load, etc.) to " -"matrix.org, you can turn on stats reporting." +msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting." msgstr "" #: ../../../CHANGELOG.md:3679 @@ -10877,26 +6757,15 @@ msgid "Changing the way SSL certificates are retrieved" msgstr "" #: ../../../CHANGELOG.md:3683 -msgid "" -"We've been using [acmetool](https://github.com/hlandau/acme) (with the " -"[willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) " -"Docker image) until now." +msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now." msgstr "" #: ../../../CHANGELOG.md:3685 -msgid "" -"Due to the Docker image being deprecated, and things looking bleak for " -"acmetool's support of the newer ACME v2 API endpoint, we've switched to " -"using [certbot](https://certbot.eff.org/) (with the " -"[certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker " -"image)." +msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)." msgstr "" #: ../../../CHANGELOG.md:3687 -msgid "" -"Simply re-running the playbook will retrieve new certificates (via " -"certbot) for you. To ensure you don't leave any old files behind, though," -" you'd better do this:" +msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:" msgstr "" #: ../../../CHANGELOG.md:3689 @@ -10904,9 +6773,7 @@ msgid "`systemctl stop 'matrix*'`" msgstr "" #: ../../../CHANGELOG.md:3690 -msgid "" -"stop your custom webserver, if you're running one (only affects you if " -"you've installed with `matrix_nginx_proxy_enabled: false`)" +msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)" msgstr "" #: ../../../CHANGELOG.md:3691 @@ -10930,15 +6797,11 @@ msgid "Matrix Corporal support" msgstr "" #: ../../../CHANGELOG.md:3700 -msgid "" -"The playbook can now install and configure [matrix-" -"corporal](https://github.com/devture/matrix-corporal) for you." +msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" #: ../../../CHANGELOG.md:3702 -msgid "" -"Additional details are available in [Setting up Matrix Corporal](docs" -"/configuring-playbook-matrix-corporal.md)." +msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../CHANGELOG.md:3705 @@ -10950,9 +6813,7 @@ msgid "Matrix Synapse rate limit control variables" msgstr "" #: ../../../CHANGELOG.md:3709 -msgid "" -"The following new variables can now be configured to control Matrix " -"Synapse's rate-limiting (default values are shown below)." +msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)." msgstr "" #: ../../../CHANGELOG.md:3716 @@ -10960,17 +6821,11 @@ msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" msgstr "" #: ../../../CHANGELOG.md:3718 -msgid "" -"The playbook can now install and configure [matrix-synapse-shared-secret-" -"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " -"you." +msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" #: ../../../CHANGELOG.md:3720 -msgid "" -"Additional details are available in [Setting up the Shared Secret Auth " -"password provider module](docs/configuring-playbook-shared-secret-" -"auth.md)." +msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3723 @@ -10982,15 +6837,11 @@ msgid "REST auth support via matrix-synapse-rest-auth" msgstr "" #: ../../../CHANGELOG.md:3727 -msgid "" -"The playbook can now install and configure [matrix-synapse-rest-" -"auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." +msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you." msgstr "" #: ../../../CHANGELOG.md:3729 -msgid "" -"Additional details are available in [Setting up the REST authentication " -"password provider module](docs/configuring-playbook-rest-auth.md)." +msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)." msgstr "" #: ../../../CHANGELOG.md:3731 @@ -10998,15 +6849,11 @@ msgid "Compression improvements" msgstr "" #: ../../../CHANGELOG.md:3733 -msgid "" -"Shifted Matrix Synapse compression from happening in the Matrix Synapse, " -"to happening in the nginx proxy that's in front of it." +msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it." msgstr "" #: ../../../CHANGELOG.md:3736 -msgid "" -"Additionally, `riot-web` also gets compressed now (in the nginx proxy), " -"which drops the initial page load's size from 5.31MB to 1.86MB." +msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB." msgstr "" #: ../../../CHANGELOG.md:3739 @@ -11022,15 +6869,11 @@ msgid "on the federation port (8448): the `client` service" msgstr "" #: ../../../CHANGELOG.md:3743 -msgid "" -"on the http port (8008, exposed over 443): the old Angular `webclient` " -"and the `federation` service" +msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service" msgstr "" #: ../../../CHANGELOG.md:3745 -msgid "" -"Federation runs only on the federation port (8448) now. The Client APIs " -"run only on the http port (8008) now." +msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now." msgstr "" #: ../../../CHANGELOG.md:3748 @@ -11042,10 +6885,7 @@ msgid "mxisd Identity Server support" msgstr "" #: ../../../CHANGELOG.md:3752 -msgid "" -"The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) " -"Identity Server for you by default. Additional details are available in " -"[Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." +msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)." msgstr "" #: ../../../CHANGELOG.md:3755 @@ -11057,16 +6897,11 @@ msgid "Email-sending support" msgstr "" #: ../../../CHANGELOG.md:3759 -msgid "" -"The playbook now configures an email-sending service (postfix) by " -"default. Additional details are available in [Adjusting email-sending " -"settings](docs/configuring-playbook-email.md)." +msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)." msgstr "" #: ../../../CHANGELOG.md:3761 -msgid "" -"With this, Matrix Synapse is able to send email notifications for missed " -"messages, etc." +msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc." msgstr "" #: ../../../CHANGELOG.md:3764 @@ -11078,9 +6913,7 @@ msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" msgstr "" #: ../../../CHANGELOG.md:3771 -msgid "" -"from `matrix_max_log_file_size_mb` to " -"`matrix_synapse_max_log_file_size_mb`" +msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`" msgstr "" #: ../../../CHANGELOG.md:3772 @@ -11108,9 +6941,7 @@ msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" msgstr "" #: ../../../CHANGELOG.md:3779 -msgid "" -"If you're overriding any of them in your `vars.yml` file, you'd need to " -"change to the new names." +msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names." msgstr "" #: ../../../CHANGELOG.md:3781 @@ -11118,9 +6949,7 @@ msgid "Renaming Ansible playbook tag" msgstr "" #: ../../../CHANGELOG.md:3783 -msgid "" -"The command for executing the whole playbook has changed. The `setup-" -"main` tag got renamed to `setup-all`." +msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`." msgstr "" #: ../../../CHANGELOG.md:3785 @@ -11128,9 +6957,5 @@ msgid "Docker container linking" msgstr "" #: ../../../CHANGELOG.md:3787 -msgid "" -"Changed the way the Docker containers are linked together. The ones that " -"need to communicate with others operate in a `matrix` network now and not" -" in the default bridge network." +msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/README.po b/i18n/locales/jp/LC_MESSAGES/README.po index 41e9558db..7d8aa909d 100644 --- a/i18n/locales/jp/LC_MESSAGES/README.po +++ b/i18n/locales/jp/LC_MESSAGES/README.po @@ -21,13 +21,7 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../README.md:1 -msgid "" -"[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-" -"ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-" -"deploy%3Adevture.com&logo=matrix&style=for-the-" -"badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-" -"docker-ansible-deploy:devture.com) " -"[![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" +msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)" msgstr "" #: ../../../README.md:1 @@ -39,9 +33,7 @@ msgid "donate" msgstr "" #: ../../../README.md:3 -msgid "" -"Matrix (An open network for secure, decentralized communication) server " -"setup using Ansible and Docker" +msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker" msgstr "" #: ../../../README.md:5 @@ -49,37 +41,19 @@ msgid "🎯 Purpose" msgstr "" #: ../../../README.md:7 -msgid "" -"This [Ansible](https://www.ansible.com/) playbook is meant to help you " -"run your own [Matrix](http://matrix.org/) homeserver, along with the " -"[various services](#supported-services) related to that." -msgstr "" -"この [Ansible](https://www.ansible.com/) Playbook は、独自の " -"[Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-" -"services) を実行するのに役立つことを目的としています。" +msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that." +msgstr "この [Ansible](https://www.ansible.com/) Playbook は、独自の [Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-services) を実行するのに役立つことを目的としています。" #: ../../../README.md:9 -msgid "" -"That is, it lets you join the Matrix network using your own user ID like " -"`@alice:example.com`, all hosted on your own server (see " -"[prerequisites](docs/prerequisites.md))." +msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))." msgstr "" #: ../../../README.md:11 -msgid "" -"We run all [supported services](#-supported-services) in " -"[Docker](https://www.docker.com/) containers (see [the container images " -"we use](docs/container-images.md)), which lets us have a predictable and " -"up-to-date setup, across multiple supported distros (see " -"[prerequisites](docs/prerequisites.md)) and [architectures](docs" -"/alternative-architectures.md) (x86/amd64 being recommended)." +msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)." msgstr "" #: ../../../README.md:13 -msgid "" -"Installation (upgrades) and some maintenance tasks are automated using " -"[Ansible](https://www.ansible.com/) (see [our Ansible " -"guide](docs/ansible.md))." +msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))." msgstr "" #: ../../../README.md:15 @@ -87,27 +61,11 @@ msgid "☁ Self-hosting or Managed / SaaS" msgstr "" #: ../../../README.md:17 -msgid "" -"This Ansible playbook tries to make self-hosting and maintaining a Matrix" -" server fairly easy (see [Getting started](#-getting-started)). Still, " -"running any service smoothly requires knowledge, time and effort." +msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort." msgstr "" #: ../../../README.md:19 -msgid "" -"If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" -"source_software) spirit of this Ansible playbook, but prefer to put the " -"responsibility on someone else, you can also [get a managed Matrix server" -" from " -"etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" (both hosting and on-premises) - a service built on top of this Ansible " -"playbook but with [additional " -"components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" and " -"[services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad)" -" which all help you run a Matrix server with ease. Be advised that " -"etke.cc operates on a subscription-based approach and there is no \"just " -"set up my server once and be done with it\" option." +msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option." msgstr "" #: ../../../README.md:21 @@ -115,51 +73,31 @@ msgid "🚀 Getting started" msgstr "" #: ../../../README.md:23 -msgid "" -"We have detailed documentation in the [docs/](./docs) directory - see the" -" Table of Contents in the [documentation README](./docs/README.md)." +msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)." msgstr "" #: ../../../README.md:25 -msgid "" -"While the [list of supported services](#-supported-services) and " -"documentation is very extensive, you don't need to read through " -"everything. We recommend:" +msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:" msgstr "" #: ../../../README.md:27 -msgid "" -"Starting with the basics. You can always add/remove or tweak services " -"later on." +msgid "Starting with the basics. You can always add/remove or tweak services later on." msgstr "" #: ../../../README.md:29 -msgid "" -"Following our installation guide. There are two guides available for " -"beginners and advanced users:" +msgid "Following our installation guide. There are two guides available for beginners and advanced users:" msgstr "" #: ../../../README.md:31 -msgid "" -"⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is " -"recommended for those who do not have an existing Matrix server and want " -"to start quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](./docs/quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../README.md:33 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide by starting with the " -"**[Prerequisites](./docs/prerequisites.md)** documentation page." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](./docs/prerequisites.md)** documentation page." msgstr "" #: ../../../README.md:35 -msgid "" -"If you experience an issue on configuring the playbook, setting up your " -"server, maintaining services on it, etc., please take a look at our " -"[FAQ](./docs/faq.md). If you cannot find an answer to your question, feel" -" free to ask for [help and support](#-support)." +msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)." msgstr "" #: ../../../README.md:37 @@ -167,11 +105,7 @@ msgid "✔ Supported services" msgstr "" #: ../../../README.md:39 -msgid "" -"Using this playbook, you can get the following list of services " -"configured on your server. Basically, this playbook aims to get you up-" -"and-running with all the necessities around Matrix, without you having to" -" do anything else." +msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else." msgstr "" #: ../../../README.md:41 @@ -179,19 +113,11 @@ msgid "**Notes**:" msgstr "" #: ../../../README.md:43 -msgid "" -"The list below is exhaustive. It includes optional or even some advanced " -"components that you will most likely not need. Sticking with the defaults" -" (which install a subset of the above components) is the best choice, " -"especially for a new installation. You can always re-run the playbook " -"later to add or remove components." +msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components." msgstr "" #: ../../../README.md:45 -msgid "" -"Deprecated or unmaintained services are not listed. You can find " -"documentations for them [here](docs/configuring-playbook.md#deprecated--" -"unmaintained--removed-services)." +msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)." msgstr "" #: ../../../README.md:47 @@ -199,9 +125,7 @@ msgid "Homeserver" msgstr "" #: ../../../README.md:49 -msgid "" -"The homeserver is the backbone of your Matrix system. Choose one from the" -" following list." +msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list." msgstr "" #: ../../../README.md @@ -229,9 +153,7 @@ msgid "✅" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" msgstr "" #: ../../../README.md @@ -247,11 +169,7 @@ msgid "❌" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" -"source server implementation of the Matrix Specification with a focus on " -"easy setup and low system requirements" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" msgstr "" #: ../../../README.md @@ -263,10 +181,7 @@ msgid "[Dendrite](https://github.com/matrix-org/dendrite)" msgstr "" #: ../../../README.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " -"Matrix homeserver written in Go, an alternative to Synapse." +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." msgstr "" #: ../../../README.md @@ -286,9 +201,7 @@ msgid "[Element Web](https://github.com/element-hq/element-web)" msgstr "" #: ../../../README.md -msgid "" -"Default Matrix web client, configured to connect to your own Synapse " -"server" +msgid "Default Matrix web client, configured to connect to your own Synapse server" msgstr "" #: ../../../README.md @@ -336,9 +249,7 @@ msgid "Server Components" msgstr "" #: ../../../README.md:70 -msgid "" -"Services that run on the server to make the various parts of your " -"installation work." +msgid "Services that run on the server to make the various parts of your installation work." msgstr "" #: ../../../README.md @@ -346,9 +257,7 @@ msgid "[PostgreSQL](https://www.postgresql.org/)" msgstr "" #: ../../../README.md -msgid "" -"Database for Synapse. [Using an external PostgreSQL server](docs" -"/configuring-playbook-external-postgres.md) is also possible." +msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible." msgstr "" #: ../../../README.md @@ -372,10 +281,7 @@ msgid "[Traefik](https://doc.traefik.io/traefik/)" msgstr "" #: ../../../README.md -msgid "" -"Web server, listening on ports 80, 443 and 8448 - standing in front of " -"all the other services. Using your own webserver [is possible](docs" -"/configuring-playbook-own-webserver.md)" +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)" msgstr "" #: ../../../README.md @@ -399,9 +305,7 @@ msgid "[Exim](https://www.exim.org/)" msgstr "" #: ../../../README.md -msgid "" -"Mail server, through which all Matrix services send outgoing email (can " -"be configured to relay through another SMTP server)" +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" msgstr "" #: ../../../README.md @@ -441,9 +345,7 @@ msgid "Extend and modify how users are authenticated on your homeserver." msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-" -"password-provider) (advanced)" +msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)" msgstr "" #: ../../../README.md @@ -455,9 +357,7 @@ msgid "[Link](docs/configuring-playbook-rest-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-" -"synapse-shared-secret-auth) (advanced)" +msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)" msgstr "" #: ../../../README.md @@ -469,9 +369,7 @@ msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-" -"ldap3) (advanced)" +msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)" msgstr "" #: ../../../README.md @@ -483,16 +381,11 @@ msgid "[Link](docs/configuring-playbook-ldap-auth.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" (advanced)" +msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)" msgstr "" #: ../../../README.md -msgid "" -"A proxy that handles Matrix registration requests and forwards them to " -"LDAP." +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../README.md @@ -512,9 +405,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../README.md -msgid "" -"[Matrix User Verification Service](https://github.com/matrix-org/matrix-" -"user-verification-service) (UVS)" +msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)" msgstr "" #: ../../../README.md @@ -526,9 +417,7 @@ msgid "[Link](docs/configuring-playbook-user-verification-service.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-" -"antispam) (advanced)" +msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)" msgstr "" #: ../../../README.md @@ -552,9 +441,7 @@ msgid "[Goofys](https://github.com/kahing/goofys)" msgstr "" #: ../../../README.md -msgid "" -"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " -"store) storage for Synapse's content repository (`media_store`) files" +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" msgstr "" #: ../../../README.md @@ -562,9 +449,7 @@ msgid "[Link](docs/configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" -"-storage-provider)" +msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)" msgstr "" #: ../../../README.md @@ -576,10 +461,7 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)" msgstr "" #: ../../../README.md -msgid "" -"matrix-media-repo is a highly customizable multi-domain media repository " -"for Matrix. Intended for medium to large deployments, this media repo de-" -"duplicates media while being fully compliant with the specification." +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." msgstr "" #: ../../../README.md @@ -591,9 +473,7 @@ msgid "Bridges" msgstr "" #: ../../../README.md:108 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../README.md @@ -697,16 +577,11 @@ msgid "[mautrix-meta](https://github.com/mautrix/instagram)" msgstr "" #: ../../../README.md -msgid "" -"Bridge to [Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/)" +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" msgstr "" #: ../../../README.md -msgid "" -"Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-" -"messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-" -"meta-instagram.md)" +msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../README.md @@ -734,9 +609,7 @@ msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-" -"irc)" +msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)" msgstr "" #: ../../../README.md @@ -748,15 +621,11 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk)" +msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)" msgstr "" #: ../../../README.md -msgid "" -"Bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" msgstr "" #: ../../../README.md @@ -764,9 +633,7 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-discord](https://github.com/matrix-org/matrix-" -"appservice-discord)" +msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)" msgstr "" #: ../../../README.md @@ -778,9 +645,7 @@ msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-appservice-slack](https://github.com/matrix-org/matrix-" -"appservice-slack)" +msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)" msgstr "" #: ../../../README.md @@ -792,9 +657,7 @@ msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)" msgstr "" #: ../../../README.md -msgid "" -"Bridge for generic webhooks and multiple project management services, " -"such as GitHub, GitLab, Figma, and Jira in particular" +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" msgstr "" #: ../../../README.md @@ -830,9 +693,7 @@ msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)" msgstr "" #: ../../../README.md -msgid "" -"Bouncer-style bridge to " -"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../README.md @@ -888,9 +749,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../README.md -msgid "" -"[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-" -"discord)" +msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)" msgstr "" #: ../../../README.md @@ -898,9 +757,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../README.md -msgid "" -"[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-" -"groupme)" +msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)" msgstr "" #: ../../../README.md @@ -960,11 +817,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)" msgstr "" #: ../../../README.md -msgid "" -"A bot that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you" +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" msgstr "" #: ../../../README.md @@ -972,9 +825,7 @@ msgid "[Link](docs/configuring-playbook-bot-baibot.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-" -"bot)" +msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)" msgstr "" #: ../../../README.md @@ -986,9 +837,7 @@ msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)" msgstr "" #: ../../../README.md -msgid "" -"[matrix-registration-bot](https://github.com/moan0s/matrix-registration-" -"bot)" +msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)" msgstr "" #: ../../../README.md @@ -1044,9 +893,7 @@ msgid "A moderation tool for Matrix (Fork of Mjolnir)" msgstr "" #: ../../../README.md -msgid "" -"[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice " -"mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" +msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" msgstr "" #: ../../../README.md @@ -1066,22 +913,15 @@ msgid "Administration" msgstr "" #: ../../../README.md:158 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../README.md -msgid "" -"[matrix-alertmanager-receiver](https://github.com/metio/matrix-" -"alertmanager-receiver)" +msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)" msgstr "" #: ../../../README.md -msgid "" -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"client" +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" msgstr "" #: ../../../README.md @@ -1089,9 +929,7 @@ msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../README.md -msgid "" -"[Matrix Authentication Service](https://github.com/element-hq/matrix-" -"authentication-service/)" +msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)" msgstr "" #: ../../../README.md @@ -1119,19 +957,11 @@ msgid "Metrics and Graphs" msgstr "" #: ../../../README.md -msgid "" -"Consists of the [Prometheus](https://prometheus.io) time-series database " -"server, the Prometheus [node-exporter](https://prometheus.io/docs/guides" -"/node-exporter/) host metrics exporter, and the " -"[Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-" -"exporter](https://github.com/martin-helmich/prometheus-nginxlog-" -"exporter/) being available too" +msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too" msgstr "" #: ../../../README.md -msgid "" -"[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-" -"nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" +msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))" msgstr "" #: ../../../README.md @@ -1159,15 +989,11 @@ msgid "[Link](docs/configuring-playbook-rageshake.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" -"exporter)" +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)" msgstr "" #: ../../../README.md -msgid "" -"Export the usage statistics of a Synapse homeserver to be scraped by " -"Prometheus." +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." msgstr "" #: ../../../README.md @@ -1187,11 +1013,7 @@ msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)" msgstr "" #: ../../../README.md -msgid "" -"(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` " -"and Conduit > `0.6.0`) Sliding Sync support for clients which require it " -"(e.g. old Element X versions before Simplified Sliding Sync was " -"developed)" +msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)" msgstr "" #: ../../../README.md @@ -1199,9 +1021,7 @@ msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-" -"accept-invite)" +msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)" msgstr "" #: ../../../README.md @@ -1213,15 +1033,11 @@ msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../README.md -msgid "" -"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" -"compress-state/#automated-tool-synapse_auto_compressor)" +msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)" msgstr "" #: ../../../README.md -msgid "" -"A cli tool that automatically compresses `state_groups` database table in" -" background." +msgid "A cli tool that automatically compresses `state_groups` database table in background." msgstr "" #: ../../../README.md @@ -1317,15 +1133,11 @@ msgid "🆕 Changes" msgstr "" #: ../../../README.md:189 -msgid "" -"This playbook evolves over time, sometimes with backward-incompatible " -"changes." +msgid "This playbook evolves over time, sometimes with backward-incompatible changes." msgstr "" #: ../../../README.md:191 -msgid "" -"When updating the playbook, refer to [the changelog](CHANGELOG.md) to " -"catch up with what's new." +msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new." msgstr "" #: ../../../README.md:193 @@ -1333,23 +1145,15 @@ msgid "🆘 Support" msgstr "" #: ../../../README.md:195 -msgid "" -"Matrix room: [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com)" +msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)" msgstr "" #: ../../../README.md:197 -msgid "" -"IRC channel: `#matrix-docker-ansible-deploy` on the [Libera " -"Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" +msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" msgstr "" #: ../../../README.md:199 -msgid "" -"GitHub issues: [spantaleev/matrix-docker-ansible-" -"deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues)" +msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)" msgstr "" #: ../../../README.md:201 @@ -1357,9 +1161,7 @@ msgid "🌐 Translation" msgstr "" #: ../../../README.md:203 -msgid "" -"See the [i18n/README.md](i18n/README.md) file for more information about " -"translation." +msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation." msgstr "" #: ../../../README.md:205 @@ -1371,21 +1173,9 @@ msgid "🤝 Related" msgstr "" #: ../../../README.md:209 -msgid "" -"You may also be interested in [mash-playbook](https://github.com/mother-" -"of-all-self-hosting/mash-playbook) - another Ansible playbook for self-" -"hosting non-Matrix services (see its [List of supported " -"services](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/supported-services.md))." +msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))." msgstr "" #: ../../../README.md:211 -msgid "" -"mash-playbook also makes use of [Traefik](./docs/configuring-playbook-" -"traefik.md) as its reverse-proxy, so with minor [interoperability " -"adjustments](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/interoperability.md), you can make matrix-docker-" -"ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix " -"services on the same server." +msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po index c0d6a2a9f..4b5536dfb 100644 --- a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po +++ b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po @@ -25,157 +25,47 @@ msgid "2023" msgstr "" #: ../../../YEAR-IN-REVIEW.md:3 -msgid "" -"2023 was a year filled with many changes for matrix-docker-ansible-" -"deploy. In this post, we're looking backward at some of the major changes" -" that happened this year, as well as taking a glimpse of what's ahead in " -"2024." +msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024." msgstr "" #: ../../../YEAR-IN-REVIEW.md:5 -msgid "" -"2023 is probably [the year of AI](https://journal.everypixel.com/2023" -"-the-year-of-ai), with millions of people jumping aboard " -"[OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) " -"train. matrix-docker-ansible-deploy is no stranger to this and 2023 began" -" with a PR from [bertybuttface](https://github.com/bertybuttface) who " -"added support for [matrix-chatgpt-bot](https://github.com/matrixgpt" -"/matrix-chatgpt-bot) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#chatgpt-support)). While OpenAI's chat GPT website was frequently " -"overloaded in the past, their API was up which made using this bot both " -"convenient and more reliable." +msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable." msgstr "" #: ../../../YEAR-IN-REVIEW.md:7 -msgid "" -"AI aside, with the playbook's focus being containers, we're **doubling " -"down on being \"container native\"** and becoming more interoperable for " -"people hosting other containers on the Matrix server. In " -"[2022](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-" -"REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their " -"use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of " -"matrix-docker-ansible-deploy also switching to this reverse-proxy. This " -"prediction materialized quickly. The **largest change** in the playbook " -"in 2023 happened way back in February - matrix-docker-ansible-deploy " -"[starting the switch from nginx to Traefik](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#backward-compatibility-reverse-proxy-configuration-changes-and-initial-" -"traefik-support) and then quickly [making Treafik the default reverse-" -"proxy](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#traefik-is-the-default-reverse-proxy-now). As noted in the changelog " -"entries, we envisioned a quick and complete elimination of `matrix-nginx-" -"proxy`, but at the end of 2023, it hasn't happened yet. The playbook is " -"already using Traefik as the front-most reverse-proxy, but nginx (via " -"`matrix-nginx-proxy`) is still around - it has taken a step back and is " -"only used internally for new setups. Work got to a stall due to:" +msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:9 -msgid "" -"complexity: untangling the overly large and messy `matrix-nginx-proxy` " -"component is difficult" +msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult" msgstr "" #: ../../../YEAR-IN-REVIEW.md:10 -msgid "" -"the current setup became \"good enough\" because nginx has become an " -"internal implementation detail for those who have migrated to Traefik. " -"Traefik is already the default public reverse-proxy and gives better " -"possibilities to people wishing to run other web-exposed containers on " -"their Matrix server via [Docker " -"Compose](https://docs.docker.com/compose/), other Ansible playbooks like " -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) (more about this one, below) or any other way." +msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way." msgstr "" #: ../../../YEAR-IN-REVIEW.md:12 -msgid "" -"`matrix-nginx-proxy` is no longer in the way of us being interoperable, " -"but its ugly internal details are still there. It is one more proxy in " -"the long chain of reverse-proxies we have and we'd like to cut it out. " -"This would both make things simpler and also boost performance." +msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance." msgstr "" #: ../../../YEAR-IN-REVIEW.md:14 -msgid "" -"The delay in eliminating `matrix-nginx-proxy` has probably been welcome " -"by many existing users who decided to postpone the Traefik migration a " -"bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will " -"continue with rapid pace. People who are still using `matrix-nginx-proxy`" -" as their front-most reverse-proxy will need to rework their setup. About" -" a year of putting it off has been long enough." +msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough." msgstr "" #: ../../../YEAR-IN-REVIEW.md:16 -msgid "" -"This large Traefik reverse-proxy change was also accompanied by another " -"internal change which began in 2022, but continued in 2023 - **moving " -"non-Matrix-related roles from being internal to the playbook to living " -"their own life outside of it**. Various roles were made more decoupled " -"and moved outside of the playbook, so that other projects (like the " -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) Ansible playbook or other Ansible playbooks) could benefit from" -" them. This led to the **death of a few sibling playbooks** ([gitea-" -"docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy), [nextcloud-docker-ansible-" -"deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), " -"[peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-" -"docker-ansible-deploy), [vaultwarden-docker-ansible-" -"deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-" -"deploy)), but brought life to something better, which supports all these " -"services and more." +msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more." msgstr "" #: ../../../YEAR-IN-REVIEW.md:18 -msgid "" -"[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-" -"playbook) is a new Ansible playbook that a few of us (matrix-docker-" -"ansible-deploy contributors) have launched in 2023. It has quickly grown " -"to supports [60+ services](https://github.com/mother-of-all-self-hosting" -"/mash-playbook/blob/main/docs/supported-services.md) and aims to do the " -"same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-" -"source_software) service hosting, as matrix-docker-ansible-deploy has " -"done for Matrix - providing a clean and secure way to run a bunch of " -"services in containers on a regular server (that is to say, without " -"Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to" -" host both mash-playbook services and matrix-docker-ansible-deploy " -"services on the same server - see mash-playbook's " -"[interoperability](https://github.com/mother-of-all-self-hosting/mash-" -"playbook/blob/main/docs/interoperability.md) documentation page. If " -"you've been looking for a holiday project or your New Year's Resolutions " -"list contains \"self-hosting more services\", then you're welcome to give" -" this new playbook a try and join its Matrix room ([#mash-" -"playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." +msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))." msgstr "" #: ../../../YEAR-IN-REVIEW.md:20 -msgid "" -"Because many of the roles are now external to this playbook (defined in " -"the [requirements.yml](https://github.com/spantaleev/matrix-docker-" -"ansible-" -"deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) " -"file), running `make roles` (or better yet `just roles` via the [just " -"tool](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#support-for-running-commands-via-just)) becomes a necessity each time " -"one pulls playbook updates (`git pull`). Pulling external roles happens " -"via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli" -"/ansible-galaxy.html) command-line tool, but if available, the playbook " -"would also use the much faster [agru](https://github.com/etkecc/agru) " -"tool (developed by [Aine](https://gitlab.com/etke.cc) from " -"[etke.cc](https://etke.cc/) this year)." +msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)." msgstr "" #: ../../../YEAR-IN-REVIEW.md:22 -msgid "" -"With the internal (but important) details out of the way, we can now talk" -" more about **new features that landed in matrix-docker-ansible-deploy in" -" 2023**." +msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**." msgstr "" #: ../../../YEAR-IN-REVIEW.md:24 @@ -183,40 +73,19 @@ msgid "The following **new** **bridges** were added to the playbook in 2023:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:26 -msgid "" -"(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a " -"PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#mautrix-slack-support))" +msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:27 -msgid "" -"(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), " -"thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#mautrix-gmessages-support))" +msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:28 -msgid "" -"(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for " -"Apple iMessage bridging (when combined with the [mautrix-" -"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" -" or Android phone), thanks to a PR by [Johan " -"Swetzén](https://github.com/jswetzen)" +msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:30 -msgid "" -"This brings the total number of **[bridges that the playbook " -"supports](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-" -"playbook.md#bridging-other-networks) up to 30**. There are alternative " -"bridge implementations for various networks and protocols, so the number " -"of \"unique bridged networks\" is surely much smaller." +msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller." msgstr "" #: ../../../YEAR-IN-REVIEW.md:32 @@ -224,204 +93,79 @@ msgid "A few other **major components and changes** landed in 2023:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:34 -msgid "" -"(2023-02-10) The [Draupnir](https://github.com/the-draupnir-" -"project/Draupnir) moderation tool (successor to " -"[Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by " -"[FSG-Cat](https://github.com/FSG-Cat) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#draupnir-moderation-tool-bot-support))" +msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:35 -msgid "" -"(2023-02-10) [Matrix User Verification Service](https://github.com" -"/matrix-org/matrix-user-verification-service) to add Matrix " -"Authentication Support to our Jitsi setup, thanks to a PR by [Jakob " -"S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com" -"/zakk-it) (see the [changelog entry](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" -"authentication-support-for-jitsi))" +msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:36 -msgid "" -"(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug" -" report server, thanks to a PR by [Benjamin " -"Kampmann](https://github.com/gnunicorn) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#rageshake-support))" +msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:37 -msgid "" -"(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-" -"sync) (currently a necessary component for [Element " -"X](https://element.io/labs/element-x) to work), thanks to: [Benjamin " -"Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com" -"/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#sliding-sync-proxy-element-x-support))" +msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:38 -msgid "" -"(2023-03-12) synapse-auto-compressor to periodically and automatically " -"run [rust-synapse-compress-state](https://github.com/matrix-org/rust-" -"synapse-compress-state), thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#synapse-auto-compressor-support))" +msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:39 -msgid "" -"(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-" -"media-repo),  thanks to a PR by [Michael Hollister](https://github.com" -"/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of " -"the [Circles app](https://circu.li/) (see the [changelog " -"entry](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-" -"media-repo-support))" +msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:40 -msgid "" -"(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat" -"/schildichat-desktop) client app (fork of [Element " -"Web)](https://github.com/element-hq/element-web), thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#schildichat-support))" +msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:41 -msgid "" -"(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#postgres-parameters-are-automatically-tuned-now))" +msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:42 -msgid "" -"(2023-10-23) Enabling federation of the room directory for Synapse (see " -"the [changelog entry](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" +msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))" msgstr "" #: ../../../YEAR-IN-REVIEW.md:44 -msgid "" -"The most recent change in the list above (Enabling federation of the room" -" directory for Synapse) has been somewhat **controversial** as it goes " -"against upstream defaults for Synapse. Nevertheless, we believe it " -"**promotes the well-being of the Matrix Federation by improving room " -"discovery**." +msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**." msgstr "" #: ../../../YEAR-IN-REVIEW.md:46 -msgid "" -"**Matrix Federation Stats** (containing the percentage of servers " -"publishing their room directory publicly) are posted to " -"[TWIM](https://matrix.org/category/this-week-in-matrix/) each week by " -"[Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The " -"number of servers which [currently published their room directory " -"publicly](https://matrix.org/blog/2023/12/2/this-week-in-" -"matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" +msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:48 -msgid "" -"**2.4% more** than when it was when [first published to " -"TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03" -"/#matrix-federation-stats) (1 month earlier, in November)" +msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:49 -msgid "" -"likely about **15+% more** than from before we flipped the switch (in " -"October)" +msgid "likely about **15+% more** than from before we flipped the switch (in October)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:51 -msgid "" -"Hopefully, Synapse defaults would also change the same way and we'd see " -"the number of servers publicly listing their room directory grow faster." +msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster." msgstr "" #: ../../../YEAR-IN-REVIEW.md:53 -msgid "" -"With this configuration change in place, projects like " -"[MatrixRooms.info](https://matrixrooms.info/) (made by " -"[etke.cc](https://etke.cc/)) and potentially others in the future, can " -"discover, index the metadata (room address, title, topic, number of " -"users, etc.) and make public rooms browsable & searchable across the " -"whole Matrix Federation. It'd be great if users joining Matrix could more" -" easily find interesting communities that match their interests!" +msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!" msgstr "" #: ../../../YEAR-IN-REVIEW.md:55 -msgid "" -"On the **media side of things**, besides Jitsi getting better Matrix " -"integration (via the aforementioned Matrix User Verification Service), " -"we've also had some [Coturn security " -"tightening](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md" -"#backward-compatibility-tightening-coturn-security-can-lead-to-" -"connectivity-issues) as well as [performance " -"optimizations](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-" -"can-now-use-host-networking) for configurations exposing lots of network " -"ports." +msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports." msgstr "" #: ../../../YEAR-IN-REVIEW.md:57 -msgid "" -"[Element Call](https://github.com/element-hq/element-call) seems to have " -"become a nice and polished product lately (as proclaimed in [The Matrix " -"Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-" -"holiday-update-2023/)), so 2024 is likely the year we'll see support for " -"it in the playbook. Element Call depends on the " -"[LiveKit](https://livekit.io/) streaming server (which is also useful to " -"developers even by itself), so the first step is likely to see LiveKit " -"support in mash-playbook via a reusable Ansible role. Such a LiveKit " -"Ansible role could later easily land in matrix-docker-ansible-deploy and " -"an Element Call static website could be hooked to it." +msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it." msgstr "" #: ../../../YEAR-IN-REVIEW.md:59 -msgid "" -"Besides these highlights, there were many other relatively large changes " -"announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-" -"ansible-" -"deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and " -"hundreds of other more minor (but still important) playbook changes that " -"didn't get a mention." +msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention." msgstr "" #: ../../../YEAR-IN-REVIEW.md:61 -msgid "" -"We have **hundreds of contributors to thank for their hard work** on " -"making Matrix self-hosting better for all of us! It should be noted that " -"**support comes in many shapes**, not only in raw code commits and " -"financial help (via [donations](https://liberapay.com/s.pantaleev) or " -"using the [etke.cc managed Matrix hosting service](https://etke.cc/) " -"which is based on matrix-docker-ansible-deploy). It also comes in the " -"shape of code reviews, helping others with " -"[issues](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues), reporting new issues, participating in our support room " -"on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to" -"/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has " -"been there to make matrix-docker-ansible-deploy better in 2023, thank " -"you! 🙇‍♂️" +msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️" msgstr "" #: ../../../YEAR-IN-REVIEW.md:64 @@ -429,34 +173,11 @@ msgid "2022" msgstr "" #: ../../../YEAR-IN-REVIEW.md:66 -msgid "" -"For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/), 2022 started with **breaking the** " -"[**Synapse**](https://github.com/element-hq/synapse) **monopoly** by " -"[adding support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#dendrite-support) for the [Dendrite](https://github.com/matrix-" -"org/dendrite) Matrix homeserver in early January. This required various " -"internal changes so that the [Ansible](https://www.ansible.com/) playbook" -" would not be Synapse-centric anymore. This groundwork paved the way for " -"continuing in this direction and we [added " -"support](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#conduit-support) for [Conduit](https://conduit.rs/) in August." +msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August." msgstr "" #: ../../../YEAR-IN-REVIEW.md:68 -msgid "" -"When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, " -"2022 was the year of the non-Synapse homeserver implementation. In " -"practice, none of these homeserver implementations seem ready for prime-" -"time yet and there is no migration path when coming from Synapse. Having " -"done our job of adding support for these alternative homeserver " -"implementations, we can say that we're not getting in the way of future " -"progress. It's time for the Dendrite developers to push harder " -"(development-wise) and for the Synapse developers to take a well-deserved" -" long (infinite) break, and we may get to see more people migrating away " -"from Synapse in the next year(s)." +msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)." msgstr "" #: ../../../YEAR-IN-REVIEW.md:70 @@ -464,35 +185,19 @@ msgid "Support for the following new **bridges** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:72 -msgid "" -"[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#postmoogle-email-bridge-support) for bi-directional email bridging, " -"which supersedes my old and simplistic " -"[email2matrix](https://github.com/devture/email2matrix) one-way bridge-" -"bot" +msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot" msgstr "" #: ../../../YEAR-IN-REVIEW.md:73 -msgid "" -"[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#mautrix-discord-support)" +msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:74 -msgid "" -"[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-" -"skype-bridge-bridging-support)" +msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:75 -msgid "" -"[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"appservice-kakaotalk-support)" +msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:77 @@ -500,38 +205,23 @@ msgid "Support for the following new **bots** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:79 -msgid "" -"[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#buscarron-bot-support)" +msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:80 -msgid "" -"[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#honoroit-bot-support)" +msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:81 -msgid "" -"[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#matrix-registration-bot-support)" +msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:82 -msgid "" -"[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"hookshot-bridging-support)" +msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:83 -msgid "" -"[maubot](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-" -"support)" +msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:85 @@ -539,144 +229,65 @@ msgid "Support for the following new **components and services** was added:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:87 -msgid "" -"[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-" -"backup-support)" +msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:88 -msgid "" -"[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-" -"comments-support)" +msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:89 -msgid "" -"[Cinny](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-" -"support) client support" +msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support" msgstr "" #: ../../../YEAR-IN-REVIEW.md:90 -msgid "" -"[ntfy](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-" -"push-notifications-support) notifications" +msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications" msgstr "" #: ../../../YEAR-IN-REVIEW.md:91 -msgid "" -"[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-" -"ldap-registration-proxy-support)" +msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:92 -msgid "" -"[matrix\\_encryption\\_disabler support](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#matrix_encryption_disabler-support)" +msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:93 -msgid "" -"[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-" -"docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3" -"-storage-provider-support) to stop the Synapse media store from being a " -"scalability problem. This brought along [another " -"feature](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#synapse-container-image-customization-support) - an easier way to " -"customize the Synapse container image without having to fork and self-" -"build all of it from scratch" +msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch" msgstr "" #: ../../../YEAR-IN-REVIEW.md:95 -msgid "" -"Besides these major user-visible changes, a lot of work also happened " -"**under the hood**:" +msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:97 -msgid "" -"we made [major improvements to Synapse " -"workers](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#potential-backward-compatibility-break-major-improvements-to-synapse-" -"workers) - adding support for stream writers and for running multiple " -"workers of various kinds (federation senders, pushers, background task " -"processing workers, etc.)" +msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:98 -msgid "" -"we [improved the compatibility of (Synapse + workers) with the rest of " -"the playbook](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-" -"works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by " -"introducing a new `matrix-synapse-reverse-proxy-companion-service` " -"service" +msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service" msgstr "" #: ../../../YEAR-IN-REVIEW.md:99 -msgid "" -"we started [splitting various Ansible roles out of the Matrix playbook " -"and into independent roles](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md" -"#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-" -"postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-" -"self-hosting/ansible-role-postgres)), which could be included in other " -"Ansible playbooks. In fact, these roles already power a few **interesting" -" other sibling playbooks**:" +msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:" msgstr "" #: ../../../YEAR-IN-REVIEW.md:100 -msgid "" -"[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-" -"ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted " -"[Git](https://git-scm.com/) service) server" +msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server" msgstr "" #: ../../../YEAR-IN-REVIEW.md:101 -msgid "" -"[nextcloud-docker-ansible-deploy](https://github.com/spantaleev" -"/nextcloud-docker-ansible-deploy), for deploying a " -"[Nextcloud](https://nextcloud.com/) groupware server" +msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server" msgstr "" #: ../../../YEAR-IN-REVIEW.md:102 -msgid "" -"[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev" -"/vaultwarden-docker-ansible-deploy), for deploying a " -"[Vaultwarden](https://github.com/dani-garcia/vaultwarden) password " -"manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible" -" server)" +msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)" msgstr "" #: ../../../YEAR-IN-REVIEW.md:104 -msgid "" -"These sibling playbooks co-exist nicely with one another due to using " -"[Traefik](https://traefik.io/) for reverse-proxying, instead of trying to" -" overtake the whole server by running their own " -"[nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix " -"playbook will follow suit and be powered by Traefik by default." +msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default." msgstr "" #: ../../../YEAR-IN-REVIEW.md:106 -msgid "" -"Last, but not least, to optimize our [etke.cc managed Matrix hosting " -"service](https://etke.cc/)'s performance (but also individual Ansible " -"playbook runs for people self-hosting by themselves using the playbook), " -"we've [improved playbook runtime 2-5x](https://github.com/spantaleev" -"/matrix-docker-ansible-" -"deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-" -"performance-improvements-in-playbook-runtime) by employing various " -"Ansible tricks." +msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/README.po b/i18n/locales/jp/LC_MESSAGES/docs/README.po index 893ee1477..bec80a71d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/README.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/README.po @@ -25,29 +25,19 @@ msgid "Table of Contents" msgstr "" #: ../../../docs/README.md:3 -msgid "" -"⬇️ Installaton guides " +msgid "⬇️ Installaton guides " msgstr "" #: ../../../docs/README.md:5 -msgid "" -"There are two installation guides available for beginners and advanced " -"users." +msgid "There are two installation guides available for beginners and advanced users." msgstr "" #: ../../../docs/README.md:7 -msgid "" -"⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended " -"for those who do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/README.md:9 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide." msgstr "" #: ../../../docs/README.md:11 @@ -75,59 +65,39 @@ msgid "🛠️ Configuration options" msgstr "" #: ../../../docs/README.md:28 -msgid "" -"You can check useful documentation for configuring components here: " -"[Configuring the playbook](configuring-playbook.md)" +msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)" msgstr "" #: ../../../docs/README.md:30 -msgid "" -"[Administration](configuring-playbook.md#administration) - services that " -"help you in administrating and monitoring your Matrix installation" +msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation" msgstr "" #: ../../../docs/README.md:32 -msgid "" -"[Authentication and user-related](configuring-playbook.md#authentication-" -"and-user-related) - extend and modify how users are authenticated on your" -" homeserver" +msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver" msgstr "" #: ../../../docs/README.md:34 -msgid "" -"[Bots](configuring-playbook.md#bots) - bots provide various additional " -"functionality to your installation" +msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation" msgstr "" #: ../../../docs/README.md:36 -msgid "" -"[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can " -"be used to connect your Matrix installation with third-party " -"communication networks" +msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks" msgstr "" #: ../../../docs/README.md:38 -msgid "" -"[Clients](configuring-playbook.md#clients) - web clients for Matrix that " -"you can host on your own domains" +msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains" msgstr "" #: ../../../docs/README.md:40 -msgid "" -"[Core service adjustments](configuring-playbook.md#core-service-" -"adjustments) - backbone of your Matrix system" +msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system" msgstr "" #: ../../../docs/README.md:42 -msgid "" -"[File Storage](configuring-playbook.md#file-storage) - use alternative " -"file storage to the default `media_store` folder" +msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder" msgstr "" #: ../../../docs/README.md:46 -msgid "" -"[Other specialized services](configuring-playbook.md#other-specialized-" -"services) - various services that don't fit any other categories" +msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories" msgstr "" #: ../../../docs/README.md:48 @@ -135,10 +105,7 @@ msgid "👨‍🔧 Maintenance" msgstr "" #: ../../../docs/README.md:50 -msgid "" -"If your server and services experience issues, feel free to come to [our " -"support room](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com) and ask for help." +msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help." msgstr "" #: ../../../docs/README.md:54 @@ -162,15 +129,11 @@ msgid "[Upgrading services](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/README.md:64 -msgid "" -"Other documentation pages " +msgid "Other documentation pages " msgstr "" #: ../../../docs/README.md:66 -msgid "" -"ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, " -"with a focus on this Ansible playbook" +msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook" msgstr "" #: ../../../docs/README.md:70 @@ -208,4 +171,3 @@ msgstr "" #: ../../../docs/README.md:86 msgid "[Updating users passwords](updating-users-passwords.md)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po index 5c7c21550..3d849ba01 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po @@ -25,15 +25,11 @@ msgid "Alternative architectures" msgstr "" #: ../../../docs/alternative-architectures.md:3 -msgid "" -"As stated in the [Prerequisites](prerequisites.md), currently only " -"`amd64` (`x86_64`) is fully supported." +msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported." msgstr "" #: ../../../docs/alternative-architectures.md:5 -msgid "" -"The playbook automatically determines the target server's architecture " -"(the `matrix_architecture` variable) to be one of the following:" +msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:" msgstr "" #: ../../../docs/alternative-architectures.md:7 @@ -49,9 +45,7 @@ msgid "`arm64`" msgstr "" #: ../../../docs/alternative-architectures.md:11 -msgid "" -"Some tools and container images can be built on the host or other " -"measures can be used to install on that architecture." +msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture." msgstr "" #: ../../../docs/alternative-architectures.md:13 @@ -59,19 +53,9 @@ msgid "Implementation details" msgstr "" #: ../../../docs/alternative-architectures.md:15 -msgid "" -"For `amd64`, prebuilt container images (see the [container images we use" -"](container-images.md)) are used for all components (except [Hydrogen" -"](configuring-playbook-client-hydrogen.md), which goes through self-" -"building)." +msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)." msgstr "" #: ../../../docs/alternative-architectures.md:17 -msgid "" -"For other architecture (`arm64`, `arm32`), components which have a " -"prebuilt image make use of it. If the component is not available for the " -"specific architecture, [self-building](self-building.md) will be used. " -"Not all components support self-building though, so your mileage may " -"vary." +msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po index aa6d88c72..f976b2a7d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po @@ -25,17 +25,11 @@ msgid "Running this playbook" msgstr "" #: ../../../docs/ansible.md:4 -msgid "" -"This playbook is meant to be run using " -"[Ansible](https://www.ansible.com/)." +msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)." msgstr "" #: ../../../docs/ansible.md:6 -msgid "" -"Ansible typically runs on your local computer and carries out tasks on a " -"remote server. If your local computer cannot run Ansible, you can also " -"run Ansible on some server somewhere (including the server you wish to " -"install to)." +msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)." msgstr "" #: ../../../docs/ansible.md:8 @@ -43,30 +37,19 @@ msgid "Supported Ansible versions" msgstr "" #: ../../../docs/ansible.md:10 -msgid "" -"To manually check which version of Ansible you're on, run: `ansible " -"--version`." +msgid "To manually check which version of Ansible you're on, run: `ansible --version`." msgstr "" #: ../../../docs/ansible.md:12 -msgid "" -"For the **best experience**, we recommend getting the **latest version of" -" Ansible available**." +msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**." msgstr "" #: ../../../docs/ansible.md:14 -msgid "" -"We're not sure what's the minimum version of Ansible that can run this " -"playbook successfully. The lowest version that we've confirmed (on " -"2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined " -"with `ansible` (`4.10.0`)." +msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)." msgstr "" #: ../../../docs/ansible.md:16 -msgid "" -"If your distro ships with an Ansible version older than this, you may run" -" into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using " -"Ansible via Docker](#using-ansible-via-docker)." +msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)." msgstr "" #: ../../../docs/ansible.md:18 @@ -74,45 +57,23 @@ msgid "Upgrading Ansible" msgstr "" #: ../../../docs/ansible.md:20 -msgid "" -"Depending on your distribution, you may be able to upgrade Ansible in a " -"few different ways:" +msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:" msgstr "" #: ../../../docs/ansible.md:22 -msgid "" -"by using an additional repository (PPA, etc.), which provides newer " -"Ansible versions. See instructions for " -"[CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-rhel-centos-or-fedora), " -"[Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-debian), or " -"[Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html" -"#installing-ansible-on-ubuntu) on the Ansible website." +msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website." msgstr "" #: ../../../docs/ansible.md:24 -msgid "" -"by removing the Ansible package (`yum remove ansible` or `apt-get remove " -"ansible`) and installing via " -"[pip](https://pip.pypa.io/en/stable/installation/) (`pip install " -"ansible`)." +msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)." msgstr "" #: ../../../docs/ansible.md:26 -msgid "" -"If using the `pip` method, do note that the `ansible-playbook` binary may" -" not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-" -"variable), but in some more special location like `/usr/local/bin" -"/ansible-playbook`. You may need to invoke it using the full path." +msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path." msgstr "" #: ../../../docs/ansible.md:28 -msgid "" -"**Note**: Both of the above methods are a bad way to run system software " -"such as Ansible. If you find yourself needing to resort to such hacks, " -"please consider reporting a bug to your distribution and/or switching to " -"a sane distribution, which provides up-to-date software." +msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software." msgstr "" #: ../../../docs/ansible.md:30 @@ -120,25 +81,15 @@ msgid "Using Ansible via Docker" msgstr "" #: ../../../docs/ansible.md:32 -msgid "" -"Alternatively, you can run Ansible inside a Docker container (powered by " -"the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker " -"image)." +msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)." msgstr "" #: ../../../docs/ansible.md:34 -msgid "" -"This ensures that you're using a very recent Ansible version, which is " -"less likely to be incompatible with the playbook." +msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook." msgstr "" #: ../../../docs/ansible.md:36 -msgid "" -"You can either [run Ansible in a container on the Matrix server itself" -"](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run " -"Ansible in a container on another computer (not the Matrix server" -")](#running-ansible-in-a-container-on-another-computer-not-the-matrix-" -"server)." +msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)." msgstr "" #: ../../../docs/ansible.md:38 @@ -146,52 +97,27 @@ msgid "Running Ansible in a container on the Matrix server itself" msgstr "" #: ../../../docs/ansible.md:40 -msgid "" -"To run Ansible in a (Docker) container on the Matrix server itself, you " -"need to have a working Docker installation. Docker is normally installed " -"by the playbook, so this may be a bit of a chicken and egg problem. To " -"solve it:" +msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:" msgstr "" #: ../../../docs/ansible.md:42 -msgid "" -"you **either** need to install Docker manually first. Follow [the " -"upstream instructions](https://docs.docker.com/engine/install/) for your " -"distribution and consider setting " -"`matrix_playbook_docker_installation_enabled: false` in your `vars.yml` " -"file, to prevent the playbook from installing Docker" +msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker" msgstr "" #: ../../../docs/ansible.md:43 -msgid "" -"**or** you need to run the playbook in another way (e.g. [Running Ansible" -" in a container on another computer (not the Matrix server)](#running-" -"ansible-in-a-container-on-another-computer-not-the-matrix-server)) at " -"least the first time around" +msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around" msgstr "" #: ../../../docs/ansible.md:45 -msgid "" -"Once you have a working Docker installation on the server, **clone the " -"playbook** somewhere on the server and configure it as per usual " -"(`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in " -"[configuring the playbook](configuring-playbook.md)." +msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)." msgstr "" #: ../../../docs/ansible.md:47 -msgid "" -"You would then need to add `ansible_connection=community.docker.nsenter` " -"to the host line in `inventory/hosts`. This tells Ansible to connect to " -"the \"remote\" machine by switching Linux namespaces with " -"[nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead " -"of using SSH." +msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH." msgstr "" #: ../../../docs/ansible.md:49 -msgid "" -"Alternatively, you can leave your `inventory/hosts` as is and specify the" -" connection type in **each** `ansible-playbook` call you do later, like " -"this: `ansible-playbook --connection=community.docker.nsenter …`" +msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`" msgstr "" #: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71 @@ -199,23 +125,15 @@ msgid "Run this from the playbook's directory:" msgstr "" #: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84 -msgid "" -"Once you execute the above command, you'll be dropped into a `/work` " -"directory inside a Docker container. The `/work` directory contains the " -"playbook's code." +msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code." msgstr "" #: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86 -msgid "" -"First, consider running `git config --global --add safe.directory /work` " -"to [resolve directory ownership issues](#resolve-directory-ownership-" -"issues)." +msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)." msgstr "" #: ../../../docs/ansible.md:67 -msgid "" -"Finally, you can execute `ansible-playbook …` (or `ansible-playbook " -"--connection=community.docker.nsenter …`) commands as per normal now." +msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now." msgstr "" #: ../../../docs/ansible.md:69 @@ -223,10 +141,7 @@ msgid "Running Ansible in a container on another computer (not the Matrix server msgstr "" #: ../../../docs/ansible.md:82 -msgid "" -"The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into " -"the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different" -" path (not in `$HOME/.ssh/id_rsa`), adjust that part." +msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part." msgstr "" #: ../../../docs/ansible.md:88 @@ -238,22 +153,15 @@ msgid "If you don't use SSH keys for authentication" msgstr "" #: ../../../docs/ansible.md:92 -msgid "" -"If you don't use SSH keys for authentication, simply remove that whole " -"line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." +msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)." msgstr "" #: ../../../docs/ansible.md:94 -msgid "" -"To authenticate at your server using a password, you need to add a " -"package. So, when you are in the shell of the ansible docker container " -"(the previously used `docker run -it …` command), run:" +msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:" msgstr "" #: ../../../docs/ansible.md:100 -msgid "" -"Then, to be asked for the password whenever running an `ansible-" -"playbook` command add `--ask-pass` to the arguments of the command." +msgid "Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command." msgstr "" #: ../../../docs/ansible.md:102 @@ -261,23 +169,13 @@ msgid "Resolve directory ownership issues" msgstr "" #: ../../../docs/ansible.md:104 -msgid "" -"Because you're `root` in the container running Ansible and this likely " -"differs fom the owner (your regular user account) of the playbook " -"directory outside of the container, certain playbook features which use " -"`git` locally may report warnings such as:" +msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:" msgstr "" #: ../../../docs/ansible.md:106 -msgid "" -"fatal: unsafe repository ('/work' is owned by someone else) To add an " -"exception for this directory, call: git config --global --add " -"safe.directory /work" +msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /work" msgstr "" #: ../../../docs/ansible.md:110 -msgid "" -"These errors can be resolved by making `git` trust the playbook directory" -" by running `git config --global --add safe.directory /work`" +msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po index 4e8c8d222..b5f7221c0 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po @@ -21,9 +21,7 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-captcha.md:1 -msgid "" -"(Adapted from the [upstream project](https://github.com/element-" -"hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" +msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))" msgstr "" #: ../../../docs/configuring-captcha.md:3 @@ -31,17 +29,11 @@ msgid "Overview" msgstr "" #: ../../../docs/configuring-captcha.md:5 -msgid "" -"Captcha can be enabled for this home server. This file explains how to do" -" that." +msgid "Captcha can be enabled for this home server. This file explains how to do that." msgstr "" #: ../../../docs/configuring-captcha.md:7 -msgid "" -"The captcha mechanism used is Google's " -"[ReCaptcha](https://www.google.com/recaptcha/). This requires API keys " -"from Google. If your homeserver is Dendrite then " -"[hCapcha](https://www.hcaptcha.com) can be used instead." +msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead." msgstr "" #: ../../../docs/configuring-captcha.md:9 @@ -63,9 +55,7 @@ msgid "" msgstr "" #: ../../../docs/configuring-captcha.md:17 -msgid "" -"Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox " -"option" +msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option" msgstr "" #: ../../../docs/configuring-captcha.md:19 @@ -73,9 +63,7 @@ msgid "Setting ReCaptcha keys" msgstr "" #: ../../../docs/configuring-captcha.md:21 -msgid "" -"Once registered as above, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-captcha.md:35 @@ -89,4 +77,3 @@ msgstr "" #: ../../../docs/configuring-captcha.md:43 msgid "Setting hCaptcha keys" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po index d53ffdd1d..fbedb7d24 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po @@ -25,10 +25,7 @@ msgid "Configuring your DNS settings" msgstr "" #: ../../../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)" +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:5 @@ -40,30 +37,19 @@ msgid "DNS setting for server delegation (optional)" msgstr "" #: ../../../docs/configuring-dns.md:9 -msgid "" -"In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " -"we recommend to use a short user ID like `@alice:example.com` instead of " -"`@alice:matrix.example.com`." +msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`." msgstr "" #: ../../../docs/configuring-dns.md:11 -msgid "" -"To use such an ID, you don't need to install anything on the actual " -"`example.com` server. Instead, you need to instruct the Matrix network " -"that Matrix services for `example.com` are redirected over to " -"`matrix.example.com`. This redirection is also known as \"delegation\"." +msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"." msgstr "" #: ../../../docs/configuring-dns.md:13 -msgid "" -"As we discuss in [Server Delegation](howto-server-delegation.md), server " -"delegation can be configured in either of these ways:" +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:" msgstr "" #: ../../../docs/configuring-dns.md:15 -msgid "" -"Setting up a `/.well-known/matrix/server` file on the base domain " -"(`example.com`)" +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" #: ../../../docs/configuring-dns.md:16 @@ -71,29 +57,15 @@ msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" #: ../../../docs/configuring-dns.md:18 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file, instead of using a " -"DNS SRV record." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record." msgstr "" #: ../../../docs/configuring-dns.md:20 -msgid "" -"If you choose the recommended method (file-based delegation), you do not " -"need to configure the DNS record to enable server delegation. You will " -"need to add a necessary configuration later, when you [finalize the " -"installation](installing.md#finalize-the-installation) after installing " -"and starting Matrix services." +msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services." msgstr "" #: ../../../docs/configuring-dns.md:22 -msgid "" -"On the other hand, if you choose this method (setting up a DNS SRV " -"record), you need to configure the additional DNS record as well as " -"adjust SSL certificate handling. Take a look at this documentation for " -"more information: [Server Delegation via a DNS SRV record (advanced" -")](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-" -"advanced)" +msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/configuring-dns.md:24 @@ -101,10 +73,7 @@ msgid "DNS settings for services enabled by default" msgstr "" #: ../../../docs/configuring-dns.md:26 -msgid "" -"To serve the base domain (`example.com`) and [Element Web](configuring-" -"playbook-client-element-web.md) with the default subdomain, adjust DNS " -"records as below." +msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below." msgstr "" #: ../../../docs/configuring-dns.md @@ -160,20 +129,11 @@ msgid "`matrix.example.com`" msgstr "" #: ../../../docs/configuring-dns.md:33 -msgid "" -"As the table illustrates, you need to create 2 subdomains " -"(`matrix.example.com` and `element.example.com`) and point both of them " -"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" #: ../../../docs/configuring-dns.md:35 -msgid "" -"The `element.example.com` subdomain is necessary, because this playbook " -"installs the [Element Web](https://github.com/element-hq/element-web) " -"client for you by default. If you'd rather instruct the playbook not to " -"install Element Web (`matrix_client_element_enabled: false` when " -"[Configuring the playbook](configuring-playbook.md) later), feel free to " -"skip the `element.example.com` DNS record." +msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record." msgstr "" #: ../../../docs/configuring-dns.md:37 @@ -181,9 +141,7 @@ msgid "Be mindful as to how long it will take for the DNS records to propagate." msgstr "" #: ../../../docs/configuring-dns.md:39 -msgid "" -"If you are using Cloudflare DNS, make sure to disable the proxy and set " -"all records to \"DNS only\". Otherwise, fetching certificates will fail." +msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail." msgstr "" #: ../../../docs/configuring-dns.md:41 @@ -191,9 +149,7 @@ msgid "DNS settings for optional services/features" msgstr "" #: ../../../docs/configuring-dns.md:43 -msgid "" -"For other services which may need subdomain settings, see the table below" -" and configure the DNS (`CNAME`) records accordingly." +msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly." msgstr "" #: ../../../docs/configuring-dns.md @@ -217,9 +173,7 @@ msgid "`jitsi`" msgstr "" #: ../../../docs/configuring-dns.md -msgid "" -"[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) " -"monitoring system" +msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system" msgstr "" #: ../../../docs/configuring-dns.md @@ -331,9 +285,7 @@ msgid "443" msgstr "" #: ../../../docs/configuring-dns.md -msgid "" -"[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix" -"](configuring-playbook-email2matrix.md) email bridges" +msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges" msgstr "" #: ../../../docs/configuring-dns.md @@ -373,20 +325,11 @@ msgid "SRV record for ma1sd" msgstr "" #: ../../../docs/configuring-dns.md:68 -msgid "" -"To make ma1sd enable its federation features, you need to set up a " -"`_matrix-identity._tcp` SRV record. Don't confuse this with the " -"`_matrix._tcp` SRV record for server delegation. See the table above and " -"[this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for " -"values which need to be specified." +msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified." msgstr "" #: ../../../docs/configuring-dns.md:70 -msgid "" -"When setting up a SRV record, if you are asked for a service and protocol" -" instead of a hostname split the host value from the table where the " -"period is. For example use service as `_matrix-identity` and protocol as " -"`_tcp`." +msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`." msgstr "" #: ../../../docs/configuring-dns.md:72 @@ -394,16 +337,9 @@ msgid "MX and TXT records for Postmoogle" msgstr "" #: ../../../docs/configuring-dns.md:74 -msgid "" -"To make Postmoogle enable its email sending features, you need to " -"configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above " -"for values which need to be specified." +msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified." msgstr "" #: ../../../docs/configuring-dns.md:78 -msgid "" -"[▶️](getting-the-playbook.md) When you're done with the DNS configuration" -" and ready to proceed, continue with [Getting the playbook](getting-the-" -"playbook.md)." +msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po index ef770ef02..f968d56f4 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 @@ -21,37 +21,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:1 -msgid "" -"Setting up Prometheus Alertmanager integration via matrix-alertmanager-" -"receiver (optional)" +msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:3 -msgid "" -"The playbook can install and configure the [matrix-alertmanager-" -"receiver](https://github.com/metio/matrix-alertmanager-receiver) service " -"for you. It's a " -"[client](https://prometheus.io/docs/alerting/latest/clients/) for " -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)," -" allowing you to deliver alerts to Matrix rooms." +msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:5 -msgid "" -"See the project's [documentation](https://github.com/metio/matrix-" -"alertmanager-receiver/blob/main/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:7 -msgid "" -"This service is meant to be used with an external " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"instance. It's **not** meant to be integrated with the [Prometheus & " -"Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by" -" this playbook, because the Alertmanager component is not installed by " -"it." +msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:9 @@ -63,22 +45,15 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:13 -msgid "" -"This service uses a bot (with a username specified in " -"`matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for " -"delivering messages." +msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:15 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 @@ -90,10 +65,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 @@ -101,21 +73,15 @@ msgid "Join to rooms as the bot manually" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 -msgid "" -"ℹ️ **This bot does not accept room invitations automatically**. To " -"deliver messages to rooms, the bot must be joined to all rooms manually." +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:33 -msgid "" -"For each new room you would like the bot to deliver alerts to, invite the" -" bot to the room." +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:35 -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." +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:37 @@ -123,17 +89,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 -msgid "" -"See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for " -"additional configuration variables." +msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 @@ -141,26 +101,15 @@ msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 -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." +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:67 -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." +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:69 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 @@ -168,10 +117,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the matrix-alertmanager-receiver domain to the " -"Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 @@ -179,9 +125,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 @@ -189,10 +133,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.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:" +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:94 @@ -200,24 +141,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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:98 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:100 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:102 @@ -229,127 +161,5 @@ msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 -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`." +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 "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/metio/matrix-alertmanager-" -#~ "receiver) to learn more about what " -#~ "this component does and why it " -#~ "might be useful to you." -#~ msgstr "" - -#~ msgid "" -#~ "At the moment, **setting up this " -#~ "service's bot requires some manual " -#~ "actions** as described below in [Account" -#~ " and room preparation](#account-and-" -#~ "room-preparation)." -#~ msgstr "" - -#~ msgid "" -#~ "To enable matrix-alertmanager-receiver, " -#~ "add the following configuration to your" -#~ " `inventory/host_vars/matrix.example.com/vars.yml` file:" -#~ msgstr "" - -#~ msgid "Account and room preparation" -#~ msgstr "" - -#~ msgid "" -#~ "The playbook can automatically create " -#~ "users, but it cannot automatically " -#~ "obtain access tokens, nor perform any" -#~ " of the other manual actions below." -#~ msgstr "" - -#~ msgid "" -#~ "`matrix-alertmanager-receiver` uses a " -#~ "bot (with a username specified in " -#~ "`matrix_alertmanager_receiver_config_matrix_user_id_localpart` -" -#~ " see above) for delivering messages. " -#~ "You need to **manually register this " -#~ "bot acccount and obtain an access " -#~ "token for it**." -#~ msgstr "" - -#~ msgid "" -#~ "[Register a new user](registering-users.md):" -#~ " `ansible-playbook -i inventory/hosts " -#~ "setup.yml --extra-vars='username=bot.alertmanager.receiver" -#~ " password=PASSWORD_FOR_THE_BOT admin=no' --tags" -#~ "=register-user`" -#~ msgstr "" - -#~ msgid "" -#~ "[Obtain an access token](obtaining-access-" -#~ "tokens.md) for the bot's user account" -#~ msgstr "" - -#~ msgid "Invite the bot to a room where you'd like to alerts to be delivered" -#~ msgstr "" - -#~ msgid "" -#~ "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 "" - -#~ msgid "" -#~ "(Optionally) Adjust " -#~ "`matrix_alertmanager_receiver_config_matrix_room_mapping` to " -#~ "create a mapping between the new " -#~ "room and its ID" -#~ msgstr "" - -#~ msgid "" -#~ "Steps 1 and 2 above only need " -#~ "to be done once, while preparing " -#~ "your [configuration](#adjusting-the-playbook-" -#~ "configuration)." -#~ msgstr "" - -#~ msgid "" -#~ "Steps 3 and 4 need to be " -#~ "done for each new room you'd like" -#~ " the bot to deliver alerts to. " -#~ "Step 5 is optional and provides " -#~ "cleaner `/alert/` URLs." -#~ msgstr "" - -#~ msgid "" -#~ "Now that you've [prepared the bot " -#~ "account and room](#account-and-room-" -#~ "preparation), [configured the playbook" -#~ "](#adjusting-the-playbook-configuration), and " -#~ "potentially [adjusted your DNS records" -#~ "](#adjusting-dns-records), you can run " -#~ "the playbook with [playbook tags](playbook-" -#~ "tags.md) as below:" -#~ msgstr "" - -#~ 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 "" - -#~ msgid "" -#~ "This bot does **not** accept room " -#~ "invitations automatically (like many other " -#~ "bots do). To deliver messages to " -#~ "rooms, **the bot must be joined to" -#~ " all rooms manually** - see Step " -#~ "4 of the [Account and room " -#~ "preparation](#account-and-room-preparation) " -#~ "section." -#~ 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 55a27cd93..a52e548fe 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 @@ -25,28 +25,15 @@ msgid "Setting up Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:3 -msgid "" -"Appservice Double Puppet is a homeserver appservice through which bridges" -" (and potentially other services) can impersonate any user on the " -"homeserver." +msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:5 -msgid "" -"This is useful for performing [double-" -"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via" -" the [appservice method](https://docs.mau.fi/bridges/general/double-" -"puppeting.html#appservice-method-new). The Appservice Double Puppet " -"service is an implementation of this approach." +msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:7 -msgid "" -"Previously, bridges supported performing [double-" -"puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"with the help of the [Shared Secret Auth password provider module" -"](./configuring-playbook-shared-secret-auth.md), but this old and hacky " -"solution has been superseded by this Appservice Double Puppet method." +msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:9 @@ -54,10 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:11 -msgid "" -"To enable the Appservice Double Puppet service, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:17 @@ -65,9 +49,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:19 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:26 @@ -75,24 +57,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:28 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:30 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:32 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:34 @@ -100,8 +73,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-appservice-double-puppet.md:36 -msgid "" -"When enabled, double puppeting will automatically be enabled for all " -"bridges that support double puppeting via the appservice method." +msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po index fc4f586b9..356109443 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 @@ -25,17 +25,11 @@ msgid "Setting up Draupnir for All/D4A (optional)" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3 -msgid "" -"The playbook can install and configure the [Draupnir](https://github.com" -"/the-draupnir-project/Draupnir) moderation tool for you in appservice " -"mode." +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5 -msgid "" -"Appservice mode can be used together with the regular [Draupnir bot" -"](configuring-playbook-bot-draupnir.md) or independently. Details about " -"the differences between the 2 modes are described below." +msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7 @@ -43,43 +37,23 @@ msgid "Draupnir Appservice mode compared to Draupnir bot mode" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9 -msgid "" -"The administrative functions for managing the appservice are alpha " -"quality and very limited. However, the experience of using an appservice-" -"provisioned Draupnir is on par with the experience of using Draupnir from" -" bot mode except in the case of avatar customisation as described later " -"on in this document." +msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11 -msgid "" -"Draupnir for all is the way to go if you need more than 1 Draupnir " -"instance, but you don't need access to Synapse Admin features as they are" -" not accessible through Draupnir for All (Even though the commands do " -"show up in help)." +msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13 -msgid "" -"Draupnir for all in the playbook is rate-limit-exempt automatically as " -"its appservice configuration file does not specify any rate limits." +msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15 -msgid "" -"Normal Draupnir does come with the benefit of access to Synapse Admin " -"features. You are also able to more easily customise your normal Draupnir" -" than D4A as D4A even on the branch with the Avatar command (To be " -"Upstreamed to Mainline Draupnir) that command is clunky as it requires " -"the use of things like Element Web devtools. In normal Draupnir this is a" -" quick operation where you login to Draupnir with a normal client and set" -" Avatar and Display name normally." +msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17 -msgid "" -"Draupnir for all does not support external tooling like " -"[MRU](https://mru.rory.gay) as it can't access Draupnir's user account." +msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19 @@ -91,9 +65,7 @@ msgid "Create a main management room" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23 -msgid "" -"The playbook does not create a management room for your Main Draupnir. " -"You **need to create the room manually** before setting up the bot." +msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25 @@ -101,25 +73,15 @@ msgid "Note that the room must be unencrypted." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29 -msgid "" -"The management room has to be given an alias and be public when you are " -"setting up the bot for the first time as the bot does not differentiate " -"between invites and invites to the management room." +msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31 -msgid "" -"This management room is used to control who has access to your D4A " -"deployment. The room stores this data inside of the control room state so" -" your bot must have sufficient powerlevel to send custom state events. " -"This is default 50 or moderator as Element clients call this powerlevel." +msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33 -msgid "" -"As noted in the Draupnir install instructions the control room is " -"sensitive. **Anyone in this room can control the bot so it is important " -"that you only invite trusted users to this room.**" +msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35 @@ -131,11 +93,7 @@ msgid "Next, set an alias to the management room." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39 -msgid "" -"This alias can be anything you want. However, for increased security " -"during the setup phase, it is recommended to make this alias be a random " -"string. When it has been locked down after setup phase, you can give your" -" room a secondary human readable alias." +msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41 @@ -143,10 +101,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ALIAS_HERE`." +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 @@ -154,22 +109,15 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53 -msgid "" -"You can configure additional options by adding the " -"`matrix_appservice_draupnir_for_all_extension_yaml` variable." +msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55 -msgid "" -"For example, to change Draupnir's `protectAllJoinedRooms` option to " -"`true`, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69 -msgid "" -"You can refer to the upstream [documentation](https://github.com/the-" -"draupnir-project/Draupnir) for more configuration documentation." +msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71 @@ -178,19 +126,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73 -msgid "" -"The playbook ships a full copy of the example config that does transfer " -"to provisioned Draupnirs in the production-bots.yaml.j2 file in the " -"template directory of the role." +msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75 -msgid "" -"Config extension does not affect the appservices config as this config is" -" not extensible in current Draupnir anyway. It instead touches the config" -" passed to the Draupnirs that your Appservice creates. So the example " -"above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs " -"protect all joined rooms." +msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77 @@ -198,30 +138,19 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94 @@ -229,17 +158,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96 -msgid "" -"If you made it through all the steps above and your main control room was" -" joined by a user called `@draupnir-main:example.com` you have " -"succesfully installed Draupnir for All and can now start using it." +msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98 -msgid "" -"The installation of Draupnir for all in this playbook is very much Alpha " -"quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot" -" mode." +msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100 @@ -247,32 +170,15 @@ msgid "Granting Users the ability to use D4A" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102 -msgid "" -"Draupnir for all includes several security measures like that it only " -"allows users that are on its allow list to ask for a bot. To add a user " -"to this list we have 2 primary options. Using the chat to tell Draupnir " -"to do this for us or if you want to automatically do it by sending " -"`m.policy.rule.user` events that target the subject you want to allow " -"provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using" -" the chat is recomended." +msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104 -msgid "" -"The bot requires a powerlevel of 50 in the management room to control who" -" is allowed to use the bot. The bot does currently not say anything if " -"this is true or false. (This is considered a bug and is documented in " -"issue [#297](https://github.com/the-draupnir-" -"project/Draupnir/issues/297))" +msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106 -msgid "" -"To allow users or whole homeservers you type /plain @draupnir-" -"main:example.com allow `target` and target can be either a MXID or a " -"wildcard like `@*:example.com` to allow all users on example.com to " -"register. We use /plain to force the client to not attempt to mess with " -"this command as it can break Wildcard commands especially." +msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108 @@ -280,141 +186,9 @@ msgid "How to provision a D4A once you are allowed to" msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110 -msgid "" -"To provision a D4A, you need to start a chat with `@draupnir-" -"main:example.com`. The bot will reject this invite and you will shortly " -"get invited to the Draupnir control room for your newly provisioned " -"Draupnir. From here its just a normal Draupnir experience." +msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience." msgstr "" #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112 -msgid "" -"Congratulations if you made it all the way here because you now have a " -"fully working Draupnir for all deployment." +msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment." msgstr "" - -#~ msgid "Installation" -#~ msgstr "" - -#~ msgid "Create a main management room." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not create a " -#~ "management room for your Main Draupnir." -#~ " This task you have to do on" -#~ " your own." -#~ msgstr "" - -#~ msgid "" -#~ "As noted in the Draupnir install " -#~ "instructions the control room is " -#~ "sensitive. The following is said about" -#~ " the control room in the Draupnir " -#~ "install instructions." -#~ msgstr "" - -#~ msgid "" -#~ "Anyone in this room can control " -#~ "the bot so it is important that" -#~ " you only invite trusted users to " -#~ "this room. The room must be " -#~ "unencrypted since the playbook does not" -#~ " support installing Pantalaimon yet." -#~ msgstr "" - -#~ msgid "Give your main management room an alias." -#~ msgstr "" - -#~ msgid "" -#~ "Give the room from step 1 an " -#~ "alias. This alias can be anything " -#~ "you want and its recommended for " -#~ "increased security during the setup " -#~ "phase of the bot that you make " -#~ "this alias be a random string. You" -#~ " can give your room a secondary " -#~ "human readable alias when it has " -#~ "been locked down after setup phase." -#~ msgstr "" - -#~ msgid "Adjusting the playbook configuration." -#~ msgstr "" - -#~ msgid "" -#~ "Add the following configuration to your" -#~ " `inventory/host_vars/matrix.example.com/vars.yml` file " -#~ "(adapt to your needs):" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` " -#~ "with the alias you created in step" -#~ " 2." -#~ msgstr "" - -#~ msgid "" -#~ "The installation of Draupnir for all " -#~ "in this playbook is very much " -#~ "Alpha quality. Usage-wise, Draupnir for" -#~ " allis almost identical to Draupnir " -#~ "bot mode." -#~ msgstr "" - -#~ msgid "How to provision a D4A once you are allowed to." -#~ msgstr "" - -#~ msgid "" -#~ "Open a DM with @draupnir-" -#~ "main:example.com and if using an Element" -#~ " client send a message into this " -#~ "DM to finalise creating it. The " -#~ "bot will reject this invite and " -#~ "you will shortly get invited to " -#~ "the Draupnir control room for your " -#~ "newly provisioned Draupnir. From here " -#~ "its just a normal Draupnir experience." -#~ msgstr "" - -#~ msgid "Configuration of D4A" -#~ msgstr "" - -#~ msgid "" -#~ "You can refer to the upstream " -#~ "[documentation](https://github.com/the-draupnir-" -#~ "project/Draupnir) for more configuration " -#~ "documentation. Please note that the " -#~ "playbook ships a full copy of the" -#~ " example config that does transfer to" -#~ " provisioned Draupnirs in the " -#~ "production-bots.yaml.j2 file in the " -#~ "template directory of the role." -#~ msgstr "" - -#~ msgid "" -#~ "Please note that Config extension does" -#~ " not affect the appservices config as" -#~ " this config is not extensible in " -#~ "current Draupnir anyways. Config extension " -#~ "instead touches the config passed to " -#~ "the Draupnirs that your Appservice " -#~ "creates. So for example below makes " -#~ "all provisioned Draupnirs protect all " -#~ "joined rooms." -#~ msgstr "" - -#~ msgid "" -#~ "You can configure additional options by" -#~ " adding the " -#~ "`matrix_appservice_draupnir_for_all_extension_yaml` variable " -#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" -#~ " file." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Draupnir's " -#~ "`protectAllJoinedRooms` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ 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 0a847ec70..e787fcd57 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 @@ -25,50 +25,27 @@ msgid "Setting up BorgBackup (optional)" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:3 -msgid "" -"The playbook can install and configure " -"[BorgBackup](https://www.borgbackup.org/) (short: Borg) with " -"[borgmatic](https://torsion.org/borgmatic/) for you." +msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:5 -msgid "" -"BorgBackup is a deduplicating backup program with optional compression " -"and encryption. That means your daily incremental backups can be stored " -"in a fraction of the space and is safe whether you store it at home or on" -" a cloud service." +msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:7 -msgid "" -"You will need a remote server where BorgBackup will store the backups. " -"There are hosted, BorgBackup compatible solutions available, such as " -"[BorgBase](https://www.borgbase.com)." +msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:9 -msgid "" -"The backup will run based on `backup_borg_schedule` var (systemd timer " -"calendar), default: 4am every day." +msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:11 -msgid "" -"By default, if you're using the integrated Postgres database server (as " -"opposed to [an external Postgres server](configuring-playbook-external-" -"postgres.md)), backups with BorgBackup will also include dumps of your " -"Postgres database. An alternative solution for backing up the Postgres " -"database is [postgres backup](configuring-playbook-postgres-backup.md). " -"If you decide to go with another solution, you can disable Postgres-" -"backup support for BorgBackup using the `backup_borg_postgresql_enabled` " -"variable." +msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:13 -msgid "" -"**Note**: the component is not managed by this repository but its [own " -"repository](https://github.com/mother-of-all-self-hosting/ansible-role-" -"backup_borg)." +msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:15 @@ -76,10 +53,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:17 -msgid "" -"If you do not disable Postgres-backup support, make sure that the " -"Postgres version of your homeserver's database is compatible with " -"borgmatic." +msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:19 @@ -87,21 +61,15 @@ msgid "Create a new SSH key:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:25 -msgid "" -"This can be done on any machine and you don't need to place the key in " -"the `.ssh` folder. It will be added to the Ansible config later." +msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:27 -msgid "" -"Add the **public** part of this SSH key (the `matrix-borg-backup.pub` " -"file) to your BorgBackup provider/server:" +msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:29 -msgid "" -"If you plan to use a hosted solution, follow their instructions. If you " -"have your own server, copy the key over:" +msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:39 @@ -109,9 +77,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:41 -msgid "" -"Minimal working configuration " -"(`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" +msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:58 @@ -127,50 +93,27 @@ msgid "HOST - SSH host of a provider/server" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:62 -msgid "" -"REPO - BorgBackup repository name, it will be initialized on backup " -"start, eg: `matrix`, regarding Syntax see [Remote " -"repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html" -"#repository-urls)" +msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:63 -msgid "" -"PASSPHRASE - passphrase used for encrypting backups, you may generate it " -"with `pwgen -s 64 1` or use any password manager" +msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:64 -msgid "" -"PRIVATE KEY - the content of the **private** part of the SSH key you " -"created before. The whole key (all of its belonging lines) under " -"`backup_borg_ssh_key_private` needs to be indented with 2 spaces" +msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:66 -msgid "" -"To backup without encryption, add `backup_borg_encryption: 'none'` to " -"your vars. This will also enable the " -"`backup_borg_unknown_unencrypted_repo_access_is_ok` variable." +msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:68 -msgid "" -"`backup_borg_location_source_directories` defines the list of directories" -" to back up: it's set to `{{ matrix_base_data_path }}` by default, which " -"is the base directory for every service's data, such as Synapse, Postgres" -" and the bridges. You might want to exclude certain directories or file " -"patterns from the backup using the " -"`backup_borg_location_exclude_patterns` variable." +msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:70 -msgid "" -"Check the [backup_borg role](https://github.com/mother-of-all-self-" -"hosting/ansible-role-backup_borg)'s " -"[defaults/main.yml](https://github.com/mother-of-all-self-hosting" -"/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full " -"list of available options." +msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:72 @@ -178,25 +121,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:74 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:81 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:83 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:85 @@ -204,12 +137,5 @@ msgid "Manually start a backup" msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:87 -msgid "" -"For testing your setup it can be helpful to not wait until 4am. If you " -"want to run the backup immediately, log onto the server and run " -"`systemctl start matrix-backup-borg`. This will not return until the " -"backup is done, so possibly a long time. Consider using " -"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " -"unstable." +msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po index 9f55db746..efd13268e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po @@ -25,24 +25,15 @@ msgid "Serving the base domain (optional)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:3 -msgid "" -"By default, this playbook sets up services on your Matrix server " -"(`matrix.example.com`), but has it configured so that it presents itself " -"as the base domain (`example.com`). To have this server officially be " -"responsible for Matrix services for the base domain (`example.com`), you " -"need to set up server delegation / redirection." +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:5 -msgid "" -"As we discuss in [Server Delegation](howto-server-delegation.md), server " -"delegation / redirection can be configured in either of these ways:" +msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:7 -msgid "" -"Setting up a `/.well-known/matrix/server` file on the base domain " -"(`example.com`)" +msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:8 @@ -50,15 +41,11 @@ msgid "Setting up a `_matrix._tcp` DNS SRV record" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:10 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:12 -msgid "" -"However, those who don't have a separate server to dedicate to the base " -"domain have trouble arranging this." +msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:14 @@ -66,33 +53,19 @@ msgid "Usually, there are 2 options:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:16 -msgid "" -"either get a separate server for the base domain, just for serving the " -"files necessary for [Server Delegation via a well-known file](howto-" -"server-delegation.md#server-delegation-via-a-well-known-file)" +msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:18 -msgid "" -"or, arrange for the Matrix server to serve the base domain. This either " -"involves you [using your own webserver](configuring-playbook-own-" -"webserver.md) or making the integrated webserver serve the base domain " -"for you." +msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:20 -msgid "" -"This documentation page tells you how to do the latter. With some easy " -"changes, we make it possible to serve the base domain from the Matrix " -"server via the integrated webserver." +msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:22 -msgid "" -"Just [**adjust your DNS records**](configuring-dns.md), so that your base" -" domain is pointed to the Matrix server's IP address (using a DNS `A` " -"record) **and then add the following configuration** to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:28 @@ -100,28 +73,15 @@ msgid "Doing this, the playbook will:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:30 -msgid "" -"obtain an SSL certificate for the base domain, just like it does for all " -"other domains (see [how we handle SSL certificates](configuring-playbook-" -"ssl-certificates.md))" +msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:32 -msgid "" -"serve the `/.well-known/matrix/*` files which are necessary for " -"[Federation Server Discovery](configuring-well-known.md#federation-" -"server-discovery) (also see [Server Delegation](howto-server-" -"delegation.md)) and [Client-Server discovery](configuring-well-known.md" -"#client-server-discovery)" +msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:34 -msgid "" -"serve a simple homepage at `https://example.com` with content `Hello from" -" example.com` (configurable via the " -"`matrix_static_files_file_index_html_template` variable). You can also " -"[serve a more complicated static website](#serving-a-static-website-at-" -"the-base-domain)." +msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:36 @@ -129,33 +89,19 @@ msgid "Serving a static website at the base domain" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:38 -msgid "" -"By default, when \"serving the base domain\" is enabled, the playbook " -"hosts a simple `index.html` webpage at `/matrix/static-" -"files/public/index.html`. The content of this page is taken from the " -"`matrix_static_files_file_index_html_template` variable." +msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:40 -msgid "" -"If you'd like to host your own static website (more than a single " -"`index.html` page) at the base domain, you can disable the creation of " -"this default `index.html` page like this:" +msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:54 -msgid "" -"With this configuration, Ansible will no longer mess around with the " -"`/matrix/static-files/public/index.html` file." +msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:56 -msgid "" -"You are then free to upload any static website files to `/matrix/static-" -"files/public` and they will get served at the base domain. You can do so " -"manually or by using the [ansible-role-aux](https://github.com/mother-of-" -"all-self-hosting/ansible-role-aux) Ansible role, which is part of this " -"playbook already." +msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:58 @@ -163,10 +109,7 @@ msgid "Serving a more complicated website at the base domain" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:60 -msgid "" -"If you'd like to serve an even more complicated (dynamic) website from " -"the Matrix server, relying on the playbook to serve the base domain is " -"not the best choice." +msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice." msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:62 @@ -178,28 +121,19 @@ msgid "**One way is to host your base domain elsewhere**. This involves:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:65 -msgid "" -"you stopping to serve it from the Matrix server: remove " -"`matrix_static_files_container_labels_base_domain_enabled` from your " -"configuration" +msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:66 -msgid "" -"[configuring Matrix Delegation via well-known](./configuring-well-" -"known.md)" +msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:68 -msgid "" -"**Another way is to serve the base domain from another (your own) " -"container on the Matrix server**. This involves:" +msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:69 -msgid "" -"telling the playbook to only serve `example.com/.well-known/matrix` files" -" by adjusting your `vars.yml` configuration like this:" +msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:70 @@ -207,10 +141,7 @@ msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:71 -msgid "" -"add an extra: " -"`matrix_static_files_container_labels_base_domain_traefik_path_prefix: " -"/.well-known/matrix`" +msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:72 @@ -218,23 +149,13 @@ msgid "building and running a new container on the Matrix server:" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:73 -msgid "" -"it should be connected to the `traefik` network, so that Traefik can " -"reverse-proxy to it" +msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:74 -msgid "" -"it should have appropriate [container " -"labels](https://docs.docker.com/config/labels-custom-metadata/), which " -"instruct Traefik to reverse-proxy to it" +msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it" msgstr "" #: ../../../docs/configuring-playbook-base-domain-serving.md:76 -msgid "" -"How you'll be managing building and running this container is up-to-you. " -"You may use of the primitives from [ansible-role-aux](https://github.com" -"/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it" -" yourself, or you can set it up in another way." +msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po index 97e8bacc6..77417d722 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -25,31 +25,15 @@ msgid "Setting up baibot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:8 -msgid "" -"🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a " -"[Matrix](https://matrix.org/) bot developed by " -"[etke.cc](https://etke.cc/) that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you. 🤖" +msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:10 -msgid "" -"It supports [OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other" -" [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:12 -msgid "" -"It's designed as a more private and [✨ " -"featureful](https://github.com/etkecc/baibot/?tab=readme-ov-" -"file#-features) alternative to [matrix-chatgpt-bot](./configuring-" -"playbook-bot-chatgpt.md). See the " -"[baibot](https://github.com/etkecc/baibot) project and its documentation " -"for more information." +msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:14 @@ -57,9 +41,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:16 -msgid "" -"API access to one or more LLM [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." +msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:18 @@ -67,10 +49,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:20 -msgid "" -"There are **a lot of configuration options** (some required, some " -"possibly required, some optional), so they're **split into multiple " -"sections below**:" +msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:23 @@ -90,16 +69,11 @@ msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:27 -msgid "" -"[🤝 Configuring initial default handlers](#-configuring-initial-default-" -"handlers)" +msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:29 -msgid "" -"Depending on your current `vars.yml` file and desired configuration, " -"**you may require more than just the [base configuration](#base-" -"configuration)**." +msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:31 @@ -107,15 +81,11 @@ msgid "Base configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:33 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:71 -msgid "" -"As mentioned above, **this may not be enough**. Continue with the " -"configuration sections below." +msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:73 @@ -128,25 +98,16 @@ msgid "This is an addition to the [base configuration](#base-configuration)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:77 -msgid "" -"To specify who is considered a bot [👮‍♂️ " -"Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators)," -" you either need to specify " -"`matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The " -"latter is a single variable which affects all bridges and bots." +msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:79 -msgid "" -"If `matrix_admin` is already configured in your `vars.yml` configuration," -" you can skip this section." +msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:81 #: ../../../docs/configuring-playbook-bot-baibot.md:110 -msgid "" -"**If necessary**, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:95 @@ -154,44 +115,27 @@ msgid "👥 Initial users configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:97 -msgid "" -"By default, **all users on your homeserver are considered allowed " -"users**. If that's OK, you can skip this section." +msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:101 -msgid "" -"To specify who is considered a bot [👥 " -"User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), " -"you may:" +msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:103 -msgid "" -"define an **initial** value for " -"`matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible " -"variable, as shown below" +msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:104 -msgid "" -"configure the list at runtime via the bot's `!bai access set-users " -"SPACE_SEPARATED_PATTERNS` command" +msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:106 -msgid "" -"Configuring " -"`matrix_bot_baibot_config_initial_global_config_user_patterns` is " -"optional, but it can be useful to pre-configure the bot with a list of " -"users who should have access to the bot's features." +msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:108 -msgid "" -"**Note**: Once initially configured, the allowed users list **cannot be " -"managed via Ansible anymore**. It can only be managed subsequently via " -"bot commands." +msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:122 @@ -199,61 +143,31 @@ msgid "🤖 Configuring agents via Ansible" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:124 -msgid "" -"You are **not required** to define agents " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration) via Ansible. **To get started quickly**, you can " -"**skip this section and define agents at runtime via chat commands** " -"(following the bot's guidance)." +msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:126 -msgid "" -"Privileged users (like the [👮‍♂️ Administrator](#️-administrator-" -"configuration), but potentially others too - see the upstream [🔒 " -"access](https://github.com/etkecc/baibot/blob/main/docs/access.md) " -"documentation) can **define agents dynamically at any time** via chat " -"commands." +msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:128 -msgid "" -"The Ansible role includes preset variables for easily enabling some [🤖 " -"agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on " -"various [☁️ " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " -"(e.g. OpenAI, etc)." +msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:130 -msgid "" -"Besides the presets, the Ansible role also includes support for " -"configuring additional statically-defined agents via the " -"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " -"variable." +msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:132 -msgid "" -"Agents defined statically and those created dynamically (via chat) are " -"named differently, so **conflict cannot arise**." +msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:134 -msgid "" -"Depending on your propensity for " -"[GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to " -"define agents statically via Ansible, or you may wish to do it " -"dynamically via chat." +msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:136 -msgid "" -"Before proceeding, we recommend reading the upstream documentation on " -"[How to choose a " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#how-to-choose-a-provider). In short, it's probably best to go with " -"[OpenAI](#openai)." +msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:138 @@ -261,12 +175,7 @@ msgid "Anthropic" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:140 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [Anthropic " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:142 @@ -280,19 +189,14 @@ msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:193 #: ../../../docs/configuring-playbook-bot-baibot.md:221 #: ../../../docs/configuring-playbook-bot-baibot.md:251 -msgid "" -"If you'd like to use more than one model, take a look at the [Configuring" -" additional agents (without a preset)](#configuring-additional-agents-" -"without-a-preset) section below." +msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:162 #: ../../../docs/configuring-playbook-bot-baibot.md:195 #: ../../../docs/configuring-playbook-bot-baibot.md:223 #: ../../../docs/configuring-playbook-bot-baibot.md:253 -msgid "" -"💡 You may also wish to use this new agent for [🤝 Configuring initial " -"default handlers](#-configuring-initial-default-handlers)." +msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:164 @@ -300,20 +204,11 @@ msgid "Groq" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:166 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [Groq " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:191 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/groq`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:197 @@ -321,20 +216,11 @@ msgid "Mistral" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:199 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [🇫🇷 Mistral " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:219 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/mistral`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:225 @@ -342,29 +228,15 @@ msgid "OpenAI" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:227 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [OpenAI " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai)" -" with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:229 -msgid "" -"The OpenAI provider is **only meant to be used with OpenAI's official " -"API** and compatibility with other services (which do not fully adhere to" -" the OpenAI API spec completely) is limited. **If you're targeting an " -"OpenAI-compatible service**, use the [OpenAI Compatible](#openai-" -"compatible) provider instead." +msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:249 -msgid "" -"Because this is a " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agent, it will be given a `static/` ID " -"prefix and will be named `static/openai`." +msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:255 @@ -372,37 +244,19 @@ msgid "OpenAI Compatible" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:257 -msgid "" -"You can statically-define a single [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) " -"instance powered by the [OpenAI Compatible " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#openai-compatible) with the help of the playbook's preset variables." +msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:259 -msgid "" -"This provider allows you to use OpenAI-compatible API services like " -"[OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter)," -" [Together " -"AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#together-ai), etc." +msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:261 -msgid "" -"Some of these popular services already have **shortcut** providers (see " -"[supported " -"providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md" -"#supported-providers) leading to this one behind the scenes - this make " -"it easier to get started." +msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:263 -msgid "" -"As of this moment, the playbook does not include presets for any of these" -" services, so you'll need to [Configuring additional agents (without a " -"preset)](#configuring-additional-agents-without-a-preset)." +msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:265 @@ -410,63 +264,35 @@ msgid "Configuring additional agents (without a preset)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:267 -msgid "" -"The Ansible role may be lacking preset variables for some [☁️ " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), " -"or you may wish to statically-define an agent on the same provider twice " -"(or more) with different configuration." +msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:269 -msgid "" -"It's possible to inject your own agent configuration using the " -"`matrix_bot_baibot_config_agents_static_definitions_custom` Ansible " -"variable." +msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:271 -msgid "" -"You can also define providers at runtime, by chatting with the bot, so " -"using Ansible is not a requirement." +msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:273 -msgid "" -"Below is an an **example** demonstrating **statically-defining agents via" -" Ansible without using presets**:" +msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:312 -msgid "" -"Because these are " -"[statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md" -"#static-configuration)-defined agents, they will be given a `static/` ID " -"prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and " -"`static/my-ollama-agent`, respectively." +msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:314 -msgid "" -"💡 To figure out what to put in the `config` section, refer to the [☁️ " -"provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) " -"page, which contains **sample configuration YAML for each provider**." +msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:316 -msgid "" -"As with any [🤖 " -"agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), " -"defining them means they exist. To actually make use of them, they need " -"to be configured as handlers globally or in a specific room - see [Mixing" -" & matching " -"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" -"--matching-models)." +msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:318 -msgid "" -"💡 You may also wish to use these new agents for [🤝 Configuring initial " -"default handlers](#-configuring-initial-default-handlers)." +msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:320 @@ -474,11 +300,7 @@ msgid "🤝 Configuring initial default handlers" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:322 -msgid "" -"This section is only useful if you're [🤖 Configuring agents via Ansible" -"](#-configuring-agents-via-ansible), as it lets you put these agents to " -"use as soon as the bot starts (by adjusting the bot's **initial global " -"configuration**)." +msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:324 @@ -486,75 +308,43 @@ msgid "If you're not configuring agents via Ansible, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:326 -msgid "" -"This section is only useful the first time around. **Once initially " -"configured the global configuration cannot be managed Ansible**, but only" -" via bot commands." +msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:328 -msgid "" -"baibot supports [various " -"purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" +msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:330 -msgid "" -"[💬 text-" -"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-text-generation): communicating with you via text" +msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:332 -msgid "" -"[🦻 speech-to-" -"text](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-speech-to-text): turning your voice messages into text" +msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:334 -msgid "" -"[🗣️ text-to-" -"speech](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-text-to-speech): turning bot or users text messages into voice messages" +msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:336 -msgid "" -"[🖌️ image-" -"generation](https://github.com/etkecc/baibot/blob/main/docs/features.md" -"#-image-generation): generating images based on instructions" +msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:338 -msgid "" -"❓ catch-all: special purposes, indicating use as a fallback (when no " -"specific handler is configured)" +msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:340 -msgid "" -"[Mixing & matching " -"models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing" -"--matching-models) is made possible by the bot's ability to have " -"different [🤝 " -"handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md)" -" configured for different purposes." +msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:342 -msgid "" -"This configuration can be done as a global fallback, or per-room. Both of" -" these [🛠️ " -"configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md)" -" are managed at runtime (viat chat), but **the global configuration can " -"have some initial defaults configured via Ansible**." +msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:344 -msgid "" -"You can configure the **initial values** for these via Ansible, via the " -"`matrix_bot_baibot_config_initial_global_config_handler_*` variables." +msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:346 @@ -562,11 +352,7 @@ msgid "Example **additional** `vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:363 -msgid "" -"**Note**: these are initial defaults for the bot's global configuration. " -"As such, changing any of these values subsequently has no effect on the " -"bot's behavior. **Once initially configured the global configuration " -"cannot be managed Ansible**, but only via bot commands." +msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:365 @@ -574,9 +360,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:367 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:374 @@ -584,35 +368,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:376 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:378 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:380 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:382 -msgid "" -"If you change the bot password (`matrix_bot_baibot_config_user_password` " -"in your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_baibot_config_user_password` to let the bot know its new " -"password." +msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:384 @@ -624,40 +392,23 @@ msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:388 -msgid "" -"If you're an allowed bot [👥 " -"user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) " -"(see [👥 Initial users configuration](#-initial-users-configuration)), the" -" bot will accept your invitation and join the room." +msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:390 -msgid "" -"After joining, the bot will introduce itself and show information about " -"the [✨ " -"features](https://github.com/etkecc/baibot/blob/main/docs/features.md) " -"that are enabled for it." +msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:392 -msgid "" -"If you've [🤖 configured one or more agents via Ansible](#-configuring-" -"agents-via-ansible) and have [🤝 configured initial default handlers" -"](#configuring-initial-default-handlers), the bot will immediately be " -"able to make use of these agents for this new room. Otherwise, you will " -"need to configure agents and/or handlers via chat commands." +msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:394 -msgid "" -"Send `!bai help` to the room at any time to see the bot's help menu for " -"additional commands." +msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:396 -msgid "" -"You can also refer to the upstream " -"[baibot](https://github.com/etkecc/baibot) project's documentation." +msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:398 @@ -665,23 +416,13 @@ msgid "Debugging" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:400 -msgid "" -"As with all other services, you can find service logs in [systemd-" -"journald](https://www.freedesktop.org/software/systemd/man/systemd-" -"journald.service.html) by running something like `journalctl -fu matrix-" -"bot-baibot`" +msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:402 -msgid "" -"The default logging level for this service is `info`, but you can " -"increase it to `debug` (or even `trace`) with the following additional " -"configuration:" +msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:416 -msgid "" -"**Alternatively**, you can use a single variable to set the logging level" -" for all of the above (bot + all libraries):" +msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po index f919880a6..2dd8ab917 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -25,15 +25,11 @@ msgid "Setting up Buscarron (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:3 -msgid "" -"The playbook can install and configure " -"[Buscarron](https://github.com/etkecc/buscarron) for you." +msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:5 -msgid "" -"Buscarron is bot that receives HTTP POST submissions of web forms and " -"forwards them to a Matrix room." +msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:7 @@ -41,9 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:9 -msgid "" -"To enable Buscarron, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:32 @@ -51,24 +45,15 @@ msgid "Adjusting the Buscarron URL" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:34 -msgid "" -"By default, this playbook installs Buscarron on the `buscarron.` " -"subdomain (`buscarron.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:36 -msgid "" -"By tweaking the `matrix_bot_buscarron_hostname` and " -"`matrix_bot_buscarron_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:38 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:49 @@ -76,21 +61,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:51 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Buscarron domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:53 -msgid "" -"By default, you will need to create a CNAME record for `buscarron`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:55 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:57 @@ -98,10 +77,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:59 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:66 @@ -109,34 +85,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:68 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:70 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:72 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:74 -msgid "" -"If you change the bot password (`matrix_bot_buscarron_password` in your " -"`vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_buscarron_password` to let the bot know its new password." +msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:76 @@ -144,16 +105,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:78 -msgid "" -"To use the bot, invite the `@bot.buscarron:example.com` to the room you " -"specified in a config, after that any point your form to the form url, " -"example for the `contact` form:" +msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:86 -msgid "" -"**Note**: to fight against spam, Buscarron is **very aggressive when it " -"comes to banning** and will ban you if:" +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:88 @@ -161,27 +117,17 @@ msgid "if you hit the homepage (HTTP `GET` request to `/`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:89 -msgid "" -"if you submit a form to the wrong URL (`POST` request to `/non-existing-" -"form`)" +msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:90 -msgid "" -"if `hasemail` is enabled for the form (like in the example above) and you" -" don't submit an `email` field" +msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:92 -msgid "" -"If you get banned, you'd need to restart the process by running the " -"playbook with `--tags=start` or running `systemctl restart matrix-bot-" -"buscarron` on the server." +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:94 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/buscarron)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index 121e56131..3214d2062 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 @@ -25,25 +25,15 @@ 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." +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." +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!" +msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:9 @@ -51,9 +41,7 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires an access token to be able to connect to your homeserver." +msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 @@ -61,9 +49,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:15 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 @@ -75,18 +61,11 @@ msgid "Get an access token and create encryption keys" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:25 -msgid "" -"Refer to the documentation on [how to obtain an access token](obtaining-" -"access-tokens.md)." +msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:27 -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)." +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:29 @@ -94,10 +73,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:31 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:52 @@ -109,9 +85,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:56 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:63 @@ -119,24 +93,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:65 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:67 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:69 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:71 @@ -144,15 +109,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:73 -msgid "" -"To use the bot, invite the `@bot.chatgpt:example.com` to the room you " -"specified in a config, after that start speaking to it, use the prefix if" -" you configured one or mention the bot." +msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:75 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." +msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index 0e3677f70..5fad573c4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -25,30 +25,19 @@ msgid "Setting up Draupnir (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:3 -msgid "" -"The playbook can install and configure the [Draupnir](https://github.com" -"/the-draupnir-project/Draupnir) moderation bot for you." +msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:5 -msgid "" -"See the project's [documentation](https://github.com/the-draupnir-" -"project/Draupnir/blob/main/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:7 -msgid "" -"This documentation page is about installing Draupnir in bot mode. As an " -"alternative, you can run a multi-instance Draupnir deployment by " -"installing [Draupnir in appservice mode](./configuring-playbook-" -"appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." +msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:9 -msgid "" -"If your migrating from Mjolnir skip to [this section](#migrating-from-" -"mjolnir-only-required-if-migrating)." +msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:11 @@ -60,15 +49,11 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:15 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 @@ -76,11 +61,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 -msgid "" -"If you would like Draupnir to be able to deactivate users, move aliases, " -"shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc " -"then it must be a server admin so you need to change `admin=no` to " -"`admin=yes` in the command above." +msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 @@ -88,10 +69,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 @@ -99,59 +77,31 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "" -"If your homeserver's implementation is Synapse, you will need to prevent " -"it from rate limiting the bot's account. **This is a required step. If " -"you do not configure it, Draupnir will crash.**" +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "" -"This can be done using Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). They can be accessed both externally and " -"internally." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 -msgid "" -"To expose the APIs publicly, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:43 -msgid "" -"The APIs can also be accessed via [Synapse " -"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " -"use to administrate users, rooms, media, etc. on your Matrix server. The " -"playbook can install and configure Synapse Admin for you. For details " -"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:45 -msgid "" -"**Note**: access to the APIs is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, " -"doing so is not recommended for additional security. See [official " -"Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints)." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:47 -msgid "" -"To discharge rate limiting, run the following command on systems that " -"ship curl (note that it does not work on outdated Windows 10). Even if " -"the APIs are not exposed to the internet, you should still be able to run" -" the command on the homeserver locally. Before running it, make sure to " -"replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:53 -msgid "" -"You can obtain an access token for a homeserver admin account in the same" -" way as you can do so for Draupnir itself. If you have made Draupnir an " -"admin, you can just use the Draupnir token." +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:55 @@ -159,32 +109,19 @@ msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:57 -msgid "" -"Using your own account, create a new invite only room that you will use " -"to manage the bot. This is the room where you will see the status of the " -"bot and where you will send commands to the bot, such as the command to " -"ban a user from another room. Anyone in this room can control the bot so " -"it is important that you only invite trusted users to this room." +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:59 -msgid "" -"If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:61 -msgid "" -"Once you have created the room you need to copy the room ID so you can " -"tell the bot to use that room. In Element Web you can do this by going to" -" the room's settings, clicking Advanced, and then copying the internal " -"room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:63 -msgid "" -"Finally invite the `@bot.draupnir:example.com` account you created " -"earlier into the room." +msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:65 @@ -192,10 +129,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:67 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:76 @@ -203,16 +137,11 @@ msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:78 -msgid "" -"Decide whether you want Draupnir to be capable of operating in end-to-end" -" encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms." +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:80 -msgid "" -"To support E2EE, Draupnir needs to [use Pantalaimon](configuring-" -"playbook-pantalaimon.md)." +msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:82 @@ -220,25 +149,15 @@ msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:84 -msgid "" -"When using Pantalaimon, Draupnir will log in to its bot account itself " -"through Pantalaimon, so configure its username and password." +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:86 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:100 -msgid "" -"The playbook's `group_vars` will configure other required settings. If " -"using this role separately without the playbook, you also need to " -"configure the two URLs that Draupnir uses to reach the homeserver, one " -"through Pantalaimon and one \"raw\". This example is taken from the " -"playbook's `group_vars`:" +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:112 @@ -246,17 +165,11 @@ msgid "Configuration without E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:114 -msgid "" -"When NOT using Pantalaimon, Draupnir does not log in by itself and you " -"must give it an access token for its bot account." +msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:116 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:122 @@ -268,19 +181,11 @@ msgid "Draupnir supports two methods to receive reports in the management room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:126 -msgid "" -"The first method intercepts the report API endpoint of the client-server " -"API, which requires integration with the reverse proxy in front of the " -"homeserver. If you are using traefik, this playbook can set this up for " -"you:" +msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:132 -msgid "" -"The other method polls an Synapse Admin API endpoint, hence it is " -"available only if using Synapse and if the Draupnir user is an admin (see" -" [above](#register-the-bot-account)). To enable it, set `pollReports: " -"true` on `vars.yml` file as below." +msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:134 @@ -288,16 +193,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:136 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_draupnir_configuration_extension_yaml` variable." +msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:138 -msgid "" -"For example, to change Draupnir's `pollReports` option to `true`, add the" -" following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:152 @@ -305,15 +205,11 @@ msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:154 -msgid "" -"Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` " -"config. Also disable Mjolnir if you're doing migration." +msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:156 -msgid "" -"That is all you need to do due to that Draupnir can complete migration on" -" its own." +msgid "That is all you need to do due to that Draupnir can complete migration on its own." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:158 @@ -321,9 +217,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:160 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:167 @@ -331,35 +225,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:169 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:171 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:173 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:175 -msgid "" -"If you change the Pantalaimon's password " -"(`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) " -"subsequently, its credentials on the homeserver won't be updated " -"automatically. If you'd like to change the password, use a tool like " -"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " -"then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon" -" know its new password." +msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:177 @@ -367,10 +245,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:179 -msgid "" -"You can refer to the upstream [documentation](https://the-draupnir-" -"project.github.io/draupnir-documentation/) for additional ways to use and" -" configure Draupnir and for a more detailed usage guide." +msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:181 @@ -382,41 +257,23 @@ msgid "Making Draupnir join and protect a room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:185 -msgid "" -"Draupnir can be told to self-join public rooms, but it's better to follow" -" this flow which works well for all kinds of rooms:" +msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:187 -msgid "" -"Invite the bot to the room manually ([inviting Draupnir to rooms](https" -"://the-draupnir-project.github.io/draupnir-documentation/moderator" -"/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, " -"the bot *may* ask for confirmation in the Management Room" +msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:189 -msgid "" -"[Give the bot permissions to do its job](#giving-draupnir-permissions-to-" -"do-its-job)" +msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:191 -msgid "" -"Tell it to protect the room (using the [rooms command](https://the-" -"draupnir-project.github.io/draupnir-documentation/moderator/managing-" -"protected-rooms#using-the-draupnir-rooms-command)) by sending the " -"following command to the Management Room: `!draupnir rooms add " -"!qporfwt:example.com`" +msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:193 -msgid "" -"To have Draupnir provide useful room protection, you need do to a bit " -"more work (at least the first time around). You may wish to [Subscribe to" -" a public policy list](#subscribing-to-a-public-policy-list), [Create " -"your own own policy and rules](#creating-your-own-policy-lists-and-rules)" -" and [Enabling built-in protections](#enabling-built-in-protections)." +msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:195 @@ -424,20 +281,11 @@ msgid "Giving Draupnir permissions to do its job" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:197 -msgid "" -"For Draupnir to do its job, you need to [give it permissions](https" -"://the-draupnir-project.github.io/draupnir-documentation/moderator" -"/managing-protected-rooms#giving-draupnir-permissions) in rooms it's " -"protecting. This involves **giving it an Administrator power level**." +msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:199 -msgid "" -"**We recommend setting this power level as soon as the bot joins your " -"room** (and before you create new rules), so that it can apply rules as " -"soon as they are available. If the bot is under-privileged, it may fail " -"to apply protections and may not retry for a while (or until your restart" -" it)." +msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:201 @@ -445,25 +293,15 @@ msgid "Subscribing to a public policy list" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:203 -msgid "" -"We recommend **subscribing to a public [policy list](https://the-" -"draupnir-project.github.io/draupnir-documentation/concepts/policy-" -"lists)** using the [watch command](https://the-draupnir-project.github.io" -"/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-" -"watch-command-to-subscribe-to-policy-rooms)." +msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:205 -msgid "" -"Polcy lists are maintained in Matrix rooms. A popular policy list is " -"maintained in the public `#community-moderation-effort-bl:neko.dev` room." +msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:207 -msgid "" -"You can tell Draupnir to subscribe to it by sending the following command" -" to the Management Room: `!draupnir watch #community-moderation-effort-" -"bl:neko.dev`" +msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:209 @@ -471,59 +309,31 @@ msgid "Creating your own policy lists and rules" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:211 -msgid "" -"We also recommend **creating your own policy lists** with the [list " -"create](https://the-draupnir-project.github.io/draupnir-" -"documentation/moderator/managing-policy-lists#using-draupnirs-list-" -"create-command-to-create-a-policy-room) command." +msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:213 -msgid "" -"You can do so by sending the following command to the Management Room: " -"`!draupnir list create my-bans my-bans-bl`. This will create a policy " -"list having a name (shortcode) of `my-bans` and stored in a public `#my-" -"bans-bl:example.com` room on your server. As soon as you run this " -"command, the bot will invite you to the policy list room." +msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:215 -msgid "" -"A policy list does nothing by itself, so the next step is **adding some " -"rules to your policy list**. Policies target a so-called `entity` (one " -"of: `user`, `room` or `server`). These entities are mentioned on the " -"[policy lists](https://the-draupnir-project.github.io/draupnir-" -"documentation/concepts/policy-lists) documentation page and in the Matrix" -" Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-" -"recommendation)." +msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:217 -msgid "" -"The simplest and most useful entity to target is `user`. Below are a few " -"examples using the [ban command](https://the-draupnir-project.github.io" -"/draupnir-documentation/moderator/managing-users#the-ban-command) and " -"targeting users." +msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:219 -msgid "" -"To create rules, you run commands in the Management Room (**not** in the " -"policy list room)." +msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:221 -msgid "" -"(ban a single user on a given homeserver): `!draupnir ban " -"@charles:example.com my-bans Rude to others`" +msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:222 -msgid "" -"(ban all users on a given homeserver by using a [wildcard](https://the-" -"draupnir-project.github.io/draupnir-documentation/moderator/managing-" -"users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - " -"all users are fake`" +msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:224 @@ -531,22 +341,15 @@ msgid "As a result of running these commands, you may observe:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:226 -msgid "" -"Draupnir creating `m.policy.rule.user` state events in the `#my-bans-" -"bl:example.com` room on your server" +msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:227 -msgid "" -"applying these rules against all rooms that Draupnir is an Administrator " -"in" +msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:229 -msgid "" -"You can undo bans with the [unban command](https://the-draupnir-" -"project.github.io/draupnir-documentation/moderator/managing-users#the-" -"unban-command)." +msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:231 @@ -554,186 +357,25 @@ msgid "Enabling built-in protections" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:233 -msgid "" -"You can also **turn on various built-in [protections](https://the-" -"draupnir-project.github.io/draupnir-documentation/protections)** like " -"`JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the " -"room to invite-only\")." +msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:235 -msgid "" -"To **see which protections are available and which are enabled**, send a " -"`!draupnir protections` command to the Management Room." +msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:237 -msgid "" -"To **see the configuration options for a given protection**, send a " -"`!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get " -"JoinWaveShortCircuit`)." +msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:239 -msgid "" -"To **set a specific option for a given protection**, send a command like " -"this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. " -"`!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." +msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:241 -msgid "" -"To **enable a given protection**, send a command like this: `!draupnir " -"enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." +msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:243 -msgid "" -"To **disable a given protection**, send a command like this: `!draupnir " -"disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." +msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/the-draupnir-project/Draupnir) to learn " -#~ "what it does and why it might " -#~ "be useful to you." -#~ msgstr "" - -#~ msgid "If your migrating from Mjolnir skip to step 5b." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not automatically " -#~ "create users for you. The bot " -#~ "requires an access token to be " -#~ "able to connect to your homeserver." -#~ msgstr "" - -#~ msgid "" -#~ "You **need to register the bot " -#~ "user manually** before setting up the" -#~ " bot." -#~ msgstr "" - -#~ msgid "" -#~ "If you would like Draupnir to be" -#~ " able to deactivate users, move " -#~ "aliases, shutdown rooms, show abuse " -#~ "reports ([see below](#abuse-reports)), etc " -#~ "then it must be a server admin " -#~ "so you need to change `admin=no` " -#~ "to `admin=yes` in the command above." -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the documentation on [how " -#~ "to obtain an access token](obtaining-" -#~ "access-tokens.md)." -#~ msgstr "" - -#~ msgid "" -#~ "You will need to prevent Synapse " -#~ "from rate limiting the bot's account." -#~ " This is not an optional step. " -#~ "If you do not do this step " -#~ "Draupnir will crash. This can be " -#~ "done using Synapse's [admin API](https" -#~ "://matrix-" -#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" -#~ "#override-ratelimiting-for-users). Please " -#~ "ask for help if you are " -#~ "uncomfortable with these steps or run" -#~ " into issues." -#~ msgstr "" - -#~ msgid "" -#~ "If your Synapse Admin API is " -#~ "exposed to the internet for some " -#~ "reason like running the Synapse Admin" -#~ " Role [Link](configuring-playbook-synapse-" -#~ "admin.md) or running " -#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -#~ " true` in your playbook config. If" -#~ " your API is not externally exposed" -#~ " you should still be able to on" -#~ " the local host for your synapse " -#~ "run these commands." -#~ msgstr "" - -#~ msgid "" -#~ "The following command works on semi " -#~ "up to date Windows 10 installs and" -#~ " All Windows 11 installations and " -#~ "other systems that ship curl. `curl " -#~ "--header \"Authorization: Bearer \"" -#~ " -X POST " -#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit`" -#~ " Replace `@bot.draupnir:example.com` with the " -#~ "MXID of your Draupnir and example.com" -#~ " with your homeserver domain. You can" -#~ " easily obtain an access token for" -#~ " a homeserver admin account the same" -#~ " way you can obtain an access " -#~ "token for Draupnir itself. If you " -#~ "made Draupnir Admin you can just " -#~ "use the Draupnir token." -#~ msgstr "" - -#~ msgid "" -#~ "If you make the management room " -#~ "encrypted (E2EE), then you MUST enable" -#~ " and use Pantalaimon (see below)." -#~ msgstr "" - -#~ msgid "" -#~ "Decide whether you want Draupnir to " -#~ "be capable of operating in end-" -#~ "to-end encrypted (E2EE) rooms. This " -#~ "includes the management room and the " -#~ "moderated rooms. To support E2EE, " -#~ "Draupnir needs to [use Pantalaimon" -#~ "](configuring-playbook-pantalaimon.md)." -#~ msgstr "" - -#~ msgid "a. Configuration with E2EE support" -#~ msgstr "" - -#~ msgid "b. Configuration without E2EE support" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace " -#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " -#~ "values." -#~ msgstr "" - -#~ msgid "c. Migrating from Mjolnir (Only required if migrating.)" -#~ msgstr "" - -#~ msgid "" -#~ "You can configure additional options by" -#~ " adding the " -#~ "`matrix_bot_draupnir_configuration_extension_yaml` variable " -#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`" -#~ " file." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Draupnir's " -#~ "`recordIgnoredInvites` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ msgstr "" - -#~ msgid "" -#~ "The other method polls an synapse " -#~ "admin API endpoint and is hence " -#~ "only available when using synapse and" -#~ " when the Draupnir user is an " -#~ "admin user (see step 1). To enable" -#~ " it, set `pollReports: true` in " -#~ "Draupnir's config:" -#~ 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 8dbd4665d..fda8f1717 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 @@ -25,33 +25,19 @@ msgid "Setting up Go-NEB (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:3 -msgid "" -"**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an " -"archived (**unmaintained**) project. We recommend not bothering with " -"installing it. While not a 1:1 replacement, the bridge's author suggests " -"taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) as a replacement, which can also be installed using [this " -"playbook](configuring-playbook-bridge-hookshot.md). Consider using that " -"bot instead of this one." +msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:5 -msgid "" -"The playbook can install and configure [Go-NEB](https://github.com" -"/matrix-org/go-neb) for you." +msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:7 -msgid "" -"Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, " -"the original Matrix bot written in Python." +msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:9 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/go-" -"neb/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 @@ -59,10 +45,7 @@ msgid "Registering the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "" -"The playbook does not automatically create users for you. The bot " -"requires at least 1 access token to be able to connect to your " -"homeserver." +msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:15 @@ -70,9 +53,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:19 @@ -80,9 +61,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:25 -msgid "" -"Once the user is created you can [obtain an access token](obtaining-" -"access-tokens.md)." +msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:27 @@ -90,9 +69,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "" -"To enable Go-NEB, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:193 @@ -100,24 +77,15 @@ msgid "Adjusting the Go-NEB URL" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:195 -msgid "" -"By default, this playbook installs Go-NEB on the `goneb.` subdomain " -"(`goneb.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:197 -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." +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:199 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:210 @@ -125,21 +93,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:212 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Go-NEB domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:214 -msgid "" -"By default, you will need to create a CNAME record for `goneb`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:216 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +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:218 @@ -147,10 +109,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:220 -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 "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:227 @@ -158,24 +117,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:229 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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:231 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:233 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:235 @@ -183,35 +133,17 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:237 -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." +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:239 -msgid "" -"Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy " -"matrix`" +msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:241 -msgid "" -"If you enabled the github_cmd service you can get the supported commands " -"via `!github help`" +msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:243 -msgid "" -"You can also refer to the upstream [Documentation](https://github.com" -"/matrix-org/go-neb)." +msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/go-neb) to learn what it" -#~ " does and why it might be " -#~ "useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index e551070dc..e996cc5a3 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -25,9 +25,7 @@ msgid "Setting up Honoroit (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:3 -msgid "" -"The playbook can install and configure " -"[Honoroit](https://github.com/etkecc/honoroit) for you." +msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:5 @@ -35,10 +33,7 @@ msgid "It's a bot you can use to setup **your own helpdesk on matrix**" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/etkecc/honoroit/blob/main/README.md) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:9 @@ -46,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:11 -msgid "" -"To enable Honoroit, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:26 @@ -56,25 +49,15 @@ msgid "Adjusting the Honoroit URL" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:28 -msgid "" -"By default, this playbook installs Honoroit on the `matrix.` subdomain, " -"at the `/honoroit` path (https://matrix.example.com/honoroit). This makes" -" it easy to install it, because it **doesn't require additional DNS " -"records to be set up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:30 -msgid "" -"By tweaking the `matrix_bot_honoroit_hostname` and " -"`matrix_bot_honoroit_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:32 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:40 @@ -82,9 +65,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:42 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Honoroit domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:44 @@ -92,9 +73,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:46 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:48 @@ -102,10 +81,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:50 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:57 @@ -113,34 +89,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:59 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:65 -msgid "" -"If you change the bot password (`matrix_bot_honoroit_password` in your " -"`vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_honoroit_password` to let the bot know its new password." +msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:67 @@ -148,29 +109,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:69 -msgid "" -"To use the bot, invite the `@honoroit:example.com` to the room you " -"specified in config, after that any Matrix user can send a message to the" -" `@honoroit:example.com` to start a new thread in that room." +msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "" -"Send `!ho help` to the room to see the bot's help menu for additional " -"commands." +msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/honoroit#features)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/etkecc/honoroit#how-it-" -#~ "looks-like) to learn what it does " -#~ "with screenshots and why it might " -#~ "be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index fb61172cc..d5efd5bbc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -25,26 +25,15 @@ msgid "Setting up matrix-registration-bot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3 -msgid "" -"The playbook can install and configure [matrix-registration-" -"bot](https://github.com/moan0s/matrix-registration-bot) for you." +msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5 -msgid "" -"The bot allows you to easily **create and manage registration tokens** " -"aka. invitation codes. It can be used for an invitation-based server, " -"where you invite someone by sending them a registration token (tokens " -"look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but " -"have to provide a valid registration token in the final step of the " -"registration process." +msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7 -msgid "" -"See the project's [documentation](https://github.com/moan0s/matrix-" -"registration-bot/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 @@ -52,9 +41,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 -msgid "" -"To enable the bot, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30 @@ -66,9 +53,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41 @@ -76,36 +61,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49 -msgid "" -"If you change the bot password " -"(`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` " -"file) subsequently, the bot user's credentials on the homeserver won't be" -" updated automatically. If you'd like to change the bot user's password, " -"use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to" -" change it, and then update " -"`matrix_bot_matrix_registration_bot_bot_password` to let the bot know its" -" new password." +msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51 @@ -113,10 +81,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53 -msgid "" -"To use the bot, start a chat with `@bot.matrix-registration-" -"bot:example.com` (where `example.com` is your base domain, not the " -"`matrix.` domain)." +msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 @@ -124,32 +89,13 @@ msgid "In this room send `help` and the bot will reply with all options." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 -msgid "" -"You can also refer to the upstream [Usage " -"documentation](https://github.com/moan0s/matrix-registration-bot" -"#supported-commands)." +msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59 -msgid "" -"If you have any questions, or if you need help setting it up, read the " -"[troublshooting guide](https://github.com/moan0s/matrix-registration-" -"bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-" -"bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." +msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61 -msgid "" -"To clean the cache (session & encryption data) after you changed the " -"bot's username, changed the login method from access_token to password " -"etc… you can use:" +msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/moan0s/matrix-" -#~ "registration-bot#supported-commands) to learn " -#~ "what it does and why it might " -#~ "be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index 5148da31a..d6abfb68d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -25,22 +25,15 @@ msgid "Setting up matrix-reminder-bot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3 -msgid "" -"The playbook can install and configure [matrix-reminder-" -"bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." +msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5 -msgid "" -"It's a bot you can use to **schedule one-off & recurring reminders and " -"alarms**." +msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7 -msgid "" -"See the project's [documentation](https://github.com/anoadragon453" -"/matrix-reminder-bot/blob/master/README.md) to learn what it does and why" -" it might be useful to you." +msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9 @@ -48,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 @@ -58,9 +49,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35 @@ -68,36 +57,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43 -msgid "" -"If you change the bot password " -"(`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml`" -" file) subsequently, the bot user's credentials on the homeserver won't " -"be updated automatically. If you'd like to change the bot user's " -"password, use a tool like [synapse-admin](configuring-playbook-synapse-" -"admin.md) to change it, and then update " -"`matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know" -" its new password." +msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45 @@ -105,15 +77,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47 -msgid "" -"To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49 -msgid "" -"You can also add the bot to any existing Matrix room (`/invite @bot" -".matrix-reminder-bot:example.com`)." +msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51 @@ -121,23 +89,9 @@ msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53 -msgid "" -"Send `!help reminders` to the room to see the bot's help menu for " -"additional commands." +msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55 -msgid "" -"You can also refer to the upstream [Usage " -"documentation](https://github.com/anoadragon453/matrix-reminder-" -"bot#usage)." +msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/anoadragon453/matrix-" -#~ "reminder-bot#usage) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po index c47d65373..b2e8d722c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -25,23 +25,15 @@ msgid "Setting up maubot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:3 -msgid "" -"The playbook can install and configure " -"[maubot](https://github.com/maubot/maubot) for you." +msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:5 -msgid "" -"After setting up maubot, you can use the web management interface to make" -" it do things. The default location of the management interface is " -"`matrix.example.com/_matrix/maubot/`" +msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn " -"what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:9 @@ -49,15 +41,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:11 -msgid "" -"To enable maubot, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:26 -msgid "" -"You can add multiple admins. The admin accounts are only used to access " -"the maubot administration interface." +msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:28 @@ -65,26 +53,15 @@ msgid "Adjusting the maubot URL" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:30 -msgid "" -"By default, this playbook installs maubot on the `matrix.` subdomain, at " -"the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/)." -" This makes it easy to install it, because it **doesn't require " -"additional DNS records to be set up**. If that's okay, you can skip this " -"section." +msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:32 -msgid "" -"By tweaking the `matrix_bot_maubot_hostname` and " -"`matrix_bot_maubot_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:42 @@ -92,9 +69,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:44 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the maubot domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:46 @@ -102,9 +77,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:48 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:50 @@ -112,10 +85,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.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:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:59 @@ -123,35 +93,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:61 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:63 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md: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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:67 -msgid "" -"If you change the bot password (`matrix_bot_maubot_initial_password` in " -"your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_bot_maubot_initial_password` to let the bot know its new " -"password." +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:69 @@ -159,9 +113,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:71 -msgid "" -"By default, you can visit `matrix.example.com/_matrix/maubot/` to manage " -"your available plugins, clients and instances." +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:73 @@ -169,24 +121,15 @@ msgid "You should start in the following order" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:74 -msgid "" -"**Create one or more clients**: A client is a Matrix account which the " -"bot will use to message. By default, the playbook creates a `bot.maubot` " -"account (as per the configuration above). You only need to [obtain an " -"access token](#obtaining-an-access-token) for it" +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:75 -msgid "" -"**Upload some Plugins**: Plugins can be obtained from " -"[here](https://github.com/maubot/maubot#plugins) or any other source." +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:76 -msgid "" -"**Create an instance**: An instance is the actual bot. You have to " -"specify a client which the bot instance will use and the plugin (how the " -"bot will behave)" +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 @@ -194,20 +137,9 @@ msgid "Obtaining an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 -msgid "" -"This can be done via `mbc login` then `mbc auth` (see the [maubot " -"documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run " -"these commands, you'll first need to `exec` into the maubot container " -"with `docker exec -it matrix-bot-maubot sh`." +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:82 -msgid "" -"Alternatively, you can follow our generic [obtain an access token" -"](obtaining-access-tokens.md) documentation. Be aware that you'd better " -"use the **Obtain an access token via curl** method (not **Obtain an " -"access token via Element Web**) as the latter will give your bot issues " -"in encrypted rooms. Read " -"[more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index cbadc9714..4d52e2e66 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -25,16 +25,11 @@ msgid "Setting up Mjolnir (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:3 -msgid "" -"The playbook can install and configure the [Mjolnir](https://github.com" -"/matrix-org/mjolnir) moderation bot for you." +msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/mjolnir/blob/main/README.md) to learn what it does and why it might " -"be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:7 @@ -46,15 +41,11 @@ msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:11 -msgid "" -"The playbook does not automatically create users for you. You **need to " -"register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 -msgid "" -"Choose a strong password for the bot. You can generate a good password " -"with a command like this: `pwgen -s 64 1`." +msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:15 @@ -62,10 +53,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:21 -msgid "" -"If you would like Mjolnir to be able to deactivate users, move aliases, " -"shutdown rooms, etc then it must be a server admin so you need to change " -"`admin=no` to `admin=yes` in the command above." +msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:23 @@ -73,10 +61,7 @@ msgid "Get an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 -msgid "" -"The bot requires an access token to be able to connect to your " -"homeserver. Refer to the documentation on [how to obtain an access token" -"](obtaining-access-tokens.md)." +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 @@ -84,59 +69,31 @@ msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "" -"If your homeserver's implementation is Synapse, you will need to prevent " -"it from rate limiting the bot's account. **This is a required step. If " -"you do not configure it, Mjolnir will crash.**" +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "" -"This can be done using Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-" -"ratelimiting-for-users). They can be accessed both externally and " -"internally." +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 -msgid "" -"To expose the APIs publicly, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:39 -msgid "" -"The APIs can also be accessed via [Synapse " -"Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can " -"use to administrate users, rooms, media, etc. on your Matrix server. The " -"playbook can install and configure Synapse Admin for you. For details " -"about it, see [this page](configuring-playbook-synapse-admin.md)." +msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:41 -msgid "" -"**Note**: access to the APIs is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, " -"doing so is not recommended for additional security. See [official " -"Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints)." +msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:43 -msgid "" -"To discharge rate limiting, run the following command on systems that " -"ship curl (note that it does not work on outdated Windows 10). Even if " -"the APIs are not exposed to the internet, you should still be able to run" -" the command on the homeserver locally. Before running it, make sure to " -"replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" +msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:49 -msgid "" -"You can obtain an access token for a homeserver admin account in the same" -" way as you can do so for Mjolnir itself. If you have made Mjolnir an " -"admin, you can just use the Mjolnir token." +msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:51 @@ -144,32 +101,19 @@ msgid "Create a management room" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:53 -msgid "" -"Using your own account, create a new invite only room that you will use " -"to manage the bot. This is the room where you will see the status of the " -"bot and where you will send commands to the bot, such as the command to " -"ban a user from another room. Anyone in this room can control the bot so " -"it is important that you only invite trusted users to this room." +msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:55 -msgid "" -"If you make the management room encrypted (E2EE), then you MUST enable " -"and use Pantalaimon (see [below](#configuration-with-e2ee-support))." +msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:57 -msgid "" -"Once you have created the room you need to copy the room ID so you can " -"tell the bot to use that room. In Element Web you can do this by going to" -" the room's settings, clicking Advanced, and then copying the internal " -"room ID. The room ID will look something like `!qporfwt:example.com`." +msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:59 -msgid "" -"Finally invite the `@bot.mjolnir:example.com` account you created earlier" -" into the room." +msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:61 @@ -177,10 +121,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:63 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:72 @@ -188,16 +129,11 @@ msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:74 -msgid "" -"Decide whether you want Mjolnir to be capable of operating in end-to-end " -"encrypted (E2EE) rooms. This includes the management room and the " -"moderated rooms." +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:76 -msgid "" -"To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-" -"pantalaimon.md)." +msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:78 @@ -205,25 +141,15 @@ msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:80 -msgid "" -"When using Pantalaimon, Mjolnir will log in to its bot account itself " -"through Pantalaimon, so configure its username and password." +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:82 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:96 -msgid "" -"The playbook's `group_vars` will configure other required settings. If " -"using this role separately without the playbook, you also need to " -"configure the two URLs that Mjolnir uses to reach the homeserver, one " -"through Pantalaimon and one \"raw\". This example is taken from the " -"playbook's `group_vars`:" +msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:108 @@ -231,17 +157,11 @@ msgid "Configuration without E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:110 -msgid "" -"When NOT using Pantalaimon, Mjolnir does not log in by itself and you " -"must give it an access token for its bot account." +msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -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](#get-an-access-" -"token)." +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](#get-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:118 @@ -249,10 +169,7 @@ msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:120 -msgid "" -"To enable Mjolnir synapse antispam module, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file (adapt to your needs):" +msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:130 @@ -260,17 +177,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:132 -msgid "" -"You can configure additional options by adding the " -"`matrix_bot_mjolnir_configuration_extension_yaml` variable to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file." +msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:134 -msgid "" -"For example, to change Mjolnir's `recordIgnoredInvites` option to `true`," -" add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:148 @@ -278,9 +189,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:150 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:157 @@ -288,35 +197,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:159 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:161 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:163 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:165 -msgid "" -"If you change the Pantalaimon's password " -"(`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) " -"subsequently, its credentials on the homeserver won't be updated " -"automatically. If you'd like to change the password, use a tool like " -"[synapse-admin](configuring-playbook-synapse-admin.md) to change it, and " -"then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon " -"know its new password." +msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:167 @@ -324,120 +217,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:169 -msgid "" -"You can refer to the upstream [documentation](https://github.com/matrix-" -"org/mjolnir) for additional ways to use and configure Mjolnir. Check out " -"their [quickstart guide](https://github.com/matrix-org/mjolnir" -"#quickstart-guide) for some basic commands you can give to the bot." +msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/mjolnir) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ msgstr "" - -#~ msgid "" -#~ "The playbook does not automatically " -#~ "create users for you. The bot " -#~ "requires an access token to be " -#~ "able to connect to your homeserver." -#~ msgstr "" - -#~ msgid "" -#~ "You **need to register the bot " -#~ "user manually** before setting up the" -#~ " bot." -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the documentation on [how " -#~ "to obtain an access token](obtaining-" -#~ "access-tokens.md)." -#~ msgstr "" - -#~ msgid "" -#~ "You will need to prevent Synapse " -#~ "from rate limiting the bot's account." -#~ " This is not an optional step. " -#~ "If you do not do this step " -#~ "Mjolnir will crash. This can be " -#~ "done using Synapse's [admin API](https" -#~ "://matrix-" -#~ "org.github.io/synapse/latest/admin_api/user_admin_api.html" -#~ "#override-ratelimiting-for-users). Please " -#~ "ask for help if you are " -#~ "uncomfortable with these steps or run" -#~ " into issues." -#~ msgstr "" - -#~ msgid "" -#~ "If your Synapse Admin API is " -#~ "exposed to the internet for some " -#~ "reason like running the Synapse Admin" -#~ " Role [Link](configuring-playbook-synapse-" -#~ "admin.md) or running " -#~ "`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -#~ " true` in your playbook config. If" -#~ " your API is not externally exposed" -#~ " you should still be able to on" -#~ " the local host for your synapse " -#~ "run these commands." -#~ msgstr "" - -#~ msgid "" -#~ "The following command works on semi " -#~ "up to date Windows 10 installs and" -#~ " All Windows 11 installations and " -#~ "other systems that ship curl. `curl " -#~ "--header \"Authorization: Bearer \"" -#~ " -X POST " -#~ "https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit`" -#~ " Replace `@bot.mjolnir:example.com` with the " -#~ "MXID of your Mjolnir and example.com " -#~ "with your homeserver domain. You can " -#~ "easily obtain an access token for " -#~ "a homeserver admin account the same " -#~ "way you can obtain an access token" -#~ " for Mjolnir itself. If you made " -#~ "Mjolnir Admin you can just use the" -#~ " Mjolnir token." -#~ msgstr "" - -#~ msgid "" -#~ "If you make the management room " -#~ "encrypted (E2EE), then you MUST enable" -#~ " and use Pantalaimon (see below)." -#~ msgstr "" - -#~ msgid "" -#~ "Decide whether you want Mjolnir to " -#~ "be capable of operating in end-" -#~ "to-end encrypted (E2EE) rooms. This " -#~ "includes the management room and the " -#~ "moderated rooms. To support E2EE, " -#~ "Mjolnir needs to [use Pantalaimon" -#~ "](configuring-playbook-pantalaimon.md)." -#~ msgstr "" - -#~ msgid "a. Configuration with E2EE support" -#~ msgstr "" - -#~ msgid "b. Configuration without E2EE support" -#~ msgstr "" - -#~ msgid "" -#~ "You must replace " -#~ "`ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and " -#~ "`ROOM_ID_FROM_STEP_4_GOES_HERE` with your own " -#~ "values." -#~ msgstr "" - -#~ msgid "" -#~ "For example to change Mjolnir's " -#~ "`recordIgnoredInvites` option to `true` you" -#~ " would add the following to your " -#~ "`vars.yml` file." -#~ 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 9471d4d91..9597f9293 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 @@ -25,38 +25,23 @@ msgid "Setting up Appservice Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" -"discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-" -"discord.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4 -msgid "" -"For using as a Bot we are recommend the Appservice Discord bridge (the " -"one being discussed here), because it supports plumbing." +msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5 -msgid "" -"For personal use we recommend the [mautrix-discord](configuring-playbook-" -"bridge-mautrix-discord.md) bridge, because it is the most fully-featured " -"and stable of the 3 Discord bridges supported by the playbook." +msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"discord](https://github.com/matrix-org/matrix-appservice-discord) for " -"you." +msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"appservice-discord/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11 @@ -64,10 +49,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13 -msgid "" -"Create a Discord Application " -"[here](https://discordapp.com/developers/applications). Then retrieve " -"Client ID, and create a bot from the Bot tab and retrieve the Bot token." +msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15 @@ -75,9 +57,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:31 @@ -85,9 +65,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40 @@ -95,24 +73,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:46 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48 @@ -120,17 +89,11 @@ msgid "Self-Service Bridging (Manual)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50 -msgid "" -"Self-service bridging allows you to bridge specific and existing Matrix " -"rooms to specific Discord rooms. To enable it, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56 -msgid "" -"**Note**: If self-service bridging is not enabled, `!discord help` " -"commands will return no results." +msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58 @@ -139,9 +102,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60 -msgid "" -"Once self-service is enabled, start a chat with " -"`@_discord_bot:example.com` and say `!discord help bridge`." +msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62 @@ -149,16 +110,11 @@ msgid "Then, follow the instructions in the help output message." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64 -msgid "" -"If the bot is not already in the Discord server, follow the provided " -"invite link. This may require you to be a administrator of the Discord " -"server." +msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 -msgid "" -"On the Discord side, you can say `!matrix help` to get a list of " -"available commands to manage the bridge and Matrix users." +msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 @@ -170,26 +126,15 @@ msgid "Portal Bridging (Automatic)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72 -msgid "" -"Through portal bridging, Matrix rooms will automatically be created by " -"the bot and bridged to the relevant Discord room. This is done by simply " -"joining a room with a specific name pattern " -"(`#_discord__`)." +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: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." +msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76 -msgid "" -"To disable portal bridging, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84 @@ -197,26 +142,15 @@ msgid "To get started with Portal Bridging:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86 -msgid "" -"To invite the bot to Discord, retrieve the invite link from the `{{ " -"matrix_appservice_discord_config_path }}/invite_link` file on the server " -"(this defaults to `/matrix/appservice-discord/config/invite_link`). You " -"need to peek at the file on the server via SSH, etc., because it's not " -"available via HTTP(S)." +msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87 -msgid "" -"Room addresses follow this syntax: `#_discord__`. 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//`." +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:88 -msgid "" -"Once you have figured out the appropriate room address, you can join by " -"doing `/join #_discord__` in your Matrix client." +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:90 @@ -224,23 +158,13 @@ msgid "Getting Administrator access in a portal bridged room" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92 -msgid "" -"By default, you won't have Administrator access in rooms created by the " -"bridge." +msgid "By default, you won't have Administrator access in rooms created by the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94 -msgid "" -"To adjust room access privileges or do various other things (change the " -"room name subsequently, etc.), you'd wish to become an Administrator." +msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96 -msgid "" -"There's the Discord bridge's guide for [setting privileges on bridge " -"managed rooms](https://github.com/matrix-org/matrix-appservice-" -"discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-" -"rooms). To do the same with our container setup, run the following " -"command on the server:" +msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po index 5b634a302..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 @@ -25,24 +25,15 @@ msgid "Setting up Appservice IRC bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3 -msgid "" -"**Note**: bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " -"via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) " -"bridge supported by the playbook." +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5 -msgid "" -"The playbook can install and configure the [matrix-appservice-" -"irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." +msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"appservice-irc/blob/master/HOWTO.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9 @@ -50,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:63 @@ -60,9 +49,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72 @@ -70,24 +57,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:78 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80 @@ -95,8 +73,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82 -msgid "" -"To use the bridge, you need to start a chat with `@irc_bot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po index 39afd04fa..be0b9f9c8 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 @@ -25,27 +25,15 @@ msgid "Setting up Appservice Kakaotalk bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) " -"for you. `matrix-appservice-kakaotalk` is a bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" -" based on [node-kakao](https://github.com/storycraft/node-kakao) (now " -"unmaintained) and some [mautrix-" -"facebook](https://github.com/mautrix/facebook) code." +msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5 -msgid "" -"⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using" -" this bridge may get your account banned**." +msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7 -msgid "" -"See the project's [documentation](https://src.miscworks.net/fair/matrix-" -"appservice-kakaotalk/src/branch/master/README.md) to learn what it does " -"and why it might be useful to you." +msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9 @@ -53,18 +41,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15 @@ -72,16 +53,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:23 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25 @@ -89,9 +65,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29 @@ -99,18 +73,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31 -msgid "" -"`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for " -"some variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32 -msgid "" -"`roles/custom/matrix-bridge-appservice-" -"kakaotalk/templates/config.yaml.j2` for the bridge's default " -"configuration. You can override settings (even those that don't have " -"dedicated playbook variables) using the " -"`matrix_appservice_kakaotalk_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_kakaotalk_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34 @@ -118,9 +85,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43 @@ -128,24 +93,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:49 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51 @@ -153,17 +109,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53 -msgid "" -"To use the bridge, you need to start a chat with " -"`@kakaotalkbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55 -msgid "" -"Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable " -"bridging for your Kakaotalk account. The `--save` flag may be omitted, if" -" you'd rather not save your password." +msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57 @@ -171,10 +121,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61 @@ -186,17 +133,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69 @@ -204,34 +145,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77 -msgid "" -"make sure you don't log out the `Appservice-Kakaotalk` device some time " -"in the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://src.miscworks.net/fair/matrix-" -#~ "appservice-kakaotalk) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ 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 dced8b80f..de682447f 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 @@ -30,37 +30,19 @@ 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." +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\"." +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." +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." +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 @@ -72,22 +54,15 @@ 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)." +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." +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`." +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 @@ -135,20 +110,11 @@ 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." +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." +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 @@ -160,10 +126,7 @@ 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." +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 @@ -171,15 +134,11 @@ 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:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64 -msgid "" -"Other configuration options are available via the " -"`matrix_appservice_slack_configuration_extension_yaml` variable." +msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66 @@ -187,30 +146,19 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83 @@ -218,42 +166,27 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85 -msgid "" -"To use the bridge, you need to send `/invite @slackbot:example.com` to " -"invite the bridge bot user into the admin room." +msgid "To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87 -msgid "" -"If Team Sync is not enabled, for each channel you would like to bridge, " -"perform the following steps:" +msgid "If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89 -msgid "" -"Create a Matrix room in the usual manner for your client. Take a note of " -"its Matrix room ID - it will look something like `!qporfwt:example.com`." +msgid "Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID - it will look something like `!qporfwt:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90 -msgid "" -"Invite the bot user to both the Slack and Matrix channels you would like " -"to bridge using `/invite @matrixbot` for Slack and `/invite " -"@slackbot:example.com` for Matrix." +msgid "Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91 -msgid "" -"Determine the \"channel ID\" that Slack uses to identify the channel. You" -" can see it when you open a given Slack channel in a browser. The URL " -"reads like this: `https://app.slack.com/client/XXX//details/`." +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:92 -msgid "" -"Issue a link command in the administration control room with these " -"collected values as arguments:" +msgid "Issue a link command in the administration control room with these collected values as arguments:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94 @@ -277,10 +210,7 @@ msgid "Channels can be unlinked again by sending this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120 -msgid "" -"Unlinking doesn't only disconnect the bridge, but also makes the slackbot" -" leave the bridged Matrix room. So in case you want to re-link later, " -"don't forget to re-invite the slackbot into this room again." +msgid "Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122 @@ -296,9 +226,7 @@ msgid "Linking: \"Room is now pending-name\"" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128 -msgid "" -"This typically means that you haven't used the correct Slack channel ID. " -"Unlink the room and recheck 'Determine the \"channel ID\"' from above." +msgid "This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the \"channel ID\"' from above." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130 @@ -311,15 +239,9 @@ msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134 #, python-format -msgid "" -"`WARN SlackEventHandler Ignoring message from unrecognised Slack channel " -"ID : %s (%s) `" +msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) `" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136 -msgid "" -"then unlink your room, reinvite the bot and re-link it again. This may " -"particularly hit you, if you tried to unsuccessfully link your room " -"multiple times without unlinking it after each failed attempt." +msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po index af53cf585..416e522f8 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 @@ -25,27 +25,15 @@ msgid "Setting up Appservice Webhooks bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3 -msgid "" -"**Note**: This bridge has been deprecated. We recommend not bothering " -"with installing it. While not a 1:1 replacement, the bridge's author " -"suggests taking a look at [matrix-hookshot](https://github.com/matrix-org" -"/matrix-hookshot) as a replacement, which can also be installed using " -"[this playbook](configuring-playbook-bridge-hookshot.md). Consider using " -"that bridge instead of this one." +msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5 -msgid "" -"The playbook can install and configure [matrix-appservice-" -"webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for " -"you. This bridge provides support for Slack-compatible webhooks." +msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7 -msgid "" -"See the project's [documentation](https://github.com/turt2live/matrix-" -"appservice-webhooks/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9 @@ -53,9 +41,7 @@ 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:" +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 @@ -63,9 +49,7 @@ 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:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36 @@ -73,24 +57,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -98,27 +73,19 @@ 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." +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)" +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)" +msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51 -msgid "" -"You then need to send a message to the bridge bot in order to receive a " -"private message including the webhook link:" +msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:" msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57 @@ -134,23 +101,13 @@ 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." +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\"." +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." +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 82271f69a..db756b10b 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 @@ -25,19 +25,11 @@ msgid "Setting up Beeper Linkedin bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3 -msgid "" -"The playbook can install and configure [beeper-" -"linkedin](https://github.com/beeper/linkedin) for you, for bridging to " -"[LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on " -"the mautrix-python framework and can be configured in a similar way to " -"the other mautrix bridges" +msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5 -msgid "" -"See the project's " -"[documentation](https://github.com/beeper/linkedin/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7 @@ -45,34 +37,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:15 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-beeper-" -"linkedin/templates/config.yaml.j2` to find other things you would like to" -" configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35 @@ -80,9 +61,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44 @@ -90,53 +69,31 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:50 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52 -msgid "" -"Set up Double Puppeting by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60 @@ -144,29 +101,19 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62 -msgid "" -"To use the bridge, you need to start a chat with " -"`@linkedinbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64 -msgid "" -"Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable " -"bridging for your LinkedIn account." +msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68 -msgid "" -"After successfully enabling bridging, you may wish to [set up Double " -"Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-" -"or-shared-secret-auth), if you haven't already done so." +msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so." msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70 @@ -178,10 +125,5 @@ msgid "Bridge asking for 2FA even if you don't have 2FA enabled" msgstr "" #: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74 -msgid "" -"If you don't have 2FA enabled and are logging in from a strange IP for " -"the first time, LinkedIn will send an email with a one-time code. You can" -" use this code to authorize the bridge session. In my experience, once " -"the IP is authorized, you will not be asked again." +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 ce60bf716..958c405a0 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 @@ -25,16 +25,11 @@ msgid "Setting up Go Skype Bridge bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3 -msgid "" -"The playbook can install and configure [go-skype-" -"bridge](https://github.com/kelaresg/go-skype-bridge) for you." +msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5 -msgid "" -"See the project's [documentation](https://github.com/kelaresg/go-skype-" -"bridge/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7 @@ -42,10 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9 -msgid "" -"To enable the [Skype](https://www.skype.com/) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15 @@ -53,9 +45,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24 @@ -63,24 +53,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32 @@ -88,19 +69,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34 -msgid "" -"To use the bridge, you need to start a chat with `Skype bridge bot` with " -"the handle `@skypebridgebot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 msgid "Send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 86ee04111..ec26b7f68 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 @@ -25,27 +25,15 @@ msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3 -msgid "" -"**Note**: bridging to " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen " -"via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-" -"irc.md) bridge supported by the playbook." +msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5 -msgid "" -"The playbook can install and configure " -"[Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style " -"[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." +msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/hifi/heisenbridge/blob/master/README.md)" -" to learn what it does and why it might be useful to you. You can also " -"take a look at [this demonstration " -"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9 @@ -53,16 +41,11 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11 -msgid "" -"To enable Heisenbridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24 -msgid "" -"For a more complete list of variables that you could override, see the " -"[`defaults/main.yml` file](../roles/custom/matrix-bridge-" -"heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26 @@ -70,32 +53,19 @@ msgid "Adjusting the Heisenbridge URL" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28 -msgid "" -"By default, this playbook installs Heisenbridge on the `matrix.` " -"subdomain, at the `/heisenbridge` path " -"(https://matrix.example.com/heisenbridge). It would handle media requests" -" there (see the [release notes for Heisenbridge " -"v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." +msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30 -msgid "" -"This makes it easy to install it, because it **doesn't require additional" -" DNS records to be set up**. If that's okay, you can skip this section." +msgid "This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:32 -msgid "" -"By tweaking the `matrix_heisenbridge_hostname` and " -"`matrix_heisenbridge_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42 @@ -103,9 +73,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Heisenbridge domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46 @@ -113,9 +81,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50 @@ -123,10 +89,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:59 @@ -134,24 +97,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:65 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67 @@ -159,11 +113,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69 -msgid "" -"To use the bridge, you need to start a chat with " -"`@heisenbridge:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain). If the bridge ignores you and a DM is not " -"accepted then the owner setting may be wrong." +msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71 @@ -171,24 +121,9 @@ msgid "Help is available for all commands with the `-h` switch." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73 -msgid "" -"You can also learn the basics by watching [this demonstration " -"video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." +msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." msgstr "" #: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75 -msgid "" -"If you encounter issues or feel lost you can join the project room at " -"[#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help." +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 "" - -#~ msgid "" -#~ "See the project's " -#~ "[README](https://github.com/hifi/heisenbridge/blob/master/README.md)" -#~ " to learn what it does and why" -#~ " it might be useful to you. You" -#~ " can also take a look at [this" -#~ " demonstration " -#~ "video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)." -#~ 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 14ef06275..e7459a3d9 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 @@ -25,30 +25,19 @@ msgid "Setting up matrix-hookshot (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:3 -msgid "" -"The playbook can install and configure [matrix-" -"hookshot](https://github.com/matrix-org/matrix-hookshot) for you." +msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:5 -msgid "" -"Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) " -"from software project management services such as GitHub, GitLab, Jira, " -"and Figma, as well as generic webhooks." +msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:7 -msgid "" -"See the project's [documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/hookshot.html) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:9 -msgid "" -"**Note**: the playbook also supports [matrix-appservice-webhooks" -"](configuring-playbook-bridge-appservice-webhooks.md), which however was " -"deprecated by its author." +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 @@ -60,16 +49,11 @@ msgid "Download GitHub app private key (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:15 -msgid "" -"If you're setting up the GitHub bridge, you need to create your GitHub " -"app, and generate a private key file of it." +msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:17 -msgid "" -"You need to download the private key file, if you will install the file " -"manually or with the `aux` role. For details, see [the section below" -"](#manage-github-private-key-with-aux-role)." +msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:19 @@ -77,27 +61,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to " -"replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-" -"github-app-private-key)." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:35 -msgid "" -"For each of the services (GitHub, GitLab, Jira, Figma, and generic " -"webhooks) fill in the respective variables `matrix_hookshot_service_*` " -"listed in [main.yml](../roles/custom/matrix-bridge-" -"hookshot/defaults/main.yml) as required." +msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:37 -msgid "" -"Take special note of the `matrix_hookshot_*_enabled` variables. Services " -"that need no further configuration are enabled by default (GitLab and " -"generic webhooks), while you must first add the required configuration " -"and enable the others (GitHub, Jira, and Figma)." +msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:39 @@ -105,18 +77,11 @@ msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:41 -msgid "" -"You can configure additional options by adding the " -"`matrix_hookshot_configuration_extension_yaml` and " -"`matrix_hookshot_registration_extension_yaml` variables." +msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:43 -msgid "" -"Refer the [official instructions](https://matrix-org.github.io/matrix-" -"hookshot/latest/setup.html) and the comments in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to " -"learn what the individual options do." +msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:45 @@ -124,24 +89,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:47 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:54 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service hookshot` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:56 -msgid "" -"`just install-service hookshot` is useful for maintaining your setup " -"quickly when its components remain unchanged. If you adjust your " -"`vars.yml` to remove other components, you'd need to run `just setup-" -"all`, or these components will still remain installed. Note `just setup-" -"all` runs the `ensure-matrix-users-created` tag too." +msgid "`just install-service hookshot` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:58 @@ -149,35 +105,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:60 -msgid "" -"To use the bridge, you need to create a room and invite the Hookshot bot " -"(`@hookshot:example.com`) to it." +msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:62 -msgid "" -"Make sure the bot is able to send state events (usually the Moderator " -"power level in clients)." +msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:64 -msgid "" -"Send `!hookshot help` to the room to see the bridge's help menu for " -"additional commands." +msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:66 -msgid "" -"Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-" -"hookshot/latest/usage.html) for more details about using the bridge's " -"various features." +msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:68 -msgid "" -"💡 **Note**: the different listeners are bound to certain paths which " -"might differ from those assumed by the hookshot documentation. See [URLs " -"for bridges setup](#urls-for-bridges-setup) below." +msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:70 @@ -185,9 +129,7 @@ msgid "Reset crypto store" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:72 -msgid "" -"Should the crypto store be corrupted, you can reset it by executing this " -"Ansible playbook with the tag `reset-hookshot-encryption` added:" +msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:78 @@ -199,9 +141,7 @@ msgid "URLs for bridges setup" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:82 -msgid "" -"Unless indicated otherwise, the following endpoints are reachable on your" -" `matrix.` subdomain (if the feature is enabled)." +msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md @@ -357,11 +297,7 @@ 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." +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 @@ -369,19 +305,11 @@ msgid "Prometheus" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:96 -msgid "" -"Also see the various `matrix_hookshot_container_labels_*` variables in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), " -"which expose URLs publicly" +msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:98 -msgid "" -"The different listeners are also reachable *internally* in the docker-" -"network via the container's name (configured by " -"`matrix_hookshot_container_url`) and on different ports (e.g. " -"`matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom" -"/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." +msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:100 @@ -389,44 +317,27 @@ msgid "Manage GitHub Private Key with aux role" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:102 -msgid "" -"The GitHub bridge requires you to install a private key file. This can be" -" done in multiple ways:" +msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:104 -msgid "" -"copy the *contents* of the downloaded file and set the variable " -"`matrix_hookshot_github_private_key` to the contents (see example in " -"[main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." +msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:105 -msgid "" -"somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ " -"matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot" -"/private-key.pem`) on the server manually." +msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:106 -msgid "" -"use the [`aux` role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-aux) to copy the file from an arbitrary path on your " -"ansible client to the correct path on the server." +msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:108 -msgid "" -"To use the `aux` role, make sure the `matrix_hookshot_github_private_key`" -" variable is empty. Then add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:119 -msgid "" -"For more information, see the documentation in the [default configuration" -" of the aux role](https://github.com/mother-of-all-self-hosting/ansible-" -"role-aux/blob/main/defaults/main.yml)." +msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:121 @@ -434,13 +345,7 @@ msgid "Provisioning API" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:123 -msgid "" -"The provisioning API will be enabled automatically if you set " -"`matrix_dimension_enabled: true` and provided a " -"`matrix_hookshot_provisioning_secret`, unless you override it either way." -" To use hookshot with dimension, you will need to enter as \"Provisioning" -" URL\": `http://matrix-hookshot:9002`, which is made up of the variables " -"`matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." +msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:125 @@ -448,45 +353,27 @@ msgid "Metrics" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:127 -msgid "" -"Metrics are **only enabled by default** if the builtin [Prometheus" -"](configuring-playbook-prometheus-grafana.md) is enabled (by default, " -"Prometheus isn't enabled). If so, metrics will automatically be collected" -" by Prometheus and made available in Grafana. You will, however, need to " -"set up your own Dashboard for displaying them." +msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:129 -msgid "" -"To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: " -"true`. This only exposes metrics over the container network, however." +msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:131 -msgid "" -"**To collect metrics from an external Prometheus server**, besides " -"enabling metrics as described above, you will also need to enable metrics" -" exposure on `https://matrix.example.com/metrics/hookshot` by:" +msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:133 -msgid "" -"either enabling metrics exposure for Hookshot via " -"`matrix_hookshot_metrics_proxying_enabled: true`" +msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:134 -msgid "" -"or enabling metrics exposure for all services via " -"`matrix_metrics_exposure_enabled: true`" +msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:136 -msgid "" -"Whichever one you go with, by default metrics are exposed publicly " -"**without** password-protection. See [the Prometheus and Grafana docs" -"](configuring-playbook-prometheus-grafana.md) for details about password-" -"protection for metrics." +msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:138 @@ -494,184 +381,5 @@ msgid "Collision with matrix-appservice-webhooks" msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:140 -msgid "" -"If you are also running [matrix-appservice-webhooks](configuring-" -"playbook-bridge-appservice-webhooks.md), it reserves its namespace by the" -" default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. " -"You should take care if you modify its or hookshot's prefix that they do " -"not collide with each other's namespace (default " -"`matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)." +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 "" - -#~ 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 "" - -#~ msgid "" -#~ "See the project's [documentation](https://matrix-" -#~ "org.github.io/matrix-hookshot/latest/hookshot.html) to " -#~ "learn what it does in detail and" -#~ " why it might be useful to you." -#~ msgstr "" - -#~ msgid "Setup Instructions" -#~ msgstr "" - -#~ msgid "" -#~ "Refer to the [official instructions](https" -#~ "://matrix-org.github.io/matrix-hookshot/latest/setup.html)" -#~ " to learn what the individual options" -#~ " do." -#~ msgstr "" - -#~ msgid "" -#~ "Enable the bridge by adding " -#~ "`matrix_hookshot_enabled: true` to your " -#~ "`vars.yml` file" -#~ msgstr "" - -#~ msgid "" -#~ "For each of the services (GitHub, " -#~ "GitLab, Jira, Figma, generic webhooks) " -#~ "fill in the respective variables " -#~ "`matrix_hookshot_service_*` listed in " -#~ "[main.yml](/roles/custom/matrix-bridge-" -#~ "hookshot/defaults/main.yml) as required." -#~ msgstr "" - -#~ msgid "" -#~ "Take special note of the " -#~ "`matrix_hookshot_*_enabled` variables. Services that" -#~ " need no further configuration are " -#~ "enabled by default (GitLab, Generic), " -#~ "while you must first add the " -#~ "required configuration and enable the " -#~ "others (GitHub, Jira, Figma)." -#~ msgstr "" - -#~ msgid "" -#~ "If you're setting up the GitHub " -#~ "bridge, you'll need to generate and " -#~ "download a private key file after " -#~ "you created your GitHub app. Copy " -#~ "the contents of that file to the" -#~ " variable `matrix_hookshot_github_private_key` so " -#~ "the playbook can install it for " -#~ "you, or use one of the [other " -#~ "methods](#manage-github-private-key-with-" -#~ "aux-role) explained below." -#~ msgstr "" - -#~ msgid "" -#~ "If you've already installed Matrix " -#~ "services using the playbook before, " -#~ "you'll need to re-run it (`--tags" -#~ "=setup-all,start`). If not, proceed with" -#~ " [configuring other playbook services" -#~ "](configuring-playbook.md) and then with " -#~ "[Installing](installing.md). Get back to this" -#~ " guide once ready. Hookshot can be" -#~ " set up individually using the tag" -#~ " `setup-hookshot`." -#~ msgstr "" - -#~ msgid "" -#~ "Other configuration options are available " -#~ "via the `matrix_hookshot_configuration_extension_yaml` " -#~ "and `matrix_hookshot_registration_extension_yaml` " -#~ "variables, see the comments in " -#~ "[main.yml](/roles/custom/matrix-bridge-" -#~ "hookshot/defaults/main.yml) for how to use " -#~ "them." -#~ msgstr "" - -#~ msgid "Finally, run the playbook (see [installing](installing.md))." -#~ msgstr "" - -#~ msgid "End-to-bridge encryption" -#~ msgstr "" - -#~ msgid "" -#~ "You can enable [encryption](https://matrix-" -#~ "org.github.io/matrix-hookshot/latest/advanced/encryption.html)" -#~ " for Hookshot by adding " -#~ "`matrix_hookshot_encryption_enabled: true` to your" -#~ " configuration (`vars.yml`) and [executing " -#~ "the playbook](installing.md) again." -#~ msgstr "" - -#~ msgid "" -#~ "Should the crypto store be corrupted," -#~ " you can reset it by executing " -#~ "this Ansible playbook with the tag " -#~ "`reset-hookshot-encryption` added, for " -#~ "example `ansible-playbook -i inventory/hosts" -#~ " setup.yml --tags=reset-hookshot-encryption`." -#~ msgstr "" - -#~ msgid "Send a `!hookshot help` message to see a list of help commands." -#~ msgstr "" - -#~ msgid "" -#~ "**Important**: Note that the different " -#~ "listeners are bound to certain paths " -#~ "which might differ from those assumed" -#~ " by the hookshot documentation, see " -#~ "[URLs for bridges setup](#urls-for-" -#~ "bridges-setup) below." -#~ msgstr "" - -#~ msgid "listener" -#~ msgstr "" - -#~ msgid "default path" -#~ msgstr "" - -#~ msgid "variable" -#~ msgstr "" - -#~ msgid "used as" -#~ msgstr "" - -#~ msgid "JIRA OAuth" -#~ msgstr "" - -#~ 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 "" - -#~ 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 "" - -#~ 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 "" - -#~ msgid "" -#~ "To use the `aux` role, make sure" -#~ " the `matrix_hookshot_github_private_key` variable " -#~ "is empty. Then add the following " -#~ "additional configuration:" -#~ 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 3ee8066a8..6b3ec344e 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 @@ -25,23 +25,15 @@ msgid "Setting up Matrix SMS bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3 -msgid "" -"The playbook can install and configure [matrix-sms-" -"bridge](https://github.com/benkuly/matrix-sms-bridge) for you." +msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5 -msgid "" -"See the project's [documentation](https://github.com/benkuly/matrix-sms-" -"bridge/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7 -msgid "" -"**The bridge uses [android-sms-gateway-" -"server](https://github.com/RebekkaMa/android-sms-gateway-server). You " -"need to configure it first.**" +msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9 @@ -49,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:34 @@ -59,9 +49,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43 @@ -69,24 +57,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:49 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51 @@ -94,14 +73,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53 -msgid "" -"Read the [user guide](https://github.com/benkuly/matrix-sms-" -"bridge/blob/master/README.md#user-guide) to see how this bridge works." +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 "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 d30d15e2e..fa8864352 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 @@ -25,38 +25,23 @@ msgid "Setting up Mautrix Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-" -"discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-" -"appservice-discord.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4 -msgid "" -"For using as a Bot we recommend the [Appservice Discord](configuring-" -"playbook-bridge-appservice-discord.md), because it supports plumbing." +msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:5 -msgid "" -"For personal use with a discord account we recommend the `mautrix-" -"discord` bridge (the one being discussed here), because it is the most " -"fully-featured and stable of the 3 Discord bridges supported by the " -"playbook." +msgid "For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7 -msgid "" -"The playbook can install and configure [mautrix-" -"discord](https://github.com/mautrix/discord) for you." +msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/discord/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:11 @@ -64,21 +49,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13 -msgid "" -"There are 2 ways to login to discord using this bridge, either by " -"[scanning a QR code](#method-1-login-using-qr-code-recommended) using the" -" Discord mobile app **or** by using a [Discord token](#method-2-login-" -"using-discord-token-not-recommended)." +msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15 -msgid "" -"If this is a dealbreaker for you, consider using one of the other Discord" -" bridges supported by the playbook: [mx-puppet-discord](configuring-" -"playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord" -"](configuring-playbook-bridge-appservice-discord.md). These come with " -"their own complexity and limitations, however, so we recommend that you " -"proceed with this one if possible." +msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17 @@ -86,19 +61,11 @@ msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23 @@ -106,16 +73,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33 @@ -123,9 +85,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge." +msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37 @@ -133,17 +93,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39 -msgid "" -"`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some " -"variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40 -msgid "" -"`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for" -" the bridge's default configuration. You can override settings (even " -"those that don't have dedicated playbook variables) using the " -"`matrix_mautrix_discord_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_discord_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42 @@ -151,9 +105,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51 @@ -161,24 +113,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:57 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59 @@ -194,9 +137,7 @@ msgid "Method 1: Login using QR code (recommended)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65 -msgid "" -"For using this bridge, you would need to authenticate by **scanning a QR " -"code** with the Discord app on your phone." +msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67 @@ -208,15 +149,7 @@ msgid "Method 2: Login using Discord token (not recommended)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71 -msgid "" -"To acquire the token, open Discord in a private browser window. Then open" -" the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or " -"by pressing \"F12\"). Navigate to the \"Network\" tab then reload the " -"page. In the URL filter or search bar type \"/api\" and find the response" -" with the file name of \"library\". Under the request headers you should " -"find a variable called \"Authorization\", this is the token to your " -"Discord account. After copying the token, you can close the browser " -"window." +msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73 @@ -224,34 +157,23 @@ msgid "Bridging" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75 -msgid "" -"Start a chat with `@discordbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "Start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:76 -msgid "" -"If you would like to login to Discord using a token, send `login-token` " -"command, otherwise, send `login-qr` command." +msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77 -msgid "" -"You'll see a QR code which you need to scan with the Discord app on your " -"phone. You can scan it with the camera app too, which will open Discord, " -"which will then instruct you to scan it a 2nd time in the Discord app." +msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78 -msgid "" -"After confirming (in the Discord app) that you'd like to allow this " -"login, the bot should respond with \"Succcessfully authenticated as …\"" +msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\"" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 -msgid "" -"Now that you're logged in, you can send a `help` command to the bot " -"again, to see additional commands you have access to" +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 @@ -267,15 +189,11 @@ msgid "send `guilds status` to see the list of guilds" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83 -msgid "" -"for each guild that you'd like bridged, send `guilds bridge GUILD_ID " -"--entire`" +msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84 -msgid "" -"You may wish to uninstall the Discord app from your phone now. It's not " -"needed for the bridge to function." +msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86 @@ -283,10 +201,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90 @@ -294,32 +209,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100 @@ -327,26 +229,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108 -msgid "" -"make sure you don't log out the `Mautrix-Discord` device some time in the" -" future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po index 5981bd708..4ff5d1c8a 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 @@ -25,25 +25,15 @@ msgid "Setting up Mautrix Facebook bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3 -msgid "" -"**Note**: This bridge has been deprecated in favor of the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " -"can be installed using [this playbook](configuring-playbook-bridge-" -"mautrix-meta-messenger.md). Consider using that bridge instead of this " -"one." +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"facebook](https://github.com/mautrix/facebook) for you." +msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9 @@ -51,18 +41,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15 @@ -70,27 +53,19 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:23 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44 @@ -98,11 +73,7 @@ msgid "Using both would look like" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-facebook/defaults/main.yml` to find other things you would like " -"to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58 @@ -110,9 +81,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67 @@ -120,24 +89,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:73 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75 @@ -145,24 +105,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77 -msgid "" -"To use the bridge, you need to start a chat with " -"`@facebookbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79 -msgid "" -"Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable " -"bridging for your Facebook Messenger account. You can learn more here " -"about authentication from the bridge's [official documentation on " -"Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." +msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83 @@ -170,10 +121,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87 @@ -185,17 +133,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95 @@ -203,27 +145,19 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103 -msgid "" -"make sure you don't log out the `Mautrix-Facebook` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105 @@ -235,25 +169,15 @@ msgid "Facebook rejecting login attempts and forcing you to change password" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109 -msgid "" -"If your Matrix server is in a wildly different location than where you " -"usually use your Facebook account from, the bridge's login attempts may " -"be outright rejected by Facebook. Along with that, Facebook may even " -"force you to change the account's password." +msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111 -msgid "" -"If you happen to run into this problem while [setting up " -"bridging](#usage), try to first get a successful session up by logging in" -" to Facebook through the Matrix server's IP address." +msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113 -msgid "" -"The easiest way to do this may be to use " -"[sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic " -"through the Matrix server." +msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115 @@ -261,10 +185,7 @@ msgid "Example command for proxying your traffic through the Matrix server:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121 -msgid "" -"Once connected, you should be able to verify that you're browsing the web" -" through the Matrix server's IP by checking " -"[icanhazip](https://icanhazip.com/)." +msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123 @@ -276,11 +197,5 @@ msgid "Once logged in, proceed to [set up bridging](#usage)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127 -msgid "" -"If that doesn't work, enable 2FA (see: [Facebook help page on enabling " -"2FA](https://www.facebook.com/help/148233965247823)) and try to login " -"again with a new password, and entering the 2FA code when prompted, it " -"may take more then one try, in between attempts, check facebook.com to " -"see if they are requiring another password change" +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 4f2ae7fbf..befacc522 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 @@ -25,17 +25,11 @@ msgid "Setting up Mautrix Google Messages bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"gmessages](https://github.com/mautrix/gmessages) for you, for bridging to" -" [Google Messages](https://messages.google.com/)." +msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7 @@ -43,18 +37,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13 @@ -62,9 +49,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:21 @@ -72,9 +57,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30 @@ -82,24 +65,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:36 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38 @@ -107,10 +81,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40 -msgid "" -"To use the bridge, you need to start a chat with " -"`@gmessagesbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42 @@ -118,10 +89,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46 @@ -133,17 +101,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54 @@ -151,26 +113,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62 -msgid "" -"make sure you don't log out the `Mautrix-gmessages` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po index 6176e5ec0..adf3e0f3b 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 @@ -25,16 +25,11 @@ msgid "Setting up Mautrix Google Chat bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"googlechat](https://github.com/mautrix/googlechat) for you." +msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/googlechat/index.html)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7 @@ -42,19 +37,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13 @@ -62,10 +49,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15 -msgid "" -"To enable the [Google Chat](https://chat.google.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21 @@ -73,9 +57,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30 @@ -83,24 +65,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:36 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38 @@ -108,38 +81,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40 -msgid "" -"To use the bridge, you need to start a chat with `googlechat bridge bot` " -"with handle `@googlechatbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42 -msgid "" -"Send `login` to the bridge bot to receive a link to the portal from which" -" you can enable the bridging. Open the link sent by the bot and follow " -"the instructions." +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44 -msgid "" -"Automatic login may not work. If it does not, reload the page and select " -"the \"Manual login\" checkbox before starting. Manual login involves " -"logging into your Google account normally and then manually getting the " -"OAuth token from browser cookies with developer tools." +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46 -msgid "" -"Once logged in, recent chats should show up as new conversations " -"automatically. Other chats will get portals as you receive messages." +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48 -msgid "" -"You can learn more about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50 @@ -147,10 +105,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54 @@ -158,32 +113,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64 @@ -191,26 +133,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72 -msgid "" -"make sure you don't log out the `Mautrix-googlechat` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po index 167839731..0aca553fe 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 @@ -25,25 +25,15 @@ msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3 -msgid "" -"💡 **Note**: This bridge has been deprecated in favor of [Google Chat " -"bridge](https://github.com/mautrix/googlechat), which can be installed " -"using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md)." -" Installing the mautrix-hangouts bridge is **no longer possible**. For " -"now, this documentation page remains here for historical purposes." +msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"hangouts](https://github.com/mautrix/hangouts) for you." +msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9 @@ -51,18 +41,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Shared Secret Auth](configuring-playbook-shared-secret-" -"auth.md) for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15 @@ -70,10 +53,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17 -msgid "" -"To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23 @@ -81,9 +61,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32 @@ -91,24 +69,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40 @@ -116,38 +85,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42 -msgid "" -"To use the bridge, you need to start a chat with `Hangouts bridge bot` " -"with handle `@hangoutsbot:example.com` (where `example.com` is your base " -"domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44 -msgid "" -"Send `login` to the bridge bot to receive a link to the portal from which" -" you can enable the bridging. Open the link sent by the bot and follow " -"the instructions." +msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46 -msgid "" -"Automatic login may not work. If it does not, reload the page and select " -"the \"Manual login\" checkbox before starting. Manual login involves " -"logging into your Google account normally and then manually getting the " -"OAuth token from browser cookies with developer tools." +msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48 -msgid "" -"Once logged in, recent chats should show up as new conversations " -"automatically. Other chats will get portals as you receive messages." +msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50 -msgid "" -"You can learn more about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." +msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52 @@ -155,10 +109,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56 @@ -170,17 +121,11 @@ msgid "Method 1: automatically, by enabling Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service is configured and " -"enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64 @@ -188,26 +133,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72 -msgid "" -"make sure you don't log out the `Mautrix-Hangouts` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po index 85ea7a1ae..6072174c9 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 @@ -25,25 +25,15 @@ msgid "Setting up Mautrix Instagram bridging (optional, deprecated)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3 -msgid "" -"**Note**: This bridge has been deprecated in favor of the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which " -"can be installed using [this playbook](configuring-playbook-bridge-" -"mautrix-meta-instagram.md). Consider using that bridge instead of this " -"one." +msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"instagram](https://github.com/mautrix/instagram) for you." +msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/instagram/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9 @@ -51,35 +41,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:17 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following to your `vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29 -msgid "" -"If you would like to be able to administrate the bridge from your account" -" it can be configured like this:" +msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-instagram/defaults/main.yml` to find other things you would like " -"to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45 @@ -87,9 +65,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54 @@ -97,24 +73,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:60 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62 @@ -122,22 +89,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64 -msgid "" -"To use the bridge, you need to start a chat with " -"`@instagrambot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66 -msgid "" -"Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the " -"bridge bot to enable bridging for your instagram/Messenger account." +msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68 -msgid "" -"You can learn more here about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po index b17ea6ba8..71919b61e 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 @@ -25,30 +25,15 @@ msgid "Setting up Instagram bridging via Mautrix Meta (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3 -msgid "" -"The playbook can install and configure the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " -"you." +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5 -msgid "" -"Since this bridge component can bridge to both " -"[Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/) and you may wish to do both at the " -"same time, the playbook makes it available via 2 different Ansible roles " -"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" -"instagram`). The latter is a reconfigured copy of the first one (created " -"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" -"instagram.sh`)." +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7 -msgid "" -"This documentation page only deals with the bridge's ability to bridge to" -" Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger" -" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" -"messenger.md)." +msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9 @@ -60,18 +45,11 @@ msgid "Migrating from the old mautrix-instagram bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13 -msgid "" -"If you've been using the [mautrix-instagram](./configuring-playbook-" -"bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first**" -" or the 2 bridges will be in conflict:" +msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15 -msgid "" -"both trying to use `@instagrambot:example.com` as their username. This " -"conflict may be resolved by adjusting " -"`matrix_mautrix_instagram_appservice_bot_username` or " -"`matrix_mautrix_meta_instagram_appservice_username`" +msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16 @@ -79,17 +57,11 @@ msgid "both trying to bridge the same DMs" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18 -msgid "" -"To do so, send a `clean-rooms` command to the management room with the " -"old bridge bot (`@instagrambot:example.com`). It gives you a list of " -"portals and groups of portals you may purge. Proceed with sending " -"commands like `clean recommended`, etc." +msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20 -msgid "" -"Then, consider disabling the old bridge in your configuration, so it " -"won't recreate the portals when you receive new messages." +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22 @@ -97,18 +69,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:26 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28 @@ -116,15 +81,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:36 -msgid "" -"Before proceeding to [re-running the playbook](./installing.md), you may " -"wish to adjust the configuration further. See below." +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38 @@ -152,37 +113,23 @@ msgid "`admin` - Use and administer the bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48 -msgid "" -"The permissions are following the sequence: nothing < `relay` < `user` < " -"`admin`." +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50 -msgid "" -"The default permissions are set via " -"`matrix_mautrix_meta_instagram_bridge_permissions_default` and are " -"somewhat like this:" +msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59 -msgid "" -"If you don't define the `matrix_admin` in your configuration (e.g. " -"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61 -msgid "" -"You may redefine " -"`matrix_mautrix_meta_instagram_bridge_permissions_default` any way you " -"see fit, or add extra permissions using " -"`matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" +msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" -"instagram/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70 @@ -190,9 +137,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79 @@ -200,24 +145,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:85 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87 @@ -225,10 +161,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89 -msgid "" -"To use the bridge, you need to start a chat with " -"`@instagrambot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91 @@ -236,10 +169,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95 @@ -251,17 +181,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103 @@ -269,27 +193,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111 -msgid "" -"make sure you don't log out the session for which you obtained an access " -"token some time in the future, as that would break the Double Puppeting " -"feature" +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po index 55a8a3868..ed1a47c96 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 @@ -25,30 +25,15 @@ msgid "Setting up Messenger bridging via Mautrix Meta (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3 -msgid "" -"The playbook can install and configure the [mautrix-" -"meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for " -"you." +msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5 -msgid "" -"Since this bridge component can bridge to both " -"[Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/) and you may wish to do both at the " -"same time, the playbook makes it available via 2 different Ansible roles " -"(`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-" -"instagram`). The latter is a reconfigured copy of the first one (created " -"by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-" -"instagram.sh`)." +msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7 -msgid "" -"This documentation page only deals with the bridge's ability to bridge to" -" Facebook Messenger. For bridging to Instagram, see [Setting up Instagram" -" bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-" -"instagram.md)." +msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9 @@ -60,34 +45,19 @@ msgid "Migrating from the old mautrix-facebook bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13 -msgid "" -"If you've been using the [mautrix-facebook](./configuring-playbook-" -"bridge-mautrix-facebook.md) bridge, it's possible to migrate the database" -" using [instructions from the bridge " -"documentation](https://docs.mau.fi/bridges/go/meta/facebook-" -"migration.html) (advanced)." +msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15 -msgid "" -"Then you may wish to get rid of the Facebook bridge. To do so, send a " -"`clean-rooms` command to the management room with the old bridge bot " -"(`@facebookbot:example.com`). It gives you a list of portals and groups " -"of portals you may purge. Proceed with sending commands like `clean " -"recommended`, etc." +msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17 -msgid "" -"Then, consider disabling the old bridge in your configuration, so it " -"won't recreate the portals when you receive new messages." +msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19 -msgid "" -"**Note**: the user ID of the new bridge bot is " -"`@messengerbot:example.com`, not `@facebookbot:example.com`. After " -"disabling the old bridge, its bot user will stop responding to a command." +msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21 @@ -95,18 +65,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:25 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27 @@ -114,15 +77,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:35 -msgid "" -"Before proceeding to [re-running the playbook](./installing.md), you may " -"wish to adjust the configuration further. See below." +msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37 @@ -130,9 +89,7 @@ msgid "Bridge mode" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39 -msgid "" -"As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) " -"bridge supports multiple modes of operation." +msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41 @@ -144,36 +101,19 @@ msgid "(`facebook`) Facebook via `facebook.com`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44 -msgid "" -"(`facebook-tor`) Facebook via " -"`facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` " -"([Tor](https://www.torproject.org/)) - does not currently proxy media " -"downloads" +msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45 -msgid "" -"(default) (`messenger`) Messenger via `messenger.com` - usable even " -"without a Facebook account" +msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47 -msgid "" -"You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode`" -" variable. The playbook defaults to the `messenger` mode, because it's " -"most universal (every Facebook user has a Messenger account, but the " -"opposite is not true)." +msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49 -msgid "" -"Note that switching the mode (especially between `facebook*` and " -"`messenger`) will intentionally make the bridge use another database " -"(`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to " -"isolate the 2 instances. Switching between Tor and non-Tor may be " -"possible without dataloss, but your mileage may vary. Before switching to" -" a new mode, you may wish to de-configure the old one (send `help` to the" -" bridge bot and unbridge your portals, etc.)." +msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51 @@ -201,37 +141,23 @@ msgid "`admin` - Use and administer the bridge" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61 -msgid "" -"The permissions are following the sequence: nothing < `relay` < `user` < " -"`admin`." +msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63 -msgid "" -"The default permissions are set via " -"`matrix_mautrix_meta_messenger_bridge_permissions_default` and are " -"somewhat like this:" +msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72 -msgid "" -"If you don't define the `matrix_admin` in your configuration (e.g. " -"`matrix_admin: @alice:example.com`), then there's no admin by default." +msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74 -msgid "" -"You may redefine " -"`matrix_mautrix_meta_messenger_bridge_permissions_default` any way you " -"see fit, or add extra permissions using " -"`matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" +msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-" -"messenger/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83 @@ -239,9 +165,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92 @@ -249,24 +173,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:98 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100 @@ -274,26 +189,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102 -msgid "" -"To use the bridge, you need to start a chat with " -"`@messengerbot:example.com` (where `example.com` is your base domain, not" -" the `matrix.` domain). Note that the user ID of the bridge's bot is not " -"`@facebookbot:example.com`." +msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104 -msgid "" -"You then need to send a `login` command and follow the bridge bot's " -"instructions." +msgid "You then need to send a `login` command and follow the bridge bot's instructions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106 -msgid "" -"Given that the bot is configured in `messenger` [bridge mode](#bridge-" -"mode) by default, you will need to log in to " -"[messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain " -"the cookies from there as per [the bridge's authentication " -"instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." +msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108 @@ -301,10 +205,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112 @@ -316,17 +217,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120 @@ -334,27 +229,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128 -msgid "" -"make sure you don't log out the session for which you obtained an access " -"token some time in the future, as that would break the Double Puppeting " -"feature" +msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po index 3912c9f1f..529fb825d 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 @@ -25,23 +25,15 @@ msgid "Setting up Mautrix Signal bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"signal](https://github.com/mautrix/signal) for you." +msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/signal/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7 -msgid "" -"**Note**: This revamped version of the [mautrix-signal (legacy" -")](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU " -"usage of your homeserver." +msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9 @@ -53,18 +45,11 @@ msgid "Prepare Postgres database on external Postgres server" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13 -msgid "" -"If you're running with the Postgres database server integrated by the " -"playbook (which is the default), you don't need to do anything special " -"and can easily proceed with installing." +msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15 -msgid "" -"However, if you're [using an external Postgres server](configuring-" -"playbook-external-postgres.md), you'd need to manually prepare a Postgres" -" database for this bridge and adjust the variables related to that " -"(`matrix_mautrix_signal_database_*`)." +msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17 @@ -72,18 +57,11 @@ msgid "Enable Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:21 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23 @@ -91,15 +69,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:31 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue." +msgid "There are some additional things you may wish to configure about the bridge before you continue." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33 @@ -123,9 +97,7 @@ msgid "admin - Use and administer the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41 -msgid "" -"The permissions are following the sequence: nothing < relay < user < " -"admin." +msgid "The permissions are following the sequence: nothing < relay < user < admin." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43 @@ -133,29 +105,19 @@ msgid "The default permissions are set as follows:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51 -msgid "" -"If you want to augment the preset permissions, you might want to set the " -"additional permissions with the following settings in your `vars.yml` " -"file:" +msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60 -msgid "" -"This will add the admin permission to the specific user, while keeping " -"the default permissions." +msgid "This will add the admin permission to the specific user, while keeping the default permissions." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62 -msgid "" -"In case you want to replace the default permissions settings " -"**completely**, populate the following item within your `vars.yml` file:" +msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"signal/templates/config.yaml.j2` to find more information on the " -"permissions settings and other options you would like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72 @@ -163,9 +125,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81 @@ -173,24 +133,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:87 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89 @@ -198,9 +149,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91 -msgid "" -"To use the bridge, you need to start a chat with `@signalbot:example.com`" -" (where `example.com` is your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93 @@ -208,10 +157,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97 @@ -223,17 +169,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105 @@ -241,26 +181,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113 -msgid "" -"make sure you don't log out the `Mautrix-Signal` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po index 439a8b7d5..0ba7b089c 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 @@ -25,48 +25,27 @@ msgid "Setting up Mautrix Slack bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3 -msgid "" -"**Note**: bridging to [Slack](https://slack.com/) can also happen via the" -" [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) bridges supported by the playbook." +msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4 -msgid "" -"For using as a Bot we recommend the [Appservice Slack](configuring-" -"playbook-bridge-appservice-slack.md), because it supports plumbing. Note " -"that it is not available for new installation unless you have already " -"created a classic Slack application, because the creation of classic " -"Slack applications, which this bridge makes use of, has been " -"discontinued." +msgid "For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5 -msgid "" -"For personal use with a slack account we recommend the `mautrix-slack` " -"bridge (the one being discussed here), because it is the most fully-" -"featured and stable of the 3 Slack bridges supported by the playbook." +msgid "For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7 -msgid "" -"The playbook can install and configure [mautrix-" -"slack](https://github.com/mautrix/slack) for you." +msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn" -" what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:11 -msgid "" -"See the [features and " -"roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more " -"information." +msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:13 @@ -74,19 +53,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15 -msgid "" -"For using this bridge, you would need to authenticate by **providing your" -" username and password** (legacy) or by using a **token login**. See more" -" information in the " -"[docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." +msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:17 -msgid "" -"Note that neither of these methods are officially supported by Slack. " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) uses a Slack bot account which is the only officially supported" -" method for bridging a Slack channel." +msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:19 @@ -94,18 +65,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:23 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25 @@ -113,16 +77,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:33 -msgid "" -"You may optionally wish to add some [Additional configuration" -"](#additional-configuration), or to [prepare for double-puppeting](#set-" -"up-double-puppeting) before the initial installation." +msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35 @@ -130,9 +89,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37 -msgid "" -"There are some additional options you may wish to configure with the " -"bridge." +msgid "There are some additional options you may wish to configure with the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39 @@ -140,17 +97,11 @@ msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41 -msgid "" -"`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some " -"variables that you can customize via your `vars.yml` file" +msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42 -msgid "" -"`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for " -"the bridge's default configuration. You can override settings (even those" -" that don't have dedicated playbook variables) using the " -"`matrix_mautrix_slack_configuration_extension_yaml` variable" +msgid "`roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_slack_configuration_extension_yaml` variable" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44 @@ -158,9 +109,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53 @@ -168,24 +117,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61 @@ -193,36 +133,23 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63 -msgid "" -"Start a chat with `@slackbot:example.com` (where `example.com` is your " -"base domain, not the `matrix.` domain)." +msgid "Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:64 -msgid "" -"If you would like to login to Slack using a token, send the `login-token`" -" command, otherwise, send the `login-password` command. Read " -"[here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how " -"to retrieve your token and cookie token." +msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65 -msgid "" -"The bot should respond with \"Successfully logged into for team " -"\"" +msgid "The bot should respond with \"Successfully logged into for team \"" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 -msgid "" -"Now that you're logged in, you can send a `help` command to the bot " -"again, to see additional commands you have access to." +msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 -msgid "" -"Slack channels should automatically begin bridging if you authenticated " -"using a token. Otherwise, you must wait to receive a message in the " -"channel if you used password authentication." +msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69 @@ -230,10 +157,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73 @@ -245,17 +169,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81 @@ -263,26 +181,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89 -msgid "" -"make sure you don't log out the `Mautrix-Slack` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po index 601653ed9..0415d7248 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 @@ -25,16 +25,11 @@ msgid "Setting up Mautrix Telegram bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"telegram](https://github.com/mautrix/telegram) for you." +msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/python/telegram/index.html) " -"to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7 @@ -42,19 +37,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13 @@ -62,11 +49,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15 -msgid "" -"You'll need to obtain API keys from " -"[https://my.telegram.org/apps](https://my.telegram.org/apps) and then add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23 @@ -74,9 +57,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32 @@ -84,24 +65,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40 @@ -109,19 +81,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42 -msgid "" -"To use the bridge, you need to start a chat with " -"`@telegrambot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44 -msgid "" -"If you want to use the relay-bot feature ([relay bot " -"documentation](https://docs.mau.fi/bridges/python/telegram/relay-" -"bot.html)), which allows anonymous user to chat with telegram users, add " -"the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54 @@ -129,17 +93,11 @@ msgid "You might also want to give permissions to administrate the bot:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63 -msgid "" -"More details about permissions in this example: " -"https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-" -"config.yaml#L410" +msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65 -msgid "" -"If you like to exclude all groups from syncing and use the Telgeram-" -"Bridge only for direct chats, you can add the following additional " -"playbook configuration:" +msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71 @@ -147,10 +105,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75 @@ -158,32 +113,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85 @@ -191,32 +133,21 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87 -msgid "" -"**Note**: This method for enabling Double Puppeting can be configured " -"only after you've already set up bridging." +msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 -msgid "" -"send `login-matrix` to the bot and follow instructions about how to send " -"the access token to it" +msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95 -msgid "" -"make sure you don't log out the `Mautrix-Telegram` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po index badc8ae74..e05a23047 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 @@ -25,23 +25,15 @@ msgid "Setting up Mautrix Twitter bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3 -msgid "" -"**Note**: bridging to [Twitter](https://twitter.com/) can also happen via" -" the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-" -"twitter.md) bridge supported by the playbook." +msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5 -msgid "" -"The playbook can install and configure [mautrix-" -"twitter](https://github.com/mautrix/twitter) for you." +msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/twitter/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9 @@ -53,18 +45,11 @@ msgid "Enable Appservice Double Puppet (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:15 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17 @@ -72,9 +57,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:25 @@ -82,9 +65,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34 @@ -92,24 +73,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:40 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42 @@ -117,22 +89,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44 -msgid "" -"You then need to start a chat with `@twitterbot:example.com` (where " -"`example.com` is your base domain, not the `matrix.` domain)." +msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45 -msgid "" -"Send login-cookie to start the login. The bot should respond with " -"instructions on how to proceed." +msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47 -msgid "" -"You can learn more here about authentication from the bridge's [official " -"documentation on " -"Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." +msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49 @@ -140,10 +105,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53 @@ -155,17 +117,11 @@ msgid "Method 1: automatically, by enabling Appservice Double Puppet" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61 @@ -173,89 +129,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69 -msgid "" -"make sure you don't log out the `Mautrix-Slack` device some time in the " -"future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/mautrix/twitter) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ msgstr "" - -#~ 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 "" - -#~ msgid "" -#~ "Method 1: automatically, by enabling " -#~ "Appservice Double Puppet or Shared " -#~ "Secret Auth" -#~ msgstr "" - -#~ msgid "" -#~ "The bridge automatically performs Double " -#~ "Puppeting if [Appservice Double Puppet" -#~ "](configuring-playbook-appservice-double-" -#~ "puppet.md) or [Shared Secret Auth" -#~ "](configuring-playbook-shared-secret-auth.md) " -#~ "service is configured and enabled on " -#~ "the server for this playbook." -#~ msgstr "" - -#~ msgid "" -#~ "Enabling [Appservice Double Puppet](configuring-" -#~ "playbook-appservice-double-puppet.md) is " -#~ "the recommended way of setting up " -#~ "Double Puppeting, as it's easier to " -#~ "accomplish, works for all your users " -#~ "automatically, and has less of a " -#~ "chance of breaking in the future." -#~ msgstr "" - -#~ msgid "" -#~ "Enabling double puppeting by enabling " -#~ "the [Shared Secret Auth](configuring-" -#~ "playbook-shared-secret-auth.md) service " -#~ "works at the time of writing, but" -#~ " is deprecated and will stop working" -#~ " in the future." -#~ msgstr "" - -#~ msgid "" -#~ "This method is currently not available" -#~ " for the Mautrix-Twitter bridge, but" -#~ " is on the " -#~ "[roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md)" -#~ " under Misc/Manual login with `login-" -#~ "matrix`" -#~ 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 dbcd9512a..db8a16cff 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 @@ -25,16 +25,11 @@ msgid "Setting up Mautrix Whatsapp bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"whatsapp](https://github.com/mautrix/whatsapp) for you." +msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5 -msgid "" -"See the project's " -"[documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to " -"learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7 @@ -42,19 +37,11 @@ msgid "Prerequisite (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9 -msgid "" -"If you want to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do) for this bridge automatically, you need to " -"have enabled [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-" -"secret-auth.md) service for this playbook." +msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:11 -msgid "" -"For details about configuring Double Puppeting for this bridge, see the " -"section below: [Set up Double Puppeting](#-set-up-double-puppeting)" +msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13 @@ -62,34 +49,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:21 -msgid "" -"Whatsapp multidevice beta is required, now it is enough if Whatsapp is " -"connected to the Internet every 2 weeks." +msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23 -msgid "" -"The relay bot functionality is off by default. If you would like to " -"enable the relay bot, add the following to your `vars.yml` file:" +msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29 -msgid "" -"By default, only admins are allowed to set themselves as relay users. To " -"allow anyone on your homeserver to set themselves as relay users add this" -" to your `vars.yml` file:" +msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35 -msgid "" -"If you want to activate the relay bot in a room, send `!wa set-relay`. To" -" deactivate, send `!wa unset-relay`." +msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37 @@ -97,9 +73,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46 @@ -107,24 +81,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:52 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54 @@ -132,10 +97,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56 -msgid "" -"To use the bridge, you need to start a chat with " -"`@whatsappbot:example.com` (where `example.com` is your base domain, not " -"the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58 @@ -143,10 +105,7 @@ msgid "💡 Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60 -msgid "" -"After successfully enabling bridging, you may wish to set up [Double " -"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) " -"(hint: you most likely do)." +msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62 @@ -154,32 +113,19 @@ msgid "To set it up, you have 2 ways of going about it." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64 -msgid "" -"Method 1: automatically, by enabling Appservice Double Puppet or Shared " -"Secret Auth" +msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66 -msgid "" -"The bridge automatically performs Double Puppeting if [Appservice Double " -"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared " -"Secret Auth](configuring-playbook-shared-secret-auth.md) service is " -"configured and enabled on the server for this playbook." +msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68 -msgid "" -"Enabling [Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md) is the recommended way of setting up Double Puppeting, " -"as it's easier to accomplish, works for all your users automatically, and" -" has less of a chance of breaking in the future." +msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70 -msgid "" -"Enabling double puppeting by enabling the [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) service works at the time " -"of writing, but is deprecated and will stop working in the future." +msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72 @@ -187,26 +133,17 @@ msgid "Method 2: manually, by asking each user to provide a working access token msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74 -msgid "" -"When using this method, **each user** that wishes to enable Double " -"Puppeting needs to follow the following steps:" +msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 -msgid "" -"retrieve a Matrix access token for yourself. Refer to the documentation " -"on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 -msgid "" -"send the access token to the bot. Example: `login-matrix " -"MATRIX_ACCESS_TOKEN_HERE`" +msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80 -msgid "" -"make sure you don't log out the `Mautrix-Whatsapp` device some time in " -"the future, as that would break the Double Puppeting feature" +msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po index 16822cbfc..ff93dfd70 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 @@ -21,22 +21,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1 -msgid "" -"Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage " -"(optional)" +msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3 -msgid "" -"The playbook can install and configure [mautrix-" -"wsproxy](https://github.com/mautrix/wsproxy) for you." +msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5 -msgid "" -"See the project's " -"[documentation](https://github.com/mautrix/wsproxy/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7 @@ -44,16 +37,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:21 -msgid "" -"Note that the tokens must match what is compiled into the [mautrix-" -"imessage](https://github.com/mautrix/imessage) bridge running on your Mac" -" or Android device." +msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23 @@ -61,23 +49,15 @@ msgid "Adjusting the wsproxy URL" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25 -msgid "" -"By default, this playbook installs wsproxy on the `wsproxy.` subdomain " -"(`wsproxy.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27 -msgid "" -"By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can " -"easily make the service available at a **different hostname** than the " -"default one." +msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36 @@ -85,15 +65,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the wsproxy domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40 -msgid "" -"By default, you will need to create a CNAME record for `wsproxy`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42 @@ -101,10 +77,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:51 @@ -112,24 +85,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:55 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:57 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59 @@ -137,16 +101,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61 -msgid "" -"Follow the [matrix-imessage " -"documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for " -"running `android-sms` and/or `matrix-imessage` on your device(s)." +msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)." msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/mautrix/wsproxy#readme) to" -#~ " learn what it does and why it" -#~ " might be useful to you." -#~ 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 715823a51..be69ce8ad 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 @@ -25,38 +25,23 @@ msgid "Setting up MX Puppet Discord bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3 -msgid "" -"**Note**: bridging to [Discord](https://discordapp.com/) can also happen " -"via the [matrix-appservice-discord](configuring-playbook-bridge-" -"appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-" -"mautrix-discord.md) bridges supported by the playbook." +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." +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." +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." +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." +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 @@ -64,10 +49,7 @@ 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:" +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 @@ -75,9 +57,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +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 @@ -85,24 +65,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -110,18 +81,11 @@ 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)." +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." +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 @@ -129,18 +93,9 @@ 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." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 4381c17cf..7b9c350c6 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 @@ -25,17 +25,11 @@ msgid "Setting up MX Puppet GroupMe bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for " -"you." +msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5 -msgid "" -"See the project's [documentation](https://gitlab.com/xangelix-pub/matrix" -"/mx-puppet-groupme/blob/master/README.md) to learn what it does and why " -"it might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7 @@ -43,10 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9 -msgid "" -"To enable the [GroupMe](https://groupme.com/) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15 @@ -54,9 +45,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24 @@ -64,24 +53,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32 @@ -89,10 +69,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34 -msgid "" -"To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` " -"with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is" -" your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36 @@ -100,31 +77,17 @@ msgid "One authentication method is available." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38 -msgid "" -"To link your GroupMe account, go to " -"[dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access" -" Token\" from the top menu. Copy the token and message the bridge with:" +msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44 -msgid "" -"Once logged in, send `listrooms` to the bot user to list the available " -"rooms." +msgid "Once logged in, send `listrooms` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 450c385de..d58429322 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 @@ -25,9 +25,7 @@ msgid "Setting up MX Puppet Instagram bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." +msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5 @@ -39,10 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9 -msgid "" -"To enable the [Instagram](https://www.instagram.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +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 @@ -50,9 +45,7 @@ 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:" +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 @@ -60,24 +53,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -85,22 +69,15 @@ 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)." +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." +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." +msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40 @@ -108,9 +85,7 @@ 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)" +msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43 @@ -118,20 +93,13 @@ 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)" +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." +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 "" -"The `help` command shows which commands are available, though at the time" -" of writing, not every command is fully implemented." +msgid "The `help` command shows which commands are available, though 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 5b094b2c3..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 @@ -25,17 +25,9 @@ msgid "Setting up MX Puppet Skype bridging (optional, removed)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3 -msgid "" -"The playbook used to be able to install and configure [mx-puppet-" -"skype](https://github.com/Sorunome/mx-puppet-skype), but no longer " -"includes this component, because it has been broken and unmaintained for " -"a long time." +msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5 -msgid "" -"Bridging to [Skype](https://www.skype.com/) can also happen via the [go-" -"skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge " -"supported by the playbook." +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 80130e822..e0cc1584d 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 @@ -25,28 +25,15 @@ msgid "Setting up MX Puppet Slack bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3 -msgid "" -"**Note**: bridging to [Slack](https://slack.com) can also happen via the " -"[matrix-appservice-slack](configuring-playbook-bridge-appservice-" -"slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-" -"slack.md) bridges supported by the playbook. Note that `matrix-" -"appservice-slack` is not available for new installation unless you have " -"already created a classic Slack application, because the creation of " -"classic Slack applications, which this bridge makes use of, has been " -"discontinued." +msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5 -msgid "" -"The playbook can install and configure [mx-puppet-" -"slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." +msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7 -msgid "" -"See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-" -"puppet-slack/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9 @@ -54,10 +41,7 @@ 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`." +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 @@ -65,10 +49,7 @@ 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:" +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 @@ -76,9 +57,7 @@ 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:" +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 @@ -86,24 +65,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -111,18 +81,11 @@ 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)." +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." +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 @@ -130,18 +93,9 @@ 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." +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 "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 e95f4c70a..39037aabe 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 @@ -25,16 +25,11 @@ msgid "Setting up MX Puppet Steam bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3 -msgid "" -"The playbook can install and configure [mx-puppet-" -"steam](https://github.com/icewind1991/mx-puppet-steam) for you." +msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5 -msgid "" -"See the project's [documentation](https://github.com/icewind1991/mx-" -"puppet-steam/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7 @@ -42,10 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9 -msgid "" -"To enable the [Steam](https://steampowered.com/) bridge, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15 @@ -53,9 +45,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24 @@ -63,24 +53,15 @@ 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." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32 @@ -88,17 +69,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34 -msgid "" -"To use the bridge, you need to start a chat with `Steam Puppet Bridge` " -"with the handle `@_steampuppet_bot:example.com` (where `example.com` is " -"your base domain, not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36 -msgid "" -"Three authentication methods are available, Legacy Token, OAuth and xoxc " -"token. See mx-puppet-steam [documentation](https://github.com/icewind1991" -"/mx-puppet-steam) for more information about how to configure the bridge." +msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38 @@ -106,18 +81,9 @@ msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 1583475ca..405bfd428 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 @@ -25,23 +25,15 @@ 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." +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." +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." +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 @@ -49,9 +41,7 @@ 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)." +msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13 @@ -59,10 +49,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15 -msgid "" -"To enable the [Twitter](https://twitter.com) bridge, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +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 @@ -70,9 +57,7 @@ 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:" +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 @@ -80,24 +65,15 @@ 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." +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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 @@ -105,10 +81,7 @@ 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)." +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 @@ -120,18 +93,9 @@ msgid "Once logged in, send `list` to the bot user to list the available rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51 -msgid "" -"Clicking rooms in the list will result in you receiving an invitation to " -"the bridged room." +msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room." msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 msgid "Also send `help` to the bot to see the commands available." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index 7bc3831ab..87c74e8c5 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -25,29 +25,19 @@ msgid "Setting up Postmoogle email bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:3 -msgid "" -"**Note**: email bridging can also happen via the [email2matrix" -"](configuring-playbook-email2matrix.md) bridge supported by the playbook." +msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:5 -msgid "" -"The playbook can install and configure " -"[Postmoogle](https://github.com/etkecc/postmoogle) for you." +msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:7 -msgid "" -"Postmoogle is a bridge you can use to have its bot user forward emails to" -" Matrix rooms. It runs an SMTP email server and allows you to assign " -"mailbox addresses to the rooms." +msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:9 -msgid "" -"See the project's " -"[documentation](https://github.com/etkecc/postmoogle/blob/master/README.md)" -" to learn what it does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:11 @@ -55,9 +45,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:13 -msgid "" -"Open the following ports on your server to be able to receive incoming " -"emails:" +msgid "Open the following ports on your server to be able to receive incoming emails:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:15 @@ -69,18 +57,11 @@ msgid "`587/tcp`: Submission (TLS-encrypted SMTP)" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:18 -msgid "" -"If you don't open these ports, you will still be able to send emails, but" -" not receive any." +msgid "If you don't open these ports, you will still be able to send emails, but not receive any." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:20 -msgid "" -"These port numbers are configurable via the " -"`matrix_postmoogle_smtp_host_bind_port` and " -"`matrix_postmoogle_submission_host_bind_port` variables, but other email " -"servers will try to deliver on these default (standard) ports, so " -"changing them is of little use." +msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:22 @@ -88,9 +69,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:24 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:45 @@ -98,10 +77,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:47 -msgid "" -"You will also need to add several DNS records so that Postmoogle can send" -" emails. See [Configuring DNS](configuring-dns.md) for details about DNS " -"changes." +msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:49 @@ -109,9 +85,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:51 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:58 @@ -119,34 +93,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:60 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create a user account of the bridge's bot." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:62 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:64 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:66 -msgid "" -"If you change the bridge's bot password (`matrix_postmoogle_password` in " -"your `vars.yml` file) subsequently, the bot user's credentials on the " -"homeserver won't be updated automatically. If you'd like to change the " -"bot user's password, use a tool like [synapse-admin](configuring-" -"playbook-synapse-admin.md) to change it, and then update " -"`matrix_postmoogle_password` to let the bot know its new password." +msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:68 @@ -154,28 +113,19 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:70 -msgid "" -"To use the bridge, invite the `@postmoogle:example.com` bot user into a " -"room you want to use as a mailbox." +msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:72 -msgid "" -"Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with " -"the email address `NAME@matrix.example.com`. Emails sent to that email " -"address will be forwarded to the room." +msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 -msgid "" -"Send `!pm help` to the room to see the bridge's help menu for additional " -"commands." +msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 -msgid "" -"You can also refer to the upstream " -"[documentation](https://github.com/etkecc/postmoogle)." +msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:78 @@ -183,23 +133,9 @@ msgid "Debug/Logs" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:80 -msgid "" -"As with all other services, you can find their logs in [systemd-" -"journald](https://www.freedesktop.org/software/systemd/man/systemd-" -"journald.service.html) by running something like `journalctl -fu matrix-" -"postmoogle`" +msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`" msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:82 -msgid "" -"The default logging level for this bridge is `INFO`, but you can increase" -" it to `DEBUG` with the following additional configuration:" +msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/etkecc/postmoogle) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 6fd0059f3..40bd7b501 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 @@ -25,17 +25,11 @@ msgid "Setting up WeChat bridging (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:3 -msgid "" -"The playbook can install and configure the [matrix-" -"wechat](https://github.com/duo/matrix-wechat) bridge for you (for " -"bridging to the [WeChat](https://www.wechat.com/) network)." +msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:5 -msgid "" -"See the project's [documentation](https://github.com/duo/matrix-" -"wechat/blob/master/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:7 @@ -43,9 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:15 @@ -53,9 +45,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:17 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:24 @@ -63,24 +53,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:26 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:32 @@ -88,18 +69,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:34 -msgid "" -"Once the bridge is installed, start a chat with `@wechatbot:example.com` " -"(where `example.com` is your base domain, not the `matrix.` domain)." +msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bridge-wechat.md:36 msgid "Send `help` to the bot to see the available commands." msgstr "" - -#~ msgid "" -#~ "See the project page to learn what" -#~ " it does and why it might be" -#~ " useful to you." -#~ 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 e0ba16d7c..15d9c546e 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 @@ -25,41 +25,27 @@ msgid "Setting up Cactus Comments (optional)" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:3 -msgid "" -"The playbook can install and configure the [Cactus " -"Comments](https://cactus.chat) system for you." +msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:5 -msgid "" -"Cactus Comments is a **federated comment system** built on Matrix. It " -"respects your privacy, and puts you in control." +msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:7 -msgid "" -"See the project's [documentation](https://cactus.chat/docs/getting-" -"started/introduction/) to learn what it does and why it might be useful " -"to you." +msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:9 -msgid "" -"The playbook contains 2 roles for configuring different pieces of the " -"Cactus Comments system:" +msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:11 -msgid "" -"`matrix-cactus-comments` - the backend appservice integrating with the " -"Matrix homeserver" +msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:13 -msgid "" -"`matrix-cactus-comments-client` - a static website server serving the " -"[cactus-client](https://cactus.chat/docs/client/introduction/) static " -"assets (`cactus.js` and `styles.css`)" +msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:15 @@ -71,9 +57,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:19 -msgid "" -"To enable Cactus Comments, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:41 @@ -81,26 +65,15 @@ msgid "Adjusting the Cactus Comments' client URL" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:43 -msgid "" -"By default, this playbook installs Cactus Comments' client on the " -"`matrix.` subdomain, at the `/cactus-comments` path " -"(https://matrix.example.com/cactus-comments). This makes it easy to " -"install it, because it **doesn't require additional DNS records to be set" -" up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:45 -msgid "" -"By tweaking the `matrix_cactus_comments_client_hostname` and " -"`matrix_cactus_comments_client_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:47 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:56 @@ -108,10 +81,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:58 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Cactus Comments' client domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:60 @@ -119,9 +89,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:62 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:64 @@ -129,10 +97,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:66 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:73 @@ -140,24 +105,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:75 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:77 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:79 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:81 @@ -165,22 +121,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:83 -msgid "" -"Upon starting Cactus Comments, a `bot.cactusbot` user account is created " -"automatically." +msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:85 -msgid "" -"To get started, send a `help` message to the `@bot.cactusbot:example.com`" -" bot to confirm it's working." +msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:87 -msgid "" -"Then, register a site by sending `register ` (where " -"`` is a unique identifier you choose. It does not have to " -"match your domain). You will then be invited into a moderation room." +msgid "Then, register a site by sending `register ` (where `` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:89 @@ -192,23 +141,15 @@ msgid "Embed Cactus Comments" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:93 -msgid "" -"The official [documentation](https://cactus.chat/docs/getting-started" -"/quick-start/) provides a useful guide to embed Cactus Comments on your " -"website." +msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:95 -msgid "" -"After including the JavaScript and CSS asset files, insert a `
` " -"where you'd like to display the comment section:" +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:101 -msgid "" -"Then, you need to initialize the comment section. Make sure to replace " -"`example.com` with your base domain and `` with the one " -"that has been registered above:" +msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `` with the one that has been registered above:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:115 @@ -216,22 +157,13 @@ msgid "Adjust the domain name for self-hosting" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:117 -msgid "" -"To have the assets served from your homeserver (not from `cactus.chat`), " -"you need to adjust the domain name on the official documentation." +msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:119 -msgid "" -"Make sure to replace `example.com` with your base domain before you " -"include the following lines, instead of the one provided by the official " -"documentation:" +msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:" msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:126 -msgid "" -"**Note**: if the `matrix_cactus_comments_client_hostname` and " -"`matrix_cactus_comments_client_path_prefix` variables are tweaked, you " -"would need to adjust the URLs of the assets accordingly." +msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po index 2368b3e4f..8e8c3fdad 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 @@ -25,30 +25,19 @@ msgid "Setting up Cinny (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:3 -msgid "" -"This playbook can install the [Cinny](https://github.com/ajbura/cinny) " -"Matrix web client for you." +msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:5 -msgid "" -"Cinny is a web client focusing primarily on simple, elegant and secure " -"interface. It can be installed alongside or instead of [Element Web" -"](./configuring-playbook-client-element-web.md)." +msgid "Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md)." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:7 -msgid "" -"💡 **Note**: the latest version of Cinny is also available on the web, " -"hosted by 3rd parties. If you trust giving your credentials to the " -"following 3rd party Single Page Applications, you can consider using it " -"from there and avoiding the (small) overhead of self-hosting:" +msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:9 -msgid "" -"[app.cinny.in](https://app.cinny.in), hosted by the " -"[Cinny](https://cinny.in/) developers" +msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:11 @@ -56,9 +45,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:13 -msgid "" -"To enable Cinny, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:19 @@ -66,32 +53,19 @@ msgid "Adjusting the Cinny URL" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:21 -msgid "" -"By default, this playbook installs Cinny on the `cinny.` subdomain " -"(`cinny.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:23 -msgid "" -"By tweaking the `matrix_client_cinny_hostname` variable, you can easily " -"make the service available at a **different hostname** than the default " -"one." +msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:25 -msgid "" -"While a `matrix_client_cinny_path_prefix` variable exists for tweaking " -"the path-prefix, it's [not supported " -"anymore](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3701), because Cinny requires an application rebuild (with " -"a tweaked build config) to be functional under a custom path." +msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:27 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:34 @@ -99,21 +73,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:36 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the Cinny domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:38 -msgid "" -"By default, you will need to create a CNAME record for `cinny`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:40 -msgid "" -"If you've adjusted `matrix_client_cinny_hostname`, you will need to " -"adjust your DNS configuration accordingly." +msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly." msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:42 @@ -121,25 +89,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:44 -msgid "" -"After configuring the playbook and [adjusting your DNS records" -"](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:51 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-cinny.md:53 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po index d1ecdbd21..8ac70be44 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 @@ -25,25 +25,15 @@ msgid "Configuring Element Web (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:3 -msgid "" -"By default, this playbook installs the [Element Web](https://github.com" -"/element-hq/element-web) Matrix client for you. If that's okay, you can " -"skip this document." +msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:5 -msgid "" -"💡 **Note**: the latest version of Element Web is also available on the " -"web, hosted by 3rd parties. If you trust giving your credentials to the " -"following 3rd party Single Page Applications, you can consider using it " -"from there and avoiding the (small) overhead of self-hosting (by " -"[disabling Element Web](#disabling-element-web)):" +msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:7 -msgid "" -"[app.element.io](https://app.element.io/), hosted by " -"[Element](https://element.io/)" +msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:8 @@ -55,11 +45,7 @@ msgid "Disabling Element Web" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:12 -msgid "" -"If you'd like for the playbook to not install Element Web (or to " -"uninstall it if it was previously installed), add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:18 @@ -67,64 +53,31 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:20 -msgid "" -"The playbook provides some customization variables you could use to " -"change Element Web's settings." +msgid "The playbook provides some customization variables you could use to change Element Web's settings." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:22 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/element/config.json` file (on the server). This file is " -"generated from the [`roles/custom/matrix-client-" -"element/templates/config.json.j2`](../roles/custom/matrix-client-" -"element/templates/config.json.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:24 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:26 -msgid "" -"Alternatively, **if there is no pre-defined variable** for an Element Web" -" setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:28 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Element Web's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:30 -msgid "" -"or, you can **extend and override the default configuration** " -"([`config.json.j2`](../roles/custom/matrix-client-" -"element/templates/config.json.j2)) by making use of the " -"`matrix_client_element_configuration_extension_json_` variable. You can " -"find information about this in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:32 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_client_element_configuration_default` (or " -"`matrix_client_element_configuration`). You can find information about " -"this in [`roles/custom/matrix-client-" -"element/defaults/main.yml`](../roles/custom/matrix-client-" -"element/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:34 @@ -132,31 +85,19 @@ msgid "Themes" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:36 -msgid "" -"To change the look of Element Web, you can define your own themes " -"manually by using the " -"`matrix_client_element_setting_defaults_custom_themes` setting." +msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:38 -msgid "" -"Or better yet, you can automatically pull it all themes provided by the " -"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" -"themes) project by simply flipping a flag " -"(`matrix_client_element_themes_enabled: true`)." +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:40 -msgid "" -"If you make your own theme, we encourage you to submit it to the " -"**aaronraimist/element-themes** project, so that the whole community " -"could easily enjoy it." +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:42 -msgid "" -"Note that for a custom theme to work well, all Element Web instances that" -" you use must have the same theme installed." +msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:44 @@ -164,24 +105,15 @@ msgid "Adjusting the Element Web URL" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:46 -msgid "" -"By default, this playbook installs Element Web on the `element.` " -"subdomain (`element.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:48 -msgid "" -"By tweaking the `matrix_client_element_hostname` and " -"`matrix_client_element_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:50 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:61 @@ -189,21 +121,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:63 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Element Web domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:65 -msgid "" -"By default, you will need to create a CNAME record for `element`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:67 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:69 @@ -211,25 +137,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:71 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:78 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-element-web.md:80 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po index c4fe82ea3..bcdae88b9 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 @@ -25,15 +25,11 @@ msgid "Setting up Hydrogen (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:3 -msgid "" -"This playbook can install the [Hydrogen](https://github.com/element-hq" -"/hydrogen-web) Matrix web client for you." +msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:5 -msgid "" -"Hydrogen is a lightweight web client that supports mobile and legacy web " -"browsers. It can be installed alongside or instead of Element Web." +msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:7 @@ -41,9 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:9 -msgid "" -"To enable Hydrogen, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:15 @@ -51,24 +45,15 @@ msgid "Adjusting the Hydrogen URL" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:17 -msgid "" -"By default, this playbook installs Hydrogen on the `hydrogen.` subdomain " -"(`hydrogen.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:19 -msgid "" -"By tweaking the `matrix_client_hydrogen_hostname` and " -"`matrix_client_hydrogen_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:21 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:32 @@ -76,21 +61,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:34 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Hydrogen domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:36 -msgid "" -"By default, you will need to create a CNAME record for `hydrogen`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:38 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:40 @@ -98,25 +77,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:42 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:49 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-hydrogen.md:51 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po index 944601214..248053755 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 @@ -25,31 +25,19 @@ msgid "Setting up SchildiChat Web (optional)" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:3 -msgid "" -"This playbook can install the [SchildiChat " -"Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client " -"for you." +msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:5 -msgid "" -"SchildiChat Web is a feature-rich messenger for Matrix based on Element " -"Web with some extras and tweaks. It can be installed alongside or instead" -" of Element Web." +msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:7 -msgid "" -"💡 **Note**: the latest version of SchildiChat Web is also available on " -"the web, hosted by 3rd parties. If you trust giving your credentials to " -"the following 3rd party Single Page Application, you can consider using " -"it from there:" +msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:9 -msgid "" -"[app.schildi.chat](https://app.schildi.chat/), hosted by the " -"[SchildiChat](https://schildi.chat/) developers" +msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:11 @@ -57,70 +45,35 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:13 -msgid "" -"To enable SchildiChat Web, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:19 -msgid "" -"The playbook provides some customization variables you could use to " -"change SchildiChat Web's settings." +msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:21 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml) and they ultimately end up in the " -"generated `/matrix/schildichat/config.json` file (on the server). This " -"file is generated from the [`roles/custom/matrix-client-" -"schildichat/templates/config.json.j2`](../roles/custom/matrix-client-" -"schildichat/templates/config.json.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:23 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:25 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a SchildiChat " -"Web setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:27 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of SchildiChat Web's various" -" settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:29 -msgid "" -"or, you can **extend and override the default configuration** " -"([`config.json.j2`](../roles/custom/matrix-client-" -"schildichat/templates/config.json.j2)) by making use of the " -"`matrix_client_schildichat_configuration_extension_json_` variable. You " -"can find information about this in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:31 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_client_schildichat_configuration_default` (or " -"`matrix_client_schildichat_configuration`). You can find information " -"about this in [`roles/custom/matrix-client-" -"schildichat/defaults/main.yml`](../roles/custom/matrix-client-" -"schildichat/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:33 @@ -128,31 +81,19 @@ msgid "Themes" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:35 -msgid "" -"To change the look of SchildiChat Web, you can define your own themes " -"manually by using the " -"`matrix_client_schildichat_setting_defaults_custom_themes` setting." +msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:37 -msgid "" -"Or better yet, you can automatically pull it all themes provided by the " -"[aaronraimist/element-themes](https://github.com/aaronraimist/element-" -"themes) project by simply flipping a flag " -"(`matrix_client_schildichat_themes_enabled: true`)." +msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:39 -msgid "" -"If you make your own theme, we encourage you to submit it to the " -"**aaronraimist/element-themes** project, so that the whole community " -"could easily enjoy it." +msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:41 -msgid "" -"Note that for a custom theme to work well, all SchildiChat Web instances " -"that you use must have the same theme installed." +msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:43 @@ -160,24 +101,15 @@ msgid "Adjusting the SchildiChat Web URL" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:45 -msgid "" -"By default, this playbook installs SchildiChat Web on the `schildichat.` " -"subdomain (`schildichat.example.com`) and requires you to [adjust your " -"DNS records](#adjusting-dns-records)." +msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:47 -msgid "" -"By tweaking the `matrix_client_schildichat_hostname` and " -"`matrix_client_schildichat_path_prefix` variables, you can easily make " -"the service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:49 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:60 @@ -185,21 +117,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:62 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the SchildiChat Web domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:64 -msgid "" -"By default, you will need to create a CNAME record for `schildichat`. See" -" [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:66 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:68 @@ -207,25 +133,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:70 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:77 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-client-schildichat-web.md:79 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po index 4e013493d..d2b467cfa 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po @@ -25,10 +25,7 @@ msgid "Configuring Conduit (optional)" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, but you can also use " -"[Conduit](https://conduit.rs)." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:5 @@ -36,19 +33,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:7 -msgid "" -"**You can't switch an existing Matrix server's implementation** (e.g. " -"Synapse -> Conduit). Proceed below only if you're OK with losing data or " -"you're dealing with a server on a new domain name, which hasn't " -"participated in the Matrix federation yet." +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:9 -msgid "" -"**homeserver implementations other than Synapse may not be fully " -"functional**. The playbook may also not assist you in an optimal way " -"(like it does with Synapse). Make yourself familiar with the downsides " -"before proceeding" +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:11 @@ -56,9 +45,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:13 -msgid "" -"To use Conduit, you **generally** need to add the following configuration" -" to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:19 @@ -66,32 +53,19 @@ msgid "Creating the first user account" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:21 -msgid "" -"Since it is difficult to create the first user account on Conduit (see " -"[famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) " -"and " -"[famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354))" -" and it does not support [registering users](registering-users.md) (via " -"the command line or via the playbook) like Synapse and Dendrite do, we " -"recommend the following procedure:" +msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:23 -msgid "" -"Add `matrix_conduit_allow_registration: true` to your `vars.yml` the " -"first time around, temporarily" +msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:24 -msgid "" -"Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags" -"=setup-all,start` - see [Installing](installing.md))" +msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:25 -msgid "" -"Create your first user via Element Web or any other client which supports" -" creating users" +msgid "Create your first user via Element Web or any other client which supports creating users" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:26 @@ -99,15 +73,11 @@ msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml` msgstr "" #: ../../../docs/configuring-playbook-conduit.md:27 -msgid "" -"Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=setup-conduit,start` would be enough this time)" +msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:28 -msgid "" -"You can now use your server safely. Additional users can be created by " -"messaging the internal Conduit bot" +msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:30 @@ -115,23 +85,13 @@ msgid "Configuring bridges / appservices" msgstr "" #: ../../../docs/configuring-playbook-conduit.md:32 -msgid "" -"Automatic appservice setup is currently unsupported when using Conduit. " -"After setting up the service as usual you may notice that it is unable to" -" start." +msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:34 -msgid "" -"You will have to manually register appservices using the the [register-" -"appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md)" -" command." +msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command." msgstr "" #: ../../../docs/configuring-playbook-conduit.md:36 -msgid "" -"Find the `registration.yaml` in the `/matrix` directory, for example " -"`/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content " -"to Conduit:" +msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po index d371a0775..ad5a7c023 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po @@ -25,10 +25,7 @@ msgid "Configuring Dendrite (optional)" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, but you can also use " -"[Dendrite](https://github.com/matrix-org/dendrite)." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:5 @@ -36,19 +33,11 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:7 -msgid "" -"**You can't switch an existing Matrix server's implementation** (e.g. " -"Synapse -> Dendrite). Proceed below only if you're OK with losing data or" -" you're dealing with a server on a new domain name, which hasn't " -"participated in the Matrix federation yet." +msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:9 -msgid "" -"**homeserver implementations other than Synapse may not be fully " -"functional**. The playbook may also not assist you in an optimal way " -"(like it does with Synapse). Make yourself familiar with the downsides " -"before proceeding" +msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:11 @@ -56,71 +45,35 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:13 -msgid "" -"To use Dendrite, you **generally** need to add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:19 -msgid "" -"The playbook provides lots of customization variables you could use to " -"change Dendrite's settings." +msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:21 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/dendrite/config/dendrite.yaml` file (on the server). This file " -"is generated from the [`roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:23 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:25 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a Dendrite " -"setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:27 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Dendrite's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:29 -msgid "" -"or, you can **extend and override the default configuration** " -"([`dendrite.yaml.j2`](../roles/custom/matrix-" -"dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the " -"`matrix_dendrite_configuration_extension_yaml` variable. You can find " -"information about this in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:31 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_dendrite_configuration` (or " -"`matrix_dendrite_configuration_yaml`). You can find information about " -"this in [`roles/custom/matrix-" -"dendrite/defaults/main.yml`](../roles/custom/matrix-" -"dendrite/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:33 @@ -128,24 +81,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:35 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:42 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dendrite.md:44 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po index f4423b101..ed1278ad1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po @@ -25,34 +25,15 @@ msgid "Setting up Dimension integration manager (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:3 -msgid "" -"**[Dimension](https://dimension.t2bot.io) can only be installed after " -"Matrix services are installed and running.** If you're just installing " -"Matrix services for the first time, please continue with the " -"[Configuration](configuring-playbook.md) / [Installation](installing.md) " -"flow and come back here later." +msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:5 -msgid "" -"**Note**: Dimension is **[officially " -"unmaintained](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering" -" with installing it." +msgid "**Note**: 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:7 -msgid "" -"**Note**: This playbook now supports running " -"[Dimension](https://dimension.t2bot.io) in both a federated and " -"[unfederated](https://github.com/turt2live/matrix-" -"dimension/blob/master/docs/unfederated.md) environments. This is handled " -"automatically based on the value of " -"`matrix_homeserver_federation_enabled`. Enabling Dimension, means that " -"the `openid` API endpoints will be exposed on the Matrix Federation port " -"(usually `8448`), even if [federation](configuring-playbook-" -"federation.md) is disabled. It's something to be aware of, especially in " -"terms of firewall whitelisting (make sure port `8448` is accessible)." +msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:9 @@ -60,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:11 -msgid "" -"To enable Dimension, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:17 @@ -70,18 +49,11 @@ msgid "Define admin users" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:19 -msgid "" -"These users can modify the integrations this Dimension supports. Add this" -" to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:27 -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." +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:29 @@ -89,37 +61,23 @@ msgid "Access token" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:31 -msgid "" -"We recommend that you create a dedicated Matrix user for Dimension " -"(`dimension` is a good username). Follow our [Registering users" -"](registering-users.md) guide to learn how to register **a regular (non-" -"admin) user**." +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:33 -msgid "" -"You are required to specify an access token (belonging to this new user) " -"for Dimension to work. To get an access token for the Dimension user, you" -" can follow the documentation on [how to do obtain an access token" -"](obtaining-access-tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:35 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:37 -msgid "" -"Add access token to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:43 -msgid "" -"For more information on how to acquire an access token, visit " -"[https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." +msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:45 @@ -127,32 +85,19 @@ msgid "Adjusting the Dimension URL" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:47 -msgid "" -"By default, this playbook installs Dimension on the `dimension.` " -"subdomain (`dimension.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:49 -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." +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:51 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:62 -msgid "" -"**Note**: While there is a `matrix_dimension_path_prefix` variable for " -"changing the path where Dimension is served, overriding it is not " -"possible due to [this Dimension issue](https://github.com/turt2live" -"/matrix-dimension/issues/510). You must serve Dimension at a dedicated " -"subdomain." +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:64 @@ -160,15 +105,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:66 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Dimension domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:68 -msgid "" -"By default, you will need to create a CNAME record for `dimension`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:70 @@ -176,10 +117,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dimension.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:" +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:79 @@ -187,28 +125,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:81 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +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:83 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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:85 -msgid "" -"After Dimension has been installed you may need to log out and log back " -"in for it to pick up the new integration manager. Then you can access " -"integrations in Element Web by opening a room, clicking the Room info " -"button (`i`) button in the top right corner of the screen, and then " -"clicking Add widgets, bridges & bots." +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:87 @@ -216,23 +141,11 @@ msgid "Jitsi domain" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:89 -msgid "" -"By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as " -"the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video " -"conference widgets. For users running [a self-hosted Jitsi instance" -"](./configuring-playbook-jitsi.md), you will likely want the widget to " -"use your own Jitsi instance. Currently there is no way to configure this " -"via the playbook, see [this issue](https://github.com/turt2live/matrix-" -"dimension/issues/345) for details." +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:91 -msgid "" -"In the interim until the above limitation is resolved, an admin user " -"needs to configure the domain via the admin ui once dimension is running." -" In Element Web, go to *Manage Integrations* → *Settings* " -"→ *Widgets* → *Jitsi Conference Settings* and set " -"*Jitsi Domain* and *Jitsi Script URL* appropriately." +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:93 @@ -240,19 +153,9 @@ msgid "Additional features" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:95 -msgid "" -"To use a more custom configuration, you can define a " -"`matrix_dimension_configuration_extension_yaml` string variable and put " -"your configuration in it. To learn more about how to do this, refer to " -"the information about `matrix_dimension_configuration_extension_yaml` in " -"the [default variables file](../roles/custom/matrix-" -"dimension/defaults/main.yml) of the Dimension component." +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:97 -msgid "" -"You can find all configuration options on [GitHub page of Dimension " -"project](https://github.com/turt2live/matrix-" -"dimension/blob/master/config/default.yaml)." +msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po index 1a8304187..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 @@ -25,18 +25,11 @@ msgid "Setting up Dynamic DNS (optional)" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:3 -msgid "" -"The playbook can configure Dynamic DNS with " -"[ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl " -"client used to update dynamic DNS entries for accounts on Dynamic DNS " -"Network Service Provider." +msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:5 -msgid "" -"Most cloud providers / ISPs will charge you extra for a static IP " -"address. If you're not hosting a highly reliable homeserver you can " -"workaround this via dynamic DNS." +msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:7 @@ -44,9 +37,7 @@ msgid "Prerequisite" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:9 -msgid "" -"You'll need to get a username and password from your DNS provider. Please" -" consult with the provider about how to retrieve them." +msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:11 @@ -54,9 +45,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:13 -msgid "" -"To enable dynamic DNS, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:26 @@ -64,25 +53,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:35 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:37 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:39 @@ -96,4 +75,3 @@ msgstr "" #: ../../../docs/configuring-playbook-dynamic-dns.md:43 msgid "https://matrix.org/docs/guides/free-small-matrix-server" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po index 0efaa7bf5..cbccf36f9 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po @@ -25,37 +25,23 @@ msgid "Adjusting email-sending settings (optional)" msgstr "" #: ../../../docs/configuring-playbook-email.md:3 -msgid "" -"By default, this playbook sets up an [Exim](https://www.exim.org/) email " -"server through which all Matrix services send emails." +msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails." msgstr "" #: ../../../docs/configuring-playbook-email.md:5 -msgid "" -"The email server would attempt to deliver emails directly to their final " -"destination. This may or may not work, depending on your domain " -"configuration (SPF settings, etc.)" +msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)" msgstr "" #: ../../../docs/configuring-playbook-email.md:7 -msgid "" -"By default, emails are sent from `matrix@matrix.example.com`, as " -"specified by the `exim_relay_sender_address` playbook variable." +msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable." msgstr "" #: ../../../docs/configuring-playbook-email.md:9 -msgid "" -"⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is" -" always blocked](https://cloud.google.com/compute/docs/tutorials/sending-" -"mail/), so sending email directly from your server is not possible. You " -"will need to [relay email through another SMTP server](#relaying-email-" -"through-another-smtp-server)." +msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)." msgstr "" #: ../../../docs/configuring-playbook-email.md:11 -msgid "" -"💡 To improve deliverability, we recommend [relaying email through another" -" SMTP server](#relaying-email-through-another-smtp-server) anyway." +msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway." msgstr "" #: ../../../docs/configuring-playbook-email.md:13 @@ -63,10 +49,7 @@ msgid "Firewall settings" msgstr "" #: ../../../docs/configuring-playbook-email.md:15 -msgid "" -"No matter whether you send email directly (the default) or you relay " -"email through another host (see how below), you'll probably need to allow" -" outgoing traffic for TCP ports 25/587 (depending on configuration)." +msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)." msgstr "" #: ../../../docs/configuring-playbook-email.md:17 @@ -74,18 +57,11 @@ msgid "Relaying email through another SMTP server" msgstr "" #: ../../../docs/configuring-playbook-email.md:19 -msgid "" -"If you'd like to relay email through another SMTP server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email.md:31 -msgid "" -"**Note**: only the secure submission protocol (using `STARTTLS`, usually " -"on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port " -"`465`) **is not supported**." +msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**." msgstr "" #: ../../../docs/configuring-playbook-email.md:33 @@ -93,26 +69,15 @@ msgid "Configuations for sending emails using Sendgrid" msgstr "" #: ../../../docs/configuring-playbook-email.md:35 -msgid "" -"An easy and free SMTP service to set up is " -"[Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 " -"emails per day to be sent. In the settings below you can provide any " -"email for `exim_relay_sender_address`." +msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`." msgstr "" #: ../../../docs/configuring-playbook-email.md:37 -msgid "" -"The only other thing you need to change is the " -"`exim_relay_relay_auth_password`, which you can generate at " -"https://app.sendgrid.com/settings/api_keys. The API key password looks " -"something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-" -"6zkdwrPP8bOeuI`." +msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`." msgstr "" #: ../../../docs/configuring-playbook-email.md:39 -msgid "" -"Note that the `exim_relay_relay_auth_username` is literally the string " -"`apikey`, it's always the same for Sendgrid." +msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid." msgstr "" #: ../../../docs/configuring-playbook-email.md:51 @@ -120,8 +85,5 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-email.md:53 -msgid "" -"If you're having trouble with email not being delivered, it may be useful" -" to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." +msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index 8b73bae84..129b07f5c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po @@ -25,24 +25,15 @@ msgid "Setting up Email2Matrix (optional)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:3 -msgid "" -"**Note**: email bridging can also happen via the [Postmoogle" -"](configuring-playbook-bridge-postmoogle.md) bridge supported by the " -"playbook. Postmoogle is much more powerful and easier to use, so we " -"recommend that you use it, instead of Email2Matrix." +msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:5 -msgid "" -"The playbook can install and configure " -"[email2matrix](https://github.com/devture/email2matrix) for you." +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." +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 @@ -54,11 +45,7 @@ msgid "DNS configuration" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:13 -msgid "" -"It's not strictly necessary, but you may increase the chances that " -"incoming emails reach your server by adding an `MX` record for " -"`matrix.example.com`, as described in the [Configuring DNS](configuring-" -"dns.md) documentation page." +msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:15 @@ -66,31 +53,19 @@ msgid "Port availability" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:17 -msgid "" -"Ensure that port 25 is available on your Matrix server and open in your " -"firewall." +msgid "Ensure that port 25 is available on your Matrix server and open in your firewall." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:19 -msgid "" -"If you have `postfix` or some other email server software installed, you " -"may need to manually remove it first (unless you need it, of course)." +msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:21 -msgid "" -"If you really need to run an email server on the Matrix machine for other" -" purposes, it may be possible to run Email2Matrix on another port (with a" -" configuration like `matrix_email2matrix_smtp_host_bind_port: " -"\"127.0.0.01:2525\"`) and have your other email server relay messages " -"there." +msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:23 -msgid "" -"For details about using Email2Matrix alongside " -"[Postfix](http://www.postfix.org/), see " -"[here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." +msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:25 @@ -98,18 +73,11 @@ msgid "Creating a user" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:27 -msgid "" -"Before enabling Email2Matrix, you'd most likely wish to create a " -"dedicated user (or more) that would be sending messages on the Matrix " -"side. 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." +msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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:29 -msgid "" -"Refer to [Registering users](registering-users.md) for ways to create a " -"user. A regular (non-admin) user works best." +msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:31 @@ -117,17 +85,11 @@ msgid "Creating a shared room" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:33 -msgid "" -"After creating the sender user, you should create one or more Matrix " -"rooms that you share with that user. It doesn't matter who creates and " -"owns the rooms and who joins later (you or the sender user)." +msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:35 -msgid "" -"What matters is that both you and the sender user are part of the same " -"room and that the sender user has enough privileges in the room to be " -"able to send messages there." +msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:37 @@ -135,10 +97,7 @@ msgid "Inviting additional people to the room is okay too." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:39 -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." +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:41 @@ -146,11 +105,7 @@ msgid "Obtaining an access token for the sender user" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 -msgid "" -"In order for the sender user created above to be able to send messages to" -" the room, we'll need to obtain an access token for it. Refer to the " -"documentation on [how to obtain an access token](obtaining-access-" -"tokens.md)." +msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:45 @@ -158,10 +113,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:47 -msgid "" -"After doing the preparation steps above, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to " -"your needs):" +msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:72 @@ -169,31 +121,19 @@ msgid "where:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:74 -msgid "" -"MailboxName - local-part of the email address, through which emails are " -"bridged to the room whose ID is defined with MatrixRoomId" +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:75 -msgid "" -"MatrixRoomId - internal ID of the room, to which received emails are sent" -" as Matrix message" +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:76 -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" +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:77 -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)" +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:78 @@ -209,15 +149,11 @@ msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matri msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:81 -msgid "" -"SkipMarkdown - if set to \"true\", emails are bridged as plain text " -"Matrix message instead of Markdown (actually HTML)" +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:83 -msgid "" -"Refer to the official documentation " -"[here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:85 @@ -225,9 +161,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:94 @@ -235,50 +169,13 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:96 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service email2matrix` or `just setup-all`" +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:98 -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." +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:100 -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." +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 "" - -#~ msgid "" -#~ "To enable Email2Matrix, run the playbook" -#~ " with [playbook tags](playbook-tags.md) as" -#~ " below:" -#~ msgstr "" - -#~ msgid "" -#~ "The shortcut commands with the [`just`" -#~ " program](just.md) are also available: " -#~ "`just run-tags setup-email2matrix,start` " -#~ "or `just setup-all`" -#~ msgstr "" - -#~ msgid "" -#~ "`just run-tags setup-email2matrix,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 "" - 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 b8ea886cf..4afdc7bb9 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po @@ -25,18 +25,11 @@ msgid "Setting up Etherpad (optional)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:3 -msgid "" -"[Etherpad](https://etherpad.org) is an open source collaborative text " -"editor that can be embedded in a Matrix chat room using the [Dimension " -"integration manager](https://dimension.t2bot.io) or used as standalone " -"web app." +msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:5 -msgid "" -"When enabled together with the Jitsi audio/video conferencing system (see" -" [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made " -"available as an option during the conferences." +msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:7 @@ -44,9 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:9 -msgid "" -"To enable Etherpad, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:19 @@ -54,23 +45,15 @@ msgid "Adjusting the Etherpad URL" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:21 -msgid "" -"By default, this playbook installs Etherpad on the `etherpad.` subdomain " -"(`etherpad.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:23 -msgid "" -"By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables," -" you can easily make the service available at a **different hostname " -"and/or path** than the default one." +msgid "By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:25 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:36 @@ -78,21 +61,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:38 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Etherpad domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:40 -msgid "" -"By default, you will need to create a CNAME record for `etherpad`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:42 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:44 @@ -100,10 +77,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:46 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:53 @@ -111,35 +85,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:55 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the Etherpad admin user (`etherpad_admin_username`)." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:61 -msgid "" -"If you change the Etherpad admin user's password " -"(`etherpad_admin_password` in your `vars.yml` file) subsequently, the " -"admin user's credentials on the homeserver won't be updated " -"automatically. If you'd like to change the admin user's password, use a " -"tool like [synapse-admin](configuring-playbook-synapse-admin.md) to " -"change it, and then update `etherpad_admin_password` to let the admin " -"user know its new password." +msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:63 @@ -147,17 +105,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:65 -msgid "" -"The Etherpad UI should be available at `https://etherpad.example.com`, " -"while the admin UI (if enabled) should then be available at " -"`https://etherpad.example.com/admin`." +msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:67 -msgid "" -"If you've [decided on another hostname or path-prefix](#adjusting-the-" -"etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these " -"URLs accordingly before usage." +msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:69 @@ -165,38 +117,23 @@ msgid "Managing / Deleting old pads" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:71 -msgid "" -"If you want to manage and remove old unused pads from Etherpad, you will " -"first need to able Admin access as described above." +msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:73 -msgid "" -"Then from the plugin manager page " -"(`https://etherpad.example.com/admin/plugins`, install the `adminpads2` " -"plugin. Once installed, you should have a \"Manage pads\" section in the " -"Admin web-UI." +msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:75 -msgid "" -"How to use Etherpad widgets without an integration manager (like " -"Dimension)" +msgid "How to use Etherpad widgets without an integration manager (like Dimension)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:77 -msgid "" -"This is how it works in Element Web, it might work quite similar with " -"other clients:" +msgid "This is how it works in Element Web, it might work quite similar with other clients:" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:79 -msgid "" -"To integrate a standalone Etherpad in a room, create your pad by visiting" -" `https://etherpad.example.com`. When the pad opens, copy the URL and " -"send a command like this to the room: `/addwidget URL`. You will then " -"find your integrated Etherpad within the right sidebar in the `Widgets` " -"section." +msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:81 @@ -204,17 +141,11 @@ msgid "Set Dimension default to the self-hosted Etherpad (optional)" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:83 -msgid "" -"If you decided to install [Dimension integration manager](configuring-" -"playbook-dimension.md) alongside Etherpad, the Dimension administrator " -"users can configure the default URL template." +msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:85 -msgid "" -"The Dimension configuration menu can be accessed with the sprocket icon " -"as you begin to add a widget to a room in Element Web. There you will " -"find the Etherpad Widget Configuration action beneath the _Widgets_ tab." +msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:87 @@ -222,9 +153,7 @@ msgid "Removing the integrated Etherpad chat" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:89 -msgid "" -"If you wish to disable the Etherpad chat button, you can do it by " -"appending `?showChat=false` to the end of the pad URL, or the template." +msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:91 @@ -236,15 +165,9 @@ msgid "Known issues" msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:95 -msgid "" -"If your Etherpad widget fails to load, this might be due to Dimension " -"generating a Pad name so long, the Etherpad app rejects it." +msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it." msgstr "" #: ../../../docs/configuring-playbook-etherpad.md:97 -msgid "" -"`$roomId_$padName` can end up being longer than 50 characters. You can " -"avoid having this problem by altering the template so it only contains " -"the three word random identifier `$padName`." +msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po index e732065fb..e9472e140 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po @@ -25,56 +25,25 @@ msgid "Using an external PostgreSQL server (optional)" msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:3 -msgid "" -"By default, this playbook would set up a PostgreSQL database server on " -"your machine, running in a Docker container. If that's okay, you can skip" -" this document." +msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:5 -msgid "" -"**Note**: using **an external Postgres server is currently [not very " -"seamless](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/1682#issuecomment-1061461683) when it comes to enabling " -"various other playbook services** - you will need to create a new " -"database/credentials for each service and to point each service to its " -"corresponding database using custom `vars.yml` configuration. **For the " -"best experience with the playbook, stick to using the integrated Postgres" -" server**." +msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:7 -msgid "" -"If you'd like to use an external Postgres server that you manage, add the" -" following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:23 -msgid "" -"The database (as specified in `matrix_synapse_database_database`) must " -"exist and be accessible with the given credentials. It must be empty or " -"contain a valid Synapse database. If empty, Synapse would populate it the" -" first time it runs." +msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:25 -msgid "" -"**Note**: the external server that you specify in " -"`matrix_synapse_database_host` must be accessible from within the " -"`matrix-synapse` Docker container (and possibly other containers too). " -"This means that it either needs to be a publicly accessible hostname or " -"that it's a hostname on the same Docker network where all containers " -"installed by this playbook run (a network called `matrix` by default). " -"Using a local PostgreSQL instance on the host (running on the same " -"machine, but not in a container) is not possible." +msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible." msgstr "" #: ../../../docs/configuring-playbook-external-postgres.md:27 -msgid "" -"The connection to your external Postgres server **will not be SSL " -"encrypted**, as [we don't support that yet](https://github.com/spantaleev" -"/matrix-docker-ansible-deploy/issues/89)." +msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po index 8056411de..2df5135eb 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po @@ -25,23 +25,11 @@ msgid "Controlling Matrix federation (optional)" msgstr "" #: ../../../docs/configuring-playbook-federation.md:3 -msgid "" -"By default, your server federates with the whole Matrix network. That is," -" people on your server can communicate with people on any other Matrix " -"server." +msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server." msgstr "" #: ../../../docs/configuring-playbook-federation.md:5 -msgid "" -"**Note**: in the sample `vars.yml` " -"([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a " -"short user ID like `@alice:example.com` instead of " -"`@alice:matrix.example.com` and set up [server delegation](howto-server-" -"delegation.md) / redirection. Without a proper configuration, your server" -" will effectively not be part of the Matrix network. If you find your " -"server is not federated, make sure to [check whether services work" -"](maintenance-checking-services.md) and your server is properly " -"delegated." +msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated." msgstr "" #: ../../../docs/configuring-playbook-federation.md:7 @@ -49,17 +37,11 @@ msgid "Federating only with select servers" msgstr "" #: ../../../docs/configuring-playbook-federation.md:9 -msgid "" -"To make your server only federate with servers of your choosing, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:17 -msgid "" -"If you wish to disable federation, you can do that with an empty list " -"(`[]`), or better yet by completely disabling federation (see below)." +msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)." msgstr "" #: ../../../docs/configuring-playbook-federation.md:19 @@ -67,15 +49,11 @@ msgid "Exposing the room directory over federation" msgstr "" #: ../../../docs/configuring-playbook-federation.md:21 -msgid "" -"By default, your server's public rooms directory is not exposed to other " -"servers via federation." +msgid "By default, your server's public rooms directory is not exposed to other servers via federation." msgstr "" #: ../../../docs/configuring-playbook-federation.md:23 -msgid "" -"If you wish to expose it, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:29 @@ -83,56 +61,29 @@ msgid "Disabling federation" msgstr "" #: ../../../docs/configuring-playbook-federation.md:31 -msgid "" -"To completely disable federation, isolating your server from the rest of " -"the Matrix network, add this to your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-federation.md:37 -msgid "" -"With that, your server's users will only be able to talk among " -"themselves, but not to anyone who is on another server." +msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server." msgstr "" #: ../../../docs/configuring-playbook-federation.md:39 -msgid "" -"**Disabling federation does not necessarily disable the federation port**" -" (`8448`). Services like [Dimension](configuring-playbook-dimension.md) " -"and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs" -" exposed on that port. Even if you disable federation and only if " -"necessary, we may still be exposing the federation port and serving the " -"`openid` APIs there. To override this and completely disable Synapse's " -"federation port use:" +msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:" msgstr "" #: ../../../docs/configuring-playbook-federation.md:51 -msgid "" -"Changing the federation port from 8448 to a different port to use a CDN " -"that only accepts 443/80 ports" +msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports" msgstr "" #: ../../../docs/configuring-playbook-federation.md:53 -msgid "" -"Why? This change could be useful for people running small Synapse " -"instances on small severs/VPSes to avoid being impacted by a simple " -"DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your " -"hosting provider does not provide a DOS/DDOS protection." +msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection." msgstr "" #: ../../../docs/configuring-playbook-federation.md:55 -msgid "" -"The following changes in the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and " -"make it possible to proxy the federation through a CDN such as CloudFlare" -" or any other:" +msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:" msgstr "" #: ../../../docs/configuring-playbook-federation.md:66 -msgid "" -"**Use this at you own risk as all the possible side-effects of doing this" -" are not fully known. However, it has been tested and works fine and " -"passes all the tests on without " -"issues.**" +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 e695de50c..5ce63d953 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po @@ -25,23 +25,15 @@ msgid "Setting up the Jitsi video-conferencing platform (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:3 -msgid "" -"The playbook can install the [Jitsi](https://jitsi.org/) video-" -"conferencing platform and integrate it with Element clients ([Element Web" -"](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." +msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:5 -msgid "" -"Jitsi installation is **not enabled by default**, because it's not a core" -" component of Matrix services." +msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:7 -msgid "" -"The setup done by the playbook is very similar to [docker-jitsi-" -"meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the " -"documentation there for many of the options here." +msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:9 @@ -57,12 +49,7 @@ msgid "`4443/tcp` - RTP media fallback over TCP" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:14 -msgid "" -"`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, " -"incoming RTP packets on port `10000` may have the external IP of your " -"firewall as destination address, due to the usage of STUN in JVB (see " -"[`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting" -"/ansible-role-jitsi/blob/main/defaults/main.yml))." +msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:16 @@ -70,9 +57,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:18 -msgid "" -"To enable Jitsi, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:24 @@ -80,22 +65,15 @@ msgid "Adjusting the Jitsi URL" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:26 -msgid "" -"By default, this playbook installs Jitsi on the `jitsi.` subdomain " -"(`jitsi.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:28 -msgid "" -"By tweaking the `jitsi_hostname` variable, you can easily make the " -"service available at a **different hostname** than the default one." +msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:30 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:37 @@ -103,15 +81,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:39 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Jitsi domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:41 -msgid "" -"By default, you will need to create a CNAME record for `jitsi`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:43 @@ -119,36 +93,23 @@ msgid "(Optional) Configure Jitsi authentication and guests mode" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:45 -msgid "" -"By default the Jitsi Meet instance does not require any kind of login and" -" is open to use for anyone without registration." +msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:47 -msgid "" -"If you're fine with such an open Jitsi instance, please skip to " -"[Installing](#installing)." +msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:49 -msgid "" -"If you would like to control who is allowed to open meetings on your new " -"Jitsi instance, then please follow the following steps to enable Jitsi's " -"authentication and optionally guests mode." +msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:51 -msgid "" -"Currently, there are three supported authentication modes: 'internal' " -"(default), 'matrix' and 'ldap'." +msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:53 -msgid "" -"**Note**: Authentication is not tested via the playbook's self-checks. We" -" therefore recommend that you manually verify if authentication is " -"required by jitsi. For this, try to manually create a conference on " -"jitsi.example.com in your browser." +msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:55 @@ -156,35 +117,19 @@ msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:57 -msgid "" -"The default authentication mechanism is 'internal' auth, which requires " -"jitsi-accounts to be setup and is the recommended setup, as it also works" -" in federated rooms. With authentication enabled, all meeting rooms have " -"to be opened by a registered user, after which guests are free to join. " -"If a registered host is not yet present, guests are put on hold in " -"individual waiting rooms." +msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:59 -msgid "" -"Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml`" -" configuration:" +msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:71 -msgid "" -"**Caution**: Accounts added here and subsequently removed will not be " -"automatically removed from the Prosody server until user account cleaning" -" is integrated into the playbook." +msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:73 -msgid "" -"**If you get an error** like this: \"Error: Account creation/modification" -" not supported.\", it's likely that you had previously installed Jitsi " -"without auth/guest support. In such a case, you should look into " -"[Rebuilding your Jitsi installation](#rebuilding-your-jitsi-" -"installation)." +msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:75 @@ -192,18 +137,11 @@ msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:77 -msgid "" -"**Attention: Probably breaks Jitsi in federated rooms and does not allow " -"sharing conference links with guests.**" +msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:79 -msgid "" -"Using this authentication type require a [Matrix User Verification " -"Service](https://github.com/matrix-org/matrix-user-verification-service)." -" By default, this playbook creates and configures a user-verification-" -"service to run locally, see [configuring-user-verification-service" -"](configuring-playbook-user-verification-service.md)." +msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:81 @@ -211,10 +149,7 @@ msgid "To enable set this configuration at host level:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:89 -msgid "" -"For more information see also [https://github.com/matrix-org/prosody-mod-" -"auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-" -"auth-matrix-user-verification)." +msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:91 @@ -226,11 +161,7 @@ msgid "An example LDAP configuration could be:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:113 -msgid "" -"For more information refer to the [docker-jitsi-" -"meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-" -"ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs" -"/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." +msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:115 @@ -238,20 +169,11 @@ msgid "(Optional) Making your Jitsi server work on a LAN" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:117 -msgid "" -"By default the Jitsi Meet instance does not work with a client in LAN " -"(Local Area Network), even if others are connected from WAN. There are no" -" video and audio. In the case of WAN to WAN everything is ok." +msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:119 -msgid "" -"The reason is the Jitsi VideoBridge git to LAN client the IP address of " -"the docker image instead of the host. The " -"[documentation](https://jitsi.github.io/handbook/docs/devops-guide" -"/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of " -"Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment " -"variable to make it work." +msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:121 @@ -259,9 +181,7 @@ msgid "Here is how to do it in the playbook." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:123 -msgid "" -"Add these two lines to your " -"`inventory/host_vars/matrix.example.com/vars.yml` configuration:" +msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:130 @@ -269,42 +189,23 @@ msgid "(Optional) Fine tune Jitsi" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:132 -msgid "" -"Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` " -"configuration to save up resources (explained below):" +msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:147 -msgid "" -"You may want to **suspend unused video layers** until they are requested " -"again, to save up resources on both server and clients. Read more on this" -" feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-" -"feature/)" +msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:149 -msgid "" -"You may wish to **disable audio levels** to avoid excessive refresh of " -"the client-side page and decrease the CPU consumption involved." +msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:151 -msgid "" -"You may want to **limit the number of video feeds forwarded to each " -"client**, to save up resources on both server and clients. As clients’ " -"bandwidth and CPU may not bear the load, use this setting to avoid lag " -"and crashes. This feature is found by default in other webconference " -"applications such as Office 365 Teams (limit is set to 4). Read how it " -"works [here](https://github.com/jitsi/jitsi-" -"videobridge/blob/master/doc/last-n.md) and performance evaluation on this" -" [study](https://jitsi.org/wp-" -"content/uploads/2016/12/nossdav2015lastn.pdf)." +msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:153 -msgid "" -"You may want to **limit the maximum video resolution**, to save up " -"resources on both server and clients." +msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:155 @@ -312,15 +213,11 @@ msgid "(Optional) Specify a Max number of participants on a Jitsi conference" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:157 -msgid "" -"The playbook allows a user to set a max number of participants allowed to" -" join a Jitsi conference. By default there is no limit." +msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:159 -msgid "" -"In order to set the max number of participants use the following " -"**additional** configuration:" +msgid "In order to set the max number of participants use the following **additional** configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:165 @@ -328,73 +225,39 @@ msgid "(Optional) Additional JVBs" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:167 -msgid "" -"By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi" -"/jitsi-videobridge)) is deployed on the same host as the Matrix server. " -"To allow more video-conferences to happen at the same time, you may need " -"to provision additional JVB services on other hosts." +msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:169 -msgid "" -"There is an ansible playbook that can be run with the following tag: " -"`ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers " -"jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" +msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:171 -msgid "" -"For this role to work you will need an additional section in the ansible " -"hosts file with the details of the JVB hosts, for example:" +msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:178 -msgid "" -"Each JVB will require a server ID to be set so that it can be uniquely " -"identified and this allows Jitsi to keep track of which conferences are " -"on which JVB. The server ID is set with the variable " -"`jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment " -"variables in the JVB docker container. This variable can be set via the " -"host file, a parameter to the ansible command or in the `vars.yaml` for " -"the host which will have the additional JVB. For example:" +msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:190 -msgid "" -"Note that the server ID `jvb-1` is reserved for the JVB instance running " -"on the Matrix host and therefore should not be used as the ID of an " -"additional jvb host." +msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:192 -msgid "" -"The additional JVB will also need to expose the colibri web socket port " -"and this can be done with the following variable:" +msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:198 -msgid "" -"The JVB will also need to know where the prosody xmpp server is located, " -"similar to the server ID this can be set in the vars for the JVB by using" -" the variable `jitsi_xmpp_server`. The Jitsi prosody container is " -"deployed on the Matrix server by default so the value can be set to the " -"Matrix domain. For example:" +msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:204 -msgid "" -"However, it can also be set the ip address of the Matrix server. This can" -" be useful if you wish to use a private ip. For example:" +msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:210 -msgid "" -"For the JVB to be able to contact the XMPP server, the latter must expose" -" the XMPP port (5222). By default, the Matrix server does not expose the " -"port; only the XMPP container exposes it internally inside the host, " -"which means that the first JVB (which runs on the Matrix server) can " -"reach it but the additional JVB cannot. The port is exposed by setting " -"`jitsi_prosody_container_jvb_host_bind_port` like this:" +msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:216 @@ -402,17 +265,11 @@ msgid "(The default is empty; if it's set then docker forwards the port.)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:218 -msgid "" -"Applied together this will allow you to provision extra JVB instances " -"which will register themselves with the prosody service and be available " -"for jicofo to route conferences too." +msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:220 -msgid "" -"To make Traefik reverse-proxy to these additional JVBs (living on other " -"hosts), **you would need to add the following Traefik configuration " -"extension**:" +msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:256 @@ -420,11 +277,7 @@ msgid "(Optional) Enable Gravatar" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:258 -msgid "" -"In the default Jisti Meet configuration, gravatar.com is enabled as an " -"avatar service. This results in third party request leaking data to " -"gravatar. Since Element clients already send the url of configured Matrix" -" avatars to Jitsi, we disabled gravatar." +msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:260 @@ -432,11 +285,7 @@ msgid "To enable Gravatar set:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:266 -msgid "" -"**Beware**: This leaks information to a third party, namely the Gravatar-" -"Service (unless configured otherwise: gravatar.com). Besides metadata, " -"this includes the Matrix user_id and possibly the room identifier (via " -"`referrer` header)." +msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:268 @@ -444,26 +293,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:270 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:277 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:279 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:281 @@ -475,34 +313,19 @@ msgid "You can use the self-hosted Jitsi server in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:285 -msgid "" -"**by adding a widget to a room via Element Web** (the one configured by " -"the playbook at `https://element.example.com`). Just start a voice or a " -"video call in a room containing more than 2 members and that would create" -" a Jitsi widget which utilizes your self-hosted Jitsi server." +msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:287 -msgid "" -"**by adding a widget to a room via the Dimension integration manager**. " -"You'll have to point the widget to your own Jitsi server manually. See " -"our [Dimension integration manager](./configuring-playbook-dimension.md) " -"documentation page for more details. Naturally, Dimension would need to " -"be installed first (the playbook doesn't install it by default)." +msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:289 -msgid "" -"**directly (without any Matrix integration)**. Just go to " -"`https://jitsi.example.com`" +msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:291 -msgid "" -"**Note**: Element apps on mobile devices currently [don't support joining" -" meetings on a self-hosted Jitsi server](https://github.com/element-hq" -"/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md" -"#mobile-app-support)." +msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:293 @@ -514,22 +337,15 @@ msgid "Rebuilding your Jitsi installation" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:297 -msgid "" -"**If you ever run into any trouble** or **if you change configuration " -"(`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi " -"setup." +msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:299 -msgid "" -"We normally don't require such manual intervention for other services, " -"but Jitsi services generate a lot of configuration files on their own." +msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:301 -msgid "" -"These files are not all managed by Ansible (at least not yet), so you may" -" sometimes need to delete them all and start fresh." +msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh." msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:303 @@ -537,20 +353,13 @@ msgid "To rebuild your Jitsi configuration:" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:305 -msgid "" -"ask Ansible to stop all Jitsi services: `just run-tags stop-group " -"--extra-vars=group=jitsi`" +msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:306 -msgid "" -"SSH into the server and do this and remove all Jitsi configuration & data" -" (`rm -rf /matrix/jitsi`)" +msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:307 -msgid "" -"ask Ansible to set up Jitsi anew and restart services (`just install-" -"service jitsi`)" +msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po index 49d8e8fe4..02a6f75ea 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 @@ -21,31 +21,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-ldap-auth.md:1 -msgid "" -"Setting up the LDAP authentication password provider module (optional, " -"advanced)" +msgid "Setting up the LDAP authentication password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:3 -msgid "" -"The playbook can install and configure the [matrix-synapse-" -"ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth " -"password provider for you." +msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/matrix-" -"synapse-ldap3/blob/main/README.rst) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:7 -msgid "" -"If you decide that you'd like to let this playbook install it for you, " -"add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:24 @@ -53,10 +41,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:26 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:32 @@ -64,11 +49,7 @@ msgid "Using ma1sd Identity Server for authentication" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:34 -msgid "" -"If you wish to use the ma1sd Identity Server for LDAP authentication " -"instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-" -"synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration" -"](configuring-playbook-ma1sd.md#authentication)." +msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)." msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:36 @@ -76,15 +57,5 @@ msgid "Handling user registration" msgstr "" #: ../../../docs/configuring-playbook-ldap-auth.md:38 -msgid "" -"If you wish for users to also be able to make new registrations against " -"LDAP, you may **also** wish to [set up the ldap-registration-proxy" -"](configuring-playbook-matrix-ldap-registration-proxy.md)." +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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 fd9b19f79..916e35d94 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po @@ -25,45 +25,23 @@ 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)." +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." +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." +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." +msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:11 -msgid "" -"**Note**: enabling ma1sd, means that the `openid` API endpoints will be " -"exposed on the Matrix Federation port (usually `8448`), even if " -"[federation](configuring-playbook-federation.md) is disabled. It's " -"something to be aware of, especially in terms of firewall whitelisting " -"(make sure port `8448` is accessible)." +msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:13 @@ -71,9 +49,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:15 -msgid "" -"To make the ma1sd Identity Server enable its federation features, set up " -"a SRV record that looks like this:" +msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:17 @@ -81,24 +57,15 @@ msgid "Name: `_matrix-identity._tcp` (use this text as-is)" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:18 -msgid "" -"Content: `10 0 443 matrix.example.com` (replace `example.com` with your " -"own)" +msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:20 -msgid "" -"See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-" -"and-your-privacy#choices-are-never-easy) for information on the privacy " -"implications of setting up this SRV record." +msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:22 -msgid "" -"**Note**: This `_matrix-identity._tcp` SRV record for the identity server" -" is different from the `_matrix._tcp` that can be used for Synapse " -"delegation. See [howto-server-delegation.md](howto-server-delegation.md) " -"for more information about delegation." +msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:24 @@ -106,9 +73,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:26 -msgid "" -"To enable ma1sd, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:32 @@ -116,23 +81,15 @@ msgid "Matrix.org lookup forwarding" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:34 -msgid "" -"To ensure maximum discovery, you can make your identity server also " -"forward lookups to the central matrix.org Identity server (at the cost of" -" potentially leaking all your contacts information)." +msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:36 -msgid "" -"Enabling this is discouraged and you'd better [learn " -"more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups)" -" before proceeding." +msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:38 -msgid "" -"To enable matrix.org forwarding, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:44 @@ -140,33 +97,19 @@ msgid "Additional features" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:46 -msgid "" -"What this playbook configures for your is some bare minimum Identity " -"Server functionality, so that you won't need to rely on external 3rd " -"party services." +msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:48 -msgid "" -"A few variables can be toggled in this playbook to alter the ma1sd " -"configuration that gets generated." +msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:50 -msgid "" -"Still, ma1sd can do much more. You can refer to the [ma1sd " -"website](https://github.com/ma1uta/ma1sd) for more details and " -"configuration options." +msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:52 -msgid "" -"To use a more custom configuration, you can define a " -"`matrix_ma1sd_configuration_extension_yaml` string variable and put your " -"configuration in it. To learn more about how to do this, refer to the " -"information about `matrix_ma1sd_configuration_extension_yaml` in the " -"[default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) " -"of the ma1sd component." +msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:54 @@ -174,10 +117,7 @@ msgid "Customizing email templates" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:56 -msgid "" -"If you'd like to change the default email templates used by ma1sd, take a" -" look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in " -"the `roles/custom/matrix-ma1sd/defaults/main.yml` file." +msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:58 @@ -185,59 +125,31 @@ msgid "ma1sd-controlled Registration" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:60 -msgid "" -"To use the " -"[Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" -" feature of ma1sd, you can make use of the following variables:" +msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:62 -msgid "" -"`matrix_synapse_enable_registration` - to enable user-initiated " -"registration in Synapse" +msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:64 -msgid "" -"`matrix_synapse_enable_registration_captcha` - to validate registering " -"users using reCAPTCHA, as described in the [enabling reCAPTCHA" -"](configuring-captcha.md) documentation." +msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:66 -msgid "" -"`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among" -" `'email'`, `'msisdn'`) required by the Synapse server for registering" +msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:68 -msgid "" -"variables prefixed with `matrix_ma1sd_container_labels_` (e.g. " -"`matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) " -"- to configure the Traefik reverse-proxy to capture and send registration" -" requests to ma1sd (instead of Synapse), so it can apply its additional " -"functionality" +msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:70 -msgid "" -"`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as " -"required. See the [Registration feature's " -"docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md)" -" for inspiration. Also see the [Additional features](#additional-" -"features) section below to learn more about how to use " -"`matrix_ma1sd_configuration_extension_yaml`." +msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:72 -msgid "" -"**Note**: For this to work, either the homeserver needs to [federate" -"](configuring-playbook-federation.md) or the `openid` APIs need to " -"exposed on the federation port. When federation is disabled and ma1sd is " -"enabled, we automatically expose the `openid` APIs (only!) on the " -"federation port. Make sure the federation port (usually " -"`https://matrix.example.com:8448`) is whitelisted in your firewall (even " -"if you don't actually use/need federation)." +msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:74 @@ -245,18 +157,11 @@ msgid "Authentication" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:76 -msgid "" -"[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md)" -" provides the possibility to use your own [Identity " -"Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md)" -" (for example LDAP) to authenticate users on your Homeserver." +msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:78 -msgid "" -"To enable authentication against an LDAP server, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:98 @@ -264,11 +169,7 @@ msgid "Example: SMS verification" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:100 -msgid "" -"If your use case requires mobile verification, it is quite simple to " -"integrate ma1sd with [Twilio](https://www.twilio.com/), an online " -"telephony services gateway. Their prices are reasonable for low-volume " -"projects and integration can be done with the following configuration:" +msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:114 @@ -276,12 +177,7 @@ msgid "Example: Open Registration for every Domain" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:116 -msgid "" -"If you want to open registration for any domain, you have to setup the " -"allowed domains with ma1sd's `blacklist` and `whitelist`. The default " -"behavior when neither the `blacklist`, nor the `whitelist` match, is to " -"allow registration. Beware: you can't block toplevel domains (aka `.xy`) " -"because the internal architecture of ma1sd doesn't allow that." +msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:130 @@ -289,25 +185,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:132 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:139 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:141 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:143 @@ -315,28 +201,13 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:145 -msgid "" -"If email address validation emails sent by ma1sd are not reaching you, " -"you should look into [Adjusting email-sending settings](configuring-" -"playbook-email.md)." +msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:147 -msgid "" -"If you'd like additional logging information, temporarily enable verbose " -"logging for ma1sd." +msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd." msgstr "" #: ../../../docs/configuring-playbook-ma1sd.md:149 -msgid "" -"To enable it, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" - -#~ msgid "" -#~ "See the project's " -#~ "[documentation](https://github.com/ma1uta/ma1sd) to learn" -#~ " what it does and why it might" -#~ " be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po index 9d9eeb8ba..7cc448789 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po @@ -25,33 +25,19 @@ msgid "Setting up Matrix Authentication Service (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:3 -msgid "" -"This playbook can install and configure [Matrix Authentication " -"Service](https://github.com/element-hq/matrix-authentication-service/) " -"(MAS) - a service operating alongside your existing [Synapse" -"](./configuring-playbook-synapse.md) homeserver and providing [better " -"authentication, session management and permissions in " -"Matrix](https://matrix.org/blog/2023/09/better-auth/)." +msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:5 -msgid "" -"Matrix Authentication Service is an implementation of [MSC3861: Next-" -"generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com" -"/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, " -"tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." +msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:7 -msgid "" -"**Before going through with starting to use Matrix Authentication " -"Service**, make sure to read:" +msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:9 -msgid "" -"the [Reasons to use Matrix Authentication Service](#reasons-to-use-" -"matrix-authentication-service) section below" +msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:10 @@ -63,10 +49,7 @@ msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:13 -msgid "" -"**If you've already been using Synapse** and have user accounts in its " -"database, you can [migrate to Matrix Authentication Service](#migrating-" -"an-existing-synapse-homeserver-to-matrix-authentication-service)." +msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:15 @@ -74,66 +57,39 @@ msgid "Reasons to use Matrix Authentication Service" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:17 -msgid "" -"You may be wondering whether you should make the switch to Matrix " -"Authentication Service (MAS) or keep using your existing authentication " -"flow via Synapse (password-based or [OIDC](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." +msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:19 -msgid "" -"Matrix Authentication Service is **still an experimental service** and " -"**not a default** for this Ansible playbook." +msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:21 -msgid "" -"The [Expectations](#expectations) section contains a list of what works " -"and what doesn't (**some services don't work with MAS yet**), as well as " -"the **relative irreversability** of the migration process." +msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:23 -msgid "" -"Below, we'll try to **highlight some potential reasons for switching** to" -" Matrix Authentication Service:" +msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:25 -msgid "" -"To use SSO in [Element X](https://element.io/blog/element-x-ignition/). " -"The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-" -"connect-for-single-sign-on) login flow is only supported in old Element " -"clients and will not be supported in Element X. Element X will only " -"support the new SSO-based login flow provided by MAS, so if you want to " -"use SSO with Element X, you will need to switch to MAS." +msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:27 -msgid "" -"To help drive adoption of the \"Next-generation auth for Matrix\" by " -"switching to what's ultimately coming anyway" +msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:29 -msgid "" -"To help discover (and potentially fix) MAS integration issues with this " -"Ansible playbook" +msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:31 -msgid "" -"To help discover (and potentially fix) MAS integration issues with " -"various other Matrix components (bridges, bots, clients, etc.)" +msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:33 -msgid "" -"To reap some of the security benefits that Matrix Authentication Service " -"offers, as outlined in the [Better authentication, session management and" -" permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) " -"article." +msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:35 @@ -141,32 +97,15 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:37 -msgid "" -"⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver " -"implementation (which is the default for this playbook). Other homeserver" -" implementations ([Dendrite](./configuring-playbook-dendrite.md), " -"[Conduit](./configuring-playbook-conduit.md), etc.) do not support " -"integrating wtih Matrix Authentication Service yet." +msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:39 -msgid "" -"⚠️ **email sending** configured (see [Adjusting email-sending settings" -"](./configuring-playbook-email.md)), because **Matrix Authentication " -"Service [still insists](https://github.com/element-hq/matrix-" -"authentication-service/issues/1505) on having a verified email address " -"for each user** going through the new SSO-based login flow. It's also " -"possible to [work around email deliverability issues](#working-around-" -"email-deliverability-issues) if your email configuration is not working." +msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:41 -msgid "" -"❌ **disabling all password providers** for Synapse (things like [shared-" -"secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth" -"](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-" -"playbook-ldap-auth.md), etc.) More details about this are available in " -"the [Expectations](#expectations) section below." +msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:43 @@ -174,37 +113,15 @@ msgid "Expectations" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:45 -msgid "" -"This section details what you can expect when switching to the Matrix " -"Authentication Service (MAS)." +msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:47 -msgid "" -"❌ **Synapse password providers will need to be disabled**. You can no " -"longer use [shared-secret-auth](./configuring-playbook-shared-secret-" -"auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth" -"](./configuring-playbook-ldap-auth.md), etc. When the authentication flow" -" is handled by MAS (not by Synapse anymore), it doesn't make sense to " -"extend the Synapse authentication flow with additional modules. Many " -"bridges used to rely on shared-secret-auth for doing double-puppeting " -"(impersonating other users), but most (at least the mautrix bridges) " -"nowadays use [Appservice Double Puppet](./configuring-playbook-" -"appservice-double-puppet.md) as a better alternative. Older/maintained " -"bridges may still rely on shared-secret-auth, as do other services like " -"[matrix-corporal](./configuring-playbook-matrix-corporal.md)." +msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:49 -msgid "" -"❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-" -"admin.md) do not have full compatibility with MAS yet**. synapse-admin " -"already supports [login with access token](https://github.com/etkecc" -"/synapse-admin/pull/58), browsing users (which Synapse will internally " -"fetch from MAS) and updating user avatars. However, editing users " -"(passwords, etc.) now needs to happen directly against MAS using the [MAS" -" Admin API](https://element-hq.github.io/matrix-authentication-" -"service/api/index.html), which synapse-admin cannot interact with yet." +msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:51 @@ -212,23 +129,15 @@ msgid "❌ **Some services experience issues when authenticating via MAS**:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:53 -msgid "" -"[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first" -" time around, but it consistently fails after restarting:" +msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:55 -msgid "" -"cannot initialize matrix bot error=\"olm account is marked as shared, " -"keys seem to have disappeared from the server\"" +msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\"" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:57 -msgid "" -"[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) " -"fails to start (see [element-hq/matrix-authentication-" -"service#3439](https://github.com/element-hq/matrix-authentication-" -"service/issues/3439))" +msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:58 @@ -236,131 +145,51 @@ msgid "Other services may be similarly affected. This list is not exhaustive." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:60 -msgid "" -"❌ **Encrypted appservices** do not work yet (related to " -"[MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) " -"and [PR 17705 for Synapse](https://github.com/element-" -"hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will" -" fail to start (see [this issue](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/3658) for Hookshot). You can use these " -"bridges/bots only if you **keep end-to-bridge encryption disabled** " -"(which is the default setting)." +msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:62 -msgid "" -"⚠️ **You will need to have email sending configured** (see [Adjusting " -"email-sending settings](./configuring-playbook-email.md)), because " -"**Matrix Authentication Service [still insists](https://github.com" -"/element-hq/matrix-authentication-service/issues/1505) on having a " -"verified email address for each user** going through the new SSO-based " -"login flow. It's also possible to [work around email deliverability " -"issues](#working-around-email-deliverability-issues) if your email " -"configuration is not working." +msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:64 -msgid "" -"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " -"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" -"authentication-service) is **possible**, but requires **some playbook-" -"assisted manual work**. Migration is **reversible with no or minor issues" -" if done quickly enough**, but as users start logging in (creating new " -"login sessions) via the new MAS setup, disabling MAS and reverting back " -"to the Synapse user database will cause these new sessions to break." +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:66 -msgid "" -"⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication " -"Service](#migrating-an-existing-synapse-homeserver-to-matrix-" -"authentication-service) does not currently seem to preserve the \"admin\"" -" flag for users (as found in the Synapse database). All users are " -"imported as non-admin - see [element-hq/matrix-authentication-" -"service#3440](https://github.com/element-hq/matrix-authentication-" -"service/issues/3440). You may need update the Matrix Authentication " -"Service's database manually and adjust the `can_request_admin` column in " -"the `users` table to `true` for users that need to be administrators " -"(e.g. `UPDATE users SET can_request_admin = true WHERE username = " -"'someone';`)" +msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:68 -msgid "" -"⚠️ Delegating user authentication to MAS causes **your Synapse server to " -"be completely dependant on one more service** for its operations. MAS is " -"quick & lightweight and should be stable enough already, but this is " -"something to keep in mind when making the switch." +msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:70 -msgid "" -"⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " -"migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 " -"configuration](#upstream-oauth2-configuration)." +msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:72 -msgid "" -"⚠️ A [compatibility layer](https://element-hq.github.io/matrix-" -"authentication-service/setup/homeserver.html#set-up-the-compatibility-" -"layer) is installed - all `/_matrix/client/*/login` (etc.) requests will " -"be routed to MAS instead of going to the homeserver. This is done both " -"publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and " -"on the internal Traefik entrypoint (e.g. `https://matrix-" -"traefik:8008/_matrix/client/*/login`) which helps addon services reach " -"the homeserver's Client-Server API. You typically don't need to do " -"anything to make this work, but it's good to be aware of it, especially " -"if you have a [custom webserver setup](./configuring-playbook-own-" -"webserver.md)." +msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:74 -msgid "" -"✅ Your **existing login sessions will continue to work** (you won't get " -"logged out). Migration will require a bit of manual work and minutes of " -"downtime, but it's not too bad." +msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:76 -msgid "" -"✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), " -"[Element Web](./configuring-playbook-client-element-web.md), Element X, " -"FluffyChat) will be able to use the **new SSO-based login flow** provided" -" by Matrix Authentication Service" +msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:78 -msgid "" -"✅ The **old login flow** (called `m.login.password`) **will still " -"continue to work**, so clients (old Element Web, etc.) and bridges/bots " -"that don't support the new OIDC-based login flow will still work. Going " -"through the old login flow does not require users to have a verified " -"email address, as [is the case](https://github.com/element-hq/matrix-" -"authentication-service/issues/1505) for the new SSO-based login flow." +msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:80 -msgid "" -"✅ [Registering users](./registering-users.md) via **the playbook's " -"`register-user` tag remains unchanged**. The playbook automatically does " -"the right thing regardless of homeserver implementation (Synapse, " -"Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, " -"the playbook will forward user-registration requests to MAS. Registering " -"users via the command-line is no longer done via the " -"`/matrix/synapse/bin/register` script, but via `/matrix/matrix-" -"authentication-service/bin/register-user`." +msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:82 -msgid "" -"✅ Users that are prepared by the playbook (for bots, bridges, etc.) will " -"continue to be registered automatically as expected. The playbook " -"automatically does the right thing regardless of homeserver " -"implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or " -"not. When MAS is enabled, the playbook will forward user-registration " -"requests to MAS." +msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:84 @@ -372,11 +201,7 @@ msgid "New homeserver" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:88 -msgid "" -"For new homeservers (which don't have any users in their Synapse database" -" yet), follow the [Adjusting the playbook configuration](#adjusting-the-" -"playbook-configuration) instructions and then proceed with " -"[Installing](#installing)." +msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:90 @@ -384,10 +209,7 @@ msgid "Existing homeserver" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:92 -msgid "" -"Other homeserver implementations ([Dendrite](./configuring-playbook-" -"dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not " -"support integrating wtih Matrix Authentication Service yet." +msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:94 @@ -395,21 +217,11 @@ msgid "For existing Synapse homeservers:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:96 -msgid "" -"when following the [Adjusting the playbook configuration](#adjusting-the-" -"playbook-configuration) instructions, make sure to **disable the " -"integration between Synapse and MAS** by **uncommenting** the " -"`matrix_authentication_service_migration_in_progress: true` line as " -"described in the [Marking an existing homeserver for migration](#marking-" -"an-existing-homeserver-for-migration) section below." +msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:98 -msgid "" -"then follow the [Migrating an existing Synapse homeserver to Matrix " -"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" -"matrix-authentication-service) instructions to perform the installation " -"and migration" +msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:100 @@ -417,23 +229,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:102 -msgid "" -"To enable Matrix Authentication Service, add the following configuration " -"to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:116 -msgid "" -"In the sub-sections that follow, we'll cover some additional " -"configuration options that you may wish to adjust." +msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:118 -msgid "" -"There are many other configuration options available. Consult the " -"[`defaults/main.yml` file](../roles/custom/matrix-authentication-" -"service/defaults/main.yml) in the [matrix-authentication-service " -"role](../roles/custom/matrix-authentication-service/) to discover them." +msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:120 @@ -441,27 +245,16 @@ msgid "Adjusting the Matrix Authentication Service URL" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:122 -msgid "" -"By default, this playbook installs the Matrix Authentication Service on " -"the `matrix.` subdomain, at the `/auth` path " -"(https://matrix.example.com/auth). This makes it easy to install it, " -"because it **doesn't require additional DNS records to be set up**. If " -"that's okay, you can skip this section." +msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:124 -msgid "" -"By tweaking the `matrix_authentication_service_hostname` and " -"`matrix_authentication_service_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:126 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:149 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:134 @@ -469,19 +262,11 @@ msgid "Marking an existing homeserver for migration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:136 -msgid "" -"The [configuration above](#adjusting-the-playbook-configuration) " -"instructs existing users wishing to migrate to add " -"`matrix_authentication_service_migration_in_progress: true` to their " -"configuration." +msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:138 -msgid "" -"This is done temporarily. The migration steps are described in more " -"detail in the [Migrating an existing Synapse homeserver to Matrix " -"Authentication Service](#migrating-an-existing-synapse-homeserver-to-" -"matrix-authentication-service) section below." +msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:140 @@ -489,60 +274,35 @@ msgid "Upstream OAuth2 configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:142 -msgid "" -"To make Matrix Authentication Service delegate to an existing upstream " -"OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` " -"setting](https://element-hq.github.io/matrix-authentication-" -"service/reference/configuration.html#upstream_oauth2providers)." +msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:144 -msgid "" -"The playbook exposes a " -"`matrix_authentication_service_config_upstream_oauth2_providers` variable" -" for controlling this setting." +msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:261 -msgid "" -"💡 Refer to the [`upstream_oauth2.providers` setting](https://element-" -"hq.github.io/matrix-authentication-" -"service/reference/configuration.html#upstream_oauth2providers) for the " -"most up-to-date schema and example for providers. The value shown above " -"here may be out of date." +msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:263 -msgid "" -"⚠️ The syntax for existing [OIDC providers configured in Synapse" -"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" -"sign-on) is slightly different, so you will need to adjust your " -"configuration when switching from Synapse OIDC to MAS upstream OAuth2." +msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:265 -msgid "" -"⚠️ When [migrating an existing homeserver](#migrating-an-existing-" -"synapse-homeserver-to-matrix-authentication-service) which contains OIDC-" -"sourced users, you will need to:" +msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:267 -msgid "" -"[Configure upstream OIDC provider mapping for syn2mas](#configuring-" -"upstream-oidc-provider-mapping-for-syn2mas)" +msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:268 -msgid "" -"go through the [migrating an existing homeserver](#migrating-an-existing-" -"synapse-homeserver-to-matrix-authentication-service) process" +msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:269 -msgid "" -"remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) " -"to prevent it being in conflict with the MAS OIDC configuration" +msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:271 @@ -550,10 +310,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:273 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Matrix Authentication Service domain to the " -"Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:275 @@ -561,9 +318,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:277 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:279 @@ -571,10 +326,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:281 -msgid "" -"Now that you've [adjusted the playbook configuration](#adjusting-the-" -"playbook-configuration) and [your DNS records](#adjusting-dns-records), " -"you can run the playbook with [playbook tags](playbook-tags.md) as below:" +msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:288 @@ -582,34 +334,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:290 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:292 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:294 -msgid "" -"If you're in the process of migrating an existing Synapse homeserver to " -"MAS, you should now follow the rest of the steps in the [Migrating an " -"existing Synapse homeserver to Matrix Authentication Service](#migrating-" -"an-existing-synapse-homeserver-to-matrix-authentication-service) guide." +msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:296 -msgid "" -"💡 After installation, you should [verify that Matrix Authentication " -"Service is installed correctly](#verify-that-matrix-authentication-" -"service-is-installed-correctly)." +msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:298 @@ -617,16 +354,11 @@ msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:300 -msgid "" -"Our migration guide is loosely based on the upstream [Migrating an " -"existing homeserver](https://element-hq.github.io/matrix-authentication-" -"service/setup/migration.html) guide." +msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:302 -msgid "" -"Migration is done via a tool called `syn2mas`, which the playbook could " -"run for you (in a container)." +msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:304 @@ -634,11 +366,7 @@ msgid "The installation + migration steps are like this:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:306 -msgid "" -"[Adjust your configuration](#adjusting-the-playbook-configuration) to " -"**disable the integration between the homeserver and MAS**. This is done " -"by **uncommenting** the " -"`matrix_authentication_service_migration_in_progress: true` line." +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:308 @@ -646,74 +374,39 @@ msgid "Perform the initial [installation](#installing). At this point:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:310 -msgid "" -"Matrix Authentication Service will be installed. Its database will be " -"empty, so it cannot validate existing access tokens or authentication " -"users yet." +msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:312 -msgid "" -"The homeserver will still continue to use its local database for " -"validating existing access tokens." +msgid "The homeserver will still continue to use its local database for validating existing access tokens." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:314 -msgid "" -"Various [compatibility layer URLs](https://element-hq.github.io/matrix-" -"authentication-service/setup/homeserver.html#set-up-the-compatibility-" -"layer) are not yet installed. New login sessions will still be forwarded " -"to the homeserver, which is capable of completing them." +msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:316 -msgid "" -"The `matrix-user-creator` role would be suppressed, so that it doesn't " -"automatically attempt to create users (for bots, etc.) in the MAS " -"database. These user accounts likely already exist in Synapse's user " -"database and could be migrated over (via syn2mas, as per the steps " -"below), so creating them in the MAS database would have been unnecessary " -"and potentially problematic (conflicts during the syn2mas migration)." +msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:318 -msgid "" -"Consider taking a full [backup of your Postgres database](./maintenance-" -"postgres.md#backing-up-postgresql). This is done just in case. The " -"**syn2mas migration tool does not delete any data**, so it should be " -"possible to revert to your previous setup by merely disabling MAS and re-" -"running the playbook (no need to restore a Postgres backup). However, do " -"note that as users start logging in (creating new login sessions) via the" -" new MAS setup, disabling MAS and reverting back to the Synapse user " -"database will cause these new sessions to break." +msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:320 -msgid "" -"[Migrate your data from Synapse to Matrix Authentication Service using " -"syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-" -"service-using-syn2mas)" +msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:322 -msgid "" -"[Adjust your configuration](#adjusting-the-playbook-configuration) again," -" to:" +msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:324 -msgid "" -"remove the `matrix_authentication_service_migration_in_progress: false` " -"line" +msgid "remove the `matrix_authentication_service_migration_in_progress: false` line" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:326 -msgid "" -"if you had been using [OIDC providers configured in Synapse" -"](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-" -"sign-on), remove all Synapse OIDC-related configuration " -"(`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS " -"OIDC configuration" +msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:328 @@ -725,42 +418,23 @@ msgid "The homeserver will start delegating authentication to MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:332 -msgid "" -"The compatibility layer URLs will be installed. New login sessions will " -"be completed by MAS." +msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:334 -msgid "" -"[Verify that Matrix Authentication Service is installed correctly" -"](#verify-that-matrix-authentication-service-is-installed-correctly)" +msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:336 -msgid "" -"Migrate your data from Synapse to Matrix Authentication Service using " -"syn2mas" +msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:338 -msgid "" -"We **don't** ask you to [run the `syn2mas` migration advisor " -"command](https://element-hq.github.io/matrix-authentication-" -"service/setup/migration.html#run-the-migration-advisor), because it only " -"gives you the green light if your Synapse configuration " -"(`homeserver.yaml`) is configured in a way that's compatible with MAS " -"(delegating authentication to MAS; disabling Synapse's password config; " -"etc.). Until we migrate your data with the `syn2mas` tool, we " -"intentionally avoid doing these changes to allow existing user sessions " -"to work." +msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:340 -msgid "" -"You can invoke the `syn2mas` tool via the playbook by running the " -"playbook's `matrix-authentication-service-syn2mas` tag. We recommend " -"first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " -"migration](#performing-a-real-syn2mas-migration)." +msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:342 @@ -768,25 +442,15 @@ msgid "Configuring syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:344 -msgid "" -"If you're using [OIDC with Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on), you will need to " -"[Configuring upstream OIDC provider mapping for syn2mas](#configuring-" -"upstream-oidc-provider-mapping-for-syn2mas)." +msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:346 -msgid "" -"If you only have local (non-OIDC) users in your Synapse database, you can" -" likely run `syn2mas` as-is (without doing additional configuration " -"changes)." +msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:348 -msgid "" -"When you're done with potentially configuring `syn2mas`, proceed to doing" -" a [dry-run](#performing-a-syn2mas-dry-run) and then a [real " -"migration](#performing-a-real-syn2mas-migration)." +msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:350 @@ -794,13 +458,7 @@ msgid "Configuring upstream OIDC provider mapping for syn2mas" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:352 -msgid "" -"If you have existing OIDC users in your Synapse user database (which will" -" be the case if when using [OIDC with Synapse](./configuring-playbook-" -"synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to " -"pass an additional `--upstreamProviderMapping` argument to the `syn2mas` " -"tool to tell it which provider (on the Synapse side) maps to which other " -"provider on the MAS side." +msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:354 @@ -808,10 +466,7 @@ msgid "If you don't do this, `syn2mas` would report errors like this one:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:356 -msgid "" -"[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-" -"b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: " -"Unknown upstream provider oidc-keycloak]" +msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:358 @@ -819,27 +474,15 @@ msgid "Below is an example situation and a guide for how to solve it." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:360 -msgid "" -"If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) " -"named `keycloak`, in the Synapse database users would be associated with " -"the `oidc-keycloak` provider (note the `oidc-` prefix that was added " -"automatically by Synapse to your `idp_id` value)." +msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:362 -msgid "" -"The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` " -"on the MAS side, as defined in " -"`matrix_authentication_service_config_upstream_oauth2_providers` (see the" -" [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section " -"above)." +msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:364 -msgid "" -"To tell `syn2mas` how the Synapse-configured OIDC provider maps to the " -"new MAS-configured OIDC provider, add this additional configuration to " -"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:373 @@ -847,10 +490,7 @@ msgid "Performing a syn2mas dry-run" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:375 -msgid "" -"Having [configured syn2mas](#configuring-syn2mas), we recommend doing a " -"[dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to " -"verify that everything will work out as expected." +msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:377 @@ -862,11 +502,7 @@ msgid "To perform a dry-run, run:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:385 -msgid "" -"Observe the command output (especially the last line of the the syn2mas " -"output). If you are confident that the migration will work out as " -"expected, you can proceed with a [real migration](#performing-a-real-" -"syn2mas-migration)." +msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:387 @@ -886,37 +522,23 @@ msgid "you've performed a Postgres backup, just in case" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:395 -msgid "" -"you're aware of the irreversibility of the migration process without " -"disruption after users have created new login sessions via the new MAS " -"setup" +msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:397 -msgid "" -"you've [configured syn2mas](#configuring-syn2mas), especially if you've " -"used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse" -"--openid-connect-for-single-sign-on)" +msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:399 -msgid "" -"you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and " -"don't see any issues in its output" +msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:401 -msgid "" -"To perform a real migration, run the `matrix-authentication-service-" -"syn2mas` tag **without** the " -"`matrix_authentication_service_syn2mas_dry_run` variable:" +msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:407 -msgid "" -"Having performed a `syn2mas` migration once, trying to do it again will " -"report errors for users that were already migrated (e.g. \"Error: Unknown" -" upstream provider oauth-delegated\")." +msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:409 @@ -924,11 +546,7 @@ msgid "Verify that Matrix Authentication Service is installed correctly" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:411 -msgid "" -"After [installation](#installing), run the `doctor` subcommand of the " -"[`mas-cli` command-line tool](https://element-hq.github.io/matrix-" -"authentication-service/reference/cli/index.html) to verify that MAS is " -"installed correctly." +msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:413 @@ -936,16 +554,11 @@ msgid "You can do it:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:415 -msgid "" -"either via the Ansible playbook's `matrix-authentication-service-mas-cli-" -"doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" +msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:417 -msgid "" -"or by running the `mas-cli` script on the server (which invokes the `mas-" -"cli` tool inside a container): `/matrix/matrix-authentication-service/bin" -"/mas-cli doctor`" +msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:419 @@ -957,11 +570,7 @@ msgid "Management" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:433 -msgid "" -"You can use the [`mas-cli` command-line tool](https://element-" -"hq.github.io/matrix-authentication-service/reference/cli/index.html) " -"(exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` " -"script) to perform administrative tasks against MAS." +msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:435 @@ -969,24 +578,15 @@ msgid "This documentation page already mentions:" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:437 -msgid "" -"the `mas-cli doctor` sub-command in the [Verify that Matrix " -"Authentication Service is installed correctly](#verify-that-matrix-" -"authentication-service-is-installed-correctly) section, which you can run" -" via the CLI and via the Ansible playbook's `matrix-authentication-" -"service-mas-cli-doctor` tag" +msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:439 -msgid "" -"the `mas-cli manage register-user` sub-command in the [Registering users" -"](./registering-users.md) documentation" +msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:441 -msgid "" -"There are other sub-commands available. Run `/matrix/matrix-" -"authentication-service/bin/mas-cli` to get an overview." +msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:443 @@ -994,17 +594,11 @@ msgid "User registration" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:445 -msgid "" -"After Matrix Authentication Service is [installed](#installing), users " -"need to be managed there (unless you're managing them in an [upstream " -"OAuth2 provider](#upstream-oauth2-configuration))." +msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:447 -msgid "" -"You can register users new users as described in the [Registering users" -"](./registering-users.md) documentation (via `mas-cli manage register-" -"user` or the Ansible playbook's `register-user` tag)." +msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:449 @@ -1012,33 +606,17 @@ msgid "Working around email deliverability issues" msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:451 -msgid "" -"Because Matrix Authentication Service [still insists](https://github.com" -"/element-hq/matrix-authentication-service/issues/1505) on having a " -"verified email address for each user, you may need to work around email " -"deliverability issues if [your email-sending configuration" -"](./configuring-playbook-email.md) is not working." +msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:453 -msgid "" -"Matrix Authentication Service attempts to verify email addresses by " -"sending a verification email to the address specified by the user " -"whenever they log in to an account without a verified email address." +msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:455 -msgid "" -"If email delivery is not working, **you can retrieve the email " -"configuration code from the Matrix Authentication Service's logs** " -"(`journalctl -fu matrix-authentication-service`)." +msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)." msgstr "" #: ../../../docs/configuring-playbook-matrix-authentication-service.md:457 -msgid "" -"Alternatively, you can use the [`mas-cli` management tool](#management) " -"to manually verify email addresses for users. Example: `/matrix/matrix-" -"authentication-service/bin/mas-cli manage verify-email some.username " -"email@example.com`" +msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po index 43934ff04..a70b79d26 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 @@ -25,49 +25,31 @@ msgid "Setting up Matrix Corporal (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:5 -msgid "" -"**WARNING**: This is an advanced feature! It requires prior experience " -"with Matrix and a specific need for using [Matrix " -"Corporal](https://github.com/devture/matrix-corporal). If you're unsure " -"whether you have such a need, you most likely don't." +msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:9 -msgid "" -"The playbook can install and configure [matrix-" -"corporal](https://github.com/devture/matrix-corporal) for you." +msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:11 -msgid "" -"In short, it's a sort of automation and firewalling service, which is " -"helpful if you're instaling Matrix services in a controlled corporate " -"environment." +msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:13 -msgid "" -"See the project's [documentation](https://github.com/devture/matrix-" -"corporal/blob/main/README.md) to learn what it does and why it might be " -"useful to you." +msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:15 -msgid "" -"If you decide that you'd like to let this playbook install it for you, " -"you'd need to also:" +msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:16 -msgid "" -"(required) [set up the Shared Secret Auth password provider module" -"](configuring-playbook-shared-secret-auth.md)" +msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:17 -msgid "" -"(optional, but encouraged) [set up the REST authentication password " -"provider module](configuring-playbook-rest-auth.md)" +msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:19 @@ -75,36 +57,23 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:74 -msgid "" -"Matrix Corporal operates with a specific Matrix user on your server. By " -"default, it's `matrix-corporal` (controllable by the " -"`matrix_corporal_reconciliation_user_id_local_part` setting, see above)." +msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:76 -msgid "" -"No matter what Matrix user ID you configure to run it with, make sure " -"that:" +msgid "No matter what Matrix user ID you configure to run it with, make sure that:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:78 -msgid "" -"the Matrix Corporal user is created by [registering it](registering-" -"users.md) **with administrator privileges**. Use a password you remember," -" as you'll need to log in from time to time to create or join rooms" +msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:80 -msgid "" -"the Matrix Corporal user is joined and has Admin/Moderator-level access " -"to any rooms you want it to manage" +msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:82 @@ -112,17 +81,11 @@ msgid "Using a locally-stored static policy" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:84 -msgid "" -"If you'd like to use a [static policy file](https://github.com/devture" -"/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-" -"style-policy-provider), you can use a configuration like this:" +msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:116 -msgid "" -"To learn more about what the policy configuration, see the matrix-" -"corporal documentation on [policy](https://github.com/devture/matrix-" -"corporal/blob/master/docs/policy.md)." +msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:118 @@ -130,25 +93,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:120 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:127 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just run-tags setup-aux-files,setup-corporal,start` or `just " -"setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:129 -msgid "" -"`just run-tags setup-aux-files,setup-corporal,start` is useful for " -"maintaining your setup quickly when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"`just setup-all` runs the `ensure-matrix-users-created` tag too." +msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:131 @@ -156,9 +109,7 @@ msgid "Matrix Corporal files" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:133 -msgid "" -"The following local filesystem paths are mounted in the `matrix-corporal`" -" container and can be used in your configuration (or policy):" +msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:135 @@ -166,35 +117,13 @@ msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:137 -msgid "" -"`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and " -"write)" +msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:139 -msgid "" -"`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read" -" and write)" +msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)" msgstr "" #: ../../../docs/configuring-playbook-matrix-corporal.md:141 -msgid "" -"As an example: you can create your own configuration files in " -"`/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` " -"in the Docker container. Your configuration (stuff in " -"`matrix_corporal_policy_provider_config`) needs to refer to these files " -"via the local container paths - `/etc/matrix-corporal` (read-only), `/var" -"/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read " -"and write)." +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 "" - -#~ 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. See that project's documentation" -#~ " to learn what it does and why" -#~ " it might be useful to you." -#~ 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 6de48f670..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 @@ -25,10 +25,7 @@ msgid "Setting up matrix-ldap-registration-proxy (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3 -msgid "" -"The playbook can install and configure [matrix-ldap-registration-" -"proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy)" -" for you." +msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5 @@ -36,10 +33,7 @@ msgid "This proxy handles Matrix registration requests and forwards them to LDAP msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7 -msgid "" -"**Note**: This does support the full Matrix specification for " -"registrations. It only provide a very coarse implementation of a basic " -"password registration." +msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration." msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9 @@ -47,18 +41,11 @@ msgid "Quickstart" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22 -msgid "" -"If you already use the [synapse external password provider via LDAP" -"](configuring-playbook-ldap-auth.md) (that is, you have " -"`matrix_synapse_ext_password_provider_ldap_enabled: true` and other " -"options in your configuration) you can use the following values as " -"configuration:" +msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35 @@ -66,24 +53,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po index 0c5a8106b..9a742c046 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 @@ -25,28 +25,15 @@ msgid "Storing Matrix media files using matrix-media-repo (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:3 -msgid "" -"[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often " -"abbreviated \"MMR\") is a highly customizable multi-domain media " -"repository for Matrix. Intended for medium to large environments " -"consisting of several homeservers, this media repo de-duplicates media " -"(including remote media) while being fully compliant with the " -"specification." +msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:5 -msgid "" -"Smaller/individual homeservers can still make use of this project's " -"features, though it may be difficult to set up or have higher than " -"expected resource consumption. Please do your research before deploying " -"this as this project may not be useful for your environment." +msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:7 -msgid "" -"For a simpler alternative (which allows you to offload your media " -"repository storage to S3, etc.), you can [configure S3 storage" -"](configuring-playbook-s3.md) instead of setting up matrix-media-repo." +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 @@ -62,9 +49,7 @@ msgid "[Additional configuration options](#configuring-the-media-repo)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md -msgid "" -"[Importing data from an existing media store](#importing-data-from-an-" -"existing-media-store)" +msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:15 @@ -72,27 +57,15 @@ msgid "Quickstart" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:17 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the " -"installation process](./installing.md) for the playbook:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:26 -msgid "" -"The repo is pre-configured for integrating with the Postgres database, " -"Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-" -"grafana.md) (if metrics enabled) from this playbook for all the available" -" homeserver roles. When the media repo is enabled, other media store " -"roles should be disabled (if using Synapse with other media store roles)." +msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:28 -msgid "" -"By default, the media-repo will use the local filesystem for data " -"storage. You can alternatively use a `s3` cloud backend as well. Access " -"token caching is also enabled by default since the logout endpoints are " -"proxied through the media repo." +msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:30 @@ -104,12 +77,7 @@ msgid "Additional common configuration options:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:91 -msgid "" -"Full list of configuration options with documentation can be found in " -"[`roles/custom/matrix-media-" -"repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/blob/master/roles/custom/matrix-media-" -"repo/defaults/main.yml)" +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:93 @@ -117,33 +85,19 @@ msgid "Signing Keys" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:95 -msgid "" -"Authenticated media endpoints ([MSC3916](https://github.com/matrix-org" -"/matrix-spec-proposals/pull/3916)) requires MMR to have a configured " -"signing key to authorize outbound federation requests. Additionally, the " -"signing key must be merged with your homeserver's signing key file." +msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:97 -msgid "" -"The playbook default is to generate a MMR signing key when invoking the " -"setup role and merge it with your homeserver if you are using Synapse or " -"Dendrite. This can be disabled if desired by setting the option in your " -"inventory:" +msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:103 -msgid "" -"If you wish to manually generate the signing key and merge it with your " -"homeserver's signing key file, see https://docs.t2bot.io/matrix-media-" -"repo/v1.3.5/installation/signing-key/ for more details." +msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:105 -msgid "" -"**Note that if you uninstall MMR from the playbook, it will not remove " -"the old MMR signing key from your homeserver's signing key file. You will" -" have to remove it manually.**" +msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:107 @@ -151,20 +105,11 @@ msgid "Key backup and revoking" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:109 -msgid "" -"Since your homeserver signing key file is modified by the playbook, a " -"backup will be created in " -"`HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to " -"remove/revoke old keys, you can restore from this backup or remove the " -"MMR key ID from your `example.com.signing.key` file." +msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:111 -msgid "" -"Additionally, its recommended after revoking a signing key to update your" -" homeserver config file (`old_signing_keys` field for Synapse and " -"`old_private_keys` for Dendrite). See your homeserver config file for " -"further documentation on how to populate the field." +msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:113 @@ -172,25 +117,15 @@ msgid "Importing data from an existing media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:115 -msgid "" -"If you want to add this repo to an existing homeserver managed by the " -"playbook, you will need to import existing media into MMR's database or " -"you will lose access to older media while it is active. MMR versions up " -"to `v1.3.3` only support importing from Synapse, but newer versions (at " -"time of writing: only `latest`) also support importing from Dendrite." +msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:117 -msgid "" -"**Before importing**: ensure you have an initial matrix-media-repo " -"deployment by following the [quickstart](#quickstart) guide above" +msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:119 -msgid "" -"Depending on the homeserver implementation yu're using (Synapse, " -"Dendrite), you'll need to use a different import tool (part of matrix-" -"media-repo) and point it to the homeserver's database." +msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:121 @@ -198,40 +133,26 @@ msgid "Importing data from the Synapse media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:123 -msgid "" -"To import the Synapse media store, you're supposed to invoke the " -"`import_synapse` tool which is part of the matrix-media-repo container " -"image. Your Synapse database is called `synapse` by default, unless " -"you've changed it by modifying `matrix_synapse_database_database`." +msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:125 -msgid "" -"This guide here is adapted from the [upstream documentation about the " -"import_synapse script](https://github.com/turt2live/matrix-media-repo" -"#importing-media-from-synapse)." +msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:127 #: ../../../docs/configuring-playbook-matrix-media-repo.md:149 -msgid "" -"Run the following command on the server (after replacing " -"`postgres_connection_password` in it with the value found in your " -"`vars.yml` file):" +msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:139 #: ../../../docs/configuring-playbook-matrix-media-repo.md:161 -msgid "" -"Enter `1` for the Machine ID when prompted (you are not doing any " -"horizontal scaling) unless you know what you're doing." +msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:141 #: ../../../docs/configuring-playbook-matrix-media-repo.md:163 -msgid "" -"This should output a `msg=\"Import completed\"` when finished " -"successfully!" +msgid "This should output a `msg=\"Import completed\"` when finished successfully!" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:143 @@ -239,18 +160,9 @@ msgid "Importing data from the Dendrite media store" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:145 -msgid "" -"If you're using the [Dendrite](configuring-playbook-dendrite.md) " -"homeserver instead of the default for this playbook (Synapse), follow " -"this importing guide here." +msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here." msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:147 -msgid "" -"To import the Dendrite media store, you're supposed to invoke the " -"`import_dendrite` tool which is part of the matrix-media-repo container " -"image. Your Dendrite database is called `dendrite_mediaapi` by default, " -"unless you've changed it by modifying " -"`matrix_dendrite_media_api_database`." +msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po index 3448174f7..40876be5f 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 @@ -25,35 +25,23 @@ msgid "Setting up matrix-registration (optional)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:3 -msgid "" -"The playbook can install and configure [matrix-" -"registration](https://github.com/ZerataX/matrix-registration) for you." +msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:5 -msgid "" -"**WARNING**: this is a poorly maintained and buggy project. It's better " -"to avoid using it." +msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:7 -msgid "" -"**WARNING**: this is not related to [matrix-registration-bot" -"](configuring-playbook-bot-matrix-registration-bot.md)" +msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:9 -msgid "" -"matrix-registration is a simple python application to have a token based " -"Matrix registration." +msgid "matrix-registration is a simple python application to have a token based Matrix registration." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:11 -msgid "" -"Use matrix-registration to **create unique registration links**, which " -"people can use to register on your Matrix server. It allows you to **keep" -" your server's registration closed (private)**, but still allow certain " -"people (these having a special link) to register a user account." +msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:13 @@ -61,17 +49,11 @@ msgid "**matrix-registration** provides 2 things:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:15 -msgid "" -"**an API for creating registration tokens** (unique registration links). " -"This API can be used via `curl` or via the playbook (see [Usage](#usage) " -"below)" +msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:17 -msgid "" -"**a user registration page**, where people can use these registration " -"tokens. By default, exposed at `https://matrix.example.com/matrix-" -"registration`" +msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:19 @@ -79,9 +61,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:21 -msgid "" -"To enable matrix-registration, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:30 @@ -89,26 +69,15 @@ msgid "Adjusting the matrix-registration URL" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:32 -msgid "" -"By default, this playbook installs the matrix-registration on the " -"`matrix.` subdomain, at the `/matrix-registration` path " -"(https://matrix.example.com/matrix-registration). This makes it easy to " -"install it, because it **doesn't require additional DNS records to be set" -" up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:34 -msgid "" -"By tweaking the `matrix_registration_hostname` and " -"`matrix_registration_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:36 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:44 @@ -116,10 +85,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:46 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the matrix-registration domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:48 @@ -127,9 +93,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:50 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:52 @@ -137,26 +101,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:54 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:65 @@ -164,17 +117,11 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:67 -msgid "" -"**matrix-registration** gets exposed at `https://matrix.example.com" -"/matrix-registration`" +msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:69 -msgid "" -"It provides various [APIs](https://github.com/ZerataX/matrix-" -"registration/wiki/api) - for creating registration tokens, listing " -"tokens, disabling tokens, etc. To make use of all of its capabilities, " -"consider using `curl`." +msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:71 @@ -190,16 +137,11 @@ msgid "To **create a new user registration token (link)**, use this command:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:83 -msgid "" -"The above command creates and returns a **one-time use** token, which " -"**expires** on the 31st of December 2021. Adjust the `one_time` and " -"`ex_date` variables as you see fit." +msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:85 -msgid "" -"Share the unique registration link (generated by the command above) with " -"users to let them register on your Matrix server." +msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server." msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:87 @@ -211,8 +153,5 @@ msgid "To **list the existing user registration tokens**, use this command:" msgstr "" #: ../../../docs/configuring-playbook-matrix-registration.md:96 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags list-matrix-registration-tokens`" +msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po index c6c954d3f..be3cde9a5 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po @@ -25,18 +25,11 @@ msgid "Setting up a Generic Mautrix Bridge (optional)" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:3 -msgid "" -"The playbook can install and configure various " -"[mautrix](https://github.com/mautrix) bridges (twitter, facebook, " -"instagram, signal, hangouts, googlechat, etc.), as well as many other " -"(non-mautrix) bridges. This is a common guide for configuring mautrix " -"bridges." +msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:5 -msgid "" -"You can see each bridge's features at in the `ROADMAP.md` file in its " -"corresponding [mautrix](https://github.com/mautrix) repository." +msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:7 @@ -44,34 +37,19 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:9 -msgid "" -"To enable the bridge, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:16 -msgid "" -"There are some additional things you may wish to configure about the " -"bridge before you continue. Each bridge may have additional requirements " -"besides `_enabled: true`. For example, the mautrix-telegram bridge (our " -"documentation page about it is [here](configuring-playbook-bridge-" -"mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and " -"`matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each" -" bridge's individual documentation page for details about enabling " -"bridges." +msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:18 -msgid "" -"To **configure a user as an administrator for all bridges**, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:24 -msgid "" -"**Alternatively** (more verbose, but allows multiple admins to be " -"configured), you can do the same on a per-bridge basis with:" +msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:33 @@ -79,10 +57,7 @@ msgid "encryption" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:35 -msgid "" -"Encryption support is off by default. If you would like to enable " -"encryption, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:37 @@ -99,10 +74,7 @@ msgid "relay mode" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:53 -msgid "" -"Relay mode is off by default. If you would like to enable relay mode, add" -" the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:55 @@ -110,11 +82,7 @@ msgid "**for all bridges with relay mode support**:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:70 -msgid "" -"You can only have one " -"`matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in " -"`vars.yml` per bridge, so if you need multiple pieces of configuration " -"there, just merge them like this:" +msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:82 @@ -130,11 +98,7 @@ msgid "Discovering additional configuration options" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:92 -msgid "" -"You may wish to look at `roles/custom/matrix-bridge-mautrix-" -"SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-" -"mautrix-SERVICENAME/defaults/main.yml` to find other things you would " -"like to configure." +msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:94 @@ -142,9 +106,7 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:96 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:103 @@ -152,24 +114,15 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:105 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:107 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:109 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:111 @@ -177,24 +130,15 @@ msgid "Set up Double Puppeting" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:113 -msgid "" -"To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-" -"puppeting.html) enable the [Appservice Double Puppet](configuring-" -"playbook-appservice-double-puppet.md) service for this playbook." +msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:115 -msgid "" -"The bridge automatically performs Double Puppeting if [Shared Secret Auth" -"](configuring-playbook-shared-secret-auth.md) is configured and enabled " -"on the server for this playbook by adding" +msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:121 -msgid "" -"This is the recommended way of setting up Double Puppeting, as it's " -"easier to accomplish, works for all your users automatically, and has " -"less of a chance of breaking in the future." +msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:123 @@ -202,16 +146,11 @@ msgid "Controlling the logging level" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:129 -msgid "" -"to `vars.yml` to control the logging level, where you may replace WARN " -"with one of the following to control the verbosity of the logs generated:" -" TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." +msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:131 -msgid "" -"If you have issues with a service, and are requesting support, the higher" -" levels of logging will generally be more helpful." +msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:133 @@ -219,24 +158,15 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:135 -msgid "" -"To use the bridge, you need to start a chat with " -"`@SERVICENAMEbot:example.com` (where `example.com` is your base domain, " -"not the `matrix.` domain)." +msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:137 -msgid "" -"Send `login` to the bridge bot to get started. You can learn more here " -"about authentication from the bridge's official documentation on " -"Authentication: " -"https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" +msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:139 -msgid "" -"If you run into trouble, check the [Troubleshooting](#troubleshooting) " -"section below." +msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:141 @@ -244,16 +174,9 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:143 -msgid "" -"For troubleshooting information with a specific bridge, please see the " -"playbook documentation about it (some other document in in `docs/`) and " -"the upstream ([mautrix](https://github.com/mautrix)) bridge documentation" -" for that specific bridge." +msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge." msgstr "" #: ../../../docs/configuring-playbook-mautrix-bridges.md:145 -msgid "" -"Reporting bridge bugs should happen upstream, in the corresponding " -"mautrix repository, not to us." +msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po index 44ec0eb4a..b5899561a 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po @@ -27,4 +27,3 @@ msgstr "" #: ../../../docs/configuring-playbook-nginx.md:3 msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po index e0c597e65..5caa7e81c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po @@ -25,33 +25,19 @@ msgid "Setting up the ntfy push notifications server (optional)" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:3 -msgid "" -"The playbook can install and configure the [ntfy](https://ntfy.sh/) push " -"notifications server for you." +msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:5 -msgid "" -"Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables " -"self-hosted (Google-free) push notifications from Matrix (and other) " -"servers to UnifiedPush-compatible Matrix compatible client apps running " -"on Android and other devices." +msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:7 -msgid "" -"This role is intended to support UnifiedPush notifications for use with " -"the Matrix and Matrix-related services that this playbook installs. This " -"role is not intended to support all of ntfy's other features." +msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:9 -msgid "" -"**Note**: In contrast to push notifications using Google's FCM or Apple's" -" APNs, the use of UnifiedPush allows each end-user to choose the push " -"notification server that they prefer. As a consequence, deploying this " -"ntfy server does not by itself ensure any particular user or device or " -"client app will use it." +msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:11 @@ -59,23 +45,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:13 -msgid "" -"To enable ntfy, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:27 -msgid "" -"For a more complete list of variables that you could override, see the " -"[`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting" -"/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." +msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:29 -msgid "" -"For a complete list of ntfy config options that you could put in " -"`ntfy_configuration_extension_yaml`, see the [ntfy config " -"documentation](https://ntfy.sh/docs/config/#config-options)." +msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:31 @@ -83,22 +61,15 @@ msgid "Adjusting the ntfy URL" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:33 -msgid "" -"By default, this playbook installs ntfy on the `ntfy.` subdomain " -"(`ntfy.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:35 -msgid "" -"By tweaking the `ntfy_hostname` variable, you can easily make the service" -" available at a **different hostname** than the default one." +msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:37 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:44 @@ -106,15 +77,11 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:46 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the ntfy domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:48 -msgid "" -"By default, you will need to create a CNAME record for `ntfy`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:50 @@ -122,26 +89,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:52 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:59 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:61 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:63 @@ -149,9 +105,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:65 -msgid "" -"To make use of your ntfy installation, on Android for example, you need " -"two things:" +msgid "To make use of your ntfy installation, on Android for example, you need two things:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:67 @@ -163,11 +117,7 @@ msgid "a UnifiedPush-compatible Matrix app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:70 -msgid "" -"You need to install the `ntfy` app on each device on which you want to " -"receive push notifications through your ntfy server. The `ntfy` app will " -"provide UnifiedPush notifications to any number of UnifiedPush-compatible" -" messaging apps installed on the same device." +msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:72 @@ -175,15 +125,11 @@ msgid "Setting up the `ntfy` Android app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:74 -msgid "" -"Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) " -"from F-droid or Google Play." +msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:75 -msgid "" -"In its Settings -> `General: Default server`, enter your ntfy server URL," -" such as `https://ntfy.example.com`." +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 @@ -191,11 +137,7 @@ 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." +msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:80 @@ -203,11 +145,7 @@ msgid "Setting up a UnifiedPush-compatible Matrix app" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:82 -msgid "" -"Install any UnifiedPush-enabled Matrix app on that same device. The " -"Matrix app will learn from the `ntfy` app that you have configured " -"UnifiedPush on this device, and then it will tell your Matrix server to " -"use it." +msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:84 @@ -227,23 +165,15 @@ msgid "SchildiChat-android:" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:90 -msgid "" -"enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push " -"gateway`." +msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:91 -msgid "" -"choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push " -"distributor`. *(For info, a more complex alternative to achieve the same " -"is: delete the relevant unifiedpush registration in `ntfy` app, force-" -"close SchildiChat, re-open it.)*" +msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:92 -msgid "" -"verify `Settings` -> `Notifications` -> `UnifiedPush: Notification " -"targets` as described below in the \"Troubleshooting\" section." +msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:94 @@ -255,21 +185,15 @@ msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:96 -msgid "" -"verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification " -"settings`" +msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:98 -msgid "" -"If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", " -"then choose \"ntfy\"." +msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:100 -msgid "" -"If the Matrix app doesn't seem to pick it up, try restarting it and try " -"the Troubleshooting section below." +msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:102 @@ -277,20 +201,11 @@ msgid "Web App" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:104 -msgid "" -"ntfy also has a web app to subscribe to and push to topics from the " -"browser. This may be helpful to further troubleshoot UnifiedPush problems" -" or to use ntfy for other purposes. The web app only runs in the browser " -"locally (after downloading the JavaScript)." +msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:106 -msgid "" -"The web app is disabled in this playbook by default as the expectation is" -" that most users won't use it. You can either use the [official hosted " -"one](https://ntfy.sh/app) (it supports using other public reachable ntfy " -"instances) or host it yourself by setting `ntfy_web_root: \"app\"` and " -"re-running Ansible." +msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:108 @@ -298,57 +213,25 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:110 -msgid "" -"First check that the Matrix client app you are using supports " -"UnifiedPush. There may well be different variants of the app." +msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:112 -msgid "" -"Set the ntfy server's log level to 'DEBUG', as shown in the example " -"settings above, and watch the server's logs with `sudo journalctl -fu " -"matrix-ntfy`." +msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:114 -msgid "" -"To check if UnifiedPush is correctly configured on the client device, " -"look at \"Settings -> Notifications -> Notification Targets\" in Element " -"Android or SchildiChat Android, or \"Settings -> Notifications -> " -"Devices\" in FluffyChat. There should be one entry for each Matrix client" -" app that has enabled push notifications, and when that client is using " -"UnifiedPush you should see a URL that begins with your ntfy server's URL." +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." +msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:118 -msgid "" -"If it is not working, useful tools are \"Settings -> Notifications -> Re-" -"register push distributor\" and \"Settings -> Notifications -> " -"Troubleshoot Notifications\" in SchildiChat Android (possibly also " -"Element Android). In particular the \"Endpoint/FCM\" step of that " -"troubleshooter should display your ntfy server's URL that it has " -"discovered from the ntfy client app." +msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app." msgstr "" #: ../../../docs/configuring-playbook-ntfy.md:120 -msgid "" -"The simple [UnifiedPush " -"troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-" -"Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be" -" used to manually test UnifiedPush registration and operation on an " -"Android device." +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 ac2916d9c..290a02620 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 @@ -21,16 +21,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-own-webserver.md:1 -msgid "" -"Using your own webserver, instead of this playbook's Traefik reverse-" -"proxy (optional, advanced)" +msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:3 -msgid "" -"By default, this playbook installs its own [Traefik](https://traefik.io/)" -" reverse-proxy server (in a Docker container) which listens on ports 80 " -"and 443. If that's okay, you can skip this document." +msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:5 @@ -38,24 +33,15 @@ msgid "Traefik" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:7 -msgid "" -"[Traefik](https://traefik.io/) is the default reverse-proxy for the " -"playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 " -"purposes**:" +msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:9 -msgid "" -"serving public traffic and providing SSL-termination with certificates " -"obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting " -"SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." +msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:11 -msgid "" -"assists internal communication between addon services (briges, bots, " -"etc.) and the homeserver via an internal entrypoint (`matrix-internal-" -"matrix-client-api`)." +msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:13 @@ -67,10 +53,7 @@ msgid "Traefik managed by the playbook" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:17 -msgid "" -"To have the playbook install and use Traefik, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:25 @@ -82,15 +65,11 @@ msgid "Traefik managed by you" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:53 -msgid "" -"In this mode all roles will still have Traefik labels attached. You will," -" however, need to configure your Traefik instance and its entrypoints." +msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:55 -msgid "" -"By default, the playbook configured a `default` certificate resolver and " -"multiple entrypoints." +msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:57 @@ -102,42 +81,27 @@ msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:60 -msgid "" -"`web-secure` (TCP port `443`) - used for exposing the Matrix Client-" -"Server API and all other services" +msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:61 -msgid "" -"`matrix-federation` (TCP port `8448`) - used for exposing the Matrix " -"Federation API" +msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:62 -msgid "" -"`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally " -"for addon services (bridges, bots) to communicate with the homserver" +msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:64 -msgid "" -"Below is some configuration for running Traefik yourself, although we " -"recommend using [Traefik managed by the playbook](#traefik-managed-by-" -"the-playbook)." +msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:66 -msgid "" -"Note that this configuration on its own does **not** redirect traffic on " -"port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing " -"this in Traefik, it can be added to Traefik in a [file " -"provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" +msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:86 -msgid "" -"You can use the following `docker-compose.yml` as example to launch " -"Traefik." +msgid "You can use the following `docker-compose.yml` as example to launch Traefik." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:122 @@ -157,22 +121,11 @@ msgid "There are 2 ways to go about it:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:130 -msgid "" -"(recommended) [Fronting the integrated reverse-proxy webserver with " -"another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-" -"with-another-reverse-proxy) - using the playbook-managed reverse-proxy " -"(Traefik), but disabling SSL termination for it, exposing this reverse-" -"proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding " -"traffic from your own webserver to those few ports" +msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:132 -msgid "" -"(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-" -"reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed " -"reverse-proxy (Traefik), exposing services one by one using " -"`_host_bind_port` variables and forwarding traffic from your own " -"webserver to those ports" +msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:134 @@ -180,57 +133,31 @@ msgid "Fronting the integrated reverse-proxy webserver with another reverse-prox msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:136 -msgid "" -"This method is about leaving the integrated reverse-proxy webserver be, " -"but making it not get in the way (using up important ports, trying to " -"retrieve SSL certificates, etc.)." +msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:138 -msgid "" -"If you wish to use another webserver, the integrated reverse-proxy " -"webserver usually gets in the way because it attempts to fetch SSL " -"certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is" -" enabled)." +msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:140 -msgid "" -"You can disable such behavior and make the integrated reverse-proxy " -"webserver only serve traffic locally on the host itself (or over a local " -"network)." +msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:142 -msgid "" -"This is the recommended way for using another reverse-proxy, because the " -"integrated one would act as a black box and wire all Matrix services " -"correctly. You would then only need to reverse-proxy a few individual " -"domains and ports over to it." +msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:144 -msgid "" -"To front Traefik with another reverse-proxy, you would need some " -"configuration like this:" +msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:194 -msgid "" -"Such a configuration would expose all services on a local port `81` and " -"Matrix Federation on a local port `8449`. Your reverse-proxy " -"configuration needs to send traffic to these ports. [`examples/reverse-" -"proxies`](../examples/reverse-proxies/) contains examples for various " -"webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy " -"Manager." +msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:196 -msgid "" -"It's important that these webservers proxy-pass requests to the correct " -"`ip:port` and also set the `Host` HTTP header appropriately. If you don't" -" pass the `Host` header correctly, Traefik will return a `404 - not " -"found` error." +msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:198 @@ -250,42 +177,17 @@ msgid "Using no reverse-proxy on the Matrix side at all" msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:204 -msgid "" -"Instead of [Fronting the integrated reverse-proxy webserver with another " -"reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-" -"another-reverse-proxy), you can also go another way -- completely " -"disabling the playbook-managed Traefik reverse-proxy. You would then need" -" to reverse-proxy from your own webserver directly to each individual " -"Matrix service." +msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:206 -msgid "" -"This is more difficult, as you would need to handle the configuration for" -" each service manually. Enabling additional services would come with " -"extra manual work you need to do." +msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:208 -msgid "" -"Also, the Traefik reverse-proxy, besides fronting everything is also " -"serving a 2nd purpose of allowing addons services to communicate with the" -" Matrix homeserver thanks to its `matrix-internal-matrix-client-api` " -"entrypoint (read more about it above). Disabling Traefik completely means" -" the playbook would wire services to directly talk to the homeserver. " -"This can work for basic setups, but not for more complex setups involving" -" [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), " -"[matrix-corporal](./configuring-playbook-matrix-corporal.md) or other " -"such services that need to \"steal routes\" from the homeserver." +msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver." msgstr "" #: ../../../docs/configuring-playbook-own-webserver.md:210 -msgid "" -"If your webserver is on the same machine, ensure your web server user " -"(something like `http`, `apache`, `www-data`, `nginx`) is part of the " -"`matrix` group. You should run something like this: `usermod -a -G matrix" -" nginx`. This allows your webserver user to access files owned by the " -"`matrix` group, so that it can serve static files from `/matrix/static-" -"files`." +msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po index 4e47061d4..ace9e5689 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po @@ -25,26 +25,15 @@ msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:3 -msgid "" -"The playbook can install and configure the " -"[pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy" -" daemon for you." +msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/pantalaimon/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:7 -msgid "" -"This role exposes Pantalaimon's API only within the container network, so" -" bots and clients installed on the same machine can use it. In particular" -" the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir" -"](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can " -"use it." +msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:9 @@ -52,17 +41,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:17 -msgid "" -"The default configuration should suffice. For advanced configuration, you" -" can override the variables documented in the role's " -"[defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." +msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:19 @@ -70,31 +53,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:21 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:28 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-pantalaimon.md:30 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/pantalaimon) to learn what it" -#~ " does and why it might be " -#~ "useful to you." -#~ 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 2b01acb85..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 @@ -25,18 +25,11 @@ 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." +msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:5 -msgid "" -"For a more complete backup solution (one that includes not only Postgres," -" but also other configuration/data files), you may wish to look into " -"[BorgBackup](configuring-playbook-backup-borg.md) instead." +msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:7 @@ -44,15 +37,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:9 -msgid "" -"To enable Postgres backup, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:15 -msgid "" -"Refer to the table below for additional configuration variables and their" -" default values." +msgid "Refer to the table below for additional configuration variables and their default values." msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md @@ -76,10 +65,7 @@ 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" +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 @@ -159,24 +145,13 @@ 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:" +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`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-postgres-backup.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 a1364f30f..9c69c7e0d 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 @@ -21,16 +21,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-prometheus-grafana.md:1 -msgid "" -"Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server " -"(optional)" +msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:3 -msgid "" -"The playbook can install [Grafana](https://grafana.com/) with " -"[Prometheus](https://prometheus.io/) and configure performance metrics of" -" your homeserver with graphs for you." +msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:5 @@ -38,16 +33,11 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:7 -msgid "" -"To enable Grafana and/or Prometheus, add the following configuration to " -"your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:33 -msgid "" -"The retention policy of Prometheus metrics is [15 days by " -"default](https://prometheus.io/docs/prometheus/latest/storage" -"/#operational-aspects). Older data gets deleted automatically." +msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:35 @@ -55,22 +45,15 @@ msgid "Adjusting the Grafana URL" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:37 -msgid "" -"By default, this playbook installs Grafana web user-interface on the " -"`stats.` subdomain (`stats.example.com`) and requires you to [adjust your" -" DNS records](#adjusting-dns-records)." +msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:39 -msgid "" -"By tweaking the `grafana_hostname` variable, you can easily make the " -"service available at a **different hostname** than the default one." +msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:41 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:48 @@ -78,21 +61,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:50 -msgid "" -"Once you've decided on the domain, **you may need to adjust your DNS** " -"records to point the Grafana domain to the Matrix server." +msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:52 -msgid "" -"By default, you will need to create a CNAME record for `stats`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:54 -msgid "" -"**Note**: It is possible to install Prometheus without installing " -"Grafana. This case it is not required to create the CNAME record." +msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:56 @@ -100,26 +77,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:58 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:65 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:67 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:69 @@ -139,9 +105,7 @@ msgid "`prometheus_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Prometheus](https://prometheus.io) is a time series database. It holds " -"all the data we're going to talk about." +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 @@ -149,10 +113,7 @@ msgid "`prometheus_node_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an " -"addon of sorts to Prometheus that collects generic system information " -"such as CPU, memory, filesystem, and even system temperatures" +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 @@ -160,9 +121,7 @@ msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an " -"addon of sorts to expose Postgres database metrics to Prometheus." +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 @@ -170,9 +129,7 @@ msgid "`matrix_prometheus_nginxlog_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an " -"addon of sorts to expose NGINX logs to Prometheus." +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 @@ -180,10 +137,7 @@ msgid "`grafana_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"[Grafana](https://grafana.com/) is the visual component. It shows (on the" -" `stats.example.com` subdomain) the dashboards with the graphs that we're" -" interested in" +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 @@ -191,11 +145,7 @@ msgid "`grafana_anonymous_access`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"By default you need to log in to see graphs. If you want to publicly " -"share your graphs (e.g. when asking for help in " -"[`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org))" -" you'll want to enable this option." +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 @@ -203,10 +153,7 @@ msgid "`grafana_default_admin_user`
`grafana_default_admin_password`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"By default Grafana creates a user with `admin` as the username and " -"password. If you feel this is insecure and you want to change it " -"beforehand, you can do that here" +msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:81 @@ -214,24 +161,11 @@ msgid "Security and privacy" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:83 -msgid "" -"Metrics and resulting graphs can contain a lot of information. This " -"includes system specs but also usage patterns. This applies especially to" -" small personal/family scale homeservers. Someone might be able to figure" -" out when you wake up and go to sleep by looking at the graphs over time." -" Think about this before enabling anonymous access. And you should really" -" not forget to change your Grafana password." +msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:85 -msgid "" -"Most of our docker containers run with limited system access, but the " -"`prometheus-node-exporter` has access to the host network stack and " -"(readonly) root filesystem. This is required to report on them. If you " -"don't like that, you can set `prometheus_node_exporter_enabled: false` " -"(which is actually the default). You will still get Synapse metrics with " -"this container disabled. Both of the dashboards will always be enabled, " -"so you can still look at historical data after disabling either source." +msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:87 @@ -239,37 +173,19 @@ msgid "Collecting metrics to an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:89 -msgid "" -"**If the integrated Prometheus server is enabled** (`prometheus_enabled: " -"true`), metrics are collected by it from each service via communication " -"that happens over the container network. Each service does not need to " -"expose its metrics \"publicly\"." +msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:91 -msgid "" -"When you'd like **to collect metrics from an external Prometheus " -"server**, you need to expose service metrics outside of the container " -"network." +msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:93 -msgid "" -"The playbook provides a single endpoint " -"(`https://matrix.example.com/metrics/*`), under which various services " -"may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics" -"/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on" -" this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To " -"protect access using [Basic " -"Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)," -" see `matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users` below." +msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:95 -msgid "" -"When using `matrix_metrics_exposure_enabled`, you don't need to expose " -"metrics for individual services one by one." +msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:97 @@ -281,12 +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/*`. 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." +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 @@ -294,13 +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). " -"When enabled, all endpoints beneath `/metrics` will be protected with the" -" same 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 @@ -308,11 +213,7 @@ msgid "`matrix_metrics_exposure_http_basic_auth_users`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to the Basic Authentication credentials (raw `htpasswd` file " -"content) used to protect `/metrics/*`. This htpasswd-file needs to be " -"generated with the `htpasswd` tool and can include multiple " -"username/password pairs." +msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -320,9 +221,7 @@ msgid "`matrix_synapse_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make Synapse expose metrics (locally, on the " -"container network)" +msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md @@ -330,20 +229,11 @@ msgid "`matrix_synapse_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose Synapse's metrics on " -"`https://matrix.example.com/metrics/synapse/main-process` and " -"`https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below" -"](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if" -" you're running a Synapse worker setup (`matrix_synapse_workers_enabled: " -"true`). To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the node (general system stats) exporter " -"(locally, on the container network)" +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 @@ -351,16 +241,11 @@ msgid "`prometheus_node_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the node (general system stats) metrics on " -"`https://matrix.example.com/metrics/node-exporter`. To password-protect " -"the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." +msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the [Postgres exporter](configuring-" -"playbook-prometheus-postgres.md) (locally, on the container network)" +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 @@ -368,18 +253,11 @@ msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Postgres exporter](configuring-" -"playbook-prometheus-postgres.md) metrics on " -"`https://matrix.example.com/metrics/postgres-exporter`. To password-" -"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " -"above." +msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to enable the [NGINX Log exporter](configuring-" -"playbook-prometheus-nginxlog.md) (locally, on the container network)" +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 @@ -387,9 +265,7 @@ msgid "`matrix_sliding_sync_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-" -"sync-proxy.md) expose metrics (locally, on the container network)" +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 @@ -397,11 +273,7 @@ msgid "`matrix_sliding_sync_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Sliding Sync](configuring-playbook-" -"sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics" -"/sliding-sync`. To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +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 @@ -409,9 +281,7 @@ msgid "`matrix_bridge_hookshot_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make [Hookshot](configuring-playbook-bridge-" -"hookshot.md) expose metrics (locally, on the container network)" +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 @@ -419,11 +289,7 @@ msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-" -"hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To" -" password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above." +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 @@ -431,13 +297,7 @@ msgid "`matrix_SERVICE_metrics_proxying_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Various other services/roles may provide similar `_metrics_enabled` and " -"`_metrics_proxying_enabled` variables for exposing their metrics. Refer " -"to each role for details. To password-protect the metrics, see " -"`matrix_metrics_exposure_http_basic_auth_users` above or " -"`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users`" -" variables provided by each role." +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 @@ -445,9 +305,7 @@ msgid "`matrix_media_repo_metrics_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md -msgid "" -"Set this to `true` to make media-repo expose metrics (locally, on the " -"container network)" +msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:118 @@ -455,23 +313,11 @@ msgid "Collecting Synapse worker metrics to an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:120 -msgid "" -"If you are using workers (`matrix_synapse_workers_enabled: true`) and " -"have enabled `matrix_synapse_metrics_proxying_enabled` as described " -"above, the playbook will also automatically expose all Synapse worker " -"threads' metrics to " -"`https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` " -"corresponds to the worker `id` as exemplified in " -"`matrix_synapse_workers_enabled_list`." +msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`." msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:122 -msgid "" -"The playbook also generates an exemplary config file " -"(`/matrix/synapse/external_prometheus.yml.template`) with all the correct" -" paths which you can copy to your Prometheus server and adapt to your " -"needs. Make sure to edit the specified `password_file` path and contents " -"and path to your `synapse-v2.rules`. It will look a bit like this:" +msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:150 @@ -479,34 +325,21 @@ msgid "More information" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:152 -msgid "" -"[Enabling synapse-usage-exporter for Synapse usage statistics" -"](configuring-playbook-synapse-usage-exporter.md)" +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:153 -msgid "" -"[Understanding Synapse Performance Issues Through Grafana Graphs](https" -"://element-" -"hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html)" -" at the Synapse Github Wiki" +msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:154 -msgid "" -"[The Prometheus scraping rules](https://github.com/element-" -"hq/synapse/tree/master/contrib/prometheus) (we use v2)" +msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:155 -msgid "" -"[The Synapse Grafana dashboard](https://github.com/element-" -"hq/synapse/tree/master/contrib/grafana)" +msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-grafana.md:156 -msgid "" -"[The Node Exporter dashboard](https://github.com/rfrail3/grafana-" -"dashboards) (for generic non-synapse performance graphs)" +msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po index 3f33df892..24ad7ec2b 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po @@ -25,45 +25,27 @@ msgid "Enabling metrics and graphs for NginX logs (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3 -msgid "" -"It can be useful to have some (visual) insight into " -"[nginx](https://nginx.org/) logs." +msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5 -msgid "" -"This adds [prometheus-nginxlog-exporter](https://github.com/martin-" -"helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." +msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7 -msgid "" -"It will collect access logs from various nginx reverse-proxies which may " -"be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if " -"Synapse workers are enabled) and will make them available at a " -"Prometheus-compatible `/metrics` endpoint." +msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9 -msgid "" -"**Note**: nginx is only used internally by this Ansible playbook. With " -"Traefik being our default reverse-proxy, collecting nginx metrics is less" -" relevant." +msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11 -msgid "" -"To make use of this, you need to install [Prometheus](./configuring-" -"playbook-prometheus-grafana.md) either via the playbook or externally. " -"When using an external Prometheus, configuration adjustments are " -"necessary - see [Save metrics on an external Prometheus server](#save-" -"metrics-on-an-external-prometheus-server)." +msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13 -msgid "" -"If your setup includes [Grafana](./configuring-playbook-prometheus-" -"grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." +msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15 @@ -71,9 +53,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23 @@ -81,25 +61,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:36 @@ -107,11 +77,7 @@ msgid "Docker Image Compatibility" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38 -msgid "" -"At the moment of writing only images for `amd64` and `arm64` " -"architectures are available. The playbook currently does not support " -"[self-building](./self-building.md) a container image on other " -"architectures. You can however use a custom-build image by setting:" +msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45 @@ -119,13 +85,7 @@ msgid "Security and privacy" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47 -msgid "" -"Metrics and resulting graphs can contain a lot of information. NginX logs" -" contain information like IP address, URLs, UserAgents and more. This " -"information can reveal usage patterns and could be considered Personally " -"Identifiable Information (PII). Think about this before enabling " -"(anonymous) access. Please make sure you change the default Grafana " -"password." +msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49 @@ -133,44 +93,21 @@ msgid "Save metrics on an external Prometheus server" msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51 -msgid "" -"The playbook will automatically integrate the metrics into the " -"[Prometheus](./configuring-playbook-prometheus-grafana.md) server " -"provided with this playbook (if enabled). In such cases, the metrics " -"endpoint is not exposed publicly - it's only available on the container " -"network." +msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53 -msgid "" -"When using an external Prometheus server, you'll need to expose metrics " -"publicly. See [Collecting metrics to an external Prometheus server" -"](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-" -"external-prometheus-server)." +msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55 -msgid "" -"You can either use " -"`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to " -"expose just this one service, or `matrix_metrics_exposure_enabled: true` " -"to expose all services." +msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57 -msgid "" -"Whichever way you go with, this service will expose its metrics endpoint " -"**without password-protection** at " -"`https://matrix.example.com/metrics/nginxlog` by default." +msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default." msgstr "" #: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59 -msgid "" -"For password-protection, use " -"(`matrix_metrics_exposure_http_basic_auth_enabled` and " -"`matrix_metrics_exposure_http_basic_auth_users`) or " -"(`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled`" -" and " -"`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." +msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po index 384f4fd51..c512d1462 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po @@ -25,12 +25,7 @@ msgid "Enabling metrics and graphs for Postgres (optional)" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:3 -msgid "" -"Expanding on the metrics exposed by the [synapse exporter and the node " -"exporter](configuring-playbook-prometheus-grafana.md), the playbook " -"enables the [postgres exporter](https://github.com/prometheus-" -"community/postgres_exporter) that exposes more detailed information about" -" what's happening on your postgres database." +msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:5 @@ -38,9 +33,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:7 -msgid "" -"To enable the postgres exporter, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:13 @@ -48,25 +41,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:15 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:22 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:24 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:26 @@ -86,11 +69,7 @@ msgid "`prometheus_postgres_exporter_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"Enable the postgres prometheus exporter. This sets up the docker " -"container, connects it to the database and adds a 'job' to the prometheus" -" config which tells prometheus about this new exporter. The default is " -"'false'" +msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -98,9 +77,7 @@ msgid "`prometheus_postgres_exporter_database_username`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"The 'username' for the user that the exporter uses to connect to the " -"database. The default is 'matrix_prometheus_postgres_exporter'" +msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -108,9 +85,7 @@ msgid "`prometheus_postgres_exporter_database_password`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"The 'password' for the user that the exporter uses to connect to the " -"database. By default, this is auto-generated by the playbook" +msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md @@ -118,13 +93,7 @@ msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md -msgid "" -"If set to `true`, exposes the Postgres exporter metrics on " -"`https://matrix.example.com/metrics/postgres-exporter` for usage with an " -"[external Prometheus server](configuring-playbook-prometheus-grafana.md" -"#collecting-metrics-to-an-external-prometheus-server). To password-" -"protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` " -"on that other documentation page." +msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page." msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:35 @@ -132,8 +101,5 @@ msgid "More information" msgstr "" #: ../../../docs/configuring-playbook-prometheus-postgres.md:37 -msgid "" -"[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) " -"(generic postgres dashboard)" +msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po index d12191917..c2afab62c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po @@ -25,15 +25,11 @@ msgid "Setting up the rageshake bug report server (optional)" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:3 -msgid "" -"The playbook can install and configure the [rageshake](https://github.com" -"/matrix-org/rageshake) bug report server for you." +msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:5 -msgid "" -"This is useful if you're developing your own applications and would like " -"to collect bug reports for them." +msgid "This is useful if you're developing your own applications and would like to collect bug reports for them." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:7 @@ -41,23 +37,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:9 -msgid "" -"To enable rageshake, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:15 -msgid "" -"rageshake has various options which don't have dedicated Ansible " -"variables. You can see the full list of options in the " -"[`rageshake.sample.yaml` file](https://github.com/matrix-" -"org/rageshake/blob/master/rageshake.sample.yaml)." +msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:17 -msgid "" -"To set these, you can make use of the " -"`matrix_rageshake_configuration_extension_yaml` variable like this:" +msgid "To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:27 @@ -65,23 +53,15 @@ msgid "Adjusting the rageshake URL" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:29 -msgid "" -"By default, this playbook installs rageshake on the `rageshake.` " -"subdomain (`rageshake.example.com`) and requires you to [adjust your DNS " -"records](#adjusting-dns-records)." +msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:31 -msgid "" -"By tweaking the `matrix_rageshake_hostname` and " -"`matrix_rageshake_path_prefix` variables, you can easily make the service" -" available at a **different hostname and/or path** than the default one." +msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:33 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:44 @@ -89,21 +69,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:46 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the rageshake domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:48 -msgid "" -"By default, you will need to create a CNAME record for `rageshake`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:50 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:52 @@ -111,26 +85,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:54 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:61 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:63 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:65 @@ -138,8 +101,5 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-rageshake.md:67 -msgid "" -"Refer to the [rageshake documentation](https://github.com/matrix-" -"org/rageshake) for available APIs, etc." +msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po index ec978d039..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 @@ -21,23 +21,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-rest-auth.md:1 -msgid "" -"Setting up the REST authentication password provider module (optional, " -"advanced)" +msgid "Setting up the REST authentication password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:3 -msgid "" -"The playbook can install and configure [matrix-synapse-rest-" -"auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) " -"for you." +msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/ma1uta/matrix-" -"synapse-rest-password-provider/blob/master/README.md) to learn what it " -"does and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:7 @@ -45,10 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:9 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:19 @@ -56,10 +45,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:21 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:27 @@ -67,30 +53,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:29 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:36 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-rest-auth.md:38 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po index d48c0f16c..6af9a9d9d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po @@ -25,29 +25,19 @@ msgid "Configuring Riot-web (optional)" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:3 -msgid "" -"By default, this playbook **used to install** the [Riot-" -"web](https://github.com/element-hq/riot-web) Matrix client web " -"application." +msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:5 -msgid "" -"Riot has since been [renamed to Element](https://element.io/blog/welcome-" -"to-element/)." +msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:7 -msgid "" -"to learn more about Element Web and its configuration, see our dedicated " -"[Configuring Element Web](configuring-playbook-client-element-web.md) " -"documentation page" +msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:8 -msgid "" -"to learn how to migrate from Riot to Element Web, see [Migrating to " -"Element Web](#migrating-to-element-web) below" +msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:10 @@ -59,17 +49,11 @@ msgid "Migrating your custom settings" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:14 -msgid "" -"If you have custom `matrix_riot_web_` variables in your " -"`inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to " -"rename them (`matrix_riot_web_` -> `matrix_client_element_`)." +msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:16 -msgid "" -"Some other playbook variables (but not all) with `riot` in their name are" -" also renamed. The playbook checks and warns if you are using the old " -"name for some commonly used ones." +msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:18 @@ -77,9 +61,7 @@ msgid "Domain migration" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:20 -msgid "" -"We used to set up Riot at the `riot.example.com` domain. The playbook now" -" sets up Element Web at `element.example.com` by default." +msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:22 @@ -87,18 +69,11 @@ msgid "There are a few options for handling this:" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:24 -msgid "" -"(**avoiding changes** - using the old `riot.example.com` domain and " -"avoiding DNS changes) -- to keep using `riot.example.com` instead of " -"`element.example.com`, override the domain at which the playbook serves " -"Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" +msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:26 -msgid "" -"(**embracing changes** - using only `element.example.com`) - set up the " -"`element.example.com` DNS record (see [Configuring DNS](configuring-" -"dns.md)). You can drop the `riot.example.com` in this case." +msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case." msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:28 @@ -106,24 +81,13 @@ msgid "Re-running the playbook" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:30 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:37 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-riot-web.md:39 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po index 801a550f1..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 @@ -25,31 +25,19 @@ msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:3 -msgid "" -"If you'd like to store Synapse's content repository (`media_store`) files" -" on Amazon S3 (or other S3-compatible service), you can let this playbook" -" configure [Goofys](https://github.com/kahing/goofys) for you." +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:5 -msgid "" -"Another (and better performing) way to use S3 storage with Synapse is " -"[synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-" -"provider.md)." +msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:7 -msgid "" -"Using a Goofys-backed media store works, but performance may not be " -"ideal. If possible, try to use a region which is close to your Matrix " -"server." +msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:9 -msgid "" -"If you'd like to move your locally-stored media store data to Amazon S3 " -"(or another S3-compatible object store), we also provide some migration " -"instructions below." +msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:11 @@ -57,25 +45,15 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:13 -msgid "" -"After [creating the S3 bucket and configuring it](configuring-" -"playbook-s3.md#bucket-creation-and-security-configuration), add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:23 -msgid "" -"You can use any S3-compatible object store by **additionally** " -"configuring these variables:" +msgid "You can use any S3-compatible object store by **additionally** configuring these variables:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:30 -msgid "" -"If you have local media store files and wish to migrate to Backblaze B2 " -"subsequently, follow our [migration guide to Backblaze B2](#migrating-to-" -"backblaze-b2) below instead of applying this configuration as-is." +msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:32 @@ -83,23 +61,15 @@ msgid "Migrating from local filesystem storage to S3" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:34 -msgid "" -"It's a good idea to [make a complete server backup](faq.md#how-do-i-back-" -"up-the-data-on-my-server) before migrating your local media store to an " -"S3-backed one." +msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:36 -msgid "" -"After making the backup, follow one of the guides below for a migration " -"path from a locally-stored media store to one stored on S3-compatible " -"storage:" +msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:38 -msgid "" -"[Migrating to any S3-compatible storage (universal, but likely slow" -")](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" +msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:39 @@ -115,34 +85,23 @@ msgid "Proceed with the steps below without stopping Matrix services" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:45 -msgid "" -"Start by adding the base S3 configuration in your `vars.yml` file (seen " -"above, may be different depending on the S3 provider of your choice)" +msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:47 -msgid "" -"In addition to the base configuration you see above, add this to your " -"`vars.yml` file:" +msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:53 -msgid "" -"This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3" -"-media-store` without hooking it to your homeserver yet. Your homeserver " -"will still continue using your local filesystem for its media store." +msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:55 -msgid "" -"Run the playbook to apply the changes: `ansible-playbook -i " -"inventory/hosts setup.yml --tags=setup-all,start`" +msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:57 -msgid "" -"Do an **initial sync of your files** by running this **on the server** " -"(it may take a very long time):" +msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:63 @@ -151,15 +110,11 @@ msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:65 #: ../../../docs/configuring-playbook-s3-goofys.md:106 -msgid "" -"Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml " -"--tags=stop`)" +msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:67 -msgid "" -"Start the S3 service by running this **on the server**: `systemctl start " -"matrix-goofys`" +msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:69 @@ -167,43 +122,31 @@ msgid "Sync the files again by re-running the `rsync` command you see in step #5 msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:71 -msgid "" -"Stop the S3 service by running this **on the server**: `systemctl stop " -"matrix-goofys`" +msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:73 #: ../../../docs/configuring-playbook-s3-goofys.md:114 -msgid "" -"Get the old media store out of the way by running this command on the " -"server:" +msgid "Get the old media store out of the way by running this command on the server:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:79 -msgid "" -"Remove the `matrix_s3_media_store_path` configuration from your " -"`vars.yml` file (undoing step #3 above)" +msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:81 #: ../../../docs/configuring-playbook-s3-goofys.md:122 -msgid "" -"Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags" -"=setup-all,start`" +msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:83 #: ../../../docs/configuring-playbook-s3-goofys.md:124 -msgid "" -"You're done! Verify that loading existing (old) media files works and " -"that you can upload new ones." +msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:85 #: ../../../docs/configuring-playbook-s3-goofys.md:126 -msgid "" -"When confident that it all works, get rid of the local media store " -"directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" +msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:87 @@ -211,9 +154,7 @@ msgid "Migrating to Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:89 -msgid "" -"While all Matrix services are running, run the following command on the " -"server:" +msgid "While all Matrix services are running, run the following command on the server:" msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:91 @@ -229,20 +170,13 @@ msgid "Run the command from step #1 again." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:110 -msgid "" -"Doing this will sync any new files that may have been created locally in " -"the meantime." +msgid "Doing this will sync any new files that may have been created locally in the meantime." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:112 -msgid "" -"Now that Matrix services aren't running, we're sure to get Backblaze B2 " -"and your local media store fully in sync." +msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync." msgstr "" #: ../../../docs/configuring-playbook-s3-goofys.md:120 -msgid "" -"Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) " -"in your `vars.yml` file" +msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po index afea36bc7..442e2d3c8 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po @@ -21,37 +21,23 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-s3.md:1 -msgid "" -"Storing Synapse media files on Amazon S3 or another compatible Object " -"Storage (optional)" +msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:3 -msgid "" -"By default, this playbook configures your server to store Synapse's " -"content repository (`media_store`) files on the local filesystem. If " -"that's okay, you can skip this document." +msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-s3.md:5 -msgid "" -"As an alternative to storing media files on the local filesystem, you can" -" store them on [Amazon S3](https://aws.amazon.com/s3/) or another " -"S3-compatible object store." +msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store." msgstr "" #: ../../../docs/configuring-playbook-s3.md:7 -msgid "" -"You can do this either by sticking to Synapse's media repository and " -"making that use S3 (read below for this method), or by switching to an " -"external media storage implementation like [matrix-media-repo" -"](configuring-playbook-matrix-media-repo.md)." +msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:9 -msgid "" -"First, [choose an Object Storage provider](#choosing-an-object-storage-" -"provider)." +msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:11 @@ -59,12 +45,7 @@ msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration) msgstr "" #: ../../../docs/configuring-playbook-s3.md:13 -msgid "" -"Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys" -"](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider" -"](configuring-playbook-synapse-s3-storage-provider.md), or use s3 " -"datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-" -"media-repo/configuration/s3-datastore.html))." +msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))." msgstr "" #: ../../../docs/configuring-playbook-s3.md:15 @@ -72,35 +53,19 @@ msgid "Choosing an Object Storage provider" msgstr "" #: ../../../docs/configuring-playbook-s3.md:17 -msgid "" -"You can create [Amazon S3](https://aws.amazon.com/s3/) or another " -"S3-compatible object storage like [Backblaze " -"B2](https://www.backblaze.com/b2/cloud-storage.html), " -"[Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean " -"Spaces](https://www.digitalocean.com/products/spaces), etc." +msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc." msgstr "" #: ../../../docs/configuring-playbook-s3.md:19 -msgid "" -"Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges" -" for storing too little data." +msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data." msgstr "" #: ../../../docs/configuring-playbook-s3.md:21 -msgid "" -"All these providers have different prices, with Storj appearing to be the" -" cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress " -"fee is $0.007 per GB). Backblaze egress is free, but for only certain " -"users for up to 3x the amount of data stored. Beyond that you will pay " -"$0.01/GB of egress." +msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress." msgstr "" #: ../../../docs/configuring-playbook-s3.md:23 -msgid "" -"Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which" -" becomes expensive if you need to store less data than that. Likewise, " -"Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of " -"2022-10)." +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 @@ -108,9 +73,7 @@ msgid "Here are some of the important aspects of choosing the right provider:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:27 -msgid "" -"if a provider is a company you like and trust (or dislike less than the " -"others)" +msgid "if a provider is a company you like and trust (or dislike less than the others)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:28 @@ -118,28 +81,19 @@ msgid "if a provider implements end-to-end encryption of your data" msgstr "" #: ../../../docs/configuring-playbook-s3.md:29 -msgid "" -"if a provider has a data region close to your Matrix server (if it's " -"farther away, high latency may cause slowdowns)" +msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:30 -msgid "" -"if a provider's infrastructure such as data center is centralized or " -"distributed" +msgid "if a provider's infrastructure such as data center is centralized or distributed" msgstr "" #: ../../../docs/configuring-playbook-s3.md:31 -msgid "" -"if a provider's price model is transparent (whether it includes hidden " -"costs like minimum charge, minimum storage term, etc.)" +msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:32 -msgid "" -"if a provider has free or cheap egress fee (in case you need to get the " -"data out often, for some reason) - likely not too important for the " -"common use-case" +msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case" msgstr "" #: ../../../docs/configuring-playbook-s3.md:34 @@ -147,24 +101,15 @@ msgid "Bucket creation and Security Configuration" msgstr "" #: ../../../docs/configuring-playbook-s3.md:36 -msgid "" -"Now that you've [chosen an Object Storage provider](#choosing-an-object-" -"storage-provider), you need to create a storage bucket." +msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket." msgstr "" #: ../../../docs/configuring-playbook-s3.md:38 -msgid "" -"How you do this varies from provider to provider, with Amazon S3 being " -"the most complicated due to its vast number of services and complicated " -"security policies." +msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies." msgstr "" #: ../../../docs/configuring-playbook-s3.md:40 -msgid "" -"Below, we provider some guides for common providers. If you don't see " -"yours, look at the others for inspiration or read some guides online " -"about how to create a bucket. Feel free to contribute to this " -"documentation with an update!" +msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!" msgstr "" #: ../../../docs/configuring-playbook-s3.md:42 @@ -172,16 +117,11 @@ msgid "Amazon S3" msgstr "" #: ../../../docs/configuring-playbook-s3.md:44 -msgid "" -"You'll need an Amazon S3 bucket and some IAM user credentials (access key" -" + secret key) with full write access to the bucket. Example IAM security" -" policy:" +msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:65 -msgid "" -"**Note**: This policy needs to be attached to an IAM user created from " -"the **Security Credentials** menu. This is not a **Bucket Policy**." +msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**." msgstr "" #: ../../../docs/configuring-playbook-s3.md:67 @@ -189,19 +129,11 @@ msgid "Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-s3.md:69 -msgid "" -"To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) " -"you first need to sign up." +msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up." msgstr "" #: ../../../docs/configuring-playbook-s3.md:71 -msgid "" -"You [can't easily change which region (US, Europe) your Backblaze account" -" stores files " -"in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/)," -" so make sure to carefully choose the region when signing up (hint: it's " -"a hard to see dropdown below the username/password fields in the signup " -"form)." +msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:73 @@ -209,15 +141,11 @@ msgid "After logging in to Backblaze:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:75 -msgid "" -"create a new **private** bucket through its user interface (you can call " -"it something like `matrix-example-media-store`)" +msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:76 -msgid "" -"note the **Endpoint** for your bucket (something like `s3.us-" -"west-002.backblazeb2.com`)." +msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)." msgstr "" #: ../../../docs/configuring-playbook-s3.md:77 @@ -225,15 +153,11 @@ msgid "adjust its Lifecycle Rules to: Keep only the last version of the file" msgstr "" #: ../../../docs/configuring-playbook-s3.md:78 -msgid "" -"go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the " -"**Add a New Application Key** to create a new one" +msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one" msgstr "" #: ../../../docs/configuring-playbook-s3.md:79 -msgid "" -"restrict it to the previously created bucket (e.g. `matrix-example-media-" -"store`)" +msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:80 @@ -241,22 +165,15 @@ msgid "give it *Read & Write* access" msgstr "" #: ../../../docs/configuring-playbook-s3.md:82 -msgid "" -"The `keyID` value is your **Access Key** and `applicationKey` is your " -"**Secret Key**." +msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**." msgstr "" #: ../../../docs/configuring-playbook-s3.md:84 -msgid "" -"For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3" -"-synapse-storage-provider](configuring-playbook-synapse-s3-storage-" -"provider.md) you will need:" +msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:86 -msgid "" -"**Endpoint URL** - this is the **Endpoint** value you saw above, but " -"prefixed with `https://`" +msgid "**Endpoint URL** - this is the **Endpoint** value you saw above, but prefixed with `https://`" msgstr "" #: ../../../docs/configuring-playbook-s3.md:88 @@ -264,9 +181,7 @@ msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:90 -msgid "" -"**Storage Class** - use `STANDARD`. Backblaze B2 does not have different " -"storage classes, so it doesn't make sense to use any other value." +msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value." msgstr "" #: ../../../docs/configuring-playbook-s3.md:92 @@ -274,16 +189,11 @@ msgid "Other providers" msgstr "" #: ../../../docs/configuring-playbook-s3.md:94 -msgid "" -"For other S3-compatible providers, you may not need to configure security" -" policies, etc. (just like for [Backblaze B2](#backblaze-b2))." +msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))." msgstr "" #: ../../../docs/configuring-playbook-s3.md:96 -msgid "" -"You most likely just need to create an S3 bucket and get some credentials" -" (access key and secret key) for accessing the bucket in a read/write " -"manner." +msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner." msgstr "" #: ../../../docs/configuring-playbook-s3.md:98 @@ -291,24 +201,17 @@ msgid "Setting up" msgstr "" #: ../../../docs/configuring-playbook-s3.md:100 -msgid "" -"To set up Synapse to store files in S3, follow the instructions for the " -"method of your choice:" +msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:" msgstr "" #: ../../../docs/configuring-playbook-s3.md:102 -msgid "" -"using [synapse-s3-storage-provider](configuring-playbook-synapse-s3" -"-storage-provider.md) (recommended)" +msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:103 -msgid "" -"using [Goofys to mount the S3 store to the local filesystem](configuring-" -"playbook-s3-goofys.md)" +msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../docs/configuring-playbook-s3.md:104 msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po index 7c1c8bc8b..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 @@ -21,23 +21,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-shared-secret-auth.md:1 -msgid "" -"Setting up the Shared Secret Auth password provider module (optional, " -"advanced)" +msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:3 -msgid "" -"The playbook can install and configure [matrix-synapse-shared-secret-" -"auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for " -"you." +msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:5 -msgid "" -"See the project's [documentation](https://github.com/devture/matrix-" -"synapse-shared-secret-auth/blob/master/README.md) to learn what it does " -"and why it might be useful to you." +msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:7 @@ -45,9 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:9 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:18 @@ -55,10 +45,7 @@ msgid "Authenticating only using a password provider" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:20 -msgid "" -"If you wish for users to **authenticate only against configured password " -"providers** (like this one), **without consulting Synapse's local " -"database**, feel free to disable it:" +msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:26 @@ -66,30 +53,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:28 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:35 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-shared-secret-auth.md:37 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 751e3b1a0..4cefcae41 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 @@ -25,30 +25,15 @@ msgid "Setting up the Sliding Sync proxy (optional)" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3 -msgid "" -"**Note**: The sliding-sync proxy is **not required** anymore as it's been" -" replaced with a different method (called Simplified Sliding Sync) which " -"is integrated into newer homeservers by default (**Conduit** homeserver " -"from version `0.6.0` or **Synapse** from version `1.114`). This component" -" and documentation remain here for historical purposes, but **installing " -"this old sliding-sync proxy is generally not recommended anymore**." +msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5 -msgid "" -"The playbook can install and configure [sliding-sync](https://github.com" -"/matrix-org/sliding-sync) proxy for you." +msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7 -msgid "" -"Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-" -"org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and " -"a prerequisite for running Element X clients ([Element X " -"iOS](https://github.com/element-hq/element-x-ios) and [Element X " -"Android](https://github.com/element-hq/element-x-android)). See the " -"project's [documentation](https://github.com/matrix-org/sliding-sync) to " -"learn more." +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 @@ -56,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11 -msgid "" -"To enable Sliding Sync proxy, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17 @@ -66,26 +49,15 @@ msgid "Adjusting the Sliding Sync proxy URL" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19 -msgid "" -"By default, this playbook installs the Sliding Sync proxy on the " -"`matrix.` subdomain, at the `/sliding-sync` path " -"(https://matrix.example.com/sliding-sync). This makes it easy to install " -"it, because it **doesn't require additional DNS records to be set up**. " -"If that's okay, you can skip this section." +msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:21 -msgid "" -"By tweaking the `matrix_sliding_sync_hostname` and " -"`matrix_sliding_sync_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:23 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31 @@ -93,9 +65,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Honoroit domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35 @@ -103,9 +73,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39 @@ -113,26 +81,15 @@ 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:" +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`" +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." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd 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 @@ -140,10 +97,7 @@ 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:" +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 @@ -151,24 +105,13 @@ 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." +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`)." +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." +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 70a3f345b..65363b1cf 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 @@ -25,17 +25,11 @@ msgid "Adjusting SSL certificate retrieval (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:3 -msgid "" -"By default, this playbook retrieves and auto-renews free SSL certificates" -" from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs " -"(e.g. `matrix.example.com` and others)" +msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:5 -msgid "" -"This guide is about using the integrated Traefik server and doesn't apply" -" if you're using [your own webserver](configuring-playbook-own-" -"webserver.md)." +msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:7 @@ -43,16 +37,12 @@ msgid "Using staging Let's Encrypt certificates instead of real ones" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:9 -msgid "" -"For testing purposes, you may wish to use staging certificates provide by" -" Let's Encrypt." +msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:11 #: ../../../docs/configuring-playbook-ssl-certificates.md:21 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:17 @@ -60,10 +50,7 @@ msgid "Disabling SSL termination" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:19 -msgid "" -"For testing or other purposes, you may wish to install services without " -"SSL termination and have services exposed to `http://` instead of " -"`https://`." +msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:27 @@ -71,11 +58,7 @@ msgid "Using self-signed SSL certificates" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:29 -msgid "" -"If you'd like to use your own SSL certificates, instead of the default " -"(SSL certificates obtained automatically via " -"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" -" from [Let's Encrypt](https://letsencrypt.org/)):" +msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:31 @@ -83,9 +66,7 @@ msgid "generate your self-signed certificate files" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:32 -msgid "" -"follow the [Using your own SSL certificates](#using-your-own-ssl-" -"certificates) documentation below" +msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:34 @@ -97,30 +78,19 @@ msgid "To use your own SSL certificates with Traefik, you need to:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:38 -msgid "" -"disable " -"[ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment)" -" / [Let's Encrypt](https://letsencrypt.org/) support" +msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:39 -msgid "" -"put a custom Traefik configuration file on the server, with the help of " -"this Ansible playbook (via the [`aux` role](https://github.com/mother-of-" -"all-self-hosting/ansible-role-aux)) or manually" +msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:40 -msgid "" -"register your custom configuration file with Traefik, by adding an extra " -"provider of type [file](https://doc.traefik.io/traefik/providers/file/)" +msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:41 -msgid "" -"put the SSL files on the server, with the help of this Ansible playbook " -"(via the [`aux` role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-aux)) or manually" +msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:89 @@ -128,12 +98,7 @@ msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:91 -msgid "" -"You can configure Traefik to use the [DNS-01 challenge " -"type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for" -" Let's Encrypt. This is less commonly used than the default [HTTP-01 " -"challenge type](https://letsencrypt.org/docs/challenge-" -"types/#http-01-challenge), but it can be helpful to:" +msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:93 @@ -141,33 +106,17 @@ msgid "hide your public IP from Let's Encrypt logs" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:94 -msgid "" -"allow you to obtain SSL certificates for servers which are not accessible" -" (via HTTP) from the public internet (and for which the HTTP-01 challenge" -" would fail)" +msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:96 -msgid "" -"This is an example for how to edit the `vars.yml` file if you're using " -"Cloudflare:" +msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:" msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:111 -msgid "" -"Make sure to change the value of \"provider\" to your particular DNS " -"solution, and provide the appropriate environment variables. The full " -"list of supported providers is available " -"[here](https://doc.traefik.io/traefik/https/acme/#providers)." +msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)." msgstr "" #: ../../../docs/configuring-playbook-ssl-certificates.md:113 -msgid "" -"This example assumes you're using Cloudflare to manage your DNS zone. " -"Note that it requires the use of two tokens: one for reading all zones " -"(`CF_ZONE_API_TOKEN`) and another that must be able to edit the " -"particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's " -"recommended that you create two fine-grained tokens for this purpose, but" -" you might choose to use the same token for both." +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 81646fa21..06a8925bd 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po @@ -25,36 +25,23 @@ msgid "Setting up the Sygnal push gateway (optional)" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:3 -msgid "" -"The playbook can install and configure the [Sygnal](https://github.com" -"/matrix-org/sygnal) push gateway for you." +msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:5 -msgid "" -"See the project's [documentation](https://github.com/matrix-" -"org/sygnal/blob/master/README.md) to learn what it does and why it might " -"be useful to you." +msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:7 -msgid "" -"**Note**: most people don't need to install their own gateway. As " -"Sygnal's [Notes for application developers](https://github.com/matrix-" -"org/sygnal/blob/master/docs/applications.md) documentation says:" +msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:9 -msgid "" -"It is not feasible to allow end-users to configure their own Sygnal " -"instance, because the Sygnal instance needs the appropriate FCM or APNs " -"secrets that belong to the application." +msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:11 -msgid "" -"This optional playbook component is only useful to people who " -"develop/build their own Matrix client applications themselves." +msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:13 @@ -62,50 +49,27 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:15 -msgid "" -"To enable Sygnal, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:43 -msgid "" -"For a more complete example of available fields and values they can take," -" see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the " -"[upstream `sygnal.yaml.sample` configuration file](https://github.com" -"/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." +msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:45 -msgid "" -"Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) " -"is easier, as it only requires that you provide some config values." +msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:47 -msgid "" -"To configure [APNS](https://developer.apple.com/notifications/) (Apple " -"Push Notification Service), you'd need to provide one or more certificate" -" files. To do that, the above example configuration:" +msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:49 -msgid "" -"makes use of the [`aux` role](https://github.com/mother-of-all-self-" -"hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to " -"make the playbook install files into `/matrix/sygnal/data` (the " -"`matrix_sygnal_data_path` variable). See [`defaults/main.yml` " -"file](https://github.com/mother-of-all-self-hosting/ansible-role-" -"aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It" -" also makes sure the files are owned by `matrix:matrix`, so that Sygnal " -"can read them. Of course, you can also install these files manually " -"yourself, if you'd rather not use `aux`." +msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:51 -msgid "" -"references these files in the Sygnal configuration (`matrix_sygnal_apps`)" -" using a path like `/data/..` (the `/matrix/sygnal/data` directory on the" -" host system is mounted into the `/data` directory inside the container)" +msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:53 @@ -113,23 +77,15 @@ msgid "Adjusting the Sygnal URL" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:55 -msgid "" -"By default, this playbook installs Sygnal on the `sygnal.` subdomain " -"(`sygnal.example.com`) and requires you to [adjust your DNS records" -"](#adjusting-dns-records)." +msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:57 -msgid "" -"By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` " -"variables, you can easily make the service available at a **different " -"hostname and/or path** than the default one." +msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:59 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:70 @@ -137,21 +93,15 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:72 -msgid "" -"Once you've decided on the domain and path, **you may need to adjust your" -" DNS** records to point the Sygnal domain to the Matrix server." +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:74 -msgid "" -"By default, you will need to create a CNAME record for `sygnal`. See " -"[Configuring DNS](configuring-dns.md) for details about DNS changes." +msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:76 -msgid "" -"If you've decided to reuse the `matrix.` domain, you won't need to do any" -" extra DNS configuration." +msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:78 @@ -159,26 +109,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:80 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:87 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:89 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:91 @@ -186,24 +125,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:93 -msgid "" -"To make use of your Sygnal installation, you'd need to build your own " -"Matrix client application, which uses the same API keys (for " -"[GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and " -"certificates (for [APNS](https://developer.apple.com/notifications/)) and" -" is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." +msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)." msgstr "" #: ../../../docs/configuring-playbook-sygnal.md:95 -msgid "" -"Refer to Sygnal's [Notes for application developers](https://github.com" -"/matrix-org/sygnal/blob/master/docs/applications.md) document." +msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/sygnal) to learn what it " -#~ "does and why it might be useful" -#~ " to you." -#~ 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 index 87d46a037..4d5ddd2c4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po @@ -25,33 +25,15 @@ 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." +msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:5 -msgid "" -"synapse-admin is a web UI tool you can use to **administrate users, " -"rooms, media, etc. on your Matrix server**. It's designed to work with " -"the Synapse homeserver implementation and WON'T work with Dendrite " -"because [Dendrite Admin API](https://matrix-" -"org.github.io/dendrite/administration/adminapi) differs from [Synapse " -"Admin API](https://element-" -"hq.github.io/synapse/latest/usage/administration/admin_api/)." +msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:7 -msgid "" -"💡 **Note**: the latest version of synapse-admin is hosted by " -"[etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). " -"If you only need this service occasionally and trust giving your admin " -"credentials to a 3rd party Single Page Application, you can consider " -"using it from there and avoiding the (small) overhead of self-hosting." +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 @@ -59,59 +41,27 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:11 -msgid "" -"To enable Synapse Admin, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:17 -msgid "" -"**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-" -"hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to" -" function. Access to them is restricted with a valid access token, so " -"exposing them publicly should not be a real security concern. Still, for " -"additional security, we normally leave them unexposed, following " -"[official Synapse reverse-proxying recommendations](https://element-" -"hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-" -"endpoints). Because Synapse Admin needs these APIs to function, when " -"installing Synapse Admin, the playbook **automatically** exposes the " -"Synapse Admin API publicly for you. Depending on the homeserver " -"implementation you're using (Synapse, Dendrite), this is equivalent to:" +msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:19 -msgid "" -"for [Synapse](./configuring-playbook-synapse.md) (our default homeserver " -"implementation): " -"`matrix_synapse_container_labels_public_client_synapse_admin_api_enabled:" -" true`" +msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:20 -msgid "" -"for [Dendrite](./configuring-playbook-dendrite.md): " -"`matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled:" -" true`" +msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:22 -msgid "" -"By default, synapse-admin installation will be [restricted to only work " -"with one homeserver](https://github.com/etkecc/synapse-" -"admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md" -"#restricting-available-homeserver) - the one managed by the playbook. To " -"adjust these restrictions, tweak the " -"`matrix_synapse_admin_config_restrictBaseUrl` variable." +msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) - the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:24 -msgid "" -"⚠️ **Warning**: If you're using [Matrix Authentication Service" -"](./configuring-playbook-matrix-authentication-service.md) (MAS) for " -"authentication, you will be able to [log into synapse-admin with an " -"access token](https://github.com/etkecc/synapse-admin/pull/58), but " -"certain synapse-admin features (especially those around user management) " -"will be limited or not work at all." +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:26 @@ -119,26 +69,15 @@ msgid "Adjusting the Synapse Admin URL" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:28 -msgid "" -"By default, this playbook installs Synapse Admin on the `matrix.` " -"subdomain, at the `/synapse-admin` path (https://matrix.example.com" -"/synapse-admin). This makes it easy to install it, because it **doesn't " -"require additional DNS records to be set up**. If that's okay, you can " -"skip this section." +msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:30 -msgid "" -"By tweaking the `matrix_synapse_admin_hostname` and " -"`matrix_synapse_admin_path_prefix` variables, you can easily make the " -"service available at a **different hostname and/or path** than the " -"default one." +msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:32 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:40 @@ -146,9 +85,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:42 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the Synapse Admin domain to the Matrix server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:44 @@ -156,9 +93,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:46 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:48 @@ -166,26 +101,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:50 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:57 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:59 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:61 @@ -193,14 +117,9 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:63 -msgid "" -"After installation, Synapse Admin will be accessible at: " -"`https://matrix.example.com/synapse-admin/`" +msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`" msgstr "" #: ../../../docs/configuring-playbook-synapse-admin.md:65 -msgid "" -"To use Synapse Admin, you need to have [registered at least one " -"administrator account](registering-users.md) on your server." +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 bf5494b8b..e239aed5b 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 @@ -25,35 +25,19 @@ msgid "Setting up Synapse Auto Invite Accept (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3 -msgid "" -"The playbook can install and configure [synapse-auto-invite-" -"accept](https://github.com/matrix-org/synapse-auto-accept-invite) for " -"you." +msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5 -msgid "" -"In short, it automatically accepts room invites. You can specify that " -"only 1:1 room invites are auto-accepted. Defaults to false if not " -"specified." +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." +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." +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 @@ -61,11 +45,7 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13 -msgid "" -"If you decide that you'd like to let this playbook install the [synapse-" -"auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-" -"invite module for you, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +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 @@ -73,19 +53,11 @@ 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:" +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)." +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 @@ -93,27 +65,9 @@ msgid "Native alternative" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33 -msgid "" -"Since Synapse [v1.109.0](https://github.com/element-" -"hq/synapse/releases/tag/v1.109.0), the functionality provided by the " -"[synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-" -"accept-invite) 3rd party module [has been made](https://github.com" -"/element-hq/synapse/pull/17147) part of Synapse." +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 "" - -#~ msgid "" -#~ "See that project's " -#~ "[documentation](https://github.com/matrix-org/synapse-" -#~ "auto-accept-invite) to learn what it" -#~ " does and why it might be " -#~ "useful to you. In short, it " -#~ "automatically accepts room invites. You " -#~ "can specify that only 1:1 room " -#~ "invites are auto-accepted. Defaults to" -#~ " false if not specified." -#~ 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 cb5655ca9..6708ae642 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 @@ -25,24 +25,15 @@ msgid "Setting up synapse-auto-compressor (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3 -msgid "" -"The playbook can install and configure " -"[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-" -"compress-state/#automated-tool-synapse_auto_compressor) for you." +msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5 -msgid "" -"It's a CLI tool that automatically compresses Synapse's `state_groups` " -"database table in the background." +msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7 -msgid "" -"See the project's [documentation](https://github.com/matrix-org/rust-" -"synapse-compress-state/blob/master/README.md#automated-tool-" -"synapse_auto_compressor) to learn what it does and why it might be useful" -" to you." +msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9 @@ -50,9 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17 @@ -60,25 +49,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:28 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:30 @@ -86,10 +65,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32 -msgid "" -"After installation, `synapse_auto_compressor` will run automatically " -"every day at `00:00:00` (as defined in " -"`matrix_synapse_auto_compressor_calendar` by default)." +msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)." msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34 @@ -97,21 +73,5 @@ msgid "Manually start the tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36 -msgid "" -"For testing your setup it can be helpful to not wait until 00:00. If you " -"want to run the tool immediately, log onto the server and run `systemctl " -"start matrix-synapse-auto-compressor`. Running this command will not " -"return control to your terminal until the compression run is done, which " -"may take a long time. Consider using " -"[tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is " -"unstable." +msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable." msgstr "" - -#~ msgid "" -#~ "See the project's [documentation](https://github.com" -#~ "/matrix-org/rust-synapse-compress-state" -#~ "/#automated-tool-synapse_auto_compressor) to " -#~ "learn what it does and why it " -#~ "might be useful to you." -#~ 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 9fc0bf73d..f31fa54e9 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 @@ -21,23 +21,15 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1 -msgid "" -"Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider" -" (optional)" +msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3 -msgid "" -"If you'd like to store Synapse's content repository (`media_store`) files" -" on Amazon S3 (or other S3-compatible service), you can use the " -"[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3" -"-storage-provider) media provider module for Synapse." +msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5 -msgid "" -"An alternative (which has worse performance) is to use [Goofys to mount " -"the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." +msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7 @@ -45,10 +37,7 @@ msgid "How it works?" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9 -msgid "" -"Summarized writings here are inspired by [this " -"article](https://quentin.dufour.io/blog/2021-09-14/matrix-" -"synapse-s3-storage/)." +msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11 @@ -56,49 +45,31 @@ msgid "The way media storage providers in Synapse work has some caveats:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13 -msgid "" -"Synapse still continues to use locally-stored files (for creating " -"thumbnails, serving files, etc)" +msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14 -msgid "" -"the media storage provider is just an extra storage mechanism (in " -"addition to the local filesystem)" +msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15 -msgid "" -"all files are stored locally at first, and then copied to the media " -"storage provider (either synchronously or asynchronously)" +msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16 -msgid "" -"if a file is not available on the local filesystem, it's pulled from a " -"media storage provider" +msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18 -msgid "" -"You may be thinking **if all files are stored locally as well, what's the" -" point**?" +msgid "You may be thinking **if all files are stored locally as well, what's the point**?" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20 -msgid "" -"You can run some scripts to delete the local files once in a while (which" -" we do automatically by default - see [Periodically cleaning up the local" -" filesystem](#periodically-cleaning-up-the-local-filesystem)), thus " -"freeing up local disk space. If these files are needed in the future (for" -" serving them to users, etc.), Synapse will pull them from the media " -"storage provider on demand." +msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22 -msgid "" -"While you will need some local disk space around, it's only to " -"accommodate usage, etc., and won't grow as large as your S3 store." +msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24 @@ -106,17 +77,11 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26 -msgid "" -"After [creating the S3 bucket and configuring it](configuring-" -"playbook-s3.md#bucket-creation-and-security-configuration), you can " -"proceed to configure `s3-storage-provider` in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`):" +msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50 -msgid "" -"If you have existing files in Synapse's media repository " -"(`/matrix/synapse/media-store/..`):" +msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52 @@ -124,25 +89,15 @@ msgid "new files will start being stored both locally and on the S3 store" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53 -msgid "" -"the existing files will remain on the local filesystem only until " -"[migrating them to the S3 store](#migrating-your-existing-media-files-to-" -"the-s3-store)" +msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54 -msgid "" -"at some point (and periodically in the future), you can delete local " -"files which have been uploaded to the S3 store already" +msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56 -msgid "" -"Regardless of whether you need to [Migrate your existing files to the S3 " -"store](#migrating-your-existing-media-files-to-the-s3-store) or not, make" -" sure you've familiarized yourself with [How it works?](#how-it-works) " -"above and [Periodically cleaning up the local filesystem](#periodically-" -"cleaning-up-the-local-filesystem) below." +msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58 @@ -154,17 +109,11 @@ msgid "Migrating your existing data can happen in multiple ways:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62 -msgid "" -"[using the `s3_media_upload` script from `synapse-s3-storage-provider" -"`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " -"(very slow when dealing with lots of data)" +msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63 -msgid "" -"[using another tool in combination with `s3_media_upload`](#using-" -"another-tool-in-combination-with-s3_media_upload) (quicker when dealing " -"with lots of data)" +msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65 @@ -172,65 +121,39 @@ msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67 -msgid "" -"Instead of using `s3_media_upload` directly, which is very slow and " -"painful for an initial data migration, we recommend [using another tool " -"in combination with `s3_media_upload`](#using-another-tool-in-" -"combination-with-s3_media_upload)." +msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69 -msgid "" -"To copy your existing files, SSH into the server and run " -"`/matrix/synapse/ext/s3-storage-provider/bin/shell`." +msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71 -msgid "" -"This launches a Synapse container, which has access to the local media " -"store, Postgres database, S3 store and has some convenient environment " -"variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, " -"`UPDATE_DB_DAYS`, etc)." +msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73 -msgid "" -"Then use the following commands (`$` values come from environment " -"variables - they're **not placeholders** that you need to substitute):" +msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75 -msgid "" -"`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite " -"database (`cache.db`) with a list of media repository files (from the " -"`synapse` Postgres database) eligible for operating on" +msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76 -msgid "" -"`$UPDATE_DB_DURATION` is influenced by the " -"`matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` " -"variable (defaults to `0`)" +msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77 -msgid "" -"`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include " -"files which haven't been accessed for more than 0 days** (that is, **all " -"files will be included**)." +msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78 -msgid "" -"`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the " -"local cache still exist in the local media repository directory" +msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79 -msgid "" -"`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class " -"$STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files " -"to S3 and deletes them from the local media repository directory" +msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81 @@ -238,23 +161,15 @@ msgid "The `s3_media_upload upload` command may take a lot of time to complete." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83 -msgid "" -"Instead of running the above commands manually in the shell, you can also" -" run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script " -"which will run the same commands automatically. We demonstrate how to do " -"it manually, because:" +msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85 -msgid "" -"it's what the upstream project demonstrates and it teaches you how to use" -" the `s3_media_upload` tool" +msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86 -msgid "" -"allows you to check and verify the output of each command, to catch " -"mistakes" +msgid "allows you to check and verify the output of each command, to catch mistakes" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87 @@ -262,11 +177,7 @@ msgid "includes progress bars and detailed output for each command" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88 -msgid "" -"allows you to easily interrupt slow-running commands, etc. (the " -"`/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container " -"without interactive TTY support, so `Ctrl+C` may not work and you and " -"require killing via `docker kill ..`)" +msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90 @@ -278,18 +189,11 @@ msgid "To migrate your existing local data to S3, we recommend to:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94 -msgid "" -"**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or " -"[`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files" -" to the S3 bucket" +msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96 -msgid "" -"**only then** [use the `s3_media_upload` tool to finish the migration" -"](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) " -"(this checks to ensure all files are uploaded and then deletes the local " -"files)" +msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98 @@ -305,20 +209,11 @@ msgid "Copying data to an S3 alternative using the aws-s3 tool" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114 -msgid "" -"To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean " -"Spaces, etc.), you can use the command for [Copying data to Amazon S3" -"](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` " -"argument." +msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116 -msgid "" -"Add this argument to the command **as-is** (`$ENDPOINT` is an environment" -" variable corresponding to " -"`matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so " -"you don't need to touch it). Make sure to add the argument **before** the" -" final quote (`'`) of the command." +msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118 @@ -326,19 +221,11 @@ msgid "Copying data to Backblaze B2" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120 -msgid "" -"You can copy files to Backblaze B2 either by following the [Copying data " -"to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3" -"-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 " -"command-line " -"tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as " -"described below." +msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122 -msgid "" -"To copy the data using the `b2` tool, start a container on the Matrix " -"server like this:" +msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136 @@ -346,17 +233,11 @@ msgid "Periodically cleaning up the local filesystem" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138 -msgid "" -"As described in [How it works?](#how-it-works) above, when new media is " -"uploaded to the Synapse homeserver, it's first stored locally and then " -"also stored on the remote S3 storage." +msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage." msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140 -msgid "" -"By default, we periodically ensure that all local files are uploaded to " -"S3 and are then removed from the local filesystem. This is done " -"automatically using:" +msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142 @@ -364,18 +245,13 @@ msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143 -msgid "" -".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` " -"service" +msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144 -msgid "" -".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` " -"timer, every day at 05:00" +msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00" msgstr "" #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146 msgid "So.. you don't need to perform any maintenance yourself." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po index 6803bc2ba..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 @@ -25,22 +25,15 @@ msgid "Setting up Synapse Simple Antispam (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3 -msgid "" -"The playbook can install and configure [synapse-simple-" -"antispam](https://github.com/t2bot/synapse-simple-antispam) for you." +msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5 -msgid "" -"It lets you fight invite-spam by automatically blocking invitiations from" -" a list of servers specified by you (blacklisting)." +msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7 -msgid "" -"See the project's [documentation](https://github.com/t2bot/synapse-" -"simple-antispam/blob/master/README.md) to learn what it does and why it " -"might be useful to you." +msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9 @@ -48,19 +41,5 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your " -"needs):" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" - -#~ msgid "" -#~ "See that project's documentation to " -#~ "learn what it does and why it " -#~ "might be useful to you. In short," -#~ " it lets you fight invite-spam " -#~ "by automatically blocking invitiations from" -#~ " a list of servers specified by " -#~ "you (blacklisting)." -#~ 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 15344e649..6e5ae6f1b 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 @@ -25,21 +25,11 @@ msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3 -msgid "" -"[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-" -"exporter) allows you to export the usage statistics of a Synapse " -"homeserver to this container service and for the collected metrics to " -"later be scraped by Prometheus." +msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5 -msgid "" -"Synapse does not include usage statistics in its Prometheus metrics. They" -" can be reported to an HTTP `PUT` endpoint 5 minutes after startup and " -"from then on at a fixed interval of once every three hours. This role " -"integrates a simple [Flask](https://flask.palletsprojects.com) project " -"that offers an HTTP `PUT` endpoint and holds the most recent received " -"record available to be scraped by Prometheus." +msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7 @@ -51,22 +41,15 @@ msgid "install the synapse-usage-exporter service" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10 -msgid "" -"re-configure Synapse to push (via HTTP `PUT`) usage statistics " -"information to synapse-usage-exporter" +msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11 -msgid "" -"re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) " -"(if Prometheus is enabled), to periodically scrape metrics from synapse-" -"usage-exporter" +msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12 -msgid "" -"add a new [Grafana](./configuring-playbook-prometheus-grafana.md) " -"dashboard (if Grafana is enabled) containing Synapse usage statistics" +msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14 @@ -74,9 +57,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16 -msgid "" -"To enable synapse-usage-exporter, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28 @@ -84,26 +65,15 @@ msgid "Adjusting the synapse-usage-exporter URL" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30 -msgid "" -"By default, this playbook installs synapse-usage-exporter on the " -"`matrix.` subdomain, at the `/report-usage-stats/push` path " -"(https://matrix.example.com/report-usage-stats/push). This makes it easy " -"to install it, because it **doesn't require additional DNS records to be " -"set up**. If that's okay, you can skip this section." +msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:32 -msgid "" -"By tweaking the `matrix_synapse_usage_exporter_hostname` and " -"`matrix_synapse_usage_exporter_path_prefix` variables, you can easily " -"make the service available at a **different hostname and/or path** than " -"the default one." +msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:34 -msgid "" -"Example additional configuration for your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43 @@ -111,10 +81,7 @@ msgid "Adjusting DNS records" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45 -msgid "" -"If you've changed the default hostname, **you may need to adjust your " -"DNS** records to point the synapse-usage-exporter domain to the Matrix " -"server." +msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47 @@ -122,9 +89,7 @@ msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49 -msgid "" -"If you've decided to use the default hostname, you won't need to do any " -"extra DNS configuration." +msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51 @@ -132,25 +97,13 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53 -msgid "" -"After configuring the playbook and potentially [adjusting your DNS " -"records](#adjusting-dns-records), run the playbook with [playbook tags" -"](playbook-tags.md) as below:" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:60 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-synapse-usage-exporter.md:62 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po index 309f23e01..60b44510c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po @@ -25,70 +25,35 @@ msgid "Configuring Synapse (optional)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:3 -msgid "" -"By default, this playbook configures the [Synapse](https://github.com" -"/element-hq/synapse) Matrix server, so that it works for the general " -"case. If that's okay, you can skip this document." +msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:5 -msgid "" -"The playbook provides lots of customization variables you could use to " -"change Synapse's settings." +msgid "The playbook provides lots of customization variables you could use to change Synapse's settings." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:7 -msgid "" -"Their defaults are defined in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml) and they ultimately end up in the generated " -"`/matrix/synapse/config/homeserver.yaml` file (on the server). This file " -"is generated from the [`roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2) template." +msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:9 -msgid "" -"**If there's an existing variable** which controls a setting you wish to " -"change, you can simply define that variable in your configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the " -"playbook](installing.md) to apply the changes." +msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:11 -msgid "" -"Alternatively, **if there is no pre-defined variable** for a Synapse " -"setting you wish to change:" +msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:13 -msgid "" -"you can either **request a variable to be created** (or you can submit " -"such a contribution yourself). Keep in mind that it's **probably not a " -"good idea** to create variables for each one of Synapse's various " -"settings that rarely get used." +msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:15 -msgid "" -"or, you can **extend and override the default configuration** " -"([`homeserver.yaml.j2`](../roles/custom/matrix-" -"synapse/templates/synapse/homeserver.yaml.j2)) by making use of the " -"`matrix_synapse_configuration_extension_yaml` variable. You can find " -"information about this in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:17 -msgid "" -"or, if extending the configuration is still not powerful enough for your " -"needs, you can **override the configuration completely** using " -"`matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). " -"You can find information about this in [`roles/custom/matrix-" -"synapse/defaults/main.yml`](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:19 @@ -96,28 +61,15 @@ msgid "Load balancing with workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:21 -msgid "" -"To have Synapse gracefully handle thousands of users, worker support " -"should be enabled. It factors out some homeserver tasks and spreads the " -"load of incoming client and server-to-server traffic between multiple " -"processes. More information can be found in the [official Synapse workers" -" documentation](https://github.com/element-" -"hq/synapse/blob/master/docs/workers.md) and [Tom " -"Foster](https://github.com/tcpipuk)'s [Synapse homeserver " -"guide](https://tcpipuk.github.io/synapse/index.html)." +msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:23 -msgid "" -"To enable Synapse worker support, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:31 -msgid "" -"By default, this enables the `one-of-each` [worker preset](#worker-" -"presets), but you may wish to use another preset or [control the number " -"of worker instances](#controlling-the-number-of-worker-instances)." +msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:33 @@ -125,34 +77,23 @@ msgid "Worker presets" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:35 -msgid "" -"We support a few configuration presets (`matrix_synapse_workers_preset: " -"one-of-each` being the default configuration right now):" +msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:37 -msgid "" -"(federation-only) `little-federation-helper` - a very minimal worker " -"configuration to improve federation performance" +msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:38 -msgid "" -"(generic) `one-of-each` - defaults to one worker of each supported type -" -" no smart routing, just generic workers" +msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:39 -msgid "" -"(specialized) `specialized-workers` - defaults to one worker of each " -"supported type, but disables generic workers and uses [specialized " -"workers](#specialized-workers) instead" +msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:41 -msgid "" -"These presets represent a few common configurations. There are many " -"worker types which can be mixed and matched based on your needs." +msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:43 @@ -160,35 +101,19 @@ msgid "Generic workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:45 -msgid "" -"Previously, the playbook only supported the most basic type of load-" -"balancing. We call it **generic load-balancing** below, because incoming " -"HTTP requests are sent to a generic worker. Load-balancing was done based" -" on the requestor's IP address. This is simple, but not necessarily " -"optimal. If you're accessing your account from multiple IP addresses " -"(e.g. your mobile phone being on a different network than your PC), these" -" separate requests may potentially be routed to different workers, each " -"of which would need to cache roughly the same data." +msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:47 -msgid "" -"This is **still the default load-balancing method (preset) used by the " -"playbook**." +msgid "This is **still the default load-balancing method (preset) used by the playbook**." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:49 -msgid "" -"To use generic load-balancing, do not specify " -"`matrix_synapse_workers_preset` to make it use the default value (`one-" -"of-each`), or better yet - explicitly set it as `one-of-each`." +msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:51 -msgid "" -"You may also consider [tweaking the number of workers of each type" -"](#controlling-the-number-of-worker-instances) from the default (one of " -"each)." +msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:53 @@ -196,15 +121,7 @@ msgid "Specialized workers" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:55 -msgid "" -"The playbook now supports a smarter **specialized load-balancing** " -"inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse " -"homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead " -"of routing requests to one or more [generic workers](#generic-workers) " -"based only on the requestor's IP adddress, specialized load-balancing " -"routes to **4 different types of specialized workers** based on **smarter" -" criteria** - the access token (username) of the requestor and/or on the " -"resource (room, etc.) being requested." +msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:57 @@ -212,43 +129,23 @@ msgid "The playbook supports these **4 types** of specialized workers:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:59 -msgid "" -"Room workers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) & " -"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs " -"dedicated to handling specific rooms" +msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:60 -msgid "" -"Sync workers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to " -"synchronization (most notably [the `/sync` " -"endpoint](https://spec.matrix.org/v1.9/client-server-" -"api/#get_matrixclientv3sync))" +msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:61 -msgid "" -"Client readers - handles various [Client-" -"Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are " -"not for specific rooms (handled by **room workers**) or for " -"synchronization (handled by **sync workers**)" +msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:62 -msgid "" -"Federation readers - handles various " -"[Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which " -"are not for specific rooms (handled by **room workers**)" +msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:64 -msgid "" -"To use specialized load-balancing, consider enabling the `specialized-" -"workers` [worker preset](#worker-presets) and potentially [tweaking the " -"number of workers of each type](#controlling-the-number-of-worker-" -"instances) from the default (one of each)." +msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:66 @@ -256,24 +153,15 @@ msgid "Controlling the number of worker instances" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:68 -msgid "" -"If you'd like more customization power, you can start with one of the " -"[worker presets](#worker-presets) and then tweak various " -"`matrix_synapse_workers_*_count` variables manually." +msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:70 -msgid "" -"To find what variables are available for you to override in your own " -"`vars.yml` configuration file, see the [`defaults/main.yml` file for the " -"`matrix-synapse` Ansible role](../roles/custom/matrix-" -"synapse/defaults/main.yml)." +msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:72 -msgid "" -"The only thing you **cannot** do is mix [generic workers](#generic-" -"workers) and [specialized workers](#specialized-workers)." +msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:74 @@ -281,30 +169,15 @@ msgid "Effect of enabling workers on the rest of your server" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:76 -msgid "" -"When Synapse workers are enabled, the integrated [Postgres database is " -"tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum " -"number of Postgres connections are increased from `200` to `500`. If you " -"need to decrease or increase the number of maximum Postgres connections " -"further, use the `postgres_max_connections` variable." +msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:78 -msgid "" -"A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and " -"component handles load-balancing for workers. This role/component is " -"automatically enabled when you enable workers. Make sure to use the " -"`setup-all` tag (not `install-all`!) during the playbook's " -"[installation](./installing.md) process, especially if you're disabling " -"workers, so that components may be installed/uninstalled correctly." +msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:80 -msgid "" -"In case any problems occur, make sure to have a look at the [list of " -"synapse issues about workers](https://github.com/element-" -"hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit " -"'matrix-*'`." +msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:82 @@ -312,10 +185,7 @@ msgid "Synapse Admin" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:84 -msgid "" -"Certain Synapse administration tasks (managing users and rooms, etc.) can" -" be performed via a web user-interace, if you install [Synapse Admin" -"](configuring-playbook-synapse-admin.md)." +msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:86 @@ -323,42 +193,24 @@ msgid "Synapse + OpenID Connect for Single-Sign-On" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:88 -msgid "" -"💡 An alternative to setting up OIDC in Synapse is to use [Matrix " -"Authentication Service](./configuring-playbook-matrix-authentication-" -"service.md) (MAS). Newer clients (like Element X) only support SSO-based " -"authentication via MAS and not via the legacy Synapse OIDC setup " -"described below. That said, MAS is still a new experimental service which" -" comes with its own downsides. Consult its documentation to learn if it " -"will be a good fit for your deployment." +msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:90 -msgid "" -"If you'd like to use OpenID Connect authentication with Synapse, you'll " -"need some additional configuration." +msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:92 -msgid "" -"This example configuration is for [keycloak](https://www.keycloak.org/), " -"an opensource Identity Provider maintained by Red Hat." +msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:94 -msgid "" -"For more detailed documentation on available options and how to setup " -"keycloak, see the [Synapse documentation on OpenID Connect with " -"keycloak](https://github.com/element-" -"hq/synapse/blob/develop/docs/openid.md#keycloak)." +msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:96 #, python-format -msgid "" -"In case you encounter errors regarding the parsing of the variables, you " -"can try to add `{% raw %}` and `{% endraw %}` blocks around them. For " -"example ;" +msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:117 @@ -366,48 +218,27 @@ msgid "Customizing templates" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:119 -msgid "" -"[Templates](https://github.com/element-" -"hq/synapse/blob/develop/docs/templates.md) are used by Synapse for " -"showing **certain web pages** handled by the server, as well as for " -"**email notifications**." +msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:121 -msgid "" -"This playbook allows you to customize the default templates (see the " -"[`synapse/res/templates` directory](https://github.com/element-" -"hq/synapse/tree/develop/synapse/res/templates))." +msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:123 -msgid "" -"If template customization is enabled, the playbook will build a custom " -"container image based on the official one." +msgid "If template customization is enabled, the playbook will build a custom container image based on the official one." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:125 -msgid "" -"Your custom templates need to live in a public or private git repository." -" This repository will be cloned during Synapse image customization " -"(during the playbook run)." +msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:127 -msgid "" -"To enable template customizations, use a configuration " -"(`inventory/host_vars/matrix.example.com/vars.yml`) like this:" +msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:153 -msgid "" -"As mentioned in Synapse's Templates documentation, Synapse will fall back" -" to its own templates if a template is not found in that directory. Due " -"to this, it's recommended to only store and maintain template files in " -"your repository if you need to make custom changes. Other files (which " -"you don't need to change), should not be duplicated, so that you don't " -"need to worry about getting out-of-sync with the original Synapse " -"templates." +msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:155 @@ -415,22 +246,13 @@ msgid "Monitoring Synapse Metrics with Prometheus and Grafana" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:157 -msgid "" -"This playbook allows you to enable Synapse metrics, which can provide " -"insight into the performance and activity of Synapse." +msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse." msgstr "" #: ../../../docs/configuring-playbook-synapse.md:159 -msgid "" -"To enable Synapse runtime metrics see: [Enabling metrics and graphs " -"(Prometheus, Grafana) for your Matrix server](configuring-playbook-" -"prometheus-grafana.md)" +msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" msgstr "" #: ../../../docs/configuring-playbook-synapse.md:161 -msgid "" -"To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter " -"for Synapse usage statistics](configuring-playbook-synapse-usage-" -"exporter.md)" +msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po index e0d7c0b9c..9c093c4dc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po @@ -25,17 +25,11 @@ msgid "Enabling Telemetry for your Matrix server (optional)" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:3 -msgid "" -"By default, this playbook configures your Matrix homeserver to not send " -"any telemetry data anywhere." +msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:5 -msgid "" -"The [matrix.org](https://matrix.org) team would really appreciate it if " -"you could help the project out by reporting usage statistics from your " -"homeserver. Enabling usage statistics helps track the growth of the " -"Matrix community, and helps to make Matrix a success." +msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:7 @@ -43,10 +37,7 @@ msgid "Enabling Telemetry" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:9 -msgid "" -"If you'd like to **help by enabling submission of general usage " -"statistics** for your homeserver, add the following configuration to your" -" `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:17 @@ -54,21 +45,9 @@ msgid "Usage statistics being submitted" msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:19 -msgid "" -"When enabled, your homeserver will regularly upload a few dozen " -"statistics about your server. This data includes your homeserver's " -"domain, the total number of users, the number of active users, the total " -"number of rooms, and the number of messages sent per day on your " -"homeserver." +msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver." msgstr "" #: ../../../docs/configuring-playbook-telemetry.md:21 -msgid "" -"See [Synapse's documentation](https://github.com/element-" -"hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md" -"#available-statistics) or [Dendrite's documentation](https://github.com" -"/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-" -"enabling-phone-home-statistics) for the full list of statistics that are " -"reported." +msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po index 6542f6b36..1de2b54a4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po @@ -25,17 +25,11 @@ msgid "Configuring the Traefik reverse-proxy (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:3 -msgid "" -"By default, this playbook installs and manages a " -"[Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered " -"by the [ansible-role-traefik](https://github.com/mother-of-all-self-" -"hosting/ansible-role-traefik) Ansible role." +msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:5 -msgid "" -"This Ansible role support various configuration options. Feel free to " -"consult its `default/main.yml` variables file." +msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:7 @@ -43,9 +37,7 @@ msgid "Adjusting SSL certificate retrieval" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:9 -msgid "" -"See the dedicated [Adjusting SSL certificate retrieval](configuring-" -"playbook-ssl-certificates.md) documentation page." +msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:11 @@ -65,22 +57,11 @@ msgid "Enable Traefik Dashboard" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:27 -msgid "" -"This will enable a Traefik " -"[Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at " -"`https://matrix.example.com/dashboard/` (note the trailing `/`)." +msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:37 -msgid "" -"**WARNING**: Enabling the dashboard on a hostname you use for something " -"else (like `matrix_server_fqn_matrix` in the configuration above) may " -"cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all" -" `/dashboard` and `/api` requests and forward them to itself. If any of " -"the services hosted on the same hostname requires any of these 2 URL " -"prefixes, you will experience problems. So far, we're not aware of any " -"playbook services which occupy these endpoints and are likely to cause " -"conflicts." +msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:39 @@ -88,10 +69,7 @@ msgid "Additional configuration" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:41 -msgid "" -"Use the `traefik_configuration_extension_yaml` variable provided by the " -"Traefik Ansible role to override or inject additional settings, even when" -" no dedicated variable exists." +msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:51 @@ -99,24 +77,11 @@ msgid "Reverse-proxying another service behind Traefik" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:53 -msgid "" -"The preferred way to reverse-proxy additional services behind Traefik " -"would be to start the service as another container, configure the " -"container with the corresponding Traefik [container " -"labels](https://docs.docker.com/config/labels-custom-metadata/) (see " -"[Traefik & " -"Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and " -"connect the service to the `traefik` network. Some services are also " -"already available via the compatible [mash-playbook](https://github.com" -"/mother-of-all-self-hosting/mash-playbook), but take a look at the minor " -"[interoperability adjustments](https://github.com/mother-of-all-self-" -"hosting/mash-playbook/blob/main/docs/interoperability.md)." +msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:55 -msgid "" -"However, if your service does not run on a container or runs on another " -"machine, the following configuration might be what you are looking for." +msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:57 @@ -124,51 +89,28 @@ msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:59 -msgid "" -"If you want to host another webserver would be reachable via `my-fancy-" -"website.example.net` from the internet and via `https://:` from inside your network, you can " -"make the playbook's integrated Traefik instance reverse-proxy the traffic" -" to the correct host." +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:61 -msgid "" -"Prerequisites: DNS and routing for the domain `my-fancy-" -"website.example.net` need to be set up correctly. In this case, you'd be " -"pointing the domain name to your Matrix server - `my-fancy-" -"website.example.net` would be a CNAME going to `matrix.example.com`." +msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:63 -msgid "" -"First, we have to adjust the static configuration of Traefik, so that we " -"can add additional configuration files:" +msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:77 -msgid "" -"If you are using a self-signed certificate on your webserver, you can " -"tell Traefik to trust your own backend servers by adding more " -"configuration to the static configuration file. If you do so, bear in " -"mind the security implications of disabling the certificate validity " -"checks towards your back end." +msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:91 -msgid "" -"Next, you have to add a new dynamic configuration file for Traefik that " -"contains the actual information of the server using the " -"`aux_file_definitions` variable. In this example, we will terminate SSL " -"at the Traefik instance and connect to the other server via HTTPS. " -"Traefik will now take care of managing the certificates." +msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:110 #: ../../../docs/configuring-playbook-traefik.md:133 -msgid "" -"Changing the `url` to one with an `http://` prefix would allow to connect" -" to the server via HTTP." +msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:112 @@ -176,28 +118,15 @@ msgid "Reverse-proxying another service behind Traefik without terminating SSL" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:114 -msgid "" -"If you do not want to terminate SSL at the Traefik instance (for example," -" because you're already terminating SSL at other webserver), you need to " -"adjust the static configuration in the same way as in the previous " -"chapter in order to be able to add our own dynamic configuration files. " -"Afterwards, you can add the following configuration to your `vars.yml` " -"configuration file:" +msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:135 -msgid "" -"With these changes, all TCP traffic will be reverse-proxied to the target" -" system." +msgid "With these changes, all TCP traffic will be reverse-proxied to the target system." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:137 -msgid "" -"**WARNING**: This configuration might lead to problems or need additional" -" steps when a [certbot](https://certbot.eff.org/) behind Traefik also " -"tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, " -"as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-" -"challenge/`)```." +msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```." msgstr "" #: ../../../docs/configuring-playbook-traefik.md:139 @@ -205,8 +134,5 @@ msgid "Traefik behind a `proxy_protocol` reverse-proxy" msgstr "" #: ../../../docs/configuring-playbook-traefik.md:141 -msgid "" -"If you run a reverse-proxy which speaks `proxy_protocol`, add the " -"following to your configuration file:" +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 7ec5ad0df..b8e523207 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po @@ -25,17 +25,11 @@ msgid "Adjusting TURN server configuration (optional, advanced)" msgstr "" #: ../../../docs/configuring-playbook-turn.md:3 -msgid "" -"The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN " -"server by default, so that clients can make audio/video calls even from " -"[NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed " -"networks." +msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks." msgstr "" #: ../../../docs/configuring-playbook-turn.md:5 -msgid "" -"By default, the Synapse chat server is configured, so that it points to " -"the Coturn TURN server installed by the playbook." +msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook." msgstr "" #: ../../../docs/configuring-playbook-turn.md:7 @@ -43,16 +37,11 @@ msgid "Disabling Coturn" msgstr "" #: ../../../docs/configuring-playbook-turn.md:9 -msgid "" -"If, for some reason, you'd like to prevent the playbook from installing " -"Coturn, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:15 -msgid "" -"In that case, Synapse would not point to any Coturn servers and " -"audio/video call functionality may fail." +msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail." msgstr "" #: ../../../docs/configuring-playbook-turn.md:17 @@ -60,36 +49,19 @@ msgid "Manually defining your public IP" msgstr "" #: ../../../docs/configuring-playbook-turn.md:19 -msgid "" -"In the `hosts` file we explicitly ask for your server's external IP " -"address when defining `ansible_host`, because the same value is used for " -"configuring Coturn." +msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring Coturn." msgstr "" #: ../../../docs/configuring-playbook-turn.md:21 -msgid "" -"If you'd rather use a local IP for `ansible_host`, make sure to set up " -"`matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with " -"the pubic IP used by the server." +msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server." msgstr "" #: ../../../docs/configuring-playbook-turn.md:27 -msgid "" -"If you'd like to rely on external IP address auto-detection (not " -"recommended unless you need it), set " -"`matrix_coturn_turn_external_ip_address` to an empty value. The playbook " -"will automatically contact an " -"[EchoIP](https://github.com/mpolden/echoip)-compatible service " -"(`https://ifconfig.co/json` by default) to determine your server's IP " -"address. This API endpoint is configurable via the " -"`matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url`" -" variable." +msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable." msgstr "" #: ../../../docs/configuring-playbook-turn.md:29 -msgid "" -"If your server has multiple external IP addresses, the Coturn role offers" -" a different variable for specifying them:" +msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:36 @@ -97,13 +69,7 @@ msgid "Changing the authentication mechanism" msgstr "" #: ../../../docs/configuring-playbook-turn.md:38 -msgid "" -"The playbook uses the [`auth-secret` authentication " -"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199)" -" by default, but you may switch to the [`lt-cred-mech` " -"method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178)" -" which [some report](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/3191) to be working better." +msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better." msgstr "" #: ../../../docs/configuring-playbook-turn.md:40 @@ -111,17 +77,11 @@ msgid "To do so, add this override to your configuration:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:46 -msgid "" -"Regardless of the selected authentication method, the playbook generates " -"secrets automatically and passes them to the homeserver and Coturn." +msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and Coturn." msgstr "" #: ../../../docs/configuring-playbook-turn.md:48 -msgid "" -"If you're using [Jitsi](./configuring-playbook-jitsi.md), note that " -"switching to `lt-cred-mech` will remove the integration between Jitsi and" -" your own Coturn server, because Jitsi only seems to support the `auth-" -"secret` authentication method." +msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method." msgstr "" #: ../../../docs/configuring-playbook-turn.md:50 @@ -129,16 +89,11 @@ msgid "Using your own external Coturn server" msgstr "" #: ../../../docs/configuring-playbook-turn.md:52 -msgid "" -"If you'd like to use another TURN server (be it Coturn or some other " -"one), you can configure the playbook like this:" +msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:" msgstr "" #: ../../../docs/configuring-playbook-turn.md:66 -msgid "" -"If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you" -" might want to enable the TURN server there too. If you do not do it, " -"Jitsi will fall back to an upstream service." +msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service." msgstr "" #: ../../../docs/configuring-playbook-turn.md:72 @@ -150,8 +105,5 @@ msgid "Further variables and configuration options" msgstr "" #: ../../../docs/configuring-playbook-turn.md:75 -msgid "" -"To see all the available configuration options, check roles/custom" -"/matrix-coturn/defaults/main.yml" +msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index d33faf33d..35da30ba4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -25,42 +25,23 @@ msgid "Setting up Matrix User Verification Service (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:3 -msgid "" -"**[Matrix User Verification Service](https://github.com/matrix-org" -"/matrix-user-verification-service) (hereafter: UVS) can only be installed" -" after Matrix services are installed and running.** If you're just " -"installing Matrix services for the first time, please continue with the " -"[Configuration](configuring-playbook.md) / [Installation](installing.md) " -"flow and come back here later." +msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:5 -msgid "" -"Currently, the main purpose of this role is to allow Jitsi to " -"authenticate Matrix users and check if they are authorized to join a " -"conference. Please refer to the documentation of the [Matrix User " -"Verification Service](https://github.com/matrix-org/matrix-user-" -"verification-service) to understand how it works." +msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:7 -msgid "" -"**Note**: enabling Matrix User Verification Service, means that the " -"`openid` API endpoints will be exposed on the Matrix Federation port " -"(usually `8448`), even if [federation](configuring-playbook-" -"federation.md) is disabled." +msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:9 -msgid "" -"If the Jitsi server is also configured by this playbook, all plugging of " -"variables and secrets is handled in `group_vars/matrix_servers`." +msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:11 -msgid "" -"__Some general concepts of UVS may be helpful to understand the rest, so " -"here they are:__" +msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:13 @@ -72,27 +53,15 @@ msgid "(A) Whether a given OpenID token is valid for a given server and" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:16 -msgid "" -"(B) whether a user is member of a given room and the corresponding " -"PowerLevel" +msgid "(B) whether a user is member of a given room and the corresponding PowerLevel" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:18 -msgid "" -"Verifying an OpenID token ID done by finding the corresponding Homeserver" -" via '.well-known/matrix/server' for the given domain. The configured " -"`matrix_user_verification_service_uvs_homeserver_url` does **not** factor" -" into this. By default, this playbook only checks against " -"`matrix_server_fqn_matrix`. Therefore, the request will be made against " -"the public openid API for `matrix_server_fqn_matrix`." +msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:20 -msgid "" -"Verifying RoomMembership and PowerLevel is done against " -"`matrix_user_verification_service_uvs_homeserver_url` which is by default" -" done via the docker network. UVS will verify the validity of the token " -"beforehand though." +msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:22 @@ -100,10 +69,7 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:24 -msgid "" -"In order to use UVS, an admin token for the configured homeserver must be" -" supplied. For now this means configuring Synapse and creating the token " -"before installing UVS." +msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:26 @@ -111,10 +77,7 @@ msgid "Enable" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:28 -msgid "" -"To enable Matrix User Verification Service, add the following " -"configuration to your `inventory/host_vars/matrix.example.com/vars.yml` " -"file:" +msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:34 @@ -122,25 +85,15 @@ msgid "Configuration" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:36 -msgid "" -"The only required configuration variable is " -"`matrix_user_verification_service_uvs_access_token` (see below)." +msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:38 -msgid "" -"For a list of all configuration options see the role defaults [`roles" -"/matrix-user-verification-service/defaults/main.yml`](../roles/custom" -"/matrix-user-verification-service/defaults/main.yml). But be aware of all" -" the plugging happening in `group_vars/matrix_servers`." +msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:40 -msgid "" -"In the default configuration, the UVS Server is only reachable via the " -"docker network, which is fine if e.g. Jitsi is also running in a " -"container on the host. However, it is possible to expose UVS via setting " -"`matrix_user_verification_service_container_http_host_bind_port`." +msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:42 @@ -148,30 +101,19 @@ msgid "Access token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:44 -msgid "" -"The Synapse Access Token is used to verify RoomMembership and PowerLevel " -"against `matrix_user_verification_service_uvs_homeserver_url`." +msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:46 -msgid "" -"We recommend that you create a dedicated Matrix user for uvs (`uvs` is a " -"good username). Follow our [Registering users](registering-users.md) " -"guide to register a user with administration privileges." +msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:48 -msgid "" -"You are required to specify an access token (belonging to this new user) " -"for UVS to work. To get an access token for the UVS user, you can follow " -"the documentation on [how to do obtain an access token](obtaining-access-" -"tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:50 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:56 @@ -179,29 +121,19 @@ msgid "(Optional) Custom Auth Token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:58 -msgid "" -"It is possible to set an API Auth Token to restrict access to the UVS. If" -" this is enabled, anyone making a request to UVS must provide it via the " -"header \"Authorization: Bearer TOKEN\"" +msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\"" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:60 -msgid "" -"By default, the token will be derived from " -"`matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." +msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:62 -msgid "" -"To set your own Token, add the following configuration to your `vars.yml`" -" file:" +msgid "To set your own Token, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:68 -msgid "" -"In case Jitsi is also managed by this playbook and 'matrix' " -"authentication in Jitsi is enabled, this collection will automatically " -"configure Jitsi to use the configured auth token." +msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:70 @@ -209,9 +141,7 @@ msgid "(Optional) Disable Auth" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:72 -msgid "" -"Authorization is enabled by default. To disable it, add the following " -"configuration to your `vars.yml` file:" +msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:78 @@ -219,16 +149,11 @@ msgid "(Optional) Federation" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:80 -msgid "" -"In theory (however currently untested), UVS can handle federation. To " -"enable it, add the following configuration to your `vars.yml` file:" +msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:86 -msgid "" -"This will instruct UVS to verify the OpenID token against any domain " -"given in a request. Homeserver discovery is done via '.well-" -"known/matrix/server' of the given domain." +msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:88 @@ -236,25 +161,15 @@ msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:90 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:97 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-service matrix-user-verification-service` or " -"`just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:99 -msgid "" -"`just install-service matrix-user-verification-service` is useful for " -"maintaining your setup quickly when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"`just setup-all` runs the `ensure-matrix-users-created` tag too." +msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:101 @@ -282,9 +197,7 @@ msgid "TLS Certificate Checking" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:110 -msgid "" -"If the Matrix Homeserver does not provide a valid TLS certificate, UVS " -"will fail with the following error message:" +msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:112 @@ -296,44 +209,9 @@ msgid "This also applies to self-signed and let's encrypt staging certificates." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:116 -msgid "" -"To disable certificate validation altogether (INSECURE! Not suitable for " -"production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" +msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:118 -msgid "" -"Alternatively, it is possible to inject your own CA certificates into the" -" container by mounting a PEM file with additional trusted CAs into the " -"container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to " -"it." +msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it." msgstr "" - -#~ msgid "" -#~ "After these variables have been set, " -#~ "run the playbook with [playbook tags" -#~ "](playbook-tags.md) as below to restart " -#~ "UVS:" -#~ msgstr "" - -#~ msgid "" -#~ "The shortcut commands with the [`just`" -#~ " program](just.md) are also available: " -#~ "`just run-tags setup-matrix-user-" -#~ "verification-service,start` or `just setup-" -#~ "all`" -#~ msgstr "" - -#~ msgid "" -#~ "`just run-tags setup-matrix-user-" -#~ "verification-service,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 "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po index 678f78e99..816d84ffc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po @@ -25,40 +25,23 @@ msgid "Configuring the playbook" msgstr "" #: ../../../docs/configuring-playbook.md:3 -msgid "" -"[Prerequisites](prerequisites.md) > [Configuring your DNS settings" -"](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) >" -" Configuring the playbook > [Installing](installing.md)" +msgid "[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)" msgstr "" #: ../../../docs/configuring-playbook.md:5 -msgid "" -"If you've configured your DNS records and retrieved the playbook's source" -" code to your computer, you can start configuring the playbook. To do so," -" follow these steps inside the playbook directory:" +msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:" msgstr "" #: ../../../docs/configuring-playbook.md:7 -msgid "" -"create a directory to hold your configuration (`mkdir -p " -"inventory/host_vars/matrix.example.com` where `example.com` is your " -"\"base domain\")" +msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")" msgstr "" #: ../../../docs/configuring-playbook.md:9 -msgid "" -"copy the sample configuration file (`cp examples/vars.yml " -"inventory/host_vars/matrix.example.com/vars.yml`)" +msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" #: ../../../docs/configuring-playbook.md:11 -msgid "" -"edit the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You " -"may also take a look at the various " -"`roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's " -"something you'd like to copy over and override in your `vars.yml` " -"configuration file." +msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file." msgstr "" #: ../../../docs/configuring-playbook.md:13 @@ -70,19 +53,11 @@ msgid "edit the inventory hosts file (`inventory/hosts`) to your liking" msgstr "" #: ../../../docs/configuring-playbook.md:17 -msgid "" -"(optional, advanced) you may wish to keep your `inventory` directory " -"under version control with [git](https://git-scm.com/) or any other " -"version-control system." +msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system." msgstr "" #: ../../../docs/configuring-playbook.md:19 -msgid "" -"(optional, advanced) to run Ansible against multiple servers with " -"different `sudo` credentials, you can copy the sample inventory hosts " -"yaml file for each of your hosts: (`cp examples/host.yml " -"inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin" -"/ansible-all-hosts.sh) script [in the installation step](installing.md)." +msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)." msgstr "" #: ../../../docs/configuring-playbook.md:21 @@ -90,15 +65,11 @@ msgid "For a basic Matrix installation, that's all you need." msgstr "" #: ../../../docs/configuring-playbook.md:23 -msgid "" -"For a more custom setup, see the [Other configuration options](#other-" -"configuration-options) below." +msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below." msgstr "" #: ../../../docs/configuring-playbook.md:25 -msgid "" -"[▶️](installing.md) When you're done with all the configuration you'd " -"like to do, continue with [Installing](installing.md)." +msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)." msgstr "" #: ../../../docs/configuring-playbook.md:27 @@ -114,22 +85,15 @@ msgid "Homeserver configuration:" msgstr "" #: ../../../docs/configuring-playbook.md:32 -msgid "" -"[Configuring Synapse](configuring-playbook-synapse.md), if you're going " -"with the default/recommended homeserver implementation" +msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:34 -msgid "" -"[Configuring Conduit](configuring-playbook-conduit.md), if you've " -"switched to the [Conduit](https://conduit.rs) homeserver implementation" +msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:36 -msgid "" -"[Configuring Dendrite](configuring-playbook-dendrite.md), if you've " -"switched to the [Dendrite](https://matrix-org.github.io/dendrite) " -"homeserver implementation" +msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation" msgstr "" #: ../../../docs/configuring-playbook.md:38 @@ -137,33 +101,23 @@ msgid "Server components:" msgstr "" #: ../../../docs/configuring-playbook.md:39 -msgid "" -"[Using an external PostgreSQL server](configuring-playbook-external-" -"postgres.md)" +msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)" msgstr "" #: ../../../docs/configuring-playbook.md:41 -msgid "" -"[Adjusting TURN server configuration](configuring-playbook-turn.md) " -"(advanced)" +msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:43 -msgid "" -"[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) " -"(advanced)" +msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:45 -msgid "" -"[Using your own webserver, instead of this playbook's Traefik reverse-" -"proxy](configuring-playbook-own-webserver.md) (advanced)" +msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:47 -msgid "" -"[Adjusting SSL certificate retrieval](configuring-playbook-ssl-" -"certificates.md) (advanced)" +msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:49 @@ -183,9 +137,7 @@ msgid "Server connectivity:" msgstr "" #: ../../../docs/configuring-playbook.md:56 -msgid "" -"[Enabling Telemetry for your Matrix server](configuring-playbook-" -"telemetry.md)" +msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)" msgstr "" #: ../../../docs/configuring-playbook.md:58 @@ -201,31 +153,19 @@ msgid "Web clients for Matrix that you can host on your own domains." msgstr "" #: ../../../docs/configuring-playbook.md:64 -msgid "" -"[Configuring Element Web](configuring-playbook-client-element-web.md), if" -" you're going with the default/recommended client" +msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client" msgstr "" #: ../../../docs/configuring-playbook.md:66 -msgid "" -"[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've" -" enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a " -"lightweight Matrix client with legacy and mobile browser support" +msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support" msgstr "" #: ../../../docs/configuring-playbook.md:68 -msgid "" -"[Setting up Cinny](configuring-playbook-client-cinny.md), if you've " -"enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing " -"primarily on simple, elegant and secure interface" +msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface" msgstr "" #: ../../../docs/configuring-playbook.md:70 -msgid "" -"[Setting up SchildiChat Web](configuring-playbook-client-schildichat-" -"web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a " -"web client based on [Element Web](https://element.io/) with some extras " -"and tweaks" +msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks" msgstr "" #: ../../../docs/configuring-playbook.md:72 @@ -237,16 +177,11 @@ msgid "Extend and modify how users are authenticated on your homeserver." msgstr "" #: ../../../docs/configuring-playbook.md:76 -msgid "" -"[Setting up Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md) (Next-generation auth for Matrix, based on " -"OAuth 2.0/OIDC)" +msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)" msgstr "" #: ../../../docs/configuring-playbook.md:78 -msgid "" -"[Setting up Appservice Double Puppet](configuring-playbook-appservice-" -"double-puppet.md)" +msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)" msgstr "" #: ../../../docs/configuring-playbook.md:80 @@ -254,45 +189,31 @@ msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)" msgstr "" #: ../../../docs/configuring-playbook.md:82 -msgid "" -"[Setting up matrix-registration](configuring-playbook-matrix-" -"registration.md)" +msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../docs/configuring-playbook.md:84 -msgid "" -"[Setting up the REST authentication password provider module" -"](configuring-playbook-rest-auth.md) (advanced)" +msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:86 -msgid "" -"[Setting up the Shared Secret Auth password provider module](configuring-" -"playbook-shared-secret-auth.md) (advanced)" +msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:88 -msgid "" -"[Setting up the LDAP authentication password provider module" -"](configuring-playbook-ldap-auth.md) (advanced)" +msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:90 -msgid "" -"[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-" -"ldap-registration-proxy.md) (advanced)" +msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:92 -msgid "" -"[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-" -"antispam.md) (advanced)" +msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:94 -msgid "" -"[Setting up Matrix User Verification Service](configuring-playbook-user-" -"verification-service.md) (advanced)" +msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:96 @@ -304,21 +225,15 @@ msgid "Use alternative file storage to the default `media_store` folder." msgstr "" #: ../../../docs/configuring-playbook.md:100 -msgid "" -"[Storing Matrix media files on Amazon S3 with Goofys](configuring-" -"playbook-s3-goofys.md)" +msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)" msgstr "" #: ../../../docs/configuring-playbook.md:102 -msgid "" -"[Storing Synapse media files on Amazon S3 or another compatible Object " -"Storage](configuring-playbook-s3.md)" +msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)" msgstr "" #: ../../../docs/configuring-playbook.md:104 -msgid "" -"[Storing Matrix media files using matrix-media-repo](configuring-" -"playbook-matrix-media-repo.md)" +msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)" msgstr "" #: ../../../docs/configuring-playbook.md:106 @@ -326,155 +241,103 @@ msgid "Bridging other networks" msgstr "" #: ../../../docs/configuring-playbook.md:108 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../docs/configuring-playbook.md:110 -msgid "" -"[Setting up Mautrix Discord bridging](configuring-playbook-bridge-" -"mautrix-discord.md)" +msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:112 -msgid "" -"[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-" -"mautrix-telegram.md)" +msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:114 -msgid "" -"[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-" -"slack.md)" +msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:116 -msgid "" -"[Setting up Mautrix Google Messages bridging](configuring-playbook-" -"bridge-mautrix-gmessages.md)" +msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)" msgstr "" #: ../../../docs/configuring-playbook.md:118 -msgid "" -"[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-" -"mautrix-whatsapp.md)" +msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)" msgstr "" #: ../../../docs/configuring-playbook.md:120 -msgid "" -"[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-" -"bridge-mautrix-meta-instagram.md)" +msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:122 -msgid "" -"[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-" -"bridge-mautrix-meta-messenger.md)" +msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)" msgstr "" #: ../../../docs/configuring-playbook.md:124 -msgid "" -"[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-" -"mautrix-googlechat.md)" +msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)" msgstr "" #: ../../../docs/configuring-playbook.md:126 -msgid "" -"[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-" -"mautrix-twitter.md)" +msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:128 -msgid "" -"[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-" -"signal.md)" +msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)" msgstr "" #: ../../../docs/configuring-playbook.md:130 -msgid "" -"[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage" -"](configuring-playbook-bridge-mautrix-wsproxy.md)" +msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)" msgstr "" #: ../../../docs/configuring-playbook.md:132 -msgid "" -"[Setting up Appservice IRC bridging](configuring-playbook-bridge-" -"appservice-irc.md)" +msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../docs/configuring-playbook.md:134 -msgid "" -"[Setting up Appservice Discord bridging](configuring-playbook-bridge-" -"appservice-discord.md)" +msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:136 -msgid "" -"[Setting up Appservice Slack bridging](configuring-playbook-bridge-" -"appservice-slack.md)" +msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:138 -msgid "" -"[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-" -"appservice-kakaotalk.md)" +msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../docs/configuring-playbook.md:140 -msgid "" -"[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-" -"linkedin.md)" +msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)" msgstr "" #: ../../../docs/configuring-playbook.md:142 -msgid "" -"[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a" -" bridge between Matrix and multiple project management services, such as " -"[GitHub](https://github.com), [GitLab](https://about.gitlab.com) and " -"[JIRA](https://www.atlassian.com/software/jira)." +msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)." msgstr "" #: ../../../docs/configuring-playbook.md:144 -msgid "" -"[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-" -"puppet-slack.md)" +msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)" msgstr "" #: ../../../docs/configuring-playbook.md:146 -msgid "" -"[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-" -"puppet-instagram.md)" +msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)" msgstr "" #: ../../../docs/configuring-playbook.md:148 -msgid "" -"[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-" -"puppet-twitter.md)" +msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:150 -msgid "" -"[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-" -"puppet-discord.md)" +msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../docs/configuring-playbook.md:152 -msgid "" -"[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-" -"puppet-groupme.md)" +msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)" msgstr "" #: ../../../docs/configuring-playbook.md:154 -msgid "" -"[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-" -"puppet-steam.md)" +msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)" msgstr "" #: ../../../docs/configuring-playbook.md:156 -msgid "" -"[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-" -"skype-bridge.md)" +msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)" msgstr "" #: ../../../docs/configuring-playbook.md:158 @@ -482,21 +345,15 @@ msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)" msgstr "" #: ../../../docs/configuring-playbook.md:160 -msgid "" -"[Setting up Postmoogle email bridging](configuring-playbook-bridge-" -"postmoogle.md)" +msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)" msgstr "" #: ../../../docs/configuring-playbook.md:162 -msgid "" -"[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-" -"bridge-sms.md)" +msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)" msgstr "" #: ../../../docs/configuring-playbook.md:164 -msgid "" -"[Setting up Heisenbridge bouncer-style IRC bridging](configuring-" -"playbook-bridge-heisenbridge.md)" +msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)" msgstr "" #: ../../../docs/configuring-playbook.md:166 @@ -512,66 +369,39 @@ msgid "Bots provide various additional functionality to your installation." msgstr "" #: ../../../docs/configuring-playbook.md:172 -msgid "" -"[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through " -"which you can talk to various " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) " -"services ([OpenAI](https://openai.com/)'s " -"[ChatGPT](https://openai.com/blog/chatgpt/) and " -"[others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" +msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))" msgstr "" #: ../../../docs/configuring-playbook.md:174 -msgid "" -"[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-" -"reminder-bot.md) - a bot to remind you about stuff" +msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff" msgstr "" #: ../../../docs/configuring-playbook.md:176 -msgid "" -"[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-" -"registration-bot.md) - a bot to create and manage registration tokens to " -"invite users" +msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users" msgstr "" #: ../../../docs/configuring-playbook.md:178 -msgid "" -"[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based " -"Matrix bot system" +msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system" msgstr "" #: ../../../docs/configuring-playbook.md:180 -msgid "" -"[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk " -"bot" +msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot" msgstr "" #: ../../../docs/configuring-playbook.md:182 -msgid "" -"[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation " -"tool/bot" +msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot" msgstr "" #: ../../../docs/configuring-playbook.md:184 -msgid "" -"[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a " -"moderation tool/bot, forked from Mjolnir and maintained by its former " -"leader developer" +msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer" msgstr "" #: ../../../docs/configuring-playbook.md:186 -msgid "" -"[Setting up Draupnir for all/D4A](configuring-playbook-appservice-" -"draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-" -"draupnir.md) mentioned above, but running in appservice mode and " -"supporting multiple instances" +msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances" msgstr "" #: ../../../docs/configuring-playbook.md:188 -msgid "" -"[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you" -" can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" +msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room" msgstr "" #: ../../../docs/configuring-playbook.md:190 @@ -579,39 +409,27 @@ msgid "Administration" msgstr "" #: ../../../docs/configuring-playbook.md:192 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../docs/configuring-playbook.md:194 -msgid "" -"[Setting up Prometheus Alertmanager integration via matrix-alertmanager-" -"receiver](configuring-playbook-alertmanager-receiver.md)" +msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../docs/configuring-playbook.md:196 -msgid "" -"[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server" -"](configuring-playbook-prometheus-grafana.md)" +msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" msgstr "" #: ../../../docs/configuring-playbook.md:198 -msgid "" -"[Enabling metrics and graphs for NginX logs](configuring-playbook-" -"prometheus-nginxlog.md)" +msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)" msgstr "" #: ../../../docs/configuring-playbook.md:200 -msgid "" -"[Setting up the rageshake bug report server](configuring-playbook-" -"rageshake.md)" +msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)" msgstr "" #: ../../../docs/configuring-playbook.md:202 -msgid "" -"[Enabling synapse-usage-exporter for Synapse usage statistics" -"](configuring-playbook-synapse-usage-exporter.md)" +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/configuring-playbook.md:204 @@ -619,15 +437,11 @@ msgid "Backups:" msgstr "" #: ../../../docs/configuring-playbook.md:205 -msgid "" -"[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full " -"Matrix server backup solution, including the Postgres database" +msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database" msgstr "" #: ../../../docs/configuring-playbook.md:207 -msgid "" -"[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a" -" Postgres-database backup solution (note: does not include other files)" +msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)" msgstr "" #: ../../../docs/configuring-playbook.md:209 @@ -639,21 +453,15 @@ msgid "Various services that don't fit any other categories." msgstr "" #: ../../../docs/configuring-playbook.md:213 -msgid "" -"[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-" -"auto-accept-invite.md)" +msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../docs/configuring-playbook.md:215 -msgid "" -"[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-" -"compressor.md) for compressing the database on Synapse homeservers" +msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers" msgstr "" #: ../../../docs/configuring-playbook.md:217 -msgid "" -"[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) " -"(advanced)" +msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:219 @@ -661,21 +469,15 @@ msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" msgstr "" #: ../../../docs/configuring-playbook.md:221 -msgid "" -"[Setting up the Jitsi video-conferencing platform](configuring-playbook-" -"jitsi.md)" +msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)" msgstr "" #: ../../../docs/configuring-playbook.md:223 -msgid "" -"[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a" -" federated comment system built on Matrix" +msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix" msgstr "" #: ../../../docs/configuring-playbook.md:225 -msgid "" -"[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-" -"pantalaimon.md) (advanced)" +msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)" msgstr "" #: ../../../docs/configuring-playbook.md:227 @@ -683,9 +485,7 @@ msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" msgstr "" #: ../../../docs/configuring-playbook.md:229 -msgid "" -"[Setting up the ntfy push notifications server](configuring-playbook-" -"ntfy.md)" +msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)" msgstr "" #: ../../../docs/configuring-playbook.md:231 @@ -693,84 +493,41 @@ msgid "Deprecated / unmaintained / removed services" msgstr "" #: ../../../docs/configuring-playbook.md:233 -msgid "" -"**Note**: since a deprecated or unmaintained service will not be updated," -" its bug or vulnerability will be unlikely to get patched. It is " -"recommended to migrate from the service to an alternative if any, and " -"make sure to do your own research before you decide to keep it running " -"nonetheless." +msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless." msgstr "" #: ../../../docs/configuring-playbook.md:235 -msgid "" -"[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-" -"proxy.md) for clients which require Sliding Sync support (like old " -"Element X versions, before it got switched to Simplified Sliding Sync)" +msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)" msgstr "" #: ../../../docs/configuring-playbook.md:237 -msgid "" -"[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-" -"appservice-webhooks.md) (deprecated; the bridge's author suggests taking " -"a look at [matrix-hookshot](https://github.com/matrix-org/matrix-" -"hookshot) as a replacement, which can also be installed using [this " -"playbook](configuring-playbook-bridge-hookshot.md))" +msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:239 -msgid "" -"[Setting up the Dimension integration manager](configuring-playbook-" -"dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-" -"docker-ansible-deploy/issues/2806#issuecomment-1673559299); after " -"[installing](installing.md))" +msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))" msgstr "" #: ../../../docs/configuring-playbook.md:241 -msgid "" -"[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; " -"the bridge's author suggests taking a look at [matrix-" -"hookshot](https://github.com/matrix-org/matrix-hookshot) as a " -"replacement, which can also be installed using [this playbook" -"](configuring-playbook-bridge-hookshot.md))" +msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:243 -msgid "" -"[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) " -"(unmaintained; the bridge's author suggests taking a look at " -"[baibot](https://github.com/etkecc/baibot) as a replacement, which can " -"also be installed using [this playbook](configuring-playbook-bot-" -"baibot.md))" +msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))" msgstr "" #: ../../../docs/configuring-playbook.md:245 -msgid "" -"[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-" -"mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram " -"bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-" -"meta-messenger.md))" +msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))" msgstr "" #: ../../../docs/configuring-playbook.md:247 -msgid "" -"[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-" -"mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with " -"[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" +msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))" msgstr "" #: ../../../docs/configuring-playbook.md:249 -msgid "" -"[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-" -"mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram " -"bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-" -"meta-instagram.md))" +msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" msgstr "" #: ../../../docs/configuring-playbook.md:251 -msgid "" -"[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-" -"puppet-skype.md) (removed; this component has been broken for a long " -"time, so it has been removed from the playbook. Consider [setting up Go " -"Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" +msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po index c6f731a5d..be002abbb 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po @@ -25,10 +25,7 @@ msgid "Configuring Service Discovery via .well-known" msgstr "" #: ../../../docs/configuring-well-known.md:3 -msgid "" -"This documentation page explains how to configure Service discovery via " -"`/.well-known/` files. Service discovery is a way for the Matrix network " -"to discover where a Matrix server is." +msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is." msgstr "" #: ../../../docs/configuring-well-known.md:5 @@ -36,34 +33,19 @@ msgid "Types of well-known service discovery mechanism" msgstr "" #: ../../../docs/configuring-well-known.md:7 -msgid "" -"There are 3 types of well-known service discovery mechanism that Matrix " -"makes use of:" +msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:" msgstr "" #: ../../../docs/configuring-well-known.md:9 -msgid "" -"(important) **Federation Server discovery** (`/.well-" -"known/matrix/server`) -- assists other servers in the Matrix network with" -" finding your server. With the default playbook configuration specified " -"on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), " -"this is necessary for federation to work. Without a proper configuration," -" your server will effectively not be part of the Matrix network." +msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/configuring-well-known.md:11 -msgid "" -"(less important) **Client Server discovery** (`/.well-" -"known/matrix/client`) -- assists programs that you use to connect to your" -" server (e.g. Element Web), so that they can make it more convenient for " -"you by automatically configuring the \"Homeserver URL\" and \"Identity " -"Server URL\" addresses." +msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses." msgstr "" #: ../../../docs/configuring-well-known.md:13 -msgid "" -"(optional) **Support service discovery** (`/.well-known/matrix/support`) " -"-- returns server admin contact and support page of the domain." +msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain." msgstr "" #: ../../../docs/configuring-well-known.md:15 @@ -71,35 +53,19 @@ msgid "Federation Server Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:17 -msgid "" -"All services created by this playbook are meant to be installed on their " -"own server (such as `matrix.example.com`), instead of the base domain " -"(`example.com`)." +msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:19 -msgid "" -"As [per the Server-Server " -"specification](https://matrix.org/docs/spec/server_server/r0.1.0.html" -"#server-discovery), in order to use a short Matrix user ID like " -"`@alice:example.com` instead of `@alice:matrix.example.com` while hosting" -" services on a subdomain such as `matrix.example.com`, the Matrix network" -" needs to be instructed of [server delegation](howto-server-" -"delegation.md) / redirection." +msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection." msgstr "" #: ../../../docs/configuring-well-known.md:21 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file." msgstr "" #: ../../../docs/configuring-well-known.md:23 -msgid "" -"If you set up the DNS SRV record for server delegation instead, take a " -"look at this documentation for more information: [Server Delegation via a" -" DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-" -"via-a-dns-srv-record-advanced)" +msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/configuring-well-known.md:25 @@ -107,46 +73,23 @@ msgid "Client Server Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:27 -msgid "" -"Client Server Service discovery lets various client programs which " -"support it, to receive a full user ID (e.g. `@alice:example.com`) and " -"determine where the Matrix server is automatically (e.g. " -"`https://matrix.example.com`)." +msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:29 -msgid "" -"This lets you (and your users) easily connect to your Matrix server " -"without having to customize connection URLs. When using client programs " -"that support it, you won't need to point them to " -"`https://matrix.example.com` in Custom Server options manually anymore. " -"The connection URL would be discovered automatically from your full " -"username." +msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username." msgstr "" #: ../../../docs/configuring-well-known.md:31 -msgid "" -"Without /.well-known/matrix/client, the client will make the wrong " -"\"homeserver URL\" assumption (it will default to using " -"https://example.com, and users will need to notice and adjust it manually" -" (changing it to https://matrix.example.com)." +msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)." msgstr "" #: ../../../docs/configuring-well-known.md:33 -msgid "" -"As [per the Client-Server " -"specification](https://matrix.org/docs/spec/client_server/r0.4.0.html" -"#server-discovery) Matrix does Client Server service discovery using a " -"`/.well-known/matrix/client` file hosted on the base domain (e.g. " -"`example.com`)." +msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:35 -msgid "" -"However, this playbook installs your Matrix server on another domain " -"(e.g. `matrix.example.com`) and not on the base domain (e.g. " -"`example.com`), so it takes a little extra manual effort to set up the " -"file." +msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file." msgstr "" #: ../../../docs/configuring-well-known.md:37 @@ -154,20 +97,11 @@ msgid "(Optional) Support Service Discovery" msgstr "" #: ../../../docs/configuring-well-known.md:39 -msgid "" -"[MSC 1929](https://github.com/matrix-org/matrix-spec-" -"proposals/pull/1929), which was added to [Matrix Specification version " -"v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-" -"knownmatrixsupport), specifies a way to add contact details of admins, as" -" well as a link to a support page for users who are having issues with " -"the service. Automated services may also index this information and use " -"it for abuse reports, etc." +msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc." msgstr "" #: ../../../docs/configuring-well-known.md:41 -msgid "" -"To enable it, add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-well-known.md:62 @@ -175,9 +109,7 @@ msgid "Installing well-known files on the base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:64 -msgid "" -"To implement the service discovery mechanisms, your base domain's server " -"(e.g. `example.com`) needs to run an HTTPS-capable webserver." +msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver." msgstr "" #: ../../../docs/configuring-well-known.md:66 @@ -185,33 +117,19 @@ msgid "Serving the base domain from the Matrix server via the playbook" msgstr "" #: ../../../docs/configuring-well-known.md:68 -msgid "" -"If you don't have a server for your base domain at all, you can use the " -"Matrix server for this. If you don't need the base domain (e.g. " -"`example.com`) for anything else (hosting a website, etc.), you can point" -" it to the Matrix server's IP address and tell the playbook to configure " -"it." +msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it." msgstr "" #: ../../../docs/configuring-well-known.md:70 -msgid "" -"**This is the easiest way to set up well-known serving** -- letting the " -"playbook handle the whole base domain for you (including SSL " -"certificates, etc.) and take care to serve the appropriate well-known " -"files automatically." +msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically." msgstr "" #: ../../../docs/configuring-well-known.md:72 -msgid "" -"If you decide to go this route, you don't need to read ahead in this " -"document. Instead, go to [Serving the base domain](configuring-playbook-" -"base-domain-serving.md) to learn how the playbook can help you set it up." +msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up." msgstr "" #: ../../../docs/configuring-well-known.md:74 -msgid "" -"However, if you need to use the base domain for other things, this method" -" is less suitable than the one explained below." +msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below." msgstr "" #: ../../../docs/configuring-well-known.md:76 @@ -219,25 +137,15 @@ msgid "Manually installing well-known files on the base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:78 -msgid "" -"If you're managing the base domain by yourself somehow, you'll need to " -"set up serving of some `/.well-known/matrix/*` files from it via HTTPS." +msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS." msgstr "" #: ../../../docs/configuring-well-known.md:80 -msgid "" -"To make things easy for you to set up, this playbook generates and hosts " -"a few well-known files on the Matrix domain's server. The files are " -"generated at the `/matrix/static-files/public/.well-known/matrix/` path " -"on the server and hosted at URLs like `https://matrix.example.com/.well-" -"known/matrix/server` and `https://matrix.example.com/.well-" -"known/matrix/client`, even though this is the wrong place to host them." +msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them." msgstr "" #: ../../../docs/configuring-well-known.md:82 -msgid "" -"You have two options when it comes to installing the files on the base " -"domain's server:" +msgid "You have two options when it comes to installing the files on the base domain's server:" msgstr "" #: ../../../docs/configuring-well-known.md:84 @@ -245,9 +153,7 @@ msgid "(Option 1): **Copying the files manually** to your base domain's server" msgstr "" #: ../../../docs/configuring-well-known.md:86 -msgid "" -"**Hint**: Option 2 is generally a better way to do this. Make sure to go " -"with it, if possible." +msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible." msgstr "" #: ../../../docs/configuring-well-known.md:88 @@ -255,40 +161,19 @@ msgid "All you need to do is:" msgstr "" #: ../../../docs/configuring-well-known.md:90 -msgid "" -"copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from " -"the Matrix server (e.g. `matrix.example.com`) to your base domain's " -"server (`example.com`). You can find these files in the `/matrix/static-" -"files/.well-known/matrix` directory on the Matrix server. They are also " -"accessible on URLs like this: `https://matrix.example.com/.well-" -"known/matrix/server` (same for `client`)." +msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)." msgstr "" #: ../../../docs/configuring-well-known.md:92 -msgid "" -"set up the server at your base domain (e.g. `example.com`) so that it " -"adds an extra HTTP header when serving the `/.well-known/matrix/client` " -"file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the" -" `Access-Control-Allow-Origin` header should be set with a value of `*`. " -"If you don't do this step, web-based Matrix clients (like Element Web) " -"may fail to work. Setting up headers for the `/.well-known/matrix/server`" -" file is not necessary, as this file is only consumed by non-browsers, " -"which don't care about CORS." +msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS." msgstr "" #: ../../../docs/configuring-well-known.md:94 -msgid "" -"This is relatively easy to do and possibly your only choice if you can " -"only host static files from the base domain's server. It is, however, **a" -" little fragile**, as future updates performed by this playbook may " -"regenerate the well-known files and you may need to notice that and copy " -"them over again." +msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again." msgstr "" #: ../../../docs/configuring-well-known.md:96 -msgid "" -"(Option 2): **Setting up reverse-proxying** of the well-known files from " -"the base domain's server to the Matrix server" +msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server" msgstr "" #: ../../../docs/configuring-well-known.md:98 @@ -296,19 +181,11 @@ msgid "This option is less fragile and generally better." msgstr "" #: ../../../docs/configuring-well-known.md:100 -msgid "" -"On the base domain's server (e.g. `example.com`), you can set up reverse-" -"proxying, so that any access for the `/.well-known/matrix` location " -"prefix is forwarded to the Matrix domain's server (e.g. " -"`matrix.example.com`)." +msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)." msgstr "" #: ../../../docs/configuring-well-known.md:102 -msgid "" -"With this method, you **don't need** to add special HTTP headers for " -"[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons " -"(like `Access-Control-Allow-Origin`), because your Matrix server (where " -"requests ultimately go) will be configured by this playbook correctly." +msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly." msgstr "" #: ../../../docs/configuring-well-known.md:104 @@ -328,11 +205,7 @@ msgid "**For HAProxy**, it would be something like this:" msgstr "" #: ../../../docs/configuring-well-known.md:164 -msgid "" -"**For Netlify**, configure a " -"[redirect](https://docs.netlify.com/routing/redirects/) using a " -"`_redirects` file in the [publish directory](https://docs.netlify.com" -"/configure-builds/overview/#definitions) with contents like this:" +msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:" msgstr "" #: ../../../docs/configuring-well-known.md:170 @@ -344,9 +217,7 @@ msgid "Add a custom origin with matrix.example.com to your distribution" msgstr "" #: ../../../docs/configuring-well-known.md:173 -msgid "" -"Add two behaviors, one for `.well-known/matrix/client` and one for " -"`.well-known/matrix/server` and point them to your new origin." +msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin." msgstr "" #: ../../../docs/configuring-well-known.md:175 @@ -354,15 +225,11 @@ msgid "Make sure to:" msgstr "" #: ../../../docs/configuring-well-known.md:177 -msgid "" -"**replace `example.com`** in the server configuration with your actual " -"domain name" +msgid "**replace `example.com`** in the server configuration with your actual domain name" msgstr "" #: ../../../docs/configuring-well-known.md:178 -msgid "" -"and: to **do this for the HTTPS-enabled server block**, as that's where " -"Matrix expects the file to be" +msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be" msgstr "" #: ../../../docs/configuring-well-known.md:180 @@ -370,10 +237,7 @@ msgid "Confirming it works" msgstr "" #: ../../../docs/configuring-well-known.md:182 -msgid "" -"No matter which method you've used to set up the well-known files, if " -"you've done it correctly you should be able to see a JSON file at these " -"URLs:" +msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:" msgstr "" #: ../../../docs/configuring-well-known.md:184 @@ -389,8 +253,5 @@ msgid "`https://example.com/.well-known/matrix/support`" msgstr "" #: ../../../docs/configuring-well-known.md:188 -msgid "" -"You can also check if everything is configured correctly, by [checking if" -" services work](maintenance-checking-services.md)." +msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/container-images.po b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po index b62028a53..52d0a92fe 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/container-images.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po @@ -25,15 +25,11 @@ msgid "Container images used by the playbook" msgstr "" #: ../../../docs/container-images.md:3 -msgid "" -"This page summarizes the container ([Docker](https://www.docker.com/)) " -"images used by the playbook when setting up your server." +msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server." msgstr "" #: ../../../docs/container-images.md:5 -msgid "" -"We try to stick to official images (provided by their respective " -"projects) as much as possible." +msgid "We try to stick to official images (provided by their respective projects) as much as possible." msgstr "" #: ../../../docs/container-images.md:7 @@ -69,9 +65,7 @@ msgid "✅" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network" msgstr "" #: ../../../docs/container-images.md @@ -79,9 +73,7 @@ msgid "[Conduit](configuring-playbook-conduit.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit" -"/matrix-conduit)" +msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)" msgstr "" #: ../../../docs/container-images.md @@ -89,11 +81,7 @@ msgid "❌" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Conduit is a lightweight open-" -"source server implementation of the Matrix Specification with a focus on " -"easy setup and low system requirements" +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements" msgstr "" #: ../../../docs/container-images.md @@ -101,16 +89,11 @@ msgid "[Dendrite](configuring-playbook-dendrite.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg" -"/dendrite-monolith/)" +msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Storing your data and managing your presence in the " -"[Matrix](http://matrix.org/) network. Dendrite is a second-generation " -"Matrix homeserver written in Go, an alternative to Synapse." +msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse." msgstr "" #: ../../../docs/container-images.md:15 @@ -130,9 +113,7 @@ msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Default Matrix web client, configured to connect to your own Synapse " -"server" +msgid "Default Matrix web client, configured to connect to your own Synapse server" msgstr "" #: ../../../docs/container-images.md @@ -176,9 +157,7 @@ msgid "Server Components" msgstr "" #: ../../../docs/container-images.md:28 -msgid "" -"Services that run on the server to make the various parts of your " -"installation work." +msgid "Services that run on the server to make the various parts of your installation work." msgstr "" #: ../../../docs/container-images.md @@ -190,9 +169,7 @@ msgid "[postgres](https://hub.docker.com/_/postgres/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Database for Synapse. [Using an external PostgreSQL server](configuring-" -"playbook-external-postgres.md) is also possible." +msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible." msgstr "" #: ../../../docs/container-images.md @@ -216,10 +193,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Web server, listening on ports 80, 443 and 8448 - standing in front of " -"all the other services. Using your own webserver [is possible" -"](configuring-playbook-own-webserver.md)" +msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)" msgstr "" #: ../../../docs/container-images.md @@ -231,9 +205,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"The [certbot](https://certbot.eff.org/) tool for obtaining SSL " -"certificates from [Let's Encrypt](https://letsencrypt.org/)" +msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)" msgstr "" #: ../../../docs/container-images.md @@ -245,9 +217,7 @@ msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Mail server, through which all Matrix services send outgoing email (can " -"be configured to relay through another SMTP server)" +msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)" msgstr "" #: ../../../docs/container-images.md @@ -271,9 +241,7 @@ msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Update dynamic DNS entries for accounts on Dynamic DNS Network Service " -"Provider" +msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider" msgstr "" #: ../../../docs/container-images.md:40 @@ -297,9 +265,7 @@ msgid "REST authentication password provider module" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-" -"auth.md)" +msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)" msgstr "" #: ../../../docs/container-images.md @@ -315,9 +281,7 @@ msgid "LDAP Auth password provider module" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-" -"registration-proxy.md)" +msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)" msgstr "" #: ../../../docs/container-images.md @@ -325,9 +289,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co msgstr "" #: ../../../docs/container-images.md -msgid "" -"A proxy that handles Matrix registration requests and forwards them to " -"LDAP." +msgid "A proxy that handles Matrix registration requests and forwards them to LDAP." msgstr "" #: ../../../docs/container-images.md @@ -335,9 +297,7 @@ msgid "[matrix-registration](configuring-playbook-matrix-registration.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-" -"matrix-registration/)" +msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)" msgstr "" #: ../../../docs/container-images.md @@ -345,16 +305,11 @@ msgid "A simple python application to have a token based Matrix registration" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Matrix User Verification Service](configuring-playbook-user-" -"verification-service.md) (UVS)" +msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-user-verification-" -"service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-" -"service)" +msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)" msgstr "" #: ../../../docs/container-images.md @@ -362,9 +317,7 @@ msgid "Service to verify details of a user based on an Open ID token" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[synapse-simple-antispam](configuring-playbook-synapse-simple-" -"antispam.md) (advanced)" +msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)" msgstr "" #: ../../../docs/container-images.md @@ -388,9 +341,7 @@ msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object " -"store) storage for Synapse's content repository (`media_store`) files" +msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files" msgstr "" #: ../../../docs/container-images.md @@ -406,10 +357,7 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"matrix-media-repo is a highly customizable multi-domain media repository " -"for Matrix. Intended for medium to large deployments, this media repo de-" -"duplicates media while being fully compliant with the specification." +msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification." msgstr "" #: ../../../docs/container-images.md:64 @@ -417,9 +365,7 @@ msgid "Bridges" msgstr "" #: ../../../docs/container-images.md:66 -msgid "" -"Bridges can be used to connect your Matrix installation with third-party " -"communication networks." +msgid "Bridges can be used to connect your Matrix installation with third-party communication networks." msgstr "" #: ../../../docs/container-images.md @@ -519,10 +465,7 @@ msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-" -"messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-" -"instagram.md))" +msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))" msgstr "" #: ../../../docs/container-images.md @@ -530,9 +473,7 @@ msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge to [Messenger](https://messenger.com/) and " -"[Instagram](https://instagram.com/)" +msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)" msgstr "" #: ../../../docs/container-images.md @@ -564,9 +505,7 @@ msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-appservice-" -"irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" +msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)" msgstr "" #: ../../../docs/container-images.md @@ -574,9 +513,7 @@ msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-" -"kakaotalk.md)" +msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)" msgstr "" #: ../../../docs/container-images.md @@ -584,21 +521,15 @@ msgid "Self-building" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge to " -"[Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" +msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-discord](configuring-playbook-bridge-appservice-" -"discord.md)" +msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-" -"appservice-discord)" +msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)" msgstr "" #: ../../../docs/container-images.md @@ -610,9 +541,7 @@ msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixdotorg/matrix-appservice-" -"slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" +msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)" msgstr "" #: ../../../docs/container-images.md @@ -620,15 +549,11 @@ msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-" -"hookshot)" +msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge for generic webhooks and multiple project management services, " -"such as GitHub, GitLab, Figma, and Jira in particular" +msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular" msgstr "" #: ../../../docs/container-images.md @@ -636,10 +561,7 @@ msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[folivonet/matrix-sms-" -"bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-" -"bridge)" +msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)" msgstr "" #: ../../../docs/container-images.md @@ -667,9 +589,7 @@ msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bouncer-style bridge to " -"[IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" +msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)" msgstr "" #: ../../../docs/container-images.md @@ -677,9 +597,7 @@ msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-" -"bridge)" +msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)" msgstr "" #: ../../../docs/container-images.md @@ -691,9 +609,7 @@ msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-" -"puppet-slack/container_registry)" +msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)" msgstr "" #: ../../../docs/container-images.md @@ -705,9 +621,7 @@ msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md) msgstr "" #: ../../../docs/container-images.md -msgid "" -"[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-" -"puppet-instagram)" +msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)" msgstr "" #: ../../../docs/container-images.md @@ -719,9 +633,7 @@ msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-" -"twitter)" +msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)" msgstr "" #: ../../../docs/container-images.md @@ -733,9 +645,7 @@ msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-" -"puppet/discord/mx-puppet-discord/container_registry)" +msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)" msgstr "" #: ../../../docs/container-images.md @@ -743,9 +653,7 @@ msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-" -"groupme)" +msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)" msgstr "" #: ../../../docs/container-images.md @@ -757,9 +665,7 @@ msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-" -"puppet-steam)" +msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)" msgstr "" #: ../../../docs/container-images.md @@ -807,11 +713,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"A bot that exposes the power of " -"[AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large " -"Language Models](https://en.wikipedia.org/wiki/Large_language_model) to " -"you" +msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you" msgstr "" #: ../../../docs/container-images.md @@ -819,9 +721,7 @@ msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-" -"bot)" +msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)" msgstr "" #: ../../../docs/container-images.md @@ -829,15 +729,11 @@ msgid "Bot for scheduling one-off & recurring reminders and alarms" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-registration-bot](configuring-playbook-bot-matrix-registration-" -"bot.md)" +msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-" -"registration-bot/)" +msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)" msgstr "" #: ../../../docs/container-images.md @@ -909,40 +805,27 @@ msgid "Administration" msgstr "" #: ../../../docs/container-images.md:116 -msgid "" -"Services that help you in administrating and monitoring your Matrix " -"installation." +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-alertmanager-receiver](configuring-playbook-alertmanager-" -"receiver.md)" +msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio" -"/matrix-alertmanager-receiver)" +msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Prometheus' " -"[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) " -"client" +msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md)" +msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[element-hq/matrix-authentication-service](https://ghcr.io/element-hq" -"/matrix-authentication-service)" +msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)" msgstr "" #: ../../../docs/container-images.md @@ -978,9 +861,7 @@ msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Prometheus [node-exporter](https://prometheus.io/docs/guides/node-" -"exporter/) host metrics exporter" +msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter" msgstr "" #: ../../../docs/container-images.md @@ -988,11 +869,7 @@ msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Graphing tool that works well with the above two images. Our playbook " -"also adds two dashboards for [Synapse](https://github.com/element-" -"hq/synapse/tree/master/contrib/grafana) and [Node " -"Exporter](https://github.com/rfrail3/grafana-dashboards)" +msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)" msgstr "" #: ../../../docs/container-images.md @@ -1000,15 +877,11 @@ msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io" -"/martin-helmich/prometheus-nginxlog-exporter/exporter)" +msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Addon for Prometheus that gathers access logs from various nginx reverse-" -"proxies" +msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies" msgstr "" #: ../../../docs/container-images.md @@ -1036,9 +909,7 @@ msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Export the usage statistics of a Synapse homeserver to be scraped by " -"Prometheus." +msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." msgstr "" #: ../../../docs/container-images.md:131 @@ -1058,15 +929,11 @@ msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Sliding Sync support for clients which require it (like old Element X " -"versions, before it got switched to Simplified Sliding Sync)" +msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-" -"invite.md)" +msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)" msgstr "" #: ../../../docs/container-images.md @@ -1078,15 +945,11 @@ msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md msgstr "" #: ../../../docs/container-images.md -msgid "" -"[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-" -"synapse-compress-state/container_registry)" +msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"A cli tool that automatically compresses `state_groups` database table in" -" background." +msgid "A cli tool that automatically compresses `state_groups` database table in background." msgstr "" #: ../../../docs/container-images.md @@ -1094,9 +957,7 @@ msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-" -"corporal/)" +msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)" msgstr "" #: ../../../docs/container-images.md @@ -1156,9 +1017,7 @@ msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[cactuscomments/cactus-" -"appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" +msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)" msgstr "" #: ../../../docs/container-images.md @@ -1166,9 +1025,7 @@ msgid "A federated comment system built on Matrix" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-" -"web-server)" +msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)" msgstr "" #: ../../../docs/container-images.md @@ -1212,27 +1069,19 @@ msgid "Container images of deprecated / unmaintained services" msgstr "" #: ../../../docs/container-images.md:154 -msgid "" -"The list of the deprecated or unmaintained services is available [here" -"](configuring-playbook.md#deprecated--unmaintained--removed-services)." +msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)." msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-" -"webhooks.md)" +msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live" -"/matrix-appservice-webhooks)" +msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-" -"ci.org/), [Slack](https://slack.com/) etc. pp.)" +msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)" msgstr "" #: ../../../docs/container-images.md @@ -1240,9 +1089,7 @@ msgid "[Dimension](configuring-playbook-dimension.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-" -"dimension)" +msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)" msgstr "" #: ../../../docs/container-images.md @@ -1266,9 +1113,7 @@ msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)" msgstr "" #: ../../../docs/container-images.md -msgid "" -"[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-" -"bot)" +msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)" msgstr "" #: ../../../docs/container-images.md @@ -1310,4 +1155,3 @@ msgstr "" #: ../../../docs/container-images.md msgid "Bridge to [Instagram](https://instagram.com/)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/faq.po b/i18n/locales/jp/LC_MESSAGES/docs/faq.po index 1d9324658..5fd864486 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/faq.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/faq.po @@ -25,17 +25,11 @@ msgid "Frequently Asked Questions" msgstr "" #: ../../../docs/faq.md:3 -msgid "" -"This documentation page tries to answer various Frequently Asked " -"Questions about all things [Matrix](https://matrix.org/), with a focus on" -" this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How" -" does it work?](#what-is-ansible-how-does-it-work))." +msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))." msgstr "" #: ../../../docs/faq.md:5 -msgid "" -"This FAQ page does not intend to replace the [matrix.org " -"FAQ](https://matrix.org/faq/) (please see that one too)." +msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)." msgstr "" #: ../../../docs/faq.md:7 @@ -43,11 +37,7 @@ msgid "We've only started this FAQ recently, so it's still somewhat empty." msgstr "" #: ../../../docs/faq.md:9 -msgid "" -"Also, we encourage you to not dig yourself into a hole by reading way too" -" much. When you've heard enough, proceed to installation. To get started," -" see [below](#how-do-i-run-the-installation) about our installation " -"guides." +msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides." msgstr "" #: ../../../docs/faq.md:11 @@ -59,72 +49,39 @@ msgid "Where do I find more questions and answers about Matrix?" msgstr "" #: ../../../docs/faq.md:15 -msgid "" -"This is a Frequently Asked Questions page focused on this " -"[Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does " -"it work?](#what-is-ansible-how-does-it-work)) for deploying a " -"[Matrix](https://matrix.org/) server." +msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server." msgstr "" #: ../../../docs/faq.md:17 -msgid "" -"For a lot more generic questions and answers, see the [matrix.org " -"FAQ](https://matrix.org/faq/)." +msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" #: ../../../docs/faq.md:19 -msgid "" -"What is Matrix? What is Element? What is Synapse? Why are you confusing " -"me with so many terms?" +msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?" msgstr "" #: ../../../docs/faq.md:21 -msgid "" -"[Matrix](https://matrix.org/) is a new type of realtime communication " -"(chat) network, the closest analogy to which is probably \"email\"." +msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"." msgstr "" #: ../../../docs/faq.md:23 -msgid "" -"You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly " -"though. There's a *server* somewhere which stores your data " -"(`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you" -" access it by using these \"email\" protocols via some *client* program " -"(Outlook, Thunderbird, some website, etc)." +msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)." msgstr "" #: ../../../docs/faq.md:25 -msgid "" -"In the world of the Matrix chat protocol, there are various client " -"programs. The first and currently most full-featured one is called " -"[Element](https://element.io/) (used to be called Riot.im and Vector.im " -"in the past). There are [many other " -"clients](https://matrix.org/clients/). You can switch clients as much as " -"you want until you find the one that is right for you on a given platform" -" (you may use Element Desktop on your desktop, but Fluffychat on your " -"phone, etc)." +msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)." msgstr "" #: ../../../docs/faq.md:27 -msgid "" -"Matrix is also like email due to the fact that there are many servers " -"around the world which can all talk to each other (you can send email " -"from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` " -"addresses). It's the same with Matrix (`@bob:example.com` can talk to " -"`@alice:example.org`)." +msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)." msgstr "" #: ../../../docs/faq.md:29 -msgid "" -"If someone else is hosting your Matrix server (you being " -"`@alice:matrix.org` or some other public server like this), all you need " -"is a Matrix client program, like Element Web or Element X Android." +msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android." msgstr "" #: ../../../docs/faq.md:31 -msgid "" -"If you'd like to host your own server (you being `@alice:example.com`), " -"you'd need to set up a Matrix server program, like Synapse." +msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse." msgstr "" #: ../../../docs/faq.md:33 @@ -132,29 +89,19 @@ msgid "In short:" msgstr "" #: ../../../docs/faq.md:35 -msgid "" -"Matrix is the protocol - a set of rules about how the chat network " -"operates" +msgid "Matrix is the protocol - a set of rules about how the chat network operates" msgstr "" #: ../../../docs/faq.md:36 -msgid "" -"Element is a client program you can use to participate on the Matrix chat" -" network via some server (yours or someone else's). There are also [many " -"other client programs](https://matrix.org/clients/)." +msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)." msgstr "" #: ../../../docs/faq.md:37 -msgid "" -"Synapse is a server program you can use to host your very own Matrix " -"server." +msgid "Synapse is a server program you can use to host your very own Matrix server." msgstr "" #: ../../../docs/faq.md:39 -msgid "" -"This FAQ here mostly focuses on installing various Matrix services using " -"the Ansible automation tool. You can learn much more about Matrix in the " -"[matrix.org FAQ](https://matrix.org/faq/)." +msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)." msgstr "" #: ../../../docs/faq.md:41 @@ -162,22 +109,15 @@ msgid "People I wish to talk to are not on Matrix. Can I talk to them?" msgstr "" #: ../../../docs/faq.md:43 -msgid "" -"You most likely can. Besides Matrix-native chats, Matrix also supports " -"the concept of \"bridging\", which allows you to plug other networks into" -" it." +msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it." msgstr "" #: ../../../docs/faq.md:45 -msgid "" -"This Ansible playbook can help you install [tens of bridges for various " -"networks](configuring-playbook.md#bridging-other-networks)." +msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)." msgstr "" #: ../../../docs/faq.md:47 -msgid "" -"Besides setting up your own bridges (preferable), you can also use some " -"[public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." +msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)." msgstr "" #: ../../../docs/faq.md:49 @@ -185,50 +125,23 @@ msgid "How do I get started with Matrix?" msgstr "" #: ../../../docs/faq.md:51 -msgid "" -"One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared" -" to other chat networks) is its decentralized nature. There's not just " -"one entity (company, organization) controlling the servers. Rather " -"there's thousands of servers operated by different people - one server " -"being insecure, slow or disrespective toward its users does not affect " -"the rest of the network. To participate in that decentralization in its " -"fullest, consider hosting your own server or using some public server " -"other than the largest/default one (`matrix.org`)." +msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)." msgstr "" #: ../../../docs/faq.md:53 -msgid "" -"There are 3 ways to get into Matrix, depending on your technical ability " -"and needs:" +msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:" msgstr "" #: ../../../docs/faq.md:55 -msgid "" -"**using the existing default server** - the easiest way is to use an " -"existing server. The largest public Matrix server is `matrix.org` and " -"it's configured as a default server in clients such as [Element " -"Web](https://app.element.io) and many others. Just use Element Web on the" -" browser via that link (or [download client apps for your Desktop or " -"smartphone](https://element.io/app-for-productivity)), create an account " -"and start chatting." +msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting." msgstr "" #: ../../../docs/faq.md:57 -msgid "" -"**using some other server** - instead of using the largest public server " -"(`matrix.org`), you can use another public one. Here's a [list of public " -"Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to " -"[Element Web](https://app.element.io) or download [some other " -"client](https://matrix.org/clients/) of your choosing and adjust the " -"homeserver URL during login." +msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login." msgstr "" #: ../../../docs/faq.md:59 -msgid "" -"**using your own server** - running your own server puts you in ultimate " -"control of your data. It also lets you have your own user IDs (e.g. " -"`@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i" -"-set-up-my-own-matrix-server)." +msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)." msgstr "" #: ../../../docs/faq.md:61 @@ -236,33 +149,19 @@ msgid "How do I set up my own Matrix server?" msgstr "" #: ../../../docs/faq.md:63 -msgid "" -"Normally, you'd first choose the [Matrix](https://matrix.org/) server " -"software you'd like to run. At the time of this writing (January/2021), " -"there's only one fully-featured server program, so there's only one " -"reasonable choice. That's [Synapse](https://github.com/element-" -"hq/synapse)." +msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)." msgstr "" #: ../../../docs/faq.md:65 -msgid "" -"There are [many guides about installing " -"Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this " -"Ansible playbook is just one way of doing it." +msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it." msgstr "" #: ../../../docs/faq.md:67 -msgid "" -"Naturally, we're biased, so our usual recommendation is to go with this " -"[Ansible](https://www.ansible.com/) playbook, instead of installing " -"Synapse (and many many other things around it) manually." +msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually." msgstr "" #: ../../../docs/faq.md:69 -msgid "" -"To get started with the playbook, check out the [Quick start](quick-" -"start.md) or full installation guide (starting at the " -"[Prerequisites](prerequisites.md) page)." +msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)." msgstr "" #: ../../../docs/faq.md:71 @@ -270,31 +169,19 @@ msgid "What is Ansible? How does it work?" msgstr "" #: ../../../docs/faq.md:73 -msgid "" -"[Ansible](https://www.ansible.com/) is an automation program. This " -"\"playbook\" is a collection of tasks/scripts that will set up a " -"[Matrix](https://matrix.org/) server for you, so you don't have to " -"perform these tasks manually." +msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually." msgstr "" #: ../../../docs/faq.md:75 -msgid "" -"We have written these automated tasks for you and all you need to do is " -"execute them using the Ansible program." +msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program." msgstr "" #: ../../../docs/faq.md:77 -msgid "" -"You can install Ansible and this playbook code repository on your own " -"computer and tell it to install Matrix services at the server living at " -"`matrix.example.com`. We recommend installing Ansible on your own " -"computer." +msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer." msgstr "" #: ../../../docs/faq.md:79 -msgid "" -"Alternatively, you can download Ansible and the playbook itself directly " -"on the `matrix.example.com` server." +msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server." msgstr "" #: ../../../docs/faq.md:81 @@ -306,31 +193,19 @@ msgid "What is `just`?" msgstr "" #: ../../../docs/faq.md:85 -msgid "" -"[`just`](https://github.com/casey/just) is a modern command-runner " -"alternative to [make](https://www.gnu.org/software/make/). It can be used" -" to invoke commands with less typing." +msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing." msgstr "" #: ../../../docs/faq.md:87 -msgid "" -"The `just` utility executes shortcut commands (called \"recipes\"), which" -" invoke `ansible-playbook`, `ansible-galaxy` or " -"[`agru`](https://github.com/etkecc/agru) (depending on what is available " -"in your system). The targets of the recipes are defined in " -"[`justfile`](../justfile)." +msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)." msgstr "" #: ../../../docs/faq.md:89 -msgid "" -"For details about `just` commands, take a look at: [Running `just` " -"commands](just.md)." +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/faq.md:91 -msgid "" -"The playbook also contains a `Makefile` for the `make` tool, but most of " -"the just recipes are not available as targets in the `Makefile`." +msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`." msgstr "" #: ../../../docs/faq.md:93 @@ -338,27 +213,19 @@ msgid "Why use this playbook and not install Synapse and other things manually?" msgstr "" #: ../../../docs/faq.md:95 -msgid "" -"There are various guides telling you how easy it is to install " -"[Synapse](https://github.com/element-hq/synapse)." +msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)." msgstr "" #: ../../../docs/faq.md:97 -msgid "" -"Reading the documentation of this Ansible playbook, you may also be " -"thinking:" +msgid "Reading the documentation of this Ansible playbook, you may also be thinking:" msgstr "" #: ../../../docs/faq.md:99 -msgid "" -"I don't know what [Ansible](https://www.ansible.com/) is. I don't know " -"what [Docker](https://www.docker.com/) is. This looks more complicated." +msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated." msgstr "" #: ../../../docs/faq.md:101 -msgid "" -".. so you may be leaning toward [installing Synapse " -"manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." +msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)." msgstr "" #: ../../../docs/faq.md:103 @@ -366,61 +233,35 @@ msgid "The problem with a manual installation is:" msgstr "" #: ../../../docs/faq.md:105 -msgid "" -"Synapse is written in Python. If not packaged for your distribution, " -"you'd need to install various Python modules, etc., and keep them " -"updated." +msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated." msgstr "" #: ../../../docs/faq.md:106 -msgid "" -"Synapse requires a [Postgres](https://www.postgresql.org/) database (it " -"can run on SQLite, but that's very much discouraged). So you'd need to " -"install Postgres as well." +msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well." msgstr "" #: ../../../docs/faq.md:107 -msgid "" -"you may also need a reverse-proxy server in front of it (nginx, Apache), " -"so you'd need to be familiar with that" +msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that" msgstr "" #: ../../../docs/faq.md:108 -msgid "" -"SSL is required, so you'd need to obtain Let's Encrypt (or other free or " -"non-free) certificates for one or more domain names. You'd need to be " -"familiar with [certbot](https://certbot.eff.org/) (when using Let's " -"Encrypt) or similar software." +msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software." msgstr "" #: ../../../docs/faq.md:109 -msgid "" -"for each additional component you'd like to add (client like " -"[Element](https://element.io), bridge to some other chat network, " -"integration manager (stickers, other services, Identity Manager, etc.), " -"you'll need to spend extra time installing and wiring it with the rest of" -" the system in a way that works." +msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works." msgstr "" #: ../../../docs/faq.md:110 -msgid "" -"you'll likely get slower updates for all of these components, depending " -"on your distro packaging or your own time and ability" +msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability" msgstr "" #: ../../../docs/faq.md:112 -msgid "" -"The playbook, on the other hand, installs a bunch of components for you " -"by default, obtains SSL certificates for you, etc. If you'd like, you can" -" enable various bridges and other services with very little effort. All " -"the components are wired to work together." +msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together." msgstr "" #: ../../../docs/faq.md:114 -msgid "" -"All services run in Docker containers (most being officially provided by " -"each component's developers), so we're not at the mercy of distro " -"packaging." +msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging." msgstr "" #: ../../../docs/faq.md:116 @@ -432,15 +273,11 @@ msgid "Reasons are similar to the reasons for not installing manually." msgstr "" #: ../../../docs/faq.md:120 -msgid "" -"Besides Synapse, you'd need other things - a Postgres database, likely " -"the [Element](https://element.io) client, etc., etc." +msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc." msgstr "" #: ../../../docs/faq.md:122 -msgid "" -"Using the playbook, you get all these components in a way that works well" -" together out of the box." +msgid "Using the playbook, you get all these components in a way that works well together out of the box." msgstr "" #: ../../../docs/faq.md:124 @@ -452,29 +289,19 @@ msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy." msgstr "" #: ../../../docs/faq.md:128 -msgid "" -"What's different about this Ansible playbook compared to [EMnify/matrix-" -"synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-" -"deploy)?" +msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?" msgstr "" #: ../../../docs/faq.md:130 -msgid "" -"This is similar to the [EMnify/matrix-synapse-auto-" -"deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible " -"deployment, but:" +msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:" msgstr "" #: ../../../docs/faq.md:132 -msgid "" -"this one is a complete Ansible playbook (instead of just a role), so it's" -" **easier to run** - especially for folks not familiar with Ansible" +msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible" msgstr "" #: ../../../docs/faq.md:134 -msgid "" -"this one installs and hooks together **a lot more Matrix-related " -"services** for you (see above)" +msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)" msgstr "" #: ../../../docs/faq.md:136 @@ -482,56 +309,35 @@ msgid "this one **can be executed more than once** without causing trouble" msgstr "" #: ../../../docs/faq.md:138 -msgid "" -"works on various distros: **CentOS** (7.0+), Debian-based distributions " -"(**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" +msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**" msgstr "" #: ../../../docs/faq.md:140 -msgid "" -"this one installs everything in a single directory (`/matrix` by default)" -" and **doesn't \"contaminate\" your server** with files all over the " -"place" +msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place" msgstr "" #: ../../../docs/faq.md:142 -msgid "" -"this one **doesn't necessarily take over** ports 80 and 443. By default, " -"it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but " -"you can also [use your own webserver](configuring-playbook-own-" -"webserver.md)" +msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)" msgstr "" #: ../../../docs/faq.md:144 -msgid "" -"this one **runs everything in Docker containers**, so it's likely more " -"predictable and less fragile (see [Docker images used by this playbook" -"](container-images.md))" +msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))" msgstr "" #: ../../../docs/faq.md:146 -msgid "" -"this one retrieves and automatically renews free [Let's " -"Encrypt](https://letsencrypt.org/) **SSL certificates** for you" +msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you" msgstr "" #: ../../../docs/faq.md:148 -msgid "" -"this one optionally can store the `media_store` content repository files " -"on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files" -" on the server's filesystem)" +msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)" msgstr "" #: ../../../docs/faq.md:150 -msgid "" -"this one optionally **allows you to use an external PostgreSQL server** " -"for Synapse's database (but defaults to running one in a container)" +msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)" msgstr "" #: ../../../docs/faq.md:152 -msgid "" -"helps you **import data from a previous installation** (so you can " -"migrate your manual virtualenv/Docker setup to a more managed one)" +msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)" msgstr "" #: ../../../docs/faq.md:154 @@ -543,9 +349,7 @@ msgid "Server-related" msgstr "" #: ../../../docs/faq.md:158 -msgid "" -"What kind of server do I need to install Matrix using this Ansible " -"playbook?" +msgid "What kind of server do I need to install Matrix using this Ansible playbook?" msgstr "" #: ../../../docs/faq.md:160 @@ -557,30 +361,19 @@ msgid "Why not run Matrix on Kubernetes?" msgstr "" #: ../../../docs/faq.md:164 -msgid "" -"There's no reason not to run Matrix on " -"[Kubernetes](https://kubernetes.io/)." +msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)." msgstr "" #: ../../../docs/faq.md:166 -msgid "" -"However, that's overly complicated for thousands of us who just want to " -"run a single small (and sometimes not so small) Matrix server, either " -"using \"cloud\" servers or even a [Raspberry " -"Pi](https://www.raspberrypi.org/) at home." +msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home." msgstr "" #: ../../../docs/faq.md:168 -msgid "" -"For us, a Kubernetes-based setup which requires a cluster of multiple " -"computers and is more technically-involved is a no-go." +msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go." msgstr "" #: ../../../docs/faq.md:170 -msgid "" -"There are others working on automating a Matrix-on-Kubernetes setup, such" -" as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21" -"/matrix-chart." +msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart." msgstr "" #: ../../../docs/faq.md:172 @@ -588,16 +381,11 @@ msgid "Why don't you use Podman instead of Docker?" msgstr "" #: ../../../docs/faq.md:174 -msgid "" -"We like the philosophy of a daemonless container runtime, but " -"[Podman](https://podman.io) is just not ready for our use case yet." +msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet." msgstr "" #: ../../../docs/faq.md:176 -msgid "" -"Learn more about our past experiences/attempts to give Podman a chance, " -"by reading [this issue](https://github.com/spantaleev/matrix-docker-" -"ansible-deploy/issues/520)." +msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)." msgstr "" #: ../../../docs/faq.md:178 @@ -609,21 +397,15 @@ msgid "Why use Docker?" msgstr "" #: ../../../docs/faq.md:182 -msgid "" -"[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the " -"other one being [systemd](https://systemd.io/))." +msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))." msgstr "" #: ../../../docs/faq.md:184 -msgid "" -"It lets us run services in an isolated manner and independently of the " -"(usually old) packages available for distributions." +msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions." msgstr "" #: ../../../docs/faq.md:186 -msgid "" -"It also lets us have a unified setup which runs the same across various " -"supported distros (see them on [Prerequisites](prerequisites.md))." +msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))." msgstr "" #: ../../../docs/faq.md:188 @@ -631,23 +413,15 @@ msgid "Is Docker a hard requirement?" msgstr "" #: ../../../docs/faq.md:190 -msgid "" -"Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-" -"podman-instead-of-docker) for why we're not using another container " -"runtime." +msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime." msgstr "" #: ../../../docs/faq.md:192 -msgid "" -"All of our services run in containers. It's how we achieve predictability" -" and also how we support tens of different services across lots of " -"distros." +msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros." msgstr "" #: ../../../docs/faq.md:194 -msgid "" -"The only thing we need on the distro is systemd and Python (we install " -"Docker ourselves, unless you ask us not to)." +msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)." msgstr "" #: ../../../docs/faq.md:196 @@ -655,19 +429,11 @@ msgid "Why don't you use docker-compose?" msgstr "" #: ../../../docs/faq.md:198 -msgid "" -"Instead of using [docker-compose](https://docs.docker.com/compose/), we " -"prefer installing systemd services and scheduling those independently." +msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently." msgstr "" #: ../../../docs/faq.md:200 -msgid "" -"There are people who have worked on turning this setup into a docker-" -"compose-based one. See these experiments " -"[here](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/64#issuecomment-603164625). There is also a demo project " -"([element-docker-demo](https://github.com/element-hq/element-docker-" -"demo)) by Element." +msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element." msgstr "" #: ../../../docs/faq.md:202 @@ -675,9 +441,7 @@ msgid "Can I run this on a distro without systemd?" msgstr "" #: ../../../docs/faq.md:204 -msgid "" -"No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the" -" other one being [Docker](https://www.docker.com/))." +msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))." msgstr "" #: ../../../docs/faq.md:206 @@ -685,21 +449,15 @@ msgid "Can I install this on a Raspberry Pi?" msgstr "" #: ../../../docs/faq.md:208 -msgid "" -"Yes, you can. See our [Alternative Architectures](alternative-" -"architectures.md) documentation page." +msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page." msgstr "" #: ../../../docs/faq.md:210 -msgid "" -"Whether a Raspberry Pi has enough power to give you a good experience is " -"another question. It depends on your use case." +msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case." msgstr "" #: ../../../docs/faq.md:212 -msgid "" -"Also see: [What kind of server specs do I need?](#what-kind-of-server-" -"specs-do-i-need)." +msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)." msgstr "" #: ../../../docs/faq.md:214 @@ -707,53 +465,27 @@ msgid "What kind of server specs do I need?" msgstr "" #: ../../../docs/faq.md:216 -msgid "" -"This largely depends on your use case. It's not so much the number of " -"users that you plan to host, but rather the number of large rooms they " -"will join." +msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join." msgstr "" #: ../../../docs/faq.md:218 -msgid "" -"Federated rooms with lots of history and containing hundreds of other " -"servers are very heavy CPU-wise and memory-wise." +msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise." msgstr "" #: ../../../docs/faq.md:220 -msgid "" -"You can probably use a 1 CPU + 1GB memory server to host hundreds of " -"local users just fine, but as soon as one of them joins a federated room " -"like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say " -"`##linux`), your server will get the need for a lot more power (at least " -"2GB RAM, etc)." +msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)." msgstr "" #: ../../../docs/faq.md:222 -msgid "" -"Running Matrix on a server with 1GB of memory is possible (especially if " -"you disable some not-so-important services). See [How do I optimize this " -"setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-" -"power-server)." +msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" #: ../../../docs/faq.md:224 -msgid "" -"**We recommend starting with a server having at least 2GB of memory** and" -" even then using it sparingly. If you know for sure you'll be joining " -"various large rooms, etc., then going for 4GB of memory or more is a good" -" idea." +msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea." msgstr "" #: ../../../docs/faq.md:226 -msgid "" -"Besides the regular Matrix stuff, we also support things like video-" -"conferencing using [Jitsi](configuring-playbook-jitsi.md) and other " -"additional services which (when installed) may use up a lot of memory. " -"Things do add up. Besides the Synapse Matrix server, Jitsi is especially " -"notorious for consuming a lot of resources. If you plan on running Jitsi," -" we recommend a server with at least 2GB of memory (preferrably more). " -"See our [Jitsi documentation page](configuring-playbook-jitsi.md) to " -"learn how to optimize its memory/CPU usage." +msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage." msgstr "" #: ../../../docs/faq.md:228 @@ -761,12 +493,7 @@ msgid "Can I run this in an LXC container?" msgstr "" #: ../../../docs/faq.md:230 -msgid "" -"If your distro runs within an [LXC " -"container](https://linuxcontainers.org/), you may hit [this " -"issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/703). It can be worked around, if absolutely necessary, but" -" we suggest that you avoid running from within an LXC container." +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" #: ../../../docs/faq.md:232 @@ -778,34 +505,19 @@ msgid "Why install my server at matrix.example.com and not at the base domain?" msgstr "" #: ../../../docs/faq.md:236 -msgid "" -"It's the same with email servers. Your email address is likely " -"`name@company.com`, not `name@mail.company.com`, even though it's " -"`mail.company.com` that is really handling your data for `@company.com` " -"email to work." +msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work." msgstr "" #: ../../../docs/faq.md:238 -msgid "" -"Using a separate domain name is easier to manage (although it's a little " -"hard to get right at first) and keeps your Matrix server isolated from " -"your website (if you have one), from your email server (if you have one)," -" etc. Therefore, this playbook sets up services on your Matrix server " -"(`matrix.example.com`) by default." +msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default." msgstr "" #: ../../../docs/faq.md:240 -msgid "" -"I don't control anything on the base domain and can't set up delegation " -"to matrix.example.com. What do I do?" +msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?" msgstr "" #: ../../../docs/faq.md:242 -msgid "" -"If you're not in control of your base domain (or the server handling it) " -"at all, you can take a look at [How do I install on matrix.example.com " -"without involving the base domain?](#how-do-i-install-on-" -"matrixexamplecom-without-involving-the-base-domain)" +msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:244 @@ -813,11 +525,7 @@ msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating msgstr "" #: ../../../docs/faq.md:246 -msgid "" -"If you really can't obtain an HTTPS certificate for your base domain, you" -" can take a look at [How do I install on matrix.example.com without " -"involving the base domain?](#how-do-i-install-on-matrixexamplecom-" -"without-involving-the-base-domain)" +msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:248 @@ -825,15 +533,11 @@ msgid "How do I install on matrix.example.com without involving the base domain? msgstr "" #: ../../../docs/faq.md:250 -msgid "" -"Add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/faq.md:271 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/faq.md:278 @@ -841,54 +545,31 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/faq.md:280 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/faq.md:282 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/faq.md:284 -msgid "" -"Without setting up [server delegation](howto-server-delegation.md) to " -"`matrix.example.com`, your user IDs will be like " -"`@alice:matrix.example.com`. This is equivalent to having an email " -"address like `bob@mail.company.com`, instead of just `bob@company.com`." +msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`." msgstr "" #: ../../../docs/faq.md:286 -msgid "" -"I don't use the base domain for anything. How am I supposed to set up " -"Server Delegation for Matrix services?" +msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?" msgstr "" #: ../../../docs/faq.md:288 -msgid "" -"If you don't use your base domain for anything, then it's hard for you to" -" \"serve files over HTTPS\" on it -- something we ask you to do for the " -"[.well-known](configuring-well-known.md) setup (needed for [Server " -"Delegation](howto-server-delegation.md))." +msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))." msgstr "" #: ../../../docs/faq.md:290 -msgid "" -"Luckily, the playbook can set up your Matrix server (at " -"`matrix.example.com`) to also handle traffic for the base domain " -"(`example.com`)." +msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)." msgstr "" #: ../../../docs/faq.md:292 -msgid "" -"See [Serving the base domain](configuring-playbook-base-domain-" -"serving.md)." +msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)." msgstr "" #: ../../../docs/faq.md:294 @@ -900,41 +581,27 @@ msgid "You can disable some not-so-important services to save on memory." msgstr "" #: ../../../docs/faq.md:318 -msgid "" -"You can also consider implementing a restriction on room complexity, in " -"order to prevent users from joining very heavy rooms:" +msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:" msgstr "" #: ../../../docs/faq.md:328 -msgid "" -"If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed" -" by default), there are additional optimizations listed on its " -"documentation page that you can perform." +msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform." msgstr "" #: ../../../docs/faq.md:330 -msgid "" -"I already have Docker on my server. Can you stop installing Docker via " -"the playbook?" +msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?" msgstr "" #: ../../../docs/faq.md:332 -msgid "" -"Yes, we can stop installing Docker ourselves. Just use this in your " -"`vars.yml` file:" +msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:" msgstr "" #: ../../../docs/faq.md:338 -msgid "" -"I run another webserver on the same server where I wish to install " -"Matrix. What now?" +msgid "I run another webserver on the same server where I wish to install Matrix. What now?" msgstr "" #: ../../../docs/faq.md:340 -msgid "" -"By default, we install a webserver for you " -"([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your " -"own webserver](configuring-playbook-own-webserver.md)." +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 @@ -942,30 +609,19 @@ 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:" +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)." +msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)." msgstr "" #: ../../../docs/faq.md:348 -msgid "" -"then, there are overrides in `group_vars/matrix_servers`, which aim to " -"adjust these \"standalone role defaults\" to something which better fits " -"the playbook in its entirety." +msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety." msgstr "" #: ../../../docs/faq.md:350 -msgid "" -"finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` " -"file, which is the ultimate override" +msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override" msgstr "" #: ../../../docs/faq.md:352 @@ -973,67 +629,39 @@ msgid "What configuration variables are available?" msgstr "" #: ../../../docs/faq.md:354 -msgid "" -"You can discover the variables you can override in each role " -"(`roles/*/*/defaults/main.yml`)." +msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)." msgstr "" #: ../../../docs/faq.md:356 -msgid "" -"As described in [How is the effective configuration determined?](#how-is-" -"the-effective-configuration-determined), these role-defaults may be " -"overriden by values defined in `group_vars/matrix_servers`." +msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`." msgstr "" #: ../../../docs/faq.md:358 -msgid "" -"Refer to both of these for inspiration. Still, as mentioned in " -"[Configuring the playbook](configuring-playbook.md), you're only ever " -"supposed to edit your own " -"`inventory/host_vars/matrix.example.com/vars.yml` file and nothing else " -"inside the playbook (unless you're meaning to contribute new features)." +msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)." msgstr "" #: ../../../docs/faq.md:360 ../../../docs/faq.md:372 -msgid "" -"**Note**: some of the roles (`roles/galaxy/*`) live in separate " -"repositories and are only installed after your run `just roles` (or `make" -" roles`) or `just update` (which automatically does `git pull` and `just " -"roles`)." +msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)." msgstr "" #: ../../../docs/faq.md:362 -msgid "" -"I'd like to adjust some configuration which doesn't have a corresponding " -"variable. How do I do it?" +msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?" msgstr "" #: ../../../docs/faq.md:364 -msgid "" -"The playbook doesn't aim to expose all configuration settings for all " -"services using variables. Doing so would amount to hundreds of variables " -"that we have to create and maintain." +msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain." msgstr "" #: ../../../docs/faq.md:366 -msgid "" -"Instead, we only try to make some important basics configurable using " -"dedicated variables you can see in each role. See [What configuration " -"variables are available?](#what-configuration-variables-are-available)." +msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)." msgstr "" #: ../../../docs/faq.md:368 -msgid "" -"Besides that, each role (component) aims to provide a " -"`matrix_SOME_COMPONENT_configuration_extension_yaml` (or " -"`matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can" -" be used to override the configuration." +msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration." msgstr "" #: ../../../docs/faq.md:370 -msgid "" -"Check each role's `roles/*/*/defaults/main.yml` for the corresponding " -"variable and an example for how use it." +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 @@ -1045,15 +673,11 @@ msgid "How do I run the installation?" msgstr "" #: ../../../docs/faq.md:378 -msgid "" -"See [Installing](installing.md) to learn how to use Ansible to install " -"Matrix services." +msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services." msgstr "" #: ../../../docs/faq.md:380 -msgid "" -"However, we recommend you to follow our installation guide, instead of " -"jumping straight to installing." +msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing." msgstr "" #: ../../../docs/faq.md:382 @@ -1061,24 +685,15 @@ msgid "There are two guides available:" msgstr "" #: ../../../docs/faq.md:384 -msgid "" -"⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended " -"for those who do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\"." +msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"." msgstr "" #: ../../../docs/faq.md:386 -msgid "" -"**Full installation guide (for advanced users)**: if you need to import " -"an existing Matrix server's data into the new server or want to learn " -"more while setting up the server, follow this guide by starting with the " -"**[Prerequisites](prerequisites.md)** documentation page." +msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page." msgstr "" #: ../../../docs/faq.md:388 -msgid "" -"I installed Synapse some other way. Can I migrate such a setup to the " -"playbook?" +msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?" msgstr "" #: ../../../docs/faq.md:390 @@ -1086,61 +701,31 @@ msgid "Yes, you can." msgstr "" #: ../../../docs/faq.md:392 -msgid "" -"You generally need to do a playbook installation. It's recommended to " -"follow the full installation guide (starting at the " -"[Prerequisites](prerequisites.md) page), not the [Quick start](quick-" -"start.md) guide. The full installation guide will tell you when it's time" -" to import your existing data into the newly-prepared server." +msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server." msgstr "" #: ../../../docs/faq.md:394 -msgid "" -"This Ansible playbook guides you into installing a server for " -"`example.com` (user IDs are like this: `@alice:example.com`), while the " -"server is at `matrix.example.com`. If your existing setup has a server " -"name (`server_name` configuration setting in Synapse's `homeserver.yaml` " -"file) other than the base `example.com`, you may need to tweak some " -"additional variables. This FAQ entry may be of use if you're dealing with" -" a more complicated setup - [How do I install on matrix.example.com " -"without involving the base domain?](#how-do-i-install-on-" -"matrixexamplecom-without-involving-the-base-domain)" +msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup - [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)" msgstr "" #: ../../../docs/faq.md:396 -msgid "" -"After configuring the playbook and installing and **before starting** " -"services (done with `ansible-playbook … --tags=start`) you'd import [your" -" SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-" -"postgres.md)) database and also [import your media store](importing-" -"synapse-media-store.md)." +msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)." msgstr "" #: ../../../docs/faq.md:398 -msgid "" -"I've downloaded Ansible and the playbook on the server. It can't connect " -"using SSH." +msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH." msgstr "" #: ../../../docs/faq.md:400 -msgid "" -"If you're using the playbook directly on the server, then Ansible doesn't" -" need to connect using SSH." +msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH." msgstr "" #: ../../../docs/faq.md:402 -msgid "" -"It can perform a local connection instead. Just set " -"`ansible_connection=local` at the end of the server line in " -"`inventory/hosts` and re-run the playbook." +msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook." msgstr "" #: ../../../docs/faq.md:404 -msgid "" -"If you're running Ansible from within a container (one of the " -"possibilities we list on our [dedicated Ansible documentation " -"page](ansible.md)), then using `ansible_connection=local` is not " -"possible." +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 @@ -1148,9 +733,7 @@ msgid "Troubleshooting" msgstr "" #: ../../../docs/faq.md:408 -msgid "" -"I get \"Error response from daemon: configured logging driver does not " -"support reading\" when I do `docker logs matrix-synapse`." +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 @@ -1162,49 +745,31 @@ msgid "How can I see the logs?" msgstr "" #: ../../../docs/faq.md:414 -msgid "" -"We utilize " -"[systemd/journald](https://www.freedesktop.org/software/systemd/man" -"/systemd-journald.service.html#Description) for logging." +msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging." msgstr "" #: ../../../docs/faq.md:416 -msgid "" -"To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You" -" may wish to see the [manual page for " -"journalctl](https://www.commandlinux.com/man-" -"page/man1/journalctl.1.html)." +msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)." msgstr "" #: ../../../docs/faq.md:418 -msgid "" -"Available service names can be seen by doing `ls " -"/etc/systemd/system/matrix*.service` on the server." +msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server." msgstr "" #: ../../../docs/faq.md:420 -msgid "" -"Some services also log to files in `/matrix/*/data/..`, but we're slowly " -"moving away from that." +msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that." msgstr "" #: ../../../docs/faq.md:422 -msgid "" -"We also disable Docker logging, so you can't use `docker logs matrix-*` " -"either. We do this to prevent useless double (or even triple) logging and" -" to avoid having to rotate log files." +msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files." msgstr "" #: ../../../docs/faq.md:424 -msgid "" -"We just simply delegate logging to journald and it takes care of " -"persistence and expiring old data." +msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data." msgstr "" #: ../../../docs/faq.md:426 -msgid "" -"Also see: [How long do systemd/journald logs persist for?](#how-long-do-" -"systemdjournald-logs-persist-for)" +msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)" msgstr "" #: ../../../docs/faq.md:428 @@ -1212,21 +777,15 @@ msgid "How long do systemd/journald logs persist for?" msgstr "" #: ../../../docs/faq.md:430 -msgid "" -"On some distros, the journald logs are just in-memory and not persisted " -"to disk." +msgid "On some distros, the journald logs are just in-memory and not persisted to disk." msgstr "" #: ../../../docs/faq.md:432 -msgid "" -"Consult (and feel free to adjust) your distro's journald logging " -"configuration in `/etc/systemd/journald.conf`." +msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`." msgstr "" #: ../../../docs/faq.md:434 -msgid "" -"To enable persistence and put some limits on how large the journal log " -"files can become, adjust your configuration like this:" +msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:" msgstr "" #: ../../../docs/faq.md:445 @@ -1242,9 +801,7 @@ msgid "Yes. We don't update anything for you automatically." msgstr "" #: ../../../docs/faq.md:451 -msgid "" -"See our [documentation page about upgrading services](maintenance-" -"upgrading-services.md)." +msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)." msgstr "" #: ../../../docs/faq.md:453 @@ -1252,18 +809,11 @@ msgid "How do I move my existing installation to another (VM) server?" msgstr "" #: ../../../docs/faq.md:455 -msgid "" -"If you have an existing installation done using this Ansible playbook, " -"you can easily migrate that to another server using [our dedicated server" -" migration guide](maintenance-migrating.md)." +msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)." msgstr "" #: ../../../docs/faq.md:457 -msgid "" -"If your previous installation is done in some other way (not using this " -"Ansible playbook), see [I installed Synapse some other way. Can I migrate" -" such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i" -"-migrate-such-a-setup-to-the-playbook)." +msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)." msgstr "" #: ../../../docs/faq.md:459 @@ -1275,17 +825,11 @@ msgid "We haven't documented this properly yet, but the general advice is to:" msgstr "" #: ../../../docs/faq.md:463 -msgid "" -"back up Postgres by making a database dump. See [Backing up PostgreSQL" -"](maintenance-postgres.md#backing-up-postgresql)" +msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)" msgstr "" #: ../../../docs/faq.md:465 -msgid "" -"back up all `/matrix` files, except for `/matrix/postgres/data` (you " -"already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` " -"(this directory may exist and contain your old data if you've [performed " -"a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." +msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))." msgstr "" #: ../../../docs/faq.md:467 @@ -1297,36 +841,23 @@ 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)" +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." +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?" +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." +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`" +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 @@ -1334,21 +865,13 @@ 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." +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`)." +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." +msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po index c81d847ca..4a6bfe641 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po @@ -25,22 +25,15 @@ msgid "Getting the playbook" msgstr "" #: ../../../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)" +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:5 -msgid "" -"This Ansible playbook is meant to be executed on your own computer (not " -"the Matrix server)." +msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)." msgstr "" #: ../../../docs/getting-the-playbook.md:7 -msgid "" -"In special cases (if your computer cannot run Ansible, etc.) you may put " -"the playbook on the server as well." +msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well." msgstr "" #: ../../../docs/getting-the-playbook.md:9 @@ -48,15 +41,11 @@ msgid "You can retrieve the playbook's source code by:" msgstr "" #: ../../../docs/getting-the-playbook.md:11 -msgid "" -"[Using git to get the playbook](#using-git-to-get-the-playbook) " -"(recommended)" +msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)" msgstr "" #: ../../../docs/getting-the-playbook.md:13 -msgid "" -"[Downloading the playbook as a ZIP archive](#downloading-the-playbook-" -"as-a-zip-archive) (not recommended)" +msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)" msgstr "" #: ../../../docs/getting-the-playbook.md:15 @@ -64,24 +53,15 @@ msgid "Using git to get the playbook" msgstr "" #: ../../../docs/getting-the-playbook.md:17 -msgid "" -"We recommend using the [git](https://git-scm.com/) tool to get the " -"playbook's source code, because it lets you easily keep up to date in the" -" future when [Maintaining services](maintenance-upgrading-services.md)." +msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)." msgstr "" #: ../../../docs/getting-the-playbook.md:19 -msgid "" -"Once you've installed git on your computer, you can go to any directory " -"of your choosing and run the following command to retrieve the playbook's" -" source code:" +msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:" msgstr "" #: ../../../docs/getting-the-playbook.md:25 -msgid "" -"This will create a new `matrix-docker-ansible-deploy` directory. You're " -"supposed to execute all other installation commands inside that " -"directory." +msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory." msgstr "" #: ../../../docs/getting-the-playbook.md:27 @@ -89,30 +69,17 @@ msgid "Downloading the playbook as a ZIP archive" msgstr "" #: ../../../docs/getting-the-playbook.md:29 -msgid "" -"Alternatively, you can download the playbook as a ZIP archive. This is " -"not recommended, as it's not easy to keep up to date with future updates." -" We suggest you [use git](#using-git-to-get-the-playbook) instead." +msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead." msgstr "" #: ../../../docs/getting-the-playbook.md:31 -msgid "" -"The latest version is always at the following URL: " -"https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/archive/master.zip" +msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip" msgstr "" #: ../../../docs/getting-the-playbook.md:33 -msgid "" -"You can extract this archive anywhere. You'll get a directory called " -"`matrix-docker-ansible-deploy-master`. You're supposed to execute all " -"other installation commands inside that directory." +msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory." msgstr "" #: ../../../docs/getting-the-playbook.md:37 -msgid "" -"[▶️](configuring-playbook.md) No matter which method you've used to " -"download the playbook, you can proceed by [Configuring the playbook" -"](configuring-playbook.md)." +msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po index 6c64fd20f..8304c4748 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po @@ -25,11 +25,7 @@ msgid "Server Delegation" msgstr "" #: ../../../docs/howto-server-delegation.md:3 -msgid "" -"By default, this playbook sets up services on your Matrix server " -"(`matrix.example.com`). To have this server officially be responsible for" -" Matrix services for the base domain (`example.com`), you need to set up " -"server delegation / redirection." +msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection." msgstr "" #: ../../../docs/howto-server-delegation.md:5 @@ -37,42 +33,23 @@ msgid "Server delegation can be configured in either of these ways:" msgstr "" #: ../../../docs/howto-server-delegation.md:7 -msgid "" -"[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a" -"-well-known-file) on the base domain (`example.com`)" +msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)" msgstr "" #: ../../../docs/howto-server-delegation.md:8 -msgid "" -"[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a" -"-dns-srv-record-advanced)" +msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)" msgstr "" #: ../../../docs/howto-server-delegation.md:10 -msgid "" -"Both methods have their place and will continue to do so. You only need " -"to use just one of these delegation methods." +msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods." msgstr "" #: ../../../docs/howto-server-delegation.md:12 -msgid "" -"For simplicity reasons, this playbook recommends you to set up server " -"delegation via a `/.well-known/matrix/server` file. However, that method " -"may have some downsides that are not to your liking. Hence this guide " -"about alternative ways to set up Server Delegation." +msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation." msgstr "" #: ../../../docs/howto-server-delegation.md:14 -msgid "" -"**Note**: as an alternative, it is possible to install the server such " -"that it uses only the `matrix.example.com` domain (instead of identifying" -" as the shorter base domain - `example.com`). This should be helpful if " -"you are not in control of anything on the base domain (`example.com`). In" -" this case, you would not need to configure server delegation, but you " -"would need to add other configuration. For more information, see [How do " -"I install on matrix.example.com without involving the base " -"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" -"the-base-domain) on our FAQ." +msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" #: ../../../docs/howto-server-delegation.md:16 @@ -80,20 +57,11 @@ msgid "Server Delegation via a well-known file" msgstr "" #: ../../../docs/howto-server-delegation.md:18 -msgid "" -"This playbook recommends you to set up server delegation by means of a " -"`/.well-known/matrix/server` file served from the base domain " -"(`example.com`), as this is the most straightforward way to set up the " -"delegation." +msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation." msgstr "" #: ../../../docs/howto-server-delegation.md:20 -msgid "" -"To configure server delegation with the well-known file, check this " -"section on [Configuring Service Discovery via .well-known](configuring-" -"well-known.md): [Installing well-known files on the base domain's server" -"](configuring-well-known.md#installing-well-known-files-on-the-base-" -"domain-s-server)" +msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)" msgstr "" #: ../../../docs/howto-server-delegation.md:22 @@ -101,46 +69,27 @@ msgid "Downsides of well-known-based Server Delegation" msgstr "" #: ../../../docs/howto-server-delegation.md:24 -msgid "" -"Server Delegation by means of a `/.well-known/matrix/server` file is the " -"most straightforward, but suffers from the following downsides:" +msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:" msgstr "" #: ../../../docs/howto-server-delegation.md:26 -msgid "" -"you need to have a working HTTPS server for the base domain " -"(`example.com`). If you don't have any server for the base domain at all," -" you can easily solve it by making the playbook [serve the base domain " -"from the Matrix server](configuring-playbook-base-domain-serving.md)." +msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)." msgstr "" #: ../../../docs/howto-server-delegation.md:28 -msgid "" -"any downtime on the base domain (`example.com`) or network trouble " -"between the Matrix subdomain (`matrix.example.com`) and the base " -"`example.com` may cause Matrix Federation outages. As the [Server-Server " -"spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" -"discovery):" +msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):" msgstr "" #: ../../../docs/howto-server-delegation.md:30 -msgid "" -"Errors are recommended to be cached for up to an hour, and servers are " -"encouraged to exponentially back off for repeated failures." +msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures." msgstr "" #: ../../../docs/howto-server-delegation.md:32 -msgid "" -"**For most people, this is a reasonable tradeoff** given that it's easy " -"and straightforward to set up. We recommend you stay on this path." +msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path." msgstr "" #: ../../../docs/howto-server-delegation.md:34 -msgid "" -"Otherwise, you can decide to go against the default for this playbook, " -"and instead set up [Server Delegation via a DNS SRV record (advanced" -")](#server-delegation-via-a-dns-srv-record-advanced) (much more " -"complicated)." +msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)." msgstr "" #: ../../../docs/howto-server-delegation.md:36 @@ -148,26 +97,15 @@ msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" #: ../../../docs/howto-server-delegation.md:38 -msgid "" -"**Note**: doing Server Delegation via a DNS SRV record is a more " -"**advanced** way to do it and is not the default for this playbook. This " -"is usually **much more complicated** to set up, so **we don't recommend " -"it**. If you're not an experienced sysadmin, you'd better stay away from " -"this." +msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this." msgstr "" #: ../../../docs/howto-server-delegation.md:40 -msgid "" -"As per the [Server-Server " -"spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-" -"discovery), it's possible to do Server Delegation using only a SRV record" -" (without a `/.well-known/matrix/server` file)." +msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)." msgstr "" #: ../../../docs/howto-server-delegation.md:42 -msgid "" -"This prevents you from suffering the [Downsides of well-known-based " -"Server Delegation](#downsides-of-well-known-based-server-delegation)." +msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)." msgstr "" #: ../../../docs/howto-server-delegation.md:44 @@ -175,33 +113,19 @@ msgid "To use DNS SRV record validation, you need to:" msgstr "" #: ../../../docs/howto-server-delegation.md:46 -msgid "" -"ensure that `/.well-known/matrix/server` is **not served** from the base " -"domain, as that would interfere with DNS SRV record Server Delegation. To" -" make the playbook **not** generate and serve the file, use the following" -" configuration: `matrix_static_files_file_matrix_server_enabled: false`." +msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`." msgstr "" #: ../../../docs/howto-server-delegation.md:48 -msgid "" -"ensure that you have a `_matrix._tcp` DNS SRV record for your base domain" -" (`example.com`) with a value of `10 0 8448 matrix.example.com`" +msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`" msgstr "" #: ../../../docs/howto-server-delegation.md:50 -msgid "" -"ensure that you are serving the Matrix Federation API (tcp/8448) with a " -"certificate for `example.com` (not `matrix.example.com`!). Getting this " -"certificate to the `matrix.example.com` server may be complicated. The " -"playbook's automatic SSL obtaining/renewal flow will likely not work and " -"you'll need to copy certificates around manually. See below." +msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below." msgstr "" #: ../../../docs/howto-server-delegation.md:52 -msgid "" -"For more details on how to configure the playbook to work with SRV " -"delegation, take a look at this documentation: [Server Delegation via a " -"DNS SRV record (advanced)](howto-srv-server-delegation.md)" +msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)" msgstr "" #: ../../../docs/howto-server-delegation.md:54 @@ -209,27 +133,15 @@ msgid "Obtaining certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:56 -msgid "" -"How you can obtain a valid certificate for `example.com` on the " -"`matrix.example.com` server is up to you." +msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you." msgstr "" #: ../../../docs/howto-server-delegation.md:58 -msgid "" -"If `example.com` and `matrix.example.com` are hosted on the same machine," -" you can let the playbook obtain the certificate for you, by following " -"our [Obtaining SSL certificates for additional domains](configuring-" -"playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-" -"domains) guide." +msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide." msgstr "" #: ../../../docs/howto-server-delegation.md:60 -msgid "" -"If `example.com` and `matrix.example.com` are not hosted on the same " -"machine, you can copy over the certificate files manually. Don't forget " -"that they may get renewed once in a while, so you may also have to " -"transfer them periodically. How often you do that is up to you, as long " -"as the certificate files don't expire." +msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire." msgstr "" #: ../../../docs/howto-server-delegation.md:62 @@ -237,10 +149,7 @@ msgid "Serving the Federation API with your certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:64 -msgid "" -"Regardless of which method for obtaining certificates you've used, once " -"you've managed to get certificates for your base domain onto the " -"`matrix.example.com` machine you can put them to use." +msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use." msgstr "" #: ../../../docs/howto-server-delegation.md:66 @@ -248,9 +157,7 @@ msgid "Based on your setup, you have different ways to go about it:" msgstr "" #: ../../../docs/howto-server-delegation.md:68 -msgid "" -"Serving the Federation API with your certificates and Synapse handling " -"Federation" +msgid "Serving the Federation API with your certificates and Synapse handling Federation" msgstr "" #: ../../../docs/howto-server-delegation.md:70 @@ -258,22 +165,15 @@ msgid "You can let Synapse handle Federation by itself." msgstr "" #: ../../../docs/howto-server-delegation.md:72 -msgid "" -"To do that, make sure the certificate files are mounted into the Synapse " -"container:" +msgid "To do that, make sure the certificate files are mounted into the Synapse container:" msgstr "" #: ../../../docs/howto-server-delegation.md:79 -msgid "" -"You can then tell Synapse to serve Federation traffic over TLS on " -"`tcp/8448`:" +msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:" msgstr "" #: ../../../docs/howto-server-delegation.md:87 -msgid "" -"Make sure to reload Synapse once in a while (`systemctl reload matrix-" -"synapse`), so that newer certificates can kick in. Reloading doesn't " -"cause any downtime." +msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime." msgstr "" #: ../../../docs/howto-server-delegation.md:89 @@ -281,20 +181,9 @@ msgid "Serving the Federation API with your certificates and another webserver" msgstr "" #: ../../../docs/howto-server-delegation.md:91 -msgid "" -"**Alternatively**, if you are using another webserver, you can set up " -"reverse-proxying for the `tcp/8448` port by yourself. Make sure to use " -"the proper certificates for `example.com` (not for `matrix.example.com`) " -"when serving the `tcp/8448` port." +msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port." msgstr "" #: ../../../docs/howto-server-delegation.md:93 -msgid "" -"As recommended in our [Fronting the integrated reverse-proxy webserver " -"with another reverse-proxy](./configuring-playbook-own-webserver.md" -"#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-" -"proxy) documentation section, we recommend you to expose the Matrix " -"Federation entrypoint from traffic at a local port (e.g. " -"`127.0.0.1:8449`), so your reverese-proxy should send traffic there." +msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po index 51f8e250b..a97672f4a 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 @@ -25,21 +25,11 @@ msgid "Server Delegation via a DNS SRV record (advanced)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:3 -msgid "" -"**Reminder** : unless you are affected by the [Downsides of well-known-" -"based Server Delegation](howto-server-delegation.md#downsides-of-well-" -"known-based-server-delegation), we suggest you **stay on the " -"simple/default path**: [Server Delegation](howto-server-delegation.md) by" -" [configuring well-known files](configuring-well-known.md) at the base " -"domain." +msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:5 -msgid "" -"This guide is about configuring Server Delegation using DNS SRV records " -"(for the [Traefik](https://doc.traefik.io/traefik/) webserver). This " -"method has special requirements when it comes to SSL certificates, so " -"various changes are required." +msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:7 @@ -47,30 +37,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:9 -msgid "" -"SRV delegation while still using the playbook provided Traefik to get / " -"renew the certificate requires a wildcard certificate." +msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:11 -msgid "" -"To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one" -" needs to use a [DNS-01 challenge](https://letsencrypt.org/docs" -"/challenge-types/#dns-01-challenge) method instead of the default " -"[HTTP-01](https://letsencrypt.org/docs/challenge-" -"types/#http-01-challenge)." +msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:13 -msgid "" -"This means that this is **limited to the list of DNS providers supported " -"by Traefik**, unless you bring in your own certificate." +msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:15 -msgid "" -"The up-to-date list can be accessed on [traefik's " -"documentation](https://doc.traefik.io/traefik/https/acme/#providers)" +msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:17 @@ -78,31 +57,19 @@ msgid "The changes" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:19 -msgid "" -"**Note**: the changes below instruct you how to do this for a basic " -"Synapse installation. You will need to adapt the variable name and the " -"content of the labels:" +msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:21 -msgid "" -"if you're using another homeserver implementation (e.g. [Conduit" -"](./configuring-playbook-conduit.md) or [Dendrite](./configuring-" -"playbook-dendrite.md))" +msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:22 -msgid "" -"if you're using [Synapse with workers enabled](./configuring-playbook-" -"synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled:" -" true`). In that case, it's actually the `matrix-synapse-reverse-proxy-" -"companion` service which has Traefik labels attached" +msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:24 -msgid "" -"Also, all instructions below are from an older version of the playbook " -"and may not work anymore." +msgid "Also, all instructions below are from an older version of the playbook and may not work anymore." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:26 @@ -110,12 +77,7 @@ msgid "Federation Endpoint" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:33 -msgid "" -"This is because with SRV federation, some servers / tools (one of which " -"being the federation tester) try to access the federation API using the " -"resolved IP address instead of the domain name (or they are not using " -"SNI). This change will make Traefik route all traffic for which the path " -"match this rule go to the federation endpoint." +msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:35 @@ -123,18 +85,11 @@ msgid "Tell Traefik which certificate to serve for the federation endpoint" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:37 -msgid "" -"Now that the federation endpoint is not bound to a domain anymore we need" -" to explicitely tell Traefik to use a wildcard certificate in addition to" -" one containing the base name." +msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:39 -msgid "" -"This is because the Matrix specification expects the federation endpoint " -"to be served using a certificate compatible with the base domain, " -"however, the other resources on the endpoint still need a valid " -"certificate to work." +msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:48 @@ -142,10 +97,7 @@ msgid "Configure the DNS-01 challenge for let's encrypt" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:50 -msgid "" -"Since we're now requesting a wildcard certificate, we need to change the " -"ACME challenge method. To request a wildcard certificate from Let's " -"Encrypt we are required to use the DNS-01 challenge." +msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:52 @@ -157,11 +109,7 @@ msgid "Add a new certificate resolver that works with DNS-01" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:54 -msgid "" -"Configure the resolver to allow access to the DNS zone to configure the " -"records to answer the challenge (refer to [Traefik's " -"documentation](https://doc.traefik.io/traefik/https/acme/#providers) to " -"know which environment variables to set)" +msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:55 @@ -169,9 +117,7 @@ msgid "Tell the playbook to use the new resolver as default" msgstr "" #: ../../../docs/howto-srv-server-delegation.md:57 -msgid "" -"We cannot just disable the default resolver as that would disable SSL in " -"quite a few places in the playbook." +msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:86 @@ -183,14 +129,7 @@ msgid "The last step is to alter the generated Coturn configuration." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:90 -msgid "" -"By default, Coturn is configured to wait on the certificate for the " -"`matrix.` subdomain using an [instantiated systemd " -"service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates)" -" using the domain name as the parameter for this service. However, we " -"need to serve the wildcard certificate, which is incompatible with " -"systemd, it will try to expand the `*`, which will break and prevent " -"Coturn from starting." +msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:92 @@ -198,21 +137,13 @@ msgid "We also need to indicate to Coturn where the wildcard certificate is." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:94 -msgid "" -"**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still " -"fail to start because Traefik is still in the process of obtaining the " -"certificates. If you still get an error, make sure Traefik obtained the " -"certificates and restart the Coturn service (`just start-group coturn`)." +msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:96 -msgid "" -"This should not happen again afterwards as Traefik will renew " -"certificates well before their expiry date, and the Coturn service is " -"setup to restart periodically." +msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically." msgstr "" #: ../../../docs/howto-srv-server-delegation.md:122 msgid "Full example of a working configuration" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po index 2c9f142b8..3fb66cefc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po @@ -21,17 +21,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-postgres.md:1 -msgid "" -"Importing an existing Postgres database from another installation " -"(optional)" +msgid "Importing an existing Postgres database from another installation (optional)" msgstr "" #: ../../../docs/importing-postgres.md:3 -msgid "" -"Run this if you'd like to import your database from a previous " -"installation. (don't forget to import your Synapse `media_store` files as" -" well - see [the importing-synape-media-store guide](importing-synapse-" -"media-store.md))." +msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))." msgstr "" #: ../../../docs/importing-postgres.md:6 @@ -39,34 +33,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/importing-postgres.md:8 -msgid "" -"For this to work, **the database name in Postgres must match** what this " -"playbook uses. This playbook uses a Postgres database name of `synapse` " -"by default (controlled by the `matrix_synapse_database_database` " -"variable). If your database name differs, be sure to change " -"`matrix_synapse_database_database` to your desired name and to re-run the" -" playbook before proceeding." +msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding." msgstr "" #: ../../../docs/importing-postgres.md:10 -msgid "" -"The playbook supports importing Postgres dump files in **text** (e.g. " -"`pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > " -"dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) " -"is also supported." +msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported." msgstr "" #: ../../../docs/importing-postgres.md:12 -msgid "" -"The migration might be a good moment, to \"reset\" a not properly working" -" bridge. Be aware, that it might affect all users (new link to bridge, " -"new rooms, …)" +msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)" msgstr "" #: ../../../docs/importing-postgres.md:14 -msgid "" -"Before doing the actual import, **you need to upload your Postgres dump " -"file to the server** (any path is okay)." +msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)." msgstr "" #: ../../../docs/importing-postgres.md:16 @@ -74,9 +53,7 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-postgres.md:18 -msgid "" -"To import, run this command (make sure to replace " -"`SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" +msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):" msgstr "" #: ../../../docs/importing-postgres.md:26 @@ -84,28 +61,15 @@ 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!)" +msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)" msgstr "" #: ../../../docs/importing-postgres.md:29 -msgid "" -"`postgres_default_import_database` defaults to `matrix`, which is useful " -"for importing multiple databases (for dumps made with `pg_dumpall`). If " -"you're importing a single database (e.g. `synapse`), consider changing " -"`postgres_default_import_database` accordingly" +msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly" msgstr "" #: ../../../docs/importing-postgres.md:30 -msgid "" -"after importing a large database, it's a good idea to run [an `ANALYZE` " -"operation](https://www.postgresql.org/docs/current/sql-analyze.html) to " -"make Postgres rebuild its database statistics and optimize its query " -"planner. You can easily do this via the playbook by running `just run-" -"tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see " -"[Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for " -"more details)." +msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)." msgstr "" #: ../../../docs/importing-postgres.md:32 @@ -117,9 +81,7 @@ msgid "Table Ownership" msgstr "" #: ../../../docs/importing-postgres.md:36 -msgid "" -"A table ownership issue can occur if you are importing from a Synapse " -"installation which was both:" +msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:" msgstr "" #: ../../../docs/importing-postgres.md:38 @@ -135,38 +97,23 @@ msgid "In this case you may run into the following error during the import task: msgstr "" #: ../../../docs/importing-postgres.md:47 -msgid "" -"where `synapse_user` is the database username from the previous Synapse " -"installation." +msgid "where `synapse_user` is the database username from the previous Synapse installation." msgstr "" #: ../../../docs/importing-postgres.md:49 -msgid "" -"This can be verified by examining the dump for ALTER TABLE statements " -"which set OWNER TO that username:" +msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:" msgstr "" #: ../../../docs/importing-postgres.md:61 -msgid "" -"It can be worked around by changing the username to `synapse`, for " -"example by using `sed`:" +msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:" msgstr "" #: ../../../docs/importing-postgres.md:67 -msgid "" -"This uses sed to perform an 'in-place' (`-i`) replacement globally " -"(`/g`), searching for `synapse_user` and replacing with `synapse` " -"(`s/synapse_user/synapse`). If your database username was different, " -"change `synapse_user` to that username instead. Expand search/replace " -"statement as shown in example above, in case of old user name like " -"`matrix` - replacing `matrix` only would… well - you can imagine." +msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine." msgstr "" #: ../../../docs/importing-postgres.md:69 -msgid "" -"Note that if the previous import failed with an error it may have made " -"changes which are incompatible with re-running the import task right " -"away; if you do so it may fail with an error such as:" +msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:" msgstr "" #: ../../../docs/importing-postgres.md:75 @@ -174,33 +121,23 @@ msgid "Repeat import" msgstr "" #: ../../../docs/importing-postgres.md:77 -msgid "" -"In this case you can use the command suggested in the import task to " -"clear the database before retrying the import:" +msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:" msgstr "" #: ../../../docs/importing-postgres.md:85 -msgid "" -"Now on your local machine run `just run-tags setup-postgres` to prepare " -"the database roles etc." +msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc." msgstr "" #: ../../../docs/importing-postgres.md:87 -msgid "" -"If not, you probably get this error. `synapse` is the correct table " -"owner, but the role is missing in database." +msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database." msgstr "" #: ../../../docs/importing-postgres.md:93 -msgid "" -"Once the database is clear and the ownership of the tables has been fixed" -" in the SQL file, the import task should succeed." +msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed." msgstr "" #: ../../../docs/importing-postgres.md:95 -msgid "" -"Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths" -" (or even better, copy this line from your terminal)" +msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)" msgstr "" #: ../../../docs/importing-postgres.md:101 @@ -210,4 +147,3 @@ msgstr "" #: ../../../docs/importing-postgres.md:103 msgid "To open psql terminal run `/matrix/postgres/bin/cli`" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po index fea696edc..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 @@ -21,15 +21,11 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-synapse-media-store.md:1 -msgid "" -"Importing `media_store` data files from an existing Synapse installation " -"(optional)" +msgid "Importing `media_store` data files from an existing Synapse installation (optional)" msgstr "" #: ../../../docs/importing-synapse-media-store.md:3 -msgid "" -"Run this if you'd like to import your `media_store` files from a previous" -" installation of Synapse." +msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse." msgstr "" #: ../../../docs/importing-synapse-media-store.md:5 @@ -37,34 +33,19 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/importing-synapse-media-store.md:7 -msgid "" -"Before doing the actual data restore, **you need to upload your media " -"store directory to the server** (any path is okay)." +msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)." msgstr "" #: ../../../docs/importing-synapse-media-store.md:9 -msgid "" -"If you are [storing Matrix media files on Amazon S3](configuring-" -"playbook-s3.md) (optional), restoring with this tool is not possible " -"right now." +msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now." msgstr "" #: ../../../docs/importing-synapse-media-store.md:11 -msgid "" -"As an alternative, you can perform a manual restore using the [AWS CLI " -"tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync " -"/path/to/server/media_store/. s3://name-of-bucket/`)" +msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)" msgstr "" #: ../../../docs/importing-synapse-media-store.md:13 -msgid "" -"**Note for Mac users**: Due to case-sensitivity issues on certain Mac " -"filesystems (HFS or HFS+), filename corruption may occur if you copy a " -"`media_store` directory to your Mac. If you're transferring a " -"`media_store` directory between 2 servers, make sure you do it directly " -"(from server to server with a tool such as " -"[rsync](https://rsync.samba.org/)), and not by downloading the files to " -"your Mac." +msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac." msgstr "" #: ../../../docs/importing-synapse-media-store.md:15 @@ -72,14 +53,9 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-synapse-media-store.md:17 -msgid "" -"Run this command (make sure to replace `` " -"with a path on your server):" +msgid "Run this command (make sure to replace `` with a path on your server):" msgstr "" #: ../../../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!)." +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 75d5fd67f..7bc36c39e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po @@ -21,31 +21,19 @@ msgstr "" "Generated-By: Babel 2.16.0\n" #: ../../../docs/importing-synapse-sqlite.md:1 -msgid "" -"Importing an existing SQLite database from another Synapse installation " -"(optional)" +msgid "Importing an existing SQLite database from another Synapse installation (optional)" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:3 -msgid "" -"Run this if you'd like to import your database from a previous default " -"installation of Synapse (don't forget to import your `media_store` files " -"as well - see [the importing-synapse-media-store guide](importing-" -"synapse-media-store.md))." +msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:5 -msgid "" -"While this playbook only supports running Synapse in combination with " -"PostgreSQL, a Synapse instance installed manually usually defaults to " -"using an SQLite database." +msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:7 -msgid "" -"If you have such a Synapse setup and wish to migrate it to one managed by" -" the playbook (and over to PostgreSQL), this documentation page is for " -"you." +msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:9 @@ -57,27 +45,15 @@ msgid "Before doing the actual import:" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:13 -msgid "" -"**ensure you have NOT started Synapse yet**. That is, make sure you have " -"followed the [Installing step](installing.md), but haven't run the " -"playbook's `start` tag yet. If you had started your new Synapse instance," -" it may have already initialized your Postgres database and importing " -"onto it may not work. In such cases, you may need to clean up the " -"`synapse` database first." +msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first." msgstr "" #: ../../../docs/importing-synapse-sqlite.md:14 -msgid "" -"**ensure you have uploaded your SQLite database file to the server** (any" -" path is okay)" +msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:15 -msgid "" -"if you're using the integrated Postgres server (**by default, you are** " -"using it, unless you've explicitly switched to [Using an external " -"PostgreSQL server](configuring-playbook-external-postgres.md)), **make " -"sure Postgres is started** by running `just start-group postgres`" +msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:17 @@ -85,9 +61,7 @@ msgid "Importing" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:19 -msgid "" -"Run this command (make sure to replace `` " -"with a file path on your server):" +msgid "Run this command (make sure to replace `` with a file path on your server):" msgstr "" #: ../../../docs/importing-synapse-sqlite.md:25 @@ -95,17 +69,9 @@ msgid "**Notes**:" msgstr "" #: ../../../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!)." +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: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." +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 84bbd57ad..44dede432 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/installing.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/installing.po @@ -25,16 +25,11 @@ msgid "Installing" msgstr "" #: ../../../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" +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:5 -msgid "" -"If you've configured your DNS records and the playbook, you can start the" -" installation procedure." +msgid "If you've configured your DNS records and the playbook, you can start the installation procedure." msgstr "" #: ../../../docs/installing.md:7 @@ -42,15 +37,11 @@ msgid "Update Ansible roles" msgstr "" #: ../../../docs/installing.md:9 -msgid "" -"Before installing, you need to update the Ansible roles that this " -"playbook uses and fetches from outside." +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" #: ../../../docs/installing.md:11 -msgid "" -"To update your playbook directory and all upstream Ansible roles (defined" -" in the `requirements.yml` file), run:" +msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:" msgstr "" #: ../../../docs/installing.md:13 @@ -58,22 +49,15 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/installing.md:14 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/installing.md:16 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/installing.md:18 -msgid "" -"For details about `just` commands, take a look at: [Running `just` " -"commands](just.md)." +msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/installing.md:20 @@ -81,47 +65,27 @@ msgid "Install Matrix server and services" msgstr "" #: ../../../docs/installing.md:22 -msgid "" -"The Ansible playbook's tasks are tagged, so that certain parts of the " -"Ansible playbook can be run without running all other tasks." +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" #: ../../../docs/installing.md:24 -msgid "" -"The general command syntax for installation (and also maintenance) is: " -"`ansible-playbook -i inventory/hosts setup.yml " -"--tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself " -"familiar with the [playbook tags](playbook-tags.md) before proceeding." +msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding." msgstr "" #: ../../../docs/installing.md:26 -msgid "" -"If you **don't** use SSH keys for authentication, but rather a regular " -"password, you may need to add `--ask-pass` to the all Ansible commands." +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands." msgstr "" #: ../../../docs/installing.md:28 -msgid "" -"If you **do** use SSH keys for authentication, **and** use a non-root " -"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" -"pass`) to all Ansible commands." +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands." msgstr "" #: ../../../docs/installing.md:30 -msgid "" -"There 2 ways to start the installation process - depending on whether " -"you're [Installing a brand new server (without importing " -"data)](#installing-a-brand-new-server-without-importing-data) or " -"[Installing a server into which you'll import old data](#installing-a" -"-server-into-which-youll-import-old-data)." +msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)." msgstr "" #: ../../../docs/installing.md:32 -msgid "" -"**Note**: if you are migrating from an old server to a new one, take a " -"look at [this guide](maintenance-migrating.md) instead. This is an easier" -" and more straightforward way than installing a server and importing old " -"data into it." +msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it." msgstr "" #: ../../../docs/installing.md:34 @@ -129,9 +93,7 @@ msgid "Installing a brand new server (without importing data)" msgstr "" #: ../../../docs/installing.md:36 -msgid "" -"If this is **a brand new** Matrix server and you **won't be importing old" -" data into it**, run all these tags:" +msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:" msgstr "" #: ../../../docs/installing.md:42 @@ -139,10 +101,7 @@ msgid "This will do a full installation and start all Matrix services." msgstr "" #: ../../../docs/installing.md:44 -msgid "" -"**Note**: if the command does not work as expected, make sure that you " -"have properly installed and configured software required to run the " -"playbook, as described on [Prerequisites](prerequisites.md)." +msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)." msgstr "" #: ../../../docs/installing.md:46 @@ -150,25 +109,15 @@ msgid "Installing a server into which you'll import old data" msgstr "" #: ../../../docs/installing.md:48 -msgid "" -"If you will be importing data into your newly created Matrix server, " -"install it, but **do not** start its services just yet. Starting its " -"services or messing with its database now will affect your data import " -"later on." +msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on." msgstr "" #: ../../../docs/installing.md:50 -msgid "" -"To do the installation **without** starting services, run `ansible-" -"playbook` with the `install-all` tag only:" +msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:" msgstr "" #: ../../../docs/installing.md:56 -msgid "" -"⚠️ **Warning**: do not run the just \"recipe\" `just install-all` " -"instead, because it automatically starts services at the end of " -"execution. See: [Difference between playbook tags and shortcuts](just.md" -"#difference-between-playbook-tags-and-shortcuts)" +msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)" msgstr "" #: ../../../docs/installing.md:58 @@ -180,21 +129,15 @@ msgid "You can now:" msgstr "" #: ../../../docs/installing.md:62 -msgid "" -"[Importing an existing SQLite database (from another Synapse installation" -")](importing-synapse-sqlite.md) (optional)" +msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)" msgstr "" #: ../../../docs/installing.md:64 -msgid "" -"[Importing an existing Postgres database (from another installation" -")](importing-postgres.md) (optional)" +msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)" msgstr "" #: ../../../docs/installing.md:66 -msgid "" -"[Importing `media_store` data files from an existing Synapse installation" -"](importing-synapse-media-store.md) (optional)" +msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)" msgstr "" #: ../../../docs/installing.md:68 @@ -206,28 +149,19 @@ msgid "Create your user account" msgstr "" #: ../../../docs/installing.md:76 -msgid "" -"ℹ️ *You can skip this step if you have installed a server and imported " -"old data to it.*" +msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*" msgstr "" #: ../../../docs/installing.md:78 -msgid "" -"As you have configured your brand new server and the client, you need to " -"**create your user account** on your Matrix server." +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" #: ../../../docs/installing.md:80 -msgid "" -"After creating the user account, you can log in to it with [Element Web" -"](configuring-playbook-client-element-web.md) that this playbook has " -"installed for you at this URL: `https://element.example.com/`." +msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`." msgstr "" #: ../../../docs/installing.md:82 -msgid "" -"To create your user account (as an administrator of the server) via this " -"Ansible playbook, run the command below on your local computer." +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" #: ../../../docs/installing.md:84 @@ -239,29 +173,19 @@ msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" #: ../../../docs/installing.md:86 -msgid "" -"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " -"full ID (`@alice:example.com`)" +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/installing.md:87 -msgid "" -"Use `admin=yes` to make your user account an administrator of the Matrix " -"server" +msgid "Use `admin=yes` to make your user account an administrator of the Matrix server" msgstr "" #: ../../../docs/installing.md:95 -msgid "" -"Feel free to create as many accounts (for friends, family, etc.) as you " -"want. Still, perhaps you should grant full administrative access to your " -"account only (with `admin=yes`), and others should be created with " -"`admin=no`." +msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" #: ../../../docs/installing.md:97 -msgid "" -"For more information, see the documentation for [registering users" -"](registering-users.md)." +msgid "For more information, see the documentation for [registering users](registering-users.md)." msgstr "" #: ../../../docs/installing.md:99 @@ -269,52 +193,27 @@ msgid "Finalize the installation" msgstr "" #: ../../../docs/installing.md:101 -msgid "" -"Now you've configured Matrix services and your user account, you need to " -"**finalize the installation process** by [setting up Matrix delegation " -"(redirection)](howto-server-delegation.md), so that your Matrix server " -"(`matrix.example.com`) can present itself as the base domain " -"(`example.com`) in the Matrix network." +msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" #: ../../../docs/installing.md:103 -msgid "" -"This is required for federation to work! Without a proper configuration, " -"your server will effectively not be part of the Matrix network." +msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/installing.md:105 -msgid "" -"To configure the delegation, you have these two options. Choose one of " -"them according to your situation." +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" #: ../../../docs/installing.md:107 -msgid "" -"If you can afford to point the base domain at the Matrix server, follow " -"the instructions below which guide you into [serving the base domain" -"](configuring-playbook-base-domain-serving.md) from the integrated web " -"server. It will enable you to use a Matrix user ID like " -"`@alice:example.com` while hosting services on a subdomain like " -"`matrix.example.com`." +msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`." msgstr "" #: ../../../docs/installing.md:108 -msgid "" -"Alternatively, if you're using the base domain for other purposes and " -"cannot point it to the Matrix server (and thus cannot \"serve the base " -"domain\" from it), you most likely need to [manually install well-known " -"files on the base domain's server](configuring-well-known.md#manually-" -"installing-well-known-files-on-the-base-domains-server), but feel free to" -" familiarize yourself with all [server delegation (redirection) options" -"](howto-server-delegation.md)." +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)." msgstr "" #: ../../../docs/installing.md:110 -msgid "" -"To have the base domain served from the integrated web server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/installing.md:116 @@ -334,15 +233,11 @@ msgid "[check if services work](maintenance-checking-services.md)" msgstr "" #: ../../../docs/installing.md:127 -msgid "" -"or [set up additional services](configuring-playbook.md#other-" -"configuration-options) (bridges to other chat networks, bots, etc.)" +msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)" msgstr "" #: ../../../docs/installing.md:128 -msgid "" -"or learn how to [upgrade services when new versions are released" -"](maintenance-upgrading-services.md)" +msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/installing.md:129 @@ -354,25 +249,15 @@ msgid "or join some Matrix rooms:" msgstr "" #: ../../../docs/installing.md:131 -msgid "" -"via the *Explore rooms* feature in Element Web or some other clients, or " -"by discovering them using this [matrix-static " -"list](https://view.matrix.org). **Note**: joining large rooms may " -"overload small servers." +msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers." msgstr "" #: ../../../docs/installing.md:132 -msgid "" -"or come say Hi in our support room - [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com). You might learn something or get to help someone " -"else new to Matrix hosting." +msgid "or come say Hi in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" #: ../../../docs/installing.md:133 -msgid "" -"or help make this playbook better by contributing (code, documentation, " -"or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" +msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))" msgstr "" #: ../../../docs/installing.md:135 @@ -380,43 +265,27 @@ msgid "Maintaining your setup in the future" msgstr "" #: ../../../docs/installing.md:137 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/installing.md:139 -msgid "" -"The upstream projects, which this playbook makes use of, occasionally if " -"not often suffer from security vulnerabilities." +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities." msgstr "" #: ../../../docs/installing.md:141 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/installing.md:143 -msgid "" -"For more information about upgrading or maintaining services with the " -"playbook, take at look at this page: [Upgrading the Matrix services" -"](maintenance-upgrading-services.md)" +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" #: ../../../docs/installing.md:145 -msgid "" -"Feel free to **re-run the setup command any time** you think something is" -" wrong with the server configuration. Ansible will take your " -"configuration and update your server to match." +msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match." msgstr "" #: ../../../docs/installing.md:151 -msgid "" -"**Note**: see [this page on the playbook tags](playbook-tags.md) for more" -" information about those tags." +msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" #: ../../../docs/installing.md:153 @@ -424,25 +293,13 @@ msgid "Make full use of `just` shortcut commands" msgstr "" #: ../../../docs/installing.md:155 -msgid "" -"After you get familiar with reconfiguring and re-running the playbook to " -"maintain the server, upgrade its services, etc., you probably would like " -"to make use of `just` shortcut commands for faster input." +msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input." msgstr "" #: ../../../docs/installing.md:157 -msgid "" -"For example, `just install-all` is useful for maintaining your setup " -"quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-" -"in-playbook-runtime) than `just setup-all`) when its components remain " -"unchanged. If you adjust your `vars.yml` to remove other components, " -"you'd need to run `just setup-all`, or these components will still remain" -" installed." +msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" #: ../../../docs/installing.md:159 -msgid "" -"You can learn about the shortcut commands on this page: [Running `just` " -"commands](just.md)" +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 819ada89b..5db4caac8 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/just.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/just.po @@ -25,37 +25,19 @@ msgid "Running `just` commands" msgstr "" #: ../../../docs/just.md:3 -msgid "" -"We have previously used [make](https://www.gnu.org/software/make/) for " -"easily running some playbook commands (e.g. `make roles` which triggers " -"[`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-" -"galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can" -" still run these commands." +msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands." msgstr "" #: ../../../docs/just.md:5 -msgid "" -"In addition, we have added support for running commands via " -"[`just`](https://github.com/casey/just) - a more modern command-runner " -"alternative to `make`. It can be used to invoke `ansible-playbook` " -"commands with less typing." +msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing." msgstr "" #: ../../../docs/just.md:7 -msgid "" -"The `just` utility executes shortcut commands (called as \"recipes\"), " -"which invoke `ansible-playbook`, `ansible-galaxy` or " -"[`agru`](https://github.com/etkecc/agru) (depending on what is available " -"in your system). The targets of the recipes are defined in " -"[`justfile`](../justfile). Most of the just recipes have no corresponding" -" `Makefile` targets." +msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets." msgstr "" #: ../../../docs/just.md:9 -msgid "" -"For some recipes such as `just update`, our `justfile` recommends " -"installing [`agru`](https://github.com/etkecc/agru) (a faster alternative" -" to `ansible-galaxy`) to speed up the process." +msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process." msgstr "" #: ../../../docs/just.md:11 @@ -75,9 +57,7 @@ msgid "`just roles`" msgstr "" #: ../../../docs/just.md -msgid "" -"Install the necessary Ansible roles pinned in " -"[`requirements.yml`](../requirements.yml)" +msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)" msgstr "" #: ../../../docs/just.md @@ -93,9 +73,7 @@ msgid "`just install-all`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all" -",ensure-matrix-users-created,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`" msgstr "" #: ../../../docs/just.md @@ -103,9 +81,7 @@ msgid "`just setup-all`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all" -",ensure-matrix-users-created,start`" +msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`" msgstr "" #: ../../../docs/just.md @@ -113,9 +89,7 @@ msgid "`just install-all --ask-vault-pass`" msgstr "" #: ../../../docs/just.md -msgid "" -"Run commands with additional arguments (`--ask-vault-pass` will be " -"appended to the above installation command)" +msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)" msgstr "" #: ../../../docs/just.md @@ -155,20 +129,11 @@ msgid "`just register-user alice secret-password yes`" msgstr "" #: ../../../docs/just.md -msgid "" -"Registers an `alice` user with the `secret-password` password and admin " -"access (admin = `yes`)" +msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)" msgstr "" #: ../../../docs/just.md:26 -msgid "" -"While [our documentation on prerequisites](prerequisites.md) lists `just`" -" as one of the requirements for installation, using `just` is optional. " -"If you find it difficult to install it, do not find it useful, or want to" -" prefer raw `ansible-playbook` commands for some reason, feel free to run" -" all commands manually. For example, you can run `ansible-galaxy` " -"directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-" -"galaxy install -r requirements.yml -p roles/galaxy/ --force`." +msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`." msgstr "" #: ../../../docs/just.md:28 @@ -176,12 +141,7 @@ msgid "Difference between playbook tags and shortcuts" msgstr "" #: ../../../docs/just.md:30 -msgid "" -"It is worth noting that `just` \"recipes\" are different from [playbook " -"tags](playbook-tags.md). The recipes are shortcuts of commands defined in" -" `justfile` and can be executed by the `just` program only, while the " -"playbook tags are available for the raw `ansible-playbook` commands as " -"well. Please be careful not to confuse them." +msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them." msgstr "" #: ../../../docs/just.md:32 @@ -193,19 +153,9 @@ msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`" msgstr "" #: ../../../docs/just.md:36 -msgid "" -"The just recipe runs `ensure-matrix-users-created` and `start` tags after" -" `install-all`, while the latter runs only `install-all` tag. The correct" -" shortcut of the latter is `just run-tags install-all`." +msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`." msgstr "" #: ../../../docs/just.md:38 -msgid "" -"Such kind of difference sometimes matters. For example, when you install " -"a Matrix server into which you will import old data (see " -"[here](installing.md#installing-a-server-into-which-youll-import-old-" -"data)), you are not supposed to run `just install-all` or `just setup-" -"all`, because these commands start services immediately after installing " -"components which may prevent your from importing old data." +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 fc7585a6d..0f39a05f2 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po @@ -29,31 +29,19 @@ msgid "How to see the current status of your services" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:5 -msgid "" -"You can check the status of your services by using `systemctl status`. " -"Example:" +msgid "You can check the status of your services by using `systemctl status`. Example:" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:15 -msgid "" -"Docker containers that the playbook configures are supervised by " -"[systemd](https://wiki.archlinux.org/title/Systemd) and their logs are " -"configured to go to [systemd-" -"journald](https://wiki.archlinux.org/title/Systemd/Journal)." +msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:17 -msgid "" -"To prevent double-logging, Docker logging is disabled by explicitly " -"passing `--log-driver=none` to all containers. Due to this, you " -"**cannot** view logs using `docker logs`." +msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you **cannot** view logs using `docker logs`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:19 -msgid "" -"To view systemd-journald logs using " -"[journalctl](https://man.archlinux.org/man/journalctl.1), run a command " -"like this:" +msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:25 @@ -61,20 +49,11 @@ msgid "Increasing Synapse logging" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:27 -msgid "" -"Because the [Synapse](https://github.com/element-hq/synapse) Matrix " -"server is originally very chatty when it comes to logging, we " -"intentionally reduce its [logging " -"level](https://docs.python.org/3/library/logging.html#logging-levels) " -"from `INFO` to `WARNING`." +msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:29 -msgid "" -"If you'd like to debug an issue or [report a Synapse " -"bug](https://github.com/element-hq/synapse/issues/new/choose) to the " -"developers, it'd be better if you temporarily increasing the logging " -"level to `INFO`." +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 @@ -90,16 +69,11 @@ msgid "Remove unused Docker data" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:43 -msgid "" -"You can free some disk space from Docker, see [docker system " -"prune](https://docs.docker.com/engine/reference/commandline/system_prune/)" -" for more information." +msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:49 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags run-docker-prune`" +msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:51 @@ -107,9 +81,7 @@ msgid "Postgres" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:53 -msgid "" -"See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) " -"documentation page." +msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page." msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:55 @@ -117,8 +89,5 @@ msgid "Ma1sd" msgstr "" #: ../../../docs/maintenance-and-troubleshooting.md:57 -msgid "" -"See the dedicated [Adjusting ma1sd Identity Server configuration" -"](configuring-playbook-ma1sd.md) documentation page." +msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po index c27fdaf82..025ea7aa4 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po @@ -25,9 +25,7 @@ msgid "Checking if services work" msgstr "" #: ../../../docs/maintenance-checking-services.md:3 -msgid "" -"This playbook can perform a check to ensure that you've configured things" -" correctly and that services are running." +msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running." msgstr "" #: ../../../docs/maintenance-checking-services.md:5 @@ -35,9 +33,7 @@ msgid "To perform the check, run:" msgstr "" #: ../../../docs/maintenance-checking-services.md:11 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags self-check`" +msgid "The shortcut command with `just` program is also available: `just run-tags self-check`" msgstr "" #: ../../../docs/maintenance-checking-services.md:13 @@ -45,10 +41,5 @@ msgid "If it's all green, everything is probably running correctly." msgstr "" #: ../../../docs/maintenance-checking-services.md:15 -msgid "" -"Besides this self-check, you can also check whether your server federates" -" with the Matrix network by using the [Federation " -"Tester](https://federationtester.matrix.org/) against your base domain " -"(`example.com`), not the `matrix.example.com` subdomain." +msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po index 81d3506bd..77987e292 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po @@ -25,9 +25,7 @@ msgid "Migrating to new server" msgstr "" #: ../../../docs/maintenance-migrating.md:3 -msgid "" -"This documentation explains how to migrate your Matrix services (server, " -"client, bridges, etc.) and data **from an old server to a new server**." +msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**." msgstr "" #: ../../../docs/maintenance-migrating.md:5 @@ -35,39 +33,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/maintenance-migrating.md:6 -msgid "" -"This migration guide is applicable if you migrate from one server to " -"another server having the same CPU architecture (e.g. both servers being " -"`amd64`)." +msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)." msgstr "" #: ../../../docs/maintenance-migrating.md:8 -msgid "" -"If you're trying to migrate between different architectures (e.g. `amd64`" -" --> `arm64`), simply copying the complete `/matrix` directory is **not**" -" possible as it would move the raw PostgreSQL data " -"(`/matrix/postgres/data`) between different architectures. In this " -"specific case, you can use the guide below as a reference, but you would " -"also need to avoid syncing `/matrix/postgres/data` to the new host, and " -"also dump the database on your current server and import it properly on " -"the new server. See our [Backing up PostgreSQL](maintenance-postgres.md" -"#backing-up-postgresql) docs for help with PostgreSQL backup/restore." +msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore." msgstr "" #: ../../../docs/maintenance-migrating.md:9 -msgid "" -"If you have any questions about migration or encountered an issue during " -"migration, do not hesitate to ask for help on [our Matrix " -"room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). " -"You probably might want to prepare a temporary/sub account on another " -"Matrix server in case it becomes impossible to use your server due to " -"migration failure by any chance." +msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance." msgstr "" #: ../../../docs/maintenance-migrating.md:11 -msgid "" -"You can't change the domain (specified in the `matrix_domain` variable) " -"after the initial deployment." +msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment." msgstr "" #: ../../../docs/maintenance-migrating.md:13 @@ -75,10 +53,7 @@ msgid "Lower DNS TTL" msgstr "" #: ../../../docs/maintenance-migrating.md:15 -msgid "" -"Prepare by lowering DNS TTL for your domains (`matrix.example.com`, " -"etc.), so that DNS record changes would happen faster, leading to less " -"downtime." +msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime." msgstr "" #: ../../../docs/maintenance-migrating.md:17 @@ -86,22 +61,15 @@ msgid "Stop services on the old server completely" msgstr "" #: ../../../docs/maintenance-migrating.md:19 -msgid "" -"Before migrating, you need to stop all services on the old server and " -"make sure they won't be starting again." +msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again." msgstr "" #: ../../../docs/maintenance-migrating.md:21 -msgid "" -"To do so, it is recommended to run the `systemctl` command on the server." -" Running the playbook's `stop` tag also stops the services, but just " -"once; they will start again if you reboot the server." +msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server." msgstr "" #: ../../../docs/maintenance-migrating.md:23 -msgid "" -"Log in to the old server and run the command as `root` (or a user that " -"can run it with `sudo`):" +msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):" msgstr "" #: ../../../docs/maintenance-migrating.md:29 @@ -109,10 +77,7 @@ msgid "Copy data directory to the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:31 -msgid "" -"After you've confirmed that all services were stopped, copy the `/matrix`" -" directory from the old server to the new server. When copying, make sure" -" to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" +msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!" msgstr "" #: ../../../docs/maintenance-migrating.md:33 @@ -120,9 +85,7 @@ msgid "Adjust DNS records" msgstr "" #: ../../../docs/maintenance-migrating.md:35 -msgid "" -"Make sure your DNS records are adjusted to point to the new server's IP " -"address." +msgid "Make sure your DNS records are adjusted to point to the new server's IP address." msgstr "" #: ../../../docs/maintenance-migrating.md:37 @@ -130,9 +93,7 @@ msgid "Update `inventory/hosts` file" msgstr "" #: ../../../docs/maintenance-migrating.md:39 -msgid "" -"Having adjusted DNS records, replace the old server's external IP address" -" on the `inventory/hosts` file with that of the new server." +msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server." msgstr "" #: ../../../docs/maintenance-migrating.md:41 @@ -140,23 +101,15 @@ msgid "Create `matrix` user and group on the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:43 -msgid "" -"Then, run the command below on your local computer to create the `matrix`" -" user and group on the new server:" +msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:" msgstr "" #: ../../../docs/maintenance-migrating.md:49 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags setup-system-user`" +msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`" msgstr "" #: ../../../docs/maintenance-migrating.md:51 -msgid "" -"**Note**: because the `matrix` user and group are created dynamically on " -"each server, the user/group ID may differ between the old and new server." -" We suggest that you adjust ownership of `/matrix` files. To adjust the " -"ownership, log in to the new server and run the command:" +msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:" msgstr "" #: ../../../docs/maintenance-migrating.md:57 @@ -164,15 +117,11 @@ msgid "Install and start all services on the new server" msgstr "" #: ../../../docs/maintenance-migrating.md:59 -msgid "" -"Finally, run the command below on your local computer to finish the " -"installation and start all services:" +msgid "Finally, run the command below on your local computer to finish the installation and start all services:" msgstr "" #: ../../../docs/maintenance-migrating.md:65 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags install-all,start`" +msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`" msgstr "" #: ../../../docs/maintenance-migrating.md:67 @@ -180,16 +129,9 @@ msgid "Check if services work" msgstr "" #: ../../../docs/maintenance-migrating.md:69 -msgid "" -"After starting the services, you probably might want to ensure that " -"you've migrated things correctly and that services are running. For " -"instructions, see: [check if services work](maintenance-checking-" -"services.md)" +msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)" msgstr "" #: ../../../docs/maintenance-migrating.md:71 -msgid "" -"Having make sure that both services and federation work as expected, you " -"can safely shutdown the old server." +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 9bf3037a2..ff051ce43 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po @@ -25,9 +25,7 @@ msgid "PostgreSQL maintenance" msgstr "" #: ../../../docs/maintenance-postgres.md:3 -msgid "" -"This document shows you how to perform various maintenance tasks related " -"to the Postgres database server used by Matrix." +msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix." msgstr "" #: ../../../docs/maintenance-postgres.md:5 @@ -35,28 +33,19 @@ msgid "Table of contents:" msgstr "" #: ../../../docs/maintenance-postgres.md:7 -msgid "" -"[Getting a database terminal](#getting-a-database-terminal), for when you" -" wish to execute SQL queries" +msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries" msgstr "" #: ../../../docs/maintenance-postgres.md:9 -msgid "" -"[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a" -" Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-" -"vacuum.html) (optimizing disk space)" +msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)" msgstr "" #: ../../../docs/maintenance-postgres.md:11 -msgid "" -"[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to " -"make a backup" +msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup" msgstr "" #: ../../../docs/maintenance-postgres.md:13 -msgid "" -"[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major" -" versions of PostgreSQL. Such **manual upgrades are sometimes required**." +msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**." msgstr "" #: ../../../docs/maintenance-postgres.md:15 @@ -68,22 +57,15 @@ msgid "Getting a database terminal" msgstr "" #: ../../../docs/maintenance-postgres.md:19 -msgid "" -"You can use the `/matrix/postgres/bin/cli` tool to get interactive " -"terminal access ([psql](https://www.postgresql.org/docs/11/app-" -"psql.html)) to the PostgreSQL server." +msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server." msgstr "" #: ../../../docs/maintenance-postgres.md:21 -msgid "" -"If you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), the above tool will not be available." +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available." msgstr "" #: ../../../docs/maintenance-postgres.md:23 -msgid "" -"By default, this tool puts you in the `matrix` database, which contains " -"nothing." +msgid "By default, this tool puts you in the `matrix` database, which contains nothing." msgstr "" #: ../../../docs/maintenance-postgres.md:25 @@ -91,23 +73,15 @@ msgid "To see the available databases, run `\\list` (or just `\\l`)." msgstr "" #: ../../../docs/maintenance-postgres.md:27 -msgid "" -"To change to another database (for example `synapse`), run `\\connect " -"synapse` (or just `\\c synapse`)." +msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)." msgstr "" #: ../../../docs/maintenance-postgres.md:29 -msgid "" -"You can then proceed to write queries. Example: `SELECT COUNT(*) FROM " -"users;`" +msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`" msgstr "" #: ../../../docs/maintenance-postgres.md:31 -msgid "" -"**Be careful**. Modifying the database directly (especially as services " -"are running) is dangerous and may lead to irreversible database " -"corruption. When in doubt, consider [making a backup](#backing-up-" -"postgresql)." +msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)." msgstr "" #: ../../../docs/maintenance-postgres.md:33 @@ -115,28 +89,19 @@ msgid "Vacuuming PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:35 -msgid "" -"Deleting lots data from Postgres does not make it release disk space, " -"until you perform a [`VACUUM` " -"operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." +msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)." msgstr "" #: ../../../docs/maintenance-postgres.md:37 -msgid "" -"You can run different `VACUUM` operations via the playbook, with the " -"default preset being `vacuum-complete`:" +msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:" msgstr "" #: ../../../docs/maintenance-postgres.md:39 -msgid "" -"(default) `vacuum-complete`: stops all services temporarily and runs " -"`VACUUM FULL VERBOSE ANALYZE`." +msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`." msgstr "" #: ../../../docs/maintenance-postgres.md:40 -msgid "" -"`vacuum-full`: stops all services temporarily and runs `VACUUM FULL " -"VERBOSE`" +msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`" msgstr "" #: ../../../docs/maintenance-postgres.md:41 @@ -144,24 +109,15 @@ msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services" msgstr "" #: ../../../docs/maintenance-postgres.md:42 -msgid "" -"`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any " -"services" +msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services" msgstr "" #: ../../../docs/maintenance-postgres.md:43 -msgid "" -"`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is " -"just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) " -"without doing a vacuum, so it's faster)" +msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)" msgstr "" #: ../../../docs/maintenance-postgres.md:45 -msgid "" -"**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll " -"need plenty of available disk space in your Postgres data directory " -"(usually `/matrix/postgres/data`). These presets also stop all services " -"(e.g. Synapse, etc.) while the vacuum operation is running." +msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running." msgstr "" #: ../../../docs/maintenance-postgres.md:47 @@ -169,16 +125,11 @@ msgid "Example playbook invocations:" msgstr "" #: ../../../docs/maintenance-postgres.md:49 -msgid "" -"`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` " -"preset and restarts all services" +msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services" msgstr "" #: ../../../docs/maintenance-postgres.md:50 -msgid "" -"`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: " -"runs the `analyze` preset with all services remaining operational at all " -"times" +msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times" msgstr "" #: ../../../docs/maintenance-postgres.md:52 @@ -186,29 +137,19 @@ msgid "Backing up PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:54 -msgid "" -"To automatically make Postgres database backups on a fixed schedule, see " -"[Setting up postgres backup](configuring-playbook-postgres-backup.md)." +msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)." msgstr "" #: ../../../docs/maintenance-postgres.md:56 -msgid "" -"To make a one off back up of the current PostgreSQL database, make sure " -"it's running and then execute a command like this on the server:" +msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:" msgstr "" #: ../../../docs/maintenance-postgres.md:67 -msgid "" -"If you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), the above command will not work, because neither " -"the credentials file (`/matrix/postgres/env-postgres-psql`), nor the " -"`matrix-postgres` container is available." +msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available." msgstr "" #: ../../../docs/maintenance-postgres.md:69 -msgid "" -"Restoring a backup made this way can be done by [importing it](importing-" -"postgres.md)." +msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)." msgstr "" #: ../../../docs/maintenance-postgres.md:71 @@ -216,16 +157,11 @@ msgid "Upgrading PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:73 -msgid "" -"Unless you are using an [external Postgres server](configuring-playbook-" -"external-postgres.md), this playbook initially installs Postgres for you." +msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you." msgstr "" #: ../../../docs/maintenance-postgres.md:75 -msgid "" -"Once installed, the playbook attempts to preserve the Postgres version it" -" starts with. This is because newer Postgres versions cannot start with " -"data generated by older Postgres versions." +msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions." msgstr "" #: ../../../docs/maintenance-postgres.md:77 @@ -233,42 +169,23 @@ msgid "Upgrades must be performed manually." msgstr "" #: ../../../docs/maintenance-postgres.md:79 -msgid "" -"This playbook can upgrade your existing Postgres setup with the following" -" command:" +msgid "This playbook can upgrade your existing Postgres setup with the following command:" msgstr "" #: ../../../docs/maintenance-postgres.md:85 -msgid "" -"**The old Postgres data directory is backed up** automatically, by " -"renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to " -"a different path, pass some extra flags to the command above, like this: " -"`--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk" -"/matrix-postgres-before-upgrade\"`" +msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:87 -msgid "" -"The auto-upgrade-backup directory stays around forever, until you " -"**manually decide to delete it**." +msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**." msgstr "" #: ../../../docs/maintenance-postgres.md:89 -msgid "" -"As part of the upgrade, the database is dumped to `/tmp`, an upgraded and" -" empty Postgres server is started, and then the dump is restored into the" -" new server. To use a different directory for the dump, pass some extra " -"flags to the command above, like this: `--extra-" -"vars=\"postgres_dump_dir=/directory/to/dump/here\"`" +msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:91 -msgid "" -"To save disk space in `/tmp`, the dump file is gzipped on the fly at the " -"expense of CPU usage. If you have plenty of space in `/tmp` and would " -"rather avoid gzipping, you can explicitly pass a dump filename which " -"doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-" -"postgres-dump.sql\"`" +msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`" msgstr "" #: ../../../docs/maintenance-postgres.md:93 @@ -280,56 +197,25 @@ msgid "Tuning PostgreSQL" msgstr "" #: ../../../docs/maintenance-postgres.md:97 -msgid "" -"PostgreSQL can be " -"[tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) " -"to make it run faster. This is done by passing extra arguments to the " -"Postgres process." +msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process." msgstr "" #: ../../../docs/maintenance-postgres.md:99 -msgid "" -"The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting" -"/ansible-role-postgres) **already does some tuning by default**, which " -"matches the [tuning " -"logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js)" -" done by websites like https://pgtune.leopard.in.ua/. You can manually " -"influence some of the tuning variables. These parameters (variables) are " -"injected via the `postgres_postgres_process_extra_arguments_auto` " -"variable." +msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable." msgstr "" #: ../../../docs/maintenance-postgres.md:101 -msgid "" -"Most users should be fine with the automatically-done tuning. However, " -"you may wish to:" +msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:" msgstr "" #: ../../../docs/maintenance-postgres.md:103 -msgid "" -"**adjust the automatically-determined tuning parameters manually**: " -"change the values for the tuning variables defined in the Postgres role's" -" [default configuration file](https://github.com/mother-of-all-self-" -"hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see " -"`postgres_max_connections`, `postgres_data_storage` etc). These variables" -" are ultimately passed to Postgres via a " -"`postgres_postgres_process_extra_arguments_auto` variable" +msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable" msgstr "" #: ../../../docs/maintenance-postgres.md:105 -msgid "" -"**turn automatically-performed tuning off**: override it like this: " -"`postgres_postgres_process_extra_arguments_auto: []`" +msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`" msgstr "" #: ../../../docs/maintenance-postgres.md:107 -msgid "" -"**add additional tuning parameters**: define your additional Postgres " -"configuration parameters in " -"`postgres_postgres_process_extra_arguments_custom`. See " -"`postgres_postgres_process_extra_arguments_auto` defined in the Postgres " -"role's [default configuration file](https://github.com/mother-of-all-" -"self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for " -"inspiration" +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 b121bf1a8..00e65f61c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po @@ -25,9 +25,7 @@ msgid "Synapse maintenance" msgstr "" #: ../../../docs/maintenance-synapse.md:3 -msgid "" -"This document shows you how to perform various maintenance tasks related " -"to the Synapse chat server." +msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server." msgstr "" #: ../../../docs/maintenance-synapse.md:5 @@ -35,22 +33,15 @@ msgid "Table of contents:" msgstr "" #: ../../../docs/maintenance-synapse.md:7 -msgid "" -"[Purging old data with the Purge History API](#purging-old-data-with-the-" -"purge-history-api), for when you wish to delete in-use (but old) data " -"from the Synapse database" +msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database" msgstr "" #: ../../../docs/maintenance-synapse.md:9 -msgid "" -"[Compressing state with rust-synapse-compress-state](#compressing-state-" -"with-rust-synapse-compress-state)" +msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)" msgstr "" #: ../../../docs/maintenance-synapse.md:11 -msgid "" -"[Browse and manipulate the database](#browse-and-manipulate-the-" -"database), for when you really need to take matters into your own hands" +msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands" msgstr "" #: ../../../docs/maintenance-synapse.md:13 @@ -62,42 +53,23 @@ msgid "Purging old data with the Purge History API" msgstr "" #: ../../../docs/maintenance-synapse.md:17 -msgid "" -"You can use the **[Purge History API](https://github.com/element-" -"hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete " -"old messages on a per-room basis. **This is destructive** (especially for" -" non-federated rooms), because it means **people will no longer have " -"access to history past a certain point**." +msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**." msgstr "" #: ../../../docs/maintenance-synapse.md:19 -msgid "" -"To make use of this Synapse Admin API, **you'll need an admin access " -"token** first. Refer to the documentation on [how to obtain an access " -"token](obtaining-access-tokens.md)." +msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/maintenance-synapse.md:21 -msgid "" -"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." +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:23 -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." +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:25 -msgid "" -"After deleting data, you may wish to run a [`FULL` Postgres `VACUUM" -"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:27 @@ -105,27 +77,15 @@ msgid "Compressing state with rust-synapse-compress-state" msgstr "" #: ../../../docs/maintenance-synapse.md:29 -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." +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:31 -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." +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:33 -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." +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:35 @@ -133,23 +93,15 @@ msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" #: ../../../docs/maintenance-synapse.md:41 -msgid "" -"The shortcut command with `just` program is also available: `just run-" -"tags rust-synapse-compress-state`" +msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" #: ../../../docs/maintenance-synapse.md:43 -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." +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:45 -msgid "" -"After state compression, you may wish to run a [`FULL` Postgres `VACUUM" -"`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:47 @@ -157,46 +109,27 @@ msgid "Browse and manipulate the database" msgstr "" #: ../../../docs/maintenance-synapse.md:49 -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." +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:51 -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)." +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:53 -msgid "" -"First, set up an SSH tunnel to your Matrix server (skip if it is your " -"local machine):" +msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" #: ../../../docs/maintenance-synapse.md:60 -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:" +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:66 -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`)" +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:68 -msgid "" -"⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB " -"operations." +msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" #: ../../../docs/maintenance-synapse.md:70 @@ -204,28 +137,15 @@ msgid "Make Synapse faster" msgstr "" #: ../../../docs/maintenance-synapse.md:72 -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." +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:74 -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)." +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:76 -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." +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:78 @@ -233,44 +153,27 @@ msgid "Tuning caches and cache autotuning" msgstr "" #: ../../../docs/maintenance-synapse.md:80 -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." +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:82 -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)." +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:84 -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)." +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:86 -msgid "" -"Cache autotuning is **enabled by default** and controlled via the " -"following variables:" +msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" #: ../../../docs/maintenance-synapse.md:88 -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" +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:89 -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" +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:90 @@ -278,12 +181,7 @@ msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" #: ../../../docs/maintenance-synapse.md:92 -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)." +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:94 @@ -291,19 +189,9 @@ msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" #: ../../../docs/maintenance-synapse.md:102 -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." +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:104 -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)." +msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po index 0e5d6d184..e73b0da3e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po @@ -25,46 +25,27 @@ msgid "Upgrading the Matrix services" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:3 -msgid "" -"This playbook not only installs the various Matrix services for you, but " -"can also upgrade them as new versions are made available." +msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:5 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:7 -msgid "" -"The upstream projects, which this playbook makes use of, occasionally if " -"not often suffer from security vulnerabilities (for example, see " -"[here](https://github.com/element-hq/element-web/security) for known ones" -" on Element Web)." +msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:9 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:11 -msgid "" -"The developers of this playbook strive to maintain the playbook updated, " -"so that you can re-run the playbook to address such vulnerabilities. It " -"is **your responsibility** to keep your server and the services on it up-" -"to-date." +msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:13 -msgid "" -"If you want to be notified when new versions of Synapse are released, you" -" should join the Synapse Homeowners room: " -"[#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." +msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:15 @@ -76,10 +57,7 @@ msgid "Check the changelog" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:19 -msgid "" -"Before updating the playbook and the Ansible roles in the playbook, take " -"a look at [the changelog](../CHANGELOG.md) to see if there have been any " -"backward-incompatible changes that you need to take care of." +msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:21 @@ -87,10 +65,7 @@ msgid "Update the playbook and the Ansible roles" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:23 -msgid "" -"If it looks good to you, go to the `matrix-docker-ansible-deploy` " -"directory, update your playbook directory and all upstream Ansible roles " -"(defined in the `requirements.yml` file) by running:" +msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:25 @@ -98,22 +73,15 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:26 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:28 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:30 -msgid "" -"**Note**: for details about `just` commands, take a look at: [Running " -"`just` commands](just.md)." +msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:32 @@ -121,18 +89,11 @@ msgid "Re-run the playbook setup" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:34 -msgid "" -"After updating the Ansible roles, then re-run the [playbook " -"setup](installing.md#maintaining-your-setup-in-the-future) and restart " -"all services:" +msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:40 -msgid "" -"If you remove components from `vars.yml`, or if we switch some component " -"from being installed by default to not being installed by default " -"anymore, you'd need to run the setup command with the `setup-all` tag as " -"below:" +msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:46 @@ -140,31 +101,19 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:48 -msgid "" -"The `ensure-matrix-users-created` playbook tag makes the playbook " -"automatically create the bot's user account, if any." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:50 -msgid "" -"Our estimation is that running `--tags=install-all,start` is " -"approximately from **2 to 5 times faster** than running `setup-all" -",ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-" -"5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for " -"more information." +msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:52 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`. Note these shortcuts " -"run the `ensure-matrix-users-created` tag too." +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:54 -msgid "" -"See [this page on the playbook tags](playbook-tags.md) for more " -"information about those tags." +msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:56 @@ -172,14 +121,9 @@ msgid "PostgreSQL major version upgrade" msgstr "" #: ../../../docs/maintenance-upgrading-services.md:58 -msgid "" -"Major version upgrades to the internal PostgreSQL database are not done " -"automatically. Upgrades must be performed manually." +msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually." msgstr "" #: ../../../docs/maintenance-upgrading-services.md:60 -msgid "" -"For details about upgrading it, refer to the [upgrading PostgreSQL guide" -"](maintenance-postgres.md#upgrading-postgresql)." +msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po index 463793e6a..7302f99d6 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -25,16 +25,11 @@ msgid "Obtaining an Access Token" msgstr "" #: ../../../docs/obtaining-access-tokens.md:3 -msgid "" -"When setting up some optional features like bots and bridges you will " -"need to provide an access token for some user. This document provides " -"documentation on how to obtain such an access token." +msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token." msgstr "" #: ../../../docs/obtaining-access-tokens.md:5 -msgid "" -"**Access tokens are sensitive information. Do not include them in any bug" -" reports, messages, or logs. Do not share the access token with anyone.**" +msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" msgstr "" #: ../../../docs/obtaining-access-tokens.md:7 @@ -42,17 +37,11 @@ msgid "Prerequisites" msgstr "" #: ../../../docs/obtaining-access-tokens.md:9 -msgid "" -"The user for whom you want to obtain an access token needs to already " -"exist. You can use this playbook to [register a new user](registering-" -"users.md), if you have not already." +msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already." msgstr "" #: ../../../docs/obtaining-access-tokens.md:11 -msgid "" -"Below, we describe 2 ways to generate an access token for a user - using " -"[Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-" -"an-access-token-via-curl). For both ways you need the user's password." +msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password." msgstr "" #: ../../../docs/obtaining-access-tokens.md:13 @@ -68,9 +57,7 @@ msgid "Log in with the user's credentials." msgstr "" #: ../../../docs/obtaining-access-tokens.md:17 -msgid "" -"In the settings page, choose \"Help & About\", scroll down to the bottom " -"and expand the `Access Token` section (see screenshot below)." +msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)." msgstr "" #: ../../../docs/obtaining-access-tokens.md:18 @@ -78,15 +65,11 @@ msgid "Copy the access token to your configuration." msgstr "" #: ../../../docs/obtaining-access-tokens.md:19 -msgid "" -"Close the private browsing session. **Do not log out**. Logging out will " -"invalidate the token, making it not work." +msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work." msgstr "" #: ../../../docs/obtaining-access-tokens.md:21 -msgid "" -"![Obtaining an access token with Element " -"Web](assets/obtain_admin_access_token_element_web.png)" +msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)" msgstr "" #: ../../../docs/obtaining-access-tokens.md:21 @@ -98,10 +81,7 @@ msgid "Obtain an access token via curl" msgstr "" #: ../../../docs/obtaining-access-tokens.md:25 -msgid "" -"You can use the following command to get an access token for your user " -"directly from the [Matrix Client-Server " -"API](https://www.matrix.org/docs/guides/client-server-api#login):" +msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):" msgstr "" #: ../../../docs/obtaining-access-tokens.md:35 @@ -109,13 +89,9 @@ msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly." msgstr "" #: ../../../docs/obtaining-access-tokens.md:37 -msgid "" -"`YOURDEVICEID` is optional and can be used to more easily identify the " -"session later. When omitted (mind the commas in the JSON payload if " -"you'll be omitting it), a random device ID will be generated." +msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated." msgstr "" #: ../../../docs/obtaining-access-tokens.md:39 msgid "Your response will look like this (prettified):" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po index 54ba6d469..7f7923611 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po @@ -25,15 +25,11 @@ msgid "Playbook tags" msgstr "" #: ../../../docs/playbook-tags.md:3 -msgid "" -"The Ansible playbook's tasks are tagged, so that certain parts of the " -"Ansible playbook can be run without running all other tasks." +msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks." msgstr "" #: ../../../docs/playbook-tags.md:5 -msgid "" -"The general command syntax is: `ansible-playbook -i inventory/hosts " -"setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" +msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`" msgstr "" #: ../../../docs/playbook-tags.md:7 @@ -41,44 +37,23 @@ msgid "Here are some playbook tags that you should be familiar with:" msgstr "" #: ../../../docs/playbook-tags.md:9 -msgid "" -"`setup-all` - runs all setup tasks (installation and uninstallation) for " -"all components, but does not start/restart services" +msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services" msgstr "" #: ../../../docs/playbook-tags.md:11 -msgid "" -"`install-all` - like `setup-all`, but skips uninstallation tasks. Useful " -"for maintaining your setup quickly when its components remain unchanged. " -"If you adjust your `vars.yml` to remove components, you'd need to run " -"`setup-all` though, or these components will still remain installed" +msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed" msgstr "" #: ../../../docs/playbook-tags.md:13 -msgid "" -"`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for" -" a given role, but does not start/restart services. You can discover " -"these additional tags in each role (`roles/**/tasks/main.yml`). Running " -"per-component setup tasks is **not recommended**, as components sometimes" -" depend on each other and running just the setup tasks for a given " -"component may not be enough. For example, setting up the [mautrix-" -"telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in " -"addition to the `setup-mautrix-telegram` tag, requires database changes " -"(the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-" -"nginx-proxy` tag)." +msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)." msgstr "" #: ../../../docs/playbook-tags.md:15 -msgid "" -"`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but" -" skips uninstallation tasks. See `install-all` above for additional " -"information." +msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information." msgstr "" #: ../../../docs/playbook-tags.md:17 -msgid "" -"`start` - starts all systemd services and makes them start automatically " -"in the future" +msgid "`start` - starts all systemd services and makes them start automatically in the future" msgstr "" #: ../../../docs/playbook-tags.md:19 @@ -86,9 +61,7 @@ msgid "`stop` - stops all systemd services" msgstr "" #: ../../../docs/playbook-tags.md:21 -msgid "" -"`ensure-matrix-users-created` - a special tag which ensures that all " -"special users needed by the playbook (for bots, etc.) are created" +msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created" msgstr "" #: ../../../docs/playbook-tags.md:23 @@ -96,17 +69,9 @@ msgid "**Notes**:" msgstr "" #: ../../../docs/playbook-tags.md:24 -msgid "" -"`setup-*` tags and `install-*` tags **do not start services** " -"automatically, because you may wish to do things before starting " -"services, such as importing a database dump, restoring data from another " -"server, etc." +msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc." msgstr "" #: ../../../docs/playbook-tags.md:25 -msgid "" -"Please be careful not to confuse the playbook tags with the `just` " -"shortcut commands (\"recipes\"). For details about `just` commands, see: " -"[Running `just` commands](just.md)" +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 d7b541d33..6192e8a8c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po @@ -25,33 +25,19 @@ msgid "Prerequisites" msgstr "" #: ../../../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)" +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: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." +msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step." msgstr "" #: ../../../docs/prerequisites.md:7 -msgid "" -"We will be using `example.com` as the domain in the following " -"instruction. Please remember to replace it with your own domain before " -"running any commands." +msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands." msgstr "" #: ../../../docs/prerequisites.md:9 -msgid "" -"**Note**: if you do not have an existing Matrix server and want to start " -"quickly with \"opinionated defaults\", we suggest you to follow ⚡ " -"**[Quick start](quick-start.md)** installation guide." +msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide." msgstr "" #: ../../../docs/prerequisites.md:11 @@ -59,49 +45,23 @@ msgid "Your local computer" msgstr "" #: ../../../docs/prerequisites.md:13 -msgid "" -"[Ansible](http://ansible.com/) program. It's used to run this playbook " -"and configures your server for you. Take a look at [our guide about " -"Ansible](ansible.md) for more information, as well as [version " -"requirements](ansible.md#supported-ansible-versions) and alternative ways" -" to run Ansible." +msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible." msgstr "" #: ../../../docs/prerequisites.md:15 -msgid "" -"[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python " -"library. See [this official " -"documentation](https://passlib.readthedocs.io/en/stable/install.html" -"#installation-instructions) for an instruction to install it. On most " -"distros, you need to install some `python-passlib` or `py3-passlib` " -"package, etc." +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." +msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components." msgstr "" #: ../../../docs/prerequisites.md:19 -msgid "" -"[`just`](https://github.com/casey/just) for running `just roles`, `just " -"update`, etc. (see [`justfile`](../justfile)), although you can also run " -"these commands manually. Take at look at this documentation for more " -"information: [Running `just` commands](just.md)." +msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)." msgstr "" #: ../../../docs/prerequisites.md:21 -msgid "" -"Strong password (random strings) generator. The playbook often requires " -"you to create a strong password and use it for settings on `vars.yml`, " -"components, etc. As any tools should be fine, this playbook has adopted " -"[`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). " -"[Password Tech](https://pwgen-win.sourceforge.io/), formerly known as " -"\"PWGen for Windows\", is available as free and open source password " -"generator for Windows. Generally, using a random generator available on " -"the internet is not recommended." +msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended." msgstr "" #: ../../../docs/prerequisites.md:23 @@ -109,10 +69,7 @@ msgid "Server" msgstr "" #: ../../../docs/prerequisites.md:25 -msgid "" -"(Recommended) An **x86** server ([What kind of server specs do I " -"need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these " -"operating systems that make use of [systemd](https://systemd.io/):" +msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):" msgstr "" #: ../../../docs/prerequisites.md:26 @@ -120,9 +77,7 @@ msgid "**Archlinux**" msgstr "" #: ../../../docs/prerequisites.md:27 -msgid "" -"**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL " -"alternatives (although your mileage may vary)" +msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)" msgstr "" #: ../../../docs/prerequisites.md:28 @@ -130,82 +85,43 @@ msgid "**Debian** (10/Buster or newer)" msgstr "" #: ../../../docs/prerequisites.md:29 -msgid "" -"**Ubuntu** (18.04 or newer, although [20.04 may be " -"problematic](ansible.md#supported-ansible-versions) if you run the " -"Ansible playbook on it)" +msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)" msgstr "" #: ../../../docs/prerequisites.md:31 -msgid "" -"Generally, newer is better. We only strive to support released stable " -"versions of distributions, not betas or pre-releases. This playbook can " -"take over your whole server or co-exist with other services that you have" -" there." +msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there." msgstr "" #: ../../../docs/prerequisites.md:33 -msgid "" -"This playbook somewhat supports running on non-`amd64` architectures like" -" ARM. See [Alternative Architectures](alternative-architectures.md)." +msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)." msgstr "" #: ../../../docs/prerequisites.md:35 -msgid "" -"If your distro runs within an [LXC " -"container](https://linuxcontainers.org/), you may hit [this " -"issue](https://github.com/spantaleev/matrix-docker-ansible-" -"deploy/issues/703). It can be worked around, if absolutely necessary, but" -" we suggest that you avoid running from within an LXC container." +msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container." msgstr "" #: ../../../docs/prerequisites.md:37 -msgid "" -"`root` access to your server (or a user capable of elevating to `root` " -"via `sudo`)." +msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)." msgstr "" #: ../../../docs/prerequisites.md:39 -msgid "" -"[Python](https://www.python.org/). Most distributions install Python by " -"default, but some don't (e.g. Ubuntu 18.04) and require manual " -"installation (something like `apt-get install python3`). On some distros," -" Ansible may incorrectly [detect the Python " -"version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html)" -" (2 vs 3) and you may need to explicitly specify the interpreter path in " -"`inventory/hosts` during installation (e.g. " -"`ansible_python_interpreter=/usr/bin/python3`)" +msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)" msgstr "" #: ../../../docs/prerequisites.md:41 -msgid "" -"[sudo](https://www.sudo.ws/), even when you've configured Ansible to log " -"in as `root`. Some distributions, like a minimal Debian net install, do " -"not include the `sudo` package by default." +msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default." msgstr "" #: ../../../docs/prerequisites.md:43 -msgid "" -"An HTTPS-capable web server at the base domain name (`example.com`) which" -" is capable of serving static files. Unless you decide to [Serve the base" -" domain from the Matrix server](configuring-playbook-base-domain-" -"serving.md) or alternatively, to use DNS SRV records for [Server " -"Delegation](howto-server-delegation.md)." +msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)." msgstr "" #: ../../../docs/prerequisites.md:45 -msgid "" -"Properly configured DNS records for `example.com` (details in " -"[Configuring DNS](configuring-dns.md))." +msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))." msgstr "" #: ../../../docs/prerequisites.md:47 -msgid "" -"Some TCP/UDP ports open. This playbook (actually [Docker " -"itself](https://docs.docker.com/network/iptables/)) configures the " -"server's internal firewall for you. In most cases, you don't need to do " -"anything special. But **if your server is running behind another " -"firewall**, you'd need to open these ports:" +msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:" msgstr "" #: ../../../docs/prerequisites.md:49 @@ -233,11 +149,7 @@ msgid "`5349/udp`: TURN over UDP (used by Coturn)" msgstr "" #: ../../../docs/prerequisites.md:55 -msgid "" -"`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some" -" cases, this **may necessary even with federation disabled**. Integration" -" Servers (like Dimension) and Identity Servers (like ma1sd) may need to " -"access `openid` APIs on the federation port." +msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port." msgstr "" #: ../../../docs/prerequisites.md:56 @@ -245,15 +157,9 @@ 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." +msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that." msgstr "" #: ../../../docs/prerequisites.md:61 -msgid "" -"[▶️](configuring-dns.md) When ready to proceed, continue with " -"[Configuring DNS](configuring-dns.md)." +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 dd3207b8d..680f8b634 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po @@ -25,15 +25,11 @@ msgid "Quick start" msgstr "" #: ../../../docs/quick-start.md:9 -msgid "" -"This page explains how to use this Ansible playbook to install Matrix " -"services on your server with a minimal set of core services." +msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." msgstr "" #: ../../../docs/quick-start.md:11 -msgid "" -"We will be using `example.com` as the \"base domain\" in the following " -"instruction." +msgid "We will be using `example.com` as the \"base domain\" in the following instruction." msgstr "" #: ../../../docs/quick-start.md:13 @@ -41,9 +37,7 @@ msgid "By following the instruction on this page, you will set up:" msgstr "" #: ../../../docs/quick-start.md:15 -msgid "" -"**your own Matrix server** on a `matrix.example.com` server, which is " -"configured to present itself as `example.com`" +msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" msgstr "" #: ../../../docs/quick-start.md:16 @@ -51,23 +45,15 @@ msgid "**your user account** like `@alice:example.com` on the server" msgstr "" #: ../../../docs/quick-start.md:17 -msgid "" -"a **self-hosted Matrix client**, [Element Web](configuring-playbook-" -"client-element-web.md) with the default subdomain at " -"`element.example.com`" +msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" msgstr "" #: ../../../docs/quick-start.md:18 -msgid "" -"Matrix delegation, so that your `matrix.example.com` server (presenting " -"itself as `example.com`) can join the Matrix Federation and communicate " -"with any other server in the Matrix network" +msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" msgstr "" #: ../../../docs/quick-start.md:20 -msgid "" -"Please remember to replace `example.com` with your own domain before " -"running any commands." +msgid "Please remember to replace `example.com` with your own domain before running any commands." msgstr "" #: ../../../docs/quick-start.md:22 @@ -75,40 +61,23 @@ msgid "Prerequisites" msgstr "" #: ../../../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)" +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: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)." +msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)." msgstr "" #: ../../../docs/quick-start.md:28 -msgid "" -"When preparing your server, make sure to check [the server specs you " -"need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting " -"with a server having at least 2GB of memory." +msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory." msgstr "" #: ../../../docs/quick-start.md:34 -msgid "" -"If you encounter an error during installation, please make sure that you " -"have installed and configured programs correctly." +msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly." msgstr "" #: ../../../docs/quick-start.md:36 -msgid "" -"One of the main reasons of basic errors is using an incompatible version " -"of required software such as Ansible. Take a look at [our guide about " -"Ansible](ansible.md) for more information. In short: installing the " -"latest available version is recommended." +msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended." msgstr "" #: ../../../docs/quick-start.md:38 @@ -116,22 +85,15 @@ msgid "Configure your DNS settings" msgstr "" #: ../../../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)" +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:42 -msgid "" -"After installing and configuring prerequisites, you will need to " -"**configure DNS records**." +msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." msgstr "" #: ../../../docs/quick-start.md:44 -msgid "" -"To configure Matrix services in the default settings, go to your DNS " -"service provider, and adjust DNS records as below." +msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below." msgstr "" #: ../../../docs/quick-start.md @@ -187,10 +149,7 @@ msgid "`matrix.example.com`" msgstr "" #: ../../../docs/quick-start.md:51 -msgid "" -"As the table illustrates, you need to create 2 subdomains " -"(`matrix.example.com` and `element.example.com`) and point both of them " -"to your server's IP address (DNS `A` record or `CNAME` record is fine)." +msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." msgstr "" #: ../../../docs/quick-start.md:53 @@ -198,9 +157,7 @@ msgid "It might take some time for the DNS records to propagate after creation." msgstr "" #: ../../../docs/quick-start.md:55 -msgid "" -"**💡 Note**: if you are using Cloudflare DNS, make sure to disable the " -"proxy and set all records to \"DNS only\"" +msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" msgstr "" #: ../../../docs/quick-start.md:57 @@ -208,10 +165,7 @@ msgid "Get the playbook" msgstr "" #: ../../../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)" +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:61 @@ -219,22 +173,15 @@ msgid "Next, let's **get the playbook's source code**." msgstr "" #: ../../../docs/quick-start.md:63 -msgid "" -"We recommend to do so with [git](https://git-scm.com/) as it enables you " -"to keep it up to date with the latest source code. While it is possible " -"to download the playbook as a ZIP archive, it is not recommended." +msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended." msgstr "" #: ../../../docs/quick-start.md:65 -msgid "" -"To get the playbook with git, install git on your computer, go to a " -"directory, and run the command:" +msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:" msgstr "" #: ../../../docs/quick-start.md:71 -msgid "" -"It will fetch the playbook to a new `matrix-docker-ansible-deploy` " -"directory underneath the directory you are currently in." +msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in." msgstr "" #: ../../../docs/quick-start.md:73 @@ -242,47 +189,31 @@ msgid "Configure the playbook" msgstr "" #: ../../../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)" +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:77 -msgid "" -"Now that the playbook was fetched, it is time to **configure** it per " -"your needs." +msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." msgstr "" #: ../../../docs/quick-start.md:79 -msgid "" -"To install Matrix services with this playbook, you would at least need 2 " -"configuration files." +msgid "To install Matrix services with this playbook, you would at least need 2 configuration files." msgstr "" #: ../../../docs/quick-start.md:81 -msgid "" -"For your convenience, we have prepared example files of them " -"([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." +msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))." msgstr "" #: ../../../docs/quick-start.md:83 -msgid "" -"To start quickly based on these example files, go into the `matrix-" -"docker-ansible-deploy` directory and follow the instructions below:" +msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:" msgstr "" #: ../../../docs/quick-start.md:85 -msgid "" -"Create a directory to hold your configuration: `mkdir -p " -"inventory/host_vars/matrix.example.com` where `example.com` is your " -"\"base domain\"" +msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\"" msgstr "" #: ../../../docs/quick-start.md:86 -msgid "" -"Copy the sample configuration file: `cp examples/vars.yml " -"inventory/host_vars/matrix.example.com/vars.yml`" +msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`" msgstr "" #: ../../../docs/quick-start.md:87 @@ -290,9 +221,7 @@ msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts` msgstr "" #: ../../../docs/quick-start.md:88 -msgid "" -"Edit the configuration file " -"(`inventory/host_vars/matrix.example.com/vars.yml`)" +msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)" msgstr "" #: ../../../docs/quick-start.md:89 @@ -300,9 +229,7 @@ msgid "Edit the inventory hosts file (`inventory/hosts`)" msgstr "" #: ../../../docs/quick-start.md:91 -msgid "" -"Before editing these 2 files, make sure to read explanations on them to " -"understand what needs to be configured." +msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured." msgstr "" #: ../../../docs/quick-start.md:93 @@ -310,30 +237,15 @@ msgid "**💡 Notes:**" msgstr "" #: ../../../docs/quick-start.md:94 -msgid "" -"If you are not in control of anything on the base domain, you would need " -"to set additional configuration on `vars.yml`. For more information, see " -"[How do I install on matrix.example.com without involving the base " -"domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-" -"the-base-domain) on our FAQ." +msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ." msgstr "" #: ../../../docs/quick-start.md:95 -msgid "" -"Certain configuration decisions (like the base domain configured in " -"`matrix_domain` and homeserver implementation configured in " -"`matrix_homeserver_implementation`) are final. If you make the wrong " -"choice and wish to change it, you'll have to run the Uninstalling step " -"and start over." +msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over." msgstr "" #: ../../../docs/quick-start.md:96 -msgid "" -"Instead of configuring a lot of things all at once, we recommend starting" -" with the basic (default) settings in order to get yourself familiar with" -" how the playbook works. After making sure that everything works as " -"expected, you can add (and remove) advanced settings / features and run " -"the playbook as many times as you wish." +msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish." msgstr "" #: ../../../docs/quick-start.md:98 @@ -341,16 +253,11 @@ msgid "Install" msgstr "" #: ../../../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)" +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:102 -msgid "" -"After editing `vars.yml` and `hosts` files, let's start the " -"**installation** procedure." +msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." msgstr "" #: ../../../docs/quick-start.md:104 @@ -358,9 +265,7 @@ msgid "Update Ansible roles" msgstr "" #: ../../../docs/quick-start.md:106 -msgid "" -"Before installing, you need to update the Ansible roles that this " -"playbook uses and fetches from outside." +msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside." msgstr "" #: ../../../docs/quick-start.md:108 @@ -372,16 +277,11 @@ msgid "either: `just update`" msgstr "" #: ../../../docs/quick-start.md:111 -msgid "" -"or: a combination of `git pull` and `just roles` (or `make roles` if you " -"have `make` program on your computer instead of `just`)" +msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)" msgstr "" #: ../../../docs/quick-start.md:113 -msgid "" -"If you don't have either `just` tool or `make` program, you can run the " -"`ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy " -"install -r requirements.yml -p roles/galaxy/ --force`" +msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`" msgstr "" #: ../../../docs/quick-start.md:115 @@ -393,22 +293,15 @@ msgid "Then, run the command below to start installation:" msgstr "" #: ../../../docs/quick-start.md:123 -msgid "" -"If you **don't** use SSH keys for authentication, but rather a regular " -"password, you may need to add `--ask-pass` to the command." +msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command." msgstr "" #: ../../../docs/quick-start.md:125 -msgid "" -"If you **do** use SSH keys for authentication, **and** use a non-root " -"user to *become* root (sudo), you may need to add `-K` (`--ask-become-" -"pass`) to the command." +msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command." msgstr "" #: ../../../docs/quick-start.md:127 -msgid "" -"Wait until the command completes. If it's all green, everything should be" -" running properly." +msgid "Wait until the command completes. If it's all green, everything should be running properly." msgstr "" #: ../../../docs/quick-start.md:129 @@ -416,22 +309,15 @@ msgid "Create your user account" msgstr "" #: ../../../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)" +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:133 -msgid "" -"As you have configured your brand new server and the client, you need to " -"**create your user account** on your Matrix server." +msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server." msgstr "" #: ../../../docs/quick-start.md:135 -msgid "" -"To create your user account (as an administrator of the server) via this " -"Ansible playbook, run the command below on your local computer." +msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer." msgstr "" #: ../../../docs/quick-start.md:137 @@ -443,9 +329,7 @@ msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`" msgstr "" #: ../../../docs/quick-start.md:139 -msgid "" -"For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your " -"full ID (`@alice:example.com`)" +msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/quick-start.md:151 @@ -453,77 +337,43 @@ msgid "Finalize server installation" msgstr "" #: ../../../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)" +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: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." +msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network." msgstr "" #: ../../../docs/quick-start.md:157 -msgid "" -"**This is required for federation to work!** Without a proper " -"configuration, your server will effectively not be part of the Matrix " -"network." +msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network." msgstr "" #: ../../../docs/quick-start.md:159 -msgid "" -"To configure the delegation, you have these two options. Choose one of " -"them according to your situation." +msgid "To configure the delegation, you have these two options. Choose one of them according to your situation." msgstr "" #: ../../../docs/quick-start.md:161 -msgid "" -"If you can afford to point the base domain at the Matrix server, follow " -"the instruction below which guides you into [serving the base domain" -"](configuring-playbook-base-domain-serving.md) from the integrated web " -"server." +msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server." msgstr "" #: ../../../docs/quick-start.md:162 -msgid "" -"Alternatively, if you're using the base domain for other purposes and " -"cannot point it to the Matrix server (and thus cannot \"serve the base " -"domain\" from it), you most likely need to [manually install well-known " -"files on the base domain's server](configuring-well-known.md#manually-" -"installing-well-known-files-on-the-base-domains-server)." +msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)." msgstr "" #: ../../../docs/quick-start.md:164 -msgid "" -"To have the base domain served from the integrated web server, add the " -"following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/quick-start.md:170 -msgid "" -"After configuring the playbook, run the command below and wait until it " -"finishes:" +msgid "After configuring the playbook, run the command below and wait until it finishes:" msgstr "" #: ../../../docs/quick-start.md:176 -msgid "" -"💡 Running the `install-matrix-static-files` playbook tag (as done here) " -"is an optimized version of running [the full setup command](#run-" -"installation-command)." +msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)." msgstr "" #: ../../../docs/quick-start.md:178 -msgid "" -"After the command finishes, you can also check whether your server " -"federates with the Matrix network by using the [Federation " -"Tester](https://federationtester.matrix.org/) against your base domain " -"(`example.com`), not the `matrix.example.com` subdomain." +msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain." msgstr "" #: ../../../docs/quick-start.md:180 @@ -531,9 +381,7 @@ msgid "Re-run the full setup command any time" msgstr "" #: ../../../docs/quick-start.md:182 -msgid "" -"If you think something is wrong with the server configuration, feel free " -"to re-run the setup command any time:" +msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:" msgstr "" #: ../../../docs/quick-start.md:188 @@ -541,32 +389,19 @@ msgid "Log in to your user account" msgstr "" #: ../../../docs/quick-start.md:190 -msgid "" -"Finally, let's make sure that you can log in to the created account with " -"the specified password." +msgid "Finally, let's make sure that you can log in to the created account with the specified password." msgstr "" #: ../../../docs/quick-start.md:192 -msgid "" -"You should be able to log in to it with your own [Element Web" -"](configuring-playbook-client-element-web.md) client which you have set " -"up at `element.example.com` by running the playbook. Open the URL " -"(`https://element.example.com`) in a web browser and enter your " -"credentials to log in." +msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in." msgstr "" #: ../../../docs/quick-start.md:194 -msgid "" -"**If you successfully logged in to your account, installing and " -"configuring is complete**🎉" +msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉" msgstr "" #: ../../../docs/quick-start.md:196 -msgid "" -"Come say Hi👋 in our support room - [#matrix-docker-ansible-" -"deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-" -"deploy:devture.com). You might learn something or get to help someone " -"else new to Matrix hosting." +msgid "Come say Hi👋 in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting." msgstr "" #: ../../../docs/quick-start.md:198 @@ -574,17 +409,11 @@ msgid "Things to do next" msgstr "" #: ../../../docs/quick-start.md:200 -msgid "" -"Once you get familiar with the playbook, you might probably want to set " -"up additional services such as a bridge on your server." +msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server." msgstr "" #: ../../../docs/quick-start.md:202 -msgid "" -"As this page intends to be a quick start guide which explains how to " -"start the core Matrix services, it does not cover a topic like how to set" -" them up. Take a look at the list of [things to do next](installing.md" -"#things-to-do-next) to learn more." +msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more." msgstr "" #: ../../../docs/quick-start.md:204 @@ -592,23 +421,13 @@ msgid "⚠️Keep the playbook and services up-to-date" msgstr "" #: ../../../docs/quick-start.md:206 -msgid "" -"While this playbook helps you to set up Matrix services and maintain " -"them, it will **not** automatically run the maintenance task for you. You" -" will need to update the playbook and re-run it **manually**." +msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**." msgstr "" #: ../../../docs/quick-start.md:208 -msgid "" -"Since it is unsafe to keep outdated services running on the server " -"connected to the internet, please consider to update the playbook and re-" -"run it periodically, in order to keep the services up-to-date." +msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date." msgstr "" #: ../../../docs/quick-start.md:210 -msgid "" -"For more information about upgrading or maintaining services with the " -"playbook, take at look at this page: [Upgrading the Matrix services" -"](maintenance-upgrading-services.md)" +msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po index 61b349423..5a62a9d95 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po @@ -25,9 +25,7 @@ msgid "Registering users" msgstr "" #: ../../../docs/registering-users.md:3 -msgid "" -"This documentation page tells you how to create user accounts on your " -"Matrix server." +msgid "This documentation page tells you how to create user accounts on your Matrix server." msgstr "" #: ../../../docs/registering-users.md:5 @@ -47,9 +45,7 @@ msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)" msgstr "" #: ../../../docs/registering-users.md:10 -msgid "" -"[Letting certain users register on your private server](#letting-certain-" -"users-register-on-your-private-server)" +msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)" msgstr "" #: ../../../docs/registering-users.md:11 @@ -57,9 +53,7 @@ msgid "[Enabling public user registration](#enabling-public-user-registration)" msgstr "" #: ../../../docs/registering-users.md:12 -msgid "" -"[Adding/Removing Administrator privileges to an existing user" -"](#addingremoving-administrator-privileges-to-an-existing-user)" +msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)" msgstr "" #: ../../../docs/registering-users.md:14 @@ -75,23 +69,15 @@ msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" #: ../../../docs/registering-users.md:18 -msgid "" -"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " -"(`@alice:example.com`)" +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/registering-users.md:19 -msgid "" -"Use `admin=yes` or `admin=no` depending on whether you wish to make the " -"user an administrator of the Matrix server" +msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server" msgstr "" #: ../../../docs/registering-users.md:21 -msgid "" -"After registering a user (using one of the methods below), **you can log " -"in with that user** via the [Element Web](configuring-playbook-client-" -"element-web.md) service that this playbook has installed for you at a URL" -" like this: `https://element.example.com/`." +msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`." msgstr "" #: ../../../docs/registering-users.md:23 @@ -99,11 +85,7 @@ msgid "Registering users via the Ansible playbook" msgstr "" #: ../../../docs/registering-users.md:25 -msgid "" -"It's best to register users via the Ansible playbook, because it works " -"regardless of homeserver implementation (Synapse, Dendrite, etc) or usage" -" of [Matrix Authentication Service](configuring-playbook-matrix-" -"authentication-service.md) (MAS)." +msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)." msgstr "" #: ../../../docs/registering-users.md:27 @@ -115,24 +97,11 @@ msgid "**or** by invoking `ansible-playbook` manually:" msgstr "" #: ../../../docs/registering-users.md:43 -msgid "" -"Feel free to register as many users (for friends, family, etc.) as you " -"want. Still, perhaps you should grant full administrative access to your " -"user account only (with `admin=yes`), and others should be created with " -"`admin=no`." +msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`." msgstr "" #: ../../../docs/registering-users.md:45 -msgid "" -"⚠️ **Warning**: If you're registering users against Matrix Authentication" -" Service, do note that it [still insists](https://github.com/element-hq" -"/matrix-authentication-service/issues/1505) on having a verified email " -"address for each user. Upon a user's first login, they will be asked to " -"confirm their email address. This requires that email sending is " -"[configured](./configuring-playbook-email.md). You can also consult the " -"[Working around email deliverability issues](./configuring-playbook-" -"matrix-authentication-service.md#working-around-email-deliverability-" -"issues) section for more information." +msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." msgstr "" #: ../../../docs/registering-users.md:47 @@ -140,12 +109,7 @@ msgid "Registering users manually for Synapse" msgstr "" #: ../../../docs/registering-users.md:49 -msgid "" -"If you're using the [Synapse](configuring-playbook-synapse.md) homeserver" -" implementation (which is the default), you can register users via the " -"command-line after **SSH**-ing to your server (requires that [all " -"services have been started](installing.md#install-matrix-server-and-" -"services)):" +msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:57 @@ -153,11 +117,7 @@ msgid "Registering users manually for Dendrite" msgstr "" #: ../../../docs/registering-users.md:59 -msgid "" -"If you're using the [Dendrite](./configuring-playbook-dendrite.md) " -"homeserver implementation, you can register users via the command-line " -"after **SSH**-ing to your server (requires that [all services have been " -"started](installing.md#install-matrix-server-and-services)):" +msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:67 @@ -165,34 +125,15 @@ msgid "Registering users manually for Matrix Authentication Service" msgstr "" #: ../../../docs/registering-users.md:69 -msgid "" -"If you're using the [Matrix Authentication Service](./configuring-" -"playbook-matrix-authentication-service.md) and your existing homeserver " -"(most likely [Synapse](./configuring-playbook-synapse.md)) is delegating " -"authentication to it, you can register users via the command-line after " -"**SSH**-ing to your server (requires that [all services have been " -"started](installing.md#install-matrix-server-and-services)):" +msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):" msgstr "" #: ../../../docs/registering-users.md:77 -msgid "" -"This `register-user` script actually invokes the `mas-cli manage " -"register-user` command under the hood. If you'd like more control over " -"the registration process, consider invoking the `mas-cli` command " -"directly:" +msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:" msgstr "" #: ../../../docs/registering-users.md:83 -msgid "" -"⚠️ **Warning**: Matrix Authentication Service [still " -"insists](https://github.com/element-hq/matrix-authentication-" -"service/issues/1505) on having a verified email address for each user. " -"Upon a user's first login, they will be asked to confirm their email " -"address. This requires that email sending is [configured](./configuring-" -"playbook-email.md). You can also consult the [Working around email " -"deliverability issues](./configuring-playbook-matrix-authentication-" -"service.md#working-around-email-deliverability-issues) section for more " -"information." +msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information." msgstr "" #: ../../../docs/registering-users.md:85 @@ -200,18 +141,11 @@ msgid "Managing users via a Web UI" msgstr "" #: ../../../docs/registering-users.md:87 -msgid "" -"To manage users more easily (via a web user-interace), you can install " -"[Synapse Admin](configuring-playbook-synapse-admin.md)." +msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)." msgstr "" #: ../../../docs/registering-users.md:89 -msgid "" -"⚠️ **Warning**: If you're using [Matrix Authentication Service" -"](configuring-playbook-matrix-authentication-service.md), note that user " -"management via synapse-admin is not fully working yet. See the " -"[Expectations](configuring-playbook-matrix-authentication-" -"service.md#expectations) section for more information." +msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information." msgstr "" #: ../../../docs/registering-users.md:91 @@ -219,12 +153,7 @@ msgid "Letting certain users register on your private server" msgstr "" #: ../../../docs/registering-users.md:93 -msgid "" -"If you'd rather **keep your server private** (public registration closed," -" as is the default), and **let certain people create accounts by " -"themselves** (instead of creating user accounts manually like this), " -"consider installing and making use of [matrix-registration](configuring-" -"playbook-matrix-registration.md)." +msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)." msgstr "" #: ../../../docs/registering-users.md:95 @@ -232,10 +161,7 @@ msgid "Enabling public user registration" msgstr "" #: ../../../docs/registering-users.md:97 -msgid "" -"To **open up user registration publicly** (usually **not recommended**), " -"add the following configuration to your " -"`inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/registering-users.md:99 @@ -247,31 +173,19 @@ msgid "For Dendrite:" msgstr "" #: ../../../docs/registering-users.md:111 -msgid "" -"After configuring the playbook, run it with [playbook tags](playbook-" -"tags.md) as below:" +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/registering-users.md:120 -msgid "" -"The shortcut commands with the [`just` program](just.md) are also " -"available: `just install-all` or `just setup-all`" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/registering-users.md:122 -msgid "" -"`just install-all` is useful for maintaining your setup quickly ([2x-5x " -"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-" -"runtime) than `just setup-all`) when its components remain unchanged. If " -"you adjust your `vars.yml` to remove other components, you'd need to run " -"`just setup-all`, or these components will still remain installed. Note " -"these shortcuts run the `ensure-matrix-users-created` tag too." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/registering-users.md:124 -msgid "" -"If you're opening up registrations publicly like this, you might also " -"wish to [configure CAPTCHA protection](configuring-captcha.md)." +msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)." msgstr "" #: ../../../docs/registering-users.md:126 @@ -283,9 +197,7 @@ msgid "Adding/Removing Administrator privileges to an existing user in Synapse" msgstr "" #: ../../../docs/registering-users.md:130 -msgid "" -"To change the admin privileges for a user in Synapse's local database, " -"you need to run an SQL query like this against the `synapse` database:" +msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:" msgstr "" #: ../../../docs/registering-users.md:136 @@ -301,16 +213,11 @@ msgid "`USER` and `example.com` pointing to a valid user on your server" msgstr "" #: ../../../docs/registering-users.md:141 -msgid "" -"If you're using the integrated Postgres server and not an [external " -"Postgres server](configuring-playbook-external-postgres.md), you can " -"launch a Postgres into the `synapse` database by:" +msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:" msgstr "" #: ../../../docs/registering-users.md:143 -msgid "" -"running `/matrix/postgres/bin/cli` - to launch " -"[`psql`](https://www.postgresql.org/docs/current/app-psql.html)" +msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)" msgstr "" #: ../../../docs/registering-users.md:144 @@ -322,28 +229,17 @@ msgid "You can then proceed to run the query above." msgstr "" #: ../../../docs/registering-users.md:148 -msgid "" -"**Note**: directly modifying the raw data of Synapse (or any other " -"software) could cause the software to break. You've been warned!" +msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!" msgstr "" #: ../../../docs/registering-users.md:150 -msgid "" -"Adding/Removing Administrator privileges to an existing user in Matrix " -"Authentication Service" +msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service" msgstr "" #: ../../../docs/registering-users.md:152 -msgid "" -"Promoting/demoting a user in Matrix Authentication Service cannot " -"currently (2024-10-19) be done via the [`mas-cli` Management tool" -"](./configuring-playbook-matrix-authentication-service.md#management)." +msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)." msgstr "" #: ../../../docs/registering-users.md:154 -msgid "" -"You can do it via the [MAS Admin API](https://element-hq.github.io" -"/matrix-authentication-service/api/index.html)'s `POST " -"/api/admin/v1/users/{id}/set-admin` endpoint." +msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/self-building.po b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po index 257ace6c6..1da0b78a1 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/self-building.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po @@ -25,34 +25,19 @@ msgid "Self-building" msgstr "" #: ../../../docs/self-building.md:3 -msgid "" -"**Caution: self-building does not have to be used on its own. See the " -"[Alternative Architectures](alternative-architectures.md) page.**" +msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**" msgstr "" #: ../../../docs/self-building.md:5 -msgid "" -"The playbook supports self-building of various components, which don't " -"have a container image for your architecture (see the [container images " -"we use](container-images.md)). For `amd64`, self-building is not " -"required." +msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required." msgstr "" #: ../../../docs/self-building.md:7 -msgid "" -"For other architectures (e.g. `arm32`, `arm64`), ready-made container " -"images are used when available. If there's no ready-made image for a " -"specific component and said component supports self-building, an image " -"will be built on the host. Building images like this takes more time and " -"resources (some build tools need to get installed by the playbook to " -"assist building)." +msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)." msgstr "" #: ../../../docs/self-building.md:9 -msgid "" -"To make use of self-building, you don't need to do anything. If a " -"component has an image for the specified architecture, the playbook will " -"use it directly. If not, it will build the image on the server itself." +msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself." msgstr "" #: ../../../docs/self-building.md:11 @@ -60,9 +45,7 @@ msgid "Note that **not all components support self-building yet**." msgstr "" #: ../../../docs/self-building.md:13 -msgid "" -"Possibly outdated list of roles where self-building the Docker image is " -"currently possible:" +msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:" msgstr "" #: ../../../docs/self-building.md:14 @@ -186,15 +169,9 @@ msgid "`matrix-pantalaimon`" msgstr "" #: ../../../docs/self-building.md:45 -msgid "" -"Adding self-building support to other roles is welcome. Feel free to " -"contribute!" +msgid "Adding self-building support to other roles is welcome. Feel free to contribute!" msgstr "" #: ../../../docs/self-building.md:47 -msgid "" -"If you'd like **to force self-building** even if an image is available " -"for your architecture, look into the `matrix_*_self_build` variables " -"provided by individual roles." +msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles." msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po index 7998ab8f0..826bd0919 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po @@ -29,18 +29,11 @@ msgid "**Warnings**:" msgstr "" #: ../../../docs/uninstalling.md:5 -msgid "" -"If your server federates with others, make sure to **leave any federated " -"rooms before nuking your Matrix server's data**. Otherwise, the next time" -" you set up a Matrix server for this domain (regardless of the " -"installation method you use), you'll encounter trouble federating." +msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating." msgstr "" #: ../../../docs/uninstalling.md:7 -msgid "" -"If you have some trouble with your installation, you can just [re-run the" -" playbook](installing.md) and it will try to set things up again. " -"**Uninstalling and then installing anew rarely solves anything**." +msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**." msgstr "" #: ../../../docs/uninstalling.md:11 @@ -52,9 +45,7 @@ msgid "Installing places a `/matrix/bin/remove-all` script on the server." msgstr "" #: ../../../docs/uninstalling.md:15 -msgid "" -"You can run it to to have it uninstall things for you automatically (see " -"below). **Use with caution!**" +msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**" msgstr "" #: ../../../docs/uninstalling.md:17 @@ -62,37 +53,23 @@ msgid "Uninstalling manually" msgstr "" #: ../../../docs/uninstalling.md:19 -msgid "" -"If you prefer to uninstall manually, run these commands (most are meant " -"to be executed on the Matrix server itself):" +msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):" msgstr "" #: ../../../docs/uninstalling.md:21 -msgid "" -"ensure all Matrix services are stopped: `ansible-playbook -i " -"inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working " -"to run this command, you can run `systemctl stop 'matrix*'` manually on " -"the server)" +msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)" msgstr "" #: ../../../docs/uninstalling.md:23 -msgid "" -"delete the Matrix-related systemd `.service` and `.timer` files (`rm -f " -"/etc/systemd/system/matrix*.{service,timer}`) and reload systemd " -"(`systemctl daemon-reload`)" +msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)" msgstr "" #: ../../../docs/uninstalling.md:25 -msgid "" -"delete some cached Docker images (`docker system prune -a`) or just " -"delete them all (`docker rmi $(docker images -aq)`)" +msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)" msgstr "" #: ../../../docs/uninstalling.md:27 -msgid "" -"delete the Docker networks: `docker network rm matrix matrix-coturn` " -"(might have been deleted already if you ran the `docker system prune` " -"command)" +msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)" msgstr "" #: ../../../docs/uninstalling.md:29 @@ -102,4 +79,3 @@ msgstr "" #: ../../../docs/uninstalling.md:31 msgid "delete the `/matrix` directory (`rm -rf /matrix`)" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po index ab02c7eee..e0720b62b 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po @@ -37,9 +37,7 @@ msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`" msgstr "" #: ../../../docs/updating-users-passwords.md:7 -msgid "" -"For `USERNAME_HERE`, use a plain username like `alice`, not a full ID " -"(`@alice:example.com`)" +msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)" msgstr "" #: ../../../docs/updating-users-passwords.md:9 @@ -47,9 +45,7 @@ msgid "You can reset a user's password via the Ansible playbook:" msgstr "" #: ../../../docs/updating-users-passwords.md:15 -msgid "" -"**You can then log in with that user** via Element Web that this playbook" -" has created for you at a URL like this: `https://element.example.com/`." +msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`." msgstr "" #: ../../../docs/updating-users-passwords.md:17 @@ -57,10 +53,7 @@ msgid "Option 2 (if you are using an external Postgres server):" msgstr "" #: ../../../docs/updating-users-passwords.md:19 -msgid "" -"You can manually generate the password hash by using the command-line " -"after **SSH**-ing to your server (requires that [all services have been " -"started](installing.md#finalize-the-installation):" +msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):" msgstr "" #: ../../../docs/updating-users-passwords.md:25 @@ -76,26 +69,15 @@ msgid "Option 3:" msgstr "" #: ../../../docs/updating-users-passwords.md:35 -msgid "" -"Use the Synapse User Admin API as described here: https://github.com" -"/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-" -"password" +msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password" msgstr "" #: ../../../docs/updating-users-passwords.md:37 -msgid "" -"This requires an [access token](obtaining-access-tokens.md) from a server" -" admin account. *This method will also log the user out of all of their " -"clients while the other options do not.*" +msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*" msgstr "" #: ../../../docs/updating-users-passwords.md:39 -msgid "" -"If you didn't make your account a server admin when you created it, you " -"can learn how to switch it now by reading about it in [Adding/Removing " -"Administrator privileges to an existing user in Synapse](registering-" -"users.md#addingremoving-administrator-privileges-to-an-existing-user-in-" -"synapse)." +msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)." msgstr "" #: ../../../docs/updating-users-passwords.md:41 @@ -103,8 +85,5 @@ msgid "Example:" msgstr "" #: ../../../docs/updating-users-passwords.md:43 -msgid "" -"To set @alice:example.com's password to `correct_horse_battery_staple` " -"you could use this curl command:" +msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:" msgstr "" - diff --git a/i18n/locales/jp/LC_MESSAGES/i18n/README.po b/i18n/locales/jp/LC_MESSAGES/i18n/README.po index 359b7173f..1707d7168 100644 --- a/i18n/locales/jp/LC_MESSAGES/i18n/README.po +++ b/i18n/locales/jp/LC_MESSAGES/i18n/README.po @@ -25,9 +25,7 @@ msgid "Internationalization" msgstr "" #: ../../README.md:3 -msgid "" -"Translated documentation files are published and maintained in " -"[`translated/`](translated/) directory." +msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." msgstr "" #: ../../README.md:5 @@ -39,9 +37,7 @@ msgid "Markdown files found at the top level project directory" msgstr "" #: ../../README.md:8 -msgid "" -"Markdown files found in the [`docs`](../docs/) directory (this is where " -"the bulk of the documentation is)" +msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" msgstr "" #: ../../README.md:9 @@ -49,11 +45,7 @@ msgid "this current document in the `i18n` directory" msgstr "" #: ../../README.md:11 -msgid "" -"💡 For readers' sake, we only [publish translations in a new language" -"](#publish-translations-in-a-new-language) when the translation " -"progresses beyond a certain threshold (requiring that at least the " -"project README and core installation guides are translated)." +msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." msgstr "" #: ../../README.md:13 @@ -61,37 +53,23 @@ msgid "Organization of this `i18n` directory is as follows:" msgstr "" #: ../../README.md:15 -msgid "" -"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we " -"publish translations for (in the [translated/](translated/) directory)" +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" msgstr "" #: ../../README.md:16 -msgid "" -"[.gitignore](.gitignore): a list of files and directories to ignore in " -"the `i18n` directory. We intentionaly ignore translated results " -"(`translated/` 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." +msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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:17 -msgid "" -"[justfile](justfile): a list of recipes for " -"[just](https://github.com/casey/just) command runner" +msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" msgstr "" #: ../../README.md:18 -msgid "" -"[requirements.txt](requirements.txt): a list of Python packages required " -"to work with translations" +msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" msgstr "" #: ../../README.md:19 -msgid "" -"[translation-templates/](translation-templates/): a list of English " -"translation templates - strings extracted from Markdown files" +msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" msgstr "" #: ../../README.md:20 @@ -99,10 +77,7 @@ msgid "[locales/](locales/): localization files for languages" msgstr "" #: ../../README.md:21 -msgid "" -"[translated/](translated/): translated documents for published languages " -"(see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations" -" in a new language](#publish-translations-in-a-new-language))" +msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" msgstr "" #: ../../README.md:23 @@ -110,24 +85,15 @@ msgid "Guide for translators" msgstr "" #: ../../README.md:25 -msgid "" -"This project uses [Sphinx](https://www.sphinx-doc.org/) to generate " -"translated documents." +msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." msgstr "" #: ../../README.md:27 -msgid "" -"For details about using Sphinx for translation, refer [this official " -"document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) " -"as well." +msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." msgstr "" #: ../../README.md:29 -msgid "" -"For now, translations are handled manually by editing `.po` files in the " -"`locales/` directory. In the future, we plan on integrating " -"with [Weblate](https://weblate.org/) to allow for translating from a web " -"interface." +msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." msgstr "" #: ../../README.md:31 @@ -135,20 +101,11 @@ msgid "(Recommended) Using the uv package manager and just command runner" msgstr "" #: ../../README.md:33 -msgid "" -"If you have the [uv](https://docs.astral.sh/uv/) package manager and " -"[just](https://github.com/casey/just) command runner installed, you can " -"use our [justfile](justfile) recipes to easily manage translation files " -"and build translated documents." +msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." msgstr "" #: ../../README.md:35 -msgid "" -"The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create" -" [a Python virtual " -"environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` " -"directory and install the required Python packages (as per " -"[requirements.txt](requirements.txt)) to it." +msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." msgstr "" #: ../../README.md:37 ../../README.md:64 @@ -156,9 +113,7 @@ msgid "Preparation" msgstr "" #: ../../README.md:39 -msgid "" -"Make sure you have the [uv](https://docs.astral.sh/uv/) package manager " -"and [just](https://github.com/casey/just) command runner installed." +msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." msgstr "" #: ../../README.md:41 ../../README.md:72 @@ -166,17 +121,11 @@ msgid "Translation" msgstr "" #: ../../README.md:43 ../../README.md:74 -msgid "" -"Recommended flow when working on a new language (replace `` " -"with the language code, e.g. `bg`):" +msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" msgstr "" #: ../../README.md:45 -msgid "" -"Update the locale files for your language: `just sync-for-language " -"` (internally, this automatically runs `just extract-" -"translation-templates` to make sure the translation templates are up-to-" -"date)" +msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" msgstr "" #: ../../README.md:47 ../../README.md:80 @@ -196,10 +145,7 @@ msgid "Commit your changes done to the `locales/` directory" msgstr "" #: ../../README.md:55 ../../README.md:88 -msgid "" -"If you have progressed with the translation beyond a certain threshold, " -"consider [Publishing translations in a new language](#publish-" -"translations-in-a-new-language)" +msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" msgstr "" #: ../../README.md:57 @@ -207,22 +153,15 @@ msgid "Using any other package manager and manual scripts" msgstr "" #: ../../README.md:59 -msgid "" -"If you cannot use [uv](https://docs.astral.sh/uv/) and/or " -"[just](https://github.com/casey/just), you can:" +msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" msgstr "" #: ../../README.md:61 -msgid "" -"manage Python packages in another way " -"([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-" -"poetry.org/), etc.)" +msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" msgstr "" #: ../../README.md:62 -msgid "" -"manage translation strings and build translated documents manually by " -"invoking scripts from the [bin](bin/) directory" +msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" msgstr "" #: ../../README.md:66 @@ -230,9 +169,7 @@ msgid "virtualenv and pip" msgstr "" #: ../../README.md:68 -msgid "" -"Create a Python virtual environment in the `.venv` directory: `virtualenv" -" .venv`" +msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" msgstr "" #: ../../README.md:69 @@ -240,22 +177,15 @@ msgid "Activate the virtual environment: `source .venv/bin/activate`" msgstr "" #: ../../README.md:70 -msgid "" -"Install the required Python packages using " -"[pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" +msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" msgstr "" #: ../../README.md:76 -msgid "" -"Ensure the English translation templates ([translation-templates" -"/](translation-templates/)) are extracted: `./bin/extract-translation-" -"templates.sh`" +msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" msgstr "" #: ../../README.md:78 -msgid "" -"Update the locale files for your language: `./bin/sync-translation-" -"templates-to-locales.sh `" +msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" msgstr "" #: ../../README.md:82 @@ -267,180 +197,17 @@ msgid "Publish translations in a new language" msgstr "" #: ../../README.md:92 -msgid "" -"To publish prebuilt documents translated in a new language to the " -"`translated/` directory:" +msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" msgstr "" #: ../../README.md:94 -msgid "" -"add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) " -"file" +msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" msgstr "" #: ../../README.md:95 -msgid "" -"whitelist its `translated/` directory by adding a " -"`!translated/` rule to the [.gitignore](.gitignore) file" +msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" msgstr "" #: ../../README.md:97 -msgid "" -"💡 Leave a trailing new line at the end of the " -"[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." +msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." msgstr "" - -#~ msgid "Translation guide" -#~ msgstr "" - -#~ msgid "" -#~ "If you are interested in translating " -#~ "this project, please check out our " -#~ "[Weblate project](https://example.com)." -#~ msgstr "" - -#~ msgid "" -#~ "If your language is not yet " -#~ "listed, please express your wishes to" -#~ " start translating it in our [Matrix" -#~ " room](https://matrix.to/#/#matrix-docker-ansible-" -#~ "deploy:devture.com). If anyone else is " -#~ "found to be working on your " -#~ "language, please co-ordinate if needed." -#~ msgstr "" - -#~ msgid "" -#~ "Currently, we manage translaion of " -#~ "markdown files on the top level " -#~ "directory and inside [`docs`](../docs/), and" -#~ " this file (`README.md`) only." -#~ msgstr "" - -#~ msgid "" -#~ "Translated files are published and " -#~ "maintained in [`markdown`](../markdown/) directory." -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ For readers' sake, we set a " -#~ "minimum condition for publishing documents " -#~ "translated in your language: translating " -#~ "basic articles such as READMEs, " -#~ "installation guides ([Quick start](quick-" -#~ "start.md) and the full installation " -#~ "guide which starts at the " -#~ "[Prerequisites](prerequisites.md)), etc. If you " -#~ "think we have missed progress of " -#~ "translation in your language, please " -#~ "ping us at the Matrix room." -#~ msgstr "" - -#~ msgid "Translation development guide" -#~ msgstr "" - -#~ msgid "Install packages" -#~ msgstr "" - -#~ msgid "" -#~ "To manage files for translation and " -#~ "build translated documents, you need to" -#~ " install packages at first. You can" -#~ " install them with " -#~ "[pip](https://pip.pypa.io/en/stable/)." -#~ msgstr "" - -#~ msgid "" -#~ "After installing pip and activating the" -#~ " virtual environment, run the command " -#~ "below on this directory:" -#~ msgstr "" - -#~ msgid "Update PO files" -#~ msgstr "" - -#~ msgid "" -#~ "If a document is updated, it is" -#~ " necessary to generate updated `.pot` " -#~ "(catalog templates) files and to apply" -#~ " differences to translated `.po` (message" -#~ " catalogs) files." -#~ msgstr "" - -#~ msgid "To do so, run these commands:" -#~ msgstr "" - -#~ msgid "" -#~ "To generate `.po` files for a new" -#~ " language, e.g. Bulgarian, run the " -#~ "command below:" -#~ msgstr "" - -#~ msgid "" -#~ "After the original documents have " -#~ "changed, run [i18n_update.sh](i18n_update.sh) to " -#~ "update `.po` files in all languages " -#~ "specified on [`LANG`](LANG) file:" -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ Unless your language code is " -#~ "added to the `LANG` file, running " -#~ "the script does not generate `.po` " -#~ "files in your language in `locales` " -#~ "directory." -#~ msgstr "" - -#~ msgid "Build" -#~ msgstr "" - -#~ msgid "To build the documentation in English, run the command below:" -#~ msgstr "" - -#~ msgid "It generates Markdown files in `_build/markdown/`." -#~ msgstr "" - -#~ msgid "" -#~ "ℹ️ As the original documents are " -#~ "also Markdown files, the generated files" -#~ " in English are identical to the " -#~ "original ones." -#~ msgstr "" - -#~ msgid "To build documents in another language, e.g. Bulgarian, run:" -#~ msgstr "" - -#~ msgid "" -#~ "Running [i18n_build.sh](i18n_build.sh) builds " -#~ "Markdown files in all languages " -#~ "specified on `LANG` file into `markdown`" -#~ " directory:" -#~ msgstr "" - -#~ msgid "Publish documents in a new language" -#~ msgstr "" - -#~ msgid "" -#~ "To publish documents translated in a " -#~ "new language on `markdown` directory, " -#~ "add its language code to `LANG` " -#~ "file. Then, run `i18n_update.sh` and " -#~ "`i18n_build.sh`. After that, you would " -#~ "need to push the documents to the" -#~ " repository." -#~ msgstr "" - -#~ msgid "💡 Leave an empty line at the end of the `LANG` file." -#~ msgstr "" - -#~ msgid "Using the uv package manager and just command runner" -#~ msgstr "" - -#~ msgid "" -#~ "Update the locale files for your " -#~ "language: `just sync-language ` " -#~ "(internally, this automatically runs `just " -#~ "extract-translation-templates` to make " -#~ "sure the translation templates are " -#~ "up-to-date)" -#~ msgstr "" - From c51e771d1af204e651c81fc906f78f964afefabf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 20 Dec 2024 21:26:48 +0900 Subject: [PATCH 125/952] =?UTF-8?q?Change=20"translated"=20=E2=86=92=20"tr?= =?UTF-8?q?anslations"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I think we might as well to use the word "translations" on this context. Signed-off-by: Suguru Hirahara --- i18n/.gitignore | 2 +- i18n/README.md | 16 ++++++++-------- i18n/bin/build-translated-result.sh | 13 +++++++------ i18n/justfile | 7 ++++--- i18n/translation-templates/i18n/README.pot | 14 +++++++------- 5 files changed, 27 insertions(+), 25 deletions(-) diff --git a/i18n/.gitignore b/i18n/.gitignore index 78794379d..dcb737746 100644 --- a/i18n/.gitignore +++ b/i18n/.gitignore @@ -3,4 +3,4 @@ doctrees .doctrees/ /**/*.mo -/translated/* +/translations/* diff --git a/i18n/README.md b/i18n/README.md index 93e99ad8e..94cf013e4 100644 --- a/i18n/README.md +++ b/i18n/README.md @@ -7,7 +7,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Internationalization -Translated documentation files are published and maintained in [`translated/`](translated/) directory. +Translated documentation files are published and maintained in [`translations/`](translations/) directory. Currently, we support translation of: @@ -19,13 +19,13 @@ Currently, we support translation of: Organization of this `i18n` directory is as follows: -- [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory) -- [.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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. +- [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory) +- [.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold. - [justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner - [requirements.txt](requirements.txt): a list of Python packages required to work with translations - [translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files - [locales/](locales/): localization files for languages -- [translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language)) +- [translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language)) ## Guide for translators @@ -55,7 +55,7 @@ Recommended flow when working on a new language (replace `` with the l - Build translated documents: `just build-for-language ` -- Preview the result in the `translated/` directory +- Preview the result in the `translations/` directory - Commit your changes done to the `locales/` directory @@ -88,7 +88,7 @@ Recommended flow when working on a new language (replace `` with the l - Build translated documents: `./bin/build-translated-result.sh ` -- Preview the result in the `translated/` directory +- Preview the result in the `translations/` directory - Commit your changes done to the `locales/` directory @@ -96,9 +96,9 @@ Recommended flow when working on a new language (replace `` with the l ### Publish translations in a new language -To publish prebuilt documents translated in a new language to the `translated/` directory: +To publish prebuilt documents translated in a new language to the `translations/` directory: - add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file -- whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file +- whitelist its `translations/` directory by adding a `!translations/` rule to the [.gitignore](.gitignore) file 💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file. diff --git a/i18n/bin/build-translated-result.sh b/i18n/bin/build-translated-result.sh index d918100d3..b55f3d823 100755 --- a/i18n/bin/build-translated-result.sh +++ b/i18n/bin/build-translated-result.sh @@ -1,10 +1,11 @@ #!/bin/bash # SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later -# This script builds the translated result (translated project) for a given language in the `translated//` directory. +# This script builds the translated result (translated project) for a given language in the `translations//` directory. set -euxo pipefail @@ -47,14 +48,14 @@ rm -rf ${base_path}/i18n/translated-result-build-${LANGUAGE}/.doctrees cp -r ${base_path}/docs/assets ${base_path}/i18n/translated-result-build-${LANGUAGE}/docs/assets/ # Remove the old result directory for this language -if [ -d ${base_path}/i18n/translated/${LANGUAGE} ]; then - rm -rf ${base_path}/i18n/translated/${LANGUAGE} +if [ -d ${base_path}/i18n/translations/${LANGUAGE} ]; then + rm -rf ${base_path}/i18n/translations/${LANGUAGE} fi -# Make sure the `translated/` directory exists +# Make sure the `translations/` directory exists if [ ! -d ${base_path}/i18n/translated ]; then mkdir -p ${base_path}/i18n/translated fi -# Relocate the built result to translated/ -mv ${base_path}/i18n/translated-result-build-${LANGUAGE} ${base_path}/i18n/translated/${LANGUAGE} +# Relocate the built result to translations/ +mv ${base_path}/i18n/translated-result-build-${LANGUAGE} ${base_path}/i18n/translations/${LANGUAGE} diff --git a/i18n/justfile b/i18n/justfile index d33f2cd61..a3936e7e9 100644 --- a/i18n/justfile +++ b/i18n/justfile @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -34,18 +35,18 @@ sync-for-language language: extract-translation-templates (_sync-translation-tem _sync-translation-templates-to-locales-for-language language: _venv PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/sync-translation-templates-to-locales.sh {{ language }} -# Builds the translated result for a given language into the `translated/{{ language }}` directory +# Builds the translated result for a given language into the `translations/{{ language }}` directory build-for-language language: _venv PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/build-translated-result.sh {{ language }} -# Builds the translated result for all published languages into the `translated/` directory +# Builds the translated result for all published languages into the `translations/` directory build-for-all-published-languages: #!/bin/sh cat {{ justfile_directory() }}/PUBLISHED_LANGUAGES | while read language ; do {{ just_executable() }} build-for-language $language done -# Builds the translated result for all known languages into the `translated/` directory +# Builds the translated result for all known languages into the `translations/` directory build-for-all-known-languages: #!/bin/sh find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do diff --git a/i18n/translation-templates/i18n/README.pot b/i18n/translation-templates/i18n/README.pot index 929792829..880598c2f 100644 --- a/i18n/translation-templates/i18n/README.pot +++ b/i18n/translation-templates/i18n/README.pot @@ -21,7 +21,7 @@ msgid "Internationalization" msgstr "" #: ../../README.md:3 -msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." +msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory." msgstr "" #: ../../README.md:5 @@ -49,11 +49,11 @@ msgid "Organization of this `i18n` directory is as follows:" msgstr "" #: ../../README.md:15 -msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)" msgstr "" #: ../../README.md:16 -msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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." +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:17 @@ -73,7 +73,7 @@ msgid "[locales/](locales/): localization files for languages" msgstr "" #: ../../README.md:21 -msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" msgstr "" #: ../../README.md:23 @@ -138,7 +138,7 @@ msgstr "" #: ../../README.md:51 #: ../../README.md:84 -msgid "Preview the result in the `translated/` directory" +msgid "Preview the result in the `translations/` directory" msgstr "" #: ../../README.md:53 @@ -200,7 +200,7 @@ msgid "Publish translations in a new language" msgstr "" #: ../../README.md:92 -msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" +msgid "To publish prebuilt documents translated in a new language to the `translations/` directory:" msgstr "" #: ../../README.md:94 @@ -208,7 +208,7 @@ msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) f msgstr "" #: ../../README.md:95 -msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" +msgid "whitelist its `translations/` directory by adding a `!translations/` rule to the [.gitignore](.gitignore) file" msgstr "" #: ../../README.md:97 From 9cbb6fd548ecca7231cd61b3abdc6e1c0d95e3a7 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 14:55:29 +0200 Subject: [PATCH 126/952] Translate a few main README strings to Bulgarian --- i18n/locales/bg/LC_MESSAGES/README.po | 38 +++++++++++++-------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/i18n/locales/bg/LC_MESSAGES/README.po b/i18n/locales/bg/LC_MESSAGES/README.po index 06e8535f1..653a76b8b 100644 --- a/i18n/locales/bg/LC_MESSAGES/README.po +++ b/i18n/locales/bg/LC_MESSAGES/README.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-12-20 09:53+0200\n" -"PO-Revision-Date: 2024-12-20 14:33+0200\n" +"PO-Revision-Date: 2024-12-20 14:56+0200\n" "Last-Translator: \n" "Language-Team: bg \n" "Language: bg\n" @@ -32,11 +32,11 @@ msgstr "Matrix стая за поддръжка" #: ../../../README.md:1 msgid "donate" -msgstr "" +msgstr "дарения" #: ../../../README.md:3 msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker" -msgstr "" +msgstr "Настройка на Matrix (отворена мрежа за сигурна децентрализирана комуникация) чрез Ansible и Docker" #: ../../../README.md:5 msgid "🎯 Purpose" @@ -44,27 +44,27 @@ msgstr "🎯 Цел" #: ../../../README.md:7 msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that." -msgstr "Този наръчник [Ansible](https://www.ansible.com/) има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#supported-services), свързани с това." +msgstr "Този [Ansible](https://www.ansible.com/) плейбук има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#-поддържани-услуги) около него." #: ../../../README.md:9 msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))." -msgstr "" +msgstr "С други думи, позволява ви да се присъедините към Matrix мрежата със собствен сървър (вижте [предварителни условия](docs/prerequisites.md)) използвайки потребителско име като `@alice:example.com`." #: ../../../README.md:11 msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)." -msgstr "" +msgstr "Подкарваме всички [поддържани услуги](#-поддържани-услуги) в [Docker](https://www.docker.com/) контейнери (вижте [използваните контейнер image-и](docs/container-images.md)), което ни позволява да имаме предсказуема и в крак с времето инсталация, без значение от операционната система (вижте [предварителните условия](docs/prerequisites.md)) и [архитектура](docs/alternative-architectures.md) (препоръчва се x86/amd64)." #: ../../../README.md:13 msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))." -msgstr "" +msgstr "Инсталацията (обновленията) и някои задачи по поддръжката са автоматизирани чрез [Ansible](https://www.ansible.com/) (вижте [нашия Ansible наръчник](docs/ansible.md))." #: ../../../README.md:15 msgid "☁ Self-hosting or Managed / SaaS" -msgstr "" +msgstr "☁ Самостоятелно хостване или Управлявано / SaaS" #: ../../../README.md:17 msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort." -msgstr "" +msgstr "Този Ansible плейбук се стреми да направи самостоятелното хостване и поддръжка на Matrix сървър лесно (вижте [Стартиране](#-стартиране)). Въпреки това, поддържането на коя да е услуга изисква знания, време и усилия." #: ../../../README.md:19 msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option." @@ -104,7 +104,7 @@ msgstr "" #: ../../../README.md:37 msgid "✔ Supported services" -msgstr "" +msgstr "✔ Поддържани услуги" #: ../../../README.md:39 msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else." @@ -160,11 +160,11 @@ msgstr "" #: ../../../README.md msgid "[Link](docs/configuring-playbook-synapse.md)" -msgstr "" +msgstr "[Връзка](docs/configuring-playbook-synapse.md)" #: ../../../README.md msgid "[Conduit](https://conduit.rs)" -msgstr "" +msgstr "[Conduit](https://conduit.rs)" #: ../../../README.md msgid "❌" @@ -176,7 +176,7 @@ msgstr "" #: ../../../README.md msgid "[Link](docs/configuring-playbook-conduit.md)" -msgstr "" +msgstr "[Връзка](docs/configuring-playbook-conduit.md)" #: ../../../README.md msgid "[Dendrite](https://github.com/matrix-org/dendrite)" @@ -256,7 +256,7 @@ msgstr "" #: ../../../README.md msgid "[PostgreSQL](https://www.postgresql.org/)" -msgstr "" +msgstr "[PostgreSQL](https://www.postgresql.org/)" #: ../../../README.md msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible." @@ -336,7 +336,7 @@ msgstr "" #: ../../../README.md msgid "[Link](docs/configuring-playbook-dynamic-dns.md)" -msgstr "" +msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)" #: ../../../README.md:82 msgid "Authentication" @@ -416,7 +416,7 @@ msgstr "" #: ../../../README.md msgid "[Link](docs/configuring-playbook-user-verification-service.md)" -msgstr "" +msgstr "[Връзка](docs/configuring-playbook-user-verification-service.md)" #: ../../../README.md msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)" @@ -1136,7 +1136,7 @@ msgstr "" #: ../../../README.md:189 msgid "This playbook evolves over time, sometimes with backward-incompatible changes." -msgstr "" +msgstr "Този плейбук се развива във времето и понякога съдържа обратно-несъвместими промени." #: ../../../README.md:191 msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new." @@ -1164,11 +1164,11 @@ msgstr "" #: ../../../README.md:203 msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation." -msgstr "" +msgstr "Вижте файла [i18n/README.md](i18n/README.md) за повече информация относно превода." #: ../../../README.md:205 msgid "Translations are still work in progress." -msgstr "" +msgstr "Все още се работи по преводите." #: ../../../README.md:207 msgid "🤝 Related" From 25601d96a7bb087c3baac7f40b1916cc49435fbf Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 15:26:07 +0200 Subject: [PATCH 127/952] Translate a few main quick-start strings to Bulgarian --- .../bg/LC_MESSAGES/docs/quick-start.po | 71 ++++++++++--------- 1 file changed, 36 insertions(+), 35 deletions(-) diff --git a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po index 5bec8b522..c92e29a4e 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po @@ -8,62 +8,63 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Project-Id-Version: matrix-docker-ansible-deploy\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-12-16 12:05+0900\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language: bg\n" +"PO-Revision-Date: 2024-12-20 15:23+0200\n" +"Last-Translator: \n" "Language-Team: bg \n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"Language: bg\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "Generated-By: Babel 2.16.0\n" +"X-Generator: Poedit 3.4.2\n" #: ../../../docs/quick-start.md:1 msgid "Quick start" -msgstr "" +msgstr "Бърза инсталация" #: ../../../docs/quick-start.md:9 msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services." -msgstr "" +msgstr "Тази страница показва как да използвате Ansible плейбука за да инсталирате минимален брой от важните Matrix услуги на ваш собствен сървър." #: ../../../docs/quick-start.md:11 msgid "We will be using `example.com` as the \"base domain\" in the following instruction." -msgstr "" +msgstr "Ще използваме `example.com` като \"базов домейн\" в инструкциите по-долу." #: ../../../docs/quick-start.md:13 msgid "By following the instruction on this page, you will set up:" -msgstr "" +msgstr "Следвайки инструкциите на тази страница, ще настройте:" #: ../../../docs/quick-start.md:15 msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`" -msgstr "" +msgstr "**ваш собствен Matrix сървър** на `matrix.example.com` сървъра, който е настроен да се представя за `example.com`" #: ../../../docs/quick-start.md:16 msgid "**your user account** like `@alice:example.com` on the server" -msgstr "" +msgstr "**ваш потребителски профил** като `@alice:example.com` на сървъра" #: ../../../docs/quick-start.md:17 msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`" -msgstr "" +msgstr "**самостоятелно-хостван Matrix клиент**, [Element Web](configuring-playbook-client-element-web.md) на поддомейн по подразбиране `element.example.com`" #: ../../../docs/quick-start.md:18 msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network" -msgstr "" +msgstr "Matrix делегиране, така че `matrix.example.com` сървърът ви (представящ се за `example.com`) да може да се включи в Matrix Федерацията и да комуникира с други сървъри в Matrix мрежата" #: ../../../docs/quick-start.md:20 msgid "Please remember to replace `example.com` with your own domain before running any commands." -msgstr "" +msgstr "Моля, помнете да замените `example.com` със собствения си домейн преди да изпълните командите по-долу." #: ../../../docs/quick-start.md:22 msgid "Prerequisites" -msgstr "" +msgstr "Предварителни условия" #: ../../../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 "" +msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Предварителни условия](prerequisites.md)" #: ../../../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)." @@ -87,7 +88,7 @@ msgstr "" #: ../../../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 "" +msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на DNS настройките](configuring-dns.md)" #: ../../../docs/quick-start.md:42 msgid "After installing and configuring prerequisites, you will need to **configure DNS records**." @@ -99,63 +100,63 @@ msgstr "" #: ../../../docs/quick-start.md msgid "Type" -msgstr "" +msgstr "Тип" #: ../../../docs/quick-start.md msgid "Host" -msgstr "" +msgstr "Домейн" #: ../../../docs/quick-start.md msgid "Priority" -msgstr "" +msgstr "Приоритет" #: ../../../docs/quick-start.md msgid "Weight" -msgstr "" +msgstr "Тегло" #: ../../../docs/quick-start.md msgid "Port" -msgstr "" +msgstr "Порт" #: ../../../docs/quick-start.md msgid "Target" -msgstr "" +msgstr "Цел" #: ../../../docs/quick-start.md msgid "A" -msgstr "" +msgstr "A" #: ../../../docs/quick-start.md msgid "`matrix`" -msgstr "" +msgstr "`matrix`" #: ../../../docs/quick-start.md msgid "-" -msgstr "" +msgstr "-" #: ../../../docs/quick-start.md msgid "`matrix-server-IP`" -msgstr "" +msgstr "`IP-на-matrix-сървъра`" #: ../../../docs/quick-start.md msgid "CNAME" -msgstr "" +msgstr "CNAME" #: ../../../docs/quick-start.md msgid "`element`" -msgstr "" +msgstr "`element`" #: ../../../docs/quick-start.md msgid "`matrix.example.com`" -msgstr "" +msgstr "`matrix.example.com`" #: ../../../docs/quick-start.md:51 msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)." -msgstr "" +msgstr "Както показва таблицата, необходимо е да създадете 2 поддомейна (`matrix.example.com` и `element.example.com`) и да ги насочите към IP адреса на сървъра (чрез DNS `A` запис или `CNAME` запис)." #: ../../../docs/quick-start.md:53 msgid "It might take some time for the DNS records to propagate after creation." -msgstr "" +msgstr "Може да отнеме известно време след създаване на DNS записите докато се отразят." #: ../../../docs/quick-start.md:55 msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\"" @@ -167,7 +168,7 @@ msgstr "" #: ../../../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 "" +msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Изтегляне на плейбука](getting-the-playbook.md)" #: ../../../docs/quick-start.md:61 msgid "Next, let's **get the playbook's source code**." @@ -191,7 +192,7 @@ msgstr "" #: ../../../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 "" +msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на плейбука](configuring-playbook.md)" #: ../../../docs/quick-start.md:77 msgid "Now that the playbook was fetched, it is time to **configure** it per your needs." @@ -255,7 +256,7 @@ msgstr "" #: ../../../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 "" +msgstr "Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Инсталиране](installing.md)" #: ../../../docs/quick-start.md:102 msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure." From a146f2199b4d5540d374bf3d91a2b996527c1e8f Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 15:27:31 +0200 Subject: [PATCH 128/952] Fix old directory name in i18n/bin/build-translated-result.sh Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3891 --- i18n/bin/build-translated-result.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/bin/build-translated-result.sh b/i18n/bin/build-translated-result.sh index b55f3d823..0f860fe7f 100755 --- a/i18n/bin/build-translated-result.sh +++ b/i18n/bin/build-translated-result.sh @@ -53,8 +53,8 @@ if [ -d ${base_path}/i18n/translations/${LANGUAGE} ]; then fi # Make sure the `translations/` directory exists -if [ ! -d ${base_path}/i18n/translated ]; then - mkdir -p ${base_path}/i18n/translated +if [ ! -d ${base_path}/i18n/translations ]; then + mkdir -p ${base_path}/i18n/translations fi # Relocate the built result to translations/ From 23bcf87596018d8e37d81705d1fbba912599086d Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 20 Dec 2024 15:28:26 +0200 Subject: [PATCH 129/952] Sync translation locales --- i18n/locales/bg/LC_MESSAGES/i18n/README.po | 142 ++++++++++----------- i18n/locales/jp/LC_MESSAGES/i18n/README.po | 142 ++++++++++----------- i18n/translation-templates/i18n/README.pot | 112 ++++++++-------- 3 files changed, 198 insertions(+), 198 deletions(-) diff --git a/i18n/locales/bg/LC_MESSAGES/i18n/README.po b/i18n/locales/bg/LC_MESSAGES/i18n/README.po index 72a8111ae..c5e6d158e 100644 --- a/i18n/locales/bg/LC_MESSAGES/i18n/README.po +++ b/i18n/locales/bg/LC_MESSAGES/i18n/README.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-20 09:29+0200\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" @@ -17,194 +17,194 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.16.0\n" -#: ../../README.md:1 +#: ../../README.md:8 msgid "Internationalization" msgstr "" -#: ../../README.md:3 -msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." +#: ../../README.md:10 +msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory." msgstr "" -#: ../../README.md:5 +#: ../../README.md:12 msgid "Currently, we support translation of:" msgstr "" -#: ../../README.md:7 +#: ../../README.md:14 msgid "Markdown files found at the top level project directory" msgstr "" -#: ../../README.md:8 +#: ../../README.md:15 msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" msgstr "" -#: ../../README.md:9 +#: ../../README.md:16 msgid "this current document in the `i18n` directory" msgstr "" -#: ../../README.md:11 +#: ../../README.md:18 msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." msgstr "" -#: ../../README.md:13 +#: ../../README.md:20 msgid "Organization of this `i18n` directory is as follows:" msgstr "" -#: ../../README.md:15 -msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" -msgstr "" - -#: ../../README.md:16 -msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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:17 -msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" -msgstr "" - -#: ../../README.md:18 -msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" -msgstr "" - -#: ../../README.md:19 -msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" -msgstr "" - -#: ../../README.md:20 -msgid "[locales/](locales/): localization files for languages" -msgstr "" - -#: ../../README.md:21 -msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +#: ../../README.md:22 +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)" msgstr "" #: ../../README.md:23 -msgid "Guide for translators" +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 +msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" msgstr "" #: ../../README.md:25 -msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." +msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" +msgstr "" + +#: ../../README.md:26 +msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" msgstr "" #: ../../README.md:27 +msgid "[locales/](locales/): localization files for languages" +msgstr "" + +#: ../../README.md:28 +msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +msgstr "" + +#: ../../README.md:30 +msgid "Guide for translators" +msgstr "" + +#: ../../README.md:32 +msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." +msgstr "" + +#: ../../README.md:34 msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." msgstr "" -#: ../../README.md:29 +#: ../../README.md:36 msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." msgstr "" -#: ../../README.md:31 +#: ../../README.md:38 msgid "(Recommended) Using the uv package manager and just command runner" msgstr "" -#: ../../README.md:33 +#: ../../README.md:40 msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." msgstr "" -#: ../../README.md:35 +#: ../../README.md:42 msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." msgstr "" -#: ../../README.md:37 ../../README.md:64 +#: ../../README.md:44 ../../README.md:71 msgid "Preparation" msgstr "" -#: ../../README.md:39 +#: ../../README.md:46 msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." msgstr "" -#: ../../README.md:41 ../../README.md:72 +#: ../../README.md:48 ../../README.md:79 msgid "Translation" msgstr "" -#: ../../README.md:43 ../../README.md:74 +#: ../../README.md:50 ../../README.md:81 msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" msgstr "" -#: ../../README.md:45 +#: ../../README.md:52 msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" msgstr "" -#: ../../README.md:47 ../../README.md:80 +#: ../../README.md:54 ../../README.md:87 msgid "Use an editor to translate the files in the `locales/` directory" msgstr "" -#: ../../README.md:49 +#: ../../README.md:56 msgid "Build translated documents: `just build-for-language `" msgstr "" -#: ../../README.md:51 ../../README.md:84 -msgid "Preview the result in the `translated/` directory" +#: ../../README.md:58 ../../README.md:91 +msgid "Preview the result in the `translations/` directory" msgstr "" -#: ../../README.md:53 ../../README.md:86 +#: ../../README.md:60 ../../README.md:93 msgid "Commit your changes done to the `locales/` directory" msgstr "" -#: ../../README.md:55 ../../README.md:88 +#: ../../README.md:62 ../../README.md:95 msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" msgstr "" -#: ../../README.md:57 +#: ../../README.md:64 msgid "Using any other package manager and manual scripts" msgstr "" -#: ../../README.md:59 +#: ../../README.md:66 msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" msgstr "" -#: ../../README.md:61 +#: ../../README.md:68 msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" msgstr "" -#: ../../README.md:62 +#: ../../README.md:69 msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" msgstr "" -#: ../../README.md:66 +#: ../../README.md:73 msgid "virtualenv and pip" msgstr "" -#: ../../README.md:68 +#: ../../README.md:75 msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" msgstr "" -#: ../../README.md:69 +#: ../../README.md:76 msgid "Activate the virtual environment: `source .venv/bin/activate`" msgstr "" -#: ../../README.md:70 +#: ../../README.md:77 msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" msgstr "" -#: ../../README.md:76 +#: ../../README.md:83 msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" msgstr "" -#: ../../README.md:78 +#: ../../README.md:85 msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" msgstr "" -#: ../../README.md:82 +#: ../../README.md:89 msgid "Build translated documents: `./bin/build-translated-result.sh `" msgstr "" -#: ../../README.md:90 +#: ../../README.md:97 msgid "Publish translations in a new language" msgstr "" -#: ../../README.md:92 -msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" +#: ../../README.md:99 +msgid "To publish prebuilt documents translated in a new language to the `translations/` directory:" msgstr "" -#: ../../README.md:94 +#: ../../README.md:101 msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" msgstr "" -#: ../../README.md:95 -msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" +#: ../../README.md:102 +msgid "whitelist its `translations/` directory by adding a `!translations/` rule to the [.gitignore](.gitignore) file" msgstr "" -#: ../../README.md:97 +#: ../../README.md:104 msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/i18n/README.po b/i18n/locales/jp/LC_MESSAGES/i18n/README.po index 1707d7168..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: 2024-12-20 09:29+0200\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" @@ -20,194 +20,194 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.16.0\n" -#: ../../README.md:1 +#: ../../README.md:8 msgid "Internationalization" msgstr "" -#: ../../README.md:3 -msgid "Translated documentation files are published and maintained in [`translated/`](translated/) directory." +#: ../../README.md:10 +msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory." msgstr "" -#: ../../README.md:5 +#: ../../README.md:12 msgid "Currently, we support translation of:" msgstr "" -#: ../../README.md:7 +#: ../../README.md:14 msgid "Markdown files found at the top level project directory" msgstr "" -#: ../../README.md:8 +#: ../../README.md:15 msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" msgstr "" -#: ../../README.md:9 +#: ../../README.md:16 msgid "this current document in the `i18n` directory" msgstr "" -#: ../../README.md:11 +#: ../../README.md:18 msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." msgstr "" -#: ../../README.md:13 +#: ../../README.md:20 msgid "Organization of this `i18n` directory is as follows:" msgstr "" -#: ../../README.md:15 -msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translated/](translated/) directory)" -msgstr "" - -#: ../../README.md:16 -msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translated/` 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:17 -msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" -msgstr "" - -#: ../../README.md:18 -msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" -msgstr "" - -#: ../../README.md:19 -msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" -msgstr "" - -#: ../../README.md:20 -msgid "[locales/](locales/): localization files for languages" -msgstr "" - -#: ../../README.md:21 -msgid "[translated/](translated/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +#: ../../README.md:22 +msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)" msgstr "" #: ../../README.md:23 -msgid "Guide for translators" +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 +msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" msgstr "" #: ../../README.md:25 -msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." +msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" +msgstr "" + +#: ../../README.md:26 +msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" msgstr "" #: ../../README.md:27 +msgid "[locales/](locales/): localization files for languages" +msgstr "" + +#: ../../README.md:28 +msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" +msgstr "" + +#: ../../README.md:30 +msgid "Guide for translators" +msgstr "" + +#: ../../README.md:32 +msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." +msgstr "" + +#: ../../README.md:34 msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." msgstr "" -#: ../../README.md:29 +#: ../../README.md:36 msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." msgstr "" -#: ../../README.md:31 +#: ../../README.md:38 msgid "(Recommended) Using the uv package manager and just command runner" msgstr "" -#: ../../README.md:33 +#: ../../README.md:40 msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." msgstr "" -#: ../../README.md:35 +#: ../../README.md:42 msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." msgstr "" -#: ../../README.md:37 ../../README.md:64 +#: ../../README.md:44 ../../README.md:71 msgid "Preparation" msgstr "" -#: ../../README.md:39 +#: ../../README.md:46 msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." msgstr "" -#: ../../README.md:41 ../../README.md:72 +#: ../../README.md:48 ../../README.md:79 msgid "Translation" msgstr "" -#: ../../README.md:43 ../../README.md:74 +#: ../../README.md:50 ../../README.md:81 msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" msgstr "" -#: ../../README.md:45 +#: ../../README.md:52 msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" msgstr "" -#: ../../README.md:47 ../../README.md:80 +#: ../../README.md:54 ../../README.md:87 msgid "Use an editor to translate the files in the `locales/` directory" msgstr "" -#: ../../README.md:49 +#: ../../README.md:56 msgid "Build translated documents: `just build-for-language `" msgstr "" -#: ../../README.md:51 ../../README.md:84 -msgid "Preview the result in the `translated/` directory" +#: ../../README.md:58 ../../README.md:91 +msgid "Preview the result in the `translations/` directory" msgstr "" -#: ../../README.md:53 ../../README.md:86 +#: ../../README.md:60 ../../README.md:93 msgid "Commit your changes done to the `locales/` directory" msgstr "" -#: ../../README.md:55 ../../README.md:88 +#: ../../README.md:62 ../../README.md:95 msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" msgstr "" -#: ../../README.md:57 +#: ../../README.md:64 msgid "Using any other package manager and manual scripts" msgstr "" -#: ../../README.md:59 +#: ../../README.md:66 msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" msgstr "" -#: ../../README.md:61 +#: ../../README.md:68 msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" msgstr "" -#: ../../README.md:62 +#: ../../README.md:69 msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" msgstr "" -#: ../../README.md:66 +#: ../../README.md:73 msgid "virtualenv and pip" msgstr "" -#: ../../README.md:68 +#: ../../README.md:75 msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" msgstr "" -#: ../../README.md:69 +#: ../../README.md:76 msgid "Activate the virtual environment: `source .venv/bin/activate`" msgstr "" -#: ../../README.md:70 +#: ../../README.md:77 msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" msgstr "" -#: ../../README.md:76 +#: ../../README.md:83 msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" msgstr "" -#: ../../README.md:78 +#: ../../README.md:85 msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" msgstr "" -#: ../../README.md:82 +#: ../../README.md:89 msgid "Build translated documents: `./bin/build-translated-result.sh `" msgstr "" -#: ../../README.md:90 +#: ../../README.md:97 msgid "Publish translations in a new language" msgstr "" -#: ../../README.md:92 -msgid "To publish prebuilt documents translated in a new language to the `translated/` directory:" +#: ../../README.md:99 +msgid "To publish prebuilt documents translated in a new language to the `translations/` directory:" msgstr "" -#: ../../README.md:94 +#: ../../README.md:101 msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" msgstr "" -#: ../../README.md:95 -msgid "whitelist its `translated/` directory by adding a `!translated/` rule to the [.gitignore](.gitignore) file" +#: ../../README.md:102 +msgid "whitelist its `translations/` directory by adding a `!translations/` rule to the [.gitignore](.gitignore) file" msgstr "" -#: ../../README.md:97 +#: ../../README.md:104 msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." msgstr "" diff --git a/i18n/translation-templates/i18n/README.pot b/i18n/translation-templates/i18n/README.pot index 880598c2f..4f94ba62b 100644 --- a/i18n/translation-templates/i18n/README.pot +++ b/i18n/translation-templates/i18n/README.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:29+0200\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" @@ -16,201 +16,201 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../README.md:1 +#: ../../README.md:8 msgid "Internationalization" msgstr "" -#: ../../README.md:3 +#: ../../README.md:10 msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory." msgstr "" -#: ../../README.md:5 +#: ../../README.md:12 msgid "Currently, we support translation of:" msgstr "" -#: ../../README.md:7 +#: ../../README.md:14 msgid "Markdown files found at the top level project directory" msgstr "" -#: ../../README.md:8 +#: ../../README.md:15 msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)" msgstr "" -#: ../../README.md:9 +#: ../../README.md:16 msgid "this current document in the `i18n` directory" msgstr "" -#: ../../README.md:11 +#: ../../README.md:18 msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)." msgstr "" -#: ../../README.md:13 +#: ../../README.md:20 msgid "Organization of this `i18n` directory is as follows:" msgstr "" -#: ../../README.md:15 +#: ../../README.md:22 msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)" msgstr "" -#: ../../README.md:16 +#: ../../README.md:23 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:17 +#: ../../README.md:24 msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner" msgstr "" -#: ../../README.md:18 +#: ../../README.md:25 msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations" msgstr "" -#: ../../README.md:19 +#: ../../README.md:26 msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files" msgstr "" -#: ../../README.md:20 +#: ../../README.md:27 msgid "[locales/](locales/): localization files for languages" msgstr "" -#: ../../README.md:21 +#: ../../README.md:28 msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))" msgstr "" -#: ../../README.md:23 +#: ../../README.md:30 msgid "Guide for translators" msgstr "" -#: ../../README.md:25 +#: ../../README.md:32 msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents." msgstr "" -#: ../../README.md:27 +#: ../../README.md:34 msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well." msgstr "" -#: ../../README.md:29 +#: ../../README.md:36 msgid "For now, translations are handled manually by editing `.po` files in the `locales/` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface." msgstr "" -#: ../../README.md:31 +#: ../../README.md:38 msgid "(Recommended) Using the uv package manager and just command runner" msgstr "" -#: ../../README.md:33 +#: ../../README.md:40 msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents." msgstr "" -#: ../../README.md:35 +#: ../../README.md:42 msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it." msgstr "" -#: ../../README.md:37 -#: ../../README.md:64 +#: ../../README.md:44 +#: ../../README.md:71 msgid "Preparation" msgstr "" -#: ../../README.md:39 +#: ../../README.md:46 msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed." msgstr "" -#: ../../README.md:41 -#: ../../README.md:72 +#: ../../README.md:48 +#: ../../README.md:79 msgid "Translation" msgstr "" -#: ../../README.md:43 -#: ../../README.md:74 +#: ../../README.md:50 +#: ../../README.md:81 msgid "Recommended flow when working on a new language (replace `` with the language code, e.g. `bg`):" msgstr "" -#: ../../README.md:45 +#: ../../README.md:52 msgid "Update the locale files for your language: `just sync-for-language ` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)" msgstr "" -#: ../../README.md:47 -#: ../../README.md:80 +#: ../../README.md:54 +#: ../../README.md:87 msgid "Use an editor to translate the files in the `locales/` directory" msgstr "" -#: ../../README.md:49 +#: ../../README.md:56 msgid "Build translated documents: `just build-for-language `" msgstr "" -#: ../../README.md:51 -#: ../../README.md:84 +#: ../../README.md:58 +#: ../../README.md:91 msgid "Preview the result in the `translations/` directory" msgstr "" -#: ../../README.md:53 -#: ../../README.md:86 +#: ../../README.md:60 +#: ../../README.md:93 msgid "Commit your changes done to the `locales/` directory" msgstr "" -#: ../../README.md:55 -#: ../../README.md:88 +#: ../../README.md:62 +#: ../../README.md:95 msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)" msgstr "" -#: ../../README.md:57 +#: ../../README.md:64 msgid "Using any other package manager and manual scripts" msgstr "" -#: ../../README.md:59 +#: ../../README.md:66 msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:" msgstr "" -#: ../../README.md:61 +#: ../../README.md:68 msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)" msgstr "" -#: ../../README.md:62 +#: ../../README.md:69 msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory" msgstr "" -#: ../../README.md:66 +#: ../../README.md:73 msgid "virtualenv and pip" msgstr "" -#: ../../README.md:68 +#: ../../README.md:75 msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`" msgstr "" -#: ../../README.md:69 +#: ../../README.md:76 msgid "Activate the virtual environment: `source .venv/bin/activate`" msgstr "" -#: ../../README.md:70 +#: ../../README.md:77 msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`" msgstr "" -#: ../../README.md:76 +#: ../../README.md:83 msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`" msgstr "" -#: ../../README.md:78 +#: ../../README.md:85 msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh `" msgstr "" -#: ../../README.md:82 +#: ../../README.md:89 msgid "Build translated documents: `./bin/build-translated-result.sh `" msgstr "" -#: ../../README.md:90 +#: ../../README.md:97 msgid "Publish translations in a new language" msgstr "" -#: ../../README.md:92 +#: ../../README.md:99 msgid "To publish prebuilt documents translated in a new language to the `translations/` directory:" msgstr "" -#: ../../README.md:94 +#: ../../README.md:101 msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file" msgstr "" -#: ../../README.md:95 +#: ../../README.md:102 msgid "whitelist its `translations/` directory by adding a `!translations/` rule to the [.gitignore](.gitignore) file" msgstr "" -#: ../../README.md:97 +#: ../../README.md:104 msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file." msgstr "" From e33bd16dc6870ff75d67c150352bd1359ec3a8e1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 19 Dec 2024 03:24:04 +0900 Subject: [PATCH 130/952] Consistent "send help" messages The common pattern is "Send `.*?` to the bot (in the room) to see the available commands." If the descripions are about a bot being invited to a certain existing room or room which is not DM, then "in the room" is inserted among them. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bot-honoroit.md | 2 +- docs/configuring-playbook-bot-matrix-registration-bot.md | 2 +- docs/configuring-playbook-bridge-appservice-discord.md | 2 +- docs/configuring-playbook-bridge-go-skype-bridge.md | 2 +- docs/configuring-playbook-bridge-hookshot.md | 2 +- docs/configuring-playbook-bridge-mautrix-discord.md | 2 +- docs/configuring-playbook-bridge-mautrix-slack.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-discord.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-groupme.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-instagram.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-slack.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-steam.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-twitter.md | 2 +- docs/configuring-playbook-bridge-postmoogle.md | 2 +- docs/configuring-playbook-cactus-comments.md | 2 +- 17 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 725c53a5a..a12af4608 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -391,7 +391,7 @@ After joining, the bot will introduce itself and show information about the [✨ If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands. -Send `!bai help` to the room at any time to see the bot's help menu for additional commands. +Send `!bai help` to the bot in the room to see the available commands. You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 5fa0ec6e3..f4e3222e9 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -238,6 +238,6 @@ To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:exam Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix` -If you enabled the github_cmd service you can get the supported commands via `!github help` +If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands. You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb). diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index af31bbd00..979404b25 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -68,6 +68,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room. -Send `!ho help` to the room to see the bot's help menu for additional commands. +Send `!ho help` to the bot in the room to see the available commands. You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features). diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 886c1e0dd..84c2e244e 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -52,7 +52,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -In this room send `help` and the bot will reply with all options. +Send `help` to the bot to see the available commands. You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands). diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 8dbf09474..2fecb6625 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -63,7 +63,7 @@ Then, follow the instructions in the help output message. If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server. -On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users. +On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users. **Note**: Encrypted Matrix rooms are not supported as of writing. diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index e5bcc450f..1b84e694f 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -33,4 +33,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 7df6f4992..57fd199fc 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -61,7 +61,7 @@ To use the bridge, you need to create a room and invite the Hookshot bot (`@hook Make sure the bot is able to send state events (usually the Moderator power level in clients). -Send `!hookshot help` to the room to see the bridge's help menu for additional commands. +Send `!hookshot help` to the bot to see the available commands. Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features. diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 061bcddd4..fbcd2b1e8 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -76,7 +76,7 @@ To acquire the token, open Discord in a private browser window. Then open the de 2. If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command. 3. You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app. 4. After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with "Succcessfully authenticated as …" -5. Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to +5. Now that you're logged in, you can send `help` to the bot to see the available commands. 6. Some Direct Messages from Discord should start syncing automatically 7. If you'd like to bridge guilds: - send `guilds status` to see the list of guilds diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 1794d9b72..19f0f75aa 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -63,7 +63,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 1. Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). 2. If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token. 3. The bot should respond with "Successfully logged into for team " -4. Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to. +4. Now that you're logged in, you can send `help` to the bot to see the available commands. 5. Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication. ### 💡 Set up Double Puppeting diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index 92f697a13..cbc61c068 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -43,4 +43,4 @@ Once logged in, send `list` to the bot user to list the available rooms. Clicking rooms in the list will result in you receiving an invitation to the bridged room. -Also send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md index 8d5cca9d8..6a7f8bb97 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md +++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md @@ -45,4 +45,4 @@ Once logged in, send `listrooms` to the bot user to list the available rooms. Clicking rooms in the list will result in you receiving an invitation to the bridged room. -Also send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md index c710fe0d1..53375a029 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md +++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md @@ -45,4 +45,4 @@ For double-puppeting, you probably want to issue these commands: If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out. -The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented. +Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented. diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index 59244ae13..b8e8971b6 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -48,4 +48,4 @@ Once logged in, send `list` to the bot user to list the available rooms. Clicking rooms in the list will result in you receiving an invitation to the bridged room. -Also send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md index 91cf92fe9..18ea7ad22 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-steam.md +++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md @@ -39,4 +39,4 @@ Once logged in, send `list` to the bot user to list the available rooms. Clicking rooms in the list will result in you receiving an invitation to the bridged room. -Also send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md index d86b1c38f..be0df2305 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md +++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md @@ -50,4 +50,4 @@ Once logged in, send `list` to the bot user to list the available rooms. Clicking rooms in the list will result in you receiving an invitation to the bridged room. -Also send `help` to the bot to see the commands available. +Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 86717c1f0..5aed1a144 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -71,7 +71,7 @@ To use the bridge, invite the `@postmoogle:example.com` bot user into a room you Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room. -Send `!pm help` to the room to see the bridge's help menu for additional commands. +Send `!pm help` to the bot in the room to see the available commands. You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle). diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 2b7911810..b39387d86 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -82,7 +82,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically. -To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working. +To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working. Then, register a site by sending `register ` (where `` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room. From e7ea6222798a19fac2d524a346820f928cf9ec87 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 20 Dec 2024 23:18:16 +0900 Subject: [PATCH 131/952] Update POT files Signed-off-by: Suguru Hirahara --- .../docs/configuring-playbook-bot-baibot.pot | 4 ++-- .../docs/configuring-playbook-bot-go-neb.pot | 4 ++-- .../docs/configuring-playbook-bot-honoroit.pot | 4 ++-- .../docs/configuring-playbook-bot-matrix-registration-bot.pot | 4 ++-- .../docs/configuring-playbook-bridge-appservice-discord.pot | 4 ++-- .../docs/configuring-playbook-bridge-go-skype-bridge.pot | 4 ++-- .../docs/configuring-playbook-bridge-hookshot.pot | 4 ++-- .../docs/configuring-playbook-bridge-mautrix-discord.pot | 4 ++-- .../docs/configuring-playbook-bridge-mautrix-slack.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-discord.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-groupme.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-instagram.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-slack.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-steam.pot | 4 ++-- .../docs/configuring-playbook-bridge-mx-puppet-twitter.pot | 4 ++-- .../docs/configuring-playbook-bridge-postmoogle.pot | 4 ++-- .../docs/configuring-playbook-cactus-comments.pot | 4 ++-- 17 files changed, 34 insertions(+), 34 deletions(-) diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot index 0056d351c..17c90fa0b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -400,7 +400,7 @@ msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring- msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:394 -msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." +msgid "Send `!bai help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:396 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot index 101a5dd72..a5c7049e3 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -137,7 +137,7 @@ msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matri msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:241 -msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" +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:243 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot index 404a4f5c1..a2660002b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -109,7 +109,7 @@ msgid "To use the bot, invite the `@honoroit:example.com` to the room you specif msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." +msgid "Send `!ho help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot index d2dfa6c62..423c6ac21 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -81,7 +81,7 @@ msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.c msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 -msgid "In this room send `help` and the bot will reply with all options." +msgid "Send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot index a0e2402a4..81f55b679 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -110,7 +110,7 @@ msgid "If the bot is not already in the Discord server, follow the provided invi msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 -msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." +msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot index 8f279cdf5..77317e407 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -69,5 +69,5 @@ msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 -msgid "Send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot index ba4ae20c1..c720cf45b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\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" @@ -109,7 +109,7 @@ msgid "Make sure the bot is able to send state events (usually the Moderator pow msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:64 -msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:66 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 6f571692f..42c732f37 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: 2024-12-20 07:23+0200\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" @@ -169,7 +169,7 @@ msgid "After confirming (in the Discord app) that you'd like to allow this login msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 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 8bca7986b..3cdcf38e4 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: 2024-12-20 07:23+0200\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" @@ -141,7 +141,7 @@ msgid "The bot should respond with \"Successfully logged into for team < msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot index 43cdf46e6..75de1e07f 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -93,5 +93,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot index 50caaae7d..0ba57698d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -85,5 +85,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot index 1b3cf7560..a6405e758 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -97,5 +97,5 @@ msgid "If you are linking only one Instagram account, your `$puppetId` is probab msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48 -msgid "The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented." +msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot index beb0f93e0..3f32ada11 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -93,5 +93,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot index a40080de2..8d2710c66 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -81,5 +81,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot index 9d538d060..d0c946e5a 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -93,5 +93,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot index 9c61b8821..b9b280c5d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -117,7 +117,7 @@ msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 -msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!pm help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 diff --git a/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot index 30b147203..9e3e8c613 100644 --- a/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot +++ b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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" @@ -121,7 +121,7 @@ msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:85 -msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." +msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:87 From e533eef620282d8b810436ea0b63ae6966af269d Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 21 Dec 2024 10:31:10 +0200 Subject: [PATCH 132/952] Upgrade Traefik (v3.2.1-0 -> v3.2.2-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 479fa0e8e..b85c5b407 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,7 +70,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.2.1-0 + version: v3.2.2-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 From c95d181c9a10e21f6e00730a6ca0549cf7dcec82 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 21 Dec 2024 13:44:09 +0200 Subject: [PATCH 133/952] Add `matrix_client_cinny_config_homeserverList` variable --- roles/custom/matrix-client-cinny/defaults/main.yml | 6 +++++- roles/custom/matrix-client-cinny/templates/config.json.j2 | 4 +--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 2137fed70..b242dee37 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -143,9 +143,13 @@ matrix_client_cinny_path_prefix: / # Controls whether the self-check feature should validate SSL certificates. matrix_client_cinny_self_check_validate_certificates: true -# config.json +# Default homeserver URL to use in the `config.json` file. +# See `matrix_client_cinny_config_homeserverList`. matrix_client_cinny_default_hs_url: "" +# Controls the `homeserverList` value in the `config.json` file. +matrix_client_cinny_config_homeserverList: "{{ [matrix_client_cinny_default_hs_url] }}" # noqa var-naming + # Default Cinny configuration template which covers the generic use case. # You can customize it by controlling the various variables inside it. # diff --git a/roles/custom/matrix-client-cinny/templates/config.json.j2 b/roles/custom/matrix-client-cinny/templates/config.json.j2 index 0da710acc..2a5bd1bcf 100644 --- a/roles/custom/matrix-client-cinny/templates/config.json.j2 +++ b/roles/custom/matrix-client-cinny/templates/config.json.j2 @@ -1,6 +1,4 @@ { "defaultHomeserver": 0, - "homeserverList": [ - {{ matrix_client_cinny_default_hs_url | string|to_json }} - ] + "homeserverList": {{ matrix_client_cinny_config_homeserverList | to_json }} } From 3b81f0974899fdaaa0c614506149d8287fc357c9 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 21 Dec 2024 13:57:01 +0200 Subject: [PATCH 134/952] Make various Cinny options configurable via dedicated variables Provoked by https://github.com/etkecc/mrs/pull/4 I've discovered that Cinny supports various configuration options and it'd be better if we add support for them. --- .../matrix-client-cinny/defaults/main.yml | 18 ++++++++++++++++++ .../templates/config.json.j2 | 11 +++++++++-- 2 files changed, 27 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index b242dee37..86e5d9ef9 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -147,9 +147,27 @@ matrix_client_cinny_self_check_validate_certificates: true # See `matrix_client_cinny_config_homeserverList`. matrix_client_cinny_default_hs_url: "" +# Controls the `defaultHomeserver` value in the `config.json` file. +matrix_client_cinny_config_defaultHomeserver: 0 # noqa var-naming + # Controls the `homeserverList` value in the `config.json` file. matrix_client_cinny_config_homeserverList: "{{ [matrix_client_cinny_default_hs_url] }}" # noqa var-naming +# Controls the `allowCustomHomeservers` value in the `config.json` file. +matrix_client_cinny_config_allowCustomHomeservers: true # noqa var-naming + +# Controls the `featuredCommunities.spaces` value in the `config.json` file. +matrix_client_cinny_config_featuredCommunities_spaces: [] # noqa var-naming + +# Controls the `featuredCommunities.rooms` value in the `config.json` file. +matrix_client_cinny_config_featuredCommunities_rooms: [] # noqa var-naming + +# Controls the `featuredCommunities.servers` value in the `config.json` file. +matrix_client_cinny_config_featuredCommunities_servers: ["matrix.org"] # noqa var-naming + +# Controls the `featuredCommunities.openAsDefault` value in the `config.json` file. +matrix_client_cinny_config_featuredCommunities_openAsDefault: false # noqa var-naming + # Default Cinny configuration template which covers the generic use case. # You can customize it by controlling the various variables inside it. # diff --git a/roles/custom/matrix-client-cinny/templates/config.json.j2 b/roles/custom/matrix-client-cinny/templates/config.json.j2 index 2a5bd1bcf..6c2b14313 100644 --- a/roles/custom/matrix-client-cinny/templates/config.json.j2 +++ b/roles/custom/matrix-client-cinny/templates/config.json.j2 @@ -1,4 +1,11 @@ { - "defaultHomeserver": 0, - "homeserverList": {{ matrix_client_cinny_config_homeserverList | to_json }} + "defaultHomeserver": {{ matrix_client_cinny_config_defaultHomeserver | to_json }}, + "homeserverList": {{ matrix_client_cinny_config_homeserverList | to_json }}, + "allowCustomHomeservers": {{ matrix_client_cinny_config_allowCustomHomeservers | to_json }}, + "featuredCommunities": { + "spaces": {{ matrix_client_cinny_config_featuredCommunities_spaces | to_json }}, + "rooms": {{ matrix_client_cinny_config_featuredCommunities_rooms | to_json }}, + "servers": {{ matrix_client_cinny_config_featuredCommunities_servers | to_json }}, + "openAsDefault": {{ matrix_client_cinny_config_featuredCommunities_openAsDefault | to_json }} + } } From 4abf6477d30bf75a5da949d442db5b9477206c0d Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sat, 21 Dec 2024 18:49:41 +0000 Subject: [PATCH 135/952] Update dependency Jinja2 to v3.1.5 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 92ee5b8b1..459f679f0 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -6,7 +6,7 @@ click==8.1.7 docutils==0.21.2 idna==3.10 imagesize==1.4.1 -Jinja2==3.1.4 +Jinja2==3.1.5 linkify-it-py==2.0.3 markdown-it-py==3.0.0 MarkupSafe==3.0.2 From b3b44a1ce8abb18718216c26bcc99da748a74fca Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sat, 21 Dec 2024 18:49:46 +0000 Subject: [PATCH 136/952] Update dependency click to v8.1.8 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 92ee5b8b1..de82cbace 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -2,7 +2,7 @@ alabaster==1.0.0 babel==2.16.0 certifi==2024.12.14 charset-normalizer==3.4.0 -click==8.1.7 +click==8.1.8 docutils==0.21.2 idna==3.10 imagesize==1.4.1 From a6a55961a914afab7e29661a5f88d0e6e9a696ac Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 22 Dec 2024 01:11:09 +0900 Subject: [PATCH 137/952] Edit docs/configuring-playbook-bot-buscarron.md: fix list items Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-buscarron.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index ee32ad90b..5dcdf9035 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -85,9 +85,9 @@ To use the bot, invite the `@bot.buscarron:example.com` to the room you specifie **Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if: -- if you hit the homepage (HTTP `GET` request to `/`) -- if you submit a form to the wrong URL (`POST` request to `/non-existing-form`) -- if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field +- you hit the homepage (HTTP `GET` request to `/`) +- you submit a form to the wrong URL (`POST` request to `/non-existing-form`) +- `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server. From 93c860305f82fa6ff861234f902ea32913036ddf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 20 Dec 2024 22:20:04 +0900 Subject: [PATCH 138/952] Edit docs for bots: fix sentences in the usage sections Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bot-buscarron.md | 6 +++++- docs/configuring-playbook-bot-chatgpt.md | 4 +++- docs/configuring-playbook-bot-honoroit.md | 4 +++- 4 files changed, 12 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index a12af4608..b8f611107 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -383,7 +383,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bot, invite the `@baibot:example.com` bot user into a room. +To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain). If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room. diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 5dcdf9035..7a1a33be8 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -75,7 +75,11 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form: +To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain). + +After the bot joins the room, anyone can call the web form via HTTP POST method. + +Here is an example for the `contact` form: ```html
diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index dd9601496..00c40b674 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -70,6 +70,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot. +To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain). + +After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot. You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot). diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index 979404b25..2f5379d18 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -66,7 +66,9 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room. +To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain). + +After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room. Send `!ho help` to the bot in the room to see the available commands. From 3be6043b5aa41258676f5ec70cba5d2583874ff4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 22 Dec 2024 11:59:03 +0900 Subject: [PATCH 139/952] Update POT files Signed-off-by: Suguru Hirahara --- .../docs/configuring-playbook-bot-baibot.pot | 4 +-- .../configuring-playbook-bot-buscarron.pot | 32 ++++++++++++------- .../docs/configuring-playbook-bot-chatgpt.pot | 8 +++-- .../configuring-playbook-bot-honoroit.pot | 10 ++++-- 4 files changed, 35 insertions(+), 19 deletions(-) diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot index 17c90fa0b..b844e768a 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 23:17+0900\n" +"POT-Creation-Date: 2024-12-22 11:54+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -384,7 +384,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:386 -msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:388 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot index dbf33309f..fc424777c 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-22 11:54+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -101,29 +101,37 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:78 -msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:86 -msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" +#: ../../../docs/configuring-playbook-bot-buscarron.md:80 +msgid "After the bot joins the room, anyone can call the web form via HTTP POST method." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:88 -msgid "if you hit the homepage (HTTP `GET` request to `/`)" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-buscarron.md:89 -msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" +#: ../../../docs/configuring-playbook-bot-buscarron.md:82 +msgid "Here is an example for the `contact` form:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:90 -msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:92 -msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgid "you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:93 +msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:96 +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:98 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot index fb7c08818..a99685101 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-22 11:54+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -105,9 +105,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:73 -msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:77 msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot index a2660002b..2d47ea65c 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 23:17+0900\n" +"POT-Creation-Date: 2024-12-22 11:54+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -105,13 +105,17 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:69 -msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "Send `!ho help` to the bot in the room to see the available commands." +msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "Send `!ho help` to the bot in the room to see the available commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:75 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." msgstr "" From 6b87d1aa7d24ce99578a252317670c80e4891be2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 22 Dec 2024 14:59:40 +0900 Subject: [PATCH 140/952] Edit docs: consistent instructions to generate passphrases or secrets with pwgen This commit replaces instructions to create passwords, passphrases, or secrets with common ones. Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- docs/configuring-playbook-alertmanager-receiver.md | 2 +- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-bot-baibot.md | 4 ++-- docs/configuring-playbook-bot-buscarron.md | 2 +- docs/configuring-playbook-bot-chatgpt.md | 2 +- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bot-honoroit.md | 2 +- docs/configuring-playbook-bot-matrix-registration-bot.md | 2 +- docs/configuring-playbook-bot-matrix-reminder-bot.md | 2 +- docs/configuring-playbook-bot-maubot.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- docs/configuring-playbook-bridge-postmoogle.md | 2 +- docs/configuring-playbook-matrix-registration.md | 2 +- docs/configuring-playbook-shared-secret-auth.md | 2 +- examples/vars.yml | 2 +- 17 files changed, 18 insertions(+), 18 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9cd25b0ab..a127deb13 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2192,7 +2192,7 @@ To migrate to the new setup, expect a few minutes of downtime, while you follow 1. We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it. -2. Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy! +2. Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy! 3. Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this: ```yaml diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 078b7be17..08aca3d54 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -14,7 +14,7 @@ This service uses a bot (with a username specified in `matrix_alertmanager_recei The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. -Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. +Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. You can use the playbook to [register a new user](registering-users.md): diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index fc933d9e2..dba51e905 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -60,7 +60,7 @@ where: * USER - SSH user of a provider/server * HOST - SSH host of a provider/server * REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) -* PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager +* PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`. * PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable. diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index b8f611107..b2d05308d 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -38,12 +38,12 @@ matrix_bot_baibot_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_baibot_config_user_mxid_localpart: baibot -# Generate a strong password here. Consider generating it with `pwgen -s 64 1`. +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. # If you'd like to change this password subsequently, see the details below. matrix_bot_baibot_config_user_password: 'PASSWORD_FOR_THE_BOT' # An optional passphrase to use for backing up and recovering the bot's encryption keys. -# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`). +# You can create one with a command like `pwgen -s 64 1`. # # If set to null, the recovery module will not be used and losing your session/database # will mean you lose access to old messages in encrypted room. diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 7a1a33be8..3fa6b4a43 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -14,7 +14,7 @@ matrix_bot_buscarron_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_buscarron_login: bot.buscarron -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_bot_buscarron_password: PASSWORD_FOR_THE_BOT # Adjust accepted forms diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 00c40b674..659ae77bb 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -12,7 +12,7 @@ The playbook does not automatically create users for you. The bot requires an ac You **need to register the bot user manually** before setting up the bot. -Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. +Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. You can use the playbook to [register a new user](registering-users.md): diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index c4a0239c8..f4ce3e759 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -14,7 +14,7 @@ If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-on The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. -Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. +Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. You can use the playbook to [register a new user](registering-users.md): diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index f4e3222e9..359f55d73 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -14,7 +14,7 @@ The playbook does not automatically create users for you. The bot requires at le You **need to register the bot user manually** before setting up the bot. -Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. +Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. You can use the playbook to [register a new user](registering-users.md): diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index 2f5379d18..d0e887563 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -16,7 +16,7 @@ matrix_bot_honoroit_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_honoroit_login: honoroit -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_bot_honoroit_password: PASSWORD_FOR_THE_BOT # Adjust this to your room ID diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 84c2e244e..8eb1132e4 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -17,7 +17,7 @@ matrix_bot_matrix_registration_bot_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_matrix_registration_bot_matrix_user_id_localpart: bot.matrix-registration-bot -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_bot_matrix_registration_bot_bot_password: PASSWORD_FOR_THE_BOT # Enables registration diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index 476dc4aa9..d2b53fc63 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -16,7 +16,7 @@ matrix_bot_matrix_reminder_bot_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_matrix_reminder_bot_matrix_user_id_localpart: bot.matrix-reminder-bot -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_bot_matrix_reminder_bot_matrix_user_password: PASSWORD_FOR_THE_BOT # Adjust this to your timezone diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index b1ffb08da..400898d39 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -16,7 +16,7 @@ matrix_bot_maubot_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_maubot_login: bot.maubot -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_bot_maubot_initial_password: PASSWORD_FOR_THE_BOT matrix_bot_maubot_admins: diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 0a52f63fa..59630ae01 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -10,7 +10,7 @@ See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/mai The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. -Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`. +Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. You can use the playbook to [register a new user](registering-users.md): diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 5aed1a144..15a7a39ec 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -29,7 +29,7 @@ matrix_postmoogle_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_postmoogle_login: postmoogle -# Generate a strong password here. Consider generating it with `pwgen -s 64 1` +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. matrix_postmoogle_password: PASSWORD_FOR_THE_BOT # Uncomment to add one or more admins to this bridge: diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 73168fdb8..4a1eeeaf5 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -23,7 +23,7 @@ To enable matrix-registration, add the following configuration to your `inventor ```yaml matrix_registration_enabled: true -# Generate a strong secret here. Consider generating it with `pwgen -s 64 1` +# Generate a strong secret here. You can create one with a command like `pwgen -s 64 1`. matrix_registration_admin_secret: "ENTER_SOME_SECRET_HERE" ``` diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index 633438aa9..c7dced046 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -11,7 +11,7 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ ```yaml matrix_synapse_ext_password_provider_shared_secret_auth_enabled: true -# Generate a strong shared secret here. Consider generating it with `pwgen -s 64 1` +# Generate a strong shared secret here. You can create one with a command like `pwgen -s 64 1`. matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: YOUR_SHARED_SECRET_GOES_HERE ``` diff --git a/examples/vars.yml b/examples/vars.yml index 31a421671..36b1fb153 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -20,7 +20,7 @@ matrix_domain: example.com matrix_homeserver_implementation: synapse # A secret used as a base, for generating various other secrets. -# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`). +# You can put any string here, but generating a strong one is preferred. You can create one with a command like `pwgen -s 64 1`. matrix_homeserver_generic_secret_key: '' # By default, the playbook manages its own Traefik (https://doc.traefik.io/traefik/) reverse-proxy server. From f044bdd2795e3e25f4d15aef32b21a16bce07860 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 22 Dec 2024 17:54:16 +0900 Subject: [PATCH 141/952] Update POT files Signed-off-by: Suguru Hirahara --- i18n/translation-templates/CHANGELOG.pot | 4 ++-- .../docs/configuring-playbook-alertmanager-receiver.pot | 4 ++-- .../docs/configuring-playbook-backup-borg.pot | 4 ++-- .../docs/configuring-playbook-bot-chatgpt.pot | 4 ++-- .../docs/configuring-playbook-bot-draupnir.pot | 4 ++-- .../docs/configuring-playbook-bot-go-neb.pot | 4 ++-- .../docs/configuring-playbook-bot-mjolnir.pot | 4 ++-- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/i18n/translation-templates/CHANGELOG.pot b/i18n/translation-templates/CHANGELOG.pot index ce8eb6286..502fcbe16 100644 --- a/i18n/translation-templates/CHANGELOG.pot +++ b/i18n/translation-templates/CHANGELOG.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -4005,7 +4005,7 @@ msgid "We believe the steps below are safe and you won't encounter any data loss msgstr "" #: ../../../CHANGELOG.md:2195 -msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" msgstr "" #: ../../../CHANGELOG.md:2197 diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot index 858379113..a0fbbaa1d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot +++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 diff --git a/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot index c4b7fc2a6..e99b346ad 100644 --- a/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot +++ b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -93,7 +93,7 @@ msgid "REPO - BorgBackup repository name, it will be initialized on backup start msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:63 -msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" +msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:64 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot index a99685101..399f7f0f6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 11:54+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -45,7 +45,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:15 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +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:17 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot index 0a1d292b3..68b3790f1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot index a5c7049e3..cf6d9249d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 23:17+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgid "You **need to register the bot user manually** before setting up the bot. msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:19 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot index d1aae2fce..ce22d9fa9 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -41,7 +41,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:15 From c5f4ea6850ad84f57ff353664a3c472c255b99dc Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 22 Dec 2024 09:30:35 +0000 Subject: [PATCH 142/952] Update dependency urllib3 to v2.3.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 3dea15066..d3f036feb 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -30,4 +30,4 @@ sphinxcontrib-qthelp==2.0.0 sphinxcontrib-serializinghtml==2.0.0 tabulate==0.9.0 uc-micro-py==1.0.3 -urllib3==2.2.3 +urllib3==2.3.0 From 9a56aff933112c484136b43ab1923175ce96abf2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 22 Dec 2024 23:44:48 +0900 Subject: [PATCH 143/952] Edit docs for bots: adopt the common format - Add "To use the bot" if it does not exist: adopt the format of the docs for bridges - Add "Prerequisites" section if an API key or user account is required - Use the common instruction for getting an access token - Replace "Get" with "Obtain" about getting keys or access tokens - Replace placeholders for access tokens on docs/configuring-playbook-bot-go.neb.md Signed-off-by: Suguru Hirahara --- ...figuring-playbook-alertmanager-receiver.md | 5 ++-- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bot-buscarron.md | 2 +- docs/configuring-playbook-bot-chatgpt.md | 28 +++++++++---------- docs/configuring-playbook-bot-draupnir.md | 6 ++-- docs/configuring-playbook-bot-go-neb.md | 18 ++++++------ docs/configuring-playbook-bot-honoroit.md | 2 +- ...ng-playbook-bot-matrix-registration-bot.md | 2 +- ...guring-playbook-bot-matrix-reminder-bot.md | 2 +- docs/configuring-playbook-bot-maubot.md | 4 +-- docs/configuring-playbook-bot-mjolnir.md | 6 ++-- docs/configuring-playbook-email2matrix.md | 2 +- docs/howto-server-delegation.md | 2 +- 13 files changed, 40 insertions(+), 41 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 08aca3d54..c42747e99 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -22,7 +22,7 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` -### Get an access token +### Obtain an access token The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). @@ -36,7 +36,7 @@ Then, log in as the bot using any Matrix client of your choosing, accept the roo ## Adjusting the playbook configuration -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](#get-an-access-token). +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_alertmanager_receiver_enabled: true @@ -44,7 +44,6 @@ matrix_alertmanager_receiver_enabled: true # Uncomment and adjust this part if you'd like to use a username different than the default # matrix_alertmanager_receiver_config_matrix_user_id_localpart: "bot.alertmanager.receiver" -# Specify the bot user's access token here. matrix_alertmanager_receiver_config_matrix_access_token: "ACCESS_TOKEN_HERE" # Optionally, configure some mappings (URL-friendly room name -> actual Matrix room ID). diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index b2d05308d..1a80546e0 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -30,7 +30,7 @@ Depending on your current `vars.yml` file and desired configuration, **you may r ### Base configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_bot_baibot_enabled: true diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 3fa6b4a43..1ac73e7e3 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -6,7 +6,7 @@ Buscarron is bot that receives HTTP POST submissions of web forms and forwards t ## Adjusting the playbook configuration -To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_bot_buscarron_enabled: true diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 659ae77bb..e3ff7a431 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -6,11 +6,15 @@ The playbook can install and configure [matrix-chatgpt-bot](https://github.com/m Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client! -## Register the bot account +## Prerequisites -The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver. +### Obtain an OpenAI API key -You **need to register the bot user manually** before setting up the bot. +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). + +### Register the bot account + +The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. @@ -20,37 +24,31 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` -## Get an access token and create encryption keys +### Obtain an access token and create encryption keys -Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +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). To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6). ## Adjusting the playbook configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively. ```yaml matrix_bot_chatgpt_enabled: true -# Obtain a new API key from https://platform.openai.com/account/api-keys -matrix_bot_chatgpt_openai_api_key: '' +matrix_bot_chatgpt_openai_api_key: 'API_KEY_HERE' -# This is the default username +# Uncomment and adjust this part if you'd like to use a username different than the default # matrix_bot_chatgpt_matrix_bot_username_localpart: 'bot.chatgpt' -# Matrix access token (from bot user above) -# see: https://webapps.stackexchange.com/questions/131056/how-to-get-an-access-token-for-element-riot-matrix -matrix_bot_chatgpt_matrix_access_token: '' +matrix_bot_chatgpt_matrix_access_token: 'ACCESS_TOKEN_HERE' # Configuring the system promt used, needed if the bot is used for special tasks. # More information: https://github.com/mustvlad/ChatGPT-System-Prompts matrix_bot_chatgpt_matrix_bot_prompt_prefix: 'Instructions:\nYou are ChatGPT, a large language model trained by OpenAI.' - ``` -You will need to get tokens for ChatGPT. - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index f4ce3e759..288a8547c 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -24,7 +24,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupni If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -### Get an access token +### Obtain an access token The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). @@ -64,7 +64,7 @@ Finally invite the `@bot.draupnir:example.com` account you created earlier into ## Adjusting the playbook configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. ```yaml # Enable Draupnir @@ -113,7 +113,7 @@ matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_ When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#get-an-access-token). +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 359f55d73..1c3118dfb 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -8,11 +8,11 @@ Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the ori 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. -## Registering the bot account +## Prerequisites -The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver. +### Register the bot account -You **need to register the bot user manually** before setting up the bot. +The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. @@ -22,11 +22,13 @@ You can use the playbook to [register a new user](registering-users.md): ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user ``` -Once the user is created you can [obtain an access token](obtaining-access-tokens.md). +### Obtain an access token + +The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). ## Adjusting the playbook configuration -To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token). ```yaml matrix_bot_go_neb_enabled: true @@ -35,7 +37,7 @@ matrix_bot_go_neb_enabled: true # Use the access token you obtained in the step above. matrix_bot_go_neb_clients: - UserID: "@goneb:{{ matrix_domain }}" - AccessToken: "MDASDASJDIASDJASDAFGFRGER" + AccessToken: "ACCESS_TOKEN_FOR_GONEB_HERE" DeviceID: "DEVICE1" HomeserverURL: "{{ matrix_addons_homeserver_client_api_url }}" Sync: true @@ -44,7 +46,7 @@ matrix_bot_go_neb_clients: AcceptVerificationFromUsers: [":{{ matrix_domain }}"] - UserID: "@another_goneb:{{ matrix_domain }}" - AccessToken: "MDASDASJDIASDJASDAFGFRGER" + AccessToken: "ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE" DeviceID: "DEVICE2" HomeserverURL: "{{ matrix_addons_homeserver_client_api_url }}" Sync: false @@ -105,7 +107,7 @@ matrix_bot_go_neb_services: api_key: "AIzaSyA4FD39m9" cx: "AIASDFWSRRtrtr" -# Get a key via https://api.imgur.com/oauth2/addclient +# Obtain a key via https://api.imgur.com/oauth2/addclient # Select "oauth2 without callback url" - ID: "imgur_service" Type: "imgur" diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index d0e887563..be8c9acee 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -8,7 +8,7 @@ See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/R ## Adjusting the playbook configuration -To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_bot_honoroit_enabled: true diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 8eb1132e4..95b86163f 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -6,7 +6,7 @@ The bot allows you to easily **create and manage registration tokens** aka. invi See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you. -## Configuration +## Adjusting the playbook configuration To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index d2b53fc63..d82c3eae1 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -8,7 +8,7 @@ See the project's [documentation](https://github.com/anoadragon453/matrix-remind ## Adjusting the playbook configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_bot_matrix_reminder_bot_enabled: true diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 400898d39..04eeb0cb8 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -8,7 +8,7 @@ See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) t ## Adjusting the playbook configuration -To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_bot_maubot_enabled: true @@ -75,7 +75,7 @@ You should start in the following order 2. **Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source. 3. **Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave) -## Obtaining an access token +## Obtain an access token This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 59630ae01..53fd17784 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -20,7 +20,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. -### Get an access token +### Obtain an access token The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). @@ -60,7 +60,7 @@ Finally invite the `@bot.mjolnir:example.com` account you created earlier into t ## Adjusting the playbook configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. ```yaml # Enable Mjolnir @@ -109,7 +109,7 @@ matrix_bot_mjolnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_u When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#get-an-access-token). +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_HERE" diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 45f928dc7..4ceda308f 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -38,7 +38,7 @@ Inviting additional people to the room is okay too. Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below. -### Obtaining an access token for the sender user +### Obtain an access token for the sender user In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index ff41f3eb3..429e06982 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -51,7 +51,7 @@ To use DNS SRV record validation, you need to: For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md) -### Obtaining certificates +### Obtain certificates How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you. From 069f1392e0d681c4a6ecdc3172d1adcc1e5782eb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 13:09:28 +0900 Subject: [PATCH 144/952] Update POT files Signed-off-by: Suguru Hirahara --- ...iguring-playbook-alertmanager-receiver.pot | 42 ++++++------- .../docs/configuring-playbook-bot-baibot.pot | 4 +- .../configuring-playbook-bot-buscarron.pot | 4 +- .../docs/configuring-playbook-bot-chatgpt.pot | 62 ++++++++++--------- .../configuring-playbook-bot-draupnir.pot | 8 +-- .../docs/configuring-playbook-bot-go-neb.pot | 56 +++++++++-------- .../configuring-playbook-bot-honoroit.pot | 4 +- ...g-playbook-bot-matrix-registration-bot.pot | 4 +- ...uring-playbook-bot-matrix-reminder-bot.pot | 4 +- .../docs/configuring-playbook-bot-maubot.pot | 6 +- .../docs/configuring-playbook-bot-mjolnir.pot | 8 +-- .../configuring-playbook-email2matrix.pot | 4 +- .../docs/howto-server-delegation.pot | 4 +- 13 files changed, 109 insertions(+), 101 deletions(-) diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot index a0fbbaa1d..7782e5c8f 100644 --- a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot +++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 17:53+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -57,7 +57,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 @@ -85,77 +85,77 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 -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](#get-an-access-token)." +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:61 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 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:67 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 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:69 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82 msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86 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:94 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 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:98 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 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:100 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:102 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:122 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot index b844e768a..6da583653 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 11:54+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -77,7 +77,7 @@ msgid "Base configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:33 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:71 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot index fc424777c..1e36161dc 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 11:54+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,7 +33,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:9 -msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:32 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot index 399f7f0f6..19e496fdb 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 17:53+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,85 +33,89 @@ msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Ma msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:9 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgid "Obtain an OpenAI API key" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 -msgid "You **need to register the bot user manually** before setting up the bot." +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 "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:19 +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:21 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 -msgid "Get an access token and create encryption keys" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 -msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." -msgstr "" - #: ../../../docs/configuring-playbook-bot-chatgpt.md:27 -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)." +msgid "Obtain an access token and create encryption keys" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:29 -msgid "Adjusting the playbook configuration" +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 "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:33 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:35 +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:52 -msgid "You will need to get tokens for ChatGPT." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:56 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:61 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 +#: ../../../docs/configuring-playbook-bot-chatgpt.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-bot-chatgpt.md:69 +#: ../../../docs/configuring-playbook-bot-chatgpt.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." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:77 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot index 68b3790f1..645d34ac6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 17:53+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -61,7 +61,7 @@ msgid "If you would like Draupnir to be able to deactivate users, move aliases, msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 @@ -125,7 +125,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:67 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:76 @@ -165,7 +165,7 @@ msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you mu msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:116 -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](#get-an-access-token)." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:122 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot index cf6d9249d..ce2d7387a 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 17:53+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -37,15 +37,15 @@ msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/bl msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 -msgid "Registering the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 @@ -57,89 +57,93 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:25 -msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:27 -msgid "Adjusting the playbook configuration" +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:193 -msgid "Adjusting the Go-NEB URL" +#: ../../../docs/configuring-playbook-bot-go-neb.md:31 +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:195 -msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgid "Adjusting the Go-NEB URL" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:197 -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." +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:199 +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:201 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +#: ../../../docs/configuring-playbook-bot-go-neb.md:212 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:218 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:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +#: ../../../docs/configuring-playbook-bot-go-neb.md:222 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:227 +#: ../../../docs/configuring-playbook-bot-go-neb.md:229 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:231 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:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:233 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:233 +#: ../../../docs/configuring-playbook-bot-go-neb.md:235 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If 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:235 +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +#: ../../../docs/configuring-playbook-bot-go-neb.md:239 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:239 +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:241 +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 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:243 +#: ../../../docs/configuring-playbook-bot-go-neb.md:245 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot index 2d47ea65c..6b1ef24b1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 11:54+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -37,7 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:11 -msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:26 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot index 423c6ac21..9773f005d 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 23:17+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,7 +33,7 @@ msgid "See the project's [documentation](https://github.com/moan0s/matrix-regist msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 -msgid "Configuration" +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot index 6c96f8b74..98bf509a9 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -37,7 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot index 674c77c54..3bbb8d3d2 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -37,7 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:11 -msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:26 @@ -129,7 +129,7 @@ msgid "**Create an instance**: An instance is the actual bot. You have to specif msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 -msgid "Obtaining an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot index ce22d9fa9..a033bff46 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-22 17:53+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -53,7 +53,7 @@ msgid "If you would like Mjolnir to be able to deactivate users, move aliases, s msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:23 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 @@ -117,7 +117,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:63 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:72 @@ -157,7 +157,7 @@ msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you mus msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -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](#get-an-access-token)." +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:118 diff --git a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot index e0308bcc2..f508b138b 100644 --- a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot +++ b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -97,7 +97,7 @@ msgid "Take note of each room's room ID (different clients show the room ID in a msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:41 -msgid "Obtaining an access token for the sender user" +msgid "Obtain an access token for the sender user" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 diff --git a/i18n/translation-templates/docs/howto-server-delegation.pot b/i18n/translation-templates/docs/howto-server-delegation.pot index 45d19bc5a..735e493f0 100644 --- a/i18n/translation-templates/docs/howto-server-delegation.pot +++ b/i18n/translation-templates/docs/howto-server-delegation.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -125,7 +125,7 @@ msgid "For more details on how to configure the playbook to work with SRV delega msgstr "" #: ../../../docs/howto-server-delegation.md:54 -msgid "Obtaining certificates" +msgid "Obtain certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:56 From f1c238e73251beeaccecb1b575fd46496b9b091b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:14:06 +0200 Subject: [PATCH 145/952] Update mautrix-discord config to latest upstream sample and introduce a few new Ansible variables Provoked by https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3900 --- group_vars/matrix_servers | 4 +- .../defaults/main.yml | 29 ++- .../tasks/validate_config.yml | 4 +- .../templates/config.yaml.j2 | 189 ++++++++++++------ 4 files changed, 158 insertions(+), 68 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index e8bef4559..4331a7a83 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -1116,9 +1116,11 @@ matrix_mautrix_discord_systemd_required_services_list_auto: | matrix_mautrix_discord_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.as.tok', rounds=655555) | to_uuid }}" matrix_mautrix_discord_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" -matrix_mautrix_discord_homeserver_public_address: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_server_fqn_matrix }}" matrix_mautrix_discord_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.hs.tok', rounds=655555) | to_uuid }}" +matrix_mautrix_discord_bridge_public_address: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_server_fqn_matrix }}" +matrix_mautrix_discord_bridge_avatar_proxy_key: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.avatar', rounds=655555) | to_uuid }}" + matrix_mautrix_discord_bridge_login_shared_secret_map_auto: |- {{ ({ diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index 81104c7f4..913f2d363 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -22,11 +22,31 @@ matrix_mautrix_discord_data_path: "{{ matrix_mautrix_discord_base_path }}/data" matrix_mautrix_discord_docker_src_files_path: "{{ matrix_mautrix_discord_base_path }}/docker-src" matrix_mautrix_discord_homeserver_address: "" -matrix_mautrix_discord_homeserver_public_address: '' matrix_mautrix_discord_homeserver_domain: "{{ matrix_domain }}" matrix_mautrix_discord_appservice_address: "http://matrix-mautrix-discord:8080" -matrix_mautrix_discord_command_prefix: "!discord" +matrix_mautrix_discord_bridge_command_prefix: "!discord" + +# Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode. +# If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address. +# This should not have a trailing slash, the endpoint above will be appended to the provided address. +matrix_mautrix_discord_bridge_public_address: '' + +# A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature. +matrix_mautrix_discord_bridge_avatar_proxy_key: '' + +# Localpart template of MXIDs for Discord users. +# {{ '{{.}}' }} is replaced with the internal ID of the Discord user. +matrix_mautrix_discord_bridge_username_template: "{% raw %}discord_{{.}}{% endraw %}" + +# Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled. +matrix_mautrix_discord_bridge_displayname_template: "{% raw %}{{or .GlobalName .Username}}{{if .Bot}} (bot){{end}}{% endraw %}" + +# Displayname template for Discord channels (bridged as rooms, or spaces when type=4). +matrix_mautrix_discord_bridge_channel_name_template: "{% raw %}{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}{% endraw %}" + +# Displayname template for Discord guilds (bridged as spaces). +matrix_mautrix_discord_bridge_guild_name_template: "{% raw %}{{.Name}}{% endraw %}" matrix_mautrix_discord_bridge_permissions: | {{ @@ -56,6 +76,8 @@ matrix_mautrix_discord_appservice_token: '' matrix_mautrix_discord_homeserver_token: '' matrix_mautrix_discord_appservice_bot_username: discordbot +matrix_mautrix_discord_appservice_bot_displayname: Discord bridge bot +matrix_mautrix_discord_appservice_bot_avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC matrix_mautrix_discord_provisioning_shared_secret: disable @@ -162,6 +184,9 @@ matrix_mautrix_discord_registration: "{{ matrix_mautrix_discord_registration_yam # Enable End-to-bridge encryption matrix_mautrix_discord_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}" matrix_mautrix_discord_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}" +matrix_mautrix_discord_bridge_encryption_require: false +matrix_mautrix_discord_bridge_encryption_appservice: false +matrix_mautrix_discord_bridge_encryption_plaintext_mentions: false matrix_mautrix_discord_bridge_encryption_key_sharing_allow: "{{ matrix_mautrix_discord_bridge_encryption_allow }}" # On Conduit versions before 0.5.0 this option prevented users from joining spaces created by the bridge. diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml index 96cffd4a7..5251564e5 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml @@ -9,7 +9,7 @@ - {'name': 'matrix_mautrix_discord_appservice_token', when: true} - {'name': 'matrix_mautrix_discord_homeserver_address', when: true} - {'name': 'matrix_mautrix_discord_homeserver_token', when: true} - - {'name': 'matrix_mautrix_discord_homeserver_public_address', when: true} + - {'name': 'matrix_mautrix_discord_bridge_public_address', when: true} - {'name': 'matrix_mautrix_discord_container_network', when: true} - {'name': 'matrix_mautrix_discord_database_hostname', when: "{{ matrix_mautrix_discord_database_engine == 'postgres' }}"} @@ -21,3 +21,5 @@ when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_discord_login_shared_secret', 'new': ''} + - {'old': 'matrix_mautrix_discord_homeserver_public_address', 'new': 'matrix_mautrix_discord_bridge_public_address'} + - {'old': 'matrix_mautrix_discord_command_prefix', 'new': 'matrix_mautrix_discord_bridge_command_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 index bed044bcb..c859c1149 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 @@ -3,13 +3,12 @@ homeserver: # The address that this appservice can use to connect to the homeserver. address: {{ matrix_mautrix_discord_homeserver_address | to_json }} - # Publicly accessible base URL for media, used for avatars in relay mode. - # If not set, the connection address above will be used. - public_address: {{ matrix_mautrix_discord_homeserver_public_address | to_json }} - # The domain of the homeserver (for MXIDs, etc). + # The domain of the homeserver (also known as server_name, used for MXIDs, etc). domain: {{ matrix_mautrix_discord_homeserver_domain | to_json }} - # Is the homeserver actually mautrix-asmux? - asmux: false + + # What software is the homeserver running? + # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here. + software: standard # The URL to push real-time bridge status to. # If set, the bridge will make POST requests to this URL whenever a user's discord connection state changes. # The bridge will use the appservice as_token to authorize requests. @@ -19,6 +18,13 @@ homeserver: # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246? async_media: false + # Should the bridge use a websocket for connecting to the homeserver? + # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy, + # mautrix-asmux (deprecated), and hungryserv (proprietary). + websocket: false + # How often should the websocket be pinged? Pinging will be disabled if this is zero. + ping_interval_seconds: 0 + # Application service host/registration related details. # Changing these values requires regeneration of the registration. appservice: @@ -31,13 +37,14 @@ appservice: # Database config. database: - # The database type. "sqlite3" and "postgres" are supported. - type: {{ matrix_mautrix_discord_appservice_database_type|to_json }} + # The database type. "sqlite3-fk-wal" and "postgres" are supported. + type: {{ matrix_mautrix_discord_appservice_database_type | to_json }} # The database URI. - # SQLite: File name is enough. https://github.com/mattn/go-sqlite3#connection-string + # SQLite: A raw file path is supported, but `file:?_txlock=immediate` is recommended. + # https://github.com/mattn/go-sqlite3#connection-string # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql - uri: {{ matrix_mautrix_discord_appservice_database_uri|to_json }} + uri: {{ matrix_mautrix_discord_appservice_database_uri | to_json }} # Maximum number of connections. Mostly relevant for Postgres. max_open_conns: 20 max_idle_conns: 2 @@ -51,15 +58,21 @@ appservice: # Appservice bot details. bot: # Username of the appservice bot. - username: {{ matrix_mautrix_discord_appservice_bot_username|to_json }} + username: {{ matrix_mautrix_discord_appservice_bot_username | to_json }} # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty # to leave display name/avatar as-is. - displayname: Discord bridge bot - avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC + displayname: {{ matrix_mautrix_discord_appservice_bot_displayname | to_json }} + avatar: {{ matrix_mautrix_discord_appservice_bot_avatar | to_json }} + # Whether or not to receive ephemeral events via appservice transactions. # Requires MSC2409 support (i.e. Synapse 1.22+). ephemeral_events: true + # Should incoming events be handled asynchronously? + # This may be necessary for large public instances with lots of messages going through. + # However, messages will not be guaranteed to be bridged in the same order they were sent in. + async_transactions: false + # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify. as_token: {{ matrix_mautrix_discord_appservice_token | to_json }} hs_token: {{ matrix_mautrix_discord_homeserver_token | to_json }} @@ -67,51 +80,67 @@ appservice: # Bridge config bridge: # Localpart template of MXIDs for Discord users. - # {{ '{{.}}' }} is replaced with the internal ID of the Discord user. - username_template: "{{ 'discord_{{.}}' }}" + # {% raw %}{{.}}{% endraw %} is replaced with the internal ID of the Discord user. + username_template: {{ matrix_mautrix_discord_bridge_username_template | to_json }} # Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled. # Available variables: - # {{ '{{.ID}}' }} - Internal user ID - # {{ '{{.Username}}' }} - Legacy display/username on Discord - # {{ '{{.GlobalName}}' }} - New displayname on Discord - # {{ '{{.Discriminator}}' }} - The 4 numbers after the name on Discord - # {{ '{{.Bot}}' }} - Whether the user is a bot - # {{ '{{.System}}' }} - Whether the user is an official system user - # {{ '{{.Webhook}}' }} - Whether the user is a webhook and is not an application - # {{ '{{.Application}}' }} - Whether the user is an application - displayname_template: "{{ '{{or .GlobalName .Username}}{{if .Bot}} (bot){{end}}' }}" + # .ID - Internal user ID + # .Username - Legacy display/username on Discord + # .GlobalName - New displayname on Discord + # .Discriminator - The 4 numbers after the name on Discord + # .Bot - Whether the user is a bot + # .System - Whether the user is an official system user + # .Webhook - Whether the user is a webhook and is not an application + # .Application - Whether the user is an application + displayname_template: {{ matrix_mautrix_discord_bridge_displayname_template | to_json }} # Displayname template for Discord channels (bridged as rooms, or spaces when type=4). # Available variables: - # {{ '{{.Name}}' }} - Channel name, or user displayname (pre-formatted with displayname_template) in DMs. - # {{ '{{.ParentName}}' }} - Parent channel name (used for categories). - # {{ '{{.GuildName}}' }} - Guild name. - # {{ '{{.NSFW}}' }} - Whether the channel is marked as NSFW. - # {{ '{{.Type}}' }} - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267) - channel_name_template: "{{ '{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}' }}" + # .Name - Channel name, or user displayname (pre-formatted with displayname_template) in DMs. + # .ParentName - Parent channel name (used for categories). + # .GuildName - Guild name. + # .NSFW - Whether the channel is marked as NSFW. + # .Type - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267) + channel_name_template: {{ matrix_mautrix_discord_bridge_channel_name_template | to_json }} # Displayname template for Discord guilds (bridged as spaces). # Available variables: - # {{ '{{.Name}}' }} - Guild name - guild_name_template: "{{ '{{.Name}}' }}" - # Should the bridge explicitly set the avatar and room name for DM portal rooms? - # This is implicitly enabled in encrypted rooms. + # .Name - Guild name + guild_name_template: {{ matrix_mautrix_discord_bridge_guild_name_template | to_json }} # Whether to explicitly set the avatar and room name for private chat portal rooms. # If set to `default`, this will be enabled in encrypted rooms and disabled in unencrypted rooms. # If set to `always`, all DM rooms will have explicit names and avatars set. # If set to `never`, DM rooms will never have names and avatars set. private_chat_portal_meta: default + + # Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode. + # If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address. + # This should not have a trailing slash, the endpoint above will be appended to the provided address. + public_address: {{ matrix_mautrix_discord_bridge_public_address | to_json }} + # A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature. + avatar_proxy_key: {{ matrix_mautrix_discord_bridge_avatar_proxy_key | to_json }} + portal_message_buffer: 128 + # Number of private channel portals to create on bridge startup. # Other portals will be created when receiving messages. startup_private_channel_create_limit: 5 # Should the bridge send a read receipt from the bridge bot when a message has been sent to Discord? delivery_receipts: false # Whether the bridge should send the message status as a custom com.beeper.message_send_status event. - message_status_events: true + message_status_events: false # Whether the bridge should send error notices via m.notice events when a message fails to bridge. message_error_notices: true # Should the bridge use space-restricted join rules instead of invite-only for guild rooms? # This can avoid unnecessary invite events in guild rooms when members are synced in. - restricted_rooms: {{ matrix_mautrix_discord_bridge_restricted_rooms|to_json }} + restricted_rooms: {{ matrix_mautrix_discord_bridge_restricted_rooms | to_json }} + # Should the bridge automatically join the user to threads on Discord when the thread is opened on Matrix? + # This only works with clients that support thread read receipts (MSC3771 added in Matrix v1.4). + autojoin_thread_on_open: true + # Should inline fields in Discord embeds be bridged as HTML tables to Matrix? + # Tables aren't supported in all clients, but are the only way to emulate the Discord inline field UI. + embed_fields_as_tables: true + # Should guild channels be muted when the portal is created? This only meant for single-user instances, + # it won't mute it for all users if there are multiple Matrix users in the same Discord guild. + mute_channels_on_create: false # Should the bridge update the m.direct account data event when double puppeting is enabled. # Note that updating the m.direct event is not atomic (except with mautrix-asmux) # and is therefore prone to race conditions. @@ -120,7 +149,7 @@ bridge: # This field will automatically be changed back to false after it, except if the config file is not writable. resend_bridge_info: false # Should incoming custom emoji reactions be bridged as mxc:// URIs? - # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image wont be available. + # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image won't be available. custom_emoji_reactions: true # Should the bridge attempt to completely delete portal rooms when a channel is deleted on Discord? # If true, the bridge will try to kick Matrix users from the room. Otherwise, the bridge only makes ghosts leave. @@ -130,7 +159,7 @@ bridge: delete_guild_on_leave: true # Whether or not created rooms should have federation enabled. # If false, created portal rooms will never be federated. - federate_rooms: {{ matrix_mautrix_discord_federate_rooms|to_json }} + federate_rooms: {{ matrix_mautrix_discord_federate_rooms | to_json }} # Prefix messages from webhooks with the profile info? This can be used along with a custom displayname_template # to better handle webhooks that change their name all the time (like ones used by bridges). prefix_webhook_messages: false @@ -140,24 +169,29 @@ bridge: # like the official client does? The other option is sending the media in the message send request as a form part # (which is always used by bots and webhooks). use_discord_cdn_upload: true + # Proxy for Discord connections + proxy: # Should mxc uris copied from Discord be cached? # This can be `never` to never cache, `unencrypted` to only cache unencrypted mxc uris, or `always` to cache everything. # If you have a media repo that generates non-unique mxc uris, you should set this to never. cache_media: unencrypted - # Patterns for converting Discord media to custom mxc:// URIs instead of reuploading. - # Each of the patterns can be set to null to disable custom URIs for that type of media. + # Settings for converting Discord media to custom mxc:// URIs instead of reuploading. # More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html - media_patterns: + direct_media: # Should custom mxc:// URIs be used instead of reuploading media? enabled: false - # Pattern for normal message attachments. - attachments: {% raw %}mxc://discord-media.mau.dev/attachments|{{.ChannelID}}|{{.AttachmentID}}|{{.FileName}}{% endraw %} - # Pattern for custom emojis. - emojis: {% raw %}mxc://discord-media.mau.dev/emojis|{{.ID}}.{{.Ext}}{% endraw %} - # Pattern for stickers. Note that animated lottie stickers will not be converted if this is enabled. - stickers: {% raw %}mxc://discord-media.mau.dev/stickers|{{.ID}}.{{.Ext}}{% endraw %} - # Pattern for static user avatars. - avatars: {% raw %}mxc://discord-media.mau.dev/avatars|{{.UserID}}|{{.AvatarID}}.{{.Ext}}{% endraw %} + # The server name to use for the custom mxc:// URIs. + # This server name will effectively be a real Matrix server, it just won't implement anything other than media. + # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge. + server_name: discord-media.example.com + # Optionally a custom .well-known response. This defaults to `server_name:443` + well_known_response: + # The bridge supports MSC3860 media download redirects and will use them if the requester supports it. + # Optionally, you can force redirects and not allow proxying at all by setting this to false. + allow_proxy: true + # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file. + # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them. + server_key: "" # Settings for converting animated stickers. animated_sticker: # Format to which animated stickers should be converted. @@ -181,11 +215,10 @@ bridge: # If set, double puppeting will be enabled automatically for local users # instead of users having to find an access token and run `login-matrix` # manually. - login_shared_secret_map: {{ matrix_mautrix_discord_bridge_login_shared_secret_map|to_json }} + login_shared_secret_map: {{ matrix_mautrix_discord_bridge_login_shared_secret_map | to_json }} # The prefix for commands. Only required in non-management rooms. - command_prefix: "{{ matrix_mautrix_discord_command_prefix }}" - + command_prefix: {{ matrix_mautrix_discord_bridge_command_prefix | to_json }} # Messages sent upon joining a management room. # Markdown is supported. The defaults are listed below. management_room_text: @@ -227,15 +260,40 @@ bridge: # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info. encryption: # Allow encryption, work in group chat rooms with e2ee enabled - allow: {{ matrix_mautrix_discord_bridge_encryption_allow|to_json }} + allow: {{ matrix_mautrix_discord_bridge_encryption_allow | to_json }} # Default to encryption, force-enable encryption in all portals the bridge creates # This will cause the bridge bot to be in private chats for the encryption to work properly. - default: {{ matrix_mautrix_discord_bridge_encryption_default|to_json }} + default: {{ matrix_mautrix_discord_bridge_encryption_default | to_json }} + # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data. + appservice: {{ matrix_mautrix_discord_bridge_encryption_appservice | to_json}} # Require encryption, drop any unencrypted messages. - require: false + require: {{ matrix_mautrix_discord_bridge_encryption_require | to_json }} # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. # You must use a client that supports requesting keys from other users to use this feature. - allow_key_sharing: {{ matrix_mautrix_discord_bridge_encryption_key_sharing_allow|to_json }} + allow_key_sharing: {{ matrix_mautrix_discord_bridge_encryption_key_sharing_allow | to_json }} + # Should users mentions be in the event wire content to enable the server to send push notifications? + plaintext_mentions: {{ matrix_mautrix_discord_bridge_encryption_plaintext_mentions | to_json }} + # Options for deleting megolm sessions from the bridge. + delete_keys: + # Beeper-specific: delete outbound sessions when hungryserv confirms + # that the user has uploaded the key to key backup. + delete_outbound_on_ack: false + # Don't store outbound sessions in the inbound table. + dont_store_outbound: false + # Ratchet megolm sessions forward after decrypting messages. + ratchet_on_decrypt: false + # Delete fully used keys (index >= max_messages) after decrypting messages. + delete_fully_used_on_decrypt: false + # Delete previous megolm sessions from same device when receiving a new one. + delete_prev_on_new_session: false + # Delete megolm sessions received from a device when the device is deleted. + delete_on_device_delete: false + # Periodically delete megolm sessions when 2x max_age has passed since receiving the session. + periodically_delete_expired: false + # Delete inbound megolm sessions that don't have the received_at field used for + # automatic ratcheting and expired session deletion. This is meant as a migration + # to delete old keys prior to the bridge update. + delete_outdated_inbound: false # What level of device verification should be required from users? # # Valid levels: @@ -271,6 +329,10 @@ bridge: # default. messages: 100 + # Disable rotating keys when a user's devices change? + # You should not enable this option unless you understand all the implications. + disable_device_change_key_rotation: false + # Settings for provisioning API provisioning: # Prefix for the provisioning API paths. @@ -278,6 +340,8 @@ bridge: # Shared secret for authentication. If set to "generate", a random secret will be generated, # or if set to "disable", the provisioning API will be disabled. shared_secret: {{ matrix_mautrix_discord_provisioning_shared_secret | to_json }} + # Enable debug API at /debug with provisioning authentication. + debug_endpoints: false # Permissions for using the bridge. # Permitted values: @@ -290,12 +354,9 @@ bridge: # mxid - Specific user permissions: {{ matrix_mautrix_discord_bridge_permissions|to_json }} +# Logging config. See https://github.com/tulir/zeroconfig for details. logging: - directory: ./logs - file_name_format: '' - file_date_format: "2006-01-02" - file_mode: 384 - timestamp_format: Jan _2, 2006 15:04:05 - print_level: {{ matrix_mautrix_discord_logging_level | to_json }} - print_json: false - file_json: false + min_level: {{ matrix_mautrix_discord_logging_level | to_json }} + writers: + - type: stdout + format: pretty-colored From cea437c84440c6841eb32923c9e3a46d72214d48 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:36:18 +0200 Subject: [PATCH 146/952] Expose mautrix-discord's avatar proxy Possibly fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3900 This patch hasn't been tested. --- group_vars/matrix_servers | 11 +++- .../defaults/main.yml | 38 +++++++++++- .../tasks/setup_install.yml | 10 ++++ .../tasks/validate_config.yml | 2 + .../templates/labels.j2 | 58 +++++++++++++++++++ .../systemd/matrix-mautrix-discord.service.j2 | 1 + 6 files changed, 118 insertions(+), 2 deletions(-) create mode 100644 roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 4331a7a83..9cd2edbd0 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -1103,9 +1103,16 @@ matrix_mautrix_discord_container_additional_networks_auto: |- ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) + ([postgres_container_network] if postgres_enabled and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname else []) + + + ([matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_playbook_reverse_proxyable_services_additional_network and matrix_mautrix_discord_container_labels_traefik_enabled) else []) ) | unique }} +matrix_mautrix_discord_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" +matrix_mautrix_discord_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" +matrix_mautrix_discord_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" +matrix_mautrix_discord_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" + matrix_mautrix_discord_systemd_required_services_list_auto: | {{ matrix_addons_homeserver_systemd_services_list @@ -1118,9 +1125,11 @@ matrix_mautrix_discord_appservice_token: "{{ '%s' | format(matrix_homeserver_gen matrix_mautrix_discord_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" matrix_mautrix_discord_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.hs.tok', rounds=655555) | to_uuid }}" -matrix_mautrix_discord_bridge_public_address: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_server_fqn_matrix }}" matrix_mautrix_discord_bridge_avatar_proxy_key: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.avatar', rounds=655555) | to_uuid }}" +matrix_mautrix_discord_hostname: "{{ matrix_server_fqn_matrix }}" +matrix_mautrix_discord_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" + matrix_mautrix_discord_bridge_login_shared_secret_map_auto: |- {{ ({ diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index 913f2d363..f362a702a 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -4,6 +4,10 @@ matrix_mautrix_discord_enabled: true +matrix_mautrix_discord_hostname: "" +matrix_mautrix_discord_path_prefix: / +matrix_mautrix_discord_scheme: https + matrix_mautrix_discord_container_image_self_build: false matrix_mautrix_discord_container_image_self_build_repo: "https://mau.dev/mautrix/discord.git" matrix_mautrix_discord_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_discord_version == 'latest' else matrix_mautrix_discord_version }}" @@ -30,7 +34,7 @@ matrix_mautrix_discord_bridge_command_prefix: "!discord" # Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode. # If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address. # This should not have a trailing slash, the endpoint above will be appended to the provided address. -matrix_mautrix_discord_bridge_public_address: '' +matrix_mautrix_discord_bridge_public_address: "{{ (matrix_mautrix_discord_scheme + '://' + matrix_mautrix_discord_hostname + (matrix_mautrix_discord_path_prefix if matrix_mautrix_discord_path_prefix != '/' else '')) if matrix_mautrix_discord_hostname else '' }}" # A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature. matrix_mautrix_discord_bridge_avatar_proxy_key: '' @@ -60,6 +64,38 @@ matrix_mautrix_discord_container_additional_networks: "{{ matrix_mautrix_discord matrix_mautrix_discord_container_additional_networks_auto: [] matrix_mautrix_discord_container_additional_networks_custom: [] +# matrix_mautrix_discord_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. +# See `../templates/labels.j2` for details. +# +# To inject your own other container labels, see `matrix_mautrix_discord_container_labels_additional_labels`. +matrix_mautrix_discord_container_labels_traefik_enabled: true +matrix_mautrix_discord_container_labels_traefik_docker_network: "{{ matrix_mautrix_discord_container_network }}" +matrix_mautrix_discord_container_labels_traefik_hostname: "{{ matrix_mautrix_discord_hostname }}" +# The path prefix must either be `/` or not end with a slash (e.g. `/matrix-alertmanager-receiver`). +matrix_mautrix_discord_container_labels_traefik_path_prefix: "{{ matrix_mautrix_discord_path_prefix }}" +matrix_mautrix_discord_container_labels_traefik_entrypoints: web-secure +matrix_mautrix_discord_container_labels_traefik_tls_certResolver: default # noqa var-naming + +# Controls whether labels will be added that expose the bridge's avatar proxy (`/mautrix-discord/avatar/{server}/{id}/{hash}`). +# See: matrix_mautrix_discord_bridge_public_address +matrix_mautrix_discord_container_labels_avatar_proxy_enabled: "{{ matrix_mautrix_discord_bridge_public_address != '' }}" +matrix_mautrix_discord_container_labels_avatar_proxy_hostname: "{{ matrix_mautrix_discord_container_labels_traefik_hostname }}" +matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix: "{{ matrix_mautrix_discord_container_labels_traefik_path_prefix if matrix_mautrix_discord_container_labels_traefik_path_prefix == '/' else (matrix_mautrix_discord_container_labels_traefik_path_prefix + '/') }}mautrix-discord/avatar" +matrix_mautrix_discord_container_labels_avatar_proxy_traefik_rule: "Host(`{{ matrix_mautrix_discord_container_labels_traefik_hostname }}`) && PathPrefix(`{{ matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix }}`)" +matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority: 0 +matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints: "{{ matrix_mautrix_discord_container_labels_traefik_entrypoints }}" +matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints != 'web' }}" +matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls_certResolver: "{{ matrix_mautrix_discord_container_labels_traefik_tls_certResolver }}" # noqa var-naming + +# matrix_mautrix_discord_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. +# See `../templates/labels.j2` for details. +# +# Example: +# matrix_mautrix_discord_container_labels_additional_labels: | +# my.label=1 +# another.label="here" +matrix_mautrix_discord_container_labels_additional_labels: '' + # A list of extra arguments to pass to the container matrix_mautrix_discord_container_extra_arguments: [] diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml index 4775b5fee..a83092973 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml @@ -93,6 +93,16 @@ owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" +- name: Ensure mautrix-discord support files installed + ansible.builtin.template: + src: "{{ role_path }}/templates/{{ item }}.j2" + dest: "{{ matrix_mautrix_discord_base_path }}/{{ item }}" + mode: 0640 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - labels + - name: Ensure mautrix-discord container network is created community.general.docker_network: enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml index 5251564e5..25b4773c9 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml @@ -12,6 +12,8 @@ - {'name': 'matrix_mautrix_discord_bridge_public_address', when: true} - {'name': 'matrix_mautrix_discord_container_network', when: true} - {'name': 'matrix_mautrix_discord_database_hostname', when: "{{ matrix_mautrix_discord_database_engine == 'postgres' }}"} + - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_hostname', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"} + - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"} - name: (Deprecation) Catch and report renamed settings ansible.builtin.fail: diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 new file mode 100644 index 000000000..adc265db2 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 @@ -0,0 +1,58 @@ +{% if matrix_mautrix_discord_container_labels_traefik_enabled %} +traefik.enable=true + +{% if matrix_mautrix_discord_container_labels_traefik_docker_network %} +traefik.docker.network={{ matrix_mautrix_discord_container_labels_traefik_docker_network }} +{% endif %} + +traefik.http.services.matrix-mautrix-discord.loadbalancer.server.port=8080 + +{% if matrix_mautrix_discord_container_labels_avatar_proxy_enabled %} +############################################################ +# # +# Avatar proxy # +# # +############################################################ + +{% set middlewares = [] %} + +{% if matrix_mautrix_discord_container_labels_traefik_path_prefix != '/' %} +traefik.http.middlewares.matrix-mautrix-discord-slashless-redirect.redirectregex.regex=({{ matrix_mautrix_discord_container_labels_traefik_path_prefix | quote }})$ +traefik.http.middlewares.matrix-mautrix-discord-slashless-redirect.redirectregex.replacement=${1}/ +{% set middlewares = middlewares + ['matrix-mautrix-discord-slashless-redirect'] %} +{% endif %} + +{% if matrix_mautrix_discord_container_labels_traefik_path_prefix != '/' %} +traefik.http.middlewares.matrix-mautrix-discord-strip-prefix.stripprefix.prefixes={{ matrix_mautrix_discord_container_labels_traefik_path_prefix }} +{% set middlewares = middlewares + ['matrix-mautrix-discord-strip-prefix'] %} +{% endif %} + +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.rule={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_rule }} + +{% if matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority | int > 0 %} +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.priority={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority }} +{% endif %} + +{% if middlewares | length > 0 %} +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.middlewares={{ middlewares | join(',') }} +{% endif %} + +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.service=matrix-mautrix-discord +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.entrypoints={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints }} + +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.tls={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls | to_json }} +{% if matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls %} +traefik.http.routers.matrix-mautrix-discord-avatar-proxy.tls.certResolver={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Avatar proxy # +# # +############################################################ +{% endif %} + + +{% endif %} + +{{ matrix_mautrix_discord_container_labels_additional_labels }} diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 index 0a5167baf..cd853e1a9 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 @@ -23,6 +23,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ --cap-drop=ALL \ --network={{ matrix_mautrix_discord_container_network }} \ + --label-file={{ matrix_mautrix_discord_base_path }}/labels \ --mount type=bind,src={{ matrix_mautrix_discord_config_path }},dst=/config,ro \ --mount type=bind,src={{ matrix_mautrix_discord_data_path }},dst=/data \ --workdir=/data \ From 47a337258c2488327fbf897d77370d7d76b8e5e1 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:55:48 +0200 Subject: [PATCH 147/952] Only create docker-src directory for matrix-registration-bot when self building is enabled --- .../matrix-bot-matrix-registration-bot/tasks/setup_install.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml index d50c0f860..c1ae8a704 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml @@ -10,7 +10,7 @@ with_items: - {path: "{{ matrix_bot_matrix_registration_bot_config_path }}", when: true} - {path: "{{ matrix_bot_matrix_registration_bot_data_path }}", when: true} - - {path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}", when: true} + - {path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}", when: "{{ matrix_bot_matrix_registration_bot_container_image_self_build }}"} when: "item.when | bool" - name: Ensure matrix-registration-bot configuration file created From 358b3486f9425fb1cfffd76f3062e249069f42a7 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:56:08 +0200 Subject: [PATCH 148/952] Group matrix-registration-bot's self-building tasks in a block --- .../tasks/setup_install.yml | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml index c1ae8a704..0c3284bc0 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml @@ -33,28 +33,28 @@ delay: "{{ devture_playbook_help_container_retries_delay }}" until: result is not failed -- name: Ensure matrix-registration-bot repository is present on self-build - ansible.builtin.git: - repo: "{{ matrix_bot_matrix_registration_bot_docker_repo }}" - version: "{{ matrix_bot_matrix_registration_bot_docker_repo_version }}" - dest: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}" - force: "yes" - become: true - become_user: "{{ matrix_user_username }}" - register: matrix_bot_matrix_registration_bot_git_pull_results - when: "matrix_bot_matrix_registration_bot_container_image_self_build | bool" +- when: matrix_bot_matrix_registration_bot_container_image_self_build | bool + block: + - name: Ensure matrix-registration-bot repository is present on self-build + ansible.builtin.git: + repo: "{{ matrix_bot_matrix_registration_bot_docker_repo }}" + version: "{{ matrix_bot_matrix_registration_bot_docker_repo_version }}" + dest: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}" + force: "yes" + become: true + become_user: "{{ matrix_user_username }}" + register: matrix_bot_matrix_registration_bot_git_pull_results -- name: Ensure matrix-registration-bot image is built - community.docker.docker_image: - name: "{{ matrix_bot_matrix_registration_bot_docker_image }}" - source: build - force_source: "{{ matrix_bot_matrix_registration_bot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_matrix_registration_bot_git_pull_results.changed }}" - build: - dockerfile: Dockerfile - path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}" - pull: true - when: "matrix_bot_matrix_registration_bot_container_image_self_build | bool" + - name: Ensure matrix-registration-bot image is built + community.docker.docker_image: + name: "{{ matrix_bot_matrix_registration_bot_docker_image }}" + source: build + force_source: "{{ matrix_bot_matrix_registration_bot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_matrix_registration_bot_git_pull_results.changed }}" + build: + dockerfile: Dockerfile + path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}" + pull: true - name: Ensure matrix-registration-bot container network is created community.general.docker_network: From 4d39efe6f6df2de8a7e2350b07cd3031c7379e92 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:58:35 +0200 Subject: [PATCH 149/952] Rename variable (`matrix_bot_matrix_registration_bot_matrix_homeserver_url` -> `matrix_bot_matrix_registration_bot_api_base_url`) We were overriding the `matrix_bot_matrix_registration_bot_matrix_homeserver_url` variable via `group_vars/matrix_servers` to point it to the container-local homeserver URL, but this variable was not being used at all. The actual variable name (which was being used) is `matrix_bot_matrix_registration_bot_api_base_url`. Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3898 --- group_vars/matrix_servers | 2 +- .../defaults/main.yml | 2 -- .../tasks/validate_config.yml | 12 +++++++----- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 9cd2edbd0..26511a65b 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -2737,7 +2737,7 @@ matrix_bot_matrix_registration_bot_container_additional_networks_auto: |- ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) }} -matrix_bot_matrix_registration_bot_matrix_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" +matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_addons_homeserver_client_api_url }}" ###################################################################### # diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index f44196d43..3f43ed920 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -57,5 +57,3 @@ matrix_bot_matrix_registration_bot_systemd_wanted_services_list: [] matrix_bot_matrix_registration_bot_matrix_user_id_localpart: "bot.matrix-registration-bot" matrix_bot_matrix_registration_bot_matrix_user_id: '@{{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart }}:{{ matrix_domain }}' - -matrix_bot_matrix_registration_bot_matrix_homeserver_url: "" diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml index 9830c5323..fb5e7de5c 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml @@ -7,12 +7,14 @@ when: "vars[item] == ''" with_items: - "matrix_bot_matrix_registration_bot_bot_password" - - "matrix_bot_matrix_registration_bot_matrix_homeserver_url" + - "matrix_bot_matrix_registration_bot_api_base_url" -- name: (Deprecation) Catch and report old settings +- name: (Deprecation) Catch and report renamed settings ansible.builtin.fail: msg: >- - Your configuration contains a variable, which is deprecated - Please check the documentation on how to configure the matrix-registration-bot. - when: "item in vars" + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" with_items: - - "matrix_bot_matrix_registration_bot_bot_access_token" + - {'old': 'matrix_bot_matrix_registration_bot_bot_access_token', 'new': ''} + - {'old': 'matrix_bot_matrix_registration_bot_matrix_homeserver_url', 'new': 'matrix_bot_matrix_registration_bot_api_base_url'} From d89e627a799e3ab563974a3f076c13309197bd3b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 08:59:04 +0200 Subject: [PATCH 150/952] Move some matrix-registration-bot variables around --- .../defaults/main.yml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index 3f43ed920..ba1fc7273 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -20,12 +20,19 @@ matrix_bot_matrix_registration_bot_config_path: "{{ matrix_bot_matrix_registrati matrix_bot_matrix_registration_bot_data_path: "{{ matrix_bot_matrix_registration_bot_base_path }}/data" matrix_bot_matrix_registration_bot_bot_server: "{{ matrix_homeserver_url }}" -matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_url }}" +# The bot's username. This user needs to be created manually beforehand. +# Also see `matrix_bot_matrix_registration_bot_user_password`. +matrix_bot_matrix_registration_bot_matrix_user_id_localpart: "bot.matrix-registration-bot" + +matrix_bot_matrix_registration_bot_matrix_user_id: '@{{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart }}:{{ matrix_domain }}' # The bot's password (can also be used to login via a client like Element Web) matrix_bot_matrix_registration_bot_bot_password: '' +# Homeserver base URL +matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_url }}" + # Optional variable that only needs to be set if the bot account is not admin # Needs to be a valid access token of an admin account matrix_bot_matrix_registration_bot_api_token: '' @@ -51,9 +58,3 @@ matrix_bot_matrix_registration_bot_systemd_required_services_list_custom: [] # List of systemd services that matrix-bot-matrix-registration-bot.service wants matrix_bot_matrix_registration_bot_systemd_wanted_services_list: [] - -# The bot's username. This user needs to be created manually beforehand. -# Also see `matrix_bot_matrix_registration_bot_user_password`. -matrix_bot_matrix_registration_bot_matrix_user_id_localpart: "bot.matrix-registration-bot" - -matrix_bot_matrix_registration_bot_matrix_user_id: '@{{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart }}:{{ matrix_domain }}' From 11a90a47893fe86972139f903f8af87117f52432 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 23 Dec 2024 09:02:58 +0200 Subject: [PATCH 151/952] Move matrix-registration-bot's token comment inside the if statement --- .../templates/config/config.yml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 index 4a2242aa2..7ea2b9d0a 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 +++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 @@ -6,8 +6,8 @@ bot: api: # API endpoint of the registration tokens base_url: {{ matrix_bot_matrix_registration_bot_api_base_url|to_json }} - # Access token of an administrator on the server {% if matrix_bot_matrix_registration_bot_api_token | length > 0 %} + # Access token of an administrator on the server token: {{ matrix_bot_matrix_registration_bot_api_token|to_json }} {% endif %} From 3ad2211d742934a49ce45e736b47e702a564f689 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 10:47:54 +0900 Subject: [PATCH 152/952] Use common instructions for referring to the documentation on obtaining an access token Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-maubot.md | 2 +- docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-user-verification-service.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 04eeb0cb8..2e43df041 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -79,4 +79,4 @@ You should start in the following order This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`. -Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients). +Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients). diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 6566015d8..6b7362c1d 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -30,7 +30,7 @@ The admin interface is accessible within Element Web by accessing it in any room We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**. -You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md). +You are required to specify an access token (belonging to this new user) for Dimension to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). **Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.** diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 37802c30a..cf89fcca7 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -45,7 +45,7 @@ The Synapse Access Token is used to verify RoomMembership and PowerLevel against We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges. -You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md). +You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). **Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.** From fb05eace5a17886945cf02452a906ed607dc24b6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 18:14:33 +0900 Subject: [PATCH 153/952] Edit instructions to obtain an access token Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-kakaotalk.md | 2 +- docs/configuring-playbook-bridge-mautrix-discord.md | 2 +- docs/configuring-playbook-bridge-mautrix-facebook.md | 2 +- docs/configuring-playbook-bridge-mautrix-gmessages.md | 2 +- docs/configuring-playbook-bridge-mautrix-googlechat.md | 2 +- docs/configuring-playbook-bridge-mautrix-hangouts.md | 2 +- docs/configuring-playbook-bridge-mautrix-meta-instagram.md | 2 +- docs/configuring-playbook-bridge-mautrix-meta-messenger.md | 2 +- docs/configuring-playbook-bridge-mautrix-signal.md | 2 +- docs/configuring-playbook-bridge-mautrix-slack.md | 2 +- docs/configuring-playbook-bridge-mautrix-telegram.md | 2 +- docs/configuring-playbook-bridge-mautrix-twitter.md | 2 +- docs/configuring-playbook-bridge-mautrix-whatsapp.md | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index f5dfcbe9f..e10f880a8 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -70,7 +70,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index fbcd2b1e8..df93b246c 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -101,7 +101,7 @@ Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playb When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index e42d58058..8baf793b9 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -96,7 +96,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index 1ca27424e..40305e06b 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -55,7 +55,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index ac16c09ba..2b077dfcf 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -65,7 +65,7 @@ Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playb When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index ba0fecbe4..e2a808ec3 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -65,7 +65,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index 5e11f50e7..6514cac90 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -104,7 +104,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 65afac8d0..9e40720bb 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -121,7 +121,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index ef2102441..f89ca1c42 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -106,7 +106,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 19f0f75aa..dd2ee5342 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -82,7 +82,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index 835bc87fb..fc775f61c 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -88,7 +88,7 @@ Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playb When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send `login-matrix` to the bot and follow instructions about how to send the access token to it diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index 7aeaca436..81813d2d1 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -62,7 +62,7 @@ This is the recommended way of setting up Double Puppeting, as it's easier to ac When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index a3bc81559..2fa6e9914 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -73,7 +73,7 @@ Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playb When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md). +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` From 7911cdb23213e8e4a9fc74e5c098b3ceb325509a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 11:01:30 +0900 Subject: [PATCH 154/952] Add a common warning message about not to share an access token Based on docs/obtaining-access-tokens.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 2 ++ docs/configuring-playbook-bot-chatgpt.md | 2 ++ docs/configuring-playbook-bot-draupnir.md | 2 ++ docs/configuring-playbook-bot-go-neb.md | 2 ++ docs/configuring-playbook-bot-maubot.md | 2 ++ docs/configuring-playbook-bot-mjolnir.md | 2 ++ docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-email2matrix.md | 2 ++ docs/configuring-playbook-user-verification-service.md | 2 +- docs/maintenance-synapse.md | 2 ++ docs/obtaining-access-tokens.md | 2 +- 11 files changed, 19 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index c42747e99..351432662 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -26,6 +26,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertma The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + ### Join to rooms as the bot manually ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually. diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index e3ff7a431..3ed5ef729 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -28,6 +28,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6). ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 288a8547c..3863b616b 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -28,6 +28,8 @@ If you would like Draupnir to be able to deactivate users, move aliases, shutdow The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + ### Make sure the account is free from rate limiting If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.** diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 1c3118dfb..c8c84f876 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -26,6 +26,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + ## Adjusting the playbook configuration 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). diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 2e43df041..cab21137e 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -80,3 +80,5 @@ You should start in the following order This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`. Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients). + +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 53fd17784..e7737420b 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -24,6 +24,8 @@ If you would like Mjolnir to be able to deactivate users, move aliases, shutdown The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + ### Make sure the account is free from rate limiting If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.** diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 6b7362c1d..90d299e17 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -32,7 +32,7 @@ We recommend that you create a dedicated Matrix user for Dimension (`dimension` You are required to specify an access token (belonging to this new user) for Dimension to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.** +⚠️ **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. Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 4ceda308f..f57904986 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -42,6 +42,8 @@ Take note of each room's room ID (different clients show the room ID in a differ In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + ## Adjusting the playbook configuration After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index cf89fcca7..341026ab8 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -47,7 +47,7 @@ We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good us You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.** +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ```yaml matrix_user_verification_service_uvs_access_token: "YOUR ACCESS TOKEN HERE" diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index 749e9deba..0c2eded9b 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -18,6 +18,8 @@ You can use the **[Purge History API](https://github.com/element-hq/synapse/blob To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. + Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file. Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions. diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index 860621f70..e1f69b226 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -2,7 +2,7 @@ When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token. -**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.** +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Prerequisites From 66ea709cb32478ae3fc22ae32ffee8b057e0080c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 11:22:31 +0900 Subject: [PATCH 155/952] Replace headers for sections about obtaining an access token Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-user-verification-service.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 90d299e17..652ed6e83 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -26,7 +26,7 @@ matrix_dimension_admins: The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the "Add widgets, bridges, & bots" link in the room information. -### Access token +### Obtain an access token We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**. diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 341026ab8..6a8dfccb9 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -39,7 +39,7 @@ For a list of all configuration options see the role defaults [`roles/matrix-use In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`. -### Access token +### Obtain an access token The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. From 4798888ac7fa0ce5bbe16caaf58361706668a7ae Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 12:14:52 +0900 Subject: [PATCH 156/952] Edit docs/configuring-playbook-dimension.md: adopt the common instruction for introduction and prerequisites - Register a dedicated Matrix user (optional) - Obtain an access token Since Dimension has been archived, this is purely for possible use as a template of another component. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 52 ++++++++++++++++---------- 1 file changed, 32 insertions(+), 20 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 652ed6e83..129911bcd 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -1,17 +1,45 @@ # Setting up Dimension integration manager (optional, unmaintained) -**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later. +**Notes**: +- Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it. +- This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible). -**Note**: Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it. +The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you. -**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible). +See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you. + +## Prerequisites + +### Install Matrix services + +Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later. + +### Register a dedicated Matrix user (optional) + +We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). + +Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`. + +You can use the playbook to [register a new user](registering-users.md): + +```sh +ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=dimension password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user +``` + +### Obtain an access token + +Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). + +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Adjusting the playbook configuration -To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): +To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_dimension_enabled: true + +matrix_dimension_access_token: "ACCESS_TOKEN_HERE" ``` ### Define admin users @@ -26,22 +54,6 @@ matrix_dimension_admins: 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. -### Obtain an access token - -We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**. - -You are required to specify an access token (belonging to this new user) for Dimension to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. - -Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): - -```yaml -matrix_dimension_access_token: "YOUR ACCESS TOKEN HERE" -``` - -For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens). - ### Adjusting the Dimension URL By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). From 2c80aaf980764d4b96f2f80305331f49c2d7b411 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 12:21:31 +0900 Subject: [PATCH 157/952] Edit docs/configuring-playbook-email2matrix.md: adopt the common instruction Based on docs/configuring-playbook-dimension.md and docs/configuring-playbook-bot-go-neb.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email2matrix.md | 33 ++++++++++++++--------- 1 file changed, 21 insertions(+), 12 deletions(-) diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index f57904986..533576bab 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -22,11 +22,25 @@ If you really need to run an email server on the Matrix machine for other purpos For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md). -### Creating a user +### Register a dedicated Matrix user (optional) -Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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. +We recommend that you create a dedicated Matrix user for Email2Matrix. -Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best. +Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`. + +You can use the playbook to [register a new user](registering-users.md): + +```sh +ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=email2matrix password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user +``` + +Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later. + +### Obtain an access token + +Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). + +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Creating a shared room @@ -38,25 +52,20 @@ Inviting additional people to the room is okay too. 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. -### Obtain an access token for the sender user - -In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. - ## Adjusting the playbook configuration -After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token). ```yaml matrix_email2matrix_enabled: true +# You need at least 1 mailbox. matrix_email2matrix_matrix_mappings: - MailboxName: "mailbox1" MatrixRoomId: "!qporfwt:{{ matrix_domain }}" MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" MatrixUserId: "@email2matrix1:{{ matrix_domain }}" - MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE" + MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE" IgnoreSubject: false IgnoreBody: false SkipMarkdown: false @@ -65,7 +74,7 @@ matrix_email2matrix_matrix_mappings: MatrixRoomId: "!aaabaa:{{ matrix_domain }}" MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" MatrixUserId: "@email2matrix2:{{ matrix_domain }}" - MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE" + MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE" IgnoreSubject: true IgnoreBody: false SkipMarkdown: true From a2b92432470ccbf38cbc87b419d6c3a1da82d5c5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 13:07:56 +0900 Subject: [PATCH 158/952] Edit docs/configuring-playbook-email2matrix.md: adopt the common instruction about registering a dedicated user Based on docs/configuring-playbook-alertmanager-receiver.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email2matrix.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 533576bab..8bbc9f1a8 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -42,13 +42,15 @@ Email2Matrix requires an access token for the sender user to be able to send mes ⚠️ **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. -### Creating a shared room +### Join to rooms as the sender user manually -After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user). +ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually. -What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there. +For each new room you would like the user to deliver messages to, invite the user to the room. -Inviting additional people to the room is okay too. +Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account. + +Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out. Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below. From 362d9cabd8c65350a56af86e08d32c5f4beb726a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 15:06:46 +0900 Subject: [PATCH 159/952] Update docs: add "recommended" to the "optional" label on the headers Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 2 +- docs/configuring-playbook-email2matrix.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 129911bcd..5e7e86b15 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -14,7 +14,7 @@ See the project's [documentation](https://github.com/turt2live/matrix-dimension/ Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later. -### Register a dedicated Matrix user (optional) +### Register a dedicated Matrix user (optional, recommended) We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 8bbc9f1a8..86a1052b2 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -22,7 +22,7 @@ If you really need to run an email server on the Matrix machine for other purpos For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md). -### Register a dedicated Matrix user (optional) +### Register a dedicated Matrix user (optional, recommended) We recommend that you create a dedicated Matrix user for Email2Matrix. From 40ef348c485dfea9b087bcf80a72489b264d694d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 24 Dec 2024 00:11:00 +0900 Subject: [PATCH 160/952] Update docs: Move "(optional)" on headers to the end of the line Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 12 ++++++------ ...configuring-playbook-user-verification-service.md | 6 +++--- docs/configuring-well-known.md | 2 +- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index dcb0a4232..69b93906b 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -40,7 +40,7 @@ Once you've decided on the domain and path, **you may need to adjust your DNS** By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. -## (Optional) Configure Jitsi authentication and guests mode +## Configure Jitsi authentication and guests mode (optional) By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration. @@ -112,7 +112,7 @@ jitsi_ldap_start_tls: false For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation. -## (Optional) Making your Jitsi server work on a LAN +## Making your Jitsi server work on a LAN (optional) By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok. @@ -127,7 +127,7 @@ jitsi_jvb_container_extra_arguments: - '--env "JVB_ADVERTISE_IPS="' ``` -## (Optional) Fine tune Jitsi +## Fine tune Jitsi (optional) Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below): @@ -152,7 +152,7 @@ You may want to **limit the number of video feeds forwarded to each client**, to You may want to **limit the maximum video resolution**, to save up resources on both server and clients. -## (Optional) Specify a Max number of participants on a Jitsi conference +## Specify a Max number of participants on a Jitsi conference (optional) The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit. @@ -162,7 +162,7 @@ In order to set the max number of participants use the following **additional** jitsi_prosody_max_participants: 4 # example value ``` -## (Optional) Additional JVBs +## Additional JVBs (optional) By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts. @@ -253,7 +253,7 @@ traefik_provider_configuration_extension_yaml: | {% endfor %} ``` -## (Optional) Enable Gravatar +## Enable Gravatar (optional) In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar. diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 6a8dfccb9..09e5ae1dd 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -53,7 +53,7 @@ You are required to specify an access token (belonging to this new user) for UVS matrix_user_verification_service_uvs_access_token: "YOUR ACCESS TOKEN HERE" ``` -### (Optional) Custom Auth Token +### Custom Auth Token (optional) It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header "Authorization: Bearer TOKEN" @@ -67,7 +67,7 @@ matrix_user_verification_service_uvs_auth_token: "TOKEN" In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token. -### (Optional) Disable Auth +### Disable Auth (optional) Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file: @@ -75,7 +75,7 @@ Authorization is enabled by default. To disable it, add the following configurat matrix_user_verification_service_uvs_require_auth: false ``` -### (Optional) Federation +### Federation (optional) In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file: diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index ad9a231dc..9c8e9bef8 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -34,7 +34,7 @@ As [per the Client-Server specification](https://matrix.org/docs/spec/client_ser 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. -### (Optional) Support Service Discovery +### Support Service Discovery (optional) [MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc. From 516a0035c878207b713bb42c9343088587479d89 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 14:38:34 +0900 Subject: [PATCH 161/952] Update docs/configuring-playbook-matrix-media-repo.md: replace an external anchor link with an internal one Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 755c27281..4a9c31372 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -88,7 +88,7 @@ matrix_media_repo_datastore_s3_opts_bucket_name: "your-media-bucket" ``` -Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml) +Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml) ## Signing Keys From a1efb78bcbc3a9205a59de3364f47192b6232f0f Mon Sep 17 00:00:00 2001 From: pviffx Date: Mon, 23 Dec 2024 20:04:38 +0100 Subject: [PATCH 162/952] Make `logout_redirect_url` configuration setting for Element Web configurable (#3903) * Add logout_redirect_url var and option templating for matrix element client * Simplify logout_redirect_url templating and make it safer Using `to_json` to make it safer. Judging by the code here https://github.com/element-hq/element-web/blob/0b24d33c64e5a161621f68fa8da65aaa8d1c847d/src/Lifecycle.ts#L1026-L1032 it doesn't seem like it leaving `logout_redirect_url` empty will hurt, so this patch removes the `if` block. * Add comment for the `matrix_client_element_logout_redirect_url` variable --------- Co-authored-by: Slavi Pantaleev --- roles/custom/matrix-client-element/defaults/main.yml | 4 ++++ roles/custom/matrix-client-element/templates/config.json.j2 | 1 + 2 files changed, 5 insertions(+) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 8f9c66a67..2216ab3f5 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -318,3 +318,7 @@ matrix_client_element_location_sharing_map_style_content_sources_localsource_til # matrix_client_element_location_sharing_map_style_content_sources_localsource_attribution: "© OpenStreetMap contributors" # Leave blank, if map does not require attribution. matrix_client_element_location_sharing_map_style_content_sources_localsource_attribution: "" + +# Optional URL to redirect the user to after they have logged out. +# See https://github.com/element-hq/element-web/blob/develop/docs/config.md#sso-setup +matrix_client_element_logout_redirect_url: '' diff --git a/roles/custom/matrix-client-element/templates/config.json.j2 b/roles/custom/matrix-client-element/templates/config.json.j2 index e45e68065..9d354a3c2 100644 --- a/roles/custom/matrix-client-element/templates/config.json.j2 +++ b/roles/custom/matrix-client-element/templates/config.json.j2 @@ -40,6 +40,7 @@ {% if matrix_client_element_location_sharing_enabled %} "map_style_url": {{ matrix_client_element_map_style_url | to_json }}, {% endif %} + "logout_redirect_url": {{ matrix_client_element_logout_redirect_url | to_json }}, "branding": { "auth_footer_links": {{ matrix_client_element_branding_auth_footer_links | to_json }}, "auth_header_logo_url": {{ matrix_client_element_branding_auth_header_logo_url | to_json }}, From 311607970d9e892909382e1be06978e570506979 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 24 Dec 2024 19:46:57 +0000 Subject: [PATCH 163/952] Update dependency charset-normalizer to v3.4.1 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index d3f036feb..2120fe628 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -1,7 +1,7 @@ alabaster==1.0.0 babel==2.16.0 certifi==2024.12.14 -charset-normalizer==3.4.0 +charset-normalizer==3.4.1 click==8.1.8 docutils==0.21.2 idna==3.10 From 75026d8c3d1b6bff04f0bc4c6f7c186d491b6854 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 25 Dec 2024 16:42:19 +0200 Subject: [PATCH 164/952] Update a few incorrect comments --- .../templates/labels.j2 | 4 ++-- roles/custom/matrix-synapse/templates/synapse/labels.j2 | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 index 8b8bd7cdb..5120b10e8 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 @@ -75,7 +75,7 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-internal-client-api. {% if matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_enabled %} ############################################################ # # -# Public Synapse Admin API (/_synapse/client) # +# Public Synapse Client API (/_synapse/client) # # # ############################################################ @@ -105,7 +105,7 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synaps ############################################################ # # -# /Public Synapse Admin API (/_synapse/client) # +# /Public Synapse Client API (/_synapse/client) # # # ############################################################ {% endif %} diff --git a/roles/custom/matrix-synapse/templates/synapse/labels.j2 b/roles/custom/matrix-synapse/templates/synapse/labels.j2 index 940e5b457..dd4d776c1 100644 --- a/roles/custom/matrix-synapse/templates/synapse/labels.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/labels.j2 @@ -130,7 +130,7 @@ traefik.http.routers.matrix-synapse-internal-client-api.entrypoints={{ matrix_sy {% if matrix_synapse_container_labels_public_client_synapse_client_api_enabled %} ############################################################ # # -# Public Synapse Admin API (/_synapse/client) # +# Public Synapse Client API (/_synapse/client) # # # ############################################################ @@ -160,7 +160,7 @@ traefik.http.routers.matrix-synapse-public-client-synapse-client-api.tls.certRes ############################################################ # # -# /Public Synapse Admin API (/_synapse/client) # +# /Public Synapse Client API (/_synapse/client) # # # ############################################################ {% endif %} From c0559870b50ad9e3848533c10066f985ff4b3ae0 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 25 Dec 2024 16:46:49 +0200 Subject: [PATCH 165/952] Make matrix-registration-bot not try to talk to the homeserver via matrix-traefik:8008 (matrix-internal-client-api) Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3898#issuecomment-2561470366 --- group_vars/matrix_servers | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 26511a65b..85e8a8717 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -2734,10 +2734,12 @@ matrix_bot_matrix_registration_bot_container_network: "{{ matrix_addons_containe matrix_bot_matrix_registration_bot_container_additional_networks_auto: |- {{ - ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) + ([matrix_homeserver_container_network] if matrix_bot_matrix_registration_bot_container_network != matrix_homeserver_container_network else []) }} -matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_addons_homeserver_client_api_url }}" +# Using `matrix_addons_homeserver_client_api_url` would not work here, +# because `matrix-traefik:8008` (matrix-internal-client-api) does not expose any `/_synapse` paths. +matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_container_url }}" ###################################################################### # From bbb58c40b66ac14a4630963662401031b9147a54 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A1szl=C3=B3=20V=C3=A1rady?= Date: Fri, 27 Dec 2024 17:21:31 +0100 Subject: [PATCH 166/952] Fix docker networking when no reverse-proxy is used For example, synapse-admin connects to additional networks here: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c0559870b50ad9e3848533c10066f985ff4b3ae0/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2#L39-L41 This defaults to 'traefik' through matrix_playbook_reverse_proxy_container_network, which is not correct in case matrix_playbook_reverse_proxy_type is set to none. --- group_vars/matrix_servers | 2 +- roles/custom/matrix-base/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 85e8a8717..a46140347 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -32,7 +32,7 @@ matrix_playbook_docker_installation_daemon_options_custom: {} # yet still use Traefik installed in another way. matrix_playbook_traefik_labels_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" -matrix_playbook_reverse_proxy_container_network: "{{ traefik_container_network if traefik_enabled else 'traefik' }}" +matrix_playbook_reverse_proxy_container_network: "{{ traefik_container_network if traefik_enabled else 'traefik' if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] else '' }}" matrix_playbook_reverse_proxy_hostname: "{{ traefik_identifier if traefik_enabled else 'traefik' }}" matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled: "{{ traefik_config_http_middlewares_compression_enabled if (traefik_enabled and traefik_config_http_middlewares_compression_enabled) else false }}" diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index 076cb8006..a0dd2f04d 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -234,7 +234,7 @@ matrix_metrics_exposure_http_basic_auth_users: '' matrix_playbook_reverse_proxy_type: '' # Specifies the network that the reverse-proxy is operating at -matrix_playbook_reverse_proxy_container_network: 'traefik' +matrix_playbook_reverse_proxy_container_network: "{{ 'traefik' if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] else '' }}" # Specifies the hostname that the reverse-proxy is available at matrix_playbook_reverse_proxy_hostname: 'matrix-traefik' From 59b8fbb13d6afe0c7a9a6fba66aa063c7a0c3178 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 28 Dec 2024 10:24:34 +0200 Subject: [PATCH 167/952] Add customizations support to maubot --- docs/configuring-playbook-bot-maubot.md | 19 ++++++ .../matrix-bot-maubot/defaults/main.yml | 42 +++++++++++- .../matrix-bot-maubot/tasks/setup_install.yml | 64 +++++++++++++------ .../templates/customizations/Dockerfile.j2 | 4 ++ .../systemd/matrix-bot-maubot.service.j2 | 2 +- 5 files changed, 108 insertions(+), 23 deletions(-) create mode 100644 roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2 diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index cab21137e..a782920af 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -47,6 +47,25 @@ See [Configuring DNS](configuring-dns.md) for details about DNS changes. If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +## Customizing the maubot container image + +Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed. + +You can customize the default maubot container image and install your own dependencies. + +Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_bot_maubot_container_image_customizations_enabled: true + +# Adjust the Dockerfile and install ffmpeg. +# +matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: | + RUN apk add --no-cache ffmpeg +``` + +Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax. + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/roles/custom/matrix-bot-maubot/defaults/main.yml b/roles/custom/matrix-bot-maubot/defaults/main.yml index cf91011b4..48087caa8 100644 --- a/roles/custom/matrix-bot-maubot/defaults/main.yml +++ b/roles/custom/matrix-bot-maubot/defaults/main.yml @@ -17,7 +17,6 @@ matrix_bot_maubot_path_prefix: /_matrix/maubot matrix_bot_maubot_container_image_self_build: false matrix_bot_maubot_docker_repo: "https://mau.dev/maubot/maubot.git" -matrix_bot_maubot_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/docker-src" matrix_bot_maubot_docker_repo_version: "{{ 'master' if matrix_bot_maubot_version == 'latest' else matrix_bot_maubot_version }}" # renovate: datasource=docker depName=dock.mau.dev/maubot/maubot @@ -26,9 +25,26 @@ matrix_bot_maubot_docker_image: "{{ matrix_bot_maubot_docker_image_name_prefix } matrix_bot_maubot_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_maubot_container_image_self_build else 'dock.mau.dev/' }}" matrix_bot_maubot_docker_image_force_pull: "{{ matrix_bot_maubot_docker_image.endswith(':latest') }}" +# matrix_bot_maubot_docker_image_customized is the name of the locally built maubot image +# which adds various customizations on top of the original (upstream) maubot image. +# This image will be based on the upstream `matrix_bot_maubot_docker_image` image, only if `matrix_bot_maubot_container_image_customizations_enabled: true`. +matrix_bot_maubot_docker_image_customized: "localhost/maubot/maubot:{{ matrix_bot_maubot_version }}-customized" + +# Controls whether the customized image (`matrix_bot_maubot_docker_image_customized`) is to be force-built without layer caching enabled. +matrix_bot_maubot_docker_image_customized_build_nocache: false + +# Controls whether the customized image (`matrix_bot_maubot_docker_image_customized`) is to be built, even if it already exists. +# Related to: matrix_bot_maubot_docker_image_customized_build_nocache +matrix_bot_maubot_docker_image_customized_force_source: "{{ matrix_bot_maubot_docker_image_customized_build_nocache }}" + +# matrix_bot_maubot_docker_image_final holds the name of the maubot image to run depending on whether or not customizations are enabled. +matrix_bot_maubot_docker_image_final: "{{ matrix_bot_maubot_docker_image_customized if matrix_bot_maubot_container_image_customizations_enabled else matrix_bot_maubot_docker_image }} " + matrix_bot_maubot_base_path: "{{ matrix_base_data_path }}/maubot" matrix_bot_maubot_data_path: "{{ matrix_bot_maubot_base_path }}/data" matrix_bot_maubot_config_path: "{{ matrix_bot_maubot_base_path }}/config" +matrix_bot_maubot_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/docker-src" +matrix_bot_maubot_customized_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/customized-docker-src" matrix_bot_maubot_bot_server_public_url: "{{ matrix_bot_maubot_scheme }}://{{ matrix_bot_maubot_hostname }}" matrix_bot_maubot_bot_server_base_path: "{{ matrix_bot_maubot_path_prefix }}/v1" @@ -87,6 +103,30 @@ matrix_bot_maubot_container_additional_networks: "{{ matrix_bot_maubot_container matrix_bot_maubot_container_additional_networks_auto: [] matrix_bot_maubot_container_additional_networks_custom: [] + +# matrix_bot_maubot_container_image_customizations_enabled controls whether a customized maubot image will be built. +# +# We toggle this variable to `true` when certain features which require a custom build are enabled. +# Feel free to toggle this to `true` yourself and specify build steps in `matrix_bot_maubot_container_image_customizations_dockerfile_body_custom`. +# +# See: +# - `roles/custom/matrix-bot-maubot/templates/maubot/customizations/Dockerfile.j2` +# - `matrix_bot_maubot_container_image_customizations_dockerfile_body_custom` +# - `matrix_bot_maubot_docker_image_customized` +# - `matrix_bot_maubot_docker_image_final` +matrix_bot_maubot_container_image_customizations_enabled: false + +# matrix_bot_maubot_container_image_customizations_dockerfile_body contains your custom Dockerfile steps +# for building your customized maubot image based on the original (upstream) image (`matrix_bot_maubot_docker_image`). +# A `FROM …` clause is included automatically so you don't have to. +# +# Example: +# matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: | +# RUN echo 'This is a custom step for building the customized container image for maubot.' +# RUN echo 'You can override matrix_bot_maubot_container_image_customizations_dockerfile_body_custom to add your own steps.' +# RUN echo 'You do NOT need to include a FROM clause yourself.' +matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: '' + # matrix_bot_maubot_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. # See `../templates/labels.j2` for details. # diff --git a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml index 318879f9b..db2b44778 100644 --- a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml @@ -15,6 +15,7 @@ - {path: "{{ matrix_bot_maubot_data_path }}/dbs", when: true} - {path: "{{ matrix_bot_maubot_data_path }}/trash", when: true} - {path: "{{ matrix_bot_maubot_docker_src_files_path }}", when: "{{ matrix_bot_maubot_container_image_self_build }}"} + - {path: "{{ matrix_bot_maubot_customized_docker_src_files_path }}", when: "{{ matrix_bot_maubot_container_image_customizations_enabled }}"} when: "item.when|bool" - name: Ensure maubot configuration file created @@ -37,28 +38,49 @@ delay: "{{ devture_playbook_help_container_retries_delay }}" until: result is not failed -- name: Ensure maubot repository is present on self-build - ansible.builtin.git: - repo: "{{ matrix_bot_maubot_docker_repo }}" - version: "{{ matrix_bot_maubot_docker_repo_version }}" - dest: "{{ matrix_bot_maubot_docker_src_files_path }}" - force: "yes" - become: true - become_user: "{{ matrix_user_username }}" - register: matrix_bot_maubot_git_pull_results - when: "matrix_bot_maubot_container_image_self_build|bool" +- when: matrix_bot_maubot_container_image_self_build | bool + block: + - name: Ensure maubot repository is present on self-build + ansible.builtin.git: + repo: "{{ matrix_bot_maubot_docker_repo }}" + version: "{{ matrix_bot_maubot_docker_repo_version }}" + dest: "{{ matrix_bot_maubot_docker_src_files_path }}" + force: "yes" + become: true + become_user: "{{ matrix_user_username }}" + register: matrix_bot_maubot_git_pull_results -- name: Ensure maubot image is built - community.docker.docker_image: - name: "{{ matrix_bot_maubot_docker_image }}" - source: build - force_source: "{{ matrix_bot_maubot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_maubot_git_pull_results.changed }}" - build: - dockerfile: Dockerfile - path: "{{ matrix_bot_maubot_docker_src_files_path }}" - pull: true - when: "matrix_bot_maubot_container_image_self_build|bool" + - name: Ensure maubot image is built + community.docker.docker_image: + name: "{{ matrix_bot_maubot_docker_image }}" + source: build + force_source: "{{ matrix_bot_maubot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_maubot_git_pull_results.changed }}" + build: + dockerfile: Dockerfile + path: "{{ matrix_bot_maubot_docker_src_files_path }}" + pull: true + +- when: "matrix_bot_maubot_container_image_customizations_enabled | bool" + block: + - name: Ensure customizations Dockerfile is created + ansible.builtin.template: + src: "{{ role_path }}/templates/customizations/Dockerfile.j2" + dest: "{{ matrix_bot_maubot_customized_docker_src_files_path }}/Dockerfile" + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + mode: 0640 + register: matrix_bot_maubot_container_image_customizations_dockerfile_result + + - name: Ensure customized Docker image for maubot is built + community.docker.docker_image: + name: "{{ matrix_bot_maubot_docker_image_customized }}" + source: build + force_source: "{{ matrix_bot_maubot_container_image_customizations_dockerfile_result.changed or matrix_bot_maubot_docker_image_customized_force_source }}" + build: + dockerfile: Dockerfile + path: "{{ matrix_bot_maubot_customized_docker_src_files_path }}" + nocache: "{{ matrix_bot_maubot_docker_image_customized_build_nocache }}" - name: Ensure maubot support files installed ansible.builtin.template: diff --git a/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2 b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2 new file mode 100644 index 000000000..0f2f4e508 --- /dev/null +++ b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2 @@ -0,0 +1,4 @@ +#jinja2: lstrip_blocks: "True" +FROM {{ matrix_bot_maubot_docker_image }} + +{{ matrix_bot_maubot_container_image_customizations_dockerfile_body_custom }} diff --git a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 index c54dbd084..25ba29a46 100644 --- a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 +++ b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ {% if matrix_bot_maubot_container_management_interface_http_bind_port %} -p {{ matrix_bot_maubot_container_management_interface_http_bind_port }}:{{ matrix_bot_maubot_server_port }} \ {% endif %} - {{ matrix_bot_maubot_docker_image }} \ + {{ matrix_bot_maubot_docker_image_final }} \ python3 -m maubot -c /config/config.yaml --no-update {% for network in matrix_bot_maubot_container_additional_networks %} From 75337384c00c664ad8a6d3982d9fb2f328b9e575 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 28 Dec 2024 10:25:48 +0200 Subject: [PATCH 168/952] Rebuild i18n files --- i18n/locales/bg/LC_MESSAGES/CHANGELOG.po | 4 +- ...figuring-playbook-alertmanager-receiver.po | 58 +++-- .../docs/configuring-playbook-backup-borg.po | 4 +- .../docs/configuring-playbook-bot-baibot.po | 8 +- .../configuring-playbook-bot-buscarron.po | 34 ++- .../docs/configuring-playbook-bot-chatgpt.po | 50 ++-- .../docs/configuring-playbook-bot-draupnir.po | 174 +++++++------ .../docs/configuring-playbook-bot-go-neb.po | 66 ++--- .../docs/configuring-playbook-bot-honoroit.po | 12 +- ...ng-playbook-bot-matrix-registration-bot.po | 6 +- ...guring-playbook-bot-matrix-reminder-bot.po | 4 +- .../docs/configuring-playbook-bot-maubot.po | 101 +++++--- .../docs/configuring-playbook-bot-mjolnir.po | 98 +++---- ...ring-playbook-bridge-appservice-discord.po | 4 +- ...ng-playbook-bridge-appservice-kakaotalk.po | 4 +- ...iguring-playbook-bridge-go-skype-bridge.po | 4 +- .../configuring-playbook-bridge-hookshot.po | 4 +- ...iguring-playbook-bridge-mautrix-discord.po | 6 +- ...guring-playbook-bridge-mautrix-facebook.po | 4 +- ...uring-playbook-bridge-mautrix-gmessages.po | 4 +- ...ring-playbook-bridge-mautrix-googlechat.po | 4 +- ...guring-playbook-bridge-mautrix-hangouts.po | 4 +- ...-playbook-bridge-mautrix-meta-instagram.po | 4 +- ...-playbook-bridge-mautrix-meta-messenger.po | 4 +- ...figuring-playbook-bridge-mautrix-signal.po | 4 +- ...nfiguring-playbook-bridge-mautrix-slack.po | 6 +- ...guring-playbook-bridge-mautrix-telegram.po | 4 +- ...iguring-playbook-bridge-mautrix-twitter.po | 4 +- ...guring-playbook-bridge-mautrix-whatsapp.po | 4 +- ...uring-playbook-bridge-mx-puppet-discord.po | 4 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 4 +- ...ing-playbook-bridge-mx-puppet-instagram.po | 4 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 4 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 4 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 4 +- .../configuring-playbook-bridge-postmoogle.po | 4 +- .../configuring-playbook-cactus-comments.po | 4 +- .../docs/configuring-playbook-dimension.po | 243 ++++++++++-------- .../docs/configuring-playbook-email2matrix.po | 120 +++++---- .../docs/configuring-playbook-jitsi.po | 14 +- .../configuring-playbook-matrix-media-repo.po | 4 +- ...ring-playbook-user-verification-service.po | 14 +- .../docs/configuring-well-known.po | 4 +- .../docs/howto-server-delegation.po | 4 +- .../LC_MESSAGES/docs/maintenance-synapse.po | 72 +++--- .../docs/obtaining-access-tokens.po | 4 +- i18n/locales/jp/LC_MESSAGES/CHANGELOG.po | 4 +- ...figuring-playbook-alertmanager-receiver.po | 58 +++-- .../docs/configuring-playbook-backup-borg.po | 4 +- .../docs/configuring-playbook-bot-baibot.po | 8 +- .../configuring-playbook-bot-buscarron.po | 34 ++- .../docs/configuring-playbook-bot-chatgpt.po | 50 ++-- .../docs/configuring-playbook-bot-draupnir.po | 174 +++++++------ .../docs/configuring-playbook-bot-go-neb.po | 66 ++--- .../docs/configuring-playbook-bot-honoroit.po | 12 +- ...ng-playbook-bot-matrix-registration-bot.po | 6 +- ...guring-playbook-bot-matrix-reminder-bot.po | 4 +- .../docs/configuring-playbook-bot-maubot.po | 101 +++++--- .../docs/configuring-playbook-bot-mjolnir.po | 98 +++---- ...ring-playbook-bridge-appservice-discord.po | 4 +- ...ng-playbook-bridge-appservice-kakaotalk.po | 4 +- ...iguring-playbook-bridge-go-skype-bridge.po | 4 +- .../configuring-playbook-bridge-hookshot.po | 4 +- ...iguring-playbook-bridge-mautrix-discord.po | 6 +- ...guring-playbook-bridge-mautrix-facebook.po | 4 +- ...uring-playbook-bridge-mautrix-gmessages.po | 4 +- ...ring-playbook-bridge-mautrix-googlechat.po | 4 +- ...guring-playbook-bridge-mautrix-hangouts.po | 4 +- ...-playbook-bridge-mautrix-meta-instagram.po | 4 +- ...-playbook-bridge-mautrix-meta-messenger.po | 4 +- ...figuring-playbook-bridge-mautrix-signal.po | 4 +- ...nfiguring-playbook-bridge-mautrix-slack.po | 6 +- ...guring-playbook-bridge-mautrix-telegram.po | 4 +- ...iguring-playbook-bridge-mautrix-twitter.po | 4 +- ...guring-playbook-bridge-mautrix-whatsapp.po | 4 +- ...uring-playbook-bridge-mx-puppet-discord.po | 4 +- ...uring-playbook-bridge-mx-puppet-groupme.po | 4 +- ...ing-playbook-bridge-mx-puppet-instagram.po | 4 +- ...iguring-playbook-bridge-mx-puppet-slack.po | 4 +- ...iguring-playbook-bridge-mx-puppet-steam.po | 4 +- ...uring-playbook-bridge-mx-puppet-twitter.po | 4 +- .../configuring-playbook-bridge-postmoogle.po | 4 +- .../configuring-playbook-cactus-comments.po | 4 +- .../docs/configuring-playbook-dimension.po | 243 ++++++++++-------- .../docs/configuring-playbook-email2matrix.po | 120 +++++---- .../docs/configuring-playbook-jitsi.po | 14 +- .../configuring-playbook-matrix-media-repo.po | 4 +- ...ring-playbook-user-verification-service.po | 14 +- .../docs/configuring-well-known.po | 4 +- .../docs/howto-server-delegation.po | 4 +- .../LC_MESSAGES/docs/maintenance-synapse.po | 72 +++--- .../docs/obtaining-access-tokens.po | 4 +- ...iguring-playbook-alertmanager-receiver.pot | 52 ++-- .../docs/configuring-playbook-bot-chatgpt.pot | 30 ++- .../configuring-playbook-bot-draupnir.pot | 158 ++++++------ .../docs/configuring-playbook-bot-go-neb.pot | 46 ++-- .../docs/configuring-playbook-bot-maubot.pot | 99 ++++--- .../docs/configuring-playbook-bot-mjolnir.pot | 82 +++--- ...g-playbook-bridge-appservice-kakaotalk.pot | 4 +- ...guring-playbook-bridge-mautrix-discord.pot | 4 +- ...uring-playbook-bridge-mautrix-facebook.pot | 4 +- ...ring-playbook-bridge-mautrix-gmessages.pot | 4 +- ...ing-playbook-bridge-mautrix-googlechat.pot | 4 +- ...uring-playbook-bridge-mautrix-hangouts.pot | 4 +- ...playbook-bridge-mautrix-meta-instagram.pot | 4 +- ...playbook-bridge-mautrix-meta-messenger.pot | 4 +- ...iguring-playbook-bridge-mautrix-signal.pot | 4 +- ...figuring-playbook-bridge-mautrix-slack.pot | 4 +- ...uring-playbook-bridge-mautrix-telegram.pot | 4 +- ...guring-playbook-bridge-mautrix-twitter.pot | 4 +- ...uring-playbook-bridge-mautrix-whatsapp.pot | 4 +- .../docs/configuring-playbook-dimension.pot | 243 ++++++++++-------- .../configuring-playbook-email2matrix.pot | 120 +++++---- .../docs/configuring-playbook-jitsi.pot | 14 +- ...configuring-playbook-matrix-media-repo.pot | 4 +- ...ing-playbook-user-verification-service.pot | 14 +- .../docs/configuring-well-known.pot | 4 +- .../docs/maintenance-synapse.pot | 72 +++--- .../docs/obtaining-access-tokens.pot | 4 +- 119 files changed, 1842 insertions(+), 1548 deletions(-) diff --git a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po index d9f668a66..a6080952c 100644 --- a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po +++ b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -4007,7 +4007,7 @@ msgid "We believe the steps below are safe and you won't encounter any data loss msgstr "" #: ../../../CHANGELOG.md:2195 -msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" msgstr "" #: ../../../CHANGELOG.md:2197 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 7c6a635af..2c03e93ea 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: 2024-12-20 09:53+0200\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" @@ -54,7 +54,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 @@ -62,7 +62,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 @@ -70,97 +70,101 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 -msgid "Join to rooms as the bot manually" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 -msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." +msgid "Join to rooms as the bot manually" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:33 -msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." +msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:35 -msgid "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." +msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:37 -msgid "Adjusting the playbook configuration" +msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 -msgid "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](#get-an-access-token)." +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:70 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80 msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84 msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:98 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po index 8d90bc9eb..9940bcadd 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: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -98,7 +98,7 @@ msgid "REPO - BorgBackup repository name, it will be initialized on backup start msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:63 -msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" +msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:64 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po index d135c0566..4c6509717 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -82,7 +82,7 @@ msgid "Base configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:33 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:71 @@ -389,7 +389,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:386 -msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:388 @@ -405,7 +405,7 @@ msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring- msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:394 -msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." +msgid "Send `!bai help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:396 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po index 1965840a5..55af029e1 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -38,7 +38,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:9 -msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:32 @@ -106,29 +106,37 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:78 -msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:86 -msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" +#: ../../../docs/configuring-playbook-bot-buscarron.md:80 +msgid "After the bot joins the room, anyone can call the web form via HTTP POST method." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:88 -msgid "if you hit the homepage (HTTP `GET` request to `/`)" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-buscarron.md:89 -msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" +#: ../../../docs/configuring-playbook-bot-buscarron.md:82 +msgid "Here is an example for the `contact` form:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:90 -msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:92 -msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgid "you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:93 +msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:96 +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:98 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index 06ee33bc8..c54da193f 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: 2024-12-16 12:05+0900\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" @@ -38,47 +38,55 @@ msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Ma msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:9 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgid "Obtain an OpenAI API key" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 -msgid "You **need to register the bot user manually** before setting up the bot." +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 "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:19 +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:21 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 -msgid "Get an access token and create encryption keys" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 -msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." -msgstr "" - #: ../../../docs/configuring-playbook-bot-chatgpt.md:27 -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)." +msgid "Obtain an access token and create encryption keys" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:29 -msgid "Adjusting the playbook configuration" +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 "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:52 -msgid "You will need to get tokens for ChatGPT." +#: ../../../docs/configuring-playbook-bot-chatgpt.md:33 +msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:37 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:54 @@ -110,9 +118,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:73 -msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:77 msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index c0d39766e..bab221487 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -54,7 +54,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 @@ -66,7 +66,7 @@ msgid "If you would like Draupnir to be able to deactivate users, move aliases, msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 @@ -74,309 +74,313 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:59 +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:61 +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:63 +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:65 +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:67 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:76 -msgid "End-to-End Encryption support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:69 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:78 -msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:80 -msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:82 -msgid "Configuration with E2EE support" +msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:84 -msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:86 +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:100 +#: ../../../docs/configuring-playbook-bot-draupnir.md:102 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:114 +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:116 -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](#get-an-access-token)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:122 -msgid "Abuse Reports" +#: ../../../docs/configuring-playbook-bot-draupnir.md:118 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:124 -msgid "Draupnir supports two methods to receive reports in the management room." +msgid "Abuse Reports" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:126 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:128 msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +#: ../../../docs/configuring-playbook-bot-draupnir.md:140 msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:154 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:156 +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 msgid "That is all you need to do due to that Draupnir can complete migration on its own." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:158 +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:160 +#: ../../../docs/configuring-playbook-bot-draupnir.md:162 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:175 +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:177 +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:203 +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:205 +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:207 +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:209 +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:211 +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:213 +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:221 +#: ../../../docs/configuring-playbook-bot-draupnir.md:223 msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:222 +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:224 +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:226 +#: ../../../docs/configuring-playbook-bot-draupnir.md:228 msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:227 +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:229 +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:231 +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:233 +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:235 +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:237 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:239 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:241 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:243 +#: ../../../docs/configuring-playbook-bot-draupnir.md:245 msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po index f9abc1654..72c8f2272 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,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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-Team: LANGUAGE \n" @@ -38,19 +38,19 @@ msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/bl msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 -msgid "Registering the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:19 @@ -58,89 +58,97 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:25 -msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:27 -msgid "Adjusting the playbook configuration" +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +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:193 -msgid "Adjusting the Go-NEB URL" +#: ../../../docs/configuring-playbook-bot-go-neb.md:31 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:195 -msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +#: ../../../docs/configuring-playbook-bot-go-neb.md:33 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:197 -msgid "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." +msgid "Adjusting the Go-NEB URL" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:199 +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:201 +msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:203 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:218 msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:222 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +#: ../../../docs/configuring-playbook-bot-go-neb.md:224 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:227 +#: ../../../docs/configuring-playbook-bot-go-neb.md:231 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:233 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:235 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:233 +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:235 +#: ../../../docs/configuring-playbook-bot-go-neb.md:239 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:239 +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:241 -msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" +#: ../../../docs/configuring-playbook-bot-go-neb.md:245 +msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +#: ../../../docs/configuring-playbook-bot-go-neb.md:247 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index 827fc18d3..06874ae70 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -42,7 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:11 -msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:26 @@ -110,13 +110,17 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:69 -msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." +msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "Send `!ho help` to the bot in the room to see the available commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:75 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index 073beaf8b..3471823b4 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -38,7 +38,7 @@ msgid "See the project's [documentation](https://github.com/moan0s/matrix-regist msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 -msgid "Configuration" +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 @@ -86,7 +86,7 @@ msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.c msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 -msgid "In this room send `help` and the bot will reply with all options." +msgid "Send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index fa00c1476..84f39a049 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -42,7 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po index cf4454110..f4130be13 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -42,7 +42,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:11 -msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:26 @@ -62,6 +62,7 @@ msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_ msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:34 +#: ../../../docs/configuring-playbook-bot-maubot.md:56 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" @@ -82,65 +83,85 @@ msgid "If you've decided to use the default hostname, you won't need to do any e msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:50 -msgid "Installing" +msgid "Customizing the maubot container image" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.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:" +msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-maubot.md:59 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:61 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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." +#: ../../../docs/configuring-playbook-bot-maubot.md:54 +msgid "You can customize the default maubot container image and install your own dependencies." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:67 -msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:69 -msgid "Usage" +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:71 -msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:73 -msgid "You should start in the following order" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:74 -msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:75 -msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:76 -msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 -msgid "Obtaining an access token" +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 -msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:82 -msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:84 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:86 +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:88 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:90 +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:92 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:93 +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:94 +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:95 +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:97 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:99 +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:101 +msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:103 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index 770378086..148e91976 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -46,7 +46,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:15 @@ -58,7 +58,7 @@ msgid "If you would like Mjolnir to be able to deactivate users, move aliases, s msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:23 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 @@ -66,157 +66,161 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 -msgid "End-to-End Encryption support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:65 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:74 -msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:76 -msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:78 -msgid "Configuration with E2EE support" +msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:80 -msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:82 +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:98 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -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](#get-an-access-token)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 -msgid "Adding Mjolnir synapse antispam module (optional)" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +msgid "Adding Mjolnir synapse antispam module (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:122 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:136 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:152 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:171 msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po index 19e765ead..c57241d4d 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: 2024-12-16 12:05+0900\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" @@ -115,7 +115,7 @@ msgid "If the bot is not already in the Discord server, follow the provided invi msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 -msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." +msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 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 f45dd6fa7..c9efff085 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: 2024-12-20 09:53+0200\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" @@ -150,7 +150,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 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 6565f7474..76a31dbd3 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: 2024-12-20 09:53+0200\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" @@ -74,5 +74,5 @@ msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 -msgid "Send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." 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 969a85e2a..4c3b51aae 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: 2024-12-20 09:53+0200\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" @@ -114,7 +114,7 @@ msgid "Make sure the bot is able to send state events (usually the Moderator pow msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:64 -msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:66 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 2c8767d29..bd0311833 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: 2024-12-16 12:05+0900\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" @@ -174,7 +174,7 @@ msgid "After confirming (in the Discord app) that you'd like to allow this login msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 @@ -234,7 +234,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 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 9325f317c..a16acf802 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: 2024-12-16 12:05+0900\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" @@ -150,7 +150,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 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 f181bca9b..40bc5001c 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: 2024-12-16 12:05+0900\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" @@ -118,7 +118,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 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 2f4d93ae1..3fd090658 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: 2024-12-16 12:05+0900\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" @@ -138,7 +138,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 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 fa5c12175..0d552d93a 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: 2024-12-16 12:05+0900\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" @@ -138,7 +138,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 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 b8e6a3229..e1c347b88 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: 2024-12-16 12:05+0900\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" @@ -198,7 +198,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 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 deedc6840..905ac480e 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: 2024-12-16 12:05+0900\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" @@ -234,7 +234,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 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 3767bf9d3..990eefa26 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: 2024-12-16 12:05+0900\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" @@ -186,7 +186,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 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 95912f8f4..3de53dfe5 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: 2024-12-16 12:05+0900\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" @@ -146,7 +146,7 @@ msgid "The bot should respond with \"Successfully logged into for team < msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 @@ -186,7 +186,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 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 fcdaf40dc..5dbfc7b62 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: 2024-12-16 12:05+0900\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" @@ -142,7 +142,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 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 e16a0a587..403b09145 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: 2024-12-20 09:53+0200\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" @@ -134,7 +134,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 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 f38bbc6b1..15cd1e448 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: 2024-12-16 12:05+0900\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" @@ -138,7 +138,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 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 63c31ff55..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: 2024-12-20 09:53+0200\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" @@ -98,5 +98,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 -msgid "Also send `help` to the bot to see the commands available." +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 61d002626..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: 2024-12-20 09:53+0200\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" @@ -90,5 +90,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 -msgid "Also send `help` to the bot to see the commands available." +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 7174fc472..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: 2024-12-16 12:05+0900\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" @@ -102,5 +102,5 @@ msgid "If you are linking only one Instagram account, your `$puppetId` is probab msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48 -msgid "The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented." +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-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po index 4ca40c767..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,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -94,5 +94,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 -msgid "Also send `help` to the bot to see the commands available." +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 fbad3d73e..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: 2024-12-20 09:53+0200\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" @@ -86,5 +86,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 -msgid "Also send `help` to the bot to see the commands available." +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 e881607c3..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: 2024-12-20 09:53+0200\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" @@ -98,5 +98,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index 17eb742c0..dceac0da9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -118,7 +118,7 @@ msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 -msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!pm help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 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 79c9dddee..b28acaeed 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: 2024-12-16 12:05+0900\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" @@ -126,7 +126,7 @@ msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:85 -msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." +msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:87 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 a2dcc6505..6bc7248aa 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: 2024-12-16 12:05+0900\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" @@ -26,137 +26,158 @@ msgid "Setting up Dimension integration manager (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:3 -msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:5 -msgid "**Note**: 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:7 -msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:9 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:11 -msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:17 -msgid "Define admin users" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:19 -msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:27 -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:29 -msgid "Access token" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:31 -msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:33 -msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:35 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:37 -msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:43 -msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:45 -msgid "Adjusting the Dimension URL" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:47 -msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:49 -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:51 -msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:62 -msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:64 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:66 -msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:68 -msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:70 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +#: ../../../docs/configuring-playbook-dimension.md:91 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:81 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../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:83 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:85 -msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +#: ../../../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:87 -msgid "Jitsi domain" +#: ../../../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:89 -msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:91 -msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +#: ../../../docs/configuring-playbook-dimension.md:13 +msgid "Install Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:15 +msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Register a dedicated Matrix user (optional, recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:21 +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:23 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:29 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:55 +msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:57 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:59 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:61 +msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:63 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:74 +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:76 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:78 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:80 +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:82 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:84 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:93 -msgid "Additional features" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:95 -msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:97 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:99 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:101 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:103 +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:105 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:107 +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:109 msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index 0bdcf7ed3..aa97b41e9 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: 2024-12-20 09:53+0200\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" @@ -70,113 +70,129 @@ msgid "For details about using Email2Matrix alongside [Postfix](http://www.postf msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:25 -msgid "Creating a user" +msgid "Register a dedicated Matrix user (optional, recommended)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:27 -msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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." +msgid "We recommend that you create a dedicated Matrix user for Email2Matrix." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:29 -msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:31 -msgid "Creating a shared room" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:33 -msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:35 -msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." +msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:37 -msgid "Inviting additional people to the room is okay too." +msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:39 -msgid "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." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:41 -msgid "Obtaining an access token for the sender user" +msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 -msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:45 -msgid "Adjusting the playbook configuration" +msgid "Join to rooms as the sender user manually" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:47 -msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:72 -msgid "where:" +#: ../../../docs/configuring-playbook-email2matrix.md:49 +msgid "For each new room you would like the user to deliver messages to, invite the user to the room." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:74 -msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +#: ../../../docs/configuring-playbook-email2matrix.md:51 +msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:75 -msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +#: ../../../docs/configuring-playbook-email2matrix.md:53 +msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:76 -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" +#: ../../../docs/configuring-playbook-email2matrix.md:55 +msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:77 -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)" +#: ../../../docs/configuring-playbook-email2matrix.md:57 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:78 -msgid "MatrixAccessToken - sender user's access token" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:79 -msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:80 -msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:81 -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:83 -msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +#: ../../../docs/configuring-playbook-email2matrix.md:59 +msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:85 -msgid "Installing" +msgid "where:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:88 +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:89 +msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:90 +msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:91 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:92 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:94 -msgid "**Notes**:" +msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:96 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:98 -msgid "`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." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:100 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:107 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:109 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:111 +msgid "`just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:113 msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po index 323995184..05f28ca05 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: 2024-12-16 12:05+0900\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" @@ -90,7 +90,7 @@ msgid "By default, you will need to create a CNAME record for `jitsi`. See [Conf msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:43 -msgid "(Optional) Configure Jitsi authentication and guests mode" +msgid "Configure Jitsi authentication and guests mode (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:45 @@ -166,7 +166,7 @@ msgid "For more information refer to the [docker-jitsi-meet](https://github.com/ msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:115 -msgid "(Optional) Making your Jitsi server work on a LAN" +msgid "Making your Jitsi server work on a LAN (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:117 @@ -186,7 +186,7 @@ msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars. msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:130 -msgid "(Optional) Fine tune Jitsi" +msgid "Fine tune Jitsi (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:132 @@ -210,7 +210,7 @@ msgid "You may want to **limit the maximum video resolution**, to save up resour msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:155 -msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgid "Specify a Max number of participants on a Jitsi conference (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:157 @@ -222,7 +222,7 @@ msgid "In order to set the max number of participants use the following **additi msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:165 -msgid "(Optional) Additional JVBs" +msgid "Additional JVBs (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:167 @@ -274,7 +274,7 @@ msgid "To make Traefik reverse-proxy to these additional JVBs (living on other h msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:256 -msgid "(Optional) Enable Gravatar" +msgid "Enable Gravatar (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:258 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 a3d6a1636..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: 2024-12-16 12:05+0900\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" @@ -78,7 +78,7 @@ msgid "Additional common configuration options:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:91 -msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:93 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index 0e4f60922..25c018878 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -98,7 +98,7 @@ msgid "In the default configuration, the UVS Server is only reachable via the do msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:42 -msgid "Access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:44 @@ -110,15 +110,15 @@ msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:48 -msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:50 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:56 -msgid "(Optional) Custom Auth Token" +msgid "Custom Auth Token (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:58 @@ -138,7 +138,7 @@ msgid "In case Jitsi is also managed by this playbook and 'matrix' authenticatio msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:70 -msgid "(Optional) Disable Auth" +msgid "Disable Auth (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:72 @@ -146,7 +146,7 @@ msgid "Authorization is enabled by default. To disable it, add the following con msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:78 -msgid "(Optional) Federation" +msgid "Federation (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:80 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 19ba61dcd..9711ff1b9 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"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-Team: LANGUAGE \n" @@ -90,7 +90,7 @@ msgid "However, this playbook installs your Matrix server on another domain (e.g msgstr "" #: ../../../docs/configuring-well-known.md:37 -msgid "(Optional) Support Service Discovery" +msgid "Support Service Discovery (optional)" msgstr "" #: ../../../docs/configuring-well-known.md:39 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po index 122665b7b..3572ebe44 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-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: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: bg\n" @@ -130,7 +130,7 @@ msgid "For more details on how to configure the playbook to work with SRV delega msgstr "" #: ../../../docs/howto-server-delegation.md:54 -msgid "Obtaining certificates" +msgid "Obtain certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:56 diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po index 1d92a8229..2463c4eb2 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: 2024-12-16 12:05+0900\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" @@ -62,137 +62,141 @@ msgid "To make use of this Synapse Admin API, **you'll need an admin access toke msgstr "" #: ../../../docs/maintenance-synapse.md:21 -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." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/maintenance-synapse.md:23 -msgid "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." +msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file." msgstr "" #: ../../../docs/maintenance-synapse.md:25 -msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions." msgstr "" #: ../../../docs/maintenance-synapse.md:27 -msgid "Compressing state with rust-synapse-compress-state" +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:29 -msgid "[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." +msgid "Compressing state with rust-synapse-compress-state" msgstr "" #: ../../../docs/maintenance-synapse.md:31 -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." +msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database." msgstr "" #: ../../../docs/maintenance-synapse.md:33 -msgid "`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." +msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again." msgstr "" #: ../../../docs/maintenance-synapse.md:35 +msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:37 msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" -#: ../../../docs/maintenance-synapse.md:41 +#: ../../../docs/maintenance-synapse.md:43 msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" -#: ../../../docs/maintenance-synapse.md:43 +#: ../../../docs/maintenance-synapse.md:45 msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above." msgstr "" -#: ../../../docs/maintenance-synapse.md:45 +#: ../../../docs/maintenance-synapse.md:47 msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:47 +#: ../../../docs/maintenance-synapse.md:49 msgid "Browse and manipulate the database" msgstr "" -#: ../../../docs/maintenance-synapse.md:49 +#: ../../../docs/maintenance-synapse.md:51 msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs." msgstr "" -#: ../../../docs/maintenance-synapse.md:51 +#: ../../../docs/maintenance-synapse.md:53 msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:53 +#: ../../../docs/maintenance-synapse.md:55 msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" -#: ../../../docs/maintenance-synapse.md:60 +#: ../../../docs/maintenance-synapse.md:62 msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:" msgstr "" -#: ../../../docs/maintenance-synapse.md:66 +#: ../../../docs/maintenance-synapse.md:68 msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)" msgstr "" -#: ../../../docs/maintenance-synapse.md:68 +#: ../../../docs/maintenance-synapse.md:70 msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" -#: ../../../docs/maintenance-synapse.md:70 +#: ../../../docs/maintenance-synapse.md:72 msgid "Make Synapse faster" msgstr "" -#: ../../../docs/maintenance-synapse.md:72 +#: ../../../docs/maintenance-synapse.md:74 msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:74 +#: ../../../docs/maintenance-synapse.md:76 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:76 +#: ../../../docs/maintenance-synapse.md:78 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:78 +#: ../../../docs/maintenance-synapse.md:80 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:80 +#: ../../../docs/maintenance-synapse.md:82 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:82 +#: ../../../docs/maintenance-synapse.md:84 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:84 +#: ../../../docs/maintenance-synapse.md:86 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:86 +#: ../../../docs/maintenance-synapse.md:88 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:88 +#: ../../../docs/maintenance-synapse.md:90 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:89 +#: ../../../docs/maintenance-synapse.md:91 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:92 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:94 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:96 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:104 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:106 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po index f14ecacfd..3a94222d7 100644 --- a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po +++ b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -30,7 +30,7 @@ msgid "When setting up some optional features like bots and bridges you will nee msgstr "" #: ../../../docs/obtaining-access-tokens.md:5 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/obtaining-access-tokens.md:7 diff --git a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po index f0f6914ef..b142bce39 100644 --- a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po +++ b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -4006,7 +4006,7 @@ msgid "We believe the steps below are safe and you won't encounter any data loss msgstr "" #: ../../../CHANGELOG.md:2195 -msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" +msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!" msgstr "" #: ../../../CHANGELOG.md:2197 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 f968d56f4..bd7e7f512 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: 2024-12-20 09:53+0200\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" @@ -53,7 +53,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:19 @@ -61,7 +61,7 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:25 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:27 @@ -69,97 +69,101 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 -msgid "Join to rooms as the bot manually" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 -msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." +msgid "Join to rooms as the bot manually" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:33 -msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." +msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:35 -msgid "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." +msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:37 -msgid "Adjusting the playbook configuration" +msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 -msgid "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](#get-an-access-token)." +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:61 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:63 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:65 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:67 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:69 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:70 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:77 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:79 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80 msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:81 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:83 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84 msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:85 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:87 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:94 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:96 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:98 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:100 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:102 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:104 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:123 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po index e787fcd57..ea0595781 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: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-22 17:53+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -97,7 +97,7 @@ msgid "REPO - BorgBackup repository name, it will be initialized on backup start msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:63 -msgid "PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager" +msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-backup-borg.md:64 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po index 77417d722..5e7d91371 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -81,7 +81,7 @@ msgid "Base configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:33 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:71 @@ -388,7 +388,7 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:386 -msgid "To use the bot, invite the `@baibot:example.com` bot user into a room." +msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:388 @@ -404,7 +404,7 @@ msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring- msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:394 -msgid "Send `!bai help` to the room at any time to see the bot's help menu for additional commands." +msgid "Send `!bai help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-baibot.md:396 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po index 2dd8ab917..6822a51fb 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -37,7 +37,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:9 -msgid "To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:32 @@ -105,29 +105,37 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:78 -msgid "To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:" +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:86 -msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" +#: ../../../docs/configuring-playbook-bot-buscarron.md:80 +msgid "After the bot joins the room, anyone can call the web form via HTTP POST method." msgstr "" -#: ../../../docs/configuring-playbook-bot-buscarron.md:88 -msgid "if you hit the homepage (HTTP `GET` request to `/`)" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-buscarron.md:89 -msgid "if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" +#: ../../../docs/configuring-playbook-bot-buscarron.md:82 +msgid "Here is an example for the `contact` form:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:90 -msgid "if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:92 -msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgid "you hit the homepage (HTTP `GET` request to `/`)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:93 +msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)" msgstr "" #: ../../../docs/configuring-playbook-bot-buscarron.md:94 +msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:96 +msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-buscarron.md:98 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po index 3214d2062..6b6d46434 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: 2024-12-16 12:05+0900\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" @@ -37,47 +37,55 @@ msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Ma msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:9 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:11 -msgid "The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver." +msgid "Obtain an OpenAI API key" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:13 -msgid "You **need to register the bot user manually** before setting up the bot." +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 "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:17 +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:19 +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:21 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:23 -msgid "Get an access token and create encryption keys" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-chatgpt.md:25 -msgid "Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." -msgstr "" - #: ../../../docs/configuring-playbook-bot-chatgpt.md:27 -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)." +msgid "Obtain an access token and create encryption keys" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:29 -msgid "Adjusting the playbook configuration" +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 "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:52 -msgid "You will need to get tokens for ChatGPT." +#: ../../../docs/configuring-playbook-bot-chatgpt.md:33 +msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:37 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:54 @@ -109,9 +117,13 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:73 -msgid "To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:77 msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po index 5fad573c4..70ab42f91 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -53,7 +53,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 @@ -65,7 +65,7 @@ msgid "If you would like Draupnir to be able to deactivate users, move aliases, msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 @@ -73,309 +73,313 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:59 +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:61 +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:63 +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:65 +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:67 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:76 -msgid "End-to-End Encryption support" +#: ../../../docs/configuring-playbook-bot-draupnir.md:69 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:78 -msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:80 -msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:82 -msgid "Configuration with E2EE support" +msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:84 -msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:86 +msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:100 +#: ../../../docs/configuring-playbook-bot-draupnir.md:102 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:114 +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:116 -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](#get-an-access-token)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:122 -msgid "Abuse Reports" +#: ../../../docs/configuring-playbook-bot-draupnir.md:118 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:124 -msgid "Draupnir supports two methods to receive reports in the management room." +msgid "Abuse Reports" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:126 +msgid "Draupnir supports two methods to receive reports in the management room." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:128 msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +#: ../../../docs/configuring-playbook-bot-draupnir.md:140 msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:154 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:156 +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 msgid "That is all you need to do due to that Draupnir can complete migration on its own." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:158 +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:160 +#: ../../../docs/configuring-playbook-bot-draupnir.md:162 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:175 +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:177 +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:203 +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:205 +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:207 +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:209 +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:211 +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:213 +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:221 +#: ../../../docs/configuring-playbook-bot-draupnir.md:223 msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:222 +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:224 +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:226 +#: ../../../docs/configuring-playbook-bot-draupnir.md:228 msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:227 +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:229 +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:231 +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:233 +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:235 +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:237 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:239 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:241 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:243 +#: ../../../docs/configuring-playbook-bot-draupnir.md:245 msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po index fda8f1717..2009436c9 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: 2024-12-20 09:53+0200\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" @@ -41,19 +41,19 @@ msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/bl msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:11 -msgid "Registering the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:13 -msgid "The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:15 -msgid "You **need to register the bot user manually** before setting up the bot." +msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:17 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:19 @@ -61,89 +61,97 @@ msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:25 -msgid "Once the user is created you can [obtain an access token](obtaining-access-tokens.md)." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:27 -msgid "Adjusting the playbook configuration" +msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +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:193 -msgid "Adjusting the Go-NEB URL" +#: ../../../docs/configuring-playbook-bot-go-neb.md:31 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:195 -msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +#: ../../../docs/configuring-playbook-bot-go-neb.md:33 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:197 -msgid "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." +msgid "Adjusting the Go-NEB URL" msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:199 +msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:201 +msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:203 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:210 +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:218 msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:222 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +#: ../../../docs/configuring-playbook-bot-go-neb.md:224 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:227 +#: ../../../docs/configuring-playbook-bot-go-neb.md:231 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:233 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:235 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:233 +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:235 +#: ../../../docs/configuring-playbook-bot-go-neb.md:239 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:239 +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:241 -msgid "If you enabled the github_cmd service you can get the supported commands via `!github help`" +#: ../../../docs/configuring-playbook-bot-go-neb.md:245 +msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +#: ../../../docs/configuring-playbook-bot-go-neb.md:247 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po index e996cc5a3..2cf15ee0d 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -41,7 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:11 -msgid "To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:26 @@ -109,13 +109,17 @@ msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:69 -msgid "To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room." +msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:71 -msgid "Send `!ho help` to the room to see the bot's help menu for additional commands." +msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room." msgstr "" #: ../../../docs/configuring-playbook-bot-honoroit.md:73 +msgid "Send `!ho help` to the bot in the room to see the available commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-honoroit.md:75 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po index d5efd5bbc..b3110a4dc 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -37,7 +37,7 @@ msgid "See the project's [documentation](https://github.com/moan0s/matrix-regist msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9 -msgid "Configuration" +msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11 @@ -85,7 +85,7 @@ msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.c msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55 -msgid "In this room send `help` and the bot will reply with all options." +msgid "Send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po index d6abfb68d..20f7e1e24 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -41,7 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po index b2e8d722c..2ea984e1e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -41,7 +41,7 @@ msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:11 -msgid "To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:26 @@ -61,6 +61,7 @@ msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_ msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:34 +#: ../../../docs/configuring-playbook-bot-maubot.md:56 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" @@ -81,65 +82,85 @@ msgid "If you've decided to use the default hostname, you won't need to do any e msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:50 -msgid "Installing" +msgid "Customizing the maubot container image" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.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:" +msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-maubot.md:59 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:61 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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." +#: ../../../docs/configuring-playbook-bot-maubot.md:54 +msgid "You can customize the default maubot container image and install your own dependencies." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:67 -msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:69 -msgid "Usage" +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:71 -msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:73 -msgid "You should start in the following order" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:74 -msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:75 -msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:76 -msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 -msgid "Obtaining an access token" +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 -msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:82 -msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:84 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:86 +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:88 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:90 +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:92 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:93 +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:94 +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:95 +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:97 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:99 +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:101 +msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:103 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po index 4d52e2e66..2cac78d7c 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -45,7 +45,7 @@ msgid "The playbook does not automatically create users for you. You **need to r msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:13 -msgid "Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`." +msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:15 @@ -57,7 +57,7 @@ msgid "If you would like Mjolnir to be able to deactivate users, move aliases, s msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:23 -msgid "Get an access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:25 @@ -65,157 +65,161 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 -msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 -msgid "End-to-End Encryption support" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:65 +msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:74 -msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." +msgid "End-to-End Encryption support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:76 -msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." +msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:78 -msgid "Configuration with E2EE support" +msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:80 -msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgid "Configuration with E2EE support" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:82 +msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:98 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 -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](#get-an-access-token)." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 -msgid "Adding Mjolnir synapse antispam module (optional)" +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +msgid "Adding Mjolnir synapse antispam module (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:122 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:136 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:152 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:171 msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po index 9597f9293..555b4be9c 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: 2024-12-16 12:05+0900\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" @@ -114,7 +114,7 @@ msgid "If the bot is not already in the Discord server, follow the provided invi msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66 -msgid "On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users." +msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68 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 be0b9f9c8..879f96227 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: 2024-12-20 09:53+0200\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" @@ -149,7 +149,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 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 958c405a0..4cf9ddce5 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: 2024-12-20 09:53+0200\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" @@ -73,5 +73,5 @@ msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with msgstr "" #: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36 -msgid "Send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." 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 e7459a3d9..cd25974f7 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: 2024-12-20 09:53+0200\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" @@ -113,7 +113,7 @@ msgid "Make sure the bot is able to send state events (usually the Moderator pow msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:64 -msgid "Send `!hookshot help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:66 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 fa8864352..c37fee3cc 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: 2024-12-16 12:05+0900\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" @@ -173,7 +173,7 @@ msgid "After confirming (in the Discord app) that you'd like to allow this login msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to" +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80 @@ -233,7 +233,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 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 4ff5d1c8a..bb31537fd 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: 2024-12-16 12:05+0900\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" @@ -149,7 +149,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 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 befacc522..9ddab67b7 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: 2024-12-16 12:05+0900\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" @@ -117,7 +117,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 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 adf3e0f3b..843db4c5a 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: 2024-12-16 12:05+0900\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" @@ -137,7 +137,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 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 0aca553fe..1bfea7e5b 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: 2024-12-16 12:05+0900\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" @@ -137,7 +137,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 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 71919b61e..162d6c528 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: 2024-12-16 12:05+0900\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" @@ -197,7 +197,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 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 ed1a47c96..62e9ae19b 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: 2024-12-16 12:05+0900\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" @@ -233,7 +233,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 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 529fb825d..cd3278b10 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: 2024-12-16 12:05+0900\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" @@ -185,7 +185,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 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 0ba7b089c..13eb94f02 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: 2024-12-16 12:05+0900\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" @@ -145,7 +145,7 @@ msgid "The bot should respond with \"Successfully logged into for team < msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66 -msgid "Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to." +msgid "Now that you're logged in, you can send `help` to the bot to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67 @@ -185,7 +185,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 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 0415d7248..1246af68f 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: 2024-12-16 12:05+0900\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" @@ -141,7 +141,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 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 e05a23047..f2c461f42 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: 2024-12-20 09:53+0200\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" @@ -133,7 +133,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 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 db8a16cff..2e12be38c 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: 2024-12-16 12:05+0900\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" @@ -137,7 +137,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 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 be69ce8ad..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: 2024-12-20 09:53+0200\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" @@ -97,5 +97,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46 -msgid "Also send `help` to the bot to see the commands available." +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 7b9c350c6..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: 2024-12-20 09:53+0200\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" @@ -89,5 +89,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48 -msgid "Also send `help` to the bot to see the commands available." +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 d58429322..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: 2024-12-16 12:05+0900\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" @@ -101,5 +101,5 @@ msgid "If you are linking only one Instagram account, your `$puppetId` is probab msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48 -msgid "The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented." +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-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po index e0cc1584d..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: 2024-12-20 09:53+0200\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" @@ -97,5 +97,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51 -msgid "Also send `help` to the bot to see the commands available." +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 39037aabe..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: 2024-12-20 09:53+0200\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" @@ -85,5 +85,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42 -msgid "Also send `help` to the bot to see the commands available." +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 405bfd428..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: 2024-12-20 09:53+0200\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" @@ -97,5 +97,5 @@ msgid "Clicking rooms in the list will result in you receiving an invitation to msgstr "" #: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53 -msgid "Also send `help` to the bot to see the commands available." +msgid "Send `help` to the bot to see the available commands." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po index 87c74e8c5..6e8b01d9e 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -121,7 +121,7 @@ msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:74 -msgid "Send `!pm help` to the room to see the bridge's help menu for additional commands." +msgid "Send `!pm help` to the bot in the room to see the available commands." msgstr "" #: ../../../docs/configuring-playbook-bridge-postmoogle.md:76 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 15d9c546e..77b63cfc0 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: 2024-12-16 12:05+0900\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" @@ -125,7 +125,7 @@ msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:85 -msgid "To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working." +msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working." msgstr "" #: ../../../docs/configuring-playbook-cactus-comments.md:87 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 ed1278ad1..70fd29702 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: 2024-12-16 12:05+0900\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" @@ -25,137 +25,158 @@ msgid "Setting up Dimension integration manager (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:3 -msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:5 -msgid "**Note**: 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:7 -msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:9 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:11 -msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:17 -msgid "Define admin users" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:19 -msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:27 -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:29 -msgid "Access token" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:31 -msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:33 -msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:35 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:37 -msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:43 -msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:45 -msgid "Adjusting the Dimension URL" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:47 -msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:49 -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:51 -msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:62 -msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:64 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:66 -msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:68 -msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:70 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +#: ../../../docs/configuring-playbook-dimension.md:91 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:81 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../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:83 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:85 -msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +#: ../../../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:87 -msgid "Jitsi domain" +#: ../../../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:89 -msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:91 -msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +#: ../../../docs/configuring-playbook-dimension.md:13 +msgid "Install Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:15 +msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Register a dedicated Matrix user (optional, recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:21 +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:23 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:29 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:55 +msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:57 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:59 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:61 +msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:63 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:74 +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:76 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:78 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:80 +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:82 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:84 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:93 -msgid "Additional features" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:95 -msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:97 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:99 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:101 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:103 +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:105 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:107 +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:109 msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po index 129b07f5c..8fcce52cb 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: 2024-12-20 09:53+0200\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" @@ -69,113 +69,129 @@ msgid "For details about using Email2Matrix alongside [Postfix](http://www.postf msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:25 -msgid "Creating a user" +msgid "Register a dedicated Matrix user (optional, recommended)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:27 -msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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." +msgid "We recommend that you create a dedicated Matrix user for Email2Matrix." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:29 -msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:31 -msgid "Creating a shared room" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:33 -msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:35 -msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." +msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:37 -msgid "Inviting additional people to the room is okay too." +msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:39 -msgid "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." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:41 -msgid "Obtaining an access token for the sender user" +msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 -msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:45 -msgid "Adjusting the playbook configuration" +msgid "Join to rooms as the sender user manually" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:47 -msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:72 -msgid "where:" +#: ../../../docs/configuring-playbook-email2matrix.md:49 +msgid "For each new room you would like the user to deliver messages to, invite the user to the room." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:74 -msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +#: ../../../docs/configuring-playbook-email2matrix.md:51 +msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:75 -msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +#: ../../../docs/configuring-playbook-email2matrix.md:53 +msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:76 -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" +#: ../../../docs/configuring-playbook-email2matrix.md:55 +msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:77 -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)" +#: ../../../docs/configuring-playbook-email2matrix.md:57 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:78 -msgid "MatrixAccessToken - sender user's access token" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:79 -msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:80 -msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:81 -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:83 -msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +#: ../../../docs/configuring-playbook-email2matrix.md:59 +msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:85 -msgid "Installing" +msgid "where:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:88 +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:89 +msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:90 +msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:91 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:92 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:94 -msgid "**Notes**:" +msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:96 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:98 -msgid "`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." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:100 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:107 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:109 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:111 +msgid "`just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:113 msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po index 5ce63d953..00813eb43 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: 2024-12-16 12:05+0900\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" @@ -89,7 +89,7 @@ msgid "By default, you will need to create a CNAME record for `jitsi`. See [Conf msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:43 -msgid "(Optional) Configure Jitsi authentication and guests mode" +msgid "Configure Jitsi authentication and guests mode (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:45 @@ -165,7 +165,7 @@ msgid "For more information refer to the [docker-jitsi-meet](https://github.com/ msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:115 -msgid "(Optional) Making your Jitsi server work on a LAN" +msgid "Making your Jitsi server work on a LAN (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:117 @@ -185,7 +185,7 @@ msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars. msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:130 -msgid "(Optional) Fine tune Jitsi" +msgid "Fine tune Jitsi (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:132 @@ -209,7 +209,7 @@ msgid "You may want to **limit the maximum video resolution**, to save up resour msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:155 -msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgid "Specify a Max number of participants on a Jitsi conference (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:157 @@ -221,7 +221,7 @@ msgid "In order to set the max number of participants use the following **additi msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:165 -msgid "(Optional) Additional JVBs" +msgid "Additional JVBs (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:167 @@ -273,7 +273,7 @@ msgid "To make Traefik reverse-proxy to these additional JVBs (living on other h msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:256 -msgid "(Optional) Enable Gravatar" +msgid "Enable Gravatar (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:258 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 9a742c046..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: 2024-12-16 12:05+0900\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" @@ -77,7 +77,7 @@ msgid "Additional common configuration options:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:91 -msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:93 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po index 35da30ba4..55c520ed5 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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" @@ -97,7 +97,7 @@ msgid "In the default configuration, the UVS Server is only reachable via the do msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:42 -msgid "Access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:44 @@ -109,15 +109,15 @@ msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:48 -msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:50 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:56 -msgid "(Optional) Custom Auth Token" +msgid "Custom Auth Token (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:58 @@ -137,7 +137,7 @@ msgid "In case Jitsi is also managed by this playbook and 'matrix' authenticatio msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:70 -msgid "(Optional) Disable Auth" +msgid "Disable Auth (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:72 @@ -145,7 +145,7 @@ msgid "Authorization is enabled by default. To disable it, add the following con msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:78 -msgid "(Optional) Federation" +msgid "Federation (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:80 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 be002abbb..20a45a880 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: 2024-12-16 12:05+0900\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" @@ -93,7 +93,7 @@ msgid "However, this playbook installs your Matrix server on another domain (e.g msgstr "" #: ../../../docs/configuring-well-known.md:37 -msgid "(Optional) Support Service Discovery" +msgid "Support Service Discovery (optional)" msgstr "" #: ../../../docs/configuring-well-known.md:39 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po index 8304c4748..f31b86f09 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-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: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 2024-12-23 13:09+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: jp\n" @@ -129,7 +129,7 @@ msgid "For more details on how to configure the playbook to work with SRV delega msgstr "" #: ../../../docs/howto-server-delegation.md:54 -msgid "Obtaining certificates" +msgid "Obtain certificates" msgstr "" #: ../../../docs/howto-server-delegation.md:56 diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po index 00e65f61c..92a7ac762 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: 2024-12-16 12:05+0900\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" @@ -61,137 +61,141 @@ msgid "To make use of this Synapse Admin API, **you'll need an admin access toke msgstr "" #: ../../../docs/maintenance-synapse.md:21 -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." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/maintenance-synapse.md:23 -msgid "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." +msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file." msgstr "" #: ../../../docs/maintenance-synapse.md:25 -msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions." msgstr "" #: ../../../docs/maintenance-synapse.md:27 -msgid "Compressing state with rust-synapse-compress-state" +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:29 -msgid "[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." +msgid "Compressing state with rust-synapse-compress-state" msgstr "" #: ../../../docs/maintenance-synapse.md:31 -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." +msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database." msgstr "" #: ../../../docs/maintenance-synapse.md:33 -msgid "`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." +msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again." msgstr "" #: ../../../docs/maintenance-synapse.md:35 +msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:37 msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" -#: ../../../docs/maintenance-synapse.md:41 +#: ../../../docs/maintenance-synapse.md:43 msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" -#: ../../../docs/maintenance-synapse.md:43 +#: ../../../docs/maintenance-synapse.md:45 msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above." msgstr "" -#: ../../../docs/maintenance-synapse.md:45 +#: ../../../docs/maintenance-synapse.md:47 msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:47 +#: ../../../docs/maintenance-synapse.md:49 msgid "Browse and manipulate the database" msgstr "" -#: ../../../docs/maintenance-synapse.md:49 +#: ../../../docs/maintenance-synapse.md:51 msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs." msgstr "" -#: ../../../docs/maintenance-synapse.md:51 +#: ../../../docs/maintenance-synapse.md:53 msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:53 +#: ../../../docs/maintenance-synapse.md:55 msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" -#: ../../../docs/maintenance-synapse.md:60 +#: ../../../docs/maintenance-synapse.md:62 msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:" msgstr "" -#: ../../../docs/maintenance-synapse.md:66 +#: ../../../docs/maintenance-synapse.md:68 msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)" msgstr "" -#: ../../../docs/maintenance-synapse.md:68 +#: ../../../docs/maintenance-synapse.md:70 msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" -#: ../../../docs/maintenance-synapse.md:70 +#: ../../../docs/maintenance-synapse.md:72 msgid "Make Synapse faster" msgstr "" -#: ../../../docs/maintenance-synapse.md:72 +#: ../../../docs/maintenance-synapse.md:74 msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:74 +#: ../../../docs/maintenance-synapse.md:76 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:76 +#: ../../../docs/maintenance-synapse.md:78 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:78 +#: ../../../docs/maintenance-synapse.md:80 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:80 +#: ../../../docs/maintenance-synapse.md:82 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:82 +#: ../../../docs/maintenance-synapse.md:84 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:84 +#: ../../../docs/maintenance-synapse.md:86 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:86 +#: ../../../docs/maintenance-synapse.md:88 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:88 +#: ../../../docs/maintenance-synapse.md:90 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:89 +#: ../../../docs/maintenance-synapse.md:91 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:92 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:94 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:96 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:104 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:106 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po index 7302f99d6..9eda037b9 100644 --- a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po +++ b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-16 12:05+0900\n" +"POT-Creation-Date: 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" @@ -29,7 +29,7 @@ msgid "When setting up some optional features like bots and bridges you will nee msgstr "" #: ../../../docs/obtaining-access-tokens.md:5 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/obtaining-access-tokens.md:7 diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot index 7782e5c8f..824ef02d4 100644 --- a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot +++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\n" +"POT-Creation-Date: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -65,97 +65,101 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:29 -msgid "Join to rooms as the bot manually" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:31 -msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." +msgid "Join to rooms as the bot manually" msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:33 -msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." +msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:35 -msgid "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." +msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:37 -msgid "Adjusting the playbook configuration" +msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out." msgstr "" #: ../../../docs/configuring-playbook-alertmanager-receiver.md:39 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:60 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 msgid "Adjusting the matrix-alertmanager-receiver URL" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:68 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:70 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:76 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80 msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82 msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84 msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:93 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:95 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105 msgid "Configure your Prometheus Alertmanager with configuration like this:" msgstr "" -#: ../../../docs/configuring-playbook-alertmanager-receiver.md:122 +#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124 msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot index 19e496fdb..bd944f467 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\n" +"POT-Creation-Date: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -69,53 +69,57 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:31 -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)." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:33 -msgid "Adjusting the playbook configuration" +msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)." msgstr "" #: ../../../docs/configuring-playbook-bot-chatgpt.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-chatgpt.md:37 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:52 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:54 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:56 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:61 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:63 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:65 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:67 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:69 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:71 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:73 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-chatgpt.md:75 +#: ../../../docs/configuring-playbook-bot-chatgpt.md:77 msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot index 645d34ac6..952063e39 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\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-Team: LANGUAGE \n" @@ -69,309 +69,313 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:37 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:39 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:43 +#: ../../../docs/configuring-playbook-bot-draupnir.md:45 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:45 +#: ../../../docs/configuring-playbook-bot-draupnir.md:47 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:47 +#: ../../../docs/configuring-playbook-bot-draupnir.md:49 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:53 +#: ../../../docs/configuring-playbook-bot-draupnir.md:55 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:55 +#: ../../../docs/configuring-playbook-bot-draupnir.md:57 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:57 +#: ../../../docs/configuring-playbook-bot-draupnir.md:59 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:59 +#: ../../../docs/configuring-playbook-bot-draupnir.md:61 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:61 +#: ../../../docs/configuring-playbook-bot-draupnir.md:63 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:63 +#: ../../../docs/configuring-playbook-bot-draupnir.md:65 msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:65 +#: ../../../docs/configuring-playbook-bot-draupnir.md:67 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:67 +#: ../../../docs/configuring-playbook-bot-draupnir.md:69 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:76 +#: ../../../docs/configuring-playbook-bot-draupnir.md:78 msgid "End-to-End Encryption support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:78 +#: ../../../docs/configuring-playbook-bot-draupnir.md:80 msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:80 +#: ../../../docs/configuring-playbook-bot-draupnir.md:82 msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:82 +#: ../../../docs/configuring-playbook-bot-draupnir.md:84 msgid "Configuration with E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:84 +#: ../../../docs/configuring-playbook-bot-draupnir.md:86 msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:86 +#: ../../../docs/configuring-playbook-bot-draupnir.md:88 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:100 +#: ../../../docs/configuring-playbook-bot-draupnir.md:102 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:112 +#: ../../../docs/configuring-playbook-bot-draupnir.md:114 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:114 +#: ../../../docs/configuring-playbook-bot-draupnir.md:116 msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:116 +#: ../../../docs/configuring-playbook-bot-draupnir.md:118 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:122 +#: ../../../docs/configuring-playbook-bot-draupnir.md:124 msgid "Abuse Reports" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:124 +#: ../../../docs/configuring-playbook-bot-draupnir.md:126 msgid "Draupnir supports two methods to receive reports in the management room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:126 +#: ../../../docs/configuring-playbook-bot-draupnir.md:128 msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +#: ../../../docs/configuring-playbook-bot-draupnir.md:140 msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:154 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:156 +#: ../../../docs/configuring-playbook-bot-draupnir.md:158 msgid "That is all you need to do due to that Draupnir can complete migration on its own." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:158 +#: ../../../docs/configuring-playbook-bot-draupnir.md:160 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:160 +#: ../../../docs/configuring-playbook-bot-draupnir.md:162 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:175 +#: ../../../docs/configuring-playbook-bot-draupnir.md:177 msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:177 +#: ../../../docs/configuring-playbook-bot-draupnir.md:179 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:183 +#: ../../../docs/configuring-playbook-bot-draupnir.md:185 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:185 +#: ../../../docs/configuring-playbook-bot-draupnir.md:187 msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:187 +#: ../../../docs/configuring-playbook-bot-draupnir.md:189 msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:189 +#: ../../../docs/configuring-playbook-bot-draupnir.md:191 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:191 +#: ../../../docs/configuring-playbook-bot-draupnir.md:193 msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:193 +#: ../../../docs/configuring-playbook-bot-draupnir.md:195 msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:195 +#: ../../../docs/configuring-playbook-bot-draupnir.md:197 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:197 +#: ../../../docs/configuring-playbook-bot-draupnir.md:199 msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:199 +#: ../../../docs/configuring-playbook-bot-draupnir.md:201 msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:201 +#: ../../../docs/configuring-playbook-bot-draupnir.md:203 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:203 +#: ../../../docs/configuring-playbook-bot-draupnir.md:205 msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:205 +#: ../../../docs/configuring-playbook-bot-draupnir.md:207 msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:207 +#: ../../../docs/configuring-playbook-bot-draupnir.md:209 msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:209 +#: ../../../docs/configuring-playbook-bot-draupnir.md:211 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:211 +#: ../../../docs/configuring-playbook-bot-draupnir.md:213 msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:213 +#: ../../../docs/configuring-playbook-bot-draupnir.md:215 msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:221 +#: ../../../docs/configuring-playbook-bot-draupnir.md:223 msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:222 +#: ../../../docs/configuring-playbook-bot-draupnir.md:224 msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:224 +#: ../../../docs/configuring-playbook-bot-draupnir.md:226 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:226 +#: ../../../docs/configuring-playbook-bot-draupnir.md:228 msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:227 +#: ../../../docs/configuring-playbook-bot-draupnir.md:229 msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:229 +#: ../../../docs/configuring-playbook-bot-draupnir.md:231 msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:231 +#: ../../../docs/configuring-playbook-bot-draupnir.md:233 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:233 +#: ../../../docs/configuring-playbook-bot-draupnir.md:235 msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:235 +#: ../../../docs/configuring-playbook-bot-draupnir.md:237 msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:237 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:239 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:241 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:243 +#: ../../../docs/configuring-playbook-bot-draupnir.md:245 msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot index ce2d7387a..6897302ae 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\n" +"POT-Creation-Date: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -65,85 +65,89 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:29 -msgid "Adjusting the playbook configuration" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-go-neb.md:31 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-go-neb.md:33 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:195 +#: ../../../docs/configuring-playbook-bot-go-neb.md:197 msgid "Adjusting the Go-NEB URL" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:197 +#: ../../../docs/configuring-playbook-bot-go-neb.md:199 msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:199 +#: ../../../docs/configuring-playbook-bot-go-neb.md:201 msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:201 +#: ../../../docs/configuring-playbook-bot-go-neb.md:203 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:212 +#: ../../../docs/configuring-playbook-bot-go-neb.md:214 msgid "Adjusting DNS records" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:214 +#: ../../../docs/configuring-playbook-bot-go-neb.md:216 msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:216 +#: ../../../docs/configuring-playbook-bot-go-neb.md:218 msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:218 +#: ../../../docs/configuring-playbook-bot-go-neb.md:220 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:220 +#: ../../../docs/configuring-playbook-bot-go-neb.md:222 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:222 +#: ../../../docs/configuring-playbook-bot-go-neb.md:224 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:229 +#: ../../../docs/configuring-playbook-bot-go-neb.md:231 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:231 +#: ../../../docs/configuring-playbook-bot-go-neb.md:233 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:233 +#: ../../../docs/configuring-playbook-bot-go-neb.md:235 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:235 +#: ../../../docs/configuring-playbook-bot-go-neb.md:237 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:237 +#: ../../../docs/configuring-playbook-bot-go-neb.md:239 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:239 +#: ../../../docs/configuring-playbook-bot-go-neb.md:241 msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:241 +#: ../../../docs/configuring-playbook-bot-go-neb.md:243 msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`" msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:243 +#: ../../../docs/configuring-playbook-bot-go-neb.md:245 msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bot-go-neb.md:245 +#: ../../../docs/configuring-playbook-bot-go-neb.md:247 msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot index 3bbb8d3d2..463906876 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\n" +"POT-Creation-Date: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -57,6 +57,7 @@ msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_ msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:34 +#: ../../../docs/configuring-playbook-bot-maubot.md:56 msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" @@ -77,65 +78,85 @@ msgid "If you've decided to use the default hostname, you won't need to do any e msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:50 -msgid "Installing" +msgid "Customizing the maubot container image" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.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:" +msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-maubot.md:59 -msgid "**Notes**:" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:61 -msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md: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-bot-maubot.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." +#: ../../../docs/configuring-playbook-bot-maubot.md:54 +msgid "You can customize the default maubot container image and install your own dependencies." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:67 -msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:69 -msgid "Usage" +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:71 -msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:73 -msgid "You should start in the following order" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:74 -msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:75 -msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-maubot.md:76 -msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:78 -msgid "Obtain an access token" +msgid "**Notes**:" msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:80 -msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" #: ../../../docs/configuring-playbook-bot-maubot.md:82 -msgid "Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:84 +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:86 +msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:88 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:90 +msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:92 +msgid "You should start in the following order" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:93 +msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:94 +msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:95 +msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:97 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:99 +msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:101 +msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-maubot.md:103 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot index a033bff46..e5d06bb95 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\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-Team: LANGUAGE \n" @@ -61,157 +61,161 @@ msgid "The bot requires an access token to be able to connect to your homeserver msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:27 -msgid "Make sure the account is free from rate limiting" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:29 -msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" +msgid "Make sure the account is free from rate limiting" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:31 -msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:33 +msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-mjolnir.md:35 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:39 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:57 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:59 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:65 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 msgid "End-to-End Encryption support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:76 msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:76 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 msgid "Configuration with E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:96 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:98 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:120 msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:120 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:122 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:134 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:136 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:150 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:152 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:157 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:159 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:161 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:163 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:165 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:167 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:169 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:171 msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot index 0d38f2077..cb917fa11 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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-Team: LANGUAGE \n" @@ -145,7 +145,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75 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 42c732f37..9a18465db 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: 2024-12-20 23:17+0900\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-Team: LANGUAGE \n" @@ -229,7 +229,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot index 3c03c30fb..ac1d04009 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -145,7 +145,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot index 6e2f83980..f5fa7acb1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -113,7 +113,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot index 004ff9bd0..14dd76870 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -133,7 +133,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot index fecd8edf9..e05c6c2eb 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -133,7 +133,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot index b71e4bb98..6a658af27 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -193,7 +193,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot index 3d2e0cebf..16fece3ae 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -229,7 +229,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot index a931c0168..732776d30 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -181,7 +181,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111 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 3cdcf38e4..30988952e 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: 2024-12-20 23:17+0900\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-Team: LANGUAGE \n" @@ -181,7 +181,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot index a83d5467f..cf64deff8 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -137,7 +137,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot index ece21b5ac..612714ca8 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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-Team: LANGUAGE \n" @@ -129,7 +129,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67 diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot index 3cbe6494c..b393ba2e3 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -133,7 +133,7 @@ msgid "When using this method, **each user** that wishes to enable Double Puppet msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76 -msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md)." +msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78 diff --git a/i18n/translation-templates/docs/configuring-playbook-dimension.pot b/i18n/translation-templates/docs/configuring-playbook-dimension.pot index ec8a03f96..3dbfc4bf3 100644 --- a/i18n/translation-templates/docs/configuring-playbook-dimension.pot +++ b/i18n/translation-templates/docs/configuring-playbook-dimension.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -21,137 +21,158 @@ msgid "Setting up Dimension integration manager (optional, unmaintained)" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:3 -msgid "**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:5 -msgid "**Note**: 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:7 -msgid "**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:9 -msgid "Adjusting the playbook configuration" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:11 -msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:17 -msgid "Define admin users" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:19 -msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:27 -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:29 -msgid "Access token" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:31 -msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:33 -msgid "You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:35 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:37 -msgid "Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:43 -msgid "For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:45 -msgid "Adjusting the Dimension URL" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:47 -msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:49 -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:51 -msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:62 -msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:64 -msgid "Adjusting DNS records" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:66 -msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:68 -msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.md:70 -msgid "Installing" -msgstr "" - -#: ../../../docs/configuring-playbook-dimension.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-dimension.md:79 +#: ../../../docs/configuring-playbook-dimension.md:91 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:81 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" +#: ../../../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:83 -msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." +#: ../../../docs/configuring-playbook-dimension.md:5 +msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)." msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:85 -msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +#: ../../../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:87 -msgid "Jitsi domain" +#: ../../../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:89 -msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +#: ../../../docs/configuring-playbook-dimension.md:11 +msgid "Prerequisites" msgstr "" -#: ../../../docs/configuring-playbook-dimension.md:91 -msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +#: ../../../docs/configuring-playbook-dimension.md:13 +msgid "Install Matrix services" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:15 +msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:17 +msgid "Register a dedicated Matrix user (optional, recommended)" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:19 +msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:21 +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:23 +msgid "You can use the playbook to [register a new user](registering-users.md):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:29 +msgid "Obtain an access token" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:31 +msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:33 +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:35 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:37 +msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:45 +msgid "Define admin users" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:47 +msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:55 +msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:57 +msgid "Adjusting the Dimension URL" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:59 +msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:61 +msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:63 +msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:74 +msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:76 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:78 +msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:80 +msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:82 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:84 +msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:93 -msgid "Additional features" +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`" msgstr "" #: ../../../docs/configuring-playbook-dimension.md:95 -msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-dimension.md:97 +msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:99 +msgid "Jitsi domain" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:101 +msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:103 +msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:105 +msgid "Additional features" +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:107 +msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component." +msgstr "" + +#: ../../../docs/configuring-playbook-dimension.md:109 msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot index f508b138b..4b61b12f1 100644 --- a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot +++ b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-23 13:09+0900\n" +"POT-Creation-Date: 2024-12-28 10:25+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -65,113 +65,129 @@ msgid "For details about using Email2Matrix alongside [Postfix](http://www.postf msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:25 -msgid "Creating a user" +msgid "Register a dedicated Matrix user (optional, recommended)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:27 -msgid "Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. 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." +msgid "We recommend that you create a dedicated Matrix user for Email2Matrix." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:29 -msgid "Refer to [Registering users](registering-users.md) for ways to create a user. A regular (non-admin) user works best." +msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:31 -msgid "Creating a shared room" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:33 -msgid "After creating the sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user)." -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:35 -msgid "What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there." +msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:37 -msgid "Inviting additional people to the room is okay too." +msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:39 -msgid "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." +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:41 -msgid "Obtain an access token for the sender user" +msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:43 -msgid "In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:45 -msgid "Adjusting the playbook configuration" +msgid "Join to rooms as the sender user manually" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:47 -msgid "After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):" +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:72 -msgid "where:" +#: ../../../docs/configuring-playbook-email2matrix.md:49 +msgid "For each new room you would like the user to deliver messages to, invite the user to the room." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:74 -msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +#: ../../../docs/configuring-playbook-email2matrix.md:51 +msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:75 -msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +#: ../../../docs/configuring-playbook-email2matrix.md:53 +msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:76 -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" +#: ../../../docs/configuring-playbook-email2matrix.md:55 +msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below." msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:77 -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)" +#: ../../../docs/configuring-playbook-email2matrix.md:57 +msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-email2matrix.md:78 -msgid "MatrixAccessToken - sender user's access token" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:79 -msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:80 -msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" -msgstr "" - -#: ../../../docs/configuring-playbook-email2matrix.md:81 -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:83 -msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." +#: ../../../docs/configuring-playbook-email2matrix.md:59 +msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:85 -msgid "Installing" +msgid "where:" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:87 -msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:88 +msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:89 +msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:90 +msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:91 +msgid "MatrixAccessToken - sender user's access token" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:92 +msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:93 +msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:94 -msgid "**Notes**:" +msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:96 -msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)." msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:98 -msgid "`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." +msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-email2matrix.md:100 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:107 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:109 +msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`" +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:111 +msgid "`just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too." +msgstr "" + +#: ../../../docs/configuring-playbook-email2matrix.md:113 msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-jitsi.pot b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot index 05c2280b2..a6f074789 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: 2024-12-20 07:23+0200\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-Team: LANGUAGE \n" @@ -85,7 +85,7 @@ msgid "By default, you will need to create a CNAME record for `jitsi`. See [Conf msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:43 -msgid "(Optional) Configure Jitsi authentication and guests mode" +msgid "Configure Jitsi authentication and guests mode (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:45 @@ -161,7 +161,7 @@ msgid "For more information refer to the [docker-jitsi-meet](https://github.com/ msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:115 -msgid "(Optional) Making your Jitsi server work on a LAN" +msgid "Making your Jitsi server work on a LAN (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:117 @@ -181,7 +181,7 @@ msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars. msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:130 -msgid "(Optional) Fine tune Jitsi" +msgid "Fine tune Jitsi (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:132 @@ -205,7 +205,7 @@ msgid "You may want to **limit the maximum video resolution**, to save up resour msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:155 -msgid "(Optional) Specify a Max number of participants on a Jitsi conference" +msgid "Specify a Max number of participants on a Jitsi conference (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:157 @@ -217,7 +217,7 @@ msgid "In order to set the max number of participants use the following **additi msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:165 -msgid "(Optional) Additional JVBs" +msgid "Additional JVBs (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:167 @@ -269,7 +269,7 @@ msgid "To make Traefik reverse-proxy to these additional JVBs (living on other h msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:256 -msgid "(Optional) Enable Gravatar" +msgid "Enable Gravatar (optional)" msgstr "" #: ../../../docs/configuring-playbook-jitsi.md:258 diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot index c75b2e87c..40aeb8401 100644 --- a/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot +++ b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -73,7 +73,7 @@ msgid "Additional common configuration options:" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:91 -msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)" +msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)" msgstr "" #: ../../../docs/configuring-playbook-matrix-media-repo.md:93 diff --git a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot index 7a47a11a8..04afcda54 100644 --- a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot +++ b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 09:53+0200\n" +"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-Team: LANGUAGE \n" @@ -93,7 +93,7 @@ msgid "In the default configuration, the UVS Server is only reachable via the do msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:42 -msgid "Access token" +msgid "Obtain an access token" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:44 @@ -105,15 +105,15 @@ msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:48 -msgid "You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md)." +msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:50 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:56 -msgid "(Optional) Custom Auth Token" +msgid "Custom Auth Token (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:58 @@ -133,7 +133,7 @@ msgid "In case Jitsi is also managed by this playbook and 'matrix' authenticatio msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:70 -msgid "(Optional) Disable Auth" +msgid "Disable Auth (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:72 @@ -141,7 +141,7 @@ msgid "Authorization is enabled by default. To disable it, add the following con msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:78 -msgid "(Optional) Federation" +msgid "Federation (optional)" msgstr "" #: ../../../docs/configuring-playbook-user-verification-service.md:80 diff --git a/i18n/translation-templates/docs/configuring-well-known.pot b/i18n/translation-templates/docs/configuring-well-known.pot index 157258f8f..7b35a517d 100644 --- a/i18n/translation-templates/docs/configuring-well-known.pot +++ b/i18n/translation-templates/docs/configuring-well-known.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -89,7 +89,7 @@ msgid "However, this playbook installs your Matrix server on another domain (e.g msgstr "" #: ../../../docs/configuring-well-known.md:37 -msgid "(Optional) Support Service Discovery" +msgid "Support Service Discovery (optional)" msgstr "" #: ../../../docs/configuring-well-known.md:39 diff --git a/i18n/translation-templates/docs/maintenance-synapse.pot b/i18n/translation-templates/docs/maintenance-synapse.pot index b33365b79..a205c177a 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: 2024-12-20 07:23+0200\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-Team: LANGUAGE \n" @@ -57,137 +57,141 @@ msgid "To make use of this Synapse Admin API, **you'll need an admin access toke msgstr "" #: ../../../docs/maintenance-synapse.md:21 -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." +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/maintenance-synapse.md:23 -msgid "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." +msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file." msgstr "" #: ../../../docs/maintenance-synapse.md:25 -msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." +msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions." msgstr "" #: ../../../docs/maintenance-synapse.md:27 -msgid "Compressing state with rust-synapse-compress-state" +msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" #: ../../../docs/maintenance-synapse.md:29 -msgid "[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." +msgid "Compressing state with rust-synapse-compress-state" msgstr "" #: ../../../docs/maintenance-synapse.md:31 -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." +msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database." msgstr "" #: ../../../docs/maintenance-synapse.md:33 -msgid "`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." +msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again." msgstr "" #: ../../../docs/maintenance-synapse.md:35 +msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first." +msgstr "" + +#: ../../../docs/maintenance-synapse.md:37 msgid "To ask the playbook to run rust-synapse-compress-state, execute:" msgstr "" -#: ../../../docs/maintenance-synapse.md:41 +#: ../../../docs/maintenance-synapse.md:43 msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`" msgstr "" -#: ../../../docs/maintenance-synapse.md:43 +#: ../../../docs/maintenance-synapse.md:45 msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above." msgstr "" -#: ../../../docs/maintenance-synapse.md:45 +#: ../../../docs/maintenance-synapse.md:47 msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:47 +#: ../../../docs/maintenance-synapse.md:49 msgid "Browse and manipulate the database" msgstr "" -#: ../../../docs/maintenance-synapse.md:49 +#: ../../../docs/maintenance-synapse.md:51 msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs." msgstr "" -#: ../../../docs/maintenance-synapse.md:51 +#: ../../../docs/maintenance-synapse.md:53 msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)." msgstr "" -#: ../../../docs/maintenance-synapse.md:53 +#: ../../../docs/maintenance-synapse.md:55 msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):" msgstr "" -#: ../../../docs/maintenance-synapse.md:60 +#: ../../../docs/maintenance-synapse.md:62 msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:" msgstr "" -#: ../../../docs/maintenance-synapse.md:66 +#: ../../../docs/maintenance-synapse.md:68 msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)" msgstr "" -#: ../../../docs/maintenance-synapse.md:68 +#: ../../../docs/maintenance-synapse.md:70 msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations." msgstr "" -#: ../../../docs/maintenance-synapse.md:70 +#: ../../../docs/maintenance-synapse.md:72 msgid "Make Synapse faster" msgstr "" -#: ../../../docs/maintenance-synapse.md:72 +#: ../../../docs/maintenance-synapse.md:74 msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file." msgstr "" -#: ../../../docs/maintenance-synapse.md:74 +#: ../../../docs/maintenance-synapse.md:76 msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)." msgstr "" -#: ../../../docs/maintenance-synapse.md:76 +#: ../../../docs/maintenance-synapse.md:78 msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually." msgstr "" -#: ../../../docs/maintenance-synapse.md:78 +#: ../../../docs/maintenance-synapse.md:80 msgid "Tuning caches and cache autotuning" msgstr "" -#: ../../../docs/maintenance-synapse.md:80 +#: ../../../docs/maintenance-synapse.md:82 msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process." msgstr "" -#: ../../../docs/maintenance-synapse.md:82 +#: ../../../docs/maintenance-synapse.md:84 msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)." msgstr "" -#: ../../../docs/maintenance-synapse.md:84 +#: ../../../docs/maintenance-synapse.md:86 msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)." msgstr "" -#: ../../../docs/maintenance-synapse.md:86 +#: ../../../docs/maintenance-synapse.md:88 msgid "Cache autotuning is **enabled by default** and controlled via the following variables:" msgstr "" -#: ../../../docs/maintenance-synapse.md:88 +#: ../../../docs/maintenance-synapse.md:90 msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` - defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:89 +#: ../../../docs/maintenance-synapse.md:91 msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` - defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes" msgstr "" -#: ../../../docs/maintenance-synapse.md:90 +#: ../../../docs/maintenance-synapse.md:92 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`" msgstr "" -#: ../../../docs/maintenance-synapse.md:92 +#: ../../../docs/maintenance-synapse.md:94 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)." msgstr "" -#: ../../../docs/maintenance-synapse.md:94 +#: ../../../docs/maintenance-synapse.md:96 msgid "To **disable cache auto-tuning**, unset all values:" msgstr "" -#: ../../../docs/maintenance-synapse.md:102 +#: ../../../docs/maintenance-synapse.md:104 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large." msgstr "" -#: ../../../docs/maintenance-synapse.md:104 +#: ../../../docs/maintenance-synapse.md:106 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)." msgstr "" diff --git a/i18n/translation-templates/docs/obtaining-access-tokens.pot b/i18n/translation-templates/docs/obtaining-access-tokens.pot index 60f498f36..d0acfad7a 100644 --- a/i18n/translation-templates/docs/obtaining-access-tokens.pot +++ b/i18n/translation-templates/docs/obtaining-access-tokens.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-12-20 07:23+0200\n" +"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-Team: LANGUAGE \n" @@ -25,7 +25,7 @@ msgid "When setting up some optional features like bots and bridges you will nee msgstr "" #: ../../../docs/obtaining-access-tokens.md:5 -msgid "**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**" +msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone." msgstr "" #: ../../../docs/obtaining-access-tokens.md:7 From 4ffa10a7b66eb482ef326659a6887a0b3c15b4a3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 3 Jan 2025 08:00:20 -0500 Subject: [PATCH 169/952] Update docs/configuring-playbook-user-verification-service.md, etc. (#3904) * Update docs/configuring-playbook-user-verification-service.md: add the common introduction Based on docs/configuring-playbook-dimension.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: use a common placeholder for an access token Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: use a common header for adjusting the playbook configuration Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: instruction for registering a dedicated user Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: use abbreviation See the line 3. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: move the section for obtaining an access token up Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: remove a redundant paragraph about necessity of token Signed-off-by: Suguru Hirahara * Update docs: notes on port 8448 for federation, etc. - Create sections for the instruction about opening Matrix Federation port - Remove unmaintained components which this project does not recommend to install from examples about opening the port on docs/prerequisites.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: create a section for explaining the function of the component Based on docs/configuring-playbook-prometheus-grafana.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: add a note about creating user as an admin Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: merge the section "Configuration" and edit it Signed-off-by: Suguru Hirahara * Apply suggestions from code review Co-authored-by: Slavi Pantaleev --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- docs/configuring-playbook-dimension.md | 6 +- docs/configuring-playbook-ma1sd.md | 6 +- ...ring-playbook-user-verification-service.md | 56 ++++++++++--------- docs/prerequisites.md | 2 +- 4 files changed, 42 insertions(+), 28 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 5e7e86b15..1c4fd99f9 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -2,7 +2,7 @@ **Notes**: - Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it. -- This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible). +- 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`. The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you. @@ -10,6 +10,10 @@ See the project's [documentation](https://github.com/turt2live/matrix-dimension/ ## Prerequisites +### Open Matrix Federation port + +Enabling the Dimension service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible. + ### Install Matrix services Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later. diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 73940d4ef..b19c0168d 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -8,7 +8,11 @@ ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) an See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you. -**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible). +## Prerequisites + +### Open Matrix Federation port + +Enabling the ma1sd service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible. ## Adjusting DNS records diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 09e5ae1dd..2f789e696 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -1,14 +1,12 @@ # Setting up Matrix User Verification Service (optional) -**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later. +The playbook can install and configure [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) for you. -Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works. +See the project's [documentation](https://github.com/matrix-org/matrix-user-verification-service/blob/master/README.md) to learn what it does and why it might be useful to you. -**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. +Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`. -If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`. - -__Some general concepts of UVS may be helpful to understand the rest, so here they are:__ +## What does it do? UVS can be used to verify two claims: @@ -21,38 +19,46 @@ Verifying RoomMembership and PowerLevel is done against `matrix_user_verificatio ## Prerequisites -In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS. +### Open Matrix Federation port -## Enable +Enabling the UVS service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible. -To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +### Install Matrix services -```yaml -matrix_user_verification_service_enabled: true +UVS can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later. + +### Register a dedicated Matrix user (optional, recommended) + +We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). **Because UVS requires an access token as an admin user, that user needs to be an admin.** + +Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`. + +You can use the playbook to [register a new user](registering-users.md): + +```sh +ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=uvs password=PASSWORD_FOR_THE_USER admin=yes' --tags=register-user ``` -## Configuration - -The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below). - -For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`. - -In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`. - ### Obtain an access token -The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. - -We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges. - -You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). +UVS requires an access token as an admin user to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). ⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +## Adjusting the playbook configuration + +To enable UVS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). + ```yaml -matrix_user_verification_service_uvs_access_token: "YOUR ACCESS TOKEN HERE" +matrix_user_verification_service_enabled: true + +matrix_user_verification_service_uvs_access_token: "ACCESS_TOKEN_HERE" ``` +Check the role's [defaults/main.yml](../roles/custom/matrix-user-verification-service/defaults/main.yml) for the full list of variables that you could override. Note that all the plugging happening in `group_vars/matrix_servers`. + +In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`. + ### Custom Auth Token (optional) It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header "Authorization: Bearer TOKEN" diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 6cbfc9a23..a574c6352 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -52,7 +52,7 @@ We will be using `example.com` as the domain in the following instruction. Pleas - `3478/udp`: TURN over UDP (used by Coturn) - `5349/tcp`: TURN over TCP (used by Coturn) - `5349/udp`: TURN over UDP (used by Coturn) - - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port. + - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**. - the range `49152-49172/udp`: TURN over UDP - potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that. From eff5e3ac2be041c358fc9e47a58f46f86af0b873 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Fri, 3 Jan 2025 13:00:53 +0000 Subject: [PATCH 170/952] Update dock.mau.dev/maubot/maubot Docker tag to v0.5.1 --- roles/custom/matrix-bot-maubot/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-maubot/defaults/main.yml b/roles/custom/matrix-bot-maubot/defaults/main.yml index 48087caa8..48c5d7464 100644 --- a/roles/custom/matrix-bot-maubot/defaults/main.yml +++ b/roles/custom/matrix-bot-maubot/defaults/main.yml @@ -20,7 +20,7 @@ matrix_bot_maubot_docker_repo: "https://mau.dev/maubot/maubot.git" matrix_bot_maubot_docker_repo_version: "{{ 'master' if matrix_bot_maubot_version == 'latest' else matrix_bot_maubot_version }}" # renovate: datasource=docker depName=dock.mau.dev/maubot/maubot -matrix_bot_maubot_version: v0.5.0 +matrix_bot_maubot_version: v0.5.1 matrix_bot_maubot_docker_image: "{{ matrix_bot_maubot_docker_image_name_prefix }}maubot/maubot:{{ matrix_bot_maubot_version }}" matrix_bot_maubot_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_maubot_container_image_self_build else 'dock.mau.dev/' }}" matrix_bot_maubot_docker_image_force_pull: "{{ matrix_bot_maubot_docker_image.endswith(':latest') }}" From 6facfb2f77d8a9665d594178a8f5e3836fad858a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 3 Jan 2025 09:54:02 -0500 Subject: [PATCH 171/952] Update docs/configuring-playbook-user-verification-service.md: adopt the common section for controlling the logging level and minor changes (#3910) * Update docs/configuring-playbook-user-verification-service.md: adopt the common section for controlling the logging level Based on: - docs/configuring-playbook-bridge-mautrix-bridges.md - roles/custom/matrix-user-verification-service/defaults/main.yml Other minor changes: - Add an upper section "troubleshooting" for "TLS Certificate Checking" - Use backticks Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- ...ring-playbook-user-verification-service.md | 23 ++++++++++++------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 2f789e696..9ff4fa60f 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -13,7 +13,7 @@ UVS can be used to verify two claims: * (A) Whether a given OpenID token is valid for a given server and * (B) whether a user is member of a given room and the corresponding PowerLevel -Verifying an OpenID token ID done by finding the corresponding Homeserver via '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`. +Verifying an OpenID token ID done by finding the corresponding Homeserver via `/.well-known/matrix/server` for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public `openid` API for `matrix_server_fqn_matrix`. Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though. @@ -91,6 +91,18 @@ matrix_user_verification_service_uvs_pin_openid_verify_server_name: false This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain. +### Controlling the logging level (optional) + +To specify the logging level, add the following configuration to your `vars.yml` file: + +```yaml +UVS_LOG_LEVEL: info +``` + +Replace `info` with one of the choices (they can be checked [here](https://github.com/winstonjs/winston#logging-levels)) to control the verbosity of the logs generated. + +If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -104,14 +116,9 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju `just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. -## Logging +## Troubleshooting -The configuration variable `UVS_LOG_LEVEL` can be set to: -- warning -- info -- debug - -## TLS Certificate Checking +### TLS Certificate Checking If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message: From ee1acdd4be3f324a57b66affe4b12b1dd64e0c6b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 4 Jan 2025 07:52:58 -0500 Subject: [PATCH 172/952] Update docs: misc edits for consistency (#3911) * Add a warning sign to "Warning" labels Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-matrix-registration.md Signed-off-by: Suguru Hirahara * Update docs/maintenance-and-troubleshooting.md: remove a section for ma1sd As the project has not updated since several years, it does not seem to be reasonable to pick it up specially on the document. Signed-off-by: Suguru Hirahara * Common header for sections about adjusting the playbook configuration Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-dendrite.md: fix links to dendrite.yaml.j2 Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-signal.md: remove a note added by a commit to remove signalgo The note has been added with 2f6525ccb3666e0ec8f295e8eeffd78bac15a23e, apparently copied from docs/configuring-playbook-bridge-mautrix-signalgo.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-wsproxy.md: fix the anchor link text to mautrix-imessage documentation Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: add a note about the component being managed externally Refer docs/configuring-playbook-backup-borg.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: use the common label for warning messages Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ldap-auth.md: unrecommend using ma1sd for authentication Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-appservice-double-puppet.md: remove a duplicate anchor link Signed-off-by: Suguru Hirahara * Update docs for old mautrix bridges for Facebook and Instagram: remove anchor links to the deleted files Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-wechat.md: use common descriptions Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-matrix-bridge-sms.md: create a section for the prerequisite Signed-off-by: Suguru Hirahara * Update docs/maintenance-and-troubleshooting.md: use the common header text Signed-off-by: Suguru Hirahara * Use common descriptions for adding the configuration Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-telegram.md: small edits - Add a section for a Telegram API key - Add a section for instruction about Appservice Double Puppet or Shared Secret Auth Signed-off-by: Suguru Hirahara * Update docs for Draupnir and Mjolnir: replace colons with periods Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-rageshake.md: adopt the common instruction Based on docs/configuring-playbook-sygnal.md regarding the notification about necessity of the service. Signed-off-by: Suguru Hirahara * Add a note about the components managed externally Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- .../configuring-playbook-appservice-double-puppet.md | 2 +- docs/configuring-playbook-backup-borg.md | 2 -- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- docs/configuring-playbook-bridge-heisenbridge.md | 2 +- .../configuring-playbook-bridge-matrix-bridge-sms.md | 4 +++- docs/configuring-playbook-bridge-mautrix-facebook.md | 2 +- .../configuring-playbook-bridge-mautrix-instagram.md | 2 -- docs/configuring-playbook-bridge-mautrix-signal.md | 2 -- docs/configuring-playbook-bridge-mautrix-telegram.md | 10 ++++++++-- docs/configuring-playbook-bridge-mautrix-wsproxy.md | 2 +- docs/configuring-playbook-bridge-wechat.md | 4 ++-- docs/configuring-playbook-cactus-comments.md | 2 +- docs/configuring-playbook-dendrite.md | 4 ++-- docs/configuring-playbook-dimension.md | 4 ++-- docs/configuring-playbook-email2matrix.md | 2 +- docs/configuring-playbook-federation.md | 6 +++--- docs/configuring-playbook-jitsi.md | 4 ++-- docs/configuring-playbook-ldap-auth.md | 6 ++++-- docs/configuring-playbook-matrix-corporal.md | 2 +- docs/configuring-playbook-matrix-registration.md | 12 +++++------- docs/configuring-playbook-mautrix-bridges.md | 8 ++++---- docs/configuring-playbook-prometheus-nginxlog.md | 2 +- docs/configuring-playbook-rageshake.md | 6 ++++-- ...onfiguring-playbook-synapse-auto-accept-invite.md | 2 +- ...nfiguring-playbook-synapse-s3-storage-provider.md | 2 +- docs/configuring-playbook-telemetry.md | 2 +- docs/configuring-playbook-traefik.md | 4 ++-- docs/configuring-playbook.md | 2 ++ docs/howto-srv-server-delegation.md | 4 ++-- docs/maintenance-and-troubleshooting.md | 6 +----- docs/uninstalling.md | 4 +--- 32 files changed, 60 insertions(+), 60 deletions(-) diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index 38b5b05b1..0c0f7077e 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -4,7 +4,7 @@ Appservice Double Puppet is a homeserver appservice through which bridges (and p This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach. -Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method. +Previously, bridges supported performing double-puppeting with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method. ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index dba51e905..2f93b0245 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -10,8 +10,6 @@ The backup will run based on `backup_borg_schedule` var (systemd timer calendar) By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable. -**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). - ## Prerequisites 1. If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 3863b616b..bce4de3fc 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -36,7 +36,7 @@ If your homeserver's implementation is Synapse, you will need to prevent it from This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. -To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. +To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index e7737420b..d79f085b5 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -32,7 +32,7 @@ If your homeserver's implementation is Synapse, you will need to prevent it from This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. -To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. +To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index 919939423..0b440547f 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -6,7 +6,7 @@ The playbook can install and configure [Heisenbridge](https://github.com/hifi/he See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I). -## Configuration +## Adjusting the playbook configuration To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index e6a9e963e..7f58a74cd 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -4,7 +4,9 @@ The playbook can install and configure [matrix-sms-bridge](https://github.com/be See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you. -**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.** +## Prerequisite + +The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first. ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 8baf793b9..a0d55b62b 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -76,7 +76,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html). +Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 9d3c4be5e..0e16c7eba 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -64,5 +64,3 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account. - -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index f89ca1c42..b925a2bc2 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -4,8 +4,6 @@ The playbook can install and configure [mautrix-signal](https://github.com/mautr See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you. -**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver. - ## Prerequisites (optional) ### Prepare Postgres database on external Postgres server diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index fc775f61c..c48820b38 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -4,7 +4,13 @@ The playbook can install and configure [mautrix-telegram](https://github.com/mau 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. -## Prerequisite (optional) +## Prerequisites + +### Obtain a Telegram API key + +To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps). + +### Enable Appservice Double Puppet or Shared Secret Auth (optional) If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook. @@ -12,7 +18,7 @@ For details about configuring Double Puppeting for this bridge, see the section ## Adjusting the playbook configuration -You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `YOUR_TELEGRAM_APP_ID` and `YOUR_TELEGRAM_API_HASH`. ```yaml matrix_mautrix_telegram_enabled: true diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index dbc4c5ea3..9a057391e 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -58,4 +58,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s). +Follow the [mautrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s). diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index f39c4a867..0016cbdd9 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -1,6 +1,6 @@ # Setting up WeChat bridging (optional) -The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network). +The playbook can install and configure [matrix-wechat](https://github.com/duo/matrix-wechat) for you, for bridging to [WeChat](https://www.wechat.com/). See the project'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. @@ -31,6 +31,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). +To use the bridge, you need to start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Send `help` to the bot to see the available commands. diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index b39387d86..f890b9775 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -14,7 +14,7 @@ The playbook contains 2 roles for configuring different pieces of the Cactus Com You can enable whichever component you need (typically both). -## Configuration +## Adjusting the playbook configuration To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 441872d73..00bde90b4 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -18,7 +18,7 @@ matrix_homeserver_implementation: dendrite The playbook provides lots of customization variables you could use to change Dendrite's settings. -Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template. +Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite.yaml.j2) template. **If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes. @@ -26,7 +26,7 @@ Alternatively, **if there is no pre-defined variable** for a Dendrite setting yo - you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used. -- or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). +- or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). - or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 1c4fd99f9..3fa0ea688 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -38,7 +38,7 @@ Dimension requires an access token to be able to connect to your homeserver. Ref ## Adjusting the playbook configuration -To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). +To enable Dimension, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_dimension_enabled: true @@ -48,7 +48,7 @@ matrix_dimension_access_token: "ACCESS_TOKEN_HERE" ### Define admin users -These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): +To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_dimension_admins: diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 86a1052b2..619dfd2c3 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -8,7 +8,7 @@ See the project's [documentation](https://github.com/devture/email2matrix/blob/m ## Preparation -### DNS configuration +## Adjusting DNS records It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page. diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index 6be892314..3bf9ecc70 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -20,7 +20,7 @@ If you wish to disable federation, you can do that with an empty list (`[]`), or By default, your server's public rooms directory is not exposed to other servers via federation. -If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): +To expose it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_allow_public_rooms_over_federation: true @@ -28,7 +28,7 @@ matrix_synapse_allow_public_rooms_over_federation: true ## Disabling federation -To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): +To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_homeserver_federation_enabled: false @@ -52,7 +52,7 @@ matrix_synapse_reverse_proxy_companion_federation_api_enabled: false Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection. -The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other: +To make it possible to proxy the federation through a CDN such as CloudFlare or any other, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_http_listener_resource_names: ["client","federation"] diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 69b93906b..29ded06b4 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -68,7 +68,7 @@ jitsi_prosody_auth_internal_accounts: password: "another-password" ``` -**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook. +⚠️ **Warning**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook. **If you get an error** like this: "Error: Account creation/modification not supported.", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation). @@ -263,7 +263,7 @@ To enable Gravatar set: jitsi_disable_gravatar: false ``` -**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header). +⚠️ **Warning**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header). ## Installing diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md index 8d11ac577..d3a95d138 100644 --- a/docs/configuring-playbook-ldap-auth.md +++ b/docs/configuring-playbook-ldap-auth.md @@ -29,9 +29,11 @@ If you wish for users to **authenticate only against configured password provide matrix_synapse_password_config_localdb_enabled: false ``` -## Using ma1sd Identity Server for authentication +## Using ma1sd Identity Server for authentication (not recommended) -If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication). +The playbook can instead configure [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for LDAP authentication. However, **we recommend not bothering with installing it** as ma1sd has been unmaintained for years. + +If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication). ## Handling user registration diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index ef9ab2d1b..622d4b59d 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -2,7 +2,7 @@
-**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't. +⚠️ **Warning**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't.
diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 4a1eeeaf5..edc8a1ea1 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -1,14 +1,12 @@ # Setting up matrix-registration (optional) -The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. +⚠️ **Warnings**: +- This is a poorly maintained and buggy project. It's better to avoid using it. +- This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) -**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it. +The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. It is a simple python application to have a token based Matrix registration. -**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - -> matrix-registration is a simple python application to have a token based Matrix registration. - -Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account. +Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows certain people (these having a special link) to register a user account, **keeping your server's registration closed (private)**. **matrix-registration** provides 2 things: diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md index 6b86863bf..ca238790a 100644 --- a/docs/configuring-playbook-mautrix-bridges.md +++ b/docs/configuring-playbook-mautrix-bridges.md @@ -30,7 +30,7 @@ matrix_mautrix_SERVICENAME_configuration_extension_yaml: | '@alice:{{ matrix_domain }}': admin ``` -## encryption +### Encryption Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -48,7 +48,7 @@ matrix_mautrix_SERVICENAME_bridge_encryption_enabled: true matrix_mautrix_SERVICENAME_bridge_encryption_default: true ``` -## relay mode +### Relay mode Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -79,7 +79,7 @@ matrix_mautrix_SERVICENAME_configuration_extension_yaml: | default: true ``` -## Setting the bot's username +### Setting the bot's username ```yaml matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" @@ -87,7 +87,7 @@ matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" Can be used to set the username for the bridge. -## Discovering additional configuration options +### Extending the configuration You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure. diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index ed90cb0aa..1683210c3 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -12,7 +12,7 @@ To make use of this, you need to install [Prometheus](./configuring-playbook-pro If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created. -## Configuration +## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index 88bc3fd61..8847811ef 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -2,7 +2,9 @@ The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you. -This is useful if you're developing your own applications and would like to collect bug reports for them. +See the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) to learn what it does and why it might be useful to you. + +**Note**: most people don't need to install rageshake to collect bug reports. This component is only useful to people who develop/build their own Matrix client applications themselves. ## Adjusting the playbook configuration @@ -64,4 +66,4 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Usage -Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc. +Refer to the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) for available APIs, etc. diff --git a/docs/configuring-playbook-synapse-auto-accept-invite.md b/docs/configuring-playbook-synapse-auto-accept-invite.md index c117346f8..52c1c46ae 100644 --- a/docs/configuring-playbook-synapse-auto-accept-invite.md +++ b/docs/configuring-playbook-synapse-auto-accept-invite.md @@ -8,7 +8,7 @@ See the project's [documentation](https://github.com/matrix-org/synapse-auto-acc **Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module. -## Configuration +## Adjusting the playbook configuration If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index 82af9574d..05b6debb2 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -21,7 +21,7 @@ You can run some scripts to delete the local files once in a while (which we do While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store. -## Installing +## Adjusting the playbook configuration After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): diff --git a/docs/configuring-playbook-telemetry.md b/docs/configuring-playbook-telemetry.md index cb144ee1c..111a27da7 100644 --- a/docs/configuring-playbook-telemetry.md +++ b/docs/configuring-playbook-telemetry.md @@ -4,7 +4,7 @@ By default, this playbook configures your Matrix homeserver to not send any tele The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success. -## Enabling Telemetry +## Adjusting the playbook configuration If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 9032ed1cf..66d6b1aee 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -34,7 +34,7 @@ traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE ``` -**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. +⚠️ **Warning**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. ## Additional configuration @@ -134,7 +134,7 @@ Changing the `url` to one with an `http://` prefix would allow to connect to the With these changes, all TCP traffic will be reverse-proxied to the target system. -**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. +⚠️ **Warning**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. ## Traefik behind a `proxy_protocol` reverse-proxy diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 1b1de3c50..78d664a89 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -26,6 +26,8 @@ For a more custom setup, see the [Other configuration options](#other-configurat ## Other configuration options +**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles. + ### Core service adjustments - Homeserver configuration: diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index f4b028b0b..ba74d38ac 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -14,7 +14,7 @@ This means that this is **limited to the list of DNS providers supported by Trae The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) -## The changes +## Adjusting the playbook configuration **Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels: @@ -91,7 +91,7 @@ By default, Coturn is configured to wait on the certificate for the `matrix.` su We also need to indicate to Coturn where the wildcard certificate is. -**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`). +⚠️ **Warning** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`). This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically. diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 673c89859..0ab46f900 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -22,7 +22,7 @@ To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/j sudo journalctl -fu matrix-synapse ``` -## Increasing Synapse logging +## Increase logging verbosity Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`. @@ -51,7 +51,3 @@ The shortcut command with `just` program is also available: `just run-tags run-d ## Postgres See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page. - -## Ma1sd - -See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page. diff --git a/docs/uninstalling.md b/docs/uninstalling.md index 717037cee..14c8c211f 100644 --- a/docs/uninstalling.md +++ b/docs/uninstalling.md @@ -1,9 +1,7 @@ # Uninstalling -**Warnings**: - +⚠️ **Warnings**: - If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating. - - If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**. ----------------- From f8b779f8ed36426eeb3db2e27aa6826d7e65f506 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 5 Jan 2025 09:47:57 +0200 Subject: [PATCH 173/952] Add `trace` as a valid logging level option for mautrix bridges bridgev2 mautrix bridges use https://github.com/tulir/zeroconfig for logging, which does support `trace` as a logging level. --- roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml | 2 +- roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml | 2 +- roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml | 2 +- roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml | 2 +- roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml | 2 +- roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index f362a702a..779816b68 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -118,7 +118,7 @@ matrix_mautrix_discord_appservice_bot_avatar: mxc://maunium.net/nIdEykemnwdisvHb matrix_mautrix_discord_provisioning_shared_secret: disable # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_discord_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml index 963894475..2cde7487f 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml @@ -86,7 +86,7 @@ matrix_mautrix_gmessages_homeserver_token: '' matrix_mautrix_gmessages_appservice_bot_username: gmessagesbot # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_gmessages_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index 752620008..026b39d2e 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -93,7 +93,7 @@ matrix_mautrix_signal_homeserver_token: '' matrix_mautrix_signal_appservice_bot_username: signalbot # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_signal_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml index 642d1ff7a..9b95d069f 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml @@ -62,7 +62,7 @@ matrix_mautrix_slack_backfill_unread_hours_threshold: 720 matrix_mautrix_slack_backfill_threads_max_initial_messages: 50 # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_slack_logging_level: 'warn' # Database-related configuration fields. diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml index 6c7949f8a..ba13e14cb 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml @@ -130,7 +130,7 @@ matrix_mautrix_twitter_backfill_max_catchup_messages: 500 matrix_mautrix_twitter_provisioning_shared_secret: disable # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_twitter_logging_level: 'warn' # Whether or not metrics endpoint should be enabled. diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml index a4309afc0..2d2519338 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml @@ -82,7 +82,7 @@ matrix_mautrix_whatsapp_homeserver_token: '' matrix_mautrix_whatsapp_appservice_bot_username: whatsappbot # Minimum severity of journal log messages. -# Options: debug, info, warn, error, fatal +# Options: trace, debug, info, warn, error, fatal matrix_mautrix_whatsapp_logging_level: 'warn' # Whether or not created rooms should have federation enabled. From 4b2e066a6159d8a368cfbab3d46e91dca3549bb4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 5 Jan 2025 03:55:51 -0500 Subject: [PATCH 174/952] Update docs/configuring-playbook-mautrix-bridges.md (#3913) * Update docs/configuring-playbook-mautrix-bridges.md: edit the section "extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-mautrix-bridges.md: edit section headers Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-mautrix-bridges.md: edit the section "Control the logging level" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-mautrix-bridges.md: replace examples for service name - Remove hangout, which has been shut down and whose role is soon to be removed from the playbook - Add a note about the Mautrix Meta bridge Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-mautrix-bridges.md: add descriptions to each section Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-mautrix-bridges.md: move the section "Set up Double Puppeting" to "Usage" Signed-off-by: Suguru Hirahara * Rename docs/configuring-playbook-mautrix-bridges.md to docs/configuring-playbook-bridge-mautrix-bridges.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: edit an instruction Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add the manual step for setting up Double Puppetting Based on other documents for mautrix bridges like docs/configuring-playbook-bridge-mautrix-discord.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add a note about bridges' incompatibility with Appservice Double Puppet Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: adopt the description on docs/configuring-playbook-appservice-double-puppet.md Make it clear that Double Puppetting with the other methods than the appservice one has been superseded. See: https://docs.mau.fi/bridges/general/double-puppeting.html#automatically Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add "recommended" label to the first method of setting up Double Puppeting Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add anchor links to the official documentation Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add descriptions about configuring bridge permissions Partially based on docs/configuring-playbook-bridge-mautrix-meta-instagram.md etc. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add description about the relaybot Based on: - the official documentation: https://docs.mau.fi/bridges/general/relay-mode.html - docs/configuring-playbook-bridge-mautrix-whatsapp.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: remove a duplicated anchor link Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook.md: add an anchor link to configuring-playbook-bridge-mautrix-bridges.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: edit a sentence Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: reflect the review See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3913#discussion_r1903215741 Co-authored-by: Slavi Pantaleev Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- ...iguring-playbook-bridge-mautrix-bridges.md | 203 ++++++++++++++++++ docs/configuring-playbook-mautrix-bridges.md | 145 ------------- docs/configuring-playbook.md | 2 + 3 files changed, 205 insertions(+), 145 deletions(-) create mode 100644 docs/configuring-playbook-bridge-mautrix-bridges.md delete mode 100644 docs/configuring-playbook-mautrix-bridges.md diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md new file mode 100644 index 000000000..24576ab94 --- /dev/null +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -0,0 +1,203 @@ +# Setting up a Generic Mautrix Bridge (optional) + +The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges. + +You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository. + +## Adjusting the playbook configuration + +To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +# Replace SERVICENAME with one of: twitter, discord, signal, googlechat, etc. +matrix_mautrix_SERVICENAME_enabled: true +``` + +**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). + +There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges. + +### Configure bridge permissions (optional) + +By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings. + +Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_admin: "@alice:{{ matrix_domain }}" +``` + +**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with: + +```yaml +matrix_mautrix_SERVICENAME_configuration_extension_yaml: | + bridge: + permissions: + '@alice:{{ matrix_domain }}': admin +``` + +This will add the admin permission to the specific user, while keeping the default permissions. + +You could also redefine the default permissions settings completely, rather than adding extra permissions. You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` to find information on the permission settings and other options you would like to configure. + +### Enable encryption (optional) + +[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +**for all bridges with encryption support**: + +```yaml +matrix_bridges_encryption_enabled: true +matrix_bridges_encryption_default: true +``` + +**Alternatively**, for a specific bridge: + +```yaml +matrix_mautrix_SERVICENAME_bridge_encryption_enabled: true +matrix_mautrix_SERVICENAME_bridge_encryption_default: true +``` + +### Enable relay mode (optional) + +[Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode. + +If you would like to enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +**for all bridges with relay mode support**: + +```yaml +matrix_bridges_relay_enabled: true +``` + +**Alternatively**, for a specific bridge: + +```yaml +matrix_mautrix_SERVICENAME_configuration_extension_yaml: | + bridge: + relay: + enabled: true +``` + +You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this: + +```yaml +matrix_mautrix_SERVICENAME_configuration_extension_yaml: | + bridge: + permissions: + '@alice:{{ matrix_domain }}': admin + encryption: + allow: true + default: true +``` + +If you want to activate the relaybot in a room, send `!prefix set-relay` in the rooms where you want to use the bot (replace `!prefix` with the appropriate command prefix for the bridge, like `!signal` or `!wa`). To deactivate, send `!prefix unset-relay`. + +Use `!prefix set-pl 100` to be able for the bot to modify room settings and invite others. + +#### Allow anyone on the homeserver to become a relay user (optional) + +By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_mautrix_SERVICENAME_bridge_relay_admin_only: false +``` + +### Set the bot's username (optional) + +To set the bot's username, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" +``` + +### Configure the logging level (optional) + +To specify the logging level, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_mautrix_SERVICENAME_logging_level: warn +``` + +Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`. + +If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful. + +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +Take a look at: + +- `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_SERVICENAME_configuration_extension_yaml` variable + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + +## Usage + +To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). + +Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html + +If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. + +### Set up Double Puppeting (optional) + +After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). + +To set it up, you have 2 ways of going about it. + +#### Method 1: automatically, by enabling Appservice Double Puppet (recommended) + +To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html), you could enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook. + +Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver. + +To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_appservice_double_puppet_enabled: true +``` + +When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method. + +This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. + +**Notes**: + +- Previously there were multiple different automatic double puppeting methods like one with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but they have been superseded by this Appservice Double Puppet method. Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future as the older methods were completely removed in the megabridge rewrites on [the upstream project](https://docs.mau.fi/bridges/general/double-puppeting.html#automatically). + + +- Some bridges like [the deprecated Facebook mautrix bridge](configuring-playbook-bridge-mautrix-facebook.md) and [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md), which is partially based on the Facebook bridge, are compatible with the Shared Secret Auth service only. These bridges automatically perform Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. + +#### Method 2: manually, by asking each user to provide a working access token + +When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: + +- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). + +- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` + +- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature + +## Troubleshooting + +For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge. + +Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us. diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md deleted file mode 100644 index ca238790a..000000000 --- a/docs/configuring-playbook-mautrix-bridges.md +++ /dev/null @@ -1,145 +0,0 @@ -# Setting up a Generic Mautrix Bridge (optional) - -The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges. - -You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository. - -## Adjusting the playbook configuration - -To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -# Replace SERVICENAME with one of: twitter, facebook, instagram, .. -matrix_mautrix_SERVICENAME_enabled: true -``` - -There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges. - -To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -matrix_admin: "@alice:{{ matrix_domain }}" -``` - -**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with: - -```yaml -matrix_mautrix_SERVICENAME_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` - -### Encryption - -Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -**for all bridges with encryption support**: - -```yaml -matrix_bridges_encryption_enabled: true -matrix_bridges_encryption_default: true -``` - -**Alternatively**, for a specific bridge: - -```yaml -matrix_mautrix_SERVICENAME_bridge_encryption_enabled: true -matrix_mautrix_SERVICENAME_bridge_encryption_default: true -``` - -### Relay mode - -Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -**for all bridges with relay mode support**: - -```yaml -matrix_bridges_relay_enabled: true -``` - -**Alternatively**, for a specific bridge: - -```yaml -matrix_mautrix_SERVICENAME_configuration_extension_yaml: | - bridge: - relay: - enabled: true -``` - -You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this: - -```yaml -matrix_mautrix_SERVICENAME_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin - encryption: - allow: true - default: true -``` - -### Setting the bot's username - -```yaml -matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" -``` - -Can be used to set the username for the bridge. - -### Extending the configuration - -You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure. - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start -``` - -**Notes**: - -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - -- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - - `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - -## Set up Double Puppeting - -To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook. - -The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding - -```yaml -matrix_appservice_double_puppet_enabled: true -``` - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -## Controlling the logging level - -```yaml -matrix_mautrix_SERVICENAME_logging_level: WARN -``` - -to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL. - -If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful. - -## Usage - -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). - -Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html - -If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. - -## Troubleshooting - -For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge. - -Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 78d664a89..1603da378 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -109,6 +109,8 @@ Use alternative file storage to the default `media_store` folder. Bridges can be used to connect your Matrix installation with third-party communication networks. +- [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) - a common guide for configuring mautrix bridges + - [Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md) - [Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md) From ace294b29da2809b332bd52d701f3e8200abff53 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 5 Jan 2025 16:46:22 +0000 Subject: [PATCH 175/952] Update dependency Pygments to v2.19.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 2120fe628..67d3033ab 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -14,7 +14,7 @@ mdit-py-plugins==0.4.2 mdurl==0.1.2 myst-parser==4.0.0 packaging==24.2 -Pygments==2.18.0 +Pygments==2.19.0 PyYAML==6.0.2 requests==2.32.3 setuptools==75.6.0 From 9fa47478cbd45275a28139a6fa6da1e22cc9efb3 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 5 Jan 2025 16:46:27 +0000 Subject: [PATCH 176/952] Update dependency setuptools to v75.7.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 2120fe628..037260446 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.18.0 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.6.0 +setuptools==75.7.0 snowballstemmer==2.2.0 Sphinx==8.1.3 sphinx-intl==2.3.1 From f2585fa171f17fd13c4b3e4ccc6fa67863a62891 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 6 Jan 2025 09:09:46 +0200 Subject: [PATCH 177/952] Adjust matrix-synapse-s3-storage-provider-migrate.{service,timer} permissions Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3917 --- .../tasks/ext/s3-storage-provider/setup_install.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml index 384f16815..ede73ec9a 100644 --- a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml @@ -43,7 +43,7 @@ ansible.builtin.template: src: "{{ role_path }}/templates/synapse/ext/s3-storage-provider/systemd/{{ item }}.j2" dest: "{{ devture_systemd_docker_base_systemd_path }}/{{ item }}" - mode: 0640 + mode: 0644 with_items: - matrix-synapse-s3-storage-provider-migrate.service - matrix-synapse-s3-storage-provider-migrate.timer From bf1ff8039807c2659bd8c0489ab31940d436b25a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 6 Jan 2025 17:42:19 +0000 Subject: [PATCH 178/952] Update dependency Pygments to v2.19.1 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index c1a311967..78bfb83f7 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -14,7 +14,7 @@ mdit-py-plugins==0.4.2 mdurl==0.1.2 myst-parser==4.0.0 packaging==24.2 -Pygments==2.19.0 +Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 setuptools==75.7.0 From ff8373c616fa2040b5c316305d6ad60ccdebd36f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 8 Jan 2025 11:48:38 +0900 Subject: [PATCH 179/952] Update .github/workflows/close-stale-issues.yml: increase operations-per-run from 100 to 500 Apparently checking issues or PRs which have been labelled with "stale" consumes more operations than checking ones without labelled, and the current amount (100) is not enough. See an example: https://github.com/spantaleev/matrix-docker-ansible-deploy/actions/runs/12566424393/job/35031806537#step:2:4083 Since the total amount of GitHub API rate is 5000, reserving 10 per cent for this action should not be an issue for now. Let's increase again if it is still too low. Signed-off-by: Suguru Hirahara --- .github/workflows/close-stale-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 3a799821b..4473c589e 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -21,7 +21,7 @@ jobs: # Issues/PRs ###################################################################### exempt-assignees: 'spantaleev,aine-etke' - operations-per-run: 100 + operations-per-run: 500 # Use this to do a dry run from a pull request # debug-only: true ###################################################################### From a381143b8fa7f134cc3e867e10ae797e833c41a5 Mon Sep 17 00:00:00 2001 From: Aine Date: Wed, 8 Jan 2025 09:41:21 +0200 Subject: [PATCH 180/952] borgmatic v1.9.5 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index b85c5b407..d4ec4695a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.4-0 + version: v1.4.0-1.9.5-0 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From eac00dbc696c94a9fd23b93b7b5fb8471863b3bf Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 8 Jan 2025 19:11:45 +0000 Subject: [PATCH 181/952] Update dependency setuptools to v75.8.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 78bfb83f7..74c9c078e 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.7.0 +setuptools==75.8.0 snowballstemmer==2.2.0 Sphinx==8.1.3 sphinx-intl==2.3.1 From 3a2b90dacd609f8170569331a49956d1e5a13df8 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 9 Jan 2025 06:56:32 +0000 Subject: [PATCH 182/952] Update dependency docker to v7.4.4 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index d4ec4695a..1fea09d2e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -10,7 +10,7 @@ version: v0.2.0-0 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker - version: 7.4.3 + version: 7.4.4 name: docker - src: git+https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python.git version: 129c8590e106b83e6f4c259649a613c6279e937a From 5cf99af0ba77eaad4c86721cb48927e703f1f29d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 9 Jan 2025 16:28:29 +0900 Subject: [PATCH 183/952] Use common descriptions for mautrix bridges to improve consistency (#3914) * Update docs for mautrix bridges: common section for extending the configuration Add links to the common guide for configuring mautrix bridges Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: add the sections 'extending the configuration' Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: add the common section "extending the configuration" based on docs for mautrix bridges Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: edit the top section Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: common section for setting up Double Puppeting Based on docs/configuring-playbook-bridge-mautrix-meta-instagram.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: common section for setting up Double Puppetting Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: replace duplicated descriptions for setting up Double Puppeting with a link to docs/configuring-playbook-bridge-mautrix-bridges.md Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: remove the section for setting up Double Puppeting The instruction has been described already in the section for prerequisites Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: add sections for enabling double puppeting Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: adopt common descriptions about bridge permissions Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-whatsapp.md: remove description for relay-bot For WhatsApp the default relay mode is used and the description for it is available on the common guide for configuring mautrix bridges. Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: remove descriptions about permissions in favor of the common one on docs/configuring-playbook-bridge-mautrix-bridges.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: remove a redundant instruction for referring to the section for troubleshooting The section is just below the instruction. Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: add notes about double puppeting with the Shared Secret Auth Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: remove redundant descriptions Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: remove links to the description about the relay mode from configuring-playbook-bridge-mautrix-bridges.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-telegram.md: move the section for instruction about using the bridge for direct chat only Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add configuration for relay to an example of matrix_mautrix_SERVICENAME_configuration_extension_yaml Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: add a header for the reference to the common guide Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: adopt the common description for the section "Usage" Fix docs/configuring-playbook-bridge-mautrix-bridges.md: simplify the instruction to refer each documentation page (note that there are two formats of the links: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html and https://docs.mau.fi/bridges/go/SERVICENAME/authentication.html) Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: edit anchor links to official documentation pages - Add links to the official documentation pages - Remove links to Hangouts' documentation page: the links have been replaced with ones to Google Chat bridge and the resources about Hangouts bridge have been removed - Replace links to documentation pages in python version with ones in go version Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: add a note about variable names Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-beeper-linkedin.md: re-add the section for instruction about appservice double puppeting Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...ng-playbook-bridge-appservice-kakaotalk.md | 34 ++------- ...ing-playbook-bridge-appservice-webhooks.md | 2 +- ...iguring-playbook-bridge-beeper-linkedin.md | 46 +++++-------- ...iguring-playbook-bridge-mautrix-bridges.md | 6 +- ...iguring-playbook-bridge-mautrix-discord.md | 42 ++++------- ...guring-playbook-bridge-mautrix-facebook.md | 69 ++++--------------- ...uring-playbook-bridge-mautrix-gmessages.md | 35 ++++------ ...ring-playbook-bridge-mautrix-googlechat.md | 41 ++++------- ...guring-playbook-bridge-mautrix-hangouts.md | 42 ++++------- ...uring-playbook-bridge-mautrix-instagram.md | 34 ++------- ...-playbook-bridge-mautrix-meta-instagram.md | 60 +++------------- ...-playbook-bridge-mautrix-meta-messenger.md | 62 +++-------------- ...figuring-playbook-bridge-mautrix-signal.md | 69 +++---------------- ...nfiguring-playbook-bridge-mautrix-slack.md | 38 +++------- ...guring-playbook-bridge-mautrix-telegram.md | 65 ++++++++--------- ...iguring-playbook-bridge-mautrix-twitter.md | 38 ++++------ ...guring-playbook-bridge-mautrix-whatsapp.md | 46 +++---------- ...iguring-playbook-bridge-mautrix-wsproxy.md | 8 +++ 18 files changed, 199 insertions(+), 538 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index e10f880a8..448a84e58 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -8,9 +8,13 @@ See the project's [documentation](https://src.miscworks.net/fair/matrix-appservi ## Prerequisite (optional) +### Enable Shared Secret Auth + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -20,9 +24,7 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_appservice_kakaotalk_enabled: true ``` -You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation. - -### Additional configuration +### Extending the configuration There are some additional things you may wish to configure about the bridge. @@ -52,26 +54,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password. - -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature +You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password. diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index 1746fb80f..e4d212f46 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -48,7 +48,7 @@ To use the bridge, you need to invite the bridge bot user to your room in either - Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room) - Add the bridge bot to a private channel (personal channels imply you being an administrator) -You then need to send a message to the bridge bot in order to receive a private message including the webhook link: +You then need to send a message to the bridge bot to receive a private message including the webhook link: ``` !webhook diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 8fea2ec93..979c188c1 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -1,9 +1,19 @@ # Setting up Beeper Linkedin bridging (optional) -The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges +The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the mautrix bridges. See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you. +## Prerequisite + +### Enable Appservice Double Puppet or Shared Secret Auth (optional) + +If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. + ## Adjusting the playbook configuration To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -12,25 +22,13 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_beeper_linkedin_enabled: true ``` -There are some additional things you may wish to configure about the bridge before you continue. +### Extending the configuration -Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: +There are some additional things you may wish to configure about the bridge. -```yaml -matrix_beeper_linkedin_bridge_encryption_allow: true -matrix_beeper_linkedin_bridge_encryption_default: true -``` +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#setting-the-bot-s-username-optional), etc. -If you would like to be able to administrate the bridge from your account it can be configured like this: - -```yaml -matrix_beeper_linkedin_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` - -You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure. +**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_beeper_linkedin_`. ## Installing @@ -49,23 +47,11 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. -## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - ## Usage 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). -Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account. - -If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. - -After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so. +You then need to send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account. ## Troubleshooting diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index 24576ab94..6fa4e0a68 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -27,6 +27,8 @@ Different levels of permission can be granted to users. For example, to **config matrix_admin: "@alice:{{ matrix_domain }}" ``` +If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default. + **Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with: ```yaml @@ -84,6 +86,8 @@ You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` ```yaml matrix_mautrix_SERVICENAME_configuration_extension_yaml: | bridge: + relay: + enabled: true permissions: '@alice:{{ matrix_domain }}': admin encryption: @@ -153,7 +157,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). -Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html +For details about the next steps, refer to each bridge's individual documentation page. If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index df93b246c..9db84cd82 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -1,5 +1,7 @@ # Setting up Mautrix Discord bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook. - For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing. - 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. @@ -18,7 +20,9 @@ If this is a dealbreaker for you, consider using one of the other Discord bridge 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -28,16 +32,12 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_discord_enabled: true ``` -You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation. - -### Additional configuration +### Extending the configuration There are some additional things you may wish to configure about the bridge. -Take a look at: - -- `roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file -- `roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_discord_configuration_extension_yaml` variable + +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#setting-the-bot-s-username-optional), etc. ## Installing @@ -60,6 +60,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ### Logging in +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html). + #### Method 1: Login using QR code (recommended) For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone. @@ -83,26 +85,6 @@ To acquire the token, open Discord in a private browser window. Then open the de - for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire` 8. You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function. -### 💡 Set up Double Puppeting +### Relaying -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature +The bridge supports using Discord's webhook feature to relay messages from Matrix users who haven't logged into the bridge. See [the official documentation](https://docs.mau.fi/bridges/go/discord/relay.html#setup) for setting up webhook relaying. diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index a0d55b62b..09124f8b7 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -1,16 +1,22 @@ # Setting up Mautrix Facebook bridging (optional, deprecated) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + **Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one. The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you. -See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you. +See the project's [documentation](https://github.com/mautrix/facebook/blob/master/README.md) to learn what it does and why it might be useful to you. ## Prerequisite (optional) +### Enable Shared Secret Auth + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -20,40 +26,11 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_facebook_enabled: true ``` -There are some additional things you may wish to configure about the bridge before you continue. +### Extending the configuration -Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: +There are some additional things you may wish to configure about the bridge. -```yaml -matrix_mautrix_facebook_configuration_extension_yaml: | - bridge: - encryption: - allow: true - default: true -``` - -If you would like to be able to administrate the bridge from your account it can be configured like this: - -```yaml -matrix_mautrix_facebook_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` - -Using both would look like - -```yaml -matrix_mautrix_facebook_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin - encryption: - allow: true - default: true -``` - -You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -76,32 +53,10 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. +You then need to send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature - ## Troubleshooting ### Facebook rejecting login attempts and forcing you to change password diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index 40305e06b..5339e67ef 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -1,14 +1,18 @@ # Setting up Mautrix Google Messages bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/). See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you. ## Prerequisite (optional) +### Enable Appservice Double Puppet + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -18,6 +22,13 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_gmessages_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + + +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#setting-the-bot-s-username-optional), etc. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -39,24 +50,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 2b077dfcf..4b179c139 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -1,14 +1,20 @@ # Setting up Mautrix Google Chat bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you. See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you. ## Prerequisite (optional) +### Enable Appservice Double Puppet or Shared Secret Auth + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -18,6 +24,13 @@ To enable the [Google Chat](https://chat.google.com/) bridge, add the following matrix_mautrix_googlechat_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + + +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#setting-the-bot-s-username-optional), etc. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -39,34 +52,10 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions. +You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions. Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools. Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages. You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html). - -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index e2a808ec3..8936217cd 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -1,16 +1,20 @@ # Setting up Mautrix Hangouts bridging (optional, deprecated) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + 💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes. The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you. -See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you. - ## Prerequisite (optional) +### Enable Shared Secret Auth + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -20,6 +24,12 @@ To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the fo matrix_mautrix_hangouts_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -41,32 +51,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions. +You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions. Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools. Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages. - -You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html). - -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 0e16c7eba..deef0c346 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -1,10 +1,12 @@ # Setting up Mautrix Instagram bridging (optional, deprecated) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + **Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one. The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you. -See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you. +See the project's [documentation](https://github.com/mautrix/instagram/blob/master/README.md) to learn what it does and why it might be useful to you. ## Adjusting the playbook configuration @@ -14,33 +16,11 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_instagram_enabled: true ``` -There are some additional things you may wish to configure about the bridge before you continue. +### Extending the configuration -Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file: +There are some additional things you may wish to configure about the bridge. -```yaml -matrix_mautrix_instagram_configuration_extension_yaml: | - bridge: - encryption: - allow: true - default: true -``` - -If you would like to be able to administrate the bridge from your account it can be configured like this: - -```yaml -# The easy way. The specified Matrix user ID will be made an admin of all bridges -matrix_admin: "@alice:{{ matrix_domain }}" - -# OR: -# The more verbose way. Applies to this bridge only. You may define multiple Matrix users as admins. -matrix_mautrix_instagram_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` - -You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -63,4 +43,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account. +You then need to send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account. diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index 6514cac90..b95fcfff2 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -1,7 +1,11 @@ # Setting up Instagram bridging via Mautrix Meta (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you. +See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you. + Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`). This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md). @@ -23,7 +27,7 @@ Then, consider disabling the old bridge in your configuration, so it won't recre 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -35,37 +39,11 @@ matrix_mautrix_meta_instagram_enabled: true Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below. -### Bridge permissions +### Extending the configuration -By default, any user on your homeserver will be able to use the bridge. +There are some additional things you may wish to configure about the bridge. -Different levels of permission can be granted to users: - -- `relay` - Allowed to be relayed through the bridge, no access to commands -- `user` - Use the bridge with puppeting -- `admin` - Use and administer the bridge - -The permissions are following the sequence: nothing < `relay` < `user` < `admin`. - -The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this: - -```yaml -matrix_mautrix_meta_instagram_bridge_permissions_default: - '*': relay - example.com: user - '{{ matrix_admin }}': admin -``` - -If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default. - -You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this: - -```yaml -matrix_mautrix_meta_instagram_bridge_permissions_custom: - '@alice:{{ matrix_domain }}': admin -``` - -You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -88,24 +66,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 9e40720bb..1890e6c27 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -1,7 +1,11 @@ # Setting up Messenger bridging via Mautrix Meta (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you. +See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you. + Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`). This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md). @@ -22,7 +26,7 @@ Then, consider disabling the old bridge in your configuration, so it won't recre 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -48,37 +52,11 @@ You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variab Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.). -### Bridge permissions +### Extending the configuration -By default, any user on your homeserver will be able to use the bridge. +There are some additional things you may wish to configure about the bridge. -Different levels of permission can be granted to users: - -- `relay` - Allowed to be relayed through the bridge, no access to commands -- `user` - Use the bridge with puppeting -- `admin` - Use and administer the bridge - -The permissions are following the sequence: nothing < `relay` < `user` < `admin`. - -The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this: - -```yaml -matrix_mautrix_meta_messenger_bridge_permissions_default: - '*': relay - example.com: user - '{{ matrix_admin }}': admin -``` - -If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default. - -You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this: - -```yaml -matrix_mautrix_meta_messenger_bridge_permissions_custom: - '@alice:{{ matrix_domain }}': admin -``` - -You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -101,28 +79,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`. -You then need to send a `login` command and follow the bridge bot's instructions. +You then need to send `login` to the bridge bot and follow the instructions. Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html). -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index b925a2bc2..575646806 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -1,8 +1,10 @@ # Setting up Mautrix Signal bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you. -See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you. +See the project's [documentation](https://docs.mau.fi/bridges/go/signal/index.html) to learn what it does and why it might be useful to you. ## Prerequisites (optional) @@ -16,7 +18,7 @@ However, if you're [using an external Postgres server](configuring-playbook-exte 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -26,46 +28,11 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_signal_enabled: true ``` -There are some additional things you may wish to configure about the bridge before you continue. +### Extending the configuration -By default, any user on your homeserver will be able to use the bridge. +There are some additional things you may wish to configure about the bridge. -Different levels of permission can be granted to users: - -* relay - Allowed to be relayed through the bridge, no access to commands; -* user - Use the bridge with puppeting; -* admin - Use and administer the bridge. - -The permissions are following the sequence: nothing < relay < user < admin. - -The default permissions are set as follows: - -```yaml -permissions: - '*': relay - example.com: user -``` - -If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file: - -```yaml -matrix_mautrix_signal_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` - -This will add the admin permission to the specific user, while keeping the default permissions. - -In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file: - -```yaml -matrix_mautrix_signal_bridge_permissions: - '@alice:{{ matrix_domain }}': admin - '@bob:{{ matrix_domain }}' : user -``` - -You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -88,24 +55,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index dd2ee5342..759020e56 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -1,5 +1,7 @@ # Setting up Mautrix Slack bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + **Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook. - For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued. - For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook. @@ -20,7 +22,7 @@ Note that neither of these methods are officially supported by Slack. [matrix-ap 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -30,16 +32,12 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_slack_enabled: true ``` -You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation. +### Extending the configuration -### Additional configuration +There are some additional things you may wish to configure about the bridge. -There are some additional options you may wish to configure with the bridge. - -Take a look at: - -- `roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file -- `roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_mautrix_slack_configuration_extension_yaml` variable + +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#setting-the-bot-s-username-optional), etc. ## Installing @@ -66,24 +64,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 4. Now that you're logged in, you can send `help` to the bot to see the available commands. 5. Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication. -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index c48820b38..20500db2e 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -1,5 +1,7 @@ # Setting up Mautrix Telegram bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you. See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you. @@ -14,7 +16,13 @@ To use the bridge, you'd need to obtain an API key from [https://my.telegram.org 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Notes**: + +- Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. + +- If you decided to enable Double Puppeting manually, send `login-matrix` to the bot in order to receive an instruction about how to send an access token to it. ## Adjusting the playbook configuration @@ -26,26 +34,7 @@ matrix_mautrix_telegram_api_id: YOUR_TELEGRAM_APP_ID matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH ``` -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start -``` - -**Notes**: - -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - -- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - - `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - -## Usage - -To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). +### Relaying If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -68,34 +57,40 @@ matrix_mautrix_telegram_configuration_extension_yaml: | More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410 -If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration: +### Use the bridge for direct chat only + +If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_mautrix_telegram_filter_mode: whitelist ``` -### 💡 Set up Double Puppeting +### Extending the configuration -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). +There are some additional things you may wish to configure about the bridge. -To set it up, you have 2 ways of going about it. + +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#setting-the-bot-s-username-optional), etc. -#### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth +## Installing -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: -Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` -Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. +**Notes**: -#### Method 2: manually, by asking each user to provide a working access token +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. -**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging. +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). +## Usage -- send `login-matrix` to the bot and follow instructions about how to send the access token to it +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). -- make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index 81813d2d1..cf2a85f75 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -1,5 +1,7 @@ # Setting up Mautrix Twitter bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + **Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook. The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you. @@ -12,7 +14,7 @@ See the project's [documentation](https://github.com/mautrix/twitter/blob/master 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. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. ## Adjusting the playbook configuration @@ -22,6 +24,13 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_twitter_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + + +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#setting-the-bot-s-username-optional), etc. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -41,29 +50,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -1. You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -2. Send login-cookie to start the login. The bot should respond with instructions on how to proceed. +To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html). +You then need to send login-cookie to start the login. The bot should respond with instructions on how to proceed. -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. - -This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index 2fa6e9914..257d53eae 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -1,14 +1,20 @@ # Setting up Mautrix Whatsapp bridging (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you. See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you. ## Prerequisite (optional) +### Enable Appservice Double Puppet or Shared Secret Auth + If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook. -For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting) +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. ## Adjusting the playbook configuration @@ -20,19 +26,11 @@ matrix_mautrix_whatsapp_enabled: true Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks. -The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file: +### Extending the configuration -```yaml -matrix_mautrix_whatsapp_bridge_relay_enabled: true -``` +There are some additional things you may wish to configure about the bridge. -By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file: - -```yaml -matrix_mautrix_whatsapp_bridge_relay_admin_only: false -``` - -If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. ## Installing @@ -55,26 +53,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). -### 💡 Set up Double Puppeting - -After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do). - -To set it up, you have 2 ways of going about it. - -#### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth - -The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook. - -Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. - -Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future. - -#### Method 2: manually, by asking each user to provide a working access token - -When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps: - -- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md). - -- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE` - -- make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature +You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html). diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index 9a057391e..02aa66fa6 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -1,5 +1,7 @@ # Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional) +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you. See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you. @@ -20,6 +22,12 @@ matrix_mautrix_wsproxy_syncproxy_shared_secret: 'secret token from bridge' Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device. +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. + ### Adjusting the wsproxy URL By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). From 638f53a889472935f43a95db8a970723a8d8ace9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 10 Jan 2025 16:36:27 +0900 Subject: [PATCH 184/952] Update docs for mautrix bridges (follow-up) (#3924) * Update docs/configuring-playbook-bridge-mautrix-telegram.md - Add a link to the official documentation on authentication - Create subsections in the section "Usage" - Update the usage based on https://github.com/mautrix/docs/blob/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/python/telegram/authentication.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-twitter.md - Remove a duplicated "optional" label - Replace the instruction with a link to the official documentation on authentication Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-appservice-kakaotalk.md - Adopt a common introduction - Move the warning message down Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-discord.md As our instruction on usage has been outdated compared to the latest one (cf. https://github.com/mautrix/docs/blob/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/go/discord/authentication.md), let alone confusing in the first place as our instruction on logging in and bridging have been mixed, this commit updates our instruction based on the latest official one. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-gmessages.md: add a link to the official documentation on authentication Based on https://github.com/mautrix/docs/blob/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/go/gmessages/authentication.md Signed-off-by: Suguru Hirahara * Update docs for mautrix-meta bridges: add links to the official documentation on authentication Based on https://github.com/mautrix/docs/blob/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/go/meta/authentication.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-signal.md: add a link to the official documentation on authentication Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-slack.md Based on https://github.com/mautrix/docs/blame/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/go/slack/authentication.md The instruction has been obsolete since https://github.com/mautrix/docs/commit/25b4006035d2cff7a8abcbc2ba1d8c1a10937674 Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-googlechat.md Based on https://github.com/mautrix/docs/blob/d33701428d36f9a4867cbd3199e525c5455e8d44/bridges/python/googlechat/authentication.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add information about troubleshooting Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: add descriptions for each mautrix bridge about the bridges behavior after logging in Based on https://github.com/mautrix/docs/tree/d33701428d36f9a4867cbd3199e525c5455e8d44 Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: add instruction for sending "help" to the bot to the common guide Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-hangouts.md: adopt a common description about usage Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-whatsapp.md - Update the note about linked devices that they will be logged out if the phone is not used over two weeks: the note has been obsolete since https://github.com/mautrix/docs/commit/0860109d05defdb952eaf872a6c24b30aef5a76d - Adopt a common description about usage Signed-off-by: Suguru Hirahara * Update docs for mautrix bridges: fix the internal anchor link Regression by 4b2e066a6159d8a368cfbab3d46e91dca3549bb4 Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-mautrix-bridges.md: add a note about the official docs Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bridge-go-skype-bridge.md: adopt the common description As the bridge was created based on mautrix-whatsapp, this commit adopts the common descriptions for mautrix bridges and ones based on them such as matrix-appservice-kakaotalk and beeper-linkedin Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...ng-playbook-bridge-appservice-kakaotalk.md | 6 ++-- ...iguring-playbook-bridge-beeper-linkedin.md | 2 +- ...iguring-playbook-bridge-go-skype-bridge.md | 26 ++++++++++++--- ...iguring-playbook-bridge-mautrix-bridges.md | 8 ++++- ...iguring-playbook-bridge-mautrix-discord.md | 33 +++++-------------- ...guring-playbook-bridge-mautrix-facebook.md | 2 +- ...uring-playbook-bridge-mautrix-gmessages.md | 6 ++-- ...ring-playbook-bridge-mautrix-googlechat.md | 12 +++---- ...guring-playbook-bridge-mautrix-hangouts.md | 4 +-- ...uring-playbook-bridge-mautrix-instagram.md | 2 +- ...-playbook-bridge-mautrix-meta-instagram.md | 6 ++-- ...-playbook-bridge-mautrix-meta-messenger.md | 8 ++--- ...figuring-playbook-bridge-mautrix-signal.md | 8 +++-- ...nfiguring-playbook-bridge-mautrix-slack.md | 12 +++---- ...guring-playbook-bridge-mautrix-telegram.md | 19 +++++------ ...iguring-playbook-bridge-mautrix-twitter.md | 8 ++--- ...guring-playbook-bridge-mautrix-whatsapp.md | 10 +++--- ...iguring-playbook-bridge-mautrix-wsproxy.md | 2 +- 18 files changed, 91 insertions(+), 83 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 448a84e58..af0955273 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -1,11 +1,11 @@ # Setting up Appservice Kakaotalk bridging (optional) -The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. - -⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**. +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. 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. +⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**. + ## Prerequisite (optional) ### Enable Shared Secret Auth diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 979c188c1..73059ce64 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -26,7 +26,7 @@ matrix_beeper_linkedin_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. **Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_beeper_linkedin_`. diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index 1b84e694f..62d1eb77b 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -1,17 +1,35 @@ # Setting up Go Skype Bridge bridging (optional) -The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you. +The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you, for bridging to [Skype](https://www.skype.com/). This bridge was created based on [mautrix-whatsapp](https://github.com/mautrix/whatsapp) and can be configured in a similar way to it. See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you. +## Prerequisite (optional) + +### Enable Shared Secret Auth + +If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. + ## Adjusting the playbook configuration -To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_go_skype_bridge_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. + +**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_go_skype_bridge_`. + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -31,6 +49,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). - -Send `help` to the bot to see the available commands. +To use the bridge, you need to start a chat with `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index 6fa4e0a68..d2484d8be 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -2,6 +2,8 @@ The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges. +The author of the bridges maintains [the official docs](https://docs.mau.fi/bridges/index.html), whose source code is available at [mautrix/docs](https://github.com/mautrix/docs) repository on GitHub. You may as well to refer it while configuring them. + You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository. ## Adjusting the playbook configuration @@ -159,6 +161,8 @@ To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` ( For details about the next steps, refer to each bridge's individual documentation page. +Send `help` to the bot to see the available commands. + If you run into trouble, check the [Troubleshooting](#troubleshooting) section below. ### Set up Double Puppeting (optional) @@ -204,4 +208,6 @@ When using this method, **each user** that wishes to enable Double Puppeting nee For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge. -Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us. +If the bridge's bot doesn't accept the invite to a chat, refer [the official troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html) as well. + +If you found bugs in mautrix bridges, they should be reported to the upstream project, in the corresponding mautrix repository, not to us. diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 9db84cd82..d5e6b4834 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -37,7 +37,7 @@ matrix_mautrix_discord_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -58,33 +58,16 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -### Logging in +To use the bridge, you need to start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html). -#### Method 1: Login using QR code (recommended) +After logging in, the bridge will create portal rooms for some recent direct messages. -For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone. +### Bridge guilds -You can delete the Discord app after the authentication process. +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. -#### Method 2: Login using Discord token (not recommended) +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. -To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be "ctrl+shift+i" or by pressing "F12"). Navigate to the "Network" tab then reload the page. In the URL filter or search bar type "/api" and find the response with the file name of "library". Under the request headers you should find a variable called "Authorization", this is the token to your Discord account. After copying the token, you can close the browser window. - -### Bridging - -1. Start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -2. If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command. -3. You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app. -4. After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with "Succcessfully authenticated as …" -5. Now that you're logged in, you can send `help` to the bot to see the available commands. -6. Some Direct Messages from Discord should start syncing automatically -7. If you'd like to bridge guilds: - - send `guilds status` to see the list of guilds - - for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire` -8. You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function. - -### Relaying - -The bridge supports using Discord's webhook feature to relay messages from Matrix users who haven't logged into the bridge. See [the official documentation](https://docs.mau.fi/bridges/go/discord/relay.html#setup) for setting up webhook relaying. +If you want to manually bridge channels, invite the bot to the room you want to bridge, and run `!discord bridge CHANNEL_ID_HERE` to bridge the room. Make sure to replace `CHANNEL_ID_HERE` with the channel's ID. diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 09124f8b7..51a162caf 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -30,7 +30,7 @@ matrix_mautrix_facebook_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index 5339e67ef..eae32a1f7 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -27,7 +27,7 @@ matrix_mautrix_gmessages_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -50,4 +50,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html). + +After logging in, the bridge will create portal rooms for recent chats. diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 4b179c139..4dbde4dd8 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -29,7 +29,7 @@ matrix_mautrix_googlechat_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -50,12 +50,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). +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). -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. +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html). -Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools. - -Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages. - -You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html). +After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages. diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index 8936217cd..307605be4 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -28,7 +28,7 @@ matrix_mautrix_hangouts_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -49,7 +49,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). +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). 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. diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index deef0c346..99988df41 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -20,7 +20,7 @@ matrix_mautrix_instagram_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index b95fcfff2..d89c1d50c 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -43,7 +43,7 @@ Before proceeding to [re-running the playbook](./installing.md), you may wish to There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -66,4 +66,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). + +After logging in, the bridge will sync recent chats. diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 1890e6c27..de3421147 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -56,7 +56,7 @@ Note that switching the mode (especially between `facebook*` and `messenger`) wi There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -79,8 +79,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`. -You then need to send `login` to the bridge bot and follow the instructions. +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). -Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html). +After logging in, the bridge will sync recent chats. -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). +**Note**: given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there. diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index 575646806..f0f1ccf74 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -32,7 +32,7 @@ matrix_mautrix_signal_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -55,4 +55,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html). + +After logging in, the bridge will bridge chats as you receive messages. + +**Note**: Signal does not support any kind of message history (even on official apps), so the bridge won't backfill any messages. diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 759020e56..b113f52f0 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -37,7 +37,7 @@ matrix_mautrix_slack_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -58,10 +58,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -1. Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -2. If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token. -3. The bot should respond with "Successfully logged into for team " -4. Now that you're logged in, you can send `help` to the bot to see the available commands. -5. Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication. +To use the bridge, you need to start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html). + +If you authenticated using a token, the recent chats will be bridged automatically (depending on the `conversation_count` setting). Otherwise (i.e. logging with the Discord application), the chats the bot is in will be bridged automatically. diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index 20500db2e..c907a1d90 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -36,6 +36,8 @@ matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH ### Relaying +### Enable relay-bot (optional) + If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml @@ -46,18 +48,13 @@ matrix_mautrix_telegram_configuration_extension_yaml: | '*': relaybot ``` -You might also want to give permissions to administrate the bot: +### Configure a user as an administrator of the bridge (optional) -```yaml -matrix_mautrix_telegram_configuration_extension_yaml: | - bridge: - permissions: - '@alice:{{ matrix_domain }}': admin -``` +You might also want to give permissions to a user to administrate the bot. See [this section](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional) on the common guide for details about it. More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410 -### Use the bridge for direct chat only +### Use the bridge for direct chats only (optional) If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -70,7 +67,7 @@ matrix_mautrix_telegram_filter_mode: whitelist There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -93,4 +90,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html). + +After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them. Note that the bridge won't automatically create rooms for private chats. diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index cf2a85f75..bb25019fe 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -10,7 +10,7 @@ See the project's [documentation](https://github.com/mautrix/twitter/blob/master ## Prerequisite (optional) -### Enable Appservice Double Puppet (optional) +### Enable Appservice Double Puppet If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook. @@ -29,7 +29,7 @@ matrix_mautrix_twitter_enabled: true There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -52,6 +52,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You then need to send login-cookie to start the login. The bot should respond with instructions on how to proceed. +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html). +After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages. diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index 257d53eae..8201be513 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -24,13 +24,11 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_whatsapp_enabled: true ``` -Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks. - ### Extending the configuration There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ## Installing @@ -53,4 +51,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). -You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html). +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html). + +Approximately in a minute after logging in, the bridge will create portal rooms for recent chats. + +**Note**: your linked devices will be logged out if you don’t use your phone for over 14 days (see the official FAQ entry [here](https://faq.whatsapp.com/general/download-and-installation/about-linked-devices)). The bridge will warn you if it doesn't receive any data from the phone over 12 days. diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index 02aa66fa6..ded9f0ca0 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -26,7 +26,7 @@ Note that the tokens must match what is compiled into the [mautrix-imessage](htt There are some additional things you may wish to configure about the bridge. -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#setting-the-bot-s-username-optional), etc. +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. ### Adjusting the wsproxy URL From 9c61742fa29d4c17d7ed57bf81238b146f5e0363 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 10 Jan 2025 23:53:39 +0900 Subject: [PATCH 185/952] Update docs for Element Web and SchildiChat Web (#3925) * Update docs for Element Web and SchildiChat Web: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs for Element Web and SchildiChat Web: remove redundant descriptions Signed-off-by: Suguru Hirahara * Update docs for Element Web and SchildiChat Web: reorganization Signed-off-by: Suguru Hirahara * Update docs for Element Web and SchildiChat Web: edit descriptions about themes Signed-off-by: Suguru Hirahara * Update docs for Element Web and SchildiChat Web: add examples of extending the configuration This follows docs/configuring-playbook-appservice-draupnir-for-all.md, etc. Note the examples are available on the main.yml files. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-client-element-web.md: add an instruction about the section on disabling Element Web Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...configuring-playbook-client-element-web.md | 84 +++++++++++++------ ...iguring-playbook-client-schildichat-web.md | 66 +++++++++++---- 2 files changed, 108 insertions(+), 42 deletions(-) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 08ad82448..0d4700377 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -2,45 +2,44 @@ By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document. +If you'd like to stop the playbook installing the client, see the section [below](#disabling-element-web) to check the configuration for disabling it. + 💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)): - [app.element.io](https://app.element.io/), hosted by [Element](https://element.io/) - [app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/) -## Disabling Element Web - -If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -matrix_client_element_enabled: false -``` - ## Adjusting the playbook configuration -The playbook provides some customization variables you could use to change Element Web's settings. - -Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template. - -**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes. - -Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change: - -- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used. - -- or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml). - -- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml). - ### Themes -To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting. +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. -Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`). +#### Use themes by `element-themes` -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. +To pull the themes from the `element-themes` project and use them for your Element Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_client_element_themes_enabled: true +``` + +If the variable is set to `true`, all themes found in the repository specified with `matrix_client_element_themes_repository_url` will be installed and enabled automatically. Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed. +#### Define themes manually + +You can also define your own themes manually by adding and adjusting the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +# Controls the `setting_defaults.custom_themes` setting of the Element Web configuration. +matrix_client_element_setting_defaults_custom_themes: [] +``` + +If you define your own themes with it and set `matrix_client_element_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well. + +If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it. + ### Adjusting the Element Web URL By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). @@ -58,6 +57,33 @@ matrix_client_element_hostname: "{{ matrix_server_fqn_matrix }}" matrix_client_element_path_prefix: /element ``` +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-client-element/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-client-element/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_element_configuration_extension_json` variable + +For example, to override some Element Web settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml + # Your custom JSON configuration for Element Web should go to `matrix_client_element_configuration_extension_json`. + # This configuration extends the default starting configuration (`matrix_client_element_configuration_default`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_client_element_configuration_default`. + # +matrix_client_element_configuration_extension_json: | + { + "disable_3pid_login": true, + "disable_login_language_selector": true + } +``` + ## Adjusting DNS records Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server. @@ -66,6 +92,14 @@ By default, you will need to create a CNAME record for `element`. See [Configuri If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +## Disabling Element Web + +If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_client_element_enabled: false +``` + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index a9064e250..0a67f04be 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -16,30 +16,35 @@ To enable SchildiChat Web, add the following configuration to your `inventory/ho matrix_client_schildichat_enabled: true ``` -The playbook provides some customization variables you could use to change SchildiChat Web's settings. - -Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template. - -**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes. - -Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change: - -- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used. - -- or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml). - -- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml). - ### Themes -To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting. +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. -Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`). +#### Use themes by `element-themes` -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. +To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_client_schildichat_themes_enabled: true +``` + +If the variable is set to `true`, all themes found in the repository specified with `matrix_client_schildichat_themes_repository_url` will be installed and enabled automatically. Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed. +#### Define themes manually + +You can also define your own themes manually by adding and adjusting the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +# Controls the `setting_defaults.custom_themes` setting of the SchildiChat Web configuration. +matrix_client_schildichat_setting_defaults_custom_themes: [] +``` + +If you define your own themes with it and set `matrix_client_schildichat_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well. + +If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it. + ### Adjusting the SchildiChat Web URL By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). @@ -57,6 +62,33 @@ matrix_client_schildichat_hostname: "{{ matrix_server_fqn_matrix }}" matrix_client_schildichat_path_prefix: /schildichat ``` +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-client-schildichat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-client-schildichat/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_schildichat_configuration_extension_json` variable + +For example, to override some SchildiChat Web settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml + # Your custom JSON configuration for SchildiChat Web should go to `matrix_client_schildichat_configuration_extension_json`. + # This configuration extends the default starting configuration (`matrix_client_schildichat_configuration_default`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_client_schildichat_configuration_default`. + # +matrix_client_schildichat_configuration_extension_json: | + { + "disable_3pid_login": true, + "disable_login_language_selector": true + } +``` + ## Adjusting DNS records Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server. From d076a75a0a969212279674fcbd5410ba06bfbd0a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Fri, 10 Jan 2025 18:58:14 +0000 Subject: [PATCH 186/952] Update joseluisq/static-web-server Docker tag to v2.35.0 --- roles/custom/matrix-cactus-comments-client/defaults/main.yml | 2 +- roles/custom/matrix-static-files/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 8d00cc1e5..6a43ba585 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -13,7 +13,7 @@ matrix_cactus_comments_client_public_path: "{{ matrix_cactus_comments_client_bas matrix_cactus_comments_client_public_path_file_permissions: "0644" # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_cactus_comments_client_version: 2.34.0 +matrix_cactus_comments_client_version: 2.35.0 matrix_cactus_comments_client_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}" diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index 112c4414b..248062ab2 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -8,7 +8,7 @@ matrix_static_files_enabled: true matrix_static_files_identifier: matrix-static-files # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_static_files_version: 2.34.0 +matrix_static_files_version: 2.35.0 matrix_static_files_base_path: "{{ matrix_base_data_path }}/{{ 'static-files' if matrix_static_files_identifier == 'matrix-static-files' else matrix_static_files_identifier }}" matrix_static_files_config_path: "{{ matrix_static_files_base_path }}/config" From 57e45c3081b05557d19a5d293d4aa77d79342f29 Mon Sep 17 00:00:00 2001 From: Jonatan Date: Fri, 10 Jan 2025 22:48:02 +0100 Subject: [PATCH 187/952] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1e487cd92..ba9439dc8 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow | ---- | -------- | ----------- | ------------- | | [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) | | [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) | -| [Dendrite](https://github.com/matrix-org/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) | +| [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) | ### Clients From b017ffd853cacbe8312b4fabcde2d865a8f8492b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 11 Jan 2025 16:49:53 +0900 Subject: [PATCH 188/952] Update docs for homeserver implementations (Conduit, Dendrite, and Synapse) (#3926) * Update docs for Dendrite and Synapse: adopt the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse.md: move down the section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs for Dendrite and Synapse: remove redundant descriptions Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-conduit.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs for Conduit and Dendrite: replace "Notes" with "Warnings" plus the warning symbol The information is important and should deserve clear attention. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse.md: reorganize sections for adjusting the playbook configuration As the section for Synapse Admin is not related to adjusting the configuration, it was moved out of the it Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse.md: on Synapse Admin Based on docs/configuring-playbook-bot-draupnir.md Signed-off-by: Suguru Hirahara * Update URLs of the forked Dendrite repository Signed-off-by: Suguru Hirahara * Update docs for Conduit and Dendrite: use the common descriptions for introductions - Edit the instruction for adjusting the configuration Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse-admin.md: update the URL of the Dendrite documentation Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse.md: add the sections "Installing" and "Usage" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-conduit.md: copy an instruction from roles/custom/matrix-conduit/defaults/main.yml Signed-off-by: Suguru Hirahara * Update docs for Conduit and Dendrite: fix capitalization Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-conduit.md | 27 +++++++-- docs/configuring-playbook-dendrite.md | 44 +++++++++++---- docs/configuring-playbook-synapse-admin.md | 2 +- docs/configuring-playbook-synapse.md | 66 +++++++++++++--------- docs/configuring-playbook-telemetry.md | 2 +- 5 files changed, 97 insertions(+), 44 deletions(-) diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 68faa0d3c..c2d010874 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -1,21 +1,40 @@ # Configuring Conduit (optional) -By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs). +The playbook can install and configure the [Conduit](https://conduit.rs) Matrix server for you. -**Notes**: +See the project's [documentation](https://docs.conduit.rs/) to learn what it does and why it might be useful to you. + +By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. + +⚠️ **Warnings**: - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. -- **homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding +- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration -To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To use Conduit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below: ```yaml matrix_homeserver_implementation: conduit ``` +### Extending the configuration + +There are some additional things you may wish to configure about the server. + +Take a look at: + +- `roles/custom/matrix-conduit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-conduit/templates/conduit.toml.j2` for the server's default configuration + +If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yaml` file like this: + +```yaml +matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduit.toml.j2" +``` + ## Creating the first user account Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure: diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 00bde90b4..8e4d8f11c 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -1,34 +1,54 @@ # Configuring Dendrite (optional) -By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite). +The playbook can install and configure the [Dendrite](https://github.com/element-hq/dendrite) Matrix server for you. -**Notes**: +See the project's [documentation](https://element-hq.github.io/dendrite/) to learn what it does and why it might be useful to you. + +By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. + +⚠️ **Warnings**: - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. -- **homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding +- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration -To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To use Dendrite, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below: ```yaml matrix_homeserver_implementation: dendrite ``` -The playbook provides lots of customization variables you could use to change Dendrite's settings. +### Extending the configuration -Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite.yaml.j2) template. +There are some additional things you may wish to configure about the server. -**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes. +Take a look at: -Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change: +- `roles/custom/matrix-dendrite/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-dendrite/templates/dendrite.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dendrite_configuration_extension_yaml` variable -- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used. +For example, to override some Dendrite settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: -- or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). - -- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml). +```yaml +matrix_dendrite_configuration_extension_yaml: | + # Your custom YAML configuration for Dendrite goes here. + # This configuration extends the default starting configuration (`matrix_dendrite_configuration_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_dendrite_configuration_yaml`. + # + # Example configuration extension follows: + # + server_notices: + system_mxid_localpart: notices + system_mxid_display_name: "Server Notices" + system_mxid_avatar_url: "mxc://example.com/oumMVlgDnLYFaPVkExemNVVZ" + room_name: "Server Notices" +``` ## Installing diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index dbdbafcd6..8c1088d28 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -2,7 +2,7 @@ The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you. -synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/). +synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/). 💡 **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. diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 9ec3876aa..bf4d05fd2 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -2,21 +2,9 @@ By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document. -The playbook provides lots of customization variables you could use to change Synapse's settings. +## Adjusting the playbook configuration -Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template. - -**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes. - -Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change: - -- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used. - -- or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml). - -- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml). - -## Load balancing with workers +### Load balancing with workers To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). @@ -30,7 +18,7 @@ matrix_synapse_workers_preset: one-of-each By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances). -### Worker presets +#### Worker presets We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now): @@ -40,7 +28,7 @@ We support a few configuration presets (`matrix_synapse_workers_preset: one-of-e These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs. -#### Generic workers +##### Generic workers Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data. @@ -50,7 +38,7 @@ To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each). -#### Specialized workers +##### Specialized workers The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested. @@ -63,7 +51,7 @@ The playbook supports these **4 types** of specialized workers: To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each). -#### Controlling the number of worker instances +##### Controlling the number of worker instances If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually. @@ -71,7 +59,7 @@ To find what variables are available for you to override in your own `vars.yml` The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers). -#### Effect of enabling workers on the rest of your server +##### Effect of enabling workers on the rest of your server When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable. @@ -79,11 +67,7 @@ A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`. -## Synapse Admin - -Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md). - -## Synapse + OpenID Connect for Single-Sign-On +### Synapse + OpenID Connect for Single-Sign-On 💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment. @@ -114,7 +98,7 @@ matrix_synapse_oidc_providers: backchannel_logout_enabled: true # Optional ``` -## Customizing templates +### Customizing templates [Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**. @@ -152,7 +136,37 @@ matrix_synapse_container_image_customizations_templates_git_repository_ssh_priva As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates. -## Monitoring Synapse Metrics with Prometheus and Grafana +### Extending the configuration + +There are some additional things you may wish to configure about the server. + +Take a look at: + +- `roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Usage + +### Synapse Admin + +With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace. + +The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). + +### Monitoring Synapse Metrics with Prometheus and Grafana This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse. diff --git a/docs/configuring-playbook-telemetry.md b/docs/configuring-playbook-telemetry.md index 111a27da7..aa26fb734 100644 --- a/docs/configuring-playbook-telemetry.md +++ b/docs/configuring-playbook-telemetry.md @@ -18,4 +18,4 @@ matrix_dendrite_report_stats: true # for dendrite When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver. -See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported. +See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/element-hq/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported. From a6f399f4a07788799dd674f4316b6ea48540a5fe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 11 Jan 2025 17:55:27 +0900 Subject: [PATCH 189/952] Update docs/configuring-playbook-synapse-s3-storage-provider.md: fix the path to media-store directory Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-s3-storage-provider.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index 05b6debb2..39482583c 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -47,7 +47,7 @@ matrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD # # For additional advanced settings, take a look at `roles/custom/matrix-synapse/defaults/main.yml` ``` -If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`): +If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/..`): - new files will start being stored both locally and on the S3 store - the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) From eaba9cc75e0c76211e3bd6c7e57834dd1d2bf939 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 11 Jan 2025 23:50:51 +0900 Subject: [PATCH 190/952] =?UTF-8?q?Replace=20double=20or=20triple=20dots?= =?UTF-8?q?=20with=20horizontal=20ellipses=20(=E2=80=9C=E2=80=A6=E2=80=9D?= =?UTF-8?q?=20U+2026)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 14 +++++++------- docs/ansible.md | 2 +- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bridge-postmoogle.md | 2 +- docs/configuring-playbook-matrix-corporal.md | 2 +- docs/configuring-playbook-ssl-certificates.md | 2 +- docs/configuring-playbook-sygnal.md | 6 +++--- ...iguring-playbook-synapse-s3-storage-provider.md | 10 +++++----- docs/configuring-playbook-synapse.md | 2 +- docs/faq.md | 2 +- docs/installing.md | 2 +- group_vars/matrix_servers | 2 +- i18n/justfile | 8 ++++---- 13 files changed, 28 insertions(+), 28 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a127deb13..ea4a530f1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -547,7 +547,7 @@ Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/ On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`). -Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service. +Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but… not quite enough to enjoy going through a chain of ~4 of them before reaching the target service. After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`. @@ -1146,7 +1146,7 @@ Others still, wanted to run Matrix locally (no SSL certificates), regardless of Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations. -When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes). +When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still… yikes). The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks: @@ -1415,7 +1415,7 @@ The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the d If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects. -These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles. +These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy …` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles. # 2022-11-20 @@ -1428,7 +1428,7 @@ These additional roles are downloaded into the playbook directory (to `roles/gal Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md). -Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090). +Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore… which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090). ### Solution @@ -2199,7 +2199,7 @@ To migrate to the new setup, expect a few minutes of downtime, while you follow matrix_postgres_connection_password: 'YOUR_POSTGRES_PASSWORD_HERE' ``` -.. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2. +… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2. 4. Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` 5. Log in to the server via SSH. The next commands will be performed there. @@ -2211,7 +2211,7 @@ To migrate to the new setup, expect a few minutes of downtime, while you follow CREATE ROLE matrix LOGIN SUPERUSER PASSWORD 'YOUR_POSTGRES_PASSWORD_HERE'; ``` -.. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2. +… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2. 9. Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**): @@ -3630,7 +3630,7 @@ Changing that value allows you to potentially decrease RAM usage or to increase `--log-driver=none` is used for all Docker containers now. -All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart. +All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/…` infinitely until service/container restart. As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs. diff --git a/docs/ansible.md b/docs/ansible.md index 0fe8c9e84..87b4d86e8 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -42,7 +42,7 @@ To run Ansible in a (Docker) container on the Matrix server itself, you need to - you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker - **or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around -Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md). +Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/…`, etc.), as described in [configuring the playbook](configuring-playbook.md). You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the "remote" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH. diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 1a80546e0..91aabb2f6 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -87,7 +87,7 @@ If `matrix_admin` is already configured in your `vars.yml` configuration, you ca # - "@*:example.com" # - "@admin:example.net" # -# .. unless you've made yourself an admin of all bots/bridges like this: +# … unless you've made yourself an admin of all bots/bridges like this: # # matrix_admin: '@yourAdminAccount:{{ matrix_domain }}' ``` diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 15a7a39ec..9622b6919 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -37,7 +37,7 @@ matrix_postmoogle_password: PASSWORD_FOR_THE_BOT # matrix_postmoogle_admins: # - '@yourAdminAccount:{{ matrix_domain }}' # -# .. unless you've made yourself an admin of all bots/bridges like this: +# … unless you've made yourself an admin of all bots/bridges like this: # # matrix_admin: '@yourAdminAccount:{{ matrix_domain }}' ``` diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 622d4b59d..6c4df4985 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -48,7 +48,7 @@ matrix_corporal_policy_provider_config: | "TimeoutMilliseconds": 300 } -# If you also want to enable Matrix Corporal's HTTP API.. +# If you also want to enable Matrix Corporal's HTTP API… matrix_corporal_http_api_enabled: true matrix_corporal_http_api_auth_token: "AUTH_TOKEN_HERE" diff --git a/docs/configuring-playbook-ssl-certificates.md b/docs/configuring-playbook-ssl-certificates.md index fc004d0bf..9345544d3 100644 --- a/docs/configuring-playbook-ssl-certificates.md +++ b/docs/configuring-playbook-ssl-certificates.md @@ -50,7 +50,7 @@ traefik_ssl_dir_enabled: true # Tell Traefik to load our custom ssl key pair by extending provider configuration. # The key pair files are created below, in `aux_file_definitions`. -# The `/ssl/..` path is an in-container path, not a path on the host (like `/matrix/traefik/ssl`). Do not change it! +# The `/ssl/…` path is an in-container path, not a path on the host (like `/matrix/traefik/ssl`). Do not change it! traefik_provider_configuration_extension_yaml: tls: certificates: diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 8965ad4da..10094e9f9 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -23,11 +23,11 @@ matrix_sygnal_apps: com.example.myapp.ios: type: apns keyfile: /data/my_key.p8 - # .. more configuration .. + # … more configuration … com.example.myapp.android: type: gcm api_key: your_api_key_for_gcm - # .. more configuration .. + # … more configuration … aux_file_definitions: - dest: "{{ matrix_sygnal_data_path }}/my_key.p8" @@ -48,7 +48,7 @@ To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Noti - makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`. -- references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container) +- references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/…` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container) ### Adjusting the Sygnal URL diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index 39482583c..bb2ccc596 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -47,7 +47,7 @@ matrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD # # For additional advanced settings, take a look at `roles/custom/matrix-synapse/defaults/main.yml` ``` -If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/..`): +If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`): - new files will start being stored both locally and on the S3 store - the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) @@ -85,7 +85,7 @@ Instead of running the above commands manually in the shell, you can also run th - it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool - allows you to check and verify the output of each command, to catch mistakes - includes progress bars and detailed output for each command -- allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`) +- allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill …`) ### Using another tool in combination with `s3_media_upload` @@ -140,7 +140,7 @@ As described in [How it works?](#how-it-works) above, when new media is uploaded By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using: - the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script -- .. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service -- .. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00 +- … invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service +- … triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00 -So.. you don't need to perform any maintenance yourself. +So… you don't need to perform any maintenance yourself. diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index bf4d05fd2..dfa9e90ff 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -130,7 +130,7 @@ matrix_synapse_container_image_customizations_templates_git_repository_keyscan_h # If your git repository is public, do not define the private key (remove the variable). matrix_synapse_container_image_customizations_templates_git_repository_ssh_private_key: | -----BEGIN OPENSSH PRIVATE KEY----- - .... + … -----END OPENSSH PRIVATE KEY----- ``` diff --git a/docs/faq.md b/docs/faq.md index fae014a3d..b11a8d0b7 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -98,7 +98,7 @@ Reading the documentation of this Ansible playbook, you may also be thinking: > I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated. -.. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md). +… so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md). The problem with a manual installation is: diff --git a/docs/installing.md b/docs/installing.md index 75d33dffc..c4eda3b9f 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -65,7 +65,7 @@ You can now: - [Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional) -.. and then proceed to starting all services: +… and then proceed to starting all services: ```sh ansible-playbook -i inventory/hosts setup.yml --tags=ensure-matrix-users-created,start diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index a46140347..de7c84d52 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -268,7 +268,7 @@ matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_s # - Matrix utility services (bridges, bots) get a level of 2000/2200, so that: # - they can start before the reverse-proxy # - so that, when the reverse-proxy is up (Matrix is up), all bots and bridges can be interacted with -# - monitoring services (Prometheus, Grafana, ..) get a level of 4000 - they can start later than all-of-Matrix +# - monitoring services (Prometheus, Grafana, …) get a level of 4000 - they can start later than all-of-Matrix # - services which aren't time-sensitive (various crons and timers) get a level of 5000 - they can start later than all-of-Matrix devture_systemd_service_manager_services_list_auto: | {{ diff --git a/i18n/justfile b/i18n/justfile index a3936e7e9..57b9d8400 100644 --- a/i18n/justfile +++ b/i18n/justfile @@ -9,7 +9,7 @@ default: # Extracts original English strings (translation templates) into the `translation-templates/` directory extract-translation-templates: _venv - @echo "Extracting translation templates..." + @echo "Extracting translation templates…" PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/extract-translation-templates.sh # Syncs the translation templates (affects `translation-templates/`) and strings (affects `locales/*`) for all published languages (`PUBLISHED_LANGUAGES`) @@ -24,7 +24,7 @@ sync-for-all-known-languages: #!/bin/sh find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do language=$(basename "$path") - echo "Syncing for language $language.." + echo "Syncing for language $language…" {{ just_executable() }} sync-for-language $language done @@ -51,7 +51,7 @@ build-for-all-known-languages: #!/bin/sh find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do language=$(basename "$path") - echo "Building for language $language.." + echo "Building for language $language…" {{ just_executable() }} build-for-language $language done @@ -59,7 +59,7 @@ build-for-all-known-languages: _venv: #!/bin/sh if [ ! -f {{ justfile_directory() }}/.venv/bin/sphinx-build ]; then - echo "No sphinx-build found, creating virtual environment and installing requirements..." + echo "No sphinx-build found, creating virtual environment and installing requirements…" uv venv {{ justfile_directory() }}/.venv VIRTUAL_ENV={{ justfile_directory() }}/.venv uv pip install -r {{ justfile_directory() }}/requirements.txt fi From 04cb2f8fa58cff5d1c71227ed99f17390d705b8d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 12 Jan 2025 20:19:08 +0900 Subject: [PATCH 191/952] Update docs/configuring-playbook-synapse-s3-storage-provider.md (#3932) * Update docs/configuring-playbook-synapse-s3-storage-provider.md: adopt the common instruction Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse-s3-storage-provider.md: add the sections "Extending the configuration" and "Usage" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-synapse-s3-storage-provider.md: minor changes Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...ng-playbook-synapse-s3-storage-provider.md | 32 ++++++++++++------- 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index bb2ccc596..02b79c240 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -23,7 +23,7 @@ While you will need some local disk space around, it's only to accommodate usage ## Adjusting the playbook configuration -After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`): +After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_ext_synapse_s3_storage_provider_enabled: true @@ -43,10 +43,18 @@ matrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD # # This only works on AWS when your server is hosted on an EC2 instance with the correct instance profile set. # Uncomment the variable below to use it. # matrix_synapse_ext_synapse_s3_storage_provider_config_ec2_instance_profile: true - -# For additional advanced settings, take a look at `roles/custom/matrix-synapse/defaults/main.yml` ``` +### Extending the configuration + +There are some additional things you may wish to configure about the server. + +Take a look at: + +- `roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + +## Usage + If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`): - new files will start being stored both locally and on the S3 store @@ -55,16 +63,16 @@ If you have existing files in Synapse's media repository (`/matrix/synapse/stora Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below. -## Migrating your existing media files to the S3 store +### Migrating your existing media files to the S3 store Migrating your existing data can happen in multiple ways: - [using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data) - [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data) -### Using the `s3_media_upload` script from `synapse-s3-storage-provider` +💡 **Note**: instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload). -Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload). +#### Using the `s3_media_upload` script from `synapse-s3-storage-provider` To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`. @@ -87,7 +95,7 @@ Instead of running the above commands manually in the shell, you can also run th - includes progress bars and detailed output for each command - allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill …`) -### Using another tool in combination with `s3_media_upload` +#### Using another tool in combination with `s3_media_upload` To migrate your existing local data to S3, we recommend to: @@ -95,7 +103,7 @@ To migrate your existing local data to S3, we recommend to: - **only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files) -#### Copying data to Amazon S3 +##### Copying data to Amazon S3 To copy to AWS S3, start a container on the Matrix server like this: @@ -109,13 +117,13 @@ docker.io/amazon/aws-cli:2.9.16 \ -c 'aws s3 sync /work/. s3://$BUCKET/' ``` -#### Copying data to an S3 alternative using the aws-s3 tool +##### Copying data to an S3 alternative using the aws-s3 tool -To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument. +To copy to a provider other than AWS S3 (e.g. Storj, Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument. Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command. -#### Copying data to Backblaze B2 +##### Copying data to Backblaze B2 You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below. @@ -133,7 +141,7 @@ docker.io/tianon/backblaze-b2:3.6.0 \ -c 'b2 authorize-account $B2_KEY_ID $B2_KEY_SECRET && b2 sync /work b2://$B2_BUCKET_NAME --skipNewer' ``` -## Periodically cleaning up the local filesystem +### Periodically cleaning up the local filesystem As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage. From 61ace3a0639242a660281b516da4f03c5f0a37cc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 12 Jan 2025 22:31:19 +0900 Subject: [PATCH 192/952] Edit lines for `vars.yml` (#3933) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Simplify paths to vars.yml if referred multiple times Signed-off-by: Suguru Hirahara * Fix the filename: vars.yaml → vars.yml Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 2 +- ...iguring-playbook-appservice-draupnir-for-all.md | 2 +- docs/configuring-playbook-bot-baibot.md | 4 ++-- docs/configuring-playbook-bot-buscarron.md | 2 +- docs/configuring-playbook-bot-draupnir.md | 8 ++++---- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bot-honoroit.md | 2 +- docs/configuring-playbook-bot-maubot.md | 4 ++-- docs/configuring-playbook-bot-mjolnir.md | 10 +++++----- ...nfiguring-playbook-bridge-appservice-discord.md | 4 ++-- docs/configuring-playbook-bridge-heisenbridge.md | 2 +- docs/configuring-playbook-bridge-hookshot.md | 2 +- .../configuring-playbook-bridge-mautrix-bridges.md | 14 +++++++------- ...configuring-playbook-bridge-mautrix-telegram.md | 4 ++-- .../configuring-playbook-bridge-mautrix-wsproxy.md | 2 +- docs/configuring-playbook-cactus-comments.md | 2 +- docs/configuring-playbook-client-cinny.md | 2 +- docs/configuring-playbook-client-element-web.md | 8 ++++---- docs/configuring-playbook-client-hydrogen.md | 2 +- .../configuring-playbook-client-schildichat-web.md | 8 ++++---- docs/configuring-playbook-conduit.md | 2 +- docs/configuring-playbook-dendrite.md | 2 +- docs/configuring-playbook-dimension.md | 4 ++-- docs/configuring-playbook-email2matrix.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-federation.md | 6 +++--- docs/configuring-playbook-jitsi.md | 12 +++++------- docs/configuring-playbook-ma1sd.md | 6 +++--- ...uring-playbook-matrix-authentication-service.md | 6 +++--- docs/configuring-playbook-matrix-registration.md | 2 +- docs/configuring-playbook-ntfy.md | 2 +- docs/configuring-playbook-prometheus-grafana.md | 2 +- docs/configuring-playbook-rageshake.md | 2 +- docs/configuring-playbook-sliding-sync-proxy.md | 2 +- docs/configuring-playbook-ssl-certificates.md | 2 +- docs/configuring-playbook-sygnal.md | 2 +- docs/configuring-playbook-synapse-admin.md | 2 +- .../configuring-playbook-synapse-usage-exporter.md | 2 +- docs/configuring-playbook-synapse.md | 2 +- roles/custom/matrix-conduit/defaults/main.yml | 2 +- 40 files changed, 74 insertions(+), 76 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 351432662..7a066c293 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -67,7 +67,7 @@ By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index a62695526..3a024545a 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -52,7 +52,7 @@ matrix_appservice_draupnir_for_all_master_control_room_alias: "MANAGEMENT_ROOM_A You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable. -For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `vars.yml` file: ```yaml matrix_appservice_draupnir_for_all_extension_yaml: | diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 91aabb2f6..3b6abcedc 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -78,7 +78,7 @@ To specify who is considered a bot [👮‍♂️ Administrator](https://github. If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section. -**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +**If necessary**, add the following configuration to your `vars.yml` file: ```yaml # Uncomment to add one or more admins to this bridge: @@ -107,7 +107,7 @@ Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is op **Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands. -**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +**If necessary**, add the following configuration to your `vars.yml` file: ```yaml # Uncomment and adjust the bot users if necessary: diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 1ac73e7e3..089fd35da 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -35,7 +35,7 @@ By default, this playbook installs Buscarron on the `buscarron.` subdomain (`bus By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index bce4de3fc..fa3d3e555 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -66,7 +66,7 @@ Finally invite the `@bot.draupnir:example.com` account you created earlier into ## Adjusting the playbook configuration -To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. ```yaml # Enable Draupnir @@ -85,7 +85,7 @@ To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantal When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +Add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml # Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md @@ -115,7 +115,7 @@ matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_ When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). +Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" @@ -137,7 +137,7 @@ The other method polls an Synapse Admin API endpoint, hence it is available only You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable. -For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `vars.yml` file: ```yaml matrix_bot_draupnir_configuration_extension_yaml: | diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index c8c84f876..01f86828e 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -200,7 +200,7 @@ By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.exam By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index be8c9acee..eed5d70db 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -29,7 +29,7 @@ By default, this playbook installs Honoroit on the `matrix.` subdomain, at the ` By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index a782920af..a82f5c66e 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -31,7 +31,7 @@ By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_ By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix @@ -53,7 +53,7 @@ Certain [maubot plugins](https://plugins.mau.bot/) require additional dependenci You can customize the default maubot container image and install your own dependencies. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml matrix_bot_maubot_container_image_customizations_enabled: true diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index d79f085b5..c7a211491 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -62,7 +62,7 @@ Finally invite the `@bot.mjolnir:example.com` account you created earlier into t ## Adjusting the playbook configuration -To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. ```yaml # Enable Mjolnir @@ -81,7 +81,7 @@ To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantala When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +Add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml # Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md @@ -111,7 +111,7 @@ matrix_bot_mjolnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_u When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). +Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). ```yaml matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_HERE" @@ -119,7 +119,7 @@ matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_HERE" ### Adding Mjolnir synapse antispam module (optional) -To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +To enable Mjolnir synapse antispam module, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml matrix_synapse_ext_spam_checker_mjolnir_antispam_enabled: true @@ -133,7 +133,7 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. -For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file: ```yaml matrix_bot_mjolnir_configuration_extension_yaml: | diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 2fecb6625..5368db974 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -47,7 +47,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Self-Service Bridging (Manual) -Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `vars.yml` file: ```yaml matrix_appservice_discord_bridge_enableSelfServiceBridging: true @@ -73,7 +73,7 @@ Through portal bridging, Matrix rooms will automatically be created by the bot a 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. -To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To disable portal bridging, add the following configuration to your `vars.yml` file: ```yaml matrix_appservice_discord_bridge_disablePortalBridging: true diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index 0b440547f..5e1ae4c27 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -31,7 +31,7 @@ This makes it easy to install it, because it **doesn't require additional DNS re By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 57fd199fc..e0f852f1c 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -105,7 +105,7 @@ The GitHub bridge requires you to install a private key file. This can be done i - somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually. - use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server. -To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `vars.yml` file: ```yaml aux_file_definitions: diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index d2484d8be..12f70a66e 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -23,7 +23,7 @@ There are some additional things you may wish to configure about the bridge befo By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings. -Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `vars.yml` file: ```yaml matrix_admin: "@alice:{{ matrix_domain }}" @@ -46,7 +46,7 @@ You could also redefine the default permissions settings completely, rather than ### Enable encryption (optional) -[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `vars.yml` file: **for all bridges with encryption support**: @@ -66,7 +66,7 @@ matrix_mautrix_SERVICENAME_bridge_encryption_default: true [Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode. -If you would like to enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +If you would like to enable it, add the following configuration to your `vars.yml` file: **for all bridges with relay mode support**: @@ -103,7 +103,7 @@ Use `!prefix set-pl 100` to be able for the bot to modify room settings and invi #### Allow anyone on the homeserver to become a relay user (optional) -By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `vars.yml` file: ```yaml matrix_mautrix_SERVICENAME_bridge_relay_admin_only: false @@ -111,7 +111,7 @@ matrix_mautrix_SERVICENAME_bridge_relay_admin_only: false ### Set the bot's username (optional) -To set the bot's username, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To set the bot's username, add the following configuration to your `vars.yml` file: ```yaml matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" @@ -119,7 +119,7 @@ matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" ### Configure the logging level (optional) -To specify the logging level, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To specify the logging level, add the following configuration to your `vars.yml` file: ```yaml matrix_mautrix_SERVICENAME_logging_level: warn @@ -177,7 +177,7 @@ To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppetin Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver. -To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable the Appservice Double Puppet service, add the following configuration to your `vars.yml` file: ```yaml matrix_appservice_double_puppet_enabled: true diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index c907a1d90..f3deabc77 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -38,7 +38,7 @@ matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH ### Enable relay-bot (optional) -If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `vars.yml` file: ```yaml matrix_mautrix_telegram_bot_token: YOUR_TELEGRAM_BOT_TOKEN @@ -56,7 +56,7 @@ More details about permissions in this example: https://github.com/mautrix/teleg ### Use the bridge for direct chats only (optional) -If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `vars.yml` file: ```yaml matrix_mautrix_telegram_filter_mode: whitelist diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index ded9f0ca0..f9a91af5c 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -34,7 +34,7 @@ By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index f890b9775..a1721eb09 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -44,7 +44,7 @@ By default, this playbook installs Cactus Comments' client on the `matrix.` subd By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix to host the client assets at a different location diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index d943819be..0bbf71222 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -24,7 +24,7 @@ By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to a different domain (`app.example.com`) than the default one (`cinny.example.com`) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 0d4700377..d88707b7d 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -29,7 +29,7 @@ Note that for a custom theme to work well, all Element Web instances that you us #### Define themes manually -You can also define your own themes manually by adding and adjusting the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file: ```yaml # Controls the `setting_defaults.custom_themes` setting of the Element Web configuration. @@ -46,7 +46,7 @@ By default, this playbook installs Element Web on the `element.` subdomain (`ele By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), @@ -66,7 +66,7 @@ Take a look at: - `roles/custom/matrix-client-element/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - `roles/custom/matrix-client-element/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_element_configuration_extension_json` variable -For example, to override some Element Web settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to override some Element Web settings, add the following configuration to your `vars.yml` file: ```yaml # Your custom JSON configuration for Element Web should go to `matrix_client_element_configuration_extension_json`. @@ -94,7 +94,7 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra ## Disabling Element Web -If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file: ```yaml matrix_client_element_enabled: false diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index 04baa5c8b..3166005ae 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -18,7 +18,7 @@ By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydro By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 0a67f04be..380382937 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -22,7 +22,7 @@ You can change the look of SchildiChat Web by pulling themes provided by the [aa #### Use themes by `element-themes` -To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file: ```yaml matrix_client_schildichat_themes_enabled: true @@ -34,7 +34,7 @@ Note that for a custom theme to work well, all SchildiChat Web instances that yo #### Define themes manually -You can also define your own themes manually by adding and adjusting the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file: ```yaml # Controls the `setting_defaults.custom_themes` setting of the SchildiChat Web configuration. @@ -51,7 +51,7 @@ By default, this playbook installs SchildiChat Web on the `schildichat.` subdoma By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), @@ -71,7 +71,7 @@ Take a look at: - `roles/custom/matrix-client-schildichat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - `roles/custom/matrix-client-schildichat/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_schildichat_configuration_extension_json` variable -For example, to override some SchildiChat Web settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to override some SchildiChat Web settings, add the following configuration to your `vars.yml` file: ```yaml # Your custom JSON configuration for SchildiChat Web should go to `matrix_client_schildichat_configuration_extension_json`. diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index c2d010874..2eb571003 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -29,7 +29,7 @@ Take a look at: - `roles/custom/matrix-conduit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - `roles/custom/matrix-conduit/templates/conduit.toml.j2` for the server's default configuration -If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yaml` file like this: +If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yml` file like this: ```yaml matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduit.toml.j2" diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 8e4d8f11c..83510e7af 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -29,7 +29,7 @@ Take a look at: - `roles/custom/matrix-dendrite/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - `roles/custom/matrix-dendrite/templates/dendrite.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dendrite_configuration_extension_yaml` variable -For example, to override some Dendrite settings, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +For example, to override some Dendrite settings, add the following configuration to your `vars.yml` file: ```yaml matrix_dendrite_configuration_extension_yaml: | diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 3fa0ea688..fe742165e 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -48,7 +48,7 @@ matrix_dimension_access_token: "ACCESS_TOKEN_HERE" ### Define admin users -To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `vars.yml` file: ```yaml matrix_dimension_admins: @@ -64,7 +64,7 @@ By default, this playbook installs Dimension on the `dimension.` subdomain (`dim By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 619dfd2c3..02881ac64 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -56,7 +56,7 @@ Take note of each room's room ID (different clients show the room ID in a differ ## Adjusting the playbook configuration -To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token). +To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token). ```yaml matrix_email2matrix_enabled: true diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 63700e955..99ec8064d 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -22,7 +22,7 @@ By default, this playbook installs Etherpad on the `etherpad.` subdomain (`ether By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index 3bf9ecc70..87e573830 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -20,7 +20,7 @@ If you wish to disable federation, you can do that with an empty list (`[]`), or By default, your server's public rooms directory is not exposed to other servers via federation. -To expose it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To expose it, add the following configuration to your `vars.yml` file: ```yaml matrix_synapse_allow_public_rooms_over_federation: true @@ -28,7 +28,7 @@ matrix_synapse_allow_public_rooms_over_federation: true ## Disabling federation -To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `vars.yml` file: ```yaml matrix_homeserver_federation_enabled: false @@ -52,7 +52,7 @@ matrix_synapse_reverse_proxy_companion_federation_api_enabled: false Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection. -To make it possible to proxy the federation through a CDN such as CloudFlare or any other, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +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: ```yaml matrix_synapse_http_listener_resource_names: ["client","federation"] diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 29ded06b4..923addd3d 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -27,7 +27,7 @@ By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.examp By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname @@ -56,7 +56,7 @@ Currently, there are three supported authentication modes: 'internal' (default), The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms. -Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration: +Add the following configuration to your `vars.yml` file: ```yaml jitsi_enable_auth: true @@ -118,9 +118,7 @@ By default the Jitsi Meet instance does not work with a client in LAN (Local Are The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work. -Here is how to do it in the playbook. - -Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration: +To enable it, add the following configuration to your `vars.yml` file: ```yaml jitsi_jvb_container_extra_arguments: @@ -129,7 +127,7 @@ jitsi_jvb_container_extra_arguments: ## Fine tune Jitsi (optional) -Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below): +If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml jitsi_web_custom_config_extension: | @@ -175,7 +173,7 @@ For this role to work you will need an additional section in the ansible hosts f ansible_host= ``` -Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example: +Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yml` for the host which will have the additional JVB. For example: ```yaml jitsi_jvb_server_id: 'jvb-2' diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index b19c0168d..597acc751 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -39,7 +39,7 @@ To ensure maximum discovery, you can make your identity server also forward look Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding. -To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable matrix.org forwarding, add the following configuration to your `vars.yml` file: ```yaml matrix_ma1sd_matrixorg_forwarding_enabled: true @@ -79,7 +79,7 @@ To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/featu [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. -To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable authentication against an LDAP server, add the following configuration to your `vars.yml` file: ```yaml matrix_synapse_ext_password_provider_rest_auth_enabled: true @@ -150,7 +150,7 @@ If email address validation emails sent by ma1sd are not reaching you, you shoul If you'd like additional logging information, temporarily enable verbose logging for ma1sd. -To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable it, add the following configuration to your `vars.yml` file: ```yaml matrix_ma1sd_verbose_logging: true diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index 71fbc7c5e..45aa1557a 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -123,7 +123,7 @@ By default, this playbook installs the Matrix Authentication Service on the `mat By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix @@ -146,7 +146,7 @@ The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_pro
Click to expand the example configuration: -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml matrix_authentication_service_config_upstream_oauth2_providers: @@ -361,7 +361,7 @@ If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `key The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above). -To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file: ```yaml # Adjust the mapping below to match your provider IDs on the Synapse side and the MAS side. diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index edc8a1ea1..218a32754 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -31,7 +31,7 @@ By default, this playbook installs the matrix-registration on the `matrix.` subd By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index 98eb703c6..50dee4d42 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -34,7 +34,7 @@ By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example. By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index edd4526cb..d44c16aa4 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -38,7 +38,7 @@ By default, this playbook installs Grafana web user-interface on the `stats.` su By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index 8847811ef..ad7057f43 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -32,7 +32,7 @@ By default, this playbook installs rageshake on the `rageshake.` subdomain (`rag By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 2cd9bcca4..e9f936f72 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -20,7 +20,7 @@ By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdo By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-ssl-certificates.md b/docs/configuring-playbook-ssl-certificates.md index 9345544d3..94c4d58c5 100644 --- a/docs/configuring-playbook-ssl-certificates.md +++ b/docs/configuring-playbook-ssl-certificates.md @@ -18,7 +18,7 @@ traefik_config_certificatesResolvers_acme_use_staging: true For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`. -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +Add the following configuration to your `vars.yml` file: ```yaml traefik_config_entrypoint_web_secure_enabled: false diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 10094e9f9..756eb2ee9 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -56,7 +56,7 @@ By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.ex By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Switch to the domain used for Matrix services (`matrix.example.com`), diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index 8c1088d28..c3811521f 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -29,7 +29,7 @@ By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index db6264cb8..81589d9e2 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -31,7 +31,7 @@ By default, this playbook installs synapse-usage-exporter on the `matrix.` subdo By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. -Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file: +Example additional configuration for your `vars.yml` file: ```yaml # Change the default hostname and path prefix diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index dfa9e90ff..6b1ec9f3e 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -108,7 +108,7 @@ If template customization is enabled, the playbook will build a custom container Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run). -To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this: +To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml # If you'd like to ensure that the customized image is built each time the playbook runs, enable this. diff --git a/roles/custom/matrix-conduit/defaults/main.yml b/roles/custom/matrix-conduit/defaults/main.yml index f8f53ba33..e38741f81 100644 --- a/roles/custom/matrix-conduit/defaults/main.yml +++ b/roles/custom/matrix-conduit/defaults/main.yml @@ -113,7 +113,7 @@ matrix_conduit_container_extra_arguments: [] # Specifies which template files to use when configuring Conduit. # If you'd like to have your own different configuration, feel free to copy and paste # the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) -# and then change the specific host's `vars.yaml` file like this: +# and then change the specific host's `vars.yml` file like this: # matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduit.toml.j2" matrix_conduit_template_conduit_config: "{{ role_path }}/templates/conduit.toml.j2" From 37ef7959a935009463cd49c87f62be79a6e98d42 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 13 Jan 2025 15:42:55 +0900 Subject: [PATCH 193/952] Tidy up docs/configuring-playbook-jitsi.md and another related file (#3934) * Update docs/configuring-playbook-jitsi.md: tidy up the introduction Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: minor changes Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: remove the obsolete notice about Element mobile apps not supporting self-hosted Jitsi server The notice has been obsolete since https://github.com/element-hq/element-web/commit/993fd04353cc0a54fe1276a3bbc7b381a7ea1334 (for Android) and https://github.com/element-hq/element-web/commit/0142bb04e41d509d1671c846017c07cc0f50224a (for iOS) Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: create a list for descriptions about each tweak for tuning Jitsi Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: tidy up the section for setting up additional JVBs Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: move down the section for tuning Jitsi Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: include sections to "Adjusting the playbook configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: move the section for confugiring additional JVBs into the 'Usage' section Since the additional JVBs are supposed to be configured after installing Jitsi with a JVB and it is confusing to place the instruction for configuring them (ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start) above the command for installation (ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start), this commit moves the section for configuring the additional JVBs into the "Usage" section. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: tidy up the section for authentication Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: move the note to the section "Troubleshooting" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: tidy up the section for setting up a Gravatar service Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: replace the description about running behind NAT or on a LAN environment with the official one Our original description was unorganized and difficult to understand, so this commit simply replaces it with the official documentation provided by Jitsi, which is clear and straightforward. See: https://github.com/jitsi/handbook/blob/630a6817c2e5e5d5d2843ed7b6cea8afc4fe880f/docs/devops-guide/docker.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: tidy up the section for rebuilding the Jitsi installation It feels like the section is no longer relevant pretty much, as one of the main reasons why rebuilding the installation has seemed to be a difficult but reasonable option would be the quality of our documentation; it has been unorganized and it has been difficult to see what needs to be done in which order. Now that the issue was mostly addressed, perhaps it might make sense to remove the section altogether or move it to FAQ.md and rewrite it for components which are as complex as Jitsi. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: switch the order of instructions about adjusting DNS records and adjusting the URL Since adjusting DNS records does not belong to adjusting the playbook configuration, the section was moved out of it. This is a first trial of placing the instruction about adjusting DNS records above the section for adjusting the URL. Once it is confirmed that this change makes sense, the other instances will be addressed with another commit. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: switch lines for fine tuning Jitsi to remove a blank line Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: add a practical example of configurations Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: remove a duplicated comment inside jitsi_web_custom_config_extension Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: edit the introduction Based on docs/configuring-playbook-etherpad.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: remove a mention about the unmaintained Dimension integration manager As Dimension has been officially declared to be unmaintained and we have stopped recommending to install it since 4574ebbd31888c26dc72a9449e8b6c7427e8bc3f, it is a reasonable choice to remove the explanation which suggests to add a Jitsi widget with the component. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: replace the obsolete details about LastN The document has been removed with https://github.com/jitsi/jitsi-videobridge/commit/9a955ef1b47be3a19832ad79668ea70e1ff1dbf2. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: minor changes Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: move the description about meetings with authentication enabled out of the section for the default authentication method Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-jitsi.md: edit descriptions about authentication methods Based on https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/f6fdb30997717d25e67f63bdc12850c078a6ce1e/defaults/main.yml Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: add an anchor link to the Jitsi docs on `matrix` authentication Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 330 +++++++++++------- ...ring-playbook-user-verification-service.md | 2 +- 2 files changed, 202 insertions(+), 130 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 923addd3d..b8ec2bc7a 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -1,17 +1,23 @@ # Setting up the Jitsi video-conferencing platform (optional) -The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS). +The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you. -Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services. +Jitsi can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app. -The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here. +See the project's [documentation](https://jitsi.github.io/handbook/) to learn what it does and why it might be useful to you. + +**Note**: the configuration by the playbook is similar to the one by [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the official documentation for Docker deployment [here](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/). ## Prerequisites You may need to open the following ports to your server: - `4443/tcp` - RTP media fallback over TCP -- `10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)). +- `10000/udp` - RTP media over UDP. Depending on your firewall/NAT configuration, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)). + +## Adjusting DNS records + +By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. ## Adjusting the playbook configuration @@ -23,8 +29,6 @@ jitsi_enabled: true ### Adjusting the Jitsi URL -By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). - By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one. Example additional configuration for your `vars.yml` file: @@ -34,51 +38,43 @@ Example additional configuration for your `vars.yml` file: jitsi_hostname: call.example.com ``` -## Adjusting DNS records +After changing the domain, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server. -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server. +### Configure Jitsi authentication and guests mode (optional) -By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +By default the Jitsi instance does not require for anyone to log in, and is open to use without an account. To control who is allowed to start meetings on your Jitsi instance, you'd need to enable Jitsi's authentication and optionally guests mode. -## Configure Jitsi authentication and guests mode (optional) +Authentication type must be one of them: `internal` (default), `jwt`, `matrix` or `ldap`. Currently, only `internal`, `matrix` and `ldap` mechanisms are supported by the [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). -By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration. +With authentication enabled, all meetings have to be started by a registered user. After the meeting is started by that user, then guests are free to join. If the registered user is not yet present, the guests are put on hold in individual waiting rooms. -If you're fine with such an open Jitsi instance, please skip to [Installing](#installing). +**Note**: authentication is not tested by the playbook's self-checks. We therefore recommend that you would make sure by yourself that authentication is configured properly. To test it, start a meeting at `jitsi.example.com` on your browser. -If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode. +#### Authenticate using Jitsi accounts: Auth-Type `internal` (recommended) -Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'. +The default authentication mechanism is `internal` auth, which requires a Jitsi account to have been configured. This is a recommended method, as it also works in federated rooms. -**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser. - -### Authenticate using Jitsi accounts (Auth-Type 'internal') - -The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms. - -Add the following configuration to your `vars.yml` file: +To enable authentication with a Jitsi account, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_…` and `PASSWORD_…` with your own values. ```yaml jitsi_enable_auth: true jitsi_enable_guests: true jitsi_prosody_auth_internal_accounts: - - username: "jitsi-moderator" - password: "secret-password" - - username: "another-user" - password: "another-password" + - username: "USERNAME_FOR_THE_FIRST_USER_HERE" + password: "PASSWORD_FOR_THE_FIRST_USER_HERE" + - username: "USERNAME_FOR_THE_SECOND_USER_HERE" + password: "PASSWORD_FOR_THE_SECOND_USER_HERE" ``` -⚠️ **Warning**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook. +**Note**: as Jitsi account removal function is not integrated into the playbook, these accounts will not be able to be removed from the Prosody server automatically, even if they are removed from your `vars.yml` file subsequently. -**If you get an error** like this: "Error: Account creation/modification not supported.", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation). +#### Authenticate using Matrix OpenID: Auth-Type `matrix` -### Authenticate using Matrix OpenID (Auth-Type 'matrix') +⚠️ **Warning**: this breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests. -**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.** +This authentication method requires [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service), which can be installed using this [playbook](configuring-playbook-user-verification-service.md). It verifies against Matrix openID, and requires a user-verification-service to run. -Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md). - -To enable set this configuration at host level: +To enable authentication with Matrix OpenID, add the following configuration to your `vars.yml` file: ```yaml jitsi_enable_auth: true @@ -88,9 +84,9 @@ matrix_user_verification_service_enabled: true For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification). -### Authenticate using LDAP (Auth-Type 'ldap') +#### Authenticate using LDAP: Auth-Type `ldap` -An example LDAP configuration could be: +To enable authentication with LDAP, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml jitsi_enable_auth: true @@ -112,110 +108,210 @@ jitsi_ldap_start_tls: false For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation. -## Making your Jitsi server work on a LAN (optional) +### Configure `JVB_ADVERTISE_IPS` for running behind NAT or on a LAN environment (optional) -By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok. +When running Jitsi in a LAN environment, or on the public Internet via NAT, the `JVB_ADVERTISE_IPS` enviornment variable should be set. -The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work. +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. -To enable it, add the following configuration to your `vars.yml` file: +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. + +To set the variable, add the following configuration to your `vars.yml` file. Make sure to replace `LOCAL_IP_ADDRESS_OF_THE_HOST_HERE` with a proper value. ```yaml jitsi_jvb_container_extra_arguments: - - '--env "JVB_ADVERTISE_IPS="' + - '--env "JVB_ADVERTISE_IPS=LOCAL_IP_ADDRESS_OF_THE_HOST_HERE"' ``` -## Fine tune Jitsi (optional) +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. -If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs): +### Set a maximum number of participants on a Jitsi conference (optional) -```yaml -jitsi_web_custom_config_extension: | - config.enableLayerSuspension = true; +You can set a maximum number of participants allowed to join a Jitsi conference. By default the number is not specified. - config.disableAudioLevels = true; - - // Limit the number of video feeds forwarded to each client - config.channelLastN = 4; - -jitsi_web_config_resolution_width_ideal_and_max: 480 -jitsi_web_config_resolution_height_ideal_and_max: 240 -``` - -You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/) - -You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved. - -You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf). - -You may want to **limit the maximum video resolution**, to save up resources on both server and clients. - -## Specify a Max number of participants on a Jitsi conference (optional) - -The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit. - -In order to set the max number of participants use the following **additional** configuration: +To set it, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml jitsi_prosody_max_participants: 4 # example value ``` -## Additional JVBs (optional) +### Enable Gravatar (optional) -By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts. +In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service. -There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start` +Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our default configuration has disabled the Gravatar service. -For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example: - -```INI -[jitsi_jvb_servers] - ansible_host= -``` - -Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yml` for the host which will have the additional JVB. For example: +To enable the Gravatar service, add the following configuration to your `vars.yml` file: ```yaml -jitsi_jvb_server_id: 'jvb-2' +jitsi_disable_gravatar: false ``` +⚠️ **Warning**: this will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party. + +### Fine tune Jitsi (optional) + +If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +jitsi_web_config_resolution_width_ideal_and_max: 480 +jitsi_web_config_resolution_height_ideal_and_max: 240 +jitsi_web_custom_config_extension: | + config.enableLayerSuspension = true; + + config.disableAudioLevels = true; + + config.channelLastN = 4; +``` + +These configurations: + +- **limit the maximum video resolution**, to save up resources on both server and clients +- **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/). +- **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved +- **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md). + +### Example configurations + +Here is an example set of configurations for running a Jitsi instance with: + +- authentication using a Jitsi account (username: `US3RNAME`, password: `passw0rd`) +- guests: allowed +- maximum participants: 6 people +- fine tuning with the configurations presented above +- other miscellaneous options (see the official Jitsi documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-configuration) and [here](https://jitsi.github.io/handbook/docs/user-guide/user-guide-advanced)) + +```yaml +jitsi_enabled: true +jitsi_enable_auth: true +jitsi_enable_guests: true +jitsi_prosody_auth_internal_accounts: + - username: "US3RNAME" + password: "passw0rd" +jitsi_prosody_max_participants: 6 +jitsi_web_config_resolution_width_ideal_and_max: 480 +jitsi_web_config_resolution_height_ideal_and_max: 240 +jitsi_web_custom_config_extension: | + config.enableLayerSuspension = true; + config.disableAudioLevels = true; + config.channelLastN = 4; + config.requireDisplayName = true; // force users to set a display name + config.startAudioOnly = true; // start the conference in audio only mode (no video is being received nor sent) +``` + +## Installing + +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Usage + +You can use the self-hosted Jitsi server in multiple ways: + +- **by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server. + +- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com` + +### Set up additional JVBs for more video-conferences (optional) + +By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts. + +These settings below will allow you to provision those extra JVB instances. The instances will register themselves with the Prosody service, and be available for Jicofo to route conferences too. + +#### Add the `jitsi_jvb_servers` section on `hosts` file + +For additional JVBs, you'd need to add the section titled `jitsi_jvb_servers` on the ansible `hosts` file with the details of the JVB hosts as below: + ```INI [jitsi_jvb_servers] -jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2 -jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2 +jvb-2.example.com ansible_host=192.168.0.2 ``` -Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host. +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. -The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable: +You could add JVB hosts as many as you would like. When doing so, add lines with the details of them. + +#### Set the server ID to each JVB + +Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB. + +The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container. + +To set the server ID to `jvb-2`, add the following configuration to either `vars.yml` or `hosts` file (adapt to your needs). If you'd specify the server ID on the `hosts` file, add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below. + +- On `vars.yml`: + + ```yaml + jitsi_jvb_server_id: 'jvb-2' + ``` + +- On `hosts`: + + ```INI + [jitsi_jvb_servers] + jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2 + jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2 + ``` + +Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook). + +**Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host. + +#### Set colibri WebSocket port + +The additional JVBs will need to expose the colibri WebSocket port. + +To expose the port, add the following configuration to your `vars.yml` file: ```yaml jitsi_jvb_container_colibri_ws_host_bind_port: 9090 ``` -The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example: +#### Set Prosody XMPP server + +The JVB will also need to know the location of the Prosody XMPP server. + +Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the variable for the JVB by using the variable `jitsi_xmpp_server`. + +##### Set the Matrix domain + +The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` file: ```yaml jitsi_xmpp_server: "{{ matrix_domain }}" ``` -However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example: +##### Set an IP address of the Matrix server + +Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address. + +To set the IP address of the Matrix server, add the following configuration to your `vars.yml` file: ```yaml jitsi_xmpp_server: "192.168.0.1" ``` -For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this: +##### Expose XMPP port + +By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it. + +To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` file: ```yaml jitsi_prosody_container_jvb_host_bind_port: 5222 ``` -(The default is empty; if it's set then docker forwards the port.) +#### Reverse-proxy with Traefik -Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too. - -To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**: +To make Traefik reverse-proxy to these additional JVBs (living on other hosts), add the following configuration to your `vars.yml` file: ```yaml # Traefik proxying for additional JVBs. These can't be configured using Docker @@ -251,55 +347,31 @@ traefik_provider_configuration_extension_yaml: | {% endfor %} ``` -## Enable Gravatar (optional) +#### Run the playbook -In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar. +After configuring `hosts` and `vars.yml` files, run the playbook with [playbook tags](playbook-tags.md) as below: -To enable Gravatar set: - -```yaml -jitsi_disable_gravatar: false -``` - -⚠️ **Warning**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header). - -## Installing - -After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: - - ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start ``` -The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - -`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - -## Usage - -You can use the self-hosted Jitsi server in multiple ways: - -- **by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server. - -- **by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default). - -- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com` - -**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support). - ## Troubleshooting +### `Error: Account creation/modification not supported` + +If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support. + +In this case, you should consider to rebuild your Jitsi installation. + ### Rebuilding your Jitsi installation -**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup. +If you ever run into any trouble or if you have changed configuration (`jitsi_*` variables) too much, you can rebuild your Jitsi installation. -We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own. +We normally don't recommend manual intervention, but Jitsi services tend to generate a lot of configuration files, and it is often wise to start afresh setting the services up, rather than messing with the existing configuration files. Since not all of those files are managed by Ansible (at least not yet), you may sometimes need to delete them by yourself manually. -These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh. +To rebuild your Jitsi configuration, follow the procedure below: -To rebuild your Jitsi configuration: - -- ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi` -- SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`) -- ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`) +- run this command locally to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi` +- log in the server with SSH +- run this command remotely to remove all Jitsi configuration & data: `rm -rf /matrix/jitsi` +- run this command locally to set up Jitsi anew and restart services: `just install-service jitsi` diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 9ff4fa60f..4b62c378b 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -71,7 +71,7 @@ To set your own Token, add the following configuration to your `vars.yml` file: matrix_user_verification_service_uvs_auth_token: "TOKEN" ``` -In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token. +If a Jitsi instance is also managed by this playbook and [`matrix` authentication](configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) is enabled there, this collection will automatically configure Jitsi to use the configured auth token. ### Disable Auth (optional) From de9551a596ffbd763cff03649bde2b8a75e02bac Mon Sep 17 00:00:00 2001 From: adam-kress Date: Mon, 13 Jan 2025 10:34:21 -0500 Subject: [PATCH 194/952] Upgrade Jitsi (v9909-0 -> v9955-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 1fea09d2e..23e0d58bd 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.4.0-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v9909-0 + version: v9955-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-keydb.git version: v6.3.4-3 From a3355423df3fef45990d3b1425dadecf977f24da Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 14 Jan 2025 15:26:52 +0200 Subject: [PATCH 195/952] Upgrade Traefik (v3.2.2-0 -> v3.3.1-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 23e0d58bd..86e7a2111 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,7 +70,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.2.2-0 + version: v3.3.1-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 From 745f04bfa546998c44148511a481b4f1ffaf924b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 14 Jan 2025 16:47:27 +0200 Subject: [PATCH 196/952] Upgrade Element Web (v1.11.89 -> v1.11.90) --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 2216ab3f5..8f4e9cb67 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.89 +matrix_client_element_version: v1.11.90 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" From 01ea98650593cd42c364f43d0dabf5697b2c70ab Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 14 Jan 2025 21:17:26 +0200 Subject: [PATCH 197/952] Upgrade Traefik (v3.3.1-0 -> v3.3.2-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 86e7a2111..2e9815666 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,7 +70,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.1-0 + version: v3.3.2-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 From 5cbd7e7652a83c98d8376a8429cd6fed3a58ce57 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 14 Jan 2025 19:18:15 +0000 Subject: [PATCH 198/952] Update ghcr.io/element-hq/synapse Docker tag to v1.122.0 --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 4cde64955..cc1a6730d 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.121.1 +matrix_synapse_version: v1.122.0 matrix_synapse_username: '' matrix_synapse_uid: '' From 04b32af0c153be3fc69f03a356150fd6d3385775 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 15 Jan 2025 16:22:00 +0900 Subject: [PATCH 199/952] Update docs for DNS settings etc. (#3936) * Update docs for DNS settings of the services which need its CNAME record by default - Buscarron - Go-NEB; fix a line on the instruction as well - wsproxy - Cinny - Element Web - Hydrogen - SchildiChat Web - Dimension - Etherpad - Jitsi - ntfy - Grafana - rageshake - Sygnal Signed-off-by: Suguru Hirahara * Update docs for DNS settings of the services which do not need its CNAME record by default - matrix-alertmanager-receiver - Honoroit - maubot - Heisenbridge - Cactus Comments - Matrix Authentication Service - matrix-registration - Sliding Sync proxy - Synapse Admin - synapse-usage-exporter Signed-off-by: Suguru Hirahara * Update docs for DNS settings: ma1sd Signed-off-by: Suguru Hirahara * Update docs for DNS settings: Email2Matrix Signed-off-by: Suguru Hirahara * Update docs for DNS settings: Postmoogle Remove the table from configuring-dns.md altogether Signed-off-by: Suguru Hirahara * Update docs for Cinny and Dimension: adopt the common note Signed-off-by: Suguru Hirahara * Update docs/configuring-dns.md: add "Note" to the line on using Cloudflare DNS Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-dns.md | 37 +------------------ ...figuring-playbook-alertmanager-receiver.md | 18 ++++----- docs/configuring-playbook-bot-buscarron.md | 16 ++++---- docs/configuring-playbook-bot-go-neb.md | 18 ++++----- docs/configuring-playbook-bot-honoroit.md | 18 ++++----- docs/configuring-playbook-bot-maubot.md | 18 ++++----- ...onfiguring-playbook-bridge-heisenbridge.md | 22 +++++------ ...iguring-playbook-bridge-mautrix-wsproxy.md | 16 ++++---- .../configuring-playbook-bridge-postmoogle.md | 17 +++++++-- docs/configuring-playbook-cactus-comments.md | 18 ++++----- docs/configuring-playbook-client-cinny.md | 23 ++++++------ ...configuring-playbook-client-element-web.md | 22 +++++------ docs/configuring-playbook-client-hydrogen.md | 16 ++++---- ...iguring-playbook-client-schildichat-web.md | 22 +++++------ docs/configuring-playbook-dimension.md | 18 +++++---- docs/configuring-playbook-email2matrix.md | 12 ++++-- docs/configuring-playbook-etherpad.md | 16 ++++---- docs/configuring-playbook-jitsi.md | 6 ++- docs/configuring-playbook-ma1sd.md | 2 + ...-playbook-matrix-authentication-service.md | 22 +++++------ ...onfiguring-playbook-matrix-registration.md | 18 ++++----- docs/configuring-playbook-ntfy.md | 16 ++++---- ...configuring-playbook-prometheus-grafana.md | 16 ++++---- docs/configuring-playbook-rageshake.md | 16 ++++---- ...configuring-playbook-sliding-sync-proxy.md | 18 ++++----- docs/configuring-playbook-sygnal.md | 16 ++++---- docs/configuring-playbook-synapse-admin.md | 18 ++++----- ...iguring-playbook-synapse-usage-exporter.md | 18 ++++----- 28 files changed, 237 insertions(+), 256 deletions(-) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 4d66469e3..5cea036fc 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -36,42 +36,7 @@ The `element.example.com` subdomain is necessary, because this playbook installs Be mindful as to how long it will take for the DNS records to propagate. -If you are using Cloudflare DNS, make sure to disable the proxy and set all records to "DNS only". Otherwise, fetching certificates will fail. - -## DNS settings for optional services/features - -For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly. - -| Used by component | Type | Host | Priority | Weight | Port | Target | -| -------------------------------------------------------------------------------------------------------------------------- | ----- | ------------------------------ | -------- | ------ | ---- | -----------------------------------| -| [Dimension](configuring-playbook-dimension.md) integration server | CNAME | `dimension` | - | - | - | `matrix.example.com` | -| [Jitsi](configuring-playbook-jitsi.md) video-conferencing platform | CNAME | `jitsi` | - | - | - | `matrix.example.com` | -| [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system | CNAME | `stats` | - | - | - | `matrix.example.com` | -| [Go-NEB](configuring-playbook-bot-go-neb.md) bot | CNAME | `goneb` | - | - | - | `matrix.example.com` | -| [Sygnal](configuring-playbook-sygnal.md) push notification gateway | CNAME | `sygnal` | - | - | - | `matrix.example.com` | -| [ntfy](configuring-playbook-ntfy.md) push notifications server | CNAME | `ntfy` | - | - | - | `matrix.example.com` | -| [Etherpad](configuring-playbook-etherpad.md) collaborative text editor | CNAME | `etherpad` | - | - | - | `matrix.example.com` | -| [Hydrogen](configuring-playbook-client-hydrogen.md) web client | CNAME | `hydrogen` | - | - | - | `matrix.example.com` | -| [Cinny](configuring-playbook-client-cinny.md) web client | CNAME | `cinny` | - | - | - | `matrix.example.com` | -| [SchildiChat Web](configuring-playbook-client-schildichat-web.md) client | CNAME | `schildichat` | - | - | - | `matrix.example.com` | -| [wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge | CNAME | `wsproxy` | - | - | - | `matrix.example.com` | -| [Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot | CNAME | `buscarron` | - | - | - | `matrix.example.com` | -| [rageshake](configuring-playbook-rageshake.md) bug report server | CNAME | `rageshake` | - | - | - | `matrix.example.com` | -| [ma1sd](configuring-playbook-ma1sd.md) identity server | SRV | `_matrix-identity._tcp` | 10 | 0 | 443 | `matrix.example.com` | -| [Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges | MX | `matrix` | 10 | 0 | - | `matrix.example.com` | -| [Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge | TXT | `matrix` | - | - | - | `v=spf1 ip4:matrix-server-IP -all` | -| [Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge | TXT | `_dmarc.matrix` | - | - | - | `v=DMARC1; p=quarantine;` | -| [Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge | TXT | `postmoogle._domainkey.matrix` | - | - | - | get it from `!pm dkim` | - -### SRV record for ma1sd - -To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified. - -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`. - -### MX and TXT records for Postmoogle - -To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified. +**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. --------------------------------------------- diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 7a066c293..8a0b8776b 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -36,6 +36,12 @@ For each new room you would like the bot to deliver alerts to, invite the bot to Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out. +## Adjusting DNS records (optional) + +By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-matrix-alertmanager-receiver-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration 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). @@ -61,9 +67,7 @@ matrix_alertmanager_receiver_config_matrix_room_mapping: See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables. -### Adjusting the matrix-alertmanager-receiver URL - -By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the matrix-alertmanager-receiver URL (optional) By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -75,13 +79,9 @@ matrix_alertmanager_receiver_hostname: alertmanager.example.com matrix_alertmanager_receiver_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the matrix-alertmanager-receiver domain (`alertmanager.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 089fd35da..c7ed4f69d 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -4,6 +4,12 @@ The playbook can install and configure [Buscarron](https://github.com/etkecc/bus Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room. +## Adjusting DNS records + +By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -29,9 +35,7 @@ matrix_bot_buscarron_forms: matrix_bot_buscarron_spamlist: [] # (optional) list of emails/domains/hosts (with wildcards support) that should be rejected automatically ``` -### Adjusting the Buscarron URL - -By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Buscarron URL (optional) By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -46,11 +50,7 @@ matrix_bot_buscarron_hostname: "{{ matrix_server_fqn_matrix }}" matrix_bot_buscarron_path_prefix: /buscarron ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server. - -By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 01f86828e..cd6e875cd 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -28,6 +28,12 @@ The bot requires an access token to be able to connect to your homeserver. Refer ⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +## Adjusting DNS records + +By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to create a CNAME record for `goneb`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable 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). @@ -194,9 +200,7 @@ matrix_bot_go_neb_services: msg_type: "m.text" # Must be either `m.text` or `m.notice` ``` -### Adjusting the Go-NEB URL - -By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Go-NEB URL (optional) By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -207,15 +211,11 @@ Example additional configuration for your `vars.yml` file: # so we won't need to add additional DNS records for Go-NEB. matrix_bot_go_neb_hostname: "{{ matrix_server_fqn_matrix }}" -# Expose under the /buscarron subpath +# Expose under the /go-neb subpath matrix_bot_go_neb_path_prefix: /go-neb ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server. - -By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index eed5d70db..d89aa7152 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -6,6 +6,12 @@ It's a bot you can use to setup **your own helpdesk on matrix** See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you. +## Adjusting DNS records (optional) + +By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -23,9 +29,7 @@ matrix_bot_honoroit_password: PASSWORD_FOR_THE_BOT matrix_bot_honoroit_roomid: "!qporfwt:{{ matrix_domain }}" ``` -### Adjusting the Honoroit URL - -By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Honoroit URL (optional) By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -37,13 +41,9 @@ matrix_bot_honoroit_hostname: honoroit.example.com matrix_bot_honoroit_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index a82f5c66e..0436de588 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -6,6 +6,12 @@ After setting up maubot, you can use the web management interface to make it do See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you. +## Adjusting DNS records (optional) + +By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. + +If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -25,9 +31,7 @@ matrix_bot_maubot_admins: You can add multiple admins. The admin accounts are only used to access the maubot administration interface. -### Adjusting the maubot URL - -By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the maubot URL (optional) By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -39,13 +43,9 @@ matrix_bot_maubot_hostname: maubot.example.com matrix_bot_maubot_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Customizing the maubot container image diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index 5e1ae4c27..a464a60f3 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -6,6 +6,12 @@ The playbook can install and configure [Heisenbridge](https://github.com/hifi/he 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). +## Adjusting DNS records (optional) + +By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-heisenbridge-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -21,13 +27,7 @@ matrix_heisenbridge_owner: "@alice:{{ matrix_domain }}" # matrix_heisenbridge_identd_enabled: true ``` -For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role. - -### Adjusting the Heisenbridge URL - -By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)). - -This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Heisenbridge URL (optional) By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -39,13 +39,9 @@ matrix_heisenbridge_hostname: heisenbridge.example.com matrix_heisenbridge_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the Heisenbridge domain (`heisenbridge.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index f9a91af5c..bdc1f3bb2 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -6,6 +6,12 @@ The playbook can install and configure [mautrix-wsproxy](https://github.com/maut See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you. +## Adjusting DNS records + +By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to create a CNAME record for `wsproxy`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -28,9 +34,7 @@ There are some additional things you may wish to configure about the bridge. See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. -### Adjusting the wsproxy URL - -By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the wsproxy URL (optional) By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -41,11 +45,7 @@ Example additional configuration for your `vars.yml` file: matrix_mautrix_wsproxy_hostname: ws.example.com ``` -## Adjusting DNS records - -Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server. - -By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server. ## Installing diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 9622b6919..af52e6acc 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -19,6 +19,19 @@ If you don't open these ports, you will still be able to send emails, but not re These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use. +## Adjusting DNS records + +To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified. + +| Type | Host | Priority | Weight | Port | Target | +|------|--------------------------------|----------|--------|------|------------------------------------| +| MX | `matrix` | 10 | 0 | - | `matrix.example.com` | +| TXT | `matrix` | - | - | - | `v=spf1 ip4:matrix-server-IP -all` | +| TXT | `_dmarc.matrix` | - | - | - | `v=DMARC1; p=quarantine;` | +| TXT | `postmoogle._domainkey.matrix` | - | - | - | get it from `!pm dkim` | + +**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot. + ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -42,10 +55,6 @@ matrix_postmoogle_password: PASSWORD_FOR_THE_BOT # matrix_admin: '@yourAdminAccount:{{ matrix_domain }}' ``` -## Adjusting DNS records - -You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes. - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index a1721eb09..ee5213be9 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -14,6 +14,12 @@ The playbook contains 2 roles for configuring different pieces of the Cactus Com You can enable whichever component you need (typically both). +## Adjusting DNS records (optional) + +By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-cactus-comments-client-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -38,9 +44,7 @@ matrix_cactus_comments_enabled: true matrix_cactus_comments_client_enabled: true ``` -### Adjusting the Cactus Comments' client URL - -By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Cactus Comments' client URL (optional) By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -53,13 +57,9 @@ matrix_cactus_comments_client_hostname: cactus.example.com matrix_cactus_comments_client_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the Cactus Comments' client domain (`cactus.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 0bbf71222..de1bd6324 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -8,6 +8,12 @@ Cinny is a web client focusing primarily on simple, elegant and secure interface - [app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers +## Adjusting DNS records + +By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to create a CNAME record for `cinny`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -16,28 +22,23 @@ To enable Cinny, add the following configuration to your `inventory/host_vars/ma matrix_client_cinny_enabled: true ``` -### Adjusting the Cinny URL - -By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Cinny URL (optional) By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one. -While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. - Example additional configuration for your `vars.yml` file: ```yaml # Switch to a different domain (`app.example.com`) than the default one (`cinny.example.com`) matrix_client_cinny_hostname: "app.{{ matrix_domain }}" + +# Expose under the /cinny subpath +# matrix_client_cinny_path_prefix: /cinny ``` -## Adjusting DNS records +After changing the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server. -Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server. - -By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly. +**Note**: while there is a `matrix_client_cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain. ## Installing diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index d88707b7d..4d832752c 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -9,6 +9,12 @@ If you'd like to stop the playbook installing the client, see the section [below - [app.element.io](https://app.element.io/), hosted by [Element](https://element.io/) - [app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/) +## Adjusting DNS records + +By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to create a CNAME record for `element`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration ### Themes @@ -40,9 +46,7 @@ If you define your own themes with it and set `matrix_client_element_themes_enab If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it. -### Adjusting the Element Web URL - -By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Element Web URL (optional) By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -57,6 +61,10 @@ matrix_client_element_hostname: "{{ matrix_server_fqn_matrix }}" matrix_client_element_path_prefix: /element ``` +After changing the domain, **you may need to adjust your DNS** records to point the Element domain to the Matrix server. + +If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. + ### Extending the configuration There are some additional things you may wish to configure about the component. @@ -84,14 +92,6 @@ matrix_client_element_configuration_extension_json: | } ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server. - -By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. - ## Disabling Element Web If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file: diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index 3166005ae..a2926956d 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -4,6 +4,12 @@ This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen- Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web. +## Adjusting DNS records + +By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to create a CNAME record for `hydrogen`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -12,9 +18,7 @@ To enable Hydrogen, add the following configuration to your `inventory/host_vars matrix_client_hydrogen_enabled: true ``` -### Adjusting the Hydrogen URL - -By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Hydrogen URL (optional) By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -29,11 +33,7 @@ matrix_client_hydrogen_hostname: "{{ matrix_server_fqn_matrix }}" matrix_client_hydrogen_path_prefix: /hydrogen ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server. - -By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 380382937..592809afe 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -8,6 +8,12 @@ SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with - [app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers +## Adjusting DNS records + +By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to create a CNAME record for `schildichat`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -45,9 +51,7 @@ If you define your own themes with it and set `matrix_client_schildichat_themes_ If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it. -### Adjusting the SchildiChat Web URL - -By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the SchildiChat Web URL (optional) By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -62,6 +66,10 @@ matrix_client_schildichat_hostname: "{{ matrix_server_fqn_matrix }}" matrix_client_schildichat_path_prefix: /schildichat ``` +After changing the domain, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server. + +If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. + ### Extending the configuration There are some additional things you may wish to configure about the component. @@ -89,14 +97,6 @@ matrix_client_schildichat_configuration_extension_json: | } ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server. - -By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. - ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index fe742165e..7d1c0ce3f 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -36,6 +36,12 @@ Dimension requires an access token to be able to connect to your homeserver. Ref ⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +## Adjusting DNS records + +By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to create a CNAME record for `dimension`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Dimension, add 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). @@ -58,9 +64,7 @@ matrix_dimension_admins: 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. -### Adjusting the Dimension URL - -By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Dimension URL (optional) By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -75,13 +79,11 @@ matrix_dimension_hostname: "{{ matrix_server_fqn_matrix }}" # matrix_dimension_path_prefix: /dimension ``` -**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain. +After changing the domain, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server. -## Adjusting DNS records +If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server. - -By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +**Note**: while there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You'd need to serve Dimension at a dedicated subdomain. ## Installing diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 02881ac64..d703d5417 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -8,10 +8,6 @@ See the project's [documentation](https://github.com/devture/email2matrix/blob/m ## Preparation -## Adjusting DNS records - -It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page. - ### Port availability Ensure that port 25 is available on your Matrix server and open in your firewall. @@ -54,6 +50,14 @@ Make sure that you and the sender user are part of the same room and that the se 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. +## Adjusting DNS records + +To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this: + +| Type | Host | Priority | Weight | Port | Target | +|------|----------|----------|--------|------|------------------------------------| +| MX | `matrix` | 10 | 0 | - | `matrix.example.com` | + ## Adjusting the playbook configuration 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). diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 99ec8064d..6e32a1a35 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -4,6 +4,12 @@ When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences. +## Adjusting DNS records + +By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -16,9 +22,7 @@ etherpad_enabled: true # etherpad_admin_password: YOUR_PASSWORD_HERE ``` -### Adjusting the Etherpad URL - -By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Etherpad URL (optional) By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -33,11 +37,7 @@ etherpad_hostname: "{{ matrix_server_fqn_matrix }}" etherpad_path_prefix: /etherpad ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server. - -By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index b8ec2bc7a..c5688b375 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -17,7 +17,9 @@ You may need to open the following ports to your server: ## Adjusting DNS records -By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. ## Adjusting the playbook configuration @@ -27,7 +29,7 @@ To enable Jitsi, add the following configuration to your `inventory/host_vars/ma jitsi_enabled: true ``` -### Adjusting the Jitsi URL +### Adjusting the Jitsi URL (optional) By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one. diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 597acc751..c2f9d3132 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -23,6 +23,8 @@ To make the ma1sd Identity Server enable its federation features, set up a SRV r See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record. +When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`. + **Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation. ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index 45aa1557a..eb9ea08b9 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -97,6 +97,12 @@ For existing Synapse homeservers: - then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration +## Adjusting DNS records (optional) + +By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-matrix-authentication-service-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -117,9 +123,7 @@ In the sub-sections that follow, we'll cover some additional configuration optio There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them. -### Adjusting the Matrix Authentication Service URL - -By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Matrix Authentication Service URL (optional) By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -131,6 +135,10 @@ matrix_authentication_service_hostname: auth.example.com matrix_authentication_service_path_prefix: / ``` +If you've changed the default hostname, you may need to create a CNAME record for the Matrix Authentication Service domain (`auth.example.com`), which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ### Marking an existing homeserver for migration The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration. @@ -268,14 +276,6 @@ matrix_authentication_service_config_upstream_oauth2_providers: - go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process - remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration -## Adjusting DNS records - -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. - ## Installing Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 218a32754..fb5e04b31 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -14,6 +14,12 @@ Use matrix-registration to **create unique registration links**, which people ca - **a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration` +## Adjusting DNS records (optional) + +By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-matrix-registration-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -25,9 +31,7 @@ matrix_registration_enabled: true matrix_registration_admin_secret: "ENTER_SOME_SECRET_HERE" ``` -### Adjusting the matrix-registration URL - -By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the matrix-registration URL (optional) By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -39,13 +43,9 @@ matrix_registration_hostname: registration.example.com matrix_registration_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the matrix-registration domain (`registration.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index 50dee4d42..12bc7fc61 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -8,6 +8,12 @@ This role is intended to support UnifiedPush notifications for use with the Matr **Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it. +## Adjusting DNS records + +By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to create a CNAME record for `ntfy`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -28,9 +34,7 @@ For a more complete list of variables that you could override, see the [`default For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options). -### Adjusting the ntfy URL - -By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the ntfy URL (optional) By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -41,11 +45,7 @@ Example additional configuration for your `vars.yml` file: ntfy_hostname: push.example.com ``` -## Adjusting DNS records - -Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server. - -By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server. ## Installing diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d44c16aa4..851fa1635 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -2,6 +2,12 @@ The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you. +## Adjusting DNS records + +By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to create a CNAME record for `stats`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -32,9 +38,7 @@ grafana_default_admin_password: "some_strong_password_chosen_by_you" The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically. -### Adjusting the Grafana URL - -By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Grafana URL (optional) By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -45,11 +49,7 @@ Example additional configuration for your `vars.yml` file: grafana_hostname: grafana.example.com ``` -## Adjusting DNS records - -Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server. - -By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server. **Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index ad7057f43..6db32e43a 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -6,6 +6,12 @@ See the project's [documentation](https://github.com/matrix-org/rageshake/blob/m **Note**: most people don't need to install rageshake to collect bug reports. This component is only useful to people who develop/build their own Matrix client applications themselves. +## Adjusting DNS records + +By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to create a CNAME record for `rageshake`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -26,9 +32,7 @@ matrix_rageshake_configuration_extension_yaml: | my-app: octocat/HelloWorld ``` -### Adjusting the rageshake URL - -By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the rageshake URL (optional) By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -43,11 +47,7 @@ matrix_rageshake_hostname: "{{ matrix_server_fqn_matrix }}" matrix_rageshake_path_prefix: /rageshake ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server. - -By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index e9f936f72..406dc6196 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -6,6 +6,12 @@ The playbook can install and configure [sliding-sync](https://github.com/matrix- 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. +## Adjusting DNS records (optional) + +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. + +If you wish to adjust it, see the section [below](#adjusting-the-sliding-sync-proxy-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -14,9 +20,7 @@ To enable Sliding Sync proxy, add the following configuration to your `inventory matrix_sliding_sync_enabled: true ``` -### Adjusting the Sliding Sync proxy URL - -By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Sliding Sync proxy URL (optional) By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -28,13 +32,9 @@ matrix_sliding_sync_hostname: ss.example.com matrix_sliding_sync_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the Sliding Sync proxy domain (`ss.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 756eb2ee9..8172a17cd 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -10,6 +10,12 @@ See the project's [documentation](https://github.com/matrix-org/sygnal/blob/mast This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves. +## Adjusting DNS records + +By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to create a CNAME record for `sygnal`, which targets `matrix.example.com`. + +When setting, replace `example.com` with your own. + ## Adjusting the playbook configuration To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -50,9 +56,7 @@ To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Noti - references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/…` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container) -### Adjusting the Sygnal URL - -By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records). +### Adjusting the Sygnal URL (optional) By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -67,11 +71,7 @@ matrix_sygnal_hostname: "{{ matrix_server_fqn_matrix }}" matrix_sygnal_path_prefix: /sygnal ``` -## Adjusting DNS records - -Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server. - -By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. +After changing the domain, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server. If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index c3811521f..22635d012 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -6,6 +6,12 @@ synapse-admin is a web UI tool you can use to **administrate users, rooms, media 💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting. +## Adjusting DNS records (optional) + +By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -23,9 +29,7 @@ By default, synapse-admin installation will be [restricted to only work with one ⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all. -### Adjusting the Synapse Admin URL - -By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the Synapse Admin URL (optional) By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -37,13 +41,9 @@ matrix_synapse_admin_hostname: admin.example.com matrix_synapse_admin_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 81589d9e2..e07fc6d0d 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -11,6 +11,12 @@ Enabling this service will automatically: - re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter - add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics +## Adjusting DNS records (optional) + +By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. + +If you wish to adjust it, see the section [below](#adjusting-the-synapse-usage-exporter-url-optional) for details about DNS configuration. + ## Adjusting the playbook configuration To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -25,9 +31,7 @@ matrix_synapse_usage_exporter_enabled: true # matrix_synapse_usage_exporter_proxying_enabled: true ``` -### Adjusting the synapse-usage-exporter URL - -By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. +### Adjusting the synapse-usage-exporter URL (optional) By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -40,13 +44,9 @@ matrix_synapse_usage_exporter_hostname: sue.example.com matrix_synapse_usage_exporter_path_prefix: / ``` -## Adjusting DNS records +If you've changed the default hostname, you may need to create a CNAME record for the synapse-usage-exporter domain (`sue.example.com`), which targets `matrix.example.com`. -If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server. - -See [Configuring DNS](configuring-dns.md) for details about DNS changes. - -If you've decided to use the default hostname, you won't need to do any extra DNS configuration. +When setting, replace `example.com` with your own. ## Installing From 310a5448ced18628c6d36c524be830aac7b203bc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 16 Jan 2025 02:44:23 +0900 Subject: [PATCH 200/952] Update docs/configuring-dns.md: move down the section about DNS setting for optional server delegation Now that the large table for DNS settings is gone, it is sensible to move the section about DNS setting for server delegation down, below the section for DNS configuration for default services. Signed-off-by: Suguru Hirahara --- docs/configuring-dns.md | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 5cea036fc..51e30d69e 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -4,23 +4,6 @@ To set up Matrix on your domain, you'd need to do some DNS configuration. -## DNS setting for server delegation (optional) - -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`. - -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". - -As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways: - -- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`) -- Setting up a `_matrix._tcp` DNS SRV record - -For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record. - -If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services. - -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) - ## DNS settings for services enabled by default 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. @@ -38,6 +21,23 @@ Be mindful as to how long it will take for the DNS records to propagate. **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. +## DNS setting for server delegation (optional) + +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`. + +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". + +As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways: + +- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`) +- Setting up a `_matrix._tcp` DNS SRV record + +For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record. + +If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services. + +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) + --------------------------------------------- [▶️](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). From a4f9bdebcdc0b9b5c98977eac00beb57a4ffc088 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 11 Jan 2025 16:51:38 +0900 Subject: [PATCH 201/952] Update docs: adopt the common instruction Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-client-cinny.md | 2 +- docs/configuring-playbook-client-hydrogen.md | 2 +- docs/configuring-playbook-client-schildichat-web.md | 2 +- docs/configuring-playbook-matrix-authentication-service.md | 2 +- docs/maintenance-checking-services.md | 2 +- docs/maintenance-postgres.md | 2 +- docs/prerequisites.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index fa3d3e555..a6f40897e 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -125,7 +125,7 @@ matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" Draupnir supports two methods to receive reports in the management room. -The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you: +The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, the playbook can set this up for you: ```yaml matrix_bot_draupnir_abuse_reporting_enabled: true diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index de1bd6324..4e9decb4f 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -1,6 +1,6 @@ # Setting up Cinny (optional) -This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you. +The playbook can install and configure the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you. Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md). diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index a2926956d..db44e6a62 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -1,6 +1,6 @@ # Setting up Hydrogen (optional) -This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you. +The playbook can install and configure the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you. Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web. diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 592809afe..e9781255a 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -1,6 +1,6 @@ # Setting up SchildiChat Web (optional) -This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you. +The playbook can install and configure the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you. SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web. diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index eb9ea08b9..616ab54cc 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -1,6 +1,6 @@ # Setting up Matrix Authentication Service (optional) -This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/). +The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/). Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website. diff --git a/docs/maintenance-checking-services.md b/docs/maintenance-checking-services.md index d68502357..b2d90554c 100644 --- a/docs/maintenance-checking-services.md +++ b/docs/maintenance-checking-services.md @@ -1,6 +1,6 @@ # Checking if services work -This playbook can perform a check to ensure that you've configured things correctly and that services are running. +The playbook can perform a check to ensure that you've configured things correctly and that services are running. To perform the check, run: diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index c2b0b3020..82c4757c6 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -76,7 +76,7 @@ Once installed, the playbook attempts to preserve the Postgres version it starts Upgrades must be performed manually. -This playbook can upgrade your existing Postgres setup with the following command: +The playbook can upgrade your existing Postgres setup with the following command: ```sh just run-tags upgrade-postgres diff --git a/docs/prerequisites.md b/docs/prerequisites.md index a574c6352..8fb4b7a4e 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -28,7 +28,7 @@ We will be using `example.com` as the domain in the following instruction. Pleas - **Debian** (10/Buster or newer) - **Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it) - Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there. + Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. The playbook can take over your whole server or co-exist with other services that you have there. This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md). From f2b69feb2942617c770b4d0e5cf2b4fa2acb9788 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 16 Jan 2025 10:13:27 +0200 Subject: [PATCH 202/952] Make catch-all `federation-reader` nginx `location` blocks have less priority than others Potentially fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3918 --- ...ix-synapse-reverse-proxy-companion.conf.j2 | 20 +++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 index f32fe1e27..d278267dc 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 @@ -269,14 +269,12 @@ server { # https://tcpipuk.github.io/synapse/deployment/workers.html {{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_room_worker_federation_locations, 'room_workers_upstream') }} {% endif %} - {% if federation_reader_workers | length > 0 %} - # https://tcpipuk.github.io/synapse/deployment/workers.html - {{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_federation_reader_federation_locations, 'federation_reader_workers_upstream') }} - {% endif %} + {% if generic_workers | length > 0 %} # https://matrix-org.github.io/synapse/latest/workers.html#synapseappgeneric_worker {{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_generic_worker_federation_locations, 'generic_workers_upstream') }} {% endif %} + {% if media_repository_workers | length > 0 %} # https://matrix-org.github.io/synapse/latest/workers.html#synapseappmedia_repository {% for location in matrix_synapse_reverse_proxy_companion_synapse_media_repository_locations %} @@ -298,6 +296,20 @@ server { } {% endfor %} {% endif %} + + {# + This is last, because we'd like more-specific requests (e.g. `/_matrix/federation/v1/media/` that may be handled by a media repository worker, if enabled) + to be routed to more specialized workers via their respective `locations` defined earlier (above). + + As https://nginx.org/en/docs/http/ngx_http_core_module.html#location says about location matching: + > .. Then regular expressions are checked, in the order of their appearance in the configuration file. + + See: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3918 + #} + {% if federation_reader_workers | length > 0 %} + # https://tcpipuk.github.io/synapse/deployment/workers.html + {{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_federation_reader_federation_locations, 'federation_reader_workers_upstream') }} + {% endif %} {% endif %} {% for configuration_block in matrix_synapse_reverse_proxy_companion_synapse_federation_api_additional_server_configuration_blocks %} From 35260cd026b991d21007185372db5fc2d3752ab9 Mon Sep 17 00:00:00 2001 From: Aine <97398200+aine-etke@users.noreply.github.com> Date: Thu, 16 Jan 2025 11:37:07 +0200 Subject: [PATCH 203/952] Synapse Admin v0.10.3-etke36 --- roles/custom/matrix-synapse-admin/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 06767753a..48ccb74c2 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -14,7 +14,7 @@ matrix_synapse_admin_container_image_self_build: false matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git" # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin -matrix_synapse_admin_version: v0.10.3-etke35 +matrix_synapse_admin_version: v0.10.3-etke36 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}" matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}" From f8ff4c55354ee1e3b1d6885edd5755c427ca0fb5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 16 Jan 2025 22:30:30 +0900 Subject: [PATCH 204/952] Update docs/configuring-playbook-backup-borg.md (#3943) * Update docs/configuring-playbook-backup-borg.md: add the section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-backup-borg.md - Move the instruction about setting up the server to the section "Prerequisites" - Replace instructions with a listing with a common format - Adopt the common descripton for setting a strong password - Create sections for optional configurations Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-backup-borg.md: add descriptions about other useful options This commit adds descriptions about options for setting the archive name and the retention policy. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-backup-borg.md: remove the instruction about creating a backup without encryption It is generally not recommended to store unencrypted backups on computers which you do not own, so this commit removes it from the guide. Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 122 +++++++++++++++++------ 1 file changed, 90 insertions(+), 32 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 2f93b0245..ed960f252 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -4,45 +4,65 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. -You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com). - -The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day. - -By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable. - ## Prerequisites -1. If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. +### Set up a remote server for storing backups -2. Create a new SSH key: +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). - ```sh - ssh-keygen -t ed25519 -N '' -f matrix-borg-backup -C matrix - ``` +### Check the Postgres version - This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later. +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. -3. Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server: +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). - If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over: +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. - ```sh - # example to append the new PUBKEY contents, where: - # PUBKEY is path to the public key, - # USER is a ssh user on a provider / server - # HOST is a ssh host of a provider / server - cat PUBKEY | ssh USER@HOST 'dd of=.ssh/authorized_keys oflag=append conv=notrunc' - ``` +### Create a new SSH key + +Run the command below on any machine to create a new SSH key: + +```sh +ssh-keygen -t ed25519 -N '' -f matrix-borg-backup -C matrix +``` + +You don't need to place the key in the `.ssh` folder. + +### Add the public key + +Next, add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server. + +If you are using a hosted solution, follow their instructions. If you have your own server, copy the key to it with the command like below: + +```sh +# Example to append the new PUBKEY contents, where: +# - PUBKEY is path to the public key +# - USER is a ssh user on a provider / server +# - HOST is a ssh host of a provider / server +cat PUBKEY | ssh USER@HOST 'dd of=.ssh/authorized_keys oflag=append conv=notrunc' +``` + +The **private** key needs to be added to `backup_borg_ssh_key_private` on your `inventory/host_vars/matrix.example.com/vars.yml` file as below. ## Adjusting the playbook configuration -Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup: +To enable BorgBackup, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml backup_borg_enabled: true + +# Set the repository location, where: +# - USER is a ssh user on a provider / server +# - HOST is a ssh host of a provider / server +# - REPO is a BorgBackup repository name backup_borg_location_repositories: - ssh://USER@HOST/./REPO + +# Generate a strong password used for encrypting backups. You can create one with a command like `pwgen -s 64 1`. backup_borg_storage_encryption_passphrase: "PASSPHRASE" + +# Add the content of the **private** part of the SSH key you have created. +# Note: the whole key (all of its belonging lines) under the variable needs to be indented with 2 spaces. backup_borg_ssh_key_private: | -----BEGIN OPENSSH PRIVATE KEY----- TG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2NpbmcgZW @@ -53,19 +73,53 @@ backup_borg_ssh_key_private: | -----END OPENSSH PRIVATE KEY----- ``` -where: +**Note**: `REPO` will be initialized on backup start, for example: `matrix`. See [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) for the syntax. -* USER - SSH user of a provider/server -* HOST - SSH host of a provider/server -* REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) -* PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`. -* PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces +### Set backup archive name (optional) -To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable. +You can specify the backup archive name format. To set it, add the following configuration to your `vars.yml` file (adapt to your needs): -`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable. +```yaml +backup_borg_storage_archive_name_format: matrix-{now:%Y-%m-%d-%H%M%S} +``` -Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options. +### Configure retention policy (optional) + +It is also possible to configure a retention strategy. To configure it, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +backup_borg_retention_keep_hourly: 0 +backup_borg_retention_keep_daily: 7 +backup_borg_retention_keep_weekly: 4 +backup_borg_retention_keep_monthly: 12 +backup_borg_retention_keep_yearly: 2 +``` + +### Edit the backup schedule (optional) + +By default the backup will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar. + +To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +backup_borg_schedule: "*-*-* 04:00:00" +``` + +**Note**: the actual job may run with a delay. See `backup_borg_schedule_randomized_delay_sec` [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/f5d5b473d48c6504be10b3d946255ef5c186c2a6/defaults/main.yml#L50) for its default value. + +### Set include and/or exclude directories (optional) + +`backup_borg_location_source_directories` defines the list of directories to back up. It's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. + +You might also want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable. + +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `backup_borg_configuration_extension_yaml` variable ## Installing @@ -82,4 +136,8 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Manually start a backup -For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. +Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration. + +If you want to run the backup immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`. + +This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. From 3a95862a959c886bd73e6a14f1c1e69f6622898b Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 16 Jan 2025 13:31:10 +0000 Subject: [PATCH 205/952] Update dock.mau.dev/mautrix/signal Docker tag to v0.7.5 --- roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index 026b39d2e..b1aecf902 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -9,7 +9,7 @@ matrix_mautrix_signal_container_image_self_build_repo: "https://mau.dev/mautrix/ matrix_mautrix_signal_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_signal_version == 'latest' else matrix_mautrix_signal_version }}" # renovate: datasource=docker depName=dock.mau.dev/mautrix/signal -matrix_mautrix_signal_version: v0.7.4 +matrix_mautrix_signal_version: v0.7.5 # See: https://mau.dev/mautrix/signal/container_registry matrix_mautrix_signal_docker_image: "{{ matrix_mautrix_signal_docker_image_name_prefix }}mautrix/signal:{{ matrix_mautrix_signal_docker_image_tag }}" From 486c55dcaba35b58b6fe28acbd623cd48284e673 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 16 Jan 2025 13:31:15 +0000 Subject: [PATCH 206/952] Update dock.mau.dev/mautrix/twitter Docker tag to v0.2.1 --- roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml index ba13e14cb..8a2fb4200 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml @@ -9,7 +9,7 @@ matrix_mautrix_twitter_container_image_self_build_repo: "https://github.com/maut matrix_mautrix_twitter_container_image_self_build_repo_version: "{{ 'master' if matrix_mautrix_twitter_version == 'latest' else matrix_mautrix_twitter_version }}" # renovate: datasource=docker depName=dock.mau.dev/mautrix/twitter -matrix_mautrix_twitter_version: v0.2.0 +matrix_mautrix_twitter_version: v0.2.1 # See: https://mau.dev/tulir/mautrix-twitter/container_registry matrix_mautrix_twitter_docker_image: "{{ matrix_mautrix_twitter_docker_image_name_prefix }}mautrix/twitter:{{ matrix_mautrix_twitter_version }}" matrix_mautrix_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_twitter_container_image_self_build else 'dock.mau.dev/' }}" From 9ffd40bcd28a7549102440fec1b6fe0adeb5916c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 16 Jan 2025 20:55:01 +0900 Subject: [PATCH 207/952] Remove an obsolete variable: backup_borg_retention_prefix It has been removed with https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/commit/30f0f92dc5e100848b4ec3ba13f0c26439cf62e8 for updating borgmatic to v1.8.2. Signed-off-by: Suguru Hirahara --- group_vars/matrix_servers | 1 - 1 file changed, 1 deletion(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index de7c84d52..607923939 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3199,7 +3199,6 @@ matrix_pantalaimon_homeserver_url: "{{ matrix_addons_homeserver_client_api_url } backup_borg_enabled: false backup_borg_identifier: matrix-backup-borg -backup_borg_retention_prefix: matrix- backup_borg_storage_archive_name_format: matrix-{now:%Y-%m-%d-%H%M%S} backup_borg_base_path: "{{ matrix_base_data_path }}/backup-borg" From 8f08736dde6add3bb2b26707cd94c90b88bea28c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 17 Jan 2025 04:30:33 +0900 Subject: [PATCH 208/952] Update docs: minor changes (#3947) * Update docs/updating-users-passwords.md: use the common placeholder for an access token Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: edit the introduction Based on docs/configuring-playbook-jitsi.md Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 4 +++- docs/updating-users-passwords.md | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 6e32a1a35..2eb839b90 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -1,6 +1,8 @@ # Setting up Etherpad (optional) -[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app. +The playbook can install and configure [Etherpad](https://etherpad.org) for you. + +Etherpad is an open source collaborative text editor. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app. When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences. diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index 91e7d8010..aecd038ef 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -43,5 +43,7 @@ If you didn't make your account a server admin when you created it, you can lear To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command: ```sh -curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@alice:example.com?access_token=MDA...this_is_my_access_token +curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@alice:example.com?access_token=ACCESS_TOKEN_HERE ``` + +Make sure to replace `ACCESS_TOKEN_HERE` with the access token of the server admin account. From 9f4ecb174957dba1f56227cdf20b629aae4e3068 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 16 Jan 2025 19:30:56 +0000 Subject: [PATCH 209/952] Update ghcr.io/t2bot/matrix-media-repo Docker tag to v1.3.8 --- roles/custom/matrix-media-repo/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-media-repo/defaults/main.yml b/roles/custom/matrix-media-repo/defaults/main.yml index b9177cc30..f9fc4eaaf 100755 --- a/roles/custom/matrix-media-repo/defaults/main.yml +++ b/roles/custom/matrix-media-repo/defaults/main.yml @@ -19,7 +19,7 @@ matrix_media_repo_docker_image_path: "t2bot/matrix-media-repo" matrix_media_repo_docker_image: "{{ matrix_media_repo_docker_image_name_prefix }}{{ matrix_media_repo_docker_image_path }}:{{ matrix_media_repo_docker_image_tag }}" matrix_media_repo_docker_image_name_prefix: "{{ 'localhost/' if matrix_media_repo_container_image_self_build else 'ghcr.io/' }}" # renovate: datasource=docker depName=ghcr.io/t2bot/matrix-media-repo -matrix_media_repo_docker_image_tag: "v1.3.7" +matrix_media_repo_docker_image_tag: "v1.3.8" matrix_media_repo_docker_image_force_pull: "{{ matrix_media_repo_docker_image.endswith(':latest') }}" matrix_media_repo_base_path: "{{ matrix_base_data_path }}/{{ matrix_media_repo_identifier }}" From dc0af853614813fdbb3ae75792a867d74a9ea18a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 16 Jan 2025 19:31:01 +0000 Subject: [PATCH 210/952] Update matrixdotorg/dendrite-monolith Docker tag to v0.14.1 --- roles/custom/matrix-dendrite/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml index 2484b6660..f57947252 100644 --- a/roles/custom/matrix-dendrite/defaults/main.yml +++ b/roles/custom/matrix-dendrite/defaults/main.yml @@ -13,7 +13,7 @@ matrix_dendrite_docker_image_path: "matrixdotorg/dendrite-monolith" matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_name_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}" matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else matrix_container_global_registry_prefix }}" # renovate: datasource=docker depName=matrixdotorg/dendrite-monolith -matrix_dendrite_docker_image_tag: "v0.14.0" +matrix_dendrite_docker_image_tag: "v0.14.1" matrix_dendrite_docker_image_force_pull: "{{ matrix_dendrite_docker_image.endswith(':latest') }}" matrix_dendrite_base_path: "{{ matrix_base_data_path }}/dendrite" From 686d9935e25c50034b479db06bed0b39b866ec29 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 17 Jan 2025 11:32:22 +0900 Subject: [PATCH 211/952] Mentions mash-playbook on feature_request.md and faq.md Make one of the list items compact for the new item about mash-playbook Signed-off-by: Suguru Hirahara --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/feature_request.md | 4 +++- docs/faq.md | 8 ++++++++ 3 files changed, 12 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index c20d7abf6..fff721410 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -11,7 +11,7 @@ assignees: '' A clear and concise description of what the bug is. **To Reproduce** diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 1c50f6145..5746ab313 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -13,7 +13,9 @@ A clear and concise description of what the problem is. Ex. I'm always frustrate diff --git a/docs/faq.md b/docs/faq.md index b11a8d0b7..51e093fc7 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -484,3 +484,11 @@ SSL certificates are managed automatically by the [Traefik](https://doc.traefik. If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`). If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way. + +## Miscellaneous + +### I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it? + +You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself. + +Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily. From 2773c053d0f659be7b9e50220a9231d6d3ed4629 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 17 Jan 2025 17:19:17 +0900 Subject: [PATCH 212/952] Update files for coturn (#3953) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update docs/configuring-playbook-turn.md: add a section for description about installing Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-turn.md and a related file - Edit the introducion based on docs/configuring-playbook-client-element-web.md - Adopt the commont format by creating the section "Adjusting the playbook configuration" - Add the section "Extending the configuration" - Move the section "Disabling Coturn" to the bottom Signed-off-by: Suguru Hirahara * Fix capitalization: Coturn → coturn See: https://github.com/coturn/coturn. Note that "coturn" is not capitalized even on the start of a sentence, except some rare cases like on the releases page: https://github.com/coturn/coturn/releases Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- CHANGELOG.md | 38 ++++----- README.md | 2 +- YEAR-IN-REVIEW.md | 2 +- docs/configuring-playbook-turn.md | 79 ++++++++++++------- docs/configuring-playbook.md | 2 +- docs/container-images.md | 2 +- docs/howto-srv-server-delegation.md | 14 ++-- docs/prerequisites.md | 8 +- examples/hosts | 2 +- examples/vars.yml | 4 +- group_vars/matrix_servers | 12 +-- roles/custom/matrix-coturn/defaults/main.yml | 18 ++--- .../matrix-coturn/tasks/setup_install.yml | 12 +-- .../matrix-coturn/tasks/validate_config.yml | 4 +- .../systemd/matrix-coturn.service.j2 | 2 +- 15 files changed, 111 insertions(+), 90 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ea4a530f1..968f32923 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -536,7 +536,7 @@ For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our s To us, `matrix-nginx-proxy` was: - an [nginx](https://nginx.org/)-based reverse-proxy -- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md) +- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [coturn TURN server](./docs/configuring-playbook-turn.md) - a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime - an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services "steal routes" from the homeserver - a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now) @@ -1200,7 +1200,7 @@ Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time. -Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool. +Some services (like [coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool. Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience. @@ -1260,29 +1260,29 @@ Other roles which aren't strictly related to Matrix are likely to follow this fa # 2023-01-26 -## Coturn can now use host-networking +## coturn can now use host-networking -Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown. +Large coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown. -Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this: +Such deployments don't need to run coturn within a private container network anymore. coturn can now run with host-networking by using configuration like this: ```yaml matrix_coturn_container_network: host ``` -With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself. +With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself. -Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network. +Thanks to us [tightening coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network. -## (Backward Compatibility) Tightening Coturn security can lead to connectivity issues +## (Backward Compatibility) Tightening coturn security can lead to connectivity issues -**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it. +**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it. -Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better. +Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better. -If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it. +If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it. -We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people. +We've also added `no-multicast-peers` to the default coturn configuration, but we don't expect this to cause trouble for most people. # 2023-01-21 @@ -2059,9 +2059,9 @@ Additional details are available in [Setting up Heisenbridge bouncer-style IRC b # 2021-04-16 -## Disabling TLSv1 and TLSv1.1 for Coturn +## Disabling TLSv1 and TLSv1.1 for coturn -To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration. +To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [coturn](https://github.com/coturn/coturn) configuration. If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration: @@ -3184,11 +3184,11 @@ We've also started building our own Docker image of Ansible ([devture/ansible](h # 2019-03-19 -## TLS support for Coturn +## TLS support for coturn -We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server. +We've added TLS support to the coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the coturn server. -This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse: +This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's coturn, make sure to rebuild both coturn and Synapse: ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-coturn,setup-synapse,start @@ -3198,9 +3198,9 @@ People who have an extra firewall (besides the iptables firewall, which Docker m People who build their own custom playbook from our roles should be aware that: -- the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates). +- the `matrix-coturn` role and actually starting coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates). -- there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers). +- there are a few variables that can help you enable TLS support for coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers). # 2019-03-12 diff --git a/README.md b/README.md index ba9439dc8..488aab37e 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ Services that run on the server to make the various parts of your installation w | Name | Default? | Description | Documentation | | ---- | -------- | ----------- | ------------- | | [PostgreSQL](https://www.postgresql.org/)| ✅ | Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible. | [Link](docs/configuring-playbook-external-postgres.md) | -| [Coturn](https://github.com/coturn/coturn) | ✅ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) | +| [coturn](https://github.com/coturn/coturn) | ✅ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) | | [Traefik](https://doc.traefik.io/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md) | [Link](docs/configuring-playbook-traefik.md) | | [Let's Encrypt](https://letsencrypt.org/) | ✅ | Free SSL certificate, which secures the connection to all components | [Link](docs/configuring-playbook-ssl-certificates.md) | | [Exim](https://www.exim.org/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | [Link](docs/configuring-playbook-email.md) | diff --git a/YEAR-IN-REVIEW.md b/YEAR-IN-REVIEW.md index cf48fc095..d14602f08 100644 --- a/YEAR-IN-REVIEW.md +++ b/YEAR-IN-REVIEW.md @@ -52,7 +52,7 @@ Hopefully, Synapse defaults would also change the same way and we'd see the numb With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests! -On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports. +On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports. [Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it. diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index f71b84e69..a0915312d 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -1,61 +1,53 @@ -# Adjusting TURN server configuration (optional, advanced) +# Configuring a TURN server (optional, advanced) -The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. +By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document. -By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook. +If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it. -## Disabling Coturn +## Adjusting the playbook configuration -If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +### Define public IP manually (optional) -```yaml -matrix_coturn_enabled: false -``` +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. -In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail. - -## Manually defining your public IP - -In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring Coturn. - -If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server. +If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server. ```yaml matrix_coturn_turn_external_ip_address: "YOUR_PUBLIC_IP" ``` -If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable. +If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable. -If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them: +If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them: ```yaml # Note: matrix_coturn_turn_external_ip_addresses is different than matrix_coturn_turn_external_ip_address matrix_coturn_turn_external_ip_addresses: ['1.2.3.4', '4.5.6.7'] ``` -## Changing the authentication mechanism +### Change the authentication mechanism (optional) The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better. -To do so, add this override to your configuration: +To do so, add the following configuration to your `vars.yml` file: ```yaml matrix_coturn_authentication_method: lt-cred-mech ``` -Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and Coturn. +Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn. -If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method. +If [Jitsi](configuring-playbook-jitsi.md) is installed, note that switching to `lt-cred-mech` will disable the integration between Jitsi and your coturn server, as Jitsi seems to support the `auth-secret` authentication method only. -## Using your own external Coturn server +### Use your own external coturn server (optional) -If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this: +If you'd like to use another TURN server (be it coturn or some other one), add the following configuration to your `vars.yml` file. Make sure to replace `HOSTNAME_OR_IP` with your own. ```yaml -# Disable integrated Coturn server +# Disable integrated coturn server matrix_coturn_enabled: false -# Point Synapse to your other Coturn server +# Point Synapse to your other coturn server matrix_synapse_turn_uris: - turns:HOSTNAME_OR_IP?transport=udp - turns:HOSTNAME_OR_IP?transport=tcp @@ -63,13 +55,42 @@ matrix_synapse_turn_uris: - turn:HOSTNAME_OR_IP?transport=tcp ``` -If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service. +If you have or want to enable Jitsi, you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service. ```yaml jitsi_web_stun_servers: - stun:HOSTNAME_OR_IP:PORT ``` -You can put multiple host/port combinations if you like. -## Further variables and configuration options -To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml +You can put multiple host/port combinations if you'd like to. + +### Extending the configuration + +There are some additional things you may wish to configure about the TURN server. + +Take a look at: + +- `roles/custom/matrix-coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + +## Disabling coturn + +If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file: + +```yaml +matrix_coturn_enabled: false +``` + +In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail. + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 1603da378..2325aea66 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -40,7 +40,7 @@ For a more custom setup, see the [Other configuration options](#other-configurat - Server components: - [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) - - [Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced) + - [Configuring a TURN server](configuring-playbook-turn.md) (advanced) - [Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced) diff --git a/docs/container-images.md b/docs/container-images.md index b893412d6..e2fd67d1a 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -30,7 +30,7 @@ Services that run on the server to make the various parts of your installation w | Service | Container image | Default? | Description | | ------- | --------------- | -------- | ----------- | | [PostgreSQL](configuring-playbook-external-postgres.md) | [postgres](https://hub.docker.com/_/postgres/) | ✅ | Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible. | -| [Coturn](configuring-playbook-turn.md) | [coturn/coturn](https://hub.docker.com/r/coturn/coturn/) | ✅ | STUN/TURN server for WebRTC audio/video calls | +| [coturn](configuring-playbook-turn.md) | [coturn/coturn](https://hub.docker.com/r/coturn/coturn/) | ✅ | STUN/TURN server for WebRTC audio/video calls | | [Traefik](configuring-playbook-traefik.md) | [Traefik](https://hub.docker.com/_/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md) | | [Let's Encrypt](configuring-playbook-ssl-certificates.md) | [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) | ✅ | The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/) | | [Exim](configuring-playbook-email.md) | [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index ba74d38ac..47659d624 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -83,17 +83,17 @@ traefik_environment_variables_additional_variables: | traefik_certResolver_primary: dns ``` -## Adjust Coturn's configuration +## Adjust coturn's configuration -The last step is to alter the generated Coturn configuration. +The last step is to alter the generated coturn configuration. -By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting. +By default, coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent coturn from starting. -We also need to indicate to Coturn where the wildcard certificate is. +We also need to indicate to coturn where the wildcard certificate is. -⚠️ **Warning** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`). +⚠️ **Warning** : On first start of the services, coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the coturn service (`just start-group coturn`). -This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically. +This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the coturn service is setup to restart periodically. ```yaml # Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things @@ -159,7 +159,7 @@ traefik_environment_variables_additional_variables: | CF_DNS_API_TOKEN=redacted LEGO_DISABLE_CNAME_SUPPORT=true -# Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart Coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things +# Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things matrix_coturn_systemd_required_services_list: ['docker.service'] # This changes the path of the loaded certificate, while maintaining the original functionality, we're now loading the wildcard certificate. diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 8fb4b7a4e..3bd3da975 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -48,10 +48,10 @@ We will be using `example.com` as the domain in the following instruction. Pleas - `80/tcp`: HTTP webserver - `443/tcp` and `443/udp`: HTTPS webserver - - `3478/tcp`: TURN over TCP (used by Coturn) - - `3478/udp`: TURN over UDP (used by Coturn) - - `5349/tcp`: TURN over TCP (used by Coturn) - - `5349/udp`: TURN over UDP (used by Coturn) + - `3478/tcp`: TURN over TCP (used by coturn) + - `3478/udp`: TURN over UDP (used by coturn) + - `5349/tcp`: TURN over TCP (used by coturn) + - `5349/udp`: TURN over UDP (used by coturn) - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**. - the range `49152-49172/udp`: TURN over UDP - potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that. diff --git a/examples/hosts b/examples/hosts index d9407b2ab..e4500455d 100644 --- a/examples/hosts +++ b/examples/hosts @@ -1,4 +1,4 @@ -# We explicitly ask for your server's external IP address, because the same value is used for configuring Coturn. +# We explicitly ask for your server's external IP address, because the same value is used for configuring coturn. # If you'd rather use a local IP here, make sure to set up `matrix_coturn_turn_external_ip_address`. # # To connect using a non-root user (and elevate to root with sudo later), diff --git a/examples/vars.yml b/examples/vars.yml index 36b1fb153..ed2c84b21 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -44,7 +44,7 @@ traefik_config_certificatesResolvers_acme_email: '' # using this superuser account. postgres_connection_password: '' -# By default, we configure Coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file. +# By default, we configure coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file. # If this value is an external IP address, you can skip this section. # # If `ansible_host` is not the server's external IP address, you have 2 choices: @@ -52,7 +52,7 @@ postgres_connection_password: '' # 2. Uncomment and adjust the line below to specify an IP address manually # # By default, auto-detection will be attempted using the `https://ifconfig.co/json` API. -# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the Coturn role +# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the coturn role # (see `roles/custom/matrix-coturn/defaults/main.yml`). # # If your server has multiple IP addresses, you may define them in another variable which allows a list of addresses. diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 607923939..7ac246bb6 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -257,12 +257,12 @@ matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_s # - so that addon services (starting later) can communicte with the homeserver via Traefik's internal entrypoint # (see `matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled`) # - core services (the homeserver) get a level of ~1000 -# - services that the homeserver depends on (database, Redis, ntfy, Coturn, etc.) get a lower level - between 500 and 1000 -# - Coturn gets a higher level if `devture_systemd_service_manager_service_restart_mode == 'one-by-one'` to intentionally delay it, because: +# - services that the homeserver depends on (database, Redis, ntfy, coturn, etc.) get a lower level - between 500 and 1000 +# - coturn gets a higher level if `devture_systemd_service_manager_service_restart_mode == 'one-by-one'` to intentionally delay it, because: # - starting services one by one means that the service manager role waits for each service to fully start before proceeding to the next one -# - if Coturn has a lower priority than the homeserver, it would be started before it -# - since Coturn is started before the homeserver, there's no container label telling Traefik to get a `matrix.example.com` certificate -# - thus, Coturn would spin and wait for a certificate until it fails. We'd get a playbook failure due to it, but service manager will proceed to start all other services anyway. +# - if coturn has a lower priority than the homeserver, it would be started before it +# - since coturn is started before the homeserver, there's no container label telling Traefik to get a `matrix.example.com` certificate +# - thus, coturn would spin and wait for a certificate until it fails. We'd get a playbook failure due to it, but service manager will proceed to start all other services anyway. # - only later, when the homeserver actually starts, would that certificate be fetched and dumped # - reverse-proxying services get level 3000 # - Matrix utility services (bridges, bots) get a level of 2000/2200, so that: @@ -3691,7 +3691,7 @@ jitsi_web_stun_servers: | # The Jitsi instance installed by this playbook is meant for embedding into Matrix clients, so framing is allowed. jitsi_web_framing_enabled: true -# Jitsi (Prosody) only seems to support authenticating with Coturn using `auth-secret`, not `lt-cred-mech`. +# Jitsi (Prosody) only seems to support authenticating with coturn using `auth-secret`, not `lt-cred-mech`. # See: https://prosody.im/doc/coturn jitsi_turn_credentials: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" jitsi_turn_host: "{{ ('turn.' + matrix_server_fqn_matrix) if matrix_coturn_enabled else '' }}" diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index edf616129..1b5f1c507 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -14,9 +14,9 @@ matrix_coturn_docker_image: "{{ matrix_coturn_docker_image_name_prefix }}coturn/ matrix_coturn_docker_image_name_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else matrix_container_global_registry_prefix }}" matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith(':latest') }}" -# The Docker network that Coturn would be put into. +# The Docker network that coturn would be put into. # -# Because Coturn relays traffic to unvalidated IP addresses, +# Because coturn relays traffic to unvalidated IP addresses, # using a dedicated network, isolated from other Docker (and local) services is preferrable. # # Setting up deny/allow rules with `matrix_coturn_allowed_peer_ips`/`matrix_coturn_denied_peer_ips` is also @@ -24,7 +24,7 @@ matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith(' # # Setting `matrix_coturn_container_network` to 'host' will run the container with host networking, # which will drastically improve performance when thousands of ports are opened due to Docker not having to set up forwarding rules for each port. -# Running with host networking can be dangerous, as it potentially exposes your local network and its services to Coturn peers. +# Running with host networking can be dangerous, as it potentially exposes your local network and its services to coturn peers. # Regardless of the networking mode, we apply a deny list which via `matrix_coturn_denied_peer_ips`, # which hopefully prevents access to such private network ranges. # When running in host-networking mode, you need to adjust the firewall yourself, so that ports are opened. @@ -51,17 +51,17 @@ matrix_coturn_container_additional_volumes: [] # A list of extra arguments to pass to the container matrix_coturn_container_extra_arguments: [] -# Controls whether the Coturn container exposes its plain STUN port (tcp/3478 and udp/3478 in the container). +# Controls whether the coturn container exposes its plain STUN port (tcp/3478 and udp/3478 in the container). # # Takes an ":" or "" value (e.g. "127.0.0.1:3478"), or empty string to not expose. matrix_coturn_container_stun_plain_host_bind_port: "{{ '3478' if matrix_coturn_container_network != 'host' else '' }}" -# Controls whether the Coturn container exposes its TLS STUN port (tcp/5349 and udp/5349 in the container). +# Controls whether the coturn container exposes its TLS STUN port (tcp/5349 and udp/5349 in the container). # # Takes an ":" or "" value (e.g. "127.0.0.1:5349"), or empty string to not expose. matrix_coturn_container_stun_tls_host_bind_port: "{{ '5349' if matrix_coturn_container_network != 'host' else '' }}" -# Controls whether the Coturn container exposes its TURN UDP port range and which interface to do it on. +# Controls whether the coturn container exposes its TURN UDP port range and which interface to do it on. # # Takes an interface "" (e.g. "127.0.0.1"), or empty string to listen on all interfaces. # Takes a null/none value (`~`) or 'none' (as a string) to prevent listening. @@ -93,7 +93,7 @@ matrix_coturn_lt_cred_mech_username: "" # A password used authentication when `matrix_coturn_authentication_method` is `lt-cred-mech`. matrix_coturn_lt_cred_mech_password: "" -# The external IP address of the machine where Coturn is. +# The external IP address of the machine where coturn is. # If do not define an IP address here or in `matrix_coturn_turn_external_ip_addresses`, auto-detection via an EchoIP service will be done. # See `matrix_coturn_turn_external_ip_address_auto_detection_enabled` matrix_coturn_turn_external_ip_address: '' @@ -117,11 +117,11 @@ matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_retries_del matrix_coturn_allowed_peer_ips: [] # We block loopback interfaces and private networks by default to prevent private resources from being accessible. -# This is especially important when Coturn does not run within a container network (e.g. `matrix_coturn_container_network: host`). +# This is especially important when coturn does not run within a container network (e.g. `matrix_coturn_container_network: host`). # # Learn more: https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/ # -# If you're running Coturn for local network peers, you may wish to override these rules. +# If you're running coturn for local network peers, you may wish to override these rules. matrix_coturn_denied_peer_ips: - 0.0.0.0-0.255.255.255 - 10.0.0.0-10.255.255.255 diff --git a/roles/custom/matrix-coturn/tasks/setup_install.yml b/roles/custom/matrix-coturn/tasks/setup_install.yml index 8ee3d5606..30aa742cd 100644 --- a/roles/custom/matrix-coturn/tasks/setup_install.yml +++ b/roles/custom/matrix-coturn/tasks/setup_install.yml @@ -32,7 +32,7 @@ - ansible.builtin.set_fact: matrix_coturn_turn_external_ip_address: "{{ result_matrix_coturn_turn_external_ip_address_auto_detection_echoip_response.json.ip }}" -- name: Ensure Matrix Coturn path exists +- name: Ensure Matrix coturn path exists ansible.builtin.file: path: "{{ item.path }}" state: directory @@ -43,7 +43,7 @@ - {path: "{{ matrix_coturn_docker_src_files_path }}", when: "{{ matrix_coturn_container_image_self_build }}"} when: "item.when | bool" -- name: Ensure Coturn image is pulled +- name: Ensure coturn image is pulled community.docker.docker_image: name: "{{ matrix_coturn_docker_image }}" source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" @@ -57,7 +57,7 @@ - when: "matrix_coturn_container_image_self_build | bool" block: - - name: Ensure Coturn repository is present on self-build + - name: Ensure coturn repository is present on self-build ansible.builtin.git: repo: "{{ matrix_coturn_container_image_self_build_repo }}" dest: "{{ matrix_coturn_docker_src_files_path }}" @@ -67,7 +67,7 @@ become_user: "{{ matrix_user_username }}" register: matrix_coturn_git_pull_results - - name: Ensure Coturn Docker image is built + - name: Ensure coturn Docker image is built community.docker.docker_image: name: "{{ matrix_coturn_docker_image }}" source: build @@ -78,7 +78,7 @@ path: "{{ matrix_coturn_docker_src_files_path }}" pull: true -- name: Ensure Coturn configuration path exists +- name: Ensure coturn configuration path exists ansible.builtin.file: path: "{{ matrix_coturn_base_path }}" state: directory @@ -94,7 +94,7 @@ owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" -- name: Ensure Coturn network is created in Docker +- name: Ensure coturn network is created in Docker when: matrix_coturn_container_network not in ['', 'host'] community.docker.docker_network: name: "{{ matrix_coturn_container_network }}" diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml index 96205b0e0..7fd26e881 100644 --- a/roles/custom/matrix-coturn/tasks/validate_config.yml +++ b/roles/custom/matrix-coturn/tasks/validate_config.yml @@ -1,6 +1,6 @@ --- -- name: (Deprecation) Catch and report renamed Coturn settings +- name: (Deprecation) Catch and report renamed coturn settings ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -15,7 +15,7 @@ Invalid authentication method specified in `matrix_coturn_authentication_method` when: "matrix_coturn_authentication_method not in ['auth-secret', 'lt-cred-mech']" -- name: Fail if required Coturn settings not defined +- name: Fail if required coturn settings not defined ansible.builtin.fail: msg: >- You need to define a required configuration setting (`{{ item.name }}`). diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 index c72f2bc08..072975b2d 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 @@ -1,6 +1,6 @@ #jinja2: lstrip_blocks: "True" [Unit] -Description=Matrix Coturn server +Description=Matrix coturn server {% for service in matrix_coturn_systemd_required_services_list %} Requires={{ service }} After={{ service }} From d6fda786caf4c800a56347e603bf30e50df634b6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 17 Jan 2025 18:34:58 +0900 Subject: [PATCH 213/952] Update docs/configuring-playbook-etherpad.md (#3954) * Update docs/configuring-playbook-etherpad.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: add the option to configure the default pad text Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: remove the detail about setting the unmaintained Dimension default to the Etherpad instance We have recommended users to avoid installing Dimension since it was deprecated, so it is no longer sensible to discuss how it could be integrated with Etherpad. This commit also removes the known issue section as it describes the issue which can be experienced on Dimension only. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-etherpad.md: minor changes - Update the internal anchor link (follow-up to 04b32af0c153be3fc69f03a356150fd6d3385775) - minor edits Signed-off-by: Suguru Hirahara * Apply the feedback Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 54 +++++++++++++++------------ 1 file changed, 31 insertions(+), 23 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 2eb839b90..65f11b9b4 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -43,6 +43,30 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +### Configure the default text (optional) + +You can also edit the default text on a new pad with the variable `etherpad_default_pad_text`. + +To do so, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +# Note: the whole text (all of its belonging lines) under the variable needs to be indented with 2 spaces. +etherpad_default_pad_text: | + Welcome to Etherpad! + + This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents! + + Get involved with Etherpad at https://etherpad.org +``` + +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- [etherpad role](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `etherpad_configuration_extension_json` variable + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: @@ -66,34 +90,18 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`. -If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage. +If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url-optional) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before using it. ### Managing / Deleting old pads -If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above. +If you want to manage and remove old unused pads from Etherpad, you will first need to create the Etherpad admin user as described above. -Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a "Manage pads" section in the Admin web-UI. +After logging in to the admin web UI, go to the plugin manager page, and install the `adminpads2` plugin. -### How to use Etherpad widgets without an integration manager (like Dimension) +Once the plugin is installed, you should have a "Manage pads" section in the UI. -This is how it works in Element Web, it might work quite similar with other clients: +### Integrating a Etherpad widget in a room + +**Note**: this is how it works in Element Web. It might work quite similar with other clients: To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section. - -### Set Dimension default to the self-hosted Etherpad (optional) - -If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template. - -The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab. - -#### Removing the integrated Etherpad chat - -If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template. - -Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false` - -## Known issues - -If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it. - -`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`. From 107e9d205ddfcdb70e8a2ced35633608ff8e706d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 17 Jan 2025 20:14:41 +0900 Subject: [PATCH 214/952] Edit YAML files: minor changes (#3955) * Update roles/custom/matrix-coturn/defaults/main.yml: edit an instruction for creating a strong password Follow-up to 6b87d1aa7d24ce99578a252317670c80e4891be2 Signed-off-by: Suguru Hirahara * Update examples/vars.yml: add a whitespace character for indenting Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- examples/vars.yml | 2 +- roles/custom/matrix-coturn/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/vars.yml b/examples/vars.yml index ed2c84b21..d4d8066f8 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -12,7 +12,7 @@ matrix_domain: example.com # The Matrix homeserver software to install. # See: # - `roles/custom/matrix-base/defaults/main.yml` for valid options -# - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice +# - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice # # By default, we use Synapse, because it's the only full-featured Matrix server at the moment. # diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index 1b5f1c507..bda15196a 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -85,7 +85,7 @@ matrix_coturn_turn_udp_max_port: 49172 matrix_coturn_authentication_method: auth-secret # A shared secret used for authentication when `matrix_coturn_authentication_method` is `auth-secret`. -# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`). +# You can put any string here, but generating a strong one is preferred. You can create one with a command like `pwgen -s 64 1`. matrix_coturn_turn_static_auth_secret: "" # A username used authentication when `matrix_coturn_authentication_method` is `lt-cred-mech`. From 532d5e21b0a432d3c156bcb9ca18df80ef595e97 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 18 Jan 2025 00:32:56 +0900 Subject: [PATCH 215/952] Update docs/configuring-playbook-appservice-double-puppet.md (#3956) * Update docs/configuring-playbook-appservice-double-puppet.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-appservice-double-puppet.md: introduction and usage The section linked from https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new has been removed. Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...onfiguring-playbook-appservice-double-puppet.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index 0c0f7077e..41967f3fa 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -1,8 +1,8 @@ # Setting up Appservice Double Puppet (optional) -Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver. +The playbook can install and configure the Appservice Double Puppet service for you. It is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver. -This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach. +This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the appservice method. The service is an implementation of this approach. Previously, bridges supported performing double-puppeting 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. @@ -14,6 +14,14 @@ To enable the Appservice Double Puppet service, add the following configuration matrix_appservice_double_puppet_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the service. + +Take a look at: + +- `roles/custom/matrix-appservice-double-puppet/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_double_puppet_registration_configuration_extension_yaml` variable + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -33,4 +41,4 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method. +Installing the service will automatically enable double puppeting for all bridges that support double puppeting via the appservice method. From 99f4af200772b38ed1ba6e9cf853f4c793178ff4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 18 Jan 2025 16:15:04 +0900 Subject: [PATCH 216/952] Update files for Sygnal (#3958) * Rename sygnal.yaml.j2 to config.yaml.j2 There does not seem to exist other yaml.j2 files, which would be named after the servive. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-sygnal.md: add the section "Extending the configuration" Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-sygnal.md | 11 +++++++++-- roles/custom/matrix-sygnal/defaults/main.yml | 2 +- .../templates/{sygnal.yaml.j2 => config.yaml.j2} | 0 3 files changed, 10 insertions(+), 3 deletions(-) rename roles/custom/matrix-sygnal/templates/{sygnal.yaml.j2 => config.yaml.j2} (100%) diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 8172a17cd..7ce58714e 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -46,8 +46,6 @@ aux_file_definitions: group: "{{ matrix_user_groupname }}" ``` -For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample)). - Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values. To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration: @@ -75,6 +73,15 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-sygnal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-sygnal/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_sygnal_configuration_extension_yaml` variable + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: diff --git a/roles/custom/matrix-sygnal/defaults/main.yml b/roles/custom/matrix-sygnal/defaults/main.yml index 4dbd8e505..3f9bc77fc 100644 --- a/roles/custom/matrix-sygnal/defaults/main.yml +++ b/roles/custom/matrix-sygnal/defaults/main.yml @@ -103,7 +103,7 @@ matrix_sygnal_metrics_prometheus_enabled: false # # For a more advanced customization, you can extend the default (see `matrix_sygnal_configuration_extension_yaml`) # or completely replace this variable with your own template. -matrix_sygnal_configuration_yaml: "{{ lookup('template', 'templates/sygnal.yaml.j2') }}" +matrix_sygnal_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" matrix_sygnal_configuration_extension_yaml: | # Your custom YAML configuration for Sygnal goes here. diff --git a/roles/custom/matrix-sygnal/templates/sygnal.yaml.j2 b/roles/custom/matrix-sygnal/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-sygnal/templates/sygnal.yaml.j2 rename to roles/custom/matrix-sygnal/templates/config.yaml.j2 From 58ad1209518f0a6092bf1273259a1785b6f794ef Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 18 Jan 2025 17:25:56 +0900 Subject: [PATCH 217/952] Update docs/configuring-playbook-bot-baibot.md (#3960) * Update docs/configuring-playbook-bot-baibot.md Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-bot-baibot.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 3b6abcedc..0874095d5 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -146,15 +146,13 @@ matrix_bot_baibot_config_agents_static_definitions_anthropic_enabled: true matrix_bot_baibot_config_agents_static_definitions_anthropic_config_api_key: "YOUR_API_KEY_HERE" -# If you'd like to use another text-generation agent, uncomment and adjust: +# Uncomment and adjust this part if you'd like to use another text-generation agent # matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_model_id: claude-3-5-sonnet-20240620 # The playbook defines a default prompt for all statically-defined agents. # You can adjust it in the `matrix_bot_baibot_config_agents_static_definitions_prompt` variable, # or you can adjust it below only for the Anthropic agent. # matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_prompt: "{{ matrix_bot_baibot_config_agents_static_definitions_prompt }}" - -# See `defaults/main.yml` in the baibot role for more configuration options. ``` If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below. @@ -184,8 +182,6 @@ matrix_bot_baibot_config_agents_static_definitions_groq_config_text_generation_m # # matrix_bot_baibot_config_agents_static_definitions_groq_config_speech_to_text_enabled: true # matrix_bot_baibot_config_agents_static_definitions_groq_config_speech_to_text_model_id: whisper-large-v3 - -# See `defaults/main.yml` in the baibot role for more configuration options. ``` Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`. @@ -212,8 +208,6 @@ matrix_bot_baibot_config_agents_static_definitions_mistral_config_api_key: "YOUR # Uncomment and adjust this part if you're not happy with these defaults: # matrix_bot_baibot_config_agents_static_definitions_mistral_config_text_generation_model_id: mistral-large-latest - -# See `defaults/main.yml` in the baibot role for more configuration options. ``` Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`. @@ -242,8 +236,6 @@ matrix_bot_baibot_config_agents_static_definitions_openai_config_api_key: "YOUR_ # If you'd like to use another text-generation agent, uncomment and adjust: # matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_model_id: gpt-4o - -# See `defaults/main.yml` in the baibot role for more configuration options. ``` Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`. @@ -362,6 +354,15 @@ matrix_bot_baibot_config_initial_global_config_handler_image_generation: null **Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands. +### Extending the configuration + +There are some additional things you may wish to configure about the bot. + +Take a look at: + +- `roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 575d98172a7559ba67d94e909c678f9f3e2135fa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 18 Jan 2025 17:09:02 +0900 Subject: [PATCH 218/952] Update docs/configuring-playbook-jitsi.md: add instructions to create vars.yml files for each additional JVB (Jitsi VideoBridge) Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 34 +++++++++++++++++++----------- 1 file changed, 22 insertions(+), 12 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index c5688b375..a6b3cc28f 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -241,28 +241,38 @@ Make sure to replace `jvb-2.example.com` with your hostname for the JVB and `192 You could add JVB hosts as many as you would like. When doing so, add lines with the details of them. +#### Prepare `vars.yml` files for additional JVBs + +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`). + +Note that most (if not all) variables are common for both servers. + +If you are setting up multiple JVB instances, you'd need to create `vars.yml` files for each of them too (`inventory/host_vars/jvb-3.example.com/vars.yml`, for example). + #### Set the server ID to each JVB Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB. The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container. -To set the server ID to `jvb-2`, add the following configuration to either `vars.yml` or `hosts` file (adapt to your needs). If you'd specify the server ID on the `hosts` file, add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below. - -- On `vars.yml`: - - ```yaml - jitsi_jvb_server_id: 'jvb-2' - ``` +To set the server ID to `jvb-2`, add the following configuration to either `hosts` or `vars.yml` files (adapt to your needs). - On `hosts`: + Add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below: + ```INI [jitsi_jvb_servers] jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2 jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2 ``` +- On `vars.yml` files: + + ```yaml + jitsi_jvb_server_id: 'jvb-2' + ``` + Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook). **Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host. @@ -271,7 +281,7 @@ Alternatively, you can specify the variable as a parameter to [the ansible comma The additional JVBs will need to expose the colibri WebSocket port. -To expose the port, add the following configuration to your `vars.yml` file: +To expose the port, add the following configuration to your `vars.yml` files: ```yaml jitsi_jvb_container_colibri_ws_host_bind_port: 9090 @@ -285,7 +295,7 @@ Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the varia ##### Set the Matrix domain -The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` file: +The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` files: ```yaml jitsi_xmpp_server: "{{ matrix_domain }}" @@ -295,7 +305,7 @@ jitsi_xmpp_server: "{{ matrix_domain }}" Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address. -To set the IP address of the Matrix server, add the following configuration to your `vars.yml` file: +To set the IP address of the Matrix server, add the following configuration to your `vars.yml` files: ```yaml jitsi_xmpp_server: "192.168.0.1" @@ -305,7 +315,7 @@ jitsi_xmpp_server: "192.168.0.1" By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it. -To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` file: +To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` files: ```yaml jitsi_prosody_container_jvb_host_bind_port: 5222 @@ -313,7 +323,7 @@ jitsi_prosody_container_jvb_host_bind_port: 5222 #### Reverse-proxy with Traefik -To make Traefik reverse-proxy to these additional JVBs (living on other hosts), add the following configuration to your `vars.yml` file: +To make Traefik reverse-proxy to these additional JVBs, add the following configuration to your main `vars.yml` file (`inventory/host_vars/matrix.example.com/vars.yml`): ```yaml # Traefik proxying for additional JVBs. These can't be configured using Docker From 3a9eb47517b378c90c7fb68062dfe636dcee028b Mon Sep 17 00:00:00 2001 From: Aine Date: Sat, 18 Jan 2025 13:39:28 +0200 Subject: [PATCH 219/952] borgmatic v1.9.6 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 2e9815666..889643e58 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.5-0 + version: v1.4.0-1.9.6-0 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From 41d0fb8c860d94b22de209ba5262212d91827259 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 18 Jan 2025 22:07:38 +0900 Subject: [PATCH 220/952] Move config j2 files out of "config" subfolder for consistency Signed-off-by: Suguru Hirahara --- .../matrix-bot-matrix-registration-bot/tasks/setup_install.yml | 2 +- .../templates/{config => }/config.yml.j2 | 0 roles/custom/matrix-bot-maubot/tasks/setup_install.yml | 2 +- .../matrix-bot-maubot/templates/{config => }/config.yaml.j2 | 0 4 files changed, 2 insertions(+), 2 deletions(-) rename roles/custom/matrix-bot-matrix-registration-bot/templates/{config => }/config.yml.j2 (100%) rename roles/custom/matrix-bot-maubot/templates/{config => }/config.yaml.j2 (100%) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml index 0c3284bc0..0ac4e6a1f 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml @@ -15,7 +15,7 @@ - name: Ensure matrix-registration-bot configuration file created ansible.builtin.template: - src: "{{ role_path }}/templates/config/config.yml.j2" + src: "{{ role_path }}/templates/config.yml.j2" dest: "{{ matrix_bot_matrix_registration_bot_config_path }}/config.yml" owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2 similarity index 100% rename from roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 rename to roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2 diff --git a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml index db2b44778..1c6f17404 100644 --- a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml @@ -20,7 +20,7 @@ - name: Ensure maubot configuration file created ansible.builtin.template: - src: "{{ role_path }}/templates/config/config.yaml.j2" + src: "{{ role_path }}/templates/config.yaml.j2" dest: "{{ matrix_bot_maubot_config_path }}/config.yaml" owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" diff --git a/roles/custom/matrix-bot-maubot/templates/config/config.yaml.j2 b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-bot-maubot/templates/config/config.yaml.j2 rename to roles/custom/matrix-bot-maubot/templates/config.yaml.j2 From f15c0a46be2f9bd4adfdff207f64701560d11b13 Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Sat, 18 Jan 2025 20:25:30 +0100 Subject: [PATCH 221/952] Draupnir 2.0.0 (#3941) * Draupnir 2.0.0 The config getting changes all over the place is because of 2.0 having removed a lot of config options due to the code being removed. * Update Draupnir Documentation to reflect state as of 2.0.0 * Apply Review Feedback Co-authored-by: Suguru Hirahara * Change Room IDs found in code review to not conform to playbook standard. Co-authored-by: Suguru Hirahara * Further Integrate Code Review Feedback * Apply remaining suggestions from code review. Co-authored-by: Suguru Hirahara * Apply Configuration Review Feedback Co-authored-by: Suguru Hirahara * Add Self Registration and Native Login to Draupnir * Rework Draupnir Documentation to Remove Pantalaimon * Set bot.draupnir as default username for the bot in config * Draupnir 2.0.1 * Integrate Review Feedback on Structure of Docs Co-authored-by: Suguru Hirahara * Further Restructure Docs and tweak variables in response. * Only auto-create draupnir user if a password has been set The Draupnir role supports configuring it with either an access token or with a password. When a password is not assigned (which means the access token mode is used), the user is to be created manually. * Add ensure-matrix-users-created tag Now that the Draupnir user may be auto-created in certain configurations (if a password is assigned), it's useful to have the tag there. --------- Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- ...ng-playbook-appservice-draupnir-for-all.md | 12 +- docs/configuring-playbook-bot-draupnir.md | 156 ++++++++---------- group_vars/matrix_servers | 10 ++ .../defaults/main.yml | 2 +- .../templates/production-bots.yaml.j2 | 18 +- .../matrix-bot-draupnir/defaults/main.yml | 28 +++- .../tasks/validate_config.yml | 16 ++ .../templates/production.yaml.j2 | 116 ++++++++----- 8 files changed, 203 insertions(+), 155 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 3a024545a..be7aacc30 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -24,9 +24,7 @@ The playbook does not create a management room for your Main Draupnir. You **nee Note that the room must be unencrypted. - - -The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room. +The management room has to be given an alias, and your bot has to be invited to the room. This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel. @@ -36,8 +34,6 @@ As noted in the Draupnir install instructions the control room is sensitive. **A Next, set an alias to the management room. -This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias. - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`. @@ -80,13 +76,11 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` **Notes**: -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. @@ -103,7 +97,7 @@ Draupnir for all includes several security measures like that it only allows use The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297)) -To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially. +To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially. ### How to provision a D4A once you are allowed to diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index a6f40897e..58c15b1af 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -2,7 +2,7 @@ The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you. -See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you. +See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you. This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead. @@ -10,33 +10,74 @@ If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-on ## Prerequisites -### Register the bot account +### Create a management room -The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot. +Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. -Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. +If you make the management room encrypted (E2EE), then you need to enable the native E2EE support (see [below](#native-e2ee-support)). -You can use the playbook to [register a new user](registering-users.md): +Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. -```sh -ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user +Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that your attempting to invite a user that doesnt have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists. + +## End-to-End Encryption support + +Decide whether you want to support having an Encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled. + +Refer to Draupnir's [Documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more information on why you might or might not care about encryption support for protected rooms. + +**Note**: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. + +### Native E2EE support + +To enable the native E2EE support, you need to obtain an access token for Draupnir. + +Note that native E2EE requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. **The access token obtained via Element Web does not work with it**. Refer to the documentation on [how to obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl). + +To enable the native E2EE support, add the following configuration to your `vars.yml` file: + +```yaml +# Enables the native E2EE Support +matrix_bot_draupnir_enable_experimental_rust_crypto: true + +# Access Token the bot uses to login. +# Comment out `matrix_bot_draupnir_login_native` when using this option. +matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" ``` -If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above. +## Adjusting the playbook configuration -### Obtain an access token +To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. -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). +```yaml +# Enable Draupnir +matrix_bot_draupnir_enabled: true -⚠️ **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. +# Uncomment and adjust this part if you'd like to use a username different than the default +# matrix_bot_draupnir_login: bot.draupnir + +# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`. +# If creating the user on your own and using `matrix_bot_draupnir_access_token` to login you can comment out this line. +matrix_bot_draupnir_password: PASSWORD_FOR_THE_BOT + +# Comment out if using `matrix_bot_draupnir_enable_experimental_rust_crypto: true` or `matrix_bot_draupnir_access_token` to login. +matrix_bot_draupnir_login_native: true + +matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE" +``` + +Before Proceeding run the playbook with the following command to make sure the Draupnir user has been created. +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created +``` ### Make sure the account is free from rate limiting -If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.** +If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a heavily recomended step. If you do not configure it, Draupnir performance will be degraded.** This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. -To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To expose the APIs publicly, add the following configuration to your `vars.yml` file: ```yaml matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true @@ -52,92 +93,33 @@ To discharge rate limiting, run the following command on systems that ship curl curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit ``` -You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token. +### Obtain an access token -### Create a management room +Manual access to Synapse's Admin API requires an access token. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. - -If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). - -Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. - -Finally invite the `@bot.draupnir:example.com` account you created earlier into the room. - -## Adjusting the playbook configuration - -To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. - -```yaml -# Enable Draupnir -matrix_bot_draupnir_enabled: true - -matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE" -``` - -### End-to-End Encryption support - -Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. - -To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md). - -#### Configuration with E2EE support - -When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password. - -Add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -# Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md -matrix_pantalaimon_enabled: true - -# Tell Draupnir to use Pantalaimon -matrix_bot_draupnir_pantalaimon_use: true - -# User name and password for the bot you have created above. Required when using Pantalaimon. -matrix_bot_draupnir_pantalaimon_username: "bot.draupnir" -matrix_bot_draupnir_pantalaimon_password: "PASSWORD_FOR_THE_BOT" -``` - -The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one "raw". This example is taken from the playbook's `group_vars`: - -```yaml -# Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API). -# Set this to the pantalaimon URL if you're using that. -matrix_bot_draupnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matrix_bot_draupnir_pantalaimon_use else matrix_addons_homeserver_client_api_url }}" - -# Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/), -# only set this to the public-internet homeserver client API URL, do NOT set this to the pantalaimon URL. -matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" -``` - -#### Configuration without E2EE support - -When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account. - -Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token). - -```yaml -matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" -``` +⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Abuse Reports -Draupnir supports two methods to receive reports in the management room. +Draupnir can receive reports in the management room. -The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, the playbook can set this up for you: +The bot can intercept the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using Traefik, this playbook can set this up for you: ```yaml matrix_bot_draupnir_abuse_reporting_enabled: true ``` -The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below. + ### Extending the configuration You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable. -For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `vars.yml` file: +For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file: ```yaml matrix_bot_draupnir_configuration_extension_yaml: | @@ -148,13 +130,15 @@ matrix_bot_draupnir_configuration_extension_yaml: | # # If you need something more special, you can take full control by # completely redefining `matrix_bot_draupnir_configuration_yaml`. - pollReports: true + acceptInvitesFromSpace: "!qporfwt:example.com" ``` ### Migrating from Mjolnir (Only required if migrating) Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration. +Note that Pantalaimon is unsupported by Draupnir so it is recommended to consult the instructions to enable [the native E2EE support](#native-e2ee-support). + That is all you need to do due to that Draupnir can complete migration on its own. ## Installing @@ -174,8 +158,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. -- If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password. - ## Usage You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide. @@ -236,7 +218,7 @@ You can also **turn on various built-in [protections](https://the-draupnir-proje To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room. -To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`). +To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`). To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`). diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 7ac246bb6..6da20c467 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -4993,6 +4993,10 @@ matrix_synapse_admin_config_asManagedUsers_auto: | '^@'+(matrix_bot_buscarron_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$', ] if matrix_bot_buscarron_enabled else []) + + ([ + '^@'+(matrix_bot_draupnir_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$', + ] if matrix_bot_draupnir_enabled else []) + + ([ '^@'+(matrix_bot_chatgpt_matrix_bot_username_localpart | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$', ] if matrix_bot_chatgpt_enabled else []) @@ -5855,6 +5859,12 @@ matrix_user_creator_users_auto: | 'initial_password': matrix_bot_maubot_initial_password, 'initial_type': 'bot', }] if matrix_bot_maubot_enabled else []) + + + ([{ + 'username': matrix_bot_draupnir_login, + 'initial_password': matrix_bot_draupnir_password, + 'initial_type': 'bot', + }] if matrix_bot_draupnir_enabled and matrix_bot_draupnir_password else []) }} ###################################################################### diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index a5680809d..0d2a0f575 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -5,7 +5,7 @@ matrix_appservice_draupnir_for_all_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_appservice_draupnir_for_all_version: "1.87.0" +matrix_appservice_draupnir_for_all_version: "v2.0.1" matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 index a40d7a105..46a7b4549 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 +++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 @@ -4,20 +4,10 @@ # This should be at INFO or DEBUG in order to get support for Draupnir problems. logLevel: "INFO" -# Whether or not Draupnir should synchronize policy lists immediately after startup. -# Equivalent to running '!draupnir sync'. -syncOnStartup: true - # Whether or not Draupnir should check moderation permissions in all protected rooms on startup. # Equivalent to running `!draupnir verify`. verifyPermissionsOnStartup: true -# Whether Draupnir should check member lists quicker (by using a different endpoint), -# keep in mind that enabling this will miss invited (but not joined) users. -# -# Turn on if your bot is in (very) large rooms, or in large amounts of rooms. -fasterMembershipChecks: false - # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for. # # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list, @@ -70,14 +60,10 @@ commands: - "draupnir_bot" - "draupnir" - # Whether or not commands with a wildcard (*) will require an additional `--force` argument - # in the command to be able to be submitted. - confirmWildcardBan: true - # The default reasons to be prompted with if the reason is missing from a ban command. ban: - defaultReasons: + defaultReasons: - "spam" - "brigading" - "harassment" - - "disagreement" \ No newline at end of file + - "disagreement" diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index aafdfb129..aa4da34f6 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_draupnir_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_bot_draupnir_version: "v1.87.0" +matrix_bot_draupnir_version: "v2.0.1" matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" @@ -49,8 +49,20 @@ matrix_bot_draupnir_systemd_wanted_services_list: [] # Whether Draupnir should talk to the homeserver through Pantalaimon # If true, then other variables must be provided including pointing # `matrix_bot_draupnir_homeserver_url` to the Pantalaimon URL. +# Enabling this option is discouraged, because Draupnir does not support +# running with Pantalaimon as it would break all workflows that involve answering +# prompts with reactions. (Hint: a lot of workflows rely on them.) matrix_bot_draupnir_pantalaimon_use: false +# If you choose to accept the risks of using Pantalaimon in your installation +# against the upstream advice, you can enable this to disable the warning about it. +matrix_bot_draupnir_pantalaimon_breakage_ignore: false + +# Tells the bot if it should use its native E2EE support in the form of experimental Rust Crypto in the bot SDK. +# This option is mutually exclusive with `matrix_bot_draupnir_pantalaimon_use`. +# Rust Crypto requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. +matrix_bot_draupnir_enable_experimental_rust_crypto: false + # The access token for the bot user. Required when NOT using Pantalaimon. # (Otherwise provide `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` instead.) matrix_bot_draupnir_access_token: "" @@ -60,6 +72,15 @@ matrix_bot_draupnir_access_token: "" matrix_bot_draupnir_pantalaimon_username: "" matrix_bot_draupnir_pantalaimon_password: "" +# Username and password the bot uses for logging in directly. If using Pantalimon +# these values become the values of `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` +matrix_bot_draupnir_login: "{{ matrix_bot_draupnir_pantalaimon_username if matrix_bot_draupnir_pantalaimon_use == 'true' else 'bot.draupnir' }}" +matrix_bot_draupnir_password: "{{ matrix_bot_draupnir_pantalaimon_password }}" + +# Controls if we activate the pantalaimon config block for now. This configuration block is proable to change name for our usecase +# due to a Draupnir push to scrub Pantalaimon from the codebase. +matrix_bot_draupnir_login_native: "" + # The room ID where people can use the bot. The bot has no access controls, so # anyone in this room can use the bot - secure your room! # This should be a room alias or room ID - not a matrix.to URL. @@ -84,6 +105,11 @@ matrix_bot_draupnir_raw_homeserver_url: "" # Its Exposed here because its common enough to be valid to expose. matrix_bot_draupnir_disable_server_acl: "false" +# Controls if the room state backing store is activated. +# Room state backing store makes restarts of the bot lightning fast as the bot does not suffer from amnesia. +# This config option has diminished improvements for bots on extremely fast homeservers or very very small bots on fast homeservers. +matrix_bot_draupnir_enable_room_state_backing_store: "true" + # Default configuration template which covers the generic use case. # You can customize it by controlling the various variables inside it. # diff --git a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml index efc5e7ddc..20acf748d 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml @@ -5,6 +5,7 @@ msg: "The `{{ item.name }}` variable must be defined and have a non-null value." with_items: - {'name': 'matrix_bot_draupnir_access_token', when: "{{ not matrix_bot_draupnir_pantalaimon_use }}"} + - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_enable_experimental_rust_crypto }}"} - {'name': 'matrix_bot_draupnir_management_room', when: true} - {'name': 'matrix_bot_draupnir_container_network', when: true} - {'name': 'matrix_bot_draupnir_homeserver_url', when: true} @@ -18,4 +19,19 @@ msg: "The `{{ item.name }}` variable must be undefined or have a null value." with_items: - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_pantalaimon_use }}"} + - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_login_native }}"} + - {'name': 'matrix_bot_draupnir_pantalaimon_use', when: "{{ matrix_bot_draupnir_enable_experimental_rust_crypto }}"} when: "item.when | bool and not (vars[item.name] == '' or vars[item.name] is none)" + +- when: "matrix_bot_draupnir_pantalaimon_use == 'true' and matrix_bot_draupnir_pantalaimon_breakage_ignore == 'false'" + block: + - name: Inject warning if Pantalaimon is used together with Draupnir + ansible.builtin.set_fact: + devture_playbook_runtime_messages_list: | + {{ + devture_playbook_runtime_messages_list | default([]) + + + [ + "Note: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. To enable E2EE for Draupnir, it is recommended to use matrix_bot_draupnir_enable_experimental_rust_crypto instead. This warning can be disabled by setting matrix_bot_draupnir_pantalaimon_breakage_ignore to true." + ] + }} diff --git a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 index 90df739cb..56b82e322 100644 --- a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 +++ b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 @@ -1,5 +1,4 @@ # Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API), -# set this to the pantalaimon URL if you're using that. homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }} # Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/), @@ -7,29 +6,36 @@ homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }} rawHomeserverUrl: {{ matrix_bot_draupnir_raw_homeserver_url | to_json }} # Matrix Access Token to use, Draupnir will only use this if pantalaimon.use is false. +# This option can be loaded from a file by passing "--access-token-path " at the command line, +# which would allow using secret management systems such as systemd's service credentials. accessToken: {{ matrix_bot_draupnir_access_token | to_json }} -{% if matrix_bot_draupnir_pantalaimon_use %} +{% if matrix_bot_draupnir_pantalaimon_use or matrix_bot_draupnir_login_native %} # Options related to Pantalaimon (https://github.com/matrix-org/pantalaimon) pantalaimon: - # Whether or not Draupnir will use pantalaimon to access the Matrix homeserver, - # set to `true` if you're using pantalaimon. - # - # Be sure to point homeserverUrl to the pantalaimon instance. + # Set to `true` when the bot is to login and fetch the access token on its own. # # Draupnir will log in using the given username and password once, # then store the resulting access token in a file under dataPath. use: true # The username to login with. - username: {{ matrix_bot_draupnir_pantalaimon_username | to_json }} + username: {{ matrix_bot_draupnir_login | to_json }} # The password Draupnir will login with. # # After successfully logging in once, this will be ignored, so this value can be blanked after first startup. - password: {{ matrix_bot_draupnir_pantalaimon_password | to_json }} + # This option can be loaded from a file by passing "--password-path " at the command line, + # which would allow using secret management systems such as systemd's service credentials. + password: {{ matrix_bot_draupnir_password | to_json }} {% endif %} +# Experimental usage of the matrix-bot-sdk rust crypto. This can not be used with Pantalaimon. +# Make sure Pantalaimon is disabled in Draupnir's configuration. +# +# Warning: At this time this is not considered production safe. +experimentalRustCrypto: {{ matrix_bot_draupnir_enable_experimental_rust_crypto | to_json }} + # The path Draupnir will store its state/data in, leave default ("/data/storage") when using containers. dataPath: "/data" @@ -57,7 +63,7 @@ managementRoom: {{ matrix_bot_draupnir_management_room | to_json }} # Running with verboseLogging is unsupported. # Whether Draupnir should log a lot more messages in the room, # mainly involves "all-OK" messages, and debugging messages for when Draupnir checks bans in a room. -#verboseLogging: false +verboseLogging: false # The log level of terminal (or container) output, # can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity. @@ -81,12 +87,6 @@ noop: false # DO NOT change this to `true` unless you are very confident that you know what you are doing. disableServerACL: {{ matrix_bot_draupnir_disable_server_acl | to_json }} -# Whether Draupnir should check member lists quicker (by using a different endpoint), -# keep in mind that enabling this will miss invited (but not joined) users. -# -# Turn on if your bot is in (very) large rooms, or in large amounts of rooms. -fasterMembershipChecks: false - # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for. # # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list, @@ -102,15 +102,6 @@ automaticallyRedactForReasons: - "spam" - "advertising" -# A list of rooms to protect. Draupnir will add this to the list it knows from its account data. -# -# It won't, however, add it to the account data. -# Manually add the room via '!draupnir rooms add' to have it stay protected regardless if this config value changes. -# -# Note: These must be matrix.to URLs -#protectedRooms: -# - "https://matrix.to/#/#matrix:example.org" - # Whether or not to add all joined rooms to the "protected rooms" list # (excluding the management room and watched policy list rooms, see below). # @@ -131,15 +122,18 @@ protectAllJoinedRooms: false # of the homeserver may be more impacted. backgroundDelayMS: 500 +# FIXME: This configuration option is currently broken in the playbook as admin APIs cannot +# be accessed from containers. See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3389 +# and https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3308 # Server administration commands, these commands will only work if Draupnir is # a global server administrator, and the bot's server is a Synapse instance. -admin: - # Whether or not Draupnir can temporarily take control of any eligible account from the local homeserver who's in the room - # (with enough permissions) to "make" a user an admin. - # - # This only works if a local user with enough admin permissions is present in the room. - enableMakeRoomAdminCommand: false - +#admin: +# # Whether or not Draupnir can temporarily take control of any eligible account from the local homeserver who's in the room +# # (with enough permissions) to "make" a user an admin. +# # +# # This only works if a local user with enough admin permissions is present in the room. +# enableMakeRoomAdminCommand: false +# # Misc options for command handling and commands commands: # Whether or not the `!draupnir` prefix is necessary to submit commands. @@ -157,10 +151,6 @@ commands: - "draupnir_bot" - "draupnir" - # Whether or not commands with a wildcard (*) will require an additional `--force` argument - # in the command to be able to be submitted. - confirmWildcardBan: true - # The default reasons to be prompted with if the reason is missing from a ban command. ban: defaultReasons: @@ -178,10 +168,9 @@ commands: # # # # WordList will ban users who use these words when first joining a room, so take caution when selecting them. # # -# # For advanced usage, regex can also be used, see the following links for more information; -# # - https://www.digitalocean.com/community/tutorials/an-introduction-to-regular-expressions -# # - https://regexr.com/ -# # - https://regexone.com/ +# # The word list protection does not support regular expressions at this time. +# # The configuration in the past stated support for Regex erroneously. +# # # words: # - "LoReM" # - "IpSuM" @@ -196,6 +185,31 @@ commands: # # (users will always be banned if they say a bad word) # minutesBeforeTrusting: 20 +# The room state backing store writes a copy of the room state for all protected +# rooms to the data directory. +# It is recommended to enable this option unless you deploy Draupnir close to the +# homeserver and know that Draupnir is starting up quickly. If your homeserver can +# respond quickly to Draupnir's requests for `/state` then you might not need this option. +roomStateBackingStore: + enabled: {{ matrix_bot_draupnir_enable_room_state_backing_store | to_json }} + +# Safe mode provides recovery options for some failure modes when Draupnir +# fails to start. For example, if the bot fails to resolve a room alias in +# a watched list, or if the server has parted from a protected room and can't +# find a way back in. Safe mode will provide different options to recover from +# these. Such as unprotecting the room or unwatching the policy list. +# By default Draupnir will boot into safe mode only when the failure mode +# is recoverable. +# It may be desirable to prevent the bot from starting into safe mode if you have +# a pager system when Draupnir is down, as Draupnir could prevent your monitoring +# system from identifying a failure to start. +#safeMode: +# # The option for entering safe mode when Draupnir fails to start up. +# # - "RecoveryOnly" will only start the bot in safe mode when there are recovery options available. This is the default. +# # - "Never" will never start the bot in safe mode when Draupnir fails to start normally. +# # - "Always" will always start the bot in safe mode when Draupnir fails to start normally. +# bootOption: RecoveryOnly + # Options for advanced monitoring of the health of the bot. health: # healthz options. These options are best for use in container environments @@ -227,6 +241,18 @@ health: # Defaults to 418. unhealthyStatus: 418 + # Sentry options. Sentry is a tool used to receive/collate/triage runtime + # errors and performance issues. Skip this section if you do not wish to use + # Sentry. + sentry: + # The key used to upload Sentry data to the server. + # dsn: "https://XXXXXXXXX@example.com/YYY + + # Frequency of performance monitoring. + # A number in [0.0, 1.0], where 0.0 means "don't bother with tracing" + # and 1.0 means "trace performance at every opportunity". + # tracesSampleRate: 0.5 + {% if matrix_bot_draupnir_web_enabled %} # Options for exposing web APIs. web: @@ -238,7 +264,12 @@ web: # The address to listen for requests on. Defaults to only the current # computer. - address: 0.0.0.0 + address: "0.0.0.0" + + # Alternative setting to open to the entire web. Be careful, + # as this will increase your security perimeter: + # + # address: "0.0.0.0" # A web API designed to intercept Matrix API # POST /_matrix/client/r0/rooms/{roomId}/report/{eventId} @@ -251,10 +282,13 @@ web: enabled: {{ matrix_bot_draupnir_abuse_reporting_enabled | to_json }} {% endif %} +# FIXME: This configuration option is currently broken in the playbook as admin APIs cannot +# be accessed from containers. See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3389 +# and https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3308 # Whether or not to actively poll synapse for abuse reports, to be used # instead of intercepting client calls to synapse's abuse endpoint, when that # isn't possible/practical. -pollReports: false +#pollReports: false # Whether or not new reports, received either by webapi or polling, # should be printed to our managementRoom. From ad3de5737e5b8b12781dd3f2b120524d3fc695a4 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 09:34:11 +0200 Subject: [PATCH 222/952] Add note about Synapse v1.122.0 requiring Postgres v13+ Ref: https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/cc5ac80e9e1a7bda144d768b50345dfc42cc54b5#commitcomment-151503687 --- CHANGELOG.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 968f32923..f2ebae5a4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,14 @@ +# 2025-01-14 + +## (Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13 + +The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034). + +If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file. + +If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup. + + # 2024-11-26 ## (Backward Compatibility Break) Synapse now defaults to enabling authenticated media From 2ad9f37da7aab5ef8466e3d6ab46e58e6968f426 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 09:38:05 +0200 Subject: [PATCH 223/952] Add more changelog notes about Synapse v1.122.0 requiring Postgres v13 --- CHANGELOG.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index f2ebae5a4..ebce4eaaa 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,15 @@ If you've been maintaining your setup for a while and you haven't been doing [Po If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup. +If you're using an external Postgres server (not installed by this playbook), you'll need to figure out how to upgrade it yourself. + +If you're not ready to upgrade your Postgres setup yet, you can temporarily remain on an old Synapse version by adding the following configuration to your `vars.yml` file: + +```yaml +# Pinning to the last Synapse version which supports Postgres v11 and v12. +matrix_synapse_version: v1.121.1 +``` + # 2024-11-26 From 7232d2b6d5f23797db52cbf3f57f7bb822f09fec Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 10:32:07 +0200 Subject: [PATCH 224/952] Pin boto3 and botocore to an old version when installing synapse-s3-storage-provider to prevent issues with non-AWS S3 providers Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3964 Related to https://github.com/aws/aws-cli/issues/9214 --- roles/custom/matrix-synapse/defaults/main.yml | 4 ++++ .../templates/synapse/customizations/Dockerfile.j2 | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index cc1a6730d..b45381c56 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -48,6 +48,10 @@ matrix_synapse_container_image_customizations_enabled: |- # The version that will be installed is specified in `matrix_synapse_ext_synapse_s3_storage_provider_version`. matrix_synapse_container_image_customizations_s3_storage_provider_installation_enabled: "{{ matrix_synapse_ext_synapse_s3_storage_provider_enabled }}" +# Controls whether to install an old version of boto3 and botocore, to work around the following issue: +# https://github.com/aws/aws-cli/issues/9214 +matrix_synapse_container_image_customizations_s3_storage_provider_installation_old_boto_workaround_enabled: true + # Controls whether custom build steps will be added to the Dockerfile for installing auto-accept-invite module. # The version that will be installed is specified in `matrix_synapse_ext_synapse_auto_accept_invite_version`. matrix_synapse_container_image_customizations_auto_accept_invite_installation_enabled: "{{ matrix_synapse_ext_synapse_auto_accept_invite_enabled }}" diff --git a/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2 b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2 index 39367fe09..d01268a4a 100644 --- a/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2 @@ -6,8 +6,12 @@ RUN pip install synapse-auto-accept-invite=={{ matrix_synapse_ext_synapse_auto_a {% endif %} {% if matrix_synapse_container_image_customizations_s3_storage_provider_installation_enabled %} +{% if matrix_synapse_container_image_customizations_s3_storage_provider_installation_old_boto_workaround_enabled %} +RUN pip install 'boto3<1.36.0' 'botocore<1.36.0' synapse-s3-storage-provider=={{ matrix_synapse_ext_synapse_s3_storage_provider_version }} +{% else %} RUN pip install synapse-s3-storage-provider=={{ matrix_synapse_ext_synapse_s3_storage_provider_version }} {% endif %} +{% endif %} {% if matrix_synapse_container_image_customizations_templates_enabled %} {# From b56f1669cf404c18d38279a83ce5e9bcf1ca2d5d Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 19 Jan 2025 08:33:12 +0000 Subject: [PATCH 225/952] Update dependency sphinx-markdown-builder to v0.6.8 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 74c9c078e..b48a508f1 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -21,7 +21,7 @@ setuptools==75.8.0 snowballstemmer==2.2.0 Sphinx==8.1.3 sphinx-intl==2.3.1 -sphinx-markdown-builder==0.6.7 +sphinx-markdown-builder==0.6.8 sphinxcontrib-applehelp==2.0.0 sphinxcontrib-devhelp==2.0.0 sphinxcontrib-htmlhelp==2.1.0 From 96b3cb839263043c58b2e01d78b34ef517183f42 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 15:22:59 +0200 Subject: [PATCH 226/952] Do not auto-add lightning bolt suffix to displayname for newly registered Conduit users This makes it consistent with other homeserver implementations, which do not mess with the displayname by adding suffixes. --- roles/custom/matrix-conduit/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-conduit/defaults/main.yml b/roles/custom/matrix-conduit/defaults/main.yml index e38741f81..247c95751 100644 --- a/roles/custom/matrix-conduit/defaults/main.yml +++ b/roles/custom/matrix-conduit/defaults/main.yml @@ -131,7 +131,7 @@ matrix_conduit_allow_registration: false matrix_conduit_allow_federation: true # Enable the display name lightning bolt on registration. -matrix_conduit_enable_lightning_bolt: true +matrix_conduit_enable_lightning_bolt: false matrix_conduit_trusted_servers: - "matrix.org" From be586f0f30aac7f901b200cb6656ae98580a0c44 Mon Sep 17 00:00:00 2001 From: Virkkunen Date: Sun, 19 Jan 2025 13:19:08 +0100 Subject: [PATCH 227/952] initial conduwuit support --- group_vars/matrix_servers | 66 +++++++- roles/custom/matrix-base/defaults/main.yml | 2 +- .../matrix-base/tasks/validate_config.yml | 2 +- .../custom/matrix-conduwuit/defaults/main.yml | 147 ++++++++++++++++++ roles/custom/matrix-conduwuit/tasks/main.yml | 20 +++ .../matrix-conduwuit/tasks/setup_install.yml | 59 +++++++ .../tasks/setup_uninstall.yml | 19 +++ .../tasks/validate_config.yml | 11 ++ .../templates/conduwuit.toml.j2 | 67 ++++++++ .../matrix-conduwuit/templates/labels.j2 | 134 ++++++++++++++++ .../systemd/matrix-conduwuit.service.j2 | 51 ++++++ roles/custom/matrix-conduwuit/vars/main.yml | 3 + .../util/ensure_user_registered_conduwuit.yml | 5 + .../tasks/validate_config.yml | 8 + setup.yml | 1 + 15 files changed, 592 insertions(+), 3 deletions(-) create mode 100644 roles/custom/matrix-conduwuit/defaults/main.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/main.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/setup_install.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/validate_config.yml create mode 100644 roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 create mode 100644 roles/custom/matrix-conduwuit/templates/labels.j2 create mode 100644 roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 create mode 100644 roles/custom/matrix-conduwuit/vars/main.yml create mode 100644 roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 6da20c467..3a0c9b963 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -232,7 +232,7 @@ matrix_addons_homeserver_client_api_url: "{{ ('http://' + matrix_playbook_revers matrix_addons_homeserver_systemd_services_list: "{{ ([traefik_identifier + '.service'] if matrix_playbook_reverse_proxy_type == 'playbook-managed-traefik' else []) if matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled else matrix_homeserver_systemd_services_list }}" # Starting from version `0.6.0` Conduit natively supports some sync v3 (sliding-sync) features. -matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_sliding_sync_enabled else (matrix_homeserver_url if matrix_homeserver_implementation in ['conduit'] else '') }}" +matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_sliding_sync_enabled else (matrix_homeserver_url if matrix_homeserver_implementation in ['conduit', 'conduwuit'] else '') }}" ######################################################################## # # @@ -553,6 +553,7 @@ matrix_homeserver_container_client_api_endpoint: |- 'synapse': ('matrix-synapse-reverse-proxy-companion:8008' if matrix_synapse_reverse_proxy_companion_enabled | default(false) else ('matrix-synapse:'+ matrix_synapse_container_client_api_port | default('8008') | string)), 'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string), 'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string), + 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_port_number | default('8008') | string), }[matrix_homeserver_implementation] }} @@ -562,6 +563,7 @@ matrix_homeserver_container_federation_api_endpoint: |- 'synapse': ('matrix-synapse-reverse-proxy-companion:8048' if matrix_synapse_reverse_proxy_companion_enabled else ('matrix-synapse:'+ matrix_synapse_container_federation_api_plain_port | default('8008') | string)), 'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string), 'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string), + 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_port_number | default('8008') | string), }[matrix_homeserver_implementation] }} @@ -5503,6 +5505,7 @@ grafana_default_home_dashboard_path: |- 'synapse': ('/etc/grafana/dashboards/synapse.json' if matrix_synapse_metrics_enabled and matrix_synapse_metrics_enabled else ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else '')), 'dendrite': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''), 'conduit': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''), + 'conduwuit': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''), }[matrix_homeserver_implementation] }} @@ -5560,6 +5563,7 @@ matrix_registration_shared_secret: |- 'synapse': matrix_synapse_registration_shared_secret | default (''), 'dendrite': matrix_dendrite_client_api_registration_shared_secret | default (''), 'conduit': '', + 'conduwuit': '', }[matrix_homeserver_implementation] }} @@ -5804,6 +5808,66 @@ matrix_conduit_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix ###################################################################### +###################################################################### +# +# matrix-conduwuit +# +###################################################################### + +matrix_conduwuit_enabled: "{{ matrix_homeserver_implementation == 'conduwuit' }}" + +matrix_conduwuit_hostname: "{{ matrix_server_fqn_matrix }}" + +matrix_conduwuit_allow_federation: "{{ matrix_homeserver_federation_enabled }}" + +matrix_conduwuit_container_network: "{{ matrix_homeserver_container_network }}" + +matrix_conduwuit_container_additional_networks_auto: | + {{ + ( + ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_conduwuit_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network else []) + ) | unique + }} + +matrix_conduwuit_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and not matrix_synapse_workers_enabled }}" +matrix_conduwuit_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" +matrix_conduwuit_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" +matrix_conduwuit_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" + +matrix_conduwuit_container_labels_public_client_root_redirection_enabled: "{{ matrix_conduwuit_container_labels_public_client_root_redirection_url != '' }}" +matrix_conduwuit_container_labels_public_client_root_redirection_url: "{{ (('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element) if matrix_client_element_enabled else '' }}" + +matrix_conduwuit_container_labels_public_federation_api_traefik_hostname: "{{ matrix_server_fqn_matrix_federation }}" +matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints: "{{ matrix_federation_traefik_entrypoint_name }}" +matrix_conduwuit_container_labels_public_federation_api_traefik_tls: "{{ matrix_federation_traefik_entrypoint_tls }}" + +matrix_conduwuit_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}" +matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}" + +matrix_conduwuit_turn_uris: | + {{ + ([ + 'turns:' + matrix_server_fqn_matrix + '?transport=udp', + 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', + ] if matrix_coturn_enabled and matrix_coturn_tls_enabled else []) + + + ([ + 'turn:' + matrix_server_fqn_matrix + '?transport=udp', + 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', + ] if matrix_coturn_enabled else []) + }} + +matrix_conduwuit_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" +matrix_conduwuit_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" +matrix_conduwuit_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" + +###################################################################### +# +# /matrix-conduwuit +# +###################################################################### + + ###################################################################### # # matrix-user-creator diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index a0dd2f04d..e70328a40 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -49,7 +49,7 @@ matrix_monitoring_container_network: matrix-monitoring matrix_homeserver_enabled: true # This will contain the homeserver implementation that is in use. -# Valid values: synapse, dendrite, conduit +# Valid values: synapse, dendrite, conduit, conduwuit # # By default, we use Synapse, because it's the only full-featured Matrix server at the moment. # diff --git a/roles/custom/matrix-base/tasks/validate_config.yml b/roles/custom/matrix-base/tasks/validate_config.yml index fd389cd1c..41320a5fb 100644 --- a/roles/custom/matrix-base/tasks/validate_config.yml +++ b/roles/custom/matrix-base/tasks/validate_config.yml @@ -3,7 +3,7 @@ - name: Fail if invalid homeserver implementation ansible.builtin.fail: msg: "You need to set a valid homeserver implementation in `matrix_homeserver_implementation`" - when: "matrix_homeserver_implementation not in ['synapse', 'dendrite', 'conduit']" + when: "matrix_homeserver_implementation not in ['synapse', 'dendrite', 'conduit', 'conduwuit']" - name: (Deprecation) Catch and report renamed settings ansible.builtin.fail: diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml new file mode 100644 index 000000000..d6cb553d2 --- /dev/null +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -0,0 +1,147 @@ +--- +# Conduwuit is a fork of Conduit, powered by Matrix +# Project source code URL: https://github.com/girlbossceo/conduwuit +# See: https://conduwuit.puppyirl.gay/ + +matrix_conduwuit_enabled: true + +matrix_conduwuit_hostname: '' + +matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_name_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}" +matrix_conduwuit_docker_image_name_prefix: "docker.io/" +# renovate: datasource=docker depName=matrixconduwuit/matrix-conduwuit +matrix_conduwuit_docker_image_tag: "main" +matrix_conduwuit_docker_image_force_pull: "{{ matrix_conduwuit_docker_image.endswith(':latest') }}" + +matrix_conduwuit_base_path: "{{ matrix_base_data_path }}/conduwuit" +matrix_conduwuit_config_path: "{{ matrix_conduwuit_base_path }}/config" +matrix_conduwuit_data_path: "{{ matrix_conduwuit_base_path }}/data" + +matrix_conduwuit_port_number: 6167 + +matrix_conduwuit_tmp_directory_size_mb: 500 + +# List of systemd services that matrix-conduwuit.service depends on +matrix_conduwuit_systemd_required_services_list: "{{ matrix_conduwuit_systemd_required_services_list_default + matrix_conduwuit_systemd_required_services_list_auto + matrix_conduwuit_systemd_required_services_list_custom }}" +matrix_conduwuit_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" +matrix_conduwuit_systemd_required_services_list_auto: [] +matrix_conduwuit_systemd_required_services_list_custom: [] + +# List of systemd services that matrix-conduwuit.service wants +matrix_conduwuit_systemd_wanted_services_list: [] + +# Controls how long to sleep for after starting the matrix-synapse container. +# +# Delaying, so that the homeserver can manage to fully start and various services +# that depend on it (`matrix_conduwuit_systemd_required_services_list` and `matrix_conduwuit_systemd_wanted_services_list`) +# may only start after the homeserver is up and running. +# +# This can be set to 0 to remove the delay. +matrix_conduwuit_systemd_service_post_start_delay_seconds: 3 + +# The base container network. It will be auto-created by this role if it doesn't exist already. +matrix_conduwuit_container_network: "" + +# A list of additional container networks that the container would be connected to. +# The role does not create these networks, so make sure they already exist. +# Use this to expose this container to another reverse proxy, which runs in a different container network. +matrix_conduwuit_container_additional_networks: "{{ matrix_conduwuit_container_additional_networks_auto + matrix_conduwuit_container_additional_networks_custom }}" +matrix_conduwuit_container_additional_networks_auto: [] +matrix_conduwuit_container_additional_networks_custom: [] + +# matrix_conduwuit_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. +# See `../templates/labels.j2` for details. +# +# To inject your own other container labels, see `matrix_conduwuit_container_labels_additional_labels`. +matrix_conduwuit_container_labels_traefik_enabled: true +matrix_conduwuit_container_labels_traefik_docker_network: "{{ matrix_conduwuit_container_network }}" +matrix_conduwuit_container_labels_traefik_entrypoints: web-secure +matrix_conduwuit_container_labels_traefik_tls_certResolver: default # noqa var-naming + +# Controls whether labels will be added for handling the root (/) path on a public Traefik entrypoint. +matrix_conduwuit_container_labels_public_client_root_enabled: true +matrix_conduwuit_container_labels_public_client_root_traefik_hostname: "{{ matrix_conduwuit_hostname }}" +matrix_conduwuit_container_labels_public_client_root_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_client_root_traefik_hostname }}`) && Path(`/`)" +matrix_conduwuit_container_labels_public_client_root_traefik_priority: 0 +matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}" +matrix_conduwuit_container_labels_public_client_root_traefik_tls: "{{ matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints != 'web' }}" +matrix_conduwuit_container_labels_public_client_root_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}" # noqa var-naming +matrix_conduwuit_container_labels_public_client_root_redirection_enabled: false +matrix_conduwuit_container_labels_public_client_root_redirection_url: "" + +# Controls whether labels will be added that expose the Client-Server API on a public Traefik entrypoint. +matrix_conduwuit_container_labels_public_client_api_enabled: true +matrix_conduwuit_container_labels_public_client_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}" +matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix: /_matrix +matrix_conduwuit_container_labels_public_client_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_client_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix }}`)" +matrix_conduwuit_container_labels_public_client_api_traefik_priority: 0 +matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}" +matrix_conduwuit_container_labels_public_client_api_traefik_tls: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints != 'web' }}" +matrix_conduwuit_container_labels_public_client_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}" # noqa var-naming + +# Controls whether labels will be added that expose the Client-Server API on the internal Traefik entrypoint. +# This is similar to `matrix_conduwuit_container_labels_public_client_api_enabled`, but the entrypoint and intent is different. +matrix_conduwuit_container_labels_internal_client_api_enabled: false +matrix_conduwuit_container_labels_internal_client_api_traefik_path_prefix: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix }}" +matrix_conduwuit_container_labels_internal_client_api_traefik_rule: "PathPrefix(`{{ matrix_conduwuit_container_labels_internal_client_api_traefik_path_prefix }}`)" +matrix_conduwuit_container_labels_internal_client_api_traefik_priority: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_priority }}" +matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "" + +# Controls whether labels will be added that expose the Server-Server API (Federation API) on a public Traefik entrypoint. +matrix_conduwuit_container_labels_public_federation_api_enabled: "{{ matrix_conduwuit_allow_federation }}" +matrix_conduwuit_container_labels_public_federation_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}" +matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix: /_matrix +matrix_conduwuit_container_labels_public_federation_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix }}`)" +matrix_conduwuit_container_labels_public_federation_api_traefik_priority: 0 +matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints: '' +# TLS is force-enabled here, because the spec (https://spec.matrix.org/v1.9/server-server-api/#tls) says that the federation API must use HTTPS. +matrix_conduwuit_container_labels_public_federation_api_traefik_tls: true +matrix_conduwuit_container_labels_public_federation_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}" # noqa var-naming + +# matrix_conduwuit_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. +# See `../templates/labels.j2` for details. +# +# Example: +# matrix_conduwuit_container_labels_additional_labels: | +# my.label=1 +# another.label="here" +matrix_conduwuit_container_labels_additional_labels: '' + +# Extra arguments for the Docker container +matrix_conduwuit_container_extra_arguments: [] + +# Specifies which template files to use when configuring conduwuit. +# If you'd like to have your own different configuration, feel free to copy and paste +# the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) +# and then change the specific host's `vars.yml` file like this: +# matrix_conduwuit_template_conduwuit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduwuit.toml.j2" +matrix_conduwuit_template_conduwuit_config: "{{ role_path }}/templates/conduwuit.toml.j2" + +# Max size for uploads, in bytes +matrix_conduwuit_max_request_size: 20_000_000 + +# Maximum number of open files for conduwuit's embedded RocksDB database +# See https://github.com/facebook/rocksdb/wiki/RocksDB-Tuning-Guide#tuning-other-options +# By default, conduwuit uses a relatively low value of 20. +matrix_conduwuit_rocksdb_max_open_files: 64 + +# Enables registration. If set to false, no users can register on this server. +matrix_conduwuit_allow_registration: false + +matrix_conduwuit_allow_federation: true + +# Enable the display name lightning bolt on registration. +matrix_conduwuit_enable_lightning_bolt: true + +matrix_conduwuit_trusted_servers: + - "matrix.org" + +# How many requests conduwuit sends to other servers at the same time +matrix_conduwuit_max_concurrent_requests: 100 + +# TURN integration. +# See: https://gitlab.com/famedly/conduwuit/-/blob/next/TURN.md +matrix_conduwuit_turn_uris: [] +matrix_conduwuit_turn_secret: '' +matrix_conduwuit_turn_username: '' +matrix_conduwuit_turn_password: '' diff --git a/roles/custom/matrix-conduwuit/tasks/main.yml b/roles/custom/matrix-conduwuit/tasks/main.yml new file mode 100644 index 000000000..e6f16d120 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/main.yml @@ -0,0 +1,20 @@ +--- + +- tags: + - setup-all + - setup-conduwuit + - install-all + - install-conduwuit + block: + - when: matrix_conduwuit_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" + + - when: matrix_conduwuit_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" + +- tags: + - setup-all + - setup-conduwuit + block: + - when: not matrix_conduwuit_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" diff --git a/roles/custom/matrix-conduwuit/tasks/setup_install.yml b/roles/custom/matrix-conduwuit/tasks/setup_install.yml new file mode 100644 index 000000000..02b189986 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/setup_install.yml @@ -0,0 +1,59 @@ +--- + +- name: Ensure conduwuit config path exists + ansible.builtin.file: + path: "{{ matrix_conduwuit_config_path }}" + state: directory + mode: 0750 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit data path exists + ansible.builtin.file: + path: "{{ matrix_conduwuit_data_path }}" + state: directory + mode: 0770 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit configuration installed + ansible.builtin.template: + src: "{{ matrix_conduwuit_template_conduwuit_config }}" + dest: "{{ matrix_conduwuit_config_path }}/conduwuit.toml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit support files installed + ansible.builtin.template: + src: "{{ role_path }}/templates/{{ item }}.j2" + dest: "{{ matrix_conduwuit_base_path }}/{{ item }}" + mode: 0640 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - labels + +- name: Ensure conduwuit container network is created + community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" + name: "{{ matrix_conduwuit_container_network }}" + driver: bridge + driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" + +- name: Ensure conduwuit container image is pulled + community.docker.docker_image: + name: "{{ matrix_conduwuit_docker_image }}" + source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" + force_source: "{{ matrix_conduwuit_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_conduwuit_docker_image_force_pull }}" + register: result + retries: "{{ devture_playbook_help_container_retries_count }}" + delay: "{{ devture_playbook_help_container_retries_delay }}" + until: result is not failed + +- name: Ensure matrix-conduwuit.service installed + ansible.builtin.template: + src: "{{ role_path }}/templates/systemd/matrix-conduwuit.service.j2" + dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + mode: 0644 diff --git a/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml new file mode 100644 index 000000000..dcf802b0a --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml @@ -0,0 +1,19 @@ +--- + +- name: Check existence of matrix-conduwuit service + ansible.builtin.stat: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + register: matrix_conduwuit_service_stat + +- when: matrix_conduwuit_service_stat.stat.exists | bool + block: + - name: Ensure matrix-conduwuit is stopped + ansible.builtin.systemd: + name: matrix-conduwuit + state: stopped + daemon_reload: true + + - name: Ensure matrix-conduwuit.service doesn't exist + ansible.builtin.file: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + state: absent diff --git a/roles/custom/matrix-conduwuit/tasks/validate_config.yml b/roles/custom/matrix-conduwuit/tasks/validate_config.yml new file mode 100644 index 000000000..26f3ab100 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/validate_config.yml @@ -0,0 +1,11 @@ +--- + +- name: Fail if required conduwuit settings not defined + ansible.builtin.fail: + msg: >- + You need to define a required configuration setting (`{{ item.name }}`). + when: "item.when | bool and vars[item.name] == ''" + with_items: + - {'name': 'matrix_conduwuit_hostname', when: true} + - {'name': 'matrix_conduwuit_container_network', when: true} + - {'name': 'matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints', when: "{{ matrix_conduwuit_container_labels_internal_client_api_enabled }}"} diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 new file mode 100644 index 000000000..9933c6573 --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 @@ -0,0 +1,67 @@ +# ============================================================================= +# This is the official example config for Conduwuit. +# If you use it for your server, you will need to adjust it to your own needs. +# At the very least, change the server_name field! +# ============================================================================= + + +[global] +# The server_name is the pretty name of this server. It is used as a suffix for user +# and room IDs. Examples: matrix.org, puppyirl.gay + +# The Conduwuit server needs all /_matrix/ requests to be reachable at +# https://example.com/ on port 443 (client-server) and 8448 (federation). + +# If that's not possible for you, you can create /.well-known files to redirect +# requests. See +# https://matrix.org/docs/spec/client_server/latest#get-well-known-matrix-client +# and +# https://matrix.org/docs/spec/server_server/r0.1.4#get-well-known-matrix-server +# for more information + +server_name = "{{ matrix_domain }}" + +# This is the only directory where Conduwuit will save its data +database_path = "/var/lib/matrix-conduwuit/" +database_backend = "rocksdb" + +# The port Conduwuit will be running on. You need to set up a reverse proxy in +# your web server (e.g. apache or nginx), so all requests to /_matrix on port +# 443 and 8448 will be forwarded to the Conduwuit instance running on this port +# Docker users: Don't change this, you'll need to map an external port to this. +port = {{ matrix_conduwuit_port_number }} + +# Max size for uploads +max_request_size = {{ matrix_conduwuit_max_request_size }} + +# Max number of open files for the RocksDB database +rocksdb_max_open_files = {{ matrix_conduwuit_rocksdb_max_open_files }} + +# Enables registration. If set to false, no users can register on this server. +allow_registration = {{ matrix_conduwuit_allow_registration | to_json }} + +allow_federation = {{ matrix_conduwuit_allow_federation | to_json }} + +# Enable the display name lightning bolt on registration. +enable_lightning_bolt = {{ matrix_conduwuit_enable_lightning_bolt | to_json }} + +trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }} + +max_concurrent_requests = {{ matrix_conduwuit_max_concurrent_requests }} + +log = "info,state_res=warn,rocket=off,_=off,sled=off" + +address = "0.0.0.0" + +turn_uris = {{ matrix_conduwuit_turn_uris | to_json }} + +{% if matrix_conduwuit_turn_secret != '' %} +turn_secret = {{ matrix_conduwuit_turn_secret | to_json }} +{% endif %} + +# If you have your TURN server configured to use a username and password +# you can provide these information too. In this case comment out `turn_secret above`! +{% if matrix_conduwuit_turn_username != '' or matrix_conduwuit_turn_password != '' %} +turn_username = {{ matrix_conduwuit_turn_username | to_json }} +turn_password = {{ matrix_conduwuit_turn_password | to_json }} +{% endif %} diff --git a/roles/custom/matrix-conduwuit/templates/labels.j2 b/roles/custom/matrix-conduwuit/templates/labels.j2 new file mode 100644 index 000000000..13ab1487c --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/labels.j2 @@ -0,0 +1,134 @@ +{% if matrix_conduwuit_container_labels_traefik_enabled %} +traefik.enable=true + +{% if matrix_conduwuit_container_labels_traefik_docker_network %} +traefik.docker.network={{ matrix_conduwuit_container_labels_traefik_docker_network }} +{% endif %} + +traefik.http.services.matrix-conduwuit.loadbalancer.server.port={{ matrix_conduwuit_port_number }} + + +{% if matrix_conduwuit_container_labels_public_client_root_enabled %} +############################################################ +# # +# Public Root path (/) # +# # +############################################################ + +{% set client_root_middlewares = [] %} + +{% if matrix_conduwuit_container_labels_public_client_root_redirection_enabled %} +{% set client_root_middlewares = client_root_middlewares + ['matrix-conduwuit-client-root-redirect'] %} +traefik.http.middlewares.matrix-conduwuit-client-root-redirect.redirectregex.regex=(.*) +traefik.http.middlewares.matrix-conduwuit-client-root-redirect.redirectregex.replacement={{ matrix_conduwuit_container_labels_public_client_root_redirection_url }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-public-client-root.rule={{ matrix_conduwuit_container_labels_public_client_root_traefik_rule }} + +traefik.http.routers.matrix-conduwuit-public-client-root.middlewares={{ client_root_middlewares | join(',') }} + +{% if matrix_conduwuit_container_labels_public_client_root_traefik_priority | int > 0 %} +traefik.http.routers.matrix-conduwuit-public-client-root.priority={{ matrix_conduwuit_container_labels_public_client_root_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-public-client-root.service=matrix-conduwuit +traefik.http.routers.matrix-conduwuit-public-client-root.entrypoints={{ matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints }} +traefik.http.routers.matrix-conduwuit-public-client-root.tls={{ matrix_conduwuit_container_labels_public_client_root_traefik_tls | to_json }} + +{% if matrix_conduwuit_container_labels_public_client_root_traefik_tls %} +traefik.http.routers.matrix-conduwuit-public-client-root.tls.certResolver={{ matrix_conduwuit_container_labels_public_client_root_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Public Root path (/) # +# # +############################################################ +{% endif %} + + +{% if matrix_conduwuit_container_labels_public_client_api_enabled %} +############################################################ +# # +# Public Client-API (/_matrix) # +# # +############################################################ + +traefik.http.routers.matrix-conduwuit-public-client-api.rule={{ matrix_conduwuit_container_labels_public_client_api_traefik_rule }} + +{% if matrix_conduwuit_container_labels_public_client_api_traefik_priority | int > 0 %} +traefik.http.routers.matrix-conduwuit-public-client-api.priority={{ matrix_conduwuit_container_labels_public_client_api_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-public-client-api.service=matrix-conduwuit +traefik.http.routers.matrix-conduwuit-public-client-api.entrypoints={{ matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints }} + +traefik.http.routers.matrix-conduwuit-public-client-api.tls={{ matrix_conduwuit_container_labels_public_client_api_traefik_tls | to_json }} +{% if matrix_conduwuit_container_labels_public_client_api_traefik_tls %} +traefik.http.routers.matrix-conduwuit-public-client-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_client_api_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Public Client-API (/_matrix) # +# # +############################################################ +{% endif %} + + +{% if matrix_conduwuit_container_labels_internal_client_api_enabled %} +############################################################ +# # +# Internal Client-API (/_matrix) # +# # +############################################################ + +traefik.http.routers.matrix-conduwuit-internal-client-api.rule={{ matrix_conduwuit_container_labels_internal_client_api_traefik_rule }} + +{% if matrix_conduwuit_container_labels_internal_client_api_traefik_priority | int > 0 %} +traefik.http.routers.matrix-conduwuit-internal-client-api.priority={{ matrix_conduwuit_container_labels_internal_client_api_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-internal-client-api.service=matrix-conduwuit +traefik.http.routers.matrix-conduwuit-internal-client-api.entrypoints={{ matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints }} + +############################################################ +# # +# /Internal Client-API (/_matrix) # +# # +############################################################ +{% endif %} + + +{% if matrix_conduwuit_container_labels_public_federation_api_enabled %} +############################################################ +# # +# Public Federation-API (/_matrix) # +# # +############################################################ + +traefik.http.routers.matrix-conduwuit-public-federation-api.rule={{ matrix_conduwuit_container_labels_public_federation_api_traefik_rule }} + +{% if matrix_conduwuit_container_labels_public_federation_api_traefik_priority | int > 0 %} +traefik.http.routers.matrix-conduwuit-public-federation-api.priority={{ matrix_conduwuit_container_labels_public_federation_api_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-public-federation-api.service=matrix-conduwuit +traefik.http.routers.matrix-conduwuit-public-federation-api.entrypoints={{ matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints }} + +traefik.http.routers.matrix-conduwuit-public-federation-api.tls={{ matrix_conduwuit_container_labels_public_federation_api_traefik_tls | to_json }} +{% if matrix_conduwuit_container_labels_public_federation_api_traefik_tls %} +traefik.http.routers.matrix-conduwuit-public-federation-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_federation_api_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Public Federation-API (/_matrix) # +# # +############################################################ +{% endif %} + + +{% endif %} + +{{ matrix_conduwuit_container_labels_additional_labels }} diff --git a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 new file mode 100644 index 000000000..54b5cc7a5 --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 @@ -0,0 +1,51 @@ +#jinja2: lstrip_blocks: "True" +[Unit] +Description=Conduwuit Matrix homeserver +{% for service in matrix_conduwuit_systemd_required_services_list %} +Requires={{ service }} +After={{ service }} +{% endfor %} + +[Service] +Type=simple +Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true' + +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ + --rm \ + --name=matrix-conduwuit \ + --log-driver=none \ + --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ + --cap-drop=ALL \ + --read-only \ + --tmpfs=/tmp:rw,noexec,nosuid,size={{ matrix_conduwuit_tmp_directory_size_mb }}m \ + --network={{ matrix_conduwuit_container_network }} \ + --env conduwuit_CONFIG=/etc/matrix-conduwuit/conduwuit.toml \ + --label-file={{ matrix_conduwuit_base_path }}/labels \ + --mount type=bind,src={{ matrix_conduwuit_data_path }},dst=/var/lib/matrix-conduwuit \ + --mount type=bind,src={{ matrix_conduwuit_config_path }},dst=/etc/matrix-conduwuit,ro \ + {% for arg in matrix_conduwuit_container_extra_arguments %} + {{ arg }} \ + {% endfor %} + {{ matrix_conduwuit_docker_image }} + +{% for network in matrix_conduwuit_container_additional_networks %} +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-conduwuit +{% endfor %} + +ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-conduwuit + +{% if matrix_conduwuit_systemd_service_post_start_delay_seconds != 0 %} +ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_conduwuit_systemd_service_post_start_delay_seconds }} +{% endif %} + +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true' +ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-conduwuit /bin/sh -c 'kill -HUP 1' +Restart=always +RestartSec=30 +SyslogIdentifier=matrix-conduwuit + +[Install] +WantedBy=multi-user.target diff --git a/roles/custom/matrix-conduwuit/vars/main.yml b/roles/custom/matrix-conduwuit/vars/main.yml new file mode 100644 index 000000000..7d26a504b --- /dev/null +++ b/roles/custom/matrix-conduwuit/vars/main.yml @@ -0,0 +1,3 @@ +--- +matrix_conduwuit_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}/_matrix/client/versions" +matrix_conduwuit_federation_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}:{{ matrix_federation_public_port }}/_matrix/federation/v1/version" diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml new file mode 100644 index 000000000..a44f982e4 --- /dev/null +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml @@ -0,0 +1,5 @@ +--- + +- name: Ensure Conduwuit user registered - {{ user.username | quote }} + ansible.builtin.debug: + msg: "Not registering user. To register Conduwuit users, message the Conduwuit bot" diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index b3b792a78..6e9b63d54 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -302,6 +302,14 @@ - {'old': 'matrix_nginx_proxy_proxy_conduit_federation_api_addr_with_container', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_conduit_federation_api_addr_sans_container', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_conduit_additional_server_configuration_blocks', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_enabled', 'new': 'matrix_conduwuit_container_labels_traefik_enabled'} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_block_federation_api_on_client_port', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_enabled', 'new': 'matrix_conduwuit_container_labels_public_federation_api_enabled'} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_client_api_addr_with_container', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_client_api_addr_sans_container', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_addr_with_container', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_addr_sans_container', 'new': ''} + - {'old': 'matrix_nginx_proxy_proxy_conduwuit_additional_server_configuration_blocks', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_dendrite_enabled', 'new': 'matrix_dendrite_container_labels_traefik_enabled'} - {'old': 'matrix_nginx_proxy_proxy_dendrite_block_federation_api_on_client_port', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_dendrite_federation_api_enabled', 'new': 'matrix_dendrite_container_labels_public_federation_api_enabled'} diff --git a/setup.yml b/setup.yml index cb5fd7a1a..95e4b4a03 100644 --- a/setup.yml +++ b/setup.yml @@ -106,6 +106,7 @@ - custom/matrix-synapse-reverse-proxy-companion - custom/matrix-dendrite - custom/matrix-conduit + - custom/matrix-conduwuit - custom/matrix-synapse-admin - custom/matrix-synapse-usage-exporter - galaxy/prometheus_node_exporter From 5e03006c5debee323cb92c1271420bd48e98a1fb Mon Sep 17 00:00:00 2001 From: Virkkunen Date: Sun, 19 Jan 2025 13:56:10 +0100 Subject: [PATCH 228/952] remove unnecessary configurations --- roles/custom/matrix-conduwuit/defaults/main.yml | 9 ++------- .../matrix-conduwuit/templates/conduwuit.toml.j2 | 10 ++-------- 2 files changed, 4 insertions(+), 15 deletions(-) diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml index d6cb553d2..14833051c 100644 --- a/roles/custom/matrix-conduwuit/defaults/main.yml +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -120,18 +120,13 @@ matrix_conduwuit_template_conduwuit_config: "{{ role_path }}/templates/conduwuit # Max size for uploads, in bytes matrix_conduwuit_max_request_size: 20_000_000 -# Maximum number of open files for conduwuit's embedded RocksDB database -# See https://github.com/facebook/rocksdb/wiki/RocksDB-Tuning-Guide#tuning-other-options -# By default, conduwuit uses a relatively low value of 20. -matrix_conduwuit_rocksdb_max_open_files: 64 - # Enables registration. If set to false, no users can register on this server. matrix_conduwuit_allow_registration: false matrix_conduwuit_allow_federation: true -# Enable the display name lightning bolt on registration. -matrix_conduwuit_enable_lightning_bolt: true +# The display name suffix on registration. Change to '' to disable. +matrix_conduwuit_new_user_displayname_suffix: '' matrix_conduwuit_trusted_servers: - "matrix.org" diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 index 9933c6573..849010b3f 100644 --- a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 +++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 @@ -23,7 +23,6 @@ server_name = "{{ matrix_domain }}" # This is the only directory where Conduwuit will save its data database_path = "/var/lib/matrix-conduwuit/" -database_backend = "rocksdb" # The port Conduwuit will be running on. You need to set up a reverse proxy in # your web server (e.g. apache or nginx), so all requests to /_matrix on port @@ -34,21 +33,16 @@ port = {{ matrix_conduwuit_port_number }} # Max size for uploads max_request_size = {{ matrix_conduwuit_max_request_size }} -# Max number of open files for the RocksDB database -rocksdb_max_open_files = {{ matrix_conduwuit_rocksdb_max_open_files }} - # Enables registration. If set to false, no users can register on this server. allow_registration = {{ matrix_conduwuit_allow_registration | to_json }} allow_federation = {{ matrix_conduwuit_allow_federation | to_json }} -# Enable the display name lightning bolt on registration. -enable_lightning_bolt = {{ matrix_conduwuit_enable_lightning_bolt | to_json }} +# Enable the display name suffix on registration. +new_user_displayname_suffix = {{ matrix_conduwuit_new_user_displayname_suffix | to_json }} trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }} -max_concurrent_requests = {{ matrix_conduwuit_max_concurrent_requests }} - log = "info,state_res=warn,rocket=off,_=off,sled=off" address = "0.0.0.0" From 1b80a76b935fa46611237bce86595bb26fd52576 Mon Sep 17 00:00:00 2001 From: Virkkunen Date: Sun, 19 Jan 2025 13:58:53 +0100 Subject: [PATCH 229/952] fix docker depName --- roles/custom/matrix-conduwuit/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml index 14833051c..3f71c515e 100644 --- a/roles/custom/matrix-conduwuit/defaults/main.yml +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -9,7 +9,7 @@ matrix_conduwuit_hostname: '' matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_name_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}" matrix_conduwuit_docker_image_name_prefix: "docker.io/" -# renovate: datasource=docker depName=matrixconduwuit/matrix-conduwuit +# renovate: datasource=docker depName=girlbossceo/conduwuit matrix_conduwuit_docker_image_tag: "main" matrix_conduwuit_docker_image_force_pull: "{{ matrix_conduwuit_docker_image.endswith(':latest') }}" From 24f3493caf3350f93b2efc9791195e0461a605f4 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 16:01:38 +0200 Subject: [PATCH 230/952] Add various polish to Conduwuit https://github.com/Virkkunen and I have been working on the same feature simultaneously. This patch adds my additional independent work on top of his changes. Notable changes here compared to Virkkunen's original work: - renaming config-related variables (`matrix_conduwuit_*` -> `matrix_conduwuit_config_*`). This is consistent with other roles (and better), but deviates from how the Conduit role was implemented. - using a full configuration sample from https://conduwuit.puppyirl.gay/configuration.html instead of using the old Conduit config file template - introducing configurability for more Conduwuit config settings, to support easy registration, etc. - removing configuration settings that Conduwuit does not support anymore (e.g. `max_concurrent_requests`) - cross-linking docs pages for Conduit and Conduwuit - a Conduwuit docs page which is much improved compared to the old Conduit one - REAMDE updates --- README.md | 1 + docs/configuring-playbook-conduit.md | 6 +- docs/configuring-playbook-conduwuit.md | 95 + group_vars/matrix_servers | 16 +- .../custom/matrix-conduwuit/defaults/main.yml | 83 +- .../custom/matrix-conduwuit/tasks/install.yml | 60 + roles/custom/matrix-conduwuit/tasks/main.yml | 13 +- .../tasks/self_check_client_api.yml | 23 + .../tasks/self_check_federation_api.yml | 28 + .../matrix-conduwuit/tasks/uninstall.yml | 19 + .../templates/conduwuit.toml.j2 | 1575 ++++++++++++++++- .../custom/matrix-conduwuit/templates/env.j2 | 1 + .../matrix-conduwuit/templates/labels.j2 | 33 +- .../systemd/matrix-conduwuit.service.j2 | 8 +- roles/custom/matrix-conduwuit/vars/main.yml | 1 + .../tasks/validate_config.yml | 8 - 16 files changed, 1879 insertions(+), 91 deletions(-) create mode 100644 docs/configuring-playbook-conduwuit.md create mode 100644 roles/custom/matrix-conduwuit/tasks/install.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml create mode 100644 roles/custom/matrix-conduwuit/tasks/uninstall.yml create mode 100644 roles/custom/matrix-conduwuit/templates/env.j2 diff --git a/README.md b/README.md index 488aab37e..ee1c5a144 100644 --- a/README.md +++ b/README.md @@ -52,6 +52,7 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow | ---- | -------- | ----------- | ------------- | | [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) | | [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) | +| [Conduwuit](https://conduwuit.puppyirl.gay/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. | [Link](docs/configuring-playbook-conduwuit.md) | | [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) | ### Clients diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 2eb571003..81ac48ee5 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -6,6 +6,8 @@ See the project's [documentation](https://docs.conduit.rs/) to learn what it doe By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. +💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [Conduwuit](./configuring-playbook-conduwuit.md). + ⚠️ **Warnings**: - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. @@ -48,9 +50,9 @@ Since it is difficult to create the first user account on Conduit (see [famedly/ ## Configuring bridges / appservices -Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start. +For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver. -You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command. +For Conduit, you will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command. Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit: diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md new file mode 100644 index 000000000..512f4530b --- /dev/null +++ b/docs/configuring-playbook-conduwuit.md @@ -0,0 +1,95 @@ +# Configuring Conduwuit (optional) + +The playbook can install and configure the [Conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you. + +See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you. + +By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. + +💡 **Note**: Conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). + +⚠️ **Warnings**: + +- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. + +- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding + +## Adjusting the playbook configuration + +To use Conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below: + +```yaml +matrix_homeserver_implementation: conduwuit + +# Registering users can only happen via the API, +# so it makes sense to enable it, at least initially. +matrix_conduwuit_config_allow_registration: true + +# Generate a strong registration token to protect the registration endpoint from abuse. +# You can create one with a command like `pwgen -s 64 1`. +matrix_conduwuit_config_registration_token: '' +``` + +### Extending the configuration + +There are some additional things you may wish to configure about the server. + +Take a look at: + +- `roles/custom/matrix-conduwuit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2` for the server's default configuration + +There are various Ansible variables that control settings in the `conduwuit.toml` file. + +If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://conduwuit.puppyirl.gay/configuration.html#environment-variables) using `matrix_conduwuit_environment_variables_extension`. For example: + +```yaml +matrix_conduwuit_environment_variables_extension: | + CONDUWUIT_MAX_REQUEST_SIZE=50000000 + CONDUWUIT_REQUEST_TIMEOUT=60 +``` + +## Creating the first user account + +Unlike other homeserver implementations (like Synapse and Dendrite), Conduwuit does not support creating users via the command line or via the playbook. + +If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token. + +This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users. + +The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**. + + +## Configuring bridges / appservices + +For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver. + +For Conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account. + +The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to Conduwuit's historical legacy. +Your first user account would already have been invited to an admin room with this bot. + +Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`. + +Then, send its content to the existing admin room: + + !admin appservices register + + ``` + as_token: + de.sorunome.msc2409.push_ephemeral: true + hs_token: + id: signal + namespaces: + aliases: + - exclusive: true + regex: ^#signal_.+:example\.org$ + users: + - exclusive: true + regex: ^@signal_.+:example\.org$ + - exclusive: true + regex: ^@signalbot:example\.org$ + rate_limited: false + sender_localpart: _bot_signalbot + url: http://matrix-mautrix-signal:29328 + ``` diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 3a0c9b963..4e5f0c9b2 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -553,7 +553,7 @@ matrix_homeserver_container_client_api_endpoint: |- 'synapse': ('matrix-synapse-reverse-proxy-companion:8008' if matrix_synapse_reverse_proxy_companion_enabled | default(false) else ('matrix-synapse:'+ matrix_synapse_container_client_api_port | default('8008') | string)), 'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string), 'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string), - 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_port_number | default('8008') | string), + 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_config_port_number | default('8008') | string), }[matrix_homeserver_implementation] }} @@ -563,7 +563,7 @@ matrix_homeserver_container_federation_api_endpoint: |- 'synapse': ('matrix-synapse-reverse-proxy-companion:8048' if matrix_synapse_reverse_proxy_companion_enabled else ('matrix-synapse:'+ matrix_synapse_container_federation_api_plain_port | default('8008') | string)), 'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string), 'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string), - 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_port_number | default('8008') | string), + 'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_config_port_number | default('8008') | string), }[matrix_homeserver_implementation] }} @@ -5818,7 +5818,7 @@ matrix_conduwuit_enabled: "{{ matrix_homeserver_implementation == 'conduwuit' }} matrix_conduwuit_hostname: "{{ matrix_server_fqn_matrix }}" -matrix_conduwuit_allow_federation: "{{ matrix_homeserver_federation_enabled }}" +matrix_conduwuit_config_allow_federation: "{{ matrix_homeserver_federation_enabled }}" matrix_conduwuit_container_network: "{{ matrix_homeserver_container_network }}" @@ -5844,7 +5844,7 @@ matrix_conduwuit_container_labels_public_federation_api_traefik_tls: "{{ matrix_ matrix_conduwuit_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}" matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}" -matrix_conduwuit_turn_uris: | +matrix_conduwuit_config_turn_uris: | {{ ([ 'turns:' + matrix_server_fqn_matrix + '?transport=udp', @@ -5857,9 +5857,11 @@ matrix_conduwuit_turn_uris: | ] if matrix_coturn_enabled else []) }} -matrix_conduwuit_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" -matrix_conduwuit_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" -matrix_conduwuit_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" +matrix_conduwuit_config_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" +matrix_conduwuit_config_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" +matrix_conduwuit_config_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" + +matrix_conduwuit_self_check_validate_certificates: "{{ matrix_playbook_ssl_enabled }}" ###################################################################### # diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml index 3f71c515e..f302ed664 100644 --- a/roles/custom/matrix-conduwuit/defaults/main.yml +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -1,5 +1,5 @@ --- -# Conduwuit is a fork of Conduit, powered by Matrix +# conduwuit is a very cool, featureful fork of conduit (https://gitlab.com/famedly/conduit). # Project source code URL: https://github.com/girlbossceo/conduwuit # See: https://conduwuit.puppyirl.gay/ @@ -7,17 +7,18 @@ matrix_conduwuit_enabled: true matrix_conduwuit_hostname: '' -matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_name_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}" +matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_registry_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}" matrix_conduwuit_docker_image_name_prefix: "docker.io/" -# renovate: datasource=docker depName=girlbossceo/conduwuit -matrix_conduwuit_docker_image_tag: "main" +# renovate: datasource=docker depName=ghcr.io/girlbossceo/conduwuit +matrix_conduwuit_docker_image_tag: v0.4.6-8f7ade4c22533a3177bfd8f175e178573ba6c1d4 matrix_conduwuit_docker_image_force_pull: "{{ matrix_conduwuit_docker_image.endswith(':latest') }}" +matrix_conduwuit_docker_image_registry_prefix: ghcr.io/ matrix_conduwuit_base_path: "{{ matrix_base_data_path }}/conduwuit" matrix_conduwuit_config_path: "{{ matrix_conduwuit_base_path }}/config" matrix_conduwuit_data_path: "{{ matrix_conduwuit_base_path }}/data" -matrix_conduwuit_port_number: 6167 +matrix_conduwuit_config_port_number: 6167 matrix_conduwuit_tmp_directory_size_mb: 500 @@ -88,7 +89,7 @@ matrix_conduwuit_container_labels_internal_client_api_traefik_priority: "{{ matr matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "" # Controls whether labels will be added that expose the Server-Server API (Federation API) on a public Traefik entrypoint. -matrix_conduwuit_container_labels_public_federation_api_enabled: "{{ matrix_conduwuit_allow_federation }}" +matrix_conduwuit_container_labels_public_federation_api_enabled: "{{ matrix_conduwuit_config_allow_federation }}" matrix_conduwuit_container_labels_public_federation_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}" matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix: /_matrix matrix_conduwuit_container_labels_public_federation_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix }}`)" @@ -98,6 +99,16 @@ matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints: '' matrix_conduwuit_container_labels_public_federation_api_traefik_tls: true matrix_conduwuit_container_labels_public_federation_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}" # noqa var-naming +# Controls whether labels will be added that expose the `/_conduwuit` path prefix on a public Traefik entrypoint. +matrix_conduwuit_container_labels_public_conduwuit_api_enabled: true +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}" +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_path_prefix: /_conduwuit +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_path_prefix }}`)" +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority: 0 +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}" +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls: "{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints != 'web' }}" +matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}" # noqa var-naming + # matrix_conduwuit_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. # See `../templates/labels.j2` for details. # @@ -118,25 +129,61 @@ matrix_conduwuit_container_extra_arguments: [] matrix_conduwuit_template_conduwuit_config: "{{ role_path }}/templates/conduwuit.toml.j2" # Max size for uploads, in bytes -matrix_conduwuit_max_request_size: 20_000_000 +matrix_conduwuit_config_server_name: "{{ matrix_domain }}" + +# Max size for uploads, in bytes +matrix_conduwuit_config_max_request_size: 20_000_000 # Enables registration. If set to false, no users can register on this server. -matrix_conduwuit_allow_registration: false +matrix_conduwuit_config_allow_registration: false -matrix_conduwuit_allow_federation: true +# Controls the `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse` setting. +# This is only used when `matrix_conduwuit_config_allow_registration` is set to true and no registration token is configured. +matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse: false -# The display name suffix on registration. Change to '' to disable. -matrix_conduwuit_new_user_displayname_suffix: '' +# Controls the `registration_token` setting. +# When registration is enabled (`matrix_conduwuit_config_allow_registration`) you: +# - either need to set a token to protect registration from abuse +# - or you need to enable the `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse` setting +# (see `matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse`), +# to allow registration without any form of 2nd-step. +matrix_conduwuit_config_registration_token: '' + +# Controls the `new_user_displayname_suffix` setting. +# This is the suffix that will be added to the displayname of new users. +# Upstream defaults this to "🏳️‍⚧️", but we keep this consistent across all homeserver implementations and do not enable a suffix. +matrix_conduwuit_config_new_user_displayname_suffix: "" + +# Controls the `allow_check_for_updates` setting. +matrix_conduwuit_config_allow_check_for_updates: false + +# Controls the `emergency_password` setting. +matrix_conduwuit_config_emergency_password: '' + +# Controls the `allow_federation` setting. +matrix_conduwuit_config_allow_federation: true matrix_conduwuit_trusted_servers: - "matrix.org" -# How many requests conduwuit sends to other servers at the same time -matrix_conduwuit_max_concurrent_requests: 100 +matrix_conduwuit_config_log: "info,state_res=warn,rocket=off,_=off,sled=off" # TURN integration. -# See: https://gitlab.com/famedly/conduwuit/-/blob/next/TURN.md -matrix_conduwuit_turn_uris: [] -matrix_conduwuit_turn_secret: '' -matrix_conduwuit_turn_username: '' -matrix_conduwuit_turn_password: '' +# See: https://conduwuit.puppyirl.gay/turn.html +matrix_conduwuit_config_turn_uris: [] +matrix_conduwuit_config_turn_secret: '' +matrix_conduwuit_config_turn_username: '' +matrix_conduwuit_config_turn_password: '' + +# Controls whether the self-check feature should validate SSL certificates. +matrix_conduwuit_self_check_validate_certificates: true + +# Additional environment variables to pass to the container. +# +# Environment variables take priority over settings in the configuration file. +# +# Example: +# matrix_conduwuit_environment_variables_extension: | +# CONDUWUIT_MAX_REQUEST_SIZE=50000000 +# CONDUWUIT_REQUEST_TIMEOUT=60 +matrix_conduwuit_environment_variables_extension: '' diff --git a/roles/custom/matrix-conduwuit/tasks/install.yml b/roles/custom/matrix-conduwuit/tasks/install.yml new file mode 100644 index 000000000..91d244c25 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/install.yml @@ -0,0 +1,60 @@ +--- + +- name: Ensure conduwuit config path exists + ansible.builtin.file: + path: "{{ matrix_conduwuit_config_path }}" + state: directory + mode: 0750 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit data path exists + ansible.builtin.file: + path: "{{ matrix_conduwuit_data_path }}" + state: directory + mode: 0770 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit configuration installed + ansible.builtin.template: + src: "{{ matrix_conduwuit_template_conduwuit_config }}" + dest: "{{ matrix_conduwuit_config_path }}/conduwuit.toml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure conduwuit support files installed + ansible.builtin.template: + src: "{{ role_path }}/templates/{{ item }}.j2" + dest: "{{ matrix_conduwuit_base_path }}/{{ item }}" + mode: 0640 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - labels + - env + +- name: Ensure conduwuit container network is created + community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" + name: "{{ matrix_conduwuit_container_network }}" + driver: bridge + driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" + +- name: Ensure conduwuit container image is pulled + community.docker.docker_image: + name: "{{ matrix_conduwuit_docker_image }}" + source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" + force_source: "{{ matrix_conduwuit_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_conduwuit_docker_image_force_pull }}" + register: result + retries: "{{ devture_playbook_help_container_retries_count }}" + delay: "{{ devture_playbook_help_container_retries_delay }}" + until: result is not failed + +- name: Ensure matrix-conduwuit.service installed + ansible.builtin.template: + src: "{{ role_path }}/templates/systemd/matrix-conduwuit.service.j2" + dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + mode: 0644 diff --git a/roles/custom/matrix-conduwuit/tasks/main.yml b/roles/custom/matrix-conduwuit/tasks/main.yml index e6f16d120..68d5daad1 100644 --- a/roles/custom/matrix-conduwuit/tasks/main.yml +++ b/roles/custom/matrix-conduwuit/tasks/main.yml @@ -10,11 +10,20 @@ ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" - when: matrix_conduwuit_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" + ansible.builtin.include_tasks: "{{ role_path }}/tasks/install.yml" - tags: - setup-all - setup-conduwuit block: - when: not matrix_conduwuit_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" + ansible.builtin.include_tasks: "{{ role_path }}/tasks/uninstall.yml" + +- tags: + - self-check + block: + - when: matrix_conduwuit_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/self_check_client_api.yml" + + - when: matrix_conduwuit_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/self_check_federation_api.yml" diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml new file mode 100644 index 000000000..a34c14fb4 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml @@ -0,0 +1,23 @@ +--- + +- name: Check Matrix Client API + ansible.builtin.uri: + url: "{{ matrix_conduwuit_client_api_url_endpoint_public }}" + follow_redirects: none + validate_certs: "{{ matrix_conduwuit_self_check_validate_certificates }}" + register: result_matrix_conduwuit_client_api + ignore_errors: true + check_mode: false + when: matrix_conduwuit_enabled | bool + delegate_to: 127.0.0.1 + become: false + +- name: Fail if Matrix Client API not working + ansible.builtin.fail: + msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`). Is Conduwuit running? Is port 443 open in your firewall? Full error: {{ result_matrix_conduwuit_client_api }}" + when: "matrix_conduwuit_enabled | bool and (result_matrix_conduwuit_client_api.failed or 'json' not in result_matrix_conduwuit_client_api)" + +- name: Report working Matrix Client API + ansible.builtin.debug: + msg: "The Matrix Client API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`) is working" + when: matrix_conduwuit_enabled | bool diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml new file mode 100644 index 000000000..fde73dae0 --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml @@ -0,0 +1,28 @@ +--- + +- name: Check Matrix Federation API + ansible.builtin.uri: + url: "{{ matrix_synapse_federation_api_url_endpoint_public }}" + follow_redirects: none + validate_certs: "{{ matrix_synapse_self_check_validate_certificates }}" + register: result_matrix_synapse_federation_api + ignore_errors: true + check_mode: false + when: matrix_synapse_enabled | bool + delegate_to: 127.0.0.1 + become: false + +- name: Fail if Matrix Federation API not working + ansible.builtin.fail: + msg: "Failed checking Matrix Federation API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`). Is Synapse running? Is port {{ matrix_federation_public_port }} open in your firewall? Full error: {{ result_matrix_synapse_federation_api }}" + when: "matrix_synapse_enabled | bool and matrix_synapse_federation_enabled | bool and (result_matrix_synapse_federation_api.failed or 'json' not in result_matrix_synapse_federation_api)" + +- name: Fail if Matrix Federation API unexpectedly enabled + ansible.builtin.fail: + msg: "Matrix Federation API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`) despite being disabled." + when: "matrix_synapse_enabled | bool and not matrix_synapse_federation_enabled | bool and not result_matrix_synapse_federation_api.failed" + +- name: Report working Matrix Federation API + ansible.builtin.debug: + msg: "The Matrix Federation API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`) is working" + when: "matrix_synapse_enabled | bool and matrix_synapse_federation_enabled | bool" diff --git a/roles/custom/matrix-conduwuit/tasks/uninstall.yml b/roles/custom/matrix-conduwuit/tasks/uninstall.yml new file mode 100644 index 000000000..dcf802b0a --- /dev/null +++ b/roles/custom/matrix-conduwuit/tasks/uninstall.yml @@ -0,0 +1,19 @@ +--- + +- name: Check existence of matrix-conduwuit service + ansible.builtin.stat: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + register: matrix_conduwuit_service_stat + +- when: matrix_conduwuit_service_stat.stat.exists | bool + block: + - name: Ensure matrix-conduwuit is stopped + ansible.builtin.systemd: + name: matrix-conduwuit + state: stopped + daemon_reload: true + + - name: Ensure matrix-conduwuit.service doesn't exist + ansible.builtin.file: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service" + state: absent diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 index 849010b3f..4b011448c 100644 --- a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 +++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 @@ -1,61 +1,1538 @@ -# ============================================================================= -# This is the official example config for Conduwuit. -# If you use it for your server, you will need to adjust it to your own needs. -# At the very least, change the server_name field! -# ============================================================================= - +### conduwuit Configuration +### See: +### https://conduwuit.puppyirl.gay/configuration.html [global] -# The server_name is the pretty name of this server. It is used as a suffix for user -# and room IDs. Examples: matrix.org, puppyirl.gay -# The Conduwuit server needs all /_matrix/ requests to be reachable at -# https://example.com/ on port 443 (client-server) and 8448 (federation). - -# If that's not possible for you, you can create /.well-known files to redirect -# requests. See -# https://matrix.org/docs/spec/client_server/latest#get-well-known-matrix-client -# and -# https://matrix.org/docs/spec/server_server/r0.1.4#get-well-known-matrix-server -# for more information - -server_name = "{{ matrix_domain }}" - -# This is the only directory where Conduwuit will save its data -database_path = "/var/lib/matrix-conduwuit/" - -# The port Conduwuit will be running on. You need to set up a reverse proxy in -# your web server (e.g. apache or nginx), so all requests to /_matrix on port -# 443 and 8448 will be forwarded to the Conduwuit instance running on this port -# Docker users: Don't change this, you'll need to map an external port to this. -port = {{ matrix_conduwuit_port_number }} - -# Max size for uploads -max_request_size = {{ matrix_conduwuit_max_request_size }} - -# Enables registration. If set to false, no users can register on this server. -allow_registration = {{ matrix_conduwuit_allow_registration | to_json }} - -allow_federation = {{ matrix_conduwuit_allow_federation | to_json }} - -# Enable the display name suffix on registration. -new_user_displayname_suffix = {{ matrix_conduwuit_new_user_displayname_suffix | to_json }} - -trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }} - -log = "info,state_res=warn,rocket=off,_=off,sled=off" +# The server_name is the pretty name of this server. It is used as a +# suffix for user and room IDs/aliases. +# +# See the docs for reverse proxying and delegation: +# https://conduwuit.puppyirl.gay/deploying/generic.html#setting-up-the-reverse-proxy +# +# Also see the `[global.well_known]` config section at the very bottom. +# +# Examples of delegation: +# - https://puppygock.gay/.well-known/matrix/server +# - https://puppygock.gay/.well-known/matrix/client +# +# YOU NEED TO EDIT THIS. THIS CANNOT BE CHANGED AFTER WITHOUT A DATABASE +# WIPE. +# +# example: "conduwuit.woof" +# +server_name = {{ matrix_conduwuit_config_server_name | to_json }} +# The default address (IPv4 or IPv6) conduwuit will listen on. +# +# If you are using Docker or a container NAT networking setup, this must +# be "0.0.0.0". +# +# To listen on multiple addresses, specify a vector e.g. ["127.0.0.1", +# "::1"] +# address = "0.0.0.0" -turn_uris = {{ matrix_conduwuit_turn_uris | to_json }} +# The port(s) conduwuit will listen on. +# +# For reverse proxying, see: +# https://conduwuit.puppyirl.gay/deploying/generic.html#setting-up-the-reverse-proxy +# +# If you are using Docker, don't change this, you'll need to map an +# external port to this. +# +# To listen on multiple ports, specify a vector e.g. [8080, 8448] +# +port = {{ matrix_conduwuit_config_port_number }} -{% if matrix_conduwuit_turn_secret != '' %} -turn_secret = {{ matrix_conduwuit_turn_secret | to_json }} +# The UNIX socket conduwuit will listen on. +# +# conduwuit cannot listen on both an IP address and a UNIX socket. If +# listening on a UNIX socket, you MUST remove/comment the `address` key. +# +# Remember to make sure that your reverse proxy has access to this socket +# file, either by adding your reverse proxy to the 'conduwuit' group or +# granting world R/W permissions with `unix_socket_perms` (666 minimum). +# +# example: "/run/conduwuit/conduwuit.sock" +# +#unix_socket_path = + +# The default permissions (in octal) to create the UNIX socket with. +# +#unix_socket_perms = 660 + +# This is the only directory where conduwuit will save its data, including +# media. Note: this was previously "/var/lib/matrix-conduit". +# +# YOU NEED TO EDIT THIS. +# +# example: "/var/lib/conduwuit" +# +database_path = "/var/lib/conduwuit" + +# conduwuit supports online database backups using RocksDB's Backup engine +# API. To use this, set a database backup path that conduwuit can write +# to. +# +# For more information, see: +# https://conduwuit.puppyirl.gay/maintenance.html#backups +# +# example: "/opt/conduwuit-db-backups" +# +#database_backup_path = + +# The amount of online RocksDB database backups to keep/retain, if using +# "database_backup_path", before deleting the oldest one. +# +#database_backups_to_keep = 1 + +# Text which will be added to the end of the user's displayname upon +# registration with a space before the text. In Conduit, this was the +# lightning bolt emoji. +# +# To disable, set this to "" (an empty string). +# +# The default is the trans pride flag. +# +# example: "🏳️‍⚧️" +# +new_user_displayname_suffix = {{ matrix_conduwuit_config_new_user_displayname_suffix | to_json }} + +# If enabled, conduwuit will send a simple GET request periodically to +# `https://pupbrain.dev/check-for-updates/stable` for any new +# announcements made. Despite the name, this is not an update check +# endpoint, it is simply an announcement check endpoint. +# +# This is disabled by default as this is rarely used except for security +# updates or major updates. +# +allow_check_for_updates = {{ matrix_conduwuit_config_allow_check_for_updates | to_json }} + +# Set this to any float value to multiply conduwuit's in-memory LRU caches +# with such as "auth_chain_cache_capacity". +# +# May be useful if you have significant memory to spare to increase +# performance. +# +# If you have low memory, reducing this may be viable. +# +# By default, the individual caches such as "auth_chain_cache_capacity" +# are scaled by your CPU core count. +# +#cache_capacity_modifier = 1.0 + +# Set this to any float value in megabytes for conduwuit to tell the +# database engine that this much memory is available for database read +# caches. +# +# May be useful if you have significant memory to spare to increase +# performance. +# +# Similar to the individual LRU caches, this is scaled up with your CPU +# core count. +# +# This defaults to 128.0 + (64.0 * CPU core count). +# +#db_cache_capacity_mb = varies by system + +# Set this to any float value in megabytes for conduwuit to tell the +# database engine that this much memory is available for database write +# caches. +# +# May be useful if you have significant memory to spare to increase +# performance. +# +# Similar to the individual LRU caches, this is scaled up with your CPU +# core count. +# +# This defaults to 48.0 + (4.0 * CPU core count). +# +#db_write_buffer_capacity_mb = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#pdu_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#auth_chain_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#shorteventid_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#eventidshort_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#eventid_pdu_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#shortstatekey_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#statekeyshort_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#servernameevent_data_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#server_visibility_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#user_visibility_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#stateinfo_cache_capacity = varies by system + +# This item is undocumented. Please contribute documentation for it. +# +#roomid_spacehierarchy_cache_capacity = varies by system + +# Maximum entries stored in DNS memory-cache. The size of an entry may +# vary so please take care if raising this value excessively. Only +# decrease this when using an external DNS cache. Please note that +# systemd-resolved does *not* count as an external cache, even when +# configured to do so. +# +#dns_cache_entries = 32768 + +# Minimum time-to-live in seconds for entries in the DNS cache. The +# default may appear high to most administrators; this is by design as the +# majority of NXDOMAINs are correct for a long time (e.g. the server is no +# longer running Matrix). Only decrease this if you are using an external +# DNS cache. +# +#dns_min_ttl = 10800 + +# Minimum time-to-live in seconds for NXDOMAIN entries in the DNS cache. +# This value is critical for the server to federate efficiently. +# NXDOMAIN's are assumed to not be returning to the federation and +# aggressively cached rather than constantly rechecked. +# +# Defaults to 3 days as these are *very rarely* false negatives. +# +#dns_min_ttl_nxdomain = 259200 + +# Number of DNS nameserver retries after a timeout or error. +# +#dns_attempts = 10 + +# The number of seconds to wait for a reply to a DNS query. Please note +# that recursive queries can take up to several seconds for some domains, +# so this value should not be too low, especially on slower hardware or +# resolvers. +# +#dns_timeout = 10 + +# Fallback to TCP on DNS errors. Set this to false if unsupported by +# nameserver. +# +#dns_tcp_fallback = true + +# Enable to query all nameservers until the domain is found. Referred to +# as "trust_negative_responses" in hickory_resolver. This can avoid +# useless DNS queries if the first nameserver responds with NXDOMAIN or +# an empty NOERROR response. +# +#query_all_nameservers = true + +# Enable using *only* TCP for querying your specified nameservers instead +# of UDP. +# +# If you are running conduwuit in a container environment, this config +# option may need to be enabled. For more details, see: +# https://conduwuit.puppyirl.gay/troubleshooting.html#potential-dns-issues-when-using-docker +# +#query_over_tcp_only = false + +# DNS A/AAAA record lookup strategy +# +# Takes a number of one of the following options: +# 1 - Ipv4Only (Only query for A records, no AAAA/IPv6) +# +# 2 - Ipv6Only (Only query for AAAA records, no A/IPv4) +# +# 3 - Ipv4AndIpv6 (Query for A and AAAA records in parallel, uses whatever +# returns a successful response first) +# +# 4 - Ipv6thenIpv4 (Query for AAAA record, if that fails then query the A +# record) +# +# 5 - Ipv4thenIpv6 (Query for A record, if that fails then query the AAAA +# record) +# +# If you don't have IPv6 networking, then for better DNS performance it +# may be suitable to set this to Ipv4Only (1) as you will never ever use +# the AAAA record contents even if the AAAA record is successful instead +# of the A record. +# +#ip_lookup_strategy = 5 + +# Max request size for file uploads in bytes. Defaults to 20MB. +# +max_request_size = {{ matrix_conduwuit_config_max_request_size }} + +# This item is undocumented. Please contribute documentation for it. +# +#max_fetch_prev_events = 192 + +# Default/base connection timeout (seconds). This is used only by URL +# previews and update/news endpoint checks. +# +#request_conn_timeout = 10 + +# Default/base request timeout (seconds). The time waiting to receive more +# data from another server. This is used only by URL previews, +# update/news, and misc endpoint checks. +# +#request_timeout = 35 + +# Default/base request total timeout (seconds). The time limit for a whole +# request. This is set very high to not cancel healthy requests while +# serving as a backstop. This is used only by URL previews and update/news +# endpoint checks. +# +#request_total_timeout = 320 + +# Default/base idle connection pool timeout (seconds). This is used only +# by URL previews and update/news endpoint checks. +# +#request_idle_timeout = 5 + +# Default/base max idle connections per host. This is used only by URL +# previews and update/news endpoint checks. Defaults to 1 as generally the +# same open connection can be re-used. +# +#request_idle_per_host = 1 + +# Federation well-known resolution connection timeout (seconds). +# +#well_known_conn_timeout = 6 + +# Federation HTTP well-known resolution request timeout (seconds). +# +#well_known_timeout = 10 + +# Federation client request timeout (seconds). You most definitely want +# this to be high to account for extremely large room joins, slow +# homeservers, your own resources etc. +# +#federation_timeout = 300 + +# Federation client idle connection pool timeout (seconds). +# +#federation_idle_timeout = 25 + +# Federation client max idle connections per host. Defaults to 1 as +# generally the same open connection can be re-used. +# +#federation_idle_per_host = 1 + +# Federation sender request timeout (seconds). The time it takes for the +# remote server to process sent transactions can take a while. +# +#sender_timeout = 180 + +# Federation sender idle connection pool timeout (seconds). +# +#sender_idle_timeout = 180 + +# Federation sender transaction retry backoff limit (seconds). +# +#sender_retry_backoff_limit = 86400 + +# Appservice URL request connection timeout. Defaults to 35 seconds as +# generally appservices are hosted within the same network. +# +#appservice_timeout = 35 + +# Appservice URL idle connection pool timeout (seconds). +# +#appservice_idle_timeout = 300 + +# Notification gateway pusher idle connection pool timeout. +# +#pusher_idle_timeout = 15 + +# Enables registration. If set to false, no users can register on this +# server. +# +# If set to true without a token configured, users can register with no +# form of 2nd-step only if you set the following option to true: +# `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse` +# +# If you would like registration only via token reg, please configure +# `registration_token` or `registration_token_file`. +# +allow_registration = {{ matrix_conduwuit_config_allow_registration | to_json }} + +yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse = {{ matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse | to_json }} + +allow_federation = {{ matrix_conduwuit_config_allow_federation | to_json }} + +# This item is undocumented. Please contribute documentation for it. +# +#yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse = false + +# A static registration token that new users will have to provide when +# creating an account. If unset and `allow_registration` is true, +# registration is open without any condition. +# +# YOU NEED TO EDIT THIS OR USE registration_token_file. +# +# example: "o&^uCtes4HPf0Vu@F20jQeeWE7" +# +registration_token = {{ matrix_conduwuit_config_registration_token | to_json }} + +# Path to a file on the system that gets read for the registration token. +# this config option takes precedence/priority over "registration_token". +# +# conduwuit must be able to access the file, and it must not be empty +# +# example: "/etc/conduwuit/.reg_token" +# +#registration_token_file = + +# Controls whether encrypted rooms and events are allowed. +# +#allow_encryption = true + +# Controls whether federation is allowed or not. It is not recommended to +# disable this after the fact due to potential federation breakage. +# +#allow_federation = true + +# This item is undocumented. Please contribute documentation for it. +# +#federation_loopback = false + +# Set this to true to require authentication on the normally +# unauthenticated profile retrieval endpoints (GET) +# "/_matrix/client/v3/profile/{userId}". +# +# This can prevent profile scraping. +# +#require_auth_for_profile_requests = false + +# Set this to true to allow your server's public room directory to be +# federated. Set this to false to protect against /publicRooms spiders, +# but will forbid external users from viewing your server's public room +# directory. If federation is disabled entirely (`allow_federation`), this +# is inherently false. +# +#allow_public_room_directory_over_federation = false + +# Set this to true to allow your server's public room directory to be +# queried without client authentication (access token) through the Client +# APIs. Set this to false to protect against /publicRooms spiders. +# +#allow_public_room_directory_without_auth = false + +# Allow guests/unauthenticated users to access TURN credentials. +# +# This is the equivalent of Synapse's `turn_allow_guests` config option. +# This allows any unauthenticated user to call the endpoint +# `/_matrix/client/v3/voip/turnServer`. +# +# It is unlikely you need to enable this as all major clients support +# authentication for this endpoint and prevents misuse of your TURN server +# from potential bots. +# +#turn_allow_guests = false + +# Set this to true to lock down your server's public room directory and +# only allow admins to publish rooms to the room directory. Unpublishing +# is still allowed by all users with this enabled. +# +#lockdown_public_room_directory = false + +# Set this to true to allow federating device display names / allow +# external users to see your device display name. If federation is +# disabled entirely (`allow_federation`), this is inherently false. For +# privacy reasons, this is best left disabled. +# +#allow_device_name_federation = false + +# Config option to allow or disallow incoming federation requests that +# obtain the profiles of our local users from +# `/_matrix/federation/v1/query/profile` +# +# Increases privacy of your local user's such as display names, but some +# remote users may get a false "this user does not exist" error when they +# try to invite you to a DM or room. Also can protect against profile +# spiders. +# +# This is inherently false if `allow_federation` is disabled +# +#allow_inbound_profile_lookup_federation_requests = true + +# Allow standard users to create rooms. Appservices and admins are always +# allowed to create rooms +# +#allow_room_creation = true + +# Set to false to disable users from joining or creating room versions +# that aren't officially supported by conduwuit. +# +# conduwuit officially supports room versions 6 - 11. +# +# conduwuit has slightly experimental (though works fine in practice) +# support for versions 3 - 5. +# +#allow_unstable_room_versions = true + +# Default room version conduwuit will create rooms with. +# +# Per spec, room version 10 is the default. +# +#default_room_version = 10 + +# This item is undocumented. Please contribute documentation for it. +# +#allow_jaeger = false + +# This item is undocumented. Please contribute documentation for it. +# +#jaeger_filter = "info" + +# If the 'perf_measurements' compile-time feature is enabled, enables +# collecting folded stack trace profile of tracing spans using +# tracing_flame. The resulting profile can be visualized with inferno[1], +# speedscope[2], or a number of other tools. +# +# [1]: https://github.com/jonhoo/inferno +# [2]: www.speedscope.app +# +#tracing_flame = false + +# This item is undocumented. Please contribute documentation for it. +# +#tracing_flame_filter = "info" + +# This item is undocumented. Please contribute documentation for it. +# +#tracing_flame_output_path = "./tracing.folded" + +# Examples: +# +# - No proxy (default): +# +# proxy = "none" +# +# - For global proxy, create the section at the bottom of this file: +# +# [global.proxy] +# global = { url = "socks5h://localhost:9050" } +# +# - To proxy some domains: +# +# [global.proxy] +# [[global.proxy.by_domain]] +# url = "socks5h://localhost:9050" +# include = ["*.onion", "matrix.myspecial.onion"] +# exclude = ["*.myspecial.onion"] +# +# Include vs. Exclude: +# +# - If include is an empty list, it is assumed to be `["*"]`. +# +# - If a domain matches both the exclude and include list, the proxy will +# only be used if it was included because of a more specific rule than +# it was excluded. In the above example, the proxy would be used for +# `ordinary.onion`, `matrix.myspecial.onion`, but not +# `hello.myspecial.onion`. +# +#proxy = "none" + +# Servers listed here will be used to gather public keys of other servers +# (notary trusted key servers). +# +# Currently, conduwuit doesn't support inbound batched key requests, so +# this list should only contain other Synapse servers. +# +# example: ["matrix.org", "envs.net", "constellatory.net", "tchncs.de"] +# +trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }} + +# Whether to query the servers listed in trusted_servers first or query +# the origin server first. For best security, querying the origin server +# first is advised to minimize the exposure to a compromised trusted +# server. For maximum federation/join performance this can be set to true, +# however other options exist to query trusted servers first under +# specific high-load circumstances and should be evaluated before setting +# this to true. +# +#query_trusted_key_servers_first = false + +# Whether to query the servers listed in trusted_servers first +# specifically on room joins. This option limits the exposure to a +# compromised trusted server to room joins only. The join operation +# requires gathering keys from many origin servers which can cause +# significant delays. Therefor this defaults to true to mitigate +# unexpected delays out-of-the-box. The security-paranoid or those willing +# to tolerate delays are advised to set this to false. Note that setting +# query_trusted_key_servers_first to true causes this option to be +# ignored. +# +#query_trusted_key_servers_first_on_join = true + +# Only query trusted servers for keys and never the origin server. This is +# intended for clusters or custom deployments using their trusted_servers +# as forwarding-agents to cache and deduplicate requests. Notary servers +# do not act as forwarding-agents by default, therefor do not enable this +# unless you know exactly what you are doing. +# +#only_query_trusted_key_servers = false + +# Maximum number of keys to request in each trusted server batch query. +# +#trusted_server_batch_size = 1024 + +# Max log level for conduwuit. Allows debug, info, warn, or error. +# +# See also: +# https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives +# +# **Caveat**: +# For release builds, the tracing crate is configured to only implement +# levels higher than error to avoid unnecessary overhead in the compiled +# binary from trace macros. For debug builds, this restriction is not +# applied. +# +log = {{ matrix_conduwuit_config_log | to_json }} + +# Output logs with ANSI colours. +# +#log_colors = true + +# Configures the span events which will be outputted with the log. +# +#log_span_events = "none" + +# Configures whether CONDUWUIT_LOG EnvFilter matches values using regular +# expressions. See the tracing_subscriber documentation on Directives. +# +#log_filter_regex = true + +# Toggles the display of ThreadId in tracing log output. +# +#log_thread_ids = false + +# OpenID token expiration/TTL in seconds. +# +# These are the OpenID tokens that are primarily used for Matrix account +# integrations (e.g. Vector Integrations in Element), *not* OIDC/OpenID +# Connect/etc. +# +#openid_token_ttl = 3600 + +# Allow an existing session to mint a login token for another client. +# This requires interactive authentication, but has security ramifications +# as a malicious client could use the mechanism to spawn more than one +# session. +# Enabled by default. +# +#login_via_existing_session = true + +# Login token expiration/TTL in milliseconds. +# +# These are short-lived tokens for the m.login.token endpoint. +# This is used to allow existing sessions to create new sessions. +# see login_via_existing_session. +# +#login_token_ttl = 120000 + +# Static TURN username to provide the client if not using a shared secret +# ("turn_secret"), It is recommended to use a shared secret over static +# credentials. +# +#turn_username = false + +# Static TURN password to provide the client if not using a shared secret +# ("turn_secret"). It is recommended to use a shared secret over static +# credentials. +# +#turn_password = false + +# Vector list of TURN URIs/servers to use. +# +# Replace "example.turn.uri" with your TURN domain, such as the coturn +# "realm" config option. If using TURN over TLS, replace the URI prefix +# "turn:" with "turns:". +# +# example: ["turn:example.turn.uri?transport=udp", +# "turn:example.turn.uri?transport=tcp"] +# +turn_uris = {{ matrix_conduwuit_config_turn_uris | to_json }} + +# TURN secret to use for generating the HMAC-SHA1 hash apart of username +# and password generation. +# +# This is more secure, but if needed you can use traditional static +# username/password credentials. +# +#turn_secret = false +{% if matrix_conduwuit_config_turn_secret != '' %} +turn_secret = {{ matrix_conduwuit_config_turn_secret | to_json }} {% endif %} # If you have your TURN server configured to use a username and password # you can provide these information too. In this case comment out `turn_secret above`! -{% if matrix_conduwuit_turn_username != '' or matrix_conduwuit_turn_password != '' %} -turn_username = {{ matrix_conduwuit_turn_username | to_json }} -turn_password = {{ matrix_conduwuit_turn_password | to_json }} +{% if matrix_conduwuit_config_turn_username != '' or matrix_conduwuit_config_turn_password != '' %} +turn_username = {{ matrix_conduwuit_config_turn_username | to_json }} +turn_password = {{ matrix_conduwuit_config_turn_password | to_json }} {% endif %} + +# TURN secret to use that's read from the file path specified. +# +# This takes priority over "turn_secret" first, and falls back to +# "turn_secret" if invalid or failed to open. +# +# example: "/etc/conduwuit/.turn_secret" +# +#turn_secret_file = + +# TURN TTL, in seconds. +# +#turn_ttl = 86400 + +# List/vector of room IDs or room aliases that conduwuit will make newly +# registered users join. The rooms specified must be rooms that you have +# joined at least once on the server, and must be public. +# +# example: ["#conduwuit:puppygock.gay", +# "!eoIzvAvVwY23LPDay8:puppygock.gay"] +# +#auto_join_rooms = [] + +# Config option to automatically deactivate the account of any user who +# attempts to join a: +# - banned room +# - forbidden room alias +# - room alias or ID with a forbidden server name +# +# This may be useful if all your banned lists consist of toxic rooms or +# servers that no good faith user would ever attempt to join, and +# to automatically remediate the problem without any admin user +# intervention. +# +# This will also make the user leave all rooms. Federation (e.g. remote +# room invites) are ignored here. +# +# Defaults to false as rooms can be banned for non-moderation-related +# reasons and this performs a full user deactivation. +# +#auto_deactivate_banned_room_attempts = false + +# RocksDB log level. This is not the same as conduwuit's log level. This +# is the log level for the RocksDB engine/library which show up in your +# database folder/path as `LOG` files. conduwuit will log RocksDB errors +# as normal through tracing or panics if severe for safety. +# +#rocksdb_log_level = "error" + +# This item is undocumented. Please contribute documentation for it. +# +#rocksdb_log_stderr = false + +# Max RocksDB `LOG` file size before rotating in bytes. Defaults to 4MB in +# bytes. +# +#rocksdb_max_log_file_size = 4194304 + +# Time in seconds before RocksDB will forcibly rotate logs. +# +#rocksdb_log_time_to_roll = 0 + +# Set this to true to use RocksDB config options that are tailored to HDDs +# (slower device storage). +# +# It is worth noting that by default, conduwuit will use RocksDB with +# Direct IO enabled. *Generally* speaking this improves performance as it +# bypasses buffered I/O (system page cache). However there is a potential +# chance that Direct IO may cause issues with database operations if your +# setup is uncommon. This has been observed with FUSE filesystems, and +# possibly ZFS filesystem. RocksDB generally deals/corrects these issues +# but it cannot account for all setups. If you experience any weird +# RocksDB issues, try enabling this option as it turns off Direct IO and +# feel free to report in the conduwuit Matrix room if this option fixes +# your DB issues. +# +# For more information, see: +# https://github.com/facebook/rocksdb/wiki/Direct-IO +# +#rocksdb_optimize_for_spinning_disks = false + +# Enables direct-io to increase database performance via unbuffered I/O. +# +# For more details about direct I/O and RockDB, see: +# https://github.com/facebook/rocksdb/wiki/Direct-IO +# +# Set this option to false if the database resides on a filesystem which +# does not support direct-io like FUSE, or any form of complex filesystem +# setup such as possibly ZFS. +# +#rocksdb_direct_io = true + +# Amount of threads that RocksDB will use for parallelism on database +# operations such as cleanup, sync, flush, compaction, etc. Set to 0 to +# use all your logical threads. Defaults to your CPU logical thread count. +# +#rocksdb_parallelism_threads = varies by system + +# Maximum number of LOG files RocksDB will keep. This must *not* be set to +# 0. It must be at least 1. Defaults to 3 as these are not very useful +# unless troubleshooting/debugging a RocksDB bug. +# +#rocksdb_max_log_files = 3 + +# Type of RocksDB database compression to use. +# +# Available options are "zstd", "zlib", "bz2", "lz4", or "none". +# +# It is best to use ZSTD as an overall good balance between +# speed/performance, storage, IO amplification, and CPU usage. For more +# performance but less compression (more storage used) and less CPU usage, +# use LZ4. +# +# For more details, see: +# https://github.com/facebook/rocksdb/wiki/Compression +# +# "none" will disable compression. +# +#rocksdb_compression_algo = "zstd" + +# Level of compression the specified compression algorithm for RocksDB to +# use. +# +# Default is 32767, which is internally read by RocksDB as the default +# magic number and translated to the library's default compression level +# as they all differ. See their `kDefaultCompressionLevel`. +# +#rocksdb_compression_level = 32767 + +# Level of compression the specified compression algorithm for the +# bottommost level/data for RocksDB to use. Default is 32767, which is +# internally read by RocksDB as the default magic number and translated to +# the library's default compression level as they all differ. See their +# `kDefaultCompressionLevel`. +# +# Since this is the bottommost level (generally old and least used data), +# it may be desirable to have a very high compression level here as it's +# less likely for this data to be used. Research your chosen compression +# algorithm. +# +#rocksdb_bottommost_compression_level = 32767 + +# Whether to enable RocksDB's "bottommost_compression". +# +# At the expense of more CPU usage, this will further compress the +# database to reduce more storage. It is recommended to use ZSTD +# compression with this for best compression results. This may be useful +# if you're trying to reduce storage usage from the database. +# +# See https://github.com/facebook/rocksdb/wiki/Compression for more details. +# +#rocksdb_bottommost_compression = false + +# Database recovery mode (for RocksDB WAL corruption). +# +# Use this option when the server reports corruption and refuses to start. +# Set mode 2 (PointInTime) to cleanly recover from this corruption. The +# server will continue from the last good state, several seconds or +# minutes prior to the crash. Clients may have to run "clear-cache & +# reload" to account for the rollback. Upon success, you may reset the +# mode back to default and restart again. Please note in some cases the +# corruption error may not be cleared for at least 30 minutes of operation +# in PointInTime mode. +# +# As a very last ditch effort, if PointInTime does not fix or resolve +# anything, you can try mode 3 (SkipAnyCorruptedRecord) but this will +# leave the server in a potentially inconsistent state. +# +# The default mode 1 (TolerateCorruptedTailRecords) will automatically +# drop the last entry in the database if corrupted during shutdown, but +# nothing more. It is extraordinarily unlikely this will desynchronize +# clients. To disable any form of silent rollback set mode 0 +# (AbsoluteConsistency). +# +# The options are: +# 0 = AbsoluteConsistency +# 1 = TolerateCorruptedTailRecords (default) +# 2 = PointInTime (use me if trying to recover) +# 3 = SkipAnyCorruptedRecord (you now voided your Conduwuit warranty) +# +# For more information on these modes, see: +# https://github.com/facebook/rocksdb/wiki/WAL-Recovery-Modes +# +# For more details on recovering a corrupt database, see: +# https://conduwuit.puppyirl.gay/troubleshooting.html#database-corruption +# +#rocksdb_recovery_mode = 1 + +# Enables or disables paranoid SST file checks. This can improve RocksDB +# database consistency at a potential performance impact due to further +# safety checks ran. +# +# For more information, see: +# https://github.com/facebook/rocksdb/wiki/Online-Verification#columnfamilyoptionsparanoid_file_checks +# +#rocksdb_paranoid_file_checks = false + +# Database repair mode (for RocksDB SST corruption). +# +# Use this option when the server reports corruption while running or +# panics. If the server refuses to start use the recovery mode options +# first. Corruption errors containing the acronym 'SST' which occur after +# startup will likely require this option. +# +# - Backing up your database directory is recommended prior to running the +# repair. +# +# - Disabling repair mode and restarting the server is recommended after +# running the repair. +# +# See https://conduwuit.puppyirl.gay/troubleshooting.html#database-corruption for more details on recovering a corrupt database. +# +#rocksdb_repair = false + +# This item is undocumented. Please contribute documentation for it. +# +#rocksdb_read_only = false + +# This item is undocumented. Please contribute documentation for it. +# +#rocksdb_secondary = false + +# Enables idle CPU priority for compaction thread. This is not enabled by +# default to prevent compaction from falling too far behind on busy +# systems. +# +#rocksdb_compaction_prio_idle = false + +# Enables idle IO priority for compaction thread. This prevents any +# unexpected lag in the server's operation and is usually a good idea. +# Enabled by default. +# +#rocksdb_compaction_ioprio_idle = true + +# Disables RocksDB compaction. You should never ever have to set this +# option to true. If you for some reason find yourself needing to use this +# option as part of troubleshooting or a bug, please reach out to us in +# the conduwuit Matrix room with information and details. +# +# Disabling compaction will lead to a significantly bloated and +# explosively large database, gradually poor performance, unnecessarily +# excessive disk read/writes, and slower shutdowns and startups. +# +#rocksdb_compaction = true + +# Level of statistics collection. Some admin commands to display database +# statistics may require this option to be set. Database performance may +# be impacted by higher settings. +# +# Option is a number ranging from 0 to 6: +# 0 = No statistics. +# 1 = No statistics in release mode (default). +# 2 to 3 = Statistics with no performance impact. +# 3 to 5 = Statistics with possible performance impact. +# 6 = All statistics. +# +#rocksdb_stats_level = 1 + +# This is a password that can be configured that will let you login to the +# server bot account (currently `@conduit`) for emergency troubleshooting +# purposes such as recovering/recreating your admin room, or inviting +# yourself back. +# +# See https://conduwuit.puppyirl.gay/troubleshooting.html#lost-access-to-admin-room for other ways to get back into your admin room. +# +# Once this password is unset, all sessions will be logged out for +# security purposes. +# +# example: "F670$2CP@Hw8mG7RY1$%!#Ic7YA" +# +emergency_password = {{ matrix_conduwuit_config_emergency_password | to_json }} + +# This item is undocumented. Please contribute documentation for it. +# +#notification_push_path = "/_matrix/push/v1/notify" + +# Allow local (your server only) presence updates/requests. +# +# Note that presence on conduwuit is very fast unlike Synapse's. If using +# outgoing presence, this MUST be enabled. +# +#allow_local_presence = true + +# Allow incoming federated presence updates/requests. +# +# This option receives presence updates from other servers, but does not +# send any unless `allow_outgoing_presence` is true. Note that presence on +# conduwuit is very fast unlike Synapse's. +# +#allow_incoming_presence = true + +# Allow outgoing presence updates/requests. +# +# This option sends presence updates to other servers, but does not +# receive any unless `allow_incoming_presence` is true. Note that presence +# on conduwuit is very fast unlike Synapse's. If using outgoing presence, +# you MUST enable `allow_local_presence` as well. +# +#allow_outgoing_presence = true + +# How many seconds without presence updates before you become idle. +# Defaults to 5 minutes. +# +#presence_idle_timeout_s = 300 + +# How many seconds without presence updates before you become offline. +# Defaults to 30 minutes. +# +#presence_offline_timeout_s = 1800 + +# Enable the presence idle timer for remote users. +# +# Disabling is offered as an optimization for servers participating in +# many large rooms or when resources are limited. Disabling it may cause +# incorrect presence states (i.e. stuck online) to be seen for some remote +# users. +# +#presence_timeout_remote_users = true + +# Allow receiving incoming read receipts from remote servers. +# +#allow_incoming_read_receipts = true + +# Allow sending read receipts to remote servers. +# +#allow_outgoing_read_receipts = true + +# Allow outgoing typing updates to federation. +# +#allow_outgoing_typing = true + +# Allow incoming typing updates from federation. +# +#allow_incoming_typing = true + +# Maximum time federation user can indicate typing. +# +#typing_federation_timeout_s = 30 + +# Minimum time local client can indicate typing. This does not override a +# client's request to stop typing. It only enforces a minimum value in +# case of no stop request. +# +#typing_client_timeout_min_s = 15 + +# Maximum time local client can indicate typing. +# +#typing_client_timeout_max_s = 45 + +# Set this to true for conduwuit to compress HTTP response bodies using +# zstd. This option does nothing if conduwuit was not built with +# `zstd_compression` feature. Please be aware that enabling HTTP +# compression may weaken TLS. Most users should not need to enable this. +# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH +# before deciding to enable this. +# +#zstd_compression = false + +# Set this to true for conduwuit to compress HTTP response bodies using +# gzip. This option does nothing if conduwuit was not built with +# `gzip_compression` feature. Please be aware that enabling HTTP +# compression may weaken TLS. Most users should not need to enable this. +# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH before +# deciding to enable this. +# +# If you are in a large amount of rooms, you may find that enabling this +# is necessary to reduce the significantly large response bodies. +# +#gzip_compression = false + +# Set this to true for conduwuit to compress HTTP response bodies using +# brotli. This option does nothing if conduwuit was not built with +# `brotli_compression` feature. Please be aware that enabling HTTP +# compression may weaken TLS. Most users should not need to enable this. +# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH +# before deciding to enable this. +# +#brotli_compression = false + +# Set to true to allow user type "guest" registrations. Some clients like +# Element attempt to register guest users automatically. +# +#allow_guest_registration = false + +# Set to true to log guest registrations in the admin room. Note that +# these may be noisy or unnecessary if you're a public homeserver. +# +#log_guest_registrations = false + +# Set to true to allow guest registrations/users to auto join any rooms +# specified in `auto_join_rooms`. +# +#allow_guests_auto_join_rooms = false + +# Enable the legacy unauthenticated Matrix media repository endpoints. +# These endpoints consist of: +# - /_matrix/media/*/config +# - /_matrix/media/*/upload +# - /_matrix/media/*/preview_url +# - /_matrix/media/*/download/* +# - /_matrix/media/*/thumbnail/* +# +# The authenticated equivalent endpoints are always enabled. +# +# Defaults to true for now, but this is highly subject to change, likely +# in the next release. +# +#allow_legacy_media = true + +# This item is undocumented. Please contribute documentation for it. +# +#freeze_legacy_media = true + +# Check consistency of the media directory at startup: +# 1. When `media_compat_file_link` is enabled, this check will upgrade +# media when switching back and forth between Conduit and conduwuit. +# Both options must be enabled to handle this. +# 2. When media is deleted from the directory, this check will also delete +# its database entry. +# +# If none of these checks apply to your use cases, and your media +# directory is significantly large setting this to false may reduce +# startup time. +# +#media_startup_check = true + +# Enable backward-compatibility with Conduit's media directory by creating +# symlinks of media. +# +# This option is only necessary if you plan on using Conduit again. +# Otherwise setting this to false reduces filesystem clutter and overhead +# for managing these symlinks in the directory. This is now disabled by +# default. You may still return to upstream Conduit but you have to run +# conduwuit at least once with this set to true and allow the +# media_startup_check to take place before shutting down to return to +# Conduit. +# +#media_compat_file_link = false + +# Prune missing media from the database as part of the media startup +# checks. +# +# This means if you delete files from the media directory the +# corresponding entries will be removed from the database. This is +# disabled by default because if the media directory is accidentally moved +# or inaccessible, the metadata entries in the database will be lost with +# sadness. +# +#prune_missing_media = false + +# Vector list of servers that conduwuit will refuse to download remote +# media from. +# +#prevent_media_downloads_from = [] + +# List of forbidden server names that we will block incoming AND outgoing +# federation with, and block client room joins / remote user invites. +# +# This check is applied on the room ID, room alias, sender server name, +# sender user's server name, inbound federation X-Matrix origin, and +# outbound federation handler. +# +# Basically "global" ACLs. +# +#forbidden_remote_server_names = [] + +# List of forbidden server names that we will block all outgoing federated +# room directory requests for. Useful for preventing our users from +# wandering into bad servers or spaces. +# +#forbidden_remote_room_directory_server_names = [] + +# Vector list of IPv4 and IPv6 CIDR ranges / subnets *in quotes* that you +# do not want conduwuit to send outbound requests to. Defaults to +# RFC1918, unroutable, loopback, multicast, and testnet addresses for +# security. +# +# Please be aware that this is *not* a guarantee. You should be using a +# firewall with zones as doing this on the application layer may have +# bypasses. +# +# Currently this does not account for proxies in use like Synapse does. +# +# To disable, set this to be an empty vector (`[]`). +# +# Defaults to: +# ["127.0.0.0/8", "10.0.0.0/8", "172.16.0.0/12", +# "192.168.0.0/16", "100.64.0.0/10", "192.0.0.0/24", "169.254.0.0/16", +# "192.88.99.0/24", "198.18.0.0/15", "192.0.2.0/24", "198.51.100.0/24", +# "203.0.113.0/24", "224.0.0.0/4", "::1/128", "fe80::/10", "fc00::/7", +# "2001:db8::/32", "ff00::/8", "fec0::/10"] +# +#ip_range_denylist = + +# Optional IP address or network interface-name to bind as the source of +# URL preview requests. If not set, it will not bind to a specific +# address or interface. +# +# Interface names only supported on Linux, Android, and Fuchsia platforms; +# all other platforms can specify the IP address. To list the interfaces +# on your system, use the command `ip link show`. +# +# example: `"eth0"` or `"1.2.3.4"` +# +#url_preview_bound_interface = + +# Vector list of domains allowed to send requests to for URL previews. +# +# This is a *contains* match, not an explicit match. Putting "google.com" +# will match "https://google.com" and +# "http://mymaliciousdomainexamplegoogle.com" Setting this to "*" will +# allow all URL previews. Please note that this opens up significant +# attack surface to your server, you are expected to be aware of the risks +# by doing so. +# +#url_preview_domain_contains_allowlist = [] + +# Vector list of explicit domains allowed to send requests to for URL +# previews. +# +# This is an *explicit* match, not a contains match. Putting "google.com" +# will match "https://google.com", "http://google.com", but not +# "https://mymaliciousdomainexamplegoogle.com". Setting this to "*" will +# allow all URL previews. Please note that this opens up significant +# attack surface to your server, you are expected to be aware of the risks +# by doing so. +# +#url_preview_domain_explicit_allowlist = [] + +# Vector list of explicit domains not allowed to send requests to for URL +# previews. +# +# This is an *explicit* match, not a contains match. Putting "google.com" +# will match "https://google.com", "http://google.com", but not +# "https://mymaliciousdomainexamplegoogle.com". The denylist is checked +# first before allowlist. Setting this to "*" will not do anything. +# +#url_preview_domain_explicit_denylist = [] + +# Vector list of URLs allowed to send requests to for URL previews. +# +# Note that this is a *contains* match, not an explicit match. Putting +# "google.com" will match "https://google.com/", +# "https://google.com/url?q=https://mymaliciousdomainexample.com", and +# "https://mymaliciousdomainexample.com/hi/google.com" Setting this to "*" +# will allow all URL previews. Please note that this opens up significant +# attack surface to your server, you are expected to be aware of the risks +# by doing so. +# +#url_preview_url_contains_allowlist = [] + +# Maximum amount of bytes allowed in a URL preview body size when +# spidering. Defaults to 256KB in bytes. +# +#url_preview_max_spider_size = 256000 + +# Option to decide whether you would like to run the domain allowlist +# checks (contains and explicit) on the root domain or not. Does not apply +# to URL contains allowlist. Defaults to false. +# +# Example usecase: If this is enabled and you have "wikipedia.org" allowed +# in the explicit and/or contains domain allowlist, it will allow all +# subdomains under "wikipedia.org" such as "en.m.wikipedia.org" as the +# root domain is checked and matched. Useful if the domain contains +# allowlist is still too broad for you but you still want to allow all the +# subdomains under a root domain. +# +#url_preview_check_root_domain = false + +# List of forbidden room aliases and room IDs as strings of regex +# patterns. +# +# Regex can be used or explicit contains matches can be done by just +# specifying the words (see example). +# +# This is checked upon room alias creation, custom room ID creation if +# used, and startup as warnings if any room aliases in your database have +# a forbidden room alias/ID. +# +# example: ["19dollarfortnitecards", "b[4a]droom"] +# +#forbidden_alias_names = [] + +# List of forbidden username patterns/strings. +# +# Regex can be used or explicit contains matches can be done by just +# specifying the words (see example). +# +# This is checked upon username availability check, registration, and +# startup as warnings if any local users in your database have a forbidden +# username. +# +# example: ["administrator", "b[a4]dusernam[3e]"] +# +#forbidden_usernames = [] + +# Retry failed and incomplete messages to remote servers immediately upon +# startup. This is called bursting. If this is disabled, said messages may +# not be delivered until more messages are queued for that server. Do not +# change this option unless server resources are extremely limited or the +# scale of the server's deployment is huge. Do not disable this unless you +# know what you are doing. +# +#startup_netburst = true + +# Messages are dropped and not reattempted. The `startup_netburst` option +# must be enabled for this value to have any effect. Do not change this +# value unless you know what you are doing. Set this value to -1 to +# reattempt every message without trimming the queues; this may consume +# significant disk. Set this value to 0 to drop all messages without any +# attempt at redelivery. +# +#startup_netburst_keep = 50 + +# Block non-admin local users from sending room invites (local and +# remote), and block non-admin users from receiving remote room invites. +# +# Admins are always allowed to send and receive all room invites. +# +#block_non_admin_invites = false + +# Allow admins to enter commands in rooms other than "#admins" (admin +# room) by prefixing your message with "\!admin" or "\\!admin" followed up +# a normal conduwuit admin command. The reply will be publicly visible to +# the room, originating from the sender. +# +# example: \\!admin debug ping puppygock.gay +# +#admin_escape_commands = true + +# Automatically activate the conduwuit admin room console / CLI on +# startup. This option can also be enabled with `--console` conduwuit +# argument. +# +#admin_console_automatic = false + +# List of admin commands to execute on startup. +# +# This option can also be configured with the `--execute` conduwuit +# argument and can take standard shell commands and environment variables +# +# For example: `./conduwuit --execute "server admin-notice conduwuit has +# started up at $(date)"` +# +# example: admin_execute = ["debug ping puppygock.gay", "debug echo hi"]` +# +#admin_execute = [] + +# Ignore errors in startup commands. +# +# If false, conduwuit will error and fail to start if an admin execute +# command (`--execute` / `admin_execute`) fails. +# +#admin_execute_errors_ignore = false + +# Controls the max log level for admin command log captures (logs +# generated from running admin commands). Defaults to "info" on release +# builds, else "debug" on debug builds. +# +#admin_log_capture = "info" + +# The default room tag to apply on the admin room. +# +# On some clients like Element, the room tag "m.server_notice" is a +# special pinned room at the very bottom of your room list. The conduwuit +# admin room can be pinned here so you always have an easy-to-access +# shortcut dedicated to your admin room. +# +#admin_room_tag = "m.server_notice" + +# Sentry.io crash/panic reporting, performance monitoring/metrics, etc. +# This is NOT enabled by default. conduwuit's default Sentry reporting +# endpoint domain is `o4506996327251968.ingest.us.sentry.io`. +# +#sentry = false + +# Sentry reporting URL, if a custom one is desired. +# +#sentry_endpoint = "https://fe2eb4536aa04949e28eff3128d64757@o4506996327251968.ingest.us.sentry.io/4506996334657536" + +# Report your conduwuit server_name in Sentry.io crash reports and +# metrics. +# +#sentry_send_server_name = false + +# Performance monitoring/tracing sample rate for Sentry.io. +# +# Note that too high values may impact performance, and can be disabled by +# setting it to 0.0 (0%) This value is read as a percentage to Sentry, +# represented as a decimal. Defaults to 15% of traces (0.15) +# +#sentry_traces_sample_rate = 0.15 + +# Whether to attach a stacktrace to Sentry reports. +# +#sentry_attach_stacktrace = false + +# Send panics to Sentry. This is true by default, but Sentry has to be +# enabled. The global `sentry` config option must be enabled to send any +# data. +# +#sentry_send_panic = true + +# Send errors to sentry. This is true by default, but sentry has to be +# enabled. This option is only effective in release-mode; forced to false +# in debug-mode. +# +#sentry_send_error = true + +# Controls the tracing log level for Sentry to send things like +# breadcrumbs and transactions +# +#sentry_filter = "info" + +# Enable the tokio-console. This option is only relevant to developers. +# +# For more information, see: +# https://conduwuit.puppyirl.gay/development.html#debugging-with-tokio-console +# +#tokio_console = false + +# This item is undocumented. Please contribute documentation for it. +# +#test = false + +# Controls whether admin room notices like account registrations, password +# changes, account deactivations, room directory publications, etc will be +# sent to the admin room. Update notices and normal admin command +# responses will still be sent. +# +#admin_room_notices = true + +# Enable database pool affinity support. On supporting systems, block +# device queue topologies are detected and the request pool is optimized +# for the hardware; db_pool_workers is determined automatically. +# +#db_pool_affinity = true + +# Sets the number of worker threads in the frontend-pool of the database. +# This number should reflect the I/O capabilities of the system, +# such as the queue-depth or the number of simultaneous requests in +# flight. Defaults to 32 or four times the number of CPU cores, whichever +# is greater. +# +# Note: This value is only used if db_pool_affinity is disabled or not +# detected on the system, otherwise it is determined automatically. +# +#db_pool_workers = 32 + +# When db_pool_affinity is enabled and detected, the size of any worker +# group will not exceed the determined value. This is necessary when +# thread-pooling approach does not scale to the full capabilities of +# high-end hardware; using detected values without limitation could +# degrade performance. +# +# The value is multiplied by the number of cores which share a device +# queue, since group workers can be scheduled on any of those cores. +# +#db_pool_workers_limit = 64 + +# Determines the size of the queues feeding the database's frontend-pool. +# The size of the queue is determined by multiplying this value with the +# number of pool workers. When this queue is full, tokio tasks conducting +# requests will yield until space is available; this is good for +# flow-control by avoiding buffer-bloat, but can inhibit throughput if +# too low. +# +#db_pool_queue_mult = 4 + +# Sets the initial value for the concurrency of streams. This value simply +# allows overriding the default in the code. The default is 32, which is +# the same as the default in the code. Note this value is itself +# overridden by the computed stream_width_scale, unless that is disabled; +# this value can serve as a fixed-width instead. +# +#stream_width_default = 32 + +# Scales the stream width starting from a base value detected for the +# specific system. The base value is the database pool worker count +# determined from the hardware queue size (e.g. 32 for SSD or 64 or 128+ +# for NVMe). This float allows scaling the width up or down by multiplying +# it (e.g. 1.5, 2.0, etc). The maximum result can be the size of the pool +# queue (see: db_pool_queue_mult) as any larger value will stall the tokio +# task. The value can also be scaled down (e.g. 0.5) to improve +# responsiveness for many users at the cost of throughput for each. +# +# Setting this value to 0.0 causes the stream width to be fixed at the +# value of stream_width_default. The default scale is 1.0 to match the +# capabilities detected for the system. +# +#stream_width_scale = 1.0 + +# Sets the initial amplification factor. This controls batch sizes of +# requests made by each pool worker, multiplying the throughput of each +# stream. This value is somewhat abstract from specific hardware +# characteristics and can be significantly larger than any thread count or +# queue size. This is because each database query may require several +# index lookups, thus many database queries in a batch may make progress +# independently while also sharing index and data blocks which may or may +# not be cached. It is worthwhile to submit huge batches to reduce +# complexity. The maximum value is 32768, though sufficient hardware is +# still advised for that. +# +#stream_amplification = 1024 + +# Number of sender task workers; determines sender parallelism. Default is +# '0' which means the value is determined internally, likely matching the +# number of tokio worker-threads or number of cores, etc. Override by +# setting a non-zero value. +# +#sender_workers = 0 + +[global.well_known] + +# The server URL that the client well-known file will serve. This should +# not contain a port, and should just be a valid HTTPS URL. +# +# example: "https://matrix.example.com" +# +#client = + +# The server base domain of the URL with a specific port that the server +# well-known file will serve. This should contain a port at the end, and +# should not be a URL. +# +# example: "matrix.example.com:443" +# +#server = + +# This item is undocumented. Please contribute documentation for it. +# +#support_page = + +# This item is undocumented. Please contribute documentation for it. +# +#support_role = + +# This item is undocumented. Please contribute documentation for it. +# +#support_email = + +# This item is undocumented. Please contribute documentation for it. +# +#support_mxid = diff --git a/roles/custom/matrix-conduwuit/templates/env.j2 b/roles/custom/matrix-conduwuit/templates/env.j2 new file mode 100644 index 000000000..026bfe308 --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/env.j2 @@ -0,0 +1 @@ +{{ matrix_conduwuit_environment_variables_extension }} diff --git a/roles/custom/matrix-conduwuit/templates/labels.j2 b/roles/custom/matrix-conduwuit/templates/labels.j2 index 13ab1487c..9ef9db4f8 100644 --- a/roles/custom/matrix-conduwuit/templates/labels.j2 +++ b/roles/custom/matrix-conduwuit/templates/labels.j2 @@ -5,7 +5,7 @@ traefik.enable=true traefik.docker.network={{ matrix_conduwuit_container_labels_traefik_docker_network }} {% endif %} -traefik.http.services.matrix-conduwuit.loadbalancer.server.port={{ matrix_conduwuit_port_number }} +traefik.http.services.matrix-conduwuit.loadbalancer.server.port={{ matrix_conduwuit_config_port_number }} {% if matrix_conduwuit_container_labels_public_client_root_enabled %} @@ -129,6 +129,37 @@ traefik.http.routers.matrix-conduwuit-public-federation-api.tls.certResolver={{ {% endif %} + + +{% if matrix_conduwuit_container_labels_public_conduwuit_api_enabled %} +############################################################ +# # +# Public Conduwuit-API (/_conduwuit) # +# # +############################################################ + +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.rule={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_rule }} + +{% if matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority | int > 0 %} +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.priority={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.service=matrix-conduwuit +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.entrypoints={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints }} + +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.tls={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls | to_json }} +{% if matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls %} +traefik.http.routers.matrix-conduwuit-public-conduwuit-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Public Conduwuit-API (/_conduwuit) # +# # +############################################################ +{% endif %} + + {% endif %} {{ matrix_conduwuit_container_labels_additional_labels }} diff --git a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 index 54b5cc7a5..5291e33a8 100644 --- a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 +++ b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 @@ -1,6 +1,6 @@ #jinja2: lstrip_blocks: "True" [Unit] -Description=Conduwuit Matrix homeserver +Description=conduwuit Matrix homeserver {% for service in matrix_conduwuit_systemd_required_services_list %} Requires={{ service }} After={{ service }} @@ -21,10 +21,10 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --read-only \ --tmpfs=/tmp:rw,noexec,nosuid,size={{ matrix_conduwuit_tmp_directory_size_mb }}m \ --network={{ matrix_conduwuit_container_network }} \ - --env conduwuit_CONFIG=/etc/matrix-conduwuit/conduwuit.toml \ + --env CONDUWUIT_CONFIG=/etc/conduwuit/conduwuit.toml \ --label-file={{ matrix_conduwuit_base_path }}/labels \ - --mount type=bind,src={{ matrix_conduwuit_data_path }},dst=/var/lib/matrix-conduwuit \ - --mount type=bind,src={{ matrix_conduwuit_config_path }},dst=/etc/matrix-conduwuit,ro \ + --mount type=bind,src={{ matrix_conduwuit_data_path }},dst=/var/lib/conduwuit \ + --mount type=bind,src={{ matrix_conduwuit_config_path }},dst=/etc/conduwuit,ro \ {% for arg in matrix_conduwuit_container_extra_arguments %} {{ arg }} \ {% endfor %} diff --git a/roles/custom/matrix-conduwuit/vars/main.yml b/roles/custom/matrix-conduwuit/vars/main.yml index 7d26a504b..02684574c 100644 --- a/roles/custom/matrix-conduwuit/vars/main.yml +++ b/roles/custom/matrix-conduwuit/vars/main.yml @@ -1,3 +1,4 @@ --- + matrix_conduwuit_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}/_matrix/client/versions" matrix_conduwuit_federation_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}:{{ matrix_federation_public_port }}/_matrix/federation/v1/version" diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 6e9b63d54..b3b792a78 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -302,14 +302,6 @@ - {'old': 'matrix_nginx_proxy_proxy_conduit_federation_api_addr_with_container', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_conduit_federation_api_addr_sans_container', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_conduit_additional_server_configuration_blocks', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_enabled', 'new': 'matrix_conduwuit_container_labels_traefik_enabled'} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_block_federation_api_on_client_port', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_enabled', 'new': 'matrix_conduwuit_container_labels_public_federation_api_enabled'} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_client_api_addr_with_container', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_client_api_addr_sans_container', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_addr_with_container', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_federation_api_addr_sans_container', 'new': ''} - - {'old': 'matrix_nginx_proxy_proxy_conduwuit_additional_server_configuration_blocks', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_dendrite_enabled', 'new': 'matrix_dendrite_container_labels_traefik_enabled'} - {'old': 'matrix_nginx_proxy_proxy_dendrite_block_federation_api_on_client_port', 'new': ''} - {'old': 'matrix_nginx_proxy_proxy_dendrite_federation_api_enabled', 'new': 'matrix_dendrite_container_labels_public_federation_api_enabled'} From 1fe8b4975580ee4e399f23eabbf4b63f19298b73 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 16:15:36 +0200 Subject: [PATCH 231/952] Mention Conduwuit in a few more places in the documentation Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3967 --- docs/configuring-playbook.md | 2 ++ docs/container-images.md | 1 + docs/howto-srv-server-delegation.md | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 2325aea66..98d182122 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -35,6 +35,8 @@ For a more custom setup, see the [Other configuration options](#other-configurat - [Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation + - [Configuring Conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation + - [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation - Server components: diff --git a/docs/container-images.md b/docs/container-images.md index e2fd67d1a..2a38b2bd4 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -10,6 +10,7 @@ We try to stick to official images (provided by their respective projects) as mu | ------- | --------------- | -------- | ----------- | | [Synapse](configuring-playbook-synapse.md) | [element-hq/synapse](https://ghcr.io/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | | [Conduit](configuring-playbook-conduit.md) | [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | +| [Conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. | | [Dendrite](configuring-playbook-dendrite.md) | [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | ## Clients diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index 47659d624..7cf484712 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -18,7 +18,7 @@ The up-to-date list can be accessed on [traefik's documentation](https://doc.tra **Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels: -- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md)) +- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [Conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md)) - if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached Also, all instructions below are from an older version of the playbook and may not work anymore. From aafd2df066be9d657895d05c1d1dfcb45ad7a4c6 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 19 Jan 2025 16:19:19 +0200 Subject: [PATCH 232/952] Announce Conduwuit support Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3967 --- CHANGELOG.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ebce4eaaa..a31ce22ff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,18 @@ +# 2025-01-19 + +## Conduwuit support + +Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations. + +Conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). + +Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook. + +To try out Conduwuit, we recommend that you **use a new server**. Refer to our [Configuring Conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details. + +**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Conduwuit) without data loss. + + # 2025-01-14 ## (Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13 From ba19e4d303e2e3c7f9c1ee8b9ba48ff55c3c3992 Mon Sep 17 00:00:00 2001 From: Catalan Lover Date: Sun, 19 Jan 2025 18:14:05 +0100 Subject: [PATCH 233/952] Replace Discharge with Disable In the context of disabling rate limits on an API its disable that is correct. We arent talking about controlling the discharge rate of a battery we dont want to blow up or harm. We are talking about matrix APIs and disabling the rate limiter on them. --- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 58c15b1af..288cc4104 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -87,7 +87,7 @@ The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/syna **Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). -To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: +To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: ```sh curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index c7a211491..2564cd2f9 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -42,7 +42,7 @@ The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/syna **Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). -To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: +To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: ```sh curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit From f987d295eee041c36dda91398dfe7a0880ac2276 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 10:32:19 -0500 Subject: [PATCH 234/952] Update docs for Draupnir, D4A, and Mjolnir: adopt the common section "Extending the configuration" Also: fix the variable "matrix_appservice_draupnir_for_all_configuration_yaml" Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-appservice-draupnir-for-all.md | 12 ++++++++---- docs/configuring-playbook-bot-draupnir.md | 6 +++++- docs/configuring-playbook-bot-mjolnir.md | 6 +++++- 3 files changed, 18 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index be7aacc30..f9d7f650e 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -46,19 +46,23 @@ matrix_appservice_draupnir_for_all_master_control_room_alias: "MANAGEMENT_ROOM_A ### Extending the configuration -You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable. +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `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 For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `vars.yml` file: ```yaml -matrix_appservice_draupnir_for_all_extension_yaml: | +matrix_appservice_draupnir_for_all_configuration_extension_yaml: | # Your custom YAML configuration goes here. - # This configuration extends the default starting configuration (`matrix_appservice_draupnir_for_all_yaml`). + # This configuration extends the default starting configuration (`matrix_appservice_draupnir_for_all_configuration_yaml`). # # You can override individual variables from the default configuration, or introduce new ones. # # If you need something more special, you can take full control by - # completely redefining `matrix_appservice_draupnir_for_all_yaml`. + # completely redefining `matrix_appservice_draupnir_for_all_configuration_yaml`. protectAllJoinedRooms: true ``` diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 288cc4104..3fb7298ea 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -117,7 +117,11 @@ The other method polls an Synapse Admin API endpoint, hence it is available only ### Extending the configuration -You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable. +There are some additional things you may wish to configure about the bot. + +Take a look at: + +- `roles/custom/matrix-bot-draupnir/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_draupnir_configuration_extension_yaml` variable For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file: diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 2564cd2f9..0702fb992 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -131,7 +131,11 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: [] ### Extending the configuration -You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file. +There are some additional things you may wish to configure about the bot. + +Take a look at: + +- `roles/custom/matrix-bot-mjolnir/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_mjolnir_configuration_extension_yaml` variable For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file: From 8ba607a76ab6fb13fabe0aeebb5124b61aa915de Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 12:38:14 +0900 Subject: [PATCH 235/952] =?UTF-8?q?Change=20capitalization=20per=20author'?= =?UTF-8?q?s=20preference:=20Conduwuit=20=E2=86=92=20conduwuit?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit See: https://github.com/girlbossceo/conduwuit/commit/e8508d16e1f5686881c40ba5b54f7a1a87cbe7e9 Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 10 +++++----- README.md | 2 +- docs/configuring-playbook-conduit.md | 2 +- docs/configuring-playbook-conduwuit.md | 16 ++++++++-------- docs/configuring-playbook.md | 2 +- docs/container-images.md | 2 +- docs/howto-srv-server-delegation.md | 2 +- .../tasks/self_check_client_api.yml | 2 +- .../matrix-conduwuit/templates/conduwuit.toml.j2 | 2 +- .../custom/matrix-conduwuit/templates/labels.j2 | 4 ++-- .../util/ensure_user_registered_conduwuit.yml | 4 ++-- 11 files changed, 24 insertions(+), 24 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a31ce22ff..bd098a3dd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,16 +1,16 @@ # 2025-01-19 -## Conduwuit support +## conduwuit support -Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations. +Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations. -Conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). +conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook. -To try out Conduwuit, we recommend that you **use a new server**. Refer to our [Configuring Conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details. +To try out conduwuit, we recommend that you **use a new server**. Refer to our [Configuring conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details. -**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Conduwuit) without data loss. +**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to conduwuit) without data loss. # 2025-01-14 diff --git a/README.md b/README.md index ee1c5a144..d3e2a4dbc 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow | ---- | -------- | ----------- | ------------- | | [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) | | [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) | -| [Conduwuit](https://conduwuit.puppyirl.gay/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. | [Link](docs/configuring-playbook-conduwuit.md) | +| [conduwuit](https://conduwuit.puppyirl.gay/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit. | [Link](docs/configuring-playbook-conduwuit.md) | | [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) | ### Clients diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 81ac48ee5..f2fc70096 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -6,7 +6,7 @@ See the project's [documentation](https://docs.conduit.rs/) to learn what it doe By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. -💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [Conduwuit](./configuring-playbook-conduwuit.md). +💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md). ⚠️ **Warnings**: diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md index 512f4530b..71cedbb5f 100644 --- a/docs/configuring-playbook-conduwuit.md +++ b/docs/configuring-playbook-conduwuit.md @@ -1,22 +1,22 @@ -# Configuring Conduwuit (optional) +# Configuring conduwuit (optional) -The playbook can install and configure the [Conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you. +The playbook can install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you. See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you. By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. -💡 **Note**: Conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). +💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). ⚠️ **Warnings**: -- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. +- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration -To use Conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below: +To use conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below: ```yaml matrix_homeserver_implementation: conduwuit @@ -51,7 +51,7 @@ matrix_conduwuit_environment_variables_extension: | ## Creating the first user account -Unlike other homeserver implementations (like Synapse and Dendrite), Conduwuit does not support creating users via the command line or via the playbook. +Unlike other homeserver implementations (like Synapse and Dendrite), conduwuit does not support creating users via the command line or via the playbook. If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token. @@ -64,9 +64,9 @@ The **first user account that you create will be marked as an admin** and **will For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver. -For Conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account. +For conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account. -The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to Conduwuit's historical legacy. +The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to conduwuit's historical legacy. Your first user account would already have been invited to an admin room with this bot. Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 98d182122..7836190f8 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -35,7 +35,7 @@ For a more custom setup, see the [Other configuration options](#other-configurat - [Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation - - [Configuring Conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation + - [Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation - [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation diff --git a/docs/container-images.md b/docs/container-images.md index 2a38b2bd4..4f77a7bc6 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -10,7 +10,7 @@ We try to stick to official images (provided by their respective projects) as mu | ------- | --------------- | -------- | ----------- | | [Synapse](configuring-playbook-synapse.md) | [element-hq/synapse](https://ghcr.io/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | | [Conduit](configuring-playbook-conduit.md) | [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | -| [Conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. | +| [conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit. | | [Dendrite](configuring-playbook-dendrite.md) | [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | ## Clients diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index 7cf484712..3d83dd86a 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -18,7 +18,7 @@ The up-to-date list can be accessed on [traefik's documentation](https://doc.tra **Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels: -- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [Conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md)) +- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md)) - if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached Also, all instructions below are from an older version of the playbook and may not work anymore. diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml index a34c14fb4..19da0161b 100644 --- a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml +++ b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml @@ -14,7 +14,7 @@ - name: Fail if Matrix Client API not working ansible.builtin.fail: - msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`). Is Conduwuit running? Is port 443 open in your firewall? Full error: {{ result_matrix_conduwuit_client_api }}" + msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`). Is conduwuit running? Is port 443 open in your firewall? Full error: {{ result_matrix_conduwuit_client_api }}" when: "matrix_conduwuit_enabled | bool and (result_matrix_conduwuit_client_api.failed or 'json' not in result_matrix_conduwuit_client_api)" - name: Report working Matrix Client API diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 index 4b011448c..86c1ac255 100644 --- a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 +++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 @@ -870,7 +870,7 @@ turn_password = {{ matrix_conduwuit_config_turn_password | to_json }} # 0 = AbsoluteConsistency # 1 = TolerateCorruptedTailRecords (default) # 2 = PointInTime (use me if trying to recover) -# 3 = SkipAnyCorruptedRecord (you now voided your Conduwuit warranty) +# 3 = SkipAnyCorruptedRecord (you now voided your conduwuit warranty) # # For more information on these modes, see: # https://github.com/facebook/rocksdb/wiki/WAL-Recovery-Modes diff --git a/roles/custom/matrix-conduwuit/templates/labels.j2 b/roles/custom/matrix-conduwuit/templates/labels.j2 index 9ef9db4f8..4a268c366 100644 --- a/roles/custom/matrix-conduwuit/templates/labels.j2 +++ b/roles/custom/matrix-conduwuit/templates/labels.j2 @@ -134,7 +134,7 @@ traefik.http.routers.matrix-conduwuit-public-federation-api.tls.certResolver={{ {% if matrix_conduwuit_container_labels_public_conduwuit_api_enabled %} ############################################################ # # -# Public Conduwuit-API (/_conduwuit) # +# Public conduwuit-API (/_conduwuit) # # # ############################################################ @@ -154,7 +154,7 @@ traefik.http.routers.matrix-conduwuit-public-conduwuit-api.tls.certResolver={{ m ############################################################ # # -# /Public Conduwuit-API (/_conduwuit) # +# /Public conduwuit-API (/_conduwuit) # # # ############################################################ {% endif %} diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml index a44f982e4..8526fe996 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml @@ -1,5 +1,5 @@ --- -- name: Ensure Conduwuit user registered - {{ user.username | quote }} +- name: Ensure conduwuit user registered - {{ user.username | quote }} ansible.builtin.debug: - msg: "Not registering user. To register Conduwuit users, message the Conduwuit bot" + msg: "Not registering user. To register conduwuit users, message the conduwuit bot" From 4e5532a0d5f17c7d16829a91b9dc4113f2246e2e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 12:32:35 +0900 Subject: [PATCH 236/952] Update docs for Draupnir, D4A, and Mjolnir: emphasize the importance of being careful when inviting a user to the management room Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-appservice-draupnir-for-all.md | 2 +- docs/configuring-playbook-bot-draupnir.md | 4 +++- docs/configuring-playbook-bot-mjolnir.md | 4 +++- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index be7aacc30..8d6547dfd 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -28,7 +28,7 @@ The management room has to be given an alias, and your bot has to be invited to This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel. -As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.** +⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. ### Set an alias to the management room diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 288cc4104..79747fae6 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -12,7 +12,9 @@ If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-on ### Create a management room -Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. +Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. + +⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. If you make the management room encrypted (E2EE), then you need to enable the native E2EE support (see [below](#native-e2ee-support)). diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 2564cd2f9..4e9717b55 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -52,7 +52,9 @@ You can obtain an access token for a homeserver admin account in the same way as ### Create a management room -Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room. +Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. + +⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). From 39625aae155869a0f65d6bbada20f0491e8631c3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 16:32:16 +0900 Subject: [PATCH 237/952] Update docs for Draupnir and Mjolnir: small edits for the common sentences Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 79747fae6..69ab00e60 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -16,7 +16,7 @@ Using your own account, create a new invite only room that you will use to manag ⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. -If you make the management room encrypted (E2EE), then you need to enable the native E2EE support (see [below](#native-e2ee-support)). +It is possible to make the management room encrypted (E2EE). If doing so, then you need to enable the native E2EE support (see [below](#native-e2ee-support)). Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 4e9717b55..4d44a0e7a 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -56,7 +56,7 @@ Using your own account, create a new invite only room that you will use to manag ⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. -If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). +It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. From 04ff68e229c9f4e2f2f9f4472e22c11bc29924f4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 13:08:49 +0900 Subject: [PATCH 238/952] Update docs for Draupnir and Mjolnir: tidy up the instruction to check the room ID Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 2 +- docs/configuring-playbook-bot-mjolnir.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 69ab00e60..6884d67e5 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -18,7 +18,7 @@ Using your own account, create a new invite only room that you will use to manag It is possible to make the management room encrypted (E2EE). If doing so, then you need to enable the native E2EE support (see [below](#native-e2ee-support)). -Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. +Once you have created the room you need to copy the room ID so you can specify it on your `inventory/host_vars/matrix.example.com/vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking "Advanced". The room ID will look something like `!qporfwt:example.com`. Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that your attempting to invite a user that doesnt have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 4d44a0e7a..8d138396d 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -58,7 +58,7 @@ Using your own account, create a new invite only room that you will use to manag It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). -Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`. +Once you have created the room you need to copy the room ID so you can specify it on your `vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking "Advanced". The room ID will look something like `!qporfwt:example.com`. Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room. From 340e569984dd3f6c8343bba6632b8b5984ca3783 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 11:42:59 +0900 Subject: [PATCH 239/952] Update docs/configuring-playbook-appservice-draupnir-for-all.md: remove the duplicated instruction to set an alias to the management room Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-appservice-draupnir-for-all.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 8d6547dfd..f2a2ade8c 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -30,10 +30,6 @@ This management room is used to control who has access to your D4A deployment. T ⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. -### Set an alias to the management room - -Next, set an alias to the management room. - ## Adjusting the playbook configuration Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`. From 7b6b103e01f842e1e7d32fe6e7dd1c4eae9e179a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 11:39:59 +0900 Subject: [PATCH 240/952] Update docs/configuring-playbook-bot-draupnir.md: misc changes mainly fixing typos The typos were introduced by f15c0a46be2f9bd4adfdff207f64701560d11b13. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 6884d67e5..bbf04217b 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -20,29 +20,29 @@ It is possible to make the management room encrypted (E2EE). If doing so, then y Once you have created the room you need to copy the room ID so you can specify it on your `inventory/host_vars/matrix.example.com/vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking "Advanced". The room ID will look something like `!qporfwt:example.com`. -Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that your attempting to invite a user that doesnt have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists. +Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that you are attempting to invite a user that does not have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists. ## End-to-End Encryption support -Decide whether you want to support having an Encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled. +Decide whether you want to support having an encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled. -Refer to Draupnir's [Documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more information on why you might or might not care about encryption support for protected rooms. +Refer to Draupnir's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more details about why you might want to care about encryption support for protected rooms. -**Note**: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. +**Note**: since v2.0.0 Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. ### Native E2EE support -To enable the native E2EE support, you need to obtain an access token for Draupnir. +To enable the native E2EE support, you need to obtain an access token for Draupnir and set it on your `vars.yml` file. Note that native E2EE requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. **The access token obtained via Element Web does not work with it**. Refer to the documentation on [how to obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl). To enable the native E2EE support, add the following configuration to your `vars.yml` file: ```yaml -# Enables the native E2EE Support +# Enables the native E2EE support matrix_bot_draupnir_enable_experimental_rust_crypto: true -# Access Token the bot uses to login. +# Access token which the bot will use for logging in. # Comment out `matrix_bot_draupnir_login_native` when using this option. matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" ``` @@ -68,14 +68,15 @@ matrix_bot_draupnir_login_native: true matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE" ``` -Before Proceeding run the playbook with the following command to make sure the Draupnir user has been created. +Before proceeding to the next step, run the playbook with the following command to make sure that the bot user has been created. + ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created ``` ### Make sure the account is free from rate limiting -If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a heavily recomended step. If you do not configure it, Draupnir performance will be degraded.** +If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a highly recommended step. If you do not configure it, Draupnir performance will be degraded.** This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. @@ -114,7 +115,7 @@ matrix_bot_draupnir_abuse_reporting_enabled: true ### Extending the configuration From 2c7914d07142ee555903c631a9309a0311dd9419 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 13:06:47 +0900 Subject: [PATCH 241/952] Update docs/configuring-playbook-bot-draupnir.md: invite the Draupnir bot after installation Now that the bot user for Draupnir is created automatically and you no longer need to register it manually since its 2.0.0 version, it does not seem to be sensible to synchronize descriptions about inviting bots between documents for Draupnir and Mjolnir. It is not friendly to instruct to invite the bot which does not exist just yet, only to let the known error message about the nonexistent user displayed. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index bbf04217b..f95e3b3c5 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -20,8 +20,6 @@ It is possible to make the management room encrypted (E2EE). If doing so, then y Once you have created the room you need to copy the room ID so you can specify it on your `inventory/host_vars/matrix.example.com/vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking "Advanced". The room ID will look something like `!qporfwt:example.com`. -Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that you are attempting to invite a user that does not have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists. - ## End-to-End Encryption support Decide whether you want to support having an encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled. @@ -163,6 +161,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage +To use Draupnir, you need to invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier. + You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide. Below is a **non-exhaustive quick-start guide** for the impatient. From 7186d5fb930f731f76e72e5dbd66f9d075fe377b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 00:00:10 +0900 Subject: [PATCH 242/952] Update docs/configuring-playbook-bot-draupnir.md: add an anchor link to configuring-playbook-bot-mjolnir.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index f95e3b3c5..a79d69b66 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -6,7 +6,7 @@ See the project's [documentation](https://the-draupnir-project.github.io/draupni This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead. -If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating). +If your migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [this section](#migrating-from-mjolnir-only-required-if-migrating). ## Prerequisites From c4507d42e3bd07c7c94269a95d216f083dc2b89d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 15:33:35 +0900 Subject: [PATCH 243/952] Update docs/configuring-playbook-bot-draupnir.md: add "optoional, recommended" label to the section Unlike Mjolnir, the step is no longer required. It is optional and recommended on Draupnir, therefore it should be clarified so. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index a79d69b66..808bc4aa6 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -72,7 +72,7 @@ Before proceeding to the next step, run the playbook with the following command ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created ``` -### Make sure the account is free from rate limiting +### Make sure the account is free from rate limiting (optional, recommended) If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a highly recommended step. If you do not configure it, Draupnir performance will be degraded.** From c691f855334ac568c80b6a5696ae209c21df98c5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 20 Jan 2025 09:41:08 +0200 Subject: [PATCH 244/952] Upgrade ddclient (3.11.2 -> 4.0.0) and adjust config path Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3971 The path change is due to: https://github.com/ddclient/ddclient/pull/789 This is untested. --- roles/custom/matrix-dynamic-dns/defaults/main.yml | 2 +- .../templates/systemd/matrix-dynamic-dns.service.j2 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-dynamic-dns/defaults/main.yml b/roles/custom/matrix-dynamic-dns/defaults/main.yml index c2810e3d9..066d501f0 100644 --- a/roles/custom/matrix-dynamic-dns/defaults/main.yml +++ b/roles/custom/matrix-dynamic-dns/defaults/main.yml @@ -8,7 +8,7 @@ matrix_dynamic_dns_enabled: true matrix_dynamic_dns_daemon_interval: '300' # renovate: datasource=docker depName=linuxserver/ddclient versioning=semver -matrix_dynamic_dns_version: 3.11.2 +matrix_dynamic_dns_version: 4.0.0 # The docker container to use when in mode matrix_dynamic_dns_docker_image: "{{ matrix_dynamic_dns_docker_image_name_prefix }}linuxserver/ddclient:{{ matrix_dynamic_dns_version }}" diff --git a/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 index 488c692ad..e5507a337 100644 --- a/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 +++ b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 @@ -23,7 +23,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --network={{ matrix_dynamic_dns_container_network }} \ -e PUID={{ matrix_user_uid }} \ -e PGID={{ matrix_user_gid }} \ - --mount type=bind,src={{ matrix_dynamic_dns_config_path }},dst=/config \ + --mount type=bind,src={{ matrix_dynamic_dns_config_path }},dst=/config/ddclient \ {% for arg in matrix_dynamic_dns_container_extra_arguments %} {{ arg }} \ {% endfor %} From 887db388e8dbe060e0a8db07dd50f649348ca3dd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 11:55:52 +0900 Subject: [PATCH 245/952] Apply the review from another PR Cherry-picked from f7c01cca9c5a4aa6002f45fd011e0a2753a86482. Regressed by f15c0a46be2f9bd4adfdff207f64701560d11b13. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 808bc4aa6..bb0d479d7 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -26,7 +26,13 @@ Decide whether you want to support having an encrypted management room or not. D Refer to Draupnir's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more details about why you might want to care about encryption support for protected rooms. -**Note**: since v2.0.0 Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. +### Disable Pantalaimon for Draupnir (since v2.0.0; optional) + +It is known that running Draupnir along with Pantalaimon breaks all workflows that involve answering prompts with reactions. + +If you are updating Draupnir from v1.x.x and have enabled Pantalaimon for it, you can disable Pantalaimon in favor of the native E2EE support. To disable Pantalaimon, remove the configuration `matrix_bot_draupnir_pantalaimon_use: true` from your `vars.yml` file. + +**Note**: because the management room is still encrypted, disabling it without enabling the native E2EE support will break the management room. ### Native E2EE support @@ -138,7 +144,7 @@ matrix_bot_draupnir_configuration_extension_yaml: | Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration. -Note that Pantalaimon is unsupported by Draupnir so it is recommended to consult the instructions to enable [the native E2EE support](#native-e2ee-support). +Note that Draupnir supports E2EE natively, so you can enable it instead of Pantalaimon. It is recommended to consult the instruction [here](#native-e2ee-support). That is all you need to do due to that Draupnir can complete migration on its own. From d000b558e12e939c3bb7dc84cc08baddfbf291cb Mon Sep 17 00:00:00 2001 From: Kolja Date: Mon, 20 Jan 2025 09:25:13 +0100 Subject: [PATCH 246/952] Fix postgres maintenance links --- CHANGELOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bd098a3dd..60fee527e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -19,9 +19,9 @@ To try out conduwuit, we recommend that you **use a new server**. Refer to our [ The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034). -If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file. +If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](docs/maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file. -If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup. +If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](docs/maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup. If you're using an external Postgres server (not installed by this playbook), you'll need to figure out how to upgrade it yourself. From 30a53efaddfc8605268b588614bc9c7534042d7b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 12:56:19 +0900 Subject: [PATCH 247/952] Update docs for Draupnir and Mjolnir: move the note about API access above Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 4 ++-- docs/configuring-playbook-bot-mjolnir.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index daa770567..e9cae6aaa 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -84,6 +84,8 @@ If your homeserver's implementation is Synapse, you will need to prevent it from This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. +**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). + To expose the APIs publicly, add the following configuration to your `vars.yml` file: ```yaml @@ -92,8 +94,6 @@ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). -**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). - To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: ```sh diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 87a8f85dc..f0d96f163 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -32,6 +32,8 @@ If your homeserver's implementation is Synapse, you will need to prevent it from This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally. +**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). + To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml @@ -40,8 +42,6 @@ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). -**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). - To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: ```sh From aea2a6d53fcd671962a0c3381ae6f9cea4dabcf9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 13:03:10 +0900 Subject: [PATCH 248/952] Update docs for Draupnir and Mjolnir: create subsections for the instruction about making sure the account is free from rate limiting Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 6 +++++- docs/configuring-playbook-bot-mjolnir.md | 6 +++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index e9cae6aaa..dce9362b1 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -86,13 +86,17 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap **Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). +The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). + +#### Add the configuration + To expose the APIs publicly, add the following configuration to your `vars.yml` file: ```yaml matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true ``` -The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). +#### Run the `curl` command To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index f0d96f163..d52952724 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -34,13 +34,17 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap **Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). +The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). + +#### Add the configuration + To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true ``` -The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md). +#### Run the `curl` command To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: From 9a0e1e64a8ac11696e6039ccdaeaed11b5363cd0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 13:08:08 +0900 Subject: [PATCH 249/952] Update docs for Draupnir and Mjolnir: move the instruction to obtain an access token for the admin account above the one about running the curl command Also: clarify that it is the admin account that needs to be obtained for Synapse's Admin APIs. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 12 ++++++------ docs/configuring-playbook-bot-mjolnir.md | 8 ++++++-- 2 files changed, 12 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index dce9362b1..89258f620 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -96,6 +96,12 @@ To expose the APIs publicly, add the following configuration to your `vars.yml` matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true ``` +#### Obtain an access token for admin account + +Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). + +⚠️ **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. + #### Run the `curl` command To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: @@ -104,12 +110,6 @@ To disable rate limiting, run the following command on systems that ship curl (n curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit ``` -### Obtain an access token - -Manual access to Synapse's Admin API requires an access token. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. - ### Abuse Reports Draupnir can receive reports in the management room. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index d52952724..ef3900277 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -44,6 +44,12 @@ To expose the APIs publicly, add the following configuration to your `inventory/ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true ``` +#### Obtain an access token for admin account + +Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). If you have made Mjolnir an admin, you can just use the Mjolnir token. + +⚠️ **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. + #### Run the `curl` command To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: @@ -52,8 +58,6 @@ To disable rate limiting, run the following command on systems that ship curl (n curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit ``` -You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token. - ### Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. From 8eb513a49de6e55c7b5db495893ace87e14d0660 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 13:20:40 +0900 Subject: [PATCH 250/952] Update docs for Draupnir and Mjolnir: improve instructions to replace the IDs Also: replace the placeholder for the clean access token Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 6 +++--- docs/configuring-playbook-bot-mjolnir.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 89258f620..92c9ce5af 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -40,7 +40,7 @@ To enable the native E2EE support, you need to obtain an access token for Draupn Note that native E2EE requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. **The access token obtained via Element Web does not work with it**. Refer to the documentation on [how to obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl). -To enable the native E2EE support, add the following configuration to your `vars.yml` file: +To enable the native E2EE support, add the following configuration to your `vars.yml` file. Make sure to replace `CLEAN_ACCESS_TOKEN_HERE` with the access token you obtained just now. ```yaml # Enables the native E2EE support @@ -48,12 +48,12 @@ matrix_bot_draupnir_enable_experimental_rust_crypto: true # Access token which the bot will use for logging in. # Comment out `matrix_bot_draupnir_login_native` when using this option. -matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE" +matrix_bot_draupnir_access_token: "CLEAN_ACCESS_TOKEN_HERE" ``` ## Adjusting the playbook configuration -To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the one of the room which you have created earlier. ```yaml # Enable Draupnir diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index ef3900277..f5218a87f 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -72,7 +72,7 @@ Finally invite the `@bot.mjolnir:example.com` account you created earlier into t ## Adjusting the playbook configuration -To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`. +To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the one of the room which you have created just now. ```yaml # Enable Mjolnir From 9c5cd42af156a07970968da52462edb77aeb4b49 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 13:44:14 +0900 Subject: [PATCH 251/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: fix capitalization, typo, and sentences Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index aa4da34f6..632c9bfff 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -72,12 +72,12 @@ matrix_bot_draupnir_access_token: "" matrix_bot_draupnir_pantalaimon_username: "" matrix_bot_draupnir_pantalaimon_password: "" -# Username and password the bot uses for logging in directly. If using Pantalimon +# Username and password the bot uses for logging in directly. If using Pantalaimon # these values become the values of `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` matrix_bot_draupnir_login: "{{ matrix_bot_draupnir_pantalaimon_username if matrix_bot_draupnir_pantalaimon_use == 'true' else 'bot.draupnir' }}" matrix_bot_draupnir_password: "{{ matrix_bot_draupnir_pantalaimon_password }}" -# Controls if we activate the pantalaimon config block for now. This configuration block is proable to change name for our usecase +# Controls if we activate the Pantalaimon config block for now. This configuration block's name will probably be changed for our usecase # due to a Draupnir push to scrub Pantalaimon from the codebase. matrix_bot_draupnir_login_native: "" @@ -88,11 +88,11 @@ matrix_bot_draupnir_login_native: "" matrix_bot_draupnir_management_room: "" # Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API). -# Set this to the pantalaimon URL if you're using that. +# Set this to the Pantalaimon URL if you're using that. matrix_bot_draupnir_homeserver_url: "" # Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/), -# only set this to the public-internet homeserver client API URL, do NOT set this to the pantalaimon URL. +# only set this to the public-internet homeserver client API URL. Do NOT set this to the Pantalaimon URL. matrix_bot_draupnir_raw_homeserver_url: "" # Disable Server ACL is used if you want to not give the bot the right to apply Server ACLs in rooms without complaints from the bot. From c3e9e513851803edb2833d07300e12acb6259d37 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 18:07:48 +0900 Subject: [PATCH 252/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: clarify that setting "matrix_bot_draupnir_pantalaimon_use" to false is opinionated Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 632c9bfff..6bd3387df 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -49,9 +49,9 @@ matrix_bot_draupnir_systemd_wanted_services_list: [] # Whether Draupnir should talk to the homeserver through Pantalaimon # If true, then other variables must be provided including pointing # `matrix_bot_draupnir_homeserver_url` to the Pantalaimon URL. -# Enabling this option is discouraged, because Draupnir does not support -# running with Pantalaimon as it would break all workflows that involve answering -# prompts with reactions. (Hint: a lot of workflows rely on them.) +# We discourage enabling this option, because it is known that running +# Draupnir along with Pantalaimon breaks all workflows that involve +# answering prompts with reactions. (Hint: a lot of workflows rely on them.) matrix_bot_draupnir_pantalaimon_use: false # If you choose to accept the risks of using Pantalaimon in your installation From 177ac8caa19fd80772bdaec38cedd14e39543f38 Mon Sep 17 00:00:00 2001 From: Catalan Lover Date: Mon, 20 Jan 2025 14:39:40 +0100 Subject: [PATCH 253/952] Replace old warnings with Github Markdown Warnings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I executed a Search for `⚠️ **Warning**:` and replaced it with ``` > [!WARNING] > ``` I also capitalised the first letter where missing. Draupnir Docs have been excluded from this Commit as to not cause a separate PR im working on for the Draupnir docs to have potential merge conflicts and im making said change in that document too. --- docs/configuring-playbook-alertmanager-receiver.md | 3 ++- docs/configuring-playbook-appservice-draupnir-for-all.md | 3 ++- docs/configuring-playbook-bot-chatgpt.md | 3 ++- docs/configuring-playbook-bot-go-neb.md | 3 ++- docs/configuring-playbook-bot-maubot.md | 3 ++- docs/configuring-playbook-bot-mjolnir.md | 6 ++++-- docs/configuring-playbook-bridge-appservice-kakaotalk.md | 3 ++- docs/configuring-playbook-dimension.md | 3 ++- docs/configuring-playbook-email.md | 3 ++- docs/configuring-playbook-email2matrix.md | 3 ++- docs/configuring-playbook-jitsi.md | 6 ++++-- docs/configuring-playbook-matrix-corporal.md | 3 ++- docs/configuring-playbook-synapse-admin.md | 3 ++- docs/configuring-playbook-traefik.md | 6 ++++-- docs/configuring-playbook-user-verification-service.md | 3 ++- docs/installing.md | 3 ++- docs/maintenance-synapse.md | 3 ++- docs/obtaining-access-tokens.md | 3 ++- docs/registering-users.md | 9 ++++++--- 19 files changed, 48 insertions(+), 24 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 8a0b8776b..2184821fb 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -26,7 +26,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertma The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Join to rooms as the bot manually diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index d3e4741b2..ee5c11700 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -28,7 +28,8 @@ The management room has to be given an alias, and your bot has to be invited to 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. -⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. +> [!WARNING] +> Anyone in this room can control the bot so it is important that you only invite trusted users to this room. ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 3ed5ef729..d29e6855d 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -28,7 +28,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6). diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index cd6e875cd..ff428c3e1 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -26,7 +26,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Adjusting DNS records diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index 0436de588..be267b326 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -100,4 +100,5 @@ This can be done via `mbc login` then `mbc auth` (see the [maubot documentation] Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 87a8f85dc..9e40ceb04 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -24,7 +24,8 @@ If you would like Mjolnir to be able to deactivate users, move aliases, shutdown The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Make sure the account is free from rate limiting @@ -54,7 +55,8 @@ You can obtain an access token for a homeserver admin account in the same way as Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. -⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. +> [!WARNING] +> Anyone in this room can control the bot so it is important that you only invite trusted users to this room. It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index af0955273..9b029e194 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -4,7 +4,8 @@ The playbook can install and configure [matrix-appservice-kakaotalk](https://src 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. -⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**. +> [!WARNING] +> There have been recent reports (~2022-09-16) that **using this bridge may get your account banned**. ## Prerequisite (optional) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 7d1c0ce3f..71d5b9c0d 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -34,7 +34,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=dimension p Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Adjusting DNS records diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index b10dd8224..85fa6e37a 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -6,7 +6,8 @@ The email server would attempt to deliver emails directly to their final destina By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable. -⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server). +> [!WARNING] +> On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server). 💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway. diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index d703d5417..64ef5e112 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -36,7 +36,8 @@ Take note of the user's ID as it needs to be specified as `MatrixUserId` on your Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Join to rooms as the sender user manually diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index a6b3cc28f..882d434e4 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -72,7 +72,8 @@ jitsi_prosody_auth_internal_accounts: #### Authenticate using Matrix OpenID: Auth-Type `matrix` -⚠️ **Warning**: this breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests. +> [!WARNING] +> This breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests. This authentication method requires [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service), which can be installed using this [playbook](configuring-playbook-user-verification-service.md). It verifies against Matrix openID, and requires a user-verification-service to run. @@ -149,7 +150,8 @@ To enable the Gravatar service, add the following configuration to your `vars.ym jitsi_disable_gravatar: false ``` -⚠️ **Warning**: this will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party. +> [!WARNING] +> This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party. ### Fine tune Jitsi (optional) diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 6c4df4985..fea63b552 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -2,7 +2,8 @@
-⚠️ **Warning**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't. +> [!WARNING] +> This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't.
diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index 22635d012..bc404b9f1 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -27,7 +27,8 @@ matrix_synapse_admin_enabled: true By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) - the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable. -⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all. +> [!WARNING] +> If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all. ### Adjusting the Synapse Admin URL (optional) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 66d6b1aee..b9f3e86e8 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -34,7 +34,8 @@ traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE ``` -⚠️ **Warning**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. +> [!WARNING] +> Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. ## Additional configuration @@ -134,7 +135,8 @@ Changing the `url` to one with an `http://` prefix would allow to connect to the With these changes, all TCP traffic will be reverse-proxied to the target system. -⚠️ **Warning**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. +> [!WARNING] +> This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. ## Traefik behind a `proxy_protocol` reverse-proxy diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 4b62c378b..0459752bb 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -43,7 +43,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=uvs passwor UVS requires an access token as an admin user to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Adjusting the playbook configuration diff --git a/docs/installing.md b/docs/installing.md index c4eda3b9f..bcd2e2325 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -53,7 +53,8 @@ To do the installation **without** starting services, run `ansible-playbook` wit ansible-playbook -i inventory/hosts setup.yml --tags=install-all ``` -⚠️ **Warning**: do not run the just "recipe" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts) +> [!WARNING] +> Do not run the just "recipe" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts) When this command completes, services won't be running yet. diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index 0c2eded9b..3bb315fcb 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -18,7 +18,8 @@ You can use the **[Purge History API](https://github.com/element-hq/synapse/blob To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file. diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index e1f69b226..909d62b8f 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -2,7 +2,8 @@ When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token. -⚠️ **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. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ## Prerequisites diff --git a/docs/registering-users.md b/docs/registering-users.md index ca62398da..1d92ce131 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -42,7 +42,8 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HE Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`. -⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information. +> [!WARNING] +> If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information. ### Registering users manually for Synapse @@ -80,13 +81,15 @@ This `register-user` script actually invokes the `mas-cli manage register-user` /matrix/matrix-authentication-service/bin/mas-cli manage register-user --help ``` -⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information. +> [!WARNING] +> Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information. ## Managing users via a Web UI To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md). -⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information. +> [!WARNING] +> If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information. ## Letting certain users register on your private server From cb0798bc0615687e3e1972b1c4c19774d565ee7f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 23:02:35 +0900 Subject: [PATCH 254/952] Update docs/configuring-playbook-bot-draupnir.md: create and soon invite the bot user to the management room Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index daa770567..eff27752d 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -72,12 +72,16 @@ matrix_bot_draupnir_login_native: true matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE" ``` -Before proceeding to the next step, run the playbook with the following command to make sure that the bot user has been created. +### Create and invite the bot to the management room + +Before proceeding to the next step, run the playbook with the following command to create the bot user. ```sh ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created ``` +Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier. + ### Make sure the account is free from rate limiting (optional, recommended) If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a highly recommended step. If you do not configure it, Draupnir performance will be degraded.** @@ -171,8 +175,6 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -To use Draupnir, you need to invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier. - You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide. Below is a **non-exhaustive quick-start guide** for the impatient. From 66d96844d66c4b82d053a0fb566fe2036da6444c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 20 Jan 2025 23:06:42 +0900 Subject: [PATCH 255/952] Update docs/configuring-playbook-bot-draupnir.md: move the note about the "ensure-matrix-users-created" playbook tag Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index eff27752d..f95adf68c 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -80,6 +80,8 @@ Before proceeding to the next step, run the playbook with the following command ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created ``` +**Note**: the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier. ### Make sure the account is free from rate limiting (optional, recommended) @@ -165,13 +167,9 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start ``` -**Notes**: +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - -- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - - `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. ## Usage From 8fadab4ee84e0c9f71d9d2b563d1c8ddf1df30e2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 12:16:51 +0900 Subject: [PATCH 256/952] Change the expression and fix other typos Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 6bd3387df..f1d4514de 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -67,7 +67,7 @@ matrix_bot_draupnir_enable_experimental_rust_crypto: false # (Otherwise provide `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` instead.) matrix_bot_draupnir_access_token: "" -# User name and password for the bot. Required when using Pantalaimon. +# Username and password for the bot. Required when using Pantalaimon. # (Otherwise provide `matrix_bot_draupnir_access_token` instead.) matrix_bot_draupnir_pantalaimon_username: "" matrix_bot_draupnir_pantalaimon_password: "" @@ -77,8 +77,8 @@ matrix_bot_draupnir_pantalaimon_password: "" matrix_bot_draupnir_login: "{{ matrix_bot_draupnir_pantalaimon_username if matrix_bot_draupnir_pantalaimon_use == 'true' else 'bot.draupnir' }}" matrix_bot_draupnir_password: "{{ matrix_bot_draupnir_pantalaimon_password }}" -# Controls if we activate the Pantalaimon config block for now. This configuration block's name will probably be changed for our usecase -# due to a Draupnir push to scrub Pantalaimon from the codebase. +# Controls if we activate the config block for Pantalaimon for now. Its name will +# probably be changed for our usecase due to Draupnir's push to scrub Pantalaimon from the codebase. matrix_bot_draupnir_login_native: "" # The room ID where people can use the bot. The bot has no access controls, so @@ -91,8 +91,8 @@ matrix_bot_draupnir_management_room: "" # Set this to the Pantalaimon URL if you're using that. matrix_bot_draupnir_homeserver_url: "" -# Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/), -# only set this to the public-internet homeserver client API URL. Do NOT set this to the Pantalaimon URL. +# Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/). +# Only set this to the public-internet homeserver client API URL. Do NOT set this to the Pantalaimon URL. matrix_bot_draupnir_raw_homeserver_url: "" # Disable Server ACL is used if you want to not give the bot the right to apply Server ACLs in rooms without complaints from the bot. @@ -102,7 +102,7 @@ matrix_bot_draupnir_raw_homeserver_url: "" # DO NOT change this to `true` unless you are very confident that you know what you are doing. # # Please follow the advice of upstream and only change this value if you know what your doing. -# Its Exposed here because its common enough to be valid to expose. +# It is exposed here because it is common enough to be valid to expose. matrix_bot_draupnir_disable_server_acl: "false" # Controls if the room state backing store is activated. From 5731bcd22211933e21e4fdcbf3b72744d49c7f2e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 12:31:16 +0900 Subject: [PATCH 257/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: fix another sentence and capitalization Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index f1d4514de..e59dfc800 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -95,8 +95,8 @@ matrix_bot_draupnir_homeserver_url: "" # Only set this to the public-internet homeserver client API URL. Do NOT set this to the Pantalaimon URL. matrix_bot_draupnir_raw_homeserver_url: "" -# Disable Server ACL is used if you want to not give the bot the right to apply Server ACLs in rooms without complaints from the bot. -# This setting is described the following way in the Configuration. +# Disable Server ACL is used if you do not want to give the bot the right to apply Server ACLs in rooms without complaints from the bot. +# This setting is described the following way in the configuration. # # Whether or not Draupnir should apply `m.room.server_acl` events. # DO NOT change this to `true` unless you are very confident that you know what you are doing. From a7e1474c3a14af4003b7f8ebd30d210ac0277caa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 12:32:02 +0900 Subject: [PATCH 258/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: strip a noisy warning and the order to check in at the upstream Multiple use of the phrase "you know what you are doing" does not increase its effect but rather makes it noisy instead. Since it is warned with capitalized "DO NOT", it is enough. Also replace the order to check in at the upstream with the recommendation, as it is inconsistent for this project overall to ask users to do so. It is not sensible to make an exception for Draupnir. Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index e59dfc800..bd283e82b 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -100,8 +100,8 @@ matrix_bot_draupnir_raw_homeserver_url: "" # # Whether or not Draupnir should apply `m.room.server_acl` events. # DO NOT change this to `true` unless you are very confident that you know what you are doing. +# It is recommended to consult with people from the upstream project beforehand. # -# Please follow the advice of upstream and only change this value if you know what your doing. # It is exposed here because it is common enough to be valid to expose. matrix_bot_draupnir_disable_server_acl: "false" From 665f7369d68e43f5e1c898552be7df8586c8b4d7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 13:41:39 +0900 Subject: [PATCH 259/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: change the subject who discourages Pantalaimon This change clarifies that it is the upstream project, not this project owner, that discourages enabling Pantalaimon for Draupnir. This distinction should make it clear who is responsible for the matter. Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index bd283e82b..fb91a1c33 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -49,8 +49,9 @@ matrix_bot_draupnir_systemd_wanted_services_list: [] # Whether Draupnir should talk to the homeserver through Pantalaimon # If true, then other variables must be provided including pointing # `matrix_bot_draupnir_homeserver_url` to the Pantalaimon URL. -# We discourage enabling this option, because it is known that running -# Draupnir along with Pantalaimon breaks all workflows that involve +# +# The upstream project discourages enabling this option, because it is +# known that running Draupnir along with Pantalaimon breaks all workflows that involve # answering prompts with reactions. (Hint: a lot of workflows rely on them.) matrix_bot_draupnir_pantalaimon_use: false From 7b979ff7a93b3fb6a30a438d78dd3f59a065d20a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 13:55:49 +0900 Subject: [PATCH 260/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: replace "when" with "if" for consistency and to clarify that these are conditions Note that there is no other "when" on this file. It is not sensible to keep these exceptions here. Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index fb91a1c33..7c2eacde8 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -64,16 +64,16 @@ matrix_bot_draupnir_pantalaimon_breakage_ignore: false # Rust Crypto requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. matrix_bot_draupnir_enable_experimental_rust_crypto: false -# The access token for the bot user. Required when NOT using Pantalaimon. +# The access token for the bot user. Required if Pantalaimon is NOT used. # (Otherwise provide `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` instead.) matrix_bot_draupnir_access_token: "" -# Username and password for the bot. Required when using Pantalaimon. +# Username and password for the bot. Required if Pantalaimon is used. # (Otherwise provide `matrix_bot_draupnir_access_token` instead.) matrix_bot_draupnir_pantalaimon_username: "" matrix_bot_draupnir_pantalaimon_password: "" -# Username and password the bot uses for logging in directly. If using Pantalaimon +# Username and password the bot uses for logging in directly. If Pantalaimon is used, # these values become the values of `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` matrix_bot_draupnir_login: "{{ matrix_bot_draupnir_pantalaimon_username if matrix_bot_draupnir_pantalaimon_use == 'true' else 'bot.draupnir' }}" matrix_bot_draupnir_password: "{{ matrix_bot_draupnir_pantalaimon_password }}" From 9d3ef6134bbba7bc91c915ce136f734317fd8841 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 14:52:39 +0900 Subject: [PATCH 261/952] Update roles/custom/matrix-bot-draupnir/defaults/main.yml: make sure what the word "it" means here Here "it" should not mean "the upstream advice". Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 7c2eacde8..2219cdd98 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -56,7 +56,7 @@ matrix_bot_draupnir_systemd_wanted_services_list: [] matrix_bot_draupnir_pantalaimon_use: false # If you choose to accept the risks of using Pantalaimon in your installation -# against the upstream advice, you can enable this to disable the warning about it. +# against the upstream advice, you can enable this to disable the warning about using it. matrix_bot_draupnir_pantalaimon_breakage_ignore: false # Tells the bot if it should use its native E2EE support in the form of experimental Rust Crypto in the bot SDK. From 2698ed85a045e9166acd49329cde92622decd2e8 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 21 Jan 2025 08:13:31 +0200 Subject: [PATCH 262/952] Replace old warnings with Github Markdown Warnings Ref: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3980 --- docs/configuring-playbook-bot-mjolnir.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index f5218a87f..78337025c 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -24,7 +24,8 @@ If you would like Mjolnir to be able to deactivate users, move aliases, shutdown The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. +> [!WARNING] +> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. ### Make sure the account is free from rate limiting @@ -48,7 +49,8 @@ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). If you have made Mjolnir an admin, you can just use the Mjolnir token. -⚠️ **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. +> [!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. #### Run the `curl` command @@ -62,7 +64,8 @@ curl --header "Authorization: Bearer " -X POST https://matrix.exam Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. -⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. +> [!WARNING] +> Anyone in this room can control the bot so it is important that you only invite trusted users to this room. It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)). From 3343eadd466c52c61468531f765e7177356560cc Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 21 Jan 2025 08:14:49 +0200 Subject: [PATCH 263/952] Replace old warnings with Github Markdown Warnings on Draupnir doc page Ref: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3980 --- docs/configuring-playbook-bot-draupnir.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 92c9ce5af..ce4ac494f 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -14,7 +14,8 @@ If your migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [ Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. -⚠️ **Warning**: anyone in this room can control the bot so it is important that you only invite trusted users to this room. +> [!WARNING] +> Anyone in this room can control the bot so it is important that you only invite trusted users to this room. It is possible to make the management room encrypted (E2EE). If doing so, then you need to enable the native E2EE support (see [below](#native-e2ee-support)). @@ -100,7 +101,8 @@ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). -⚠️ **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. +> [!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. #### Run the `curl` command From 3b685df1abde9271794ac61bcbd135570aecf7ff Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 14:33:37 +0900 Subject: [PATCH 264/952] Update docs for Draupnir and Mjolnir: improve the instructions for running the curl command to disable rate limiting Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-draupnir.md | 12 ++++++++++-- docs/configuring-playbook-bot-mjolnir.md | 12 ++++++++++-- 2 files changed, 20 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index ecc63256b..965906b16 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -112,12 +112,20 @@ Manual access to Synapse's Admin APIs requires an access token for a homeserver #### Run the `curl` command -To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir: +To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace: + +- `ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account +- `example.com` with your base domain +- `@bot.draupnir:example.com` with the MXID of your Draupnir bot user ```sh -curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit +curl --header "Authorization: Bearer ADMIN_ACCESS_TOKEN_HERE" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit ``` +**Notes**: +- This does not work on outdated Windows 10 as curl is not available there. +- Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. + ### Abuse Reports Draupnir can receive reports in the management room. diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 78337025c..2f068e7fa 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -54,12 +54,20 @@ Manual access to Synapse's Admin APIs requires an access token for a homeserver #### Run the `curl` command -To disable rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir: +To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace: + +- `ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account +- `example.com` with your base domain +- `@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user ```sh -curl --header "Authorization: Bearer " -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit +curl --header "Authorization: Bearer ADMIN_ACCESS_TOKEN_HERE" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit ``` +**Notes**: +- This does not work on outdated Windows 10 as curl is not available there. +- Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. + ### Create a management room Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. From ef6f50e898d873a9e7d3ad0438abe15d7dd7c6c1 Mon Sep 17 00:00:00 2001 From: Catalan Lover Date: Tue, 21 Jan 2025 16:49:21 +0100 Subject: [PATCH 265/952] Change matrix_synapse_forgotten_room_retention_period from null to 28d As we automatically forget rooms on leave in the playbook this option working at all is probably heavily desired. Timing is copied from upstream example. Credit goes to Anoa for making me even check this. --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index b45381c56..657d546bf 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -1456,7 +1456,7 @@ matrix_synapse_redaction_retention_period: 7d # Controls how long to keep locally forgotten rooms before purging them from the DB. # Defaults to `null`, meaning it's disabled. # Example value: 28d -matrix_synapse_forgotten_room_retention_period: ~ +matrix_synapse_forgotten_room_retention_period: 28d matrix_synapse_user_ips_max_age: 28d From fbe32cc17ce431dc88fa03587d9413d5523d059b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 22 Jan 2025 01:35:34 +0900 Subject: [PATCH 266/952] Update docs/configuring-playbook-backup-borg.md and docs/configuring-playbook-synapse-auto-compressor.md: adopt the common description Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-synapse-auto-compressor.md | 8 ++++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index ed960f252..702e72613 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -138,6 +138,6 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration. -If you want to run the backup immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`. +If you want to run it immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 50e981cb4..8af611fae 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -31,6 +31,10 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default). -## Manually start the tool +## Manually execute compression -For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. +Sometimes it can be helpful to execute compression as you'd like, avoiding to wait until 00:00, like when you test your configuration. + +If you want to execute it immediately, log in to the server with SSH and run `systemctl start matrix-synapse-auto-compressor`. + +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. From 4d6ee3db7e249f641ba74f440306f1509685f95a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 21 Jan 2025 21:34:42 +0000 Subject: [PATCH 267/952] Update matrixdotorg/mjolnir Docker tag to v1.9.2 --- roles/custom/matrix-bot-mjolnir/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml index 9f7fea28c..cba27a58d 100644 --- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml +++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_mjolnir_enabled: true # renovate: datasource=docker depName=matrixdotorg/mjolnir -matrix_bot_mjolnir_version: "v1.9.1" +matrix_bot_mjolnir_version: "v1.9.2" matrix_bot_mjolnir_container_image_self_build: false matrix_bot_mjolnir_container_image_self_build_repo: "https://github.com/matrix-org/mjolnir.git" From 52da325ab83bb6b16e15adbd7bdad1e5b32c3943 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 22 Jan 2025 08:43:35 +0200 Subject: [PATCH 268/952] Cross-link `matrix_synapse_forget_rooms_on_leave` and `matrix_synapse_forgotten_room_retention_period` variables --- roles/custom/matrix-synapse/defaults/main.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 657d546bf..2c070b47d 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -1415,6 +1415,7 @@ matrix_synapse_default_room_version: "10" # Controls whether leaving a room will automatically forget it. # The upstream default is `false`, but we try to make Synapse less wasteful of resources, so we do things differently. +# Also see: `matrix_synapse_forgotten_room_retention_period` matrix_synapse_forget_rooms_on_leave: true # Controls the Synapse `modules` list. @@ -1455,6 +1456,7 @@ matrix_synapse_redaction_retention_period: 7d # Controls how long to keep locally forgotten rooms before purging them from the DB. # Defaults to `null`, meaning it's disabled. +# Also see: `matrix_synapse_forget_rooms_on_leave` # Example value: 28d matrix_synapse_forgotten_room_retention_period: 28d From c8ca9489bb833cf2460993717cf1aa68a1a3bf36 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 16 Jan 2025 23:54:20 +0900 Subject: [PATCH 269/952] Update docs/configuring-playbook-bridge-mautrix-wsproxy.md: move down the section "Extending the configuration" for consistency Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-wsproxy.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index bdc1f3bb2..fb2005c6d 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -28,12 +28,6 @@ matrix_mautrix_wsproxy_syncproxy_shared_secret: 'secret token from bridge' Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device. -### Extending the configuration - -There are some additional things you may wish to configure about the bridge. - -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. - ### Adjusting the wsproxy URL (optional) By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -47,6 +41,12 @@ matrix_mautrix_wsproxy_hostname: ws.example.com After changing the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server. +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 97418bf2ea8cc20a31b297fe84a107b5eeea7328 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 23 Jan 2025 18:43:11 +0900 Subject: [PATCH 270/952] Update docs/configuring-playbook-email.md: tidy up This commit applies the common format to the file. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 85fa6e37a..e3713c142 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -15,7 +15,9 @@ By default, emails are sent from `matrix@matrix.example.com`, as specified by th No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration). -## Relaying email through another SMTP server +## Adjusting the playbook configuration + +### Relaying email through another SMTP server If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): @@ -26,29 +28,34 @@ exim_relay_relay_host_name: "mail.example.com" exim_relay_relay_host_port: 587 exim_relay_relay_auth: true exim_relay_relay_auth_username: "another.sender@example.com" -exim_relay_relay_auth_password: "some-password" +exim_relay_relay_auth_password: "PASSWORD_FOR_THE_RELAY_HERE" ``` **Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**. -### Configuations for sending emails using Sendgrid +### Sending emails using Sendgrid -An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`. +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. -The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`. - -Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid. +To set it up, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml -exim_relay_sender_address: "arbitrary@email.com" +exim_relay_sender_address: "example@example.org" exim_relay_relay_use: true exim_relay_relay_host_name: "smtp.sendgrid.net" exim_relay_relay_host_port: 587 exim_relay_relay_auth: true + +# This needs to be literally the string "apikey". It is always the same for Sendgrid. exim_relay_relay_auth_username: "apikey" -exim_relay_relay_auth_password: "" + +# You can generate the API key password at this URL: https://app.sendgrid.com/settings/api_keys +# The password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`. +exim_relay_relay_auth_password: "YOUR_API_KEY_PASSWORD_HERE" ``` ## Troubleshooting -If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`. +If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs. + +To do so, log in to the server with SSH and run `journalctl -f -u matrix-exim-relay`. From 4b155c276ba3c682a2571b64b1c2c507d5ac4662 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 23 Jan 2025 10:11:01 +0000 Subject: [PATCH 271/952] Update halfshot/matrix-hookshot Docker tag to v6.0.2 --- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 8dd61e973..82ceabe24 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -17,7 +17,7 @@ matrix_hookshot_container_additional_networks_auto: [] matrix_hookshot_container_additional_networks_custom: [] # renovate: datasource=docker depName=halfshot/matrix-hookshot -matrix_hookshot_version: 6.0.1 +matrix_hookshot_version: 6.0.2 matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_name_prefix }}matrix-org/matrix-hookshot:{{ matrix_hookshot_version }}" matrix_hookshot_docker_image_name_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else 'ghcr.io/' }}" From e047e860ffbe766aa07300693f2eadb246e47053 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 27 Dec 2024 10:20:30 -0500 Subject: [PATCH 272/952] Update docs/configuring-playbook-bridge-postmoogle.md: add the section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-postmoogle.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index af52e6acc..9ab01f2ee 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -55,6 +55,14 @@ matrix_postmoogle_password: PASSWORD_FOR_THE_BOT # matrix_admin: '@yourAdminAccount:{{ matrix_domain }}' ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +Take a look at: + +- `roles/custom/matrix-bridge-postmoogle/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From a6333df04e996718e0cacac0187657451cc1a102 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 23 Jan 2025 23:26:08 +0900 Subject: [PATCH 273/952] Update configuring-playbook-bot-baibot.md and configuring-playbook-bridge-postmoogle.md: the common section for troubleshooting Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bridge-postmoogle.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 0874095d5..bdc29eafd 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -396,7 +396,7 @@ Send `!bai help` to the bot in the room to see the available commands. You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation. -## Debugging +## Troubleshooting As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot` diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 9ab01f2ee..20ecce4c7 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -92,7 +92,7 @@ Send `!pm help` to the bot in the room to see the available commands. You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle). -### Debug/Logs +## Troubleshooting As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle` From 74e4c2a5bd910713b76e50e63278c4475d4d91c9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 08:43:30 -0500 Subject: [PATCH 274/952] Update docs/configuring-playbook-pantalaimon.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-pantalaimon.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index db40fe018..a2e0be4b8 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -14,7 +14,13 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_pantalaimon_enabled: true ``` -The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml). +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-pantalaimon/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_pantalaimon_configuration` variable ## Installing From 4c00e88fa4d306d1801297726dc7ee64b22a3d88 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 01:32:01 +0900 Subject: [PATCH 275/952] Update docs/configuring-playbook-pantalaimon.md: add the common section "Troubleshooting" The comment was copied from roles/custom/matrix-pantalaimon/defaults/main.yml. The latest status of the variable "matrix_pantalaimon_log_level" can be checked on 55fcaac1f1d5c9a05bfede2ba516aa2073c10392. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-pantalaimon.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index a2e0be4b8..fb34c7b5c 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -34,3 +34,14 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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-pantalaimon`. + +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: + +```yaml +# Pantalaimon log level, case-insensitive (Error, Warning, Info, Debug) +matrix_pantalaimon_log_level: Debug +``` From d6abd309045b1ea9f12f3cba49bd61c77468d452 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 16:01:51 +0900 Subject: [PATCH 276/952] Update docs/configuring-playbook-user-verification-service.md (#3994) * Update docs/configuring-playbook-user-verification-service.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: replace single quotes with backticks Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: adopt the common section "Troubleshooting" Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: use the variable specified on main.yml directly There are other variables specified on .env.j2 such as UVS_ACCESS_TOKEN and UVS_AUTH_TOKEN, but these are not used in the description on the document other than UVS_LOG_LEVEL. This commit therefore replaces the variable with the one specified on main.yml (matrix_user_verification_service_uvs_log_level) to improve consistency. Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: fix capitalization Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: replace the placeholder TOKEN with YOUR_TOKEN_HERE Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-user-verification-service.md: change a section title Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara --- ...ring-playbook-user-verification-service.md | 39 +++++++++++-------- 1 file changed, 22 insertions(+), 17 deletions(-) diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 0459752bb..8e09d61ef 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -56,25 +56,23 @@ matrix_user_verification_service_enabled: true matrix_user_verification_service_uvs_access_token: "ACCESS_TOKEN_HERE" ``` -Check the role's [defaults/main.yml](../roles/custom/matrix-user-verification-service/defaults/main.yml) for the full list of variables that you could override. Note that all the plugging happening in `group_vars/matrix_servers`. - In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`. ### Custom Auth Token (optional) -It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header "Authorization: Bearer TOKEN" +It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header `Authorization: Bearer YOUR_TOKEN_HERE`. -By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`. +By default, the token (`YOUR_TOKEN_HERE`) will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`. -To set your own Token, add the following configuration to your `vars.yml` file: +To set your own token, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_TOKEN_HERE` with your own. ```yaml -matrix_user_verification_service_uvs_auth_token: "TOKEN" +matrix_user_verification_service_uvs_auth_token: "YOUR_TOKEN_HERE" ``` If a Jitsi instance is also managed by this playbook and [`matrix` authentication](configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) is enabled there, this collection will automatically configure Jitsi to use the configured auth token. -### Disable Auth (optional) +### Disable Authorization (optional) Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file: @@ -90,19 +88,15 @@ In theory (however currently untested), UVS can handle federation. To enable it, matrix_user_verification_service_uvs_pin_openid_verify_server_name: false ``` -This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain. +This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via `.well-known/matrix/server` of the given domain. -### Controlling the logging level (optional) +### Extending the configuration -To specify the logging level, add the following configuration to your `vars.yml` file: +There are some additional things you may wish to configure about the component. -```yaml -UVS_LOG_LEVEL: info -``` +Take a look at: -Replace `info` with one of the choices (they can be checked [here](https://github.com/winstonjs/winston#logging-levels)) to control the verbosity of the logs generated. - -If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful. +- `roles/custom/matrix-user-verification-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file ## Installing @@ -119,13 +113,24 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Troubleshooting +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-user-verification-service`. + +### Increase logging verbosity + +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: + +```yaml +# See choices here: https://github.com/winstonjs/winston#logging-levels +matrix_user_verification_service_uvs_log_level: debug +``` + ### TLS Certificate Checking If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message: > message: 'No response received: [object Object]', -This also applies to self-signed and let's encrypt staging certificates. +This also applies to self-signed and Let's Encrypt staging certificates. To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0` From 01050c520de6a03f03d3a1f50eb9cc0b17fda1f9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 17:15:16 +0900 Subject: [PATCH 277/952] Update roles/custom/matrix-bridge-appservice-slack/defaults/main.yml: fix indentation Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bridge-appservice-slack/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml index 5b8594e51..b5c6f6bf9 100644 --- a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml @@ -153,7 +153,7 @@ matrix_appservice_slack_configuration_extension_yaml: | # console: "info" # files: # - "./debug.log": "info" - #- "./error.log": "error" + # - "./error.log": "error" matrix_appservice_slack_configuration_extension: "{{ matrix_appservice_slack_configuration_extension_yaml | from_yaml if matrix_appservice_slack_configuration_extension_yaml | from_yaml else {} }}" From ff7dbcee1b786618119d644b0170ae53e3e17df8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 26 Dec 2024 22:42:41 -0500 Subject: [PATCH 278/952] Update docs/configuring-playbook-bridge-appservice-slack.md: add the common section "Extending the configuration" Also: add an example for "+matrix_appservice_slack_configuration_extension_yaml" Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bridge-appservice-slack.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index b33f565cf..d3295311c 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -61,7 +61,21 @@ matrix_appservice_slack_control_room_id: "Your Matrix admin room ID" # matrix_appservice_slack_team_sync_enabled: true ``` -Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable. +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +Take a look at: + +- `roles/custom/matrix-bridge-appservice-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `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 + +For example, to change the bot's username from `slackbot`, add the following configuration to your `vars.yml` file. Replace `examplebot` with your own. + +```yaml +matrix_appservice_slack_configuration_extension_yaml: | + bot_username: "examplebot" +``` ## Installing From 2b4865d44beb6d45c932ca8ef498e7fbedcd1d89 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 17:08:25 +0900 Subject: [PATCH 279/952] Update docs/configuring-playbook-bridge-appservice-slack.md: adopt the common expression for troubleshooting Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index d3295311c..7c6a7c7a8 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -135,7 +135,7 @@ Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave ## Troubleshooting -As always, check the logs: `journalctl -fu matrix-appservice-slack` +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`. ### Linking: "Room is now pending-name" From e6d631c6f1b275a754f9645d14a281e954babfe3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 17:58:08 +0900 Subject: [PATCH 280/952] Update docs/configuring-playbook-bridge-appservice-slack.md: change the instruction into a sentence Fixing the grammatical structure to avoid word puzzles for better i18n. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-slack.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index 7c6a7c7a8..d21e1496a 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -143,8 +143,8 @@ This typically means that you haven't used the correct Slack channel ID. Unlink ### Messages work from Matrix to Slack, but not the other way around -Check you logs, if they say something like +Check the logs, and if you find the message like below, unlink your room, reinvite the bot and re-link it again. `WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) ` -then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt. +This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt. From 9d8dac83cc12ecafbbb509ae35606af39972671c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 27 Dec 2024 10:43:24 -0500 Subject: [PATCH 281/952] Update docs/configuring-playbook-dimension.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 71d5b9c0d..30b945f8c 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -86,6 +86,17 @@ If you've decided to reuse the `matrix.` domain, you won't need to do any extra **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. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-dimension/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `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 + +You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml). + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: @@ -108,9 +119,3 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details. In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately. - -## Additional features - -To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component. - -You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml). From 5ea579d4ee811d016788ac205417f913a54476c2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 22:20:58 +0900 Subject: [PATCH 282/952] Update docs/configuring-playbook-dimension.md: apply the fact that the project has been finished and the update will not be provided The original description has been added with a0ce5eec6457b80f0b812a5c1ccefbc6d4c7c679 on 2020. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 30b945f8c..9989d9154 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -116,6 +116,8 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ## Jitsi domain -By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details. +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. -In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately. +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. + +There is unfortunately no way to configure it via the playbook. See [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details. From 4400d3c06daaca071f68ce34a65b682fb831e394 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 22:27:43 +0900 Subject: [PATCH 283/952] Update docs/configuring-playbook-dimension.md: create the section "Usage" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 9989d9154..ef3df23b3 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -112,12 +112,14 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. -- After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots. +## Usage -## Jitsi domain +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. + +### Set up a Jitsi widget 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. 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. -There is unfortunately no way to configure it via the playbook. See [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details. +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. From 30d01cc22d32a933853c07c2c04aff1b1390015d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 22:30:26 +0900 Subject: [PATCH 284/952] Update docs/configuring-playbook-dimension.md: replace right arrows with actual ones Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index ef3df23b3..6a662e87c 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -120,6 +120,6 @@ After Dimension has been installed you may need to log out and log back in for i 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. -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. +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. 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. From 292b0704cce486d1a6ed78334eb2fd1fb2157be5 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Fri, 24 Jan 2025 19:29:15 +0000 Subject: [PATCH 285/952] Update gnuxie/draupnir Docker tag to v2.0.2 --- .../custom/matrix-appservice-draupnir-for-all/defaults/main.yml | 2 +- roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index 0d2a0f575..8d028a98b 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -5,7 +5,7 @@ matrix_appservice_draupnir_for_all_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_appservice_draupnir_for_all_version: "v2.0.1" +matrix_appservice_draupnir_for_all_version: "v2.0.2" matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 2219cdd98..08f3fa4e7 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_draupnir_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_bot_draupnir_version: "v2.0.1" +matrix_bot_draupnir_version: "v2.0.2" matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" From d225f52ba27315b0bca62c196741a86bd981a37a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 10:35:19 -0500 Subject: [PATCH 286/952] Update docs/configuring-playbook-alertmanager-receiver.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 2184821fb..84be123f6 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -66,8 +66,6 @@ matrix_alertmanager_receiver_config_matrix_room_mapping: some-room-name: "!qporfwt:{{ matrix_domain }}" ``` -See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables. - ### Adjusting the matrix-alertmanager-receiver URL (optional) By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -84,6 +82,15 @@ If you've changed the default hostname, you may need to create a CNAME record fo When setting, replace `example.com` with your own. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-alertmanager-receiver/templates/config.yml.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 + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 42f38dae07f1ecfa531aec5362a09a4ed3f5713d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 11:51:30 +0900 Subject: [PATCH 287/952] Update docs/configuring-playbook-alertmanager-receiver.md: add the common section "Troubleshooting" The configuration was copied from main.yml. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 84be123f6..1d64b1af7 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -130,3 +130,16 @@ route: ``` 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`. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-alertmanager-receiver`. + +### Increase logging verbosity + +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: + +```yaml +# Valid values: error, warn, info, debug +matrix_alertmanager_receiver_container_process_argument_log_level: debug +``` From 21b5963f63f19524bcc5cec223e59e521e599a30 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 12:03:42 +0900 Subject: [PATCH 288/952] Update files for the matrix-alertmanager-receiver: rename config.yml.j2 to config.yaml.j2 in order to improve consistency Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 2 +- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- .../templates/{config.yml.j2 => config.yaml.j2} | 0 3 files changed, 2 insertions(+), 2 deletions(-) rename roles/custom/matrix-alertmanager-receiver/templates/{config.yml.j2 => config.yaml.j2} (100%) diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index 1d64b1af7..eee2dd0a5 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -89,7 +89,7 @@ There are some additional things you may wish to configure about the component. Take a look at: - `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for some variables that you can customize via your `vars.yml` file -- `roles/custom/matrix-alertmanager-receiver/templates/config.yml.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 +- `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 ## Installing diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index 05e9c9705..e3c423340 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -218,7 +218,7 @@ matrix_alertmanager_receiver_config_templating_resolved_template: |- # # For a more advanced customization, you can extend the default (see `matrix_alertmanager_receiver_configuration_extension_yaml`) # or completely replace this variable with your own template. -matrix_alertmanager_receiver_configuration_yaml: "{{ lookup('template', 'templates/config.yml.j2') }}" +matrix_alertmanager_receiver_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" matrix_alertmanager_receiver_configuration_extension_yaml: | # Your custom YAML configuration for matrix-alertmanager-receiver goes here. diff --git a/roles/custom/matrix-alertmanager-receiver/templates/config.yml.j2 b/roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-alertmanager-receiver/templates/config.yml.j2 rename to roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2 From 5b2282de27674c31489d590fdeda9c200948b822 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 29 Dec 2024 13:07:04 -0500 Subject: [PATCH 289/952] Update docs/configuring-playbook-bridge-hookshot.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index e0f852f1c..2cb197156 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -38,7 +38,12 @@ Take special note of the `matrix_hookshot_*_enabled` variables. Services that ne ### Extending the configuration -You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables. +There are some additional things you may wish to configure about the bridge. + +Take a look at: + +- `roles/custom/matrix-bridge-hookshot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-bridge-hookshot/templates/config.yml.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 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. From 5c39ef8ca225701eaa9563dbd6b8fd6f25b7f7c5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 18:02:18 +0900 Subject: [PATCH 290/952] Update docs/configuring-playbook-bridge-hookshot.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 2cb197156..948704ecc 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -143,3 +143,16 @@ Whichever one you go with, by default metrics are exposed publicly **without** p ### Collision with matrix-appservice-webhooks 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_'`). + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bridge-hookshot`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: debug, info, warn, error +matrix_hookshot_logging_level: debug +``` From e8213768a5661b20c322c881db712f0ac6c99b71 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 18:04:42 +0900 Subject: [PATCH 291/952] Update files for matrix-bridge-hookshot: sort logging levels Based on docs/configuring-playbook-alertmanager-receiver.md We can re-sort the levels it if is found out that debug should be placed at the first. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 2 +- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 948704ecc..6f6bda8e8 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -153,6 +153,6 @@ As with all other services, you can find the logs in [systemd-journald](https:// The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: ```yaml -# Valid values: debug, info, warn, error +# Valid values: error, warn, info, debug matrix_hookshot_logging_level: debug ``` diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 82ceabe24..835ef6c38 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -183,7 +183,7 @@ matrix_hookshot_provisioning_internal: "/v1" matrix_hookshot_provisioning_hostname: "{{ matrix_hookshot_public_hostname }}" matrix_hookshot_provisioning_endpoint: "{{ matrix_hookshot_public_endpoint }}{{ matrix_hookshot_provisioning_internal }}" -# Valid logging levels are: debug, info, warn, error +# Valid values: error, warn, info, debug matrix_hookshot_logging_level: warn matrix_hookshot_widgets_enabled: true From acf2b9034629ed689cad155a340be14ef65b56e5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 17:54:00 +0900 Subject: [PATCH 292/952] Update files for matrix-bridge-hookshot: change the file path of config.yml.j2 in order to improve consistency Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 2 +- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 2 +- .../templates/{config.yml.j2 => config.yaml.j2} | 0 3 files changed, 2 insertions(+), 2 deletions(-) rename roles/custom/matrix-bridge-hookshot/templates/{config.yml.j2 => config.yaml.j2} (100%) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 6f6bda8e8..ec5f72700 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -43,7 +43,7 @@ There are some additional things you may wish to configure about the bridge. Take a look at: - `roles/custom/matrix-bridge-hookshot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file -- `roles/custom/matrix-bridge-hookshot/templates/config.yml.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 +- `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 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. diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 835ef6c38..4de899ca9 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -330,7 +330,7 @@ matrix_hookshot_homeserver_token: '' # # For a more advanced customization, you can extend the default (see `matrixhookshot_configuration_extension_yaml`) # or completely replace this variable with your own template. -matrix_hookshot_configuration_yaml: "{{ lookup('template', 'templates/config.yml.j2') }}" +matrix_hookshot_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" matrix_hookshot_configuration_extension_yaml: | # Your custom YAML configuration goes here. diff --git a/roles/custom/matrix-bridge-hookshot/templates/config.yml.j2 b/roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-bridge-hookshot/templates/config.yml.j2 rename to roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2 From 5c80c820bc62f40c44bd052f7e00efecbdcf0fa9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 18:24:40 +0900 Subject: [PATCH 293/952] Update docs/configuring-playbook-bridge-hookshot.md: add a period Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index ec5f72700..13c6eb6f3 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -98,7 +98,7 @@ Unless indicated otherwise, the following endpoints are reachable on your `matri | widgets | `/hookshot/widgetapi/` | `matrix_hookshot_widgets_endpoint` | Widgets | | metrics | `/metrics/hookshot` | `matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below. | Prometheus | -Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly +Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly. The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info. From 6c19bf509e7924f6ad792ec31a3b5628bc97915d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 26 Dec 2024 12:02:03 -0500 Subject: [PATCH 294/952] Update docs/configuring-playbook-bot-buscarron.md: add the section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-buscarron.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index c7ed4f69d..691aa2468 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -54,6 +54,14 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +### Extending the configuration + +There are some additional things you may wish to configure about the bot. + +Take a look at: + +- `roles/custom/matrix-bot-buscarron/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 2a7111f287b011da7d88cf2be5462956f8e33f6d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 22:24:32 +0900 Subject: [PATCH 295/952] Update docs/configuring-playbook-bot-buscarron.md: add the common section "Troubleshooting" See roles/custom/matrix-bot-buscarron/defaults/main.yml at 601406ddda79b1ea4dd50ffe38d65ddada5ee62b for the default log value (INFO). Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-buscarron.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 691aa2468..f74bf2ea8 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -104,3 +104,15 @@ Here is an example for the `contact` form: If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server. You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron). + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-buscarron`. + +### Increase logging verbosity + +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: + +```yaml +matrix_bot_buscarron_loglevel: DEBUG +``` From 0dc566f1a3643112d439d7a91d16fd6bbdc34d27 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 25 Jan 2025 22:28:15 +0900 Subject: [PATCH 296/952] Update docs/configuring-playbook-bot-buscarron.md: add the common expression for linking to the documentation Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-buscarron.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index f74bf2ea8..e2762ed94 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -4,6 +4,8 @@ The playbook can install and configure [Buscarron](https://github.com/etkecc/bus Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room. +See the project's [documentation](https://github.com/etkecc/buscarron/blob/main/README.md) to learn what it does and why it might be useful to you. + ## Adjusting DNS records By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`. @@ -103,8 +105,6 @@ Here is an example for the `contact` form: If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server. -You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron). - ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-buscarron`. From 50f259d505008b388353df9583e61a4cf4d2f37f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 27 Dec 2024 10:30:35 -0500 Subject: [PATCH 297/952] Update docs/configuring-playbook-cactus-comments.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index ee5213be9..679a0cea5 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -61,6 +61,18 @@ If you've changed the default hostname, you may need to create a CNAME record fo When setting, replace `example.com` with your own. +### Extending the configuration + +There are some additional things you may wish to configure about the components. + +For `matrix-cactus-comments`, take a look at: + +- `roles/custom/matrix-cactus-comments/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + +For `matrix-cactus-comments-client`, take a look at: + +- `roles/custom/matrix-cactus-comments-client/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 909ca59cb7cee4f44670ce878dfca01ef3bc9581 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 02:49:37 +0900 Subject: [PATCH 298/952] Update docs/configuring-playbook-cactus-comments.md: remove the uncommon comment block Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 679a0cea5..77b6c54d2 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -25,10 +25,6 @@ If you wish to adjust it, see the section [below](#adjusting-the-cactus-comments To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml -################# -## Cactus Comments ## -################# - # This enables the backend (appservice) matrix_cactus_comments_enabled: true From 7f13747e82225418c3297f914484ce0667c09913 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 11:15:42 +0900 Subject: [PATCH 299/952] Update docs/configuring-playbook-cactus-comments.md: move the configuration enabled by default Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 77b6c54d2..4542fe11d 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -28,16 +28,15 @@ To enable Cactus Comments, add the following configuration to your `inventory/ho # This enables the backend (appservice) matrix_cactus_comments_enabled: true +# This enables client assets static files serving on `https://matrix.example.com/cactus-comments`. +# When the backend (appservice) is enabled, this is also enabled automatically, but we explicitly enable it here. +matrix_cactus_comments_client_enabled: true + # To allow guest comments without users needing to log in, you need to have guest registration enabled. # To do this you need to uncomment one of the following lines (depending if you are using Synapse or Dendrite as a homeserver) # If you don't know which one you use: The default is Synapse ;) # matrix_synapse_allow_guest_access: true # matrix_dendrite_allow_guest_access: true - -# This enables client assets static files serving on `https://matrix.example.com/cactus-comments`. -# When the backend (appservice) is enabled, this is also enabled automatically, -# but we explicitly enable it here. -matrix_cactus_comments_client_enabled: true ``` ### Adjusting the Cactus Comments' client URL (optional) From f2083aa8a7c62df1c6a1ae414a7d1e29d01dd769 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 02:51:19 +0900 Subject: [PATCH 300/952] Update docs/configuring-playbook-cactus-comments.md: replace the placeholders for the site name Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 4542fe11d..62dda0392 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -91,7 +91,7 @@ Upon starting Cactus Comments, a `bot.cactusbot` user account is created automat To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working. -Then, register a site by sending `register ` (where `` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room. +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. Now you are good to go and can embed the comment section on your website! @@ -105,7 +105,7 @@ After including the JavaScript and CSS asset files, insert a `
` where you'd
```` -Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `` with the one that has been registered above: +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: ```html From 83ad4d4975a0c4bacd7997a4f2a3fc8b9918bca9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 11:18:44 +0900 Subject: [PATCH 301/952] Update docs/configuring-playbook-cactus-comments.md: adopt the common instruction to start using the component Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 62dda0392..6dfdc4bd6 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -87,9 +87,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage -Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically. - -To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working. +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). 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. From 89864c6de0e8592164fa23aba2de50003acbe86e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 02:48:06 +0900 Subject: [PATCH 302/952] Update files for cactus-comments: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 15 +++++++++++++++ .../defaults/main.yml | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 6dfdc4bd6..e6410946e 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -129,3 +129,18 @@ Make sure to replace `example.com` with your base domain before you include the ``` **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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-cactus-comments` for the backend appservice or `journalctl -fu matrix-cactus-comments-client` for the server serving the client assets, respectively. + +### Increase logging verbosity + +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: + +```yaml +# Controls the SERVER_LOG_LEVEL environment variable. +# See: https://static-web-server.net/configuration/environment-variables/ +# Valid values: error, warn, info, debug, trace +matrix_cactus_comments_client_environment_variable_server_log_level: debug +``` diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 6a43ba585..7c5b15bfc 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -67,7 +67,7 @@ matrix_cactus_comments_client_environment_variable_server_port: 8080 # Controls the SERVER_LOG_LEVEL environment variable. # See: https://static-web-server.net/configuration/environment-variables/ -# Valid values: error, warn, info, debug or trace +# Valid values: error, warn, info, debug, trace matrix_cactus_comments_client_environment_variable_server_log_level: error # Controls the SERVER_LOG_REMOTE_ADDRESS environment variable. From 1f532fe90d259acdf676171cce9defe14d2aae9f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 11:40:28 +0900 Subject: [PATCH 303/952] Update docs/configuring-playbook-cactus-comments.md: add the configuration for changing the default username (bot.cactusbot) Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index e6410946e..3b6916d2f 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -32,6 +32,9 @@ matrix_cactus_comments_enabled: true # When the backend (appservice) is enabled, this is also enabled automatically, but we explicitly enable it here. matrix_cactus_comments_client_enabled: true +# Uncomment and adjust this part if you'd like to use a username different than the default +# matrix_cactus_comments_user_id: "bot.cactusbot" + # To allow guest comments without users needing to log in, you need to have guest registration enabled. # To do this you need to uncomment one of the following lines (depending if you are using Synapse or Dendrite as a homeserver) # If you don't know which one you use: The default is Synapse ;) From abff629e366f484dabeab45026afee14f0681edd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 11:42:10 +0900 Subject: [PATCH 304/952] Update docs/configuring-playbook-cactus-comments.md: replace "-" with "—" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index 3b6916d2f..f6adfda36 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -8,9 +8,9 @@ See the project's [documentation](https://cactus.chat/docs/getting-started/intro The playbook contains 2 roles for configuring different pieces of the Cactus Comments system: -- `matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver +- `matrix-cactus-comments` — the backend appservice integrating with the Matrix homeserver -- `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`) +- `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`) You can enable whichever component you need (typically both). From 76e346573c95caaca85ef895f766fa8c7edec96e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 12:18:31 +0900 Subject: [PATCH 305/952] Replace hyphen as dash with "Em Dash" unicode character (U+2014) This commit replaces hyphen characters used as dash with the actual unicode character for dash. It avoids using HTML character entity reference (—), because IMHO it would make it a bit harder to read documents as plain markdown files on your local text editor. Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 168 +++++++++--------- docs/README.md | 18 +- docs/configuring-playbook-bot-baibot.md | 6 +- ...guring-playbook-bridge-appservice-slack.md | 2 +- ...onfiguring-playbook-bridge-heisenbridge.md | 2 +- ...-playbook-bridge-mautrix-meta-messenger.md | 4 +- docs/configuring-playbook-cactus-comments.md | 4 +- docs/configuring-playbook-conduit.md | 2 +- docs/configuring-playbook-email2matrix.md | 16 +- .../configuring-playbook-external-postgres.md | 2 +- docs/configuring-playbook-jitsi.md | 4 +- docs/configuring-playbook-ma1sd.md | 10 +- ...-playbook-matrix-authentication-service.md | 6 +- docs/configuring-playbook-matrix-corporal.md | 2 +- .../configuring-playbook-matrix-media-repo.md | 8 +- ...onfiguring-playbook-matrix-registration.md | 2 +- docs/configuring-playbook-own-webserver.md | 10 +- ...onfiguring-playbook-prometheus-nginxlog.md | 4 +- docs/configuring-playbook-riot-web.md | 4 +- docs/configuring-playbook-s3.md | 8 +- docs/configuring-playbook-synapse-admin.md | 2 +- ...ng-playbook-synapse-s3-storage-provider.md | 14 +- docs/configuring-playbook-synapse.md | 18 +- docs/configuring-playbook-traefik.md | 2 +- docs/configuring-playbook.md | 28 +-- docs/container-images.md | 2 +- docs/faq.md | 16 +- docs/howto-server-delegation.md | 2 +- docs/importing-postgres.md | 4 +- docs/importing-synapse-sqlite.md | 2 +- docs/installing.md | 4 +- docs/just.md | 2 +- docs/maintenance-synapse.md | 6 +- docs/obtaining-access-tokens.md | 2 +- docs/playbook-tags.md | 14 +- docs/quick-start.md | 2 +- docs/registering-users.md | 4 +- group_vars/matrix_servers | 8 +- 38 files changed, 207 insertions(+), 207 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 60fee527e..d2951af62 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -60,11 +60,11 @@ You can disable authenticated media at any time by setting `matrix_synapse_enabl The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.). -Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis). +Earlier this year, we switched from Redis to KeyDB — see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis). Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey. -Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it. +Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency — you don't need custom configuration in `vars.yml` to enable it. Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens. @@ -186,7 +186,7 @@ As always, the playbook would let you know about this and point out any variable ## Support for baibot -The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖 +The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) — a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖 It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md). @@ -198,7 +198,7 @@ To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baib The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software. -The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork. +The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) — to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork. If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now. @@ -269,7 +269,7 @@ matrix_corporal_version: 2.8.0 ## synapse-usage-exporter support -Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape. +Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) — a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape. To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page. @@ -300,7 +300,7 @@ If you're using the playbook's Traefik instance to reverse-proxy to some other s If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp). -If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand. +If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` — a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand. ### HTTP/3 is enabled by default @@ -371,7 +371,7 @@ When generating new webhooks, you should start seeing the new URLs being used. **For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet. -However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs. +However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side — you merely need to reconfigure the remote systems that use your webhook URLs. # 2024-06-22 @@ -433,7 +433,7 @@ It should be noted that: ## Pantalaimon support -Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details. +Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms — see our Draupnir docs for details. See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started. @@ -453,9 +453,9 @@ The documentation page for [Draupnir for all](./docs/configuring-playbook-appser ## Support for bridging to Facebook/Messenger via the new mautrix-meta bridge -The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge. +The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) — the [mautrix-meta](https://github.com/mautrix/meta) bridge. -The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time. +The playbook now supports the new mautrix-meta bridge — a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time. If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See: @@ -476,9 +476,9 @@ The playbook has always used a very conservative cache factor (`matrix_synapse_c The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables: -- `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 -- `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 -- `matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s` +- `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 +- `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 +- `matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s` These values should be good defaults for most servers, but may change over time as we experiment further. @@ -491,7 +491,7 @@ Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.m This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook. -That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page. +That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain — redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page. If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file. @@ -515,7 +515,7 @@ To get started, refer to our [Specialized workers](./docs/configuring-playbook-s A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under: -- the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used +- the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license — the same license that this Ansible playbook has always used - a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation. @@ -546,7 +546,7 @@ matrix_synapse_version: v1.98.0 Notes: -- if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version +- if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` — see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version - running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution. @@ -564,14 +564,14 @@ As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir ### Backstory on `matrix-nginx-proxy` -We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago. +We gather here today to celebrate the loss of a once-beloved component in our stack — `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago. -For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others. +For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use — even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others. To us, `matrix-nginx-proxy` was: - an [nginx](https://nginx.org/)-based reverse-proxy -- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [coturn TURN server](./docs/configuring-playbook-turn.md) +- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) — retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [coturn TURN server](./docs/configuring-playbook-turn.md) - a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime - an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services "steal routes" from the homeserver - a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now) @@ -596,9 +596,9 @@ This reduces "network" hops (improving performance) and also decreases the numbe ### Traefik now has an extra job -Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job. +Previously, **Traefik had a single purpose** — being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case — it had this central (yet decentralized) job. -Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it. +Now, **Traefik has one more role** — it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it. To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint. @@ -633,7 +633,7 @@ If you don't do these changes (switching from `traefik_additional_entrypoints_au ### Supported reverse proxy types are now fewer -This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`). +This section is for people using a more custom reverse-proxy setup — those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`). Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups. @@ -658,7 +658,7 @@ Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out s Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network. -Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity. +Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity. All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things. @@ -672,11 +672,11 @@ This section is for people who are exposing monitoring metrics publicly, to be c Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file). -From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details. +From now on, there are new variables for doing roughly the same — `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details. `matrix-nginx-proxy` is not acting as a "global guardian" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason. -The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything! +The playbook will tell you about all variables that you need to migrate during runtime, so rest assured — you shouldn't be able to miss anything! ### Matrix static files @@ -696,9 +696,9 @@ We believe that using Traefik provides way too many benefits to worry about this The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front. -Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this. +Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic — hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this. -If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all. +If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part — SSL termination — happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all. ### Migration procedure @@ -710,7 +710,7 @@ The updated playbook will automatically perform some migration tasks for you: 3. It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do. -4. It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file. +4. It will tell you about all variables (`matrix_nginx_proxy_*` and many others — even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file. 5. It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file. @@ -833,17 +833,17 @@ The playbook should **automatically migrate your mautrix-signal installation to **TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected. -We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default. +We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) — the default value was making Synapse more wasteful of resources by default. Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms). The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member. -**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation. +**We go against the upstream default** in an effort to make Matrix federation more useful — a public room should be globally public — not only joinable, but also discoverable across federation. The **historical reasoning** behind this change is as follows: -- `allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation. +- `allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network — rooms should be joinable and discoverable across federation. - In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense. @@ -853,7 +853,7 @@ Here are **actions you may wish to take** as a result of this change: - (recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery. -- (switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for "mostly private" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them. +- (switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for "mostly private" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces — you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting — controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them. - (keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures. @@ -912,7 +912,7 @@ Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playb ## matrix-media-repo support -Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features. +Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) — an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features. To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page. @@ -936,7 +936,7 @@ If you'd like to go back to the old behavior, add the following to your configur **TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact. -The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so. +The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project — an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so. As part of the extraction process of this role out of the Matrix playbook, a few other things improved: @@ -966,7 +966,7 @@ This change was already applied a while before this entry, but as some users wer **TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact. -The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so. +The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project — an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so. Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know. @@ -985,7 +985,7 @@ If you're making use of Prometheus via this playbook, you will need to update va Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically. -If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because: +If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before — see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because: - it runs on a more up-to-date version of `rust-synapse-compress-state` - it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore @@ -1049,7 +1049,7 @@ Until now, we've been doing the migration gradually and keeping full backward co - Traefik managed by the user in another way - another reverse-proxy on the same host (`127.0.0.1` port exposure) - another reverse-proxy on another host (`0.0.0.0` port exposure) -- `matrix-nginx-proxy` - an `nginx` container managed by the playbook +- `matrix-nginx-proxy` — an `nginx` container managed by the playbook - `nginx` webserver operated by the user, running without a container on the same server Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support. @@ -1166,7 +1166,7 @@ You need to **update your roles** (`just roles` or `make roles`) regardless of w ### Motivation for redoing our reverse-proxy setup -The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**. +The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though — hard to figure out and with lots of variables to toggle to make things work as you'd expect — huge **operational complexity**. We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**. @@ -1181,19 +1181,19 @@ Others still, wanted to run Matrix locally (no SSL certificates), regardless of Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations. -When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still… yikes). +When using `matrix-nginx-proxy` as is, we still had another problem — one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime — see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still… yikes). The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks: -- [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager -- [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service -- [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform +- [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server — an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager +- [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) — for hosting the [Gitea](https://gitea.io/) git source code hosting service +- [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy. These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`. -Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with. +Finally, at [etke.cc — a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with. ### How do these changes fix all these problems? @@ -1258,7 +1258,7 @@ You can help by: - **explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles -- **adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers). +- **adding native Traefik support to a role** (requires adding Traefik labels, etc.) — for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers). - **adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server @@ -1341,16 +1341,16 @@ Other roles which aren't strictly related to Matrix are likely to follow this fa We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands. -In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same. +In addition, we've added support for running commands via [just](https://github.com/casey/just) — a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same. Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples: - `just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command -- `just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command) -- `just run-tags install-mautrix-slack,start` - to run specific playbook tags -- `just start-all` - (re-)starts all services -- `just stop-group postgres` - to stop only the Postgres service -- `just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`) +- `just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command) +- `just run-tags install-mautrix-slack,start` — to run specific playbook tags +- `just start-all` — (re-)starts all services +- `just stop-group postgres` — to stop only the Postgres service +- `just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`) Additional helpful commands and shortcuts may be defined in the future. @@ -1370,7 +1370,7 @@ Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now ## ChatGPT support -Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model. +Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) — a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model. See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started. @@ -1379,7 +1379,7 @@ See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md ## matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role -Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup). +Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role — [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup). You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix. @@ -1388,7 +1388,7 @@ You'll need to rename your `matrix_postgres_backup`-prefixed variables such that ## matrix-postgres has been replaced by the ansible-role-postgres external role -**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`). +**TLDR**: the tasks that install the integrated Postgres server now live in an external role — [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`). The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability. @@ -1399,7 +1399,7 @@ The new role is an upgraded version of the old `matrix-postgres` role with these You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix. -Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin). +Note: the systemd service still remains the same — `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin). ## The playbook no longer installs scripts to /usr/local/bin @@ -1455,9 +1455,9 @@ These additional roles are downloaded into the playbook directory (to `roles/gal # 2022-11-20 -## (Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service +## (Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service -**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below. +**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected — see [Webserver configuration](#webserver-configuration) below. ### Background @@ -1475,7 +1475,7 @@ From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxyin - `matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic - `matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic -- simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers +- simplify `matrix-nginx-proxy` configuration — it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers - allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled @@ -1491,7 +1491,7 @@ Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx- - if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work -- if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead +- if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default — just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead - if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead @@ -1527,7 +1527,7 @@ Starting now, the playbook is composed of 2 types of Ansible roles: - those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community. -We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role. +We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves — installing Docker on the server from our `matrix-base` role, etc. — something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role. Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook. @@ -1540,7 +1540,7 @@ Some variable names will change during the transition to having more and more ex **`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.** -You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work). +You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) — a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work). This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`. @@ -1572,7 +1572,7 @@ With the new Synapse-customization feature in the playbook, we use the original ## matrix-ldap-registration-proxy support -Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP. +Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) — a proxy which handles Matrix registration requests and forwards them to LDAP. See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started. @@ -1664,7 +1664,7 @@ Below we'll discuss **potential backward incompatibilities**. ## Cactus Comments support -Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix. +Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) — federated comment system for the web based on Matrix. See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started. @@ -1719,7 +1719,7 @@ Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now ## matrix-appservice-kakaotalk support -The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this! +The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) — a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this! See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started. @@ -1728,7 +1728,7 @@ See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bri ## maubot support -Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system. +Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) — a plugin-based Matrix bot system. See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started. @@ -1869,7 +1869,7 @@ See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) docum ## matrix-registration-bot support -Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server. +Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) — a bot that is used to create and manage registration tokens for a Matrix server. See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started. @@ -1911,7 +1911,7 @@ When self-building, the playbook used to `git clone` repositories (into `/matrix If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories. -The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf` +The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places — something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf` # 2022-03-17 @@ -1998,7 +1998,7 @@ We're excited to gain support for other homeserver implementations, like [Condui ## Honoroit bot support -Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot. +Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) — a helpdesk bot. See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started. @@ -2007,7 +2007,7 @@ See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documen ## Cinny support -Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client. +Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) — a new simple, elegant and secure Matrix client. By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook. @@ -2061,7 +2061,7 @@ To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridgi # 2021-08-20 -# Sygnal upgraded - ARM support and no longer requires a database +# Sygnal upgraded — ARM support and no longer requires a database The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`. @@ -2076,7 +2076,7 @@ The new version is also available for the ARM architecture. It also no longer re ## Hydrogen support -Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support. +Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) — a new lightweight Matrix client with legacy and mobile browser support. By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook. @@ -2166,7 +2166,7 @@ After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansibl Having support for workers makes the playbook suitable for larger homeserver deployments. -Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk). +Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 — TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk). By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup). @@ -2317,7 +2317,7 @@ You have 3 ways to proceed: - stop the bridge (`systemctl stop matrix-mautrix-facebook`) - create a new `matrix_mautrix_facebook` Postgres database for it - run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well) - - define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml` + - define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) — you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml` - switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file) - re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`) - send a `login` message to the Facebook bridge bot again @@ -2406,7 +2406,7 @@ Moving all services to Postgres brings a few **benefits** to us: - **improved performance** - **improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres. - **easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further. -- we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc. +- we're now **more prepared to introduce other services** that need a Postgres database — [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc. ### Key takeway @@ -2556,7 +2556,7 @@ If you have have an existing setup, it's likely running on an older Postgres ver ## matrix-registration support -The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves. +The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) — an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves. See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started. @@ -2659,7 +2659,7 @@ See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database. -ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc. +ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users — including users created by bridges, etc. Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**. @@ -2811,7 +2811,7 @@ Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playboo Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram). -This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you. +This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) — yet another component that this playbook can install for you. To get started, following the playbook's documentation for the bridge you'd like to configure. @@ -3065,10 +3065,10 @@ Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/d Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different: -- `edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message -- `inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message. -- `authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible -- `whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands +- `edits_as_replies` (used to be `false`, now `true`) — previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message +- `inline_images` (used to be `true`, now `false`) — this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message. +- `authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible +- `whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where). @@ -3109,7 +3109,7 @@ Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/d Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup. -`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`. +`matrix_*_expose_port` variables were not granular enough — sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`. All such variables have been superseded by a better (more flexible) way to do it. @@ -3317,7 +3317,7 @@ Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The fi If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md)). -Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99). +Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 — around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99). **What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0: @@ -3373,7 +3373,7 @@ Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) cont ## (BC Break) Making the playbook's roles more independent of one another -The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. +The following change **affects people running a more non-standard setup** — external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers). Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components. @@ -3645,7 +3645,7 @@ The playbook can now [check if services are configured correctly](docs/maintenan ## Presence tracking made configurable -The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled). +The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` — enabled). If users participate in large rooms with many other servers, disabling presence will decrease server load significantly. diff --git a/docs/README.md b/docs/README.md index 6a0cf1059..600a4c557 100644 --- a/docs/README.md +++ b/docs/README.md @@ -27,23 +27,23 @@ NOTE: You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md) -- [Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation +- [Administration](configuring-playbook.md#administration) — services that help you in administrating and monitoring your Matrix installation -- [Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver +- [Authentication and user-related](configuring-playbook.md#authentication-and-user-related) — extend and modify how users are authenticated on your homeserver -- [Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation +- [Bots](configuring-playbook.md#bots) — bots provide various additional functionality to your installation -- [Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks +- [Bridges](configuring-playbook.md#bridging-other-networks) — bridges can be used to connect your Matrix installation with third-party communication networks -- [Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains +- [Clients](configuring-playbook.md#clients) — web clients for Matrix that you can host on your own domains -- [Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system +- [Core service adjustments](configuring-playbook.md#core-service-adjustments) — backbone of your Matrix system -- [File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder +- [File Storage](configuring-playbook.md#file-storage) — use alternative file storage to the default `media_store` folder -- [Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories +- [Other specialized services](configuring-playbook.md#other-specialized-services) — various services that don't fit any other categories ## 👨‍🔧 Maintenance @@ -63,7 +63,7 @@ If your server and services experience issues, feel free to come to [our support ## Other documentation pages -- ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook +- ℹ️ **[FAQ](faq.md)** — various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index bdc29eafd..01984a4b7 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -123,7 +123,7 @@ Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is op You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance). -Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands. +Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands. The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc). @@ -250,7 +250,7 @@ You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc. -Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started. +Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started. As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset). @@ -305,7 +305,7 @@ Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/c 💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**. -As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models). +As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models). 💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers). diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index d21e1496a..4d602da35 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -100,7 +100,7 @@ To use the bridge, you need to send `/invite @slackbot:example.com` to invite th If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps: -- Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID - it will look something like `!qporfwt:example.com`. +- Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID — it will look something like `!qporfwt:example.com`. - Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix. - Determine the "channel ID" that Slack uses to identify the channel. You can see it when you open a given Slack channel in a browser. The URL reads like this: `https://app.slack.com/client/XXX//details/`. - Issue a link command in the administration control room with these collected values as arguments: diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index a464a60f3..d3a08fb82 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -2,7 +2,7 @@ **Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook. -The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you. +The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) — the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you. See the project's [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). diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index de3421147..96041c829 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -45,8 +45,8 @@ As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge s The bridge can pull your Messenger messages via 3 different methods: - (`facebook`) Facebook via `facebook.com` -- (`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads -- (default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account +- (`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) — does not currently proxy media downloads +- (default) (`messenger`) Messenger via `messenger.com` — usable even without a Facebook account 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). diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index f6adfda36..f6b704133 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -8,9 +8,9 @@ See the project's [documentation](https://cactus.chat/docs/getting-started/intro The playbook contains 2 roles for configuring different pieces of the Cactus Comments system: -- `matrix-cactus-comments` — the backend appservice integrating with the Matrix homeserver +- `matrix-cactus-comments` — the backend appservice integrating with the Matrix homeserver -- `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`) +- `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`) You can enable whichever component you need (typically both). diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index f2fc70096..760307b22 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -42,7 +42,7 @@ matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/ Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure: 1. Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily -2. Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md)) +2. Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` — see [Installing](installing.md)) 3. Create your first user via Element Web or any other client which supports creating users 4. Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml` 5. Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time) diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 64ef5e112..7b24cd335 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -89,14 +89,14 @@ matrix_email2matrix_matrix_mappings: where: -* MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId -* MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message -* MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable -* MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain) -* MatrixAccessToken - sender user's access token -* IgnoreSubject - if set to "true", the subject is not bridged to Matrix -* IgnoreBody - if set to "true", the message body is not bridged to Matrix -* SkipMarkdown - if set to "true", emails are bridged as plain text Matrix message instead of Markdown (actually HTML) +* MailboxName — local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId +* MatrixRoomId — internal ID of the room, to which received emails are sent as Matrix message +* MatrixHomeserverUrl — URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable +* MatrixUserId — the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain) +* MatrixAccessToken — sender user's access token +* IgnoreSubject — if set to "true", the subject is not bridged to Matrix +* IgnoreBody — if set to "true", the message body is not bridged to Matrix +* SkipMarkdown — if set to "true", emails are bridged as plain text Matrix message instead of Markdown (actually HTML) Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md). diff --git a/docs/configuring-playbook-external-postgres.md b/docs/configuring-playbook-external-postgres.md index e922c8299..ca49d985c 100644 --- a/docs/configuring-playbook-external-postgres.md +++ b/docs/configuring-playbook-external-postgres.md @@ -2,7 +2,7 @@ By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document. -**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**. +**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** — you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**. If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 882d434e4..b9aca9819 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -12,8 +12,8 @@ See the project's [documentation](https://jitsi.github.io/handbook/) to learn wh You may need to open the following ports to your server: -- `4443/tcp` - RTP media fallback over TCP -- `10000/udp` - RTP media over UDP. Depending on your firewall/NAT 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)). +- `4443/tcp` — RTP media fallback over TCP +- `10000/udp` — RTP media over UDP. Depending on your firewall/NAT configuration, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)). ## Adjusting DNS records diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index c2f9d3132..7138ce3d3 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -65,15 +65,15 @@ If you'd like to change the default email templates used by ma1sd, take a look a To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables: -- `matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse +- `matrix_synapse_enable_registration` — to enable user-initiated registration in Synapse -- `matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation. +- `matrix_synapse_enable_registration_captcha` — to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation. -- `matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering +- `matrix_synapse_registrations_require_3pid` — a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering -- 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 +- 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 -- `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`. +- `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`. **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). diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index 616ab54cc..ee8960352 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -1,6 +1,6 @@ # Setting up Matrix Authentication Service (optional) -The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/). +The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/). Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website. @@ -63,13 +63,13 @@ This section details what you can expect when switching to the Matrix Authentica - ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break. -- ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the "admin" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`) +- ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the "admin" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`) - ⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch. - ⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration). -- ⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md). +- ⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed — all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md). - ✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad. diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index fea63b552..03bf7b22f 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -139,4 +139,4 @@ The following local filesystem paths are mounted in the `matrix-corporal` contai - `/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write) -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). +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). diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 4a9c31372..748d3aaf0 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -60,10 +60,10 @@ matrix_media_repo_admins: [] # To disable this datastore, making it readonly, specify `forKinds: []`. # # The kinds available are: -# thumbnails - Used to store thumbnails of media (local and remote). -# remote_media - Original copies of remote media (servers not configured by this repo). -# local_media - Original uploads for local media. -# archives - Archives of content (GDPR and similar requests). +# thumbnails — Used to store thumbnails of media (local and remote). +# remote_media — Original copies of remote media (servers not configured by this repo). +# local_media — Original uploads for local media. +# archives — Archives of content (GDPR and similar requests). matrix_media_repo_datastore_file_for_kinds: ["thumbnails", "remote_media", "local_media", "archives"] matrix_media_repo_datastore_s3_for_kinds: [] diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index fb5e04b31..311be8fb7 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -64,7 +64,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju **matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration` -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`. +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`. We make the most common APIs easy to use via the playbook (see below). diff --git a/docs/configuring-playbook-own-webserver.md b/docs/configuring-playbook-own-webserver.md index 8f8f8682d..d738183a6 100644 --- a/docs/configuring-playbook-own-webserver.md +++ b/docs/configuring-playbook-own-webserver.md @@ -56,10 +56,10 @@ By default, the playbook configured a `default` certificate resolver and multipl You need to configure 4 entrypoints for your Traefik server: -- `web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`) -- `web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services -- `matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API -- `matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver +- `web` (TCP port `80`) — used for redirecting to HTTPS (`web-secure`) +- `web-secure` (TCP port `443`) — used for exposing the Matrix Client-Server API and all other services +- `matrix-federation` (TCP port `8448`) — used for exposing the Matrix Federation API +- `matrix-internal-matrix-client-api` (TCP port `8008`) — used internally for addon services (bridges, bots) to communicate with the homserver Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook). @@ -127,7 +127,7 @@ Doing this is possible, but requires manual work. There are 2 ways to go about it: -- (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 +- (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 - (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 diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 1683210c3..224061c07 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -8,7 +8,7 @@ It will collect access logs from various nginx reverse-proxies which may be used **Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant. -To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server). +To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary — see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server). If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created. @@ -48,7 +48,7 @@ Metrics and resulting graphs can contain a lot of information. NginX logs contai ## Save metrics on an external Prometheus server -The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network. +The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index e008a3f89..4e312a7c2 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -21,9 +21,9 @@ We used to set up Riot at the `riot.example.com` domain. The playbook now sets u There are a few options for handling this: -- (**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: "riot.{{ matrix_domain }}"` +- (**avoiding changes** — using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: "riot.{{ matrix_domain }}"` -- (**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case. +- (**embracing changes** — using only `element.example.com`) — set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case. ### Re-running the playbook diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md index cb43c62fb..2f6f1ad49 100644 --- a/docs/configuring-playbook-s3.md +++ b/docs/configuring-playbook-s3.md @@ -29,7 +29,7 @@ Here are some of the important aspects of choosing the right provider: - if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns) - if a provider's infrastructure such as data center is centralized or distributed - if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.) -- if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case +- if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) — likely not too important for the common use-case ## Bucket creation and Security Configuration @@ -83,11 +83,11 @@ The `keyID` value is your **Access Key** and `applicationKey` is your **Secret K For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need: -- **Endpoint URL** - this is the **Endpoint** value you saw above, but prefixed with `https://` +- **Endpoint URL** — this is the **Endpoint** value you saw above, but prefixed with `https://` -- **Region** - use the value you see in the Endpoint (e.g. `us-west-002`) +- **Region** — use the value you see in the Endpoint (e.g. `us-west-002`) -- **Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value. +- **Storage Class** — use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value. ## Other providers diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index bc404b9f1..b5e8991bd 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -25,7 +25,7 @@ matrix_synapse_admin_enabled: true - for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` - for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true` -By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) - the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable. +By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable. > [!WARNING] > If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all. diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index 02b79c240..c564e4c83 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -17,7 +17,7 @@ The way media storage providers in Synapse work has some caveats: You may be thinking **if all files are stored locally as well, what's the point**? -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. +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. 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. @@ -33,13 +33,13 @@ matrix_synapse_ext_synapse_s3_storage_provider_config_region_name: some-region-n matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url: https://s3.REGION_NAME.amazonaws.com # adjust this matrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD # or STANDARD_IA, etc. -# Authentication Method 1 - (access key ID + secret) +# Authentication Method 1 — (access key ID + secret) # This works on all providers (AWS and other compatible systems). # Uncomment the variables below to use it. # matrix_synapse_ext_synapse_s3_storage_provider_config_access_key_id: access-key-goes-here # matrix_synapse_ext_synapse_s3_storage_provider_config_secret_access_key: secret-key-goes-here -# Authentication Method 2 - EC2 instance profile which grants permission to access S3 +# Authentication Method 2 — EC2 instance profile which grants permission to access S3 # This only works on AWS when your server is hosted on an EC2 instance with the correct instance profile set. # Uncomment the variable below to use it. # matrix_synapse_ext_synapse_s3_storage_provider_config_ec2_instance_profile: true @@ -78,13 +78,13 @@ To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3 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). -Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute): +Then use the following commands (`$` values come from environment variables — they're **not placeholders** that you need to substitute): -1. `s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on +1. `s3_media_upload update-db $UPDATE_DB_DURATION` — create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on - `$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`) - `$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**). -2. `s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory -3. `s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory +2. `s3_media_upload check-deleted $MEDIA_PATH` — check whether files in the local cache still exist in the local media repository directory +3. `s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` — uploads locally-stored files to S3 and deletes them from the local media repository directory The `s3_media_upload upload` command may take a lot of time to complete. diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 6b1ec9f3e..12ae0f061 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -22,9 +22,9 @@ By default, this enables the `one-of-each` [worker preset](#worker-presets), but We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now): -- (federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance -- (generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers -- (specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead +- (federation-only) `little-federation-helper` — a very minimal worker configuration to improve federation performance +- (generic) `one-of-each` — defaults to one worker of each supported type — no smart routing, just generic workers +- (specialized) `specialized-workers` — defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs. @@ -34,20 +34,20 @@ Previously, the playbook only supported the most basic type of load-balancing. W This is **still the default load-balancing method (preset) used by the playbook**. -To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`. +To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet — explicitly set it as `one-of-each`. You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each). ##### Specialized workers -The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested. +The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requestor and/or on the resource (room, etc.) being requested. The playbook supports these **4 types** of specialized workers: -- Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms -- Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync)) -- Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**) -- Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**) +- Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms +- Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync)) +- Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**) +- Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**) To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each). diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index b9f3e86e8..cab20454f 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -59,7 +59,7 @@ However, if your service does not run on a container or runs on another machine, 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. -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`. +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`. First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files: diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 7836190f8..a2332f9bf 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -111,7 +111,7 @@ Use alternative file storage to the default `media_store` folder. Bridges can be used to connect your Matrix installation with third-party communication networks. -- [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) - a common guide for configuring mautrix bridges +- [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges - [Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md) @@ -145,7 +145,7 @@ Bridges can be used to connect your Matrix installation with third-party communi - [Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md) -- [Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira). +- [Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) — a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira). - [Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) @@ -175,23 +175,23 @@ Bridges can be used to connect your Matrix installation with third-party communi Bots provide various additional functionality to your installation. -- [Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md)) +- [Setting up baibot](configuring-playbook-bot-baibot.md) — a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md)) -- [Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff +- [Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) — a bot to remind you about stuff -- [Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users +- [Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) — a bot to create and manage registration tokens to invite users -- [Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system +- [Setting up maubot](configuring-playbook-bot-maubot.md) — a plugin-based Matrix bot system -- [Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot +- [Setting up Honoroit](configuring-playbook-bot-honoroit.md) — a helpdesk bot -- [Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot +- [Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) — a moderation tool/bot -- [Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer +- [Setting up Draupnir](configuring-playbook-bot-draupnir.md) — a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer -- [Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances +- [Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) — like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances -- [Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room +- [Setting up Buscarron](configuring-playbook-bot-buscarron.md) — a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room ### Administration @@ -208,9 +208,9 @@ Services that help you in administrating and monitoring your Matrix installation - [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) - Backups: - - [Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database + - [Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database - - [Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files) + - [Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files) ### Other specialized services @@ -226,7 +226,7 @@ Various services that don't fit any other categories. - [Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md) -- [Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix +- [Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix - [Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced) diff --git a/docs/container-images.md b/docs/container-images.md index 4f77a7bc6..4c43786b8 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -32,7 +32,7 @@ Services that run on the server to make the various parts of your installation w | ------- | --------------- | -------- | ----------- | | [PostgreSQL](configuring-playbook-external-postgres.md) | [postgres](https://hub.docker.com/_/postgres/) | ✅ | Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible. | | [coturn](configuring-playbook-turn.md) | [coturn/coturn](https://hub.docker.com/r/coturn/coturn/) | ✅ | STUN/TURN server for WebRTC audio/video calls | -| [Traefik](configuring-playbook-traefik.md) | [Traefik](https://hub.docker.com/_/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md) | +| [Traefik](configuring-playbook-traefik.md) | [Traefik](https://hub.docker.com/_/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md) | | [Let's Encrypt](configuring-playbook-ssl-certificates.md) | [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) | ✅ | The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/) | | [Exim](configuring-playbook-email.md) | [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | | [ma1sd](configuring-playbook-ma1sd.md) | [ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/) | ❌ | Matrix Identity Server | diff --git a/docs/faq.md b/docs/faq.md index 51e093fc7..92b9238b1 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -32,7 +32,7 @@ If you'd like to host your own server (you being `@alice:example.com`), you'd ne In short: -- Matrix is the protocol - a set of rules about how the chat network operates +- Matrix is the protocol — a set of rules about how the chat network operates - 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/). - Synapse is a server program you can use to host your very own Matrix server. @@ -48,15 +48,15 @@ Besides setting up your own bridges (preferable), you can also use some [public ### How do I get started with Matrix? -One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`). +One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people — one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`). There are 3 ways to get into Matrix, depending on your technical ability and needs: -- **using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting. +- **using the existing default server** — the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting. -- **using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login. +- **using some other server** — instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login. -- **using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user 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). +- **using your own server** — running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server). ### How do I set up my own Matrix server? @@ -117,7 +117,7 @@ All services run in Docker containers (most being officially provided by each co Reasons are similar to the reasons for not installing manually. -Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc. +Besides Synapse, you'd need other things — a Postgres database, likely the [Element](https://element.io) client, etc., etc. Using the playbook, you get all these components in a way that works well together out of the box. @@ -129,7 +129,7 @@ It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy. This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but: -- 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 +- 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 - this one installs and hooks together **a lot more Matrix-related services** for you (see above) @@ -391,7 +391,7 @@ Yes, you can. You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server. -This Ansible playbook guides you into installing a server for `example.com` (user 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) +This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain) After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md). diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index 429e06982..602fda481 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -11,7 +11,7 @@ Both methods have their place and will continue to do so. You only need to use j For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation. -**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ. +**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain — `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ. ## Server Delegation via a well-known file diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index 44c49c7c6..d73b3c95a 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -1,7 +1,7 @@ # Importing an existing Postgres database from another installation (optional) 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)). +(don't forget to import your Synapse `media_store` files as well — see [the importing-synape-media-store guide](importing-synapse-media-store.md)). ## Prerequisites @@ -64,7 +64,7 @@ It can be worked around by changing the username to `synapse`, for example by us $ sed -i "s/OWNER TO synapse_user;/OWNER TO synapse;/g" homeserver.sql ``` -This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine. +This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` — replacing `matrix` only would… well — you can imagine. Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as: diff --git a/docs/importing-synapse-sqlite.md b/docs/importing-synapse-sqlite.md index 2453e8cfc..29fa0594a 100644 --- a/docs/importing-synapse-sqlite.md +++ b/docs/importing-synapse-sqlite.md @@ -1,6 +1,6 @@ # Importing an existing SQLite database from another Synapse installation (optional) -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)). +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)). While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database. diff --git a/docs/installing.md b/docs/installing.md index bcd2e2325..10bbd32bc 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -27,7 +27,7 @@ If you **don't** use SSH keys for authentication, but rather a regular password, If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands. -There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data). +There 2 ways to start the installation process — depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data). **Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it. @@ -130,7 +130,7 @@ After finilizing the installation, you can: - or learn how to [maintain your server](faq.md#maintenance) - or join some Matrix rooms: * via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers. - * or come say Hi in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. + * or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. - or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate)) ### Maintaining your setup in the future diff --git a/docs/just.md b/docs/just.md index ecc09e495..53743a03b 100644 --- a/docs/just.md +++ b/docs/just.md @@ -2,7 +2,7 @@ We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands. -In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing. +In addition, we have added support for running commands via [`just`](https://github.com/casey/just) — a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing. The `just` utility executes shortcut commands (called as "recipes"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets. diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index 3bb315fcb..bc78f28fd 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -88,9 +88,9 @@ Tuning the cache factor is useful only to a limited degree (as its crude to do i Cache autotuning is **enabled by default** and controlled via the following variables: -- `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 -- `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 -- `matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s` +- `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 +- `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 +- `matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s` 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). diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index 909d62b8f..3466f1a4e 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -9,7 +9,7 @@ When setting up some optional features like bots and bridges you will need to pr The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already. -Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password. +Below, we describe 2 ways to generate an access token for a user — using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password. ## Obtain an access token via Element Web diff --git a/docs/playbook-tags.md b/docs/playbook-tags.md index 8e2a064ce..02da3ea7e 100644 --- a/docs/playbook-tags.md +++ b/docs/playbook-tags.md @@ -6,19 +6,19 @@ The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml -- Here are some playbook tags that you should be familiar with: -- `setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services +- `setup-all` — runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services -- `install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed +- `install-all` — like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed -- `setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag). +- `setup-SERVICE` (e.g. `setup-postmoogle`) — runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag). -- `install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information. +- `install-SERVICE` (e.g. `install-postmoogle`) — like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information. -- `start` - starts all systemd services and makes them start automatically in the future +- `start` — starts all systemd services and makes them start automatically in the future -- `stop` - stops all systemd services +- `stop` — stops all systemd services -- `ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created +- `ensure-matrix-users-created` — a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created **Notes**: - `setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc. diff --git a/docs/quick-start.md b/docs/quick-start.md index 9f75b61f7..fbb579f61 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -193,7 +193,7 @@ You should be able to log in to it with your own [Element Web](configuring-playb **If you successfully logged in to your account, installing and configuring is complete**🎉 -Come say Hi👋 in our support room - [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. +Come say Hi👋 in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. ## Things to do next diff --git a/docs/registering-users.md b/docs/registering-users.md index 1d92ce131..2972378b6 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -143,8 +143,8 @@ where: If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by: -- running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html) -- running `\c synapse` - to change to the `synapse` database +- running `/matrix/postgres/bin/cli` — to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html) +- running `\c synapse` — to change to the `synapse` database You can then proceed to run the query above. diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 4e5f0c9b2..857a470d9 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -257,7 +257,7 @@ matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_s # - so that addon services (starting later) can communicte with the homeserver via Traefik's internal entrypoint # (see `matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled`) # - core services (the homeserver) get a level of ~1000 -# - services that the homeserver depends on (database, Redis, ntfy, coturn, etc.) get a lower level - between 500 and 1000 +# - services that the homeserver depends on (database, Redis, ntfy, coturn, etc.) get a lower level — between 500 and 1000 # - coturn gets a higher level if `devture_systemd_service_manager_service_restart_mode == 'one-by-one'` to intentionally delay it, because: # - starting services one by one means that the service manager role waits for each service to fully start before proceeding to the next one # - if coturn has a lower priority than the homeserver, it would be started before it @@ -268,8 +268,8 @@ matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_s # - Matrix utility services (bridges, bots) get a level of 2000/2200, so that: # - they can start before the reverse-proxy # - so that, when the reverse-proxy is up (Matrix is up), all bots and bridges can be interacted with -# - monitoring services (Prometheus, Grafana, …) get a level of 4000 - they can start later than all-of-Matrix -# - services which aren't time-sensitive (various crons and timers) get a level of 5000 - they can start later than all-of-Matrix +# - monitoring services (Prometheus, Grafana, …) get a level of 4000 — they can start later than all-of-Matrix +# - services which aren't time-sensitive (various crons and timers) get a level of 5000 — they can start later than all-of-Matrix devture_systemd_service_manager_services_list_auto: | {{ ([{'name': (backup_borg_identifier + '.timer'), 'priority': 5000, 'groups': ['matrix', 'backup', 'borg']}] if backup_borg_enabled else []) @@ -5966,7 +5966,7 @@ matrix_user_verification_service_container_additional_networks: | ) | unique }} -# If Jitsi is managed by this playbook we can use the docker network - no need to expose a port. +# If Jitsi is managed by this playbook we can use the docker network — no need to expose a port. # If Jitsi is not managed by this playbook, or you otherwise have a need for it, you can expose # matrix-user-verfification-services's client-server port to port 3003. # By default Matrix-User-Verification-Service binds to port 3000, which collides with grafana, therefore this uses port 3003. From 1db5f76024ba23bf29ac4aea5a4889e57b90ef4d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 16:35:06 +0900 Subject: [PATCH 306/952] Replace double hyphens with "Em Dash" unicode character (U+2014) Signed-off-by: Suguru Hirahara --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/i-need-help.md | 2 +- CHANGELOG.md | 4 ++-- docs/configuring-playbook-own-webserver.md | 2 +- docs/configuring-playbook-riot-web.md | 2 +- docs/configuring-well-known.md | 8 ++++---- docs/faq.md | 2 +- group_vars/matrix_servers | 2 +- .../matrix-client-schildichat/tasks/setup_install.yml | 2 +- .../conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 | 6 +++--- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 11 files changed, 17 insertions(+), 17 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index fff721410..985806d5b 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -34,7 +34,7 @@ A clear and concise description of what you expected to happen. **Ansible:** If your problem appears to be with Ansible, tell us: -- where you run Ansible -- e.g. on the Matrix server itself; on another computer (which OS? distro? standard installation or containerized Ansible?) +- where you run Ansible — e.g. on the Matrix server itself; on another computer (which OS? distro? standard installation or containerized Ansible?) - what version of Ansible you're running (see `ansible --version`) -- [Checking if services work](maintenance-checking-services.md) - - [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md) - [PostgreSQL maintenance](maintenance-postgres.md) diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index 87e573830..e87d10e79 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -2,7 +2,7 @@ By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server. -**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated. +**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. ## Federating only with select servers diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index e7bbc9562..58bd1615b 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -185,4 +185,4 @@ No matter which method you've used to set up the well-known files, if you've don - `https://example.com/.well-known/matrix/client` - `https://example.com/.well-known/matrix/support` -You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md). +You can also check if everything is configured correctly, by [checking if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work). diff --git a/docs/installing.md b/docs/installing.md index 10bbd32bc..860e8d9bf 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -124,7 +124,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files After finilizing the installation, you can: -- [check if services work](maintenance-checking-services.md) +- [check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work) - or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.) - or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md) - or learn how to [maintain your server](faq.md#maintenance) diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 0ab46f900..41704dfe4 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -38,6 +38,22 @@ matrix_synapse_root_log_level: "INFO" Re-run the playbook after making these configuration changes. +## How to check if services work + +The playbook can perform a check to ensure that you've configured things correctly and that services are running. + +To perform the check, run: + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=self-check +``` + +The shortcut command with `just` program is also available: `just run-tags self-check` + +If it's all green, everything is probably running correctly. + +Besides this self-check, you can also check 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. + ## Remove unused Docker data You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information. diff --git a/docs/maintenance-checking-services.md b/docs/maintenance-checking-services.md deleted file mode 100644 index b2d90554c..000000000 --- a/docs/maintenance-checking-services.md +++ /dev/null @@ -1,15 +0,0 @@ -# Checking if services work - -The playbook can perform a check to ensure that you've configured things correctly and that services are running. - -To perform the check, run: - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=self-check -``` - -The shortcut command with `just` program is also available: `just run-tags self-check` - -If it's all green, everything is probably running correctly. - -Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain. diff --git a/docs/maintenance-migrating.md b/docs/maintenance-migrating.md index e2c0a7efa..2aa2e5a86 100644 --- a/docs/maintenance-migrating.md +++ b/docs/maintenance-migrating.md @@ -66,6 +66,6 @@ The shortcut command with `just` program is also available: `just run-tags insta ### Check if services work -After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md) +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) Having make sure that both services and federation work as expected, you can safely shutdown the old server. From cbcbe33a91a80375393701309d2aa3fc43036bb4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:10:12 +0900 Subject: [PATCH 368/952] Update docs for Element Web and SchildiChat Web: add the instruction to change the default theme from light to dark Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-element-web.md | 13 +++++++++++-- docs/configuring-playbook-client-schildichat-web.md | 13 +++++++++++-- 2 files changed, 22 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 4d832752c..0656c93fa 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -19,11 +19,20 @@ When setting, replace `example.com` with your own. ### Themes -You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually. +#### Change the default theme + +You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +# Controls the default theme +matrix_client_element_default_theme: 'dark' +``` #### Use themes by `element-themes` -To pull the themes from the `element-themes` project and use them for your Element Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +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. + +To pull the themes and use them for your Element Web instance, add the following configuration to your `vars.yml` file: ```yaml matrix_client_element_themes_enabled: true diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index e9781255a..147d8056e 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -24,11 +24,20 @@ matrix_client_schildichat_enabled: true ### Themes -You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually. +#### Change the default theme + +You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +# Controls the default theme +matrix_client_schildichat_default_theme: 'dark' +``` #### Use themes by `element-themes` -To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file: +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. + +To pull the themes and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file: ```yaml matrix_client_schildichat_themes_enabled: true From 22ea3b00d67d298aa6723b6372690c886b40b3f8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:19:02 +0900 Subject: [PATCH 369/952] Update docs for Element Web and SchildiChat Web: add the instruction to change the default country code to help to make the clients less British Note the order of the instructions is intended to align with that of configurations on main.yml files. Also: replace the explanations with the one available at https://github.com/element-hq/element-web/blob/develop/docs/config.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-element-web.md | 10 +++++++++- docs/configuring-playbook-client-schildichat-web.md | 10 +++++++++- roles/custom/matrix-client-element/defaults/main.yml | 2 +- .../custom/matrix-client-schildichat/defaults/main.yml | 2 +- 4 files changed, 20 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 0656c93fa..21ab26591 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -17,11 +17,19 @@ When setting, replace `example.com` with your own. ## Adjusting the playbook configuration +### Set the country code for phone number inputs + +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: + +```yaml +matrix_client_element_default_country_code: "FR" +``` + ### Themes #### Change the default theme -You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file: ```yaml # Controls the default theme diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 147d8056e..9c2f1eba4 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -22,11 +22,19 @@ To enable SchildiChat Web, add the following configuration to your `inventory/ho matrix_client_schildichat_enabled: true ``` +### Set the country code for phone number inputs + +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: + +```yaml +matrix_client_schildichat_default_country_code: "FR" +``` + ### Themes #### Change the default theme -You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +You can change the default theme from `light` to `dark`. To do so, add the following configuration to your `vars.yml` file: ```yaml # Controls the default theme diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 863c14910..c970b3f38 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -194,7 +194,7 @@ matrix_client_element_self_check_validate_certificates: true # don't show the registration button on welcome page matrix_client_element_registration_enabled: false -# Default country code on welcome page when login by phone number +# An optional ISO 3166 alpha2 country code (eg: GB, the default) to use when showing phone number inputs matrix_client_element_default_country_code: "GB" # Controls whether presence will be enabled diff --git a/roles/custom/matrix-client-schildichat/defaults/main.yml b/roles/custom/matrix-client-schildichat/defaults/main.yml index 68f0e86b9..8d170e4e3 100644 --- a/roles/custom/matrix-client-schildichat/defaults/main.yml +++ b/roles/custom/matrix-client-schildichat/defaults/main.yml @@ -189,7 +189,7 @@ matrix_client_schildichat_self_check_validate_certificates: true # don't show the registration button on welcome page matrix_client_schildichat_registration_enabled: false -# Default country code on welcome page when login by phone number +# An optional ISO 3166 alpha2 country code (eg: GB, the default) to use when showing phone number inputs matrix_client_schildichat_default_country_code: "GB" # Controls whether presence will be enabled From 45a09bc37d276905b85c1881832597b561cadf46 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:27:53 +0900 Subject: [PATCH 370/952] Update docs/configuring-playbook-client-schildichat-web.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-schildichat-web.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index 9c2f1eba4..ec34b2be7 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -126,3 +126,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 21b003ef270daf6ce136f5d16641ca744bcfb6f1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:28:59 +0900 Subject: [PATCH 371/952] Update docs/configuring-playbook-client-element-web.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-element-web.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 21ab26591..071be15ee 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -129,3 +129,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 0515787de28cf89bb87d4def7187198f4256b5ca Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 31 Jan 2025 14:33:34 +0200 Subject: [PATCH 372/952] Upgrade Traefik (v3.3.2-0 -> v3.3.2-1) and remove `traefik_config_certificatesResolvers_acme_email` references Ref: - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4014 - https://github.com/mother-of-all-self-hosting/ansible-role-traefik/commit/21b36ce336c6ab391f30632df3d7d970b8ad94c0 Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4014 --- CHANGELOG.md | 2 -- docs/configuring-playbook-own-webserver.md | 2 -- docs/howto-srv-server-delegation.md | 3 --- examples/vars.yml | 10 ---------- requirements.yml | 2 +- roles/custom/matrix-base/defaults/main.yml | 1 - 6 files changed, 1 insertion(+), 19 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index aeb956290..2f659a85a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1246,8 +1246,6 @@ Unless we have some regression, **existing `matrix-nginx-proxy` users should be ```yaml matrix_playbook_reverse_proxy_type: playbook-managed-traefik - -traefik_config_certificatesResolvers_acme_email: YOUR_EMAIL_ADDRESS ``` You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed. diff --git a/docs/configuring-playbook-own-webserver.md b/docs/configuring-playbook-own-webserver.md index 214640725..e49c454ae 100644 --- a/docs/configuring-playbook-own-webserver.md +++ b/docs/configuring-playbook-own-webserver.md @@ -18,8 +18,6 @@ To have the playbook install and use Traefik, add the following configuration to ```yaml matrix_playbook_reverse_proxy_type: playbook-managed-traefik - -traefik_config_certificatesResolvers_acme_email: YOUR_EMAIL_ADDRESS ``` Traefik will manage SSL certificates for all services seamlessly. diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index 3d83dd86a..4512dfca8 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -64,7 +64,6 @@ traefik_configuration_extension_yaml: | acme: # To use a staging endpoint for testing purposes, uncomment the line below. # caServer: https://acme-staging-v02.api.letsencrypt.org/directory - email: {{ traefik_config_certificatesResolvers_acme_email | to_json }} dnsChallenge: provider: cloudflare resolvers: @@ -124,7 +123,6 @@ matrix_coturn_container_additional_volumes: | ```yaml # Choosing the reverse proxy implementation matrix_playbook_reverse_proxy_type: playbook-managed-traefik -traefik_config_certificatesResolvers_acme_email: redacted@example.com # To serve the federation from any domain, as long as the path matches matrix_synapse_container_labels_public_federation_api_traefik_rule: PathPrefix(`/_matrix/federation`) @@ -141,7 +139,6 @@ traefik_configuration_extension_yaml: | acme: # To use a staging endpoint for testing purposes, uncomment the line below. # caServer: https://acme-staging-v02.api.letsencrypt.org/directory - email: {{ traefik_config_certificatesResolvers_acme_email | to_json }} dnsChallenge: provider: cloudflare resolvers: diff --git a/examples/vars.yml b/examples/vars.yml index d4d8066f8..cc6aa8333 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -28,16 +28,6 @@ matrix_homeserver_generic_secret_key: '' # For alternatives, see `docs/configuring-playbook-own-webserver.md`. matrix_playbook_reverse_proxy_type: playbook-managed-traefik -# This is something which is provided to Let's Encrypt when retrieving SSL certificates for domains. -# -# In case SSL renewal fails at some point, you'll also get an email notification there. -# -# If you decide to use another method for managing SSL certificates (different than the default Let's Encrypt), -# you won't be required to define this variable (see `docs/configuring-playbook-ssl-certificates.md`). -# -# Example value: someone@example.com -traefik_config_certificatesResolvers_acme_email: '' - # A Postgres password to use for the superuser Postgres user (called `matrix` by default). # # The playbook creates additional Postgres users and databases (one for each enabled service) diff --git a/requirements.yml b/requirements.yml index 3e1de26f2..8943945b4 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.2-0 + version: v3.3.2-1 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index e70328a40..8dabc239d 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -217,7 +217,6 @@ matrix_metrics_exposure_http_basic_auth_users: '' # - `playbook-managed-traefik` # - the playbook will run a managed Traefik instance (matrix-traefik) # - Traefik will do SSL termination, unless you disable it (e.g. `traefik_config_entrypoint_web_secure_enabled: false`) -# - if SSL termination is enabled (as it is by default), you need to populate: `traefik_config_certificatesResolvers_acme_email` # # - `other-traefik-container` # - this playbook will not install Traefik From 0318ee1f3867e1412ce067a9b08db95ceb5a5b4c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 31 Jan 2025 17:04:41 +0200 Subject: [PATCH 373/952] Remove `ensure-matrix-users-created` Ansible tag recommendation from WeChat bot docs This tag does nothing for the WeChat bot user. It appears like the matrix-wechat appservice is supposed to register it. --- docs/configuring-playbook-bridge-wechat.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index aa4ce17e5..60986016c 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -27,13 +27,11 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` **Notes**: -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. From f8ad4384fac19c5a9ff3fb1b4a2d87e32b0fd4c8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 08:48:59 -0500 Subject: [PATCH 374/952] Update docs/configuring-playbook-prometheus-nginxlog.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-nginxlog.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 224061c07..af8cf3306 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -20,6 +20,14 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_prometheus_nginxlog_exporter_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 421f13f6c531572549bf35eed82ec8875605e9b9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 13:40:56 +0900 Subject: [PATCH 375/952] Update docs/configuring-playbook-prometheus-nginxlog.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-nginxlog.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index af8cf3306..74e10be30 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -65,3 +65,7 @@ You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default. For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-prometheus-nginxlog-exporter`. From ac926fb6b78522ad3a3306a4fced9bb9bbaf0d94 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 13:48:47 +0900 Subject: [PATCH 376/952] Update docs/configuring-playbook-prometheus-nginxlog.md: adopt the common format for the introduction Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-nginxlog.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 74e10be30..4b68ad3bc 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -1,13 +1,15 @@ # Enabling metrics and graphs for NginX logs (optional) -It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs. - -This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment. +The playbook can install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you, in order to make it possible to have some (visual) insight into [nginx](https://nginx.org/) logs. It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint. +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. + **Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant. +## Prerequisite + To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary — see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server). If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created. From 57bc9f46cc3d01341fe6b97d4721e7b33bbdb733 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 13:50:40 +0900 Subject: [PATCH 377/952] Update docs/configuring-playbook-prometheus-nginxlog.md: move sections related to configuration to the dedicated one Signed-off-by: Suguru Hirahara --- ...onfiguring-playbook-prometheus-nginxlog.md | 50 +++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 4b68ad3bc..9218a0553 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -22,6 +22,31 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_prometheus_nginxlog_exporter_enabled: true ``` +### Docker Image Compatibility (optional) + +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: + +```yaml +matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false +matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag +``` + +## Security and privacy + +Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. + +### Save metrics on an external Prometheus server (optional) + +The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. + +When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). + +You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services. + +Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default. + +For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). + ### Extending the configuration There are some additional things you may wish to configure about the component. @@ -43,31 +68,6 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. -## Docker Image Compatibility - -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: - -```yaml -matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false -matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag -``` - -## Security and privacy - -Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. - -## Save metrics on an external Prometheus server - -The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. - -When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). - -You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services. - -Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default. - -For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). - ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-prometheus-nginxlog-exporter`. From a6364cc6a9f320838aeedb8f0488a905dc82e9f6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 14:05:12 +0900 Subject: [PATCH 378/952] Update docs/configuring-playbook-prometheus-nginxlog.md: change the section "Security and privacy" into the warning blockquote Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-nginxlog.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 9218a0553..eb46f1b54 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -31,12 +31,11 @@ matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag ``` -## Security and privacy - -Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. - ### Save metrics on an external Prometheus server (optional) +> [!WARNING] +> Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. + The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). From 5543e1523c5fb7db3cf9e798ea3e374c4c7b783d Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 31 Jan 2025 17:53:38 +0200 Subject: [PATCH 379/952] Add warning about WeChat bridge not working anymore --- docs/configuring-playbook-bridge-wechat.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index 60986016c..b42388bb7 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -4,6 +4,9 @@ The playbook can install and configure [matrix-wechat](https://github.com/duo/ma 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. +> [!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. + ## Adjusting the playbook configuration To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: From 7f90dda4fcec32bf2a0e798e60684b2a187e6eea Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 14:12:19 +0900 Subject: [PATCH 380/952] Update docs/configuring-playbook-prometheus-nginxlog.md: move down the section "Docker Image Compatibility" The section seems to be less relevant than the one for saving metrics on a Prometheus server. Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-nginxlog.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index eb46f1b54..5d04d905b 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -22,15 +22,6 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_prometheus_nginxlog_exporter_enabled: true ``` -### Docker Image Compatibility (optional) - -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: - -```yaml -matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false -matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag -``` - ### Save metrics on an external Prometheus server (optional) > [!WARNING] @@ -46,6 +37,15 @@ Whichever way you go with, this service will expose its metrics endpoint **witho For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). +### Docker Image Compatibility (optional) + +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: + +```yaml +matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false +matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag +``` + ### Extending the configuration There are some additional things you may wish to configure about the component. From 90bb956a2e129057474305a84e2525c557691f37 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 26 Dec 2024 22:22:17 -0500 Subject: [PATCH 381/952] Update configuring-playbook-bridge-appservice-discord.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-discord.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 5368db974..d7ce54893 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -28,6 +28,15 @@ matrix_appservice_discord_bot_token: "YOUR DISCORD APP BOT TOKEN" # use_appservice_legacy_authorization: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + +Take a look at: + +- `roles/custom/matrix-bridge-appservice-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `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 + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 97a7540e5d0588d95af9d383fa2fd34ecc239a00 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 28 Jan 2025 02:52:16 +0900 Subject: [PATCH 382/952] Update docs/configuring-playbook-bridge-appservice-discord.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- ...figuring-playbook-bridge-appservice-discord.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index d7ce54893..a8ad36fc7 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -108,3 +108,18 @@ There's the Discord bridge's guide for [setting privileges on bridge managed roo docker exec -it matrix-appservice-discord \ /bin/sh -c 'cp /cfg/registration.yaml /tmp/discord-registration.yaml && cd /tmp && node /build/tools/adminme.js -c /cfg/config.yaml -m "!qporfwt:example.com" -u "@alice:example.com" -p 100' ``` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-appservice-discord`. + +### Increase logging verbosity + +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: + +```yaml +matrix_appservice_discord_configuration_extension_yaml: | + logging: + # What level should the logger output to the console at. + console: "info" #silly, verbose, info, http, warn, error, silent +``` From 811abc09a83980fb46a13046d48fa7375c5be4ee Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 28 Jan 2025 02:54:51 +0900 Subject: [PATCH 383/952] Update files for matrix-appservice-discord: sort the logging levels Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-discord.md | 2 +- .../matrix-bridge-appservice-discord/templates/config.yaml.j2 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index a8ad36fc7..6ea6b88db 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -121,5 +121,5 @@ The default logging level for this component is `warn`. If you want to increase matrix_appservice_discord_configuration_extension_yaml: | logging: # What level should the logger output to the console at. - console: "info" #silly, verbose, info, http, warn, error, silent + console: "info" # Valid values: silent, error, warn, http, info, verbose, silly ``` diff --git a/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2 index 64f2923cc..a304a4f24 100644 --- a/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2 @@ -48,7 +48,7 @@ auth: usePrivilegedIntents: {{ matrix_appservice_discord_auth_usePrivilegedIntents|to_json }} logging: # What level should the logger output to the console at. - console: "warn" #silly, verbose, info, http, warn, error, silent + console: "warn" # Valid values: silent, error, warn, http, info, verbose, silly lineDateFormat: "MMM-D HH:mm:ss.SSS" # This is in moment.js format # files: # - file: "debug.log" From 18983f66031b11896820eceb8c41aaade08d42fc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 14:29:43 +0900 Subject: [PATCH 384/952] Update docs/configuring-playbook-conduit.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-conduit.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 760307b22..be5b46f6a 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -75,3 +75,7 @@ Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/ma sender_localpart: _bot_signalbot url: http://matrix-mautrix-signal:29328 ``` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-conduit`. From 85b766124975dba1470226466ee41444485d300e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 14:41:39 +0900 Subject: [PATCH 385/952] Update docs/configuring-playbook-dendrite.md: add the common section "Troubleshooting" See: https://matrix-org.github.io/dendrite/administration/troubleshooting#1-logs Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dendrite.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 83510e7af..7496e918d 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -62,3 +62,18 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. + +### Increase logging verbosity + +The default logging level for this component is `warning`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_dendrite_configuration_extension_yaml: | + logging: + - type: std + level: debug +``` From bd7f35d38392efb1f998d02ac69311a83b778dce Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 29 Dec 2024 10:03:09 -0500 Subject: [PATCH 386/952] Update docs/configuring-playbook-client-cinny.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-cinny.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 4e9decb4f..9e1aabc30 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -40,6 +40,15 @@ After changing the domain, **you may need to adjust your DNS** records to point **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. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-client-cinny/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-client-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 `matrix_client_cinny_configuration_extension_json` variable + ## Installing After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 69c64073726974320a3887cfb9c4ada4bd05f01e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 18:48:48 +0900 Subject: [PATCH 387/952] Update docs/configuring-playbook-client-cinny.md: adopt the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-cinny.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 9e1aabc30..2ba895eb9 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -61,3 +61,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 533ab41f7975015a411f287527372b06acffba76 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 29 Dec 2024 10:20:24 -0500 Subject: [PATCH 388/952] Update docs/configuring-playbook-client-hydrogen.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-hydrogen.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index db44e6a62..c99856873 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -37,6 +37,15 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +### Extending the configuration + +There are some additional things you may wish to configure about the client. + +Take a look at: + +- `roles/custom/matrix-client-hydrogen/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-client-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 `matrix_client_hydrogen_configuration_extension_json` variable + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From f38c69b30bb76efb62fa74e66c7bf34700dda52e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:31:44 +0900 Subject: [PATCH 389/952] Update docs/configuring-playbook-client-hydrogen.md: adopt the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-hydrogen.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index c99856873..cf9b30335 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -58,3 +58,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 74b95b57f1d8b78b54f29ff1ad150bd9aef2674a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 07:51:02 -0500 Subject: [PATCH 390/952] Update docs/configuring-playbook-matrix-media-repo.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 748d3aaf0..0a8302db3 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -88,7 +88,13 @@ matrix_media_repo_datastore_s3_opts_bucket_name: "your-media-bucket" ``` -Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml) +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-media-repo/defaults/main.yml` for some variables that you can customize via your `vars.yml` file ## Signing Keys From 66bb56db1821ac16b7891869eda7e297189eda49 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 03:41:12 +0900 Subject: [PATCH 391/952] Update docs/configuring-playbook-matrix-media-repo.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 0a8302db3..da4250b0d 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -167,3 +167,15 @@ docker exec -it matrix-media-repo \ Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing. This should output a `msg="Import completed"` when finished successfully! + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-media-repo`. + +### Increase logging verbosity + +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: + +```yaml +matrix_media_repo_sentry_debug: true +``` From cc3fa496efe5df14ff697d08746be1d350d974f7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 01:06:59 +0900 Subject: [PATCH 392/952] Update docs/configuring-playbook-matrix-media-repo.md: adopt the common format - Adopt the common introduction - Remove the ToC - Merge sections for additional configuration options and extending the configuration Signed-off-by: Suguru Hirahara --- .../configuring-playbook-matrix-media-repo.md | 38 ++++++++----------- 1 file changed, 16 insertions(+), 22 deletions(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index da4250b0d..b832e4b85 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -1,20 +1,18 @@ # Storing Matrix media files using matrix-media-repo (optional) -[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated "MMR") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification. +The playbook can install and configure [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated "MMR") for you. -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. +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. -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. +**Notes**: -| **Table of Contents** | -| :------------------------------------------------------------------------------------------ | -| [Quickstart](#quickstart) | -| [Additional configuration options](#configuring-the-media-repo) | -| [Importing data from an existing media store](#importing-data-from-an-existing-media-store) | +- 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. -## Quickstart +- 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. -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: +## Adjusting the playbook configuration + +To enable matrix-media-repo, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_media_repo_enabled: true @@ -27,12 +25,17 @@ The repo is pre-configured for integrating with the Postgres database, Traefik p 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. -## Configuring the media-repo +### Extending the configuration -Additional common configuration options: +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-media-repo/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + +Here is a list of additional common configuration options: ```yaml - # The postgres database pooling options # The maximum number of connects to hold open. More of these allow for more concurrent @@ -85,17 +88,8 @@ matrix_media_repo_datastore_s3_opts_bucket_name: "your-media-bucket" # An optional storage class for tuning how the media is stored at s3. # See https://aws.amazon.com/s3/storage-classes/ for details; uncomment to use. # matrix_media_repo_datastore_s3_opts_storage_class: "STANDARD" - ``` -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- `roles/custom/matrix-media-repo/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - ## Signing Keys 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. From 1242281fa2fca16a2544db2061bec2a840dbbf86 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 09:30:04 -0500 Subject: [PATCH 393/952] Update docs/configuring-playbook-synapse-usage-exporter.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-usage-exporter.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index e07fc6d0d..59f2b42d1 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -48,6 +48,14 @@ If you've changed the default hostname, you may need to create a CNAME record fo When setting, replace `example.com` with your own. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-synapse-usage-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From a67fea982c488d12503255dc7fbd47258f221ab3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 18:19:51 +0900 Subject: [PATCH 394/952] Update docs/configuring-playbook-synapse-usage-exporter.md: adopt the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-usage-exporter.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 59f2b42d1..ca1881667 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -68,3 +68,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 17761aaa876dbb3cd1b7c384df5823d22c957ce6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 16:35:47 +0900 Subject: [PATCH 395/952] Update docs/configuring-playbook-synapse-usage-exporter.md: adopt the common description for the introduction Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-usage-exporter.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index ca1881667..3eb98921f 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -1,6 +1,8 @@ # Enabling synapse-usage-exporter for Synapse usage statistics (optional) -[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus. +The playbook can install and configure [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) for you. + +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. 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. @@ -11,6 +13,8 @@ Enabling this service will automatically: - re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter - add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics +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. + ## Adjusting DNS records (optional) By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. From 39066954b3d53254fc647023ba57c958c3747896 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 09:23:34 -0500 Subject: [PATCH 396/952] Update docs/configuring-playbook-synapse-admin.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-admin.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index b5e8991bd..0ce5e9d6f 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -46,6 +46,14 @@ If you've changed the default hostname, you may need to create a CNAME record fo When setting, replace `example.com` with your own. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-synapse-admin/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_admin_configuration_extension_json` variable + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 57172d85e48c12ea2ae52ba8e0a39887ace2d820 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:51:58 +0900 Subject: [PATCH 397/952] Update docs/configuring-playbook-synapse-admin.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-admin.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index 0ce5e9d6f..bd07a8bb9 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -72,3 +72,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/` To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-admin`. From 42694883e6cdb855f6ddbea4a972845b7c04e821 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 00:18:15 +0900 Subject: [PATCH 398/952] Update files for Mjolnir: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-mjolnir.md | 14 ++++++++++++++ .../templates/production.yaml.j2 | 5 ++--- 2 files changed, 16 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index 2f068e7fa..ec56f345f 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -194,3 +194,17 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-mjolnir`. + +### Increase logging verbosity + +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: + +```yaml +# Valid values: ERROR, WARN, INFO, DEBUG +matrix_bot_mjolnir_configuration_extension_yaml: | + logLevel: "DEBUG" +``` diff --git a/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 b/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 index 35aac3af4..ec2b0ea28 100644 --- a/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 +++ b/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 @@ -57,10 +57,9 @@ managementRoom: {{ matrix_bot_mjolnir_management_room | to_json }} # mainly involves "all-OK" messages, and debugging messages for when mjolnir checks bans in a room. verboseLogging: false -# The log level of terminal (or container) output, -# can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity. +# The log level of terminal (or container) output. # -# This should be at INFO or DEBUG in order to get support for Mjolnir problems. +# Valid values: ERROR, WARN, INFO, DEBUG logLevel: "INFO" # Whether or not Mjolnir should synchronize policy lists immediately after startup. From 6bd94d860f06e1120d7a9b134ded180b21c5edd9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 01:29:07 +0900 Subject: [PATCH 399/952] Update docs/configuring-playbook-jitsi.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index b9aca9819..9e976b691 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -175,6 +175,17 @@ These configurations: - **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved - **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md). +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/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 these variables: + - `jitsi_web_custom_interface_config_extension`: custom configuration to be appended to `interface_config.js`, passed to Jitsi Web + - `jitsi_web_custom_config_extension`: custom configuration to be injected into `custom-config.js`, passed to Jitsi Web + - `jitsi_jvb_custom_config_extension`: custom configuration to be injected into `custom-sip-communicator.properties`, passed to Jitsi JVB + ### Example configurations Here is an example set of configurations for running a Jitsi instance with: From 25298cb6966c9f7812eb2a0f07dbbffb57d041c1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:41:48 +0900 Subject: [PATCH 400/952] Update docs/configuring-playbook-sygnal.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sygnal.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 7ce58714e..9db6ee290 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -100,3 +100,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju 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`). Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-sygnal`. From 8889b018f3b88e8e59ee65de9e0712573d0a110e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 1 Feb 2025 07:56:06 +0200 Subject: [PATCH 401/952] Adjust baibot's openai-config.yml.j2 to avoid `max_response_tokens` if unspecified Reasoning models like `o1` and `o3` and their `-mini` variants report errors if we try to configure `max_response_tokens` (which ultimately influences the `max_tokens` field in the API request): > invalid_request_error: Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead. (param: max_tokens) (code: unsupported_parameter) `max_completion_tokens` is not yet supported by baibot, so the best we can do is at least get rid of `max_response_tokens` (`max_tokens`). Ref: https://github.com/etkecc/baibot/commit/db9422740ceca32956d9628b6326b8be206344e2 --- .../matrix-bot-baibot/templates/provider/openai-config.yml.j2 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 index 56cf47fdd..c239e6d4a 100644 --- a/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 +++ b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 @@ -8,7 +8,9 @@ text_generation: model_id: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_model_id | to_json }} prompt: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_prompt | to_json }} temperature: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_temperature | to_json }} + {% if matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_response_tokens %} max_response_tokens: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_response_tokens | int | to_json }} + {% endif %} max_context_tokens: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_context_tokens | int | to_json }} {% endif %} From 4853de26de0cc57371919783cfc7ff3bccd91d86 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 1 Feb 2025 08:15:36 +0200 Subject: [PATCH 402/952] Upgrade Traefik (v3.3.2-1 -> v3.3.3-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 8943945b4..dd8644f0a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.2-1 + version: v3.3.3-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 From a1430f4d3f713af3eab9c295a260677a1fea631e Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sat, 1 Feb 2025 22:06:58 +0000 Subject: [PATCH 403/952] Update dependency babel to v2.17.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index d7693e0b8..cf48bd5a0 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -1,5 +1,5 @@ alabaster==1.0.0 -babel==2.16.0 +babel==2.17.0 certifi==2025.1.31 charset-normalizer==3.4.1 click==8.1.8 From 1034c06fc7caa53915ab8ef6dbf06f8ad8f6bc2b Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 2 Feb 2025 16:54:40 +0000 Subject: [PATCH 404/952] Update gnuxie/draupnir Docker tag to v2.1.0 --- .../custom/matrix-appservice-draupnir-for-all/defaults/main.yml | 2 +- roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index 8d028a98b..140b92d4a 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -5,7 +5,7 @@ matrix_appservice_draupnir_for_all_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_appservice_draupnir_for_all_version: "v2.0.2" +matrix_appservice_draupnir_for_all_version: "v2.1.0" matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 08f3fa4e7..57db9448d 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_draupnir_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_bot_draupnir_version: "v2.0.2" +matrix_bot_draupnir_version: "v2.1.0" matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" From a321b069f9b72a4ae6761df812e5720e6807bf93 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 02:09:36 +0900 Subject: [PATCH 405/952] Update docs/configuring-playbook-traefik.md: add the common introduction Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index cab20454f..40a27c798 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -1,6 +1,6 @@ # Configuring the Traefik reverse-proxy (optional, advanced) -By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role. +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. This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file. From 30d46397e66c3d121007dfa6c026949b2c4e4ffb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 19:39:43 +0900 Subject: [PATCH 406/952] Update docs/configuring-playbook-traefik.md: adopt the common format to descriptions Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 40a27c798..4529f167e 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -16,7 +16,7 @@ traefik_config_log_level: DEBUG ## Disable access logs -This will disable access logging. +To disable access logging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml traefik_config_accessLog_enabled: false @@ -24,7 +24,7 @@ traefik_config_accessLog_enabled: false ## Enable Traefik Dashboard -This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`). +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: ```yaml traefik_dashboard_enabled: true @@ -140,7 +140,7 @@ With these changes, all TCP traffic will be reverse-proxied to the target system ## Traefik behind a `proxy_protocol` reverse-proxy -If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file: +If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file: ```yaml traefik_configuration_extension_yaml: | From f5c6b61561f719a3bcc98a334aaaa263fb642215 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 03:58:53 +0900 Subject: [PATCH 407/952] Update docs/just.md: fix the description Signed-off-by: Suguru Hirahara --- docs/just.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/just.md b/docs/just.md index 53743a03b..153a20f1e 100644 --- a/docs/just.md +++ b/docs/just.md @@ -35,4 +35,4 @@ For example, these two commands are different: The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`. -Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data. +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. From 452bc3273ffc2491996d177a0d78d99aa9fc941f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 25 Dec 2024 11:04:51 -0500 Subject: [PATCH 408/952] Update docs/configuring-playbook-traefik.md: add the common section "Extending the configuration" Refer: - docs/configuring-playbook-backup-borg.md - https://github.com/mother-of-all-self-hosting/ansible-role-traefik/blob/main/defaults/main.yml Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 24 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 4529f167e..5cdc0826a 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -37,14 +37,30 @@ traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE > [!WARNING] > Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. -## Additional configuration +## Extending the configuration -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. +There are some additional things you may wish to configure about the component. + +Take a look at: + +- [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 + +For example, to enable and secure the Dashboard, you can add the following configuration to your `vars.yml` file: + +**Note**: this is a contrived example as you can enable and secure the Dashboard using the dedicated variables. See above for details. ```yaml -# This is a contrived example. -# You can enable and secure the Dashboard using dedicated variables. See above. traefik_configuration_extension_yaml: | + # Your custom YAML configuration for Traefik goes here. + # This configuration extends the default starting configuration (`traefik_configuration_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `traefik_configuration_yaml`. + # + # Example configuration extension follows: + # api: dashboard: true ``` From c2cd5fdb48a7a6d38f2ecbfc317248be0483dc9c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 19:09:52 +0900 Subject: [PATCH 409/952] Update docs/configuring-playbook-traefik.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 5cdc0826a..6873b3f77 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -8,12 +8,6 @@ This Ansible role support various configuration options. Feel free to consult it See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page. -## Increase logging verbosity - -```yaml -traefik_config_log_level: DEBUG -``` - ## Disable access logs To disable access logging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -174,3 +168,15 @@ traefik_configuration_extension_yaml: | - "/32" - "/128" ``` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-traefik`. + +### Increase logging verbosity + +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: + +```yaml +traefik_config_log_level: DEBUG +``` From eb51913deaa8f889c552b31159e9d43641b5697c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 19:29:28 +0900 Subject: [PATCH 410/952] Update docs/configuring-playbook-traefik.md: add the common section "Adjusting the playbook configuration" - Move the section not related to adjusting the playbook configurations out of it Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 6873b3f77..876492ff5 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -2,13 +2,11 @@ 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. +## Adjusting the playbook configuration + This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file. -## Adjusting SSL certificate retrieval - -See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page. - -## Disable access logs +### Disable access logs To disable access logging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -16,7 +14,7 @@ To disable access logging, add the following configuration to your `inventory/ho traefik_config_accessLog_enabled: false ``` -## Enable Traefik Dashboard +### Enable Traefik Dashboard To enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`), add the following configuration to your `vars.yml` file: @@ -31,7 +29,7 @@ traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE > [!WARNING] > Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts. -## Extending the configuration +### Extending the configuration There are some additional things you may wish to configure about the component. @@ -59,13 +57,13 @@ traefik_configuration_extension_yaml: | dashboard: true ``` -## Reverse-proxying another service behind Traefik +### Reverse-proxying another service behind Traefik 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). 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. -## Reverse-proxying a remote HTTP/HTTPS service behind Traefik +### Reverse-proxying a remote HTTP/HTTPS service behind Traefik 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. @@ -120,7 +118,7 @@ aux_file_definitions: ``` Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP. -## Reverse-proxying another service behind Traefik without terminating SSL +### Reverse-proxying another service behind Traefik without terminating SSL 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: @@ -148,7 +146,7 @@ With these changes, all TCP traffic will be reverse-proxied to the target system > [!WARNING] > This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. -## Traefik behind a `proxy_protocol` reverse-proxy +### Traefik behind a `proxy_protocol` reverse-proxy If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file: @@ -169,6 +167,12 @@ traefik_configuration_extension_yaml: | - "/128" ``` +## Other configurations + +### Adjusting SSL certificate retrieval + +See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page. + ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-traefik`. From 0c60d0898ad780b1b149eaa5b783e382c9a4538d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Feb 2025 16:48:39 +0900 Subject: [PATCH 411/952] Update docs/configuring-playbook-traefik.md: change section levels of ones related to reverse-proxying Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 876492ff5..71bfc7f0a 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -63,7 +63,7 @@ The preferred way to reverse-proxy additional services behind Traefik would be t 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. -### Reverse-proxying a remote HTTP/HTTPS service behind Traefik +#### Reverse-proxying a remote HTTP/HTTPS service behind Traefik 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. @@ -118,7 +118,7 @@ aux_file_definitions: ``` Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP. -### Reverse-proxying another service behind Traefik without terminating SSL +#### Reverse-proxying another service behind Traefik without terminating SSL 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: @@ -146,7 +146,7 @@ With these changes, all TCP traffic will be reverse-proxied to the target system > [!WARNING] > This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. -### Traefik behind a `proxy_protocol` reverse-proxy +#### Traefik behind a `proxy_protocol` reverse-proxy If you run a reverse-proxy which speaks `proxy_protocol`, add the following configuration to your `vars.yml` file: From 7f1695b2b52aae18839f81b6fb3ab639cd1f71eb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Feb 2025 17:07:20 +0900 Subject: [PATCH 412/952] Update docs/configuring-playbook-traefik.md: add the common section "Installing" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 71bfc7f0a..489d2e8df 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -173,6 +173,19 @@ traefik_configuration_extension_yaml: | See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page. +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + ## Troubleshooting 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`. From 9cb3c99bf915ab878839c70af85dc19aa3088113 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 3 Feb 2025 10:40:27 +0200 Subject: [PATCH 413/952] Upgrade devture/ansible and note that it also includes agru now Ref https://github.com/devture/docker-ansible/issues/2 --- docs/ansible.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/ansible.md b/docs/ansible.md index 87b4d86e8..1962c83bb 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -31,7 +31,10 @@ If using the `pip` method, do note that the `ansible-playbook` binary may not be Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image). -This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook. +This ensures that: + +- you're using a very recent Ansible version, which is less likely to be incompatible with the playbook +- 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` 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). @@ -57,7 +60,7 @@ docker run -it --rm \ -w /work \ -v `pwd`:/work \ --entrypoint=/bin/sh \ -docker.io/devture/ansible:2.18.1-r0-0 +docker.io/devture/ansible:2.18.1-r0-2 ``` 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. @@ -76,7 +79,7 @@ docker run -it --rm \ -v `pwd`:/work \ -v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro \ --entrypoint=/bin/sh \ -docker.io/devture/ansible:2.18.1-r0-0 +docker.io/devture/ansible:2.18.1-r0-2 ``` 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. From 8fb2719a68ce9260694a8bb97fc9d8683ec55bd0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 02:31:54 +0900 Subject: [PATCH 414/952] Update docs for Synapse: move descriptions from docs/maintenance-and-troubleshooting.md and create the common section "Troubleshooting" I am not sure what would be the motive to put the instruction for debugging Synapse on maintenance-and-troubleshooting.md above all, but now that we have the common section for an instruction about troubleshooting, it should make sense to move the instruction to the documentation page for configuring Synapse. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse.md | 15 +++++++++++++++ docs/maintenance-and-troubleshooting.md | 16 ---------------- 2 files changed, 15 insertions(+), 16 deletions(-) diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 12ae0f061..590434117 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -173,3 +173,18 @@ This playbook allows you to enable Synapse metrics, which can provide insight in To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`. + +### Increase logging verbosity + +Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`. + +If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_synapse_log_level: "INFO" +matrix_synapse_storage_sql_log_level: "INFO" +matrix_synapse_root_log_level: "INFO" diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 41704dfe4..fa38df727 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -22,22 +22,6 @@ To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/j sudo journalctl -fu matrix-synapse ``` -## Increase logging verbosity - -Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`. - -If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increasing the logging level to `INFO`. - -Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`): - -```yaml -matrix_synapse_log_level: "INFO" -matrix_synapse_storage_sql_log_level: "INFO" -matrix_synapse_root_log_level: "INFO" -``` - -Re-run the playbook after making these configuration changes. - ## How to check if services work The playbook can perform a check to ensure that you've configured things correctly and that services are running. From b67e5729dacdcdf458815d6849981f1d48b35084 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 02:34:41 +0900 Subject: [PATCH 415/952] Update docs/configuring-playbook-synapse: remove the duplicated anchor link Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 590434117..f31ca5d81 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -180,7 +180,7 @@ As with all other services, you can find the logs in [systemd-journald](https:// ### Increase logging verbosity -Because the [Synapse](https://github.com/element-hq/synapse) Matrix server is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`. +Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`. If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook: From da0952e05862d8a0cb8aba7076fb8ca4ddbfa3b3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 01:12:38 +0900 Subject: [PATCH 416/952] Update docs for Synapse: add anchor links to each other Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse.md | 2 ++ docs/maintenance-synapse.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index f31ca5d81..04e33c36b 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -2,6 +2,8 @@ By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document. +💡 See this page for details about maintaining Synapse: [Synapse maintenance](maintenance-synapse.md) + ## Adjusting the playbook configuration ### Load balancing with workers diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index bc78f28fd..cd8f11697 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -12,6 +12,8 @@ Table of contents: - [Make Synapse faster](#make-synapse-faster) +💡 See this page for details about configuring Synapse: [Configuring Synapse](configuring-playbook-synapse.md) + ## Purging old data with the Purge History API 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**. From 4c9ea2ef304d9d0c8dfaa24b631edb7f10f2678f Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 3 Feb 2025 11:00:19 +0200 Subject: [PATCH 417/952] Upgrade exim-relay (v4.98-r0-3-0 -> v4.98-r0-4-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index dd8644f0a..298406d3d 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.6-0 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98-r0-3-0 + version: v4.98-r0-4-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.4.0-0 From d5d64f7ca3d75076e9236343ca214f3bd3c31713 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 3 Feb 2025 11:46:43 +0200 Subject: [PATCH 418/952] Upgrade matrix-corporal (3.1.2 -> 3.1.3) --- roles/custom/matrix-corporal/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml index c6829a689..6013e3a28 100644 --- a/roles/custom/matrix-corporal/defaults/main.yml +++ b/roles/custom/matrix-corporal/defaults/main.yml @@ -5,7 +5,7 @@ matrix_corporal_enabled: true # renovate: datasource=docker depName=devture/matrix-corporal -matrix_corporal_version: 3.1.2 +matrix_corporal_version: 3.1.3 matrix_corporal_container_image_self_build: false matrix_corporal_container_image_self_build_repo: "https://github.com/devture/matrix-corporal.git" From bd42874ed721d5ca5658fe4eaa4c9b16e71b99e7 Mon Sep 17 00:00:00 2001 From: adam-kress Date: Mon, 3 Feb 2025 07:46:58 -0500 Subject: [PATCH 419/952] Upgrade Jitsi (v9955-0 -> v10008-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 298406d3d..7c4a1db6e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.4.0-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v9955-0 + version: v10008-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git version: v2.11.0-0 From 98d5ede2c6c7bec177e92ebdf0eed59a6fb91338 Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 3 Feb 2025 16:42:34 +0200 Subject: [PATCH 420/952] grafana v11.5.1 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 7c4a1db6e..7d4f69401 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98-r0-4-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.4.0-0 + version: v11.5.1-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v10008-0 From c399992542aa4b7f19e7fea9c1d24d64b4a3cab5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 3 Feb 2025 17:08:12 +0200 Subject: [PATCH 421/952] Remove `matrix-bridge-mautrix-hangouts` role Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3863 --- CHANGELOG.md | 11 + ...guring-playbook-bridge-mautrix-hangouts.md | 59 +----- ...iguring-playbook-bridge-mx-puppet-skype.md | 2 +- docs/configuring-playbook.md | 2 - docs/container-images.md | 1 - docs/self-building.md | 1 - group_vars/matrix_servers | 84 -------- .../defaults/main.yml | 190 ------------------ .../tasks/main.yml | 20 -- .../tasks/setup_install.yml | 144 ------------- .../tasks/setup_uninstall.yml | 20 -- .../tasks/validate_config.yml | 31 --- .../templates/config.yaml.j2 | 149 -------------- .../templates/labels.j2 | 76 ------- .../matrix-mautrix-hangouts.service.j2 | 69 ------- .../tasks/validate_config.yml | 13 ++ setup.yml | 1 - 17 files changed, 34 insertions(+), 839 deletions(-) delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/defaults/main.yml delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/tasks/main.yml delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_install.yml delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_uninstall.yml delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/templates/config.yaml.j2 delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/templates/labels.j2 delete mode 100644 roles/custom/matrix-bridge-mautrix-hangouts/templates/systemd/matrix-mautrix-hangouts.service.j2 diff --git a/CHANGELOG.md b/CHANGELOG.md index 2f659a85a..bbbc609d9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,14 @@ +# 2025-02-03 + +## The mautrix-hangouts bridge has been removed from the playbook + +The [mautrix-hangouts](./docs/configuring-playbook-bridge-mautrix-hangouts.md) bridge has been deprecated in the playbook since December 2024 and finally got completely removed from the playbook in February 2025. + +This is because Google Hangouts has been discontinued since the 1st of November 2022. + +The playbook will let you know if you're using any `matrix_mautrix_hangouts_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-mautrix-hangouts.md#uninstalling-the-bridge-manually). + + # 2025-01-27 ## Redis and KeyDB are no longer part of the playbook diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index 307605be4..c12283d0c 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -1,58 +1,17 @@ # Setting up Mautrix Hangouts bridging (optional, deprecated) -Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) +🪦 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. -💡 **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. +You may wish to use the [Google Chat bridge](https://github.com/mautrix/googlechat) instead. -The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you. +## Uninstalling the bridge manually -## Prerequisite (optional) +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: -### Enable Shared Secret Auth - -If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook. - -See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. - -**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future. - -## Adjusting the playbook configuration - -To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -matrix_mautrix_hangouts_enabled: true -``` - -### Extending the configuration - -There are some additional things you may wish to configure about the bridge. - -See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +systemctl disable --now matrix-mautrix-hangouts.service + +rm -rf /matrix/mautrix-hangouts + +/matrix/postgres/bin/cli-non-interactive 'DROP DATABASE matrix_mautrix_hangouts;' ``` - -**Notes**: - -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - -- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - - `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. - -## Usage - -To use the bridge, you need to start a chat with `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). - -You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions. - -Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools. - -Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages. diff --git a/docs/configuring-playbook-bridge-mx-puppet-skype.md b/docs/configuring-playbook-bridge-mx-puppet-skype.md index bc9d6d534..6bbfb7aa5 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-skype.md +++ b/docs/configuring-playbook-bridge-mx-puppet-skype.md @@ -1,5 +1,5 @@ # Setting up MX Puppet Skype bridging (optional, removed) -The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time. +🪦 The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time. Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index ea371c99b..6a2942a24 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -250,8 +250,6 @@ Various services that don't fit any other categories. - [Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md)) -- [Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)) - - [Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md)) - [Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)) diff --git a/docs/container-images.md b/docs/container-images.md index 7fb671c16..23e2004f9 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -161,5 +161,4 @@ The list of the deprecated or unmaintained services is available [here](configur | [Go-NEB](configuring-playbook-bot-go-neb.md) | [matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb) | ❌ | Multi functional bot written in Go | | [matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md) | [matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot) | ❌ | Accessing ChatGPT via your favourite Matrix client | | [mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md) | [mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry) | ❌ | Bridge to [Facebook](https://facebook.com/) | -| [mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md) | [mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry) | ❌ | Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts) | | [mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md) | [mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry) | ❌ | Bridge to [Instagram](https://instagram.com/) | diff --git a/docs/self-building.md b/docs/self-building.md index 4304f4ded..543065d89 100644 --- a/docs/self-building.md +++ b/docs/self-building.md @@ -28,7 +28,6 @@ Possibly outdated list of roles where self-building the Docker image is currentl - `matrix-bridge-appservice-webhooks` - `matrix-bridge-beeper-linkedin` - `matrix-bridge-mautrix-facebook` -- `matrix-bridge-mautrix-hangouts` - `matrix-bridge-mautrix-googlechat` - `matrix-bridge-mautrix-telegram` - `matrix-bridge-mautrix-signal` diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index b08f02e6a..516fd6d83 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -115,8 +115,6 @@ matrix_homeserver_container_extra_arguments_auto: | + (['--mount type=bind,src=' + matrix_mautrix_googlechat_config_path + '/registration.yaml,dst=/matrix-mautrix-googlechat-registration.yaml,ro'] if matrix_mautrix_googlechat_enabled else []) + - (['--mount type=bind,src=' + matrix_mautrix_hangouts_config_path + '/registration.yaml,dst=/matrix-mautrix-hangouts-registration.yaml,ro'] if matrix_mautrix_hangouts_enabled else []) - + (['--mount type=bind,src=' + matrix_mautrix_instagram_config_path + '/registration.yaml,dst=/matrix-mautrix-instagram-registration.yaml,ro'] if matrix_mautrix_instagram_enabled else []) + (['--mount type=bind,src=' + matrix_mautrix_signal_config_path + '/registration.yaml,dst=/matrix-mautrix-signal-registration.yaml,ro'] if matrix_mautrix_signal_enabled else []) @@ -188,8 +186,6 @@ matrix_homeserver_app_service_config_files_auto: | + (['/matrix-mautrix-googlechat-registration.yaml'] if matrix_mautrix_googlechat_enabled else []) + - (['/matrix-mautrix-hangouts-registration.yaml'] if matrix_mautrix_hangouts_enabled else []) - + (['/matrix-mautrix-instagram-registration.yaml'] if matrix_mautrix_instagram_enabled else []) + (['/matrix-mautrix-signal-registration.yaml'] if matrix_mautrix_signal_enabled else []) @@ -332,8 +328,6 @@ devture_systemd_service_manager_services_list_auto: | + ([{'name': 'matrix-mautrix-googlechat.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-googlechat']}] if matrix_mautrix_googlechat_enabled else []) + - ([{'name': 'matrix-mautrix-hangouts.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-hangouts']}] if matrix_mautrix_hangouts_enabled else []) - + ([{'name': 'matrix-mautrix-instagram.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-instagram']}] if matrix_mautrix_instagram_enabled else []) + ([{'name': 'matrix-mautrix-signal.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-signal', 'mautrix-signal']}] if matrix_mautrix_signal_enabled else []) @@ -1362,73 +1356,6 @@ matrix_mautrix_googlechat_database_password: "{{ '%s' | format(matrix_homeserver ###################################################################### -###################################################################### -# -# matrix-bridge-mautrix-hangouts -# -###################################################################### - -# We don't enable bridges by default. -matrix_mautrix_hangouts_enabled: false - -matrix_mautrix_hangouts_systemd_required_services_list_auto: | - {{ - matrix_addons_homeserver_systemd_services_list - + - ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_hangouts_database_hostname == postgres_connection_hostname) else []) - }} - -matrix_mautrix_hangouts_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" - -matrix_mautrix_hangouts_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9007') if matrix_playbook_service_host_bind_interface_prefix else '' }}" - -matrix_mautrix_hangouts_container_network: "{{ matrix_addons_container_network }}" - -matrix_mautrix_hangouts_container_additional_networks_auto: |- - {{ - ( - ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) - + - ([postgres_container_network] if (postgres_enabled and matrix_mautrix_hangouts_database_hostname == postgres_connection_hostname and matrix_mautrix_hangouts_container_network != postgres_container_network) else []) - + - ([matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_playbook_reverse_proxyable_services_additional_network and matrix_mautrix_gmessages_container_labels_traefik_enabled) else []) - ) | unique - }} - -matrix_mautrix_hangouts_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" -matrix_mautrix_hangouts_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" -matrix_mautrix_hangouts_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" -matrix_mautrix_hangouts_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" - -matrix_mautrix_hangouts_container_labels_public_endpoint_hostname: "{{ matrix_server_fqn_matrix }}" - -matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_enabled: "{{ matrix_metrics_exposure_http_basic_auth_enabled }}" -matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_users: "{{ matrix_metrics_exposure_http_basic_auth_users }}" - -matrix_mautrix_hangouts_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'ho.as.token', rounds=655555) | to_uuid }}" - -matrix_mautrix_hangouts_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" -matrix_mautrix_hangouts_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'ho.hs.token', rounds=655555) | to_uuid }}" - -matrix_mautrix_hangouts_login_shared_secret: "{{ matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled else '' }}" - -matrix_mautrix_hangouts_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}" - -matrix_mautrix_hangouts_metrics_proxying_enabled: "{{ matrix_mautrix_hangouts_metrics_enabled and matrix_metrics_exposure_enabled }}" -matrix_mautrix_hangouts_metrics_proxying_hostname: "{{ matrix_metrics_exposure_hostname }}" -matrix_mautrix_hangouts_metrics_proxying_path_prefix: "{{ matrix_metrics_exposure_path_prefix }}/mautrix-hangouts" - -# Postgres is the default, except if not using internal Postgres server -matrix_mautrix_hangouts_database_engine: "{{ 'postgres' if postgres_enabled else 'sqlite' }}" -matrix_mautrix_hangouts_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}" -matrix_mautrix_hangouts_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.hangouts.db', rounds=655555) | to_uuid }}" - -###################################################################### -# -# /matrix-bridge-mautrix-hangouts -# -###################################################################### - ###################################################################### # @@ -4139,12 +4066,6 @@ postgres_managed_databases_auto: | 'password': matrix_mautrix_facebook_database_password, }] if (matrix_mautrix_facebook_enabled and matrix_mautrix_facebook_database_engine == 'postgres' and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname) else []) + - ([{ - 'name': matrix_mautrix_hangouts_database_name, - 'username': matrix_mautrix_hangouts_database_username, - 'password': matrix_mautrix_hangouts_database_password, - }] if (matrix_mautrix_hangouts_enabled and matrix_mautrix_hangouts_database_engine == 'postgres' and matrix_mautrix_hangouts_database_hostname == postgres_connection_hostname) else []) - + ([{ 'name': matrix_mautrix_googlechat_database_name, 'username': matrix_mautrix_googlechat_database_username, @@ -5009,11 +4930,6 @@ matrix_synapse_admin_config_asManagedUsers_auto: | '^@googlechat_[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$', ] if matrix_mautrix_googlechat_enabled else []) + - ([ - '^@'+(matrix_mautrix_hangouts_appservice_bot_username | default('') | regex_escape)+':'+(matrix_domain | regex_escape)+'$', - '^@hangouts_[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$', - ] if matrix_mautrix_hangouts_enabled else []) - + ([ '^@'+(matrix_mautrix_instagram_appservice_bot_username | default('') | regex_escape)+':'+(matrix_domain | regex_escape)+'$', '^@instagram_[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$', diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-hangouts/defaults/main.yml deleted file mode 100644 index 764854017..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/defaults/main.yml +++ /dev/null @@ -1,190 +0,0 @@ ---- -# mautrix-hangouts is a Matrix <-> Hangouts bridge -# Project source code URL: https://github.com/mautrix/hangouts - -matrix_mautrix_hangouts_enabled: true - -matrix_mautrix_hangouts_container_image_self_build: false -matrix_mautrix_hangouts_container_image_self_build_repo: "https://github.com/mautrix/hangouts.git" -matrix_mautrix_hangouts_container_image_self_build_repo_version: "{{ 'master' if matrix_mautrix_hangouts_version == 'latest' else matrix_mautrix_hangouts_version }}" - -# renovate: datasource=docker depName=dock.mau.dev/mautrix/hangouts -matrix_mautrix_hangouts_version: latest -# See: https://mau.dev/mautrix/hangouts/container_registry -matrix_mautrix_hangouts_docker_image: "{{ matrix_mautrix_hangouts_docker_image_name_prefix }}mautrix/hangouts:{{ matrix_mautrix_hangouts_version }}" -matrix_mautrix_hangouts_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_hangouts_container_image_self_build else 'dock.mau.dev/' }}" -matrix_mautrix_hangouts_docker_image_force_pull: "{{ matrix_mautrix_hangouts_docker_image.endswith(':latest') }}" - -matrix_mautrix_hangouts_base_path: "{{ matrix_base_data_path }}/mautrix-hangouts" -matrix_mautrix_hangouts_config_path: "{{ matrix_mautrix_hangouts_base_path }}/config" -matrix_mautrix_hangouts_data_path: "{{ matrix_mautrix_hangouts_base_path }}/data" -matrix_mautrix_hangouts_docker_src_files_path: "{{ matrix_mautrix_hangouts_base_path }}/docker-src" - -matrix_mautrix_hangouts_public_endpoint: '/mautrix-hangouts' - -matrix_mautrix_hangouts_homeserver_address: "" -matrix_mautrix_hangouts_homeserver_domain: '{{ matrix_domain }}' -matrix_mautrix_hangouts_appservice_address: 'http://matrix-mautrix-hangouts:8080' - -matrix_mautrix_hangouts_command_prefix: "!HO" - -matrix_mautrix_hangouts_bridge_permissions: | - {{ - {matrix_mautrix_hangouts_homeserver_domain: 'user'} - | combine({matrix_admin: 'admin'} if matrix_admin else {}) - }} - -# Controls whether the matrix-mautrix-hangouts container exposes its HTTP port (tcp/8080 in the container). -# -# Takes an ":" or "" value (e.g. "127.0.0.1:9007"), or empty string to not expose. -matrix_mautrix_hangouts_container_http_host_bind_port: '' - -matrix_mautrix_hangouts_container_network: "" - -matrix_mautrix_hangouts_container_additional_networks: "{{ matrix_mautrix_hangouts_container_additional_networks_auto + matrix_mautrix_hangouts_container_additional_networks_custom }}" -matrix_mautrix_hangouts_container_additional_networks_auto: [] -matrix_mautrix_hangouts_container_additional_networks_custom: [] - -# matrix_mautrix_hangouts_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. -# See `../templates/labels.j2` for details. -# -# To inject your own other container labels, see `matrix_mautrix_hangouts_container_labels_additional_labels`. -matrix_mautrix_hangouts_container_labels_traefik_enabled: true -matrix_mautrix_hangouts_container_labels_traefik_docker_network: "{{ matrix_mautrix_hangouts_container_network }}" -matrix_mautrix_hangouts_container_labels_traefik_entrypoints: web-secure -matrix_mautrix_hangouts_container_labels_traefik_tls_certResolver: default # noqa var-naming - -# Controls whether labels will be added that expose mautrix-googlechat's public endpoint -matrix_mautrix_hangouts_container_labels_public_endpoint_enabled: true -matrix_mautrix_hangouts_container_labels_public_endpoint_hostname: "" -matrix_mautrix_hangouts_container_labels_public_endpoint_path_prefix: "{{ matrix_mautrix_hangouts_public_endpoint }}" -matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_rule: "Host(`{{ matrix_mautrix_hangouts_container_labels_public_endpoint_hostname }}`) && PathPrefix(`{{ matrix_mautrix_hangouts_container_labels_public_endpoint_path_prefix }}`)" -matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_priority: 0 -matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_entrypoints: "{{ matrix_mautrix_hangouts_container_labels_traefik_entrypoints }}" -matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_tls: "{{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_entrypoints != 'web' }}" -matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_tls_certResolver: "{{ matrix_mautrix_hangouts_container_labels_traefik_tls_certResolver }}" # noqa var-naming - -# Controls whether labels will be added that expose mautrix-googlechat's metrics -matrix_mautrix_hangouts_container_labels_metrics_enabled: "{{ matrix_mautrix_hangouts_metrics_enabled and matrix_mautrix_hangouts_metrics_proxying_enabled }}" -matrix_mautrix_hangouts_container_labels_metrics_traefik_rule: "Host(`{{ matrix_mautrix_hangouts_metrics_proxying_hostname }}`) && PathPrefix(`{{ matrix_mautrix_hangouts_metrics_proxying_path_prefix }}`)" -matrix_mautrix_hangouts_container_labels_metrics_traefik_priority: 0 -matrix_mautrix_hangouts_container_labels_metrics_traefik_entrypoints: "{{ matrix_mautrix_hangouts_container_labels_traefik_entrypoints }}" -matrix_mautrix_hangouts_container_labels_metrics_traefik_tls: "{{ matrix_mautrix_hangouts_container_labels_metrics_traefik_entrypoints != 'web' }}" -matrix_mautrix_hangouts_container_labels_metrics_traefik_tls_certResolver: "{{ matrix_mautrix_hangouts_container_labels_traefik_tls_certResolver }}" # noqa var-naming -matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_enabled: false -# See: https://doc.traefik.io/traefik/middlewares/http/basicauth/#users -matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_users: '' - -# matrix_mautrix_hangouts_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. -# See `../templates/labels.j2` for details. -# -# Example: -# matrix_mautrix_hangouts_container_labels_additional_labels: | -# my.label=1 -# another.label="here" -matrix_mautrix_hangouts_container_labels_additional_labels: '' - -# A list of extra arguments to pass to the container -matrix_mautrix_hangouts_container_extra_arguments: [] - -# List of systemd services that matrix-mautrix-hangouts.service depends on. -matrix_mautrix_hangouts_systemd_required_services_list: "{{ matrix_mautrix_hangouts_systemd_required_services_list_default + matrix_mautrix_hangouts_systemd_required_services_list_auto + matrix_mautrix_hangouts_systemd_required_services_list_custom }}" -matrix_mautrix_hangouts_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" -matrix_mautrix_hangouts_systemd_required_services_list_auto: [] -matrix_mautrix_hangouts_systemd_required_services_list_custom: [] - -# List of systemd services that matrix-mautrix-hangouts.service wants -matrix_mautrix_hangouts_systemd_wanted_services_list: [] - -matrix_mautrix_hangouts_appservice_token: '' -matrix_mautrix_hangouts_homeserver_token: '' - -# Whether or not metrics endpoint should be enabled. -# Enabling them is usually enough for a local (in-container) Prometheus to consume them. -# If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_mautrix_hangouts_metrics_proxying_enabled`. -matrix_mautrix_hangouts_metrics_enabled: false - -# Controls whether metrics should be proxied (exposed) on a public URL. -matrix_mautrix_hangouts_metrics_proxying_enabled: false -matrix_mautrix_hangouts_metrics_proxying_hostname: '' -matrix_mautrix_hangouts_metrics_proxying_path_prefix: '' - -# Database-related configuration fields. -# -# To use SQLite, stick to these defaults. -# -# To use Postgres: -# - change the engine (`matrix_mautrix_hangouts_database_engine: 'postgres'`) -# - adjust your database credentials via the `matrix_mautrix_hangouts_database_*` variables -matrix_mautrix_hangouts_database_engine: 'sqlite' - -matrix_mautrix_hangouts_sqlite_database_path_local: "{{ matrix_mautrix_hangouts_data_path }}/mautrix-hangouts.db" -matrix_mautrix_hangouts_sqlite_database_path_in_container: "/data/mautrix-hangouts.db" - -matrix_mautrix_hangouts_database_username: 'matrix_mautrix_hangouts' -matrix_mautrix_hangouts_database_password: 'some-password' -matrix_mautrix_hangouts_database_hostname: '' -matrix_mautrix_hangouts_database_port: 5432 -matrix_mautrix_hangouts_database_name: 'matrix_mautrix_hangouts' - -matrix_mautrix_hangouts_database_connection_string: 'postgres://{{ matrix_mautrix_hangouts_database_username }}:{{ matrix_mautrix_hangouts_database_password }}@{{ matrix_mautrix_hangouts_database_hostname }}:{{ matrix_mautrix_hangouts_database_port }}/{{ matrix_mautrix_hangouts_database_name }}' - -matrix_mautrix_hangouts_appservice_database: "{{ - { - 'sqlite': ('sqlite:///' + matrix_mautrix_hangouts_sqlite_database_path_in_container), - 'postgres': matrix_mautrix_hangouts_database_connection_string, - }[matrix_mautrix_hangouts_database_engine] -}}" - - -# Can be set to enable automatic double-puppeting via Shared Secret Auth (https://github.com/devture/matrix-synapse-shared-secret-auth). -matrix_mautrix_hangouts_login_shared_secret: '' - -matrix_mautrix_hangouts_appservice_bot_username: hangoutsbot - -# Specifies the default log level for all bridge loggers. -matrix_mautrix_hangouts_logging_level: WARNING - -# Default configuration template which covers the generic use case. -# You can customize it by controlling the various variables inside it. -# -# For a more advanced customization, you can extend the default (see `matrix_mautrix_hangouts_configuration_extension_yaml`) -# or completely replace this variable with your own template. -matrix_mautrix_hangouts_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" - -matrix_mautrix_hangouts_configuration_extension_yaml: | - # Your custom YAML configuration goes here. - # This configuration extends the default starting configuration (`matrix_mautrix_hangouts_configuration_yaml`). - # - # You can override individual variables from the default configuration, or introduce new ones. - # - # If you need something more special, you can take full control by - # completely redefining `matrix_mautrix_hangouts_configuration_yaml`. - -matrix_mautrix_hangouts_configuration_extension: "{{ matrix_mautrix_hangouts_configuration_extension_yaml | from_yaml if matrix_mautrix_hangouts_configuration_extension_yaml | from_yaml is mapping else {} }}" - -# Holds the final configuration (a combination of the default and its extension). -# You most likely don't need to touch this variable. Instead, see `matrix_mautrix_hangouts_configuration_yaml`. -matrix_mautrix_hangouts_configuration: "{{ matrix_mautrix_hangouts_configuration_yaml | from_yaml | combine(matrix_mautrix_hangouts_configuration_extension, recursive=True) }}" - -matrix_mautrix_hangouts_registration_yaml: | - id: hangouts - as_token: "{{ matrix_mautrix_hangouts_appservice_token }}" - hs_token: "{{ matrix_mautrix_hangouts_homeserver_token }}" - namespaces: - users: - - exclusive: true - regex: '^@hangouts_.+:{{ matrix_mautrix_hangouts_homeserver_domain | regex_escape }}$' - - exclusive: true - regex: '^@{{ matrix_mautrix_hangouts_appservice_bot_username | regex_escape }}:{{ matrix_mautrix_hangouts_homeserver_domain | regex_escape }}$' - url: {{ matrix_mautrix_hangouts_appservice_address }} - # See https://github.com/mautrix/signal/issues/43 - sender_localpart: _bot_{{ matrix_mautrix_hangouts_appservice_bot_username }} - rate_limited: false - de.sorunome.msc2409.push_ephemeral: true - -matrix_mautrix_hangouts_registration: "{{ matrix_mautrix_hangouts_registration_yaml | from_yaml }}" - -# Enable End-to-bridge encryption -matrix_mautrix_hangouts_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}" -matrix_mautrix_hangouts_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}" diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/main.yml deleted file mode 100644 index 601c0b0ae..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/main.yml +++ /dev/null @@ -1,20 +0,0 @@ ---- - -- tags: - - setup-all - - setup-mautrix-hangouts - - install-all - - install-mautrix-hangouts - block: - - when: matrix_mautrix_hangouts_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" - - - when: matrix_mautrix_hangouts_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" - -- tags: - - setup-all - - setup-mautrix-hangouts - block: - - when: not matrix_mautrix_hangouts_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_install.yml deleted file mode 100644 index 49bdb5ab2..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_install.yml +++ /dev/null @@ -1,144 +0,0 @@ ---- - -- ansible.builtin.set_fact: - matrix_mautrix_hangouts_requires_restart: false - -- when: "matrix_mautrix_hangouts_database_engine == 'postgres'" - block: - - name: Check if an SQLite database already exists - ansible.builtin.stat: - path: "{{ matrix_mautrix_hangouts_sqlite_database_path_local }}" - register: matrix_mautrix_hangouts_sqlite_database_path_local_stat_result - - - when: "matrix_mautrix_hangouts_sqlite_database_path_local_stat_result.stat.exists | bool" - block: - - ansible.builtin.include_role: - name: galaxy/postgres - tasks_from: migrate_db_to_postgres - vars: - postgres_db_migration_request: - src: "{{ matrix_mautrix_hangouts_sqlite_database_path_local }}" - dst: "{{ matrix_mautrix_hangouts_database_connection_string }}" - caller: "{{ role_path | basename }}" - engine_variable_name: 'matrix_mautrix_hangouts_database_engine' - engine_old: 'sqlite' - systemd_services_to_stop: ['matrix-mautrix-hangouts.service'] - - - ansible.builtin.set_fact: - matrix_mautrix_hangouts_requires_restart: true - -- name: Ensure Mautrix Hangouts image is pulled - community.docker.docker_image: - name: "{{ matrix_mautrix_hangouts_docker_image }}" - source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" - force_source: "{{ matrix_mautrix_hangouts_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_mautrix_hangouts_docker_image_force_pull }}" - when: not matrix_mautrix_hangouts_container_image_self_build - register: result - retries: "{{ devture_playbook_help_container_retries_count }}" - delay: "{{ devture_playbook_help_container_retries_delay }}" - until: result is not failed - -- name: Ensure Mautrix Hangouts paths exist - ansible.builtin.file: - path: "{{ item.path }}" - state: directory - mode: 0750 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - with_items: - - {path: "{{ matrix_mautrix_hangouts_base_path }}", when: true} - - {path: "{{ matrix_mautrix_hangouts_config_path }}", when: true} - - {path: "{{ matrix_mautrix_hangouts_data_path }}", when: true} - - {path: "{{ matrix_mautrix_hangouts_docker_src_files_path }}", when: "{{ matrix_mautrix_hangouts_container_image_self_build }}"} - when: "item.when | bool" - -- name: Ensure Mautrix Hangots repository is present on self build - ansible.builtin.git: - repo: "{{ matrix_mautrix_hangouts_container_image_self_build_repo }}" - version: "{{ matrix_mautrix_hangouts_container_image_self_build_repo_version }}" - dest: "{{ matrix_mautrix_hangouts_docker_src_files_path }}" - force: "yes" - become: true - become_user: "{{ matrix_user_username }}" - register: matrix_mautrix_hangouts_git_pull_results - when: "matrix_mautrix_hangouts_container_image_self_build | bool" - -- name: Ensure Mautrix Hangouts Docker image is built - community.docker.docker_image: - name: "{{ matrix_mautrix_hangouts_docker_image }}" - source: build - force_source: "{{ matrix_mautrix_hangouts_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_mautrix_hangouts_git_pull_results.changed }}" - build: - dockerfile: Dockerfile - path: "{{ matrix_mautrix_hangouts_docker_src_files_path }}" - pull: true - when: "matrix_mautrix_hangouts_container_image_self_build | bool" - -- name: Check if an old database file already exists - ansible.builtin.stat: - path: "{{ matrix_mautrix_hangouts_base_path }}/mautrix-hangouts.db" - register: matrix_mautrix_hangouts_stat_database - -- name: (Data relocation) Ensure matrix-mautrix-hangouts.service is stopped - ansible.builtin.service: - name: matrix-mautrix-hangouts - state: stopped - enabled: false - daemon_reload: true - failed_when: false - when: "matrix_mautrix_hangouts_stat_database.stat.exists" - -- name: (Data relocation) Move mautrix-hangouts database file to ./data directory - ansible.builtin.command: - cmd: "mv {{ matrix_mautrix_hangouts_base_path }}/mautrix-hangouts.db {{ matrix_mautrix_hangouts_data_path }}/mautrix-hangouts.db" - creates: "{{ matrix_mautrix_hangouts_data_path }}/mautrix-hangouts.db" - removes: "{{ matrix_mautrix_hangouts_base_path }}/mautrix-hangouts.db" - when: "matrix_mautrix_hangouts_stat_database.stat.exists" - -- name: Ensure mautrix-hangouts config.yaml installed - ansible.builtin.copy: - content: "{{ matrix_mautrix_hangouts_configuration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_mautrix_hangouts_config_path }}/config.yaml" - mode: 0644 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - -- name: Ensure mautrix-hangouts registration.yaml installed - ansible.builtin.copy: - content: "{{ matrix_mautrix_hangouts_registration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_mautrix_hangouts_config_path }}/registration.yaml" - mode: 0644 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - -- name: Ensure mautrix-hangouts support files installed - ansible.builtin.template: - src: "{{ role_path }}/templates/{{ item }}.j2" - dest: "{{ matrix_mautrix_hangouts_base_path }}/{{ item }}" - mode: 0640 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - with_items: - - labels - -- name: Ensure matrix-mautrix-hangouts container network is created - community.general.docker_network: - enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" - name: "{{ matrix_mautrix_hangouts_container_network }}" - driver: bridge - driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" - -- name: Ensure matrix-mautrix-hangouts.service installed - ansible.builtin.template: - src: "{{ role_path }}/templates/systemd/matrix-mautrix-hangouts.service.j2" - dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-hangouts.service" - mode: 0644 - -- name: Ensure matrix-mautrix-hangouts.service restarted, if necessary - ansible.builtin.service: - name: "matrix-mautrix-hangouts.service" - state: restarted - daemon_reload: true - when: "matrix_mautrix_hangouts_requires_restart | bool" diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_uninstall.yml deleted file mode 100644 index 02d7183f6..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/setup_uninstall.yml +++ /dev/null @@ -1,20 +0,0 @@ ---- - -- name: Check existence of matrix-mautrix-hangouts service - ansible.builtin.stat: - path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-hangouts.service" - register: matrix_mautrix_hangouts_service_stat - -- when: matrix_mautrix_hangouts_service_stat.stat.exists | bool - block: - - name: Ensure matrix-mautrix-hangouts is stopped - ansible.builtin.service: - name: matrix-mautrix-hangouts - state: stopped - enabled: false - daemon_reload: true - - - name: Ensure matrix-mautrix-hangouts.service doesn't exist - ansible.builtin.file: - path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-hangouts.service" - state: absent diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml deleted file mode 100644 index 0d992175e..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml +++ /dev/null @@ -1,31 +0,0 @@ ---- - -- ansible.builtin.fail: - msg: |- - The Google Hangouts service was discontinued on November 1st, 2022. - The mautrix-hangouts bridge (which you have enabled via the `matrix_mautrix_hangouts_enabled` variable) will be removed from the playbook soon (in February 2025). - - We suggest that you uninstall this bridge by: - 1. Tweaking your `vars.yml` file - setting `matrix_mautrix_hangouts_enabled` to `false` or better yet removing all `matrix_mautrix_hangouts_*` variables - 2. Re-running the playbook with the `setup-all` (e.g. `just setup-all`) or `setup-mautrix-hangouts` tag (e.g. `just run-tags setup-mautrix-hangouts`), so that uninstallation tasks will run. - - In the future, an error will be raised for any `matrix_mautrix_hangouts_*` variables that the playbook detects in your `vars.yml` configuration file. - - Also see: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3863 - -- name: Fail if required mautrix-hangouts settings not defined - ansible.builtin.fail: - msg: >- - You need to define a required configuration setting (`{{ item.name }}`). - when: "item.when | bool and vars[item.name] == ''" - with_items: - - {'name': 'matrix_mautrix_hangouts_public_endpoint', when: true} - - {'name': 'matrix_mautrix_hangouts_appservice_token', when: true} - - {'name': 'matrix_mautrix_hangouts_homeserver_token', when: true} - - {'name': 'matrix_mautrix_hangouts_homeserver_address', when: true} - - {'name': 'matrix_mautrix_hangouts_database_hostname', when: "{{ matrix_mautrix_hangouts_database_engine == 'postgres' }}"} - - {'name': 'matrix_mautrix_hangouts_container_network', when: true} - - {'name': 'matrix_mautrix_hangouts_metrics_proxying_hostname', when: "{{ matrix_mautrix_hangouts_metrics_proxying_enabled }}"} - - {'name': 'matrix_mautrix_hangouts_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_hangouts_metrics_proxying_enabled }}"} - - {'name': 'matrix_mautrix_hangouts_container_labels_public_endpoint_hostname', when: "{{ matrix_mautrix_hangouts_container_labels_public_endpoint_enabled }}"} - - {'name': 'matrix_mautrix_hangouts_container_labels_public_endpoint_path_prefix', when: "{{ matrix_mautrix_hangouts_container_labels_public_endpoint_enabled }}"} diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-hangouts/templates/config.yaml.j2 deleted file mode 100644 index 79fdffd53..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/templates/config.yaml.j2 +++ /dev/null @@ -1,149 +0,0 @@ -#jinja2: lstrip_blocks: "True" -# Homeserver details -homeserver: - # The address that this appservice can use to connect to the homeserver. - address: {{ matrix_mautrix_hangouts_homeserver_address }} - # The domain of the homeserver (for MXIDs, etc). - domain: {{ matrix_mautrix_hangouts_homeserver_domain }} - # Whether or not to verify the SSL certificate of the homeserver. - # Only applies if address starts with https:// - verify_ssl: true - -# Application service host/registration related details -# Changing these values requires regeneration of the registration. -appservice: - # The address that the homeserver can use to connect to this appservice. - address: {{ matrix_mautrix_hangouts_appservice_address }} - - # The hostname and port where this appservice should listen. - hostname: 0.0.0.0 - port: 8080 - # The maximum body size of appservice API requests (from the homeserver) in mebibytes - # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s - max_body_size: 1 - - # The full URI to the database. SQLite and Postgres are fully supported. - # Other DBMSes supported by SQLAlchemy may or may not work. - # Format examples: - # SQLite: sqlite:///filename.db - # Postgres: postgres://username:password@hostname/dbname - database: {{ matrix_mautrix_hangouts_appservice_database|to_json }} - - # The unique ID of this appservice. - id: hangouts - # Username of the appservice bot. - bot_username: {{ matrix_mautrix_hangouts_appservice_bot_username|to_json }} - # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty - # to leave display name/avatar as-is. - bot_displayname: Hangouts bridge bot - bot_avatar: mxc://maunium.net/FBXZnpfORkBEruORbikmleAy - - # Authentication tokens for AS <-> HS communication. - as_token: "{{ matrix_mautrix_hangouts_appservice_token }}" - hs_token: "{{ matrix_mautrix_hangouts_homeserver_token }}" - -# Prometheus telemetry config. Requires prometheus-client to be installed. -metrics: - enabled: {{ matrix_mautrix_hangouts_metrics_enabled | to_json }} - listen_port: 8000 - -# Bridge config -bridge: - # Localpart template of MXIDs for Hangouts users. - # {userid} is replaced with the user ID of the Hangouts user. - username_template: "hangouts_{userid}" - # Displayname template for Hangouts users. - # {displayname} is replaced with the display name of the Hangouts user - # as defined below in displayname_preference. - # Keys available for displayname_preference are also available here. - displayname_template: '{full_name} (Hangouts)' - # Available keys: - # "name" (full name) - # "first_name" - # "last_name" - # "nickname" - # "own_nickname" (user-specific!) - displayname_preference: - - name - - # The prefix for commands. Only required in non-management rooms. - command_prefix: "{{ matrix_mautrix_hangouts_command_prefix }}" - - # Number of chats to sync (and create portals for) on startup/login. - # Maximum 20, set 0 to disable automatic syncing. - initial_chat_sync: 20 - # Whether or not the Hangouts users of logged in Matrix users should be - # invited to private chats when the user sends a message from another client. - invite_own_puppet_to_pm: false - # Whether or not to use /sync to get presence, read receipts and typing notifications when using - # your own Matrix account as the Matrix puppet for your Hangouts account. - sync_with_custom_puppets: true - # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth - # - # If set, custom puppets will be enabled automatically for local users - # instead of users having to find an access token and run `login-matrix` - # manually. - login_shared_secret: {{ matrix_mautrix_hangouts_login_shared_secret|to_json }} - # Whether or not to update avatars when syncing all contacts at startup. - update_avatar_initial_sync: true - # End-to-bridge encryption support options. These require matrix-nio to be installed with pip - # and login_shared_secret to be configured in order to get a device for the bridge bot. - # - # Additionally, https://github.com/matrix-org/synapse/pull/5758 is required if using a normal - # application service. - encryption: - # Allow encryption, work in group chat rooms with e2ee enabled - allow: {{ matrix_mautrix_hangouts_bridge_encryption_allow|to_json }} - # Default to encryption, force-enable encryption in all portals the bridge creates - # This will cause the bridge bot to be in private chats for the encryption to work properly. - default: {{ matrix_mautrix_hangouts_bridge_encryption_default|to_json }} - - # Public website and API configs - web: - # Auth server config - auth: - # Publicly accessible base URL for the login endpoints. - # The prefix below is not implicitly added. This URL and all subpaths should be proxied - # or otherwise pointed to the appservice's webserver to the path specified below (prefix). - # This path should usually include a trailing slash. - # Internal prefix in the appservice web server for the login endpoints. - public: "{{ matrix_homeserver_url }}{{ matrix_mautrix_hangouts_public_endpoint }}/login" - prefix: "{{ matrix_mautrix_hangouts_public_endpoint }}/login" - - - # Permissions for using the bridge. - # Permitted values: - # user - Use the bridge with puppeting. - # admin - Use and administrate the bridge. - # Permitted keys: - # * - All Matrix users - # domain - All users on that homeserver - # mxid - Specific user - permissions: {{ matrix_mautrix_hangouts_bridge_permissions|to_json }} - -# Python logging configuration. -# -# See section 16.7.2 of the Python documentation for more info: -# https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema -logging: - version: 1 - formatters: - colored: - (): mautrix_hangouts.util.ColorFormatter - format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s" - normal: - format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s" - handlers: - console: - class: logging.StreamHandler - formatter: colored - loggers: - mau: - level: {{ matrix_mautrix_hangouts_logging_level|to_json }} - hangups: - level: {{ matrix_mautrix_hangouts_logging_level|to_json }} - aiohttp: - level: {{ matrix_mautrix_hangouts_logging_level|to_json }} - root: - level: {{ matrix_mautrix_hangouts_logging_level|to_json }} - handlers: [console] diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-hangouts/templates/labels.j2 deleted file mode 100644 index 31dd03e2d..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/templates/labels.j2 +++ /dev/null @@ -1,76 +0,0 @@ -{% if matrix_mautrix_hangouts_container_labels_traefik_enabled %} -traefik.enable=true - -{% if matrix_mautrix_hangouts_container_labels_traefik_docker_network %} -traefik.docker.network={{ matrix_mautrix_hangouts_container_labels_traefik_docker_network }} -{% endif %} - -traefik.http.services.matrix-mautrix-hangouts-public.loadbalancer.server.port=8080 -traefik.http.services.matrix-mautrix-hangouts-metrics.loadbalancer.server.port=8000 - -{% if matrix_mautrix_hangouts_container_labels_public_endpoint_enabled %} -############################################################ -# # -# Public # -# # -############################################################ - -traefik.http.routers.matrix-mautrix-hangouts-public.rule={{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_rule }} - -{% if matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_priority | int > 0 %} -traefik.http.routers.matrix-mautrix-hangouts-public.priority={{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_priority }} -{% endif %} - -traefik.http.routers.matrix-mautrix-hangouts-public.service=matrix-mautrix-hangouts-public -traefik.http.routers.matrix-mautrix-hangouts-public.entrypoints={{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_entrypoints }} - -traefik.http.routers.matrix-mautrix-hangouts-public.tls={{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_tls | to_json }} -{% if matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_tls %} -traefik.http.routers.matrix-mautrix-hangouts-public.tls.certResolver={{ matrix_mautrix_hangouts_container_labels_public_endpoint_traefik_tls_certResolver }} -{% endif %} - -############################################################ -# # -# /Public # -# # -############################################################ -{% endif %} - - -{% if matrix_mautrix_hangouts_container_labels_metrics_enabled %} -############################################################ -# # -# Metrics # -# # -############################################################ - -{% if matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_enabled %} -traefik.http.middlewares.matrix-mautrix-hangouts-metrics-basic-auth.basicauth.users={{ matrix_mautrix_hangouts_container_labels_metrics_middleware_basic_auth_users }} -traefik.http.routers.matrix-mautrix-hangouts-metrics.middlewares=matrix-mautrix-hangouts-metrics-basic-auth -{% endif %} - -traefik.http.routers.matrix-mautrix-hangouts-metrics.rule={{ matrix_mautrix_hangouts_container_labels_metrics_traefik_rule }} - -{% if matrix_mautrix_hangouts_container_labels_metrics_traefik_priority | int > 0 %} -traefik.http.routers.matrix-mautrix-hangouts-metrics.priority={{ matrix_mautrix_hangouts_container_labels_metrics_traefik_priority }} -{% endif %} - -traefik.http.routers.matrix-mautrix-hangouts-metrics.service=matrix-mautrix-hangouts-metrics -traefik.http.routers.matrix-mautrix-hangouts-metrics.entrypoints={{ matrix_mautrix_hangouts_container_labels_metrics_traefik_entrypoints }} - -traefik.http.routers.matrix-mautrix-hangouts-metrics.tls={{ matrix_mautrix_hangouts_container_labels_metrics_traefik_tls | to_json }} -{% if matrix_mautrix_hangouts_container_labels_metrics_traefik_tls %} -traefik.http.routers.matrix-mautrix-hangouts-metrics.tls.certResolver={{ matrix_mautrix_hangouts_container_labels_metrics_traefik_tls_certResolver }} -{% endif %} - -############################################################ -# # -# /Metrics # -# # -############################################################ -{% endif %} - - -{% endif %} - -{{ matrix_mautrix_hangouts_container_labels_additional_labels }} diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/templates/systemd/matrix-mautrix-hangouts.service.j2 b/roles/custom/matrix-bridge-mautrix-hangouts/templates/systemd/matrix-mautrix-hangouts.service.j2 deleted file mode 100644 index cc0dfa353..000000000 --- a/roles/custom/matrix-bridge-mautrix-hangouts/templates/systemd/matrix-mautrix-hangouts.service.j2 +++ /dev/null @@ -1,69 +0,0 @@ -#jinja2: lstrip_blocks: "True" -[Unit] -Description=Matrix Mautrix Hangouts bridge -{% for service in matrix_mautrix_hangouts_systemd_required_services_list %} -Requires={{ service }} -After={{ service }} -{% endfor %} -{% for service in matrix_mautrix_hangouts_systemd_wanted_services_list %} -Wants={{ service }} -{% endfor %} -DefaultDependencies=no - -[Service] -Type=simple -Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-hangouts matrix-mautrix-hangouts-db 2>/dev/null || true' -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-hangouts matrix-mautrix-hangouts-db 2>/dev/null || true' - -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ - --rm \ - --name=matrix-mautrix-hangouts-db \ - --log-driver=none \ - --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ - --cap-drop=ALL \ - --network={{ matrix_mautrix_hangouts_container_network }} \ - --mount type=bind,src={{ matrix_mautrix_hangouts_config_path }},dst=/config \ - --mount type=bind,src={{ matrix_mautrix_hangouts_data_path }},dst=/data \ - {{ matrix_mautrix_hangouts_docker_image }} \ - alembic -x config=/config/config.yaml upgrade head - -{% for network in matrix_mautrix_hangouts_container_additional_networks %} -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-mautrix-hangouts-db -{% endfor %} - -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-hangouts-db - -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ - --rm \ - --name=matrix-mautrix-hangouts \ - --log-driver=none \ - --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ - --cap-drop=ALL \ - --network={{ matrix_mautrix_hangouts_container_network }} \ - {% if matrix_mautrix_hangouts_container_http_host_bind_port %} - -p {{ matrix_mautrix_hangouts_container_http_host_bind_port }}:8080 \ - {% endif %} - --mount type=bind,src={{ matrix_mautrix_hangouts_config_path }},dst=/config \ - --mount type=bind,src={{ matrix_mautrix_hangouts_data_path }},dst=/data \ - --label-file={{ matrix_mautrix_hangouts_base_path }}/labels \ - {% for arg in matrix_mautrix_hangouts_container_extra_arguments %} - {{ arg }} \ - {% endfor %} - {{ matrix_mautrix_hangouts_docker_image }} \ - python3 -m mautrix_hangouts -c /config/config.yaml --no-update - -{% for network in matrix_mautrix_hangouts_container_additional_networks %} -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-mautrix-hangouts -{% endfor %} - -ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-hangouts - -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-hangouts 2>/dev/null || true' -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-hangouts 2>/dev/null || true' -Restart=always -RestartSec=30 -SyslogIdentifier=matrix-mautrix-hangouts - -[Install] -WantedBy=multi-user.target diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 77a72aa3a..4d61f765f 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -452,3 +452,16 @@ The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map (attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | list | items2dict" + +- name: (Deprecation) Catch and report mautrix-hangouts variables + ansible.builtin.fail: + msg: |- + The Google Hangouts service was discontinued on 1st of November 2022. + The mautrix-hangouts bridge has been deprecated in the playbook since December 2024 and was completely removed from the playbook in February 2025. + + Please change your configuration (`vars.yml`) to remove all `matrix_mautrix_hangouts_*` variables. + + You may also wish to uninstall the bridge manually. See `docs/configuring-playbook-bridge-mautrix-hangouts.md` for more information. + + The following variables in your configuration need to be removed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | map (attribute='key') | join(', ') }} + when: "vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | list | items2dict" diff --git a/setup.yml b/setup.yml index 1eb867c7f..37ae61f26 100644 --- a/setup.yml +++ b/setup.yml @@ -64,7 +64,6 @@ - custom/matrix-bridge-wechat - custom/matrix-bridge-mautrix-facebook - custom/matrix-bridge-mautrix-twitter - - custom/matrix-bridge-mautrix-hangouts - custom/matrix-bridge-mautrix-googlechat - custom/matrix-bridge-mautrix-instagram - custom/matrix-bridge-mautrix-meta-messenger From 038d046612f1d225c8aecfe15a43882c8be94cd6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 13:29:38 +0900 Subject: [PATCH 422/952] Update docs/maintenance-and-troubleshooting.md: tidy up Signed-off-by: Suguru Hirahara --- docs/maintenance-and-troubleshooting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index fa38df727..ed164997e 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -14,14 +14,14 @@ sudo systemctl status matrix-synapse 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). -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`. - -To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this: +To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), log in to the server with SSH and run a command like this: ```sh sudo journalctl -fu matrix-synapse ``` +**Note**: 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`. + ## How to check if services work The playbook can perform a check to ensure that you've configured things correctly and that services are running. @@ -40,7 +40,7 @@ Besides this self-check, you can also check whether your server federates with t ## Remove unused Docker data -You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information. +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. ```sh ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune From 61c9d4c55c49966b4b8bcbc684a1118c24b95fda Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 15:48:59 +0900 Subject: [PATCH 423/952] Update docs/faq.md and docs/maintenance-and-troubleshooting.md: adopt the common description Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 +- docs/maintenance-and-troubleshooting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index c41c7fe11..bd537aa69 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -419,7 +419,7 @@ Available service names can be seen by doing `ls /etc/systemd/system/matrix*.ser Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that. -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. +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-*`. We just simply delegate logging to journald and it takes care of persistence and expiring old data. diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index ed164997e..e6439a3bb 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -20,7 +20,7 @@ To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/j sudo journalctl -fu matrix-synapse ``` -**Note**: 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`. +**Note**: 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-*`. ## How to check if services work From ecdf370cb77553568bf708a51adf544af56859c8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:19:10 +0900 Subject: [PATCH 424/952] Update docs/faq.md and docs/maintenance-and-troubleshooting.md: move the troubleshooting section from the FAQ page to the dedicated page As the theme deserves the dedicated page and we already have it, it seems sensible to move the topic from the general FAQ page. Signed-off-by: Suguru Hirahara --- docs/faq.md | 33 +------------------------ docs/maintenance-and-troubleshooting.md | 25 +++++++++++++++++-- 2 files changed, 24 insertions(+), 34 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index bd537aa69..502e40b0d 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -407,40 +407,9 @@ If you're running Ansible from within a container (one of the possibilities we l ### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`. -See [How can I see the logs?](#how-can-i-see-the-logs). - -### How can I see the logs? - -We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging. - -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). - -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. - 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-*`. -We just simply delegate logging to journald and it takes care of persistence and expiring old data. - -Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for) - -### How long do systemd/journald logs persist for? - -On some distros, the journald logs are just in-memory and not persisted to disk. - -Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`. - -To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this: - -```ini -[Journal] -RuntimeMaxUse=200M -SystemMaxUse=1G -RateLimitInterval=0 -RateLimitBurst=0 -Storage=persistent -``` +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. ## Maintenance diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index e6439a3bb..377eca51a 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -12,15 +12,36 @@ sudo systemctl status matrix-synapse Active: active (running) since Sun 2024-01-14 09:13:06 UTC; 1h 31min ago ``` +## How to see the logs + 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). -To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), log in to the server with SSH and run a command like this: +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: ```sh sudo journalctl -fu matrix-synapse ``` -**Note**: 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-*`. +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. + +We just simply delegate logging to journald and it takes care of persistence and expiring old data. + +### Enable systemd/journald logs persistence + +On some distros, the journald logs are just in-memory and not persisted to disk. + +Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`. + +To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this: + +```ini +[Journal] +RuntimeMaxUse=200M +SystemMaxUse=1G +RateLimitInterval=0 +RateLimitBurst=0 +Storage=persistent +``` ## How to check if services work From bd794e8c2c39020724474dacf25b65f0280ca934 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:21:21 +0900 Subject: [PATCH 425/952] Update maintenance-and-troubleshooting.md: create sections "Maintenance" and "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/maintenance-and-troubleshooting.md | 40 ++++++++++++++----------- 1 file changed, 22 insertions(+), 18 deletions(-) diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 377eca51a..460144183 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -1,6 +1,24 @@ # Maintenance and Troubleshooting -## How to see the current status of your services +## Maintenance + +### Remove unused Docker data + +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. + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune +``` + +The shortcut command with `just` program is also available: `just run-tags run-docker-prune` + +### Postgres + +See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page. + +## Troubleshooting + +### How to see the current status of your services You can check the status of your services by using `systemctl status`. Example: @@ -12,7 +30,7 @@ sudo systemctl status matrix-synapse Active: active (running) since Sun 2024-01-14 09:13:06 UTC; 1h 31min ago ``` -## How to see the logs +### How to see the logs 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). @@ -26,7 +44,7 @@ Available service names can be seen by doing `ls /etc/systemd/system/matrix*.ser We just simply delegate logging to journald and it takes care of persistence and expiring old data. -### Enable systemd/journald logs persistence +#### Enable systemd/journald logs persistence On some distros, the journald logs are just in-memory and not persisted to disk. @@ -43,7 +61,7 @@ RateLimitBurst=0 Storage=persistent ``` -## How to check if services work +### How to check if services work The playbook can perform a check to ensure that you've configured things correctly and that services are running. @@ -58,17 +76,3 @@ The shortcut command with `just` program is also available: `just run-tags self- If it's all green, everything is probably running correctly. 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. - -## Remove unused Docker data - -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. - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune -``` - -The shortcut command with `just` program is also available: `just run-tags run-docker-prune` - -## Postgres - -See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page. From 1be1a5e3970828d4edcdfbb53b9423c99066bbe2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:30:46 +0900 Subject: [PATCH 426/952] Update docs/faq.md and docs/maintenance-and-troubleshooting.md: move entries which are instruction and how-to, rather than questions Signed-off-by: Suguru Hirahara --- docs/faq.md | 23 ----------------------- docs/maintenance-and-troubleshooting.md | 23 +++++++++++++++++++++++ 2 files changed, 23 insertions(+), 23 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 502e40b0d..9effaa235 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -425,35 +425,12 @@ If you have an existing installation done using this Ansible playbook, you can e 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). -### How do I back up the data on my server? - -We haven't documented this properly yet, but the general advice is to: - -- back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) - -- back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql)). - -You can later restore these by: - -- Restoring the `/matrix` directory and files on the new server manually -- Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data) - -If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again. - ### What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space? 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. After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup` -### How do I debug or force SSL certificate renewal? - -SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server. - -If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`). - -If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way. - ## Miscellaneous ### I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it? diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 460144183..7cf08e2eb 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -2,6 +2,21 @@ ## Maintenance +### How to back up the data on your server + +We haven't documented this properly yet, but the general advice is to: + +- back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) + +- back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql)). + +You can later restore these by: + +- Restoring the `/matrix` directory and files on the new server manually +- Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data) + +If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again. + ### Remove unused Docker data 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. @@ -76,3 +91,11 @@ The shortcut command with `just` program is also available: `just run-tags self- If it's all green, everything is probably running correctly. 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. + +### How to debug or force SSL certificate renewal + +SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server. + +If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`). + +If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way. From e36848e9e6605b720e0a9a935761e1ad929427d4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:41:19 +0900 Subject: [PATCH 427/952] Update docs/faq.md: merge the sections "Troubleshooting" and "Maintenance" Signed-off-by: Suguru Hirahara --- docs/faq.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 9effaa235..e48dba495 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -403,15 +403,7 @@ It can perform a local connection instead. Just set `ansible_connection=local` a If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible. -## Troubleshooting - -### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`. - -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-*`. - -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. - -## Maintenance +## Maintenance and Troubleshooting ### Do I need to do anything to keep my Matrix server updated? @@ -431,6 +423,12 @@ When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-po After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup` +### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`. + +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-*`. + +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. + ## Miscellaneous ### I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it? From 05fb62e525c3abf86285dfc28c9c56af9dbc9274 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:43:06 +0900 Subject: [PATCH 428/952] Update docs/faq.md: change the entry for troubleshooting into a question Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index e48dba495..313e29a29 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -423,7 +423,7 @@ When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-po After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup` -### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`. +### I get "Error response from daemon: configured logging driver does not support reading" when I run `docker logs matrix-synapse`. Why? 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-*`. From 46a821af75da64a269d9770b619f72156c468252 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:47:28 +0900 Subject: [PATCH 429/952] Update docs/faq.md: remove an emphasis from the entry for troubleshooting Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 313e29a29..7a74d4043 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -425,7 +425,7 @@ After verifying that everything still works after the Postgres upgrade, you can ### I get "Error response from daemon: configured logging driver does not support reading" when I run `docker logs matrix-synapse`. Why? -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-*`. +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-*`. 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. From 0b1ee94b0046015235f095fd3355e4760a41695a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 03:48:48 +0900 Subject: [PATCH 430/952] Update docs/maintenance-and-troubleshooting.md: add the link to Synapse maintenance documentation page Signed-off-by: Suguru Hirahara --- docs/maintenance-and-troubleshooting.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 7cf08e2eb..99205697e 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -29,7 +29,11 @@ The shortcut command with `just` program is also available: `just run-tags run-d ### Postgres -See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page. +See the dedicated [PostgreSQL maintenance](maintenance-postgres.md) documentation page. + +### Synapse + +See the dedicated [Synapse maintenance](maintenance-synapse.md) documentation page. ## Troubleshooting From 143f8a541548d68b68b5bd8f3455689e478b8682 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Feb 2025 17:38:01 +0900 Subject: [PATCH 431/952] Update docs/faq.md: add the link to maintenance-and-troubleshooting.md Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index 7a74d4043..df8f74e86 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -405,6 +405,8 @@ If you're running Ansible from within a container (one of the possibilities we l ## Maintenance and Troubleshooting +💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md) + ### Do I need to do anything to keep my Matrix server updated? Yes. We don't update anything for you automatically. From 5d7971a7909f97f3dd51db8a196340b2d45ffcf3 Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 4 Feb 2025 15:05:39 +0200 Subject: [PATCH 432/952] borgmatic v1.9.9 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 7d4f69401..f5097355a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.6-0 + version: v1.4.0-1.9.9-0 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From fac9ac16404e37c841d9e7a4ba36651424ca3f17 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 09:26:05 -0500 Subject: [PATCH 433/952] Update docs/configuring-playbook-synapse-auto-compressor.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-auto-compressor.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 8af611fae..1b3c7690b 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -14,6 +14,14 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_synapse_auto_compressor_enabled: true ``` +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-synapse-auto-compressor/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 931e6e2dcecec549155c4c5d13d539236b990bc0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 16:13:10 +0900 Subject: [PATCH 434/952] Update docs/configuring-playbook-synapse-auto-compressor.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-auto-compressor.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 1b3c7690b..419c781ac 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -46,3 +46,7 @@ Sometimes it can be helpful to execute compression as you'd like, avoiding to wa If you want to execute it immediately, log in to the server with SSH and run `systemctl start matrix-synapse-auto-compressor`. 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-auto-compressor`. From b0c73c8378aab45cd073b53e98bff7a0c9bd4edd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 16:19:12 +0900 Subject: [PATCH 435/952] Update docs for backup-borg and synapse-auto-compressor: use the common descriptions Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 10 +++++++--- docs/configuring-playbook-synapse-auto-compressor.md | 12 +++++++++++- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 702e72613..9f219ffc4 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -95,9 +95,9 @@ backup_borg_retention_keep_monthly: 12 backup_borg_retention_keep_yearly: 2 ``` -### Edit the backup schedule (optional) +### Edit the schedule (optional) -By default the backup will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar. +By default the task will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): @@ -134,7 +134,11 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. -## Manually start a backup +## Usage + +After installation, `backup-borg` will run automatically every day at `04:00:00` (as defined in `backup_borg_schedule` by default). + +### Manually start the task 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. diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 419c781ac..959765531 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -14,6 +14,16 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/ matrix_synapse_auto_compressor_enabled: true ``` +### Edit the schedule (optional) + +By default the task will run 0 a.m. every day based on the `matrix_synapse_auto_compressor_calendar` variable. It is defined in the format of systemd timer calendar. + +To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +matrix_synapse_auto_compressor_calendar: "*-*-* 00:00:00" +``` + ### Extending the configuration There are some additional things you may wish to configure about the component. @@ -39,7 +49,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default). -## Manually execute compression +### Manually start the task Sometimes it can be helpful to execute compression as you'd like, avoiding to wait until 00:00, like when you test your configuration. From 08e34a4a6fb8db87a81afaa88ec7a6f5cf1759c3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 01:24:55 +0900 Subject: [PATCH 436/952] Rename "matrix_synapse_auto_compressor_calendar" to "matrix_synapse_auto_compressor_schedule" for consistency Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-auto-compressor.md | 6 +++--- .../matrix-synapse-auto-compressor/defaults/main.yml | 2 +- .../tasks/validate_config.yml | 9 +++++++++ .../templates/matrix-synapse-auto-compressor.timer.j2 | 2 +- 4 files changed, 14 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 959765531..988be65c3 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -16,12 +16,12 @@ matrix_synapse_auto_compressor_enabled: true ### Edit the schedule (optional) -By default the task will run 0 a.m. every day based on the `matrix_synapse_auto_compressor_calendar` variable. It is defined in the format of systemd timer calendar. +By default the task will run 0 a.m. every day based on the `matrix_synapse_auto_compressor_schedule` variable. It is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): ```yaml -matrix_synapse_auto_compressor_calendar: "*-*-* 00:00:00" +matrix_synapse_auto_compressor_schedule: "*-*-* 00:00:00" ``` ### Extending the configuration @@ -47,7 +47,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Usage -After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default). +After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_schedule` by default). ### Manually start the task diff --git a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml index e80ce35f0..212213d64 100644 --- a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml +++ b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml @@ -56,7 +56,7 @@ matrix_synapse_auto_compressor_database_name: 'synapse' matrix_synapse_auto_compressor_synapse_database: 'postgres://{{ matrix_synapse_auto_compressor_database_username | urlencode() }}:{{ matrix_synapse_auto_compressor_database_password | urlencode() }}@{{ matrix_synapse_auto_compressor_database_hostname }}:{{ matrix_synapse_auto_compressor_database_port }}/{{ matrix_synapse_auto_compressor_database_name }}' # systemd calendar configuration for the compressor job -matrix_synapse_auto_compressor_calendar: "*-*-* 00:00:00" +matrix_synapse_auto_compressor_schedule: "*-*-* 00:00:00" # The number of state groups to work on at once. # All of the entries from state_groups_state are requested from the database for state groups that are worked on. diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml index b0dbfab06..1d1405044 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml @@ -1,4 +1,13 @@ --- +- name: (Deprecation) Catch and report renamed settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - "old": "matrix_synapse_auto_compressor_calendar" + "new": "matrix_synapse_auto_compressor_schedule" - name: Fail if required matrix-synapse-auto-compressor settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 index 1d7b16d33..82c235c80 100644 --- a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 +++ b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 @@ -3,7 +3,7 @@ Description=Synapse State Auto Compressor Timer [Timer] Unit=matrix-synapse-auto-compressor.service -OnCalendar={{ matrix_synapse_auto_compressor_calendar }} +OnCalendar={{ matrix_synapse_auto_compressor_schedule }} [Install] WantedBy=timers.target From 1bb21388c5cabadaf727078502b7f2af4fc4c5a9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 16:25:02 +0900 Subject: [PATCH 437/952] Update docs/configuring-playbook-backup-borg.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 9f219ffc4..aca22c2f6 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -145,3 +145,7 @@ Sometimes it can be helpful to run the backup as you'd like, avoiding to wait un If you want to run it immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu backup-borg`. From 030f0c6e5c0c5f96be6c87507f2cad0711f6ccd5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 16:44:52 +0900 Subject: [PATCH 438/952] Update docs/faq.md: replace the link to a new issue This commit replaces the link to a blank issue to the one to the chooser. Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index df8f74e86..3e475fba8 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -435,6 +435,6 @@ See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on th ### I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it? -You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself. +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. 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. From 2123aa5eb20a73afda07085f74b6998288a8f725 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 4 Feb 2025 16:42:41 +0000 Subject: [PATCH 439/952] Update ghcr.io/element-hq/matrix-authentication-service Docker tag to v0.13.0 --- roles/custom/matrix-authentication-service/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 9e7780e34..3b9546424 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -17,7 +17,7 @@ matrix_authentication_service_container_repo_version: "{{ 'main' if matrix_authe matrix_authentication_service_container_src_files_path: "{{ matrix_base_data_path }}/matrix-authentication-service/container-src" # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service -matrix_authentication_service_version: 0.12.0 +matrix_authentication_service_version: 0.13.0 matrix_authentication_service_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service:{{ matrix_authentication_service_version }}" matrix_authentication_service_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_container_image_force_pull: "{{ matrix_authentication_service_container_image.endswith(':latest') }}" From 18bd34a6651f5433921a83271855fa55aae9fdee Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 4 Feb 2025 16:42:48 +0000 Subject: [PATCH 440/952] Update ghcr.io/element-hq/matrix-authentication-service/syn2mas Docker tag to v0.13.0 --- roles/custom/matrix-authentication-service/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 9e7780e34..4cafe1bf7 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -555,7 +555,7 @@ matrix_authentication_service_syn2mas_start_wait_time_seconds: 5 matrix_authentication_service_syn2mas_dry_run: false # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service/syn2mas -matrix_authentication_service_syn2mas_version: 0.12.0 +matrix_authentication_service_syn2mas_version: 0.13.0 matrix_authentication_service_syn2mas_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service/syn2mas:{{ matrix_authentication_service_syn2mas_version }}" matrix_authentication_service_syn2mas_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_syn2mas_container_image_force_pull: "{{ matrix_authentication_service_syn2mas_container_image.endswith(':latest') }}" From 97b458bec8bbe7eeeac73bca136cf49096b02f8e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 4 Feb 2025 21:05:40 +0200 Subject: [PATCH 441/952] Update Matrix Authentication Service docs in light of MAS v0.13.0 Ref: - https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4030 - https://github.com/element-hq/matrix-authentication-service/releases/tag/v0.13.0 - https://github.com/element-hq/matrix-authentication-service/issues/1505 - https://github.com/element-hq/matrix-authentication-service/pull/3784 --- ...ing-playbook-matrix-authentication-service.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index ad2fb8b7f..cdf43a0c0 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -36,8 +36,6 @@ Below, we'll try to **highlight some potential reasons for switching** to Matrix - ⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet. -- ⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working. - - ❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below. ## Expectations @@ -59,8 +57,6 @@ This section details what you can expect when switching to the Matrix Authentica - ❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting). -- ⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working. - - ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break. - ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the "admin" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`) @@ -75,7 +71,7 @@ This section details what you can expect when switching to the Matrix Authentica - ✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service -- ✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow. +- ✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work - ✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`. @@ -459,11 +455,15 @@ You can register users new users as described in the [Registering users](./regis ### Working around email deliverability issues -Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working. +Matrix Authentication Service only sends emails when: -Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address. +- it verifies email addresses for users who are self-registering with a password -If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`). +- a user tries to add an email to their account + +If Matrix Authentication Service tries to send an email and it fails because [your email-sending configuration](./configuring-playbook-email.md) is not working, you may need to work around email deliverability. + +If email delivery is not working, **you can retrieve the email verification code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`). Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com` From 16761c4c178138ea576544b2ed4e2ca5eaa38351 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 4 Feb 2025 21:08:11 +0200 Subject: [PATCH 442/952] Update Matrix Authentication Service docs in light of MAS v0.13.0 - part 2 Ref: - https://github.com/element-hq/matrix-authentication-service/issues/3440 - https://github.com/element-hq/matrix-authentication-service/pull/3447 --- docs/configuring-playbook-matrix-authentication-service.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index cdf43a0c0..ce5c7aa5d 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -59,8 +59,6 @@ This section details what you can expect when switching to the Matrix Authentica - ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break. -- ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the "admin" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`) - - ⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch. - ⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration). From b1856f0a225b407840fa055c0b34c4c91efd82cf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 14:07:01 +0900 Subject: [PATCH 443/952] Fix capitalization: nginx It should be either NGINX or nginx, and this commit converts the string in uppercase to lowercase. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- docs/configuring-playbook-prometheus-nginxlog.md | 4 ++-- docs/configuring-playbook.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 851fa1635..001500c59 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -73,7 +73,7 @@ Name | Description `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. `prometheus_node_exporter_enabled`|[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 `prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. -`matrix_prometheus_nginxlog_exporter_enabled`|[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus. +`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. `grafana_enabled`|[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 `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. `grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here @@ -107,7 +107,7 @@ Name | Description `prometheus_node_exporter_container_labels_traefik_enabled`|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. `prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network) `prometheus_postgres_exporter_container_labels_traefik_enabled`|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. -`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network) +`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network) `matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network) `matrix_sliding_sync_metrics_proxying_enabled`|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. `matrix_bridge_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 5d04d905b..80107b906 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -1,4 +1,4 @@ -# Enabling metrics and graphs for NginX logs (optional) +# Enabling metrics and graphs for nginx logs (optional) The playbook can install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you, in order to make it possible to have some (visual) insight into [nginx](https://nginx.org/) logs. @@ -25,7 +25,7 @@ matrix_prometheus_nginxlog_exporter_enabled: true ### Save metrics on an external Prometheus server (optional) > [!WARNING] -> Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. +> Metrics and resulting graphs can contain a lot of information. nginx logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 6a2942a24..71a7426c4 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -199,7 +199,7 @@ Services that help you in administrating and monitoring your Matrix installation - [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) -- [Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md) +- [Enabling metrics and graphs for nginx logs](configuring-playbook-prometheus-nginxlog.md) - [Setting up the rageshake bug report server](configuring-playbook-rageshake.md) From 16eda7a0727bed072eab113cf7f60503546edeb7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 03:00:26 +0900 Subject: [PATCH 444/952] Replace "Warnings" with the colorfully decorated one Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-conduit.md | 8 +++----- docs/configuring-playbook-conduwuit.md | 8 +++----- docs/configuring-playbook-dendrite.md | 8 +++----- docs/configuring-playbook-matrix-registration.md | 6 +++--- docs/uninstalling.md | 8 +++----- 5 files changed, 15 insertions(+), 23 deletions(-) diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index be5b46f6a..51cfb8e64 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -8,11 +8,9 @@ By default, the playbook installs [Synapse](https://github.com/element-hq/synaps 💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md). -⚠️ **Warnings**: - -- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. - -- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding +> [!WARNING] +> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. +> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md index 71cedbb5f..a2ea0c925 100644 --- a/docs/configuring-playbook-conduwuit.md +++ b/docs/configuring-playbook-conduwuit.md @@ -8,11 +8,9 @@ By default, the playbook installs [Synapse](https://github.com/element-hq/synaps 💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html). -⚠️ **Warnings**: - -- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. - -- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding +> [!WARNING] +> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. +> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index 7496e918d..ac5671dbf 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -6,11 +6,9 @@ See the project's [documentation](https://element-hq.github.io/dendrite/) to lea By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document. -⚠️ **Warnings**: - -- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. - -- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding +> [!WARNING] +> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet. +> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding ## Adjusting the playbook configuration diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index e46fbc652..2a08fa681 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -1,8 +1,8 @@ # Setting up matrix-registration (optional) -⚠️ **Warnings**: -- This is a poorly maintained and buggy project. It's better to avoid using it. -- This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) +> [!WARNING] +> - This is a poorly maintained and buggy project. It's better to avoid using it. +> - This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) 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. diff --git a/docs/uninstalling.md b/docs/uninstalling.md index 14c8c211f..4c70082f5 100644 --- a/docs/uninstalling.md +++ b/docs/uninstalling.md @@ -1,10 +1,8 @@ # Uninstalling -⚠️ **Warnings**: -- If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating. -- If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**. - ------------------ +> [!WARNING] +> - If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating. +> - If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**. ## Uninstalling using a script From bf7f2f6734a21750e01836ec1b02c30b963dfee2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 03:01:34 +0900 Subject: [PATCH 445/952] Update docs/configuring-playbook-bot-baibot.md: adopt the common description for increasing logging verbosity Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index 01984a4b7..ac270d3a3 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -400,7 +400,9 @@ You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) pr As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot` -The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration: +### Increase logging verbosity + +The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook: ```yaml # Adjust the bot's own logging level. From f40b26d3d308db7d756ff8540a6a445273b11d42 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 6 Feb 2025 05:17:01 +0000 Subject: [PATCH 446/952] Update nginx Docker tag to v1.27.4 --- .../matrix-synapse-reverse-proxy-companion/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 192ece0a2..98e0c2d65 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -13,7 +13,7 @@ matrix_synapse_reverse_proxy_companion_enabled: true # renovate: datasource=docker depName=nginx -matrix_synapse_reverse_proxy_companion_version: 1.27.3-alpine +matrix_synapse_reverse_proxy_companion_version: 1.27.4-alpine matrix_synapse_reverse_proxy_companion_base_path: "{{ matrix_synapse_base_path }}/reverse-proxy-companion" matrix_synapse_reverse_proxy_companion_confd_path: "{{ matrix_synapse_reverse_proxy_companion_base_path }}/conf.d" From f01d95f2dd5a3d281603d810557438a686fb1ade Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 11:49:05 -0500 Subject: [PATCH 447/952] Update docs/configuring-playbook-rageshake: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-rageshake.md | 37 +++++++++++++++++--------- 1 file changed, 25 insertions(+), 12 deletions(-) diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index 6db32e43a..aa61314f0 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -20,18 +20,6 @@ To enable rageshake, add the following configuration to your `inventory/host_var matrix_rageshake_enabled: true ``` -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). - -To set these, you can make use of the `matrix_rageshake_configuration_extension_yaml` variable like this: - -```yaml -matrix_rageshake_configuration_extension_yaml: | - github_token: secrettoken - - github_project_mappings: - my-app: octocat/HelloWorld -``` - ### Adjusting the rageshake URL (optional) By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -51,6 +39,31 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. +### Extending the configuration + +There are some additional things you may wish to configure about the server. + +Take a look at: + +- `roles/custom/matrix-rageshake/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `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 + +```yaml +matrix_rageshake_configuration_extension_yaml: | + # Your custom YAML configuration goes here. + # This configuration extends the default starting configuration (`matrix_rageshake_configuration_extension_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_rageshake_configuration_extension_yaml`. + + github_token: secrettoken + + github_project_mappings: + my-app: octocat/HelloWorld +``` + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 51f0a315ac5f93bdc0fb116971e799c59e539024 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 00:42:45 +0900 Subject: [PATCH 448/952] =?UTF-8?q?Update=20files=20for=20rageshake:=20cha?= =?UTF-8?q?nge=20config.yml.j2=20=E2=86=92=20config.yaml.j2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Suguru Hirahara --- roles/custom/matrix-rageshake/defaults/main.yml | 2 +- roles/custom/matrix-rageshake/tasks/install.yml | 2 +- .../templates/{config.yml.j2 => config.yaml.j2} | 0 .../templates/systemd/matrix-rageshake.service.j2 | 2 +- 4 files changed, 3 insertions(+), 3 deletions(-) rename roles/custom/matrix-rageshake/templates/{config.yml.j2 => config.yaml.j2} (100%) diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index 77caeab1b..f104cbebd 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -93,7 +93,7 @@ matrix_rageshake_config_api_prefix: "{{ matrix_rageshake_scheme }}://{{ matrix_r # # For a more advanced customization, you can extend the default (see `matrix_rageshake_configuration_extension_yaml`) # or completely replace this variable with your own template. -matrix_rageshake_configuration_yaml: "{{ lookup('template', 'templates/config.yml.j2') }}" +matrix_rageshake_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" matrix_rageshake_configuration_extension_yaml: | # Your custom YAML configuration for Synapse goes here. diff --git a/roles/custom/matrix-rageshake/tasks/install.yml b/roles/custom/matrix-rageshake/tasks/install.yml index 572f03f1f..33953de5e 100644 --- a/roles/custom/matrix-rageshake/tasks/install.yml +++ b/roles/custom/matrix-rageshake/tasks/install.yml @@ -19,7 +19,7 @@ - name: Ensure rageshake config file created ansible.builtin.copy: content: "{{ matrix_rageshake_configuration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_rageshake_config_path }}/config.yml" + dest: "{{ matrix_rageshake_config_path }}/config.yaml" owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" mode: 0640 diff --git a/roles/custom/matrix-rageshake/templates/config.yml.j2 b/roles/custom/matrix-rageshake/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-rageshake/templates/config.yml.j2 rename to roles/custom/matrix-rageshake/templates/config.yaml.j2 diff --git a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 index 9abaf3db5..ba98d0e3a 100644 --- a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 +++ b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 @@ -32,7 +32,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ {{ arg }} \ {% endfor %} {{ matrix_rageshake_container_image }} \ - --config /config/config.yml + --config /config/config.yaml {% for network in matrix_rageshake_container_additional_networks %} ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-rageshake From fd2428972ded775a5c6dcfe227c9b937fdf22932 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:33:26 +0900 Subject: [PATCH 449/952] Update docs/configuring-playbook-rageshake.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-rageshake.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index aa61314f0..e52c8cdef 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -80,3 +80,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Usage Refer to the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) for available APIs, etc. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-rageshake`. From 0980339e70f4380ba3482ae7f51ae1b6a42e5045 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 11:49:36 -0500 Subject: [PATCH 450/952] Update docs/configuring-playbook-bot-matrix-registration-bot.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-matrix-registration-bot.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 95b86163f..a425b5969 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -29,6 +29,15 @@ matrix_synapse_registration_requires_token: true The bot account will be created automatically. +### Extending the configuration + +There are some additional things you may wish to configure about the bot. + +Take a look at: + +- `roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +- `roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2` for the bridge's default configuration + ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: From 66df132e666186f1782a441bf9135339102a3992 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 00:41:38 +0900 Subject: [PATCH 451/952] =?UTF-8?q?Update=20files=20for=20matrix-registrat?= =?UTF-8?q?ion-bot:=20change=20config.yml.j2=20=E2=86=92=20config.yaml.j2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Suguru Hirahara --- .../tasks/setup_install.yml | 4 ++-- .../templates/{config.yml.j2 => config.yaml.j2} | 0 .../systemd/matrix-bot-matrix-registration-bot.service.j2 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) rename roles/custom/matrix-bot-matrix-registration-bot/templates/{config.yml.j2 => config.yaml.j2} (100%) diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml index 0ac4e6a1f..a05c04109 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml @@ -15,8 +15,8 @@ - name: Ensure matrix-registration-bot configuration file created ansible.builtin.template: - src: "{{ role_path }}/templates/config.yml.j2" - dest: "{{ matrix_bot_matrix_registration_bot_config_path }}/config.yml" + src: "{{ role_path }}/templates/config.yaml.j2" + dest: "{{ matrix_bot_matrix_registration_bot_config_path }}/config.yaml" owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" mode: 0640 diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2 rename to roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 index a48c4f045..d12d2f588 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 +++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 @@ -21,7 +21,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --name=matrix-bot-matrix-registration-bot \ --log-driver=none \ --cap-drop=ALL \ - -e "CONFIG_PATH=/config/config.yml" \ + -e "CONFIG_PATH=/config/config.yaml" \ --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ --read-only \ --mount type=bind,src={{ matrix_bot_matrix_registration_bot_config_path }},dst=/config,ro \ From f732007b376fff9b8797617644dd85182d8cb330 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 00:08:22 +0900 Subject: [PATCH 452/952] Update files for matrix-registration-bot: add the common section for "Troubleshooting" See: https://github.com/moan0s/matrix-registration-bot/blob/main/README.md Signed-off-by: Suguru Hirahara --- ...figuring-playbook-bot-matrix-registration-bot.md | 13 +++++++++++++ .../defaults/main.yml | 3 ++- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index a425b5969..fffd239f2 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -72,3 +72,16 @@ To clean the cache (session & encryption data) after you changed the bot's usern ```sh just run-tags bot-matrix-registration-bot-clean-cache ``` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-registration-bot`. + +### Increase logging verbosity + +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: + +```yaml +# Valid values: ERROR, INFO, DEBUG +matrix_bot_matrix_registration_bot_logging_level: DEBUG +``` diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index ba1fc7273..9423e8fad 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -39,7 +39,8 @@ matrix_bot_matrix_registration_bot_api_token: '' matrix_bot_matrix_registration_bot_device_id: "matrix-docker-ansible-deploy" -matrix_bot_matrix_registration_bot_logging_level: info +# Valid values: ERROR, INFO, DEBUG +matrix_bot_matrix_registration_bot_logging_level: INFO matrix_bot_matrix_registration_bot_container_network: "" From 30dad8ba277bc32494125b70794e2d0df5ac08ae Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 00:40:58 +0900 Subject: [PATCH 453/952] =?UTF-8?q?Updat=20files=20for=20baibot:=20change?= =?UTF-8?q?=20config.yml.j2=20=E2=86=92=20config.yaml.j2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-baibot/defaults/main.yml | 2 +- roles/custom/matrix-bot-baibot/tasks/install.yml | 2 +- .../templates/{config.yml.j2 => config.yaml.j2} | 0 .../templates/systemd/matrix-bot-baibot.service.j2 | 2 +- 4 files changed, 3 insertions(+), 3 deletions(-) rename roles/custom/matrix-bot-baibot/templates/{config.yml.j2 => config.yaml.j2} (100%) diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index fba1cd908..d3737b2a8 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -461,7 +461,7 @@ matrix_bot_baibot_configuration: "{{ matrix_bot_baibot_configuration_yaml | from # # For a more advanced customization, you can extend the default (see `matrix_bot_baibot_configuration_extension_yaml`) # or completely replace this variable with your own template. -matrix_bot_baibot_configuration_yaml: "{{ lookup('template', 'templates/config.yml.j2') }}" +matrix_bot_baibot_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" matrix_bot_baibot_configuration_extension_yaml: | # Your custom YAML configuration for baibot goes here. diff --git a/roles/custom/matrix-bot-baibot/tasks/install.yml b/roles/custom/matrix-bot-baibot/tasks/install.yml index f74ab3442..d2dcfdb6d 100644 --- a/roles/custom/matrix-bot-baibot/tasks/install.yml +++ b/roles/custom/matrix-bot-baibot/tasks/install.yml @@ -17,7 +17,7 @@ - name: Ensure baibot configuration installed ansible.builtin.copy: content: "{{ matrix_bot_baibot_configuration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_bot_baibot_config_path }}/config.yml" + dest: "{{ matrix_bot_baibot_config_path }}/config.yaml" mode: 0644 owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" diff --git a/roles/custom/matrix-bot-baibot/templates/config.yml.j2 b/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 similarity index 100% rename from roles/custom/matrix-bot-baibot/templates/config.yml.j2 rename to roles/custom/matrix-bot-baibot/templates/config.yaml.j2 diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 index 346925c4a..e34f62357 100644 --- a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 @@ -29,7 +29,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --read-only \ --network={{ matrix_bot_baibot_container_network }} \ --env-file={{ matrix_bot_baibot_config_path }}/env \ - --mount type=bind,src={{ matrix_bot_baibot_config_path }}/config.yml,dst=/app/config.yml,ro \ + --mount type=bind,src={{ matrix_bot_baibot_config_path }}/config.yaml,dst=/app/config.yaml,ro \ --mount type=bind,src={{ matrix_bot_baibot_data_path }},dst=/data \ --tmpfs=/tmp:rw,noexec,nosuid,size=1024m \ {% for arg in matrix_bot_baibot_container_extra_arguments %} From 589aa949f4dc9edcec80683d701d6f2abb0bdcf8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 19:38:21 +0900 Subject: [PATCH 454/952] Update docs/configuring-playbook-bot-baibot.md: adopt the common description for the section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index ac270d3a3..a9c3d2c66 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -398,7 +398,7 @@ You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) pr ## Troubleshooting -As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot` +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-baibot`. ### Increase logging verbosity From bad9785103573e01aec6b56660fb5c07cd60b4fc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:24:12 +0900 Subject: [PATCH 455/952] Update docs/configuring-playbook-etherpad.md: add the common section "Troubleshooting" See: https://etherpad.org/doc/v2.2.7/index.html Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 65f11b9b4..f6664f19d 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -105,3 +105,19 @@ Once the plugin is installed, you should have a "Manage pads" section in the UI. **Note**: this is how it works in Element Web. It might work quite similar with other clients: To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-etherpad`. + +### Increase logging verbosity + +The default logging level for this component is `WARN`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: ERROR, WARN, INFO, DEBUG +etherpad_configuration_extension_json: | + { + "loglevel": "DEBUG", + } +``` From dd4690fba40fbda3108b25c0304eb2b0f43ef78d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:54:50 +0900 Subject: [PATCH 456/952] Update docs/configuring-playbook-dimension.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 6a662e87c..5bc709c12 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -123,3 +123,7 @@ By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `co 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. 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-dimension`. From 271f386d1b659a9b6528621b81ad9724f060e7a5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 18:42:53 +0900 Subject: [PATCH 457/952] Update docs/configuring-playbook-turn.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-turn.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index a0915312d..611037415 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -94,3 +94,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. From 76f35d95a24563f67eb62590d523001bf3784358 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 00:46:12 +0900 Subject: [PATCH 458/952] Update docs/configuring-playbook-bridge-postmoogle.md: adopt the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-postmoogle.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index 18321207e..eff5b62e3 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -92,9 +92,11 @@ You can also refer to the upstream [documentation](https://github.com/etkecc/pos ## Troubleshooting -As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle` +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-postmoogle`. -The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration: +### Increase logging verbosity + +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: ```yaml matrix_postmoogle_loglevel: 'DEBUG' From cf8e5f8e0a16f7ea0af5e8f4da910d5a2f283361 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 00:47:41 +0900 Subject: [PATCH 459/952] Update docs/configuring-playbook-conduwuit.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-conduwuit.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md index a2ea0c925..b198dd814 100644 --- a/docs/configuring-playbook-conduwuit.md +++ b/docs/configuring-playbook-conduwuit.md @@ -91,3 +91,7 @@ Then, send its content to the existing admin room: sender_localpart: _bot_signalbot url: http://matrix-mautrix-signal:29328 ``` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-conduwuit`. From b0e67c365baf4f1f0ed0e9fe2b24786d28852abd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 02:23:36 +0900 Subject: [PATCH 460/952] Update docs/configuring-playbook-bridge-appservice-kakaotalk.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bridge-appservice-kakaotalk.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index 9b029e194..c8fbb12fc 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -56,3 +56,15 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use 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). 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-appservice-kakaotalk`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_appservice_kakaotalk_logging_level: DEBUG +``` From f920bf2cba8ffa9bf949d252173b3058e15c7783 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 02:29:35 +0900 Subject: [PATCH 461/952] Update docs/configuring-playbook-bridge-beeper-linkedin.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-beeper-linkedin.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 73059ce64..995ea6faa 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -55,6 +55,16 @@ You then need to send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to e ## Troubleshooting +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-beeper-linkedin`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_beeper_linkedin_logging_level: DEBUG +``` + ### Bridge asking for 2FA even if you don't have 2FA enabled 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. From 4a178b534bbd6693a9da38863e14463bf6732adf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 02:37:32 +0900 Subject: [PATCH 462/952] Update docs/configuring-playbook-sliding-sync-proxy.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sliding-sync-proxy.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 406dc6196..3f74c45ef 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -68,3 +68,7 @@ You **don't need to do anything special** to make use of the Sliding Sync proxy. 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`). This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-sliding-sync-proxy`. From 056a502d5fab525dc58aa75072b7ee25f31e59e7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 6 Feb 2025 23:22:28 +0900 Subject: [PATCH 463/952] Update files for Sliding Sync proxy: change "matrix-sliding-sync-proxy" to "matrix-sliding-sync" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sliding-sync-proxy.md | 2 +- roles/custom/matrix-sliding-sync/defaults/main.yml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 3f74c45ef..72da17ed3 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -71,4 +71,4 @@ This allows clients which support Sliding Sync to detect the Sliding Sync proxy' ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-sliding-sync-proxy`. +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-sliding-sync`. diff --git a/roles/custom/matrix-sliding-sync/defaults/main.yml b/roles/custom/matrix-sliding-sync/defaults/main.yml index adc6312ac..d8fbdff7c 100644 --- a/roles/custom/matrix-sliding-sync/defaults/main.yml +++ b/roles/custom/matrix-sliding-sync/defaults/main.yml @@ -93,13 +93,13 @@ matrix_sliding_sync_container_labels_additional_labels: '' # A list of extra arguments to pass to the container matrix_sliding_sync_container_extra_arguments: [] -# List of systemd services that matrix-sliding-sync-proxy.service depends on +# List of systemd services that matrix-sliding-sync.service depends on matrix_sliding_sync_systemd_required_services_list: "{{ matrix_sliding_sync_systemd_required_services_list_default + matrix_sliding_sync_systemd_required_services_list_auto + matrix_sliding_sync_systemd_required_services_list_custom }}" matrix_sliding_sync_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" matrix_sliding_sync_systemd_required_services_list_auto: [] matrix_sliding_sync_systemd_required_services_list_custom: [] -# List of systemd services that matrix-sliding-sync-proxy.service wants +# List of systemd services that matrix-sliding-sync.service wants matrix_sliding_sync_systemd_wanted_services_list: [] # Controls the SYNCV3_SERVER environment variable From 6531c61c7a865c0867b1a5033bbd931c02534ccf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 15:34:46 +0900 Subject: [PATCH 464/952] Update files for matrix-coturn: make the reloading schedule configurable with variables This commit adopts the common format which can be seen for BorgBackup. It should be probably helpful, though I am not quite sure how much. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-turn.md | 12 ++++++++++++ roles/custom/matrix-coturn/defaults/main.yml | 6 ++++++ .../templates/systemd/matrix-coturn-reload.timer.j2 | 4 ++-- 3 files changed, 20 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index 611037415..56858d886 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -64,6 +64,18 @@ jitsi_web_stun_servers: You can put multiple host/port combinations if you'd like to. +### Edit the reloading schedule (optional) + +By default the service is reloaded on 6:30 a.m. every day based on the `matrix_coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar. + +To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): + +```yaml +matrix_coturn_reload_schedule: "*-*-* 06:30:00" +``` + +**Note**: the actual job may run with a delay. See `matrix_coturn_reload_schedule_randomized_delay_sec` for its default value. + ### Extending the configuration There are some additional things you may wish to configure about the TURN server. diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index bda15196a..60641c196 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -186,3 +186,9 @@ matrix_coturn_tls_key_path: ~ matrix_coturn_tls_v1_enabled: false matrix_coturn_tls_v1_1_enabled: false + +# systemd calendar configuration for the reload job +# the actual job may run with a delay (see matrix_coturn_reload_schedule_randomized_delay_sec) +matrix_coturn_reload_schedule: "*-*-* 06:30:00" +# the delay with which the systemd timer may run in relation to the `matrix_coturn_reload_schedule` schedule +matrix_coturn_reload_schedule_randomized_delay_sec: 1h diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 index 528945412..d4b0b1093 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 @@ -3,8 +3,8 @@ Description=Reloads matrix-coturn periodically so that new SSL certificates can [Timer] Unit=matrix-coturn-reload.service -OnCalendar=*-*-* 06:30:00 -RandomizedDelaySec=1h +OnCalendar={{ matrix_coturn_reload_schedule }} +RandomizedDelaySec={{ matrix_coturn_reload_schedule_randomized_delay_sec }} [Install] WantedBy=timers.target From 2e986012c42aef8b375d9438ade3ac4836cd4c44 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 01:11:57 +0900 Subject: [PATCH 465/952] Update docs/configuring-playbook-synapse-s3-storage-provider.md: add the instruction to edit the schedule Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-s3-storage-provider.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index c564e4c83..efe3a5a82 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -152,3 +152,9 @@ By default, we periodically ensure that all local files are uploaded to S3 and a - … triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00 So… you don't need to perform any maintenance yourself. + +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): + +```yaml +matrix_synapse_ext_synapse_s3_storage_provider_periodic_migration_schedule: "*-*-* 05:00:00" +``` From bab827c62c2f60d4d5f71e6285d8ec56efb6b71c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 28 Dec 2024 09:11:35 -0500 Subject: [PATCH 466/952] Update docs/configuring-playbook-sliding-sync-proxy.md: add the common section "Extending the configuration" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sliding-sync-proxy.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 72da17ed3..0e72bffaa 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -36,6 +36,14 @@ If you've changed the default hostname, you may need to create a CNAME record fo When setting, replace `example.com` with your own. +### Extending the configuration + +There are some additional things you may wish to configure about the component. + +Take a look at: + +- `roles/custom/matrix-sliding-sync/defaults/main.yml` for some variables that you can customize via your `vars.yml` file + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 049769514d8d0727a3bf1ccf41b85d90e00d64df Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 19 Jan 2025 01:11:41 +0900 Subject: [PATCH 467/952] Update docs/configuring-playbook-prometheus-grafana.md: add the common section "Extending the configuration" for Prometheus Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 001500c59..89530058e 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -53,6 +53,14 @@ After changing the domain, **you may need to adjust your DNS** records to point **Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. +### Extending the configuration + +There are some additional things you may wish to configure about Prometheus. + +Take a look at: + +- [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 + ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 8592e5a185739786274898d20cf4221580d9a8fb Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 6 Feb 2025 22:05:11 +0000 Subject: [PATCH 468/952] Update dependency docker to v7.4.5 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index f5097355a..3f6fea07a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -10,7 +10,7 @@ version: v0.2.0-0 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker - version: 7.4.4 + version: 7.4.5 name: docker - src: git+https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python.git version: 129c8590e106b83e6f4c259649a613c6279e937a From da398b4ba5695205d9d0bf1f434d9cfa7c02313a Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 7 Feb 2025 08:29:14 +0200 Subject: [PATCH 469/952] Use `config.yml` on the server for baibot Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4039 Partially reverts 30dad8ba277bc32494125b70794e2d0df5ac08ae which renamed `config.yml` to `config.yaml` in the playbook and on the server, for consistency with the rest of the playbook. The problem is that: - baibot defaults to looking for `config.yml`, not `config.yaml` (as provided). This can be worked around by specifying a new `BAIBOT_CONFIG_FILE_PATH=config.yaml` environment variable. This brings more complexity. - renaming the target file (on the server) to `config.yaml` means people with an existing installation would drag around the old file (`config.yml`) as well, unless we create a new Ansible task (`ansible.builtin.file` with `state: absent`) to remove the old file. This brings more complexity as well. https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4039 adjusts where the file is mounted, which fixes the immediate problem (baibot not starting), but still means people will end up with 2 config files for baibot (`config.yml` and `config.yaml`). This patch, reverts a bit more, so that we still continue to use `config.yml` on the server. People who have upgraded within the last ~17 hours may end up with 2 files, but it shouldn't be too many of them. --- roles/custom/matrix-bot-baibot/tasks/install.yml | 2 +- .../templates/systemd/matrix-bot-baibot.service.j2 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-bot-baibot/tasks/install.yml b/roles/custom/matrix-bot-baibot/tasks/install.yml index d2dcfdb6d..f74ab3442 100644 --- a/roles/custom/matrix-bot-baibot/tasks/install.yml +++ b/roles/custom/matrix-bot-baibot/tasks/install.yml @@ -17,7 +17,7 @@ - name: Ensure baibot configuration installed ansible.builtin.copy: content: "{{ matrix_bot_baibot_configuration | to_nice_yaml(indent=2, width=999999) }}" - dest: "{{ matrix_bot_baibot_config_path }}/config.yaml" + dest: "{{ matrix_bot_baibot_config_path }}/config.yml" mode: 0644 owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 index e34f62357..346925c4a 100644 --- a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 @@ -29,7 +29,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --read-only \ --network={{ matrix_bot_baibot_container_network }} \ --env-file={{ matrix_bot_baibot_config_path }}/env \ - --mount type=bind,src={{ matrix_bot_baibot_config_path }}/config.yaml,dst=/app/config.yaml,ro \ + --mount type=bind,src={{ matrix_bot_baibot_config_path }}/config.yml,dst=/app/config.yml,ro \ --mount type=bind,src={{ matrix_bot_baibot_data_path }},dst=/data \ --tmpfs=/tmp:rw,noexec,nosuid,size=1024m \ {% for arg in matrix_bot_baibot_container_extra_arguments %} From e4e34333daf87b9be3137a25961477ff908e2960 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 15:15:12 +0900 Subject: [PATCH 470/952] Update files for some mautrix bridges: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-discord.md | 13 +++++++++++++ ...configuring-playbook-bridge-mautrix-gmessages.md | 13 +++++++++++++ docs/configuring-playbook-bridge-mautrix-signal.md | 13 +++++++++++++ docs/configuring-playbook-bridge-mautrix-slack.md | 13 +++++++++++++ docs/configuring-playbook-bridge-mautrix-twitter.md | 13 +++++++++++++ .../configuring-playbook-bridge-mautrix-whatsapp.md | 13 +++++++++++++ .../matrix-bridge-mautrix-discord/defaults/main.yml | 2 +- .../defaults/main.yml | 2 +- .../matrix-bridge-mautrix-signal/defaults/main.yml | 2 +- .../matrix-bridge-mautrix-slack/defaults/main.yml | 2 +- .../matrix-bridge-mautrix-twitter/defaults/main.yml | 2 +- .../defaults/main.yml | 2 +- 12 files changed, 84 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index d5e6b4834..0a8c743bb 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -71,3 +71,16 @@ If you'd like to bridge guilds, send `guilds status` to see the list of guilds, 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. 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_discord_logging_level: 'debug' +``` diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index eae32a1f7..658b8eb95 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -53,3 +53,16 @@ To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (wh You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html). After logging in, the bridge will create portal rooms for recent chats. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-gmessages`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_gmessages_logging_level: 'debug' +``` diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index f0f1ccf74..d156c7b0a 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -60,3 +60,16 @@ You can then follow instructions on the bridge's [official documentation on Auth After logging in, the bridge will bridge chats as you receive messages. **Note**: Signal does not support any kind of message history (even on official apps), so the bridge won't backfill any messages. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-signal`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_signal_logging_level: 'debug' +``` diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index b113f52f0..6ead5487d 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -63,3 +63,16 @@ To use the bridge, you need to start a chat with `@slackbot:example.com` (where You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html). If you authenticated using a token, the recent chats will be bridged automatically (depending on the `conversation_count` setting). Otherwise (i.e. logging with the Discord application), the chats the bot is in will be bridged automatically. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-slack`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_slack_logging_level: 'debug' +``` diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index bb25019fe..b24264a6c 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -55,3 +55,16 @@ To use the bridge, you need to start a chat with `@twitterbot:example.com` (wher You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html). 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-twitter`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_twitter_logging_level: 'debug' +``` diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index 8201be513..b9d23652e 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -56,3 +56,16 @@ You can then follow instructions on the bridge's [official documentation on Auth Approximately in a minute after logging in, the bridge will create portal rooms for recent chats. **Note**: your linked devices will be logged out if you don’t use your phone for over 14 days (see the official FAQ entry [here](https://faq.whatsapp.com/general/download-and-installation/about-linked-devices)). The bridge will warn you if it doesn't receive any data from the phone over 12 days. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-whatsapp`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_whatsapp_logging_level: 'debug' +``` diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index 779816b68..63a40c07f 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -118,7 +118,7 @@ matrix_mautrix_discord_appservice_bot_avatar: mxc://maunium.net/nIdEykemnwdisvHb matrix_mautrix_discord_provisioning_shared_secret: disable # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_discord_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml index 2cde7487f..c2409ec61 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml @@ -86,7 +86,7 @@ matrix_mautrix_gmessages_homeserver_token: '' matrix_mautrix_gmessages_appservice_bot_username: gmessagesbot # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_gmessages_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index b1aecf902..f4e754a41 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -93,7 +93,7 @@ matrix_mautrix_signal_homeserver_token: '' matrix_mautrix_signal_appservice_bot_username: signalbot # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_signal_logging_level: 'warn' # Whether or not created rooms should have federation enabled. diff --git a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml index 9b95d069f..bf5ed4bd0 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml @@ -62,7 +62,7 @@ matrix_mautrix_slack_backfill_unread_hours_threshold: 720 matrix_mautrix_slack_backfill_threads_max_initial_messages: 50 # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_slack_logging_level: 'warn' # Database-related configuration fields. diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml index 8a2fb4200..e79db967c 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml @@ -130,7 +130,7 @@ matrix_mautrix_twitter_backfill_max_catchup_messages: 500 matrix_mautrix_twitter_provisioning_shared_secret: disable # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_twitter_logging_level: 'warn' # Whether or not metrics endpoint should be enabled. diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml index 2d2519338..88b40dd81 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml @@ -82,7 +82,7 @@ matrix_mautrix_whatsapp_homeserver_token: '' matrix_mautrix_whatsapp_appservice_bot_username: whatsappbot # Minimum severity of journal log messages. -# Options: trace, debug, info, warn, error, fatal +# Valid values: fatal, error, warn, info, debug, trace matrix_mautrix_whatsapp_logging_level: 'warn' # Whether or not created rooms should have federation enabled. From c69892ec1f3bfb203c750e5e0b6992950de822f4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 18:54:43 +0900 Subject: [PATCH 471/952] Update docs/configuring-playbook-bridge-mautrix-wsproxy.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-wsproxy.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index fb2005c6d..b761e71d9 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -67,3 +67,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use ## Usage 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). + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-wsproxy`. From c9ae1efa07053205f3f714042a682d736a5eb566 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 19:03:34 +0900 Subject: [PATCH 472/952] Update docs for Meta Instagram and Messenger: add the common section "Troubleshooting" The comments are copied from the configuration files. Signed-off-by: Suguru Hirahara --- ...guring-playbook-bridge-mautrix-meta-instagram.md | 13 +++++++++++++ ...guring-playbook-bridge-mautrix-meta-messenger.md | 13 +++++++++++++ 2 files changed, 26 insertions(+) diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index d89c1d50c..26c34f8d9 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -69,3 +69,16 @@ To use the bridge, you need to start a chat with `@instagrambot:example.com` (wh You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html). After logging in, the bridge will sync recent chats. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-meta-instagram`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# This bridge uses zerolog, so valid levels are: panic, fatal, error, warn, info, debug, trace +matrix_mautrix_meta_instagram_logging_min_level: debug +``` diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 96041c829..51b1a40ca 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -84,3 +84,16 @@ You can then follow instructions on the bridge's [official documentation on Auth After logging in, the bridge will sync recent chats. **Note**: given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-meta-messenger`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# This bridge uses zerolog, so valid levels are: panic, fatal, error, warn, info, debug, trace +matrix_mautrix_meta_messenger_logging_min_level: debug +``` From 145d2cc6758d15fb61753c2206471b653e831ec1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Feb 2025 19:04:20 +0900 Subject: [PATCH 473/952] Update docs for the other mautrix bridges: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-facebook.md | 10 ++++++++++ ...configuring-playbook-bridge-mautrix-googlechat.md | 12 ++++++++++++ .../configuring-playbook-bridge-mautrix-instagram.md | 12 ++++++++++++ docs/configuring-playbook-bridge-mautrix-telegram.md | 12 ++++++++++++ 4 files changed, 46 insertions(+) diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 51a162caf..67d2b3d9b 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -59,6 +59,16 @@ If you run into trouble, check the [Troubleshooting](#troubleshooting) section b ## Troubleshooting +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-facebook`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_mautrix_facebook_logging_level: DEBUG +``` + ### Facebook rejecting login attempts and forcing you to change password 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. diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index 4dbde4dd8..a2e3dff61 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -55,3 +55,15 @@ To use the bridge, you need to start a chat with `@googlechatbot:example.com` (w You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html). 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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-googlechat`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_mautrix_googlechat_logging_level: DEBUG +``` diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 99988df41..4bacb9ebd 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -44,3 +44,15 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). You then need to send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-instagram`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_mautrix_instagram_logging_level: DEBUG +``` diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index f3deabc77..77f92a1dc 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -93,3 +93,15 @@ To use the bridge, you need to start a chat with `@telegrambot:example.com` (whe You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html). After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them. Note that the bridge won't automatically create rooms for private chats. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-telegram`. + +### Increase logging verbosity + +The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +matrix_mautrix_telegram_logging_level: DEBUG +``` From 63a6d7e73ae0fbeb8a13268f07e91bfab1c371dc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:03:38 +0900 Subject: [PATCH 474/952] Update docs/configuring-playbook-prometheus-grafana.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 89530058e..013fa8869 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -155,6 +155,12 @@ scrape_configs: index: 18111 ``` +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running the commands below: +- `journalctl -fu matrix-prometheus` for Prometheus +- `journalctl -fu matrix-grafana` for Grafana + ## More information - [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) From 4e977bd3b2c75005ad9356c7fc6354f48971e9c6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:07:00 +0900 Subject: [PATCH 475/952] Update docs/configuring-playbook-bot-matrix-registration-bot.md: fix the service name Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-matrix-registration-bot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index fffd239f2..96c9dd54a 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -75,7 +75,7 @@ just run-tags bot-matrix-registration-bot-clean-cache ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-registration-bot`. +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-matrix-registration-bot`. ### Increase logging verbosity From 7f8f241e81842725a6b95e21747811bd61c37f07 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:09:26 +0900 Subject: [PATCH 476/952] Update docs/configuring-playbook-bridge-appservice-webhooks.md: remove the duplicated instruction in favor of the dedicated section below Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-webhooks.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index c57e1239f..1fbecfdb1 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -14,9 +14,6 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_appservice_webhooks_enabled: true matrix_appservice_webhooks_api_secret: '' -# Uncomment to increase the verbosity of logging via `journalctl -fu matrix-appservice-webhooks.service` -# matrix_appservice_webhooks_log_level: 'verbose' - # As of Synapse 1.90.0, uncomment to enable the backwards compatibility (https://matrix-org.github.io/synapse/latest/upgrade#upgrading-to-v1900) that this bridge needs. # Note: This deprecated method is considered insecure. # From 596136412574f5b58909cb9fabef8632f9ea6287 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:11:09 +0900 Subject: [PATCH 477/952] Update docs/configuring-playbook-bridge-wechat.md: fix the service name Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-wechat.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index b42388bb7..0ae3fe21f 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -47,7 +47,7 @@ Send `help` to the bot to see the available commands. ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bridge-wechat`. +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`. ### Increase logging verbosity From ddeae3c1c4f1ab5c7a801d5eef8a774587baa492 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:12:27 +0900 Subject: [PATCH 478/952] Update docs/configuring-playbook-bridge-hookshot.md: fix the service name Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 13c6eb6f3..4ed8d2186 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -146,7 +146,7 @@ If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bridge-hookshot`. +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`. ### Increase logging verbosity From eff8c8e4b34dd091b7c3ded838b6324c33eaf3aa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:21:43 +0900 Subject: [PATCH 479/952] Update docs/configuring-playbook-jitsi.md: adopt the common instruction for troubleshooting Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 9e976b691..48c7516c7 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -382,6 +382,12 @@ ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --ta ## Troubleshooting +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running the commands below: +- `journalctl -fu matrix-jitsi-web` +- `journalctl -fu matrix-jitsi-prosody` +- `journalctl -fu matrix-jitsi-jicofo` +- `journalctl -fu matrix-jitsi-jvb` + ### `Error: Account creation/modification not supported` If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support. From b72de6995d88ef4ecbbff8d11f8dacc29ee30896 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:24:56 +0900 Subject: [PATCH 480/952] Update docs/configuring-playbook-postgres-backup.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-postgres-backup.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 165609d0c..08f88b8bf 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -36,3 +36,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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-postgres-backup`. From 1bccda962905a87bbd72adcc046221e468e9ce20 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 16:32:30 +0900 Subject: [PATCH 481/952] Update docs/configuring-playbook-s3-goofys.md: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3-goofys.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-s3-goofys.md b/docs/configuring-playbook-s3-goofys.md index 720c7d8b2..2efdac86e 100644 --- a/docs/configuring-playbook-s3-goofys.md +++ b/docs/configuring-playbook-s3-goofys.md @@ -124,3 +124,7 @@ After making the backup, follow one of the guides below for a migration path fro 7. You're done! Verify that loading existing (old) media files works and that you can upload new ones. 8. When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup` + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-goofys`. From 9a287d04eea8a360099fbd9243192723b5c45dda Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 31 Jan 2025 03:05:36 +0900 Subject: [PATCH 482/952] Update docs/configuring-playbook-matrix-corporal.md: remove the hr HTML elements used for styling Now that the warning message is styled with the fancy decoration, it is no longer to wrap them with the hr HTML elements as they are redundant. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-corporal.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 1e387e046..946a0209d 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -1,12 +1,8 @@ # Setting up Matrix Corporal (optional, advanced) -
- > [!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. -
- The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you. In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment. From 331fe31ecf5aad9bfb8fdc5515679fabf005f9cf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 29 Dec 2024 13:07:24 -0500 Subject: [PATCH 483/952] Update docs/configuring-playbook-bridge-matrix-bridge-sms.md: remove a blank line Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-matrix-bridge-sms.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index 5ea15577d..c580f26c5 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -30,7 +30,6 @@ matrix_sms_bridge_provider_android_password: supeSecretPassword # (optional) if your android-sms-gateway-server uses a self signed vertificate, the bridge needs a "truststore". This can be the certificate itself. matrix_sms_bridge_provider_android_truststore_local_path: android-sms-gateway-server.p12 matrix_sms_bridge_provider_android_truststore_password: 123 - ``` ### Extending the configuration From 47525903b03f08cb4862d303983677558cd2604f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 26 Jan 2025 20:12:44 +0900 Subject: [PATCH 484/952] Update docs/configuring-playbook-s3.md: make the loose list tight Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md index 2f6f1ad49..3679b6add 100644 --- a/docs/configuring-playbook-s3.md +++ b/docs/configuring-playbook-s3.md @@ -84,9 +84,7 @@ The `keyID` value is your **Access Key** and `applicationKey` is your **Secret K For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need: - **Endpoint URL** — this is the **Endpoint** value you saw above, but prefixed with `https://` - - **Region** — use the value you see in the Endpoint (e.g. `us-west-002`) - - **Storage Class** — use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value. ## Other providers From e356f404ad5107704a08ea5cff171d8242116332 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 01:12:38 +0900 Subject: [PATCH 485/952] Update docs/maintenance-synapse.md: make the loose list tight Signed-off-by: Suguru Hirahara --- docs/maintenance-synapse.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index cd8f11697..e7cb17c9d 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -3,13 +3,9 @@ This document shows you how to perform various maintenance tasks related to the Synapse chat server. Table of contents: - - [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 - - [Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state) - - [Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands - - [Make Synapse faster](#make-synapse-faster) 💡 See this page for details about configuring Synapse: [Configuring Synapse](configuring-playbook-synapse.md) From 522c59038e72fa5a3071a4b34a11b16c9c1bac20 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 23:12:05 +0900 Subject: [PATCH 486/952] Update examples/reverse-proxies/nginx/matrix.conf: fix capitalization Signed-off-by: Suguru Hirahara --- examples/reverse-proxies/nginx/matrix.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/reverse-proxies/nginx/matrix.conf b/examples/reverse-proxies/nginx/matrix.conf index 0919011ef..7d2459543 100644 --- a/examples/reverse-proxies/nginx/matrix.conf +++ b/examples/reverse-proxies/nginx/matrix.conf @@ -11,9 +11,9 @@ server { http3 on; # TODO: add/remove services and their subdomains if you use/don't use them - # this example is using hosting something on the base domain and an element web client, so example.com and element.example.com are listed in addition to matrix.example.com + # this example is using hosting something on the base domain and an Element Web client, so example.com and element.example.com are listed in addition to matrix.example.com # if you don't use those, you can remove them - # if you use e.g. dimension on dimension.example.com, add dimension.example.com to the server_name list + # if you use e.g. Dimension on dimension.example.com, add dimension.example.com to the server_name list server_name example.com matrix.example.com element.example.com; location / { From 298bc21d5452264820b76d013fc5e3740354bf13 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 23:12:34 +0900 Subject: [PATCH 487/952] Update roles/custom/matrix-bridge-hookshot/defaults/main.yml: fix capitalization Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 4de899ca9..f4538e143 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -178,7 +178,7 @@ matrix_hookshot_provisioning_enabled: false # There is no need to edit ports. use matrix_hookshot_container_http_host_bind_ports below to expose ports instead. matrix_hookshot_provisioning_port: 9002 matrix_hookshot_provisioning_secret: '' -# Provisioning will be automatically enabled if dimension is enabled and you have provided a provisioning secret, unless you override it +# Provisioning will be automatically enabled if Dimension is enabled and you have provided a provisioning secret, unless you override it matrix_hookshot_provisioning_internal: "/v1" matrix_hookshot_provisioning_hostname: "{{ matrix_hookshot_public_hostname }}" matrix_hookshot_provisioning_endpoint: "{{ matrix_hookshot_public_endpoint }}{{ matrix_hookshot_provisioning_internal }}" From c202091063eb8d6f5c5d173f7a2bac2b51f3856a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 24 Jan 2025 23:13:11 +0900 Subject: [PATCH 488/952] Update roles/custom/matrix-dimension/tasks/setup_install.yml: fix capitalization Signed-off-by: Suguru Hirahara --- roles/custom/matrix-dimension/tasks/setup_install.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-dimension/tasks/setup_install.yml b/roles/custom/matrix-dimension/tasks/setup_install.yml index ce7080c52..1c4c4827f 100644 --- a/roles/custom/matrix-dimension/tasks/setup_install.yml +++ b/roles/custom/matrix-dimension/tasks/setup_install.yml @@ -105,7 +105,7 @@ delay: "{{ devture_playbook_help_container_retries_delay }}" until: matrix_dimension_pull_results is not failed -- name: Ensure dimension repository is present on self-build +- name: Ensure Dimension repository is present on self-build ansible.builtin.git: repo: "{{ matrix_dimension_container_image_self_build_repo }}" dest: "{{ matrix_dimension_docker_src_files_path }}" From b72aec0c18783943ef7549ad0909b1168dd54bf8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 7 Feb 2025 17:39:26 +0900 Subject: [PATCH 489/952] Update docs/configuring-playbook-bridge-hookshot.md: fix capitalization Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 4ed8d2186..514f6b888 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -125,7 +125,7 @@ For more information, see the documentation in the [default configuration of the ### Provisioning API -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`. +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`. ### Metrics From 6b5275519202e0855b6f1576329a6d0004fd5ac0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 30 Jan 2025 15:27:49 +0900 Subject: [PATCH 490/952] Update files for Pantalaimon: adopt the common description for logging verbosity Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-pantalaimon.md | 2 +- roles/custom/matrix-pantalaimon/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index fb34c7b5c..4341a07f4 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -42,6 +42,6 @@ As with all other services, you can find the logs in [systemd-journald](https:// 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: ```yaml -# Pantalaimon log level, case-insensitive (Error, Warning, Info, Debug) +# Valid values: Error, Warning, Info, Debug matrix_pantalaimon_log_level: Debug ``` diff --git a/roles/custom/matrix-pantalaimon/defaults/main.yml b/roles/custom/matrix-pantalaimon/defaults/main.yml index 8746519d3..977f53d0a 100644 --- a/roles/custom/matrix-pantalaimon/defaults/main.yml +++ b/roles/custom/matrix-pantalaimon/defaults/main.yml @@ -42,7 +42,7 @@ matrix_pantalaimon_systemd_wanted_services_list_default: [] matrix_pantalaimon_systemd_wanted_services_list_auto: [] matrix_pantalaimon_systemd_wanted_services_list_custom: [] -# Pantalaimon log level, case-insensitive (Error, Warning, Info, Debug) +# Valid values: Error, Warning, Info, Debug matrix_pantalaimon_log_level: Warning # Base URL where matrix-pantalaimon can reach your homeserver C-S API. From cfe5010773246462524b8e640b8b08ae1aed6ef3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 03:47:22 +0900 Subject: [PATCH 491/952] Update docs/configuring-playbook-synapse-usage-exporter.md: add the section "What does it do?" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-usage-exporter.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 3eb98921f..6c3e9629d 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -6,6 +6,10 @@ It allows you to export the usage statistics of a Synapse homeserver to this con 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. +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. + +## What does it do? + Enabling this service will automatically: - install the synapse-usage-exporter service @@ -13,8 +17,6 @@ Enabling this service will automatically: - re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter - add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics -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. - ## Adjusting DNS records (optional) By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section. From 1ddab522946c51e3474c37fc184f60016b635de6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Feb 2025 02:03:43 +0900 Subject: [PATCH 492/952] Update docs/configuring-playbook-prometheus-grafana.md: add periods to sentences Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 013fa8869..ca8b6a082 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -79,12 +79,12 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju Name | Description -----|---------- `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. -`prometheus_node_exporter_enabled`|[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 +`prometheus_node_exporter_enabled`|[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. `prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. `matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. -`grafana_enabled`|[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 +`grafana_enabled`|[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. `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. -`grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here +`grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here. ## Security and privacy @@ -107,21 +107,21 @@ The following variables may be of interest: Name | Description -----|---------- `matrix_metrics_exposure_enabled`|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. -`matrix_metrics_exposure_http_basic_auth_enabled`|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 +`matrix_metrics_exposure_http_basic_auth_enabled`|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. `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs. -`matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network) +`matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). `matrix_synapse_metrics_proxying_enabled`|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. -`prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network) +`prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). `prometheus_node_exporter_container_labels_traefik_enabled`|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. -`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network) +`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network). `prometheus_postgres_exporter_container_labels_traefik_enabled`|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. -`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network) -`matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network) +`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network). +`matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). `matrix_sliding_sync_metrics_proxying_enabled`|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. -`matrix_bridge_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network) +`matrix_bridge_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). `matrix_bridge_hookshot_metrics_proxying_enabled`|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. `matrix_SERVICE_metrics_proxying_enabled`|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. -`matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network) +`matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). ### Collecting Synapse worker metrics to an external Prometheus server From 0f940af3978a0ac5b72c2e934579f5475f2ef9b2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Feb 2025 01:51:16 +0900 Subject: [PATCH 493/952] Update docs/faq.md and docs for importing data: adopt the common introduction Signed-off-by: Suguru Hirahara --- docs/faq.md | 2 +- docs/importing-postgres.md | 7 +++++-- docs/importing-synapse-media-store.md | 2 +- docs/importing-synapse-sqlite.md | 4 +++- 4 files changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 3e475fba8..c7e4cd2fb 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -415,7 +415,7 @@ See our [documentation page about upgrading services](maintenance-upgrading-serv ### How do I move my existing installation to another (VM) server? -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). +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). 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). diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index d73b3c95a..1113caf1e 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -1,7 +1,10 @@ # Importing an existing Postgres database from another installation (optional) -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)). +You can manually import your database from a previous default installation of Synapse. + +**Notes**: +- 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. +- 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). ## Prerequisites diff --git a/docs/importing-synapse-media-store.md b/docs/importing-synapse-media-store.md index dd1fe9671..69c8b0ef6 100644 --- a/docs/importing-synapse-media-store.md +++ b/docs/importing-synapse-media-store.md @@ -1,6 +1,6 @@ # Importing `media_store` data files from an existing Synapse installation (optional) -Run this if you'd like to import your `media_store` files from a previous installation of Synapse. +You can manually import your `media_store` files from a previous installation of Synapse. ## Prerequisites diff --git a/docs/importing-synapse-sqlite.md b/docs/importing-synapse-sqlite.md index 29fa0594a..0fe0ec84e 100644 --- a/docs/importing-synapse-sqlite.md +++ b/docs/importing-synapse-sqlite.md @@ -1,11 +1,13 @@ # Importing an existing SQLite database from another Synapse installation (optional) -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)). +You can manually import your database from a previous default installation of Synapse. While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database. 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. +**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. + ## Prerequisites Before doing the actual import: From 8df253b80a627d07488962acb7b8633d21b06a0c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 20:42:38 +0900 Subject: [PATCH 494/952] Update roles/custom/matrix-authentication-service/defaults/main.yml: minor changes to comments - Fix punctuations - Set the common expression for matrix_authentication_service_config_email_mode Signed-off-by: Suguru Hirahara --- .../defaults/main.yml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 61dc8f58c..2936d313f 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -161,13 +161,13 @@ matrix_authentication_service_config_email_reply_to_address: "{{ matrix_authenti # Controls the `email.transport` configuration setting. # -# Valid options are: blackhole, smtp, aws_ses +# Valid values: blackhole, smtp, aws_ses # Upstream reports that `sendmail` is supported as well, # but this is not true when running it in a container image due to the `sendmail` binary not being included. matrix_authentication_service_config_email_transport: blackhole # Controls the `email.mode` configuration setting for SMTP. -# Options are 'plain', 'tls', or 'starttls'. +# Valid values: plain, tls, starttls matrix_authentication_service_config_email_mode: plain # Controls the `email.hostname` configuration setting for SMTP. @@ -220,7 +220,7 @@ matrix_authentication_service_config_account_password_change_allowed: true # Controls the `account.password_recovery_enabled` configuration setting. # -# Whether email-based password recovery is enabled +# Whether email-based password recovery is enabled. # This has no effect if password login is disabled. matrix_authentication_service_config_account_password_recovery_enabled: false @@ -340,7 +340,7 @@ matrix_authentication_service_config_http_trusted_proxies: matrix_authentication_service_config_matrix_homeserver: "" # Controls the `matrix.endpoint` configuration setting. -# URL to which the homeserver is accessible from the service +# URL to which the homeserver is accessible from the service. matrix_authentication_service_config_matrix_endpoint: "" # Controls the `matrix.secret` configuration setting. @@ -361,20 +361,20 @@ matrix_authentication_service_config_matrix_secret: "" # Controls the `passwords.enabled` configuration setting. # Whether to enable the password database. -# If disabled, users will only be able to log in using upstream OIDC providers +# If disabled, users will only be able to log in using upstream OIDC providers. matrix_authentication_service_config_passwords_enabled: true # Controls the `passwords.schemes` configuration setting. # List of password hashing schemes being used. -# Only change this if you know what you're doing +# Only change this if you know what you're doing. matrix_authentication_service_config_passwords_schemes: - version: 1 algorithm: argon2id # Controls the `passwords.minimum_complexity` configuration setting. -# Minimum complexity required for passwords, estimated by the zxcvbn algorithm -# Must be between 0 and 4, default is 3 -# See https://github.com/dropbox/zxcvbn#usage for more information +# Minimum complexity required for passwords, estimated by the zxcvbn algorithm. +# Must be between 0 and 4. Default is 3. +# See https://github.com/dropbox/zxcvbn#usage for more information. matrix_authentication_service_config_passwords_minimum_complexity: 3 ######################################################################################## @@ -502,7 +502,7 @@ matrix_authentication_service_container_labels_public_main_tls_certResolver: "{{ # - https://element-hq.github.io/matrix-authentication-service/setup/reverse-proxy.html#compatibility-layer # # Regardless of whether this is enabled, it may or may not take effect due to the value of other variables. -# See `matrix_authentication_service_container_labels_traefik_enabled` +# See `matrix_authentication_service_container_labels_traefik_enabled`. matrix_authentication_service_container_labels_public_compatibility_layer_enabled: false matrix_authentication_service_container_labels_public_compatibility_layer_hostname: "" matrix_authentication_service_container_labels_public_compatibility_layer_path_regexp: "^/_matrix/client/(?P([^/]+))/(?P(login|logout|refresh))" From 2a9cf7de9748177809352f5d253d440f849dbf60 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 21 Jan 2025 20:45:55 +0900 Subject: [PATCH 495/952] Update roles/custom/matrix-authentication-service/tasks/syn2mas.yml: fix punctuation Signed-off-by: Suguru Hirahara --- roles/custom/matrix-authentication-service/tasks/syn2mas.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-authentication-service/tasks/syn2mas.yml b/roles/custom/matrix-authentication-service/tasks/syn2mas.yml index 46ae2688c..821892f8d 100644 --- a/roles/custom/matrix-authentication-service/tasks/syn2mas.yml +++ b/roles/custom/matrix-authentication-service/tasks/syn2mas.yml @@ -106,7 +106,7 @@ # See: https://ansibledaily.com/print-to-standard-output-without-escaping/ # # We want to run `debug: msg=".."`, but that dumps it as JSON and escapes double quotes within it, -# which ruins the command (`matrix_authentication_service_syn2mas_migration_command`) +# which ruins the command (`matrix_authentication_service_syn2mas_migration_command`). - name: Note about syn2mas migration ansible.builtin.set_fact: dummy: true From 1e7dba3737dc1ff0951cf25fc375499219822d5e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Feb 2025 02:06:25 +0900 Subject: [PATCH 496/952] Update docs/configuring-playbook-prometheus-grafana.md: move up the section for explanations about the variables Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index ca8b6a082..9fb3bf5b9 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -38,6 +38,18 @@ grafana_default_admin_password: "some_strong_password_chosen_by_you" The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically. +### What does it do? + +Name | Description +-----|---------- +`prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. +`prometheus_node_exporter_enabled`|[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. +`prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. +`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. +`grafana_enabled`|[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. +`grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. +`grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here. + ### Adjusting the Grafana URL (optional) By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -74,18 +86,6 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. -## What does it do? - -Name | Description ------|---------- -`prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. -`prometheus_node_exporter_enabled`|[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. -`prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. -`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. -`grafana_enabled`|[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. -`grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. -`grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here. - ## Security and privacy Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password. From 19f17bb729496a935a091c3c796b20dcad8ce944 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Feb 2025 15:35:08 +0900 Subject: [PATCH 497/952] Update docs/configuring-playbook-prometheus-grafana.md: use the common placeholders Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 9fb3bf5b9..5e7c08dbc 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -30,10 +30,10 @@ grafana_anonymous_access: false # This has no relation to your Matrix user ID. It can be any username you'd like. # Changing the username subsequently won't work. -grafana_default_admin_user: "some_username_chosen_by_you" +grafana_default_admin_user: "USERNAME_HERE" # Changing the password subsequently won't work. -grafana_default_admin_password: "some_strong_password_chosen_by_you" +grafana_default_admin_password: "PASSWORD_HERE" ``` 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. From 8d52dc985a9ce891abda7535272653dff869c48f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 01:42:41 +0900 Subject: [PATCH 498/952] Update docs/configuring-playbook-prometheus-grafana.md: add sections for Prometheus and Grafana The introductions are copied from their configuration files. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 5e7c08dbc..3b2f5514d 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -10,7 +10,9 @@ When setting, replace `example.com` with your own. ## Adjusting the playbook configuration -To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +### Configure Prometheus + +Prometheus is an open-source systems monitoring and alerting toolkit. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml prometheus_enabled: true @@ -23,7 +25,13 @@ prometheus_postgres_exporter_enabled: true # You can remove this, if unnecessary. matrix_prometheus_nginxlog_exporter_enabled: true +``` +### Configure Grafana + +Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file: + +```yaml grafana_enabled: true grafana_anonymous_access: false From 15e889c21a16ccad2da3dbc922c1ebe6fb1b90f6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 02:20:04 +0900 Subject: [PATCH 499/952] Update docs/configuring-playbook-prometheus-grafana.md: comment out lines for configs disabled by default - Replace the comments for them Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 3b2f5514d..d5a3d2953 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -17,14 +17,14 @@ Prometheus is an open-source systems monitoring and alerting toolkit. To enable ```yaml prometheus_enabled: true -# You can remove this, if unnecessary. -prometheus_node_exporter_enabled: true +# Uncomment to enable Node Exporter. +# prometheus_node_exporter_enabled: true -# You can remove this, if unnecessary. -prometheus_postgres_exporter_enabled: true +# Uncomment to enable Postgres Exporter. +# prometheus_postgres_exporter_enabled: true -# You can remove this, if unnecessary. -matrix_prometheus_nginxlog_exporter_enabled: true +# Uncomment to enable nginx Log Exporter. +# matrix_prometheus_nginxlog_exporter_enabled: true ``` ### Configure Grafana From 8ecc83f2a94213077cc59427c1d2731458867dce Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 03:21:39 +0900 Subject: [PATCH 500/952] Update docs/configuring-playbook-prometheus-grafana.md: copy the comments from the main.yml file Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d5a3d2953..3a07a9a5c 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -34,6 +34,7 @@ Grafana is an open source visualization and analytics software. To enable it, ad ```yaml grafana_enabled: true +# Allow viewing Grafana without logging in. grafana_anonymous_access: false # This has no relation to your Matrix user ID. It can be any username you'd like. @@ -56,7 +57,7 @@ Name | Description `matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. `grafana_enabled`|[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. `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. -`grafana_default_admin_user`
`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here. +`grafana_default_admin_user`
`grafana_default_admin_password`|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. ### Adjusting the Grafana URL (optional) From 781f6d68a756222509477e4851692d9813cb5c68 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 03:25:36 +0900 Subject: [PATCH 501/952] Update docs/configuring-playbook-prometheus-grafana.md: comment out grafana_anonymous_access as it is disabled by default Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 3a07a9a5c..1e607b62c 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -34,8 +34,8 @@ Grafana is an open source visualization and analytics software. To enable it, ad ```yaml grafana_enabled: true -# Allow viewing Grafana without logging in. -grafana_anonymous_access: false +# Uncomment to allow viewing Grafana without logging in. +# grafana_anonymous_access: true # This has no relation to your Matrix user ID. It can be any username you'd like. # Changing the username subsequently won't work. From 35b88ced00ff816dd5007bda4dd9ac03972d4762 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 02:21:12 +0900 Subject: [PATCH 502/952] Update docs/configuring-playbook-prometheus-grafana.md: split the table for the variables into two Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 1e607b62c..a579fc4ec 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -27,6 +27,15 @@ prometheus_enabled: true # matrix_prometheus_nginxlog_exporter_enabled: true ``` +Name | Description +-----|---------- +`prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. +`prometheus_node_exporter_enabled`|[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. +`prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. +`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. + +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. + ### Configure Grafana Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file: @@ -45,16 +54,8 @@ grafana_default_admin_user: "USERNAME_HERE" grafana_default_admin_password: "PASSWORD_HERE" ``` -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. - -### What does it do? - Name | Description -----|---------- -`prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. -`prometheus_node_exporter_enabled`|[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. -`prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. -`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. `grafana_enabled`|[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. `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. `grafana_default_admin_user`
`grafana_default_admin_password`|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. From 598cec4257325535fdc7230ee369028fb9f779bb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 02:48:45 +0900 Subject: [PATCH 503/952] Update docs/configuring-playbook-prometheus-grafana.md: add the note label Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index a579fc4ec..418758cf4 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -34,7 +34,7 @@ Name | Description `prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. `matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. -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. +**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. ### Configure Grafana From 0154bc9931d8d9f3a52a365126a3bd510e244017 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 13:46:43 +0900 Subject: [PATCH 504/952] Update docs/configuring-playbook-prometheus-grafana.md: move descriptions specific to each component to its subsection Signed-off-by: Suguru Hirahara --- .../configuring-playbook-prometheus-grafana.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 418758cf4..d3ea84f38 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -36,6 +36,14 @@ Name | Description **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. +#### Extending the configuration + +There are some additional things you may wish to configure about Prometheus. + +Take a look at: + +- [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 + ### Configure Grafana Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file: @@ -60,7 +68,7 @@ Name | Description `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. `grafana_default_admin_user`
`grafana_default_admin_password`|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. -### Adjusting the Grafana URL (optional) +#### Adjusting the Grafana URL (optional) By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -75,14 +83,6 @@ After changing the domain, **you may need to adjust your DNS** records to point **Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. -### Extending the configuration - -There are some additional things you may wish to configure about Prometheus. - -Take a look at: - -- [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 - ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 2163daead26389562384da339295958841be0fb0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 23:48:00 +0900 Subject: [PATCH 505/952] Update docs/configuring-playbook-prometheus-grafana.md: move the comments out of the YAML block Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d3ea84f38..13da39f81 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -46,7 +46,11 @@ Take a look at: ### Configure Grafana -Grafana is an open source visualization and analytics software. To enable it, add the following configuration to your `vars.yml` file: +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`. + +**Notes**: +- `grafana_default_admin_user` has nothing to do with your Matrix user ID. It can be any string you'd like. +- Changing the username/password subsequently won't work. ```yaml grafana_enabled: true @@ -54,11 +58,7 @@ grafana_enabled: true # Uncomment to allow viewing Grafana without logging in. # grafana_anonymous_access: true -# This has no relation to your Matrix user ID. It can be any username you'd like. -# Changing the username subsequently won't work. grafana_default_admin_user: "USERNAME_HERE" - -# Changing the password subsequently won't work. grafana_default_admin_password: "PASSWORD_HERE" ``` From 5e2bc80e6b5d5aae3bac3448a9312264736a7a51 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 23:49:02 +0900 Subject: [PATCH 506/952] Update docs/configuring-playbook-prometheus-grafana.md: move down the optional configuration Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 13da39f81..e02270d7a 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -55,18 +55,18 @@ Grafana is an open source visualization and analytics software. To enable it, ad ```yaml grafana_enabled: true -# Uncomment to allow viewing Grafana without logging in. -# grafana_anonymous_access: true - grafana_default_admin_user: "USERNAME_HERE" grafana_default_admin_password: "PASSWORD_HERE" + +# Uncomment to allow viewing Grafana without logging in. +# grafana_anonymous_access: true ``` Name | Description -----|---------- `grafana_enabled`|[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. -`grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. `grafana_default_admin_user`
`grafana_default_admin_password`|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. +`grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. #### Adjusting the Grafana URL (optional) From d7eb3f27650c354eaa0a4b9f766930593435a9f5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Feb 2025 23:51:33 +0900 Subject: [PATCH 507/952] Update docs/configuring-playbook-prometheus-grafana.md: move up the note about creating a CNAME record Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index e02270d7a..897ebedab 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -8,6 +8,8 @@ By default, this playbook installs Grafana web user-interface on the `stats.` su When setting, replace `example.com` with your own. +**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. + ## Adjusting the playbook configuration ### Configure Prometheus @@ -81,8 +83,6 @@ grafana_hostname: grafana.example.com After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server. -**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. - ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From 3d4c9bd0e9a0d59bcb01cf72daa2a32793d5d7da Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 13:35:58 +0900 Subject: [PATCH 508/952] Update docs/configuring-playbook-prometheus-grafana.md Co-authored-by: Slavi Pantaleev --- docs/configuring-playbook-prometheus-grafana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 897ebedab..477cb172e 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -8,7 +8,7 @@ By default, this playbook installs Grafana web user-interface on the `stats.` su When setting, replace `example.com` with your own. -**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record. +**Note**: It is possible to install Prometheus without installing Grafana. In this case it is not required to create the CNAME record. ## Adjusting the playbook configuration From 7ae30239db780640a94b2ed89d3353004d400cd7 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 9 Feb 2025 08:28:00 +0000 Subject: [PATCH 509/952] Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2025 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index e3c423340..ea631464f 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -6,7 +6,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2024.12.18 +matrix_alertmanager_receiver_version: 2025.2.9 matrix_alertmanager_receiver_scheme: https From 747e8ad589ada45496e4d85588a0fe354f5157b7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 14:54:21 +0900 Subject: [PATCH 510/952] Update docs/configuring-playbook-prometheus-grafana.md: switch the position of "Grafana" and "Prometheus" in the first sentence Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 477cb172e..253ad0fb4 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -1,6 +1,6 @@ # Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional) -The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you. +The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you. ## Adjusting DNS records From 5ca5613d95cb5ef4cd8297856606e5d5ce6890a8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:48:59 +0900 Subject: [PATCH 511/952] Update docs/configuring-playbook-prometheus-postgres.md: add the copyright header before deleting the file Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-postgres.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md index 74d3eda4f..59080ba4d 100644 --- a/docs/configuring-playbook-prometheus-postgres.md +++ b/docs/configuring-playbook-prometheus-postgres.md @@ -1,3 +1,12 @@ + + # Enabling metrics and graphs for Postgres (optional) Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. From 07cca8f4b4fd9cc20d666f965a076a81dc8b3765 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 15:19:04 +0900 Subject: [PATCH 512/952] Merge the document for instruction about metrics for Postgres to docs/configuring-playbook-prometheus-grafana.md to improve maintainability Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- ...configuring-playbook-prometheus-grafana.md | 24 ++++++++-- ...onfiguring-playbook-prometheus-postgres.md | 46 ------------------- 3 files changed, 22 insertions(+), 50 deletions(-) delete mode 100644 docs/configuring-playbook-prometheus-postgres.md diff --git a/CHANGELOG.md b/CHANGELOG.md index bbbc609d9..c04e39d90 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1824,7 +1824,7 @@ See our [Setting up the ntfy push notifications server](docs/configuring-playboo **If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`. -**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`. +**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enabling-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`. **If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that: diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 253ad0fb4..0fe941d60 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -33,11 +33,28 @@ Name | Description -----|---------- `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. `prometheus_node_exporter_enabled`|[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. -`prometheus_postgres_exporter_enabled`|[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus. +`prometheus_postgres_exporter_enabled`|[Postgres Exporter](#enabling-metrics-and-graphs-for-postgres-optional) is an addon of sorts to expose Postgres database metrics to Prometheus. `matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. **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. +#### Enabling metrics and graphs for Postgres (optional) + +Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. + +To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +prometheus_postgres_exporter_enabled: true +``` + +Name | Description +-----|---------- +`prometheus_postgres_exporter_enabled`|Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false' +`prometheus_postgres_exporter_database_username`| The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter' +`prometheus_postgres_exporter_database_password`| The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook +`prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page. + #### Extending the configuration There are some additional things you may wish to configure about Prometheus. @@ -123,8 +140,8 @@ Name | Description `matrix_synapse_metrics_proxying_enabled`|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. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). `prometheus_node_exporter_container_labels_traefik_enabled`|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. -`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network). -`prometheus_postgres_exporter_container_labels_traefik_enabled`|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. +`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enabling-metrics-and-graphs-for-postgres-optional) (locally, on the container network). +`prometheus_postgres_exporter_container_labels_traefik_enabled`|Set this to `true` to expose the [Postgres exporter](#enabling-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network). `matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). `matrix_sliding_sync_metrics_proxying_enabled`|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. @@ -178,3 +195,4 @@ As with all other services, you can find the logs in [systemd-journald](https:// - [The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2) - [The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana) - [The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs) +- [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard) diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md deleted file mode 100644 index 59080ba4d..000000000 --- a/docs/configuring-playbook-prometheus-postgres.md +++ /dev/null @@ -1,46 +0,0 @@ - - -# Enabling metrics and graphs for Postgres (optional) - -Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. - -## Adjusting the playbook configuration - -To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -prometheus_postgres_exporter_enabled: true -``` - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start -``` - -The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - -`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - -## What does it do? - -Name | Description ------|---------- -`prometheus_postgres_exporter_enabled`|Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false' -`prometheus_postgres_exporter_database_username`| The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter' -`prometheus_postgres_exporter_database_password`| The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook -`prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page. - -## More information - -- [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard) From 505ff582920fca7e16134a7785bf073ce6430482 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 15:21:40 +0900 Subject: [PATCH 513/952] Update docs/configuring-playbook-prometheus-grafana.md: tidy the section for Postgres exporter Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- docs/configuring-playbook-prometheus-grafana.md | 14 +++++--------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c04e39d90..4dcd99ba6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1824,7 +1824,7 @@ See our [Setting up the ntfy push notifications server](docs/configuring-playboo **If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`. -**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enabling-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`. +**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`. **If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that: diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 0fe941d60..8f63f8533 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -22,9 +22,6 @@ prometheus_enabled: true # Uncomment to enable Node Exporter. # prometheus_node_exporter_enabled: true -# Uncomment to enable Postgres Exporter. -# prometheus_postgres_exporter_enabled: true - # Uncomment to enable nginx Log Exporter. # matrix_prometheus_nginxlog_exporter_enabled: true ``` @@ -33,16 +30,15 @@ Name | Description -----|---------- `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. `prometheus_node_exporter_enabled`|[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. -`prometheus_postgres_exporter_enabled`|[Postgres Exporter](#enabling-metrics-and-graphs-for-postgres-optional) is an addon of sorts to expose Postgres database metrics to Prometheus. `matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. **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. -#### Enabling metrics and graphs for Postgres (optional) +#### Enable metrics and graphs for Postgres (optional) -Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. +Expanding on the metrics exposed by the Synapse exporter and the Node exporter, the playbook can also install and configure the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. -To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable it, add the following configuration to your `vars.yml` file: ```yaml prometheus_postgres_exporter_enabled: true @@ -140,8 +136,8 @@ Name | Description `matrix_synapse_metrics_proxying_enabled`|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. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). `prometheus_node_exporter_container_labels_traefik_enabled`|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. -`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enabling-metrics-and-graphs-for-postgres-optional) (locally, on the container network). -`prometheus_postgres_exporter_container_labels_traefik_enabled`|Set this to `true` to expose the [Postgres exporter](#enabling-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. +`prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network). +`prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network). `matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). `matrix_sliding_sync_metrics_proxying_enabled`|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. From 8b7b7732efa6f87c54993578c985b16ff5ce7585 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 15:41:30 +0900 Subject: [PATCH 514/952] Update docs/configuring-playbook-prometheus-grafana.md: move variables for setting username and password of Postgres exporter to the YAML block above Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 8f63f8533..f37613603 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -40,16 +40,24 @@ Expanding on the metrics exposed by the Synapse exporter and the Node exporter, To enable it, add the following configuration to your `vars.yml` file: +**Note**: `prometheus_postgres_exporter_database_username` has nothing to do with your Matrix user ID. It can be any string you'd like. + ```yaml prometheus_postgres_exporter_enabled: true + +# The username for the user that the exporter uses to connect to the database. +# Uncomment and adjust this part if you'd like to use a username different than the default. +# prometheus_postgres_exporter_database_username: "matrix_prometheus_postgres_exporter" + +# The password for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook. +# Uncomment and adjust this part if you'd like to set the password by yourself. +# prometheus_postgres_exporter_database_password: "PASSWORD_HERE" ``` Name | Description -----|---------- `prometheus_postgres_exporter_enabled`|Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false' -`prometheus_postgres_exporter_database_username`| The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter' -`prometheus_postgres_exporter_database_password`| The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook -`prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page. +`prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` below. #### Extending the configuration From 4ecf6c2ba325cb25648bbaa254c0384b33625730 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 15:43:38 +0900 Subject: [PATCH 515/952] Update docs/configuring-playbook-prometheus-grafana.md: fix capitalization Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index f37613603..d85b60232 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -36,7 +36,7 @@ Name | Description #### Enable metrics and graphs for Postgres (optional) -Expanding on the metrics exposed by the Synapse exporter and the Node exporter, the playbook can also install and configure the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database. +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. To enable it, add the following configuration to your `vars.yml` file: @@ -56,7 +56,7 @@ prometheus_postgres_exporter_enabled: true Name | Description -----|---------- -`prometheus_postgres_exporter_enabled`|Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false' +`prometheus_postgres_exporter_enabled`|Enable the Postgres Prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter. The default is 'false' `prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` below. #### Extending the configuration @@ -199,4 +199,4 @@ As with all other services, you can find the logs in [systemd-journald](https:// - [The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2) - [The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana) - [The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs) -- [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard) +- [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic Postgres dashboard) From 152031bbae616f193d26ee4c083ceb86292e4768 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:01:24 +0900 Subject: [PATCH 516/952] Update docs/configuring-playbook-prometheus-grafana.md: move the security notice to the top Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d85b60232..96ee9b694 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -2,6 +2,11 @@ The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you. +> [!WARNING] +> Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password. +> +> Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source. + ## Adjusting DNS records By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to create a CNAME record for `stats`, which targets `matrix.example.com`. @@ -117,12 +122,6 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. -## Security and privacy - -Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password. - -Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source. - ## Collecting metrics to an external Prometheus server **If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics "publicly". From 00f3eda4dc0ab3272bc8c58c64c4652dbbc5c102 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:09:08 +0900 Subject: [PATCH 517/952] Update docs for Prometheus: adopt the common warning message Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 +- docs/configuring-playbook-prometheus-nginxlog.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 96ee9b694..4c4346e88 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -3,7 +3,7 @@ The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you. > [!WARNING] -> 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. +> Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling (anonymous) access. And you should really not forget to change your Grafana password. > > Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source. diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 80107b906..4d1c08a9a 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -25,7 +25,7 @@ matrix_prometheus_nginxlog_exporter_enabled: true ### Save metrics on an external Prometheus server (optional) > [!WARNING] -> Metrics and resulting graphs can contain a lot of information. nginx logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password. +> Metrics and resulting graphs can contain a lot of information. nginx logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. And you should really not forget to change your Grafana password. The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. From a691306614eef3613a1acd4ae02b368e2a855944 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:12:40 +0900 Subject: [PATCH 518/952] Update docs/configuring-playbook-prometheus-grafana.md: create sections for adjusting configurations of Prometheus and Grafanato decrease the section level Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 4c4346e88..c9de18383 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -15,9 +15,7 @@ When setting, replace `example.com` with your own. **Note**: It is possible to install Prometheus without installing Grafana. In this case it is not required to create the CNAME record. -## Adjusting the playbook configuration - -### Configure Prometheus +## Adjusting the playbook configuration — Prometheus Prometheus is an open-source systems monitoring and alerting toolkit. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -39,7 +37,7 @@ Name | Description **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. -#### Enable metrics and graphs for Postgres (optional) +### Enable metrics and graphs for Postgres (optional) 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. @@ -64,7 +62,7 @@ Name | Description `prometheus_postgres_exporter_enabled`|Enable the Postgres Prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter. The default is 'false' `prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` below. -#### Extending the configuration +### Extending the configuration There are some additional things you may wish to configure about Prometheus. @@ -72,7 +70,7 @@ Take a look at: - [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 -### Configure Grafana +## Adjusting the playbook configuration — Grafana 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`. @@ -96,7 +94,7 @@ Name | Description `grafana_default_admin_user`
`grafana_default_admin_password`|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. `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option. -#### Adjusting the Grafana URL (optional) +### Adjusting the Grafana URL (optional) By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one. From f4bc9c98ed1cd0b12d41df816c1e2e1b5e4cfcbe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:23:26 +0900 Subject: [PATCH 519/952] Update docs/configuring-playbook-prometheus-grafana.md: remove the note about the component disabled by default It is not common to add a note about the component disabled by default. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index c9de18383..ba8085869 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -59,7 +59,7 @@ prometheus_postgres_exporter_enabled: true Name | Description -----|---------- -`prometheus_postgres_exporter_enabled`|Enable the Postgres Prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter. The default is 'false' +`prometheus_postgres_exporter_enabled`|Enable the Postgres Prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter. `prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` below. ### Extending the configuration From a67745b1fc9e6b6ff0f7cbe9e4a611b6c174311a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 16:29:15 +0900 Subject: [PATCH 520/952] Remove the table for variables about the Postgres Server Exporter As prometheus_postgres_exporter_container_labels_traefik_enabled is explained below, it is sensible to remove this duplicated entry in favor of it. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index ba8085869..cd6514e80 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -41,6 +41,8 @@ Name | Description 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. +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. + To enable it, add the following configuration to your `vars.yml` file: **Note**: `prometheus_postgres_exporter_database_username` has nothing to do with your Matrix user ID. It can be any string you'd like. @@ -57,11 +59,6 @@ prometheus_postgres_exporter_enabled: true # prometheus_postgres_exporter_database_password: "PASSWORD_HERE" ``` -Name | Description ------|---------- -`prometheus_postgres_exporter_enabled`|Enable the Postgres Prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the Prometheus config which tells Prometheus about this new exporter. -`prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` below. - ### Extending the configuration There are some additional things you may wish to configure about Prometheus. From 2df8793a9cb0749441b529bc456d25127330b595 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 18:24:41 +0900 Subject: [PATCH 521/952] Update docs/configuring-playbook-prometheus-grafana.md: add two entries for journalctl (matrix-prometheus-node-exporter and matrix-prometheus-postgres-exporter) Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index cd6514e80..5733bd44d 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -184,6 +184,8 @@ scrape_configs: 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: - `journalctl -fu matrix-prometheus` for Prometheus +- `journalctl -fu matrix-prometheus-node-exporter` for Node Exporter +- `journalctl -fu matrix-prometheus-postgres-exporter` for PostgreSQL Server Exporter - `journalctl -fu matrix-grafana` for Grafana ## More information From c5019b5a30165553ec8ae0e4e228e6f3e83e9b5c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:52:19 +0900 Subject: [PATCH 522/952] Update docs/configuring-playbook-prometheus-nginxlog.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-nginxlog.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 4d1c08a9a..f09ff568d 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -1,3 +1,11 @@ + + # Enabling metrics and graphs for nginx logs (optional) The playbook can install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you, in order to make it possible to have some (visual) insight into [nginx](https://nginx.org/) logs. From e4d3b00927d0c6c4e80c0337719da49c5cdb26cd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:18:06 +0900 Subject: [PATCH 523/952] Partially merge docs for prometheus-nginx-log-exporter to docs/configuring-playbook-prometheus-grafana.md Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 27 ++++++++++++++----- ...onfiguring-playbook-prometheus-nginxlog.md | 22 +-------------- 2 files changed, 22 insertions(+), 27 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 5733bd44d..8a3c8dd60 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -24,16 +24,12 @@ prometheus_enabled: true # Uncomment to enable Node Exporter. # prometheus_node_exporter_enabled: true - -# Uncomment to enable nginx Log Exporter. -# matrix_prometheus_nginxlog_exporter_enabled: true ``` Name | Description -----|---------- `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. `prometheus_node_exporter_enabled`|[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. -`matrix_prometheus_nginxlog_exporter_enabled`|[nginx Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose nginx logs to Prometheus. **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. @@ -59,6 +55,24 @@ prometheus_postgres_exporter_enabled: true # prometheus_postgres_exporter_database_password: "PASSWORD_HERE" ``` +### Enable metrics and graphs for nginx logs (optional) + +The playbook can also install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you. + +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. + +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. + +To enable it, add the following configuration to your `vars.yml` file: + +```yaml +matrix_prometheus_nginxlog_exporter_enabled: true +``` + +If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be created. + +**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant. + ### Extending the configuration There are some additional things you may wish to configure about Prometheus. @@ -123,7 +137,7 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network. -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. +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). 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. When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one. @@ -140,7 +154,8 @@ Name | Description `prometheus_node_exporter_container_labels_traefik_enabled`|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. `prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network). `prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. -`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network). +`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network). +`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). `matrix_sliding_sync_metrics_proxying_enabled`|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. `matrix_bridge_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index f09ff568d..244d124b7 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -8,28 +8,12 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Enabling metrics and graphs for nginx logs (optional) -The playbook can install and configure the [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) service for you, in order to make it possible to have some (visual) insight into [nginx](https://nginx.org/) logs. - -It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint. - -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. - -**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant. - ## Prerequisite To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary — see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server). -If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created. - ## Adjusting the playbook configuration -Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -matrix_prometheus_nginxlog_exporter_enabled: true -``` - ### Save metrics on an external Prometheus server (optional) > [!WARNING] @@ -39,11 +23,7 @@ The playbook will automatically integrate the metrics into the [Prometheus](./co When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). -You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services. - -Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default. - -For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). +For password-protection, use or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). ### Docker Image Compatibility (optional) From be02f12fed822a654b3a143f1a30c9267c532bcd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:22:30 +0900 Subject: [PATCH 524/952] Update docs/configuring-playbook-prometheus-grafana.md: fix the variables name Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 8a3c8dd60..f36be5ec3 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -158,8 +158,8 @@ Name | Description `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). `matrix_sliding_sync_metrics_proxying_enabled`|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. -`matrix_bridge_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). -`matrix_bridge_hookshot_metrics_proxying_enabled`|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. +`matrix_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). +`matrix_hookshot_metrics_proxying_enabled`|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. `matrix_SERVICE_metrics_proxying_enabled`|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. `matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). From 7907a649ee9648f7b98e9da59705bf085918e977 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:25:00 +0900 Subject: [PATCH 525/952] Update docs/configuring-playbook-prometheus-grafana.md: remove variables for Sliding Sync proxy metrics The component has been deprecated and it is not really sensible to keep those entries. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index f36be5ec3..7b97fb4ba 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -156,8 +156,6 @@ Name | Description `prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network). `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. -`matrix_sliding_sync_metrics_enabled`|Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network). -`matrix_sliding_sync_metrics_proxying_enabled`|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. `matrix_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). `matrix_hookshot_metrics_proxying_enabled`|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. `matrix_SERVICE_metrics_proxying_enabled`|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. From 2180c58e6299a90aee670675daea5140552d2fee Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:27:02 +0900 Subject: [PATCH 526/952] Update docs for Prometheus: move the description for Docker image compatibility Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 9 +++++++++ docs/configuring-playbook-prometheus-nginxlog.md | 9 --------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 7b97fb4ba..e37175569 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -73,6 +73,15 @@ If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be creat **Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant. +#### Docker image compatibility (optional) + +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: + +```yaml +matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false +matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag +``` + ### Extending the configuration There are some additional things you may wish to configure about Prometheus. diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 244d124b7..6689d0d26 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -25,15 +25,6 @@ When using an external Prometheus server, you'll need to expose metrics publicly For password-protection, use or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). -### Docker Image Compatibility (optional) - -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: - -```yaml -matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false -matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag -``` - ### Extending the configuration There are some additional things you may wish to configure about the component. From 7c81c148cfd108b95852680b9578bdb9abcebeb4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:30:03 +0900 Subject: [PATCH 527/952] Update docs for Prometheus: move other relevant instructions Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 +++- docs/configuring-playbook-prometheus-nginxlog.md | 12 ------------ 2 files changed, 3 insertions(+), 13 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index e37175569..8a82002f8 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -84,11 +84,12 @@ matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag ### Extending the configuration -There are some additional things you may wish to configure about Prometheus. +There are some additional things you may wish to configure about Prometheus and its add-on. Take a look at: - [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 +- `roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file ## Adjusting the playbook configuration — Grafana @@ -208,6 +209,7 @@ As with all other services, you can find the logs in [systemd-journald](https:// - `journalctl -fu matrix-prometheus` for Prometheus - `journalctl -fu matrix-prometheus-node-exporter` for Node Exporter - `journalctl -fu matrix-prometheus-postgres-exporter` for PostgreSQL Server Exporter +- `journalctl -fu matrix-prometheus-nginxlog-exporter` for prometheus-nginxlog-exporter - `journalctl -fu matrix-grafana` for Grafana ## More information diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md index 6689d0d26..fedd17609 100644 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ b/docs/configuring-playbook-prometheus-nginxlog.md @@ -25,14 +25,6 @@ When using an external Prometheus server, you'll need to expose metrics publicly For password-protection, use or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- `roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - ## Installing After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: @@ -45,7 +37,3 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - -## Troubleshooting - -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-prometheus-nginxlog-exporter`. From 66753136c07b412bbd445bf3d88dbdf284656f11 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:37:06 +0900 Subject: [PATCH 528/952] Delete docs/configuring-playbook-prometheus-nginxlog.md Signed-off-by: Suguru Hirahara --- README.md | 2 +- ...onfiguring-playbook-prometheus-nginxlog.md | 39 ------------------- docs/configuring-playbook.md | 2 - docs/container-images.md | 2 +- 4 files changed, 2 insertions(+), 43 deletions(-) delete mode 100644 docs/configuring-playbook-prometheus-nginxlog.md diff --git a/README.md b/README.md index 38db15f0b..4fad24e8c 100644 --- a/README.md +++ b/README.md @@ -162,7 +162,7 @@ Services that help you in administrating and monitoring your Matrix installation | [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client | [Link](docs/configuring-playbook-alertmanager-receiver.md) | | [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) | ❌ | OAuth 2.0 and OpenID Provider server | [Link](docs/configuring-playbook-matrix-authentication-service.md) | | [synapse-admin](https://github.com/etkecc/synapse-admin) | ❌ | Web UI tool for administrating users and rooms on your Matrix server | [Link](docs/configuring-playbook-synapse-admin.md) | -| Metrics and Graphs | ❌ | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too | [Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md)) | +| Metrics and Graphs | ❌ | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too | [Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)) | | [Borg](https://borgbackup.org) | ❌ | Backups | [Link](docs/configuring-playbook-backup-borg.md) | | [rageshake](https://github.com/matrix-org/rageshake) | ❌ | Bug report server | [Link](docs/configuring-playbook-rageshake.md) | | [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) | ❌ | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. | [Link](docs/configuring-playbook-synapse-usage-exporter.md) | diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md deleted file mode 100644 index fedd17609..000000000 --- a/docs/configuring-playbook-prometheus-nginxlog.md +++ /dev/null @@ -1,39 +0,0 @@ - - -# Enabling metrics and graphs for nginx logs (optional) - -## Prerequisite - -To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary — see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server). - -## Adjusting the playbook configuration - -### Save metrics on an external Prometheus server (optional) - -> [!WARNING] -> Metrics and resulting graphs can contain a lot of information. nginx logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. And you should really not forget to change your Grafana password. - -The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network. - -When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). - -For password-protection, use or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`). - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start -``` - -The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - -`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 71a7426c4..30e8c808d 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -199,8 +199,6 @@ Services that help you in administrating and monitoring your Matrix installation - [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) -- [Enabling metrics and graphs for nginx logs](configuring-playbook-prometheus-nginxlog.md) - - [Setting up the rageshake bug report server](configuring-playbook-rageshake.md) - [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) diff --git a/docs/container-images.md b/docs/container-images.md index 23e2004f9..efed979c2 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -123,7 +123,7 @@ Services that help you in administrating and monitoring your Matrix installation | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/prometheus](https://hub.docker.com/r/prom/prometheus/) | ❌ | [Prometheus](https://prometheus.io) time-series database server | | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/) | ❌ | Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter | | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) | ❌ | Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards) | -| [Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md) | [martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter) | ❌ | Addon for Prometheus that gathers access logs from various nginx reverse-proxies | +| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional) | [martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter) | ❌ | Addon for Prometheus that gathers access logs from various nginx reverse-proxies | | [Borg](configuring-playbook-backup-borg.md) | (N/A) | ❌ | Backups | | [rageshake](configuring-playbook-rageshake.md) | [matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake) | ❌ | Bug report server | | [synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md) | Self-building | ❌ | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. | From 8cbeb3d7dd699c1b14c4b1de98ca2e13fab5cf0d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:44:22 +0900 Subject: [PATCH 529/952] Update docs/configuring-playbook-prometheus-grafana.md: create a section for the Node Exporter Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 8a82002f8..0ffa208e6 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -21,18 +21,24 @@ Prometheus is an open-source systems monitoring and alerting toolkit. To enable ```yaml prometheus_enabled: true - -# Uncomment to enable Node Exporter. -# prometheus_node_exporter_enabled: true ``` Name | Description -----|---------- `prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. -`prometheus_node_exporter_enabled`|[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. **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. +### Enable metrics and graphs for generic system information (optional) + +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. + +To enable it, add the following configuration to your `vars.yml` file: + +```yaml +prometheus_node_exporter_enabled: true +``` + ### Enable metrics and graphs for Postgres (optional) 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. From 833c73de5666b9e793f736f9107d670ffa166c2f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 22:46:09 +0900 Subject: [PATCH 530/952] Update docs/configuring-playbook-prometheus-grafana.md: remove the table with one entry Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 0ffa208e6..160570e21 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -17,16 +17,14 @@ When setting, replace `example.com` with your own. ## Adjusting the playbook configuration — Prometheus -Prometheus is an open-source systems monitoring and alerting toolkit. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +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. + +To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml prometheus_enabled: true ``` -Name | Description ------|---------- -`prometheus_enabled`|[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about. - **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. ### Enable metrics and graphs for generic system information (optional) From dbab4a5329d9b98ad66f6e66e3deea0ed97b2d5a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 00:41:55 +0900 Subject: [PATCH 531/952] Update docs/configuring-playbook-prometheus-grafana.md: move down the entries for exposing metrics of Synapse The metrics of Synapse belongs to the category of individual services not introduced on the document. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 160570e21..50089863b 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -162,8 +162,6 @@ Name | Description `matrix_metrics_exposure_enabled`|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. `matrix_metrics_exposure_http_basic_auth_enabled`|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. `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs. -`matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). -`matrix_synapse_metrics_proxying_enabled`|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. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). `prometheus_node_exporter_container_labels_traefik_enabled`|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. `prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network). @@ -173,6 +171,8 @@ Name | Description `matrix_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). `matrix_hookshot_metrics_proxying_enabled`|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. `matrix_SERVICE_metrics_proxying_enabled`|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. +`matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). +`matrix_synapse_metrics_proxying_enabled`|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. `matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). ### Collecting Synapse worker metrics to an external Prometheus server From 042f587ba4b46b1d965e5c552b33aa8839857739 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 01:16:49 +0900 Subject: [PATCH 532/952] Update docs/configuring-playbook-prometheus-grafana.md: add an entry for matrix_media_repo_metrics_proxying_enabled Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 50089863b..75c50dff6 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -174,6 +174,7 @@ Name | Description `matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). `matrix_synapse_metrics_proxying_enabled`|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. `matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). +`matrix_media_repo_metrics_proxying_enabled`|Set this to `true` to expose media-repo's metrics on `https://matrix.example.com/metrics/matrix-media-repo`. ### Collecting Synapse worker metrics to an external Prometheus server From 16bb022390f2ba59d8d4a2efaa744aad327ae873 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Feb 2025 23:29:45 +0900 Subject: [PATCH 533/952] Update docs/configuring-playbook-prometheus-grafana.md: create a section for exposing metrics of other services/roles focusing on Hookshot Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 30 ++++++++++++++++--- 1 file changed, 26 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 75c50dff6..de4c2b49c 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -159,7 +159,7 @@ The following variables may be of interest: Name | Description -----|---------- -`matrix_metrics_exposure_enabled`|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. +`matrix_metrics_exposure_enabled`|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 [this section](#expose-metrics-of-other-services-roles) for exposing metrics on a per-service basis. `matrix_metrics_exposure_http_basic_auth_enabled`|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. `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). @@ -168,14 +168,36 @@ Name | Description `prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network). `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. -`matrix_hookshot_metrics_enabled`|Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network). -`matrix_hookshot_metrics_proxying_enabled`|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. -`matrix_SERVICE_metrics_proxying_enabled`|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. `matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). `matrix_synapse_metrics_proxying_enabled`|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. `matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). `matrix_media_repo_metrics_proxying_enabled`|Set this to `true` to expose media-repo's metrics on `https://matrix.example.com/metrics/matrix-media-repo`. +### Expose metrics of other services/roles + +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 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. + +**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. + +For example, you can enable and expose metrics for [Hookshot](configuring-playbook-bridge-hookshot.md) protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file: + +```yaml +# Expose metrics (locally, on the container network). +matrix_hookshot_metrics_enabled: true + +# Uncomment to expose metrics on https://matrix.example.com/metrics/hookshot. +# matrix_hookshot_metrics_proxying_enabled: true + +# Uncomment to password-protect the metrics for Hookshot. +# matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true + +# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/hookshot`. +# See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users +# matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' +``` + ### Collecting Synapse worker metrics to an external Prometheus server 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`. From 64d9340f70074308d522b4c5983c693e2da69e16 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 01:40:05 +0900 Subject: [PATCH 534/952] Update docs/configuring-playbook-prometheus-grafana.md: add another example for exposing metrics with dedicated credentials for matrix-media-repo Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index de4c2b49c..30488cfc5 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -170,8 +170,6 @@ Name | Description `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. `matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). `matrix_synapse_metrics_proxying_enabled`|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. -`matrix_media_repo_metrics_enabled`|Set this to `true` to make media-repo expose metrics (locally, on the container network). -`matrix_media_repo_metrics_proxying_enabled`|Set this to `true` to expose media-repo's metrics on `https://matrix.example.com/metrics/matrix-media-repo`. ### Expose metrics of other services/roles @@ -198,6 +196,23 @@ matrix_hookshot_metrics_enabled: true # matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' ``` +If you wish to enable and expose metrics for [matrix-media-repo](configuring-playbook-matrix-media-repo.md) protecting them with dedicated credentials, you can add the following configuration to your `vars.yml` file in a similar way: + +```yaml +# Expose metrics (locally, on the container network). +matrix_media_repo_metrics_enabled: true + +# Uncomment to expose metrics on https://matrix.example.com/metrics/matrix-media-repo. +# matrix_media_repo_metrics_proxying_enabled: true + +# Uncomment to password-protect the metrics for matrix-media-repo. +# matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_enabled: true + +# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/matrix-media-repo`. +# See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users +# matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users: '' +``` + ### Collecting Synapse worker metrics to an external Prometheus server 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`. From da8e446e027d71c5773e1f0489561099f8f3b459 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 00:31:19 +0900 Subject: [PATCH 535/952] Update docs/configuring-playbook-prometheus-grafana.md: move some descriptions out of the table Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 30488cfc5..b6943cd4b 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -151,16 +151,18 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network. -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). 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. +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). -When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one. +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. + +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. The following variables may be of interest: Name | Description -----|---------- -`matrix_metrics_exposure_enabled`|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 [this section](#expose-metrics-of-other-services-roles) for exposing metrics on a per-service basis. -`matrix_metrics_exposure_http_basic_auth_enabled`|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. +`matrix_metrics_exposure_enabled`|Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. +`matrix_metrics_exposure_http_basic_auth_enabled`|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). `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). `prometheus_node_exporter_container_labels_traefik_enabled`|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. From bfe86947956111d3d8493f914550f077f63eeaab Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 00:38:46 +0900 Subject: [PATCH 536/952] Update docs/configuring-playbook-prometheus-grafana.md: add the instruction about setting dedicated credentials to each endpoint Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index b6943cd4b..d5f4554df 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -155,7 +155,7 @@ The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`) 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. -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. +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. The following variables may be of interest: From 968129398f499b4ac2407de522bfa269908b39c1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 04:19:35 +0900 Subject: [PATCH 537/952] Update docs/configuring-playbook-prometheus-grafana.md: remove duplicated instruction to refer matrix_metrics_exposure_http_basic_auth_users Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d5f4554df..c64581076 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -165,13 +165,13 @@ Name | Description `matrix_metrics_exposure_http_basic_auth_enabled`|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). `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs. `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network). -`prometheus_node_exporter_container_labels_traefik_enabled`|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. +`prometheus_node_exporter_container_labels_traefik_enabled`|Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. `prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network). -`prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. +`prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network). -`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above. +`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. `matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). -`matrix_synapse_metrics_proxying_enabled`|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. +`matrix_synapse_metrics_proxying_enabled`|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`). ### Expose metrics of other services/roles From 88e946173fba30ac2cd7ae078ad95a73fa945caa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 15:00:39 +0900 Subject: [PATCH 538/952] Update docs/configuring-playbook-prometheus-grafana.md: move descriptions about configuring Synapse metrics out of the table Signed-off-by: Suguru Hirahara --- ...configuring-playbook-prometheus-grafana.md | 27 ++++++++++++++----- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index c64581076..fc5804278 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -170,8 +170,6 @@ Name | Description `prometheus_postgres_exporter_container_labels_traefik_enabled`|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`. `matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network). `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|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`. -`matrix_synapse_metrics_enabled`|Set this to `true` to make Synapse expose metrics (locally, on the container network). -`matrix_synapse_metrics_proxying_enabled`|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`). ### Expose metrics of other services/roles @@ -181,7 +179,25 @@ To password-protect the metrics of a specific role, you can use `matrix_SERVICE_ **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. -For example, you can enable and expose metrics for [Hookshot](configuring-playbook-bridge-hookshot.md) protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file: +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: + +```yaml +# Expose metrics (locally, on the container network). +matrix_synapse_metrics_enabled: true + +# Uncomment to expose metrics on https://matrix.example.com/metrics/synapse/main-process and https://matrix.example.com/metrics/synapse/worker/TYPE-ID. +# Read the section below ("Collecting Synapse worker metrics to an external Prometheus server") if you're running a Synapse worker setup by setting `matrix_synapse_workers_enabled` to true. +# matrix_synapse_metrics_proxying_enabled: true + +# Uncomment to password-protect the metrics for Synapse. +# matrix_synapse_container_labels_public_metrics_middleware_basic_auth_enabled: true + +# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoints. +# See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users +# matrix_synapse_container_labels_public_metrics_middleware_basic_auth_users: '' +``` + +You can enable and expose metrics for [Hookshot](configuring-playbook-bridge-hookshot.md) protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file: ```yaml # Expose metrics (locally, on the container network). @@ -193,7 +209,7 @@ matrix_hookshot_metrics_enabled: true # Uncomment to password-protect the metrics for Hookshot. # matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true -# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/hookshot`. +# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. # See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users # matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' ``` @@ -210,8 +226,7 @@ matrix_media_repo_metrics_enabled: true # Uncomment to password-protect the metrics for matrix-media-repo. # matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_enabled: true -# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/matrix-media-repo`. -# See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users +# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. # matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users: '' ``` From 210a431c823cbde936be4fc616aac0ce1c154ee8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 15:33:29 +0900 Subject: [PATCH 539/952] Update docs for metrics of Hookshot As the document for Hookshot has the section for instrucion about configuring its metrics, this commit moves the instruction to it. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 29 +++++++++++++++---- ...configuring-playbook-prometheus-grafana.md | 17 ----------- 2 files changed, 23 insertions(+), 23 deletions(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 514f6b888..8341ad373 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -127,18 +127,35 @@ For more information, see the documentation in the [default configuration of the 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`. -### Metrics +### Enable metrics + +The playbook can enable and configure the metrics of the service for you. 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. -To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however. +To enable the metrics, add the following configuration to your `vars.yml` file: -**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: +```yaml +# Expose metrics (locally, on the container network). +matrix_hookshot_metrics_enabled: true +``` -- either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true` -- or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true` +**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: -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. +```yaml +matrix_hookshot_metrics_proxying_enabled: true +``` + +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: + +```yaml +matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true +matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' +``` + +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. + +**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. ### Collision with matrix-appservice-webhooks diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index fc5804278..d8a5aca41 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -197,23 +197,6 @@ matrix_synapse_metrics_enabled: true # matrix_synapse_container_labels_public_metrics_middleware_basic_auth_users: '' ``` -You can enable and expose metrics for [Hookshot](configuring-playbook-bridge-hookshot.md) protecting them with dedicated credentials by adding the following configuration to your `vars.yml` file: - -```yaml -# Expose metrics (locally, on the container network). -matrix_hookshot_metrics_enabled: true - -# Uncomment to expose metrics on https://matrix.example.com/metrics/hookshot. -# matrix_hookshot_metrics_proxying_enabled: true - -# Uncomment to password-protect the metrics for Hookshot. -# matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true - -# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. -# See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users -# matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' -``` - If you wish to enable and expose metrics for [matrix-media-repo](configuring-playbook-matrix-media-repo.md) protecting them with dedicated credentials, you can add the following configuration to your `vars.yml` file in a similar way: ```yaml From 39c1c8b925606df45410a4628d048b9727700731 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 18:39:13 +0900 Subject: [PATCH 540/952] Update docs/configuring-playbook-bridge-hookshot.md: move the section for matrix-appservice-webhooks up It should make the section for Grafana more noticiable. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 8341ad373..2f8c96a25 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -127,6 +127,10 @@ For more information, see the documentation in the [default configuration of the 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`. +### Collision with matrix-appservice-webhooks + +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_'`). + ### Enable metrics The playbook can enable and configure the metrics of the service for you. @@ -157,10 +161,6 @@ To `matrix_hookshot_container_labels_metrics_middleware_basic_auth_users`, set t **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. -### Collision with matrix-appservice-webhooks - -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_'`). - ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-hookshot`. From a814d5a499e9412c29abf8d033483e7e4f12a4c6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 18:15:50 +0900 Subject: [PATCH 541/952] Update docs/configuring-playbook-bridge-hookshot.md: add the subsection for enabling Grafana Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 2f8c96a25..b1bd39ab3 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -161,6 +161,12 @@ To `matrix_hookshot_container_labels_metrics_middleware_basic_auth_users`, set t **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. +#### Enable Grafana (optional) + +Probably you wish to enable Grafana along with Prometheus for generating graphs of the metics. + +To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions. + ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-hookshot`. From c0f440a0aa3d7d2672520292f2e20fe90f4881df Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 18:27:18 +0900 Subject: [PATCH 542/952] Update docs/configuring-playbook-bridge-hookshot.md: remove the line for metrics from the URLs table in favor of the section below Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index b1bd39ab3..8aacefd66 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -96,7 +96,6 @@ Unless indicated otherwise, the following endpoints are reachable on your `matri | provisioning | `/hookshot/v1/` | `matrix_hookshot_provisioning_endpoint` | Dimension [provisioning](#provisioning-api) | | appservice | `/hookshot/_matrix/app/` | `matrix_hookshot_appservice_endpoint` | Matrix server | | widgets | `/hookshot/widgetapi/` | `matrix_hookshot_widgets_endpoint` | Widgets | -| metrics | `/metrics/hookshot` | `matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below. | Prometheus | Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly. From 63ff7a08ee1781a876e87db9f39067315fa566b0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 17:55:19 +0900 Subject: [PATCH 543/952] Update docs/configuring-playbook-matrix-media-repo.md: move a note about disabling other media store roles up Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index b832e4b85..a633794d3 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -5,9 +5,8 @@ The playbook can install and configure [matrix-media-repo](https://docs.t2bot.io 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. **Notes**: - +- If MMR is enabled, other media store roles should be disabled (if using Synapse with other media store roles). - 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. - - 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. ## Adjusting the playbook configuration @@ -21,7 +20,7 @@ matrix_media_repo_enabled: true # matrix_media_repo_metrics_enabled: true ``` -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). +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. 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. From 60457af840023cb65fdf238698029658f88bda8a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 17:56:38 +0900 Subject: [PATCH 544/952] Update docs/configuring-playbook-matrix-media-repo.md: remove descriptions about metrics for now Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index a633794d3..a4f1af80a 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -15,13 +15,8 @@ To enable matrix-media-repo, add the following configuration to your `inventory/ ```yaml matrix_media_repo_enabled: true - -# (optional) Turned off by default -# matrix_media_repo_metrics_enabled: true ``` -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. - 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. ### Extending the configuration From 2ffea4fe73b7b53708e481da6af4e37c05bfe694 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 17:57:19 +0900 Subject: [PATCH 545/952] Update docs/configuring-playbook-matrix-media-repo.md: copy metrics section from configuring-playbook-bridge-hookshot.md Signed-off-by: Suguru Hirahara --- .../configuring-playbook-matrix-media-repo.md | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index a4f1af80a..fa0f33eba 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -19,6 +19,42 @@ matrix_media_repo_enabled: true 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. +### Enable metrics + +The playbook can enable and configure the metrics of the service for you. + +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. + +To enable the metrics, add the following configuration to your `vars.yml` file: + +```yaml +# Expose metrics (locally, on the container network). +matrix_hookshot_metrics_enabled: true +``` + +**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: + +```yaml +matrix_hookshot_metrics_proxying_enabled: true +``` + +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: + +```yaml +matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true +matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' +``` + +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. + +**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. + +#### Enable Grafana (optional) + +Probably you wish to enable Grafana along with Prometheus for generating graphs of the metics. + +To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions. + ### Extending the configuration There are some additional things you may wish to configure about the component. From 11d423308806c731cc75b435a6cb189d1ff82549 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 17:58:58 +0900 Subject: [PATCH 546/952] Update docs/configuring-playbook-matrix-media-repo.md: replace variables for Hookshot with ones for MMR Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index fa0f33eba..052cd90c3 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -29,23 +29,23 @@ To enable the metrics, add the following configuration to your `vars.yml` file: ```yaml # Expose metrics (locally, on the container network). -matrix_hookshot_metrics_enabled: true +matrix_media_repo_metrics_enabled: true ``` -**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: +**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: ```yaml -matrix_hookshot_metrics_proxying_enabled: true +matrix_media_repo_metrics_proxying_enabled: true ``` 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: ```yaml -matrix_hookshot_container_labels_metrics_middleware_basic_auth_enabled: true -matrix_hookshot_container_labels_metrics_middleware_basic_auth_users: '' +matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_enabled: true +matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users: '' ``` -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. +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. **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. From 471944a72c8fc0cfbb25cbb72acb40b78c1d7ccc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 18:01:38 +0900 Subject: [PATCH 547/952] Update docs/configuring-playbook-prometheus-grafana.md: remove instructions for setting up enabling and exposing metrics for MMR in favor of the one on the document for it Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index d8a5aca41..e88e31b1e 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -197,22 +197,6 @@ matrix_synapse_metrics_enabled: true # matrix_synapse_container_labels_public_metrics_middleware_basic_auth_users: '' ``` -If you wish to enable and expose metrics for [matrix-media-repo](configuring-playbook-matrix-media-repo.md) protecting them with dedicated credentials, you can add the following configuration to your `vars.yml` file in a similar way: - -```yaml -# Expose metrics (locally, on the container network). -matrix_media_repo_metrics_enabled: true - -# Uncomment to expose metrics on https://matrix.example.com/metrics/matrix-media-repo. -# matrix_media_repo_metrics_proxying_enabled: true - -# Uncomment to password-protect the metrics for matrix-media-repo. -# matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_enabled: true - -# Uncomment and set this part to the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. -# matrix_media_repo_container_labels_traefik_metrics_middleware_basic_auth_users: '' -``` - ### Collecting Synapse worker metrics to an external Prometheus server 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`. From 561ec6d622146d522480c9de81a60f37d2ee8143 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 20:32:30 +0900 Subject: [PATCH 548/952] Update docs/configuring-playbook-synapse.md: add an anchor link to the subsection on the Prometheus document Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 04e33c36b..72666042c 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -172,7 +172,7 @@ The playbook can install and configure Synapse Admin for you. For details about This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse. -To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) +To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles) To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) From 39cd32aa26e37481ba9fca5c11df51f32a18d90e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 22:36:36 +0900 Subject: [PATCH 549/952] Update docs/maintenance-postgres.md: add the warning styling Signed-off-by: Suguru Hirahara --- docs/maintenance-postgres.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index 82c4757c6..ce27e7404 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -28,7 +28,8 @@ To change to another database (for example `synapse`), run `\connect synapse` (o You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;` -**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql). +> [!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). ## Vacuuming PostgreSQL From ea18d9d87ec76a14ee1b7f7a8ccd50631c01b551 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Feb 2025 22:43:06 +0900 Subject: [PATCH 550/952] Remove blank lines around lists titled with "Table of contents" Signed-off-by: Suguru Hirahara --- docs/maintenance-postgres.md | 5 ----- docs/registering-users.md | 1 - 2 files changed, 6 deletions(-) diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index ce27e7404..2c69d038e 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -3,15 +3,10 @@ This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix. Table of contents: - - [Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries - - [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) - - [Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup - - [Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**. - - [Tuning PostgreSQL](#tuning-postgresql) to make it run faster ## Getting a database terminal diff --git a/docs/registering-users.md b/docs/registering-users.md index 2972378b6..d6b606055 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -3,7 +3,6 @@ This documentation page tells you how to create user accounts on your Matrix server. Table of contents: - - [Registering users](#registering-users) - [Registering users manually](#registering-users-manually) - [Managing users via a Web UI](#managing-users-via-a-web-ui) From 5eb2e28ecae95c169731e48556c4b785a9e9cb4f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 11 Feb 2025 14:05:13 +0900 Subject: [PATCH 551/952] Add the copyright header for reusing the document for the MASH project This is preparation for the document to be copied to the MASH project at https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index aca22c2f6..8acc3d9ba 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -1,3 +1,13 @@ + + # Setting up BorgBackup (optional) The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you. From 86beae48634e0b45a220073ad5dea28bedd8ce29 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 11 Feb 2025 14:58:10 +0900 Subject: [PATCH 552/952] Update docs/configuring-playbook-backup-borg.md: sync the description with the document for the MASH project Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 8acc3d9ba..ca75f80f7 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -22,7 +22,7 @@ You will need a remote server where BorgBackup will store the backups. There are ### Check the Postgres version -By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. +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 by default. 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). From 44d5228011ed0f6adcb6d8d7cb91ffa27c444e5e Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 11 Feb 2025 09:08:46 +0000 Subject: [PATCH 553/952] Update ajbura/cinny Docker tag to v4.3.0 --- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 86e5d9ef9..7016240c4 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -7,7 +7,7 @@ matrix_client_cinny_container_image_self_build: false matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git" # renovate: datasource=docker depName=ajbura/cinny -matrix_client_cinny_version: v4.2.3 +matrix_client_cinny_version: v4.3.0 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_container_global_registry_prefix }}" matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}" From 34cded9b8d8f1fc43acaac880466c2d756ba3271 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 11 Feb 2025 09:08:51 +0000 Subject: [PATCH 554/952] Update joseluisq/static-web-server Docker tag to v2.36.0 --- roles/custom/matrix-cactus-comments-client/defaults/main.yml | 2 +- roles/custom/matrix-static-files/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 7c5b15bfc..e8ff73d08 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -13,7 +13,7 @@ matrix_cactus_comments_client_public_path: "{{ matrix_cactus_comments_client_bas matrix_cactus_comments_client_public_path_file_permissions: "0644" # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_cactus_comments_client_version: 2.35.0 +matrix_cactus_comments_client_version: 2.36.0 matrix_cactus_comments_client_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}" diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index 248062ab2..e31c9b75b 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -8,7 +8,7 @@ matrix_static_files_enabled: true matrix_static_files_identifier: matrix-static-files # renovate: datasource=docker depName=joseluisq/static-web-server -matrix_static_files_version: 2.35.0 +matrix_static_files_version: 2.36.0 matrix_static_files_base_path: "{{ matrix_base_data_path }}/{{ 'static-files' if matrix_static_files_identifier == 'matrix-static-files' else matrix_static_files_identifier }}" matrix_static_files_config_path: "{{ matrix_static_files_base_path }}/config" From 6dfe5d53497252deeb927f22c00a998add22e70d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edward=20And=C3=B2?= <2989690+edwardando@users.noreply.github.com> Date: Tue, 11 Feb 2025 10:03:20 +0000 Subject: [PATCH 555/952] Update configuring-well-known.md add 302 redirect option as well as reverse-proxy --- docs/configuring-well-known.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index 58bd1615b..cd387bc00 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -97,7 +97,7 @@ This is relatively easy to do and possibly your only choice if you can only host This option is less fragile and generally better. -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`). +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`). 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. From 38b0e86a2ecc8e92fac15cabb3a96fa7d9f44e95 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 11 Feb 2025 13:24:26 +0000 Subject: [PATCH 556/952] Update ghcr.io/element-hq/synapse Docker tag to v1.124.0 --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 69ceb6cd7..81508bb48 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.123.0 +matrix_synapse_version: v1.124.0 matrix_synapse_username: '' matrix_synapse_uid: '' From 2a289606931ab5d5596d0adf91725f1753ce312f Mon Sep 17 00:00:00 2001 From: Aine <97398200+aine-etke@users.noreply.github.com> Date: Tue, 11 Feb 2025 17:36:30 +0200 Subject: [PATCH 557/952] Element Web v1.11.92 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index c970b3f38..d536b55e4 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.91 +matrix_client_element_version: v1.11.92 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" From 930029ccda8c4d90ce230dfa740c0cab15a3c733 Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 11 Feb 2025 17:38:11 +0200 Subject: [PATCH 558/952] borgmatic v1.9.10 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 3f6fea07a..9ec613089 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.9-0 + version: v1.4.0-1.9.10-0 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From 44de5d91f18cb33e91eceae13743d6df2c50f6b5 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 11 Feb 2025 15:38:53 +0000 Subject: [PATCH 559/952] Update ghcr.io/matrix-org/rageshake Docker tag to v1.14.0 --- roles/custom/matrix-rageshake/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index f104cbebd..1c3d059c1 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -17,7 +17,7 @@ matrix_rageshake_path_prefix: / # There are no stable container image tags yet. # See: https://github.com/matrix-org/rageshake/issues/69 # renovate: datasource=docker depName=ghcr.io/matrix-org/rageshake -matrix_rageshake_version: 1.13.0 +matrix_rageshake_version: 1.14.0 matrix_rageshake_base_path: "{{ matrix_base_data_path }}/rageshake" matrix_rageshake_config_path: "{{ matrix_rageshake_base_path }}/config" From 414445b6bf09d29dc1075e8954fb78a66d26a53a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 12 Feb 2025 03:54:34 +0900 Subject: [PATCH 560/952] Update docs/configuring-playbook-backup-borg.md: replace the instruction with the reference to the document copied to the MASH project Now that the document for setting up BorgBackup has been moved to the MASH project (https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg) it is sensible to remove the details in favor of it. Because it may as well be noted that the document becomes available locally once the Ansible role is fetched, I think the document itself should not be deleted from the repository. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 148 +---------------------- 1 file changed, 3 insertions(+), 145 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index ca75f80f7..135ca8501 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -14,148 +14,6 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. -## Prerequisites - -### Set up a remote server for storing backups - -You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com). - -### Check the Postgres version - -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 by default. - -Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml). - -An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable. - -### Create a new SSH key - -Run the command below on any machine to create a new SSH key: - -```sh -ssh-keygen -t ed25519 -N '' -f matrix-borg-backup -C matrix -``` - -You don't need to place the key in the `.ssh` folder. - -### Add the public key - -Next, add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server. - -If you are using a hosted solution, follow their instructions. If you have your own server, copy the key to it with the command like below: - -```sh -# Example to append the new PUBKEY contents, where: -# - PUBKEY is path to the public key -# - USER is a ssh user on a provider / server -# - HOST is a ssh host of a provider / server -cat PUBKEY | ssh USER@HOST 'dd of=.ssh/authorized_keys oflag=append conv=notrunc' -``` - -The **private** key needs to be added to `backup_borg_ssh_key_private` on your `inventory/host_vars/matrix.example.com/vars.yml` file as below. - -## Adjusting the playbook configuration - -To enable BorgBackup, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -backup_borg_enabled: true - -# Set the repository location, where: -# - USER is a ssh user on a provider / server -# - HOST is a ssh host of a provider / server -# - REPO is a BorgBackup repository name -backup_borg_location_repositories: - - ssh://USER@HOST/./REPO - -# Generate a strong password used for encrypting backups. You can create one with a command like `pwgen -s 64 1`. -backup_borg_storage_encryption_passphrase: "PASSPHRASE" - -# Add the content of the **private** part of the SSH key you have created. -# Note: the whole key (all of its belonging lines) under the variable needs to be indented with 2 spaces. -backup_borg_ssh_key_private: | - -----BEGIN OPENSSH PRIVATE KEY----- - TG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2NpbmcgZW - xpdCwgc2VkIGRvIGVpdXNtb2QgdGVtcG9yIGluY2lkaWR1bnQgdXQgbGFib3JlIGV0IGRv - bG9yZSBtYWduYSBhbGlxdWEuIFV0IGVuaW0gYWQgbWluaW0gdmVuaWFtLCBxdWlzIG5vc3 - RydWQgZXhlcmNpdGF0aW9uIHVsbGFtY28gbGFib3JpcyBuaXNpIHV0IGFsaXF1aXAgZXgg - ZWEgY29tbW9kbyBjb25zZXF1YXQuIA== - -----END OPENSSH PRIVATE KEY----- -``` - -**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. - -### Set backup archive name (optional) - -You can specify the backup archive name format. To set it, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -backup_borg_storage_archive_name_format: matrix-{now:%Y-%m-%d-%H%M%S} -``` - -### Configure retention policy (optional) - -It is also possible to configure a retention strategy. To configure it, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -backup_borg_retention_keep_hourly: 0 -backup_borg_retention_keep_daily: 7 -backup_borg_retention_keep_weekly: 4 -backup_borg_retention_keep_monthly: 12 -backup_borg_retention_keep_yearly: 2 -``` - -### Edit the schedule (optional) - -By default the task will run 4 a.m. every day based on the `backup_borg_schedule` variable. It is defined in the format of systemd timer calendar. - -To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -backup_borg_schedule: "*-*-* 04:00:00" -``` - -**Note**: the actual job may run with a delay. See `backup_borg_schedule_randomized_delay_sec` [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/f5d5b473d48c6504be10b3d946255ef5c186c2a6/defaults/main.yml#L50) for its default value. - -### Set include and/or exclude directories (optional) - -`backup_borg_location_source_directories` defines the list of directories to back up. It's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. - -You might also want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable. - -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `backup_borg_configuration_extension_yaml` variable - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start -``` - -The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - -`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - -## Usage - -After installation, `backup-borg` will run automatically every day at `04:00:00` (as defined in `backup_borg_schedule` by default). - -### Manually start the task - -Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration. - -If you want to run it immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`. - -This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable. - -## Troubleshooting - -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu backup-borg`. +For details about configuring and installing it, you can check them via: +- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) +- `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have fetched the Ansible roles From 8b129eefba200a4b281899ab83812f85af2ebe40 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 12 Feb 2025 14:42:13 +0900 Subject: [PATCH 561/952] Update docs/configuring-playbook-postgres-backup.md: add the copyright header This is a preparation to copy the document to its own repository at the MASH project (https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-postgres-backup.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 08f88b8bf..39f51835f 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -1,3 +1,11 @@ + + # Setting up postgres backup (optional) 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. From 4ee2f6ffea6b9682f5b676669b0d3bc6711fa8f1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 13 Feb 2025 00:31:30 +0900 Subject: [PATCH 562/952] Update docs/configuring-playbook-postgres-backup.md: replace the instruction with the reference to the document copied to the MASH project This follows the change for docs on BorgBackup with 414445b6bf09d29dc1075e8954fb78a66d26a53a. The document on the MASH project is available at https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-postgres-backup.md | 41 ++------------------ 1 file changed, 4 insertions(+), 37 deletions(-) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 39f51835f..54e058f00 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -10,41 +10,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later 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. -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. +For details about configuring and installing it, you can check them via: +- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) +- `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have fetched the Ansible roles -## Adjusting the playbook configuration - -To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: - -```yaml -postgres_backup_enabled: true -``` - -Refer to the table below for additional configuration variables and their default values. - -| Name | Default value | Description | -| :-------------------------------- | :--------------------------- | :--------------------------------------------------------------- | -|`postgres_backup_enabled`|`false`|Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups| -|`postgres_backup_schedule`| `'@daily'` |Cron-schedule specifying the interval between postgres backups.| -|`postgres_backup_keep_days`|`7`|Number of daily backups to keep| -|`postgres_backup_keep_weeks`|`4`|Number of weekly backups to keep| -|`postgres_backup_keep_months`|`12`|Number of monthly backups to keep| -|`postgres_backup_base_path` | `"{{ matrix_base_data_path }}/postgres-backup"` | Base path for postgres-backup. Also see `postgres_backup_data_path` | -|`postgres_backup_data_path` | `"{{ postgres_backup_base_path }}/data"` | Storage path for postgres-backup database backups | - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start -``` - -The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` - -`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. - -## Troubleshooting - -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-postgres-backup`. +**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. From 3620870173540097230e5ae3ef47a4779c9134b0 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 12 Feb 2025 15:51:55 +0000 Subject: [PATCH 563/952] Update dependency myst-parser to v4.0.1 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index cf48bd5a0..9a2b21645 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -12,7 +12,7 @@ markdown-it-py==3.0.0 MarkupSafe==3.0.2 mdit-py-plugins==0.4.2 mdurl==0.1.2 -myst-parser==4.0.0 +myst-parser==4.0.1 packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 From 9f17f748b1c1979f381f4b69b7630e73f39b6361 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 13 Feb 2025 06:30:07 +0200 Subject: [PATCH 564/952] Upgrade ntfy (v2.11.0-0 -> v2.11.0-1) Ref: https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/pull/2 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 9ec613089..47990bf1f 100644 --- a/requirements.yml +++ b/requirements.yml @@ -28,7 +28,7 @@ version: v10008-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git - version: v2.11.0-0 + version: v2.11.0-1 name: ntfy - src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git version: 201c939eed363de269a83ba29784fc3244846048 From c27fb2a832e69d3fb7bfd49751db1d00d95ff91b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 12 Feb 2025 19:07:46 +0900 Subject: [PATCH 565/952] =?UTF-8?q?Fix=20capitalization:=20postgres=20?= =?UTF-8?q?=E2=86=92=20Postgres?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 2 +- docs/configuring-playbook-matrix-media-repo.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- docs/configuring-playbook.md | 2 +- docs/maintenance-postgres.md | 2 +- docs/updating-users-passwords.md | 2 +- roles/custom/matrix-bot-maubot/templates/config.yaml.j2 | 2 +- roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml | 2 +- roles/custom/matrix-synapse-auto-compressor/defaults/main.yml | 4 ++-- .../matrix-synapse/templates/synapse/homeserver.yaml.j2 | 2 +- .../matrix_playbook_migration/tasks/validate_config.yml | 2 +- 11 files changed, 12 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4dcd99ba6..f850d47e7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2144,7 +2144,7 @@ matrix_coturn_tls_v1_1_enabled: true Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local). -Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md). +Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md). # 2021-04-03 diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 052cd90c3..33dd5ce1a 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -66,7 +66,7 @@ Take a look at: Here is a list of additional common configuration options: ```yaml -# The postgres database pooling options +# The Postgres database pooling options # The maximum number of connects to hold open. More of these allow for more concurrent # processes to happen. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 54e058f00..27aafd1ae 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -6,7 +6,7 @@ SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> -# Setting up postgres backup (optional) +# Setting up Postgres backup (optional) 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. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 30e8c808d..31d443616 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -206,7 +206,7 @@ Services that help you in administrating and monitoring your Matrix installation - Backups: - [Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database - - [Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files) + - [Setting up Postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files) ### Other specialized services diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index 2c69d038e..569d5fd4d 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -47,7 +47,7 @@ Example playbook invocations: ## Backing up PostgreSQL -To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md). +To automatically make Postgres database backups on a fixed schedule, see [Setting up Postgres backup](configuring-playbook-postgres-backup.md). To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server: diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index aecd038ef..87a844bb8 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -22,7 +22,7 @@ You can manually generate the password hash by using the command-line after **SS docker exec -it matrix-synapse /usr/local/bin/hash_password -c /data/homeserver.yaml ``` -and then connecting to the postgres server and executing: +and then connecting to the Postgres server and executing: ```sql UPDATE users SET password_hash = '' WHERE name = '@alice:example.com'; diff --git a/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 index 8da34c9ed..73c75ce58 100644 --- a/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 +++ b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 @@ -28,7 +28,7 @@ plugin_directories: # Configuration for storing plugin databases plugin_databases: # Some plugins still require sqlite, so configure a path here. - # postgres will be used if supported. + # Postgres will be used if supported. sqlite: /data/dbs postgres: default diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml index 030ac871f..b46df5994 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml @@ -108,7 +108,7 @@ matrix_mx_puppet_slack_login_shared_secret: '' matrix_mx_puppet_slack_presence_enabled: true matrix_mx_puppet_slack_presence_interval: 5000 -# Database configuration, role uses 'sqlite' per default but playbook sets up postgres by default +# Database configuration, role uses 'sqlite' per default but playbook sets up Postgres by default matrix_mx_puppet_slack_database_engine: sqlite matrix_mx_puppet_slack_sqlite_database_path_local: "{{ matrix_mx_puppet_slack_data_path }}/database.db" diff --git a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml index 212213d64..020a447c5 100644 --- a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml +++ b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml @@ -8,11 +8,11 @@ matrix_synapse_auto_compressor_enabled: true # renovate: datasource=docker depName=registry.gitlab.com/etke.cc/rust-synapse-compress-state matrix_synapse_auto_compressor_version: v0.1.4 -# note: UID/GID better to match the UID/GID of the postgres container, but it doesn't really matter, as volumes are not used here +# note: UID/GID better to match the UID/GID of the Postgres container, but it doesn't really matter, as volumes are not used here matrix_synapse_auto_compressor_uid: '' matrix_synapse_auto_compressor_gid: '' -# note: the postgres image version doesn't matter, as it is used for a SQL script that doesn't use any specific features +# note: the Postgres image version doesn't matter, as it is used for a SQL script that doesn't use any specific features matrix_synapse_auto_compressor_postgres_image: "postgres" matrix_synapse_auto_compressor_base_path: "{{ matrix_base_data_path }}/synapse-auto-compressor" diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 index 457726774..6c4624919 100644 --- a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 @@ -837,7 +837,7 @@ caches: # before reconnecting. Defaults to 0, which means no limit. # # 'allow_unsafe_locale' is an option specific to Postgres. Under the default behavior, Synapse will refuse to -# start if the postgres db is set to a non-C locale. You can override this behavior (which is *not* recommended) +# start if the Postgres db is set to a non-C locale. You can override this behavior (which is *not* recommended) # by setting 'allow_unsafe_locale' to true. Note that doing so may corrupt your database. You can find more information # here: https://matrix-org.github.io/synapse/latest/postgres.html#fixing-incorrect-collate-or-ctype and here: # https://wiki.postgresql.org/wiki/Locale_data_changes diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 4d61f765f..272011c88 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -423,7 +423,7 @@ - name: (Deprecation) Catch and report devture_postgres variables ansible.builtin.fail: msg: |- - The postgres role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-postgres). + The Postgres role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-postgres). The new role is pretty much the same, but uses differently named variables. Please change your configuration (vars.yml) to rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`). From f4f666e5ecda1e2db6e7c4b6ba57d8ac93039a9c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 13 Feb 2025 00:20:29 +0900 Subject: [PATCH 566/952] Update docs/container-images.md: add an entry for postgres-backup-local Signed-off-by: Suguru Hirahara --- docs/container-images.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/container-images.md b/docs/container-images.md index efed979c2..fbafe02e0 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -125,6 +125,7 @@ Services that help you in administrating and monitoring your Matrix installation | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) | ❌ | Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards) | | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional) | [martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter) | ❌ | Addon for Prometheus that gathers access logs from various nginx reverse-proxies | | [Borg](configuring-playbook-backup-borg.md) | (N/A) | ❌ | Backups | +| [postgres-backup-local](configuring-playbook-postgres-backup.md) | [prodrigestivill/postgres-backup-local](https://hub.docker.com/r/prodrigestivill/postgres-backup-local) | ❌ | Create automatic database backups | | [rageshake](configuring-playbook-rageshake.md) | [matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake) | ❌ | Bug report server | | [synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md) | Self-building | ❌ | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. | From 3c9067c4c2d640bf672cd6e5fb5c4d6c14e77716 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 13 Feb 2025 01:40:14 +0900 Subject: [PATCH 567/952] Update docs/configuring-playbook-etherpad.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index f6664f19d..0f151d3db 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -1,3 +1,15 @@ + + # Setting up Etherpad (optional) The playbook can install and configure [Etherpad](https://etherpad.org) for you. From 5c874f036d48abd050be3647fe5ccc3f85c4eb17 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 14 Feb 2025 09:59:22 +0200 Subject: [PATCH 568/952] Upgrade Etherpad (v2.2.6-0 -> v2.2.7-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 47990bf1f..cc083ba7c 100644 --- a/requirements.yml +++ b/requirements.yml @@ -16,7 +16,7 @@ version: 129c8590e106b83e6f4c259649a613c6279e937a name: docker_sdk_for_python - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git - version: v2.2.6-0 + version: v2.2.7-0 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git version: v4.98-r0-4-0 From ed673bf07152503c29ab2bad9b5ae74dfdc21c34 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 14 Feb 2025 10:03:41 +0200 Subject: [PATCH 569/952] Comment-out `claims_imports.displayname` for matrix-authentication-service Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4058 --- docs/configuring-playbook-matrix-authentication-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index ce5c7aa5d..0c86096b6 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -242,7 +242,7 @@ matrix_authentication_service_config_upstream_oauth2_providers: #action: force #template: "{% raw %}{{ user.preferred_username }}{% endraw %}" # The display name is the user's display name. - displayname: + #displayname: #action: suggest #template: "{% raw %}{{ user.name }}{% endraw %}" # An email address to import. From 15f7f41afe116aae5193ce44bd73b4867e112935 Mon Sep 17 00:00:00 2001 From: akdk7 <97784161+akdk7@users.noreply.github.com> Date: Fri, 14 Feb 2025 09:23:36 +0100 Subject: [PATCH 570/952] =?UTF-8?q?This=20push=20request=20is=20about=20ha?= =?UTF-8?q?ndling=20Traefik=20ipallowlist=20to=20synapse-ad=E2=80=A6=20(#4?= =?UTF-8?q?063)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * This push request is about handling Traefik ipallowlist to synapse-admin application. It's my first push request. If I forgot something please let me know. :-) * Changed position of variable and naming for better expandebility of traefik options * Remove useless `noqa var-naming` comment and too many blank lines at the end of the file --------- Co-authored-by: AkDk7 Co-authored-by: Slavi Pantaleev --- roles/custom/matrix-synapse-admin/defaults/main.yml | 5 +++++ roles/custom/matrix-synapse-admin/templates/labels.j2 | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 9fcf9532e..50ebe9098 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -49,6 +49,11 @@ matrix_synapse_admin_container_labels_traefik_priority: 0 matrix_synapse_admin_container_labels_traefik_entrypoints: web-secure matrix_synapse_admin_container_labels_traefik_tls: "{{ matrix_synapse_admin_container_labels_traefik_entrypoints != 'web' }}" matrix_synapse_admin_container_labels_traefik_tls_certResolver: default # noqa var-naming +# This setting is to define a list ip addresses to allow access to synapse-admin. +# Each IP address should be in CIDR format, e.g. xxx.xxx.xxx.xxx/xx. +# For more information, see: https://doc.traefik.io/traefik/middlewares/http/ipallowlist/ +# If the list is empty, all IP addresses are allowed. +matrix_synapse_admin_container_labels_traefik_ipallowlist_sourcerange: [] # Controls which additional headers to attach to all HTTP responses. # To add your own headers, use `matrix_synapse_admin_container_labels_traefik_additional_response_headers_custom` diff --git a/roles/custom/matrix-synapse-admin/templates/labels.j2 b/roles/custom/matrix-synapse-admin/templates/labels.j2 index b4e973e00..eeb29756e 100644 --- a/roles/custom/matrix-synapse-admin/templates/labels.j2 +++ b/roles/custom/matrix-synapse-admin/templates/labels.j2 @@ -9,6 +9,11 @@ traefik.http.services.matrix-synapse-admin.loadbalancer.server.port=80 {% set middlewares = [] %} +{% if matrix_synapse_admin_container_labels_traefik_ipallowlist_sourcerange | length > 0 %} +traefik.http.middlewares.matrix-synapse-admin-ipallowlist.ipallowlist.sourcerange={{ matrix_synapse_admin_container_labels_traefik_ipallowlist_sourcerange | join(',') }} +{% set middlewares = middlewares + ['matrix-synapse-admin-ipallowlist'] %} +{% endif %} + {% if matrix_synapse_admin_container_labels_traefik_path_prefix != '/' %} traefik.http.middlewares.matrix-synapse-admin-slashless-redirect.redirectregex.regex=({{ matrix_synapse_admin_container_labels_traefik_path_prefix | quote }})$ traefik.http.middlewares.matrix-synapse-admin-slashless-redirect.redirectregex.replacement=${1}/ From e521ffca80e80f760c9be69787e603f6805c674c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 13 Feb 2025 23:16:50 +0900 Subject: [PATCH 571/952] Make docs/configuring-playbook-etherpad.md slim - Add links to the role at MASH project and its document - Replace common instructions with the links to the role at MASH project Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 62 +++++---------------------- 1 file changed, 11 insertions(+), 51 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 0f151d3db..79c1273fc 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -18,6 +18,8 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. +This Ansible role for Etherpad is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). + ## Adjusting DNS records By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`. @@ -30,12 +32,14 @@ To enable Etherpad, add the following configuration to your `inventory/host_vars ```yaml etherpad_enabled: true - -# Uncomment and adjust this part if you'd like to enable the admin web UI -# etherpad_admin_username: YOUR_USERNAME_HERE -# etherpad_admin_password: YOUR_PASSWORD_HERE ``` +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. + +For details about configuring Etherpad per your preference (such as [enabling the admin web UI](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#enable-admin-web-ui-optional)), you can check them via: +- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) +- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles + ### Adjusting the Etherpad URL (optional) By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. @@ -55,30 +59,6 @@ After changing the domain, **you may need to adjust your DNS** records to point If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. -### Configure the default text (optional) - -You can also edit the default text on a new pad with the variable `etherpad_default_pad_text`. - -To do so, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -# Note: the whole text (all of its belonging lines) under the variable needs to be indented with 2 spaces. -etherpad_default_pad_text: | - Welcome to Etherpad! - - This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents! - - Get involved with Etherpad at https://etherpad.org -``` - -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- [etherpad role](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/defaults/main.yml) for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `etherpad_configuration_extension_json` variable - ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: @@ -96,21 +76,13 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. -- If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password. - ## Usage -The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`. +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`. If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url-optional) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before using it. -### Managing / Deleting old pads - -If you want to manage and remove old unused pads from Etherpad, you will first need to create the Etherpad admin user as described above. - -After logging in to the admin web UI, go to the plugin manager page, and install the `adminpads2` plugin. - -Once the plugin is installed, you should have a "Manage pads" section in the UI. +💡 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 document. ### Integrating a Etherpad widget in a room @@ -120,16 +92,4 @@ To integrate a standalone Etherpad in a room, create your pad by visiting `https ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-etherpad`. - -### Increase logging verbosity - -The default logging level for this component is `WARN`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: - -```yaml -# Valid values: ERROR, WARN, INFO, DEBUG -etherpad_configuration_extension_json: | - { - "loglevel": "DEBUG", - } -``` +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 document for details. From 39f0239be23a982bf6105b2cf067b8c4c2a3fa58 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 14 Feb 2025 17:34:01 +0900 Subject: [PATCH 572/952] Update docs/configuring-playbook-jitsi.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 48c7516c7..280f85d3c 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -1,3 +1,19 @@ + + # Setting up the Jitsi video-conferencing platform (optional) The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you. From 541b46cf8fba802f3e714adf6ea2a1d1c160c42f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 15 Feb 2025 16:34:42 +0900 Subject: [PATCH 573/952] Add the comment block around the variable Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 79c1273fc..772e37e97 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -31,7 +31,19 @@ When setting, replace `example.com` with your own. To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml +######################################################################## +# # +# etherpad # +# # +######################################################################## + etherpad_enabled: true + +######################################################################## +# # +# /etherpad # +# # +######################################################################## ``` 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. From 91d991cac6d497f0383a31a2c0e760953716b427 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 15 Feb 2025 16:27:39 +0900 Subject: [PATCH 574/952] Add a section for creating admin user Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 772e37e97..ad55d3b9c 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -48,10 +48,18 @@ etherpad_enabled: true 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. -For details about configuring Etherpad per your preference (such as [enabling the admin web UI](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#enable-admin-web-ui-optional)), you can check them via: +For details about configuring Etherpad per your preference, you can check them via: - [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) - `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles +### Create admin user (optional) + +You probably might want to enable authentication to disallow anonymous access to your Etherpad. + +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. + +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 document for details about how to create the admin user. + ### Adjusting the Etherpad URL (optional) By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one. From afb97e18ac3595753f6948fe686b6b10ebf20550 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 16 Feb 2025 12:01:11 +0200 Subject: [PATCH 575/952] Make matrix-coturn role respect `devture_systemd_docker_base_ipv6_enabled` --- roles/custom/matrix-coturn/tasks/setup_install.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/custom/matrix-coturn/tasks/setup_install.yml b/roles/custom/matrix-coturn/tasks/setup_install.yml index 30aa742cd..9349c7be0 100644 --- a/roles/custom/matrix-coturn/tasks/setup_install.yml +++ b/roles/custom/matrix-coturn/tasks/setup_install.yml @@ -97,6 +97,7 @@ - name: Ensure coturn network is created in Docker when: matrix_coturn_container_network not in ['', 'host'] community.docker.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" name: "{{ matrix_coturn_container_network }}" driver: bridge driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" From a2cbaf21f208f0dda16858e9a1c9d42c4ee0a5ce Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 16 Feb 2025 12:02:51 +0200 Subject: [PATCH 576/952] Upgrade exim-relay (v4.98-r0-4-0 -> v4.98-r0-4-1) to make it respect `devture_systemd_docker_base_ipv6_enabled` --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index cc083ba7c..0238d4ef0 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-0 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98-r0-4-0 + version: v4.98-r0-4-1 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.1-0 From 9e11da7829fe2b04f521fb5f4a74f5c568b06578 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 16 Feb 2025 12:04:55 +0200 Subject: [PATCH 577/952] Upgrade Valkey (v8.0.1-0 -> v8.0.1-1) to make it respect `devture_systemd_docker_base_ipv6_enabled` --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 0238d4ef0..047dbf3ac 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,5 +70,5 @@ version: v2.8.3-5 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git - version: v8.0.1-0 + version: v8.0.1-1 name: valkey From a0ae269051c2132f87300f2490671eeb9be68a63 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 16 Feb 2025 18:36:59 +0000 Subject: [PATCH 578/952] Update dock.mau.dev/mautrix/meta Docker tag to v0.4.4 --- .../matrix-bridge-mautrix-meta-instagram/defaults/main.yml | 2 +- .../matrix-bridge-mautrix-meta-messenger/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml index 848e86bde..a4f6abf90 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml @@ -13,7 +13,7 @@ matrix_mautrix_meta_instagram_enabled: true matrix_mautrix_meta_instagram_identifier: matrix-mautrix-meta-instagram # renovate: datasource=docker depName=dock.mau.dev/mautrix/meta -matrix_mautrix_meta_instagram_version: v0.4.3 +matrix_mautrix_meta_instagram_version: v0.4.4 matrix_mautrix_meta_instagram_base_path: "{{ matrix_base_data_path }}/mautrix-meta-instagram" matrix_mautrix_meta_instagram_config_path: "{{ matrix_mautrix_meta_instagram_base_path }}/config" diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml index ca951a333..1f4dc54be 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml @@ -13,7 +13,7 @@ matrix_mautrix_meta_messenger_enabled: true matrix_mautrix_meta_messenger_identifier: matrix-mautrix-meta-messenger # renovate: datasource=docker depName=dock.mau.dev/mautrix/meta -matrix_mautrix_meta_messenger_version: v0.4.3 +matrix_mautrix_meta_messenger_version: v0.4.4 matrix_mautrix_meta_messenger_base_path: "{{ matrix_base_data_path }}/mautrix-meta-messenger" matrix_mautrix_meta_messenger_config_path: "{{ matrix_mautrix_meta_messenger_base_path }}/config" From 4a0855db0ad1b43a58dcb93e635177090f09feb1 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 16 Feb 2025 18:37:02 +0000 Subject: [PATCH 579/952] Update dock.mau.dev/mautrix/whatsapp Docker tag to v0.11.3 --- roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml index 88b40dd81..4711262fa 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml @@ -9,7 +9,7 @@ matrix_mautrix_whatsapp_container_image_self_build_repo: "https://mau.dev/mautri matrix_mautrix_whatsapp_container_image_self_build_branch: "{{ 'master' if matrix_mautrix_whatsapp_version == 'latest' else matrix_mautrix_whatsapp_version }}" # renovate: datasource=docker depName=dock.mau.dev/mautrix/whatsapp -matrix_mautrix_whatsapp_version: v0.11.2 +matrix_mautrix_whatsapp_version: v0.11.3 # See: https://mau.dev/mautrix/whatsapp/container_registry matrix_mautrix_whatsapp_docker_image: "{{ matrix_mautrix_whatsapp_docker_image_name_prefix }}mautrix/whatsapp:{{ matrix_mautrix_whatsapp_version }}" From 9c52331da6574ebdcaebfa896e34249de8aa3d2a Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 16 Feb 2025 22:27:19 +0000 Subject: [PATCH 580/952] Update dock.mau.dev/mautrix/signal Docker tag to v0.8.0 --- roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index f4e754a41..53b5de4da 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -9,7 +9,7 @@ matrix_mautrix_signal_container_image_self_build_repo: "https://mau.dev/mautrix/ matrix_mautrix_signal_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_signal_version == 'latest' else matrix_mautrix_signal_version }}" # renovate: datasource=docker depName=dock.mau.dev/mautrix/signal -matrix_mautrix_signal_version: v0.7.5 +matrix_mautrix_signal_version: v0.8.0 # See: https://mau.dev/mautrix/signal/container_registry matrix_mautrix_signal_docker_image: "{{ matrix_mautrix_signal_docker_image_name_prefix }}mautrix/signal:{{ matrix_mautrix_signal_docker_image_tag }}" From 245192ff7f781532f2a1f02af18879457cea8a0f Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 17 Feb 2025 02:56:08 +0000 Subject: [PATCH 581/952] Update ajbura/cinny Docker tag to v4.3.2 --- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 7016240c4..cae8c5727 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -7,7 +7,7 @@ matrix_client_cinny_container_image_self_build: false matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git" # renovate: datasource=docker depName=ajbura/cinny -matrix_client_cinny_version: v4.3.0 +matrix_client_cinny_version: v4.3.2 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_container_global_registry_prefix }}" matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}" From a2111dece7118d38e0bb6c63ae81346717fd52b8 Mon Sep 17 00:00:00 2001 From: Aine <97398200+aine-etke@users.noreply.github.com> Date: Mon, 17 Feb 2025 09:15:15 +0000 Subject: [PATCH 582/952] add FluffyChat (#4068) * add FluffyChat * capitalization * Update group_vars/matrix_servers Co-authored-by: Slavi Pantaleev * fix link in readme --------- Co-authored-by: Slavi Pantaleev --- README.md | 1 + ...figuring-playbook-client-fluffychat-web.md | 59 ++++++++ group_vars/matrix_servers | 33 +++++ roles/custom/matrix-base/defaults/main.yml | 3 + .../defaults/main.yml | 137 ++++++++++++++++++ .../matrix-client-fluffychat/tasks/main.yml | 26 ++++ .../tasks/self_check.yml | 24 +++ .../tasks/setup_install.yml | 70 +++++++++ .../tasks/setup_uninstall.yml | 25 ++++ .../tasks/validate_config.yml | 29 ++++ .../templates/labels.j2 | 46 ++++++ .../matrix-client-fluffychat.service.j2 | 48 ++++++ setup.yml | 1 + 13 files changed, 502 insertions(+) create mode 100644 docs/configuring-playbook-client-fluffychat-web.md create mode 100644 roles/custom/matrix-client-fluffychat/defaults/main.yml create mode 100644 roles/custom/matrix-client-fluffychat/tasks/main.yml create mode 100644 roles/custom/matrix-client-fluffychat/tasks/self_check.yml create mode 100644 roles/custom/matrix-client-fluffychat/tasks/setup_install.yml create mode 100644 roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml create mode 100644 roles/custom/matrix-client-fluffychat/tasks/validate_config.yml create mode 100644 roles/custom/matrix-client-fluffychat/templates/labels.j2 create mode 100644 roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 diff --git a/README.md b/README.md index 4fad24e8c..9806e2caf 100644 --- a/README.md +++ b/README.md @@ -65,6 +65,7 @@ Web clients for Matrix that you can host on your own domains. | [Hydrogen](https://github.com/element-hq/hydrogen-web) | ❌ | Lightweight Matrix client with legacy and mobile browser support | [Link](docs/configuring-playbook-client-hydrogen.md) | | [Cinny](https://github.com/ajbura/cinny) | ❌ | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-cinny.md) | | [SchildiChat Web](https://schildi.chat/) | ❌ | Based on Element Web, with a more traditional instant messaging experience | [Link](docs/configuring-playbook-client-schildichat-web.md) | +| [FluffyChat Web](https://fluffychat.im/) | ❌ | The cutest messenger in Matrix | [Link](docs/configuring-playbook-client-fluffychat-web.md) | ### Server Components diff --git a/docs/configuring-playbook-client-fluffychat-web.md b/docs/configuring-playbook-client-fluffychat-web.md new file mode 100644 index 000000000..cc31bbed5 --- /dev/null +++ b/docs/configuring-playbook-client-fluffychat-web.md @@ -0,0 +1,59 @@ +# Setting up FluffyChat Web (optional) + +The playbook can install and configure the [FluffyChat Web](https://github.com/krille-chan/fluffychat) Matrix client for you. + +FluffyChat Web is a cute messenger for Matrix based. + +💡 **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: + +- [fluffychat.im](https://fluffychat.im/web), hosted by the [FluffyChat](https://fluffychat.im/) developers + +## Adjusting DNS records + +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`. + +When setting, replace `example.com` with your own. + +## Adjusting the playbook configuration + +To enable FluffyChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_client_fluffychat_enabled: true +``` + +### Adjusting the FluffyChat Web URL (optional) + +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. + +Example additional configuration for your `vars.yml` file: + +```yaml +# Switch to the domain used for Matrix services (`matrix.example.com`), +# so we won't need to add additional DNS records for FluffyChat Web. +matrix_client_fluffychat_hostname: "{{ matrix_server_fqn_matrix }}" + +# Expose under the /fluffychat subpath +matrix_client_fluffychat_path_prefix: /fluffychat +``` + +After changing the domain, **you may need to adjust your DNS** records to point the FluffyChat Web domain to the Matrix server. + +If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. + +## Installing + +After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Troubleshooting + +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`. diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 516fd6d83..132f6918f 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -376,6 +376,8 @@ devture_systemd_service_manager_services_list_auto: | + ([{'name': 'matrix-client-schildichat.service', 'priority': 2000, 'groups': ['matrix', 'clients', 'schildichat', 'client-schildichat']}] if matrix_client_schildichat_enabled else []) + + ([{'name': 'matrix-client-fluffychat.service', 'priority': 2000, 'groups': ['matrix', 'clients', 'fluffychat', 'client-fluffychat']}] if matrix_client_fluffychat_enabled else []) + + ([{'name': ('matrix-' + matrix_homeserver_implementation + '.service'), 'priority': 1000, 'groups': ['matrix', 'homeservers', matrix_homeserver_implementation]}] if matrix_homeserver_enabled else []) + ([{'name': 'matrix-corporal.service', 'priority': 1500, 'groups': ['matrix', 'corporal']}] if matrix_corporal_enabled else []) @@ -4524,6 +4526,37 @@ matrix_client_schildichat_jitsi_preferred_domain: "{{ matrix_server_fqn_jitsi if # ###################################################################### +###################################################################### +# +# matrix-client-fluffychat +# +###################################################################### + +matrix_client_fluffychat_enabled: false + +matrix_client_fluffychat_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" + +matrix_client_fluffychat_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" + +matrix_client_fluffychat_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8770') if matrix_playbook_service_host_bind_interface_prefix else '' }}" + +matrix_client_fluffychat_container_network: "{{ matrix_addons_container_network }}" + +matrix_client_fluffychat_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_client_fluffychat_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network) else [] }}" + +matrix_client_fluffychat_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" +matrix_client_fluffychat_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" +matrix_client_fluffychat_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" +matrix_client_fluffychat_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" + +matrix_client_fluffychat_self_check_validate_certificates: "{{ matrix_playbook_ssl_enabled }}" + +###################################################################### +# +# /matrix-client-fluffychat +# +###################################################################### + ###################################################################### # # matrix-synapse diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index 8dabc239d..f44db0ba6 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -80,6 +80,9 @@ matrix_server_fqn_cinny: "cinny.{{ matrix_domain }}" # This is where you access the SchildiChat Web from (if enabled via matrix_client_schildichat_enabled; disabled by default). matrix_server_fqn_schildichat: "schildichat.{{ matrix_domain }}" +# This is where you access the FluffyChat Web from (if enabled via matrix_client_fluffychat_enabled; disabled by default). +matrix_server_fqn_fluffychat: "fluffychat.{{ matrix_domain }}" + # This is where you access the Buscarron bot from (if enabled via matrix_bot_buscarron_enabled; disabled by default). matrix_server_fqn_buscarron: "buscarron.{{ matrix_domain }}" diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml new file mode 100644 index 000000000..2ba282e9e --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -0,0 +1,137 @@ +--- +# Project source code URL: https://github.com/krille-chan/fluffychat + +matrix_client_fluffychat_enabled: true + +matrix_client_fluffychat_container_image_self_build: false +matrix_client_fluffychat_container_image_self_build_repo: "https://github.com/etkecc/fluffychat-web.git" +matrix_client_fluffychat_container_image_self_build_version: "{{ 'main' if matrix_client_fluffychat_version == 'latest' else matrix_client_fluffychat_version }}" + +# renovate: datasource=docker depName=ghcr.io/etkecc/fluffychat-web +matrix_client_fluffychat_version: v1.24.0 +matrix_client_fluffychat_docker_image: "{{ matrix_client_fluffychat_docker_image_name_prefix }}etkecc/fluffychat-web:{{ matrix_client_fluffychat_version }}" +matrix_client_fluffychat_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_fluffychat_container_image_self_build else 'ghcr.io/' }}" +matrix_client_fluffychat_docker_image_force_pull: "{{ matrix_client_fluffychat_docker_image.endswith(':latest') }}" + +matrix_client_fluffychat_data_path: "{{ matrix_base_data_path }}/client-fluffychat" +matrix_client_fluffychat_container_src_files_path: "{{ matrix_client_fluffychat_data_path }}/docker-src" + +# The base container network +matrix_client_fluffychat_container_network: '' + +# A list of additional container networks that the container would be connected to. +# The role does not create these networks, so make sure they already exist. +# Use this to expose this container to a reverse proxy, which runs in a different container network. +matrix_client_fluffychat_container_additional_networks: [] + +# Controls whether the matrix-client-fluffychat container exposes its HTTP port (tcp/8080 in the container). +# +# Takes an ":" or "" value (e.g. "127.0.0.1:8765"), or empty string to not expose. +matrix_client_fluffychat_container_http_host_bind_port: '' + +# matrix_client_fluffychat_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. +# See `../templates/labels.j2` for details. +# +# To inject your own other container labels, see `matrix_client_fluffychat_container_labels_additional_labels`. +matrix_client_fluffychat_container_labels_traefik_enabled: true +matrix_client_fluffychat_container_labels_traefik_docker_network: "{{ matrix_client_fluffychat_container_network }}" +matrix_client_fluffychat_container_labels_traefik_hostname: "{{ matrix_client_fluffychat_hostname }}" +# The path prefix must either be `/` or not end with a slash (e.g. `/fluffychat`). +matrix_client_fluffychat_container_labels_traefik_path_prefix: "{{ matrix_client_fluffychat_path_prefix }}" +matrix_client_fluffychat_container_labels_traefik_rule: "Host(`{{ matrix_client_fluffychat_container_labels_traefik_hostname }}`){% if matrix_client_fluffychat_container_labels_traefik_path_prefix != '/' %} && PathPrefix(`{{ matrix_client_fluffychat_container_labels_traefik_path_prefix }}`){% endif %}" +matrix_client_fluffychat_container_labels_traefik_priority: 0 +matrix_client_fluffychat_container_labels_traefik_entrypoints: web-secure +matrix_client_fluffychat_container_labels_traefik_tls: "{{ matrix_client_fluffychat_container_labels_traefik_entrypoints != 'web' }}" +matrix_client_fluffychat_container_labels_traefik_tls_certResolver: default # noqa var-naming + +# Controls which additional headers to attach to all HTTP responses. +# To add your own headers, use `matrix_client_fluffychat_container_labels_traefik_additional_response_headers_custom` +matrix_client_fluffychat_container_labels_traefik_additional_response_headers: "{{ matrix_client_fluffychat_container_labels_traefik_additional_response_headers_auto | combine(matrix_client_fluffychat_container_labels_traefik_additional_response_headers_custom) }}" +matrix_client_fluffychat_container_labels_traefik_additional_response_headers_auto: | + {{ + {} + | combine ({'X-XSS-Protection': matrix_client_fluffychat_http_header_xss_protection} if matrix_client_fluffychat_http_header_xss_protection else {}) + | combine ({'X-Frame-Options': matrix_client_fluffychat_http_header_frame_options} if matrix_client_fluffychat_http_header_frame_options else {}) + | combine ({'X-Content-Type-Options': matrix_client_fluffychat_http_header_content_type_options} if matrix_client_fluffychat_http_header_content_type_options else {}) + | combine ({'Content-Security-Policy': matrix_client_fluffychat_http_header_content_security_policy} if matrix_client_fluffychat_http_header_content_security_policy else {}) + | combine ({'Permission-Policy': matrix_client_fluffychat_http_header_content_permission_policy} if matrix_client_fluffychat_http_header_content_permission_policy else {}) + | combine ({'Strict-Transport-Security': matrix_client_fluffychat_http_header_strict_transport_security} if matrix_client_fluffychat_http_header_strict_transport_security and matrix_client_fluffychat_container_labels_traefik_tls else {}) + }} +matrix_client_fluffychat_container_labels_traefik_additional_response_headers_custom: {} + +# matrix_client_fluffychat_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. +# See `../templates/labels.j2` for details. +# +# Example: +# matrix_client_fluffychat_container_labels_additional_labels: | +# my.label=1 +# another.label="here" +matrix_client_fluffychat_container_labels_additional_labels: '' + +# A list of extra arguments to pass to the container +matrix_client_fluffychat_container_extra_arguments: [] + +# List of systemd services that matrix-client-fluffychat.service depends on +matrix_client_fluffychat_systemd_required_services_list: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" + +# Specifies the value of the `X-XSS-Protection` header +# Stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. +# +# Learn more about it is here: +# - https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection +# - https://portswigger.net/web-security/cross-site-scripting/reflected +matrix_client_fluffychat_http_header_xss_protection: "1; mode=block" + +# Specifies the value of the `X-Frame-Options` header which controls whether framing can happen. +# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options +matrix_client_fluffychat_http_header_frame_options: SAMEORIGIN + +# Specifies the value of the `X-Content-Type-Options` header. +# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options +matrix_client_fluffychat_http_header_content_type_options: nosniff + +# Specifies the value of the `Content-Security-Policy` header. +# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy +matrix_client_fluffychat_http_header_content_security_policy: frame-ancestors 'self' + +# Specifies the value of the `Permission-Policy` header. +# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permission-Policy +matrix_client_fluffychat_http_header_content_permission_policy: "{{ 'interest-cohort=()' if matrix_client_fluffychat_floc_optout_enabled else '' }}" + +# Specifies the value of the `Strict-Transport-Security` header. +# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security +matrix_client_fluffychat_http_header_strict_transport_security: "max-age=31536000; includeSubDomains{{ '; preload' if matrix_client_fluffychat_hsts_preload_enabled else '' }}" + +# Controls whether to send a "Permissions-Policy interest-cohort=();" header along with all responses +# +# Learn more about what it is here: +# - https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea +# - https://paramdeo.com/blog/opting-your-website-out-of-googles-floc-network +# - https://amifloced.org/ +# +# Of course, a better solution is to just stop using browsers (like Chrome), which participate in such tracking practices. +# See: `matrix_client_fluffychat_content_permission_policy` +matrix_client_fluffychat_floc_optout_enabled: true + +# Controls if HSTS preloading is enabled +# +# In its strongest and recommended form, the [HSTS policy](https://www.chromium.org/hsts) includes all subdomains, and +# indicates a willingness to be "preloaded" into browsers: +# `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload` +# For more information visit: +# - https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security +# - https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security +# - https://hstspreload.org/#opt-in +# See: `matrix_client_fluffychat_http_header_strict_transport_security` +matrix_client_fluffychat_hsts_preload_enabled: false + +matrix_client_fluffychat_scheme: https +# The hostname at which FluffyChat Web is served. +matrix_client_fluffychat_hostname: "{{ matrix_server_fqn_fluffychat }}" + +# The path at which FluffyChat Web is exposed. +# This value must either be `/` or not end with a slash (e.g. `/fluffychat`). +matrix_client_fluffychat_path_prefix: / + +# Controls whether the self-check feature should validate SSL certificates. +matrix_client_fluffychat_self_check_validate_certificates: true diff --git a/roles/custom/matrix-client-fluffychat/tasks/main.yml b/roles/custom/matrix-client-fluffychat/tasks/main.yml new file mode 100644 index 000000000..55ca7a933 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/tasks/main.yml @@ -0,0 +1,26 @@ +--- + +- tags: + - setup-all + - setup-client-fluffychat + - install-all + - install-client-fluffychat + block: + - when: matrix_client_fluffychat_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" + + - when: matrix_client_fluffychat_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" + +- tags: + - setup-all + - setup-client-fluffychat + block: + - when: not matrix_client_fluffychat_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" + +- tags: + - self-check + block: + - when: matrix_client_fluffychat_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/self_check.yml" diff --git a/roles/custom/matrix-client-fluffychat/tasks/self_check.yml b/roles/custom/matrix-client-fluffychat/tasks/self_check.yml new file mode 100644 index 000000000..b0dda25c1 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/tasks/self_check.yml @@ -0,0 +1,24 @@ +--- + +- ansible.builtin.set_fact: + matrix_client_fluffychat_url_endpoint_public: "{{ matrix_client_fluffychat_scheme }}://{{ matrix_client_fluffychat_hostname }}/" + +- name: Check FluffyChat Web + ansible.builtin.uri: + url: "{{ matrix_client_fluffychat_url_endpoint_public }}" + follow_redirects: none + validate_certs: "{{ matrix_client_fluffychat_self_check_validate_certificates }}" + register: matrix_client_fluffychat_self_check_result + check_mode: false + ignore_errors: true + delegate_to: 127.0.0.1 + become: false + +- name: Fail if FluffyChat Web not working + ansible.builtin.fail: + msg: "Failed checking FluffyChat Web is up at `{{ matrix_server_fqn_fluffychat }}` (checked endpoint: `{{ matrix_client_fluffychat_url_endpoint_public }}`). Is FluffyChat Web running? Is port 443 open in your firewall? Full error: {{ matrix_client_fluffychat_self_check_result }}" + when: "matrix_client_fluffychat_self_check_result.failed or 'json' not in matrix_client_fluffychat_self_check_result" + +- name: Report working FluffyChat Web + ansible.builtin.debug: + msg: "FluffyChat Web at `{{ matrix_server_fqn_fluffychat }}` is working (checked endpoint: `{{ matrix_client_fluffychat_url_endpoint_public }}`)" diff --git a/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml b/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml new file mode 100644 index 000000000..ca5619b51 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml @@ -0,0 +1,70 @@ +--- + +- name: Ensure FluffyChat Web paths exists + ansible.builtin.file: + path: "{{ item.path }}" + state: directory + mode: 0750 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - {path: "{{ matrix_client_fluffychat_data_path }}", when: true} + - {path: "{{ matrix_client_fluffychat_container_src_files_path }}", when: "{{ matrix_client_fluffychat_container_image_self_build }}"} + when: "item.when | bool" + +- name: Ensure FluffyChat Web container image is pulled + community.docker.docker_image: + name: "{{ matrix_client_fluffychat_docker_image }}" + source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" + force_source: "{{ matrix_client_fluffychat_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_client_fluffychat_docker_image_force_pull }}" + when: "not matrix_client_fluffychat_container_image_self_build | bool" + register: result + retries: "{{ devture_playbook_help_container_retries_count }}" + delay: "{{ devture_playbook_help_container_retries_delay }}" + until: result is not failed + +- when: "matrix_client_fluffychat_container_image_self_build | bool" + block: + - name: Ensure FluffyChat Web repository is present on self-build + ansible.builtin.git: + repo: "{{ matrix_client_fluffychat_container_image_self_build_repo }}" + dest: "{{ matrix_client_fluffychat_container_src_files_path }}" + version: "{{ matrix_client_fluffychat_container_image_self_build_version }}" + force: "yes" + become: true + become_user: "{{ matrix_user_username }}" + register: matrix_client_fluffychat_git_pull_results + + - name: Ensure FluffyChat Web container image is built + ansible.builtin.command: + cmd: |- + {{ devture_systemd_docker_base_host_command_docker }} buildx build + --tag={{ matrix_client_fluffychat_docker_image }} + --file={{ matrix_client_fluffychat_container_src_files_path }}/Dockerfile + {{ matrix_client_fluffychat_container_src_files_path }} + changed_when: true + +- name: Ensure FluffyChat Web config files installed + ansible.builtin.template: + src: "{{ item.src }}" + dest: "{{ matrix_client_fluffychat_data_path }}/{{ item.name }}" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - {src: "{{ role_path }}/templates/labels.j2", name: "labels"} + when: "item.src is not none" + +- name: Ensure FluffyChat Web container network is created + community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" + name: "{{ matrix_client_fluffychat_container_network }}" + driver: bridge + driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" + +- name: Ensure matrix-client-fluffychat.service installed + ansible.builtin.template: + src: "{{ role_path }}/templates/systemd/matrix-client-fluffychat.service.j2" + dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-client-fluffychat.service" + mode: 0644 diff --git a/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml b/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml new file mode 100644 index 000000000..313489bb5 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml @@ -0,0 +1,25 @@ +--- + +- name: Check existence of matrix-client-fluffychat.service + ansible.builtin.stat: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-client-fluffychat.service" + register: matrix_client_fluffychat_service_stat + +- when: matrix_client_fluffychat_service_stat.stat.exists | bool + block: + - name: Ensure matrix-client-fluffychat is stopped + ansible.builtin.service: + name: matrix-client-fluffychat + state: stopped + enabled: false + daemon_reload: true + + - name: Ensure matrix-client-fluffychat.service doesn't exist + ansible.builtin.file: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-client-fluffychat.service" + state: absent + + - name: Ensure FluffyChat Web path doesn't exist + ansible.builtin.file: + path: "{{ matrix_client_fluffychat_data_path }}" + state: absent diff --git a/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml new file mode 100644 index 000000000..063ffa898 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml @@ -0,0 +1,29 @@ +--- + +- name: Fail if required FluffyChat Web settings not defined + ansible.builtin.fail: + msg: > + You need to define a required configuration setting (`{{ item }}`) for using FluffyChat Web. + when: "vars[item] == ''" + with_items: + - matrix_client_fluffychat_container_network + +- when: matrix_client_fluffychat_container_labels_traefik_enabled | bool + block: + - name: Fail if required matrix-client-fluffychat Traefik settings not defined + ansible.builtin.fail: + msg: >- + You need to define a required configuration setting (`{{ item }}`). + when: "vars[item] == ''" + with_items: + - matrix_client_fluffychat_container_labels_traefik_hostname + - matrix_client_fluffychat_container_labels_traefik_path_prefix + + # We ensure it doesn't end with a slash, because we handle both (slash and no-slash). + # Knowing that `matrix_client_fluffychat_container_labels_traefik_path_prefix` does not end with a slash + # ensures we know how to set these routes up without having to do "does it end with a slash" checks elsewhere. + - name: Fail if matrix_client_fluffychat_container_labels_traefik_path_prefix ends with a slash + ansible.builtin.fail: + msg: >- + matrix_client_fluffychat_container_labels_traefik_path_prefix (`{{ matrix_client_fluffychat_container_labels_traefik_path_prefix }}`) must either be `/` or not end with a slash (e.g. `/fluffychat`). + when: "matrix_client_fluffychat_container_labels_traefik_path_prefix != '/' and matrix_client_fluffychat_container_labels_traefik_path_prefix[-1] == '/'" diff --git a/roles/custom/matrix-client-fluffychat/templates/labels.j2 b/roles/custom/matrix-client-fluffychat/templates/labels.j2 new file mode 100644 index 000000000..2f1ea5a87 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/templates/labels.j2 @@ -0,0 +1,46 @@ +{% if matrix_client_fluffychat_container_labels_traefik_enabled %} +traefik.enable=true + +{% if matrix_client_fluffychat_container_labels_traefik_docker_network %} +traefik.docker.network={{ matrix_client_fluffychat_container_labels_traefik_docker_network }} +{% endif %} + +traefik.http.services.matrix-client-fluffychat.loadbalancer.server.port=8080 + +{% set middlewares = [] %} + +{% if matrix_client_fluffychat_container_labels_traefik_path_prefix != '/' %} +traefik.http.middlewares.matrix-client-fluffychat-slashless-redirect.redirectregex.regex=({{ matrix_client_fluffychat_container_labels_traefik_path_prefix | quote }})$ +traefik.http.middlewares.matrix-client-fluffychat-slashless-redirect.redirectregex.replacement=${1}/ +{% set middlewares = middlewares + ['matrix-client-fluffychat-slashless-redirect'] %} +{% endif %} + +{% if matrix_client_fluffychat_container_labels_traefik_path_prefix != '/' %} +traefik.http.middlewares.matrix-client-fluffychat-strip-prefix.stripprefix.prefixes={{ matrix_client_fluffychat_container_labels_traefik_path_prefix }} +{% set middlewares = middlewares + ['matrix-client-fluffychat-strip-prefix'] %} +{% endif %} + +{% if matrix_client_fluffychat_container_labels_traefik_additional_response_headers.keys() | length > 0 %} +{% for name, value in matrix_client_fluffychat_container_labels_traefik_additional_response_headers.items() %} +traefik.http.middlewares.matrix-client-fluffychat-add-headers.headers.customresponseheaders.{{ name }}={{ value }} +{% endfor %} +{% set middlewares = middlewares + ['matrix-client-fluffychat-add-headers'] %} +{% endif %} + +traefik.http.routers.matrix-client-fluffychat.rule={{ matrix_client_fluffychat_container_labels_traefik_rule }} +{% if matrix_client_fluffychat_container_labels_traefik_priority | int > 0 %} +traefik.http.routers.matrix-client-fluffychat.priority={{ matrix_client_fluffychat_container_labels_traefik_priority }} +{% endif %} +traefik.http.routers.matrix-client-fluffychat.service=matrix-client-fluffychat +{% if middlewares | length > 0 %} +traefik.http.routers.matrix-client-fluffychat.middlewares={{ middlewares | join(',') }} +{% endif %} +traefik.http.routers.matrix-client-fluffychat.entrypoints={{ matrix_client_fluffychat_container_labels_traefik_entrypoints }} +traefik.http.routers.matrix-client-fluffychat.tls={{ matrix_client_fluffychat_container_labels_traefik_tls | to_json }} +{% if matrix_client_fluffychat_container_labels_traefik_tls %} +traefik.http.routers.matrix-client-fluffychat.tls.certResolver={{ matrix_client_fluffychat_container_labels_traefik_tls_certResolver }} +{% endif %} + +{% endif %} + +{{ matrix_client_fluffychat_container_labels_additional_labels }} diff --git a/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 new file mode 100644 index 000000000..5747637e5 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 @@ -0,0 +1,48 @@ +#jinja2: lstrip_blocks: "True" +[Unit] +Description=Matrix FluffyChat Web server +{% for service in matrix_client_fluffychat_systemd_required_services_list %} +Requires={{ service }} +After={{ service }} +{% endfor %} +DefaultDependencies=no + +[Service] +Type=simple +Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-fluffychat 2>/dev/null || true' + +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ + --rm \ + --name=matrix-client-fluffychat \ + --log-driver=none \ + --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ + --cap-drop=ALL \ + --read-only \ + --network={{ matrix_client_fluffychat_container_network }} \ + {% if matrix_client_fluffychat_container_http_host_bind_port %} + -p {{ matrix_client_fluffychat_container_http_host_bind_port }}:8080 \ + {% endif %} + --label-file={{ matrix_client_fluffychat_data_path }}/labels \ + --tmpfs=/tmp:rw,noexec,nosuid,size=10m \ + {% for arg in matrix_client_fluffychat_container_extra_arguments %} + {{ arg }} \ + {% endfor %} + {{ matrix_client_fluffychat_docker_image }} + +{% for network in matrix_client_fluffychat_container_additional_networks %} +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-client-fluffychat +{% endfor %} + +ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-fluffychat + +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-fluffychat 2>/dev/null || true' + +Restart=always +RestartSec=30 +SyslogIdentifier=matrix-client-fluffychat + +[Install] +WantedBy=multi-user.target diff --git a/setup.yml b/setup.yml index 37ae61f26..d65222648 100644 --- a/setup.yml +++ b/setup.yml @@ -117,6 +117,7 @@ - custom/matrix-client-hydrogen - custom/matrix-client-cinny - custom/matrix-client-schildichat + - custom/matrix-client-fluffychat - galaxy/jitsi - custom/matrix-user-verification-service - custom/matrix-ldap-registration-proxy From d6c60fd5385950e38b89e1f9557ee26468d2b067 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 17 Feb 2025 11:16:38 +0200 Subject: [PATCH 583/952] Split `matrix_client_fluffychat_container_additional_networks` into `_auto` and `_custom` Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4068 --- group_vars/matrix_servers | 2 +- roles/custom/matrix-client-fluffychat/defaults/main.yml | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 132f6918f..ac2f386dd 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -4542,7 +4542,7 @@ matrix_client_fluffychat_container_http_host_bind_port: "{{ (matrix_playbook_ser matrix_client_fluffychat_container_network: "{{ matrix_addons_container_network }}" -matrix_client_fluffychat_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_client_fluffychat_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network) else [] }}" +matrix_client_fluffychat_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_client_fluffychat_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network) else [] }}" matrix_client_fluffychat_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" matrix_client_fluffychat_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml index 2ba282e9e..b403ad597 100644 --- a/roles/custom/matrix-client-fluffychat/defaults/main.yml +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -22,7 +22,9 @@ matrix_client_fluffychat_container_network: '' # A list of additional container networks that the container would be connected to. # The role does not create these networks, so make sure they already exist. # Use this to expose this container to a reverse proxy, which runs in a different container network. -matrix_client_fluffychat_container_additional_networks: [] +matrix_client_fluffychat_container_additional_networks: "{{ matrix_client_fluffychat_container_additional_networks_auto + matrix_client_fluffychat_container_additional_networks_custom }}" +matrix_client_fluffychat_container_additional_networks_auto: [] +matrix_client_fluffychat_container_additional_networks_custom: [] # Controls whether the matrix-client-fluffychat container exposes its HTTP port (tcp/8080 in the container). # From 76f235f494b842953c9ed6cd9b6f79c9640933a1 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 17 Feb 2025 11:17:40 +0200 Subject: [PATCH 584/952] Split `matrix_client_fluffychat_systemd_required_services_list` into `_default`, `_auto` and `_custom` Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4068 --- roles/custom/matrix-client-fluffychat/defaults/main.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml index b403ad597..b0e974e11 100644 --- a/roles/custom/matrix-client-fluffychat/defaults/main.yml +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -74,7 +74,10 @@ matrix_client_fluffychat_container_labels_additional_labels: '' matrix_client_fluffychat_container_extra_arguments: [] # List of systemd services that matrix-client-fluffychat.service depends on -matrix_client_fluffychat_systemd_required_services_list: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" +matrix_client_fluffychat_systemd_required_services_list: "{{ matrix_client_fluffychat_systemd_required_services_list_default + matrix_client_fluffychat_systemd_required_services_list_auto + matrix_client_fluffychat_systemd_required_services_list_custom }}" +matrix_client_fluffychat_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" +matrix_client_fluffychat_systemd_required_services_list_auto: [] +matrix_client_fluffychat_systemd_required_services_list_custom: [] # Specifies the value of the `X-XSS-Protection` header # Stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. From 6e591da0abd0713b8854cd7ef56076d89aca3f39 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 17 Feb 2025 11:23:22 +0200 Subject: [PATCH 585/952] Announce FluffyChat Web support Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4068 --- CHANGELOG.md | 9 +++++++++ docs/configuring-playbook-client-fluffychat-web.md | 2 +- docs/configuring-playbook.md | 3 +++ 3 files changed, 13 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f850d47e7..85bdaed2e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,12 @@ +# 2025-02-17 + +## FluffyChat Web suport + +Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [FluffyChat Web](https://github.com/krille-chan/fluffychat) as an additional Matrix client you can self-host. + +To learn more, see our [Setting up FluffyChat Web](docs/configuring-playbook-client-fluffychat-web.md) documentation page. + + # 2025-02-03 ## The mautrix-hangouts bridge has been removed from the playbook diff --git a/docs/configuring-playbook-client-fluffychat-web.md b/docs/configuring-playbook-client-fluffychat-web.md index cc31bbed5..262c31488 100644 --- a/docs/configuring-playbook-client-fluffychat-web.md +++ b/docs/configuring-playbook-client-fluffychat-web.md @@ -2,7 +2,7 @@ The playbook can install and configure the [FluffyChat Web](https://github.com/krille-chan/fluffychat) Matrix client for you. -FluffyChat Web is a cute messenger for Matrix based. +FluffyChat Web is a cute cross-platform (web, iOS, Android) messenger for Matrix written in [Flutter](https://flutter.dev/). 💡 **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: diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 31d443616..e43376006 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -73,6 +73,9 @@ Web clients for Matrix that you can host on your own domains. - [Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks +- [Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/) + + ### Authentication and user-related Extend and modify how users are authenticated on your homeserver. From 6647e08e6e1d5f05a5cd671dd68de8768625a114 Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 17 Feb 2025 15:08:00 +0200 Subject: [PATCH 586/952] fix etherpad --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 047dbf3ac..ed9b88a13 100644 --- a/requirements.yml +++ b/requirements.yml @@ -16,7 +16,7 @@ version: 129c8590e106b83e6f4c259649a613c6279e937a name: docker_sdk_for_python - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git - version: v2.2.7-0 + version: v2.2.7-1 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git version: v4.98-r0-4-1 From 6e94f5f1f70d162ae199f3303cef7c07b9ff2d3c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:01:32 +0900 Subject: [PATCH 587/952] Update docs/configuring-playbook-jitsi.md: edit the introduction - Add a link to the role at MASH project and its document: https://github.com/mother-of-all-self-hosting/ansible-role-jitsi Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 280f85d3c..88048dea8 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -20,9 +20,9 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. -See the project's [documentation](https://jitsi.github.io/handbook/) to learn what it does and why it might be useful to you. - -**Note**: the configuration by the playbook is similar to the one by [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the official documentation for Docker deployment [here](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/). +The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: +- [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) +- `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have fetched the Ansible roles ## Prerequisites From 26e285e9729fd4ded2a4ab7aef40e46e2c21f07f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:01:58 +0900 Subject: [PATCH 588/952] Update docs/configuring-playbook-etherpad.md: adopt the common introduction - Add links to the role's document: https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index ad55d3b9c..632e72661 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -18,7 +18,9 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. -This Ansible role for Etherpad is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). +The Ansible role for Etherpad is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: +- [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) +- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles ## Adjusting DNS records @@ -48,9 +50,7 @@ etherpad_enabled: true 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. -For details about configuring Etherpad per your preference, you can check them via: -- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) -- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles +See the role's document 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)). ### Create admin user (optional) From a86f904baa4254c8c3cb33f17d12cd22e44565ba Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:07 +0900 Subject: [PATCH 589/952] Update docs for Etherpad and Jitsi: adopt the common description Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 632e72661..bde0fb638 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -16,7 +16,7 @@ The playbook can install and configure [Etherpad](https://etherpad.org) for you. Etherpad is an open source collaborative text editor. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app. -When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences. +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. The Ansible role for Etherpad is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: - [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 88048dea8..e3cf5ade7 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -18,7 +18,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you. -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. +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. The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: - [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) From a9c3db299461044af7470e916d050feb5837e620 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:15 +0900 Subject: [PATCH 590/952] Update docs/configuring-playbook-jitsi.md: edit the section for prerequisites - Add a link to the handbook: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-requirements - Add a link to the role's document Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index e3cf5ade7..3b2adf9a1 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -26,10 +26,9 @@ The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-s ## Prerequisites -You may need to open the following ports to your server: +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). -- `4443/tcp` — RTP media fallback over TCP -- `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)). +You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's document](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. ## Adjusting DNS records From 0a33e69e56e108c146e4f9a38a6ae842665d16f3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:26 +0900 Subject: [PATCH 591/952] Update docs/configuring-playbook-jitsi.md: edit the section for adjusting the playbook configuration - Add the comment blocks around the variable - Add links to the role's document Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 3b2adf9a1..258a14143 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -41,9 +41,25 @@ When setting, replace `example.com` with your own. To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml +######################################################################## +# # +# jitsi # +# # +######################################################################## + jitsi_enabled: true + +######################################################################## +# # +# /jitsi # +# # +######################################################################## ``` +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. + +See the role's document for details about configuring Jitsi per your preference (such as [authentication and guests mode](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) 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)). + ### Adjusting the Jitsi URL (optional) By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one. From e53056ac4860fb040321682be849a77d753f0f5b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:33 +0900 Subject: [PATCH 592/952] Update docs/configuring-playbook-jitsi.md: add a note about the example configuration and the instruction to set up additional JVBs Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 258a14143..9232009d6 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -58,6 +58,8 @@ jitsi_enabled: true 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. +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. + See the role's document for details about configuring Jitsi per your preference (such as [authentication and guests mode](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) 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)). ### Adjusting the Jitsi URL (optional) From 2f8152936cbd693344a8a36956e4ca8500ddab7f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:38 +0900 Subject: [PATCH 593/952] Update docs/configuring-playbook-jitsi.md: remove the instructions for adjusting the URL in favor of the role's document at the MASH project The document is available at https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/af5b04fc32e79cdcdf091dff993856c14d1e4d70/docs/configuring-jitsi.md - Add an anchor link to the section for setting the hostname on the role's document Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 9232009d6..edd4f5e4b 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -60,20 +60,7 @@ As the most of the necessary settings for the role have been taken care of by th 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. -See the role's document for details about configuring Jitsi per your preference (such as [authentication and guests mode](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) 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)). - -### Adjusting the Jitsi URL (optional) - -By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one. - -Example additional configuration for your `vars.yml` file: - -```yaml -# Change the default hostname -jitsi_hostname: call.example.com -``` - -After changing the domain, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server. +See the role's document 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), [authentication and guests mode](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional), 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)). ### Configure Jitsi authentication and guests mode (optional) From 7d9f5c594a9f0a497b723da40a35fbd19e5d7901 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:49 +0900 Subject: [PATCH 594/952] Update docs/configuring-playbook-jitsi.md: create a section for instruction to enable authentication Partially based on https://github.com/mother-of-all-self-hosting/mash-playbook/commit/699b458733b0d890588286a0345b3636c79f7b58 Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index edd4f5e4b..689f2d81c 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -60,7 +60,15 @@ As the most of the necessary settings for the role have been taken care of by th 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. -See the role's document 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), [authentication and guests mode](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional), 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)). +See the role's document 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)). + +### Enable authentication and guests mode (optional) + +By default the Jitsi Meet instance **does not require for anyone to log in, and is open to use without an account**. + +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. + +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 document for details about how to configure the authentication and guests mode. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. ### Configure Jitsi authentication and guests mode (optional) From b14a0f7854bc04c1fb160c335c0c3d582133bd52 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:02:54 +0900 Subject: [PATCH 595/952] Update docs/configuring-playbook-jitsi.md: re-add the recommendation of authentication method Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 689f2d81c..e5388c8fc 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -68,7 +68,7 @@ By default the Jitsi Meet instance **does not require for anyone to log in, and 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. -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 document for details about how to configure the authentication and guests mode. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. +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 document 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)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. ### Configure Jitsi authentication and guests mode (optional) From 31971011dc13593bac99001ffcd7eba3d31ec282 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:00 +0900 Subject: [PATCH 596/952] Update docs/configuring-playbook-jitsi.md: remove the instructions for other optional configurations in favor of the role's document - The section about enabling Gravater service is not removed as it is specific to configuring Jitsi on a Matrix server. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 157 ----------------------------- 1 file changed, 157 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index e5388c8fc..c5ac95746 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -70,102 +70,6 @@ If you would like to control who is allowed to start meetings on your instance, 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 document 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)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. -### Configure Jitsi authentication and guests mode (optional) - -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. - -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). - -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. - -**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. - -#### Authenticate using Jitsi accounts: Auth-Type `internal` (recommended) - -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. - -To enable authentication with a Jitsi account, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_…` and `PASSWORD_…` with your own values. - -```yaml -jitsi_enable_auth: true -jitsi_enable_guests: true -jitsi_prosody_auth_internal_accounts: - - username: "USERNAME_FOR_THE_FIRST_USER_HERE" - password: "PASSWORD_FOR_THE_FIRST_USER_HERE" - - username: "USERNAME_FOR_THE_SECOND_USER_HERE" - password: "PASSWORD_FOR_THE_SECOND_USER_HERE" -``` - -**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. - -#### Authenticate using Matrix OpenID: Auth-Type `matrix` - -> [!WARNING] -> This breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests. - -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. - -To enable authentication with Matrix OpenID, add the following configuration to your `vars.yml` file: - -```yaml -jitsi_enable_auth: true -jitsi_auth_type: matrix -matrix_user_verification_service_enabled: true -``` - -For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification). - -#### Authenticate using LDAP: Auth-Type `ldap` - -To enable authentication with LDAP, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -jitsi_enable_auth: true -jitsi_auth_type: ldap -jitsi_ldap_url: "ldap://ldap.example.com" -jitsi_ldap_base: "OU=People,DC=example.com" -#jitsi_ldap_binddn: "" -#jitsi_ldap_bindpw: "" -jitsi_ldap_filter: "uid=%u" -jitsi_ldap_auth_method: "bind" -jitsi_ldap_version: "3" -jitsi_ldap_use_tls: true -jitsi_ldap_tls_ciphers: "" -jitsi_ldap_tls_check_peer: true -jitsi_ldap_tls_cacert_file: "/etc/ssl/certs/ca-certificates.crt" -jitsi_ldap_tls_cacert_dir: "/etc/ssl/certs" -jitsi_ldap_start_tls: false -``` - -For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation. - -### Configure `JVB_ADVERTISE_IPS` for running behind NAT or on a LAN environment (optional) - -When running Jitsi in a LAN environment, or on the public Internet via NAT, the `JVB_ADVERTISE_IPS` enviornment variable should be set. - -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. - -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. - -To set the variable, add the following configuration to your `vars.yml` file. Make sure to replace `LOCAL_IP_ADDRESS_OF_THE_HOST_HERE` with a proper value. - -```yaml -jitsi_jvb_container_extra_arguments: - - '--env "JVB_ADVERTISE_IPS=LOCAL_IP_ADDRESS_OF_THE_HOST_HERE"' -``` - -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. - -### Set a maximum number of participants on a Jitsi conference (optional) - -You can set a maximum number of participants allowed to join a Jitsi conference. By default the number is not specified. - -To set it, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -jitsi_prosody_max_participants: 4 # example value -``` - ### Enable Gravatar (optional) In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service. @@ -181,67 +85,6 @@ jitsi_disable_gravatar: false > [!WARNING] > This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party. -### Fine tune Jitsi (optional) - -If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -jitsi_web_config_resolution_width_ideal_and_max: 480 -jitsi_web_config_resolution_height_ideal_and_max: 240 -jitsi_web_custom_config_extension: | - config.enableLayerSuspension = true; - - config.disableAudioLevels = true; - - config.channelLastN = 4; -``` - -These configurations: - -- **limit the maximum video resolution**, to save up resources on both server and clients -- **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/). -- **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved -- **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md). - -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/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 these variables: - - `jitsi_web_custom_interface_config_extension`: custom configuration to be appended to `interface_config.js`, passed to Jitsi Web - - `jitsi_web_custom_config_extension`: custom configuration to be injected into `custom-config.js`, passed to Jitsi Web - - `jitsi_jvb_custom_config_extension`: custom configuration to be injected into `custom-sip-communicator.properties`, passed to Jitsi JVB - -### Example configurations - -Here is an example set of configurations for running a Jitsi instance with: - -- authentication using a Jitsi account (username: `US3RNAME`, password: `passw0rd`) -- guests: allowed -- maximum participants: 6 people -- fine tuning with the configurations presented above -- other miscellaneous options (see the official Jitsi documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-configuration) and [here](https://jitsi.github.io/handbook/docs/user-guide/user-guide-advanced)) - -```yaml -jitsi_enabled: true -jitsi_enable_auth: true -jitsi_enable_guests: true -jitsi_prosody_auth_internal_accounts: - - username: "US3RNAME" - password: "passw0rd" -jitsi_prosody_max_participants: 6 -jitsi_web_config_resolution_width_ideal_and_max: 480 -jitsi_web_config_resolution_height_ideal_and_max: 240 -jitsi_web_custom_config_extension: | - config.enableLayerSuspension = true; - config.disableAudioLevels = true; - config.channelLastN = 4; - config.requireDisplayName = true; // force users to set a display name - config.startAudioOnly = true; // start the conference in audio only mode (no video is being received nor sent) -``` - ## Installing After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below: From de14a55e337d417ae6701eb147edda6865d6bba4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:04 +0900 Subject: [PATCH 597/952] Update docs/configuring-playbook-jitsi.md: edit the instruction about enabling Gravatar service Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index c5ac95746..b9e7dfe72 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -74,9 +74,9 @@ See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ji In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service. -Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our default configuration has disabled the Gravatar service. +Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our configuration has disabled the Gravatar service. -To enable the Gravatar service, add the following configuration to your `vars.yml` file: +To enable the Gravatar service nevertheless, add the following configuration to your `vars.yml` file: ```yaml jitsi_disable_gravatar: false From 7aa08149f50d971571fbcad1ba9b828e10e89a01 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:09 +0900 Subject: [PATCH 598/952] Update docs/configuring-playbook-jitsi.md: copy and edit the section for usage from the Jitsi's role document at the MASH project Based on https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/af5b04fc32e79cdcdf091dff993856c14d1e4d70/docs/configuring-jitsi.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index b9e7dfe72..ebebd5578 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -104,7 +104,9 @@ You can use the self-hosted Jitsi server in multiple ways: - **by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server. -- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com` +- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`, and you can start a videoconference. + +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. ### Set up additional JVBs for more video-conferences (optional) From 4403340cef63d0b7401cb7ed716108c567d1cd07 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:14 +0900 Subject: [PATCH 599/952] Update docs/configuring-playbook-jitsi.md: add a link to the official user guide to the usage section Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index ebebd5578..81fa88b16 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -108,6 +108,8 @@ You can use the self-hosted Jitsi server in multiple ways: 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. +Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi. + ### Set up additional JVBs for more video-conferences (optional) By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts. From 61f1357bfc56984d472762bd6da05a9b5b283993 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:18 +0900 Subject: [PATCH 600/952] Update docs/configuring-playbook-jitsi.md: remove the instruction for setting up additional JVBs in favor of the role's document The instruction is available at https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/af5b04fc32e79cdcdf091dff993856c14d1e4d70/docs/configuring-jitsi.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 145 ----------------------------- 1 file changed, 145 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 81fa88b16..84288349c 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -110,151 +110,6 @@ Note that you'll need to log in to your Jitsi's account to start a conference if Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi. -### Set up additional JVBs for more video-conferences (optional) - -By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts. - -These settings below will allow you to provision those extra JVB instances. The instances will register themselves with the Prosody service, and be available for Jicofo to route conferences too. - -#### Add the `jitsi_jvb_servers` section on `hosts` file - -For additional JVBs, you'd need to add the section titled `jitsi_jvb_servers` on the ansible `hosts` file with the details of the JVB hosts as below: - -```INI -[jitsi_jvb_servers] -jvb-2.example.com ansible_host=192.168.0.2 -``` - -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. - -You could add JVB hosts as many as you would like. When doing so, add lines with the details of them. - -#### Prepare `vars.yml` files for additional JVBs - -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`). - -Note that most (if not all) variables are common for both servers. - -If you are setting up multiple JVB instances, you'd need to create `vars.yml` files for each of them too (`inventory/host_vars/jvb-3.example.com/vars.yml`, for example). - -#### Set the server ID to each JVB - -Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB. - -The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container. - -To set the server ID to `jvb-2`, add the following configuration to either `hosts` or `vars.yml` files (adapt to your needs). - -- On `hosts`: - - Add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below: - - ```INI - [jitsi_jvb_servers] - jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2 - jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2 - ``` - -- On `vars.yml` files: - - ```yaml - jitsi_jvb_server_id: 'jvb-2' - ``` - -Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook). - -**Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host. - -#### Set colibri WebSocket port - -The additional JVBs will need to expose the colibri WebSocket port. - -To expose the port, add the following configuration to your `vars.yml` files: - -```yaml -jitsi_jvb_container_colibri_ws_host_bind_port: 9090 -``` - -#### Set Prosody XMPP server - -The JVB will also need to know the location of the Prosody XMPP server. - -Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the variable for the JVB by using the variable `jitsi_xmpp_server`. - -##### Set the Matrix domain - -The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` files: - -```yaml -jitsi_xmpp_server: "{{ matrix_domain }}" -``` - -##### Set an IP address of the Matrix server - -Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address. - -To set the IP address of the Matrix server, add the following configuration to your `vars.yml` files: - -```yaml -jitsi_xmpp_server: "192.168.0.1" -``` - -##### Expose XMPP port - -By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it. - -To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` files: - -```yaml -jitsi_prosody_container_jvb_host_bind_port: 5222 -``` - -#### Reverse-proxy with Traefik - -To make Traefik reverse-proxy to these additional JVBs, add the following configuration to your main `vars.yml` file (`inventory/host_vars/matrix.example.com/vars.yml`): - -```yaml -# Traefik proxying for additional JVBs. These can't be configured using Docker -# labels, like the first JVB is, because they run on different hosts, so we add -# the necessary configuration to the file provider. -traefik_provider_configuration_extension_yaml: | - http: - routers: - {% for host in groups['jitsi_jvb_servers'] %} - - additional-{{ hostvars[host]['jitsi_jvb_server_id'] }}-router: - entryPoints: - - "{{ traefik_entrypoint_primary }}" - rule: "Host(`{{ jitsi_hostname }}`) && PathPrefix(`/colibri-ws/{{ hostvars[host]['jitsi_jvb_server_id'] }}/`)" - service: additional-{{ hostvars[host]['jitsi_jvb_server_id'] }}-service - {% if traefik_entrypoint_primary != 'web' %} - - tls: - certResolver: "{{ traefik_certResolver_primary }}" - - {% endif %} - - {% endfor %} - - services: - {% for host in groups['jitsi_jvb_servers'] %} - - additional-{{ hostvars[host]['jitsi_jvb_server_id'] }}-service: - loadBalancer: - servers: - - url: "http://{{ host }}:9090/" - - {% endfor %} -``` - -#### Run the playbook - -After configuring `hosts` and `vars.yml` files, run the playbook with [playbook tags](playbook-tags.md) as below: - -```sh -ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start -``` - ## Troubleshooting As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running the commands below: From 3becee78ae8946a7d6ac5909902965575642ccb2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 17 Feb 2025 23:03:22 +0900 Subject: [PATCH 601/952] Update docs/configuring-playbook-jitsi.md: replace the instruction for troubleshooting with a link to the role's document The instruction is available at https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/af5b04fc32e79cdcdf091dff993856c14d1e4d70/docs/configuring-jitsi.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-jitsi.md | 25 +------------------------ 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 84288349c..44700b59f 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -112,27 +112,4 @@ Check [the official user guide](https://jitsi.github.io/handbook/docs/category/u ## Troubleshooting -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running the commands below: -- `journalctl -fu matrix-jitsi-web` -- `journalctl -fu matrix-jitsi-prosody` -- `journalctl -fu matrix-jitsi-jicofo` -- `journalctl -fu matrix-jitsi-jvb` - -### `Error: Account creation/modification not supported` - -If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support. - -In this case, you should consider to rebuild your Jitsi installation. - -### Rebuilding your Jitsi installation - -If you ever run into any trouble or if you have changed configuration (`jitsi_*` variables) too much, you can rebuild your Jitsi installation. - -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. - -To rebuild your Jitsi configuration, follow the procedure below: - -- run this command locally to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi` -- log in the server with SSH -- run this command remotely to remove all Jitsi configuration & data: `rm -rf /matrix/jitsi` -- run this command locally to set up Jitsi anew and restart services: `just install-service jitsi` +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 document for details. From a8c6682333b2d64998aa13386cb50f4572b785b1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 00:24:16 +0900 Subject: [PATCH 602/952] Apply suggestions from code review Co-authored-by: Slavi Pantaleev --- docs/configuring-playbook-etherpad.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index bde0fb638..066df3069 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -18,8 +18,8 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. -The Ansible role for Etherpad is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: -- [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md) +The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: +- [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) - `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles ## Adjusting DNS records @@ -50,7 +50,7 @@ etherpad_enabled: true 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. -See the role's document 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)). +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)). ### Create admin user (optional) From 1693581013d19f654bb68cc87c9a83ffc9f8bb09 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 00:27:01 +0900 Subject: [PATCH 603/952] Change "role's document" to "role's documentation" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-etherpad.md | 6 +++--- docs/configuring-playbook-jitsi.md | 10 +++++----- docs/configuring-playbook-postgres-backup.md | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 135ca8501..1de46a2b7 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -15,5 +15,5 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. For details about configuring and installing it, you can check them via: -- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) +- [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) - `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have fetched the Ansible roles diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 066df3069..81374eb4b 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -58,7 +58,7 @@ You probably might want to enable authentication to disallow anonymous access to 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. -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 document for details about how to create the admin user. +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. ### Adjusting the Etherpad URL (optional) @@ -102,7 +102,7 @@ By default, the Etherpad UI should be available at `https://etherpad.example.com 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. -💡 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 document. +💡 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. ### Integrating a Etherpad widget in a room @@ -112,4 +112,4 @@ To integrate a standalone Etherpad in a room, create your pad by visiting `https ## Troubleshooting -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 document for details. +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. diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 44700b59f..5fc84b2a7 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -21,14 +21,14 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: -- [the role's document at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) +- [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) - `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have fetched the Ansible roles ## Prerequisites 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). -You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's document](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. +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. ## Adjusting DNS records @@ -60,7 +60,7 @@ As the most of the necessary settings for the role have been taken care of by th 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. -See the role's document 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)). +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)). ### Enable authentication and guests mode (optional) @@ -68,7 +68,7 @@ By default the Jitsi Meet instance **does not require for anyone to log in, and 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. -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 document 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)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. +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)](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/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. ### Enable Gravatar (optional) @@ -112,4 +112,4 @@ Check [the official user guide](https://jitsi.github.io/handbook/docs/category/u ## Troubleshooting -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 document for details. +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. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 27aafd1ae..24834162d 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later 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. For details about configuring and installing it, you can check them via: -- [the role's document on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) +- [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) - `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have fetched the Ansible roles **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. From cc0811492be3b21da46584294abaa6a1d96af6ec Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 00:33:01 +0900 Subject: [PATCH 604/952] Add links to installing.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 1de46a2b7..dff77045c 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -16,4 +16,4 @@ BorgBackup is a deduplicating backup program with optional compression and encry For details about configuring and installing it, you can check them via: - [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) -- `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have fetched the Ansible roles +- `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 81374eb4b..9ec25739b 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -20,7 +20,7 @@ When enabled together with the Jitsi video-conferencing platform (see [our docs The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: - [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) -- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have fetched the Ansible roles +- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Adjusting DNS records diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 5fc84b2a7..9bca704d3 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -22,7 +22,7 @@ Jitsi is an open source video-conferencing platform. It can not only be integrat The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: - [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) -- `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have fetched the Ansible roles +- `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Prerequisites diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 24834162d..4c1897455 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -12,6 +12,6 @@ The playbook can install and configure [docker-postgres-backup-local](https://gi For details about configuring and installing it, you can check them via: - [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) -- `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have fetched the Ansible roles +- `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) **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. From 4b390bb50a8ae6cc888fe8a341697ccd10091fbd Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 17 Feb 2025 18:05:35 +0200 Subject: [PATCH 605/952] fix jitsi role --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index ed9b88a13..e8a9f2630 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.5.1-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v10008-0 + version: v10008-1 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git version: v2.11.0-1 From ac6fb796321fee9190c50f50a6c4a05f5d510466 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 01:12:21 +0900 Subject: [PATCH 606/952] Update docs for BackupBprg and docker-postgres-backup-local: adopt the common description Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 4 ++-- docs/configuring-playbook-postgres-backup.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index dff77045c..c2917199b 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -14,6 +14,6 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. -For details about configuring and installing it, you can check them via: -- [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/docs/configuring-backup-borg.md) +The Ansible role for BorgBackup is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: +- [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) - `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 4c1897455..562ff8cb1 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -8,10 +8,10 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up Postgres backup (optional) -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. +The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. -For details about configuring and installing it, you can check them via: -- [the role's documentation on the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/blob/main/docs/configuring-postgres-backup.md) +The Ansible role for docker-postgres-backup-local is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: +- [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) - `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) **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. From 9dc9646fe76a59a5821c8b78cf61e3305fa4df83 Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 18 Feb 2025 10:41:20 +0200 Subject: [PATCH 607/952] Honoroit v0.9.27 --- roles/custom/matrix-bot-honoroit/defaults/main.yml | 5 ++++- roles/custom/matrix-bot-honoroit/templates/env.j2 | 1 + 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-honoroit/defaults/main.yml b/roles/custom/matrix-bot-honoroit/defaults/main.yml index 850842db6..5b7720689 100644 --- a/roles/custom/matrix-bot-honoroit/defaults/main.yml +++ b/roles/custom/matrix-bot-honoroit/defaults/main.yml @@ -21,7 +21,7 @@ matrix_bot_honoroit_docker_repo_version: "{{ matrix_bot_honoroit_version }}" matrix_bot_honoroit_docker_src_files_path: "{{ matrix_base_data_path }}/honoroit/docker-src" # renovate: datasource=docker depName=ghcr.io/etkecc/honoroit -matrix_bot_honoroit_version: v0.9.26 +matrix_bot_honoroit_version: v0.9.27 matrix_bot_honoroit_docker_image: "{{ matrix_bot_honoroit_docker_image_name_prefix }}etkecc/honoroit:{{ matrix_bot_honoroit_version }}" matrix_bot_honoroit_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_honoroit_container_image_self_build else 'ghcr.io/' }}" matrix_bot_honoroit_docker_image_force_pull: "{{ matrix_bot_honoroit_docker_image.endswith(':latest') }}" @@ -178,6 +178,9 @@ matrix_bot_honoroit_cachesize: '' # List of ignored room IDs matrix_bot_honoroit_ignoredrooms: [] +# If enabled, the bot will not send a warning message in an encrypted room +matrix_bot_honoroit_no_encryption_warning: false + # Ignore messages outside of threads matrix_bot_honoroit_ignorenothread: false diff --git a/roles/custom/matrix-bot-honoroit/templates/env.j2 b/roles/custom/matrix-bot-honoroit/templates/env.j2 index e061a3687..abbb66f0f 100644 --- a/roles/custom/matrix-bot-honoroit/templates/env.j2 +++ b/roles/custom/matrix-bot-honoroit/templates/env.j2 @@ -5,6 +5,7 @@ HONOROIT_ROOMID={{ matrix_bot_honoroit_roomid }} HONOROIT_DB_DSN={{ matrix_bot_honoroit_database_connection_string }} HONOROIT_DB_DIALECT={{ matrix_bot_honoroit_database_dialect }} HONOROIT_PREFIX={{ matrix_bot_honoroit_prefix }} +HONOROIT_NOENCRYPTIONWARNING={{ matrix_bot_honoroit_no_encryption_warning }} HONOROIT_AUTH_METRICS_LOGIN={{ matrix_bot_honoroit_auth_metrics_login }} HONOROIT_AUTH_METRICS_PASSWORD={{ matrix_bot_honoroit_auth_metrics_password }} HONOROIT_AUTH_METRICS_IPS={{ matrix_bot_honoroit_auth_metrics_ips | default([]) | join(' ') }} From 7702983d63b044f79cd8ad764c27d17a10a129fa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 18:18:26 +0900 Subject: [PATCH 608/952] Update jitsi_jvb.yml: replace "Jitsi JVB" to "Jitsi Videobridge (JVB)" Signed-off-by: Suguru Hirahara --- jitsi_jvb.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jitsi_jvb.yml b/jitsi_jvb.yml index 16acd0ee6..33786bebe 100644 --- a/jitsi_jvb.yml +++ b/jitsi_jvb.yml @@ -1,5 +1,5 @@ --- -- name: "Set up additional Jitsi JVB servers" +- name: "Set up additional Jitsi Videobridge (JVB) servers" hosts: "jitsi_jvb_servers" become: true From a3954ec4a4f7bfb0d6a3b346618794900e5bd9fe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 19:54:07 +0900 Subject: [PATCH 609/952] Update docs linking to the documentation at the MASH project: add emojis to list items Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 4 ++-- docs/configuring-playbook-etherpad.md | 4 ++-- docs/configuring-playbook-jitsi.md | 4 ++-- docs/configuring-playbook-postgres-backup.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index c2917199b..eb5a31375 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -15,5 +15,5 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. The Ansible role for BorgBackup is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: -- [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) -- `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) +- 📄 [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) +- 📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 9ec25739b..d5da149ad 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -19,8 +19,8 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: -- [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) -- `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) +- 📄 [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) +- 📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Adjusting DNS records diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 9bca704d3..c93216ac6 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -21,8 +21,8 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: -- [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) -- `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) +- 📄 [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) +- 📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Prerequisites diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 562ff8cb1..a704b13ae 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. The Ansible role for docker-postgres-backup-local is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: -- [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) -- `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) +- 📄 [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) +- 📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) **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. From e621b00370648f1fc8f1c53c79c63b564617532e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 20:48:41 +0900 Subject: [PATCH 610/952] Update docs linking to the MASH project's roles Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index eb5a31375..251e81fec 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -14,6 +14,6 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. -The Ansible role for BorgBackup is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: +The Ansible role for BorgBackup is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: - 📄 [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) - 📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index c93216ac6..9c568ecf5 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -20,7 +20,7 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. -The Ansible role for Jitsi is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: +The Ansible role for Jitsi is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: - 📄 [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) - 📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index a704b13ae..ffb0ed9fb 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -10,7 +10,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. -The Ansible role for docker-postgres-backup-local is developed and maintained by [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: +The Ansible role for docker-postgres-backup-local is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: - 📄 [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) - 📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) From 8709981cbef9c4c753eaa67607e411c5eba5f915 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 23:04:55 +0900 Subject: [PATCH 611/952] Update docs linking to the MASH project's roles: replace the paper icon with globe Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index 251e81fec..c382569cc 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -15,5 +15,5 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. The Ansible role for BorgBackup is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: -- 📄 [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) +- 🌐 [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) - 📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index d5da149ad..79601499a 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -19,7 +19,7 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: -- 📄 [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) +- 🌐 [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) - 📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Adjusting DNS records diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 9c568ecf5..af989e38b 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -21,7 +21,7 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. The Ansible role for Jitsi is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: -- 📄 [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) +- 🌐 [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) - 📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Prerequisites diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index ffb0ed9fb..710f6853a 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. The Ansible role for docker-postgres-backup-local is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: -- 📄 [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) +- 🌐 [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) - 📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) **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. From 2f069bfadd72334075cf9476c503aed8580d7c47 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 18 Feb 2025 23:07:00 +0900 Subject: [PATCH 612/952] Update docs linking to the MASH project's roles: add "online" as suffix in comparison to "locally" Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index c382569cc..cef21d45a 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -15,5 +15,5 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. The Ansible role for BorgBackup is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: -- 🌐 [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) +- 🌐 [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 - 📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 79601499a..4a9287dd8 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -19,7 +19,7 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: -- 🌐 [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) +- 🌐 [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 - 📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Adjusting DNS records diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index af989e38b..7f4eaa535 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -21,7 +21,7 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. The Ansible role for Jitsi is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: -- 🌐 [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) +- 🌐 [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 - 📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Prerequisites diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 710f6853a..08aa8ef71 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. The Ansible role for docker-postgres-backup-local is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: -- 🌐 [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) +- 🌐 [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 - 📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) **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. From f798ec81e83ff1d1498f1953a426c2ed97ed4005 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 18 Feb 2025 21:00:55 +0200 Subject: [PATCH 613/952] Upgrade matrix-authentication-service (0.13.0 -> 0.14.0) and mark matrix-reminder-bot's usage with it as fixed --- roles/custom/matrix-authentication-service/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 2936d313f..a0a06eb4b 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -17,7 +17,7 @@ matrix_authentication_service_container_repo_version: "{{ 'main' if matrix_authe matrix_authentication_service_container_src_files_path: "{{ matrix_base_data_path }}/matrix-authentication-service/container-src" # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service -matrix_authentication_service_version: 0.13.0 +matrix_authentication_service_version: 0.14.0 matrix_authentication_service_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service:{{ matrix_authentication_service_version }}" matrix_authentication_service_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_container_image_force_pull: "{{ matrix_authentication_service_container_image.endswith(':latest') }}" From 4e981ed36c520370fb8ce2614c6745fbed5c5715 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 18 Feb 2025 21:04:09 +0200 Subject: [PATCH 614/952] Mark matrix-reminder-bot's usage with matrix-authentication-service as fixed Fixup for f798ec81e83ff1d1498f1953a426c2ed97ed4005. --- docs/configuring-playbook-matrix-authentication-service.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index 0c86096b6..da339f5ed 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -52,9 +52,6 @@ This section details what you can expect when switching to the Matrix Authentica > cannot initialize matrix bot error="olm account is marked as shared, keys seem to have disappeared from the server" - - [matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439)) - - Other services may be similarly affected. This list is not exhaustive. - - ❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting). - ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break. From 2bca5cb445a99ac2220c518736fdea5c517062c0 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 18 Feb 2025 20:01:35 +0000 Subject: [PATCH 615/952] Update ghcr.io/element-hq/matrix-authentication-service/syn2mas Docker tag to v0.14.0 --- roles/custom/matrix-authentication-service/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index a0a06eb4b..33c998a17 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -555,7 +555,7 @@ matrix_authentication_service_syn2mas_start_wait_time_seconds: 5 matrix_authentication_service_syn2mas_dry_run: false # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service/syn2mas -matrix_authentication_service_syn2mas_version: 0.13.0 +matrix_authentication_service_syn2mas_version: 0.14.0 matrix_authentication_service_syn2mas_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service/syn2mas:{{ matrix_authentication_service_syn2mas_version }}" matrix_authentication_service_syn2mas_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_syn2mas_container_image_force_pull: "{{ matrix_authentication_service_syn2mas_container_image.endswith(':latest') }}" From 53a55cdc4c6889f857c8b7b87da7c28318903cd2 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 18 Feb 2025 20:25:56 +0000 Subject: [PATCH 616/952] Update dependency Sphinx to v8.2.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 9a2b21645..159799311 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -19,7 +19,7 @@ PyYAML==6.0.2 requests==2.32.3 setuptools==75.8.0 snowballstemmer==2.2.0 -Sphinx==8.1.3 +Sphinx==8.2.0 sphinx-intl==2.3.1 sphinx-markdown-builder==0.6.8 sphinxcontrib-applehelp==2.0.0 From 20d1352a4965cb63e1b9701517055d70425bae2f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 19 Feb 2025 15:11:42 +0900 Subject: [PATCH 617/952] Update docs/configuring-playbook-email.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index e3713c142..8968b48f1 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -1,3 +1,12 @@ + + # Adjusting email-sending settings (optional) By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails. From a56b49da03ab24de5736041ec9d92f9e00b43176 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 19 Feb 2025 06:20:40 +0000 Subject: [PATCH 618/952] Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2025.2.19 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index ea631464f..561ca62a2 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -6,7 +6,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2025.2.9 +matrix_alertmanager_receiver_version: 2025.2.19 matrix_alertmanager_receiver_scheme: https From ac26cc1cb0d6423b751b74ddb06a8c793f63dd56 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 19 Feb 2025 11:48:12 +0200 Subject: [PATCH 619/952] Allow STUN/TURN exposure over TCP/UDP to be controlled separately & disable STUN over UDP by default --- CHANGELOG.md | 22 ++++++++++++++++ docs/prerequisites.md | 7 +++--- group_vars/matrix_servers | 4 +-- roles/custom/matrix-coturn/defaults/main.yml | 25 ++++++++++++++++--- .../matrix-coturn/tasks/validate_config.yml | 2 ++ .../systemd/matrix-coturn.service.j2 | 16 +++++++----- 6 files changed, 60 insertions(+), 16 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 85bdaed2e..c27faf943 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,25 @@ +# 2025-02-19 + +## The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP + +We've previously done some work to **decrease the severity** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md)'s STUN port (2.8x -> 1.6x) as reported in [coturn: Lower DDoS amplification/reflection factor from 2.8 to 1.6 #2592](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2592). + +To **completely eliminate the problem** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md) STUN port even further (read more about this in [this article](https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit)), the playbook now **disables exposure of the Coturn STUN port (`3478`) over UDP**. This is a bit heavy-handed, but is probably the only way to completely eliminate the problem. + +The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by default**. + +💡 Users may wish to further remove the (now unnnecessary) firewall rule allowing access to `3478/udp`. + +If you'd like the Coturn STUN port to be exposed over UDP like before, you can revert to the previous behavior by using the following configuration in your `vars.yml` file: + +```yaml +matrix_coturn_container_stun_plain_host_bind_port_udp: "3478" +``` + +> [!WARNING] +> People running Coturn directly on the `host` network (using `matrix_coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc). + + # 2025-02-17 ## FluffyChat Web suport diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 3bd3da975..94445befe 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -48,10 +48,9 @@ We will be using `example.com` as the domain in the following instruction. Pleas - `80/tcp`: HTTP webserver - `443/tcp` and `443/udp`: HTTPS webserver - - `3478/tcp`: TURN over TCP (used by coturn) - - `3478/udp`: TURN over UDP (used by coturn) - - `5349/tcp`: TURN over TCP (used by coturn) - - `5349/udp`: TURN over UDP (used by coturn) + - `3478/tcp`: STUN/TURN over TCP (used by [coturn](./docs/configuring-playbook-turn.md)) + - `5349/tcp`: TURN over TCP (used by [coturn](./docs/configuring-playbook-turn.md)) + - `5349/udp`: TURN over UDP (used by [coturn](./docs/configuring-playbook-turn.md)) - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**. - the range `49152-49172/udp`: TURN over UDP - potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that. diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index ac2f386dd..46e08f6a8 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3615,8 +3615,8 @@ jitsi_web_framing_enabled: true jitsi_turn_credentials: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" jitsi_turn_host: "{{ ('turn.' + matrix_server_fqn_matrix) if matrix_coturn_enabled else '' }}" jitsi_turns_host: "{{ ('turn.' + matrix_server_fqn_matrix) if matrix_coturn_enabled else '' }}" -jitsi_turn_port: "{{ matrix_coturn_container_stun_plain_host_bind_port.split(':')[-1] if matrix_coturn_enabled else '' }}" -jitsi_turns_port: "{{ matrix_coturn_container_stun_tls_host_bind_port.split(':')[-1] if matrix_coturn_enabled else '' }}" +jitsi_turn_port: "{{ matrix_coturn_container_stun_plain_host_bind_port_tcp.split(':')[-1] if matrix_coturn_enabled else '' }}" +jitsi_turns_port: "{{ matrix_coturn_container_stun_tls_host_bind_port_tcp.split(':')[-1] if matrix_coturn_enabled else '' }}" # If the self-hosted Etherpad instance is available, it will also show up in Jitsi conferences, # unless explicitly disabled by setting `jitsi_etherpad_enabled` to false. diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index 60641c196..78e8e35f9 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -51,15 +51,32 @@ matrix_coturn_container_additional_volumes: [] # A list of extra arguments to pass to the container matrix_coturn_container_extra_arguments: [] -# Controls whether the coturn container exposes its plain STUN port (tcp/3478 and udp/3478 in the container). +# Controls whether the coturn container exposes its plain STUN port (tcp/3478 in the container) over TCP. # # Takes an ":" or "" value (e.g. "127.0.0.1:3478"), or empty string to not expose. -matrix_coturn_container_stun_plain_host_bind_port: "{{ '3478' if matrix_coturn_container_network != 'host' else '' }}" +matrix_coturn_container_stun_plain_host_bind_port_tcp: "{{ '3478' if matrix_coturn_container_network != 'host' else '' }}" -# Controls whether the coturn container exposes its TLS STUN port (tcp/5349 and udp/5349 in the container). +# Controls whether the coturn container exposes its plain STUN port (udp/3478 in the container) over UDP. +# +# Takes an ":" or "" value (e.g. "127.0.0.1:3478"), or empty string to not expose. +# +# This is not done by default to decrease the risk of DDoS amplification attacks. +# See: https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit +matrix_coturn_container_stun_plain_host_bind_port_udp: "" + +# Controls whether the coturn container exposes its TLS STUN port (tcp/5349 in the container) over TCP. # # Takes an ":" or "" value (e.g. "127.0.0.1:5349"), or empty string to not expose. -matrix_coturn_container_stun_tls_host_bind_port: "{{ '5349' if matrix_coturn_container_network != 'host' else '' }}" +matrix_coturn_container_stun_tls_host_bind_port_tcp: "{{ '5349' if matrix_coturn_container_network != 'host' else '' }}" + +# Controls whether the coturn container exposes its TLS STUN port (udp/5349 in the container) over UDP. +# +# Takes an ":" or "" value (e.g. "127.0.0.1:5349"), or empty string to not expose. +# +# This is enabled by default, unlike `matrix_coturn_container_stun_plain_host_bind_port_udp`, +# because the risk of DDoS amplification attacks is lower for TLS +# due to the handshake requiring two-way authentication and being generally more expensive. +matrix_coturn_container_stun_tls_host_bind_port_udp: "{{ '5349' if matrix_coturn_container_network != 'host' else '' }}" # Controls whether the coturn container exposes its TURN UDP port range and which interface to do it on. # diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml index 7fd26e881..a90adb812 100644 --- a/roles/custom/matrix-coturn/tasks/validate_config.yml +++ b/roles/custom/matrix-coturn/tasks/validate_config.yml @@ -8,6 +8,8 @@ when: "item.old in vars" with_items: - {'old': 'matrix_coturn_docker_network', 'new': 'matrix_coturn_container_network'} + - {'old': 'matrix_coturn_container_stun_plain_host_bind_port', 'new': 'superseded by matrix_coturn_container_stun_plain_host_bind_port_tcp and matrix_coturn_container_stun_plain_host_bind_port_udp'} + - {'old': 'matrix_coturn_container_stun_tls_host_bind_port', 'new': 'superseded by matrix_coturn_container_stun_tls_host_bind_port_tcp and matrix_coturn_container_stun_tls_host_bind_port_udp'} - name: Fail if matrix_coturn_authentication_method is invalid ansible.builtin.fail: diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 index 072975b2d..6d3ffe310 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 @@ -24,13 +24,17 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --read-only \ --tmpfs=/var/tmp:rw,noexec,nosuid,size=100m \ --network={{ matrix_coturn_container_network }} \ - {% if matrix_coturn_container_stun_plain_host_bind_port != '' %} - -p {{ matrix_coturn_container_stun_plain_host_bind_port }}:3478 \ - -p {{ matrix_coturn_container_stun_plain_host_bind_port }}:3478/udp \ + {% if matrix_coturn_container_stun_plain_host_bind_port_tcp != '' %} + -p {{ matrix_coturn_container_stun_plain_host_bind_port_tcp }}:3478 \ {% endif %} - {% if matrix_coturn_container_stun_tls_host_bind_port != '' %} - -p {{ matrix_coturn_container_stun_tls_host_bind_port }}:5349 \ - -p {{ matrix_coturn_container_stun_tls_host_bind_port }}:5349/udp \ + {% if matrix_coturn_container_stun_plain_host_bind_port_udp != '' %} + -p {{ matrix_coturn_container_stun_plain_host_bind_port_udp }}:3478/udp \ + {% endif %} + {% if matrix_coturn_container_stun_tls_host_bind_port_tcp != '' %} + -p {{ matrix_coturn_container_stun_tls_host_bind_port_tcp }}:5349 \ + {% endif %} + {% if matrix_coturn_container_stun_tls_host_bind_port_udp != '' %} + -p {{ matrix_coturn_container_stun_tls_host_bind_port_udp }}:5349/udp \ {% endif %} {% if matrix_coturn_container_turn_range_listen_interface is not in [none, 'none'] %} -p {{ matrix_coturn_container_turn_range_listen_interface }}{{ ':' if matrix_coturn_container_turn_range_listen_interface else '' }}{{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}:{{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}/udp \ From c0722c74e9476ea49cccbc22f514570bb852f5b2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:03:55 +0900 Subject: [PATCH 620/952] Update docs/configuring-playbook-email.md: add the links to the role and its documentation Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 8968b48f1..3e01449a7 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -20,6 +20,10 @@ By default, emails are sent from `matrix@matrix.example.com`, as specified by th 💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway. +The Ansible role for exim-relay is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay). For details about configuring exim-relay, you can check them via: +- 🌐 [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 +- 📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) + ## Firewall settings No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration). From 916831f94d142945a1a67c87edcacd3ec1765f5d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:04:07 +0900 Subject: [PATCH 621/952] Update docs/configuring-playbook-email.md: refer the docs at the role Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 48 ++++-------------------------- 1 file changed, 6 insertions(+), 42 deletions(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 3e01449a7..1ab654181 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -11,15 +11,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails. -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.) - By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable. -> [!WARNING] -> On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server). - -💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway. - The Ansible role for exim-relay is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay). For details about configuring exim-relay, you can check them via: - 🌐 [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 - 📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) @@ -30,45 +23,16 @@ No matter whether you send email directly (the default) or you relay email throu ## Adjusting the playbook configuration -### Relaying email through another SMTP server +### Relaying email through another SMTP server (optional) -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): +By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration (SPF settings, etc.) -```yaml -exim_relay_sender_address: "another.sender@example.com" -exim_relay_relay_use: true -exim_relay_relay_host_name: "mail.example.com" -exim_relay_relay_host_port: 587 -exim_relay_relay_auth: true -exim_relay_relay_auth_username: "another.sender@example.com" -exim_relay_relay_auth_password: "PASSWORD_FOR_THE_RELAY_HERE" -``` +**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. -**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**. +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. -### Sending emails using Sendgrid - -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. - -To set it up, add the following configuration to your `vars.yml` file (adapt to your needs): - -```yaml -exim_relay_sender_address: "example@example.org" -exim_relay_relay_use: true -exim_relay_relay_host_name: "smtp.sendgrid.net" -exim_relay_relay_host_port: 587 -exim_relay_relay_auth: true - -# This needs to be literally the string "apikey". It is always the same for Sendgrid. -exim_relay_relay_auth_username: "apikey" - -# You can generate the API key password at this URL: https://app.sendgrid.com/settings/api_keys -# The password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`. -exim_relay_relay_auth_password: "YOUR_API_KEY_PASSWORD_HERE" -``` +💡 To improve deliverability, we recommend relaying email through another SMTP server anyway. ## Troubleshooting -If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs. - -To do so, log in to the server with SSH and run `journalctl -f -u matrix-exim-relay`. +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. From 2e9e6e60947d06909ff0a67ef0ae55ad931594a3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:04:13 +0900 Subject: [PATCH 622/952] Update docs/configuring-playbook-email.md: edit the introduction Based on https://github.com/mother-of-all-self-hosting/mash-playbook/blob/00214dc4939981f187b1678678ecfc6c1bcd29df/docs/services/exim-relay.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 1ab654181..4a24a89ca 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -9,9 +9,9 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Adjusting email-sending settings (optional) -By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails. +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. -By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable. +**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. The Ansible role for exim-relay is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay). For details about configuring exim-relay, you can check them via: - 🌐 [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 @@ -19,7 +19,7 @@ The Ansible role for exim-relay is developed and maintained by [the MASH (mother ## Firewall settings -No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration). +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). ## Adjusting the playbook configuration From 5b3b372f367df24b616ec41b2536c41365eb7604 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:04:23 +0900 Subject: [PATCH 623/952] Update docs/configuring-playbook-email.md: copy the instruction for firewall It was copied from https://github.com/mother-of-all-self-hosting/mash-playbook/commit/699b458733b0d890588286a0345b3636c79f7b58. The current copyright header covers this one. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 4a24a89ca..4857796bd 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -21,6 +21,8 @@ The Ansible role for exim-relay is developed and maintained by [the MASH (mother 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). +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. + ## Adjusting the playbook configuration ### Relaying email through another SMTP server (optional) From 235f11fede6c9ce9b73d6c1144ba7edab86e801f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:04:32 +0900 Subject: [PATCH 624/952] Update docs/configuring-playbook-email.md: add an instruction to disable mail service Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 4857796bd..ceaca94c1 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -35,6 +35,18 @@ For details about configuration, refer [this section](https://github.com/mother- 💡 To improve deliverability, we recommend relaying email through another SMTP server anyway. +### Disable mail service (optional) + +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: + +```yaml +exim_relay_enabled: false +``` + +Note that disabling exim-relay will stop email-notifications and other similar functions from working. + +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. + ## Troubleshooting 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. From c1bd6ba965f9b26c5e61e3c5e1ab75fd92d763f3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 01:04:37 +0900 Subject: [PATCH 625/952] Update docs/configuring-playbook-email.md: copy the common section for installing The copyright header covers this one. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index ceaca94c1..a1d7dff76 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -47,6 +47,19 @@ Note that disabling exim-relay will stop email-notifications and other similar f 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. +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + ## Troubleshooting 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. From 9c822f7817e1ab99ad51ce65bd9e0dba4115f4f2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 20 Feb 2025 14:26:03 +0900 Subject: [PATCH 626/952] Update docs/faq.md: remove matrix_ma1sd_enabled from the suggestion to disable it ma1sd has not been installed by default since 958d089b68d46d1810b3b508234bfc4809522f68, so it seems that the variable does not need to be mentioned here. Signed-off-by: Suguru Hirahara --- docs/faq.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index c7e4cd2fb..04bfde784 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -296,9 +296,6 @@ See [Serving the base domain](configuring-playbook-base-domain-serving.md). You can disable some not-so-important services to save on memory. ```yaml -# An identity server is not a must. -matrix_ma1sd_enabled: false - # Disabling this will prevent email-notifications and other such things from working. exim_relay_enabled: false From 2db103a4ebfa413641ca74dc00eae5354f9afc79 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 20 Feb 2025 10:41:27 +0200 Subject: [PATCH 627/952] Upgrade matrix-authentication-service (0.14.0 -> 0.14.1) --- roles/custom/matrix-authentication-service/defaults/main.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 33c998a17..f00cb8eda 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -17,7 +17,7 @@ matrix_authentication_service_container_repo_version: "{{ 'main' if matrix_authe matrix_authentication_service_container_src_files_path: "{{ matrix_base_data_path }}/matrix-authentication-service/container-src" # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service -matrix_authentication_service_version: 0.14.0 +matrix_authentication_service_version: 0.14.1 matrix_authentication_service_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service:{{ matrix_authentication_service_version }}" matrix_authentication_service_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_container_image_force_pull: "{{ matrix_authentication_service_container_image.endswith(':latest') }}" @@ -555,7 +555,7 @@ matrix_authentication_service_syn2mas_start_wait_time_seconds: 5 matrix_authentication_service_syn2mas_dry_run: false # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service/syn2mas -matrix_authentication_service_syn2mas_version: 0.14.0 +matrix_authentication_service_syn2mas_version: 0.14.1 matrix_authentication_service_syn2mas_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service/syn2mas:{{ matrix_authentication_service_syn2mas_version }}" matrix_authentication_service_syn2mas_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" matrix_authentication_service_syn2mas_container_image_force_pull: "{{ matrix_authentication_service_syn2mas_container_image.endswith(':latest') }}" From c80fb913e7973deb76da6f445b565d9fc364823f Mon Sep 17 00:00:00 2001 From: Aine Date: Thu, 20 Feb 2025 15:48:19 +0200 Subject: [PATCH 628/952] borg backup: do not backup remote content by default --- group_vars/matrix_servers | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 46e08f6a8..285a26470 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3144,7 +3144,7 @@ backup_borg_location_source_directories: backup_borg_location_exclude_patterns: | {{ - ([matrix_synapse_media_store_path + '/local_thumbnails', matrix_synapse_media_store_path + '/remote_thumbnail', matrix_synapse_media_store_path + '/url_cache', matrix_synapse_media_store_path + '/url_cache_thumbnails'] if matrix_homeserver_implementation == 'synapse' else []) + ([matrix_synapse_media_store_path + '/remote_content', matrix_synapse_media_store_path + '/local_thumbnails', matrix_synapse_media_store_path + '/remote_thumbnail', matrix_synapse_media_store_path + '/url_cache', matrix_synapse_media_store_path + '/url_cache_thumbnails'] if matrix_homeserver_implementation == 'synapse' else []) + ([postgres_data_path] if postgres_enabled else []) }} From 2f8489fce036ec5058f115521e0adcb9ae82acbc Mon Sep 17 00:00:00 2001 From: Aine Date: Thu, 20 Feb 2025 18:21:12 +0200 Subject: [PATCH 629/952] FluffyChat v1.25.0 --- roles/custom/matrix-client-fluffychat/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml index b0e974e11..98fb6aa59 100644 --- a/roles/custom/matrix-client-fluffychat/defaults/main.yml +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -8,7 +8,7 @@ matrix_client_fluffychat_container_image_self_build_repo: "https://github.com/et matrix_client_fluffychat_container_image_self_build_version: "{{ 'main' if matrix_client_fluffychat_version == 'latest' else matrix_client_fluffychat_version }}" # renovate: datasource=docker depName=ghcr.io/etkecc/fluffychat-web -matrix_client_fluffychat_version: v1.24.0 +matrix_client_fluffychat_version: v1.25.0 matrix_client_fluffychat_docker_image: "{{ matrix_client_fluffychat_docker_image_name_prefix }}etkecc/fluffychat-web:{{ matrix_client_fluffychat_version }}" matrix_client_fluffychat_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_fluffychat_container_image_self_build else 'ghcr.io/' }}" matrix_client_fluffychat_docker_image_force_pull: "{{ matrix_client_fluffychat_docker_image.endswith(':latest') }}" From 4e44c4885e02630a45247f8667dc7e94fc106a54 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 21 Feb 2025 12:23:26 +0900 Subject: [PATCH 630/952] Update docs: add copyright headers for reusing them at the MASH project This commit adds copyright headers to the same kind of docs as ones linked from https://github.com/mother-of-all-self-hosting/mash-playbook/tree/e48af8a3273b416188b1fa4bc9009ef7e923235f/docs/README.md, so that these files can be reused over there. - docs/README.md - prerequisites.md - configuring-dns.md - getting-the-playbook.md - configuring-playbook.md - maintenance-upgrading-services.md - maintenance-and-troubleshooting.md - uninstalling.md Signed-off-by: Suguru Hirahara --- docs/README.md | 9 +++++++++ docs/configuring-dns.md | 17 +++++++++++++++++ docs/getting-the-playbook.md | 7 +++++++ docs/installing.md | 14 ++++++++++++++ docs/maintenance-and-troubleshooting.md | 11 +++++++++++ docs/maintenance-upgrading-services.md | 11 +++++++++++ docs/prerequisites.md | 11 +++++++++++ docs/uninstalling.md | 8 ++++++++ 8 files changed, 88 insertions(+) diff --git a/docs/README.md b/docs/README.md index 34a660c7b..ba0fd1e48 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,3 +1,12 @@ + + # Table of Contents ## ⬇️ Installaton guides diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 51e30d69e..a5237889f 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -1,3 +1,20 @@ + + # Configuring your DNS settings [Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index 4db76c5c6..6607cae49 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -1,3 +1,10 @@ + + # Getting the playbook [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) diff --git a/docs/installing.md b/docs/installing.md index 860e8d9bf..e0bf44404 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -1,3 +1,17 @@ + + # Installing [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 99205697e..21d1c07ae 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -1,3 +1,14 @@ + + # Maintenance and Troubleshooting ## Maintenance diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md index ca1ea78f1..c6ef5f62d 100644 --- a/docs/maintenance-upgrading-services.md +++ b/docs/maintenance-upgrading-services.md @@ -1,3 +1,14 @@ + + # Upgrading the Matrix services This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available. diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 94445befe..8b813f1bd 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -1,3 +1,14 @@ + + # Prerequisites Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) diff --git a/docs/uninstalling.md b/docs/uninstalling.md index 4c70082f5..1a0f3f6ef 100644 --- a/docs/uninstalling.md +++ b/docs/uninstalling.md @@ -1,3 +1,11 @@ + + # Uninstalling > [!WARNING] From a445f8a5aef5182c2f208af933350d74bf791595 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 07:50:48 +0200 Subject: [PATCH 631/952] Upgrade postgres-backup (v17-0 -> v17-1) Ref: https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/pull/6 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index e8a9f2630..5c882cff8 100644 --- a/requirements.yml +++ b/requirements.yml @@ -43,7 +43,7 @@ version: v17.2-0 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git - version: v17-0 + version: v17-1 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git version: v2.55.1-0 From d6301db5edf9734b9d3f5f4c59b9b7ece4893818 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 07:51:51 +0200 Subject: [PATCH 632/952] Switch from `postgres_backup_databases` to `postgres_backup_databases_auto` Ref: https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup/pull/6 Related to a445f8a5aef5182c2f208af933350d74bf791595 --- group_vars/matrix_servers | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 285a26470..1fc6a5cf8 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -4246,7 +4246,7 @@ postgres_backup_connection_password: "{{ postgres_connection_password if postgre postgres_backup_postgres_data_path: "{{ postgres_data_path if postgres_enabled else '' }}" postgres_backup_postgres_role_include_name: galaxy/postgres -postgres_backup_databases: "{{ postgres_managed_databases | map(attribute='name') if postgres_enabled else [] }}" +postgres_backup_databases_auto: "{{ postgres_managed_databases | map(attribute='name') if postgres_enabled else [] }}" ######################################################################## # # From b0c63914cbba16b47ad8cac9f6bdfb9114c75d25 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 08:08:59 +0200 Subject: [PATCH 633/952] Upgrade backup-borg (v1.4.0-1.9.10-0 -> v1.4.0-1.9.10-1) Ref: - https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/pull/12 - https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/commit/02dd1a8d70f573e39d2edecba2dcf7cab5c2dba2 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 5c882cff8..fd7818cc4 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-0 + version: v1.4.0-1.9.10-1 name: backup_borg - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git version: v0.2.0-0 From 9d05994dce30c2a7509e6a90b0687e1849d8c3bf Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 08:09:38 +0200 Subject: [PATCH 634/952] Make use of `backup_borg_postgresql_databases_auto` Related to b0c63914cbba16b47ad8cac9f6bdfb9114c75d25 Ref: - https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/pull/12 - https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/commit/02dd1a8d70f573e39d2edecba2dcf7cab5c2dba2 --- group_vars/matrix_servers | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 1fc6a5cf8..5433ead4f 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3137,7 +3137,7 @@ backup_borg_postgresql_databases_hostname: "{{ postgres_connection_hostname if p backup_borg_postgresql_databases_username: "{{ postgres_connection_username if postgres_enabled else '' }}" backup_borg_postgresql_databases_password: "{{ postgres_connection_password if postgres_enabled else '' }}" backup_borg_postgresql_databases_port: "{{ postgres_connection_port if postgres_enabled else 5432 }}" -backup_borg_postgresql_databases: "{{ postgres_managed_databases | map(attribute='name') if postgres_enabled else [] }}" +backup_borg_postgresql_databases_auto: "{{ postgres_managed_databases | map(attribute='name') if postgres_enabled else [] }}" backup_borg_location_source_directories: - "{{ matrix_base_data_path }}" From 40dc285a3159c2b383a98b4f79a944b1de23fa90 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 21 Feb 2025 16:27:54 +0900 Subject: [PATCH 635/952] Update docs/playbook-tags.md: add a copyright header The original author can be seen here: 66a812d99c12cb24f38f57fb271875ca80a9d4cc/docs/installing.md#L12-L35 Signed-off-by: Suguru Hirahara --- docs/playbook-tags.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/playbook-tags.md b/docs/playbook-tags.md index 02da3ea7e..cd5cdcb39 100644 --- a/docs/playbook-tags.md +++ b/docs/playbook-tags.md @@ -1,3 +1,10 @@ + + # Playbook tags The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks. From 0dac0d8f83dfb4fd5bf69f04f4b0f4ac4b6cb125 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 21 Feb 2025 16:28:07 +0900 Subject: [PATCH 636/952] Update docs/just.md: add a copyright header This file was created with e36115a5b94b29c15d3159837d6a1e1b68ba5539 based on fb60ba67f646288b40818a555bb716405e144956 (announcement of adoption of just program). Signed-off-by: Suguru Hirahara --- docs/just.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/just.md b/docs/just.md index 153a20f1e..b02385f11 100644 --- a/docs/just.md +++ b/docs/just.md @@ -1,3 +1,10 @@ + + # Running `just` commands We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands. From ff986b7512923b2f410a5a47a37ad118edc433cd Mon Sep 17 00:00:00 2001 From: Zepmann Date: Wed, 19 Feb 2025 18:52:44 +0100 Subject: [PATCH 637/952] Add mautrix-bluesky to the playbook. --- group_vars/matrix_servers | 86 ++++ .../defaults/main.yml | 192 ++++++++ .../tasks/main.yml | 20 + .../tasks/setup_install.yml | 98 ++++ .../tasks/setup_uninstall.yml | 19 + .../tasks/validate_config.yml | 15 + .../templates/config.yaml.j2 | 428 ++++++++++++++++++ .../templates/labels.j2 | 46 ++ .../systemd/matrix-mautrix-bluesky.service.j2 | 48 ++ setup.yml | 1 + 10 files changed, 953 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2 create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 5433ead4f..94e0f3fc9 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -107,6 +107,8 @@ matrix_homeserver_container_extra_arguments_auto: | + (['--mount type=bind,src=' + matrix_hookshot_base_path + '/registration.yml,dst=/hookshot-registration.yml,ro'] if matrix_hookshot_enabled else []) + + (['--mount type=bind,src=' + matrix_mautrix_bluesky_config_path + '/registration.yaml,dst=/matrix-mautrix-bluesky-registration.yaml,ro'] if matrix_mautrix_bluesky_enabled else []) + + (['--mount type=bind,src=' + matrix_mautrix_discord_config_path + '/registration.yaml,dst=/matrix-mautrix-discord-registration.yaml,ro'] if matrix_mautrix_discord_enabled else []) + (['--mount type=bind,src=' + matrix_mautrix_slack_config_path + '/registration.yaml,dst=/matrix-mautrix-slack-registration.yaml,ro'] if matrix_mautrix_slack_enabled else []) @@ -178,6 +180,8 @@ matrix_homeserver_app_service_config_files_auto: | + (['/hookshot-registration.yml'] if matrix_hookshot_enabled else []) + + (['/matrix-mautrix-bluesky-registration.yaml'] if matrix_mautrix_bluesky_enabled else []) + + (['/matrix-mautrix-discord-registration.yaml'] if matrix_mautrix_discord_enabled else []) + (['/matrix-mautrix-slack-registration.yaml'] if matrix_mautrix_slack_enabled else []) @@ -320,6 +324,8 @@ devture_systemd_service_manager_services_list_auto: | + ([{'name': 'matrix-hookshot.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'hookshot', 'bridge-hookshot']}] if matrix_hookshot_enabled else []) + + ([{'name': 'matrix-mautrix-bluesky.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-bluesky']}] if matrix_mautrix_bluesky_enabled else []) + + ([{'name': 'matrix-mautrix-discord.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-discord']}] if matrix_mautrix_discord_enabled else []) + ([{'name': 'matrix-mautrix-slack.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mautrix-slack']}] if matrix_mautrix_slack_enabled else []) @@ -1077,6 +1083,75 @@ matrix_go_skype_bridge_database_password: "{{ '%s' | format(matrix_homeserver_ge # ###################################################################### +###################################################################### +# +# matrix-bridge-mautrix-bluesky +# +###################################################################### + +# We don't enable bridges by default. +matrix_mautrix_bluesky_enabled: false + +matrix_mautrix_bluesky_systemd_required_services_list_auto: | + {{ + matrix_addons_homeserver_systemd_services_list + + + ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_bluesky_database_hostname == postgres_connection_hostname) else []) + }} + +matrix_mautrix_bluesky_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" + +matrix_mautrix_bluesky_container_network: "{{ matrix_addons_container_network }}" + +matrix_mautrix_bluesky_container_additional_networks_auto: |- + {{ + ( + ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) + + + ([postgres_container_network] if (postgres_enabled and matrix_mautrix_bluesky_database_hostname == postgres_connection_hostname and matrix_mautrix_bluesky_container_network != postgres_container_network) else []) + + + ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network and matrix_mautrix_bluesky_container_labels_traefik_enabled else []) + ) | unique + }} + +matrix_mautrix_bluesky_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}" +matrix_mautrix_bluesky_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" +matrix_mautrix_bluesky_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" +matrix_mautrix_bluesky_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" + +matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_enabled: "{{ matrix_metrics_exposure_http_basic_auth_enabled }}" +matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_users: "{{ matrix_metrics_exposure_http_basic_auth_users }}" + +matrix_mautrix_bluesky_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'twt.as.token', rounds=655555) | to_uuid }}" + +matrix_mautrix_bluesky_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" +matrix_mautrix_bluesky_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'twt.hs.token', rounds=655555) | to_uuid }}" + +matrix_mautrix_bluesky_provisioning_shared_secret: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.twit.prov', rounds=655555) | to_uuid }}" + +matrix_mautrix_bluesky_double_puppet_secrets_auto: |- + {{ + ({ + matrix_mautrix_bluesky_homeserver_domain: ("as_token:" + matrix_appservice_double_puppet_registration_as_token) + }) + if matrix_appservice_double_puppet_enabled + else {} + }} + +matrix_mautrix_bluesky_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}" + +matrix_mautrix_bluesky_metrics_proxying_enabled: "{{ matrix_mautrix_bluesky_metrics_enabled and matrix_metrics_exposure_enabled }}" +matrix_mautrix_bluesky_metrics_proxying_hostname: "{{ matrix_metrics_exposure_hostname }}" +matrix_mautrix_bluesky_metrics_proxying_path_prefix: "{{ matrix_metrics_exposure_path_prefix }}/mautrix-bluesky" + +matrix_mautrix_bluesky_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}" +matrix_mautrix_bluesky_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.twt.db', rounds=655555) | to_uuid if postgres_enabled else '' }}" + +###################################################################### +# +# /matrix-bridge-mautrix-bluesky +# +###################################################################### ###################################################################### # @@ -4062,6 +4137,12 @@ postgres_managed_databases_auto: | 'password': matrix_wechat_database_password, }] if (matrix_wechat_enabled and matrix_wechat_database_engine == 'postgres' and matrix_wechat_database_hostname == postgres_connection_hostname) else []) + + ([{ + 'name': matrix_mautrix_bluesky_database_name, + 'username': matrix_mautrix_bluesky_database_username, + 'password': matrix_mautrix_bluesky_database_password, + }] if (matrix_mautrix_bluesky_enabled and matrix_mautrix_bluesky_database_engine == 'postgres' and matrix_mautrix_bluesky_database_hostname == postgres_connection_hostname) else []) + + ([{ 'name': matrix_mautrix_facebook_database_name, 'username': matrix_mautrix_facebook_database_username, @@ -4943,6 +5024,11 @@ matrix_synapse_admin_config_asManagedUsers_auto: | '^@'+(matrix_hookshot_generic_userIdPrefix | default('') | regex_escape)+'[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$', ] if matrix_hookshot_enabled else []) + + ([ + '^@'+(matrix_mautrix_bluesky_appservice_bot_username | default('') | regex_escape)+':'+(matrix_domain | regex_escape)+'$', + '^@bluesky_[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$', + ] if matrix_mautrix_bluesky_enabled else []) + + ([ '^@'+(matrix_mautrix_discord_appservice_bot_username | default('') | regex_escape)+':'+(matrix_domain | regex_escape)+'$', '^@discord_[0-9]+:'+(matrix_domain | regex_escape)+'$', diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml new file mode 100644 index 000000000..1d159496b --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml @@ -0,0 +1,192 @@ +--- +# mautrix-bluesky is a Matrix <-> Bluesky bridge +# Project source code URL: https://github.com/mautrix/bluesky + +matrix_mautrix_bluesky_enabled: true + +matrix_mautrix_bluesky_container_image_self_build: false +matrix_mautrix_bluesky_container_image_self_build_repo: "https://github.com/mautrix/bluesky.git" +matrix_mautrix_bluesky_container_image_self_build_repo_version: "{{ 'master' if matrix_mautrix_bluesky_version == 'latest' else matrix_mautrix_bluesky_version }}" + +# renovate: datasource=docker depName=dock.mau.dev/mautrix/bluesky +matrix_mautrix_bluesky_version: v0.1.0 +# See: https://mau.dev/tulir/mautrix-bluesky/container_registry +matrix_mautrix_bluesky_docker_image: "{{ matrix_mautrix_bluesky_docker_image_name_prefix }}mautrix/bluesky:{{ matrix_mautrix_bluesky_version }}" +matrix_mautrix_bluesky_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_bluesky_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_bluesky_docker_image_force_pull: "{{ matrix_mautrix_bluesky_docker_image.endswith(':latest') }}" + +matrix_mautrix_bluesky_base_path: "{{ matrix_base_data_path }}/mautrix-bluesky" +matrix_mautrix_bluesky_config_path: "{{ matrix_mautrix_bluesky_base_path }}/config" +matrix_mautrix_bluesky_data_path: "{{ matrix_mautrix_bluesky_base_path }}/data" +matrix_mautrix_bluesky_docker_src_files_path: "{{ matrix_mautrix_bluesky_base_path }}/docker-src" + +matrix_mautrix_bluesky_homeserver_address: "" +matrix_mautrix_bluesky_homeserver_domain: '{{ matrix_domain }}' +matrix_mautrix_bluesky_appservice_address: 'http://matrix-mautrix-bluesky:29340' + +# A public address that external services can use to reach this appservice. +matrix_mautrix_bluesky_appservice_public_address: '' + +matrix_mautrix_bluesky_bridge_command_prefix: "!bs" + +matrix_mautrix_bluesky_bridge_permissions: | + {{ + {matrix_mautrix_bluesky_homeserver_domain: 'user'} + | combine({matrix_admin: 'admin'} if matrix_admin else {}) + }} + +matrix_mautrix_bluesky_container_network: "" + +matrix_mautrix_bluesky_container_additional_networks: "{{ matrix_mautrix_bluesky_container_additional_networks_auto + matrix_mautrix_bluesky_container_additional_networks_custom }}" +matrix_mautrix_bluesky_container_additional_networks_auto: [] +matrix_mautrix_bluesky_container_additional_networks_custom: [] + +# matrix_mautrix_bluesky_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. +# See `../templates/labels.j2` for details. +# +# To inject your own other container labels, see `matrix_mautrix_bluesky_container_labels_additional_labels`. +matrix_mautrix_bluesky_container_labels_traefik_enabled: true +matrix_mautrix_bluesky_container_labels_traefik_docker_network: "{{ matrix_mautrix_bluesky_container_network }}" +matrix_mautrix_bluesky_container_labels_traefik_entrypoints: web-secure +matrix_mautrix_bluesky_container_labels_traefik_tls_certResolver: default # noqa var-naming + +# Controls whether labels will be added that expose mautrix-instagram's metrics +matrix_mautrix_bluesky_container_labels_metrics_enabled: "{{ matrix_mautrix_bluesky_metrics_enabled and matrix_mautrix_bluesky_metrics_proxying_enabled }}" +matrix_mautrix_bluesky_container_labels_metrics_traefik_rule: "Host(`{{ matrix_mautrix_bluesky_metrics_proxying_hostname }}`) && PathPrefix(`{{ matrix_mautrix_bluesky_metrics_proxying_path_prefix }}`)" +matrix_mautrix_bluesky_container_labels_metrics_traefik_priority: 0 +matrix_mautrix_bluesky_container_labels_metrics_traefik_entrypoints: "{{ matrix_mautrix_bluesky_container_labels_traefik_entrypoints }}" +matrix_mautrix_bluesky_container_labels_metrics_traefik_tls: "{{ matrix_mautrix_bluesky_container_labels_metrics_traefik_entrypoints != 'web' }}" +matrix_mautrix_bluesky_container_labels_metrics_traefik_tls_certResolver: "{{ matrix_mautrix_bluesky_container_labels_traefik_tls_certResolver }}" # noqa var-naming +matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_enabled: false +# See: https://doc.traefik.io/traefik/middlewares/http/basicauth/#users +matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_users: '' + +# matrix_mautrix_bluesky_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. +# See `../templates/labels.j2` for details. +# +# Example: +# matrix_mautrix_bluesky_container_labels_additional_labels: | +# my.label=1 +# another.label="here" +matrix_mautrix_bluesky_container_labels_additional_labels: '' + +# A list of extra arguments to pass to the container +matrix_mautrix_bluesky_container_extra_arguments: [] + +# List of systemd services that matrix-mautrix-bluesky.service depends on. +matrix_mautrix_bluesky_systemd_required_services_list: "{{ matrix_mautrix_bluesky_systemd_required_services_list_default + matrix_mautrix_bluesky_systemd_required_services_list_auto + matrix_mautrix_bluesky_systemd_required_services_list_custom }}" +matrix_mautrix_bluesky_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" +matrix_mautrix_bluesky_systemd_required_services_list_auto: [] +matrix_mautrix_bluesky_systemd_required_services_list_custom: [] + +# List of systemd services that matrix-mautrix-bluesky.service wants +matrix_mautrix_bluesky_systemd_wanted_services_list: [] + +matrix_mautrix_bluesky_appservice_token: '' +matrix_mautrix_bluesky_homeserver_token: '' + +# Whether or not created rooms should have federation enabled. +# If false, created portal rooms will never be federated. +matrix_mautrix_bluesky_matrix_federate_rooms: true + +# Database-related configuration fields. +# +# To use Postgres: +# - adjust your database credentials via the `matrix_mautrix_bluesky_postgres_*` variables +matrix_mautrix_bluesky_database_engine: 'postgres' + +matrix_mautrix_bluesky_database_username: 'matrix_mautrix_bluesky' +matrix_mautrix_bluesky_database_password: 'some-password' +matrix_mautrix_bluesky_database_hostname: '' +matrix_mautrix_bluesky_database_port: 5432 +matrix_mautrix_bluesky_database_name: 'matrix_mautrix_bluesky' +matrix_mautrix_bluesky_database_sslmode: disable + +matrix_mautrix_bluesky_database_connection_string: 'postgres://{{ matrix_mautrix_bluesky_database_username }}:{{ matrix_mautrix_bluesky_database_password }}@{{ matrix_mautrix_bluesky_database_hostname }}:{{ matrix_mautrix_bluesky_database_port }}/{{ matrix_mautrix_bluesky_database_name }}?sslmode={{ matrix_mautrix_bluesky_database_sslmode }}' + +matrix_mautrix_bluesky_database_uri: "{{ + { + 'postgres': matrix_mautrix_bluesky_database_connection_string, + }[matrix_mautrix_bluesky_database_engine] +}}" + +matrix_mautrix_bluesky_double_puppet_secrets: "{{ matrix_mautrix_bluesky_double_puppet_secrets_auto | combine(matrix_mautrix_bluesky_double_puppet_secrets_custom) }}" +matrix_mautrix_bluesky_double_puppet_secrets_auto: {} +matrix_mautrix_bluesky_double_puppet_secrets_custom: {} + +matrix_mautrix_bluesky_appservice_bot_username: blueskybot +matrix_mautrix_bluesky_appservice_bot_displayname: Bluesky bridge bot +matrix_mautrix_bluesky_appservice_bot_avatar: mxc://maunium.net/ezAjjDxhiJWGEohmhkpfeHYf + +matrix_mautrix_bluesky_backfill_enabled: true +# Maximum number of messages to backfill in empty rooms +matrix_mautrix_bluesky_backfill_max_initial_messages: 50 + +# Maximum number of missed messages to backfill after bridge restarts +matrix_mautrix_bluesky_backfill_max_catchup_messages: 500 + +# Shared secret for authentication of provisioning API requests. +# If set to "disable", the provisioning API will be disabled. +matrix_mautrix_bluesky_provisioning_shared_secret: disable + +# Minimum severity of journal log messages. +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_bluesky_logging_level: 'warn' + +# Whether or not metrics endpoint should be enabled. +# Enabling them is usually enough for a local (in-container) Prometheus to consume them. +# If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_mautrix_bluesky_metrics_proxying_enabled`. +matrix_mautrix_bluesky_metrics_enabled: false + +# Controls whether metrics should be exposed on a public URL. +matrix_mautrix_bluesky_metrics_proxying_enabled: false +matrix_mautrix_bluesky_metrics_proxying_hostname: '' +matrix_mautrix_bluesky_metrics_proxying_path_prefix: '' + +# Default configuration template which covers the generic use case. +# You can customize it by controlling the various variables inside it. +# +# For a more advanced customization, you can extend the default (see `matrix_mautrix_bluesky_configuration_extension_yaml`) +# or completely replace this variable with your own template. +matrix_mautrix_bluesky_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}" + +matrix_mautrix_bluesky_configuration_extension_yaml: | + # Your custom YAML configuration goes here. + # This configuration extends the default starting configuration (`matrix_mautrix_bluesky_configuration_yaml`). + # + # You can override individual variables from the default configuration, or introduce new ones. + # + # If you need something more special, you can take full control by + # completely redefining `matrix_mautrix_bluesky_configuration_yaml`. + +matrix_mautrix_bluesky_configuration_extension: "{{ matrix_mautrix_bluesky_configuration_extension_yaml | from_yaml if matrix_mautrix_bluesky_configuration_extension_yaml | from_yaml is mapping else {} }}" + +# Holds the final configuration (a combination of the default and its extension). +# You most likely don't need to touch this variable. Instead, see `matrix_mautrix_bluesky_configuration_yaml`. +matrix_mautrix_bluesky_configuration: "{{ matrix_mautrix_bluesky_configuration_yaml | from_yaml | combine(matrix_mautrix_bluesky_configuration_extension, recursive=True) }}" + +matrix_mautrix_bluesky_registration_yaml: | + id: bluesky + as_token: "{{ matrix_mautrix_bluesky_appservice_token }}" + hs_token: "{{ matrix_mautrix_bluesky_homeserver_token }}" + namespaces: + users: + - exclusive: true + regex: '^@bluesky_.+:{{ matrix_mautrix_bluesky_homeserver_domain | regex_escape }}$' + - exclusive: true + regex: '^@{{ matrix_mautrix_bluesky_appservice_bot_username | regex_escape }}:{{ matrix_mautrix_bluesky_homeserver_domain | regex_escape }}$' + url: {{ matrix_mautrix_bluesky_appservice_address }} + sender_localpart: _bot_{{ matrix_mautrix_bluesky_appservice_bot_username }} + rate_limited: false + de.sorunome.msc2409.push_ephemeral: true + receive_ephemeral: true + +matrix_mautrix_bluesky_registration: "{{ matrix_mautrix_bluesky_registration_yaml | from_yaml }}" + +# Enable End-to-bridge encryption +matrix_mautrix_bluesky_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}" +matrix_mautrix_bluesky_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}" +matrix_mautrix_bluesky_bridge_encryption_require: false +matrix_mautrix_bluesky_bridge_encryption_appservice: false +matrix_mautrix_bluesky_bridge_encryption_key_sharing_allow: "{{ matrix_mautrix_bluesky_bridge_encryption_allow }}" +matrix_mautrix_bluesky_bridge_encryption_pickle_key: mautrix.bridge.e2ee diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml new file mode 100644 index 000000000..dd56963ab --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml @@ -0,0 +1,20 @@ +--- + +- tags: + - setup-all + - setup-mautrix-bluesky + - install-all + - install-mautrix-bluesky + block: + - when: matrix_mautrix_bluesky_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" + + - when: matrix_mautrix_bluesky_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" + +- tags: + - setup-all + - setup-mautrix-bluesky + block: + - when: not matrix_mautrix_bluesky_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml new file mode 100644 index 000000000..17fbaed14 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml @@ -0,0 +1,98 @@ +--- + +- ansible.builtin.set_fact: + matrix_mautrix_bluesky_requires_restart: false + +- name: Ensure Mautrix Bluesky image is pulled + community.docker.docker_image: + name: "{{ matrix_mautrix_bluesky_docker_image }}" + source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" + force_source: "{{ matrix_mautrix_bluesky_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_mautrix_bluesky_docker_image_force_pull }}" + when: matrix_mautrix_bluesky_enabled | bool and not matrix_mautrix_bluesky_container_image_self_build + register: result + retries: "{{ devture_playbook_help_container_retries_count }}" + delay: "{{ devture_playbook_help_container_retries_delay }}" + until: result is not failed + +- name: Ensure Mautrix Bluesky paths exist + ansible.builtin.file: + path: "{{ item.path }}" + state: directory + mode: 0750 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - {path: "{{ matrix_mautrix_bluesky_base_path }}", when: true} + - {path: "{{ matrix_mautrix_bluesky_config_path }}", when: true} + - {path: "{{ matrix_mautrix_bluesky_data_path }}", when: true} + - {path: "{{ matrix_mautrix_bluesky_docker_src_files_path }}", when: "{{ matrix_mautrix_bluesky_container_image_self_build }}"} + when: item.when | bool + +- name: Ensure Mautrix Bluesky repository is present on self-build + ansible.builtin.git: + repo: "{{ matrix_mautrix_bluesky_container_image_self_build_repo }}" + version: "{{ matrix_mautrix_bluesky_container_image_self_build_repo_version }}" + dest: "{{ matrix_mautrix_bluesky_docker_src_files_path }}" + force: "yes" + become: true + become_user: "{{ matrix_user_username }}" + register: matrix_mautrix_bluesky_git_pull_results + when: "matrix_mautrix_bluesky_enabled | bool and matrix_mautrix_bluesky_container_image_self_build" + +- name: Ensure Mautrix Bluesky Docker image is built + community.docker.docker_image: + name: "{{ matrix_mautrix_bluesky_docker_image }}" + source: build + force_source: "{{ matrix_mautrix_bluesky_git_pull_results.changed }}" + build: + dockerfile: Dockerfile + path: "{{ matrix_mautrix_bluesky_docker_src_files_path }}" + pull: true + when: "matrix_mautrix_bluesky_enabled | bool and matrix_mautrix_bluesky_container_image_self_build | bool" + +- name: Ensure mautrix-bluesky config.yaml installed + ansible.builtin.copy: + content: "{{ matrix_mautrix_bluesky_configuration | to_nice_yaml(indent=2, width=999999) }}" + dest: "{{ matrix_mautrix_bluesky_config_path }}/config.yaml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure mautrix-bluesky registration.yaml installed + ansible.builtin.copy: + content: "{{ matrix_mautrix_bluesky_registration | to_nice_yaml(indent=2, width=999999) }}" + dest: "{{ matrix_mautrix_bluesky_config_path }}/registration.yaml" + mode: 0644 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + +- name: Ensure mautrix-bluesky support files installed + ansible.builtin.template: + src: "{{ role_path }}/templates/{{ item }}.j2" + dest: "{{ matrix_mautrix_bluesky_base_path }}/{{ item }}" + mode: 0640 + owner: "{{ matrix_user_username }}" + group: "{{ matrix_user_groupname }}" + with_items: + - labels + +- name: Ensure matrix-mautrix-bluesky container network is created + community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" + name: "{{ matrix_mautrix_bluesky_container_network }}" + driver: bridge + driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" + +- name: Ensure matrix-mautrix-bluesky.service installed + ansible.builtin.template: + src: "{{ role_path }}/templates/systemd/matrix-mautrix-bluesky.service.j2" + dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-bluesky.service" + mode: 0644 + +- name: Ensure matrix-mautrix-bluesky.service restarted, if necessary + ansible.builtin.service: + name: "matrix-mautrix-bluesky.service" + state: restarted + daemon_reload: true + when: "matrix_mautrix_bluesky_requires_restart | bool" diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml new file mode 100644 index 000000000..c3c170699 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml @@ -0,0 +1,19 @@ +--- + +- name: Check existence of matrix-mautrix-bluesky service + ansible.builtin.stat: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-bluesky.service" + register: matrix_mautrix_bluesky_service_stat + +- when: matrix_mautrix_bluesky_service_stat.stat.exists | bool + block: + - name: Ensure matrix-mautrix-bluesky is stopped + ansible.builtin.service: + name: matrix-mautrix-bluesky + state: stopped + daemon_reload: true + + - name: Ensure matrix-mautrix-bluesky.service doesn't exist + ansible.builtin.file: + path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-bluesky.service" + state: absent diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml new file mode 100644 index 000000000..acd3c30cd --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml @@ -0,0 +1,15 @@ +--- + +- name: Fail if required mautrix-bluesky settings not defined + ansible.builtin.fail: + msg: >- + You need to define a required configuration setting (`{{ item.name }}`). + when: "item.when | bool and vars[item.name] == ''" + with_items: + - {'name': 'matrix_mautrix_bluesky_appservice_token', when: true} + - {'name': 'matrix_mautrix_bluesky_homeserver_address', when: true} + - {'name': 'matrix_mautrix_bluesky_homeserver_token', when: true} + - {'name': 'matrix_mautrix_bluesky_database_hostname', when: "{{ matrix_mautrix_bluesky_database_engine == 'postgres' }}"} + - {'name': 'matrix_mautrix_bluesky_container_network', when: true} + - {'name': 'matrix_mautrix_bluesky_metrics_proxying_hostname', when: "{{ matrix_mautrix_bluesky_metrics_proxying_enabled }}"} + - {'name': 'matrix_mautrix_bluesky_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_bluesky_metrics_proxying_enabled }}"} diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2 new file mode 100644 index 000000000..156c68048 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2 @@ -0,0 +1,428 @@ +#jinja2: lstrip_blocks: "True" +# Network-specific config options +network: + # Proxy to use for all Bluesky connections. + proxy: null + # Alternative to proxy: an HTTP endpoint that returns the proxy URL to use for Bluesky connections. + get_proxy_url: null + + # Displayname template for Bluesky users. + # {% raw %} + # {{ .DisplayName }} is replaced with the display name of the Bluesky user. + # {{ .Username }} is replaced with the username of the Bluesky user. + # {% endraw %} + displayname_template: "{% raw %}{{ .DisplayName }}{% endraw %} (Bluesky)" + + # Maximum number of conversations to sync on startup + conversation_sync_limit: 20 + + +# Config options that affect the central bridge module. +bridge: + # The prefix for commands. Only required in non-management rooms. + command_prefix: {{ matrix_mautrix_bluesky_bridge_command_prefix | to_json }} + # Should the bridge create a space for each login containing the rooms that account is in? + personal_filtering_spaces: true + # Whether the bridge should set names and avatars explicitly for DM portals. + # This is only necessary when using clients that don't support MSC4171. + private_chat_portal_meta: true + # Should events be handled asynchronously within portal rooms? + # If true, events may end up being out of order, but slow events won't block other ones. + # This is not yet safe to use. + async_events: false + # Should every user have their own portals rather than sharing them? + # By default, users who are in the same group on the remote network will be + # in the same Matrix room bridged to that group. If this is set to true, + # every user will get their own Matrix room instead. + split_portals: false + # Should the bridge resend `m.bridge` events to all portals on startup? + resend_bridge_info: false + + # Should leaving Matrix rooms be bridged as leaving groups on the remote network? + bridge_matrix_leave: false + # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority. + # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone. + tag_only_on_create: true + # List of tags to allow bridging. If empty, no tags will be bridged. + only_bridge_tags: [m.favourite, m.lowpriority] + # Should room mute status only be synced when creating the portal? + # Like tags, mutes can't currently be synced back to the remote network. + mute_only_on_create: true + + # What should be done to portal rooms when a user logs out or is logged out? + # Permitted values: + # nothing - Do nothing, let the user stay in the portals + # kick - Remove the user from the portal rooms, but don't delete them + # unbridge - Remove all ghosts in the room and disassociate it from the remote chat + # delete - Remove all ghosts and users from the room (i.e. delete it) + cleanup_on_logout: + # Should cleanup on logout be enabled at all? + enabled: false + # Settings for manual logouts (explicitly initiated by the Matrix user) + manual: + # Action for private portals which will never be shared with other Matrix users. + private: nothing + # Action for portals with a relay user configured. + relayed: nothing + # Action for portals which may be shared, but don't currently have any other Matrix users. + shared_no_users: nothing + # Action for portals which have other logged-in Matrix users. + shared_has_users: nothing + # Settings for credentials being invalidated (initiated by the remote network, possibly through user action). + # Keys have the same meanings as in the manual section. + bad_credentials: + private: nothing + relayed: nothing + shared_no_users: nothing + shared_has_users: nothing + + # Settings for relay mode + relay: + # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any + # authenticated user into a relaybot for that chat. + enabled: false + # Should only admins be allowed to set themselves as relay users? + # If true, non-admins can only set users listed in default_relays as relays in a room. + admin_only: true + # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room. + default_relays: [] + # The formats to use when sending messages via the relaybot. + # Available variables: + # .Sender.UserID - The Matrix user ID of the sender. + # .Sender.Displayname - The display name of the sender (if set). + # .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room. + # .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set, + # plus the user ID in parentheses if the displayname is not unique. + # If the displayname is not set, this is just the user ID. + # .Message - The `formatted_body` field of the message. + # .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string. + # .FileName - The name of the file being sent. + message_formats: + m.text: "{% raw %}{{ .Sender.DisambiguatedName }}: {{ .Message }}{% endraw %}" + m.notice: "{% raw %}{{ .Sender.DisambiguatedName }}: {{ .Message }}{% endraw %}" + m.emote: "{% raw %}* {{ .Sender.DisambiguatedName }} {{ .Message }}{% endraw %}" + m.file: "{% raw %}{{ .Sender.DisambiguatedName }} sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}" + m.image: "{% raw %}{{ .Sender.DisambiguatedName }} sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}" + m.audio: "{% raw %}{{ .Sender.DisambiguatedName }} sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}" + m.video: "{% raw %}{{ .Sender.DisambiguatedName }} sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}" + m.location: "{% raw %}{{ .Sender.DisambiguatedName }} sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}" + # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names. + # This has all the Sender variables available under message_formats (but without the .Sender prefix). + # Note that you need to manually remove the displayname from message_formats above. + displayname_format: "{% raw %}{{ .DisambiguatedName }}{% endraw %}" + + # Permissions for using the bridge. + # Permitted values: + # relay - Talk through the relaybot (if enabled), no access otherwise + # commands - Access to use commands in the bridge, but not login. + # user - Access to use the bridge with puppeting. + # admin - Full access, user level with some additional administration tools. + # Permitted keys: + # * - All Matrix users + # domain - All users on that homeserver + # mxid - Specific user + permissions: {{ matrix_mautrix_bluesky_bridge_permissions | to_json }} + +# Config for the bridge's database. +database: + # The database type. "sqlite3-fk-wal" and "postgres" are supported. + type: postgres + # The database URI. + # SQLite: A raw file path is supported, but `file:?_txlock=immediate` is recommended. + # https://github.com/mattn/go-sqlite3#connection-string + # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable + # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql + uri: {{ matrix_mautrix_bluesky_database_uri | to_json }} + # Maximum number of connections. + max_open_conns: 5 + max_idle_conns: 1 + # Maximum connection idle time and lifetime before they're closed. Disabled if null. + # Parsed with https://pkg.go.dev/time#ParseDuration + max_conn_idle_time: null + max_conn_lifetime: null + +# Homeserver details. +homeserver: + # The address that this appservice can use to connect to the homeserver. + # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine, + # but https also works if they run on different machines. + address: {{ matrix_mautrix_bluesky_homeserver_address | to_json }} + # The domain of the homeserver (also known as server_name, used for MXIDs, etc). + domain: {{ matrix_mautrix_bluesky_homeserver_domain | to_json }} + + # What software is the homeserver running? + # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here. + software: standard + # The URL to push real-time bridge status to. + # If set, the bridge will make POST requests to this URL whenever a user's remote network connection state changes. + # The bridge will use the appservice as_token to authorize requests. + status_endpoint: + # Endpoint for reporting per-message status. + # If set, the bridge will make POST requests to this URL when processing a message from Matrix. + # It will make one request when receiving the message (step BRIDGE), one after decrypting if applicable + # (step DECRYPTED) and one after sending to the remote network (step REMOTE). Errors will also be reported. + # The bridge will use the appservice as_token to authorize requests. + message_send_checkpoint_endpoint: + # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246? + async_media: false + + # Should the bridge use a websocket for connecting to the homeserver? + # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy, + # mautrix-asmux (deprecated), and hungryserv (proprietary). + websocket: false + # How often should the websocket be pinged? Pinging will be disabled if this is zero. + ping_interval_seconds: 0 + +# Application service host/registration related details. +# Changing these values requires regeneration of the registration (except when noted otherwise) +appservice: + # The address that the homeserver can use to connect to this appservice. + # Like the homeserver address, a local non-https address is recommended when the bridge is on the same machine. + # If the bridge is elsewhere, you must secure the connection yourself (e.g. with https or wireguard) + # If you want to use https, you need to use a reverse proxy. The bridge does not have TLS support built in. + address: {{ matrix_mautrix_bluesky_appservice_address | to_json }} + # A public address that external services can use to reach this appservice. + # This is only needed for things like public media. A reverse proxy is generally necessary when using this field. + # This value doesn't affect the registration file. + public_address: {{ matrix_mautrix_bluesky_appservice_public_address | to_json }} + + # The hostname and port where this appservice should listen. + # For Docker, you generally have to change the hostname to 0.0.0.0. + hostname: 0.0.0.0 + port: 29340 + + # The unique ID of this appservice. + id: bluesky + # Appservice bot details. + bot: + # Username of the appservice bot. + username: {{ matrix_mautrix_bluesky_appservice_bot_username | to_json }} + # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty + # to leave display name/avatar as-is. + displayname: {{ matrix_mautrix_bluesky_appservice_bot_displayname | to_json }} + avatar: {{ matrix_mautrix_bluesky_appservice_bot_avatar | to_json }} + + # Whether to receive ephemeral events via appservice transactions. + ephemeral_events: true + # Should incoming events be handled asynchronously? + # This may be necessary for large public instances with lots of messages going through. + # However, messages will not be guaranteed to be bridged in the same order they were sent in. + # This value doesn't affect the registration file. + async_transactions: false + # Whether to use MSC4190 instead of appservice login to create the bridge bot device. + # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202. + # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861). + msc4190: false + + # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify. + as_token: {{ matrix_mautrix_bluesky_appservice_token | to_json }} + hs_token: {{ matrix_mautrix_bluesky_homeserver_token | to_json }} + + # Localpart template of MXIDs for remote users. + # {% raw %}{{.}}{% endraw %} is replaced with the internal ID of the user. + username_template: "{% raw %}bluesky_{{.}}{% endraw %}" + +# Config options that affect the Matrix connector of the bridge. +matrix: + # Whether the bridge should send the message status as a custom com.beeper.message_send_status event. + message_status_events: false + # Whether the bridge should send a read receipt after successfully bridging a message. + delivery_receipts: false + # Whether the bridge should send error notices via m.notice events when a message fails to bridge. + message_error_notices: true + # Whether the bridge should update the m.direct account data event when double puppeting is enabled. + sync_direct_chat_list: true + # Whether created rooms should have federation enabled. If false, created portal rooms + # will never be federated. Changing this option requires recreating rooms. + federate_rooms: {{ matrix_mautrix_bluesky_matrix_federate_rooms | to_json }} + # The threshold as bytes after which the bridge should roundtrip uploads via the disk + # rather than keeping the whole file in memory. + upload_file_threshold: 5242880 + +# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors. +analytics: + # API key to send with tracking requests. Tracking is disabled if this is null. + token: null + # Address to send tracking requests to. + url: https://api.segment.io/v1/track + # Optional user ID for tracking events. If null, defaults to using Matrix user ID. + user_id: null + +# Settings for provisioning API +provisioning: + # Prefix for the provisioning API paths. + prefix: /_matrix/provision + # Shared secret for authentication. If set to "generate" or null, a random secret will be generated, + # or if set to "disable", the provisioning API will be disabled. + shared_secret: {{ matrix_mautrix_bluesky_provisioning_shared_secret | to_json }} + # Whether to allow provisioning API requests to be authed using Matrix access tokens. + # This follows the same rules as double puppeting to determine which server to contact to check the token, + # which means that by default, it only works for users on the same server as the bridge. + allow_matrix_auth: true + # Enable debug API at /debug with provisioning authentication. + debug_endpoints: false + +# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks). +# These settings control whether the bridge will provide such public media access. +public_media: + # Should public media be enabled at all? + # The public_address field under the appservice section MUST be set when enabling public media. + enabled: false + # A key for signing public media URLs. + # If set to "generate", a random key will be generated. + signing_key: "" + # Number of seconds that public media URLs are valid for. + # If set to 0, URLs will never expire. + expiry: 0 + # Length of hash to use for public media URLs. Must be between 0 and 32. + hash_length: 32 + +# Settings for converting remote media to custom mxc:// URIs instead of reuploading. +# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html +direct_media: + # Should custom mxc:// URIs be used instead of reuploading media? + enabled: false + # The server name to use for the custom mxc:// URIs. + # This server name will effectively be a real Matrix server, it just won't implement anything other than media. + # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge. + server_name: discord-media.example.com + # Optionally a custom .well-known response. This defaults to `server_name:443` + well_known_response: + # Optionally specify a custom prefix for the media ID part of the MXC URI. + media_id_prefix: + # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916 + # media download redirects if the requester supports it. Optionally, you can force redirects + # and not allow proxying at all by setting this to false. + # This option does nothing if the remote network does not support media downloads over HTTP. + allow_proxy: true + # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file. + # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them. + server_key: "" + +# Settings for backfilling messages. +# Note that the exact way settings are applied depends on the network connector. +# See https://docs.mau.fi/bridges/general/backfill.html for more details. +backfill: + # Whether to do backfilling at all. + enabled: {{ matrix_mautrix_bluesky_backfill_enabled | to_json }} + # Maximum number of messages to backfill in empty rooms. + max_initial_messages: {{ matrix_mautrix_bluesky_backfill_max_initial_messages | to_json }} + # Maximum number of missed messages to backfill after bridge restarts. + max_catchup_messages: {{ matrix_mautrix_bluesky_backfill_max_catchup_messages | to_json }} + # If a backfilled chat is older than this number of hours, + # mark it as read even if it's unread on the remote network. + unread_hours_threshold: 720 + # Settings for backfilling threads within other backfills. + threads: + # Maximum number of messages to backfill in a new thread. + max_initial_messages: 50 + # Settings for the backwards backfill queue. This only applies when connecting to + # Beeper as standard Matrix servers don't support inserting messages into history. + queue: + # Should the backfill queue be enabled? + enabled: false + # Number of messages to backfill in one batch. + batch_size: 100 + # Delay between batches in seconds. + batch_delay: 20 + # Maximum number of batches to backfill per portal. + # If set to -1, all available messages will be backfilled. + max_batches: -1 + # Optional network-specific overrides for max batches. + # Interpretation of this field depends on the network connector. + max_batches_override: {} + +# Settings for enabling double puppeting +double_puppet: + # Servers to always allow double puppeting from. + # This is only for other servers and should NOT contain the server the bridge is on. + servers: {} + # Whether to allow client API URL discovery for other servers. When using this option, + # users on other servers can use double puppeting even if their server URLs aren't + # explicitly added to the servers map above. + allow_discovery: false + # Shared secrets for automatic double puppeting. + # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions. + secrets: {{ matrix_mautrix_bluesky_double_puppet_secrets | to_json }} + +# End-to-bridge encryption support options. +# +# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info. +encryption: + # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms. + allow: {{ matrix_mautrix_bluesky_bridge_encryption_allow | to_json }} + # Whether to force-enable encryption in all bridged rooms. + default: {{ matrix_mautrix_bluesky_bridge_encryption_default | to_json }} + # Whether to require all messages to be encrypted and drop any unencrypted messages. + require: {{ matrix_mautrix_bluesky_bridge_encryption_require | to_json }} + # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data. + # This option is not yet compatible with standard Matrix servers like Synapse and should not be used. + appservice: {{ matrix_mautrix_bluesky_bridge_encryption_appservice | to_json }} + # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. + # You must use a client that supports requesting keys from other users to use this feature. + allow_key_sharing: {{ matrix_mautrix_bluesky_bridge_encryption_key_sharing_allow | to_json }} + # Pickle key for encrypting encryption keys in the bridge database. + # If set to generate, a random key will be generated. + pickle_key: {{ matrix_mautrix_bluesky_bridge_encryption_pickle_key | to_json }} + # Options for deleting megolm sessions from the bridge. + delete_keys: + # Beeper-specific: delete outbound sessions when hungryserv confirms + # that the user has uploaded the key to key backup. + delete_outbound_on_ack: false + # Don't store outbound sessions in the inbound table. + dont_store_outbound: false + # Ratchet megolm sessions forward after decrypting messages. + ratchet_on_decrypt: false + # Delete fully used keys (index >= max_messages) after decrypting messages. + delete_fully_used_on_decrypt: false + # Delete previous megolm sessions from same device when receiving a new one. + delete_prev_on_new_session: false + # Delete megolm sessions received from a device when the device is deleted. + delete_on_device_delete: false + # Periodically delete megolm sessions when 2x max_age has passed since receiving the session. + periodically_delete_expired: false + # Delete inbound megolm sessions that don't have the received_at field used for + # automatic ratcheting and expired session deletion. This is meant as a migration + # to delete old keys prior to the bridge update. + delete_outdated_inbound: false + # What level of device verification should be required from users? + # + # Valid levels: + # unverified - Send keys to all device in the room. + # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys. + # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes). + # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot. + # Note that creating user signatures from the bridge bot is not currently possible. + # verified - Require manual per-device verification + # (currently only possible by modifying the `trust` column in the `crypto_device` database table). + verification_levels: + # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix. + receive: unverified + # Minimum level that the bridge should accept for incoming Matrix messages. + send: unverified + # Minimum level that the bridge should require for accepting key requests. + share: cross-signed-tofu + # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content. + # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event. + rotation: + # Enable custom Megolm room key rotation settings. Note that these + # settings will only apply to rooms created after this option is set. + enable_custom: false + # The maximum number of milliseconds a session should be used + # before changing it. The Matrix spec recommends 604800000 (a week) + # as the default. + milliseconds: 604800000 + # The maximum number of messages that should be sent with a given a + # session before changing it. The Matrix spec recommends 100 as the + # default. + messages: 100 + # Disable rotating keys when a user's devices change? + # You should not enable this option unless you understand all the implications. + disable_device_change_key_rotation: false + +# Logging config. See https://github.com/tulir/zeroconfig for details. +logging: + min_level: {{ matrix_mautrix_bluesky_logging_level | to_json }} + writers: + - type: stdout + format: pretty-colored diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 new file mode 100644 index 000000000..876f48012 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 @@ -0,0 +1,46 @@ +{% if matrix_mautrix_bluesky_container_labels_traefik_enabled %} +traefik.enable=true + +{% if matrix_mautrix_bluesky_container_labels_traefik_docker_network %} +traefik.docker.network={{ matrix_mautrix_bluesky_container_labels_traefik_docker_network }} +{% endif %} + +traefik.http.services.matrix-mautrix-bluesky-metrics.loadbalancer.server.port=8000 + +{% if matrix_mautrix_bluesky_container_labels_metrics_enabled %} +############################################################ +# # +# Metrics # +# # +############################################################ + +{% if matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_enabled %} +traefik.http.middlewares.matrix-mautrix-bluesky-metrics-basic-auth.basicauth.users={{ matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_users }} +traefik.http.routers.matrix-mautrix-bluesky-metrics.middlewares=matrix-mautrix-bluesky-metrics-basic-auth +{% endif %} + +traefik.http.routers.matrix-mautrix-bluesky-metrics.rule={{ matrix_mautrix_bluesky_container_labels_metrics_traefik_rule }} + +{% if matrix_mautrix_bluesky_container_labels_metrics_traefik_priority | int > 0 %} +traefik.http.routers.matrix-mautrix-bluesky-metrics.priority={{ matrix_mautrix_bluesky_container_labels_metrics_traefik_priority }} +{% endif %} + +traefik.http.routers.matrix-mautrix-bluesky-metrics.service=matrix-mautrix-bluesky-metrics +traefik.http.routers.matrix-mautrix-bluesky-metrics.entrypoints={{ matrix_mautrix_bluesky_container_labels_metrics_traefik_entrypoints }} + +traefik.http.routers.matrix-mautrix-bluesky-metrics.tls={{ matrix_mautrix_bluesky_container_labels_metrics_traefik_tls | to_json }} +{% if matrix_mautrix_bluesky_container_labels_metrics_traefik_tls %} +traefik.http.routers.matrix-mautrix-bluesky-metrics.tls.certResolver={{ matrix_mautrix_bluesky_container_labels_metrics_traefik_tls_certResolver }} +{% endif %} + +############################################################ +# # +# /Metrics # +# # +############################################################ +{% endif %} + + +{% endif %} + +{{ matrix_mautrix_bluesky_container_labels_additional_labels }} diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 new file mode 100644 index 000000000..b26d402b3 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 @@ -0,0 +1,48 @@ +#jinja2: lstrip_blocks: "True" +[Unit] +Description=Matrix Mautrix Bluesky bridge +{% for service in matrix_mautrix_bluesky_systemd_required_services_list %} +Requires={{ service }} +After={{ service }} +{% endfor %} +{% for service in matrix_mautrix_bluesky_systemd_wanted_services_list %} +Wants={{ service }} +{% endfor %} +DefaultDependencies=no + +[Service] +Type=simple +Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-bluesky 2>/dev/null || true' + +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ + --rm \ + --name=matrix-mautrix-bluesky \ + --log-driver=none \ + --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ + --cap-drop=ALL \ + --network={{ matrix_mautrix_bluesky_container_network }} \ + --mount type=bind,src={{ matrix_mautrix_bluesky_config_path }},dst=/config,ro \ + --mount type=bind,src={{ matrix_mautrix_bluesky_data_path }},dst=/data \ + --label-file={{ matrix_mautrix_bluesky_base_path }}/labels \ + {% for arg in matrix_mautrix_bluesky_container_extra_arguments %} + {{ arg }} \ + {% endfor %} + {{ matrix_mautrix_bluesky_docker_image }} \ + /usr/bin/mautrix-bluesky -c /config/config.yaml -r /config/registration.yaml --no-update + +{% for network in matrix_mautrix_bluesky_container_additional_networks %} +ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-mautrix-bluesky +{% endfor %} + +ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-bluesky + +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-bluesky 2>/dev/null || true' +Restart=always +RestartSec=30 +SyslogIdentifier=matrix-mautrix-bluesky + +[Install] +WantedBy=multi-user.target diff --git a/setup.yml b/setup.yml index d65222648..d36f16c6b 100644 --- a/setup.yml +++ b/setup.yml @@ -75,6 +75,7 @@ - custom/matrix-bridge-mautrix-wsproxy - custom/matrix-bridge-mautrix-discord - custom/matrix-bridge-mautrix-slack + - custom/matrix-bridge-mautrix-bluesky - custom/matrix-bridge-mx-puppet-discord - custom/matrix-bridge-mx-puppet-groupme - custom/matrix-bridge-mx-puppet-steam From 104f1b7838f5b70584c6f9b0fa3490aafddf6fb9 Mon Sep 17 00:00:00 2001 From: Zepmann Date: Wed, 19 Feb 2025 19:08:26 +0100 Subject: [PATCH 638/952] Add documentation for mautrix-bluesky. --- README.md | 1 + ...iguring-playbook-bridge-mautrix-bluesky.md | 68 +++++++++++++++++++ 2 files changed, 69 insertions(+) create mode 100644 docs/configuring-playbook-bridge-mautrix-bluesky.md diff --git a/README.md b/README.md index 9806e2caf..f91e24b3b 100644 --- a/README.md +++ b/README.md @@ -117,6 +117,7 @@ Bridges can be used to connect your Matrix installation with third-party communi | [mautrix-gmessages](https://github.com/mautrix/gmessages) | ❌ | Bridge to [Google Messages](https://messages.google.com/) | [Link](docs/configuring-playbook-bridge-mautrix-gmessages.md) | | [mautrix-whatsapp](https://github.com/mautrix/whatsapp) | ❌ | Bridge to [WhatsApp](https://www.whatsapp.com/) | [Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md) | | [mautrix-wsproxy](https://github.com/mautrix/wsproxy) | ❌ | Bridge to Android SMS or Apple iMessage | [Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md) | +| [mautrix-bluesky](https://github.com/mautrix/bluesky) | ❌ | Bridge to [Bluesky](https://bsky.social/) | [Link](docs/configuring-playbook-bridge-mautrix-bluesky.md) | | [mautrix-twitter](https://github.com/mautrix/twitter) | ❌ | Bridge to [Twitter](https://twitter.com/) | [Link](docs/configuring-playbook-bridge-mautrix-twitter.md) | | [mautrix-googlechat](https://github.com/mautrix/googlechat) | ❌ | Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat) | [Link](docs/configuring-playbook-bridge-mautrix-googlechat.md) | | [mautrix-meta](https://github.com/mautrix/instagram) | ❌ | Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) | Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md) | diff --git a/docs/configuring-playbook-bridge-mautrix-bluesky.md b/docs/configuring-playbook-bridge-mautrix-bluesky.md new file mode 100644 index 000000000..6ac9e4417 --- /dev/null +++ b/docs/configuring-playbook-bridge-mautrix-bluesky.md @@ -0,0 +1,68 @@ +# Setting up Mautrix Bluesky bridging (optional) + +Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) + +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). + +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. + +## Prerequisite (optional) + +### Enable Appservice Double Puppet + +If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook. + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting. + +## Adjusting the playbook configuration + +To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: + +```yaml +matrix_mautrix_bluesky_enabled: true +``` + +### Extending the configuration + +There are some additional things you may wish to configure about the bridge. + + +See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc. + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +``` + +**Notes**: + +- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. + +- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + + `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. + +## Usage + +To use the bridge, you need to start a chat with `@blueskybot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). + +You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/bluesky/authentication.html). + +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. + +## Troubleshooting + +As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-bluesky`. + +### Increase logging verbosity + +The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: + +```yaml +# Valid values: fatal, error, warn, info, debug, trace +matrix_mautrix_bluesky_logging_level: 'debug' +``` From fd78acd67b7aede1c56db39ebb2d499662f2153e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 09:21:33 +0200 Subject: [PATCH 639/952] Remove inaccurate mention of `ensure-matrix-users-created` in mautrix-bluesky documentation mautrix bridges run in appservice mode and create their own user automatically. There's no need for `ensure-matrix-users-created`. This patch only fixes the mautrix-blusky bridge's documentation. --- docs/configuring-playbook-bridge-mautrix-bluesky.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-bluesky.md b/docs/configuring-playbook-bridge-mautrix-bluesky.md index 6ac9e4417..632f6509a 100644 --- a/docs/configuring-playbook-bridge-mautrix-bluesky.md +++ b/docs/configuring-playbook-bridge-mautrix-bluesky.md @@ -35,13 +35,11 @@ After configuring the playbook, run it with [playbook tags](playbook-tags.md) as ```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start ``` **Notes**: -- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account. - - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. From dae0f446034ae594f4ca77fe3c0861ded24ad3f9 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 10:11:19 +0200 Subject: [PATCH 640/952] Announce mautrix-bluesky support Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/4082 --- CHANGELOG.md | 9 +++++++++ docs/configuring-playbook.md | 2 ++ 2 files changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index c27faf943..cd3cd5735 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,12 @@ +# 2025-02-21 + +## Support for bridging to Bluesky via mautrix-bluesky + +Thanks to [Zepmann](https://github.com/Zepmann), the playbook now supports bridging to [Bluesky](https://bsky.app/) via [mautrix-bluesky](https://github.com/mautrix/bluesky). + +To learn more, see our [Setting up mautrix-bluesky](./docs/configuring-playbook-bridge-mautrix-bluesky.md) documentation page. + + # 2025-02-19 ## The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index e43376006..5edc22326 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -116,6 +116,8 @@ Bridges can be used to connect your Matrix installation with third-party communi - [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges +- [Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md) + - [Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md) - [Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md) From 74177d9ba3fe9feeeb546af3cc766291918dba0c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 16:37:41 +0200 Subject: [PATCH 641/952] Document the state of the `ip6tables` and `experimental` daemon options for Docker --- group_vars/matrix_servers | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 94e0f3fc9..832fe5df7 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -22,6 +22,14 @@ matrix_playbook_docker_installation_enabled: true matrix_playbook_docker_installation_daemon_options: "{{ matrix_playbook_docker_installation_daemon_options_auto | combine(matrix_playbook_docker_installation_daemon_options_custom, recursive=True) }}" matrix_playbook_docker_installation_daemon_options_auto: + # Since Docker 27.0.1: + # - `experimental` is no longer required to enable `ip6tables` + # - `ip6tables` defaults to enabled + # + # See: https://docs.docker.com/engine/release-notes/27/#ipv6 + # + # Still, we intend to keep these around a while longer to benefit people who are still on older versions. + # In the future, we won't be specifying any of these options by default. experimental: "{{ devture_systemd_docker_base_ipv6_enabled }}" ip6tables: "{{ devture_systemd_docker_base_ipv6_enabled }}" From 0de1b76da763acaf7535a6088c79ba43c0d4eea5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 21 Feb 2025 18:34:39 +0200 Subject: [PATCH 642/952] Upgrade systemd_docker_base (v1.3.0-0 -> v1.4.0-0) and make use of the new `devture_systemd_docker_base_ipv6_daemon_options_changing_enabled` variable --- CHANGELOG.md | 32 ++++++++++++++++++++++++++++++++ group_vars/matrix_servers | 23 ++++++++++++----------- requirements.yml | 2 +- 3 files changed, 45 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index cd3cd5735..d02bbc69c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,37 @@ # 2025-02-21 +## Docker daemon options are no longer adjusted when IPv6 is enabled + +We landed [initial IPv6 support](#initial-work-on-ipv6-support) in the past via a `devture_systemd_docker_base_ipv6_enabled` variable that one had to toggle to `true`. + +This variable did **2 different things at once**: + +- ensured that container networks were created with IPv6 being enabled +- adjusted the Docker daemon's configuration to set `experimental: true` and `ip6tables: true` (a necessary prerequisite for creating IPv6-enabled networks) + +Since Docker 27.0.1's [changes to how it handles IPv6](https://docs.docker.com/engine/release-notes/27/#ipv6), **adjusting the Docker daemon's configuration is no longer necessary**, because: +- `ip6tables` defaults to `true` for everyone +- `ip6tables` is out of the experimental phase, so `experimental` is no longer necessary + +In light of this, we're introducing a new variable (`devture_systemd_docker_base_ipv6_daemon_options_changing_enabled`) for controlling if IPv6 should be force-enabled in the Docker daemon's configuration options. +Since most people should be on a modern enough Docker daemon version which doesn't require such changes, this variable defaults to `false`. + +This change affects you like this: + +- ✅ if you're **not explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration): you're unaffected +- ❓ if you're **explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration): + - ✅ .. and you're on a modern enough Docker version (which you most likely are): the playbook will no longer mess with your Docker daemon options. You're unaffected. + - 🔧 .. and you're on an old Docker version, you **are affected** and need to use the following configuration to restore the old behavior: + + ```yml + # Force-enable IPv6 by changing the Docker daemon's options. + # This is necessary for Docker < 27.0.1, but not for newer versions. + devture_systemd_docker_base_ipv6_daemon_options_changing_enabled: true + + # Request that individual container networks are created with IPv6 enabled. + devture_systemd_docker_base_ipv6_enabled: true + ``` + ## Support for bridging to Bluesky via mautrix-bluesky Thanks to [Zepmann](https://github.com/Zepmann), the playbook now supports bridging to [Bluesky](https://bsky.app/) via [mautrix-bluesky](https://github.com/mautrix/bluesky). diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 832fe5df7..89b5253b3 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -21,17 +21,18 @@ matrix_playbook_docker_installation_enabled: true matrix_playbook_docker_installation_daemon_options: "{{ matrix_playbook_docker_installation_daemon_options_auto | combine(matrix_playbook_docker_installation_daemon_options_custom, recursive=True) }}" -matrix_playbook_docker_installation_daemon_options_auto: - # Since Docker 27.0.1: - # - `experimental` is no longer required to enable `ip6tables` - # - `ip6tables` defaults to enabled - # - # See: https://docs.docker.com/engine/release-notes/27/#ipv6 - # - # Still, we intend to keep these around a while longer to benefit people who are still on older versions. - # In the future, we won't be specifying any of these options by default. - experimental: "{{ devture_systemd_docker_base_ipv6_enabled }}" - ip6tables: "{{ devture_systemd_docker_base_ipv6_enabled }}" +# Since Docker 27.0.1, Docker daemon options do not need to be changed to enable IPv6 support on the daemon side. +# See: https://docs.docker.com/engine/release-notes/27/#ipv6 +# We only enable `ip6tables` and `experimental` for people who explicitly request it (perhaps due to running an old Docker version). +# +# Despite IPv6-enablement at the Docker level being a thing, for IPv6 to work for containers +# networks need to be created with IPv6 explicitly enabled. +# This is controlled by the `devture_systemd_docker_base_ipv6_enabled` variable and it's up to the various roles to +# respect this variable when creating their networks. +matrix_playbook_docker_installation_daemon_options_auto: | + {{ + ({'experimental': true, 'ip6tables': true} if devture_systemd_docker_base_ipv6_daemon_options_changing_enabled else {}) + }} matrix_playbook_docker_installation_daemon_options_custom: {} diff --git a/requirements.yml b/requirements.yml index fd7818cc4..202757e8f 100644 --- a/requirements.yml +++ b/requirements.yml @@ -55,7 +55,7 @@ version: v0.14.0-6 name: prometheus_postgres_exporter - src: git+https://github.com/devture/com.devture.ansible.role.systemd_docker_base.git - version: v1.3.0-0 + version: v1.4.0-0 name: systemd_docker_base - src: git+https://github.com/devture/com.devture.ansible.role.systemd_service_manager.git version: v1.0.0-4 From 00bd973c3b7b46fc7b52ed88db0a8c7259b5207e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 22 Feb 2025 02:21:06 +0900 Subject: [PATCH 643/952] Update docs/playbook-tags.md: copy the recommendation for using the just command from mash-playbook This is based on https://github.com/mother-of-all-self-hosting/mash-playbook/commit/581e6ca080247dc4343b2eb9458a4e5400498a88. Signed-off-by: Suguru Hirahara --- docs/playbook-tags.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/playbook-tags.md b/docs/playbook-tags.md index cd5cdcb39..42d2354d6 100644 --- a/docs/playbook-tags.md +++ b/docs/playbook-tags.md @@ -1,5 +1,5 @@ # Running this playbook From edc2cab925d8831707f8e6a8c75e749175573d93 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 22 Feb 2025 13:26:33 +0900 Subject: [PATCH 654/952] Update docs/ansible.md: copy from the MASH project It was copied from https://github.com/mother-of-all-self-hosting/mash-playbook/blob/2bc4cc45d7cc5896772a092428fa501728132063/docs/ansible.md Signed-off-by: Suguru Hirahara --- docs/ansible.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ansible.md b/docs/ansible.md index 0665ed627..7458def5b 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -58,7 +58,7 @@ Once you have a working Docker installation on the server, **clone the playbook* You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the "remote" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH. -Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …` +Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `just install-all --connection=community.docker.nsenter` (or `ansible-playbook --connection=community.docker.nsenter …`). Run this from the playbook's directory: @@ -76,7 +76,7 @@ Once you execute the above command, you'll be dropped into a `/work` directory i First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues). -Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now. +Finally, you can execute `just` or `ansible-playbook …` (e.g. `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now. ### Running Ansible in a container on another computer (not the Matrix server) @@ -97,7 +97,7 @@ Once you execute the above command, you'll be dropped into a `/work` directory i First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues). -Finally, you execute `ansible-playbook …` commands as per normal now. +Finally, you execute `just` or `ansible-playbook …` commands as per normal now. #### If you don't use SSH keys for authentication From 5f0b74bac2966126a68c033fbb5bebf8fcb516da Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 22 Feb 2025 13:26:42 +0900 Subject: [PATCH 655/952] Update docs/ansible.md: remove a whitespace character Signed-off-by: Suguru Hirahara --- docs/ansible.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ansible.md b/docs/ansible.md index 7458def5b..83814cc92 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -109,7 +109,7 @@ To authenticate at your server using a password, you need to add a package. So, apk add sshpass ``` -Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command. +Then, to be asked for the password whenever running an `ansible-playbook` command add `--ask-pass` to the arguments of the command. #### Resolve directory ownership issues From 30997ee2ff73a819dc5c8a4efa6ee68dadfc33c5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 09:55:03 +0200 Subject: [PATCH 656/952] Upgrade container-socket-proxy (v0.3.0-0 -> v0.3.0-1) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 2922e701c..01122204e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -7,7 +7,7 @@ version: v1.4.0-1.9.10-2 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git - version: v0.3.0-0 + version: v0.3.0-1 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker version: 7.4.5 From 804b9007eca18dcf1389ac7638a9b896bbb06ba2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 10:01:00 +0200 Subject: [PATCH 657/952] Upgrade Traefik (v3.3.3-0 -> v3.3.3-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 01122204e..24de53511 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.3-0 + version: v3.3.3-2 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-5 From b21a0b367dedf2c42a29cf2f30a4e6d70dd4e81a Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 10:08:37 +0200 Subject: [PATCH 658/952] Upgrade container-socket-proxy (v0.3.0-1 -> v0.3.0-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 24de53511..b5025259f 100644 --- a/requirements.yml +++ b/requirements.yml @@ -7,7 +7,7 @@ version: v1.4.0-1.9.10-2 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git - version: v0.3.0-1 + version: v0.3.0-2 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker version: 7.4.5 From 87a05ef94b3405b0718557b78e006bd03e05aabb Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 10:23:48 +0200 Subject: [PATCH 659/952] Upgrade Etherpad (v2.2.7-1 -> v2.2.7-2) and switch to newly introduced variables --- group_vars/matrix_servers | 10 ++++------ requirements.yml | 2 +- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 84980b679..7f4cac7bc 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3532,7 +3532,7 @@ matrix_dimension_database_password: "{{ '%s' | format(matrix_homeserver_generic_ ###################################################################### # -# etke/etherpad +# etherpad # ###################################################################### @@ -3554,7 +3554,7 @@ etherpad_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_i etherpad_container_network: "{{ matrix_addons_container_network }}" -etherpad_container_additional_networks: | +etherpad_container_additional_networks_auto: | {{ ( ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) @@ -3568,10 +3568,8 @@ etherpad_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_pr etherpad_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" etherpad_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}" -etherpad_systemd_required_services_list: | +etherpad_systemd_required_services_list_auto: | {{ - [devture_systemd_docker_base_docker_service_name] - + ([postgres_identifier ~ '.service'] if postgres_enabled else []) }} @@ -3582,7 +3580,7 @@ etherpad_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_k ###################################################################### # -# /etke/etherpad +# /etherpad # ###################################################################### diff --git a/requirements.yml b/requirements.yml index b5025259f..1d2558788 100644 --- a/requirements.yml +++ b/requirements.yml @@ -16,7 +16,7 @@ version: 129c8590e106b83e6f4c259649a613c6279e937a name: docker_sdk_for_python - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git - version: v2.2.7-1 + version: v2.2.7-2 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git version: v4.98-r0-4-1 From b6db2eaf15464d24c7b89f2d1cbd507936cb8482 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 10:31:14 +0200 Subject: [PATCH 660/952] Upgrade Grafana (v11.5.1-0 -> v11.5.2-0) --- group_vars/matrix_servers | 4 ++-- requirements.yml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 7f4cac7bc..c896bcd72 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -5401,7 +5401,7 @@ matrix_prometheus_services_connect_scraper_synapse_usage_exporter_static_configs ###################################################################### # -# etke/grafana +# grafana # ###################################################################### @@ -5482,7 +5482,7 @@ grafana_default_home_dashboard_path: |- ###################################################################### # -# /etke/grafana +# /grafana # ###################################################################### diff --git a/requirements.yml b/requirements.yml index 1d2558788..d5ba6c962 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98-r0-4-1 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.5.1-0 + version: v11.5.2-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v10008-1 From 5b3f9510b0fa637c98ddec2ec9c0a21445fbcef6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 22 Feb 2025 18:26:29 +0900 Subject: [PATCH 661/952] Update docs/just.md: remove a duplicate anchor link Signed-off-by: Suguru Hirahara --- docs/just.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/just.md b/docs/just.md index b02385f11..c12743b74 100644 --- a/docs/just.md +++ b/docs/just.md @@ -13,7 +13,7 @@ In addition, we have added support for running commands via [`just`](https://git The `just` utility executes shortcut commands (called as "recipes"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets. -For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process. +For some recipes such as `just update`, our `justfile` recommends installing `agru` (a faster alternative to `ansible-galaxy`) to speed up the process. Here are some examples of shortcuts: From 64a402eb657c5104780575a54a243515799144d8 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 13:42:23 +0200 Subject: [PATCH 662/952] Do not duplicate `turn_uris` construction for each homeserver implementation (extract to `matrix_coturn_turn_uris`) --- group_vars/matrix_servers | 57 ++---------------------- roles/custom/matrix-coturn/vars/main.yml | 14 ++++++ 2 files changed, 18 insertions(+), 53 deletions(-) create mode 100644 roles/custom/matrix-coturn/vars/main.yml diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index c896bcd72..884a52726 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -4746,19 +4746,7 @@ matrix_synapse_email_smtp_port: 8025 matrix_synapse_email_smtp_require_transport_security: false matrix_synapse_email_notif_from: "Matrix <{{ exim_relay_sender_address }}>" -matrix_synapse_turn_uris: | - {{ - ([ - 'turns:' + matrix_server_fqn_matrix + '?transport=udp', - 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled and matrix_coturn_tls_enabled else []) - + - ([ - 'turn:' + matrix_server_fqn_matrix + '?transport=udp', - 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled else []) - }} - +matrix_synapse_turn_uris: "{{ matrix_coturn_turn_uris if matrix_coturn_enabled else [] }}" matrix_synapse_turn_shared_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" matrix_synapse_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" matrix_synapse_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" @@ -5673,20 +5661,7 @@ matrix_dendrite_database_hostname: "{{ postgres_connection_hostname if postgres_ matrix_dendrite_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'dendrite.db', rounds=655555) | to_uuid }}" -# Even if TURN doesn't support TLS (it does by default), -# it doesn't hurt to try a secure connection anyway. -matrix_dendrite_client_api_turn_uris: | - {{ - [ - 'turns:' + matrix_server_fqn_matrix + '?transport=udp', - 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', - 'turn:' + matrix_server_fqn_matrix + '?transport=udp', - 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', - ] - if matrix_coturn_enabled - else [] - }} - +matrix_dendrite_client_api_turn_uris: "{{ matrix_coturn_turn_uris if matrix_coturn_enabled else [] }}" matrix_dendrite_client_api_turn_shared_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" matrix_dendrite_client_api_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" matrix_dendrite_client_api_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" @@ -5755,19 +5730,7 @@ matrix_conduit_container_labels_public_federation_api_traefik_tls: "{{ matrix_fe matrix_conduit_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}" matrix_conduit_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}" -matrix_conduit_turn_uris: | - {{ - ([ - 'turns:' + matrix_server_fqn_matrix + '?transport=udp', - 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled and matrix_coturn_tls_enabled else []) - + - ([ - 'turn:' + matrix_server_fqn_matrix + '?transport=udp', - 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled else []) - }} - +matrix_conduit_turn_uris: "{{ matrix_coturn_turn_uris if matrix_coturn_enabled else [] }}" matrix_conduit_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" matrix_conduit_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" matrix_conduit_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" @@ -5815,19 +5778,7 @@ matrix_conduwuit_container_labels_public_federation_api_traefik_tls: "{{ matrix_ matrix_conduwuit_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}" matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}" -matrix_conduwuit_config_turn_uris: | - {{ - ([ - 'turns:' + matrix_server_fqn_matrix + '?transport=udp', - 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled and matrix_coturn_tls_enabled else []) - + - ([ - 'turn:' + matrix_server_fqn_matrix + '?transport=udp', - 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', - ] if matrix_coturn_enabled else []) - }} - +matrix_conduwuit_config_turn_uris: "{{ matrix_coturn_turn_uris if matrix_coturn_enabled else [] }}" matrix_conduwuit_config_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}" matrix_conduwuit_config_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" matrix_conduwuit_config_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}" diff --git a/roles/custom/matrix-coturn/vars/main.yml b/roles/custom/matrix-coturn/vars/main.yml new file mode 100644 index 000000000..96e9f60a2 --- /dev/null +++ b/roles/custom/matrix-coturn/vars/main.yml @@ -0,0 +1,14 @@ +--- + +matrix_coturn_turn_uris: |- + {{ + ([ + 'turns:' + matrix_server_fqn_matrix + '?transport=udp', + 'turns:' + matrix_server_fqn_matrix + '?transport=tcp', + ] if matrix_coturn_tls_enabled else []) + + + ([ + 'turn:' + matrix_server_fqn_matrix + '?transport=udp', + 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', + ]) + }} From 671a3dc94f117cb478025a9908cd17ddca47203c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 13:44:14 +0200 Subject: [PATCH 663/952] Only advertise 3478/udp (STUN/TURN) if Coturn actually enables it Related to ac26cc1cb0d6423b751b74ddb06a8c793f63dd56 which disabled `3478/udp` by default. Without this patch, homeservers continued to advertise the `3478/udp` port, even though it was no longer exposed. While clients should handle that gracefully (by falling back to TCP, etc.), it seems like Element either doesn't do that or it doesn't support TCP (which this patch won't fix). In any case, it's better to only announce what is actually supported/exposed. --- roles/custom/matrix-coturn/vars/main.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-coturn/vars/main.yml b/roles/custom/matrix-coturn/vars/main.yml index 96e9f60a2..0c0a1c24f 100644 --- a/roles/custom/matrix-coturn/vars/main.yml +++ b/roles/custom/matrix-coturn/vars/main.yml @@ -9,6 +9,9 @@ matrix_coturn_turn_uris: |- + ([ 'turn:' + matrix_server_fqn_matrix + '?transport=udp', + ] if (matrix_coturn_container_stun_plain_host_bind_port_udp != '' or matrix_coturn_container_network == 'host') else []) + + + ([ 'turn:' + matrix_server_fqn_matrix + '?transport=tcp', - ]) + ] if (matrix_coturn_container_stun_plain_host_bind_port_tcp != '' or matrix_coturn_container_network == 'host') else []) }} From 0750e709720671b93e78dee848475795b7a5c041 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:00:18 +0200 Subject: [PATCH 664/952] Upgrade traefik-certs-dumper (v2.8.3-5 -> v2.8.3-6) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index d5ba6c962..8e8975acb 100644 --- a/requirements.yml +++ b/requirements.yml @@ -67,7 +67,7 @@ version: v3.3.3-2 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git - version: v2.8.3-5 + version: v2.8.3-6 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git version: v8.0.1-1 From ee75543aa722927aaf759602873d350ec79fd47b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:04:23 +0200 Subject: [PATCH 665/952] Upgrade Prometheus (v2.55.1-0 -> v2.55.1-1) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 8e8975acb..32ab9af27 100644 --- a/requirements.yml +++ b/requirements.yml @@ -46,7 +46,7 @@ version: v17-1 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git - version: v2.55.1-0 + version: v2.55.1-1 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git version: v1.8.2-2 From 053ef3f35a081b1afe2c38b919caa4748366b7f3 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:07:59 +0200 Subject: [PATCH 666/952] Upgrade prometheus-postgres-exporter (v0.14.0-6 -> v0.14.0-7) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 32ab9af27..f895a0035 100644 --- a/requirements.yml +++ b/requirements.yml @@ -52,7 +52,7 @@ version: v1.8.2-2 name: prometheus_node_exporter - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter.git - version: v0.14.0-6 + version: v0.14.0-7 name: prometheus_postgres_exporter - src: git+https://github.com/devture/com.devture.ansible.role.systemd_docker_base.git version: v1.4.0-0 From b41cb172fe93596b0af8ddec3887c2ff89731816 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:17:17 +0200 Subject: [PATCH 667/952] Upgrade ntfy (v2.11.0-1 -> v2.11.0-2) --- group_vars/matrix_servers | 6 +++--- requirements.yml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 884a52726..7908a071f 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -4375,7 +4375,7 @@ matrix_sygnal_container_labels_traefik_tls_certResolver: "{{ traefik_certResolve ###################################################################### # -# etke/ntfy +# ntfy # ###################################################################### @@ -4390,7 +4390,7 @@ ntfy_gid: "{{ matrix_user_gid }}" ntfy_hostname: "{{ matrix_server_fqn_ntfy }}" -ntfy_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" +ntfy_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" ntfy_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '2586') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4406,7 +4406,7 @@ ntfy_visitor_request_limit_exempt_hosts_hostnames_auto: | ###################################################################### # -# /etky/ntfy +# /ntfy # ###################################################################### diff --git a/requirements.yml b/requirements.yml index f895a0035..9cfffb96e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -28,7 +28,7 @@ version: v10008-1 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git - version: v2.11.0-1 + version: v2.11.0-2 name: ntfy - src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git version: 201c939eed363de269a83ba29784fc3244846048 From f7c89e3abefdf73357e54f35d08016e843d63fe2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:19:22 +0200 Subject: [PATCH 668/952] Upgrade postgres-backup (v17-1 -> v17-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 9cfffb96e..5668b2ee8 100644 --- a/requirements.yml +++ b/requirements.yml @@ -43,7 +43,7 @@ version: v17.2-2 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git - version: v17-1 + version: v17-2 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git version: v2.55.1-1 From 49c60deb8a834a68feb35eea545342686a459f13 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:35:09 +0200 Subject: [PATCH 669/952] Upgrade prometheus-node-exporter (v1.8.2-2 -> v1.8.2-3) --- group_vars/matrix_servers | 2 +- requirements.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 7908a071f..ee5212f6e 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -5173,7 +5173,7 @@ prometheus_node_exporter_hostname: "{{ matrix_server_fqn_matrix }}" prometheus_node_exporter_container_network: "{{ matrix_monitoring_container_network }}" -prometheus_node_exporter_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" +prometheus_node_exporter_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" prometheus_node_exporter_container_labels_traefik_enabled: "{{ matrix_metrics_exposure_enabled }}" prometheus_node_exporter_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" diff --git a/requirements.yml b/requirements.yml index 5668b2ee8..aa0f5a9b0 100644 --- a/requirements.yml +++ b/requirements.yml @@ -49,7 +49,7 @@ version: v2.55.1-1 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git - version: v1.8.2-2 + version: v1.8.2-3 name: prometheus_node_exporter - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter.git version: v0.14.0-7 From 44baf74b9bed77a019a24e0554750dbb609dbc05 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:36:32 +0200 Subject: [PATCH 670/952] Make all remaining roles respect `devture_systemd_docker_base_ipv6_enabled` and `devture_systemd_docker_base_container_networks_driver_options` --- roles/custom/matrix-bot-baibot/tasks/install.yml | 1 + roles/custom/matrix-bridge-wechat/tasks/install.yml | 1 + roles/custom/matrix-pantalaimon/tasks/install.yml | 1 + 3 files changed, 3 insertions(+) diff --git a/roles/custom/matrix-bot-baibot/tasks/install.yml b/roles/custom/matrix-bot-baibot/tasks/install.yml index f74ab3442..340efdd69 100644 --- a/roles/custom/matrix-bot-baibot/tasks/install.yml +++ b/roles/custom/matrix-bot-baibot/tasks/install.yml @@ -70,6 +70,7 @@ enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" name: "{{ matrix_bot_baibot_container_network }}" driver: bridge + driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" - name: Ensure matrix-bot-baibot.service installed ansible.builtin.template: diff --git a/roles/custom/matrix-bridge-wechat/tasks/install.yml b/roles/custom/matrix-bridge-wechat/tasks/install.yml index 36d530c75..d9a74db20 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/install.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/install.yml @@ -111,6 +111,7 @@ - name: Ensure matrix-wechat container network is created community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" name: "{{ matrix_wechat_container_network }}" driver: bridge driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" diff --git a/roles/custom/matrix-pantalaimon/tasks/install.yml b/roles/custom/matrix-pantalaimon/tasks/install.yml index 9a9b9a38c..88417681a 100644 --- a/roles/custom/matrix-pantalaimon/tasks/install.yml +++ b/roles/custom/matrix-pantalaimon/tasks/install.yml @@ -57,6 +57,7 @@ - name: Ensure pantalaimon container network is created community.general.docker_network: + enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" name: "{{ matrix_pantalaimon_container_network }}" driver: bridge driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" From d12643eb91a8568dee2ab8510cdc373c2f63bdf7 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:42:18 +0200 Subject: [PATCH 671/952] Do not use `docker stop --time` (deprecated in Docker v28 in favor of `--timeout` or just `-t`) `-t` works on both old and new Docker versions, so it's best to use that. --- .../systemd/matrix-alertmanager-receiver.service.j2 | 4 ++-- .../systemd/matrix-appservice-draupnir-for-all.service.j2 | 4 ++-- .../systemd/matrix-authentication-service.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-baibot.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-buscarron.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-chatgpt.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-draupnir.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-go-neb.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-honoroit.service.j2 | 4 ++-- .../systemd/matrix-bot-matrix-registration-bot.service.j2 | 4 ++-- .../systemd/matrix-bot-matrix-reminder-bot.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-maubot.service.j2 | 4 ++-- .../templates/systemd/matrix-bot-mjolnir.service.j2 | 6 +++--- .../templates/systemd/matrix-appservice-discord.service.j2 | 4 ++-- .../templates/systemd/matrix-appservice-irc.service.j2 | 4 ++-- .../systemd/matrix-appservice-kakaotalk-node.service.j2 | 4 ++-- .../systemd/matrix-appservice-kakaotalk.service.j2 | 4 ++-- .../templates/systemd/matrix-appservice-slack.service.j2 | 4 ++-- .../templates/systemd/matrix-appservice-webhooks.service.j2 | 4 ++-- .../templates/systemd/matrix-beeper-linkedin.service.j2 | 4 ++-- .../templates/systemd/matrix-go-skype-bridge.service.j2 | 4 ++-- .../templates/systemd/matrix-heisenbridge.service.j2 | 4 ++-- .../templates/systemd/matrix-hookshot.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-bluesky.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-discord.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-facebook.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-gmessages.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-googlechat.service.j2 | 2 +- .../templates/systemd/matrix-mautrix-instagram.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-meta.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-meta.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-signal.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-slack.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-telegram.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-twitter.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-whatsapp.service.j2 | 4 ++-- .../systemd/matrix-mautrix-wsproxy-syncproxy.service.j2 | 4 ++-- .../templates/systemd/matrix-mautrix-wsproxy.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-discord.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-groupme.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-instagram.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-slack.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-steam.service.j2 | 4 ++-- .../templates/systemd/matrix-mx-puppet-twitter.service.j2 | 4 ++-- .../templates/systemd/matrix-postmoogle.service.j2 | 4 ++-- .../templates/systemd/matrix-sms-bridge.service.j2 | 4 ++-- .../templates/systemd/matrix-wechat-agent.service.j2 | 4 ++-- .../templates/systemd/matrix-wechat.service.j2 | 4 ++-- .../systemd/matrix-cactus-comments-client.service.j2 | 4 ++-- .../templates/systemd/matrix-cactus-comments.service.j2 | 4 ++-- .../templates/systemd/matrix-client-cinny.service.j2 | 4 ++-- .../templates/systemd/matrix-client-element.service.j2 | 4 ++-- .../templates/systemd/matrix-client-fluffychat.service.j2 | 4 ++-- .../templates/systemd/matrix-client-hydrogen.service.j2 | 4 ++-- .../templates/systemd/matrix-client-schildichat.service.j2 | 4 ++-- .../templates/systemd/matrix-conduit.service.j2 | 4 ++-- .../templates/systemd/matrix-conduwuit.service.j2 | 4 ++-- .../templates/systemd/matrix-corporal.service.j2 | 4 ++-- .../templates/systemd/matrix-coturn.service.j2 | 4 ++-- .../templates/systemd/matrix-dendrite.service.j2 | 4 ++-- .../templates/systemd/matrix-dimension.service.j2 | 4 ++-- .../templates/systemd/matrix-dynamic-dns.service.j2 | 4 ++-- .../templates/systemd/matrix-email2matrix.service.j2 | 4 ++-- .../systemd/matrix-ldap-registration-proxy.service.j2 | 4 ++-- .../matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2 | 4 ++-- .../media-repo/systemd/matrix-media-repo.service.j2 | 4 ++-- .../systemd/matrix-prometheus-nginxlog-exporter.service.j2 | 4 ++-- .../templates/systemd/matrix-rageshake.service.j2 | 4 ++-- .../templates/systemd/matrix-registration.service.j2 | 4 ++-- .../templates/systemd/matrix-sliding-sync.service.j2 | 4 ++-- .../templates/systemd/matrix-static-files.service.j2 | 4 ++-- .../templates/systemd/matrix-sygnal.service.j2 | 4 ++-- .../templates/systemd/matrix-synapse-admin.service.j2 | 4 ++-- .../templates/matrix-synapse-auto-compressor.service.j2 | 4 ++-- .../matrix-synapse-reverse-proxy-companion.service.j2 | 4 ++-- .../systemd/matrix-synapse-usage-exporter.service.j2 | 4 ++-- .../templates/goofys/systemd/matrix-goofys.service.j2 | 4 ++-- .../synapse/systemd/matrix-synapse-worker.service.j2 | 4 ++-- .../templates/synapse/systemd/matrix-synapse.service.j2 | 4 ++-- .../systemd/matrix-user-verification-service.service.j2 | 4 ++-- 80 files changed, 160 insertions(+), 160 deletions(-) diff --git a/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2 b/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2 index 4d7e43c54..2f0b6622d 100644 --- a/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2 +++ b/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-alertmanager-receiver 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-alertmanager-receiver 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-alertmanager-receiver 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-alertmanager-receiver -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-alertmanager-receiver 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-alertmanager-receiver 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-alertmanager-receiver 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2 b/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2 index 303e9e614..008d0feb1 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2 +++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-draupnir-for-all 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-draupnir-for-all 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-draupnir-for-all 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-draupnir-for-all -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-draupnir-for-all 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-draupnir-for-all 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-draupnir-for-all 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2 b/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2 index c8b487138..1f03c6b4f 100644 --- a/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2 +++ b/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-authentication-service 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-authentication-service 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-authentication-service 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-authentication-service -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-authentication-service 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-authentication-service 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-authentication-service 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 index 346925c4a..01b6c0a06 100644 --- a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-baibot 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-baibot 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-baibot 2>/dev/null || true' {# @@ -43,7 +43,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-baibot -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-baibot 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-baibot 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-baibot 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2 b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2 index aa4314a13..c5ed0f3e0 100644 --- a/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2 +++ b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-buscarron 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-buscarron 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-buscarron 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-buscarron -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-buscarron 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-buscarron 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-buscarron 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2 b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2 index 01b0763a4..a3a3ba219 100644 --- a/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2 +++ b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ matrix_bot_chatgpt_container_stop_grace_time_seconds }} matrix-bot-chatgpt 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ matrix_bot_chatgpt_container_stop_grace_time_seconds }} matrix-bot-chatgpt 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-chatgpt 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-chatgpt -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ matrix_bot_chatgpt_container_stop_grace_time_seconds }} matrix-bot-chatgpt 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ matrix_bot_chatgpt_container_stop_grace_time_seconds }} matrix-bot-chatgpt 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-chatgpt 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2 b/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2 index d83f088f2..1c9c72de1 100644 --- a/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2 +++ b/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-draupnir 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-draupnir 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-draupnir 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -42,7 +42,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-draupnir -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-draupnir 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-draupnir 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-draupnir 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2 b/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2 index 876c13829..c8c028b77 100644 --- a/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2 +++ b/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-go-neb 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-go-neb 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-go-neb 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -44,7 +44,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-go-neb -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-go-neb 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-go-neb 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-go-neb 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2 b/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2 index 2749ec520..3bcd8441b 100644 --- a/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2 +++ b/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-honoroit 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-honoroit 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-honoroit 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-honoroit -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-honoroit 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-honoroit 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-honoroit 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 index d12d2f588..1ad089e3d 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 +++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-registration-bot 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-registration-bot 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-matrix-registration-bot 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -35,7 +35,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-matrix-registration-bot -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-registration-bot 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-registration-bot 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-matrix-registration-bot 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2 b/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2 index ecd59bd7b..823d050c2 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2 +++ b/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-reminder-bot 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-reminder-bot 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-matrix-reminder-bot 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-matrix-reminder-bot -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-reminder-bot 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-matrix-reminder-bot 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-matrix-reminder-bot 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 index 25ba29a46..6c6174677 100644 --- a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 +++ b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-maubot 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-maubot 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-maubot 2>/dev/null || true' {# @@ -47,7 +47,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-maubot -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-maubot 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-maubot 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-maubot 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2 b/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2 index b87601891..9c1f46733 100644 --- a/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2 +++ b/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-mjolnir 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-mjolnir 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-mjolnir 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -30,7 +30,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ {{ arg }} \ {% endfor %} {{ matrix_bot_mjolnir_docker_image }} \ - bot --mjolnir-config /data/config/production.yaml + bot --mjolnir-config /data/config/production.yaml {% for network in matrix_bot_mjolnir_container_additional_networks %} ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-bot-mjolnir @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-mjolnir -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-mjolnir 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-mjolnir 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-mjolnir 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2 b/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2 index 3a5c9f060..e4a943bc2 100644 --- a/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2 +++ b/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-discord 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-discord 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-discord 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-discord -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-discord 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-discord 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-discord 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2 b/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2 index c13acfe09..0b50d10e2 100644 --- a/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2 +++ b/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-irc 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-irc 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-irc 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-irc -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-irc 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-irc 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-irc 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2 b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2 index bb971f77a..12f688112 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2 +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk-node 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk-node 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-kakaotalk-node 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -36,7 +36,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-kakaotalk-node -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk-node 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk-node 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-kakaotalk-node 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2 b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2 index fae5f25a1..0f5e2fe2d 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2 +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-kakaotalk 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -37,7 +37,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-kakaotalk -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-kakaotalk 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-kakaotalk 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2 b/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2 index 6445f06af..36d9377ea 100644 --- a/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2 +++ b/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-slack 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-slack 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-slack 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-slack -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-slack 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-slack 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-slack 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2 b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2 index b1168cb7f..e761442cc 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2 +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-webhooks 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-webhooks 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-webhooks 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-appservice-webhooks -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-webhooks 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-appservice-webhooks 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-appservice-webhooks 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 index 1b1cc582b..d3fe0d249 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 +++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-beeper-linkedin 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-beeper-linkedin 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-beeper-linkedin 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -37,7 +37,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-beeper-linkedin -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-beeper-linkedin 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-beeper-linkedin 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-beeper-linkedin 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2 b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2 index 825d4eb34..fcd05f49e 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2 +++ b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-go-skype-bridge 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-go-skype-bridge 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-go-skype-bridge 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-go-skype-bridge -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-go-skype-bridge 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-go-skype-bridge 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-go-skype-bridge 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2 b/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2 index e0981b2a7..556eb28c9 100644 --- a/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2 +++ b/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ matrix_heisenbridge_container_stop_grace_time_seconds }} matrix-heisenbridge +ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ matrix_heisenbridge_container_stop_grace_time_seconds }} matrix-heisenbridge ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} rm matrix-heisenbridge ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -50,7 +50,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-heisenbridge -ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ matrix_heisenbridge_container_stop_grace_time_seconds }} matrix-heisenbridge +ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ matrix_heisenbridge_container_stop_grace_time_seconds }} matrix-heisenbridge ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} rm matrix-heisenbridge Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2 b/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2 index aca952f1e..3ad5df541 100644 --- a/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2 +++ b/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_hookshot_identifier }} +ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_hookshot_identifier }} ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_hookshot_identifier }} ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create --rm --name {{ matrix_hookshot_identifier }} \ --log-driver=none \ @@ -36,7 +36,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_hookshot_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_hookshot_identifier }} +ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_hookshot_identifier }} ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_hookshot_identifier }} Restart=always diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 index b26d402b3..5dd291dd2 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-bluesky 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-bluesky -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-bluesky 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-bluesky 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 index cd853e1a9..9344d7866 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-discord 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-discord 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-discord 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-discord -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-discord 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-discord 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-discord 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2 b/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2 index 3fbb4ad24..754c48885 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-facebook 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-facebook 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-facebook 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-facebook -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-facebook 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-facebook 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-facebook 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2 b/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2 index f90597730..af3c1731f 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-gmessages 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-gmessages 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-gmessages 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-gmessages -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-gmessages 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-gmessages 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-gmessages 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2 b/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2 index 50cd131a4..00025295c 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2 @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-googlechat -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-googlechat 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-googlechat 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-googlechat 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2 b/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2 index e8e6e0f51..35248d9d1 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-instagram 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-instagram 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-instagram 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-instagram -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-instagram 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-instagram 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-instagram 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2 b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2 index a772b3eca..e72e911f2 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_mautrix_meta_instagram_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_mautrix_meta_instagram_identifier }} 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2 b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2 index 0ca0263b1..92439132e 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_mautrix_meta_messenger_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_mautrix_meta_messenger_identifier }} 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2 b/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2 index 431dfd736..f108dce1c 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-signal 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-signal 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-signal 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-signal -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-signal 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-signal 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-signal 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2 b/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2 index e81bd4cef..563ff2552 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-slack 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-slack 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-slack 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-slack -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-slack 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-slack 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-slack 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2 b/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2 index 9b611affe..ce59de6af 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-telegram 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-telegram 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-telegram 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-telegram -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-telegram 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-telegram 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-telegram 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2 b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2 index ef16a675d..c044cc616 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-twitter 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-twitter 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-twitter 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-twitter -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-twitter 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-twitter 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-twitter 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2 b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2 index f7b4a9ee5..fe77ca34d 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-whatsapp 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-whatsapp 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-whatsapp 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-whatsapp -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-whatsapp 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-whatsapp 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-whatsapp 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2 b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2 index 9e1137a97..c46d7b6f9 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy-syncproxy 2>/dev/null' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy-syncproxy 2>/dev/null' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-wsproxy-syncproxy 2>/dev/null' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -35,7 +35,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-wsproxy-syncproxy -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy-syncproxy 2>/dev/null' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy-syncproxy 2>/dev/null' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-wsproxy-syncproxy 2>/dev/null' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2 b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2 index 206342676..ab71702ea 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2 +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy 2>/dev/null' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy 2>/dev/null' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-wsproxy 2>/dev/null' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create --rm --name matrix-mautrix-wsproxy \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mautrix-wsproxy -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy 2>/dev/null' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mautrix-wsproxy 2>/dev/null' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mautrix-wsproxy 2>/dev/null' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2 b/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2 index 55efcfba4..6d75a9332 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-discord 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-discord 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-discord 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-discord -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-discord 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-discord 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-discord 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2 b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2 index eb9fd2574..9f4483c6a 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-groupme 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-groupme 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-groupme 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-groupme -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-groupme 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-groupme 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-groupme 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2 b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2 index a3b9d1739..0efca1941 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-instagram 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-instagram 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-instagram 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-instagram -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-instagram 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-instagram 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-instagram 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2 b/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2 index a87672dd4..0727c4ec1 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-slack 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-slack 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-slack 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -42,7 +42,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-slack -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-slack 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-slack 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-slack 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2 b/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2 index cdb1efaa6..dd235a4e3 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-steam 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-steam 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-steam 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-steam -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-steam 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-steam 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-steam 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2 b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2 index 6d2ff145b..1e4771d9a 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-twitter 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-twitter 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-twitter 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-mx-puppet-twitter -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-twitter 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-mx-puppet-twitter 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-mx-puppet-twitter 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2 b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2 index fa4c1bf36..5d730184e 100644 --- a/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2 +++ b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-postmoogle 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -44,7 +44,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-postmoogle -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-postmoogle 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2 b/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2 index 5f12e4922..49af8b715 100644 --- a/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2 +++ b/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sms-bridge 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sms-bridge 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sms-bridge 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-sms-bridge -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sms-bridge 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sms-bridge 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sms-bridge 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2 b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2 index 8e5ea5239..dc8d348da 100644 --- a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2 +++ b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat-agent 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat-agent 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-wechat-agent 2>/dev/null || true' {# @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-wechat-agent -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat-agent 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat-agent 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-wechat-agent 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2 b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2 index 96f87e9bb..193042a66 100644 --- a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2 +++ b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-wechat 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -37,7 +37,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-wechat -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-wechat 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-wechat 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2 b/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2 index 10fd74d94..6e49e6fad 100755 --- a/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2 +++ b/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments-client 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments-client 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-cactus-comments-client 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-cactus-comments-client -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments-client 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments-client 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-cactus-comments-client 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2 b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2 index 9c862e178..64220e310 100644 --- a/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2 +++ b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-cactus-comments 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -34,7 +34,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-cactus-comments -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-cactus-comments 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-cactus-comments 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2 b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2 index c5b5ab3ac..6aac5e9c3 100644 --- a/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2 +++ b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-cinny 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-cinny 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-cinny 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-cinny -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-cinny 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-cinny 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-cinny 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 index 9748cfe7c..834e5cb87 100644 --- a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 +++ b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-element 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-element 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-element 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -47,7 +47,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-element -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-element 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-element 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-element 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 index 5747637e5..ad10c6297 100644 --- a/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 +++ b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-fluffychat 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -37,7 +37,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-fluffychat -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-fluffychat 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-fluffychat 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2 b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2 index 28867dd5a..5f6dbe30d 100644 --- a/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2 +++ b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-hydrogen 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-hydrogen 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-hydrogen 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-hydrogen -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-hydrogen 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-hydrogen 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-hydrogen 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2 b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2 index 98941d47e..ab223e166 100644 --- a/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2 +++ b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-schildichat 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-schildichat 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-schildichat 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -46,7 +46,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-client-schildichat -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-schildichat 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-schildichat 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-schildichat 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2 b/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2 index 4084f6a11..1ae8b7e97 100644 --- a/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2 +++ b/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2 @@ -9,7 +9,7 @@ After={{ service }} [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduit 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduit 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduit 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach m ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_conduit_systemd_service_post_start_delay_seconds }} {% endif %} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduit 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduit 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduit 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-conduit /bin/sh -c 'kill -HUP 1' Restart=always diff --git a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 index 5291e33a8..2c05c7872 100644 --- a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 +++ b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 @@ -9,7 +9,7 @@ After={{ service }} [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach m ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_conduwuit_systemd_service_post_start_delay_seconds }} {% endif %} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-conduwuit /bin/sh -c 'kill -HUP 1' Restart=always diff --git a/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2 b/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2 index 41900d130..473d9450b 100644 --- a/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2 +++ b/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-corporal 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-corporal 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-corporal 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -43,7 +43,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-corporal -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-corporal 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-corporal 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-corporal 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 index 6d3ffe310..5aec071f6 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-coturn 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-coturn 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-coturn 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -55,7 +55,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-coturn -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-coturn 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-coturn 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-coturn 2>/dev/null || true' # This only reloads certificates (not other configuration). diff --git a/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2 b/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2 index 7dff4e0f9..ca09cb292 100644 --- a/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2 +++ b/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dendrite 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dendrite 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dendrite 2>/dev/null || true' {% if (postgres_identifier + '.service') in matrix_dendrite_systemd_required_services_list %} @@ -67,7 +67,7 @@ ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach m ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_dendrite_systemd_service_post_start_delay_seconds }} {% endif %} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dendrite 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dendrite 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dendrite 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-dendrite /bin/sh -c 'kill -HUP 1' Restart=always diff --git a/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2 b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2 index 7898a7ba3..33a800838 100644 --- a/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2 +++ b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dimension 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dimension 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dimension 2>/dev/null || true' # Fixup database ownership if it got changed somehow (during a server migration, etc.) @@ -47,7 +47,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-dimension -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dimension 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dimension 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dimension 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 index e5507a337..97c0b5989 100644 --- a/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 +++ b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dynamic-dns 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dynamic-dns 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dynamic-dns 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -36,7 +36,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-dynamic-dns -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dynamic-dns 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-dynamic-dns 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-dynamic-dns 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 index 10d4de04d..4b84d13dd 100644 --- a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 +++ b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-email2matrix 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -34,7 +34,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-email2matrix -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-email2matrix 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2 b/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2 index 5d3ef7f47..5668d0a86 100644 --- a/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2 +++ b/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ldap-registration-proxy 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ldap-registration-proxy 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-ldap-registration-proxy 2>/dev/null || true' # matrix_ldap_registration_proxy writes an SQLite shared library (libsqlitejdbc.so) to /tmp and executes it from there, @@ -42,7 +42,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-ldap-registration-proxy -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ldap-registration-proxy 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ldap-registration-proxy 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-ldap-registration-proxy 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2 b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2 index 36e6a353b..7f9ec27f4 100644 --- a/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2 +++ b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ma1sd 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ma1sd 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-ma1sd 2>/dev/null || true' # ma1sd writes an SQLite shared library (libsqlitejdbc.so) to /tmp and executes it from there, @@ -47,7 +47,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-ma1sd -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ma1sd 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-ma1sd 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-ma1sd 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2 b/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2 index ea2fb125f..cb8e6a547 100755 --- a/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2 +++ b/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_media_repo_identifier }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_media_repo_identifier }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_media_repo_identifier }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -46,7 +46,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_media_repo_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_media_repo_identifier }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_media_repo_identifier }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_media_repo_identifier }} 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec {{ matrix_media_repo_identifier }} /bin/sh -c 'kill -HUP 1' Restart=always diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2 b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2 index 63ea4f1ef..027ab8ddc 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2 +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -44,7 +44,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_prometheus_nginxlog_exporter_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_prometheus_nginxlog_exporter_identifier }} 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 index ba98d0e3a..fc90ea1e0 100644 --- a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 +++ b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-rageshake 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-rageshake 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-rageshake 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -40,7 +40,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-rageshake -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-rageshake 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-rageshake 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-rageshake 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2 b/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2 index 0544676c1..1888a2448 100644 --- a/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2 +++ b/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-registration 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-registration 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-registration 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-registration -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-registration 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-registration 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-registration 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2 b/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2 index d3a22e1d4..20ca0edf3 100644 --- a/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2 +++ b/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sliding-sync 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sliding-sync 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sliding-sync 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -38,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-sliding-sync -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sliding-sync 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sliding-sync 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sliding-sync 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2 b/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2 index b1bc2dd1b..ef828c22d 100755 --- a/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2 +++ b/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-static-files 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-static-files 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-static-files 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-static-files -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-static-files 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-static-files 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-static-files 2>/dev/null || true' Restart=always RestartSec=30 diff --git a/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2 b/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2 index 12140146a..96e6ea72e 100644 --- a/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2 +++ b/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sygnal 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sygnal 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sygnal 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -41,7 +41,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-sygnal -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sygnal 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-sygnal 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-sygnal 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2 b/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2 index ed72bef7c..dd3675fae 100644 --- a/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2 +++ b/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-admin 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-admin 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-admin 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -42,7 +42,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-synapse-admin -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-admin 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-admin 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-admin 2>/dev/null || true' Restart=always diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2 b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2 index 842f33670..486579f8a 100644 --- a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2 +++ b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=oneshot Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-auto-compressor 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-auto-compressor 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-auto-compressor 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} {{ matrix_synapse_auto_compressor_base_path }}/matrix-synapse-auto-compressor-fix.sh @@ -39,7 +39,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-synapse-auto-compressor -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-auto-compressor 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-auto-compressor 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-auto-compressor 2>/dev/null || true' SyslogIdentifier=matrix-synapse-auto-compressor diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2 index 3e1732369..0a2434061 100755 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-reverse-proxy-companion 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-reverse-proxy-companion 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-reverse-proxy-companion 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -48,7 +48,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-synapse-reverse-proxy-companion -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-reverse-proxy-companion 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse-reverse-proxy-companion 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse-reverse-proxy-companion 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-synapse-reverse-proxy-companion /usr/sbin/nginx -s reload Restart=always diff --git a/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2 b/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2 index da09078c3..1b560dc9a 100644 --- a/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2 +++ b/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -36,7 +36,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_synapse_usage_exporter_identifier }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_synapse_usage_exporter_identifier }} 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec {{ matrix_synapse_usage_exporter_identifier }} /bin/sh -c 'kill -HUP 1' Restart=always diff --git a/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2 b/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2 index 0f7a83620..8459cd723 100644 --- a/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2 +++ b/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2 @@ -10,7 +10,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} %n +ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} %n ExecStartPre=-{{ devture_systemd_docker_base_host_command_docker }} rm %n ExecStart={{ devture_systemd_docker_base_host_command_docker }} run --rm --name %n \ @@ -33,7 +33,7 @@ ExecStartPost={{ matrix_host_command_sleep }} 3 TimeoutStartSec=5min ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop %n -ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} %n +ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} %n ExecStop=-{{ devture_systemd_docker_base_host_command_docker }} rm %n ExecStop=-{{ matrix_host_command_fusermount }} -u {{ matrix_s3_media_store_path }} Restart=always diff --git a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2 b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2 index 21b747b0e..bdd5b5742 100644 --- a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2 @@ -37,7 +37,7 @@ Requires=matrix-synapse.service Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -83,7 +83,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach {{ matrix_synapse_worker_container_name }} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_synapse_worker_container_name }} 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec {{ matrix_synapse_worker_container_name }} /bin/sh -c 'kill -HUP 1' diff --git a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2 b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2 index a22c09b1e..9fa7a1dfb 100644 --- a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2 @@ -21,7 +21,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse 2>/dev/null || true' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse 2>/dev/null || true' ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ @@ -73,7 +73,7 @@ ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach m ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_synapse_systemd_service_post_start_delay_seconds }} {% endif %} -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse 2>/dev/null || true' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-synapse 2>/dev/null || true' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-synapse 2>/dev/null || true' ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-synapse /bin/sh -c 'kill -HUP 1' diff --git a/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2 b/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2 index 19956496b..16df27a1c 100644 --- a/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2 +++ b/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2 @@ -13,7 +13,7 @@ DefaultDependencies=no [Service] Type=simple Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_user_verification_service_container_name }} 2>/dev/null' +ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_user_verification_service_container_name }} 2>/dev/null' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_user_verification_service_container_name }} 2>/dev/null' @@ -40,7 +40,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network conne {% endfor %} ExecStart=/usr/bin/env docker start --attach matrix-user-verification-service -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_user_verification_service_container_name }} 2>/dev/null' +ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} {{ matrix_user_verification_service_container_name }} 2>/dev/null' ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm {{ matrix_user_verification_service_container_name }} 2>/dev/null' Restart=always RestartSec=30 From a518fcce818ef940117edb0a6932576b944be8d5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:47:58 +0200 Subject: [PATCH 672/952] Upgrade Prometheus (v2.55.1-1 -> v2.55.1-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index aa0f5a9b0..66b8ff8f2 100644 --- a/requirements.yml +++ b/requirements.yml @@ -46,7 +46,7 @@ version: v17-2 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git - version: v2.55.1-1 + version: v2.55.1-2 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git version: v1.8.2-3 From ecefbc8b44d50b51119ec5f014f892bd1b68abc1 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:54:25 +0200 Subject: [PATCH 673/952] Upgrade backup-borg (v1.4.0-1.9.10-2 -> v1.4.0-1.9.10-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 66b8ff8f2..87cc2e082 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-2 + version: v1.4.0-1.9.10-3 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git version: v0.3.0-2 From 5aa149fb5295b8ec54e11b2dc9a6feb48fed7af8 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 21:56:49 +0200 Subject: [PATCH 674/952] Upgrade Traefik (v3.3.3-2 -> v3.3.3-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 87cc2e082..47e64339e 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.3-2 + version: v3.3.3-3 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-6 From 41fc044ee0a768d8c82e81c7dee6790ac36b191b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 22:03:02 +0200 Subject: [PATCH 675/952] Upgrade Jitsi (v10008-1 -> v10008-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 47e64339e..7579119cd 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.5.2-0 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v10008-1 + version: v10008-2 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git version: v2.11.0-2 From 6d501b9cc6962c0656a3013681d4a0bcf09d5929 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 22:03:54 +0200 Subject: [PATCH 676/952] Upgrade container-socket-proxy (v0.3.0-2 -> v0.3.0-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 7579119cd..650ff3fb3 100644 --- a/requirements.yml +++ b/requirements.yml @@ -7,7 +7,7 @@ version: v1.4.0-1.9.10-3 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git - version: v0.3.0-2 + version: v0.3.0-3 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker version: 7.4.5 From c28630355a73f5e2ef8136901b615a4e4ea57ed4 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 22:31:11 +0200 Subject: [PATCH 677/952] Upgrade exim-relay (v4.98-r0-4-1 -> v4.98-r0-4-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 650ff3fb3..ac3c99c84 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-2 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98-r0-4-1 + version: v4.98-r0-4-2 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-0 From 9a035eeabe58a7c6ef0291b522fbc9db8c139260 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 22:40:28 +0200 Subject: [PATCH 678/952] Upgrade Etherpad (v2.2.7-2 -> v2.2.7-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index ac3c99c84..5ba67b06c 100644 --- a/requirements.yml +++ b/requirements.yml @@ -16,7 +16,7 @@ version: 129c8590e106b83e6f4c259649a613c6279e937a name: docker_sdk_for_python - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git - version: v2.2.7-2 + version: v2.2.7-3 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git version: v4.98-r0-4-2 From 56e9967f5db3efd18f946ca98df0d49c1e902692 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 22 Feb 2025 22:41:52 +0200 Subject: [PATCH 679/952] Upgrade Valkey (v8.0.1-1 -> v8.0.1-2) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 5ba67b06c..675569d11 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,5 +70,5 @@ version: v2.8.3-6 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git - version: v8.0.1-1 + version: v8.0.1-2 name: valkey From 807da7433461dc207bb706740a1edd6296369ce6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 13:33:30 +0900 Subject: [PATCH 680/952] Add license information to files for MX bridges As the future for the MX bridges in this playbook and by themselves seems uncertain, this commit adds license information in SPDX format to the files for those bridges, before the bridges would be deprecated and possibly get removed from the project. Please note that .license files are added for the files which would be broken if such information are added as header, following the REUSE's specification. Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bridge-mx-puppet-discord.md | 9 +++++++++ ...nfiguring-playbook-bridge-mx-puppet-groupme.md | 9 +++++++++ ...iguring-playbook-bridge-mx-puppet-instagram.md | 7 +++++++ ...configuring-playbook-bridge-mx-puppet-skype.md | 8 ++++++++ ...configuring-playbook-bridge-mx-puppet-slack.md | 11 +++++++++++ ...configuring-playbook-bridge-mx-puppet-steam.md | 9 +++++++++ ...nfiguring-playbook-bridge-mx-puppet-twitter.md | 8 ++++++++ .../defaults/main.yml | 12 ++++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 6 ++++++ .../matrix-mx-puppet-discord.service.j2.license | 5 +++++ .../defaults/main.yml | 11 +++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 10 ++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../matrix-mx-puppet-groupme.service.j2.license | 4 ++++ .../defaults/main.yml | 10 ++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../matrix-mx-puppet-instagram.service.j2.license | 5 +++++ .../defaults/main.yml | 15 +++++++++++++++ .../matrix-bridge-mx-puppet-slack/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 6 ++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 8 ++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mx-puppet-slack.service.j2.license | 6 ++++++ .../defaults/main.yml | 11 +++++++++++ .../matrix-bridge-mx-puppet-steam/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 12 ++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 6 ++++++ .../matrix-mx-puppet-steam.service.j2.license | 5 +++++ .../defaults/main.yml | 11 +++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mx-puppet-twitter.service.j2.license | 5 +++++ 51 files changed, 371 insertions(+) create mode 100644 roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2.license diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index cbc61c068..b866dd5f6 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -1,3 +1,12 @@ + + # Setting up MX Puppet Discord bridging (optional) **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook. diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md index 6a7f8bb97..cf3653870 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md +++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md @@ -1,3 +1,12 @@ + + # Setting up MX Puppet GroupMe bridging (optional) The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you. diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md index 53375a029..507b61f8f 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md +++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md @@ -1,3 +1,10 @@ + + # Setting up MX Puppet Instagram bridging (optional) The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you. diff --git a/docs/configuring-playbook-bridge-mx-puppet-skype.md b/docs/configuring-playbook-bridge-mx-puppet-skype.md index 6bbfb7aa5..d45a98569 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-skype.md +++ b/docs/configuring-playbook-bridge-mx-puppet-skype.md @@ -1,3 +1,11 @@ + + # Setting up MX Puppet Skype bridging (optional, removed) 🪦 The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time. diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md index b8e8971b6..468705122 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-slack.md +++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md @@ -1,3 +1,14 @@ + + # Setting up MX Puppet Slack bridging (optional) **Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note 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. diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md index 18ea7ad22..5be67884b 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-steam.md +++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md @@ -1,3 +1,12 @@ + + # Setting up MX Puppet Steam bridging (optional) The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you. diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md index be0df2305..2311b6dfd 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md +++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md @@ -1,3 +1,11 @@ + + # Setting up MX Puppet Twitter bridging (optional) **Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook. diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml index faf1a770c..d4284d0d5 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Daniel Sonck +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Mx Puppet Discord is a Matrix <-> Discord bridge # Project source code URL: https://gitlab.com/mx-puppet/discord/mx-puppet-discord diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml index c0300b513..273640969 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml index 5922c59c3..268cf0364 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure MX Puppet Discord paths exist diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_uninstall.yml index c1ed9ec36..2deb391a0 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-discord service diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml index f5faa2333..67bf4966f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-discord settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2.license new file mode 100644 index 000000000..7b4bc3507 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2022 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2.license new file mode 100644 index 000000000..16b2b499b --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-discord/templates/systemd/matrix-mx-puppet-discord.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml index 67ecd6cbd..3672be8ce 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Mx Puppet GroupMe is a Matrix <-> GroupMe bridge # Project source code URL: https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml index de225e71d..2deab4a92 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml index 44dc72e47..28f5700b5 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure MX Puppet Groupme paths exist diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml index ce0823e6e..04a7eed54 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-groupme service diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml index c52c038b1..a5cce9efa 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-groupme settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2.license new file mode 100644 index 000000000..3065e3d50 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2021 Cody Neiman +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2.license new file mode 100644 index 000000000..eaa700407 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/systemd/matrix-mx-puppet-groupme.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Cody Neiman +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml index 168c4a3b3..e5d132cee 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mx-puppet-instagram bridges instagram DMs # Project source code URL: https://github.com/Sorunome/mx-puppet-instagram diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml index 0d46532ce..81a6441d2 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml index 47ec55ef7..c57f86fac 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_uninstall.yml index 943c0556a..b3b465060 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-instagram service diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml index 67a2c6978..2cd23b9c5 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-instagram settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2.license new file mode 100644 index 000000000..7ae771d35 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2022 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2.license new file mode 100644 index 000000000..ed96bddd2 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/systemd/matrix-mx-puppet-instagram.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml index b46df5994..fd71a20c5 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml @@ -1,3 +1,18 @@ +# SPDX-FileCopyrightText: 2020 Rodrigo Belem +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Marcel Ackermann +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Daniel Sonck +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Mx Puppet Slack is a Matrix <-> Slack bridge # Project source code URL: https://gitlab.com/mx-puppet/slack/mx-puppet-slack diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml index d5d3d421e..69ac4bfb7 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Rodrigo Belem +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml index c46a25bd1..f194959d3 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Rodrigo Belem +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure MX Puppet Slack paths exist diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_uninstall.yml index 444939198..33d2ad22c 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Rodrigo Belem +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-slack service diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml index dbc1d0025..0299dcdfe 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 Rodrigo Belem +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-slack settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2.license new file mode 100644 index 000000000..e590b6fec --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2021 Marcel Ackermann +SPDX-FileCopyrightText: 2022 Jim Myhrberg +SPDX-FileCopyrightText: 2022 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/templates/labels.j2 b/roles/custom/matrix-bridge-mx-puppet-slack/templates/labels.j2 index 0937c9d75..d00e0d067 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-slack/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mx_puppet_slack_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2.license new file mode 100644 index 000000000..04f321b44 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-slack/templates/systemd/matrix-mx-puppet-slack.service.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Rodrigo Belem +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml index 0e4ce1674..7fb0ce320 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Mx Puppet Steam is a Matrix <-> Steam bridge # Project source code URL: https://github.com/icewind1991/mx-puppet-steam diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml index 66d2980d3..bae270632 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml index a29c5e44f..ef7c7ee13 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2020 Panagiotis Vasilopoulos +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure MX Puppet Steam paths exist diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_uninstall.yml index 75d0ebc0f..1281ee4f8 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-steam service diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/validate_config.yml index 7a09a8073..50e3a124f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-steam settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2.license new file mode 100644 index 000000000..7b4bc3507 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2022 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2.license new file mode 100644 index 000000000..16b2b499b --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-steam/templates/systemd/matrix-mx-puppet-steam.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml index 24fc7fc07..3d6d2d40c 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 Tulir Asokan +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Mx Puppet Twitter is a Matrix <-> Twitter bridge diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml index 3cfe6a793..fb8d79a78 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Tulir Asokan +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml index 8d385dd14..f128a990f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 Tulir Asokan +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure MX Puppet Twitter paths exist diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_uninstall.yml index c529f0b34..c5f3bc2bf 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Tulir Asokan +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mx-puppet-twitter service diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml index a8f6b0bb0..07584ac85 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 Tulir Asokan +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mx-puppet-twitter settings not defined diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2.license new file mode 100644 index 000000000..cd0180bcb --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2020 Tulir Asokan + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/labels.j2 b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/labels.j2 index 9aef5fe0d..a1f2b295a 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mx_puppet_twitter_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2.license b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2.license new file mode 100644 index 000000000..2bcb63426 --- /dev/null +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/systemd/matrix-mx-puppet-twitter.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2020 Tulir Asokan + +SPDX-License-Identifier: AGPL-3.0-or-later From 1bc0a1bf07fcc8e812b499932e0fe20b0c535adf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 14:41:51 +0900 Subject: [PATCH 681/952] Update docs/configuring-dns.md: reduce the width of the table Signed-off-by: Suguru Hirahara --- docs/configuring-dns.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index a5237889f..2b2b425eb 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -25,10 +25,10 @@ To set up Matrix on your domain, you'd need to do some DNS configuration. To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below. -| Type | Host | Priority | Weight | Port | Target | -| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------| -| A | `matrix` | - | - | - | `matrix-server-IP` | -| CNAME | `element` | - | - | - | `matrix.example.com` | +| Type | Host | Priority | Weight | Port | Target | +| ----- | --------- | -------- | ------ | ---- | ---------------------| +| A | `matrix` | - | - | - | `matrix-server-IP` | +| CNAME | `element` | - | - | - | `matrix.example.com` | As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine). From 54467fe7d5de045573dbc57820f44c2ec336a626 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 14:59:25 +0900 Subject: [PATCH 682/952] Update docs/alternative-architectures.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/alternative-architectures.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/alternative-architectures.md b/docs/alternative-architectures.md index fa05a4b46..63127b317 100644 --- a/docs/alternative-architectures.md +++ b/docs/alternative-architectures.md @@ -1,3 +1,11 @@ + + # Alternative architectures As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported. From 86d94d77e3ad99aa3671cbb67f10b1ee4df60063 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 14:59:58 +0900 Subject: [PATCH 683/952] Update docs/configuring-playbook.md: add a copyright header Those authors were picked up based on the current status (dae0f446034ae594f4ca77fe3c0861ded24ad3f9), the others (around 30 people whose contributions have been removed) being grouped as "MDAD project contributors". Signed-off-by: Suguru Hirahara --- docs/configuring-playbook.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 5edc22326..2220c9d3f 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -1,3 +1,19 @@ + + # Configuring the playbook [Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md) From d6bf789710dec1567f47f5d7f3c4911ebafff9ea Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 23 Feb 2025 10:06:44 +0200 Subject: [PATCH 684/952] Remove `matrix_container_global_registry_prefix` variable This is done for a few reasons: - less globals and more indepdendence for each role is better. We rely on various externally-hosted roles and they don't rely on this global either. - `matrix_container_global_registry_prefix` could make people think they could just override this variable and have all their images pull from elsewhere. This is rarely the case, unless you've taken special care to mirror all the various components (from their respective registries) to your own. In such a case, you probably know what you're mirroring and can adjust individual variables. - nowadays, various components live on different registries. With Docker Inc tightening rate limits for Docker Hub, it's even more likely that we'll see increased diversity in where images are hosted --- CHANGELOG.md | 2 +- .../matrix-appservice-draupnir-for-all/defaults/main.yml | 2 +- roles/custom/matrix-base/defaults/main.yml | 2 -- roles/custom/matrix-base/tasks/validate_config.yml | 1 + roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- .../matrix-bot-matrix-registration-bot/defaults/main.yml | 3 ++- roles/custom/matrix-bot-mjolnir/defaults/main.yml | 2 +- .../matrix-bridge-appservice-irc/defaults/main.yml | 5 +++-- .../matrix-bridge-appservice-slack/defaults/main.yml | 3 ++- .../matrix-bridge-appservice-webhooks/defaults/main.yml | 2 +- .../matrix-bridge-go-skype-bridge/defaults/main.yml | 2 +- .../custom/matrix-bridge-heisenbridge/defaults/main.yml | 3 ++- .../matrix-bridge-mx-puppet-instagram/defaults/main.yml | 2 +- .../matrix-bridge-mx-puppet-steam/defaults/main.yml | 2 +- .../matrix-bridge-mx-puppet-twitter/defaults/main.yml | 2 +- roles/custom/matrix-bridge-sms/defaults/main.yml | 4 +++- roles/custom/matrix-bridge-wechat/defaults/main.yml | 4 ++-- .../matrix-cactus-comments-client/defaults/main.yml | 3 ++- roles/custom/matrix-cactus-comments/defaults/main.yml | 4 +++- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- roles/custom/matrix-client-element/defaults/main.yml | 2 +- roles/custom/matrix-corporal/defaults/main.yml | 2 +- roles/custom/matrix-coturn/defaults/main.yml | 2 +- roles/custom/matrix-dendrite/defaults/main.yml | 2 +- roles/custom/matrix-dimension/defaults/main.yml | 2 +- roles/custom/matrix-dynamic-dns/defaults/main.yml | 2 +- roles/custom/matrix-email2matrix/defaults/main.yml | 2 +- roles/custom/matrix-ma1sd/defaults/main.yml | 2 +- roles/custom/matrix-pantalaimon/defaults/main.yml | 2 +- roles/custom/matrix-registration/defaults/main.yml | 2 +- roles/custom/matrix-static-files/defaults/main.yml | 3 ++- roles/custom/matrix-sygnal/defaults/main.yml | 2 +- .../defaults/main.yml | 4 +++- .../matrix-synapse-usage-exporter/defaults/main.yml | 2 +- .../matrix-user-verification-service/defaults/main.yml | 4 ++-- .../tasks/validate_config.yml | 9 +++++++++ 36 files changed, 58 insertions(+), 38 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d02bbc69c..2e1d832ba 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -312,7 +312,7 @@ If you'd like to switch back to the original synapse-admin software, you can do ```yaml matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}awesometechnologies/synapse-admin:{{ matrix_synapse_admin_version }}" -matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'docker.io/' }}" matrix_synapse_admin_version: 0.10.3 diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index 140b92d4a..658fd4b66 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -11,7 +11,7 @@ matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" matrix_appservice_draupnir_for_all_docker_image: "{{ matrix_appservice_draupnir_for_all_docker_image_name_prefix }}gnuxie/draupnir:{{ matrix_appservice_draupnir_for_all_version }}" -matrix_appservice_draupnir_for_all_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_draupnir_for_all_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_appservice_draupnir_for_all_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_draupnir_for_all_container_image_self_build else 'docker.io/' }}" matrix_appservice_draupnir_for_all_docker_image_force_pull: "{{ matrix_appservice_draupnir_for_all_docker_image.endswith(':latest') }}" matrix_appservice_draupnir_for_all_base_path: "{{ matrix_base_data_path }}/draupnir-for-all" diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index f44db0ba6..1741924af 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -136,8 +136,6 @@ matrix_architecture: "{{ 'amd64' if ansible_architecture == 'x86_64' else ('arm6 # We just remap from our `matrix_architecture` values to what Debian and possibly other distros call things. matrix_debian_arch: "{{ 'armhf' if matrix_architecture == 'arm32' else matrix_architecture }}" -matrix_container_global_registry_prefix: "docker.io/" - matrix_user_username: "matrix" matrix_user_groupname: "matrix" diff --git a/roles/custom/matrix-base/tasks/validate_config.yml b/roles/custom/matrix-base/tasks/validate_config.yml index 41320a5fb..68020a2b3 100644 --- a/roles/custom/matrix-base/tasks/validate_config.yml +++ b/roles/custom/matrix-base/tasks/validate_config.yml @@ -21,6 +21,7 @@ - {'old': 'matrix_client_element_e2ee_default', 'new': 'matrix_static_files_file_matrix_client_property_io_element_e2ee_default'} - {'old': 'matrix_client_element_e2ee_secure_backup_required', 'new': 'matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_required'} - {'old': 'matrix_client_element_e2ee_secure_backup_setup_methods', 'new': 'matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_setup_methods'} + - {'old': 'matrix_container_global_registry_prefix', 'new': ''} # We have a dedicated check for this variable, because we'd like to have a custom (friendlier) message. - name: Fail if matrix_homeserver_generic_secret_key is undefined diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 57db9448d..472da0afa 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -11,7 +11,7 @@ matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" matrix_bot_draupnir_docker_image: "{{ matrix_bot_draupnir_docker_image_name_prefix }}gnuxie/draupnir:{{ matrix_bot_draupnir_version }}" -matrix_bot_draupnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_draupnir_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_bot_draupnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_draupnir_container_image_self_build else 'docker.io/' }}" matrix_bot_draupnir_docker_image_force_pull: "{{ matrix_bot_draupnir_docker_image.endswith(':latest') }}" matrix_bot_draupnir_base_path: "{{ matrix_base_data_path }}/draupnir" diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index 9423e8fad..d4ab6579f 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -12,7 +12,8 @@ matrix_bot_matrix_registration_bot_docker_src_files_path: "{{ matrix_bot_matrix_ matrix_bot_matrix_registration_bot_version: 1.3.0 matrix_bot_matrix_registration_bot_docker_iteration: 0 matrix_bot_matrix_registration_bot_docker_tag: "{{ matrix_bot_matrix_registration_bot_version }}-{{ matrix_bot_matrix_registration_bot_docker_iteration}}" -matrix_bot_matrix_registration_bot_docker_image: "{{ matrix_container_global_registry_prefix }}moanos/matrix-registration-bot:{{ matrix_bot_matrix_registration_bot_docker_tag }}" +matrix_bot_matrix_registration_bot_docker_image: "{{ matrix_bot_matrix_registration_bot_docker_image_registry_prefix }}moanos/matrix-registration-bot:{{ matrix_bot_matrix_registration_bot_docker_tag }}" +matrix_bot_matrix_registration_bot_docker_image_registry_prefix: docker.io/ matrix_bot_matrix_registration_bot_docker_image_force_pull: "{{ matrix_bot_matrix_registration_bot_docker_image.endswith(':latest') }}" matrix_bot_matrix_registration_bot_base_path: "{{ matrix_base_data_path }}/matrix-registration-bot" diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml index cba27a58d..149818653 100644 --- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml +++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml @@ -11,7 +11,7 @@ matrix_bot_mjolnir_container_image_self_build: false matrix_bot_mjolnir_container_image_self_build_repo: "https://github.com/matrix-org/mjolnir.git" matrix_bot_mjolnir_docker_image: "{{ matrix_bot_mjolnir_docker_image_name_prefix }}matrixdotorg/mjolnir:{{ matrix_bot_mjolnir_version }}" -matrix_bot_mjolnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_mjolnir_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_bot_mjolnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_mjolnir_container_image_self_build else 'docker.io/' }}" matrix_bot_mjolnir_docker_image_force_pull: "{{ matrix_bot_mjolnir_docker_image.endswith(':latest') }}" matrix_bot_mjolnir_base_path: "{{ matrix_base_data_path }}/mjolnir" diff --git a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml index 4ae0d8655..534cac9f0 100644 --- a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml @@ -13,10 +13,11 @@ matrix_appservice_irc_docker_src_files_path: "{{ matrix_base_data_path }}/appser # It's a bare version number now. We try to somewhat retain compatibility below. # renovate: datasource=docker depName=docker.io/matrixdotorg/matrix-appservice-irc matrix_appservice_irc_version: 1.0.1 -matrix_appservice_irc_docker_image: "{{ matrix_container_global_registry_prefix }}matrixdotorg/matrix-appservice-irc:{{ matrix_appservice_irc_docker_image_tag }}" +matrix_appservice_irc_docker_image: "{{ matrix_appservice_irc_docker_image_registry_prefix }}matrixdotorg/matrix-appservice-irc:{{ matrix_appservice_irc_docker_image_tag }}" +matrix_appservice_irc_docker_image_registry_prefix: docker.io/ matrix_appservice_irc_docker_image_tag: "{{ 'latest' if matrix_appservice_irc_version == 'latest' else ('release-' + matrix_appservice_irc_version) }}" matrix_appservice_irc_docker_image_force_pull: "{{ matrix_appservice_irc_docker_image.endswith(':latest') }}" -matrix_appservice_irc_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_irc_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_appservice_irc_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_irc_container_image_self_build else 'docker.io/' }}" matrix_appservice_irc_base_path: "{{ matrix_base_data_path }}/appservice-irc" matrix_appservice_irc_config_path: "{{ matrix_appservice_irc_base_path }}/config" diff --git a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml index b5c6f6bf9..195106cee 100644 --- a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml @@ -17,7 +17,8 @@ matrix_appservice_slack_docker_src_files_path: "{{ matrix_base_data_path }}/apps # It's a bare version number now. We try to somewhat retain compatibility below. # renovate: datasource=docker depName=docker.io/matrixdotorg/matrix-appservice-slack matrix_appservice_slack_version: 2.1.2 -matrix_appservice_slack_docker_image: "{{ matrix_container_global_registry_prefix }}matrixdotorg/matrix-appservice-slack:{{ matrix_appservice_slack_docker_image_tag }}" +matrix_appservice_slack_docker_image: "{{ matrix_appservice_slack_docker_image_registry_prefix }}matrixdotorg/matrix-appservice-slack:{{ matrix_appservice_slack_docker_image_tag }}" +matrix_appservice_slack_docker_image_registry_prefix: docker.io/ matrix_appservice_slack_docker_image_tag: "{{ 'latest' if matrix_appservice_slack_version == 'latest' else ('release-' + matrix_appservice_slack_version) }}" matrix_appservice_slack_docker_image_force_pull: "{{ matrix_appservice_slack_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml index aaa8d564f..226c893d0 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml @@ -15,7 +15,7 @@ matrix_appservice_webhooks_container_image_self_build_repo_dockerfile_path: "Doc matrix_appservice_webhooks_version: v1.0.3-01 matrix_appservice_webhooks_docker_image: "{{ matrix_appservice_webhooks_docker_image_name_prefix }}redoonetworks/matrix-appservice-webhooks:{{ matrix_appservice_webhooks_version }}" -matrix_appservice_webhooks_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_webhooks_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_appservice_webhooks_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_webhooks_container_image_self_build else 'docker.io/' }}" matrix_appservice_webhooks_docker_image_force_pull: "{{ matrix_appservice_webhooks_docker_image.endswith(':latest') }}" matrix_appservice_webhooks_base_path: "{{ matrix_base_data_path }}/appservice-webhooks" diff --git a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml index a8e29d547..7b8b8c732 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml @@ -11,7 +11,7 @@ matrix_go_skype_bridge_container_image_self_build_branch: "{{ 'master' if matrix # renovate: datasource=docker depName=nodefyme/go-skype-bridge matrix_go_skype_bridge_version: latest matrix_go_skype_bridge_docker_image: "{{ matrix_go_skype_bridge_docker_image_name_prefix }}nodefyme/go-skype-bridge:{{ matrix_go_skype_bridge_version }}" -matrix_go_skype_bridge_docker_image_name_prefix: "{{ 'localhost/' if matrix_go_skype_bridge_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_go_skype_bridge_docker_image_name_prefix: "{{ 'localhost/' if matrix_go_skype_bridge_container_image_self_build else 'docker.io/' }}" matrix_go_skype_bridge_docker_image_force_pull: "{{ matrix_go_skype_bridge_docker_image.endswith(':latest') }}" matrix_go_skype_bridge_base_path: "{{ matrix_base_data_path }}/go-skype-bridge" diff --git a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml index ee1cea6b4..a6a34c444 100644 --- a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml @@ -10,7 +10,8 @@ matrix_heisenbridge_path_prefix: "/heisenbridge" # renovate: datasource=docker depName=hif1/heisenbridge matrix_heisenbridge_version: 1.15.0 -matrix_heisenbridge_docker_image: "{{ matrix_container_global_registry_prefix }}hif1/heisenbridge:{{ matrix_heisenbridge_version }}" +matrix_heisenbridge_docker_image: "{{ matrix_heisenbridge_docker_image_registry_prefix }}hif1/heisenbridge:{{ matrix_heisenbridge_version }}" +matrix_heisenbridge_docker_image_registry_prefix: docker.io/ matrix_heisenbridge_docker_image_force_pull: "{{ matrix_heisenbridge_docker_image.endswith(':latest') }}" # Set this to your Matrix ID if you want to enforce the owner, otherwise first _local_ user becomes one diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml index e5d132cee..78ea2ad33 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml @@ -21,7 +21,7 @@ matrix_mx_puppet_instagram_container_image_self_build_repo_version: "{{ 'master' # renovate: datasource=docker depName=sorunome/mx-puppet-instagram matrix_mx_puppet_instagram_version: latest matrix_mx_puppet_instagram_docker_image: "{{ matrix_mx_puppet_instagram_docker_image_name_prefix }}sorunome/mx-puppet-instagram:{{ matrix_mx_puppet_instagram_version }}" -matrix_mx_puppet_instagram_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_instagram_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_mx_puppet_instagram_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_instagram_container_image_self_build else 'docker.io/' }}" matrix_mx_puppet_instagram_docker_image_force_pull: "{{ matrix_mx_puppet_instagram_docker_image.endswith(':latest') }}" matrix_mx_puppet_instagram_base_path: "{{ matrix_base_data_path }}/mx-puppet-instagram" diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml index 7fb0ce320..94b1e4def 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml @@ -27,7 +27,7 @@ matrix_mx_puppet_steam_container_http_host_bind_port: '' # renovate: datasource=docker depName=icewind1991/mx-puppet-steam matrix_mx_puppet_steam_version: latest matrix_mx_puppet_steam_docker_image: "{{ matrix_mx_puppet_steam_docker_image_name_prefix }}icewind1991/mx-puppet-steam:{{ matrix_mx_puppet_steam_version }}" -matrix_mx_puppet_steam_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_steam_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_mx_puppet_steam_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_steam_container_image_self_build else 'docker.io/' }}" matrix_mx_puppet_steam_docker_image_force_pull: "{{ matrix_mx_puppet_steam_docker_image.endswith(':latest') }}" matrix_mx_puppet_steam_base_path: "{{ matrix_base_data_path }}/mx-puppet-steam" diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml index 3d6d2d40c..7dfded3d7 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml @@ -31,7 +31,7 @@ matrix_mx_puppet_twitter_container_http_host_bind_port: '' # renovate: datasource=docker depName=sorunome/mx-puppet-twitter matrix_mx_puppet_twitter_version: latest matrix_mx_puppet_twitter_docker_image: "{{ matrix_mx_puppet_twitter_docker_image_name_prefix }}sorunome/mx-puppet-twitter:{{ matrix_mx_puppet_twitter_version }}" -matrix_mx_puppet_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_twitter_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_mx_puppet_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_twitter_container_image_self_build else 'docker.io/' }}" matrix_mx_puppet_twitter_docker_image_force_pull: "{{ matrix_mx_puppet_twitter_docker_image.endswith(':latest') }}" matrix_mx_puppet_twitter_base_path: "{{ matrix_base_data_path }}/mx-puppet-twitter" diff --git a/roles/custom/matrix-bridge-sms/defaults/main.yml b/roles/custom/matrix-bridge-sms/defaults/main.yml index 048bc85c2..2cabe39b5 100644 --- a/roles/custom/matrix-bridge-sms/defaults/main.yml +++ b/roles/custom/matrix-bridge-sms/defaults/main.yml @@ -6,7 +6,9 @@ matrix_sms_bridge_enabled: true # renovate: datasource=docker depName=folivonet/matrix-sms-bridge matrix_sms_bridge_version: 0.5.9 -matrix_sms_bridge_docker_image: "{{ matrix_container_global_registry_prefix }}folivonet/matrix-sms-bridge:{{ matrix_sms_bridge_version }}" +matrix_sms_bridge_docker_image: "{{ matrix_sms_bridge_docker_image_registry_prefix }}folivonet/matrix-sms-bridge:{{ matrix_sms_bridge_docker_image_tag }}" +matrix_sms_bridge_docker_image_registry_prefix: docker.io/ +matrix_sms_bridge_docker_image_tag: "{{ matrix_sms_bridge_version }}" matrix_sms_bridge_base_path: "{{ matrix_base_data_path }}/matrix-sms-bridge" matrix_sms_bridge_config_path: "{{ matrix_base_data_path }}/matrix-sms-bridge/config" diff --git a/roles/custom/matrix-bridge-wechat/defaults/main.yml b/roles/custom/matrix-bridge-wechat/defaults/main.yml index 4c9d9f0b0..948329083 100644 --- a/roles/custom/matrix-bridge-wechat/defaults/main.yml +++ b/roles/custom/matrix-bridge-wechat/defaults/main.yml @@ -8,7 +8,7 @@ matrix_wechat_enabled: true # renovate: datasource=docker depName=lxduo/matrix-wechat matrix_wechat_version: 0.2.4 matrix_wechat_container_image: "{{ matrix_wechat_container_image_name_prefix }}lxduo/matrix-wechat:{{ matrix_wechat_version }}" -matrix_wechat_container_image_name_prefix: "{{ 'localhost/' if matrix_wechat_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_wechat_container_image_name_prefix: "{{ 'localhost/' if matrix_wechat_container_image_self_build else 'docker.io/' }}" matrix_wechat_container_image_force_pull: "{{ matrix_wechat_container_image.endswith(':latest') }}" matrix_wechat_container_image_self_build: false @@ -18,7 +18,7 @@ matrix_wechat_container_image_self_build_branch: "{{ 'master' if matrix_wechat_v # renovate: datasource=docker depName=lxduo/matrix-wechat-agent matrix_wechat_agent_version: 0.0.1 matrix_wechat_agent_container_image: "{{ matrix_wechat_agent_container_image_name_prefix }}lxduo/matrix-wechat-agent:{{ matrix_wechat_agent_version }}" -matrix_wechat_agent_container_image_name_prefix: "{{ 'localhost/' if matrix_wechat_agent_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_wechat_agent_container_image_name_prefix: "{{ 'localhost/' if matrix_wechat_agent_container_image_self_build else 'docker.io/' }}" matrix_wechat_agent_container_image_force_pull: "{{ matrix_wechat_agent_container_image.endswith(':latest') }}" # The agent needs to write to /home/user/.vnc. diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index e8ff73d08..36493e87f 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -15,7 +15,8 @@ matrix_cactus_comments_client_public_path_file_permissions: "0644" # renovate: datasource=docker depName=joseluisq/static-web-server matrix_cactus_comments_client_version: 2.36.0 -matrix_cactus_comments_client_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" +matrix_cactus_comments_client_container_image: "{{ matrix_cactus_comments_client_container_image_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" +matrix_cactus_comments_client_container_image_registry_prefix: docker.io/ matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}" matrix_cactus_comments_client_container_image_force_pull: "{{ matrix_cactus_comments_client_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-cactus-comments/defaults/main.yml b/roles/custom/matrix-cactus-comments/defaults/main.yml index a31ae1a1d..96f98d048 100644 --- a/roles/custom/matrix-cactus-comments/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments/defaults/main.yml @@ -27,7 +27,9 @@ matrix_cactus_comments_container_port: 5000 # renovate: datasource=docker depName=cactuscomments/cactus-appservice matrix_cactus_comments_version: 0.9.0 -matrix_cactus_comments_docker_image: "{{ matrix_container_global_registry_prefix }}cactuscomments/cactus-appservice:{{ matrix_cactus_comments_version }}" +matrix_cactus_comments_docker_image: "{{ matrix_cactus_comments_docker_image_registry_prefix }}cactuscomments/cactus-appservice:{{ matrix_cactus_comments_docker_image_tag }}" +matrix_cactus_comments_docker_image_registry_prefix: docker.io/ +matrix_cactus_comments_docker_image_tag: "{{ matrix_cactus_comments_version }}" matrix_cactus_comments_docker_image_force_pull: "{{ matrix_cactus_comments_docker_image.endswith(':latest') }}" matrix_cactus_comments_container_network: "" diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index cae8c5727..57085fd5b 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -9,7 +9,7 @@ matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/ # renovate: datasource=docker depName=ajbura/cinny matrix_client_cinny_version: v4.3.2 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" -matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else 'docker.io/' }}" matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}" matrix_client_cinny_data_path: "{{ matrix_base_data_path }}/client-cinny" diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index d536b55e4..1cfcae331 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -14,7 +14,7 @@ matrix_client_element_container_image_self_build_low_memory_system_patch_enabled matrix_client_element_version: v1.11.92 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" -matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else 'docker.io/' }}" matrix_client_element_docker_image_force_pull: "{{ matrix_client_element_docker_image.endswith(':latest') }}" matrix_client_element_data_path: "{{ matrix_base_data_path }}/client-element" diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml index 6013e3a28..1b0d52f0a 100644 --- a/roles/custom/matrix-corporal/defaults/main.yml +++ b/roles/custom/matrix-corporal/defaults/main.yml @@ -82,7 +82,7 @@ matrix_corporal_systemd_required_services_list_auto: [] matrix_corporal_systemd_required_services_list_custom: [] matrix_corporal_docker_image: "{{ matrix_corporal_docker_image_name_prefix }}devture/matrix-corporal:{{ matrix_corporal_docker_image_tag }}" -matrix_corporal_docker_image_name_prefix: "{{ 'localhost/' if matrix_corporal_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_corporal_docker_image_name_prefix: "{{ 'localhost/' if matrix_corporal_container_image_self_build else 'docker.io/' }}" matrix_corporal_docker_image_tag: "{{ matrix_corporal_version }}" # for backward-compatibility matrix_corporal_docker_image_force_pull: "{{ matrix_corporal_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index 78e8e35f9..04d221224 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -11,7 +11,7 @@ matrix_coturn_container_image_self_build_repo_dockerfile_path: "docker/coturn/al # renovate: datasource=docker depName=coturn/coturn matrix_coturn_version: 4.6.2-r11 matrix_coturn_docker_image: "{{ matrix_coturn_docker_image_name_prefix }}coturn/coturn:{{ matrix_coturn_version }}-alpine" -matrix_coturn_docker_image_name_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_coturn_docker_image_name_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else 'docker.io/' }}" matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith(':latest') }}" # The Docker network that coturn would be put into. diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml index f57947252..e39ccae6a 100644 --- a/roles/custom/matrix-dendrite/defaults/main.yml +++ b/roles/custom/matrix-dendrite/defaults/main.yml @@ -11,7 +11,7 @@ matrix_dendrite_container_image_self_build_repo: "https://github.com/matrix-org/ matrix_dendrite_docker_image_path: "matrixdotorg/dendrite-monolith" matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_name_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}" -matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else 'docker.io/' }}" # renovate: datasource=docker depName=matrixdotorg/dendrite-monolith matrix_dendrite_docker_image_tag: "v0.14.1" matrix_dendrite_docker_image_force_pull: "{{ matrix_dendrite_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml index 136d9b9ec..d0ba9727c 100644 --- a/roles/custom/matrix-dimension/defaults/main.yml +++ b/roles/custom/matrix-dimension/defaults/main.yml @@ -32,7 +32,7 @@ matrix_dimension_docker_src_files_path: "{{ matrix_base_data_path }}/docker-src/ # renovate: datasource=docker depName=turt2live/matrix-dimension matrix_dimension_version: latest matrix_dimension_docker_image: "{{ matrix_dimension_docker_image_name_prefix }}turt2live/matrix-dimension:{{ matrix_dimension_version }}" -matrix_dimension_docker_image_name_prefix: "{{ 'localhost/' if matrix_dimension_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_dimension_docker_image_name_prefix: "{{ 'localhost/' if matrix_dimension_container_image_self_build else 'docker.io/' }}" matrix_dimension_docker_image_force_pull: "{{ matrix_dimension_docker_image.endswith(':latest') }}" # List of systemd services that matrix-dimension.service depends on. diff --git a/roles/custom/matrix-dynamic-dns/defaults/main.yml b/roles/custom/matrix-dynamic-dns/defaults/main.yml index 066d501f0..269072c67 100644 --- a/roles/custom/matrix-dynamic-dns/defaults/main.yml +++ b/roles/custom/matrix-dynamic-dns/defaults/main.yml @@ -13,7 +13,7 @@ matrix_dynamic_dns_version: 4.0.0 # The docker container to use when in mode matrix_dynamic_dns_docker_image: "{{ matrix_dynamic_dns_docker_image_name_prefix }}linuxserver/ddclient:{{ matrix_dynamic_dns_version }}" -matrix_dynamic_dns_docker_image_name_prefix: "{{ 'localhost/' if matrix_dynamic_dns_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_dynamic_dns_docker_image_name_prefix: "{{ 'localhost/' if matrix_dynamic_dns_container_image_self_build else 'docker.io/' }}" # The image to force pull matrix_dynamic_dns_docker_image_force_pull: "{{ matrix_dynamic_dns_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-email2matrix/defaults/main.yml b/roles/custom/matrix-email2matrix/defaults/main.yml index 2c55c6661..d5355e877 100644 --- a/roles/custom/matrix-email2matrix/defaults/main.yml +++ b/roles/custom/matrix-email2matrix/defaults/main.yml @@ -13,7 +13,7 @@ matrix_email2matrix_container_image_self_build_branch: "{{ matrix_email2matrix_v # renovate: datasource=docker depName=devture/email2matrix matrix_email2matrix_version: 1.1.0 -matrix_email2matrix_docker_image_prefix: "{{ 'localhost/' if matrix_email2matrix_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_email2matrix_docker_image_prefix: "{{ 'localhost/' if matrix_email2matrix_container_image_self_build else 'docker.io/' }}" matrix_email2matrix_docker_image: "{{ matrix_email2matrix_docker_image_prefix }}devture/email2matrix:{{ matrix_email2matrix_version }}" matrix_email2matrix_docker_image_force_pull: "{{ matrix_email2matrix_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-ma1sd/defaults/main.yml b/roles/custom/matrix-ma1sd/defaults/main.yml index 39d0d4ed3..78d6cfac4 100644 --- a/roles/custom/matrix-ma1sd/defaults/main.yml +++ b/roles/custom/matrix-ma1sd/defaults/main.yml @@ -15,7 +15,7 @@ matrix_ma1sd_container_image_self_build_branch: "{{ matrix_ma1sd_version }}" matrix_ma1sd_version: "2.5.0" matrix_ma1sd_docker_image: "{{ matrix_ma1sd_docker_image_name_prefix }}ma1uta/ma1sd:{{ matrix_ma1sd_version }}" -matrix_ma1sd_docker_image_name_prefix: "{{ 'localhost/' if matrix_ma1sd_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_ma1sd_docker_image_name_prefix: "{{ 'localhost/' if matrix_ma1sd_container_image_self_build else 'docker.io/' }}" matrix_ma1sd_docker_image_force_pull: "{{ matrix_ma1sd_docker_image.endswith(':latest') }}" matrix_ma1sd_base_path: "{{ matrix_base_data_path }}/ma1sd" diff --git a/roles/custom/matrix-pantalaimon/defaults/main.yml b/roles/custom/matrix-pantalaimon/defaults/main.yml index 977f53d0a..3708a0b33 100644 --- a/roles/custom/matrix-pantalaimon/defaults/main.yml +++ b/roles/custom/matrix-pantalaimon/defaults/main.yml @@ -11,7 +11,7 @@ matrix_pantalaimon_container_image_self_build_repo: "https://github.com/matrix-o matrix_pantalaimon_container_image_self_build_repo_version: "{{ 'main' if matrix_pantalaimon_version == 'latest' else matrix_pantalaimon_version }}" matrix_pantalaimon_docker_image: "{{ matrix_pantalaimon_docker_image_name_prefix }}matrixdotorg/pantalaimon:v{{ matrix_pantalaimon_version }}" -matrix_pantalaimon_docker_image_name_prefix: "{{ 'localhost/' if matrix_pantalaimon_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_pantalaimon_docker_image_name_prefix: "{{ 'localhost/' if matrix_pantalaimon_container_image_self_build else 'docker.io/' }}" matrix_pantalaimon_docker_image_force_pull: "{{ matrix_pantalaimon_docker_image.endswith(':latest') }}" matrix_pantalaimon_base_path: "{{ matrix_base_data_path }}/pantalaimon" diff --git a/roles/custom/matrix-registration/defaults/main.yml b/roles/custom/matrix-registration/defaults/main.yml index 9e8a350ab..0cc776fe7 100644 --- a/roles/custom/matrix-registration/defaults/main.yml +++ b/roles/custom/matrix-registration/defaults/main.yml @@ -26,7 +26,7 @@ matrix_registration_docker_src_files_path: "{{ matrix_registration_base_path }}/ matrix_registration_version: "v0.7.2" matrix_registration_docker_image: "{{ matrix_registration_docker_image_name_prefix }}zeratax/matrix-registration:{{ matrix_registration_version }}" -matrix_registration_docker_image_name_prefix: "{{ 'localhost/' if matrix_registration_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_registration_docker_image_name_prefix: "{{ 'localhost/' if matrix_registration_container_image_self_build else 'docker.io/' }}" matrix_registration_docker_image_force_pull: "{{ matrix_registration_docker_image.endswith(':latest') }}" matrix_registration_container_network: "" diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index e31c9b75b..e4dd36e95 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -24,7 +24,8 @@ matrix_static_files_systemd_wanted_services_list: "{{ matrix_static_files_system matrix_static_files_systemd_wanted_services_list_auto: [] matrix_static_files_systemd_wanted_services_list_custom: [] -matrix_static_files_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_static_files_container_image_tag }}" +matrix_static_files_container_image: "{{ matrix_static_files_container_image_registry_prefix }}joseluisq/static-web-server:{{ matrix_static_files_container_image_tag }}" +matrix_static_files_container_image_registry_prefix: docker.io/ matrix_static_files_container_image_tag: "{{ 'latest' if matrix_static_files_version == 'latest' else (matrix_static_files_version + '-alpine') }}" matrix_static_files_container_image_force_pull: "{{ matrix_static_files_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-sygnal/defaults/main.yml b/roles/custom/matrix-sygnal/defaults/main.yml index 3f9bc77fc..490b391d8 100644 --- a/roles/custom/matrix-sygnal/defaults/main.yml +++ b/roles/custom/matrix-sygnal/defaults/main.yml @@ -27,7 +27,7 @@ matrix_sygnal_systemd_wanted_services_list: [] matrix_sygnal_docker_image: "{{ matrix_sygnal_docker_image_registry_prefix }}matrixdotorg/sygnal:{{ matrix_sygnal_docker_image_tag }}" matrix_sygnal_docker_image_tag: "{{ matrix_sygnal_version }}" -matrix_sygnal_docker_image_registry_prefix: "{{ matrix_container_global_registry_prefix }}" +matrix_sygnal_docker_image_registry_prefix: docker.io/ matrix_sygnal_docker_image_force_pull: "{{ matrix_sygnal_docker_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 98e0c2d65..47074216e 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -30,7 +30,9 @@ matrix_synapse_reverse_proxy_companion_systemd_wanted_services_list: ['matrix-sy # We use an official nginx image, which we fix-up to run unprivileged. # An alternative would be an `nginxinc/nginx-unprivileged` image, but # that is frequently out of date. -matrix_synapse_reverse_proxy_companion_container_image: "{{ matrix_container_global_registry_prefix }}nginx:{{ matrix_synapse_reverse_proxy_companion_version }}" +matrix_synapse_reverse_proxy_companion_container_image: "{{ matrix_synapse_reverse_proxy_companion_container_image_registry_prefix }}nginx:{{ matrix_synapse_reverse_proxy_companion_container_image_tag }}" +matrix_synapse_reverse_proxy_companion_container_image_registry_prefix: docker.io/ +matrix_synapse_reverse_proxy_companion_container_image_tag: "{{ matrix_synapse_reverse_proxy_companion_version }}" matrix_synapse_reverse_proxy_companion_container_image_force_pull: "{{ matrix_synapse_reverse_proxy_companion_container_image.endswith(':latest') }}" matrix_synapse_reverse_proxy_companion_container_network: "" diff --git a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml index 71f7b7423..3b0579bad 100644 --- a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml +++ b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml @@ -22,7 +22,7 @@ matrix_synapse_usage_exporter_container_image_self_build_repo: "https://github.c matrix_synapse_usage_exporter_container_image_path: "loelkes/synapse-usage-exporter" matrix_synapse_usage_exporter_container_image: "{{ matrix_synapse_usage_exporter_container_image_name_prefix }}{{ matrix_synapse_usage_exporter_container_image_path }}:{{ matrix_synapse_usage_exporter_container_image_tag }}" -matrix_synapse_usage_exporter_container_image_name_prefix: "{{ 'localhost/' if matrix_synapse_usage_exporter_container_image_self_build else matrix_container_global_registry_prefix }}" +matrix_synapse_usage_exporter_container_image_name_prefix: "{{ 'localhost/' if matrix_synapse_usage_exporter_container_image_self_build else 'docker.io/' }}" matrix_synapse_usage_exporter_container_image_tag: "{{ 'main' if matrix_synapse_usage_exporter_container_image_self_build else 'latest' }}" matrix_synapse_usage_exporter_container_image_force_pull: "{{ matrix_synapse_usage_exporter_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-user-verification-service/defaults/main.yml b/roles/custom/matrix-user-verification-service/defaults/main.yml index d46b99194..510d258da 100644 --- a/roles/custom/matrix-user-verification-service/defaults/main.yml +++ b/roles/custom/matrix-user-verification-service/defaults/main.yml @@ -24,8 +24,8 @@ matrix_user_verification_service_config_env_file: "{{ matrix_user_verification_s matrix_user_verification_service_docker_src_files_path: "{{ matrix_user_verification_service_base_path }}/docker-src" # Docker -matrix_user_verification_service_docker_image_name_prefix: "{{ matrix_container_global_registry_prefix }}" -matrix_user_verification_service_docker_image: "{{ matrix_user_verification_service_docker_image_name_prefix }}matrixdotorg/matrix-user-verification-service:{{ matrix_user_verification_service_version }}" +matrix_user_verification_service_docker_image: "{{ matrix_user_verification_service_docker_image_registry_prefix }}matrixdotorg/matrix-user-verification-service:{{ matrix_user_verification_service_version }}" +matrix_user_verification_service_docker_image_registry_prefix: docker.io/ matrix_user_verification_service_docker_image_force_pull: "{{ matrix_user_verification_service_docker_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. diff --git a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml index e283ce6c3..309557c84 100644 --- a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml +++ b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml @@ -32,3 +32,12 @@ with_items: - {'name': 'matrix_user_verification_service_uvs_homeserver_url', when: true} - {'name': 'matrix_user_verification_service_container_network', when: true} + +- name: (Deprecation) Catch and report renamed matrix-user-verification-service variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_user_verification_service_docker_image_name_prefix', 'new': 'matrix_user_verification_service_docker_image_registry_prefix'} From ee431798a6d6e3a867d792b159787d744840dd5a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 18:20:47 +0900 Subject: [PATCH 685/952] Update docs/getting-the-playbook.md: make the list tighter Signed-off-by: Suguru Hirahara --- docs/getting-the-playbook.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index 6607cae49..d1c951fa5 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -14,9 +14,7 @@ This Ansible playbook is meant to be executed on your own computer (not the Matr In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well. You can retrieve the playbook's source code by: - - [Using git to get the playbook](#using-git-to-get-the-playbook) (recommended) - - [Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended) ## Using git to get the playbook From 0d137db283c3b029a2ced8d734e5baf414f292aa Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 23 Feb 2025 12:09:06 +0200 Subject: [PATCH 686/952] Re-enable STUN/UDP by default so that old Element mobile clients can work Partially reverts ac26cc1cb0d6423b751b74ddb06a8c793f63dd56. The configurability introduced there is still available, so people can easily disable this, if necessary. --- CHANGELOG.md | 25 ++++++++++++++++++++ docs/prerequisites.md | 1 + roles/custom/matrix-coturn/defaults/main.yml | 5 ++-- 3 files changed, 29 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2e1d832ba..c5a21d80f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,28 @@ +# 2025-02-23 + +## The playbook defaults to exposing the Coturn STUN port (3478) over UDP once again + +Recently, we made the playbook [default to exposing the Coturn STUN port (3478) only over TCP](#the-playbook-now-defaults-to-exposing-the-coturn-stun-port-3478-only-over-tcp) to reduce the severity of DDoS amplification/reflection attacks. + +It seems like old Element clients on mobile devices only support talking to the STUN port over UDP, not TCP. +To accommodate such ancient clients, we're now **reversing this change** and **defaulting to exposing the Coturn STUN port (3478) over UDP once again**. + +In light of this new information, you have 2 options: + +1. **If you already adapted to the previous change and would like to adapt to this change one again**: + +- make sure the `3478/udp` port is whitelisted in your external firewall (if you have one) once again. + +2. **If you don't care about old Element clients and wish to reduce the severity of DDoS amplification/reflection attacks**: + +- Consider closing the STUN/UDP port with the following configuration: + + ```yaml + matrix_coturn_container_stun_plain_host_bind_port_udp: "" + ``` + +- Consider keeping `3478/udp` blocked in your external firewall (if you have one) + # 2025-02-21 ## Docker daemon options are no longer adjusted when IPv6 is enabled diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 8b813f1bd..b1f891d7c 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -60,6 +60,7 @@ We will be using `example.com` as the domain in the following instruction. Pleas - `80/tcp`: HTTP webserver - `443/tcp` and `443/udp`: HTTPS webserver - `3478/tcp`: STUN/TURN over TCP (used by [coturn](./docs/configuring-playbook-turn.md)) + - `3478/udp`: STUN/TURN over TCP (used by [coturn](./docs/configuring-playbook-turn.md)) - `5349/tcp`: TURN over TCP (used by [coturn](./docs/configuring-playbook-turn.md)) - `5349/udp`: TURN over UDP (used by [coturn](./docs/configuring-playbook-turn.md)) - `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**. diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index 04d221224..febee5009 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -60,9 +60,10 @@ matrix_coturn_container_stun_plain_host_bind_port_tcp: "{{ '3478' if matrix_cotu # # Takes an ":" or "" value (e.g. "127.0.0.1:3478"), or empty string to not expose. # -# This is not done by default to decrease the risk of DDoS amplification attacks. +# Ideally, we'd like to set this to "" to avoid exposing this port and decrease the risk of DDoS amplification attacks. # See: https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit -matrix_coturn_container_stun_plain_host_bind_port_udp: "" +# In practice, old Element clients only support talking to the STUN port over UDP, not TCP, so we need to keep this enabled for now. +matrix_coturn_container_stun_plain_host_bind_port_udp: "{{ '3478' if matrix_coturn_container_network != 'host' else '' }}" # Controls whether the coturn container exposes its TLS STUN port (tcp/5349 in the container) over TCP. # From c1eae5fc00cdced01ee54a73c403f99fbb662533 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 19:25:04 +0900 Subject: [PATCH 687/952] Update docs/installing.md: minor edits Signed-off-by: Suguru Hirahara --- docs/installing.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/installing.md b/docs/installing.md index e0bf44404..181dc3a1b 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -134,9 +134,11 @@ After configuring the playbook, run the command below: ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files,start ``` +**If an error is not returned, the installation has completed and the services have been started successfully**🎉 + ## Things to do next -After finilizing the installation, you can: +After completing the installation, you can: - [check if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work) - or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.) @@ -147,7 +149,7 @@ After finilizing the installation, you can: * or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. - or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate)) -### Maintaining your setup in the future +### ⚠️Keep the playbook and services up-to-date While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**. From b4bcac7e481fb9936788a64bd1b90f568bdc3614 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 23 Feb 2025 19:25:12 +0900 Subject: [PATCH 688/952] Update docs/quick-start.md: minor edits - Reduce width of the table for DNS configuration Signed-off-by: Suguru Hirahara --- docs/quick-start.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/quick-start.md b/docs/quick-start.md index fbb579f61..70e4de3f3 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -43,10 +43,10 @@ After installing and configuring prerequisites, you will need to **configure DNS To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below. -| Type | Host | Priority | Weight | Port | Target | -| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------| -| A | `matrix` | - | - | - | `matrix-server-IP` | -| CNAME | `element` | - | - | - | `matrix.example.com` | +| Type | Host | Priority | Weight | Port | Target | +| ----- | ----------| -------- | ------ | ---- | ---------------------| +| A | `matrix` | - | - | - | `matrix-server-IP` | +| CNAME | `element` | - | - | - | `matrix.example.com` | As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine). @@ -191,7 +191,7 @@ Finally, let's make sure that you can log in to the created account with the spe You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in. -**If you successfully logged in to your account, installing and configuring is complete**🎉 +**If you successfully logged in to your account, the installation and configuration have completed successfully**🎉 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. From cca3b06cf09206e681ad663360929a5f78c1b2f7 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 23 Feb 2025 12:32:32 +0200 Subject: [PATCH 689/952] =?UTF-8?q?Add=20space=20after=20=E2=9A=A0?= =?UTF-8?q?=EF=B8=8F=20on=20installing.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/installing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/installing.md b/docs/installing.md index 181dc3a1b..34e4548b5 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -149,7 +149,7 @@ After completing the installation, you can: * or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting. - or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate)) -### ⚠️Keep the playbook and services up-to-date +### ⚠️ Keep the playbook and services up-to-date While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**. From af054a48336e84fc2bb9eefa6261f720d89ea1ff Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 23 Feb 2025 14:39:53 +0000 Subject: [PATCH 690/952] Update ajbura/cinny Docker tag to v4.4.0 --- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 57085fd5b..7612576e5 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -7,7 +7,7 @@ matrix_client_cinny_container_image_self_build: false matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git" # renovate: datasource=docker depName=ajbura/cinny -matrix_client_cinny_version: v4.3.2 +matrix_client_cinny_version: v4.4.0 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else 'docker.io/' }}" matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}" From 31e5c10a1bedbd6c968e5ea7bd4582759a613e2a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 24 Feb 2025 03:33:47 +0900 Subject: [PATCH 691/952] Update docs for Ansible This commit changes ansible.md title and adds a link to the page on docs/README.md to improve discoverability of the guide a little bit. Signed-off-by: Suguru Hirahara --- docs/README.md | 2 ++ docs/ansible.md | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index ba0fd1e48..f1765920f 100644 --- a/docs/README.md +++ b/docs/README.md @@ -91,3 +91,5 @@ If your server and services experience issues, feel free to come to [our support - [Uninstalling](uninstalling.md) - [Updating users passwords](updating-users-passwords.md) + +- [Using Ansible for the playbook](ansible.md) diff --git a/docs/ansible.md b/docs/ansible.md index 83814cc92..15f00632f 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -3,12 +3,12 @@ SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev SPDX-FileCopyrightText: 2020 Hanno J. Gödecke SPDX-FileCopyrightText: 2020 Aaron Raimist SPDX-FileCopyrightText: 2022 Kai Biebel -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> -# Running this playbook +# Using Ansible for the playbook This playbook is meant to be run using [Ansible](https://www.ansible.com/). From 7448b4728c9b2907c7cfb17c983968ca256aa2b1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 24 Feb 2025 12:47:36 +0900 Subject: [PATCH 692/952] Edit docs: minor edits Signed-off-by: Suguru Hirahara --- docs/installing.md | 2 +- docs/prerequisites.md | 2 +- docs/quick-start.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/installing.md b/docs/installing.md index 34e4548b5..6bc0a463e 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -157,7 +157,7 @@ The upstream projects, which this playbook makes use of, occasionally if not oft Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date. -For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md) +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) 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. diff --git a/docs/prerequisites.md b/docs/prerequisites.md index b1f891d7c..0e65548b5 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -27,7 +27,7 @@ We will be using `example.com` as the domain in the following instruction. Pleas - [`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components. -- [`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md). +- [`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). - 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. diff --git a/docs/quick-start.md b/docs/quick-start.md index 70e4de3f3..cedb18a9d 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -207,4 +207,4 @@ While this playbook helps you to set up Matrix services and maintain them, it wi Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date. -For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md) +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) From 90540c244ff7078fbbc93a50d416e543f88e31fe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 24 Feb 2025 17:03:54 +0900 Subject: [PATCH 693/952] Update docs/maintenance-postgres.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/maintenance-postgres.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index 569d5fd4d..7beff8e7c 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -1,3 +1,15 @@ + + # PostgreSQL maintenance This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix. From 77209126bb624a68c90fce8e52761778e017166d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 24 Feb 2025 17:47:38 +0900 Subject: [PATCH 694/952] Update docs: remove duplicated whitespace characters Signed-off-by: Suguru Hirahara --- CHANGELOG.md | 8 ++++---- docs/configuring-playbook-bridge-mx-puppet-discord.md | 2 +- docs/configuring-playbook-ntfy.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c5a21d80f..a25aebfda 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -787,7 +787,7 @@ If you were using these values as a way to stay away from Traefik, you now have Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt. -Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network. +Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network. Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity. @@ -2799,12 +2799,12 @@ Until the issue gets fixed, we're making User Directory search not go to ma1sd b ## Newer IRC bridge (with potential breaking change) -This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream -made a change to how you define manual mappings. If you added a +This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream +made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no -change is necessary. `mappings` is not part of the default +change is necessary. `mappings` is not part of the default configuration. diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index b866dd5f6..f135d9b84 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -9,7 +9,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up MX Puppet Discord bridging (optional) -**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook. +**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook. - For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing. - For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook. diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index cbf67c7c3..ac7c157e2 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -6,7 +6,7 @@ Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hos 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. -**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. +**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer. As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it. ## Adjusting DNS records From 0da9c0c07593fd2ea65b4a28e9aeadbb7313f8b0 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:27:08 +0200 Subject: [PATCH 695/952] Upgrade backup-borg (v1.4.0-1.9.10-3 -> v1.4.0-1.9.10-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 675569d11..c1cfdc207 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-3 + version: v1.4.0-1.9.10-4 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git version: v0.3.0-3 From 3e17ae8b1bd66be303ec5025bcecdefb20912c41 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:29:22 +0200 Subject: [PATCH 696/952] Upgrade container-socket-proxy (v0.3.0-3 -> v0.3.0-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index c1cfdc207..b4d10fbac 100644 --- a/requirements.yml +++ b/requirements.yml @@ -7,7 +7,7 @@ version: v1.4.0-1.9.10-4 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git - version: v0.3.0-3 + version: v0.3.0-4 name: container_socket_proxy - src: git+https://github.com/geerlingguy/ansible-role-docker version: 7.4.5 From c212346881ca90cdd7e9ad15aca7e69da91e0da2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:31:56 +0200 Subject: [PATCH 697/952] Upgrade Etherpad (v2.2.7-3 -> v2.2.7-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index b4d10fbac..5da5c857a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -16,7 +16,7 @@ version: 129c8590e106b83e6f4c259649a613c6279e937a name: docker_sdk_for_python - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git - version: v2.2.7-3 + version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git version: v4.98-r0-4-2 From 650fca9d27b8f71648f8dd61bd3804c48fdbd3be Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:34:44 +0200 Subject: [PATCH 698/952] Upgrade exim-relay (v4.98-r0-4-2 -> v4.98-r0-4-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 5da5c857a..896fd3209 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98-r0-4-2 + version: v4.98-r0-4-3 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-0 From ed63688bb8d493b499b71750db164197e6d0d371 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:36:17 +0200 Subject: [PATCH 699/952] Upgrade Grafana (v11.5.2-0 -> v11.5.2-1) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 896fd3209..92910f9cd 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98-r0-4-3 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.5.2-0 + version: v11.5.2-1 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v10008-2 From 3441a29b7b3e13029e8da8e84996db5aedfd2e9c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:39:05 +0200 Subject: [PATCH 700/952] Upgrade Jitsi (v10008-2 -> v10008-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 92910f9cd..0f7b4b714 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.5.2-1 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v10008-2 + version: v10008-3 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git version: v2.11.0-2 From 9dd3a71c389153e68d1f96a74b2ae6cb6ac62123 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:40:28 +0200 Subject: [PATCH 701/952] Upgrade ntfy (v2.11.0-2 -> v2.11.0-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 0f7b4b714..60406765a 100644 --- a/requirements.yml +++ b/requirements.yml @@ -28,7 +28,7 @@ version: v10008-3 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git - version: v2.11.0-2 + version: v2.11.0-3 name: ntfy - src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git version: 201c939eed363de269a83ba29784fc3244846048 From 200059e3c6545532a7a0e0fcc7f3c64194cea99b Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:44:05 +0200 Subject: [PATCH 702/952] Upgrade Postgres (v17.2-2 -> v17.2-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 60406765a..8c9cf1d48 100644 --- a/requirements.yml +++ b/requirements.yml @@ -40,7 +40,7 @@ version: ff2fd42e1c1a9e28e3312bbd725395f9c2fc7f16 name: playbook_state_preserver - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres.git - version: v17.2-2 + version: v17.2-3 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git version: v17-2 From 400fa61bd0c15a18ca2ee91863160142c75c0e6e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:45:36 +0200 Subject: [PATCH 703/952] Upgrade postgres-backup (v17-2 -> v17-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 8c9cf1d48..ea9ca298b 100644 --- a/requirements.yml +++ b/requirements.yml @@ -43,7 +43,7 @@ version: v17.2-3 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git - version: v17-2 + version: v17-3 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git version: v2.55.1-2 From d4bfc268033ca3b85edadfa6de5d5fd77333f482 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:46:55 +0200 Subject: [PATCH 704/952] Upgrade Prometheus (v2.55.1-2 -> v2.55.1-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index ea9ca298b..642a05fbf 100644 --- a/requirements.yml +++ b/requirements.yml @@ -46,7 +46,7 @@ version: v17-3 name: postgres_backup - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git - version: v2.55.1-2 + version: v2.55.1-3 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git version: v1.8.2-3 From 66746bfa01a8e31fd5cb5cfd22af8b158aaff12a Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:48:55 +0200 Subject: [PATCH 705/952] Upgrade prometheus-node-exporter (v1.8.2-3 -> v1.8.2-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 642a05fbf..0b91e8594 100644 --- a/requirements.yml +++ b/requirements.yml @@ -49,7 +49,7 @@ version: v2.55.1-3 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git - version: v1.8.2-3 + version: v1.8.2-4 name: prometheus_node_exporter - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter.git version: v0.14.0-7 From 620dfa889d9e7882a88201b8c1d32d35c48f27a5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:52:24 +0200 Subject: [PATCH 706/952] Upgrade prometheus-postgres-exporter (v0.14.0-7 -> v0.14.0-9) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 0b91e8594..c326102b2 100644 --- a/requirements.yml +++ b/requirements.yml @@ -52,7 +52,7 @@ version: v1.8.2-4 name: prometheus_node_exporter - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter.git - version: v0.14.0-7 + version: v0.14.0-9 name: prometheus_postgres_exporter - src: git+https://github.com/devture/com.devture.ansible.role.systemd_docker_base.git version: v1.4.0-0 From a97988c7941cd63ebe4a2c6fded6f63ec9d42162 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:53:57 +0200 Subject: [PATCH 707/952] Upgrade prometheus-node-exporter (v1.8.2-4 -> v1.8.2-5) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index c326102b2..5e68de64b 100644 --- a/requirements.yml +++ b/requirements.yml @@ -49,7 +49,7 @@ version: v2.55.1-3 name: prometheus - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git - version: v1.8.2-4 + version: v1.8.2-5 name: prometheus_node_exporter - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter.git version: v0.14.0-9 From ce835c395ffd5c7994936df0174e7003c976fd89 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:55:48 +0200 Subject: [PATCH 708/952] Upgrade Traefik (v3.3.3-3 -> v3.3.3-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 5e68de64b..a4855e666 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.3-3 + version: v3.3.3-4 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-6 From 6ef6bcdf387c77d2b3fe1e45f1bde9aa014ae0fa Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:57:00 +0200 Subject: [PATCH 709/952] Upgrade traefik-certs-dumper (v2.8.3-6 -> v2.8.3-7) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index a4855e666..a53ccf2c0 100644 --- a/requirements.yml +++ b/requirements.yml @@ -67,7 +67,7 @@ version: v3.3.3-4 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git - version: v2.8.3-6 + version: v2.8.3-7 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git version: v8.0.1-2 From 11842116b361ce7b13443a4f95d4106dc37166f2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:58:14 +0200 Subject: [PATCH 710/952] Upgrade Valkey (v8.0.1-2 -> v8.0.1-3) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index a53ccf2c0..57b5db2d7 100644 --- a/requirements.yml +++ b/requirements.yml @@ -70,5 +70,5 @@ version: v2.8.3-7 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git - version: v8.0.1-2 + version: v8.0.1-3 name: valkey From c47eca389b921243d7befcd7d8083a8abb018913 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 07:59:37 +0200 Subject: [PATCH 711/952] Rework all roles to include `component_(docker|container)_image_registry_prefix*` variables This: - brings consistency - no more mixing `_name_prefix` and `_registry_prefix` - adds extensibility - a future patch will allow reconfiguring all registry prefixes for all roles in the playbook We still have `_docker_` vs `_container_` inconsistencies. These may be worked on later. --- .../matrix-alertmanager-receiver/defaults/main.yml | 7 ++++--- .../tasks/validate_config.yml | 8 ++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ roles/custom/matrix-bot-baibot/defaults/main.yml | 6 ++++-- .../matrix-bot-baibot/tasks/validate_config.yml | 9 +++++++++ .../custom/matrix-bot-buscarron/defaults/main.yml | 6 ++++-- .../matrix-bot-buscarron/tasks/validate_config.yml | 1 + roles/custom/matrix-bot-chatgpt/defaults/main.yml | 7 ++++--- .../matrix-bot-chatgpt/tasks/validate_config.yml | 1 + roles/custom/matrix-bot-draupnir/defaults/main.yml | 6 ++++-- .../matrix-bot-draupnir/tasks/validate_config.yml | 9 +++++++++ roles/custom/matrix-bot-go-neb/defaults/main.yml | 4 +++- roles/custom/matrix-bot-honoroit/defaults/main.yml | 6 ++++-- .../matrix-bot-honoroit/tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 4 +++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + roles/custom/matrix-bot-maubot/defaults/main.yml | 6 ++++-- .../matrix-bot-maubot/tasks/validate_config.yml | 1 + roles/custom/matrix-bot-mjolnir/defaults/main.yml | 6 ++++-- .../matrix-bot-mjolnir/tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../matrix-bridge-appservice-irc/defaults/main.yml | 5 +++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 12 ++++++++---- .../tasks/validate_config.yml | 10 ++++++++++ .../defaults/main.yml | 4 +++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../matrix-bridge-heisenbridge/defaults/main.yml | 4 +++- .../matrix-bridge-hookshot/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 9 +++++++++ .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-signal/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-slack/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 12 ++++++++---- .../tasks/validate_config.yml | 4 +++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 5 ++++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 10 +++++++++- .../defaults/main.yml | 8 +++++--- .../tasks/validate_config.yml | 10 +++++++++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 10 +++++++++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 10 +++++++++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-postmoogle/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 8 ++++++++ roles/custom/matrix-bridge-sms/defaults/main.yml | 4 +++- .../custom/matrix-bridge-wechat/defaults/main.yml | 6 ++++-- .../matrix-bridge-wechat/tasks/validate_config.yml | 8 ++++++++ .../defaults/main.yml | 4 +++- .../matrix-cactus-comments/defaults/main.yml | 4 +++- roles/custom/matrix-client-cinny/defaults/main.yml | 6 ++++-- .../matrix-client-cinny/tasks/validate_config.yml | 8 ++++++++ .../custom/matrix-client-element/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + .../matrix-client-fluffychat/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 8 ++++++++ .../matrix-client-hydrogen/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 8 ++++++++ .../matrix-client-schildichat/defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + roles/custom/matrix-conduit/defaults/main.yml | 6 ++++-- .../matrix-conduit/tasks/validate_config.yml | 8 ++++++++ roles/custom/matrix-conduwuit/defaults/main.yml | 5 +++-- roles/custom/matrix-corporal/defaults/main.yml | 6 ++++-- .../matrix-corporal/tasks/validate_config.yml | 1 + roles/custom/matrix-coturn/defaults/main.yml | 6 ++++-- .../custom/matrix-coturn/tasks/validate_config.yml | 1 + roles/custom/matrix-dendrite/defaults/main.yml | 6 ++++-- .../matrix-dendrite/tasks/validate_config.yml | 1 + roles/custom/matrix-dimension/defaults/main.yml | 6 ++++-- .../matrix-dimension/tasks/validate_config.yml | 1 + roles/custom/matrix-dynamic-dns/defaults/main.yml | 6 ++++-- .../matrix-dynamic-dns/tasks/validate_config.yml | 14 +++++++++++--- roles/custom/matrix-email2matrix/defaults/main.yml | 6 ++++-- .../matrix-email2matrix/tasks/validate_config.yml | 8 ++++++++ .../defaults/main.yml | 7 ++++++- roles/custom/matrix-ma1sd/defaults/main.yml | 6 ++++-- .../custom/matrix-ma1sd/tasks/validate_config.yml | 1 + roles/custom/matrix-media-repo/defaults/main.yml | 6 ++++-- .../matrix-media-repo/tasks/validate_config.yml | 1 + roles/custom/matrix-pantalaimon/defaults/main.yml | 6 ++++-- .../matrix-pantalaimon/tasks/validate_config.yml | 10 +++++++++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 1 + roles/custom/matrix-rageshake/defaults/main.yml | 7 ++++--- .../matrix-rageshake/tasks/validate_config.yml | 8 ++++++++ roles/custom/matrix-registration/defaults/main.yml | 6 ++++-- roles/custom/matrix-sliding-sync/defaults/main.yml | 7 ++++--- .../matrix-sliding-sync/tasks/validate_config.yml | 8 ++++++++ roles/custom/matrix-static-files/defaults/main.yml | 4 +++- roles/custom/matrix-sygnal/defaults/main.yml | 4 +++- .../custom/matrix-synapse-admin/defaults/main.yml | 6 ++++-- .../matrix-synapse-admin/tasks/validate_config.yml | 3 ++- .../defaults/main.yml | 6 ++++-- .../tasks/validate_config.yml | 4 +++- .../defaults/main.yml | 4 +++- .../defaults/main.yml | 6 ++++-- .../matrix-synapse-usage-exporter/tasks/main.yml | 3 +++ .../tasks/validate_config.yml | 10 ++++++++++ roles/custom/matrix-synapse/defaults/main.yml | 13 ++++++++----- .../matrix-synapse/tasks/validate_config.yml | 2 ++ .../defaults/main.yml | 5 +++-- 138 files changed, 610 insertions(+), 171 deletions(-) create mode 100644 roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index 561ca62a2..8dcd3a8f0 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -25,11 +25,12 @@ matrix_alertmanager_receiver_container_image_self_build_repo: https://github.com matrix_alertmanager_receiver_container_image_self_build_repo_version: "{{ 'main' if matrix_alertmanager_receiver_version == 'main' else matrix_alertmanager_receiver_version }}" matrix_alertmanager_receiver_container_src_path: "{{ matrix_alertmanager_receiver_base_path }}/container-src" -matrix_alertmanager_receiver_container_image: "{{ matrix_alertmanager_receiver_container_image_name_prefix }}metio/matrix-alertmanager-receiver:{{ matrix_alertmanager_receiver_container_image_tag }}" -matrix_alertmanager_receiver_container_image_name_prefix: "{{ 'localhost/' if matrix_alertmanager_receiver_container_image_self_build else matrix_alertmanager_receiver_container_image_registry_prefix }}" +matrix_alertmanager_receiver_container_image: "{{ matrix_alertmanager_receiver_container_image_registry_prefix }}metio/matrix-alertmanager-receiver:{{ matrix_alertmanager_receiver_container_image_tag }}" matrix_alertmanager_receiver_container_image_tag: "{{ matrix_alertmanager_receiver_version }}" matrix_alertmanager_receiver_container_image_force_pull: "{{ matrix_alertmanager_receiver_container_image.endswith(':main') }}" -matrix_alertmanager_receiver_container_image_registry_prefix: docker.io/ +matrix_alertmanager_receiver_container_image_registry_prefix: "{{ matrix_alertmanager_receiver_container_image_registry_prefix_upstream }}" +matrix_alertmanager_receiver_container_image_registry_prefix_upstream: "{{ matrix_alertmanager_receiver_container_image_registry_prefix_upstream_default }}" +matrix_alertmanager_receiver_container_image_registry_prefix_upstream_default: "docker.io/" # The base container network. It will be auto-created by this role if it doesn't exist already. matrix_alertmanager_receiver_container_network: '' diff --git a/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml b/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml index 83591a956..34878b670 100644 --- a/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml +++ b/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml @@ -12,3 +12,11 @@ - {'name': 'matrix_alertmanager_receiver_container_network', when: true} - {'name': 'matrix_alertmanager_receiver_metrics_proxying_hostname', when: "{{ matrix_alertmanager_receiver_metrics_proxying_enabled }}"} - {'name': 'matrix_alertmanager_receiver_metrics_proxying_path_prefix', when: "{{ matrix_alertmanager_receiver_metrics_proxying_enabled }}"} + +- name: (Deprecation) Catch and report renamed matrix-alertmanager-receiver variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_alertmanager_receiver_container_image_name_prefix', 'new': 'matrix_alertmanager_receiver_container_image_registry_prefix'} diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index 658fd4b66..c7fe4a506 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -10,8 +10,10 @@ matrix_appservice_draupnir_for_all_version: "v2.1.0" matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" -matrix_appservice_draupnir_for_all_docker_image: "{{ matrix_appservice_draupnir_for_all_docker_image_name_prefix }}gnuxie/draupnir:{{ matrix_appservice_draupnir_for_all_version }}" -matrix_appservice_draupnir_for_all_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_draupnir_for_all_container_image_self_build else 'docker.io/' }}" +matrix_appservice_draupnir_for_all_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_draupnir_for_all_container_image_self_build else matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream }}" +matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream: "{{ matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream_default: "docker.io/" +matrix_appservice_draupnir_for_all_docker_image: "{{ matrix_appservice_draupnir_for_all_docker_image_registry_prefix }}gnuxie/draupnir:{{ matrix_appservice_draupnir_for_all_version }}" matrix_appservice_draupnir_for_all_docker_image_force_pull: "{{ matrix_appservice_draupnir_for_all_docker_image.endswith(':latest') }}" matrix_appservice_draupnir_for_all_base_path: "{{ matrix_base_data_path }}/draupnir-for-all" diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml index f0a1daf49..db572635d 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml @@ -7,3 +7,12 @@ - "matrix_appservice_draupnir_for_all_master_control_room_alias" - "matrix_bot_draupnir_container_network" when: "vars[item] == '' or vars[item] is none" + +- name: (Deprecation) Catch and report renamed matrix-appservice-draupnir-for-all settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_appservice_draupnir_for_all_docker_image_name_prefix', 'new': 'matrix_appservice_draupnir_for_all_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index f00cb8eda..4f50ce9dc 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -18,8 +18,10 @@ matrix_authentication_service_container_src_files_path: "{{ matrix_base_data_pat # renovate: datasource=docker depName=ghcr.io/element-hq/matrix-authentication-service matrix_authentication_service_version: 0.14.1 -matrix_authentication_service_container_image: "{{ matrix_authentication_service_container_image_name_prefix }}element-hq/matrix-authentication-service:{{ matrix_authentication_service_version }}" -matrix_authentication_service_container_image_name_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else 'ghcr.io/' }}" +matrix_authentication_service_container_image_registry_prefix: "{{ 'localhost/' if matrix_authentication_service_container_image_self_build else matrix_authentication_service_container_image_registry_prefix_upstream }}" +matrix_authentication_service_container_image_registry_prefix_upstream: "{{ matrix_authentication_service_container_image_registry_prefix_upstream_default }}" +matrix_authentication_service_container_image_registry_prefix_upstream_default: "ghcr.io/" +matrix_authentication_service_container_image: "{{ matrix_authentication_service_container_image_registry_prefix }}element-hq/matrix-authentication-service:{{ matrix_authentication_service_version }}" matrix_authentication_service_container_image_force_pull: "{{ matrix_authentication_service_container_image.endswith(':latest') }}" matrix_authentication_service_base_path: "{{ matrix_base_data_path }}/matrix-authentication-service" diff --git a/roles/custom/matrix-authentication-service/tasks/validate_config.yml b/roles/custom/matrix-authentication-service/tasks/validate_config.yml index 70cf3662d..7ef8b5a1c 100644 --- a/roles/custom/matrix-authentication-service/tasks/validate_config.yml +++ b/roles/custom/matrix-authentication-service/tasks/validate_config.yml @@ -29,3 +29,12 @@ ansible.builtin.fail: msg: "matrix_authentication_service_config_email_transport must be one of: blackhole, smtp, or aws_ses" when: "matrix_authentication_service_config_email_transport not in ['blackhole', 'smtp', 'aws_ses']" + +- name: (Deprecation) Catch and report renamed matrix-authentication-service settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_authentication_service_container_image_name_prefix', 'new': 'matrix_authentication_service_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index d3737b2a8..b17a55af3 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -12,8 +12,10 @@ matrix_bot_baibot_container_src_files_path: "{{ matrix_base_data_path }}/baibot/ # renovate: datasource=docker depName=ghcr.io/etkecc/baibot matrix_bot_baibot_version: v1.4.1 -matrix_bot_baibot_container_image: "{{ matrix_bot_baibot_container_image_name_prefix }}etkecc/baibot:{{ matrix_bot_baibot_version }}" -matrix_bot_baibot_container_image_name_prefix: "{{ 'localhost/' if matrix_bot_baibot_container_image_self_build else 'ghcr.io/' }}" +matrix_bot_baibot_container_image: "{{ matrix_bot_baibot_container_image_registry_prefix }}etkecc/baibot:{{ matrix_bot_baibot_version }}" +matrix_bot_baibot_container_image_registry_prefix: "{{ 'localhost/' if matrix_bot_baibot_container_image_self_build else matrix_bot_baibot_container_image_registry_prefix_upstream }}" +matrix_bot_baibot_container_image_registry_prefix_upstream: "{{ matrix_bot_baibot_container_image_registry_prefix_upstream_default }}" +matrix_bot_baibot_container_image_registry_prefix_upstream_default: "ghcr.io/" matrix_bot_baibot_container_image_force_pull: "{{ matrix_bot_baibot_container_image.endswith(':latest') }}" matrix_bot_baibot_base_path: "{{ matrix_base_data_path }}/baibot" diff --git a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml index 43e4cb8fc..bbf830c1f 100644 --- a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml @@ -26,3 +26,12 @@ msg: >- You need to define a required configuration setting (`matrix_bot_baibot_config_access_admin_patterns`) to specify which users are bot administrators. when: "matrix_bot_baibot_config_access_admin_patterns | length == 0" + +- name: (Deprecation) Catch and report renamed baibot settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_bot_baibot_container_image_name_prefix', 'new': 'matrix_bot_baibot_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-buscarron/defaults/main.yml b/roles/custom/matrix-bot-buscarron/defaults/main.yml index e8e2fa3e9..fd2295d84 100644 --- a/roles/custom/matrix-bot-buscarron/defaults/main.yml +++ b/roles/custom/matrix-bot-buscarron/defaults/main.yml @@ -29,8 +29,10 @@ matrix_bot_buscarron_docker_repo: "https://github.com/etkecc/buscarron.git" matrix_bot_buscarron_docker_repo_version: "{{ matrix_bot_buscarron_version }}" matrix_bot_buscarron_docker_src_files_path: "{{ matrix_base_data_path }}/buscarron/docker-src" -matrix_bot_buscarron_docker_image: "{{ matrix_bot_buscarron_docker_image_name_prefix }}etkecc/buscarron:{{ matrix_bot_buscarron_version }}" -matrix_bot_buscarron_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_buscarron_container_image_self_build else 'ghcr.io/' }}" +matrix_bot_buscarron_docker_image: "{{ matrix_bot_buscarron_docker_image_registry_prefix }}etkecc/buscarron:{{ matrix_bot_buscarron_version }}" +matrix_bot_buscarron_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_buscarron_container_image_self_build else matrix_bot_buscarron_docker_image_registry_prefix_upstream }}" +matrix_bot_buscarron_docker_image_registry_prefix_upstream: "{{ matrix_bot_buscarron_docker_image_registry_prefix_upstream_default }}" +matrix_bot_buscarron_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_bot_buscarron_docker_image_force_pull: "{{ matrix_bot_buscarron_docker_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. diff --git a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml index 0e968e55a..e9014ccea 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml @@ -10,6 +10,7 @@ - {'old': 'matrix_bot_buscarron_spam_hosts', 'new': ''} - {'old': 'matrix_bot_buscarron_spam_emails', 'new': ''} - {'old': 'matrix_bot_buscarron_spam_localparts', 'new': ''} + - {'old': 'matrix_bot_buscarron_container_image_name_prefix', 'new': 'matrix_bot_buscarron_container_image_registry_prefix'} - name: Fail if required Buscarron settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-bot-chatgpt/defaults/main.yml b/roles/custom/matrix-bot-chatgpt/defaults/main.yml index 50ca9c286..3b1c59a88 100644 --- a/roles/custom/matrix-bot-chatgpt/defaults/main.yml +++ b/roles/custom/matrix-bot-chatgpt/defaults/main.yml @@ -11,11 +11,12 @@ matrix_bot_chatgpt_container_image_self_build: false matrix_bot_chatgpt_container_image_self_build_repo: "https://github.com/matrixgpt/matrix-chatgpt-bot" matrix_bot_chatgpt_container_image_self_build_repo_version: "{{ 'main' if matrix_bot_chatgpt_version == 'latest' else matrix_bot_chatgpt_version }}" -matrix_bot_chatgpt_container_image: "{{ matrix_bot_chatgpt_container_image_name_prefix }}matrixgpt/matrix-chatgpt-bot:{{ matrix_bot_chatgpt_container_image_tag }}" -matrix_bot_chatgpt_container_image_name_prefix: "{{ 'localhost/' if matrix_bot_chatgpt_container_image_self_build else matrix_bot_chatgpt_container_image_registry_prefix }}" +matrix_bot_chatgpt_container_image: "{{ matrix_bot_chatgpt_container_image_registry_prefix }}matrixgpt/matrix-chatgpt-bot:{{ matrix_bot_chatgpt_container_image_tag }}" +matrix_bot_chatgpt_container_image_registry_prefix: "{{ 'localhost/' if matrix_bot_chatgpt_container_image_self_build else matrix_bot_chatgpt_container_image_registry_prefix_upstream }}" +matrix_bot_chatgpt_container_image_registry_prefix_upstream: "{{ matrix_bot_chatgpt_container_image_registry_prefix_upstream_default }}" +matrix_bot_chatgpt_container_image_registry_prefix_upstream_default: "ghcr.io/" matrix_bot_chatgpt_container_image_tag: "{{ matrix_bot_chatgpt_version }}" matrix_bot_chatgpt_container_image_force_pull: "{{ matrix_bot_chatgpt_container_image.endswith(':latest') }}" -matrix_bot_chatgpt_container_image_registry_prefix: ghcr.io/ matrix_bot_chatgpt_base_path: "{{ matrix_base_data_path }}/chatgpt" matrix_bot_chatgpt_config_path: "{{ matrix_bot_chatgpt_base_path }}/config" diff --git a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml index 44f103e01..51797882f 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml @@ -35,3 +35,4 @@ - {'old': 'matrix_bot_chatgpt_docker_repo', 'new': 'matrix_bot_chatgpt_container_image_self_build_repo'} - {'old': 'matrix_bot_chatgpt_docker_repo_version', 'new': 'matrix_bot_chatgpt_container_image_self_build_repo_version'} - {'old': 'matrix_bot_chatgpt_docker_src_files_path', 'new': 'matrix_bot_chatgpt_container_src_path'} + - {'old': 'matrix_bot_chatgpt_container_image_name_prefix', 'new': 'matrix_bot_chatgpt_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 472da0afa..42fce6812 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -10,8 +10,10 @@ matrix_bot_draupnir_version: "v2.1.0" matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" -matrix_bot_draupnir_docker_image: "{{ matrix_bot_draupnir_docker_image_name_prefix }}gnuxie/draupnir:{{ matrix_bot_draupnir_version }}" -matrix_bot_draupnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_draupnir_container_image_self_build else 'docker.io/' }}" +matrix_bot_draupnir_docker_image: "{{ matrix_bot_draupnir_docker_image_registry_prefix }}gnuxie/draupnir:{{ matrix_bot_draupnir_version }}" +matrix_bot_draupnir_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_draupnir_container_image_self_build else matrix_bot_draupnir_docker_image_registry_prefix_upstream }}" +matrix_bot_draupnir_docker_image_registry_prefix_upstream: "{{ matrix_bot_draupnir_docker_image_registry_prefix_upstream_default }}" +matrix_bot_draupnir_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_bot_draupnir_docker_image_force_pull: "{{ matrix_bot_draupnir_docker_image.endswith(':latest') }}" matrix_bot_draupnir_base_path: "{{ matrix_base_data_path }}/draupnir" diff --git a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml index 20acf748d..b369a5c00 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml @@ -35,3 +35,12 @@ "Note: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. To enable E2EE for Draupnir, it is recommended to use matrix_bot_draupnir_enable_experimental_rust_crypto instead. This warning can be disabled by setting matrix_bot_draupnir_pantalaimon_breakage_ignore to true." ] }} + +- name: (Deprecation) Catch and report renamed Draupnir settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_bot_draupnir_container_image_name_prefix', 'new': 'matrix_bot_draupnir_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-go-neb/defaults/main.yml b/roles/custom/matrix-bot-go-neb/defaults/main.yml index fd4bd9bd8..6695f621a 100644 --- a/roles/custom/matrix-bot-go-neb/defaults/main.yml +++ b/roles/custom/matrix-bot-go-neb/defaults/main.yml @@ -28,7 +28,9 @@ matrix_bot_go_neb_data_store_path: "{{ matrix_bot_go_neb_data_path }}/store" matrix_bot_go_neb_container_image: "{{ matrix_bot_go_neb_container_image_registry_prefix }}matrixdotorg/go-neb:{{ matrix_bot_go_neb_container_image_tag }}" matrix_bot_go_neb_container_image_tag: "{{ matrix_bot_go_neb_version }}" matrix_bot_go_neb_container_image_force_pull: "{{ matrix_bot_go_neb_container_image.endswith(':latest') }}" -matrix_bot_go_neb_container_image_registry_prefix: docker.io/ +matrix_bot_go_neb_container_image_registry_prefix: "{{ matrix_bot_go_neb_container_image_registry_prefix_upstream }}" +matrix_bot_go_neb_container_image_registry_prefix_upstream: "{{ matrix_bot_go_neb_container_image_registry_prefix_upstream_default }}" +matrix_bot_go_neb_container_image_registry_prefix_upstream_default: "docker.io/" # The base container network. It will be auto-created by this role if it doesn't exist already. matrix_bot_go_neb_container_network: matrix-bot-go-neb diff --git a/roles/custom/matrix-bot-honoroit/defaults/main.yml b/roles/custom/matrix-bot-honoroit/defaults/main.yml index 5b7720689..dd48cb36f 100644 --- a/roles/custom/matrix-bot-honoroit/defaults/main.yml +++ b/roles/custom/matrix-bot-honoroit/defaults/main.yml @@ -22,8 +22,10 @@ matrix_bot_honoroit_docker_src_files_path: "{{ matrix_base_data_path }}/honoroit # renovate: datasource=docker depName=ghcr.io/etkecc/honoroit matrix_bot_honoroit_version: v0.9.27 -matrix_bot_honoroit_docker_image: "{{ matrix_bot_honoroit_docker_image_name_prefix }}etkecc/honoroit:{{ matrix_bot_honoroit_version }}" -matrix_bot_honoroit_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_honoroit_container_image_self_build else 'ghcr.io/' }}" +matrix_bot_honoroit_docker_image: "{{ matrix_bot_honoroit_docker_image_registry_prefix }}etkecc/honoroit:{{ matrix_bot_honoroit_version }}" +matrix_bot_honoroit_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_honoroit_container_image_self_build else matrix_bot_honoroit_docker_image_registry_prefix_upstream }}" +matrix_bot_honoroit_docker_image_registry_prefix_upstream: "{{ matrix_bot_honoroit_docker_image_registry_prefix_upstream_default }}" +matrix_bot_honoroit_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_bot_honoroit_docker_image_force_pull: "{{ matrix_bot_honoroit_docker_image.endswith(':latest') }}" matrix_bot_honoroit_base_path: "{{ matrix_base_data_path }}/honoroit" diff --git a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml index afd580c2a..95df51dca 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml @@ -10,3 +10,12 @@ - {'name': 'matrix_bot_honoroit_password', when: true} - {'name': 'matrix_bot_honoroit_roomid', when: true} - {'name': 'matrix_bot_honoroit_database_hostname', when: "{{ matrix_bot_honoroit_database_engine == 'postgres' }}"} + +- name: (Deprecation) Catch and report renamed Honoroit settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_bot_honoroit_container_image_name_prefix', 'new': 'matrix_bot_honoroit_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index d4ab6579f..769e84b60 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -13,7 +13,9 @@ matrix_bot_matrix_registration_bot_version: 1.3.0 matrix_bot_matrix_registration_bot_docker_iteration: 0 matrix_bot_matrix_registration_bot_docker_tag: "{{ matrix_bot_matrix_registration_bot_version }}-{{ matrix_bot_matrix_registration_bot_docker_iteration}}" matrix_bot_matrix_registration_bot_docker_image: "{{ matrix_bot_matrix_registration_bot_docker_image_registry_prefix }}moanos/matrix-registration-bot:{{ matrix_bot_matrix_registration_bot_docker_tag }}" -matrix_bot_matrix_registration_bot_docker_image_registry_prefix: docker.io/ +matrix_bot_matrix_registration_bot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_matrix_registration_bot_container_image_self_build else matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream }}" +matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream: "{{ matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream_default }}" +matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_bot_matrix_registration_bot_docker_image_force_pull: "{{ matrix_bot_matrix_registration_bot_docker_image.endswith(':latest') }}" matrix_bot_matrix_registration_bot_base_path: "{{ matrix_base_data_path }}/matrix-registration-bot" diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml index e6074f70a..69d27307e 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml @@ -11,8 +11,10 @@ matrix_bot_matrix_reminder_bot_docker_src_files_path: "{{ matrix_base_data_path # renovate: datasource=docker depName=ghcr.io/anoadragon453/matrix-reminder-bot matrix_bot_matrix_reminder_bot_version: v0.3.0 -matrix_bot_matrix_reminder_bot_docker_image: "{{ matrix_bot_matrix_reminder_bot_docker_image_name_prefix }}anoadragon453/matrix-reminder-bot:{{ matrix_bot_matrix_reminder_bot_version }}" -matrix_bot_matrix_reminder_bot_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_matrix_reminder_bot_container_image_self_build else 'ghcr.io/' }}" +matrix_bot_matrix_reminder_bot_docker_image: "{{ matrix_bot_matrix_reminder_bot_docker_image_registry_prefix }}anoadragon453/matrix-reminder-bot:{{ matrix_bot_matrix_reminder_bot_version }}" +matrix_bot_matrix_reminder_bot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_matrix_reminder_bot_container_image_self_build else matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream }}" +matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream: "{{ matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream_default }}" +matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_bot_matrix_reminder_bot_docker_image_force_pull: "{{ matrix_bot_matrix_reminder_bot_docker_image.endswith(':latest') }}" matrix_bot_matrix_reminder_bot_base_path: "{{ matrix_base_data_path }}/matrix-reminder-bot" diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml index 072e392bd..96bab685f 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml @@ -20,3 +20,4 @@ when: "item.old in vars" with_items: - {'old': 'matrix_bot_matrix_reminder_bot_container_self_build', 'new': 'matrix_bot_matrix_reminder_bot_container_image_self_build'} + - {'old': 'matrix_bot_matrix_reminder_bot_container_image_name_prefix', 'new': 'matrix_bot_matrix_reminder_bot_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-maubot/defaults/main.yml b/roles/custom/matrix-bot-maubot/defaults/main.yml index 1ba960dca..976cdc16c 100644 --- a/roles/custom/matrix-bot-maubot/defaults/main.yml +++ b/roles/custom/matrix-bot-maubot/defaults/main.yml @@ -21,8 +21,10 @@ matrix_bot_maubot_docker_repo_version: "{{ 'master' if matrix_bot_maubot_version # renovate: datasource=docker depName=dock.mau.dev/maubot/maubot matrix_bot_maubot_version: v0.5.1 -matrix_bot_maubot_docker_image: "{{ matrix_bot_maubot_docker_image_name_prefix }}maubot/maubot:{{ matrix_bot_maubot_version }}" -matrix_bot_maubot_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_maubot_container_image_self_build else 'dock.mau.dev/' }}" +matrix_bot_maubot_docker_image: "{{ matrix_bot_maubot_docker_image_registry_prefix }}maubot/maubot:{{ matrix_bot_maubot_version }}" +matrix_bot_maubot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_maubot_container_image_self_build else matrix_bot_maubot_docker_image_registry_prefix_upstream }}" +matrix_bot_maubot_docker_image_registry_prefix_upstream: "{{ matrix_bot_maubot_docker_image_registry_prefix_upstream_default }}" +matrix_bot_maubot_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_bot_maubot_docker_image_force_pull: "{{ matrix_bot_maubot_docker_image.endswith(':latest') }}" # matrix_bot_maubot_docker_image_customized is the name of the locally built maubot image diff --git a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml index 297cec952..29409f7b8 100644 --- a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml @@ -10,6 +10,7 @@ - {'old': 'matrix_bot_maubot_management_interface_port', 'new': 'matrix_bot_maubot_server_port'} - {'old': 'matrix_bot_maubot_management_interface_http_bind_port', 'new': 'matrix_bot_maubot_container_management_interface_http_bind_port'} - {'old': 'matrix_bot_maubot_registration_shared_secret', 'new': 'matrix_bot_maubot_homeserver_secret'} + - {'old': 'matrix_bot_maubot_container_image_name_prefix', 'new': 'matrix_bot_maubot_container_image_registry_prefix'} - name: Fail if required maubot settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml index 149818653..25a958631 100644 --- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml +++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml @@ -10,8 +10,10 @@ matrix_bot_mjolnir_version: "v1.9.2" matrix_bot_mjolnir_container_image_self_build: false matrix_bot_mjolnir_container_image_self_build_repo: "https://github.com/matrix-org/mjolnir.git" -matrix_bot_mjolnir_docker_image: "{{ matrix_bot_mjolnir_docker_image_name_prefix }}matrixdotorg/mjolnir:{{ matrix_bot_mjolnir_version }}" -matrix_bot_mjolnir_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_mjolnir_container_image_self_build else 'docker.io/' }}" +matrix_bot_mjolnir_docker_image: "{{ matrix_bot_mjolnir_docker_image_registry_prefix }}matrixdotorg/mjolnir:{{ matrix_bot_mjolnir_version }}" +matrix_bot_mjolnir_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_mjolnir_container_image_self_build else matrix_bot_mjolnir_docker_image_registry_prefix_upstream }}" +matrix_bot_mjolnir_docker_image_registry_prefix_upstream: "{{ matrix_bot_mjolnir_docker_image_registry_prefix_upstream_default }}" +matrix_bot_mjolnir_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_bot_mjolnir_docker_image_force_pull: "{{ matrix_bot_mjolnir_docker_image.endswith(':latest') }}" matrix_bot_mjolnir_base_path: "{{ matrix_base_data_path }}/mjolnir" diff --git a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml index 7fd67e589..8788609a1 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml @@ -19,3 +19,12 @@ with_items: - {'name': 'matrix_bot_mjolnir_access_token', when: "{{ matrix_bot_mjolnir_pantalaimon_use }}"} when: "item.when | bool and not (vars[item.name] == '' or vars[item.name] is none)" + +- name: (Deprecation) Catch and report renamed Mjolnir settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_bot_mjolnir_container_image_name_prefix', 'new': 'matrix_bot_mjolnir_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml index 64b2d7db8..8fa789f38 100644 --- a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml @@ -7,8 +7,10 @@ matrix_appservice_discord_container_image_self_build: false # renovate: datasource=docker depName=ghcr.io/matrix-org/matrix-appservice-discord matrix_appservice_discord_version: v4.0.0 -matrix_appservice_discord_docker_image: "{{ matrix_appservice_discord_docker_image_name_prefix }}matrix-org/matrix-appservice-discord:{{ matrix_appservice_discord_version }}" -matrix_appservice_discord_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_discord_container_image_self_build else 'ghcr.io/' }}" +matrix_appservice_discord_docker_image: "{{ matrix_appservice_discord_docker_image_registry_prefix }}matrix-org/matrix-appservice-discord:{{ matrix_appservice_discord_version }}" +matrix_appservice_discord_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_discord_container_image_self_build else matrix_appservice_discord_docker_image_registry_prefix_upstream }}" +matrix_appservice_discord_docker_image_registry_prefix_upstream: "{{ matrix_appservice_discord_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_discord_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_appservice_discord_docker_image_force_pull: "{{ matrix_appservice_discord_docker_image.endswith(':latest') }}" matrix_appservice_discord_base_path: "{{ matrix_base_data_path }}/appservice-discord" diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml index 8b9d1d160..033a8b337 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml @@ -22,6 +22,7 @@ when: "item.old in vars" with_items: - {'old': 'matrix_appservice_discord_container_expose_client_server_api_port', 'new': ''} + - {'old': 'matrix_appservice_discord_container_image_name_prefix', 'new': 'matrix_appservice_discord_docker_image_registry_prefix'} - name: Require a valid database engine ansible.builtin.fail: diff --git a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml index 534cac9f0..22f166857 100644 --- a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml @@ -14,10 +14,11 @@ matrix_appservice_irc_docker_src_files_path: "{{ matrix_base_data_path }}/appser # renovate: datasource=docker depName=docker.io/matrixdotorg/matrix-appservice-irc matrix_appservice_irc_version: 1.0.1 matrix_appservice_irc_docker_image: "{{ matrix_appservice_irc_docker_image_registry_prefix }}matrixdotorg/matrix-appservice-irc:{{ matrix_appservice_irc_docker_image_tag }}" -matrix_appservice_irc_docker_image_registry_prefix: docker.io/ +matrix_appservice_irc_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_irc_container_image_self_build else matrix_appservice_irc_docker_image_registry_prefix_upstream }}" +matrix_appservice_irc_docker_image_registry_prefix_upstream: "{{ matrix_appservice_irc_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_irc_docker_image_registry_prefix_upstream_default: docker.io/ matrix_appservice_irc_docker_image_tag: "{{ 'latest' if matrix_appservice_irc_version == 'latest' else ('release-' + matrix_appservice_irc_version) }}" matrix_appservice_irc_docker_image_force_pull: "{{ matrix_appservice_irc_docker_image.endswith(':latest') }}" -matrix_appservice_irc_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_irc_container_image_self_build else 'docker.io/' }}" matrix_appservice_irc_base_path: "{{ matrix_base_data_path }}/appservice-irc" matrix_appservice_irc_config_path: "{{ matrix_appservice_irc_base_path }}/config" diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml index 5d76def1b..f8dcf76ab 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml @@ -37,3 +37,4 @@ with_items: - {'old': 'matrix_appservice_irc_container_expose_client_server_api_port', 'new': ''} - {'old': 'matrix_appservice_irc_container_self_build', 'new': 'matrix_appservice_irc_container_image_self_build'} + - {'old': 'matrix_appservice_irc_docker_image_name_prefix', 'new': 'matrix_appservice_irc_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml index 09d6daa2b..1f628eef4 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml @@ -29,13 +29,17 @@ matrix_appservice_kakaotalk_container_image_self_build_repo: "https://src.miscwo matrix_appservice_kakaotalk_container_image_self_build_repo_version: "{{ 'master' if matrix_appservice_kakaotalk_version == 'latest' else matrix_appservice_kakaotalk_version }}" matrix_appservice_kakaotalk_node_version: "{{ matrix_appservice_kakaotalk_version }}" -matrix_appservice_kakaotalk_node_docker_image: "{{ matrix_appservice_kakaotalk_node_docker_image_prefix }}fair/matrix-appservice-kakaotalk-node:{{ matrix_appservice_kakaotalk_node_version }}" -matrix_appservice_kakaotalk_node_docker_image_prefix: "localhost/" +matrix_appservice_kakaotalk_node_docker_image: "{{ matrix_appservice_kakaotalk_node_docker_image_registry_prefix }}fair/matrix-appservice-kakaotalk-node:{{ matrix_appservice_kakaotalk_node_version }}" +matrix_appservice_kakaotalk_node_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_kakaotalk_container_image_self_build else matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream }}" +matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream: "{{ matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream_default: "" matrix_appservice_kakaotalk_node_docker_image_force_pull: "{{ matrix_appservice_kakaotalk_node_docker_image.endswith(':latest') }}" matrix_appservice_kakaotalk_version: 86c038fd2ffee5e0aebf65136f085cce7e38b54e -matrix_appservice_kakaotalk_docker_image: "{{ matrix_appservice_kakaotalk_docker_image_name_prefix }}fair/matrix-appservice-kakaotalk:{{ matrix_appservice_kakaotalk_version }}" -matrix_appservice_kakaotalk_docker_image_name_prefix: "localhost/" +matrix_appservice_kakaotalk_docker_image: "{{ matrix_appservice_kakaotalk_docker_image_registry_prefix }}fair/matrix-appservice-kakaotalk:{{ matrix_appservice_kakaotalk_version }}" +matrix_appservice_kakaotalk_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_kakaotalk_container_image_self_build else matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream }}" +matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream: "{{ matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream_default: "" matrix_appservice_kakaotalk_docker_image_force_pull: "{{ matrix_appservice_kakaotalk_docker_image.endswith(':latest') }}" matrix_appservice_kakaotalk_base_path: "{{ matrix_base_data_path }}/appservice-kakaotalk" diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml index bcb670146..20da0206e 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml @@ -11,3 +11,13 @@ - {'name': 'matrix_appservice_kakaotalk_homeserver_token', when: true} - {'name': 'matrix_appservice_kakaotalk_database_hostname', when: "{{ matrix_appservice_kakaotalk_database_engine == 'postgres' }}"} - {'name': 'matrix_appservice_kakaotalk_container_network', when: true} + +- name: (Deprecation) Catch and report renamed appservice-kakaotalk variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_appservice_kakaotalk_node_docker_image_name_prefix', 'new': 'matrix_appservice_kakaotalk_node_docker_image_registry_prefix'} + - {'old': 'matrix_appservice_kakaotalk_docker_image_name_prefix', 'new': 'matrix_appservice_kakaotalk_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml index 195106cee..abc875cc2 100644 --- a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml @@ -18,7 +18,9 @@ matrix_appservice_slack_docker_src_files_path: "{{ matrix_base_data_path }}/apps # renovate: datasource=docker depName=docker.io/matrixdotorg/matrix-appservice-slack matrix_appservice_slack_version: 2.1.2 matrix_appservice_slack_docker_image: "{{ matrix_appservice_slack_docker_image_registry_prefix }}matrixdotorg/matrix-appservice-slack:{{ matrix_appservice_slack_docker_image_tag }}" -matrix_appservice_slack_docker_image_registry_prefix: docker.io/ +matrix_appservice_slack_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_slack_container_image_self_build else matrix_appservice_slack_docker_image_registry_prefix_upstream }}" +matrix_appservice_slack_docker_image_registry_prefix_upstream: "{{ matrix_appservice_slack_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_slack_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_appservice_slack_docker_image_tag: "{{ 'latest' if matrix_appservice_slack_version == 'latest' else ('release-' + matrix_appservice_slack_version) }}" matrix_appservice_slack_docker_image_force_pull: "{{ matrix_appservice_slack_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml index 226c893d0..2a46e2a14 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml @@ -14,8 +14,10 @@ matrix_appservice_webhooks_container_image_self_build_repo_version: "{{ 'master' matrix_appservice_webhooks_container_image_self_build_repo_dockerfile_path: "Dockerfile" matrix_appservice_webhooks_version: v1.0.3-01 -matrix_appservice_webhooks_docker_image: "{{ matrix_appservice_webhooks_docker_image_name_prefix }}redoonetworks/matrix-appservice-webhooks:{{ matrix_appservice_webhooks_version }}" -matrix_appservice_webhooks_docker_image_name_prefix: "{{ 'localhost/' if matrix_appservice_webhooks_container_image_self_build else 'docker.io/' }}" +matrix_appservice_webhooks_docker_image: "{{ matrix_appservice_webhooks_docker_image_registry_prefix }}redoonetworks/matrix-appservice-webhooks:{{ matrix_appservice_webhooks_version }}" +matrix_appservice_webhooks_docker_image_registry_prefix: "{{ 'localhost/' if matrix_appservice_webhooks_container_image_self_build else matrix_appservice_webhooks_docker_image_registry_prefix_upstream }}" +matrix_appservice_webhooks_docker_image_registry_prefix_upstream: "{{ matrix_appservice_webhooks_docker_image_registry_prefix_upstream_default }}" +matrix_appservice_webhooks_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_appservice_webhooks_docker_image_force_pull: "{{ matrix_appservice_webhooks_docker_image.endswith(':latest') }}" matrix_appservice_webhooks_base_path: "{{ matrix_base_data_path }}/appservice-webhooks" diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml index fa8a75fc2..0a8bee983 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml @@ -14,3 +14,12 @@ - matrix_appservice_webhooks_container_network - matrix_appservice_webhooks_hostname - matrix_appservice_webhooks_path_prefix + +- name: (Deprecation) Catch and report renamed appservice-webhooks variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_appservice_webhooks_docker_image_name_prefix', 'new': 'matrix_appservice_webhooks_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml index fcba1e9b6..873e9be95 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml @@ -8,9 +8,11 @@ matrix_beeper_linkedin_enabled: true matrix_beeper_linkedin_version: latest # See: https://github.com/beeper/linkedin/pkgs/container/linkedin -matrix_beeper_linkedin_docker_image: "{{ matrix_beeper_linkedin_docker_image_name_prefix }}beeper/linkedin:{{ matrix_beeper_linkedin_docker_image_tag }}" +matrix_beeper_linkedin_docker_image: "{{ matrix_beeper_linkedin_docker_image_registry_prefix }}beeper/linkedin:{{ matrix_beeper_linkedin_docker_image_tag }}" matrix_beeper_linkedin_docker_image_force_pull: "{{ matrix_beeper_linkedin_docker_image_tag.startswith('latest') }}" -matrix_beeper_linkedin_docker_image_name_prefix: "{{ 'localhost/' if matrix_beeper_linkedin_container_image_self_build else 'ghcr.io/' }}" +matrix_beeper_linkedin_docker_image_registry_prefix: "{{ 'localhost/' if matrix_beeper_linkedin_container_image_self_build else matrix_beeper_linkedin_docker_image_registry_prefix_upstream }}" +matrix_beeper_linkedin_docker_image_registry_prefix_upstream: "{{ matrix_beeper_linkedin_docker_image_registry_prefix_upstream_default }}" +matrix_beeper_linkedin_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_beeper_linkedin_docker_image_tag: "{{ 'latest' if matrix_beeper_linkedin_version == 'master' else matrix_beeper_linkedin_version }}" matrix_beeper_linkedin_container_image_self_build: false diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml index cbf77eb71..dc87a45e7 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml @@ -20,3 +20,4 @@ when: "item.old in vars" with_items: - {'old': 'matrix_beeper_linkedin_login_shared_secret', 'new': ''} + - {'old': 'matrix_beeper_linkedin_docker_image_name_prefix', 'new': 'matrix_beeper_linkedin_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml index 7b8b8c732..de0e0ed7d 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml @@ -10,8 +10,10 @@ matrix_go_skype_bridge_container_image_self_build_branch: "{{ 'master' if matrix # renovate: datasource=docker depName=nodefyme/go-skype-bridge matrix_go_skype_bridge_version: latest -matrix_go_skype_bridge_docker_image: "{{ matrix_go_skype_bridge_docker_image_name_prefix }}nodefyme/go-skype-bridge:{{ matrix_go_skype_bridge_version }}" -matrix_go_skype_bridge_docker_image_name_prefix: "{{ 'localhost/' if matrix_go_skype_bridge_container_image_self_build else 'docker.io/' }}" +matrix_go_skype_bridge_docker_image: "{{ matrix_go_skype_bridge_docker_image_registry_prefix }}nodefyme/go-skype-bridge:{{ matrix_go_skype_bridge_version }}" +matrix_go_skype_bridge_docker_image_registry_prefix: "{{ 'localhost/' if matrix_go_skype_bridge_container_image_self_build else matrix_go_skype_bridge_docker_image_registry_prefix_upstream }}" +matrix_go_skype_bridge_docker_image_registry_prefix_upstream: "{{ matrix_go_skype_bridge_docker_image_registry_prefix_upstream_default }}" +matrix_go_skype_bridge_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_go_skype_bridge_docker_image_force_pull: "{{ matrix_go_skype_bridge_docker_image.endswith(':latest') }}" matrix_go_skype_bridge_base_path: "{{ matrix_base_data_path }}/go-skype-bridge" diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml index 9afe48f6e..7c3f00a18 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml @@ -11,3 +11,12 @@ - {'name': 'matrix_go_skype_bridge_homeserver_token', when: true} - {'name': 'matrix_go_skype_bridge_database_hostname', when: "{{ matrix_go_skype_bridge_database_engine == 'postgres' }}"} - {'name': 'matrix_go_skype_bridge_container_network', when: true} + +- name: (Deprecation) Catch and report renamed go-skype-bridge variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_go_skype_bridge_docker_image_name_prefix', 'new': 'matrix_go_skype_bridge_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml index a6a34c444..c39c20c68 100644 --- a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml @@ -11,7 +11,9 @@ matrix_heisenbridge_path_prefix: "/heisenbridge" # renovate: datasource=docker depName=hif1/heisenbridge matrix_heisenbridge_version: 1.15.0 matrix_heisenbridge_docker_image: "{{ matrix_heisenbridge_docker_image_registry_prefix }}hif1/heisenbridge:{{ matrix_heisenbridge_version }}" -matrix_heisenbridge_docker_image_registry_prefix: docker.io/ +matrix_heisenbridge_docker_image_registry_prefix: "{{ matrix_heisenbridge_docker_image_registry_prefix_upstream }}" +matrix_heisenbridge_docker_image_registry_prefix_upstream: "{{ matrix_heisenbridge_docker_image_registry_prefix_upstream_default }}" +matrix_heisenbridge_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_heisenbridge_docker_image_force_pull: "{{ matrix_heisenbridge_docker_image.endswith(':latest') }}" # Set this to your Matrix ID if you want to enforce the owner, otherwise first _local_ user becomes one diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index f4538e143..5483890ec 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -19,8 +19,10 @@ matrix_hookshot_container_additional_networks_custom: [] # renovate: datasource=docker depName=halfshot/matrix-hookshot matrix_hookshot_version: 6.0.2 -matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_name_prefix }}matrix-org/matrix-hookshot:{{ matrix_hookshot_version }}" -matrix_hookshot_docker_image_name_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else 'ghcr.io/' }}" +matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_registry_prefix }}matrix-org/matrix-hookshot:{{ matrix_hookshot_version }}" +matrix_hookshot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else matrix_hookshot_docker_image_registry_prefix_upstream }}" +matrix_hookshot_docker_image_registry_prefix_upstream: "{{ matrix_hookshot_docker_image_registry_prefix_upstream_default }}" +matrix_hookshot_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_hookshot_docker_image_force_pull: "{{ matrix_hookshot_docker_image.endswith(':latest') }}" matrix_hookshot_base_path: "{{ matrix_base_data_path }}/hookshot" diff --git a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml index de961c186..760fd8048 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml @@ -32,6 +32,7 @@ - {'old': 'matrix_hookshot_queue_host', 'new': 'matrix_hookshot_cache_redis_host'} - {'old': 'matrix_hookshot_queue_port', 'new': 'matrix_hookshot_cache_redis_port'} - {'old': 'matrix_hookshot_experimental_encryption_enabled', 'new': 'matrix_hookshot_encryption_enabled'} + - {'old': 'matrix_hookshot_docker_image_name_prefix', 'new': 'matrix_hookshot_docker_image_registry_prefix'} - name: Fail if required Hookshot settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml index 1d159496b..2fb7c44f2 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml @@ -11,8 +11,10 @@ matrix_mautrix_bluesky_container_image_self_build_repo_version: "{{ 'master' if # renovate: datasource=docker depName=dock.mau.dev/mautrix/bluesky matrix_mautrix_bluesky_version: v0.1.0 # See: https://mau.dev/tulir/mautrix-bluesky/container_registry -matrix_mautrix_bluesky_docker_image: "{{ matrix_mautrix_bluesky_docker_image_name_prefix }}mautrix/bluesky:{{ matrix_mautrix_bluesky_version }}" -matrix_mautrix_bluesky_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_bluesky_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_bluesky_docker_image: "{{ matrix_mautrix_bluesky_docker_image_registry_prefix }}mautrix/bluesky:{{ matrix_mautrix_bluesky_version }}" +matrix_mautrix_bluesky_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_bluesky_container_image_self_build else matrix_mautrix_bluesky_docker_image_registry_prefix_upstream }}" +matrix_mautrix_bluesky_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_bluesky_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_bluesky_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_bluesky_docker_image_force_pull: "{{ matrix_mautrix_bluesky_docker_image.endswith(':latest') }}" matrix_mautrix_bluesky_base_path: "{{ matrix_base_data_path }}/mautrix-bluesky" diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml index acd3c30cd..23e433d33 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml @@ -13,3 +13,12 @@ - {'name': 'matrix_mautrix_bluesky_container_network', when: true} - {'name': 'matrix_mautrix_bluesky_metrics_proxying_hostname', when: "{{ matrix_mautrix_bluesky_metrics_proxying_enabled }}"} - {'name': 'matrix_mautrix_bluesky_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_bluesky_metrics_proxying_enabled }}"} + +- name: (Deprecation) Catch and report renamed mautrix-bluesky variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_mautrix_bluesky_docker_image_name_prefix', 'new': 'matrix_mautrix_bluesky_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index 63a40c07f..b6486ed0c 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -16,8 +16,10 @@ matrix_mautrix_discord_container_image_self_build_branch: "{{ 'main' if matrix_m matrix_mautrix_discord_version: v0.7.2 # See: https://mau.dev/mautrix/discord/container_registry -matrix_mautrix_discord_docker_image: "{{ matrix_mautrix_discord_docker_image_name_prefix }}mautrix/discord:{{ matrix_mautrix_discord_version }}" -matrix_mautrix_discord_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_discord_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_discord_docker_image: "{{ matrix_mautrix_discord_docker_image_registry_prefix }}mautrix/discord:{{ matrix_mautrix_discord_version }}" +matrix_mautrix_discord_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_discord_container_image_self_build else matrix_mautrix_discord_docker_image_registry_prefix_upstream }}" +matrix_mautrix_discord_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_discord_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_discord_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_discord_docker_image_force_pull: "{{ matrix_mautrix_discord_docker_image.endswith(':latest') }}" matrix_mautrix_discord_base_path: "{{ matrix_base_data_path }}/mautrix-discord" diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml index 25b4773c9..ed04f643b 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml @@ -15,7 +15,7 @@ - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_hostname', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"} - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"} -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-discord settings ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -25,3 +25,4 @@ - {'old': 'matrix_mautrix_discord_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_discord_homeserver_public_address', 'new': 'matrix_mautrix_discord_bridge_public_address'} - {'old': 'matrix_mautrix_discord_command_prefix', 'new': 'matrix_mautrix_discord_bridge_command_prefix'} + - {'old': 'matrix_mautrix_discord_docker_image_name_prefix', 'new': 'matrix_mautrix_discord_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml index dacd2e24a..ce448c1bc 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml @@ -9,8 +9,10 @@ matrix_mautrix_facebook_container_image_self_build_repo: "https://mau.dev/mautri # renovate: datasource=docker depName=dock.mau.dev/mautrix/facebook matrix_mautrix_facebook_version: v0.5.1 -matrix_mautrix_facebook_docker_image: "{{ matrix_mautrix_facebook_docker_image_name_prefix }}mautrix/facebook:{{ matrix_mautrix_facebook_version }}" -matrix_mautrix_facebook_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_facebook_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_facebook_docker_image: "{{ matrix_mautrix_facebook_docker_image_registry_prefix }}mautrix/facebook:{{ matrix_mautrix_facebook_version }}" +matrix_mautrix_facebook_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_facebook_container_image_self_build else matrix_mautrix_facebook_docker_image_registry_prefix_upstream }}" +matrix_mautrix_facebook_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_facebook_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_facebook_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_facebook_docker_image_force_pull: "{{ matrix_mautrix_facebook_docker_image.endswith(':latest') }}" matrix_mautrix_facebook_base_path: "{{ matrix_base_data_path }}/mautrix-facebook" diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml index 72961cb0e..12286f320 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml @@ -8,6 +8,7 @@ when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_facebook_public_endpoint', 'new': 'matrix_mautrix_facebook_appservice_public_prefix'} + - {'old': 'matrix_mautrix_facebook_docker_image_name_prefix', 'new': 'matrix_mautrix_facebook_docker_image_registry_prefix'} - name: Fail if required mautrix-facebook settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml index c2409ec61..46b1e3099 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml @@ -12,8 +12,10 @@ matrix_mautrix_gmessages_container_image_self_build_branch: "{{ 'main' if matrix matrix_mautrix_gmessages_version: v0.6.0 # See: https://mau.dev/mautrix/gmessages/container_registry -matrix_mautrix_gmessages_docker_image: "{{ matrix_mautrix_gmessages_docker_image_name_prefix }}mautrix/gmessages:{{ matrix_mautrix_gmessages_version }}" -matrix_mautrix_gmessages_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_gmessages_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_gmessages_docker_image: "{{ matrix_mautrix_gmessages_docker_image_registry_prefix }}mautrix/gmessages:{{ matrix_mautrix_gmessages_version }}" +matrix_mautrix_gmessages_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_gmessages_container_image_self_build else matrix_mautrix_gmessages_docker_image_registry_prefix_upstream }}" +matrix_mautrix_gmessages_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_gmessages_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_gmessages_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_gmessages_docker_image_force_pull: "{{ matrix_mautrix_gmessages_docker_image.endswith(':latest') }}" matrix_mautrix_gmessages_base_path: "{{ matrix_base_data_path }}/mautrix-gmessages" diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml index 7f2510a1f..1358465e5 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml @@ -25,3 +25,4 @@ - {'old': 'matrix_mautrix_gmessages_bridge_mute_bridging', 'new': ''} - {'old': 'matrix_mautrix_gmessages_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_gmessages_bridge_login_shared_secret_map', 'new': 'matrix_mautrix_gmessages_double_puppet_secrets_custom'} + - {'old': 'matrix_mautrix_gmessages_docker_image_name_prefix', 'new': 'matrix_mautrix_gmessages_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml index f9ff35681..50d991dd5 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml @@ -11,8 +11,10 @@ matrix_mautrix_googlechat_container_image_self_build_repo_version: "{{ 'master' # renovate: datasource=docker depName=dock.mau.dev/mautrix/googlechat matrix_mautrix_googlechat_version: v0.5.2 # See: https://mau.dev/mautrix/googlechat/container_registry -matrix_mautrix_googlechat_docker_image: "{{ matrix_mautrix_googlechat_docker_image_name_prefix }}mautrix/googlechat:{{ matrix_mautrix_googlechat_version }}" -matrix_mautrix_googlechat_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_googlechat_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_googlechat_docker_image: "{{ matrix_mautrix_googlechat_docker_image_registry_prefix }}mautrix/googlechat:{{ matrix_mautrix_googlechat_version }}" +matrix_mautrix_googlechat_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_googlechat_container_image_self_build else matrix_mautrix_googlechat_docker_image_registry_prefix_upstream }}" +matrix_mautrix_googlechat_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_googlechat_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_googlechat_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_googlechat_docker_image_force_pull: "{{ matrix_mautrix_googlechat_docker_image.endswith(':latest') }}" matrix_mautrix_googlechat_base_path: "{{ matrix_base_data_path }}/mautrix-googlechat" diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml index 9c8e79d1e..b6543a188 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml @@ -16,3 +16,12 @@ - {'name': 'matrix_mautrix_googlechat_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_googlechat_metrics_proxying_enabled }}"} - {'name': 'matrix_mautrix_googlechat_container_labels_public_endpoint_hostname', when: "{{ matrix_mautrix_googlechat_container_labels_public_endpoint_enabled }}"} - {'name': 'matrix_mautrix_googlechat_container_labels_public_endpoint_path_prefix', when: "{{ matrix_mautrix_googlechat_container_labels_public_endpoint_enabled }}"} + +- name: (Deprecation) Catch and report renamed mautrix-googlechat variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_mautrix_googlechat_docker_image_name_prefix', 'new': 'matrix_mautrix_googlechat_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml index 566a01bb5..ad0a2a00a 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml @@ -11,8 +11,10 @@ matrix_mautrix_instagram_container_image_self_build_repo_version: "{{ 'master' i # renovate: datasource=docker depName=dock.mau.dev/mautrix/instagram matrix_mautrix_instagram_version: v0.3.1 # See: https://mau.dev/tulir/mautrix-instagram/container_registry -matrix_mautrix_instagram_docker_image: "{{ matrix_mautrix_instagram_docker_image_name_prefix }}mautrix/instagram:{{ matrix_mautrix_instagram_version }}" -matrix_mautrix_instagram_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_instagram_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_instagram_docker_image: "{{ matrix_mautrix_instagram_docker_image_registry_prefix }}mautrix/instagram:{{ matrix_mautrix_instagram_version }}" +matrix_mautrix_instagram_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_instagram_container_image_self_build else matrix_mautrix_instagram_docker_image_registry_prefix_upstream }}" +matrix_mautrix_instagram_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_instagram_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_instagram_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_instagram_docker_image_force_pull: "{{ matrix_mautrix_instagram_docker_image.endswith(':latest') }}" matrix_mautrix_instagram_base_path: "{{ matrix_base_data_path }}/mautrix-instagram" diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml index 1a0c1cda7..72a97f9bd 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml @@ -12,3 +12,12 @@ - {'name': 'matrix_mautrix_instagram_database_hostname', when: "{{ matrix_mautrix_instagram_database_engine == 'postgres' }}"} - {'name': 'matrix_mautrix_instagram_metrics_proxying_hostname', when: "{{ matrix_mautrix_instagram_metrics_proxying_enabled }}"} - {'name': 'matrix_mautrix_instagram_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_instagram_metrics_proxying_enabled }}"} + +- name: (Deprecation) Catch and report renamed mautrix-instagram variables + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_mautrix_instagram_docker_image_name_prefix', 'new': 'matrix_mautrix_instagram_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml index a4f6abf90..006fcda7e 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml @@ -23,8 +23,10 @@ matrix_mautrix_meta_instagram_container_src_files_path: "{{ matrix_mautrix_meta_ matrix_mautrix_meta_instagram_container_image_self_build: false matrix_mautrix_meta_instagram_container_image_self_build_repo: "https://github.com/mautrix/meta.git" -matrix_mautrix_meta_instagram_container_image: "{{ matrix_mautrix_meta_instagram_container_image_name_prefix }}mautrix/meta:{{ matrix_mautrix_meta_instagram_container_image_tag }}" -matrix_mautrix_meta_instagram_container_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_meta_instagram_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_meta_instagram_container_image: "{{ matrix_mautrix_meta_instagram_container_image_registry_prefix }}mautrix/meta:{{ matrix_mautrix_meta_instagram_container_image_tag }}" +matrix_mautrix_meta_instagram_container_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_meta_instagram_container_image_self_build else matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream }}" +matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream: "{{ matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream_default }}" +matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream_default: "dock.mau.dev/" # Prebuilt container images for specific commit hashes are tagged with an architecture suffix (e.g. `HASH-amd64`). matrix_mautrix_meta_instagram_container_image_tag: "{{ matrix_mautrix_meta_instagram_version }}{{ ('-' ~ matrix_architecture) if (matrix_mautrix_meta_instagram_version | length == 40) else '' }}" matrix_mautrix_meta_instagram_container_image_force_pull: "{{ matrix_mautrix_meta_instagram_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml index fbaa3da1c..212e261b8 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml @@ -15,7 +15,7 @@ - {'name': 'matrix_mautrix_meta_instagram_database_hostname', when: "{{ matrix_mautrix_meta_instagram_database_engine == 'postgres' }}"} - {'name': 'matrix_mautrix_meta_instagram_database_password', when: "{{ matrix_mautrix_meta_instagram_database_engine == 'postgres' }}"} -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-meta-instagram settings ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -25,3 +25,4 @@ - {'old': 'matrix_mautrix_meta_instagram_bridge_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_meta_instagram_bridge_login_shared_secret_map_custom', 'new': ''} - {'old': 'matrix_mautrix_meta_instagram_bridge_management_room_text_welcome', 'new': ''} + - {'old': 'matrix_mautrix_meta_instagram_container_image_name_prefix', 'new': 'matrix_mautrix_meta_instagram_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml index 1f4dc54be..d6f5debcb 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml @@ -23,8 +23,10 @@ matrix_mautrix_meta_messenger_container_src_files_path: "{{ matrix_mautrix_meta_ matrix_mautrix_meta_messenger_container_image_self_build: false matrix_mautrix_meta_messenger_container_image_self_build_repo: "https://github.com/mautrix/meta.git" -matrix_mautrix_meta_messenger_container_image: "{{ matrix_mautrix_meta_messenger_container_image_name_prefix }}mautrix/meta:{{ matrix_mautrix_meta_messenger_container_image_tag }}" -matrix_mautrix_meta_messenger_container_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_meta_messenger_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_meta_messenger_container_image: "{{ matrix_mautrix_meta_messenger_container_image_registry_prefix }}mautrix/meta:{{ matrix_mautrix_meta_messenger_container_image_tag }}" +matrix_mautrix_meta_messenger_container_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_meta_messenger_container_image_self_build else matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream }}" +matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream: "{{ matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream_default }}" +matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream_default: "dock.mau.dev/" # Prebuilt container images for specific commit hashes are tagged with an architecture suffix (e.g. `HASH-amd64`). matrix_mautrix_meta_messenger_container_image_tag: "{{ matrix_mautrix_meta_messenger_version }}{{ ('-' ~ matrix_architecture) if (matrix_mautrix_meta_messenger_version | length == 40) else '' }}" matrix_mautrix_meta_messenger_container_image_force_pull: "{{ matrix_mautrix_meta_messenger_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml index d9f40022f..2d69f924e 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml @@ -15,7 +15,7 @@ - {'name': 'matrix_mautrix_meta_messenger_database_hostname', when: "{{ matrix_mautrix_meta_messenger_database_engine == 'postgres' }}"} - {'name': 'matrix_mautrix_meta_messenger_database_password', when: "{{ matrix_mautrix_meta_messenger_database_engine == 'postgres' }}"} -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-meta-messenger variables ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -25,3 +25,4 @@ - {'old': 'matrix_mautrix_meta_messenger_bridge_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_meta_messenger_bridge_login_shared_secret_map_custom', 'new': ''} - {'old': 'matrix_mautrix_meta_messenger_bridge_management_room_text_welcome', 'new': ''} + - {'old': 'matrix_mautrix_meta_messenger_container_image_name_prefix', 'new': 'matrix_mautrix_meta_messenger_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index 53b5de4da..acd545817 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -12,9 +12,11 @@ matrix_mautrix_signal_container_image_self_build_branch: "{{ 'main' if matrix_ma matrix_mautrix_signal_version: v0.8.0 # See: https://mau.dev/mautrix/signal/container_registry -matrix_mautrix_signal_docker_image: "{{ matrix_mautrix_signal_docker_image_name_prefix }}mautrix/signal:{{ matrix_mautrix_signal_docker_image_tag }}" +matrix_mautrix_signal_docker_image: "{{ matrix_mautrix_signal_docker_image_registry_prefix }}mautrix/signal:{{ matrix_mautrix_signal_docker_image_tag }}" matrix_mautrix_signal_docker_image_tag: "{{ matrix_mautrix_signal_version }}" -matrix_mautrix_signal_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_signal_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_signal_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_signal_container_image_self_build else matrix_mautrix_signal_docker_image_registry_prefix_upstream }}" +matrix_mautrix_signal_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_signal_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_signal_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_signal_docker_image_force_pull: "{{ matrix_mautrix_signal_docker_image.endswith(':latest') }}" matrix_mautrix_signal_base_path: "{{ matrix_base_data_path }}/mautrix-signal" diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml index 702842e39..a3059ef83 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml @@ -14,7 +14,7 @@ - {'name': 'matrix_mautrix_signal_metrics_proxying_hostname', when: "{{ matrix_mautrix_signal_metrics_proxying_enabled }}"} - {'name': 'matrix_mautrix_signal_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_signal_metrics_proxying_enabled }}"} -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-signal variables ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -27,3 +27,4 @@ - {'old': 'matrix_mautrix_signal_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_signal_bridge_login_shared_secret_map', 'new': ''} - {'old': 'matrix_mautrix_signal_bridge_double_puppet_server_map', 'new': ''} + - {'old': 'matrix_mautrix_signal_docker_image_name_prefix', 'new': 'matrix_mautrix_signal_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml index bf5ed4bd0..9489385e7 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml @@ -11,8 +11,10 @@ matrix_mautrix_slack_container_image_self_build_branch: "{{ 'main' if matrix_mau # renovate: datasource=docker depName=dock.mau.dev/mautrix/slack matrix_mautrix_slack_version: v0.1.4 # See: https://mau.dev/mautrix/slack/container_registry -matrix_mautrix_slack_docker_image: "{{ matrix_mautrix_slack_docker_image_name_prefix }}mautrix/slack:{{ matrix_mautrix_slack_version }}" -matrix_mautrix_slack_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_slack_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_slack_docker_image: "{{ matrix_mautrix_slack_docker_image_registry_prefix }}mautrix/slack:{{ matrix_mautrix_slack_version }}" +matrix_mautrix_slack_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_slack_container_image_self_build else matrix_mautrix_slack_docker_image_registry_prefix_upstream }}" +matrix_mautrix_slack_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_slack_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_slack_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_slack_docker_image_force_pull: "{{ matrix_mautrix_slack_docker_image.endswith(':latest') }}" matrix_mautrix_slack_base_path: "{{ matrix_base_data_path }}/mautrix-slack" diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml index 19c51c61e..9a6e4a845 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml @@ -21,7 +21,7 @@ Consider either changing `matrix_mautrix_slack_appservice_bot_username` (the bot username for the mautrix-slack component) or `matrix_appservice_slack_bot_name` (the bot username for the appservice-slack component). We recommend that you change the username for the newly-added (and yet unused) component. -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-slack variables ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -31,3 +31,4 @@ - {'old': 'matrix_mautrix_slack_login_shared_secret', 'new': ''} - {'old': 'matrix_mautrix_slack_bridge_login_shared_secret_map', 'new': ''} - {'old': 'matrix_mautrix_slack_bridge_double_puppet_server_map', 'new': ''} + - {'old': 'matrix_mautrix_slack_docker_image_name_prefix', 'new': 'matrix_mautrix_slack_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml index 619dfee86..a876a6587 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml @@ -14,8 +14,10 @@ matrix_telegram_lottieconverter_container_image_self_build_mask_arch: false matrix_telegram_lottieconverter_docker_repo: "https://mau.dev/tulir/lottieconverter.git" matrix_telegram_lottieconverter_docker_repo_version: "master" matrix_telegram_lottieconverter_docker_src_files_path: "{{ matrix_base_data_path }}/lotticonverter/docker-src" -matrix_telegram_lottieconverter_docker_image: "{{ matrix_telegram_lottieconverter_docker_image_name_prefix }}tulir/lottieconverter:alpine-3.16" # needs to be adjusted according to the FROM clause of Dockerfile of mautrix-telegram -matrix_telegram_lottieconverter_docker_image_name_prefix: "{{ 'localhost/' if matrix_telegram_lottieconverter_container_image_self_build else 'dock.mau.dev/' }}" +matrix_telegram_lottieconverter_docker_image: "{{ matrix_telegram_lottieconverter_docker_image_registry_prefix }}tulir/lottieconverter:alpine-3.16" # needs to be adjusted according to the FROM clause of Dockerfile of mautrix-telegram +matrix_telegram_lottieconverter_docker_image_registry_prefix: "{{ 'localhost/' if matrix_telegram_lottieconverter_container_image_self_build else matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream }}" +matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream: "{{ matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default }}" +matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_telegram_container_image_self_build: false matrix_mautrix_telegram_docker_repo: "https://mau.dev/mautrix/telegram.git" @@ -25,8 +27,10 @@ matrix_mautrix_telegram_docker_src_files_path: "{{ matrix_base_data_path }}/maut # renovate: datasource=docker depName=dock.mau.dev/mautrix/telegram matrix_mautrix_telegram_version: v0.15.2 # See: https://mau.dev/mautrix/telegram/container_registry -matrix_mautrix_telegram_docker_image: "{{ matrix_mautrix_telegram_docker_image_name_prefix }}mautrix/telegram:{{ matrix_mautrix_telegram_version }}" -matrix_mautrix_telegram_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_telegram_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_telegram_docker_image: "{{ matrix_mautrix_telegram_docker_image_registry_prefix }}mautrix/telegram:{{ matrix_mautrix_telegram_version }}" +matrix_mautrix_telegram_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_telegram_container_image_self_build else matrix_mautrix_telegram_docker_image_registry_prefix_upstream }}" +matrix_mautrix_telegram_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_telegram_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_telegram_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_telegram_docker_image_force_pull: "{{ matrix_mautrix_telegram_docker_image.endswith(':latest') }}" matrix_mautrix_telegram_base_path: "{{ matrix_base_data_path }}/mautrix-telegram" diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml index 040d7da42..8db84dbd0 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml @@ -19,7 +19,7 @@ - {'name': 'matrix_mautrix_telegram_metrics_proxying_hostname', when: "{{ matrix_mautrix_telegram_metrics_proxying_enabled }}"} - {'name': 'matrix_mautrix_telegram_metrics_proxying_path_prefix', when: "{{ matrix_mautrix_telegram_metrics_proxying_enabled }}"} -- name: (Deprecation) Catch and report renamed Telegram variables +- name: (Deprecation) Catch and report renamed mautrix-telegram variables ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -31,3 +31,5 @@ - {'old': 'matrix_telegram_lottieconverter_container_self_build', 'new': 'matrix_mautrix_telegram_container_image_self_build'} - {'old': 'matrix_telegram_lottieconverter_container_self_build_mask_arch', 'new': 'matrix_telegram_lottieconverter_container_image_self_build_mask_arch'} - {'old': 'matrix_mautrix_telegram_login_shared_secret', 'new': ''} + - {'old': 'matrix_telegram_lottieconverter_docker_image_name_prefix', 'new': 'matrix_telegram_lottieconverter_docker_image_registry_prefix'} + - {'old': 'matrix_mautrix_telegram_docker_image_name_prefix', 'new': 'matrix_mautrix_telegram_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml index e79db967c..449d71eb3 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml @@ -11,8 +11,10 @@ matrix_mautrix_twitter_container_image_self_build_repo_version: "{{ 'master' if # renovate: datasource=docker depName=dock.mau.dev/mautrix/twitter matrix_mautrix_twitter_version: v0.2.1 # See: https://mau.dev/tulir/mautrix-twitter/container_registry -matrix_mautrix_twitter_docker_image: "{{ matrix_mautrix_twitter_docker_image_name_prefix }}mautrix/twitter:{{ matrix_mautrix_twitter_version }}" -matrix_mautrix_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_twitter_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_twitter_docker_image: "{{ matrix_mautrix_twitter_docker_image_registry_prefix }}mautrix/twitter:{{ matrix_mautrix_twitter_version }}" +matrix_mautrix_twitter_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_twitter_container_image_self_build else matrix_mautrix_twitter_docker_image_registry_prefix_upstream }}" +matrix_mautrix_twitter_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_twitter_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_twitter_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_twitter_docker_image_force_pull: "{{ matrix_mautrix_twitter_docker_image.endswith(':latest') }}" matrix_mautrix_twitter_base_path: "{{ matrix_base_data_path }}/mautrix-twitter" diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml index b63a61558..0e33dcae8 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml @@ -28,3 +28,4 @@ - {'old': 'matrix_mautrix_twitter_bridge_login_shared_secret_map_custom', 'new': 'matrix_mautrix_twitter_double_puppet_secrets_custom'} - {'old': 'matrix_mautrix_twitter_federate_rooms', 'new': 'matrix_mautrix_twitter_matrix_federate_rooms'} - {'old': 'matrix_mautrix_twitter_command_prefix', 'new': 'matrix_mautrix_twitter_bridge_command_prefix'} + - {'old': 'matrix_mautrix_twitter_docker_image_name_prefix', 'new': 'matrix_mautrix_twitter_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml index 4711262fa..5f3d36ee4 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml @@ -12,8 +12,10 @@ matrix_mautrix_whatsapp_container_image_self_build_branch: "{{ 'master' if matri matrix_mautrix_whatsapp_version: v0.11.3 # See: https://mau.dev/mautrix/whatsapp/container_registry -matrix_mautrix_whatsapp_docker_image: "{{ matrix_mautrix_whatsapp_docker_image_name_prefix }}mautrix/whatsapp:{{ matrix_mautrix_whatsapp_version }}" -matrix_mautrix_whatsapp_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_whatsapp_container_image_self_build else 'dock.mau.dev/' }}" +matrix_mautrix_whatsapp_docker_image: "{{ matrix_mautrix_whatsapp_docker_image_registry_prefix }}mautrix/whatsapp:{{ matrix_mautrix_whatsapp_version }}" +matrix_mautrix_whatsapp_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_whatsapp_container_image_self_build else matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream }}" +matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_whatsapp_docker_image_force_pull: "{{ matrix_mautrix_whatsapp_docker_image.endswith(':latest') }}" matrix_mautrix_whatsapp_base_path: "{{ matrix_base_data_path }}/mautrix-whatsapp" diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml index 220f99b15..21cd9fc09 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml @@ -11,7 +11,7 @@ - {'name': 'matrix_mautrix_whatsapp_homeserver_token', when: true} - {'name': 'matrix_mautrix_whatsapp_database_hostname', when: "{{ matrix_mautrix_whatsapp_database_engine == 'postgres' }}"} -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed mautrix-whatsapp variables ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -24,3 +24,4 @@ - {'old': 'matrix_mautrix_whatsapp_bridge_double_puppet_server_map', 'new': ''} - {'old': 'matrix_mautrix_whatsapp_bridge_allow_user_invite', 'new': ''} - {'old': 'matrix_mautrix_whatsapp_bridge_mute_bridging', 'new': ''} + - {'old': 'matrix_mautrix_whatsapp_docker_image_name_prefix', 'new': 'matrix_mautrix_whatsapp_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml index 51ad2a990..f9a514e9f 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml @@ -6,7 +6,10 @@ matrix_mautrix_wsproxy_enabled: true matrix_mautrix_wsproxy_version: latest # See: https://mau.dev/mautrix/wsproxy/container_registry -matrix_mautrix_wsproxy_docker_image: "dock.mau.dev/mautrix/wsproxy:{{ matrix_mautrix_wsproxy_version }}" +matrix_mautrix_wsproxy_docker_image: "{{ matrix_mautrix_wsproxy_docker_image_registry_prefix }}mautrix/wsproxy:{{ matrix_mautrix_wsproxy_version }}" +matrix_mautrix_wsproxy_docker_image_registry_prefix: "{{ matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream }}" +matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_wsproxy_docker_image_force_pull: "{{ matrix_mautrix_wsproxy_docker_image.endswith(':latest') }}" matrix_mautrix_wsproxy_base_path: "{{ matrix_base_data_path }}/wsproxy" diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml index d4284d0d5..966524ab4 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml @@ -28,8 +28,10 @@ matrix_mx_puppet_discord_container_http_host_bind_port: '' # renovate: datasource=docker depName=registry.gitlab.com/mx-puppet/discord/mx-puppet-discord matrix_mx_puppet_discord_version: v0.1.1 -matrix_mx_puppet_discord_docker_image: "{{ matrix_mx_puppet_discord_docker_image_name_prefix }}mx-puppet/discord/mx-puppet-discord:{{ matrix_mx_puppet_discord_version }}" -matrix_mx_puppet_discord_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_discord_container_image_self_build else 'registry.gitlab.com/' }}" +matrix_mx_puppet_discord_docker_image: "{{ matrix_mx_puppet_discord_docker_image_registry_prefix }}mx-puppet/discord/mx-puppet-discord:{{ matrix_mx_puppet_discord_version }}" +matrix_mx_puppet_discord_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mx_puppet_discord_container_image_self_build else matrix_mx_puppet_discord_docker_image_registry_prefix_upstream }}" +matrix_mx_puppet_discord_docker_image_registry_prefix_upstream: "{{ matrix_mx_puppet_discord_docker_image_registry_prefix_upstream_default }}" +matrix_mx_puppet_discord_docker_image_registry_prefix_upstream_default: "registry.gitlab.com/" matrix_mx_puppet_discord_docker_image_force_pull: "{{ matrix_mx_puppet_discord_docker_image.endswith(':latest') }}" matrix_mx_puppet_discord_base_path: "{{ matrix_base_data_path }}/mx-puppet-discord" diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml index 67bf4966f..d343fbba6 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2020 Hugues Morisset -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -16,3 +16,11 @@ - {'name': 'matrix_mx_puppet_discord_homeserver_token', when: true} - {'name': 'matrix_mx_puppet_discord_database_hostname', when: "{{ matrix_mx_puppet_discord_database_engine == 'postgres' }}"} - {'name': 'matrix_mx_puppet_discord_container_network', when: true} + +- name: (Deprecation) Catch and report renamed mx-puppet-discord variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_mx_puppet_discord_docker_image_name_prefix', 'new': 'matrix_mx_puppet_discord_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml index 3672be8ce..2487ab7d7 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2021 Cody Neiman # SPDX-FileCopyrightText: 2021 MDAD project contributors -# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi @@ -25,8 +25,10 @@ matrix_mx_puppet_groupme_container_image_self_build_repo_version: "{{ 'main' if matrix_mx_puppet_groupme_container_http_host_bind_port: '' matrix_mx_puppet_groupme_version: 533cccc8 -matrix_mx_puppet_groupme_docker_image: "{{ matrix_mx_puppet_groupme_docker_image_name_prefix }}xangelix-pub/matrix/mx-puppet-groupme:{{ matrix_mx_puppet_groupme_version }}" -matrix_mx_puppet_groupme_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_groupme_container_image_self_build else 'registry.gitlab.com/' }}" +matrix_mx_puppet_groupme_docker_image: "{{ matrix_mx_puppet_groupme_docker_image_registry_prefix }}xangelix-pub/matrix/mx-puppet-groupme:{{ matrix_mx_puppet_groupme_version }}" +matrix_mx_puppet_groupme_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mx_puppet_groupme_container_image_self_build else matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream }}" +matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream: "{{ matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream_default }}" +matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream_default: "registry.gitlab.com/" matrix_mx_puppet_groupme_docker_image_force_pull: "{{ matrix_mx_puppet_groupme_docker_image.endswith(':latest') }}" matrix_mx_puppet_groupme_base_path: "{{ matrix_base_data_path }}/mx-puppet-groupme" diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml index a5cce9efa..8d195daff 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2021 Cody Neiman -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -16,3 +16,11 @@ - {'name': 'matrix_mx_puppet_groupme_homeserver_token', when: true} - {'name': 'matrix_mx_puppet_groupme_database_hostname', when: "{{ matrix_mx_puppet_groupme_database_engine == 'postgres' }}"} - {'name': 'matrix_mx_puppet_groupme_container_network', when: true} + +- name: (Deprecation) Catch and report renamed mx-puppet-groupme variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_mx_puppet_groupme_docker_image_name_prefix', 'new': 'matrix_mx_puppet_groupme_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml index 78ea2ad33..14568af1a 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml @@ -20,8 +20,10 @@ matrix_mx_puppet_instagram_container_image_self_build_repo_version: "{{ 'master' # renovate: datasource=docker depName=sorunome/mx-puppet-instagram matrix_mx_puppet_instagram_version: latest -matrix_mx_puppet_instagram_docker_image: "{{ matrix_mx_puppet_instagram_docker_image_name_prefix }}sorunome/mx-puppet-instagram:{{ matrix_mx_puppet_instagram_version }}" -matrix_mx_puppet_instagram_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_instagram_container_image_self_build else 'docker.io/' }}" +matrix_mx_puppet_instagram_docker_image: "{{ matrix_mx_puppet_instagram_docker_image_registry_prefix }}sorunome/mx-puppet-instagram:{{ matrix_mx_puppet_instagram_version }}" +matrix_mx_puppet_instagram_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mx_puppet_instagram_container_image_self_build else matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream }}" +matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream: "{{ matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream_default }}" +matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_mx_puppet_instagram_docker_image_force_pull: "{{ matrix_mx_puppet_instagram_docker_image.endswith(':latest') }}" matrix_mx_puppet_instagram_base_path: "{{ matrix_base_data_path }}/mx-puppet-instagram" diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml index 2cd23b9c5..13a9fbf7d 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2020 MDAD project contributors -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -16,3 +16,11 @@ - {'name': 'matrix_mx_puppet_instagram_homeserver_token', when: true} - {'name': 'matrix_mx_puppet_instagram_database_hostname', when: "{{ matrix_mx_puppet_instagram_database_engine == 'postgres' }}"} - {'name': 'matrix_mx_puppet_instagram_container_network', when: true} + +- name: (Deprecation) Catch and report renamed mx-puppet-instagram variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_mx_puppet_instagram_docker_image_name_prefix', 'new': 'matrix_mx_puppet_instagram_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml index fd71a20c5..4b4eb76eb 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml @@ -38,8 +38,10 @@ matrix_mx_puppet_slack_container_http_host_bind_port: '' # renovate: datasource=docker depName=registry.gitlab.com/mx-puppet/slack/mx-puppet-slack matrix_mx_puppet_slack_version: v0.1.2 -matrix_mx_puppet_slack_docker_image: "{{ matrix_mx_puppet_slack_docker_image_name_prefix }}mx-puppet/slack/mx-puppet-slack:{{ matrix_mx_puppet_slack_version }}" -matrix_mx_puppet_slack_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_slack_container_image_self_build else 'registry.gitlab.com/' }}" +matrix_mx_puppet_slack_docker_image: "{{ matrix_mx_puppet_slack_docker_image_registry_prefix }}mx-puppet/slack/mx-puppet-slack:{{ matrix_mx_puppet_slack_version }}" +matrix_mx_puppet_slack_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mx_puppet_slack_container_image_self_build else matrix_mx_puppet_slack_docker_image_registry_prefix_upstream }}" +matrix_mx_puppet_slack_docker_image_registry_prefix_upstream: "{{ matrix_mx_puppet_slack_docker_image_registry_prefix_upstream_default }}" +matrix_mx_puppet_slack_docker_image_registry_prefix_upstream_default: "registry.gitlab.com/" matrix_mx_puppet_slack_docker_image_force_pull: "{{ matrix_mx_puppet_slack_docker_image.endswith(':latest') }}" matrix_mx_puppet_slack_base_path: "{{ matrix_base_data_path }}/mx-puppet-slack" diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml index 0299dcdfe..fd67a1c80 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2020 Rodrigo Belem -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -28,3 +28,4 @@ with_items: - {'old': 'matrix_mx_puppet_slack_redirect_path', 'new': 'matrix_mx_puppet_slack_oauth_redirect_path, but setting matrix_mx_puppet_slack_path_prefix is better'} - {'old': 'matrix_mx_puppet_slack_redirect_uri', 'new': '- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_mx_puppet_steam_docker_image_name_prefix', 'new': 'matrix_mx_puppet_steam_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml index 7dfded3d7..2b8f40c97 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml @@ -30,8 +30,10 @@ matrix_mx_puppet_twitter_container_http_host_bind_port: '' # renovate: datasource=docker depName=sorunome/mx-puppet-twitter matrix_mx_puppet_twitter_version: latest -matrix_mx_puppet_twitter_docker_image: "{{ matrix_mx_puppet_twitter_docker_image_name_prefix }}sorunome/mx-puppet-twitter:{{ matrix_mx_puppet_twitter_version }}" -matrix_mx_puppet_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mx_puppet_twitter_container_image_self_build else 'docker.io/' }}" +matrix_mx_puppet_twitter_docker_image: "{{ matrix_mx_puppet_twitter_docker_image_registry_prefix }}sorunome/mx-puppet-twitter:{{ matrix_mx_puppet_twitter_version }}" +matrix_mx_puppet_twitter_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mx_puppet_twitter_container_image_self_build else matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream }}" +matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream: "{{ matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream_default }}" +matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_mx_puppet_twitter_docker_image_force_pull: "{{ matrix_mx_puppet_twitter_docker_image.endswith(':latest') }}" matrix_mx_puppet_twitter_base_path: "{{ matrix_base_data_path }}/mx-puppet-twitter" diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml index 07584ac85..132984974 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2020 Tulir Asokan -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -28,3 +28,4 @@ with_items: - {'old': 'matrix_mx_puppet_twitter_webhook_path', 'new': '- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_postmoogle_docker_image_name_prefix', 'new': 'matrix_postmoogle_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-sms/defaults/main.yml b/roles/custom/matrix-bridge-sms/defaults/main.yml index 2cabe39b5..4dc5b4268 100644 --- a/roles/custom/matrix-bridge-sms/defaults/main.yml +++ b/roles/custom/matrix-bridge-sms/defaults/main.yml @@ -7,7 +7,9 @@ matrix_sms_bridge_enabled: true # renovate: datasource=docker depName=folivonet/matrix-sms-bridge matrix_sms_bridge_version: 0.5.9 matrix_sms_bridge_docker_image: "{{ matrix_sms_bridge_docker_image_registry_prefix }}folivonet/matrix-sms-bridge:{{ matrix_sms_bridge_docker_image_tag }}" -matrix_sms_bridge_docker_image_registry_prefix: docker.io/ +matrix_sms_bridge_docker_image_registry_prefix: "{{ matrix_sms_bridge_docker_image_registry_prefix_upstream }}" +matrix_sms_bridge_docker_image_registry_prefix_upstream: "{{ matrix_sms_bridge_docker_image_registry_prefix_upstream_default }}" +matrix_sms_bridge_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_sms_bridge_docker_image_tag: "{{ matrix_sms_bridge_version }}" matrix_sms_bridge_base_path: "{{ matrix_base_data_path }}/matrix-sms-bridge" diff --git a/roles/custom/matrix-bridge-wechat/defaults/main.yml b/roles/custom/matrix-bridge-wechat/defaults/main.yml index 948329083..18d7b01ca 100644 --- a/roles/custom/matrix-bridge-wechat/defaults/main.yml +++ b/roles/custom/matrix-bridge-wechat/defaults/main.yml @@ -7,8 +7,10 @@ matrix_wechat_enabled: true # renovate: datasource=docker depName=lxduo/matrix-wechat matrix_wechat_version: 0.2.4 -matrix_wechat_container_image: "{{ matrix_wechat_container_image_name_prefix }}lxduo/matrix-wechat:{{ matrix_wechat_version }}" -matrix_wechat_container_image_name_prefix: "{{ 'localhost/' if matrix_wechat_container_image_self_build else 'docker.io/' }}" +matrix_wechat_container_image: "{{ matrix_wechat_container_image_registry_prefix }}lxduo/matrix-wechat:{{ matrix_wechat_version }}" +matrix_wechat_container_image_registry_prefix: "{{ 'localhost/' if matrix_wechat_container_image_self_build else matrix_wechat_container_image_registry_prefix_upstream }}" +matrix_wechat_container_image_registry_prefix_upstream: "{{ matrix_wechat_container_image_registry_prefix_upstream_default }}" +matrix_wechat_container_image_registry_prefix_upstream_default: "docker.io/" matrix_wechat_container_image_force_pull: "{{ matrix_wechat_container_image.endswith(':latest') }}" matrix_wechat_container_image_self_build: false diff --git a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml index 49159be21..c6868e1ae 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml @@ -17,3 +17,11 @@ when: matrix_architecture not in ['amd64'] ansible.builtin.fail: msg: "The WeChat Agent does not support the '{{ matrix_architecture }}' architecture yet. Its Dockerfile downloads amd64 binaries and does not work on arm64." + +- name: (Deprecation) Catch and report renamed WeChat variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_wechat_container_image_name_prefix', 'new': 'matrix_wechat_container_image_registry_prefix'} diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 36493e87f..9c5b61a05 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -16,7 +16,9 @@ matrix_cactus_comments_client_public_path_file_permissions: "0644" matrix_cactus_comments_client_version: 2.36.0 matrix_cactus_comments_client_container_image: "{{ matrix_cactus_comments_client_container_image_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}" -matrix_cactus_comments_client_container_image_registry_prefix: docker.io/ +matrix_cactus_comments_client_container_image_registry_prefix: "{{ matrix_cactus_comments_client_container_image_registry_prefix_upstream }}" +matrix_cactus_comments_client_container_image_registry_prefix_upstream: "{{ matrix_cactus_comments_client_container_image_registry_prefix_upstream_default }}" +matrix_cactus_comments_client_container_image_registry_prefix_upstream_default: docker.io/ matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}" matrix_cactus_comments_client_container_image_force_pull: "{{ matrix_cactus_comments_client_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-cactus-comments/defaults/main.yml b/roles/custom/matrix-cactus-comments/defaults/main.yml index 96f98d048..4794d1517 100644 --- a/roles/custom/matrix-cactus-comments/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments/defaults/main.yml @@ -28,7 +28,9 @@ matrix_cactus_comments_container_port: 5000 # renovate: datasource=docker depName=cactuscomments/cactus-appservice matrix_cactus_comments_version: 0.9.0 matrix_cactus_comments_docker_image: "{{ matrix_cactus_comments_docker_image_registry_prefix }}cactuscomments/cactus-appservice:{{ matrix_cactus_comments_docker_image_tag }}" -matrix_cactus_comments_docker_image_registry_prefix: docker.io/ +matrix_cactus_comments_docker_image_registry_prefix: "{{ 'localhost/' if matrix_cactus_comments_container_image_self_build else matrix_cactus_comments_docker_image_registry_prefix_upstream }}" +matrix_cactus_comments_docker_image_registry_prefix_upstream: "{{ matrix_cactus_comments_docker_image_registry_prefix_upstream_default }}" +matrix_cactus_comments_docker_image_registry_prefix_upstream_default: docker.io/ matrix_cactus_comments_docker_image_tag: "{{ matrix_cactus_comments_version }}" matrix_cactus_comments_docker_image_force_pull: "{{ matrix_cactus_comments_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 7612576e5..918740edb 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -8,8 +8,10 @@ matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/ # renovate: datasource=docker depName=ajbura/cinny matrix_client_cinny_version: v4.4.0 -matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" -matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else 'docker.io/' }}" +matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_registry_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" +matrix_client_cinny_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_client_cinny_docker_image_registry_prefix_upstream }}" +matrix_client_cinny_docker_image_registry_prefix_upstream: "{{ matrix_client_cinny_docker_image_registry_prefix_upstream_default }}" +matrix_client_cinny_docker_image_registry_prefix_upstream_default: docker.io/ matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}" matrix_client_cinny_data_path: "{{ matrix_base_data_path }}/client-cinny" diff --git a/roles/custom/matrix-client-cinny/tasks/validate_config.yml b/roles/custom/matrix-client-cinny/tasks/validate_config.yml index 7a7ee2dfe..e9a54ac0a 100644 --- a/roles/custom/matrix-client-cinny/tasks/validate_config.yml +++ b/roles/custom/matrix-client-cinny/tasks/validate_config.yml @@ -9,6 +9,14 @@ - {'name': 'matrix_client_cinny_container_network', when: true} - {'name': 'matrix_client_cinny_container_labels_traefik_compression_middleware_name', when: "{{ matrix_client_cinny_container_labels_traefik_compression_middleware_enabled }}"} +- name: (Deprecation) Catch and report renamed Cinny variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_client_cinny_container_image_name_prefix', 'new': 'matrix_client_cinny_container_image_registry_prefix'} + - name: Fail if matrix_client_cinny_path_prefix is not / ansible.builtin.fail: msg: >- diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 1cfcae331..ef415efa1 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -13,8 +13,10 @@ matrix_client_element_container_image_self_build_low_memory_system_patch_enabled # renovate: datasource=docker depName=vectorim/element-web matrix_client_element_version: v1.11.92 -matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" -matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else 'docker.io/' }}" +matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" +matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" +matrix_client_element_docker_image_registry_prefix_upstream: "{{ matrix_client_element_docker_image_registry_prefix_upstream_default }}" +matrix_client_element_docker_image_registry_prefix_upstream_default: docker.io/ matrix_client_element_docker_image_force_pull: "{{ matrix_client_element_docker_image.endswith(':latest') }}" matrix_client_element_data_path: "{{ matrix_base_data_path }}/client-element" diff --git a/roles/custom/matrix-client-element/tasks/validate_config.yml b/roles/custom/matrix-client-element/tasks/validate_config.yml index a61d8bcaf..fa76cdcd2 100644 --- a/roles/custom/matrix-client-element/tasks/validate_config.yml +++ b/roles/custom/matrix-client-element/tasks/validate_config.yml @@ -45,6 +45,7 @@ - {'old': 'matrix_client_element_branding_welcomeBackgroundUrl', 'new': 'matrix_client_element_branding_welcome_background_url'} - {'old': 'matrix_client_element_jitsi_preferredDomain', 'new': 'matrix_client_element_jitsi_preferred_domain'} - {'old': 'matrix_client_element_welcome_user_id', 'new': ''} + - {'old': 'matrix_client_element_docker_image_name_prefix', 'new': 'matrix_client_element_docker_image_registry_prefix'} - when: matrix_client_element_container_labels_traefik_enabled | bool block: diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml index 0f747c584..adb72fc94 100644 --- a/roles/custom/matrix-client-fluffychat/defaults/main.yml +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -9,8 +9,10 @@ matrix_client_fluffychat_container_image_self_build_version: "{{ 'main' if matri # renovate: datasource=docker depName=ghcr.io/etkecc/fluffychat-web matrix_client_fluffychat_version: v1.25.1 -matrix_client_fluffychat_docker_image: "{{ matrix_client_fluffychat_docker_image_name_prefix }}etkecc/fluffychat-web:{{ matrix_client_fluffychat_version }}" -matrix_client_fluffychat_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_fluffychat_container_image_self_build else 'ghcr.io/' }}" +matrix_client_fluffychat_docker_image: "{{ matrix_client_fluffychat_docker_image_registry_prefix }}etkecc/fluffychat-web:{{ matrix_client_fluffychat_version }}" +matrix_client_fluffychat_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_fluffychat_container_image_self_build else matrix_client_fluffychat_docker_image_registry_prefix_upstream }}" +matrix_client_fluffychat_docker_image_registry_prefix_upstream: "{{ matrix_client_fluffychat_docker_image_registry_prefix_upstream_default }}" +matrix_client_fluffychat_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_client_fluffychat_docker_image_force_pull: "{{ matrix_client_fluffychat_docker_image.endswith(':latest') }}" matrix_client_fluffychat_data_path: "{{ matrix_base_data_path }}/client-fluffychat" diff --git a/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml index 063ffa898..b42495c53 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml @@ -8,6 +8,14 @@ with_items: - matrix_client_fluffychat_container_network +- name: (Deprecation) Catch and report renamed FluffyChat Web variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_client_fluffychat_container_image_name_prefix', 'new': 'matrix_client_fluffychat_container_image_registry_prefix'} + - when: matrix_client_fluffychat_container_labels_traefik_enabled | bool block: - name: Fail if required matrix-client-fluffychat Traefik settings not defined diff --git a/roles/custom/matrix-client-hydrogen/defaults/main.yml b/roles/custom/matrix-client-hydrogen/defaults/main.yml index 78d1b8618..8d92b9f88 100644 --- a/roles/custom/matrix-client-hydrogen/defaults/main.yml +++ b/roles/custom/matrix-client-hydrogen/defaults/main.yml @@ -8,8 +8,10 @@ matrix_client_hydrogen_container_image_self_build_repo: "https://github.com/elem # renovate: datasource=docker depName=ghcr.io/element-hq/hydrogen-web matrix_client_hydrogen_version: v0.5.1 -matrix_client_hydrogen_docker_image: "{{ matrix_client_hydrogen_docker_image_name_prefix }}element-hq/hydrogen-web:{{ matrix_client_hydrogen_version }}" -matrix_client_hydrogen_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_hydrogen_container_image_self_build else 'ghcr.io/' }}" +matrix_client_hydrogen_docker_image: "{{ matrix_client_hydrogen_docker_image_registry_prefix }}element-hq/hydrogen-web:{{ matrix_client_hydrogen_version }}" +matrix_client_hydrogen_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_hydrogen_container_image_self_build else matrix_client_hydrogen_docker_image_registry_prefix_upstream }}" +matrix_client_hydrogen_docker_image_registry_prefix_upstream: "{{ matrix_client_hydrogen_docker_image_registry_prefix_upstream_default }}" +matrix_client_hydrogen_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_client_hydrogen_docker_image_force_pull: "{{ matrix_client_hydrogen_docker_image.endswith(':latest') }}" matrix_client_hydrogen_data_path: "{{ matrix_base_data_path }}/client-hydrogen" diff --git a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml index 93b9354eb..c5affb624 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml @@ -10,6 +10,14 @@ - {'name': 'matrix_client_hydrogen_container_network', when: true} - {'name': 'matrix_client_hydrogen_container_labels_traefik_compression_middleware_name', when: "{{ matrix_client_hydrogen_container_labels_traefik_compression_middleware_enabled }}"} +- name: (Deprecation) Catch and report renamed Hydrogen variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_client_hydrogen_container_image_name_prefix', 'new': 'matrix_client_hydrogen_container_image_registry_prefix'} + - when: matrix_client_hydrogen_container_labels_traefik_enabled | bool block: - name: Fail if required matrix-client-hydrogen Traefik settings not defined diff --git a/roles/custom/matrix-client-schildichat/defaults/main.yml b/roles/custom/matrix-client-schildichat/defaults/main.yml index 8d170e4e3..ec3d5e39d 100644 --- a/roles/custom/matrix-client-schildichat/defaults/main.yml +++ b/roles/custom/matrix-client-schildichat/defaults/main.yml @@ -13,8 +13,10 @@ matrix_client_schildichat_container_image_self_build_low_memory_system_patch_ena # renovate: datasource=docker depName=ghcr.io/etkecc/schildichat-web matrix_client_schildichat_version: 1.11.86-sc.0.test.0 -matrix_client_schildichat_docker_image: "{{ matrix_client_schildichat_docker_image_name_prefix }}etkecc/schildichat-web:{{ matrix_client_schildichat_version }}" -matrix_client_schildichat_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_schildichat_container_image_self_build else 'ghcr.io/' }}" +matrix_client_schildichat_docker_image: "{{ matrix_client_schildichat_docker_image_registry_prefix }}etkecc/schildichat-web:{{ matrix_client_schildichat_version }}" +matrix_client_schildichat_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_schildichat_container_image_self_build else matrix_client_schildichat_docker_image_registry_prefix_upstream }}" +matrix_client_schildichat_docker_image_registry_prefix_upstream: "{{ matrix_client_schildichat_docker_image_registry_prefix_upstream_default }}" +matrix_client_schildichat_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_client_schildichat_docker_image_force_pull: "{{ matrix_client_schildichat_docker_image.endswith(':latest') }}" matrix_client_schildichat_data_path: "{{ matrix_base_data_path }}/client-schildichat" diff --git a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml index a9cb7358c..3331a705b 100644 --- a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml +++ b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml @@ -8,6 +8,7 @@ when: "item.old in vars" with_items: - {'old': 'matrix_client_schildichat_welcome_user_id', 'new': ''} + - {'old': 'matrix_client_schildichat_container_image_name_prefix', 'new': 'matrix_client_schildichat_container_image_registry_prefix'} - name: Fail if required SchildiChat Web settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-conduit/defaults/main.yml b/roles/custom/matrix-conduit/defaults/main.yml index 247c95751..aba5a8a3a 100644 --- a/roles/custom/matrix-conduit/defaults/main.yml +++ b/roles/custom/matrix-conduit/defaults/main.yml @@ -7,8 +7,10 @@ matrix_conduit_enabled: true matrix_conduit_hostname: '' -matrix_conduit_docker_image: "{{ matrix_conduit_docker_image_name_prefix }}matrixconduit/matrix-conduit:{{ matrix_conduit_docker_image_tag }}" -matrix_conduit_docker_image_name_prefix: "docker.io/" +matrix_conduit_docker_image: "{{ matrix_conduit_docker_image_registry_prefix }}matrixconduit/matrix-conduit:{{ matrix_conduit_docker_image_tag }}" +matrix_conduit_docker_image_registry_prefix: "{{ matrix_conduit_docker_image_registry_prefix_upstream }}" +matrix_conduit_docker_image_registry_prefix_upstream: "{{ matrix_conduit_docker_image_registry_prefix_upstream_default }}" +matrix_conduit_docker_image_registry_prefix_upstream_default: docker.io/ # renovate: datasource=docker depName=matrixconduit/matrix-conduit matrix_conduit_docker_image_tag: "v0.9.0" matrix_conduit_docker_image_force_pull: "{{ matrix_conduit_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-conduit/tasks/validate_config.yml b/roles/custom/matrix-conduit/tasks/validate_config.yml index 7d643c654..8635661d0 100644 --- a/roles/custom/matrix-conduit/tasks/validate_config.yml +++ b/roles/custom/matrix-conduit/tasks/validate_config.yml @@ -9,3 +9,11 @@ - {'name': 'matrix_conduit_hostname', when: true} - {'name': 'matrix_conduit_container_network', when: true} - {'name': 'matrix_conduit_container_labels_internal_client_api_traefik_entrypoints', when: "{{ matrix_conduit_container_labels_internal_client_api_enabled }}"} + +- name: (Deprecation) Catch and report renamed Conduit variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_conduit_container_image_name_prefix', 'new': 'matrix_conduit_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml index f302ed664..ad420f2a4 100644 --- a/roles/custom/matrix-conduwuit/defaults/main.yml +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -8,11 +8,12 @@ matrix_conduwuit_enabled: true matrix_conduwuit_hostname: '' matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_registry_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}" -matrix_conduwuit_docker_image_name_prefix: "docker.io/" # renovate: datasource=docker depName=ghcr.io/girlbossceo/conduwuit matrix_conduwuit_docker_image_tag: v0.4.6-8f7ade4c22533a3177bfd8f175e178573ba6c1d4 matrix_conduwuit_docker_image_force_pull: "{{ matrix_conduwuit_docker_image.endswith(':latest') }}" -matrix_conduwuit_docker_image_registry_prefix: ghcr.io/ +matrix_conduwuit_docker_image_registry_prefix: "{{ matrix_conduwuit_docker_image_registry_prefix_upstream }}" +matrix_conduwuit_docker_image_registry_prefix_upstream: "{{ matrix_conduwuit_docker_image_registry_prefix_upstream_default }}" +matrix_conduwuit_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_conduwuit_base_path: "{{ matrix_base_data_path }}/conduwuit" matrix_conduwuit_config_path: "{{ matrix_conduwuit_base_path }}/config" diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml index 1b0d52f0a..b446acd3f 100644 --- a/roles/custom/matrix-corporal/defaults/main.yml +++ b/roles/custom/matrix-corporal/defaults/main.yml @@ -81,8 +81,10 @@ matrix_corporal_systemd_required_services_list_default: "{{ [devture_systemd_doc matrix_corporal_systemd_required_services_list_auto: [] matrix_corporal_systemd_required_services_list_custom: [] -matrix_corporal_docker_image: "{{ matrix_corporal_docker_image_name_prefix }}devture/matrix-corporal:{{ matrix_corporal_docker_image_tag }}" -matrix_corporal_docker_image_name_prefix: "{{ 'localhost/' if matrix_corporal_container_image_self_build else 'docker.io/' }}" +matrix_corporal_docker_image: "{{ matrix_corporal_docker_image_registry_prefix }}devture/matrix-corporal:{{ matrix_corporal_docker_image_tag }}" +matrix_corporal_docker_image_registry_prefix: "{{ 'localhost/' if matrix_corporal_container_image_self_build else matrix_corporal_docker_image_registry_prefix_upstream }}" +matrix_corporal_docker_image_registry_prefix_upstream: "{{ matrix_corporal_docker_image_registry_prefix_upstream_default }}" +matrix_corporal_docker_image_registry_prefix_upstream_default: docker.io/ matrix_corporal_docker_image_tag: "{{ matrix_corporal_version }}" # for backward-compatibility matrix_corporal_docker_image_force_pull: "{{ matrix_corporal_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-corporal/tasks/validate_config.yml b/roles/custom/matrix-corporal/tasks/validate_config.yml index 39f7190d4..b6f857e62 100644 --- a/roles/custom/matrix-corporal/tasks/validate_config.yml +++ b/roles/custom/matrix-corporal/tasks/validate_config.yml @@ -26,3 +26,4 @@ with_items: - {'old': 'matrix_corporal_container_expose_ports', 'new': ''} - {'old': 'matrix_corporal_reconciliation_user_id_local_part', 'new': 'matrix_corporal_corporal_user_id_local_part'} + - {'old': 'matrix_corporal_container_image_name_prefix', 'new': 'matrix_corporal_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index febee5009..b3ecb1efd 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -10,8 +10,10 @@ matrix_coturn_container_image_self_build_repo_dockerfile_path: "docker/coturn/al # renovate: datasource=docker depName=coturn/coturn matrix_coturn_version: 4.6.2-r11 -matrix_coturn_docker_image: "{{ matrix_coturn_docker_image_name_prefix }}coturn/coturn:{{ matrix_coturn_version }}-alpine" -matrix_coturn_docker_image_name_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else 'docker.io/' }}" +matrix_coturn_docker_image: "{{ matrix_coturn_docker_image_registry_prefix }}coturn/coturn:{{ matrix_coturn_version }}-alpine" +matrix_coturn_docker_image_registry_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else matrix_coturn_docker_image_registry_prefix_upstream }}" +matrix_coturn_docker_image_registry_prefix_upstream: "{{ matrix_coturn_docker_image_registry_prefix_upstream_default }}" +matrix_coturn_docker_image_registry_prefix_upstream_default: docker.io/ matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith(':latest') }}" # The Docker network that coturn would be put into. diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml index a90adb812..2b71deb2a 100644 --- a/roles/custom/matrix-coturn/tasks/validate_config.yml +++ b/roles/custom/matrix-coturn/tasks/validate_config.yml @@ -10,6 +10,7 @@ - {'old': 'matrix_coturn_docker_network', 'new': 'matrix_coturn_container_network'} - {'old': 'matrix_coturn_container_stun_plain_host_bind_port', 'new': 'superseded by matrix_coturn_container_stun_plain_host_bind_port_tcp and matrix_coturn_container_stun_plain_host_bind_port_udp'} - {'old': 'matrix_coturn_container_stun_tls_host_bind_port', 'new': 'superseded by matrix_coturn_container_stun_tls_host_bind_port_tcp and matrix_coturn_container_stun_tls_host_bind_port_udp'} + - {'old': 'matrix_coturn_container_image_name_prefix', 'new': 'matrix_coturn_docker_image_registry_prefix'} - name: Fail if matrix_coturn_authentication_method is invalid ansible.builtin.fail: diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml index e39ccae6a..8a3a7bc40 100644 --- a/roles/custom/matrix-dendrite/defaults/main.yml +++ b/roles/custom/matrix-dendrite/defaults/main.yml @@ -10,8 +10,10 @@ matrix_dendrite_container_image_self_build: false matrix_dendrite_container_image_self_build_repo: "https://github.com/matrix-org/dendrite.git" matrix_dendrite_docker_image_path: "matrixdotorg/dendrite-monolith" -matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_name_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}" -matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else 'docker.io/' }}" +matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_registry_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}" +matrix_dendrite_docker_image_registry_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else matrix_dendrite_docker_image_registry_prefix_upstream }}" +matrix_dendrite_docker_image_registry_prefix_upstream: "{{ matrix_dendrite_docker_image_registry_prefix_upstream_default }}" +matrix_dendrite_docker_image_registry_prefix_upstream_default: docker.io/ # renovate: datasource=docker depName=matrixdotorg/dendrite-monolith matrix_dendrite_docker_image_tag: "v0.14.1" matrix_dendrite_docker_image_force_pull: "{{ matrix_dendrite_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-dendrite/tasks/validate_config.yml b/roles/custom/matrix-dendrite/tasks/validate_config.yml index 581825a38..339ac8fb2 100644 --- a/roles/custom/matrix-dendrite/tasks/validate_config.yml +++ b/roles/custom/matrix-dendrite/tasks/validate_config.yml @@ -27,6 +27,7 @@ - {'old': 'matrix_dendrite_pushserver_database', 'new': 'matrix_dendrite_push_server_database'} - {'old': 'matrix_dendrite_relayapi_database', 'new': 'matrix_dendrite_relay_api_database'} - {'old': 'matrix_dendrite_keyserver_database', 'new': 'matrix_dendrite_key_server_database'} + - {'old': 'matrix_dendrite_container_image_name_prefix', 'new': 'matrix_dendrite_docker_image_registry_prefix'} - name: Fail if required Dendrite settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml index d0ba9727c..c5226694f 100644 --- a/roles/custom/matrix-dimension/defaults/main.yml +++ b/roles/custom/matrix-dimension/defaults/main.yml @@ -31,8 +31,10 @@ matrix_dimension_docker_src_files_path: "{{ matrix_base_data_path }}/docker-src/ # renovate: datasource=docker depName=turt2live/matrix-dimension matrix_dimension_version: latest -matrix_dimension_docker_image: "{{ matrix_dimension_docker_image_name_prefix }}turt2live/matrix-dimension:{{ matrix_dimension_version }}" -matrix_dimension_docker_image_name_prefix: "{{ 'localhost/' if matrix_dimension_container_image_self_build else 'docker.io/' }}" +matrix_dimension_docker_image: "{{ matrix_dimension_docker_image_registry_prefix }}turt2live/matrix-dimension:{{ matrix_dimension_version }}" +matrix_dimension_docker_image_registry_prefix: "{{ 'localhost/' if matrix_dimension_container_image_self_build else matrix_dimension_docker_image_registry_prefix_upstream }}" +matrix_dimension_docker_image_registry_prefix_upstream: "{{ matrix_dimension_docker_image_registry_prefix_upstream_default }}" +matrix_dimension_docker_image_registry_prefix_upstream_default: docker.io/ matrix_dimension_docker_image_force_pull: "{{ matrix_dimension_docker_image.endswith(':latest') }}" # List of systemd services that matrix-dimension.service depends on. diff --git a/roles/custom/matrix-dimension/tasks/validate_config.yml b/roles/custom/matrix-dimension/tasks/validate_config.yml index b001ceedb..bad6712a2 100644 --- a/roles/custom/matrix-dimension/tasks/validate_config.yml +++ b/roles/custom/matrix-dimension/tasks/validate_config.yml @@ -22,6 +22,7 @@ when: "item.old in vars" with_items: - {'old': 'matrix_dimension_container_expose_port', 'new': ''} + - {'old': 'matrix_dimension_container_image_name_prefix', 'new': 'matrix_dimension_docker_image_registry_prefix'} - when: matrix_dimension_container_labels_traefik_enabled | bool block: diff --git a/roles/custom/matrix-dynamic-dns/defaults/main.yml b/roles/custom/matrix-dynamic-dns/defaults/main.yml index 269072c67..e9b7b0eab 100644 --- a/roles/custom/matrix-dynamic-dns/defaults/main.yml +++ b/roles/custom/matrix-dynamic-dns/defaults/main.yml @@ -11,9 +11,11 @@ matrix_dynamic_dns_daemon_interval: '300' matrix_dynamic_dns_version: 4.0.0 # The docker container to use when in mode -matrix_dynamic_dns_docker_image: "{{ matrix_dynamic_dns_docker_image_name_prefix }}linuxserver/ddclient:{{ matrix_dynamic_dns_version }}" +matrix_dynamic_dns_docker_image: "{{ matrix_dynamic_dns_docker_image_registry_prefix }}linuxserver/ddclient:{{ matrix_dynamic_dns_version }}" -matrix_dynamic_dns_docker_image_name_prefix: "{{ 'localhost/' if matrix_dynamic_dns_container_image_self_build else 'docker.io/' }}" +matrix_dynamic_dns_docker_image_registry_prefix: "{{ 'localhost/' if matrix_dynamic_dns_container_image_self_build else matrix_dynamic_dns_docker_image_registry_prefix_upstream }}" +matrix_dynamic_dns_docker_image_registry_prefix_upstream: "{{ matrix_dynamic_dns_docker_image_registry_prefix_upstream_default }}" +matrix_dynamic_dns_docker_image_registry_prefix_upstream_default: docker.io/ # The image to force pull matrix_dynamic_dns_docker_image_force_pull: "{{ matrix_dynamic_dns_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml b/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml index 8174a8487..d7dd34717 100644 --- a/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml +++ b/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml @@ -1,12 +1,12 @@ --- -- name: Fail if no configurations specified +- name: Fail if no matrix-dynamic-dns configurations specified ansible.builtin.fail: msg: >- You need to define at least one configuration in `matrix_dynamic_dns_domain_configurations` for using matrix-dynamic-dns. when: "matrix_dynamic_dns_domain_configurations | length == 0" -- name: Fail if required settings not defined in configuration blocks +- name: Fail if required matrix-dynamic-dns settings not defined in configuration blocks ansible.builtin.fail: msg: >- One of the configurations in matrix_dynamic_dns_domain_configurations is missing a required key (domain, provider, protocol). @@ -15,10 +15,18 @@ loop_control: loop_var: configuration -- name: Fail if required mautrix-dynamic-dns settings not defined +- name: Fail if required matrix-dynamic-dns settings not defined ansible.builtin.fail: msg: >- You need to define a required configuration setting (`{{ item.name }}`). when: "item.when | bool and vars[item.name] == ''" with_items: - {'name': 'matrix_dynamic_dns_container_network', when: true} + +- name: (Deprecation) Catch and report renamed matrix-dynamic-dns variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_dynamic_dns_container_image_name_prefix', 'new': 'matrix_dynamic_dns_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-email2matrix/defaults/main.yml b/roles/custom/matrix-email2matrix/defaults/main.yml index d5355e877..966d3a21b 100644 --- a/roles/custom/matrix-email2matrix/defaults/main.yml +++ b/roles/custom/matrix-email2matrix/defaults/main.yml @@ -13,8 +13,10 @@ matrix_email2matrix_container_image_self_build_branch: "{{ matrix_email2matrix_v # renovate: datasource=docker depName=devture/email2matrix matrix_email2matrix_version: 1.1.0 -matrix_email2matrix_docker_image_prefix: "{{ 'localhost/' if matrix_email2matrix_container_image_self_build else 'docker.io/' }}" -matrix_email2matrix_docker_image: "{{ matrix_email2matrix_docker_image_prefix }}devture/email2matrix:{{ matrix_email2matrix_version }}" +matrix_email2matrix_docker_image: "{{ matrix_email2matrix_docker_image_registry_prefix }}devture/email2matrix:{{ matrix_email2matrix_version }}" +matrix_email2matrix_docker_image_registry_prefix: "{{ 'localhost/' if matrix_email2matrix_container_image_self_build else matrix_email2matrix_docker_image_registry_prefix_upstream }}" +matrix_email2matrix_docker_image_registry_prefix_upstream: "{{ matrix_email2matrix_docker_image_registry_prefix_upstream_default }}" +matrix_email2matrix_docker_image_registry_prefix_upstream_default: docker.io/ matrix_email2matrix_docker_image_force_pull: "{{ matrix_email2matrix_docker_image.endswith(':latest') }}" matrix_email2matrix_container_network: "" diff --git a/roles/custom/matrix-email2matrix/tasks/validate_config.yml b/roles/custom/matrix-email2matrix/tasks/validate_config.yml index eab9b3268..d623bc583 100644 --- a/roles/custom/matrix-email2matrix/tasks/validate_config.yml +++ b/roles/custom/matrix-email2matrix/tasks/validate_config.yml @@ -13,3 +13,11 @@ when: "item.when | bool and vars[item.name] == ''" with_items: - {'name': 'matrix_email2matrix_container_network', when: true} + +- name: (Deprecation) Catch and report renamed Email2Matrix variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_email2matrix_docker_image_name_prefix', 'new': 'matrix_email2matrix_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml b/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml index ce9ba1259..b7dd0996c 100644 --- a/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml +++ b/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml @@ -6,7 +6,12 @@ matrix_ldap_registration_proxy_enabled: true matrix_ldap_registration_proxy_hostname: '' -matrix_ldap_registration_proxy_docker_image: matrix_ldap_registration_proxy +matrix_ldap_registration_proxy_docker_image: "{{ matrix_ldap_registration_proxy_docker_image_registry_prefix }}matrix_ldap_registration_proxy" +matrix_ldap_registration_proxy_docker_image_registry_prefix: "{{ 'localhost/' if matrix_ldap_registration_proxy_container_image_self_build else matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream }}" +matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream: "{{ matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream_default }}" +matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream_default: "" + +matrix_ldap_registration_proxy_container_image_self_build: true matrix_ldap_registration_proxy_container_image_self_build_repo: "https://gitlab.com/activism.international/matrix_ldap_registration_proxy.git" matrix_ldap_registration_proxy_container_image_self_build_branch: "{{ matrix_ldap_registration_proxy_version }}" diff --git a/roles/custom/matrix-ma1sd/defaults/main.yml b/roles/custom/matrix-ma1sd/defaults/main.yml index 78d6cfac4..53c93df33 100644 --- a/roles/custom/matrix-ma1sd/defaults/main.yml +++ b/roles/custom/matrix-ma1sd/defaults/main.yml @@ -14,8 +14,10 @@ matrix_ma1sd_container_image_self_build_branch: "{{ matrix_ma1sd_version }}" # renovate: datasource=docker depName=ma1uta/ma1sd matrix_ma1sd_version: "2.5.0" -matrix_ma1sd_docker_image: "{{ matrix_ma1sd_docker_image_name_prefix }}ma1uta/ma1sd:{{ matrix_ma1sd_version }}" -matrix_ma1sd_docker_image_name_prefix: "{{ 'localhost/' if matrix_ma1sd_container_image_self_build else 'docker.io/' }}" +matrix_ma1sd_docker_image: "{{ matrix_ma1sd_docker_image_registry_prefix }}ma1uta/ma1sd:{{ matrix_ma1sd_version }}" +matrix_ma1sd_docker_image_registry_prefix: "{{ 'localhost/' if matrix_ma1sd_container_image_self_build else matrix_ma1sd_docker_image_registry_prefix_upstream }}" +matrix_ma1sd_docker_image_registry_prefix_upstream: "{{ matrix_ma1sd_docker_image_registry_prefix_upstream_default }}" +matrix_ma1sd_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_ma1sd_docker_image_force_pull: "{{ matrix_ma1sd_docker_image.endswith(':latest') }}" matrix_ma1sd_base_path: "{{ matrix_base_data_path }}/ma1sd" diff --git a/roles/custom/matrix-ma1sd/tasks/validate_config.yml b/roles/custom/matrix-ma1sd/tasks/validate_config.yml index 8e4787507..6a2345777 100644 --- a/roles/custom/matrix-ma1sd/tasks/validate_config.yml +++ b/roles/custom/matrix-ma1sd/tasks/validate_config.yml @@ -68,6 +68,7 @@ - {'old': 'matrix_ma1sd_default_port', 'new': 'matrix_ma1sd_container_port'} - {'old': 'matrix_ma1sd_container_labels_matrix_client_user_directory_search_path', 'new': 'matrix_ma1sd_container_labels_matrix_client_user_directory_search_path_regexp'} - {'old': 'matrix_ma1sd_container_labels_matrix_client_3pid_registration_path', 'new': 'matrix_ma1sd_container_labels_matrix_client_3pid_registration_path_regexp'} + - {'old': 'matrix_ma1sd_docker_image_name_prefix', 'new': 'matrix_ma1sd_docker_image_registry_prefix'} - name: (Deprecation) Catch and report mxisd variables ansible.builtin.fail: diff --git a/roles/custom/matrix-media-repo/defaults/main.yml b/roles/custom/matrix-media-repo/defaults/main.yml index f9fc4eaaf..f41489a5b 100755 --- a/roles/custom/matrix-media-repo/defaults/main.yml +++ b/roles/custom/matrix-media-repo/defaults/main.yml @@ -16,8 +16,10 @@ matrix_media_repo_container_image_self_build: false matrix_media_repo_container_image_self_build_repo: "https://github.com/turt2live/matrix-media-repo.git" matrix_media_repo_docker_image_path: "t2bot/matrix-media-repo" -matrix_media_repo_docker_image: "{{ matrix_media_repo_docker_image_name_prefix }}{{ matrix_media_repo_docker_image_path }}:{{ matrix_media_repo_docker_image_tag }}" -matrix_media_repo_docker_image_name_prefix: "{{ 'localhost/' if matrix_media_repo_container_image_self_build else 'ghcr.io/' }}" +matrix_media_repo_docker_image: "{{ matrix_media_repo_docker_image_registry_prefix }}{{ matrix_media_repo_docker_image_path }}:{{ matrix_media_repo_docker_image_tag }}" +matrix_media_repo_docker_image_registry_prefix: "{{ 'localhost/' if matrix_media_repo_container_image_self_build else matrix_media_repo_docker_image_registry_prefix_upstream }}" +matrix_media_repo_docker_image_registry_prefix_upstream: "{{ matrix_media_repo_docker_image_registry_prefix_upstream_default }}" +matrix_media_repo_docker_image_registry_prefix_upstream_default: "ghcr.io/" # renovate: datasource=docker depName=ghcr.io/t2bot/matrix-media-repo matrix_media_repo_docker_image_tag: "v1.3.8" matrix_media_repo_docker_image_force_pull: "{{ matrix_media_repo_docker_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-media-repo/tasks/validate_config.yml b/roles/custom/matrix-media-repo/tasks/validate_config.yml index 8b0ecb7cd..bd923eec6 100644 --- a/roles/custom/matrix-media-repo/tasks/validate_config.yml +++ b/roles/custom/matrix-media-repo/tasks/validate_config.yml @@ -34,3 +34,4 @@ - {'old': 'matrix_media_repo_container_labels_traefik_admin_path_prefix', 'new': 'matrix_media_repo_container_labels_traefik_admin_path_regexp'} - {'old': 'matrix_media_repo_container_labels_traefik_logout_federation_path_prefix', 'new': 'matrix_media_repo_container_labels_traefik_logout_federation_path_regexp'} - {'old': 'matrix_media_repo_container_labels_traefik_admin_federation_path_prefix', 'new': 'matrix_media_repo_container_labels_traefik_admin_federation_path_regexp'} + - {'old': 'matrix_media_repo_docker_image_name_prefix', 'new': 'matrix_media_repo_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-pantalaimon/defaults/main.yml b/roles/custom/matrix-pantalaimon/defaults/main.yml index 3708a0b33..28b727b93 100644 --- a/roles/custom/matrix-pantalaimon/defaults/main.yml +++ b/roles/custom/matrix-pantalaimon/defaults/main.yml @@ -10,8 +10,10 @@ matrix_pantalaimon_container_image_self_build: false matrix_pantalaimon_container_image_self_build_repo: "https://github.com/matrix-org/pantalaimon.git" matrix_pantalaimon_container_image_self_build_repo_version: "{{ 'main' if matrix_pantalaimon_version == 'latest' else matrix_pantalaimon_version }}" -matrix_pantalaimon_docker_image: "{{ matrix_pantalaimon_docker_image_name_prefix }}matrixdotorg/pantalaimon:v{{ matrix_pantalaimon_version }}" -matrix_pantalaimon_docker_image_name_prefix: "{{ 'localhost/' if matrix_pantalaimon_container_image_self_build else 'docker.io/' }}" +matrix_pantalaimon_docker_image: "{{ matrix_pantalaimon_docker_image_registry_prefix }}matrixdotorg/pantalaimon:v{{ matrix_pantalaimon_version }}" +matrix_pantalaimon_docker_image_registry_prefix: "{{ 'localhost/' if matrix_pantalaimon_container_image_self_build else matrix_pantalaimon_docker_image_registry_prefix_upstream }}" +matrix_pantalaimon_docker_image_registry_prefix_upstream: "{{ matrix_pantalaimon_docker_image_registry_prefix_upstream_default }}" +matrix_pantalaimon_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_pantalaimon_docker_image_force_pull: "{{ matrix_pantalaimon_docker_image.endswith(':latest') }}" matrix_pantalaimon_base_path: "{{ matrix_base_data_path }}/pantalaimon" diff --git a/roles/custom/matrix-pantalaimon/tasks/validate_config.yml b/roles/custom/matrix-pantalaimon/tasks/validate_config.yml index 00fc96ced..6fc490ef1 100644 --- a/roles/custom/matrix-pantalaimon/tasks/validate_config.yml +++ b/roles/custom/matrix-pantalaimon/tasks/validate_config.yml @@ -1,8 +1,16 @@ --- -- name: Fail if required variables are undefined +- name: Fail if required Pantalaimon variables are undefined ansible.builtin.fail: msg: "The `{{ item }}` variable must be defined and have a non-null value." with_items: - "matrix_pantalaimon_homeserver_url" when: "vars[item] == '' or vars[item] is none" + +- name: (Deprecation) Catch and report renamed Pantalaimon variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_pantalaimon_docker_image_name_prefix', 'new': 'matrix_pantalaimon_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml index a7177861e..d02bdcb43 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml @@ -17,9 +17,11 @@ matrix_prometheus_nginxlog_exporter_container_metrics_port: '4040' matrix_prometheus_nginxlog_exporter_container_syslog_port: '6514' matrix_prometheus_nginxlog_exporter_docker_image_arch: ['amd64', 'arm64'] -matrix_prometheus_nginxlog_exporter_docker_image_name_prefix: "{{ 'ghcr.io/martin-helmich/' }}" +matrix_prometheus_nginxlog_exporter_docker_image: "{{ matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix }}martin-helmich/prometheus-nginxlog-exporter/exporter:{{ matrix_prometheus_nginxlog_exporter_docker_image_tag }}" +matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix: "{{ matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream }}" +matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream: "{{ matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream_default }}" +matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_prometheus_nginxlog_exporter_docker_image_tag: "{{ 'latest' if matrix_prometheus_nginxlog_exporter_version == 'master' else matrix_prometheus_nginxlog_exporter_version }}-{{ matrix_architecture }}" -matrix_prometheus_nginxlog_exporter_docker_image: "{{ matrix_prometheus_nginxlog_exporter_docker_image_name_prefix }}prometheus-nginxlog-exporter/exporter:{{ matrix_prometheus_nginxlog_exporter_docker_image_tag }}" matrix_prometheus_nginxlog_exporter_docker_image_force_pull: "{{ matrix_prometheus_nginxlog_exporter_docker_image.endswith(':latest') }}" matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: true diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml index bf97f4cbc..1978ed6ed 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml @@ -8,6 +8,7 @@ when: "item.old in vars" with_items: - {'old': 'matrix_prometheus_nginxlog_exporter_container_hostname', 'new': 'matrix_prometheus_nginxlog_exporter_identifier'} + - {'old': 'matrix_prometheus_nginxlog_exporter_docker_image_name_prefix', 'new': 'matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix'} - name: Fail if docker image not availble for arch ansible.builtin.fail: diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index 1c3d059c1..3b16546d2 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -24,11 +24,12 @@ matrix_rageshake_config_path: "{{ matrix_rageshake_base_path }}/config" matrix_rageshake_data_path: "{{ matrix_rageshake_base_path }}/data" matrix_rageshake_container_src_files_path: "{{ matrix_rageshake_base_path }}/container-src" -matrix_rageshake_container_image: "{{ matrix_rageshake_container_image_name_prefix }}matrix-org/rageshake:{{ matrix_rageshake_container_image_tag }}" -matrix_rageshake_container_image_name_prefix: "{{ 'localhost/' if matrix_rageshake_container_image_self_build else matrix_rageshake_container_registry_prefix }}" +matrix_rageshake_container_image: "{{ matrix_rageshake_container_image_registry_prefix }}matrix-org/rageshake:{{ matrix_rageshake_container_image_tag }}" +matrix_rageshake_container_image_registry_prefix: "{{ 'localhost/' if matrix_rageshake_container_image_self_build else matrix_rageshake_container_image_registry_prefix_upstream }}" +matrix_rageshake_container_image_registry_prefix_upstream: "{{ matrix_rageshake_container_image_registry_prefix_upstream_default }}" +matrix_rageshake_container_image_registry_prefix_upstream_default: "ghcr.io/" matrix_rageshake_container_image_force_pull: "{{ matrix_rageshake_container_image.endswith(':master') }}" matrix_rageshake_container_image_tag: "{{ matrix_rageshake_version }}" -matrix_rageshake_container_registry_prefix: ghcr.io/ matrix_rageshake_container_image_self_build: false matrix_rageshake_container_image_self_build_repo: "https://github.com/matrix-org/rageshake/" diff --git a/roles/custom/matrix-rageshake/tasks/validate_config.yml b/roles/custom/matrix-rageshake/tasks/validate_config.yml index b61a486d2..7ebb2b6b0 100644 --- a/roles/custom/matrix-rageshake/tasks/validate_config.yml +++ b/roles/custom/matrix-rageshake/tasks/validate_config.yml @@ -10,6 +10,14 @@ - matrix_rageshake_path_prefix - matrix_rageshake_container_network +- name: (Deprecation) Catch and report renamed rageshake variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_rageshake_docker_image_name_prefix', 'new': 'matrix_rageshake_docker_image_registry_prefix'} + - when: matrix_rageshake_container_labels_traefik_enabled | bool block: - name: Fail if required rageshake Traefik settings not defined diff --git a/roles/custom/matrix-registration/defaults/main.yml b/roles/custom/matrix-registration/defaults/main.yml index 0cc776fe7..77d8f371d 100644 --- a/roles/custom/matrix-registration/defaults/main.yml +++ b/roles/custom/matrix-registration/defaults/main.yml @@ -25,8 +25,10 @@ matrix_registration_docker_src_files_path: "{{ matrix_registration_base_path }}/ # renovate: datasource=docker depName=zeratax/matrix-registration matrix_registration_version: "v0.7.2" -matrix_registration_docker_image: "{{ matrix_registration_docker_image_name_prefix }}zeratax/matrix-registration:{{ matrix_registration_version }}" -matrix_registration_docker_image_name_prefix: "{{ 'localhost/' if matrix_registration_container_image_self_build else 'docker.io/' }}" +matrix_registration_docker_image: "{{ matrix_registration_docker_image_registry_prefix }}zeratax/matrix-registration:{{ matrix_registration_version }}" +matrix_registration_docker_image_registry_prefix: "{{ 'localhost/' if matrix_registration_container_image_self_build else matrix_registration_docker_image_registry_prefix_upstream }}" +matrix_registration_docker_image_registry_prefix_upstream: "{{ matrix_registration_docker_image_registry_prefix_upstream_default }}" +matrix_registration_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_registration_docker_image_force_pull: "{{ matrix_registration_docker_image.endswith(':latest') }}" matrix_registration_container_network: "" diff --git a/roles/custom/matrix-sliding-sync/defaults/main.yml b/roles/custom/matrix-sliding-sync/defaults/main.yml index d8fbdff7c..41ef93dc2 100644 --- a/roles/custom/matrix-sliding-sync/defaults/main.yml +++ b/roles/custom/matrix-sliding-sync/defaults/main.yml @@ -24,11 +24,12 @@ matrix_sliding_sync_container_image_self_build_repo: https://github.com/matrix-o matrix_sliding_sync_container_image_self_build_repo_version: "{{ 'main' if matrix_sliding_sync_version == 'main' else matrix_sliding_sync_version }}" matrix_sliding_sync_container_src_path: "{{ matrix_sliding_sync_base_path }}/container-src" -matrix_sliding_sync_container_image: "{{ matrix_sliding_sync_container_image_name_prefix }}matrix-org/sliding-sync:{{ matrix_sliding_sync_container_image_tag }}" -matrix_sliding_sync_container_image_name_prefix: "{{ 'localhost/' if matrix_sliding_sync_container_image_self_build else matrix_sliding_sync_container_image_registry_prefix }}" +matrix_sliding_sync_container_image: "{{ matrix_sliding_sync_container_image_registry_prefix }}matrix-org/sliding-sync:{{ matrix_sliding_sync_container_image_tag }}" +matrix_sliding_sync_container_image_registry_prefix: "{{ 'localhost/' if matrix_sliding_sync_container_image_self_build else matrix_sliding_sync_container_image_registry_prefix_upstream }}" +matrix_sliding_sync_container_image_registry_prefix_upstream: "{{ matrix_sliding_sync_container_image_registry_prefix_upstream_default }}" +matrix_sliding_sync_container_image_registry_prefix_upstream_default: "ghcr.io/" matrix_sliding_sync_container_image_tag: "{{ matrix_sliding_sync_version }}" matrix_sliding_sync_container_image_force_pull: "{{ matrix_sliding_sync_container_image.endswith(':main') }}" -matrix_sliding_sync_container_image_registry_prefix: ghcr.io/ # The base container network. It will be auto-created by this role if it doesn't exist already. matrix_sliding_sync_container_network: '' diff --git a/roles/custom/matrix-sliding-sync/tasks/validate_config.yml b/roles/custom/matrix-sliding-sync/tasks/validate_config.yml index 8b1fee201..d5ba9e89c 100644 --- a/roles/custom/matrix-sliding-sync/tasks/validate_config.yml +++ b/roles/custom/matrix-sliding-sync/tasks/validate_config.yml @@ -13,3 +13,11 @@ - {'name': 'matrix_sliding_sync_container_network', when: true} - {'name': 'matrix_sliding_sync_metrics_proxying_hostname', when: "{{ matrix_sliding_sync_metrics_proxying_enabled }}"} - {'name': 'matrix_sliding_sync_metrics_proxying_path_prefix', when: "{{ matrix_sliding_sync_metrics_proxying_enabled }}"} + +- name: (Deprecation) Catch and report renamed matrix-sliding-sync variables + ansible.builtin.fail: + msg: >- + The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. + when: "item.old in vars" + with_items: + - {'old': 'matrix_sliding_sync_container_image_name_prefix', 'new': 'matrix_sliding_sync_container_image_registry_prefix'} diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index e4dd36e95..b7f393d0a 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -25,7 +25,9 @@ matrix_static_files_systemd_wanted_services_list_auto: [] matrix_static_files_systemd_wanted_services_list_custom: [] matrix_static_files_container_image: "{{ matrix_static_files_container_image_registry_prefix }}joseluisq/static-web-server:{{ matrix_static_files_container_image_tag }}" -matrix_static_files_container_image_registry_prefix: docker.io/ +matrix_static_files_container_image_registry_prefix: "{{ matrix_static_files_container_image_registry_prefix_upstream }}" +matrix_static_files_container_image_registry_prefix_upstream: "{{ matrix_static_files_container_image_registry_prefix_upstream_default }}" +matrix_static_files_container_image_registry_prefix_upstream_default: "docker.io/" matrix_static_files_container_image_tag: "{{ 'latest' if matrix_static_files_version == 'latest' else (matrix_static_files_version + '-alpine') }}" matrix_static_files_container_image_force_pull: "{{ matrix_static_files_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-sygnal/defaults/main.yml b/roles/custom/matrix-sygnal/defaults/main.yml index 490b391d8..ecce0f518 100644 --- a/roles/custom/matrix-sygnal/defaults/main.yml +++ b/roles/custom/matrix-sygnal/defaults/main.yml @@ -27,7 +27,9 @@ matrix_sygnal_systemd_wanted_services_list: [] matrix_sygnal_docker_image: "{{ matrix_sygnal_docker_image_registry_prefix }}matrixdotorg/sygnal:{{ matrix_sygnal_docker_image_tag }}" matrix_sygnal_docker_image_tag: "{{ matrix_sygnal_version }}" -matrix_sygnal_docker_image_registry_prefix: docker.io/ +matrix_sygnal_docker_image_registry_prefix: "{{ matrix_sygnal_docker_image_registry_prefix_upstream }}" +matrix_sygnal_docker_image_registry_prefix_upstream: "{{ matrix_sygnal_docker_image_registry_prefix_upstream_default }}" +matrix_sygnal_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_sygnal_docker_image_force_pull: "{{ matrix_sygnal_docker_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 50ebe9098..09e13dd9e 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -15,8 +15,10 @@ matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin matrix_synapse_admin_version: v0.10.3-etke37 -matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" -matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}" +matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_registry_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" +matrix_synapse_admin_docker_image_registry_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else matrix_synapse_admin_docker_image_registry_prefix_upstream }}" +matrix_synapse_admin_docker_image_registry_prefix_upstream: "{{ matrix_synapse_admin_docker_image_registry_prefix_upstream_default }}" +matrix_synapse_admin_docker_image_registry_prefix_upstream_default: "ghcr.io/" matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}" # The base container network diff --git a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml index 0fa3ce77b..1b9856d51 100644 --- a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml @@ -1,6 +1,6 @@ --- -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed matrix-synapse-admin settings ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -12,6 +12,7 @@ - {'old': 'matrix_synapse_admin_container_self_build_repo', 'new': 'matrix_synapse_admin_container_image_self_build_repo'} - {'old': 'matrix_synapse_admin_public_endpoint', 'new': 'matrix_synapse_admin_path_prefix'} - {'old': 'matrix_synapse_admin_nginx_proxy_integration_enabled', 'new': ''} + - {'old': 'matrix_synapse_admin_docker_image_name_prefix', 'new': 'matrix_synapse_admin_docker_image_registry_prefix'} - when: matrix_synapse_admin_container_labels_traefik_enabled | bool block: diff --git a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml index 020a447c5..f5d02cd17 100644 --- a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml +++ b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml @@ -22,8 +22,10 @@ matrix_synapse_auto_compressor_container_image_self_build: false matrix_synapse_auto_compressor_container_image_self_build_repo: "https://github.com/matrix-org/rust-synapse-compress-state.git" matrix_synapse_auto_compressor_container_image_self_build_version: "{{ 'main' if matrix_synapse_auto_compressor_version == 'latest' else matrix_synapse_auto_compressor_version }}" -matrix_synapse_auto_compressor_container_image: "{{ matrix_synapse_auto_compressor_container_image_name_prefix }}etke.cc/rust-synapse-compress-state:{{ matrix_synapse_auto_compressor_version }}" -matrix_synapse_auto_compressor_container_image_name_prefix: "{{ 'localhost/' if matrix_synapse_auto_compressor_container_image_self_build else 'registry.gitlab.com/' }}" +matrix_synapse_auto_compressor_container_image: "{{ matrix_synapse_auto_compressor_container_image_registry_prefix }}etke.cc/rust-synapse-compress-state:{{ matrix_synapse_auto_compressor_version }}" +matrix_synapse_auto_compressor_container_image_registry_prefix: "{{ 'localhost/' if matrix_synapse_auto_compressor_container_image_self_build else matrix_synapse_auto_compressor_container_image_registry_prefix_upstream }}" +matrix_synapse_auto_compressor_container_image_registry_prefix_upstream: "{{ matrix_synapse_auto_compressor_container_image_registry_prefix_upstream_default }}" +matrix_synapse_auto_compressor_container_image_registry_prefix_upstream_default: "registry.gitlab.com/" matrix_synapse_auto_compressor_container_image_force_pull: "{{ matrix_synapse_auto_compressor_container_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml index 1d1405044..9441eea5f 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml @@ -1,5 +1,5 @@ --- -- name: (Deprecation) Catch and report renamed settings +- name: (Deprecation) Catch and report renamed matrix-synapse-auto-compressor settings ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. @@ -8,6 +8,8 @@ with_items: - "old": "matrix_synapse_auto_compressor_calendar" "new": "matrix_synapse_auto_compressor_schedule" + - "old": "matrix_synapse_auto_compressor_container_image_name_prefix" + "new": "matrix_synapse_auto_compressor_container_image_registry_prefix" - name: Fail if required matrix-synapse-auto-compressor settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 47074216e..241f0c7e9 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -31,7 +31,9 @@ matrix_synapse_reverse_proxy_companion_systemd_wanted_services_list: ['matrix-sy # An alternative would be an `nginxinc/nginx-unprivileged` image, but # that is frequently out of date. matrix_synapse_reverse_proxy_companion_container_image: "{{ matrix_synapse_reverse_proxy_companion_container_image_registry_prefix }}nginx:{{ matrix_synapse_reverse_proxy_companion_container_image_tag }}" -matrix_synapse_reverse_proxy_companion_container_image_registry_prefix: docker.io/ +matrix_synapse_reverse_proxy_companion_container_image_registry_prefix: "{{ matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream }}" +matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream: "{{ matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream_default }}" +matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream_default: "docker.io/" matrix_synapse_reverse_proxy_companion_container_image_tag: "{{ matrix_synapse_reverse_proxy_companion_version }}" matrix_synapse_reverse_proxy_companion_container_image_force_pull: "{{ matrix_synapse_reverse_proxy_companion_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml index 3b0579bad..25768f0e2 100644 --- a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml +++ b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml @@ -21,8 +21,10 @@ matrix_synapse_usage_exporter_container_image_self_build: true matrix_synapse_usage_exporter_container_image_self_build_repo: "https://github.com/loelkes/synapse-usage-exporter.git" matrix_synapse_usage_exporter_container_image_path: "loelkes/synapse-usage-exporter" -matrix_synapse_usage_exporter_container_image: "{{ matrix_synapse_usage_exporter_container_image_name_prefix }}{{ matrix_synapse_usage_exporter_container_image_path }}:{{ matrix_synapse_usage_exporter_container_image_tag }}" -matrix_synapse_usage_exporter_container_image_name_prefix: "{{ 'localhost/' if matrix_synapse_usage_exporter_container_image_self_build else 'docker.io/' }}" +matrix_synapse_usage_exporter_container_image: "{{ matrix_synapse_usage_exporter_container_image_registry_prefix }}{{ matrix_synapse_usage_exporter_container_image_path }}:{{ matrix_synapse_usage_exporter_container_image_tag }}" +matrix_synapse_usage_exporter_container_image_registry_prefix: "{{ 'localhost/' if matrix_synapse_usage_exporter_container_image_self_build else matrix_synapse_usage_exporter_container_image_registry_prefix_upstream }}" +matrix_synapse_usage_exporter_container_image_registry_prefix_upstream: "{{ matrix_synapse_usage_exporter_container_image_registry_prefix_upstream_default }}" +matrix_synapse_usage_exporter_container_image_registry_prefix_upstream_default: "docker.io/" matrix_synapse_usage_exporter_container_image_tag: "{{ 'main' if matrix_synapse_usage_exporter_container_image_self_build else 'latest' }}" matrix_synapse_usage_exporter_container_image_force_pull: "{{ matrix_synapse_usage_exporter_container_image.endswith(':latest') }}" diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml index 0ac9c1f50..22b9df8c4 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml @@ -6,6 +6,9 @@ - install-all - install-synapse-usage-exporter block: + - when: matrix_synapse_usage_exporter_enabled | bool + ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" + - when: matrix_synapse_usage_exporter_enabled | bool ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml new file mode 100644 index 000000000..5609ad241 --- /dev/null +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml @@ -0,0 +1,10 @@ +--- + +- name: (Deprecation) Catch and report renamed matrix-synapse-usage-exporter settings + ansible.builtin.fail: + msg: >- + Your configuration contains a variable, which now has a different name. + Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + when: "item.old in vars" + with_items: + - {'old': 'matrix_synapse_usage_exporter_docker_image_name_prefix', 'new': 'matrix_synapse_usage_exporter_container_image_registry_prefix'} diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 67e198c10..2b469c459 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -93,12 +93,13 @@ matrix_synapse_container_image_customizations_templates_git_repository_keyscan_h # RUN echo 'You do NOT need to include a FROM clause yourself.' matrix_synapse_container_image_customizations_dockerfile_body_custom: '' -matrix_synapse_docker_image: "{{ matrix_synapse_docker_image_name_prefix }}{{ matrix_synapse_docker_image_name }}:{{ matrix_synapse_docker_image_tag }}" -matrix_synapse_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_container_image_self_build else matrix_synapse_docker_image_registry_prefix }}" +matrix_synapse_docker_image: "{{ matrix_synapse_docker_image_registry_prefix }}{{ matrix_synapse_docker_image_name }}:{{ matrix_synapse_docker_image_tag }}" matrix_synapse_docker_image_name: "{{ matrix_synapse_github_org_and_repo }}" matrix_synapse_docker_image_tag: "{{ matrix_synapse_version }}" matrix_synapse_docker_image_force_pull: "{{ matrix_synapse_docker_image.endswith(':latest') }}" -matrix_synapse_docker_image_registry_prefix: ghcr.io/ +matrix_synapse_docker_image_registry_prefix: "{{ 'localhost/' if matrix_synapse_container_image_self_build else matrix_synapse_docker_image_registry_prefix_upstream }}" +matrix_synapse_docker_image_registry_prefix_upstream: "{{ matrix_synapse_docker_image_registry_prefix_upstream_default }}" +matrix_synapse_docker_image_registry_prefix_upstream_default: "ghcr.io/" # matrix_synapse_docker_image_customized is the name of the locally built Synapse image # which adds various customizations on top of the original (upstream) Synapse image. @@ -1410,8 +1411,10 @@ matrix_synapse_ext_media_repo_enabled: false matrix_s3_media_store_enabled: false matrix_s3_media_store_custom_endpoint_enabled: false -matrix_s3_goofys_docker_image: "{{ matrix_s3_goofys_docker_image_name_prefix }}ewoutp/goofys:latest" -matrix_s3_goofys_docker_image_name_prefix: "docker.io/" +matrix_s3_goofys_docker_image: "{{ matrix_s3_goofys_docker_image_registry_prefix }}ewoutp/goofys:latest" +matrix_s3_goofys_docker_image_registry_prefix: "{{ matrix_s3_goofys_docker_image_registry_prefix_upstream }}" +matrix_s3_goofys_docker_image_registry_prefix_upstream: "{{ matrix_s3_goofys_docker_image_registry_prefix_upstream_default }}" +matrix_s3_goofys_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_s3_goofys_docker_image_force_pull: "{{ matrix_s3_goofys_docker_image.endswith(':latest') }}" matrix_s3_media_store_custom_endpoint: "your-custom-endpoint" matrix_s3_media_store_bucket_name: "your-bucket-name" diff --git a/roles/custom/matrix-synapse/tasks/validate_config.yml b/roles/custom/matrix-synapse/tasks/validate_config.yml index e1e6fbe27..8f73ad005 100644 --- a/roles/custom/matrix-synapse/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse/tasks/validate_config.yml @@ -102,6 +102,8 @@ - {'old': 'matrix_synapse_caches_autotuning_target_cache_memory_usage', 'new': 'matrix_synapse_cache_autotuning_target_cache_memory_usage'} - {'old': 'matrix_synapse_caches_autotuning_min_cache_ttl', 'new': 'matrix_synapse_cache_autotuning_min_cache_ttl'} - {'old': 'matrix_synapse_memtotal_kb', 'new': ''} + - {'old': 'matrix_synapse_docker_image_name_prefix', 'new': 'matrix_synapse_docker_image_registry_prefix'} + - {'old': 'matrix_s3_goofys_docker_image_name_prefix', 'new': 'matrix_s3_goofys_docker_image_registry_prefix'} - name: (Deprecation) Catch and report renamed settings in matrix_synapse_configuration_extension_yaml ansible.builtin.fail: diff --git a/roles/custom/matrix-user-verification-service/defaults/main.yml b/roles/custom/matrix-user-verification-service/defaults/main.yml index 510d258da..abd1655c1 100644 --- a/roles/custom/matrix-user-verification-service/defaults/main.yml +++ b/roles/custom/matrix-user-verification-service/defaults/main.yml @@ -13,7 +13,6 @@ matrix_user_verification_service_container_image_self_build: "{{ matrix_architec matrix_user_verification_service_container_image_self_build_repo: "https://github.com/matrix-org/matrix-user-verification-service" matrix_user_verification_service_container_image_self_build_branch: "{{ 'master' if matrix_registration_version == 'latest' else matrix_user_verification_service_version }}" -# Fix version tag # renovate: datasource=docker depName=matrixdotorg/matrix-user-verification-service matrix_user_verification_service_version: "v3.0.0" @@ -25,7 +24,9 @@ matrix_user_verification_service_docker_src_files_path: "{{ matrix_user_verifica # Docker matrix_user_verification_service_docker_image: "{{ matrix_user_verification_service_docker_image_registry_prefix }}matrixdotorg/matrix-user-verification-service:{{ matrix_user_verification_service_version }}" -matrix_user_verification_service_docker_image_registry_prefix: docker.io/ +matrix_user_verification_service_docker_image_registry_prefix: "{{ 'localhost/' if matrix_user_verification_service_container_image_self_build else matrix_user_verification_service_docker_image_registry_prefix_upstream }}" +matrix_user_verification_service_docker_image_registry_prefix_upstream: "{{ matrix_user_verification_service_docker_image_registry_prefix_upstream_default }}" +matrix_user_verification_service_docker_image_registry_prefix_upstream_default: "docker.io/" matrix_user_verification_service_docker_image_force_pull: "{{ matrix_user_verification_service_docker_image.endswith(':latest') }}" # The base container network. It will be auto-created by this role if it doesn't exist already. From b88b6ae7a3f1b58ea61990a3b1b6dc319be0ab3e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 11:18:05 +0200 Subject: [PATCH 712/952] Introduce a new `matrix_container_global_registry_prefix_override` variable and make all roles respect it `matrix_container_global_registry_prefix_override` may look similar to the old `matrix_container_global_registry_prefix` variable (removed in d6bf789710dec1567f47f5d7f3c4911ebafff9ea), but it's different. The old `matrix_container_global_registry_prefix` variable was just a hardcode of `docker.io/` and roles that needed to refer to `docker.io/` could use it. However, this was: - not used by all roles, because some need another registry (not `docker.io/`) - used only by roles within the playbook (`roles/custom`), not external roles Overriding the old `matrix_container_global_registry_prefix` variable was rather pointless, as it didn't cover everything. The new `matrix_container_global_registry_prefix_override` variable, on the other hand, lets you override the registry prefix for all components, regardless of whether they use `docker.io/` or another registry by default. This is useful to people who have somehow mirrored all container images to their own registry, as it provides them with a single variable they can flip to influence the whole playbook. --- group_vars/matrix_servers | 215 +++++++++++++++++- roles/custom/matrix-base/defaults/main.yml | 7 + .../defaults/main.yml | 18 +- .../tasks/setup_install.yml | 22 +- .../tasks/validate_config.yml | 13 +- 5 files changed, 242 insertions(+), 33 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index ee5212f6e..7c38f1710 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -593,6 +593,8 @@ matrix_integration_manager_ui_url: "{{ matrix_dimension_integrations_ui_url if m # We don't enable this by default. matrix_alertmanager_receiver_enabled: false +matrix_alertmanager_receiver_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_alertmanager_receiver_container_image_registry_prefix_upstream_default }}" + matrix_alertmanager_receiver_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_alertmanager_receiver_container_network: "{{ matrix_addons_container_network }}" @@ -676,6 +678,8 @@ matrix_authentication_service_config_email_port: "{{ 8025 if exim_relay_enabled matrix_authentication_service_config_email_mode: "{{ 'plain' if exim_relay_enabled else 'starttls' }}" matrix_authentication_service_config_email_from_address: "{{ exim_relay_sender_address }}" +matrix_authentication_service_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_authentication_service_container_image_registry_prefix_upstream_default }}" + matrix_authentication_service_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_authentication_service_container_network: "{{ matrix_homeserver_container_network }}" @@ -748,6 +752,8 @@ matrix_appservice_discord_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_appservice_discord_database_hostname == postgres_connection_hostname) else []) }} +matrix_appservice_discord_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_discord_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_discord_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9005') if matrix_playbook_service_host_bind_interface_prefix else '' }}" matrix_appservice_discord_container_network: "{{ matrix_addons_container_network }}" @@ -797,6 +803,8 @@ matrix_appservice_webhooks_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_appservice_webhooks_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_webhooks_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_webhooks_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_appservice_webhooks_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ matrix_appservice_webhooks_matrix_port) if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -849,6 +857,8 @@ matrix_appservice_slack_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_appservice_slack_database_hostname == postgres_connection_hostname) else []) }} +matrix_appservice_slack_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_slack_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_slack_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_appservice_slack_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ matrix_appservice_slack_slack_port) if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -906,6 +916,8 @@ matrix_appservice_irc_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_appservice_irc_database_hostname == postgres_connection_hostname) else []) }} +matrix_appservice_irc_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_irc_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_irc_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_appservice_irc_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9999') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -957,6 +969,10 @@ matrix_appservice_kakaotalk_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_appservice_kakaotalk_database_hostname == postgres_connection_hostname) else []) }} +matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_kakaotalk_node_docker_image_registry_prefix_upstream_default }}" + +matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_kakaotalk_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_kakaotalk_container_network: "{{ matrix_addons_container_network }}" matrix_appservice_kakaotalk_container_additional_networks_auto: |- @@ -1002,6 +1018,8 @@ matrix_beeper_linkedin_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_beeper_linkedin_database_hostname == postgres_connection_hostname) else []) }} +matrix_beeper_linkedin_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_beeper_linkedin_docker_image_registry_prefix_upstream_default }}" + matrix_beeper_linkedin_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" matrix_beeper_linkedin_container_network: "{{ matrix_addons_container_network }}" @@ -1061,6 +1079,8 @@ matrix_go_skype_bridge_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_go_skype_bridge_database_hostname == postgres_connection_hostname) else []) }} +matrix_go_skype_bridge_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_go_skype_bridge_docker_image_registry_prefix_upstream_default }}" + matrix_go_skype_bridge_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_go_skype_bridge_container_network: "{{ matrix_addons_container_network }}" @@ -1108,6 +1128,8 @@ matrix_mautrix_bluesky_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_bluesky_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_bluesky_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_bluesky_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_bluesky_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_bluesky_container_network: "{{ matrix_addons_container_network }}" @@ -1171,6 +1193,8 @@ matrix_mautrix_bluesky_database_password: "{{ '%s' | format(matrix_homeserver_ge # We don't enable bridges by default. matrix_mautrix_discord_enabled: false +matrix_mautrix_discord_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_discord_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_discord_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mautrix_discord_container_network: "{{ matrix_addons_container_network }}" @@ -1249,6 +1273,8 @@ matrix_mautrix_slack_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_slack_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_slack_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_slack_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_slack_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mautrix_slack_container_network: "{{ matrix_addons_container_network }}" @@ -1307,6 +1333,8 @@ matrix_mautrix_facebook_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_facebook_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_facebook_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_facebook_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_facebook_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9008') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -1381,6 +1409,8 @@ matrix_mautrix_googlechat_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_googlechat_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_googlechat_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_googlechat_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_googlechat_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_googlechat_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9007') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -1459,6 +1489,8 @@ matrix_mautrix_instagram_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_instagram_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_instagram_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_instagram_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_instagram_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_instagram_container_network: "{{ matrix_addons_container_network }}" @@ -1525,6 +1557,8 @@ matrix_mautrix_signal_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_signal_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_signal_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_signal_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_signal_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mautrix_signal_container_network: "{{ matrix_addons_container_network }}" @@ -1599,6 +1633,8 @@ matrix_mautrix_meta_messenger_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_meta_messenger_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_meta_messenger_container_image_registry_prefix_upstream_default }}" + matrix_mautrix_meta_messenger_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_meta_messenger_container_network: "{{ matrix_addons_container_network }}" @@ -1673,6 +1709,8 @@ matrix_mautrix_meta_instagram_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_meta_instagram_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_meta_instagram_container_image_registry_prefix_upstream_default }}" + matrix_mautrix_meta_instagram_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_meta_instagram_container_network: "{{ matrix_addons_container_network }}" @@ -1749,10 +1787,14 @@ matrix_mautrix_telegram_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_telegram_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default }}" + +matrix_mautrix_telegram_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_telegram_docker_image_registry_prefix_upstream_default }}" + # Images are multi-arch (amd64 and arm64, but not arm32). matrix_mautrix_telegram_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" -matrix_telegram_lottieconverter_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" -matrix_telegram_lottieconverter_container_image_self_build_mask_arch: "{{ matrix_architecture != 'amd64' }}" +matrix_mautrix_telegram_lottieconverter_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" +matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch: "{{ matrix_architecture != 'amd64' }}" matrix_mautrix_telegram_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9006') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -1829,6 +1871,8 @@ matrix_mautrix_twitter_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_twitter_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_twitter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_twitter_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_twitter_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_mautrix_twitter_container_network: "{{ matrix_addons_container_network }}" @@ -1899,6 +1943,8 @@ matrix_mautrix_gmessages_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname) else []) }} +matrix_mautrix_gmessages_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_gmessages_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_gmessages_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mautrix_gmessages_container_network: "{{ matrix_addons_container_network }}" @@ -1976,6 +2022,8 @@ matrix_mautrix_wsproxy_hostname: "wsproxy.{{ matrix_mautrix_wsproxy_homeserver_d matrix_mautrix_wsproxy_syncproxy_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}" +matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_wsproxy_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_wsproxy_container_network: "{{ matrix_addons_container_network }}" matrix_mautrix_wsproxy_container_additional_networks: | @@ -2019,6 +2067,8 @@ matrix_wechat_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_wechat_database_hostname == postgres_connection_hostname) else []) }} +matrix_wechat_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_wechat_container_image_registry_prefix_upstream_default }}" + matrix_wechat_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_wechat_agent_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" @@ -2063,6 +2113,8 @@ matrix_wechat_database_password: "{{ '%s' | format(matrix_homeserver_generic_sec # We don't enable bridges by default. matrix_mautrix_whatsapp_enabled: false +matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mautrix_whatsapp_docker_image_registry_prefix_upstream_default }}" + matrix_mautrix_whatsapp_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mautrix_whatsapp_container_network: "{{ matrix_addons_container_network }}" @@ -2140,6 +2192,8 @@ matrix_sms_bridge_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname) else []) }} +matrix_sms_bridge_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_sms_bridge_docker_image_registry_prefix_upstream_default }}" + matrix_sms_bridge_container_network: "{{ matrix_addons_container_network }}" matrix_sms_bridge_container_additional_networks_auto: |- @@ -2175,6 +2229,8 @@ matrix_heisenbridge_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_heisenbridge_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_heisenbridge_docker_image_registry_prefix_upstream_default }}" + matrix_heisenbridge_container_network: "{{ matrix_addons_container_network }}" matrix_heisenbridge_container_additional_networks_auto: |- @@ -2212,6 +2268,8 @@ matrix_heisenbridge_homeserver_url: "{{ matrix_addons_homeserver_client_api_url # We don't enable bridges by default. matrix_hookshot_enabled: false +matrix_hookshot_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_hookshot_docker_image_registry_prefix_upstream_default }}" + matrix_hookshot_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_hookshot_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'hookshot.as.tok', rounds=655555) | to_uuid }}" @@ -2296,6 +2354,8 @@ matrix_mx_puppet_slack_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_slack_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_slack_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_slack_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_slack_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_mx_puppet_slack_container_network: "{{ matrix_addons_container_network }}" @@ -2354,6 +2414,8 @@ matrix_mx_puppet_twitter_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_twitter_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_twitter_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_twitter_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_mx_puppet_twitter_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '' ~ matrix_mx_puppet_twitter_appservice_port) if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -2413,6 +2475,8 @@ matrix_mx_puppet_instagram_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_instagram_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_instagram_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_instagram_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_mx_puppet_instagram_container_network: "{{ matrix_addons_container_network }}" @@ -2462,6 +2526,8 @@ matrix_mx_puppet_discord_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_discord_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_discord_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_discord_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_discord_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_mx_puppet_discord_container_network: "{{ matrix_addons_container_network }}" @@ -2511,6 +2577,8 @@ matrix_mx_puppet_steam_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_steam_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_steam_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_steam_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_steam_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_mx_puppet_steam_container_network: "{{ matrix_addons_container_network }}" @@ -2561,6 +2629,8 @@ matrix_mx_puppet_groupme_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_mx_puppet_groupme_database_hostname == postgres_connection_hostname) else []) }} +matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_mx_puppet_groupme_docker_image_registry_prefix_upstream_default }}" + matrix_mx_puppet_groupme_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_mx_puppet_groupme_container_network: "{{ matrix_addons_container_network }}" @@ -2603,6 +2673,8 @@ matrix_mx_puppet_groupme_database_password: "{{ '%s' | format(matrix_homeserver_ # We don't enable bridges by default. matrix_postmoogle_enabled: false +matrix_postmoogle_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_postmoogle_docker_image_registry_prefix_upstream_default }}" + matrix_postmoogle_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_postmoogle_ssl_path: |- @@ -2686,6 +2758,8 @@ matrix_bot_matrix_reminder_bot_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if postgres_enabled and matrix_bot_matrix_reminder_bot_database_hostname == postgres_connection_hostname else []) }} +matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_matrix_reminder_bot_docker_image_registry_prefix_upstream_default }}" + matrix_bot_matrix_reminder_bot_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_bot_matrix_reminder_bot_container_network: "{{ matrix_addons_container_network }}" @@ -2731,6 +2805,8 @@ matrix_bot_matrix_registration_bot_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream_default }}" + matrix_bot_matrix_registration_bot_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" matrix_bot_matrix_registration_bot_container_network: "{{ matrix_addons_container_network }}" @@ -2778,6 +2854,8 @@ matrix_bot_maubot_homeserver_secret: |- }[matrix_homeserver_implementation] | default('') }} +matrix_bot_maubot_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_maubot_docker_image_registry_prefix_upstream_default }}" + matrix_bot_maubot_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" matrix_bot_maubot_container_management_interface_http_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '' ~ matrix_bot_maubot_server_port | string) if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -2834,6 +2912,8 @@ matrix_bot_honoroit_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if postgres_enabled and matrix_bot_honoroit_database_hostname == postgres_connection_hostname else []) }} +matrix_bot_honoroit_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_honoroit_docker_image_registry_prefix_upstream_default }}" + matrix_bot_honoroit_container_network: "{{ matrix_addons_container_network }}" matrix_bot_honoroit_container_additional_networks: | @@ -2888,6 +2968,8 @@ matrix_bot_buscarron_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_bot_buscarron_database_hostname == postgres_connection_hostname) else []) }} +matrix_bot_buscarron_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_buscarron_docker_image_registry_prefix_upstream_default }}" + matrix_bot_buscarron_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_bot_buscarron_container_network: "{{ matrix_addons_container_network }}" @@ -2931,6 +3013,8 @@ matrix_bot_buscarron_database_password: "{{ '%s' | format(matrix_homeserver_gene # We don't enable bots by default. matrix_bot_baibot_enabled: false +matrix_bot_baibot_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_baibot_container_image_registry_prefix_upstream_default }}" + matrix_bot_baibot_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_bot_baibot_systemd_required_services_list_auto: | @@ -2964,6 +3048,8 @@ matrix_bot_baibot_container_additional_networks_auto: |- # We don't enable bots by default. matrix_bot_chatgpt_enabled: false +matrix_bot_chatgpt_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_chatgpt_container_image_registry_prefix_upstream_default }}" + matrix_bot_chatgpt_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_bot_chatgpt_container_network: "{{ matrix_addons_container_network }}" @@ -2998,6 +3084,8 @@ matrix_bot_go_neb_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_bot_go_neb_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_go_neb_container_image_registry_prefix_upstream_default }}" + matrix_bot_go_neb_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '4050') if matrix_playbook_service_host_bind_interface_prefix else '' }}" matrix_bot_go_neb_container_network: "{{ matrix_addons_container_network }}" @@ -3039,6 +3127,8 @@ matrix_bot_mjolnir_systemd_required_services_list_auto: | (['matrix-pantalaimon.service'] if matrix_bot_mjolnir_pantalaimon_use else []) }} +matrix_bot_mjolnir_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_mjolnir_docker_image_registry_prefix_upstream_default }}" + matrix_bot_mjolnir_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_bot_mjolnir_container_network: "{{ matrix_addons_container_network }}" @@ -3075,6 +3165,8 @@ matrix_bot_draupnir_systemd_required_services_list_auto: | (['matrix-pantalaimon.service'] if matrix_bot_draupnir_pantalaimon_use else []) }} +matrix_bot_draupnir_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_bot_draupnir_docker_image_registry_prefix_upstream_default }}" + matrix_bot_draupnir_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_bot_draupnir_container_network: "{{ matrix_addons_container_network }}" @@ -3123,6 +3215,8 @@ matrix_appservice_draupnir_for_all_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_appservice_draupnir_for_all_database_hostname == postgres_connection_hostname) else []) }} +matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_appservice_draupnir_for_all_docker_image_registry_prefix_upstream_default }}" + matrix_appservice_draupnir_for_all_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_appservice_draupnir_for_all_container_network: "{{ matrix_addons_container_network }}" @@ -3180,6 +3274,8 @@ matrix_pantalaimon_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_pantalaimon_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_pantalaimon_docker_image_registry_prefix_upstream_default }}" + matrix_pantalaimon_container_network: "{{ matrix_homeserver_container_network }}" matrix_pantalaimon_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" @@ -3210,6 +3306,8 @@ backup_borg_username: "{{ matrix_user_username }}" backup_borg_uid: "{{ matrix_user_uid }}" backup_borg_gid: "{{ matrix_user_gid }}" +backup_borg_docker_image_registry_prefix_upstream: "{{ backup_borg_docker_image_registry_prefix_upstream_default }}" + backup_borg_container_network: "{{ postgres_container_network if postgres_enabled else backup_borg_identifier }}" backup_borg_postgresql_version_detection_postgres_role_name: "{{ 'galaxy/postgres' if postgres_enabled else '' }}" @@ -3260,6 +3358,8 @@ matrix_cactus_comments_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_cactus_comments_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_cactus_comments_docker_image_registry_prefix_upstream_default }}" + matrix_cactus_comments_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" matrix_cactus_comments_container_network: "{{ matrix_addons_container_network }}" @@ -3290,6 +3390,8 @@ matrix_cactus_comments_client_enabled: "{{ matrix_cactus_comments_enabled }}" matrix_cactus_comments_client_hostname: "{{ matrix_server_fqn_matrix }}" +matrix_cactus_comments_client_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_cactus_comments_client_container_image_registry_prefix_upstream_default }}" + matrix_cactus_comments_client_container_network: "{{ matrix_addons_container_network }}" matrix_cactus_comments_client_container_additional_networks_auto: |- @@ -3323,6 +3425,8 @@ matrix_corporal_systemd_required_services_list_auto: | (['matrix-' + matrix_homeserver_implementation + '.service']) }} +matrix_corporal_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_corporal_docker_image_registry_prefix_upstream_default }}" + matrix_corporal_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" matrix_corporal_container_http_gateway_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '41080') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3375,6 +3479,8 @@ matrix_rageshake_container_image_self_build: "{{ matrix_architecture not in ['am matrix_rageshake_hostname: "{{ matrix_server_fqn_rageshake }}" +matrix_rageshake_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_rageshake_container_image_registry_prefix_upstream_default }}" + matrix_rageshake_container_network: matrix-rageshake matrix_rageshake_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" @@ -3400,6 +3506,8 @@ matrix_rageshake_container_labels_traefik_tls_certResolver: "{{ traefik_certReso matrix_coturn_enabled: true +matrix_coturn_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_coturn_docker_image_registry_prefix_upstream_default }}" + matrix_coturn_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" # We make the assumption that `ansible_host` points to an external IP address, which may not always be the case. @@ -3471,11 +3579,13 @@ matrix_coturn_systemd_required_services_list: | matrix_dimension_enabled: false -matrix_dimension_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" - matrix_dimension_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" matrix_dimension_hostname: "{{ matrix_server_fqn_dimension }}" +matrix_dimension_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_dimension_docker_image_registry_prefix_upstream_default }}" + +matrix_dimension_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" + matrix_dimension_container_network: "{{ matrix_addons_container_network }}" # Dimension is connected both to `matrix_addons_homeserver_container_network` and `matrix_homeserver_container_network`, @@ -3548,6 +3658,8 @@ etherpad_framing_enabled: "{{ matrix_dimension_enabled or jitsi_enabled }}" etherpad_hostname: "{{ matrix_server_fqn_etherpad }}" +etherpad_container_image_registry_prefix_upstream: "{{ etherpad_container_image_registry_prefix_upstream_default }}" + etherpad_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" etherpad_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '9001') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3592,6 +3704,8 @@ etherpad_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_k matrix_dynamic_dns_enabled: false +matrix_dynamic_dns_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_dynamic_dns_docker_image_registry_prefix_upstream_default }}" + matrix_dynamic_dns_container_network: matrix-dynamic-dns ###################################################################### @@ -3613,6 +3727,8 @@ matrix_email2matrix_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_email2matrix_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_email2matrix_docker_image_registry_prefix_upstream_default }}" + matrix_email2matrix_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" matrix_email2matrix_container_network: "{{ matrix_addons_container_network }}" @@ -3649,6 +3765,8 @@ jitsi_gid: "{{ matrix_user_gid }}" jitsi_user_username: "{{ matrix_user_username }}" +jitsi_web_container_image_registry_prefix_upstream: "{{ jitsi_web_container_image_registry_prefix_upstream_default }}" + jitsi_web_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '13080') if matrix_playbook_service_host_bind_interface_prefix else '' }}" jitsi_web_container_additional_networks_auto: | @@ -3656,6 +3774,8 @@ jitsi_web_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} +jitsi_jvb_container_image_registry_prefix_upstream: "{{ jitsi_jvb_container_image_registry_prefix_upstream_default }}" + jitsi_jvb_container_colibri_ws_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '13090') if matrix_playbook_service_host_bind_interface_prefix else '' }}" jitsi_jvb_container_additional_networks_auto: | @@ -3663,6 +3783,8 @@ jitsi_jvb_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} +jitsi_prosody_container_image_registry_prefix_upstream: "{{ jitsi_prosody_container_image_registry_prefix_upstream_default }}" + jitsi_prosody_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '5280') if matrix_playbook_service_host_bind_interface_prefix else '' }}" jitsi_prosody_container_additional_networks_auto: | @@ -3670,6 +3792,8 @@ jitsi_prosody_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} +jitsi_jicofo_container_image_registry_prefix_upstream: "{{ jitsi_jicofo_container_image_registry_prefix_upstream_default }}" + jitsi_container_labels_traefik_enabled: "{{ matrix_playbook_traefik_labels_enabled }}" jitsi_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" jitsi_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}" @@ -3743,6 +3867,8 @@ matrix_ldap_registration_proxy_systemd_required_services_list_auto: | matrix_addons_homeserver_systemd_services_list }} +matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_ldap_registration_proxy_docker_image_registry_prefix_upstream_default }}" + matrix_ldap_registration_proxy_container_network: "{{ matrix_addons_container_network }}" matrix_ldap_registration_proxy_container_additional_networks_auto: |- @@ -3783,12 +3909,14 @@ exim_relay_base_path: "{{ matrix_base_data_path }}/exim-relay" exim_relay_uid: "{{ matrix_user_uid }}" exim_relay_gid: "{{ matrix_user_gid }}" -exim_relay_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" - exim_relay_hostname: "{{ matrix_server_fqn_matrix }}" exim_relay_sender_address: "matrix@{{ exim_relay_hostname }}" +exim_relay_container_image_registry_prefix_upstream: "{{ exim_relay_container_image_registry_prefix_upstream_default }}" + +exim_relay_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" + ######################################################################## # # # /exim-relay # @@ -3816,6 +3944,8 @@ matrix_ma1sd_enabled: false matrix_ma1sd_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" matrix_ma1sd_hostname: "{{ matrix_server_fqn_matrix }}" +matrix_ma1sd_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_ma1sd_docker_image_registry_prefix_upstream_default }}" + matrix_ma1sd_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_ma1sd_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '' ~ matrix_ma1sd_container_port | string) if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3890,6 +4020,8 @@ matrix_ma1sd_database_password: "{{ '%s' | format(matrix_homeserver_generic_secr matrix_media_repo_enabled: false +matrix_media_repo_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_media_repo_docker_image_registry_prefix_upstream_default }}" + matrix_media_repo_container_network: "{{ matrix_homeserver_container_network }}" matrix_media_repo_container_additional_networks: | @@ -3996,6 +4128,9 @@ postgres_systemd_services_to_stop_for_maintenance_list_auto: "{{ devture_systemd postgres_max_connections: "{{ 500 if matrix_synapse_workers_enabled else 200 }}" +postgres_container_image_registry_prefix_upstream: "{{ postgres_container_image_registry_prefix_upstream_default }}" +postgres_pgloader_container_image_registry_prefix_upstream: "{{ postgres_pgloader_container_image_registry_prefix_upstream_default }}" + postgres_managed_databases_auto: | {{ ([{ @@ -4316,6 +4451,8 @@ postgres_backup_systemd_required_services_list_auto: | ([(postgres_identifier + '.service')] if (postgres_enabled and postgres_backup_connection_hostname == postgres_connection_hostname) else []) }} +postgres_backup_container_image_registry_prefix_upstream: "{{ postgres_backup_container_image_registry_prefix_upstream_default }}" + postgres_backup_container_network: "{{ (postgres_container_network if (postgres_enabled and postgres_backup_connection_hostname == postgres_connection_hostname) else postgres_backup_identifier) }}" postgres_backup_container_additional_networks_auto: |- @@ -4356,6 +4493,8 @@ matrix_sygnal_metrics_prometheus_enabled: "{{ prometheus_enabled or matrix_metri matrix_sygnal_hostname: "{{ matrix_server_fqn_sygnal }}" +matrix_sygnal_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_sygnal_docker_image_registry_prefix_upstream_default }}" + matrix_sygnal_container_network: "{{ matrix_homeserver_container_network }}" matrix_sygnal_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" @@ -4390,6 +4529,8 @@ ntfy_gid: "{{ matrix_user_gid }}" ntfy_hostname: "{{ matrix_server_fqn_ntfy }}" +ntfy_container_image_registry_prefix_upstream: "{{ ntfy_container_image_registry_prefix_upstream_default }}" + ntfy_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" ntfy_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '2586') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4428,6 +4569,8 @@ valkey_base_path: "{{ matrix_base_data_path }}/valkey" valkey_arch: "{{ matrix_architecture }}" +valkey_container_image_registry_prefix_upstream: "{{ valkey_container_image_registry_prefix_upstream_default }}" + ###################################################################### # # valkey @@ -4447,6 +4590,8 @@ matrix_client_element_enabled: true matrix_client_element_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" +matrix_client_element_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_client_element_docker_image_registry_prefix_upstream_default }}" + matrix_client_element_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_client_element_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8765') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4499,6 +4644,8 @@ matrix_client_element_jitsi_preferred_domain: "{{ matrix_server_fqn_jitsi if jit matrix_client_hydrogen_enabled: false +matrix_client_hydrogen_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_client_hydrogen_docker_image_registry_prefix_upstream_default }}" + matrix_client_hydrogen_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_client_hydrogen_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8768') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4535,6 +4682,8 @@ matrix_client_hydrogen_self_check_validate_certificates: "{{ matrix_playbook_ssl matrix_client_cinny_enabled: false +matrix_client_cinny_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_client_cinny_docker_image_registry_prefix_upstream_default }}" + matrix_client_cinny_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_client_cinny_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8080') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4573,6 +4722,8 @@ matrix_client_schildichat_enabled: false matrix_client_schildichat_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" +matrix_client_schildichat_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_client_schildichat_docker_image_registry_prefix_upstream_default }}" + matrix_client_schildichat_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_client_schildichat_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8765') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4624,6 +4775,8 @@ matrix_client_fluffychat_enabled: false matrix_client_fluffychat_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}" +matrix_client_fluffychat_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_client_fluffychat_docker_image_registry_prefix_upstream_default }}" + matrix_client_fluffychat_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_client_fluffychat_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8770') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -4659,6 +4812,10 @@ matrix_synapse_gid: "{{ matrix_user_gid }}" matrix_synapse_federation_enabled: "{{ matrix_homeserver_federation_enabled }}" +matrix_synapse_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_docker_image_registry_prefix_upstream_default }}" + +matrix_s3_goofys_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_s3_goofys_docker_image_registry_prefix_upstream_default }}" + matrix_synapse_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" matrix_synapse_account_threepid_delegates_msisdn_mas1sd_url: "{{ ('http://matrix-ma1sd:' + matrix_ma1sd_container_port| string) }}" @@ -4823,6 +4980,8 @@ matrix_synapse_auto_compressor_gid: "{{ matrix_user_gid }}" matrix_synapse_auto_compressor_postgres_image: "{{ postgres_container_image_to_use }}" +matrix_synapse_auto_compressor_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_auto_compressor_container_image_registry_prefix_upstream_default }}" + matrix_synapse_auto_compressor_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" matrix_synapse_auto_compressor_container_network: "{{ (postgres_container_network if (postgres_enabled and matrix_synapse_auto_compressor_database_hostname == matrix_synapse_database_host and matrix_synapse_database_host == postgres_connection_hostname) else 'matrix-synapse-auto-compressor') }}" @@ -4853,6 +5012,8 @@ matrix_synapse_auto_compressor_systemd_required_services_list_auto: | matrix_synapse_reverse_proxy_companion_enabled: "{{ matrix_synapse_enabled and matrix_synapse_workers_enabled }}" +matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_reverse_proxy_companion_container_image_registry_prefix_upstream_default }}" + matrix_synapse_reverse_proxy_companion_container_network: "{{ matrix_synapse_container_network }}" matrix_synapse_reverse_proxy_companion_container_additional_networks_auto: | @@ -4923,6 +5084,8 @@ matrix_synapse_reverse_proxy_companion_access_log_syslog_integration_server_port matrix_synapse_admin_enabled: false +matrix_synapse_admin_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_admin_docker_image_registry_prefix_upstream_default }}" + matrix_synapse_admin_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8766') if matrix_playbook_service_host_bind_interface_prefix else '' }}" matrix_synapse_admin_container_image_self_build: "{{ matrix_architecture not in ['arm64', 'amd64'] }}" @@ -5139,6 +5302,8 @@ matrix_synapse_admin_config_asManagedUsers_auto: | matrix_synapse_usage_exporter_enabled: false +matrix_synapse_usage_exporter_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_synapse_usage_exporter_container_image_registry_prefix_upstream_default }}" + matrix_synapse_usage_exporter_container_network: "{{ matrix_monitoring_container_network }}" matrix_synapse_usage_exporter_container_additional_networks: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" @@ -5156,7 +5321,7 @@ matrix_synapse_usage_exporter_container_labels_traefik_tls_certResolver: "{{ tra ###################################################################### # -# etke/prometheus_node_exporter +# prometheus_node_exporter # ###################################################################### @@ -5171,6 +5336,8 @@ prometheus_node_exporter_gid: "{{ matrix_user_gid }}" prometheus_node_exporter_hostname: "{{ matrix_server_fqn_matrix }}" +prometheus_node_exporter_docker_image_registry_prefix_upstream: "{{ prometheus_node_exporter_docker_image_registry_prefix_upstream_default }}" + prometheus_node_exporter_container_network: "{{ matrix_monitoring_container_network }}" prometheus_node_exporter_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" @@ -5185,14 +5352,14 @@ prometheus_node_exporter_container_labels_metrics_middleware_basic_auth_users: " ###################################################################### # -# /etke/prometheus_node_exporter +# /prometheus_node_exporter # ###################################################################### ###################################################################### # -# etke/prometheus_postgres_exporter +# prometheus_postgres_exporter # ###################################################################### @@ -5207,6 +5374,8 @@ prometheus_postgres_exporter_gid: "{{ matrix_user_gid }}" prometheus_postgres_exporter_hostname: "{{ matrix_server_fqn_matrix }}" +prometheus_postgres_exporter_docker_image_registry_prefix_upstream: "{{ prometheus_postgres_exporter_docker_image_registry_prefix_upstream_default }}" + prometheus_postgres_exporter_container_network: "{{ matrix_monitoring_container_network }}" prometheus_postgres_exporter_container_additional_networks: | @@ -5236,7 +5405,7 @@ prometheus_postgres_exporter_systemd_required_services_list_auto: | ###################################################################### # -# /etke/prometheus_postgres_exporter +# /prometheus_postgres_exporter # ###################################################################### @@ -5253,6 +5422,8 @@ matrix_prometheus_nginxlog_exporter_identifier: matrix-prometheus-nginxlog-expor matrix_prometheus_nginxlog_exporter_hostname: "{{ matrix_server_fqn_matrix }}" +matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_prometheus_nginxlog_exporter_docker_image_registry_prefix_upstream_default }}" + matrix_prometheus_nginxlog_exporter_container_network: "{{ matrix_monitoring_container_network }}" matrix_prometheus_nginxlog_exporter_container_additional_networks_auto: |- @@ -5295,6 +5466,8 @@ prometheus_base_path: "{{ matrix_base_data_path }}/prometheus" prometheus_uid: "{{ matrix_user_uid }}" prometheus_gid: "{{ matrix_user_gid }}" +prometheus_container_image_registry_prefix_upstream: "{{ prometheus_container_image_registry_prefix_upstream_default }}" + prometheus_container_network: "{{ matrix_monitoring_container_network }}" prometheus_container_additional_networks_auto: | @@ -5404,6 +5577,8 @@ grafana_hostname: "{{ matrix_server_fqn_grafana }}" grafana_base_path: "{{ matrix_base_data_path }}/grafana" +grafana_container_image_registry_prefix_upstream: "{{ grafana_container_image_registry_prefix_upstream_default }}" + grafana_container_network: "{{ matrix_monitoring_container_network }}" grafana_container_additional_networks_auto: | @@ -5492,6 +5667,8 @@ matrix_registration_systemd_required_services_list_auto: | ([postgres_identifier ~ '.service'] if (postgres_enabled and matrix_registration_database_hostname == postgres_connection_hostname) else []) }} +matrix_registration_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_registration_docker_image_registry_prefix_upstream_default }}" + matrix_registration_container_image_self_build: "{{ matrix_architecture != 'amd64' }}" matrix_registration_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '8767') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -5557,6 +5734,8 @@ matrix_sliding_sync_hostname: "{{ matrix_server_fqn_matrix }}" matrix_sliding_sync_path_prefix: /sliding-sync +matrix_sliding_sync_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_sliding_sync_container_image_registry_prefix_upstream_default }}" + matrix_sliding_sync_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_sliding_sync_container_network: "{{ matrix_homeserver_container_network }}" @@ -5618,6 +5797,8 @@ matrix_dendrite_hostname: "{{ matrix_server_fqn_matrix }}" matrix_dendrite_federation_enabled: "{{ matrix_homeserver_federation_enabled }}" +matrix_dendrite_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_dendrite_docker_image_registry_prefix_upstream_default }}" + matrix_dendrite_container_network: "{{ matrix_homeserver_container_network }}" matrix_dendrite_container_additional_networks_auto: | @@ -5706,6 +5887,8 @@ matrix_conduit_hostname: "{{ matrix_server_fqn_matrix }}" matrix_conduit_allow_federation: "{{ matrix_homeserver_federation_enabled }}" +matrix_conduit_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_conduit_docker_image_registry_prefix_upstream_default }}" + matrix_conduit_container_network: "{{ matrix_homeserver_container_network }}" matrix_conduit_container_additional_networks_auto: | @@ -5754,6 +5937,8 @@ matrix_conduwuit_hostname: "{{ matrix_server_fqn_matrix }}" matrix_conduwuit_config_allow_federation: "{{ matrix_homeserver_federation_enabled }}" +matrix_conduwuit_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_conduwuit_docker_image_registry_prefix_upstream_default }}" + matrix_conduwuit_container_network: "{{ matrix_homeserver_container_network }}" matrix_conduwuit_container_additional_networks_auto: | @@ -5877,6 +6062,8 @@ matrix_user_verification_service_systemd_required_services_list: | (['matrix-' + matrix_homeserver_implementation + '.service']) }} +matrix_user_verification_service_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_user_verification_service_docker_image_registry_prefix_upstream_default }}" + matrix_user_verification_service_container_network: "{{ matrix_addons_container_network }}" matrix_user_verification_service_container_additional_networks: | @@ -5919,6 +6106,8 @@ matrix_user_verification_service_uvs_auth_token: "{{ '%s' | format(matrix_homese matrix_static_files_enabled: true +matrix_static_files_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_static_files_container_image_registry_prefix_upstream_default }}" + matrix_static_files_container_network: "{{ (matrix_static_files_identifier if matrix_playbook_reverse_proxy_type == 'none' else matrix_playbook_reverse_proxy_container_network) }}" matrix_static_files_container_labels_traefik_enabled: "{{ matrix_playbook_traefik_labels_enabled }}" @@ -5983,6 +6172,8 @@ container_socket_proxy_gid: "{{ matrix_user_gid }}" # Traefik requires read access to the containers APIs to do its job container_socket_proxy_api_containers_enabled: true +container_socket_proxy_container_image_registry_prefix_upstream: "{{ container_socket_proxy_container_image_registry_prefix_upstream_default }}" + ######################################################################## # # # /container-socket-proxy # @@ -6018,6 +6209,8 @@ traefik_additional_entrypoints_auto: | traefik_config_providers_docker_endpoint: "{{ container_socket_proxy_endpoint if container_socket_proxy_enabled else 'unix:///var/run/docker.sock' }}" +traefik_container_image_registry_prefix_upstream: "{{ traefik_container_image_registry_prefix_upstream_default }}" + traefik_container_additional_networks_auto: | {{ ([container_socket_proxy_container_network] if container_socket_proxy_enabled else []) @@ -6054,6 +6247,8 @@ traefik_certs_dumper_gid: "{{ matrix_user_gid }}" traefik_certs_dumper_ssl_dir_path: "{{ traefik_ssl_dir_path if traefik_enabled else '' }}" +traefik_certs_dumper_container_image_registry_prefix_upstream: "{{ traefik_certs_dumper_container_image_registry_prefix_upstream_default }}" + ######################################################################## # # # /traefik_certs_dumper # diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index 1741924af..63027e487 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -136,6 +136,13 @@ matrix_architecture: "{{ 'amd64' if ansible_architecture == 'x86_64' else ('arm6 # We just remap from our `matrix_architecture` values to what Debian and possibly other distros call things. matrix_debian_arch: "{{ 'armhf' if matrix_architecture == 'arm32' else matrix_architecture }}" +# If specified, the playbook will override the default registry prefix for all components. +# +# This is to be used when you've mirrored all the necessary container images (from their respective registries) by yourself. +# +# Example value: "registry.example.com/" (note the trailing `/`). +matrix_container_global_registry_prefix_override: "" + matrix_user_username: "matrix" matrix_user_groupname: "matrix" diff --git a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml index a876a6587..01917528f 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml @@ -9,15 +9,15 @@ matrix_mautrix_telegram_scheme: https matrix_mautrix_telegram_hostname: '' matrix_mautrix_telegram_path_prefix: '' -matrix_telegram_lottieconverter_container_image_self_build: false -matrix_telegram_lottieconverter_container_image_self_build_mask_arch: false -matrix_telegram_lottieconverter_docker_repo: "https://mau.dev/tulir/lottieconverter.git" -matrix_telegram_lottieconverter_docker_repo_version: "master" -matrix_telegram_lottieconverter_docker_src_files_path: "{{ matrix_base_data_path }}/lotticonverter/docker-src" -matrix_telegram_lottieconverter_docker_image: "{{ matrix_telegram_lottieconverter_docker_image_registry_prefix }}tulir/lottieconverter:alpine-3.16" # needs to be adjusted according to the FROM clause of Dockerfile of mautrix-telegram -matrix_telegram_lottieconverter_docker_image_registry_prefix: "{{ 'localhost/' if matrix_telegram_lottieconverter_container_image_self_build else matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream }}" -matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream: "{{ matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default }}" -matrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" +matrix_mautrix_telegram_lottieconverter_container_image_self_build: false +matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch: false +matrix_mautrix_telegram_lottieconverter_docker_repo: "https://mau.dev/tulir/lottieconverter.git" +matrix_mautrix_telegram_lottieconverter_docker_repo_version: "master" +matrix_mautrix_telegram_lottieconverter_docker_src_files_path: "{{ matrix_base_data_path }}/lotticonverter/docker-src" +matrix_mautrix_telegram_lottieconverter_docker_image: "{{ matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix }}tulir/lottieconverter:alpine-3.16" # needs to be adjusted according to the FROM clause of Dockerfile of mautrix-telegram +matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix: "{{ 'localhost/' if matrix_mautrix_telegram_lottieconverter_container_image_self_build else matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream }}" +matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream: "{{ matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default }}" +matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix_upstream_default: "dock.mau.dev/" matrix_mautrix_telegram_container_image_self_build: false matrix_mautrix_telegram_docker_repo: "https://mau.dev/mautrix/telegram.git" diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml index c73468bb8..4c9aa8558 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml @@ -55,26 +55,26 @@ - name: Ensure lottieconverter is present when self-building ansible.builtin.git: - repo: "{{ matrix_telegram_lottieconverter_docker_repo }}" - version: "{{ matrix_telegram_lottieconverter_docker_repo_version }}" - dest: "{{ matrix_telegram_lottieconverter_docker_src_files_path }}" + repo: "{{ matrix_mautrix_telegram_lottieconverter_docker_repo }}" + version: "{{ matrix_mautrix_telegram_lottieconverter_docker_repo_version }}" + dest: "{{ matrix_mautrix_telegram_lottieconverter_docker_src_files_path }}" force: "yes" become: true become_user: "{{ matrix_user_username }}" - register: matrix_telegram_lottieconverter_git_pull_results - when: "matrix_telegram_lottieconverter_container_image_self_build | bool and matrix_mautrix_telegram_container_image_self_build | bool" + register: matrix_mautrix_telegram_lottieconverter_git_pull_results + when: "matrix_mautrix_telegram_lottieconverter_container_image_self_build | bool and matrix_mautrix_telegram_container_image_self_build | bool" - name: Ensure lottieconverter Docker image is built community.docker.docker_image: - name: "{{ matrix_telegram_lottieconverter_docker_image }}" + name: "{{ matrix_mautrix_telegram_lottieconverter_docker_image }}" source: build - force_source: "{{ matrix_telegram_lottieconverter_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_telegram_lottieconverter_git_pull_results.changed }}" + force_source: "{{ matrix_mautrix_telegram_lottieconverter_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" + force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_mautrix_telegram_lottieconverter_git_pull_results.changed }}" build: dockerfile: Dockerfile - path: "{{ matrix_telegram_lottieconverter_docker_src_files_path }}" + path: "{{ matrix_mautrix_telegram_lottieconverter_docker_src_files_path }}" pull: true - when: "matrix_telegram_lottieconverter_container_image_self_build | bool and matrix_telegram_lottieconverter_git_pull_results.changed and matrix_mautrix_telegram_container_image_self_build | bool" + when: "matrix_mautrix_telegram_lottieconverter_container_image_self_build | bool and matrix_mautrix_telegram_lottieconverter_git_pull_results.changed and matrix_mautrix_telegram_container_image_self_build | bool" - name: Ensure matrix-mautrix-telegram repository is present when self-building ansible.builtin.git: @@ -96,7 +96,7 @@ build: dockerfile: Dockerfile path: "{{ matrix_mautrix_telegram_docker_src_files_path }}" - pull: "{{ not matrix_telegram_lottieconverter_container_image_self_build_mask_arch | bool }}" + pull: "{{ not matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch | bool }}" args: TARGETARCH: "" when: "matrix_mautrix_telegram_container_image_self_build | bool and matrix_mautrix_telegram_git_pull_results.changed" diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml index 8db84dbd0..c4a48110c 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml @@ -28,8 +28,15 @@ with_items: - {'old': 'matrix_mautrix_telegram_container_exposed_port_number', 'new': ''} - {'old': 'matrix_mautrix_telegram_container_self_build', 'new': 'matrix_mautrix_telegram_container_image_self_build'} - - {'old': 'matrix_telegram_lottieconverter_container_self_build', 'new': 'matrix_mautrix_telegram_container_image_self_build'} - - {'old': 'matrix_telegram_lottieconverter_container_self_build_mask_arch', 'new': 'matrix_telegram_lottieconverter_container_image_self_build_mask_arch'} + - {'old': 'matrix_mautrix_telegram_lottieconverter_container_self_build', 'new': 'matrix_mautrix_telegram_container_image_self_build'} + - {'old': 'matrix_mautrix_telegram_lottieconverter_container_self_build_mask_arch', 'new': 'matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch'} - {'old': 'matrix_mautrix_telegram_login_shared_secret', 'new': ''} - - {'old': 'matrix_telegram_lottieconverter_docker_image_name_prefix', 'new': 'matrix_telegram_lottieconverter_docker_image_registry_prefix'} + - {'old': 'matrix_mautrix_telegram_lottieconverter_docker_image_name_prefix', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_image_registry_prefix'} - {'old': 'matrix_mautrix_telegram_docker_image_name_prefix', 'new': 'matrix_mautrix_telegram_docker_image_registry_prefix'} + - {'old': 'matrix_telegram_lottieconverter_container_image_self_build', 'new': 'matrix_mautrix_telegram_lottieconverter_container_image_self_build'} + - {'old': 'matrix_telegram_lottieconverter_container_image_self_build_mask_arch', 'new': 'matrix_mautrix_telegram_lottieconverter_container_image_self_build_mask_arch'} + - {'old': 'matrix_telegram_lottieconverter_docker_repo', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_repo'} + - {'old': 'matrix_telegram_lottieconverter_docker_repo_version', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_repo_version'} + - {'old': 'matrix_telegram_lottieconverter_docker_src_files_path', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_src_files_path'} + - {'old': 'matrix_telegram_lottieconverter_docker_image', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_image'} + From f7a8c8e83ca6fed2584e0a6c27098ef1f9458431 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 11:47:05 +0200 Subject: [PATCH 713/952] Make external roles also respect `matrix_container_global_registry_prefix_override` Fixup for b88b6ae7a3f1b58ea61990a3b1b6dc319be0ab3e --- group_vars/matrix_servers | 39 ++++++++++++++++++++------------------- 1 file changed, 20 insertions(+), 19 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 7c38f1710..6e5f1d67c 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3306,7 +3306,7 @@ backup_borg_username: "{{ matrix_user_username }}" backup_borg_uid: "{{ matrix_user_uid }}" backup_borg_gid: "{{ matrix_user_gid }}" -backup_borg_docker_image_registry_prefix_upstream: "{{ backup_borg_docker_image_registry_prefix_upstream_default }}" +backup_borg_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else backup_borg_docker_image_registry_prefix_upstream_default }}" backup_borg_container_network: "{{ postgres_container_network if postgres_enabled else backup_borg_identifier }}" @@ -3658,7 +3658,7 @@ etherpad_framing_enabled: "{{ matrix_dimension_enabled or jitsi_enabled }}" etherpad_hostname: "{{ matrix_server_fqn_etherpad }}" -etherpad_container_image_registry_prefix_upstream: "{{ etherpad_container_image_registry_prefix_upstream_default }}" +etherpad_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else etherpad_container_image_registry_prefix_upstream_default }}" etherpad_container_image_self_build: "{{ matrix_architecture not in ['amd64'] }}" @@ -3765,7 +3765,7 @@ jitsi_gid: "{{ matrix_user_gid }}" jitsi_user_username: "{{ matrix_user_username }}" -jitsi_web_container_image_registry_prefix_upstream: "{{ jitsi_web_container_image_registry_prefix_upstream_default }}" +jitsi_web_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else jitsi_web_container_image_registry_prefix_upstream_default }}" jitsi_web_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '13080') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3774,7 +3774,7 @@ jitsi_web_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} -jitsi_jvb_container_image_registry_prefix_upstream: "{{ jitsi_jvb_container_image_registry_prefix_upstream_default }}" +jitsi_jvb_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else jitsi_jvb_container_image_registry_prefix_upstream_default }}" jitsi_jvb_container_colibri_ws_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '13090') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3783,7 +3783,7 @@ jitsi_jvb_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} -jitsi_prosody_container_image_registry_prefix_upstream: "{{ jitsi_prosody_container_image_registry_prefix_upstream_default }}" +jitsi_prosody_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else jitsi_prosody_container_image_registry_prefix_upstream_default }}" jitsi_prosody_container_http_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '5280') if matrix_playbook_service_host_bind_interface_prefix else '' }}" @@ -3792,7 +3792,7 @@ jitsi_prosody_container_additional_networks_auto: | ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else []) }} -jitsi_jicofo_container_image_registry_prefix_upstream: "{{ jitsi_jicofo_container_image_registry_prefix_upstream_default }}" +jitsi_jicofo_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else jitsi_jicofo_container_image_registry_prefix_upstream_default }}" jitsi_container_labels_traefik_enabled: "{{ matrix_playbook_traefik_labels_enabled }}" jitsi_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}" @@ -3913,7 +3913,7 @@ exim_relay_hostname: "{{ matrix_server_fqn_matrix }}" exim_relay_sender_address: "matrix@{{ exim_relay_hostname }}" -exim_relay_container_image_registry_prefix_upstream: "{{ exim_relay_container_image_registry_prefix_upstream_default }}" +exim_relay_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else exim_relay_container_image_registry_prefix_upstream_default }}" exim_relay_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" @@ -4128,8 +4128,9 @@ postgres_systemd_services_to_stop_for_maintenance_list_auto: "{{ devture_systemd postgres_max_connections: "{{ 500 if matrix_synapse_workers_enabled else 200 }}" -postgres_container_image_registry_prefix_upstream: "{{ postgres_container_image_registry_prefix_upstream_default }}" -postgres_pgloader_container_image_registry_prefix_upstream: "{{ postgres_pgloader_container_image_registry_prefix_upstream_default }}" +postgres_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else postgres_container_image_registry_prefix_upstream_default }}" + +postgres_pgloader_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else postgres_pgloader_container_image_registry_prefix_upstream_default }}" postgres_managed_databases_auto: | {{ @@ -4451,7 +4452,7 @@ postgres_backup_systemd_required_services_list_auto: | ([(postgres_identifier + '.service')] if (postgres_enabled and postgres_backup_connection_hostname == postgres_connection_hostname) else []) }} -postgres_backup_container_image_registry_prefix_upstream: "{{ postgres_backup_container_image_registry_prefix_upstream_default }}" +postgres_backup_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else postgres_backup_container_image_registry_prefix_upstream_default }}" postgres_backup_container_network: "{{ (postgres_container_network if (postgres_enabled and postgres_backup_connection_hostname == postgres_connection_hostname) else postgres_backup_identifier) }}" @@ -4529,7 +4530,7 @@ ntfy_gid: "{{ matrix_user_gid }}" ntfy_hostname: "{{ matrix_server_fqn_ntfy }}" -ntfy_container_image_registry_prefix_upstream: "{{ ntfy_container_image_registry_prefix_upstream_default }}" +ntfy_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else ntfy_container_image_registry_prefix_upstream_default }}" ntfy_container_additional_networks_auto: "{{ [matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network else [] }}" @@ -4569,7 +4570,7 @@ valkey_base_path: "{{ matrix_base_data_path }}/valkey" valkey_arch: "{{ matrix_architecture }}" -valkey_container_image_registry_prefix_upstream: "{{ valkey_container_image_registry_prefix_upstream_default }}" +valkey_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else valkey_container_image_registry_prefix_upstream_default }}" ###################################################################### # @@ -5336,7 +5337,7 @@ prometheus_node_exporter_gid: "{{ matrix_user_gid }}" prometheus_node_exporter_hostname: "{{ matrix_server_fqn_matrix }}" -prometheus_node_exporter_docker_image_registry_prefix_upstream: "{{ prometheus_node_exporter_docker_image_registry_prefix_upstream_default }}" +prometheus_node_exporter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else prometheus_node_exporter_docker_image_registry_prefix_upstream_default }}" prometheus_node_exporter_container_network: "{{ matrix_monitoring_container_network }}" @@ -5374,7 +5375,7 @@ prometheus_postgres_exporter_gid: "{{ matrix_user_gid }}" prometheus_postgres_exporter_hostname: "{{ matrix_server_fqn_matrix }}" -prometheus_postgres_exporter_docker_image_registry_prefix_upstream: "{{ prometheus_postgres_exporter_docker_image_registry_prefix_upstream_default }}" +prometheus_postgres_exporter_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else prometheus_postgres_exporter_docker_image_registry_prefix_upstream_default }}" prometheus_postgres_exporter_container_network: "{{ matrix_monitoring_container_network }}" @@ -5466,7 +5467,7 @@ prometheus_base_path: "{{ matrix_base_data_path }}/prometheus" prometheus_uid: "{{ matrix_user_uid }}" prometheus_gid: "{{ matrix_user_gid }}" -prometheus_container_image_registry_prefix_upstream: "{{ prometheus_container_image_registry_prefix_upstream_default }}" +prometheus_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else prometheus_container_image_registry_prefix_upstream_default }}" prometheus_container_network: "{{ matrix_monitoring_container_network }}" @@ -5577,7 +5578,7 @@ grafana_hostname: "{{ matrix_server_fqn_grafana }}" grafana_base_path: "{{ matrix_base_data_path }}/grafana" -grafana_container_image_registry_prefix_upstream: "{{ grafana_container_image_registry_prefix_upstream_default }}" +grafana_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else grafana_container_image_registry_prefix_upstream_default }}" grafana_container_network: "{{ matrix_monitoring_container_network }}" @@ -6172,7 +6173,7 @@ container_socket_proxy_gid: "{{ matrix_user_gid }}" # Traefik requires read access to the containers APIs to do its job container_socket_proxy_api_containers_enabled: true -container_socket_proxy_container_image_registry_prefix_upstream: "{{ container_socket_proxy_container_image_registry_prefix_upstream_default }}" +container_socket_proxy_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else container_socket_proxy_container_image_registry_prefix_upstream_default }}" ######################################################################## # # @@ -6209,7 +6210,7 @@ traefik_additional_entrypoints_auto: | traefik_config_providers_docker_endpoint: "{{ container_socket_proxy_endpoint if container_socket_proxy_enabled else 'unix:///var/run/docker.sock' }}" -traefik_container_image_registry_prefix_upstream: "{{ traefik_container_image_registry_prefix_upstream_default }}" +traefik_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else traefik_container_image_registry_prefix_upstream_default }}" traefik_container_additional_networks_auto: | {{ @@ -6247,7 +6248,7 @@ traefik_certs_dumper_gid: "{{ matrix_user_gid }}" traefik_certs_dumper_ssl_dir_path: "{{ traefik_ssl_dir_path if traefik_enabled else '' }}" -traefik_certs_dumper_container_image_registry_prefix_upstream: "{{ traefik_certs_dumper_container_image_registry_prefix_upstream_default }}" +traefik_certs_dumper_container_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else traefik_certs_dumper_container_image_registry_prefix_upstream_default }}" ######################################################################## # # From 2129cbf95ea30ebe1079474986032cee805d3d74 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 11:47:53 +0200 Subject: [PATCH 714/952] Fix yamllint-reported errors --- .../matrix-bridge-mautrix-telegram/tasks/validate_config.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml index c4a48110c..faaa37f6e 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml @@ -39,4 +39,3 @@ - {'old': 'matrix_telegram_lottieconverter_docker_repo_version', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_repo_version'} - {'old': 'matrix_telegram_lottieconverter_docker_src_files_path', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_src_files_path'} - {'old': 'matrix_telegram_lottieconverter_docker_image', 'new': 'matrix_mautrix_telegram_lottieconverter_docker_image'} - From 3478c6f65b5f0e7326983eb7412d5100043617cf Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 15:52:11 +0200 Subject: [PATCH 715/952] Upgrade backup-borg (v1.4.0-1.9.10-4 -> v1.4.0-1.9.10-5) Ref: https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/issues/15 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 57b5db2d7..0c2bd79bb 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-4 + version: v1.4.0-1.9.10-5 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git version: v0.3.0-4 From 91d5aa40886e25f3868b979f858ac400bd7bfbcd Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 24 Feb 2025 15:55:47 +0200 Subject: [PATCH 716/952] Upgrade backup-borg (v1.4.0-1.9.10-5 -> v1.4.0-1.9.10-6) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 0c2bd79bb..1d324f1ee 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-5 + version: v1.4.0-1.9.10-6 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git version: v0.3.0-4 From dc9672a86f93bd36a21d90c7dc05ae56d6ca4a6f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 00:14:49 +0900 Subject: [PATCH 717/952] Tribute to deprecated components: add license information to files for matrix-bridge-appservice-webhooks This commit adds copyright headers to Markdown, YAML, and labels.j2 files. For the rest of the files, which are ones in YAML and JSON files with the extention ".j2", ".license" files are added following the REUSE's specification. Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bridge-appservice-webhooks.md | 11 +++++++++++ .../defaults/main.yml | 13 +++++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 12 ++++++++++++ .../tasks/setup_uninstall.yml | 7 +++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 3 +++ .../templates/database.json.j2.license | 4 ++++ .../templates/labels.j2 | 6 ++++++ .../templates/schema.yml.j2.license | 4 ++++ .../matrix-appservice-webhooks.service.j2.license | 8 ++++++++ 11 files changed, 80 insertions(+) create mode 100644 roles/custom/matrix-bridge-appservice-webhooks/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-webhooks/templates/database.json.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-webhooks/templates/schema.yml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index 1fbecfdb1..8113341d8 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -1,3 +1,14 @@ + + # Setting up Appservice Webhooks bridging (optional, deprecated) **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. diff --git a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml index 226c893d0..309545e3a 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2020 Björn Marten +# SPDX-FileCopyrightText: 2020 David Gnedt +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 - 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Béla Becker +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-appservice-webhooks is a Matrix <-> webhook bridge # Project source code URL: https://github.com/redoonetworks/matrix-appservice-webhooks diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml index b8d8c8cd4..cb4c68829 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Björn Marten +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml index 2896c7580..507918a5e 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2020 Björn Marten +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-appservice-webhooks paths exist diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_uninstall.yml index c47b724cf..55b7d7521 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2020 Björn Marten +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-webhooks service diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml index fa8a75fc2..f4b704916 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Björn Marten +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-appservice-webhooks settings not defined diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-webhooks/templates/config.yaml.j2.license new file mode 100644 index 000000000..b0cab88b0 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/config.yaml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/database.json.j2.license b/roles/custom/matrix-bridge-appservice-webhooks/templates/database.json.j2.license new file mode 100644 index 000000000..57a3f5b69 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/database.json.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/labels.j2 b/roles/custom/matrix-bridge-appservice-webhooks/templates/labels.j2 index 2749af957..8e3db68be 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/templates/labels.j2 +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_appservice_webhooks_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/schema.yml.j2.license b/roles/custom/matrix-bridge-appservice-webhooks/templates/schema.yml.j2.license new file mode 100644 index 000000000..57a3f5b69 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/schema.yml.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license new file mode 100644 index 000000000..63b731d1e --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2020 Stefan Warnat +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 34ed8105090b43c206ce27e7976d1d0ff85c6c99 Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 24 Feb 2025 18:45:11 +0200 Subject: [PATCH 718/952] fix bluesky tokens --- group_vars/matrix_servers | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 6e5f1d67c..c71911822 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -1153,12 +1153,12 @@ matrix_mautrix_bluesky_container_labels_traefik_tls_certResolver: "{{ traefik_ce matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_enabled: "{{ matrix_metrics_exposure_http_basic_auth_enabled }}" matrix_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_users: "{{ matrix_metrics_exposure_http_basic_auth_users }}" -matrix_mautrix_bluesky_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'twt.as.token', rounds=655555) | to_uuid }}" +matrix_mautrix_bluesky_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'bsky.as.token', rounds=655555) | to_uuid }}" matrix_mautrix_bluesky_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}" -matrix_mautrix_bluesky_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'twt.hs.token', rounds=655555) | to_uuid }}" +matrix_mautrix_bluesky_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'bsky.hs.token', rounds=655555) | to_uuid }}" -matrix_mautrix_bluesky_provisioning_shared_secret: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.twit.prov', rounds=655555) | to_uuid }}" +matrix_mautrix_bluesky_provisioning_shared_secret: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.bsky.prov', rounds=655555) | to_uuid }}" matrix_mautrix_bluesky_double_puppet_secrets_auto: |- {{ From ab53f163eea3089ec26b956d823d26b22d03f30d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:08:39 +0900 Subject: [PATCH 719/952] Tribute to deprecated components: add license information to files for matrix-email2matrix This commit adds copyright attirbutions in SPDX format to files for matrix-email2matrix, following the REUSE's specification. ".license" files are added for config.json.j2 and matrix-email2matrix.service.j2. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email2matrix.md | 10 ++++++++++ roles/custom/matrix-email2matrix/defaults/main.yml | 11 +++++++++++ roles/custom/matrix-email2matrix/tasks/main.yml | 5 +++++ .../matrix-email2matrix/tasks/setup_install.yml | 8 ++++++++ .../matrix-email2matrix/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-email2matrix/tasks/validate_config.yml | 4 ++++ .../templates/config.json.j2.license | 3 +++ .../systemd/matrix-email2matrix.service.j2.license | 4 ++++ 8 files changed, 51 insertions(+) create mode 100644 roles/custom/matrix-email2matrix/templates/config.json.j2.license create mode 100644 roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index ec91658bb..ce2cd2570 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -1,3 +1,13 @@ + + # Setting up Email2Matrix (optional, deprecated) **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. diff --git a/roles/custom/matrix-email2matrix/defaults/main.yml b/roles/custom/matrix-email2matrix/defaults/main.yml index 966d3a21b..43569a6c5 100644 --- a/roles/custom/matrix-email2matrix/defaults/main.yml +++ b/roles/custom/matrix-email2matrix/defaults/main.yml @@ -1,4 +1,15 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- + # Project source code URL: https://github.com/devture/email2matrix matrix_email2matrix_enabled: true diff --git a/roles/custom/matrix-email2matrix/tasks/main.yml b/roles/custom/matrix-email2matrix/tasks/main.yml index acd2c9c1e..f557ccaa0 100644 --- a/roles/custom/matrix-email2matrix/tasks/main.yml +++ b/roles/custom/matrix-email2matrix/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-email2matrix/tasks/setup_install.yml b/roles/custom/matrix-email2matrix/tasks/setup_install.yml index 5cf88c002..242deb01d 100644 --- a/roles/custom/matrix-email2matrix/tasks/setup_install.yml +++ b/roles/custom/matrix-email2matrix/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Email2Matrix paths exist diff --git a/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml b/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml index e95ce6617..e10464f72 100644 --- a/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-email2matrix service diff --git a/roles/custom/matrix-email2matrix/tasks/validate_config.yml b/roles/custom/matrix-email2matrix/tasks/validate_config.yml index d623bc583..17533397f 100644 --- a/roles/custom/matrix-email2matrix/tasks/validate_config.yml +++ b/roles/custom/matrix-email2matrix/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if no Email2Matrix mappings diff --git a/roles/custom/matrix-email2matrix/templates/config.json.j2.license b/roles/custom/matrix-email2matrix/templates/config.json.j2.license new file mode 100644 index 000000000..2fe1c727d --- /dev/null +++ b/roles/custom/matrix-email2matrix/templates/config.json.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license new file mode 100644 index 000000000..d29979396 --- /dev/null +++ b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Chris van Dijk + +SPDX-License-Identifier: AGPL-3.0-or-later From 12e0a8433133dce4f68d43cdb2c543aba3b64958 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:17:32 +0900 Subject: [PATCH 720/952] Tribute to deprecated components: add license information to files for matrix-dimension This commit adds copyright attirbutions in SPDX format to files for matrix-dimension, following the REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dimension.md | 15 +++++++++++++++ roles/custom/matrix-dimension/defaults/main.yml | 15 +++++++++++++++ roles/custom/matrix-dimension/tasks/main.yml | 7 +++++++ .../matrix-dimension/tasks/setup_install.yml | 13 +++++++++++++ .../matrix-dimension/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-dimension/tasks/validate_config.yml | 8 ++++++++ .../templates/config.yaml.j2.license | 5 +++++ roles/custom/matrix-dimension/templates/labels.j2 | 6 ++++++ .../systemd/matrix-dimension.service.j2.license | 7 +++++++ roles/custom/matrix-dimension/vars/main.yml | 6 ++++++ 10 files changed, 88 insertions(+) create mode 100644 roles/custom/matrix-dimension/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 5bc709c12..4eaefb76d 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -1,3 +1,18 @@ + + # Setting up Dimension integration manager (optional, unmaintained) **Notes**: diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml index c5226694f..ba36b8c07 100644 --- a/roles/custom/matrix-dimension/defaults/main.yml +++ b/roles/custom/matrix-dimension/defaults/main.yml @@ -1,3 +1,18 @@ +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2019 Sylvia van Os +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/turt2live/matrix-dimension diff --git a/roles/custom/matrix-dimension/tasks/main.yml b/roles/custom/matrix-dimension/tasks/main.yml index 1e949d3f2..0018acf10 100644 --- a/roles/custom/matrix-dimension/tasks/main.yml +++ b/roles/custom/matrix-dimension/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-dimension/tasks/setup_install.yml b/roles/custom/matrix-dimension/tasks/setup_install.yml index 1c4c4827f..03fee6a99 100644 --- a/roles/custom/matrix-dimension/tasks/setup_install.yml +++ b/roles/custom/matrix-dimension/tasks/setup_install.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-dimension/tasks/setup_uninstall.yml b/roles/custom/matrix-dimension/tasks/setup_uninstall.yml index 239e4d892..b52995681 100644 --- a/roles/custom/matrix-dimension/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-dimension/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-dimension service diff --git a/roles/custom/matrix-dimension/tasks/validate_config.yml b/roles/custom/matrix-dimension/tasks/validate_config.yml index bad6712a2..f7b32e389 100644 --- a/roles/custom/matrix-dimension/tasks/validate_config.yml +++ b/roles/custom/matrix-dimension/tasks/validate_config.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Dimension settings not defined diff --git a/roles/custom/matrix-dimension/templates/config.yaml.j2.license b/roles/custom/matrix-dimension/templates/config.yaml.j2.license new file mode 100644 index 000000000..2c26fe3c7 --- /dev/null +++ b/roles/custom/matrix-dimension/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dimension/templates/labels.j2 b/roles/custom/matrix-dimension/templates/labels.j2 index 09ad07b96..d5d76aeaa 100644 --- a/roles/custom/matrix-dimension/templates/labels.j2 +++ b/roles/custom/matrix-dimension/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_dimension_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license new file mode 100644 index 000000000..0db4becf9 --- /dev/null +++ b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2019 Edgars Voroboks +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2020 Chris van Dijk + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dimension/vars/main.yml b/roles/custom/matrix-dimension/vars/main.yml index 0415989fa..f3ce6a300 100644 --- a/roles/custom/matrix-dimension/vars/main.yml +++ b/roles/custom/matrix-dimension/vars/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Doing `|from_yaml` when the extension contains nothing yields an empty string (""). From d4347ccbf22a97b151b6db253df44ea431f60efe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:28:44 +0900 Subject: [PATCH 721/952] Update docs/configuring-playbook-bridge-mautrix-hangouts.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-hangouts.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index c12283d0c..737a90f26 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -1,3 +1,13 @@ + + # Setting up Mautrix Hangouts bridging (optional, deprecated) 🪦 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. From 66b03d0ca9f74a23a2aa2fa24632ace7c4f03a98 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:52:56 +0900 Subject: [PATCH 722/952] Tribute to deprecated components: add license information to files for matrix-sliding-sync This commit adds copyright attirbutions in SPDX format to files for matrix-sliding-sync, following the REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sliding-sync-proxy.md | 13 +++++++++++++ roles/custom/matrix-sliding-sync/defaults/main.yml | 11 +++++++++++ roles/custom/matrix-sliding-sync/tasks/install.yml | 5 +++++ roles/custom/matrix-sliding-sync/tasks/main.yml | 4 ++++ .../custom/matrix-sliding-sync/tasks/uninstall.yml | 4 ++++ .../matrix-sliding-sync/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-sliding-sync/templates/env.j2 | 7 +++++++ .../custom/matrix-sliding-sync/templates/labels.j2 | 7 +++++++ .../systemd/matrix-sliding-sync.service.j2.license | 3 +++ roles/custom/matrix-sliding-sync/vars/main.yml | 4 ++++ 10 files changed, 63 insertions(+) create mode 100644 roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2.license diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md index 0e72bffaa..f08686719 100644 --- a/docs/configuring-playbook-sliding-sync-proxy.md +++ b/docs/configuring-playbook-sliding-sync-proxy.md @@ -1,3 +1,16 @@ + + # Setting up the Sliding Sync proxy (optional) **Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**. diff --git a/roles/custom/matrix-sliding-sync/defaults/main.yml b/roles/custom/matrix-sliding-sync/defaults/main.yml index 41ef93dc2..036b8023d 100644 --- a/roles/custom/matrix-sliding-sync/defaults/main.yml +++ b/roles/custom/matrix-sliding-sync/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Kabir Kwatra +# SPDX-FileCopyrightText: 2023 David Mehren +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 HarHarLinks +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Sliding Sync proxy is an implementation of MSC3575 for the new sliding sync diff --git a/roles/custom/matrix-sliding-sync/tasks/install.yml b/roles/custom/matrix-sliding-sync/tasks/install.yml index 3526aa644..50128b583 100644 --- a/roles/custom/matrix-sliding-sync/tasks/install.yml +++ b/roles/custom/matrix-sliding-sync/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-sliding-sync paths exist diff --git a/roles/custom/matrix-sliding-sync/tasks/main.yml b/roles/custom/matrix-sliding-sync/tasks/main.yml index 521f16fe7..ad97616b3 100644 --- a/roles/custom/matrix-sliding-sync/tasks/main.yml +++ b/roles/custom/matrix-sliding-sync/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-sliding-sync/tasks/uninstall.yml b/roles/custom/matrix-sliding-sync/tasks/uninstall.yml index 8a559cacc..085b9c548 100644 --- a/roles/custom/matrix-sliding-sync/tasks/uninstall.yml +++ b/roles/custom/matrix-sliding-sync/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-sliding-sync service diff --git a/roles/custom/matrix-sliding-sync/tasks/validate_config.yml b/roles/custom/matrix-sliding-sync/tasks/validate_config.yml index d5ba9e89c..24a29539d 100644 --- a/roles/custom/matrix-sliding-sync/tasks/validate_config.yml +++ b/roles/custom/matrix-sliding-sync/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-sliding-sync settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-sliding-sync/templates/env.j2 b/roles/custom/matrix-sliding-sync/templates/env.j2 index 352e7d958..4a3a06dd4 100644 --- a/roles/custom/matrix-sliding-sync/templates/env.j2 +++ b/roles/custom/matrix-sliding-sync/templates/env.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + SYNCV3_SERVER={{ matrix_sliding_sync_environment_variable_syncv3_server }} SYNCV3_SECRET={{ matrix_sliding_sync_environment_variable_syncv3_secret }} SYNCV3_BINDADDR=:8008 diff --git a/roles/custom/matrix-sliding-sync/templates/labels.j2 b/roles/custom/matrix-sliding-sync/templates/labels.j2 index 736a94354..e2c76c8a4 100644 --- a/roles/custom/matrix-sliding-sync/templates/labels.j2 +++ b/roles/custom/matrix-sliding-sync/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_sliding_sync_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2.license b/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2.license new file mode 100644 index 000000000..97357d3ef --- /dev/null +++ b/roles/custom/matrix-sliding-sync/templates/systemd/matrix-sliding-sync.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-sliding-sync/vars/main.yml b/roles/custom/matrix-sliding-sync/vars/main.yml index 8ec69c087..50fc46bf1 100644 --- a/roles/custom/matrix-sliding-sync/vars/main.yml +++ b/roles/custom/matrix-sliding-sync/vars/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Public facing base URL of the Sliding Sync service. From 329fa105bfa91bea571b716d57bb38fda0897c89 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:53:10 +0900 Subject: [PATCH 723/952] Tribute to deprecated components: add license information to files for matrix-bot-go-neb This commit adds copyright attirbutions in SPDX format to files for matrix-bot-go-neb, following the REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-go-neb.md | 10 ++++++++++ roles/custom/matrix-bot-go-neb/defaults/main.yml | 9 +++++++++ roles/custom/matrix-bot-go-neb/tasks/install.yml | 10 ++++++++++ roles/custom/matrix-bot-go-neb/tasks/main.yml | 6 ++++++ roles/custom/matrix-bot-go-neb/tasks/uninstall.yml | 7 +++++++ .../custom/matrix-bot-go-neb/tasks/validate_config.yml | 5 +++++ .../matrix-bot-go-neb/templates/config.yaml.j2.license | 4 ++++ roles/custom/matrix-bot-go-neb/templates/env.j2 | 6 ++++++ roles/custom/matrix-bot-go-neb/templates/labels.j2 | 6 ++++++ .../systemd/matrix-bot-go-neb.service.j2.license | 4 ++++ 10 files changed, 67 insertions(+) create mode 100644 roles/custom/matrix-bot-go-neb/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2.license diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 5fdf511eb..2bf69ef61 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -1,3 +1,13 @@ + + # Setting up Go-NEB (optional, unmaintained) **Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one. diff --git a/roles/custom/matrix-bot-go-neb/defaults/main.yml b/roles/custom/matrix-bot-go-neb/defaults/main.yml index 6695f621a..cff674cff 100644 --- a/roles/custom/matrix-bot-go-neb/defaults/main.yml +++ b/roles/custom/matrix-bot-go-neb/defaults/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python. diff --git a/roles/custom/matrix-bot-go-neb/tasks/install.yml b/roles/custom/matrix-bot-go-neb/tasks/install.yml index 10002904c..ee418fd0f 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/install.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure go-neb paths exist diff --git a/roles/custom/matrix-bot-go-neb/tasks/main.yml b/roles/custom/matrix-bot-go-neb/tasks/main.yml index 9367419da..666296156 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/main.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml b/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml index cc5f9fa57..56cee88e1 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-go-neb service diff --git a/roles/custom/matrix-bot-go-neb/tasks/validate_config.yml b/roles/custom/matrix-bot-go-neb/tasks/validate_config.yml index 72bc3cb41..ead635626 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if there's not at least 1 client diff --git a/roles/custom/matrix-bot-go-neb/templates/config.yaml.j2.license b/roles/custom/matrix-bot-go-neb/templates/config.yaml.j2.license new file mode 100644 index 000000000..c74bd679c --- /dev/null +++ b/roles/custom/matrix-bot-go-neb/templates/config.yaml.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Yannick Goossens +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-go-neb/templates/env.j2 b/roles/custom/matrix-bot-go-neb/templates/env.j2 index 22e605e5c..7fd62d5d7 100644 --- a/roles/custom/matrix-bot-go-neb/templates/env.j2 +++ b/roles/custom/matrix-bot-go-neb/templates/env.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + BIND_ADDRESS=:4050 DATABASE_TYPE={{ matrix_bot_go_neb_database_engine }} diff --git a/roles/custom/matrix-bot-go-neb/templates/labels.j2 b/roles/custom/matrix-bot-go-neb/templates/labels.j2 index 1f0123add..4f8d18670 100644 --- a/roles/custom/matrix-bot-go-neb/templates/labels.j2 +++ b/roles/custom/matrix-bot-go-neb/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_bot_go_neb_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2.license b/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2.license new file mode 100644 index 000000000..99d44ac5b --- /dev/null +++ b/roles/custom/matrix-bot-go-neb/templates/systemd/matrix-bot-go-neb.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Yannick Goossens +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From cd4b1ca72f00e8276c57446cd1582e4a496568d0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 02:53:17 +0900 Subject: [PATCH 724/952] Tribute to deprecated components: add license information to files for matrix-bot-chatgpt This commit adds copyright attirbutions in SPDX format to files for matrix-bot-chatgpt, following the REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-chatgpt.md | 8 ++++++++ roles/custom/matrix-bot-chatgpt/defaults/main.yml | 9 +++++++++ roles/custom/matrix-bot-chatgpt/tasks/install.yml | 5 +++++ roles/custom/matrix-bot-chatgpt/tasks/main.yml | 5 +++++ roles/custom/matrix-bot-chatgpt/tasks/uninstall.yml | 5 +++++ .../custom/matrix-bot-chatgpt/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-bot-chatgpt/templates/env.j2 | 9 +++++++++ .../systemd/matrix-bot-chatgpt.service.j2.license | 5 +++++ 8 files changed, 51 insertions(+) create mode 100644 roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 2ddd72bfd..74e687bbc 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -1,3 +1,11 @@ + + # Setting up matrix-bot-chatgpt (optional, unmaintained) **Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one. diff --git a/roles/custom/matrix-bot-chatgpt/defaults/main.yml b/roles/custom/matrix-bot-chatgpt/defaults/main.yml index 3b1c59a88..3727962db 100644 --- a/roles/custom/matrix-bot-chatgpt/defaults/main.yml +++ b/roles/custom/matrix-bot-chatgpt/defaults/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Joe Kappus +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # chatgpt is a bot for chatting to openAI chatgpt Matrix bot # Project source code URL: https://github.com/matrixgpt/matrix-chatgpt-bot diff --git a/roles/custom/matrix-bot-chatgpt/tasks/install.yml b/roles/custom/matrix-bot-chatgpt/tasks/install.yml index af9550f15..1f2beae64 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/install.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure chatgpt paths exist diff --git a/roles/custom/matrix-bot-chatgpt/tasks/main.yml b/roles/custom/matrix-bot-chatgpt/tasks/main.yml index 3f5a7b7ec..3160fde32 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/main.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - diff --git a/roles/custom/matrix-bot-chatgpt/tasks/uninstall.yml b/roles/custom/matrix-bot-chatgpt/tasks/uninstall.yml index 4a50d7337..e6b488789 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/uninstall.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-chatgpt service diff --git a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml index 51797882f..3d1fff512 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Chatgpt settings not defined diff --git a/roles/custom/matrix-bot-chatgpt/templates/env.j2 b/roles/custom/matrix-bot-chatgpt/templates/env.j2 index 375ef18f2..bbb6d01e3 100644 --- a/roles/custom/matrix-bot-chatgpt/templates/env.j2 +++ b/roles/custom/matrix-bot-chatgpt/templates/env.j2 @@ -1,3 +1,12 @@ +{# +SPDX-FileCopyrightText: 2023 MDAD project contributors +SPDX-FileCopyrightText: 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Joe Kappus +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + MATRIX_HOMESERVER_URL={{ matrix_bot_chatgpt_matrix_homeserver_url }} MATRIX_ACCESS_TOKEN={{ matrix_bot_chatgpt_matrix_access_token }} diff --git a/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license new file mode 100644 index 000000000..5eda5a739 --- /dev/null +++ b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2023 MDAD project contributors +SPDX-FileCopyrightText: 2023 Vladimir Panteleev +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 2a3fee7b80d89c95ab180933d84230e70c24e5ce Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 03:48:09 +0900 Subject: [PATCH 725/952] Fix some of the spacing warnings with ansible-lint Signed-off-by: Suguru Hirahara --- roles/custom/matrix-base/defaults/main.yml | 2 +- roles/custom/matrix-bot-baibot/defaults/main.yml | 8 ++++---- .../defaults/main.yml | 2 +- .../defaults/main.yml | 2 +- .../defaults/main.yml | 16 ++++++++-------- .../tasks/setup_install.yml | 6 +++--- .../tasks/validate_config.yml | 16 ++++++++-------- 7 files changed, 26 insertions(+), 26 deletions(-) diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index 63027e487..6a72154a4 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -278,7 +278,7 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_name: "{{ matrix matrix_playbook_public_matrix_federation_api_traefik_entrypoint_port: "{{ matrix_federation_public_port }}" matrix_playbook_public_matrix_federation_api_traefik_entrypoint_host_bind_port: "{{ matrix_federation_public_port }}" matrix_playbook_public_matrix_federation_api_traefik_entrypoint_host_bind_port_udp: "{{ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_advertisedPort if matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_enabled else '' }}" -matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config: "{{ (matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_default | combine (matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_auto)) | combine(matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_custom, recursive=True) }}" +matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config: "{{ (matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_default | combine(matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_auto)) | combine(matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_custom, recursive=True) }}" matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_enabled: true matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_advertisedPort: "{{ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_port }}" # noqa var-naming matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout: "{{ traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout }}" # noqa var-naming diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index b17a55af3..41576a01b 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -169,7 +169,7 @@ matrix_bot_baibot_config_agents_static_definitions_anthropic_enabled: false matrix_bot_baibot_config_agents_static_definitions_anthropic_id: anthropic matrix_bot_baibot_config_agents_static_definitions_anthropic_provider: anthropic -matrix_bot_baibot_config_agents_static_definitions_anthropic_config: "{{ matrix_bot_baibot_config_agents_static_definitions_anthropic_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_anthropic_config_extension, recursive=True)}}" +matrix_bot_baibot_config_agents_static_definitions_anthropic_config: "{{ matrix_bot_baibot_config_agents_static_definitions_anthropic_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_anthropic_config_extension, recursive=True) }}" matrix_bot_baibot_config_agents_static_definitions_anthropic_config_yaml: "{{ lookup('template', 'templates/provider/anthropic-config.yml.j2') }}" @@ -222,7 +222,7 @@ matrix_bot_baibot_config_agents_static_definitions_groq_enabled: false matrix_bot_baibot_config_agents_static_definitions_groq_id: groq matrix_bot_baibot_config_agents_static_definitions_groq_provider: groq -matrix_bot_baibot_config_agents_static_definitions_groq_config: "{{ matrix_bot_baibot_config_agents_static_definitions_groq_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_groq_config_extension, recursive=True)}}" +matrix_bot_baibot_config_agents_static_definitions_groq_config: "{{ matrix_bot_baibot_config_agents_static_definitions_groq_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_groq_config_extension, recursive=True) }}" matrix_bot_baibot_config_agents_static_definitions_groq_config_yaml: "{{ lookup('template', 'templates/provider/groq-config.yml.j2') }}" @@ -278,7 +278,7 @@ matrix_bot_baibot_config_agents_static_definitions_mistral_enabled: false matrix_bot_baibot_config_agents_static_definitions_mistral_id: mistral matrix_bot_baibot_config_agents_static_definitions_mistral_provider: mistral -matrix_bot_baibot_config_agents_static_definitions_mistral_config: "{{ matrix_bot_baibot_config_agents_static_definitions_mistral_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_mistral_config_extension, recursive=True)}}" +matrix_bot_baibot_config_agents_static_definitions_mistral_config: "{{ matrix_bot_baibot_config_agents_static_definitions_mistral_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_mistral_config_extension, recursive=True) }}" matrix_bot_baibot_config_agents_static_definitions_mistral_config_yaml: "{{ lookup('template', 'templates/provider/mistral-config.yml.j2') }}" @@ -331,7 +331,7 @@ matrix_bot_baibot_config_agents_static_definitions_openai_enabled: false matrix_bot_baibot_config_agents_static_definitions_openai_id: openai matrix_bot_baibot_config_agents_static_definitions_openai_provider: openai -matrix_bot_baibot_config_agents_static_definitions_openai_config: "{{ matrix_bot_baibot_config_agents_static_definitions_openai_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_openai_config_extension, recursive=True)}}" +matrix_bot_baibot_config_agents_static_definitions_openai_config: "{{ matrix_bot_baibot_config_agents_static_definitions_openai_config_yaml | from_yaml | combine(matrix_bot_baibot_config_agents_static_definitions_openai_config_extension, recursive=True) }}" matrix_bot_baibot_config_agents_static_definitions_openai_config_yaml: "{{ lookup('template', 'templates/provider/openai-config.yml.j2') }}" diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index 769e84b60..ca438720c 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -11,7 +11,7 @@ matrix_bot_matrix_registration_bot_docker_src_files_path: "{{ matrix_bot_matrix_ # renovate: datasource=docker depName=moanos/matrix-registration-bot matrix_bot_matrix_registration_bot_version: 1.3.0 matrix_bot_matrix_registration_bot_docker_iteration: 0 -matrix_bot_matrix_registration_bot_docker_tag: "{{ matrix_bot_matrix_registration_bot_version }}-{{ matrix_bot_matrix_registration_bot_docker_iteration}}" +matrix_bot_matrix_registration_bot_docker_tag: "{{ matrix_bot_matrix_registration_bot_version }}-{{ matrix_bot_matrix_registration_bot_docker_iteration }}" matrix_bot_matrix_registration_bot_docker_image: "{{ matrix_bot_matrix_registration_bot_docker_image_registry_prefix }}moanos/matrix-registration-bot:{{ matrix_bot_matrix_registration_bot_docker_tag }}" matrix_bot_matrix_registration_bot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_bot_matrix_registration_bot_container_image_self_build else matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream }}" matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream: "{{ matrix_bot_matrix_registration_bot_docker_image_registry_prefix_upstream_default }}" diff --git a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml index de0e0ed7d..a162a5848 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml @@ -96,7 +96,7 @@ matrix_go_skype_bridge_bridge_login_shared_secret_map: # Servers to always allow double puppeting from matrix_go_skype_bridge_bridge_double_puppet_server_map: - "{{ matrix_go_skype_bridge_homeserver_domain : matrix_go_skype_bridge_homeserver_address }}" + "{{ matrix_go_skype_bridge_homeserver_domain: matrix_go_skype_bridge_homeserver_address }}" # Enable End-to-bridge encryption matrix_go_skype_bridge_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}" diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml index f9a514e9f..36bd8dc12 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml @@ -98,11 +98,11 @@ matrix_mautrix_wsproxy_configuration_extension_yaml: | # If you need something more special, you can take full control by # completely redefining `matrix_mautrix_wsproxy_configuration_yaml`. -matrix_mautrix_wsproxy_configuration_extension: "{{ matrix_mautrix_wsproxy_configuration_extension_yaml|from_yaml if matrix_mautrix_wsproxy_configuration_extension_yaml|from_yaml is mapping else {} }}" +matrix_mautrix_wsproxy_configuration_extension: "{{ matrix_mautrix_wsproxy_configuration_extension_yaml | from_yaml if matrix_mautrix_wsproxy_configuration_extension_yaml | from_yaml is mapping else {} }}" # Holds the final configuration (a combination of the default and its extension). # You most likely don't need to touch this variable. Instead, see `matrix_mautrix_wsproxy_configuration_yaml`. -matrix_mautrix_wsproxy_configuration: "{{ matrix_mautrix_wsproxy_configuration_yaml|from_yaml|combine(matrix_mautrix_wsproxy_configuration_extension, recursive=True) }}" +matrix_mautrix_wsproxy_configuration: "{{ matrix_mautrix_wsproxy_configuration_yaml | from_yaml | combine(matrix_mautrix_wsproxy_configuration_extension, recursive=True) }}" matrix_mautrix_androidsms_registration_yaml: | id: androidsms @@ -113,12 +113,12 @@ matrix_mautrix_androidsms_registration_yaml: | rate_limited: false namespaces: users: - - regex: '@androidsms_.+:{{ matrix_mautrix_wsproxy_homeserver_domain|regex_escape }}$' + - regex: '@androidsms_.+:{{ matrix_mautrix_wsproxy_homeserver_domain | regex_escape }}$' exclusive: true - exclusive: true - regex: '^@{{ matrix_mautrix_androidsms_appservice_bot_username|regex_escape }}:{{ matrix_mautrix_wsproxy_homeserver_domain|regex_escape }}$' + regex: '^@{{ matrix_mautrix_androidsms_appservice_bot_username | regex_escape }}:{{ matrix_mautrix_wsproxy_homeserver_domain | regex_escape }}$' -matrix_mautrix_androidsms_registration: "{{ matrix_mautrix_androidsms_registration_yaml|from_yaml }}" +matrix_mautrix_androidsms_registration: "{{ matrix_mautrix_androidsms_registration_yaml | from_yaml }}" matrix_mautrix_imessage_registration_yaml: | id: imessage @@ -129,12 +129,12 @@ matrix_mautrix_imessage_registration_yaml: | rate_limited: false namespaces: users: - - regex: '@imessage_.+:{{ matrix_mautrix_wsproxy_homeserver_domain|regex_escape }}$' + - regex: '@imessage_.+:{{ matrix_mautrix_wsproxy_homeserver_domain | regex_escape }}$' exclusive: true - exclusive: true - regex: '^@{{ matrix_mautrix_imessage_appservice_bot_username|regex_escape }}:{{ matrix_mautrix_wsproxy_homeserver_domain|regex_escape }}$' + regex: '^@{{ matrix_mautrix_imessage_appservice_bot_username | regex_escape }}:{{ matrix_mautrix_wsproxy_homeserver_domain | regex_escape }}$' -matrix_mautrix_imessage_registration: "{{ matrix_mautrix_imessage_registration_yaml|from_yaml }}" +matrix_mautrix_imessage_registration: "{{ matrix_mautrix_imessage_registration_yaml | from_yaml }}" # Syncproxy-related configuration fields # renovate: datasource=docker depName=dock.mau.dev/mautrix/syncproxy diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml index 703d412df..59744ab48 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml @@ -69,7 +69,7 @@ - name: Ensure mautrix-wsproxy config.yaml installed ansible.builtin.copy: - content: "{{ matrix_mautrix_wsproxy_configuration|to_nice_yaml }}" + content: "{{ matrix_mautrix_wsproxy_configuration | to_nice_yaml }}" dest: "{{ matrix_mautrix_wsproxy_config_path }}/config.yaml" mode: 0644 owner: "{{ matrix_user_username }}" @@ -77,7 +77,7 @@ - name: Ensure mautrix-androidsms registration.yaml installed ansible.builtin.copy: - content: "{{ matrix_mautrix_androidsms_registration|to_nice_yaml }}" + content: "{{ matrix_mautrix_androidsms_registration | to_nice_yaml }}" dest: "{{ matrix_mautrix_wsproxy_config_path }}/androidsms-registration.yaml" mode: 0644 owner: "{{ matrix_user_username }}" @@ -85,7 +85,7 @@ - name: Ensure mautrix-imessage registration.yaml installed ansible.builtin.copy: - content: "{{ matrix_mautrix_imessage_registration|to_nice_yaml }}" + content: "{{ matrix_mautrix_imessage_registration | to_nice_yaml }}" dest: "{{ matrix_mautrix_wsproxy_config_path }}/imessage-registration.yaml" mode: 0644 owner: "{{ matrix_user_username }}" diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 37b8669f8..4232196d3 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -78,7 +78,7 @@ Please change your configuration (vars.yml) to rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | list | items2dict" - name: (Deprecation) Catch and report matrix_mailer_ variables @@ -89,7 +89,7 @@ Please change your configuration (vars.yml) to rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | list | items2dict" - when: matrix_playbook_migration_matrix_prometheus_node_exporter_migration_validation_enabled | bool @@ -417,7 +417,7 @@ Please change your configuration (vars.yml) to rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | list | items2dict" - name: (Deprecation) Catch and report devture_postgres variables @@ -428,7 +428,7 @@ Please change your configuration (vars.yml) to rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | list | items2dict" - name: (Deprecation) Catch and report traefik_certs_dumper variables @@ -439,7 +439,7 @@ Please change your configuration (vars.yml) to rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | list | items2dict" - name: (Deprecation) Catch and report devture_traefik variables @@ -450,7 +450,7 @@ Please change your configuration (vars.yml) to rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | list | items2dict" - name: (Deprecation) Catch and report devture_container_socket_proxy variables @@ -461,7 +461,7 @@ Please change your configuration (vars.yml) to rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`). - The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | list | items2dict" - name: (Deprecation) Catch and report mautrix-hangouts variables @@ -474,5 +474,5 @@ You may also wish to uninstall the bridge manually. See `docs/configuring-playbook-bridge-mautrix-hangouts.md` for more information. - The following variables in your configuration need to be removed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | map (attribute='key') | join(', ') }} + The following variables in your configuration need to be removed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | list | items2dict" From 0a72b7b3965cb0c58efba0f4da03fa5b2c3bce12 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 13:07:56 +0900 Subject: [PATCH 726/952] Tribute to deprecated components: add license information to files for matrix-bridge-mautrix-facebook This commit adds copyright attributions in SPDX format as of 6aa320e117c1e051957383229a96fcb58bb0cfa3 to the files for matrix-bridge-mautrix-facebook, following REUSE's specification. Signed-off-by: Suguru Hirahara --- ...onfiguring-playbook-bridge-mautrix-facebook.md | 12 ++++++++++++ .../defaults/main.yml | 14 ++++++++++++++ .../matrix-bridge-mautrix-facebook/tasks/main.yml | 7 +++++++ .../tasks/setup_install.yml | 15 +++++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 7 +++++++ .../templates/config.yaml.j2.license | 9 +++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-facebook.service.j2.license | 7 +++++++ 9 files changed, 83 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index 67d2b3d9b..f5f6d581f 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -1,3 +1,15 @@ + + # Setting up Mautrix Facebook bridging (optional, deprecated) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml index ce448c1bc..c4a80ba70 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml @@ -1,3 +1,17 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Arthur Brugière +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-facebook is a Matrix <-> Facebook bridge # Project source code URL: https://github.com/mautrix/facebook diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/main.yml index d26ce1733..c5cf1123e 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jason Locklin +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml index 02dd8e511..12907c16b 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml @@ -1,3 +1,18 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_uninstall.yml index 566da5b71..d88c98feb 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-facebook service diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml index 12286f320..45c751627 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Jason Locklin +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed mautrix-facebook settings diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license new file mode 100644 index 000000000..309dd31e7 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license @@ -0,0 +1,9 @@ +SPDX-FileCopyrightText: 2019 Hugues Morisset +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 Olivér Falvai +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2023 Adrien le Maire + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-facebook/templates/labels.j2 index d71e7eed2..d7eecb2ec 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_facebook_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2.license b/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2.license new file mode 100644 index 000000000..f74c84d94 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/systemd/matrix-mautrix-facebook.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues Morisset +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2022 László Várady + +SPDX-License-Identifier: AGPL-3.0-or-later From bcd641063ec1e01580c46ac18f07272c172f0e58 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 13:10:56 +0900 Subject: [PATCH 727/952] Tribute to deprecated components: add license information to files for matrix-bridge-mautrix-instagram This commit adds copyright attributions in SPDX format as of 6aa320e117c1e051957383229a96fcb58bb0cfa3 to the files for matrix-bridge-mautrix-instagram, following REUSE's specification. Signed-off-by: Suguru Hirahara --- .../configuring-playbook-bridge-mautrix-instagram.md | 9 +++++++++ .../defaults/main.yml | 12 ++++++++++++ .../matrix-bridge-mautrix-instagram/tasks/main.yml | 7 +++++++ .../tasks/setup_install.yml | 10 ++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 10 ++++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-instagram.service.j2.license | 4 ++++ 9 files changed, 69 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index 4bacb9ebd..c4694e0f1 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -1,3 +1,12 @@ + + # Setting up Mautrix Instagram bridging (optional, deprecated) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml index ad0a2a00a..b2acb3afc 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-instagram is a Matrix <-> Instagram bridge # Project source code URL: https://github.com/mautrix/instagram diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml index a9c63922c..b662b59d4 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml index f355edc3b..f122dff98 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Mautrix instagram image is pulled diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml index 6ac0f6d52..da2d3f98e 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-instagram service ansible.builtin.stat: diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml index 72a97f9bd..ef430fcbd 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-instagram settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license new file mode 100644 index 000000000..6e01bd18d --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license @@ -0,0 +1,10 @@ +SPDX-FileCopyrightText: 2021 Marcus Proest +SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Adrien le Maire +SPDX-FileCopyrightText: 2023 Kevin Kengen +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-instagram/templates/labels.j2 index c67f2264d..e5b9154ab 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_instagram_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2.license b/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2.license new file mode 100644 index 000000000..41f4c833d --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/systemd/matrix-mautrix-instagram.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Marcus Proest +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 6a4366d75de576bdbe7274b2c2a616face6b9cf2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 25 Feb 2025 08:36:15 +0200 Subject: [PATCH 728/952] Upgrade Postgres (v17.2-3 -> v17.4-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 1d324f1ee..602bd55a3 100644 --- a/requirements.yml +++ b/requirements.yml @@ -40,7 +40,7 @@ version: ff2fd42e1c1a9e28e3312bbd725395f9c2fc7f16 name: playbook_state_preserver - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres.git - version: v17.2-3 + version: v17.4-0 name: postgres - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git version: v17-3 From 83ee9ba41586927ff783bc12120099f8cc7bc165 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 17:36:07 +0900 Subject: [PATCH 729/952] Add license information to files for matrix-ma1sd This commit adds copyright attributions in SPDX format to the files for matrix-ma1sd following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ma1sd.md | 11 +++++++++++ roles/custom/matrix-ma1sd/defaults/main.yml | 14 ++++++++++++++ roles/custom/matrix-ma1sd/tasks/main.yml | 6 ++++++ roles/custom/matrix-ma1sd/tasks/self_check.yml | 7 +++++++ roles/custom/matrix-ma1sd/tasks/setup_install.yml | 14 ++++++++++++++ .../custom/matrix-ma1sd/tasks/setup_uninstall.yml | 6 ++++++ .../custom/matrix-ma1sd/tasks/validate_config.yml | 6 ++++++ roles/custom/matrix-ma1sd/templates/labels.j2 | 6 ++++++ .../matrix-ma1sd/templates/ma1sd.yaml.j2.license | 4 ++++ .../systemd/matrix-ma1sd.service.j2.license | 7 +++++++ roles/custom/matrix-ma1sd/vars/main.yml | 5 +++++ 11 files changed, 86 insertions(+) create mode 100644 roles/custom/matrix-ma1sd/templates/ma1sd.yaml.j2.license create mode 100644 roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index ced162b8c..812ef14d4 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -1,3 +1,14 @@ + + # Setting up ma1sd Identity Server (optional) **⚠️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). diff --git a/roles/custom/matrix-ma1sd/defaults/main.yml b/roles/custom/matrix-ma1sd/defaults/main.yml index 53c93df33..e235c924e 100644 --- a/roles/custom/matrix-ma1sd/defaults/main.yml +++ b/roles/custom/matrix-ma1sd/defaults/main.yml @@ -1,3 +1,17 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Matt Cengia +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # ma1sd is a Federated Matrix Identity Server # Project source code URL: https://github.com/ma1uta/ma1sd diff --git a/roles/custom/matrix-ma1sd/tasks/main.yml b/roles/custom/matrix-ma1sd/tasks/main.yml index 09e7114bf..ee4613b65 100644 --- a/roles/custom/matrix-ma1sd/tasks/main.yml +++ b/roles/custom/matrix-ma1sd/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-ma1sd/tasks/self_check.yml b/roles/custom/matrix-ma1sd/tasks/self_check.yml index 7ce57e1ec..a90ae7a9c 100644 --- a/roles/custom/matrix-ma1sd/tasks/self_check.yml +++ b/roles/custom/matrix-ma1sd/tasks/self_check.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check ma1sd Identity Service diff --git a/roles/custom/matrix-ma1sd/tasks/setup_install.yml b/roles/custom/matrix-ma1sd/tasks/setup_install.yml index e77f2d689..a6bb87c76 100644 --- a/roles/custom/matrix-ma1sd/tasks/setup_install.yml +++ b/roles/custom/matrix-ma1sd/tasks/setup_install.yml @@ -1,3 +1,17 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Matt Cengia +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure ma1sd paths exist diff --git a/roles/custom/matrix-ma1sd/tasks/setup_uninstall.yml b/roles/custom/matrix-ma1sd/tasks/setup_uninstall.yml index b27df269e..2bfbdeeb5 100644 --- a/roles/custom/matrix-ma1sd/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-ma1sd/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-ma1sd service diff --git a/roles/custom/matrix-ma1sd/tasks/validate_config.yml b/roles/custom/matrix-ma1sd/tasks/validate_config.yml index 6a2345777..ca7009df4 100644 --- a/roles/custom/matrix-ma1sd/tasks/validate_config.yml +++ b/roles/custom/matrix-ma1sd/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 boris runakov +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Warn about ma1sd variables that are not used anymore diff --git a/roles/custom/matrix-ma1sd/templates/labels.j2 b/roles/custom/matrix-ma1sd/templates/labels.j2 index 4570e3b23..b3df693e8 100644 --- a/roles/custom/matrix-ma1sd/templates/labels.j2 +++ b/roles/custom/matrix-ma1sd/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_ma1sd_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-ma1sd/templates/ma1sd.yaml.j2.license b/roles/custom/matrix-ma1sd/templates/ma1sd.yaml.j2.license new file mode 100644 index 000000000..a519212f1 --- /dev/null +++ b/roles/custom/matrix-ma1sd/templates/ma1sd.yaml.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license new file mode 100644 index 000000000..c893e025f --- /dev/null +++ b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2021 boris runakov + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/vars/main.yml b/roles/custom/matrix-ma1sd/vars/main.yml index 3adc735e9..944099e50 100644 --- a/roles/custom/matrix-ma1sd/vars/main.yml +++ b/roles/custom/matrix-ma1sd/vars/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Doing `|from_yaml` when the extension contains nothing yields an empty string (""). From 3efc5099c30bcd4c381eedce93e72f2018580b6d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 17:36:59 +0900 Subject: [PATCH 730/952] Add license information to files for matrix-bridge-wechat This commit adds copyright attributions in SPDX format to the files for matrix-bridge-wechat following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-wechat.md | 7 +++++++ roles/custom/matrix-bridge-wechat/defaults/main.yml | 5 +++++ roles/custom/matrix-bridge-wechat/tasks/install.yml | 5 +++++ roles/custom/matrix-bridge-wechat/tasks/main.yml | 4 ++++ roles/custom/matrix-bridge-wechat/tasks/uninstall.yml | 4 ++++ .../custom/matrix-bridge-wechat/tasks/validate_config.yml | 5 +++++ .../matrix-bridge-wechat/templates/agent-config.yaml.j2 | 6 ++++++ .../matrix-bridge-wechat/templates/config.yaml.j2.license | 4 ++++ .../systemd/matrix-wechat-agent.service.j2.license | 3 +++ .../templates/systemd/matrix-wechat.service.j2.license | 3 +++ 10 files changed, 46 insertions(+) create mode 100644 roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2.license create mode 100644 roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2.license diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md index 0ae3fe21f..2c7590b40 100644 --- a/docs/configuring-playbook-bridge-wechat.md +++ b/docs/configuring-playbook-bridge-wechat.md @@ -1,3 +1,10 @@ + + # Setting up WeChat bridging (optional) The playbook can install and configure [matrix-wechat](https://github.com/duo/matrix-wechat) for you, for bridging to [WeChat](https://www.wechat.com/). diff --git a/roles/custom/matrix-bridge-wechat/defaults/main.yml b/roles/custom/matrix-bridge-wechat/defaults/main.yml index 18d7b01ca..50167b91c 100644 --- a/roles/custom/matrix-bridge-wechat/defaults/main.yml +++ b/roles/custom/matrix-bridge-wechat/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # WeChat Bridge is a Matrix <-> WeChat bridge diff --git a/roles/custom/matrix-bridge-wechat/tasks/install.yml b/roles/custom/matrix-bridge-wechat/tasks/install.yml index d9a74db20..607ca780b 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/install.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure WeChat Bridge paths exists diff --git a/roles/custom/matrix-bridge-wechat/tasks/main.yml b/roles/custom/matrix-bridge-wechat/tasks/main.yml index effcd7d5e..bcad351ab 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/main.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-wechat/tasks/uninstall.yml b/roles/custom/matrix-bridge-wechat/tasks/uninstall.yml index cf19203fa..7972bd7df 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/uninstall.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-wechat service diff --git a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml index c6868e1ae..6400ccfd3 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + + --- - name: Fail if required WeChat settings not defined diff --git a/roles/custom/matrix-bridge-wechat/templates/agent-config.yaml.j2 b/roles/custom/matrix-bridge-wechat/templates/agent-config.yaml.j2 index 19c1d1ad9..6b30c6345 100644 --- a/roles/custom/matrix-bridge-wechat/templates/agent-config.yaml.j2 +++ b/roles/custom/matrix-bridge-wechat/templates/agent-config.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + wechat: version: 3.8.1.26 listen_port: 22222 diff --git a/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license new file mode 100644 index 000000000..b94e0d95e --- /dev/null +++ b/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2.license b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat-agent.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2.license b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-bridge-wechat/templates/systemd/matrix-wechat.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 379229c4e098c9bee4efe109c4c334c82bb16239 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 17:37:14 +0900 Subject: [PATCH 731/952] Add license information to files for matrix-bridge-appservice-kakaotalk This commit adds copyright attributions in SPDX to the files for matrix-bridge-appservice-kakaotalk following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-appservice-kakaotalk.md | 9 +++++++++ .../matrix-bridge-appservice-kakaotalk/defaults/main.yml | 6 ++++++ .../matrix-bridge-appservice-kakaotalk/tasks/main.yml | 4 ++++ .../tasks/setup_install.yml | 6 ++++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/config.yaml.j2.license | 6 ++++++ .../templates/node-config.json.j2.license | 3 +++ .../matrix-appservice-kakaotalk-node.service.j2.license | 3 +++ .../matrix-appservice-kakaotalk.service.j2.license | 3 +++ 10 files changed, 48 insertions(+) create mode 100644 roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-kakaotalk/templates/node-config.json.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2.license diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md index c8fbb12fc..e92bbe6ab 100644 --- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md +++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md @@ -1,3 +1,12 @@ + + # Setting up Appservice Kakaotalk bridging (optional) The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you, 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. diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml index 1f628eef4..aed2476e5 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-appservice-kakaotalk is a Matrix <-> Kakaotalk bridge # Project source code URL: https://src.miscworks.net/fair/matrix-appservice-kakaotalk/ diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/main.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/main.yml index 7a360024e..c99b77fbe 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_install.yml index 1cb1e6026..3c3da6765 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-appservice-kakaotalk image is pulled diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_uninstall.yml index e258b9ab2..f92960991 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-kakaotalk service diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml index 20da0206e..8ba158fe8 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required appservice-kakaotalk settings not defined diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license new file mode 100644 index 000000000..f9a202b63 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/node-config.json.j2.license b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/node-config.json.j2.license new file mode 100644 index 000000000..7b1e56adc --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/node-config.json.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2.license b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2.license new file mode 100644 index 000000000..b2bdc9cb4 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk-node.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2.license b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2.license new file mode 100644 index 000000000..7b1e56adc --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/systemd/matrix-appservice-kakaotalk.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From afd122330bb0c83eb061a584780f160eb9082168 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 18:01:02 +0900 Subject: [PATCH 732/952] Add license information to files for matrix-client-hydrogen This commit adds copyright attributions in SPDX to the files for matrix-client-hydrogen following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-hydrogen.md | 9 +++++++++ roles/custom/matrix-client-hydrogen/defaults/main.yml | 11 +++++++++++ roles/custom/matrix-client-hydrogen/tasks/main.yml | 6 ++++++ .../matrix-client-hydrogen/tasks/self_check.yml | 6 ++++++ .../matrix-client-hydrogen/tasks/setup_install.yml | 11 +++++++++++ .../matrix-client-hydrogen/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-client-hydrogen/tasks/validate_config.yml | 6 ++++++ .../templates/config.json.j2.license | 7 +++++++ .../custom/matrix-client-hydrogen/templates/labels.j2 | 6 ++++++ .../templates/nginx.conf.j2.license | 4 ++++ .../systemd/matrix-client-hydrogen.service.j2.license | 5 +++++ 11 files changed, 77 insertions(+) create mode 100644 roles/custom/matrix-client-hydrogen/templates/config.json.j2.license create mode 100644 roles/custom/matrix-client-hydrogen/templates/nginx.conf.j2.license create mode 100644 roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md index cf9b30335..0f7c8bb85 100644 --- a/docs/configuring-playbook-client-hydrogen.md +++ b/docs/configuring-playbook-client-hydrogen.md @@ -1,3 +1,12 @@ + + # Setting up Hydrogen (optional) The playbook can install and configure the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you. diff --git a/roles/custom/matrix-client-hydrogen/defaults/main.yml b/roles/custom/matrix-client-hydrogen/defaults/main.yml index 8d92b9f88..c31fc3002 100644 --- a/roles/custom/matrix-client-hydrogen/defaults/main.yml +++ b/roles/custom/matrix-client-hydrogen/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Matthew Cengia +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/element-hq/hydrogen-web diff --git a/roles/custom/matrix-client-hydrogen/tasks/main.yml b/roles/custom/matrix-client-hydrogen/tasks/main.yml index 9e7445c0b..f5073ce9c 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/main.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-client-hydrogen/tasks/self_check.yml b/roles/custom/matrix-client-hydrogen/tasks/self_check.yml index 4892c40dc..2a894593c 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/self_check.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/self_check.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml b/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml index 08727586c..18c06f3c8 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Matthew Cengia +# SPDX-FileCopyrightText: 2023 Julian Foad +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Hydrogen paths exists diff --git a/roles/custom/matrix-client-hydrogen/tasks/setup_uninstall.yml b/roles/custom/matrix-client-hydrogen/tasks/setup_uninstall.yml index d6caa5b97..d963ac0b8 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-client-hydrogen.service diff --git a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml index c5affb624..2bd1ae7ff 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Hydrogen settings not defined diff --git a/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license b/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license new file mode 100644 index 000000000..86cf6f8f1 --- /dev/null +++ b/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Matthew Cengia +SPDX-FileCopyrightText: 2023 Sergio Durigan Junior + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/templates/labels.j2 b/roles/custom/matrix-client-hydrogen/templates/labels.j2 index 011d02d1d..3431f7157 100644 --- a/roles/custom/matrix-client-hydrogen/templates/labels.j2 +++ b/roles/custom/matrix-client-hydrogen/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_client_hydrogen_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-client-hydrogen/templates/nginx.conf.j2.license b/roles/custom/matrix-client-hydrogen/templates/nginx.conf.j2.license new file mode 100644 index 000000000..c69a90227 --- /dev/null +++ b/roles/custom/matrix-client-hydrogen/templates/nginx.conf.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Aaron Raimist +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license new file mode 100644 index 000000000..f23ca62d3 --- /dev/null +++ b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2021 Aaron Raimist +SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Matthew Cengia + +SPDX-License-Identifier: AGPL-3.0-or-later From 44d91c6383f3ce78ac6771561ef69b2ac6e8e4c3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 18:18:30 +0900 Subject: [PATCH 733/952] Add license information to files for matrix-registration This commit adds copyright attributions in SPDX to the files for matrix-registration following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-registration.md | 8 ++++++++ roles/custom/matrix-registration/defaults/main.yml | 10 ++++++++++ .../matrix-registration/tasks/generate_token.yml | 5 +++++ roles/custom/matrix-registration/tasks/list_tokens.yml | 6 ++++++ roles/custom/matrix-registration/tasks/main.yml | 6 ++++++ .../custom/matrix-registration/tasks/setup_install.yml | 10 ++++++++++ .../matrix-registration/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-registration/tasks/validate_config.yml | 4 ++++ .../matrix-registration/templates/config.yaml.j2 | 6 ++++++ roles/custom/matrix-registration/templates/labels.j2 | 6 ++++++ .../systemd/matrix-registration.service.j2.license | 3 +++ 11 files changed, 70 insertions(+) create mode 100644 roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2.license diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md index 2a08fa681..441c85973 100644 --- a/docs/configuring-playbook-matrix-registration.md +++ b/docs/configuring-playbook-matrix-registration.md @@ -1,3 +1,11 @@ + + # Setting up matrix-registration (optional) > [!WARNING] diff --git a/roles/custom/matrix-registration/defaults/main.yml b/roles/custom/matrix-registration/defaults/main.yml index 77d8f371d..0f2298904 100644 --- a/roles/custom/matrix-registration/defaults/main.yml +++ b/roles/custom/matrix-registration/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-registration is a simple python application to have a token based Matrix registration # See: https://zeratax.github.io/matrix-registration/ diff --git a/roles/custom/matrix-registration/tasks/generate_token.yml b/roles/custom/matrix-registration/tasks/generate_token.yml index aa2b0111f..0a3e47258 100644 --- a/roles/custom/matrix-registration/tasks/generate_token.yml +++ b/roles/custom/matrix-registration/tasks/generate_token.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-registration/tasks/list_tokens.yml b/roles/custom/matrix-registration/tasks/list_tokens.yml index 1001c4fa2..f5c85a04d 100644 --- a/roles/custom/matrix-registration/tasks/list_tokens.yml +++ b/roles/custom/matrix-registration/tasks/list_tokens.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Call matrix-registration list all tokens API diff --git a/roles/custom/matrix-registration/tasks/main.yml b/roles/custom/matrix-registration/tasks/main.yml index 7b5647dc0..dcae5528e 100644 --- a/roles/custom/matrix-registration/tasks/main.yml +++ b/roles/custom/matrix-registration/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-registration/tasks/setup_install.yml b/roles/custom/matrix-registration/tasks/setup_install.yml index 2358da0c4..06ebc9e41 100644 --- a/roles/custom/matrix-registration/tasks/setup_install.yml +++ b/roles/custom/matrix-registration/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-registration/tasks/setup_uninstall.yml b/roles/custom/matrix-registration/tasks/setup_uninstall.yml index 97c144358..b8037d59d 100644 --- a/roles/custom/matrix-registration/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-registration/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-registration service diff --git a/roles/custom/matrix-registration/tasks/validate_config.yml b/roles/custom/matrix-registration/tasks/validate_config.yml index 50996a7cb..9e76a19c7 100644 --- a/roles/custom/matrix-registration/tasks/validate_config.yml +++ b/roles/custom/matrix-registration/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-registration settings not defined diff --git a/roles/custom/matrix-registration/templates/config.yaml.j2 b/roles/custom/matrix-registration/templates/config.yaml.j2 index 39211b249..2884d6800 100644 --- a/roles/custom/matrix-registration/templates/config.yaml.j2 +++ b/roles/custom/matrix-registration/templates/config.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + server_location: {{ matrix_registration_server_location|to_json }} server_name: {{ matrix_registration_server_name|to_json }} shared_secret: {{ matrix_registration_shared_secret|to_json }} diff --git a/roles/custom/matrix-registration/templates/labels.j2 b/roles/custom/matrix-registration/templates/labels.j2 index 7a87d1b06..7961e84aa 100644 --- a/roles/custom/matrix-registration/templates/labels.j2 +++ b/roles/custom/matrix-registration/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_registration_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2.license b/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2.license new file mode 100644 index 000000000..9d697f20f --- /dev/null +++ b/roles/custom/matrix-registration/templates/systemd/matrix-registration.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2020 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From fe72de7dc540657240b68a63b0a352db9515a2bf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 23:04:10 +0900 Subject: [PATCH 734/952] Update docs/configuring-playbook.md: copy from the MASH project Copied from https://github.com/mother-of-all-self-hosting/mash-playbook/blob/802032cda74e0d0088ebb198a87165ce2e71ebbc/docs/configuring-playbook.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 2220c9d3f..30f93e0ad 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -24,7 +24,7 @@ If you've configured your DNS records and retrieved the playbook's source code t 2. copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`) -3. edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file. +3. edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files (after importing external roles with `just update` into `roles/galaxy`) and see if there's something you'd like to copy over and override in your `vars.yml` configuration file. 4. copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`) From f57ee8d3e0b825ef5641935077e39d3131521320 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 23:06:47 +0900 Subject: [PATCH 735/952] Update docs/maintenance-postgres.md: copy from the MASH playbook Copied from https://github.com/mother-of-all-self-hosting/mash-playbook/blob/802032cda74e0d0088ebb198a87165ce2e71ebbc/docs/services/postgres.md Signed-off-by: Suguru Hirahara --- docs/maintenance-postgres.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index 7beff8e7c..70596f90f 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -5,7 +5,7 @@ SPDX-FileCopyrightText: 2020 Hardy Erlinger SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors SPDX-FileCopyrightText: 2021 Marc Leuser SPDX-FileCopyrightText: 2024 Kim Brose -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> @@ -23,7 +23,7 @@ Table of contents: ## Getting a database terminal -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. +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. If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available. @@ -59,9 +59,9 @@ Example playbook invocations: ## Backing up PostgreSQL -To automatically make Postgres database backups on a fixed schedule, see [Setting up Postgres backup](configuring-playbook-postgres-backup.md). +To automatically make Postgres database backups on a fixed schedule, consider enabling the [Postgres Backup](configuring-playbook-postgres-backup.md) service. -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: +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: ```sh /usr/bin/docker exec \ From 4df7b983ed3e80fe2c93a76b40885d0546b6a21f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 25 Feb 2025 23:09:19 +0900 Subject: [PATCH 736/952] Update docs: title of the document for configuring DNS settings This follows https://github.com/mother-of-all-self-hosting/mash-playbook/blob/802032cda74e0d0088ebb198a87165ce2e71ebbc/docs/configuring-dns.md Signed-off-by: Suguru Hirahara --- docs/README.md | 2 +- docs/configuring-dns.md | 4 ++-- docs/configuring-playbook.md | 2 +- docs/getting-the-playbook.md | 2 +- docs/installing.md | 2 +- docs/prerequisites.md | 2 +- docs/quick-start.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/README.md b/docs/README.md index f1765920f..0473b77e5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -19,7 +19,7 @@ There are two installation guides available for beginners and advanced users. - [Prerequisites](prerequisites.md) - - [Configuring your DNS settings](configuring-dns.md) + - [Configuring DNS settings](configuring-dns.md) - [Getting the playbook](getting-the-playbook.md) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 2b2b425eb..b88195ec9 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -15,9 +15,9 @@ SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> -# Configuring your DNS settings +# Configuring DNS settings -[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +[Prerequisites](prerequisites.md) > Configuring DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) To set up Matrix on your domain, you'd need to do some DNS configuration. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 30f93e0ad..756986f23 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -16,7 +16,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Configuring the playbook -[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md) +[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md) If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory: diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md index d1c951fa5..7f725038b 100644 --- a/docs/getting-the-playbook.md +++ b/docs/getting-the-playbook.md @@ -7,7 +7,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Getting the playbook -[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) This Ansible playbook is meant to be executed on your own computer (not the Matrix server). diff --git a/docs/installing.md b/docs/installing.md index 6bc0a463e..c11a79b2b 100644 --- a/docs/installing.md +++ b/docs/installing.md @@ -14,7 +14,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Installing -[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing +[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing If you've configured your DNS records and the playbook, you can start the installation procedure. diff --git a/docs/prerequisites.md b/docs/prerequisites.md index 0e65548b5..dc0b73e5d 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Prerequisites -Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) +Prerequisites > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md) 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. diff --git a/docs/quick-start.md b/docs/quick-start.md index cedb18a9d..21b8515e2 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -37,7 +37,7 @@ One of the main reasons of basic errors is using an incompatible version of requ ## Configure your DNS settings -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) +This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring DNS settings](configuring-dns.md) After installing and configuring prerequisites, you will need to **configure DNS records**. From eba494eb8640c6a23a99c9bc3f78467d9aaec3c0 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 25 Feb 2025 14:35:25 +0000 Subject: [PATCH 737/952] Update halfshot/matrix-hookshot Docker tag to v6.0.3 --- roles/custom/matrix-bridge-hookshot/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 5483890ec..0bf53fbbe 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -17,7 +17,7 @@ matrix_hookshot_container_additional_networks_auto: [] matrix_hookshot_container_additional_networks_custom: [] # renovate: datasource=docker depName=halfshot/matrix-hookshot -matrix_hookshot_version: 6.0.2 +matrix_hookshot_version: 6.0.3 matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_registry_prefix }}matrix-org/matrix-hookshot:{{ matrix_hookshot_version }}" matrix_hookshot_docker_image_registry_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else matrix_hookshot_docker_image_registry_prefix_upstream }}" From 6d44f6d7afa6f1ddd110b12b88ed975915914fb2 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 25 Feb 2025 14:35:32 +0000 Subject: [PATCH 738/952] Update vectorim/element-web Docker tag to v1.11.93 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index ef415efa1..655a020a8 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=vectorim/element-web -matrix_client_element_version: v1.11.92 +matrix_client_element_version: v1.11.93 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" From 7d4f9fe7dc6e37335433ed868229898536b4a92e Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 25 Feb 2025 17:53:03 +0200 Subject: [PATCH 739/952] Upgrade matrix-corporal (3.1.3 -> 3.1.4) and switch where its gets pulled from From 3.1.4 and onward, container images will be published to ghcr.io instead of docker.io. These images are built for arm64 and amd64, but not for arm32 anymore. --- group_vars/matrix_servers | 2 +- roles/custom/matrix-corporal/defaults/main.yml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index c71911822..623fd763d 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3427,7 +3427,7 @@ matrix_corporal_systemd_required_services_list_auto: | matrix_corporal_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_corporal_docker_image_registry_prefix_upstream_default }}" -matrix_corporal_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" +matrix_corporal_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}" matrix_corporal_container_http_gateway_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '41080') if matrix_playbook_service_host_bind_interface_prefix else '' }}" matrix_corporal_container_http_api_host_bind_port: "{{ (matrix_playbook_service_host_bind_interface_prefix ~ '41081') if matrix_playbook_service_host_bind_interface_prefix else '' }}" diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml index b446acd3f..9d55096a9 100644 --- a/roles/custom/matrix-corporal/defaults/main.yml +++ b/roles/custom/matrix-corporal/defaults/main.yml @@ -4,8 +4,8 @@ matrix_corporal_enabled: true -# renovate: datasource=docker depName=devture/matrix-corporal -matrix_corporal_version: 3.1.3 +# renovate: datasource=docker depName=ghcr.io/devture/matrix-corporal +matrix_corporal_version: 3.1.4 matrix_corporal_container_image_self_build: false matrix_corporal_container_image_self_build_repo: "https://github.com/devture/matrix-corporal.git" @@ -84,7 +84,7 @@ matrix_corporal_systemd_required_services_list_custom: [] matrix_corporal_docker_image: "{{ matrix_corporal_docker_image_registry_prefix }}devture/matrix-corporal:{{ matrix_corporal_docker_image_tag }}" matrix_corporal_docker_image_registry_prefix: "{{ 'localhost/' if matrix_corporal_container_image_self_build else matrix_corporal_docker_image_registry_prefix_upstream }}" matrix_corporal_docker_image_registry_prefix_upstream: "{{ matrix_corporal_docker_image_registry_prefix_upstream_default }}" -matrix_corporal_docker_image_registry_prefix_upstream_default: docker.io/ +matrix_corporal_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_corporal_docker_image_tag: "{{ matrix_corporal_version }}" # for backward-compatibility matrix_corporal_docker_image_force_pull: "{{ matrix_corporal_docker_image.endswith(':latest') }}" From 5c708339a0929f11787f29addee77fe8f826acae Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 25 Feb 2025 21:28:23 +0200 Subject: [PATCH 740/952] Upgrade Synapse (v1.124.0 -> v1.125.0) --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 2b469c459..0925e2c15 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.124.0 +matrix_synapse_version: v1.125.0 matrix_synapse_username: '' matrix_synapse_uid: '' From 9493356adb6b0368407f1af78a761e60fd29b343 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 25 Feb 2025 19:49:08 +0000 Subject: [PATCH 741/952] Update dependency setuptools to v75.8.1 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index e58915fa0..fc9e436fb 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.8.0 +setuptools==75.8.1 snowballstemmer==2.2.0 Sphinx==8.2.1 sphinx-intl==2.3.1 From ae9185210953933f8959e4c8c3699cc7b8843150 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 07:15:26 +0200 Subject: [PATCH 742/952] Upgrade exim-relay (v4.98-r0-4-3 -> 4.98.1-r0-0-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 602bd55a3..90f56d006 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98-r0-4-3 + version: 4.98.1-r0-0-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-1 From 5007ad453efd40022f66ee20411a2df8d9b018c2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 07:18:47 +0200 Subject: [PATCH 743/952] Fix exim-relay version tag (4.98.1-r0-0-0 -> v4.98.1-r0-0-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 90f56d006..207ff01e9 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: 4.98.1-r0-0-0 + version: v4.98.1-r0-0-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-1 From 74bdd8cbe5e78cf90cee993f1018aa6705382bf5 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 07:39:55 +0200 Subject: [PATCH 744/952] `docker.io/devture/ansible` -> `ghcr.io/devture/ansible` --- docs/ansible.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/docs/ansible.md b/docs/ansible.md index 15f00632f..a4a595002 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -38,7 +38,7 @@ If using the `pip` method, do note that the `ansible-playbook` binary may not be ## Using Ansible via Docker -Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image). +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). This ensures that: @@ -63,13 +63,15 @@ Alternatively, you can leave your `inventory/hosts` as is and specify the connec Run this from the playbook's directory: ```sh -docker run -it --rm \ +docker run \ +-it \ +--rm \ --privileged \ --pid=host \ -w /work \ --v `pwd`:/work \ +--mount type=bind,src=`pwd`,dst=/work \ --entrypoint=/bin/sh \ -docker.io/devture/ansible:2.18.1-r0-2 +ghcr.io/devture/ansible:11.1.0-r0-0 ``` Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code. @@ -83,15 +85,17 @@ Finally, you can execute `just` or `ansible-playbook …` (e.g. `ansible-playboo Run this from the playbook's directory: ```sh -docker run -it --rm \ +docker run \ +-it \ +--rm \ -w /work \ --v `pwd`:/work \ --v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro \ +--mount type=bind,src=`pwd`,dst=/work \ +--mount type=bind,src$HOME/.ssh/id_ed25519,dst=/root/.ssh/id_ed25519,ro \ --entrypoint=/bin/sh \ -docker.io/devture/ansible:2.18.1-r0-2 +ghcr.io/devture/ansible:11.1.0-r0-0 ``` -The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part. +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. 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. @@ -101,7 +105,7 @@ Finally, you execute `just` or `ansible-playbook …` commands as per normal now #### If you don't use SSH keys for authentication -If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`). +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`). 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: From 1b05343aba19852d627ded4934c0580960aaadb9 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 08:00:17 +0200 Subject: [PATCH 745/952] Remove Email2Matrix support --- CHANGELOG.md | 9 ++ docs/configuring-playbook-email2matrix.md | 136 +----------------- docs/configuring-playbook.md | 2 +- docs/self-building.md | 1 - group_vars/matrix_servers | 30 ---- .../matrix-email2matrix/defaults/main.yml | 80 ----------- .../custom/matrix-email2matrix/tasks/main.yml | 25 ---- .../tasks/setup_install.yml | 78 ---------- .../tasks/setup_uninstall.yml | 31 ---- .../tasks/validate_config.yml | 27 ---- .../templates/config.json.j2 | 14 -- .../templates/config.json.j2.license | 3 - .../systemd/matrix-email2matrix.service.j2 | 44 ------ .../matrix-email2matrix.service.j2.license | 4 - .../tasks/validate_config.yml | 12 ++ setup.yml | 1 - 16 files changed, 29 insertions(+), 468 deletions(-) delete mode 100644 roles/custom/matrix-email2matrix/defaults/main.yml delete mode 100644 roles/custom/matrix-email2matrix/tasks/main.yml delete mode 100644 roles/custom/matrix-email2matrix/tasks/setup_install.yml delete mode 100644 roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml delete mode 100644 roles/custom/matrix-email2matrix/tasks/validate_config.yml delete mode 100644 roles/custom/matrix-email2matrix/templates/config.json.j2 delete mode 100644 roles/custom/matrix-email2matrix/templates/config.json.j2.license delete mode 100644 roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 delete mode 100644 roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license diff --git a/CHANGELOG.md b/CHANGELOG.md index a25aebfda..070d18e17 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,12 @@ +# 2025-02-26 + +## 🪦 Bye-bye, Email2Matrix + +The [Email2Matrix](./docs/configuring-playbook-email2matrix.md) service has been superseded by the [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) bridge for a long time now and was completely removed from the playbook today. + +If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually as described in the [Uninstalling Email2Matrix manually](./docs/configuring-playbook-email2matrix.md#uninstalling-email2matrix-manually) section of the documentation. The playbook will warn you if there are any `matrix_email2matrix_*` variables still remaining in your configuration. + + # 2025-02-23 ## The playbook defaults to exposing the Coturn STUN port (3478) over UDP once again diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index ce2cd2570..4044ec565 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -10,139 +10,17 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up Email2Matrix (optional, deprecated) -**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. +🪦 The playbook used to be able to install and configure [Email2Matrix](https://github.com/devture/email2matrix), but no longer includes this component. -The playbook can install and configure [Email2Matrix](https://github.com/devture/email2matrix) for you. +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). -See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you. -## Preparation +## Uninstalling Email2Matrix manually -### Port availability - -Ensure that port 25 is available on your Matrix server and open in your firewall. - -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). - -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. - -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). - -### Register a dedicated Matrix user (optional, recommended) - -We recommend that you create a dedicated Matrix user for Email2Matrix. - -Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`. - -You can use the playbook to [register a new user](registering-users.md): +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: ```sh -ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=email2matrix password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user -``` - -Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later. - -### Obtain an access token - -Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). - -> [!WARNING] -> Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone. - -### Join to rooms as the sender user manually - -ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually. - -For each new room you would like the user to deliver messages to, invite the user to the room. - -Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account. - -Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out. - -Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below. - -## Adjusting DNS records - -To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this: - -| Type | Host | Priority | Weight | Port | Target | -|------|----------|----------|--------|------|------------------------------------| -| MX | `matrix` | 10 | 0 | - | `matrix.example.com` | - -## Adjusting the playbook configuration - -To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token). - -```yaml -matrix_email2matrix_enabled: true - -# You need at least 1 mailbox. -matrix_email2matrix_matrix_mappings: - - MailboxName: "mailbox1" - MatrixRoomId: "!qporfwt:{{ matrix_domain }}" - MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" - MatrixUserId: "@email2matrix1:{{ matrix_domain }}" - MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE" - IgnoreSubject: false - IgnoreBody: false - SkipMarkdown: false - - - MailboxName: "mailbox2" - MatrixRoomId: "!aaabaa:{{ matrix_domain }}" - MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" - MatrixUserId: "@email2matrix2:{{ matrix_domain }}" - MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE" - IgnoreSubject: true - IgnoreBody: false - SkipMarkdown: true -``` - -where: - -* MailboxName — local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId -* MatrixRoomId — internal ID of the room, to which received emails are sent as Matrix message -* MatrixHomeserverUrl — URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable -* MatrixUserId — the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain) -* MatrixAccessToken — sender user's access token -* IgnoreSubject — if set to "true", the subject is not bridged to Matrix -* IgnoreBody — if set to "true", the message body is not bridged to Matrix -* SkipMarkdown — if set to "true", emails are bridged as plain text Matrix message instead of Markdown (actually HTML) - -Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md). - -### Extending the configuration - -There are some additional things you may wish to configure about the component. - -Take a look at: - -- `roles/custom/matrix-email2matrix/defaults/main.yml` for some variables that you can customize via your `vars.yml` file - -## Installing - -After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: - - -```sh -ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start -``` - -**Notes**: - -- The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all` - - `just install-service email2matrix` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too. - -- After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected. - -## Troubleshooting - -As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-email2matrix`. - -### Increase logging verbosity - -If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: - -```yaml -matrix_email2matrix_misc_debug: true +systemctl disable --now matrix-email2matrix.service + +rm -rf /matrix/email2matrix ``` diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 756986f23..9efe8d065 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -261,7 +261,7 @@ Various services that don't fit any other categories. - [Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md)) -- [Setting up Email2Matrix](configuring-playbook-email2matrix.md) (unmaintained; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-postmoogle.md)) +- [Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-postmoogle.md)) - [Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md)) diff --git a/docs/self-building.md b/docs/self-building.md index 543065d89..d09e587df 100644 --- a/docs/self-building.md +++ b/docs/self-building.md @@ -38,7 +38,6 @@ Possibly outdated list of roles where self-building the Docker image is currentl - `matrix-bot-honoroit` - `matrix-bot-matrix-reminder-bot` - `matrix-bot-maubot` -- `matrix-email2matrix` - `matrix-pantalaimon` Adding self-building support to other roles is welcome. Feel free to contribute! diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 623fd763d..6f1b45607 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -3714,36 +3714,6 @@ matrix_dynamic_dns_container_network: matrix-dynamic-dns # ###################################################################### -###################################################################### -# -# matrix-email2matrix -# -###################################################################### - -matrix_email2matrix_enabled: false - -matrix_email2matrix_systemd_required_services_list_auto: | - {{ - matrix_addons_homeserver_systemd_services_list - }} - -matrix_email2matrix_docker_image_registry_prefix_upstream: "{{ matrix_container_global_registry_prefix_override if matrix_container_global_registry_prefix_override else matrix_email2matrix_docker_image_registry_prefix_upstream_default }}" - -matrix_email2matrix_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm32', 'arm64'] }}" - -matrix_email2matrix_container_network: "{{ matrix_addons_container_network }}" - -matrix_email2matrix_container_additional_networks_auto: |- - {{ - ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network]) - }} - -###################################################################### -# -# /matrix-email2matrix -# -###################################################################### - ###################################################################### # # jitsi diff --git a/roles/custom/matrix-email2matrix/defaults/main.yml b/roles/custom/matrix-email2matrix/defaults/main.yml deleted file mode 100644 index 43569a6c5..000000000 --- a/roles/custom/matrix-email2matrix/defaults/main.yml +++ /dev/null @@ -1,80 +0,0 @@ -# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2021 MDAD project contributors -# SPDX-FileCopyrightText: 2021 Ahmad Haghighi -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Nikita Chernyi -# SPDX-FileCopyrightText: 2023 Samuel Meenzen -# SPDX-FileCopyrightText: 2024 Suguru Hirahara -# -# SPDX-License-Identifier: AGPL-3.0-or-later - ---- - -# Project source code URL: https://github.com/devture/email2matrix - -matrix_email2matrix_enabled: true - -matrix_email2matrix_base_path: "{{ matrix_base_data_path }}/email2matrix" -matrix_email2matrix_config_dir_path: "{{ matrix_email2matrix_base_path }}/config" -matrix_email2matrix_docker_src_files_path: "{{ matrix_email2matrix_base_path }}/docker-src" - -matrix_email2matrix_container_image_self_build: false -matrix_email2matrix_container_image_self_build_repo: "https://github.com/devture/email2matrix.git" -matrix_email2matrix_container_image_self_build_branch: "{{ matrix_email2matrix_version }}" - -# renovate: datasource=docker depName=devture/email2matrix -matrix_email2matrix_version: 1.1.0 -matrix_email2matrix_docker_image: "{{ matrix_email2matrix_docker_image_registry_prefix }}devture/email2matrix:{{ matrix_email2matrix_version }}" -matrix_email2matrix_docker_image_registry_prefix: "{{ 'localhost/' if matrix_email2matrix_container_image_self_build else matrix_email2matrix_docker_image_registry_prefix_upstream }}" -matrix_email2matrix_docker_image_registry_prefix_upstream: "{{ matrix_email2matrix_docker_image_registry_prefix_upstream_default }}" -matrix_email2matrix_docker_image_registry_prefix_upstream_default: docker.io/ -matrix_email2matrix_docker_image_force_pull: "{{ matrix_email2matrix_docker_image.endswith(':latest') }}" - -matrix_email2matrix_container_network: "" - -matrix_email2matrix_container_additional_networks: "{{ matrix_email2matrix_container_additional_networks_auto + matrix_email2matrix_container_additional_networks_custom }}" -matrix_email2matrix_container_additional_networks_auto: [] -matrix_email2matrix_container_additional_networks_custom: [] - -# A list of extra arguments to pass to the container -matrix_email2matrix_container_extra_arguments: [] - -# List of systemd services that matrix-corporal.service depends on -matrix_email2matrix_systemd_required_services_list: "{{ matrix_email2matrix_systemd_required_services_list_default + matrix_email2matrix_systemd_required_services_list_auto + matrix_email2matrix_systemd_required_services_list_custom }}" -matrix_email2matrix_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" -matrix_email2matrix_systemd_required_services_list_auto: [] -matrix_email2matrix_systemd_required_services_list_custom: [] - -# Controls where the matrix-email2matrix container exposes the SMTP (tcp/2525 in the container). -# -# Takes an ":" or "" value (e.g. "127.0.0.1:2525"). -# -# By default, we listen on port 25 on all of the host's network interfaces. -matrix_email2matrix_smtp_host_bind_port: "25" - -matrix_email2matrix_smtp_hostname: "{{ matrix_server_fqn_matrix }}" - -# A list of mailbox to Matrix mappings. -# -# Example: -# matrix_email2matrix_matrix_mappings: -# - MailboxName: "mailbox1" -# MatrixRoomId: "!qporfwt:{{ matrix_domain }}" -# MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" -# MatrixUserId: "@email2matrix1:{{ matrix_domain }}" -# MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE" -# IgnoreSubject: false -# IgnoreBody: false -# SkipMarkdown: false -# -# - MailboxName: "mailbox2" -# MatrixRoomId: "!aaabaa:{{ matrix_domain }}" -# MatrixHomeserverUrl: "{{ matrix_homeserver_url }}" -# MatrixUserId: "@email2matrix2:{{ matrix_domain }}" -# MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE" -# IgnoreSubject: true -# IgnoreBody: false -# SkipMarkdown: true -matrix_email2matrix_matrix_mappings: [] - -matrix_email2matrix_misc_debug: false diff --git a/roles/custom/matrix-email2matrix/tasks/main.yml b/roles/custom/matrix-email2matrix/tasks/main.yml deleted file mode 100644 index f557ccaa0..000000000 --- a/roles/custom/matrix-email2matrix/tasks/main.yml +++ /dev/null @@ -1,25 +0,0 @@ -# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# -# SPDX-License-Identifier: AGPL-3.0-or-later - ---- - -- tags: - - setup-all - - setup-email2matrix - - install-all - - install-email2matrix - block: - - when: matrix_email2matrix_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml" - - - when: matrix_email2matrix_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml" - -- tags: - - setup-all - - setup-email2matrix - block: - - when: not matrix_email2matrix_enabled | bool - ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml" diff --git a/roles/custom/matrix-email2matrix/tasks/setup_install.yml b/roles/custom/matrix-email2matrix/tasks/setup_install.yml deleted file mode 100644 index 242deb01d..000000000 --- a/roles/custom/matrix-email2matrix/tasks/setup_install.yml +++ /dev/null @@ -1,78 +0,0 @@ -# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Nikita Chernyi -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Sebastian Gumprich -# SPDX-FileCopyrightText: 2024 David Mehren -# -# SPDX-License-Identifier: AGPL-3.0-or-later - ---- - -- name: Ensure Email2Matrix paths exist - ansible.builtin.file: - path: "{{ item.path }}" - state: directory - mode: 0750 - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - with_items: - - {path: "{{ matrix_email2matrix_base_path }}", when: true} - - {path: "{{ matrix_email2matrix_config_dir_path }}", when: true} - - {path: "{{ matrix_email2matrix_docker_src_files_path }}", when: "{{ matrix_email2matrix_container_image_self_build }}"} - when: "item.when | bool" - -- name: Ensure Email2Matrix configuration file created - ansible.builtin.template: - src: "{{ role_path }}/templates/config.json.j2" - dest: "{{ matrix_email2matrix_config_dir_path }}/config.json" - owner: "{{ matrix_user_username }}" - group: "{{ matrix_user_groupname }}" - mode: 0640 - -- name: Ensure Email2Matrix image is pulled - community.docker.docker_image: - name: "{{ matrix_email2matrix_docker_image }}" - source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}" - force_source: "{{ matrix_email2matrix_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_email2matrix_docker_image_force_pull }}" - when: "not matrix_email2matrix_container_image_self_build | bool" - register: result - retries: "{{ devture_playbook_help_container_retries_count }}" - delay: "{{ devture_playbook_help_container_retries_delay }}" - until: result is not failed - -- name: Ensure Email2Matrix repository is present on self-build - ansible.builtin.git: - repo: "{{ matrix_email2matrix_container_image_self_build_repo }}" - dest: "{{ matrix_email2matrix_docker_src_files_path }}" - version: "{{ matrix_email2matrix_container_image_self_build_branch }}" - force: "yes" - become: true - become_user: "{{ matrix_user_username }}" - register: matrix_email2matrix_git_pull_results - when: "matrix_email2matrix_container_image_self_build | bool" - -- name: Ensure Email2Matrix Docker image is built - community.docker.docker_image: - name: "{{ matrix_email2matrix_docker_image }}" - source: build - force_source: "{{ matrix_email2matrix_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}" - force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_email2matrix_git_pull_results.changed }}" - build: - dockerfile: etc/docker/Dockerfile - path: "{{ matrix_email2matrix_docker_src_files_path }}" - pull: true - when: "matrix_email2matrix_container_image_self_build | bool" - -- name: Ensure matrix-email2matrix container network is created - community.general.docker_network: - enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}" - name: "{{ matrix_email2matrix_container_network }}" - driver: bridge - driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}" - -- name: Ensure matrix-email2matrix.service installed - ansible.builtin.template: - src: "{{ role_path }}/templates/systemd/matrix-email2matrix.service.j2" - dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-email2matrix.service" - mode: 0644 diff --git a/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml b/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml deleted file mode 100644 index e10464f72..000000000 --- a/roles/custom/matrix-email2matrix/tasks/setup_uninstall.yml +++ /dev/null @@ -1,31 +0,0 @@ -# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Sebastian Gumprich -# -# SPDX-License-Identifier: AGPL-3.0-or-later - ---- - -- name: Check existence of matrix-email2matrix service - ansible.builtin.stat: - path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-email2matrix.service" - register: matrix_email2matrix_service_stat - -- when: matrix_email2matrix_service_stat.stat.exists | bool - block: - - name: Ensure matrix-email2matrix is stopped - ansible.builtin.service: - name: matrix-email2matrix - state: stopped - enabled: false - daemon_reload: true - - - name: Ensure matrix-email2matrix.service doesn't exist - ansible.builtin.file: - path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-email2matrix.service" - state: absent - - - name: Ensure Email2Matrix data path doesn't exist - ansible.builtin.file: - path: "{{ matrix_email2matrix_base_path }}" - state: absent diff --git a/roles/custom/matrix-email2matrix/tasks/validate_config.yml b/roles/custom/matrix-email2matrix/tasks/validate_config.yml deleted file mode 100644 index 17533397f..000000000 --- a/roles/custom/matrix-email2matrix/tasks/validate_config.yml +++ /dev/null @@ -1,27 +0,0 @@ -# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev -# -# SPDX-License-Identifier: AGPL-3.0-or-later - ---- - -- name: Fail if no Email2Matrix mappings - ansible.builtin.fail: - msg: > - You need to define at least one mapping in `matrix_email2matrix_matrix_mappings` for enabling Email2Matrix. - when: "matrix_email2matrix_matrix_mappings | length == 0" - -- name: Fail if required Email2Matrix settings not defined - ansible.builtin.fail: - msg: >- - You need to define a required configuration setting (`{{ item.name }}`). - when: "item.when | bool and vars[item.name] == ''" - with_items: - - {'name': 'matrix_email2matrix_container_network', when: true} - -- name: (Deprecation) Catch and report renamed Email2Matrix variables - ansible.builtin.fail: - msg: >- - The variable `{{ item.old }}` is deprecated. Please use `{{ item.new }}` instead. - when: "item.old in vars" - with_items: - - {'old': 'matrix_email2matrix_docker_image_name_prefix', 'new': 'matrix_email2matrix_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-email2matrix/templates/config.json.j2 b/roles/custom/matrix-email2matrix/templates/config.json.j2 deleted file mode 100644 index a7ca7bc47..000000000 --- a/roles/custom/matrix-email2matrix/templates/config.json.j2 +++ /dev/null @@ -1,14 +0,0 @@ -#jinja2: lstrip_blocks: "True" -{ - "Smtp": { - "ListenInterface": "0.0.0.0:2525", - "Hostname": {{ matrix_email2matrix_smtp_hostname|to_json }}, - "Workers": 10 - }, - "Matrix": { - "Mappings": {{ matrix_email2matrix_matrix_mappings | to_nice_json }} - }, - "Misc": { - "Debug": {{ matrix_email2matrix_misc_debug|to_json }} - } -} diff --git a/roles/custom/matrix-email2matrix/templates/config.json.j2.license b/roles/custom/matrix-email2matrix/templates/config.json.j2.license deleted file mode 100644 index 2fe1c727d..000000000 --- a/roles/custom/matrix-email2matrix/templates/config.json.j2.license +++ /dev/null @@ -1,3 +0,0 @@ -SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev - -SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 deleted file mode 100644 index 4b84d13dd..000000000 --- a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2 +++ /dev/null @@ -1,44 +0,0 @@ -#jinja2: lstrip_blocks: "True" -[Unit] -Description=Email2Matrix -{% for service in matrix_email2matrix_systemd_required_services_list %} -Requires={{ service }} -After={{ service }} -{% endfor %} -DefaultDependencies=no - -[Service] -Type=simple -Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' -ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-email2matrix 2>/dev/null || true' - -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ - --rm \ - --name=matrix-email2matrix \ - --log-driver=none \ - --user={{ matrix_user_uid }}:{{ matrix_user_gid }} \ - --cap-drop=ALL \ - --read-only \ - --network={{ matrix_email2matrix_container_network }} \ - -p {{ matrix_email2matrix_smtp_host_bind_port }}:2525 \ - --mount type=bind,src={{ matrix_email2matrix_config_dir_path }}/config.json,dst=/config.json,ro \ - {% for arg in matrix_email2matrix_container_extra_arguments %} - {{ arg }} \ - {% endfor %} - {{ matrix_email2matrix_docker_image }} - -{% for network in matrix_email2matrix_container_additional_networks %} -ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-email2matrix -{% endfor %} - -ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-email2matrix - -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-email2matrix 2>/dev/null || true' -ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-email2matrix 2>/dev/null || true' -Restart=always -RestartSec=30 -SyslogIdentifier=matrix-email2matrix - -[Install] -WantedBy=multi-user.target diff --git a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license b/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license deleted file mode 100644 index d29979396..000000000 --- a/roles/custom/matrix-email2matrix/templates/systemd/matrix-email2matrix.service.j2.license +++ /dev/null @@ -1,4 +0,0 @@ -SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev -SPDX-FileCopyrightText: 2020 Chris van Dijk - -SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 4232196d3..0043e8dd5 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -476,3 +476,15 @@ The following variables in your configuration need to be removed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mautrix_hangouts_.*') | list | items2dict" + +- name: (Deprecation) Catch and report Email2Matrix variables + ansible.builtin.fail: + msg: |- + The Email2Matrix service has been superseded by the Postmoogle bridge for a long time now and was completely removed from the playbook in February 2025. + + Please change your configuration (`vars.yml`) to remove all `matrix_email2matrix_*` variables. + + You may also wish to uninstall the bridge manually. See `docs/configuring-playbook-email2matrix.md` for more information. + + The following variables in your configuration need to be removed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_email2matrix_.*') | map(attribute='key') | join(', ') }} + when: "vars | dict2items | selectattr('key', 'match', 'matrix_email2matrix_.*') | list | items2dict" diff --git a/setup.yml b/setup.yml index d36f16c6b..7149b3cdf 100644 --- a/setup.yml +++ b/setup.yml @@ -126,7 +126,6 @@ - custom/matrix-dimension - galaxy/etherpad - custom/matrix-sliding-sync - - custom/matrix-email2matrix - custom/matrix-sygnal - galaxy/ntfy - custom/matrix-static-files From 852b9ebdc166bf9411f838b2eaecdf634d594761 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 08:01:27 +0200 Subject: [PATCH 746/952] Adjust "installed using this playbook" links when linking to specific components We previously made "this playbook" a link to some specific component. This is somewhat misleading. Reading the text and seeing that "this playbook" is a link, one might think that "this playbook" actually links to the playbook's home page or something, not to the specific component which could be "installed using this playbook". This patch adjusts the markup so that the whole phrase "installed using this playbook" is turned into a link (to the specific component's page). This makes it more obvious where we're linking. This work was initially done for the Email2Matrix docs page in 1b05343aba19852d627ded4934c0580960aaadb9. This patch brings the same change to all other instances. --- docs/configuring-playbook-bot-chatgpt.md | 2 +- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bridge-appservice-webhooks.md | 2 +- docs/configuring-playbook-bridge-mautrix-bridges.md | 2 +- docs/configuring-playbook-bridge-mautrix-facebook.md | 2 +- docs/configuring-playbook-bridge-mautrix-instagram.md | 2 +- docs/configuring-playbook.md | 8 ++++---- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md index 74e687bbc..6bf3b429a 100644 --- a/docs/configuring-playbook-bot-chatgpt.md +++ b/docs/configuring-playbook-bot-chatgpt.md @@ -8,7 +8,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up matrix-bot-chatgpt (optional, unmaintained) -**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one. +**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be [installed using this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one. The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you. diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md index 2bf69ef61..074f843f5 100644 --- a/docs/configuring-playbook-bot-go-neb.md +++ b/docs/configuring-playbook-bot-go-neb.md @@ -10,7 +10,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up Go-NEB (optional, unmaintained) -**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one. +**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one. The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you. diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md index 8113341d8..d7df18ed6 100644 --- a/docs/configuring-playbook-bridge-appservice-webhooks.md +++ b/docs/configuring-playbook-bridge-appservice-webhooks.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later # Setting up Appservice Webhooks bridging (optional, deprecated) -**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one. +**Note**: This bridge 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. 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. diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index 12f70a66e..def918c84 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -15,7 +15,7 @@ To enable the bridge, add the following configuration to your `inventory/host_va matrix_mautrix_SERVICENAME_enabled: true ``` -**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). +**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges. diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md index f5f6d581f..e56c2ee38 100644 --- a/docs/configuring-playbook-bridge-mautrix-facebook.md +++ b/docs/configuring-playbook-bridge-mautrix-facebook.md @@ -14,7 +14,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) -**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. +**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one. The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you. diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md index c4694e0f1..4dcc780bf 100644 --- a/docs/configuring-playbook-bridge-mautrix-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-instagram.md @@ -11,7 +11,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) -**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. +**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be [installed using this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one. The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 9efe8d065..769ec21ab 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -257,15 +257,15 @@ Various services that don't fit any other categories. - [Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync) -- [Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md)) +- [Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md)) - [Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md)) -- [Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-postmoogle.md)) +- [Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md)) -- [Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md)) +- [Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md)) -- [Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md)) +- [Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bot-baibot.md)) - [Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md)) From 0329cbb1b0714fce6a8604a812a92319463912c9 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 08:05:16 +0200 Subject: [PATCH 747/952] Remove leftover `matrix_email2matrix_enabled` usage in `devture_systemd_service_manager_services_list_auto` Fixup for 1b05343aba19852d627ded4934c0580960aaadb9 --- group_vars/matrix_servers | 2 -- 1 file changed, 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 6f1b45607..7031927ee 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -407,8 +407,6 @@ devture_systemd_service_manager_services_list_auto: | + ([{'name': 'matrix-dynamic-dns.service', 'priority': 5000, 'groups': ['matrix', 'dynamic-dns']}] if matrix_dynamic_dns_enabled else []) + - ([{'name': 'matrix-email2matrix.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'email2matrix']}] if matrix_email2matrix_enabled else []) - + ([{'name': (etherpad_identifier + '.service'), 'priority': 4000, 'groups': ['matrix', 'etherpad']}] if etherpad_enabled else []) + ([{'name': (grafana_identifier + '.service'), 'priority': 4000, 'groups': ['matrix', 'monitoring', 'grafana']}] if grafana_enabled else []) From ed62ce70f019b06b4a4a0202dc018c09cd9b1703 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 15:35:13 +0900 Subject: [PATCH 748/952] Update docs: edit titles of the removed components This commit updates titles of the docs for removed components, following 0bc4ef8f4d6611f4b18a94d0b4439f69922a8279. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-hangouts.md | 2 +- docs/configuring-playbook-email2matrix.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md index 737a90f26..9fd04d444 100644 --- a/docs/configuring-playbook-bridge-mautrix-hangouts.md +++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md @@ -8,7 +8,7 @@ SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> -# Setting up Mautrix Hangouts bridging (optional, deprecated) +# Setting up Mautrix Hangouts bridging (optional, removed) 🪦 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. diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md index 4044ec565..e3544ff85 100644 --- a/docs/configuring-playbook-email2matrix.md +++ b/docs/configuring-playbook-email2matrix.md @@ -1,5 +1,5 @@ -# Setting up Email2Matrix (optional, deprecated) +# Setting up Email2Matrix (optional, removed) 🪦 The playbook used to be able to install and configure [Email2Matrix](https://github.com/devture/email2matrix), but no longer includes this component. From baefcd4923dfe2b14aeea8984bd0d144b03464c8 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 26 Feb 2025 06:46:20 +0000 Subject: [PATCH 749/952] Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2025.2.26 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index 8dcd3a8f0..6209fe1b3 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -6,7 +6,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2025.2.19 +matrix_alertmanager_receiver_version: 2025.2.26 matrix_alertmanager_receiver_scheme: https From 68e9dc85e9d492764879d23db276771f8b0c8373 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 15:52:33 +0900 Subject: [PATCH 750/952] Add license information to files for matrix-bot-matrix-reminder-bot This commit adds copyright attributions in SPDX to the files for matrix-reminder-bot, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-matrix-reminder-bot.md | 8 ++++++++ .../matrix-bot-matrix-reminder-bot/defaults/main.yml | 10 ++++++++++ .../matrix-bot-matrix-reminder-bot/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../matrix-bot-matrix-reminder-bot.service.j2.license | 4 ++++ 8 files changed, 54 insertions(+) create mode 100644 roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2.license diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md index ad81b0f70..9661ed6fa 100644 --- a/docs/configuring-playbook-bot-matrix-reminder-bot.md +++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md @@ -1,3 +1,11 @@ + + # Setting up matrix-reminder-bot (optional) The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you. diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml index 69d27307e..bf4176b1a 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Richard Meyer +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-reminder-bot is a bot for one-off and recurring reminders # Project source code URL: https://github.com/anoadragon453/matrix-reminder-bot diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/main.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/main.yml index f475afc06..aaef35450 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/main.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml index 4db0372f9..e8442c0b9 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_uninstall.yml index 512c0f2dd..55d89ffbf 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-matrix-reminder-bot service diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml index 96bab685f..68925dc4f 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-reminder-bot settings not defined diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2.license b/roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2.license new file mode 100644 index 000000000..89e5ea1b7 --- /dev/null +++ b/roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2.license b/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2.license new file mode 100644 index 000000000..ba251d31b --- /dev/null +++ b/roles/custom/matrix-bot-matrix-reminder-bot/templates/systemd/matrix-bot-matrix-reminder-bot.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From b0d53d1b53184c1b09407f3766c80bc5ed760840 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 15:52:43 +0900 Subject: [PATCH 751/952] Add license information to files for matrix-bridge-go-skype-bridge This commit adds copyright attributions in SPDX to the files for go-skype-bridge, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-go-skype-bridge.md | 7 +++++++ .../matrix-bridge-go-skype-bridge/defaults/main.yml | 10 ++++++++++ .../matrix-bridge-go-skype-bridge/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 7 +++++++ .../tasks/setup_uninstall.yml | 5 +++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 6 ++++++ .../systemd/matrix-go-skype-bridge.service.j2.license | 4 ++++ 8 files changed, 49 insertions(+) create mode 100644 roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md index 22ec97905..c90d120cc 100644 --- a/docs/configuring-playbook-bridge-go-skype-bridge.md +++ b/docs/configuring-playbook-bridge-go-skype-bridge.md @@ -1,3 +1,10 @@ + + # Setting up Go Skype Bridge bridging (optional) The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you, 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. diff --git a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml index a162a5848..a27f22905 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2022 - 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Arthur Brugière +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Go Skype Bridge is a Matrix <-> Skype bridge # Project source code URL: https://github.com/kelaresg/go-skype-bridge diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml index 7ba914213..18b488a44 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml index 9d5bed211..1f142759f 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml index d7b5999a1..6215ac8b5 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-go-skype-bridge service diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml index 7c3f00a18..12f4172af 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required go-skype-bridge settings not defined diff --git a/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license new file mode 100644 index 000000000..227ac864a --- /dev/null +++ b/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2022 Vladimir Panteleev +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license new file mode 100644 index 000000000..6ef6a26f8 --- /dev/null +++ b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Vladimir Panteleev +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 6acf82a3efac5a81221b4016b423dcfd63801c85 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 15:52:54 +0900 Subject: [PATCH 752/952] Add license information to files for matrix-prometheus-nginxlog-exporter This commit adds copyright attributions in SPDX to the files for prometheus-nginxlog-exporter, following REUSE's specification. Signed-off-by: Suguru Hirahara --- .../matrix-prometheus-nginxlog-exporter/defaults/main.yml | 7 +++++++ .../examples/grafana.png.license | 3 +++ .../examples/metrics.png.license | 3 +++ .../matrix-prometheus-nginxlog-exporter/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 6 ++++++ .../tasks/setup_uninstall.yml | 5 +++++ .../tasks/validate_config.yml | 5 +++++ .../templates/grafana/nginx-proxy.json.license | 3 +++ .../templates/labels.j2 | 6 ++++++ .../templates/nginx-proxy.json.license | 3 +++ .../templates/prometheus-nginxlog-exporter.yaml.j2 | 7 +++++++ .../matrix-prometheus-nginxlog-exporter.service.j2.license | 4 ++++ 12 files changed, 57 insertions(+) create mode 100644 roles/custom/matrix-prometheus-nginxlog-exporter/examples/grafana.png.license create mode 100644 roles/custom/matrix-prometheus-nginxlog-exporter/examples/metrics.png.license create mode 100644 roles/custom/matrix-prometheus-nginxlog-exporter/templates/grafana/nginx-proxy.json.license create mode 100644 roles/custom/matrix-prometheus-nginxlog-exporter/templates/nginx-proxy.json.license create mode 100644 roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2.license diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml index d02bdcb43..3cbed7a22 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # prometheus-nginxlog-exporter exports nginx logs in a prometheus usable format on a `/metrics/ endpoint # See: https://github.com/martin-helmich/prometheus-nginxlog-exporter/ diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/examples/grafana.png.license b/roles/custom/matrix-prometheus-nginxlog-exporter/examples/grafana.png.license new file mode 100644 index 000000000..bf4d752e6 --- /dev/null +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/examples/grafana.png.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/examples/metrics.png.license b/roles/custom/matrix-prometheus-nginxlog-exporter/examples/metrics.png.license new file mode 100644 index 000000000..bf4d752e6 --- /dev/null +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/examples/metrics.png.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/main.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/main.yml index 124bb61d9..5b2ea34b3 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/main.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_install.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_install.yml index f7a0ee213..702c65e3a 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_install.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-prometheus-nginxlog-exporter image is pulled diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_uninstall.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_uninstall.yml index 8828f4ecb..9b1e5035e 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-prometheus-nginxlog-exporter service diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml index 1978ed6ed..9e20017f9 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed prometheus-nginxlog-exporter settings diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/grafana/nginx-proxy.json.license b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/grafana/nginx-proxy.json.license new file mode 100644 index 000000000..9c2c35bce --- /dev/null +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/grafana/nginx-proxy.json.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2023 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/labels.j2 b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/labels.j2 index e5aa3c620..7aa35d9c6 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/labels.j2 +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_prometheus_nginxlog_exporter_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/nginx-proxy.json.license b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/nginx-proxy.json.license new file mode 100644 index 000000000..bf4d752e6 --- /dev/null +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/nginx-proxy.json.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/prometheus-nginxlog-exporter.yaml.j2 b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/prometheus-nginxlog-exporter.yaml.j2 index 2816ec087..b4c9b94b6 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/prometheus-nginxlog-exporter.yaml.j2 +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/prometheus-nginxlog-exporter.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + listen: port: {{ matrix_prometheus_nginxlog_exporter_container_metrics_port }} address: "0.0.0.0" diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2.license b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2.license new file mode 100644 index 000000000..fcdcd2e0e --- /dev/null +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/templates/systemd/matrix-prometheus-nginxlog-exporter.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 59b40fb28e910acc33f99eb04d458e35de3474d0 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 09:00:44 +0200 Subject: [PATCH 753/952] Upgrade Grafana (v11.5.2-1 -> v11.5.2-2) Ref: https://github.com/mother-of-all-self-hosting/ansible-role-grafana/issues/4 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 207ff01e9..389df2513 100644 --- a/requirements.yml +++ b/requirements.yml @@ -22,7 +22,7 @@ version: v4.98.1-r0-0-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git - version: v11.5.2-1 + version: v11.5.2-2 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git version: v10008-3 From ba3b82ed20aeb67a4b920a062a8abc3137ae8f25 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 09:37:05 +0200 Subject: [PATCH 754/952] Switch to pulling Element Web from Github Container Registry, not Docker Hub --- roles/custom/matrix-client-element/defaults/main.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 655a020a8..cba52d7aa 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -10,13 +10,13 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme # - https://github.com/element-hq/element-web/issues/19544 matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" -# renovate: datasource=docker depName=vectorim/element-web +# renovate: datasource=docker depName=ghcr.io/element-hq/element-web matrix_client_element_version: v1.11.93 -matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}vectorim/element-web:{{ matrix_client_element_version }}" +matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}element-hq/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" matrix_client_element_docker_image_registry_prefix_upstream: "{{ matrix_client_element_docker_image_registry_prefix_upstream_default }}" -matrix_client_element_docker_image_registry_prefix_upstream_default: docker.io/ +matrix_client_element_docker_image_registry_prefix_upstream_default: ghcr.io/ matrix_client_element_docker_image_force_pull: "{{ matrix_client_element_docker_image.endswith(':latest') }}" matrix_client_element_data_path: "{{ matrix_base_data_path }}/client-element" From ff031dfd96ceaa43f15c34d2184076ea3c6b16ec Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 22:50:04 +0900 Subject: [PATCH 755/952] Update ansible-lint.yml: add the license information Signed-off-by: Suguru Hirahara --- .config/ansible-lint.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.config/ansible-lint.yml b/.config/ansible-lint.yml index 0ff5748cb..16d4cb0fa 100644 --- a/.config/ansible-lint.yml +++ b/.config/ansible-lint.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- use_default_rules: true From 5fa5026d69552162bf850c14edfc2b7faa9bde64 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 26 Feb 2025 22:52:29 +0900 Subject: [PATCH 756/952] Update .github directory: add copyright information - Exclude renovate.json - Rename reuse.toml: capitalization Signed-off-by: Suguru Hirahara --- .github/FUNDING.yml | 5 +++++ .github/ISSUE_TEMPLATE/bug_report.md | 7 +++++++ .github/ISSUE_TEMPLATE/config.yml | 4 ++++ .github/ISSUE_TEMPLATE/feature_request.md | 7 +++++++ .github/ISSUE_TEMPLATE/i-need-help.md | 7 +++++++ .github/dependabot.yaml | 4 ++++ .github/workflows/close-stale-issues.yml | 4 ++++ .github/workflows/matrix.yml | 6 ++++++ reuse.toml => REUSE.toml | 1 + 9 files changed, 45 insertions(+) rename reuse.toml => REUSE.toml (95%) diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml index 463b7cd47..d1e7546da 100644 --- a/.github/FUNDING.yml +++ b/.github/FUNDING.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # These are supported funding model platforms diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 985806d5b..67582267d 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -1,3 +1,10 @@ + + --- name: Bug report about: Create a report to help us improve diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 57488385d..98f6bad20 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- blank_issues_enabled: false contact_links: diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 5746ab313..0b21a2fef 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -1,3 +1,10 @@ + + --- name: Feature request about: Suggest an idea for this project diff --git a/.github/ISSUE_TEMPLATE/i-need-help.md b/.github/ISSUE_TEMPLATE/i-need-help.md index 03632d440..9f76ce259 100644 --- a/.github/ISSUE_TEMPLATE/i-need-help.md +++ b/.github/ISSUE_TEMPLATE/i-need-help.md @@ -1,3 +1,10 @@ + + --- name: I need help about: Get support from our community diff --git a/.github/dependabot.yaml b/.github/dependabot.yaml index b9c3cd49d..dad8d2cf2 100644 --- a/.github/dependabot.yaml +++ b/.github/dependabot.yaml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- version: 2 updates: diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index 4473c589e..13da4f81a 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- name: 'Close stale issues and PRs' on: # yamllint disable-line rule:truthy diff --git a/.github/workflows/matrix.yml b/.github/workflows/matrix.yml index de1455688..0f9abd338 100644 --- a/.github/workflows/matrix.yml +++ b/.github/workflows/matrix.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- name: Matrix CI diff --git a/reuse.toml b/REUSE.toml similarity index 95% rename from reuse.toml rename to REUSE.toml index 77ad4587b..849d77627 100644 --- a/reuse.toml +++ b/REUSE.toml @@ -7,6 +7,7 @@ version = 1 # Computer-generated files and other files which cannot be copyrighted [[annotations]] path = [ + ".github/renovate.json", "i18n/.gitignore", "i18n/requirements.txt", "i18n/PUBLISHED_LANGUAGES" From 8367981bfb075ae42dad0a0cca671e5eb7c10dbb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 01:56:36 +0900 Subject: [PATCH 757/952] Add license information to files for matrix-conduwuit This commit adds copyright attributions in SPDX to the files for matrix-conduwuit, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-conduwuit.md | 7 +++++++ roles/custom/matrix-conduwuit/defaults/main.yml | 5 +++++ roles/custom/matrix-conduwuit/tasks/install.yml | 4 ++++ roles/custom/matrix-conduwuit/tasks/main.yml | 5 +++++ .../matrix-conduwuit/tasks/self_check_client_api.yml | 5 +++++ .../matrix-conduwuit/tasks/self_check_federation_api.yml | 4 ++++ roles/custom/matrix-conduwuit/tasks/setup_install.yml | 4 ++++ roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml | 4 ++++ roles/custom/matrix-conduwuit/tasks/uninstall.yml | 4 ++++ roles/custom/matrix-conduwuit/tasks/validate_config.yml | 4 ++++ roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 | 8 ++++++++ roles/custom/matrix-conduwuit/templates/env.j2.license | 3 +++ roles/custom/matrix-conduwuit/templates/labels.j2 | 8 ++++++++ .../templates/systemd/matrix-conduwuit.service.j2.license | 4 ++++ roles/custom/matrix-conduwuit/vars/main.yml | 5 +++++ 15 files changed, 74 insertions(+) create mode 100644 roles/custom/matrix-conduwuit/templates/env.j2.license create mode 100644 roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2.license diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md index b198dd814..f31d57ab4 100644 --- a/docs/configuring-playbook-conduwuit.md +++ b/docs/configuring-playbook-conduwuit.md @@ -1,3 +1,10 @@ + + # Configuring conduwuit (optional) The playbook can install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you. diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml index ad420f2a4..37db36882 100644 --- a/roles/custom/matrix-conduwuit/defaults/main.yml +++ b/roles/custom/matrix-conduwuit/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # conduwuit is a very cool, featureful fork of conduit (https://gitlab.com/famedly/conduit). # Project source code URL: https://github.com/girlbossceo/conduwuit diff --git a/roles/custom/matrix-conduwuit/tasks/install.yml b/roles/custom/matrix-conduwuit/tasks/install.yml index 91d244c25..aa489386e 100644 --- a/roles/custom/matrix-conduwuit/tasks/install.yml +++ b/roles/custom/matrix-conduwuit/tasks/install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure conduwuit config path exists diff --git a/roles/custom/matrix-conduwuit/tasks/main.yml b/roles/custom/matrix-conduwuit/tasks/main.yml index 68d5daad1..425f81bee 100644 --- a/roles/custom/matrix-conduwuit/tasks/main.yml +++ b/roles/custom/matrix-conduwuit/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml index 19da0161b..5ea3f830f 100644 --- a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml +++ b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Client API diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml index fde73dae0..000a4b608 100644 --- a/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml +++ b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Federation API diff --git a/roles/custom/matrix-conduwuit/tasks/setup_install.yml b/roles/custom/matrix-conduwuit/tasks/setup_install.yml index 02b189986..4a5651fcf 100644 --- a/roles/custom/matrix-conduwuit/tasks/setup_install.yml +++ b/roles/custom/matrix-conduwuit/tasks/setup_install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure conduwuit config path exists diff --git a/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml index dcf802b0a..24326b337 100644 --- a/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-conduwuit service diff --git a/roles/custom/matrix-conduwuit/tasks/uninstall.yml b/roles/custom/matrix-conduwuit/tasks/uninstall.yml index dcf802b0a..9755d5ad1 100644 --- a/roles/custom/matrix-conduwuit/tasks/uninstall.yml +++ b/roles/custom/matrix-conduwuit/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-conduwuit service diff --git a/roles/custom/matrix-conduwuit/tasks/validate_config.yml b/roles/custom/matrix-conduwuit/tasks/validate_config.yml index 26f3ab100..acb95bec1 100644 --- a/roles/custom/matrix-conduwuit/tasks/validate_config.yml +++ b/roles/custom/matrix-conduwuit/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required conduwuit settings not defined diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 index 86c1ac255..0438a2d97 100644 --- a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 +++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2025 MDAD project contributors +SPDX-FileCopyrightText: 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + ### conduwuit Configuration ### See: ### https://conduwuit.puppyirl.gay/configuration.html diff --git a/roles/custom/matrix-conduwuit/templates/env.j2.license b/roles/custom/matrix-conduwuit/templates/env.j2.license new file mode 100644 index 000000000..a149c4232 --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/env.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-conduwuit/templates/labels.j2 b/roles/custom/matrix-conduwuit/templates/labels.j2 index 4a268c366..bcaf3b2dc 100644 --- a/roles/custom/matrix-conduwuit/templates/labels.j2 +++ b/roles/custom/matrix-conduwuit/templates/labels.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2025 MDAD project contributors +SPDX-FileCopyrightText: 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_conduwuit_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2.license b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2.license new file mode 100644 index 000000000..6fe7fc50c --- /dev/null +++ b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2025 MDAD project contributors +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-conduwuit/vars/main.yml b/roles/custom/matrix-conduwuit/vars/main.yml index 02684574c..fa5ec9d6e 100644 --- a/roles/custom/matrix-conduwuit/vars/main.yml +++ b/roles/custom/matrix-conduwuit/vars/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_conduwuit_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}/_matrix/client/versions" From 74aec2f31473dad42548e41a1f1f06030b3d560e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 01:57:07 +0900 Subject: [PATCH 758/952] Add license information to files for matrix-client-fluffychat This commit adds copyright attributions in SPDX to the files for matrix-client-fluffychat, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-fluffychat-web.md | 7 +++++++ roles/custom/matrix-client-fluffychat/defaults/main.yml | 5 +++++ roles/custom/matrix-client-fluffychat/tasks/main.yml | 4 ++++ roles/custom/matrix-client-fluffychat/tasks/self_check.yml | 4 ++++ .../matrix-client-fluffychat/tasks/setup_install.yml | 4 ++++ .../matrix-client-fluffychat/tasks/setup_uninstall.yml | 4 ++++ .../matrix-client-fluffychat/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-client-fluffychat/templates/labels.j2 | 6 ++++++ .../systemd/matrix-client-fluffychat.service.j2.license | 4 ++++ 9 files changed, 43 insertions(+) create mode 100644 roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2.license diff --git a/docs/configuring-playbook-client-fluffychat-web.md b/docs/configuring-playbook-client-fluffychat-web.md index 262c31488..a438c585d 100644 --- a/docs/configuring-playbook-client-fluffychat-web.md +++ b/docs/configuring-playbook-client-fluffychat-web.md @@ -1,3 +1,10 @@ + + # Setting up FluffyChat Web (optional) The playbook can install and configure the [FluffyChat Web](https://github.com/krille-chan/fluffychat) Matrix client for you. diff --git a/roles/custom/matrix-client-fluffychat/defaults/main.yml b/roles/custom/matrix-client-fluffychat/defaults/main.yml index adb72fc94..417911a4c 100644 --- a/roles/custom/matrix-client-fluffychat/defaults/main.yml +++ b/roles/custom/matrix-client-fluffychat/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/krille-chan/fluffychat diff --git a/roles/custom/matrix-client-fluffychat/tasks/main.yml b/roles/custom/matrix-client-fluffychat/tasks/main.yml index 55ca7a933..846913577 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/main.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-client-fluffychat/tasks/self_check.yml b/roles/custom/matrix-client-fluffychat/tasks/self_check.yml index b0dda25c1..12f8bd298 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/self_check.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/self_check.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml b/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml index ca5619b51..a774ad724 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/setup_install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure FluffyChat Web paths exists diff --git a/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml b/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml index 313489bb5..140c95344 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-client-fluffychat.service diff --git a/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml index b42495c53..f5a5ae961 100644 --- a/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml +++ b/roles/custom/matrix-client-fluffychat/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required FluffyChat Web settings not defined diff --git a/roles/custom/matrix-client-fluffychat/templates/labels.j2 b/roles/custom/matrix-client-fluffychat/templates/labels.j2 index 2f1ea5a87..f3527c61a 100644 --- a/roles/custom/matrix-client-fluffychat/templates/labels.j2 +++ b/roles/custom/matrix-client-fluffychat/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2025 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_client_fluffychat_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2.license b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2.license new file mode 100644 index 000000000..a12f6a9f4 --- /dev/null +++ b/roles/custom/matrix-client-fluffychat/templates/systemd/matrix-client-fluffychat.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2025 Nikita Chernyi +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 59890c2805d0604c7246b40749a9e86aa363821d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 02:17:26 +0900 Subject: [PATCH 759/952] Add license information to files for matrix-client-cinny This commit adds copyright attributions in SPDX to the files for matrix-client-cinny, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-cinny.md | 8 ++++++++ roles/custom/matrix-client-cinny/defaults/main.yml | 10 ++++++++++ roles/custom/matrix-client-cinny/tasks/main.yml | 6 ++++++ roles/custom/matrix-client-cinny/tasks/self_check.yml | 6 ++++++ .../custom/matrix-client-cinny/tasks/setup_install.yml | 9 +++++++++ .../matrix-client-cinny/tasks/setup_uninstall.yml | 7 +++++++ .../matrix-client-cinny/tasks/validate_config.yml | 5 +++++ .../templates/config.json.j2.license | 4 ++++ roles/custom/matrix-client-cinny/templates/labels.j2 | 6 ++++++ .../templates/nginx.conf.j2.license | 5 +++++ .../systemd/matrix-client-cinny.service.j2.license | 4 ++++ 11 files changed, 70 insertions(+) create mode 100644 roles/custom/matrix-client-cinny/templates/config.json.j2.license create mode 100644 roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license create mode 100644 roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md index 2ba895eb9..095458c14 100644 --- a/docs/configuring-playbook-client-cinny.md +++ b/docs/configuring-playbook-client-cinny.md @@ -1,3 +1,11 @@ + + # Setting up Cinny (optional) The playbook can install and configure the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you. diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 918740edb..3f103becb 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/ajbura/cinny diff --git a/roles/custom/matrix-client-cinny/tasks/main.yml b/roles/custom/matrix-client-cinny/tasks/main.yml index 40c6514b5..bed3c1803 100644 --- a/roles/custom/matrix-client-cinny/tasks/main.yml +++ b/roles/custom/matrix-client-cinny/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-client-cinny/tasks/self_check.yml b/roles/custom/matrix-client-cinny/tasks/self_check.yml index 8e8634153..6bf0d2187 100644 --- a/roles/custom/matrix-client-cinny/tasks/self_check.yml +++ b/roles/custom/matrix-client-cinny/tasks/self_check.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-client-cinny/tasks/setup_install.yml b/roles/custom/matrix-client-cinny/tasks/setup_install.yml index ab3dcbf64..2c19d421d 100644 --- a/roles/custom/matrix-client-cinny/tasks/setup_install.yml +++ b/roles/custom/matrix-client-cinny/tasks/setup_install.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Cinny paths exists ansible.builtin.file: diff --git a/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml b/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml index a73825623..0474902ba 100644 --- a/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-client-cinny.service ansible.builtin.stat: diff --git a/roles/custom/matrix-client-cinny/tasks/validate_config.yml b/roles/custom/matrix-client-cinny/tasks/validate_config.yml index e9a54ac0a..e267b93fe 100644 --- a/roles/custom/matrix-client-cinny/tasks/validate_config.yml +++ b/roles/custom/matrix-client-cinny/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Cinny settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-client-cinny/templates/config.json.j2.license b/roles/custom/matrix-client-cinny/templates/config.json.j2.license new file mode 100644 index 000000000..33dc112bd --- /dev/null +++ b/roles/custom/matrix-client-cinny/templates/config.json.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/templates/labels.j2 b/roles/custom/matrix-client-cinny/templates/labels.j2 index e18e804c0..17e4057d0 100644 --- a/roles/custom/matrix-client-cinny/templates/labels.j2 +++ b/roles/custom/matrix-client-cinny/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_client_cinny_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license b/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license new file mode 100644 index 000000000..ea80b31e7 --- /dev/null +++ b/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 James Reilly + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license new file mode 100644 index 000000000..69c513d50 --- /dev/null +++ b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From d49e9f81da9c0ed6442f22d7c1fcf5aa9357be3c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 02:17:33 +0900 Subject: [PATCH 760/952] Add license information to files for matrix-cactus-comments and matrix-cactus-comments-client This commit adds copyright attributions in SPDX to the files for matrix-cactus-comments and matrix-cactus-comments-client, following REUSE's specification. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-cactus-comments.md | 9 +++++++++ .../matrix-cactus-comments-client/defaults/main.yml | 5 +++++ .../matrix-cactus-comments-client/tasks/install.yml | 5 +++++ .../custom/matrix-cactus-comments-client/tasks/main.yml | 4 ++++ .../matrix-cactus-comments-client/tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/env.j2.license | 3 +++ .../matrix-cactus-comments-client/templates/labels.j2 | 6 ++++++ .../matrix-cactus-comments-client.service.j2.license | 3 +++ roles/custom/matrix-cactus-comments/defaults/main.yml | 6 ++++++ roles/custom/matrix-cactus-comments/tasks/main.yml | 5 +++++ .../matrix-cactus-comments/tasks/setup_install.yml | 6 ++++++ .../matrix-cactus-comments/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-cactus-comments/tasks/validate_config.yml | 5 +++++ .../templates/cactus_appservice.yaml.j2 | 8 ++++++++ .../matrix-cactus-comments/templates/env.j2.license | 4 ++++ .../systemd/matrix-cactus-comments.service.j2.license | 4 ++++ 17 files changed, 87 insertions(+) create mode 100644 roles/custom/matrix-cactus-comments-client/templates/env.j2.license create mode 100644 roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2.license create mode 100644 roles/custom/matrix-cactus-comments/templates/env.j2.license create mode 100644 roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md index f6b704133..61a8bf0d6 100644 --- a/docs/configuring-playbook-cactus-comments.md +++ b/docs/configuring-playbook-cactus-comments.md @@ -1,3 +1,12 @@ + + # Setting up Cactus Comments (optional) The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you. diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml index 9c5b61a05..4e7a8c751 100644 --- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Cactus Comments is a federated comment system built on Matrix. # This role installs the client assets (JS, CSS files). diff --git a/roles/custom/matrix-cactus-comments-client/tasks/install.yml b/roles/custom/matrix-cactus-comments-client/tasks/install.yml index 16fdde5e2..466a9900e 100644 --- a/roles/custom/matrix-cactus-comments-client/tasks/install.yml +++ b/roles/custom/matrix-cactus-comments-client/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-cactus-comments-client paths exist diff --git a/roles/custom/matrix-cactus-comments-client/tasks/main.yml b/roles/custom/matrix-cactus-comments-client/tasks/main.yml index 9423aada2..7defa906b 100644 --- a/roles/custom/matrix-cactus-comments-client/tasks/main.yml +++ b/roles/custom/matrix-cactus-comments-client/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-cactus-comments-client/tasks/uninstall.yml b/roles/custom/matrix-cactus-comments-client/tasks/uninstall.yml index df6c55324..f38c7658c 100644 --- a/roles/custom/matrix-cactus-comments-client/tasks/uninstall.yml +++ b/roles/custom/matrix-cactus-comments-client/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-cactus-comments-client service diff --git a/roles/custom/matrix-cactus-comments-client/tasks/validate_config.yml b/roles/custom/matrix-cactus-comments-client/tasks/validate_config.yml index c1142ce32..fc3901551 100644 --- a/roles/custom/matrix-cactus-comments-client/tasks/validate_config.yml +++ b/roles/custom/matrix-cactus-comments-client/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-cactus-comments-client settings not defined diff --git a/roles/custom/matrix-cactus-comments-client/templates/env.j2.license b/roles/custom/matrix-cactus-comments-client/templates/env.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-cactus-comments-client/templates/env.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments-client/templates/labels.j2 b/roles/custom/matrix-cactus-comments-client/templates/labels.j2 index 274ba9e07..d5e7291ae 100644 --- a/roles/custom/matrix-cactus-comments-client/templates/labels.j2 +++ b/roles/custom/matrix-cactus-comments-client/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_cactus_comments_client_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2.license b/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-cactus-comments-client/templates/systemd/matrix-cactus-comments-client.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/defaults/main.yml b/roles/custom/matrix-cactus-comments/defaults/main.yml index 4794d1517..6189f9faf 100644 --- a/roles/custom/matrix-cactus-comments/defaults/main.yml +++ b/roles/custom/matrix-cactus-comments/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Cactus Comments is a federated comment system built on Matrix. # This role installs the backend appservice. diff --git a/roles/custom/matrix-cactus-comments/tasks/main.yml b/roles/custom/matrix-cactus-comments/tasks/main.yml index 12ee16717..00f3c4b1f 100644 --- a/roles/custom/matrix-cactus-comments/tasks/main.yml +++ b/roles/custom/matrix-cactus-comments/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-cactus-comments/tasks/setup_install.yml b/roles/custom/matrix-cactus-comments/tasks/setup_install.yml index b79611595..5e6219746 100644 --- a/roles/custom/matrix-cactus-comments/tasks/setup_install.yml +++ b/roles/custom/matrix-cactus-comments/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-cactus-comments paths exist diff --git a/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml b/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml index 833708aa7..451a2db0b 100644 --- a/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-cactus-comments service diff --git a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml index 683b2f0d9..1fccefc47 100644 --- a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml +++ b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed matrix-cactus-comments settings diff --git a/roles/custom/matrix-cactus-comments/templates/cactus_appservice.yaml.j2 b/roles/custom/matrix-cactus-comments/templates/cactus_appservice.yaml.j2 index 007a2e87a..2ecf4d508 100644 --- a/roles/custom/matrix-cactus-comments/templates/cactus_appservice.yaml.j2 +++ b/roles/custom/matrix-cactus-comments/templates/cactus_appservice.yaml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # A unique, user-defined ID of the application service which will never change. id: "Cactus Comments" diff --git a/roles/custom/matrix-cactus-comments/templates/env.j2.license b/roles/custom/matrix-cactus-comments/templates/env.j2.license new file mode 100644 index 000000000..28d697fbe --- /dev/null +++ b/roles/custom/matrix-cactus-comments/templates/env.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license new file mode 100644 index 000000000..c3b55344f --- /dev/null +++ b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 1eea92ba567974f6cd5fcf7b7f86c92a6bb2a8d2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 26 Feb 2025 20:47:32 +0200 Subject: [PATCH 761/952] Add a `matrix_synapse_redis_use_tls` variable Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4113 --- roles/custom/matrix-synapse/defaults/main.yml | 1 + .../templates/synapse/homeserver.yaml.j2 | 15 +++++++++------ 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 0925e2c15..cd9cfa7ea 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -1145,6 +1145,7 @@ matrix_synapse_redis_host: "" matrix_synapse_redis_port: 6379 matrix_synapse_redis_password: "" matrix_synapse_redis_dbid: 0 +matrix_synapse_redis_use_tls: false # Controls whether Synapse starts a replication listener necessary for workers. # diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 index 1a6cb6c41..aecaf0301 100644 --- a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 @@ -2919,20 +2919,23 @@ media_instance_running_background_jobs: {{ matrix_synapse_media_instance_running redis: # Uncomment the below to enable Redis support. # - enabled: {{ matrix_synapse_redis_enabled }} + enabled: {{ matrix_synapse_redis_enabled | to_json }} # Optional host and port to use to connect to redis. Defaults to # localhost and 6379 # - host: {{ matrix_synapse_redis_host }} - port: {{ matrix_synapse_redis_port }} + host: {{ matrix_synapse_redis_host | to_json }} + port: {{ matrix_synapse_redis_port | to_json }} # Optional database ID to connect to. Defaults to 0. - dbid: {{ matrix_synapse_redis_dbid }} + dbid: {{ matrix_synapse_redis_dbid | to_json }} # Optional password if configured on the Redis instance - # - password: {{ matrix_synapse_redis_password }} + {% if matrix_synapse_redis_password %} + password: {{ matrix_synapse_redis_password | to_json }} + {% endif %} + + use_tls: {{ matrix_synapse_redis_use_tls | to_json }} ## Background Updates ## From b92d8517ebdc33384b68f69153aa20782bfd0a84 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 26 Feb 2025 21:38:12 +0000 Subject: [PATCH 762/952] Update dependency setuptools to v75.8.2 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index fc9e436fb..747c42ffa 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.8.1 +setuptools==75.8.2 snowballstemmer==2.2.0 Sphinx==8.2.1 sphinx-intl==2.3.1 From f10f16d9b8599f28804de147029d7250ddbd06d7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 13:31:01 +0900 Subject: [PATCH 763/952] Add copyright header to docs/configuring-captcha.md Signed-off-by: Suguru Hirahara --- docs/configuring-captcha.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-captcha.md b/docs/configuring-captcha.md index a4a16a1dc..0bdd76d50 100644 --- a/docs/configuring-captcha.md +++ b/docs/configuring-captcha.md @@ -1,3 +1,12 @@ + + (Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md)) # Overview From b4ff3a816b6bce873c22cee7a44a13f1e8cdb8d2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:02:52 +0900 Subject: [PATCH 764/952] Add copyright header to docs/configuring-playbook-base-domain-serving.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-base-domain-serving.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/configuring-playbook-base-domain-serving.md b/docs/configuring-playbook-base-domain-serving.md index 3a3335e70..b24ab3d38 100644 --- a/docs/configuring-playbook-base-domain-serving.md +++ b/docs/configuring-playbook-base-domain-serving.md @@ -1,3 +1,10 @@ + + # Serving the base domain (optional) By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection. From 307353742035f8dd06657b1156815063e0e25d56 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:10:48 +0900 Subject: [PATCH 765/952] Add copyright header to docs/configuring-playbook-federation.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-federation.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index e87d10e79..c06928748 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -1,3 +1,11 @@ + + # Controlling Matrix federation (optional) 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. From e19de8aa3f91f387186f00bc193e7c7caf8a6cc0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:10:58 +0900 Subject: [PATCH 766/952] Add copyright header to docs/configuring-playbook-nginx.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-nginx.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/configuring-playbook-nginx.md b/docs/configuring-playbook-nginx.md index 2d3353081..c15ad7f14 100644 --- a/docs/configuring-playbook-nginx.md +++ b/docs/configuring-playbook-nginx.md @@ -1,3 +1,14 @@ + + # Configure Nginx (optional, advanced) Since 2024-01, this playbook no longer uses nginx as its reverse-proxy. From 922236c185c52f6dd94d141bb6e24433d1d6cc05 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:11:42 +0900 Subject: [PATCH 767/952] Add copyright header to docs/configuring-playbook-own-webserver.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-own-webserver.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/configuring-playbook-own-webserver.md b/docs/configuring-playbook-own-webserver.md index e49c454ae..0cac72b64 100644 --- a/docs/configuring-playbook-own-webserver.md +++ b/docs/configuring-playbook-own-webserver.md @@ -1,3 +1,21 @@ + + # Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced) 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. From 1fd9cf0de909e078494ba23b9a8af8365ca01eac Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:11:51 +0900 Subject: [PATCH 768/952] Add copyright header to docs/configuring-playbook-ssl-certificates.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ssl-certificates.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/configuring-playbook-ssl-certificates.md b/docs/configuring-playbook-ssl-certificates.md index 94c4d58c5..50f2fbc2b 100644 --- a/docs/configuring-playbook-ssl-certificates.md +++ b/docs/configuring-playbook-ssl-certificates.md @@ -1,3 +1,14 @@ + + # Adjusting SSL certificate retrieval (optional, advanced) 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) From 86d72d9b60a2328ddda7e741d801ac1e67e666dd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:12:00 +0900 Subject: [PATCH 769/952] Add copyright header to docs/configuring-playbook-telemetry.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-telemetry.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuring-playbook-telemetry.md b/docs/configuring-playbook-telemetry.md index aa26fb734..58e67543a 100644 --- a/docs/configuring-playbook-telemetry.md +++ b/docs/configuring-playbook-telemetry.md @@ -1,3 +1,13 @@ + + # Enabling Telemetry for your Matrix server (optional) By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere. From 032a3fc059ceda2bbbd064fa23cc43f96e8b20bb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:12:13 +0900 Subject: [PATCH 770/952] Add copyright header to docs/configuring-well-known.md Signed-off-by: Suguru Hirahara --- docs/configuring-well-known.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index cd387bc00..ec5ad90ce 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -1,3 +1,16 @@ + + # Configuring Service Discovery via .well-known 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. From 504d0dca9aa8087b01b62c8bfd099c08ec389638 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:12:24 +0900 Subject: [PATCH 771/952] Add copyright header to docs/container-images.md Signed-off-by: Suguru Hirahara --- docs/container-images.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/container-images.md b/docs/container-images.md index fbafe02e0..d9bb657f9 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -1,3 +1,20 @@ + + # Container images used by the playbook This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server. From a717eb1053b2489482e532e32eecb5beff68f464 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:39:19 +0900 Subject: [PATCH 772/952] Add copyright header to docs/howto-server-delegation.md Signed-off-by: Suguru Hirahara --- docs/howto-server-delegation.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index 602fda481..fb6a26f79 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -1,3 +1,15 @@ + + # Server Delegation By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection. From 13aef904a46837ea72ff7c29c742885f28c70e09 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:09 +0900 Subject: [PATCH 773/952] Add copyright header to docs/howto-srv-server-delegation.md Signed-off-by: Suguru Hirahara --- docs/howto-srv-server-delegation.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md index 4512dfca8..7a13ddab4 100644 --- a/docs/howto-srv-server-delegation.md +++ b/docs/howto-srv-server-delegation.md @@ -1,3 +1,11 @@ + + # Server Delegation via a DNS SRV record (advanced) **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. From 3f21b22cd0d2ca6701a4c50111a4cf118c98c5a0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:31 +0900 Subject: [PATCH 774/952] Add copyright header to docs/importing-postgres.md Signed-off-by: Suguru Hirahara --- docs/importing-postgres.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md index 1113caf1e..a27c7d6d5 100644 --- a/docs/importing-postgres.md +++ b/docs/importing-postgres.md @@ -1,3 +1,12 @@ + + # Importing an existing Postgres database from another installation (optional) You can manually import your database from a previous default installation of Synapse. From 275f01419eba438504b7e4e94829c87ffed521cb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:42 +0900 Subject: [PATCH 775/952] Add copyright header to docs/importing-synapse-media-store.md Signed-off-by: Suguru Hirahara --- docs/importing-synapse-media-store.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/importing-synapse-media-store.md b/docs/importing-synapse-media-store.md index 69c8b0ef6..08993f952 100644 --- a/docs/importing-synapse-media-store.md +++ b/docs/importing-synapse-media-store.md @@ -1,3 +1,10 @@ + + # Importing `media_store` data files from an existing Synapse installation (optional) You can manually import your `media_store` files from a previous installation of Synapse. From 3dc46d225b1cf2fde48a15f12ef01736d63f34ee Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:48 +0900 Subject: [PATCH 776/952] Add copyright header to docs/importing-synapse-sqlite.md Signed-off-by: Suguru Hirahara --- docs/importing-synapse-sqlite.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/importing-synapse-sqlite.md b/docs/importing-synapse-sqlite.md index 0fe0ec84e..f3ce1d2f4 100644 --- a/docs/importing-synapse-sqlite.md +++ b/docs/importing-synapse-sqlite.md @@ -1,3 +1,11 @@ + + # Importing an existing SQLite database from another Synapse installation (optional) You can manually import your database from a previous default installation of Synapse. From ea5c0f71e06667837d301a637075020791b8d0ea Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:53 +0900 Subject: [PATCH 777/952] Add copyright header to docs/maintenance-migrating.md Signed-off-by: Suguru Hirahara --- docs/maintenance-migrating.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/maintenance-migrating.md b/docs/maintenance-migrating.md index 2aa2e5a86..2b07201c4 100644 --- a/docs/maintenance-migrating.md +++ b/docs/maintenance-migrating.md @@ -1,3 +1,12 @@ + + # Migrating to new server This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**. From ec7d9898b55e6edbde1978520f02499f94aef930 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:41:58 +0900 Subject: [PATCH 778/952] Add copyright header to docs/maintenance-synapse.md Signed-off-by: Suguru Hirahara --- docs/maintenance-synapse.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md index e7cb17c9d..15b6eb62b 100644 --- a/docs/maintenance-synapse.md +++ b/docs/maintenance-synapse.md @@ -1,3 +1,14 @@ + + # Synapse maintenance This document shows you how to perform various maintenance tasks related to the Synapse chat server. From 24f97e9f546a185196c40f96799bde1acd74c034 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:42:03 +0900 Subject: [PATCH 779/952] Add copyright header to docs/obtaining-access-tokens.md Signed-off-by: Suguru Hirahara --- docs/obtaining-access-tokens.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md index 3466f1a4e..1600e413c 100644 --- a/docs/obtaining-access-tokens.md +++ b/docs/obtaining-access-tokens.md @@ -1,3 +1,12 @@ + + # Obtaining an Access Token When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token. From bcdf1f803c56707c725d9ed0d8a8ea9a9b6a3e28 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:42:08 +0900 Subject: [PATCH 780/952] Add copyright header to docs/quick-start.md Signed-off-by: Suguru Hirahara --- docs/quick-start.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/quick-start.md b/docs/quick-start.md index 21b8515e2..c9513c964 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -1,3 +1,9 @@ + + # Quick start + # Registering users This documentation page tells you how to create user accounts on your Matrix server. From 8a1809463bbcaa4e53ec12a24491d5acad594969 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:42:18 +0900 Subject: [PATCH 782/952] Add copyright header to docs/self-building.md Signed-off-by: Suguru Hirahara --- docs/self-building.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/self-building.md b/docs/self-building.md index d09e587df..d1aa855b7 100644 --- a/docs/self-building.md +++ b/docs/self-building.md @@ -1,3 +1,17 @@ + + # Self-building **Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.** From 38792b924af2053269cd5a043d6d51e4644db468 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 14:42:23 +0900 Subject: [PATCH 783/952] Add copyright header to docs/updating-users-passwords.md Signed-off-by: Suguru Hirahara --- docs/updating-users-passwords.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index 87a844bb8..7a9eade91 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -1,3 +1,15 @@ + + # Updating users passwords ## Option 1 (if you are using the integrated Postgres database): From 2889607941b472adedbb007c4e7307b911339b44 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 18:30:12 +0900 Subject: [PATCH 784/952] Add license information to files for matrix-corporal Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-corporal.md | 8 ++++++++ roles/custom/matrix-corporal/defaults/main.yml | 11 +++++++++++ roles/custom/matrix-corporal/tasks/main.yml | 6 ++++++ roles/custom/matrix-corporal/tasks/self_check.yml | 7 +++++++ roles/custom/matrix-corporal/tasks/setup_install.yml | 11 +++++++++++ .../custom/matrix-corporal/tasks/setup_uninstall.yml | 4 ++++ .../custom/matrix-corporal/tasks/validate_config.yml | 5 +++++ .../matrix-corporal/templates/config.json.j2.license | 4 ++++ roles/custom/matrix-corporal/templates/labels.j2 | 6 ++++++ .../systemd/matrix-corporal.service.j2.license | 6 ++++++ 10 files changed, 68 insertions(+) create mode 100644 roles/custom/matrix-corporal/templates/config.json.j2.license create mode 100644 roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2.license diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md index 946a0209d..34c80fe6b 100644 --- a/docs/configuring-playbook-matrix-corporal.md +++ b/docs/configuring-playbook-matrix-corporal.md @@ -1,3 +1,11 @@ + + # Setting up Matrix Corporal (optional, advanced) > [!WARNING] diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml index 9d55096a9..53151c2b0 100644 --- a/roles/custom/matrix-corporal/defaults/main.yml +++ b/roles/custom/matrix-corporal/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Sylvia van Os +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-corporal is a reconciliator and gateway for a managed Matrix server. # Project source code URL: https://github.com/devture/matrix-corporal diff --git a/roles/custom/matrix-corporal/tasks/main.yml b/roles/custom/matrix-corporal/tasks/main.yml index 54ca8ef78..0af9f70c9 100644 --- a/roles/custom/matrix-corporal/tasks/main.yml +++ b/roles/custom/matrix-corporal/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-corporal/tasks/self_check.yml b/roles/custom/matrix-corporal/tasks/self_check.yml index 0758863f8..262c30bed 100644 --- a/roles/custom/matrix-corporal/tasks/self_check.yml +++ b/roles/custom/matrix-corporal/tasks/self_check.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Corporal HTTP gateway diff --git a/roles/custom/matrix-corporal/tasks/setup_install.yml b/roles/custom/matrix-corporal/tasks/setup_install.yml index a8633ffc9..cdbf3af87 100644 --- a/roles/custom/matrix-corporal/tasks/setup_install.yml +++ b/roles/custom/matrix-corporal/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix Corporal paths exist diff --git a/roles/custom/matrix-corporal/tasks/setup_uninstall.yml b/roles/custom/matrix-corporal/tasks/setup_uninstall.yml index 6c6e8063a..9631e37f3 100644 --- a/roles/custom/matrix-corporal/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-corporal/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-corporal service diff --git a/roles/custom/matrix-corporal/tasks/validate_config.yml b/roles/custom/matrix-corporal/tasks/validate_config.yml index b6f857e62..57938ac91 100644 --- a/roles/custom/matrix-corporal/tasks/validate_config.yml +++ b/roles/custom/matrix-corporal/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-corporal settings not defined diff --git a/roles/custom/matrix-corporal/templates/config.json.j2.license b/roles/custom/matrix-corporal/templates/config.json.j2.license new file mode 100644 index 000000000..e2fc3ce69 --- /dev/null +++ b/roles/custom/matrix-corporal/templates/config.json.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-corporal/templates/labels.j2 b/roles/custom/matrix-corporal/templates/labels.j2 index e28fd7761..9c068309b 100644 --- a/roles/custom/matrix-corporal/templates/labels.j2 +++ b/roles/custom/matrix-corporal/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_corporal_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2.license b/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2.license new file mode 100644 index 000000000..8d7f54f75 --- /dev/null +++ b/roles/custom/matrix-corporal/templates/systemd/matrix-corporal.service.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2020 Chris van Dijk + +SPDX-License-Identifier: AGPL-3.0-or-later From 4a92cc11d06d8ed41cb92964ffab60d12f8d3653 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 18:31:49 +0900 Subject: [PATCH 785/952] Add license information to files for matrix-rageshake Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-rageshake.md | 7 +++++++ roles/custom/matrix-rageshake/defaults/main.yml | 7 +++++++ roles/custom/matrix-rageshake/tasks/install.yml | 7 +++++++ roles/custom/matrix-rageshake/tasks/main.yml | 5 +++++ roles/custom/matrix-rageshake/tasks/uninstall.yml | 5 +++++ roles/custom/matrix-rageshake/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-rageshake/templates/config.yaml.j2 | 7 +++++++ roles/custom/matrix-rageshake/templates/labels.j2 | 6 ++++++ .../templates/systemd/matrix-rageshake.service.j2.license | 5 +++++ 9 files changed, 54 insertions(+) create mode 100644 roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md index e52c8cdef..14343f525 100644 --- a/docs/configuring-playbook-rageshake.md +++ b/docs/configuring-playbook-rageshake.md @@ -1,3 +1,10 @@ + + # Setting up the rageshake bug report server (optional) The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you. diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index 3b16546d2..14092cde2 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # rageshake is a bug report collection service diff --git a/roles/custom/matrix-rageshake/tasks/install.yml b/roles/custom/matrix-rageshake/tasks/install.yml index 33953de5e..bcba5ee4f 100644 --- a/roles/custom/matrix-rageshake/tasks/install.yml +++ b/roles/custom/matrix-rageshake/tasks/install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 - 2024 lavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure rageshake paths exist diff --git a/roles/custom/matrix-rageshake/tasks/main.yml b/roles/custom/matrix-rageshake/tasks/main.yml index a211296d0..d314be440 100644 --- a/roles/custom/matrix-rageshake/tasks/main.yml +++ b/roles/custom/matrix-rageshake/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-rageshake/tasks/uninstall.yml b/roles/custom/matrix-rageshake/tasks/uninstall.yml index 8f04d9894..d0f0c8a47 100644 --- a/roles/custom/matrix-rageshake/tasks/uninstall.yml +++ b/roles/custom/matrix-rageshake/tasks/uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-rageshake service diff --git a/roles/custom/matrix-rageshake/tasks/validate_config.yml b/roles/custom/matrix-rageshake/tasks/validate_config.yml index 7ebb2b6b0..e8b40c459 100644 --- a/roles/custom/matrix-rageshake/tasks/validate_config.yml +++ b/roles/custom/matrix-rageshake/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required rageshake settings not defined diff --git a/roles/custom/matrix-rageshake/templates/config.yaml.j2 b/roles/custom/matrix-rageshake/templates/config.yaml.j2 index 6790f2938..a616c5629 100644 --- a/roles/custom/matrix-rageshake/templates/config.yaml.j2 +++ b/roles/custom/matrix-rageshake/templates/config.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # Default configuration for rageshake. # To extend it, use `matrix_rageshake_configuration_extension_yaml`. diff --git a/roles/custom/matrix-rageshake/templates/labels.j2 b/roles/custom/matrix-rageshake/templates/labels.j2 index 626c2fb7c..f5db88f0d 100644 --- a/roles/custom/matrix-rageshake/templates/labels.j2 +++ b/roles/custom/matrix-rageshake/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_rageshake_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license new file mode 100644 index 000000000..0c2880506 --- /dev/null +++ b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2023 Benjamin Kampmann +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 181d393254b61bff1004f2fe01c3915e631f4452 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 18:32:00 +0900 Subject: [PATCH 786/952] Add license information to files for matrix-pantalaimon Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-pantalaimon.md | 7 +++++++ roles/custom/matrix-pantalaimon/defaults/main.yml | 5 +++++ roles/custom/matrix-pantalaimon/tasks/install.yml | 5 +++++ roles/custom/matrix-pantalaimon/tasks/main.yml | 4 ++++ roles/custom/matrix-pantalaimon/tasks/uninstall.yml | 4 ++++ roles/custom/matrix-pantalaimon/tasks/validate_config.yml | 4 ++++ .../matrix-pantalaimon/templates/pantalaimon.conf.j2 | 6 ++++++ .../systemd/matrix-pantalaimon.service.j2.license | 3 +++ 8 files changed, 38 insertions(+) create mode 100644 roles/custom/matrix-pantalaimon/templates/systemd/matrix-pantalaimon.service.j2.license diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md index 4341a07f4..d19f18024 100644 --- a/docs/configuring-playbook-pantalaimon.md +++ b/docs/configuring-playbook-pantalaimon.md @@ -1,3 +1,10 @@ + + # Setting up Pantalaimon (E2EE aware proxy daemon) (optional) The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. diff --git a/roles/custom/matrix-pantalaimon/defaults/main.yml b/roles/custom/matrix-pantalaimon/defaults/main.yml index 28b727b93..1302c60f7 100644 --- a/roles/custom/matrix-pantalaimon/defaults/main.yml +++ b/roles/custom/matrix-pantalaimon/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # E2EE aware proxy daemon for Matrix clients. # Project source code URL: https://github.com/matrix-org/pantalaimon diff --git a/roles/custom/matrix-pantalaimon/tasks/install.yml b/roles/custom/matrix-pantalaimon/tasks/install.yml index 88417681a..4bd4283f7 100644 --- a/roles/custom/matrix-pantalaimon/tasks/install.yml +++ b/roles/custom/matrix-pantalaimon/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-pantalaimon paths exist diff --git a/roles/custom/matrix-pantalaimon/tasks/main.yml b/roles/custom/matrix-pantalaimon/tasks/main.yml index 63cdef198..b3b670eb1 100644 --- a/roles/custom/matrix-pantalaimon/tasks/main.yml +++ b/roles/custom/matrix-pantalaimon/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-pantalaimon/tasks/uninstall.yml b/roles/custom/matrix-pantalaimon/tasks/uninstall.yml index a6c7cd5f6..eb6165405 100644 --- a/roles/custom/matrix-pantalaimon/tasks/uninstall.yml +++ b/roles/custom/matrix-pantalaimon/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-pantalaimon service diff --git a/roles/custom/matrix-pantalaimon/tasks/validate_config.yml b/roles/custom/matrix-pantalaimon/tasks/validate_config.yml index 6fc490ef1..ff3116355 100644 --- a/roles/custom/matrix-pantalaimon/tasks/validate_config.yml +++ b/roles/custom/matrix-pantalaimon/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Pantalaimon variables are undefined diff --git a/roles/custom/matrix-pantalaimon/templates/pantalaimon.conf.j2 b/roles/custom/matrix-pantalaimon/templates/pantalaimon.conf.j2 index 9e8f6fd97..4cd01c478 100644 --- a/roles/custom/matrix-pantalaimon/templates/pantalaimon.conf.j2 +++ b/roles/custom/matrix-pantalaimon/templates/pantalaimon.conf.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + [Default] LogLevel = {{ matrix_pantalaimon_log_level }} diff --git a/roles/custom/matrix-pantalaimon/templates/systemd/matrix-pantalaimon.service.j2.license b/roles/custom/matrix-pantalaimon/templates/systemd/matrix-pantalaimon.service.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-pantalaimon/templates/systemd/matrix-pantalaimon.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 9bb3d2457ca380b258027822095bd22a46a9f2f2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 27 Feb 2025 18:32:26 +0900 Subject: [PATCH 787/952] Add license information to files for matrix-sygnal Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-sygnal.md | 7 +++++++ roles/custom/matrix-sygnal/defaults/main.yml | 9 +++++++++ roles/custom/matrix-sygnal/tasks/install.yml | 9 +++++++++ roles/custom/matrix-sygnal/tasks/main.yml | 5 +++++ roles/custom/matrix-sygnal/tasks/uninstall.yml | 4 ++++ roles/custom/matrix-sygnal/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-sygnal/templates/config.yaml.j2 | 7 +++++++ roles/custom/matrix-sygnal/templates/labels.j2 | 6 ++++++ .../templates/systemd/matrix-sygnal.service.j2.license | 3 +++ 9 files changed, 55 insertions(+) create mode 100644 roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2.license diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md index 9db6ee290..2bd800cdd 100644 --- a/docs/configuring-playbook-sygnal.md +++ b/docs/configuring-playbook-sygnal.md @@ -1,3 +1,10 @@ + + # Setting up the Sygnal push gateway (optional) The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you. diff --git a/roles/custom/matrix-sygnal/defaults/main.yml b/roles/custom/matrix-sygnal/defaults/main.yml index ecce0f518..540dece4e 100644 --- a/roles/custom/matrix-sygnal/defaults/main.yml +++ b/roles/custom/matrix-sygnal/defaults/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Sygnal is a reference Push Gateway for Matrix. diff --git a/roles/custom/matrix-sygnal/tasks/install.yml b/roles/custom/matrix-sygnal/tasks/install.yml index 7ac656819..af6b88fe9 100644 --- a/roles/custom/matrix-sygnal/tasks/install.yml +++ b/roles/custom/matrix-sygnal/tasks/install.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Sygnal paths exists diff --git a/roles/custom/matrix-sygnal/tasks/main.yml b/roles/custom/matrix-sygnal/tasks/main.yml index a586cbd02..c194a800f 100644 --- a/roles/custom/matrix-sygnal/tasks/main.yml +++ b/roles/custom/matrix-sygnal/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-sygnal/tasks/uninstall.yml b/roles/custom/matrix-sygnal/tasks/uninstall.yml index 5f01daf1f..cc67c59fd 100644 --- a/roles/custom/matrix-sygnal/tasks/uninstall.yml +++ b/roles/custom/matrix-sygnal/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-sygnal service diff --git a/roles/custom/matrix-sygnal/tasks/validate_config.yml b/roles/custom/matrix-sygnal/tasks/validate_config.yml index 1cdf20381..dfb806a18 100644 --- a/roles/custom/matrix-sygnal/tasks/validate_config.yml +++ b/roles/custom/matrix-sygnal/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Sygnal settings not defined diff --git a/roles/custom/matrix-sygnal/templates/config.yaml.j2 b/roles/custom/matrix-sygnal/templates/config.yaml.j2 index bb81ea9a4..aba36a9dd 100644 --- a/roles/custom/matrix-sygnal/templates/config.yaml.j2 +++ b/roles/custom/matrix-sygnal/templates/config.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + ## # This is a configuration for Sygnal, the reference Push Gateway for Matrix # See: matrix.org diff --git a/roles/custom/matrix-sygnal/templates/labels.j2 b/roles/custom/matrix-sygnal/templates/labels.j2 index 3ef6731c3..83a415752 100644 --- a/roles/custom/matrix-sygnal/templates/labels.j2 +++ b/roles/custom/matrix-sygnal/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_sygnal_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2.license b/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2.license new file mode 100644 index 000000000..0e5f722c4 --- /dev/null +++ b/roles/custom/matrix-sygnal/templates/systemd/matrix-sygnal.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From f7d25a36912344aad0173b9b36d3208d993e4368 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 27 Feb 2025 11:49:03 +0200 Subject: [PATCH 788/952] Upgrade baibot (v1.4.1 -> v1.5.0) and adapt configuration --- roles/custom/matrix-bot-baibot/defaults/main.yml | 7 ++++++- roles/custom/matrix-bot-baibot/templates/config.yaml.j2 | 4 ++++ .../templates/provider/openai-config.yml.j2 | 3 +++ 3 files changed, 13 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index 41576a01b..434352b2c 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -11,7 +11,7 @@ matrix_bot_baibot_container_repo_version: "{{ 'main' if matrix_bot_baibot_versio matrix_bot_baibot_container_src_files_path: "{{ matrix_base_data_path }}/baibot/container-src" # renovate: datasource=docker depName=ghcr.io/etkecc/baibot -matrix_bot_baibot_version: v1.4.1 +matrix_bot_baibot_version: v1.5.0 matrix_bot_baibot_container_image: "{{ matrix_bot_baibot_container_image_registry_prefix }}etkecc/baibot:{{ matrix_bot_baibot_version }}" matrix_bot_baibot_container_image_registry_prefix: "{{ 'localhost/' if matrix_bot_baibot_container_image_self_build else matrix_bot_baibot_container_image_registry_prefix_upstream }}" matrix_bot_baibot_container_image_registry_prefix_upstream: "{{ matrix_bot_baibot_container_image_registry_prefix_upstream_default }}" @@ -89,6 +89,10 @@ matrix_bot_baibot_config_user_encryption_recovery_reset_allowed: false # If you leave this empty, the bot will use the default (!bai). matrix_bot_baibot_config_command_prefix: "!bai" +# Controls the `room.post_join_self_introduction_enabled` configuration setting. +# Influences whether the bot should send an introduction message after joining a room. +matrix_bot_baibot_config_room_post_join_self_introduction_enabled: true + # Controls the `access.admin_patterns` configuration setting. # A space-separated list of MXID patterns which specify who is an admin. # @@ -366,6 +370,7 @@ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation # See: https://blogs.novita.ai/what-are-large-language-model-settings-temperature-top-p-and-max-tokens/#what-is-llm-temperature matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_temperature: 1.0 matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_response_tokens: 16384 +matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_completion_tokens: ~ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_context_tokens: 128000 matrix_bot_baibot_config_agents_static_definitions_openai_config_speech_to_text_enabled: true diff --git a/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 b/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 index d7e3a4771..af9e2b3fc 100644 --- a/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 +++ b/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 @@ -35,6 +35,10 @@ user: # Command prefix. Leave empty to use the default (!bai). command_prefix: {{ matrix_bot_baibot_config_command_prefix | to_json }} +room: + # Whether the bot should send an introduction message after joining a room. + post_join_self_introduction_enabled: {{ matrix_bot_baibot_config_room_post_join_self_introduction_enabled | to_json }} + access: # Space-separated list of MXID patterns which specify who is an admin. admin_patterns: {{ matrix_bot_baibot_config_access_admin_patterns | to_json }} diff --git a/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 index c239e6d4a..aada4234e 100644 --- a/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 +++ b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2 @@ -11,6 +11,9 @@ text_generation: {% if matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_response_tokens %} max_response_tokens: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_response_tokens | int | to_json }} {% endif %} + {% if matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_completion_tokens %} + max_completion_tokens: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_completion_tokens | int | to_json }} + {% endif %} max_context_tokens: {{ matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_max_context_tokens | int | to_json }} {% endif %} From 032d4f975d84b6495622ebcaad73c1b84bc21466 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 27 Feb 2025 11:49:25 +0200 Subject: [PATCH 789/952] Update default Anthropic text-generation model (`claude-3-5-sonnet-20240620` -> `claude-3-7-sonnet-20250219`) The new baibot version (v1.5.0) supports the new Claude Sonnet 3.7 model, which is supposedly improved and priced the same way, so it makes sense to upgrade to it in our static definitions. --- roles/custom/matrix-bot-baibot/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index 434352b2c..c9031a36e 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -199,7 +199,7 @@ matrix_bot_baibot_config_agents_static_definitions_anthropic_config_api_key: "" matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_enabled: true # For valid model choices, see: https://platform.anthropic.com/docs/models -matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_model_id: claude-3-5-sonnet-20240620 +matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_model_id: claude-3-7-sonnet-20250219 # The prompt text to use (can be null or empty to not use a prompt). # See: https://huggingface.co/docs/transformers/en/tasks/prompting matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_prompt: "{{ matrix_bot_baibot_config_agents_static_definitions_prompt }}" From 2319c6e33b6f3dd34b1bcd6e5a1ba8fc083d26f6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 00:03:25 +0900 Subject: [PATCH 790/952] Add license information to files for matrix-alertmanager-receiver Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-alertmanager-receiver.md | 8 ++++++++ .../custom/matrix-alertmanager-receiver/defaults/main.yml | 5 +++++ .../custom/matrix-alertmanager-receiver/tasks/install.yml | 5 +++++ roles/custom/matrix-alertmanager-receiver/tasks/main.yml | 4 ++++ .../matrix-alertmanager-receiver/tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/config.yaml.j2.license | 4 ++++ .../matrix-alertmanager-receiver/templates/labels.j2 | 6 ++++++ .../matrix-alertmanager-receiver.service.j2.license | 3 +++ 9 files changed, 43 insertions(+) create mode 100644 roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2.license diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md index eee2dd0a5..cd43c2c7e 100644 --- a/docs/configuring-playbook-alertmanager-receiver.md +++ b/docs/configuring-playbook-alertmanager-receiver.md @@ -1,3 +1,11 @@ + + # Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional) The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms. diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index 6209fe1b3..1b7763a37 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-alertmanager-receiver is a service which receives webhook payloads from Prometheus' Alertmanager and forwards them to a Matrix room. diff --git a/roles/custom/matrix-alertmanager-receiver/tasks/install.yml b/roles/custom/matrix-alertmanager-receiver/tasks/install.yml index 50bb44627..a710fcdf3 100644 --- a/roles/custom/matrix-alertmanager-receiver/tasks/install.yml +++ b/roles/custom/matrix-alertmanager-receiver/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-alertmanager-receiver paths exist diff --git a/roles/custom/matrix-alertmanager-receiver/tasks/main.yml b/roles/custom/matrix-alertmanager-receiver/tasks/main.yml index b6ff76aca..ac7500030 100644 --- a/roles/custom/matrix-alertmanager-receiver/tasks/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-alertmanager-receiver/tasks/uninstall.yml b/roles/custom/matrix-alertmanager-receiver/tasks/uninstall.yml index f0a82acbf..71b76298d 100644 --- a/roles/custom/matrix-alertmanager-receiver/tasks/uninstall.yml +++ b/roles/custom/matrix-alertmanager-receiver/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-alertmanager-receiver service diff --git a/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml b/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml index 34878b670..77ecdce2a 100644 --- a/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml +++ b/roles/custom/matrix-alertmanager-receiver/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-alertmanager-receiver settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2.license b/roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2.license new file mode 100644 index 000000000..401253ee1 --- /dev/null +++ b/roles/custom/matrix-alertmanager-receiver/templates/config.yaml.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-alertmanager-receiver/templates/labels.j2 b/roles/custom/matrix-alertmanager-receiver/templates/labels.j2 index 8bf7d22b9..77dc78e8b 100644 --- a/roles/custom/matrix-alertmanager-receiver/templates/labels.j2 +++ b/roles/custom/matrix-alertmanager-receiver/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_alertmanager_receiver_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2.license b/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-alertmanager-receiver/templates/systemd/matrix-alertmanager-receiver.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 195864980b2fdff32c485de0bc0113ed5aa9d793 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 00:03:35 +0900 Subject: [PATCH 791/952] Add license information to files for appservice-double-puppet Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-appservice-double-puppet.md | 7 +++++++ .../matrix-appservice-double-puppet/defaults/main.yml | 4 ++++ .../matrix-appservice-double-puppet/tasks/install.yml | 4 ++++ .../custom/matrix-appservice-double-puppet/tasks/main.yml | 4 ++++ .../matrix-appservice-double-puppet/tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/registration.yaml.j2 | 6 ++++++ 7 files changed, 33 insertions(+) diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index 41967f3fa..d2bac9d42 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -1,3 +1,10 @@ + + # Setting up Appservice Double Puppet (optional) 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. diff --git a/roles/custom/matrix-appservice-double-puppet/defaults/main.yml b/roles/custom/matrix-appservice-double-puppet/defaults/main.yml index a8a0c8e51..33907875d 100644 --- a/roles/custom/matrix-appservice-double-puppet/defaults/main.yml +++ b/roles/custom/matrix-appservice-double-puppet/defaults/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_appservice_double_puppet_enabled: true diff --git a/roles/custom/matrix-appservice-double-puppet/tasks/install.yml b/roles/custom/matrix-appservice-double-puppet/tasks/install.yml index c0818477b..a0a427aae 100644 --- a/roles/custom/matrix-appservice-double-puppet/tasks/install.yml +++ b/roles/custom/matrix-appservice-double-puppet/tasks/install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-appservice-double-puppet paths exist diff --git a/roles/custom/matrix-appservice-double-puppet/tasks/main.yml b/roles/custom/matrix-appservice-double-puppet/tasks/main.yml index c7860d03b..79e61c0eb 100644 --- a/roles/custom/matrix-appservice-double-puppet/tasks/main.yml +++ b/roles/custom/matrix-appservice-double-puppet/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-appservice-double-puppet/tasks/uninstall.yml b/roles/custom/matrix-appservice-double-puppet/tasks/uninstall.yml index cc22920cc..0fd5d561c 100644 --- a/roles/custom/matrix-appservice-double-puppet/tasks/uninstall.yml +++ b/roles/custom/matrix-appservice-double-puppet/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-appservice-double-puppet paths don't exist diff --git a/roles/custom/matrix-appservice-double-puppet/tasks/validate_config.yml b/roles/custom/matrix-appservice-double-puppet/tasks/validate_config.yml index 0151b1db1..abe7b371b 100644 --- a/roles/custom/matrix-appservice-double-puppet/tasks/validate_config.yml +++ b/roles/custom/matrix-appservice-double-puppet/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-appservice-double-puppet settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-appservice-double-puppet/templates/registration.yaml.j2 b/roles/custom/matrix-appservice-double-puppet/templates/registration.yaml.j2 index e3d19ee1f..7702b2585 100644 --- a/roles/custom/matrix-appservice-double-puppet/templates/registration.yaml.j2 +++ b/roles/custom/matrix-appservice-double-puppet/templates/registration.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # The ID doesn't really matter, put whatever you want. id: {{ matrix_appservice_double_puppet_registration_id | to_json }} # The URL is intentionally left empty (null), as the homeserver shouldn't From 57d1f417dfa011bd6c82f0d7450f8928214f6794 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 27 Feb 2025 15:23:27 +0000 Subject: [PATCH 792/952] Update ghcr.io/element-hq/element-web Docker tag to v1.11.94 --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index cba52d7aa..93079df8f 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=ghcr.io/element-hq/element-web -matrix_client_element_version: v1.11.93 +matrix_client_element_version: v1.11.94 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}element-hq/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" From 10fabc32bc7cf7576418ea3e1c9e7f4c55474439 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 27 Feb 2025 18:53:56 +0200 Subject: [PATCH 793/952] Rework `client_body_buffer_size`/`client_max_body_size` and `proxy_max_temp_file_size` configuration for `matrix-synapse-reverse-proxy-companion` Until now, most sections were specifying their own values for these. For `client_max_body_size`, a value of 25MB was hardcoded in most places. This was generally OK, but.. Some sections (those generated by the `render_locations_to_upstream` macro), were not specifying these options and were ending up with a default value for configuration options for `client_max_body_size` (likely 1MB), etc. From now on: - we use individual variables for defining these for the Client-Server and Federation API and apply these once at the `server` level - we keep auto-determining the `client_max_body_size` for the Client-Server API based on `matrix_synapse_max_upload_size_mb` - we keep auto-calculating the `client_max_body_size` for the Federation API based on the one for the Client API, but now also add a "minimum" value (`matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb_minimum: 100`) to ensure we don't go too low Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4100 --- .../defaults/main.yml | 16 ++++++- ...ix-synapse-reverse-proxy-companion.conf.j2 | 46 +++++-------------- 2 files changed, 26 insertions(+), 36 deletions(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 241f0c7e9..051684ef9 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -203,14 +203,26 @@ matrix_synapse_reverse_proxy_companion_hostname: "matrix-synapse-reverse-proxy-c # matrix_synapse_reverse_proxy_companion_client_api_addr specifies the address where the Client-Server API is matrix_synapse_reverse_proxy_companion_client_api_addr: 'matrix-synapse:{{ matrix_synapse_container_client_api_port }}' + +# The maximum body size for client requests to any of the endpoints on the Client-Server API. # This needs to be equal or higher than the maximum upload size accepted by Synapse. -matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb: 50 +matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb: 100 + +# The buffer size for client requests to any of the endpoints on the Client-Server API. +matrix_synapse_reverse_proxy_companion_client_api_client_body_buffer_size_mb: "{{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}" # matrix_synapse_reverse_proxy_companion_federation_api_enabled specifies whether reverse proxying for the Federation (Server-Server) API should be done matrix_synapse_reverse_proxy_companion_federation_api_enabled: true # matrix_synapse_reverse_proxy_companion_federation_api_addr specifies the address where the Federation (Server-Server) API is matrix_synapse_reverse_proxy_companion_federation_api_addr: 'matrix-synapse:{{ matrix_synapse_container_federation_api_plain_port }}' -matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb: "{{ (matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb | int) * 3 }}" + +# The maximum body size for client requests to any of the endpoints on the Federation API. +# We auto-calculate this based on the Client-Server API's maximum body size, but use a minimum value to ensure we don't go to low. +matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb: "{{ [matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb_minimum, (matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb | int) * 3] | max }}" +matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb_minimum: 100 + +# The buffer size for client requests to any of the endpoints on the Federation API. +matrix_synapse_reverse_proxy_companion_federation_api_client_body_buffer_size_mb: "{{ matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb }}" # A list of strings containing additional configuration blocks to add to the nginx vhost handling the Synapse Client-Server API matrix_synapse_reverse_proxy_companion_synapse_client_api_additional_server_configuration_blocks: [] diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 index 5c3560ef3..4d18b380d 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 @@ -91,6 +91,12 @@ server { server_tokens off; root /dev/null; + client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; + client_body_buffer_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_body_buffer_size_mb }}M; + + proxy_buffering on; + proxy_max_temp_file_size 0; + {% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %} # Client-server overrides — These locations must go to the main Synapse process location ~ {{ matrix_synapse_reverse_proxy_companion_client_server_main_override_locations_regex }} { @@ -101,10 +107,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } # Client-server SSO overrides — These locations must go to the main Synapse process @@ -116,10 +118,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } # QR code login (`rendezvous`) locations need to go to the same Synapse process. @@ -133,10 +131,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } {# Workers redirects BEGIN #} @@ -199,12 +193,7 @@ server { proxy_pass http://media_repository_workers_upstream$request_uri; proxy_set_header Host $host; - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; - {% if matrix_synapse_reverse_proxy_companion_synapse_cache_enabled %} - proxy_buffering on; proxy_cache {{ matrix_synapse_reverse_proxy_companion_synapse_cache_keys_zone_name }}; proxy_cache_valid any {{ matrix_synapse_reverse_proxy_companion_synapse_cache_proxy_cache_valid_time }}; proxy_force_ranges on; @@ -233,10 +222,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } } @@ -246,9 +231,14 @@ server { server_name {{ matrix_synapse_reverse_proxy_companion_hostname }}; server_tokens off; - root /dev/null; + client_max_body_size {{ matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb }}M; + client_body_buffer_size {{ matrix_synapse_reverse_proxy_companion_federation_api_client_body_buffer_size_mb }}M; + + proxy_buffering on; + proxy_max_temp_file_size 0; + {% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %} # Federation overrides — These locations must go to the main Synapse process location ~ {{ matrix_synapse_reverse_proxy_companion_federation_override_locations_regex }} { @@ -259,10 +249,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } {% if room_workers | length > 0 %} @@ -282,10 +268,6 @@ server { proxy_pass http://media_repository_workers_upstream$request_uri; proxy_set_header Host $host; - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; - {% if matrix_synapse_reverse_proxy_companion_synapse_cache_enabled %} proxy_buffering on; proxy_cache {{ matrix_synapse_reverse_proxy_companion_synapse_cache_keys_zone_name }}; @@ -323,10 +305,6 @@ server { proxy_pass http://$backend; proxy_set_header Host $host; - - client_body_buffer_size 25M; - client_max_body_size {{ matrix_synapse_reverse_proxy_companion_federation_api_client_max_body_size_mb }}M; - proxy_max_temp_file_size 0; } } {% endif %} From 37f84173f07662aede5004cafa62781e2f040553 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 27 Feb 2025 19:04:26 +0200 Subject: [PATCH 794/952] Put `proxy_set_header Host $host;` at the `server` level for `matrix-synapse-reverse-proxy-companion` Continuation of the refactoring done in 10fabc32bc7cf7576418ea3e1c9e7f4c55474439 --- ...trix-synapse-reverse-proxy-companion.conf.j2 | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 index 4d18b380d..57dee1d9b 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 @@ -29,7 +29,6 @@ {% for location in locations %} location ~ {{ location }} { proxy_pass http://{{ upstream_name }}$request_uri; - proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Connection ""; } @@ -96,6 +95,7 @@ server { proxy_buffering on; proxy_max_temp_file_size 0; + proxy_set_header Host $host; {% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %} # Client-server overrides — These locations must go to the main Synapse process @@ -105,8 +105,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_client_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } # Client-server SSO overrides — These locations must go to the main Synapse process @@ -116,8 +114,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_client_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } # QR code login (`rendezvous`) locations need to go to the same Synapse process. @@ -129,8 +125,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_client_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } {# Workers redirects BEGIN #} @@ -191,7 +185,6 @@ server { {% for location in matrix_synapse_reverse_proxy_companion_synapse_media_repository_locations %} location ~ {{ location }} { proxy_pass http://media_repository_workers_upstream$request_uri; - proxy_set_header Host $host; {% if matrix_synapse_reverse_proxy_companion_synapse_cache_enabled %} proxy_cache {{ matrix_synapse_reverse_proxy_companion_synapse_cache_keys_zone_name }}; @@ -220,8 +213,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_client_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } } @@ -238,6 +229,7 @@ server { proxy_buffering on; proxy_max_temp_file_size 0; + proxy_set_header Host $host; {% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %} # Federation overrides — These locations must go to the main Synapse process @@ -247,8 +239,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_federation_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } {% if room_workers | length > 0 %} @@ -266,7 +256,6 @@ server { {% for location in matrix_synapse_reverse_proxy_companion_synapse_media_repository_locations %} location ~ {{ location }} { proxy_pass http://media_repository_workers_upstream$request_uri; - proxy_set_header Host $host; {% if matrix_synapse_reverse_proxy_companion_synapse_cache_enabled %} proxy_buffering on; @@ -303,8 +292,6 @@ server { resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; set $backend "{{ matrix_synapse_reverse_proxy_companion_federation_api_addr }}"; proxy_pass http://$backend; - - proxy_set_header Host $host; } } {% endif %} From 0a8117d96c50dfd15d13bfe680406aa3706af645 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:06:14 +0900 Subject: [PATCH 795/952] Add license information to files for matrix-bot-baibot Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-baibot.md | 7 +++++++ roles/custom/matrix-bot-baibot/defaults/main.yml | 6 ++++++ roles/custom/matrix-bot-baibot/tasks/install.yml | 5 +++++ roles/custom/matrix-bot-baibot/tasks/main.yml | 4 ++++ roles/custom/matrix-bot-baibot/tasks/uninstall.yml | 4 ++++ roles/custom/matrix-bot-baibot/tasks/validate_config.yml | 4 ++++ roles/custom/matrix-bot-baibot/templates/config.yaml.j2 | 7 +++++++ roles/custom/matrix-bot-baibot/templates/env.j2 | 6 ++++++ .../templates/provider/anthropic-config.yml.j2.license | 3 +++ .../templates/provider/groq-config.yml.j2.license | 3 +++ .../templates/provider/mistral-config.yml.j2.license | 3 +++ .../templates/provider/openai-config.yml.j2.license | 3 +++ .../templates/systemd/matrix-bot-baibot.service.j2.license | 4 ++++ 13 files changed, 59 insertions(+) create mode 100644 roles/custom/matrix-bot-baibot/templates/provider/anthropic-config.yml.j2.license create mode 100644 roles/custom/matrix-bot-baibot/templates/provider/groq-config.yml.j2.license create mode 100644 roles/custom/matrix-bot-baibot/templates/provider/mistral-config.yml.j2.license create mode 100644 roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2.license create mode 100644 roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md index a9c3d2c66..543a23502 100644 --- a/docs/configuring-playbook-bot-baibot.md +++ b/docs/configuring-playbook-bot-baibot.md @@ -1,3 +1,10 @@ + + # Setting up baibot (optional)

diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml index c9031a36e..2ce998d0d 100644 --- a/roles/custom/matrix-bot-baibot/defaults/main.yml +++ b/roles/custom/matrix-bot-baibot/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # baibot is a bot exposing the power of Large Language Models to you. diff --git a/roles/custom/matrix-bot-baibot/tasks/install.yml b/roles/custom/matrix-bot-baibot/tasks/install.yml index 340efdd69..c2d781e59 100644 --- a/roles/custom/matrix-bot-baibot/tasks/install.yml +++ b/roles/custom/matrix-bot-baibot/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure baibot paths exist diff --git a/roles/custom/matrix-bot-baibot/tasks/main.yml b/roles/custom/matrix-bot-baibot/tasks/main.yml index 1b9d9c5b5..348c11d08 100644 --- a/roles/custom/matrix-bot-baibot/tasks/main.yml +++ b/roles/custom/matrix-bot-baibot/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-baibot/tasks/uninstall.yml b/roles/custom/matrix-bot-baibot/tasks/uninstall.yml index 176edaa6a..f9f53f9f7 100644 --- a/roles/custom/matrix-bot-baibot/tasks/uninstall.yml +++ b/roles/custom/matrix-bot-baibot/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-baibot service diff --git a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml index bbf830c1f..6129e3806 100644 --- a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required baibot settings not defined diff --git a/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 b/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 index af9e2b3fc..4b4838192 100644 --- a/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 +++ b/roles/custom/matrix-bot-baibot/templates/config.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # Default configuration for baibot. # To extend it, use `matrix_bot_baibot_configuration_extension_yaml`. diff --git a/roles/custom/matrix-bot-baibot/templates/env.j2 b/roles/custom/matrix-bot-baibot/templates/env.j2 index fb26fe3df..fe4733ab2 100644 --- a/roles/custom/matrix-bot-baibot/templates/env.j2 +++ b/roles/custom/matrix-bot-baibot/templates/env.j2 @@ -1 +1,7 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {{ matrix_bot_baibot_environment_variables_extension }} diff --git a/roles/custom/matrix-bot-baibot/templates/provider/anthropic-config.yml.j2.license b/roles/custom/matrix-bot-baibot/templates/provider/anthropic-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-bot-baibot/templates/provider/anthropic-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-baibot/templates/provider/groq-config.yml.j2.license b/roles/custom/matrix-bot-baibot/templates/provider/groq-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-bot-baibot/templates/provider/groq-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-baibot/templates/provider/mistral-config.yml.j2.license b/roles/custom/matrix-bot-baibot/templates/provider/mistral-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-bot-baibot/templates/provider/mistral-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2.license b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-bot-baibot/templates/provider/openai-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license new file mode 100644 index 000000000..fadc9dc1e --- /dev/null +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2024 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 43199effd52a4e796d0833b703eea69640482ff5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:09:18 +0900 Subject: [PATCH 796/952] Add license information to files for matrix-bot-buscarron Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-buscarron.md | 8 ++++++++ roles/custom/matrix-bot-buscarron/defaults/main.yml | 7 +++++++ roles/custom/matrix-bot-buscarron/tasks/main.yml | 5 +++++ roles/custom/matrix-bot-buscarron/tasks/setup_install.yml | 8 ++++++++ .../custom/matrix-bot-buscarron/tasks/setup_uninstall.yml | 7 +++++++ .../custom/matrix-bot-buscarron/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-bot-buscarron/templates/env.j2 | 7 +++++++ roles/custom/matrix-bot-buscarron/templates/labels.j2 | 7 +++++++ .../systemd/matrix-bot-buscarron.service.j2.license | 4 ++++ 9 files changed, 58 insertions(+) create mode 100644 roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index e2762ed94..45266d338 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -1,3 +1,11 @@ + + # Setting up Buscarron (optional) The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you. diff --git a/roles/custom/matrix-bot-buscarron/defaults/main.yml b/roles/custom/matrix-bot-buscarron/defaults/main.yml index fd2295d84..bf715808c 100644 --- a/roles/custom/matrix-bot-buscarron/defaults/main.yml +++ b/roles/custom/matrix-bot-buscarron/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Buscarron is a Web forms (HTTP POST) to Matrix service. diff --git a/roles/custom/matrix-bot-buscarron/tasks/main.yml b/roles/custom/matrix-bot-buscarron/tasks/main.yml index fbf5c96ac..b90cfaa25 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/main.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml b/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml index a011a016b..35d583f8c 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: matrix_bot_buscarron_requires_restart: false diff --git a/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml index 7a47471ef..5769de2d3 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-buscarron service diff --git a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml index e9014ccea..e07cbffef 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed Buscarron settings ansible.builtin.fail: diff --git a/roles/custom/matrix-bot-buscarron/templates/env.j2 b/roles/custom/matrix-bot-buscarron/templates/env.j2 index 11a4f6bd6..db9b903c4 100644 --- a/roles/custom/matrix-bot-buscarron/templates/env.j2 +++ b/roles/custom/matrix-bot-buscarron/templates/env.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + BUSCARRON_LOGIN={{ matrix_bot_buscarron_login }} BUSCARRON_PASSWORD={{ matrix_bot_buscarron_password }} BUSCARRON_HOMESERVER={{ matrix_bot_buscarron_homeserver }} diff --git a/roles/custom/matrix-bot-buscarron/templates/labels.j2 b/roles/custom/matrix-bot-buscarron/templates/labels.j2 index b5f020a17..a302c5269 100644 --- a/roles/custom/matrix-bot-buscarron/templates/labels.j2 +++ b/roles/custom/matrix-bot-buscarron/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_bot_buscarron_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license new file mode 100644 index 000000000..70a8f1992 --- /dev/null +++ b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From be667ee7839e9175d3e297045e486590bcf206d9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:10:04 +0900 Subject: [PATCH 797/952] Add license information to files for matrix-bot-honoroit Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-honoroit.md | 8 ++++++++ roles/custom/matrix-bot-honoroit/defaults/main.yml | 9 +++++++++ roles/custom/matrix-bot-honoroit/tasks/main.yml | 6 ++++++ .../custom/matrix-bot-honoroit/tasks/setup_install.yml | 10 ++++++++++ .../matrix-bot-honoroit/tasks/setup_uninstall.yml | 8 ++++++++ .../matrix-bot-honoroit/tasks/validate_config.yml | 6 ++++++ roles/custom/matrix-bot-honoroit/templates/env.j2 | 9 +++++++++ roles/custom/matrix-bot-honoroit/templates/labels.j2 | 7 +++++++ .../systemd/matrix-bot-honoroit.service.j2.license | 5 +++++ 9 files changed, 68 insertions(+) create mode 100644 roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2.license diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md index 82e0df2c7..967ea0050 100644 --- a/docs/configuring-playbook-bot-honoroit.md +++ b/docs/configuring-playbook-bot-honoroit.md @@ -1,3 +1,11 @@ + + # Setting up Honoroit (optional) The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you. diff --git a/roles/custom/matrix-bot-honoroit/defaults/main.yml b/roles/custom/matrix-bot-honoroit/defaults/main.yml index dd48cb36f..edac46e0a 100644 --- a/roles/custom/matrix-bot-honoroit/defaults/main.yml +++ b/roles/custom/matrix-bot-honoroit/defaults/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Honoroit is a helpdesk bot # Project source code URL: https://github.com/etkecc/honoroit diff --git a/roles/custom/matrix-bot-honoroit/tasks/main.yml b/roles/custom/matrix-bot-honoroit/tasks/main.yml index 9b4e29089..4e7dfbc09 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/main.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml b/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml index be96d021b..18730e27c 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: matrix_bot_honoroit_requires_restart: false diff --git a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml index 72df4f013..1ab17b516 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-honoroit service diff --git a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml index 95df51dca..a8e2e87af 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Honoroit settings not defined diff --git a/roles/custom/matrix-bot-honoroit/templates/env.j2 b/roles/custom/matrix-bot-honoroit/templates/env.j2 index abbb66f0f..5383b6525 100644 --- a/roles/custom/matrix-bot-honoroit/templates/env.j2 +++ b/roles/custom/matrix-bot-honoroit/templates/env.j2 @@ -1,3 +1,12 @@ +{# +SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + HONOROIT_LOGIN={{ matrix_bot_honoroit_login }} HONOROIT_PASSWORD={{ matrix_bot_honoroit_password }} HONOROIT_HOMESERVER={{ matrix_bot_honoroit_homeserver }} diff --git a/roles/custom/matrix-bot-honoroit/templates/labels.j2 b/roles/custom/matrix-bot-honoroit/templates/labels.j2 index 74e357914..4a027ddad 100644 --- a/roles/custom/matrix-bot-honoroit/templates/labels.j2 +++ b/roles/custom/matrix-bot-honoroit/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_bot_honoroit_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2.license b/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2.license new file mode 100644 index 000000000..09e19b00a --- /dev/null +++ b/roles/custom/matrix-bot-honoroit/templates/systemd/matrix-bot-honoroit.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2023 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later From 1189673e4aa37478e2bdd434dd4d8825bbbdb9fd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:11:02 +0900 Subject: [PATCH 798/952] Add license information to files for matrix-bot-matrix-registration-bot Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bot-matrix-registration-bot.md | 12 ++++++++++++ .../defaults/main.yml | 10 ++++++++++ .../tasks/clean_cache.yml | 4 ++++ .../tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 8 ++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2 | 9 ++++++++- ...ix-bot-matrix-registration-bot.service.j2.license | 6 ++++++ 9 files changed, 64 insertions(+), 1 deletion(-) create mode 100644 roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2.license diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md index 96c9dd54a..c171b733a 100644 --- a/docs/configuring-playbook-bot-matrix-registration-bot.md +++ b/docs/configuring-playbook-bot-matrix-registration-bot.md @@ -1,3 +1,15 @@ + + # Setting up matrix-registration-bot (optional) The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you. diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml index ca438720c..c26848c73 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Erick Wibben +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-registration-bot creates and manages registration tokens for a Matrix server # Project source code URL: https://github.com/moan0s/matrix-registration-bot diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/clean_cache.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/clean_cache.yml index ae4433b8f..d5d590895 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/clean_cache.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/clean_cache.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Julian-Samuel Gebühr +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Delete cache files diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/main.yml index cd11c1d5d..b420f4cde 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/main.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml index a05c04109..c23ce719f 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-registration-bot paths exist diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_uninstall.yml index b83ea783b..662f8e5da 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-matrix-registration-bot service diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml index fb5e7de5c..dfa5c7115 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required settings not defined diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 index 7ea2b9d0a..b76ee9824 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 +++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + bot: server: {{ matrix_bot_matrix_registration_bot_bot_server|to_json }} username: {{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart|to_json }} @@ -13,4 +21,3 @@ api: logging: level: {{ matrix_bot_matrix_registration_bot_logging_level|to_json }} - diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2.license b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2.license new file mode 100644 index 000000000..3a4dec62d --- /dev/null +++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/systemd/matrix-bot-matrix-registration-bot.service.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Erick Wibben +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 7d210cbafdcbc1617f8f16658810bc63c21919c8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:11:30 +0900 Subject: [PATCH 799/952] Add license information to files for matrix-bot-mjolnir Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-mjolnir.md | 11 +++++++++++ roles/custom/matrix-bot-mjolnir/defaults/main.yml | 12 ++++++++++++ roles/custom/matrix-bot-mjolnir/tasks/main.yml | 6 ++++++ .../matrix-bot-mjolnir/tasks/setup_install.yml | 10 ++++++++++ .../matrix-bot-mjolnir/tasks/setup_uninstall.yml | 7 +++++++ .../matrix-bot-mjolnir/tasks/validate_config.yml | 6 ++++++ .../matrix-bot-mjolnir/templates/production.yaml.j2 | 9 +++++++++ .../systemd/matrix-bot-mjolnir.service.j2.license | 5 +++++ 8 files changed, 66 insertions(+) create mode 100644 roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2.license diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md index ec56f345f..9f4a96dfa 100644 --- a/docs/configuring-playbook-bot-mjolnir.md +++ b/docs/configuring-playbook-bot-mjolnir.md @@ -1,3 +1,14 @@ + + # Setting up Mjolnir (optional) The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you. diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml index 25a958631..24f24e573 100644 --- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml +++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Chirayu Desai +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # A moderation tool for Matrix # Project source code URL: https://github.com/matrix-org/mjolnir diff --git a/roles/custom/matrix-bot-mjolnir/tasks/main.yml b/roles/custom/matrix-bot-mjolnir/tasks/main.yml index 03f5ba905..433827c1d 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/main.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-mjolnir/tasks/setup_install.yml b/roles/custom/matrix-bot-mjolnir/tasks/setup_install.yml index 082948344..c533948f4 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bot-mjolnir/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-mjolnir/tasks/setup_uninstall.yml index 06be71e15..08ea3b95f 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-bot-mjolnir service diff --git a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml index 8788609a1..a5de35ead 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-bot-mjolnir variables are undefined diff --git a/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 b/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 index ec2b0ea28..00e7ab7e0 100644 --- a/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 +++ b/roles/custom/matrix-bot-mjolnir/templates/production.yaml.j2 @@ -1,3 +1,12 @@ +{# +SPDX-FileCopyrightText: 2021 Aaron Raimist +SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # Endpoint URL that Mjolnir uses to interact with the Matrix homeserver (client-server API), # set this to the pantalaimon URL if you're using that. homeserverUrl: {{ matrix_bot_mjolnir_homeserver_url | to_json }} diff --git a/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2.license b/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2.license new file mode 100644 index 000000000..4ec9445b4 --- /dev/null +++ b/roles/custom/matrix-bot-mjolnir/templates/systemd/matrix-bot-mjolnir.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 Aaron Raimist + +SPDX-License-Identifier: AGPL-3.0-or-later From 2e54072f1bd2f9b8a7bc1adee3087fe835dd7e9f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 02:47:58 +0900 Subject: [PATCH 800/952] Fix copyright attribution Signed-off-by: Suguru Hirahara --- roles/custom/matrix-appservice-double-puppet/tasks/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-appservice-double-puppet/tasks/main.yml b/roles/custom/matrix-appservice-double-puppet/tasks/main.yml index 79e61c0eb..fda0c1b13 100644 --- a/roles/custom/matrix-appservice-double-puppet/tasks/main.yml +++ b/roles/custom/matrix-appservice-double-puppet/tasks/main.yml @@ -1,4 +1,4 @@ -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later From 6c605a6193a8da5d35c1970026b63533da26cdb5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 14:45:49 +0900 Subject: [PATCH 801/952] Add license information to matrix-appservice-draupnir-for-all Signed-off-by: Suguru Hirahara --- .../matrix-appservice-draupnir-for-all/defaults/main.yml | 6 ++++++ .../matrix-appservice-draupnir-for-all/tasks/main.yml | 4 ++++ .../tasks/setup_install.yml | 7 +++++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../templates/production-appservice.yaml.j2 | 7 +++++++ .../templates/production-bots.yaml.j2 | 6 ++++++ .../matrix-appservice-draupnir-for-all.service.j2.license | 4 ++++ 8 files changed, 43 insertions(+) create mode 100644 roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2.license diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index c7fe4a506..e65ed32e8 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2024 - 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # A moderation tool for Matrix # Project source code URL: https://github.com/the-draupnir-project/Draupnir diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/main.yml index 8048ee95a..5e4af332b 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml index 6dc2bf95e..e4d51b7f7 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_uninstall.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_uninstall.yml index f81cbfef3..da78634d6 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 - 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-draupnir-for-all service diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml index db572635d..a25fb991d 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-bot-draupnir variables are undefined diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-appservice.yaml.j2 b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-appservice.yaml.j2 index e10952ef4..346b57e96 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-appservice.yaml.j2 +++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-appservice.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2024 MDAD project contributors +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + homeserver: # The Matrix server name, this will be the name of the server in your Matrix ID. domain: "{{ matrix_domain }}" diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 index 46a7b4549..de581ed8e 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 +++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # The log level of terminal (or container) output, # can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity. # diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2.license b/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2.license new file mode 100644 index 000000000..c66c5baed --- /dev/null +++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/systemd/matrix-appservice-draupnir-for-all.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2024 MDAD project contributors +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From aac44ad920a03ab74fcfe9637b102003b358d8ce Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 14:46:20 +0900 Subject: [PATCH 802/952] Add license information to matrix-bot-maubot Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bot-maubot.md | 11 +++++++++++ roles/custom/matrix-bot-maubot/defaults/main.yml | 10 ++++++++++ roles/custom/matrix-bot-maubot/tasks/main.yml | 6 ++++++ .../custom/matrix-bot-maubot/tasks/setup_install.yml | 9 +++++++++ .../matrix-bot-maubot/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-bot-maubot/tasks/validate_config.yml | 6 ++++++ .../custom/matrix-bot-maubot/templates/config.yaml.j2 | 9 +++++++++ .../templates/customizations/Dockerfile.j2.license | 3 +++ roles/custom/matrix-bot-maubot/templates/labels.j2 | 6 ++++++ .../systemd/matrix-bot-maubot.service.j2.license | 5 +++++ 10 files changed, 71 insertions(+) create mode 100644 roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2.license create mode 100644 roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2.license diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md index e45ca87db..367a3aaac 100644 --- a/docs/configuring-playbook-bot-maubot.md +++ b/docs/configuring-playbook-bot-maubot.md @@ -1,3 +1,14 @@ + + # Setting up maubot (optional) The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you. diff --git a/roles/custom/matrix-bot-maubot/defaults/main.yml b/roles/custom/matrix-bot-maubot/defaults/main.yml index 976cdc16c..64e717219 100644 --- a/roles/custom/matrix-bot-maubot/defaults/main.yml +++ b/roles/custom/matrix-bot-maubot/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 Stuart Mumford +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 Fabio Bonelli +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # maubot is a plugin-based Matrix bot system. diff --git a/roles/custom/matrix-bot-maubot/tasks/main.yml b/roles/custom/matrix-bot-maubot/tasks/main.yml index d954a452a..b17fe4200 100644 --- a/roles/custom/matrix-bot-maubot/tasks/main.yml +++ b/roles/custom/matrix-bot-maubot/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml index 1c6f17404..973dff0c6 100644 --- a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Stuart Mumford +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure maubot paths exist diff --git a/roles/custom/matrix-bot-maubot/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-maubot/tasks/setup_uninstall.yml index 9d7695763..b5d6c15d6 100644 --- a/roles/custom/matrix-bot-maubot/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-maubot/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-maubot service diff --git a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml index 29409f7b8..6b8be3cce 100644 --- a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed maubot variables diff --git a/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 index 73c75ce58..e5c5be630 100644 --- a/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 +++ b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2 @@ -1,3 +1,12 @@ +{# +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Stuart Mumford +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # The full URI to the database. SQLite and Postgres are fully supported. # Other DBMSes supported by SQLAlchemy may or may not work. # Format examples: diff --git a/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2.license b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-maubot/templates/labels.j2 b/roles/custom/matrix-bot-maubot/templates/labels.j2 index 4c4592e89..e937775d4 100644 --- a/roles/custom/matrix-bot-maubot/templates/labels.j2 +++ b/roles/custom/matrix-bot-maubot/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_bot_maubot_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2.license b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2.license new file mode 100644 index 000000000..c34c637f0 --- /dev/null +++ b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Stuart Mumford + +SPDX-License-Identifier: AGPL-3.0-or-later From 766ad9ebaadffb8a0085e8cb345eb45756acfae1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 14:46:49 +0900 Subject: [PATCH 803/952] Add license information to matrix-bridge-appservice-discord Signed-off-by: Suguru Hirahara --- ...onfiguring-playbook-bridge-appservice-discord.md | 9 +++++++++ .../defaults/main.yml | 13 +++++++++++++ .../matrix-bridge-appservice-discord/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 13 +++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 4 ++++ .../templates/config.yaml.j2.license | 6 ++++++ .../matrix-appservice-discord.service.j2.license | 7 +++++++ 8 files changed, 64 insertions(+) create mode 100644 roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2.license diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md index 6ea6b88db..d4a97a445 100644 --- a/docs/configuring-playbook-bridge-appservice-discord.md +++ b/docs/configuring-playbook-bridge-appservice-discord.md @@ -1,3 +1,12 @@ + + # Setting up Appservice Discord bridging (optional) **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook. diff --git a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml index 8fa789f38..6da159f0d 100644 --- a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Daniel Løvbrøtte Olsen +# SPDX-FileCopyrightText: 2020 John Goerzen +# SPDX-FileCopyrightText: 2021 - 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-appservice-discord is a Matrix <-> Discord bridge # Project source code URL: https://github.com/matrix-org/matrix-appservice-discord diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/main.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/main.yml index 88a772204..617a70849 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/setup_install.yml index f847c743a..0fddef00e 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/setup_install.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2019 - 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/setup_uninstall.yml index ca2354c63..fb164945c 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-discord service diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml index 033a8b337..3d5fec6fe 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required appservice-discord settings not defined diff --git a/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2.license new file mode 100644 index 000000000..9747b420b --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2022 Jim Myhrberg +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2.license b/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2.license new file mode 100644 index 000000000..894501b8a --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-discord/templates/systemd/matrix-appservice-discord.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 MDAD project contributors +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 9ac31fb37c8ff3366c70a5bd4d4ca727fdee01e6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 14:47:01 +0900 Subject: [PATCH 804/952] Add license information to matrix-bridge-appservice-irc Signed-off-by: Suguru Hirahara --- ...figuring-playbook-bridge-appservice-irc.md | 9 ++++++++ .../defaults/main.yml | 21 +++++++++++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/migrate_nedb_to_postgres.yml | 7 +++++++ .../tasks/setup_install.yml | 13 ++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../matrix-appservice-irc.service.j2.license | 7 +++++++ 9 files changed, 79 insertions(+) create mode 100644 roles/custom/matrix-bridge-appservice-irc/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2.license diff --git a/docs/configuring-playbook-bridge-appservice-irc.md b/docs/configuring-playbook-bridge-appservice-irc.md index da655a77b..79cf0aee3 100644 --- a/docs/configuring-playbook-bridge-appservice-irc.md +++ b/docs/configuring-playbook-bridge-appservice-irc.md @@ -1,3 +1,12 @@ + + # Setting up Appservice IRC bridging (optional) **Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook. diff --git a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml index 22f166857..3ce0a176d 100644 --- a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml @@ -1,3 +1,24 @@ +# SPDX-FileCopyrightText: 2019 - 2020 Lee Verberne +# SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Aaron Raimist +# SPDX-FileCopyrightText: 2019 Alexander Acevedo +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Hugues Morisset +# SPDX-FileCopyrightText: 2019 Lyubomir Popov +# SPDX-FileCopyrightText: 2019 Sylvia van Os +# SPDX-FileCopyrightText: 2020 John Goerzen +# SPDX-FileCopyrightText: 2021 - 2023 Thom Wiggers +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Joseph Walton-Rivers +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2021 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Matrix Appservice IRC is a Matrix <-> IRC bridge # Project source code URL: https://github.com/matrix-org/matrix-appservice-irc diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/main.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/main.yml index d46698480..ba6332519 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/migrate_nedb_to_postgres.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/migrate_nedb_to_postgres.yml index 47d796886..866d0cba3 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/migrate_nedb_to_postgres.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/migrate_nedb_to_postgres.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Jez Cope +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if Postgres not enabled diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/setup_install.yml index 4e91e073f..b4cb63c86 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/setup_install.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.include_role: diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/setup_uninstall.yml index f16d3763f..371c42503 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-irc service diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml index f8dcf76ab..e923180ed 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required appservice-irc settings not defined diff --git a/roles/custom/matrix-bridge-appservice-irc/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-irc/templates/config.yaml.j2.license new file mode 100644 index 000000000..919fa142d --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-irc/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2.license b/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2.license new file mode 100644 index 000000000..cadd27bdd --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-irc/templates/systemd/matrix-appservice-irc.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 MDAD project contributors +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 4b7dbcefecd98e66e4ca4674c5255357d8fff999 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 14:47:17 +0900 Subject: [PATCH 805/952] Add license information to matrix-bridge-appservice-slack Signed-off-by: Suguru Hirahara --- ...nfiguring-playbook-bridge-appservice-slack.md | 11 +++++++++++ .../defaults/main.yml | 16 ++++++++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/migrate_nedb_to_postgres.yml | 6 ++++++ .../tasks/setup_install.yml | 12 ++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 6 ++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-appservice-slack.service.j2.license | 6 ++++++ 10 files changed, 81 insertions(+) create mode 100644 roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2.license diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md index 4d602da35..5de62f97c 100644 --- a/docs/configuring-playbook-bridge-appservice-slack.md +++ b/docs/configuring-playbook-bridge-appservice-slack.md @@ -1,3 +1,14 @@ + + # Setting up Appservice Slack bridging (optional) **Notes**: diff --git a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml index abc875cc2..4a8eb2dc7 100644 --- a/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-slack/defaults/main.yml @@ -1,3 +1,19 @@ +# SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Daniel Wiegreffe +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Béla Becker +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 Didier 'OdyX' Raboud +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Fabio Bonelli +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-appservice-slack is a Matrix <-> Slack bridge # Project source code URL: https://github.com/matrix-org/matrix-appservice-slack diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/main.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/main.yml index c98dc5198..c9251c190 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/migrate_nedb_to_postgres.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/migrate_nedb_to_postgres.yml index b3a6ee937..e4b2f372f 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/migrate_nedb_to_postgres.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/migrate_nedb_to_postgres.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if Postgres not enabled diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/setup_install.yml index 619276bdb..b556910f8 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/setup_install.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure AppService Slack paths exist diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/setup_uninstall.yml index 51c77fef0..e37cfb046 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-appservice-slack service diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml index d6d802dd3..66eddaf11 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 boris runakov +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required appservice-slack settings not defined diff --git a/roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2.license new file mode 100644 index 000000000..52f246738 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Didier 'OdyX' Raboud +SPDX-FileCopyrightText: 2024 Fabio Bonelli + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-slack/templates/labels.j2 b/roles/custom/matrix-bridge-appservice-slack/templates/labels.j2 index 5e025ae12..212902fde 100644 --- a/roles/custom/matrix-bridge-appservice-slack/templates/labels.j2 +++ b/roles/custom/matrix-bridge-appservice-slack/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_appservice_slack_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2.license b/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2.license new file mode 100644 index 000000000..c395d00d7 --- /dev/null +++ b/roles/custom/matrix-bridge-appservice-slack/templates/systemd/matrix-appservice-slack.service.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2019 MDAD project contributors +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 497a0f8a42bcac2f75930ede3edd91514c685776 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:38:54 +0900 Subject: [PATCH 806/952] Add license information to files for matrix-bridge-beeper-linkedin Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-beeper-linkedin.md | 10 ++++++++++ .../matrix-bridge-beeper-linkedin/defaults/main.yml | 11 +++++++++++ .../matrix-bridge-beeper-linkedin/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 6 ++++++ .../systemd/matrix-beeper-linkedin.service.j2.license | 4 ++++ 8 files changed, 60 insertions(+) create mode 100644 roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2.license diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md index 995ea6faa..e2628661b 100644 --- a/docs/configuring-playbook-bridge-beeper-linkedin.md +++ b/docs/configuring-playbook-bridge-beeper-linkedin.md @@ -1,3 +1,13 @@ + + # Setting up Beeper Linkedin bridging (optional) The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the mautrix bridges. diff --git a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml index 873e9be95..e06c37c37 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Alexandar Mechev +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Paul ALNET +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # beeper-linkedin is a Matrix <-> LinkedIn bridge # Project source code URL: https://github.com/beeper/linkedin diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/main.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/main.yml index 56eb91e52..34a4ea3dd 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/main.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Alexandar Mechev +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml index 7d27b1559..e61dc18fb 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Alexandar Mechev +# SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Beeper LinkedIn paths exists diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_uninstall.yml index 4d3334692..aea2f34cf 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Alexandar Mechev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-beeper-linkedin service diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml index dc87a45e7..059eeebc8 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Alexandar Mechev +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required beeper-linkedin settings not defined diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2.license new file mode 100644 index 000000000..fa76a7a16 --- /dev/null +++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2021 Alexandar Mechev +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2.license b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2.license new file mode 100644 index 000000000..a6a2062ab --- /dev/null +++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Alexandar Mechev +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From d403a7e4ae9ee467cc9c951e1a924c3554bff9fb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:40:16 +0900 Subject: [PATCH 807/952] Add license information to files for matrix-bridge-heisenbridge Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-heisenbridge.md | 8 ++++++++ .../matrix-bridge-heisenbridge/defaults/main.yml | 10 ++++++++++ roles/custom/matrix-bridge-heisenbridge/tasks/main.yml | 6 ++++++ .../matrix-bridge-heisenbridge/tasks/setup_install.yml | 10 ++++++++++ .../tasks/setup_uninstall.yml | 7 +++++++ .../tasks/validate_config.yml | 5 +++++ .../matrix-bridge-heisenbridge/templates/labels.j2 | 6 ++++++ .../systemd/matrix-heisenbridge.service.j2.license | 4 ++++ 8 files changed, 56 insertions(+) create mode 100644 roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2.license diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md index d8f0dcde6..c49b7b21a 100644 --- a/docs/configuring-playbook-bridge-heisenbridge.md +++ b/docs/configuring-playbook-bridge-heisenbridge.md @@ -1,3 +1,11 @@ + + # Setting up Heisenbridge bouncer-style IRC bridging (optional) **Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook. diff --git a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml index c39c20c68..0bf20fc21 100644 --- a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Toni Spets +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Heisenbridge is a bouncer-style Matrix IRC bridge # Project source code URL: https://github.com/hifi/heisenbridge diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/main.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/main.yml index b281d00bf..7de077071 100644 --- a/roles/custom/matrix-bridge-heisenbridge/tasks/main.yml +++ b/roles/custom/matrix-bridge-heisenbridge/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Toni Spets +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml index 9ea3500ff..a748464db 100644 --- a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 Toni Spets +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Heisenbridge image is pulled diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_uninstall.yml index 090427ca3..ba42105de 100644 --- a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Michael Sasser +# SPDX-FileCopyrightText: 2021 Toni Spets +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-heisenbridge service diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml index 604df5a56..34e63877f 100644 --- a/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Heisenbridge settings not defined diff --git a/roles/custom/matrix-bridge-heisenbridge/templates/labels.j2 b/roles/custom/matrix-bridge-heisenbridge/templates/labels.j2 index ee54ac8e1..fa2cb1ee1 100644 --- a/roles/custom/matrix-bridge-heisenbridge/templates/labels.j2 +++ b/roles/custom/matrix-bridge-heisenbridge/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_heisenbridge_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2.license b/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2.license new file mode 100644 index 000000000..8d056c7ba --- /dev/null +++ b/roles/custom/matrix-bridge-heisenbridge/templates/systemd/matrix-heisenbridge.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From b7bd54113dc425c18ee4b61b4c28ed8e8c32d516 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:40:25 +0900 Subject: [PATCH 808/952] Add license information to files for matrix-bridge-sms Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-matrix-bridge-sms.md | 8 ++++++++ roles/custom/matrix-bridge-sms/defaults/main.yml | 10 ++++++++++ roles/custom/matrix-bridge-sms/tasks/main.yml | 6 ++++++ roles/custom/matrix-bridge-sms/tasks/setup_install.yml | 10 ++++++++++ .../custom/matrix-bridge-sms/tasks/setup_uninstall.yml | 6 ++++++ .../custom/matrix-bridge-sms/tasks/validate_config.yml | 7 +++++++ .../systemd/matrix-sms-bridge.service.j2.license | 5 +++++ 7 files changed, 52 insertions(+) create mode 100644 roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2.license diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md index c580f26c5..0f0a1bbbe 100644 --- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md +++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md @@ -1,3 +1,11 @@ + + # Setting up Matrix SMS bridging (optional) The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you. diff --git a/roles/custom/matrix-bridge-sms/defaults/main.yml b/roles/custom/matrix-bridge-sms/defaults/main.yml index 4dc5b4268..992d8b936 100644 --- a/roles/custom/matrix-bridge-sms/defaults/main.yml +++ b/roles/custom/matrix-bridge-sms/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-sms-bridge is a Matrix <-> SMS bridge # Project source code URL: https://github.com/benkuly/matrix-sms-bridge diff --git a/roles/custom/matrix-bridge-sms/tasks/main.yml b/roles/custom/matrix-bridge-sms/tasks/main.yml index 57d517275..574dba74b 100644 --- a/roles/custom/matrix-bridge-sms/tasks/main.yml +++ b/roles/custom/matrix-bridge-sms/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-sms/tasks/setup_install.yml b/roles/custom/matrix-bridge-sms/tasks/setup_install.yml index 1fc34b9ca..a46bc21dc 100644 --- a/roles/custom/matrix-bridge-sms/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-sms/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-sms-bridge image is pulled diff --git a/roles/custom/matrix-bridge-sms/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-sms/tasks/setup_uninstall.yml index c7d0011ec..f6e1e2a6e 100644 --- a/roles/custom/matrix-bridge-sms/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-sms/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-sms-bridge service diff --git a/roles/custom/matrix-bridge-sms/tasks/validate_config.yml b/roles/custom/matrix-bridge-sms/tasks/validate_config.yml index 474e2526c..2830ae8bb 100644 --- a/roles/custom/matrix-bridge-sms/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-sms/tasks/validate_config.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-bridge-sms settings not defined diff --git a/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2.license b/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2.license new file mode 100644 index 000000000..cb09f3c35 --- /dev/null +++ b/roles/custom/matrix-bridge-sms/templates/systemd/matrix-sms-bridge.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 MDAD project contributors +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 52cf117e8bccc0e6ec048923e8cc40d22293a234 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:40:59 +0900 Subject: [PATCH 809/952] Add license information to files for matrix-bridge-postmoogle Refer fd39392ec5924edbbac5217248872a2e7554a7de as well Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-postmoogle.md | 9 +++++++++ roles/custom/matrix-bridge-postmoogle/defaults/main.yml | 8 ++++++++ roles/custom/matrix-bridge-postmoogle/tasks/main.yml | 6 ++++++ .../matrix-bridge-postmoogle/tasks/setup_install.yml | 8 ++++++++ .../matrix-bridge-postmoogle/tasks/setup_uninstall.yml | 7 +++++++ .../matrix-bridge-postmoogle/tasks/validate_config.yml | 6 ++++++ roles/custom/matrix-bridge-postmoogle/templates/env.j2 | 8 ++++++++ .../systemd/matrix-postmoogle.service.j2.license | 5 +++++ 8 files changed, 57 insertions(+) create mode 100644 roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2.license diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md index eff5b62e3..6a21043a7 100644 --- a/docs/configuring-playbook-bridge-postmoogle.md +++ b/docs/configuring-playbook-bridge-postmoogle.md @@ -1,3 +1,12 @@ + + # Setting up Postmoogle email bridging (optional) The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you. diff --git a/roles/custom/matrix-bridge-postmoogle/defaults/main.yml b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml index fd2838141..930225bd2 100644 --- a/roles/custom/matrix-bridge-postmoogle/defaults/main.yml +++ b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Luke D Iremadze +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # postmoogle is an email to Matrix bridge using its bot user # Project source code URL: https://github.com/etkecc/postmoogle diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/main.yml b/roles/custom/matrix-bridge-postmoogle/tasks/main.yml index 0b4dbc60b..ecbbff69a 100644 --- a/roles/custom/matrix-bridge-postmoogle/tasks/main.yml +++ b/roles/custom/matrix-bridge-postmoogle/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml b/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml index 61a8e7873..4dc78ddc7 100644 --- a/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Check and remove the legacy systemd service (`matrix-bot-postmoogle.service`). diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml index 28b243429..9db50fc5c 100644 --- a/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-postmoogle service diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml b/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml index b2138a6de..78b40d94c 100644 --- a/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Postmoogle settings not defined diff --git a/roles/custom/matrix-bridge-postmoogle/templates/env.j2 b/roles/custom/matrix-bridge-postmoogle/templates/env.j2 index b56f88ae2..a2a8348bf 100644 --- a/roles/custom/matrix-bridge-postmoogle/templates/env.j2 +++ b/roles/custom/matrix-bridge-postmoogle/templates/env.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + POSTMOOGLE_LOGIN={{ matrix_postmoogle_login }} POSTMOOGLE_PASSWORD={{ matrix_postmoogle_password }} POSTMOOGLE_SHAREDSECRET={{ matrix_postmoogle_sharedsecret }} diff --git a/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2.license b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2.license new file mode 100644 index 000000000..c8f114ab8 --- /dev/null +++ b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 974971719f5f8df9d610d51ff039043248d1ace0 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:41:23 +0900 Subject: [PATCH 810/952] Add license information to files for matrix-bridge-hookshot Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-hookshot.md | 10 ++++++++++ .../custom/matrix-bridge-hookshot/defaults/main.yml | 12 ++++++++++++ roles/custom/matrix-bridge-hookshot/tasks/main.yml | 6 ++++++ .../tasks/reset_encryption.yml | 4 ++++ .../matrix-bridge-hookshot/tasks/setup_install.yml | 12 ++++++++++++ .../matrix-bridge-hookshot/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-bridge-hookshot/tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 6 ++++++ .../matrix-bridge-hookshot/templates/labels.j2 | 6 ++++++ .../templates/registration.yml.j2.license | 6 ++++++ .../systemd/matrix-hookshot.service.j2.license | 4 ++++ 11 files changed, 78 insertions(+) create mode 100644 roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2.license create mode 100644 roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2.license diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md index 8aacefd66..fc637d853 100644 --- a/docs/configuring-playbook-bridge-hookshot.md +++ b/docs/configuring-playbook-bridge-hookshot.md @@ -1,3 +1,13 @@ + + # Setting up matrix-hookshot (optional) The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you. diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml index 0bf53fbbe..2b204cbd3 100644 --- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml +++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Arthur Brugière +# SPDX-FileCopyrightText: 2022 Kim Brose +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Kris Watson +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # A bridge between Matrix and multiple project management services, such as GitHub, GitLab and JIRA. diff --git a/roles/custom/matrix-bridge-hookshot/tasks/main.yml b/roles/custom/matrix-bridge-hookshot/tasks/main.yml index 89f110dd4..afe5da088 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/main.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml b/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml index 2ae5e7f8f..26c0e3eba 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-hookshot is stopped diff --git a/roles/custom/matrix-bridge-hookshot/tasks/setup_install.yml b/roles/custom/matrix-bridge-hookshot/tasks/setup_install.yml index f76ae653c..a44edff15 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/setup_install.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Arthur Brugière +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2023 Luke Moch +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.include_role: diff --git a/roles/custom/matrix-bridge-hookshot/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-hookshot/tasks/setup_uninstall.yml index b4c72d38a..253bba45a 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-hookshot service diff --git a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml index 760fd8048..a0848da91 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed Hookshot variables diff --git a/roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2.license new file mode 100644 index 000000000..e7fcfb5ab --- /dev/null +++ b/roles/custom/matrix-bridge-hookshot/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-hookshot/templates/labels.j2 b/roles/custom/matrix-bridge-hookshot/templates/labels.j2 index 31c035300..d7a36da4d 100644 --- a/roles/custom/matrix-bridge-hookshot/templates/labels.j2 +++ b/roles/custom/matrix-bridge-hookshot/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_hookshot_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2.license b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2.license new file mode 100644 index 000000000..00feb2e4f --- /dev/null +++ b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Kim Brose + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2.license b/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2.license new file mode 100644 index 000000000..c751d3d6f --- /dev/null +++ b/roles/custom/matrix-bridge-hookshot/templates/systemd/matrix-hookshot.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later From cb18b5235f4f54d1866dcbaeef7f91492fcf9389 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 18:41:51 +0900 Subject: [PATCH 811/952] Add license information to files for matrix-dynamic-dns Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dynamic-dns.md | 8 ++++++++ roles/custom/matrix-dynamic-dns/defaults/main.yml | 10 ++++++++++ roles/custom/matrix-dynamic-dns/tasks/main.yml | 6 ++++++ .../custom/matrix-dynamic-dns/tasks/setup_install.yml | 9 +++++++++ .../matrix-dynamic-dns/tasks/setup_uninstall.yml | 6 ++++++ .../matrix-dynamic-dns/tasks/validate_config.yml | 5 +++++ .../matrix-dynamic-dns/templates/ddclient.conf.j2 | 7 +++++++ .../systemd/matrix-dynamic-dns.service.j2.license | 4 ++++ 8 files changed, 55 insertions(+) create mode 100644 roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2.license diff --git a/docs/configuring-playbook-dynamic-dns.md b/docs/configuring-playbook-dynamic-dns.md index 6db0e941d..0a254a76d 100644 --- a/docs/configuring-playbook-dynamic-dns.md +++ b/docs/configuring-playbook-dynamic-dns.md @@ -1,3 +1,11 @@ + + # Setting up Dynamic DNS (optional) 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. diff --git a/roles/custom/matrix-dynamic-dns/defaults/main.yml b/roles/custom/matrix-dynamic-dns/defaults/main.yml index e9b7b0eab..6ecdcd404 100644 --- a/roles/custom/matrix-dynamic-dns/defaults/main.yml +++ b/roles/custom/matrix-dynamic-dns/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Scott Crossen +# SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/linuxserver/docker-ddclient diff --git a/roles/custom/matrix-dynamic-dns/tasks/main.yml b/roles/custom/matrix-dynamic-dns/tasks/main.yml index 8327a84ac..e56d44c0f 100644 --- a/roles/custom/matrix-dynamic-dns/tasks/main.yml +++ b/roles/custom/matrix-dynamic-dns/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Scott Crossen +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-dynamic-dns/tasks/setup_install.yml b/roles/custom/matrix-dynamic-dns/tasks/setup_install.yml index 8440d791b..45eac171d 100644 --- a/roles/custom/matrix-dynamic-dns/tasks/setup_install.yml +++ b/roles/custom/matrix-dynamic-dns/tasks/setup_install.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Scott Crossen +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Dynamic DNS image is pulled diff --git a/roles/custom/matrix-dynamic-dns/tasks/setup_uninstall.yml b/roles/custom/matrix-dynamic-dns/tasks/setup_uninstall.yml index 8f9f1b040..af7ce670b 100644 --- a/roles/custom/matrix-dynamic-dns/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-dynamic-dns/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Scott Crossen +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-dynamic-dns service diff --git a/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml b/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml index d7dd34717..3b567415a 100644 --- a/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml +++ b/roles/custom/matrix-dynamic-dns/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Scott Crossen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if no matrix-dynamic-dns configurations specified diff --git a/roles/custom/matrix-dynamic-dns/templates/ddclient.conf.j2 b/roles/custom/matrix-dynamic-dns/templates/ddclient.conf.j2 index 1480d834e..158f9f66e 100644 --- a/roles/custom/matrix-dynamic-dns/templates/ddclient.conf.j2 +++ b/roles/custom/matrix-dynamic-dns/templates/ddclient.conf.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + daemon={{ matrix_dynamic_dns_daemon_interval }} syslog=no pid=/var/run/ddclient/ddclient.pid diff --git a/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2.license b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2.license new file mode 100644 index 000000000..ba251d31b --- /dev/null +++ b/roles/custom/matrix-dynamic-dns/templates/systemd/matrix-dynamic-dns.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 41c59a122347af610e8d767f6d5d05fad7c3811a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 21:24:13 +0900 Subject: [PATCH 812/952] Add license information to files for matrix-authentication-service Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-authentication-service.md | 7 +++++++ .../custom/matrix-authentication-service/defaults/main.yml | 5 +++++ .../custom/matrix-authentication-service/tasks/install.yml | 4 ++++ roles/custom/matrix-authentication-service/tasks/main.yml | 4 ++++ .../matrix-authentication-service/tasks/mas_cli_doctor.yml | 4 ++++ .../matrix-authentication-service/tasks/register_user.yml | 4 ++++ .../custom/matrix-authentication-service/tasks/syn2mas.yml | 5 +++++ .../matrix-authentication-service/tasks/uninstall.yml | 4 ++++ .../tasks/util/prepare_key.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/bin/mas-cli.j2.license | 3 +++ .../templates/bin/register-user.j2.license | 3 +++ .../templates/config.yaml.j2.license | 3 +++ .../custom/matrix-authentication-service/templates/env.j2 | 6 ++++++ .../matrix-authentication-service/templates/labels.j2 | 6 ++++++ .../templates/provider/anthropic-config.yml.j2.license | 3 +++ .../templates/provider/groq-config.yml.j2.license | 3 +++ .../templates/provider/mistral-config.yml.j2.license | 3 +++ .../templates/provider/openai-config.yml.j2.license | 3 +++ .../matrix-authentication-service.service.j2.license | 3 +++ roles/custom/matrix-authentication-service/vars/main.yml | 4 ++++ 21 files changed, 85 insertions(+) create mode 100644 roles/custom/matrix-authentication-service/templates/bin/mas-cli.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/bin/register-user.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/provider/anthropic-config.yml.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/provider/groq-config.yml.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/provider/mistral-config.yml.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/provider/openai-config.yml.j2.license create mode 100644 roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2.license diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md index da339f5ed..eda09cc4b 100644 --- a/docs/configuring-playbook-matrix-authentication-service.md +++ b/docs/configuring-playbook-matrix-authentication-service.md @@ -1,3 +1,10 @@ + + # Setting up Matrix Authentication Service (optional) The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/). diff --git a/roles/custom/matrix-authentication-service/defaults/main.yml b/roles/custom/matrix-authentication-service/defaults/main.yml index 4f50ce9dc..c6c441d34 100644 --- a/roles/custom/matrix-authentication-service/defaults/main.yml +++ b/roles/custom/matrix-authentication-service/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-authentication-service (MAS) is an OAuth 2.0 and OpenID Provider server for Matrix. diff --git a/roles/custom/matrix-authentication-service/tasks/install.yml b/roles/custom/matrix-authentication-service/tasks/install.yml index b766c1cb6..2b04b6708 100644 --- a/roles/custom/matrix-authentication-service/tasks/install.yml +++ b/roles/custom/matrix-authentication-service/tasks/install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix Authentication Service paths exist diff --git a/roles/custom/matrix-authentication-service/tasks/main.yml b/roles/custom/matrix-authentication-service/tasks/main.yml index c5a7e9c80..6b6a07718 100644 --- a/roles/custom/matrix-authentication-service/tasks/main.yml +++ b/roles/custom/matrix-authentication-service/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-authentication-service/tasks/mas_cli_doctor.yml b/roles/custom/matrix-authentication-service/tasks/mas_cli_doctor.yml index 96689d6e2..a172f8629 100644 --- a/roles/custom/matrix-authentication-service/tasks/mas_cli_doctor.yml +++ b/roles/custom/matrix-authentication-service/tasks/mas_cli_doctor.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix Authentication Service is started diff --git a/roles/custom/matrix-authentication-service/tasks/register_user.yml b/roles/custom/matrix-authentication-service/tasks/register_user.yml index 9aef7ab47..34abb6b7a 100644 --- a/roles/custom/matrix-authentication-service/tasks/register_user.yml +++ b/roles/custom/matrix-authentication-service/tasks/register_user.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-authentication-service/tasks/syn2mas.yml b/roles/custom/matrix-authentication-service/tasks/syn2mas.yml index 821892f8d..fd30158a4 100644 --- a/roles/custom/matrix-authentication-service/tasks/syn2mas.yml +++ b/roles/custom/matrix-authentication-service/tasks/syn2mas.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-authentication-service/tasks/uninstall.yml b/roles/custom/matrix-authentication-service/tasks/uninstall.yml index e7e0dfe43..4d7938fbd 100644 --- a/roles/custom/matrix-authentication-service/tasks/uninstall.yml +++ b/roles/custom/matrix-authentication-service/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-authentication-service service diff --git a/roles/custom/matrix-authentication-service/tasks/util/prepare_key.yml b/roles/custom/matrix-authentication-service/tasks/util/prepare_key.yml index 79fdc2e73..1c1877ccd 100644 --- a/roles/custom/matrix-authentication-service/tasks/util/prepare_key.yml +++ b/roles/custom/matrix-authentication-service/tasks/util/prepare_key.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Prepare Matrix Authentication Service private key file path ({{ private_key_definition.key_file }}) diff --git a/roles/custom/matrix-authentication-service/tasks/validate_config.yml b/roles/custom/matrix-authentication-service/tasks/validate_config.yml index 7ef8b5a1c..59b59957b 100644 --- a/roles/custom/matrix-authentication-service/tasks/validate_config.yml +++ b/roles/custom/matrix-authentication-service/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-authentication-service settings not defined diff --git a/roles/custom/matrix-authentication-service/templates/bin/mas-cli.j2.license b/roles/custom/matrix-authentication-service/templates/bin/mas-cli.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/bin/mas-cli.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/bin/register-user.j2.license b/roles/custom/matrix-authentication-service/templates/bin/register-user.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/bin/register-user.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/config.yaml.j2.license b/roles/custom/matrix-authentication-service/templates/config.yaml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/config.yaml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/env.j2 b/roles/custom/matrix-authentication-service/templates/env.j2 index 80c4290de..3a0423c61 100644 --- a/roles/custom/matrix-authentication-service/templates/env.j2 +++ b/roles/custom/matrix-authentication-service/templates/env.j2 @@ -1 +1,7 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {{ matrix_authentication_service_environment_variables_extension }} diff --git a/roles/custom/matrix-authentication-service/templates/labels.j2 b/roles/custom/matrix-authentication-service/templates/labels.j2 index 461c7abd7..f66cf4c7f 100644 --- a/roles/custom/matrix-authentication-service/templates/labels.j2 +++ b/roles/custom/matrix-authentication-service/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_authentication_service_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-authentication-service/templates/provider/anthropic-config.yml.j2.license b/roles/custom/matrix-authentication-service/templates/provider/anthropic-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/provider/anthropic-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/provider/groq-config.yml.j2.license b/roles/custom/matrix-authentication-service/templates/provider/groq-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/provider/groq-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/provider/mistral-config.yml.j2.license b/roles/custom/matrix-authentication-service/templates/provider/mistral-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/provider/mistral-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/provider/openai-config.yml.j2.license b/roles/custom/matrix-authentication-service/templates/provider/openai-config.yml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/provider/openai-config.yml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2.license b/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-authentication-service/templates/systemd/matrix-authentication-service.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-authentication-service/vars/main.yml b/roles/custom/matrix-authentication-service/vars/main.yml index 4bedfdbfc..45e7ad639 100644 --- a/roles/custom/matrix-authentication-service/vars/main.yml +++ b/roles/custom/matrix-authentication-service/vars/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Like `matrix_authentication_service_config_http_public_base` but a private base URL only accessible from within the container network. From 09893ced8dbd35e224304d3195313ea2f1bbba99 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 21:24:22 +0900 Subject: [PATCH 813/952] Add license information to files for matrix-client-schildichat Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-client-schildichat-web.md | 8 ++++++++ roles/custom/matrix-client-schildichat/defaults/main.yml | 7 +++++++ roles/custom/matrix-client-schildichat/tasks/main.yml | 4 ++++ .../matrix-client-schildichat/tasks/prepare_themes.yml | 5 +++++ .../custom/matrix-client-schildichat/tasks/self_check.yml | 6 ++++++ .../matrix-client-schildichat/tasks/setup_install.yml | 8 ++++++++ .../matrix-client-schildichat/tasks/setup_uninstall.yml | 5 +++++ .../matrix-client-schildichat/tasks/validate_config.yml | 6 ++++++ .../templates/config.json.j2.license | 4 ++++ .../custom/matrix-client-schildichat/templates/labels.j2 | 7 +++++++ .../templates/map_style.json.j2.license | 3 +++ .../systemd/matrix-client-schildichat.service.j2.license | 5 +++++ .../templates/welcome.html.j2.license | 4 ++++ roles/custom/matrix-client-schildichat/vars/main.yml | 4 ++++ 14 files changed, 76 insertions(+) create mode 100644 roles/custom/matrix-client-schildichat/templates/config.json.j2.license create mode 100644 roles/custom/matrix-client-schildichat/templates/map_style.json.j2.license create mode 100644 roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2.license create mode 100644 roles/custom/matrix-client-schildichat/templates/welcome.html.j2.license diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md index ec34b2be7..e26a6837f 100644 --- a/docs/configuring-playbook-client-schildichat-web.md +++ b/docs/configuring-playbook-client-schildichat-web.md @@ -1,3 +1,11 @@ + + # Setting up SchildiChat Web (optional) The playbook can install and configure the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you. diff --git a/roles/custom/matrix-client-schildichat/defaults/main.yml b/roles/custom/matrix-client-schildichat/defaults/main.yml index ec3d5e39d..4619af27c 100644 --- a/roles/custom/matrix-client-schildichat/defaults/main.yml +++ b/roles/custom/matrix-client-schildichat/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/SchildiChat/schildichat-desktop diff --git a/roles/custom/matrix-client-schildichat/tasks/main.yml b/roles/custom/matrix-client-schildichat/tasks/main.yml index 240dee1cf..476bc76d5 100644 --- a/roles/custom/matrix-client-schildichat/tasks/main.yml +++ b/roles/custom/matrix-client-schildichat/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml b/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml index 521679bc0..4c2167bcd 100644 --- a/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml +++ b/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # diff --git a/roles/custom/matrix-client-schildichat/tasks/self_check.yml b/roles/custom/matrix-client-schildichat/tasks/self_check.yml index 5e8771111..255975cad 100644 --- a/roles/custom/matrix-client-schildichat/tasks/self_check.yml +++ b/roles/custom/matrix-client-schildichat/tasks/self_check.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml index 0be2563d4..2a577df58 100644 --- a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml +++ b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure SchildiChat Web paths exists diff --git a/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml b/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml index 67f6856ff..d53238fb4 100644 --- a/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-client-schildichat.service diff --git a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml index 3331a705b..97f556092 100644 --- a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml +++ b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed SchildiChat Web settings diff --git a/roles/custom/matrix-client-schildichat/templates/config.json.j2.license b/roles/custom/matrix-client-schildichat/templates/config.json.j2.license new file mode 100644 index 000000000..2d30733cd --- /dev/null +++ b/roles/custom/matrix-client-schildichat/templates/config.json.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-schildichat/templates/labels.j2 b/roles/custom/matrix-client-schildichat/templates/labels.j2 index 25f19f6b4..e7b87ad72 100644 --- a/roles/custom/matrix-client-schildichat/templates/labels.j2 +++ b/roles/custom/matrix-client-schildichat/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_client_schildichat_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-client-schildichat/templates/map_style.json.j2.license b/roles/custom/matrix-client-schildichat/templates/map_style.json.j2.license new file mode 100644 index 000000000..d84b8388e --- /dev/null +++ b/roles/custom/matrix-client-schildichat/templates/map_style.json.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2023 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2.license b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2.license new file mode 100644 index 000000000..4f7c9af82 --- /dev/null +++ b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-schildichat/templates/welcome.html.j2.license b/roles/custom/matrix-client-schildichat/templates/welcome.html.j2.license new file mode 100644 index 000000000..27cec7bdf --- /dev/null +++ b/roles/custom/matrix-client-schildichat/templates/welcome.html.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-schildichat/vars/main.yml b/roles/custom/matrix-client-schildichat/vars/main.yml index bbd0d3dd0..d338feb65 100644 --- a/roles/custom/matrix-client-schildichat/vars/main.yml +++ b/roles/custom/matrix-client-schildichat/vars/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_client_schildichat_embedded_pages_home_url: "{{ ('' if matrix_client_schildichat_embedded_pages_home_path is none else 'home.html') }}" From 0bbe13b474f880915dde2ec897a948bac890ee84 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 21:24:31 +0900 Subject: [PATCH 814/952] Add license information to files for matrix-conduit Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-conduit.md | 8 ++++++++ roles/custom/matrix-conduit/defaults/main.yml | 7 +++++++ roles/custom/matrix-conduit/tasks/main.yml | 5 +++++ roles/custom/matrix-conduit/tasks/setup_install.yml | 8 ++++++++ roles/custom/matrix-conduit/tasks/setup_uninstall.yml | 6 ++++++ roles/custom/matrix-conduit/tasks/validate_config.yml | 4 ++++ roles/custom/matrix-conduit/templates/conduit.toml.j2 | 8 ++++++++ roles/custom/matrix-conduit/templates/labels.j2 | 7 +++++++ .../templates/systemd/matrix-conduit.service.j2.license | 4 ++++ roles/custom/matrix-conduit/vars/main.yml | 5 +++++ 10 files changed, 62 insertions(+) create mode 100644 roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2.license diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index 51cfb8e64..ef5e381fe 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -1,3 +1,11 @@ + + # Configuring Conduit (optional) The playbook can install and configure the [Conduit](https://conduit.rs) Matrix server for you. diff --git a/roles/custom/matrix-conduit/defaults/main.yml b/roles/custom/matrix-conduit/defaults/main.yml index aba5a8a3a..726c39d29 100644 --- a/roles/custom/matrix-conduit/defaults/main.yml +++ b/roles/custom/matrix-conduit/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Samuel Meenzen +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Charles Wright +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Conduit is a simple, fast and reliable chat server powered by Matrix # Project source code URL: https://gitlab.com/famedly/conduit diff --git a/roles/custom/matrix-conduit/tasks/main.yml b/roles/custom/matrix-conduit/tasks/main.yml index d8389a5b9..1c790ce58 100644 --- a/roles/custom/matrix-conduit/tasks/main.yml +++ b/roles/custom/matrix-conduit/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Charles Wright +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-conduit/tasks/setup_install.yml b/roles/custom/matrix-conduit/tasks/setup_install.yml index 5db1ba225..a4a65b097 100644 --- a/roles/custom/matrix-conduit/tasks/setup_install.yml +++ b/roles/custom/matrix-conduit/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Charles Wright +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Conduit config path exists diff --git a/roles/custom/matrix-conduit/tasks/setup_uninstall.yml b/roles/custom/matrix-conduit/tasks/setup_uninstall.yml index 1745ff973..d8b4743de 100644 --- a/roles/custom/matrix-conduit/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-conduit/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Charles Wright +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-conduit service diff --git a/roles/custom/matrix-conduit/tasks/validate_config.yml b/roles/custom/matrix-conduit/tasks/validate_config.yml index 8635661d0..2e5bdc3e2 100644 --- a/roles/custom/matrix-conduit/tasks/validate_config.yml +++ b/roles/custom/matrix-conduit/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Conduit settings not defined diff --git a/roles/custom/matrix-conduit/templates/conduit.toml.j2 b/roles/custom/matrix-conduit/templates/conduit.toml.j2 index 42f215f5a..e1ae99dee 100644 --- a/roles/custom/matrix-conduit/templates/conduit.toml.j2 +++ b/roles/custom/matrix-conduit/templates/conduit.toml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Charles Wright +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # ============================================================================= # This is the official example config for Conduit. # If you use it for your server, you will need to adjust it to your own needs. diff --git a/roles/custom/matrix-conduit/templates/labels.j2 b/roles/custom/matrix-conduit/templates/labels.j2 index 33c2789a0..9dafbef81 100644 --- a/roles/custom/matrix-conduit/templates/labels.j2 +++ b/roles/custom/matrix-conduit/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2024 Daniel Lo Nigro +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_conduit_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2.license b/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2.license new file mode 100644 index 000000000..e05b9cf3f --- /dev/null +++ b/roles/custom/matrix-conduit/templates/systemd/matrix-conduit.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Charles Wright + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-conduit/vars/main.yml b/roles/custom/matrix-conduit/vars/main.yml index 633204070..8ac0e1257 100644 --- a/roles/custom/matrix-conduit/vars/main.yml +++ b/roles/custom/matrix-conduit/vars/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Charles Wright +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_conduit_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduit_hostname }}/_matrix/client/versions" matrix_conduit_federation_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduit_hostname }}:{{ matrix_federation_public_port }}/_matrix/federation/v1/version" From e870f0b66453dbbeb475c5150f9fb195b016e51c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 21:24:39 +0900 Subject: [PATCH 815/952] Add license information to files for matrix-dendrite Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-dendrite.md | 8 ++++++++ roles/custom/matrix-dendrite/defaults/main.yml | 14 ++++++++++++++ roles/custom/matrix-dendrite/tasks/main.yml | 7 +++++++ .../custom/matrix-dendrite/tasks/register_user.yml | 6 ++++++ .../tasks/self_check_client_api.yml | 6 ++++++ .../tasks/self_check_federation_api.yml | 6 ++++++ .../custom/matrix-dendrite/tasks/setup_install.yml | 11 +++++++++++ .../matrix-dendrite/tasks/setup_uninstall.yml | 4 ++++ .../matrix-dendrite/tasks/validate_config.yml | 6 ++++++ .../templates/bin/create-account.j2.license | 3 +++ .../matrix-dendrite/templates/dendrite.yaml.j2 | 10 ++++++++++ roles/custom/matrix-dendrite/templates/labels.j2 | 6 ++++++ .../systemd/matrix-dendrite.service.j2.license | 7 +++++++ roles/custom/matrix-dendrite/vars/main.yml | 5 +++++ 14 files changed, 99 insertions(+) create mode 100644 roles/custom/matrix-dendrite/templates/bin/create-account.j2.license create mode 100644 roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2.license diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md index ac5671dbf..80481e864 100644 --- a/docs/configuring-playbook-dendrite.md +++ b/docs/configuring-playbook-dendrite.md @@ -1,3 +1,11 @@ + + # Configuring Dendrite (optional) The playbook can install and configure the [Dendrite](https://github.com/element-hq/dendrite) Matrix server for you. diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml index 8a3a7bc40..50e9116eb 100644 --- a/roles/custom/matrix-dendrite/defaults/main.yml +++ b/roles/custom/matrix-dendrite/defaults/main.yml @@ -1,3 +1,17 @@ +# SPDX-FileCopyrightText: 2022 - 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Darren Rambaud +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Shaleen Jain +# SPDX-FileCopyrightText: 2023 Isaiah Becker-Mayer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Dendrite is a second-generation Matrix homeserver currently in Beta # Project source code URL: https://github.com/matrix-org/dendrite diff --git a/roles/custom/matrix-dendrite/tasks/main.yml b/roles/custom/matrix-dendrite/tasks/main.yml index 78d81524c..b241677b1 100644 --- a/roles/custom/matrix-dendrite/tasks/main.yml +++ b/roles/custom/matrix-dendrite/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-dendrite/tasks/register_user.yml b/roles/custom/matrix-dendrite/tasks/register_user.yml index 8ee18ed2f..fa2c0339b 100644 --- a/roles/custom/matrix-dendrite/tasks/register_user.yml +++ b/roles/custom/matrix-dendrite/tasks/register_user.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-dendrite/tasks/self_check_client_api.yml b/roles/custom/matrix-dendrite/tasks/self_check_client_api.yml index f6eb602c6..d681793a1 100644 --- a/roles/custom/matrix-dendrite/tasks/self_check_client_api.yml +++ b/roles/custom/matrix-dendrite/tasks/self_check_client_api.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Client API ansible.builtin.uri: diff --git a/roles/custom/matrix-dendrite/tasks/self_check_federation_api.yml b/roles/custom/matrix-dendrite/tasks/self_check_federation_api.yml index bba20ff16..82b220679 100644 --- a/roles/custom/matrix-dendrite/tasks/self_check_federation_api.yml +++ b/roles/custom/matrix-dendrite/tasks/self_check_federation_api.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Federation API ansible.builtin.uri: diff --git a/roles/custom/matrix-dendrite/tasks/setup_install.yml b/roles/custom/matrix-dendrite/tasks/setup_install.yml index acc2558f7..262f16d04 100644 --- a/roles/custom/matrix-dendrite/tasks/setup_install.yml +++ b/roles/custom/matrix-dendrite/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2023 Isaiah Becker-Mayer +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Dendrite paths exist ansible.builtin.file: diff --git a/roles/custom/matrix-dendrite/tasks/setup_uninstall.yml b/roles/custom/matrix-dendrite/tasks/setup_uninstall.yml index f6a537b30..fb744a88f 100644 --- a/roles/custom/matrix-dendrite/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-dendrite/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-dendrite service diff --git a/roles/custom/matrix-dendrite/tasks/validate_config.yml b/roles/custom/matrix-dendrite/tasks/validate_config.yml index 339ac8fb2..243015588 100644 --- a/roles/custom/matrix-dendrite/tasks/validate_config.yml +++ b/roles/custom/matrix-dendrite/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed Dendrite settings diff --git a/roles/custom/matrix-dendrite/templates/bin/create-account.j2.license b/roles/custom/matrix-dendrite/templates/bin/create-account.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-dendrite/templates/bin/create-account.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2 b/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2 index 3b7947260..8f03b16db 100644 --- a/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2 +++ b/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2 @@ -1,3 +1,13 @@ +{# +SPDX-FileCopyrightText: 2022 - 2023 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Jip J. Dekker +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # This is the Dendrite configuration file. # # The configuration is split up into sections - each Dendrite component has a diff --git a/roles/custom/matrix-dendrite/templates/labels.j2 b/roles/custom/matrix-dendrite/templates/labels.j2 index d74424b99..18a69573a 100644 --- a/roles/custom/matrix-dendrite/templates/labels.j2 +++ b/roles/custom/matrix-dendrite/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_dendrite_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2.license b/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2.license new file mode 100644 index 000000000..e4e9cc7ca --- /dev/null +++ b/roles/custom/matrix-dendrite/templates/systemd/matrix-dendrite.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Charles Wright +SPDX-FileCopyrightText: 2022 Jip J. Dekker +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 Shaleen Jain + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dendrite/vars/main.yml b/roles/custom/matrix-dendrite/vars/main.yml index 28a0f1bde..0a09d57c1 100644 --- a/roles/custom/matrix-dendrite/vars/main.yml +++ b/roles/custom/matrix-dendrite/vars/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jip J. Dekker +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_dendrite_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_dendrite_hostname }}/_matrix/client/versions" matrix_dendrite_federation_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_dendrite_hostname }}:{{ matrix_federation_public_port }}/_matrix/federation/v1/version" From 87634922dddf591e1c4268ff96bacf825df2c6eb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 22:24:58 +0900 Subject: [PATCH 816/952] Update docs for components related to authentication: add copyright headers Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ldap-auth.md | 9 +++++++++ docs/configuring-playbook-rest-auth.md | 8 ++++++++ docs/configuring-playbook-shared-secret-auth.md | 8 ++++++++ 3 files changed, 25 insertions(+) diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md index d3a95d138..7507c8330 100644 --- a/docs/configuring-playbook-ldap-auth.md +++ b/docs/configuring-playbook-ldap-auth.md @@ -1,3 +1,12 @@ + + # Setting up the LDAP authentication password provider module (optional, advanced) The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you. diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index d15ba586b..6952f3f1e 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -1,3 +1,11 @@ + + # Setting up the REST authentication password provider module (optional, advanced) The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you. diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index c7dced046..9f4dfd736 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -1,3 +1,11 @@ + + # Setting up the Shared Secret Auth password provider module (optional, advanced) The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you. From 66093857bcf32009b02bde37ff3b4acbdad43e7a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 22:25:08 +0900 Subject: [PATCH 817/952] Update docs for components related to authentication: adopt the common descriptions Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ldap-auth.md | 10 ++++++---- docs/configuring-playbook-rest-auth.md | 6 +++--- docs/configuring-playbook-shared-secret-auth.md | 6 +++--- 3 files changed, 12 insertions(+), 10 deletions(-) diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md index 7507c8330..ba135cca1 100644 --- a/docs/configuring-playbook-ldap-auth.md +++ b/docs/configuring-playbook-ldap-auth.md @@ -2,7 +2,7 @@ SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev SPDX-FileCopyrightText: 2019 - 2023 MDAD project contributors SPDX-FileCopyrightText: 2020 Marcel Partap -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> @@ -13,7 +13,9 @@ The playbook can install and configure the [matrix-synapse-ldap3](https://github See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you. -If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): +## Adjusting the playbook configuration + +Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs): ```yaml matrix_synapse_ext_password_provider_ldap_enabled: true @@ -30,9 +32,9 @@ matrix_synapse_ext_password_provider_ldap_bind_password: "" matrix_synapse_ext_password_provider_ldap_filter: "" ``` -## Authenticating only using a password provider +### Authenticating only using a password provider -If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it: +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: ```yaml matrix_synapse_password_config_localdb_enabled: false diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index 6952f3f1e..1ec45d17a 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -1,7 +1,7 @@ @@ -24,9 +24,9 @@ matrix_synapse_ext_password_provider_rest_auth_registration_profile_name_autofil matrix_synapse_ext_password_provider_rest_auth_login_profile_name_autofill: false ``` -## Authenticating only using a password provider +### Authenticating only using a password provider -If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it: +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: ```yaml matrix_synapse_password_config_localdb_enabled: false diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md index 9f4dfd736..07d42d762 100644 --- a/docs/configuring-playbook-shared-secret-auth.md +++ b/docs/configuring-playbook-shared-secret-auth.md @@ -1,7 +1,7 @@ @@ -23,9 +23,9 @@ matrix_synapse_ext_password_provider_shared_secret_auth_enabled: true matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: YOUR_SHARED_SECRET_GOES_HERE ``` -## Authenticating only using a password provider +### Authenticating only using a password provider -If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it: +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: ```yaml matrix_synapse_password_config_localdb_enabled: false From ff1f882d3c638db9262267109d67f38f29a51bfb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 22:25:14 +0900 Subject: [PATCH 818/952] Update docs for components related to authentication: tidy up MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Move the recommendation to avoid installing ma1sd from configuring-playbook-ldap-auth.md to configuring-playbook-rest-auth.md It has been long since recommending to install ma1sd was stopped, and the warning message is placed on the documentation about installing ma1sd as well, so it does not really seem to be sensible to advertise the component by repeating the warning… The message can rather be reused on the latter, as it is expected to be implemented with a backend such as ma1sd (see: matrix_synapse_ext_password_provider_rest_auth_endpoint on the file) - Add instruction to install the component to configuring-playbook-ldap-auth.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ldap-auth.md | 17 +++++++++++++---- docs/configuring-playbook-rest-auth.md | 9 +++++++++ 2 files changed, 22 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md index ba135cca1..f6736a735 100644 --- a/docs/configuring-playbook-ldap-auth.md +++ b/docs/configuring-playbook-ldap-auth.md @@ -40,12 +40,21 @@ If you wish for users to **authenticate only against configured password provide matrix_synapse_password_config_localdb_enabled: false ``` -## Using ma1sd Identity Server for authentication (not recommended) +## Installing -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. +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: -If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication). + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` -## Handling user registration +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Usage + +### Handling user registration 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). diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md index 1ec45d17a..216b71e37 100644 --- a/docs/configuring-playbook-rest-auth.md +++ b/docs/configuring-playbook-rest-auth.md @@ -44,3 +44,12 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + +## Usage + +### Use ma1sd Identity Server for the backend (not recommended) + +This module does not provide direct integration with any backend. For the backend you can use [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server, which can be configured with the playbook. + +> [!WARNING] +> We recommend not bothering with installing ma1sd as it has been unmaintained for years. If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md). From 4d5367fe934b00160df6fadc1beeeecae796fa4c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 28 Feb 2025 22:27:56 +0900 Subject: [PATCH 819/952] Update docs/configuring-playbook-ma1sd.md: improve the warning message on top Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ma1sd.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md index 812ef14d4..694a1f39c 100644 --- a/docs/configuring-playbook-ma1sd.md +++ b/docs/configuring-playbook-ma1sd.md @@ -4,14 +4,17 @@ SPDX-FileCopyrightText: 2019 Noah Fleischmann SPDX-FileCopyrightText: 2019 - 2020 MDAD project contributors SPDX-FileCopyrightText: 2020 Marcel Partap SPDX-FileCopyrightText: 2020 Justin Croonenberghs -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> # Setting up ma1sd Identity Server (optional) -**⚠️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). +> [!WARNING] +> Since ma1sd has been unmaintained for years (the latest commit and release being from 2021) and the future of identity server's role in the Matrix specification is uncertain, **we recommend not bothering with installing it unless it's the only way you can do what you need to do**. +> +> Please note that certain things 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. 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. From e2d18794109f72b090aa6e709fe8265fece3f31c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 01:38:47 +0900 Subject: [PATCH 820/952] Add license information to files for matrix-ldap-registration-proxy Signed-off-by: Suguru Hirahara --- ...configuring-playbook-matrix-ldap-registration-proxy.md | 8 ++++++++ .../matrix-ldap-registration-proxy/defaults/main.yml | 6 ++++++ .../custom/matrix-ldap-registration-proxy/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 8 ++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 6 ++++++ .../matrix-ldap-registration-proxy/templates/labels.j2 | 6 ++++++ .../templates/ldap-registration-proxy.env.j2 | 8 ++++++++ .../matrix-ldap-registration-proxy.service.j2.license | 5 +++++ 9 files changed, 59 insertions(+) create mode 100644 roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2.license diff --git a/docs/configuring-playbook-matrix-ldap-registration-proxy.md b/docs/configuring-playbook-matrix-ldap-registration-proxy.md index 29e825a92..7073b81b6 100644 --- a/docs/configuring-playbook-matrix-ldap-registration-proxy.md +++ b/docs/configuring-playbook-matrix-ldap-registration-proxy.md @@ -1,3 +1,11 @@ + + # Setting up matrix-ldap-registration-proxy (optional) The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you. diff --git a/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml b/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml index b7dd0996c..4ff410860 100644 --- a/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml +++ b/roles/custom/matrix-ldap-registration-proxy/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix_ldap_registration_proxy - Want to build a large-scale Matrix server using external registration on LDAP? # Project source code URL: https://gitlab.com/activism.international/matrix_ldap_registration_proxy diff --git a/roles/custom/matrix-ldap-registration-proxy/tasks/main.yml b/roles/custom/matrix-ldap-registration-proxy/tasks/main.yml index 9a7f24d2d..191a3538b 100644 --- a/roles/custom/matrix-ldap-registration-proxy/tasks/main.yml +++ b/roles/custom/matrix-ldap-registration-proxy/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-ldap-registration-proxy/tasks/setup_install.yml b/roles/custom/matrix-ldap-registration-proxy/tasks/setup_install.yml index 43f16292e..e068a629b 100644 --- a/roles/custom/matrix-ldap-registration-proxy/tasks/setup_install.yml +++ b/roles/custom/matrix-ldap-registration-proxy/tasks/setup_install.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix_ldap_registration_proxy paths exist diff --git a/roles/custom/matrix-ldap-registration-proxy/tasks/setup_uninstall.yml b/roles/custom/matrix-ldap-registration-proxy/tasks/setup_uninstall.yml index 20e98a6e4..281488b18 100644 --- a/roles/custom/matrix-ldap-registration-proxy/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-ldap-registration-proxy/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-matrix_ldap_registration_proxy service diff --git a/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml b/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml index d8fcdf96b..97d94fe7f 100644 --- a/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml +++ b/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-ldap-registration-proxy settings not defined diff --git a/roles/custom/matrix-ldap-registration-proxy/templates/labels.j2 b/roles/custom/matrix-ldap-registration-proxy/templates/labels.j2 index 8ce1832f1..73a7d25ed 100644 --- a/roles/custom/matrix-ldap-registration-proxy/templates/labels.j2 +++ b/roles/custom/matrix-ldap-registration-proxy/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_ldap_registration_proxy_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-ldap-registration-proxy/templates/ldap-registration-proxy.env.j2 b/roles/custom/matrix-ldap-registration-proxy/templates/ldap-registration-proxy.env.j2 index 0def38932..d40193e1b 100644 --- a/roles/custom/matrix-ldap-registration-proxy/templates/ldap-registration-proxy.env.j2 +++ b/roles/custom/matrix-ldap-registration-proxy/templates/ldap-registration-proxy.env.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # please specify the configuration here # # these settings are mandatory diff --git a/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2.license b/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2.license new file mode 100644 index 000000000..618b21aeb --- /dev/null +++ b/roles/custom/matrix-ldap-registration-proxy/templates/systemd/matrix-ldap-registration-proxy.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later From d3826ee6528cc4584688887bc9a58a81478e7419 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 01:41:41 +0900 Subject: [PATCH 821/952] Add license information to files for matrix-media-repo Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-matrix-media-repo.md | 9 +++++++++ roles/custom/matrix-media-repo/defaults/main.yml | 8 ++++++++ roles/custom/matrix-media-repo/tasks/main.yml | 5 +++++ roles/custom/matrix-media-repo/tasks/setup_install.yml | 7 +++++++ roles/custom/matrix-media-repo/tasks/setup_uninstall.yml | 4 ++++ roles/custom/matrix-media-repo/tasks/validate_config.yml | 5 +++++ .../templates/grafana/media-repo.json.license | 3 +++ .../custom/matrix-media-repo/templates/media-repo/env.j2 | 6 ++++++ .../matrix-media-repo/templates/media-repo/labels.j2 | 7 +++++++ .../templates/media-repo/media-repo.yaml.j2 | 7 +++++++ .../systemd/matrix-media-repo.service.j2.license | 4 ++++ 11 files changed, 65 insertions(+) create mode 100644 roles/custom/matrix-media-repo/templates/grafana/media-repo.json.license create mode 100644 roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2.license diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md index 33dd5ce1a..e660d434d 100644 --- a/docs/configuring-playbook-matrix-media-repo.md +++ b/docs/configuring-playbook-matrix-media-repo.md @@ -1,3 +1,12 @@ + + # Storing Matrix media files using matrix-media-repo (optional) The playbook can install and configure [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated "MMR") for you. diff --git a/roles/custom/matrix-media-repo/defaults/main.yml b/roles/custom/matrix-media-repo/defaults/main.yml index f41489a5b..c2485207e 100755 --- a/roles/custom/matrix-media-repo/defaults/main.yml +++ b/roles/custom/matrix-media-repo/defaults/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-media-repo is a highly customizable multi-domain media repository for Matrix. # Intended for medium to large environments consisting of several homeservers, this diff --git a/roles/custom/matrix-media-repo/tasks/main.yml b/roles/custom/matrix-media-repo/tasks/main.yml index 4bf63251d..2ebd19ef1 100644 --- a/roles/custom/matrix-media-repo/tasks/main.yml +++ b/roles/custom/matrix-media-repo/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Michael Hollister +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-media-repo/tasks/setup_install.yml b/roles/custom/matrix-media-repo/tasks/setup_install.yml index 67bf8bec2..525df257f 100755 --- a/roles/custom/matrix-media-repo/tasks/setup_install.yml +++ b/roles/custom/matrix-media-repo/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +# SPDX-FileCopyrightText: 2024 Daniel A. Maierhofer +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure media-repo paths exist diff --git a/roles/custom/matrix-media-repo/tasks/setup_uninstall.yml b/roles/custom/matrix-media-repo/tasks/setup_uninstall.yml index 449cd48b8..45595daee 100644 --- a/roles/custom/matrix-media-repo/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-media-repo/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Michael Hollister +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of media-repo service diff --git a/roles/custom/matrix-media-repo/tasks/validate_config.yml b/roles/custom/matrix-media-repo/tasks/validate_config.yml index bd923eec6..e9b4d64f9 100644 --- a/roles/custom/matrix-media-repo/tasks/validate_config.yml +++ b/roles/custom/matrix-media-repo/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Michael Hollister +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-media-repo settings not defined diff --git a/roles/custom/matrix-media-repo/templates/grafana/media-repo.json.license b/roles/custom/matrix-media-repo/templates/grafana/media-repo.json.license new file mode 100644 index 000000000..147b2c483 --- /dev/null +++ b/roles/custom/matrix-media-repo/templates/grafana/media-repo.json.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-media-repo/templates/media-repo/env.j2 b/roles/custom/matrix-media-repo/templates/media-repo/env.j2 index 8b26f77d7..e325e595d 100644 --- a/roles/custom/matrix-media-repo/templates/media-repo/env.j2 +++ b/roles/custom/matrix-media-repo/templates/media-repo/env.j2 @@ -1 +1,7 @@ +{# +SPDX-FileCopyrightText: 2023 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + REPO_CONFIG=/config/media-repo.yaml diff --git a/roles/custom/matrix-media-repo/templates/media-repo/labels.j2 b/roles/custom/matrix-media-repo/templates/media-repo/labels.j2 index 57b21d897..17eac5cc9 100755 --- a/roles/custom/matrix-media-repo/templates/media-repo/labels.j2 +++ b/roles/custom/matrix-media-repo/templates/media-repo/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_media_repo_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2 b/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2 index 6142bc95b..fa60434fa 100644 --- a/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2 +++ b/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # General repo configuration repo: bindAddress: {{ matrix_media_repo_bind_address | to_json }} diff --git a/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2.license b/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2.license new file mode 100644 index 000000000..1c5c26f3b --- /dev/null +++ b/roles/custom/matrix-media-repo/templates/media-repo/systemd/matrix-media-repo.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later From 66e37a68ae16f8499827364d9e8cd282cd68459f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 01:41:49 +0900 Subject: [PATCH 822/952] Add license information to files for matrix-coturn Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-turn.md | 10 ++++++++++ roles/custom/matrix-coturn/defaults/main.yml | 15 +++++++++++++++ roles/custom/matrix-coturn/tasks/main.yml | 6 ++++++ .../custom/matrix-coturn/tasks/setup_install.yml | 14 ++++++++++++++ .../matrix-coturn/tasks/setup_uninstall.yml | 5 +++++ .../matrix-coturn/tasks/validate_config.yml | 5 +++++ .../systemd/matrix-coturn-reload.service.j2 | 6 ++++++ .../systemd/matrix-coturn-reload.timer.j2 | 8 ++++++++ .../systemd/matrix-coturn.service.j2.license | 8 ++++++++ .../templates/turnserver.conf.j2.license | 6 ++++++ roles/custom/matrix-coturn/vars/main.yml | 4 ++++ 11 files changed, 87 insertions(+) create mode 100644 roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2.license create mode 100644 roles/custom/matrix-coturn/templates/turnserver.conf.j2.license diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index 56858d886..9c9b31271 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -1,3 +1,13 @@ + + # Configuring a TURN server (optional, advanced) 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. diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml index b3ecb1efd..9c82097c4 100644 --- a/roles/custom/matrix-coturn/defaults/main.yml +++ b/roles/custom/matrix-coturn/defaults/main.yml @@ -1,3 +1,18 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Stuart Mumford +# SPDX-FileCopyrightText: 2019 Sylvia van Os +# SPDX-FileCopyrightText: 2020 - 2021 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Hefty Zauk +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/coturn/coturn diff --git a/roles/custom/matrix-coturn/tasks/main.yml b/roles/custom/matrix-coturn/tasks/main.yml index 1b1332fb7..0aa46f58f 100644 --- a/roles/custom/matrix-coturn/tasks/main.yml +++ b/roles/custom/matrix-coturn/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-coturn/tasks/setup_install.yml b/roles/custom/matrix-coturn/tasks/setup_install.yml index 9349c7be0..697edb4ee 100644 --- a/roles/custom/matrix-coturn/tasks/setup_install.yml +++ b/roles/custom/matrix-coturn/tasks/setup_install.yml @@ -1,3 +1,17 @@ +# SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 - 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Béla Becker +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - when: matrix_coturn_turn_external_ip_address_auto_detection_enabled | bool diff --git a/roles/custom/matrix-coturn/tasks/setup_uninstall.yml b/roles/custom/matrix-coturn/tasks/setup_uninstall.yml index e747ff094..57746906c 100644 --- a/roles/custom/matrix-coturn/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-coturn/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-coturn service diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml index 2b71deb2a..ff0ac914b 100644 --- a/roles/custom/matrix-coturn/tasks/validate_config.yml +++ b/roles/custom/matrix-coturn/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed coturn settings diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.service.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.service.j2 index 7d12f6ec8..f1f3d0f6a 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.service.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.service.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + [Unit] Description=Reloads matrix-coturn so that new SSL certificates can kick in diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 index d4b0b1093..902ed5821 100644 --- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.timer.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 Hardy Erlinger +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + [Unit] Description=Reloads matrix-coturn periodically so that new SSL certificates can kick in diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2.license b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2.license new file mode 100644 index 000000000..df5eb9b5a --- /dev/null +++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2021 Dan Arnfield +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-coturn/templates/turnserver.conf.j2.license b/roles/custom/matrix-coturn/templates/turnserver.conf.j2.license new file mode 100644 index 000000000..98807515d --- /dev/null +++ b/roles/custom/matrix-coturn/templates/turnserver.conf.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Stuart Mumford +SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-coturn/vars/main.yml b/roles/custom/matrix-coturn/vars/main.yml index 0c0a1c24f..4391c2853 100644 --- a/roles/custom/matrix-coturn/vars/main.yml +++ b/roles/custom/matrix-coturn/vars/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_coturn_turn_uris: |- From 70655e898163f0e0078ca6bb611ff7b943f02df3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 12:25:45 +0900 Subject: [PATCH 823/952] Fix GitHub issue template selector Apparently those Markdown files are not expected to have something before the three hyphens on the top. Signed-off-by: Suguru Hirahara --- .github/ISSUE_TEMPLATE/bug_report.md | 7 ------- .github/ISSUE_TEMPLATE/bug_report.md.license | 4 ++++ .github/ISSUE_TEMPLATE/feature_request.md | 7 ------- .github/ISSUE_TEMPLATE/feature_request.md.license | 4 ++++ .github/ISSUE_TEMPLATE/i-need-help.md | 7 ------- .github/ISSUE_TEMPLATE/i-need-help.md.license | 4 ++++ 6 files changed, 12 insertions(+), 21 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md.license create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md.license create mode 100644 .github/ISSUE_TEMPLATE/i-need-help.md.license diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 67582267d..985806d5b 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -1,10 +1,3 @@ - - --- name: Bug report about: Create a report to help us improve diff --git a/.github/ISSUE_TEMPLATE/bug_report.md.license b/.github/ISSUE_TEMPLATE/bug_report.md.license new file mode 100644 index 000000000..3e8049371 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 0b21a2fef..5746ab313 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -1,10 +1,3 @@ - - --- name: Feature request about: Suggest an idea for this project diff --git a/.github/ISSUE_TEMPLATE/feature_request.md.license b/.github/ISSUE_TEMPLATE/feature_request.md.license new file mode 100644 index 000000000..3e8049371 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/.github/ISSUE_TEMPLATE/i-need-help.md b/.github/ISSUE_TEMPLATE/i-need-help.md index 9f76ce259..03632d440 100644 --- a/.github/ISSUE_TEMPLATE/i-need-help.md +++ b/.github/ISSUE_TEMPLATE/i-need-help.md @@ -1,10 +1,3 @@ - - --- name: I need help about: Get support from our community diff --git a/.github/ISSUE_TEMPLATE/i-need-help.md.license b/.github/ISSUE_TEMPLATE/i-need-help.md.license new file mode 100644 index 000000000..3e8049371 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/i-need-help.md.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From b57081debdfb530cd702e9ec27a37733f6ddcc1d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 12:50:15 +0900 Subject: [PATCH 824/952] Add CC0-1.0.txt to LICENSES directory Signed-off-by: Suguru Hirahara --- LICENSES/CC0-1.0.txt | 121 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 LICENSES/CC0-1.0.txt diff --git a/LICENSES/CC0-1.0.txt b/LICENSES/CC0-1.0.txt new file mode 100644 index 000000000..0e259d42c --- /dev/null +++ b/LICENSES/CC0-1.0.txt @@ -0,0 +1,121 @@ +Creative Commons Legal Code + +CC0 1.0 Universal + + CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE + LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN + ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS + INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES + REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS + PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM + THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED + HEREUNDER. + +Statement of Purpose + +The laws of most jurisdictions throughout the world automatically confer +exclusive Copyright and Related Rights (defined below) upon the creator +and subsequent owner(s) (each and all, an "owner") of an original work of +authorship and/or a database (each, a "Work"). + +Certain owners wish to permanently relinquish those rights to a Work for +the purpose of contributing to a commons of creative, cultural and +scientific works ("Commons") that the public can reliably and without fear +of later claims of infringement build upon, modify, incorporate in other +works, reuse and redistribute as freely as possible in any form whatsoever +and for any purposes, including without limitation commercial purposes. +These owners may contribute to the Commons to promote the ideal of a free +culture and the further production of creative, cultural and scientific +works, or to gain reputation or greater distribution for their Work in +part through the use and efforts of others. + +For these and/or other purposes and motivations, and without any +expectation of additional consideration or compensation, the person +associating CC0 with a Work (the "Affirmer"), to the extent that he or she +is an owner of Copyright and Related Rights in the Work, voluntarily +elects to apply CC0 to the Work and publicly distribute the Work under its +terms, with knowledge of his or her Copyright and Related Rights in the +Work and the meaning and intended legal effect of CC0 on those rights. + +1. Copyright and Related Rights. A Work made available under CC0 may be +protected by copyright and related or neighboring rights ("Copyright and +Related Rights"). Copyright and Related Rights include, but are not +limited to, the following: + + i. the right to reproduce, adapt, distribute, perform, display, + communicate, and translate a Work; + ii. moral rights retained by the original author(s) and/or performer(s); +iii. publicity and privacy rights pertaining to a person's image or + likeness depicted in a Work; + iv. rights protecting against unfair competition in regards to a Work, + subject to the limitations in paragraph 4(a), below; + v. rights protecting the extraction, dissemination, use and reuse of data + in a Work; + vi. database rights (such as those arising under Directive 96/9/EC of the + European Parliament and of the Council of 11 March 1996 on the legal + protection of databases, and under any national implementation + thereof, including any amended or successor version of such + directive); and +vii. other similar, equivalent or corresponding rights throughout the + world based on applicable law or treaty, and any national + implementations thereof. + +2. Waiver. To the greatest extent permitted by, but not in contravention +of, applicable law, Affirmer hereby overtly, fully, permanently, +irrevocably and unconditionally waives, abandons, and surrenders all of +Affirmer's Copyright and Related Rights and associated claims and causes +of action, whether now known or unknown (including existing as well as +future claims and causes of action), in the Work (i) in all territories +worldwide, (ii) for the maximum duration provided by applicable law or +treaty (including future time extensions), (iii) in any current or future +medium and for any number of copies, and (iv) for any purpose whatsoever, +including without limitation commercial, advertising or promotional +purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each +member of the public at large and to the detriment of Affirmer's heirs and +successors, fully intending that such Waiver shall not be subject to +revocation, rescission, cancellation, termination, or any other legal or +equitable action to disrupt the quiet enjoyment of the Work by the public +as contemplated by Affirmer's express Statement of Purpose. + +3. Public License Fallback. Should any part of the Waiver for any reason +be judged legally invalid or ineffective under applicable law, then the +Waiver shall be preserved to the maximum extent permitted taking into +account Affirmer's express Statement of Purpose. In addition, to the +extent the Waiver is so judged Affirmer hereby grants to each affected +person a royalty-free, non transferable, non sublicensable, non exclusive, +irrevocable and unconditional license to exercise Affirmer's Copyright and +Related Rights in the Work (i) in all territories worldwide, (ii) for the +maximum duration provided by applicable law or treaty (including future +time extensions), (iii) in any current or future medium and for any number +of copies, and (iv) for any purpose whatsoever, including without +limitation commercial, advertising or promotional purposes (the +"License"). The License shall be deemed effective as of the date CC0 was +applied by Affirmer to the Work. Should any part of the License for any +reason be judged legally invalid or ineffective under applicable law, such +partial invalidity or ineffectiveness shall not invalidate the remainder +of the License, and in such case Affirmer hereby affirms that he or she +will not (i) exercise any of his or her remaining Copyright and Related +Rights in the Work or (ii) assert any associated claims and causes of +action with respect to the Work, in either case contrary to Affirmer's +express Statement of Purpose. + +4. Limitations and Disclaimers. + + a. No trademark or patent rights held by Affirmer are waived, abandoned, + surrendered, licensed or otherwise affected by this document. + b. Affirmer offers the Work as-is and makes no representations or + warranties of any kind concerning the Work, express, implied, + statutory or otherwise, including without limitation warranties of + title, merchantability, fitness for a particular purpose, non + infringement, or the absence of latent or other defects, accuracy, or + the present or absence of errors, whether or not discoverable, all to + the greatest extent permissible under applicable law. + c. Affirmer disclaims responsibility for clearing rights of other persons + that may apply to the Work or any use thereof, including without + limitation any person's Copyright and Related Rights in the Work. + Further, Affirmer disclaims responsibility for obtaining any necessary + consents, permissions or other rights required for any use of the + Work. + d. Affirmer understands and acknowledges that Creative Commons is not a + party to this document and has no duty or obligation with respect to + this CC0 or use of the Work. From f88df9b782dafafd47305e4241da5d2555a65205 Mon Sep 17 00:00:00 2001 From: adam-kress Date: Fri, 28 Feb 2025 23:58:29 -0500 Subject: [PATCH 825/952] Upgrade Jitsi (v10008-3 -> v10078-1-0) (#4126) * Upgrade Jitsi (v10008-3 -> v10073-1) * Upgrade Jitsi (v10073-1 -> v10078-0) * v10078-0 -> v10078-1 * Fix Jitsi version tag --------- Co-authored-by: Slavi Pantaleev --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 389df2513..372b7fcee 100644 --- a/requirements.yml +++ b/requirements.yml @@ -25,7 +25,7 @@ version: v11.5.2-2 name: grafana - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git - version: v10008-3 + version: v10078-1-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git version: v2.11.0-3 From dbfcb2d2c12a07577523509505134d0e1b5c9fbc Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 1 Mar 2025 07:01:56 +0200 Subject: [PATCH 826/952] Upgrade Traefik (v3.3.3-4 -> v3.3.4-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 372b7fcee..b042d8ef1 100644 --- a/requirements.yml +++ b/requirements.yml @@ -64,7 +64,7 @@ version: v1.0.0-0 name: timesync - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git - version: v3.3.3-4 + version: v3.3.4-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git version: v2.8.3-7 From b488ff5dd51d5f4705d556cdb1d55e5aa403a2d7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:03:55 +0900 Subject: [PATCH 827/952] Add license information to files for matrix-bridge-mautrix-bluesky Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-bluesky.md | 7 +++++++ .../custom/matrix-bridge-mautrix-bluesky/defaults/main.yml | 5 +++++ roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml | 4 ++++ .../matrix-bridge-mautrix-bluesky/tasks/setup_install.yml | 4 ++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 3 +++ .../matrix-bridge-mautrix-bluesky/templates/labels.j2 | 6 ++++++ .../systemd/matrix-mautrix-bluesky.service.j2.license | 4 ++++ 9 files changed, 42 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-bluesky.md b/docs/configuring-playbook-bridge-mautrix-bluesky.md index 632f6509a..fac227c78 100644 --- a/docs/configuring-playbook-bridge-mautrix-bluesky.md +++ b/docs/configuring-playbook-bridge-mautrix-bluesky.md @@ -1,3 +1,10 @@ + + # Setting up Mautrix Bluesky bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml index 2fb7c44f2..e43d3bea2 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-bluesky is a Matrix <-> Bluesky bridge # Project source code URL: https://github.com/mautrix/bluesky diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml index dd56963ab..0071485aa 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml index 17fbaed14..305ac5730 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml index c3c170699..e38cd26c9 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-bluesky service diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml index 23e433d33..5e7b03753 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-bluesky settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2.license new file mode 100644 index 000000000..826be4a75 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/config.yaml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2025 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 index 876f48012..bec40b880 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2025 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_bluesky_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2.license b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2.license new file mode 100644 index 000000000..6fe7fc50c --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-bluesky/templates/systemd/matrix-mautrix-bluesky.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2025 MDAD project contributors +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 9da4317d42fd7e0cadabde1a38e3fc15e72b9184 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:05 +0900 Subject: [PATCH 828/952] Update docs/configuring-playbook-bridge-mautrix-bridges.md: add a copyright header Refer f8b779f8ed36426eeb3db2e27aa6826d7e65f506 as well Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-bridges.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index def918c84..557e1a9a4 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -1,3 +1,12 @@ + + # Setting up a Generic Mautrix Bridge (optional) The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges. From f6b74f9d3010570646809c96723ddb7239983831 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:15 +0900 Subject: [PATCH 829/952] Add license information to files for matrix-bridge-mautrix-discord Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-discord.md | 12 ++++++++++++ .../matrix-bridge-mautrix-discord/defaults/main.yml | 8 ++++++++ .../matrix-bridge-mautrix-discord/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 7 +++++++ .../tasks/setup_uninstall.yml | 5 +++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-discord.service.j2.license | 4 ++++ 9 files changed, 57 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md index 0a8c743bb..12d9f243d 100644 --- a/docs/configuring-playbook-bridge-mautrix-discord.md +++ b/docs/configuring-playbook-bridge-mautrix-discord.md @@ -1,3 +1,15 @@ + + # Setting up Mautrix Discord bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml index b6486ed0c..fa1a8e777 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-discord is a Matrix <-> Discord bridge # Project source code URL: https://github.com/mautrix/discord diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/main.yml index 19698f9f1..dc5ccdd4e 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml index a83092973..e08b1c34c 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_uninstall.yml index ade37c2f8..0b5ddc54f 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-discord service diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml index ed04f643b..63552ebb7 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-discord settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2.license new file mode 100644 index 000000000..9c33473b5 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Samuel Meenzen + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 index adc265db2..be59b906e 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_discord_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2.license b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2.license new file mode 100644 index 000000000..c751d3d6f --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later From 053a0e8b9977dba28e736dd6a124530929e13d6f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:24 +0900 Subject: [PATCH 830/952] Add license information to files for matrix-bridge-mautrix-gmessages Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-gmessages.md | 8 ++++++++ .../matrix-bridge-mautrix-gmessages/defaults/main.yml | 9 +++++++++ .../matrix-bridge-mautrix-gmessages/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 7 +++++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../matrix-bridge-mautrix-gmessages/templates/labels.j2 | 6 ++++++ .../systemd/matrix-mautrix-gmessages.service.j2.license | 4 ++++ 9 files changed, 53 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md index 658b8eb95..d9289ec56 100644 --- a/docs/configuring-playbook-bridge-mautrix-gmessages.md +++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md @@ -1,3 +1,11 @@ + + # Setting up Mautrix Google Messages bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml index 46b1e3099..92099b6b1 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-gmessages is a Matrix <-> gmessages bridge # Project source code URL: https://github.com/mautrix/gmessages diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/main.yml index 4ca9e19fe..df53f0892 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_install.yml index 5a3e59f75..777dceab7 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_uninstall.yml index e324a523e..e0fae19e7 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-gmessages service diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml index 1358465e5..ccf220349 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-gmessages settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2.license new file mode 100644 index 000000000..fb1e93f66 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2023 MDAD project contributors +SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-gmessages/templates/labels.j2 index 1beea2c1c..8dfe66067 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-gmessages/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_gmessages_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2.license b/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2.license new file mode 100644 index 000000000..90f8a2544 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-gmessages/templates/systemd/matrix-mautrix-gmessages.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu + +SPDX-License-Identifier: AGPL-3.0-or-later From 42e09a4aa53411b22700b8246d401585f78fa459 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:33 +0900 Subject: [PATCH 831/952] Add license information to files for matrix-bridge-mautrix-googlechat Signed-off-by: Suguru Hirahara --- .../configuring-playbook-bridge-mautrix-googlechat.md | 9 +++++++++ .../defaults/main.yml | 11 +++++++++++ .../matrix-bridge-mautrix-googlechat/tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 10 ++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 6 ++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-googlechat.service.j2.license | 4 ++++ 9 files changed, 64 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-googlechat/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md index a2e3dff61..5fd1ef99b 100644 --- a/docs/configuring-playbook-bridge-mautrix-googlechat.md +++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md @@ -1,3 +1,12 @@ + + # Setting up Mautrix Google Chat bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml index 50d991dd5..213573c11 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Ruben Hias +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-googlechat is a Matrix <-> googlechat bridge # Project source code URL: https://github.com/mautrix/googlechat diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/main.yml index be11089b7..3cdc701da 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_install.yml index 6d8adebf4..d7cc1f1d5 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_uninstall.yml index 12b486308..412a08847 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-googlechat service diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml index b6543a188..19c89c46c 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-googlechat settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-googlechat/templates/config.yaml.j2.license new file mode 100644 index 000000000..0e41586c5 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-googlechat/templates/config.yaml.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2022 László Várady + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-googlechat/templates/labels.j2 index 8f35f5c51..567dc2958 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-googlechat/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_googlechat_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2.license b/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2.license new file mode 100644 index 000000000..f91d0b692 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-googlechat/templates/systemd/matrix-mautrix-googlechat.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 40939cde65d368b8a58714fd577e80608937a6e9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:38 +0900 Subject: [PATCH 832/952] Add license information to files for matrix-bridge-mautrix-meta-instagram Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-meta-instagram.md | 7 +++++++ .../custom/matrix-bridge-mautrix-meta-instagram/README.md | 6 ++++++ .../matrix-bridge-mautrix-meta-instagram/defaults/main.yml | 7 +++++++ .../matrix-bridge-mautrix-meta-instagram/tasks/install.yml | 5 +++++ .../matrix-bridge-mautrix-meta-instagram/tasks/main.yml | 4 ++++ .../tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/config.yaml.j2.license | 5 +++++ .../templates/labels.j2 | 6 ++++++ .../systemd/matrix-mautrix-meta.service.j2.license | 3 +++ 10 files changed, 51 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index 26c34f8d9..c53a22aba 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -1,3 +1,10 @@ + + # Setting up Instagram bridging via Mautrix Meta (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/README.md b/roles/custom/matrix-bridge-mautrix-meta-instagram/README.md index 41e9d77d9..ef06fdc36 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/README.md +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/README.md @@ -1,3 +1,9 @@ + + # matrix-mautrix-meta-instagram This bridge role is derived from the matrix-mautrix-meta-messenger Ansible role via automatic changes (see `just rebuild-mautrix-meta-instagram` or `bin/rebuild-mautrix-meta-instagram.sh`). diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml index 006fcda7e..65e1b7268 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-meta is a Matrix <-> Facebook/Messenger/Instagram bridge diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/install.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/install.yml index 3debb493e..4f3749c1e 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/install.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/main.yml index 0acc399f0..f06937433 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/uninstall.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/uninstall.yml index 991f47b40..794607e04 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of mautrix-meta-instagram service diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml index 212e261b8..833106582 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-meta-instagram settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2.license new file mode 100644 index 000000000..dfee73659 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/labels.j2 index 3648706cb..de8156bfe 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_meta_instagram_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2.license b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/systemd/matrix-mautrix-meta.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 51671926c03e2fe4d1bf5592da7376f1c088eb4c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 16:04:43 +0900 Subject: [PATCH 833/952] Add license information to files for matrix-bridge-mautrix-meta-messenger Signed-off-by: Suguru Hirahara --- .../configuring-playbook-bridge-mautrix-meta-messenger.md | 8 ++++++++ .../defaults/main.yml | 7 +++++++ .../tasks/install.yml | 5 +++++ .../matrix-bridge-mautrix-meta-messenger/tasks/main.yml | 4 ++++ .../tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/config.yaml.j2.license | 5 +++++ .../templates/labels.j2 | 6 ++++++ .../systemd/matrix-mautrix-meta.service.j2.license | 3 +++ 9 files changed, 46 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 51b1a40ca..27f640bba 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -1,3 +1,11 @@ + + # Setting up Messenger bridging via Mautrix Meta (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml index d6f5debcb..ae26f7c1f 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-meta is a Matrix <-> Facebook/Messenger/Instagram bridge diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/install.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/install.yml index 438682d2b..ef09d425b 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/install.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/main.yml index 5e5a7bebd..c77b53fa0 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/uninstall.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/uninstall.yml index 22040c2df..7ec36ad14 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of mautrix-meta-messenger service diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml index 2d69f924e..3300a54a0 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-meta-messenger settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2.license new file mode 100644 index 000000000..dfee73659 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/labels.j2 index 79e1fc743..1c5b0a6e0 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_meta_messenger_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2.license b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/systemd/matrix-mautrix-meta.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 751511139c13bd6ffdd01ed9af8f8c525bc795fe Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 20:54:22 +0900 Subject: [PATCH 834/952] Add license information to files for matrix-bridge-mautrix-signal Signed-off-by: Suguru Hirahara --- ...configuring-playbook-bridge-mautrix-signal.md | 16 ++++++++++++++++ .../defaults/main.yml | 16 ++++++++++++++++ .../matrix-bridge-mautrix-signal/tasks/main.yml | 8 ++++++++ .../tasks/remove_legacy.yml | 4 ++++ .../tasks/setup_install.yml | 12 ++++++++++++ .../tasks/setup_uninstall.yml | 8 ++++++++ .../tasks/validate_config.yml | 7 +++++++ .../templates/config.yaml.j2.license | 10 ++++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-signal.service.j2.license | 5 +++++ 10 files changed, 92 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md index d156c7b0a..ce94e6a00 100644 --- a/docs/configuring-playbook-bridge-mautrix-signal.md +++ b/docs/configuring-playbook-bridge-mautrix-signal.md @@ -1,3 +1,19 @@ + + # Setting up Mautrix Signal bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml index acd545817..3ac88352b 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml @@ -1,3 +1,19 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Sabine Laszakovits +# SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Wolfgang Winter +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Matthew Cengia +# SPDX-FileCopyrightText: 2023 - 2024 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 Yousef Amar +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-signal is a Matrix <-> Signal bridge # Project source code URL: https://github.com/mautrix/signal diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/main.yml index ded64b60c..60266ba91 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/remove_legacy.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/remove_legacy.yml index d65b2d14d..f566606fc 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/remove_legacy.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/remove_legacy.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Signal daemon service diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_install.yml index ca6568c8e..55bcb2cb4 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_install.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Sabine Laszakovits +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_uninstall.yml index 4a76bf141..79e3f8249 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/setup_uninstall.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Sabine Laszakovits +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-signal service diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml index a3059ef83..eeb6d5ea2 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Sabine Laszakovits +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-signal settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2.license new file mode 100644 index 000000000..7fa4396c7 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2.license @@ -0,0 +1,10 @@ +SPDX-FileCopyrightText: 2020 - 2021 Sabine Laszakovits +SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 Wolfgang Winter +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2023 - 2024 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2023 Adrien le Maire + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-signal/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-signal/templates/labels.j2 index fb912080a..334ca6fbc 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-signal/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_signal_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2.license b/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2.license new file mode 100644 index 000000000..1c3358e43 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty + +SPDX-License-Identifier: AGPL-3.0-or-later From 8b784735d3c85c3f9e4686442162d37d6c490609 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 20:54:46 +0900 Subject: [PATCH 835/952] Add license information to files for matrix-bridge-mautrix-slack Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-slack.md | 9 +++++++++ .../custom/matrix-bridge-mautrix-slack/defaults/main.yml | 8 ++++++++ roles/custom/matrix-bridge-mautrix-slack/tasks/main.yml | 5 +++++ .../matrix-bridge-mautrix-slack/tasks/setup_install.yml | 6 ++++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 5 +++++ .../systemd/matrix-mautrix-slack.service.j2.license | 4 ++++ 8 files changed, 46 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md index 6ead5487d..27aa5e12f 100644 --- a/docs/configuring-playbook-bridge-mautrix-slack.md +++ b/docs/configuring-playbook-bridge-mautrix-slack.md @@ -1,3 +1,12 @@ + + # Setting up Mautrix Slack bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml index 9489385e7..da778c2e2 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-slack is a Matrix <-> Slack bridge # Project source code URL: https://github.com/mautrix/slack diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/main.yml index b7a2199d7..9112981f2 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_install.yml index be5e11d80..c5266dfff 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_uninstall.yml index 19350b443..7361983d2 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-slack service diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml index 9a6e4a845..0f085735f 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-slack settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2.license new file mode 100644 index 000000000..21834835b --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-slack/templates/config.yaml.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2023 Shaleen Jain +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2.license b/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2.license new file mode 100644 index 000000000..1792ce657 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-slack/templates/systemd/matrix-mautrix-slack.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman + +SPDX-License-Identifier: AGPL-3.0-or-later From 0810054b78ee3c93deacefdef0e6ca325c975f39 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 21:05:02 +0900 Subject: [PATCH 836/952] Add license information to files for matrix-bridge-mautrix-telegram Signed-off-by: Suguru Hirahara --- ...figuring-playbook-bridge-mautrix-telegram.md | 13 +++++++++++++ .../defaults/main.yml | 16 ++++++++++++++++ .../tasks/main.yml | 6 ++++++ .../tasks/setup_install.yml | 17 +++++++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2.license | 11 +++++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-telegram.service.j2.license | 9 +++++++++ 9 files changed, 89 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md index 77f92a1dc..e15fa2d38 100644 --- a/docs/configuring-playbook-bridge-mautrix-telegram.md +++ b/docs/configuring-playbook-bridge-mautrix-telegram.md @@ -1,3 +1,16 @@ + + # Setting up Mautrix Telegram bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml index 01917528f..f941b7c59 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml @@ -1,3 +1,19 @@ +# SPDX-FileCopyrightText: 2019 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Johanna Dorothea Reichmann +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Olivér Falvai +# SPDX-FileCopyrightText: 2022 Vincent Post +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Pierre 'McFly' Marty +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-telegram is a Matrix <-> Telegram bridge diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/main.yml index 9fb6fb48f..fab0c1657 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml index 4c9aa8558..f45cd306f 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_install.yml @@ -1,3 +1,20 @@ +# SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2018 Hugues Morisset +# SPDX-FileCopyrightText: 2019 Aaron Raimist +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jan Christian Grünhage +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_uninstall.yml index ebb7e5db2..cbde3ff57 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-telegram service diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml index faaa37f6e..08ce0d3dc 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-telegram settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2.license new file mode 100644 index 000000000..ded8b03d5 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2.license @@ -0,0 +1,11 @@ +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Vincent Post +SPDX-FileCopyrightText: 2024 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-telegram/templates/labels.j2 index 494a45bdc..04021d807 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_telegram_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2.license b/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2.license new file mode 100644 index 000000000..575ca9abb --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/systemd/matrix-mautrix-telegram.service.j2.license @@ -0,0 +1,9 @@ +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2022 László Várady + +SPDX-License-Identifier: AGPL-3.0-or-later From 6fd48fcf9085c0ffab1ac720335d1c99e41e1486 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 21:05:12 +0900 Subject: [PATCH 837/952] Add license information to files for matrix-bridge-mautrix-twitter Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-twitter.md | 9 +++++++++ .../matrix-bridge-mautrix-twitter/defaults/main.yml | 13 +++++++++++++ .../matrix-bridge-mautrix-twitter/tasks/main.yml | 7 +++++++ .../tasks/setup_install.yml | 10 ++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.yaml.j2.license | 9 +++++++++ .../templates/labels.j2 | 6 ++++++ .../matrix-mautrix-twitter.service.j2.license | 4 ++++ 9 files changed, 70 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md index b24264a6c..ff8eb8f1f 100644 --- a/docs/configuring-playbook-bridge-mautrix-twitter.md +++ b/docs/configuring-playbook-bridge-mautrix-twitter.md @@ -1,3 +1,12 @@ + + # Setting up Mautrix Twitter bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml index 449d71eb3..c6e6d5e72 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml @@ -1,3 +1,16 @@ +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Matthew Cengia +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-twitter is a Matrix <-> Twitter bridge # Project source code URL: https://github.com/mautrix/twitter diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/main.yml index bb5a3a32e..39aff219b 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 Matthew Cengia +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_install.yml index f89ef1994..4e5b1d149 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Matthew Cengia +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_uninstall.yml index 2a73e4818..be45fe4ac 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Matthew Cengia +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-twitter service diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml index 0e33dcae8..e97779600 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 Matthew Cengia +# SPDX-FileCopyrightText: 2021 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-twitter settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2.license new file mode 100644 index 000000000..1cdaa53c0 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2.license @@ -0,0 +1,9 @@ +SPDX-FileCopyrightText: 2021 Matthew Cengia +SPDX-FileCopyrightText: 2021 Shreyas Ajjarapu +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2023 Adrien le Maire + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-twitter/templates/labels.j2 index e54502e74..fbf530be4 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_twitter_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2.license b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2.license new file mode 100644 index 000000000..e0357d6e9 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 Matthew Cengia + +SPDX-License-Identifier: AGPL-3.0-or-later From 06340e423b105e12c267c57b682b238fa1ebd5ff Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 21:05:18 +0900 Subject: [PATCH 838/952] Add license information to files for matrix-bridge-mautrix-whatsapp Signed-off-by: Suguru Hirahara --- ...guring-playbook-bridge-mautrix-whatsapp.md | 13 +++++++++++++ .../defaults/main.yml | 19 +++++++++++++++++++ .../tasks/main.yml | 7 +++++++ .../tasks/setup_install.yml | 17 +++++++++++++++++ .../tasks/setup_uninstall.yml | 6 ++++++ .../tasks/validate_config.yml | 7 +++++++ .../templates/config.yaml.j2.license | 13 +++++++++++++ .../templates/labels.j2 | 6 ++++++ ...matrix-mautrix-whatsapp.service.j2.license | 8 ++++++++ 9 files changed, 96 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md index b9d23652e..a00f41155 100644 --- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md +++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md @@ -1,3 +1,16 @@ + + # Setting up Mautrix Whatsapp bridging (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml index 5f3d36ee4..a183d2526 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml @@ -1,3 +1,22 @@ +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Julian Foad +# SPDX-FileCopyrightText: 2019 Thomas Kuehne +# SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Arthur Brugière +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Petteri Pucilowski +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# SPDX-FileCopyrightText: 2023 James Collier +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +# SPDX-FileCopyrightText: 2024 Nikolai Raitsev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-whatsapp is a Matrix <-> Whatsapp bridge # Project source code URL: https://github.com/mautrix/whatsapp diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/main.yml index c7de3e189..4fb583f66 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Thomas Kuehne +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Adrien le Maire +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_install.yml index fd2c1a1ed..ecafc5a32 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_install.yml @@ -1,3 +1,20 @@ +# SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2018 Hugues Morisset +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jan Christian Grünhage +# SPDX-FileCopyrightText: 2019 Thomas Kuehne +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Stuart Mumford +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_uninstall.yml index 98607b945..9a0beafd5 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-whatsapp service diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml index 21cd9fc09..e321aa414 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 Thomas Kuehne +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required mautrix-whatsapp settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2.license new file mode 100644 index 000000000..00e16d9b7 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2.license @@ -0,0 +1,13 @@ +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Thomas Kuehne +SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2023 Adrien le Maire +SPDX-FileCopyrightText: 2023 James Collier +SPDX-FileCopyrightText: 2024 Nikolai Raitsev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/labels.j2 index 23f94361e..74bd55954 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_whatsapp_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2.license b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2.license new file mode 100644 index 000000000..6a14dbaad --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Thomas Kuehne +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Scott Crossen + +SPDX-License-Identifier: AGPL-3.0-or-later From 29b6a3a9733845741616549d44cb42aecf64dc5f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 1 Mar 2025 21:06:48 +0900 Subject: [PATCH 839/952] Add license information to files for matrix-bridge-mautrix-wsproxy Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-wsproxy.md | 8 ++++++++ .../matrix-bridge-mautrix-wsproxy/defaults/main.yml | 7 +++++++ roles/custom/matrix-bridge-mautrix-wsproxy/tasks/main.yml | 5 +++++ .../matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml | 7 +++++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../templates/config.yaml.j2 | 6 ++++++ .../templates/syncproxy-env.j2 | 7 +++++++ .../matrix-mautrix-wsproxy-syncproxy.service.j2.license | 4 ++++ .../systemd/matrix-mautrix-wsproxy.service.j2.license | 4 ++++ .../templates/wsproxy-labels.j2 | 6 ++++++ 11 files changed, 63 insertions(+) create mode 100644 roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2.license create mode 100644 roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2.license diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md index b761e71d9..25fbb18dd 100644 --- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md +++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md @@ -1,3 +1,11 @@ + + # Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional) Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml index 36bd8dc12..b55933180 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # mautrix-wsproxy is a Matrix <-> websocket bridge # See: https://github.com/mautrix/wsproxy diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/main.yml index 77ba520f4..dd2cee331 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml index 59744ab48..9685df0e0 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # If the matrix-synapse role is not used, `matrix_synapse_role_executed` won't exist. diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_uninstall.yml index c39fd29f4..0326fcb96 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-mautrix-wsproxy service diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/validate_config.yml index 6a7012385..244da474f 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required settings not defined diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/config.yaml.j2 index 2c7932614..b0eae9f68 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/config.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 Johan Swetzén + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + listen_address: 0.0.0.0:29331 appservices: - id: androidsms diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/syncproxy-env.j2 b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/syncproxy-env.j2 index 0ce02496d..45ff0d9b6 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/syncproxy-env.j2 +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/syncproxy-env.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Johan Swetzén +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + DATABASE_URL={{ matrix_mautrix_signal_wsproxy_syncproxy_connection_string }} HOMESERVER_URL={{ matrix_mautrix_wsproxy_syncproxy_homeserver_url }} SHARED_SECRET={{ matrix_mautrix_wsproxy_syncproxy_shared_secret }} diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2.license b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2.license new file mode 100644 index 000000000..bf57ad87b --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy-syncproxy.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Johan Swetzén + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2.license b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2.license new file mode 100644 index 000000000..3cc582ba8 --- /dev/null +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/systemd/matrix-mautrix-wsproxy.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Johan Swetzén + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/wsproxy-labels.j2 b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/wsproxy-labels.j2 index f16a631e8..06a879b9c 100644 --- a/roles/custom/matrix-bridge-mautrix-wsproxy/templates/wsproxy-labels.j2 +++ b/roles/custom/matrix-bridge-mautrix-wsproxy/templates/wsproxy-labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 Johan Swetzén + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_mautrix_wsproxy_container_labels_traefik_enabled %} traefik.enable=true From 76326e3c57e9be439a9847d7d3dd387be36db699 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Mar 2025 01:04:48 +0900 Subject: [PATCH 840/952] Add license information to files in bin/ Signed-off-by: Suguru Hirahara --- bin/ansible-all-hosts.sh | 6 ++++++ bin/rebuild-mautrix-meta-instagram.sh | 5 +++++ 2 files changed, 11 insertions(+) diff --git a/bin/ansible-all-hosts.sh b/bin/ansible-all-hosts.sh index c4b903162..7b4ba3248 100755 --- a/bin/ansible-all-hosts.sh +++ b/bin/ansible-all-hosts.sh @@ -1,4 +1,10 @@ #!/usr/bin/env bash + +# SPDX-FileCopyrightText: 2022 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # # Run the playbook on multiple hosts with different credentials with this script # It defaults to ansible tags "setup-all,start". You can pass alternative tags diff --git a/bin/rebuild-mautrix-meta-instagram.sh b/bin/rebuild-mautrix-meta-instagram.sh index d637168bd..8c4a01ec4 100644 --- a/bin/rebuild-mautrix-meta-instagram.sh +++ b/bin/rebuild-mautrix-meta-instagram.sh @@ -1,4 +1,9 @@ #!/bin/bash + +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + set -euxo pipefail # This script rebuilds the mautrix-meta-instagram Ansible role, using the mautrix-meta-messenger role as a source. From 37f69e92d5f6c6cc30526b094689f76ca10b5c80 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Mar 2025 01:14:30 +0900 Subject: [PATCH 841/952] Add license information to files in examples/reverse-proxies/ Signed-off-by: Suguru Hirahara --- examples/reverse-proxies/README.md | 6 ++++++ examples/reverse-proxies/apache/README.md | 8 ++++++++ .../reverse-proxies/apache/matrix-client-element.conf | 5 +++++ examples/reverse-proxies/apache/matrix-domain.conf | 6 ++++++ examples/reverse-proxies/caddy2-in-container/Caddyfile | 6 ++++++ examples/reverse-proxies/caddy2-in-container/README.md | 7 +++++++ .../caddy2-in-container/docker-compose.yaml | 5 +++++ examples/reverse-proxies/caddy2/Caddyfile | 9 +++++++++ examples/reverse-proxies/caddy2/README.md | 10 ++++++++++ examples/reverse-proxies/haproxy/README.md | 8 ++++++++ examples/reverse-proxies/haproxy/haproxy.cfg | 5 +++++ examples/reverse-proxies/nginx-proxy-manager/README.md | 9 +++++++++ examples/reverse-proxies/nginx/README.md | 10 ++++++++++ examples/reverse-proxies/nginx/matrix.conf | 6 ++++++ 14 files changed, 100 insertions(+) diff --git a/examples/reverse-proxies/README.md b/examples/reverse-proxies/README.md index 91e10d5f6..3f8f12868 100644 --- a/examples/reverse-proxies/README.md +++ b/examples/reverse-proxies/README.md @@ -1,3 +1,9 @@ + + ## Using other reverse-proxies for fronting the integrated Traefik reverse-proxy This directory contains sample configuration for various webservers, showing you how to put these reverse-proxies in front of the integrated Traefik reverse-proxy used by the playbook. diff --git a/examples/reverse-proxies/apache/README.md b/examples/reverse-proxies/apache/README.md index b4608c87c..89b6fde58 100644 --- a/examples/reverse-proxies/apache/README.md +++ b/examples/reverse-proxies/apache/README.md @@ -1,3 +1,11 @@ + + # Apache reverse-proxy This directory contains sample files that show you how to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with your Apache reverse-proxy. diff --git a/examples/reverse-proxies/apache/matrix-client-element.conf b/examples/reverse-proxies/apache/matrix-client-element.conf index d4321c2bd..d3f281856 100644 --- a/examples/reverse-proxies/apache/matrix-client-element.conf +++ b/examples/reverse-proxies/apache/matrix-client-element.conf @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # This is a sample file demonstrating how to set up reverse-proxy for element.example.com. # If you're not using Element Web (`matrix_client_element_enabled: false`), you won't need this. diff --git a/examples/reverse-proxies/apache/matrix-domain.conf b/examples/reverse-proxies/apache/matrix-domain.conf index 18aaabd25..cce7723b0 100644 --- a/examples/reverse-proxies/apache/matrix-domain.conf +++ b/examples/reverse-proxies/apache/matrix-domain.conf @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # This is a sample file demonstrating how to set up reverse-proxy for matrix.example.com diff --git a/examples/reverse-proxies/caddy2-in-container/Caddyfile b/examples/reverse-proxies/caddy2-in-container/Caddyfile index 0a3d1df07..d5611c06d 100644 --- a/examples/reverse-proxies/caddy2-in-container/Caddyfile +++ b/examples/reverse-proxies/caddy2-in-container/Caddyfile @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + matrix.example.com { handle { diff --git a/examples/reverse-proxies/caddy2-in-container/README.md b/examples/reverse-proxies/caddy2-in-container/README.md index 3a87bf234..cef786aed 100644 --- a/examples/reverse-proxies/caddy2-in-container/README.md +++ b/examples/reverse-proxies/caddy2-in-container/README.md @@ -1,3 +1,10 @@ + + # Caddy reverse-proxy fronting the playbook's integrated Traefik reverse-proxy This directory contains a sample config that shows you how to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with your own **containerized** [Caddy](https://caddyserver.com/) reverse-proxy. If you have a server with a Caddy container already serving several applications and you want to install Matrix on it (with no changes to existing traffic routing), then this guide is for you. diff --git a/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml b/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml index 49671e7ac..c6b1889c7 100644 --- a/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml +++ b/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- version: "3.9" diff --git a/examples/reverse-proxies/caddy2/Caddyfile b/examples/reverse-proxies/caddy2/Caddyfile index c63b794ca..bf0a2b425 100644 --- a/examples/reverse-proxies/caddy2/Caddyfile +++ b/examples/reverse-proxies/caddy2/Caddyfile @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2020 - 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Olaf Schoenwald +# SPDX-FileCopyrightText: 2020 Panagiotis Vasilopoulos +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 François Darveau +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + matrix.example.com { handle { diff --git a/examples/reverse-proxies/caddy2/README.md b/examples/reverse-proxies/caddy2/README.md index dcc1538af..0da1fe3e4 100644 --- a/examples/reverse-proxies/caddy2/README.md +++ b/examples/reverse-proxies/caddy2/README.md @@ -1,3 +1,13 @@ + + # Caddy reverse-proxy fronting the playbook's integrated Traefik reverse-proxy This directory contains a sample config that shows you how to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with your own [Caddy](https://caddyserver.com/) reverse-proxy. diff --git a/examples/reverse-proxies/haproxy/README.md b/examples/reverse-proxies/haproxy/README.md index 086e49aa5..b2b389536 100644 --- a/examples/reverse-proxies/haproxy/README.md +++ b/examples/reverse-proxies/haproxy/README.md @@ -1,3 +1,11 @@ + + # HAproxy reverse-proxy This directory contains sample files that show you how to do reverse-proxying using HAproxy. diff --git a/examples/reverse-proxies/haproxy/haproxy.cfg b/examples/reverse-proxies/haproxy/haproxy.cfg index 57c562bdd..633922065 100644 --- a/examples/reverse-proxies/haproxy/haproxy.cfg +++ b/examples/reverse-proxies/haproxy/haproxy.cfg @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + global log /dev/log local0 log /dev/log local1 notice diff --git a/examples/reverse-proxies/nginx-proxy-manager/README.md b/examples/reverse-proxies/nginx-proxy-manager/README.md index e90289e9c..dad498435 100644 --- a/examples/reverse-proxies/nginx-proxy-manager/README.md +++ b/examples/reverse-proxies/nginx-proxy-manager/README.md @@ -1,3 +1,12 @@ + + # Nginx Proxy Manager fronting the playbook's integrated Traefik reverse-proxy Similar to standard nginx, [Nginx Proxy Manager](https://nginxproxymanager.com/) provides nginx capabilities but inside a pre-built Docker container. With the ability for managing proxy hosts and automatic SSL certificates via a simple web interface. diff --git a/examples/reverse-proxies/nginx/README.md b/examples/reverse-proxies/nginx/README.md index 1fe76340d..9ca86c86a 100644 --- a/examples/reverse-proxies/nginx/README.md +++ b/examples/reverse-proxies/nginx/README.md @@ -1,3 +1,13 @@ + + # Nginx reverse-proxy fronting the playbook's integrated Traefik reverse-proxy This directory contains a sample config that shows you how to use the [nginx](https://nginx.org/) webserver to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with another reverse-proxy. diff --git a/examples/reverse-proxies/nginx/matrix.conf b/examples/reverse-proxies/nginx/matrix.conf index 7d2459543..8e6c89711 100644 --- a/examples/reverse-proxies/nginx/matrix.conf +++ b/examples/reverse-proxies/nginx/matrix.conf @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Jost Alemann +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + server { # TODO: once per IP and port you should add `reuseport`, if you don't have that in any other nginx config file, add it here by uncommenting the lines below and commenting the one after with `quic` but without `reuseport` #listen 443 quic reuseport; From cd5cd60e8ccea70ff2bb48cce6c9dac98113196e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Mar 2025 01:23:31 +0900 Subject: [PATCH 842/952] Update REUSE.toml: add files which cannot be copyrighted Signed-off-by: Suguru Hirahara --- REUSE.toml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/REUSE.toml b/REUSE.toml index 849d77627..574d76a82 100644 --- a/REUSE.toml +++ b/REUSE.toml @@ -8,9 +8,18 @@ version = 1 [[annotations]] path = [ ".github/renovate.json", + "collections/requirements.yml", "i18n/.gitignore", "i18n/requirements.txt", - "i18n/PUBLISHED_LANGUAGES" + "i18n/PUBLISHED_LANGUAGES", + ".editorconfig", + ".envrc", + ".gitattributes", + ".gitignore", + ".yamllint", + "flake.lock", + "flake.nix", + "requirements.yml" ] SPDX-FileCopyrightText = "NONE" SPDX-License-Identifier = "CC0-1.0" From da30db76d641df8a3a0291dfdb210808024522e6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Mar 2025 14:16:44 +0900 Subject: [PATCH 843/952] Update docs: remove abbreviations for Matrix User Verification Service from the tables As there are not other instances where an abbreviation is written along with the service's full name, it is sensible to remove them from there. Signed-off-by: Suguru Hirahara --- README.md | 2 +- docs/container-images.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f91e24b3b..ca51c76ac 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ Extend and modify how users are authenticated on your homeserver. | [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced) | ❌ | LDAP Auth password provider module | [Link](docs/configuring-playbook-ldap-auth.md) | | [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced) | ❌ | Proxy that handles Matrix registration requests and forwards them to LDAP | [Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md) | | [matrix-registration](https://github.com/ZerataX/matrix-registration) | ❌ | Simple python application to have a token based Matrix registration | [Link](docs/configuring-playbook-matrix-registration.md) | -| [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS) | ❌ | Service to verify details of a user based on an Open ID token | [Link](docs/configuring-playbook-user-verification-service.md) | +| [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) | ❌ | Service to verify details of a user based on an Open ID token | [Link](docs/configuring-playbook-user-verification-service.md) | | [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced) | ❌ | Spam checker module | [Link](docs/configuring-playbook-synapse-simple-antispam.md) | ### File Storage diff --git a/docs/container-images.md b/docs/container-images.md index d9bb657f9..4212d7674 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -66,7 +66,7 @@ Extend and modify how users are authenticated on your homeserver. | [matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced) | (N/A) | ❌ | LDAP Auth password provider module | | [matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) | [activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry) | ❌ | Proxy that handles Matrix registration requests and forwards them to LDAP | | [matrix-registration](configuring-playbook-matrix-registration.md) | [zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/) | ❌ | Simple python application to have a token based Matrix registration | -| [Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS) | [matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service) | ❌ | Service to verify details of a user based on an Open ID token | +| [Matrix User Verification Service](configuring-playbook-user-verification-service.md) | [matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service) | ❌ | Service to verify details of a user based on an Open ID token | | [synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced) | (N/A) | ❌ | Spam checker module | ## File Storage From 67b106c7c2213459a7cd05fa223a1e90d1d9d270 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 2 Mar 2025 14:20:45 +0900 Subject: [PATCH 844/952] Add mautrix-bluesky to a table on docs/container-images.md Signed-off-by: Suguru Hirahara --- docs/container-images.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/container-images.md b/docs/container-images.md index 4212d7674..844cce810 100644 --- a/docs/container-images.md +++ b/docs/container-images.md @@ -85,6 +85,7 @@ Bridges can be used to connect your Matrix installation with third-party communi | Service | Container image | Default? | Description | | ------- | --------------- | -------- | ----------- | +| [mautrix-bluesky](configuring-playbook-bridge-mautrix-bluesky.md) | [mautrix/bluesky](https://mau.dev/mautrix/bluesky/container_registry) | ❌ | Bridge to [Bluesky](https://bsky.social/about) | | [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) | [mautrix/discord](https://mau.dev/mautrix/discord/container_registry) | ❌ | Bridge to [Discord](https://discord.com/) | | [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) | [mautrix/slack](https://mau.dev/mautrix/slack/container_registry) | ❌ | Bridge to [Slack](https://slack.com/) | | [mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md) | [mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry) | ❌ | Bridge to [Telegram](https://telegram.org/) | From 27c3be55b074992a27bf7f25bca17cc9166a202b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:17:08 +0900 Subject: [PATCH 845/952] Add license information to files for matrix-synapse-admin Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-admin.md | 12 ++++++++++++ roles/custom/matrix-synapse-admin/defaults/main.yml | 11 +++++++++++ roles/custom/matrix-synapse-admin/tasks/main.yml | 5 +++++ .../matrix-synapse-admin/tasks/setup_install.yml | 11 +++++++++++ .../matrix-synapse-admin/tasks/setup_uninstall.yml | 4 ++++ .../matrix-synapse-admin/tasks/validate_config.yml | 5 +++++ .../custom/matrix-synapse-admin/templates/labels.j2 | 7 +++++++ .../systemd/matrix-synapse-admin.service.j2.license | 4 ++++ 8 files changed, 59 insertions(+) create mode 100644 roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2.license diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md index bd07a8bb9..4c992e09b 100644 --- a/docs/configuring-playbook-synapse-admin.md +++ b/docs/configuring-playbook-synapse-admin.md @@ -1,3 +1,15 @@ + + # Setting up Synapse Admin (optional) The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you. diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 09e13dd9e..4a3028839 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Dennis Ciba +# SPDX-FileCopyrightText: 2021 - 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-synapse-admin is a web UI for managing the Synapse Matrix server # Project source code URL: https://github.com/Awesome-Technologies/synapse-admin diff --git a/roles/custom/matrix-synapse-admin/tasks/main.yml b/roles/custom/matrix-synapse-admin/tasks/main.yml index da3f2b56d..c66e9998e 100644 --- a/roles/custom/matrix-synapse-admin/tasks/main.yml +++ b/roles/custom/matrix-synapse-admin/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse-admin/tasks/setup_install.yml b/roles/custom/matrix-synapse-admin/tasks/setup_install.yml index 2dcdd0cfb..1c3fb8673 100644 --- a/roles/custom/matrix-synapse-admin/tasks/setup_install.yml +++ b/roles/custom/matrix-synapse-admin/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Dennis Ciba +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-synapse-admin paths exists diff --git a/roles/custom/matrix-synapse-admin/tasks/setup_uninstall.yml b/roles/custom/matrix-synapse-admin/tasks/setup_uninstall.yml index 69820a005..5436bc82b 100644 --- a/roles/custom/matrix-synapse-admin/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-synapse-admin/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-synapse-admin service diff --git a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml index 1b9856d51..ceb7ddec2 100644 --- a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed matrix-synapse-admin settings diff --git a/roles/custom/matrix-synapse-admin/templates/labels.j2 b/roles/custom/matrix-synapse-admin/templates/labels.j2 index eeb29756e..bab69cec3 100644 --- a/roles/custom/matrix-synapse-admin/templates/labels.j2 +++ b/roles/custom/matrix-synapse-admin/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2025 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_synapse_admin_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2.license b/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2.license new file mode 100644 index 000000000..9b305e18b --- /dev/null +++ b/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Dan Arnfield + +SPDX-License-Identifier: AGPL-3.0-or-later From a039174f968e68d083583743b069f8f410d28d4c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:17:47 +0900 Subject: [PATCH 846/952] Add license information to files for matrix-synapse-auto-compressor Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-auto-compressor.md | 8 ++++++++ .../matrix-synapse-auto-compressor/defaults/main.yml | 7 +++++++ .../matrix-synapse-auto-compressor/tasks/install.yml | 6 ++++++ .../custom/matrix-synapse-auto-compressor/tasks/main.yml | 5 +++++ .../matrix-synapse-auto-compressor/tasks/uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 5 +++++ .../matrix-synapse-auto-compressor/templates/env.j2 | 7 +++++++ .../matrix-synapse-auto-compressor-fix.sh.j2.license | 3 +++ .../matrix-synapse-auto-compressor.service.j2.license | 4 ++++ .../templates/matrix-synapse-auto-compressor.timer.j2 | 7 +++++++ 10 files changed, 56 insertions(+) create mode 100644 roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor-fix.sh.j2.license create mode 100644 roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2.license diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md index 988be65c3..4934e65a0 100644 --- a/docs/configuring-playbook-synapse-auto-compressor.md +++ b/docs/configuring-playbook-synapse-auto-compressor.md @@ -1,3 +1,11 @@ + + # Setting up synapse-auto-compressor (optional) The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you. diff --git a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml index f5d02cd17..78a07a9ed 100644 --- a/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml +++ b/roles/custom/matrix-synapse-auto-compressor/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # synapse_auto_compressor tool diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/install.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/install.yml index 2f51b5a0b..3e69d9f5d 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/install.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure synapse-auto-compressor paths exist diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/main.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/main.yml index 5993e4f9b..746896ab3 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/main.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/uninstall.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/uninstall.yml index 075f3c101..d29e40bc3 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/uninstall.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-synapse-auto-compressor service ansible.builtin.stat: diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml index 9441eea5f..411508c80 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed matrix-synapse-auto-compressor settings ansible.builtin.fail: diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/env.j2 b/roles/custom/matrix-synapse-auto-compressor/templates/env.j2 index 85f18066d..85b0d20cd 100644 --- a/roles/custom/matrix-synapse-auto-compressor/templates/env.j2 +++ b/roles/custom/matrix-synapse-auto-compressor/templates/env.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + POSTGRES_LOCATION={{ matrix_synapse_auto_compressor_environment_variable_postgres_location }} # PG-prefixed variables below are for the matrix-synapse-auto-compressor-fix.sh script diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor-fix.sh.j2.license b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor-fix.sh.j2.license new file mode 100644 index 000000000..b1840694f --- /dev/null +++ b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor-fix.sh.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Nikita Chernyi + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2.license b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2.license new file mode 100644 index 000000000..f86013a08 --- /dev/null +++ b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Nikita Chernyi +SPDX-FileCopyrightText: 2023 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 index 82c235c80..1bced0d46 100644 --- a/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 +++ b/roles/custom/matrix-synapse-auto-compressor/templates/matrix-synapse-auto-compressor.timer.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2023 Nikita Chernyi +SPDX-FileCopyrightText: 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + [Unit] Description=Synapse State Auto Compressor Timer From aae64ebde4f85f3dd42e047c1f685689e83ae06f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:18:04 +0900 Subject: [PATCH 847/952] Add license information to files for matrix-synapse-reverse-proxy-companion Signed-off-by: Suguru Hirahara --- .../defaults/main.yml | 10 ++++++++++ .../tasks/main.yml | 4 ++++ .../tasks/setup_install.yml | 5 +++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../templates/labels.j2 | 6 ++++++ ...rix-synapse-reverse-proxy-companion.conf.j2.license | 5 +++++ .../templates/nginx/conf.d/nginx-http.conf.j2.license | 3 +++ .../templates/nginx/nginx.conf.j2.license | 4 ++++ ...-synapse-reverse-proxy-companion.service.j2.license | 4 ++++ 10 files changed, 49 insertions(+) create mode 100644 roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2.license create mode 100644 roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/nginx-http.conf.j2.license create mode 100644 roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2.license create mode 100644 roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2.license diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml index 051684ef9..57b208d84 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Dan Arnfield +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Charles Wright +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Michael Hollister +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-synapse-reverse-proxy-companion is a role which brings up a containerized nginx webserver which helps with reverse-proxying to Synapse when workers are enabled. diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/main.yml index e4149cbb3..bd8c3f680 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/main.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_install.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_install.yml index edfa7c212..34ab589d8 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_install.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-synapse-reverse-proxy-companion paths exist diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_uninstall.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_uninstall.yml index 7b820b35b..ff0686345 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-synapse-reverse-proxy-companion service diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml index 4da323182..7a8ef3e29 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-synapse-reverse-proxy-companion settings not defined diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 index 5120b10e8..8b8945d2e 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_synapse_reverse_proxy_companion_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2.license b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2.license new file mode 100644 index 000000000..2124bb25d --- /dev/null +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Charles Wright +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/nginx-http.conf.j2.license b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/nginx-http.conf.j2.license new file mode 100644 index 000000000..7b1e56adc --- /dev/null +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/nginx-http.conf.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2.license b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2.license new file mode 100644 index 000000000..7f7a5e8fa --- /dev/null +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2.license b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2.license new file mode 100644 index 000000000..c3e289cc7 --- /dev/null +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/systemd/matrix-synapse-reverse-proxy-companion.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later From 2f2e551798653476873edada9fc703adff6bde5d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:18:26 +0900 Subject: [PATCH 848/952] Add license information to files for matrix-synapse-usage-exporter Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-usage-exporter.md | 8 ++++++++ .../matrix-synapse-usage-exporter/defaults/main.yml | 6 ++++++ roles/custom/matrix-synapse-usage-exporter/tasks/main.yml | 5 +++++ .../matrix-synapse-usage-exporter/tasks/setup_install.yml | 5 +++++ .../tasks/setup_uninstall.yml | 4 ++++ .../tasks/validate_config.yml | 4 ++++ .../custom/matrix-synapse-usage-exporter/templates/env.j2 | 6 ++++++ .../templates/grafana/synapse-usage-exporter.json.license | 3 +++ .../matrix-synapse-usage-exporter/templates/labels.j2 | 6 ++++++ .../matrix-synapse-usage-exporter.service.j2.license | 4 ++++ 10 files changed, 51 insertions(+) create mode 100644 roles/custom/matrix-synapse-usage-exporter/templates/grafana/synapse-usage-exporter.json.license create mode 100644 roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2.license diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md index 6c3e9629d..cb66cdffe 100644 --- a/docs/configuring-playbook-synapse-usage-exporter.md +++ b/docs/configuring-playbook-synapse-usage-exporter.md @@ -1,3 +1,11 @@ + + # Enabling synapse-usage-exporter for Synapse usage statistics (optional) The playbook can install and configure [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) for you. diff --git a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml index 25768f0e2..b4256d3bc 100644 --- a/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml +++ b/roles/custom/matrix-synapse-usage-exporter/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Michael Hollister +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Synapse Usage Exporter diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml index 22b9df8c4..892dfac01 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Michael Hollister +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/setup_install.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/setup_install.yml index 72cdbd37c..591e377e3 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/setup_install.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/setup_install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Michael Hollister +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure synapse-usage-exporter paths exist diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/setup_uninstall.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/setup_uninstall.yml index 1b1492bb4..bf085df0e 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Michael Hollister +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of synapse-usage-exporter service diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml index 5609ad241..3274e595a 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed matrix-synapse-usage-exporter settings diff --git a/roles/custom/matrix-synapse-usage-exporter/templates/env.j2 b/roles/custom/matrix-synapse-usage-exporter/templates/env.j2 index e3f1e814d..0420d358a 100644 --- a/roles/custom/matrix-synapse-usage-exporter/templates/env.j2 +++ b/roles/custom/matrix-synapse-usage-exporter/templates/env.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + PROMETHEUS_MULTIPROC_DIR=/tmp/prometheus WERKZEUG_LOG_LEVEL=INFO APP_LOG_LEVEL=INFO diff --git a/roles/custom/matrix-synapse-usage-exporter/templates/grafana/synapse-usage-exporter.json.license b/roles/custom/matrix-synapse-usage-exporter/templates/grafana/synapse-usage-exporter.json.license new file mode 100644 index 000000000..2265e3041 --- /dev/null +++ b/roles/custom/matrix-synapse-usage-exporter/templates/grafana/synapse-usage-exporter.json.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse-usage-exporter/templates/labels.j2 b/roles/custom/matrix-synapse-usage-exporter/templates/labels.j2 index 7811c3372..50c3ca82f 100755 --- a/roles/custom/matrix-synapse-usage-exporter/templates/labels.j2 +++ b/roles/custom/matrix-synapse-usage-exporter/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_synapse_usage_exporter_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2.license b/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2.license new file mode 100644 index 000000000..eceecc820 --- /dev/null +++ b/roles/custom/matrix-synapse-usage-exporter/templates/systemd/matrix-synapse-usage-exporter.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2024 Michael Hollister +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 621a41cbf7348e63a8ec9050ace4cb32db08ea96 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:47:55 +0900 Subject: [PATCH 849/952] Update docs/configuring-playbook-synapse-auto-accept-invite.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-auto-accept-invite.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-synapse-auto-accept-invite.md b/docs/configuring-playbook-synapse-auto-accept-invite.md index 52c1c46ae..f6f80120a 100644 --- a/docs/configuring-playbook-synapse-auto-accept-invite.md +++ b/docs/configuring-playbook-synapse-auto-accept-invite.md @@ -1,3 +1,11 @@ + + # Setting up Synapse Auto Invite Accept (optional) The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you. From 2c28a8c9bf1ddde9be4d89a5d875bea0990bc1cc Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:48:07 +0900 Subject: [PATCH 850/952] Update docs/configuring-playbook-synapse-s3-storage-provider.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-s3-storage-provider.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index efe3a5a82..eccd58c02 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -1,3 +1,12 @@ + + # Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional) 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. From e89a4708e7d1d898e1104cbe406951d7e93f98e1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 00:48:16 +0900 Subject: [PATCH 851/952] Update docs/configuring-playbook-synapse-simple-antispam.md: add the copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse-simple-antispam.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/configuring-playbook-synapse-simple-antispam.md b/docs/configuring-playbook-synapse-simple-antispam.md index 069b26d2f..35b106a60 100644 --- a/docs/configuring-playbook-synapse-simple-antispam.md +++ b/docs/configuring-playbook-synapse-simple-antispam.md @@ -1,3 +1,10 @@ + + # Setting up Synapse Simple Antispam (optional, advanced) The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you. From 06cafa6908a79ddd5366b0a85e21a65dad67425d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 12:13:29 +0900 Subject: [PATCH 852/952] Add license information to files for matrix-prometheus-services-connect Signed-off-by: Suguru Hirahara --- .../matrix-prometheus-services-connect/defaults/main.yml | 5 +++++ .../tasks/install_synapse_rules.yml | 4 ++++ .../custom/matrix-prometheus-services-connect/tasks/main.yml | 4 ++++ 3 files changed, 13 insertions(+) diff --git a/roles/custom/matrix-prometheus-services-connect/defaults/main.yml b/roles/custom/matrix-prometheus-services-connect/defaults/main.yml index f9d12e7f4..ccbaefdb8 100644 --- a/roles/custom/matrix-prometheus-services-connect/defaults/main.yml +++ b/roles/custom/matrix-prometheus-services-connect/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-prometheus-services-connect is a role which helps integrate diff --git a/roles/custom/matrix-prometheus-services-connect/tasks/install_synapse_rules.yml b/roles/custom/matrix-prometheus-services-connect/tasks/install_synapse_rules.yml index 78b218aca..76b2d9453 100644 --- a/roles/custom/matrix-prometheus-services-connect/tasks/install_synapse_rules.yml +++ b/roles/custom/matrix-prometheus-services-connect/tasks/install_synapse_rules.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Download synapse-v2.rules diff --git a/roles/custom/matrix-prometheus-services-connect/tasks/main.yml b/roles/custom/matrix-prometheus-services-connect/tasks/main.yml index f2c22b7f4..ef698e41e 100644 --- a/roles/custom/matrix-prometheus-services-connect/tasks/main.yml +++ b/roles/custom/matrix-prometheus-services-connect/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: From 1af310864c9a1af660106e38d507587e0378429f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 12:14:03 +0900 Subject: [PATCH 853/952] Add license information to files in matrix_playbook_migration/ Signed-off-by: Suguru Hirahara --- roles/custom/matrix_playbook_migration/defaults/main.yml | 5 +++++ .../tasks/cleanup_matrix_static_files_well_known.yml | 4 ++++ .../tasks/cleanup_usr_local_bin.yml | 6 ++++++ .../tasks/debian_docker_signedby_migration.yml | 4 ++++ .../debian_docker_trusted_gpg_d_migration_migration.yml | 4 ++++ .../tasks/devture_traefik_to_matrix_traefik.yml | 4 ++++ roles/custom/matrix_playbook_migration/tasks/main.yml | 4 ++++ .../tasks/migrate_matrix_mailer.yml | 4 ++++ .../tasks/uninstall_matrix_nginx_proxy.yml | 4 ++++ .../tasks/uninstall_matrix_ssl.yml | 5 +++++ .../matrix_playbook_migration/tasks/validate_config.yml | 6 ++++++ 11 files changed, 50 insertions(+) diff --git a/roles/custom/matrix_playbook_migration/defaults/main.yml b/roles/custom/matrix_playbook_migration/defaults/main.yml index 43628f1fb..2cac16e45 100644 --- a/roles/custom/matrix_playbook_migration/defaults/main.yml +++ b/roles/custom/matrix_playbook_migration/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Controls if (`matrix_prometheus_node_exporter` -> `prometheus_node_exporter`) validation will run. diff --git a/roles/custom/matrix_playbook_migration/tasks/cleanup_matrix_static_files_well_known.yml b/roles/custom/matrix_playbook_migration/tasks/cleanup_matrix_static_files_well_known.yml index 9e95826bd..7912d7eb4 100644 --- a/roles/custom/matrix_playbook_migration/tasks/cleanup_matrix_static_files_well_known.yml +++ b/roles/custom/matrix_playbook_migration/tasks/cleanup_matrix_static_files_well_known.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Files used to be installed by the `matrix-base` role into `/matrix/static-files/.well-known/*`. diff --git a/roles/custom/matrix_playbook_migration/tasks/cleanup_usr_local_bin.yml b/roles/custom/matrix_playbook_migration/tasks/cleanup_usr_local_bin.yml index 54e6f4646..f6c561aef 100644 --- a/roles/custom/matrix_playbook_migration/tasks/cleanup_usr_local_bin.yml +++ b/roles/custom/matrix_playbook_migration/tasks/cleanup_usr_local_bin.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Find leftover Matrix scripts in /usr/local/bin diff --git a/roles/custom/matrix_playbook_migration/tasks/debian_docker_signedby_migration.yml b/roles/custom/matrix_playbook_migration/tasks/debian_docker_signedby_migration.yml index ac1c5cd13..5948ff539 100644 --- a/roles/custom/matrix_playbook_migration/tasks/debian_docker_signedby_migration.yml +++ b/roles/custom/matrix_playbook_migration/tasks/debian_docker_signedby_migration.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Remove old Docker apt repository, potentially lacking signed-by option diff --git a/roles/custom/matrix_playbook_migration/tasks/debian_docker_trusted_gpg_d_migration_migration.yml b/roles/custom/matrix_playbook_migration/tasks/debian_docker_trusted_gpg_d_migration_migration.yml index 81f396603..fc15a4a85 100644 --- a/roles/custom/matrix_playbook_migration/tasks/debian_docker_trusted_gpg_d_migration_migration.yml +++ b/roles/custom/matrix_playbook_migration/tasks/debian_docker_trusted_gpg_d_migration_migration.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check if the Docker apt repository file exists diff --git a/roles/custom/matrix_playbook_migration/tasks/devture_traefik_to_matrix_traefik.yml b/roles/custom/matrix_playbook_migration/tasks/devture_traefik_to_matrix_traefik.yml index 0b299279f..61b815e61 100644 --- a/roles/custom/matrix_playbook_migration/tasks/devture_traefik_to_matrix_traefik.yml +++ b/roles/custom/matrix_playbook_migration/tasks/devture_traefik_to_matrix_traefik.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This migrates Traefik from the old path (`/devture-traefik`) to the new path (`/matrix/traefik`, controlled by `traefik_base_path`), diff --git a/roles/custom/matrix_playbook_migration/tasks/main.yml b/roles/custom/matrix_playbook_migration/tasks/main.yml index f72e2b03c..c11dbcb5b 100644 --- a/roles/custom/matrix_playbook_migration/tasks/main.yml +++ b/roles/custom/matrix_playbook_migration/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix_playbook_migration/tasks/migrate_matrix_mailer.yml b/roles/custom/matrix_playbook_migration/tasks/migrate_matrix_mailer.yml index e1785774f..dae519322 100644 --- a/roles/custom/matrix_playbook_migration/tasks/migrate_matrix_mailer.yml +++ b/roles/custom/matrix_playbook_migration/tasks/migrate_matrix_mailer.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This migrates the mailer from the old path (`/matrix/mailer`) to the new path (`/matrix/exim-relay`, controlled by `exim_relay_base_path`), diff --git a/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_nginx_proxy.yml b/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_nginx_proxy.yml index acfacddb0..76f7ac301 100644 --- a/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_nginx_proxy.yml +++ b/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_nginx_proxy.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-nginx-proxy service diff --git a/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_ssl.yml b/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_ssl.yml index ecfad1591..11b84bb47 100644 --- a/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_ssl.yml +++ b/roles/custom/matrix_playbook_migration/tasks/uninstall_matrix_ssl.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix SSL-related files are deleted diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 0043e8dd5..ecb36f762 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 - 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: (Deprecation) Catch and report renamed Matrix playbook settings From 85c93f85331b185c0c561d591f073fc3d96a364d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 12:14:23 +0900 Subject: [PATCH 854/952] Add license information to files for matrix-user-verification-service Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-user-verification-service.md | 7 +++++++ .../matrix-user-verification-service/defaults/main.yml | 7 +++++++ .../custom/matrix-user-verification-service/tasks/main.yml | 5 +++++ .../tasks/setup_install.yml | 6 ++++++ .../tasks/setup_uninstall.yml | 5 +++++ .../tasks/validate_config.yml | 5 +++++ .../matrix-user-verification-service/templates/.env.j2 | 7 ++++++- .../matrix-user-verification-service.service.j2.license | 4 ++++ 8 files changed, 45 insertions(+), 1 deletion(-) create mode 100644 roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2.license diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index 8e09d61ef..662f8408e 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -1,3 +1,10 @@ + + # Setting up Matrix User Verification Service (optional) The playbook can install and configure [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) for you. diff --git a/roles/custom/matrix-user-verification-service/defaults/main.yml b/roles/custom/matrix-user-verification-service/defaults/main.yml index abd1655c1..1bc8cf60f 100644 --- a/roles/custom/matrix-user-verification-service/defaults/main.yml +++ b/roles/custom/matrix-user-verification-service/defaults/main.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-user-verification-service - Service to verify details of a user based on an Open ID token diff --git a/roles/custom/matrix-user-verification-service/tasks/main.yml b/roles/custom/matrix-user-verification-service/tasks/main.yml index 1b65f86a6..7f7f8616e 100644 --- a/roles/custom/matrix-user-verification-service/tasks/main.yml +++ b/roles/custom/matrix-user-verification-service/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-user-verification-service/tasks/setup_install.yml b/roles/custom/matrix-user-verification-service/tasks/setup_install.yml index 8fa4b670e..a539168b5 100644 --- a/roles/custom/matrix-user-verification-service/tasks/setup_install.yml +++ b/roles/custom/matrix-user-verification-service/tasks/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: "Ensure Matrix User Verification Service paths exist" diff --git a/roles/custom/matrix-user-verification-service/tasks/setup_uninstall.yml b/roles/custom/matrix-user-verification-service/tasks/setup_uninstall.yml index b61f9cdd2..8ce0c0234 100644 --- a/roles/custom/matrix-user-verification-service/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-user-verification-service/tasks/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-user-verification-service service diff --git a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml index 309557c84..871a8f0e2 100644 --- a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml +++ b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Verify homeserver_url is not empty diff --git a/roles/custom/matrix-user-verification-service/templates/.env.j2 b/roles/custom/matrix-user-verification-service/templates/.env.j2 index 359eed2a1..e07870e02 100644 --- a/roles/custom/matrix-user-verification-service/templates/.env.j2 +++ b/roles/custom/matrix-user-verification-service/templates/.env.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + UVS_ACCESS_TOKEN={{ matrix_user_verification_service_uvs_access_token }} UVS_HOMESERVER_URL={{ matrix_user_verification_service_uvs_homeserver_url }} UVS_DISABLE_IP_BLACKLIST={{ matrix_user_verification_service_uvs_disable_ip_blacklist }} @@ -8,4 +14,3 @@ UVS_LOG_LEVEL={{ matrix_user_verification_service_uvs_log_level }} {% if matrix_user_verification_service_uvs_pin_openid_verify_server_name | bool %} UVS_OPENID_VERIFY_SERVER_NAME={{ matrix_user_verification_service_uvs_openid_verify_server_name }} {% endif %} - diff --git a/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2.license b/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2.license new file mode 100644 index 000000000..68dc46f44 --- /dev/null +++ b/roles/custom/matrix-user-verification-service/templates/systemd/matrix-user-verification-service.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later From 92adfb50e7b1ed5d83c37493f895d1cef57ba469 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 12:14:55 +0900 Subject: [PATCH 855/952] Add license information to some files on the top level directory Signed-off-by: Suguru Hirahara --- Makefile | 4 ++++ YEAR-IN-REVIEW.md | 7 +++++++ jitsi_jvb.yml | 7 +++++++ justfile | 6 ++++++ 4 files changed, 24 insertions(+) diff --git a/Makefile b/Makefile index 3379b8fff..9ac77bb07 100644 --- a/Makefile +++ b/Makefile @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + .PHONY: roles lint help: ## Show this help. diff --git a/YEAR-IN-REVIEW.md b/YEAR-IN-REVIEW.md index bac3d10ac..e66882873 100644 --- a/YEAR-IN-REVIEW.md +++ b/YEAR-IN-REVIEW.md @@ -1,3 +1,10 @@ + + # 2023 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. diff --git a/jitsi_jvb.yml b/jitsi_jvb.yml index 33786bebe..d57c15a97 100644 --- a/jitsi_jvb.yml +++ b/jitsi_jvb.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2022 Warren Bailey +# SPDX-FileCopyrightText: 2023 Antonis Christofides +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: "Set up additional Jitsi Videobridge (JVB) servers" hosts: "jitsi_jvb_servers" diff --git a/justfile b/justfile index ca57d6143..a2bab08f2 100644 --- a/justfile +++ b/justfile @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + # Shows help default: @{{ just_executable() }} --list --justfile {{ justfile() }} From 245900e32f1dd4a673cc4530855fc95cc55ad075 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 12:15:39 +0900 Subject: [PATCH 856/952] Update REUSE.toml Signed-off-by: Suguru Hirahara --- REUSE.toml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/REUSE.toml b/REUSE.toml index 574d76a82..0985a21af 100644 --- a/REUSE.toml +++ b/REUSE.toml @@ -12,11 +12,13 @@ path = [ "i18n/.gitignore", "i18n/requirements.txt", "i18n/PUBLISHED_LANGUAGES", + "roles/custom/**/*.repo", ".editorconfig", ".envrc", ".gitattributes", ".gitignore", ".yamllint", + "ansible.cfg", "flake.lock", "flake.nix", "requirements.yml" @@ -31,5 +33,5 @@ path = [ "i18n/**/*.pot" ] precedence = "aggregate" -SPDX-FileCopyrightText = "Slavi Pantaleev, MDAD community members" +SPDX-FileCopyrightText = "2024 - 2025 Slavi Pantaleev, MDAD project contributors" SPDX-License-Identifier = "AGPL-3.0-or-later" From 5ce83312822f77ded936e2a5b9d91c97b1eb318c Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 3 Mar 2025 03:28:32 +0000 Subject: [PATCH 857/952] Update dependency Sphinx to v8.2.3 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 747c42ffa..894bbe199 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -19,7 +19,7 @@ PyYAML==6.0.2 requests==2.32.3 setuptools==75.8.2 snowballstemmer==2.2.0 -Sphinx==8.2.1 +Sphinx==8.2.3 sphinx-intl==2.3.1 sphinx-markdown-builder==0.6.8 sphinxcontrib-applehelp==2.0.0 From c6babc12024a419c2b3580d441358f7faf6917ed Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 17:57:17 +0900 Subject: [PATCH 858/952] Add license information to files in matrix-base Signed-off-by: Suguru Hirahara --- roles/custom/matrix-base/defaults/main.yml | 29 +++++++++++++++++++ .../tasks/ensure_fuse_installed.yml | 4 +++ .../tasks/ensure_fuse_installed_archlinux.yml | 4 +++ .../tasks/ensure_fuse_installed_debian.yml | 4 +++ .../tasks/ensure_fuse_installed_redhat.yml | 4 +++ .../tasks/ensure_openssl_installed.yml | 4 +++ roles/custom/matrix-base/tasks/main.yml | 9 ++++++ .../matrix-base/tasks/setup_matrix_base.yml | 12 ++++++++ .../matrix-base/tasks/setup_matrix_user.yml | 5 ++++ .../matrix-base/tasks/validate_config.yml | 10 +++++++ .../templates/bin/remove-all.j2.license | 6 ++++ 11 files changed, 91 insertions(+) create mode 100644 roles/custom/matrix-base/templates/bin/remove-all.j2.license diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml index 6a72154a4..31ccaad86 100644 --- a/roles/custom/matrix-base/defaults/main.yml +++ b/roles/custom/matrix-base/defaults/main.yml @@ -1,3 +1,32 @@ +# SPDX-FileCopyrightText: 2019 - 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 Lyubomir Popov +# SPDX-FileCopyrightText: 2019 Stuart Mumford +# SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Alin Trăistaru +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2020 Tobias Küchel +# SPDX-FileCopyrightText: 2021 Blaž Tomažič +# SPDX-FileCopyrightText: 2021 Krisztian Szegi +# SPDX-FileCopyrightText: 2021 Yannick Goossens +# SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Charles Wright +# SPDX-FileCopyrightText: 2022 Julian Foad +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann +# SPDX-FileCopyrightText: 2023 Jayesh Nirve +# SPDX-FileCopyrightText: 2023 Johan Swetzén +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 László Várady +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # The bare domain name which represents your Matrix identity. diff --git a/roles/custom/matrix-base/tasks/ensure_fuse_installed.yml b/roles/custom/matrix-base/tasks/ensure_fuse_installed.yml index 8f768bd13..3a30837cf 100644 --- a/roles/custom/matrix-base/tasks/ensure_fuse_installed.yml +++ b/roles/custom/matrix-base/tasks/ensure_fuse_installed.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This is for both RedHat 7 and 8 diff --git a/roles/custom/matrix-base/tasks/ensure_fuse_installed_archlinux.yml b/roles/custom/matrix-base/tasks/ensure_fuse_installed_archlinux.yml index 676543d83..6abff8bf9 100644 --- a/roles/custom/matrix-base/tasks/ensure_fuse_installed_archlinux.yml +++ b/roles/custom/matrix-base/tasks/ensure_fuse_installed_archlinux.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure fuse installed (Archlinux) diff --git a/roles/custom/matrix-base/tasks/ensure_fuse_installed_debian.yml b/roles/custom/matrix-base/tasks/ensure_fuse_installed_debian.yml index b9491eb49..8f3637dd4 100644 --- a/roles/custom/matrix-base/tasks/ensure_fuse_installed_debian.yml +++ b/roles/custom/matrix-base/tasks/ensure_fuse_installed_debian.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure fuse installed (Debian/Raspbian) diff --git a/roles/custom/matrix-base/tasks/ensure_fuse_installed_redhat.yml b/roles/custom/matrix-base/tasks/ensure_fuse_installed_redhat.yml index 878fb5682..be2888030 100644 --- a/roles/custom/matrix-base/tasks/ensure_fuse_installed_redhat.yml +++ b/roles/custom/matrix-base/tasks/ensure_fuse_installed_redhat.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure fuse installed (RedHat) diff --git a/roles/custom/matrix-base/tasks/ensure_openssl_installed.yml b/roles/custom/matrix-base/tasks/ensure_openssl_installed.yml index d0cd8edea..11a25fbc9 100644 --- a/roles/custom/matrix-base/tasks/ensure_openssl_installed.yml +++ b/roles/custom/matrix-base/tasks/ensure_openssl_installed.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure openssl installed diff --git a/roles/custom/matrix-base/tasks/main.yml b/roles/custom/matrix-base/tasks/main.yml index 7351d1b8a..d6d4d8f26 100644 --- a/roles/custom/matrix-base/tasks/main.yml +++ b/roles/custom/matrix-base/tasks/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Warren Bailey +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-base/tasks/setup_matrix_base.yml b/roles/custom/matrix-base/tasks/setup_matrix_base.yml index 448ac7693..337017a46 100644 --- a/roles/custom/matrix-base/tasks/setup_matrix_base.yml +++ b/roles/custom/matrix-base/tasks/setup_matrix_base.yml @@ -1,3 +1,15 @@ +# SPDX-FileCopyrightText: 2017 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2018 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2019 Stuart Mumford +# SPDX-FileCopyrightText: 2020 Béla Becker +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 László Várady +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix base paths exists diff --git a/roles/custom/matrix-base/tasks/setup_matrix_user.yml b/roles/custom/matrix-base/tasks/setup_matrix_user.yml index 0c9086e59..146452302 100644 --- a/roles/custom/matrix-base/tasks/setup_matrix_user.yml +++ b/roles/custom/matrix-base/tasks/setup_matrix_user.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix group is created diff --git a/roles/custom/matrix-base/tasks/validate_config.yml b/roles/custom/matrix-base/tasks/validate_config.yml index 68020a2b3..f1a78f614 100644 --- a/roles/custom/matrix-base/tasks/validate_config.yml +++ b/roles/custom/matrix-base/tasks/validate_config.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 - 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2020 Christian Wolf +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2022 Charles Wright +# SPDX-FileCopyrightText: 2022 Warren Bailey +# SPDX-FileCopyrightText: 2023 Jayesh Nirve +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if invalid homeserver implementation diff --git a/roles/custom/matrix-base/templates/bin/remove-all.j2.license b/roles/custom/matrix-base/templates/bin/remove-all.j2.license new file mode 100644 index 000000000..34a0c1266 --- /dev/null +++ b/roles/custom/matrix-base/templates/bin/remove-all.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2018 - 2023 MDAD project contributors +SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 4915f14a580ccea8c89923cf42eade7f1d6efbc5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 17:58:12 +0900 Subject: [PATCH 859/952] Add license information to files for matrix-client-element Signed-off-by: Suguru Hirahara --- .../configuring-playbook-client-element-web.md | 10 ++++++++++ .../matrix-client-element/defaults/main.yml | 18 ++++++++++++++++++ .../matrix-client-element/tasks/main.yml | 5 +++++ .../tasks/prepare_themes.yml | 6 ++++++ .../matrix-client-element/tasks/self_check.yml | 5 +++++ .../tasks/setup_install.yml | 11 +++++++++++ .../tasks/setup_uninstall.yml | 7 +++++++ .../tasks/validate_config.yml | 6 ++++++ .../templates/config.json.j2.license | 6 ++++++ .../matrix-client-element/templates/labels.j2 | 6 ++++++ .../templates/map_style.json.j2.license | 3 +++ .../templates/nginx.conf.j2.license | 4 ++++ .../matrix-client-element.service.j2.license | 5 +++++ .../templates/welcome.html.j2.license | 9 +++++++++ .../custom/matrix-client-element/vars/main.yml | 4 ++++ 15 files changed, 105 insertions(+) create mode 100644 roles/custom/matrix-client-element/templates/config.json.j2.license create mode 100644 roles/custom/matrix-client-element/templates/map_style.json.j2.license create mode 100644 roles/custom/matrix-client-element/templates/nginx.conf.j2.license create mode 100644 roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2.license create mode 100644 roles/custom/matrix-client-element/templates/welcome.html.j2.license diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md index 071be15ee..2f2420965 100644 --- a/docs/configuring-playbook-client-element-web.md +++ b/docs/configuring-playbook-client-element-web.md @@ -1,3 +1,13 @@ + + # Configuring Element Web (optional) By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document. diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 93079df8f..237214cf1 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -1,3 +1,21 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Paul Tötterman +# SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Christos Karamolegkos +# SPDX-FileCopyrightText: 2022 Joe Kappus +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2023 Igor Goldenberg +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Project source code URL: https://github.com/element-hq/element-web diff --git a/roles/custom/matrix-client-element/tasks/main.yml b/roles/custom/matrix-client-element/tasks/main.yml index 770200678..eddb03ad0 100644 --- a/roles/custom/matrix-client-element/tasks/main.yml +++ b/roles/custom/matrix-client-element/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-client-element/tasks/prepare_themes.yml b/roles/custom/matrix-client-element/tasks/prepare_themes.yml index cb3bf2bd4..56ddb3403 100644 --- a/roles/custom/matrix-client-element/tasks/prepare_themes.yml +++ b/roles/custom/matrix-client-element/tasks/prepare_themes.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # diff --git a/roles/custom/matrix-client-element/tasks/self_check.yml b/roles/custom/matrix-client-element/tasks/self_check.yml index 8a08d8d04..b2e70a5d1 100644 --- a/roles/custom/matrix-client-element/tasks/self_check.yml +++ b/roles/custom/matrix-client-element/tasks/self_check.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-client-element/tasks/setup_install.yml b/roles/custom/matrix-client-element/tasks/setup_install.yml index e528faa8b..730e50282 100644 --- a/roles/custom/matrix-client-element/tasks/setup_install.yml +++ b/roles/custom/matrix-client-element/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Element Web paths exists diff --git a/roles/custom/matrix-client-element/tasks/setup_uninstall.yml b/roles/custom/matrix-client-element/tasks/setup_uninstall.yml index 279dd8166..a8823ed4a 100644 --- a/roles/custom/matrix-client-element/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-element/tasks/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-client-element.service diff --git a/roles/custom/matrix-client-element/tasks/validate_config.yml b/roles/custom/matrix-client-element/tasks/validate_config.yml index fa76cdcd2..7e3623aeb 100644 --- a/roles/custom/matrix-client-element/tasks/validate_config.yml +++ b/roles/custom/matrix-client-element/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Element Web settings not defined diff --git a/roles/custom/matrix-client-element/templates/config.json.j2.license b/roles/custom/matrix-client-element/templates/config.json.j2.license new file mode 100644 index 000000000..d679203dd --- /dev/null +++ b/roles/custom/matrix-client-element/templates/config.json.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Aaron Raimist +SPDX-FileCopyrightText: 2023 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2023 Igor Goldenberg + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/templates/labels.j2 b/roles/custom/matrix-client-element/templates/labels.j2 index 67ed2b95a..2d12275e5 100644 --- a/roles/custom/matrix-client-element/templates/labels.j2 +++ b/roles/custom/matrix-client-element/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_client_element_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-client-element/templates/map_style.json.j2.license b/roles/custom/matrix-client-element/templates/map_style.json.j2.license new file mode 100644 index 000000000..bf4d752e6 --- /dev/null +++ b/roles/custom/matrix-client-element/templates/map_style.json.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/templates/nginx.conf.j2.license b/roles/custom/matrix-client-element/templates/nginx.conf.j2.license new file mode 100644 index 000000000..f54d32e63 --- /dev/null +++ b/roles/custom/matrix-client-element/templates/nginx.conf.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2.license b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2.license new file mode 100644 index 000000000..909ecff79 --- /dev/null +++ b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/templates/welcome.html.j2.license b/roles/custom/matrix-client-element/templates/welcome.html.j2.license new file mode 100644 index 000000000..8338f12af --- /dev/null +++ b/roles/custom/matrix-client-element/templates/welcome.html.j2.license @@ -0,0 +1,9 @@ +SPDX-FileCopyrightText: 2019 Daniel Hoffend +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Clement Renaud +SPDX-FileCopyrightText: 2020 Stefan Warnat +SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/vars/main.yml b/roles/custom/matrix-client-element/vars/main.yml index 8237b5110..f332b4312 100644 --- a/roles/custom/matrix-client-element/vars/main.yml +++ b/roles/custom/matrix-client-element/vars/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2020 - 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_client_element_embedded_pages_home_url: "{{ ('' if matrix_client_element_embedded_pages_home_path is none else 'home.html') }}" From c84c39fbc4a496dc7c7961b1ed594bba3ca97e7c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 17:58:28 +0900 Subject: [PATCH 860/952] Add license information to files in matrix-common-after Signed-off-by: Suguru Hirahara --- roles/custom/matrix-common-after/tasks/main.yml | 9 +++++++++ .../matrix-common-after/tasks/run_docker_prune.yml | 5 +++++ 2 files changed, 14 insertions(+) diff --git a/roles/custom/matrix-common-after/tasks/main.yml b/roles/custom/matrix-common-after/tasks/main.yml index 5e4dc76b9..30e32027a 100644 --- a/roles/custom/matrix-common-after/tasks/main.yml +++ b/roles/custom/matrix-common-after/tasks/main.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Marcel Partap +# SPDX-FileCopyrightText: 2019 Stuart Mumford +# SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-common-after/tasks/run_docker_prune.yml b/roles/custom/matrix-common-after/tasks/run_docker_prune.yml index 58f0e7933..0917d019d 100644 --- a/roles/custom/matrix-common-after/tasks/run_docker_prune.yml +++ b/roles/custom/matrix-common-after/tasks/run_docker_prune.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Run Docker System Prune From 68a78857b80c466bb7dbc9cd5e813e7340ff17c2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 17:58:55 +0900 Subject: [PATCH 861/952] Add license information to files for matrix-static-files Signed-off-by: Suguru Hirahara --- roles/custom/matrix-static-files/defaults/main.yml | 5 +++++ roles/custom/matrix-static-files/tasks/install.yml | 5 +++++ roles/custom/matrix-static-files/tasks/main.yml | 4 ++++ .../matrix-static-files/tasks/self_check_well_known.yml | 7 +++++++ .../tasks/self_check_well_known_file.yml | 9 +++++++++ roles/custom/matrix-static-files/tasks/uninstall.yml | 4 ++++ .../custom/matrix-static-files/tasks/validate_config.yml | 4 ++++ .../matrix-static-files/templates/config.toml.j2.license | 3 +++ roles/custom/matrix-static-files/templates/env.j2 | 6 ++++++ roles/custom/matrix-static-files/templates/labels.j2 | 7 +++++++ .../public/.well-known/matrix/client.j2.license | 3 +++ .../public/.well-known/matrix/server.j2.license | 3 +++ .../public/.well-known/matrix/support.j2.license | 3 +++ .../systemd/matrix-static-files.service.j2.license | 3 +++ 14 files changed, 66 insertions(+) create mode 100644 roles/custom/matrix-static-files/templates/config.toml.j2.license create mode 100644 roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2.license create mode 100644 roles/custom/matrix-static-files/templates/public/.well-known/matrix/server.j2.license create mode 100644 roles/custom/matrix-static-files/templates/public/.well-known/matrix/support.j2.license create mode 100644 roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2.license diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index b7f393d0a..045d28b70 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-static-files is a role which generates and serves `/.well-known/matrix` files for the purposes of Matrix Delegation. diff --git a/roles/custom/matrix-static-files/tasks/install.yml b/roles/custom/matrix-static-files/tasks/install.yml index 3cbd9d4c6..f23592644 100644 --- a/roles/custom/matrix-static-files/tasks/install.yml +++ b/roles/custom/matrix-static-files/tasks/install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-static-files paths exist diff --git a/roles/custom/matrix-static-files/tasks/main.yml b/roles/custom/matrix-static-files/tasks/main.yml index 7b5f25377..145a6952f 100644 --- a/roles/custom/matrix-static-files/tasks/main.yml +++ b/roles/custom/matrix-static-files/tasks/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-static-files/tasks/self_check_well_known.yml b/roles/custom/matrix-static-files/tasks/self_check_well_known.yml index b6b8f5494..807ffa55a 100644 --- a/roles/custom/matrix-static-files/tasks/self_check_well_known.yml +++ b/roles/custom/matrix-static-files/tasks/self_check_well_known.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2018 Aaron Raimist +# SPDX-FileCopyrightText: 2019 - 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Marcel Partap +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Determine well-known files to check (start with /.well-known/matrix/client) diff --git a/roles/custom/matrix-static-files/tasks/self_check_well_known_file.yml b/roles/custom/matrix-static-files/tasks/self_check_well_known_file.yml index 7dace4be2..03cd81823 100644 --- a/roles/custom/matrix-static-files/tasks/self_check_well_known_file.yml +++ b/roles/custom/matrix-static-files/tasks/self_check_well_known_file.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2021 Alexandros Afentoulis +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-static-files/tasks/uninstall.yml b/roles/custom/matrix-static-files/tasks/uninstall.yml index 5e5208ef6..610a33585 100644 --- a/roles/custom/matrix-static-files/tasks/uninstall.yml +++ b/roles/custom/matrix-static-files/tasks/uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-static-files systemd service diff --git a/roles/custom/matrix-static-files/tasks/validate_config.yml b/roles/custom/matrix-static-files/tasks/validate_config.yml index 9a590ea06..2697fa654 100644 --- a/roles/custom/matrix-static-files/tasks/validate_config.yml +++ b/roles/custom/matrix-static-files/tasks/validate_config.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-static-files settings not defined diff --git a/roles/custom/matrix-static-files/templates/config.toml.j2.license b/roles/custom/matrix-static-files/templates/config.toml.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-static-files/templates/config.toml.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-static-files/templates/env.j2 b/roles/custom/matrix-static-files/templates/env.j2 index 23c21aa86..0dd9b6f10 100644 --- a/roles/custom/matrix-static-files/templates/env.j2 +++ b/roles/custom/matrix-static-files/templates/env.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + SERVER_PORT={{ matrix_static_files_environment_variable_server_port }} SERVER_LOG_LEVEL={{ matrix_static_files_environment_variable_server_log_level }} diff --git a/roles/custom/matrix-static-files/templates/labels.j2 b/roles/custom/matrix-static-files/templates/labels.j2 index b2fe0ccf0..2d5be3895 100644 --- a/roles/custom/matrix-static-files/templates/labels.j2 +++ b/roles/custom/matrix-static-files/templates/labels.j2 @@ -1,3 +1,10 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_static_files_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2.license b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-static-files/templates/public/.well-known/matrix/server.j2.license b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/server.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/server.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-static-files/templates/public/.well-known/matrix/support.j2.license b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/support.j2.license new file mode 100644 index 000000000..e64bd56b9 --- /dev/null +++ b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/support.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2.license b/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2.license new file mode 100644 index 000000000..e18b238ea --- /dev/null +++ b/roles/custom/matrix-static-files/templates/systemd/matrix-static-files.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later From 0046d3a8d816b619a85004f7b511184dee96fecb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 3 Mar 2025 18:00:04 +0900 Subject: [PATCH 862/952] Add license information to files for matrix-user-creator Signed-off-by: Suguru Hirahara --- roles/custom/matrix-user-creator/defaults/main.yml | 4 ++++ roles/custom/matrix-user-creator/tasks/main.yml | 5 +++++ roles/custom/matrix-user-creator/tasks/setup.yml | 4 ++++ .../tasks/util/ensure_user_registered_conduit.yml | 4 ++++ .../tasks/util/ensure_user_registered_conduwuit.yml | 5 +++++ .../tasks/util/ensure_user_registered_dendrite.yml | 4 ++++ .../ensure_user_registered_matrix_authentication_service.yml | 4 ++++ .../tasks/util/ensure_user_registered_synapse.yml | 4 ++++ .../custom/matrix-user-creator/tasks/util/validate_user.yml | 4 ++++ roles/custom/matrix-user-creator/vars/main.yml | 5 +++++ 10 files changed, 43 insertions(+) diff --git a/roles/custom/matrix-user-creator/defaults/main.yml b/roles/custom/matrix-user-creator/defaults/main.yml index 20aad3d10..00642521c 100644 --- a/roles/custom/matrix-user-creator/defaults/main.yml +++ b/roles/custom/matrix-user-creator/defaults/main.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix-user-creator is a role that aims to automate initial Matrix user account creation. diff --git a/roles/custom/matrix-user-creator/tasks/main.yml b/roles/custom/matrix-user-creator/tasks/main.yml index 2d9cc1c38..6a1a0b20c 100644 --- a/roles/custom/matrix-user-creator/tasks/main.yml +++ b/roles/custom/matrix-user-creator/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-user-creator/tasks/setup.yml b/roles/custom/matrix-user-creator/tasks/setup.yml index 55e1dedef..efb9647dc 100644 --- a/roles/custom/matrix-user-creator/tasks/setup.yml +++ b/roles/custom/matrix-user-creator/tasks/setup.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Validate Matrix users to create diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduit.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduit.yml index 8bbd147b5..fa961d08f 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduit.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduit.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Conduit user registered - {{ user.username | quote }} diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml index 8526fe996..a322db2f2 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure conduwuit user registered - {{ user.username | quote }} diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_dendrite.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_dendrite.yml index 2fede49f8..2db976f3e 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_dendrite.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_dendrite.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Dendrite user registered - {{ user.username | quote }} diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_matrix_authentication_service.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_matrix_authentication_service.yml index ddf8eeff1..4fbeb03bf 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_matrix_authentication_service.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_matrix_authentication_service.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Matrix Authentication Service user registered - {{ user.username | quote }} diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_synapse.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_synapse.yml index 00189e5c5..1ae191e21 100644 --- a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_synapse.yml +++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_synapse.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Synapse user registered - {{ user.username | quote }} diff --git a/roles/custom/matrix-user-creator/tasks/util/validate_user.yml b/roles/custom/matrix-user-creator/tasks/util/validate_user.yml index e35475d4e..d21ffd0e1 100644 --- a/roles/custom/matrix-user-creator/tasks/util/validate_user.yml +++ b/roles/custom/matrix-user-creator/tasks/util/validate_user.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if invalid username diff --git a/roles/custom/matrix-user-creator/vars/main.yml b/roles/custom/matrix-user-creator/vars/main.yml index 7bb3a1a66..e5ed50746 100644 --- a/roles/custom/matrix-user-creator/vars/main.yml +++ b/roles/custom/matrix-user-creator/vars/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # matrix_user_creator_users holds a list of users that should be created on the Matrix homeserver. From 88413a08cbb8543c49458bf6841bf8bff6345912 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 3 Mar 2025 20:24:16 +0000 Subject: [PATCH 863/952] Update gnuxie/draupnir Docker tag to v2.2.0 --- .../custom/matrix-appservice-draupnir-for-all/defaults/main.yml | 2 +- roles/custom/matrix-bot-draupnir/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml index e65ed32e8..a1eebf5af 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml @@ -11,7 +11,7 @@ matrix_appservice_draupnir_for_all_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_appservice_draupnir_for_all_version: "v2.1.0" +matrix_appservice_draupnir_for_all_version: "v2.2.0" matrix_appservice_draupnir_for_all_container_image_self_build: false matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 42fce6812..3ce88a4a0 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -5,7 +5,7 @@ matrix_bot_draupnir_enabled: true # renovate: datasource=docker depName=gnuxie/draupnir -matrix_bot_draupnir_version: "v2.1.0" +matrix_bot_draupnir_version: "v2.2.0" matrix_bot_draupnir_container_image_self_build: false matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git" From 2ef1a2e48d55e7a77c582a1b1c0231167f0df587 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 3 Mar 2025 22:33:07 +0200 Subject: [PATCH 864/952] Upgrade exim-relay (v4.98.1-r0-0-0 -> v4.98.1-r0-1-0) to allow usage over IPv6 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index b042d8ef1..6677b8ec2 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98.1-r0-0-0 + version: v4.98.1-r0-1-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-2 From f70ad4affb1756a36bf07449d8b8b9dd490ba978 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:19:51 +0900 Subject: [PATCH 865/952] Add license information to files in matrix-synapse/defaults Signed-off-by: Suguru Hirahara --- .../matrix-synapse/defaults/main.yml.license | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 roles/custom/matrix-synapse/defaults/main.yml.license diff --git a/roles/custom/matrix-synapse/defaults/main.yml.license b/roles/custom/matrix-synapse/defaults/main.yml.license new file mode 100644 index 000000000..1bca653ea --- /dev/null +++ b/roles/custom/matrix-synapse/defaults/main.yml.license @@ -0,0 +1,39 @@ +SPDX-FileCopyrightText: 2019 - 2020 Dan Arnfield +SPDX-FileCopyrightText: 2019 - 2022 Aaron Raimist +SPDX-FileCopyrightText: 2019 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Alexander Acevedo +SPDX-FileCopyrightText: 2019 Hugues Morisset +SPDX-FileCopyrightText: 2019 Lee Verberne +SPDX-FileCopyrightText: 2019 Lyubomir Popov +SPDX-FileCopyrightText: 2019 Oleg Fiksel +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Horvath Gergely +SPDX-FileCopyrightText: 2020 Justin Croonenberghs +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Max Klenk +SPDX-FileCopyrightText: 2020 Paul Tötterman +SPDX-FileCopyrightText: 2021 Ahmad Haghighi +SPDX-FileCopyrightText: 2021 Alejo Diaz +SPDX-FileCopyrightText: 2021 Davy Landman +SPDX-FileCopyrightText: 2021 Janar Juusu +SPDX-FileCopyrightText: 2021 Pablo Montepagano +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2021 boris runakov +SPDX-FileCopyrightText: 2022 - 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Benjamin Castellan +SPDX-FileCopyrightText: 2022 Joe Kappus +SPDX-FileCopyrightText: 2022 Marko Weltzer +SPDX-FileCopyrightText: 2022 Quentin Young +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2022 Yan Minagawa +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2023 Aeris One +SPDX-FileCopyrightText: 2023 Luke D Iremadze +SPDX-FileCopyrightText: 2023 Samuel Meenzen +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +SPDX-FileCopyrightText: 2024 Charles Wright + +SPDX-License-Identifier: AGPL-3.0-or-later From a4532762c2ef5dabc3c7b835077b58a346d8459e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:19:59 +0900 Subject: [PATCH 866/952] Add license information to files in matrix-synapse/tasks/ext Signed-off-by: Suguru Hirahara --- .../tasks/ext/encryption-disabler/setup_install.yml | 5 +++++ .../tasks/ext/encryption-disabler/setup_uninstall.yml | 4 ++++ .../matrix-synapse/tasks/ext/ldap-auth/setup_install.yml | 7 +++++++ .../tasks/ext/mjolnir-antispam/setup_install.yml | 7 +++++++ .../tasks/ext/mjolnir-antispam/setup_uninstall.yml | 5 +++++ .../matrix-synapse/tasks/ext/rest-auth/setup_install.yml | 7 +++++++ .../tasks/ext/rest-auth/setup_uninstall.yml | 4 ++++ .../tasks/ext/s3-storage-provider/setup_install.yml | 4 ++++ .../tasks/ext/s3-storage-provider/setup_uninstall.yml | 4 ++++ .../tasks/ext/s3-storage-provider/validate_config.yml | 6 ++++++ roles/custom/matrix-synapse/tasks/ext/setup_install.yml | 6 ++++++ .../custom/matrix-synapse/tasks/ext/setup_uninstall.yml | 4 ++++ .../tasks/ext/shared-secret-auth/setup_install.yml | 7 +++++++ .../tasks/ext/shared-secret-auth/setup_uninstall.yml | 4 ++++ .../ext/synapse-auto-accept-invite/setup_install.yml | 4 ++++ .../tasks/ext/synapse-simple-antispam/setup_install.yml | 9 +++++++++ .../ext/synapse-simple-antispam/setup_uninstall.yml | 4 ++++ 17 files changed, 91 insertions(+) diff --git a/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml index b8046033b..97ee49673 100644 --- a/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Download matrix_encryption_disabler diff --git a/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_uninstall.yml index c223f6e85..d169ad539 100644 --- a/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/encryption-disabler/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix_encryption_disabler doesn't exist diff --git a/roles/custom/matrix-synapse/tasks/ext/ldap-auth/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/ldap-auth/setup_install.yml index 6d4843771..baf0a285a 100644 --- a/roles/custom/matrix-synapse/tasks/ext/ldap-auth/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/ldap-auth/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2018 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2018 Thomas vO +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_install.yml index 0fc2a7506..ea43bb34a 100644 --- a/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure git installed diff --git a/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_uninstall.yml index 8211d51ae..67fff39a5 100644 --- a/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/mjolnir-antispam/setup_uninstall.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure mjolnir-antispam doesn't exist diff --git a/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_install.yml index 4c59a4b1f..d50a32cd9 100644 --- a/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2018 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Michael Haak +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if REST Auth endpoint not configured diff --git a/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_uninstall.yml index d95dd1c7c..7c094f847 100644 --- a/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/rest-auth/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-synapse-rest-auth doesn't exist diff --git a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml index ede73ec9a..d3c7b8610 100644 --- a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # We install this into Synapse by making `matrix_synapse_ext_synapse_s3_storage_provider_enabled` influence other variables: diff --git a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_uninstall.yml index 83e8a0f7d..0301df667 100644 --- a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-synapse-s3-storage-provider-migrate.service and timer don't exist diff --git a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/validate_config.yml b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/validate_config.yml index 406f186dc..b9e84a3d2 100644 --- a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/validate_config.yml +++ b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2022 Luke Moch +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required s3-storage-provider settings not defined ansible.builtin.fail: diff --git a/roles/custom/matrix-synapse/tasks/ext/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/setup_install.yml index f7be477aa..17bd5670b 100644 --- a/roles/custom/matrix-synapse/tasks/ext/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/setup_install.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2019 Hugues Morisset +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # encryption-disabler diff --git a/roles/custom/matrix-synapse/tasks/ext/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/setup_uninstall.yml index f584f584d..21aa141de 100644 --- a/roles/custom/matrix-synapse/tasks/ext/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # encryption-disabler diff --git a/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml index ecec3e803..ac09fe46e 100644 --- a/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Michael Haak +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if Shared Secret Auth secret not set diff --git a/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_uninstall.yml index b2f909443..8bb39dc92 100644 --- a/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/shared-secret-auth/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure matrix-synapse-shared-secret-auth doesn't exist diff --git a/roles/custom/matrix-synapse/tasks/ext/synapse-auto-accept-invite/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/synapse-auto-accept-invite/setup_install.yml index 182d42b03..9bbabdbaf 100644 --- a/roles/custom/matrix-synapse/tasks/ext/synapse-auto-accept-invite/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/synapse-auto-accept-invite/setup_install.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_install.yml index e62c62dfe..8f2b4ac6e 100644 --- a/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_install.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Michael Haak +# SPDX-FileCopyrightText: 2020 Christian Wolf +# SPDX-FileCopyrightText: 2022 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if Synapse Simple Antispam blocked homeservers is not set diff --git a/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_uninstall.yml index b1d558aa5..bcfb1d694 100644 --- a/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/ext/synapse-simple-antispam/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure synapse-simple-antispam doesn't exist From 03293205749f0cdddc8140c80e1df27611595ac5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:20:04 +0900 Subject: [PATCH 867/952] Add license information to files in matrix-synapse/tasks/goofys Signed-off-by: Suguru Hirahara --- .../matrix-synapse/tasks/goofys/setup_install.yml | 10 ++++++++++ .../matrix-synapse/tasks/goofys/setup_uninstall.yml | 7 +++++++ 2 files changed, 17 insertions(+) diff --git a/roles/custom/matrix-synapse/tasks/goofys/setup_install.yml b/roles/custom/matrix-synapse/tasks/goofys/setup_install.yml index dd6d3e922..f057bcc48 100644 --- a/roles/custom/matrix-synapse/tasks/goofys/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/goofys/setup_install.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.include_role: diff --git a/roles/custom/matrix-synapse/tasks/goofys/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/goofys/setup_uninstall.yml index 252877dee..3c784cfcc 100644 --- a/roles/custom/matrix-synapse/tasks/goofys/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/goofys/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-goofys service From f0abe85c1821170294733d4dce80c4e2cba83894 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:20:12 +0900 Subject: [PATCH 868/952] Add license information to files in matrix-synapse/tasks/rust-synapse-compress-state Signed-off-by: Suguru Hirahara --- .../tasks/rust-synapse-compress-state/compress_room.yml | 6 ++++++ .../tasks/rust-synapse-compress-state/main.yml | 8 ++++++++ 2 files changed, 14 insertions(+) diff --git a/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/compress_room.yml b/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/compress_room.yml index 300571059..c7235b0e9 100644 --- a/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/compress_room.yml +++ b/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/compress_room.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Béla Becker +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.debug: diff --git a/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/main.yml b/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/main.yml index efebe6e92..f691a74ba 100644 --- a/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/main.yml +++ b/roles/custom/matrix-synapse/tasks/rust-synapse-compress-state/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Pre-checks From 54b7df44ec49a73f6940923a9667f03ffe3c3646 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:20:20 +0900 Subject: [PATCH 869/952] Add license information to files in matrix-synapse/tasks/synapse Signed-off-by: Suguru Hirahara --- .../custom/matrix-synapse/tasks/synapse/setup.yml | 5 +++++ .../tasks/synapse/setup_install.yml | 15 +++++++++++++++ .../tasks/synapse/setup_uninstall.yml | 7 +++++++ .../matrix-synapse/tasks/synapse/workers/init.yml | 7 +++++++ .../tasks/synapse/workers/setup_install.yml | 5 +++++ .../tasks/synapse/workers/setup_uninstall.yml | 6 ++++++ .../tasks/synapse/workers/util/inject_worker.yml | 4 ++++ .../workers/util/setup_files_for_worker.yml | 6 ++++++ 8 files changed, 55 insertions(+) diff --git a/roles/custom/matrix-synapse/tasks/synapse/setup.yml b/roles/custom/matrix-synapse/tasks/synapse/setup.yml index 80f761e59..19fb2983c 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/setup.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/setup.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.import_tasks: "{{ role_path }}/tasks/synapse/setup_install.yml" diff --git a/roles/custom/matrix-synapse/tasks/synapse/setup_install.yml b/roles/custom/matrix-synapse/tasks/synapse/setup_install.yml index 1181fd7c8..dcc009050 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/setup_install.yml @@ -1,3 +1,18 @@ +# SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jan Christian Grünhage +# SPDX-FileCopyrightText: 2019 Lyubomir Popov +# SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2024 David Mehren +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This will throw a Permission Denied error if already mounted using fuse diff --git a/roles/custom/matrix-synapse/tasks/synapse/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/synapse/setup_uninstall.yml index 6b8ae5a01..4798983c5 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/setup_uninstall.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-synapse service diff --git a/roles/custom/matrix-synapse/tasks/synapse/workers/init.yml b/roles/custom/matrix-synapse/tasks/synapse/workers/init.yml index 8bf8201a0..2f16215e8 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/workers/init.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/workers/init.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Michael Hollister +# SPDX-FileCopyrightText: 2024 Charles Wright +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Below is a huge hack for dynamically building a list of workers and finally assigning it to `matrix_synapse_workers_enabled_list`. # diff --git a/roles/custom/matrix-synapse/tasks/synapse/workers/setup_install.yml b/roles/custom/matrix-synapse/tasks/synapse/workers/setup_install.yml index b474be92a..e50df3259 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/workers/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/workers/setup_install.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2020 - 2021 Marcel Partap +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Determine current worker configs diff --git a/roles/custom/matrix-synapse/tasks/synapse/workers/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/synapse/workers/setup_uninstall.yml index 2b0d21df4..5677a5a89 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/workers/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/workers/setup_uninstall.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Populate service facts diff --git a/roles/custom/matrix-synapse/tasks/synapse/workers/util/inject_worker.yml b/roles/custom/matrix-synapse/tasks/synapse/workers/util/inject_worker.yml index c52777ebd..9338ce30b 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/workers/util/inject_worker.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/workers/util/inject_worker.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # The tasks below run before `validate_config.yml`. # To avoid failing with a cryptic error message, we'll do validation here. diff --git a/roles/custom/matrix-synapse/tasks/synapse/workers/util/setup_files_for_worker.yml b/roles/custom/matrix-synapse/tasks/synapse/workers/util/setup_files_for_worker.yml index 480ffba02..c09291d4a 100644 --- a/roles/custom/matrix-synapse/tasks/synapse/workers/util/setup_files_for_worker.yml +++ b/roles/custom/matrix-synapse/tasks/synapse/workers/util/setup_files_for_worker.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2024 Michael Hollister +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: From f7a030297468d40cae2931d386fda8a8d92381d4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:20:27 +0900 Subject: [PATCH 870/952] Add license information to files in matrix-synapse/tasks Signed-off-by: Suguru Hirahara --- .../matrix-synapse/tasks/import_media_store.yml | 9 +++++++++ .../matrix-synapse/tasks/import_synapse_sqlite_db.yml | 4 ++++ roles/custom/matrix-synapse/tasks/init.yml | 8 ++++++++ roles/custom/matrix-synapse/tasks/main.yml | 8 ++++++++ roles/custom/matrix-synapse/tasks/register_user.yml | 8 ++++++++ .../matrix-synapse/tasks/self_check_client_api.yml | 7 +++++++ .../tasks/self_check_federation_api.yml | 8 ++++++++ roles/custom/matrix-synapse/tasks/setup_install.yml | 11 +++++++++++ roles/custom/matrix-synapse/tasks/setup_uninstall.yml | 4 ++++ .../matrix-synapse/tasks/update_user_password.yml | 10 ++++++++++ roles/custom/matrix-synapse/tasks/validate_config.yml | 6 ++++++ 11 files changed, 83 insertions(+) diff --git a/roles/custom/matrix-synapse/tasks/import_media_store.yml b/roles/custom/matrix-synapse/tasks/import_media_store.yml index a6c085874..f9757df39 100644 --- a/roles/custom/matrix-synapse/tasks/import_media_store.yml +++ b/roles/custom/matrix-synapse/tasks/import_media_store.yml @@ -1,3 +1,12 @@ +# SPDX-FileCopyrightText: 2017 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jan Christian Grünhage +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # Pre-checks diff --git a/roles/custom/matrix-synapse/tasks/import_synapse_sqlite_db.yml b/roles/custom/matrix-synapse/tasks/import_synapse_sqlite_db.yml index 92bd36b42..a8ba6f153 100644 --- a/roles/custom/matrix-synapse/tasks/import_synapse_sqlite_db.yml +++ b/roles/custom/matrix-synapse/tasks/import_synapse_sqlite_db.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-synapse/tasks/init.yml b/roles/custom/matrix-synapse/tasks/init.yml index 341350a49..cbf204a2f 100644 --- a/roles/custom/matrix-synapse/tasks/init.yml +++ b/roles/custom/matrix-synapse/tasks/init.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This validation task is here, not in validate_config.yml, diff --git a/roles/custom/matrix-synapse/tasks/main.yml b/roles/custom/matrix-synapse/tasks/main.yml index 8bdf05e84..01d35eebf 100644 --- a/roles/custom/matrix-synapse/tasks/main.yml +++ b/roles/custom/matrix-synapse/tasks/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Lyubomir Popov +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse/tasks/register_user.yml b/roles/custom/matrix-synapse/tasks/register_user.yml index 215409593..55ece72ed 100644 --- a/roles/custom/matrix-synapse/tasks/register_user.yml +++ b/roles/custom/matrix-synapse/tasks/register_user.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2017 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Jan Christian Grünhage +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-synapse/tasks/self_check_client_api.yml b/roles/custom/matrix-synapse/tasks/self_check_client_api.yml index 7ec3fb09b..dc0a27814 100644 --- a/roles/custom/matrix-synapse/tasks/self_check_client_api.yml +++ b/roles/custom/matrix-synapse/tasks/self_check_client_api.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 - 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Client API diff --git a/roles/custom/matrix-synapse/tasks/self_check_federation_api.yml b/roles/custom/matrix-synapse/tasks/self_check_federation_api.yml index fde73dae0..d50098eef 100644 --- a/roles/custom/matrix-synapse/tasks/self_check_federation_api.yml +++ b/roles/custom/matrix-synapse/tasks/self_check_federation_api.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 - 2020 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Lorrin Nelson +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check Matrix Federation API diff --git a/roles/custom/matrix-synapse/tasks/setup_install.yml b/roles/custom/matrix-synapse/tasks/setup_install.yml index a2185da57..d131bd118 100644 --- a/roles/custom/matrix-synapse/tasks/setup_install.yml +++ b/roles/custom/matrix-synapse/tasks/setup_install.yml @@ -1,3 +1,14 @@ +# SPDX-FileCopyrightText: 2018 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2020 Marcel Partap +# SPDX-FileCopyrightText: 2020 Max Klenk +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Quentin Young +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Ensure Synapse paths exist diff --git a/roles/custom/matrix-synapse/tasks/setup_uninstall.yml b/roles/custom/matrix-synapse/tasks/setup_uninstall.yml index 66cda3e7d..c8e24493f 100644 --- a/roles/custom/matrix-synapse/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-synapse/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-synapse/tasks/update_user_password.yml b/roles/custom/matrix-synapse/tasks/update_user_password.yml index 32d24a154..cd8c44fe0 100644 --- a/roles/custom/matrix-synapse/tasks/update_user_password.yml +++ b/roles/custom/matrix-synapse/tasks/update_user_password.yml @@ -1,3 +1,13 @@ +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Lyubomir Popov +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Christian Wolf +# SPDX-FileCopyrightText: 2020 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if playbook called incorrectly diff --git a/roles/custom/matrix-synapse/tasks/validate_config.yml b/roles/custom/matrix-synapse/tasks/validate_config.yml index 8f73ad005..a0df4c057 100644 --- a/roles/custom/matrix-synapse/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse/tasks/validate_config.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Charles Wright +# SPDX-FileCopyrightText: 2024 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required Synapse settings not defined From 431d4c414b2272bdd8e9b60001b87eb884e1c444 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:22:26 +0900 Subject: [PATCH 871/952] Add license information to files in matrix-synapse/templates/goofys Signed-off-by: Suguru Hirahara --- .../matrix-synapse/templates/goofys/env-goofys.j2.license | 5 +++++ .../goofys/systemd/matrix-goofys.service.j2.license | 7 +++++++ 2 files changed, 12 insertions(+) create mode 100644 roles/custom/matrix-synapse/templates/goofys/env-goofys.j2.license create mode 100644 roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2.license diff --git a/roles/custom/matrix-synapse/templates/goofys/env-goofys.j2.license b/roles/custom/matrix-synapse/templates/goofys/env-goofys.j2.license new file mode 100644 index 000000000..72b378d97 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/goofys/env-goofys.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Alexander Acevedo +SPDX-FileCopyrightText: 2019 Hugues De Keyzer + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2.license b/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2.license new file mode 100644 index 000000000..cf2001184 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/goofys/systemd/matrix-goofys.service.j2.license @@ -0,0 +1,7 @@ +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Alexander Acevedo +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2024 Jim Myhrberg + +SPDX-License-Identifier: AGPL-3.0-or-later From 2eb952201c41c6a0fa5b4b81041da3aef7dbdcb4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:22:38 +0900 Subject: [PATCH 872/952] Add license information to files in matrix-synapse/templates/synapse Signed-off-by: Suguru Hirahara --- .../synapse/bin/register-user.j2.license | 6 ++++ .../customizations/Dockerfile.j2.license | 5 +++ .../bin/migrate.j2.license | 5 +++ .../s3-storage-provider/bin/shell.j2.license | 4 +++ .../ext/s3-storage-provider/database.yaml.j2 | 6 ++++ .../synapse/ext/s3-storage-provider/env.j2 | 8 +++++ .../media_storage_provider.yaml.j2 | 8 +++++ ...torage-provider-migrate.service.j2.license | 3 ++ ...-storage-provider-migrate.timer.j2.license | 3 ++ .../synapse/homeserver.yaml.j2.license | 33 +++++++++++++++++++ .../templates/synapse/labels.j2 | 6 ++++ .../external_prometheus.yml.example.j2 | 8 +++++ .../synapse/synapse.log.config.j2.license | 5 +++ .../matrix-synapse-worker.service.j2.license | 5 +++ .../systemd/matrix-synapse.service.j2.license | 13 ++++++++ .../templates/synapse/worker-labels.j2 | 6 ++++ .../templates/synapse/worker.yaml.j2.license | 8 +++++ 17 files changed, 132 insertions(+) create mode 100644 roles/custom/matrix-synapse/templates/synapse/bin/register-user.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/migrate.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/shell.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.service.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.timer.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/synapse.log.config.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2.license create mode 100644 roles/custom/matrix-synapse/templates/synapse/worker.yaml.j2.license diff --git a/roles/custom/matrix-synapse/templates/synapse/bin/register-user.j2.license b/roles/custom/matrix-synapse/templates/synapse/bin/register-user.j2.license new file mode 100644 index 000000000..d75acb7c2 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/bin/register-user.j2.license @@ -0,0 +1,6 @@ +SPDX-FileCopyrightText: 2017 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Julian Foad +SPDX-FileCopyrightText: 2021 boris runakov + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2.license b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2.license new file mode 100644 index 000000000..183cfa51b --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/migrate.j2.license b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/migrate.j2.license new file mode 100644 index 000000000..a4cf34b72 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/migrate.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2024 Tiago Carrondo + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/shell.j2.license b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/shell.j2.license new file mode 100644 index 000000000..939a124be --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/bin/shell.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Tiago Carrondo + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/database.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/database.yaml.j2 index ed11645eb..6b9cf159b 100644 --- a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/database.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/database.yaml.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + user: {{ matrix_synapse_database_user | to_json }} password: {{ matrix_synapse_database_password | to_json }} database: {{ matrix_synapse_database_database | to_json }} diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/env.j2 b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/env.j2 index e50bf7e54..f9d8cd8f4 100644 --- a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/env.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/env.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if not matrix_synapse_ext_synapse_s3_storage_provider_config_ec2_instance_profile | bool %} AWS_ACCESS_KEY_ID={{ matrix_synapse_ext_synapse_s3_storage_provider_config_access_key_id }} AWS_SECRET_ACCESS_KEY={{ matrix_synapse_ext_synapse_s3_storage_provider_config_secret_access_key }} diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/media_storage_provider.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/media_storage_provider.yaml.j2 index 97387e55c..988ff9868 100644 --- a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/media_storage_provider.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/media_storage_provider.yaml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2022 - 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + module: s3_storage_provider.S3StorageProviderBackend store_local: {{ matrix_synapse_ext_synapse_s3_storage_provider_store_local | to_json }} store_remote: {{ matrix_synapse_ext_synapse_s3_storage_provider_store_remote | to_json }} diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.service.j2.license b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.service.j2.license new file mode 100644 index 000000000..7b1e56adc --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.service.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.timer.j2.license b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.timer.j2.license new file mode 100644 index 000000000..63cfcee34 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/ext/s3-storage-provider/systemd/matrix-synapse-s3-storage-provider-migrate.timer.j2.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2.license b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2.license new file mode 100644 index 000000000..6cb772fc7 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2.license @@ -0,0 +1,33 @@ +SPDX-FileCopyrightText: 2018 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2018 Thomas vO +SPDX-FileCopyrightText: 2019 - 2021 Marcel Partap +SPDX-FileCopyrightText: 2019 - 2022 Aaron Raimist +SPDX-FileCopyrightText: 2019 Ciaran Ainsworth +SPDX-FileCopyrightText: 2019 Dan Arnfield +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Lee Verberne +SPDX-FileCopyrightText: 2019 Lyubomir Popov +SPDX-FileCopyrightText: 2019 Oleg Fiksel +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Justin Croonenberghs +SPDX-FileCopyrightText: 2020 Max Klenk +SPDX-FileCopyrightText: 2021 Ahmad Haghighi +SPDX-FileCopyrightText: 2021 Alejo Diaz +SPDX-FileCopyrightText: 2021 Pablo Montepagano +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2021 boris runakov +SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Benjamin Castellan +SPDX-FileCopyrightText: 2022 Jim Myhrberg +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2022 Yan Minagawa +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2023 Aeris One +SPDX-FileCopyrightText: 2023 Alexis Yushin +SPDX-FileCopyrightText: 2023 Luke D Iremadze +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/labels.j2 b/roles/custom/matrix-synapse/templates/synapse/labels.j2 index dd4d776c1..0d522c356 100644 --- a/roles/custom/matrix-synapse/templates/synapse/labels.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_synapse_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-synapse/templates/synapse/prometheus/external_prometheus.yml.example.j2 b/roles/custom/matrix-synapse/templates/synapse/prometheus/external_prometheus.yml.example.j2 index de39e36fa..897c19fce 100644 --- a/roles/custom/matrix-synapse/templates/synapse/prometheus/external_prometheus.yml.example.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/prometheus/external_prometheus.yml.example.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2021 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Kim Brose + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + global: scrape_interval: 5s diff --git a/roles/custom/matrix-synapse/templates/synapse/synapse.log.config.j2.license b/roles/custom/matrix-synapse/templates/synapse/synapse.log.config.j2.license new file mode 100644 index 000000000..17b1ad961 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/synapse.log.config.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2018 - 2022 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Aaron Raimist +SPDX-FileCopyrightText: 2019 Hugues De Keyzer + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2.license b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2.license new file mode 100644 index 000000000..18a2c5037 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker.service.j2.license @@ -0,0 +1,5 @@ +SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2.license b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2.license new file mode 100644 index 000000000..4ebda2856 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/systemd/matrix-synapse.service.j2.license @@ -0,0 +1,13 @@ +SPDX-FileCopyrightText: 2017 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 - 2021 MDAD project contributors +SPDX-FileCopyrightText: 2019 Aaron Raimist +SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2020 - 2021 Marcel Partap +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2021 boris runakov +SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2024 Michael Hollister + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-synapse/templates/synapse/worker-labels.j2 b/roles/custom/matrix-synapse/templates/synapse/worker-labels.j2 index 9cf4feaed..2fcbe4add 100644 --- a/roles/custom/matrix-synapse/templates/synapse/worker-labels.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/worker-labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_synapse_worker_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-synapse/templates/synapse/worker.yaml.j2.license b/roles/custom/matrix-synapse/templates/synapse/worker.yaml.j2.license new file mode 100644 index 000000000..2ab771284 --- /dev/null +++ b/roles/custom/matrix-synapse/templates/synapse/worker.yaml.j2.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Max Klenk +SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 boris runakov +SPDX-FileCopyrightText: 2022 David Mehren +SPDX-FileCopyrightText: 2024 Charles Wright + +SPDX-License-Identifier: AGPL-3.0-or-later From d9d4c6f05fc27a6c84cbbece206ffe7858561668 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:22:43 +0900 Subject: [PATCH 873/952] Add license information to roles/custom/matrix-synapse/vars/main.yml Signed-off-by: Suguru Hirahara --- roles/custom/matrix-synapse/vars/main.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/roles/custom/matrix-synapse/vars/main.yml b/roles/custom/matrix-synapse/vars/main.yml index f47a2e848..f4de30ac8 100644 --- a/roles/custom/matrix-synapse/vars/main.yml +++ b/roles/custom/matrix-synapse/vars/main.yml @@ -1,3 +1,11 @@ +# SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2023 Alexis Yushin +# SPDX-FileCopyrightText: 2024 Charles Wright +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- matrix_synapse_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_server_fqn_matrix }}/_matrix/client/versions" From 3684842e86adc0b027e6960ff95f9500a3b8f32d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 19:22:48 +0900 Subject: [PATCH 874/952] Add license information to docs/configuring-playbook-synapse.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-synapse.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md index 72666042c..4a15ef701 100644 --- a/docs/configuring-playbook-synapse.md +++ b/docs/configuring-playbook-synapse.md @@ -1,3 +1,14 @@ + + # Configuring Synapse (optional) By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document. From 7fca7ceea860d2cc24afd0640fd20b04ad47ac69 Mon Sep 17 00:00:00 2001 From: Aine Date: Tue, 4 Mar 2025 12:43:52 +0200 Subject: [PATCH 875/952] Borgmatic v1.9.13 --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 6677b8ec2..7c11007ca 100644 --- a/requirements.yml +++ b/requirements.yml @@ -4,7 +4,7 @@ version: v1.0.0-5 name: auxiliary - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git - version: v1.4.0-1.9.10-6 + version: v1.4.0-1.9.13-0 name: backup_borg - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy.git version: v0.3.0-4 From 76f9e7f34f5fdc55bcff423d81407e997091ee11 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Tue, 4 Mar 2025 10:44:30 +0000 Subject: [PATCH 876/952] Update ajbura/cinny Docker tag to v4.5.0 --- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index 3f103becb..fa0597af6 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -17,7 +17,7 @@ matrix_client_cinny_container_image_self_build: false matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git" # renovate: datasource=docker depName=ajbura/cinny -matrix_client_cinny_version: v4.4.0 +matrix_client_cinny_version: v4.5.0 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_registry_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" matrix_client_cinny_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_client_cinny_docker_image_registry_prefix_upstream }}" matrix_client_cinny_docker_image_registry_prefix_upstream: "{{ matrix_client_cinny_docker_image_registry_prefix_upstream_default }}" From 424e5c66464ee1de70615000d244cfd82243a2f2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 20:49:21 +0900 Subject: [PATCH 877/952] Update docs/configuring-playbook-synapse-simple-antispam.md: add the section for installing Signed-off-by: Suguru Hirahara --- ...onfiguring-playbook-synapse-simple-antispam.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/configuring-playbook-synapse-simple-antispam.md b/docs/configuring-playbook-synapse-simple-antispam.md index 35b106a60..b5d99844c 100644 --- a/docs/configuring-playbook-synapse-simple-antispam.md +++ b/docs/configuring-playbook-synapse-simple-antispam.md @@ -1,6 +1,6 @@ @@ -24,3 +24,16 @@ matrix_synapse_ext_spam_checker_synapse_simple_antispam_config_blocked_homeserve - example.com - example.net ``` + +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. From 70b4fd0489d8c8e886d04206ae5b696f1de390f5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 20:57:57 +0900 Subject: [PATCH 878/952] Update docs/configuring-playbook-synapse-s3-storage-provider.md: adopt the common introduction and add the section for installing Signed-off-by: Suguru Hirahara --- ...ng-playbook-synapse-s3-storage-provider.md | 23 ++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md index eccd58c02..0d7c312ce 100644 --- a/docs/configuring-playbook-synapse-s3-storage-provider.md +++ b/docs/configuring-playbook-synapse-s3-storage-provider.md @@ -2,16 +2,20 @@ SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman SPDX-FileCopyrightText: 2023 MDAD project contributors -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> # Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional) -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. +The playbook can install and configure the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) for you. -An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md). +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. + +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. + +**Note**: alternatively you can use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md) despite worse performance. ## How it works? @@ -62,6 +66,19 @@ Take a look at: - `roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file +## Installing + +After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below: + + +```sh +ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start +``` + +The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all` + +`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too. + ## Usage If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`): From f059b72bb58572953c906d295efddb924c7f26c9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 21:20:57 +0900 Subject: [PATCH 879/952] Update docs/configuring-playbook-s3-goofys.md - Adopt the common instruction - Add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3-goofys.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-s3-goofys.md b/docs/configuring-playbook-s3-goofys.md index 2efdac86e..2e3e76bea 100644 --- a/docs/configuring-playbook-s3-goofys.md +++ b/docs/configuring-playbook-s3-goofys.md @@ -1,12 +1,21 @@ + + # Storing Matrix media files on Amazon S3 with Goofys (optional) -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. +The playbook can install and configure [Goofys](https://github.com/kahing/goofys) for you. -Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md). +Goofys makes it possible to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service) object storage. -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. +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. -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. +**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. + +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. ## Adjusting the playbook configuration From 0b9e4df5d336959549e1c28b5b76f61d58f703eb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 21:29:29 +0900 Subject: [PATCH 880/952] Update docs: add "Synapse" to the title of configuring-playbook-s3-goofys.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3-goofys.md | 2 +- docs/configuring-playbook.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-s3-goofys.md b/docs/configuring-playbook-s3-goofys.md index 2e3e76bea..8fcf145a0 100644 --- a/docs/configuring-playbook-s3-goofys.md +++ b/docs/configuring-playbook-s3-goofys.md @@ -5,7 +5,7 @@ SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> -# Storing Matrix media files on Amazon S3 with Goofys (optional) +# Storing Synapse media files on Amazon S3 with Goofys (optional) The playbook can install and configure [Goofys](https://github.com/kahing/goofys) for you. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 769ec21ab..1e8762ca4 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -120,7 +120,7 @@ Extend and modify how users are authenticated on your homeserver. Use alternative file storage to the default `media_store` folder. -- [Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md) +- [Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md) - [Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md) From ed23f9b5dbf710d257af0c37bc8c68a564c3ba39 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 4 Mar 2025 21:32:11 +0900 Subject: [PATCH 881/952] Update docs/configuring-playbook.md: file storage section - Add a link to configuring-playbook-synapse-s3-storage-provider.md - Sort items Signed-off-by: Suguru Hirahara --- docs/configuring-playbook.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 1e8762ca4..6a867b8d6 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -120,11 +120,13 @@ Extend and modify how users are authenticated on your homeserver. Use alternative file storage to the default `media_store` folder. -- [Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md) +- [Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md) - [Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md) -- [Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md) +- [Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md) + +- [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) ### Bridging other networks From 015b0d7cb43e480c698fb483df3cc7c0e0aa7c0c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:25:49 +0900 Subject: [PATCH 882/952] Add license information to files in examples Signed-off-by: Suguru Hirahara --- examples/host.yml | 5 +++++ examples/hosts.license | 8 ++++++++ examples/vars.yml.license | 9 +++++++++ 3 files changed, 22 insertions(+) create mode 100644 examples/hosts.license create mode 100644 examples/vars.yml.license diff --git a/examples/host.yml b/examples/host.yml index 85d2f3170..cd43db4da 100644 --- a/examples/host.yml +++ b/examples/host.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # This is a host file for usage with the `../bin/ansible-all-hosts.sh` script, diff --git a/examples/hosts.license b/examples/hosts.license new file mode 100644 index 000000000..91ac0d395 --- /dev/null +++ b/examples/hosts.license @@ -0,0 +1,8 @@ +SPDX-FileCopyrightText: 2017 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Dan Arnfield +SPDX-FileCopyrightText: 2019 MDAD project contributors +SPDX-FileCopyrightText: 2021 Aaron Raimist +SPDX-FileCopyrightText: 2023 David Holdeman +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/examples/vars.yml.license b/examples/vars.yml.license new file mode 100644 index 000000000..a0845f66a --- /dev/null +++ b/examples/vars.yml.license @@ -0,0 +1,9 @@ +SPDX-FileCopyrightText: 2017 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Hugues Morisset +SPDX-FileCopyrightText: 2018 MDAD project contributors +SPDX-FileCopyrightText: 2020 Olaf Schoenwald +SPDX-FileCopyrightText: 2021 Kim Brose +SPDX-FileCopyrightText: 2022 Marko Weltzer +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 687449fcbaf2dba11481cff861112bd981554a2e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:25:58 +0900 Subject: [PATCH 883/952] Add license information for README.md Signed-off-by: Suguru Hirahara --- README.md.license | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 README.md.license diff --git a/README.md.license b/README.md.license new file mode 100644 index 000000000..430773b9b --- /dev/null +++ b/README.md.license @@ -0,0 +1,34 @@ +SPDX-FileCopyrightText: 2017 - 2025 MDAD project contributors +SPDX-FileCopyrightText: 2017 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 - 2021 Aaron Raimist +SPDX-FileCopyrightText: 2019 - 2020 Hugues Morisset +SPDX-FileCopyrightText: 2019 Edgars Voroboks +SPDX-FileCopyrightText: 2019 Eduardo Beltrame +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2020 Lee Verberne +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Matthew Croughan +SPDX-FileCopyrightText: 2020 Tulir Asokan +SPDX-FileCopyrightText: 2021 Alexandar Mechev +SPDX-FileCopyrightText: 2021 Béla Becker +SPDX-FileCopyrightText: 2021 Cody Neiman +SPDX-FileCopyrightText: 2021 Marcus Proest +SPDX-FileCopyrightText: 2021 Matthew Cengia +SPDX-FileCopyrightText: 2021 Prasiddh Pooskur +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2021 Yannick Goossens +SPDX-FileCopyrightText: 2022 - 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Andrew Morgan +SPDX-FileCopyrightText: 2022 Christos Karamolegkos +SPDX-FileCopyrightText: 2022 Dennis Ciba +SPDX-FileCopyrightText: 2022 Julian Foad +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Kim Brose +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2023 Joe Kappus +SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From e1c03dc7ff3cee9abb89a5796eb8e531196ec633 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:05 +0900 Subject: [PATCH 884/952] Add license information to a role Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-appservice-draupnir-for-all.md | 7 +++++++ docs/configuring-playbook-bot-draupnir.md | 9 +++++++++ roles/custom/matrix-bot-draupnir/defaults/main.yml | 6 ++++++ roles/custom/matrix-bot-draupnir/tasks/main.yml | 5 +++++ roles/custom/matrix-bot-draupnir/tasks/setup_install.yml | 7 +++++++ .../custom/matrix-bot-draupnir/tasks/setup_uninstall.yml | 4 ++++ .../custom/matrix-bot-draupnir/tasks/validate_config.yml | 5 +++++ roles/custom/matrix-bot-draupnir/templates/labels.j2 | 6 ++++++ .../matrix-bot-draupnir/templates/production.yaml.j2 | 8 ++++++++ .../systemd/matrix-bot-draupnir.service.j2.license | 4 ++++ 10 files changed, 61 insertions(+) create mode 100644 roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2.license diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index ee5c11700..69890b3af 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -1,3 +1,10 @@ + + # Setting up Draupnir for All/D4A (optional) The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode. diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 965906b16..92f5c5969 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -1,3 +1,12 @@ + + # Setting up Draupnir (optional) The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you. diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml index 3ce88a4a0..8bb6ae8b4 100644 --- a/roles/custom/matrix-bot-draupnir/defaults/main.yml +++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml @@ -1,3 +1,9 @@ +# SPDX-FileCopyrightText: 2023 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # A moderation tool for Matrix # Project source code URL: https://github.com/the-draupnir-project/Draupnir diff --git a/roles/custom/matrix-bot-draupnir/tasks/main.yml b/roles/custom/matrix-bot-draupnir/tasks/main.yml index 66c7cd06e..e379c5e21 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/main.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/main.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - tags: diff --git a/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml b/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml index 0ddf994e7..140d6e7e6 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml @@ -1,3 +1,10 @@ +# SPDX-FileCopyrightText: 2023 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - ansible.builtin.set_fact: diff --git a/roles/custom/matrix-bot-draupnir/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-draupnir/tasks/setup_uninstall.yml index 10583a0bc..78f577a56 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/setup_uninstall.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 MDAD project contributors +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Check existence of matrix-bot-draupnir service diff --git a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml index b369a5c00..81b7ab00c 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml @@ -1,3 +1,8 @@ +# SPDX-FileCopyrightText: 2023 - 2025 MDAD project contributors +# SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- - name: Fail if required matrix-bot-draupnir variables are undefined diff --git a/roles/custom/matrix-bot-draupnir/templates/labels.j2 b/roles/custom/matrix-bot-draupnir/templates/labels.j2 index f24a77ddf..aeab96277 100644 --- a/roles/custom/matrix-bot-draupnir/templates/labels.j2 +++ b/roles/custom/matrix-bot-draupnir/templates/labels.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + {% if matrix_bot_draupnir_container_labels_traefik_enabled %} traefik.enable=true diff --git a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 index 56b82e322..147472936 100644 --- a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 +++ b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 @@ -1,3 +1,11 @@ +{# +SPDX-FileCopyrightText: 2023 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + # Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API), homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }} diff --git a/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2.license b/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2.license new file mode 100644 index 000000000..ff638a924 --- /dev/null +++ b/roles/custom/matrix-bot-draupnir/templates/systemd/matrix-bot-draupnir.service.j2.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 MDAD project contributors + +SPDX-License-Identifier: AGPL-3.0-or-later From 8be34c1ef1a712dc0fe52aea9f564ad64b9a528b Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:13 +0900 Subject: [PATCH 885/952] Add license information for setup.yml Signed-off-by: Suguru Hirahara --- setup.yml.license | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 setup.yml.license diff --git a/setup.yml.license b/setup.yml.license new file mode 100644 index 000000000..1668032ac --- /dev/null +++ b/setup.yml.license @@ -0,0 +1,36 @@ +SPDX-FileCopyrightText: 2017 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 - 2025 MDAD project contributors +SPDX-FileCopyrightText: 2019 Dan Arnfield +SPDX-FileCopyrightText: 2019 Edgars Voroboks +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Max Klenk +SPDX-FileCopyrightText: 2020 Rodrigo Belem +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2020 Tulir Asokan +SPDX-FileCopyrightText: 2021 Aaron Raimist +SPDX-FileCopyrightText: 2021 Alexandar Mechev +SPDX-FileCopyrightText: 2021 Béla Becker +SPDX-FileCopyrightText: 2021 Cody Neiman +SPDX-FileCopyrightText: 2021 Marcus Proest +SPDX-FileCopyrightText: 2021 Matthew Cengia +SPDX-FileCopyrightText: 2021 Raymond Coetzee +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2021 Yannick Goossens +SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Charles Wright +SPDX-FileCopyrightText: 2022 Jip J. Dekker +SPDX-FileCopyrightText: 2022 Julian Foad +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Vladimir Panteleev +SPDX-FileCopyrightText: 2022 Warren Bailey +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2023 Antonis Christofides +SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2023 Johan Swetzén +SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 975692c84d398225eea66e413d6788e82f1480f4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:22 +0900 Subject: [PATCH 886/952] Add SPDX-License-Identifier to extract-translation-templates.sh Signed-off-by: Suguru Hirahara --- i18n/bin/extract-translation-templates.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/i18n/bin/extract-translation-templates.sh b/i18n/bin/extract-translation-templates.sh index 3cbaeec8f..f023ea28c 100755 --- a/i18n/bin/extract-translation-templates.sh +++ b/i18n/bin/extract-translation-templates.sh @@ -1,6 +1,8 @@ #!/bin/bash # SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later # This script extracts translation templates (original English strings) into the `translation-templates/` directory. # These templates are later used to generate locale files for each language in the `locales/` directory. From d0ad3f22f8ddb7c60f3d6c0825e140f1f7e8f1cb Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:29 +0900 Subject: [PATCH 887/952] Update docs/configuring-playbook-ntfy.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ntfy.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index ac7c157e2..47c7d953a 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -1,3 +1,13 @@ + + # Setting up the ntfy push notifications server (optional) The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you. From 4bc715da4be8996a81b402f778b5b1b3ac1e0f2c Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:36 +0900 Subject: [PATCH 888/952] Update docs/configuring-playbook-external-postgres.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-external-postgres.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/configuring-playbook-external-postgres.md b/docs/configuring-playbook-external-postgres.md index ca49d985c..f860f4413 100644 --- a/docs/configuring-playbook-external-postgres.md +++ b/docs/configuring-playbook-external-postgres.md @@ -1,3 +1,10 @@ + + # Using an external PostgreSQL server (optional) By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document. From 825cef5f04a4873a267fb174368f7a2c0cb865c4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:43 +0900 Subject: [PATCH 889/952] Update docs/configuring-playbook-prometheus-grafana.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-prometheus-grafana.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index e88e31b1e..6a32b5ab1 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -1,3 +1,16 @@ + + # Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional) The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you. From 0996b3098f454d5c46d2a2d0dd027859216b1934 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:49 +0900 Subject: [PATCH 890/952] Update docs/configuring-playbook-riot-web.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-riot-web.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md index b967b6b6b..1652f5eb9 100644 --- a/docs/configuring-playbook-riot-web.md +++ b/docs/configuring-playbook-riot-web.md @@ -1,3 +1,11 @@ + + # Configuring Riot-web (optional) By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application. From c72b8f1726faa144a31521eb9edb4a00c2a032d6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:26:55 +0900 Subject: [PATCH 891/952] Update docs/configuring-playbook-traefik.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-traefik.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md index 489d2e8df..46b236580 100644 --- a/docs/configuring-playbook-traefik.md +++ b/docs/configuring-playbook-traefik.md @@ -1,3 +1,12 @@ + + # Configuring the Traefik reverse-proxy (optional, advanced) By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role for you. If that's okay, you can skip this document. From d467c5f54f82a64d76d47d351c17c26032f74e41 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:00 +0900 Subject: [PATCH 892/952] Update docs/configuring-playbook-s3.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md index 3679b6add..1aa190df5 100644 --- a/docs/configuring-playbook-s3.md +++ b/docs/configuring-playbook-s3.md @@ -1,3 +1,11 @@ + + # Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional) 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. From e3b17186ce25cf34070c57ef2d177194c716e567 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:05 +0900 Subject: [PATCH 893/952] Update docs/faq.md: add a copyright header Signed-off-by: Suguru Hirahara --- docs/faq.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index 04bfde784..9f1ddc6e3 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -1,3 +1,15 @@ + + # Frequently Asked Questions 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)). From 13d54c350452ad658f2df687ea591c1602314611 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:09 +0900 Subject: [PATCH 894/952] Update main.yml for matrix-client-cinny: fix a copyright year Signed-off-by: Suguru Hirahara --- roles/custom/matrix-client-cinny/tasks/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/tasks/main.yml b/roles/custom/matrix-client-cinny/tasks/main.yml index bed3c1803..925e15dcf 100644 --- a/roles/custom/matrix-client-cinny/tasks/main.yml +++ b/roles/custom/matrix-client-cinny/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later From 818794bd837d287d82961c6854ff764a8fb3bf62 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:13 +0900 Subject: [PATCH 895/952] Add license information for CHANGELOG.md Signed-off-by: Suguru Hirahara --- CHANGELOG.md.license | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 CHANGELOG.md.license diff --git a/CHANGELOG.md.license b/CHANGELOG.md.license new file mode 100644 index 000000000..75cfbe6c7 --- /dev/null +++ b/CHANGELOG.md.license @@ -0,0 +1,14 @@ +SPDX-FileCopyrightText: 2018 - 2024 MDAD project contributors +SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2018 Aaron Raimist +SPDX-FileCopyrightText: 2019 Thomas Kuehne +SPDX-FileCopyrightText: 2020 John Goerzen +SPDX-FileCopyrightText: 2020 Julian Foad +SPDX-FileCopyrightText: 2021 Agustin Ferrario +SPDX-FileCopyrightText: 2021 Dan Arnfield +SPDX-FileCopyrightText: 2022 Jost Alemann +SPDX-FileCopyrightText: 2023 Felix Stupp +SPDX-FileCopyrightText: 2023 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From 318b3b7d408c85f26dfdcb364cad127d45a58ac1 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:17 +0900 Subject: [PATCH 896/952] Add license information for obtain_admin_access_token_element_web.png Signed-off-by: Suguru Hirahara --- docs/assets/obtain_admin_access_token_element_web.png.license | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 docs/assets/obtain_admin_access_token_element_web.png.license diff --git a/docs/assets/obtain_admin_access_token_element_web.png.license b/docs/assets/obtain_admin_access_token_element_web.png.license new file mode 100644 index 000000000..e254eb619 --- /dev/null +++ b/docs/assets/obtain_admin_access_token_element_web.png.license @@ -0,0 +1,3 @@ +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr + +SPDX-License-Identifier: AGPL-3.0-or-later From 0223289180199d09a88a429fadc6c07e447d256e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 00:27:21 +0900 Subject: [PATCH 897/952] Update REUSE.toml: sort an item Signed-off-by: Suguru Hirahara --- REUSE.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/REUSE.toml b/REUSE.toml index 0985a21af..076d318ff 100644 --- a/REUSE.toml +++ b/REUSE.toml @@ -10,8 +10,8 @@ path = [ ".github/renovate.json", "collections/requirements.yml", "i18n/.gitignore", - "i18n/requirements.txt", "i18n/PUBLISHED_LANGUAGES", + "i18n/requirements.txt", "roles/custom/**/*.repo", ".editorconfig", ".envrc", From 3f0082e56be3e823b415bb6218a2bd0fc559ea11 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 12:15:48 +0900 Subject: [PATCH 898/952] Update docs/configuring-playbook.md: update the instruction to use git This is based on https://github.com/mother-of-all-self-hosting/mash-playbook/blob/5facc06a3c98cb07b23c137712db256753a4e6ad/docs/configuring-playbook.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 6a867b8d6..df5ca8c85 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -30,7 +30,7 @@ If you've configured your DNS records and retrieved the playbook's source code t 5. edit the inventory hosts file (`inventory/hosts`) to your liking -6. (optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. +6. (optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. The `inventory` directory path is ignored via `.gitignore`, so it won't be part of the playbook repository. You can safely create a new git repository inside that directory with `git init`, etc. 7. (optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md). From 2997fd9eefdf3d21e4871444d1fe7ef6493ec183 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 12:37:37 +0900 Subject: [PATCH 899/952] Add license information to files in group_vars Signed-off-by: Suguru Hirahara --- group_vars/jitsi_jvb_servers | 4 ++ group_vars/matrix_servers.license | 65 +++++++++++++++++++++++++++++++ 2 files changed, 69 insertions(+) create mode 100644 group_vars/matrix_servers.license diff --git a/group_vars/jitsi_jvb_servers b/group_vars/jitsi_jvb_servers index af927c9f1..91d33fead 100644 --- a/group_vars/jitsi_jvb_servers +++ b/group_vars/jitsi_jvb_servers @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2023 Antonis Christofides +# +# SPDX-License-Identifier: AGPL-3.0-or-later + jitsi_architecture: "{{ matrix_architecture }}" jitsi_hostname: "{{ matrix_server_fqn_jitsi }}" jitsi_uid: "{{ matrix_user_uid }}" diff --git a/group_vars/matrix_servers.license b/group_vars/matrix_servers.license new file mode 100644 index 000000000..1325849fc --- /dev/null +++ b/group_vars/matrix_servers.license @@ -0,0 +1,65 @@ +SPDX-FileCopyrightText: 2019 - 2021 Aaron Raimist +SPDX-FileCopyrightText: 2019 - 2021 Stuart Mumford +SPDX-FileCopyrightText: 2019 - 2025 MDAD project contributors +SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Dan Arnfield +SPDX-FileCopyrightText: 2019 Daniel Hoffend +SPDX-FileCopyrightText: 2019 Edgars Voroboks +SPDX-FileCopyrightText: 2019 Thomas Kuehne +SPDX-FileCopyrightText: 2020 - 2021 Sabine Laszakovits +SPDX-FileCopyrightText: 2020 Björn Marten +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 David Gnedt +SPDX-FileCopyrightText: 2020 Horvath Gergely +SPDX-FileCopyrightText: 2020 Hugues Morisset +SPDX-FileCopyrightText: 2020 Marcel Partap +SPDX-FileCopyrightText: 2020 Max Klenk +SPDX-FileCopyrightText: 2020 Rodrigo Belem +SPDX-FileCopyrightText: 2020 Scott Crossen +SPDX-FileCopyrightText: 2020 Tulir Asokan +SPDX-FileCopyrightText: 2020 Zach Mertes +SPDX-FileCopyrightText: 2021 - 2022 Matthew Cengia +SPDX-FileCopyrightText: 2021 - 2023 Shreyas Ajjarapu +SPDX-FileCopyrightText: 2021 Ahmad Haghighi +SPDX-FileCopyrightText: 2021 Alexandar Mechev +SPDX-FileCopyrightText: 2021 Béla Becker +SPDX-FileCopyrightText: 2021 Christos Karamolegkos +SPDX-FileCopyrightText: 2021 Cody Neiman +SPDX-FileCopyrightText: 2021 Marc Leuser +SPDX-FileCopyrightText: 2021 Marcus Proest +SPDX-FileCopyrightText: 2021 Panagiotis Georgiadis +SPDX-FileCopyrightText: 2021 Raymond Coetzee +SPDX-FileCopyrightText: 2021 Stuart Thomson +SPDX-FileCopyrightText: 2021 Toni Spets +SPDX-FileCopyrightText: 2021 Yannick Goossens +SPDX-FileCopyrightText: 2021 boris runakov +SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 - 2023 Samuel Meenzen +SPDX-FileCopyrightText: 2022 - 2024 Charles Wright +SPDX-FileCopyrightText: 2022 - 2024 László Várady +SPDX-FileCopyrightText: 2022 - 2025 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Arthur Brugière +SPDX-FileCopyrightText: 2022 Devin Dooley +SPDX-FileCopyrightText: 2022 Hefty Zauk +SPDX-FileCopyrightText: 2022 Jim Myhrberg +SPDX-FileCopyrightText: 2022 Jip J. Dekker +SPDX-FileCopyrightText: 2022 Julian Foad +SPDX-FileCopyrightText: 2022 Kim Brose +SPDX-FileCopyrightText: 2022 Marko Weltzer +SPDX-FileCopyrightText: 2022 Shaleen Jain +SPDX-FileCopyrightText: 2022 Vladimir Panteleev +SPDX-FileCopyrightText: 2023 - 2024 Michael Hollister +SPDX-FileCopyrightText: 2023 - 2024 Pierre 'McFly' Marty +SPDX-FileCopyrightText: 2023 Antonis Christofides +SPDX-FileCopyrightText: 2023 Benjamin Kampmann +SPDX-FileCopyrightText: 2023 Catalan Lover +SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman +SPDX-FileCopyrightText: 2023 Johan Swetzén +SPDX-FileCopyrightText: 2023 Kabir Kwatra +SPDX-FileCopyrightText: 2023 Thomas Baer +SPDX-FileCopyrightText: 2024 Chasethechicken +SPDX-FileCopyrightText: 2024 Fabio Bonelli +SPDX-FileCopyrightText: 2024 Igor Goldenberg +SPDX-FileCopyrightText: 2024 Suguru Hirahara + +SPDX-License-Identifier: AGPL-3.0-or-later From c385bee7afcceb703911b1bbf8e01d639357aff2 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 12:43:41 +0900 Subject: [PATCH 900/952] Re-run "reuse annotate" to sort statements Signed-off-by: Suguru Hirahara --- docs/ansible.md | 2 +- docs/configuring-captcha.md | 2 +- docs/configuring-dns.md | 4 ++-- docs/configuring-playbook-alertmanager-receiver.md | 2 +- docs/configuring-playbook-appservice-double-puppet.md | 2 +- docs/configuring-playbook-backup-borg.md | 4 ++-- docs/configuring-playbook-bot-baibot.md | 2 +- docs/configuring-playbook-bot-buscarron.md | 2 +- docs/configuring-playbook-bot-chatgpt.md | 2 +- docs/configuring-playbook-bot-go-neb.md | 2 +- docs/configuring-playbook-bridge-appservice-kakaotalk.md | 2 +- docs/configuring-playbook-bridge-appservice-webhooks.md | 2 +- docs/configuring-playbook-bridge-matrix-bridge-sms.md | 2 +- docs/configuring-playbook-bridge-mautrix-facebook.md | 6 +++--- docs/configuring-playbook-bridge-mautrix-hangouts.md | 2 +- docs/configuring-playbook-bridge-mautrix-instagram.md | 2 +- .../configuring-playbook-bridge-mautrix-meta-messenger.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-discord.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-skype.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-slack.md | 2 +- docs/configuring-playbook-bridge-mx-puppet-steam.md | 2 +- docs/configuring-playbook-cactus-comments.md | 2 +- docs/configuring-playbook-client-cinny.md | 2 +- docs/configuring-playbook-conduit.md | 3 +-- docs/configuring-playbook-dendrite.md | 2 +- docs/configuring-playbook-dimension.md | 8 ++++---- docs/configuring-playbook-email2matrix.md | 2 +- docs/configuring-playbook-etherpad.md | 2 +- docs/configuring-playbook-jitsi.md | 4 ++-- docs/configuring-playbook-ma1sd.md | 4 ++-- ...configuring-playbook-matrix-ldap-registration-proxy.md | 2 +- docs/configuring-playbook-pantalaimon.md | 2 +- docs/configuring-playbook-postgres-backup.md | 2 +- docs/configuring-playbook-sliding-sync-proxy.md | 4 ++-- docs/configuring-playbook.md | 2 +- docs/installing.md | 6 +++--- docs/maintenance-and-troubleshooting.md | 2 +- docs/maintenance-postgres.md | 2 +- docs/maintenance-upgrading-services.md | 2 +- docs/obtaining-access-tokens.md | 2 +- docs/prerequisites.md | 4 ++-- docs/registering-users.md | 4 ++-- .../systemd/matrix-bot-baibot.service.j2.license | 2 +- roles/custom/matrix-bot-buscarron/tasks/main.yml | 2 +- .../custom/matrix-bot-buscarron/tasks/validate_config.yml | 2 +- roles/custom/matrix-bot-buscarron/templates/labels.j2 | 2 +- .../systemd/matrix-bot-buscarron.service.j2.license | 2 +- roles/custom/matrix-bot-chatgpt/defaults/main.yml | 2 +- roles/custom/matrix-bot-chatgpt/templates/env.j2 | 2 +- .../systemd/matrix-bot-chatgpt.service.j2.license | 2 +- roles/custom/matrix-bot-go-neb/defaults/main.yml | 2 +- roles/custom/matrix-bot-go-neb/tasks/install.yml | 6 +++--- roles/custom/matrix-bot-go-neb/tasks/main.yml | 2 +- roles/custom/matrix-bot-go-neb/tasks/uninstall.yml | 2 +- .../custom/matrix-bot-honoroit/tasks/setup_uninstall.yml | 2 +- .../tasks/setup_install.yml | 2 +- .../templates/config.yaml.j2.license | 2 +- .../matrix-bridge-appservice-webhooks/defaults/main.yml | 4 ++-- .../matrix-bridge-appservice-webhooks/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 2 +- .../systemd/matrix-appservice-webhooks.service.j2.license | 2 +- .../matrix-bridge-go-skype-bridge/defaults/main.yml | 4 ++-- roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml | 2 +- .../matrix-bridge-go-skype-bridge/tasks/setup_install.yml | 2 +- .../tasks/setup_uninstall.yml | 2 +- .../tasks/validate_config.yml | 2 +- .../templates/config.yaml.j2.license | 4 ++-- .../systemd/matrix-go-skype-bridge.service.j2.license | 2 +- .../matrix-bridge-mautrix-facebook/defaults/main.yml | 8 ++++---- .../tasks/setup_install.yml | 4 ++-- .../templates/config.yaml.j2.license | 4 ++-- .../matrix-bridge-mautrix-instagram/defaults/main.yml | 6 +++--- .../custom/matrix-bridge-mautrix-instagram/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 4 ++-- .../tasks/setup_uninstall.yml | 2 +- .../tasks/validate_config.yml | 2 +- .../templates/config.yaml.j2.license | 4 ++-- .../matrix-bridge-mx-puppet-discord/defaults/main.yml | 4 ++-- .../custom/matrix-bridge-mx-puppet-discord/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 4 ++-- .../matrix-bridge-mx-puppet-groupme/defaults/main.yml | 6 +++--- .../custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 4 ++-- .../tasks/setup_uninstall.yml | 2 +- .../matrix-bridge-mx-puppet-instagram/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 2 +- .../matrix-bridge-mx-puppet-slack/defaults/main.yml | 4 ++-- roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml | 2 +- .../matrix-bridge-mx-puppet-slack/tasks/setup_install.yml | 2 +- .../matrix-bridge-mx-puppet-steam/defaults/main.yml | 4 ++-- roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml | 2 +- .../matrix-bridge-mx-puppet-steam/tasks/setup_install.yml | 4 ++-- .../matrix-bridge-mx-puppet-twitter/defaults/main.yml | 4 ++-- .../custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml | 2 +- .../tasks/setup_install.yml | 4 ++-- .../custom/matrix-bridge-wechat/tasks/validate_config.yml | 1 - .../matrix-bridge-wechat/templates/config.yaml.j2.license | 2 +- .../matrix-cactus-comments-client/tasks/install.yml | 2 +- roles/custom/matrix-cactus-comments/tasks/main.yml | 2 +- .../matrix-cactus-comments/tasks/setup_uninstall.yml | 2 +- .../matrix-cactus-comments/tasks/validate_config.yml | 2 +- .../matrix-cactus-comments/templates/env.j2.license | 2 +- .../systemd/matrix-cactus-comments.service.j2.license | 2 +- roles/custom/matrix-client-cinny/defaults/main.yml | 8 ++++---- roles/custom/matrix-client-cinny/tasks/main.yml | 2 +- roles/custom/matrix-client-cinny/tasks/self_check.yml | 2 +- roles/custom/matrix-client-cinny/tasks/setup_install.yml | 2 +- .../custom/matrix-client-cinny/tasks/setup_uninstall.yml | 2 +- .../custom/matrix-client-cinny/tasks/validate_config.yml | 2 +- .../matrix-client-cinny/templates/nginx.conf.j2.license | 2 +- .../systemd/matrix-client-cinny.service.j2.license | 2 +- roles/custom/matrix-client-hydrogen/defaults/main.yml | 4 ++-- roles/custom/matrix-client-hydrogen/tasks/main.yml | 2 +- roles/custom/matrix-client-hydrogen/tasks/self_check.yml | 2 +- .../custom/matrix-client-hydrogen/tasks/setup_install.yml | 2 +- .../templates/config.json.j2.license | 2 +- .../systemd/matrix-client-hydrogen.service.j2.license | 2 +- roles/custom/matrix-dimension/defaults/main.yml | 8 ++++---- roles/custom/matrix-dimension/tasks/main.yml | 2 +- roles/custom/matrix-dimension/tasks/setup_install.yml | 4 ++-- roles/custom/matrix-dimension/tasks/validate_config.yml | 4 ++-- .../templates/systemd/matrix-dimension.service.j2.license | 4 ++-- roles/custom/matrix-dimension/vars/main.yml | 2 +- roles/custom/matrix-ma1sd/defaults/main.yml | 6 +++--- roles/custom/matrix-ma1sd/tasks/main.yml | 2 +- roles/custom/matrix-ma1sd/tasks/self_check.yml | 4 ++-- roles/custom/matrix-ma1sd/tasks/setup_install.yml | 6 +++--- roles/custom/matrix-ma1sd/tasks/validate_config.yml | 2 +- .../templates/systemd/matrix-ma1sd.service.j2.license | 4 ++-- roles/custom/matrix-pantalaimon/tasks/install.yml | 2 +- roles/custom/matrix-rageshake/defaults/main.yml | 2 +- roles/custom/matrix-rageshake/tasks/install.yml | 2 +- roles/custom/matrix-rageshake/tasks/validate_config.yml | 2 +- .../templates/systemd/matrix-rageshake.service.j2.license | 2 +- roles/custom/matrix-registration/defaults/main.yml | 2 +- roles/custom/matrix-registration/tasks/setup_install.yml | 2 +- roles/custom/matrix-sliding-sync/defaults/main.yml | 4 ++-- 137 files changed, 191 insertions(+), 193 deletions(-) diff --git a/docs/ansible.md b/docs/ansible.md index a4a595002..ff0398374 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -1,7 +1,7 @@ diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md index d2bac9d42..fe67d1768 100644 --- a/docs/configuring-playbook-appservice-double-puppet.md +++ b/docs/configuring-playbook-appservice-double-puppet.md @@ -1,6 +1,6 @@ diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index cef21d45a..dabb8911c 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -1,8 +1,8 @@ diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md index 45266d338..969c1c93d 100644 --- a/docs/configuring-playbook-bot-buscarron.md +++ b/docs/configuring-playbook-bot-buscarron.md @@ -1,6 +1,6 @@ diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md index f135d9b84..43b3d2522 100644 --- a/docs/configuring-playbook-bridge-mx-puppet-discord.md +++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md @@ -1,6 +1,6 @@ diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md index ef5e381fe..76a3c9666 100644 --- a/docs/configuring-playbook-conduit.md +++ b/docs/configuring-playbook-conduit.md @@ -1,6 +1,5 @@ diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md index 4eaefb76d..a1d17b4c1 100644 --- a/docs/configuring-playbook-dimension.md +++ b/docs/configuring-playbook-dimension.md @@ -1,13 +1,13 @@ diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 4a9287dd8..5c414cb00 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -1,6 +1,6 @@ diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 08aa8ef71..10c65643a 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -1,6 +1,6 @@ diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md index 21d1c07ae..bd3e4b84c 100644 --- a/docs/maintenance-and-troubleshooting.md +++ b/docs/maintenance-and-troubleshooting.md @@ -1,7 +1,7 @@ diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md index c6ef5f62d..7f0f1bc17 100644 --- a/docs/maintenance-upgrading-services.md +++ b/docs/maintenance-upgrading-services.md @@ -1,9 +1,9 @@ diff --git a/docs/prerequisites.md b/docs/prerequisites.md index dc0b73e5d..e53246d98 100644 --- a/docs/prerequisites.md +++ b/docs/prerequisites.md @@ -2,9 +2,9 @@ SPDX-FileCopyrightText: 2018 - 2025 Slavi Pantaleev SPDX-FileCopyrightText: 2019 - 2022 Aaron Raimist SPDX-FileCopyrightText: 2019 - 2023 MDAD project contributors -SPDX-FileCopyrightText: 2024 Nikita Chernyi -SPDX-FileCopyrightText: 2024 Fabio Bonelli SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara +SPDX-FileCopyrightText: 2024 Fabio Bonelli +SPDX-FileCopyrightText: 2024 Nikita Chernyi SPDX-License-Identifier: AGPL-3.0-or-later --> diff --git a/docs/registering-users.md b/docs/registering-users.md index b4ef6710e..8de5bfeb3 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -1,9 +1,9 @@ diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license index fadc9dc1e..c24b3ae88 100644 --- a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2024 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 Slavi Pantaleev SPDX-FileCopyrightText: 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-buscarron/tasks/main.yml b/roles/custom/matrix-bot-buscarron/tasks/main.yml index b90cfaa25..adfc56db8 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/main.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml index e07cbffef..4890655b6 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Nikita Chernyi # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-buscarron/templates/labels.j2 b/roles/custom/matrix-bot-buscarron/templates/labels.j2 index a302c5269..6376a5412 100644 --- a/roles/custom/matrix-bot-buscarron/templates/labels.j2 +++ b/roles/custom/matrix-bot-buscarron/templates/labels.j2 @@ -1,6 +1,6 @@ {# -SPDX-FileCopyrightText: 2023 Nikita Chernyi SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Nikita Chernyi SPDX-License-Identifier: AGPL-3.0-or-later #} diff --git a/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license index 70a8f1992..2195e952c 100644 --- a/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license +++ b/roles/custom/matrix-bot-buscarron/templates/systemd/matrix-bot-buscarron.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2022 Nikita Chernyi SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Nikita Chernyi SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-chatgpt/defaults/main.yml b/roles/custom/matrix-bot-chatgpt/defaults/main.yml index 3727962db..aa65a7ae4 100644 --- a/roles/custom/matrix-bot-chatgpt/defaults/main.yml +++ b/roles/custom/matrix-bot-chatgpt/defaults/main.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2023 MDAD project contributors # SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2023 Joe Kappus +# SPDX-FileCopyrightText: 2023 MDAD project contributors # SPDX-FileCopyrightText: 2023 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen # SPDX-FileCopyrightText: 2024 Suguru Hirahara diff --git a/roles/custom/matrix-bot-chatgpt/templates/env.j2 b/roles/custom/matrix-bot-chatgpt/templates/env.j2 index bbb6d01e3..2abf4327b 100644 --- a/roles/custom/matrix-bot-chatgpt/templates/env.j2 +++ b/roles/custom/matrix-bot-chatgpt/templates/env.j2 @@ -1,7 +1,7 @@ {# +SPDX-FileCopyrightText: 2023 Joe Kappus SPDX-FileCopyrightText: 2023 MDAD project contributors SPDX-FileCopyrightText: 2023 Slavi Pantaleev -SPDX-FileCopyrightText: 2023 Joe Kappus SPDX-FileCopyrightText: 2024 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license index 5eda5a739..8970217f2 100644 --- a/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license +++ b/roles/custom/matrix-bot-chatgpt/templates/systemd/matrix-bot-chatgpt.service.j2.license @@ -1,5 +1,5 @@ +SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev SPDX-FileCopyrightText: 2023 MDAD project contributors SPDX-FileCopyrightText: 2023 Vladimir Panteleev -SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-go-neb/defaults/main.yml b/roles/custom/matrix-bot-go-neb/defaults/main.yml index cff674cff..5d5e8b97f 100644 --- a/roles/custom/matrix-bot-go-neb/defaults/main.yml +++ b/roles/custom/matrix-bot-go-neb/defaults/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen diff --git a/roles/custom/matrix-bot-go-neb/tasks/install.yml b/roles/custom/matrix-bot-go-neb/tasks/install.yml index ee418fd0f..d590bc999 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/install.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/install.yml @@ -1,8 +1,8 @@ # SPDX-FileCopyrightText: 2021 Yannick Goossens -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Jim Myhrberg -# SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren # diff --git a/roles/custom/matrix-bot-go-neb/tasks/main.yml b/roles/custom/matrix-bot-go-neb/tasks/main.yml index 666296156..09cf4bb84 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/main.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2021 Yannick Goossens -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml b/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml index 56cee88e1..ad862821d 100644 --- a/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml +++ b/roles/custom/matrix-bot-go-neb/tasks/uninstall.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # diff --git a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml index 1ab17b516..28456d53c 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml @@ -1,7 +1,7 @@ +# SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2022 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2024 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml index e8442c0b9..ebe0815a2 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/setup_install.yml @@ -1,8 +1,8 @@ # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford # SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license index f9a202b63..8b6d0c244 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2.license @@ -1,5 +1,5 @@ -SPDX-FileCopyrightText: 2022 Slavi Pantaleev SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 Slavi Pantaleev SPDX-FileCopyrightText: 2023 Nikita Chernyi SPDX-FileCopyrightText: 2024 Suguru Hirahara diff --git a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml index fa17baf34..b90735561 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/defaults/main.yml @@ -1,9 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Björn Marten # SPDX-FileCopyrightText: 2020 David Gnedt -# SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 - 2023 MDAD project contributors -# SPDX-FileCopyrightText: 2021 Béla Becker # SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Béla Becker # SPDX-FileCopyrightText: 2021 boris runakov # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml index cb4c68829..bc6a17105 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Björn Marten -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml index 507918a5e..208399355 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/setup_install.yml @@ -2,8 +2,8 @@ # SPDX-FileCopyrightText: 2020 Chris van Dijk # SPDX-FileCopyrightText: 2020 MDAD project contributors # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license index 63b731d1e..fe9fa1747 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license +++ b/roles/custom/matrix-bridge-appservice-webhooks/templates/systemd/matrix-appservice-webhooks.service.j2.license @@ -1,8 +1,8 @@ +SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev SPDX-FileCopyrightText: 2020 Björn Marten SPDX-FileCopyrightText: 2020 Chris van Dijk SPDX-FileCopyrightText: 2020 MDAD project contributors SPDX-FileCopyrightText: 2020 Scott Crossen SPDX-FileCopyrightText: 2020 Stefan Warnat -SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml index a27f22905..0b8c9b3e0 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/defaults/main.yml @@ -1,8 +1,8 @@ -# SPDX-FileCopyrightText: 2022 Vladimir Panteleev -# SPDX-FileCopyrightText: 2022 - 2025 MDAD project contributors # SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 - 2025 MDAD project contributors # SPDX-FileCopyrightText: 2022 Arthur Brugière +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2023 Samuel Meenzen # SPDX-FileCopyrightText: 2024 Suguru Hirahara # diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml index 18b488a44..a92f08d98 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml index 1f142759f..5d05a3540 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_install.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2024 David Mehren # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml index 6215ac8b5..b7d3373c3 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/setup_uninstall.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml index 12f4172af..49e3eafcb 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Vladimir Panteleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license index 227ac864a..c9507bbdb 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license +++ b/roles/custom/matrix-bridge-go-skype-bridge/templates/config.yaml.j2.license @@ -1,6 +1,6 @@ -SPDX-FileCopyrightText: 2022 Vladimir Panteleev -SPDX-FileCopyrightText: 2022 Nikita Chernyi SPDX-FileCopyrightText: 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 Nikita Chernyi +SPDX-FileCopyrightText: 2022 Vladimir Panteleev SPDX-FileCopyrightText: 2024 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license index 6ef6a26f8..9815cd215 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license +++ b/roles/custom/matrix-bridge-go-skype-bridge/templates/systemd/matrix-go-skype-bridge.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2022 Vladimir Panteleev SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Vladimir Panteleev SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml index c4a80ba70..0fe7f52f1 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml @@ -1,12 +1,12 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 Horvath Gergely +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors -# SPDX-FileCopyrightText: 2021 Arthur Brugière # SPDX-FileCopyrightText: 2021 Aaron Raimist -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2021 Arthur Brugière # SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2023 Adrien le Maire # SPDX-FileCopyrightText: 2023 Samuel Meenzen # diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml index 12907c16b..36fe8fabb 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/setup_install.yml @@ -1,12 +1,12 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2020 Chris van Dijk # SPDX-FileCopyrightText: 2020 Horvath Gergely # SPDX-FileCopyrightText: 2020 MDAD project contributors -# SPDX-FileCopyrightText: 2020 Chris van Dijk # SPDX-FileCopyrightText: 2020 Stuart Mumford # SPDX-FileCopyrightText: 2021 Aaron Raimist -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license index 309dd31e7..aa26685bf 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license +++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2.license @@ -1,9 +1,9 @@ -SPDX-FileCopyrightText: 2019 Hugues Morisset SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2019 Hugues Morisset SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi SPDX-FileCopyrightText: 2022 László Várady SPDX-FileCopyrightText: 2022 Olivér Falvai -SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi SPDX-FileCopyrightText: 2023 Adrien le Maire SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml index b2acb3afc..1304d7586 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml @@ -1,10 +1,10 @@ -# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2021 - 2024 MDAD project contributors # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 Aaron Raimist -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2023 Adrien le Maire # SPDX-FileCopyrightText: 2023 Samuel Meenzen # diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml index b662b59d4..1dcc341fb 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2021 Marcus Proest -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2023 Adrien le Maire # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml index f122dff98..21e4e5f44 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_install.yml @@ -1,7 +1,7 @@ -# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml index da2d3f98e..de533aa7c 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/setup_uninstall.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml index ef430fcbd..2fa0a14fd 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Marcus Proest # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license index 6e01bd18d..89b223f9b 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license +++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2.license @@ -1,8 +1,8 @@ -SPDX-FileCopyrightText: 2021 Marcus Proest SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors -SPDX-FileCopyrightText: 2022 László Várady +SPDX-FileCopyrightText: 2021 Marcus Proest SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 László Várady SPDX-FileCopyrightText: 2023 Adrien le Maire SPDX-FileCopyrightText: 2023 Kevin Kengen SPDX-FileCopyrightText: 2024 Suguru Hirahara diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml index 966524ab4..5cda2b0f4 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2020 Hugues Morisset -# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Hugues Morisset # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Daniel Sonck # SPDX-FileCopyrightText: 2022 Marko Weltzer diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml index 273640969..67e4948e4 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Hugues Morisset -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml index 268cf0364..af1717a0f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-discord/tasks/setup_install.yml @@ -1,8 +1,8 @@ -# SPDX-FileCopyrightText: 2020 Hugues Morisset # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Hugues Morisset # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml index 2487ab7d7..a4d7570ef 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml @@ -1,10 +1,10 @@ -# SPDX-FileCopyrightText: 2021 Cody Neiman -# SPDX-FileCopyrightText: 2021 MDAD project contributors # SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 Ahmad Haghighi +# SPDX-FileCopyrightText: 2021 Cody Neiman +# SPDX-FileCopyrightText: 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi -# SPDX-FileCopyrightText: 2022 Cody Wyatt Neiman # SPDX-FileCopyrightText: 2024 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml index 2deab4a92..8b6e0be39 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2021 Cody Neiman -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml index 28f5700b5..5e09ca887 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_install.yml @@ -1,7 +1,7 @@ -# SPDX-FileCopyrightText: 2021 Cody Neiman # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2021 Cody Neiman # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml index 04a7eed54..6f698ca62 100644 --- a/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-bridge-mx-puppet-groupme/tasks/setup_uninstall.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Cody Neiman # SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Cody Neiman # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml index 81a6441d2..c2944596f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml index c57f86fac..1846ede1f 100644 --- a/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-instagram/tasks/setup_install.yml @@ -1,8 +1,8 @@ # SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml index 4b4eb76eb..338eb3691 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml @@ -1,13 +1,13 @@ -# SPDX-FileCopyrightText: 2020 Rodrigo Belem # SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Hugues Morisset +# SPDX-FileCopyrightText: 2020 Rodrigo Belem # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2021 Marcel Ackermann +# SPDX-FileCopyrightText: 2022 Daniel Sonck # SPDX-FileCopyrightText: 2022 Jim Myhrberg # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi -# SPDX-FileCopyrightText: 2022 Daniel Sonck # SPDX-FileCopyrightText: 2023 Samuel Meenzen # SPDX-FileCopyrightText: 2024 Suguru Hirahara # diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml index 69ac4bfb7..3e66fd822 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Rodrigo Belem -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml index f194959d3..55e0cdecf 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/setup_install.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Rodrigo Belem -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml index b42e37f7f..65161cf54 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2020 Hugues Morisset -# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Hugues Morisset # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml index bae270632..a7619e431 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Hugues Morisset -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml index ef7c7ee13..298913aec 100644 --- a/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-steam/tasks/setup_install.yml @@ -1,9 +1,9 @@ +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Hugues Morisset # SPDX-FileCopyrightText: 2020 Panagiotis Vasilopoulos -# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml index 2b8f40c97..c556cda4a 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2020 Tulir Asokan -# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 - 2021 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Tulir Asokan # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml index fb8d79a78..b534f22c0 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 Tulir Asokan -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml index f128a990f..2f6a7807e 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/setup_install.yml @@ -1,8 +1,8 @@ -# SPDX-FileCopyrightText: 2020 Tulir Asokan # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2020 Tulir Asokan # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml index 6400ccfd3..c0eb73927 100644 --- a/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-wechat/tasks/validate_config.yml @@ -2,7 +2,6 @@ # # SPDX-License-Identifier: AGPL-3.0-or-later - --- - name: Fail if required WeChat settings not defined diff --git a/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license b/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license index b94e0d95e..9470a96a3 100644 --- a/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license +++ b/roles/custom/matrix-bridge-wechat/templates/config.yaml.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2024 Slavi Pantaleev SPDX-FileCopyrightText: 2024 Nikita Chernyi +SPDX-FileCopyrightText: 2024 Slavi Pantaleev SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments-client/tasks/install.yml b/roles/custom/matrix-cactus-comments-client/tasks/install.yml index 466a9900e..6a86df4ce 100644 --- a/roles/custom/matrix-cactus-comments-client/tasks/install.yml +++ b/roles/custom/matrix-cactus-comments-client/tasks/install.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2024 David Mehren +# SPDX-FileCopyrightText: 2024 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/tasks/main.yml b/roles/custom/matrix-cactus-comments/tasks/main.yml index 00f3c4b1f..6d2a418ff 100644 --- a/roles/custom/matrix-cactus-comments/tasks/main.yml +++ b/roles/custom/matrix-cactus-comments/tasks/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml b/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml index 451a2db0b..4eebcacaf 100644 --- a/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-cactus-comments/tasks/setup_uninstall.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml index 1fccefc47..c26b0b8f1 100644 --- a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml +++ b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/templates/env.j2.license b/roles/custom/matrix-cactus-comments/templates/env.j2.license index 28d697fbe..da108d1da 100644 --- a/roles/custom/matrix-cactus-comments/templates/env.j2.license +++ b/roles/custom/matrix-cactus-comments/templates/env.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr SPDX-FileCopyrightText: 2022 Slavi Pantaleev SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license index c3b55344f..1c63cc4e4 100644 --- a/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license +++ b/roles/custom/matrix-cactus-comments/templates/systemd/matrix-cactus-comments.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index fa0597af6..405ecc82f 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -1,8 +1,8 @@ -# SPDX-FileCopyrightText: 2022 MDAD project contributors -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 László Várady # SPDX-FileCopyrightText: 2022 - 2024 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 László Várady +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2023 Samuel Meenzen # SPDX-FileCopyrightText: 2024 Suguru Hirahara # diff --git a/roles/custom/matrix-client-cinny/tasks/main.yml b/roles/custom/matrix-client-cinny/tasks/main.yml index 925e15dcf..935b4ee03 100644 --- a/roles/custom/matrix-client-cinny/tasks/main.yml +++ b/roles/custom/matrix-client-cinny/tasks/main.yml @@ -1,6 +1,6 @@ +# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/tasks/self_check.yml b/roles/custom/matrix-client-cinny/tasks/self_check.yml index 6bf0d2187..054fdf87e 100644 --- a/roles/custom/matrix-client-cinny/tasks/self_check.yml +++ b/roles/custom/matrix-client-cinny/tasks/self_check.yml @@ -1,6 +1,6 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/tasks/setup_install.yml b/roles/custom/matrix-client-cinny/tasks/setup_install.yml index 2c19d421d..228aa0614 100644 --- a/roles/custom/matrix-client-cinny/tasks/setup_install.yml +++ b/roles/custom/matrix-client-cinny/tasks/setup_install.yml @@ -1,7 +1,7 @@ +# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi -# SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren # diff --git a/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml b/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml index 0474902ba..7a8b5f1bc 100644 --- a/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml +++ b/roles/custom/matrix-client-cinny/tasks/setup_uninstall.yml @@ -1,7 +1,7 @@ # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Sebastian Gumprich +# SPDX-FileCopyrightText: 2022 Slavi Pantaleev # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/tasks/validate_config.yml b/roles/custom/matrix-client-cinny/tasks/validate_config.yml index e267b93fe..b3e324a38 100644 --- a/roles/custom/matrix-client-cinny/tasks/validate_config.yml +++ b/roles/custom/matrix-client-cinny/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 MDAD project contributors # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license b/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license index ea80b31e7..ec432fa3c 100644 --- a/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license +++ b/roles/custom/matrix-client-cinny/templates/nginx.conf.j2.license @@ -1,5 +1,5 @@ -SPDX-FileCopyrightText: 2022 MDAD project contributors SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors SPDX-FileCopyrightText: 2024 James Reilly SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license index 69c513d50..c751d3d6f 100644 --- a/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license +++ b/roles/custom/matrix-client-cinny/templates/systemd/matrix-client-cinny.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2022 MDAD project contributors SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2022 MDAD project contributors SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/defaults/main.yml b/roles/custom/matrix-client-hydrogen/defaults/main.yml index c31fc3002..eae7aed87 100644 --- a/roles/custom/matrix-client-hydrogen/defaults/main.yml +++ b/roles/custom/matrix-client-hydrogen/defaults/main.yml @@ -1,11 +1,11 @@ # SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist # SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors # SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2023 Nikita Chernyi +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Matthew Cengia -# SPDX-FileCopyrightText: 2023 Samuel Meenzen # SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2023 Samuel Meenzen # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/tasks/main.yml b/roles/custom/matrix-client-hydrogen/tasks/main.yml index f5073ce9c..838b82a47 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/main.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2021 Aaron Raimist # SPDX-FileCopyrightText: 2021 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2021 Aaron Raimist # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/tasks/self_check.yml b/roles/custom/matrix-client-hydrogen/tasks/self_check.yml index 2a894593c..b89cddc61 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/self_check.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/self_check.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml b/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml index 18c06f3c8..f720fe5f5 100644 --- a/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml +++ b/roles/custom/matrix-client-hydrogen/tasks/setup_install.yml @@ -1,9 +1,9 @@ # SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2022 Matthew Cengia # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich -# SPDX-FileCopyrightText: 2022 Matthew Cengia # SPDX-FileCopyrightText: 2023 Julian Foad # SPDX-FileCopyrightText: 2024 David Mehren # diff --git a/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license b/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license index 86cf6f8f1..a4ca23eb3 100644 --- a/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license +++ b/roles/custom/matrix-client-hydrogen/templates/config.json.j2.license @@ -1,7 +1,7 @@ SPDX-FileCopyrightText: 2021 - 2022 Aaron Raimist -SPDX-FileCopyrightText: 2022 Nikita Chernyi SPDX-FileCopyrightText: 2022 - 2023 Slavi Pantaleev SPDX-FileCopyrightText: 2022 Matthew Cengia +SPDX-FileCopyrightText: 2022 Nikita Chernyi SPDX-FileCopyrightText: 2023 Sergio Durigan Junior SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license index f23ca62d3..0379e85ae 100644 --- a/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license +++ b/roles/custom/matrix-client-hydrogen/templates/systemd/matrix-client-hydrogen.service.j2.license @@ -1,5 +1,5 @@ -SPDX-FileCopyrightText: 2021 Aaron Raimist SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2021 Aaron Raimist SPDX-FileCopyrightText: 2022 Matthew Cengia SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml index ba36b8c07..8d4a11c7e 100644 --- a/roles/custom/matrix-dimension/defaults/main.yml +++ b/roles/custom/matrix-dimension/defaults/main.yml @@ -1,11 +1,11 @@ -# SPDX-FileCopyrightText: 2019 Edgars Voroboks -# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 - 2021 MDAD project contributors -# SPDX-FileCopyrightText: 2019 Sylvia van Os +# SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Edgars Voroboks +# SPDX-FileCopyrightText: 2019 Sylvia van Os # SPDX-FileCopyrightText: 2020 Chris van Dijk -# SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen diff --git a/roles/custom/matrix-dimension/tasks/main.yml b/roles/custom/matrix-dimension/tasks/main.yml index 0018acf10..19385f106 100644 --- a/roles/custom/matrix-dimension/tasks/main.yml +++ b/roles/custom/matrix-dimension/tasks/main.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2019 Edgars Voroboks # SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Edgars Voroboks # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dimension/tasks/setup_install.yml b/roles/custom/matrix-dimension/tasks/setup_install.yml index 03fee6a99..5aaeb6d1e 100644 --- a/roles/custom/matrix-dimension/tasks/setup_install.yml +++ b/roles/custom/matrix-dimension/tasks/setup_install.yml @@ -1,9 +1,9 @@ # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2021 MDAD project contributors -# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2021 Yannick Goossens # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-dimension/tasks/validate_config.yml b/roles/custom/matrix-dimension/tasks/validate_config.yml index f7b32e389..6fa3a8d21 100644 --- a/roles/custom/matrix-dimension/tasks/validate_config.yml +++ b/roles/custom/matrix-dimension/tasks/validate_config.yml @@ -1,6 +1,6 @@ -# SPDX-FileCopyrightText: 2019 Edgars Voroboks -# SPDX-FileCopyrightText: 2019 Dan Arnfield # SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2019 Edgars Voroboks # SPDX-FileCopyrightText: 2020 Chris van Dijk # SPDX-FileCopyrightText: 2022 Marko Weltzer # diff --git a/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license index 0db4becf9..22f65f580 100644 --- a/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license +++ b/roles/custom/matrix-dimension/templates/systemd/matrix-dimension.service.j2.license @@ -1,7 +1,7 @@ -SPDX-FileCopyrightText: 2019 Edgars Voroboks SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev -SPDX-FileCopyrightText: 2019 Sylvia van Os +SPDX-FileCopyrightText: 2019 Edgars Voroboks SPDX-FileCopyrightText: 2019 Hugues De Keyzer +SPDX-FileCopyrightText: 2019 Sylvia van Os SPDX-FileCopyrightText: 2020 Chris van Dijk SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-dimension/vars/main.yml b/roles/custom/matrix-dimension/vars/main.yml index f3ce6a300..4a931a6aa 100644 --- a/roles/custom/matrix-dimension/vars/main.yml +++ b/roles/custom/matrix-dimension/vars/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2019 Edgars Voroboks # SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev +# SPDX-FileCopyrightText: 2019 Edgars Voroboks # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/defaults/main.yml b/roles/custom/matrix-ma1sd/defaults/main.yml index e235c924e..05be4717e 100644 --- a/roles/custom/matrix-ma1sd/defaults/main.yml +++ b/roles/custom/matrix-ma1sd/defaults/main.yml @@ -1,10 +1,10 @@ -# SPDX-FileCopyrightText: 2020 Marcel Partap -# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 Matt Cengia +# SPDX-FileCopyrightText: 2021 Aaron Raimist # SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2021 boris runakov -# SPDX-FileCopyrightText: 2021 Aaron Raimist # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen diff --git a/roles/custom/matrix-ma1sd/tasks/main.yml b/roles/custom/matrix-ma1sd/tasks/main.yml index ee4613b65..5376e5ace 100644 --- a/roles/custom/matrix-ma1sd/tasks/main.yml +++ b/roles/custom/matrix-ma1sd/tasks/main.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/tasks/self_check.yml b/roles/custom/matrix-ma1sd/tasks/self_check.yml index a90ae7a9c..d1a1714a6 100644 --- a/roles/custom/matrix-ma1sd/tasks/self_check.yml +++ b/roles/custom/matrix-ma1sd/tasks/self_check.yml @@ -1,7 +1,7 @@ -# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 MDAD project contributors -# SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2022 Marko Weltzer # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/tasks/setup_install.yml b/roles/custom/matrix-ma1sd/tasks/setup_install.yml index a6bb87c76..93aa2f14e 100644 --- a/roles/custom/matrix-ma1sd/tasks/setup_install.yml +++ b/roles/custom/matrix-ma1sd/tasks/setup_install.yml @@ -1,11 +1,11 @@ -# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Chris van Dijk +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 Matt Cengia # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer -# SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-ma1sd/tasks/validate_config.yml b/roles/custom/matrix-ma1sd/tasks/validate_config.yml index ca7009df4..9e645002c 100644 --- a/roles/custom/matrix-ma1sd/tasks/validate_config.yml +++ b/roles/custom/matrix-ma1sd/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2021 boris runakov # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license index c893e025f..713174173 100644 --- a/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license +++ b/roles/custom/matrix-ma1sd/templates/systemd/matrix-ma1sd.service.j2.license @@ -1,6 +1,6 @@ -SPDX-FileCopyrightText: 2020 Marcel Partap -SPDX-FileCopyrightText: 2020 Chris van Dijk SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2020 Chris van Dijk +SPDX-FileCopyrightText: 2020 Marcel Partap SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors SPDX-FileCopyrightText: 2021 boris runakov diff --git a/roles/custom/matrix-pantalaimon/tasks/install.yml b/roles/custom/matrix-pantalaimon/tasks/install.yml index 4bd4283f7..256aa2f83 100644 --- a/roles/custom/matrix-pantalaimon/tasks/install.yml +++ b/roles/custom/matrix-pantalaimon/tasks/install.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2024 David Mehren # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2024 David Mehren # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index 14092cde2..38a9cf17a 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -1,6 +1,6 @@ +# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2023 Benjamin Kampmann # SPDX-FileCopyrightText: 2023 Samuel Meenzen -# SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-rageshake/tasks/install.yml b/roles/custom/matrix-rageshake/tasks/install.yml index bcba5ee4f..796adf852 100644 --- a/roles/custom/matrix-rageshake/tasks/install.yml +++ b/roles/custom/matrix-rageshake/tasks/install.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2023 Benjamin Kampmann # SPDX-FileCopyrightText: 2023 - 2024 lavi Pantaleev +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann # SPDX-FileCopyrightText: 2024 David Mehren # SPDX-FileCopyrightText: 2025 Suguru Hirahara # diff --git a/roles/custom/matrix-rageshake/tasks/validate_config.yml b/roles/custom/matrix-rageshake/tasks/validate_config.yml index e8b40c459..80db54151 100644 --- a/roles/custom/matrix-rageshake/tasks/validate_config.yml +++ b/roles/custom/matrix-rageshake/tasks/validate_config.yml @@ -1,5 +1,5 @@ -# SPDX-FileCopyrightText: 2023 Benjamin Kampmann # SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2023 Benjamin Kampmann # # SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license index 0c2880506..2d5160f8f 100644 --- a/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license +++ b/roles/custom/matrix-rageshake/templates/systemd/matrix-rageshake.service.j2.license @@ -1,5 +1,5 @@ -SPDX-FileCopyrightText: 2023 Benjamin Kampmann SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev +SPDX-FileCopyrightText: 2023 Benjamin Kampmann SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-registration/defaults/main.yml b/roles/custom/matrix-registration/defaults/main.yml index 0f2298904..40b840f84 100644 --- a/roles/custom/matrix-registration/defaults/main.yml +++ b/roles/custom/matrix-registration/defaults/main.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2021 Aaron Raimist +# SPDX-FileCopyrightText: 2021 Ahmad Haghighi # SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen diff --git a/roles/custom/matrix-registration/tasks/setup_install.yml b/roles/custom/matrix-registration/tasks/setup_install.yml index 06ebc9e41..9a97c1704 100644 --- a/roles/custom/matrix-registration/tasks/setup_install.yml +++ b/roles/custom/matrix-registration/tasks/setup_install.yml @@ -1,7 +1,7 @@ # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Stuart Mumford -# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Jim Myhrberg +# SPDX-FileCopyrightText: 2022 Marko Weltzer # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 Sebastian Gumprich # SPDX-FileCopyrightText: 2024 David Mehren diff --git a/roles/custom/matrix-sliding-sync/defaults/main.yml b/roles/custom/matrix-sliding-sync/defaults/main.yml index 036b8023d..6e1e2c10f 100644 --- a/roles/custom/matrix-sliding-sync/defaults/main.yml +++ b/roles/custom/matrix-sliding-sync/defaults/main.yml @@ -1,11 +1,11 @@ # SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2023 Kabir Kwatra # SPDX-FileCopyrightText: 2023 David Mehren +# SPDX-FileCopyrightText: 2023 Kabir Kwatra # SPDX-FileCopyrightText: 2023 Nikita Chernyi # SPDX-FileCopyrightText: 2023 Samuel Meenzen +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # SPDX-FileCopyrightText: 2024 HarHarLinks # SPDX-FileCopyrightText: 2024 MDAD project contributors -# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later From f5492e37273937dc4d765ae1302ce28fc81ca53f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 12:43:52 +0900 Subject: [PATCH 901/952] Fix license year on matrix-bot-baibot.service.j2.license Signed-off-by: Suguru Hirahara --- .../templates/systemd/matrix-bot-baibot.service.j2.license | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license index c24b3ae88..53f94a9fa 100644 --- a/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license +++ b/roles/custom/matrix-bot-baibot/templates/systemd/matrix-bot-baibot.service.j2.license @@ -1,4 +1,4 @@ -SPDX-FileCopyrightText: 2024 Slavi Pantaleev +SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev SPDX-FileCopyrightText: 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later From 416d560ffe61bb67e46ea27d9bf9ca50921d3aa3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:01:11 +0900 Subject: [PATCH 902/952] Add GitHub Action "REUSE Compliance Check" Signed-off-by: Suguru Hirahara --- .github/workflows/reuse.yml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .github/workflows/reuse.yml diff --git a/.github/workflows/reuse.yml b/.github/workflows/reuse.yml new file mode 100644 index 000000000..34b7a09bf --- /dev/null +++ b/.github/workflows/reuse.yml @@ -0,0 +1,20 @@ +# SPDX-FileCopyrightText: 2022 Free Software Foundation Europe e.V. +# +# SPDX-License-Identifier: CC0-1.0 +--- +name: REUSE Compliance Check + +on: [push, pull_request] # yamllint disable-line rule:truthy + +permissions: + contents: read + +jobs: + reuse-compliance-check: + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + + - name: REUSE Compliance Check + uses: fsfe/reuse-action@v5 From cbc192771114c6a0434b6b9b6896685bc9d66caf Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:19:25 +0900 Subject: [PATCH 903/952] Update validate_config.yml for migration: add a hint to update Ansible roles This commit adds the hint to fetch Ansible roles which have been replaced, as it is pretty easy to overlook necessity of doing so, especially if you had not enabled (and disabled thereafter) roles, whose variable names has been changed. Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index ecb36f762..5476ed382 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -84,6 +84,8 @@ Please change your configuration (vars.yml) to rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | list | items2dict" @@ -95,6 +97,8 @@ Please change your configuration (vars.yml) to rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | list | items2dict" @@ -110,6 +114,7 @@ The matrix-prometheus-node-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" @@ -125,6 +130,7 @@ The matrix-prometheus-postgres-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" @@ -140,6 +146,7 @@ The matrix-backup-borg role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_backup_borg_` -> `backup_borg_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" @@ -155,6 +162,7 @@ The matrix-grafana role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-grafana. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_grafana_` -> `grafana_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" @@ -170,6 +178,7 @@ The matrix-ntfy role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-ntfy. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_ntfy_` -> `ntfy_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" @@ -185,6 +194,7 @@ The matrix-redis role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-redis. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_redis_` -> `redis_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -199,6 +209,7 @@ msg: >- The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please change your configuration (vars.yml) to rename all variables (`redis_` -> `valkey_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -213,6 +224,7 @@ msg: >- The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please change your configuration (vars.yml) to rename all variables (`keydb_` -> `valkey_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" @@ -228,6 +240,7 @@ The matrix-etherpad role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-etherpad. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_etherpad_` -> `etherpad_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" @@ -243,6 +256,7 @@ The matrix-aux role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-aux. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_aux_` -> `aux_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" @@ -258,6 +272,7 @@ The matrix-jitsi role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-jitsi. The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_jitsi_` -> `jitsi_`). + After changing it, please do not forget to fetch the Ansible role. We found usage of the following variables: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" @@ -423,6 +438,8 @@ Please change your configuration (vars.yml) to rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | list | items2dict" @@ -434,6 +451,8 @@ Please change your configuration (vars.yml) to rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | list | items2dict" @@ -445,6 +464,8 @@ Please change your configuration (vars.yml) to rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | list | items2dict" @@ -456,6 +477,8 @@ Please change your configuration (vars.yml) to rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | list | items2dict" @@ -467,6 +490,8 @@ Please change your configuration (vars.yml) to rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`). + After changing it, please do not forget to fetch the Ansible role. + The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | list | items2dict" From 28d6862b7dfdd725424232cc46b7c6680439c672 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:21:06 +0900 Subject: [PATCH 904/952] Update validate_config.yml for migration: use a common instruction for renaming variables Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 5476ed382..58312a7e0 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -115,7 +115,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_validation_enabled | bool @@ -131,7 +131,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_backup_borg_migration_validation_enabled | bool @@ -147,7 +147,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_backup_borg_` -> `backup_borg_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_grafana_migration_validation_enabled | bool @@ -163,7 +163,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_grafana_` -> `grafana_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_ntfy_migration_validation_enabled | bool @@ -179,7 +179,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_ntfy_` -> `ntfy_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_redis_migration_validation_enabled | bool @@ -195,7 +195,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_redis_` -> `redis_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" - when: matrix_playbook_migration_redis_valkey_migration_validation_enabled | bool @@ -210,7 +210,7 @@ The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please change your configuration (vars.yml) to rename all variables (`redis_` -> `valkey_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" - when: matrix_playbook_migration_keydb_valkey_migration_validation_enabled | bool @@ -225,7 +225,7 @@ The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please change your configuration (vars.yml) to rename all variables (`keydb_` -> `valkey_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_etherpad_migration_validation_enabled | bool @@ -241,7 +241,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_etherpad_` -> `etherpad_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_aux_migration_validation_enabled | bool @@ -257,7 +257,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_aux_` -> `aux_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_jitsi_migration_validation_enabled | bool @@ -273,7 +273,7 @@ The new role is compatible with the old one, but uses different names for its variables. Please change your configuration (vars.yml) to rename all variables (`matrix_jitsi_` -> `jitsi_`). After changing it, please do not forget to fetch the Ansible role. - We found usage of the following variables: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled | bool @@ -287,7 +287,7 @@ msg: >- Your configuration contains a variable, which now has a different name. Please change your configuration (vars.yml) to rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). - We found usage of the following variables: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }} + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_postmoogle_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled | bool From 2ae6b5d82b40ada52c6a986718002186eaf63675 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:21:33 +0900 Subject: [PATCH 905/952] Update validate_config.yml for migration: replace instructions for renaming variables Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 58312a7e0..c54c09dcc 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -113,7 +113,7 @@ msg: >- The matrix-prometheus-node-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`). + Please rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" @@ -129,7 +129,7 @@ msg: >- The matrix-prometheus-postgres-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`). + Please rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" @@ -145,7 +145,7 @@ msg: >- The matrix-backup-borg role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_backup_borg_` -> `backup_borg_`). + Please rename all variables (`matrix_backup_borg_` -> `backup_borg_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" @@ -161,7 +161,7 @@ msg: >- The matrix-grafana role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-grafana. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_grafana_` -> `grafana_`). + Please rename all variables (`matrix_grafana_` -> `grafana_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" @@ -177,7 +177,7 @@ msg: >- The matrix-ntfy role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-ntfy. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_ntfy_` -> `ntfy_`). + Please rename all variables (`matrix_ntfy_` -> `ntfy_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" @@ -193,7 +193,7 @@ msg: >- The matrix-redis role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-redis. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_redis_` -> `redis_`). + Please rename all variables (`matrix_redis_` -> `redis_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -208,7 +208,7 @@ ansible.builtin.fail: msg: >- The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. - Please change your configuration (vars.yml) to rename all variables (`redis_` -> `valkey_`). + Please rename all variables (`redis_` -> `valkey_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -223,7 +223,7 @@ ansible.builtin.fail: msg: >- The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. - Please change your configuration (vars.yml) to rename all variables (`keydb_` -> `valkey_`). + Please rename all variables (`keydb_` -> `valkey_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" @@ -239,7 +239,7 @@ msg: >- The matrix-etherpad role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-etherpad. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_etherpad_` -> `etherpad_`). + Please rename all variables (`matrix_etherpad_` -> `etherpad_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" @@ -255,7 +255,7 @@ msg: >- The matrix-aux role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-aux. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_aux_` -> `aux_`). + Please rename all variables (`matrix_aux_` -> `aux_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" @@ -271,7 +271,7 @@ msg: >- The matrix-jitsi role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-jitsi. The new role is compatible with the old one, but uses different names for its variables. - Please change your configuration (vars.yml) to rename all variables (`matrix_jitsi_` -> `jitsi_`). + Please rename all variables (`matrix_jitsi_` -> `jitsi_`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" @@ -286,7 +286,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration (vars.yml) to rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). + Please rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`) on your vars.yml. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_postmoogle_migration_vars | length > 0" From e4d98811cf42b58b591b141b719b07751fd6662f Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:23:01 +0900 Subject: [PATCH 906/952] Update validate_config.yml for migration: replace instructions for renaming prefixed variables Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index c54c09dcc..5443fa8be 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -82,7 +82,7 @@ The matrix-postgres-backup role in the playbook has been replaced with the ansible-role-postgres-backup role (https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`). + Please rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -95,7 +95,7 @@ The matrix-mailer role in the playbook has been replaced with the exim-relay role (https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`). + Please rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -436,7 +436,7 @@ The postgres-backup role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`). + Please rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -449,7 +449,7 @@ The Postgres role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-postgres). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`). + Please rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -462,7 +462,7 @@ The traefik-certs-dumper role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`). + Please rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -475,7 +475,7 @@ The traefik role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-traefik). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`). + Please rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. @@ -488,7 +488,7 @@ The container-socket-proxy role in the playbook now lives under the MASH organization (https://github.com/mother-of-all-self-hosting/ansible-role-container-socket-proxy). The new role is pretty much the same, but uses differently named variables. - Please change your configuration (vars.yml) to rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`). + Please rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`) on your configuration file (vars.yml). After changing it, please do not forget to fetch the Ansible role. From 5e07de1d8560d70069565b28290b7717b790f848 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:27:13 +0900 Subject: [PATCH 907/952] Update validate_config.yml for migration: edit the instructions to update Ansible roles Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 36 +++++++++---------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 5443fa8be..5558a6117 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -84,7 +84,7 @@ Please rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | list | items2dict" @@ -97,7 +97,7 @@ Please rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | list | items2dict" @@ -114,7 +114,7 @@ The matrix-prometheus-node-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" @@ -130,7 +130,7 @@ The matrix-prometheus-postgres-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" @@ -146,7 +146,7 @@ The matrix-backup-borg role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_backup_borg_` -> `backup_borg_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" @@ -162,7 +162,7 @@ The matrix-grafana role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-grafana. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_grafana_` -> `grafana_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" @@ -178,7 +178,7 @@ The matrix-ntfy role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-ntfy. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_ntfy_` -> `ntfy_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" @@ -194,7 +194,7 @@ The matrix-redis role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-redis. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_redis_` -> `redis_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -209,7 +209,7 @@ msg: >- The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please rename all variables (`redis_` -> `valkey_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -224,7 +224,7 @@ msg: >- The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please rename all variables (`keydb_` -> `valkey_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" @@ -240,7 +240,7 @@ The matrix-etherpad role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-etherpad. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_etherpad_` -> `etherpad_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" @@ -256,7 +256,7 @@ The matrix-aux role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-aux. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_aux_` -> `aux_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" @@ -272,7 +272,7 @@ The matrix-jitsi role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-jitsi. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_jitsi_` -> `jitsi_`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" @@ -438,7 +438,7 @@ Please rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | list | items2dict" @@ -451,7 +451,7 @@ Please rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | list | items2dict" @@ -464,7 +464,7 @@ Please rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | list | items2dict" @@ -477,7 +477,7 @@ Please rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | list | items2dict" @@ -490,7 +490,7 @@ Please rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`) on your configuration file (vars.yml). - After changing it, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | list | items2dict" From 2da6e4bac2a57c2c3a3928583ee73b758bb68f06 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:27:30 +0900 Subject: [PATCH 908/952] Update validate_config.yml for migration: add instruction to check docs/maintenance-upgrading-services.md Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 36 +++++++++---------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 5558a6117..514925f93 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -84,7 +84,7 @@ Please rename all `matrix_postgres`-prefixed variables (`matrix_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_postgres_.*') | list | items2dict" @@ -97,7 +97,7 @@ Please rename all `matrix_mailer`-prefixed variables (`matrix_mailer_*` -> `exim_relay_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'matrix_mailer_.*') | list | items2dict" @@ -114,7 +114,7 @@ The matrix-prometheus-node-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" @@ -130,7 +130,7 @@ The matrix-prometheus-postgres-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" @@ -146,7 +146,7 @@ The matrix-backup-borg role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_backup_borg_` -> `backup_borg_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" @@ -162,7 +162,7 @@ The matrix-grafana role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-grafana. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_grafana_` -> `grafana_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" @@ -178,7 +178,7 @@ The matrix-ntfy role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-ntfy. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_ntfy_` -> `ntfy_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" @@ -194,7 +194,7 @@ The matrix-redis role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-redis. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_redis_` -> `redis_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -209,7 +209,7 @@ msg: >- The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please rename all variables (`redis_` -> `valkey_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -224,7 +224,7 @@ msg: >- The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. Please rename all variables (`keydb_` -> `valkey_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" @@ -240,7 +240,7 @@ The matrix-etherpad role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-etherpad. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_etherpad_` -> `etherpad_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" @@ -256,7 +256,7 @@ The matrix-aux role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-aux. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_aux_` -> `aux_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" @@ -272,7 +272,7 @@ The matrix-jitsi role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-jitsi. The new role is compatible with the old one, but uses different names for its variables. Please rename all variables (`matrix_jitsi_` -> `jitsi_`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" @@ -438,7 +438,7 @@ Please rename all `devture_postgres_backup_`-prefixed variables (`devture_postgres_backup_*` -> `postgres_backup_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_backup_.*') | list | items2dict" @@ -451,7 +451,7 @@ Please rename all `devture_postgres_`-prefixed variables (`devture_postgres_*` -> `postgres_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_postgres_.*') | list | items2dict" @@ -464,7 +464,7 @@ Please rename all `devture_traefik_certs_dumper_`-prefixed variables (`devture_traefik_certs_dumper_*` -> `traefik_certs_dumper_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_certs_dumper_.*') | list | items2dict" @@ -477,7 +477,7 @@ Please rename all `devture_traefik_`-prefixed variables (`devture_traefik_*` -> `traefik_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_traefik_.*') | list | items2dict" @@ -490,7 +490,7 @@ Please rename all `devture_container_socket_proxy_`-prefixed variables (`devture_container_socket_proxy_*` -> `container_socket_proxy_*`) on your configuration file (vars.yml). - After renaming them, please do not forget to fetch the Ansible role. + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. The following variables in your configuration need to be renamed: {{ vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | map(attribute='key') | join(', ') }} when: "vars | dict2items | selectattr('key', 'match', 'devture_container_socket_proxy_.*') | list | items2dict" From d2fe3bc5b6cc2caaf0febfdf54da404d36ad8aef Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:27:45 +0900 Subject: [PATCH 909/952] Update validate_config.yml for migration: add blank lines between messages where expected Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 514925f93..4b051082b 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -113,8 +113,11 @@ msg: >- The matrix-prometheus-node-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_node_exporter_migration_vars | length > 0" @@ -129,8 +132,11 @@ msg: >- The matrix-prometheus-postgres-exporter role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_matrix_prometheus_postgres_exporter_migration_vars | length > 0" @@ -145,8 +151,11 @@ msg: >- The matrix-backup-borg role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_backup_borg_` -> `backup_borg_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_backup_borg_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_backup_borg_migration_vars | length > 0" @@ -161,8 +170,11 @@ msg: >- The matrix-grafana role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-grafana. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_grafana_` -> `grafana_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_grafana_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_grafana_migration_vars | length > 0" @@ -177,8 +189,11 @@ msg: >- The matrix-ntfy role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-ntfy. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_ntfy_` -> `ntfy_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_ntfy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ntfy_migration_vars | length > 0" @@ -193,8 +208,11 @@ msg: >- The matrix-redis role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-redis. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_redis_` -> `redis_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -208,8 +226,11 @@ ansible.builtin.fail: msg: >- The Redis role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. + Please rename all variables (`redis_` -> `valkey_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_redis_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_redis_migration_vars | length > 0" @@ -223,8 +244,11 @@ ansible.builtin.fail: msg: >- The KeyDB role that used to be part of this playbook has been superseded by https://github.com/mother-of-all-self-hosting/ansible-role-valkey. + Please rename all variables (`keydb_` -> `valkey_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_keydb_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_keydb_migration_vars | length > 0" @@ -239,8 +263,11 @@ msg: >- The matrix-etherpad role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-etherpad. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_etherpad_` -> `etherpad_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_etherpad_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_etherpad_migration_vars | length > 0" @@ -255,8 +282,11 @@ msg: >- The matrix-aux role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-aux. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_aux_` -> `aux_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_aux_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_aux_migration_vars | length > 0" @@ -271,8 +301,11 @@ msg: >- The matrix-jitsi role that used to be part of this playbook has been replaced by https://github.com/mother-of-all-self-hosting/ansible-role-jitsi. The new role is compatible with the old one, but uses different names for its variables. + Please rename all variables (`matrix_jitsi_` -> `jitsi_`) on your configuration file (vars.yml). + After renaming them, please do not forget to fetch the Ansible role. See docs/maintenance-upgrading-services.md for details about how to do so. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_jitsi_migration_vars | length > 0" @@ -286,7 +319,9 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. + Please rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`) on your vars.yml. + The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_postmoogle_migration_vars | length > 0" From 06ffbb3681213ce5b39a5e7883c7d777ef56f1b3 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:28:12 +0900 Subject: [PATCH 910/952] Update validate_config.yml for migration: adopt a simpler description Signed-off-by: Suguru Hirahara --- .../matrix_playbook_migration/tasks/validate_config.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 4b051082b..0333a6642 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -10,7 +10,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_vars_yml_snapshotting_enabled', 'new': 'devture_playbook_state_preserver_vars_preservation_enabled'} @@ -331,7 +331,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_nginx_proxy_proxy_matrix_metrics_enabled', 'new': 'matrix_metrics_exposure_enabled'} @@ -536,7 +536,7 @@ The Google Hangouts service was discontinued on 1st of November 2022. The mautrix-hangouts bridge has been deprecated in the playbook since December 2024 and was completely removed from the playbook in February 2025. - Please change your configuration (`vars.yml`) to remove all `matrix_mautrix_hangouts_*` variables. + Please remove all `matrix_mautrix_hangouts_*` variables from your configuration file (vars.yml). You may also wish to uninstall the bridge manually. See `docs/configuring-playbook-bridge-mautrix-hangouts.md` for more information. @@ -548,7 +548,7 @@ msg: |- The Email2Matrix service has been superseded by the Postmoogle bridge for a long time now and was completely removed from the playbook in February 2025. - Please change your configuration (`vars.yml`) to remove all `matrix_email2matrix_*` variables. + Please remove all `matrix_email2matrix_*` variables from your configuration file (vars.yml). You may also wish to uninstall the bridge manually. See `docs/configuring-playbook-email2matrix.md` for more information. From 219cd7702d3db40de048479d2469d1b9c4dbb78d Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:28:24 +0900 Subject: [PATCH 911/952] Update validate_config.yml for migration: adopt a common instruction Signed-off-by: Suguru Hirahara --- .../custom/matrix_playbook_migration/tasks/validate_config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index 0333a6642..a72e88578 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -320,7 +320,7 @@ msg: >- Your configuration contains a variable, which now has a different name. - Please rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`) on your vars.yml. + Please rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`) on your configuration file (vars.yml). The following variables in your configuration need to be renamed: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_postmoogle_migration_vars | length > 0" From cdc12e0ecb870ff5b755477186405d17ab2ebaaa Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:29:36 +0900 Subject: [PATCH 912/952] Update validate_config.yml for migration: adopt a common instruction to variables which should be removed Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml index a72e88578..437d1fc69 100644 --- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml +++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml @@ -425,8 +425,10 @@ ansible.builtin.fail: msg: >- The matrix-nginx-proxy role that used to be part of this playbook has been removed. - You should remove all its variables (`matrix_nginx_proxy_*`) from your vars.yml file. - We found usage of the following variables: {{ matrix_playbook_migration_nginx_proxy_migration_vars.keys() | join(', ') }} + + You should remove all its variables (`matrix_nginx_proxy_*`) from your configuration file (vars.yml). + + The following variables in your configuration should be renamed: {{ matrix_playbook_migration_nginx_proxy_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_nginx_proxy_migration_vars | length > 0" - when: matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled | bool @@ -439,8 +441,10 @@ ansible.builtin.fail: msg: >- The matrix-nginx-proxy role that used to be part of this playbook has been removed. - You should remove all its variables (`matrix_ssl_*`) from your vars.yml file. - We found usage of the following variables: {{ matrix_playbook_migration_ssl_migration_vars.keys() | join(', ') }} + + You should remove all its variables (`matrix_ssl_*`) from your configuration file (vars.yml). + + The following variables in your configuration should be renamed: {{ matrix_playbook_migration_ssl_migration_vars.keys() | join(', ') }} when: "matrix_playbook_migration_ssl_migration_vars | length > 0" - block: From c18fc93a225a3321959ab5eb3d8131763eda9ca8 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:30:50 +0900 Subject: [PATCH 913/952] Update validate_config.yml files: edit the banner message for variables name Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 3 ++- .../matrix-authentication-service/tasks/validate_config.yml | 3 ++- roles/custom/matrix-base/tasks/validate_config.yml | 2 +- roles/custom/matrix-bot-baibot/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bot-buscarron/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bot-draupnir/tasks/validate_config.yml | 2 +- roles/custom/matrix-bot-honoroit/tasks/validate_config.yml | 4 ++-- .../tasks/validate_config.yml | 3 ++- .../matrix-bot-matrix-reminder-bot/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bot-maubot/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-appservice-irc/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-appservice-slack/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-beeper-linkedin/tasks/validate_config.yml | 3 ++- .../matrix-bridge-go-skype-bridge/tasks/validate_config.yml | 3 ++- roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml | 4 ++-- .../matrix-bridge-mautrix-bluesky/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-discord/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-facebook/tasks/validate_config.yml | 4 ++-- .../matrix-bridge-mautrix-gmessages/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-instagram/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-signal/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-slack/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-telegram/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-twitter/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mx-puppet-slack/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml | 3 ++- roles/custom/matrix-cactus-comments/tasks/validate_config.yml | 3 ++- roles/custom/matrix-client-element/tasks/validate_config.yml | 2 +- .../matrix-client-schildichat/tasks/validate_config.yml | 4 ++-- roles/custom/matrix-corporal/tasks/validate_config.yml | 3 ++- roles/custom/matrix-coturn/tasks/validate_config.yml | 4 ++-- roles/custom/matrix-dendrite/tasks/validate_config.yml | 3 ++- roles/custom/matrix-dimension/tasks/validate_config.yml | 3 ++- .../matrix-ldap-registration-proxy/tasks/validate_config.yml | 3 ++- roles/custom/matrix-ma1sd/tasks/validate_config.yml | 3 ++- roles/custom/matrix-media-repo/tasks/validate_config.yml | 3 ++- .../tasks/validate_config.yml | 3 ++- roles/custom/matrix-registration/tasks/validate_config.yml | 3 ++- roles/custom/matrix-synapse-admin/tasks/validate_config.yml | 3 ++- .../matrix-synapse-auto-compressor/tasks/validate_config.yml | 4 ++-- .../matrix-synapse-usage-exporter/tasks/validate_config.yml | 3 ++- roles/custom/matrix-synapse/tasks/validate_config.yml | 4 ++-- .../tasks/validate_config.yml | 2 +- 52 files changed, 100 insertions(+), 59 deletions(-) diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml index a25fb991d..8d8d1168c 100644 --- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml +++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2024 MDAD project contributors # SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -17,7 +18,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_draupnir_for_all_docker_image_name_prefix', 'new': 'matrix_appservice_draupnir_for_all_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-authentication-service/tasks/validate_config.yml b/roles/custom/matrix-authentication-service/tasks/validate_config.yml index 59b59957b..d2adbe56c 100644 --- a/roles/custom/matrix-authentication-service/tasks/validate_config.yml +++ b/roles/custom/matrix-authentication-service/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -38,7 +39,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_authentication_service_container_image_name_prefix', 'new': 'matrix_authentication_service_container_image_registry_prefix'} diff --git a/roles/custom/matrix-base/tasks/validate_config.yml b/roles/custom/matrix-base/tasks/validate_config.yml index f1a78f614..730b0d1d8 100644 --- a/roles/custom/matrix-base/tasks/validate_config.yml +++ b/roles/custom/matrix-base/tasks/validate_config.yml @@ -19,7 +19,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'host_specific_hostname_identity', 'new': 'matrix_domain'} diff --git a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml index 6129e3806..ee4eae03c 100644 --- a/roles/custom/matrix-bot-baibot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-baibot/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -35,7 +36,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_baibot_container_image_name_prefix', 'new': 'matrix_bot_baibot_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml index e07cbffef..58bdc3371 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2022 Nikita Chernyi # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -8,7 +9,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_buscarron_noencryption', 'new': ''} diff --git a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml index 3d1fff512..d9c266dad 100644 --- a/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-chatgpt/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2023 MDAD project contributors # SPDX-FileCopyrightText: 2023 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -31,7 +32,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_chatgpt_docker_image', 'new': 'matrix_bot_chatgpt_container_image'} diff --git a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml index b369a5c00..476c4482d 100644 --- a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml @@ -40,7 +40,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_draupnir_container_image_name_prefix', 'new': 'matrix_bot_draupnir_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml index a8e2e87af..fcaa04b68 100644 --- a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -21,7 +21,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_honoroit_container_image_name_prefix', 'new': 'matrix_bot_honoroit_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml index dfa5c7115..8fc291061 100644 --- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2022 - 2023 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -18,7 +19,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_matrix_registration_bot_bot_access_token', 'new': ''} diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml index 68925dc4f..06781bd19 100644 --- a/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-matrix-reminder-bot/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -21,7 +22,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_matrix_reminder_bot_container_self_build', 'new': 'matrix_bot_matrix_reminder_bot_container_image_self_build'} diff --git a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml index 6b8be3cce..11c53f8ca 100644 --- a/roles/custom/matrix-bot-maubot/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-maubot/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -10,7 +11,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_maubot_management_interface_port', 'new': 'matrix_bot_maubot_server_port'} diff --git a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml index a5de35ead..6b9ae0030 100644 --- a/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-mjolnir/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2021 Aaron Raimist # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2024 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -30,7 +31,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_mjolnir_container_image_name_prefix', 'new': 'matrix_bot_mjolnir_container_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml index 3d5fec6fe..e2be8da0a 100644 --- a/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-discord/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -22,7 +23,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_discord_container_expose_client_server_api_port', 'new': ''} diff --git a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml index e923180ed..fb7d77281 100644 --- a/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-irc/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -37,7 +38,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_irc_container_expose_client_server_api_port', 'new': ''} diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml index 8ba158fe8..ebabe36aa 100644 --- a/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-kakaotalk/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -20,7 +21,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_kakaotalk_node_docker_image_name_prefix', 'new': 'matrix_appservice_kakaotalk_node_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml index 66eddaf11..b35e2cdb6 100644 --- a/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-slack/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -26,7 +27,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_slack_container_self_build', 'new': 'matrix_appservice_slack_container_image_self_build'} diff --git a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml index a5f930a36..7f0d8bfec 100644 --- a/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-appservice-webhooks/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2020 Björn Marten # SPDX-FileCopyrightText: 2021 boris runakov # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -25,7 +26,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_appservice_webhooks_docker_image_name_prefix', 'new': 'matrix_appservice_webhooks_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml index 059eeebc8..1bc9de53a 100644 --- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2021 Alexandar Mechev # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -22,7 +23,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_beeper_linkedin_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml index 12f4172af..6f82a28b4 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2022 Vladimir Panteleev # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -21,7 +22,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_go_skype_bridge_docker_image_name_prefix', 'new': 'matrix_go_skype_bridge_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml index a0848da91..1c35abe88 100644 --- a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -10,7 +10,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_hookshot_feeds_interval', 'new': 'matrix_hookshot_feeds_pollIntervalSeconds'} diff --git a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml index 5e7b03753..e14168283 100644 --- a/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-bluesky/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2025 MDAD project contributors # SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_bluesky_docker_image_name_prefix', 'new': 'matrix_mautrix_bluesky_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml index 63552ebb7..a354dbcd6 100644 --- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -24,7 +25,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_discord_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml index 45c751627..aaab4839f 100644 --- a/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-facebook/tasks/validate_config.yml @@ -1,7 +1,7 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 Jason Locklin # SPDX-FileCopyrightText: 2022 László Várady -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -11,7 +11,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_facebook_public_endpoint', 'new': 'matrix_mautrix_facebook_appservice_public_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml index ccf220349..6b1b76e1d 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-gmessages/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2023 Shreyas Ajjarapu # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_gmessages_log_level', 'new': 'matrix_mautrix_gmessages_logging_level'} diff --git a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml index 19c89c46c..9e2b20132 100644 --- a/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-googlechat/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2021 MDAD project contributors # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -27,7 +28,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_googlechat_docker_image_name_prefix', 'new': 'matrix_mautrix_googlechat_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml index ef430fcbd..b793c80b2 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2021 Marcus Proest # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -22,7 +23,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_instagram_docker_image_name_prefix', 'new': 'matrix_mautrix_instagram_docker_image_registry_prefix'} diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml index 833106582..4abd0f5ba 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_meta_instagram_bridge_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml index 3300a54a0..db8bb4fb1 100644 --- a/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_meta_messenger_bridge_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml index eeb6d5ea2..1f08f1feb 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-signal/tasks/validate_config.yml @@ -2,6 +2,7 @@ # SPDX-FileCopyrightText: 2020 - 2022 MDAD project contributors # SPDX-FileCopyrightText: 2021 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -25,7 +26,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_signal_log_level', 'new': 'matrix_mautrix_signal_logging_level'} diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml index 0f085735f..8265ee865 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2023 Cody Wyatt Neiman # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -30,7 +31,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_slack_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml index 08ce0d3dc..20bad5816 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-telegram/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -28,7 +29,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_telegram_container_exposed_port_number', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml index e97779600..0a30cd1d7 100644 --- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2021 Matthew Cengia # SPDX-FileCopyrightText: 2021 Shreyas Ajjarapu # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -24,7 +25,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_twitter_login_shared_secret', 'new': ''} diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml index e321aa414..a1f7605f3 100644 --- a/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/validate_config.yml @@ -2,6 +2,7 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -22,7 +23,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mautrix_whatsapp_log_level', 'new': 'matrix_mautrix_whatsapp_logging_level'} diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml index fd67a1c80..8ede9eed3 100644 --- a/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-slack/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2020 Rodrigo Belem # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mx_puppet_slack_redirect_path', 'new': 'matrix_mx_puppet_slack_oauth_redirect_path, but setting matrix_mx_puppet_slack_path_prefix is better'} diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml index 132984974..84e2c1c76 100644 --- a/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mx-puppet-twitter/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2020 Tulir Asokan # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_mx_puppet_twitter_webhook_path', 'new': '- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_bot_cactus_comments_systemd_required_services_list', 'new': 'matrix_cactus_comments_systemd_required_services_list'} diff --git a/roles/custom/matrix-client-element/tasks/validate_config.yml b/roles/custom/matrix-client-element/tasks/validate_config.yml index 7e3623aeb..136c26e5f 100644 --- a/roles/custom/matrix-client-element/tasks/validate_config.yml +++ b/roles/custom/matrix-client-element/tasks/validate_config.yml @@ -39,7 +39,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_client_element_showLabsSettings', 'new': 'matrix_client_element_show_lab_settings'} diff --git a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml index 97f556092..09ef97434 100644 --- a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml +++ b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml @@ -1,6 +1,6 @@ # SPDX-FileCopyrightText: 2023 Nikita Chernyi # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -10,7 +10,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_client_schildichat_welcome_user_id', 'new': ''} diff --git a/roles/custom/matrix-corporal/tasks/validate_config.yml b/roles/custom/matrix-corporal/tasks/validate_config.yml index 57938ac91..366527fcb 100644 --- a/roles/custom/matrix-corporal/tasks/validate_config.yml +++ b/roles/custom/matrix-corporal/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2019 Dan Arnfield +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -26,7 +27,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_corporal_container_expose_ports', 'new': ''} diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml index ff0ac914b..4d7568cee 100644 --- a/roles/custom/matrix-coturn/tasks/validate_config.yml +++ b/roles/custom/matrix-coturn/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2019 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -9,7 +9,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_coturn_docker_network', 'new': 'matrix_coturn_container_network'} diff --git a/roles/custom/matrix-dendrite/tasks/validate_config.yml b/roles/custom/matrix-dendrite/tasks/validate_config.yml index 243015588..2f91bfa74 100644 --- a/roles/custom/matrix-dendrite/tasks/validate_config.yml +++ b/roles/custom/matrix-dendrite/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Jip J. Dekker # SPDX-FileCopyrightText: 2023 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -10,7 +11,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_dendrite_enable_registration_captcha', 'new': 'matrix_dendrite_client_api_enable_registration_captcha'} diff --git a/roles/custom/matrix-dimension/tasks/validate_config.yml b/roles/custom/matrix-dimension/tasks/validate_config.yml index f7b32e389..8b8e69b8d 100644 --- a/roles/custom/matrix-dimension/tasks/validate_config.yml +++ b/roles/custom/matrix-dimension/tasks/validate_config.yml @@ -3,6 +3,7 @@ # SPDX-FileCopyrightText: 2019 - 2023 Slavi Pantaleev # SPDX-FileCopyrightText: 2020 Chris van Dijk # SPDX-FileCopyrightText: 2022 Marko Weltzer +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -26,7 +27,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_dimension_container_expose_port', 'new': ''} diff --git a/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml b/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml index 97d94fe7f..fc2d870b5 100644 --- a/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml +++ b/roles/custom/matrix-ldap-registration-proxy/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2022 - 2024 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -23,7 +24,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_ldap_registration_proxy_registration_addr_with_container', 'new': ''} diff --git a/roles/custom/matrix-ma1sd/tasks/validate_config.yml b/roles/custom/matrix-ma1sd/tasks/validate_config.yml index ca7009df4..d6d308d32 100644 --- a/roles/custom/matrix-ma1sd/tasks/validate_config.yml +++ b/roles/custom/matrix-ma1sd/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2020 Marcel Partap # SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2021 boris runakov +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -66,7 +67,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_ma1sd_container_expose_port', 'new': ''} diff --git a/roles/custom/matrix-media-repo/tasks/validate_config.yml b/roles/custom/matrix-media-repo/tasks/validate_config.yml index e9b4d64f9..4d10a44ed 100644 --- a/roles/custom/matrix-media-repo/tasks/validate_config.yml +++ b/roles/custom/matrix-media-repo/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2023 Michael Hollister # SPDX-FileCopyrightText: 2024 - 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -19,7 +20,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_media_repo_access_tokens', 'new': ''} diff --git a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml index 9e20017f9..67668dc7e 100644 --- a/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml +++ b/roles/custom/matrix-prometheus-nginxlog-exporter/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2022 MDAD project contributors # SPDX-FileCopyrightText: 2023 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -9,7 +10,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_prometheus_nginxlog_exporter_container_hostname', 'new': 'matrix_prometheus_nginxlog_exporter_identifier'} diff --git a/roles/custom/matrix-registration/tasks/validate_config.yml b/roles/custom/matrix-registration/tasks/validate_config.yml index 9e76a19c7..dba8f7497 100644 --- a/roles/custom/matrix-registration/tasks/validate_config.yml +++ b/roles/custom/matrix-registration/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -22,7 +23,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_registration_docker_repo', 'new': 'matrix_registration_container_image_self_build_repo'} diff --git a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml index ceb7ddec2..d0e953d24 100644 --- a/roles/custom/matrix-synapse-admin/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-admin/tasks/validate_config.yml @@ -1,5 +1,6 @@ # SPDX-FileCopyrightText: 2020 - 2025 Slavi Pantaleev # SPDX-FileCopyrightText: 2022 MDAD project contributors +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -9,7 +10,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_synapse_admin_docker_repo', 'new': 'matrix_synapse_admin_container_self_build_repo'} diff --git a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml index 411508c80..ccaf4b42a 100644 --- a/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-auto-compressor/tasks/validate_config.yml @@ -1,5 +1,5 @@ # SPDX-FileCopyrightText: 2023 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2024 Suguru Hirahara +# SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -8,7 +8,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - "old": "matrix_synapse_auto_compressor_calendar" diff --git a/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml index 3274e595a..c6fa07e23 100644 --- a/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse-usage-exporter/tasks/validate_config.yml @@ -1,4 +1,5 @@ # SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara # # SPDX-License-Identifier: AGPL-3.0-or-later @@ -8,7 +9,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_synapse_usage_exporter_docker_image_name_prefix', 'new': 'matrix_synapse_usage_exporter_container_image_registry_prefix'} diff --git a/roles/custom/matrix-synapse/tasks/validate_config.yml b/roles/custom/matrix-synapse/tasks/validate_config.yml index a0df4c057..40c843794 100644 --- a/roles/custom/matrix-synapse/tasks/validate_config.yml +++ b/roles/custom/matrix-synapse/tasks/validate_config.yml @@ -72,7 +72,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_synapse_email_riot_base_url', 'new': ''} @@ -115,7 +115,7 @@ ansible.builtin.fail: msg: >- Your matrix_synapse_configuration_extension_yaml configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in matrix_synapse_configuration_extension" with_items: - {'old': 'federation_ip_range_blacklist', 'new': 'ip_range_blacklist'} diff --git a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml index 871a8f0e2..449cad532 100644 --- a/roles/custom/matrix-user-verification-service/tasks/validate_config.yml +++ b/roles/custom/matrix-user-verification-service/tasks/validate_config.yml @@ -42,7 +42,7 @@ ansible.builtin.fail: msg: >- Your configuration contains a variable, which now has a different name. - Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "item.old in vars" with_items: - {'old': 'matrix_user_verification_service_docker_image_name_prefix', 'new': 'matrix_user_verification_service_docker_image_registry_prefix'} From b4ce0274c9dfd294a3219e0667d1801eefb8328a Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 13:36:57 +0900 Subject: [PATCH 914/952] Update validate_configs.yml for riot-web and ma1sd: adopt the common instruction Signed-off-by: Suguru Hirahara --- roles/custom/matrix-client-element/tasks/validate_config.yml | 2 +- roles/custom/matrix-ma1sd/tasks/validate_config.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-client-element/tasks/validate_config.yml b/roles/custom/matrix-client-element/tasks/validate_config.yml index 136c26e5f..7ff71cc2f 100644 --- a/roles/custom/matrix-client-element/tasks/validate_config.yml +++ b/roles/custom/matrix-client-element/tasks/validate_config.yml @@ -29,7 +29,7 @@ msg: >- Riot has been renamed to Element (https://element.io/blog/welcome-to-element/). The playbook will migrate your existing configuration and data automatically, but you need to adjust variable names. - Please change your configuration (vars.yml) to rename all riot-web variables (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). Also note that DNS configuration changes may be necessary. when: "vars | dict2items | selectattr('key', 'match', item.old) | list | items2dict" with_items: diff --git a/roles/custom/matrix-ma1sd/tasks/validate_config.yml b/roles/custom/matrix-ma1sd/tasks/validate_config.yml index d6d308d32..451205e92 100644 --- a/roles/custom/matrix-ma1sd/tasks/validate_config.yml +++ b/roles/custom/matrix-ma1sd/tasks/validate_config.yml @@ -82,7 +82,7 @@ msg: >- mxisd is deprecated and has been replaced with ma1sd (https://github.com/ma1uta/ma1sd), a compatible fork. The playbook will migrate your existing mxisd configuration and data automatically, but you need to adjust variable names. - Please change your configuration (vars.yml) to rename all mxisd variables (`{{ item.old }}` -> `{{ item.new }}`). + Please rename the variable (`{{ item.old }}` -> `{{ item.new }}`) on your configuration file (vars.yml). when: "vars | dict2items | selectattr('key', 'match', item.old) | list | items2dict" with_items: - {'old': 'matrix_mxisd_.*', 'new': 'matrix_ma1sd_.*'} From 91130c8a1c4b6c4fb80a734a90f078e8bf49ec70 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 5 Mar 2025 06:27:58 +0000 Subject: [PATCH 915/952] Update ajbura/cinny Docker tag to v4.5.1 --- roles/custom/matrix-client-cinny/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml index fa0597af6..56ead3e5d 100644 --- a/roles/custom/matrix-client-cinny/defaults/main.yml +++ b/roles/custom/matrix-client-cinny/defaults/main.yml @@ -17,7 +17,7 @@ matrix_client_cinny_container_image_self_build: false matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git" # renovate: datasource=docker depName=ajbura/cinny -matrix_client_cinny_version: v4.5.0 +matrix_client_cinny_version: v4.5.1 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_registry_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}" matrix_client_cinny_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_client_cinny_docker_image_registry_prefix_upstream }}" matrix_client_cinny_docker_image_registry_prefix_upstream: "{{ matrix_client_cinny_docker_image_registry_prefix_upstream_default }}" From ae661b991e02384812e563671f4bbf8e5454e1d1 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 5 Mar 2025 06:28:02 +0000 Subject: [PATCH 916/952] Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2025.3.5 --- roles/custom/matrix-alertmanager-receiver/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml index 1b7763a37..3bd6107f4 100644 --- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml +++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml @@ -11,7 +11,7 @@ matrix_alertmanager_receiver_enabled: true # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver -matrix_alertmanager_receiver_version: 2025.2.26 +matrix_alertmanager_receiver_version: 2025.3.5 matrix_alertmanager_receiver_scheme: https From d4c007dffdfb5dabd2713e88ae1e8b481e5a0460 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 16:03:16 +0900 Subject: [PATCH 917/952] Re-run reuse annotate for roles/ Signed-off-by: Suguru Hirahara --- roles/custom/matrix-bot-buscarron/tasks/validate_config.yml | 3 ++- .../matrix-bridge-go-skype-bridge/tasks/validate_config.yml | 3 ++- .../matrix-bridge-mautrix-instagram/tasks/validate_config.yml | 3 ++- roles/custom/matrix-cactus-comments/tasks/validate_config.yml | 3 ++- 4 files changed, 8 insertions(+), 4 deletions(-) diff --git a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml index 9dc56f60d..45e6690e2 100644 --- a/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml +++ b/roles/custom/matrix-bot-buscarron/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2025 Suguru Hirahara # SPDX-FileCopyrightText: 2022 Nikita Chernyi +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# # SPDX-License-Identifier: AGPL-3.0-or-later --- diff --git a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml index 62cb9676d..d7d20b94d 100644 --- a/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-go-skype-bridge/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2022 - 2025 Slavi Pantaleev -# SPDX-FileCopyrightText: 2025 Suguru Hirahara # SPDX-FileCopyrightText: 2022 Vladimir Panteleev +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# # SPDX-License-Identifier: AGPL-3.0-or-later --- diff --git a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml index 3e6e4ab27..f86e3e243 100644 --- a/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-instagram/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2025 Suguru Hirahara # SPDX-FileCopyrightText: 2021 Marcus Proest +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# # SPDX-License-Identifier: AGPL-3.0-or-later --- diff --git a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml index 9c1be1d6f..125b4b858 100644 --- a/roles/custom/matrix-cactus-comments/tasks/validate_config.yml +++ b/roles/custom/matrix-cactus-comments/tasks/validate_config.yml @@ -1,6 +1,7 @@ # SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev -# SPDX-FileCopyrightText: 2025 Suguru Hirahara # SPDX-FileCopyrightText: 2022 Julian-Samuel Gebühr +# SPDX-FileCopyrightText: 2025 Suguru Hirahara +# # SPDX-License-Identifier: AGPL-3.0-or-later --- From 0bad96ac909911d678c70a522a15bc5bacce0cb9 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 5 Mar 2025 16:03:27 +0900 Subject: [PATCH 918/952] Add REUSE compliant badge on README.md Signed-off-by: Suguru Hirahara --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ca51c76ac..72ca57855 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) +[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) [![REUSE status](https://api.reuse.software/badge/github.com/spantaleev/matrix-docker-ansible-deploy)](https://api.reuse.software/info/github.com/spantaleev/matrix-docker-ansible-deploy) # Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker From 60bc545d0e737e1ce01b199647b09ae32697f009 Mon Sep 17 00:00:00 2001 From: Aine Date: Wed, 5 Mar 2025 15:24:00 +0200 Subject: [PATCH 919/952] Synapse Admin v0.10.3-etke38 --- roles/custom/matrix-synapse-admin/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml index 4a3028839..350b3b5cd 100644 --- a/roles/custom/matrix-synapse-admin/defaults/main.yml +++ b/roles/custom/matrix-synapse-admin/defaults/main.yml @@ -25,7 +25,7 @@ matrix_synapse_admin_container_image_self_build: false matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git" # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin -matrix_synapse_admin_version: v0.10.3-etke37 +matrix_synapse_admin_version: v0.10.3-etke38 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_registry_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}" matrix_synapse_admin_docker_image_registry_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else matrix_synapse_admin_docker_image_registry_prefix_upstream }}" matrix_synapse_admin_docker_image_registry_prefix_upstream: "{{ matrix_synapse_admin_docker_image_registry_prefix_upstream_default }}" From 36f00c82e7d1b1a9526c25974f8e10895bc89702 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 6 Mar 2025 00:50:26 +0900 Subject: [PATCH 920/952] Update docs/configuring-playbook-s3.md: add links to Storj and edit the section for other S3-compatible storage providers Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-s3.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md index 1aa190df5..bb7a51e7f 100644 --- a/docs/configuring-playbook-s3.md +++ b/docs/configuring-playbook-s3.md @@ -26,7 +26,7 @@ You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data. -All these providers have different prices, with 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. +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; check actual pricing [here](https://storj.dev/dcs/pricing)). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress. Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10). @@ -97,9 +97,9 @@ For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-stora ## Other providers -For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2)). +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. -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. +For details about setting up a bucket at Storj, please see the instruction [here](https://storj.dev/dcs/getting-started) to get started. ## Setting up From 1c68fd0d9b44aae71abd47a75f89deaaaea84778 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 5 Mar 2025 21:24:43 +0200 Subject: [PATCH 921/952] Make matrix-synapse-reverse-proxy-companion not report "502 Bad Gateway" when Synapse workers restart Since nginx 1.27.3, we can make use of the `resolve` parameter for an `upstream`'s `server`, to allow DNS resolution to happen continuously at runtime, not just once during startup. Previously, this was not possible to do in an `upstream` block without an nginx-plus subscription. Outside of an `upstream` block, we've used and still use `set $backend ..` workarounds to get DNS resolution at runtime, but now we can do it in `upstream` as well. --- .../matrix-synapse-reverse-proxy-companion.conf.j2 | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 index 57dee1d9b..46dbb010e 100644 --- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 +++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 @@ -16,10 +16,18 @@ {% macro render_worker_upstream(name, workers, load_balance) %} {% if workers | length > 0 %} upstream {{ name }} { + {# + We need to use a zone so that the upstream is stored in shared memory, + otherwise we can't use `resolve` below, as reported by nginx: + > resolving names at run time requires upstream ".." in ... to be in shared memory + #} + zone {{ name }} 64k; + {{ load_balance }} keepalive {{ ((workers | length) * 2) | string }}; + resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s; {% for worker in workers %} - server "{{ worker.name }}:{{ worker.port }}"; + server "{{ worker.name }}:{{ worker.port }}" resolve; {% endfor %} } {% endif %} From a72d017e47c15b4cf91f40189e75ce1896a52055 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 5 Mar 2025 22:34:23 +0000 Subject: [PATCH 922/952] Update dependency Jinja2 to v3.1.6 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 894bbe199..c82e718f9 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -6,7 +6,7 @@ click==8.1.8 docutils==0.21.2 idna==3.10 imagesize==1.4.1 -Jinja2==3.1.5 +Jinja2==3.1.6 linkify-it-py==2.0.3 markdown-it-py==3.0.0 MarkupSafe==3.0.2 From 820acce224a413911e13d256826b4a7f173a0199 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Thu, 6 Mar 2025 04:46:44 +0000 Subject: [PATCH 923/952] Bump jinja2 from 3.1.5 to 3.1.6 in /i18n Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.5 to 3.1.6. - [Release notes](https://github.com/pallets/jinja/releases) - [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst) - [Commits](https://github.com/pallets/jinja/compare/3.1.5...3.1.6) --- updated-dependencies: - dependency-name: jinja2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 894bbe199..c82e718f9 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -6,7 +6,7 @@ click==8.1.8 docutils==0.21.2 idna==3.10 imagesize==1.4.1 -Jinja2==3.1.5 +Jinja2==3.1.6 linkify-it-py==2.0.3 markdown-it-py==3.0.0 MarkupSafe==3.0.2 From 55e47d69dbe6a206573eadc25469cd38df9901ac Mon Sep 17 00:00:00 2001 From: Iruwen <11341130+Iruwen@users.noreply.github.com> Date: Thu, 6 Mar 2025 14:48:23 +0100 Subject: [PATCH 924/952] Enable room summary API (MSC3266) support for Synapse to support Element X clients --- roles/custom/matrix-synapse/defaults/main.yml | 9 +++++++++ .../matrix-synapse/templates/synapse/homeserver.yaml.j2 | 3 +++ 2 files changed, 12 insertions(+) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index cd9cfa7ea..7742f4764 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -1252,6 +1252,15 @@ matrix_synapse_experimental_features_msc4108_enabled: false ################################################################################ +# Controls whether to enable the "room summary API" experimental feature. +# See https://github.com/matrix-org/matrix-spec-proposals/pull/3266 +# Despite being experimental, this feature is mandatory for the next-generation Element X clients, which is why it is enabled by default: +# https://github.com/element-hq/element-x-ios/issues/3713#issuecomment-2620958291 +# If you're worried about the privacy implications of this unauthenticated API, see: +# https://github.com/deepbluev7/matrix-doc/blob/room-summaries/proposals/3266-room-summary.md#client-server-api +# Set this to false if you still want to disable to API for some reason. Note that doing so breaks Element X compatibility though. +matrix_synapse_experimental_features_msc3266_enabled: true + # Enable this to activate the REST auth password provider module. # See: https://github.com/ma1uta/matrix-synapse-rest-password-provider matrix_synapse_ext_password_provider_rest_auth_enabled: false diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 index aecaf0301..dbfbdffaf 100644 --- a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 +++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 @@ -2984,5 +2984,8 @@ experimental_features: {% if matrix_synapse_experimental_features_msc4108_enabled %} msc4108_enabled: true {% endif %} + {% if matrix_synapse_experimental_features_msc3266_enabled %} + msc3266_enabled: true + {% endif %} # vim:ft=yaml From c90e40b24d31e7ae763eb2d95138f5cd526fafed Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 8 Mar 2025 07:36:55 +0200 Subject: [PATCH 925/952] Upgrade exim-relay (v4.98.1-r0-1-0 -> v4.98.1-r0-2-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 7c11007ca..46fc6f727 100644 --- a/requirements.yml +++ b/requirements.yml @@ -19,7 +19,7 @@ version: v2.2.7-4 name: etherpad - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git - version: v4.98.1-r0-1-0 + version: v4.98.1-r0-2-0 name: exim_relay - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git version: v11.5.2-2 From 40446e341bac7b0994dbe1e8e49754c9df8936af Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sat, 8 Mar 2025 21:36:14 +0900 Subject: [PATCH 926/952] Update docs/configuring-playbook-email.md: copy from the ansible-role-exim-relay role's document and edit Based on https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/eac4201a0253e098983cdfee47c112790b3b198c/docs/configuring-exim-relay.md - Add instruction to enable DKIM - Replace the recommendation to use another SMTP server as relay, as DKIM has become available on exim-relay and configuring it greatly improves deliverability Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index a1d7dff76..658f66394 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -25,16 +25,22 @@ Docker automatically opens these ports in the server's firewall, so you likely d ## Adjusting the playbook configuration -### Relaying email through another SMTP server (optional) +### Enable DKIM authentication to improve deliverability (optional) -By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration (SPF settings, etc.) +By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration. + +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. + +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 document. + +💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server. + +### Relaying email through another SMTP server (optional) **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. 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. -💡 To improve deliverability, we recommend relaying email through another SMTP server anyway. - ### Disable mail service (optional) 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: From ffa1ff67eb45b8844d2d75eebf4790940afc60ee Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 8 Mar 2025 15:22:13 +0200 Subject: [PATCH 927/952] Recommend IPv6 enablement by default to all users Follow-up to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3218 --- CHANGELOG.md | 18 +++ docs/configuring-dns.md | 7 +- docs/configuring-playbook-ipv6.md | 191 ++++++++++++++++++++++++++++++ docs/configuring-playbook.md | 2 + docs/quick-start.md | 7 +- examples/vars.yml | 23 +++- 6 files changed, 242 insertions(+), 6 deletions(-) create mode 100644 docs/configuring-playbook-ipv6.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 070d18e17..4ccba7cf7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,21 @@ +# 2025-03-08 + +## 6️⃣ IPv6 support enablement recommended by default + +Our [default example configuration](./examples/vars.yml) and [Configuring DNS](./docs/configuring-dns.md) guides now recommend enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support. We recommend that everyone enables IPv6 support for their Matrix server, even if they don't have IPv6 connectivity yet. + +Our new [Configuring IPv6](./docs/configuring-playbook-ipv6.md) documentation page has more details about the playbook's IPv6 support. + +**Existing playbook users** will **need to do some manual work** to enable IPv6 support. This consists of: + +- enabling IPv6 support for the Docker container networks: + - add `devture_systemd_docker_base_ipv6_enabled: true` to their `vars.yml` configuration file + - stop all services (`just stop-all`) + - delete all container networks on the server: `docker network rm $(docker network ls -q)` + - re-run the playbook fully: `just install-all` + +- [configuring IPv6 (`AAAA`) DNS records](./docs/configuring-playbook-ipv6.md#configuring-dns-records-for-ipv6) + # 2025-02-26 ## 🪦 Bye-bye, Email2Matrix diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index a5c0918ab..62d4b7a55 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -27,10 +27,13 @@ To serve the base domain (`example.com`) and [Element Web](configuring-playbook- | Type | Host | Priority | Weight | Port | Target | | ----- | --------- | -------- | ------ | ---- | ---------------------| -| A | `matrix` | - | - | - | `matrix-server-IP` | +| A | `matrix` | - | - | - | `matrix-server-IPv4` | +| AAAA | `matrix` | - | - | - | `matrix-server-IPv6` | | CNAME | `element` | - | - | - | `matrix.example.com` | -As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine). +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. + +If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-playbook-ipv6.md) documentation page. 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. diff --git a/docs/configuring-playbook-ipv6.md b/docs/configuring-playbook-ipv6.md new file mode 100644 index 000000000..68fd29d2d --- /dev/null +++ b/docs/configuring-playbook-ipv6.md @@ -0,0 +1,191 @@ + +# Configuring IPv6 + +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. + +**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: + +- 📥 incoming IPv6 connectivity to the server via the server's IPv6 address/addresses (containers won't have their own individual publicly accessible IPs) +- 📤 outgoing IPv6 connectivity from the server via the server's IPv6 address/addresses (containers won't exit via their own individual IPv6 address) +- 🔄 IPv6 connectivity for cross-container communication + +**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) + +As such, **we recommend that you follow the default example configuration and leave IPv6 support for Docker enabled in all cases**. + +Enabling IPv6 consists of 2 steps: + +- [Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) +- [Configuring DNS records for IPv6](#configuring-dns-records-for-ipv6) + +💡 If you've followed a recent version of our documentation, you would have already done these steps, so there's nothing else to do. + +## Enabling IPv6 support for the playbook + +You can enable IPv6 support for all components' Docker container networks by using the following `vars.yml` configuration: + +```yml +# Controls whether container networks will be created with IPv6 support. +# +# If you also have IPv6 support on your server/network and AAAA DNS records pointing to the server, +# enabling this will effectively give you full public IPv6 connectivity (powered by NAT66). +# +# We recommend leaving this enabled even if you don't currently have IPv6 connectivity on your server/network. +# This way, once you eventually get IPv6 connectivity, you won't have to change anything (besides DNS records). +# +# Flipping this setting later on requires manual work (stopping services, deleting and recreating all container networks). +# +# In the future, this setting will likely default to `true`, so if you really want IPv6 disabled, explicitly set this to `false`. +# +# People managing Docker themselves and running an older Docker version will need additional configuration. +# +# Learn more in `docs/configuring-playbook-ipv6.md`. +devture_systemd_docker_base_ipv6_enabled: true +``` + +Doing this: + +- all container networks will be IPv6-enabled + +- NAT66 will be used, so that: + - containers will get [Unique Local Addresses (ULA)](https://en.wikipedia.org/wiki/Unique_local_address) + - the outgoing IPv6 address for containers will be the same as the one on the server + - traffic destined for the IPv6 address of the server will be forwarded to the containers that handle (and publish) that specific port + +> [!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. + +To confirm connectivity, see the following other resources: + +- [How do I check if my server has IPv6 connectivity?](#how-do-i-check-if-my-server-has-ipv6-connectivity) +- [How do I check outgoing IPv6 connectivity for containers?](#how-do-i-check-outgoing-ipv6-connectivity-for-containers) +- [How do I check incoming IPv6 connectivity for containers?](#how-do-i-check-incoming-ipv6-connectivity-for-containers) +- [How do I confirm if my container networks are IPv6-enabled?](#how-do-i-confirm-if-my-container-networks-are-ipv6-enabled) +- Ensure that the [Federation Tester](https://federationtester.matrix.org/) reports that your server is reachable over IPv6. + +## Configuring DNS records for IPv6 + +[Enabling IPv6 support for the playbook](#enabling-ipv6-support-for-the-playbook) tells you how to prepare for IPv6 on the container (Docker) side. + +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. + +Also see the [Configuring DNS settings](configuring-dns.md) documentation page for more details. + +### A note about old Docker + +With our [default example configuration](../examples/vars.yml), the playbook manages Docker for you and installs a modern-enough version. + +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. + +**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: + +- 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` + +- 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`). + +### Frequently Asked Questions + +#### How do I check if my server has IPv6 connectivity? + +##### With curl + +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. + +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. + +##### With other network utilities + +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). + +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. + +#### What does the `devture_systemd_docker_base_ipv6_enabled` setting actually do? + +The `devture_systemd_docker_base_ipv6_enabled` setting controls whether container networks will be created with IPv6 support. + +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). + +#### I've changed the `devture_systemd_docker_base_ipv6_enabled` setting, but it doesn't seem to have any effect. + +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). + +If you've previously installed with one `devture_systemd_docker_base_ipv6_enabled` value and then changed it to another, you need to: + +- stop all services (`just stop-all`) +- delete all container networks on the server: `docker network rm $(docker network ls -q)` +- re-run the playbook fully: `just install-all` + +#### How do I confirm if my container networks are IPv6-enabled? + +You can list container networks by running `docker network ls` on the server. + +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`. + +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) + +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). + +#### How do I check outgoing IPv6 connectivity for containers? + +```sh +docker run --rm --network=matrix-homeserver quay.io/curl/curl:latest curl -6 https://icanhazip.com +``` + +💡 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 + +✅ If this command returns an IPv6 address, you're all good. + +❌ If this command doesn't return an IPv6 address, it may be that: + +- 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. + +- 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. + +#### How do I check incoming IPv6 connectivity for containers? + +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. + +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)). + +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. + +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`. + +💡 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). + +#### Why enable IPv6 if my network doesn't support it yet? + +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). + +#### Can I use a custom subnet for IPv6? + +Not easily. + +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. + +There's no support for passing a custom subnet for IPv4 and IPv6. We let Docker auto-generate the subnets for us. + +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`). + +#### Can I use Global Unicast Addresses (GUA) for IPv6? + +No. You cannot have GUA addresses where each container is individually addressable over the public internet. + +The playbook only supports NAT66, which should be good enough for most use cases. + +Having containers get IPv6 addresses from your own GUA subnet requires complex configuration (ndp-proxy, etc.) and is not supported. + +You may find [this Reddit post](https://www.reddit.com/r/ipv6/comments/1alpzmb/comment/kphpw11/) interesting. + +#### Is there a performance penalty to enabling IPv6 if the server/network doesn't support IPv6 connectivity? + +Probably a tiny one, as services may try to make (unsuccessful) outgoing requests over IPv6. + +In practice, it's probably negligible. diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index da19662de..474a4c509 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -77,6 +77,8 @@ For a more custom setup, see the [Other configuration options](#other-configurat - [Controlling Matrix federation](configuring-playbook-federation.md) + - [Configuring IPv6](./configuring-playbook-ipv6.md) + ### Clients Web clients for Matrix that you can host on your own domains. diff --git a/docs/quick-start.md b/docs/quick-start.md index c9513c964..d4141580f 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -51,10 +51,13 @@ To configure Matrix services in the default settings, go to your DNS service pro | Type | Host | Priority | Weight | Port | Target | | ----- | ----------| -------- | ------ | ---- | ---------------------| -| A | `matrix` | - | - | - | `matrix-server-IP` | +| A | `matrix` | - | - | - | `matrix-server-IPv4` | +| AAAA | `matrix` | - | - | - | `matrix-server-IPv6` | | CNAME | `element` | - | - | - | `matrix.example.com` | -As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine). +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. + +If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-playbook-ipv6.md) documentation page. It might take some time for the DNS records to propagate after creation. diff --git a/examples/vars.yml b/examples/vars.yml index cc6aa8333..c3d1faa85 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -28,10 +28,29 @@ matrix_homeserver_generic_secret_key: '' # For alternatives, see `docs/configuring-playbook-own-webserver.md`. matrix_playbook_reverse_proxy_type: playbook-managed-traefik +# Controls whether container networks will be created with IPv6 support. +# +# If you also have IPv6 support on your server/network and AAAA DNS records pointing to the server, +# enabling this will effectively give you full public IPv6 connectivity (powered by NAT66). +# +# We recommend leaving this enabled even if you don't currently have IPv6 connectivity on your server/network. +# This way, once you eventually get IPv6 connectivity, you won't have to change anything (besides DNS records). +# +# Flipping this setting later on requires manual work (stopping services, deleting and recreating all container networks). +# +# In the future, this setting will likely default to `true`, so if you really want IPv6 disabled, explicitly set this to `false`. +# +# People managing Docker themselves and running an older Docker version will need additional configuration. +# +# Learn more in `docs/configuring-playbook-ipv6.md`. +devture_systemd_docker_base_ipv6_enabled: true + # A Postgres password to use for the superuser Postgres user (called `matrix` by default). # -# The playbook creates additional Postgres users and databases (one for each enabled service) -# using this superuser account. +# The playbook creates additional Postgres users and databases (one for each enabled service) using this superuser account. +# +# Changing this value subsequently requires manual work. +# The value used here must be shorter than 100 characters. postgres_connection_password: '' # By default, we configure coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file. From ce90df519eec013a4eed1e14842a38f0c8afc080 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sat, 8 Mar 2025 15:41:45 +0200 Subject: [PATCH 928/952] docs/configuring-playbook-ipv6.md -> docs/configuring-ipv6.md --- CHANGELOG.md | 4 ++-- docs/configuring-dns.md | 2 +- docs/{configuring-playbook-ipv6.md => configuring-ipv6.md} | 2 +- docs/configuring-playbook.md | 2 +- docs/quick-start.md | 2 +- examples/vars.yml | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) rename docs/{configuring-playbook-ipv6.md => configuring-ipv6.md} (99%) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4ccba7cf7..b223f3875 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,7 @@ Our [default example configuration](./examples/vars.yml) and [Configuring DNS](./docs/configuring-dns.md) guides now recommend enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support. We recommend that everyone enables IPv6 support for their Matrix server, even if they don't have IPv6 connectivity yet. -Our new [Configuring IPv6](./docs/configuring-playbook-ipv6.md) documentation page has more details about the playbook's IPv6 support. +Our new [Configuring IPv6](./docs/configuring-ipv6.md) documentation page has more details about the playbook's IPv6 support. **Existing playbook users** will **need to do some manual work** to enable IPv6 support. This consists of: @@ -14,7 +14,7 @@ Our new [Configuring IPv6](./docs/configuring-playbook-ipv6.md) documentation pa - delete all container networks on the server: `docker network rm $(docker network ls -q)` - re-run the playbook fully: `just install-all` -- [configuring IPv6 (`AAAA`) DNS records](./docs/configuring-playbook-ipv6.md#configuring-dns-records-for-ipv6) +- [configuring IPv6 (`AAAA`) DNS records](./docs/configuring-ipv6.md#configuring-dns-records-for-ipv6) # 2025-02-26 diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 62d4b7a55..398f5999b 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -33,7 +33,7 @@ To serve the base domain (`example.com`) and [Element Web](configuring-playbook- 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. -If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-playbook-ipv6.md) documentation page. +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. 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. diff --git a/docs/configuring-playbook-ipv6.md b/docs/configuring-ipv6.md similarity index 99% rename from docs/configuring-playbook-ipv6.md rename to docs/configuring-ipv6.md index 68fd29d2d..de6820a44 100644 --- a/docs/configuring-playbook-ipv6.md +++ b/docs/configuring-ipv6.md @@ -43,7 +43,7 @@ You can enable IPv6 support for all components' Docker container networks by usi # # People managing Docker themselves and running an older Docker version will need additional configuration. # -# Learn more in `docs/configuring-playbook-ipv6.md`. +# Learn more in `docs/configuring-ipv6.md`. devture_systemd_docker_base_ipv6_enabled: true ``` diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md index 474a4c509..fe1184ebd 100644 --- a/docs/configuring-playbook.md +++ b/docs/configuring-playbook.md @@ -77,7 +77,7 @@ For a more custom setup, see the [Other configuration options](#other-configurat - [Controlling Matrix federation](configuring-playbook-federation.md) - - [Configuring IPv6](./configuring-playbook-ipv6.md) + - [Configuring IPv6](./configuring-ipv6.md) ### Clients diff --git a/docs/quick-start.md b/docs/quick-start.md index d4141580f..ae9328f0a 100644 --- a/docs/quick-start.md +++ b/docs/quick-start.md @@ -57,7 +57,7 @@ To configure Matrix services in the default settings, go to your DNS service pro 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. -If you don't have IPv6 connectivity yet, you can skip the `AAAA` record. For more details about IPv6, see the [Configuring IPv6](./configuring-playbook-ipv6.md) documentation page. +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. It might take some time for the DNS records to propagate after creation. diff --git a/examples/vars.yml b/examples/vars.yml index c3d1faa85..b5e0b0a35 100644 --- a/examples/vars.yml +++ b/examples/vars.yml @@ -42,7 +42,7 @@ matrix_playbook_reverse_proxy_type: playbook-managed-traefik # # People managing Docker themselves and running an older Docker version will need additional configuration. # -# Learn more in `docs/configuring-playbook-ipv6.md`. +# Learn more in `docs/configuring-ipv6.md`. devture_systemd_docker_base_ipv6_enabled: true # A Postgres password to use for the superuser Postgres user (called `matrix` by default). From 52c75604c1f72068732f989bfa3afc8fee3b345b Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 9 Mar 2025 01:37:42 +0000 Subject: [PATCH 929/952] Update dependency setuptools to v75.9.0 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index c82e718f9..5489ef425 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.8.2 +setuptools==75.9.0 snowballstemmer==2.2.0 Sphinx==8.2.3 sphinx-intl==2.3.1 From 90d83bb5bceeafa629a8673b9f4e36e7059d6423 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Mar 2025 12:59:31 +0900 Subject: [PATCH 930/952] Update docs/configuring-playbook-email.md: minor edit Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-email.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 658f66394..2ab5fcdb9 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -31,7 +31,7 @@ By default, exim-relay attempts to deliver emails directly. This may or may not 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. -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 document. +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. 💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server. From 74b85d5b8773a75732ff0cca0bf4a326ea015920 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 9 Mar 2025 05:19:13 +0000 Subject: [PATCH 931/952] Update dependency setuptools to v75.9.1 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 5489ef425..3031fc5d7 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.9.0 +setuptools==75.9.1 snowballstemmer==2.2.0 Sphinx==8.2.3 sphinx-intl==2.3.1 From bd073bca742d98cd0254d2a5cf76b92a2bc60621 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 9 Mar 2025 16:03:15 +0200 Subject: [PATCH 932/952] Remove `/etc/docker/daemon.json` when no Docker options are set anymore --- group_vars/matrix_servers | 2 ++ .../docker_daemon_options_file_cleanup.yml | 20 +++++++++++++++++++ .../matrix_playbook_migration/tasks/main.yml | 9 +++++++++ 3 files changed, 31 insertions(+) create mode 100644 roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 7031927ee..45b5625b3 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -21,6 +21,8 @@ matrix_playbook_docker_installation_enabled: true matrix_playbook_docker_installation_daemon_options: "{{ matrix_playbook_docker_installation_daemon_options_auto | combine(matrix_playbook_docker_installation_daemon_options_custom, recursive=True) }}" +matrix_playbook_docker_installation_daemon_options_file_path: /etc/docker/daemon.json + # Since Docker 27.0.1, Docker daemon options do not need to be changed to enable IPv6 support on the daemon side. # See: https://docs.docker.com/engine/release-notes/27/#ipv6 # We only enable `ip6tables` and `experimental` for people who explicitly request it (perhaps due to running an old Docker version). diff --git a/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml new file mode 100644 index 000000000..9018d4a29 --- /dev/null +++ b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml @@ -0,0 +1,20 @@ +--- + +# ansible-role-docker creates the Docker daemon options file (`/etc/docker/daemon.json`) when options are set +# via `matrix_playbook_docker_installation_daemon_options` (which influences the `docker_daemon_options` variable of the role). +# See: https://github.com/geerlingguy/ansible-role-docker/blob/acade8d01f11bcd5efecba6d8211138d7567ce4b/tasks/main.yml#L53-L66 +# +# However, it doesn't delete the file when the options list is empty. +# +# This means that people who previously force-disabled IPv6 (and injected `{'ipv6': false}` options, etc) +# or had some other custom options had that file created for them. +# Later, when they stopped setting these options, they were stuck with the configuration file that still retained them. +# +# Here, we make the file go away of no options are set. +# Idealy, this task would be part of the `ansible-role-docker` role, but it's not (yet). +- name: Ensure the Docker daemon options file is deleted when no longer needed + when: matrix_playbook_docker_installation_daemon_options.keys() | length == 0 + ansible.builtin.file: + path: "{{ matrix_playbook_docker_installation_daemon_options_file_path }}" + state: absent + notify: restart docker diff --git a/roles/custom/matrix_playbook_migration/tasks/main.yml b/roles/custom/matrix_playbook_migration/tasks/main.yml index c11dbcb5b..a4ccb8e3c 100644 --- a/roles/custom/matrix_playbook_migration/tasks/main.yml +++ b/roles/custom/matrix_playbook_migration/tasks/main.yml @@ -28,6 +28,15 @@ block: - ansible.builtin.include_tasks: "{{ role_path }}/tasks/debian_docker_trusted_gpg_d_migration_migration.yml" +- when: matrix_playbook_docker_installation_enabled | bool + tags: + - setup-all + - install-all + - setup-docker + - install-docker + block: + - ansible.builtin.include_tasks: "{{ role_path }}/tasks/docker_daemon_options_file_cleanup.yml" + - tags: - setup-all - install-all From e33ed912cbda8b75f79bbc209aea140fbab9f8f1 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 9 Mar 2025 16:04:18 +0200 Subject: [PATCH 933/952] Reorder `matrix_playbook_docker_installation_daemon_options*` variables a bit --- group_vars/matrix_servers | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index 45b5625b3..cc7a09de6 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -21,8 +21,6 @@ matrix_playbook_docker_installation_enabled: true matrix_playbook_docker_installation_daemon_options: "{{ matrix_playbook_docker_installation_daemon_options_auto | combine(matrix_playbook_docker_installation_daemon_options_custom, recursive=True) }}" -matrix_playbook_docker_installation_daemon_options_file_path: /etc/docker/daemon.json - # Since Docker 27.0.1, Docker daemon options do not need to be changed to enable IPv6 support on the daemon side. # See: https://docs.docker.com/engine/release-notes/27/#ipv6 # We only enable `ip6tables` and `experimental` for people who explicitly request it (perhaps due to running an old Docker version). @@ -38,6 +36,8 @@ matrix_playbook_docker_installation_daemon_options_auto: | matrix_playbook_docker_installation_daemon_options_custom: {} +matrix_playbook_docker_installation_daemon_options_file_path: /etc/docker/daemon.json + # Controls whether to attach Traefik labels to services. # This is separate from `traefik_enabled`, because you may wish to disable Traefik installation by the playbook, # yet still use Traefik installed in another way. From 6d6fd4bf85ca8108d7d3c6e8af6e040e0e77bc57 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 9 Mar 2025 16:07:01 +0200 Subject: [PATCH 934/952] Add license information to `roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml` --- .../tasks/docker_daemon_options_file_cleanup.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml index 9018d4a29..a721412c2 100644 --- a/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml +++ b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml @@ -1,3 +1,7 @@ +# SPDX-FileCopyrightText: 2025 Slavi Pantaleev +# +# SPDX-License-Identifier: AGPL-3.0-or-later + --- # ansible-role-docker creates the Docker daemon options file (`/etc/docker/daemon.json`) when options are set From 35dd8e46cd66921c21e9c1c921fe29403b1cc611 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Sun, 9 Mar 2025 16:22:46 +0200 Subject: [PATCH 935/952] Adjust `/etc/docker/daemon.json` cleanup comment with link to ansible-role-docker PR --- .../tasks/docker_daemon_options_file_cleanup.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml index a721412c2..e7636161e 100644 --- a/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml +++ b/roles/custom/matrix_playbook_migration/tasks/docker_daemon_options_file_cleanup.yml @@ -16,6 +16,7 @@ # # Here, we make the file go away of no options are set. # Idealy, this task would be part of the `ansible-role-docker` role, but it's not (yet). +# See: https://github.com/geerlingguy/ansible-role-docker/pull/498 - name: Ensure the Docker daemon options file is deleted when no longer needed when: matrix_playbook_docker_installation_daemon_options.keys() | length == 0 ansible.builtin.file: From 87bdaf5bfebd1ef5a6ad60afa5404e31ea653697 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Sun, 9 Mar 2025 14:24:52 +0000 Subject: [PATCH 936/952] Update dependency setuptools to v76 --- i18n/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/requirements.txt b/i18n/requirements.txt index 3031fc5d7..35addfe1e 100644 --- a/i18n/requirements.txt +++ b/i18n/requirements.txt @@ -17,7 +17,7 @@ packaging==24.2 Pygments==2.19.1 PyYAML==6.0.2 requests==2.32.3 -setuptools==75.9.1 +setuptools==76.0.0 snowballstemmer==2.2.0 Sphinx==8.2.3 sphinx-intl==2.3.1 From c291d53d3ea1fbd12096b907fc64334f2c1c9f38 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 9 Mar 2025 16:27:49 +0000 Subject: [PATCH 937/952] Update docs/configuring-playbook-prometheus-grafana.md: warning message (#4159) --- docs/configuring-playbook-prometheus-grafana.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md index 6a32b5ab1..c426af8ff 100644 --- a/docs/configuring-playbook-prometheus-grafana.md +++ b/docs/configuring-playbook-prometheus-grafana.md @@ -6,7 +6,7 @@ SPDX-FileCopyrightText: 2021 Kim Brose SPDX-FileCopyrightText: 2021 Luca Di Carlo SPDX-FileCopyrightText: 2022 Olivér Falvai SPDX-FileCopyrightText: 2023 Michael Hollister -SPDX-FileCopyrightText: 2024 Suguru Hirahara +SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara SPDX-License-Identifier: AGPL-3.0-or-later --> @@ -16,9 +16,9 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install [Prometheus](https://prometheus.io/) with [Grafana](https://grafana.com/) and configure performance metrics of your homeserver with graphs for you. > [!WARNING] -> 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. +> 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. > -> 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. +> 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. ## Adjusting DNS records From 82c5afd214fc7429b5a707e63b25eaef1ba95a60 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 10 Mar 2025 07:08:49 +0200 Subject: [PATCH 938/952] Upgrade ntfy (v2.11.0-3 -> v2.11.0-4) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 46fc6f727..55bf8c9a5 100644 --- a/requirements.yml +++ b/requirements.yml @@ -28,7 +28,7 @@ version: v10078-1-0 name: jitsi - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git - version: v2.11.0-3 + version: v2.11.0-4 name: ntfy - src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git version: 201c939eed363de269a83ba29784fc3244846048 From 7e24667fc7817e56e9219984786e42d6341c897c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Mon, 10 Mar 2025 07:14:50 +0200 Subject: [PATCH 939/952] Upgrade traefik-certs-dumper (v2.8.3-7 -> v2.10.0-0) --- requirements.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.yml b/requirements.yml index 55bf8c9a5..556634277 100644 --- a/requirements.yml +++ b/requirements.yml @@ -67,7 +67,7 @@ version: v3.3.4-0 name: traefik - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git - version: v2.8.3-7 + version: v2.10.0-0 name: traefik_certs_dumper - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git version: v8.0.1-3 From fe71555dbcd62727ad9a969c608620009e5db984 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Mar 2025 08:36:17 +0000 Subject: [PATCH 940/952] Update docs: configuring-playbook-ntfy.md and others (#4160) * Update docs/configuring-playbook-ntfy.md: adopt the same description format as documentation for Jitsi and Etherpad Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md: introduction and other edits Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md: fix the link to the ansible-role-ntfy's documentation Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md: edit the list item Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md: the section for the web app Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md: re-add the note about subscribing to a notification topic Signed-off-by: Suguru Hirahara * Update docs: links to MASH project and its components Signed-off-by: Suguru Hirahara * Update docs/configuring-playbook-ntfy.md Co-authored-by: Slavi Pantaleev * Update docs/configuring-playbook-ntfy.md: create a section for the web app - Remove the reasoning on why the web app is disabled by default as it is uncommon among the playbook's documentation - Add the link to the official documentation about using the web app Signed-off-by: Suguru Hirahara --------- Signed-off-by: Suguru Hirahara Co-authored-by: Suguru Hirahara Co-authored-by: Slavi Pantaleev --- docs/configuring-playbook-backup-borg.md | 2 +- docs/configuring-playbook-email.md | 2 +- docs/configuring-playbook-etherpad.md | 3 +- docs/configuring-playbook-jitsi.md | 2 +- docs/configuring-playbook-ntfy.md | 92 ++++++++++---------- docs/configuring-playbook-postgres-backup.md | 2 +- 6 files changed, 52 insertions(+), 51 deletions(-) diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md index dabb8911c..b21c66ad1 100644 --- a/docs/configuring-playbook-backup-borg.md +++ b/docs/configuring-playbook-backup-borg.md @@ -14,6 +14,6 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service. -The Ansible role for BorgBackup is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). For details about configuring BorgBackup, you can check them via: +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: - 🌐 [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 - 📁 `roles/galaxy/backup_borg/docs/configuring-backup-borg.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index 2ab5fcdb9..5fcc4d820 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -13,7 +13,7 @@ By default, this playbook sets up an [Exim](https://www.exim.org/) relay SMTP ma **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. -The Ansible role for exim-relay is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay). For details about configuring exim-relay, you can check them via: +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: - 🌐 [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 - 📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md index 5c414cb00..30b204004 100644 --- a/docs/configuring-playbook-etherpad.md +++ b/docs/configuring-playbook-etherpad.md @@ -18,7 +18,8 @@ Etherpad is an open source collaborative text editor. It can not only be integra 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. -The Ansible role for Etherpad is developed and maintained by the [MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). For details about configuring Etherpad, you can check them via: +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: + - 🌐 [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 - 📁 `roles/galaxy/etherpad/docs/configuring-etherpad.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md index 5141cf3bb..59fd6b6c4 100644 --- a/docs/configuring-playbook-jitsi.md +++ b/docs/configuring-playbook-jitsi.md @@ -20,7 +20,7 @@ The playbook can install and configure the [Jitsi](https://jitsi.org/) video-con 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. -The Ansible role for Jitsi is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi). For details about configuring Jitsi, you can check them via: +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: - 🌐 [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 - 📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index 47c7d953a..b70e1212e 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -14,9 +14,15 @@ The playbook can install and configure the [ntfy](https://ntfy.sh/) push notific 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. -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. +See the project's [documentation](https://docs.ntfy.sh/) to learn what it does and why it might be useful to you. -**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. +**Notes**: +- To make use of your ntfy installation, you need to install [the `ntfy` app](https://docs.ntfy.sh/subscribe/phone/) on your device and configuring your UnifiedPush-compatible Matrix client. **Otherwise your device will not receive push notifications from the ntfy server.** Refer [this section](#usage) for details. +- This playbook focuses on setting up a ntfy server for getting it send UnifiedPush notifications to Matrix-related services that this playbook installs, while the installed server will be available for other non-Matrix apps as well like [Tusky](https://tusky.app/) and [DAVx⁵](https://www.davx5.com/). This playbook does not intend to support all of ntfy's features. + +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: +- 🌐 [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 +- 📁 `roles/galaxy/ntfy/docs/configuring-ntfy.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) ## Adjusting DNS records @@ -29,13 +35,25 @@ When setting, replace `example.com` with your own. To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml -# Enabling it is the only required setting +######################################################################## +# # +# ntfy # +# # +######################################################################## + ntfy_enabled: true -# Uncomment to enable the ntfy web app (disabled by default) -# ntfy_web_root: app # defaults to "disable" +######################################################################## +# # +# /ntfy # +# # +######################################################################## ``` +As the most of the necessary settings for the role have been taken care of by the playbook, you can enable ntfy on your Matrix server with this minimum configuration. + +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)). + ### Adjusting the ntfy URL (optional) By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one. @@ -49,15 +67,17 @@ ntfy_hostname: push.example.com After changing the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server. -### Extending the configuration +### Enable web app (optional) -There are some additional things you may wish to configure about the component. +ntfy also has a web app to subscribe to and push to topics from the browser. This 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. -Take a look at: +To enable the web app, add the following configuration to your `vars.yml` file: -- [ntfy role](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/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 `ntfy_configuration_extension_yaml` variable +```yaml +ntfy_web_root: app +``` -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). +See [the official documentation](https://docs.ntfy.sh/subscribe/web/) for details about how to use it. ## Installing @@ -74,29 +94,24 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju ## Usage -To make use of your ntfy installation, on Android for example, you need two things: +Unlike push notifications using Google's FCM or Apple's APNs, each end-user can choose the UnifiedPush-enabled push notification server that one prefer. This means that deploying a ntfy server does not ensure any particular user, device or Matrix client will use it. -* the `ntfy` app -* a UnifiedPush-compatible Matrix app +To receive push notifications from your ntfy server, you need to set up these two applications on your device: -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. +* [the `ntfy` app](https://docs.ntfy.sh/subscribe/phone/) +* a UnifiedPush-compatible Matrix client -### Setting up the `ntfy` Android app +For details about installing and configuring the `ntfy` app, take a look at [this section](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#setting-up-the-ntfy-android-app) on the role's documentation. -1. Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play. -2. In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`. -3. In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`. +**Note**: on the app you do not need to subscribe to a notification topic by yourself, as UnifiedPush will do that automatically. -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. +### Setting up a UnifiedPush-compatible Matrix client -### Setting up a UnifiedPush-compatible Matrix app +After installing the `ntfy` app, install any UnifiedPush-enabled Matrix client on that same device. The Matrix client 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. -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. +Steps needed for specific Matrix clients: -Steps needed for specific Matrix apps: - -* FluffyChat-android: - - Should auto-detect and use it. No manual settings. +* FluffyChat-android: this should auto-detect and use the app. No manual settings required. * SchildiChat-android: 1. enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`. @@ -107,23 +122,17 @@ Steps needed for specific Matrix apps: 1. choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy` 2. verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings` -If the Matrix app asks, "Choose a distributor: FCM Fallback or ntfy", then choose "ntfy". +If the Matrix client asks, "Choose a distributor: FCM Fallback or ntfy", then choose "ntfy". -If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below. - -### Web App - -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). - -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. +If the Matrix client doesn't seem to pick it up, try restarting it and try the Troubleshooting section below. ## Troubleshooting -### Check a client application +### Check the Matrix client -First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app. +First, make sure that the Matrix client you are using supports UnifiedPush. There may well be different variants of the app. -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. +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. 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. @@ -133,13 +142,4 @@ The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troublesh ### Check the service's logs -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-ntfy`. - -#### Increase logging verbosity - -If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook: - -```yaml -ntfy_configuration_extension_yaml: | - log_level: DEBUG -``` +See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#check-the-service-s-logs) on the role's documentation for details. diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md index 10c65643a..d5bd0fc87 100644 --- a/docs/configuring-playbook-postgres-backup.md +++ b/docs/configuring-playbook-postgres-backup.md @@ -10,7 +10,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you. -The Ansible role for docker-postgres-backup-local is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup). For details about configuring docker-postgres-backup-local, you can check them via: +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: - 🌐 [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 - 📁 `roles/galaxy/postgres_backup/docs/configuring-postgres-backup.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles) From 96adaf9916714606ce6c58b50802e7d72962d91d Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 10 Mar 2025 08:36:54 +0000 Subject: [PATCH 941/952] Update ghcr.io/matrix-org/rageshake Docker tag to v1.15.0 --- roles/custom/matrix-rageshake/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-rageshake/defaults/main.yml b/roles/custom/matrix-rageshake/defaults/main.yml index 38a9cf17a..a643619ae 100644 --- a/roles/custom/matrix-rageshake/defaults/main.yml +++ b/roles/custom/matrix-rageshake/defaults/main.yml @@ -24,7 +24,7 @@ matrix_rageshake_path_prefix: / # There are no stable container image tags yet. # See: https://github.com/matrix-org/rageshake/issues/69 # renovate: datasource=docker depName=ghcr.io/matrix-org/rageshake -matrix_rageshake_version: 1.14.0 +matrix_rageshake_version: 1.15.0 matrix_rageshake_base_path: "{{ matrix_base_data_path }}/rageshake" matrix_rageshake_config_path: "{{ matrix_rageshake_base_path }}/config" From ccab72aa2e883ed4728fa8c3cfc499ed6faacecb Mon Sep 17 00:00:00 2001 From: Aine Date: Mon, 10 Mar 2025 17:59:07 +0200 Subject: [PATCH 942/952] Postmoogle v0.9.25 --- roles/custom/matrix-bridge-postmoogle/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-postmoogle/defaults/main.yml b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml index 930225bd2..40013eb8d 100644 --- a/roles/custom/matrix-bridge-postmoogle/defaults/main.yml +++ b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml @@ -18,7 +18,7 @@ matrix_postmoogle_docker_repo_version: "{{ 'main' if matrix_postmoogle_version = matrix_postmoogle_docker_src_files_path: "{{ matrix_base_data_path }}/postmoogle/docker-src" # renovate: datasource=docker depName=ghcr.io/etkecc/postmoogle -matrix_postmoogle_version: v0.9.24 +matrix_postmoogle_version: v0.9.25 matrix_postmoogle_docker_image: "{{ matrix_postmoogle_docker_image_registry_prefix }}etkecc/postmoogle:{{ matrix_postmoogle_version }}" matrix_postmoogle_docker_image_registry_prefix: "{{ 'localhost/' if matrix_postmoogle_container_image_self_build else matrix_postmoogle_docker_image_registry_prefix_upstream }}" matrix_postmoogle_docker_image_registry_prefix_upstream: "{{ matrix_postmoogle_docker_image_registry_prefix_upstream_default }}" From 1313f1e4149218b4d20ff01e795daedfd32c7a39 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 19:05:18 +0200 Subject: [PATCH 943/952] Make base domain root path redirect also handle URLs with query strings (passing them along) Previously `https://example.com` and `https://example.com/` would be redirected to `https://matrix.example.com`. However, `https://example.com/?something` was not handled and was tried to be served as a file by matrix-static-files for this base domain. From now on, paths containing query strings will be handled as well and the query string will be passed along. Example: `https://example.com/?something` -> `https://matrix.example.com/?something` --- group_vars/matrix_servers | 2 +- roles/custom/matrix-static-files/defaults/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers index cc7a09de6..f3eca1dc7 100755 --- a/group_vars/matrix_servers +++ b/group_vars/matrix_servers @@ -6094,7 +6094,7 @@ matrix_static_files_container_labels_base_domain_traefik_hostname: "{{ matrix_do # If we're not serving a static webpage, serve a redirect instead of a 404. matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: "{{ not matrix_static_files_file_index_html_enabled }}" -matrix_static_files_container_labels_base_domain_root_path_redirection_url: "{{ ('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_matrix }}" +matrix_static_files_container_labels_base_domain_root_path_redirection_url: "{{ ('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_matrix }}/${1}" matrix_static_files_file_matrix_client_property_io_element_jitsi_preferred_domain: "{{ matrix_server_fqn_jitsi if jitsi_enabled else '' }}" diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml index 045d28b70..38d014157 100644 --- a/roles/custom/matrix-static-files/defaults/main.yml +++ b/roles/custom/matrix-static-files/defaults/main.yml @@ -91,7 +91,7 @@ matrix_static_files_container_labels_base_domain_traefik_tls: "{{ matrix_static_ matrix_static_files_container_labels_base_domain_traefik_tls_certResolver: "{{ matrix_static_files_container_labels_traefik_tls_certResolver }}" # noqa var-naming # Controls whether the root path (/) at the base domain would respond with a redirect to some URL. matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false -matrix_static_files_container_labels_base_domain_root_path_redirection_regex: "^{{ matrix_static_files_scheme }}://{{ matrix_static_files_container_labels_base_domain_traefik_hostname }}{{ matrix_static_files_container_labels_base_domain_traefik_path_prefix }}$" +matrix_static_files_container_labels_base_domain_root_path_redirection_regex: "^{{ matrix_static_files_scheme }}://{{ matrix_static_files_container_labels_base_domain_traefik_hostname }}{{ matrix_static_files_container_labels_base_domain_traefik_path_prefix }}(\\?.*)?$" matrix_static_files_container_labels_base_domain_root_path_redirection_url: "" # matrix_static_files_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file. From 178f7a9fffc3264553d1c17c83df05d33a263817 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 19:14:08 +0200 Subject: [PATCH 944/952] Upgrade Element Web (v1.11.94 -> v1.11.95) --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 237214cf1..ccd9c3c3f 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -29,7 +29,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=ghcr.io/element-hq/element-web -matrix_client_element_version: v1.11.94 +matrix_client_element_version: v1.11.95 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}element-hq/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" From bda63024ee9e879abcd5e439dd7d2dfee4d17e33 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 19:14:37 +0200 Subject: [PATCH 945/952] Upgrade Synapse (v1.125.0 -> v1.126.0) --- roles/custom/matrix-synapse/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml index 7742f4764..9a99d5cd1 100644 --- a/roles/custom/matrix-synapse/defaults/main.yml +++ b/roles/custom/matrix-synapse/defaults/main.yml @@ -16,7 +16,7 @@ matrix_synapse_enabled: true matrix_synapse_github_org_and_repo: element-hq/synapse # renovate: datasource=docker depName=ghcr.io/element-hq/synapse -matrix_synapse_version: v1.125.0 +matrix_synapse_version: v1.126.0 matrix_synapse_username: '' matrix_synapse_uid: '' From 16f9e7dd46c899963d8fc6cedcfac82b383aac55 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 19:25:31 +0200 Subject: [PATCH 946/952] Revert "Upgrade Element Web (v1.11.94 -> v1.11.95)" This reverts commit 178f7a9fffc3264553d1c17c83df05d33a263817. Element v1.11.95 doesn't seem to work. The container starts and is unhealthy. Until this is investigated and fixed, reverting. --- roles/custom/matrix-client-element/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index ccd9c3c3f..237214cf1 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -29,7 +29,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=ghcr.io/element-hq/element-web -matrix_client_element_version: v1.11.95 +matrix_client_element_version: v1.11.94 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}element-hq/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" From e65d198841b4bcd84224fae9c739bdd71c8537eb Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 22:21:47 +0200 Subject: [PATCH 947/952] Run Element Web in tightened/read-only mode without a custom nginx config Newer Element Web versions allow for the nginx port to be overriden, etc., and provide instructions for running in read-only mode. This makes our custom `nginx.conf` patches unnecessary. Passing the correct `ELEMENT_WEB_PORT` environment variable also helps with future changes. Another benefit of this (besides keeping closer to upstream recommendations and the improved simplicity) is that: - the container can run its entrypoint env-substitutions code now, without reporting errors - IPv6 for nginx works, so `matrix-client-element:8080` is accessible via IPv6 on the container network now (this affects only for Traefik's communicaton with Element Web internally; public connectivity was handled by Traefik and IPv6 was available there even before) Ref: - https://github.com/element-hq/element-web/blob/2052080d7d8a213064910cac491ec5cf9057610e/docs/install.md#docker - https://github.com/element-hq/element-web/pull/28849 - https://github.com/element-hq/element-web/pull/28840 --- .../matrix-client-element/defaults/main.yml | 7 ++ .../tasks/setup_install.yml | 7 +- .../matrix-client-element/templates/env.j2 | 1 + .../templates/nginx.conf.j2 | 66 ------------------- .../templates/nginx.conf.j2.license | 4 -- .../systemd/matrix-client-element.service.j2 | 8 ++- 6 files changed, 20 insertions(+), 73 deletions(-) create mode 100644 roles/custom/matrix-client-element/templates/env.j2 delete mode 100644 roles/custom/matrix-client-element/templates/nginx.conf.j2 delete mode 100644 roles/custom/matrix-client-element/templates/nginx.conf.j2.license diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 237214cf1..28309355e 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -48,9 +48,16 @@ matrix_client_element_container_network: '' # Use this to expose this container to a reverse proxy, which runs in a different container network. matrix_client_element_container_additional_networks: [] +# Controls the in-container port that Element will use. +# +# Also see: `matrix_client_element_container_http_host_bind_port` +matrix_client_element_container_port: 8080 + # Controls whether the matrix-client-element container exposes its HTTP port (tcp/8080 in the container). # # Takes an ":" or "" value (e.g. "127.0.0.1:8765"), or empty string to not expose. +# +# Also see: `matrix_client_element_container_port` matrix_client_element_container_http_host_bind_port: '' # matrix_client_element_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container. diff --git a/roles/custom/matrix-client-element/tasks/setup_install.yml b/roles/custom/matrix-client-element/tasks/setup_install.yml index 730e50282..10a8b61ae 100644 --- a/roles/custom/matrix-client-element/tasks/setup_install.yml +++ b/roles/custom/matrix-client-element/tasks/setup_install.yml @@ -95,12 +95,17 @@ owner: "{{ matrix_user_username }}" group: "{{ matrix_user_groupname }}" with_items: - - {src: "{{ role_path }}/templates/nginx.conf.j2", name: "nginx.conf"} - {src: "{{ role_path }}/templates/labels.j2", name: "labels"} + - {src: "{{ role_path }}/templates/env.j2", name: "env"} - {src: "{{ matrix_client_element_page_template_welcome_path }}", name: "welcome.html"} - {src: "{{ matrix_client_element_embedded_pages_home_path }}", name: "home.html"} when: "item.src is not none" +- name: Ensure Element Web nginx.conf file is removed + ansible.builtin.file: + path: "{{ matrix_client_element_data_path }}/nginx.conf" + state: absent + - name: Ensure Element Web config files removed ansible.builtin.file: path: "{{ matrix_client_element_data_path }}/{{ item.name }}" diff --git a/roles/custom/matrix-client-element/templates/env.j2 b/roles/custom/matrix-client-element/templates/env.j2 new file mode 100644 index 000000000..a142b6205 --- /dev/null +++ b/roles/custom/matrix-client-element/templates/env.j2 @@ -0,0 +1 @@ +ELEMENT_WEB_PORT={{ matrix_client_element_container_port }} diff --git a/roles/custom/matrix-client-element/templates/nginx.conf.j2 b/roles/custom/matrix-client-element/templates/nginx.conf.j2 deleted file mode 100644 index fba16bbdc..000000000 --- a/roles/custom/matrix-client-element/templates/nginx.conf.j2 +++ /dev/null @@ -1,66 +0,0 @@ -#jinja2: lstrip_blocks: "True" -# This is a custom nginx configuration file that we use in the container (instead of the default one), -# because it allows us to run nginx with a non-root user. -# -# For this to work, the default vhost file (`/etc/nginx/conf.d/default.conf`) also needs to be removed. -# (mounting `/dev/null` over `/etc/nginx/conf.d/default.conf` works well) -# -# The following changes have been done compared to a default nginx configuration file: -# - default server port is changed (80 -> 8080), so that a non-root user can bind it -# - various temp paths are changed to `/tmp`, so that a non-root user can write to them -# - the `user` directive was removed, as we don't want nginx to switch users - -worker_processes 1; - -error_log /var/log/nginx/error.log warn; -pid /tmp/nginx.pid; - - -events { - worker_connections 1024; -} - - -http { - proxy_temp_path /tmp/proxy_temp; - client_body_temp_path /tmp/client_temp; - fastcgi_temp_path /tmp/fastcgi_temp; - uwsgi_temp_path /tmp/uwsgi_temp; - scgi_temp_path /tmp/scgi_temp; - - include /etc/nginx/mime.types; - default_type application/octet-stream; - - log_format main '$remote_addr - $remote_user [$time_local] "$request" ' - '$status $body_bytes_sent "$http_referer" ' - '"$http_user_agent" "$http_x_forwarded_for"'; - - access_log /var/log/nginx/access.log main; - - sendfile on; - #tcp_nopush on; - - keepalive_timeout 65; - - #gzip on; - - server { - listen 8080; - server_name localhost; - - root /usr/share/nginx/html; - - location / { - index index.html index.htm; - } - - location ~* ^/(config(.+)?\.json$|(.+)\.html$|i18n) { - expires -1; - } - - error_page 500 502 503 504 /50x.html; - location = /50x.html { - root /usr/share/nginx/html; - } - } -} diff --git a/roles/custom/matrix-client-element/templates/nginx.conf.j2.license b/roles/custom/matrix-client-element/templates/nginx.conf.j2.license deleted file mode 100644 index f54d32e63..000000000 --- a/roles/custom/matrix-client-element/templates/nginx.conf.j2.license +++ /dev/null @@ -1,4 +0,0 @@ -SPDX-FileCopyrightText: 2019 - 2022 Slavi Pantaleev -SPDX-FileCopyrightText: 2019 Hugues De Keyzer - -SPDX-License-Identifier: AGPL-3.0-or-later diff --git a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 index 834e5cb87..1b1903b49 100644 --- a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 +++ b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 @@ -22,11 +22,15 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --read-only \ --network={{ matrix_client_element_container_network }} \ {% if matrix_client_element_container_http_host_bind_port %} - -p {{ matrix_client_element_container_http_host_bind_port }}:8080 \ + -p {{ matrix_client_element_container_http_host_bind_port }}:{{ matrix_client_element_container_port }} \ {% endif %} --label-file={{ matrix_client_element_data_path }}/labels \ + --env-file={{ matrix_client_element_data_path }}/env \ --tmpfs=/tmp:rw,noexec,nosuid,size=10m \ - --mount type=bind,src={{ matrix_client_element_data_path }}/nginx.conf,dst=/etc/nginx/nginx.conf,ro \ + --tmpfs=/var/cache/nginx:rw,mode=777 \ + --tmpfs=/var/run:rw,mode=777 \ + --tmpfs=/tmp/element-web-config:rw,mode=777 \ + --tmpfs=/etc/nginx/conf.d:rw,mode=777 \ --mount type=bind,src={{ matrix_client_element_data_path }}/config.json,dst=/app/config.json,ro \ --mount type=bind,src={{ matrix_client_element_data_path }}/config.json,dst=/app/config.{{ matrix_server_fqn_element }}.json,ro \ {% if matrix_client_element_location_sharing_enabled %} From a5d850d800d63ac9a758d400a24d44852204a47a Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 22:28:16 +0200 Subject: [PATCH 948/952] Add `matrix_client_element_environment_variable_element_web_port` and `matrix_client_element_environment_variables_extension` variables --- roles/custom/matrix-client-element/defaults/main.yml | 12 ++++++++++++ roles/custom/matrix-client-element/templates/env.j2 | 4 +++- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index 28309355e..c38ae8649 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -349,3 +349,15 @@ matrix_client_element_location_sharing_map_style_content_sources_localsource_att # Optional URL to redirect the user to after they have logged out. # See https://github.com/element-hq/element-web/blob/develop/docs/config.md#sso-setup matrix_client_element_logout_redirect_url: '' + +# Controls the `ELEMENT_WEB_PORT` environment variable. +matrix_client_element_environment_variable_element_web_port: "{{ matrix_client_element_container_port }}" + +# Additional environment variables to pass to the container. +# +# Environment variables take priority over settings in the configuration file. +# +# Example: +# matrix_client_element_environment_variables_extension: | +# ELEMENT_WEB_PORT=8080 +matrix_client_element_environment_variables_extension: '' \ No newline at end of file diff --git a/roles/custom/matrix-client-element/templates/env.j2 b/roles/custom/matrix-client-element/templates/env.j2 index a142b6205..152f7cc30 100644 --- a/roles/custom/matrix-client-element/templates/env.j2 +++ b/roles/custom/matrix-client-element/templates/env.j2 @@ -1 +1,3 @@ -ELEMENT_WEB_PORT={{ matrix_client_element_container_port }} +ELEMENT_WEB_PORT={{ matrix_client_element_environment_variable_element_web_port }} + +{{ matrix_client_element_environment_variables_extension }} From 40732e359440276580b4f2b5e16b2e8b2621468c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 11 Mar 2025 22:28:55 +0200 Subject: [PATCH 949/952] Upgrade Element Web (v1.11.94 -> v1.11.95) and patch healthcheck Related to: - https://github.com/element-hq/element-web/pull/29471 - 16f9e7dd46c899963d8fc6cedcfac82b383aac55 --- roles/custom/matrix-client-element/defaults/main.yml | 12 ++++++++++-- .../systemd/matrix-client-element.service.j2 | 7 +++++++ 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml index c38ae8649..763ba1c97 100644 --- a/roles/custom/matrix-client-element/defaults/main.yml +++ b/roles/custom/matrix-client-element/defaults/main.yml @@ -29,7 +29,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}" # renovate: datasource=docker depName=ghcr.io/element-hq/element-web -matrix_client_element_version: v1.11.94 +matrix_client_element_version: v1.11.95 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_registry_prefix }}element-hq/element-web:{{ matrix_client_element_version }}" matrix_client_element_docker_image_registry_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_client_element_docker_image_registry_prefix_upstream }}" @@ -110,6 +110,14 @@ matrix_client_element_container_extra_arguments: [] # List of systemd services that matrix-client-element.service depends on matrix_client_element_systemd_required_services_list: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}" +# Controls the healthcheck command for the container. +# +# Leave empty to use the default (upstream) command. +# +# The default command is a patch until https://github.com/element-hq/element-web/pull/29471 +# lands in a release. +matrix_client_element_container_healthcheck_cmd: "wget -q --spider http://localhost:$ELEMENT_WEB_PORT/config.json" + # Specifies the value of the `X-XSS-Protection` header # Stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. # @@ -360,4 +368,4 @@ matrix_client_element_environment_variable_element_web_port: "{{ matrix_client_e # Example: # matrix_client_element_environment_variables_extension: | # ELEMENT_WEB_PORT=8080 -matrix_client_element_environment_variables_extension: '' \ No newline at end of file +matrix_client_element_environment_variables_extension: '' diff --git a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 index 1b1903b49..9a1475b49 100644 --- a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 +++ b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 @@ -13,6 +13,10 @@ Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}" ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop -t {{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-client-element 2>/dev/null || true' ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-client-element 2>/dev/null || true' +{# + The custom healthcheck command is a patch until https://github.com/element-hq/element-web/pull/29471 + lands in a release. +#} ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --rm \ --name=matrix-client-element \ @@ -40,6 +44,9 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \ --mount type=bind,src={{ matrix_client_element_data_path }}/home.html,dst=/app/home.html,ro \ {% endif %} --mount type=bind,src={{ matrix_client_element_data_path }}/welcome.html,dst=/app/welcome.html,ro \ + {% if matrix_client_element_container_healthcheck_cmd %} + --health-cmd="{{ matrix_client_element_container_healthcheck_cmd }}" \ + {% endif %} {% for arg in matrix_client_element_container_extra_arguments %} {{ arg }} \ {% endfor %} From 72f28474c255e1ee4f63fa92926007e07e896266 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Wed, 12 Mar 2025 12:26:11 +0900 Subject: [PATCH 950/952] Update roles/custom/matrix-client-element/templates/env.j2: add the copyright header Signed-off-by: Suguru Hirahara --- roles/custom/matrix-client-element/templates/env.j2 | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/roles/custom/matrix-client-element/templates/env.j2 b/roles/custom/matrix-client-element/templates/env.j2 index 152f7cc30..83d1cdca0 100644 --- a/roles/custom/matrix-client-element/templates/env.j2 +++ b/roles/custom/matrix-client-element/templates/env.j2 @@ -1,3 +1,9 @@ +{# +SPDX-FileCopyrightText: 2025 Slavi Pantaleev + +SPDX-License-Identifier: AGPL-3.0-or-later +#} + ELEMENT_WEB_PORT={{ matrix_client_element_environment_variable_element_web_port }} {{ matrix_client_element_environment_variables_extension }} From 104bc63741252b9584fa4bbc40b90f74d22f85f7 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 10 Mar 2025 17:56:09 +0900 Subject: [PATCH 951/952] Fix docs/configuring-playbook-ntfy.md: link to the role's documentation Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ntfy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index b70e1212e..b30aa2153 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -142,4 +142,4 @@ The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troublesh ### Check the service's logs -See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/docs/configuring-etherpad.md#check-the-service-s-logs) on the role's documentation for details. +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. From 5ece1fea5a1a7084e8a937e774487b418bdf9c42 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Tue, 11 Mar 2025 17:58:05 +0900 Subject: [PATCH 952/952] Update docs/configuring-playbook-ntfy.md: reflect the role's documentation Based on https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/4e27dafc5cd48e1ce0804613f5a2afb94f9d8256/docs/configuring-ntfy.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-ntfy.md | 64 +++++++++++++++++++------------ 1 file changed, 40 insertions(+), 24 deletions(-) diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md index b30aa2153..8d5a63997 100644 --- a/docs/configuring-playbook-ntfy.md +++ b/docs/configuring-playbook-ntfy.md @@ -1,5 +1,6 @@